[JOSS review] Improve documentation

(Main review for JOSS happening here)
The current documentation is very very minimal and needs to be expanded to describe capabilities and usage.
More specifically, here are some of the issues I've seen:

The readme does not say what the package is about
The readme has broken links to your CI badges
The readme does not provide installation instructions
The "about" page in the documentation consist of a single diagram (the meaning of which is unclear to me)
The "installation" page points to a repository that is not GitHub
It is unclear what version of Python is supported, but the installation instruction recommends Python 3.8 and points users to a link to a version of Anaconda that is 2 years old.
The "pip install" method does no longer work for Debian 12+ or Ubuntu 23.04+ (see PEP 668). More distributions will probably follow soon.
The "installation" page also claims that there are no released versions.
The "contributing" page points users to LIGO servers
The "contributing" page does not mention pre-commit or coverage, but mentions pytest (which is not listed among the dependencies).
Why is there a pickle file in the repo? (Pickle file are not portable).
Most tutorials do not contain any explanation, are not well formatted, and some have warnings/errors.
Acronyms are used but not defined (e.g., SGWB, CBC).
The documentation for the APIs is also bare bones. For example, there are no explanations for functions/arguments, or types.

This list is not comprehensive and I would recommend designing the documentation from scratch.
Here is a good resource for a possible way to write effective documentation: https://documentation.divio.com/

Thank you! We are hard at work addressing this issue. Could this be turned into a checklist by any chance?

[ ] State of the field in the JOSS paper submission.

One more with the paper itself. The state of the field is a requirement in the paper. But there wasn't really any mention of the state of the field (eg. LALStochastic) and other packages, and what separates pygwb from those packages.

@Sbozzolo and @cmbiwer : thanks for your feedback! Several of the issues you point out are easy to resolve and we will update the documentation accordingly; there are a couple though that I am unsure how to address so let me post questions here.

I went through before looking at @Sbozzolo review. I wrote down basically the same issues and agree with @Sbozzolo . There is a lot missing from the documentation/tutorial and things currently point to URLs that require LIGO credentials.
I'll add a few more things though.

[ ]  Test suite seems to fail.

I installed pytest myself (see the comments above, its not there) and tried the test suite. I see two test fail; TestInterferometer.test_set_timeseries_from_channel_name and TestInterferometer.test_from_parameters.

Aside from the issues already mentioned. It says to do:
conda install .

From the dir above the repo.
That didn't work either there. And even cd into in the repo, it didn't work. Conda couldn't find the package; eg.:
$ conda install .
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.

PackagesNotFoundError: The following packages are not available from current channels:

  - .

Current channels:

  - https://conda.anaconda.org/conda-forge/osx-64
  - https://conda.anaconda.org/conda-forge/noarch
  - https://repo.anaconda.com/pkgs/main/osx-64
  - https://repo.anaconda.com/pkgs/main/noarch
  - https://repo.anaconda.com/pkgs/r/osx-64
  - https://repo.anaconda.com/pkgs/r/noarch

To search for alternate channels that may provide the conda package you're
looking for, navigate to

    https://anaconda.org

I ended up using python -m pip install . to try using the package.
It may just be my Anaconda version. But its not stated anywhere what version is required.

The failure of the test suite here seems to be due to a gwpy issue which (at least to my knowledge) was solved a while ago. Could you upload the full logs so I know what version you are running, etc?
Also, we run the testing suite in the pygwb gitlab repo, so that is why the CI badges are broken in the github version. Should I duplicate the testing also in github? It seems like a bit of a waste of computational resources. The gitlab repo is now public so you can see the test coverage there.

@Sbozzolo the reason there are pickle files as a part of the repository is because some of our tests depend on them; they are not part of the codebase itself (when packaging the code for distribution the test suite is omitted). Our objects are designed as data containers, at different stages of a GWB analysis, and the test suite is based on pre-compiled pickled versions of these objects. We have found this an effective way of keeping track of changes in the modules and objects, without having the test suite re-run the analysis every time.

[ ] The "about" page in the documentation consist of a single diagram (the meaning of which is unclear to me)

Now addressed here: 7ea65ea8621ae952e368bd8b2dd81e88abeefca6

@cmbiwer re:

[ ]  Test suite seems to fail.

I tracked this issue back and it is due to a backwards-incompatible change in the gwosc package; this was fixed in pygwb v.1.1, but the version you see here is the one associated to the ApJ paper, and thus does not have this change. I have gone ahead and updated (and cleaned up) the code here, removing the tag argument which was deprecated by gwosc. We will merge these changes into pygwb once the review is over. The documentation should now run.
See 213fa0cd7bbba3b2acc682977cd043209ca1a01d
(I could also have fixed the version of gwosc to an older one, to make the old v1.0.0 work; however, as I expect the changes we make here will eventually be merged with the current version of the code, I thought it would be more useful to update the code this way. I am also happy to go the other way.)

The failure of the test suite here seems to be due to a gwpy issue which (at least to my knowledge) was solved a while ago. Could you upload the full logs so I know what version you are running, etc?

This is the version it installed for me:
(pygwb) pn1618376:pygwb cmbiwer$ python
Python 3.8.16 | packaged by conda-forge | (default, Feb  1 2023, 16:05:36)
[Clang 14.0.6 ] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import pygwb
>>> pygwb.__version__
'1.0.1.dev4'

The failure of the test suite here seems to be due to a gwpy issue which (at least to my knowledge) was solved a while ago. Could you upload the full logs so I know what version you are running, etc?

This is the version it installed for me:
(pygwb) pn1618376:pygwb cmbiwer$ python
Python 3.8.16 | packaged by conda-forge | (default, Feb  1 2023, 16:05:36)
[Clang 14.0.6 ] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import pygwb
>>> pygwb.__version__
'1.0.1.dev4'

sorry - I meant gwpy version; in any case, I addressed this issue now in 213fa0cd7bbba3b2acc682977cd043209ca1a01d as mentioned above - please let me know whether the test suite now works with these changes :)
(note that the issue was coming from the fact that gwpy depends on gwosc, and although the version of gwpy installed by pygwb v1.0.0 is correct, gwpy doesn't fix the version of gwosc it needs and the break was coming from updates in gwosc)

Thank you! We are hard at work addressing this issue. Could this be turned into a checklist by any chance?

Sorry for the delay. I changed the list into a checklist. In this, let me remark again that this list summarizes my first impressions, so I'd encourage you to also think about the documentation beyond these points.

@Sbozzolo the reason there are pickle files as a part of the repository is because some of our tests depend on them; they are not part of the codebase itself (when packaging the code for distribution the test suite is omitted). Our objects are designed as data containers, at different stages of a GWB analysis, and the test suite is based on pre-compiled pickled versions of these objects. We have found this an effective way of keeping track of changes in the modules and objects, without having the test suite re-run the analysis every time.

I was under the impression that pickle files were not portable across versions/OSs, but it turns out that they are, as long as the same protocol is being used. Nonetheless, I think that sharing pickles is not the best idea. As the documentation clearly remarks, pickles are not safe. Moreover, they are opaque and can only be read by Python. If it is possible and not too difficult, I'd suggest moving to something like JSON. Also, if used only for tests, the file should not be at the root level of your repository.

Now addressed here: https://github.com/a-renzini/pygwb/commit/07926e35901c09130752054cab414bc18a352a0c

What branch should I look at when reviewing the code/documentation?

Sorry for the delay. I changed the list into a checklist. In this, let me remark again that this list summarizes my first impressions, so I'd encourage you to also think about the documentation beyond these points.

Thank you - yes I understand the documentation is very lacking, we are working hard on it. Apologies it is taking quite some time, we will keep updating here as we go along!

I was under the impression that pickle files were not portable across versions/OSs, but it turns out that they are, as long as the same protocol is being used. Nonetheless, I think that sharing pickles is not the best idea. As the documentation clearly remarks, pickles are not safe. Moreover, they are opaque and can only be read by Python. Finally, if you change the object in your code in a future version (or if an upstream package changes its code), the pickle might stop working. If it is possible and not too difficult, I'd suggest moving to something like JSON. Also, if used only for tests, the file should not be at the root level of your repository.

Apologies - I don't quite understand what you mean by "the file should not be at the root level of your repository". Should these be in a separate branch? Every time we update a part of the code, indeed the pickles "stop working", and we update them accordingly. We've found this to be a useful check of the structure of the code. I'm afraid moving to JSON, while surely possible, would remove a layer of the checks we do, so I would be slightly against that.

What branch should I look at when reviewing the code/documentation?

Please refer to the joss_submission branch.

Sorry for the delay. I changed the list into a checklist. In this, let me remark again that this list summarizes my first impressions, so I'd encourage you to also think about the documentation beyond these points.

Thank you - yes I understand the documentation is very lacking, we are working hard on it. Apologies it is taking quite some time, we will keep updating here as we go along!

Thank you! There's no hurry, the goal of this review is to help you built and publish an awesome package :)

Apologies - I don't quite understand what you mean by "the file should not be at the root level of your repository". Should these be in a separate branch?

The file is at the same level as the directories "docs", "pygwb", ....
However, this file is very technical and is used only for tests (as I understand). Wouldn't it more appropriate to put it in the "test" folder? This would immediately give users a sense of what the file is about.

Every time we update a part of the code, indeed the pickles "stop working", and we update them accordingly. We've found this to be a useful check of the structure of the code. I'm afraid moving to JSON, while surely possible, would remove a layer of the checks we do, so I would be slightly against that.

In the interest of maintainability of the package, I think it would be best to have readers/writers to standard formats, and unit tests over those readers and writers to restore the layer of checks. This would be a more robust solution for two reasons: (1) you use a stable and clear format, as opposed to an opaque pickle, (2) new developers would see the reader/writer functions with their unit tests, and they would be able to more easily understand what is going on and extend the package (suppose a test fails with a pickle error, how would the developer know what to do? If you have reader/writers with tests, the failing test would immediately point the developer to the right direction).
Of course, this is my suggestion, and you are free to pick your preferred implementation. In any case, make sure to document everything.

Addendum: I realized that there are more pickle files in the tests folder. I had "checkpoint.pkl" in mind when writing the message.

Addendum: I realized that there are more pickle files in the tests folder. I had "checkpoint.pkl" in mind when writing the message.

oops - that file is NOT meant to be there. All the pickles used for checks should be in test/test_data! We must have forgotten to gitignore it...

Sorry for the delay. I changed the list into a checklist. In this, let me remark again that this list summarizes my first impressions, so I'd encourage you to also think about the documentation beyond these points.

Thank you - yes I understand the documentation is very lacking, we are working hard on it. Apologies it is taking quite some time, we will keep updating here as we go along!

Thank you! There's no hurry, the goal of this review is to help you built and publish an awesome package :)

Apologies - I don't quite understand what you mean by "the file should not be at the root level of your repository". Should these be in a separate branch?

The file is at the same level as the directories "docs", "pygwb", ....
However, this file is very technical and is used only for tests (as I understand). Wouldn't it more appropriate to put it in the "test" folder? This would immediately give users a sense of what the file is about.

Every time we update a part of the code, indeed the pickles "stop working", and we update them accordingly. We've found this to be a useful check of the structure of the code. I'm afraid moving to JSON, while surely possible, would remove a layer of the checks we do, so I would be slightly against that.

In the interest of maintainability of the package, I think it would be best to have readers/writers to standard formats, and unit tests over those readers and writers to restore the layer of checks. This would be a more robust solution for two reasons: (1) you use a stable and clear format, as opposed to an opaque pickle, (2) new developers would see the reader/writer functions with their unit tests, and they would be able to more easily understand what is going on and extend the package (suppose a test fails with a pickle error, how would the developer know what to do? If you have reader/writers with tests, the failing test would immediately point the developer to the right direction).
Of course, this is my suggestion, and you are free to pick your preferred implementation. In any case, make sure to document everything.

I like this suggestion. Our data writer functions can write to multiple formats, pickle is just one of them. So as I said, storing/checking JSONs (or other) is no problem. However, what I was originally thinking of adding is a test which runs our pipeline and writes the object pickle file, which then can be used by other tests to check its content. This would avoid storing static pickle files, but would maintain the test of the object structure. What are your thoughts on this?

I like this suggestion. Our data writer functions can write to multiple formats, pickle is just one of them. So as I said, storing/checking JSONs (or other) is no problem. However, what I was originally thinking of adding is a test which runs our pipeline and writes the object pickle file, which then can be used by other tests to check its content. This would avoid storing static pickle files, but would maintain the test of the object structure. What are your thoughts on this?

That's excellent!

Hello @Sbozzolo and @cmbiwer - apologies on the delay. I'm making a list here of the things we have addressed which you can take a look at, as we continue working on documentation+. I remember I had a few things to improve in the unit tests as well, I'm working on it!
READY (ish)

About page
Installation page
All the API pages

We're working on restructuring the docs, essentially turning some of the tutorials into actual pages and leaving some remaining tutorials as "extras". The idea is that the API pages present each module/object, but we will add pages that describe how these are then used for analysis, and clarify the objectives/deliverables of the package, as well as how to obtain them. We will probably add about one page per script present in the pygwb_pipe folder (these are the scripts used in our day to day analyses)

Hello @Sbozzolo and @cmbiwer,
We have made significant progress in updating and refining our code and the documentation. Concretely,

All module API pages have been updated, ensuring that all class methods contain a description, and that the style used across module API pages is consistent throughout. Each of the API “landing pages" contains a brief description of the module itself, often with a few lines of code to illustrate the basic functionalities of the module.
The about, contribution and installation pages have been updated.
A few additional pages were created as well, and will be added moving forward. This to highlight some of the key scripts and functionalities of the pygwb package. The addition of those pages goes together with the removal of some tutorials. The idea behind these changes is to group all general information in these pages, whereas tutorials should contain more details or anything that deviates from the default usage.

At this point of the review process, it would be most useful if you could  provide feedback on the work that has been done so far, while we finalize the documentation. This will allow us to incorporate any proposed changes as we are making these final modifications to the documentation.

Hi @kevinturbang.
Thank you for your hard work. I'll review the new documentation over the weekend and provide my feedback.

Should I still be looking at the joss_submission branch even if the last commit was on Jun 21?

@Sbozzolo no - we are now working directly in the gitlab as suggested: https://pygwb.docs.ligo.org/pygwb/ (I have updated the README in the repo to reflect this)

Thanks, @a-renzini. I went through the documentation and here are some comments.

The diagram in the about page feels too technical detail for an "about" page. I'd suggest moving it somewhere else because it is not useful to readers that are not already familiar with pyGWB.
I don't see where you specify what versions of python are supported (or recommended).
There is no clear progression on how users should approach the documentation. Right now, if you follow the "next" buttons in the docs you get: About, Installation, Contributing guide, Using pygwb_pipe: a quickstart manual, ... It would be nice to have a general quickstart. It's unclear how I should use the package. If pygwb_pipe is a central piece, it should be explained.
Following on the previous point, given that I am unfamiliar with pygwb_pipe, I do not understand what it means to be a pipeline, or what a dag file is, or why I should care about this. Similar to pygwb_pe.
The tutorials look good. I would recommend backlinking all the various functions/objects you name in the notebooks, so that one can click on the link and learn more about the object/function from the API manual.
I'd recommend running the tutorials in a sandbox while you generate your documentation instead of uploading an evaluated notebook. Right now, the tutorials come with warnings generated on Keving Turbang's machine. If you run in a sandbox, you can do some additional quality control on your docs/package, and be closer to the environment a new user might have. (Also, it is not great to see unexplanined warnings in tutorials)
There's a typo "choise -> choice" in the inject a power spectrum tutorial, "cto -> to" in inject SGWB. If you care about it, there's also  a mix of British (e.g., initialise) and American (e.g., visualize) spelling of words. There are also extra new lines.
Some acronyms are never defined. Most people in the field know what PSD or H1 are, but you can make your package even more accessible to outsiders (or new students!) by defining all the acronyms at least once.
What is a notch list/notches?
I'd also recommend ensuring that your plots are readable (e.g., with a large font size, with different line styles for visually impaired people)

I haven't gone through the APIs carefully yet, but they seem fairly comprehensive.
To sum up my current assessment of your documentation: you wrote good pages/API/tutorials, but there is no underlying thread that joins them. As a new user, I still feel lost and I couldn't explain what pyGWB does exactly. I would recommend holding your users's hands a little bit more (e.g., providing a learning progression). I can give you examples of packages with good documentation if you want some inspiration on how to structure yours. One that might be close is LEGWORK.

Dear @Sbozzolo,
First of all, thank you very much for all the useful feedback. This has been very valuable to get the documentation to its current status. We have implemented the comments above, and tried to add a more logical structure within the documentation itself. Could you please have a look and let us know if any further improvements are necessary? Thank you!

Dear PyGWB team,
Thank you for your efforts. The user documentation is looking great (I like the "tips" to direct the reader to other pages).
I only have two remaining comments, one trivial, and the other less so:

I think it is uncommon to have external links in the main menu (the one of the side, e.g., "pyGWB paper"), so I was surprised when I clicked on some items and left the documentation. There's nothing wrong about it, but I think it's always good to follow the principle of least surprise.
It would be great if you could describe in more detail the input/outputs of the various scripts, and maybe provide some examples and comments. You are already kind of doing that, but you fall short from actually showing and discussing the output. Instead of telling the user "load the file and print the keys", I'd recommend being very explicit. Users that might be interested in your package would want to know what it produces. Moreover, plots are a great way for visual learners to get a sense of what pyGWB is about.

Also, the CONTRIBUTING.MD file and the contributing page in the docs are not perfectly in agreement.
By the way, can non-LIGO users contribute using LIGO's gitlab?

Dear reviewers,
Apologies for the delay on our end. We have added the following to address the points above:

Additional explanation on how to contribute for non-LIGO members.
Additional information about the output of the various scripts in the documentation.
We decided to keep the external links in the documentation, as we thought these are an added value for the users. Furthermore, the example of the LEGWORK documentation that you previously shared with us also has some external links.

Hopefully this addresses all your remaining comments. Please let us know if anything else needs modification.

Dear @Sbozzolo and team, can we mark this issue as closed? Thanks!

(sorry accidentally hit the purple button)

Documentation is a never ending process, and I invite you to keep working on it as you expand PyGWB. For JOSS, feel free to close this issue.


OpenAI GitHub Community Token on Solana $AIGIT

The first OpenAI GitHub community token to launch on Solana.
$AIGIT
All communication will run from this thread. I will handle dex payment/ads and external marketing.
First comment will contain the official PF contract address, all others are fake.

https://pump.fun/8nc8mL4YDMNWMHo7bphGcoZGKzFchKFgHLrDJfuPpump


add timeout input

Hi @erzz thanks for this convenient action!
I ran into a timeout error. My images were rather big and because of that dockle showed following error:
FATAL	Pull it with "docker pull <image tag>" or "dockle --timeout 600s" to increase the timeout

I've added an additional optional timeout input for the action that sets the env var DOCKLE_TIMEOUT. Now dockle has all the time it needs for my images. :)

Hi @NikLeberg !!!
I am so sorry for this PR flying under my radar for so long! For some reason I was not getting any kind of notification!
Really appreciated! Tested and working fine here!


Add configuration options for cluster-cidr, service-cidr and cluster-dns

This PR adds three new options to the configuration:

cluster_cidr
service_cidr
cluster_dns

These three options are basically just passed on to the CLI command when setting up the master.
I have compiled and tested it with a small test cluster on Hetzner. Everything seems to work.
Please note: This is the first time that I work with Crystal. I haven't really heard of this language before I've seen this project. So if anything is wrong, please tell me so I can fix it (and learn).

is it possible to specify CIDR for the control plane?

This is a good change, thank you. Is it possible to specify CIDR for the control plane?

Not with the changes of this PR. I've looked around the documentation a bit and didn't find anything that would allow to change this.

Hi @Floppy012 thanks a lot for this and sorry for the delay, I have been really busy with the day job. I also forgot to check PRs before releasing a new version today. :-/
The PR looks awesome, thanks! Before I merge, are you aware of any potential side effects with these changes and k3s?

Thanks @vitobotta
I've just noticed that the CCM deployment also has the Cluster-CIDR defined as CLI Argument. I didn't notice this as it worked fine while testing and just tested again and it doesn't seem to have any impact on the actual creation of routes as they are correct:
$ k -n kube-system get deployment/hcloud-cloud-controller-manager -o jsonpath='{.spec.template.spec.containers[0].command}'
["/bin/hcloud-cloud-controller-manager","--allow-untagged-cloud","--cloud-provider=hcloud","--leader-elect=false","--route-reconciliation-period=30s","--allocate-node-cidrs=true","--cluster-cidr=<IP_ADDRESS>/16"]

$ hcloud network describe network-1
ID:             ...
Name:           network-1
Created:        Tue Apr 11 13:00:57 CEST 2023 (6 days ago)
IP Range:       <IP_ADDRESS>/16
Subnets:
  - Type:               cloud
    Network Zone:       eu-central
    IP Range:           <IP_ADDRESS>/16
    Gateway:            <IP_ADDRESS>
Routes:
  - Destination:        <IP_ADDRESS>/24
    Gateway:            <IP_ADDRESS>
  - Destination:        <IP_ADDRESS>/24
    Gateway:            <IP_ADDRESS>
  - Destination:        <IP_ADDRESS>/24
    Gateway:            <IP_ADDRESS>
  - Destination:        <IP_ADDRESS>/24
    Gateway:            <IP_ADDRESS>
  - Destination:        <IP_ADDRESS>/24
    Gateway:            <IP_ADDRESS>
Protection:
  Delete:       no
Labels:
  No labels

But I feel not updating the CLI Arg could lead to unexpected error when Hetzner decides to use it somewhere. Shall I just manipulate it with regex or include the CCM deployment as template?

I think it's safer just in case. If you have a chance to try this other change it would be awesome, otherwise I will look into it when I have time. Thanks

@vitobotta I have included the CCM-Networks manifest as a Crinja template. It now produces a CCM manifest with the correct Cluster-CIDR. Due to the CCM having hostNetwork: true SonarCloud fails. I found nothing regarding ignore files for SonarCloud so you probably have to ignore the file in the settings somewhere.
Maybe that is helpful: https://docs.sonarcloud.io/advanced-setup/analysis-scope/#ignoring-issues

Hi @Floppy012 , are you still interested in completing this PR? :)

@vitobotta should be fixed now

Thanks! I will make a release soon. Thank you for your contribution :)


[FEATURE] Add experimental PHP7 memcached extension

I added the TODO and switched to building it with the interpreter.

LGTM, merging


Plugin Launcher Setup

As a user, I want to be able to launch some plugins from a homepage/startup plugin to do my day-to-day business.
ACs:

[ ] setup a plugin
[ ] define it as start-plugin users see first when they start OpenSCD


How I do it? I want solve buffering/lagging problems

http://docs.livestreamer.io/issues.html
I want to solve the problem of buffering/lagging  but I do not know how to do... how should I do exactly ? Where do I put the commands ?

On livestreamer's command line, add:
--player "/path/to/mplayer -cache <cachevalue>" (in KB)
--player "/path/to/mplayer2 -cache <cachevalue>" (in KB)
--player "/path/to/mpv --cache <cachevalue>" (in KB)
--player "/path/to/vlc --file-caching <cache-ms> --network-caching <cache-ms>" (values in miliseconds)

Thanks... but I put just as you told me ?  with " "  at the beginning and end? In the file there is a lot of examples with # at the beginning , I put it down command at the end of them ?

Yes, you need them or single quotes ' , as this is needed to be treated as one single param for livestreamer. Without them, livestreamer would use them for itself.
Where'd you see the # ?
A complete command line can be as following:
livestreamer whatyouwanttoplay --player "vlc --file-caching=5000 --network-caching=2000"

ok ty... i open livestreamerrc as a notepad and  I see it...I already put what you gave me it in the end
--player "/path/to/vlc --file-caching 10000 --network-caching 10000" is it correct?
Format is option=value. Lines starting with a # is considered comments
and are ignored.
By default livestreamer will attempt to locate VLC on your system
and use that, but you can also specify the location of a player
yourself.
Important: You must use a quoted path if there are spaces in the path. This
is because the player command is parsed like a shell command to allow
parameters to be passed to the player.
Here is a few examples of players:
VLC
#player="C:\Program Files (x86)\VideoLAN\VLC\vlc.exe"
#player="C:\Program Files\VideoLAN\VLC\vlc.exe"
Using --file-caching is recommended, but is only supported in VLC 2.0+
#player="C:\Program Files (x86)\VideoLAN\VLC\vlc.exe" --file-caching=5000
#player="C:\Program Files\VideoLAN\VLC\vlc.exe" --file-caching=5000
MPC-HC, must be at least version 1.7 to be used
#player="C:\Program Files (x86)\MPC-HC\mpc-hc.exe"
MPlayer2
#player=C:\mplayer2\mplayer2.exe -cache 4096
Use this if you want to transport the stream to the player via a named pipe.
#player-fifo
Use this if you want to transport the stream to the player via HTTP.
#player-http
Use this if you want Livestreamer to only pass a URL to your player and
let it handle the transport of the stream itself.
#player-passthrough=http,hls,rtmp
By default Livestreamer will close the player when stream is over.
Use this option to let the player stay or close itself instead.
#player-no-close
Use this option if you want Livestreamer to keep trying to access
the stream even if it goes offline or disconnects. Your player must
support HTTP and its playlist should be set to repeat mode.
#player-continuous-http
Show console output from the video player
#verbose-player
RTMP streams are downloaded using rtmpdump. Full path to the rtmpdump exe
should be specified here.
rtmpdump=C:\Program Files\Livestreamer\rtmpdump\rtmpdump.exe
Log level, default is info
#loglevel=debug
Number of threads to use when streaming HLS streams
#hls-segment-threads=1
Number of threads to use when streaming HDS streams
#hds-segment-threads=1

I'm unsure about the =-signs for vlc's params, but yeah, this should work.
If vlc doesn't recognize the = then just replace them with a space (like you already did):
--player "/path/to/vlc --file-caching 10000 --network-caching 10000"

oh ok, thanks man :D

Playing -.
Reading from stdin...
Cache fill: 17.02% (1568672 bytes)
libavformat version 56.40.101 (external)
TS file format detected.
Cache empty, consider increasing -cache and/or -cache-min. [performance issue]

different -cache-min and  -cache options for mplayer return the "cache empty" message no matter what.
any other ideas for mplayer?
it is constantly buffering no matter what.
tried messing with each single "Stream transport options" as well. no difference really. just constant buffering.

For twitch I use this on my livestreamerrc.twitch file:
ringbuffer-size=196M
hls-live-edge=3
hls-segment-threads=4

No excessive buffering for me with these settings. Not sure if relevant, but I pipe to mpv.


panzer treats format+/-extension as a separate format

While I know that you don't think that panzer should concern itself with the arguments to pandoc's -r and -w options (or their synonyms) there is one aspect of them which panzer probably needs to at least be enough aware of to ignore: pandoc extensions. Currently panzer 1.3 considers e.g. html and html-smart as two different output formats, totally ignoring styles for html when running with -w html-smart. As you can see from the example at the end of this post it can be exploited, but most of the time it is just plain annoying. There is really no workaround except duplicating styles in YAML files albeit eased a bit by the use of YAML anchors and references. When using multiple extensions it gets hard to handle, because you must use the exact same extensions, specified in the exact same order each time! Arguably this is due to a design flaw in pandoc: rather than appending these cute +this-that suffixes to the reader/writer name there should have been proper options -X, --reader-extension +ENABLED and -x --writer-extension -DISABLED. I can see three and a half solutions to this:

Just ignoring all extensions in the -w option argument when looking up styles. This is entirely acceptable but IMO a bit too limiting.

Parsing out the extensions part of -w option arguments and format keys in styles alike, split it into format and individual extensions, sort sextensions ASCIIbetically, join them together again and do lookup based on that. This would however be messy and confusing, and what if a style contains several keys with the same format and extensions but in different order?

Let panzer users specify extensions in styles as lists:

Pretend that those --reader-extension and --writer-extension options actually exist, letting panzer users specify them in styles just like other options and then append them to the reader/writer format. This would work very well and might motivate jgm to actually provide those options in pandoc. Alas there is the possibility, however slight, that like-named options with other functions be introduced in pandoc.

Better then to introduce an extensions field in styles:
Fancy:
  markdown:
    extensions:
      reader:
        on:
          - '`four_space_rule`'     # Keep my sanity!
          - '`emoji`'               # One of the few other off-by-default extensions I might consider turning on!
        off:
          - '`tex_math`'            # Strictly empirical linguistics and humanities here!

Simple:
  parent: Fancy
  markdown:
    extensions:
      writer:
        on:
          - '`smart`'               # Which actually means "NOT smart"! :-(
          - '`ascii_identifiers`'
        off:
          - '`bracketed_spans`'
          - '`fenced_divs`'

The on/off level rather than +/-foo in the lists is of course not strictly needed, but would greatly help me for one to see at a glance what gives!

I'll fully understand, and be quite happy, if you opt for 1. for the time being (format = re.match('\w+', options['write']) or 'html' and call it a day!) but please keep 3.ii. in mind for the future!

Example:
~/Dokument/bugs/panzer/extensions$ cat example.md
---
style: Foo
styledef:
  Foo:
    html:
      commandline:
        number-sections: true
    html-smart:
      commandline:
        number-sections: false
---

# Primum

## Primum "Alpha"

## Primum "Beta"

# Secundum

## Secundum "Alpha"

# Tertium

## Tertium "Alpha"

~/Dokument/bugs/panzer/extensions$ panzer example.md -w html
         ----- pandoc read -----
         running
         ----- style definitions -----
         global:
           <classified>
         document:
           Foo
         ----- document style -----
         style:
           Foo
         full hierarchy:
           Foo
         writer:
           html
         ----- run list -----
           empty
         ----- pandoc write -----
         pandoc writing with options:
           --number-sections

1 Primum

1.1 Primum “Alpha”

1.2 Primum “Beta”

2 Secundum

2.1 Secundum “Alpha”

3 Tertium

3.1 Tertium “Alpha”

~/Dokument/bugs/panzer/extensions$ panzer example.md -w html-smart
         ----- pandoc read -----
         running
         ----- style definitions -----
         global:
           <classified>
         document:
           Foo
         ----- document style -----
         style:
           Foo
         full hierarchy:
           Foo
         writer:
           html-smart
         ----- run list -----
           empty
         ----- pandoc write -----
         running

Primum

Primum "Alpha"

Primum "Beta"

Secundum

Secundum "Alpha"

Tertium

Tertium "Alpha"

This is a good point, well made. I knew that the current behaviour wasn't ideal, but this shows that it needs some proper attention. I will introduce a proper fix along the lines of 3.ii (but perhaps not with exactly this syntax).
Let me think about the best way to implement this.
I'm closing this pull request (https://github.com/msprev/panzer/pull/16), as it is related to the same point.

How is this going?

This is a fairly big change and I haven't had time to do it. It's on the list though, so it will get done.


ASE v3 and Azure Firewall

Hi, I can't find details how lock down ASE v3 with Azure Firewall. I found this only for v2
https://docs.microsoft.com/en-us/azure/app-service/environment/firewall-integration

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

ID: 29246f12-744e-08a1-c222-b0eae866b401
Version Independent ID: 6e925f96-dc31-d400-2681-2e387b40ed74
Content: Lock down outbound traffic - Azure App Service Environment
Content Source: articles/app-service/environment/firewall-integration.md
Service: app-service
GitHub Login: @ccompy
Microsoft Alias: ccompy

@jjindrich Thank you for your query . We will try to check internally and update the thread.

@jjindrich Thanks for asking question! ASEv3 has several major changes in the system architecture that serve to remove all management traffic from the customer VNet. This allows you to configure your firewall tightly without breaking your ASE. So, the documented steps not need to be followed.
Also suggest you to check this document on Feature differences Compared to earlier versions of the ASE.
Also, see: https://azure.github.io/AppService/2021/05/25/asev3-march-to-ga.html

Thank you, answer is here https://docs.microsoft.com/en-us/azure/app-service/environment/networking#extra-configurations


How to include your code in our library

In my initial experiments I got some promising results with our ASR library. Can I include a modified py version in our library? How can I reference your work? I didn't see any license anywhere.

Hi @bobchennan the repo is now MIT Licensed, feel free to use. Of course a friendly link back or little credit in the ReadMe would be appreciated if you use it.


Add a MAINTAINERS/CODEOWNERS file

It would be great if the maintainers were listed via a file. GitHub now actually has support for something called "CODEOWNERS" which should work: https://help.github.com/articles/about-codeowners/
cc: @yurishkuro

[ ] uber/jaeger https://github.com/uber/jaeger/commit/358138444457ba228eb08cce9994963f75b559f3
[ ] uber/jaeger-ui
[ ] uber/jaeger-lib
[ ] uber/jaeger-client-go
[ ] uber/jaeger-client-java
[ ] uber/jaeger-client-python
[ ] uber/jaeger-client-node

Per #3362, we're sunsetting Jaeger clients, so this is done for other repos


Receiving { return_code: 27012, error_message: 'Data is invalid' } while  calling get_address() in integration test.

I am using ledger-substrate-js to make my chain compatible with Ledger Nano S.
Here is the process that i followed:
I followed all the steps in the README after which i ran the key_derivation test using my seed phrase and from that i could get an address and a pubkey that are required for the integration tests. I also got hold of a blob from polkadot tests and used it for the sake of integration test.
The test for get version passed but for every other test i am getting { return_code: 27012, error_message: 'Data is invalid' }.
I am setting pathAccount, pathChange, pathIndex = 0x80000000.
What am i  missing?

:link: zboto Link

@anshulWeb3 Talk to Ledgerwallet Support on the Live support chat so that your issue can be looked into.

How have you created the blob? Probably you are using a wrong blob and your app is not able to parse the information

I've used a blob from current testcases and for the app i was taking a reference from app-polkadot and trying to reuse it for my purpose. I think the issues are on the app side. Can you suggest a good reference for substrate based chains? Or can you guide me to what all changes i need to make for making my app compatible. The documentation is insufficient for that. As far as i remember,  I changed #define COIN_ADDR_TYPE 42 and
#define CLA  <my cla > in substrate_coin.h also i made some changes in the makefile, specifically APPPATH = "44'/354'" --path "44'/<my_cointype>'". I'll be happy to provide any other information that might be required.

You can base your app in either Polkadot or Kusama apps that are the most updated apps. There is no such documentation to create a custom app based on Polkadot app. The readme from this repo explain how to use this package and how to support a new chain here.
If you can call getAddress command, then for sure you have something wrong in your parser. Be aware that the blobs contain information about the version of the transactions and it must match with the app.
It's hard to point something else without any code but I suggest to check that everything is working fine in your setup with Polkadot or Kusama and make the changes one at the time

I have based my app on polkadot only. I'll share code snippets so that you can take a look at it.

Here is the link to the code. I hope this  is helpful.
Also i had a few more queries that would help me understand the code better.

What is the significance of COIN_GENESIS_HASH here and how can i find one for my chain?
What is the significance of APPPATH here, I am aware it targets the  m’ / **purpose**’ / **coin_type**’ / account’ / change / address_index of a HD derivation path but when i looked at app-polkadot and app-kusama, they are using each other's coin type. My question is should i add my path there or i have to replace one of them?

Hi @anshulWeb3, this is not the place and there is none to discuss different parameters, configurations or code from apps.
1 - That is the hash of the first block of your blockchain.
2 - You can check the Ledger developer portal for more info about the apps
I'll close this ticket since your repo is cloned from Polkadot app and the issue is related to your implementation or setup in your testing.


[BUG] Start fails after cheking libvirtd

General information

OS: Linux / macOS / Windows
Hypervisor: KVM
Did you run crc setup before starting it? Yes

CRC version
# crc version
crc version: 1.5.0+e1c8fb8
OpenShift version: 4.2.14 (embedded in binary)

CRC status
# crc status
CRC VM:          Stopped
OpenShift:       Stopped
Disk Usage:      0B of 0B (Inside the CRC VM)
Cache Usage:     11.98GB
Cache Directory: /home/b1zzu/.crc/cache

CRC config
Doesn't print anything
# crc config view

Host Operating System
NAME=Fedora
VERSION="31 (Workstation Edition)"
ID=fedora
VERSION_ID=31
VERSION_CODENAME=""
PLATFORM_ID="platform:f31"
PRETTY_NAME="Fedora 31 (Workstation Edition)"
ANSI_COLOR="0;34"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:31"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f31/system-administrators-guide/"
SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=31
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=31
PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
VARIANT="Workstation Edition"
VARIANT_ID=workstation

Steps to reproduce

crc setup
crc start On the first time it works
crc stop
crc start

Expected
To start OpenShift
Actual
It doesn't start
Logs
# crc start --log-level debug
DEBU No new version available. The latest version is 1.5.0
INFO Checking if oc binary is cached
DEBU oc binary already cached
INFO Checking if running as non-root
INFO Checking if Virtualization is enabled
DEBU Checking if the vmx/svm flags are present in /proc/cpuinfo
DEBU CPU virtualization flags are good
INFO Checking if KVM is enabled
DEBU Checking if /dev/kvm exists
DEBU /dev/kvm was found
INFO Checking if libvirt is installed
DEBU Checking if 'virsh' is available
DEBU 'virsh' was found in /usr/bin/virsh
INFO Checking if user is part of libvirt group
DEBU Checking if current user is part of the libvirt group
DEBU Current user is already in the libvirt group
INFO Checking if libvirt is enabled
DEBU Checking if libvirtd.service is enabled
DEBU libvirtd.service is already enabled
INFO Checking if libvirt daemon is running
DEBU Checking if libvirtd.service is running
DEBU exit status 3 :
FATA exit status 3 :

I would like to add more but this is really everything I have

It looks like systemctl is-active libvirtd is failing on the second run? Relevant code is https://github.com/code-ready/crc/blob/master/pkg/crc/preflight/preflight_checks_linux.go#L211

Thanks, @cfergeau, I've found out that libvirtd was not running. But as an imrpovement it would be good to log a better error message. Feel free to close this bug as I've manged to solve the problem

it should be able to restart the service, but something here prevented it?
$ crc setup would start it... but why do you say the second time executing crc start fails? our crc stop does not stop libvirt, so likely something else might be misconfigured or failing here that might not relate to CRC.

Yes, crc setup should start libvirtd, and ensure it starts automatically on reboots. So it's surprising if it stops between runs.

it's surprising if it stops between runs

@b1zzu can you provide feedback on this?

@gbraad @cfergeau I'm not running crc as sudo/root so I don't see how it could start libvirtd which is a systemd service. If the tool is supposed to ask for root password that the fact that I'm using the zsh shell  could be the problem maybe.
I tried to go again throw the steps crc start, crc stop, and crc start but I can't reproduce the issue probably because the first time libvirtd stopped for some other reasons.
I think here the problem is not the behavior of crc but just the fact that the error was not helping at all

It is hard to provide an error for a situation that might be caused by a daemon that perhaps failed during usage. I think it crashed during an api call... but this is merely guessing.
We do a specific  check to see if libvirtd is running and fail accordingly if not. I believe what happened here is that the vm driver returned a null as the value wasn't able to be determined.

I'm not running crc as sudo/root so I don't see how it could start libvirtd which is a systemd service. If the tool is supposed to ask for root password that the fact that I'm using the zsh shell could be the problem maybe.

crc setup is taking care of starting libvirtd, asking for elevated privileges if needed. You are correct that crc start should not be run with sudo/as root, and that it won't try to start libvirtd. It will only check if it's running.

It is hard to provide an error for a situation that might be caused by a daemon that perhaps failed during usage. I think it crashed during an api call... but this is merely guessing.

DEBU Checking if libvirtd.service is running
DEBU Running `systemctl is-active libvirtd`
DEBU command failed with exit status 3
FATA libvirtd.service is not running

would be much nicer than
DEBU Checking if libvirtd.service is running
DEBU exit status 3 :
FATA exit status 3 :

Hi, just adding a quick feedback here after a fresh fedora 32 installation and system update sudo dnf update:
[hf@localhost ~]$ crc start
INFO Checking if oc binary is cached
INFO Checking if podman remote binary is cached
INFO Checking if running as non-root
INFO Checking if Virtualization is enabled
INFO Checking if KVM is enabled
INFO Checking if libvirt is installed
INFO Checking if user is part of libvirt group
INFO Checking if libvirt is enabled
INFO Checking if libvirt daemon is running
FATA Failed to check if libvirtd service is active

In other terminal:
[hf@localhost ~]$ sudo systemctl is-active libvirtd
inactive
[hf@localhost ~]$ sudo systemctl start libvirtd
[hf@localhost ~]$ sudo systemctl is-active libvirtd
active

crc start again (now working):
[hf@localhost ~]$ crc start
INFO Checking if oc binary is cached
INFO Checking if podman remote binary is cached
INFO Checking if running as non-root
INFO Checking if Virtualization is enabled
INFO Checking if KVM is enabled
INFO Checking if libvirt is installed
INFO Checking if user is part of libvirt group
INFO Checking if libvirt is enabled
INFO Checking if libvirt daemon is running
INFO Checking if a supported libvirt version is installed
INFO Checking if crc-driver-libvirt is installed
INFO Checking if libvirt 'crc' network is available
INFO Checking if libvirt 'crc' network is active
INFO Checking if NetworkManager is installed
INFO Checking if NetworkManager service is running
INFO Checking if /etc/NetworkManager/conf.d/crc-nm-dnsmasq.conf exists
INFO Checking if /etc/NetworkManager/dnsmasq.d/crc.conf exists
? Image pull secret [? for help]
...

INFO Extracting bundle: crc_libvirt_4.4.3.crcbundle ...
INFO Checking size of the disk image /home/hf/.crc/cache/crc_libvirt_4.4.3/crc.qcow2 ...
INFO Creating CodeReady Containers VM for OpenShift 4.4.3...
INFO CodeReady Containers VM is running
INFO Verifying validity of the cluster certificates ...
INFO Check internal and public DNS query ...
INFO Check DNS query from host ...
INFO Generating new SSH key
INFO Copying kubeconfig file to instance dir ...
INFO Starting OpenShift kubelet service
INFO Configuring cluster for first start
INFO Adding user's pull secret ...
INFO Updating cluster ID ...
INFO Starting OpenShift cluster ... [waiting 3m]

$ cat /etc/redhat-release
Fedora release 32 (Thirty Two)

$ crc version
crc version: 1.10.0+9025021
OpenShift version: 4.4.3 (embedded in binary)

FATA Failed to check if libvirtd service is active

This is unexpected as this message would mean that systemctl is-active libvirtd failed?

yeah, the first time I ran crc start it failed with the message: FATA Failed to check if libvirtd service is active.
Then, in other terminal I started the libvirtd and ran crc start again and the issue gone.
But yesterday I tested same fedora 32 in other computer and everything goes correct without need to manually start libvirtd.

It's been fixed by https://github.com/code-ready/crc/commit/6c0b5122ff29b75af0467d06f0cb9bec2cf2fead


plugin request: aniwatch (zoro)

main domain
recently updated

till someone does it, i can't do it


Fix challenge.js

Add new buff images & don't show levels with fast pass

@bietiaop QAQ

@bietiaop QAQ

Roger that.


chore: merge dev into master

Coverage remained the same at 79.448% when pulling 1ecc4ac61933ddc7ef0855d888b5a31042ecb5d7 on dev into c755a03d3e4cfecda3ed303812c2ca62e8f18b7d on master.


cancel button in camera selection mode of Scanning with barcode pausing the camera

Checklist

[x] Bug Report - The issue you are reporting might be there already. Please search on the issues tracker before creating or reporting a issue.
[x] Before reporting, please ensure (if you can) that you have tested it with the latest (dev) version of the software.
[x] Don't forget to tag your issue, it makes it easier to discover.

Summary:
ON pressing cancel button in camera selection mode (i.e rear of front) in scanning with barcode option pauses the camera instead of taking back to it's previous state as no change is selected.
Steps to reproduce:
By clicking cancel option in camera selection mode of scanning with barcode in slide bar menu.
Expected behavior:
Going back to same state of camera as no change is selected.
Observed behavior:
It pauses the camera
Device and Android version:
Redmi Note 4 having android 7.0 (nougat)

already fixed #883

OK


App crash on UAI

Version 1.1.9 (284)
https://github.com/bithyve/bitcoin-keeper/assets/107177634/b6e188d6-a1b0-46a0-851f-2bc0759c678b

Verified this issue on keeper app v 1.1.9(288)


Many Values to Multiple Variables

I know in python it support the mode - many values to multiple variables, but in swift it doesn't support.
x, y, z = "Orange", "Banana", "Cherry"

It does but you need to add parentheses and a let or var in-front of it if the variables are not yet defined in scope.
let (x, y, z) = ("Orange", "Banana", "Cherry")

BTW: The right place to start a discussion like this is in the forums: https://forums.swift.org/c/evolution/discuss/11

I mean make it shorter , delete single quote and the let key word...

This is an unrelated commit, not a proposal. Please see https://github.com/apple/swift-evolution/blob/main/process.md for information on the Swift Evolution process.


Page to a different month programmatically ?

Hi,
I have tried the following to programmatically page between months (instead of physically swiping) but it doesn't seem to work when using the correct width for offset (if I use 374 it works fine but the view is then shifted by 1 pixel).
contentView.setContentOffset(CGPointMake(375, contentView.contentOffset.y), animated: true)
contentView.selectPage(Int(2.0))
delegate?.calendarDidPageToDate(contentView.currentMonth().date)

I think I resolved this:
    contentView.selectPage(Int(2.0))
    contentView.setContentOffset(CGPointMake(375, contentView.contentOffset.y), animated: true)
    contentView.setNeedsLayout()
    delegate?.calendarDidPageToDate(contentView.currentMonth().date)

lgtm


fixes a couple of bugs in aks samples

Contributing an example
Fixes #3910

[x] This is a bug fix for an existing example
[x] I have resolved all warnings and errors shown by the Bicep VS Code extension
[x] I have checked that all tests are passing by running dotnet test
[x] I have consistent casing for all of my identifiers and am using camelCasing unless I have a justification to use another casing style

I still need to fix the verification in the tests. Missed that. :)

To fix the tests I did what was described in the test output:
Overwrite the single baseline:
    xcopy /yq "C:\git\uuu\bicep\src\Bicep.Core.Samples\TestResults\Deploy_dagk 2021-08-05 14_52_06\In\2eb0de7f-0bb7-4e0e-aa4a-c4dd84ff8b89\main.json.actual" "C:\git\uuu\bicep\docs\examples\101\aks-vmss-systemassigned-identity\main.json"

I hope this is the right way to mitigate the failing tests?

Ported this change to https://github.com/Azure/azure-quickstart-templates/pull/11121.

@buzzfrog Anything else you wanted to change before I merge?  Feel free to suggest changes to https://github.com/Azure/azure-quickstart-templates/pull/11121 as well.

@StephenWeatherford. No more changes at this time. :)


Documentation on process custom B2C layout

This cumbersome process will be fixed by https://app.zenhub.com/workspaces/mighty-ducks---the-outlaws-6193fe815d79fc0011e741b1/issues/energinet-datahub/the-outlaws/403


No such module "BRCrypto"

Hi,
I am using Pods for SwiftProtobuf.
Issue: No module "BRCrypto"
Any ideas whats is wrong?

I had the same problem, turns out I didn't clone the git submodules including breadwallet-core.


fixed spread error

Description
RHOAIENG-7212
The spread operator was not needed in this case (nor is it syntactically supported), thus I removed it.
UI stays the same:

How Has This Been Tested?
I testing by running npm run test:cypress-ci -- --spec "**/homeAIFlows.cy.ts"
Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

/cc @jeff-phillips-18


Feat: Query puzzles based on rating, themes from Lichess puzzles DB

Is your feature request related to a problem? Please describe.
the puzzles in /puzzle are random and are not able to query the puzzle by rating or themes, let's say a user wants to do a puzzle by checkmate or 1800 rated puzzle this is not possible currently
Describe the solution you'd like
A clear and concise description of what you want to happen.
/puzzle should have mode of Lichess puzzle by rating, Lichess puzzle by theme or random Lichess puzzle
Describe alternatives you've considered
No alternatives
Additional context
The code for rendering puzzles is already present in abstraction and ChessUtil, you can also look at how other puzzle components like Daily puzzle are done in the code.
The Lichess puzzle database is here, ChessLise should be able to query https://database.lichess.org/ in CSV format
from there, it should be able to render the puzzles and show them to the user
making the puzzle trigger solution module is (optional) but also needed so if you're down for the challenge this is great also.
opening this as the good first issue, because everything is already there, just querying the db is missing

6909a015782a41c48a0c75a984210fb7f5d7d51d


bash completion: Add remaining flags for brew outdated

Adds --verbose, --formula, and --greedy

[X] Have you followed the guidelines in our Contributing document?
[X] Have you checked to ensure there aren't other open Pull Requests for the same change?
[X] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?
[X] Have you successfully run brew man locally and committed any changes?

As far as other commands go, there are plenty of other flags documented in the man page that are missing from bash completion; I'd be happy to submit a PR to add some (all?) of them if desired (or can just do it here).

Thanks again @Amorymeltzer! Something to perhaps pique your interest: it'd be great if there was a way to autogenerate this stuff the same way we generate the e.g. manpage given that we know the names of all options etc. at runtime. If you're interested in this and need any more information to work on it: ask any questions here and I'll happily answer.

Neat idea!  Ruby's not my strong suit but I do think it'd be neat, so I can look into it and see if it's not beyond me.


Can't install license version 1.0.0 and up

When trying to install or use license via npx I get the following error message
npm i license
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

npm ERR! code ENOENT
npm ERR! syscall chmod
npm ERR! path /Users/pnash/projects/project-name/node_modules/license/dist/cli/index.js
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, chmod '/Users/pnash/projects/project-name/node_modules/license/dist/cli/index.js'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR!      /Users/pnash/.npm/_logs/2020-03-24T03_59_10_214Z-debug.log

Version 0.0.3 still works. Was the project released without building the files to dist? Or are the dist files not being included in the package?
Thanks

Hmm, looks like dist does exist, but for some reason its only got getLicense in it, none of the CLI stuff. Oops.
I'll see and try to resolve it later this week, thanks for reporting this.

And by later this week I mean now I guess. 1.0.2 should fix this, simply forgot to add dist to the files array. Oops.

Thanks for the quick fix! :+1:

No problem!


Automatic Updation of Footer Copyright Year

Description
Hey @manankohlii
Changed the footer copyright year into automatic.
Please check and update.
Thanks
Fixes #103
Type of Change:

Bugs
New Feature
Documentation

How Has This Been Tested?

Checklist:

[ ] My PR follows the style guidelines of this project
[ ] I have performed a self-review of my own code or materials
[ ] I have commented my code or provided relevant documentation, particularly in hard-to-understand areas
[ ] My changes generate no new warnings
[ ] New and existing unit tests pass locally with my changes

@Shaishav0507 merged,


Add support for an optional on_exit callback

Added an on_exit() -> Option<Box<dyn FnOnce>> function to the iced::Application trait that provides that callback.
When the returned closure does not actually exit the application then iced::Application::run() can return as well, allowing the program to continue when the main window is closed.
For iced_web it could make sense to invoke the on_exit() closure when unloading the page, did not try to implement that though.
The main use-case for this is to allow to change the exit code of the application.

yeah - I somehow overlooked that. I did not want to change the control flow of Application::run() it currently only returns when initializing the application fails.
I realized that the run() method may return normally when running through the code for the pull-request.
Letting it return in all cases would be simpler than any callback - unless returning from Application::run does not work with all backends.

Removed the on_exit() callback entirely and added an example that Application::run returns. Also that it may be called in a loop.
Added another commit that demonstrates the same when calling iced_winit::run or iced_glutin::run

sure, I get rid of the examples...
and rename the pull request. There is no more on_exit callback


Upgrading 1.1 -> 1.2 docs can suggest a new way of specifying custom image tags

Before proceeding

[X] I didn't find a similar issue

Problem
https://werf.io/documentation/v1.2/resources/how_to_migrate_from_v1_1_to_v1_2.html#interface-rework

There is no more --tag-by-stages-signature, --tag-git-branch, --tag-git-commit, --tag-git-tag, --tag-custom options, --tag-by-stages-signature behaviour is default.
Forcing of custom tags is not yet available in the v1.2

https://github.com/werf/werf/issues/2869 is already resolved.
Solution (if you have one)
Upgrading docs can be updated according to provided feature to use custom tagging.
Additional information
https://github.com/werf/werf/releases/tag/v1.2.28

Version 1.1 is no longer supported (only critical cases), so the article may differ from the current functionality. We have tried to change the structure of the 1.2 documentation so that the search for solutions to such issues does not take much time.
In any case, thanks for the feedback ❤


Stopping Asynchronous Python

Thanks and congrats for the great project.
I am starting on python and this helped me a lot.
I am running your assync example and it is working good:
import eel
eel.init('web')
def my_other_thread():
    while True:
        print("I'm a thread")
        eel.sleep(1.0)                  # Must use eel.sleep()

eel.spawn(my_other_thread)

eel.start('main.html', block=False)     # Don't block on this call

while True:
    print("I'm a main loop")
    eel.sleep(1.0)                      # Must use eel.sleep()

Therefore, I need at a certain moment to stop the thread which is running (  eel.spawn(my_other_thread)   ).
I already tried something like:    test = eel.spawn(my_other_thread),   and test.kill() to stop it, but did not work.
How should I do it?
Actually, I am working on a project with some pages. Each page will have some functions that should be running in the background for retrieving new data. But when I switch pages, the other functions should be stopped.
How could I make this easier?
Thank you very much!

@tburd Sorry for not getting back - did you work this out yourself?

I'm also trying to figure this out. If I do
task = eel.gvt.spawn(my_func)
is there a way to click a button to run task.kill() while my_func is still running?
If I try to run task.kill() via an exposed python function it only executes after my_func is finished.

This is a bug I think, this line should have a return. I will add it to list of bug fixes...


Could not find module 'TheRouter' for target 'arm64-apple-ios-simulator'; found: x86_64-apple-ios-simulator

Chip
Apple M2
OS
14.1.1 (23B81)
What I need
Build success
What I get
Could not find module 'TheRouter' for target 'arm64-apple-ios-simulator'; found: x86_64-apple-ios-simulator

Solution
Edit Scheme -> Run -> Debug


Azure Dataplane does not register any generator function for AzureStorage type (v0.7.1)

Bug Report
Describe the Bug
Similar to https://github.com/eclipse-edc/Technology-Aws/issues/401 but for AzureStorage.
This issue only impacts 0.7.X. versions.
The issue was fixed for 0.8.0 and the solution shouldn't be merged to the main branch.

already resolved in main, was backported in 0.7.2 by #237


[WIP] Add F# pipeline operator

Related #5443

[x] await parsing
[x] arrow body parsing

Well, it's actually looks like I implemented minimal, not F#

I ended up implementing typechecking as well 😀

Babel PR https://github.com/babel/babel/pull/9450 for reference

Well, there's already was function body parsing in assignment_cover, so I just copy-pasted it

I don't think it's possible to implement all three in Flow, because there isn't such thing as parser plugins. Flow just parses everything and then errors on wrong things with PseudoParseError

@mAAdhaTTah What you think? Is this still too early?

Probably. I don't know the Flow team's policy around this sort of thing. I know TS won't implement anything until stage 3, especially after the pain they've had with decorators.
I'll point out that the committee isn't necessarily sold on the operator at all and there is a significant contingent who prefer the bind operator. Not only are we risking implementing the wrong version of the operator, we're risking the syntax not advancing and needing to rip it out.

Well, Flow supports nullish coalescing, and optional chaining, but they're still stage 2

@mAAdhaTTah I thought bind operator was dropped in 2015 and always was stage 0?

AFAIK, Bind is still Stage 1, but it's stalled out. However, we have gotten suggestions, including from committee members, about bind: https://github.com/tc39/proposal-pipeline-operator/issues/110 and https://github.com/tc39/proposal-pipeline-operator/issues/107 so I'm still viewing it as a competing proposal.

Closing since the PR has too many merge conflicts, and we do not plan to implement proposals before stage 3


【Hackathon No.76】基于pointer_summarizer完成中文文本摘要任务

76、基于pointer_summarizer完成中文文本摘要任务（提交rfc）

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


Crash with Forge microblock and Bluepower

http://jpst.it/yVhi
I always get this crash

qmunity author needs to update to latest FMP, downagrade to version 1.1.X, rather than 1.2


Dockerizing the Website

I want to Dockerize the website so it becomes to run the application irrespective of dependencies versions and system requirements

hey @ssouravs, I can work on Dockerizing the website. Can you assign me??

Hey I want to work on this issue can you assign it to me

if no one has done this job, can you assign me this task? I can complete this task.


TPM based signing

not a bug but incase anyone is interested, here are some  samples of the signing flow where the hmac or roles anywhere key is embedded inside a TPM:

as library python v4signing:

https://github.com/salrashid123/cloud_auth_tpm   (both hmac and rolesanywhere)
Variant of AWS v4 signing without SDK (hmac based off of v4-nosdk)

as library golang v4 signing

aws hmac signer
aws_rolesanywhere_signer

as process credential

aws-tpm-process-credential
aws-pkcs-process-credential

coming back to v4a signing, i don't have mrap setup anywhere but i was able to issue a header which should work..
import boto3
from cloud_auth_tpm.aws.awshmaccredentials import AWSHMACCredentials
from cloud_auth_tpm.policy import PCRPolicy, PCRAuthValuePolicy
from botocore import crt, awsrequest

pc = AWSHMACCredentials(
    tcti=args.tcti,
    keyfile=args.keyfile,
    ownerpassword=args.ownerpassword,
    password=args.password,
    policy_impl=policy_impl,
    enc_key_name=args.enc_key_name,

    access_key=args.aws_access_key_id,
    region=args.region,
    duration_seconds=3600,
    role_session_name=args.role_session_name,
    assume_role_arn=args.assume_role_arn,

    get_session_token=args.get_session_token
)

session = pc.get_session()

service = 's3'
region = '*'
method = 'GET'
url = 'https://myalias.accesspoint.s3-global.amazonaws.com/someobject'

headers = SigV4ASign(session).get_headers_basic(service, region, method, url)
print(headers)

gave a header with AWS4-ECDSA-P256-SHA256
{'host': 'myalias.accesspoint.s3-global.amazonaws.com', 'X-Amz-Security-Token': 'FwoGZXIvYXdzEEEaDHMvPaP3Io6RxB9qI-redacted', 'X-Amz-Date': '20240930T160229Z', 'X-Amz-Region-Set': '*', 'x-amz-content-sha256': 'e3b0c44298fc1c149afbf4c8996-redacted', 'Authorization': 'AWS4-ECDSA-P256-SHA256 Credential=ASIAUH3H6EGK-redacted/20240930/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date;x-amz-region-set;x-amz-security-token, Signature=3044022045106142-redacted'}

again, if your'e interested, please try it out and if there are modification or outright corrections, pls add a comment on those repos...and just to be clear, its not affiliated with aws and i'm pretty much a novice when it comes to aws so maybe doing thing totally wrong.

Hey @salrashid123 , thanks for this - if you'd like to contribute an example, please do open a PR, for now I will close this issue.


Fix Windows testing in AMD64-Linux-OSX-Windows-test.yml

No need to specify the generator, this is currently causing the build to fail under Windows.

Thank you for the PR.  I've merged your patch into the master.


Add Splunk logging driver #16207

Allow to send Splunk logs using Http Event Collector
Signed-off-by: Denis Gladkikh<EMAIL_ADDRESS>Fixes #16207

This PR is for #16207

Updated OP's description to include the issue it fixes (so that it automatically closes it if this PR is merged)

Thanks very much for also implementing bash completion. That's really cool stuff!

@albers thank you for review! Just updated PR

Bash completion LGTM. Thanks for updating.

Didn't read the code, but I'm +1 for a splunk driver since we already have many logging drivers.
I do have to state again the fact that it's unfortunate we have to compile all of these drivers in, and would prefer to have these as run-time Go plugins whenever they are ready. I understand having out-of-process logging plugins can be a significant performance hit.

ping @sdurrheimer zsh completion: new log-driver

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "splunk_log_driver" git@github.com:splunk/docker.git somewhere
$ cd somewhere
$ git rebase -i HEAD~3
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

@outcoldman Is there any easy way to test driver?

@LK4D4 it depends on the definition of "easy". I did all my tests manually. To test it we need to

Download Splunk
Extract it somewhere, in case if it will be inside docker container - we will need to have access to any mapped volume with supported file system.
The test scripts can preconfigure HTTP Event Collector and start Splunk.
After we can just send some logs to Splunk and verify that these events were indexed.

Do you think that we can perform first 2 steps? Do you have an example?

@outcoldman I mean test manually, not unit-tests. Yes, I thought maybe you have docker image with splunk.

Ah, I see, so you are asking for instructions how to test it manually. This make sense.

You can use my own Docker Image with Splunk (https://hub.docker.com/r/outcoldman/splunk/) - this is not officially supported by Splunk image, but will be good enough for testing. Or you can download Splunk directly in Docker Dev image in mapped volume, let's say at /opt/splunk, you can download it from http://www.splunk.com/en_us/download.html
You need to expose port 8000 for Web Interface and 8088 for HTTP Event Collector.
After you will start Splunk open 8000 to get access to the Web Interface, you will need to configure HTTP Event Collector, see http://docs.splunk.com/Documentation/Splunk/6.3.0/Data/UsetheHTTPEventCollector (use port 8088 for HTTP Event Collector, it is a default port, you can use HTTP or HTTPS, if you want to use HTTPS - you will need to configure custom certificates or use ca certificate for Docker daemon to configure Splunk driver or just ignore verification).
I used these parameters for HTTP (let me know if you also want to test HTTPS) to start nginx container (replace path to your Splunk instance and token given to you by Splunk on previous step)

docker run --log-driver=splunk --log-opt splunk-token=176FCEBF-4CF5-4EDF-91BC-703796522D20 --log-opt splunk-url=http://splunk:8088  -d -p 80:80 nginx

After to test the driver I have send few curl requests to nginx container using

curl http://localhost:80/?justatest=hello

In Splunk Web Interface in search string just run "*" and you should see your events.

@outcoldman thanks, I'll try. Moving to code-review in the meantime.

btw need rebase, sorry :)

@LK4D4 np, rebased!

I would recommend accepting both username & password, as well as http event collector tokens.
As it is, I am unable to test this PR because I am using splunk cloud, which does not yet support the http event collector.

Hi @phemmer
Thanks for the input. Event Collector is available in Splunk Cloud, but it needs to be enabled via a support request. There's no UI yet for self-service. But it is definitely available.
As to the username / password. Going forward we will encourage people not to use the REST API to send events as it requires a username and password that can potentially leak access to Splunk. Event Collector tokens are not attached to user credentials, they are specifically designed just for logging events. It is a special endpoint that only allows sending data with a valid token. This makes it more secure from a Splunk perspective as using the token will not allow accessing any part of Splunk, you can't even authenticate to the management port (8089) with it.
You are correct that it is only in Splunk 6.3, but you can stand up dedicated Event Collector instances within a 6.2 environment and they will work fine. EC can run anywhere, and indexer, a forwarder, etc.

Thanks for the input. Event Collector is available in Splunk Cloud, but it needs to be enabled via a support request. There's no UI yet for self-service. But it is definitely available. Please contact Splunk Cloud support and they will get you up and running.

I have:

@phemmer btw you can always use syslog with splunk forwarder if you cannot upgrade to 6.3, see https://outcoldman.com/en/archive/2015/08/22/collecting-docker-logs-and-stats-with-splunk/

@phemmer btw you can always use syslog with splunk forwarder if you cannot upgrade to 6.3, see https://outcoldman.com/en/archive/2015/08/22/collecting-docker-logs-and-stats-with-splunk/

But that defeats the point of this logging driver :-)

@phemmer please email me<EMAIL_ADDRESS>According to cloud folks it is avail now.

@phemmer not really, for some people it can be expensive to install forwarder on every machine where they have docker daemon, especially when we are talking about small tiny VMs in the cloud with 512mb RAM. Also it is much simpler to configure automatic deployment with splunk logger driver, especially if they want to make it secure.

@phemmer I agree with you. The driver is there to mitigate the need for deploying a forwarder :-)

@phemmer Update on this. Sounds like new customers get it now. Existing customers will be upgraded in the next few weeks. I am going to see if we can push yours up to happen sooner.

@phemmer Let us know if it'll work for you with splunk cloud.

As to the username / password. Going forward we will encourage people not to use the REST API to send events as it requires a username and password that can potentially leak access to Splunk. Also EC has been designed in a more scalable / available fashion than the receiver endpoints. Event Collector tokens are not attached to user credentials, they are specifically designed just for logging events. It is a special endpoint that only allows sending data with a valid token. This makes it more secure from a Splunk perspective as using the token will not allow accessing any part of Splunk, you can't even authenticate to the management port (8089) with the token.

Was really busy earlier and didn't have time to respond to this in full, but my thoughts:
I understand the argument behind tokens, and why you shouldn't use user credentials. But we're talking about a feature which is so new, many people don't even have access to it yet (as is my own situation). Yes, for older versions of splunk, you could use syslog/forwarder, but there are many reasons this might not be feasible.
Additionally, I'm always of the opinion that you shouldn't limit people's options because you don't think some of the options should be used. Said people might have unforeseen reasons for using these other options.

You can deploy dedicated 6.3 event collector instances in a hybrid
environment. I agree it is new, but a big problem with the REST API is also
scale. If wasn't really designed for massive scale. The simple receiver is
really slow and the streaming endpoint is really an HTTP hack that won't
scale out easily behind a load balancer.
On Wed, Sep 30, 2015 at 5:13 PM Patrick Hemmer<EMAIL_ADDRESS>wrote:

As to the username / password. Going forward we will encourage people not
to use the REST API to send events as it requires a username and password
that can potentially leak access to Splunk. Also EC has been designed in a
more scalable / available fashion than the receiver endpoints. Event
Collector tokens are not attached to user credentials, they are
specifically designed just for logging events. It is a special endpoint
that only allows sending data with a valid token. This makes it more secure
from a Splunk perspective as using the token will not allow accessing any
part of Splunk, you can't even authenticate to the management port (8089)
with the token.
Was really busy earlier and didn't have time to respond to this in full,
but my thoughts:
I understand the argument behind tokens, and why you shouldn't use user
credentials. But we're talking about a feature which is so new, many people
don't even have access to it yet (as is my own situation). Yes, for older
versions of splunk, you could use syslog/forwarder, but there are many
reasons this might not be feasible.
Additionally, I'm always of the opinion that you shouldn't limit people's
options because you don't think some of the options should be used. Said
people might have unforeseen reasons for using these other options.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/16488#issuecomment-144579229.

@phemmer would you be willing to test the driver for us if we can get you a Splunk Cloud instance with EC enabled? I've talked to our Cloud Folks, and if you create a trial, we can the open it up with a token for you to test.

@phemmer would you be willing to test the driver for us if we can get you a Splunk Cloud instance with EC enabled? I've talked to our Cloud Folks, and if you create a trial, we can the open it up with a token for you to test.

My splunk cloud account is scheduled to be upgraded tomorrow. So I'll just wait for that.

Ok perfect
On Tue, Oct 6, 2015 at 6:58 PM Patrick Hemmer<EMAIL_ADDRESS>wrote:

@phemmer https://github.com/phemmer would you be willing to test the
driver for us if we can get you a Splunk Cloud instance with EC enabled?
I've talked to our Cloud Folks, and if you create a trial, we can the open
it up with a token for you to test.
My splunk cloud account is scheduled to be upgraded tomorrow. So I'll just
wait for that.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/16488#issuecomment-146056624.

@cpuguy83 anything else pending approval on this aside from @phemmer's validation?

Are there not going to be any tests for this? Shouldn't be hard to mock out a fake  event collector server.

In regards to my testing, I'm waiting on support to enable the collector

Good call.
On Wed, Oct 7, 2015 at 8:00 PM Patrick Hemmer<EMAIL_ADDRESS>wrote:

Are there not going to be any tests for this? Shouldn't be hard to mock
out a fake event collector server.
In regards to my testing, I'm waiting on support to enable the collector
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/16488#issuecomment-146404017.

@phemmer this is something we'll look into. It doesn't look like tests are a requirement for now though we do have to manually test it. Thanks for the suggestion.

I tried with splunk enterprise and it seems to work. However it require rebase and fix comment from @itay

I'm still waiting for support to enable the collector on my splunk cloud account.
Supporting splunk cloud out of the box instead of making people wait weeks to be able to use docker with it would be great. </DeadHorse>

Totally agree, we're working in it.
On Tue, Oct 20, 2015 at 9:16 AM Patrick Hemmer<EMAIL_ADDRESS>wrote:

I'm still waiting for support to enable the collector on my splunk cloud
account.
Supporting splunk cloud out of the box instead of making people wait weeks
to be able to use docker with it would be great.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/16488#issuecomment-149619590.

@LK4D4 thanks for testing.

@LK4D4 awesome, thanks! fixed what Itay found and rebased to the latest.

We're working on getting the collector open on @phemmer's account so he can
test.
On Tue, Oct 20, 2015 at 1:47 PM Denis Gladkikh<EMAIL_ADDRESS>wrote:

@LK4D4 https://github.com/LK4D4 awesome, thanks! fixed what Itay found
and rebased to the latest.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/16488#issuecomment-149696784.

@outcoldman can you squash your commit to one now, when review is almost finished?

@LK4D4 sure, done!

LGTM

LGTM
moving to docs review.

ping @thaJeztah

Thanks @outcoldman, I added my comments inline :+1:
Also, ping @sdurrheimer if he's interested to update the zsh completions, thanks!

@thaJeztah docs are updated!

Thanks @outcoldman I'm still looking, will run a make docs to test if all works correctly.
It looks like you missed the change to move the API changes to the v1.22 docs; https://github.com/docker/docker/pull/16488/files#r42693762
I'll ask @moxiegirl to have a look as well

Thanks for updating, @outcoldman LGTM!

@thaJeztah @moxiegirl thank you for feedback - updated docs.

Thanks all!
On Fri, Oct 23, 2015 at 10:23 AM Denis Gladkikh<EMAIL_ADDRESS>wrote:

@thaJeztah https://github.com/thaJeztah @moxiegirl
https://github.com/moxiegirl thank you for feedback - updated docs.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/16488#issuecomment-150638174.

@moxiegirl gave me a "LGTM" in person :+1: waiting for Janky to finish

Sweet!
On Fri, Oct 23, 2015 at 10:30 AM Sebastiaan van Stijn <
<EMAIL_ADDRESS>wrote:

@moxiegirl https://github.com/moxiegirl gave me a "LGTM" in person [image:
:+1:] waiting for Janky to finish
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/16488#issuecomment-150640165.

I'd recommend clarifying that one paragraph.  Otherwise, LGTM

Oh, boy.. looks like this needs a rebase :'( sorry for that @mountkin

@thaJeztah np, rebased!

Al green! merging \o/

@outcoldman @glennblock congrats!

Thank you all for helping! And my personal huge thank to the @LK4D4.
Docker folks, you are great!

Thanks for contributing @outcoldman open source FTW!

Yay!!!! This rocks!
On Fri, Oct 23, 2015 at 9:02 PM Sebastiaan van Stijn <
<EMAIL_ADDRESS>wrote:

Thanks for contributing @outcoldman https://github.com/outcoldman open
source FTW!
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/16488#issuecomment-150751170.

Thank you all! We are seeing a lot of interest in Docker in our Splunk
customer base. This is an awesome day!
On Sat, Oct 24, 2015 at 9:11 AM Glenn Block<EMAIL_ADDRESS>wrote:

Yay!!!! This rocks!
On Fri, Oct 23, 2015 at 9:02 PM Sebastiaan van Stijn <
<EMAIL_ADDRESS>wrote:

Thanks for contributing @outcoldman https://github.com/outcoldman open
source FTW!
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/16488#issuecomment-150751170.

Keewl! =)

@thaJeztah Looks like this was missed and not cherry picked in.  Any idea when 1.9.3 is going out?

@moxiegirl I dunno why you think it should be in a milestone. It's a new feature == shouldn't be in the minor release.

There was some confusion about the timing, but this PR was merged after the 1.9.0 code freeze (1.9.0-rc1 was released on October 14th).
This driver will be part of the 1.10 release. For people wanting to give it a spin before that, it is available in the "Experimental" or "Master" builds (not intended for production)

Our understanding was it was part of 1.10. Thanks for confirming.
On Thu, Dec 10, 2015 at 4:48 PM Sebastiaan van Stijn <
<EMAIL_ADDRESS>wrote:

There was some confusion about the timing, but this PR was merged after
the 1.9.0 code freeze (1.9.0-rc1 was released on October 14th
https://github.com/docker/docker/releases/tag/v1.9.0-rc1).
This driver will be part of the 1.10 release. For people wanting to give
it a spin before that, it is available in the "Experimental" or "Master"
builds (not intended for production)
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/16488#issuecomment-163797851.

Maybe the splunk driver could receive more than one host in "--log-opt splunk-url" for the cases splunk running in cluster ?

Thanks for the suggestion. With HEC the recommendation is always to have a load balancer in front of the HEC pool. Based on that I don't think we need clustering support. Also that will complicate the implementation.


Added Q-tensor example

Added a morpho example to minimize the Q-tensor free energy subject to anchoring boundary conditions. Also added a write-up (PDF and .tex) detailing the physics and morpho implementation.

I really like this, @joshichaitanya3; I think the documentation could be a good model for the other examples and we can merge this into the manual at some point.

Look like this just got merged in. I've created #45 to track the changes I mentioned above.

Oops, mea culpa, @ConduitDan ! I should note that the other examples don't necessarily meet these (excellent requirements!) Maybe we should have a convo about the above; it would be nice to figure out a standard template for examples etc. I feel that documentation belongs in the manual rather than the examples directory... but I really like the above.


Using dashes for lists doesn't work

The following markdown:
- Item 1
- Item 2
- Item 3

doesn't render using this library.

On further inspection, it is converting the dashes to bullets, but it's not creating new lines or wrapping text.

Hi @danieljvdm, thanks for the feedback! If you can fix it and send a PR that would be awesome. Otherwise I'll take a couple of minutes this week-end to solve this issue.

Hey, I just came back to this and seems that the intended behavior still doesn't work. Was this meant to be fixed when you closed the issue or should I look into doing a PR?

Hey @danieljvdm! If you still have your issue, don't hesitate to send a PR, you'd be nice to you yeah!


Auto-detect what I2C bus to use based on the Revision

If you try to run the piglow-example on an older (revision 1) Pi, you'll get a somewhat cryptic and unhelpful error message:
Traceback (most recent call last):
  File "piglow-example.py", line 52, in <module>
    piglow = PiGlow(1)
  File "piglow-example.py", line 24, in __init__
    self.write_i2c(CMD_ENABLE_OUTPUT, 0x01)
  File "piglow-example.py", line 43, in write_i2c
    self.bus.write_i2c_block_data(self.i2c_addr, reg_addr, value)
IOError: [Errno 5] Input/output error

The code has a comment about needing to use a different bus for the older Pi models, but it would be a better quickstart example if the code detected and picked for you!

A useful example, thank you!


object of type 'NoneType' has no len()

When I start training for more than 1 labels it shows an error as
Traceback (most recent call last):
File "", line 1, in
File "/home/deploy/rahul_vir/venv/lib/python3.5/site-packages/imageai/Detection/Custom/init.py", line 233, in trainModel
norm=normalize
File "/home/deploy/rahul_vir/venv/lib/python3.5/site-packages/imageai/Detection/Custom/generator.py", line 36, in init
if shuffle: np.random.shuffle(self.instances)
File "mtrand.pyx", line 4417, in numpy.random.mtrand.RandomState.shuffle
TypeError: object of type 'NoneType' has no len()
code:------------------------------------------------
from imageai.Detection.Custom import DetectionModelTrainer
trainer = DetectionModelTrainer()
trainer.setModelTypeAsYOLOv3()
trainer.setDataDirectory(data_directory="hololens")
trainer.setTrainConfig( ["hololens", "google-glass", "oculus"], batch_size=2, num_experiments=100, train_from_pretrained_model="pretrained-yolov3.h5")

How did you fix it?


refactor: migrate axios to node-fetch

Currently, node 16, hence the need for this extra package.
Migration will be good, but nothing planned at the moment.


added "swot/lib/domains/net/aims.txt" (AIMS)

added "swot/lib/domains/net/aims.txt" (African Institute for Mathematical Sciences (AIMS))

@deaspo First stage of verification passed, official domain is nexteinstein.org as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision. Proof of domain ownership: https://nexteinstein.org/industry-initiative-2/aims-ms4cr-open-opportunities/


TwitchPlays Balatro Request

Hey, i run a twitchplays channel and was hoping to do a run of Balatro. Unfortunately mouse only games are very difficult. Does your system allow for full control via keybinds including menus, item selection etc?

Hey there! Not an original mod creator, but I've set up a fork a while ago that aims to build up on it (https://github.com/maaxxaam/Keyboard-Voucher). This version allows to select/deselect cards in hand, play or discard the hand, sort it and show run and deck info, but not much more than that. My fork as of now goes out further by manually mapping most of other stuff during the run (selecting jokers, consumables, shop, using/buying/selling cards, etc.), but lacks menu navigation. I'm currently working on bringing that feature in (by reusing existing gamepad controls to be as vanilla friendly as I can and to write less of my own code). When I'll get that more or less ready to test, I can write here about it if you would be interested to check it out.


Tensorflow installation error

Hi I installed tensorflow for cpu and while trying to run command to check the version of tensor i am prompted error message.  Please help me to get this resolved
Please see below the log:
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>python
Python 3.5.2 (v3.5.2:4def2a2901a5, Jun 25 2016, 22:18:55) [MSC v.1900 64 bit (AM
D64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

import tensorflow as tf

Traceback (most recent call last):
File "C:\Program Files\Python35\lib\site-packages\tensorflow\python\pywrap_ten
sorflow.py", line 18, in swig_import_helper
return importlib.import_module(mname)
File "C:\Program Files\Python35\lib\importlib_init_.py", line 126, in impor
t_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 986, in _gcd_import
File "", line 969, in _find_and_load
File "", line 958, in _find_and_load_unlocked
File "", line 666, in _load_unlocked
File "", line 577, in module_from_spec
File "", line 906, in create_module
File "", line 222, in _call_with_frames_removed
ImportError: DLL load failed: The specified module could not be found.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Program Files\Python35\lib\site-packages\tensorflow\python_init_.p
y", line 66, in
from tensorflow.python import pywrap_tensorflow
File "C:\Program Files\Python35\lib\site-packages\tensorflow\python\pywrap_ten
sorflow.py", line 21, in
_pywrap_tensorflow = swig_import_helper()
File "C:\Program Files\Python35\lib\site-packages\tensorflow\python\pywrap_ten
sorflow.py", line 20, in swig_import_helper
return importlib.import_module('pywrap_tensorflow')
File "C:\Program Files\Python35\lib\importlib_init.py", line 126, in impor
t_module
return _bootstrap._gcd_import(name[level:], package, level)
ImportError: No module named '_pywrap_tensorflow'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1, in
File "C:\Program Files\Python35\lib\site-packages\tensorflow_init_.py", lin
e 24, in
from tensorflow.python import *
File "C:\Program Files\Python35\lib\site-packages\tensorflow\python_init_.p
y", line 72, in
raise ImportError(msg)
ImportError: Traceback (most recent call last):
File "C:\Program Files\Python35\lib\site-packages\tensorflow\python\pywrap_ten
sorflow.py", line 18, in swig_import_helper
return importlib.import_module(mname)
File "C:\Program Files\Python35\lib\importlib_init_.py", line 126, in impor
t_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 986, in _gcd_import
File "", line 969, in _find_and_load
File "", line 958, in _find_and_load_unlocked
File "", line 666, in _load_unlocked
File "", line 577, in module_from_spec
File "", line 906, in create_module
File "", line 222, in _call_with_frames_removed
ImportError: DLL load failed: The specified module could not be found.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Program Files\Python35\lib\site-packages\tensorflow\python_init_.p
y", line 66, in
from tensorflow.python import pywrap_tensorflow
File "C:\Program Files\Python35\lib\site-packages\tensorflow\python\pywrap_ten
sorflow.py", line 21, in
_pywrap_tensorflow = swig_import_helper()
File "C:\Program Files\Python35\lib\site-packages\tensorflow\python\pywrap_ten
sorflow.py", line 20, in swig_import_helper
return importlib.import_module('pywrap_tensorflow')
File "C:\Program Files\Python35\lib\importlib_init.py", line 126, in impor
t_module
return _bootstrap._gcd_import(name[level:], package, level)
ImportError: No module named '_pywrap_tensorflow'
Failed to load the native TensorFlow runtime.
See https://github.com/tensorflow/tensorflow/blob/master/tensorflow/g3doc/get_st
arted/os_setup.md#import_error
for some common reasons and solutions.  Include the entire stack trace
above this error message when asking for help.

I see you are trying to install on Windows, @mrry has a great installation troubleshooter script that can help pinpoint issues available here: mrry's Self-check Script

This issue is automatically closed due to lack of activity. Please re-open if this is still an issue for you. Thanks!

Installing the Microsoft Visual C++ 2015 Redistributable Update 3 has solved my issue