How can I create HTML Page with Serenity Grid ?

Hello,
I want to add serenity grid in my .html page , which are the css and js  files responsible to it. I want similar look and feel.

serenity grid is based off of slickfrid. you can use that repository as reference. Are you using serenity as the base of you site or are you just looking to add the grid template to an existing site?

I want to add grid template in my existing site.

Then I suggest looking at the Slickgrid repository from. https://github.com/mleibman/SlickGrid though I do believe there are some more active forks. Do note @volkanceylan did make changes in the functionality to meet the Serenity needs so if you want to use the features as they stand in Serenity, you'd have to use the core build of serenity as a base and then use the usual approach of adding a grid much like explained in the docs.


feat: add maven check for code signature (static)

Still need to add this for the JavaScript ecosystem, @Stamp9 do you know where I should start to look for this?
Relates to #12

For the JS ecosystem:

yarn doesn't seem to allow this yet: https://github.com/yarnpkg/berry/issues/6487
npm does, with npm audit signatures; this requires cloning the repo and installing all dependencies though, would be nice to find an alternative way
pnpm doesn't seem to allow this yet either: https://github.com/pnpm/pnpm/issues/7909

^force push made to remove commit wrongfully made in this branch, cherry-picked to #54


Stereo camera SLAM to generate Point cloud data

Can we use stereo camera (web cameras or pi cameras) as the input sensors for the cartographer.
This support will help a lot to deploy this easy in multiple places/devices.

Using ROS and stereo vision package was able to pipeline data, but the accuracy required for cartographer will not be achieved with this setup.


windows aarch64: build break: cannot execute binary file: Exec format error

https://ci.adoptopenjdk.net/view/Failing Builds/job/build-scripts/job/jobs/job/jdk16/job/jdk16-windows-aarch64-hotspot/7/console
04:16:55  Creating jdk image
04:19:18  cl : Command line warning D9025 : overriding '/MD' with '/MT'
04:25:42  Finished building targets 'product-images legacy-jre-image test-image' in configuration 'windows-aarch64-server-release'
04:25:42  Should have the source, I'm at /cygdrive/c/workspace/openjdk-build/workspace/build/src
04:25:42  '/cygdrive/c/workspace/openjdk-build/workspace/build/src/build/windows-aarch64-server-release/images/jdk' found
04:25:42  =JAVA VERSION OUTPUT=
04:25:42  /cygdrive/c/workspace/openjdk-build/sbin/build.sh: line 551: /cygdrive/c/workspace/openjdk-build/workspace/build/src/build/windows-aarch64-server-release/images/jdk/bin/java: cannot execute binary file: Exec format error

/cygdrive/c/workspace/openjdk-build/workspace/build/src/build/windows-aarch64-server-release/images/jdk/bin/java

This is a AArch64 binary, so it cannot executed by the build host which is x86/x86_64).
I think you have to specify a build JDK via --with-build-jdk in configure.
See also: https://github.com/openjdk/jdk/blob/master/doc/building.md#boot-jdk-and-build-jdk

this is all fixed now I think, closing

this is all fixed now I think, closing


Fix typo in README.md

Example command for the binary scanner has an incorrect script name.

Thanks 👍


Runtime and sensitivity on performance of TadGAN

Hi @sarahmish
I have some questions related to TadGAN runtime and sensitivity adjustment.
1.Runtime
According to the published benchmarking leaderboard shared on this Google Doc and my personal experience using orion package and TadGAN pipeline, I found that TadGAN takes a very long to train on CPU machines. According to the results, TadGAN takes around 10k - 20k seconds to finish.

Is that on 35 epochs mentioned here or 2000 epochs declared in the paper?
Have you thought about approaches in cutting down the train/detect time? Such as leveraging CudaNN trained on GPU machine etc.

2.sensitivity and global performance
In the paper and repo, I saw that the 4 sigma based fixed thresholding was chosen to be applied to all testing datasets. Have you tried tweaking sensitivity parameter from 4 to other values, and check their respective F1/Precision/Recall and AUC so that global performance can be obtained? If not, could you explain why the static thresholding was chosen?
It will be great if you could clarify those questions to help me understand the package better. Thank you and looking forward to your reply.
Regards

Hi @jessb126, thanks for opening an issue!
1. Runtime

epochs. The implementation of TadGAN in Orion differs slightly from the model mentioned in the paper. Based on experimentation, we find that 35 epochs is enough to produce an effective result.
gpu. There is a CudNN version of tadgan which you can find here. You can run it by declaring Orion('tadgan_gpu').

2. Sensitivity
We experimented with different thresholding values, including 3 standard deviations as well as trying a dynamic threshold mechanism, 4 standard deviations away from the mean was the best obtained score, therefore we kept it consistent in our evaluations.
I hope this answers your questions!

Question, when I ran 'tadgan_gpu' as the pipeline name instead of just tadgan, I got this error: No module named 'tensorflow.contrib.cudnn_rnn'
I take it I am missing a tensorflow module?

There is a specific configuration to using tensorflow gpu. Here are some resources to guide you through the setup https://www.tensorflow.org/install/gpu and https://www.tensorflow.org/install/source#gpu. Also keep in mind that TadGAN currently is only supported by tensorflow 1.

@NIckyVNYC , I had some issues getting tadgan to run on my GPU as well. This was my resolution:

Ensure you have tensorflow 1.14 AND tensorflow-gpu 1.14 installed in your python environment.
Make sure you have CUDA 10.0 installed and on your path. This is the version of CUDA that TF 1.14 requires.


added --skip-bmc-check validation flag for create cluster command

Issue #, if available:
Description of changes:
Added --skip-bmc-check flag for create cluster command for tinkerbell. This feature is useful if customers do not have or do not want to provide an IPMI interface credentials.
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm


Properly handle sourceId and targetId in property mappings

Summary
Closes #1202

How did you test this change?

[ ] Test(s) added
[ ] Manual testing (please provide screenshots/recordings)
[x] No testing (please provide an explanation)

@gayathrir11 there's a problem with some unit/integration tests. You might need to run them locally to find the culprit, but apparently one of your changes caused a mem-leak (or so it seems). I would try to run test by package to narrow down the tests causing the issue. If the mem-leak is built up overtime and running them all cause the mem-leak, it's harder to debug, unfortunately.

Closing in favor of https://github.com/finos/legend-studio/pull/1324


Add an alternative top level exception handler to main for node and cli tool

The exception handler will print the output of displayException e in
addition to the exception of show e when they differ. The former should be a human-readable error message intended for users/sysadmins.
The exceptions are not rethrown as handleSimpleNode is basically the main
function of the node. The actual top-level function is part of
cardano-shell.

See https://github.com/input-output-hk/ouroboros-network/pull/1311

Ok, I've redone this again, based on the top level exception handler from Cabal.
I've moved the use of the handler to the very top level in main, and changed the name accordingly. So there should be no question of what it does when used elsewhere, that's a misuse, and it's documented as such.
Again, it does not catch (technically rethrows) async exceptions and ExitCode exceptions. It catches and prints others (with different formatting to the default) and then throws ExitCode 1.
    Add a top level exception handler to main in the node and cli

    The intention is to provide a more helpful top level exception handler
    than the default one GHC provides that sits "above main".

    In particular, the exception handler will print the output of
    `displayException e` in case it differs from the output of `show e`.
    The former should be a human-readable error message intended for
    users/sysadmins.

    The structure of the code is borrowed from Cabal where it has been used
    for years. Appropriate copyright notices are included.

    Note that only synchronous exceptions are handled/caught, and ExitCode
    is also passed through. This means it handles control-C and exitWith
    appropriately.

@dcoutts Shall we bors this?

bors r+

bors retry


Capture the logger

I want to redirect the log from gringo to my own logger, s.t. everything is nice and ordered:
The following program ends with an exception of a syntax error, which is expected. But the logging seems to report an additional error:
import logging
from clingo.ast import parse_string

def main() -> None:
    prg = []
    parse_string("*", prg.append, logger=logging.warning)

if __name__ == "__main__":
    main()

produces
--- Logging error ---
Traceback (most recent call last):
  File "...miniconda3/envs/ngo/lib/python3.10/logging/__init__.py", line 1100, in emit
    msg = self.format(record)
  File "...miniconda3/envs/ngo/lib/python3.10/logging/__init__.py", line 943, in format
    return fmt.format(record)
  File "...miniconda3/envs/ngo/lib/python3.10/logging/__init__.py", line 678, in format
    record.message = record.getMessage()
  File "...miniconda3/envs/ngo/lib/python3.10/logging/__init__.py", line 368, in getMessage
    msg = msg % self.args
TypeError: not all arguments converted during string formatting
Call stack:
  File "...work/krbiz/potassco/ngo/log.py", line 13, in <module>
    main()
  File "...work/krbiz/potassco/ngo/log.py", line 10, in main
    parse_string("*", prg.append, logger=logging.warning)
  File "...miniconda3/envs/ngo/lib/python3.10/site-packages/clingo/ast.py", line 1347, in parse_string
    _lib.clingo_ast_parse_string(
  File "...miniconda3/envs/ngo/lib/python3.10/site-packages/clingo/core.py", line 95, in _pyclingo_logger_callback
    handler(MessageCode(code), _to_str(message))
Message: <MessageCode.RuntimeError: 1>
Arguments: ('<string>:1:1-2: error: syntax error, unexpected *\n',)
Traceback (most recent call last):
  File "...work/krbiz/potassco/ngo/log.py", line 13, in <module>
    main()
  File "...work/krbiz/potassco/ngo/log.py", line 10, in main
    parse_string("*", prg.append, logger=logging.warning)
  File "...miniconda3/envs/ngo/lib/python3.10/site-packages/clingo/ast.py", line 1346, in parse_string
    _handle_error(
  File "...miniconda3/envs/ngo/lib/python3.10/site-packages/clingo/_internal.py", line 75, in _handle_error
    raise RuntimeError(msg)
RuntimeError: syntax error

How can I handle this case correctly ?

logging.warning and the clingo logger do not have the same signature. You'll have to write some wrapper code. Check the type annotations!


fix the disorder issue of texture atlas

Objective
fix the disorder of SpriteSheetBundle built with TextureAtlasBuilder
When TextureAtlasBuilder builds the final TextureAtlas, it uses the handleId to draw layers, but the handleId is created in a random manner, So the SpriteSheetBundle would display in a disordered way.
Solution
use a Vec to store the textures info to make sure the sprite index is as the order as the adding textures.
and since TextureAtlasBuilder is usually temp, the overhead of the Vec is nothing, but the output TextureAtlas would be steady.

This seems to change the behavior somewhat when a user attempts to add the same image multiple times.
I've not considered this, but I think it's the client's choice.
Maybe someone want to do that to have the same frames in animation :)

I've not considered this, but I think it's the client's choice.

This PR would actually introduce inconsistencies. images with the same handles will be written at the same place in the atlas, but would have several records in the atlas.texture pointing to them, but only one entry in the atlas.texture_handles pointing to those rects.
Could you change the order to something that would guarantee uniqueness like an HashSet to keep the same behaviour?

Fixed in https://github.com/bevyengine/bevy/pull/11474


Output from stdout and stderr mixed

We need to redirect stderr to stdout and capture only stdout to ensure that lines corresponding to them don't get mixed in the final output window or log file

there are some suggestions to use OutputDataReceived:
https://stackoverflow.com/questions/52088894/when-run-a-program-in-c-all-the-messages-go-to-the-standard-output-but-the-st

Found this snippet: https://stackoverflow.com/a/38882348/837816, maybe it is enough.


Drop set_openstack_containers from edpm_prepare role

All the reference of set_openstack_containers role is replace with update_containers role.
We are keeping set_openstack_containers role as update team wants to use it to perform minor update with installed operators.
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running

Closing this pr, set_openstack_containers may be needed for update testing.


Add TLS support to server

Also, just curious: is client.CqlServer being used somewhere in production? We designed it as a testing tool, which is why I'm asking this.

I approved the code changes but I'm also interested in the answers to the questions that Alex asked.


[CARBONDATA-4064] Fix tpcds query failure with SI

Why is this PR needed?
TPCDS queries are failing with None.get exception when SI is configured for some tables.
What changes were proposed in this PR?
Check if parentRelation is none for filter condition, and return false for checkIfPushDownOrderByLimitAndNotNullFilter
Does this PR introduce any user interface change?

No

Is any new testcase added?

No

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/4960/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/3205/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/4970/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/3215/

LGTM


Document $PORT and $PS

Update the ronn documentation to explain that $PORT and $PS exist and
that $PORT starts as the base port number and is incremented on each
line.

Hey @ddollar, just a polite nudge about this.

Ping @ddollar . Anything to know that you've seen this is welcome.

@ddollar is this repo still used?

Thanks!

Hi @ddollar,
I've been happily using foreman for a long time now but what is the rationale behind adding 100 to the port for each line in a Procfile?
I just discovered this by having this strange effect:
prompt> PORT=1234 foreman start web
....
stdout> web.1    | [42390] * Listening on tcp://<IP_ADDRESS>:1334

i.e. PORT value was strangely 100 higher than I intended.
This was my Procfile:
worker: bundle exec sidekiq -C config/sidekiq.yml -r ./application.rb
web: bundle exec puma -p ${PORT:-8080} -C config/puma.rb

i.e. web process on line 2, not the first line.
So in order to get the right port, I had to define the web process on the first line of my Procfile:
PORT=1234 foreman start web
....
web.1    | [43088] * Listening on tcp://<IP_ADDRESS>:1234

(Having swapped the two lines of my Procfile.)
This is incredibly subtle. I don't understand how the PORT variable can vary according to line on which something is defined in the Procfile.
I guess this is covering PORT number overlapping when starting multiple services in a single Procfile. But I would have assumed this would be an application responsibility, i.e. the application decides what to do if an PORT is taken and not foremans concern.


update cd command(s) to match the repository-name

replaces #2
(fixes both references now)

Thanks!


Updates player.js indents

Fixes.

This is a really weird change. You removed some lines and you added some empty trailing whitespace for some reason?

Better, thx.


WIP: update kube subnet manager to k8s.io/client-go

This diff seems absurdly large.

The diff is the difference between glide install and glide install --strip-vendor I think.
There should probably be a makefile target or script so it's clear that flag's typically being used.

Yes glide install --strip-vendor should be used

@mikedanese Any special reason for bumping kube-cross? (Just trying to understand it so I can make a minimal patch release if needed)

@tomdee "context" (added in go1.7) is required by k8s.io/client-go but the current kube-cross has go1.6.

I suspect the build errors are down to the kube-cross change
/opt/bin/flanneld: relocation error: /lib/libpthread.so.0: symbol __libc_vfork, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

@mikedanese The kube-cross upgrade is a bit tricky. You could rebase on top of #678 or just switch to using a different build container.

I tested this by hand and it seems to work fine. @aaronlevy suggested a possibly smaller patch that would fix this.

I was thinking we might just switch to using Patch() rather than Update(), which we should eventually do anyway. Then wait on changing vendor to client-go (also client-go v3 is still technically beta - so we might need to bump this again soon anyway)
Using PATCH was brought up in: https://github.com/coreos/flannel/issues/667#issuecomment-293150531 and an example https://github.com/kubernetes/kubernetes/blob/3b1d2343a84d3b8e3fd21554568e06b8594cdf26/pkg/controller/controller_utils.go#L956-L961

We definitely want to do both. I do think moving to client-go sooner rather then later is safe. FWIW we are using the same packages in client-go that are used extensively in the controller-manager already. beta here means that the public API might change and you will compile errors when you rebase, but the client is tested extensively. I can look at that patch later today.

I built flannel using this PR and did a fair bit of testing, both in host-pod and host-host networking as well as making sure that flannel correctly preserved the taints. Everything LGTM.

Gah. Needs a rebase now.
@tomdee does this LGTY?
@mikedanese can you rebase?


⚠ File access (beta) has degraded performance

In f8ef656, File access (beta) (https://beta.fyle.uk/file/fish) experienced degraded performance:

HTTP code: 200
Response time: 7109 ms

Resolved: File access (beta) performance has improved in ff1d9ec.


Add URL pattern logging

This is useful for monitoring the general endpoints without using route parameters like resource ID's etc. It allows better monitoring on a per endpoint/controller method.
For example, it would help with this: https://www.honeycomb.io/blog/tell-me-more-nginx/

@iDontCYnot @SaxJ should I also add a middleware to this PR that can be used to log the URL pattern and the corresponding response code? It could be a middleware that is applied to every route and just logs before/after passing the request through and getting the response back to log the code.
That way, it would allow monitoring and alerting on URL patterns and the HTTP response codes they result in

@iDontCYnot @SaxJ should I also add a middleware to this PR that can be used to log the URL pattern and the corresponding response code? It could be a middleware that is applied to every route and just logs before/after passing the request through and getting the response back to log the code.
That way, it would allow monitoring and alerting on URL patterns and the HTTP response codes they result in

Would the middleware be optionally applied. I'm happy for a middleware to exist with this functionality but i'm unsure we want to apply it over all routes in all situations

Yeah I agree, I think just creating the middleware for optional use

I'll follow up with a PR that adds middleware as above


Decoding & flattening an array

I have response that I'd like to flatten:
{
    "foo": "bar"
    "bazCollection": [
      { "bazId": 1 },
      { "bazId": 2 },
    ]
}

Is there a combination of operators that I can use to decode this response to following struct:
struct FooResponse {
  let foo: String
  let bazIds: [Int]
}

Hi @eimantas,
I believe you can do something like:
extension FooResponse: Decodable {

    static func decode(j: JSON) -> Decoded<FooResponse> {

        return curry(FooResponse.init)
            <^> j <| "foo"
            <*> j <|| ["bazCollection", "bazId"]
    }
}

There is probably a cleaner way but this will do what you want.
import Foundation
import Argo
import Curry

var jsonString = "{\"foo\":\"bar\",\"bazCollection\":[{\"bazId\":1},{\"bazId\":2}]}"

struct FooResponse {
    let foo: String
    let bazIds: [Int]
}

extension FooResponse: Decodable {
    static func decode(json: JSON) -> Decoded<FooResponse> {
        let decodedBazIds: Decoded<[BazId]> = curry([BazId].init) <^> json <|| "bazCollection"
        let decodedIds: Decoded<[Int]> = decodedBazIds.map { $0.map({ $0.id }) }
        return curry(FooResponse.init)
            <^> json <| "foo"
            <*> decodedIds
    }

    struct BazId: Decodable {
        let id: Int

        static func decode(json: JSON) -> Decoded<BazId> {
            return curry(BazId.init)
                <^> json <| "bazId"
        }
    }
}

let json = try! NSJSONSerialization.JSONObjectWithData(jsonString.dataUsingEncoding(NSUTF8StringEncoding)!, options: [])
var result: Decoded<FooResponse> = decode(json)

Oh, interesting. This is an unusual path, and we don't have an optimized API for it. Seems like what we really need is some sort of keypath support. Unfortunately we don't have anything like that right now.
This turns into another one of these interesting "follow the types" puzzles we run into a lot. The end result that I came up with is really similar to the one proposed by @jkennington, but I'm preferring to use specialized functions instead of the intermediate type.
The root of the issue is that we need to go through a couple of awkward transformations of our data and it's not immediately obvious what the path should be. We start with JSON, and somehow need to get to [Int]. We know based on our expected json object that this should be true:
let collection: Decoded<[JSON]> = json <|| "bazCollection"

So now we're left with needing to go from Decoded<[JSON]> -> Decoded<[Int]>. We also know (because of our expected json) that JSON is an object with a bazId key. So our first attempt will be to map over that array, pull out that key, and decode it into an Int. Unfortunately, since we're dealing with a decoded array we need to do an awkward double map. We're one step closer but not quite there:
let collection: Decoded<[JSON]> = json <|| "bazCollection"
let decodedInts: Decoded<[Decoded<Int>]> = collection.map { $0.map { $0 <| "bazId" } }

That gets us to that weird nested Decoded type. If we could flatten that, it'd get us to the type we actually want.
The first step towards that goal will be to move from [Decoded<Int>] to Decoded<[Int]>. Luckily for us, that type lines up perfectly with the free function we're exporting called sequence ([Decoded<T>] -> Decoded<[T]>). So tossing that into the mix gets us to:
let collection: Decoded<[JSON]> = json <|| "bazCollection"
let decodedInts: Decoded<Decoded<[Int]>> = collection.map { sequence($0.map { $0 <| "bazId" }) }

And hey, now that we have two Decoded types like that, we should just be able to change our initial map to a flatMap and get to our final goal:
let collection: Decoded<[JSON]> = json <|| "bazCollection"
let decodedInts: Decoded<[Int]> = collection.flatMap { sequence($0.map { $0 <| "bazId" }) }

A little more complex than I'd like ideally, but it compiles and therefore we know it produces the correct types. So assuming our string keys are correct, it will decode what we expect it to decode.
fwiw, I dropped this into a single line helper function when I was playing with it, which I think pulls the complexity out of the main parser nicely and makes it a bit more readable:
extension FooResponse: Decodable {
  static func decode(_ json: JSON) -> Decoded<FooResponse> {
    return curry(FooResponse.init)
      <^> json <| "foo"
      <*> decodeIDs(json)
  }
}

private func decodeIDs(_ json: JSON) -> Decoded<[Int]> {
  return (json <|| "bazCollection").flatMap { sequence($0.map { $0 <| "bazId" }) }
}

I'm going to close this due to inactivity, but please feel free to re-open if this is still unresolved.


Problem f1 reply

hello, i'm try to user part of your code to do the ota update from an ionic app and an esp32
i'm writing the android part as new in angular and ionic, but the arduino esp32 part i'll try to use the most to test if it works, and now i'm avaing some issue,
i've managed to send the version of the esp32 at setup, on the app i'll check it and if it's different i'll start the update process,
i'll send an 0xFD to format the SPIFFS,
after that i'll send an 0xFF with the size and total number of packets
after that i'll send 0xFB with the number of the packet and the part of the firmware file itself
then i'll send 0xFC with the size of the packet and the number of that packet
at this point the esp32 should send 0xF1 to android, but here it's my issue the loop, when it enter the updating if and the request if, i will receive 0 0 on andorid
(i've tried sent again the version instead of 0xF1 but still i receive 0 0, because i was thinkig about some issue on the data structure on the rq variable)
any idea why that is happening ?
thanks

seems this is an issue with the received data on your app. I don't know about angular or iconic.
Check that you can receive data on your app


Fix and improve scripts/wp-plugin.js.

Holy on this until further notice.

Well, the script is broken currently without this PR.
I could remove the bs4 addition so that it works and merge for now, but my 2 questions still stand:

Why do we need the script since we generate data/bootstrapcdn.json via express?
Will the WP plugin throw with the jsBundle entry?

@jmervine: are we sure the bootstrap4 addition will not break the WP plugin?
Also, why do we need the script since we generate the json file server-side?

No, I'm assuming it will break the WP plugin basedon @jdorfman's comments.
I approve the code change though, it all looks good. I'd assume you'd wait for the go-ahead from Justin to merge.

All right, but do we need the script anymore?

Oh, I see what you're asking now. Not 100% sure, but I doubt it unless someone is uploading the result to S3.

Should I just remove it then and all its references?

I removed the bootstrap 4 addition.
I added one more patch to remove the script and its references, so just let me know which way we should go.

I'm merging this as is, without any removal, but we should revisit it and remove it if it's unused.


update origin

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


submodule?

Idea: Move yml from website repo to here, make this the one where people make contributions
Info:
https://djoepramono.github.io/jekyll-and-git-submodule/
https://stackoverflow.com/questions/11817338/how-to-add-submodule-into-gh-pages-branch-build-static-pages-correctly

Success!
Will need to see how changes propagate to the website when the database is updated.

Still need to figure out how to auto-rebuild the Jekyll website whenever there's a new commit here (i.e., the submodule).


Is the emulator intended to support happy-path testing only?

I'm getting the impression from ~20 minutes of searching for ways to configure the emulator behaviour for a given test that the emulator's prime use case is testing happy paths. Can anyone confirm or deny this. If denying a link to the documentation I've been looking for would be much appreciated.
I also have the same question about the pubsub emulator in case anyone answering happens to oversight over both.

@nickform Thank you for your patience. We document the limitations of both the DataStore and Pub/Sub emulators (See "Known issues" or "Known limitations" sections).  Because the emulators are not open source, they won't be able to support all test cases. In that sense, you can say that the prime use case for them is testing the happy paths. If you'd like to request a feature and tell us why it is important to you, please let us know again. Below are the links to the documentation:
DataStore:

https://cloud.google.com/datastore/docs/tools/datastore-emulator
https://cloud.google.com/datastore/docs/tools/emulator-export-import

Pub/Sub

https://cloud.google.com/pubsub/docs/emulator


Google Chrome Next/Previous clicks not working

Hi there,
I believe the issue has to do with touch support. When clicking on Next/Previous, nothing happens. If I keep the dev tools open, I see the class changing on the container, which looks like a "grab" is being triggered rather than a click.
It looks like the class cursor: -webkit-grabbing; is being applied when I am clicking on the next/previous buttons.
Is there a way to threshold when "grabbing" is considered started (once mouse moved 5px, etc.)? Perhaps it's a simple re-order of listeners to have click happen before the grab start

It is a browser/platform issue, the same as in #1152 and here http://www.idangero.us/swiper/forum/#!/bugs-and-issues:nextbuttonprevbutton-doesn

Thanks. It would be great if you could address the issue in one of these, then. As mentioned, this is also happening on your demo sliders, so it's not only a CSS issue.

It is not a CSS issue, it is device/platform issue in Chrome, as there is no such issues on Mac, Linux, only on Chrome for Windows and not for everyone. At least, i can't replicate it


login page responsive design added fixed logo half display

mobile screen responsive design added  and fixed logo problem it's display half only

merged.


Running Two Versions

Issue Type: Bug
I have already updated VS Code to latest version 1.35 but sometimes when opening workspaces or folders it randomly run some of them on 1.34.
At this moment, I have two copies of VS Code running next to each other one on 1.35 and the other on 1.34
How can I fix that?
VS Code version: Code 1.34.0 (a622c65b2c713c890fcf4fbf07cf34049d5fe758, 2019-05-15T21:59:37.030Z)
OS version: Windows_NT x64 10.0.18362

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8 x 2592)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
23.88GB (9.21GB free)

Process Argv
D:\permagreen\PermaGreen\PermaGreen.code-workspace

Screen Reader
no

VM
0%

Uninstall both and install VS Code again.


ARTEMIS-1977 ASYNCIO can reduce sys-calls to retrieve I/O events

On LibAIO is possible to retrieve the I/O completion
events without using io_getevents sys-calls by reading
the user-space ring buffer used by the kernel to store them.
This commit include another optimization to avoid
calling a method to obtain the buffers address, saving
safepoint polls, a method call and implicit instance of
checks performed.

I close this because It needs to be refined and battle tested...it is a WIP :+1:


Negative single bar

Fixed single bar chart to correctly display negative values below the 0 tick mark.

Looks good


Replace k3s replaces with the offical k8s

What this PR does / why we need it:
Remove the dependency on k8s.io/kubernetes
Use the k8s deps instead of k3s
Which issue(s) this PR fixes:

Fixes #47238
Special notes for your reviewer:
None

Steps to reproduce
None

Does this PR introduce a user-facing change?

NONE

Does this PR require documentation?

@marccampbell  in regards to the testing.  I tested in Okteto and locally but I want to run the regression tests on this for sure.  That will give us more confidences about kube versions and configurations.  But right now the regression stuff triggers off main.

@marccampbell Fixed the issues you mentioned in the code.

These changes were tested locally and in Okteto.

@marccampbell here is the passing regression test.  There was one failure but it was completely unrelated to the change.  everything else passed.


Downgrade io_bazel_rules_go to v0.27.0 restore Bazel 3.x support

Tested builds:

Bazel 4.2.2 on macOS with v0.27.0 (OK)
Bazel 4.0.0 on Linux with v0.27.0 (Minimum Bazel 3.0.0) (OK)
Bazel 4.0.0 on Linux with v0.28.0 (Minimum Bazel 4.0.0) (OK)
Bazel 4.0.0 on Linux with v0.29.0 (Minimum Bazel 4.2.1) (FAIL)

As @veblush pointed out, we still want to support Bazel 3.x declared in https://github.com/grpc/grpc/blob/master/bazel/supported_versions.txt. So, the best version of io_bazel_rules_go to downgrade to at this point is v0.27.0.
In future, when we deprecate Bazel 3.x, we should be free to upgrade the Bazel go rules again.
Related https://github.com/grpc/grpc/pull/29593.

@lidizheng Thank you for doing this!

The failures are known.

As @veblush pointed out, we still want to support Bazel 3.x declared in https://github.com/grpc/grpc/blob/master/bazel/supported_versions.txt. So, the best version of io_bazel_rules_go to downgrade to at this point is v0.27.0.

Our support policy is at least the two most recent LTS releases of Bazel. If we have a compelling reason to drop support for 3.X, we're free to do so.


build fails on newer java

In detail it is the canonicalize-source and build-guidelines-html that fail with:
java.lang.UnsupportedOperationException: The Security Manager is deprecated and will be removed in a future release

While build-guidelines-html already has @failonerror="true" and thus makes the whole build fail, canonicalize-source would still signal BUILD SUCCESSFUL although the canonicalization actually failed.
Adding @fork="trueon both java-calls and @failonerror="true" on canonicalize-source will do the trick ;-)

@bwbohl Thanks for tracking this down. Will this still work with older java versions? Would you like to open a PR?

fixed in pdf-guidelines-test by 2493df814624861601c8c2386eb05feff8b6d504

@bwbohl Thanks for tracking this down. Will this still work with older java versions? Would you like to open a PR?

yes, does work with older java versions. Tested in container with JRE8


[WIP] NewWithPasswordCredentials/NewWithClientCredentials return wrapper struct with .Token()

See example: https://github.com/starkandwayne/ultimate-guide-to-uaa-examples/blob/e8ca806baadb7907a91ca32ade13246c61bbdcbc/golang/resource-server-cli/src/resource-server-cli/main.go#L54-L66
With consideration to #5 proposal to change API#AuthenticatedClient into a function, perhaps API can become an interface with AuthenticatedClient  rather than a struct; and the returned struct from NewWithXYZ can hold the xyz.Config and have its own AuthenticatedClient functions etc.

I see no problems with this but I'll wait for @joefitzgerald to get back from his vacation to look at it, as he's been working with the UAA team on this and may have to take this into account.

This is fixed in v0.2.0, which includes a uaa.API.Token function.


sketchybar-app-font: 2.0.12 -> 2.0.15

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/kvndrsslr/sketchybar-app-font/releases.
meta.description for sketchybar-app-font is: A ligature-based symbol font and a mapping function for sketchybar
meta.homepage for sketchybar-app-font is: https://github.com/kvndrsslr/sketchybar-app-font
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.0.15 in filename of file in /nix/store/anzdk8pjph80k5vnhy7s3wzdcf4jqrbx-sketchybar-app-font-2.0.15

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
sketchybar-app-font

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/anzdk8pjph80k5vnhy7s3wzdcf4jqrbx-sketchybar-app-font-2.0.15 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A sketchybar-app-font https://github.com/r-ryantm/nixpkgs/archive/e6bf7d35a4a786a0975210ab3ff8905a59e2e26c.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/e6bf7d35a4a786a0975210ab3ff8905a59e2e26c#sketchybar-app-font

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/anzdk8pjph80k5vnhy7s3wzdcf4jqrbx-sketchybar-app-font-2.0.15
ls -la /nix/store/anzdk8pjph80k5vnhy7s3wzdcf4jqrbx-sketchybar-app-font-2.0.15/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

sketchybar-app-font

Maintainer pings
cc @khaneliman for testing.

superseded by https://github.com/NixOS/nixpkgs/pull/297722


just install-operator fails when using the Rust stable release channel

Context
On d952d312
Problem
just install-operator

error[E0554]: `#![feature]` may not be used on the stable release channel
  --> /Users/rootulp/.cargo/git/checkouts/union-ee564f669096b471/18c86b4/lib/unionlabs/src/lib.rs:13:1
   |
13 | #![feature(trait_alias)]
   | ^^^^^^^^^^^^^^^^^^^^^^^^

For more information about this error, try `rustc --explain E0554`.

Proposal
To resolve I had to do:
rustup install nightly
rustup override set nightly
just install-operator

which worked

This was true in older commits of this repository, but since then, we removed union dependencies and should no longer require nightly. Our ci also fully runs on stable rust. Am I missing something?

Oops nope, sorry I only tested on an older commit because I was trying to setup https://github.com/celestiaorg/celestia-zkevm-ibc-demo/ for local development and the commit of solidity-ibc-eureka is no longer accessible so I downgraded to the last known working version https://github.com/celestiaorg/celestia-zkevm-ibc-demo/issues/17#issuecomment-2526702920
Can close this and the PR if it's resolved on main.


dev environment for front end

hi.
i was using augury for angular 2 to degub the frontend.
augury does not support angular 4. can u help me setting up the dev env for frontend.
thanks

chromes vanilla devtools of chrome to debug. I used VS-Code debugger too, but returned back to chrome debugger, Thats better suited for front-end debugging.
I am sorry cant help you with augury. May be they will start supporting ng4 soon


Long delay after first token generation in 0.1.8 that's not in 0.1.7.  Also 0.1.8 is much slower than 0.1.7

Reported by user of h2oGPT: https://github.com/h2oai/h2ogpt/issues/1309
I used an edited version of the text streamer, only changed by printing every token instead of waiting for a space.  You'll see it print Wh, then wait nearly 0.5 seconds, then continue.
This only occurs with 0.1.8
https://github.com/casper-hansen/AutoAWQ/releases/download/v0.1.7/autoawq-0.1.7+cu118-cp310-cp310-linux_x86_64.whl

and not in 0.1.7:
https://github.com/casper-hansen/AutoAWQ/releases/download/v0.1.7/autoawq-0.1.7+cu118-cp310-cp310-linux_x86_64.whl

Also, the script for the 2+ generations runs in 3.6 seconds with 0.1.8 and in 2.5 seconds in 0.1.7.
So there are 2 problems, but perhaps the delay accounts for all of the difference.
Script, ran on 4A10G or 4A6000:
prompt = """Pay attention and remember the information below, which will help to answer the question or imperative after the context ends.
\"\"\"
103.9
60.6
74.6
126.0
109.6
64.3
Whisper small
16.4
87.3
103.6
14.7
92.9
7.3
29.8
11.4
131.7
33.3
49.3
140.0
105.3
42.2
Whisper medium
9.9
79.5
102.0
8.0
119.4
5.0
20.0
7.2
147.0
17.3
31.9
143.9
104.0
44.9
Whisper large
8.3
75.9
102.8
7.2
92.7
4.8
15.4
6.4
177.9
15.7
27.8
130.0
103.5
29.2
Model
Swedish
Swahili
Tamil
Telugu
Tajik
Thai
Turkish
Ukrainian
Urdu
Uzbek
Vietnamese
Yoruba
Whisper tiny
52.7
100.9
99.9
105.1
101.7
58.8
42.5
51.2
65.2
105.2
60.0
106.4
Whisper base
37.4
92.5
58.7
105.2
109.3
38.2
27.5

Table 18. Whisper model learning rates.

70.3
104.4
100.4
19.6
100.1
Whisper medium
19.3
24.3
60.1
10.2
49.9
5.2
7.1
67.9
117.3
48.8
98.9
77.7
16.4
90.0
Whisper large
16.7
21.0
53.7
8.5
43.0
4.2
6.4
87.0
100.5
43.8
96.0
69.8
15.2
86.5
Model
Lingala
Lao
Lithuanian
Latvian
Maori
Macedonian
Malayalam
Mongolian
Marathi
Malay
Maltese
Myanmar
Norwegian
Nepali
Whisper tiny
105.4
115.1
98.5
91.6
94.5
73.3
101.5
113.7
100.3
51.2
100.8
124.8
62.0
101.8
Whisper base
96.7
105.1
87.3
79.8
77.5
59.9
107.4
125.7
100.3
35.1
97.6
122.6
44.0
102.4
Whisper small

We?d like to thank the millions of people who were involved
in creating the data used by Whisper. We?d also like to
thank Nick Ryder, Will Zhuk, and Andrew Carr for the
conversation on the waterfall hike that inspired this project.
We are also grateful to the Acceleration and Supercomputing
teams at OpenAI for their critical work on software and
hardware infrastructure this project used. We?d also like to
thank Pamela Mishkin for advising the project from a policy

the Whisper model under additive pub noise of SNR below
10 dB. This showcases Whisper?s robustness to noise, es-
pecially under more natural distribution shifts like the pub
noise.
3.8. Long-form Transcription
Whisper models are trained on 30-second audio chunks and
cannot consume longer audio inputs at once. This is not a
problem with most academic datasets comprised of short
utterances but presents challenges in real-world applications
which often require transcribing minutes- or hours-long au-

Whisper large
34.3
21.7
77.8
22.8
15.9
17.6
20.6
22.7
31.6
26.0
14.8
0.5
19.6
20.7
Model
Croatian
Hungarian
Armenian
Indonesian
Icelandic
Italian
Japanese
Javanese
Georgian
Kazakh
Khmer
Kannada
Korean
Luxembourgish
Whisper tiny
0.6
0.1
0.1
0.3
0.4
5.3
0.2
0.2
0.1
0.1
0.1
0.8
0.5
0.8
Whisper base
3.7
0.2
0.1
2.6
0.4
11.3
1.5
0.2
0.2
0.2
0.1
0.9
3.7
1.7
Whisper small
14.6
4.8
0.7
16.4
1.8
17.8
9.6
1.4
0.2
0.8
0.5
2.3
12.2
5.7
Whisper medium
23.0
15.5
10.4
24.1
6.8
21.6
14.9
5.0
1.3
4.3
3.3
8.5
19.2
13.6

Robust Speech Recognition via Large-Scale Weak Supervision
5
Model
Layers
Width
Heads
Parameters
Tiny
4
384
6
39M
Base
6
512
8
74M
Small
12
768
12
244M
Medium
24
1024
16
769M
Large
32
1280
20
1550M
Table 1. Architecture details of the Whisper model family.
3. Experiments
3.1. Zero-shot Evaluation
The goal of Whisper is to develop a single robust speech
processing system that works reliably without the need for
dataset specific fine-tuning to achieve high-quality results

Whisper tiny.en
5.5
12.8
13.8
15.1
17.0
22.0
30.3
Whisper tiny
6.8
15.5
16.7
17.0
18.7
24.4
33.1
Whisper base.en
4.6
9.4
11.2
13.2
12.5
16.6
25.2
Whisper base
4.8
12.2
12.2
14.5
13.5
18.4
26.9
Whisper small.en
4.6
6.0
9.4
12.0
10.8
14.0
21.9
Whisper small
4.2
6.9
10.1
12.1
11.1
14.3
22.3
Whisper medium.en
3.6
5.2
8.9
11.9
10.2
13.3
20.6
Whisper medium
3.8
5.4
8.6
11.4
10.3
13.2
20.3
Whisper large
3.8
5.3
8.8
11.0
10.3
13.4
20.4
wav2vec2-base-100h
17.6
27.7
39.3
35.2
45.7
57.1
55.4
wav2vec2-base-960h
12.8

Whisper large
25.4
18.3
13.2
27.2
6.6
23.5
17.0
5.1
2.7
6.3
5.2
9.9
20.0
15.4
Model
Lingala
Lao
Lithuanian
Latvian
Maori
Macedonian
Malayalam
Mongolian
Marathi
Malay
Maltese
Myanmar
Norwegian
Nepali
Whisper tiny
0.1
0.2
0.1
0.2
0.3
1.0
0.8
0.1
0.2
0.3
0.6
0.1
1.4
0.1
Whisper base
0.1
0.3
0.3
0.4
1.0
5.4
1.4
0.1
0.9
2.1
1.4
0.1
8.4
0.3
Whisper small
0.5
2.0
1.9
1.5
3.9
15.3
5.7
0.1
3.8
14.1
4.9
0.0
22.0
2.9
Whisper medium
0.9
8.1
9.6
10.0
8.5
23.5
13.8
0.5
10.9
23.2
11.2
0.2
29.1
12.7
Whisper large
1.2
9.3

the following URL: https://github.com/openai/
whisper.
2. Approach
2.1. Data Processing
Following the trend of recent work leveraging web-scale
text from the internet for training machine learning systems,
we take a minimalist approach to data pre-processing. In
contrast to a lot of work on speech recognition, we train
Whisper models to predict the raw text of transcripts without
any significant standardization, relying on the expressive-
ness of sequence-to-sequence models to learn to map be-
\"\"\"
According to only the information in the document sources provided within the context above:
What is Whisper?
"""

from awq import AutoAWQForCausalLM
from transformers import AutoTokenizer
from transformers.generation.streamers import BaseStreamer

class TextStreamer(BaseStreamer):
    """
    Simple text streamer that prints the token(s) to stdout as soon as entire words are formed.

    <Tip warning={true}>

    The API for the streamer classes is still under development and may change in the future.

    </Tip>

    Parameters:
        tokenizer (`AutoTokenizer`):
            The tokenized used to decode the tokens.
        skip_prompt (`bool`, *optional*, defaults to `False`):
            Whether to skip the prompt to `.generate()` or not. Useful e.g. for chatbots.
        decode_kwargs (`dict`, *optional*):
            Additional keyword arguments to pass to the tokenizer's `decode` method.

    Examples:

        ```python
        >>> from transformers import AutoModelForCausalLM, AutoTokenizer, TextStreamer

        >>> tok = AutoTokenizer.from_pretrained("gpt2")
        >>> model = AutoModelForCausalLM.from_pretrained("gpt2")
        >>> inputs = tok(["An increasing sequence: one,"], return_tensors="pt")
        >>> streamer = TextStreamer(tok)

        >>> # Despite returning the usual output, the streamer will also print the generated text to stdout.
        >>> _ = model.generate(**inputs, streamer=streamer, max_new_tokens=20)
        An increasing sequence: one, two, three, four, five, six, seven, eight, nine, ten, eleven,
        ```
    """

    def __init__(self, tokenizer: "AutoTokenizer", skip_prompt: bool = False, **decode_kwargs):
        self.tokenizer = tokenizer
        self.skip_prompt = skip_prompt
        self.decode_kwargs = decode_kwargs

        # variables used in the streaming process
        self.token_cache = []
        self.print_len = 0
        self.next_tokens_are_prompt = True

    def put(self, value):
        """
        Receives tokens, decodes them, and prints them to stdout as soon as they form entire words.
        """
        if len(value.shape) > 1 and value.shape[0] > 1:
            raise ValueError("TextStreamer only supports batch size 1")
        elif len(value.shape) > 1:
            value = value[0]

        if self.skip_prompt and self.next_tokens_are_prompt:
            self.next_tokens_are_prompt = False
            return

        # Add the new token to the cache and decodes the entire thing.
        self.token_cache.extend(value.tolist())
        text = self.tokenizer.decode(self.token_cache, **self.decode_kwargs)

        # After the symbol for a new line, we flush the cache.
        if text.endswith("\n"):
            printable_text = text[self.print_len :]
            self.token_cache = []
            self.print_len = 0
        # If the last token is a CJK character, we print the characters.
        elif len(text) > 0 and self._is_chinese_char(ord(text[-1])):
            printable_text = text[self.print_len :]
            self.print_len += len(printable_text)
        # Otherwise, prints until the last space char (simple heuristic to avoid printing incomplete words,
        # which may change with the subsequent token -- there are probably smarter ways to do this!)
        else:
            # printable_text = text[self.print_len : text.rfind(" ") + 1]
            printable_text = text[self.print_len:]
            self.print_len += len(printable_text)
            print("Token: %s" % printable_text, flush=True)

        self.on_finalized_text(printable_text)

    def end(self):
        """Flushes any remaining cache and prints a newline to stdout."""
        # Flush the cache, if it exists
        if len(self.token_cache) > 0:
            text = self.tokenizer.decode(self.token_cache, **self.decode_kwargs)
            printable_text = text[self.print_len :]
            self.token_cache = []
            self.print_len = 0
        else:
            printable_text = ""

        self.next_tokens_are_prompt = True
        self.on_finalized_text(printable_text, stream_end=True)

    def on_finalized_text(self, text: str, stream_end: bool = False):
        """Prints the new text to stdout. If the stream is ending, also prints a newline."""
        print(text, flush=True, end="" if not stream_end else None)

    def _is_chinese_char(self, cp):
        """Checks whether CP is the codepoint of a CJK character."""
        # This defines a "chinese character" as anything in the CJK Unicode block:
        #   https://en.wikipedia.org/wiki/CJK_Unified_Ideographs_(Unicode_block)
        #
        # Note that the CJK Unicode block is NOT all Japanese and Korean characters,
        # despite its name. The modern Korean Hangul alphabet is a different block,
        # as is Japanese Hiragana and Katakana. Those alphabets are used to write
        # space-separated words, so they are not treated specially and handled
        # like the all of the other languages.
        if (
            (cp >= 0x4E00 and cp <= 0x9FFF)
            or (cp >= 0x3400 and cp <= 0x4DBF)  #
            or (cp >= 0x20000 and cp <= 0x2A6DF)  #
            or (cp >= 0x2A700 and cp <= 0x2B73F)  #
            or (cp >= 0x2B740 and cp <= 0x2B81F)  #
            or (cp >= 0x2B820 and cp <= 0x2CEAF)  #
            or (cp >= 0xF900 and cp <= 0xFAFF)
            or (cp >= 0x2F800 and cp <= 0x2FA1F)  #
        ):  #
            return True

        return False

quant_path = "TheBloke/openchat_3.5-16k-AWQ"

# Load model
model = AutoAWQForCausalLM.from_quantized(quant_path, fuse_layers=True)
tokenizer = AutoTokenizer.from_pretrained(quant_path, trust_remote_code=True)
streamer = TextStreamer(tokenizer, skip_prompt=True, skip_special_tokens=True)

prompt_template = """GPT4 Correct User: {prompt}<|end_of_turn|>GPT4 Correct Assistant:"""

tokens = tokenizer(
    prompt_template.format(prompt=prompt),
    return_tensors='pt'
).input_ids.cuda()

# Generate output
import time
t0 = time.time()
generation_output = model.generate(
    tokens,
    streamer=streamer,
    max_new_tokens=256,
)
print("duration: %s" % (time.time() - t0), flush=True)

import time
t0 = time.time()
generation_output = model.generate(
    tokens,
    streamer=streamer,
    max_new_tokens=256,
)
print("duration: %s" % (time.time() - t0), flush=True)

time.sleep(100)

I understand why users might report this as an issue. Previously, we hard-coded rope_theta=10000 in 0.1.7 but in 0.1.8, we read it from the config. The model linked just so happens to have rope_theta=1000000 which might be a bit slower.

So you can explain the ~1s delay between the first token and the 2+ tokens?

I am not able to explain it without further checking out between commits, which I won't have time to do right now. A potential issue is the change in how we handle position ids. Tough to say without thorough testing.

Understood, I haven't seen such a massive lag before in other tools, and 0.1.7 doesn't do it.  I'll recommend users use 0.1.7 if they are concerned. Thanks!

Closing this issue as not planned for now, I am not having an easy time reproducing the suggested delay that was introduced.


Fix issue #38

@plocket - I didn't change phone-number-validation.yml to conform to the name convention, just so that you can see what's changed in the file itself. Feel free to change the name yourself or let me know if you want me to change, or we just leave it alone.

We might want to add a future goal to use getValidationError of the phone number validation library (https://www.npmjs.com/package/intl-tel-input#user-content-public-methods), along with the validate customDataType class method (https://docassemble.org/docs/fields.html#custom datatype) to give better error messages to the user.
We could also try to manage client-side validation so they don't have to press 'continue' to get the validation message.

I do want to change the name of the file, but only once we're done reviewing the changes to the code.


increase version to 3.6.3-SNAPSHOT

... since 3.6.2 is already released.

I will update that to 3.7.0-SNAPSHOT since I don't think we will have another bugfix release.
Thanks anyway.


How to multiple spinners at once?

Hi there.
Say I have 3 concurrent processes running at the same time can I have 3 spinners running at the same time, displaying one for each process? I've tried the naive approach of creating a spinner for each process but the spinners overwrite each other, competing for stdout.
Is it possible?
Cheers!

Hi @TotalSynthesis
Great question and one I wish I could give a better answer to than, no.  It's a feature I've wanted to add for the life of the project but have never gotten around to adding it.  I can play around with it a little today to see if I can find a way to make it work.  Please let me know if you figure out a way.
You're more than welcome to submit a pull request with this functionality.


use fseeko64,ftello64 in android when api level >= 24

This should be fixed. I used a different branch to resolve merge conflict.


Add deleteEvent feature

Typo in the latest commit:
Edit class descriptor of DeletEventCommand
Should be:
Edit class descriptor of DeleteEventCommand


[BSI][20210621] Usage of Outdated Components

Rating:
low
Description:
The cwa-quick-test-backend relies on the third-party com.upokecenter CBOR library. The pom.xml specifies the version
4.0.1 which was released in late 2019. The current version is 4.4.3 released in May 2021.
In the context of another (mobile) application known to the testers, which uses the same library, a denial-of-service vulnerability could be identified. In this context, it was possible to construct a CBOR object which caused the app to be caught in an endless loop. The issue was mitigated by updating to the most recent version of the library.
Affected components:
cwa-quick-test-backend
Proof of concept:

Suggested controls:
The dependency should be updated to the newest version to ensure that functional and security-related fixes are included. Additionally, a process should be put in place that handles dependency versions and updates them accordingly.

will be fixed with #145


Duplicate IDs

This is an odd one, and I don't know if it can be replicated.
I have 3 different patients with the same ID - P00001. They were the first 3 patients created on the system and I didn't notice it happening at the time. Subsequent patients have incremented IDs. Presumably the system should not be able to do this?
I don't know how to replicate this one as all newly-added patients have unique IDs.

I don't really remember, but it was probably a combination of different
browser, same pc and possibly another - but not at the same time!
I know that's not very helpful, but I just noticed it tonight and thought
it was strange.
On Mon, 9 Jul 2018, 22:27 Matthew Dorner<EMAIL_ADDRESS>wrote:

I have done a lot of creating test patients and never seen this. Did you
do anything special with the patients or just enter them into the system? I
wonder, did you possibly enter the patients from different client PCs?
Sounds like something that could happen with databases being out of sync on
multiple clients.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/HospitalRun/hospitalrun-server/issues/112#issuecomment-403625989,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZtkQk9omsVGbXsaYEazu85u-sWt9-PFks5uE8q7gaJpZM4VIZCy
.

it's happening if I use Firefox, but not Chrome. To reproduce:

start with a database having >0 patients in it
close HospitalRun tab and erase Firefox browser cache
log in to HospitalRun, view list of patients. It will (incorrectly) show 0 patients. waiting for the database to sync doesn't seem to make any difference.
add a patient. it will get P00001 even if that ID is already in use
you will now also be able to see all the patients

same thing happens with inventory items. good thing you noticed, I will try to figure it out.

OK, this behavior occurs if you refuse Push notifications. That's the pop-up that says something like "This website wants to send you notifications. Allow / Deny". And this is because the Push API is used to sync the database. Maybe it should be made more obvious that users need to Allow, since I and others Deny these requests out of habit.

Indeed, I think it would need to be made explicit as many people refuse pop-ups routinely.
When I have installed hospitalrun, I usually accept the data storage request, but I don't think the push notification request shows every time if you have previously declined it.

I'm going to close this issue and move it over to the front-end


Small issue in the cairo binding

>>> return tostring(require('lgi').cairo.PathData._field.header[3])
stdin:1: '__tostring' must return a string
stack traceback:
	[C]: in function 'tostring'
	stdin:1: in main chunk
	[C]: in ?
>>> return getmetatable(require('lgi').cairo.PathData._field.header[3]):__tostring()
nil

And similarly for cairo.PathData._field.point. I got this error by attempting to perform a recursive dump on _G; I'm not sure where else it may come up.

Looks like the third argument of component.create is supposed to be the name. According to git grep, there are many calls to that function with just two arguments (not just in cairo).
A possible fix (besides fixing all callers) might be:
diff --git a/lgi/component.lua b/lgi/component.lua
index a6803ae..d15a177 100644
--- a/lgi/component.lua
+++ b/lgi/component.lua
@@ -319,7 +319,7 @@ function component.create(info, mt, name)
    end

    -- Fill in meta of the compound.
-   local component = { _name = name }
+   local component = { _name = name or "__unnamed__" }
    if gtype then
       -- Bind component in repo, make the relation using GType.
       component._gtype = gtype

@fstirlitz What's your Lua version? My Lua 5.2 does not really complain here:
> return tostring(require('lgi').cairo.PathData._field.header[3])
nil

@pavouk I'll leave it up to you to fix this. I don't know if all callers should be fixed or the implementation should work around this issue (as in the above example patch). Also, no idea what good names for these things would be.

I use Lua 5.3.
I'd rather use something that isn't a valid identifier instead of "__unnamed__" to avoid the usual problems with in-band signalling.


Add support for --watch option

tye run supports passing --watch as an argument. It would be awesome to be able to do this with this plugin!
https://github.com/dotnet/tye/blob/main/docs/reference/commandline/tye-run.md
Thanks for the awesome plugin!

Thank you for the feedback!
I will try to add this in the next release.

Hello @ChristopherHaws. New version is available now.


Add instructions on how to build dev environment

What this PR does / why we need it:
This commit enhances the CI playbooks to allow deploying from master branch and adds documentation on how to use them to deploy a development environment.
Release note:
NONE

/approve

@dulek I'll try this on my local VM and let you know if it works smoothly.

@dulek works great
/lgtm

/cherry-pick release-1.28
/cherry-pick release-1.27
/cherry-pick release-1.26

Honestly I wouldn't bother too much with backporting this, it's just a development script.


Develop

dithillobothrium  wants to merge 4 commits into dithillobothrium:develop from toxa81:develop

well, ok...


Create some samples for Swift equivalent to existing node.js ones

Adding various samples mentioned in issue #284

This pr depends on issue #457

I will be adding a split util as well for swift.  I am not going to include it as part of cat like we do for nodejs since this makes no sense and nobody is even aware that it exists as a separate parameter for cat.  I will separate it out for nodejs as well.

looks good.   Please reference a PG when ready to merge.

PPG 528

rebased and merged

@csantanapr does this require updating docs for cat vs split?

I did find a doc update that is needed for the change in the existing cat action and will do that as part of issue #467


Update Tilt configuration files to restore functionality

Update Tilt configuration to update references to the new path of the catalogd Tiltfile thereby restoring all previous tilt functionality

Linked to internal Jira issue EET-4416.


Support extensibility for exports

This updates the namedExports() method to be a more general exports() method that for now simply exposes an { export: string }.
From recent discussions, this allows us future extensibility, if we want to support fine-grained bindings analysis (https://github.com/tc39/proposal-esm-phase-imports/issues/20), or also to support possible module declarations analysis in future (https://github.com/tc39/proposal-esm-phase-imports/issues/19).

This is no longer relevant with https://github.com/tc39/proposal-esm-phase-imports/pull/22.


License clarification

I've seen that the repository is listed as MIT license, but checking files headers I've seen they mention "the Microsoft License".

Which one is the right one?

Thanks for reporting this. We have updated the project headers.


[TW#28767] HID : Is there a way to know if we are connected with an Iphone or an Android phone ?

Hello,
I'm developing an HID device using HID over BLE example stack provided in the esp-idf example and i would like to know if there is a way to know if the device is connected with an iphone or an android. Indeed, it seems that the report map behavior is not interpreted in the same way according to the platform so i need to know with which platform i'm connected to give the right report map.
Regards,
Aurélien

@Marc-Aurele  Iphone mobile phone has a dedicated server, such as ANCS.

Hello @Yulong-espressif ,
Thank you very much for the reply. I fanally make all i want except i have some unexpected behavior with iphone. First of all, for launching the voice assitant, i send an AC_HOME event for 1 second but when my phone is asleep; it wakes up the phone but then all event that i will send won't be interpreted anymore by the iphone.
My second issue occurs sometime at pairing. Most of the time all is working fine but sometime pairing seems to be ok but every event i send to the iphone are not interpreted. I have noticed in that case that i don't see the following event "ESP_GAP_BLE_UPDATE_CONN_PARAMS_EVT" in the gap_event_handler function whereas when all is working fine, this event seems to be propagated.
Regards,
Aurélien


Add support for validation and custom types

 Issue by clmcgrath
Monday Jun 26, 2017 at 18:21 GMT
Originally opened as https://github.com/gsscoder/commandline/issues/455

Add some sort of hook or attribute to plug validation into the parser pipeline
similar some similar frameworks use attributes or factory registration to allow an entrypoint for custom validation and type mapping (DI support would be awesome as well ;) )
a typical and widely used usage scenario for this would be filesystem path validation and mapping to IO classes such as FileInfo / DirectoryInfo
an seemingly easy way to  to add this type of validation functionality  would be to allow validation attributes  that inherit from a validation base class or interface and  run custom  or pre-written code
some examples of validation provided in similar frameworks are
[FileExists]
[DirectoryExists]
[FileNotExists]
[DirectoryNotExists]
[RegExValidation]

Powerargs provides a special class called a Reviver for custom type mapping  as well  that the framework looks for to try and map values to a custom or complex type ie  path string  => FileInfo
It is very hard to find a framework that does all 3 of these well currently and make this library a go to framework for myself and many other developers i am sure
as CLP 2.x is still in beta and major rewrite phase i think now would be a good time to look at feature expansion as well to increase the power of this framework

 Comment by stanislavromanov
Wednesday Jul 26, 2017 at 13:56 GMT

IMHO this would be overkill and it destroys the single-responsibility-principle aspect of this library.

 Comment by nemec
Wednesday Jul 26, 2017 at 17:55 GMT

@stanislavromanov what if it was set up to allow you to plug in an existing validation library (e.g. FluentValidation) that's run after all parsing or after each argument is parsed? The validations mentioned in the OP would either be built in (but optional) or compiled to a separate nuget and you could always design your own.

 Comment by clmcgrath
Wednesday Jul 26, 2017 at 23:40 GMT

@stanislavromanov,  i agree and disagree with you on this,  without some sort of validation mechanism or custom mapping mechanism it really limits what can be used as an argument  ie : FileInfo DirectoryInfo mapping,  DateTime , TimeSpan, DateTimeOffset , are a few examples for mapping ,   being able to validate path exists is a good example of a custom validation , or an argument is in specified range .. I don't think allowing business rules in your parsing pipeline violates SRP and is a quite common requirement and a feature of many libraries,

 Comment by ohadschn
Thursday Nov 02, 2017 at 19:43 GMT

+1 from me.
If I have to do my own validation, not only do I need to write code for annoying things like parsing and regex matching, I also don't get the benefits of automatic help text display on parsing errors (including the text that explains exactly what went wrong in the parsing).

Fighting this battle right now as well validating if a file actually exists on disk. I don't see an easy way to add a custom error to the help text and display the help text after successful parsing is done.
Is this possible?

So realistically, this is a parsing library and all the validation is around successful parsing of strings to numbers etc.
[FileExists], [DirectoryExists], [NetworkServerReachable], [AmazonServiceHasItem] and similar, would definitely be out-of-scope for a library like this.
For things like File Doesnt Exist, your best bet is probably after parsing, run through your use-case validations, (ie file exists, amazon service has item, etc) and invoke the Help to display usage, and display your validation message afterwards in red or different color... "File specified 'xxx.txt' doesn't exist"

That would work. Do you know what snippet I would need to run in order to pull the current help usage text? Right now, I have this:
private static Options parseArgs(string[] args)
        {
            ParserResult<Options> result = Parser.Default.ParseArguments<Options>(args);

            if (result.Tag == ParserResultType.NotParsed)
            {
                return null;
            }
            else
            {
                var parsedResult = result as Parsed<Options>;
                Options o = parsedResult.Value;

                if (!File.Exists(o.Solution))
                {
                    Console.WriteLine($"Solution file does not exist: {o.Solution}");
                    return null;
                }

                return parsedResult.Value;
            }
        }

I would love to be able to pull the "usage" text from the parsedResult somehow and include that in the error message.

You almost need to return ParserResult from that instead, so you
won't have a null return that you'll have to guard against.
Next, I'd have a ValidateOptions method that would then roll through the
various specified options and check them for validity, and return a
ValidationResults type of structure,
Which would then be processed by a ParseAndValidate method that would be
responsible for analyzing the ParserResult from parseArgs and
deciding if it needs to display usage and/or exit with a non-zero error
code.  Realistically a non-existing file wouldn't generate a usage banner,
but your ParseAndValidate method could do that, and calling the GetHelp
routines to output the usage banner.
Sorry i'm a little vague on the GetHelp routines, mainly because I picked
up the project trying to push the v2 changes into a release state after the
original author disappeared into contract work (I'm assuming)
On Tue, Mar 13, 2018 at 1:24 PM, Eric Johnson<EMAIL_ADDRESS>wrote:

That would work. Do you know what snippet I would need to run in order to
pull the current help usage text? Right now, I have this:
private static Options parseArgs(string[] args)
{
ParserResult result = Parser.Default.ParseArguments(args);
        if (result.Tag == ParserResultType.NotParsed)
        {
            return null;
        }
        else
        {
            var parsedResult = result as Parsed<Options>;
            Options o = parsedResult.Value;

            if (!File.Exists(o.Solution))
            {
                Console.WriteLine($"Solution file does not exist: {o.Solution}");
                return null;
            }

            return parsedResult.Value;
        }
    }

I would love to be able to pull the "usage" text from the parsedResult
somehow and include that in the error message.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/commandlineparser/commandline/issues/146#issuecomment-372748635,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACG_zOoZud1x5vqP9DeTMGzTqBdPNl0Yks5teADZgaJpZM4QSHQ7
.

--
E.Newton
Senior Software Craftsman
Cell:<PHONE_NUMBER>
EMail<EMAIL_ADDRESS>

The GetHelp routines are a bit difficult to use since most of it is marked internal, but you are in luck - with ParserResult<Options> result it's quite easy to generate the help text:
var help = HelpText.AutoBuild(result);
Console.WriteLine(help.ToString());

@ericnewton76:
Speaking to the original issue, I feel like this might be a case where inversion of control is more headache than its worth. Rather than concocting some way for CommandLineParser to call a plug-in validator, it might be a lot easier and cleaner to just provide more/better opportunities for the recipient of parser results to call back into the parser's output logic.
I'm even less familiar with HelpText and friends, but as @nemec points out, most of the help logic is marked internal, so about the only control we have over output is the onError delegate argument of AutoBuild<T>(). That's fine except that HelpText doesn't expose enough to inject error messages (without getting really hacky) and, of course, it only gets invoked in the context of errors.
If we had more building blocks like BuildHeaderText(), BuildOptionsText(), etc. then you could suppress and inject output pretty much any way you'd like, whether or not the parsing succeeded.
Because there are cases of actual syntax checking that are simply too complicated or specialized to fit into a general command line parser. For instance, a company might have a standard format for project numbers. That's a syntax issue, but I think it's fair to say that it's beyond the scope of CommandLineParser's niche. So it would be good to be able to augment it with a more sophisticated validator somehow.

If you can provide a custom validator instance, used for specific custom validation, it should handle minimum modifications in the CommandLine lib, and respect SRP.
I think to something like this :
            parsed.MapResult(
                (Verb1Options opts, Validator validator) =>
                {
                    if(opts.ValueToCheck != "thegoodvalue")
                        validator.ValidationError("The value should be like thegoodvalue");
                    return 0;
                },
                (Verb2Options opts, Validator validator) =>
                {
                    ....
                    return 0;
                },
                errs => 1);

If a single validator.ValidationError() call happens, then we should call the errs => 1 delegate, and WriteOut the custom message on the console.

Is there still interest to add validation capabilities to the framework?
I am thinking about adding to Option an optional Func<Error> which contains user-provided validation logic and runs after parsing is done.
The approach listed by @rducom would also be good IMHO.
In any case, I think it's an useful addition to the library.

I did a first "draft" thinking about custom validations in 3a689998bdad1dc959f3c5dbff526064c57b1925. Maybe somebody will have a look before providing more validations. A test case shows the general usage.

Is there any progress on this?
If not, at the current state of things, what would be the best place to perform such validation as checking if the provided path is valid?

I would like an abstract base class or interface like:
public class MyOptions : IValidatedOptions {
    [Option('s', "something", Required=true, HelpText="Some option")]
    public string Something {get;set;}

    // From Interface
    public bool Validate(){
      if(!Util.CheckSomething(Something))
        return false; // this automatically tells CommandLineParser to fail the parsing and print the help.
    }
}

Alternatively instead of bool it could return some kind of new ValidationError("Reason for failing").

The library support validation in set property as described here:
It integrate the validation Exception Messages with ERROR(s) in help.

@moh-hassan
This is fairly limited, as we don’t know the order in which the properties are set, and if an option might or might not be valid depending on another parameter, there isn’t a way to do it.

@p-kaczynski
The limitation of Property Setter validation can be enhanced by submitting a new PR.
I find your approach of IValidatedOptions is promising and it can be executed at the final stage of Parsing.

Python's command line parser uses the type= option to do this.
https://docs.python.org/2/library/argparse.html#type

@donnyv
Yes, Python validation  is similar to the property setter validation in commandLineParser.
What about if validation is applied per property and  one property is depending on another one?

The way I do this in the meantime is by adding a Validate method to my options class:
[Verb("open", HelpText = "Open the foo file")]
public class FooOptions
{
    [Option('f', "fooPath", Required = true, HelpText = "Foo")]
    public string FooPath { get; }

    protected FooOptions(string fooPath)
    {
        FooPath = fooPath;
    }

    public void Validate()
    {
        if (!File.Exists(FooPath))
        {
            throw new ArgumentValidationException($"Foo path does not exist!");
        }
    }
}

The exception I'm throwing is just a custom type:
class ArgumentValidationException : Exception
{
    public ArgumentValidationException(string message) : base(message) { }
}

And in my parsing code I do something like this:
static int Main(string[] args)
{
    try
    {
        return Parser.Default.ParseArguments<FooOptions>(args)
            .MapResult(
                (FooOptions opts) =>
                {
                    opts.Validate();
                    //do something with opts.FooPath
                    return 0;
                },
                errors => 1);
    }
    catch (ArgumentValidationException e)
    {
        Console.WriteLine("Invalid arguments detected: {0}", e);
        return 1;
    }
}

@ohadschn How about custom types? Like ObjectId in Mongodb C# library.

@donnyv presumably a custom type can be initialized by primitives. In the case of MongoDB ObjectId it looks like it can be created from a string. So the options class could look like this:
[Verb("get", HelpText = "get a Mongo object")]
public class MongoOptions
{
    private readonly string _objectIdStr;
    [Option('o', "objectId", Required = true, HelpText = "MongoDB Object ID")]
    public string ObjectIdStr =>
       throw new InvalidOperationException($"You should use the {nameof(ObjectId)} property");

    private ObjectId _objectId;
    public ObjectId ObjectId => _objectId;

    public MongoOptions(string objectIdStr)
    {
        _objectIdStr = objectIdStr;
    }

    public void Init()
    {
        try
        {
            _objectId = new ObjectId(_objectIdStr);
        }
        catch (Exception e)
        {
            throw new ArgumentException("Error initializing MongoDB object ID", e);
        }

        Validate();
    }

    public void Validate()
    {
        if (_objectId.CreationTime < DateTime.Now.AddYears(-3))
        {
            throw new ArgumentValidationException($"Object too old!");
        }
    }
}

And you would call Init instead of Validate in your parsing logic (e.g. Program.Main).

Hi,
Any news about this subject ?
I need to do a custom validation, and when this custom validation fails, I would like to use the error flow (RunErrors) and not the normal flow (Run) :
            var parserResult = parser.ParseArguments(args, optionsClasses);
            parserResult.MapResult(Run, errors => RunErrors(errors, parserResult, args));

I found the idea of @p-kaczynski very good :
If we have an interface like he describe IValidatedOptions, it's exactly my need...
Regards
Sybaris


Move images to ./docs/images

I've moved the images to ./docs/images.
You can also create a GitHub Page from the ./docs folder, see https://help.github.com/articles/configuring-a-publishing-source-for-github-pages/

thanks a lot :+1:


twister: add options to shuffle tests across subsets

Add option to shuffle tests (randomly) before they are split into subsets.
This allow to fairly distribute tests across subsets,
so that long tests are not crowded in a single group.
This also allows to detect unwanted dependencies in test execution order.
Also, added option to provide custom seed to random generator
used to shuffle tests.
This will allow to reproduce certain test order if needed.
Used seed is printed at console.

This option only works when used with --subset flag. Please add a check in arg parser to quit with error if one tries to call twister with --shuffle-tests/--shuffle-tests-seed but without --subset.

Thanks ;)
Done as suggested:

there is info about required commands in help message
there is check if needed arguments were provided


Failover Clustering/Deploy: Set-ClusterQuorum URL

Description:
As reported in issue ticket #4454 (Set-ClusterQuorum link is outdated), the link URL for Set-ClusterQuorum is outdated by currently using an old TechNet link permanently redirected to docs.microsoft.com and that the page belongs to the "Windows Server 2008 R2 and 2008" subdirectory of the Previous Versions hierarchy. Better to use a more updated page.
Thanks to @grayjeremy (Jeremy Gray) for pointing out this issue.
Changes proposed:

Replace the old TechNet URL with the new PowerShell page URL
Typo correction: "Configue" -> Configure
Whitespace and codestyle adjustments:

Remove redundant end-of-line blanks (53 lines)
Add a blank line between metadata and the page title
Normalize H2/H3/H4 headings by adding blank line after (10 lines)
Standardize on hyphens as bullet point list indicators (3 lines)
Standardize on 1 blank line above image link (1 line)

Additional note: When reviewing this PR source, it is recommended to use the Hide whitespace changes feature for readability, because git reacts to the changes in number of lines and messes up the line order between old and new lines, mostly because of the added blank lines.
Ticket closure or reference:
Closes #4454

#sign-off

What is the MS Docs team review plan status for this PR?

#sign-off

Going to make a new PR to resolve the file conflict. See you later.


AMD GPU

Hi,
Were you able to run this in an AMD GPU like AMD Ryzen 9 7950X ?
If so can you please advise how to set it up for and AMD GPU ?
Thanks
Hakan

AMD is not supported at the moment. I am hoping the open-source community can come together to support AMD GPUs for AWQ at some point.


Test devbot

Summarize the results of the make test command

I apologize, but I couldn't find the necessary information about the environment variables in the repository. It seems that the required files are either missing or inaccessible. Please make sure that the repository contains the appropriate documentation or configuration files that specify the required environment variables.

maybe you should check .env.template


when websocket execute webSocket.close(1000, null),WebSocketListener onfailue java.net.socketexception:socket closed

when websocket execute webSocket.close(1000, null),WebSocketListener onfailue java.net.socketexception:socket closed

Please post a reproduction on stackoverflow for community support.

Hello, I also encountered the same situation, how did you solve it?


Exit code of kubectl config delete-* is not unified

What happened?
Only exit code of kubectl config delete-user is 1
$ kubectl config delete-cluster || echo $?
Delete the specified cluster from the kubeconfig.

Examples:
  # Delete the minikube cluster
  kubectl config delete-cluster minikube

Usage:
  kubectl config delete-cluster NAME [options]

Use "kubectl options" for a list of global command-line options (applies to all commands).

$ kubectl config delete-context || echo $?
Delete the specified context from the kubeconfig.

Examples:
  # Delete the context for the minikube cluster
  kubectl config delete-context minikube

Usage:
  kubectl config delete-context NAME [options]

Use "kubectl options" for a list of global command-line options (applies to all commands).

$ kubectl config delete-user || echo $?
error: user to delete is required
See 'kubectl config delete-user -h' for help and examples
1

What did you expect to happen?
Exit code of kubectl config delete-user is 0
How can we reproduce it (as minimally and precisely as possible)?
Run kubectl config delete-user
Anything else we need to know?
https://github.com/kubernetes/kubernetes/blob/a87612b6676723b34a5b3d2d80ab4e04552221ae/staging/src/k8s.io/kubectl/pkg/cmd/config/delete_cluster.go#L61-L64
https://github.com/kubernetes/kubernetes/blob/a87612b6676723b34a5b3d2d80ab4e04552221ae/staging/src/k8s.io/kubectl/pkg/cmd/config/delete_context.go#L61-L64
https://github.com/kubernetes/kubernetes/blob/a87612b6676723b34a5b3d2d80ab4e04552221ae/staging/src/k8s.io/kubectl/pkg/cmd/config/delete_user.go#L87-L89
Kubernetes version

$ kubectl version
Client Version: v1.28.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.29.4-eks-036c24b

Cloud provider

All

OS version

$ uname -a
Darwin tagawahirotakanoMacBook-Pro.local 23.5.0 Darwin Kernel Version 23.5.0: Wed May  1 20:12:58 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6000 arm64

Install tools

Homebrew

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)

/triage accepted
/kind feature
/remove-kind bug
Add to https://github.com/kubernetes/enhancements/issues/2551


[Feature Request] Support Oreo Colored Media Notifications

https://arstechnica.com/gadgets/2017/09/android-8-0-oreo-thoroughly-reviewed/3/#h3
Would look super slick if Kore would do this and ALSO display media art on the lockscreen like other media apps (Netflix, Yatse, Google Play Music, etc.).

Thanks for reporting this. I tested on an emulator and it seems that notifications don't work at all on Oreo. Can you confirm?
The following warning is what logcat shows regarding the issue.
12-30 20:45:47.238 4377-4377/org.xbmc.kore.instrumentationtest W/Notification: Use of stream types is deprecated for operations other than volume control
12-30 20:45:47.238 4377-4377/org.xbmc.kore.instrumentationtest W/Notification: See the documentation of setSound() for what to use instead with android.media.AudioAttributes to qualify your playback use case
12-30 20:45:47.240 2062-2105/system_process E/NotificationService: No Channel found for pkg=org.xbmc.kore.instrumentationtest, channelId=null, id=1, tag=null, opPkg=org.xbmc.kore.instrumentationtest, callingUid=10085, userId=0, incomingUserId=0, notificationUid=10085, notification=Notification(channel=null pri=0 contentView=org.xbmc.kore.instrumentationtest/0x7f04005f vibrate=null sound=null defaults=0x0 flags=0x42 color=0x00000000 category=transport vis=PUBLIC)

They show for me on 8.1.0 on my Pixel 2 XL.
https://imgur.com/vjx7SrY

Notifications work on Oreo with the latest build.
Does the instrumentatioTest build issue notifications? In Oreo they need to
be posted to a channel (I've done that but not on the tests)
On Dec 30, 2017 20:54, "carlylemiii"<EMAIL_ADDRESS>wrote:

They show for me on 8.1.0 on my Pixel 2 XL.
https://imgur.com/vjx7SrY
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/xbmc/Kore/issues/499#issuecomment-354567763, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFwrQHjUH8JPEwBrvdtjt1c3m-vICz0vks5tFqLpgaJpZM4RPePG
.

Ah I see you already fixed the issue in 3077653dd9f815052161565766f4a6a5a418d01a.
I didn't notice there were changes on master. Commits directly pushed on master don't sent notifications unfortunately...
@carlylemiii thanks for posting the screenshots. I must say that I actually find the Yatse notification worse. Hopefully it's a Yatse issue and with a proper poster image the new notification will look good as well.

@poisdeux yeah, it doesn't look great with the poster being cropped. My point was showing how it auto-colors like other media apps and how it's a fuller-sized notification.

Looks like Kore need implement MediaSession for Colored Media Notifications

Adding to my previous comment, there will likely need to be some "hacks" happening to get the notification lookin' good. The Yatse developer improved this notification - it takes away the smooth blending somewhat, but it adds the color and makes it so the poster isn't cropped terribly.


helm-operator will be templated via CI and commit to PR on upstream release

Details
Describe the solution you'd like:
When the upstream helm charts or maintainers provide a new official release the helm-operator should be able to be templated via CI and create a PR with the proposed upgrade within the repository.
Anything else you would like to add:
It could even be possible that the particular PR is using Flagger to test the upgrade before complete rollout
Additional Information:
N/A

Fixed: #13


feat: port Algebra.Module.Pi

One earlier failure was extensively discussed:

https://leanprover.zulipchat.com/#narrow/stream/287929-mathlib4/topic/Performance.20issue.20with.20.60CompleteBooleanAlgebra.60/near/319019205
https://leanprover.zulipchat.com/#narrow/stream/270676-lean4/topic/type.20class.20inference.20looping

and is fixed as of https://github.com/leanprover/lean4/commit/70a6c06eef060d8e14869e2848749287e5364742, in mathlib as of the bump #1335.
Another failure posted to Zulip and the Lean 4 repo

https://leanprover.zulipchat.com/#narrow/stream/270676-lean4/topic/type.20class.20inference.20failure.20in.20pi.20type
https://github.com/leanprover/lean4/issues/2011

This one is temporarily fixed with a workaround posted by Gabriel, and can return to the mathlib3 spelling after https://github.com/leanprover/lean4/commit/fedf235cba35ed8bf6bf571cf38e6d8536b904ac makes it downstream to mathlib.
There is one failure left.  It looks like a pain to isolate; I think it's worth waiting until https://github.com/leanprover/lean4/commit/fedf235cba35ed8bf6bf571cf38e6d8536b904ac makes it downstream in case that fixes it for free.

[x] depends on: #1397

One of the errors will be fixed after https://github.com/leanprover/lean4/commit/70a6c06eef060d8e14869e2848749287e5364742
makes it downstream to mathlib.  Might as well wait and see if all of them are.
Zulip

This PR/issue depends on:

leanprover-community/mathlib4#1397
By Dependent Issues (🤖). Happy coding!

This PR/issue depends on:

leanprover-community/mathlib4#1397
By Dependent Issues (🤖). Happy coding!

bors r+


Add CompositeCancelable.getAndResetTo

We have the following use-case: given a set of cancelables, we want to reset it to some other set of cancelable references, returning the old set.
This is used for example in Observable.firstStartedOf to pick a winner and cancel the rest.

It's on master.


Translation Delivery

Translation Delivery

This pull request is for translation delivery. Please review and approve them.

Here are two dots at the end of the sentence: https://github.com/corona-warn-app/cwa-app-android/blob/a1110d3d0906273936ef1db7e8024ec581f8dfbc/Corona-Warn-App/src/main/res/values/strings.xml#L261
This should be fixed.

Here are two dots at the end of the sentence:
https://github.com/corona-warn-app/cwa-app-android/blob/a1110d3d0906273936ef1db7e8024ec581f8dfbc/Corona-Warn-App/src/main/res/values/strings.xml#L261
This should be fixed.

@Ein-Tim
is it part of this PR? I don't see it here

@mtwalli No, but I suggest to change it either with this or the next PR (-:

@mtwalli No, but I suggest to change it either with this or the next PR (-:

This is a translation of newly added/changed strings . Please file a separate issue ?

@Mtwalli
FYI: https://github.com/corona-warn-app/cwa-app-ios/pull/4066#pullrequestreview-848171943
I'll go ahead and file a new issue, but as you can see in the PRs linked to from my comment, @marcuscc stated that this should be fixed with the next translation delivery.

@mtwalli Issue https://github.com/corona-warn-app/cwa-documentation/issues/803 created.

@Ein-Tim If you see the repo where this PR was initiated. you will notice that is not part of cwa-android. Translation delivery comes from the translation team, if we do the change you suggest here it will be overridden with the next delivery. So it is better to file an issue so translation team can take of it. I hope that is clear now

This pull request is for translation delivery. Please review and approve them.


ARROW-10292: [Rust] [DataFusion] Simplify merge

Currently, mergeExec uses tokio::spawn to parallelize the work, by calling tokio::spawn once per logical thread. However, tokio::spawn returns a task / future, which tokio runtime will then schedule on its thread pool.
Therefore, there is no need to limit the number of tasks to the number of logical threads, as tokio's runtime itself is responsible for that work. In particular, since we are using rt-threaded, tokio already declares a thread pool from the number of logical threads available.
This PR removes the coupling, in mergeExec, between the number of logical threads (max_concurrency) and the number of created tasks. I observe no change in performance:

Benchmark results
Switched to branch 'simplify_merge'
Your branch is up to date with 'origin/simplify_merge'.
   Compiling datafusion v2.0.0-SNAPSHOT (/Users/jorgecarleitao/projects/arrow/rust/datafusion)
    Finished bench [optimized] target(s) in 38.02s
     Running /Users/jorgecarleitao/projects/arrow/rust/target/release/deps/aggregate_query_sql-5241a705a1ff29ae
Gnuplot not found, using plotters backend
aggregate_query_no_group_by 15 12
                        time:   [715.17 us 722.60 us 730.19 us]
                        change: [-8.3167% -5.2253% -2.2675%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 3 outliers among 100 measurements (3.00%)
  1 (1.00%) high mild
  2 (2.00%) high severe

aggregate_query_group_by 15 12
                        time:   [5.6538 ms 5.6695 ms 5.6892 ms]
                        change: [+0.1012% +0.5308% +0.9913%] (p = 0.02 < 0.05)
                        Change within noise threshold.
Found 10 outliers among 100 measurements (10.00%)
  4 (4.00%) high mild
  6 (6.00%) high severe

aggregate_query_group_by_with_filter 15 12
                        time:   [2.6598 ms 2.6665 ms 2.6751 ms]
                        change: [-0.5532% -0.1446% +0.2679%] (p = 0.51 > 0.05)
                        No change in performance detected.
Found 7 outliers among 100 measurements (7.00%)
  3 (3.00%) high mild
  4 (4.00%) high severe

Note that there is an important note in Tokio's documentation:

If your code is CPU-bound and you wish to limit the number of threads used to run it, you should run it on another thread pool such as rayon. You can use an oneshot channel to send the result back to Tokio when the rayon task finishes.

I.e. Tokio's spawn is suitable for non-blocking, non-CPU-bound tasks. This may explain why we do not see a significant performance increase when using tokio::spawn: most of our tasks are CPU-bounded.

This looks great, but how do we control the concurrency now? The concurrency attribute in ExecutionConfig is now effectively unused.  think we should either create the tokio thread pool explicitly using the ExecutionConfig.concurrency value or remove this config entirely since it is no longer used.
Without being able to control the concurrency level it will be difficult (but not impossible) to run scalability benchmarks to see how we scale with an increasing concurrency level.

I wonder if the scope of this is too much. I really like this change and would like to see if merged. Perhaps we just remove the concurrency config and let users of DataFusion create their own tokio runtimes?

It would make sense to create the tokio runtime specifically in the benchmark crate and in the CLI but for other cases, we are being called as a library and should assume that the user has created the tokio runtime, I think.

@jorgecarleitao I see no reason to wait before merging this (unless you want to remove the concurrency attribute from ExecutionConfig as part of this PR since it no longer has any effect).

Ah, ok, I mistakenly understood that we were in a "feature freeze" until the release (which is why I have not been merging stuff these days).

I think there are some things we would want to hold off on merging, like
changing the Rust nightly version for example, or anything else we feel
would be risky at the last minute.
On Tue, Oct 13, 2020 at 12:07 PM Jorge Leitao<EMAIL_ADDRESS>wrote:

Ah, ok, I mistakenly understood that we were in a "feature freeze" until
the release (which is why I have not been merging stuff these days).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/arrow/pull/8453#issuecomment-707916680, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHEBRDSPNVFQAQLRA2BPVTSKSJO5ANCNFSM4SOBNGPA
.

Note that in the benchmarks, we can even specify different concurrency parameter depending on the benchmark (in case we want to perform some scaling).

For what it is worth, one thing I plan to do as part of my internal project, is to limit "concurrent CPU bound tasks" by using a tokio::sync::mpsc::Channel as a way to limit the maximum number of concurrent tasks.


Fix POS tags

We're now using part-of-speech and not part-of-speech-tagging, see discussion here: https://github.com/huggingface/datasets/commit/114c09aff2fa1519597b46fbcd5a8e0c0d3ae020#r78794777

CI failures are about missing content in the dataset cards or bad tags, and this is unrelated to this PR. Merging :)


CNV-47477: fix switching project from all-namespaces

📝 Description
Remove the useEffect that was causing a bug switching projects. Now the activeKey is not a state but we get it directly from the pathname.
useVirtualMachineInstanceTypes hook now has a third parameter that we need to use.
🎥 Demo
Before
https://github.com/user-attachments/assets/35d5985b-d2b9-4e88-8d92-89a7c4032a94
After
https://github.com/user-attachments/assets/2869fc22-d564-4b50-871a-7a0b3793352e

/cherry-pick release-4.17


Support draft-wright-json-schema-01 / draft6?

The newest draft is draft-wright-json-schema-01, aka draft6. The largest change (I saw) was making true a valid schema equivalent to {}, and false a valid schema equivalent to { "not": {} }.

I did a quick diff between draft4 and draft6 tests in https://github.com/json-schema-org/JSON-Schema-Test-Suite/tree/master/tests
It seems you are correct. draft6 allows boolean as valid schema. so only compilation has to be changed to support draft6
i will work on it.

seems there are quite a number additions and backward incompatible changes in draft6.
see complete changes in draft6 here

draft6 support is in progress in  branch draft6

draft6 implementation finished in branch draft6
needs final code-review and documentation update before merging to master

merged draft6 into master.


Syntactic sugar - allow easier config of @PactTestFor(providerName = "farmer", port = "8084")

Instead of writing
@PactTestFor(providerName = "farmer", port = "8084")

it would be nice to be able to provide a rest client config key (similar to what we set in @RegisterRestClient(configKey = "farmer-api"). That would give us the URL and should also allow us to work out a sensible default provider name.
Alternatively, we pass through a class name of a RestClient, just as we do with some other Quarkus tests.

See also #69, which is a more extreme version of this.

This would also allow us to provide different config for %test profiles, to avoid port conflicts between mock and real servers.


Fix sensitive values in outputs

https://github.com/cloudposse/terraform-aws-cloudfront-s3-cdn/issues/182
references

closes #182

Can we get this merged?

/test all

I believe sensitive is a terraform 0.15 feature
https://www.terraform.io/docs/language/functions/sensitive.html

Note: This function is only available in Terraform v0.15 and later.

We're currently have a pin to allow this module to work on terraform 0.13 and above
https://github.com/cloudposse/terraform-aws-cloudfront-s3-cdn/blob/47d70f2f66272b0dd11984168463b2fcd02eb9a1/versions.tf#L1-L2

Here's something else that's also interesting. The sensitive flag isn't even on the aws_cloudfront_distribution resource's argument origin.origin_id schema
https://github.com/hashicorp/terraform-provider-aws/blob/e26f89a007dbddb3d967a3b506a129e6605f4846/aws/resource_aws_cloudfront_distribution.go#L568-L572
If the output was sensitive, shouldn't it have the Sensitive: true flag enabled for it like for other resources ?