1.2.3 installers for Mac and Linux are not archives

Hello,
When I download 1.23 for Mac and Linux from https://github.com/ccsb-scripps/AutoDock-Vina/releases, files come without tgz extensions. Adding tgz or tar.gz to file does not allow to open archive with tar.
How to use these installers?
Thanks,
Misha

I found out how to open it
thanks

Sorry, I thought I figured it out by adding gz but clicking on Mac just makes it cpgz.
How to open these files?
thanks

Hi. They are not installers. These files are meant to be executed in the command line.

Hi Diogo,
Thanks for this.
Can I ask you not related question?
Do you know if there is MGL Tools compiled for Catalina, and higher? For 64 bit Mac.
Best,
Misha
Mikhael Guy
Research Scientist
Science Research Software Core
Yale Center for Research Computing
Yale University
P.O. Box 208107
Sterling Chemistry Laboratory
225 Prospect Street, Rm. 154
New Haven, CT 06520
203.436.8599
For questions related to scientific, analytical and computational software, please e-mail at<EMAIL_ADDRESS>On Aug 9, 2022, at 1:09 AM, Diogo<EMAIL_ADDRESS>wrote:
Hi. They are not installers. These files are meant to be executed in the command line.
—
Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fccsb-scripps%2FAutoDock-Vina%2Fissues%2F127%23issuecomment-1208921739&data=05|01|mikhael.guy%40yale.edu|a61bd72b0ff24356686b08da79c5613b|dd8cbebb21394df8b4114e3e87abeb5c|0|0|637956185890577244|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=HpdW1Emk2mLxpkoogWhEkwCLrmfltfkDz%2Bi9FfxHKtc%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAUVZLV5VSWQPBEYIHCBQRU3VYHRZVANCNFSM557KRC4A&data=05|01|mikhael.guy%40yale.edu|a61bd72b0ff24356686b08da79c5613b|dd8cbebb21394df8b4114e3e87abeb5c|0|0|637956185890577244|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=0LzJ4%2BFLWzhaVRHYUrDrehjgU1EPAEHjKDz78b9Cojo%3D&reserved=0.
You are receiving this because you modified the open/close state.Message ID: @.***>

MGLTools is a collection of tools, I don't know if they all work on Catalina, sorry. The autodock mailing list might know: https://autodocksuite.scripps.edu/support/

@diogomart , using Mac M1 and download the vina_1.2.2_macos_arm64 release, but I can't use it as an executable. Please, am I maybe forgetting something?

@RomuloBarrosPI what error do you get?

@RomuloBarrosPI what error do you get?

@diogomart , thanks so much for your attention.
I get an error message saying there is no application set to opening the document “vina_1.2.2_macos_arm64”.

So it is like mac is seeing it as a simple document and not as an executable file.

You need to run it from the command line, i.e. ./vina_1.2.2_macos_arm64. You may need to give permission to execute with the chmod command. If you are not familiar with the command line, this linux tutorial may help.

This is just awesome. It almost did it!
I typed this:chmod 777 ./vina_1.2.2_macos_arm64, and then ./vina_1.2.2_macos_arm64. Had to tweak Mac's System Secutiry & Privacy to allow it to run.
It ran, but I got this error: '/usr/local/lib/libboost_system.dylib' (no such file)

I gonna keep trying.

Wow!! Got it @diogomart !
just running brew install boost did the job!
Thank you so much for your help! This may also help others with the same problem on a Mac M1 and M2 processors.

Awesome!


Build 1.0.1 bundle end-to-end daily

Rename 1.0 manifest to 1.0.1 and kick off automation daily.
Meta issue of bundle building end-to-end with all its related remaining work.

[x] https://github.com/opensearch-project/opensearch-build/issues/148
[x] https://github.com/opensearch-project/opensearch-build/issues/149
[x] https://github.com/opensearch-project/opensearch-build/issues/200
[ ] https://github.com/opensearch-project/opensearch-build/issues/153
[x] https://github.com/opensearch-project/opensearch-build/issues/135
[x] https://github.com/opensearch-project/opensearch-build/issues/113

While some automation is being used now, we punted on running end-to-end for 1.0.1. cc: @peterzhuamazon if you think otherwise.


Dev/ah mvn

@TomKimsey @oliver-walker-hms When you get the chance, this is still pending for review. The bulk of functionality changes are in commit https://github.com/hms-networks/flexy-thingworx-connector/pull/60/commits/d6ce3ba9fe7c5c6446866c2bda4353e7ada031dc

@TomKimsey @oliver-walker-hms When you get the chance, this is still pending for review. The bulk of functionality changes are in commit d6ce3ba

Sorry about that, for some reason it doesnt show up in my review requests.

@TomKimsey @oliver-walker-hms When you get the chance, this is still pending for review. The bulk of functionality changes are in commit d6ce3ba

Sorry about that, for some reason it doesnt show up in my review requests.

No problem, I've had that happen before.


[BEAM-22] Allow InProcess TransformEvaluators to refuse inputs

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[x] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[x] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[x] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[x] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

Inputs that cannot be processed (generally due to a side input not being
ready) can be added to a list of unprocessed elements, which will
schedule them to be executed at a later point.
Built on top of #282, and includes that PR.

R: @kennknowles
will rebase appropriately if #282 is merged. o/w feel free to only review the later commit.

LGTM. Will merge.


Water Glitching Out

PLEASE DO NOT USE THIS FORM TO REQUEST FEATURES!  THIS IS FOR BUG REPORTS ONLY!
If you wish to discuss new features, please join our Discord server: http://discord.smrpgspeedruns.com
Console or Emulator: zsnesw151
If emulator state which emulator and version.  If console, state which flash cart firmware.
Flags (paste flag string if available): Ks Rk Cjl Tc4 M2 Sb4 Ef B Qa P1 Nbmq D4s
Description of problem: Water flickers blindingly and/or is covered by a flat texture in Midas River, Rose Way, and Tadpole Pond.

Also: Game softlocked when I tried to switch Amulet and Scrooge Ring on Mario in Equip Menu.

That's because you're using zsnes.  This emulator uses various speed hacks that don't emulate things properly, and doesn't handle SA-1 games properly at all.  It's completely banned in any speedrunning activities for this reason.  Try one of the recommended emulators from the site: https://randomizer.smrpgspeedruns.com/how-to-play


Update official scenario configs to armory v0.11.1

Updating official scenario configs to armory v0.11.1

LGTM

CI tests failing because black formatting version needs to be pinned on this repo.


Errors

I tried you verification enrollment api. I created a profile and I created some wav files with the requested format, containing one of the verification sentences. I tried with 2 different sentences, byt I always get { error: { code: 'BadRequest', message: 'InvalidPhrase' } }....

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

ID: 3604fe7e-46a3-6f5b-41e0-d3e69e01c8ae
Version Independent ID: 9415c8a5-177e-fe11-7198-3d97ed438dc8
Content: Speaker Recognition API
Content Source: articles/cognitive-services/Speaker-recognition/Home.md
Service: cognitive-services
GitHub Login: @dwlin
Microsoft Alias: dwlin

@raffax
Thanks for the feedback! We are currently investigating and will update you shortly.

Enroll1.zip

I leave here a sample file,  hope it can be helpful
Enroll1.zip

Is there any update about this? I'm getting the same cad request


[Key Vault - Certificates]Integration test libraries failing in nightly runs

Key Vault - Certificates nightly test runs are failing with:

Error message:
Trace: [Internal Error]
at D:\a_work\1\s\common\tools\dev-tool\src\index.ts:10:11
at processTicksAndRejections (node:internal/process/task_queues:95:5)
The script failed with exit code 255
##[error]Cmd.exe exited with code '255'.
Finishing: Integration test libraries

For more details check here:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=3162078&view=results

Certificates tests have been fairly stable lately, closing for now


Split package openpgp to make it reusable

Is your feature request related to a problem? Please describe.
I'd like to reuse openpgp package, but depending on a maven-plugin is a no-no.
Describe the solution you'd like
Ideally a small reusable openpgp library that is used by this plugin as a dependency. Same stands for me, I'd like to depend on new openpgp.
Describe alternatives you've considered
Lift the sources? :smile:
Additional context
Maven Plugins are just that: maven plugins and are not reusable as libs. Hence, I myself always tend to keep maven-plugins as "thin" as possible (basically just config + calls into "real thing").

Good idea.
There is a Commons OpenPGP project under Apache Commons sandboxes ... we can try to reactivate it
https://commons.apache.org/sandbox/commons-openpgp/index.html

I'd keep it out of a (dead) ASF project, just do it here.


buildDotnetModule: fix PublishAOT failing on .NET7 and above

Description of changes
The necessary libraries require patchelf to successfully publish a
Native AOT package.
jitinterface_x64.so: cannot open shared object file: No such file or directory

Extracted from #267743 . I don't know the tests, but this patchelf alone unbreaks PublishAOT packaging.
Closes: #280923

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

In patch-nupkgs we do --add-rpath instead of --set-rpath.  I wonder if we should do the same here?
https://github.com/NixOS/nixpkgs/blob/6d7edef8d2def6997ea8f2ec03f3b0d8223531b4/pkgs/development/compilers/dotnet/patch-nupkgs.nix#L66
I do plan on unifying all this package patching stuff at some point.
Also I'm currently working on a minimal AOT test:
https://github.com/corngood/nixpkgs/commit/dotnet-tests

Why close?

I have been working on and off on AOT support.  Current progress is here: https://github.com/corngood/nixpkgs/commits/dotnet-aot
It's working fine on linux, but I'm still trying to sort out some toolchain stuff on darwin...

see #309409


*: add pause memchanism

Example
// gofail: var pausePoint struct{}

and notify the wait chan in runtime:
runtime.Enable("....","pause")

until Disable the Failpoint.

Will the forked gofail support Go packages outside the GOPATH ?
@nolouch

@tiancaiamao Hope so but not now. Maybe you can give us some help.


Wrong HEIGHT/WIDTH dimensions on GetMap responses for COG layers

GetMap responses generated from COG layers sometimes don't have the appropriate HEIGHT/WIDTH dimensions
As example, a request such as the following is producing an output of 256x54 (attached) instead of the expected 256x256.
https://beta.datacube-dev.cgp-pgc.ca/ows/aerial?service=WMS&request=GetMap&layers=salish-1970-1980&styles=&format=image%2Fpng&transparent=false&version=1.3.0&width=256&height=256&crs=EPSG%3A3857&bbox=-13736651.227185596,6339992.874085658,-13697515.468703587,6379128.63256767

This is producing stretched or misplaced image in web tools such as OpenLayers or Leaflet

Also an example of how the WMS is actually configured
salish-1970-1980 = {
        type = "rastersourceconf"
        name = "salish-1970-1980"
        title = "1970-1980 - NAPL photos over Salish area"
        source = "s3://datacube-dev-data/cogs/napl-salish-1970-1980.tif"
        #overview-strategy = "auto-0"
        default-style = "default"
    }

After further testing, it appears that this issue is present when the GetMap request involves reprojection (e.g. requested CRS is different than the COG reference system) and when the image origin (top-left corner) is outside of the COG coverage.

It was fixed in terms of https://github.com/locationtech/geotrellis/pull/3252
GeoTiffRasterSource region reproject produced incorrect results.
@jfbourgon could you doublecheck that with the current master the issue is gone?
The output that I got by using the same parameters that are in the url from the issue description:
$ gdalinfo download

Driver: PNG/Portable Network Graphics
Files: download
Size is 256, 256
Coordinate System is `'
Image Structure Metadata:
  INTERLEAVE=PIXEL
Corner Coordinates:
Upper Left  (    0.0,    0.0)
Lower Left  (    0.0,  256.0)
Upper Right (  256.0,    0.0)
Lower Right (  256.0,  256.0)
Center      (  128.0,  128.0)
Band 1 Block=256x1 Type=Byte, ColorInterp=Red
  Mask Flags: PER_DATASET ALPHA
Band 2 Block=256x1 Type=Byte, ColorInterp=Green
  Mask Flags: PER_DATASET ALPHA
Band 3 Block=256x1 Type=Byte, ColorInterp=Blue
  Mask Flags: PER_DATASET ALPHA
Band 4 Block=256x1 Type=Byte, ColorInterp=Alpha

This is also looking good from my end. Attached a screen capture, all tiled WMS images now have the proper dimensions even when a reprojection is involved.


Translation System

Hey all. I have a question here about translation system. May I know how can I get an empty translation string to translate the bot? I have try to use "import from source" method from poedit and it didn't return any string for me to translate. I also have try the CMD method using gettext tools that come with python as well. Same thing happend, nothing has been return for me to translate. May I know the exact way to do it? Thanks.

May I know, which file will got effected in order to fix this bug? Because
I have my own copy of the bot that I already make changes to it. Thanks.
On Tue, Nov 30, 2021, 9:42 PM Vladislav Kopylov @.***>
wrote:

The string extraction script is currently broken. This is going to be
fixed soon.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/gumerov-amir/TTMediaBot/issues/51#issuecomment-982648328,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM64WYVV3VKF3GT4TO4HR4LUOTIF5ANCNFSM5JB25XTQ
.

tools/compile_locales.py

Only that file? Because I have make changes in the TeamTalk init.py. I
change the default status. I also have totally edit the commands
init.py, admin_commands.py and user_commands.py. With the changes, the
config and app_vars.py also effected.
On Tue, Nov 30, 2021, 9:47 PM Vladislav Kopylov @.***>
wrote:

tools/compile_locales.py
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/gumerov-amir/TTMediaBot/issues/51#issuecomment-982651758,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM64WYT4XHPBXMJNHZXKGFTUOTIWHANCNFSM5JB25XTQ
.

That's mean I no need to worry about those file accept the compile_local.py
in site the tools folder only. I have edit that file also but just change
the file name for the po and mo file. "translation.py" also not got
effected right? Sorry if I ask to many. Just want to make sure for the
update preparation. Thanks.
On Tue, Nov 30, 2021, 10:10 PM Vladislav Kopylov @.***>
wrote:

Yes. The problem is in that file.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/gumerov-amir/TTMediaBot/issues/51#issuecomment-982671417,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM64WYXQFOYH6XYL7O4C4VTUOTLMNANCNFSM5JB25XTQ
.

Don't worry. Everything will be fixed.

Thanks. I hope I can learn many things from this source code. Are you have
telegram or other contact information so that I can send you message if I
have any question to ask about python?
On Tue, Nov 30, 2021, 10:18 PM Vladislav Kopylov @.***>
wrote:

Don't worry. Everything will be fixed.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/gumerov-amir/TTMediaBot/issues/51#issuecomment-982678769,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM64WYTAFZHNJ6RBADNNGQLUOTMKVANCNFSM5JB25XTQ
.

@lbk2907 https://t.me/a11cf0


SA-19554 Extend cloudera scm manager start timeout

Firstly I will confirm by this branches code.

I don't think that it will help. In tests:
https://jenkins.bigdata.9livesdata.com/view/Platform/job/sa_platform_install_with_external_hadoop_secured/70/consoleFull
this command ends instantaneously. This "reaching timeout" may just not complete at all.

Below result, were 64 seconds passed during wait?
Then I thought waiting time affects result.
11:09:59  task path: /ansible/roles/scm/handlers/main.yml:9
11:11:07  ok: [ec2-34-218-234-17.us-west-2.compute.amazonaws.com] => {"changed": false, "elapsed": 64, "path": null, "port": 7180, "search_regex": null, "state": "started"}
11:11:07  META: ran handlers```

Yes, sorry, I made a mistake.
And I see that in AWS message:
2019-07-24 04:31:19,094 INFO ScmActive-0:com.cloudera.server.cmf.components.ScmActive: ScmActive completed successfully.

comes after a minute delay, so I think you are right.


Add twitter tweet image support

Only seems to work for videos ATM

I can't do this, only youtubedl can do this :(


Get-SecureUEFI can't get dbt variable.

Get-SecureBootUEFI used the wrong GUID (EFI_GLOBAL_VARIABLE_GUID) so cause it can not get dbt.
In UEFI spec 2.8, define the EFI_IMAGE_SECURITY_DATABASE2(dbt) should use the EFI_IMAGE_SECURITY_DATABASE_GUID, so this is the power shell command issue, you can refer to UEFI spec 2.8 - 32.6.1 UEFI Image Variable GUID & Variable Name for detail.

@YunSyuan Get-SecureBootUEFI is not in the repo. Please report on UserVoice site or use Windows 10 Feedback tool.


Is it possible to finetune codet5 with the programming language which is not a part of codesearchnet dataset.

If it is not possible is pretraining codet5 with that new programming language dataset the only option?

Hi, it is possible that fine-tuning CodeT5 on a new programming language (PL) would achieve a reasonable result, as different PLs might share some common patterns and this allows transfer learning to another PL. For example, we find that fine-tuning CodeT5 on Apex yields good results (as shown in the GIF animation) as it is very similar to Java.


ci(gui-client/linux): publish deb package in the release

### Before merging
- [x] (FAILED) Test CI deb on Ubuntu 24.04 #4883
- [x] Wait for everything else to merge: #3884
- [x] Fix #4889
- [x] Fix #4890
- [x] Test on Ubuntu 20.04 (683bddc0b passed)
- [x] Test on Ubuntu 22.04 (683bddc0b passed)
- [x] diff between main and 683bddc0b to make sure nothing in the code changed
- [ ] Someone other than me should give it a once-over. `intended_behavior.md` has the manual smoke test I've been doing on it. Install script is <https://github.com/firezone/firezone/blob/a943a9dba1797317327563bb2de48e22f239175a/scripts/firezone-client-gui-install.sh> Deb package from CI is <https://github.com/firezone/firezone/actions/runs/8972824465/artifacts/1477261361>

I'm not aware of any. I think we've been using the GitHub CLI as long as I've been here

Blocked on #4898


Xray integration

I have one suggestion to have a better synergy between Xray and Karate for you to consider.
In order to have a better experience between the tools it could be useful for the users to be able to refer a test case or requirement in Xray to connect to the Karate test, with this change users that want to link the Karate test case to a test case in the Xray side can by using tags, in the same way if they want to link a test to a requirement they could also using tags. I added a possible example of this for you to consider, in the feature file we can see new tags: @xray_requirement=CALC-1 @xray_test=CALC-2
Feature: sample karate test script

Background:

* url 'http://dummy.restapiexample.com/api/v1/'

@xray_requirement=CALC-1 @xray_test=CALC-2
Scenario: get all dummy users and then get the first user by id
Given path 'employees'
When method get
Then status 200

* def first = response.data[0]

Given path 'employee', first.id
When method get
Then status 200

That, when those tags exist, must be added to the report like we can see below:
<testsuite failures="0" name="examples/DummyUsers/dummyusers.feature" skipped="0" tests="2" time="3.646495">
	<testcase classname="examples.DummyUsers.dummyusers" name="[1:7] get all dummy users and then get the first user by id" time="2.036197">
		<properties>
			 <!-- using a custom "test_key" property -->
			 <property name="test_key" value="CALC-2" />
			<!-- using a custom "requirement" property -->
			 <property name="requirement" value="CALC-1" />
		</properties>
		<system-out>
		* url 'http://dummy.restapiexample.com/api/v1/' ........................... passed
		Given path 'employees' .................................................... passed
		When method get ........................................................... passed
		Then status 200 ........................................................... passed
		* def first = response.data[0] ............................................ passed
		Given path 'employee', first.id ........................................... passed
		When method get ........................................................... passed
		Then status 200 ........................................................... passed
		</system-out>
	</testcase>
(...)
</testsuite>

Once this information is added to the report it will be used in the Xray importation and link the test to the requirement and test.

I'd like the community to comment - will adding these extra XML elements break any tools that depend on the JUnit XML

Just to add here some info and some thoughts. Properties at testcase level are not common even though some other tools (e.g. Datadog) also follow a similar approach. Tools making a strict validation of the schema may not like this but AFAIK it should not be a issue. More, my recommendation would be to only add the <properties> element under the <testcase>, if any of those properties is provided. That way, we would ensure the report stays as it is for users that don't use these new tags.

Well @borzykin , it's true that a generic way could be applied but it all depends on the goal. If the goal was to provide a unidirectional link, so it would be present on the Karate report on the respective Scenarios to have a quick way to jump to the test management tool, that approach would perhaps make more sense.
However, here the goal is not just to provide that link on the report; the goal is to be able to report results to existing tests in Xray/Jira that someone decided that should be automated,  so that the results will be added to them. More, also to automatically cover a existing Story/requirement right from the code in order to have to avoid doing it manually... so that whenever results are imported, the corresponding Test in Xray/Jira will be linked back to the identified story.  These are scenarios are highly common among teams, based on our experience.
The mentioned goal requires that the information that is passed to Xray (i.e. the JUnit  XML report in this case) has some specific information that Xray can process in order to link the the results back to the correct entities.

I tried linking scenarios to xray. With Junit report, the tickets were identified by feeature pathname. Was not very refactoring friendly. Then I moved to cucumber report. With cucubmer, tickets were linked to tags correctly, but can tickets had to be predefined already. So I had to create a script that makes a xray json.
I don't know if Xray now can identify Junit report by tags. If yes, upvote for this suggestion. If now, you better of using cucumber report, as it have all the tags needed.

I agree that this change will be very helpful. And I hope Xray will also enable this feature on Xray Server as well.

Hi @bltemrah,
Please check this tutorial: https://docs.getxray.app/display/XRAYCLOUD/Testing+APIs+using+Karate+DSL that we did showcasing a possible integration (that as originated this thread actually).

@CMCunha
Thank you for your prompt response. I found a valuable information in what you addressed. However, my FW based on gradle build which does not support XML report, I can only reach HTML report. Can you please let me know how I can integrate the gradle FW with Jira Xray?
Thanks in advance

@bltemrah I'm glad you find valuable information in the documentation. We also have a tutorial that can help you to integrate Gradle with Xray: https://docs.getxray.app/display/XRAYCLOUD/Integration+with+Gradle.

@CMCunha thank you. We use Karate FW with Gradle. So my question is here which one do I need to consider Gradle? or Karate fw? I lost myself in the below two web pages :) If Gradle works well, why do we need to apply the below?
https://docs.getxray.app/display/XRAYCLOUD/Testing+APIs+using+Karate+DSL
If the below Karate fw approach/solution works well, why do we need to use Gradle?
https://docs.getxray.app/display/XRAYCLOUD/Integration+with+Gradle.
I just confuse which one is important the build way or fw itself.
Thanks in advance

@bltemrah Xray is agnostic of the framework or tool you are using as long as it produces a compatible test report (junit, xunit, nunit, robot, behave, etc) that can be interpreted by Xray.
So if you are using Karate DSL to perform the tests and generate a Junit report you can follow this tutorial https://docs.getxray.app/display/XRAYCLOUD/Testing+APIs+using+Karate+DSL to see how to upload those results to Xray using an API call.
If you are using Gradle to compile and execute the tests and want to upload the results from the Gradle scripts you can do it following this tutorial https://docs.getxray.app/display/XRAYCLOUD/Integration+with+Gradle.
These are two use cases that showcase two possibilities to integrate with Xray, you should check what is best for your case and adapt to your situation. If you prefer you can use the API and import the results on the best place on your process making an API call: https://docs.getxray.app/display/XRAYCLOUD/Import+Execution+Results+-+REST.

Thank you for your statement @CMCunha
Actually, we need to run more than one "test case" in the one test scenario outline that has more than one scenario. We use "tag" for each test case, likes;

Today, I applied what guided in the below
https://docs.getxray.app/display/XRAYCLOUD/Integration+with+Gradle
with the below properties

Everything went well, and the report was directly integrated with the test plan in Xray. However, there is only one execution ticket created;

As I mentioned above, I run many test cases under this test scenarios. My question is  " is there any way to create the different test execution tickets based on "tag" defined on the scenario?
Thanks again

Whenever importing test results using a JUnit XML file,  each Junit  element on the JUnit XML report is mapped to a Test in Xray.
@bltemrah can you please clarify exactly the scenario outline you have and how those tags are applied? I got a bit confused with:  Actually, we need to run more than one "test case" in the one test scenario outline that has more than one scenario.
Note: usually, whenever you import results from a report file, only 1 Test Execution issue will be created; it will contain the test results (i.e. test runs), one per each testcase on the report... which in this case may correspond to a Scenario on your .feature file.

Hi @CMCunha,
I achieved the integration by using Jira UI way;

However, API approached did not work;

First I used the below authentication script to get token
curl -H "Content-Type: application/json" -X POST --data '{ "client_id": "API_KEY","client_secret": "API_SECRET" }' https://xray.cloud.getxray.app/api/v2/authenticate
and it returns a valid token.
After that, I used the below Post request script with the token received by using above script;
curl -H "Content-Type: text/xml" -X POST -H "Authorization: Bearer $token"  --data @"junit-new.xml" https://xray.cloud.getxray.app/api/v2/import/execution/junit?projectKey=XT&testPlanKey=XT-351
I got the below error;

Can you please help me to solve this problem.
Thanks in advance

Hi @bitcoder For example, the below scenario outline has more than one test case, and each test case has its own "Tag";  Let me share what I understood. I need to separate each test case with one test scenario, otherwise, it is not possible to see their test result separately in different test execution under the test plan or test set in Jira-Xray based on their "tag"

Yes, each Scenario is indeed a test scenario (or should be).

@CMCunha
When I checked the below;
https://docs.getxray.app/display/XRAYCLOUD/Exporting+Cucumber+Tests+-+REST+v2
It shows an example request;
curl -H "Content-Type: application/json" -X GET -H "Authorization: Bearer $token"  "https://xray.cloud.getxray.app/api/v2/export/cucumber?keys=DEMO-6;DEMO-7"
As you see, this script is particularly for cucumber. Do you think we can use it without "cucumber" as mentioned below;
https://docs.getxray.app/display/XRAYCLOUD/Testing+APIs+using+Karate+DSL#tab-API

@bltemrah
The cucumber example you are referring to is to export scenarios written in Xray to your code, the first example you were talking about was about importing test results to Xray. Are you writing scenarios in Xray and want to export those?
Regarding the error of the request you are showing it seems that you need to enclose the URL with " in order to be considered with all parameters.
Replace the last part from:
--data @"junit-new.xml" https://xray.cloud.getxray.app/api/v2/import/execution/junit?projectKey=CQA&testPlanKey=CQA-811
to
--data @"junit-new.xml" "https://xray.cloud.getxray.app/api/v2/import/execution/junit?projectKey=CQA&testPlanKey=CQA-811"

Hi @CMCunha
Thank you so much. It works once adding URL btw "".
For your 1st point, I do not write the scenarios in Xray.
I really thank you for your assistance.

If you do not mind, I have 2 more quick questions @CMCunha
In the karate fw, we should run our tests only with/in ParallelRunner to generate .xml report in the "Build" folder.

Otherwise, the running test in the feature generates the test report under the "Target" folder with HTML type, NOT .xml format. Also, the test report is not created under "build" folder if we run the test in the feature;

As seen, we need .xml test report for the above script (as mentioned on the below page) to integrate and directly send our test report to Jira-Xray.
https://docs.getxray.app/display/XRAYCLOUD/Testing+APIs+using+Karate+DSL#tab-API
My question;

Is there any way to get .xml report of test results without using ParallelRunner? meaning directly run the test in the feature;

Can we use the scripts (as we have discussed in the previous msgs) with different test reports such as Json or Html? If yes, how can we get JSON report in karate fw with Gradle build? Under the "Target" folder, I can only have below;

Thanks again.

@bltemrah
1. Is there any way to get .xml report of test results without using ParallelRunner? meaning directly run the test in the feature;
-> From my understanding you must use ParallelRunner to generate xml reports.
2. Can we use the scripts (as we have discussed in the previous msgs) with different test reports such as Json or Html? If yes, how can we get JSON report in karate fw with Gradle build? Under the "Target" folder, I can only have below;
-> Xray does not support HTML or other custom reports, the full list of supported formats is here: https://docs.getxray.app/display/XRAYCLOUD/Import+Execution+Results+-+REST , so in order to upload results to Xray you must obtain one report that is compatible.
Make sure that you are using the .outputJunitXml(true) method to generate the xml report as it is described in the tutorial: https://docs.getxray.app/display/XRAYCLOUD/Testing+APIs+using+Karate+DSL (look at the class ExamplesTest.java).

Thank you, @CMCunha
For the below URL, is it possible to Post a different ticket type than "testPlanKey", i.e. Test Set or Story?
"https://xray.cloud.getxray.app/api/v2/import/execution/junit?projectKey=CQA&testPlanKey=CQA-811"

@bltemrah No, it is not possible to define a Test Set or Story in the API call to Xray.
Please check the possible parameters to use in the import request here: https://docs.getxray.app/display/XRAYCLOUD/Import+Execution+Results+-+REST#ImportExecutionResultsREST-JUnitXMLresults.

Hi @CMCunha,
After running the below script to send our test scenario results to Jira Xray, it will create a test case for each test scenario.
curl -H "Content-Type: text/xml" -X POST -H "Authorization: Bearer TOKEN"  --data @"io.token.features.adapter.obie.unitedKingdom.Natwest_PIS.xml" "https://xray.cloud.getxray.app/api/v2/import/execution/junit?projectKey=CQA&testExecKey=CQA-1077"
We do not expect that Jira Xray create a test case ticket for the same scenario. However, if its classname or name in the .XML report as seen below is different, Jira Xray creates a new test case again and again;
* def theBank = bankDetails.UnitedKingdom.Natwest ......................... passed

call read(makePayment) .................................................. failed

Stack Trace:
com.intuit.karate.KarateException: driver config / start failed: http call failed after 2 milliseconds for url: http://localhost:9222/json, options: {type=chrome, headless=false, target=null}
classpath:io/token/webAppConsent/genericWebAppActions.feature:77
classpath:io/token/webAppConsent/unitedkingdom/NatWestBank_PIS.feature:51
classpath:io/token/features/generic/pisGeneric.feature:222
classpath:io/token/features/adapter/obie/unitedKingdom/Natwest_PIS.feature:9
at <feature>.: * call read(makePayment) (classpath:io/token/features/adapter/obie/unitedKingdom/Natwest_PIS.feature:9:9)

<testcase classname="io.token.features.adapter.obie.unitedKingdom.Natwest_PIS" name="PIS - fasterPayments - TPP should successfully initiate with mandatory and optional fields" time="87.593227">* def theBank = bankDetails.UnitedKingdom.Natwest ......................... passed

def enableOptionalFields = true ......................................... passed
call read(makePayment) .................................................. passed

<testcase classname="io.token.features.adapter.obie.unitedKingdom.Natwest_PIS" name="PIS - fasterPayments - Tpp should sucessfully initiate a future-dated payment (if supported)" time="94.048597">*

My question is how we ignore classname or name in the above script by adding something to prohibit a creating a different test case for the same test scenario?
Thanks
Emrah

Hi @bltemrah , Xray creates a Test entity based on the classname+name attributes of the <testcase> element on the JUnit XML report. If a Test already exists with that identifier (which is stored on the Generic Definition field on the Test issue), then it will just report results against it; otherwise, it creates/autoprovision the Test.
If your scenario results in <testcase>  elements on the JUnit XML with different identifiers, then Xray will consider them as different tests; this is the standard behavior of Xray whenever handling JUnit XML files (more info here).
From my understanding, you wanted to have just one Test in Xray corresponding to the whole Scenario Outline that you have in karate, instead of having one Test per each row of the Example section of the scenario outline? Is that it?
I'm not sure exactly about the internals of karate and the current logic on how scenarios are mapped to testcase elements on the JUnit XML report.

Hi @bitcoder,
First, thanks for your prompt response. Let me make it clear. We have the below test scenario (not scenario outline);
Scenario: PIS - sepa - TPP should successfully initiate with mandatory fields only
* call read(makePayment)
I need to run this test scenario for several different banks such as HSBC, NatWest and Commerz. Even though I run the same test case, XML report has a different name and classname because of the changing of the Bank name in the below path for each Bank;
name="io/token/features/adapter/obie/unitedKingdom/Commerz_PIS.feature"
name="io/token/features/adapter/obie/unitedKingdom/HSBC_PIS.feature"
name="io/token/features/adapter/obie/unitedKingdom/NatWest_PIS.feature"
As you see, the test case is same, so it is better for us not to see/have more than one test case related to the same scenario even though we run it for the different banks. Can you please let me know how we can handle this issue? Is there any solution/way?
Thanks in advance
Emrah

@bltemrah , If possible, can you please shaer exactly your full Scenario specification ?

@bitcoder
Here it is;
Scenario: PIS - sepa - TPP should successfully initiate with mandatory fields only

call read(makePayment)

@makePayment
And configure continueOnStepFailure = { enabled: true, continueAfter: true, keywords: ['match'] }
* call read('classpath:io/token/features/generic/pisGeneric.feature@initiatePISRequest')
* if (disableFutureDatedPaymentConversion == true) karate.call(true, "classpath:io/token/features/generic/pisGeneric.feature@futureDateConversionTrueScenario")
* if (disableFutureDatedPaymentConversion == true) karate.abort()
* call read(bankAuthToCall)
* if (isBetaFdt) karate.abort()
* if (isFdtTrue) karate.abort()
* call read('classpath:io/token/features/generic/pisGeneric.feature@getTransferDetails')
And match response.transfer.payload.amount.value == transferAmount
And match response.transfer.providerDetails.status == '#notnull'
* if (isReturnRefundAccount == true) karate.call(true, 'classpath:io/token/features/generic/pisGeneric.feature@checkReturnRefundAccount')
* call read('classpath:io/token/features/generic/pisGeneric.feature@checkIfTransferStatusMatchProviderDetailsStatus')
* if (makeFutureDatedPayment == true) karate.call(true, 'classpath:io/token/features/generic/pisGeneric.feature@checkFutureDatedPayment')
* if (isCheckTransactionStatusSecondTime == true) karate.call(true, 'classpath:io/token/features/generic/pisGeneric.feature@checkTransferStatusA2ndTime')
@initiatePISRequest
Scenario: Initiate PIS request
* def isPisScenario = true
* callonce read('classpath:io/token/features/generic/generic.feature@prepareBankAuthPathName')
* call read('classpath:io/token/features/generic/pisGeneric.feature@defineBankData')
* call read('classpath:io/token/features/generic/pisGeneric.feature@defineRequestPayload')
Given url apiUrl+"/token-requests"
And header Content-Type = "application/json"
And header Authorization = apiKey
* def apiKeyForConsent = apiKey
* basePisRequestPayload.requestPayload.refId = 'R'+refId
* basePisRequestPayload.requestPayload.description = 'D'+refId
* basePisRequestPayload.requestPayload.to.alias.value = alias
* basePisRequestPayload.requestPayload.to.id = memberId
* basePisRequestPayload.requestPayload.redirectUrl = callbackUrl
* basePisRequestPayload.requestOptions = bankId
* call read('classpath:io/token/features/generic/generic.feature@defineAuthorizationPath')
And request basePisRequestPayload
When method post
Then match responseStatus == 200
* def tokenRequestId = response.tokenRequest.id
@futureDateConversionTrueScenario
Scenario: Given futureDateConversion = true, this scenario to be called
Given url apiUrl+"/token-requests/"+tokenRequestId+"/authorization"
And header Authorization = apiKeyForConsent
And header Content-Type = "application/json"
And request { "consentAccepted":true }
When method post
Then status 400
* match response == "FAILED_PRECONDITION: Bank " + bankIdPlain + outOfOurOperationalHouseMessage
@getTransferDetails
Scenario: get token request result
Given url apiUrl+"/token-requests/"+tokenRequestId+"/token_request_result"
And header Authorization = apiKey
* retry until responseStatus == 200
When method get
Then match responseStatus == 200
* def tokenId = response.tokenId
* if (karate.match("getBanksInfo.requiresOneStepPayment == '#notpresent'").pass == true) karate.call(true,'classpath:io/token/features/generic/pisGeneric.feature@redeemTransferTokenTwoStep')
* def transferId = (karate.match("getBanksInfo.requiresOneStepPayment == '#notpresent'").pass == true) ? transferId : response.transferId
Given url apiUrl+ "/transfers/"+ transferId
And header Authorization = apiKey
* retry until responseStatus == 200
When method get
Then match responseStatus == 200

if you need other path, please let me know.

@bltemrah  you shared 4 scenarios, therefore I would expect, generally speaking, one <testcase>  entry on the JUnit XML report.
Weren't you just referring to the scenario "PIS - sepa - TPP should successfully initiate with mandatory fields only" ?
How do you run that scenario exactly against the different banks?

@bitcoder
Actually, it is only one scenario which calls others. I just run the below scenario which includes one test case;
Scenario: PIS - sepa - TPP should successfully initiate with mandatory fields only

call read(makePayment)

Even though the name of scenarios is "PIS - Sepa - TPP should successfully initiate with mandatory fields only", the classname and name is seen differently;
<testsuite failures="3" name="io/token/features/adapter/obie/unitedKingdom/Natwest_PIS.feature" skipped="0" tests="9" time="317.715079"><testcase classname="io.token.features.adapter.obie.unitedKingdom.Natwest_PIS" name="PIS - sepa - TPP should successfully initiate with mandatory fields only" time="40.285838">* def theBank = bankDetails.UnitedKingdom.Natwest ......................... passed

call read(makePayment) .................................................. passed

<testcase classname="io.token.features.adapter.obie.unitedKingdom.Natwest_PIS" name="PIS - sepa - TPP should successfully initiate with mandatory and optional fields" time="38.244523">* def theBank = bankDetails.UnitedKingdom.Natwest ......................... passed

As seen above, there are two different name. What name does Jira Xray consider?
As I mentioned in my old comment,
Since the name of the bank in "name="io/token/features/adapter/obie/unitedKingdom/Natwest_PIS.feature"
will be updated in each run, the path will also be changed. Although I run the same test case for each bank, Jira creates a new test case each time because the name has changed.
This is the issue that I need to solve.
Thanks

Hmm. Well, I think the issue you're facing is in the end because you're calling scenarios from within another scenarios (I'm not sure if that's a recommended practice or not in terms of Karate).
In terms of Xray, it will look at the testcase element on the junit report... and uses the classname and name attributes.
How Karate generates the junit xml report is beyond of Xray control; I don't know exactly those internals of Karate, so in that respect I'm unable to help, sorry.
This doc explains how Xray processes the Junit xml report.

@bitcoder thank you. FYI, There are two names in the karate creates XML reports, first is path, second is the scenario name. But, Xray considers the name which includes path, not the scenario name one. This is the problem that I need to solve. I want Xray create test case based on the scenario name, not path name.
<testsuite failures="3" name="io/token/features/adapter/obie/unitedKingdom/Natwest_PIS.feature" skipped="0" tests="9" time="317.715079"><testcase classname="io.token.features.adapter.obie.unitedKingdom.Natwest_PIS" name="PIS - sepa - TPP should successfully initiate with mandatory fields only" time="40.285838">* def theBank = bankDetails.UnitedKingdom.Natwest ......................... passed

Hi @bitcoder and @CMCunha
Is it possible to send the environment, which is already defined in the Jira-Xray, with/in the below script;
curl -H "Content-Type: text/xml" -X POST -H "Authorization: Bearer $TOKEN"  --data @"io.token.features.adapter.nextgenPsd2.germany.Commerz_AIS.xml" "https://xray.cloud.getxray.app/api/v2/import/execution/junit?projectKey=CQA&testPlanKey=CQA-TicketNumber"
curl -H "Content-Type: text/xml" -X POST -H "Authorization: Bearer $TOKEN"  --data @"io.token.features.adapter.nextgenPsd2.germany.Commerz_AIS.xml" "https://xray.cloud.getxray.app/api/v2/import/execution/junit?projectKey=CQA&testExecKey=CQA-TicketNumber"
If yes, does the Jira Xray automatically put all test results under the defined environment?

@bltemrah ,

you can pass the test environment using the "testEnvironments" parameter; please check the endpoint documentation here.

The results are not "put" under the defined environment (it doesn't work like that). Test Environments are like an attribute at the Test Execution level, affecting all the results (i.e. the Test Runs) that you report in the context of that Test Execution.  More info on Test Environments here.
In Xray cloud, you need to have the Test Environments created beforehand btw. Please check documentation.

Concerning triggering, it requires some customization effort depending on the CI/CD tool you use, etc. You can see some examples here.

@CMCunha @bitcoder regarding the proposed change to the JUnit XML output
if you can submit a PR I can include this in the next release

closing this ticket, it can be re-opened with a PR

Hi @ptrthomas
As mentioned above, the XML report in the karate fw displays like below;

we expect that the "name" has only the test case name, not the path. If its value has a path, Jira Xray creates a new test case ticket in the test case board even though you run the same test scenario/case.
Can you please fix this issue?
Thanks in advance

@bltemrah as mentioned above, I don't see this as a priority as this has nothing to do with karate. many teams are using the junit report in ci/cd with e.g. jenkins. this also hasn't been reported by anyone else. if this has to be changed all this has to be investigated and a PR should address all these concerns


how to add basic authenticator?

Hello, I am trying to implement basic authentication, but without success yet. Have you planned something similar?

Hi @lsjack93,
basic auth is not part of the router. This is an extra topic. I will not plan to add this to the router because this is has nothing to do with basic routing. You can use PHP to add basic auth before the routers run() method is called or you can add those logic inside single routes. Examples can be found here: https://www.php.net/manual/de/features.http-auth.php
If you are on Apache you can also use .htaccess basic auth to protect the whole app: https://homepage-kosten.de/htaccess/

Hi @lsjack93,
basic auth is not part of the router. This is an extra topic. I will not plan to add this to the router because this is has nothing to do with basic routing. You can use PHP to add basic auth before the routers run() method is called or you can add those logic inside single routes. Examples can be found here: https://www.php.net/manual/de/features.http-auth.php
If you are on Apache you can also use .htaccess basic auth to protect the whole app: https://homepage-kosten.de/htaccess/


[web] Error in flutter_service_worker.js

Steps to Reproduce

Create a Flutter Project with web enabled
Run flutter build web --release.

Expected results:
No errors in the service worker file
Actual results:
add() is used instead of push()
No method named add() exists for array in JavaScript
Cache variable used instead of caches (No variable named Cache exists)

Logs

[  +11 ms] executing: [/Users/aseef/SDKs/flutter/] git -c
log.showSignature=false log -n 1 --pretty=format:%H
[  +45 ms] Exit code 0 from: git -c log.showSignature=false log -n 1
--pretty=format:%H
[        ] 9d58a87066d1da98eb06826918e4b90cc76ae0ef
[        ] executing: [/Users/aseef/SDKs/flutter/] git tag --contains HEAD
[ +187 ms] Exit code 0 from: git tag --contains HEAD
[   +3 ms] executing: [/Users/aseef/SDKs/flutter/] git describe --match
*.*.*-*.*.pre --first-parent --long --tags
[ +151 ms] Exit code 0 from: git describe --match *.*.*-*.*.pre --first-parent
--long --tags
[        ] 1.19.0-1.0.pre-143-g9d58a8706
[   +9 ms] executing: [/Users/aseef/SDKs/flutter/] git rev-parse --abbrev-ref
--symbolic @{u}
[  +11 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/master
[        ] executing: [/Users/aseef/SDKs/flutter/] git ls-remote --get-url
origin
[  +10 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +59 ms] executing: [/Users/aseef/SDKs/flutter/] git rev-parse --abbrev-ref
HEAD
[  +11 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] master
[   +5 ms] executing: sw_vers -productName
[  +13 ms] Exit code 0 from: sw_vers -productName
[        ] Mac OS X
[        ] executing: sw_vers -productVersion
[  +12 ms] Exit code 0 from: sw_vers -productVersion
[        ] 10.15.4
[        ] executing: sw_vers -buildVersion
[  +13 ms] Exit code 0 from: sw_vers -buildVersion
[        ] 19E287
[  +34 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping
update.
[   +8 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required,
skipping update.
[  +18 ms] executing: /Users/aseef/Library/Android/sdk/platform-tools/adb
devices -l
[   +7 ms] executing: /usr/bin/xcode-select --print-path
[   +7 ms] Exit code 0 from: /usr/bin/xcode-select --print-path
[        ] /Applications/Xcode.app/Contents/Developer
[   +1 ms] executing: /usr/bin/xcodebuild -version
[ +435 ms] Exit code 0 from: /usr/bin/xcodebuild -version
[        ] Xcode 11.4.1
           Build version 11E503a
[   +2 ms] executing: xcrun --find xcdevice
[   +9 ms] Exit code 0 from: xcrun --find xcdevice
[        ] /Applications/Xcode.app/Contents/Developer/usr/bin/xcdevice
[        ] executing: xcrun xcdevice list --timeout 2
[   +3 ms] /usr/bin/xcrun simctl list --json devices
[        ] executing: /usr/bin/xcrun simctl list --json devices
[  +41 ms] List of devices attached
[  +97 ms] {
             "devices" : {
               "com.apple.CoreSimulator.SimRuntime.iOS-13-2" : [
                 {
                   "availabilityError" : "runtime profile not found",
                   "dataPath" :
                   "\/Users\/aseef\/Library\/Developer\/CoreSimulator\/Devices\/
                   CE784987-C6EC-4E5B-8BD1-6C6816522563\/data",
                   "logPath" :
                   "\/Users\/aseef\/Library\/Logs\/CoreSimulator\/CE784987-C6EC-
                   4E5B-8BD1-6C6816522563",
                   "udid" : "CE784987-C6EC-4E5B-8BD1-6C6816522563",
                   "isAvailable" : false,
                   "deviceTypeIdentifier" :
                   "com.apple.CoreSimulator.SimDeviceType.iPhone-8-Plus",
                   "state" : "Shutdown",
                   "name" : "iPhone 8 Plus"
                 },
                 {
                   "availabilityError" : "runtime profile not found",
                   "dataPath" :
                   "\/Users\/aseef\/Library\/Developer\/CoreSimulator\/Devices\/
                   94D40E1A-0901-458C-A660-014FC45FF489\/data",
                   "logPath" :
                   "\/Users\/aseef\/Library\/Logs\/CoreSimulator\/94D40E1A-0901-
                   458C-A660-014FC45FF489",
                   "udid" : "94D40E1A-0901-458C-A660-014FC45FF489",
                   "isAvailable" : false,
                   "deviceTypeIdentifier" :
                   "com.apple.CoreSimulator.SimDeviceType.iPhone-11",
                   "state" : "Shutdown",
                   "name" : "iPhone 11"
                 },
                 {
                   "availabilityError" : "runtime profile not found",
                   "dataPath" :
                   "\/Users\/aseef\/Library\/Developer\/CoreSimulator\/Devices\/
                   A7FC7EB6-DF36-495C-8A78-B14293A3C9F8\/data",
                   "logPath" :
                   "\/Users\/aseef\/Library\/Logs\/CoreSimulator\/A7FC7EB6-DF36-
                   495C-8A78-B14293A3C9F8",
                   "udid" : "A7FC7EB6-DF36-495C-8A78-B14293A3C9F8",
                   "isAvailable" : false,
                   "deviceTypeIdentifier" :
                   "com.apple.CoreSimulator.SimDeviceType.iPhone-11-Pro",
                   "state" : "Creating",
                   "name" : "iPhone 11 Pro"
                 },
                 {
                   "availabilityError" : "runtime profile not found",
                   "dataPath" :
                   "\/Users\/aseef\/Library\/Developer\/CoreSimulator\/Devices\/
                   43396A0E-4D2A-481C-9B3B-BA12FDE6CC31\/data",
                   "logPath" :
                   "\/Users\/aseef\/Library\/Logs\/CoreSimulator\/43396A0E-4D2A-
                   481C-9B3B-BA12FDE6CC31",
                   "udid" : "43396A0E-4D2A-481C-9B3B-BA12FDE6CC31",
                   "isAvailable" : false,
                   "deviceTypeIdentifier" :
                   "com.apple.CoreSimulator.SimDeviceType.iPhone-11-Pro-Max",
                   "state" : "Creating",
                   "name" : "iPhone 11 Pro Max"
                 },
               ],
             }
           }
[+3084 ms] [
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.4.1 (17E8260)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPad8,12",
                        "identifier" : "9F03EA65-602B-4D9D-B0FF-D262D2EC131B",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.ipad-pro-12point9-4th-1",
                        "modelName" : "iPad Pro (12.9-inch) (4th generation)",
                        "name" : "iPad Pro (12.9-inch) (4th generation)"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "6.2 (17T256)",
                        "available" : true,
                        "platform" : "com.apple.platform.watchsimulator",
                        "modelCode" : "Watch5,4",
                        "identifier" : "E38F4806-A5E2-4281-B54F-7BDBD702B821",
                        "architecture" : "i386",
                        "modelUTI" : "com.apple.watch-series5-1",
                        "modelName" : "Apple Watch Series 5 - 44mm",
                        "name" : "Apple Watch Series 5 - 44mm"
                      },{
                        "simulator" : true,
                        "operatingSystemVersion" : "13.4.1 (17E8260)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone10,5",
                        "identifier" : "DA3C4D56-43D4-4035-A83E-EFE65CEDAFAE",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.iphone-8-plus-2",
                        "modelName" : "iPhone 8 Plus",
                        "name" : "iPhone 8 Plus"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.4.1 (17E8260)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone11,8",
                        "identifier" : "25DFA499-7A1C-40C4-9D9A-F6C675BBC7D1",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.iphone-xr-1",
                        "modelName" : "iPhone Xʀ",
                        "name" : "iPhone XR"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.4.1 (17E8260)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone12,5",
                        "identifier" : "20E825BA-3456-42E7-A0D2-DDD8872B570E",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.iphone-11-pro-max-1",
                        "modelName" : "iPhone 11 Pro Max",
                        "name" : "iPhone 11 Pro Max"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.4.1 (17E8260)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone12,1",
                        "identifier" : "960D2BAC-4A4D-4B55-9F49-B3ECBF486EF3",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.iphone-11-1",
                        "modelName" : "iPhone 11",
                        "name" : "iPhone 11"
                      },
                    ]
[   +9 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping
update.
[   +3 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required,
skipping update.
[  +93 ms] Found plugin cloud_firestore at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/cloud_firestore-0.13.5/
[   +8 ms] Found plugin cloud_firestore_web at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/cloud_firestore_web-0.1.1+2/
[   +6 ms] Found plugin firebase_auth at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.16.0/
[   +3 ms] Found plugin firebase_auth_web at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/firebase_auth_web-0.1.2/
[   +2 ms] Found plugin firebase_core at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/firebase_core-0.4.4+3/
[   +3 ms] Found plugin firebase_core_web at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/firebase_core_web-0.1.1+2/
[   +2 ms] Found plugin fluttertoast at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/fluttertoast-3.1.3/
[   +2 ms] Found plugin google_sign_in at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/google_sign_in-4.5.1/
[   +2 ms] Found plugin google_sign_in_web at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/google_sign_in_web-0.9.1+1/
[  +59 ms] Found plugin cloud_firestore at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/cloud_firestore-0.13.5/
[   +2 ms] Found plugin cloud_firestore_web at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/cloud_firestore_web-0.1.1+2/
[   +4 ms] Found plugin firebase_auth at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.16.0/
[   +2 ms] Found plugin firebase_auth_web at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/firebase_auth_web-0.1.2/
[   +1 ms] Found plugin firebase_core at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/firebase_core-0.4.4+3/
[   +2 ms] Found plugin firebase_core_web at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/firebase_core_web-0.1.1+2/
[   +2 ms] Found plugin fluttertoast at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/fluttertoast-3.1.3/
[   +1 ms] Found plugin google_sign_in at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/google_sign_in-4.5.1/
[   +1 ms] Found plugin google_sign_in_web at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/google_sign_in_web-0.9.1+1/
[  +72 ms] Generating
/Users/aseef/Desktop/FlutterWebProjects/cigarette_track/android/app/src/main/jav
a/io/flutter/plugins/GeneratedPluginRegistrant.java
[ +161 ms] Launching lib/main.dart on Chrome in debug mode...
[  +60 ms] Updating assets
[ +153 ms] Manifest contained wildcard assets. Inserting missing file into build
graph to force rerun. for more information see #56466.
[   +5 ms] Syncing files to device Chrome...
[   +7 ms] Found plugin cloud_firestore at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/cloud_firestore-0.13.5/
[   +1 ms] Found plugin cloud_firestore_web at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/cloud_firestore_web-0.1.1+2/
[   +2 ms] Found plugin firebase_auth at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.16.0/
[   +1 ms] Found plugin firebase_auth_web at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/firebase_auth_web-0.1.2/
[        ] Found plugin firebase_core at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/firebase_core-0.4.4+3/
[   +1 ms] Found plugin firebase_core_web at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/firebase_core_web-0.1.1+2/
[   +1 ms] Found plugin fluttertoast at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/fluttertoast-3.1.3/
[        ] Found plugin google_sign_in at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/google_sign_in-4.5.1/
[   +1 ms] Found plugin google_sign_in_web at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/google_sign_in_web-0.9.1+1/
[  +17 ms] Found plugin cloud_firestore at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/cloud_firestore-0.13.5/
[   +1 ms] Found plugin cloud_firestore_web at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/cloud_firestore_web-0.1.1+2/
[   +2 ms] Found plugin firebase_auth at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.16.0/
[   +1 ms] Found plugin firebase_auth_web at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/firebase_auth_web-0.1.2/
[   +1 ms] Found plugin firebase_core at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/firebase_core-0.4.4+3/
[   +1 ms] Found plugin firebase_core_web at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/firebase_core_web-0.1.1+2/
[   +1 ms] Found plugin fluttertoast at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/fluttertoast-3.1.3/
[        ] Found plugin google_sign_in at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/google_sign_in-4.5.1/
[   +1 ms] Found plugin google_sign_in_web at
/Users/aseef/.pub-cache/hosted/pub.dartlang.org/google_sign_in_web-0.9.1+1/
[  +15 ms] Generating
/Users/aseef/Desktop/FlutterWebProjects/cigarette_track/android/app/src/main/jav
a/io/flutter/plugins/GeneratedPluginRegistrant.java
[  +45 ms] <- reset
[   +6 ms] /Users/aseef/SDKs/flutter/bin/cache/dart-sdk/bin/dart
/Users/aseef/SDKs/flutter/bin/cache/artifacts/engine/darwin-x64/frontend_server.
dart.snapshot --sdk-root /Users/aseef/SDKs/flutter/bin/cache/flutter_web_sdk/
--incremental --target=dartdevc --debugger-module-names
-Ddart.developer.causal_async_stacks=true --output-dill
/var/folders/1k/vg7lwkkd5_35y7s476gn723h0000gn/T/flutter_tools.XZ0Emw/flutter_to
ol.bramao/app.dill --libraries-spec
file:///Users/aseef/SDKs/flutter/bin/cache/flutter_web_sdk/libraries.json
--packages .packages -Ddart.vm.profile=false -Ddart.vm.product=false
--bytecode-options=source-positions,local-var-info,debugger-stops,instance-field
-initializers,keep-unreachable-code,avoid-closure-call-instructions
--enable-asserts --track-widget-creation --filesystem-root
/var/folders/1k/vg7lwkkd5_35y7s476gn723h0000gn/T/flutter_tools.XZ0Emw/flutter_to
ols.ZbC00I --filesystem-scheme org-dartlang-app --initialize-from-dill
build/cache.dill.track.dill --platform
file:///Users/aseef/SDKs/flutter/bin/cache/flutter_web_sdk/kernel/flutter_ddc_sd
k.dill
[   +7 ms] <- compile org-dartlang-app:/web_entrypoint.dart
[+17646 ms] Syncing files to device Chrome... (completed in 17,758ms, longer
than expected)
[   +1 ms] Synced 26.8MB.
[        ] <- accept
[ +488 ms] [CHROME]:
[   +1 ms] [CHROME]:DevTools listening on
ws://<IP_ADDRESS>:63840/devtools/browser/c7790d0b-100a-4453-a71c-e93c3112c7a9
[+3489 ms] Debug service listening on ws://<IP_ADDRESS>:63949/XkNhZFZv2X0=

[ +566 ms] Debug service listening on ws://<IP_ADDRESS>:63949/XkNhZFZv2X0=
[   +2 ms] Warning: Flutter's support for web development is not stable yet and
hasn't
[        ] been thoroughly tested in production environments.
[        ] For more information see https://flutter.dev/web
[        ] 🔥  To hot restart changes while running, press "r" or "R".
[   +1 ms] For a more detailed help message, press "h". To quit, press "q".
[  +82 ms] WARNING: found an existing <meta name="viewport"> tag. Flutter Web
uses its own
           viewport configuration for better compatibility with Flutter. This
tag will be
           replaced.

Analyzing web_test...
No issues found! (ran in 4.7s)

[✓] Flutter (Channel master, 1.19.0-2.0.pre.143, on Mac OS X 10.15.4 19E287,
    locale en-GB)
    • Flutter version 1.19.0-2.0.pre.143 at /Users/aseef/SDKs/flutter
    • Framework revision 9d58a87066 (2 days ago), 2020-05-22 22:37:01 -0700
    • Engine revision 9ce1e5c5c7
    • Dart version 2.9.0 (build 2.9.0-10.0.dev 7706afbcf5)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/aseef/Library/Android/sdk
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.4.1, Build version 11E503a
    • CocoaPods version 1.8.4

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 43.0.1
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build
      1.8.0_202-release-1483-b49-5587405)

[✓] VS Code (version 1.45.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.10.2

[✓] Connected device (2 available)
    • Web Server • web-server • web-javascript • Flutter Tools
    • Chrome     • chrome     • web-javascript • Google Chrome 81.0.4044.138

• No issues found!

FWIW downloadOffline isn't quite ready yet, but thanks for the bug report

FWIW downloadOffline isn't quite ready yet, but thanks for the bug report

Thanks for the update. 👍


[CH][Minor] Fix build due to Clickhouse Refactor

What changes were proposed in this pull request?
Fix build due to https://github.com/ClickHouse/ClickHouse/pull/62170, which avoids public dependency on CurrentThread.h  and hence cause our build failed.
We can avoid https://github.com/apache/incubator-gluten/pull/5289 upgrading clickhouse backend by this PR.
How was this patch tested?
Using existed UT

lgtm


Bool.succ, .pred methods explained (please review)

I first encountered the method "succ" today, and it was a method on Bool. At first I misunderstood it to mean "success", and wondered what type of failure or disaster "pred" stood for. Then I discovered that "succ" means "successor" and "pred" means "predecessor" and that they seem to totally make sense if we think of Bool in terms of it consisting of two possible enums.  So, that's what I tried to explain, but I would really like someone that feels more comfortable with this topic to please review my proposed changes (and please improve them if needed), before merging this pull request. (I could have committed directly, but I wanted someone to review this first.)

Looks good to me.

Thanks!

I thought that I wrote a comment… where did it go?
I liked everything except two things:

“In many languages” – is it true that many languages actually have a succ function? How many? Is it a good way to start a sentence? Probably not.
“to return the "next" enum” – “next enum” sounds a bit weird to me. Next enum value perhaps?

Thanks @AlexDaniel. See in https://github.com/perl6/doc/commit/1b63b98eb737ae2491dfc245b3eff9e6a9eb1bd9.


Add ELB Context to HttpApiV2Request

Serverless Java Container version: 1.9
Implementations: Micronaut
Framework version: Micronaut AWS master branch
Frontend service: HTTP API / ALB
Deployment method: SAM`
Scenario
Describe what you are trying to accomplish
Implement https://github.com/micronaut-projects/micronaut-aws/issues/1317
Expected behavior
Payload V2 working with both HTTP API and ALB
Actual behavior
Cannot differentiate HTTP API from ALB Request via requestContext
Steps to reproduce
N/A
Full log output
N/A

cc @msailes

Released as part of version 1.9.1.


Set minimum window size

Set a minimum window size so that manually resizing a window can't collapse it all the way, ala:

Most windowed Mac apps keep a small content area displayed at their smallest size. After the change:

Cool, this is a good addition, thanks!
In Document.swift:199 we declare a minimum size for new windows; I think it makes sense for us to use the same size in both places, so maybe we could declare a static minWindowSize (or minWindowWidth + minWindowHeight in Document and then use that both for new windows and for this setting?

Good point - I just simplified it by reusing the frame object to take its size for the min size instead.

Thanks again @paulsmith!


Add ESRI service to AWS staging

This PR pipes through the variables we need to enable ESRI in staging for AWS. All Esri vars in the server code are included here.
Issue: https://github.com/civiform/civiform/issues/4621
Corresponding PR to add these to our AWS staging config file: https://github.com/civiform/civiform-staging-deploy/pull/47

@gwendolyngoetz that's good to know. I was going to check in with you about that. I time boxed figuring out how to pipe arrays through the deploy system this morning and wasn't able to do it. I'm going to merge this to unblock some perf measurement stuff @dkatzz is working on and will make a new issue for the service area vars. I'll bring it up at Monday's meeting as well.


I get an error What should I do?

🐛 Bug

h$ python3 train.py   --dataset musdb
Using GPU: True
Using Torchaudio:  False
Traceback (most recent call last):
File "train.py", line 294, in
main()
File "train.py", line 158, in main
train_dataset, valid_dataset, args = data.load_datasets(parser, args)
File "/home/scss/DeepLearning/VocalEX/Separation/open-unmix-pytorch/open-unmix-pytorch/data.py", line 226, in load_datasets
**dataset_kwargs
File "/home/scss/DeepLearning/VocalEX/Separation/open-unmix-pytorch/open-unmix-pytorch/data.py", line 751, in init
*args, **kwargs
TypeError: init() got an unexpected keyword argument 'root'
To Reproduce
Steps to reproduce the behavior:
1.　Python3 train.py　--root (Datasets)

Expected behavior

Environment
Please add some information about your environment

PyTorch Version (e.g., 1.0.0):
OS (e.g., Linux):
torchaudio loader (y/n): N
Python version:
CUDA/cuDNN version: 440
Any other relevant information:

If unsure you can paste the output from the pytorch environment collection script
(or fill out the checklist below manually).
You can get that script and run it with:
wget https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py
# For security purposes, please check the contents of collect_env.py before running it.
python collect_env.py

Additional context

TypeError: init() got an unexpected keyword argument 'root'

looks like you have an old version of musdb installed. Can you try again with updating your requirements to the one we have in the environment files?

Thank you for your reply
MUSDB==0.3.0 but I get an error

please check the environment files:
https://github.com/sigsep/open-unmix-pytorch/blob/ba8e9f1e968cf4725be02009dacd6e2b97b44a7f/environment-cpu-linux.yml#L19

I downloaded it from the official website.
It was a new update
Sincerest apologies
Worked

manually installing requirements is very risky. Please follow the installation instruction in the readme.


build of version 1.7.1 fails

hello,
I'm unable to perform Drogon installattion:
git clone https://github.com/an-tao/drogon - works
cd drogon - works
but  git submodule update --init
failed with  :
fatal: reference is not a tree: 4ec01750b0e8a77c1e118e99dbbe4da38df1ffbd
Unable to checkout '4ec01750b0e8a77c1e118e99dbbe4da38df1ffbd' in submodule path 'trantor'
please advise.
Omer.

Weird. I can run the exact commands without problem. Are you cloning into a empty directoy? Which OS are you using? And please try deleting the entire drogon directory and try again.
❯ git clone https://github.com/an-tao/drogon
Cloning into 'drogon'...
remote: Enumerating objects: 13861, done.
remote: Counting objects: 100% (1118/1118), done.
remote: Compressing objects: 100% (658/658), done.
remote: Total 13861 (delta 563), reused 805 (delta 382), pack-reused 12743
Receiving objects: 100% (13861/13861), 4.14 MiB | 2.05 MiB/s, done.
Resolving deltas: 100% (9304/9304), done.
❯ cd drogon
❯ git submodule update --init
Submodule 'trantor' (https://github.com/an-tao/trantor.git) registered for path 'trantor'
Cloning into '/tmp/drogon/trantor'...
remote: Enumerating objects: 5, done.
remote: Counting objects: 100% (5/5), done.
remote: Compressing objects: 100% (2/2), done.
remote: Total 5 (delta 3), reused 5 (delta 3), pack-reused 0
Unpacking objects: 100% (5/5), 531 bytes | 531.00 KiB/s, done.
From https://github.com/an-tao/trantor
 * branch            4ec01750b0e8a77c1e118e99dbbe4da38df1ffbd -> FETCH_HEAD
Submodule path 'trantor': checked out '4ec01750b0e8a77c1e118e99dbbe4da38df1ffbd'

retried, failed again.
...$ git clone https://github.com/an-tao/drogon
Cloning into 'drogon'...
remote: Enumerating objects: 13861, done.
remote: Counting objects: 100% (1118/1118), done.
remote: Compressing objects: 100% (658/658), done.
remote: Total 13861 (delta 563), reused 805 (delta 382), pack-reused 12743
Receiving objects: 100% (13861/13861), 4.14 MiB | 95.00 KiB/s, done.
Resolving deltas: 100% (9304/9304), done.
Checking connectivity... done.
...$ cd drogon/
..../drogon$  git submodule update --init
Submodule 'trantor' (https://github.com/an-tao/trantor.git) registered for path 'trantor'
Cloning into 'trantor'...
remote: Enumerating objects: 3415, done.
remote: Counting objects: 100% (235/235), done.
remote: Compressing objects: 100% (134/134), done.
remote: Total 3415 (delta 127), reused 168 (delta 98), pack-reused 3180
Receiving objects: 100% (3415/3415), 834.83 KiB | 166.00 KiB/s, done.
Resolving deltas: 100% (2340/2340), done.
Checking connectivity... done.
fatal: reference is not a tree: 4ec01750b0e8a77c1e118e99dbbe4da38df1ffbd
Unable to checkout '4ec01750b0e8a77c1e118e99dbbe4da38df1ffbd' in submodule path 'trantor'
running ubnut 16.04
git version 2.7.4
:-)
Omer.

i also tried following trantor's installation instructions to "manually" install it under drogon/trantor. trantors build worked,
but drogon's cmake failed with "You have called ADD_LIBRARY for library trantor without any source files."
:-)
Omer.

Do you mean the following failed?
git clone https://github.com/an-tao/drogon
cd drogon
git clone https://github.com/an-tao/trantor
mkdir build
cd build
cmake ..
make

I've tried
git clone https://github.com/an-tao/drogon
cd drogon
rm -r trantor
git clone https://github.com/an-tao/trantor
cd trantor
cmake -Bbuild -H.
cd build
make -j
cd ..
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release .. failed with  "You have called ADD_LIBRARY for library trantor without any source files."

I've contacted Github support asking what's going on, Likely their CDN screwed up and have to wail until the cache expires.
Please try:
git clone https://github.com/an-tao/drogon
cd drogon
rm -r trantor
git clone https://github.com/an-tao/trantor
mkdir build
cd build
cmake ..
make

tried the latest suggestion , hasn't solved the problem.
still getting
got :
You have called ADD_LIBRARY for library drogon without any source files. This typically indicates a problem with your CMakeLists.txt file
.
.
.
You have called ADD_LIBRARY for library trantor without any source files. This typically indicates a problem with your CMakeLists.txt file
.
.
.
CMake Error: The source directory "/home/omerbrandis/ffrobotics/drogon/cmake/tests/check_has_std_filesystem_path.cc" is a file, not a directory.
Specify --help for usage, or press the help button on the CMake GUI.
CMake Error: Internal CMake error, TryCompile configure of cmake failed
.
.
.
-- Configuring incomplete, errors occurred!
Omer.

try to remove your drogon clone first.
assuming you're on $HOME
sudo rm -rf drogon

then,
git clone https://github.com/drogonframework/drogon
cd drogon
git submodule update --init
mkdir build && cd build
sudo cmake ..
sudo make && sudo make install

then try
drogon_ctl -v

try to remove your drogon clone first.
assuming you're on $HOME
sudo rm -rf drogon

then,
git clone https://github.com/drogonframework/drogon
cd drogon
git submodule update --init
mkdir build && cd build
sudo cmake ..
sudo make && sudo make install

then try
drogon_ctl -v

I'm not sure with Ubuntu 16 anyway

I just tested,
Ubuntu 18.04 also unable to build with sudo cmake -DCMAKE_BUILD_TYPE=Release ..
But Debian 10 (buster) & Ubuntu 20.04 (focal) are able to build with Release type.

Surprisingly, my windows 10 are unable to use Debug type, but able to build with Release type (ninja build)

#993 Should fix the std::filesystem error on Ubuntu 18.04.


Update Deprecation Warning on Service Composition with ||

Location
@deprecated("Import `cats.syntax.semigroup._` and use `service1 |+| service2` instead", "0.16")

is now outdated.
Should either be removed or replaced with something like
"Import `cats.implicits._` and `org.http4s.implicits._` and use `service1 <+> service2` instead. Ensure partial unification is enabled.", "0.16"

Open to discussion.

I think it doesn't hurt to keep it deprecated.  The message looks good, though I might use the actual flag name. -Ypartial-unification, I think it is.

@ChristopherDavenport I can pick this one up.

@ChristopherDavenport Can this issue be closed? Not sure what the requirements for a closed issue are.

Sorry yes. Thanks again!


Carousel component does not show its captions in smaller than md size (768px)

Windows 10 (Chrome Version 91.0.4472.77 (Official Build) (64-bit))
Android 10, MIUI Global 12.0.8 (Chrome Version 91.0.4472.88)
iOS iPhone 7 (Safari)
Carousel component does not show its captions in smaller than md size (768px)
You can check it here:
https://getbootstrap.com/docs/5.0/components/carousel

Was rised by mistake


Add getting of multiple currencies

Updates the AccountState and json-rpc interfaces to handle multiple currencies.

@bors-libra r=phoenix-antigravity

:pushpin: Commit 7f55ef6 has been approved by phoenix-antigravity

:hourglass: Testing commit 7f55ef661bf197c14110e8d17bde3810ff2e2ba1 with merge 2bdaf896c10b5afa569264443f32e01f78447c13...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: phoenix-antigravity
Pushing 2bdaf896c10b5afa569264443f32e01f78447c13 to master...


Ability to display Github issues in Jira

Basically, the same list as it's currently exist for PRs, branches and commits. But for issues.

I can make a PR, if this feature has chances to be accepted.

Our commits were not showing in Jira from the past day or so.

Has this been resolved?

Hi @Leksat. I'm from a team at Atlassian that is currently in the process of migrating the ownership over to us from GitHub. As a part of this, we're currently going through the backlog of issues and prs to see what can still be addressed and what should be closed.
I've flagged this with the 'to triage' label so my team can discuss. We'll keep you posted on the status of this.

Hey @Leksat. Just need some clarification: are you proposing, if there is a Jira issue key e.g. ARC-123 referenced in a GitHub issue (title &/or body?) that a link to the GitHub issue/s would be visible in the Jira dev panel?
So here we'd see 'X GitHub issues'

And here we'd see a 'GitHub issues' tab?

The main problem I see with this is that the Jira dev panel is a component that serves multiple providers - not just GitHub - and is essentially 'dumb' in the respect that it just pulls in data from each provider and renders it. There's very little logic and there is no conditional logic to say 'if this provider, add this extra link/tab'. I can run this by the team that owns the dev panel but my guess is they won't be able to implement this request as it breaks the existing patterns in that component.

@rachellerathbone yes, exactly!
Something like this:

We really want this feature because developers love Github and PMs/clients love Jira. If it's implemented, developers can create multiple issues for Jira tickets and there discuss technical details using all the cool Github features. While Jira will be used for communicating with client, planning, billing, etc.
As for the implementation issues, maybe it's possible to change the logic a bit?
- if this provider, add this extra link/tab
+ add this link/tab if this provider supports it

(Just look at this beauty ^ Can I embed a diff like this in Jira? No! Can I drag'n'drop an image to a comment in Jira? Well, maybe, but Github does it in much nicer way. Please let developers use Github 🙏 😅 )

Hi @Leksat. I was able to chat with some folks from various Jira teams and found out that there was an "Other links" tab in the dev detail dialog that was introduced last year. Current problem is, are all hardcoded, but should be easy to extend. Just need to wait now for these to be triaged by our PM. I'll keep you posted.

Any news on that? I basically want to use JIRA to manage my GitHub issues. Now seems like I would need to use Zapier to import them into JIRA, and close them on JIRA when closed on GitHub if I don't want people to add JIRA tags.

What's the current state of this? Given the current support and documentation of Github issues synchronization with Jira issues, and given that this has been requested multiple times so far, it's taking a long time to update.
Any news regarding Github issues sync are much appreciated.

With Jira being a product focused tool & Github issues being far more developer friendly. A feature like this is sorely needed, so devs can track work where it works best for them, and where they have useful features & configuration for them (Github) and product knows, generally, what's happening (Jira)


shpool list hangs

I'm moving an issue filed on the google internal bug tracker here. The problem seems to be that shpool list can sometimes hang. Reproduction steps are unknown, but we do have a log file (attached).
shpool.log

I think the relevant bit is
May 13 10:17:51 tower.lon.corp.google.com shpool[2894224]: 2024-05-13T09:17:51.286942Z  INFO ThreadId(01) run:serve: socket got a new connection
May 13 10:17:51 tower.lon.corp.google.com shpool[2894224]: 2024-05-13T09:17:51.287057Z  INFO ThreadId(371) handle_conn{cid=212}: new
May 13 10:17:51 tower.lon.corp.google.com shpool[2894224]: 2024-05-13T09:17:51.287077Z  INFO ThreadId(371) handle_conn{cid=212}:parse_connect_header: new
May 13 10:17:51 tower.lon.corp.google.com shpool[2894224]: 2024-05-13T09:17:51.287108Z  INFO ThreadId(371) handle_conn{cid=212}:parse_connect_header: close time.busy=24.8µs time.idle=5.71µs
May 13 10:17:51 tower.lon.corp.google.com shpool[2894224]: 2024-05-13T09:17:51.287143Z  INFO ThreadId(371) handle_conn{cid=212}:handle_session_message: new
May 13 10:17:51 tower.lon.corp.google.com shpool[2894224]: 2024-05-13T09:17:51.393112Z  INFO ThreadId(01) run:serve: socket got a new connection
May 13 10:17:51 tower.lon.corp.google.com shpool[2894224]: 2024-05-13T09:17:51.393218Z  INFO ThreadId(372) handle_conn{cid=213}: new
May 13 10:17:51 tower.lon.corp.google.com shpool[2894224]: 2024-05-13T09:17:51.393241Z  INFO ThreadId(372) handle_conn{cid=213}:parse_connect_header: new
May 13 10:17:51 tower.lon.corp.google.com shpool[2894224]: 2024-05-13T09:17:51.393254Z  INFO ThreadId(372) handle_conn{cid=213}:parse_connect_header: close time.busy=8.01µs time.idle=5.38µs
May 13 10:17:51 tower.lon.corp.google.com shpool[2894224]: 2024-05-13T09:17:51.393289Z  INFO ThreadId(372) handle_conn{cid=213}:handle_list: new

All the previous shpool list commands completed as normal, and from this point on in the log they start hanging. shpool list needs to take a lock on the global sessions table, and there are some other handlers which also grab that lock. One of them is the handle_session_message handler, which is an internal plumbing handler that handles out-of-band detach as well as resize messages.
Both of those session messages are handled by talking to the shell->client reader thread via some crossbeam channels, so likely what is happening is that we are taking the lock on the shells table then blocking on a changle send or receive with that lock held. This will pretty much entirely lock up the daemon.


Common Attributed Strings Attrs in Styles

We should have functions that take a UIColor for common attributes that we have all over the place  so instead of calling:
attributes: [
  .font: Styles.Fonts.body,
  .foregroundColor: Styles.Colors.Gray.dark.color
]

We can call:
attributes: .hawkBody(color: Styles.Colors.Gray.dark.color)

or:
attributes: Styles.Attributes.body(color: Styles.Colors.Gray.dark.color)

@heshamsalman I would like to tackle this one. Which one of the two proposed solutions should I go with?

@spsjvc the second solution is more consistent with the rest of the project, despite how minimal the first one looks. so i say probably the second :+1:


hash: allow Hash to implement encoding.BinaryMarshaler, encoding.BinaryUnmarshaler

There are some use cases that aren't met by current hashing functions

Serialize state of a partial byte stream processing for later work; recalculating the hash from the beginning is inefficient and, in our case, infeasible due to the size of the data and legacy compatibility requirements that inhibit use of, say, a Merkle tree.
Sharing calculation of common prefix hashes; this only requires in-memory copying rather than serialization.
Conditional append based on hash matches, which is a corollary of the previous.

Previous thread on golang-dev.
In my specific case, I'm looking for MD5 [de]serialization.
/cc @jlhawn

Seems like we could make the concrete types implement https://golang.org/pkg/encoding/#BinaryMarshaler and https://golang.org/pkg/encoding/#BinaryUnmarshaler at least.
We can't change the signature of e.g. https://golang.org/pkg/crypto/md5/#New but we could document in an Example that you can type-assert that the returned hash.Hash is also an encoding.BinaryUnmarshaler etc.

Any objections to hashes implementing BinaryMarshaler and BinaryUnmarshaler? Will leave this open for a week.

Proposal accepted. CLs welcome for the Go 1.10 cycle for

Updating hash.Hash docs to document the convention.
Updating hash/* and crypto/* hashes to implement it.


Uninitialized variable and parameter

I wrote a proposal of uninitialized variable and parameter. The uninitialized variable is a variable that does not have the data array. It can be used to represent an uninitialized parameter, which appears when using parameter shape placeholder (i.e., the weight matrix with unknown input size that will be inferred at the first iteration). It makes the handling of uninitialized parameters as easy as handling initialized parameters.
The details are explained in the following design document: https://docs.google.com/document/d/1-3fG8zs7jq3kM9jie1_No6beWn2jHtX1WqXWeXlhpCU/edit?usp=sharing. I don't think it breaks the compatibility, but it changes the way to implement parameter shape placeholder support, so it would be better to introduce it in v2.

Solved by #2072


Create a Label component that is always in editable mode

Close #99.

As far as I understand, input event is supported in all browsers: https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/input_event.


[iomgr] Second take for iomgr shutdown

Keep the event engine choice stable, but allow an init/shutdown for engines that desire it.
We'll use this internally to cover some existing use cases.

Removed approval to prevent submission while we're discussing the bm_cq test removal.


Mix release closure size

Motivation for this change
@dlesl started the work of removing the reference to erlang in rebarRelx resulting closure in https://github.com/NixOS/nixpkgs/pull/124779
This PR aims at starting the work for mix-release. @NobbZ you noticed in the initial PR that the resulting closure built by mix-release contained reference to erlang.
This PR does the following.

Removing the setup hook from the generic builder of erlang. It seems it has no effect. Also from a reference found by @dlesl , it seems not needed https://erlang.org/doc/man/code.html
Switches some dependencies from buildInputs to nativeBuildInputs. This is more a semantic difference, but just to make the intent clearer to future contributors.
Remove reference to rebar into mix release. There is likely no need anymore for the old rebar.
Remove the explicit reference of erlang into closure built by mix-release.

Please note however that the resulting closure built by mix-release still reference erlang somehow, even though I can't find any explicit reference by grepping. This is still a work in progress.
Since removing the erlang setup hook might be impactful, I'm curious to have people test this and give feedback
@NixOS/beam
@ydlr @petabyteboy @cw789 you might be interested in this as well.
Things done

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

[ ] NixOS
[X] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

TIL nix why-depends
I was browsing randomly through the doc and discovered this.
Needless to say it works!
❯ nix why-depends ./result ../../nixpkgs#erlang
/nix/store/l0339q9yqnqya6al8ay0b3bmg9m3rmvv-union-0.0.1
└───lib/bcrypt_elixir-2.3.0/priv/bcrypt_nif.so.dSYM/Contents/Resources/DWARF/bcrypt_nif.so: ….............
    → /nix/store/k5vq393x6c0ykfwamwcy0jhlf6iw9d8w-erlang-24.0.2

Nice find! It might just be debug info. I think we might need to modify buildRebar3 and buildMix to strip ELF/DWARF binaries in /priv, because I don't think the default builder looks there, see stripDebugList. It could also be a linux/darwin difference, I'll test some NIF-containing derivations on linux.

I was able to reproduce this with buildRebar3. Since the output goes to $out/lib which is already in stripDebugList, all I had to do was remove the line dontStrip = true

Would you be able to make the dontStrip change to buildRebar3 as part of this PR (since packages built by it might end up as dependencies of mixRelease derivations), and I can make a separate PR to fix rebar3Relx (since its output goes to rel, I think we will need to override stripDebugList)?

Thanks for the find on stripping.
From what I understood stripping has no effect on beam files. That's why originally dontStrip was set to true.
If I understand well, for buildMix it will be useful for dependencies with NIFs so I added stripDebugList = [ "priv" ];
with the example of bcrypt that has stuff to be stripped in priv
No problem in removing the dontStrip for buildRebar3 in this PR.

Thanks! Since buildMix also copies everything into $out/lib/erlang/lib you probably don't need to set stripDebugList?

@dlesl added the commit that references stripping. Let me know if you think it's a little too much to add a comment and leave the default.
Unless I'm wrong, even after being stripped, the reference to erlang remains. So I still need to do some grep magic to remove it in the postFix hook of mix-release. Since I think you only know at that time if ERTS is present or not. So probably not possible to do it in a buildMix hook.

Also just to make sure, this is how I tested that the bcrypt.so binary was stripped
objdump --syms bcrypt_nif.so | grep debug
just in case it wasn't the right way.

I think we should try to strip the debug info whether or not ERTS is included in the release, since stripping binaries is the default nix behaviour and leaving it might cause other issues.
Regarding the reference to erlang remaining, it might be a difference between darwin and linux? IMHO it's good enough if it works correctly on linux (just guessing that most people deploy their releases on linux)

I think we should try to strip the debug info whether or not ERTS is included in the release, since stripping binaries is the default nix behaviour and leaving it might cause other issues.

I agree, did I mistakenly include some conditional in there? Or are you talking about stripping FOD deps?
including the stripping in buildMix and buildRebar3 should be enough right? Let me know if I missed something.

Regarding the reference to erlang remaining, it might be a difference between darwin and linux? IMHO it's good enough if it works correctly on linux (just guessing that most people deploy their releases on linux)

I don't think it's a darwin specific thing unfortunately. I've pushed a fix.
Here is the result
After
❯ nix path-info -rsSh ./result
/nix/store/4salp61q5ic2zw6s22ii0j8d7dxg1vfx-union-0.0.1                   38.9M  117.9M
/nix/store/4salp61q5ic2zw6s22ii0j8d7dxg1vfx-union-0.0.1                   38.9M  117.9M
/nix/store/64d69jqbz4s8ziqbpam41sd70w338ars-libcxx-7.1.0                   2.4M    2.9M
/nix/store/6q1rhqvyzxb3j5pb1h4qxsa0hh1i45wv-libcxxabi-7.1.0              533.3K  533.3K
/nix/store/892bqs4h7gck4qzysnj6s8niy9jk9qbn-libkrb5-1.18                   1.6M   19.8M
/nix/store/8f4wp5sdl08wrnj3ajsqrjbv7fw5lgv7-zlib-1.2.11                  102.2K  102.2K
/nix/store/96j2ai9h4f5kaqcnp9kvgbp2srr79xhx-openssl-1.1.1k                 3.1M   75.9M
/nix/store/az26q1v080bqfwhn8snapbscxgdw80qn-nghttp2-1.43.0-lib           167.4K  167.4K
/nix/store/cykikdmpsksd35xs8ppds7iwqa2rllzl-curl-7.76.1                  560.8K   25.8M
/nix/store/d4spin3lyclblj5lji2ih4axg19dfmfw-libssh2-1.9.0                233.5K    3.4M
/nix/store/f695vk4n50d3i528ldnf9rvnkciknm5y-libxml2-2.9.12                 1.4M    1.5M
/nix/store/f7f3gz636cqxkav7cy1nlldkwv2b22n1-swift-corefoundation           3.3M   72.8M
/nix/store/kdydav4gqzd91qlpprnjascbs5hs8qmg-ncurses-6.2                    3.2M    3.2M
/nix/store/npjd5jnk4chfz39lv0vm24f029ry6h6r-openssl-1.1.1k                 3.1M    3.1M
/nix/store/pcjan45rssdn01cxx3sjg70avjg6c3ni-bash-4.4-p23                 997.6K  997.6K
/nix/store/qhz9xpqbj6xvwmzxwspdixpr4px2l22j-ICU-66108                     39.4M   42.2M
/nix/store/riasnjlb9bb3d3gciv2aaz1ypxrg7hp3-brotli-1.0.9-lib               1.9M    1.9M
/nix/store/rvqdp9l0ncp69mcxfpf0vfmrafh8zqa8-Libsystem-1238.60.2           17.2M   17.2M

@dlesl you were right about stripping things from buildMix, no need to override the stripDebug flag
It made me realize that the mix-release also needs to be stripped. I think that is what you were referring to earlier.
I'm testing this at the moment.

I changed the fixupPhase to a postFixup since there is no use overriding anymore.
I think this PR is good to merge.
Will leave one more day open in case anybody wants to comment or test.


Ridge Racer 3D

Game boots. Intro movie didn't play, and it crashed on first boot when setting up profile. Otherwise, it seems pretty playable. Graphical glitches however... (glitched confetti, flickering screen, missing nitrous bursts from exhausts)

The crash is I think due to trying to connect to wifi, I remember the intro asking you if you want to connect to the interwebs

The crash is I think due to trying to connect to wifi, I remember the intro asking you if you want to connect to the interwebs

The same thing also happens on NFS The Run.


Add typehints

...and fix remove_action parameters

These were also discovered by @phpstan

Remove.
I'm very sad that you are not (yet) a fan of static analysis.

Thanks!

You're welcome.