service entry: warn on ignored targetPort

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
29c51ef5f0225c0451d0c9f7e5d9e4573c165d9c
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
29c51ef5f0225c0451d0c9f7e5d9e4573c165d9c
link
true
/test unit-tests-arm64

unit-tests_istio
29c51ef5f0225c0451d0c9f7e5d9e4573c165d9c
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

remove the hold if it is not used

Its ignored for NONE specifically ,not always


Need to redesign tooltips as it's hard to read them in dark mode

Need to redesign tooltips as it's hard to read them in dark mode. Example:

Figma: https://www.figma.com/file/lwL5jneveZczAj5RLcLFH2/DIAL-Chat?type=design&node-id=3146-7888&mode=design&t=3np28RqfCidGWmaF-0

Tooltip design has been updated successfully.


OBR HL7 Enhancements

Make sure OBR-16 holds the ordering physician information
Make sure OBR-3 holds the filler order number


Don't enable IPv6 forwarding if IPv6 isn't enabled.

Fixes #600

Pull Request Test Coverage Report for Build 571ad3d8d9919b9ee057416041f30b00796998d3-PR-609

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

Totals

Change from base Build 11a2045b18dafad83fdec9b739077935fde5bfe7:
0.0%

Covered Lines:
696

Relevant Lines:
915

💛  - Coveralls


[Question] Anyone know of an EAP library?

Anyone know of an EAP library that can be used with this?

I dont think there should be any problems implementing eap of some sort on top of this but i havent had the need or time. Then there is also tje question of which eap flavor?
Sent from my iPhone

On 9. Apr 2020, at 23.58, Allen Byron Penner<EMAIL_ADDRESS>wrote:

Anyone know of an EAP library that can be used with this?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

by flavor I assume you mean which auth scheme?

Yes exactly
Sent from my iPhone

On 11. Apr 2020, at 2.16, Allen Byron Penner<EMAIL_ADDRESS>wrote:

by flavor I assume you mean which auth scheme?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

I think only a few really would need to be added since most only use a select few like mschapv2, I think md5 is kinda depreciated, etc...

Mschapv2 and eap-tls i guess.
I actually got a bit inspired so if i have the time ill probably add eap message parsing and creation. Then it would also need to handle fragmented packets.
Then it would of course still need to do something sensible with the eap messages
Sent from my iPhone

On 11. Apr 2020, at 21.26, Allen Byron Penner<EMAIL_ADDRESS>wrote:

I think only a few really would need to be added since most only use a select few like mschapv2, I think md5 is kinda depreciated, etc...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Invoke a plugin :-) like everything else does. I have a guy working on adding it but he may have questions so I refereed him to this thread.

Hey @vforteli , I am the guy @ByronAP referring to,  The biggest issue I had came across is failure to parse all attributes by RadiusPacketParser library even though it has the same secret key, and with a bit of research it seems, it's using PEAP and EAP-TLS in top to be able to access the other attributes like User-Password, that is crucial to to implement the Mschapv2 handshake.
How would you advise me to do this in an efficient way with speed in mind?

Thats the thing, if its EAP the interesting attribute is eap-message. There can be several in one packet and then they have to be concatenated and then parsed. This should be doable with the library with a custom packet handler. Also if its EAP it shouldnt have a user-password at all
Sent from my iPhone

On 15. Apr 2020, at 19.14, neals-sudo<EMAIL_ADDRESS>wrote:

Hey @vforteli , I am the guy @ByronAP referring to, The biggest issue I had came across is failure to parse all attributes by RadiusPacketParser library even though it has the same secret key, and with a bit of research it seems, it's using PEAP and EAP-TLS in top to be able to access the other attributes like User-Password, that is crucial to to implement the Mschapv2 handshake.
How would you advise me to do this in an efficient way with speed in mind?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Yeah it's just a lot of reading for us both as we try to figure out the whole flow and back and encryption/decryption properly. It is very cryptic when looking at the actual eap message bytes which I guess is the point and the docs are very scattered and seem to have t o be pieced together to make a working flow from what I have seen.


turn on travis for preformat balance

updates https://github.com/kubernetes/kubernetes/issues/31264
to be merged after https://github.com/kubernetes/kubernetes.github.io/pull/1527
just want to make sure this fails correctly before that PR is merged

This change is

perfect it failed in the way I wanted it to, so it should pass after the other PR is merged \o/

I am back so ping me after you rebase?

@lavalamp rebased, thanks!

Looks like travis is mad about the new entry!

Pingity ping.  What's the plan with this PR?  It's been a while.

whoa sorry will figure it out..

ok updated!

We should probably figure out a way of doing this that doesn't involve downloading the entire k8s repo at some point in the future...

for reals
On Fri, Jan 27, 2017 at 1:58 PM Daniel Smith<EMAIL_ADDRESS>wrote:

We should probably figure out a way of doing this that doesn't involve
downloading the entire k8s repo at some point in the future...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/kubernetes.github.io/pull/1528#issuecomment-275786358,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABYNbGvQphCwubAWLOZBDNfQ0mTM8bngks5rWmiCgaJpZM4KcgyO
.


IKRPG Update

General cleaning; sheet is a direct copy of what I use in my games, and it works.  If something is broken in this one, I will do an line by line search for the issue.

Thanks!


addException

how to  resolve

This is an old version of ButterKnife, but it never generated code like that. I would suggest updating to the latest version and ensuring you have the same version of the runtime as the compiler.


Fix issue 17574 - Avoid range error by checking the result of indexOf

Looks good, but please add a unittest for this.

LGTM, thanks!


 See this comment.
There was a test failure on prop_shrinkTermSound :

unpacking sources
unpacking source archive /nix/store/lkm426ykvh3q7y0iqx9lp1zj6pgvpcsb-plutus-root-plutus-core-test-plutus-ir-test-root
source root is plutus-root-plutus-core-test-plutus-ir-test-root
patching sources
building
plutus-ir
  prettyprinting
    basic:                                              OK
    maybe:                                              OK
  prettyprintingReadable
    basic:                                              OK
    maybe:                                              OK
    letInLet:                                           OK
    letDep:                                             OK
    listMatch:                                          OK
    idleAll:                                            OK
    some:                                               OK
    even3:                                              OK
    stupidZero:                                         OK
    mutuallyRecursiveValues:                            OK
    errorBinding:                                       OK
    some:                                               OK
    stupidZero:                                         OK
    recursiveTypeBind:                                  OK
  parsing
    parser round-trip:                                  OK (0.48s)
        ✓ propRoundTrip passed 100 tests.
    parser ignores whitespace:                          OK (2.21s)
        ✓ propIgnores whitespace passed 100 tests.
    parser ignores comments:                            OK (27.73s)
        ✓ propIgnores comments passed 100 tests.
  lets
    letInLet:                                           OK
    letDep:                                             OK
  datatypes
    maybe:                                              OK
    listMatch:                                          OK
    idleAll:                                            OK
    some:                                               OK
    listMatchEval:                                      OK
    dataEscape:                                         OK
  recursion
    factorial:                                          OK
    even3:                                              OK (0.02s)
    even3Eval:                                          OK (0.03s)
    stupidZero:                                         OK
    mutuallyRecursiveValues:                            OK (0.02s)
    errorBinding:                                       OK
  serialization
    serializeBasic:                                     OK
    serializeMaybePirTerm:                              OK
    serializeEvenOdd:                                   OK
    serializeListMatch:                                 OK
  errors
    mutuallyRecursiveTypes:                             OK
    recursiveTypeBind:                                  OK
  names
    renamer does not destroy scoping:                   OK (0.16s)
        ✓ test_scopingGood passed 100 tests.
    scoping bad
      wrong renaming destroys scoping:                  OK
      no renaming does not result in global uniqueness: OK
      renaming with no marking destroys scoping:        OK
  transform
    thunkRecursions
      listFold:                                         OK
      monoMap:                                          OK
      errorBinding:                                     OK
    nonStrict
      nonStrict1:                                       OK
    letFloat
      letInLet:                                         OK
      listMatch:                                        OK
      maybe:                                            OK
      ifError:                                          OK
      mutuallyRecursiveTypes:                           OK
      mutuallyRecursiveValues:                          OK
      nonrec1:                                          OK
      nonrec2:                                          OK
      nonrec3:                                          OK
      nonrec4:                                          OK
      nonrec6:                                          OK
      nonrec7:                                          OK
      nonrec8:                                          OK
      nonrec9:                                          OK
      rec1:                                             OK
      rec2:                                             OK
      rec3:                                             OK
      rec4:                                             OK
      nonrecToRec:                                      OK
      nonrecToNonrec:                                   OK
      oldLength:                                        OK
      strictValue:                                      OK
      strictNonValue:                                   OK
      strictNonValue2:                                  OK
      strictNonValue3:                                  OK
      strictValueNonValue:                              OK
      strictValueValue:                                 OK
      even3Eval:                                        OK
      strictNonValueDeep:                               OK
      oldFloatBug:                                      OK
      outRhs:                                           OK
      outLam:                                           OK
      inLam:                                            OK
      rhsSqueezeVsNest:                                 OK
    recSplit
      truenonrec:                                       OK
      mutuallyRecursiveTypes:                           OK
      mutuallyRecursiveValues:                          OK
      selfrecursive:                                    OK
      small:                                            OK
      big:                                              OK
    inline
      var:                                              OK
      builtin:                                          OK
      constant:                                         OK
      transitive:                                       OK
      tyvar:                                            OK
      single:                                           OK
      immediateVar:                                     OK
      immediateApp:                                     OK
    beta
      lamapp:                                           OK
      lamapp2:                                          OK
      absapp:                                           OK
      multiapp:                                         OK
      multilet:                                         OK
    unwrapCancel
      unwrapWrap:                                       OK
      wrapUnwrap:                                       OK
    deadCode
      typeLet:                                          OK
      termLet:                                          OK
      strictLet:                                        OK
      nonstrictLet:                                     OK
      datatypeLiveType:                                 OK
      datatypeLiveConstr:                               OK
      datatypeLiveDestr:                                OK
      datatypeDead:                                     OK
      singleBinding:                                    OK
      builtinBinding:                                   OK
      etaBuiltinBinding:                                OK
      nestedBindings:                                   OK
      nestedBindingsIndirect:                           OK
      recBindingSimple:                                 OK
      recBindingComplex:                                OK
      pruneDatatype:                                    OK
    retainedSize
      typeLet:                                          OK
      termLet:                                          OK
      strictLet:                                        OK
      nonstrictLet:                                     OK
      datatypeLiveType:                                 OK
      datatypeLiveConstr:                               OK
      datatypeLiveDestr:                                OK
      datatypeDead:                                     OK
      singleBinding:                                    OK
      builtinBinding:                                   OK
      etaBuiltinBinding:                                OK
      etaBuiltinBindingUsed:                            OK
      nestedBindings:                                   OK
      nestedBindingsIndirect:                           OK
      recBindingSimple:                                 OK
      recBindingComplex:                                OK
    rename
      allShadowedDataNonRec:                            OK
      allShadowedDataRec:                               OK
      paramShadowedDataNonRec:                          OK
      paramShadowedDataRec:                             OK
  types
    letInLet:                                           OK
    listMatch:                                          OK
    maybe:                                              OK
    ifError:                                            OK
    mutuallyRecursiveTypes:                             OK
    mutuallyRecursiveValues:                            OK
    nonrec1:                                            OK
    nonrec2:                                            OK
    nonrec3:                                            OK
    nonrec4:                                            OK
    nonrec6:                                            OK
    nonrec7:                                            OK
    nonrec8:                                            OK
    rec1:                                               OK
    rec2:                                               OK
    rec3:                                               OK
    rec4:                                               OK
    nonrecToRec:                                        OK
    nonrecToNonrec:                                     OK
    oldLength:                                          OK
    strictValue:                                        OK
    strictNonValue:                                     OK
    strictNonValue2:                                    OK
    strictNonValue3:                                    OK
    strictValueNonValue:                                OK
    strictValueValue:                                   OK
    strictNonValueDeep:                                 OK
    even3Eval:                                          OK
    sameNameDifferentEnv:                               OK
    typeLet:                                            OK
    typeLetRec:                                         OK
  type-errors
    wrongDataConstrReturnType:                          OK
    nonSelfRecursive:                                   OK
    typeLet:                                            OK
  generators
    prop_genData:                                       OK (8.23s)
      +++ OK, passed 3000 tests.
    prop_genKindCorrect:                                OK (4.93s)
      +++ OK, passed 100000 tests.
    prop_shrinkTypeSound:                               OK (12.88s)
      +++ OK, passed 30000 tests.
    prop_substType:                                     OK (2.55s)
      +++ OK, passed 10000 tests.
    prop_unify:                                         OK (5.37s)
      +++ OK, passed 10000 tests; 63676 discarded.

      sizes (10000 in total):
      84.72% 1
      11.30% 0
       2.91% 2
       0.98% 3
       0.09% 4
    prop_genTypeCorrect:                                OK (13.63s)
      +++ OK, passed 10000 tests.
    prop_genWellTypedFullyApplied:                      OK (4.87s)
      +++ OK, passed 1000 tests.
    prop_findInstantiation:                             OK (1.52s)
      +++ OK, passed 10000 tests.
    prop_inhabited:                                     OK (6.21s)
      +++ OK, passed 3000 tests.
    prop_stats_numShrink:                               OK (3.81s)
      +++ OK, passed 40 tests.

      distribution | duplicates (40 in total):
      62%          | 0%
      22%          | 5%
      10%          | 10%
       2%          | 15%
       2%          | 20%
    prop_noTermShrinkLoops:                             OK (6.83s)
      +++ OK, passed 40 tests.
    prop_shrinkTermSound:                               FAIL
      *** Failed! Falsified (after 3 tests and 3 shrinks):
      ty,tm = ( integer -> d4_4
      , let data d4_4 | m2_2 where

        in error {integer -> d4_4} )
      [ E019: Error during PIR typechecking:
      Free type variable at  () :  d4
      , E019: Error during PIR typechecking:
      Free type variable at  () :  d4
      , E019: Error during PIR typechecking:
      Free type variable at  () :  d4 ]
      Use --quickcheck-replay=257544 to reproduce.
      Use -p '/prop_shrinkTermSound/' to rerun this test only.

1 out of 184 tests failed (102.05s)

Extricated from https://input-output.atlassian.net/browse/PLT-1333

There was a test failure on prop_shrinkTermSound:

I can no longer reproduce it.
Closing in favor of #6084 6531.


Installation stops after hash file download

Describe the bug:
I cannot install k3s on a ubuntu 21.04 system using the install script.
The installation stops without an error output.
Steps To Reproduce:
Run curl -sfL https://get.k3s.io | INSTALL_K3S_EXEC="--disable=traefik" sh -s -.
Expected behavior:
k3s is installed
Actual behavior:
k3s installation stops after hash download.
Additional context / logs:
curl -sfL https://get.k3s.io | INSTALL_K3S_EXEC="--disable=traefik" sh -s -
[INFO]  Finding release for channel stable
[INFO]  Using v1.25.6+k3s1 as release
[INFO]  Downloading hash https://github.com/k3s-io/k3s/releases/download/v1.25.6+k3s1/sha256sum-amd64.txt

Maybe because of the network, can you debug or give a short point？

What do you mean with short point? I can actually execute the curl command
seperately.
Xinwei Xiong @.***> schrieb am Fr., 3. März 2023, 18:28:

Maybe because of the network, can you debug or give a short point？
—
Reply to this email directly, view it on GitHub
https://github.com/k3s-io/k3s/issues/7020#issuecomment-1453862366, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AJNAQIAHMU6ASV33KEYXQODW2IS27ANCNFSM6AAAAAAVOZYJSQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

is your curl perhaps installed from a snap, instead of as a .deb? I'm not finding an existing issue for it, but I have seen curl fail to download files with a permission denied errors when it is installed from a snap.
You can run curl -sfL https://get.k3s.io/ | INSTALL_K3S_EXEC="--disable=traefik" sh -sx - to see the full curl command that's being run, and try the same manually.

Thank you! The installation of curl was the reason. Strange that it did not output any error.


fix: use for-loops in Pluto persistence methods

Description:
We were seeing a problem with @pluto-encrypted/leveldb where 2 did-key links were persisted, but on recall we were only getting one back. We traced this down to a race-condition in the index updating, and so to Promise.all which calls in quick succession 2 updates to Pluto.Store index, so that one immediately overwrites the other.
Alternatives Considered (optional):
What's needed is some sort of "lock" on the updating of indexes. We considered 2 options:

modify @pluto-encrypted/leveldb to add a "queue" to the update index call so that it's safe to hammer it
modify the Pluto.Store code to run more in series with it's writes

We opted for (2) because:

the write times involved are imperceptible to humans
we want to avoid other developers falling in this exact same hole when they implement their own store

there needs to be a queue somewhere in the stack, may as well put it here so it doesn't need to be re-implemented multiple times

Checklist:

[x] My PR follows the contribution guidelines of this project
[x] My PR is free of third-party dependencies that don't comply with the Allowlist
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have checked the PR title to follow the conventional commit specification

cc @elribonazo WE FOUND THE BUG!!!
so excited

I think when @pluto-encrypted/database was merged into the SDK that the for-loop was replaced with a Promise.all (I suspect this because our tests were formerly passing).
To that end it *may* be wise to add comments next to these for-loops saying "DO NOT PROMISE.ALL THIS".
I'll leave that up to the Identus team to decide.

Very nice! Awesome work!

@elribonazo built this - https://github.com/atala-community-projects/pluto-encrypted/tree/master/packages/test-suite
We could extend that to test. I think it would be a really strategic collaboration - anyone wanting to build their own storage would be well supported by that.
FWIW we have tests in https://gitlab.com/matou-collective/lib/atala-prism/ssb-atala-prism which surfaced these problems

@elribonazo @curtis-h this is approved, but says it needs approval from a maintainer?
What's the next step here in your process? I'm not sure if I'm supposed to be following up

Pull Request Test Coverage Report for Build<PHONE_NUMBER>7
Details

8 of 8 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.005%) to 71.504%

Totals

Change from base Build<PHONE_NUMBER>7:
0.005%

Covered Lines:
2720

Relevant Lines:
3614

💛  - Coveralls


Added basic error handler to Tw2TextureRes

Errors now caught on Tw2TextureRes
The resources _isLoading variable is correctly updated
The onLoadFinished callback is called if it exists
Error message emitted/ logged

Moved changes to https://github.com/ccpgames/ccpwgl/pull/236


feat: port Analysis.LocallyConvex.BalancedCoreHull

Slightly rewrote the one proof to avoid convert and renamed two lemmas, so that their names fit better with the naming convention.

bors r+


Adding as a node package

I've been working on a fork to wrap this in javascript to make it into an NPM package (https://github.com/Kotarski/ipa-dict).
Is this something that could be pulled or should I keep it as a fork?
Are you happy for me to submit this to NPM as ipa-dict?
Thanks,

Hi @Kotarski thanks for working on this! Sounds like a great idea to have this available on NPM. The only thing would be keeping it up to date -- there are quite a few issues with some of the experimental data (e.g., in nb, yue, zh) that will be corrected in upcoming commits. Would it be fairly easy to pull those in (perhaps automatically?) when the repo updates?

@dohliam
It should be just a case of pulling the new version as it's just a repo inside. Not sure how I'd go about doing it automatically at the moment but can look into it... maybe the new git workflow stuff will help. Still a bit of work to be done, but I'll continue once I'm back from holiday!

I've finally got around to actually doing this over the holidays (https://www.npmjs.com/package/ipa-dict). I've set it up so everything is generated from the data files, so just a pull and republish will update it.
Should we pull the fork back into the main repo, or leave it separate? One benefit of merging it back in is that it could automatically publish when the data changes, but I don't mind.

I've finally got around to actually doing this over the holidays (https://www.npmjs.com/package/ipa-dict). I've set it up so everything is generated from the data files, so just a pull and republish will update it.
Should we pull the fork back into the main repo, or leave it separate? One benefit of merging it back in is that it could automatically publish when the data changes, but I don't mind.


Taghelper - Images serialize to base64 encoding directly into html

I want to be able to serialize images directly to web page .
One possible use : send the file over email ( or directly as html) and not have the issue to download images from a webserver.
For this we can use  https://en.wikipedia.org/wiki/Data_URI_scheme - base 64 encoding of images.
My proposal is a tag helper asp-append-base64
e.g.
<img src="~/images/red.png" alt="Red versioned" title="Red versioned" asp-append-base64="true" />
I will submit a pull request for this ASAP.

Hi @ignatandrei thank you for logging the suggestion and sending the PR. This doesn't currently align with our release plans, so we are putting this issue in the backlog and closing the PR.
If you end up releasing the tag helper as your own package on NuGet.org, we'd be happy to add a link to it from the readme of this repo.

Thank you for the comment , @Eilon
I have created NuGet for .NET Framework 4x , but not for .NET core.
Do you have any recommended way to create this kind of packages for .NET Core?  ( a blog post link / an msdn link?)

@ignatandrei it's actually quite easy! In fact, it's hard not to make a package when working with .NET Core because every project by default creates a NuGet package!

@ignatandrei to produce a NuGet package from your project, go to the command line, navigate to the folder of the project, and type dotnet pack -c Release. This will generate a "release" build of your NuGet package (and it will tell you where on disk the package was created).

Nice. Thank you. I will put sources on github and I will update the thread.

https://www.nuget.org/packages/AspNetCore.Mvc.ImageBase64 and source at https://github.com/ignatandrei/AspNetCoreImageTagHelper
And yes, I like that my little extensions to be added in the readme of this repo ;-)

@ignatandrei I added a link, check it out. Thanks!

Thank you!

This is gold. This should be included into the framework IMHO.


RigidBody created by script cannot be selected in editor

Godot version:
4.0 and 3.2.3
OS/device including version:
Windows 10
Issue description:
The RigidBody created by the script in the "tool" mode cannot be selected in the editor.
Steps to reproduce:
Add a RigidBody3d with script to the scene and try to select it in the viewport. Script for object creation:
@tool
extends RigidBody3D

var _collision : CollisionShape3D
var _mesh : MeshInstance3D

func _init():
	_collision = CollisionShape3D.new()
	_collision.shape = SphereShape3D.new()
	self.add_child(_collision)

	_mesh = MeshInstance3D.new()
	_mesh.mesh = SphereMesh.new()
	self.add_child(_mesh)

	return

Minimal reproduction project:

Test-RigidBody.zip

I can confirm this on commit https://github.com/godotengine/godot/commit/32b31a5fa47b1e068be98f3196cf5d83a2260667 (Linux).
That said, it's probably "intended" in the sense that RigidBody has no visual representation. Only the MeshInstance can be selected by clicking in the editor, and it's being added in a tool script here.

That said, it's probably "intended" in the sense that RigidBody has no visual representation. Only the MeshInstance3D or the CollisionShape3D can be selected by clicking in the editor, and it's being added in a tool script here. Therefore, there would be no way to display its details in the Inspector dock since it's not present in the Scene tree dock in the first place.

If this is intentional, then why does it work with RigidBody2D?

@TvoyBatek The selection code in the 2D and 3D editor is entirely different. In general, the one in the 3D editor tends to be much less reliable (I don't know why).

I agree with @TvoyBatek that this is a bug.


Fixes #16

Coverage remained the same at 99.114% when pulling da60bf516a3533853000555800580d6aa9c1938d on no-consumption-after-expiry into a29d7b88c222410e12947feb68c74b454e47397b on master.

Coverage remained the same at 99.114% when pulling da60bf516a3533853000555800580d6aa9c1938d on no-consumption-after-expiry into a29d7b88c222410e12947feb68c74b454e47397b on master.


Cannot update a field to be required once already created

I have a model with a simple field I created. In the next migration I wanted to make this field required, however the update was being rejected, even though I was passing a migration value.
When testing I noticed that I had to delete every entry and then I could update the field to be required.
In the UI this isn't an issue as it asks for a migration value. I assume there is some sort of ordering of mutations issue meaning that the migration is rejected?
e.g
model.addSimpleField({
  apiId: 'label',
  displayName: 'Label',
  type: FieldType.String,
  isLocalized: true
});

on next run when content has been added (this fails)
model.updateSimpleField({
  apiId: 'label',
  migrationValue: 'test',
  isRequired: true
});

Internal Issue: ENG-3642

Just wanted to drop a word here saying this is still relevant today.
The migration gets rejected with 'FAILED Could not apply schema changes'

@notrab - was there any movement on this one? Could it be solved by your draft PR https://github.com/GraphCMS/management-sdk/pull/20 ?

@joelpierre this should be resolved now, right?

@joelpierre this should be resolved now, right?

I am not sure haven't re-checked since Jan. I just generally avoid it 😅

Hello any update on this issue?
I am having similar issue, trying to do upsert to a model based on the apiId


Fixed errors in example.c

The example.c file did not compile because it had various errors in it. This patch fixes those.
(Let me know if you want me to stop sending you bug reports and pull requests. I've just been looking through SuperNOVAS which helped me understand a few concepts in NOVAS itself which I previously didn't quite get...)

Thanks,
It's much appreciated. I admit, I did not really care much about the examples, beyond some perfunctory updates from its original  NOVAS C version to use the new constants and enums. And, so I never even bothered to check if it compiled. :-D
Good work!

I took a closer look at the example again, and made some further fixes:

Changed T0 from novascon.h to NOVAS_JD_J2000 in novas.h, and removed the include for novascon.h from preamble. We want to wean off the ill-designed novascon.h / .c, so we don't want to espouse it.
jd_tt was left undefined (my bad) when I ported the example from NOVAS C 3.1. Now it is what it was in the original.
Added workflow to check the warning-free compilation of the example.

These changes have been committed to the v1.0.1 branch.


fix: grpc dependency path resolution

Summary:
fixes #1686
Fixing the path resolution for imported files in the proto file
Build & Testing:

[ ] I ran cargo test successfully.
[ ] I have run ./lint.sh --mode=fix to fix all linting issues raised by ./lint.sh --mode=check.

Checklist:

[ ] I have added relevant unit & integration tests.
[ ] I have updated the documentation accordingly.
[ ] I have performed a self-review of my code.
[ ] PR follows the naming convention of <type>(<optional scope>): <title>

fixed in #1705


Add TargetFrameworks netstandard2.1 or net6.0 for Tingle.AspNetCore.DataProtection.MongoDB

Hi,
would it be possible to add the TargetFrameworks netstandard2.1 or net6.0 to the Tingle.AspNetCore.DataProtection.MongoDB project? The project Tingle.Extensions.Caching.MongoDB for example does support it. And i dont see any obvious code the wouldnt compile. This would help to use this project in a net6 environment.
Regards
Thomas

This sounds like a reasonable request. We shall add net6 to the list

You can also do a PR that overrides the value in the specific project.
See #144


Remove defunct manner of creating a BSK python module

Review: By commit
Merge strategy: Merge (no squash)

Description
A year ago an elegant new method was introduced to create python BSK modules.
The depreciated manner of creating python modules is now being removed.
Verification
Did a clean build and all tests passed.
Documentation
Did a clean build of documentation and no warnings or errors appeared.
Future work
none

Thanks for the help @juan-g-bonilla getting this depreciation system setup.  Seems to be working well for python and C++ code.

Could this be looked into? https://github.com/AVSLab/basilisk/issues/658
The older python module gave out python error messages, the new one gives out a generic SWIG error.


Make Package "..." is already installed handling more robust

DNF5 sometimes prints Package "..." is already installed. in the middle of the list of packages to be installed.  This is possibly a race condition in dnf5 itself that should be fixed, but in the meantime, this should handle the cases that have been seen so far.
Also, allow testing against an arbitrary root.log provided on the command line.
Currently available test cases:
https://kojipkgs.fedoraproject.org//packages/ipa/4.12.1/1.eln142.1/data/logs/s390x/root.log
https://kojipkgs.fedoraproject.org//packages/acl/2.3.2/2.eln142/data/logs/ppc64le/root.log
https://kojipkgs.fedoraproject.org//packages/flatpak-builder/1.4.4/2.eln142/data/logs/s390x/root.log
https://kojipkgs.fedoraproject.org//packages/ktls-utils/0.11/2.eln142/data/logs/ppc64le/root.log
https://kojipkgs.fedoraproject.org//packages/subscription-manager/1.29.41/1.eln142/data/logs/s390x/root.log
https://kojipkgs.fedoraproject.org//packages/time/1.9/24.eln142/data/logs/x86_64/root.log

Also filed https://github.com/rpm-software-management/dnf5/issues/1636 but we can't wait for that to be fixed.

LGTM


[Draft] Widgets for itless environment

Within the itless environment, not all services are available so not all widgets should be available by default for the customers in that environment. This is meant to resolve that using a feature flag that will be checked to ensure that if a customer is in an itless env, they'll get only a subset of the available widgets.
Working on this a bit with @florkbr.

@SteveHNH when do you need this? We will soon be using actual CRDs to specify widgets and the widgets should be defined by the available frontends. Just to avoid adding "technical debt" to the repository if we can.

@Hyperkid123 oh that sounds great. I didn't know that was on the roadmap. I have tickets for getting widgets in the itless environment so I'm just trying to get those done. The main part of it is that the we need to make sure we only allow widgets that are useful in that environment, so as long as the CRD approach will allow us to do that, I think that should be fine.
Any ETA on that feature?

ETA is Q4.
But considering there will also be some transition and onboarding from the app side, its like that thing swill be ready in Q1. So I think you should not wait.

Okay, that's good to know. I appreciate your willingness to help us get this working in the FR environment, but I'm bummed it adds technical debt. I'll continue working with @florkbr on it and try to make it as clean as possible so it's easy to remove when the time comes.

Oh, this was a technical debt from the start. We knew we would replace it eventually. But the changes we are working are not trivial. Don't worry about it.

I reworked the widget filtering. The only thing that bothers me is the looping through widgets to see which ones to turn on/off. There might be a smarter way to go after this. I feel like this could introduce a little lag by needing to reach out to unleash for each one.
The other downside I can see is that if for some reason Unleash is unavailable when a user hits the service, the chrome-service.filterWidgets.enable flag could get set to false which would throw all the default widgets at them by default. According to Bryan, this would load some stuff into the DB that we don't want and make it difficult to reset things. But that was going to be a problem anyway, even with the first attempt I made at setting this up.
I'm open to ideas on how we might resolve that if there are any. Maybe invert that filterWidgets check? The worst case would be a commercial customer would see a limited set of widgets until Unleash came back.

@Hyperkid123 I went ahead and figured out how to un-invert that logic so that it reads a little more clearly. Added a comment as well.

/retest


CSS rule typo: word-wrap

The body element has the rules
word-wrap: break-word;
overflow-wrap: break-word;

https://github.com/janraasch/hugo-bearblog/blob/2fa45b92a24e76a610f86f1e039225be5d8cb695/layouts/partials/style.html#L9
However, there is no such rule as word-wrap. The correct rule name is word-break.
I did not submit a PR because I am not sure what the intended goal is. MDN says the break-word value for word-break is deprecated and

Has the same effect as word-break: normal and overflow-wrap: anywhere, regardless of the actual value of the overflow-wrap property.

Hi @ilmari-lauhakangas, nice catch ⚾ 👍.

I did not submit a PR because I am not sure what the intended goal is.

I am not sure either 😅. This whole repo is a blatant 😛 copy & paste from the original bearblog, see
https://github.com/HermanMartinus/bearblog/blob/2ee04f04efa172fd32b63d0480692f405106b943/templates/styles/main.css
You could check in with @HermanMartinus - the man behind this wonderful idea. I am sure he will appreciate your input.

Thanks, I copied the issue over to bearblog.

Thanks, then we'll follow along over there https://github.com/HermanMartinus/bearblog/issues/115.

Ok now I see from the notes in https://caniuse.com/wordwrap that overflow-wrap used to be called word-wrap in ancient times and IE11 only supports word-wrap. I was thrown off by Firefox reporting it as an invalid name.


Runner

This modifies the narps_open.runner module in order to allow pipelines to run partially. I.e.: either the first level (preprocessing, run level, and subject level) or the group level only.
It remains possible to run the pipelines completely.
This feature is documented (docs/runner.md) and tested (tests/test_runner.py).

Excellent, this is something we really needed! Thanks @bclenet


RocketPants + Rollbar

Hi, can someone add support for Rollbar?
Thanks!

@MatayoshiMariano you can for sure! What kind of support do you mean, there's nothing needed AFAIK?


Auto generate password in Paralus init script

What does this PR change?

as part of #92 issue

Does the PR depend on any other PRs or Issues? If yes, please list them.

#102

Checklist
I confirm, that I have...

[ ] Read and followed the contributing guide in CONTRIBUTING.md
[ ] Added tests for this PR
[ ] Formatted the code using go fmt (if applicable)
[ ] Updated documentation on the Paralus docs site (if applicable)
[ ] Updated CHANGELOG.md

Moved commits to https://github.com/paralus/paralus/pull/124


"ADA Accessible" appears to have replaced the Add to Calendar button

Possible to move ADA to center and keep Calendar?

spacing issue:

I'll look into


[Bug] Completion does not work for markdown files inside folder

reference: #24
Without folder (both current file and file cta.md in root folder of workspace),

With folder  (both current file and file cta.md in pages subfolder of workspace),

LspInfo
 Detected filetype:   markdown

2 client(s) attached to this buffer:

 Client: markdown_oxide (id: 3, bufnr: [2])
 	filetypes:       markdown
 	autostart:       true
 	root directory:  /Users/rayx/obsidian
 	cmd:             /Users/rayx/bin/markdown-oxide

Hey!
The completions were set up to be the path relative to the folder. There have been several issues opened about this, so I changed the default here b60fc9e. Markdown links have been set up for the filenames for a while, but as of that commit, wikilink completions will be set up that way as well.


Unnecessary markup in ddoc's html generation

Charles Smith reported this on 2015-12-23T02:07:29Z
Transferred from https://issues.dlang.org/show_bug.cgi?id=15470
CC List

Andrei Alexandrescu (@andralex)
Adam D. Ruppe

Description
This issue expands on Issue #14473, https://issues.dlang.org/show_bug.cgi?id=14473.

I've gone through and highlighted some issues with the generated markup.

Example source:

* view-source:http://dlang.org/spec/property.html

I went ahead and ran this page through an HTML validator(https://validator.w3.org/nu/?doc=http%3A%2F%2Fdlang.org%2Fspec%2Fproperty.html), and here's a brief summary:

* links need to be striped for anchor tags.
* center is obsolete, use CSS
* nesting code in an order list generates invalid html

Additional notes that pass the validator:

* Usage of the  tag instead of . This breaks the semantic layer html is supposed to provide. See http://www.w3.org/International/questions/qa-b-and-i-tags.
* Loading a stylesheet in the body, all stylesheets using rel should be in the head. http://www.w3.org/html/wg/drafts/html/master/single-page.html#the-link-element:attr-link-rel-4
* Unnecessary span tags. Example: `<td><span class="d_inlinecode donthyphenate notranslate">float.nan</span></td>` could be reduced to `<td class="d_inlinecode donthyphenate notranslate">float.nan</td>`
* Tons of unnecessary whitespace, and at the same time, insufficient whitespace for this to be readily editable after html generation.

Overall, all of these things can account for slower page loads, which can impact page ranking in search engines.

destructionator commented on 2015-12-23T03:51:37Z
Ah, yes indeed, though the whitespace is prolly generated accidentally by some macro which can't generically strip :(

csmith.ku2013 commented on 2015-12-23T04:08:34Z
(In reply to Adam D. Ruppe from comment #3)
> Ah, yes indeed, though the whitespace is prolly generated accidentally by
> some macro which can't generically strip :(

That's what I was afraid of, and is pretty unfortunate. This actually violates the standard, so there's nothing requiring the browsers to actually support what we're trying to do, and they could change at any time (not necessarily they will ever though).

csmith.ku2013 commented on 2015-12-23T03:41:47Z
(In reply to Adam D. Ruppe from comment #1)
> What do you mean by "links need to be striped for anchor tags." ?

Poor phrasing, my mistake. I'm referring to the white space in the href. E.g anchor tag on that page:

Introduction

I think this should be something as simple as adding std.string.stripLeft to, but I haven't investigated every occurrence.

destructionator commented on 2015-12-23T15:26:46Z
Indeed, the load time of these things is probably irrelevant. Minification efforts, in general, are almost plain negligible after gzipping.

gzip though, does make a huge difference and we should ensure it is enabled.

destructionator commented on 2015-12-23T02:10:37Z
What do you mean by "links need to be striped for anchor tags." ?

andrei (@andralex) commented on 2015-12-23T15:39:53Z
I recall Jan has enabled compression a while ago. How do we check?

csmith.ku2013 commented on 2015-12-23T16:27:04Z
(In reply to Andrei Alexandrescu from comment #5)
> We can do some of these with relative ease bot some others are likely to be
> difficult. In particular,
>
>  notranslate">float.nan
>
> is an artifact of how generation occurs, first the code font is expanded
> then the table tag is expanded. Merging those two is nontrivial with what we
> have.

This is what I figured, I figured I'd point it out just the same. Unfortunately these kind of things can make designing new templates a bit chaotic, since you end up with oddball things like:

div#search-box, span#search-query, span#search-dropdown, span#search-submit
{
    border: 0.1em none #aaa;
}

I should've explicitly listed this as a concern.

> All of these issues in aggregate, including whitespace, would add to some
> inefficiency. I think it may be unmeasurable or difficult to measure, and at
> best add only to a couple percent. Certainly at this point "all of these
> things can account for slower page loads, which can impact page ranking in
> search engines" is pure speculation.

Fair enough, it was a weak argument, and as Adam pointed out, gzipping makes this not even that. The only concern I was thinking of when pointing this out was more for search engine page ranking, which favors compact compressed sites, but I have no idea to what degree.

Nonconforming and deprecated html however is also present, and that is perhaps a larger issue. I don't suspect browsers to just stop what they're doing already that fixes the mistakes, so it might just be good to know for the future.

andrei (@andralex) commented on 2015-12-23T15:25:01Z
We can do some of these with relative ease bot some others are likely to be difficult. In particular,

float.nan

is an artifact of how generation occurs, first the code font is expanded then the table tag is expanded. Merging those two is nontrivial with what we have.

I'll add that we generate a few tags that are in fact optional, see the list at http://www.w3.org/TR/2011/WD-html5-20110525/syntax.html#optional-tags.

All of these issues in aggregate, including whitespace, would add to some inefficiency. I think it may be unmeasurable or difficult to measure, and at best add only to a couple percent. Certainly at this point "all of these things can account for slower page loads, which can impact page ranking in search engines" is pure speculation.

Do we want nice tight generated HTML? Somewhat. Does fixing this issue help? Yes. Do we want fast-loading pages? Yes. Does fixing this issue help? Unlikely to make any sensible improvement.

destructionator commented on 2015-12-23T15:43:33Z
Just load it with an empty cache with network console open.

Yes, the homepage is gzipped. It comes in at about 8 KB on the wire, not bad at all.

dfj1esp02 commented on 2015-12-23T16:44:43Z
(In reply to Charles Smith from comment #0)
> * Unnecessary span tags. Example: ` donthyphenate notranslate">float.nan	` could be reduced to ` class="d_inlinecode donthyphenate notranslate">float.nan	`

Not equivalent if you want the span to have a border.


Another prep work to enable partitionining

Add update_partition_context() function.

Add partition_context_lookup[] and subsize_lookup[] tables.

Add mi_size_wide[] and mi_size_high[] tables.

Fix outdated lookup tables, for ex: all 2x2, 4x2, 2x4 are dropped.

Use BLOCK_SIZES_ALL whenever possible for the size of lookup table.

As a separate commit for submodule libaom,
manually update the corresponding lookup tables, esp. all the tables with the size
BLOCK_SIZES_ALL.

Does this need the libaom patches?


custom vision

[Enter feedback here]

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

ID: 97b63c98-e3f6-6ccc-e6db-0422a96a8042
Version Independent ID: 06e0e981-d666-2fab-a44f-66622a16c144
Content: Image categorization - Computer Vision - Azure Cognitive Services
Content Source: articles/cognitive-services/Computer-vision/concept-categorizing-images.md
Service: cognitive-services
Sub-service: computer-vision
GitHub Login: @PatrickFarley
Microsoft Alias: pafarley

@xppolo Can you please elaborate or explain what your feedback is regarding?

@xppolo Can you please elaborate or explain what your feedback is regarding?

@xppolo We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Upgrade golangci-lint

Signed-off-by: Tetiana Kravchenko<EMAIL_ADDRESS>What does this PR do?
Upgrade version of golangci-lint.
Why is it important?
When running locally mage lllc with older version I am getting error:
 beats % mage llc
panic: load embedded ruleguard rules: rules/rules.go:13: can't load fmt

goroutine 1 [running]:
github.com/go-critic/go-critic/checkers.init.22()
	github.com/go-critic/go-critic@v0.6.3/checkers/embedded_rules.go:47 +0x4b4
Error: running "build/v1.47.2/golangci-lint run --new-from-rev=origin/main --whole-files -c .golangci.yml ./..." failed with exit code 2

 beats % mage llc
golangci/golangci-lint info checking GitHub for tag 'v1.50.1'
golangci/golangci-lint info found version: 1.50.1 for v1.50.1/darwin/amd64
golangci/golangci-lint info installed build/v1.50.1/golangci-lint
WARN [runner] The linter 'varcheck' is deprecated (since v1.49.0) due to: The owner seems to have abandoned the linter.  Replaced by unused.
WARN [runner] The linter 'structcheck' is deprecated (since v1.49.0) due to: The owner seems to have abandoned the linter.  Replaced by unused.
WARN [linters_context] structcheck is disabled because of generics. You can track the evolution of the generics support by following the https://github.com/golangci/golangci-lint/issues/2649.
WARN [linters_context] wastedassign is disabled because of generics. You can track the evolution of the generics support by following the https://github.com/golangci/golangci-lint/issues/2649.

Checklist

[ ] My code follows the style guidelines of this project
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added an entry in CHANGELOG.md

Author's Checklist

[ ]

Related issues

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-11-25T18:20:35.842+0000

Duration: 9 min 25 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
723

Skipped
5

Total
728

:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.


Added option to not to create empty archive

Some days ago I created this issue: https://github.com/gruntjs/grunt-contrib-compress/issues/185
I realized, that compress task from grunt-contrib-compress npm module will create empty zip file if files, which are specified at files option are not exists.
I created this pull request. I added option, which will add this missing (as I think) feature.
I have 2 questions also:

Do you think this name of option is good? Or should I rename it to some another name?
About tests. Do you think I created correct tests for the changes?

Please, correct my PR or add some comments so I can correct the code or PR.

I got "AppVeyor build failed" message. As I see in log this happened because system couldn't connect to GitHub on 443 port. Looks like I have to rerun this build. I can't find how I can do this.

Hm, I updated 1 message and did one more commit. Now everything is good with AppVeyor.

How about naming the option createEmptyArchive? It's shorter.

I was thinking about this option is too long, but didn't know how I can change it.  So yes it is possible to change the name and invert it value. I think your name is better (it is understandable and a bit shorter).

Yeah, please do so.

I renamed option to "createEmptyArchive"

I also fixed trailing spaces issue

Why check about CLA is not completed? I signed it about ~10 minutes ago?

Because you keep committing with various git accounts.

Hm. I have problems.

I connected most of my commits to my github account, but I can't do this for 6: these comits was done with email<EMAIL_ADDRESS>This is not my email. It is my mistake. I can't link it with my github account
Anyway I have this message:
0 out of 3 committers have signed the CLA.
:x: Alina.Zaytseva
:x: Vladislav.Sharikov
:x: Sharikov Vladislav

I can't sign CLA with others emails except<EMAIL_ADDRESS>(it is already signed).
What should I do know? Should I create new PR and commit only with correct email in my local github settings?
PS Yes I am committing from different places: my different home pc`s and work pc.

Look I am trying this to replace commit author. Looks like it can help: http://stackoverflow.com/a/28845565/2898694
Also why CLA for<EMAIL_ADDRESS>is not signed?

OK. It is going to good. I will finish this in a few minutes.

Ok I changed all authors (it was me, but I set up correct email): https://github.com/sharikovvladislav/grunt-contrib-compress/commits/master
Now is everything alright, correct?

I made some changes according to this https://github.com/gruntjs/grunt-contrib-compress/pull/186#pullrequestreview-6430123 review.

Looks goods but 2 final thoughts:

NotExisting ->NotExistent
Do not modify README.md; instead modify the needed file in docs

Done
Done

@vladikoff: what do you think about this?

What is the usecase? We distribute our product as zips. So our ci makes some zip files. We also store units test results and other statistics . We put it in zip files too . We have npm package that build sources in the repos. Each subsystem has this package in dependencies . This tool uses grunt-contrib-compress to compress files . Some subsystems does not have units . In that case empty zip is created . So this new option will allow everybody to not get empty archive if they don't want to .

Something seems weird. With this patch merged, running grunt in this repo doesn't run the contrib tasks but only runs the test target.

Nvm, it's not this patch to blame.

Yes, I just had checked changes again. There is nothing (seems to me) that can affect contrib tasks.


Dr 1 testing 1

DR-1 Pull request

@Rajmate16 Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.


Bugfix/161 correct temporary dataset path

Now the data.zip is downloaded to the correct path.
This fixes the issue: Incorrect temporary folder for the cats-vs-dogs dataset LINK
fixes #161

Hi @zaleslaw! Did you have a chance to take a look at it?

Fixed in #235


Add WP_DEBUG_LOG

See: https://github.com/roots/trellis/pull/1160

Is app/uploads the only guaranteed writeable place?

I believe so.
Updated default to $webroot_dir . Config::get('CONTENT_DIR') . '/uploads/debug.log'.

Thank you both.
Sorry my brain not functioning yesterday.


Align repo names with the official names

Follow up to https://github.com/ManageIQ/manageiq-appliance/pull/293
@simaishi Please review.

Only one I'm not sure about is google-cloud-compute...do you know what's in the .repo file for that one?

Only one I'm not sure about is google-cloud-compute...do you know what's in the .repo file for that one?

We specify the repo name for post installation (as we have to manually create the repo file): https://github.com/ManageIQ/manageiq-appliance-build/blob/master/kickstarts/partials/post/repos.ks.erb

Looks good, just need change for gce (google-compute-engine vs google-cloud-compute)

@simaishi Updated.

Jansa backport details:
$ git log -1
commit 36770d83dd0db8eb1eb4fb44f863848851449c95
Author: Satoe Imaishi<EMAIL_ADDRESS>Date:   Wed Sep 16 11:12:24 2020 -0400

    Merge pull request #439 from Fryguy/align_names

    Align repo names with the official names

    (cherry picked from commit bec064ece6146a9877bfb91c609609a741836419)


CookieStorer, SessionStorer invalid types for CookieState, SessionState

Hey there, my code is failing when I use the pattern provided in https://github.com/volatiletech/authboss-sample/blob/master/blog.go#L66. Here's what my code looks like:
import (
	"github.com/volatiletech/authboss"
	abclientstate "github.com/volatiletech/authboss-clientstate"

)

var sessionStore abclientstate.SessionStorer
var cookieStore abclientstate.CookieStorer

authBoss.Config.Storage.CookieState = cookieStore
authBoss.Config.Storage.SessionState = sessionStore

This is the error:
./main.go:91:38: cannot use cookieStore (type abclientstate.CookieStorer) as type "github.com/drshrey/scobophile/scobophile-go-api/vendor/github.com/volatiletech/authboss".ClientStateReadWriter in assignment:
        abclientstate.CookieStorer does not implement "github.com/drshrey/scobophile/scobophile-go-api/vendor/github.com/volatiletech/authboss".ClientStateReadWriter (wrong type for ReadState method)
                have ReadState(*http.Request) ("github.com/volatiletech/authboss".ClientState, error)
                want ReadState(*http.Request) ("github.com/drshrey/scobophile/scobophile-go-api/vendor/github.com/volatiletech/authboss".ClientState, error)
./main.go:92:39: cannot use sessionStore (type abclientstate.SessionStorer) as type "github.com/drshrey/scobophile/scobophile-go-api/vendor/github.com/volatiletech/authboss".ClientStateReadWriter in assignment:
        abclientstate.SessionStorer does not implement "github.com/drshrey/scobophile/scobophile-go-api/vendor/github.com/volatiletech/authboss".ClientStateReadWriter (wrong type for ReadState method)
                have ReadState(*http.Request) ("github.com/volatiletech/authboss".ClientState, error)
                want ReadState(*http.Request) ("github.com/drshrey/scobophile/scobophile-go-api/vendor/github.com/volatiletech/authboss".ClientState, error)

Versions of both packages:
[[constraint]]
  name = "github.com/volatiletech/authboss"
  version = "2.3.0"

[[constraint]]
  branch = "master"
  name = "github.com/volatiletech/authboss-clientstate"

Any reason why the types don't match? I checked out the definitions and they do seem to implement the ClientStateReadWriter interface, so help here would be much appreciated!

Nevermind, I was able to fix it by doing dep ensure -add github.com/volatiletech/authboss-clientstate. Before, it was including the the clientstate lib from my /go/src/... path. Not sure why a go get -u on the package would be different from dep ensure, but that seems to have fixed it. Closing this!


Brute Force linear explainer implementation

Hello.
In order to get an indication of how well the sampling approximation works as a function of nsamples in the LinearExplainer, I decided to calculate the pure shapley values using a brute force approach. I noticed a ToDo comment proposing exactly this approach for the case where nsamples is actually larger than the number of possible coalitions and would therefore be happy to submit a PR once its done.
However I have had some trouble understanding the _estimate_transforms method. Issue #573 seems to ask a similar question but is as of now unaddressed. I could submit a [WIP] PR to initiate some discussion but it would also be really helpful to get a reference for that method (be it a paper or an informal write-up). I did check several related papers including the NIPS one but there is nothing about linear models that consider correlation of input features. For example section 4.2 of the linked paper only considers the independent case.
@slundberg since you are the author of the function is question (as well as the paper) maybe you could shed some light into this? Thanks in advance!
EDIT: Potential Issue in the existing estimation
By going through the existing estimation code I observed that smaller coalitions have a greater effect on the estimation than larger ones. Please correct me if I am wrong but here is the reasoning:
Each of nsamples iterations will start with a coalition of size 1, then build up towards bigger ones. So there is an equal additive effect on the estimation coming from coalitions of size 1, as from coalitions of arbitrary size s >> 1. However this is not true for the number of unique coalitions. For example, if we have 10 features, then there are 10 coalitions of size 1 but 252 coalitions of size 5. Therefore those coalitions of size 5 have individually a much smaller effect on the estimation than the coalitions of size 1 (some of them might never be explored when nsamples is small). This discrepancy will of course get much larger when M increases arbitrarily.
This could be a desired effect if we consider very small and very large coalitions more important (I have some intuition that supports this but can't quite formulate it yet). Since we currently lack documentation I am not sure that this is a feature and not a bug.

See link in this issue:
https://github.com/slundberg/shap/issues/952


Can not change name

I always spawn as "NotReallyABot" On first load I get no chance to change it because it jumps into the game instantly.
I was told to press esc and change it there. I did it,upon respawn I still have the default name.

press esc change name press play as guest

I am logged in with FB, and I want to keep it that way.

then press the fb button instead of the guest one

so log out and back in? I only got one play button, but it doesnt change the name like I said.

Hmm so the issue is the fb play button does not work when changing names?


bug catalog uncommitted test timeout

PR used to run the pipeline and debug test

@N-o-Z still relevant? can close?


[Documentation] Provide a guide for ruby users, aka a ruby-to-crystal guide, ideally linked in via: https://crystal-lang.org/docs/

I would like to propose to providing a guide that focuses on ruby users who know ruby very well already.
Something that makes it possible to understand the DIFFERENCES in crystal.
In theory people can read the documentation and learn on their own, but some users are very very
lazy. I am one of those!
For those lazy users, a succinct how-to-guide would be super useful. It does not have to be super-long,
by the way; just a medium sized article that focuses on the most important differences, and specifically
has "expert ruby users" as main target audience. This should be a collaborative guide that can be
easily extended by different crystal users, but please not the github wiki - the github wiki is, unfortunately,
really really bad. (Github issues on the other hand are super-useful.)
PS: For the length, I recommend a "normal" sized article on medium.com. While I hate medium, the
SIZE of the articles there is quite ok, so the aim of this proposal is to aim for a similarly sized, but still
succinct, article in this regard as well.

Wasn't there something already done...I think..maybe @sdogruyol did it? Crystal for Rubiests...or something like that but I can't find it

@bararchy It's a wiki page: https://github.com/crystal-lang/crystal/wiki/Crystal-for-Rubyists.
Maybe it should be moved over to the book.

There's an entire website: https://www.crystalforrubyists.com/
We should definitely link that from the book. Maybe we could even incorporate it as a tutorial? 🤔
I'm not sure how up to date the wiki page is. I'd like to remove it / transfer it to the book (/cc https://forum.crystal-lang.org/t/overhauling-the-github-wiki/1303). But it seems https://www.crystalforrubyists.com/ is overall better than the wiki page, so we could really just remove it.


fix: Add list components to the news-item customComponents renderer

This PR fixes the list component rendered from the custom renderer on the news-item.

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


Support horizontal controls on dashboards

It looks like DeepSeeWeb doesn't currently support displaying controls in a horizontal layout. The "horizontalControls" widget gets rendered with a vertical layout, and so does the "Filters" box that is created when controls have location dashboard.
It would be nice to support this to allow e.g. a horizontal row of filters displayed on the top of a dashboard.

@evshvarov could you please make an example for that

I did!
Here it is.
But turned out @gnibeda already implemented it.
@isc-pbarton , could you please check?

Now you can set up horizontak view of the filter  in 1,2 and 3 columns
use the icons in the upper right corner of the widget


[WIP] Draw line on x

This still needs scrolling to be fixed (right now the line just appears after 80chars and if you scroll it stays in the same position).

Alright, this works now, but I'm not quite sure on the implementation. We could either do the following:

So just one line which acts as indicator for the (soft) char limit
Other editors do it like this:

So they draw one rectangle for the OK-area and one rectangle for the This-is-too-wide-area
Opinion, @LiHRaM?

The second one seems better to me. It seems like a more natural transition.

Alright, thanks :)

Looks like this now:

Looks good - do you think it would make sense to have the middle portion lighter and the two sides darker, though? I guess that's just what I expected based on the second example.

Looks good - do you think it would make sense to have the middle portion lighter and the two sides darker, though?

Ah, that highly depends on what theme is chosen.

This makes me feel like maybe xi theming options don't account for this sort of design, maybe going back to option 1 makes the most sense, then?

I've asked in Xi's zulipchat, let's see. FWIW, do you think adding a black line to the rightmost of the linecount to limit it would be a good idea?

I've asked in Xi's zulipchat, let's see. FWIW, do you think adding a black line to the rightmost of the linecount to limit it would be a good idea?

Honestly, I think maybe we should try playing around with spacing a little more. A lot can be achieved with the appropriate padding. (I take inspiration from VSCode mostly, which I think is very well designed.)

Hm, so instead of having a different colour for them you'd suggest to just leave more space between the linecount and the editing area?

Exactly. It works well for other editors at least.
On Sat, Mar 9, 2019, 17:12 Rasmus Thomsen<EMAIL_ADDRESS>wrote:

Hm, so instead of having a different colour for them you'd suggest to just
leave more space between the linecount and the editing area?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Cogitri/gxi/pull/103#issuecomment-471196509, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AYICkc8fuUg6IgqsIJYbDmVm-vjZ0jacks5vU92DgaJpZM4bQ9t9
.

Hmm..will look into that

It looks like this now:

The whole theming situation with Xi-Editor is little mediocre, how about we provide an option to just use whatever the GTK theme dictates (I think some other GTK editors have similar options - not quite sure how to implement it though, will look into it if you think it makes sense). We could also add our own themes, that'd most likely be easier for now.

I think supporting both Xi and GTK themes makes sense, but it might
also be too much work. Your second option of having our own themes also
seems like a big job - maybe we could support custom theming options
within the framework of xi theming, and then PR to the main repo for
the ones we really like?
On Sun, Mar 10, 2019 at 12:51 PM, Rasmus Thomsen
<EMAIL_ADDRESS>wrote:

It looks like this now:
The whole theming situation with Xi-Editor is little mediocre, how
about we provide an option to just use whatever the GTK theme
dictates (I think some other GTK editors have similar options - not
quite sure how to implement it though, will look into it if you think
it makes sense). We could also add our own themes, that'd most likely
be easier for now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

maybe we could support custom theming options within the framework of xi theming, and then PR to the main repo for the ones we really like?

Yes, Xi does plan to rework the theming, but there's no schedule for that yet. We could just hardcode some Themes into gxi for the time being, right now only Solarized* and Inspired GitHub are usable IMHO

I really do prefer the current look to just drawing a line (thanks with helping me with that decision), but it's not visible in InspiredGithub (the standard theme) :c
I'm kind of inclined to just work around this for InspiredGithub while we wait for the theming situation to get better at Xi's side.

This looms very similar to what gedit does now and simply uses a darker version of the background's color


Current Nuxt + Uno docs on minimal install does not apply styles

UnoCSS version
0.54.1
Describe the bug
After following the current default Nuxt 3 install and Uno integration docs, utility classes on app.vue have no affect, and shows no errors.
Reproduction
Maybe I'm missing something super obvious here, but I'm following Nuxt's current install guide (v3.6.5):
And Uno's current integration guide (v0.54.1):
Which equates to:

npx nuxi@latest init nuxt-uno
npm install -D @unocss/nuxt
Add @unocss/nuxt module to Nuxt config
Create default uno.config.ts config
In app.vue, replace <NuxtWelcome /> with
Hello World

Run npm run dev

Minimal repo if needed.
Thanks
System Info
No response
Validations

[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

same, stopped working few hours ago

same here, use @unocss/nuxt: 0.53.5 works well, but 0.54.1 fail.

same problems after update to 0.54.1

Latest working version for me: 0.54.0

Latest working version for me: 0.54.0

not work for me

Investigating, presumably, it's some transmit dependencies break it. So downgrading might not help, if you still have the older lockfile, you can revert to the old lock to workaround it temporarily while we are investigating it.

@antfu after use the cmd pnpm up unimport,  the project works well:
"nuxt": "^3.6.5",
"@unocss/nuxt": "^0.54.1",


Taking a screenshot within a fragment causes a crash

Do you want to request a feature or report a bug?
Report A Bug
What is the current behavior?
My app is crashing upon trying to take a screenshot in a fragment
If the current behavior is a bug, please provide the steps to reproduce.

Any logs, error output, bugreport etc?

07-30 22:32:47.013 2675-2675/com.octothorpeplus.evanstonsubaru E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.octothorpeplus.evanstonsubaru, PID: 2675
java.lang.NullPointerException: Attempt to invoke virtual method 'void android.view.View.measure(int, int)' on a null object reference
at github.nisrulz.screenshott.ScreenShott.takeScreenShotOfJustView(ScreenShott.java:98)
at com.octothropeplus.octolib.fragments.RewardFragment.saveScreenshot(RewardFragment.java:71)
at com.octothropeplus.octolib.fragments.RewardFragment.onCreateView(RewardFragment.java:63)
at android.support.v4.app.Fragment.performCreateView(Fragment.java:2087)
at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1113)
at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1295)
at android.support.v4.app.BackStackRecord.run(BackStackRecord.java:801)
at android.support.v4.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1682)
at android.support.v4.app.FragmentManagerImpl$1.run(FragmentManager.java:541)
at android.os.Handler.handleCallback(Handler.java:751)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6682)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1520)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1410)
What is the expected behavior?
I expect it to take and save the screenshot
Any other comments?
What versions of software are you using?

Device Information:
Samsung Note 5

Android Version:
7.1.1

Configuration Information:

Misc:

Looks like your view is null when you are trying to take the screenshot. Make sure you have the view available of which you take the screenshot of.
java.lang.NullPointerException: Attempt to invoke virtual method 'void android.view.View.measure(int, int)' on a null object reference
at github.nisrulz.screenshott.ScreenShott.takeScreenShotOfJustView(ScreenShott.java:98)

I don't think it's a problem of the fragment itself. Could you share a barebone implementation where the lib crashes because its been called inside a fragment? I would make sure that its being called once the view is created and then try to take the screenshot.


Extract DRM videos from invidious

I'm not an expert in perl but for videos that require youtube-dl you could bring it from https://invidio.us
code extracted from lib/WWW/YoutubeViewer.pm
use JSON;
use Data::Dumper;
use LWP::Simple;

sub _get_formats_from_ytdl {

    my ($videoID) = @_;
    # my ($self, $videoID) = @_;

    my $content = get("https://invidio.us/api/v1/videos/${videoID}?fields=formatStreams");

    my @array;
    my $ref = decode_json( $content ) // return;

    if (ref($ref) eq 'HASH' and exists($ref->{formatStreams}) and ref($ref->{formatStreams}) eq 'ARRAY') {
        foreach my $format (@{$ref->{formatStreams}}) {
            if (exists($format->{type}) and exists($format->{url})) {

                push @array,
                  {
                    itag => $format->{itag},
                    url  => $format->{url},
                    type => $format->{type},
                  };
            }
            print $format->{url};
        }
    }

    #return @array;
}

_get_formats_from_ytdl('TxAtgcNFGfk');

output:
https://r3---sn-ab5szn7z.googlevideo.com/videoplayback?expire=1562757467&ei=-3QlXcb_CNrGhwbC6o4w&ip=2604%3Aa880%3A400%3Ad1%3A%3A92a%3Ab001&id=o-AJNw3o7J1-xSxrcrkJ1LxqEC_knKglIHbyUq3NX8wUgr&itag=18&source=youtube&requiressl=yes&mm=31%2C29&mn=sn-ab5szn7z%2Csn-ab5l6n67&ms=au%2Crdu&mv=m&mvi=2&pl=49&pcm2=yes&gcr=us&initcwndbps=126250&mime=video%2Fmp4&gir=yes&clen=23883497&ratebypass=yes&dur=327.726&lmt=1537305106544723&mt=1562735794&fvip=3&c=WEB&sparams=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cpcm2%2Cgcr%2Cmime%2Cgir%2Cclen%2Cratebypass%2Cdur%2Clmt&lsparams=mm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpl%2Cinitcwndbps&lsig=AHylml4wRgIhAMGzIORxsHR8JT0R7HYcSGzkuVdC3ZzFRslGjTsZPcgjAiEAxIeY9u0w35NpiefreqZY7y-zOpQG8fxBElMlRZ0K5ww%3D&host=r3---sn-ab5szn7z.googlevideo.com&sig=ALgxI2wwRQIhAIACT905b3YYm7lwTaZk52mDYBOSRYOyxTLWR0Vbj4XmAiBGj4zOZjceZsNdwxYBDc-iYfhdobNmm0Z701HcQooFyQ==

^ is a test, with that you would get the YT URL without youtube-dl
Please could do this implementation without using youtube-dl. Or in the last case you could help me how to add this change

Thank you for your suggestion.
I will consider implementing this as a configuration option disabled by default, which users (that are willing to share the video IDs with invidio.us) can enable, but the implementation which uses "youtube-dl" will still be used by default.
Notes:

The API documentation of invidio.us is available at: https://github.com/omarroth/invidious/wiki/API
For videos with audio/video on split URLs, the adaptiveFormats needs to be used. (e.g.: https://invidio.us/api/v1/videos/j5-yKhDd64s?fields=formatStreams,adaptiveFormats&pretty=1)

However, it's unclear at the moment how reliable invidio.us is or will be in the future.

However, it's unclear at the moment how reliable invidio.us is or will be in the future.

It's true I had not thought about that.
As a third option invidious I find it the best 😄

Support for invidio.us has been added in https://github.com/trizen/youtube-viewer/commit/0cd9a5414513d18213d8fe460c533b7107b56ebc.
In my tests, I discovered a few videos for which invidious fails, but youtube-dl succeeds.
One such video is: https://invidio.us/watch?v=Dsp_8Lm1eSk

Support for invidio.us has been added in 0cd9a54.
In my tests, I discovered a few videos for which invidious fails, but youtube-dl succeeds.
One such video is: https://invidio.us/watch?v=Dsp_8Lm1eSk

when I put the option --invidious does not work
I've tried with: youtube-viewer --invidious

There was indeed something missing. Should be fixed now. Thanks for testing and reporting this issue.


Fix config.yaml

What type of PR is this?
(REQUIRED)

[X] bug
[ ] cleanup
[ ] documentation
[ ] feature

What this PR does / why we need it:
The current logic for building config.yaml doesn't populate values properly.
To simplify and fix the proposed fix is using the jinia2 template.

Which issue(s) this PR fixes:
Fixes #138

Release Notes

NONE

Thank you for contributing @marcinkubica. Unfortunately, this change does not work as it did previously. I like the approach you took, but we also need to account for other variables that can be passed into the RKE2 config file. The roles were written so you can pass in arbitrary RKE2 configuration. The logic in the config.yml was to allow for the possibility of adding certain variables to both host_vars and group_vars while also being open-ended for the rest of the config options.
for example, an RKE2 config can be provided via group_vars like this:
rke2_config:
  selinux: false
  node-label:
    - groupvarlabel1=true
    - groupvarlabel2=true
  kube-controller-manager-arg:
    - "tls-min-version=VersionTLS12"

with your change, the SELinux and controller args are dropped.

thanks for the info @mddamato
I won't be able to continue on this anymore - feel free to drop/develop as needed


 There are two holes in the eyes. the lip edge is too sharp which is different from the true data.  The third picture is more accurate which is captured by other RGBD device. Actually we found Kinect One also have the same problem before.
camera configuration:
k4a_device_configuration_t config = K4A_DEVICE_CONFIG_INIT_DISABLE_ALL;
config.depth_mode = K4A_DEPTH_MODE_NFOV_UNBINNED;
config.camera_fps = K4A_FRAMES_PER_SECOND_30;
config.color_format = K4A_IMAGE_FORMAT_COLOR_BGRA32;
config.color_resolution = K4A_COLOR_RESOLUTION_720P;
the distance between camera and face is about 700mm.

Thanks for the report. Do the lip edge and nose edge look different if the camera is placed lower relative to the face?

@Ayangdanny thanks for reporting this issue. I believe the issues you are seeing are artifacts of the camera hardware and not software. For now I am resolving this bug as by design. Please reactivate the issue if there are specific changes you would like to see.


o.snapshotRequest is confusing and misleading

Making a quick note to try and address this.
This method is strange and feels out of place. Maybe it has to live on the Operator, but it's odd....
https://github.com/terrapower/armi/blob/78477048c1f9d331bc531351bd450fe82d786e5e/armi/operators/operator.py#L1063-L1076
The docstring calls out that the concept of "snapshots" has evolved since this method was written - and as is, is quite confusing relative to the snapshot operator. I would propose that this method (if possible) get moved over to the snapshotInterface -- and if possible renaming the snapshotInterface to something more accurate with its current intended usage. Something like dumpInputInterface or something like that....

@keckler

Sure, I like this.
The method Operator.snapshotRequest() only needs two class attributes from the Operator: the Reactor and the CaseSettings.  These will both be easily available in the SnapshotInterface, so there will be no problems moving the method over.
I only see snapshotRequest() used once outside of ARMI, so this should be an easy change to make.

@john-science any thoughts on renaming the snapshotInterface too?

and if possible renaming the snapshotInterface to something more accurate with its current intended usage. Something like dumpInputInterface or something like that....

Renaming snapshotRequest() or moving it, will affect one downstream repo, that I see.
Renaming SnapshotInterface and it's file, will affect three downstream repos, that I see.


added branches to cert manager builds

release-cd
release-efix
release-eus

deleted build for release-3.8 since release-eus replaces it
What this PR does / why we need it: To work with new CICD pipelines
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Specify your PR reviewers:

/cc @gyliu513 @horis233
Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

/assign @ashank07

According to the new pipeline, I believe you need to use release-future to replace release-cd.
cc @ashank07 Please correct me if I am wrong.


fix: Enforce NonAdminBackup spec field values

Why the changes were made
Resolves https://github.com/migtools/oadp-non-admin/discussions/33
Related to: https://github.com/migtools/oadp-non-admin/issues/37
~Blocked by: https://github.com/openshift/oadp-operator/pull/1584~
This PR adds fetching of OADP's DPA during NAC set up, adding DPA spec.nonAdmin.enforceBackupSpec to NonAdminBackupReconciler and adds validation for NonAdminBackup spec respecting enforcement.

Note: admin user can not enforce falsy values.

How to test the changes made
Read design.
Follow install-from-source testing documentation, pointing this branch and my OADP fork branch fix/enforce-non-admin-bckup-spec-field-values

/hold Blocked by https://github.com/openshift/oadp-operator/pull/1584

@shubham-pampattiwar there was also small lint issue while running make lint on that PR, should be fixed now:
internal/common/function/function.go:85:21: cannot range over enforcedSpec.NumField() (value of type int) (typecheck)
	for index := range enforcedSpec.NumField() {
	                   ^
internal/common/function/function_test.go:363:22: cannot range over backupSpec.NumField() (value of type int) (typecheck)
		for index := range backupSpec.NumField() {
		                   ^
internal/controller/nonadminbackup_controller.go:610:22: cannot range over enforcedSpec.NumField() (value of type int) (typecheck)
		for index := range enforcedSpec.NumField() {
		                   ^
make: *** [Makefile:75: lint] Error 1

cmd/main.go:33: File is not `gci`-ed with --skip-generated -s standard -s default -s prefix(github.com/migtools/oadp-non-admin) (gci)

/lgtm

/retest

override snyk as it's not problematic atm


Location after first start

When location access is disabled after sparcl was opened the first time, starting the AR session isn't possible - start button is disabled - and there is no easy way to allow location access again.
Add slider to repeated visit overlay and add location permission request screen when location access isn't allowed

Resolved in 7285311fa856cd1bcb20bc487fac85aecb381469


remove unused code

Issue link

#534
#525
What changes have been made

deletion of dead code and legacy operator code
Verification steps

Checks

[X] I've made sure the tests are passing.
Testing Strategy

[ ] Unit tests
[ ] Manual tests
[ ] Testing is not required for this change

Nice!
/approve

/retest

@asm582: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name	Commit	Details	Required	Rerun command
ci/prow/unit-hypershift	00b0758 link	true	/test unit-hypershift
Full PR test history. Your PR dashboard.

@astefanutti  hypershift CI job is failing, can you please help, I am not sure how to fix it


[google compute] adding all list params to all list functions

This PR adds support to all list_XXX() and ex_list_XXX() driver methods using the parameters provided by GCE API as described in this example, https://cloud.google.com/compute/docs/reference/latest/diskTypes/list.

Users can now provide an ex_filter to restrict search results to filter matches such as nodes that match name eq "test.*".

Users can now step through large resource sets ex_max_results for each method call until no more results are returned. In GCE terms, this allows for "pagination" and uses a pageToken query parameter to step through the resource set. Users can 'reset' the step pointer by specifying ex_reset_page_token, e.g.
subset = gce_driver.ex_list_snapshots(ex_max_results=2):
while subset:
    # do something with this subset of snapshots...
    subset = gce_driver.ex_list_snapshots(ex_max_results=2)
gce_driver.ex_list_snapshots(ex_reset_page_token=True)

@verb - I like your idea much better! I'd be totally fine with closing out this PR if you want to take this over. :)
@Kami - thanks, that makes sense. I was partly on auto-pilot with the ex_ convention because filter is a reserved word and happens to match the GCE API. But we can use a different param name such as filter_match or some such.

@erjohnso SGTM.  I'll polish it up and create a PR.  You may want to hang on to your git history until then, though. :)


Fix text width on documentation pages

Text Width on doc pages seems strange (but this is the Docusaurus default?)
Recommend following Readability Guidelines for Text Width which is 50 to 75 characters

@dan-gnosis check the layout width (red) vs the image size (yellow). it seems that the image is not using the whole width of the page, which makes us think that "text width" is the problem when the width of the images is.


autoSpacing  not working when jumping between pages in swipeHorizontal(false)

When .swipeHorizontal(true), then .autoSpacing(true) works just fine.
However, when .swipeHorizontal(false), then  .autoSpacing(true) works only when swiping between pages, meaning that, when using pdfView.jumpTo(pageNumber), then autoSpacing doesn't seem to work!
Can you please fix this?

I found a workaround for this issue.
After calling jumpTo, call performPageSnap.
pdfView.jumpTo(pageNumber, false);
pdfView.performPageSnap();