[Question] Test Assembly lifecycle in VS Test Task

Required Information
Question, Bug, or Feature?
Type: Question
Enter Task Name: Visual Studio Test
Environment

Server - TFS on-premises

If using TFS on-premises, provide the version: 16.131.28507.4

Agent - Private

Windows 10, Agent v2.148.2

Issue Description
We are using Selenium with MSTest unit test projects and run them with the Visual STudio Test task in on-prem TFS. We face some problems with web driver instances (those which are known resp. common in the community). In order to face some of them, we need some more information:

Is there a possibility to write message directly from a unit test to the log of the VS Test task, and so to the TFS release log?
How is the lifecycle of aa test assembly managed? Is a test assembly loaded per agent once a release executes a test task? Or is the test assembly loaded per test batch? To give some context: we try to reuse web drivers and to shut them down when the assembly is unloaded (resp the method marked with the AssemblyCleanup attribute is called). For troubleshooting it is important for us to know the lifecycle.

Regarding both questions, please see the code below:

We like to see the messages written to the console in the TFS release log of each release.
Many thanks for help and tips in advance!

Hi,

For a failed test case, the console output will be available as a test case attachment. But for passed tests, we do not have any such feature.
The assembly will be loaded for every batch.

Hi @kaadhina!
Great, many thx for your response!

Yes, so far so good. Known and clear.
Thx, helpful.

So there is absolutely no way to write to the log from own code?

I guess you can write to a file and upload it using https://docs.microsoft.com/en-us/dotnet/api/microsoft.visualstudio.testtools.unittesting.testcontext.addresultfile?view=mstest-net-1.2.0
I haven't tried this myself. But I think this should work.

Yes, at least we can do this. Had that in mind already. So, many thanks again. Your answers were more helpful than those from the developer community this time.


[WIP] Documentation for computetools.py

Pull Request
Description
Add docstrings to computetools.py, including all four classes within it.
This pull request addresses #54

[x] make sure you are pulling from a dev branch on your fork
[x] check for code linting

In the PoissonSolver solve() method, what's would the argument sources look like (i.e. datatype and typical structure)?
I'm trying to figure out how the method works so I can document it properly, but I can't tell what sources is supposed to be.

@OwenGrannis we are going to close this PR and delete the dev-documentation branch here. We are switching policy to branch off main to develop documentation. Please resubmit the PR to pull into main.

@padamson: I was able to change this to point to main.
@OwenGrannis: How close are you being done with this PR? We discussed this morning that we should probably take the approach of doing "small" PRs that can be completed in ~day, rather than working on one huge PR.

There were some things that aren't done, but on the whole, they can be separate tasks (like documentation for the FiniteDifference class), and all of those have been noted with TODO. I think it's fine to merge it in now.


FIX : print full channels present in forward ie don't exclude bads

LGTM. We could consider printing the number of bads but it's probably not worth making the repr longer

bads is a concept unrelated with the forward computation. I don't think we should print bads.

[Current coverage][cc-pull] is 86.26%

Merging [#3325][cc-pull] into [master][cc-base-branch] will increase coverage by <.01%

@@             master      #3325   diff @@
==========================================
  Files           336        336
  Lines         57353      57356     +3
  Methods           0          0
  Messages          0          0
  Branches       8721       8721
==========================================
+ Hits          49473      49476     +3
  Misses         5215       5215
  Partials       2665       2665

[][cc-pull]

Powered by Codecov. Last updated by [ef18316...4faffd9][cc-compare]
[cc-base-branch]: https://codecov.io/gh/mne-tools/mne-python/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/mne-tools/mne-python/compare/ef1831679b0829518a5b889ccb74ac899ffba517...4faffd929aea075c217408f51baf6cc15882eb35
[cc-pull]: https://codecov.io/gh/mne-tools/mne-python/pull/3325?src=pr

Thanks @agramfort


Documentation incomplete

This documentation is missing many steps. It states to "create external table" but provides no links or guidance for how to do so. It also misses steps for setting up an external data source and external file format. (unless I am mistaken then please advise but I believe this is required)
I followed the steps exactly and got an error.
The steps I needed to do were

Create external data source to the dataverse lake database
Create external file format
Create external table
Create view

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

ID: f56503e8-3781-b603-8960-d99dccf2d023
Version Independent ID: f56503e8-3781-b603-8960-d99dccf2d023
Content: Create a view of your Azure Synapse Link for Dataverse data - Power Apps
Content Source: powerapps-docs/maker/data-platform/azure-synapse-link-create-view.md
Service: powerapps
Sub-service: dataverse-maker
GitHub Login: @sabinn-msft
Microsoft Alias: matp

Thanks for your comment, @bonomo1. This issue has been assigned to the doc author for review.

Thank you. I worked with it some more and believe the documentation should just remove the part about the external table. I was able to do a cross database query as started in the part about creating a view. What confused me was the part about creating an external table. I don't believe that is necessary?


cppclean thinks a forward declaration is not used

cppclean prints the following warning:
cppclean_test.h:7: 'A' not used

for the sample cppclean_test.h below:
// A function template
template<class T> void foo();

// This forward declaration really is used in the full specialization
// below, but cppclean thinks it is not.  The code will not compile
// without it.
class A;

// A full specialization of foo declared before A.
template<>
void foo<A>();

// Actual class definition.
class A {};

It's not a crash so I don't think it counts as a bug, just a warning that I have to ignore a lot, as I use a framework that makes extensive use of this pattern.

Should the title refer to "forward declaration" rather than "typedef"?

Yes, you're right of course!

Thanks for the bug report. This should be fixed by my last commit.


chore: Merge with upstream @ v1.5.7

Merge with upstream @ v1.5.7

Wrong repo. This pull should be a pull into seedlingo-en


corrected POM dependencies

GroupId with hyphen is not allowed (https://docs.oracle.com/javase/tutorial/java/package/namingpkgs.html). Also i think there would confusion to leave Java out from artifact name.

Thank you, mixed this with package names.


[Automation] Generate Fluent Lite from TypeSpec standbypool

[Automation] Generate Fluent Lite from TypeSpec standbypool

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

I am adding a live test in PR https://github.com/Azure/azure-sdk-for-java/pull/42019

close as wrong sdk version


Add ZSTD Compression Option

Allows us to experiment with different compressors, modeled after lz4_file

Nice! Zstd is impressive and a good default for anything internal, this will definitely aid adoption. Cargo.lock had a lot of churn including some dependency downgrades, it might be a good idea to try to clean that up before merging. Given that this is used as a library, I'm honestly not clear on why Cargo.lock is checked into the repo in the first place...

Yeah, why is it checked in?? And also, I am totally confused how I wound up changing so many seeming unrelated things in the Cargo.lock file here.

Cargo.lock is checked in so that we use consistent crate versions in the CI. The versions in there do not matter for extrernal crates.

Cargo.lock is checked in so that we use consistent crate versions in the CI. The versions in there do not matter for extrernal crates.

That makes a lot of sense.  What doesn't make a lot of sense is how I apparently did not pull from master prior to starting on this PR, and that created a bunch of unnecessary churn, fixing that now...

And I bjorked this PR pretty badly - back in the day I didn't have access to this repo, so I forked it, didn't realize I was pulling from that outdated fork when "updating" master, and lots of unnecessary churn as a result.
Closing in favor of: https://github.com/martian-lang/martian-rust/pull/343 - time to start fresh


resolve undefined name array_ops

flake8 testing of https://github.com/tensorflow/tensorflow on Python 2.7.14
$ flake8 . --count --select=E901,E999,F821,F822,F823 --show-source --statistics
./tensorflow/contrib/framework/python/ops/accumulate_n_v2.py:94:12: F821 undefined name 'array_ops'
    return array_ops.identity(inputs[0], name=name)
           ^

@rmlarsen Could I please get reviewers assigned to https://github.com/tensorflow/tensorflow/pulls/cclauss  They should not take long to evaluate.


build(docker): Allows sharing of network

See #16936 for details

Merged changes from https://github.com/freeCodeCamp/freeCodeCamp/pull/16825, good to review when you have time. /cc @Bouncey

@Bouncey ready for re-review 😄

AFAICT to get mailhog to function we'll need to add a datasources file for docker, or make changes to datasources.development to use mailhog instead of localhost.
Before I make those changes (far outside of the scope of this original PR), do you have any preference? I'm erring on staying with datasources.development, adding some complexity to it, but I still believe in a bright future where all the things are neatly containerised.

@raisedadead why is the blocked for Beta? Because PR work is a constrained resource?

Hi @ojongerius can you take a minute to squash this? I am having trouble pulling the PR. Sorry I just happened to switch machines and dont have my usual dotfiles to rescue me.

Fixed.

Hi @ojongerius I have rebased / sqashed this PR (don't worry the descriptions are in there).
You should just delete you local branch for this PR and then fetch and checkout.
One minor change and we are good to go!

@raisedadead thanks for squashing and the suggestion to simplify!


browse/exploration-oriented views of projects?

Aside from the list of most-recently-added projects, I couldn't find a non-search interface. Apologies if I've just missed it.
I think browse/exploration-oriented views could add a lot of value for people who might be looking for projects to help. I think there are at least two main components to this:

A search-oriented interface entails knowing what I want to do already, but aside from searching for certain languages/dependencies, I'm not sure how many people will be able to find a project that really sparks their own interest by searching?
I hesitate on this, because it might discourage people from joining the smallest projects, and I'm not certain if prospective maintainers would actually care, but I can at least imagine that project statistics highlighting which projects are generating the most demand for maintenance might help direct effort towards need? (I'd hesitate to just privilege starts or forks, but some good metrics might be: the number of open issues/PRs, the number of issues/PRs opened since the last release, the total number of comments or unique commenters since the last release, and--of course--the number of people that have directly marked interest via adoptoposs in finding maintainers?

Hey @abathur, thanks for opening this issue.
I think you are raising some valid points!
Regarding 1.:
Currently the only exploration-oriented view is a personal dashboard for logged in users, where you can subscribe to and apply quick filters for languages that you are interested in. So, if logged in, you’ll be presented with the respective most recent submitted projects on the landing page.
The second "exploration"-oriented feature is the projects newslettter/digest you can subscribe to (which will show projects from your subscribed languages, so basically the same as the dashboard, but via email).
Maybe the subscription feature is not communicated well enough at the moment and users could need some further guidance to explore projects in general? Better feature description on landing page, etc.
Besides, I’m also not too happy with the current ability to explore projects. Especially on the search page –as you said– you might feel a bit lost, if you have no clear goal. So some exploration-oriented views would definitely make sense from my point of view.
Maybe as a rather quick improvement we could have a logged-out version of the logged-in landing page, where you could filter by available languages. Maybe some statistics & metrics would also be nice here, which boils down to your second point.
We are also currently thinking about how to enhance the search/project tagging, e.g. by introducing free-form tags. That would allow to check for more specific interest. I’ll write down a some related thoughts in a separate issue over the next couple of days.
Regarding 2.:
I really like the idea to somehow indicate the demand for maintenance. That could be an important hint of what impact it would have if I decided to help this or that project.
In order to direct effort towards need, I’m wondering if it would also help to guide and allow maintainers to formulate their specific needs – beyond the free-form text description that a project currently has.
I’ll further think about the metrics you proposed. The last one (people who marked interest in finding maintainers references #79, right?)
@abathur would you like to be involved in the development of the mentioned ideas? Any help is always appreciated :pray:
Also @co0lsky & @floriank: feel free to add any comments, thoughts and ideas you might have here.

The last one (people who marked interest in finding maintainers references #79, right?)

Yep!

@abathur would you like to be involved in the development of the mentioned ideas? Any help is always appreciated 🙏

I think this is good work for the ecosystem and would love to pitch in, but I'm juggling a small army of ever-closer-to-release projects and a several-year-long yak shave that I am desperate to get finished off this year. Taking a little time to write up some thoughts is sort of the most-and-least I feel like I can do at the moment. I don't want to rule it out in the longer run, but in the short term at least I don't think I can go beyond feedback and spreading word of mouth.

For the first part, we just launched a brand new explore page: https://adoptoposs.org/explore. :rocket:  :tada:

@paulgoetze This is great!


Add icons for RiotJS tags, .ko files, VimL files, and Bash profiles

This PR addresses two issues (#285 and #276), as well as a few other things:

VimL files (including .vimrc) now display the Vim icon
Bash profiles and bashrc files without dots now display the shell icon properly

lgtm thanks


Does not build with Xcode 12

Maybe also older versions of Xcode but 12 is what I'm using and getting this result after executing GenerateXMPToolkitSDK_mac.sh:
Check dependencies
No architectures to compile for (ONLY_ACTIVE_ARCH=YES, active arch=arm64, VALID_ARCHS=arm64 arm64e i386 x86_64, EXCLUDED_ARCHS=(
arm64,
arm64e
)).
** BUILD FAILED **
Not really sure why it would assume active arch=arm64 as it is on an Intel Mac running macOS 10.15.6
And admittedly I'm not an expert cmake user

Currently, we are supporting Xcode 10.2. Let us know if you face any issues with it.

To add support for arm64, we need to use XCode 12. Why would we not consider adding support?


fix(versions): update Activiti/activiti-cloud-gateway versions into master

UpdateBot pushed helm dependency: common to: 1.1.19

UpdateBot commands:
updatebot push-version --kind helm common 1.1.19


[windows][build] pass the /debug flag to the linker

when building with debug information enabled
This ensures that every executable and dll get a corresponding PDB file with the debug information.

@swift-ci please test

@swift-ci please build toolchain


[Failing Test]: RowCoderTest.test_batch_encode_decode failure: setting an array element with a sequence. The requested array has an inhomogeneous shape after 1 dimensions.

What happened?
 The requested array has an inhomogeneous shape after 1 dimensions. The detected shape was (3,) + inhomogeneous part.

apache_beam/coders/row_coder_test.py:419: ValueError

I'm guessing that this is due to the numpy version: 1.24.2. This is running the Python test suite on beam version v2.45.0.
Issue Failure
Failure: Test is continually failing
Issue Priority
Priority: 1 (unhealthy code / failing or flaky postcommit so we cannot be sure the product is healthy)
Issue Components

[X] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

Thanks for reporting the issue. I am not seeing this test failing at master:
https://ci-beam.apache.org/job/beam_PreCommit_Python_Cron/
https://github.com/apache/beam/actions/workflows/python_tests.yml
Note that Beam  2.45.0 is not compatible with numpy==1.24.2. You should use Beam 2.46.0 or newer, see:
https://github.com/apache/beam/blob/fef98f7597f11aaa93388d547f58bf0482ed74f0/sdks/python/setup.py#L249 and https://github.com/apache/beam/pull/24725.
Given the above, I am closing this issue, but feel free to reopen if you disagree with my assessment.

Ah gotcha, thanks @tvalentyn !


URL "http://inshare.herokuapp.com/" does not exist.

The above used URL does not exist,
so if there is any other option for database server let me know.,

You can host it locally as well in the meantime
I'll try to put it back somewhere

Thank you for your response..
On Sun, 5 Dec, 2021, 10:03 PM Shivam, @.***> wrote:

You can host it locally as well in the meantime
I'll try to put it back somewhere
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ShivamJoker/InShare/issues/7#issuecomment-986261118,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWAB3TCGB5YRCU5SJWEZBATUPOH4VANCNFSM5JMK6JOA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Allowing the user to choose shifts directly or asssing them to offspring

Allow the admin to choose between:

Customers choosing shifts themselves (no offspring)
Offspring being assigned to shifts (no parents)
Both

And configuring it in the environment, the configuration does not need to be dynamic, but has to be documented

This should be done changing the way assignments are done. Currently they are related to offspring, so either a new type of offspring (self) is used, or a change in assignments is done.


Storage write streams should be able to use a pre-existing uri

Allow users to pass through an already existing uri when creating a write stream.
// create resumable url
file.createResumableUpload((err, uri) =>  {
    // hang on to uri somehow
});

// create a new stream with the same uri
const config = { uri };
bucket.file('zebra.jpg').createWriteStream(config);

PR with the enhancement coming shortly!

Fixed in https://github.com/GoogleCloudPlatform/gcloud-node/commit/3d6fa8a164c7307c6d62197e69ac3adde37037bf.


nixos-rebuild: add --no-ssh-tty flag

Description of changes
This closes #336967 by adding a --no-ssh-tty flag to nixos-rebuild.sh.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

@roberth Haha, I never thought of that! But I took a look at other options and it seems to be the convention to put no at front. Maybe we'll just keep it that way?

Alright! Thank you for making nixos-rebuild conditionally less ssh-tty :rocket:


Compiler redefines .call in thread-safe way

Summary
Redefine component's call method in a thread-safe way, by making Compiler acquire a lock (Monitor), per each component class.
fixes https://github.com/github/view_component/issues/869

I've added your suggestions. Thanks a lot!
I've removed the lock from render_template_for and I will see what the tests say.


Only index kept records in ES

What:

Only index kept Invoice records in ES

Why:

So that discarded once don't show up accidentally

@shalapatil can you add specs for this?
@supriya3105 any concerns?


Add indicators and test data

Adding Scheff Trend Cycle indicator
Manually copy data from tradeview charts. Testing data round to 2 decimal places
Adding Stoch RSI indicator, percentage volume oscillator, percentage price oscillator

Congratulations on your work @lit26
Let me know when the pull request is ready for revision!
Best,
Dario

Sure, you can review the previous commit.
Best,
Tianning

Hey @lit26 ,
Sorry for the delay. I am reviewing the PR, and I have a question:
What is the origin of ta/tests/data/cs-stc.csv? We will need more rows in the file to test the results correctly.
Best,
Dario

I copy the data from tradeview.com.

Hey @lit26 ,
Your work was included in the 0.5.26 version of the library.
Thank you so much for your collaboration!
Best,
Dario


Fix exception when an error message is returned from Alexa

Proposed changes
When the Alexa service returns an error message, Jovo throws an exception because the error request object doesn't have the getSessionAttributes method. This change adds a check for that method before calling it.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My code follows the code style of this project
[ ] My change requires a change to the documentation
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] All new and existing tests passed

I'll clean this up tonight and move the second commit to its own pull request.
For some background, these are both issues that show up when trying to send different animations to different buttons.


Update Zombieverse Pass data

Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:

Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.

Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.

Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.

Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.

No other tokens shares the same name, symbol or address.

For example, this change would be rejected due to unrelated changes:

The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.

I did such a rookie mistake and added the wrong mint address, also the path to the logo.
This PR:

Add the correct token mint address
Fix path to the Zombieverse logo

To speed up the review process, I'm adding the link of the original PR made by me: https://github.com/solana-labs/token-list/pull/15403
I added the Zombieverse token in this PR. Thanks in advance


Motion UI - Docs

Hi All,
I have looked through motion ui and love it, however installation was too bad. However my issue is with the documentation or lack of.
In this ticket I found out that I was calling foundation incorrectly https://github.com/zurb/foundation-sites/issues/7849. However looking through the docs this did not seem obvious that this was how you initiate Motion UI.
What I am trying to do:
As I am using Wordpress queries which return a list of data, I want a incremental delay across the page as you scroll down. I understand that I need trigger form the JS to initiate the Motion UI library.
Aim:
I ideally want to use data attributes to animate / transition them in.
Are there any examples, such as a Codepen with default classes or customisable SCSS settings?

I'm working on a tutorial to show how you can integrate WOW.js and Motion UI to do "animate on scroll". It'll be done by the end of the week. In the mean time, check out this CodePen to see a working example.
Here's a basic summary:

Add WOW.js to your project.
Make an animation class using the mui-animation() mixin. Motion UI only has four built-in animation classes, so you'll need to make your own. Refer to the docs here.
Also add animation-duration to the class so it functions properly.
Add the class, along with the class .wow to an element.
Initialize WOW.
Profit!


Adds setup for google-codelab-survey

This might slightly overlap Luke's PR, mainly the suggestion Alex make on tools/defs.bzl

I'm a Google employee, added my Google email to my account<EMAIL_ADDRESS>


unplugin-vue-define-options esbuild  Cannot read properties of undefined

Describe the bug

"esbuild": "^0.13.15",
"unplugin": "^0.9.2",
"unplugin-vue": "^0.2.2",
"unplugin-vue-define-options": "^0.10.0",
Reproduction
cant
System Info
System:
    OS: Windows 10 10.0.19044
    CPU: (12) x64 11th Gen Intel(R) Core(TM) i5-11400F @ 2.60GHz
    Memory: 4.39 GB / 15.86 GB
  Binaries:
    Node: 16.16.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 8.11.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (104.0.1293.54), ChromiumDev (Hey friend

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

please provide reproduction repo
https://antfu.me/posts/why-reproductions-are-required-zh

reproduction https://github.com/nextjm/unplugin-vue-define-options-esbuild-demo  @sxzz

@nextjm Please upgrade your esbuild to the latest version.
By the way, you still need esbuild-plugin-transform, since there's no transform stage in esbuild https://github.com/evanw/esbuild/issues/1902
import { Transform } from 'esbuild-plugin-transform'
// ...
    plugins: [
      Transform({
        plugins: [
          DefineOptions(),
          vue({
            sourceMap: false,
            style: {
              preprocessLang: 'less',
              preprocessOptions: {
                less: {
                  javascriptEnabled: true,
                  additionalData: `@import '${process.cwd()}/packages/styles/index.less'`,
                },
              },
            },
          }),
        ],
      }),
    ],


Add Image Shrinker

App: Image Shrinker
Description:
Minify your images and graphics with just one drop. Autorenamed in the same place where it comes from. Immediately
Website: https://image-shrinker.com
Screenshot:

Nice work! Looks like a useful app.


Verify the content spelling and grammar of the 'Assistant Manager' job page

Description: You must ensure that all written content on the 'Assistant Manager' job page is free from spelling and grammatical errors.
Preconditions: The website  is live and accessible.

Step 1: Go to 'Cum poți ajuta tu?' section and click on the 'Assistant Manager' job.
Expected Result: The job page loads successfully.

Step 2: Review the job's header for spelling and grammatical errors.
Expected Result: No spelling or grammatical errors in the job's header.

Step 3: Review the job's description text for spelling and grammatical errors.
Expected Result: No spelling or grammatical errors in the job's description.

Step 4: Review the contact information section for spelling and grammatical errors.
Expected Result: No spelling or grammatical errors in the contact information section.

Step 5: Check if the 'Aplica' button text is written correctly.
Expected Result: The 'Aplica' button text is spelled correctly.

Step 6: Check if the 'Inapoi la locurile de munca' button text is written correctly.
Expected Result: The 'Inapoi la locurile de munca'' button text is spelled correctly.

Tested on:
Leptotp
Ios: Windows 10
Browser : Chrome, Modzilla, Edge, Opera.
Mobile:
Android Samsung S8+ on Samsung Internet


Manual triggers

Looking at sem cli tool it currently supports one-off jobs, but there is no way to trigger a workflow in a different project. The use-case would be releasing a new package version and triggering a build in another package that would use the newly released version to test compatibility. Or triggering end-to-end tests that are stored in a different repo.
This would also be useful for release pipelines that could be manually triggered and from the UI as well.

guess there's a way now -> https://docs.semaphoreci.com/reference/sem-command-line-tool/#creating-one-off-jobs


some bugs about the code

some adaptation is needed for code downloaded. Otherwise, it will generate errors. (Actually we can change the output file also but I simply change the code downloaded)

for Evaluation/bleu/bleu.py line22 assert(list(gts.keys()) == list(res.keys())) should be changed to
assert(sorted(gts.keys()) == sorted(res.keys()))
for Evaluation/rouge/rouge.py line85 assert(list(gts.keys()) == list(res.keys())) should be changed to
assert(sorted(gts.keys()) == sorted(res.keys()))
for Evaluation/ms_marco_eval.py line 132 133
precision = true_positives/(true_positives+false_positives)
recall = true_positives/(true_positives+false_negatives)
should be changed to
precision = float(true_positives)/(true_positives+false_positives) if (true_positives+false_positives)>0 else 1.
recall = float(true_positives)/(true_positives+false_negatives) if (true_positives+false_negatives)>0 else 1.
in case divide zero

Hi @javacjh,
Do u encounter this error?

Thanks for the keen eye. Ive updated eval scripts with this input.

@ChinHui-Chen please open another issue focused on baseline errors describing your setup, what commands you are running and I'll take a look

Hi there:
I only run the code in evaluation so I don't know what happen to other
code. So far I have coded with tensorflow, so I am not so familiar with
torch.
Based on the information you provided, the error occur at line 154 of
train.py. You may check whether it's typo about queries or the problem
about the format of queries variable.
Best,
Jiahua
On Thu, May 31, 2018 at 11:47 AM, Chin-Hui (Johnson) <
<EMAIL_ADDRESS>wrote:

Hi @javacjh https://github.com/javacjh,
Do u encounter this error?
[image: image]
https://user-images.githubusercontent.com/625355/40792579-df6d32fa-652c-11e8-9c55-d90cd70de680.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dfcf93/MSMARCOV2/issues/2#issuecomment-393576364, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AVCjPlMNkRuAv6Zk2NuT2jOPf0-wYZNcks5t4BB8gaJpZM4UP32M
.


White list default http headers for logging

Refer to the headers added here, we need to white list the same set for Java logging.

We should get this snuck in ahead of GA
https://github.com/Azure/azure-sdk-for-net/pull/8166/files

(tagging as blocking-release for Preview 5 solely for bug tracking on the query; not that I would actually block Preview 5 for this change if it doesn't make it in time)

Closed in #5893


Fix MariaDB persistance documentation

Fixes #26

Changed from mariadb.persistence.enabled to mariadb.master.persistence.enabled
Added rootUser parameter
Added information to support upgrades
Added titles to group parameters
Fix some typos in the documentation

Hey all, I have donated this chart to the folks over at Gitea who have been doing an amazing job maintaining and updating the chart so it is up to date. Please open up any issues here: https://gitea.com/gitea/helm-chart and try theirs own!
Many thanks for all who've contributed.


Update polkadot-chains.ts

Changed display name of "Statemint" to "Polkadot Asset Hub".
Updated icon to Polkadot Asset Hub chain icon svg.
Hopefully this helps towards this issue: https://github.com/galacticcouncil/apps/issues/62
Please sers the normies don't know what Statemint is anymore 😩

Yaaas.


HBASE-24681 Remove the cache walsById/walsByIdRecoveredQueues from Re…

…plicationSourceManager

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 29s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ HBASE-24666 Compile Tests _

+1 :green_heart:
mvninstall
3m 47s
HBASE-24666 passed

+1 :green_heart:
checkstyle
1m  8s
HBASE-24666 passed

+1 :green_heart:
spotbugs
1m 59s
HBASE-24666 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 21s
the patch passed

-0 :warning:
checkstyle
1m  2s
hbase-server: The patch generated 1 new + 3 unchanged - 0 fixed = 4 total (was 3)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
11m 10s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
2m  6s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 15s
The patch does not generate ASF License warnings.

32m 24s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2019

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 91cf0d917179 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-24666 / fe2ae809d1

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

Max. process+thread count
94 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 30s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ HBASE-24666 Compile Tests _

+1 :green_heart:
mvninstall
4m 19s
HBASE-24666 passed

+1 :green_heart:
compile
1m  4s
HBASE-24666 passed

+1 :green_heart:
shadedjars
5m 51s
branch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 44s
hbase-server in HBASE-24666 failed.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 59s
the patch passed

+1 :green_heart:
compile
1m  3s
the patch passed

+1 :green_heart:
javac
1m  3s
the patch passed

+1 :green_heart:
shadedjars
5m 44s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 40s
hbase-server in the patch failed.

_ Other Tests _

-1 :x:
unit
136m 11s
hbase-server in the patch failed.

162m 18s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2019

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 24549fb1185f 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-24666 / fe2ae809d1

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/1/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/1/testReport/

Max. process+thread count
4761 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 26s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ HBASE-24666 Compile Tests _

+1 :green_heart:
mvninstall
4m  2s
HBASE-24666 passed

+1 :green_heart:
compile
0m 57s
HBASE-24666 passed

+1 :green_heart:
shadedjars
5m 59s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 36s
HBASE-24666 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 42s
the patch passed

+1 :green_heart:
compile
0m 58s
the patch passed

+1 :green_heart:
javac
0m 58s
the patch passed

+1 :green_heart:
shadedjars
6m  1s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 36s
hbase-server generated 7 new + 28 unchanged - 0 fixed = 35 total (was 28)

_ Other Tests _

-1 :x:
unit
205m 21s
hbase-server in the patch failed.

230m 25s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2019

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 5464af8faf74 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-24666 / fe2ae809d1

Default Java
1.8.0_232

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/1/artifact/yetus-jdk8-hadoop3-check/output/diff-javadoc-javadoc-hbase-server.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/1/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/1/testReport/

Max. process+thread count
3916 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 37s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ HBASE-24666 Compile Tests _

+1 :green_heart:
mvninstall
3m 34s
HBASE-24666 passed

+1 :green_heart:
checkstyle
1m  7s
HBASE-24666 passed

+1 :green_heart:
spotbugs
2m  2s
HBASE-24666 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 21s
the patch passed

+1 :green_heart:
checkstyle
1m  4s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
11m  9s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
2m 40s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 17s
The patch does not generate ASF License warnings.

35m  5s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2019

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 07fea145f23d 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-24666 / c2949719c5

Max. process+thread count
94 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/2/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 37s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ HBASE-24666 Compile Tests _

+1 :green_heart:
mvninstall
3m 48s
HBASE-24666 passed

+1 :green_heart:
compile
0m 55s
HBASE-24666 passed

+1 :green_heart:
shadedjars
5m 41s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 40s
HBASE-24666 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 24s
the patch passed

+1 :green_heart:
compile
0m 56s
the patch passed

+1 :green_heart:
javac
0m 56s
the patch passed

+1 :green_heart:
shadedjars
5m 33s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 36s
hbase-server generated 7 new + 28 unchanged - 0 fixed = 35 total (was 28)

_ Other Tests _

+1 :green_heart:
unit
141m 35s
hbase-server in the patch passed.

165m 57s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/2/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2019

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux d9d40903c967 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-24666 / c2949719c5

Default Java
1.8.0_232

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/2/artifact/yetus-jdk8-hadoop3-check/output/diff-javadoc-javadoc-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/2/testReport/

Max. process+thread count
4710 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/2/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 47s
Docker mode activated.

-0 :warning:
yetus
0m  2s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ HBASE-24666 Compile Tests _

+1 :green_heart:
mvninstall
5m 15s
HBASE-24666 passed

+1 :green_heart:
compile
1m 15s
HBASE-24666 passed

+1 :green_heart:
shadedjars
6m 47s
branch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 46s
hbase-server in HBASE-24666 failed.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 55s
the patch passed

+1 :green_heart:
compile
1m 28s
the patch passed

+1 :green_heart:
javac
1m 28s
the patch passed

+1 :green_heart:
shadedjars
6m 58s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 45s
hbase-server in the patch failed.

_ Other Tests _

-1 :x:
unit
149m 42s
hbase-server in the patch failed.

180m 36s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2019

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 39aeeeb16c39 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-24666 / c2949719c5

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/2/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/2/testReport/

Max. process+thread count
4455 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/2/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 35s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ HBASE-24666 Compile Tests _

+1 :green_heart:
mvninstall
3m 36s
HBASE-24666 passed

+1 :green_heart:
checkstyle
1m  3s
HBASE-24666 passed

+1 :green_heart:
spotbugs
2m  0s
HBASE-24666 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 25s
the patch passed

+1 :green_heart:
checkstyle
1m  6s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
11m 31s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
2m 44s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 13s
The patch does not generate ASF License warnings.

35m 29s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/3/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2019

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 6ccdd6a84494 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-24666 / c2949719c5

Max. process+thread count
94 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/3/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 35s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ HBASE-24666 Compile Tests _

+1 :green_heart:
mvninstall
3m 34s
HBASE-24666 passed

+1 :green_heart:
compile
0m 56s
HBASE-24666 passed

+1 :green_heart:
shadedjars
5m 38s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 37s
HBASE-24666 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 29s
the patch passed

+1 :green_heart:
compile
0m 56s
the patch passed

+1 :green_heart:
javac
0m 56s
the patch passed

+1 :green_heart:
shadedjars
5m 34s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 35s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
142m 14s
hbase-server in the patch passed.

166m 16s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/3/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2019

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 0e1a963ab077 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-24666 / c2949719c5

Default Java
1.8.0_232

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/3/testReport/

Max. process+thread count
4384 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/3/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 34s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ HBASE-24666 Compile Tests _

+1 :green_heart:
mvninstall
4m 47s
HBASE-24666 passed

+1 :green_heart:
compile
1m 10s
HBASE-24666 passed

+1 :green_heart:
shadedjars
6m 51s
branch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 46s
hbase-server in HBASE-24666 failed.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 53s
the patch passed

+1 :green_heart:
compile
1m 12s
the patch passed

+1 :green_heart:
javac
1m 12s
the patch passed

+1 :green_heart:
shadedjars
6m 46s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 45s
hbase-server in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
224m 27s
hbase-server in the patch passed.

255m  7s

Subsystem
Report/Notes

Docker
Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/3/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2019

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 86581908c096 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-24666 / c2949719c5

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/3/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/3/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/3/testReport/

Max. process+thread count
2976 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2019/3/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

Yes. But I plan to implement it piece by piece and make sure all ut passed, it will be easy for review. Will finish the complete "decouple" in the follow on issues. Meanwhile, I will add a implementation plan section in the design doc. Thanks.


app crashes on android

Version
No response
Problem Area
react-native-pytorch-core (core package)
Steps to Reproduce
I am trying to run Image Classification model on Android. I had followed manual instructions for setup on linux machine. Everything is fine till the last step of installation and app gets succesfully installed on my android phone running android v9(Pie). But app crashes as soon as it is launched at start.
Expected Results
No response
Code example, screenshot, or link to repository
No response

Hi @yMayanand,
Would you please attach a crash log from the Metro logs and from adb logcat? I expect this would contain a stack trace and help to pinpoint the root issue.
Thanks!

@yMayanand, PyTorch Live supports Android 10+ (see README)

PyTorch Live apps may target Android 10.0 (API 21) and iOS 12.0 or newer.

It seems that the shared libraries for PyTorch Android (libpytorch_jni_lite) are missing. Can you check if the *.so are in the app-debug.apk?

Go to cd <PROJECT>/android/app/build/outputs/apk/debug
unzip app-debug.apk
Check if the lib folder for your device's architecture has the *.so files

e.g., cd <PROJECT>/android/app/build/outputs/apk/debug/lib/x86

The project is currently building for arm64-v8a, armeabi-v7a, x86, and x86_64.

@raedle My phones architecture is arm64-v8a and i had checked the folder
<PROJECT>/android/app/build/outputs/apk/debug/lib/arm64-v8a for *.so files. It has all the  *.so files and i  also looked for libpytorch_jni_lite file it had that too.

@yMayanand, does the app also crash on a device Android 10.0+ (API 21+)? If yes, would you be able to share the project in a repo?

@raedle  I am running on Android 11 and it crashes for me as well...

Here's the logcat of crash
03-29 16:14:56.279 18407 18407 W unknown:ReactNative: Packager connection already open, nooping.
03-29 16:14:56.315  1532  1709 I ActivityTaskManager: Displayed org.pytorch.live.example/.MainActivity: +739ms
03-29 16:14:56.320  1532  1692 D EventSequenceValidator: dec AccIntentStartedEvents to 1
03-29 16:14:56.508 18407 18460 D SoLoader: About to load: libhermes.so
03-29 16:14:56.508 18407 18460 D SoLoader: libhermes.so not found on /data/user/0/org.pytorch.live.example/lib-main
03-29 16:14:56.508 18407 18460 D SoLoader: libhermes.so found on /data/app/~~oQy-oOr9y0FDzYve7IgTEw==/org.pytorch.live.example-voXhERWr7pFbLgSsuzABsw==/lib/arm64
03-29 16:14:56.508 18407 18460 D SoLoader: Not resolving dependencies for libhermes.so
03-29 16:14:56.517 18407 18460 D SoLoader: Loaded: libhermes.so
03-29 16:14:56.517 18407 18460 D SoLoader: About to load: libhermes-executor-debug.so
03-29 16:14:56.518 18407 18460 D SoLoader: libhermes-executor-debug.so not found on /data/user/0/org.pytorch.live.example/lib-main
03-29 16:14:56.518 18407 18460 D SoLoader: libhermes-executor-debug.so found on /data/app/~~oQy-oOr9y0FDzYve7IgTEw==/org.pytorch.live.example-voXhERWr7pFbLgSsuzABsw==/lib/arm64
03-29 16:14:56.518 18407 18460 D SoLoader: Not resolving dependencies for libhermes-executor-debug.so
03-29 16:14:56.547 18407 18460 D SoLoader: Loaded: libhermes-executor-debug.so
03-29 16:14:56.568 18407 18460 E AndroidRuntime: FATAL EXCEPTION: create_react_context
03-29 16:14:56.568 18407 18460 E AndroidRuntime: Process: org.pytorch.live.example, PID: 18407
03-29 16:14:56.568 18407 18460 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "_ZN8facebook3jni12jtype_traitsIiE11kDescriptorE" referenced by "/data/app/~~oQy-oOr9y0FDzYve7IgTEw==/org.pytorch.live.example-voXhERWr7pFbLgSsuzABsw==/lib/arm64/libpytorch_jni_lite.so"...
03-29 16:14:56.568 18407 18460 E AndroidRuntime:        at java.lang.Runtime.loadLibrary0(Runtime.java:1087)
03-29 16:14:56.568 18407 18460 E AndroidRuntime:        at java.lang.Runtime.loadLibrary0(Runtime.java:1008)
03-29 16:14:56.568 18407 18460 E AndroidRuntime:        at java.lang.System.loadLibrary(System.java:1664)
03-29 16:14:56.568 18407 18460 E AndroidRuntime:        at org.pytorch.rn.core.jsi.PyTorchCoreJSIModule.<clinit>(PyTorchCoreJSIModule.java:25)
03-29 16:14:56.568 18407 18460 E AndroidRuntime:        at org.pytorch.rn.core.PyTorchCorePackage.createNativeModules(PyTorchCorePackage.java:30)
03-29 16:14:56.568 18407 18460 E AndroidRuntime:        at com.facebook.react.ReactPackageHelper.getNativeModuleIterator(ReactPackageHelper.java:42)
03-29 16:14:56.568 18407 18460 E AndroidRuntime:        at com.facebook.react.NativeModuleRegistryBuilder.processPackage(NativeModuleRegistryBuilder.java:42)
03-29 16:14:56.568 18407 18460 E AndroidRuntime:        at com.facebook.react.ReactInstanceManager.processPackage(ReactInstanceManager.java:1347)
03-29 16:14:56.568 18407 18460 E AndroidRuntime:        at com.facebook.react.ReactInstanceManager.processPackages(ReactInstanceManager.java:1318)
03-29 16:14:56.568 18407 18460 E AndroidRuntime:        at com.facebook.react.ReactInstanceManager.createReactContext(ReactInstanceManager.java:1240)
03-29 16:14:56.568 18407 18460 E AndroidRuntime:        at com.facebook.react.ReactInstanceManager.access$1100(ReactInstanceManager.java:131)
03-29 16:14:56.568 18407 18460 E AndroidRuntime:        at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:1023)
03-29 16:14:56.568 18407 18460 E AndroidRuntime:        at java.lang.Thread.run(Thread.java:923)
03-29 16:14:56.571  1532 18461 I DropBoxManagerService: add tag=data_app_crash isTagEnabled=true flags=0x2
03-29 16:14:56.571  1532  8668 W ActivityTaskManager:   Force finishing activity org.pytorch.live.example/.MainActivity
03-29 16:14:56.574  1532 18461 W DropBoxManagerService: Dropping: data_app_crash (1526 > 0 bytes)
03-29 16:14:56.578 18407 18460 I Process : Sending signal. PID: 18407 SIG: 9
03-29 16:14:56.580  1532  1710 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
03-29 16:14:56.581  1532  1710 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
03-29 16:14:56.630  1532  3795 I ActivityManager: Process org.pytorch.live.example (pid 18407) has died: prcp TOP

Just to be sure i confirmed if i have libpytorch_jni_lite.so file bundled
and it is present in the installed app

I have tried first option but the problem was not solved, i am eagerly waiting for next version
so that problem would get solved implicitly.


Besides paper summaries, will additional resources like data, courses, and blogs be added later

Hello, thank you for your sharing. Besides paper summaries, will additional resources like data, courses, and blogs be added later? I noticed they are listed in the table of contents, but the actual content is still empty for now.

The rendering of the repo is buggy due to the limited capabilities of github. Either look at the raw Readme.md or checkout the repo and read it locally. It is all there!


consume cypress test configuration from yaml file

https://issues.redhat.com/browse/RHOAIENG-9635
Description

Adds support for configuring test users and the e2e test cluster URL via a yaml file.
To align with the yaml file configured by QA, I've updated the env vars that can be supplied to the .env.cypress(.local) file as well.
How Has This Been Tested?

Create a yaml file:
ODH_DASHBOARD_URL: https://<odh url>
TEST_USER:
  AUTH_TYPE: htpasswd
  USERNAME: regularuser1
  PASSWORD: <password>
OCP_ADMIN_USER:
  AUTH_TYPE: htpasswd
  USERNAME: clusteradminuser1
  PASSWORD: <password>

Run the cypress e2e test:
CY_TEST_CONFIG=~/path/to/yaml/cy-testing.yml npm run cypress:run
Also, test the local configuration by updating frontend/.env.cypress.local to override the defaults from frontend/.env.cypress.
Then run npm run cypress:run
Note that for cypress config, the process.env can be used. But once the cypress tests are running, we need to use Cypress.env(...). Therefore we must set the data as part of the env property of the cypress config to be retrieved later with a cypress test.
Updated the visitWithLogin command to use the TEST_USER by default.
Test Impact

N/A
Part of testing infrastructure configuration for cypress e2e.
Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

cc @manosnoam @sthundat

cc @manosnoam @sthundat

I tested on Jenkins, it used the new env file CY_TEST_CONFIG, and its defined vars to access the RHOAI cluster.
/approve


same messages guard

SQS returns same messages sometime.
If sqs-notify has feature to ignore last received N messages,
we can limit command execution for a message.

実装は終わった。要テスト。

Done


The corner of CommandBarFlyout will no longer rounded when closing

Describe the bug
The corner of CommandBarFlyout will no longer rounded when closing
Steps to reproduce the bug

Create a new CommandBarFlyout without PrimaryCommand
Pop it

Expected behavior
Should have round corner
Screenshots

NuGet package version
Microsoft.UI.Xaml 2.5.0
Windows app type

[X] UWP
[ ] Win32

Device form factor
Desktop
Windows version
May 2021 Update (19043)
Additional context
No response

@zhuxb711 this issue appears to be fixed in the latest versions of winui2.


Add Number#positive? and #negative?

Summary
For example, when an array [-2, -1, 0, 1, 2] is given, I'd like to write
[-2, -1, 0, 1, 2].select(&.positive?)
[-2, -1, 0, 1, 2].select(&.negative?)

instead of
[-2, -1, 0, 1, 2].select { |i| i > 0 }
[-2, -1, 0, 1, 2].select { |i| i < 0 }

So I  want to add Number#positive? and #negative? like Ruby.

Duplicate of #6552

IMO it's sad they were rejected.

I probably wasn't around when this was rejected, but I think it's harmless to add those two methods, and they might be a bit more descriptive than { |x| x > 0 } or &.>(0).

I'll argue against bloating stdlib API, as such use-case isn't standard, and app specific functionality should be treated differently. IMHO stdlib does provide enough mechanism to extend and shouldn't be bloated to cater all use-cases needs. Just my two cents

Let's do it 👍


zoraxy: 3.0.7 -> 3.1.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/tobychui/zoraxy/releases.
meta.description for zoraxy is: General purpose HTTP reverse proxy and forwarding tool written in Go
meta.homepage for zoraxy is: https://zoraxy.arozos.com/
meta.changelog for zoraxy is: https://github.com/tobychui/zoraxy/blob/v3.0.8/CHANGELOG.md
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.0.8 with grep in /nix/store/2chayhr8393dbk4xl6vakxq9nfhxhzzy-zoraxy-3.0.8
found 3.0.8 in filename of file in /nix/store/2chayhr8393dbk4xl6vakxq9nfhxhzzy-zoraxy-3.0.8

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

zoraxy

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/5ebae4e210f994ba21bf86be8fc00b5d960592cc#zoraxy

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/2chayhr8393dbk4xl6vakxq9nfhxhzzy-zoraxy-3.0.8
ls -la /nix/store/2chayhr8393dbk4xl6vakxq9nfhxhzzy-zoraxy-3.0.8/bin

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

1 package built:

zoraxy

Maintainer pings
cc @luftmensch-luftmensch for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/tobychui/zoraxy/releases.
meta.description for zoraxy is: General purpose HTTP reverse proxy and forwarding tool written in Go
meta.homepage for zoraxy is: https://zoraxy.arozos.com/
meta.changelog for zoraxy is: https://github.com/tobychui/zoraxy/blob/v3.1.0/CHANGELOG.md
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.1.0 with grep in /nix/store/3rrddr0xh2lzsxmzw3j2378js47yrp3r-zoraxy-3.1.0
found 3.1.0 in filename of file in /nix/store/3rrddr0xh2lzsxmzw3j2378js47yrp3r-zoraxy-3.1.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

zoraxy

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/111b49d11c032e6026671c87dbbe9c1562d98c1e#zoraxy

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3rrddr0xh2lzsxmzw3j2378js47yrp3r-zoraxy-3.1.0
ls -la /nix/store/3rrddr0xh2lzsxmzw3j2378js47yrp3r-zoraxy-3.1.0/bin

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

1 package built:

zoraxy

Maintainer pings
cc @luftmensch-luftmensch for testing.

Result of nixpkgs-review pr 327416 run on x86_64-linux 1

1 package built:

zoraxy


Cheat sheet ...

This is a great package that I am trying to use to write a Soduko solver using Conor McBride's types:
   20 type Triple = Id :*: Id :*: Id
   21
   22 pattern Tr :: a -> a -> a -> (:*:) (Id :*: Id) Id a
   23
   24 pattern Tr a b c = (Id a :*: Id b) :*: Id c
   25
   26 type Row = Triple :. Triple
   27
   28 type Grid = Matrix Value
   29
   30 type Matrix = Row :. Row
   31
   32 type Value = Char
   33
   34 type Choices = [Value]

rather than lists + indexes.
Everything is easy, using functor-combo's Functor until I get to trying to implement a version of the Bird expand / expand1 functions, which use pattern matching for elegant simplicity.  For these I think that I need holes / derivatives (to test candidate solutions for a cell, aka guessing).  There seem to be two implementations of these concepts in functor-combo (DHoley, Derivative + Holey). Which should I be using?  Similarly, I assume that I will need some sort of Zipper, but it isn't obvious how to create these from the modules.  For example, in the ZipperFix case, Fix is not accessible to the user.
It would be helpful to expand the documentation to cover use cases (the blog is helpful for concepts / implementation of the package).
Many thanks!

Everything is easy, using functor-combo's Functor until I get to trying to implement a version of the Bird expand / expand1 functions, which use pattern matching for elegant simplicity.

Do you have a pointer to these functions? I just looked in Richard Bird's Soduko paper but didn't spot them.
I made the functor-combo package to support some experiments and blog posts, but now there's GHC.Generics. It may be worthwhile to port some functionality from functor-combo and then abandon it.

Hi Conal,
Here is Graham Hutton's rendering of the Bird approach: http://www.cs.nott.ac.uk/~pszgmh/sudoku.lhs
It can be refactored to use the types above quite easily, although there are some interesting cases, such as checking for duplicates.
The expand function is:
> expand                :: Matrix Choices -> [Matrix Choices]
> expand m              =
>    [rows1 ++ [row1 ++ [c] : row2] ++ rows2 | c <- cs]
>    where
>       (rows1,row:rows2) = break (any (not . single)) m
>       (row1,cs:row2)    = break (not . single) row

This can be further optimized to
expand1 :: Matrix Choices → [Matrix Choices]
expand1 rows = [rows1 ++ [row1 + [c] : row2] ++ rows2 | c ← cs]
  where( rows1,row:rows2) = break(any smallest) rows
             (row1,cs : row2)  = break smallest row
             smallest cs          = length cs ==  n
             n                           = minimum (counts rows)
counts = filter (/= 1) · map length · concat

expand = concat · map expand · expand 1

The initial parts of the problem illustrate the power and elegance of foldable / traversable / applicative, but a different model is needed when you need to do more than apply the same effect uniformly across the grid.
A further refinement uses a generalisation of the approach of pruning pairs used here.  It is described here https://wiki.haskell.org/Sudoku/Thorkil_Naur.  Links to an implementation of this approach can be found at https://wiki.haskell.org/Sudoku under the Generalized Solver section.
I have found this a good exercise because the problem is well-known and there are lots of model Haskell solutions around.  But most of them use lists and / or indexes (which is fine, but it feels a bit hand-crafted).  nextGrids here https://abhinavsarkar.net/posts/fast-sudoku-solver-in-haskell-1/ is another version of expand1 that illustrates the point. I feel that it ought to be possible to use Conor's Triple type as the basis of a more satisfying approach (or use it to provide insights into the limitations of the approach).
I'll have a look at GHC.Generics more closely.  I didn't spot the plumbing for holes and derivatives, the last time I looked (for other purposes).


Add documentation for new GCP pubsub reconnect loop configuration

Add documentation for new GCP pubsub reconnect loop configuration metadata properties (MaxReconnectionAttempts and ConnectionRecoveryInSec) added in https://github.com/dapr/components-contrib/pull/1293
The content can be copied from the Azure Service Bus component documentation here: https://github.com/dapr/docs/blob/v1.5/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-azure-servicebus.md?plain=1#L82

I merged #dapr/components-contrib#1293.
Please make the docs PR against release 1.7 to document the new metadata fields @yordan-pavlov

Resolved


set of advanced data API examples

@realmarcin I am going to merge this into my current docs branch and push it all up as a new PR
The goal is to get it all in develop so we can continue off the same code
Right now here are the conflicts I am seeing
CONFLICT (modify/delete): lib/doekbase/data_api/tests/examples/test_proteins_to_fasta.py deleted in HEAD and modified in marcin-examples/develop. Version marcin-examples/develop of lib/doekbase/data_api/tests/examples/test_proteins_to_fasta.py left in tree.
CONFLICT (modify/delete): lib/doekbase/data_api/tests/examples/proteins_to_fasta.py deleted in HEAD and modified in marcin-examples/develop. Version marcin-examples/develop of lib/doekbase/data_api/tests/examples/proteins_to_fasta.py left in tree.
Automatic merge failed; fix conflicts and then commit the result.

@realmarcin the other implication here is that you must merge all changes from develop into your fork once this PR is merged, before continuing

@realmarcin ok, it looks like the tests don't work yet so I aborted that effort and instead would ask you to merge kbase/develop into your branch, then please fix the tests. I also would really like you to put the tests all inside the appropriate _api.py file (annotation, taxon, assembly) and follow the same pattern I started for the other tests. If you really have ones that cross multiple APIs, though the ones I looked at didn't and by the design of the API they tend not to, I would suggest you put all those in a new genome.py (and test_genome.py) file.

I don't think this is relevant any more. It should all be merged up through the other docs branch, or otherwise out of date.