Add suggestion how to convert the distro in step 12

needed ,if it was created earlier as WLS 1 distro.
just added :
If not , and your linux distro was created earlier with version 1, you can convert it in Powershell: wsl --set-version <distro> 2. Replace <distro> with the shown distro
The Problem/Issue/Bug:
Running in Error in step 12 as my distro was set up more thatn 12 month ago without wsl --set-default-version 2 before
How this PR Solves The Problem:
just tried it once and helped me
Manual Testing Instructions:
Automated Testing Overview:
as it is an optional step, only needed when Step 12 does not show the  wanted : all distros have version 2
Related Issue Link(s):
Release/Deployment notes:

Step 9 references distro with [Ubuntu] recommended. Step 12 references Ubuntu but also  ....
wsl --set-version <distro> 2`. Replace `<distro>
For consistency,  I suggest the following changes
- 9. Install a WSL2 distro from the Microsoft Store. We recommend [Ubuntu]
+ 9. Install a WSL2 `<distro>` from the Microsoft Store. We recommend [Ubuntu]
...
- 12. Double-check in PowerShell: `wsl -l -v` should show three distros, and your Ubuntu should be the default. All three should be WSL version 2.
+ 12. Double-check in PowerShell: `wsl -l -v` should show three distros, and your `<distro>` should be the default. All three should be WSL version 2.

I very much appreciate you taking the time to add this, but after consideration I don't think it belongs in ddev docs.
Also, I recommend to people to create a new distro rather than converting one. It takes absolutely forever to convert one, and who knows what might go wrong.


Mutating this.props.layouts

I am maybe doing something wrong, but I am trying to make an editor where i provide the layouts using the "layouts" props from my internal state. I then listen for changes using onLayoutChange, and update my own state.layouts which is then propagated down to the ResponsiveGrid component. Anyway
https://github.com/STRML/react-grid-layout/blob/master/lib/ResponsiveReactGridLayout.jsx#L130-L142
It looks like this code is mutating the props.layouts object, and therefore my state object is mutated in place. Is this by design. It makes it hard to create an "controlled" component.
Does my question even make sense :)

+1 -- this issue (mainly the fact that the library depends on holding/managing the current layout in its own state) makes it nearly impossible make a decent implementation using redux or similar. If anyone's done this, I would love to hear how.
belive this was also discussed in #156

I managed to get something decent working by

not letting my reducer update the modified layout if it hadn't actually changed. The library was firing off tons of useless onLayoutChange calls with identical layouts.
deep-cloning the layout passed in by onLayoutChange before putting it in state, so the library can't mutate it.

still a bit hacky, and i'd love to see the library take a better approach to state in the future

I'm with you on this - would like to do a similar approach to what I did with <Draggable>, where we expose a Core component that has no state, or make a breaking change and create a HoC like WidthProvider that does the state management.
Then consumers will simply have to listen to onLayoutChange and assign it back via state, or modify it... or do whatever they like.

great, yeah, i think for nontrivial cases most people are going to want to manage the state themselves -- having a HOC that provides the same "just works" behavior, + a stateless core would be a great approach.

Cool, i think it will clean up a lot of code when you don't have to keep state yourself. Making it more stable. And also, "everyone" in the React community is used to and expects components to work this way.

Hi, is there anyone working on this?

The library shouldn't be mutating the input layouts item anymore. It clones it and then goes to town. Please comment if you are still seeing this bad behavior.

@STRML this is great. Is the change present in release 0.13.7 ?

Yeah.
On Oct 4, 2016 2:57 AM, "Arun Kumar Jain"<EMAIL_ADDRESS>wrote:

@STRML https://github.com/STRML this is great. Is the change present in
release 0.13.7 ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/STRML/react-grid-layout/issues/178#issuecomment-251319673,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABJFPy5jgRiayQxWp-hVUyj-6iJsUiqPks5qwgbZgaJpZM4HnxUw
.

so i have been testing this a lot now and it seems to be good :)

Hi guys, sorry to "reopen" this issue, but 0.17.1 still mutates the state. It adds some new breakpoints when non are defined. I would also love a version, where the component is stateless and we can manage our own state. Outside drag is ideal candidate for such a behavior.


Refactoring Model

We need a class to represent the model/rd visualiaztion. It holds the list of disks that are currently stored in the JQA2RD class. It needs a write method to be written to the database. Similar to the disk and disksegment classes we need testcases for this as well.

Model and ModesTest are done.


fix: fix peer dependency typeorm

:tada: This PR is included in version 1.4.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


automaticList error pops up on markdown files

Hi,
I have an issues that stops me from editing my markdown files since the upgrade to 1.31
Every time I hit the  key for a new line, the error in the image pops up.
I checked the issues, but I don't have the insiders build sorry.
This error happened since the upgrade to 1.31

VSCode Version: 1.31
OS Version: macos 10.14.3

Steps to Reproduce:

Open markdown file
press the  key

Launch with code --disable-extensions to check.
Yes it does

Apologies - after another crash start of the program, the issues didn't appear.


Contents of top app bar are not vertically centered on home screen

Normal screenshot

Layout bounds enabled screenshot

@akshay2211 mind if I open PR to fix this or do you already know about it?

@mddanishansari thanks for trying paper
Contribution from your side would be appreciated.


Minimize the scope of some string consts

Help prevent "duplicate symbol" linker errors when this code is included more than once in an app (because one or more included libraries also includes this code).
Note that this set of changes does not solve the entire problem. There are several other string consts which are declared in the .h file. So if an app and one of its libraries both include a copy of this code, then one or both of them will need to rename those string consts to prevent linker collisions.
If there's not a clever technical fix (none has yet occurred to me), then another thought would be to modify the names of all these strings consts. For example OnePasswordAppExtensionURLStringKey -> YourAppPrefixOnePasswordAppExtensionURLStringKey, so as to at least suggest what each developer should do. (Use of preprocessor string concatenation, to improve DRYness, is also left as an exercise for the reader.)

Hey there; as I scuffed quite a bit when I saw all these #defines I’m wondering if it’s really worth it for such a corner case? Maybe it’s because I don’t understand why a library/framework should include the OnePasswordExtension code in the first place?
However to resolve the issue in a more graceful manner I think that the real technical solution would be for the third party libraries to include the code using git’s subtree feature. Much like how one adds libextobjc: https://github.com/jspahrsummers/libextobjc#adding-to-your-project. This way we could keep everything which proper constants give us: types better Swift integration (e.g. using an enum for the error codes) and what not.
That way the library could quite easily add its own prefix to the constant and still be able to merge in new changes. Usage for the library maintainer would look something like:
$ git remote add onepasswordextension https://github.com/AgileBits/onepassword-app-extension.git
$ git fetch onepasswordextension
$ git read-tree --prefix=External/ -u onepasswordextension/master
$ git reset

And when it’s time to bring in new changes the maintainer would perform:
$ git fetch -p onepasswordextension
$ git merge -Xsubtree=External/ onepasswordextension/master
$ git reset

The changes (prefix and such) would probably need to be re-added at this point.

Maybe it’s because I don’t understand why a library/framework should include the OnePasswordExtension code in the first place?

In our case, the library is the PayPal iOS SDK, which a developer can add to their app to enable payments via PayPal (not entirely a corner case these days). When the user logs into their PayPal account, the SDK allows them to use 1Password to do so.

However to resolve the issue in a more graceful manner I think that the real technical solution would be for the third party libraries to include the code using git’s subtree feature.

Sorry, but I'm not understanding this suggestion. Whether we use git subtrees or not, we will run into the problem re duplicate symbols.

The changes (prefix and such) would probably need to be re-added at this point.

The point of this pull request was to eliminate the need for anyone to add any changes (e.g., symbol prefixes).


header/p2p: limit Head request in header.Exchange

We should limit a Head request on the caller side.

This is about header/sync.Syncer calling the Head which should be limited with a context deadline.

Was done in https://github.com/celestiaorg/go-header/pull/152


[e2e]: generic push branch1 default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/branch1
Run: https://github.com/slsa-framework/example-package/actions/runs/7720627042
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.push.branch1.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.push.branch1.default.slsa3.yml
Trigger: push
Branch: branch1
Date: Wed Jan 31 03:09:12 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/branch1
Run: https://github.com/slsa-framework/example-package/actions/runs/7720627042
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.push.branch1.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.push.branch1.default.slsa3.yml
Trigger: push
Branch: branch1
Date: Thu Feb  1 01:31:28 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/branch1
Run: https://github.com/slsa-framework/example-package/actions/runs/7735655647
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.push.branch1.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.push.branch1.default.slsa3.yml
Trigger: push
Branch: branch1
Date: Thu Feb  1 03:11:15 UTC 2024
Tests are passing now. Closing this issue.


Ideas for Physics Based Games

Pinball

2D Open Source

Minigolf

1 level
Detailed experience but no source code | Issues with the physics engine

Sport games

Other interesting links:

Packt Godot Engine book
Udemy course about creating quick games | Udemy courses

Curling
Petanca
Robot combat

Taking a quick look in internet, several people had the same idea and there are interesting experiences with Godot y several of this mini games. I am adding them to the original entries.

Could be possible simulate a robot combat in Minecraft?
With magicavoxel animations for example?

Hmmm, in Magicavoxel you can no create animations AFAIK. You can create the robot models that can be imported in Minecraft. But the animations should be done in Minecraft, and more concretely, from McThings.


Fix for old merge request syntax using inheritance

when a sole 'approvals_before_merge' settings is inherited/overwritten.
Also change an order in the transformed config from to put 'merge_requests_approvals' before 'merge_requests_approval_rules' (although I does not affect processing order, but it seems to be more logical).

Codecov Report

Merging #481 (943490d) into main (e68f4bd) will decrease coverage by 42.46%.
The diff coverage is 100.00%.

Additional details and impacted files

@@             Coverage Diff             @@
##             main     #481       +/-   ##
===========================================
- Coverage   84.48%   42.01%   -42.47%
===========================================
  Files          70       70
  Lines        2643     2644        +1
===========================================
- Hits         2233     1111     -1122
- Misses        410     1533     +1123

Impacted Files
Coverage Δ

gitlabform/configuration/transform.py
84.24% <100.00%> (-12.10%)
:arrow_down:

...abform/processors/group/group_members_processor.py
15.11% <0.00%> (-83.73%)
:arrow_down:

...tlabform/processors/multiple_entities_processor.py
20.25% <0.00%> (-75.95%)
:arrow_down:

gitlabform/lists/projects.py
20.58% <0.00%> (-73.53%)
:arrow_down:

gitlabform/lists/groups.py
26.19% <0.00%> (-71.43%)
:arrow_down:

...tlabform/processors/project/schedules_processor.py
21.15% <0.00%> (-71.16%)
:arrow_down:

gitlabform/processors/project/members_processor.py
16.92% <0.00%> (-69.24%)
:arrow_down:

...labform/gitlab/project_merge_requests_approvals.py
20.83% <0.00%> (-66.67%)
:arrow_down:

gitlabform/gitlab/branches.py
22.80% <0.00%> (-64.92%)
:arrow_down:

gitlabform/processors/project/files_processor.py
22.32% <0.00%> (-64.29%)
:arrow_down:

... and 51 more


Property Correction

Category

[x] Content fix
[ ] New article
Related issues: fixes #2847

What's in this Pull Request?
Changed the detailed syntax to use hideColumnHeader from hideListHeader. Although both work, the preferred/supported syntax is hideColumnHeader

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/declarative-customization/view-formatting.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

thx Chris, appreciated.


Change raw_to_displayed to only compute colours for all labels when required

Rather than passing the whole image through low_discrepancy_image, we compute the colours once for all possible label values, and only if the max has changed.
This is likely to still be slow as we are computing np.max() on a potentially very large array.
One option to improve this is to try directly indexing into the self._all_vals, and only when this throws an IndexError do we recompute the maximum. This will be very slow, but hopefully infrequently - only when a new label colour is added.

Ok so @jni @sofroniewn I've fixed the tests and done some benchmarking and profiling.
The benchmarks have... mixed results. I've ran it against master a few times now and it's anyone's guess as to whether it will report no significant change, an improvement, or a decrease in performance.
However, I profiled 1000 set_view_slice calls in a (100, 4000, 4000) layer and this branch took 0.1024s per call as opposed to master's 0.4474s so... :shrug: . I'm not sure why we're not seeing the same improvement with the benchmarks.
Note - this version of raw_to_displayed can only work with integers, so float labels would no longer be a possibility. Personally I think this is okay, since the only float labels we were ever testing were integral anyway and a result of np.zeros or np.ones calls. Curious what others think as well though.

I just tried it out, I feel like i notice a subtle improvement in painting in a 2048 x 2048 image, which is good. I'll give this a detailed review tomorrow. For the float, can we just detect  and internally call astype(int)? We might want to do that just once on load or setting and emit a warning?

We could detect on __init__ whether the data is float type. We could try cast to integer and warn, and if the cast fails, throw an error. The only thing we don't want to be doing is casting in _raw_to_displayed.

@jni fixed up those two comments and also added a few extra tests for those code paths.

🙏 🚀


Fully automate the release process

Description:
Automatically close and release as part of the Maven deployment stage using nexus-staging-maven-plugin as described here: https://central.sonatype.org/publish/publish-maven/#nexus-staging-maven-plugin-for-deployment-and-release.
Expected outcome:

Releasing doesn't require any manual step.
All contributors can release without requiring intervention from a single person.

Thanks for releasing 2.2.0 @acm19 !

I'll take on documenting the manual parts of this for now once I get maven access.

This one is about releasing with a fully automated process, unfortunately I've been swamped lately, so haven't been able to make the changes :(


Mingw update

This PR fixes up conflicts and makes possible to build without extra defines (necessary to build simply with other build systems).
If you merge this than it offers to the main repository automatically.

Thank you!


Telegram integration

Telegram its opensource and very used, i think it would be a good alternative for secure and cheap notifications.

Yes sure, would you like to propose a pull request?

@BDav24  In addition, it would be nice to add other socials. List of examples written for laravel https://github.com/laravel-notification-channels


Missing declarations for SCRIPT_BEFORE_REQUIRED and SCRIPT_AFTER_REQUIRED flags

The commits added by the #141  work as expected, but there is a lack of relevant declarations in action.yml, leading to:

VS Code prompting Invalid action input 'SCRIPT_BEFORE_REQUIRED' and Invalid action input 'SCRIPT_AFTER_REQUIRED'
GitHub Action execution displaying a warning: "Unexpected input(s) 'SCRIPT_BEFORE_REQUIRED', 'SCRIPT_AFTER_REQUIRED', valid inputs are ['SSH_PRIVATE_KEY', 'REMOTE_HOST', 'REMOTE_USER', 'REMOTE_PORT', 'SOURCE', 'TARGET', 'ARGS', 'SSH_CMD_ARGS', 'EXCLUDE', 'SCRIPT_BEFORE', 'SCRIPT_AFTER']".

Therefore, I have added the relevant declarations in the PR to fix this issue.

Shouldn't this be closed as completed after #178 was merged + a release went out with the fix?

release at v5.0.2


Hide pour over selectors

Similar to espresso, some fields may not be desirable. Add option to hide them

The only thing that I think should be hidden is "paper filter" and that's already free from the refactor. No work needed.


Light Switch

Hi, I have this hubspace device all over my phone. Is there any way for me to get it working with this plugin?
https://www.homedepot.com/p/Commercial-Electric-500-Watt-Single-White-Pole-Smart-Dimmer-with-Motion-Sensor-Powered-by-Hubspace-HPDA311CWB/317249353

Please

Has any one looked into this? I also have this switch, I can get it to work in homebridge but I only have 'On/Off' and no ability to use the 'dimming' feature.


Fix cache invalidation for Flow.run(ignore_fresh_input=True)

We decided to swtich from the cache_keys concept currently implemented to storing input_hash+cache_fn_hash for tasks and to rely on the fact that the transport from output_json to next task's input_hash is always going through the database. And cache hashes in the database only change if the task producing a certain input was invalidated.

@NMAC427 which hashes should we use for memoization? If we just use the input_hash, rerunning the same task will yield the exact same result for the same input. Like this it is for example impossible to write a random number generator as task and to expect that it will yield different outputs within one stage. On the other hand if it has a @materialize(cache=fn) function, then it appears like the multiple instances of the task would be called in the exact same moment producing the exact same result. I think this behavior is ok.
        ctx = RunContext.get()
        with ctx.task_memo(task, task.input_hash) as (success, memo):

I think this is the place where task cache key and query str are combined into one hash: base.py:394
        return compute_cache_key("LAZY-TABLE", table.cache_key, query_str)

This essentially means that when we store a cache_key in a Table object, then it must be the correct combination of input_hash, version, and cache_fn_hash according to ignore_fresh_input parameter. The name Table.cache_key, however, may be misleading for this kind of use.

The Flow.run(ignore_fresh_input) option is read in two places.

for Eager:

    def retrieve_task_metadata(self, task: MaterializingTask) -> TaskMetadata:
        # noinspection PyUnresolvedReferences
        ignore_fresh_input = RunContext.get().ignore_fresh_input
        try:
            with self.engine.connect() as conn:
                result = (
                    conn.execute(
                        self.tasks_table.select()
                        .where(self.tasks_table.c.stage == task.stage.name)
                        .where(self.tasks_table.c.version == task.version)
                        .where(self.tasks_table.c.input_hash == task.input_hash)
                        .where(self.tasks_table.c.cache_fn_hash == task.cache_fn_hash if not ignore_fresh_input else sa.literal(True))
                        .where(self.tasks_table.c.in_transaction_schema.in_([False]))
                    )
                    .mappings()
                    .one_or_none()
                )

For Lazy:

            # Do the materialization
            if isinstance(x, (Table, RawSql, Blob)):
                x.cache_key = task.get_effective_cache_key(ctx)

    def get_effective_cache_key(self: Task, ctx: RunContext):
        if ctx.ignore_fresh_input:
            return self.input_hash + self.version
        else:
            return self.input_hash + self.version + self.cache_fn_hash

@NMAC427 I think here we still have a problem: table/base.py:225
            # Try retrieving the table from the cache and then copying it
            # to the transaction stage
            metadata = self.retrieve_lazy_table_metadata(
                lazy_cache_key, table.stage
            )

We only store one cache_key for the Lazy table. But we need to only look whether the task was cache valid and the query_str was cache valid. So point 2. from previous comment is actually wrong:
            if isinstance(x, (Table, RawSql, Blob)):
                x.cache_key = task.get_effective_cache_key(ctx)

I propose this solution:
        # Store table
        try:
            if not is_task_cache_valid:
                raise CacheError(f"Task producing table '{table.name}' is not cache valid")
            # Try retrieving the table from the cache and then copying it
            # to the transaction stage
            metadata = self.retrieve_lazy_table_metadata(
                lazy_query_hash, table.stage
            )
            self.copy_lazy_table_to_transaction(metadata, table)
            self.logger.info(f"Lazy cache of table '{table.name}' found")
            store_id = metadata.store_id
        except CacheError as e:
            self.logger.warning("cache miss", exception=str(e))
            # invalidate downstream tasks reading this table with UUID in metadata
            store_id = uuid.uuid4().hex[:20]

            # Either not found in cache, or copying failed -> fallback
            self.store_table(table)

        # Store metadata
        self.store_lazy_table_metadata(
            LazyTableMetadata(
                name=table.name,
                stage=table.stage.name,
                query_hash=lazy_query_hash,
                store_id=store_id,
            )
        )


build(drag-drop): remove incorrect and unnecessary typings file from tsconfig

This allows build scripts (e.g. gulp material:build-release) on the ivy-2019 branch to complete successfully.

cc @devversion

Closing since ivy-2019 branch is now obsolete


Forbidden value, forbidden key and required key check cannot use a scope

Forbidden value and forbidden key can use regular expressions for the value and key resp., however, they cannot define a scope / (nested) dictionary where they should or should not be located.
Similarly, requiredKeyCheck can select for a parent key/value, however not for a scope/(nested)dictionary.

I would suggest to use a regular expression for the scope. Example:
my-service:
  my-endpoint:
    connectionTimeout: 3000

we want to check if value < 1000 ms (violation when match \d\d\d\d) for such a key, however, not when it is defined as such:
spring:
  datasource:
    hikari:
      connectionTimeout: 5000

So, not when inside a scope containing 'hikari' or 'datasource'.

Other example,
resilience4j:
  circuitbreaker:
    minimumNumberOfCalls: 10
    failureRateThreshold: 50
    permittedNumberOfCallsInHalfOpenState: 2
    waitDurationInOpenState: 60
    slidingWindowSize: 20
    waitInterval: 30

We want to forbid the key 'waitInterval' because it is invalid and require the key 'waitDurationInOpenState'. Yet, we want to make sure this is checked only within resilience4j:circuitbreaker, preferable matching with a regex.
Furthermore, we like to do range checking for the property values, but maybe that is possible with regex already.

Created a solution with included-ancestors and excluded-ancestors fields for the template checks, and a InValueInRangeCheck. To be a PR.

Unit tests are all green


[BEAM-11157] Write Schema enum to BigQuery string field

Currently it is an error to try to write a Schema enum to a BigQuery table.  This enhancement will write a Schema enum value to a BigQuery string field.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[X] Choose reviewer(s) and mention them in a comment (R: @username).
[X] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

A Schema enum is written to a BigQuery string field, but the same BigQuery string field is read back into a Schema string field.  I'm not sure if there is a practical/good way to recreate the Schema enum when reading from BigQuery.  Would that be a requirement for this enhancement?
Brainstorming options:

The enum value set could be stored in the BigQuery field description, but this is brittle because the description can be altered/corrupted by third parties.
Add a method SchemaConversionOptions.setParseEnums(Map<String, Enum<E>>), but this assumes that an enum value is never renamed or removed.  What to do with a value in the BigQuery table that no longer maps to a value in the provided enum?  Create EnumerationType.Value(-1) and the user will see the value as null?  Add the unexpected value to a new EnumerationType instance (if practical to update the Schema while iterating TableRows)?

R: @apilloud


Push permission

Please give me push access, so I can push the init project

There seems to be a bug with adding individual members, so I have added a team

You will need to accept the invite to the team first I believe, should be a notification of some kind


Appium tests stability improvements

I'm not sure if this is a limitation of the way appium injects functions, but since the promise-related callbacks seem to be the same for iOS and Android, can they be moved to a common location?

@riknoll addressed both of your comments


[Feature Request] ESC to close the last Hover Editor Window

More often than not, I want to check multiple pages with the hover editor but whenever I want to close and open a new page I need to move the cursor out of the hovering link and the hover editor window and wait for the delay until the window closes before opening a new one.

I second this request. I sometimes find myself inadvertently triggering hover editor when beginning to use a keyboard shortcut for something else. (For example, when I use my keyboard shortcut to go back from a note I clicked the link of.) When that happens, it blocks me from being able to do anything in the main note until I go to the mouse and move it away form the link it's over.
So it would be nice to be able to dismiss it with ESC (and/or a customizable hotkey combo) when I'm either done with it or didn't intend to summon it to begin with.

would also love to see this. holding down the esc key for a second or two with a ui indicator (like loading bar) could be a fun user experience too, but just being able to press esc to close them would be very useful!


Fix Proxy Tickets Issue Where After Being Issued They Are Already Used/Expired Immediately

Closes #1966 and #1963

Brief description of changes applied: Set the ProxyValidateController's validationSpecification field (on line 198) to cas20ProtocolValidationSpecification instead of this.cas20WithoutProxyProtocolValidationSpecification.
Any documentation on how to configure, test: Run MultiLevelProxySpec.groovy to validate.
Any possible limitations, side effects, etc: None/Unknown
Reference any other pull requests that might be related: Includes a fix for #1963 where the Travis build failed for some unknown issue.

Very good. Much appreciated.
So, the entire batch of tests you have at the moment: everything passes for master?

My cas-functional-tests all do pass.  I am going to check those into the 5.0.x branch of: https://github.com/wcrowell/cas-functional-tests

Perfect. Thank you for the good news! What is your email address by the way? And if you find the time, could I ask you to jump on Gitter?


Clicking popovers scrolls up

Reproduction steps:

Scroll down (but not so far that all tooltips disappear)
Click on a tooltip
The screen scrolls up

Fixed in 17c784882d702fa9d9f221eb1c06329bbfe2b545

@jacobnewsted fixed with new pop-over system


Support multiple git repositories

It seems like its not possible to have Git support if the actual repo lives in a subfolder of the project.
My current Folder structure look like this:
Project/
  GitRepositoryWithTheCode/
  DesignerStuff/ (images, etc)
  Documentation/
  ect../

In this setup, the GitRepo is not tracked, so sadly I cannot use the benefits of this feature :(
Did I missed some configuration, where I could map the git repo to the GitFolder?

Yes, unfortunately this doesn't work. You need to open Code at GitRepositoryWithTheCode.

@joaomoreno It seems that nobody cares about this.
Is there a solid reason for which the design should not change to meet all users' needs? Why not handle git repositories from sub-folders?
In my case I have a root folder called Projects in which I have multiple git repositories. There are too many to open them separately in different windows and switching between them is pretty annoying. I'm really dissapointed seeing that this hasn't been fixed yet and voting is closed on uservoice.com: https://visualstudio.uservoice.com/forums/293070-visual-studio-code/suggestions/9483534-recognize-git-repositories-in-nested-folders

Seems like a duplicate of #396...

@jlk #396 may be related but there are two different issues:

Cannot open multiple folders (/tmp and ~/Projects for example)
I cannot manipulate different Git repositories somewhere inside my opened folder. Notice that the Git repositories may be at different levels from the opened folder. Example:

Projects/
  project1/
    .git
    lib/
      .git
      lib.c
    main.c
    a.out
  project2/
    component1/
      .git
      file0
    component2/
      .git
      file1

@aalexgabi Yep - fair point. Seems like #2 is a subset of #1, but I see now that they're not full duplicates of each other.

I too requires this feature.  All my code is modules or "microservices" inside a company folder.  I have 40+ projects, not practical to have 40 code windows open one to each individual folder.  This is why I keep going back to sublime, because it recognizes the git repo of the FILE you are currently working in, no of the root of your "project".

I am also facing the same problem in VS Code. Are there any plans by MSFT to address this? Support for multiple folders without having to pack your projects into the same root folder, could possibly fix this I guess?

Me too. I've never used the GIT features of VS Code because my projects all consist of multiple repos.

Closing as a duplicate of #396. Supporting multiple workspaces will enable working with multiple Git repositories.


How to refresh/re-render previous scene after pop() the current scene.?

Version
Tell us which versions you are using:

react-native-router-flux v4.?.?
react v16.?.?
react-native v0.?.?

Expected behaviour
Actual behaviour
Steps to reproduce
For non-obvious bugs, please fork this component, modify Example project to reproduce your issue and include link here.
1.
2.
3.
Reproducible Demo

Please provide a minimized reproducible demonstration of the problem you're reporting.
Issues that come with minimal repro's are resolved much more quickly than issues where a maintainer has to reproduce themselves.

show which versions you are using first please
react-native-router-flux v4.?.?
react v16.?.?
react-native v0.?.?

react-native-router-flux: v4.0.6
react-native: v0.59.9
react-native: v16.8.3

same issue

@uplamartya have you solved it?

Previously I was not using redux, so it was necessary to refresh/re-render the previous Scene on pop() of the current scene. But, later on, I achieved this with redux.


⚠ Bofrost.at has degraded performance

In 23cdfaf, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2332 ms

Resolved: Bofrost.at performance has improved in e85f9f2 after 20 minutes.


Label text overflows when uploading multiple files in iOS Safari

I noticed when doing some testing that when using iOS Safari, if you upload multiple image files (which have pretty long names when stored in Photos), the text overflows the label and isn't hidden.
I propose something like:
.custom-file-label {
    white-space: nowrap !important;
    overflow: hidden !important;
    text-overflow: ellipsis !important;
    padding-right: 25%;
}

The padding is optional but I think it looks better truncated with an ellipsis. This was the easiest way to achieve that.

Hi @alstr
bs-custom-file-input is just a JavaScript lib, for CSS changes please open an issue on Bootstrap


CE Fails to Load

CE doesn't come up with the current version 4.01.  I've had to go back to 3.1.1 in order to have CE come up with I push on the CE 'jazz hands' button.
I've confirmed with FTC that the offending module is CE.  I unloaded all modules but CE and required modules, and ran FTC.  FTC indicated it was one of the ones I ran.  I also ran FTC with the modules listed in this error message, and it still confirmed that CE was what caused the error.
Expected behavior:  I click on the CE button and can use it to change conditions and attendant effects on my tokens.

Bah! Thanks, fixed in 4.0.2.


[Fix] Load support ServiceProvider

Codebase does require filament-support::grid but tests do not register the ServiceProvider

Thanks!


[SPARK-48350][SQL] Introduction of Custom Exceptions for Sql Scripting

What changes were proposed in this pull request?
Previous PRs introduced basic changes for SQL Scripting. This PR is a follow-up to introduce custom exceptions that can arise while using SQL Scripting language.
Why are the changes needed?
The intent is to add precise errors for various SQL scripting concepts.
Does this PR introduce any user-facing change?
Users will now see specific SQL Scripting language errors.
How was this patch tested?
There are tests for newly introduced parser changes:
SqlScriptingParserSuite - unit tests for execution nodes.
Was this patch authored or co-authored using generative AI tooling?
No.

thanks, merging to master!


Android Crash

Godot version:

Godot 3.0.2 stable
OS/device including version:

Samsung Galaxy A7 2017 ,Android 7.0
Issue description:

When I run the game on android the splash screen blinks and the game closes
Steps to reproduce:
Minimal reproduction project:

Is the Samsung Galaxy an Adreno device? Is the game 2d or 3d?

No, the graphics card is ARM Mali-T830 MP3, and it's a 2D game.

No, the graphics card is ARM Mali-T830 MP3, and it's a 2D game.

You should run adb logcat to see the output from Godot. Otherwise it's impossible to know what's happening.

It was nothing, it was the JDK that is outdated, anyway thanks for the support. :)

@NedJaims Is this issue fixed then?

I'm closing this since this issue is resolved.


[action][match] match_nuke action - Nuke your certificate and provisioning profiles (via match)

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context

Motivation
Allow user to use api_key / api_key_path to match nuke to use App Store Connect JWT Auth
Context
Problem1: Nuke certificate and provisioning profiles using match nuke CLI command is crazy
fastlane match nuke development --passing here AppStoreConnect API key details

Problem2: match nuke CLI command with app_store_connect_api_key (@joshdholtz's lovely action) is almost impossible
Description

Introduce a new action match_nuke to easily nuke certificate and provisioning profiles (via match)

Testing Steps

lane :renew_certificate do
   ENV["MATCH_TYPE"] = "development"

  app_store_connect_api_key(
    key_id: "D383SF739",
    issuer_id: "6053b7fe-68a8-4acb-89be-165aa6465141",
    key_filepath: "./AuthKey_D383SF739.p8",
    in_house: false
  )

  # Automatically loads Actions.lane_context[SharedValues::APP_STORE_CONNECT_API_KEY]
  match_nuke
  match
end

Thank you very much for reviewing this PR! 🙇♂ @joshdholtz

I’m so torn about this 😱 I didn’t think I was going to like this as an action but... I kind of like this as an action 🤔
I’m very conflicted on a few fronts...

The action sub commands (like match nuke) should be automatically made as actions somehow because that would make mike it easier on everyone so they don’t need to be created like this

That will be really really great and perfectly make sense! but I am guessing it might require lots of testing and lots of effort. because of many sub-commands. maybe we can make a goal for 2021 or something in the Fastlane roadmap.

The naming might need to also be aliased because of match and sync_signing. I mean... I think match_nuke makes enough sense but 🤷♂

I agree! I name it match_nuke to be consistent with fastlane match nuke  sub-command and easily recognizable/readable by name what this action will do.

I think that fastlane match nuke should be able to be easily called with the --api_key_path option. With this option you just need to point to a JSON file which contains the same info that the app_store_connect_api_key action takes - https://docs.fastlane.tools/app-store-connect-api/#using-fastlane-api-key-json-file

The main problem is Security team does not allow JSON file under Git commit and most of the CI (i.e CircleCI, GitHub action) just support to store secrets in ENV variables ONLY.
Of course, there is always a way, i.e Create the JSON file first using CI ENV variables and run the nuke sub-command but that will defeat the purpose of this action Easily nuke certificate and provisioning profiles (via _match_)

I’m do still like this PR and I just want to make sure that everything is thought about before merging 😊

Agree! Thank you very much for taking your time, really appreciate it! Also if this action does not make sense then don't worry I will close the PR 😉 [The best way is to support all subcommands as action, but I don't know yet how to do that 😬]

So if you have any thoughts/concerns on my thoughts/concerns that would be great to hear!

Please see some input inline and let me know if this action can merge or not. 😇
Thank you again!

@crazymanish

The main problem is Security team does not allow JSON file under Git commit and most of the CI (i.e CircleCI, GitHub action) just support to store secrets in ENV variables ONLY.

Ahhhh, this makes sense on why it’s almost impossible mentioned in your description 😊 Thanks for explaining that!

I’m having such a internal struggle with this lol 😛 I had two other thoughts that you could put this in the fastlane/actions directory of your own project but... this is probably a thing that others would use. I then thought that you could make this a plugin but... its such a core fastlane thing that it should just be made an action (which is where we are at right now 🙃 )
Making the sub commands all actions would be ideal but would be a lot of work sooooooo...
I think that last thing that is holding me back is making this almost too easy for people to delete all of their certificates when they really didn’t mean to. I use match nuke pretty often myself but its my own team where things really don’t matter. Do you have any thoughts if making this too easy would cause any problems?

The main problem is Security team does not allow JSON file under Git commit and most of the CI (i.e CircleCI, GitHub action) just support to store secrets in ENV variables ONLY.
Of course, there is always a way, i.e Create the JSON file first using CI ENV variables and run the nuke sub-command but that will defeat the purpose of this action Easily nuke certificate and provisioning profiles (via match)

I do understand this concern. However, it does support environment variables to inject App Store Connect API key settings. You can inject .p8 file as a string so don't need to store/keep a file somewhere insecure🙂 (The document page hasn't got enough explanations about it.)
export APP_STORE_CONNECT_API_KEY_KEY_ID=
export APP_STORE_CONNECT_API_KEY_ISSUER_ID=
# You need to combine multiple lines of .p8 file's content with "\n"
export APP_STORE_CONNECT_API_KEY_KEY=

https://github.com/fastlane/fastlane/blob/e6fc532712772f574636492bd3a9e209344854c8/fastlane/lib/fastlane/actions/app_store_connect_api_key.rb#L49-L68

The main problem is Security team does not allow JSON file under Git commit and most of the CI (i.e CircleCI, GitHub action) just support to store secrets in ENV variables ONLY.
Of course, there is always a way, i.e Create the JSON file first using CI ENV variables and run the nuke sub-command but that will defeat the purpose of this action Easily nuke certificate and provisioning profiles (via match)

I do understand this concern. However, it does support environment variables to inject App Store Connect API key settings. You can inject .p8 file as a string so don't need to store/keep a file somewhere insecure🙂 (The document page hasn't got enough explanations about it.)
export APP_STORE_CONNECT_API_KEY_KEY_ID=
export APP_STORE_CONNECT_API_KEY_ISSUER_ID=
# You need to combine multiple lines of .p8 file's content with "\n"
export APP_STORE_CONNECT_API_KEY_KEY=

https://github.com/fastlane/fastlane/blob/e6fc532712772f574636492bd3a9e209344854c8/fastlane/lib/fastlane/actions/app_store_connect_api_key.rb#L49-L68

@ainame
I know, we can store .p8 file's content with "\n" as String in the ENV variable but passing those ENV variable values to fastlane match nuke sub-command is really crazy and this is exactly what I mentioned in the PR description 😉

I think that last thing that is holding me back is making this almost too easy for people to delete all of their certificates when they really didn’t mean to. I use match nuke pretty often myself but its my own team where things really don’t matter. Do you have any thoughts if making this too easy would cause any problems?

@joshdholtz
Personally this what I believe, people might be using match nuke command once in a year, but code-signing is real pain from Day1 and Fastlane is a lifesaver from Day1.
AppStore API connect KEY is the future and pretty sure people will use the API_KEY more & more.
match_nuke action is for that day when suddenly people realize their certificates are expired and what to do next...how to renew using API_KEY, that moment people will proud of Fastlane again because match_nuke will be lifesaver again on that day. 😇

@crazymanish

I know, we can store .p8 file's content with "\n" as String in the ENV variable but passing those ENV variable values to fastlane match nuke sub-command is really crazy and this is exactly what I mentioned in the PR description 😉

Oh, I got what you mean. This is actually a good point✅ I personally use only custom lanes on my own Fastfiles so didn't notice it.
Regarding how to pass API key via CLI, another option I can suggest is adding all of the options that app_store_connect_api_key action has to other ASC API kRaey compatible actions. That way it enables not only match nuke  command to be able to pass ASC API key settings via environment variables (with what I explained) but also other main modules of fastlane (deliver, sigh. pilot, ...) and some actions using it. Or it might be good that we can make it possible to inject JSON content with a single option like api_key_json (APP_STORE_CONNECT_API_KEY_JSON) rather than giving key_id, issuers_id, etc.. individually.
https://github.com/fastlane/fastlane/blob/e6fc532712772f574636492bd3a9e209344854c8/fastlane/lib/fastlane/actions/app_store_connect_api_key.rb#L49-L87
If we make some helper that returns the set of options for ASC API key, it's not something that we have to worry about too much about duplication or misaligned.
@joshdholtz What do you think about ^ option?

Either way, match_nuke action itself sounds good to me. If the concern remains, we can prompt the "y/n" question by default (and prepare "force" option for CI)?

Either way, match_nuke action itself sounds good to me.

Thank you @ainame 🙇♂

If the concern remains, we can prompt the "y/n" question by default (and prepare "force" option for CI)?

match_nuke action is using match options, so we don't need to introduce anything. 😇
# for local: It will ask for confimation with "y/n" question before nuke
# see for more details: https://github.com/fastlane/fastlane/blob/master/match/lib/match/nuke.rb#L85
match_nuke(
    type: "development",
    api_key: app_store_connect_api_key,
    read_only: false,
    force: true
)

For CI, we can pass additional skip_confirmation param
match_nuke(
    type: "development",
    api_key: app_store_connect_api_key,
    read_only: false,
    force: true,
    skip_confirmation: true
)

@googlebot I consent.


Add context timeout logging

We have seen twice now that short timeouts on context to frontend creates an issue with the cadence service. In order to get insight into this issue logging needs to be added showing what the timeout is on the given on context.

Finished


Port useful changes from foolip/mdn-bcd-collector

I can't submit a PR because this repo isn't recognized as a fork. But I've prepared a commit that you can easily apply:
https://github.com/foolip/mdn-bcd-collector/commit/0541cab28e0a0f66af0dc5c9c7816b4a1926382f

I've run through the commit and implemented the changes I think are useful.


Getting pub: command not found after using setup-dart within Github Actions

I had been using this action for some time now, and everything was working fine until today I noticed that my actions were failing.
I have not changed the action yaml file, so was wondering what could be causing this error.
Here is the action file that I am using:
name: Test

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]
  workflow_dispatch:

jobs:
  test:
    name: Test / OS ${{ matrix.os }} / Node ${{ matrix.node }} / SDK ${{ matrix.sdk }}
    strategy:
      matrix:
        os: [ubuntu-latest]
        node: ["12"]
        sdk: [stable, beta, dev]

    runs-on: ${{ matrix.os }}

    steps:
      - name: Checks-out repo
        uses: actions/checkout@v2

      - name: Setup Dart
        uses: dart-lang/setup-dart@v1
        with:
          sdk: ${{ matrix.sdk }}

      - name: Install dependencies
        run: pub get

This action fails with the following error:
/home/runner/work/_temp/f9745214-a5f6-41e6-a039-c51f64d69379.sh: line 1: pub: command not found
Error: Process completed with exit code 127.

You can find the actual action file here
You can also find the failing Github action here.

The standalone Dart CLI tools are being deprecated and discontinued: https://github.com/dart-lang/sdk/issues/46100. pub was deprecated in Dart 2.15 and is now discontinued in Dart 2.17, according to the table in the linked issue. Your workflow is installing Dart 2.17.0-91.0.dev (dev), so it is now affected by this breaking change.
Changing two commands in your workflow file should fix this problem:

pub get → dart pub get
https://github.com/supabase-community/gotrue-dart/blob/a41464a95a436b2de8e9b77b9bbe69a891f93f1a/.github/workflows/main.yml#L30-L31
pub run test → dart test
https://github.com/supabase-community/gotrue-dart/blob/a41464a95a436b2de8e9b77b9bbe69a891f93f1a/.github/workflows/main.yml#L50-L51

Thank you so much @JonasWanke! That fixed the issue!


[rcore] Having Caps-Lock or Num-Lock on locks all pressed keys down

[x] I tested it on latest raylib version from master branch
[x] I checked there is no similar issue already reported
[x] My code has no errors or misuse of raylib

Issue description
If you have num lock or caps lock enabled it'll "lock" whatever keys you press to be down, until you disable num/caps lock and press the key again.
It looks like this issue was introduced in a recent commit (ea87491a82a0fc778056d1538d37ec851e8e0fbe), since commenting out line 5273 of rcore.c (introduced in that commit) fixes the issue.
I'm not sure what the point of that commit is, otherwise I'd try to give a fix as well.
Code Example
if(isKeyDown(KEY_Q)
    printf("Down\n");
else
    printf("Not Down\n");

// After pressing "q" once with caps/num lock on "Down" will keep printing, even after you release it.

@masterex1000 My bad, just fixed the issue.

 Those two special keys behave different than the other keys because they work like sticky-keys, once pressed they get stuck and that state should be detected. Now raylib can detect it with this fix.
I'm aware it's a bit hacky solution and could imply other issues, let's see if someone complains about it...


model's inference

Hi, i found your work and it's very interesting , could you please explain how to do inference on a image/video with your models ? I tried by executing test.py (for YOLOV3 ) but it didn't worked for me

Hello!
Due to file size limitations on github, i cannot upload a trained network file. It should be located in the "Model_Weights" folder, and the file name should be changed accordingly. You can change it in line 77, in the test.py file. You need to first train your network, so then you can use it for inference later.

I thought you had a model zoo or a google link where the weights model's were stored. it could be a good idea.
Thank you for your response .

It is something we will consider in the future, since we already share our image database on Zenodo. You basically "just" need to train the network, using one the the base weight files available for YOLOv3.


Introduces pipeline.yml Github actions pipeline

I think we should go ahead and merge this in its broken state since this MR was about hooking up the pipeline and not fixing the errors. We can fix the errors after ;)

The publish.yml is a workflow that will get triggered when we create a new release from the Releases page. Right now, it will simply echo a message. We have to submit the first version of the app via the UI in Splunkbase. Once it gets approved, it will then have an AppID. We need the AppID in order to submit new releases via API.


Avoid crash when onPrepareVpn fails

Task/Issue URL: https://app.asana.com/0/488551667048375/1203455535355535/f
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

Current dependencies on/for this PR:

develop

PR #2600   👈

This comment was auto-generated by Graphite.


root password

Hello, can you please explain, how password will be a 5iveL!fe instead of randomly generated like in this instruction:
https://docs.gitlab.com/omnibus/installation/index.html#set-up-the-initial-password
?

Last time I tried, it was randomly generated. Though, you can manually set the password and email by setting the environment variables GITLAB_ROOT_EMAIL or GITLAB_ROOT_PASSWORD, you can set these within a playbook like this:
- name: Gitlab
  environment:
     GITLAB_ROOT_PASSWORD: "{{ gitlab_password }}"
     GITLAB_ROOT_EMAIL: "{{ gitlab_email }}"


Kubernetes ingress controller daemonset disappears

When creating an ingress controller using Trafik as a LB the pods get created, but after a couple of seconds they disappear.
The logs can be found here: http://<IP_ADDRESS>:5601/goto/2485b0e5312aa07110ce7695ea78e067

I don't see any error log from traefik. But I see:
Resources are within the expected limits.
The expected resources are {Limits:map[cpu:{i:{value:0 scale:0} d:{Dec:0xc8204698c0} s: Format:DecimalSI} memory:{i:{value:0 scale:0} d:{Dec:0xc820469d40} s: Format:BinarySI}] Requests:map[memory:{i:{value:0 scale:0} d:{Dec:0xc820469d40} s: Format:BinarySI} cpu:{i:{value:0 scale:0} d:{Dec:0xc8204698c0} s: Format:DecimalSI}]}

Here's the export:
22:47:36.000 time="2016-12-07T21:47:36Z" level=debug msg="Received event from kubernetes map[object:map[kind:Endpoints apiVersion:v1 metadata:map[creationTimestamp:2016-12-07T21:11:13Z annotations:map[control-plane.alpha.kubernetes.io/leader:{\"holderIdentity\":\"gke-486949053560-5d1898d9aa2046ca6bbb\",\"leaseDurationSeconds\":15,\"acquireTime\":\"2016-12-07T21:11:13Z\",\"renewTime\":\"2016-12-07T21:47:36Z\",\"leaderTransitions\":0}] name:kube-scheduler namespace:kube-system selfLink:/api/v1/namespaces/kube-system/endpoints/kube-scheduler uid:af215c73-bcc1-11e6-b9d7-42010af00144 resourceVersion:4512] subsets:[]] type:MODIFIED]" {  metadata: {…}     textPayload: "time="2016-12-07T21:47:36Z" level=debug msg="Received event from kubernetes map[object:map[kind:Endpoints apiVersion:v1 metadata:map[creationTimestamp:2016-12-07T21:11:13Z annotations:map[control-plane.alpha.kubernetes.io/leader:{\"holderIdentity\":\"gke-486949053560-5d1898d9aa2046ca6bbb\",\"leaseDurationSeconds\":15,\"acquireTime\":\"2016-12-07T21:11:13Z\",\"renewTime\":\"2016-12-07T21:47:36Z\",\"leaderTransitions\":0}] name:kube-scheduler namespace:kube-system selfLink:/api/v1/namespaces/kube-system/endpoints/kube-scheduler uid:af215c73-bcc1-11e6-b9d7-42010af00144 resourceVersion:4512] subsets:[]] type:MODIFIED]"  "     insertId: "tyzf05for6wzf"     log: "traefik-ingress-lb"    } 22:47:36.000 time="2016-12-07T21:47:36Z" level=debug msg="Skipping event from kubernetes map[type:MODIFIED object:map[apiVersion:v1 metadata:map[selfLink:/api/v1/namespaces/kube-system/endpoints/kube-scheduler uid:af215c73-bcc1-11e6-b9d7-42010af00144 resourceVersion:4512 creationTimestamp:2016-12-07T21:11:13Z annotations:map[control-plane.alpha.kubernetes.io/leader:{\"holderIdentity\":\"gke-486949053560-5d1898d9aa2046ca6bbb\",\"leaseDurationSeconds\":15,\"acquireTime\":\"2016-12-07T21:11:13Z\",\"renewTime\":\"2016-12-07T21:47:36Z\",\"leaderTransitions\":0}] name:kube-scheduler namespace:kube-system] subsets:[] kind:Endpoints]]" {  metadata: {…}     textPayload: "time="2016-12-07T21:47:36Z" level=debug msg="Skipping event from kubernetes map[type:MODIFIED object:map[apiVersion:v1 metadata:map[selfLink:/api/v1/namespaces/kube-system/endpoints/kube-scheduler uid:af215c73-bcc1-11e6-b9d7-42010af00144 resourceVersion:4512 creationTimestamp:2016-12-07T21:11:13Z annotations:map[control-plane.alpha.kubernetes.io/leader:{\"holderIdentity\":\"gke-486949053560-5d1898d9aa2046ca6bbb\",\"leaseDurationSeconds\":15,\"acquireTime\":\"2016-12-07T21:11:13Z\",\"renewTime\":\"2016-12-07T21:47:36Z\",\"leaderTransitions\":0}] name:kube-scheduler namespace:kube-system] subsets:[] kind:Endpoints]]"  "     insertId: "tyzf05for6wzg"     log: "traefik-ingress-lb"    } 22:47:37.000 shutting down, got signal: Terminated {  metadata: {…}     textPayload: "shutting down, got signal: Terminated "     insertId: "epmy8nfoaj3ea"     log: "POD"    } 22:47:37.000 time="2016-12-07T21:47:37Z" level=info msg="I have to go... terminated" {  metadata: {…}     textPayload: "time="2016-12-07T21:47:37Z" level=info msg="I have to go... terminated"  "     insertId: "tyzf05for6wzh"     log: "traefik-ingress-lb"    } 22:47:37.000 time="2016-12-07T21:47:37Z" level=info msg="Stopping server" {  metadata: {…}     textPayload: "time="2016-12-07T21:47:37Z" level=info msg="Stopping server"  "     insertId: "tyzf05for6wzi"     log: "traefik-ingress-lb"    } 22:47:37.000 time="2016-12-07T21:47:37Z" level=debug msg="Waiting 30 seconds before killing connections on entrypoint http..." {  metadata: {…}     textPayload: "time="2016-12-07T21:47:37Z" level=debug msg="Waiting 30 seconds before killing connections on entrypoint http..."
{
metadata: {…}
textPayload: "time="2016-12-07T21:47:37Z" level=debug msg="Waiting 30 seconds before killing connections on entrypoint http..."
"
insertId: "tyzf05for6wzj"
log: "traefik-ingress-lb"
}
22:47:37.000
time="2016-12-07T21:47:37Z" level=info msg="Server stopped"
{
metadata: {…}
textPayload: "time="2016-12-07T21:47:37Z" level=info msg="Server stopped"
"
insertId: "tyzf05for6wzk"
log: "traefik-ingress-lb"
}
22:47:37.000
time="2016-12-07T21:47:37Z" level=info msg="Shutting down"
{
metadata: {…}
textPayload: "time="2016-12-07T21:47:37Z" level=info msg="Shutting down"
"
insertId: "tyzf05for6wzl"
log: "traefik-ingress-lb"
}

I'm seeing similar behavior with Kubernetes 1.5.3 and both current versions of Traefik (v1.1.2 and v1.2.0-rc2).  The container starts and within a few seconds it starts to terminate.  Can provide log examples if needed.

Does kubectl describe <the terminated Traefik pod> provide anything helpful?

It does not because the pod records are removed when it is terminated.  I've gone through describe of the pod and daemonset while they were active, but didn't see anything noteworthy.

@lmickh do the logs of the pod give anything? (You might need the --previous flag to see the logs of the terminated pod.)

@timoreimann Here is a gist of the logs from both the pod and the kube system stuff as well.
https://gist.github.com/lmickh/423b19543cb0a6f94e8e5d62d69ce075

@lmickh Traefik clearly receives a SIGTERM here:
"time=\"2017-03-16T16:16:18Z\" level=info msg=\"I have to go... terminated\" \n"
By any chance, do you possibly have a liveness probe (mis-)configured?
Pinging @dtomcej for further ideas.

No liveness probes set.  I'll look into adding some later today to see if that matters.

Sure, give it try. It shouldn't make a difference though since the kubelet will use the container state by default, and we can see from the logs that the container is up and running.
FWIW, we're running Traefik as a DaemonSet too with no problems whatsoever. Haven't had a single restart in two weeks.
Are you possibly experiencing pod evictions due to resource contention? Have you set request and/or resource limits? Do you run Traefik in the kube-system namespace or a different one?
There's always a chance for running into k8s bugs too.

It does run in a the kube-system namespace.  There are no request/limits defined nor quotas on the namespaces.  I've set aside an empty node just to run this deamonset so I would think resources are not an issue.  Have not been able to find any logs or indications of a pod eviction.
I'm trying to make sure to eliminate any of the kube related possibilities, but I've managed to do this with the nginx ingress controller without issue.  I chimed in on this since it seemed like muemich had a similar issue.

I recently built a new cluster and was able to get a daemonset running on the v1.2.2 release.  Whatever the issue was, I can't recreate it on the new cluster.

I was suspecting some cluster-related issue too, though I can't say it was more than a gut feeling.
Glad you have a working configuration now. Shall we close this issue?


Improve performance

We measured the changes from the issue_79 branches and saw improvement: https://github.ibm.com/IBM-Swift/Performance/issues/30
However the later changes for Prepared Statements didn't achieve the same level of performance (in fact no improvement at all, @shmuelk and @irar2 were investigating).
Please can we document what additional work we're planning to do to address the Kuery <-> Raw gap?

I have opened https://github.com/IBM-Swift/Swift-Kuery/issues/156 to address the first part of these changes.
Closing this work item.


Create branch off of numeric-investigations then clean up for merge into master

Will leave behind numeric-investigations branch in case it's needed again.
Clean ups after creating new branch:

[x] Delete FoundationPointIssue folder (keep NumericTypesTests folder, it could be convenient to have it in master)
[x] In UWP code: Delete data dumping class and remove references to it and globals for it

Closed by PR #41


Initial Travis Integration

Fixes #31 based on https://www.ansible.com/blog/testing-ansible-roles-with-docker and http://www.jeffgeerling.com/blog/testing-ansible-roles-travis-ci-github

i can start to be lazy now as travis tells me that all is well :)

Was too excited that I accidentally closed the PR. Reopened and saw the build automation in real time. good stuff!. merging!


StyleRoot @Media Queries don't work properly if you are not using some kind of grid system - Chrome bug

I first started using Radium and StyleRoot when I also was using CSS Grid for a project. Now I am using Radium and StyleRoot on another project in which I am not using any grid system. Only Flexbox. As a result, my Radium styles are not changing at the breakpoints I am specifying in my @media queries. They are changing at some other seemingly random breakpoints not of my choosing. Unless this was meant to me and I have overlooked something in the docs, I think this might be a bug.
Code:
import React, {Component} from 'react';
import Radium from 'radium';
import Slider from './components/Slider';
import Footer from './components/Footer';

import photoAug15100332 from '../images/photoAug15100332.jpg';
import photoAug15111608 from '../images/photoAug15111608.jpg';
import photoAug15111623 from '../images/photoAug15111623.jpg';
import photoAug15112130 from '../images/photoAug15112130.jpg';

const sliderData = [
	{
		src: photoAug15100332,
		credits: 'The Beauty'
	},
	{
		src: photoAug15111608,
		credits: 'The Plotter'
	},
	{
		src: photoAug15111623,
		credits: 'The Gazer'
	},
	{
		src: photoAug15112130,
		credits: 'The Ponderer'
	}
];

class App extends Component {
	render() {
		const headerStyle = {
			header: {
				height: '60px',
				textAlign: 'center',
				width: '100%'
			},
			h1: {
				width: '100%',
				zIndex: '10',
				top: '35px',
				position: 'absolute',
				color: '#b22222',
				left: '50%',
				transform: 'translateX(-50%)',
				fontSize: '1.5em',
				letterSpacing: '0.03em',
			},
			minWidth680H1: {
				'@media (min-width: 680px)': {
					fontSize: '2.5em',
					top: '20px'
				}
			},
			minWidth960H1: {
				'@media (min-width: 960px)': {
					fontSize: '2.5em',
					top: '20px'
				}
			}
		}
		return (

Cat Slider

					<Slider slides={sliderData} />

		)
	}
}

export default Radium(App);

I also tried without the all and after @media first. Then I tried this way just in case. Same deal. The breakpoint I am getting right now that changes the font size  is only one and it's at 850px. And the browser I have been using is Chrome. Then I went to double check if the same thing was happening in Firefox and Safari, and it was NOT. There it was FINE and worked like it should. I will check in IE Edge on my Windows Laptop when I have access to it tonight and let you know what transpires there. DEFINITELY a browser-related BUG. Thnx!

It seems that this is the issue: https://stackoverflow.com/questions/45025397/media-query-not-working-in-react The answer in the thread is that the last media query is chosen and that it is a css thing. I personally  have never come across this I don' t think in Chrome, especially with JS (non react) applications when using Chrome DevTools, but it is  a"thing" now with React in Chrome. As I mentioned earlier, it does not happen in Safari, Firefox, or Edge (tested). So it's an FYI. I removed Radium to see what would happen, and still have problems. The answer in Stack Overflow is not QUITE right, because my font does change twice, just not in the right place. Something is up with React, Chrome, and media queries. I'm using scss. Should this become a React issue? It's kind of a pretty deal in my opinion. Not being able to create a fully responsive web site that renders properly in Chrome is not good! This has never happened to me before.

Forget everything I said previously. I just pushed this project to Github, and the media queries work as expected. This is a bug that is specific to Chrome and occurs only locally for whatever reason. I will be writing about this too. It also seems to be specific to React. Don't know why this is seems to be occurring now. Perhaps also specific to 16+? Not quite sure, but will keep my eyes open to this. my work around will be to either use Firefox or Safari to render my React applications (and keep on checking with Chrome too for the hell of it) as that is how I will be able to gauge the responsiveness of my apps.

did you ever figure out the problem for local chrome? I ran into the same issue today and it was driving me crazy but after reading your post I tried with firefox and the media queries worked as expected.

I experienced the same issue with React + Next.js on Chrome. Bootstrap media queries work properly on Firefox and Safari but Chrome makes the app irresponsive. I want to know whether this issue persists in prodcution as well?

I experienced the same issue with React + Next.js on Chrome. Bootstrap media queries work properly on Firefox and Safari but Chrome makes the app irresponsive. I want to know whether this issue persists in prodcution as well?

This you find any solution?

This you find any solution?

I personally quit using Radium and went with a different approach because of this issue.

For Chrome specifically, try adding this to your page's  section :
<meta name="viewport" content="width=device-width,initial-scale=1">

Besides the App component, you also have to wrap your App with the StyleRoot tag located in the index.js file.
Like this:


Question: Firmwareflash

Only a short question...
When I install a newer Firmware on my Coordinator CC26X2R1, will i be able to use my sensors further or must I pair all sensors new?

see https://www.zigbee2mqtt.io/guide/faq/#what-does-and-does-not-require-repairing-of-all-devices , note that the issues section is not meant for questions, use support channels and read the docs first next time.


إدج

Originally posted by @aliokfi in https://github.com/MicrosoftDocs/windows-itpro-docs/issues/10191


Buildpack can't fetch jemalloc-3.6.0-1.tar.gz

I have:
$  heroku buildpacks
1. https://github.com/heroku/heroku-buildpack-apt
2. https://github.com/mojodna/heroku-buildpack-jemalloc.git#v3.6.0
3. heroku/ruby

When I deploy, the build phase crashes:
[...]
remote: -----> jemalloc app detected
remote: -----> Vendoring binaries
remote:        Fetching https://s3.amazonaws.com/mojodna-heroku/heroku-16/jemalloc-3.6.0-1.tar.gz
remote:
remote: gzip: stdin: not in gzip format
remote: tar: Child returned status 1
remote: tar: Error is not recoverable: exiting now
remote:  !     Push rejected, failed to compile jemalloc app.
remote:
remote:  !     Push failed
[...]

This file doesn't exist: https://s3.amazonaws.com/mojodna-heroku/heroku-16/jemalloc-3.6.0-1.tar.gz
Everything is fine if I don't pin to v3.6.0.
Is there a reason 3.6.0 is still shown as a fallback option? Is it still supported?

We need to create a heroku-16 build, we haven't done that yet.

I have the same exact problem. I read that jemalloc 3.6 works better with Ruby, I'm using Ruby 2.3.1.

I encountered this issue today. Are there any plans for building 3.6 for heroku 16?
Or should I just be using the latest version instead? I have heard of instabilities with 4.0, and unknown performance with 5.0

See #18.


Add test case to clarify method overloading in java interop functions

Purpose

$title

Fixes #20918
Approach

N/A

Samples

N/A

Remarks

It seems that the issue is not existent in the master. Therefore, relevant test cases are added.

Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[x] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Can we address the changes we requested during the sprint meeting on this PR?

the changes are addressed in the latest commit.

 Please fix it.

 Please fix it.
Updated the commit message

This added test does not cover the scenario mentioned in the #20918.
One of the overloaded type should be a child of the other. Like the example given in the mentioned issue, one is an Object and the other is a  String, which is a child of the Object.


Updating lock file

Codecov Report

Merging #32 (24dcab5) into main (db23864) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #32   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines           22        22
=========================================
  Hits            22        22

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update db23864...24dcab5. Read the comment docs.


[rfc] - fast drawrule merging

There was a lot of copying of StyleParams in the SceneLayer matching. This patch splits the duplicate use of DrawRule into a static container class and a new DrawRule optimized for storing the match results.

DrawRule became StaticDrawRule as a container for the actual scene data.
(a better would be welcome :)

DrawRule is now a reusable result container with direct access to keys
for fast merging and retrieval. For non-dynamic parameters it only holds
the pointer the static DrawRule, so no copying there.

[ ] Update tests

@hjanetzek can you rebase this!. We should also get some eyes on this. This has some good perf improvements.

Closing in favor of https://github.com/tangrams/tangram-es/pull/372


[TASK] SPDK raid merge with upstream

What's the task? Please describe
We need to recreate the development made to grow the number of base bdevs of a raid1. To have raid1 support, last year we started from a version of spdk still under review in Gerrit: after having imported this version in our repo, some great changes have been made on the version under review. So we need to adapt our development to this new code base.
Describe the sub-tasks

[ ] Replace raid suspend/resume with bdev quiesce/unquiesce
[ ] Make sure the rebuild does not start when growing a raid
[ ] Add raid grow e2e test

Additional context

cc @derekbit @shuo-wu


Diesel initial setup migration comments are unclear or not up-to-date

Setup
Versions

Rust: rustc 1.42.0 (b8cedc004 2020-03-09)
Diesel: 1.4.3
Database: Postgresql
Operating System Ubuntu

Feature Flags

diesel: postgres

Problem Description
The migration file<PHONE_NUMBER>0000_diesel_initial_setup/up.sql contains a comment explaining that future changes tothis file will be added to existing projects as new migrations :
-- This file was automatically created by Diesel to setup helper functions
-- and other internal bookkeeping. This file is safe to edit, any future
-- changes will be added to existing projects as new migrations.

Performing diesel migration redo or diesel database reset will correctly take the changes into account. However the changes are not "added to existing projects as new migrations".
Did I misunderstand? Or has the feature been removed?
Checklist

[x] I have already looked over the issue tracker for similar issues.
[x] This issue can be reproduced on Rust's stable channel. (Your issue will be
closed if this is not the case)

The sentence "added to existing projects as new migrations" refers to changes to the initial setup migration that diesel will create on it's own for internal reasons. So if we decide to add a new sql helper function or something like that, we will do that as new migration, not by modifying the existing<PHONE_NUMBER>0000_diesel_initial_setup one.

Ok thank you !


Mobile UI Prototype to validate behavior

Overview
Create  prototypes for v3 and v4 progress indicators for mobile.
See Issue #887 for reference.

Check out these resources for MUI stepper process, especially for how we would address the experience for mobile:

https://material.io/archive/guidelines/components/steppers.html
https://mui.com/components/steppers/
https://material.angular.io/components/stepper/overview


twice dispatch an async action creator with different params

i'm pretty sure that is my mistake, but...
for example:
I have 2 dummy Root, TopicPage, and one dumb Header which render received data as navigation.
@connect(state => ({ topics: state.topics }))

export default class Root extends Component {

	static propTypes = {
		dispatch: PropTypes.func.isRequired,
		topics: PropTypes.object.isRequired
	}

	componentDidMount() {
		this.props.dispatch(fetchTopics('defaults'));
	}

	render() {
		return (

			// for example TopicPage
			{ this.props.children }
		);
	}
}

@connect(state => ({ images: state.topics }))

export default class TopicPage extends Component {

	static propTypes = {
		dispatch: PropTypes.func.isRequired,
		images: PropTypes.object.isRequired
	}

	componentDidMount() {
		this.props.dispatch(fetchTopics(this.props.params.id));
	}

	render() {
		return (

{ this.props.images.data.map(item =>

{ item.id }
) }

		);
	}

But data in Root and TopicPage the same and receive it as random...
https://www.youtube.com/watch?v=_hSRKY-5efo&feature=youtu.be
Sorry for my English and low skill, and for leave the question here, I couldn't ask it on stack overflow..

Your selector is the same so the data is the same. I don't understand your
question I think.
Why could you not ask on stackoverflow?
On Thu, Sep 24, 2015, 02:08 Alexey Bogoslovskiy<EMAIL_ADDRESS>wrote:

i'm pretty sure that is my mistake, but...
for example:
I have 2 dummy Root, TopicPage, and one dumb Header which render received
data as navigation.
@connect(state => ({ topics: state.topics }))
export default class Root extends Component {
static propTypes = {
    dispatch: PropTypes.func.isRequired,
    topics: PropTypes.object.isRequired
}

componentDidMount() {
    this.props.dispatch(fetchTopics('defaults'));
}

render() {
    return (

        // for example TopicPage
        { this.props.children }
    );
}

}
@connect(state => ({ images: state.topics }))
export default class TopicPage extends Component {
static propTypes = {
    dispatch: PropTypes.func.isRequired,
    images: PropTypes.object.isRequired
}

componentDidMount() {
    this.props.dispatch(fetchTopics(this.props.params.id));
}

render() {
    return (

{ this.props.images.data.map(item =>
{ item.id }
) }

    );
}

But data in Root and TopicPage the same and receive it as random...
https://www.youtube.com/watch?v=_hSRKY-5efo&feature=youtu.be
Sorry for my English and low skill, and for leave the question here, I
couldn't ask it on stack overflow..
—
Reply to this email directly or view it on GitHub
https://github.com/rackt/redux/issues/790.

--
Wout.
(typed on mobile, excuse terseness)

Please provide the whole project source code, a list of steps to reproduce the issue, the expected, and the actual result.

@wmertens Because, I should to wait for a 2 days to ask a question...
project source code: https://github.com/dontlemmedown/isomorphic

a list of steps to reproduce the issue

if I got you correctly, then

npm run dev
```open localhost:3000`
click to a link in a header
refresh the page a few times (to see result)

I want to receive different data in headers (navigation) and TopicPage from fetchTopics action creator. But now, when I dispatch the action fetchTopics('defaults') in Root component and send the data to Header its ok, but when I dispatch it again  fetchTopics(params.id) in TopicPage component (a child of Root) then result is randomly receiving data in Header and TopicPage...
Hope you got my meaning and English as well =)

The problem is with your reducer. You're using splats to merge, but they
only do a shallow merge.
https://github.com/dontlemmedown/isomorphic/blob/master/src/reducers/topics.js#L17
I think you want
return { ...state, isFetching: false, data: {state.data, ...action.response.
data }};
(not tested)
On Fri, Sep 25, 2015 at 12:53 AM Alexey Bogoslovskiy <
<EMAIL_ADDRESS>wrote:

@wmertens https://github.com/wmertens Because, I should to wait for a 2
days to ask a question...
project source code: https://github.com/dontlemmedown/isomorphic
a list of steps to reproduce the issue
if I got you correctly, then

npm run dev
``open localhost:3000
click to a link in a header
refresh the page a few times (to see result)

I want to receive different data in headers (navigation) and TopicPage
from fetchTopics action creator. But now, when I dispatch the action
fetchTopics('defaults') in Root component and send the data to Header its
ok, but when I dispatch it again fetchTopics(params.id) in TopicPage
component (a child of Root) then result is randomly receiving data in
Header and TopicPage...
Hope you got my meaning and English as well =)
—
Reply to this email directly or view it on GitHub
https://github.com/rackt/redux/issues/790#issuecomment-143070437.

--
Wout.
(typed on mobile, excuse terseness)

BTW, with redux-devtools you would have seen this :)
On Sun, Sep 27, 2015 at 10:06 AM Wout Mertens<EMAIL_ADDRESS>wrote:

The problem is with your reducer. You're using splats to merge, but they
only do a shallow merge.
https://github.com/dontlemmedown/isomorphic/blob/master/src/reducers/topics.js#L17
I think you want
return { ...state, isFetching: false, data: {state.data,
...action.response.data }};
(not tested)
On Fri, Sep 25, 2015 at 12:53 AM Alexey Bogoslovskiy <
<EMAIL_ADDRESS>wrote:

@wmertens https://github.com/wmertens Because, I should to wait for a
2 days to ask a question...
project source code: https://github.com/dontlemmedown/isomorphic
a list of steps to reproduce the issue
if I got you correctly, then

npm run dev
``open localhost:3000
click to a link in a header
refresh the page a few times (to see result)

I want to receive different data in headers (navigation) and TopicPage
from fetchTopics action creator. But now, when I dispatch the action
fetchTopics('defaults') in Root component and send the data to Header
its ok, but when I dispatch it again fetchTopics(params.id) in TopicPage
component (a child of Root) then result is randomly receiving data in
Header and TopicPage...
Hope you got my meaning and English as well =)
—
Reply to this email directly or view it on GitHub
https://github.com/rackt/redux/issues/790#issuecomment-143070437.

--
Wout.
(typed on mobile, excuse terseness)

--
Wout.
(typed on mobile, excuse terseness)

@wmertens, it didnt works, cuz there's an error   data: {state.data, ...action.response. data } and most importantly for me - i dont get how to should it work :(
But.. redux-devtools, I'll try to use this to get solution =)
thanks.

Oops that should have been
return { ...state, isFetching: false, data: {...state.data,
...action.response.data }};
On Mon, Sep 28, 2015, 00:15 Alexey Bogoslovskiy<EMAIL_ADDRESS>wrote:

@wmertens https://github.com/wmertens, it didnt works, cuz there's an
error data: {state.data, ...action.response. data } and most importantly
for me - i dont get how to should it work :(
But.. redux-devtools, I'll try to use this to get solution =)
thanks.
—
Reply to this email directly or view it on GitHub
https://github.com/rackt/redux/issues/790#issuecomment-143598341.

--
Wout.
(typed on mobile, excuse terseness)

@wmertens, thanks for trying to help me and I apologize for molestation, but could you explain me - how should it work, because I've got the same problem
https://github.com/dontlemmedown/isomorphic/commit/9bbe5a9bad54b5602cb7eec83cbf33f6b2ac2bb8

I'll close this, as we're starting to adopt the policy of not allowing questions in issues (#838).
Please feel free to ask this on StackOverflow or other QA resources.


Azure CLI: Typo in az keyvault secret set.

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az keyvault secret set
Errors:
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az keyvault secret set -n {} --value {} --vault-name {}

Expected Behavior
"kind" is spelled correctly in json output instead of "kid".

Environment Summary
Windows-10-10.0.18362-SP0
Python 3.6.6
Installer: MSI

azure-cli 2.9.1

Additional Context

@bim-msft please take a look

@plooploops Thanks for reaching out. Actually it's not a type: here kid represents If this is a secret backing a KV certificate, then this field specifies the corresponding key backing the KV certificate..
https://docs.microsoft.com/en-us/rest/api/keyvault/setsecret/setsecret#secretbundle

For normal (non-certificate related) secrets, this field is useless.

@bim-msft Thank you for the clarification and the link to the docs.  Looks like it's expected behavior then!

Anyway, thank you for your feedback! :-)


WIP - fix guestbook test flake

Signed-off by: Ian Vernon<EMAIL_ADDRESS>

Aborted the build, as @aanm says he has found the issue, and I didn't want to take up a slot for the build slaves. Closing this.


Add some help text to explain diff between load and % active nodes

we might want to explain the difference between load and % nodes active. You could have 70% load and 100% nodes active because jobs may not be using 100% of the resources they requested
italicized text below or above something? tooltip or popover?

Not doing


[Task] Implement key deletion in the Account

Description
The Storage::key_del function can be used to delete the key belonging to a verification method, but it is currently not used from the Account. The task is to decide when to delete the key material of a verification method, and implement it.
Motivation
The key material of deleted verification methods does not need to be retained, and so it should be deleted to keep the storage clean.
When to delete keys?
In theory, keys can be deleted as soon as the verification method has been deleted. One caveat comes for methods that are used to sign updates. Rotating DID document signing keys means deleting an old method from the document, but the old method is still required to sign the update that removes itself. Thus, deleting keys immediately when processing Update::DeleteMethod is not possible in general.
In theory, publishing waits for milestone confirmation, so it is safe to delete keys afterwards.
One approach (I believe suggested by @cycraig) was to compare (diff?) the old and new document during publishing, and if publishing is successful, attempt to delete all keys that were removed. "Attempt", because in a distributed setup, not all verification methods may actually have local key material. Considering distributed setups, keys also need to be removed during Account::fetch_document, because methods may have been removed from a different machine. A nice feature of this approach is that it should not require additional state to be kept.
This approach may or may not have to be discussed some more.
To-do list
Create a task-specific to-do list. Please link PRs that match the To-do list item behind the item after it has been submitted.

[ ] Implement key deletion in the account.

Change checklist
Add an x to the boxes that are relevant to your changes, and delete any items that are not.

[ ] The feature or fix is implemented in Rust and across all bindings whereas possible.
[ ] The feature or fix has sufficient testing coverage
[ ] All tests and examples build and run locally as expected
[ ] Every piece of code has been document according to the documentation guidelines.
[ ] If conceptual documentation (mdbook) and examples highlighting the feature exist, they are properly updated.
[ ] If the feature is not currently documented, a documentation task Issue has been opened to address this.

compare (diff?) the old and new document during publishing, and if publishing is successful, attempt to delete all keys that were removed.

Indeed that's one of the approaches we could use. I think I raised that we should only attempt that after resolving to ensure the latest state does not contain the keys (only resolving really confirms that a published update was successful), and resolving might be something we want to do for that reason anyway.
However I believe we should never automatically delete or remove private keys from storage. Users may be temporarily removing a verification method in order to re-add it with different verification method relationships---this is actually a use-case we do not support since the Account rejects adding verification method relationships to embedded methods, so we say to remove and re-add the method but that is impossible since the private key is not extractable/movable in storage by end-developers using the Account alone. The second reason is that those private keys may be important and removing a verification method could be a mistake.
I think we should have a method similar to purge---purge_keys perhaps---that has to be manually called by a developer, and that deletes any keys in storage that are not linked to any verification methods in the current or previous state of the DID Document.

We discussed this more in yesterday's weekly.
Key Deletion
Publishing currently can wait for milestone confirmation or not, depending on user-supplied options, but only when using the Client directly. The Account uses the default, which is to wait for milestone confirmation.  In my opinion, the Account should always wait for milestone confirmation. It's fine to give this control to lower-level uses, but the Account manages keys and so it needs to work with all the guarantees it can get. Since all the operations are async, users can easily poll it in the background if it takes too long.
There are at least two approaches for key deletion:

After a milestone-confirmed update (e.g. one that rotates signing keys) we could delete the key of the removed verification method automatically, since a milestone is a proper confirmation that the message was included. Unless the used node lies, this should be a pretty safe solution.

After a milestone-confirmed publication, we mark the key for deletion in some auxiliary data structure. Users can manually call Account::purge_unused_keys (or similar) to delete those marked keys for good. The Account can maintain that data structure without requiring every Storage implementation to take care of it. This is an even safer alternative than 1., that never automatically deletes keys and puts the responsibility (or burden) on the user. Depending on the value of the identity, users may choose to check with multiple nodes (quorum) to decide whether an update was published correctly and to increase confidence in that outcome. Note that the marked keys can continue to be used, because Storage is unaware of these markers. If a message was not published correctly, for whatever reason, users can attempt another publication because the key is still in storage (as long as they did not call purge_unused_keys).
This solution should enable @cycraig's point about re-adding verification methods. Removing a method marks the key for deletion, but adding a method with an existing key location (not currently part of the API, but could be) could unmark the key for deletion.

Account DID Deactivation
Since we discussed this in the context of DID document deactivation, I'll try to propose a solution for this as well.
Add an Account::deactivate_identity method, that publishes a deactivated DID document. This does not delete any local keys or state. Once a user is sure that they want the Account to be gone for good, they can call Account::delete_identity to purge every key and state associated to the identity. In delete_identity we may want to check if a deactivation update was published and throw an error otherwise. Even if a deactivation update fails, another one can be attempted because the key is still in storage. If built in concert with solution 2 from above, deactivate_identity should not mark any keys for deletion because as long as the Account can be loaded from Storage, we cannot consider it deactivated. The last key(s) capable to sign a document update will be removed with delete_identity instead.
Let me know if I missed something from yesterday's discussion. Personally, I would prefer solution 2 for key deletion.


Bump fauxton to v1.2.3

Overview
Use Fauxton v1.2.3.
Testing recommendations

Related Issues or Pull Requests

Checklist

[ ] Code is written and works correctly
[ ] Changes are covered by tests
[ ] Any new configurable parameters are documented in rel/overlay/etc/default.ini
[ ] A PR for documentation changes has been made in https://github.com/apache/couchdb-documentation

@willholley Will you be able to assist with https://github.com/apache/couchdb-documentation/issues/493 as well?

I updated the Fauxton v1.2.3 tag, so you're good to go.
Also added Fauxton changes to the 3.0.0 release notes in https://github.com/apache/couchdb-documentation/pull/494

@willholley I'm going to merge this here and 3.0.x and 3.x, but do we need a Fauxton 1.2.4 before we release 3.0.1 and 3.1.0?

there are a few small fixes to Fauxton since 1.2.3; @Antonio-Maranhao what do you think?

I would us to fix https://github.com/apache/couchdb-fauxton/issues/1037#issuecomment-609685270 before we cut another release


Set up a Cognito SAML connection

Just a test one to any SAML IDP to prove we can do it.

Made a sample connection here,
which is an app client with SAML connection to okta. Step-by-step walkthrough to setup here
When connecting, two things to note about using the returned code to post to cognito:

When posting to cognito to get a token, parameters need to be in the body as x-www-url-formencoded
If the app client has a secret, add to params as client_secret


Remove ccache dependency for macOS

ccache does not appear to be a dependency required to compile anymore - https://github.com/bitcoin/bitcoin/blob/master/doc/dependencies.md

Can also be removed for Linux, forgot to make that change sorry.

Hi @Bosch-0! Thanks for the proposal. Yes, ccache is not strictly a dependency for any OS, but it speeds up repeated compiling to the point that it's essential for testing PRs, so I prefer to leave it in and add an explanation about why it's in the list.

Okay thanks for clarifying that! Closing PR


SSL Protocol

We should work towards this as soon as testing is complete

We don't have to do this in Node. Instead we can put NGINX or Apache in front of the backend as a reverse proxy and have one of them deal with TLS, they'll just talk to the backend via regular HTTP.

Will be handled by NGINX.


refactor: replace deprecated String.prototype.substr()

String.prototype.substr() is deprecated so we replace it with String.prototype.slice() which works similarily but isn't deprecated.
.substr() probably isn't going away anytime soon but the change is trivial so it doesn't hurt to do it.

Thanks for your contribution!
If you haven't already done so, could you please make sure you sign our CLA (https://jitsi.org/icla for individuals and https://jitsi.org/ccla for corporations)? We would, unfortunately, be unable to merge your patch unless we have that piece :(.

I have now signed the CLA as requested


Separate writing from reading/processing resources

For historical reasons and when we were dealing with memory issues of DirectRunner, we merged the writing phase of the batch pipeline with resource fetching/processing. We should revisit this with FlinkRunner and if there are no memory issues, then separate the writing stages. That way it would be easier to use standard Beam IO classes like ParquetIO, JdbcIO, etc.

Just checking - I see this is currently assigned.  Does this mean there is active work on this?  If so, should this be tagged for Beta or Mid-march?

This is not required for Beta (nice to have). @chandrashekar-s please feel free to unassign this if you are not actively working on it (the original assignment was because of a related bug which is fixed now).


Atom crash after narrow:search

When I search some word by narrow:search and I move cursor to bottom in narrow-editor, Atom always freeze up like following gif(only vim-mode-plus & atom-narrow is activated).

I can't see console so this might not be caused by narrow.
Have you ever seen like this crash and do you know why this caused?
Thanks!
Atom: 1.19.0
vim-mode-plus: 0.96.2
atom-narrow: 0.50.3

I can't reproduce and haven't experienced that.
What your OS?
What is your narrow config?
Do you tune key-repeat rate via Karabiner or similar software?
In your GIF, why auto-preview is not happen while you are moving down, because of too fast or you explicitly disable it?

I use macOS 10.12.6.
My narrow config is following.
  narrow:
    Search:
      autoPreview: false
      autoPreviewOnQueryChange: false
      revealOnStartCondition: "always"
    directionToOpen: "down:always-new-pane"
    queryCurrentWordByDoubleClick: false

I turn off auto-preview only for narrow:search.
I tune key-repeat rate via System Preferences, not using like Karabiner.

how is the rate? I want to reproduce to fix it.

My key repeat settings.

I tried with your config and same keyrepeat setting, but couldn't reproduce.
I use narrow with vim-mode-plus enabled but have no freeze issue.
Can you find minimum set of package combination to reproduce.

And what is your keystroke to move down, j ? ctrl-n?
Does that happen in small code base?
Ideally I want full set of codebase/keystroke on each step to reproduce issue.

I can produce this issue only enabling narrow.
I used j to move down in the gif above.
In following gif, I produce this issue.

Codebase is here. https://github.com/kdnk/dotfiles
And my atom setting is here https://github.com/kdnk/dotfiles/tree/master/atom
I hope it might help you.
In the gif, I use Atom 1.19.1 only activate narrow and the other packages is disabled.
Following is the step I produce this.

Open my dotfile directory in Atom by atom . command.
Open command pallte by cmd+shift+p and put enter to confirm narrow:search
Put statement vim-mode-plus  to narrow-editor and scroll to the bottom by down key.
Then curor move to the bottom, always atom is crushed.

Let me clarify, you can reproduce 1. "with atom +narrow  only" or 2. "atom +narrow +vim-mode-plus"?
Which is your situation 1 or 2?

After i read again i understand vmp is not necessary to repro.
Will try to reproduce later.

I couldn't repro with your dot file and codebase, so what I can do next is to use your atom config.
But I also want you to narrow down condition further.
Since might not common issue where every user hit.
You can reproduce issue with older narrow?
You find any common condition when editor stops like "always stops when cursor reached to line which is one line before last line" or something.
Anyway my motivation to reproduce issue is getting decrease, I want to try it again after concrete reproduce steps was settled.

OK, I can repro using your config :tada:
Investigate it from now.

Still not clear if it's Atom-core issue or narrow issue, I thinks I found config to avoid freezing.
Can you check issue resolved by checking "Scroll Past End" editor config.
By enabling this I no longer see issue. That's why I couldn't reproduce.

I checked "Scroll Past End", narrow works!!!🤣
Thanks so much!!!!!

Can you remember this was not happened in Atom v1.18.0 then after updating to Atom v1.19.0, issue started?
If so, this might be Atom-core's bug, v1.19.0 includes tons of rewritten for editor-rendering logic.
Why I say this is I could reproduce issue with older version of narrow v0.49.0.

This issue happened after I updated to Atom v1.19.0.
But for these two months, I used v1.19.0-beta, I also remember this issue was not happened.

Thanks.


Add Services Processor

I heard you like annotation processors, so I made an annotation processor for the annotation processor for annotation processors.

Uses Services Processor to generate META-INF/services/javax.annotation.processing.Processor files for prism core
Now avaje-prisms itself will automatically generate META-INF/services/javax.annotation.processing.Processor entries for detected annotation processors.

Services entries will be added if a concrete processor class has any of the following annotations:

Any avaje prisms annotation
@SupportedAnnotationTypes
@SupportedOptions
@SupportedSourceVersion

requires the spi lib to be deployed.

Hmm, maybe there's another way to go about this.

Yeah, I'm good with this

Alright then, I'll merge as soon as services gets deployed