[Wave8] [Simplified Collect] [Workflows] Create Payment page

We've recently merged the main workflows page.
The task here is to create the Payment page present under the main worfklows page.
It will appear when we click on the > icon under the Connect bank account menu item:

Expected mockups below
No VBBA flow

VBBA flow

Technical details can be found here.

@ishpaul777 would you be able to work on the implementation for this issue since you have access to the design doc?

would you be able to work on the implementation for this issue since you have access to the design doc

Sure 😃 i'd love to work on it

Perfect! Thank you. Assigning it to you

@ishpaul777 the reimbursementAccount key should have these details, I think we can use that to build the bank account name as shown in the image

This is the object I see when I have a bank account added. Maybe your account doesn't have a bank account properly set up:

we’ll check for plaidData Onyx key details
this seems wrong since that key is temporary only when we're in the process of connecting with Plaid.

That should navigate to ROUTES.BANK_ACCOUNT_WITH_STEP_TO_OPEN, which would show the EnableBankAccount page

@ishpaul777 how's it going with this issue? Do you have a branch or draft PR up yet?

Draft PR is up, @ishpaul777 what's your ETA on marking it ready for review?

Thanks for the update, @ishpaul777. @lakchote, can you help here?

what's your ETA on marking it ready for review?

I have completed the most part, a few blocker i have:

The SetWorkspacePayer is throwing a 404 error from server, so for now i tried setWorkspaceReimbursement command to set workspace admin as reimburserEmail which seems to working fine but i'll change it once that command is working

There is no command for changing policy.reimbursementChoice to toggle on/off the option, and i dont find a way to have the VBA owner set as default workspace payer.

For 1., it should be the command that exists is SetWorkspaceReimbursement and not SetWorkspacePayer.
If we want to use the latter, we should change the alias name in Web-E. cc @luacmartins
For 2.,  to toggle on/off the option, you need to call Policy_setReimbursementFromChoice  with parameters policyID, and reimbursementChoice (set it as reimburseManual )
To have the VBBA owner set as default workspace payer, call SetWorkspaceReimbursement with the VBBA owner's email
For 3., you can maybe add a param to ReimbursementAccountPage so that on redirect from the Workflows screen, it knows it's from Workflows and as such doesn't clear reimbursement data

To have the VBBA owner set as default workspace payer, call SetWorkspaceReimbursement with the VBBA owner's email

Actually achData dont dont have a VBA owner email property :( #37197 (comment), so we dont have a way to know the owner email

I'm going to look into it. I'll report back

@lakchote is the command Policy_setReimbursementFromChoice with Policy_ post fix, asking because i dont see this pattern followed anywhere ?

It's Policy_setReimbursementFromChoice with setReimbursementFromChoice in lowercase.
It's an old command that's why it didn't follow the new and proper convention naming.
We can create an alias for it later.
Could you please use it and report back if you can make it work?

Its working 👍, one more thing for clarity, when option is reimburseManual option is on and when its off is it reimburseYes or reimburseNo

When it's on it's reimburseYes, when it's off it'sreimburseManual

@ishpaul777 I've found an ISO way of getting the reimburser email if it's set or default to the owner of the VBBA account.
Will put up a PR for @luacmartins to review.

@ishpaul777 I've found an ISO way of getting the reimburser email if it's set or default to the owner of the VBBA account.
Will put up a PR for @luacmartins to review.

PR ready for review too @luacmartins
Here's a quick link to the PRs:
Alias for API command
Reimburser email for VBBA

Update:

Alias PR is merged. You can keep using Policy_setReimbursementFromChoice for testing for now until the new command SetReimbursementFromChoice is deployed.
For the reimburser email from VBBA, we should be using the new reimbursementAccount<policyID> key, with the policyID appended to it. It seems like we don't load this information when opening the Workflows page, so we need a command to do that @lakchote.

@ishpaul777 we'll have to create an OpenPolicyWorkflowsPage API command that should be called when the user opens the Workflows page to load this data. I wouldn't block your PR on it though

@trjExpensify Could you assign me here as I'll be reviewing the PR as C+? Thanks! :pray:

Done

@ishpaul777 we'll have to create an OpenPolicyWorkflowsPage API command that should be called when the user opens the Workflows page to load this data. I wouldn't block your PR on it though

PR should be merged today

Alright, alright...

$500 to @jjcoffee for the C+ review
$500 to @ishpaul777 for the fix

We'll take care of the regression tests for the simplified collect project. :)
Let me know if that's correct and I'll get these paid out.

@trjExpensify LGTM!

Perfect. Offers sent!

@trjExpensify Accepted, thanks!

@jjcoffee paid you.

@ishpaul777 we're still waiting on you to accept the offer.

Paid! :)


[Investigation] What happens when the same entity is deployed in different servers?

Content servers don't require any type of consensus. Each deployment is shared and validated by all servers, and there is no concept similar to "double spending". However, there is a possibility that the same entity could be deployed in two or more different servers at the same time.
This should have no effect other than having the same entity with different originTimestamp and originServerUrl, but we need to make sure that is the case.

The concepts of originTimestamp and originServerUrl do not longer exist.


Logcat shows unexplained error (copyAndPost)

I'm using a DecoratedBarcodeView and continousDecode.
The library send the following error to the app's logcat, on each frame:
E/Camera-JNI: copyAndPost: off=0, size=3110400 msg=10
But everything works correctly. Can this error message be disabled/hidden?
Thank you!

This seems like an issue with the camera drivers on the device, and you will likely see it with other apps using the camera as well. Nothing we can do from the library side.


chore: enable useUnknownInCatchVariables TypeScript option

This enables the useUnknownInCatchVariables TypeScript option, bringing a little more type safety.
I fixed a few violations, in part by moving isRecord to its own file with tests.

Looks like the isRecord() implementation can be completely removed now

It looks like it's still needed but only by one place now, so I've moved it back in aaf0af5604bc2e43b75c34adddcb2d75d612d031.


Syncing of user data, stores, and permissions between Hubs

There will be many implementations of Hubs written in different languages and backed by different data storage systems. An identity may be leveraging many different Hub implementations across different devices and systems - for example: a Java/Swift implementation on a phone, a Node implementation located in a cloud, and a .NET implementation on their gaming/media device. All of these Hubs need to sync the same identity data and handle inbound requests in a way that produces a single, consistent surface area for the identity(s) they manage.
How best to do that is an open question, which I would like to pose to the members of this group. I look forward to exploring solutions with you.

Maybe not exactly the most thorough addition to the conversation, but I've used https://www.npmjs.com/package/ipfs-log with success for IPFS.

I think this is discussed here: https://hackmd.io/OInEIRLxQY2s48tze0E7IQ#
@csuwildcat let me know if you think we should close this issue.


Provide java.version in java toolchains' metadata

Fixes #17085

@bot-gradle test QF

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

@bot-gradle test QF

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

@bot-gradle test and merge

Your PR is queued because #17077 is being built.

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

Pre-tested commit build failed.

@bot-gradle test and merge

Your PR is queued because #15979 is being built.

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

Pre-tested commit build failed.

@bot-gradle test and merge

Your PR is queued because #15979 is being built.

Your PR is queued because #15979 is being built.

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

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

Pre-tested commit build failed.

@bot-gradle test and merge

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


How to boost performance speed on browser?

I see this below video is has very fast detect and i see that use faceapi.js how to optimize like this?
link : https://www.youtube.com/shorts/rQL5faV9-rw

This code is in python

Areyou suggesting to use python rather than javascript? Are the same libraries used?


redis: failed to set/get cache when making concurrent requests

I got the following error when I have multiple requests going out and try to cache their reponses:
redigo: unexpected response line (possible server error or unsupported concurrent read by application)
My understanding is that redis.Conn doesn't support concurrency for Do(). I suggest to use Pool instead of Conn inside the cache struct.

/cc @ghbutton who added the redis backend in PR #55 (for issue #54).


Update IG examples with new valueCode for corrected messages

Correct error related to activity - the organization is a who

error corrected and pull request created


Revert pack trimming introduced by #82084

Partially reverts #82084.
Fixes #89825.
This reverts the trimming of what was erroneously considered non-main packs in #82084, where files like project.binary, the project icon and the project splash image were omitted from the pack. These will now always be exported, like they were prior to #82084.
These changes will instead be incorporated into #89928 as part of the ability to opt in to this type of trimming.

Thanks!


org.apache.dubbo.rpc.RpcException Invoke remote method timeout. during startup.

[*] I have searched the issues of this repository and believe that this is not a duplicate.
[*] I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.7
Operating System version: CentOS 7.3.1611
Java version: 1.8

Here is the dubbo consumer configuration:
@DubboReference(version = "1.0.0", check = false, timeout = 1000, retries = 0)
the web services qps is 15
the p99 avg of the dubbo provider is about 40ms
Steps to reproduce this issue
We have springboot web service, it contains a dubbo consumer to call remote dubbo service.
Now we have a problem during the springboot web service startup.
During the web service startup, the dubbo consumer call remote dubbo service timeout. it lasts no more than 2 seconds. After that, no more timeout.
It happens everytime when we deploy the springboot web services.
Pls. provide [GitHub address] to reproduce this issue.
Expected Result
What do you expected from the above steps？
No dubbo consumer timeout during web services startup.
Actual Result
What actually happens?
There are timeout.
If there is an exception, please attach the exception trace:
Just put your stack trace here!

org.apache.dubbo.rpc.RpcException: Failed to invoke the method xxxx in the service xxxxService. Tried 1 times of the providers [xxxx] (1/40) from the registry xxxxx:xxxx on the consumer xxxx using the dubbo version 2.7.7. Last error is: Invoke remote method timeout. method: xxxx, provider: dubbo://xxxx/hxxxx?anyhost=true&application=xxxxx&check=false&delay=5000&deprecated=false&dubbo=2.0.2&dynamic=true&generic=false&init=false&interface=xxxxx&methods=xxxxx,xxxxx&pid=122&qos.enable=false&register.ip=xxxxx&release=2.7.7&remote.application=xxxxx&retries=0&revision=0.0.8&side=consumer&sticky=false&timeout=1000&timestamp=1608792429242&version=1.0.0, cause: org.apache.dubbo.remoting.TimeoutException: Sending request timeout in client-side by scan timer. start time: 2021-01-12 16:48:27.034, end time: 2021-01-12 16:48:28.638, elapsed: 1604 ms, timeout: 1000 ms

Have you try to increase the timeout period for this consumer

Have you try to increase the timeout period for this consumer

Have you try to increase the timeout period for this consumer

Have tried, less timeout, but the latency will increase.
But it only happened during the startup. Is there a way to warmup the consumer?

Have you try to increase the timeout period for this consumer

Have tried, less timeout, but the latency will increase.
But it only happened during the startup. Is there a way to warmup the consumer?

Have you try to increase the timeout period for this consumer

Have tried, less timeout, but the latency will increase.
But it only happened during the startup. Is there a way to warmup the consumer?

See if this meets your needs   http://dubbo.apache.org/docs/v2.7/user/examples/async-call/

Have you try to increase the timeout period for this consumer

Have tried, less timeout, but the latency will increase.
But it only happened during the startup. Is there a way to warmup the consumer?

See if this meets your needs   http://dubbo.apache.org/docs/v2.7/user/examples/async-call/

这个应该是 dubbo provider 延迟暴露了，把 provider 不延迟暴露试下。

这个应该是 dubbo provider 延迟暴露了，把 provider 不延迟暴露试下。

这个应该是 dubbo provider 延迟暴露了，把 provider 不延迟暴露试下。

这个应该是 dubbo provider 延迟暴露了，把 provider 不延迟暴露试下。

这个应该是 dubbo provider 延迟暴露了，把 provider 不延迟暴露试下。

provider没有重新启动，是我们的consumer所在的web 服务重启过程中的问题。

这个应该是 dubbo provider 延迟暴露了，把 provider 不延迟暴露试下。

provider没有重新启动，是我们的consumer所在的web 服务重启过程中的问题。

能否提供哦一个 demo？

能否提供哦一个 demo？

可以吧 check = false  改成 check = true 试试，在 check = true  的情况下，会先创建建立TCP 连接，并执行类似 ping的操作，检查通讯是否可用。consumer 在启动的时候，第一次 RPC 调用 确实耗时会比较多。

可以吧 check = false  改成 check = true 试试，在 check = true  的情况下，会先创建建立TCP 连接，并执行类似 ping的操作，检查通讯是否可用。consumer 在启动的时候，第一次 RPC 调用 确实耗时会比较多。

可以吧 check = false 改成 check = true 试试，在 check = true 的情况下，会先创建建立TCP 连接，并执行类似 ping的操作，检查服务是否可用。consumer 在启动的时候，第一次 RPC 调用 确实耗时会比较多（因为要先建立TCP链接）。

谢谢建议，我们试下。

可以吧 check = false 改成 check = true 试试，在 check = true 的情况下，会先创建建立TCP 连接，并执行类似 ping的操作，检查服务是否可用。consumer 在启动的时候，第一次 RPC 调用 确实耗时会比较多（因为要先建立TCP链接）。

谢谢建议，我们试下。


line-wrap CONTRIBUTING.rst

Current coverage is 96.87%

Branch #90 has no coverage reports uploaded yet.

Powered by Codecov. Updated on successful CI builds.

❤


Update UI design component part of the developer guide

Previous DG was empty. This PR will update UI component of the design section of the DG.
Includes some small refactoring of the MainWindow code.

Address #117


chore: Upgrade to node 20

Description of changes
Node 18 is out of active support and current actions are encouraged to upgrade away.
How has this been tested?

Created node20 branch which points all actions to @node20 of the actions package.
Created test branches on consuming packages to validate dry-run and release targets still work as expected

components draft PR against branch

build job
dry-run

components release job

Build Job log

Issue #, if available:
AWSUI-59859
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Rolled these changes into https://github.com/cloudscape-design/actions/pull/55


Added a section for adding a slash to requests for /wp-admin.

Seems legit!
Could we add a quick test for ensuring /wp-admin is a 200?

@bshaffer Thanks, added a test for that, PTAL

minor tweaks

@bshaffer Thanks, PTAL

Oh wait, guzzle automatically follow the redirects. I think I need to explicitly suppress this.

Now I use https because nginx thinks the schema is http because App Engine terminates SSL. This redirect doesn't work on localhost, but it's not a big deal.
Suppressed the follow_redirects behavior, so that we can just check the 301 response generated by the added configuration.
The test passes locally.
PTAL

LGTM

Alright, merging


nativescript-bottombar has Podfile and you don't have Cocoapods installed or it is not configured correctly. Please verify Cocoapods can work on your machine..

what type of error is it? @rhanb

Well you don't have cocoapods installed on your Mac.. Or you have a config issue


[New game]: 3D racing game

🎮 Game Request
Game logic and basic description:I created  this racing game using html,css and javascript.The game can played only using a pc.Use keyboard arrow keys to move your car.
Point down the features
Game points
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @Kaashish1111 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign

/assign

Hey @avneetsingh154 ! , This issue is already assigned to @Kaashish1111. 💗
You can work on other issues 🚀
If there is anything wrong you can contact us on Discord🕹👀

I am done with the task

Hello @Kaashish1111, Time's up!⏰
Sorry for closing your issue!
But it's more than a week since we haven't received anything from your side 😢 .
Come up with new ideas, create a new issue and make sure you finish it within a week! 🔥
All the best! 🚀
Happy Hacking! 💗


Discrepancy in Llava-cot Results Between Paper and VLMEvalKit Leaderboard

Hello,
Thank you for your valuable work!
I noticed in your paper that the evaluation tool used is VLMEvalKit. However, on the VLMEvalKit leaderboard (https://rank.opencompass.org.cn/leaderboard-multimodal/?m=REALTIME), the reported test results for Llava-cot differ significantly from those presented in your paper.
I hope you can help address my concerns. Thank you!

Hi @JCruan519 ,
Thank you so much for raising this issue! If the difference is within 1-2%, it might be because they did not filter out the content between . However, regardless of the testing method, such a significant discrepancy is impossible. The result reported by OpenCompass is clearly unreasonable. Thank you again for bringing this to our attention, and we will follow up on this matter.

We provide an evidence: https://huggingface.co/spaces/opencompass/Open_LMM_Reasoning_Leaderboard.
This is also an OpenCompass leaderboard. On this leaderboard, as of the release date, our model ranked second among 10B-scale models, only behind Qwen2-VL-7B, and performed significantly better than Llama-3.2V-11B. However, on the leaderboard you provided, our model performs even significantly worse than Llama-3.2V-11B, which we believe is impossible.

@JCruan519 We have basically identified the issue: OpenCompass used the Llama-3.2V configuration when running the tests, which sets max_token to 128/512. This is completely insufficient for our model (2048), especially for challenging tasks. This explains why our model performed significantly worse, particularly on tasks like MMMU.

@XuGW-Kevin
Hello, thank you very much for your response!
In the link you provided, it seems that only math-related benchmarks are included, with MathVista being the repeated benchmark in your paper. The result in the provided link is 54.2, in your paper it is 54.8, and in the link I provided it is 53.5. These are quite similar, and I don't have any concerns about them.
However, for MMStar, MMBench, HallusionBench, and AI2D, the results show significant differences.
Additionally, during my local reproduction using VLMEvalKit, I found that, for example, in MMStar, due to the influence of the max_new_tokens parameter, and because Llava-COT outputs relatively long reasoning processes, the results are truncated before they are fully generated. This may be one of the reasons for the large discrepancies in performance.
Therefore, I would greatly appreciate it if you could provide the evaluation setup details for VLMEvalKit, such as the max_new_tokens parameter!

Thank you very much for your willingness to test locally! In fact, we have provided the evaluation parameters and instructions for modifying VLMEvalKit at https://huggingface.co/Xkev/Llama-3.2V-11B-cot. However, it seems that many users still tend to use the original parameters.
The modification involves replacing self.kwargs with:
dict(do_sample=True, temperature=0.6, top_p=0.9, max_new_tokens=2048).
I have already reported this to OpenCompass, and they mentioned they would re-run the tests. Just now, I immediately ran a test on MMStar (this is why our response was slightly delayed), and the result was 56.7% (complete answers) and 57.6% (answers only within ),  which is exactly consistent with the reported 57.6% (answers only within ).
We provide the generated results here for your reference:
complete answers: base_model_MMStar.xlsx
answers only within : base_model_MMStar.xlsx
To facilitate verifying our analysis locally, I will soon upload an evaluation script that you can download and run on your local setup. Thank you very much for your support!

@XuGW-Kevin
Thank you very much for your timely reply!
I indeed only focused on the GitHub homepage and the paper, neglecting Huggingface homepage. I will adjust the parameter settings and conduct local testing later.
Once again, thank you for your timely response!

Hello! I used the evaluation.txt you provided above to retest Llava-cot locally. The test results on the other four benchmarks show minimal deviation from the original paper. However, on AI2D, my local test results show an overall score of only 77.49. On MMVet, the result is only 27.94, both of which differ significantly from the original paper. I have attached my XLSX file for your reference:
LLaVA-CoT_AI2D_TEST_openai_result.xlsx
LLaVA-CoT_MMVet_gpt-4-turbo.xlsx
I would greatly appreciate it if you could help resolve my doubts!

Hi, we’re glad you were able to take the time to reproduce our work so quickly!

MMVet Benchmark

This is likely a network issue. (In many examples, we answer correctly, but GPT scores 0.)
Note that Opencompass also reports 63.6% on this benchmark.

AI2D Benchmark
In fact, since you raised this issue three days ago, we have conducted additional tests. Previously, we had been using the AI2D_TEST_NO_MASK version of VLMEvalKit. As a result, the AI2D portion of our training dataset was also trained using the NO_MASK images.
After you brought up this issue, we carefully tried to reproduce why our results differed from those of OpenCompass. We discovered that they were using the AI2D_TEST dataset in their benchmark, not AI2D_TEST_NO_MASK.  (To the best of my knowledge, they did not mention this anywhere. I thought these two versions have no significant difference.) We realized this was an error we had overlooked previously. As a result, we are now replacing the AI2D images in our training set with the MASK versions, retraining the model, and updating the data in our paper. We will report four numbers: train on NO_MASK, test on MASK/NO_MASK; train on MASK, test on MASK/NO_MASK.

Got it, thank you for your quick response! I will check my judge API again.


changing port error (win)

When I want to change port it gives this error.
Private key path must begin with / .

I will check it right now

Yes , i built the windows version with linux web-ui , sorry
will update 0.1.9 win exe asap

updated 0.1.9 windows, you should download it again.


ux: hide show affiliations for contributors if no contributors

Package version (if known): october
Describe the bug
show affiliations” button (in record detail view) shouldn’t appear if no affiliations available

Still the case as of 2021-02-12

Closed by https://github.com/inveniosoftware/invenio-app-rdm/pull/608


Strange characters in the listing

The debug listing contains some strange symbols that look like grave crosses 😱

Suggestion to replace them with regular spaces, the symbol | will still be separated.

@ogamespec bman.lst.tmp is temprary file, it is not the final listing file.
the final listing file is bman.lst ,
you got the bman.lst.tmp because you had an error of assembling that causes a crash.

Oh, I see.
But in general, with it at least roughly understand how the process of assembling goes, even if there was a crash :)


How to reload collectionView in UIViewController?

Thanks for your article firstly!
I'm using Firebase, but I can't figure out how to update collectionView, because the reference is just in the cell where I have the function with delegate etc.
Basically I'm fetching photos from Firebase on viewDidLoad and then user can add photo which means I need to update collectionView.
Do you know how to manage it please?
Thanks!
Vlasti

Oh, solution which works for me is here:
DataService.dateService.fetchPhotos((gallery)!){ (photo) in
    self.photos.append(photo)
    self.tableView.reloadData()

    let indexPath = NSIndexPath(forItem: 2, inSection: 0)
    let collectionViewIndexPath = NSIndexPath(forItem: (self.photos.count + 1), inSection: 0)

    let photoCell: DetailPhotoTableViewCell = self.tableView.dequeueReusableCellWithIdentifier("cell", forIndexPath: indexPath) as! DetailPhotoTableViewCell
    photoCell.configureCell()
    photoCell.setCollectionViewDataSourceDelegate(self, forRow: collectionViewIndexPath.row)
    photoCell.photosCollectionView.reloadData()
}

This code is in my ViewController in viewDidLoad and update my collectionView real-time by Firebase.

Fab! Glad you got it sorted, and thanks for posting a follow-up!


Avoid using the too heavy lodash

This is the only thing keeping from using this library right now. 84% of the size is lodash<EMAIL_ADDRESS>

This is the only thing keeping from using this library right now. 84% of the size is lodash<EMAIL_ADDRESS>
I'll check that

It's not mergeable. Tests fail.
Current version is enough. Probably in 3.0.0, I'll remove color names, so all lodash functions may be removed.


HDDS-8768. Update cross-compatibility test for 1.3.0 release

What changes were proposed in this pull request?
Run cross-compatibility test for both 1.3.0 (already released) and 1.4.0 (built from source).
https://issues.apache.org/jira/browse/HDDS-8768
How was this patch tested?
CI:
https://github.com/adoroszlai/hadoop-ozone/actions/runs/5191899874

Thanks @adoroszlai for the patch. The change looks good.
Does test_ec_cross_compatibility need to be modified?

Does test_ec_cross_compatibility need to be modified?

Good point, I was not aware of this custom test.  I think this will need a bigger change, because the way it is implemented does not scale to new versions.  Created HDDS-8819 for this.

Thanks @captainzmc for reviewing and merging this.


Use set_bone_global_pose_override instead of set_bone_custom_pose

Changes head scaling logic to scale to a small amount instead of 0 so that the original matrix can be reconstructed.

Added similar changes to the avatar tool so it should be good to merge this now


osd_auto_discovery not working on (our) kvm instances

I'm working on getting ceph-ansible testable via teuthology. The osd_auto_discovery feature isn't working on our KVM-based virtual machines. It might be working in our OpenStack test lab. I'm attempting to figure out what is causing the difference in behavior but I figured I should file an issue while I do that, in case there is a fix obvious to someone more experienced with ceph-ansible.
The error I see is:
error while evaluating conditional: item.0.rc != 0 and item.1.rc != 0 and journal_collocation and not osd_auto_discovery
Here is an example of the same job executed on OpenStack vs. executed on KVM.
That's a ton of output so I'll attempt to isolate some relevant things. First, I'm using a separate branch of ceph-ansible with extra debugging.
Here is just the debug from OpenStack vs. the debug from KVM
combined_parted_results.results and combined_ispartition_results.results are very different between the two instances. What I haven't unraveled yet is why - aside from the obvious difference in device counts.

@zmc at a first glance, if the output is so different is mainly because the KVM env has more disks than the OpenStack. On OpenStack, you seem to only have a single drive /dev/vda where on KVM you have /dev/vda, /dev/vdb, /dev/vdc, /dev/vdd.
I just figured out that this https://github.com/ceph/ceph-ansible/blob/master/roles/ceph-osd/tasks/check_devices.yml#L21-L30 is useless while using osd_auto_discovery, the device list will always be a raw device. So this shouldn't run.
I'll push some changes in your branch, if you can try that out since I can't reproduce this with vagrant (somehow :/)


The method get_cover_file_names() doesn't search all the .cover files

The current function only gets the cover files in the test directory, it doesn't move through the folders to search the reports.

We should check the possibility of defining a path to write all .cover files. It may already exist. Take a look at Trace's write_results_file() documentation.

Now all the cover files are saved in the /coverage_reports folder.


Swap HTTPParser Swift package for http-parser - issue #52

Description
Swapped Swift HTTPParser for 'C' http-parser ("CHTTPParser").  HTTPParser is a direct port of http-parser with the goal of being as maintainable as possible.
Motivation and Context
This was initially a thought experiment, but the performance of HTTPParser was only 1.4 times slower than http-parser.  It processes over 500K requests per second using the 'bench' tool in Release mode.  Performance tuning continues.
We also noticed that the CHTTPParser module was causing Xcode compile issues for new Kitura developers.
To Do

Performance comparisons between Kitura based apps using HTTPParser vs CHTTPParser
Test use of NSData bytesNoCopy inside of HTTPParser callbacks within Kitura-net.

How Has This Been Tested?
Kitura-net unit tests pass on Linux and Mac
Kitura unit tests pass on Linux and Mac
Checklist:

[x] I have submitted a CLA form
[ ] If applicable, I have updated the documentation accordingly.
[x] If applicable, I have added tests to cover my changes.

@shmuelk can you review this please?
@dsperling we will probably not want to depend on a 3rd party repo - would you be ok with us forking your repo to IBM-Swift/HTTPParser and making Kitura-net depend on that? We would sync our HTTPParser repo with smithmicro regularly and all development work would happen in your repo. Thoughts?

@ianpartridge I don't have a problem with forking.  I'm glad the port is of interest.
However I would like to understand the reasoning behind your 3rd party repro concerns.  My assumption was that the Swift Package Manager would do the heavy lifting for us where Kitura-net would be pinned to specific HTTPParser releases.  It seems like a extra step having a intermediary repro that needs to be synced.
Another option is that we move the project to IBM-Swift sandbox and I simply provide PR's.  Either way works for us.

Thanks @dsperling. The slight concern about depending on a 3rd party repo is that if a git tag was deleted for some reason, Kitura would stop building. Unlikely I know, but... We have a large and growing stack of projects and repos which rely on Kitura-net.
The offer to host this under IBM-Swift is very much appreciated. I'll discuss with our team and get back to you if that's OK?

Sounds good @ianpartridge

Just ran some performance numbers against this, patched onto Kitura 0.23:
Linux
Implementation | Avg Throughput | Max Throughput | Avg CPU | Avg RSS (kb) | Avg Lat (ms) | Max Lat (ms)
---------------|----------------|----------------|---------|--------------|--------------|--------------
          0.23 |        51837.1 |       52991.06 |    90.6 |       537110 |          2.6 |       219.73
     0.23+pr55 |        45890.1 |       46424.85 |    89.7 |       682325 |          3.0 |        209.5

Throughput reduction is around 12%.  I'll grab a profile from Perf later on.
Mac
Implementation | Avg Throughput | Max Throughput | Avg CPU | Avg RSS (kb) | Avg Lat (ms) | Max Lat (ms)
---------------|----------------|----------------|---------|--------------|--------------|--------------
          0.23 |        18602.5 |       18937.34 |    77.3 |       419451 |          7.3 |       120.37
     0.23+pr55 |        18539.1 |       18850.79 |    78.2 |       490662 |          8.5 |       452.95

Doesn't seem to significantly impact performance on Mac (throughput + cpu differences are within noise), however we have scalability issues at the moment which could obscure a simple compare, we'd need to look at a profile to confirm where time is really being spent.

Profiles for the compare on Linux:
perf-report.023.txt
Requests/sec:  50386.92
Average CPU util: 91.8 %
perf-report.023pr55.txt
Requests/sec:  44668.58
Average CPU util: 91.0 %

This is consistent with what I see using the http-parser stress code.  Time spent in the core parser is:

1.51%  HTTPParser.http_parser.execute
1.19%  http_parser_execute
27% slower

With the ported stress.c to swift, I see:

http-parser - 'C' - 782K req/sec
HTTPParser - Swift - 566K req/sec
38% slower

While HTTPParser does not add memory allocation overhead, it is still adding overhead via retain/release calls.  I am assuing that is reflected here:
023:

0.35%  TechEmpower  libswiftCore.so      [.] swift_release_n
0.34%  TechEmpower  libswiftCore.so      [.] swift_retain_n

023pr55:

0.70%  TechEmpower  libswiftCore.so      [.] swift_retain_n
0.70%  TechEmpower  libswiftCore.so      [.] swift_release_n

This should be the focus on further HTTPParser optimization.  Are we "good enough" to proceed?  What does the team think?
One risk item is that not all unit tests for HTTPParser are ported.  This is progressing but at a slow pace.

Hi @dsperling - I don't think we could merge a PR which impacts Kitura throughput by this much, unfortunately. We are definitely interested in reducing our dependency on external C code, but HTTP parsing is a sensitive area so we'll need to ensure quality (through the ported testsuite) and performance (I'm not sure exactly what cost would be acceptable, I'd guess low single figures).
On the performance front, do you think it would be possible to reduce the ARC overhead? For example, by identifying hot loops that contain swift_retain/release calls and working around them. Just an idea?

@ianpartridge Thanks for your consideration.  We will continue to work on optimizations and test coverage.  I will close the PR and will report status via https://github.com/IBM-Swift/Kitura-net/issues/52.
I would ask that the team suggests an acceptable performance benchmark.  Right now we are 38% slower than http-parser based on bench.c performance tests.  You mentioned low single figures.  That does that mean < 5% slower?

Hi @dsperling!
The bench.c numbers you report seem to be worse than the Kitura throughput numbers that @djones6 measured - 38% compared to 12%. It's the Kitura performance that we're mainly interested in (I guess improving the bench.c results will help Kitura).
There's a tradeoff here: the win of using pure Swift code, ridding ourselves of a C dependency, and simplifying our build process; versus a potential loss of performance and the risks of switching to relatively untested code (the node.js parser has been field-tested for years).
So it's going to come down to a judgement call, eventually. It's fair to ask what the "bar" is though - I will discuss and see what other people's views are. What do you think an appropriate number would be?
As a matter of general principle Swift shouldn't be necessarily slower than C, as a compiled language. If it looks like ARC is the cost here, then it might be worth experimenting with using structs instead of classes as structs don't participate in ARC.

To weigh in here, I agree that < 5% impact on Kitura is a good number to set the bar at in this instance.
In theory, a pure Swift implementation should give the Swift compiler more opportunities to optimize (if I understand correctly that calling into C code is an optimization boundary), so there's the potential for some future performance gain.
There are other considerations besides performance - future enhancement / maintenance, code quality / test coverage, 'swiftyness' - which it would be good to discuss.

@ianpartridge Is it possible for you to submit some form of this as a stripped down benchmark upstream? We are interested in it as an optimization target.

Hi @gottesmm. This PR was for switching Kitura to use a Swift-based HTTP parser - it doesn't contain the new parser itself.
The new parser is at https://github.com/smithmicro/HTTPParser and was written by @dsperling as a port of the Node.js http_parser C code.
Perhaps @dsperling would be interested in contributing his code upstream?

@gottesmm - I would be happy to help.
I stopped work on the Swift HTTPParser back in September when it was clear that the codebase could not meet the performance requirements of Kitura in the short term.  The codebase if functional, but only 10% of the unit tests are ported.
I will get this upgraded to Swift 3.0.1.  I think using the Swift HTTPParser as a benchmark would be a great initial use of this port.
Question:  The codebase has a MIT license where Kitura is Apache 2.  Is that an issue?
Let me know how I can help strip this down for a benchmark.

Ideally we would contribute this to the swift benchmark suite. That would require the code to licensed under the same license as Swift (which is Apache2). Is that possible?
In terms of stripping down the benchmark, I imagine you would want to create a library that could parse any HTTP header. Then we would write a test case that would invoke the HTTP header parser with the same raw pointer that is taken from a constant string.
What do you think?

@gottesmm The project is a port of https://github.com/nodejs/http-parser so I will need to contact the authors.  I will post a question in that project and tag you.

Thanks!

@gottesmm - I couldn't tag you over there, so here is the issue.  Please add any color or correct any of my assumptions.
https://github.com/nodejs/http-parser/issues/344


Polish JUnitPlatformTestClassProcessor

avoid allocating unnecessary intermediate objects via reuse
compose long methods
make long method chains readable under narrower form factor

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test and merge

I've triggered a build for you. Click here to see all failures if there's any.


[Douyin] can't download

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm asking a question and not reporting a bug or requesting a feature
[X] I've looked through the README
[X] I've verified that I'm running yt-dlp version 2023.07.06 (update instructions) or later (specify commit)
[X] I've searched known issues and the bugtracker for similar questions including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Please make sure the question is worded well enough to be understood
PS C:\bin> yt-dlp -S "+codec:h264" --cookies-from-browser firefox https://www.douyin.com/video/7265151697159310644 -o '%(autonumber)s-%(title).20s.%(ext)s'
Extracting cookies from firefox
Extracted 17 cookies from firefox
[Douyin] Extracting URL: https://www.douyin.com/video/7265151697159310644
[Douyin]<PHONE_NUMBER>159310644: Downloading video feed
[Douyin]<PHONE_NUMBER>159310644: Unable to find video in feed; trying with webpage
[Douyin]<PHONE_NUMBER>159310644: Downloading webpage
WARNING: [Douyin] unable to extract render data; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
ERROR: [Douyin]<PHONE_NUMBER>159310644: Fresh cookies (not necessarily logged in) are needed; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
PS C:\bin>
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
No response

Fresh cookies (not necessarily logged in) are needed;

You need to load the video in your browser, solve the anti-bot puzzle challenge, and then pass cookies from your browser to yt-dlp

Fresh cookies (not necessarily logged in) are needed;

You need to load the video in your browser, solve the anti-bot puzzle challenge, and then pass cookies from your browser to yt-dlp

Thank you

Could you provide more details to load the video in browser, I was use --cookies before，but not work in douyin

@xyx361100238 you need to solve the anti-bot challenge, then use --cookies. I'm guessing that the cookies expire after a little bit of time

I was use the latest generated cookies file，unable to resolve address. and i don't know how to solve the anti-bot challenge


writing to bigquery from dataproc

when trying to write to bigquery like so from pyspark in dataproc:
`bigquery = spark._sc._jvm.com.samelamin.spark.bigquery
Prepare the bigquery context
bq = bigquery.BigQuerySQLContext(spark._wrapped._jsqlContext)
bq.setBigQueryProjectId(BQ_PROJECT_ID)
bq.setGSProjectId(BQ_PROJECT_ID)
bq.setBigQueryGcsBucket(STAGING_BUCKET)
bq.setBigQueryDatasetLocation(DATASET_LOCATION)
Extract and Transform a dataframe
df = session.read.csv(...)
Load into a table or table partition
bqDF = bigquery.BigQueryDataFrame(df_master._jdf)
bqDF.saveAsBigQueryTable(
"{0}:{1}.{2}".format(BQ_PROJECT_ID, DATASET_ID, TABLE_NAME),
False, # Day paritioned when created
0,     # Partition expired when created
bigquery.getattr("package$WriteDisposition$").getattr("MODULE$").WRITE_EMPTY(),
bigquery.getattr("package$CreateDisposition$").getattr("MODULE$").CREATE_IF_NEEDED(),
)`
I am getting the following exception:
`Ivy Default Cache set to: /root/.ivy2/cache
The jars for the packages stored in: /root/.ivy2/jars
:: loading settings :: url = jar:file:/usr/lib/spark/jars/ivy-2.4.0.jar!/org/apache/ivy/core/settings/ivysettings.xml
com.github.samelamin#spark-bigquery_2.11 added as a dependency
:: resolving dependencies :: org.apache.spark#spark-submit-parent-c234c14e-60d0-482e-a149-6a46d2a4c43f;1.0
confs: [default]
found com.github.samelamin#spark-bigquery_2.11;0.2.6 in central
found com.databricks#spark-avro_2.11;4.0.0 in central
found org.slf4j#slf4j-api;1.7.5 in central
found org.apache.avro#avro;1.7.6 in central
found org.codehaus.jackson#jackson-core-asl;1.9.13 in central
found org.codehaus.jackson#jackson-mapper-asl;1.9.13 in central
found com.thoughtworks.paranamer#paranamer;2.3 in central
found org.xerial.snappy#snappy-java;1.0.5 in central
found org.apache.commons#commons-compress;1.4.1 in central
found org.tukaani#xz;1.0 in central
found com.google.cloud.bigdataoss#bigquery-connector;0.13.4-hadoop2 in central
found com.google.api-client#google-api-client-java6;1.24.1 in central
found com.google.api-client#google-api-client;1.24.1 in central
found com.google.oauth-client#google-oauth-client;1.24.1 in central
found com.google.http-client#google-http-client;1.24.1 in central
found com.google.code.findbugs#jsr305;3.0.2 in central
found org.apache.httpcomponents#httpclient;4.0.1 in central
found org.apache.httpcomponents#httpcore;4.0.1 in central
found commons-logging#commons-logging;1.1.1 in central
found commons-codec#commons-codec;1.6 in central
found com.google.http-client#google-http-client-jackson2;1.24.1 in central
found com.fasterxml.jackson.core#jackson-core;2.9.2 in central
found com.google.guava#guava;26.0-jre in central
found org.checkerframework#checker-qual;2.5.2 in central
found com.google.errorprone#error_prone_annotations;2.1.3 in central
found com.google.j2objc#j2objc-annotations;1.1 in central
found org.codehaus.mojo#animal-sniffer-annotations;1.14 in central
found com.google.oauth-client#google-oauth-client-java6;1.24.1 in central
found com.google.api-client#google-api-client-jackson2;1.24.1 in central
found com.google.apis#google-api-services-storage;v1-rev135-1.24.1 in central
found com.google.apis#google-api-services-bigquery;v2-rev398-1.24.1 in central
found com.google.cloud.bigdataoss#util;1.9.4 in central
found com.google.auto.value#auto-value-annotations;1.6.2 in central
found com.google.cloud.bigdataoss#util-hadoop;1.9.4-hadoop2 in central
found com.google.cloud.bigdataoss#gcs-connector;1.9.4-hadoop2 in central
found com.google.cloud.bigdataoss#gcsio;1.9.4 in central
found joda-time#joda-time;2.9.3 in central
:: resolution report :: resolve 1060ms :: artifacts dl 27ms
:: modules in use:
com.databricks#spark-avro_2.11;4.0.0 from central in [default]
com.fasterxml.jackson.core#jackson-core;2.9.2 from central in [default]
com.github.samelamin#spark-bigquery_2.11;0.2.6 from central in [default]
com.google.api-client#google-api-client;1.24.1 from central in [default]
com.google.api-client#google-api-client-jackson2;1.24.1 from central in [default]
com.google.api-client#google-api-client-java6;1.24.1 from central in [default]
com.google.apis#google-api-services-bigquery;v2-rev398-1.24.1 from central in [default]
com.google.apis#google-api-services-storage;v1-rev135-1.24.1 from central in [default]
com.google.auto.value#auto-value-annotations;1.6.2 from central in [default]
com.google.cloud.bigdataoss#bigquery-connector;0.13.4-hadoop2 from central in [default]
com.google.cloud.bigdataoss#gcs-connector;1.9.4-hadoop2 from central in [default]
com.google.cloud.bigdataoss#gcsio;1.9.4 from central in [default]
com.google.cloud.bigdataoss#util;1.9.4 from central in [default]
com.google.cloud.bigdataoss#util-hadoop;1.9.4-hadoop2 from central in [default]
com.google.code.findbugs#jsr305;3.0.2 from central in [default]
com.google.errorprone#error_prone_annotations;2.1.3 from central in [default]
com.google.guava#guava;26.0-jre from central in [default]
com.google.http-client#google-http-client;1.24.1 from central in [default]
com.google.http-client#google-http-client-jackson2;1.24.1 from central in [default]
com.google.j2objc#j2objc-annotations;1.1 from central in [default]
com.google.oauth-client#google-oauth-client;1.24.1 from central in [default]
com.google.oauth-client#google-oauth-client-java6;1.24.1 from central in [default]
com.thoughtworks.paranamer#paranamer;2.3 from central in [default]
commons-codec#commons-codec;1.6 from central in [default]
commons-logging#commons-logging;1.1.1 from central in [default]
joda-time#joda-time;2.9.3 from central in [default]
org.apache.avro#avro;1.7.6 from central in [default]
org.apache.commons#commons-compress;1.4.1 from central in [default]
org.apache.httpcomponents#httpclient;4.0.1 from central in [default]
org.apache.httpcomponents#httpcore;4.0.1 from central in [default]
org.checkerframework#checker-qual;2.5.2 from central in [default]
org.codehaus.jackson#jackson-core-asl;1.9.13 from central in [default]
org.codehaus.jackson#jackson-mapper-asl;1.9.13 from central in [default]
org.codehaus.mojo#animal-sniffer-annotations;1.14 from central in [default]
org.slf4j#slf4j-api;1.7.5 from central in [default]
org.tukaani#xz;1.0 from central in [default]
org.xerial.snappy#snappy-java;1.0.5 from central in [default]
:: evicted modules:
org.slf4j#slf4j-api;1.6.4 by [org.slf4j#slf4j-api;1.7.5] in [default]
---------------------------------------------------------------------
|                  |            modules            ||   artifacts   |
|       conf       | number| search|dwnlded|evicted|| number|dwnlded|
---------------------------------------------------------------------
|      default     |   38  |   0   |   0   |   1   ||   37  |   0   |
---------------------------------------------------------------------
:: retrieving :: org.apache.spark#spark-submit-parent-c234c14e-60d0-482e-a149-6a46d2a4c43f
confs: [default]
0 artifacts copied, 37 already retrieved (0kB/19ms)
19/09/17 16:14:30 INFO org.spark_project.jetty.util.log: Logging initialized @4647ms
19/09/17 16:14:30 INFO org.spark_project.jetty.server.Server: jetty-9.3.z-SNAPSHOT, build timestamp: unknown, git hash: unknown
19/09/17 16:14:31 INFO org.spark_project.jetty.server.Server: Started @4753ms
19/09/17 16:14:31 WARN org.apache.spark.util.Utils: Service 'SparkUI' could not bind on port 4040. Attempting port 4041.
19/09/17 16:14:31 INFO org.spark_project.jetty.server.AbstractConnector: Started ServerConnector@2242b679{HTTP/1.1,[http/1.1]}{<IP_ADDRESS>:4041}
19/09/17 16:14:31 WARN org.apache.spark.scheduler.FairSchedulableBuilder: Fair Scheduler configuration file not found so jobs will be scheduled in FIFO order. To use fair scheduling, configure pools in fairscheduler.xml or set spark.scheduler.allocation.file to a file that contains the configuration.
19/09/17 16:14:31 INFO org.apache.hadoop.yarn.client.RMProxy: Connecting to ResourceManager at sidm-cluster-02-m/<IP_ADDRESS>:8032
19/09/17 16:14:31 INFO org.apache.hadoop.yarn.client.AHSProxy: Connecting to Application History server at sidm-cluster-02-m/<IP_ADDRESS>:10200
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/com.github.samelamin_spark-bigquery_2.11-0.2.6.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/com.databricks_spark-avro_2.11-4.0.0.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/com.google.cloud.bigdataoss_bigquery-connector-0.13.4-hadoop2.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/joda-time_joda-time-2.9.3.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/org.slf4j_slf4j-api-1.7.5.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/org.apache.avro_avro-1.7.6.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/org.codehaus.jackson_jackson-core-asl-1.9.13.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/org.codehaus.jackson_jackson-mapper-asl-1.9.13.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/com.thoughtworks.paranamer_paranamer-2.3.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/org.xerial.snappy_snappy-java-1.0.5.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/org.apache.commons_commons-compress-1.4.1.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/org.tukaani_xz-1.0.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/com.google.api-client_google-api-client-java6-1.24.1.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/com.google.api-client_google-api-client-jackson2-1.24.1.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/com.google.apis_google-api-services-storage-v1-rev135-1.24.1.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/com.google.apis_google-api-services-bigquery-v2-rev398-1.24.1.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/com.google.code.findbugs_jsr305-3.0.2.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/com.google.guava_guava-26.0-jre.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/com.google.oauth-client_google-oauth-client-1.24.1.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/com.google.oauth-client_google-oauth-client-java6-1.24.1.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/com.google.cloud.bigdataoss_util-1.9.4.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/com.google.cloud.bigdataoss_util-hadoop-1.9.4-hadoop2.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/com.google.cloud.bigdataoss_gcs-connector-1.9.4-hadoop2.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/com.google.api-client_google-api-client-1.24.1.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/com.google.http-client_google-http-client-jackson2-1.24.1.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/com.google.http-client_google-http-client-1.24.1.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/org.apache.httpcomponents_httpclient-4.0.1.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/org.apache.httpcomponents_httpcore-4.0.1.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/commons-logging_commons-logging-1.1.1.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/commons-codec_commons-codec-1.6.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/com.fasterxml.jackson.core_jackson-core-2.9.2.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/org.checkerframework_checker-qual-2.5.2.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/com.google.errorprone_error_prone_annotations-2.1.3.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/com.google.j2objc_j2objc-annotations-1.1.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/org.codehaus.mojo_animal-sniffer-annotations-1.14.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/com.google.auto.value_auto-value-annotations-1.6.2.jar added multiple times to distributed cache.
19/09/17 16:14:33 WARN org.apache.spark.deploy.yarn.Client: Same path resource file:///root/.ivy2/jars/com.google.cloud.bigdataoss_gcsio-1.9.4.jar added multiple times to distributed cache.
19/09/17 16:14:35 INFO org.apache.hadoop.yarn.client.api.impl.YarnClientImpl: Submitted application application_1568730559207_0014
19/09/17 16:16:10 WARN org.apache.spark.util.Utils: Truncated the string representation of a plan since it was too large. This behavior can be adjusted by setting 'spark.debug.maxToStringFields' in SparkEnv.conf.
Traceback (most recent call last):
File "/tmp/5573a94d3db144558111c14b4dba7f38/ingest_bq.py", line 49, in
bigquery.getattr("package$CreateDisposition$").getattr("MODULE$").CREATE_IF_NEEDED(),
File "/usr/lib/spark/python/lib/py4j-0.10.7-src.zip/py4j/java_gateway.py", line 1257, in call
File "/usr/lib/spark/python/lib/pyspark.zip/pyspark/sql/utils.py", line 63, in deco
File "/usr/lib/spark/python/lib/py4j-0.10.7-src.zip/py4j/protocol.py", line 328, in get_return_value
py4j.protocol.Py4JJavaError: An error occurred while calling o68.saveAsBigQueryTable.
: java.lang.NoSuchMethodError: com.google.cloud.hadoop.io.bigquery.BigQueryStrings.parseTableReference(Ljava/lang/String;)Lcom/google/api/services/bigquery/model/TableReference;
at com.samelamin.spark.bigquery.BigQueryDataFrame.saveAsBigQueryTable(BigQueryDataFrame.scala:40)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at py4j.reflection.MethodInvoker.invoke(MethodInvoker.java:244)
at py4j.reflection.ReflectionEngine.invoke(ReflectionEngine.java:357)
at py4j.Gateway.invoke(Gateway.java:282)
at py4j.commands.AbstractCommand.invokeMethod(AbstractCommand.java:132)
at py4j.commands.CallCommand.execute(CallCommand.java:79)
at py4j.GatewayConnection.run(GatewayConnection.java:238)
at java.lang.Thread.run(Thread.java:748)
19/09/17 16:16:11 INFO org.spark_project.jetty.server.AbstractConnector: Stopped Spark@2242b679{HTTP/1.1,[http/1.1]}{<IP_ADDRESS>:4041}
Job output is complete`

Sounds like you are missing some libraries, try ensuring the bigdata-interop libraries are added to the class path
Using scala libs from python is always a pain im afraid


Add JDK 11 Builds

This commit adds build jobs for JDK 11 to CircleCI.

these ci failures are really random 😢
I didn't even touch the code, but build jobs that have not been affected at all suddenly fail...

failing tests are fixed with #10.
Please merge that one first :)

Sorry for the late reply.
Thanks for contributing!
Looks good to me 👍

v1.9.0 has been released 🎉
https://github.com/akihyro/orika-spring-boot-starter/releases/tag/v1.9.0


fix authentication typos

Modify this link to include the branch name, and possibly the page this PR modifies:
https://github.com/OSC/ood-documentation/blob/develop/source/authentication.rst
Add your description here
Fixes "authentication" typos -- was "authentiction"

Thank you for the fixes. Could you instead make a pull request against latest branch? develop is for the next release and there's automation to sync latest -> develop so it'll get fixed in the current docs (latest) and the next release too.

submitted for latest, closing this one.


Empty and unmodifiable collections [HPPC-167]

It will be useful to have analog of java standard Collections in HPPC like

public static IntIntMap emptyIntIntMap()
public static IntIntMap unmodifiableIntIntMap(IntIntMap map)

Issue: HPPC-167 (migrated from JIRA), created by Konstantin Pavelko, resolved Oct 24 2017

Comment by Dawid Weiss (@dweiss) (migrated from JIRA)
Well, the tradeoffs are always there. Mine is size. If you need full collection support then look at Fastutil or Koloboke – I think both provide what you're looking for.

Comment by Konstantin Pavelko (migrated from JIRA)
I did, but creating them manually, on demand, is too complicated.

Comment by Dawid Weiss (@dweiss) (migrated from JIRA)
Those things are useful, but lead to a lot of generated code (for all type combinations) and I'd rather keep it small. You can create such utilities in your own code though!


Added HTML parser support

:)
@stephanebachelier It's squashed into one single commit.
Thanks

Why do we need run.js in root? Can't you move it in test/?

Sorry. I forgot remove it. It will be done.

It's done.
Will it be merged?

I'll leave this to @stephanebachelier. But you should squash those 2 commits.

Squash again?
:sweat:
Let's go...

It's done.

Any feedback guys?
I'm using my own repository but I wish move to the right target
:blush:

Any reason you use parse5 instead of cheerio?

Only one reason, performance!

@marcelaraujo sorry for the delay, client work in the pipe. I really want to merge your work as it's a major feature and will solve lots of issues in this repo. I come back to you this week after having made some tests on real projects.

@marcelaraujo @XhmikosR I would like to have the #518 to pass before if it might be accepted, as I had hard time rebasing the work done in #306. This PR should be easy to rebase on #518.

Ok.
:+1:

@marcelaraujo BTW feel free to ping me if I ever get lost in client work :)

I don't think we will have problems between both PR's because we work on different files. Maybe some tests will break... maybe...
:)

@marcelaraujo I've created a dev branch to merge majors PR. Could you create another PR on top of dev branch. You can't edit a PR.


Allow enabling NoNeckPain per buffer

Describe the problem
Currently, running :NoNeckPain will enable it for every opened and new buffers.
Describe the solution
It would be nice to be able to choose whether to enable the NoNeckPain mode for every opened and new buffers or only for the current buffer. We could then be able to enable it on selected buffers rather than all of them by default. This would also, as a consequence, allow users to enable the plugin for specific filetypes using autocmd.

Hey, do you mean you'd like the plugin to automatically enables for specific files only?

Not exactly, I was more describing having a way to enable it manually per buffer. Say I'm looking at buffer A and I also have buffer B opened, if I run the command :NoNeckPain enable-only-on-this-buffer then NoNeckPain would be enabled for buffer A. Then if I switch to buffer B, NoNeckPain would be disabled, until I switch back to buffer A.
I'm not sure how feasible that would be but it'd be very useful in my use-case.

Not exactly, I was more describing having a way to enable it manually per buffer. Say I'm looking at buffer A and I also have buffer B opened, if I run the command :NoNeckPain enable-only-on-this-buffer then NoNeckPain would be enabled for buffer A. Then if I switch to buffer B, NoNeckPain would be disabled, until I switch back to buffer A.
I'm not sure how feasible that would be but it'd be very useful in my use-case.

Ahhh that make sense, in that case it seems to perfectly suit the tab behavior on Neovim, not sure if we can abstract that at the buffer level


[core] add oom-specific retry to tasks

Why are these changes needed?
The task can be killed by the memory monitor when the node is low on memory. This may cause more failures and retries and may cause existing workload to fail if it uses up its retry.
This PR adds additional retry for when the task was killed due to OOM. When this happens it will first consume a OOM-specific retry, and if it ran out of OOM-specific retry it will then fall back to task retry.
Related issue number
Checks

[x] I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
[x] I've run scripts/format.sh to lint the changes in this PR.
[x] I've included any doc changes needed for https://docs.ray.io/en/master/.
[x] I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
Testing Strategy

[x] Unit tests
[ ] Release tests
[ ] This PR is not tested :(

Moved to https://github.com/ray-project/ray/pull/28714


DOC: Create MAINTAINERS.md

As discussed in person. This lists the people that are maintainers on ophyd

We decided it in person as a large group of NSLS-II, DLS and LCLS people, using basically the methodology you describe. I appreciate though that some people on the list may feel it's been thrust upon them and I should have been more descriptive in the PR description that this is effectively that request. I'll add everyone on the list as a reviewer and we won't merge until we're all happy. @danielballan maybe we should do the same process for the other MAINTAINER.md files?
We can discuss further on here or mattermost if people have concerns but my understanding was that the role isn't really any additional work above what people are doing anyway and that we wanted to err on the side of lots of people from lots of facilities.

@DominicOram Thanks for your response.  I'm just asking so the process becomes documented (resolves any questions in the future).

This approved PR languishes.  Can it be merged now?

I think that it was @klauer's intention to step back, and that we should remove him from this list. I hope it goes without saying that future input from Ken would always be more than welcome anywhere in the project.
Maybe @ZLLentz or @tangkong can confirm. With that change, I think we should merge.


Define the file name on storageOptions

First of all thanks for this great library. It is very useful.
Feature Request
Option to define the not only the path, also the file name to be save on storage.

Why it is needed
When it is need to store a profile picture, we can use the user ID. Therefore, it will be easy to find the foto desired among the other photos.

Regards,
Iúri

yup ! it is the most needed feature. In Many projects we need to save by the customized name like userID or something unique related to user. so that accessing user photo along with other profile details can be done without extra efforts.
there are some libraries that allows to reaname and move to desired directory but that needs extra efforts.
If this tiny attribute "fileName" as string is added to the storageOptions object then it will be very awesome.
we need this feature. dont close this repo. remove the stale label.
I'm struggling with this issue from last somedays.

Is anything happening about this issue ?


Conflicting info on live fire

To launch a server for Live Fire, gamemode needs to be set to "speedball", not "lf". If "lf" is used, the server starts up with Skirmish.
Simultaneously, for a server to display as Live Fire in the server browser, "lf" does need to be set, but only as the playlist.
Nowhere did I find this info on the wiki hosting info page, and the "speedball" term I only found on discord.

Huh, thanks for the heads-up <3

this is a vanilla issue, the gamemode is speedball, and the playlist is lf, it's the only playlist/gamemode in the game to be like this (thanks respawn!)

Right, want it to be documented, as the wiki currently does not make note of this.
I was left scratching my head on why my Live Fire server kept starting up with skirmish, yet "correctly" appearing as Live Fire in the server browser. I found the "speedball" term on discord, but there "lf" was missing a mention in turn.
In both cases, setting up a server one will run into this "special case" causing confusing issues. Both terms need to be included in the wiki, then, along with an explanation.

I'm not quite sure what the best place is to mention that for Live Fire gamemode and playlist variable are different. A disclaimer in Gamemodes section on the Hosting a Dedicated Server page maybe?

Gamemodes section, I'd say.
Maybe add a third column called Gamemode next to playlist. Either add a third column for whole the table, with the same names for playlist and gamemode for all but Live Fire, or move Live Fire into it's own table either above or below of the other vanilla modes.

Playlist
Gamemode
Title

lf
speedball
Live Fire

Perhaps also mention in the blurb at the top of the section, that Live Fire is an exception to the rule, where playlist and gamemode names for it differ, and that startup args need to be set accordingly.

Closed by #74


feat(EMS-2583): No PDF - Policy - Another company - Form validation, redirections

Introduction :pencil2:
This PR adds form validation to the "Another company" form as part of a No PDF's policy section.
Also updated the policy section flow so that:

The "Pre-credit period" form redirects to the "Another company" form.
The "Another company" form redirects to the "Broker" form

Resolution :heavy_check_mark:

Add a new post route and validation rules for the  "Another company" form.
Add error message content strings.
Create new cypress command to complete and submit the "Another company" form.
Add/update E2E test coverage.

Miscellaneous :heavy_plus_sign:

Fix some typos.

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

:exclamation: No coverage uploaded for pull request base (main-application-no-pdf@baa9f14). Click here to learn what that means.

Additional details and impacted files
@@                    Coverage Diff                     @@
##             main-application-no-pdf    #1744   +/-   ##
==========================================================
  Coverage                           ?   98.38%
==========================================================
  Files                              ?      484
  Lines                              ?     8087
  Branches                           ?      871
==========================================================
  Hits                               ?     7956
  Misses                             ?      129
  Partials                           ?        2

Flag
Coverage Δ

unit-test
98.38% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Add support for defined startup containers in preferences.yml

Provides a method for defining startup containers (in docker compose v2 format) within the preferences.yml file.
I have several utility containers (such as postgres and redis) that I like to have always running when I bring up the VM. This change allows for these to be started as part of dinghy.
Example preferences.yml:
---
:preferences:
  :proxy_disabled: true
  :fsevents_disabled: false
  :create:
    provider: virtualbox
    disk: 40960
  :startup_containers:
    postgres:
      image: postgres
      ports:
      - 5432:5432
      environment:
      - VIRTUAL_HOST=postgres.docker
    redis:
      image: redis
      ports:
      - 6379:6379
      environment:
      - VIRTUAL_HOST=redis.docker

Open to any feedback as I see this as a nice enhancement.

I was just considering something like this.  Bonus points if we can use this to send arguments to docker run for the http proxy.

so, was considering if there would potentially be a better way to handle the http_proxy container. There is no reason that the same http_proxy container couldn't be listed as a 'startup' container here, and all of the arguments sent to it. In fact, disabling the proxy, and then adding it to the startup container would get you the behavior you are looking for, since you can add whatever arguments you would want to the compose file. What sort of arguments would you want to send to it?
For my purposes, we are using kong as the front proxy, so we are disabling the http_proxy container, but I figured it would be better to keep it as is, since this is the behavior most people would want (I think)

I was interested in leveraging the per-vhost config behavior from nginx-proxy.

Hey @dbeard thanks for the PR. I'm not sure I understand the utility here, why is adding this to Dinghy preferable to just running docker-compose yourself? It seems if anything more difficult for teams to keep their dinghy preferences in sync than it would be to just share a repo containing a docker-compose.yml file.

Thanks @codekitchen - the past week that I've been using dinghy and it's been a great tool - something we'll probably move over to as a team.
I would say my reasoning is similar to the reason that I assume you are including http_proxy within dinghy as well - trying to simplify and make our development environment as easy and seamless as possible. Coming from the rails world, it felt a little cumbersome imo to have to start the vm, and then on top of that go to another project and run docker-compose before you could even start working on your main task.
Personally, would rather just run dinghy up and I'm ready to go. Keeping the preferences file in sync is something I've considered, and I think there are various ways we could accomplish that (and I wouldn't really anticipate this changing that much).

@dbeard That desire is why I've wrapped dinghy with a fork of dash.  See: https://github.com/outstand/dash
Note: I haven't updated the project README.
Getting started:

Install Parallels from http://www.parallels.com/directdownload/pd11
bash <(curl -fsSL https://raw.githubusercontent.com/outstand/dash/master/bin/bootstrap)
Start a new shell
dev machine create
eval $(dev machine env)
dev up

OK I think I understand where you're coming from. I would propose that the most common way of doing this, and the way that our 150+ engineers are doing this, is to have a docker-compose.yml in each of your projects, which starts up postgres, redis, etc. along with your application. Running a global instance of these dependencies destroys many of the benefits of using docker for development work.
That's not to say this should be impossible to do, if that's how you want to set things up for your teams. But as @ryansch suggests, it makes more sense for your team to write a custom launcher script, it'll be much more flexible and easier to make changes to.
Regarding the DNS resolver and HTTP proxy, the only reason it exists as part of dinghy today is because it's not yet possible for it to exist as a docker-machine plugin. That's my eventual goal, and in fact, as docker-machine evolves and its plugin system becomes more powerful, I anticipate that someday dinghy won't exist at all, or will be nothing more than an installer script. I should write up a roadmap explaining these goals, that's my fault for not having any clarifying documentation around. Dinghy predates docker-machine, so a lot of the decisions made in the code still don't reflect the current long-term plan.

Thanks for the feedback, and I think you're right upon further consideration, we should segment out our docker compose files to each have their own reference to a postgres/redis/etc container instead of a global container that is used by all local applications.
We do still have the challenge of the HTTP proxy - we are using Kong currently, and trying to have parity between our development and production environments. I do still see value in having startup containers for some of these services that are really outside of the scope of the application.
I could re-architect it so that it's more about having a different proxy container instead of calling them generic startup containers? Even limiting it to just a proxy container though I feel like limits other possible utility containers such as a mail proxy (e.g. mailcatcher), etc. Having a general startup containers section in the preferences I feel gives the flexibility, but would like to better understand what makes the most sense from dinghy's perspective and where you are planning on taking it.
Definitely excited about some of the long term goals you have with docker-machine!

Yeah it's unfortunate that the proxy and DNS resolving is built into Dinghy itself, it's solving a different problem and should be a separate system. It'll probably get moved into a separate project soon, actually, because we have a dev team using Linux that wants the same DNS+proxy functionality. For now, you can disable it with dinghy up --no-proxy or modify preferences.yml so that you can set up Kong in its place.
I'd really like to avoid getting Dinghy into the business of managing containers, there's better tools for the job. In my ideal world docker-machine would have this solved already, but perhaps the best solution for now is a simple hook system where Dinghy can call one or more scripts which can do whatever they want. I'll need something like that anyway if I move the DNS resolver to a separate project.
Rather than potentially having multiple plugins trying to write themselves into one preferences file, I'm thinking something like a ~/.dinghy/hooks/up dir, and dinghy just executes each script it finds in that dir, in name order.

Great idea - I like the flexibility of hooks for other things as well. Closing this now, and will open a separate PR for hooks functionality to get feedback


elinks-git: Rebuild with gnutls.

Why build it with gnutls instead openssl?

I notice that elinks's GNU license dosen't include OpenSSL exception.
So, I rebuild with GnuTLS.


Enable secret scanning with the enterprise-level REST API

GitHub Changelog: Enable secret scanning with the enterprise-level REST API
https://github.blog/changelog/2022-12-13-enable-secret-scanning-with-the-enterprise-level-rest-api/

This would be a great PR for any new contributor to this repo or a new Go developer.
All contributions are greatly appreciated!
Feel free to volunteer for any issue and the issue can be assigned to you so that others don't attempt to duplicate the work.
Please check out our CONTRIBUTING.md guide to get started. (In particular, please remember to go generate ./... and don't use force-push to your PRs.)
Thank you!


Plotting code and tutorial enhancements

Notes to self. From while going through draft tutorial notebooks #84 with @kammerje  and @juliengirard.

[x] display image function, would be nice to label SCI vs REF in the images
[ ] Show in tutorial notebook use of !open on a Mac to open the PDFs
[x] Add comment explanation text about level 2 images should look much like level 1, except scaled now to MJy/sr
[ ]  Consider updating log text output to update lines in place in some cases, for instance using tqdm for a progress meter
[ ] Update the plotting code in recenter and align to show those plots in the notebook, or just read the output PDFs into the notebook
[ ]  Check debug align_ref plots that should show all the data points for all 9 dithers
[x]  Minor, move the Align-ref plots gray axes lines to further back zorder. And add some metadata in these plots for filters etc.
[x]  check if the bad pixel fixing corrects the DQ flags or not; why does my plotting code still show many BPs after the cleaning steps? It may not save the DQs in the output. Specifically the DO NOT USE bit.
[ ]  extract_companions doc str says it can accept a dict but it actually can’t
[ ]  Extract companions should not need the star spectrum input. That’s only really needed for the contrast.
[ ]  MIRI contrast analyses needs the mask file for where to mask out around the QPM axes
[ ]  If you haven’t made the contrast PSF masks, it should print a warning about that.
[ ]  Update the method behind the scenes for producing the PSF mask file with the many shifted copies. Can avoid outputting many temp files, instead use the shift metadata at the end to generate it all
[ ]  Consider masking all the ND square regions to NANs or otherwise in general mask them to be unused.

[ ] write an update_miri_centers() equivalent to update_nircam_centers() to move that code out of the tutorial notebook

[ ] Revisit and think more about order of operations for recentering/aligning frames versus padding. Right now, the reentering steps happen before padding, which introduces wrapping. It seems it would be better to pad with zeros first at least enough to avoid wrapping, and shift into that padded array. This is only relevant for the outermost pixels in the FOV however, but may be relevant for minimizing edge effects in MIRI coronagraphy?

MIRI masks for the FQPM have been incorporated in the calcon branch.


Change language - compatibility with Next 13

What version of this package are you using?
2.6.2 (latest at this day)
What problem do you want to solve?
With Next 13 and  app dir compatibly is poor, specially when changing the language in current navigation.
import setLanguage from 'next-translate/setLanguage' gives an error (even with a use client directive):
Error: No router instance found.
You should only use "next/router" on the client side of your app.
Based on what I see on README note the workaround for now it to use a middleware that appends ?lang=es to each navigation. And add "dynamic root directory" [lang]
Readme note : https://www.npmjs.com/package/next-translate#14-use-next-13-app-directory
What do you think is the correct solution to this problem?
Fix import setLanguage from 'next-translate/setLanguage' to allow changing language programmatically.
The workaround provided in the readme note suggest changing the files structure of the project and depending on how the app is hosted and built this could require changes on all Links (add /lang path)

Any workaround on this??


Mentioning a common pitfall in the tutorial

Since a user can reasonably be expected to land on this tutorial immediately following the one regarding the manifest generation pipeline, it seems like a good idea to mention this pitfall.

It would also make sense to remove the step from the preceding tutorial to set FAB_ENVS, as the build script will automatically set the env to 'prod' as it is done in the tutorial. There would be functionally no difference.


fix: ignore merge commit linting

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


Comparison with old Non-R implementation of statistics.

I cleaned up the data from Jonathan's old project and wrapped it in a script that generates a comparison. Should be able to run this out of the box. Since the file doesn't start with "test" it shouldn't run as part of the CI tests.

Coverage remained the same at 83.632% when pulling db7de4145fdbef960ada75bc9e156e8c29b4f60a on dblodgett-usgs:master into 7eeccdf96595e47aed785d17c22fbdc560eb86f5 on USGS-R:master.

Coverage remained the same at 83.632% when pulling 4d927d4cdea3cd7a24d1e2cf10231ee9e821a78e on dblodgett-usgs:master into 7eeccdf96595e47aed785d17c22fbdc560eb86f5 on USGS-R:master.

Coverage increased (+1.3%) to 84.91% when pulling b797dfee03a40b35bec8ffc55532075b39bfdb67 on dblodgett-usgs:master into 7eeccdf96595e47aed785d17c22fbdc560eb86f5 on USGS-R:master.

Coverage increased (+1.4%) to 85.081% when pulling 150cf3c8da76ee22dfeeb6ac6297e5163105e290 on dblodgett-usgs:master into 7eeccdf96595e47aed785d17c22fbdc560eb86f5 on USGS-R:master.


Build fails with resolve import "lit-html/directives/until.js" from "build/client/App.js".

build fails with
3 modules transformed.
[vite]: Rollup failed to resolve import "lit-html/directives/until.js" from "build/client/App.js".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
error during build:
Error: [vite]: Rollup failed to resolve import "lit-html/directives/until.js" from "build/client/App.js".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
    at onRollupWarning (/Users/onurgumus/.nvm/versions/node/v16.9.0/lib/node_modules/vite/dist/node/chunks/dep-e0fe87f8.js:43253:19)
    at onwarn (/Users/onurgumus/.nvm/versions/node/v16.9.0/lib/node_modules/vite/dist/node/chunks/dep-e0fe87f8.js:43037:13)
    at Object.onwarn (/Users/onurgumus/.nvm/versions/node/v16.9.0/lib/node_modules/vite/node_modules/rollup/dist/shared/rollup.js:22994:13)
    at ModuleLoader.handleResolveId (/Users/onurgumus/.nvm/versions/node/v16.9.0/lib/node_modules/vite/node_modules/rollup/dist/shared/rollup.js:22338:26)
    at /Users/onurgumus/.nvm/versions/node/v16.9.0/lib/node_modules/vite/node_modules/rollup/dist/shared/rollup.js:22310:26

Ok, this is probably related to #4. Are you using pnpm? I think I finally understand what it's happening, some places in Fable.Lit request things directly from lit-html, which should be there because it's a dependency of lit, but pnpm doesn't create symlinks for transitive dependencies so the bundler complains.
I will change Fable.Lit so everything is requested from "lit" package instead :+1:

Yes I was using npm. Thanks for the quick fix,

I've updated the repo to use latest Fable.Lit, can you please try again and reopen if you still have issues?
BTW, latest Fable.Lit also enables scoped CSS for components not using Shadow DOM.


Multiple descriptions of switches

Hello,
Just wondering why there is a second set of descriptions for the following switches:  /xc /xn /xo /xx /xl /im /is /it
Thank you

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

ID: bf2281d4-1470-0658-ec5a-687fe2cd451c
Version Independent ID: 2ce2be3e-e3a2-790c-3bff-90efe7318450
Content: robocopy
Content Source: WindowsServerDocs/administration/windows-commands/robocopy.md
Product: windows-server
Technology: windows-commands
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

#assign:xelu86

Hey @b-cpu,
Thanks again for contacting Microsoft. We value your feedback. A documentation change has been made and will be live after the next business day. We will be closing this as resolved. Thank you and have a most pleasant day. #please-close

Thank you for the update!
On Fri, Aug 5, 2022, 5:03 PM Xelu86 @.***> wrote:

Hey @b-cpu https://github.com/b-cpu,
Thanks again for contacting Microsoft. We value your feedback. A
documentation change has been made and will be live after the next business
day. We will be closing this as resolved. Thank you and have a most
pleasant day. #please-close
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/windowsserverdocs/issues/5701#issuecomment-1206961734,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMP2IGGDLQEF7AWWQPAZXMDVXWFS3ANCNFSM5AFRFWGA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Overload for FromJsonAsync with JsonReferenceResolver factory support

Proposed fix for https://github.com/RSuter/NSwag/issues/1458 with overload for SwaggerDocument.FromJsonAsync() with JsonReferenceResolver factory parameter. Also referenced NJsonSchema.Yaml in NSwag.Core.Yaml project, and used JsonAndYamlReferenceResolver.

I also did the changes but didnt have the time to commit: https://github.com/RSuter/NSwag/pull/1470
Are these the same changes? Can we merge my PR and you provide the tests with this PR?

Thanks for your time again! Your changes looks more clear in case of public api, but you don't use JsonAndYamlReferenceResolver as a default ReferenceResolver in FromYamlAsync method. To fix the issue, it needs to be the default ReferenceResolver, or JsonAndYamlReferenceResolver should be passed to other calls of FromYamlAsync method in the project, for example, in OutputCommandBase.ReadSwaggerDocumentAsync(). Depending on your decision, tests from my PR should take JsonAndYamlReferenceResolver as a parameter, or not.

Merged your changes from https://github.com/RSuter/NSwag/pull/1470 and used JsonAndYamlReferenceResolver as a default in SwaggerYamlDocument.


Use buffered reading when reading files in SynthesizeDependenciesTask

Fixes #828

@autonomousapps Could you review this one? 1% of total builds are hit by this issue:
Execution failed for task *
> A failure occurred while executing com.autonomousapps.tasks.SynthesizeDependenciesTask$SynthesizeDependenciesWorkAction
   > Java heap space

@daanschipper feel free to submit another PR with this idea.

@autonomousapps Can you release a new version with this fix again? 🙏

@autonomousapps apologies for another ping (I am a colleague of Daan). We are hitting this particular issue quite often and are currently contemplating temporarily disabling the plugin to unblock our engineers. Ideally we don't do that, but we are running out of options. A new release would help us a lot to get the fix in our build. Would that be a possibility today? Thank you so much for your dedication to this project and we are eager to continue contributing to it.

Published as 1.18.0 🎉


ACM-4239 throw error on invalid hosted cluster name import

backport of https://github.com/stolostron/console/pull/2515

/cc @fxiang1


Why is the fastify.close() method in successful connection?

I removed that line of code and It started working again.

It's an example file which shows a message in the console and closes Fastify server and Sequelize.
You do not need to use the example file in your project.

It's an example file which shows a message in the console and closes Fastify server and Sequelize.
You do not need to use the example file in your project.

Ok I understand, thank you very much for the plugin.

@santi1428 thank you, glad to hear that!


[BUG] cannot install this package by pnpm

Summary:
Follow document to install this package with pnpm and occur below problem

its looks like be block with package.json.
because document allow install with pnpm, so i think this should be a bug

Environment:
Operating System & version: windows 10
Node.js version (node -v): v18.18.0
NPM version: (npm -v): pnpm version is 8.3.1
Dynamode version: 0.7.3
Other:

[x] I have read through the Dynamode documentation before posting this issue
[x] I have searched through the GitHub issues (including closed issues) and pull requests to ensure this issue has not already been raised before
[x] I have searched the internet to ensure this issue hasn't been raised or answered before

Interesting! Thanks for posting this issue I'll look into it tomorrow 😄

@moonrailgun It should be fine now, with version 0.7.5. I also updated the docs:


Clappr is not playing when clicked/touched with chromeless: true

Browser: All
Clappr Version: 0.2.38
Steps to reproduce:

go to cdn.clappr.io
then set chromeless: true try to click/touch to play
I was expecting Clappr start to play but instead it didn't

Notice also that a mini play icon is shown

I thought that was a feature so that you could programmatically control the playback without the user being able to change it.
Not sure about the play button though.

On 10 Mar 2016, at 14:47, Leandro Moreira<EMAIL_ADDRESS>wrote:
Browser: All
Clappr Version: 0.2.38
Steps to reproduce:
go to cdn.clappr.io
then set chromeless: true try to click/touch to play
I was expecting Clappr start to play but instead it didn't
Notice also that a mini play icon is shown
—
Reply to this email directly or view it on GitHub.

@tjenkinson actually this is related to mobile. Since there's no autoplay support on most mobile devices, there should be a way to allow the player to work chromeless, but still being able to play through user interaction.

@towerz I agree mobiles not supporting play without user interaction causes issues. But I don't think we should allow user interactions in chromeless because developers might have code that depends on the user not being able to interact with the player.
Or chromeless could be changed so user interaction is allowed, but then there could be a separate option 'disableUserInteraction'? It's just that that would break backwards compatibility.

@tjenkinson I think you're right. Perhaps we should add this option disableUserInteraction you suggested.
My idea for that option, in order to keep backwards compatibility, is to have a default value set to !Browser.isMobile when the option is not set. This option should only work when chromeless is set to true.
What do you think?

@towerz that sounds good to me

Closing the issue, there are no more needed changes to fix this behavior.


Count in source control in side bar is wrong

VSCode Version: Code 1.16.1 (27492b6bf3acb0775d82d2f87b25a93490673c6d, 2017-09-14T16:26:20.018Z)
OS Version: Linux x64 4.10.0-35-generic
Extensions: none

Steps to Reproduce: I don't know
Hitting the refresh button doesn't update the erroneous counter.
Screenshots: https://i.imgur.com/mjeQUR3.png https://i.imgur.com/UIeyAXf.png
It seems that the counter is always 1 higher than the real number
Restarting VSCode fixes the problem

Interesting. What does git status -u return in the command line?


HDDS-10733. Merge HDDS-7593 (related to hsync and lease recovery) feature branch into master.

What changes were proposed in this pull request?
Support HSync and lease recovery required for HBASE. This feature is to make HBASE works using Ozone.
More details about this feature is attached in design doc mentioned in HDDS-7593.
Below are the conflicts:
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/audit/OMAction.java
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/request/key/OMKeyCommitRequest.java
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/request/key/OMDirectoriesPurgeRequestWithFSO.java
hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/keyvalue/impl/BlockManagerImpl.java

Above conflicts are due to HDDS-11194, HDDS-10658, HDDS-11215, HDDS-11259
Vote for merge is OPEN. We will proceed for merge once we get sufficient number of votes.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-10733
How was this patch tested?
Unit/Integration tests are added for every change.
CI: https://github.com/ashishkumar50/ozone/actions/runs/10141629794/workflow

Hi @ashishkumar50 please rebase the merge. We added a few commits in the HDDS-7593 branch. Thanks!

Thanks @ashishkumar50 for the PR.
Also a gentle reminder that one should use git push CLI to complete this merge when this is approved.
"Squash and merge" button below must NOT be used.

Hi @ashishkumar50 please rebase the merge. We added a few commits in the HDDS-7593 branch. Thanks!

Rebased the latest commits from HDDS-7593 branch.
One new simple conflict in:
hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/keyvalue/impl/BlockManagerImpl.java

@adoroszlai, Thanks for the review. This PR has only commits from HDDS-7593 branch.
The above related to "test case" was just for checking test flakiness. But at the end it is same as HDDS-7593 branch.
And the one related to "HBASE_SUPPORT" commit also it is same as feature branch.

This PR has only commits from HDDS-7593 branch

@ashishkumar50 Not really:
$ git log --oneline origin/HDDS-7593.. | head
a32b4d0e4d Update enum name to use HBASE_SUPPORT, as this is also used now by finalizeBlock
bb94b50ba9 Rebase latest commits from HDDS-7593 branch
fbe434bf48 Update test case
304c9f836d Merge remote-tracking branch 'upstream/HDDS-7593' into HDDS-10733
89a0b5cc92 Fix test case
3257e9cc06 Update test case
717df1d674 HDDS-10733. Merge HDDS-7593 related to hsync and lease recovery feature branch into master.
...

Closing this one, Opened a new PR for review.


Issues due to the tracepoint size fields

Since the tracetools_benchmark and tracetools_image_pipeline packages from robotperf/benchmarks and ros-acceleration/image_pipeline respectively have been modified to include two new fields, some files need to be updated in acceleration_examples packages

PR in #Issue22


Heroku instance is sometimes slow

I know for a fact that Heroku's free account might sleep if there's no activity.
I extensively using this https://cors-anywhere.herokuapp.com/, in my project, but sometimes the response of the Heroku instance is too slow which possibly due to startup time. Can you guys confirm which instance/dyno type you use in this Heroku instance https://cors-anywhere.herokuapp.com/?

I don't have a slow startup because the service is too popular. It's running 24/7.

Thank you for your answer @Rob--W, I know your service is popular, but I might be 1% minority here, I found out that it sometimes slow to load, about  30 seconds to 1 minute. Not sure if it's coming from the cors-anywhere or the service I'm trying to access which is the TinyUrl, which is popular as well.
Just so you know, I set up a NewRelic synthetic just now to ping the service if it's up 99.99%.

The service is too popular. Sometimes the public demo cannot keep up with the demand.


HDH AUTH TEST  - adding netlify function

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

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

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://662bb7a64d7ac9ded11f1dcd--harness-developer.netlify.app

GET https://662bb7a64d7ac9ded11f1dcd--harness-developer.netlify.app/api/hello

POST https://662bb7a64d7ac9ded11f1dcd--harness-developer.netlify.app/api/auth {
acccount_id,token
}


Postgres support

[x] SQHExecuteCommand
[x] SQHExecute
[x] SQHExecuteFile
[x] SQHShowDatabases
[x] Support in SQHDatabase, SQHTable, SQHResult

https://github.com/joereynolds/SQHell.vim/commit/0afe0e59b35cb14e8ec4aa975886277a0ad64928