unused parameters in the empty.ts are causing TypeScript check errors

This empty.ts was auto generated from protobuf file "google/protobuf/empty.proto" (package "google.protobuf", syntax proto3)
the error is in the function internalBinaryRead

    internalBinaryRead(reader: IBinaryReader, length: number, options: BinaryReadOptions, target?: Empty): Empty {
        return target ?? this.create();
    }

if run script vue-tsc --noEmit --skipLibCheck
It will cause ts-check error
'reader' is declared but its value is never read.
'length' is declared but its value is never read.
'options' is declared but its value is never read.

It's not only in empty.ts. It's in any proto message without members. A solution would be to prefix unused variables with _.
Use-case: I've got multiple empty types because I expect to add members in the future.

https://github.com/timostamm/protobuf-ts/pull/609

As timostamm suggested there, generate proto with  --ts_opt ts_nocheck.

See the documentation here.
version: v1
plugins:
  - plugin: buf.build/community/timostamm-protobuf-ts:v2.9.1
    out: ./ts
    opt: ts_nocheck

For multiple plugin options, use:
version: v1
plugins:
  - plugin: ...
    out: ...
    opt:
      - ts_nocheck
      - other_option

opt: ts_nocheck

Many thanks, now it works!
empty.ts before
// @generated by protobuf-ts 2.9.1 with parameter ts_nocheck
// @generated from protobuf file "google/protobuf/empty.proto" (package "google.protobuf", syntax proto3)
// tslint:disable
......

empty.ts after
// @generated by protobuf-ts 2.9.1 with parameter ts_nocheck
// @generated from protobuf file "google/protobuf/empty.proto" (package "google.protobuf", syntax proto3)
// tslint:disable
// @ts-nocheck
......

and also thanks @danielvandenberg95   I think https://github.com/timostamm/protobuf-ts/pull/609. is a good PR


Checkpoint fingerprint mappings only upon shutdown

Before, we checkpointed after every newly detected fingerprint
collision, which is not a problem as long as collisions are
rare. However, with a sufficient number of metrics or particular
nature of the data set, there might be a lot of collisions, all to be
detected upon the first set of scrapes, and then the checkpointing
after each detection will take a quite long time (it's O(n²),
essentially).
Since we are rebuilding the fingerprint mapping during crash recovery,
the previous, very conservative approach didn't even buy us
anything. We only ever read from the checkpoint file after a clean
shutdown, so the only time we need to write the checkpoint file is
during a clean shutdown.
@fabxc @brian-brazil Fixes #1513

:+1:

👍

OK. Still need to look into #1550, and then we can release 0.18.0 (or 0.18rc2?)


Strict type checking of keys

Is your feature request related to a problem? Please describe.
let res = client.get(2020).consistent().run().await; // should be error 🔥

Why this problem is happen? Because IntoAttribute trait has lots of implementations. This means that it's possible to pass lots of values and not strict. So I'd like to squeeze types to prevent runtime errors.
Describe the solution you'd like
A type of key can be used to generate code, especially a type of key argument in function signatures.
fn get(&self, key: impl ::raiden::IntoAttribute + std::marker::Send) -> #builder_name; // Actual 🤔

fn get(&self, key: String) -> #builder_name; // To be 😄

Describe alternatives you've considered
N/A
Additional context
Rest in https://github.com/raiden-rs/raiden/pull/46

More elastic type conversion by @bokuweb
fn get(&self, key: impl Into<String>) -> #builder_name;


Description edit

Edit description w/ character limits
Use textarea for input

also with cancel (muted) and save (success) button


Update angular-router-loader to version 0.5.0

Update angular-router-loader from version 0.4.0 to version 0.5.0 to fixe issue #156

If problem after this merge, remove manually the old compiled folder rm -rf src/compiled


[linux] Bump CI image to one built 2022-02-25

Looks like we may need to pin to Gradle 6. Testing that locally.

I have a proposed fix for the Gradle 6 error. Please see PR #1139, [java] Pin to Gradle 6


Install role to .ansible/roles directory

This PR should fix CI for this role since we switched to single-workspace builds.

The CI failures were due to a very outdated molecule version. @ala-ableton This PR is now ready to review!


Fix upgrade scenarios 06 and 07

Fixes several minor upgrade issues

closing, because NCTL has been moved and this fix has been included


Broken link

Following path is broken:
Azure > App Service > Resources > Cookbooks > Reference Architecture

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

ID: 2b0ec12a-11b2-52c5-2b20-1705609a7ea8
Version Independent ID: 10b10bd9-2cf2-60d1-f30c-8c7ad4e57223
Content: Web Apps overview
Content Source: articles/app-service/app-service-web-overview.md
Service: app-service-web
GitHub Login: @cephalin
Microsoft Alias: cephalin

Hi @odvoskin, thanks for the feedback! Can you please specify which link is broken so that we can update it?

@Grace-MacJones-MSFT, looks like the link was fixed? Working now.

@odvoskin glad the link works. We will now proceed to close this thread.


Updated all class that subclass XCTestCase as final class

Checklist

[X] I checked the Contributing Guidelines before creating this request.
[X] New extensions are written in Swift 4.
[X] New extensions support iOS 8.0+ / tvOS 9.0+ / macOS 10.10+ / watchOS 2.0+.
[X] I have added tests for new extensions, and they passed.
[X] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
[X] All extensions are declared as public.

          1 Message

:book:
Thank you for submitting a pull request to SwifterSwift. The team will review your submission as soon as possible.

  Generated by :no_entry_sign: Danger


Using super to extend Interceptor

On the overrides, is there any reason this isn't just calling super for onRequest, onResponse, and onError?
Ex: return super.onRequest(options, handler);
When I use Dio I have multiple interceptors so in my client class I have:
Dio _dio = Dio(BaseOptions(       baseUrl: URL,       contentType: 'application/json; charset=utf-8'))     ..interceptors.add(DioNetworkLogger())     ..interceptors.add(OtherInterceptor()));
When I use DioNetworkLogger it seems to hang my requests. I added the supers to continue the chain of requests and seems to work fine.

Sorry. I'm blind, it is calling super but some reason isn't passing through. I'll see what I was playing with to get it working on my side


/rowkey table directive

Hi
I tried to use /rowkey as a table directive for a specific table and it works!  However it's not listed as a table directive in the help on APEX 24.1; can it be added?
Si

This would be an issue for apex where this grid is printed. This repo is limits to the library/.


Migration plan for 0.8.0 to 0.9.0

Conversation on Slack http://slack.kubernetes.io

https://kubernetes.slack.com/archives/C8149MREV/p1536171512000100

I have summarized and rephrased my conversation with @stormmore below:
We are in the camp that the operator should be able to do an upgrade once it is told that it should upgrade without any further manual steps unless there is a problem. Say, for a 3 node ES cluster, once one replica is updated, the cluster should be verified ok, then another replica gets updated. Kinda like how kops rolling-update works - cordon, drain, terminate, start new, validate cluster (verifies that the new node can have pods scheduled), rinse and repeat. If validation fails, then kops stops so that it can be investigated and the cluster manually brought back in to a verifiable state.
The issue is operator currently don't have the capability and it will take time to implement this correctly. We don't want to block 0.9.0 for this.
So, the plan is:
Give users choice of using RollingUpdate (default) or OnDelete. Later, we add an option for operator managed AutoUpdate that will use appropriate approach to achieve the goal is first paragraph.

Tags must not be reapplied for any docker images. Because, it is hard to guarantee that things will not break. Also, people using old version of operator, it will probably break if they use the modified image.
So, we will have say, ES 6.2.0 (for  0.8.0) and 6.2.0-v2 (for 0.9.0). Upgrade from 0.8.0 to 0.9.0 doesn't change things unless the user requests it (updating CRD spec), and it is documented that to get the latest feature you have to update to image tag x.x.x-v2 to get those features. If they do make the choice to change the spec, then operator will perform a rolling update with the caveat that verification is done at the end of the rolling update.

It is worth noting that, at least for ES, there is an end point that can be queried about the status of the indices

The process is documented here from Postgres: https://github.com/kubedb/cli/blob/0.10.0/docs/guides/postgres/upgrade-manual.md
Please open new issues, if there are further issues.


Reflect ALD contracts changes regarding queueing exits by (vault id, token) pair

PR that introduced changes in contracts: https://github.com/omisego/plasma-contracts/pull/324/files
Contract API changes:

processExit takes vault id as a new argument https://github.com/omisego/plasma-contracts/blob/dc3d60a72b814916902c343cea30e65f1e4144c3/plasma_framework/contracts/src/framework/ExitGameController.sol#L118
addToken function is removed, exit queues are created by calling addExitQueue instead https://github.com/omisego/plasma-contracts/blob/dc3d60a72b814916902c343cea30e65f1e4144c3/plasma_framework/contracts/src/framework/ExitGameController.sol#L63
hasToken is removed, use hasExitQueue instead https://github.com/omisego/plasma-contracts/blob/dc3d60a72b814916902c343cea30e65f1e4144c3/plasma_framework/contracts/src/framework/ExitGameController.sol#L52
PaymentExitGame now takes vault ids instead of vault addresses as arguments https://github.com/omisego/plasma-contracts/blob/dc3d60a72b814916902c343cea30e65f1e4144c3/plasma_framework/migrations/5_deploy_and_register_payment_exit_game.js#L54

Some of the events published by aforementioned functions have changed.

Thank you :pray:.
Question that came to mind - were these changes included in the nascent ALD-contract integration docs?

@pdobacz Changes are included only in docs here: https://github.com/omisego/plasma-contracts/tree/master/plasma_framework/docs

solved in https://github.com/omisego/elixir-omg/pull/1046


Add pod dependencies

Pod dependencies check for at least one pod which satisfies all of:

On the same host
In the specified (defaults to same) namespace
Matches the specified labels
In ready state

It uses JSON for the the env var encoding to avoid inventing a new complicated syntax for specifying labels.
The use case here is the same as #27 and should address it since the pods of the targeted daemonsets likely have (or least can have) pods with shared labels.  The decision to target pods with labels instead of daemonsets with labels is to be more generic and cover any case of needing a certain type of pod on the same node, regardless of how it got there.

@kfox1111 this may be of interest to you :)

@PiotrProkop @Quentin-M can we possibly get this merged/reviewed - for OpenStack-Helm this is a feature urgently required for deployment - and I'd ideally not like to run a fork.

Yeah, thanks for the heads up. :)

Absolutely, thanks!

@Quentin-M @PiotrProkop could we get a new image pushed with this PR?

@intlabs There youuu go: https://github.com/stackanetes/kubernetes-entrypoint/releases/tag/v0.3.0


UI should disable the "manage" menu if an owner removes themselves

The ownership management UI allows an owner to remove themselves from ownership, as it should.
Once this change is saved, however, the "manage" menu link stays enabled, which is a mode error.
It may make sense to warn a user that removing themselves will lock them out of further ownership actions, including adding themselves back as an owner.

This seems to have been fixed at some point.


record.lookup does not narrow the type when used in flow

🐛 Bug report
Current Behavior

Expected behavior
I expect record.lookup to narrow the type down accordingly, i.e.: if Record<string, number> is provided, an Option<number> is returned instead of Option<A>.
Reproducible example
Link to TS playground
import { option, record } from "fp-ts";
import { flow } from "fp-ts/lib/function";

const lookupCount = flow(
  record.lookup("total"),
  option.map((count) => ({ count }))
);

const res: option.Option<number> = lookupCount({ total: 42 });

console.log({ res });

Suggested solution(s)
Additional context
Your environment
I don't recall this working in any of the fp-ts versions I've used so far.

Software
Version(s)

fp-ts
2.13.1

TypeScript
v4.9.3

Same behavior if pipe is used instead:
import { option, record } from "fp-ts";
import { pipe } from "fp-ts/lib/function";

const lookupCount = <A>(r: Record<string, A>) => pipe(
  r,
  record.lookup("total"),
  option.map((count) => ({ count }))
);

const res: option.Option<number> = lookupCount({ total: 42 });

#1527 may be related.


Sac/line

Functional program detections, obstacle recognition and decision making

Add matlan integration demo. This should had go into a separate branch


added sample script for analyticsreporting api

Fixes #<issue_number_goes_here> (it's a good idea to open an issue first for discussion)

[ ] npm test succeeds
[ ] Pull request has been squashed into 1 commit
[ ] I did NOT manually make changes to anything in apis/
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate JSDoc comments were updated in source code (if applicable)
[ ] Approprate changes to readme/docs are included in PR

I signed it!
Best,
Zach Boldyga
Scalabull  |  Founder
1<PHONE_NUMBER> x 101
On Tue, Jan 3, 2017 at 9:18 PM, googlebot<EMAIL_ADDRESS>wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project. Before we can look at your
pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll
verify. Thanks.

If you've already signed a CLA, it's possible we don't have your
GitHub username or you're using a different email address. Check your
existing CLA data https://cla.developers.google.com/clas and verify
that your email is set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
If you signed the CLA as a corporation, please let us know the
company's name.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/google/google-api-nodejs-client/pull/694#issuecomment-270279589,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADiOPml9mbBxVQzkR5yWq41TIs8KWJ9kks5rOwFcgaJpZM4LaOm-
.

Thanks for the PR!  Sadly, we can't merge this unless the CI passes.  If you can re-open this with passing CI, I would be happy to merge it!


Why did the LInfinityNorm function M [0] of Matrix not take an absolute value

template <int32_t NumRows, int32_t NumCols, typename Real>
Real LInfinityNorm(Matrix<NumRows, NumCols, Real> const& M)
{
Real maxAbsElement = M[0];
for (int32_t i = 1; i < NumRows * NumCols; ++i)
{
Real absElement = std::fabs(M[i]);
if (absElement > maxAbsElement)
{
maxAbsElement = absElement;
}
}
return maxAbsElement;
}

You have a polite way of saying "There is a bug in your code." Thank you for reporting this. I have pushed the fix to the repository. This is GTE code. I looked at the GTL code and verified that code is correct.

Closing the issue because the bug is fixed.


api-docs: Add missing.md file specifically for API documentation.

Previously, templates/zerver/api/missing.md was a symlink to the file in the help center documentation.
Prep commit for moving the help center documentation to a top level directory.
See relevant CZO conversation.

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Merged, thanks @laurynmm!


Fix broken link

The links in the documentation points to a page that doesn't exist due to an escape character. Removed \ character to point to the correct resource.
⚠⚠⚠⚠⚠⚠⚠⚠⚠⚠⚠
⚠⚠⚠⚠WARNING ⚠⚠⚠⚠
⚠⚠⚠⚠⚠⚠⚠⚠⚠⚠⚠
This repo is AUTO UPDATED by a scheduled task so submitting pull requests here will make NO DIFFERENCE 😊 to the docs content.
PLEASE CONSIDER to submit either an issue or a PR with the fix intended in the source repository this documentation is based on. You can find it here: https://github.com/OfficeDev/office-ui-fabric-react
THANKS 👍
⚠⚠⚠⚠⚠⚠⚠⚠⚠⚠⚠
⚠⚠⚠⚠WARNING ⚠⚠⚠⚠
⚠⚠⚠⚠⚠⚠⚠⚠⚠⚠⚠

Docs Build status updates of commit 9de5e05:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

office-ui-fabric-react/api/react-internal/itextfieldprops.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 9de5e05:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

office-ui-fabric-react/api/react-internal/itextfieldprops.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Add release notes for dual-stack support promotion

Please provide a description of this PR:
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Ambient
[ ] Configuration Infrastructure
[ ] Docs
[X] Dual Stack
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Control Plane Revisions

In response to a cherrypick label: new pull request created: #52722

@thedebugger this one was missed in the release announcement. Sorry, I was on vacation, and couldn't review the announcement PR. I think the problem happened coz the release note was added only to master.

@kfaseela does this include ambient?
Could you please update either the first or both entries in https://github.com/istio/enhancements/blob/master/features.yaml#L353

@kfaseela does this include ambient? Could you please update either the first or both entries in https://github.com/istio/enhancements/blob/master/features.yaml#L353

I will update the original issue with ambient items as well, and see if everything is completed. I was supposed to add some new integ CI jobs for ambient for dualstack which is not yet merged. So may be that needs to go in.


Get rid of Visual C++ Runtime dependencies

This may be the reason of https://github.com/feel-the-dz3n/WinCeCompatLayer/issues/1

https://discord.gg/u74Pk5e


Consider contributor guidelines

According to the work item lifecycle:
https://github.com/decentralized-identity/org/blob/master/work-item-lifecycle.md#72-draft

Work items or their groups MAY customize the standard contributor guidelines template.

Let's find out if this work item should do anything to customize the contributor guidelines.

We included the working group in the acknowledgements section. Nothing else required here.


Acrolinx

@gewarren They did work until you changed .openpublishing.publish.config.json in this PR. The config (fixed via https://github.com/dotnet/docs-maui/pull/613) as it was is what's required for those xref's to resolve.


Sort u is specialised to u = 0, allowing apparent proofs of false theorems.

In https://gist.github.com/semorrison/f9703d01d2f9a3016a49dedacf39ee34, the proof on line 32 should not be possible, however Lean claims that it is true.
If you look carefully, with set_option pp.universes true, at the resulting signature, you see that we have defined
IdentityNaturalTransformation.{u_1 u_2} :
  Π (F : Functor.{u_1 u_2 0 0} ?M_1 ?M_2), NaturalTransformation.{u_1 u_2 0 0} F F

This is not the expected signature --- in particular the two zero universe values should still be arbitrary. Lean has decided that by specialising those universe parameters to zero, it can provide a proof of naturality, because we are then looking for an equality between two proofs.
Although Lean is strictly correct, this seems a very misleading situation, where something false has apparently been proved, and the only way to see what's happened is to inspect universe annotations on the resulting lemma.
(Note that changing Sort to Type in lines 4 and 5, Lean correctly says that it is not possible to prove the required result in line 32. Then uncommenting out lines 8-12, we get the correct proof, with no universe specialisation cheating. Further, note that if we stay with Sort, and uncomment out lines 8-12, we still get the trivial proof with universes specialised to zero, rather than the desired one.)

(I initially posted this at lean-user.)

The indicated behavior is also useful, though. Consider the case of proving that a category has all limits. The statement of the claim includes universe vars (coming from the domain of the diagrams whose limits are claimed to exist). For categories which merely have all limits for certain universe levels (such as the category of Lean terms and functions), the behavior described above correctly restricts the statement of the claim. Or, at the very least, it'd be an annoyance if Lean rejected the claim because it didn't literally hold for all universe levels.

First a clarification, if the user specified the universe parameter u, then u never magically becomes u := 0 in their definitions. What is happening in your example is that Sort ?u (where ?u is a metavariable, aka placeholder, aka hole, aka unification variable) is being assigned to ?u := 0.
I agree the assignment ?u := 0 is not desirable, but I want to emphasize this can only happen in very particular situations.
1- User is leaving universe parameters implicit. This is your case, you don't specify the universe parameters for Category and Functor at IdentityNaturalTransformation.
2- User is using automation for constructing definitions instead of lemmas. In Lean, the type of the lemma/theorem cannot be influenced by its proof. We elaborate the type of the lemma before we elaborate the proof. That is, when we elaborate the proof, we don't have universe metavariables anymore. This is your case, you are using definition and automation.
3- User is using automation that is tries to synthesize subsingleton type class instances.
We have the following instance in the standard library
instance subsingleton_prop (p : Prop) : subsingleton p :=
...

https://github.com/leanprover/lean/blob/master/library/init/logic.lean#L763
It says that every proposition has at most one element.
I'm pushing a commit that address the issue by disabling the assignment of universe metavariables when trying to synthesize elements of the type class instance subsingleton a.

Thanks for the careful clarification. The distinction between lemmas and definitions here makes sense, but I hadn't expected it.


android scenario_app tests documentation / scripts is out of date

The instructions for running the android scenario_app tests refers a script that no longer exists ./build_and_run_android_tests.sh.
There is a run_android_tests.sh script but it just errors:
$ ./run_android_tests.sh
./run_android_tests.sh: line 37: ../../../../third_party/bin/gradle: No such file or directory

cc @blasten @dnfield

I probably missed updating this when I was refactoring. There's no single script anymore that builds and runs tests, you have to build your engine variant and then you can run the tests from there. I'll try to look at updating the docs after the weekend.

Yea, i saw it was building an apk in the variant directory.  I don't know what to do with it though.

So I think the only thing that works right now are the firebase testlab tests. The local tests on an emulator do not work, and it seems like they may never have worked - there was a bug in the harness that hid breakage.  My undrestanding is the long term plan is to just remove them. /cc @blasten.
I'll try to add instructions about running the FTL tests, but those are really mainly just smoke tests. What test are you trying to run or add?

I need tests for the Android embedder.  What is the Android equivalent of our iOS unit tests?

They currently do not work.

I think we should just do the equivalent to what we did for iOS, a JUnit test target that is building against the flutter.jar.  I told another team member it would be no problem writing this test.  I'm getting that sinking feeling I signed up for more than i bargained for haha

Ah! Sorry, there are JUnit tests of course, but they are built and run differently - they don't use scenario_app at all

See run_test.py --type=java

Okay, I'll check those out, those might be good enough, thanks dan.


Recursion error, same as in #122

Hi
I get the recursion error described in https://github.com/mopidy/pyspotify/issues/122 with 2.0.0b4. The fix in that thread seems to help.

This has recently surfaced as mopidy/mopidy-spotify#49 too.

Currently I can't reproduce this. I could blindly disable the playlist_update_in_progress event in the hope of it making sure this never happens again. That doesn't feel like a very good solution, and we'll be left without that event forever.
Thus, I opt to close this issue until it resurfaces again, in the hope of ending up with a better solution then.


Improved Docs

Is this just whitespace or do I overlook something?

I don't get this, it only seems a whitespace change.


Forked to get things working

We (Digitalist Open Cloud) sort of had the functionality as a acute need to get this working on the latest Backstage release, so we forked both the plugins:
https://github.com/Digitalist-Open-Cloud/backstage-plugin-harbor
https://github.com/Digitalist-Open-Cloud/backstage-plugin-harbor-backend
Published NPM packages:
https://www.npmjs.com/package/@digitalist-open-cloud/backstage-plugin-harbor
https://www.npmjs.com/package/@digitalist-open-cloud/backstage-plugin-harbor-backend
The goal is to contribute back to this repo - but our case right now is not to be backwards compatible with older versions or the old backend system.
If that is fine, we are happy to create pull requests for the updates.

Not backwards compatible to what version?

Generally, I am up for that

We are focusing on the the new backend system, so I am not sure that our changes will work on the old one. We are running on Backstage v1.29.1.

I will create pull requests for the changes tomorrow or the day after, both for frontend and backend plugin.


Added junit test framework with gradle build and added test case with v4 signature

What type of PR is this?
This PR with v4 signature api test case for create bucket and backend with gradle build tool framework

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:

kind new feature

/kind bug fix
/kind cleanup
/kind revert change
/kind design
/kind documentation
/kind enhancement

What this PR does / why we need it:
In this PR I have added the code for generate v4 signature and code build tool changed in gradle
Which issue(s) this PR fixes:
No issue in this PR

Fixes #
Test Report Added?:

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:

kind TESTED

/kind NOT-TESTED

Test Report:

Special notes for your reviewer:

@Click2cloud-Wadhai We will need


avocode: 4.12.0 -> 4.14.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/avocode/versions.
meta.description for avocode is: "The bridge between designers and developers"
meta.homepage for avocode is: "https://avocode.com/"
meta.changelog for avocode is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/9fd9bs2288j0ksmzjzilnl01yxvzinmj-avocode-4.14.0/bin/avocode passed the binary check.

/nix/store/9fd9bs2288j0ksmzjzilnl01yxvzinmj-avocode-4.14.0/bin/.avocode-wrapped passed the binary check.

0 of 2 passed binary check by having a zero exit code.

2 of 2 passed binary check by having the new version present in output.

found 4.14.0 with grep in /nix/store/9fd9bs2288j0ksmzjzilnl01yxvzinmj-avocode-4.14.0

found 4.14.0 in filename of file in /nix/store/9fd9bs2288j0ksmzjzilnl01yxvzinmj-avocode-4.14.0

directory tree listing: https://gist.github.com/50f8dadcc8d14c315bf5ee8d787a0f27

du listing: https://gist.github.com/94b3d6bd2bf2bb9257bc09d3c467c497

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

3 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
avocode

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9fd9bs2288j0ksmzjzilnl01yxvzinmj-avocode-4.14.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 avocode https://github.com/r-ryantm/nixpkgs/archive/4a2bd30be8455428574f6210993125f0ffec4802.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9fd9bs2288j0ksmzjzilnl01yxvzinmj-avocode-4.14.0
ls -la /nix/store/9fd9bs2288j0ksmzjzilnl01yxvzinmj-avocode-4.14.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:

avocode

Maintainer pings
cc @megheaiulian for testing.

Result of nixpkgs-review pr 122962 at 4a2bd30b run on x86_64-linux 1

1 package built successfully:

avocode

1 suggestion:

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/applications/graphics/avocode/default.nix:71:3:
   |
71 |   installPhase = ''
   |   ^


Add Nav to top in all pages

Add a nav to top button in the bottom right corner in all the pages.

Please assign this issue to me.


Elements tag doesn't accept locale

Summary
I cannot seem to change the locale of my elements. Here's a basic sample of my reproduction. When I run the app it always displays English even though I'd expect French.
const Checkout = ({
  item,
  onClose,
  summary,
}: {
  item: Item;
  onClose: Function;
  summary: Array<object>;
}) => {
  const { checkout_token, currency, language } = useContext(Context);
  const lang = useContext(LocalisationContext);
  const [state, setState] = useState(CheckoutState.Idle);
  const stripePromise = useMemo(() => loadStripe(checkout_token), []);
  return (
    <Modal
      onClose={state === CheckoutState.Charged ? null : () => onClose()}
      icon={null}
      loading={false}
      title={lang.checkout}
      size={ModalSize.Narrow}
    >
      <CheckoutStyle>
        <Elements key={language} locale="fr" stripe={stripePromise}>
          <CheckoutDetail
            currency={currency}
            summary={summary}
            item={item}
          />
        </Elements>
      </CheckoutStyle>
    </Modal>
  );
};

Other information
What's strange is that Typescript also complains about that locale doesn't exist on ElementProps. I'm using ts-ignore to supress the warning:

I believe I'm following examples and documentation correctly. Does anyone have a workaround? This is rather critical for our application. Removing the hooks would be a pretty big set back for us.

Yes, if you hadn't made it obvious that the value exists in options, I doubt I would have found a viable solution. The other conditions you mentioned aren't a concern. I didn't at any point recognise the legacy vs current release versions. I suppose I was reading the docs and getting confused by this repo version. It should maybe be made a bit clearer? It's possible that I made an error on this as well, I suppose it just wasn't obvious.


Fix MUNIT_MAVEN_PLUGIN_ATTRIBUTES Rule to check coverageAttribute as text and properties in pom.xml

MUNIT_MAVEN_PLUGIN_ATTRIBUTES rule checks for the coverage elements in the pom.xml to match with the values provided in the rule configuration. If the values for coverage elements are configured as properties like <runCoverage>${munit.runCoverage}</runCoverage> within the pom.xml, they aren't matched and it fails the rule.
Here's configuration for MUNIT_MAVEN_PLUGIN_ATTRIBUTES linter rule:
MUNIT_MAVEN_PLUGIN_ATTRIBUTES {
      coverageAttributeMap =[
        'runCoverage':'true',
        'failBuild':'true',
        'requiredApplicationCoverage':'80',
        'requiredResourceCoverage':'80',
        'requiredFlowCoverage':'80'
      ]
      includeDefaults = false
    }

We would need to fix this rule to handle match as both free text and properties in the pom.xml.

In the current implementation, getConfigProperty(String propertyName) method is implemented in ArtifactDescriptor.groovy to fetch Maven MUnit coverageAttributeMap attributes. This method returns the text for the value in the coverageAttributeMap XML elements.
However, when the MUnit coverage XML elements is provided with property variable - <runCoverage>${munit.runCoverage}</runCoverage>, It doesn't return the value for the property - munit.runCoverage in the pom.xml.
To fix this issue, we will implement below -

Update getConfigProperty(String propertyName) method is implemented in ArtifactDescriptor.groovy, to return value for the property from the pom.xml in the PomElement response, when MUnit coverage XML elements with property variable - <runCoverage>${munit.runCoverage}</runCoverage>in the pom.xml.
Response from getConfigProperty(String propertyName) should be as below:

When MUnit coverage XML elements contains text value: true

PomElement : [name= runCoverage, value= true]

When MUnit coverage XML elements contains text value: ${munit.runCoverage}

PomElement : [name= runCoverage, value= value of **munit.runCoverage** property in pom.xml]

Implemented with PR# https://github.com/avioconsulting/mule-linter/pull/157


Add class to input when dropdown is active

I'm working with inputs that have a border radius:

And when the results are open I'd like to remove the bottom border radius from the input, to achieve:

However, there doesn't seem to be a class on the input when the results panel is open for me to do this.
The aria-expanded attribute does change when the results panel has results, so I can do this:
.autocomplete__input[aria-expanded=true] {
  border-bottom-left-radius: 0;
  border-bottom-right-radius: 0;
}

But not when the panel is open for the "no results" message. So it only half works:

This seems like a pretty common use case that could warrant adding a class for? Or perhaps aria-expanded should be set to true when the results panel is expanded showing "No results"?

Hello @AlecRust ,
Thanks for raising this.
It seems like the aria-expanded state should be consistent when showing 'no results', but I would need to properly think this through and test this.
We're primarily focused on supporting users of government since we have limited time as a team.
If you want to contribute this fix you're welcome to raise a pull request and we can review it when we get the time, thanks for your patience. 👍

+1 This would be super helpful. I'm having this same issue right now.

I think it'd be helpful to add the class to .autocomplete__wrapper, so that other elements could be styled too.


Fix tax function indexing

This PR fixes two cases of tax function parameters not being indexed (or sized) correctly.
The first is a change to parameters.py to make sure tax functions that are input are extrapolated to the appropriate model dimensions.  This addresses Issue #877.
Second is a changes to the plotting of 2D tax functions in parameter_plots.py. This function had not been updated (or not correctly updated) to notes that the dimensions of the lists of lists of tax functions parameters are TxS. The change here is to make sure time period index is given before the age index.

Codecov Report

Merging #878 (7686139) into master (816aeec) will increase coverage by 0.05%.
The diff coverage is 100.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #878      +/-   ##
==========================================
+ Coverage   79.93%   79.98%   +0.05%
==========================================
  Files          18       18
  Lines        4146     4157      +11
==========================================
+ Hits         3314     3325      +11
  Misses        832      832

Flag
Coverage Δ

unittests
79.98% <100.00%> (+0.05%)
:arrow_up:

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

Files Changed
Coverage Δ

ogcore/firm.py
97.35% <100.00%> (+0.11%)
:arrow_up:

ogcore/parameter_plots.py
81.08% <100.00%> (ø)

ogcore/parameters.py
74.20% <100.00%> (+0.35%)
:arrow_up:

All unit tests are passing and I've run the example script successfully my my machine.
There is some issue building miniconda in the "Check that docs build" workflow. It continues to time out, even after re-running this job 3 times. I do not know the issue since the same actions are used to build miniconda here as are used in the successful unit test actions.
If @rickecon doesn't have a quick solution, I would say go ahead and merge this PR. It is otherwise ready to go.

@jdebacker. All tests have passed except for Build and test [Python 3.9, 3.10] / build (ubuntu-latest, 3.9). Maybe we need to use mambaforge for our build_and_test.yaml.

@jdebacker. We'll see how this goes. I am worried that we will run out of compute time with 9 build_and_test.yml matrix runs. If it times out, we can just remove Python 3.9 from the tests. Unfortunately, I don't know an easy way to do "local only" Python 3.11 tests.

@jdebacker. It looks like Python 3.11 is resulting in some pickle.load errors. Below is the traceback from the Build and test Linux Python 3.11 tests.
=========================== short test summary info ============================
ERROR tests/test_TPI.py - _pickle.UnpicklingError: Memo value not found at index 80
ERROR tests/test_output_plots.py - _pickle.UnpicklingError: Memo value not found at index 15776
ERROR tests/test_output_tables.py - _pickle.UnpicklingError: Memo value not found at index 15776
ERROR tests/test_parameter_plots.py - _pickle.UnpicklingError: Memo value not found at index 15776
ERROR tests/test_parameter_tables.py - _pickle.UnpicklingError: Memo value not found at index 15776

@jdebacker. The good news is that it ran really fast.

@rickecon writes:

@jdebacker. It looks like Python 3.11 is resulting in some pickle.load errors. Below is the traceback from the Build and test Linux Python 3.11 tests.

Yes, if you save a pickle file in an earlier version of Python (or relevant packages that the pickled objects are from), it's difficult to open in a later version, as far as I know.  We've run into this before.  Since I don't want to save all pickle files again right now, I've just removed 3.11 from the test matrix.

Thanks @jdebacker. Looks great. Merging.

Oops. We just need to update the version number in setup.py and ogcore/__init__.py. Probably bump it up to 0.10.8 rather than 0.11.0. Right?

@rickecon Let me do a quick PR to resolve Issue #879 before we release a new version.  We've got several changes we can package together. But yet, that will be 0.10.8.


Adding xsens-awinda to documentation index for distro

The diff shows several unrelated changes. Please update the changes to only show your changes.

I will close this due to no response. Please either update the branch and comment here and the PR can be reopened or create a new PR.


three dots patterns seem to not be formatted

rustfmt seems to format such things as 1 .. 2 to 1..2 but does not format 1 ... 2 pattern into 1...2.

We don't reformat any patterns yet: https://github.com/nrc/rustfmt/issues/18

A dupe then, I guess.


Remove default OAuth2 configurations

As a developer, as part of ongoing security consolidation on 2.0 line, I'd like to remove the default OAuth2 configurations from the bundled JAR. If someone wants to enable it, they would have to explicitly configure the required properties.
child of spring-cloud/spring-cloud-dataflow#2574

We will also have to remove the default security configurations from the ref. guide.

Added some clarification with commit https://github.com/spring-cloud/spring-cloud-dataflow-server-cloudfoundry/commit/06a5125739ae82aa089652894cfc76e934c0137d


[SP-6106] backport of BACKLOG-35528 Upgrade log4j - change log4j.xml …

…to log4j2.xml

:white_check_mark: Build finished in 3m 17s
Build command:
mvn clean verify -B -e -Daudit -amd -pl assemblies/static

:exclamation: No tests found!
:information_source:  This is an automatic message


UnsupportedOperationException thrown when using Spring Actuator

I am trying to use Spring Actuator with redis as a single server but I'm getting UnsupportedOperationException at RedisHealthCheck so the application is considering redis DOWN
Expected behavior
Actuator is able to perform health checks to determine the status of Redis server
Actual behavior
java.lang.UnsupportedOperationException is thrown when Actuator tries to do the Redis health check
Steps to reproduce or test case
Add spring actuator to project
Configure RedissonClient as a single server (default configuration from here https://github.com/redisson/redisson/wiki/2.-Configuration#26-single-instance-mode can be used)
Start the application with health check enabled
Redis version
redis_version:4.0.9
redis_git_sha1:00000000
redis_git_dirty:0
redis_build_id:d3ebfc7feabc1290
redis_mode:standalone
Redisson version
redisson-3.8.1
Redisson configuration
{
"singleServerConfig":{
"idleConnectionTimeout":10000,
"pingTimeout":1000,
"connectTimeout":10000,
"timeout":3000,
"retryAttempts":3,
"retryInterval":1500,
"password":null,
"subscriptionsPerConnection":5,
"clientName":null,
"address": "redis://<IP_ADDRESS>:6379",
"subscriptionConnectionMinimumIdleSize":1,
"subscriptionConnectionPoolSize":50,
"connectionMinimumIdleSize":32,
"connectionPoolSize":64,
"database":0,
"dnsMonitoringInterval":5000
},
"threads":0,
"nettyThreads":0,
"codec":{
"class":"org.redisson.codec.JsonJacksonCodec"
},
"transportMode":"NIO"
}
redisson-stack-trace.log

Thanks for report! Fixed in https://github.com/redisson/redisson/commit/d10be369f1d203422e5c84b82395127e79f2d953


Why is weave not working in this scenario?

I'm trying to assign an ip to a docker container and expose it to the public, but I cant get it to work.
I created a new docker host, called aldebaran, with ubuntu 14.04 and the latest docker.
root@aldebaran:~# weave launch
OK!
root@aldebaran:~#  C=$(weave run <IP_ADDRESS>/24 -t -i nginx)
OK!
root@aldebaran:~# weave expose <IP_ADDRESS>/24
OK!
root@aldebaran:~# ping <IP_ADDRESS>
OK!
root@aldebaran:~# ping <IP_ADDRESS>
OK!
root@aldebaran:~# curl <IP_ADDRESS>
OK!
root@aldebaran:~# curl <IP_ADDRESS>
curl: (7) Failed to connect to <IP_ADDRESS> port 80: Connection refused
What am I doing wrong? It works in the default example, why is not working here?

From the docs for expose

we run expose choosing an unused IP address in the application subnet

and from the docs for service export

we add a NAT rule to route from the outside world to the destination container (example ...)

Do those two things and it should work.
Let me know what we should have said in the docs to avoid the trap you fell into.

Do those two things and it should work.

(And the first step alone is sufficient if you only need to access the container from the host, which is what you do in your transcript)

thank you @rade! you are doing REALLY an excellent job with this app. It's really helping me with my project, and the code is very well written and much simpler than docker, really helping me in learning advanced Go.
I'm trying to create an open source docker web interface, and weave is just what I was looking for.
My goal is to try to assign a local, static IP accessible from the host, so I can setup iptables rules to make it accessible to the internet. I'm starting just from host accessibility, as I already know how to use Iptables, but I'm stuck.
You say I gotta use an unused IP, but that IP is only used by that container. The only thing that I'm doing different from the screencast, is that I'm using curl on the host and not on the other VMs.
Given this is a fresh install, with no used IPs, can you help me understand how do I assign an IP in the format 10.x.x.x to a container, so that such IP is accessible from the host? If my commands were wrong how should I have done it?
Consider I'm really noob, so maybe a more experencied user wouldn't have met this problems, but I think some HowTos could be helpful, and I will be more than glad in helping you :)

You say I gotta use an unused IP, but that IP is only used by that container.

It's not unused then, is it?
weave expose exposes an entire sub-net. The given IP address needs to be unused since it serves as a "gateway" into that sub-net.

how do I assign an IP in the format 10.x.x.x to a container, so that such IP is accessible from the host?

There is nothing wrong with your IP assignment to the container. The problem is that you are using the same IP in expose. Choose a different, unused IP on the same sub-net.

root@aldebaran:~# weave expose <IP_ADDRESS>/24
OK!
root@aldebaran:~# ping <IP_ADDRESS>
OK!
root@aldebaran:~# curl <IP_ADDRESS>
curl: (7) Failed to connect to <IP_ADDRESS> port 80: Connection refused
<IP_ADDRESS> is in the same sub-net right?

root@aldebaran:~# weave attach <IP_ADDRESS>/24 9e9
root@aldebaran:~# curl <IP_ADDRESS>
curl: (7) Failed to connect to <IP_ADDRESS> port 80: Connection refused
doesnt work either. I'm sorry if I'm sounding really noob, but I have just very basic understanding of networking, I repeated the step you made in the screencast, step by step, and it doesnt work. I'm sure I will laugh about my noobishness in 30 minutes, but for now it's just frustrating that it isnt working :p

Trying curling to <IP_ADDRESS>.

It's the first thing I tried, as you can see in the first question. It's still not working :(
root@aldebaran:~# curl <IP_ADDRESS>
curl: (7) Failed to connect to <IP_ADDRESS> port 80: Connection refuse

Try exposing <IP_ADDRESS>/24 and pinging <IP_ADDRESS>.
Notice how in the docs the example exposes <IP_ADDRESS> but then pings <IP_ADDRESS> and <IP_ADDRESS>.

I started from the ground up.
C=$(weave run <IP_ADDRESS>/24 -t -i nginx)
OK!
weave expose <IP_ADDRESS>/24
OK!
curl <IP_ADDRESS>
OK!!!
it works!!! great!!! So I gotta expose an unused ip, from the same subnet, because it will act as gateway?
So a smart way to do it, would be to assign a /30 size subnet to each docker container, so it has 2 IPs, one for the container, and one for the gateway?
I feel like a linux rockstar thanks to you.

So a smart way to do it, would be to assign a /30 size subnet to each docker container, so it has 2 IPs, one for the container, and one for the gateway?

Then none of your containers would be able to talk to each other, since they'd all be on different sub-nets. Perhaps that is what you want, but it seems a bit unusual.
As I said, expose acts on an entire sub-net; so a more typical application is to place a bunch of containers in a common sub-net, giving them each their own IP, and then use one extra IP from the same sub-net to expose the entire sub-net, i.e. all containers, to the host.

Very good point!
Is there a way with weave to let 2 subnet talk to each other? Or should I use the usual ip route tools?

Is there a way with weave to let 2 subnet talk to each other?

Nope. Though you can assgin containers IPs on more than one sub-net.

thank you rade. You built an exceptional project.
I can help three ways:

Create a blog post/git commit with a zero to start explanation on how to use weave, for n00bs like me.

I can ask a friend to make you a logo for this project for free, if you want, as I think it would greatly help spread your project (think a nice clickable logo in my blog post, or on the list of the technologies used in my docker web panel)

Help you to create a better website? It's already pretty good, but you can always improve, and this is one of  the few stuff I can help you with

this project solved me a lot of troubles, and I'm willing to help it anyway I can :)

@servermeta Thanks for the kind offer. A blog post would be great. Email us at<EMAIL_ADDRESS>if you want to discuss the content or would like us to review the post prior to publication.


Combine pots page was superseded

See: guidance-guarantee-programme/pension_guidance#630

🚢

Whoops, thanks


Update CI runner versions

test Irmin core on 4.06
update Windows CI version number to match equivalents on Travis CI

I was thinking we could also add runners for lower and upper bounds for every packages, but that might be too many runners.
If we don't do that, I suggest all backends run the oldest supported version of the compiler, so we can detect more easily if we break something.

Yes the opam file should reflect the lowest bound. We should also try to test some packages with the most recent version of the compiler to detect breakage early.

Could you rebase on master? For the lower bound in opam files: they are necessary only if the package actively not build on the given version -- if it's a transitive dependencies (in that case because of one of the mirage dependencies) let not add it ; the constraint solver will give the proper error message to our users.

For the lower bound in opam files: they are necessary only if the package actively not build on the given version -- if it's a transitive dependencies (in that case because of one of the mirage dependencies) let not add it

Could you clarify that? Do you mean that the lower bound should denote the minimal OCaml version necessary to compile the package itself (without dependencies)? What about transitive dependencies with the Irmin packages themselves?

Sorry I was not clear: what I meant is that we try to add bounds only when the error comes from the current package, not its dependencies. Which means that if in the future one of the dependency is fixed to work with an older version of OCaml, there is nothing to change to compile the current package.


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 11:21:29 on 2023.06.06
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 2, errors out: 0
Original problem ID: 23426
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=23426

Problem has been resolved in 12m 0s at 11:33:29 on 2023.06.06
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 23426


Fixed typo in nodes doc

 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.


ArgumentException when Scrolling

To reproduce:

Start TreeListBoxDemo project
Scroll down in the TreeListBox

An ArgumentException, stating "The height can not be negative" is thrown here:
https://github.com/objorke/PropertyTools/blob/develop/Source/PropertyTools.Wpf/TreeListBox/TreeListBox.cs#L733

are you running on .net 4.5.2 or later?

#38 is very similar

The TreeListBoxDemo uses .NET 4.5. If I change that to 4.5.2, it seems to work fine.

I just tested the demo, upgrading to 4.5.2 or even 4.6.2 seems not solve it on my machine.

Doesn't work for

It consistently crashes for me so I looked at it a bit:
There's some code in the VirtualizingStackPanel involved here where  ExtendViewport() is called with a few arguments equal to Size.Empty (which has a Height of -Infinity).
Later under certain conditions one of the -Infinity values are used when updating a Rect.Height property, which fails.
Unfortunately I don't have source stepping for 4.6.2, so I'm only able to see locals and the callstack...

would it help to change to a lower .NET framework version?

I'm also encountering this bug, with .NET 4.6.2. I just put a try...catch around the final line in the Insert method for TreeListBox and have encountered no errors since.

try
{
    this.Items.Insert(index, item);
}
catch (ArgumentException ex)
{
    // Do nothing
}

Unsure of the ramifications,  but I haven't encountered any issues so far.

Closing this for now, but I hope to see a better solution :-)


added brew cask functionality

Added brew cask.
Added iterm2 as an example. Can remove if desired.

Just my 2 cents, not really a big deal but I still have issues with cask.

wrt caskroom/homebrew-cask#2534, shall I append this to the zshrc?
export HOMEBREW_CASK_OPTS="--appdir=/Applications"

Yep you can definitely set that. I'm definitely deferring this to others, cask just isn't for me.

Updated script to append to zshrc to set brew cask opts

The current script doesn't require cask for any packages, does it?
We have https://github.com/thoughtbot/laptop/wiki, which is similar to this pull request, but we don't do a good job linking to it from the "Customize" section of the README.
What if instead of merging this into the codebase, you make any improvements to that wiki page, and then make this pull request just a doc change, adding a link to the wiki from the "Customize" section of the README?

Put your personal customizations in ~/.laptop.local
Duh.
It seems this is already accounted for in the wiki. Thanks for the feedback. Amended PR as per comments.

@autodidacticon Awesome, thanks. Merged as b153d5e.


integrate passport authentication into seller model

WIP NOT READY TO MERGE
need a reliable way to test to ensure the authentication model has been integrated correctly.

this will not be merged into main


Most links are broken on wiki "List of available algorithms"

https://github.com/andrewssobral/bgslibrary/wiki/List-of-available-algorithms

Thank you @luvhalvorson for reporting this issue, I will check it


The app is able to perform all BLE operations even if the radio is turned off

We should also check device connection while performing all BLE operations


Frag does not explode once thrown in v50.

Like the title says, when thrown the frag will not explode afterwards, and will just sit on the ground in v50.

Done.


Indent level text object

Is there an indent level text object?
If not, it would be nice to have that. An example would be in JSON files.

https://github.com/kiyoon/treesitter-indent-obhect.nvim
I use this. Is this something you'd like?

This is perfect. Thank you!


Implement TupleAsRef, etc. for ()

It would only return (), but for completion's sake it should be implemented. I'm currently getting errors in a program because this doesn't compile if the tuple is ():
Reproduce with (dependencies tuples and tuple-fn):
use tuples::tuple_as::TupleAsRef;
use tuple_fn::TupleFn;

fn call_closure_on_tuple<'a, T, F>(tuple: &'a T, func: F)
where T: TupleAsRef<'a> + 'a,
      F: TupleFn<<T as TupleAsRef<'a>>::OutTuple, TupleFnOutput = ()>,
{
    func.call_with_args_tuple(tuple.as_ref())
}

fn main() {
    call_closure_on_tuple(&(), || {
        println!("Hello, world!");
    })
}

Error:
error[E0277]: the trait bound `(): TupleAsRef<'_>` is not satisfied
  --> src/main.rs:12:27
   |
12 |     call_closure_on_tuple(&(), || {
   |     --------------------- ^^^ the trait `TupleAsRef<'_>` is not implemented for `()`
   |     |
   |     required by a bound introduced by this call
   |
   = help: the following other types implement trait `TupleAsRef<'a>`:
             (T,)
             (T0, T1)
             (T0, T1, T2)
             (T0, T1, T2, T3)
             (T0, T1, T2, T3, T4)
             (T0, T1, T2, T3, T4, T5)
             (T0, T1, T2, T3, T4, T5, T6)
             (T0, T1, T2, T3, T4, T5, T6, T7)
           and 24 others
note: required by a bound in `call_closure_on_tuple`
  --> src/main.rs:5:10
   |
4  | fn call_closure_on_tuple<'a, T, F>(tuple: &'a T, func: F)
   |    --------------------- required by a bound in this
5  | where T: TupleAsRef<'a> + 'a,
   |          ^^^^^^^^^^^^^^ required by this bound in `call_closure_on_tuple`

Included in 1.10.0


Healthcheck

I'm running this container on my arm device for a while now (2 containers for different purposes).
Containers running okay.
I check the health-state and IP-addresses from the containers a few times a day with a cronjob.
The health-state toggles between unhealthy and healthy over the day while the IP-addresses are still the same.
kr.,
Frepke

Hi there,
Thanks for your input!
The healthcheck performs the command ping -W 1 -w 1 -q -s 8 <IP_ADDRESS> where it simply pings Cloudflare's <IP_ADDRESS> address. So that's just a connectivity test.
Maybe Cloudflare took too long to respond.
I'm opened to other domain names or IP addressese to ping against, but they would have to work everywhere (i. e. in China as well).
I had a healthcheck back then which would check your IP address but it would fail quite often for a reason I don't exactly recall :smile:

Okay,
I've put an extra line (echo $status) in healthcheck.sh so I could see the result from the ping command.
The healthcheck often has error 1/ as a result so I've changed the -w option from 1 to 2 which solved the problem for me.
In the past, I had a similar problem with a curl-command in a Lua script in a domoticz container.
Then I read somewhere on the internet that ping and curl commands often are much slower from within a Docker container as from the host cli itself.
kr.,
Frepke


mapjs/src/browser/dom-map-widget.js: Using deprecated keyCode within document listener

https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/code
https://workflowy.com/#/b3ab0251f2e5

mapjs/src/browser/dom-map-widget.js: 190
Also see: #4

Should use KeyboardEvent.key instead.


1.3 Roadmap

These are the features for a 1.3 release.

[ ] Improve JDBC #248 236
[ ] Add support for typed rows
[ ] eel cli
[ ] #262 enforce schema option
[ ] #263 on complete does not fire

@sksamuel @hannesmiller do you think we should consider the Java API for the 1.3 roadmap?

Why not - I have already started on it.
Sent from my iPhone
On 20 May 2017, at 17:16, Gary Frost <notifications<EMAIL_ADDRESS>wrote:
@sksamuelhttps://github.com/sksamuel @hannesmillerhttps://github.com/hannesmiller do you think we should consider the Java API for the 1.3 roadmap?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/51zero/eel-sdk/issues/267#issuecomment-302882893, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATyi-WpkAmhaYEJarJjkhReA0_ayxRVpks5r7xHcgaJpZM4NF1uT.

For 1.3 yes.
On 20 May 2017 5:19 pm, "hannesmiller"<EMAIL_ADDRESS>wrote:

Why not - I have already started on it.
Sent from my iPhone
On 20 May 2017, at 17:16, Gary Frost<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
@sksamuelhttps://github.com/sksamuel @hannesmiller<https://github.
com/hannesmiller> do you think we should consider the Java API for the
1.3 roadmap?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<https://github.com/
51zero/eel-sdk/issues/267#issuecomment-302882893>, or mute the thread<
https://github.com/notifications/unsubscribe-auth/ATyi-
WpkAmhaYEJarJjkhReA0_ayxRVpks5r7xHcgaJpZM4NF1uT>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/51zero/eel-sdk/issues/267#issuecomment-302883030, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAtZGu8MCjP69BRc18Pv0SX90ruqAjvhks5r7xJxgaJpZM4NF1uT
.

Closing this, as an epic doesn't really work on github.


(PDB-4255) update taoensso libs to remove warnings

Update taoensso/nippy and taoensso/encore to remove warnings:
WARNING: pos-int? already refers to: #'clojure.core/pos-int? in namespace: taoensso.encore, being replaced by: #'taoensso.encore/pos-int?
WARNING: bytes? already refers to: #'clojure.core/bytes? in namespace: taoensso.encore, being replaced by: #'taoensso.encore/bytes?

CLA signed by all contributors.

No strong opinion, but wondered about putting at least the shared bit into clj-parent instead -- good/bad idea?  (Only wondering if that might mean we can avoid having to remember to undo this later if/when it's updated there.)

as soon as we merge puppetlabs/clj-parent#219, I'll redo this change to just update clj-parent


Introducing error to demonstrate Repodex PR Review

Repodex should be able to catch this error and acknowledge it in the review.

Hey @repodex can you review this for me?


modifying post effect shaders for multiview support

This fixes issue  #1138

looks good to me now as well.

Verified


Removed erroneous e.g.

@JShep1 thanks for the iterations. I've come to the conclusion that nothing was sitting right with me because it's just not something that bears mentioning here. The packages being built in this example don't even install things to bin. Removing references to explicit bin directories but keeping the text explaining paths and environment scripts seems like the way to go. How does it look to you now?

Looks good!  I'm going to need someone with write privileges to merge - I don't have mine... yet


Display hostname and Musicbox version number in title bar

It would be very handy (i my case at least) to have the hostname and version number shown in the title bar (i.e. 'Home' -> 'Home | LivingRoom (v.0.60)').
Ideally the title bar can have a configurable/customizable syntaxis based on variables.
$Menu -> 'Home'
$HostName -> musicbox.local
$ProductName -> MusicBox
$ProductVersion -> 0.60
$NowPlayingArtist -> Antony and the Johnsons
$NowPlayingAlbum -> I am a bird now
$NowPlayingSong -> You are my sister
The aim is to configure your own header in the GUI.

This belongs in the webclient repo and sounds like https://github.com/pimusicbox/mopidy-musicbox-webclient/issues/67


Download: Fix error downloading thumbnails

In a previous change, the _get_channel_metadata function was moved outside EndlessKeyContentManifest. However, this was not corrected in get_contentthumbnail_tasks.
https://github.com/endlessm/kolibri-explore-plugin/issues/648

Yeesh. Sorry about that. I meant to rebase #584 after #630 landed. Too much juggling.


Add ansible playbook to install requirements for UMI team

UMI Requirements

java 8
mongoDB 4.4
prometheus 2.48

Can you please provide some additional details:

which node(s) are these components installed to?
default configuration / ports? Do services need to be started? (I believe mongo does not start by default after installation)
In what condition does this need to be installed? Or what is the user flow

We currently have nodes sdpv-dss01 though 04.  I installed the requirements manually but there should be a reproducible way to do it.  Nadim is setting up a physical cluster but I don't know the nodes
No unusual conditions/ports as long as all the nodes in the cluster can reach each other.   MongoDB does not need to be started.  prometheus doesn't need to be started since we need to run it with our own config files - we should figure out how to automate that later
It needs to be installed for UMI to run, so before any user or developer gets to the node

I mean in a general sense, with regards to DSS. Targets, hosts, collocated servers, clients, etc? Let me know if we need a meeting to discuss architecture.


start-process doesn't work properly in functions invoked from REPL

Steps to reproduce
Define this function:
function su { Start-Process PowerShell -Verb RunAs }

Type su at the prompt.
Expected behavior
It should either:

launch a new powershell widow running as Administrator or
Suspend the current shell and run an Administrator shell in the same window

Actual behavior
It seems like it's trying to run both processes in the same console where possibly both are getting stdin and outputting to stderr. It looks similar to trying to run an interactive process in using with & (background).

Using -Verb open makes no difference.
Environment data
C:\Program Files\PowerShell\<IP_ADDRESS>> $PSVersionTable

Name                           Value
----                           -----
PSEdition                      Core
SerializationVersion           <IP_ADDRESS>
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
WSManStackVersion              3.0
GitCommitId                    v6.0.0-alpha.10
CLRVersion
BuildVersion                   <IP_ADDRESS>
PSVersion                      6.0.0-alpha

This works on Windows PowerShell, not clear yet if cmdlet or engine issue

It doesn't work in Windows PowerShell for me. It pretty much does the same thing. Here's the info from PowerShell on my Win10 system just upated with the anniversary update:
Name                           Value
----                           -----
PSVersion                      5.1.14393.187
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14393.187
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

@rjstone I cut and pasted your repro into Windows PowerShell.  Calling 'su' brings up UAC to run elevated PowerShell as expected.  I'm running the same version of Windows PowerShell as you.  In alpha.10 on Windows, I see it not working.

Its work well on:
1.
PS C:> $PSVersionTable
Name                           Value

PSVersion                      5.1.14926.1000
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14926.1000
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

PS C:> $PSVersionTable
Name                           Value

PSVersion                      5.0.10240.17113
WSManStackVersion              3.0
SerializationVersion           <IP_ADDRESS>
CLRVersion                     4.0.30319.42000
BuildVersion                   10.0.10011.16384
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3

Ok, I'll clean out my profile and such to make sure that this isn't being caused by a module import or something similar. I really should have done that in the first place.

Ok, cleaned out my profiles and modules folders. Still have problems with alpha but different:

Actually, the same thing happens even if I run it directly rather than in a function.
Works fine in WindowsPowerShell now.
The first PowerShell.exe in my path is WindowsPowerShell. If I try to invoke alpha with start-process using the full path then something else happens. (For this test I didn't use RunAs.) The window appears but wont respond to keyboard input.

In the latest PowerShell Core alpha (6.0.0-alpha.12) we explicitly don't allow Start-Process -Verb, but the problem does not appear to exist without -Verb (a new console is launched as you'd expect).
#1691 is there to support -Verb


Fix segfault if pageserver connection is lost during backend startup.

See commit messages.
Fixes https://github.com/neondatabase/neon/issues/3231.

The new test case is flaky. I've disabled it for now, because I believe it's flaky because of other, pre-existing issues, not caused by the code changes here. Opened https://github.com/neondatabase/neon/issues/3273 to track one such pre-existing bug.


Error: Xvfb program was not found

running ./nimwc gives:
Error: Xvfb program was not found in /usr/bin directory, please install it
I have noX=true in config.cfg in the firejail section.
Why does it want Xvfb?

X Isolation.
You have 2 options, Install it or Disable it noX=false.
Usually is named xorg-server-xvfb or xvfb on most Linux distros.
:slightly_smiling_face:

Thank you!  I had that option backwards in my mind.
Now I get:
Mounting tmpfs on /var/lock
Error mounting /lock: fs_var.c:254 fs_var_lock: Too many levels of symbolic links
Error: proc 4901 cannot sync with peer: unexpected EOF
Peer 4902 unexpectedly exited with status 1

I'm running this on crouton on a chromebook.
Is this another firejail problem?
How can I disable firejail?
I tried nim c -d:firejail=no nimwc.nim but that didnt' do it.

Just remove the -d:firejail from the compile command.
Then is Disabled and no Firejail code is on the binary.
Everything Firejail is also gone, including its UI.
You can also set everything to false on the config.cfg

[firejail]
noDvd=false
noSound=false
noAutoPulse=false
no3d=false
noX=false
noVideo=false
noDbus=false
noDebuggers=false
noMachineId=false
noRoot=false
noAllusers=false
noU2f=false
privateTmp=false
privateCache=false
privateDev=false
noShell=false
forceEnUsUtf8=false
caps=false
seccomp=false
noTv=false
writables=false
noMnt=false
maxSubProcesses=0
maxOpenFiles=0
maxFileSize=0
maxPendingSignals=0
timeout=0
maxCpu=0
maxRam=0
cpuCoresByNumber=0
hostsFile=/etc/hosts
dns0=""
dns1=""
dns2=""
dns3=""

Thanks.  I commented out -d:firejail from nimwc.nim.cfg  and it works!
I look forward to checking this system out, it seems very cool!


GLOW

Glow dosent work i think new offsets idk maybe look for that mfg Sandro :)

Working on it :100: :ok_hand:

The list offset has moved... can you tell how do you find the offsets? Im very interisted in stuff like this

nop
i can send you a screen the glow not work

ah you update this nice work man :)


CommandFramework improperly responds when a stream is passed

A stream is allowed to be set but when you set it, the code looks to ignore it and rather would raise an error saying that a framework cannot be made without a prefix - specifically the bit seen below
client.onReady.listen((_) {
    if (prefix == null && stream == null) {
      prefix = client.self.mention;
      stream = client.onSelfMention;
    } else if (stream == null && prefix != null)
      stream = client.onMessageReceived;
    else {
      _logger.severe("CANNOT CREATE FRAMEWORK WITHOUT PREFIX");
      exit(1);
    }

I dunno how exactly the intended behaviour would be where if a stream was given and a prefix was not given. Logically I assume you would just inherit the prefix to be the bot's mention and the stream to be the given stream.
If that's the intended path of what you want to do, the final else could be changed to
else if (stream != null && prefix == null)
        prefix = client.self.mention;

instead and not stop execution because in another scenario all that would be left is stream != null && prefix != null which would be the intended action in my scenario (because I want stream & prefix to be custom)
(also as always I'm on the rewrite_modular branch)

I'll go ahead and make a pull request - but feel free to give input if this isn't what you think should happen (and something else should happen instead).


Explore more retained rendering

After finishing our first milestone of retained rendering (https://github.com/flutter/flutter/issues/21756), let's explore what more we can achieve with retained rendering. Here are some examples:

[x] Explore PhysicalShapeLayer in Fuchsia: https://github.com/flutter/engine/pull/6558
[ ] Explore if we can add an option to RepaintBoundary and improve performance significantly by using snapshot of a layer subtree that's not a child of an OpacityLayer. See https://github.com/flutter/flutter/issues/32662.

@liyuqian Can you elaborate on "Explore if we can add an option to RepaintBoundary and improve performance significantly by using snapshot of a layer subtree that's not a child of an OpacityLayer"?

@Hixie : I was thinking about raster caching the whole layer subtree for either a TransformLayer (https://github.com/flutter/flutter/issues/24627),  or an ImageFiltered layer. See https://github.com/flutter/flutter/issues/32662 for more details. @flar has been doing a lot of work recently (including introducing the new ImageFiltered layer https://github.com/flutter/engine/pull/14491). So @flar may be able to provide more details.

ImageFiltered does cache if its child layer is stable, but it is only stable if you use a RepaintBoundary.
Right now we recreate a lot of layers even if nothing changes. I'm still digging into our strategies there, but a lot of it probably hinges on the way that we manage Picture layers. They are recreated if the part of the tree they are in is visited even if they themselves don't involve any Widgets/RenderObjects that changed.
They are also created from groups of RenderObjects that are next to each other in a depth-first traversal of the tree, but that don't necessarily all descend from a single parent. If the picture was generated from a single RenderObject then we might be able to just check a flag on that object, but pictures are actually generated from a group of them and since they aren't aware that they are all contributing to the same picture together, we end up with no specific flag that can be checked to see if the picture is dirty and so we pessimistically recreate it every time we traverse the tree.
I have a change pending that can try to make a better determination if a picture is actually changing, but it is more reactive than I'd like and it doesn't have as much impact as I'd like to see. I'm still investigating its potential and thinking of alternate solutions. A preliminary version of it can be seen in a branch on my fork of the framework repo in this commit: https://github.com/flar/flutter/commit/bc131bf7b28d5c3d984b0f839e982bcd86a57cd6
If we can get our layers to be reused more then it becomes a lot more feasible to cache layer renderings in the engine with a few lines of code in the engine layers and potentially without requiring developers to use RepaintBoundary all the time.

Impeller is moving away from full scene or layer based caching. Closing as obsolete.


Missing state for membership in nested teams

Say a user is a member of team Child which is a child of team Parent, but the user is not directly a member of team Parent.
Then the imported state shows the user to be a member of both teams:
resource "github_team_membership" "Child-user" {
  username = "user"
  team_id = "${github_team.Child.id}"
  role = "member"
}

resource "github_team_membership" "Parent-user" {
  username = "user"
  team_id = "${github_team.Parent.id}"
  role = "member"
}

Adding a new user to both teams via terraform results in similar terraform state, that is the new user is shown to be a member of both teams in the terraform state. However, the result on GitHub is different: the user has been added to both teams, instead of only being a member of the child team.
How to add a user to a child team without adding them to the parent, or requiring a subsequent import?
Terraform Version
Terraform v0.11.8

provider.github v1.3.0

Affected Resource(s)
github_team_membership
Repro steps

Create two teams, by any means, one parent and one child
Add the same user to each team using terraform and apply changes
Verify that GitHub shows the user to be a member of both teams
On GitHub, remove the user from the parent team
Run terraform plan
Verify that there are no changes to apply! The two states are identical.

References
Related to #47

Hi @joebowbeer !
Thank you for submitting this issue!  I was able to reproduce this as well.  While digging into it I found a very interesting implementation in the GitHub API where, depending on the media type passed, the API will return child team members along with parent team members when requesting team members of a parent team (https://developer.github.com/v3/teams/members/#get-team-membership).  Thus, when we go to GetTeamMembership on the parent team resource, it shows the member of the child team as a member as well.
Unfortunately, the go-github SDK sets this media type for us, so I don't see how we could do this without reimplementing or forking the SDK. (https://github.com/google/go-github/blob/0573e88402f1db392537e0cbb2c79f1c03d1c6a0/github/github.go#L95)
Please let me know if you have further questions or if I can help in any way.
Thanks!

Is the SDK still unable to differentiate between the two?

hi @docwhat @joebowbeer! so the v3 github API still returns child team members w/in a parent team as referenced in the comments above; however, the github graphql api v4 provides the ability to explicitly differentiate membership types within a team (https://developer.github.com/v4/enum/teammembershiptype/) such that one can retrieve a team's immediate members vs. child_team members. It looks like adding the graphql client is in the works and tagged for v2.7.0 within the provider (https://github.com/terraform-providers/terraform-provider-github/pull/331) so a re-look at the team_membership resource's Read functionality can take place there. @jcudit or @patrickmarabeas can you confirm if an uplift for this resource is in the works or is something that can be worked on?

I have only written a teams data source so far - https://github.com/terraform-providers/terraform-provider-github/pull/339. The schema is radically different, so some discussion is probably warranted around it.

@patrickmarabeas I'd be happy to contribute to updating the team_membership data_source/resource if it hasn't been started on.

I would like some feedback on the schema before any further development effort goes into it. If you want some working code to test with - play around with https://github.com/patrickmarabeas/terraform-provider-github-v4
There's some additional work that needs to go into how we toggle v4 resources that I'm currently working on before any actual resources will make it in.

I have not looked into this yet.  I want to get this one figured out but think we should focus on a plan to toggle v4 resources first.


libuv: 1.14.1 -> 1.15.0

Motivation for this change
Changelog
Things done

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

[ ] NixOS
[x] macOS
[ ] other Linux distributions

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

I had staged that already: 63a06627

@vcunat Ah, haven’t seen that. Do you already know when this commit will land on master?

Probably around the end of this week.


[Drag] Improve UX

Try fixing some UX issues with drag & drop.
The most important found:

x offset of tooltip is put to 0 instead of original x point
change cursor appearance to adhere to browser standard
make canvas move when dragging to the bound of canvas

Closed as duplicate of #103.


Fix conf not found error when using init script to restart radosgw-agent

Init script wrongly passed conf file name recursively in restarting case, so conf file not found after re-entry init script. It should pass initial conf file path.
Signed-off-by: Zhi Zhang<EMAIL_ADDRESS>

Can one of the admins OK this pull request so I can run a build?


Event bus handle types

Types currently missing for the event bus handle and the publish method arguments.
Provide type definitions for all of the publish arguments.

Fixed in #10


Add Flex to valid achievement categories

Pull Request Test Coverage Report for Build 3133

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.919%

Totals

Change from base Build 3132:
0.0%

Covered Lines:
1447

Relevant Lines:
1493

💛  - Coveralls


android google map callout support

Does any other open PR do the same thing?

NO
What issue is this PR fixing?
https://github.com/react-native-community/react-native-maps/issues/2633
How did you test this PR?

Use the example page  [Arbitrary Views as Markers] , wait a little time, and tap the bear marker

Any ETA on when this will be tested/merged?
Can I help with something to fasten up the process?

Any ETA on when this will be tested/merged?
Can I help with something to fasten up the process?

I'm still waiting for it too. Don't know why it had taken a long time

Same issue, fix works for me, why it was not merged ?

why this is nor merge yet?

If it works. Why it not merged? Please, merge it!

please merge!

MERGE it please !!! 👍 👍 👍 👍 👍

@johnhaup any help is more than welcome :)

LGTM @christopherdro @alvelig  🐽

Pls merge! Thank you

Thank you for merging, however, I pulled the latest and it's still not working for me, am i missing something? Is anyone else getting the same issue still?
🐛 Bug Report
Package version
0.26.1
Steps to Reproduce
Add an Image component within the Callout component, and it's failing to render, only fails to render for Android, iOS works fine.
Expected Behavior
That the image renders in both Android and iOS
Actual Behavior
Image does not render in Android
Reproducible Demo
https://snack.expo.io/HJFqIAsVU

These changes have been reverted. Please see discussion in #3035

@christopherdro why these changes were reverted?
In my case the image issue on Android was solved in 0.27.0.

@piotrgomola It's possible the fix worked for some, but as for @DanLeCornu and I it did not. For the meantime I had to resort to doing the Text wrapper fix. Hoping a consistent fix gets added in though, current workarounds are less than ideal.

Thank you for merging, however, I pulled the latest and it's still not working for me, am i missing something? Is anyone else getting the same issue still?
🐛 Bug Report
Package version
0.26.1
Steps to Reproduce
Add an Image component within the Callout component, and it's failing to render, only fails to render for Android, iOS works fine.
Expected Behavior
That the image renders in both Android and iOS
Actual Behavior
Image does not render in Android
Reproducible Demo
https://snack.expo.io/HJFqIAsVU

You may need add this prop 'tracksViewChanges={true}'

These changes have been reverted. Please see discussion in #3035
@dkleikesa Can you take a look?

I tested it and it works fine, you may need to add this configuration 'tracksViewChanges={true}'

thanks! will test it out asap

I tried https://github.com/dragma/react-native-maps.git#BOUYA and version 0.27.1 and Image is still not showing on Android. Also Text wrapping was not working for me. Can someone help on this one?

I tried https://github.com/dragma/react-native-maps.git#BOUYA and version 0.27.1 and Image is still not showing on Android. Also Text wrapping was not working for me. Can someone help on this one?

Okay, wrapping with Text was not working because of flex, now I managed to fix it with static width and height, but it would be good if this is fixed and Image is supported.


the result object printing code and to_dict method are not dry

fixed with https://github.com/BrainLesion/panoptica/releases/tag/v0.5.6


[WFLY-13632] [WFLY-13633] Deploying CMR resources is not thread safe

Issue: https://issues.redhat.com/browse/WFLY-13633
Issue: https://issues.redhat.com/browse/WFLY-13632
This PR replaces pr #13525. The new PR pulls in the commit made by @gaol plus two extra commits that force a restart-required (see the commits in the PR by @bstansberry) plus one commit by myself to add a manual mode test for Brian's commits.
The reason for Brian's two commits is:
The first triggers restart-required for add or remove, but does not change the management API description. The current state is the API description is wrong, plus the behaviour is wrong. With this commit the behaviour is okay, description remains wrong.
The second commit fixes the description and bumps the API version accordingly.
Brian did this split in case we want to port this to EAP 7.3.  Bumping the API versions in a CP is very problematic; so much so that we have a rule against it. So if we do port this we can leave off the last commit.

I am OK with this PR as well, thanks :)

Thanks, @mmusgrov and @gaol !


Changing Satoshi to Luna and removing await from Wallet generation in demos.

Excellent @MatthewDLudwig, thank you!


Some minor adjusts on the front

Hey Cédric,
Loved your lil system, made some minor frontend adjustments, if you like.
Kind regards,
Lauro Sollero

Thank you Lauro!


Release 0.3

Basing this PR against the new release branch, which will only contain commits for tagged releases.

@jeffbaumes the only other reference to a version 0.2.0 in the source code is in the pycandela directory. Should we update that at this time to sync with this release?

Up to you - I'm ok with that just sitting there for now unless you plan to also host it on github.io which in that case it makes some sense to update the link. I guess pushing a hosted bundle somewhere should be part of the release process eventually but it does not need to be now.

LGTM. I am assuming "bump version number for release" is the only actual new commit here and that seems fine.

The other necessary commit will be to build the dist files. That commit
will be merged to the new release branch, while the bump version commit
will be merged back to master (simply to avoid merging the built libraries
back to master). A tiny bit messy but not too bad.
On Fri, Apr 15, 2016 at 10:03 AM Jeffrey Baumes<EMAIL_ADDRESS>wrote:

LGTM. I am assuming "bump version number for release" is the only actual
new commit here and that seems fine.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/Kitware/candela/pull/118#issuecomment-210475364

As long as the process is documented, it can be as convoluted as you like :) There is always weirdness when you have files (like the bundle) that is checked in "sometimes".

Right. My next task on master will be to document this actually :-D
On Fri, Apr 15, 2016 at 10:07 AM Jeffrey Baumes<EMAIL_ADDRESS>wrote:

As long as the process is documented, it can be as convoluted as you like
:) There is always weirdness when you have files (like the bundle) that is
checked in "sometimes".
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/Kitware/candela/pull/118#issuecomment-210476555

@jeffbaumes PTOML

ITOML, and LGTM! I verified that I can include and use the bundle in a basic HTML page.


{AKS} Fix azdev style issues for decorators

This checklist is used to make sure that common guidelines for a pull request are followed.

Fix azdev style issues for decorators (may refer to PR #7112).

Related command

General Guidelines

[ ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ ] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

AKS

Queued full live test to validate the change.


New version: Optim v1.6.0

Registering package: Optim
Repository: https://github.com/JuliaNLSolvers/Optim.jl
Created by: @pkofod
Version: v1.6.0
Commit: b61dd38bc37525a07adbfe7a2def1f1d9610c18e
Reviewed by: @pkofod
Reference: https://github.com/JuliaNLSolvers/Optim.jl/commit/b61dd38bc37525a07adbfe7a2def1f1d9610c18e#commitcomment-59105215
Description: Optimization functions for Julia

This can be closed, sorry


Appstudio update test-component-pac-mxxj

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-pac-mxxj-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
5 seconds
init

✅ Succeeded
25 seconds
clone-repository

✅ Succeeded
1 minute
sast-snyk-check

✅ Succeeded
48 seconds
build-container

✅ Succeeded
26 seconds
inspect-image

✅ Succeeded
24 seconds
deprecated-base-image-check

✅ Succeeded
55 seconds
clamav-scan

✅ Succeeded
4 minutes
clair-scan

✅ Succeeded
18 seconds
sbom-json-check

✅ Succeeded
7 seconds
label-check

✅ Succeeded
7 seconds
show-sbom

✅ Succeeded
6 seconds
show-summary

Pipelines as Code CI/test-component-pac-mxxj-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
5 seconds
init

✅ Succeeded
25 seconds
clone-repository

✅ Succeeded
1 minute
sast-snyk-check

✅ Succeeded
48 seconds
build-container

✅ Succeeded
4 minutes
clair-scan

✅ Succeeded
26 seconds
inspect-image

✅ Succeeded
24 seconds
deprecated-base-image-check

✅ Succeeded
55 seconds
clamav-scan

✅ Succeeded
18 seconds
sbom-json-check

✅ Succeeded
7 seconds
label-check

✅ Succeeded
7 seconds
show-sbom

✅ Succeeded
6 seconds
show-summary

Pipelines as Code CI/test-component-pac-mxxj-on-pull-request has successfully validated your commit.


Dont you have upgrade this library components to latest react-native version?

always shows an error in proptypes when i run this library to my latest react-native version i.e 0.26

Hello @susylPearl ,
Please, give me a screenshot of your error or at least a text copy paste.

Just create a new project with latest react native and try to use this module. React Native has moved a few imports, causing some errors. In particular, the imports for Component & PropTypes should come from 'react', not 'react-native'.
Hope this helps.

Solved: now needs react-native >= 0.29.0


In IE11, when the popper is near the viewport boundary, extra spacing is added to the page creating a scrollbar

https://codepen.io/caseyjhol/pen/BVBOVL

Steps to reproduce the problem

Click the ref element

What is the expected behavior?
The green pop element appears above the ref element and the rest of the page remains as is with no scrollbar.
What went wrong?
Extra spacing is created below the ref element, creating a scrollbar.
This appears to work properly in all browsers except IE10 and IE11.
I'm using a click listener for the popper (and showing it using display: block to make the issue easier to see, but it persists without one as well (https://codepen.io/caseyjhol/pen/VdZGRY). This issue is the cause of twbs/bootstrap#24851. I go into more detail here: https://github.com/twbs/bootstrap/issues/24851#issuecomment-392584969.

This is not a Popper.js problem, you should apply an initial position to your popper element so that it doesn't cause any overflow (usually top 0 and left 0), we can't do that in Popper.js because it would already be too late.

The problem is occurring because Popper is applying the style top: 0, left: 0 to the element. If Popper could detect the element is near the bottom edge of the viewport and set bottom: 0, left: 0 instead, the issue could be avoided.

@FezVrasta I found a way to fix this with a minimal addition of code (just a few lines). Would you be open to a PR?

Yes I'd be curious to see your proposed solution, but absolutely it's not a bug, maybe a not super clear behavior. Popper elements are supposed to be positioned (initially, by your CSS) in a way that doesn't cause overflows.

The problem occurs because of the top: 0, left: 0 styling that is applied by Popper prior to being positioned correctly via the transform property. So, even if the Popper is positioned manually beforehand, it's irrelevant, because Popper changes the positioning.

I had the same issue, but was able to get around it by disabling gpuAcceleration.
new Popper(..., ..., {
  modifiers: {
    computeStyle: {
      gpuAcceleration: false,
    },
  },
});

@craigjennings11 Awesome - looks like that works!


Remove unused import from ui/src/embeddable/inlinelist/index.jsx

There is an unused import that gives a runtime error
import Icon from "../body/Heart";

Done


Conditionally include V1 API

closes #1477
Checklist before merging

[ ] I added an appropriate entry to CHANGELOG.md
[ ] I merged main into the current branch.

https://github.com/fractal-analytics-platform/fractal-server/issues/1477#issuecomment-2107096875


Log in for private accounts

How do I enter in the username and password in secret.py? I am getting errors that there is no username and password after I directly edit secret.py. I am also running the cp inscrawler/secret.py.dist inscrawler/secret.py command after I edit.

The program reads acct/passwd from inscrawler/secret.py. Execute cp inscrawler/secret.py.dist inscrawler/secret.py and put your acct/passwd in inscrawler/secret.py.


Adding translation coverage score and json file output

@pdeziel Thank you so much for helping me review this PR 🙏 .  I made some changes based on your suggestions and have one following-up questions in the above conversation.


Can't import plugin to project

I have some problems with importing the plugin to the project. When I unzip it to the plugins folder, and try to open my project it's got the error that can't be rebuild. I have UE 4.26.1.

@kisgergo99 Have the same problem. Have you some succeed with it?

Check this https://github.com/ue4plugins/StreetMap/issues/84#issue-866834054


[EventHub]: SDK for 2022-01-01-preview api version

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

/azp run net - mgmt - ci


LoadError: UNdefVarError: iscontrol not defined

I also do not see any records of iscontrol in IRTools, so I don't know how to investigate this further.

You probably just need to pin IRTools at 0.1, or whatever version is listed in the IRTools manifest. Hopefully @Maaarcocr can update for recent changes in IRTools at some point.


BasicFormat should not be generating trailing whitespace

SwiftBasicFormat currently sometimes generates trailing whitespace in a line. That’s never what we want. We should rewrite SwiftBasicFormat in a way that fundamentally removes this problem. An implementation paradigm would be:

A first pass just gathers information between which tokens spaces or newlines (including any following indentation) should be inserted
A second pass will then apply the changes gathered in the first pass to the syntax tree

If two spaces should be inserted between tokens (e.g. because the first token requires a trailing space and the next token a leading space), it will only add a single space
If a space should be inserted followed by a newline, the space will not be isnerted

Tracked in Apple’s issue tracker as rdar://107973326

Fixed by https://github.com/apple/swift-syntax/pull/1532


Update network-tutorial-standalone.md

Fix Step 7 Detach from alpine1 instead of alpine2. Previous step is to attach to alpine1.

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Thanks for the contribution @LydellManganti. Let's ship it 🚀


Faulty links on dashboard page report

What is the current behavior?
Multiple links to external pages on dashboard page don't lead anywhere
What is the expected behavior?
The messages page, product, wishlist, help and support links are expected to lead the user to the respective pages.

@MarsIncarnate, I want to work on this.

@nirajpdn I've worked on this already but you can fix the messages page and logout behavior. You can also help make all the different pages uniform.

@nirajpdn I've worked on this already but you can fix the messages page and logout behavior. You can also help make all the different pages uniform.

Sure @MarsIncarnate , push all the updates and assign this to me as well.