Unable to publish to external stores.

Description:
Followed the following doc to publish to an external store.
https://apim.docs.wso2.com/en/latest/learn/design-api/publish-api/publish-to-multiple-external-api-stores/#publish-to-multiple-external-developer-portals
Steps to reproduce:
Get two instances of APIM ( instance1, instance2 )
Make instance 2 port offset to 1.
Change instance 1  /_system/governance/apimgt/externalstores/external-api-stores.xml to the following.
<ExternalAPIStores>
    <StoreURL>http://localhost:9443/devportal</StoreURL>
        <ExternalAPIStore id="DeveloperPortal2" type="wso2" className="org.wso2.carbon.apimgt.impl.publishers.WSO2APIPublisher">
            <DisplayName>DeveloperPortal2</DisplayName>
            <Endpoint>http://localhost:9444/devportal</Endpoint>
            <Username>admin</Username>
            <Password>admin</Password>
        </ExternalAPIStore>
</ExternalAPIStores>

Go to instance 1 publisher portal and try to publish to the DeveloperPOrtal2.

http://localhost:9444/devportal needs to be pointed to https

Did the change in the registry config.
The configuration change is visible in the publisher.

Following error printed in the terminal.
[2021-03-23 17:07:04,441] ERROR - WSO2APIPublisher Import API service call received unsuccessful response:  status: 404
[2021-03-23 17:07:04,442] ERROR - APIProviderImpl org.wso2.carbon.apimgt.api.APIManagementException: Import API service call received unsuccessful response:  status: 404
[2021-03-23 17:07:04,443] ERROR - GlobalThrowableMapper org.wso2.carbon.apimgt.api.APIManagementException: Failed to publish API to external Store.


Is there a unix socket support available ?

I can't use the DOCKER_HOST and DOCKER_CERT_PATH environment variables cause i'am using ubuntu machine.

@SaltyJahmale it does not have unix support now. I can add it for you. Are you planning to use the library for some project?

Yes for a school project i'm working right now. If you can add it that
would be great.
On Tuesday, May 24, 2016, Shekhar Gulati<EMAIL_ADDRESS>wrote:

@SaltyJahmale https://github.com/SaltyJahmale it does not have unix
support now. I can add it for you. Are you planning to use the library for
some project?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/shekhargulati/rx-docker-client/issues/72#issuecomment-221169450

@shekhargulati are there any specific constraints? You might find an inspiration at https://github.com/docker-java/docker-java or a more low level approach at https://github.com/gesellix/docker-client.
Disclaimer: I'm the docker-client developer, and currently looking into the OkHttp library to handle Unix sockets.

@shekhargulati ah, I just saw your comment at https://github.com/square/okhttp/issues/2576
Looking at the rx-docker-client dependencies, there's a rx-okhttp lib, but I didn't find a repo, yet. Do you maintain it as closed source?

@gesellix this is the library https://github.com/shekhargulati/rx-okhttp. I maintain this as well.

@shekhargulati ah, looks like I was blind ;-)
I'm going to look into it tomorrow, if you like. Looks like we both go into the same direction.

@gesellix 👍 please give it a shot.  Looking forward to your PR :)

@shekhargulati you can see a proof of concept over there: https://github.com/gesellix/okhttp/blob/master/samples/simple-client/src/main/java/okhttp3/sample/OkDocker.java
It depends on the https://github.com/kohlschutter/junixsocket library, although you mentioned https://github.com/jnr/jnr-unixsocket. Do you have any preference for one of those libs?

@gesellix thanks for the POC. I have no preference to jnr-unixsocket. I will base my implementation on your work. Thanks for the help.

@shekhargulati I now made unix socket connections work with this class: https://github.com/gesellix/docker-client/blob/d8f4ad4f81acb70ccfc701d868c3a22514bcaaff/src/main/groovy/de/gesellix/docker/client/UnixSocketFactory.groovy
The integration looks like this: https://github.com/gesellix/docker-client/blob/d8f4ad4f81acb70ccfc701d868c3a22514bcaaff/src/main/groovy/de/gesellix/docker/client/OkHttpClient.groovy#L129
Please have a quick look at the overall idea, I'm going to integrate it into your rx-okhttp lib as the next step. We can then discuss details in the PR.

ah, you already added an implementation in https://github.com/shekhargulati/rx-okhttp/commit/54645d478b6de7f3f7a169c37f7f6596e1f8cc79
nice :-)


Removed string from definition of KNet generic types

Description

Removed the use of <string, string> definition into KNet types moving to the .NET typed classes.
Related Issue

Closed #59
Motivation and Context

How Has This Been Tested?

Tested with available tests
Screenshots (if appropriate):
Types of changes

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

Checklist:

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

Testing the modifications introduced from this PR many times the test raises a java.lang.NullPointerException at https://github.com/masesgroup/KEFCore/blob/160895975f49637cf5c25b31e08d89cca50d54db/src/net/KEFCore/Storage/Internal/EntityTypeProducer.cs#L254
The exception is raised after an uncertain number of iterations over the input of https://github.com/masesgroup/KEFCore/blob/160895975f49637cf5c25b31e08d89cca50d54db/src/net/KEFCore/Storage/Internal/EntityTypeProducer.cs#L237
The remote callstack reports:
org.apache.kafka.clients.producer.KafkaProducer.doSend(KafkaProducer.java:996)
org.apache.kafka.clients.producer.KafkaProducer.send(KafkaProducer.java:962)
org.apache.kafka.clients.producer.KafkaProducer.send(KafkaProducer.java:847)

Testing the modification introduced from this PR seems the speed of LINQ query is very poor; the following code
context.Posts.Single(b => b.BlogId == 2)

takes more or less 16 seconds to be executed as reported from the following output:
Elapsed context.Posts.Single(b => b.BlogId == 2) 16299 ms. Result is PostId: 2 Title: title Content: 2 BlogId: 2


Property sonar.login is deprecated

Use sonar.token instead.

Fixed in https://github.com/JavierSegoviaCordoba/hubdle/commit/b11a256393ef4800b248c55f2c9e8000109957ff


Add support for basic UDP networking

This PR adds support for a few basic UDP operations. More will be added later, but I'd like to get some discussion going about the implementation details used here before more work is done.

I'm going to close this once LinkTed's PR is in.

Obseleted by #40


『Site』view count

is it any way to get page View for root (path: "/"  ) or any way to get whole『Site』view count?

@jamesdouble Sorry , It is not supported by the current version.


Update pipenv commands and add requirements tox run

Fixes #72
The changes in this pr are as follows:

update the pipenv command in Makefile
add a tox ci test where we check if there is a new dependency or version of a dependency that should be added to any of the requirements files.

PS: These changes in this pr were first discussed here: https://github.com/vmware/repository-service-tuf-api/pull/124

Codecov Report
Base: 83.70% // Head: 83.70% // No change to project coverage :thumbsup:

Coverage data is based on head (09f404c) compared to base (577ced4).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #85   +/-   ##
=======================================
  Coverage   83.70%   83.70%
=======================================
  Files           9        9
  Lines         540      540
=======================================
  Hits          452      452
  Misses         88       88

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Labels, Names, and Tests

Fix Default Label from Plugin
Fix Object Reference Bug
Update Name for inputs
Require kebab case for IDs
Clean up error messages

Increased code coverage?


Discovery concurrent running bug

When one discovery process is in the state of IN_PROGRESS, other discoveries are not running and also in the state of IN_PROCESS waiting for the previous discovery to finish.
This is blocking behaviour and the expected is that the discoveries can run in parallel. One discovery should not block the other. In current situation, when there is an issue with the discovery provider, we are waiting until the process is finished, which can take up to 6 hours according to the current implementation in the source code:
private static final Long MAXIMUM_WAIT_TIME = (long) (6 * 60 * 60); // Hours * Minutes * Seconds *

Issue not possible to reproduce. Seems it is already when resolving other issues.


BuildSystem: use llvm-ar rather than ar

Unlike UNIX systems, Windows does not have an archiver.  Traditionally,
this role has been fulfilled by link.  Since we already need clang
and LLVM, let us just switch to llvm-ar which can support BSD style
archives (Darwin), GNU style archives (Linux), and SysV archives
(Windows).

@swift-ci please test

@swift-ci please test

@swift-ci please test

I had a conversation with Daniel on slack about actually changing the invocation to call libtool in some cases. Specifically we found an issue where if you had a .o file with no symbols and create an archive from it with ar, it will fail to link into the final binary since it's missing the table of contents. If you link the same thing with libtool this isn't a problem. I'm not sure how that fits in with this change.

@keith this wouldn't really be related to that.  If you are building a single library, I suppose that you could use it to use lipo rather than ar.

@swift-ci please test

FEIW this currently goes through this same codepath. But we could possible figure that out separately, I'm not sure how that would affect the public API

@ddunbar @dmbryson - ping?

@swift-ci please smoke test

@swift-ci please smoke test os x


Data Log History

It seems like the changes to the dns_rr table are not logged in the Data Log History of ISPConfig. I think this would be a very welcome addition, so you can see when the last changes were done easily.

Just checked and the data log history entries are created on my server for both dns_rr and dns_soa updates.
Are you sure the DNS entry was actually updated and the IP was not already correct?

The only issue I see is it is logged for the admin user, not the user the token is assigned to.
Will check if I can fix that.

With the latest release v1.3.0, the correct user should be logged.

You are correct, thanks. Great and quick work!


9518 NR legal type refactor + misc cleanup

Issue #: /bcgov/entity#9518
Description of changes:

used nr.legalType instead of converting
fixed whitespace in Entity Info component
deleted obsolete Entity Filter mixin
replaced entityFilter() with isXXX getters
added entity subtype enum for SP
removed unneeded nameRequestType
removed "applicant" from certify stmt
updated unit tests
app version = 3.4.1

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the bcrs-entities-create-ui license (Apache 2.0).

Local test results (to see entity info header and NR data):


Feature: flutter_secure_storage

Use case
No access to the data in the secure key value storage.
Message: The specified item already exists in the keychain, IOS
Proposal
flutter_secure_storage is an essential security feature of flutter. In the current version, serious errors can occur which lead to high user losses.
My question would be whether this package should be included in flutter so that more people can keep an eye on the code.

Use case
No access to the data in the secure key value storage.
Message: The specified item already exists in the keychain, IOS

This appears to be a description of a bug in third-party package; a use case would be a high-level description of something that you are trying to accomplish in an application. In the future please provide an actual use case when filing a proposal.

My question would be whether this package should be included in flutter so that more people can keep an eye on the code.

You've linked to a package that is open source; anyone can read all the code already, and based on the discussion there it appears that at number of people are doing so, as well as providing PRs. If the Flutter team were to fork that plugin, thus splitting the user base, the result would be fewer people looking at, and contributing to, each individual fork.
Closing, as we have no plans to add a first-party plugin that covers the same use case as flutter_secure_storage:

Having the Flutter team maintain all popular packages is infeasible, and there is nothing about secure storage that involves specific Flutter team expertise.
Competing with an established, actively maintained plugin duplicates effort that can be better spent on existing first-party packages, and undermines the goal of creating a thriving package ecosystem.


Docker swarm

Title of change
why the change and what has changed
Checklist

[ ] Unit tests written
[ ] Manually tested
[ ] Prettier & ESLint were run
[ ] New dependencies are included in package-lock.json

Screenshot
insert screenshot if needed

@mmahalwy Is this one to throw out? Was the migration to docker swarm successful, etc.?


Add a few samples based on support of jspecify annotations in Kotlin

Here is a few tests from Kotlin with rewritten Kotlin use sites to Java ones.
It's quite possible that some annotations are missing or jspecify_nullness_mismatch is misused somewhere in accordance with the latest spec, so the review is required. Now inside Kotlin, we can only handle jspecify_nullness_mismatch (compare with errors or warnings from the Kotlin type enhancement).
The next step for Kotlin is to take all existing jspecify tests, automatically convert them to Kotlin use sites and support them in our test infrastructure if needed. After that we are going to create a public build with status of those tests passing.

Thanks. JetBrains has already accepted the corporate CLA, so we need you to do this part:

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).

I've found out that JetBrains doesn't restrict employees from participating in Google open source projects so it seems no action needed, right?

@googlebot rescan

Thanks again for these, and I'm sorry again that I've taken so long to get to them.
I've pushed several commits to your repo. I hope that's OK.
I have tried to separate out the cleanup changes (like adding licenses and reformatting code) from the functional changes.
Th functional changes are:

https://github.com/jspecify/jspecify/pull/148/commits/d571282356f315225cc323349ecab013444200b1: Some files had a Use class that was not annotated @DefaultNonNull. This meant that their method parameters all had unspecified nullness. Thus, many operations on those parameters would need jspecify_nullness_not_enough_information comments. To avoid adding those comments, I changed the files to operate on fields or methods that are known to produce non-nullable values.
https://github.com/jspecify/jspecify/pull/148/commits/6560f3bee65c731632e3c84bf382805a3fd84679: I found some places that appeared to need jspecify_nullness_mismatch or jspecify_nullness_not_enough_information comments. Most of them were jspecify_nullness_not_enough_information. I wouldn't expect Kotlin to issue any warnings or errors for those, so I think the changes are no-ops for you. In some cases, I did add jspecify_nullness_mismatch. Usually, that was because a line contained chained method calls, one of which was safe and one of which was not. If you'd prefer to remove the unsafe calls, that would be fine with me.
https://github.com/jspecify/jspecify/pull/148/commits/3c72e8eebc32706ee3cbcc9fc7823aa77afba9f5: I go into a little detail about this in the commit message. It's about <?>.
https://github.com/jspecify/jspecify/pull/148/commits/89c49e75b586fad757295aadd6803137260c252e: I go into a little detail about this in the TODO I added. It's about usage of type variables when the file does not have @DefaultNonNull but the type parameter has a @Nullable bound.

Let me know what you think of all this.
One other note: I am going to try to move these files to separate directories and packages. That way, every class has a unique fully qualified name, as covered in this section of the README.

Thank you, @cpovirk!
I think the changes are fine to me. If something diverges from Kotlin side, then after a while I will just create an additional PR.
jspecify_nullness_not_enough_information may indeed have been missed in some places, mostly due to the fact that we are not yet checking this jspecify mark on the Kotlin side.

Thanks again. I've merged this, and one of the new samples already prevented me from introducing a new bug.


Add option to update saved window to current state

After a few hours of browsing, I usually end up with a large difference between the saved state of the window in Tabli and the actual tabs I have open. Based on the usage guide, it appears that I would have to manually click on each of the unsaved tabs to add them to the window, which is quite tedious. Alternatively, I could unsave the window and re-save it, but in many cases I would like to keep the tabs that I have closed saved as well.
I would like a button (or two buttons) that can update the saved window to the actual window or add the unsaved tabs to the current state. Thanks for this amazing Chrome extension!

I'd love this option. And for me the button is not neccesary, since it's a more specific action I think a key shortcut would be enough. Any of them is fine by me. Thanks for the extension, it's been really useful.

While it doesn't address the specific request in this issue, Tabli does have the ability to restore saved windows to the set of tabs that were open at the time the window was closed:  Go to Tabli preferences (via the menu button next to the search input) and un-check "Only re-open saved tabs when re-opening saved windows".
This isn't the default behavior only because it can be a fairly slow operation to re-open many tabs, and I found this a bit painful in practice, but it's very much a function of how many tabs you regularly have open in your saved windows and how fast those tabs load, which will be very specific to your personal browsing habits.
That's a bit different from what's being requested in this issue, though, so leaving this issue open.

Tabli does have the ability to restore saved windows to the set of tabs that were open at the time the window was closed: Go to Tabli preferences (via the menu button next to the search input) and un-check "Only re-open saved tabs when re-opening saved windows"

In my opinion the formulation of the said parameter is tricky. When I read it, I instinctively understand it as "Regarding reopening saved tabs, it only happens when restoring saved window", whereas the real meaning is the other way around : "When restoring saved window, the only things to be reopened are the saved tabs, not the others (un-checked) tabs formerly present in the saved window"
Reading @antonycourtney 's comment and assuming my paragraph above is correct, I understand that a saved window both saves checked AND unchecked tabs, meaning that there is a real-time saving of those without needing any manual interaction. Thus if I empty my whole history and then close all my browser's (previously Tabli-saved) windows, I'll still be able to restore their tabs afterwards through Tabli ?
When holding the mouse above a tab's left-side box in a saved window, displayed messages are "bookmark this tab" OR "remove bookmark for this tab". Does it mean that the saved-windows 's not-saved tabs won't be saved as bookmark (browser-wide classic definition of "bookmark") but will still be saved somehow in the extension data ?
In this case I guess we may rename this parameter's info text for more clarity, and hence close the issue cause the primary concern of @generic-github-user  doesn't seem to be necessarily adding a button to auto-add all unsaved tabs in a(ll) save window, but instead to cover cases of crashes (i.e real-time saving of currently opened tabs)

New try : something strange happened
With the said parameter unset, my PC shutdown with one window opened due to flat battery. The window was saved but almost all of its opened tabs weren't. When I restored my browser session with the standard Ctrl-Shift-T it successfully restored my opened tabs from before the out-of-battery incident. Of course this part is not due to Tabli but to my browser that remembered which tabs were last opened.
On Tabli-side however, I notice that it considers the restored browser window as a new, unsaved window, but still remembers that its tabs were previously part of the saved window that appears closed on the Tabli display.
That means there is a way Tabli remembers unsaved tabs attribution to saved window, maybe using history ? Meaning why my previous test failed https://github.com/antonycourtney/tabli/issues/129#issuecomment-688356706 : I had emptied the history beforehand.
Recap :
Before out-of-battery

Windows :

Opened

[X] foo (saved)

[X] tab1 (saved) (closed)
[X] tab2 (saved) (closed)
[ ] tab3 (unsaved) (opened)
[ ] tab4 (unsaved) (opened)

Closed

None

After restoration

Windows :

Opened

[ ] AnonymousWindow (unsaved)

[ ] tab3 (unsaved) (opened)
[ ] tab4 (unsaved) (opened)

Closed

[X] foo (saved)

[X] tab1 (saved) (closed)
[X] tab2 (saved) (closed)
[ ] tab3 (unsaved) (closed)
[ ] tab4 (unsaved) (closed)


Petrained weight?

Hi, Thanks for this repo!
Can you give your pretrained weight to everyone?
Best regards

Hi @ngochoangminh,
Sorry for the late reply. At the moment I am still performing testing, so I am unable to provide the pretrained weights. I will provide them at a later time. Thank you for your understanding.


Review all of OPUS for compliance with accessibility guidelines

https://www.w3.org/WAI/WCAG21/Understanding/

https://www.section508.gov/

In general:

add aria-label="Collapse"  (or appropriate) to all unlabeled buttons

ul elements must only contain li; example on front page widgets contains div (op-input)

li parent ul must have role="list" <currently 'tablist'>

document should not have more than one banner landmark  -

ensures landmarks are unique

multiple area role/attribute issues w/"Recent Announcements"

form elements must have labels

select element must have an accessible name

elements must meet enhanced color contrast ratio thresholds

page should contain a level-one heading

aria dialog and alert dialog nodes should have an accessible name

Certain ARIA roles must contain particular children; in this case, the ul element has children which are not allowed

list view table header text should not be empty

links must have discernible text (addition of aria-label to href links)

document should have one landmark (add role="main", etc do appropriate divs); ensures landmarks are unique (role and/or title )

form elements must have labels

All touch targets must be 24px large, or leave sufficient space

Table header text should not be empty

Heading levels should only increase by one (there is an  as part of the download options list)

Select element must have an accessible name (the recommended method for most circumstances is to use the label element and an explicit association using the for and id attributes. )

This is super helpful, @dstopp.  I wonder whether we might want to give a presentation about this at the PDS Management Council "virtual face-to-face" meeting in July.

@mseritan  👀

Since @dstopp has done the analysis, I'm changing this issue to be for actually changing OPUS to meet accessibility guidelines.


Weirdly enough, this extension is not finding its own Intelephense installation

Hi @mikebronner 👋
Recently I noticed that your Intelephense extension stopped working (I cannot pinpoint exactly when that first happened, but my guess is that it stopped working around the time Nova upgraded to 8; I'm currently running Nova 8.3 [Build 343365] under macOS Big Sur 11.6.3 [20G405]).
These are the logs I get (restarting the extension will basically print out the same errors, just on a different workspace storage path). Note that the red exclamation mark is the closest I could come with a symbol that marks the error in Nova (the white exclamation mark inside a red circle).
   Intelephense[20:14:43.906000] Creating extension workspace storage path: /Users/gwyneth/Library/Application Support/Nova/Workspaces/5901757A-1876-40A2-A83F-89948CB68871/genealabs.intelephense
   Intelephense[20:14:43.906000] Creating extension global storage path: /Users/gwyneth/Library/Application Support/Nova/Extensions/genealabs.intelephense
   Intelephense[20:14:43.906000] Creating Intelephense workspace storage path: /Users/gwyneth/Library/Application Support/Nova/Workspaces/5901757A-1876-40A2-A83F-89948CB68871/genealabs.intelephense/intelephense
   Intelephense[20:14:43.906000] Creating Intelephense global storage path: /Users/gwyneth/Library/Application Support/Nova/Extensions/genealabs.intelephense/intelephense
   Intelephense[20:14:44.899000] Starting Intelephense installation.
❗ Intelephense LSP[20:14:48.626000] node:internal/modules/cjs/loader:936
❗ Intelephense LSP[20:14:48.626000]   throw err;
❗ Intelephense LSP[20:14:48.626000]   ^
❗ Intelephense LSP[20:14:48.626000]
❗ Intelephense LSP[20:14:48.626000] Error: Cannot find module '/Users/gwyneth/Library/Application Support/Nova/Workspaces/5901757A-1876-40A2-A83F-89948CB68871/genealabs.intelephense/node_modules/intelephense/lib/intelephense.js'
❗ Intelephense LSP[20:14:48.627000]     at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
❗ Intelephense LSP[20:14:48.627000]     at Function.Module._load (node:internal/modules/cjs/loader:778:27)
❗ Intelephense LSP[20:14:48.627000]     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
❗ Intelephense LSP[20:14:48.627000]     at node:internal/main/run_main_module:17:47 {
❗ Intelephense LSP[20:14:48.627000]   code: 'MODULE_NOT_FOUND',
❗ Intelephense LSP[20:14:48.627000]   requireStack: []
❗ Intelephense LSP[20:14:48.627000] }
❗ Intelephense LSP[20:14:48.627000]
❗ Intelephense LSP[20:14:48.627000] Node.js v17.3.0

I have looked through your code just very superficially, so I might be completely out of my league here, but I believe that, for some reason, npm is failing to create the required node_modules directory inside the workspace.
Indeed, the directory /Users/gwyneth/Library/Application Support/Nova/Workspaces/5901757A-1876-40A2-A83F-89948CB68871/genealabs.intelephense/intelephense does exist — i.e. it was properly created, with 755 permissions (which is about right) and the correct user owning it.
Now, I have several possible explanations for this behaviour, but sadly I cannot figure out to fix them, even if my hypothesis were correct...

I'm currently running PHP 8.1. While this ought not to interfere with npm, your README explicitly mentions that Intelephense does not yet support PHP 8+. For my purposes, it's pretty much irrelevant; while I use some very minor things that appeared in 7.3 or 7.4, I mostly stick to 'old school' PHP, so I wouldn't really worry much about the lack of support for 8+. And the errors on the Nova log do not seem to point to that, anyway...
Almost all CLI software I've got on my Mac (and some of the GUI-based as well) has been installed via Homebrew. In particular, nodejs and npm — because I'm not overly familiar with hard-core JavaScript coding — have been installed, but for many months (years?) I have long suspected that there is something wrong with the configuration. Ironically, I only noticed that when installing one Nova extension, which looked for the installed npm binary in the right place, but... it wasn't there! (Every time  eithernodejs or npm get upgraded, I need to remember to add a symbolic link for npm). This could have some consequences for your code, which may be expecting a rational layout for nodejs, and my Mac just happens to have a very messy installation (but, as said, I don't know how to fix it!).

Also, I wonder if there is a way to use the system-wide Intelephense installation, instead of getting Nova to install its own...
Anyway, any insights into this would be most appreciated! Thanks so much in advance!

Hi @GwynethLlewelyn, thanks for writing in, good to hear from you! I have been absent from the Nova community for the past year or so, as I just spend too much time trying to fix things in Nova packages, and can never get Nova configured as I would like it. I'm doing all my development on remote dev servers, something that Nova doesn't really support either. (I'm back on VSCode, although I would much prefer a native app like Nova -- I had high hopes for it, but my use-case is a bit outside of its scope.)
I think Nova changed how the bootstrapping of language providers works in version 8, and I have not kept up. My apologies for the inconveniences caused. I don't have a quick answer for you at the moment, other than perhaps trying reykjalin's Intelphense package -- not sure if that works or not, either. We didn't have much luck getting Intelephense to run correctly on Nova's language server API, but maybe that has changed now with Nova 8? Once can hope.

... oh, and just for the sake of completeness, I did simply copy the system-wide Intelephense install to the path that your extension expects it, just to understand if it was merely an issue with installing it from within Nova.
Interestingly, these are the logs...
Intelephense LSP[20:57:34.125000] /Users/gwyneth/Library/Application Support/Nova/Workspaces/5901757A-1876-40A2-A83F-89948CB68871/genealabs.intelephense/node_modules/intelephense/lib/intelephense.js:3
Intelephense LSP[20:57:34.293000] is.authority),this.query&&(e.query=this.query),this.fragment&&(e.fragment=this.fragment),e},t}(f),g=((i={})[58]="%3A",i[47]="%2F",i[63]="%3F",i[35]="%23",i[91]="%5B",i[93]="%5D",i[64]="%40",i[33]="%21",i[36]="%24",i[38]="%26",i[39]="%27",i[40]="%28",i[41]="%29",i[42]="%2A",i[43]="%2B",i[44]="%2C",i[59]="%3B",i[61]="%3D",i[32]="%20",i);function _(e,t){for(var n=void 0,r=-1,i=0;i<e.length;i++){var a=e.charCodeAt(i);if(a>=97&&a<=122||a>=65&&a<=90||a>=48&&a<=57||45===a||46===a||95===a||126===a||t&&47===a)-1!==r&&(n+=encodeURIComponent(e.substring(r,i)),r=-1),void 0!==n&&(n+=e.charAt(i));else{void 0===n&&(n=e.substr(0,i));var o=g[a];void 0!==o?(-1!==r&&(n+=encodeURIComponent(e.substring(r,i)),r=-1),n+=o):-1===r&&(r=i)}}return-1!==r&&(n+=encodeURIComponent(e.substring(r))),void 0!==n?n:e}function y(e){for(var t=void 0,n=0;n<e.length;n++){var r=e.charCodeAt(n);35===r||63===r?(void 0===t&&(t=e.substr(0,n)),t+=g[r]):void 0!==t&&(t+=e[n])}return void 0!==t?t:e}function v(e,t){var n;return

... full dump of intelephense.js here in the Nova logs...

Intelephense LSP[20:57:34.345000]     at /Users/gwyneth/Library/Application Support/Nova/Workspaces/5901757A-1876-40A2-A83F-89948CB68871/genealabs.intelephense/node_modules/intelephense/lib/intelephense.js:3:168725
Intelephense LSP[20:57:34.345000]     at /Users/gwyneth/Library/Application Support/Nova/Workspaces/5901757A-1876-40A2-A83F-89948CB68871/genealabs.intelephense/node_modules/intelephense/lib/intelephense.js:3:169019
Intelephense LSP[20:57:34.345000]     at Immediate.<anonymous> (/Users/gwyneth/Library/Application Support/Nova/Workspaces/5901757A-1876-40A2-A83F-89948CB68871/genealabs.intelephense/node_modules/intelephense/lib/intelephense.js:3:169378)

That's not very useful, I guess, but I also get similar errors when manually launching the system-wide installed Intelephense directly from the Homebrew-installed nodejs...

 I have a bit more work to do on the Intelephense extension by providing all the configuration options, but will have that in soon.
Now that I got my Mac Studio, I can go nuts with Docker containers locally and develop locally again.
(At the moment we're using SSH to develop remotely on servers, which is working out great in VSCode, but not for Nova)

Hi @mikebronner! So glad to see you around again :-)
I promptly downloaded your latest version and hurried to test it out — I've got a project which is mostly C# (ugh) but has some PHP in it, which gets flagged by GitHub Actions as being horribly out of date. Time to get some Intelephense magic! 😹
Sadly, however, it seems that I'm stuck with precisely the same errors as before.
Notice how your extension, when creating things on a new workplace under Library/Application Support/Nova/Workspaces/<UUID>, will create (correctly) the directory genealabs.intelephense, but inside it, it places everything under the directory intelephense— while nodejs is expecting to find a node_modules directory first!
Worse than that: the directory intelephense, in my system, is empty. Weird, huh?
All right, it was time for me to fork your code and take a peek at it :-) Fortunately, you write clean, understandable code (as opposed to, uh, some of our fellow Nova extension developers, which shall remain unnamed because I don't want to sound offensive, or, worse, condescending...), and it's also very short, so I managed to spend a few hours hacking at it.
The first thing I noticed was some inconsistency in the way the directories were being called/named. I'm not quite sure if that was intentional or not, but you have defined workspaceStoragePath right at the beginning (to include not only the extension name in the workplace space, but a new directory under it, intelephense — an approach that seems quite reasonable to me), but... somehow, this variable gets called inconsistently. Sometimes you use it, sometimes you don't, and I was confused why you made some of the choices... so, I decided to use workspaceStoragePath for everything, and hoped for the best!
Well, that wasn't enough.
Now, I have absolutely no idea if this is something that only happens in my case, but npm refuses to install anything on a specific directory unless it has a project.json in it. I'm not sure if that's by design or by choice or by mistake or just because I'm really too clueless about how npm is expected to work, but... my point is, with the npm straight out of brew install npm (possibly if one installs npm in other ways, the issue I have does not occur — I don't know!), it only works that way. No matter where in the filesystem I am, by default, it always attempts to use the project.json which I've got on my home directory (let's call it 'my local configuration'), unless, of course, I pass it a --global flag.
In the case of your extension, Intelephense clearly should not be globally installed — there is no need for that, unless the user also uses Intelephense someplace else (and if you're using Nova... you won't be using any other tool. Heh! 😁 ). So, the correct way is to do it exactly as you did (again, IMHO, I'm not an expert...): install Intelephense on a local directory under the control of the Nova ecosystem, and run it from there, for as long as the user wants to use your extension; and clean up afterwards.
Well, I have no idea if I have 'broken' my npm configuration at some point, but the truth is, from what I read on the online npm manuals (very, very briefly! I didn't spend much time on that...), npm is supposed to always work in conjunction with a project.json. You can, however, instruct npm to generate one by default, with reasonable defaults, a process that can be either interactive or automated (basically, replying 'yes' to all questions...).
So, I gave it a try. I changed your code to create a project.json file on the directory that npm expects to find it — workspaceStoragePath, that is — with some reasonable defaults (mostly using data extracted from nova.extension.xxx information, and the rest hard-coded.
Guess what? Everything worked flawlessly on the first attempt! :-) Expect a PR shortly!
Again — I'm not really sure if the problem is simply because I have somehow misconfigured npm in some obscure way, which is perfectly possible. I'm also not sure if there isn't a more elegant way to deal with this. The truth is that, in my case, while working on the PR, as soon as I activated Intelephense with my changes, I started getting lots of notifications on my other windows, where I had a few PHP scripts, alerting me for a series of small issues that I had overlooked... lol. I didn't even switch to those windows, they were happily running in the background, Nova automagically activated the 'new' extension for all of them, and all of them worked (I'm sort of 'upgrading' ancient PHP 4/5 code to 7/8... so you can imagine there will be lots of deprecated functions and obscure errors...).
Anyway, as always, look carefully at whatever code I've submitted, I'm not a JS programmer, there might be much better ways to accomplish the same thing, and, as said, it might be worth checking out if npm is behaving in the 'expected' way first. I'm assuming that, since everything works in your own setup, it means that I have something wrongly configured somewhere — and it might be easy for you to figure out what you expect to be the correct npm installation first, and, if the extension detects that something is wrong with it, then it executes the code that adds the required project.json in the correct place (maybe there is even an option for npm to work without a project.json...?).
Also, please take a look at the directories where you're placing things. For instance, testing for an empty directory (which ought to have a node_modules inside, allegedly created by npm during the installation procedure...) should be a quick fix to at least alert the user that something is wrong.
My wishlist for 1.9.0: add the possibility for using the global npm installation of Intelephense, as an option (just like you have for your other extensions!)...
Cheers, happy code reviewing ;-)

@GwynethLlewelyn   Thanks for you VERY detailed response!!! :) I have been running it successfully on my machine, but I may have some pre-existing settings outside of Nova that satisfied those requirements.

@GwynethLlewelyn Thanks for you VERY detailed response!!! :) I have been running it successfully on my machine, but I may have some pre-existing settings outside of Nova that satisfied those requirements.

Perhaps you could add those to the README.md... I don't know, it's just a suggestion! And in that case you could ignore PR #2 completely :)

For sure! I just have to identify exactly what those are :)

@GwynethLlewelyn if you did want to take a stab at a PR, that would be awesome, even if it just for me to see the changes you made, so that I can make sense of what you had going on

Done :) See #2 :)

Yay! Thanks 🥇


ENDOC-6 Add containers/repo summary and expand on backup/restore tuto…

…rial.

@joewhite101 , this is almost verbatim your content, with formatting added. I expanded the backup/restore tutorial per your notes.


Why does the popover styling look so odd compared to example?

The popover doesn't look like the one in the example docs and it moves as I scroll vs. staying put and looking all nice (like it does in the docs)

I realize this is all volunteer run and it open source. So thank you for that. But it's sooooooooooo endlessly frustrating when you spend hours fighting with something while following the docs exactly.

You need to use bootstrap v4-beta.2 with reactstrap alpha.
Follow the docs for how to install and use reactstrap.
If you don't want to use bootstrap v4, reactstrap recommends react-bootstrap for bootstrap v3.

Pretty sure I am
{
  "name": "CallYourGovernmentCoreUI",
  "version": "1.0.0-alpha.3",
  "private": true,
  "homepage": ".",
  "devDependencies": {
    "firebase": "^4.6.0",
    "google-map-react": "^0.25.0",
    "gulp": "^3.9.1",
    "gulp-concat": "^2.6.0",
    "gulp-sass": "^2.3.2",
    "moment": "^2.19.1",
    "react-loader": "^2.4.2",
    "react-moment": "^0.6.5",
    "react-scripts": "0.8.5",
    "react-soundcloud-widget": "^2.0.4",
    "react-spotify-player": "^1.0.3",
    "react-transition-group": "^2.2.1"
  },
  "dependencies": {
    "bootstrap": "^4.0.0-beta.2",
    "react": "^15.6.2",
    "react-addons-css-transition-group": "^15.4.2",
    "react-addons-transition-group": "^15.4.2",
    "react-breadcrumbs": "^1.5.2",
    "react-dom": "^15.6.2",
    "react-router": "^3.0.2",
    "react-router-dom": "^4.2.2",
    "react-transition-group": "^2.2.1",
    "reactstrap": "^5.0.0-alpha.4"
  },
  "scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test --env=jsdom",
    "eject": "react-scripts eject"
  }
}

Tried this as well:

{
  "name": "CallYourGovernmentCoreUI",
  "version": "1.0.0-alpha.3",
  "private": true,
  "homepage": ".",
  "devDependencies": {
    "firebase": "^4.6.0",
    "google-map-react": "^0.25.0",
    "gulp": "^3.9.1",
    "gulp-concat": "^2.6.0",
    "gulp-sass": "^2.3.2",
    "moment": "^2.19.1",
    "react-loader": "^2.4.2",
    "react-moment": "^0.6.5",
    "react-scripts": "0.8.5",
    "react-soundcloud-widget": "^2.0.4",
    "react-spotify-player": "^1.0.3",
    "react-transition-group": "^2.2.1"
  },
  "dependencies": {
    "bootstrap": "^4.0.0-beta.2",
    "react": "^16.2.0",
    "react-addons-css-transition-group": "^15.4.2",
    "react-addons-transition-group": "^15.4.2",
    "react-breadcrumbs": "^1.5.2",
    "react-dom": "^16.2.0",
    "react-popper": "^0.7.4",
    "react-router": "^3.0.2",
    "react-router-dom": "^4.2.2",
    "react-transition-group": "^2.2.1",
    "reactstrap": "^5.0.0-alpha.4"
  },
  "scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test --env=jsdom",
    "eject": "react-scripts eject"
  }
}

Now getting:
PropTypes.js:8 Uncaught TypeError: Cannot read property 'func' of undefined
    at Object.<anonymous> (PropTypes.js:8)
    at __webpack_require__ (bootstrap f7a4c8009a1d4f678d82:555)
    at fn (bootstrap f7a4c8009a1d4f678d82:86)
    at Object.<anonymous> (index.js:15)
    at __webpack_require__ (bootstrap f7a4c8009a1d4f678d82:555)
    at fn (bootstrap f7a4c8009a1d4f678d82:86)
    at Object.<anonymous> (index.js:3)
    at __webpack_require__ (bootstrap f7a4c8009a1d4f678d82:555)
    at fn (bootstrap f7a4c8009a1d4f678d82:86)
    at Object.<anonymous> (bootstrap f7a4c8009a1d4f678d82:578)

Popovers and collapses work perfectly. It's most likely configuration error on your side. If you want more immediate help you need to reproduce the issue in a codepen where we can confirm the EXACT issue you are seeing.

That's fair. I'm in dependency hell. I'm just going to switch to material ui or https://github.com/react-bootstrap/react-bootstrap. I can't deal with this anymore.

@kpennell You do realize reactstrap has the same deep dependencies (the only dependencies you have to worry about and install on your own) as react-bootstrap... in-fact the only difference when installing is using reactstrap instead of react-bootstrap and using bootstrap v4 instead of v3 (which doesn't even need to be installed if you reference the css from a cdn)......
Maybe if you post some code we can help you figure out the problem with your code.

Turns about you are using bootstrap v4.0.0.alpha.6 which is not support in the latest reactstrap, please upgrade to bootstrap v4.0.0-beta or v4.0.0-beta.2.
I see you are referencing "bootstrap": "^4.0.0-beta.2", in your package.json but you are most likely pulling in v4.0.0.alpha.6 via a CDN reference or just have an outdated version installed locally.
Below are examples, the only difference is the version of the bootstrap css
What you are seeing (using bootstrap 4.0.0-alpha.6): https://www.webpackbin.com/bins/-L-CkY5ee-hDSscZDBUN
What we recommend (uising bootstrap 4.0.0-beta.2): https://www.webpackbin.com/bins/-L-CmZ08c8W40LTWK7YQ

I'll try some things and try other libraries and report if I find a breakthrough


Add support for secret synchronization across clusters

What would you like to be added: Add support for using management cluster secrets in deployments to workload clusters and ideally synchronize them downstream when there are changes.
Why is this needed: https://github.com/aws/eks-anywhere-packages/issues/600 requests for using passwordSecret in MetalLB BGP peer configuration, however, this requires creating the secret on the target cluster manually. If we create the secret from the package config, the package would include a plain-text version of the secret. We could make the controller copy secret data to the values and render a secret on the target cluster using the templates. Ideally, to keep the secret in sync, we'd want to also track changes to the source secret and re-render the package on the target cluster every time.

related https://github.com/aws/eks-anywhere-packages/issues/106 plus maybe support a secret manager as a package


On mobile: move search bar to the bottom

Hello there,
On mobile, the "Search everywhere..." search bar is located at the top, which is nice, but is a bit far for most people's fingers.
Today, mobile browsers even have the url bar at the bottom for reachability purposes.
Would it be possible to have the search bar be sticky at the bottom on the viewport instead of at the top?
Basically having bottom: 0 instead of top: 0 for header and setting top: 0 instead of top: 60px for main in the css.
WDYT?

Hello @Jiehong ,
thanks for the suggestion.
First of all, if this feature is to be implemented, I would like to make it configurable. Personally, I like the current behavior, but I understand that I might be in the minority.
The challenge will be to answer the question what "mobile" means. "Device width" is not a reliable factor, and can lead to issues (e.g. when resizing a desktop browser window). "Hover-able devices" will include tablets.
Having a fixed user configuration option independent of the device width etc. would fulfil your request without having to detect a mobile device. Would this cover your use case? Or do you have other suggestions?

I suppose that both a screen, width and pointer coarse would mostly match smartphones.
Although, today I see that .collections has a media query of @media screen and (min-width: 481px), so this could be a basis.
I think perhaps we could combine your last suggestion of a fixed user configuration that would alter the media query's css content accordingly?


Draining node is called multiple times (30+) while deleting a machine

I created k3s cluster with CAPZ clusterclass, while deleting a machine, even though node drain is successful, CAPI keeps draining the same machine for 30+ times. Need more investigation if this is specific to capi k3s.
Log:
#1st time
I0606 09:56:31.424772       1 machine_controller.go:379] "Draining node" controller="machine" controllerGroup="cluster.x-k8s.io" controllerKind="Machine" Machine="default/demok3s-jtx7s-tpjl2" namespace="default" name="demok3s-jtx7s-tpjl2" reconcileID="e220ef5b-d4d8-454d-a787-cc29777a4d31" KThreesControlPlane="default/demok3s-jtx7s" Cluster="default/demok3s" Node="demok3s-tbbs6-hmxp4"
E0606 09:56:33.831664       1 machine_controller.go:669] "WARNING: ignoring DaemonSet-managed Pods: kube-system/cloud-node-manager-877r7, kube-system/etcd-proxy-dq28c, kube-system/svclb-traefik-9d54adee-jmxgh\n" controller="machine" controllerGroup="cluster.x-k8s.io" controllerKind="Machine" Machine="default/demok3s-jtx7s-tpjl2" namespace="default" name="demok3s-jtx7s-tpjl2" reconcileID="e220ef5b-d4d8-454d-a787-cc29777a4d31" KThreesControlPlane="default/demok3s-jtx7s" Cluster="default/demok3s" Node="demok3s-tbbs6-hmxp4"
I0606 09:56:34.146008       1 machine_controller.go:927] "evicting pod kube-system/traefik-f4564c4f4-fhqsl\n" controller="machine" controllerGroup="cluster.x-k8s.io" controllerKind="Machine" Machine="default/demok3s-jtx7s-tpjl2" namespace="default" name="demok3s-jtx7s-tpjl2" reconcileID="e220ef5b-d4d8-454d-a787-cc29777a4d31" KThreesControlPlane="default/demok3s-jtx7s" Cluster="default/demok3s" Node="demok3s-tbbs6-hmxp4"
...
E0606 09:56:54.324252       1 machine_controller.go:686] "Drain failed, retry in 20s" err="error when waiting for pod \"local-path-provisioner-84db5d44d9-lhvh6\" in namespace \"kube-system\" to terminate: global timeout reached: 20s" controller="machine" controllerGroup="cluster.x-k8s.io" controllerKind="Machine" Machine="default/demok3s-jtx7s-tpjl2" namespace="default" name="demok3s-jtx7s-tpjl2" reconcileID="e220ef5b-d4d8-454d-a787-cc29777a4d31" KThreesControlPlane="default/demok3s-jtx7s" Cluster="default/demok3s" Node="demok3s-tbbs6-hmxp4"
....
# 2nd time (repeated for 30+ times under 2mins)
I0606 09:57:05.236640       1 machine_controller.go:379] "Draining node" controller="machine" controllerGroup="cluster.x-k8s.io" controllerKind="Machine" Machine="default/demok3s-jtx7s-tpjl2" namespace="default" name="demok3s-jtx7s-tpjl2" reconcileID="a706ce50-e0f7-443c-bcd7-33a3168a85ab" KThreesControlPlane="default/demok3s-jtx7s" Cluster="default/demok3s" Node="demok3s-tbbs6-hmxp4"
E0606 09:57:08.328683       1 machine_controller.go:669] "WARNING: ignoring DaemonSet-managed Pods: kube-system/cloud-node-manager-877r7, kube-system/etcd-proxy-dq28c, kube-system/svclb-traefik-9d54adee-jmxgh\n" controller="machine" controllerGroup="cluster.x-k8s.io" controllerKind="Machine" Machine="default/demok3s-jtx7s-tpjl2" namespace="default" name="demok3s-jtx7s-tpjl2" reconcileID="a706ce50-e0f7-443c-bcd7-33a3168a85ab" KThreesControlPlane="default/demok3s-jtx7s" Cluster="default/demok3s" Node="demok3s-tbbs6-hmxp4"
I0606 09:57:08.328722       1 machine_controller.go:690] "Drain successful" controller="machine" controllerGroup="cluster.x-k8s.io" controllerKind="Machine" Machine="default/demok3s-jtx7s-tpjl2" namespace="default" name="demok3s-jtx7s-tpjl2" reconcileID="a706ce50-e0f7-443c-bcd7-33a3168a85ab" KThreesControlPlane="default/demok3s-jtx7s" Cluster="default/demok3s" Node="demok3s-tbbs6-hmxp4"
...
# 37th time -> machine got deleted
I0606 09:59:42.458023       1 machine_controller.go:379] "Draining node" controller="machine" controllerGroup="cluster.x-k8s.io" controllerKind="Machine" Machine="default/demok3s-jtx7s-tpjl2" namespace="default" name="demok3s-jtx7s-tpjl2" reconcileID="af7a743d-dec6-402f-a16d-843dc438d654" KThreesControlPlane="default/demok3s-jtx7s" Cluster="default/demok3s" Node="demok3s-tbbs6-hmxp4"
E0606 09:59:42.765445       1 machine_controller.go:643] "Could not find node from noderef, it may have already been deleted" err="nodes \"demok3s-tbbs6-hmxp4\" not found" controller="machine" controllerGroup="cluster.x-k8s.io" controllerKind="Machine" Machine="default/demok3s-jtx7s-tpjl2" namespace="default" name="demok3s-jtx7s-tpjl2" reconcileID="af7a743d-dec6-402f-a16d-843dc438d654" KThreesControlPlane="default/demok3s-jtx7s" Cluster="default/demok3s" Node="demok3s-tbbs6-hmxp4"
E0606 09:59:42.765538       1 machine_controller.go:710] "Could not find node from noderef, it may have already been deleted" err="Node \"demok3s-tbbs6-hmxp4\" not found" controller="machine" controllerGroup="cluster.x-k8s.io" controllerKind="Machine" Machine="default/demok3s-jtx7s-tpjl2" namespace="default" name="demok3s-jtx7s-tpjl2" reconcileID="af7a743d-dec6-402f-a16d-843dc438d654" KThreesControlPlane="default/demok3s-jtx7s" Cluster="default/demok3s" Node="demok3s-tbbs6-hmxp4"
I0606 09:59:42.766135       1 machine_controller.go:468] "Deleting node" controller="machine" controllerGroup="cluster.x-k8s.io" controllerKind="Machine" Machine="default/demok3s-jtx7s-tpjl2" namespace="default" name="demok3s-jtx7s-tpjl2" reconcileID="af7a743d-dec6-402f-a16d-843dc438d654" KThreesControlPlane="default/demok3s-jtx7s" Cluster="default/demok3s" Node="demok3s-tbbs6-hmxp4"
E0606 09:59:43.098869       1 controller.go:329] "Reconciler error" err="failed to patch Machine default/demok3s-jtx7s-tpjl2: machines.cluster.x-k8s.io \"demok3s-jtx7s-tpjl2\" not found" controller="machine" controllerGroup="cluster.x-k8s.io" controllerKind="Machine" Machine="default/demok3s-jtx7s-tpjl2" namespace="default" name="demok3s-jtx7s-tpjl2" reconcileID="af7a743d-dec6-402f-a16d-843dc438d654"

Could be solved by adding setting nodedraintimeout to something short like 30s. But it is a potential issue if we keep sending lots of unnecessary messages to api server.

it seems that after removing etcd from the machine to be deleted, that machine still receives apiserver requests but failed to responds.
Let's confirm if that's the case, and why loadbalaner doesn't remove the unresponding apiserver.

it seems that after removing etcd from the machine to be deleted, that machine still receives apiserver requests but failed to responds.
Let's confirm if that's the case, and why loadbalaner doesn't remove the unresponding apiserver.

More detail about the potential bug we found:
Bug
I created a local management cluster, and created a k3s workload cluster with 3 CPs. During upgrade, I observed the upgrade  process takes a very long time, from the log, I observed that k3s controlplane controller complains that it could not reach the api server. The problem persists and after an hour, it finally being able to reach the api server. What is interesting is that the api server is reachable with kubeconfig during this period.
E0611 08:05:43.195801       1 controller.go:329] "Reconciler error" err="failed to create cluster accessor: error creating http client and mapper for remote cluster \"default/demok3s\": error creating client for remote cluster \"default/demok3s\": error getting rest mapping: failed to get API group resources: unable to retrieve the complete list of server APIs: v1: Get \"https://demok3s-cd37da3.eastus.cloudapp.azure.com:6443/api/v1?timeout=10s\": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" ClusterResourceSet="default/crs-azure-cn" namespace="default" name="crs-azure-cn" reconcileID="4652e61f-c74d-4182-a35d-47001dd5db07"
(repeating.....)

Also, draining node could also fail due to timeout, the log from CAPI core:
I0611 08:25:21.039890       1 recorder.go:104] "error draining Machine's node \"demok3s-zbwfr-9vkxq\": unable to get node demok3s-zbwfr-9vkxq: Get \"https://demok3s-cd37da3.eastus.cloudapp.azure.com:6443/api/v1/nodes/demok3s-zbwfr-9vkxq?timeout=10s\": net/http: request canceled (Client.Timeout exceeded while awaiting headers)" logger="events" type="Warning" object={"kind":"Machine","namespace":"default","name":"demok3s-9xzb4-d5vxx","uid":"de5598fb-ac2c-4f2f-9bf6-ae8f4df1923b","apiVersion":"cluster.x-k8s.io/v1beta1","resourceVersion":"40683"} reason="FailedDrainNode"
(repeating.....)

By moving the management cluster to Azure, the problem seems to be fixed, but we also observed the timeout log  occassionally, lasting for ~1 minutes.
Potential cause
This is the image for the Azure load balancer when we upgrade a machine. During upgrade, a machine is being deleting (in this image, machine z95c7 is being deleting, and we have removed its etcd member, and its api server is not reachable), however, it is still inside the azure load balancer pool. We are suspecting that k3s controlplane controller is trying to sending request to the deleting machine, which causing the timeout.


Binding not working in HttpPost

The parameter binding in this controller worked on RC1 but fails after migrating the project to RC2.
    [HttpPost]
    [Authorize]
    public HttpResponseMessage Post(string id, string value)
    {
    _siteService.CreateSite(id, value);
    }

Request payload is the following when debugging in Chrome
id=cab37355-605c-416e-aabe-a262dfba5e26&value=water
But both id and value are null at a breakpoint within the action.
This is my project.json
{
  "version": "1.0.0-*",
  "buildOptions": {
    "emitEntryPoint": true
  },

  "dependencies": {
    "Microsoft.NETCore.App": {
      "version": "1.0.0-rc2-3002702",
      "type": "platform"
    },
    "Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore": "1.0.0-rc2-final",
    "Autofac.Extensions.DependencyInjection": "4.0.0-rc2-240",
    "Microsoft.AspNetCore.Server.IISIntegration": "1.0.0-rc2-final",
    "Microsoft.EntityFrameworkCore.InMemory": "1.0.0-rc2-final",
    "Microsoft.AspNetCore.Mvc": "1.0.0-rc2-final",
    "Microsoft.AspNetCore.Server.Kestrel": "1.0.0-rc2-final",
    "Microsoft.AspNetCore.StaticFiles": "1.0.0-rc2-final",
    "Microsoft.Extensions.Configuration.FileExtensions": "1.0.0-rc2-final",
    "Microsoft.Extensions.Configuration.Json": "1.0.0-rc2-final",
    "Microsoft.Extensions.Logging": "1.0.0-rc2-final",
    "Microsoft.Extensions.Logging.Console": "1.0.0-rc2-final",
    "Microsoft.Extensions.Logging.Debug": "1.0.0-rc2-final",
    "Microsoft.Framework.DependencyInjection": "1.0.0-beta8",
    "VisitorDigitalSignIn.Core": "1.0.0-*",
    "Microsoft.EntityFrameworkCore.Tools": "1.0.0-preview1-final",
    "Microsoft.EntityFrameworkCore.SqlServer": "1.0.0-rc2-final",
    "Microsoft.AspNetCore.Cors": "1.0.0-rc2-final",
    "MailKit": "1.3.0-beta7",
    "Microsoft.AspNetCore.Authentication.JwtBearer": "1.0.0-rc2-final",
    "Microsoft.Extensions.Configuration.EnvironmentVariables": "1.0.0-rc2-final",
    "Serilog.Extensions.Logging": "1.0.0-rc2-10110",
    "Serilog.Sinks.Seq": "2.0.0-rc-46"
  },

  "tools": {
    "Microsoft.AspNetCore.Server.IISIntegration.Tools": {
      "version": "1.0.0-preview1-final",
      "imports": "portable-net45+win8+dnxcore50"
    },
    "Microsoft.EntityFrameworkCore.Tools": {
      "version": "1.0.0-preview1-final",
      "imports": [
        "portable-net45+win8+dnxcore50",
        "portable-net45+win8"
      ]
    },
    "Microsoft.Extensions.SecretManager.Tools": {
      "version": "1.0.0-preview1-final",
      "imports": "portable-net45+win8+dnxcore50"
    },
    "Microsoft.VisualStudio.Web.CodeGeneration.Tools": {
      "version": "1.0.0-preview1-final",
      "imports": [
        "portable-net45+win8+dnxcore50",
        "portable-net45+win8"
      ]
    }
  },
  "scripts": {
    "postpublish": "dotnet publish-iis --publish-folder %publish:OutputPath% --framework %publish:FullTargetFramework%"
  },

  "frameworks": {
    "netcoreapp1.0": {
      "imports": [
        "dotnet5.6",
        "dnxcore50",
        "portable-net45+win8"
      ]
    }
  },
  "publishOptions": {
    "include": [
      "wwwroot",
      "Views",
      "appsettings.json",
      "web.config"
    ]
  }
}

There are several things that might be going on. Have you tried adding [FromQuery] to each parameter? Are the values sent on the query string or on the body?
From what I see you are using the Web API compatiblity shim, is that correct?

I did have Web API compatibility shim before but removed it to see if it made any difference to this working.  No success.  I tired [FromBody] on both but no success.  I will try [FromQuery] when I'm back at my pc.
Values are sent in the body.  I'm using angular2 to do the post.  The authHttpbelow is just a wrapper to add authorization to the standard angular2 http post.
    addSite(siteName: string) {
        let newSite = new SimpleKeyValue(GuidGenerator.generateGuid(), siteName);
        var body = "id=" + newSite.id + "&value=" + newSite.value;
        var headers = new Headers({ 'Content-Type': 'application/x-www-form-urlencoded' });
        var options = new RequestOptions({ headers: headers });
        this.authHttp.post(this._postSiteUrl, body, options).share()
            .map(response => response.json()).subscribe(() => {
                this._dataStore.sites.push(new Site(newSite.id, newSite.value));
                this._dataStore.sites = this._dataStore.sites.slice(0);
                this._sites.next(this._dataStore.sites);
            }, error => console.log("Could not add new site."));
    }

I believe you can only have one parameter coming from the body, I would try to group those two parameters together in a class and add [FromBody] to the parameter. If you are using HttpResponseMessage you will need the shim.

Thanks for your help javiercn.  I readded the shim (was needed after all) and passed the two parameters as an object with [FromBody] and it works fine now :smile:


2 high severity vulnerabilities

# npm audit report

tar  <=4.4.17
Severity: high
Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization - https://github.com/advisories/GHSA-5955-9wpr-37jh
Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links - https://github.com/advisories/GHSA-qq89-hq3f-393p
Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links - https://github.com/advisories/GHSA-9r2w-394v-53qc
Arbitrary File Creation/Overwrite due to insufficient absolute path sanitization - https://github.com/advisories/GHSA-3jfq-g458-7qm9
Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning - https://github.com/advisories/GHSA-r628-mhmh-qjhw
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/react-js-pagination/node_modules/tar
  react-js-pagination  >=3.0.3
  Depends on vulnerable versions of tar
  node_modules/react-js-pagination

2 high severity vulnerabilities

Is this bad?

Does anyone know why tar is even a dependency of this package? I looked through the source code of react-js-pagination and didn't immediately see any code related to tar. Why would an archiving tool be a dependency of a react pagination plugin anyway?

They fixed this issue in https://github.com/wwwaiser/react-js-pagination/commit/56301a6b25ef60072801d9e6593c74f4bfdd6cb4, but never made a release out of it.


Disable pinch-zoom functionality

This fixes #156
We don't have yet a specific config file/location for the renderer.
Should I keep it in the index.js file?

Yep that sounds great.


⭐ Stars nulled

Unfortunately stars was nulled for cupertino-pane after some origin issues between 2 repos.
Already touched GitHub support and await for ticket progress.
I hope support can helps to restore all stars.
Otherwise, don't upset. Eventually, all who's needs drawer solution will come here with new stars.

Hello Roman,
Thank you for reaching out to GitHub Support. When changing a repository from public to private all stars and followers are lost. It is unfortunately not possible to restore these to the repository after switching it back to public.
I can certainly understand how disappointing this must be! I'll forward this along to our product team to request that we retain the stars and followers so that they can be re-displayed when changing the repository back to public.
Thanks,

Steve G.
GitHub Support


Check Docker version in Kubelet /healthz handler

This cl is fixing issue #3003

This will add a second approach to docker version checking to the code base, see:
https://github.com/GoogleCloudPlatform/kubernetes/blob/207d0f5d405a41b5b131f07fe89c907b68231ce7/pkg/kubelet/dockertools/docker.go#L107
Let's refactor so that the implementation of this check is shared.
My bad, I should have told you about that implementation when I was discussing the issue with you elsewhere.  Sorry!
--brendan

Please take another look.
I have one more question. I've refactored the code to use the method you mentioned. However, this method is returning the API version (which is currently 1.16). Previously I was testing the Docker version itself (which is currently 1.4.1).
Which value to we really want to test?

Please take another look - all tests are now passing.


Environmetal variable for temporary directory

Allow the user to specify the the temporary directoy where the batch upload creates a temporary file.
This implementation goes in the create_resolvers.ejs view. Line 305 in this file

Found a very simple solution.
Using os.tmpdir() to find and use the system's temporary directory.
In the production docker-compose.yml the container's /tmp volume is mounted onto the host system's /tmp.
commit in ScienceDbStarterPack
commit in graphql-server-model-codegen


Using a period as a separator changes the date value altogether

`>>> extract_dates("31.12.1986")[0].strftime('%m/%d/%Y')
'03/01/2012'`

Hi, @saikiranbandaru .  That's a great find.  I'll try to think up a way to implement this.


able to add one or more threshold lines to charts

@andygout @laurieboyes @adambraimbridge @mmockett FYI
so you can e.g. have a horizontal line called 'target'


Complete update to ZF v3 releases

This patch builds on #346, to provide forwards compatibility with v3 releases of ZF components.
In addition to the changes already present in #346, this patch:

Moves all factories originally defined in the Module::getServiceConfig() and Module::getControllerConfig() methods into their own classes, all under the ZF\Apigility\Admin\Factory namespace.
Redefines all invokables as factories using InvokableFactory; aliases were also created when necessary.
Updates configuration to use ::class notation.
Updates all existing factories to be forwards compatible with zend-servicemanager v3.
Ensures all listeners are attached in a forwards compatible fashion.
Ensures all triggers happen correctly.
Ensures checks for RouteMatch will check for either the v2 or v3 router releases.
Updates to zf-apigility 1.3 stable release.

Currently, tests pass with v2 ZF releases, but fail with dozens of errors and several failures when tested against v3 releases; this will be the focus for completion of the patch.
TODO

[x] Extract listeners from the Module class to their own classes (and include tests):

[x] normalizeMatchedControllerServiceName
[x] normalizeMatchedInputFilterName
[x] onRoute
[x] onRender
[x] onFinish
[x] HalPlugin::onRenderEntity
[x] HalPlugin::onRenderCollectionEntity

[x] Test all new factories

[x] AuthenticationControllerFactory
[x] AuthenticationModelFactory
[x] AuthorizationControllerFactory
[x] AuthorizationModelFactory
[x] ConfigControllerFactory
[x] ContentNegotiationModelFactory
[x] ContentNegotiationResourceFactory
[x] DbAdapterModelFactory
[x] DbAdapterResourceFactory
[x] DbAutodiscoveryModelFactory
[x] DoctrineAdapterModelFactory
[x] DoctrineAdapterResourceFactory
[x] ModuleConfigControllerFactory
[x] ModuleCreationControllerFactory
[x] ModuleModelFactory
[x] ModulePathSpecFactory
[x] ModuleResourceFactory
[x] ModuleVersioningModelFactoryFactory
[x] RestServiceModelFactoryFactory
[x] RestServiceResourceFactory
[x] RpcServiceModelFactoryFactory
[x] RpcServiceResourceFactory
[x] SourceControllerFactory
[x] VersioningControllerFactory
[x] VersioningModelFactoryFactory

Ready for review!
Ping @zfcampus/community-review-team and @webimpress

... and tests are passing, after doing a re-install to fix a composer.lock issue. REALLY READY NOW! :smile:

https://github.com/weierophinney/zf-apigility-admin/blob/ae607978c028bd3f468a9043483bcef96ed798ac/config/module.config.php#L385
missing C
I'll review it in full tomorrow.
It's was a lot of work, thanks @weierophinney ! 😄

missing C

Fixed - thanks, @webimpress !

@webimpress All listeners are now extracted and tested, including updates to use ZF\Hal\Entity::getEntity() instead of ZF\Hal\Entity::$entity. Turning to the factories now.

All factories now have test cases; doing so unearthed a few issues, which I was able to fix.
Additionally, @webimpress discovered an issue with how InjectModuleResourceLinksListener was attaching its onHalRenderEvents listener. The original code was passing an array events to the event manager's attach() method; however, this is no longer supported in zend-eventmanager v3. I've updated the tests for that listener and the code for it to attach the listener to each event individually.

Ping @zfcampus/community-review-team ; ready for review (@webimpress is already working on it...).

A few thoughts:

[ ] Move factories to corresponding namespaces - now there is mess, some factories are in Factories and some in Controller namespace, etc. Not sure if new Factory namespace is needed as long as all factories are with Factory suffix.

[ ] s/hal/Hal/ in Controller\AuthenticationController#L69

[ ] controllers.aliases in module..config.php - do we need them? Can we sort it out a bit? - Not sure if everything is right in controllers.factories - for example:
Controller\Validators::class => Controller\ValidatorsControllerFactory::class,
but class Controller\Validators doesn't exist (I know, ::class works anyway), but maybe we should have in aliases:
Controller\Validators::class => Controller\ValidatorController::class
and in factories:
Controller\ValidatorsController::class => Controller\ValidatorsControllerFactory::class

[ ] Alphabetical order in:

[ ] service_manager.factories
[ ] controllers.aliases
[ ] controller.factories
[ ] input_filters.aliases
[ ] input_filters.factories

[ ] Short array notation in files test/Model/TestAsset/module/Version/config/*.config.php.dist and remove controllers.invokables in module.config.php.dist

[ ] RpcServiceResource::__construct and RestServiceResource::getModel php-docs needs update

@weierophinney Thanks for your work!
I'll continue my review later.
I'd like to run apigility admin on my local and check if everything works as expected. Will do it later.

controllers.aliases in module..config.php - do we need them?

Yes, they're needed, for a few reasons.
Every single alias I created was originally defined as an invokable; in each of these cases, though, the service name did not match the actual class being created, but instead truncated the class name to omit the Controller suffix.
Internally, when we use the invokables key, it does exactly what I did here: define an alias of the short name to the FQCN, and a factory mapping the FQCN to InvokableFactory.
In the cases where we have a short name pointing to a factory name, these generally already existed, and modifying them to do create alias/FQCN + FQCN/factory pairs would potentially break cases where an alternate factory was defined by an end-user.

Factories are all moved into their respective namespaces now, @webimpress .

I'm now testing this against the skeleton, and have discovered that:

StrategyController is calling getServiceLocator(). It may have an actual need to do so, but I'll update it to receive it during instantiation.
Some of the existing controller factories were written as invokables, and thus call getServiceLocator() internally in order to retrieve the parent context. I will update these to implement FactoryInterface.

All controller factories are now updated, and the StrategyController was also updated to accept a ContainerInterface to the constructor.

I've rebased this against #350 at this time.

@weierophinney
this part is gone after rebase:
 -    public function init(ModuleManagerInterface $modules)
 -    {
 -        $loaded = $modules->getLoadedModules(false);
 -        if (isset($loaded['ZF\Apigility\Admin\Ui'])) {
 -            return;
 -        }
 -
 -        $modules->loadModule('ZF\Apigility\Admin\Ui');
 -    }

Now we need add module 'ZF\\Apigility\\Admin\\Ui' manually into development.config.php, is it fine?

Now we need add module 'ZF\Apigility\Admin\Ui' manually into development.config.php, is it fine?

Nope, bad rebase. I'll push that back in a moment.

@webimpress Just pushed commits addressing your last round of feedback.

I've just done the following to test that upgrading works as expected:

Installed a fresh Apigility project, using the installer from the website.
Updated the composer.json to make the following changes:

Added a path repository pointing to my local checkout of zf-apigility-admin
Updated the zf-apigility-admin constraint to read @dev

Ran composer update

This picked up the latest releases of all Apigility components, with the exception of zf-development-mode (as the current default constraint is ~2.0), and the latest v2 releases of all zf components (as the default skeleton has zendframework with the constraint ^2.5.3 as the default).
This mostly works; the one issue is that we've removed rwoverdijk/assetmanager as a requirement in zf-apigility, zf-apigility-admin, and zf-apigility-admin-ui, but the skeleton enables the AssetManager module. This can be corrected by running:
$ composer require rwoverdijk/assetmanager

after an update, however.
Once I'd done that, I tested all functionality of the admin UI, and found everything worked perfectly out-of-the-box, with the exception of the UI issues that @webimpress and I discussed over the weekend (in particular, the sidebar does not refresh correctly after creating services; additionally, the fully service name is listed in the service title — e.g., Test-V1-Rest-Foo-Controller vs the simpler Foo).
My thoughts on this are that we will need to document the following migration steps:

Initial update will be:

composer update
composer require rwoverdijk/assetmanager

More comprehensive update will be:

composer.json changes:

Remove the entry for zendframework/zendframework from the requirements.
Update the zfcampus/zf-development-mode constraint to ^2.1 || ^3.0 (or just ^3.0).
Remove the entry for rwoverdijk/assetmanager.
Add zfcampus/zf-asset-manager with constraint ^1.0 as a development requirement.

config/modules.config.php changes:

Remove the following entries:

AssetManager
ZF\DevelopmentMode

Add the following entries to config/modules.config.php (at the top of the list):

Zend\Db
Zend\Filter
Zend\Hydrator
Zend\InputFilter
Zend\Paginator
Zend\Router
Zend\Validator

Remove, recursively, the vendor/ directory and composer.lock.
Run composer install.

The above will update the application to the latest versions of all Apigility modules, as well as ZF v3 releases.

@ezimuel has suggested we provide a vendor binary script that performs the migration steps; I'm going to work on that now.

Upgrade script is now provided!

CHANGELOG written, and migration instructions provided in the README.

@weierophinney Please have a look on my PR with some small fixes to your branch: https://github.com/weierophinney/zf-apigility-admin/pull/1
I've added also some TODO / Questions in the description, also copied below (some of them we discussed yesterday):
TODO / Quesions:

[ ] setRequest method in AuthorizationController should be removed or at least marked as @deprecated
[ ] VersioningModelFactoryFactory should be marked as @deprecated as long as VersioningModelFactory is deprecated
[ ] upgrade script should leave one empty line at the end of modules.config.php and composer.json
[ ] upgrade script should remove ZFTool module from development.config.php and development.config.php.dist
[ ] HHVM tests need to be checked - many of them are failing
[ ] remove markTestSkipped in some mongo tests (fix if needed) - all test should run on travis
[ ] check tests sh: 1: tree: not found in https://travis-ci.org/zfcampus/zf-apigility-admin/jobs/150746938#L415

Thanks!

@weierophinney upgrade script does not remove ZFTool from modules list (development.config.php and development.config.php.dist).
Now one test is failing on PHP7. I would go with slightly different travis configuration for mongo:
https://github.com/webimpress/zf-apigility-doctrine/blob/0294a485c27d6fa3564f2d1dba1759b622592599/.travis.yml
I'm not sure about HHVM and mongo configuration, it doesn't work for me now. But maybe we can skip it for now on hhvm?


Document cert-manager manual installation

The latest release of the CAPI Operator doesn't support installing cert-manager as a dependency, this PR removes cert-manager dependency docs.
Fixes https://github.com/rancher/turtles-docs/issues/125

Can you also update https://turtles.docs.rancher.com/#prerequisites accordingly?

@furkatgofurov7 ptal, I updated the PR

Looks good, thanks


[Rancher v2.6.4] Cluster Management page displays incorrect cluster count due to Harvester onboarding

Setup

Rancher version: 2.6.4  (also present in 2.6.5-rc1)
Browser type & version: Edge 100.0.1185.39

Describe the bug
On-boarding a Harvester cluster causes the cluster count in Clusters & Mgmt Clusters to increment by 1 even though Harvester cluster is not displayed or able to be managed
To Reproduce
Onboard Harvester cluster via Virtualization Management
Expected Result
Cluster count in left pane of Cluster Management page should reflect the number of downstream clusters the user is able to manage to avoid confusion

backend input no happening, closing


Added all_scores property to BeamSearchDecoderOutput to expose scores for all tokens

Description
The purpose of this PR is expose the scores for all token IDs, not only the ones that are selected as predicted_ids. In doing so, we enable the user of the BeamSearchDecoder to directly access the logits as requested in #1915.
This PR also fixes documentation from #1916 that described the scores property as having the shape of all_scores. Based on the existing unit tests, it looks as though the intent is for scores to have the shape [batch_size, beam_width], not [batch_size, beam_width, vocab_size], which is what is now exposed through all_scores.
Type of change

[ ] Bug fix
[ ] New Tutorial
[X] Updated or additional documentation
[ ] Additional Testing
[ ] New Activation and the changes conform to the activation contribution guidelines
[ ] New Callback and the changes conform to the callback contribution guidelines
[ ] New Image addition and the changes conform to the image op contribution guidelines
[ ] New Layer and the changes conform to the layer contribution guidelines
[ ] New Loss and the changes conform to the loss contribution guidelines
[ ] New Metric and the changes conform to the metric contribution guidelines
[ ] New Optimizer and the changes conform to the optimizer contribution guidelines
[ ] New RNN Cell and the changes conform to the rnn contribution guidelines
[X] New Seq2seq addition and the changes conform to the seq2seq contribution guidelines
[ ] New Text addition and the changes conform to the text op contribution guidelines

Checklist:

[X] I've properly formatted my code according to the guidelines

[ ] By running Black + Flake8
[ ] By running pre-commit hooks

[ ] This PR addresses an already submitted issue for TensorFlow Addons
[X] I have made corresponding changes to the documentation
[X] I have added tests that prove my fix is effective or that my feature works
[ ] This PR contains modifications to C++ custom-ops

How Has This Been Tested?
Unit tests have been added to verify that the new property has the correct shape.

@googlebot I signed it!

FYI, @guillaumekln @qlzh727 looks like failures are unrelated:
#17 [base_install 9/15] RUN python -m pip install --default-timeout=1000 ten...
#17 0.662 Collecting tensorflow==2.3.0
#17 1.925   Downloading https://files.pythonhosted.org/packages/fc/55/28d97d62ac476d589acdbf501f20dfb6265fbc016dcbd2e0e628d5b4b87a/tensorflow-2.3.0-cp35-cp35m-manylinux2010_x86_64.whl (320.4MB)
#17 4.233 THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them.
#17 4.233     tensorflow==2.3.0 from https://files.pythonhosted.org/packages/fc/55/28d97d62ac476d589acdbf501f20dfb6265fbc016dcbd2e0e628d5b4b87a/tensorflow-2.3.0-cp35-cp35m-manylinux2010_x86_64.whl#sha256=6f74ef59dc59cf8f2002738c65dffa591e2c332e9b1b4ced33ff8d39b6fb477c:
#17 4.233         Expected sha256 6f74ef59dc59cf8f2002738c65dffa591e2c332e9b1b4ced33ff8d39b6fb477c
#17 4.233              Got        d061cfc74bce02ceecbf5f2f9d3459b562dc7afec6e9d0f2f5cc9e4bc05e3286
#17 4.233
#17 4.358 You are using pip version 19.0, however version 20.2.1 is available.
#17 4.358 You should consider upgrading via the 'pip install --upgrade pip' command.
#17 ERROR: executor failed running [/bin/sh -c python -m pip install --default-timeout=1000 tensorflow==$TF_VERSION]: runc did not terminate sucessfully

FYI, @guillaumekln @qlzh727 looks like failures are unrelated:
#17 [base_install 9/15] RUN python -m pip install --default-timeout=1000 ten...
#17 0.662 Collecting tensorflow==2.3.0
#17 1.925   Downloading https://files.pythonhosted.org/packages/fc/55/28d97d62ac476d589acdbf501f20dfb6265fbc016dcbd2e0e628d5b4b87a/tensorflow-2.3.0-cp35-cp35m-manylinux2010_x86_64.whl (320.4MB)
#17 4.233 THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them.
#17 4.233     tensorflow==2.3.0 from https://files.pythonhosted.org/packages/fc/55/28d97d62ac476d589acdbf501f20dfb6265fbc016dcbd2e0e628d5b4b87a/tensorflow-2.3.0-cp35-cp35m-manylinux2010_x86_64.whl#sha256=6f74ef59dc59cf8f2002738c65dffa591e2c332e9b1b4ced33ff8d39b6fb477c:
#17 4.233         Expected sha256 6f74ef59dc59cf8f2002738c65dffa591e2c332e9b1b4ced33ff8d39b6fb477c
#17 4.233              Got        d061cfc74bce02ceecbf5f2f9d3459b562dc7afec6e9d0f2f5cc9e4bc05e3286
#17 4.233
#17 4.358 You are using pip version 19.0, however version 20.2.1 is available.
#17 4.358 You should consider upgrading via the 'pip install --upgrade pip' command.
#17 ERROR: executor failed running [/bin/sh -c python -m pip install --default-timeout=1000 tensorflow==$TF_VERSION]: runc did not terminate sucessfully

Sorry about that it's a flaky failure related to GitHub Actions

Thanks for the change. I'm a little bit concerned about memory usage, especially for users who do not need this information. Could it be optional in some way?

Hey @guillaumekln, thanks for taking a look.  I added a param to BeamSearchDecoder called output_all_scores that will toggle the BeamSearchDecoderOutput.scores property to contain either the top scores (default) or all scores.  Let me know if this addresses your concerns.
I figured this would make more sense than keeping both properties, but having one be None unless an upstream param is set, which seems unintuitive.


Inquiry

Hi.
As I already have thousands of viral genome sequences, I do not need pre-precessing (e.g. assembly)
Is there any submodule to validate whether my genomes are giant virus or not ?
Thanks !

Do you plan on binning them or are they already binned?
On Wed, Dec 11, 2024, 10:49 PM ||||||||||||||||||||||||||||||||||||||||||||
@.***> wrote:

Hi.
As I already have thousands of viral genome sequences, I do not need
pre-precessing (e.g. assembly)
Is there any submodule to validate whether my genomes are giant virus or
not ?
Thanks !
—
Reply to this email directly, view it on GitHub
https://github.com/BenMinch/PIGv/issues/4, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUT6BLJTFICRX4CFKPPKZST2FEBV3AVCNFSM6AAAAABTO35P3SVHI2DSMVQWIX3LMV43ASLTON2WKOZSG4ZTINRZGE4DOMQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

No. They are already binned

How confident are you in your coding abilities. There is a simple way to
comment out the binning step so that you can use bins as input.
On Wed, Dec 11, 2024, 11:02 PM ||||||||||||||||||||||||||||||||||||||||||||
@.***> wrote:

No. They are already binned
—
Reply to this email directly, view it on GitHub
https://github.com/BenMinch/PIGv/issues/4#issuecomment-2537763396, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AUT6BLOYNEXZSU7WXJB5Y6L2FEDGXAVCNFSM6AAAAABTO35P3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZXG43DGMZZGY
.
You are receiving this because you commented.Message ID:
@.***>


Partial fix for #172 to set content type for views

@dsyer I'm not sure about Spring's MediaType and if I'm using it correctly.
One thing I did miss is the View was not using the newer output stream work which will use pre-encoding. That is fixed and so is the content type.
Because Spring seems to take preference on View returns and ignores @ResponseBody only these two use the MessageConverter:
http://localhost:8080/templateModel
http://localhost:8080/responseEntity
However the problem with the above (MessageConverter) is the Transfer-Encoding is "chunked". This is bad for HTML. TechEmpower benchmark will straight up disqualify for that.

@dsyer
Also I wonder if the MockHttpServlet stuff will test this (ie I can check for the headers) or do I need a full end to end?
I will try but it has been a while since I have used Spring's testing stuff.

@dsyer when you get a chance just take a quick look and then I will rebase it to main and then do a patch release.


Pre-Requisite URL change

Hi Team,
in Device registration enterpriseregistration.windows.net is a http end point not https please change https://enterpriseregistration.windows.net to http://enterpriseregistration.windows.net.

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

ID: 816f0138-d336-3905-9f4f-e60c04da9326
Version Independent ID: ce5166e4-5d15-ef1f-1090-576a69e601e8
Content: Configure hybrid Azure Active Directory join for managed domains
Content Source: articles/active-directory/devices/hybrid-azuread-join-managed-domains.md
Service: active-directory
Sub-service: devices
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@sowndarrajandr Thanks for your feedback. AFAIK it is actually a HTTPS endpoint. Can you help me understand why you are suggesting otherwise?

Hi Manoj,
Please check the screenshots i attached.
It may be HTTPS in future but in the past and right now it is HTTP.
If it is going to be HTTPS please let me know the effective change date so, that i can inform some of my customers who have only allowed the HTTP endpoint.

@sowndarrajandr The entire device registration flow happens over SSL, so it has to be HTTPS. Azure AD , does not accept HTTP communication as it is not secure.
Even if you try to access HTTP endpoint, it will be converted to HTTPS. Try to access the HTTP endpoint in Edge or IE to see this behavior.
Please ask all your customers to whitelist HTTPS endpoint.

@sowndarrajandr We will now proceed to close this thread. If you have further questions, please tag me in the comments and I will gladly continue the conversation.


allow logging to systemd journal

SecAuditLog currently does not allow logging to systemd journal. Or at least that's not documented.
Could you please allow logging to systemd journal?
Might be simple to implement. For example any daemon written in bash just has to do echo message and that will end up in systemd journal. No very special code required in ModSecurity. Just write to stdout/stderr normally. Perhaps SecAuditLog stdout?
Another option might be supporting SecAuditLog /dev/log but /dev/log is not a file, it's a unix domain socket file.

@adrelanos Is v3 is safe to output the logs to /dev/stdout. Have you faced any issues by doing that?

@adrelanos Is v3 is safe to output the logs to /dev/stdout. Have you faced any issues by doing that?

I wouldn't know why that wouldn't be safe. Lots of daemons doing that.
SecAuditLog /dev/stdout however doesn't work. Nothing ends up in journal.

I wouldn't know why that wouldn't be safe. Lots of daemons doing that.
SecAuditLog /dev/stdout however doesn't work. Nothing ends up in journal.

Can you perform a test with the DebugLogs? I am going to check the AuditLogs here as well.

Can you perform a test with the DebugLogs? I am going to check the AuditLogs here as well.

My test result:

Set SecDebugLog /dev/stdout. Got the error when reloading Nginx: "Failed to start DebugLog: Failed to open file: /dev/stdout".
Set SecAuditLog /dev/stdout. There is no audit log in systemd journal.

It will be better if it is possible to set SecAuditLog to a Unix domain socket.
I have tried to add setting CURLOPT_UNIX_SOCKET_PATH in /src/utils/https_client.cc and do something simple change.
But the connection to the socket is failed with "Download failed: Couldn't connect to server" shown in debug log. I can see "Sending log to: /dev/log" in the log too. It is the correct path to the socket file.
I am not familiar with the Modsecurity code. Could anybody instruct me to debug this issue? Thanks in advance.


WIP: how to create dataset

What does this PR do?
This is a placeholder for future notebook on how to create a dataset from custom real-world data.
Who can review?
cc @MKhalusova
-->

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Demo Scene not displaying right on Samsung S7 Edge

Hi !
The Demo Scene is working properly on my Nexus 6P but comes out very wrong on the Samsung S7 Edge. Is this a known issue? Or are only Nexus devices supported?
Here's a screenshot of how it outputs

Thanks !

In the Build Settings, make sure you set the default orientation to
Landscape Left.

Thank you, that was it


maximize flag has no effect when f is None

Basically what title says. When using GPyOpt to optimize an externally evaluated function, the maximize flag has no effect.
I would expect this snippet to maximize based on the inputs:
Snippet 1:
X_data = np.array([ [1.0, 1.5, 1.0], [1.5, 3.0, 1.0],
                   [2.0, 5.0, 2.0]])
Y_data = np.array([ [0.7248], [0.4579],
                   [0.4192]])
bo_step = GPyOpt.methods.BayesianOptimization(f=None, domain=domain, X=X_data, Y=Y_data, maximize=True, acquisition_type='EI')
x_next = bo_step.suggest_next_locations()
x_next

array([[1.93984549, 4.90429719, 1.9519504 ]])
This snippet gives the result that I expect.
Snippet 2:
X_data = np.array([ [1.0, 1.5, 1.0], [1.5, 3.0, 1.0],
                   [2.0, 5.0, 2.0]])
Y_data = np.array([ [-0.7248], [-0.4579],
                   [-0.4192]])
bo_step = GPyOpt.methods.BayesianOptimization(f=None, domain=domain, X=X_data, Y=Y_data, maximize=False, acquisition_type='EI')
x_next = bo_step.suggest_next_locations()
x_next

array([[0.95508769, 1.42728523, 1.019358  ]])
Not sure if this is the designed behavior, but I think the naive expected behavior is that Y should be transformed to -Y internally if maximize=True

Also, I didn't follow the code fully, but I think that if Y_init is provided with maximize=True, the initialization is not correct (unless user is aware that -Y_init should be provided).

I also got confused by the maximize flag. The following example reproduces the unexpected behaviour:
import GPyOpt
import numpy as np
import matplotlib.pyplot as plt

def foo(val):
    return (np.sin(val * 8) * val - val ** 2 + val)

def plot_samples(samples_x, samples_y):
    xs = np.arange(-5.0, 5.0, 0.01)
    ys = foo(xs)
    plt.plot(xs, ys)
    plt.plot(samples_x, samples_y, "*r")

bounds = [{'name': 'x', 'type': 'continuous', 'domain': (-5.0, 5.0)}]
max_iter = 20

xs = np.array([[-5.0]])
ys = foo(xs)

for i in range(max_iter):
    bo_gp = GPyOpt.methods.BayesianOptimization(
        f=None,
        domain=bounds,
        model_type="GP",
        acquisition_type ="EI",
        maximize=True,
        initial_design_numdata=len(xs),
        X=xs,
        Y=ys,
        exact_feval=True)

    new_x = bo_gp.suggest_next_locations()
    xs = np.concatenate([xs, new_x])
    ys = np.concatenate([ys, foo(new_x)])

plot_samples(xs, ys)

resulting in:

However, if you change Y=ys to Y=-ys the optimisation produces results as expected and neither of the options maximize=False and maximize=True have any noticeable effect on the quality of the samples:

I'm struggling with the same confusion. I've resorted to simply taking the negative of the objective value as mentioned above, but confused by the necessity for this.

I've also just discovered this issue after a while. Would be nice if this it was pointed out in the documentation since I've run quite a few things without being aware of this.

The problem is that GPyOpt changes a minimization problem into a maximization one by simply changing the sign of the evaluation function:
https://github.com/SheffieldML/GPyOpt/blob/c9e214c49f57af4c7ee92d94ab859f46d65fd842/GPyOpt/methods/bayesian_optimization.py#L106
I guess there is no easy fix for this issue, but maybe one could issue a warning when maximize=True and f=None, so that users know the maximization will not be effective...


在部分情況下存在輸入法異常

系統：Archlinux
桌面環境：gnome on wayland
安裝方式：yay -S fcitx5-mcbopomofo-git
在部分應用中，會像輸入法自動關閉重啟一瞬間，導致那一瞬間的按鍵直接被輸入而沒有被輸入法捕獲，使得輸入的文字異常。
例如：「中文」會變成「j中ㄣˊ」但因為ㄣˊ打不出字，就變成了「j中」，非常耽誤打字
這種情況幾乎都在於xwayland和chromium應用中，原生gtk4和wayland應用沒有這個問題。無論打字快慢都可能發生。
另外，似乎輸入法被切換到其他時沒有清空緩衝區，所以當有輸入中內容時切換會導致再切回來上屏的和輸入中的（帶下滑線）是不同的內容，並會一直持續，除非重啟整個fcitx。應該在每次輸入法啟用時清空一次緩衝區（這段話我打了足有5分鐘！！反覆出現按鍵捕獲的故障）

Thanks for making this report.
See if you can find out which version/commit of fcitx5-mcbopomofo your package manager installed for you. If it's an old version, see if you can try the latest commit or tagged version. Older versions handled the focus out and reset events differently, but at any rate it shouldn't be as jarring as what you described here, even with an older version.

在部分應用中，會像輸入法自動關閉重啟一瞬間，導致那一瞬間的按鍵直接被輸入而沒有被輸入法捕獲

This unfortunately does not sound like an issue with fcitx5-mcbopomofo. An input method only handles events it's told to handle. How those events come to be in the first place, as well as in which sequence they are delivered, is all beyond the input method's control.

另外，似乎輸入法被切換到其他時沒有清空緩衝區

That is strange and sounds more like a problem in the interaction between certain versions of fcitx5 and certain versions of Xwayland or Chromium, or maybe a problem in how the events are managed and passed. My understanding is that fcitx5 would force-commit the pre-edit buffer upon events such os focus-out or reset, and fcitx5-mcbopomofo resets its own internal state upon such events.
fcitx5 also allows one to share input state (it's in the global config)—it may be a factor, but I can't repro the issue with the different settings there.
You may also want to see if it's a problem specific to fcitx5-mcbopomofo, or if other fcitx5 input method modules also exhibit the same problem with your setup.


Is there a way of getting the id of the newly added record like you can do in ef?

I very  much like your product but like the guy in #8 always have these errors when retrieving data

Any chance of a response???? Yours is the only wrapper that works on a Blazor Web App .Net 8 project??

@sohnavcom Yes, give me a bit I'm working on it. I'm bouncing between a lot of projects right now. I'm going to try and get a lot of nice updates for everyone this week.

Closing. Fixed / feature added by @yueyinqiu

@magiccodingman please take a lot at the current implemention:
https://github.com/magiccodingman/Magic.IndexedDb/blob/master/Magic.IndexedDb/IndexDbManager.cs#L131
await CallJavascriptVoid(IndexedDbFunctions.ADD_ITEM, trans, RecordToSend); is inside a nested if block, which means that it might not be invoked. Is is a mistake? Or the statements must be true?

Sorry but the link above will change with the new commits. And the below one is what I'm referring to previously:
https://github.com/magiccodingman/Magic.IndexedDb/blob/b689ce84336cdb13605124fcab8d39319e4aa46b/Magic.IndexedDb/IndexDbManager.cs#L134
When convertedRecord == null or updatedRecord != null, it won't call the js function. And the transaction won't be ended in this case?


Clicking on an ingestion doesn't route you to airflow

Affected module
I think it's Ingestion Framework? @harshach correct me on this if I am wrong
Describe the bug
When you are looking at a service on the "ingestion" tab, and you click the hyperlinked "Name" to view the service in airflow, it should open a new tab in airflow and show you the running service. Instead, it picks up the wrong URL and you get an error page (this site can't be reached)
To Reproduce

Go to a service connection and click on "ingestions"
Click the "name" of the ingestion you want to view in airflow

this opens a new tab
new tab URL is wrong and brings you to an error page

Expected behaviour

when you click on the "name" of the ingestion, it should redirect you to localhost:8080/path/to/airflow and not http://ingestion:8080/path/to/airflow

Version:

OS: any
Python version: any
OpenMetadata version:  10.0
OpenMetadata Ingestion package version: N/A

closing this in favor of https://github.com/open-metadata/OpenMetadata/issues/4776


Using private value to validate public field

Discussed in https://github.com/samuelcolvin/pydantic/discussions/3211

Originally posted by otaviodantas September 14, 2021
How use a private field to validate another field in same model.
Something like that:
class Foo(BaseModel):
    name: str
    _hidden: bool

    class Config:
        underscore_attrs_are_private = True

    @validator("*")
    def testing(cls, name):
        if cls._hidden is False:
            name = "changed"

        return name

obviously this code doesn't work, but i need of something similar, how i do?

bump

This works on both v1 and v2:
from pydantic import BaseModel, root_validator

class Foo(BaseModel):
    name: str
    _hidden: bool

    @root_validator(pre=True)
    def testing(cls, values):
        if values['_hidden'] is False:
            values['name'] = "changed"

        return values

print(Foo(_hidden=False, name="b"))
"""name='changed'"""


Allowed uploading files more than 65536 bytes.

sendWindowSize was never updated with new stream.windowSize value

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.petroakzhygitov seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


addon-knobs: Failed prop type: Invalid prop knob.value of type array supplied to ObjectType, expected object

The documentation for the object knob states:
Allows you to get a JSON object or array from the user.
But I get an error in console that it expects only an object:
Failed prop type: Invalid prop knob.value of type array supplied to ObjectType, expected object
The rendering still works correctly, so am assuming something is wrong in the prop type check
This is with the latest version

If you'd like to open a PR for this, we'd really appreciate it.

Looks like it was fixed a few days ago so should be in the 3.3 release: https://github.com/storybooks/storybook/pull/2227
Apologies, did do a search but didn't find anything originally, will close.

Yeah, that's actually fixed twice =D #1701 #2227
So the fix included in 3.3.0-alpha.3 and will be included in 3.2.15

Glad I didn't fix it a third time! ;-)  Thanks folks!