rand: implement an unbiased random integer from a range

Refer: https://github.com/apple/swift/pull/39143 for a description of the algorithm.
It is optimal in the sense of having:

no divisions
minimal number of blocks of random bits from the generator

[ ] documentation is added or updated
[ ] tests are added or updated

[0, max) is the commonest range required.
A helper function is a reasonable idea still.

I temporarily copied this into my HPKE code and it seems to work when picking GREASE values.
There's a snippet of code I used to informally test this here. Not sure how one could write a good test that could be part of the test harness without generating some bogus test fails.

The pathological case will be around 2³¹+1 where just under half the values are in the rejection region.  Given the test only needs the third random sample less than one time in 2³², testing isn't practical using less than (at a guess) 2⁶⁴ samples.
It would be possible to test this better by reducing the size.  E.g. generating 4 bit numbers under 9.  A mistake should become obvious in reasonable time.  Not useful for our test suite but good for confirmation.  χ² is probably good enough here.

I've run a χ² test (p=0.99) for the output of this algorithm modified to work with 4 bit "words" and it seems good.  Test harness is attached.
There seems to be a slight problem with the χ² test for this discrete uniform distribution.  I'm seeing test failures for small samples at a higher than expected rate (gut feel, not measured).  For large samples it comes good and the test statistic reduces nicely.  I'm pretty sure this is because the sum of uniform distributions is pretty non-normal in nature.  As the number increases the central limit theorem kicks in and it tends towards normal.  Convergence to normal being, aproportional to the square root of the number of samples accumulated (i.e. 100 gives approx 1 digit, 10,000 gives approx 2 digits, 1,000,000 gives approx 3, etc).
Given the instability for small sample sizes and the time required to generate large samples, I do not see how this can reasonably be directly tested as part of our CIs.
Run using 1,000,000 samples (note the jmax of -1 for powers of two which means no extra sampling was required which is optimal):
max =   2: 5000209,4999791,
max: 2, chi_sq: 0.017472, exp: 5000000.000000, jmax: -1
max =   3: 3334176,3333923,3331901,
max: 3, chi_sq: 0.932812, exp: 3333333.333333, jmax: 5
max =   4: 2499708,2501113,2499781,2499398,
max: 4, chi_sq: 0.693759, exp: 2500000.000000, jmax: -1
max =   5: 1999827,1998874,2000430,2001946,1998923,
max: 5, chi_sq: 3.214775, exp: 2000000.000000, jmax: 5
max =   6: 1668577,1665917,1664706,1666297,1667846,1666657,
max: 6, chi_sq: 5.749897, exp: 1666666.666667, jmax: 5
max =   7: 1430465,1428065,1427089,1431038,1428160,1427327,1427856,
max: 7, chi_sq: 10.047356, exp: 1428571.428571, jmax: 6
max =   8: 1249737,1249194,1249188,1250900,1250879,1247944,1250256,1251902,
max: 8, chi_sq: 8.696853, exp: 1250000.000000, jmax: -1
max =   9: 1110782,1112213,1110730,1109803,1111333,1110297,1112125,1110449,1112268,
max: 9, chi_sq: 6.026075, exp: 1111111.111111, jmax: 6
max =  10: 1001779,999831,1000708,999221,999167,999181,1000838,1000199,999904,999172,
max: 10, chi_sq: 7.102802, exp: 1000000.000000, jmax: 6
max =  11: 909015,909267,908319,909278,909771,909127,909099,909859,908548,909467,908250,
max: 11, chi_sq: 3.151274, exp:<PHONE_NUMBER>91, jmax: 5
max =  12: 833981,833851,832271,833759,831721,834955,833605,831482,833055,833270,833272,834778,
max: 12, chi_sq: 15.480190, exp:<PHONE_NUMBER>33, jmax: 5
max =  13: 769947,769383,769361,768888,769172,768927,770154,770032,769173,768483,769544,769447,767489,
max: 13, chi_sq: 7.802330, exp:<PHONE_NUMBER>31, jmax: 6
max =  14: 714751,714341,715299,715759,715366,714639,715462,714295,713665,713116,713868,713069,712071,714299,
max: 14, chi_sq: 20.168345, exp:<PHONE_NUMBER>86, jmax: 5
max =  15: 666945,666580,666357,666583,666835,665888,666941,666078,666901,667459,666406,667807,666785,665420,667015,
max: 15, chi_sq: 7.477271, exp:<PHONE_NUMBER>67, jmax: 5

Run using 100,000,000 samples:
max =   2: 50000227,49999773,
max: 2, chi_sq: 0.002061, exp: 50000000.000000, jmax: -1
max =   3: 33333736,33335688,33330576,
max: 3, chi_sq: 0.399284, exp: 33333333.333333, jmax: 6
max =   4: 24999959,24991483,25010198,24998360,
max: 4, chi_sq: 7.169191, exp: 25000000.000000, jmax: -1
max =   5: 19997333,19999866,19998849,20005677,19998275,
max: 5, chi_sq: 2.182980, exp: 20000000.000000, jmax: 6
max =   6: 16662808,16667571,16670404,16665877,16662650,16670690,
max: 6, chi_sq: 3.757151, exp: 16666666.666667, jmax: 6
max =   7: 14292468,14286611,14284433,14281405,14284730,14290095,14280258,
max: 7, chi_sq: 8.159124, exp: 14285714.285714, jmax: 7
max =   8: 12501541,12502211,12498975,12494419,12499109,12498508,12503983,12501254,
max: 8, chi_sq: 4.793451, exp: 12500000.000000, jmax: -1
max =   9: 11115182,11112197,11108881,11111277,11111626,11110032,11107010,11109843,11113952,
max: 9, chi_sq: 4.561170, exp: 11111111.111111, jmax: 6
max =  10: 10003841,9996950,9997881,10000856,10006798,9996979,9997489,10003917,9998301,9996988,
max: 10, chi_sq: 11.822468, exp: 10000000.000000, jmax: 6
max =  11: 9082970,9093585,9093643,9088370,9092530,9093158,9090855,9093816,9090446,9092860,9087767,
max: 11, chi_sq: 12.555633, exp: 9090909.090909, jmax: 7
max =  12: 8333088,8336416,8331807,8332156,8332507,8333341,8331224,8337499,8332227,8336944,8327919,8334872,
max: 12, chi_sq: 9.804860, exp: 8333333.333333, jmax: 6
max =  13: 7696332,7692870,7692381,7688343,7697700,7691600,7689949,7693650,7697364,7690380,7694020,7684898,7690513,
max: 13, chi_sq: 20.737228, exp: 7692307.692308, jmax: 7
max =  14: 7145699,7144015,7140442,7139170,7146915,7145519,7140261,7147240,7141788,7141980,7139704,7141792,7143237,7142238,
max: 14, chi_sq: 12.860781, exp: 7142857.142857, jmax: 6
max =  15: 6664666,6667752,6665883,6667425,6671139,6667166,6666848,6669380,6662383,6664535,6663906,6663461,6665028,6668392,6672036,
max: 15, chi_sq: 16.394865, exp: 6666666.666667, jmax: 7

nit: unbiassed -> unbiased

Addressed comments...

Ping @openssl/committers for reviews.
The algorithm isn't as daunting as it first appears.

@mspncp Are you happy that your requested changes have been made?

Yes I am. You may dismiss my previous change request if you like. (I didn't find a way how to do it from the mobile app.)

Ping @mspncp or @openssl/otc for review please.

Adding 3.2 because the HPKE change is worthwhile there and it depends on this.

Adding 3.2 because the HPKE change is worthwhile there and it depends on this.

Can I get a clarification here? This comment from @mattcaswell says that beta releases are usually treated as stable releases - would new features go there?

The HPKE fix has been deemed a bug fix which means it can be back ported.  It requires this, so this will be too.
Beta (hopefully) freezes the public API.  Since this is entirely internal it not part of our API guarantee.

Hiya,
A good set of questions, worth asking...
On 31/10/2023 00:52, Matthias St. Pierre wrote:

What about timing issues? As mentioned in
https://github.com/apple/swift/pull/39143#issuecomment-912185936, the
algorithm can leak timing information. Can this potentially cause
problems for the intended use-case, HPKE?

I can try answer that part. As of now, the only coded-up use of this
is for GREASEing HPKE which is so far only for ECH, and only for use on
TLS clients before sending a ClientHello, so I don't think there's a
timing concern there for any realistic client using OpenSSL.
That said, with ECH, I have a TODO which is to add some GREASEing of
retry_config values, sent in response to a TLS ClientHello as an
encrypted extension. In theory, that could emit a timing signal, but
my plan is to do that GREASEing (and hence call this RNG) at key load
time and not at response generation time. (That code is not written
yet, so that could change I guess, but I'm happy to say I won't do
that particular bad thing when making a PR for ECH:-)
I think QUIC+ECH would/should be the same as TLS+ECH in terms of the
above, but there's no actual QUIC+ECH implementation so far.
The other HPKE-using specification that might warrant consideration is
MLS. I've not done any analysis of how timing issues might arise there
but if this were also only used for GREASEing then the situation should
be similar.
For this PR, I'd say adding a note to the documentation that says "do
consider timing issues" might be sufficient at this point, given that
the function is so far only being used to select GREASE'y values and
not values that are later used as keys or similar. Having that
documentation describe whatever timing issues may exist would be nice.
Lastly, for HPKE, the alternative to this is to emit packets with a
minor bias in GREASE'y codepoints (the status-quo ante), or to do
rejection sampling, and I'd guess either would emit more of a signal
(via timing or codepoints) to network observers than this algorithm.
If it helps, I'm happy to raise the GREASE'y codepoint timing issue
with relevant IETF lists, but I suspect the answer we get will be that
there are so many other timing and/or traffic analysis signals in
protocols using HPKE that this is not currently a live concern And I
think that'd likely be a correct conclusion.
Cheers,
S.
PS: In case it helps, the GREASE'y use of this for ECH is not to
pick values like fake keys or ciphertext values, but only to pick
fake algorithm/suite IDs. Subsequent code then generates "real"
fake values for keys/ciphertext based on those not-really-in-use,
but usable, algorithm/suite IDs.

IMO a CLA is not required.  I wrote all of this code myself.  I did not base it on the referenced code.
More specifically, the reference code generates at most two 64 bit integers and assumes the final error is less than 2^-64.
Here, I keep generating 32 bit integers until there is a final definite resolution (at least until the loop terminates via the counter).  I figured things out from the description and extended it to multiple limbs.
Thus, I do not believe the CLA: require tag is appropriate.

In response to the other questions:

How trustworthy is the algorithm?

Very.  It is generating a uniform [0, 1) value which is multiplied by the range.
If there isn't a definitive outcome based on the fractional part of the range, it generates more bits until there is.
So long as the RNG is unbiassed, the result will be.
I have no concerns here.

What about timing issues?

Irrelevant IMO.  Multiple steps generating a random number reveals nothing about the final result.  All an attacker could learn was that the generated number's fractional part was just under one half.  For r ∈ [0, n), you know that frac(r) was either just below or equal to ½.  Assuming that rounding down is the final outcome (which it almost always will be), this gives you no information about ⌊r⌋, just that it cannot be n.

Should this go into 3.2 as a last-minute change?

This should go in if the associated HPKE PR goes in.  If that doesn't go in, this shouldn't.
It's not a public API so it is not a breaking change.
I believe there is an OTC hold in place, so we'll discuss later (assuming I'm awake).

This was written from scratch. CLA hold does not apply.

OTC: vote to include PR subject to normal review process

This was written from scratch. CLA hold does not apply.

I didn't doubt the fact that it was written from scratch. But except for minor adjustments, it is the same algorithm. As a mathematician, I find it remarkable and non-intuitive that it's only the written program and not the underlying algorithm which is considered an intellectual property. Fortunately, I'm not a lawyer, and if they are happy with this interpretation, I'll not dive down further into this rabbit hole.

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

The code here is different to the one referenced.  The referenced one only generates a second 64 bit value and accepts a 1 in 2^64 chance of bias.  This PR, instead, generates 32 bit values and continues to do so until a definitive result is obtained -- this is not covered by the referenced code.
Algorithms cannot be copyrighted.  They are patentable (unfortunately).

@tom-cosgrove-arm please reconfirm

Still okay

Merged to the master and 3.2 branches. Thank you.


[DS-2767] Sites can no longer inject preconfigured connection pool using config/dspace.cfg:db.jndi

https://jira.duraspace.org/browse/DS-2767
Note that this does not resurrect db.jndi.  It uses a fixed name 'java:comp/env/jdbc/dspace'.  This name is only used in the Context, where it is linked either to the DataSource itself or to a global resource which may have any name.

This way the JNI becomes the primary check for the datasource, was this also the case before the hibernate changes ?
If JNI was not the default previously perhaps we should add the JNI config in comments and then document how to enable ?

The first thing done in the old DatabaseManager.initDataSource() is to see if configuration parameter "db.jndi" is defined and, if so, look up the object that it names.  If not defined or not found, then it builds its own connection pool.  So, yes, this is a little different.  I've tested the new arrangement with and without defining jdbc/dspace, and without is quick and IMO actually less noisy than the old way.
Looking up a name in the container-provided InitialContext is perhaps the cheapest thing that DSpace does at startup.  Since Spring's factory bean for this does defaulting for us, it seemed better to just use that, than to resort to SPEL conditionals or ask people to hack on the Hibernate configuration.

@mwoodiupui Understood, then this change makes sense, haven't tested it yet but a +1 from me (as we want to perserve as many default configurations as we can)

+1 looks good, and we do need to retain this functionality.  Needs documentation on its new location though, so folks are not continuing to look for 'db.jndi'


fingerprint duplicate dialog appears

Samsung s10, Android 9
"nativescript-fingerprint-auth": "^7.0.2",
useCustomAndroidUI: true
Please check it.

My guess here is that your phone is having an in-display fingerprint scanner.
The whitebox behind is the "useCustomAndroidUI" however your phone has its own fingerprint dialog. The right fix would be to have useCustomAndroidUI to false on devices having an in-display fingerprint scanner

@jamesst20 Is there any way to know that a device have in-display fingerprint scanner?


Allow for multiple push credentials

It should be possible to have active credentials for multiple image registries. So that Build CRD can push images to difference locations depending on the function.
Currently riff namespace init requires one of a manual secret, Docker Hub or GCR credentials. If a preexisting secret exists, it is replaced with the new value. New credentials should augment the service account to allow for migrating to a new image registry.

Apologies in advance if I misunderstand the current state of riff and Knative:

If a preexisting secret exists, it is replaced with the new value
It seems to me that the current impl preserves the pre-existing secret, if they share the same name (https://github.com/projectriff/riff/blob/master/pkg/core/namespace.go#L142).
TheIsn't it sufficient to bind a new secret with a different name to the existing service account to have subsequent builds

It seems to me that the current impl preserves the pre-existing secret, if they share the same name

Good question, registering the secret is a two step process:

create the Secret resource
reference the Secret in the ServiceAccount

The line you linked to is when the secret is registered with the ServiceAccount. We delete a preexisting secret as a part of step 1.

is it sufficient to bind a new secret with a different name to the existing service account

I think so, but we'll need to try it to verify.

Thanks for clearing that up.
Without changing code, my assumption is that running namespace init against the same namespace with different secret names each time would do the job (although I'm not saying this is a good solution).
Back to the initial suggestion, do we want to get rid of the secret overwrite in 100% of cases? Shouldn't we remove the preexisting secrets if the metadata annotations of the existing and new secrets are equivalent?

I think we should add a command to add credentials to an already existing riff-build service account.
We would require the secret name to be something other than push-credentials and the service account riff-build to already exist, the rest of the flags would match namespace init
riff namespace add-credentials --secret extra-creds [--gcr <path>] [--docker-hub <docker-id>] [--registry <registry-url> --registry-user <user>]

Note: these added credentials should be removed when running riff namespace cleanup.

Here is the updated specification for this issue:

[ ] introduce credentials set [--secret <secret> (default: push-credentials)] [--gcr <path>] [--docker-hub <docker-id>] [--registry <registry-url> --registry-user <user>] [--namespace <ns>]
[ ] introduce credentials list [--namespace <ns>]
[ ] introduce credentials delete [--secret <secret>] [--namespace <ns>]

By supporting the following features, the plan is to also deprecate/remove namespace init:

create the riff build service account if it does not exist when credentials set is called
handle the image prefix just like namespace init does when credentials set is called

As suggested by @scothis, there are two options to implement riff namespace cleanup:

delete the service account and remove the image prefix from the config map when the last secret of the namespace is removed with riff credentials delete.
let riff-system match the resources by the initialization labels used

done in #1266


any plan to build new release?

2023.Q3 it's always panic for concurrent map. New version release is supposed

Sorry for the delay on this.
v0.18.0 is out now:
https://github.com/dolthub/go-mysql-server/releases/tag/v0.18.0
Please let us know if you have any issues using it.


App doesn't show images

First of all thank you for this really nice project. I installed v2.0.0-alpha1 because v1.7. is not running at all. But the App doesn't show the post images and author images.

Be sure when you run v1.7 that you are following the instruction for this version.
If this screenshot was taken from firefox, it's normal, use chrome and it should work. If not, it might be because your posts don't have featured images.

It works with Chrome. Thank you :)

Thanks @PierreBresson :)


Rewrite to use websockets.

I've become convinced that the basic problems with the WebRTC/PeerJS implementation are not going to go away. Though this version has the advantage of permitting the entire application to be served statically, without any work for a server, it is simply too difficult to reliably guarantee connections between arbitrary peers across the network.
Without doing too much damage to the rest of the program, I've changed the underlying system to use websockets instead. This requires a dedicated server program to forward requests between clients. This has the disadvantage of requiring a server somewhere, but the current deployment is so lightweight and receives so little traffic that I've only burned through 1% of my free $5 from fly.io. I'm happy to foot the bill for $5/month for this, frankly.
The primary changes to the client were in the functions usePlayerConnection and useDmConnection. These were entirely rewritten to handle a new set of rules for sending and receiving messages. I also moved the warden's logic for keeping track of which players are connected into the server, which required adding a new message type for the server to tell the warden which players are connected.
For more details about the proposed changes, see the modified client, and server, at:

https://git.sr.ht/~p0mf/mothership-assistant-client
https://git.sr.ht/~p0mf/mothership-assistant-server

I am not formatting this as a pull request since the changes are at the end of a long series of miscellaneous fixes and improvements made for personal use. Before preparing a clean pull request, I'd like to ask your input and opinion. I can confirm that this resolved some difficult connection issues in my case and would like to invite other people to test this new version.
PS: this version is deployed at https://mothership-assistant.surge.sh

So this is something I had considered (and somewhat implemented in an old project) but I really wanted to avoid any kind of infrastructure. The reason isn't the cost but rather the maintainability & monitoring required.

How do you see this test? do you want to invite people on https://mothership-assistant.surge.sh/ or that we deploy it on https://mothership-assistant-canary.wandering-mushroom.com/ ?


Hammerdb

addition of hammerdb benchmarking to ripsaw (I had a couple of git issues, so please bear with me..)


Docker Dashboard UI issue - image name foreshortened

The Docker Dashboard provides a tabular display of images, tag, image ID, creation data and size.
The columns are of equal width and fixed width.
For images with long names, particularly of the form VERY_LONG_ORGANISATION_NAME/IMAGE, this can make it hard to identify which image is which.
On a Mac:

It would be useful to be able to:

resize / drag the columns, or
give the image name a larger column width, or
provide a tooltip to display the full image name when the mouse hovers over it

@psychemedia thanks for raising, we had added this as a bug in our backlog. We will probably start with a tooltip at least on hover over here and in the details view


Change Interactive effects speed maximum

List any issues that this PR fixes: fixes # , etc...

N/A
This pull request proposes the following changes:

Change Interactive effects speed maximum from 20 to 500
Interactive effects speed at x500 look super cool on corsair K70

Known issues/To do:

N/A

Please submit a pull request to the dev branch, not master. Also make sure to work from the dev branch, not master.
Consult CONTRIBUTING.md for details.


Requesting help to reproduce a memory corruption crash in task creation

Hello,
I found a crash when trying to read /proc/%d/cmdline on a kthread manually created with argv=NULL.
After some unresponded messages on the mailing list I got no feedback so here is a github issue.
The crash happens when trying to read /proc/%d/cmdline, but using gdb watchpoints, I have determined that the memory address that stores tcb->group->tg_info->argv[n] is written  by an later arm exception, which is most probably a context switch.
This leads me to believe that the stack adjustment does not work correctly in certain cases.
This is a very annoying bug with a memory corruption and I would like to fix it, but I need to reproduce it in an isolated case that developers can reproduce.
Who has nucleo h7 boards and is able to help me fix this?
Thank you for your help.

Can some one please help me with the CI? like it failed successfully but I have no idea why
https://github.com/apache/nuttx/pull/9277

No one cares, ok. worked around but still no root cause for this.

No worries, I worked around it.
I was waiting to integrate watchdog kicker support, so people can reproduce it, thats why there are not a lot of info as of now.
However, lots of tests showed that I could not reproduce it with a canned config on the nucleo board.
The best fix was to avoid the issue, which is not very satisfying, but seem to work.
If someone finds weirdness around corruption of kthread arguments, that might be it reappearing.

I have the board your PR was for so if you do end up finding some kind of repro with it I am happy to dig it out of the box and try to help.

@slorquet get some love and be patient, they are virtues.  Thank you.


Typo in extension.json

There is a typo in the extension.json in the zip file created by clicking 'Generate Extension' - the description key is mispelled.
This causes CoVE to crash when you upload a spreadsheet which references the extension.json in the Meta tab

Fixed in d45486ea (typo was desription).
(When reporting typos, it's easier to find the issue if the typo is known, rather than the correction :))


[Feature Request] Media 'Cleanup' function

As I've been updating my FullDMD videos, I've noticed a lot of media that no longer has an associated table. A function that scans all Popper media folders and deletes media that is not associated to a table would be a nice addition to keep the file count down.

Isn't this a duplicate of https://github.com/syd711/vpin-studio/issues/134 ?
This feature is under development from the Visual Pinball Back Manager guy. I'll integrate it once he is finished.

coool

I close this as duplicate and will contact Matt (@Malibu) about the status.


Legend for color schemes

Hello,
Thanks for the excellent package, I use it all the time and love it.
I want to add in a legend that defines which colors mean what for a color scheme (eg which colors indicate hydrophilic or hydrophobic for the hydrophobic color scheme). Is there some way to expose exactly which colors are used in the color schemes? Like the hex values or something?
Thank you,
Lili

I was able to find the colors via logo.rgb_dict or logo.color_scheme


Check possibility to deploy several replicas of Fybrik manager in active-passive config

To increase HA check possibility to deploy several replicas of Fybrik manager in active-passive config.

The manager already supports this option by default:
--leader-elect option is set by default in manager-deployment.yaml. It uses a config map named fybrik-operator-leader-election  as a lock in the leader election process. This config-map contains info about the elected leader:
apiVersion: v1 kind: ConfigMap metadata:   annotations:     control-plane.alpha.kubernetes.io/leader: '{"holderIdentity":"manager-658d5f4fdf-785p6_ba63ebbb-844c-4e2d-9148-100f16551d24","leaseDurationSeconds":15,"acquireTime":"2022-06-20T03:39:55Z","renewTime":"2022-06-20T03:49:52Z","leaderTransitions":2}'   creationTimestamp: "2022-06-19T12:58:08Z"
So, when changing the value of replicaCount in Values.yaml to 3 for example, 3 manager pods are created while only one is the leader. This is the info from the leader's log.
 attempting to acquire leader lease fybrik-system/fybrik-operator-leader-election... I0620 03:39:55.887444       1 leaderelection.go:258] successfully acquired lease fybrik-system/fybrik-operator-leader-election
and when deleting the manager pod which is the leader a new leader is chosen and the config map fybrik-operator-leader-election is update accordantly,


feat: grab agent code via REST api

Be smarter and more dynamic by utilizing the api to pull the agent code vs. having a potentially outdated version in this repository.
Add or list browser apps
curl -X GET 'https://api.newrelic.com/v2/browser_applications.json' \
     -H 'X-Api-Key:<Account REST API KEY>' -i \
     -G -d 'filter[ids]=<Browser App ID>'

There's a better way, closing in favor of #4


Official docker image for Hugo

Would you be open to me contributing a Dockerfile so as to automatically create official docker images (via hub.docker.com as a 'trusted' image) based on release tags of this repo?
I'm also thinking that perhaps the hugo new site --with-docker command can be made to include a Dockerfile that looks like:
FROM gohugo/hugo

ADD . /app
ENV HUGO_THEME hyde-x
RUN hugo -t ${HUGO_THEME}

where my Dockerfile would define the gohugo/hugo image. I would be basing it off something like https://github.com/srid/www.srid.name/blob/master/Dockerfile

Note/Update: This issue is marked as stale, and I may have said something earlier about "opening a thread on the discussion forum". Please don't.
If this is a bug and you can still reproduce this error on the latest release or the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.

This issue is old and stale, and no one has shown enough interest in it to make it happen. I will close this now, and by that, I'm not saying that this "isn't worth adding to Hugo", I'm just saying that anyone that really wants this, will have to create a new tracking issue for any future Pull Request that solves this issue.


feat: update results ranking

This PR update the results ranking for nemeton builders program.

When will it be updated today?

When will it be updated today?

@antho31
There is only @amimart who can release and deploy , I asked him to release it ASAP..

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


Do I need arduino to control the dc motor and direction?

I'm a newbie at E&E and try to learn something. However I'm looking at the coding for a long time and I'm wondering do I need the arduino uno to control the rc car. Thanks in advance.

No, i used the adafruit motor HAT with the raspberry pi to run the motors using just the keyboard. Theres a bit of code change but its easy to understand once you try a few tutorials from adafruit.

any chance you would share your code?


TypeError: tv.getVector is not a function

I did npm install term-frequency. Then, there were complaints about other modules like stopword and term-vector not installed. I did install them via npm install. However, I am unable to get the example up and running.

Thanks for the feedback. Which example is not working? Can you copy it here?

var sw = require('stopword'); var tf = require('term-frequency'); var tv = require('term-vector'); var vec = tv.getVector(   sw.removeStopwords(     'This is a really, really cool vector. I like this VeCTor'       .toLowerCase()       .split(/[ ,\.]+/)>    ) ) var freq = tf.getTermFrequency(vec);
This one.

ah yes, term-frequency is looking for an older version of term-vector in this example.
try npm install stopword<EMAIL_ADDRESS>term-frequency and then run the example

Yes. It works.


Kary Foundation themes added.

Kary Foundation - Light and Kary Foundation - Dark added.

P.S
As you guys seems to be busy. I would be really honored to help you with Colorsublime, your website helped me a lot and well what's better than I helping back 😄


Change API app names to remove "management"

On hold due to further discussions on DNS/naming, see #791

no longer needed


Brazil Southeast?

Now that Brazil Southeast is available, is it going to become a paired region for Brazil South? Thanks.
[Enter feedback here]

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

ID: 09a788e4-0130-73f2-d985-6fc3aec77974
Version Independent ID: a9f4ec3f-f0a3-b050-020b-f487c74c5179
Content: Ensure business continuity & disaster recovery using Azure Paired Regions
Content Source: articles/best-practices-availability-paired-regions.md
Service: multiple
GitHub Login: @barbkess
Microsoft Alias: barbkess

@niklarin We are assigning this to our author for information regarding this.
@barbkess Please help us to answer the Cx question.

Hello, any movement on this?

@martinekuan Please help here.

#please-close


Key already registered with the same priority: GroupSpatialSoftmax

When I am running the code from the following command
python test.py

Then I am getting just the following output:
Key already registered with the same priority: GroupSpatialSoftmax
Please help me.

Hi @mayanktiwariiiitdmj
Is this solve? I got the same issue.

yes, I solved this issue by deleting the current environment and then making another.


How to keep configuration up to date?

I have generated configuration some time ago using version RC-13. I also modified many of the attributes (mainly enabling more rules and updated a few settings).
New detect versions introduce new "configuration attributes" (like ignoreLocalVariableDeclaration introduced here https://github.com/arturbosch/detekt/pull/1555).
What is the best way to make sure that my configuration contains all the "config attributes" (not just use default values because an attribute is missing from my old config)?

I think using your favorite diff viewer for the config file might be the easiest option to see what changed between different versions.
Checking the change log is also helpful.
If you only have minor changes the flag --build-upon-default-config makes sense.

Diff tool works, but nowadays detect config has 500+ lines, so considering the fact that I have also changed some default settings there are many other diffs in this file than simple "attribute difs".
As a last result, diff tool works, but it is a bit painful, so I was really hoping for something extra like "add missing config attributes " task (I would be nice to have).
Anyway. Which change log you refer to? This one is empty 🤔
So regarding https://arturbosch.github.io/detekt/changelog.html

so considering the fact that I have also changed some default settings there are many other diffs in this file than simple "attribute difs"

You should compare the unmodified default default-detekt-config.yml of RC15 and RC16 for example. This is easier than comparing your modified file with the config file of a newer version.
As I suggested building upon a default config also helps to solve this issue.
I refer to the following change log. It lists all changes.
https://arturbosch.github.io/detekt/changelog-rc.html

As a last result, diff tool works, but it is a bit painful, so I was really hoping for something extra like "add missing config attributes " task

That's not as easy to do as it might sound. Furthermore, I don't think messing with the users config is worth the effort.

Thanks a lot for help 👍

You're welcome.


Split to make ambertools agnostic base package

Checklist

[X] Used a personal fork of the feedstock to propose changes
[X] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[X] Ensured the license file is being packaged.

This PR splits the package into openff-fragmenter-base and openff-fragmenter whereby the base package does not depend on AmberTools while the full package does. The base package is require to install certain fortran packages from other channels (e.g. psi4) that conflict with ambertools

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender


Release v0.6.0

Codecov Report

Merging #44 (b701b0b) into master (2de8e28) will decrease coverage by 1.16%.
The diff coverage is 49.25%.

@@            Coverage Diff             @@
##           master      #44      +/-   ##
==========================================
- Coverage   59.27%   58.11%   -1.17%
==========================================
  Files           6        6
  Lines         582      647      +65
==========================================
+ Hits          345      376      +31
- Misses        237      271      +34

Impacted Files
Coverage Δ

hn2016_falwa/oopinterface.py
81.52% <49.25%> (-7.97%)
:arrow_down:

Continue to review full report at Codecov.

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


Release Google.Cloud.Firestore.Admin.V1 version 2.3.0

Changes in this release:

Commit ac367e2: feat: Regenerate all APIs to support self-signed JWTs

Created release for Google.Cloud.Firestore.Admin.V1-2.3.0


First draft of 'shame' report.

This report is intended to be sent as an email. The purpose is to shame people into fixing the flaky tests they own.
Still a bit of a WIP.
Run with the command $ ./mungegithub --token-file=$HOME/lavalamp-github-token --issue-reports=shame
It outputs:
To: dawnchen@google.com,karl@mesosphere.com,madhusudancs@gmail.com,pmorie@redhat.com,quinton<EMAIL_ADDRESS>Missing addresses for: ArtfulCoder, bprashanth, brendandburns, davidopp, fgrzadkowski, gmarek, ixdy, jdef, mikedanese, piosz, wojtek-t
Subject: Kubernetes flaky Test Report: 38 flaky tests

If you are in the To: line of this email, you have flaky tests to fix! Flaky
tests, even if they flake only a small percentage of the time, cause the merge
queue to become very long, which causes everyone on the team pain and
suffering.  Please either fix the tests assigned to you or find them an owner
who will fix them.

There were 11 P2/P3 issues which are not reported here.

Full report:
ArtfulCoder:
  [P0] 13818: "flaky/broken e2e: Services should be able to change the type and nodeport settings of a service" (71 days)

UNASSIGNED:
  [P1] 10300: "Lack of visibility/attention to shippable/travis flakes may be hiding real bugs" (1.5e+02 days)
  [P1] 12765: "Flakey Test: Monitoring - should verify monitoring pods and all cluster nodes are available on influxdb using heapster. " (98 days)
  [P1] 13515: "GKE upgrade e2e tests leaking target pools, forwarding rules, and firewall rules" (79 days)
  [P1] 14370: "Document how to write good tests" (59 days)
  [P1] 14691: "oidc.TestOIDCDiscoverySecureConnection Flaky" (53 days)
  [P1] 15381: "Services should work after restarting apiserver flake" (42 days)
  [P1] 16308: "PD E2E Tests could leak PDs in some failure scenarios" (25 days)
  [P1] 17018: "Flaky: k8s.io/kubernetes/pkg/controller/framework_test.TestUpdate" (11 days)
  [P1] 9121: "Flaky test: TestUpgradeResponse" (1.7e+02 days)

UNPRIORITIZED:
  [??] 14931: "cni.TestCNIPlugin flake" (50 days)
  [??] 15412: "[mesos/docker] Flakey Smoke Test - TLS handshake timeout" (42 days)
  [??] 15413: "[mesos/docker] Flakey Smoke Test - provided IP is already allocated" (42 days)
  [??] 15872: "Flaky: Kubectl client Guestbook application should create and stop a working application" (32 days)
  [??] 17181: "exec.TestSelectPlugin is flaky" (8 days)
  [??] 17256: "Flaky Service test in per-PR jenkins" (7 days)
  [??] 17332: "unit test TestGenericScheduler is flaky" (4.1 days)

bprashanth:
  [P0] 17518: "Flaky test: Kubernetes e2e suite.GCE L7 LoadBalancer Controller should create GCE L7 loadbalancers and verify Ingress" (1.1 days)

davidopp:
  [P1] 14421: "runSchedulerNoPhantomPodsTest integration flake" (58 days)

dchen1107:
  [P0] 15498: "e2e: Reboot each node by triggering kernel panic and ensure they function upon restart flaky" (39 days)

fgrzadkowski:
  [P1] 14695: "flaky e2e: Network when a minion node becomes unreachable [replication controller] recreates pods scheduled on the unreachable minion node AND allows scheduling of pods on a minion after it rejoins the cluster" (53 days)
  [P1] 14836: "Visibility into gce-reboot failures is poor" (51 days)

gmarek:
  [P0] 15139: "\"SchedulerPredicates validates MaxPods\" e2e test is flaky" (46 days)

ixdy:
  [P0] 16828: "kubernetes-soak-continuous-e2e-gce-1.1 broken on SchedulerPredicates tests" (16 days)

jdef:
  [P1] 11821: "Flaky: TestDQ_always_pop_earliest_deadline_multi" (1.2e+02 days)
  [P1] 11857: "Flaky: TestDQ_always_pop_earliest_deadline" (1.2e+02 days)

madhusudancs:
  [P0] 17521: "Flake: NodeOutOfDisk runs out of disk space" (1.1 days)

mikedanese:
  [P0] 16385: "e2e flake: failed to initialize within 300 seconds" (24 days)
  [P0] 17583: "Flake: Services should work after restarting kube-proxy" (0.091 days)
  [P1] 13764: "pkg/probe/http fails with Go 1.5 or 1.4" (72 days)
  [P1] 14072: "flaky e2e: Daemon set should launch a daemon pod on every node of the cluster" (65 days)
  [P1] 16623: "e2e flake: Daemon set should run and stop complex daemon" (21 days)

piosz:
  [P0] 17584: "Flake: Horizontal pod autoscaling [Autoscaling Suite] should scale from 1 pod to 3 pods and from 3 to 5 (via deployment, with scale resource: CPU)" (0.09 days)
  [P1] 15496: "Initial Resources should set initial resources based on historical data flaky" (39 days)

pmorie:
  [P1] 13690: "soak test failure: Downward API fails to provide pod IP as an env variable after a while" (73 days)

quinton-hoole:
  [P1] 13062: "Label and move slow e2e tests into a separate test job" (91 days)
  [P1] 13828: "Multiple e2e tests fail with \"Namespace x is active\"" (71 days)

wojtek-t:
  [P1] 14899: "TestMaxInFlight is flaky" (50 days)

I won't make all the detailed comments, but at a high level I don't see why this wouldn't be just a normal munger? --once would get you this behavior. --poll=1d would get you something we can run normally.
I know that the argument is --pr-mungers, but that isn't acurate, it's really issue or PR mungers.

I won't make all the detailed comments, but at a high level I don't see why this wouldn't be just a normal munger? --once would get you this behavior. --poll=1d would get you something we can run normally.

The mungers are factored wrong for something that generates a report over a specific set of issues.

I know that the argument is --pr-mungers, but that isn't acurate, it's really issue or PR mungers.

I originally did start it as a munger, but then I noticed that the flag was --pr-mungers, and my spot-checking of existing mungers didn't turn up any that operated on issues.

I'm fine with all that code, after we merge I'll probably redo that boilerplate to make it a munger. But I don't see that as a blocker. Instead it seems like a future simplification.

fixed & pushed

I was going to merge and hack on it myself, but CI fail.
Verifying hack/../hack/verify-golint.sh
FAILED
Verifying hack/../hack/verify-flags-underscore.py
FAILED

Doh! I will look into that later-- I have a big stack of code reviews I need to do.

I'll fix it right now.


Upgrade eslint-plugin-vue to 6.0.0

@michalsnik Now that this PR is approved, could you also release a new version on NPM? I don't have the publish access to this package 😂

Hi, could this be deployed please? It's just a small dependency change that's already been done and is working, it will help in regards to the acorn vulnerability that has been fixed in the newer 6.2 release.


User Story: As a user I want to be able to mark other user feedback as 'helpful' or 'unhelpful'

Currently on the mock-up, it looks like this is set up as a score from 1-10, I think it would be better as just a thumbs up or thumbs down


Add exercise 11

This PR will add exercise set 11.
Binder: https://mybinder.org/v2/gh/andersle/chemometrics/add_exercise_11

LGTM, merging


Add license file

every repo requires a license file
this is the default very permissive MIT license (from a GitHub template) with no modifications

thanks for the nudge @broeder-j   In fact I fully agree with you (no code or docs should be placed on GitHub without a license).  Will talk to the team ASAP.

I approve the merge @jmckenna @arnounesco - the MIT License is fine with me (note virality of license)

merging this now, as it can always be changed later if need be.


ERROR in ./.nuxt/cloudinary/plugin.client.js

I'm on Nuxt version 2.11.0 and I get this error:
 ERROR in ./.nuxt/cloudinary/plugin.client.js Module not found: Error: Can't resolve './cloudinary-api' in '/app/.nuxt/cloudinary'
Looking at my .nuxt folder, and I see the structure like this:
There is an issue with the cloudinary-api js file being placed in the root rather than the cloudinary folder

same here
@mayashavin

@keng0o @genu That's weird. Which version are you using? The latest?

@mayashavin I used the latest cloudinary module, and Nuxt 2.11.0 and this issue occurs.
This issues doesn't occurs, however, in newer versions of Nuxt. (I can't say for sure which version of Nuxt it starts working)
The issue may be that there is a possible API change in older Nuxt versions resulting in this weird behavior. Maybe add a fix for that, or put a minimum Nuxt version requirement.
Are you able to reproduce this at all?

@genu I tried Nuxt < 2.11 and it did happen. So yeah, it looks like something about the Nuxt API changes for earlier version. I will add a minimum Nuxt version requirement for now and see if we can add a fix without too much hassle :). Thanks

Ok, there is a change in convention from 2.13 onwards, where fileName becomes filename 😅. A fix will be on the way :)


Feature/delegation fees config

weeeep

Codecov Report

Merging #457 into master will decrease coverage by 0.12%.
The diff coverage is 18.18%.

@@            Coverage Diff             @@
##           master     #457      +/-   ##
==========================================
- Coverage   63.84%   63.71%   -0.13%
==========================================
  Files          53       53
  Lines        4107     4115       +8
==========================================
  Hits         2622     2622
- Misses       1485     1493       +8

Impacted Files
Coverage Δ

src/relay/blockchain/delegate.py
88.23% <ø> (+0.73%)
:arrow_up:

src/relay/config/schema.py
76.55% <18.18%> (-4.93%)
:arrow_down:

Continue to review full report at Codecov.

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


Allow one.vm.updateconf in cloud view

Description
Sunstone cloud view doesn't have an option for updating the VM Conf section when the section is enabled. Other views have it. If you force it by adding it to the yaml file and restart Sunstone, it adds a button, however the button is not functional.

Use case
Allow end users to reset their VM password.
Interface Changes
Make the button functional
Additional Context
In user.yaml the option is located under the vms-tab identation. In cloud.yaml the action would be located under provision-tab

Progress Status

[x] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

@tinova PRs to be approved:

Code: https://github.com/OpenNebula/one-ee/pull/1737
Conf files: https://github.com/OpenNebula/one-ee/pull/1738
Docs: https://github.com/OpenNebula/docs/pull/2128


Problem with xmlrpc_encode_request

Hello
After installing your extension i have the following error : Call to undefined function
HieuLe\WordpressXmlrpcClient\xmlrpc_encode_request() at line 823
if (!$this->_endPoint)
{        echo $this->_endPoint;exit();
        $this->_error = "Invalid endpoint " . json_encode(array('endpoint' => $this->_endPoint, 'username' => $this->_username, 'password' => $this->_password));
        $this->_logError();
        throw new \Exception($this->_error);
    }
    $this->_responseHeader = array();
    $this->_setXmlrpcType($params);
    $this->_request        = xmlrpc_encode_request($method, $params, array('encoding' => 'UTF-8', 'escaping' => 'markup'));
    $body                  = "";
    // Call sending event callbacks
    $callbacks = $this->_getCallback('sending');

Also when you look at php they do not recommend to use as it s still experimental. Do you have any tips to solve ? I use mamp php version 5.5.10 with apache
i tried to install /Applications/MAMP/bin/php/php5.5.10/bin/pear install XML_RPC successfully but still get my error.

Can you double check if XMLRPC php extension is loaded?
Create file info.php and run it in your browser:
<?php
echo 'XMLRPC is ', extension_loaded('xmlrpc') ? 'loaded' : 'not loaded';

Without `xmlrpc` extension is not possible to run this plugin, since it's used to communicate between Wordpress and Yii2.

`yii2-wordpress` is wrapper for https://github.com/letrunghieu/wordpress-xmlrpc-client which requires xmlrpc.

So if it's not installed, maybe check this discussion:
http://stackoverflow.com/questions/2031564/php-xmlrpc-extension-and-mamp
Also if XMLRPC is installed by pear and still is not loaded, all you may need is to add
extension=xmlrpc.so

to your php.ini and restart mamp.

Hi,
After installing extension im getting following error, and as per ur suggestion I have cross checked that XMLRPC is loaded in my localhost.
How to use this please explain asap.
PHP Fatal Error – yii\base\ErrorException
Class 'HieuLe\WordpressXmlrpcClient\WordpressClient' not found

in D:\xampp\htdocs\yii2\vendor\monitorbacklinks\yii2-wordpress\Wordpress.php at line 207
198199200201202203204205206207208209210211212213214215216        }
if (!is_array($this->proxyConfig)) {
throw new InvalidConfigException("Class "{$className}" requires "$proxyConfig" to be given in array format.");
}
if (!is_array($this->httpAuthConfig)) {
throw new InvalidConfigException("Class "{$className}" requires "$httpAuthConfig" to be given in array format.");
}
 // Create API client
 $this->_clientInstance = new WordpressClient($this->endpoint, $this->username, $this->password);
 $this->_clientInstance->setProxy($this->proxyConfig);
 $this->_clientInstance->setAuth($this->httpAuthConfig


Test on smallNORM with parameters specified in the paper have very bad result

Thanks for posting the code!
I tried your code on smallNORM dataset with the parameter specified in the paper: A=64 B=8 C=D=16, routing iteration = 3, batch_size = 64 (set the number myself). But the result is very bad (cannot even converge). However in the paper the author said the accuracy should be 97.8%.  I am wondering why it is so sensitive to how many capsules in A and also routing iterations?
And could the author post more testing result with different number of capsules/ routing iteration/ learning rate/ batch size etc.
Thank you very much!

Facing a similar issue. In the initial runs, the result  was quite bad with the smallNORB.  After trying multiple runs, I was able to get a decent accuracy. I got similar huge variance in the training runs for MNIST. @www0wwwjs1 do you know what might cause this much variance?

Because the test script doesn't read the latest training parameters, it reads the whole models saved starting from the first iteration, hence the first training parameters will have a terrible accuracy, try using the latest training parameters only, the output should be stable.

Has anyone here had similar results to me on smallNORB? Images for output are in issue #30 This is just the training loop.

I also get very poor performance when using 3 iterations on smallNORB. The model failed to learn anything after almost 30k iterations. Any suggestions?


compiler fails and stops if a plugin calls callback with error

Do you want to request a feature or report a bug?
Report a bug

What is the current behavior?
Compiler stops if a plugin calls callback with error.
If the current behavior is a bug, please provide the steps to reproduce.
webpack.config.js:
class Foo {
  constructor() {
    console.log("Foo");
  }

  apply(compiler) {
    compiler.plugin("after-emit", (compileation, callback) => {
      callback(new Error("foo"));
    });
  }
}

class Bar {
  constructor() {
    console.log("Bar");
  }

  apply(compiler) {
    compiler.plugin("done", (stats) => {
      console.log("Bar done");
    });

    compiler.plugin("fail", (error) => {
      console.log("Bar fail");
    });
  }
}

module.exports = {
  entry: "./app.js",
  output: {
    filename: "bundle.js"
  },
  plugins: [
    new Foo(),
    new Bar()
  ]
};

app.js:
console.log("hello");

What is the expected behavior?
done and/or fail in Bar called.
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
$ node -v
v6.9.2
$ node_modules/.bin/webpack -v
2.2.1
$ npm -v
3.10.10
$ uname -a
Darwin L-SB8H1M2G8W-M.local 16.0.0 Darwin Kernel Version 16.0.0: Mon Aug 29 17:56:20 PDT 2016; root:xnu-3789.1.32~3/RELEASE_X86_64 x86_64

While watching the failed plugin is called.
When calling run or compile the error is passed in the callback.

@sokra is there any reason to not be consistent?

I guess this is intended @jchip, see: https://github.com/webpack/docs/wiki/plugins/ad6ef7e44bec0c2f1a545a5d983a0938966ccaee#failederr-error

while watching failed could be called multiple times. watch just starts the watching.
run and compile are one-time operations, which "return" with success or error.


[Draft] OnRender DisplayName for fetching in component

What

Add onRenderDisplayName for component to:

leverage react reconciliation to update per displayName per component
Allow user to render their own displayName in component level
Allow user to match displayName customization to match custom avatar

Add an example of doing a fetch-and-forget displayName override

Why

How Tested

Process & policy checklist

[ ] I have updated the project documentation to reflect my changes if necessary.
[ ] I have read the CONTRIBUTING documentation.

Is this a breaking change?

[ ] This change causes current functionality to break.

Close this because it is created from a wrong branch


Uncaught RuntimeError: The browser supports WebGL, but initialization failed.

Hello!
I detected an error.
Uncaught RuntimeError: The browser supports WebGL, but initialization failed.
Error
at new t (https://www.webglearth.com/v2/api.js:14:14467)
at new $ (https://www.webglearth.com/v2/api.js:40:4805)
at new pt (https://www.webglearth.com/v2/api.js:48:13213)
at new Y (https://www.webglearth.com/v2/api.js:127:482)
at new  (https://www.webglearth.com/v2/api.js:198:358)
at initialize (https://www.prime-college.ru/globe-frame/:5:157)
at onload (https://www.prime-college.ru/globe-frame/:14:118)

What browser in which version?
What hardware do you use?
If you try a different web browsers on the same hardware do you see the same error?
Have you seen the problem while visiting http://www.webglearth.com/ website?
The page: http://get.webgl.org/ tells you you have WebGL enabled?

Google Chrome 40.0.2214.93 m (latest)
Win 7
Work in Mozilla Firefox
Yes. I have seen the same problem.
I see a cube. It rotates.

This seems to be a problem inside the Cesium itself. To be fixed by #44.


queue processing randomly stops

I have been running beantalkd successfully for many months with no crashes or problems whatsoever. However very recently, I have been getting this issue:
Jobs are added to tubes, beantalkd is running and worker scripts are also running, but for some reason jobs are not being processed. The only fix for this is to restart the workers which are spawned and kills via supervisord.
What could cause a worker that is watching a tube with jobs in it to not process the jobs randomly and create a backlog of jobs?
The workers use the Pheanstalk php library and have worked well for months up to now and there have not been any code changes. There are about 5 tubes doing very different things and they all get hung up together at the same time, the workers are run on several servers with different specs but same OS ubuntu 10.10 so the only common factor between them is Pheanstalk and beantalkd (which is run on one server)
Any insight would be greatly appreciated.

Anyone else having this issue? We have been experiencing this with a couple of our apps now (on different servers). We have no idea what errors to be looking for. It just stops processing jobs. Only way to fix for us is to restart. Running on Ubuntu 14.04. Also using the Pheanstalk library.

What version of beanstalk are you using ? The one from Ubuntu distro ? Because that one is pretty old.
I created a github project to create a deb for the last master from beanstalkd. I personally don't have any issue with the master.
https://github.com/silviucpp/beanstalkd-deb

Also @chrisbjr  what you restarted the server or the workers ? I'm using the erlang client and php one and I didn't found an issue like this( for several months when I integrated bk in my solution) .

I know this question doesn't really belong here, but this is the only place I found the same problem. Did one of you found a solution for this annoying problem?

Hello @gjongenelen ,
I'm using beanstalkd for 3 years in production and processing lot of jobs and never got this issue. You need to describe better your case .. what kind of jobs what libraries are you using... helps if you restart the consumers or problem it's fixed only if server is restarted and so on.
Silviu

Okay, but I'm not really sure if this is a problem with beanstalkd. But here we go anyway:
I have 6 workers running on PHP 7.1 (dockerized), with pda/pheanstalk:3.1.0
The payload of the messages is all JSON.
When I restart the workers, the problem solves itself. But keeps coming back after a few minutes.
I placed some breakpoints and concluded that the workers hang when they enter the watch-command. The stats-tube command shows an increasing amount of current-jobs-ready.
Full output of stats-tube:
current-jobs-urgent: 64
current-jobs-ready: 64
current-jobs-reserved: 0
current-jobs-delayed: 0
current-jobs-buried: 0
total-jobs: 561
current-using: 1
current-watching: 0
current-waiting: 0
cmd-delete: 497
cmd-pause-tube: 0
pause: 0
pause-time-left: 0

After a restart of the workers, I don't see any messages of a invalid job being skipped or something.
I'm thinking about migrating to AWS SQS to quickly solve this problem.

Problem might be caused by a bug into your driver.. on our side we are using an erlang driver for consuming and  the one you mention for producing.
Regarding watch command should be done once.. when you open the connection you register what tubes you want to watch .. you don't call this after single message processed...
Silviu

Hi guys, after desperately trying to figure out how to fix this issue,
Laravel 5.3 came out with "better handling for queues". Specific to this
was the addition of the timeout parameter.
I didn't know if this issue was related to Laravel but I took the risk and
migrated to Laravel 5.3 (originally from 4.2). After a few hours of
migration, I finally had my queues up and running.
I have 20 queues all processing jobs at the same time and the job involves
database transactions and making API calls. Each queue processes around
1,000 jobs per day.
After experimenting with the timeout parameter of Laravel's queues, I have
finally achieved queues that do not freeze anymore.
My suspicion with this is that the API calls I make probably takes a while
sometimes and times out once in a while. And since Laravel didn't handle
timeouts properly in earlier versions, this caused my queues to freeze
without any indication of what went wrong.
Anyway, this proves that my original issue is not with Beanstalkd but
rather the way earlier versions of Laravel handles queues.
I am now very happy that I don't have to monitor my queues everyday and
they have been running without any restarts or interventions from me for
more than 3 months and running now. Very very happy about this.
On Wed, Mar 15, 2017, 11:20 PM Silviu Caragea<EMAIL_ADDRESS>wrote:

Problem might be caused by a bug into your driver.. on our side we are
using an erlang driver for consuming and the one you mention for producing.
Regarding watch command should be done once.. when you open the connection
you register what tubes you want to watch .. you don't call this after
single message processed...
Silviu
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kr/beanstalkd/issues/148#issuecomment-286775420, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAi3j4OulsZmNjm8qMzesyKTg7EJ5Sx0ks5rmAG_gaJpZM4ANTdw
.

I have just deployed a hotfix which uses AWS SQS. Tomorrow I will investigate the issues with beanstalkd.


yaml arrays are not supported for secrets

I updated my brigade project to send a particular secret as an array like so:
project: "buildasign/designer"
...
secrets:
  environments:
    - name: dev
      serverName: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      databaseName: "xxxxxxxxxxxx"
      userName: "xxxxxxxxxx"
      password: "xxxxxxxxxxxxxxxxx"
...

and we get the following error from brig CLI. The build does not kick off either in k8s. I assume Go is blowing up internally before creating the worker with the same error.
λ brig project get buildasign/designer -n brigade
Error: json: cannot unmarshal array into Go value of type string
Usage:
  brig project get PROJECT [flags]

Global Flags:
      --kubeconfig string   The path to a KUBECONFIG file, overrides $KUBECONFIG.
  -n, --namespace string    The Kubernetes namespace for Brigade (default "default")
  -v, --verbose             Turn on verbose output

json: cannot unmarshal array into Go value of type string

This secrect should be JSON.stringify'd and then passed around as a string.
e.g. environments: "[{\"name\": \"dev\", \"serverName\": \"xxx\", ...}]"

I'll have to check whether there was some reason this was done by design, but it seems to be a bug.

Closing this in favor of #486, which offers some more context.
Feel free to comment there, or reopen if this is actually another issue.
Thanks!


Fix auto.sh script

Description
There was a small type in the auto.sh script where instagram command was being used for the brute-force attack instead of the expected instagram-py as seen in the manual.sh script which seems to work fine. This PR updates all the instances of the wrong command to the expected command to get the desired results for the end user.
Fixes issue #2

Ok I fixed it
On Tue, Feb 23, 2021, 9:37 PM Souhit Dey<EMAIL_ADDRESS>wrote:

Description
There was a small type in the auto.sh script where instagram command was
being used for the brute-force attack instead of the expected instagram-py
as seen in the manual.sh script which seems to work fine. This PR updates
all the instances of the wrong command to the expected command to get the
desired results for the end user.
Fixes issue #2
https://github.com/Hackertrackersj/Instabruteforce/issues/2
You can view, comment on, or merge this pull request online at:
https://github.com/Hackertrackersj/Instabruteforce/pull/4
Commit Summary

Fix auto.sh script

File Changes

M auto.sh
https://github.com/Hackertrackersj/Instabruteforce/pull/4/files#diff-6831790917c6357fcdd817b73d410954a67eb6c17db54159e4d1fcd371a04d53
(6)

Patch Links:

https://github.com/Hackertrackersj/Instabruteforce/pull/4.patch
https://github.com/Hackertrackersj/Instabruteforce/pull/4.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Hackertrackersj/Instabruteforce/pull/4, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APTJOWU32CRWRUIEASK7VNLTAPHENANCNFSM4YCYDCVA
.

Shall I close the PR in favor of your latest changes then?

Description
There was a small type in the auto.sh script where instagram command was being used for the brute-force attack instead of the expected instagram-py as seen in the manual.sh script which seems to work fine. This PR updates all the instances of the wrong command to the expected command to get the desired results for the end user.
Fixes issue #2

Still dont work for me, tried to Update and change it manually. Instagram to instagram-py

@w0LFzk1nD please share your logs if possible would help a ton in debugging the real cause of the issue.

@w0LFzk1nD please share your logs if possible would help a ton in debugging the real cause of the issue.

It just says 'instagram-py: command not found'
I made Update And i changed the 3 lines u mentioned manually.

@w0LFzk1nD Check the readme section where instagram-py talks about it's usage. This is the command to start the brute force attack:
usage: instagram-py [-h] [--username USERNAME] [--password-list PASSWORD_LIST]
                    [--script SCRIPT] [--inspect-username INSPECT_USERNAME]
                    [--create-configuration] [--default-configuration]
                    [--countinue] [--verbose]

With respect to that, instagram-py should work as expected when edited into the script.
I think you should try pip3 install instagram-py before running the script this is a line from the setup script maybe you missed it?

@w0LFzk1nD Check the readme section where instagram-py talks about it's usage. This is the command to start the brute force attack:
usage: instagram-py [-h] [--username USERNAME] [--password-list PASSWORD_LIST]
                    [--script SCRIPT] [--inspect-username INSPECT_USERNAME]
                    [--create-configuration] [--default-configuration]
                    [--countinue] [--verbose]

With respect to that, instagram-py should work as expected when edited into the script.
I think you should try pip3 install instagram-py before running the script this is a line from the setup script maybe you missed it?

I tried to run this command, but pip3 somehoe does not work. Command not found and i cant find the reason or a solution for that :/ but pip3 should be working... Right?

Ok i managed to get it done :)
But now i am facing another problem after choosing the option for the amount.
[#] Enter Selected Number: 1
Instagram-Py 2.0.7 ,  Slick Instagram brute force command line tool.
Copyright (C) 2018 The Future Shell , Antony Jr.
[+] Started @ 2021-02-25 21:28:36.238068
fatal error:: Tor configuration invalid or server down :: [Errno 111] Connection refused
But Tor is installed and running in another shell/session.

@w0LFzk1nD try using Orbot to re-route all of your device's  network traffic via tor and give it a try again and tell me how it behaves.

@OBITORASU
Mh now i get this Message
[+] Started @ 2021-02-26 05:14:19.486719
fatal error:: Tor configuration invalid or server down :: unable to use the control socket
Pkg torsocket(s)
Is installed and i enabled bridges.

@w0LFzk1nD  refer to this issue https://github.com/deathsec/instagram-py/issues/8

@w0LFzk1nD  refer to this issue https://github.com/deathsec/instagram-py/issues/8

Okey, i kinda got it working. There is no Error showing up after choosing the option now. But now, it remains empty, should there be any other output or nothing? :)

@w0LFzk1nD  refer to this issue deathsec/instagram-py#8

Okey, i kinda got it working. There is no Error showing up after choosing the option now. But now, it remains empty, should there be any other output or nothing? :)

Add the -v flag at the end of all occurances of instagram-py and you should see relevant output, by default this script is not verbose.
Heres a reference:
(Current)
instagram-py --username $usrnm --password-list $HOME/Instabruteforce/pass1.txt
(What I suggested)
instagram-py --username $usrnm --password-list $HOME/Instabruteforce/pass1.txt -v

@w0LFzk1nD  refer to this issue deathsec/instagram-py#8

Okey, i kinda got it working. There is no Error showing up after choosing the option now. But now, it remains empty, should there be any other output or nothing? :)

Add the -v flag at the end of all occurances of instagram-py and you should see relevant output, by default this script is not verbose.
Here is a reference:
(Current)
instagram-py --username $usrnm --password-list $HOME/Instabruteforce/pass1.txt
(What I suggested)
instagram-py --username $usrnm --password-list $HOME/Instabruteforce/pass1.txt -v

Okey! I will try that when i got time! Thanks a lot for the help and support.
Note: i want to use it in ethical way! A friend of mine got 'a stalker' and i want to help him a bit.

Try -vvv instead of -v then

If scripts finishes with exit code 0 it should be working you can check exit code by using this command echo $?, if it is 0 then all good, errors during the run would result in 1.

@OBITORASU
So, i start the App OrBot. Run thw Script and is says 'started and time' then it remains completely quiet.
When i open up the OrBot App and retuen to Termux, it shows the problem, mentioned earlier.
Echo $?
Results 148
I think it wont work out for me then :'/

That means the process is basically running but in the background, you have to foreground it to see whats happening. Backgrounding and foregrounding looks something like this.

That means the process is basically running but in the background, you have to foreground it to see whats happening. Backgrounding and foregrounding looks something like this.

Yeah! It is working! Thank you very muchos gracias :P

@OBITORASU
Ok now i have another small question :)
Does the
Imp-seq
Show the Attempt/Number of the password it tried?
Bcs i got confused, afzer choosing the 1k password option, and seeing this number go over 1000 :)
Should be the last comment here :)
If there's anything else, ill put it in the edit here.

Share a snippet of how it looks like (this output you are talking about) I will check in the main repo and report back :)

Share a snippet of how it looks like (this output you are talking about) I will check in the main repo and report back :)

Exactly the output that you showed on the screenshot :)

That 1k password txt file has slightly more passwords than 1k so that might be the reason you saw it going over 1k.

That 1k password txt file has slightly more passwords than 1k so that might be the reason you saw it going over 1k.

But the weird thing is, i made the account with one of the pw in the list. But somehow, it wasn't able or didn't show up that it found it. :/ ill do some testing later on :3

That 1k password txt file has slightly more passwords than 1k so that might be the reason you saw it going over 1k.

So, what happend.
I started the auto option and it started it for 1k. I left the device running for a while, but checked a fee times.
I had 2 sessions open.
The skript
And the ping <IP_ADDRESS>
The skript did not change, after it said that it started.
The ping  was running and counting.
When the ping hit around 1800 (in your screenshot u see a number, that is going 1,2,3,4,5...), it showed the options at the skript again for auto/manuell/etc
When i exit out, and type echo $?
It says 1
Additional, i chose one of the passwords, that where one of thr first in the pass1.txt list
I am probably doing something wrong here :/

That 1k password txt file has slightly more passwords than 1k so that might be the reason you saw it going over 1k.

So, what happend.
I started the auto option and it started it for 1k. I left the device running for a while, but checked a fee times.
I had 2 sessions open.
The skript
And the ping <IP_ADDRESS>
The skript did not change, after it said that it started.
The ping was running and counting.
When the ping hit around 1800 (in your screenshot u see a number, that is going 1,2,3,4,5...), it showed the options at the skript again for auto/manuell/etc
When i exit out, and type echo $?
It says 1
Additional, i chose one of the passwords, that where one of thr first in the pass1.txt list
I am probably doing something wrong here :/

Don't worry about what that ping is doing those numbers in the screenshot have nothing to do with this script, it was just a demo to show how backgrounding and foregrounding looks like. If the script took you back to its home menu and the exit code the run was 1 then it should mean it failed to find the password.


[SR SQL Planner Summer Camp] Support ShowTransactionStmt for new parser #7962

What type of PR is this：

[ ] BugFix
[ ] Feature
[ ] Enhancement
[x] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：
Fixes #7962
Problem Summary(Required) ：
Support ShowTransactionStmt for new parser #7962
Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

[FE PR Coverage Check]
:disappointed: fail : 2 / 10 (20.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
0
7
00.00%
[3086, 3087, 3088, 3091, 3092, 3093, 3096]

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[157]

:large_blue_circle:
com/starrocks/analysis/ShowTransactionStmt.java
2
2
100.00%
[]

is it failed? how should i change my code

Lack of the relevant logic of analyze in the original code


feat: publish artifacts: json-ld context and json schemas on gh-pages

WHAT

Verify artifacts before publishing
Publishes resources under artifacts/src/main/resources in resources/v0.8 folder when publishing to gh-pages
removes artifacts folder from the gh-pages artifact

Relates #63
How was the issue fixed?
Briefly state why the change was necessary.
More context
List other areas that have changed but are not necessarily linked to the main feature. This could be naming changes,
bugs that were encountered and were fixed inline, etc.

/cc @arnoweiss


Set entity_category for generated switches to 'config'

As per documentation the integration creates 4 switches:

switch.adaptive_lighting_living_room
switch.adaptive_lighting_sleep_mode_living_room
switch.adaptive_lighting_adapt_brightness_living_room
switch.adaptive_lighting_adapt_color_living_room

I think it is nice if the last 3 switches (sleep_mode, adapt_brightness and adapt_color) are of entity_category: config
These switches are used to configure the integration, and do not need to show up on my main dashboard.
More info here: https://developers.home-assistant.io/docs/core/entity/#generic-properties
Solution might be something like this. Add the following line to switch.py line 1003:
self.entity_category = "config"
Thanks!

Thanks for the headsup. I moved this to the todo list for version 2, as version 1 is in feature freeze.

Hey @stefanroelofs,
this is now part of the Roadmap for Version 2.
Feel free to vote on the point which will fix this:
https://github.com/basnijholt/adaptive-lighting/discussions/291#discussioncomment-2946844

@stefanroelofs Hi @stefenroelof,
I was trying to implement this request into the integration and ran into a few questions I could have clarified further, my apologies! I indeed did read your original post
I don't quite understand what entity_category does or exactly the ramifications of changing it to config when considering existing systems.
from the docs you listed:

Classification of a non-primary entity. Set to config for an entity which allows changing the configuration of a device, for example a switch entity making it possible to turn the background illumination of a switch on and off. Set to diagnostic for an entity exposing some configuration parameter or diagnostics of a device but does not allow changing it, for example a sensor showing RSSI or MAC-address.

I'd rather switches aren't disappearing from lovelace dashboards unnecessarily in use cases where users are expecting it to be there.
Additionally I don't know why you can't just use this option:

Thank you for your suggestion

Hi, thanks for your response, and I understand your reservations.
The entire reason for my suggestion is to make the switches disappear from my (auto-generated) Lovelace dashboard.
I think the 3 switches are used to configure the integration, and I don't need to see them on my dashboard.
If I mark the entities as 'Hidden', they are also hidden in the Settings view. Not exactly what I like.
Anyway, it's up to you. Good luck!


Query Builder

Smart Query Builder Story: https://openshift.io/openshiftio/Openshift_io/plan/detail/383

[test]

[test]

@sahil143 is this ready for review or are there still changes being made?

[test]

[test]

@sahil143 Your image is available in the registry. Run docker pull quay.io/openshiftio/fabric8-ui-fabric8-planner:SNAPSHOT-PR-2806 && docker run -it -p 5000:8080 quay.io/openshiftio/fabric8-ui-fabric8-planner:SNAPSHOT-PR-2806 and visit http://localhost:5000 to access it.

@sahil143 I get this error whenever the query is incorrect. It's very intrusive. An error message below the input would probably be better.

That being said, when the query is correct it seems to work as expected.
There's also some oddities with the content assist when the cursor isn't at the end of the input.

When I press enter and the query completes, focus is lost from the input. I would expect focus to remain in the query input field.

Sometimes pressing enter executes the query and sometimes it performs an auto complete. It's confusing and often messes up the query. Worst part is that after the query gets messed up I cannot simply press cmd+z to undo, because it doesn't undo the auto complete entry.

Got the following error when clicking on a query item to go to the details and then pressing the back button:
ERROR Error: ExpressionChangedAfterItHasBeenCheckedError: Expression has changed after it was checked. Previous value: 'ngIf: false'.  Previous value: 'ngIf: false'. Current value: 'ngIf: true'.
View_PlannerQueryComponent_0 | @ | PlannerQueryComponent.html:22

Fixed in latest commit

Sometimes pressing enter executes the query and sometimes it performs an auto complete

When suggestion dropdown is open pressing enter auto completes the query and when dropdown is close pressing enter executes the query

Worst part is that after the query gets messed up I cannot simply press cmd+z to undo, because it doesn't undo the auto complete entry.

Solution for this would be to keep our own history(ctrl z) for query input field?

When I press enter and the query completes, focus is lost from the input. I would expect focus to remain in the query input field.

This is intended behaviour but I dont see why we can't focus on input after pressing enter. Fixed in latest commit

I get this error whenever the query is incorrect. It's very intrusive. An error message below the input would probably be better.

We dont have query validator which can validate the query. We send the api request for invalid queries and when backend throws error we show this notification error. Also, Area below input has other text. Adding error below input field would disrupt the experience. WDYT?
@christianvogt ^^

@sahil143 Your image is available in the registry. Run docker pull quay.io/openshiftio/fabric8-ui-fabric8-planner:SNAPSHOT-PR-2806 && docker run -it -p 5000:8080 quay.io/openshiftio/fabric8-ui-fabric8-planner:SNAPSHOT-PR-2806 and visit http://localhost:5000 to access it.

@christianvogt is this ready to be merged?

@sahil143 there's something wrong w/ the auto complete and the enter key. After entering in the value, pressing enter again replaced my value with the field again. I would expect the query to be issued at this point when pressing enter.

@sahil143 Your image is available in the registry. Run docker pull quay.io/openshiftio/fabric8-ui-fabric8-planner:SNAPSHOT-PR-2806 && docker run -it -p 5000:8080 quay.io/openshiftio/fabric8-ui-fabric8-planner:SNAPSHOT-PR-2806 and visit http://localhost:5000 to access it.

@sahil143 Your image is available in the registry. Run docker pull quay.io/openshiftio/fabric8-ui-fabric8-planner:SNAPSHOT-PR-2806 && docker run -it -p 5000:8080 quay.io/openshiftio/fabric8-ui-fabric8-planner:SNAPSHOT-PR-2806 and visit http://localhost:5000 to access it.

@sahil143 Your image is available in the registry. Run docker pull quay.io/openshiftio/fabric8-ui-fabric8-planner:SNAPSHOT-PR-2806 && docker run -it -p 5000:8080 quay.io/openshiftio/fabric8-ui-fabric8-planner:SNAPSHOT-PR-2806 and visit http://localhost:5000 to access it.

@sahil143 Your image is available in the registry. Run docker pull quay.io/openshiftio/fabric8-ui-fabric8-planner:SNAPSHOT-PR-2806 && docker run -it -p 5000:8080 quay.io/openshiftio/fabric8-ui-fabric8-planner:SNAPSHOT-PR-2806 and visit http://localhost:5000 to access it.


HARP-4545: Implement animated extrusion of the buildings

@heremaps-bot ok to test

@heremaps-bot ok to test

Forgot to write why I am requesting changes while my 2 comments are minors: as sent in DM, there is a bug that appears in the rendering sometimes, I haven't identified where it comes from though. It needs to be ironed out before merging.


Pop to the first actual context when resolving rootpath - fixes #2026

Description of the pull request:
This adds a step to @rootpath resolution that pops to the first non-empty (keypath-wise) context to get the keypath. Here's the example:
{{#with foo.bar.baz.bat}}<cmp>{{@rootpath}}</cmp>{{/with}}

Without this, the result is an empty string, and with it, the result is foo.bar.baz.bat. So, with node info helpers on the event object, you can get the root path to the event context with event.resolve('@rootpath').
Fixes the following issues:
#2026
Is breaking:
Shouldn't be.

awesome!! I think this will allow me to do something in a decorator I previously couldn't: resolve the keypath correctly from inside a loop instead of having to pass the value directly to the decorator. excellent!!

Sounds like info.resolve('..') could help in that case too. In an iteration, that would give you the path to the list being iterated. Any template refs can now be resolved in code with that resolve method, so ../../foo would work as you would expect too.


Update README.md file

The current description of usage CLI isn't actual for develop branch. Please, update it.

:tada: This issue has been resolved in version 1.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[GA Version] GA version need to update with latest version

Current GA version is 2.4, which need to upgrade to 2.5, dev and other environment can use the latest 2.5 version.

Updated GA to 2.5


Actions - state updating for different actions files

Consider Action1.ACTION_NAME and Action2.ACTION_NAME, whenever their are 2 actions and 2 different reducers for each action, and i want to update by dispatching to (Action2.ACTION_NAME) the dispatch is updating both the actions  (Action1.ACTION_NAME and Action2.ACTION_NAME) and the state gets changed.

The issue tracker here on GitHub is reserved for bug reports and feature requests. For usage questions (which is what I believe this is), please use Stack Overflow or Reactiflux where there are a lot more people ready to help you out. Thanks!
Please feel free to reply if you think this issue was closed prematurely.


Istio Operator 1.5.1 creates ingressgateway despite flag false

Bug description
Despite the following IstioOperator manifest:
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
metadata:
  name: istio-control-plane
  namespace: istio-system
spec:
  profile: default
  addonComponents:
    prometheus:
      enabled: false
  values:
    global:
      k8sIngress:
        enabled: false

IstioOperator is creating the Gateway object named: ingressgateway in the istio-system namespace.
Expected behavior
IstioOperator should not create the ingressgateway Gateway object as per default profile in IstioOperator.
Steps to reproduce the bug
Install istio operator:
$ helm template install/kubernetes/operator/operator-chart/ \
  --set hub=docker.io/istio \
  --set tag=1.5.1 \
  --set operatorNamespace=istio-operator \
  --set istioNamespace=istio-system | kubectl apply -f -

Apply IstioOperator chart:
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
metadata:
  name: istio-control-plane
  namespace: istio-system
spec:
  profile: default
  addonComponents:
    prometheus:
      enabled: false
  values:
    global:
      k8sIngress:
        enabled: false

And then this will happen, while no gateway should have been created.
kubectl get gateway -n istio-system
NAME             AGE
ingressgateway   49s

Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
istioctl version --remote
client version: 1.5-alpha.da2d49ef041ea6b82d5da506d9f25676a1795646
control plane version: 1.5.1
data plane version: 1.5.1 (3 proxies)

 kubectl version
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.4", GitCommit:"8d8aa39598534325ad77120c120a22b3a990b5ea", GitTreeState:"clean", BuildDate:"2020-03-12T23:40:44Z", GoVersion:"go1.14", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.5", GitCommit:"20c265fef0741dd71a66480e35bd69f18351daea", GitTreeState:"clean", BuildDate:"2019-10-15T19:07:57Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}

Helm N/A
How was Istio installed?
Istio Operator, please see above.
Environment where bug was observed (cloud vendor, OS, etc)
docker-for-desktop

k8sIngress refers to whether handinlg of the kubernetes Ingress object is enabled, not about whether a gateway is deployed

Okay, but, given the default profile for the IstioOperator chart, is that normal that the following gateway is created?
I've been using quite extensively with Istio 1.4.x and it's the first time I see this gateway being created from a fresh istio install.
kubectl get gateway -n istio-system
NAME             AGE
ingressgateway   49s

If it is, how can I prevent this from being created?

Sorry I read the issue wrong. That's isn't a way to disable it currently but as have removed this on master https://github.com/istio/istio/pull/22223. I'm a bit concerned about backporting to 1.5 as it could break some folks when they upgrade potentially

ah ok, so will this be fixed in the next (minor?) release?

This seems to be fixed. Is there a way I can point to the new manifests from the IstioOperator chart with version 1.5.1?


BaseFrame causes issues when the type is Record<string, unknown>

When you use the default type Record<string, unknown> this causes issues for nested frames.
So let's say I dezerialize an SD-JWT ey123.ey123.ey123~123~456~ into a sd-jwt the types for Header and Payload will be Record<string, unknown>.
If I now want to do create a presentation frame (or disclosure frame, they're based on the same base frame) it will result in errors If I use a nested object:
{
   // errors as 'nested' key is expected to have boolean | undefined value
   nested: {
    claim: true
  }
}

I think when we don't know the value of something (= unknown) we should not say the value should be boolean, but rather it can be an array with booleans an objects with new key values or a boolean, as we don't know the structure of the object

I think that makes sense, yeah. When I designed the API I think I had the issuer mainly in my mind, which does not encounter this issue as the type of the payload is always complete. But from the holder or verifier, some of the values might be in the disclosure array.

I had the issuer mainly in my mind, which does not encounter this issue as the type of the payload is always complete

Not necessarily if the payload is passed dynamically (think over rest api).


Can''t import png files

Tested versions
4.2.2 and 4.2.1
System information
Windows 11
Issue description
When i try to import a png file, it loads a
Steps to reproduce
Importing a png file
Minimal reproduction project (MRP)
MRP.zip

"When i try to import a png file, it loads a" ?

Please add more details, you should explain what isn't working and what happens instead, and what you expect to happen instead

PNG is too large, maximum texture size is 16384x16384 and your PNG is 16599x4114.

Consolidating in:

https://github.com/godotengine/godot/issues/93018

As this is the same issue, see there for more

Ok! Thanks!
El lun, 8 jul 2024 a la(s) 6:34 a.m., bruvzg @.***)
escribió:

PNG is too large, maximum texture size is 16384x16384 and your PNG is
16599x4114.
—
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/94051#issuecomment-2213523337,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJHN6GOSCQMUBOYOJEZ72XLZLJMMFAVCNFSM6AAAAABKPU5X3KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJTGUZDGMZTG4
.
You are receiving this because you authored the thread.Message ID:
@.***>


no lua highlighting

no lua highlighting

OS: Debian GNU/Linux bookworm/sid
Neovim: v0.6.1(Release)

In my usual programming languages, only lua has a problem with syntax highlighting. But I can't see what's the problem.
mini config(init.lua)
require('nvim-treesitter.configs').setup({
        ensure_installed = 'maintained',
        highlight  = { enable = true }
})

You need to open this issue in https://github.com/nvim-treesitter/nvim-treesitter repo. All the highlighting are done by queries in https://github.com/nvim-treesitter/nvim-treesitter.
But from the error message it looks like you need to update the nvim-treesitter plugin and reinstall the lua parser by doing :TSInstall lua.


schemas: remove 'required' properties from jsonschema

previously, missing required properties would lead to generic 500
errors during the upload of metadata for drafts without useful
information
also, the draft would not be saved
this was because during draft creation, marshmallow validation
errors wouldn't lead to an abort, but jsonschema validation errors
would
as per discussion, the role of jsonschema is primarily for basic
structural validation nowadays

removed many of the required fields where there exist such rules in marshmallow
exceptions: the internal PIDs (field pid) because there's no marshmallow equivalent for that, and many of the GEO JSON things, as they're still WIP


Fixes #1: Should not add empty items

It should not save if the value is not defined, or empty.
WDYT @iainreid820?


Add ruby 2.7.0

Signed-off-by: Yuta Iwama<EMAIL_ADDRESS>Which issue(s) this PR fixes:
none
What this PR does / why we need it:
Add ruby 2.7 ci support
Docs Changes:
none
Release Note:
none

Right. I'll use rake 12 becuase it supports ruby 2.1. but now I'm working on fixing other errors https://travis-ci.org/fluent/fluentd/jobs/629558001?utm_medium=notification&utm_source=github_status.

We will drop ruby 2.1/2.2/2.3 support after a few more days.
Waiting it is one approach.

If I couldn't fix the error this year, I'll do so~(I think it's not good to mix adding support and droping support in the same PR).

Tests are passed. I'll merge later https://travis-ci.org/fluent/fluentd/builds/629889073?utm_medium=notification&utm_source=github_status


Error<EMAIL_ADDRESS>

Editet
Color picker not launching.

Hi @mihail-karimov, thank you for the report.
That seems an error messages about wcwhit's extension.
This is "Color Picker for VS Code" repository.

sorry wrong screen and error i'd edited issue. Please check. Thank you.

Could you tell me details, please?
See: https://github.com/anseki/vscode-color/blob/master/.github/ISSUE_TEMPLATE.md
And also, you should not change previous comments with breaking the conversation flow.


Emphasis on introducing component props in tutorial

In the tutorial when introducing social media component at https://docs.astro.build/en/tutorial/3-components/2/#create-a-social-media-component Astro.props was used for the first time. And there was no mention about what are props, how you can pass them to components and how you can access them in the components. The example straight away introduce this concept and encourages user to copy paste the code.
There was a reference to component props basics at the end of the page, but a brief introduction can be given about the component props or link to the basics can be mentioned before beginning of this header https://docs.astro.build/en/tutorial/3-components/2/#create-a-social-media-component so that interested readers can cover the basics to understand what they'll be doing.
The following file is the source code
https://github.com/withastro/docs/blob/main/src/pages/en/tutorial/3-components/2.md

I think this should have been closed by https://github.com/withastro/docs/pull/2023 which added a brief intro about props to 3.2 exactly like you suggest here. I’ll close as done, but if you think there’s anything still missing, let us know!


Added support for 3D transformations

Content view can now be transformed in 3D for the left/right menu.

This git is not updated for a while. What if we created a new git???


Fatal Exception: java.lang.SecurityException

I'm having an issue using Community version of the library
Fatal Exception: java.lang.SecurityException
Must have USE_BIOMETRIC permission: Neither user {userId} nor current process has android.permission.USE_BIOMETRIC.
Currently the app is not using any biometric verification in it, however, I'm having this issue on some devices with Android 12 and Android 13
SDK Version: 7.0.0

Hi @arshakavag92,
I've managed to reproduce this issue. Permissions USE_BIOMETRIC, USE_FINGERPRINT should be merged automatically from your dependencies. If the permission merging is disabled, the SecurityException occurs.
We're going to add a fix that will skip the biometric presence check if the permission is not declared in the manifest. The new release with this bug fix should be available soon. Thank you for reporting this bug.
Best regards,
Talsec Team

Hello @arshakavag92 ,
the issue has been solved in the new version: 8.0.4.
Kind regards,
Talsec team


Off-by-one error in fee calculation

We use sat/kwu and Core uses sats/kvb. Likely because of div by 4 we have an off by one error when calculating the fee from an amount and fee rate.
Question: Why did we choose kwu in FeeRate instead of kvb? Was it to match weight units in Weight?
Proof
These are part of the tests from Core
    feeRate = CFeeRate(123);
    // Rounds up the result, if not integer
    BOOST_CHECK_EQUAL(feeRate.GetFee(0), CAmount(0));
    BOOST_CHECK_EQUAL(feeRate.GetFee(8), CAmount(1)); // Special case: returns 1 instead of 0
    BOOST_CHECK_EQUAL(feeRate.GetFee(9), CAmount(2));
    BOOST_CHECK_EQUAL(feeRate.GetFee(121), CAmount(15));
    BOOST_CHECK_EQUAL(feeRate.GetFee(122), CAmount(16));
    BOOST_CHECK_EQUAL(feeRate.GetFee(999), CAmount(123));
    BOOST_CHECK_EQUAL(feeRate.GetFee(1e3), CAmount(123));
    BOOST_CHECK_EQUAL(feeRate.GetFee(9e3), CAmount(1107));

Which in Rust is this, and it fails with an off-by-one for 122 virtual bytes.
    #[test]
    fn core_get_fee() {
        // Bitcoin Core's GetFee function uses virtual bytes where
        // as we use weight units. Remember `1vb = 4wu`.
        let fee_rate = FeeRate::from_sat_per_kvb(123);

        assert_eq!(fee_rate.fee_vb(0).unwrap(), Amount::ZERO);
        assert_eq!(fee_rate.fee_vb(8).unwrap(), Amount::from_sat(1));
        assert_eq!(fee_rate.fee_vb(9).unwrap(), Amount::from_sat(2));
        assert_eq!(fee_rate.fee_vb(121).unwrap(), Amount::from_sat(15));
        assert_eq!(fee_rate.fee_vb(122).unwrap(), Amount::from_sat(16));
        assert_eq!(fee_rate.fee_vb(999).unwrap(), Amount::from_sat(123));
        assert_eq!(fee_rate.fee_vb(1_000).unwrap(), Amount::from_sat(123));
        assert_eq!(fee_rate.fee_vb(9_000).unwrap(), Amount::from_sat(123));
    }

I wrote this issue instead of just fixing it to discuss the question and make sure we are happy with it.
To close this issue I would expect a bucket load of unit tests be added to the units module. (And likely that they are taken from Core but writing bugs in the unit tests will be easy to do because of the whole kvb vs kwu thing.)

Why did we choose kwu in FeeRate instead of kvb? Was it to match weight units in Weight?

I always use sats/kvb or sats/vb. I can guess we opted for this to maintain maximum precision and to support both from_sat_per_kwu and from_sats_per_pvu. If we were to define FeeRate(u64) in terms of kvb, it would result in a loss of precision when using the from_sats_per_kwu constructor?

I know what you mean :)

Note that currently we have undocumented loss of precision in FeeRate::from_sat_per_kvb

Why did we choose kwu in FeeRate instead of kvb? Was it to match weight units in Weight?

Yes, weight is a more natural unit than vbytes, which is inherently imprecise. But unfortunately "per vbyte" is more precise than "per wu".

Note that currently we have undocumented loss of precision in FeeRate::from_sat_per_kvb

Yeah, I see. This shouldn't happen.
So, we have a couple options:

Just live with it
Change from_sat_per_kvb to round up; or split it into _ceil/_floor methods.
Change the internal repr of FeeRate to be fee/kwu to match Core (and do no better)
Change the internal repr of FeeRate to use a f64 (which will handle integers <= MAX_MONEY and multiplication/division by 4 perfectly)

BTW this whole from_sat_per collection of functions is a bit weird looking. As an independent thing, maybe we want to replace/augment these with FeeRate::per_* methods that just take an Amount?

After reading https://github.com/rust-bitcoin/rust-bitcoin/issues/3807 I am warming up to the f64 solution.
We can add an to_sat_f64 method to Amount/SignedAmount/Weight to avoid casting, and Weight::from_f64_floor and Weight::from_f64_ceil. Then we taboo / 4 and insist that it be / 4.0 (or have a justifying comment). Then all of our conversions will be exact and any loss of precision is made explicit by the use of _floor or _ceil functions.
(In the case of the code quoted in #3807 we might just keep the existing "107 / 4" but we should comment that this is a deliberate truncation and was copied from Core.)

Checked that 123 sat/kvb * 122 vb = 15.006 sats.  Rounding up would give 16.

Change the internal repr of FeeRate to be fee/kwu to match Core (and do no better)

did you mean sats/kvb since the issue states that's what is used as the basis for core?

Change the internal repr of FeeRate to use a f64

I thought for financial application, it's preferable to use decimal over float.  I think it follows that if decimal/float is used for the back-end calculation, there are much less precision rounding errors that could be.

I think that it's fine for library authors to use IEEE 754 floats based on a correct understanding of them instead of blindly applying generic rules of thumb.

Agree to may as well use what's easiest to begin with until there's an actual reason to add complexity.  Probably easiest to go with IEEE 754 float.