Make Drupal VM prod-ready (on a DigitalOcean 1GB Droplet)

This VM would do nicely on a 1 GB (or greater) Linode of DigitalOcean VM, or really anywhere (server or VM) where you would want to host a typical Drupal site.
While it doesn't (yet) include Nginx or Varnish as a reverse proxy (which would make for huge gains in performance for a typical Drupal site), it has the entire stack in place for a decent and secure production environment. Plus, those comfortable developing with the Drupal VM could use the exact same stack/configuration for production (or other environments), making this a more flexible environment.
I think I can make a couple tweaks to the playbook (to do things like not disable AppArmor on production, based on a variable, and to add the geerlingguy.security role for extra security hardening), and then add a guide for 'setting up a Drupal VM production server on DigitalOcean... or Linode... etc."
It's a similar setup to how I deploy and locally test www.midwesternmac.com, www.hostedapachesolr.com, www.servercheck.in, etc.
While I've had the idea in my head a bit, it was really @wizonesolutions, @attiks and @stevepurkiss who kicked off this issue—see: https://twitter.com/wizonesolutions/status/591958086648274944
Steps to success:

[x] Add new 'extra_security_enabled' variable (to be used as toggle for security-related features)
[x] Don't disable AppArmor MySQL config when secure variable is true
[x] Use geerlingguy.security role when secure variable is true
[x] Add example-prod.config.yml file with example configuration for 1GB VM baseline (targeting DigitalOcean or Linode, for starters... but it will be generic enough to run anywhere).
[ ] Add Wiki page "Drupal VM prod on DigitalOcean" with a tutorial
[ ] Copy the configured make file up to the server into /tmp directory (instead of using shared path)—possibly create new issue for this.

Hopefully I'll have this ready by the Ansible for Drupal Infrastructure BoF on Wednesday at DrupalCon LA! https://events.drupal.org/losangeles2015/bofs/ansible-drupal-infrastructure-and-deployments

I suppose I'll have to come to that BoF :o

Almost there. I got almost everything working, besides the make file Drupal site build (since it's configured for vagrant/local only right now). See the last checkbox in the OP.

Curious why you're using root as the ansible user?
Don't you want to use a different user and add sudo only where necessary?

@ajfabbri - As this is more of a PoC for beginners (who may not be too familiar with the entire SSH key-based authentication workflow), and as DigitalOcean's new droplets are configured using your SSH key for the root account by default (with no other system users available by default), I wanted to keep things simple.
For those wishing to base a production site on Drupal VM's configuration, I think the best route at this point would be to fork the project and make changes necessary to add a separate admin account, and have a more full-fledged provisioning process.
For Drupal VM's purposes, I just want to show how simple it is to use the same provisioning configuration to provision to a local VM as to a cloud server.

Sounds reasonable.  I would add some comments in the files to that effect maybe?

Also, I have this stuff working with Rackspace if you'd like a patch.  If so, let me know how you'd want it structured (e.g. another directory parallel to prod/, or just make prod/ stuff speak both providers and update README)

@ajfabbri - How about just adding another config to the prod/ directory? And you could rename the configs to something like prod-digitalocean.config.yml and prod-rackspace.config.yml... that kind of thing. And update the README.

Just noticed the prod stuff bypasses Vagrant.. which makes sense.  In case anyone wants to spin up VMs on rackspace via Vagrant, checkout vagrant-rackspace.  We were able to integrate it into the Vagrantfile here easily.
Besides the Vagrantfile, though, I don't think there is much of a delta for Digital Ocean versus Rackspace.  You are just doing ansible/ssh to a linux box.

Sounds good! I've never directly used Rackspace, but a VM is a VM (on most platforms, at least), so I'm sure you're right!

Getting closer...

In testing this, I noticed the vagrant_user is still required. I'd commented it out because deploying to a real VM isn't vagrant based, but the playbook fails. https://github.com/geerlingguy/drupal-vm/blob/master/provisioning/tasks/www.yml#L12
Maybe this variable should be refactored to be application_user or something more generic?

@CashWilliams - D'oh! You're correct. I'll get that fixed as well. Basically, to make things simpler, I need to finish divorcing the playbook from the idea of being deployed to Vagrant-based installations.

re root login - I see your point on simplicity, however it's bad practice to allow ssh from root, and the security role disables it anyway https://github.com/geerlingguy/ansible-role-security/blob/master/tasks/ssh.yml#L10
I haven't tried, but I'd think running this a 2nd time would get a failed login? I added sudo: yes to the top of the playbook and provided --ask-become-pass to the command and all (almost) worked fine.

I installed DrupalVM with examples/prod/README.md instructions successfully. Just small error:
TASK: [Generate Drupal site with drush makefile.] *****************************
failed: [] => {"changed": true, "cmd": ["/usr/local/bin/drush", "make", "-y", "/vagrant/drupal.make.yml", "--no-gitinfofile"], "delta": "0:00:00.180702", "end": "2015-08-02 07:01:24.956305", "rc": 1, "start": "2015-08-02 07:01:24.775603", "warnings": []}
stderr: file_get_contents(/vagrant/drupal.make.yml): failed to open stream:  [warning]
No such file or directory make.utilities.inc:527
Invalid or empty make file: /vagrant/drupal.make.yml                 [error]
Beginning to build /vagrant/drupal.make.yml.                         [ok]
No core project specified.                                           [error]

I copied file myself and rerun playbook to fix it.

@kalabro - Ha, thanks for reporting this nonetheless (especially that you had success getting everything going on DO!); I've been putting off completing this task for a little while, mostly because I spent a bit of time focusing on the 2.0.0 release and getting a few more dev-focused features completed. I'll be finishing this off very soon!

This is great! Here's where I'm at:

had to create /vagrant and copy the drupal.make.yml file up but unlike above it wouldn't let me rerun playbook due to git existing files/access issue so rebuilt drop & did that first
site couldn't write to sites/default/files/something, couldn't ssh in access denied so turned off security settings for the moment - perhaps fail2ban issue, not sure
need to work something 'better' out than my usual sudo chmod -R 777 files ;)
got rate-limited, googled, found answer by adding --prefer-source to drush_composer_cli_options

realising quickly quite just how much there is to do to set these things up - thanks for the kickstart!

A few of these quirks have now been fixed:

The makefile path no longer relies on on a /vagrant directory https://github.com/geerlingguy/drupal-vm/commit/e11b685f591a397824d8e2a2de0bcc995f0cde35
Not mentioned before but the drush aliases scaffolded on the remote are now the correct aliases https://github.com/geerlingguy/drupal-vm/commit/43914c513a02ee00593c447e6befc72f044812a0

Once https://github.com/geerlingguy/drupal-vm/pull/378#issuecomment-174257495 gets fixed upstream in Vagrant the last technical bit can be fixed too (also mentioned here https://github.com/geerlingguy/drupal-vm/issues/305#issuecomment-177395703).

[ ] Determine whether it's easier to specify a command-line-passed vars filename for the override for prod config, or specify extra-vars via CLI.

It could be solved in a similar way as #378. By checking if there's a local.config.yml and passing that on as an extra variable to ansible that gets included dynamically if defined.

We're awfully close on this now!

I think I can push a couple more things through to get this working decently. We can optimize later, but I'm testing on a fresh droplet right now. My idea is to add an 'init' playbook that sets up an admin account with the current user's SSH key; then run the playbook through that user's admin account with sudo, and it will set up security (e.g. disallow root, etc.), and the rest of the configuration.
Still need to add some big, bold warnings about security and such, but I think I can have this working tonight!

I ran into https://github.com/ansible/ansible-modules-core/issues/2585 when testing this with Ansible <IP_ADDRESS> (hopefully 2.0.1 is released soon so I can stop patching file.py all the time!), so I'm re-testing with a fresh VM on DigitalOcean. Everything's working great so far up to the Drupal installation. Fingers crossed!

I added #455 to address the (now-struck) task:

[x] Determine whether it's easier to specify a command-line-passed vars filename for the override for prod config, or specify extra-vars via CLI.

It worked!

hi - is there a guide?  Where is it? I'm happy to give it a spin and provide feedback.  thx.

@shawnholt - See: https://github.com/geerlingguy/drupal-vm/tree/master/examples/prod (specifically, the README in there).

GREAT!  So I guess if I'm on windows, I should install Ansible or create another droplet to install/run ansible (then destroy when done....)

@shawnachieve - check out: http://www.jeffgeerling.com/blog/running-ansible-within-windows
But also, you could just install a local instance of Drupal VM (vagrant up), then log in (vagrant ssh) and use ansible and the other commands inside the VM (just cd over to /vagrant).

thx @geerlingguy !  yeah I had some trouble with ansible/vagrant and windows.
sorry if this is a dumb question but ...
If I create 2 DO droplets, one for Drupal VM and another disposbile to install ansible is there a problem if i destroy the ansible droplet or will i need that to manage Drupal VM?

@shawnholt - since the security role sets things up for automatic security updates by default, things should be pretty solid after the initial provisioning.
I'd recommend you set up a system that you can easily re-setup again in the future if you want to make changes through Ansible, but technically, after the VM is built, you don't ever need to run the playbook again.

Great - i can just keep the snapshot if i need it. will give it a spin!


Fix heatmap colors for Chrome/Safari

Workaround Chrome/Safari bug
Fixes #5420

Should also fix #5191


syslog plugin is unable to collect data

i loaded syslog plugin in centos 7....and my syslog deamon is running....when i start my syslog task to collect metrics to a file i can see null displaying in file....when i do snaptel task watch nothing is showing there....what might be the issue here?
my task file looks like below
---
  version: 1
  schedule:
    type: "simple"
    interval: "1s"
  max-failures: 10
  workflow:
    collect:
      config:
        /opsvision/syslog:
          port: 1514
          bufsize: 1024
      metrics:
        /opsvision/syslog/counter: {}
        /opsvision/syslog/event/*/summary: {}
        /opsvision/syslog/event/*/message: {}
      publish:
        - plugin_name: "file"
          config:
            file: "/tmp/syslog_metrics.log"

In place of
# remote host is: name/ip:port, e.g. <IP_ADDRESS>:514, port optional
#<IP_ADDRESS>:514
# ### end of the forwarding rule ###

<IP_ADDRESS>:514 should i have an entry of . <IP_ADDRESS>:514?

I do not know where the snap-telemetry syslog plugin is installed.  However, you have to tell rsyslog to send events to the plugin.  The plugin configuration says it will listen on port 1514.  Depending on where the plugin is installed, you need to configure rsyslog to send to the plugin.  If the plugin is installed locally and listening on <IP_ADDRESS>:1514, then yes, configure rsyslog to send to that and then restart the rsyslog daemon.

@sachinkademane were you able to get things working by making the config changes to rsyslog?

@dishmael No....still i am unable to get mtrics from syslog..i changed that <IP_ADDRESS>:514 to 1514 but still it is unable to pull metrics...i think now my plugin config and rsyslog config matches properly...but still unable to pull metrics

what does it say when you run netstat -an | grep 1514

Since i uncommented UDP and TCP it is showing following
[root@AELAB110 ~]# netstat -an | grep 1514
tcp        0      0 <IP_ADDRESS>:1514             <IP_ADDRESS>:*               LISTEN
tcp6       0      0 :::1514                  :::*                    LISTEN
udp        0      0 <IP_ADDRESS>:1514             <IP_ADDRESS>:*
udp6       0      0 :::1514                  :::*

change your rsyslog.conf to the local IP address and port 1514.  Then restart rsyslog and the plugin.

yea that also i did and i tried...but still the result is same

I assume everything you are doing is on the same host. Try setting up a new line to log to a test file in your rsyslog.conf file to confirm it is working properly.
*.*                                                  /var/log/testing
When you restart rsyslog, confirm you have a log file /var/log/testing.


Being able to clone from a specific changeset

...like what could be done with quick-clone

So, what's the difference betwen "quick-clone" and "clone" then?

So, what's the difference betwen "quick-clone" and "clone" then?

That's a good question...
quick-clone is still there to clone only ONE changeset.
So, what this new option bring:

Better discovery. Quite some new users ask if it is possible to clone from a specific changeset but not knowing quick-clone because clone is the main entry, they think that it is not possible. I have answer much more time that I would like on this subject or even tutorial not knowing this option...
Not be obliged to do a quick-clone then a fetch or a pull (all is done in the same command!) especially when you are a new user and that you do not understand well what are the differences between all the commands
More important, you could use all the options only available with the clone commands. I especially think to --export and --with-branches that will permit to export a tfs repository to a git one but just since a specific changeset particularly in the case where you have a huge and complex history that perhaps git-tfs could not handle perfectly (or that you don't want to bring entirely like Microsoft recommend ;) ). It worked well on my test tfs repository and not possible to do before that PR. But it's the first step of a more complex development...

:+1:


dynpros and cua in FUGR

Hi,
I suggest moving methods deserialize_dynpros and deserialize_cua to class lcl_objects_program as protected, that way both lcl_object_fugr and lcl_object_prog can access it. Currently it looks like both methods exist twice in the big picture?

Yes, identical. Will try with next PR

just do another commit to your branch, then it will show up in this PR

OK, got it, thanks

Done.

thanks, looks good to me


fix: standardise hierarchy env var across apps

This implements the variable changes to standardise ABAC environment variables between SCS and SCG following issue raised by customer.
Already completed in base/profile manifests from release v1.21.0+

Lgtm

Lgtm


[Demo App] Create the tokens section in the demo application

Internal reference
Jira reference: OUDS-284
Description
As a user of the design system for mobile
I want to find the token section in the demo app
So that the user can access the list of the available tokens in alphabetical order:

Border
Color
Dimention
Elevation
Grid
Opacity
Motion
Typography

Context
The Ouds Mobile app is demonstrating the available work within the Design System dev library. The objective is to present the tokens.

The initial app architecture should follow previous ODS app structure Navigation menu sections > Top Navigation item > card view to selec an item > item page with content description
As for the ODS app the bottom navigation will replace the "Guidelines" menu item section with this new "Tokens" menu item
The selection page of this section will use the large card model and prensent the list of tokens in alphabetical order
A new design will be provided to support each component page description

📣 New TestFlight ALPHA uploap available 🚀
Please, get the new build from TestFlight app.

Display name: OUDS Showcase ALPHA (120)
Version: 0.3.0
Build number:<PHONE_NUMBER>
Build tag: ab352e4
Build type: ALPHA
Build details (GitHub): 120

This is an automated message sent with love and Fastlane from our CI/CD pipeline 🤘

📣 New TestFlight ALPHA uploap available 🚀
Please, get the new build from TestFlight app.

Display name: OUDS Showcase ALPHA (120)
Version: 0.3.0
Build number:<PHONE_NUMBER>
Build tag: bf5cc7a8c2568f02ced056183b40caae629948d0
Build type: ALPHA
Build details (GitHub): 120

This is not an automated message, there was an issue with TestFlight and Fastlane making the CI/CD pipeline fail after the delayed upload

@pylapp
"Border page In the radius list I see the borderRadiusPill"
Does not exist, do we need to add it ?

@pylapp "Border page In the radius list I see the borderRadiusPill" Does not exist, do we need to add it ?

No. It has been removed since v0.2.0.

📣 New TestFlight ALPHA uploap available 🚀
Please, get the new build from TestFlight app.

Display name: OUDS Showcase ALPHA (120)
Version: 0.3.0
Build number:<PHONE_NUMBER>
Build tag: 70e992d
Build type: ALPHA
Build details (GitHub): 120

This is not an automated message, there was an issue with TestFlight and Fastlane making the CI/CD pipeline fail after the delayed upload
cc @B3nz01d

📣 New TestFlight ALPHA uploap available 🚀
Please, get the new build from TestFlight app.

Display name: OUDS Showcase ALPHA (120)
Version: 0.3.0
Build number:<PHONE_NUMBER>
Build tag: 66c6580
Build type: ALPHA
Build details (GitHub): 120

This is an automated message sent with love and Fastlane from our CI/CD pipeline 🤘

📣 New TestFlight ALPHA upload available 🚀
Please, get the new build from TestFlight app.

Display name: OUDS Showcase ALPHA (120)
Version: 0.3.0
Build number:<PHONE_NUMBER>
Build tag: fd3cb86
Build type: ALPHA
Build details (GitHub): 120

cc @B3nz01d @pylapp @ludovic35 @Tayebsed93 @mccart77
This is an automated message sent with love and Fastlane from our CI/CD pipeline 🤘

New version available since versionv0.3.0


External call

Description
If there is an external call to a precompile then we probably don't want to report an issue at all.
Example contract for which we report a vulnerability: https://github.com/TokenMarketNet/smart-contracts/blob/master/contracts/test/TestSolidityAddressHash.sol

@JoranHonig @norhh we should also downgrade the severity of external calls to "low", as an external call by itself doesn't cause a vulnerability.

@b-mueller external calls that have a static target will already be seen as low severity.
We can definately make regular external calls low severity as well. But we should open up another issue for that 😅


1.0.184 might be causing a compilation error.

I got a compilation error which doesn't occur with serde 1.0.183. Is it a some breaking change?
example project
Cargo.toml
[package]
name = "serde_184_error"
version = "0.1.0"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
sentry = "0.31.5"

#The compile error not occured on serde = "= 1.0.183"
serde = "1.0.184"

Error message
    Updating crates.io index
    Checking sentry-types v0.31.5
error[E0507]: cannot move out of `*self` which is behind a shared reference
    --> /g/cargo/registry/src/index.crates.io-6f17d22bba15001f/sentry-types-0.31.5/src/protocol/v7.rs:1083:10
     |
1083 | #[derive(Serialize, Deserialize, Debug, Clone, Parti...
     |          ^^^^^^^^^
     |          |
     |          data moved here
     |          move occurs because `unrecognized` has type `v7::Context`, which does not implement the `Copy` trait
     |
     = note: this error originates in the derive macro `Serialize` (in Nightly builds, run with -Z macro-backtrace for moreinfo)
help: consider borrowing here
     |
1083 | #[derive(&Serialize, Deserialize, Debug, Clone, PartialEq)]
     |          +

For more information about this error, try `rustc --explain E0507`.
error: could not compile `sentry-types` (lib) due to previouserror

Indeed, this was a bug in #2570. I've published serde_derive 1.0.185 with a fix. Sorry about the breakage!

@dtolnay I was wondering why my CI builds started failing. Thanks for the quick fix! 🍺

@dtolnay Thank you for the excellent job as always. In fact, on my team, we refer to you as  "dtolnay Sensei" with respect :)


Can I disable some providers in the config file?

Feature request
I have several providers configured and I want to control whether a model is enabled or not by a certain configuration item (like diasbled).
Why?
I'd like to be able to easily switch between providers.
Alternatives
No response
Additional context
Also, if I have multiple providers configured at the same time, how are they determined to be called or not?

Hello @zybzzc
There is no disabled option yet. Please remove the key property from the configuration file.

open ~/.aicommit2
update your config
remove key or change key to another property (e.g. key => key2)

@zybzzc I've just updated to v2.1.3 to add disabled option.
Please take a look at the link.

@tak-bro Thank you!


Update trashschedule to 2.3.0

Please update my adapter ioBroker.trashschedule to version 2.3.0.
This pull request was created by https://www.iobroker.dev c0726ff.

2.3.0 created 25.10.2023
900 user
OK


Remove obsolete Xerces dependency

In my project I use mockServer and log4j2. When I upgraded log4j2 to 2.9.1 I got a nasty error "java.lang.AbstractMethodError: javax.xml.parsers.DocumentBuilderFactory.setFeature(Ljava/lang/String;Z)V" after some researches, that comes from old version of Xerces as the one used in mockServer.
So I had to do the same workaround as https://github.com/jamesdbloom/mockserver/issues/362.
I propose this pull request to remove Xerces dependency. As far as I understood mockServer's code I think this dependency is no longer required.

@jamesdbloom can you tell me why my build is failing.
By the way, this code is not meant to be built on Windows, i can't run the unit test properly, that's a shame.

The build failed due to a random reason.  For some unknown reason about 1/10 build fail in the maven plugin integration tests.

  There has been some effort to ensure that this runs on Windows but I haven't had time to install a Windows VM and test it properly.

Can you please raise a bug / issue with the specific reasons why the build doesn't run on Windows.


Memory leak since upgrade to 1.19.1

BUG REPORT INFORMATION
Description
upgrading to 1.19.1 (from 1.18.1) caused portainer to start leaking memory
the upgrade moment can be seen here (monitored via influxdb/telegraf):

redeployed again to make sure. After 1 day:

Steps to reproduce the issue:

deploy

docker run --restart=always -d --name portainer -p 9000:9000 \
                  -v /portainer/data:/data \
                  -v /var/run/docker.sock:/var/run/docker.sock \
                  portainer/portainer

monitor & wait for sufficient amount of time to observe the leak

Could this be a goroutine leak by any chance?
Technical details:

Portainer version: 1.19.1
Target Docker version (the host/cluster you manage):

 Engine:
  Version:      18.03.0
  API version:  1.37 (minimum version 1.12)
  Go version:   go1.9.4
  Git commit:   0520e24
  Built:        Fri May  4 12:40:05 2018
  OS/Arch:      linux/amd64
  Experimental: false

Platform (windows/linux): Photon OS
Command used to start Portainer: see above

Hi @d-led
Anything in the Portainer container logs to share with us? Could you try to reproduce by starting Portainer with the --no-snapshot flag and check the memory usage?
Could be related to #1991

@deviantony ok. deploying

I'm not sure, the --no-snapshot flag reaches the container.
inspecting it after restarting it manually on the command line:

the leak seems to be consistent with the 5 minutes frequency (10:58-11:03)

@d-led a message should be displayed in the home view telling you that the snapshot are disabled.

I'm not sure if it's related to this, but I noticed, after updating from 1.18 to 1.19 that when the portainer container is running on my docker host, it leaves a lot of open file descriptor (mostly sockets), with enough time, the dockerd runs out of available filedescriptors (1024).
Terminating the container immediately releases the open files.
The increase in filedescriptor usage seems also to happen every 5 minutes:

@neothematrix thanks for the report, the related issue to this problem is #1991
Although I believe that these issues are related, we're investigating.

ah! sorry about that I stopped at the first issue and didn't look at the rest.
Is there an environment variable I can set to disable snapshot? Unfortunately on QNAP Container Station I cannot really add custom parameters as I don't control the "docker run" directly.

while the snapshots are turned off in my installation (according to the UI), the file handles keep increasing by 1 every 5 minutes:

(2 redeploys seen here)

@neothematrix no sorry it's only available via a CLI flag.
Thanks to your report both of you, we're checking what might be causing these issues.

@deviantony thanks too!  Thus, as a temporary work-around, I have tried passing the snapshot interval via the command line, which didn't reach the UI, thus I simply set the interval in the settings:

1 file handle and a bit of memory in 9999h is ok for now 😄
@neothematrix I'd recommend simply setting the interval to something large for now

in my case, turning off snapshots (I managed to pass the --no-snapshot flag) seems to have completely solved the filedescriptor leak, latest deploy of the portainer container was at 18:00 in the graph:

however I never noticed the memory leak issue:

however I did change another parameter, I'm now bind mounting /var/run/docker.sock instead of the whole /var/run folder as I was doing before (I had no choice with Container Station since it allowed only directory bind mounts, not files), I'll try to perform a reverse-test by removing the --no-snapshot flag and see if the fd leak starts again.

@deviantony yes, no leaks every 5 mins. Strange, that contrary to @neothematrix, I could pass the flag (as seen in the UI) to stop snapshots, but the flag did not have an effect

Same problem here. Is there any solution or workaround about this issue? Thanks!

@deviantony I just started it (without the no-snapshot parameter of course) and keeping it monitored, I'll let you know in a while the status of open file descriptors, meanwhile thanks for the fix!

Thanks for the report @neothematrix, I'm going to wait for an update of the other contributors if possible before we decide to merge this fix.

no file or memory leaks → OK!

@d-led is this using the portainer/portainer:fix1991-open-files image?

@deviantony yep
6f6d2d412365        portainer/portainer:fix1991-open-files    "/portainer"             4 hours ago

the red line is the moment where I deployed. Stil looks ok

no file handle leak for a day. Memory usage looks like this:

Awesome @d-led, I'll merge the fix.
Thanks a lot for the feedback !

@deviantony superb. Thank you too

Would also like to chime in and say thanks, I pulled this image about 12 hours ago and haven't seen any leaking since. Anxiously waiting for this in the latest image :slightly_smiling_face:

Looks good here also..

Thanks again for the feedback everyone.


I don't know.

Can you revert everything before 2b74ce5624984a1d23d10a873460faaa24b95d09 and delete all these commits?


User and Pasword always invalid

hello i follow the step for Running SerpBear Locally
Fresh install
i add .env.local copy past of the ex. no change and i can't login

Are you using docker or are you pulling the source from github directly ?

Thanks from github directly

.env.local
USER=admin PASSWORD=0123456789 SECRET=4715aed3216f7b0a38e6b534a958362654e96d10fbc04700770d572af3dce43625dd APIKEY=5saedXklbslhnapihe2pihp3pih4fdnakhjwq5 SESSION_DURATION=24 NEXT_PUBLIC_APP_URL=http://localhost:3000

Same issue with docker

Solved fly.io was running ... Thanks


Show incorrect Destination Chain fee on XCM history detail

Describe the bug
Show incorrect Destination Chain fee on XCM history detail
Actual: Do not get Destination Chain fee but show Destination Chain fee = Origin Chain fee

Expect: Temporarity remove Destination Chain fee on the history detail

Version test: https://file.cdmteck.com/s/4oimk9zDJ8R5Aai/download?path=%2F&files=./upgrade-ui-build-1.0.9-2023-06-17T07-35-51UTC.zip
Validation passed.
Notes: Re-check all transaction history


The * operator should perform dot product of vectors

Using the operator * to perform element-wise multiplication (e.g. for Vector2 in #ktx-math) is a sin. There is a special circle in Hell (of length 3π) for those that blaspheme about Linear Algebra.
I propose instead an infix fun named hadamard or schur -- as penance for those who seek brevity at the cost of their souls.

Um.
Not that you're wrong, but this is pretty much the behavior that I would expect as a simple ignorant app developer, who normally doesn't do a lot of math. I mean, in case of simple mobile games, you're far more likely to want to combine something like vector representing speed with sort of a speed bonus vector with simple multiplication, rather than perform any advanced calculations, right? This might take me straight to hell, but I'm guessing I'd write such extension in personal projects sooner or later even if it was removed from there.
If you want to "fix" this issue, I'd be happy to go through the pull request though.

Yeah, I know, it was mostly tongue-in-cheek. I understand the context. And it mainly stems from the fact of using vector when we actually mean a tuple of numbers and we just want to streamline a set of operations to the whole tuple...
As a serious proposition now: maybe we should use *= (i.e. timesAssign(..)) for the Hadamard product, since as you say, it's mostly used as a self-updating  position *= velocity, and reserve the regular multiplication for dot products, since the result is not something self-updating but rather a new kind of object (a scalar or a square matrix -- if we add the notion of a transpose to the mix).
But only if enough people agree with this - otherwise indeed, practicality wins the day, sinners be damned...

times operator lets you use *= for free. Providing two different implementations for what's supposed to be the same operator might be really confusing, especially if you want to chain some operations on vectors. I'm glad you agree with the practical approach. If more people want the dot instead of scl, changing the implementation would be trivial - but for now let's just leave it in the backlog.

Alrighty :)
Cheers!

Dot product was added as dot infix function in #130.


fix: add max number of concurrent calls allowed for the C method configuration item

Codecov Report
Attention: Patch coverage is 92.85714% with 9 lines in your changes missing coverage. Please review.

Project coverage is 64.66%. Comparing base (4fc5884) to head (2bb3e29).

Files with missing lines
Patch %
Lines

db/async/row.go
73.91%
5 Missing and 1 partial :warning:

controller/ws/query/ws.go
66.66%
2 Missing :warning:

controller/ws/tmq/tmq.go
66.66%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##              3.0     #353      +/-   ##
==========================================
- Coverage   69.29%   64.66%   -4.63%
==========================================
  Files          88      105      +17
  Lines       11245    13908    +2663
==========================================
+ Hits         7792     8994    +1202
- Misses       2721     4115    +1394
- Partials      732      799      +67

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Wrong output allocation in matrix/vector product

When computing the product between a (row) AlgebraicVector and an AlgebraicMatrix or an AlgebraicMatrix and a (column) AlgebraicVector the size allocated for the output vector is wrong, leading to unexpected results or errors if the matrix is not square.
The allocation occurs at lines 57 and 79 of AlgebraicMatrix_t.h.

line 57: obj1.size() should be obj2.ncols()
line 79: obj2.size() should be obj1.nrows()

fixed by merge in commit #47


Potential rendering issue with basic paragraphs

Not sure if this is an issue of not applying any styles, but I've got a layout issue with a couple of paragraphs.
This is the code:
<Markdown>{this.props.ingredient.description}</Markdown>

Text:
A thick, slippery wheat-flour noodle from Japan.

Look for fresh udon in the refrigerator or freezer aisles. Dried udon does exist, but this is the one noodle that really doesn’t take well to the process.

Render:
https://www.evernote.com/shard/s554/sh/c1249afc-7a25-4113-81a3-98e6c4b3ce3b/e878dd870f8870d7674943c9e30970e0

Did you manage to solve this? I'm also looking in manipulating styles to get simple line-breaks to render correct but no dice (yet).

might be related to https://github.com/Khan/simple-markdown/issues/32


Has this been abandoned?

This software looks like it hasn't been updated by the person in control of it in over a year...
Has it been abandoned?  Is there someone else out here that'd start a new git and implement the updates that there are pull's for and keep it going under a new name??
I would myself, except I'm still new to Github and really don't know what I'm doing yet...
Thanks!

The last bunch of merged pull requests were merged after half a year of inactivity, so it's hard to say.

I honestly don't know, I've tweeted at the developer asking if he needs donations to keep working on this and so forth but have never received a response.

Judging from the forks graph alone, @FurryFur seems to have improved this tool for a while over here. Not anymore apparantly though.

Yeah none of the forks have continued to be maintained.

I'll try my hand at continuing it a bit by simply merging other peoples merge requests into my repository.
I know some python, but I have zero experience with bigger projects like this one, so if you want to help/join/collaborate, feel free to ask & I'll set you as admin or whatever it's called on here.

@noodle- Yeah add me in. I'm proposing the following remediation plan of action:

We go through the develop branch and ensure all the tests pass and determine code coverage (no more merges until that is done and 2 is done).
Duplicate and set up the Travis settings to make sure everything is getting tested on a variety of operating systems.
Begin the very tedious process of merging in some of these existing PRs and noting where they were merged, if possible retain history for the associated user to try and get them involved.
Start looking through the issues, create tags that are available for users in the new repo which we can port over if needed.

My only experience with working on a large project is https://github.com/saltstack/salt/, and I've learned the following from that:
Prioritize proper release naming, no bugs on releases, and proper issue/PR handling over anything else. If we can get more people who are good with Python involved that would be beneficial. My Python is okay but I am by no means a grade A developer.

I'm in for testing/validating on Windows OS

From: Forrest<EMAIL_ADDRESS>Sent: Wednesday, August 10, 2016 3:39:41 PM
To: chrippa/livestreamer
Subject: Re: [chrippa/livestreamer] Has this been abandoned? (#1427)
@noodle-https://github.com/noodle- Yeah add me in. I'm proposing the following remediation plan of action:

We go through the develop branch and ensure all the tests pass and determine code coverage (no more merges until that is done and 2 is done).
Duplicate and set up the Travis settings to make sure everything is getting tested on a variety of operating systems.
Begin the very tedious process of merging in some of these existing PRs and noting where they were merged, if possible retain history for the associated user to try and get them involved.
Start looking through the issues, create tags that are available for users in the new repo which we can port over if needed.

My only experience with working on a large project is https://github.com/saltstack/salt/, and I've learned the following from that:
Prioritize proper release naming, no bugs on releases, and proper issue/PR handling over anything else. If we can get more people who are good with Python involved that would be beneficial. My Python is okay but I am by no means a grade A developer.

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/chrippa/livestreamer/issues/1427#issuecomment-238980217, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AESJ1mL0Dt2BFJOtWAwO4H1O0wkvkJolks5qeij9gaJpZM4JeurO.

This reminds me that once we have things in a reasonable state we should notify these guys: https://github.com/bastimeyer/livestreamer-twitch-gui

Maybe even ask them for help with it?
On Aug 10, 2016 9:49 AM, "Forrest"<EMAIL_ADDRESS>wrote:

This reminds me that once we have things in a reasonable state we should
notify these guys: https://github.com/bastimeyer/livestreamer-twitch-gui
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/chrippa/livestreamer/issues/1427#issuecomment-238982738,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AT0oiI3Qfqu_LkRMAog4b8udf0PJSW5-ks5qeis9gaJpZM4JeurO
.

@Junior1544 I edited my message to mention the primary maintainer.

@Junior1544 My plan was more along the lines of

Look at all the pull requests on here
Merge & test whether it works
yay

So maybe it's better if you set up the (new) main repository and add me as little helper instead. I don't have time to do much, but I'd be happy to help & learn wherever I can.

Thanks for mentioning me here and letting me know...
Sadly, I don't have any python knowledge, all I can do is open an issue on my repo and add a reference to this thread here. Hopefully you'll find a couple of more people that support your fork ideas.
It's a shame that Chrippa seems to have abandoned his project. Personally, I would welcome a fork with all necessary bugfixes and having an assurance that it's being maintained if something breaks and gets fixed in time. We don't have this now and it's quite scary, because it might break any day. Having a working and maintained fork would save me from reimplementing something similar to livestreamer in my application.
The last time something broke regarding viewing Twitch streams, it was fixed within a couple of hours, back in early december 2014. I've heard that there are currently some issues with certain VODs on Twitch that livestreamer is unable to read correctly. That's a problem for the future plans of my application. There are also a couple of player argument parsing bugs in the current version that are around for quite some time.
As I've already said, I'm fine with the idea of a fork, but I don't know how you are planning to do this.

Are there any licensing issues?
Would a rename be required? If so, the name of my application wouldn't make sense anymore if I support the fork.
Will the API/CLI change? Are there any other changes necessary that might break the compatibility of both programs?
Will the maintainers be able to lead the fork into the right direction or will the community reject or ignore it?

I have no idea on where to even start, otherwise I would have done it
already...
Sorry.
On Aug 10, 2016 10:58 AM, "Nils"<EMAIL_ADDRESS>wrote:

@Junior1544 https://github.com/Junior1544 My plan was more along the
lines of

Look at all the pull requests on here
Merge & test whether it works
yay

So maybe it's better if you set up the (new) main repository and add me as
little helper instead. I don't have time to do much, but I'd be happy to
help & learn wherever I can.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/chrippa/livestreamer/issues/1427#issuecomment-239002117,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AT0oiPSj9dvw_5uju8wFS-0u1DlPjCDTks5qejtngaJpZM4JeurO
.

I think a new fork with new maintainers might be a good idea at this point. Also sorry to say that my fork is quite a lot of extra code and I didn't write any tests for it. It probably needs tidying up quite a bit. I used a lot of threading, and it's prone to deadlock issues. The mailbox behavior should be changed to work like a golang channel to make it a bit more consistent. When I wrote it I was trying to add code without changing too much existing stuff. A lot of it could probably be rewritten to be a lot simpler.

I don't know much about the code of this project but in general I would like to help with this. I would be a lousy maintainer, but if there are open issues in a fork I might take a look at it.

I've posted some stuff about the issues I currently have with my own fork over at #1311
I think anyone looking at creating a new fork of this would need to be quite dedicated to it. There are a lot of things to think about like, a new website, checking any licensing issues, setting up continuous integration, documentation, making sure there is good test coverage, making sure the tests are actually useful, making sure you don't accept any pull requests into master that would break anything, and continued development of the project.
I think it would be a good idea for anyone serious about making a new fork to create a Patreon page to support the core maintainers of the package, so that there is something to justify their time input other than "just being a cool project". The fork I made was my first real crack at making some fairly significant changes to an open source project, and it was a lot more work than I thought it would be.

@FurryFur This has been my main concern when I considered taking this over almost a year ago after @chrippa didn't respond even after I asked about donations to the project. It's a big project to take over, and I honestly don't know if the community that uses Livestreamer is even willing to donate to make the amount of work required to maintain it tenable. Even 10 hours a week is a LOT of hours, and for most software developers that's easily a couple grand a month to maintain.

I don't know about anyone else, but i'd donate to a good developer (or
team) to help get this thing back on track...   I'm trying to use it with
livestream.com and it wont play the stream for more then 10 seconds before
it stops...  I've heard of a way to fix it but I don't know how to put it
in place...
Hopefully someone can get this thing going again, or maybe @chrippa will
allow a few other people here to help him keeping it up and going...
Thanks guys and girls!  this whole discussion is giving me at least some
hope that this project isn't dead!
--James
James Hauge
James Virtual Tours LLC.
http://JamesVirtualTours.com
<EMAIL_ADDRESS>808-782-8461
On Thu, Aug 11, 2016 at 6:29 AM, Forrest<EMAIL_ADDRESS>wrote:

@FurryFur https://github.com/FurryFur This has been my main concern
when I considered taking this over almost a year ago after @chrippa
https://github.com/chrippa didn't respond even after I asked about
donations to the project. It's a big project to take over, and I honestly
don't know if the community that uses Livestreamer is even willing to
donate to make the amount of work required to maintain it tenable. Even 10
hours a week is a LOT of hours, and for most software developers that's
easily a couple grand a month to maintain.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/chrippa/livestreamer/issues/1427#issuecomment-239214718,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AT0oiF85NGF9uof-sxhfL565vnmb7zMFks5qe03PgaJpZM4JeurO
.

As a a side note, youtube-dl is another maintained free software project that does have much of the same functionality (though it's more focused on downloading as opposed to streaming.)

Hey @junior1544 -- there is an easy way to make livestream.com streams work -- just open the page that's streaming, and use CTRL+U (assuming you're in Google Chrome) then press CTRL+F (for "find") and search for .m3u8.  Take that full URL (including all of the code after it, up until the closing quotes) and that will be the stream URL for livestreamer.  Request it with the hlsvariant:// prefix and you're golden.

From: Junior1544<EMAIL_ADDRESS>Sent: Thursday, August 11, 2016 2:00:23 PM
To: chrippa/livestreamer
Cc: scottbernstein; Comment
Subject: Re: [chrippa/livestreamer] Has this been abandoned? (#1427)
I don't know about anyone else, but i'd donate to a good developer (or
team) to help get this thing back on track... I'm trying to use it with
livestream.com and it wont play the stream for more then 10 seconds before
it stops... I've heard of a way to fix it but I don't know how to put it
in place...
Hopefully someone can get this thing going again, or maybe @chrippa will
allow a few other people here to help him keeping it up and going...
Thanks guys and girls! this whole discussion is giving me at least some
hope that this project isn't dead!
--James
James Hauge
James Virtual Tours LLC.
http://JamesVirtualTours.com
<EMAIL_ADDRESS>808-782-8461
On Thu, Aug 11, 2016 at 6:29 AM, Forrest<EMAIL_ADDRESS>wrote:

@FurryFur https://github.com/FurryFur This has been my main concern
when I considered taking this over almost a year ago after @chrippa
https://github.com/chrippa didn't respond even after I asked about
donations to the project. It's a big project to take over, and I honestly
don't know if the community that uses Livestreamer is even willing to
donate to make the amount of work required to maintain it tenable. Even 10
hours a week is a LOT of hours, and for most software developers that's
easily a couple grand a month to maintain.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/chrippa/livestreamer/issues/1427#issuecomment-239214718,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AT0oiF85NGF9uof-sxhfL565vnmb7zMFks5qe03PgaJpZM4JeurO
.

You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/chrippa/livestreamer/issues/1427#issuecomment-239240481, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AESJ1gTnO098jHutCXJsv-ZAmURw_DW6ks5qe2M3gaJpZM4JeurO.

Thanks @scottbernstein !!  But, I just gave that a shot, and am getting a
forbidden error...
the live stream i'm trying to play can be viewed directly on this url:
http://livestream.com/accounts/18265544/events/5004281/player?width=560&height=315&autoPlay=true&mute=false
and the livestream command i tried is:
livestreamer hlsvariant://
api.new.livestream.com/accounts/18265544/events/5004281/broadcasts/132546519.m3u8?dw=100&hdnea=st=1470942579~exp=1470944379~acl=/i/18265544_5004281_lsihzu8nfbyy7wbdl7s_1@193775/*~hmac=e8cf72ad0c8097a5fc3ac9ca5d0cbfebd013edc02bdcf89fe34a628bc2dc92cc
270p_hls --player omxplayer
I also tried putting quotes around the whole url because it was giving me
an error about an invalid command --player without it, with the quotes it
gave me the forbidden command...
Thanks!
--James
James Hauge
James Virtual Tours LLC.
http://JamesVirtualTours.com
<EMAIL_ADDRESS>808-782-8461
On Thu, Aug 11, 2016 at 8:34 AM, scottbernstein<EMAIL_ADDRESS>wrote:

Hey @junior1544 -- there is an easy way to make livestream.com streams
work -- just open the page that's streaming, and use CTRL+U (assuming
you're in Google Chrome) then press CTRL+F (for "find") and search for
.m3u8. Take that full URL (including all of the code after it, up until the
closing quotes) and that will be the stream URL for livestreamer. Request
it with the hlsvariant:// prefix and you're golden.

From: Junior1544<EMAIL_ADDRESS>Sent: Thursday, August 11, 2016 2:00:23 PM
To: chrippa/livestreamer
Cc: scottbernstein; Comment
Subject: Re: [chrippa/livestreamer] Has this been abandoned? (#1427)
I don't know about anyone else, but i'd donate to a good developer (or
team) to help get this thing back on track... I'm trying to use it with
livestream.com and it wont play the stream for more then 10 seconds before
it stops... I've heard of a way to fix it but I don't know how to put it
in place...
Hopefully someone can get this thing going again, or maybe @chrippa will
allow a few other people here to help him keeping it up and going...
Thanks guys and girls! this whole discussion is giving me at least some
hope that this project isn't dead!
--James
James Hauge
James Virtual Tours LLC.
http://JamesVirtualTours.com
<EMAIL_ADDRESS>808-782-8461
On Thu, Aug 11, 2016 at 6:29 AM, Forrest<EMAIL_ADDRESS>wrote:

@FurryFur https://github.com/FurryFur This has been my main concern
when I considered taking this over almost a year ago after @chrippa
https://github.com/chrippa didn't respond even after I asked about
donations to the project. It's a big project to take over, and I honestly
don't know if the community that uses Livestreamer is even willing to
donate to make the amount of work required to maintain it tenable. Even
10
hours a week is a LOT of hours, and for most software developers that's
easily a couple grand a month to maintain.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/chrippa/livestreamer/issues/1427#
issuecomment-239214718>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AT0oiF85NGF9uof-
sxhfL565vnmb7zMFks5qe03PgaJpZM4JeurO>
.

You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://github.com/
chrippa/livestreamer/issues/1427#issuecomment-239240481>, or mute the
thread<https://github.com/notifications/unsubscribe-
auth/AESJ1gTnO098jHutCXJsv-ZAmURw_DW6ks5qe2M3gaJpZM4JeurO>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/chrippa/livestreamer/issues/1427#issuecomment-239250320,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AT0oiB96hZYFWv1tkeYdK74f_zViDwdbks5qe2ssgaJpZM4JeurO
.

@junior1544
That should work -- with 2 caveats:

You DO need quotes around the full stream (for MS Windows command line at least).

You must issue the command IMMEDIATELY after grabbing that m38 URL.  If you let more than a minute or 2 pass, you need to refresh the page and grab the new M3u8 URL there.

In fact, I just validated your video stream from the URL you used and it worked perfectly.
Most important thing is to refresh the page and grab the m3u8 link JUST before you issue the livestreamer command.

From: Junior1544<EMAIL_ADDRESS>Sent: Thursday, August 11, 2016 3:43:04 PM
To: chrippa/livestreamer
Cc: scottbernstein; Mention
Subject: Re: [chrippa/livestreamer] Has this been abandoned? (#1427)
Thanks @scottbernstein !! But, I just gave that a shot, and am getting a
forbidden error...
the live stream i'm trying to play can be viewed directly on this url:
http://livestream.com/accounts/18265544/events/5004281/player?width=560&height=315&autoPlay=true&mute=false
and the livestream command i tried is:
livestreamer hlsvariant://
api.new.livestream.com/accounts/18265544/events/5004281/broadcasts/132546519.m3u8?dw=100&hdnea=st=1470942579~exp=1470944379~acl=/i/18265544_5004281_lsihzu8nfbyy7wbdl7s_1@193775/*~hmac=e8cf72ad0c8097a5fc3ac9ca5d0cbfebd013edc02bdcf89fe34a628bc2dc92cc
270p_hls --player omxplayer
I also tried putting quotes around the whole url because it was giving me
an error about an invalid command --player without it, with the quotes it
gave me the forbidden command...
Thanks!
--James
James Hauge
James Virtual Tours LLC.
http://JamesVirtualTours.com
<EMAIL_ADDRESS>808-782-8461
On Thu, Aug 11, 2016 at 8:34 AM, scottbernstein<EMAIL_ADDRESS>wrote:

Hey @junior1544 -- there is an easy way to make livestream.com streams
work -- just open the page that's streaming, and use CTRL+U (assuming
you're in Google Chrome) then press CTRL+F (for "find") and search for
.m3u8. Take that full URL (including all of the code after it, up until the
closing quotes) and that will be the stream URL for livestreamer. Request
it with the hlsvariant:// prefix and you're golden.

From: Junior1544<EMAIL_ADDRESS>Sent: Thursday, August 11, 2016 2:00:23 PM
To: chrippa/livestreamer
Cc: scottbernstein; Comment
Subject: Re: [chrippa/livestreamer] Has this been abandoned? (#1427)
I don't know about anyone else, but i'd donate to a good developer (or
team) to help get this thing back on track... I'm trying to use it with
livestream.com and it wont play the stream for more then 10 seconds before
it stops... I've heard of a way to fix it but I don't know how to put it
in place...
Hopefully someone can get this thing going again, or maybe @chrippa will
allow a few other people here to help him keeping it up and going...
Thanks guys and girls! this whole discussion is giving me at least some
hope that this project isn't dead!
--James
James Hauge
James Virtual Tours LLC.
http://JamesVirtualTours.com
<EMAIL_ADDRESS>808-782-8461
On Thu, Aug 11, 2016 at 6:29 AM, Forrest<EMAIL_ADDRESS>wrote:

@FurryFur https://github.com/FurryFur This has been my main concern
when I considered taking this over almost a year ago after @chrippa
https://github.com/chrippa didn't respond even after I asked about
donations to the project. It's a big project to take over, and I honestly
don't know if the community that uses Livestreamer is even willing to
donate to make the amount of work required to maintain it tenable. Even
10
hours a week is a LOT of hours, and for most software developers that's
easily a couple grand a month to maintain.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/chrippa/livestreamer/issues/1427#
issuecomment-239214718>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AT0oiF85NGF9uof-
sxhfL565vnmb7zMFks5qe03PgaJpZM4JeurO>
.

You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://github.com/
chrippa/livestreamer/issues/1427#issuecomment-239240481>, or mute the
thread<https://github.com/notifications/unsubscribe-
auth/AESJ1gTnO098jHutCXJsv-ZAmURw_DW6ks5qe2M3gaJpZM4JeurO>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/chrippa/livestreamer/issues/1427#issuecomment-239250320,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AT0oiB96hZYFWv1tkeYdK74f_zViDwdbks5qe2ssgaJpZM4JeurO
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/chrippa/livestreamer/issues/1427#issuecomment-239269429, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AESJ1s7nDXrL13jP1LSOfBRxbnlaJyFJks5qe3tIgaJpZM4JeurO.

Thank you @scottbernstein
I think that there's a rather large issue here....
It's not for a windows computer.  it's for use with Linux, the Raspberry Pi...
And, I did it within a minute...   but, I also need something that'll work for longer than 1 minute, that's why I was hoping that this program was going to start being supported again...
I was told that there was a solution that works, but I don't know how to put it into place, it's a change to a few lines of the code...    it's listed at #1277
Thanks...

yes, I have also confirmed that pull request #1277 will work

From: Junior1544<EMAIL_ADDRESS>Sent: Thursday, August 11, 2016 3:55:05 PM
To: chrippa/livestreamer
Cc: scottbernstein; Mention
Subject: Re: [chrippa/livestreamer] Has this been abandoned? (#1427)
Thank you @scottbernsteinhttps://github.com/scottbernstein
I think that there's a rather large issue here....
It's not for a windows computer. it's for use with Linux, the Raspberry Pi...
And, I did it within a minute... but, I also need something that'll work for longer than 1 minute, that's why I was hoping that this program was going to start being supported again...
I was told that there was a solution that works, but I don't know how to put it into place, it's a change to a few lines of the code... it's listed at #1277https://github.com/chrippa/livestreamer/pull/1277
Thanks...

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/chrippa/livestreamer/issues/1427#issuecomment-239272635, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AESJ1ihBbtTqlo4KQjZdyrz5rMoFfx-dks5qe34ZgaJpZM4JeurO.

@scottbernstein thanks, the next question would then be, how do I put that in place?  I can't even find the files on my Raspberry Pi to make any changes to it...

Reading the comments above, it seems that no one has the time to properly maintain the overall project, but at the same time there's interest in contribute to it from several people.
Looking at the forks' map (https://github.com/chrippa/livestreamer/network), it seems several devs work regularly on their forks recently (ie @FurryFur @intact @steven7851 ); so maybe a workable strategy would be to integrate those forks as a loosely organized continuation effort? (and invite whoever is submitting PRs in this original project to do it in the continuation as well to add valuable community efforts?)
Just thinking aloud...

@WolfganP Yes, someone who's able & willing will have to step forward to do the honours of hosting the main project/repository though.

@WolfganP The main problem is whoever is the primary maintainer is going to have a lot of work to do no matter what. We're talking at least a full 40 hours just to get the project back into the barest of shape with merging and reviewing PRs. The work has built up over time unfortunately so now we're in this shitty spot.

How scary is the codebase on this thing?  Looked at a few files and the py3 compatibility looks a bit hackish.  I was going to use this as an example or fork/refactor in my crazy media stream/transcode suite...but now I'm not so sure. Don't know if I want to walk into 500 bug/issues and 50 pr's.  heh

Maybe, if anyone is able to get a hold of the current person who 'own's' this git, can get a few more people added as admin's to it and then spread out the work a bit?  I'd do it in a second if I knew what I was doing to begin with...

I think someone just needs to take the initiative, call their fork the new "master" and try to reach out to the ones we know maintaining their own forks, ask them to push to your repo, and get the word out. Hopefully we can avoid ego clashes about whose name is on the new master and just run with it.
The longer it stagnates the worse it's going to get.

I'm definitely willing to help out on some issues / bugs, but taking maintainership of the project is definitely out of question with my current occupation. I'll be following this thread for further updates, I hope something comes out of this. Im using livestreamer daily, and would be glad to be able to help this tool and give something back to it.

@cdrage

@lawli3t thanks for ping me here, going to cross-post me response from https://github.com/bastimeyer/livestreamer-twitch-gui/issues/289
i'm interesting in devoting some time to this. i have some knowledge of python, and maintenance, however, I'd only be able to devote a few hours a week to this, just enough to maintain it.
anyone want to come up with a decent name / alternative to "livestreamer"?
i propose perhaps "streamlink" as a decent name

@lawli3t @hubbcaps @Junior1544 @oyvindln @gravyboat @noodle- @scottbernstein @bastimeyer @FurryFur @luceatnobis @WolfganP @SpootDev @hubbcaps
So I've created https://github.com/streamlink/streamlink which is the initial fork of livestreamer.
Let's have this 100% open with access from ANYONE. Seriously. No more waiting for PR's to get merged or continual pinging of the original maintainer.
This is the power of Git and open source.
Feel free to submit PR's. I'll be busy for the rest of the day, but I should have a few hours this weekend to devote some time to this.
Feel free to ping me or email me (it's on my profile) and I'll add you, no matter who you are!

@cdrage Good stuff, add me to the org please.

@cdrage Feel free to add me too.

@cdrage Me too.

ok, dogpile on @cdrage hehehehehehe   Might as well throw my hat in too.

@cdrage I'll gladly help where I can.

Thanks all! I'm out today, but I'll have time tomorrow to add everyone and
organize the repo.

Some things that are broken and need immediate check-ins into this  build (from the most recent updates to the following plugins):
livestream.py
ustream.py
dailymotion.py
periscope.py
Scott

From: Charlie Drage<EMAIL_ADDRESS>Sent: Friday, September 16, 2016 4:34:46 PM
To: chrippa/livestreamer
Cc: scottbernstein; Mention
Subject: Re: [chrippa/livestreamer] Has this been abandoned? (#1427)
Thanks all! I'm out today, but I'll have time tomorrow to add everyone and
organize the repo.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/chrippa/livestreamer/issues/1427#issuecomment-247702681, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AESJ1l554Y5_G1-NxhExQTOTWInMwN3Nks5qqv1mgaJpZM4JeurO.

@cdrage
Thanks for stepping up here and initializing this, much appreciated! 👍
Using a github org and giving the right people write access to the repo is the correct decision, but don't forget that at least one needs to stay responsible for the project, even after months. I've seen other projects like this with multiple authorized contributors going inactive/stale, because noone felt responsible and cared for any open issues/PRs after a while.
Also, the amount of work that needs to be done in order to get this going must not be underestimated. Fixing bugs and merging PRs is just one thing. Packages need to be created for various distros/OSes and maybe also gh-pages set up for the docs and other instructions. Having a plan or a list where everyone can see what needs to be done should help with this.
Thanks a lot! 😃 🎉 👍 😄

@bastimeye brings up good points.  I have a Jenkins/Proxmox that could possibly be throw into the mix for build/vm, CI, etc.....we'll see.

@SpootDev I've started several issues over in the other repo to address these points. We should be able to push most of that stuff through Travis to ensure that it stays open and accessible to everyone.

Really, it's a bad idea to change the name of the project. Are you sure you can't simply maintain a new branch "proposed-updates" or something along the lines and merge all the pending patches over there?

@javiercantero the problem is that since this has been abandoned, we can't maintain / update the packages that are currently on CentOS / Debian / Ubuntu / etc. With a new name (as well as an org instead of a user) we have more control whether this project is abandoned again in the future, etc.

Everyone check your invites, I've added everyone to the org with admin access to http://github.com/streamlink/streamlink if you feel that you need to add another collaborator with push access, etc.
Keep in mind that the permissions (admin) is very lenient, I'd like us to be as open as possible. Luckily with the power of Git, if someone were to be toxic it's a quick git reset --hard<PHONE_NUMBER> && git push -f.

@cdrage You don't have to maintain the packages, the distro package maintainers will do it. Believe me, it's going to be more difficult to add a new package to Debian in time for the next stable release (the freeze is in 3 months and the package should be accept and ready before that) that to convince the current livestreamer Debian maintainter to add some patches downstream (this applies not only to Debian but also to any derivative including Ubuntu since the Debian package is the basis for the rest).

While others are busy talking about doing things and therefore not actually doing anything, I went through all the pull requests and merged most of them into the master branch of my repo branch of my repo. Included are:

#1203 Dplay + removal of defunct plugin (UNTESTED, all streams seem to be geo restricted)
#1234 New plugin for bilibili.com
#1240 Support afreecatv.jp domain (Appears to not work... and why there are two separate plugins for afreeca?)
#1241 New plugin for panda.tv
#1243 New plugin for sportschau.de (UNTESTED, no live streams available, does not work for non-livestream videos on the site)
#1251 Support twitch host mode
#1252 itv.com fixes (UNTESTED, all streams seem to be geo restricted)
#1253 New plugin for mediaklikk.hu
#1257 New plugin for tvthek.orf.at
#1277 livestream.com fix
#1289 tga plugin fix/update
#1291 Fix for youtube
#1329 New plugin for rtl.nl
#1332 Fix for picarto.tv
#1333 New plugin for openrec.tv
#1352 Fix for tv.nrk.no
#1359 Update twitch oauth redirect URL
#1375 Fix for svtplay
#1376 Fix for vaughnlive
#1378 New plugin for vidio.com
#1383 Fix for afreecatv
#1397 Fix for twitch
#1401 Another fix for afreecatv
#1414 Fix for douyu.com
#1429 Fix some twitch stream names
#1439 Documentation fix
#1450 Fix livecoding.tv vods
#1461 Fix for goodgame.ru
#1469 Another fix for picarto.tv
#1476 New plugin for viafree.dk
#1483 twitch client ID patch

and these didn't get in:

#233  Abandoned back in 2013, don't know why
#1024 I'm not sure what this is good for...
#1105 Python 3.6 fix, we'll think about it once python 3.6 is released.
#1160 goodgame.ru fix superseded by #1461
#1167 VLC specific, can't test without VLC, and it probably breaks other players that don't support --meta-title argument.
#1197, #1227, #1278 ustream.tv fixes conflict with each other. Some comments say that the whole plugin should be rewritten. Need someone who actually knows this stuff to sort it out.
#1200 Documentation change, I'm not sure if this belongs here...
#1204, #1210, #1298, #1311 I didn't want to add any big new features to this. Let's fix all broken things first.
#1206, #1214, #1274, #1302 streamup.com, castamp.com, immono.com, and periscope.tv. These seem to require some sort of mobile app to use (no stream list on the websites), meaning that I don't have any means of testing them. Personally, I think that nothing of value is lost if this hipster stuff is left out. If someone else feels otherwise, go ahead and include them.
#1238 Looks like some sort of configuration error on reporter's computer...
#1242, #1364 douyu fixes superseded by #1414
#1267 BS on wheels? For me, the Right Way™ to release software is a source tarball. Someone who actually uses the binary nonsense should handle this one.
#1269 According to comments, this fix has problems and the videos are geo restricted, so I cannot test.
#1280 Another bilibili.com plugin, duplicate of #1234
#1386 Documentation change that may not be true anymore. Should wait until the new upstream is well established.

Now I'm trying to find out how to upload a release tarball here, so that all the Technologically Impaired Ducks using the program can get a working version without needing to deal with git...
Also, hasn't anyone noticed that the streamlink repository is cloned from master rather than develop branch and therefore is missing all commits between 1.12.2 release and the last merge at March of this year?

Really, it's a bad idea to change the name of the project. Are you sure you can't simply maintain a new branch "proposed-updates" or something along the lines and merge all the pending patches over there?

I disagree, when the community agrees that changes need to happen I think the best way is to completely fork it and start a new project, but honor the legacy from which it came. LibreOffice is a good example in my mind.

@sondr3 That only applies when a community splits in two different ways. That's not what is happening here.

A tarball + Windows installation instructions are now available here. Again, it's meant to be a temporary solution until the streamlink folks have a better release available.

@LoneFox78 Don't bother with any PR < 1192 (the last one merged by chrippa)

Hey @LoneFox78 thank you so much for all the work you've done for your fork / branch.
IMO, we should still fork / split as unfortunately we can't get anything merged into livestreamer as @chrippa has abandoned it.
A good start would be to merge your branch / fork into streamlink.
I've created the PR https://github.com/streamlink/streamlink/pull/9 so we can have a great starting point / code-base for everything.

I'm just a bystander, but my two cents: While it would be ideal to receive stewardship of the project from @chrippa, in the absence of that, forking and renamin g is the only viable path forward.  If this, the canonical repo for livestreamer, is to remain stuck, there must be a new name for the fork to distinguish it.

#1495 is my own selection of urgent fixes. It's based on the list provided by @LoneFox78 above but shorter since it doesn't include new code, new features or new plugins, only fixes for existing plugings.
My goal is to try to convince the Debian maintainers to include the patch in the livestreamer package for the next release of Debian (9.0) before it is too late. This also should affect any derivative of Debian (including Ubuntu and its derivatives).
Any testing of the patched plugins is greatly appreciated.

@javiercantero How long do we have for the Debian release? We've got a working release of streamlink that we might be able to push if we can package it up.

@gravyboat The hard deadline for the "freeze" of Debian Stretch is January 5, 2017 but I recommend you to start ASAP (since I don't know if the inclusion of new packages is welcome so close to the freeze date).

The joy of slow moving projects, 3 months to go is 'close' to the freeze date.

@javiercantero Thanks for your effort to get the patches into Debian.  As a Debian user, I appreciate it!

@gravyboat The whole process is (at least) two years, so 3 months is really close :)

I am the author of the twitchlive extension for gnome shell (https://github.com/maweki/twitchlive-extension) and for now I will be pointing people to streamlink

@LoneFox78
I noticed this project was abandoned for a while now. But I come back to see how was my pr #1204 going. I've been using it ever since I coded. I disagree it's a big change, as you've put it. I changed very few lines. And this option is great for streaming and recording at the same time. Best of both worlds. Nice to see things moving, though.

@grazzolini That looks like a very nice addition!  I agree that it seems like few lines for adding such a feature.  Well done.

@giancarlo -- please issue the same pull request to the Streamlink project which has taken over development of livestreamer as an active project:
https://github.com/streamlink/streamlink
[https://avatars0.githubusercontent.com/u/22243823?v=3&s=400]https://github.com/streamlink/streamlink
GitHub - streamlink/streamlink: CLI for extracting streams ...https://github.com/streamlink/streamlink
github.com
streamlink - CLI for extracting streams from various websites to video player of your choosing [fork of livestreamer]
It started off with the same code base and has only recently started making some changes

From: Giancarlo Razzolini<EMAIL_ADDRESS>Sent: Wednesday, October 26, 2016 9:14:05 AM
To: chrippa/livestreamer
Cc: scottbernstein; Mention
Subject: Re: [chrippa/livestreamer] Has this been abandoned? (#1427)
@LoneFox78https://github.com/LoneFox78
I noticed this project was abandoned for a while now. But I come back to see how was my pr #1204https://github.com/chrippa/livestreamer/pull/1204 going. I've been using it ever since I coded. I disagree it's a big change, as you've put it. I changed very few lines. And this option is great for streaming and recording at the same time. Best of both worlds. Nice to see things moving, though.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/chrippa/livestreamer/issues/1427#issuecomment-256343124, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AESJ1u_rE6h35i7oGTAR5IGWaNdKnS7aks5q31IdgaJpZM4JeurO.

I tested streamlink and it's just the most user unfriendly BS ever (for Windows).  Then there is no config file to find like it was in livestreamer, to define which player should be used, VLC ect. Then how to use it ? Just replaced livestreamer.exe with the streamlink.exe doesn't work ... it seems not to support the same commands. This is unbelievable.

@makedir Perhaps you should make a new issue in the Streamlink repo with your issue with a coherent statement of your problems rather than necro posting in this thread on an abandoned project. You'll be much more likely to get help over there.

Yes, Please raise an issue over at Streamlink
Livestreamer was forked several months ago and has understandably changed a bit to meet changes in API's and to meet the needs of those using it. But let's discuss your concerns over at Streamlink. :)

For me (on Windows), Streamlink has been exactly a drop in replacement.  Sorry it doesn't work for you....
On Apr 7, 2017, at 11:31 AM, fishscene <notifications<EMAIL_ADDRESS>wrote:
Yes, Please raise an issue over at Streamlinkhttps://github.com/streamlink/streamlink/issues
Livestreamer was forked several months ago and has understandably changed a bit to meet changes in API's and to meet the needs of those using it. But let's discuss your concerns over at Streamlink. :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/chrippa/livestreamer/issues/1427#issuecomment-292569209, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AESJ1rPa2sH6zCKdCF1rWvgThq9ekYvNks5rtla9gaJpZM4JeurO.

@LoneFox78 Castamp is not mobile only, it just does not have public streams. Also, it's not untestable, I even have an example of testing it here: https://github.com/rbong/livestreamer-nightly/tree/castamp
However it has been several years since I used this software so I will likely not be porting it over to your fork, so if someone wants castamp support unfortunately they will have to add it themselves.


fix: RPCs spending 2*timeout before throwing DEADLINE_EXCEEDED.

Moving the call to exponentialRetryAlgorithm.createFirstAttempt before the first RPC is sent. This allows the ExponentialRetryAlgorithm to capture the correct time of first call which is later used to evaluate if deadline has expired.
Fixes #2567

@googlebot


Remove build warnings from Console

Type of change

Refactoring

Description

Remove unwanted variables.
Refactor plan dropdowns and error Loops
Upgrade React Popper version to 1.3.7
Fix type mismatches
Fix Test Case Fails
Remove Test Warnings

@enmasse-ci run tests testcase=FirefoxConsoleTest

This doesn't look right to me.  For a clean build, I see lots of the following and some test failures.
console-init_build_out.txt
FAIL src/modules/address-space/containers/AddressSpaceListContainer/AddressSpaceListContainer.test.tsx (7.835s)
[INFO]   ● Console
[INFO]
[INFO]     console.error node_modules/react-dom/cjs/react-dom.development.js:88
[INFO]       Warning: An update to AddressSpaceListContainer inside a test was not wrapped in act(...).
[INFO]
[INFO]       When testing, code that causes React state updates should be wrapped into act(...):
[INFO]
[INFO]       act(() => {
[INFO]         /* fire events that update state /
[INFO]       });
[INFO]       / assert on the output */

:heavy_check_mark: Test Summary :heavy_check_mark:
TEST_PROFILE: pr
TEST_CASE: FirefoxConsoleTest
TOTAL: 94
PASS: 87
FAIL: 0
SKIP: 7
BUILD_NUMBER: 893
BUILD_ENV: oc cluster up

This doesn't look right to me. For a clean build, I see now lots of the following and some test failures.
console-init_build_out.txt
FAIL src/modules/address-space/containers/AddressSpaceListContainer/AddressSpaceListContainer.test.tsx (7.835s)
[INFO] ● Console
[INFO]
[INFO] console.error node_modules/react-dom/cjs/react-dom.development.js:88
[INFO] Warning: An update to AddressSpaceListContainer inside a test was not wrapped in act(...).
[INFO]
[INFO] When testing, code that causes React state updates should be wrapped into act(...):
[INFO]
[INFO] act(() => {
[INFO] /* fire events that update state / [INFO] }); [INFO] / assert on the output */

These fails and test warnings are not because of the changes in this PR. I think it has resulted from a month old PR in the UI test cases. I will create a new JIRA issue to track this issue and fix this.

@enmasse-ci run tests testcase=FirefoxConsoleTest

:heavy_check_mark: Test Summary :heavy_check_mark:
TEST_PROFILE: pr
TEST_CASE: FirefoxConsoleTest
TOTAL: 95
PASS: 88
FAIL: 0
SKIP: 7
BUILD_NUMBER: 925
BUILD_ENV: oc cluster up

@k-wall The test cases and warnings are fixed, I had to comment out one test case in AddressSpaceListContainer because the test case needed some refactoring to fix the warning and the it's bound to change entirely in the 2.0 release. So, it seemed more logical at this point to skip it.

@anukritijha the test failures are gone.   However, I still see a whole series of build warnings. What is causing these?
 make -C console/console-init/

[INFO] warning<EMAIL_ADDRESS>Invalid bin entry for "sha.js" (in "sha.js").
[INFO] [3/4] Linking dependencies...
[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning "@apollo/react-hooks ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning "@apollo/react-hooks ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning "@rescripts/cli ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency "webpack@>=2".
[INFO] warning "@storybook/react ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INFO] warning "@storybook/react ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INFO] warning "@storybook/react > @storybook/core ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INFO] warning "@storybook/react > @storybook/core ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INFO] warning "@storybook/addon-docs ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INFO] warning "@storybook/addon-actions ><EMAIL_ADDRESS>has unmet peer dependency "regenerator-runtime@".
[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning "@storybook/addon-docs ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning "@storybook/addon-docs ><EMAIL_ADDRESS>has unmet peer dependency "webpack@>=4".
[INFO] warning "@storybook/react ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INFO] warning "@storybook/react ><EMAIL_ADDRESS>has unmet peer dependency "@babel/core@".
[INFO] [4/4] Building fresh packages...
[INFO] info This package requires node-gyp, which is not currently installed. Yarn will attempt to automatically install it. If this fails, you can run "yarn global add node-gyp" to manually install it.
[INFO] [1/4] Resolving packages...
[INFO] warning Error running install script for optional dependency: "/Users/keith/go/src/github.com/enmasseproject/enmasse/console/console-init/ui/node_modules/fsevents: Failed to auto-install node-gyp. Please run "yarn global add node-gyp" manually. Error: "Couldn't find any versions for \"node-gyp\" that matches \"latest\" in our cache (possible versions are \"\"). This is usually caused by a missing entry in the lockfile, running Yarn without the --offline flag may help fix this issue.""
[INFO] warning Error running install script for optional dependency: "/Users/keith/go/src/github.com/enmasseproject/enmasse/console/console-init/ui/node_modules/fsevents: Failed to auto-install node-gyp. Please run "yarn global add node-gyp" manually. Error: "Couldn't find any versions for \"node-gyp\" that matches \"latest\" in our cache (possible versions are \"\"). This is usually caused by a missing entry in the lockfile, running Yarn without the --offline flag may help fix this issue.""info This module is OPTIONAL, you can safely ignore this error
[INFO] Done in 108.66s.

@anukritijha the test failures are gone, thanks. However, I still see a whole series of build warnings. What is causing these?
 make -C console/console-init/

[INFO] warning<EMAIL_ADDRESS>Invalid bin entry for "sha.js" (in "sha.js").
[INFO] [3/4] Linking dependencies...
[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning "@apollo/react-hooks ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning "@apollo/react-hooks ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning "@rescripts/cli ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency "webpack@>=2".
[INFO] warning "@storybook/react ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INFO] warning "@storybook/react ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INFO] warning "@storybook/react > @storybook/core ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INFO] warning "@storybook/react > @storybook/core ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INFO] warning "@storybook/addon-docs ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INFO] warning "@storybook/addon-actions ><EMAIL_ADDRESS>has unmet peer dependency "regenerator-runtime@*".
[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning "@storybook/addon-docs ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[INFO] warning "@storybook/addon-docs ><EMAIL_ADDRESS>has unmet peer dependency "webpack@>=4".
[INFO] warning "@storybook/react ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INFO] warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[INFO] warning "@storybook/react ><EMAIL_ADDRESS>has unmet peer dependency "@babel/core@*".
[INFO] [4/4] Building fresh packages...
[INFO] info This package requires node-gyp, which is not currently installed. Yarn will attempt to automatically install it. If this fails, you can run "yarn global add node-gyp" to manually install it.
[INFO] [1/4] Resolving packages...
[INFO] warning Error running install script for optional dependency: "/Users/keith/go/src/github.com/enmasseproject/enmasse/console/console-init/ui/node_modules/fsevents: Failed to auto-install node-gyp. Please run \"yarn global add node-gyp\" manually. Error: \"Couldn't find any versions for \\\"node-gyp\\\" that matches \\\"latest\\\" in our cache (possible versions are \\\"\\\"). This is usually caused by a missing entry in the lockfile, running Yarn without the --offline flag may help fix this issue.\""
[INFO] warning Error running install script for optional dependency: "/Users/keith/go/src/github.com/enmasseproject/enmasse/console/console-init/ui/node_modules/fsevents: Failed to auto-install node-gyp. Please run \"yarn global add node-gyp\" manually. Error: \"Couldn't find any versions for \\\"node-gyp\\\" that matches \\\"latest\\\" in our cache (possible versions are \\\"\\\"). This is usually caused by a missing entry in the lockfile, running Yarn without the --offline flag may help fix this issue.\""info This module is OPTIONAL, you can safely ignore this error
[INFO] Done in 108.66s.

@k-wall The peer dependency warnings happen because the libraries that we use in our app like apollo, patternfly, storybook etc have other dependencies which are not included in our package.json. As these dependencies are a part of node modules, so our application works as expected. But Yarn is being safe here and warning us about these dependencies. A simple solution would just be to add these dependencies in package.json. I have tried to do this in the past, the warnings were gone, however the application fell into another set of issues with Babel which is dependent on a different version. Hence I chose to ignore these warnings. Wdyt?

@enmasse-ci run tests testcase=FirefoxConsoleTest

:x: Test Summary :x:
TEST_PROFILE: pr
TEST_CASE: FirefoxConsoleTest
TOTAL: 95
PASS: 87
FAIL: 1
SKIP: 7
BUILD_NUMBER: 951
BUILD_ENV: oc cluster up
:heavy_exclamation_mark: Test Failures :heavy_exclamation_mark:

testEditAddressSpace in io.enmasse.systemtest.isolated.web.FirefoxConsoleTest

@enmasse-ci run tests testcase=FirefoxConsoleTest

make -C console/console-init/

:heavy_check_mark: Test Summary :heavy_check_mark:
TEST_PROFILE: pr
TEST_CASE: FirefoxConsoleTest
TOTAL: 95
PASS: 88
FAIL: 0
SKIP: 7
BUILD_NUMBER: 954
BUILD_ENV: oc cluster up

@enmasse-ci run tests testcase=FirefoxConsoleTest.testViewAddressSpacesAsBasicUser

:heavy_check_mark: Test Summary :heavy_check_mark:
TEST_PROFILE: pr
TEST_CASE: FirefoxConsoleTest.testViewAddressSpacesAsBasicUser
TOTAL: 22
PASS: 22
FAIL: 0
SKIP: 0
BUILD_NUMBER: 967
BUILD_ENV: oc cluster up

@anukritijha you wrongly triggered test, if you want to specify one test from test class you nee to use # as separator between test class and test

@enmasse-ci run tests testcase=FirefoxConsoleTest#testViewAddressSpacesAsBasicUser

@anukritijha you wrongly triggered test, if you want to specify one test from test class you nee to use # as separator between test class and test

Gotcha, thanks for helping out.

:heavy_check_mark: Test Summary :heavy_check_mark:
TEST_PROFILE: pr
TEST_CASE: FirefoxConsoleTest#testViewAddressSpacesAsBasicUser
TOTAL: 23
PASS: 23
FAIL: 0
SKIP: 0
BUILD_NUMBER: 968
BUILD_ENV: oc cluster up


How to use ModelExchange's model

Hi Tuebel,
Now, I can use Co-Simulation's Model in my C# App by your wrapper.
And I want to use ModelExchange's Model, Does this wrapper support ModelExchange's model ?
Thanks.

Hi,
it has been a while when I implemented this, but I think the ModelExchange types are available. However, you will need to provide your own solver / integrator.

嗨，当我实现这个时已经有一段时间了，但我认为模型交换类型是可用的。但是，您需要提供自己的求解器/积分器。

Ok. I'll try that


[Bug]: the error.log database.log ... are not fellow the formater: "[%(levelname)s] [%(asctime)s] [%(module)s.%(funcName)s] [line:%(lineno)d]: %(message)s"

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Branch name
main
Commit ID
1eb4caf02a9fdb1f3c5a7e8f304163d8823bfa5c
Other environment information
No response
Actual behavior
LookupError: Model(text-embedding-v2) not authorized
Expected behavior
[ERROR] [2024-06-11 09:09:13,408] [xxx.xxx] [line:xxx]: LookupError: Model(text-embedding-v2) not authorized
Steps to reproduce
see log files of logs/api

Additional information
No response

text-embedding-v2 is autherized by Aliyun. Set API key in settings >> model providers.
Or, use embedding model from BAAI.

Actual behavior
LookupError: Model(text-embedding-v2) not authorized
Expected behavior
[ERROR] [2024-06-11 09:09:13,408] [xxx.xxx] [line:xxx]: LookupError: Model(text-embedding-v2) not authorized

i do not care the exception


Update code blocks to always specify syntax, fix ordered list

General cleanup to finish up the last bit of formatting on https://github.com/attic-labs/decent-website/issues/13

Intentionally outdented the code there because it seems like showdownjs doesn't support indented code blocks - I could preprocess the blocks (I currently do that but I don't like it), but my preference is to just use formatting it can handle. What do you think?

Sgtm
On Sep 22, 2017 10:47 AM, "Jesse Ditson"<EMAIL_ADDRESS>wrote:

Intentionally outdented the code there because it seems like showdownjs
doesn't support indented code blocks - I could preprocess the blocks (I
currently do that but I don't like it), but my preference is to just use
formatting it can handle. What do you think?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/attic-labs/noms/pull/3734#issuecomment-331556526, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAJl4bZlgt22By6g3lrx5LT155g3xT2gks5slBzEgaJpZM4PgGT3
.

That is, outdenting is fine.
On Sep 22, 2017 11:43 AM<EMAIL_ADDRESS>wrote:

Sgtm
On Sep 22, 2017 10:47 AM, "Jesse Ditson"<EMAIL_ADDRESS>wrote:

Intentionally outdented the code there because it seems like showdownjs
doesn't support indented code blocks - I could preprocess the blocks (I
currently do that but I don't like it), but my preference is to just use
formatting it can handle. What do you think?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/attic-labs/noms/pull/3734#issuecomment-331556526,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJl4bZlgt22By6g3lrx5LT155g3xT2gks5slBzEgaJpZM4PgGT3
.


[iOS] The marker label does not work when update the state

When you display markers with title and description and you update the state the old markers dosn't have the title and description again.
For fix it I remove the old markers and update the state with all markers but the re-render its anti ux.

Let me know if you experience this on latest version (0.19.0) Might be related to #483


ARROW-10158: [C++][Parquet] Expose page index info from ColumnChunkMetaData

This is the first step to support page index of parquet.

@pitrou @emkornfield Can you please take a look? As I have mentioned in other thread, I will work on the page index and break it down into small commits to make it review-friendly.

I have addressed your comment, and the unsuccessful CI checks are unrelated to my change. Can you please take a look again? @emkornfield

Test failures are unrelated, will merge.


cloning repository with --single-branch blocks checkouts on specific tag/revision

reproducible examples:
gb vendor fetch -tag v1.5.0 github.com/docker/docker
gb vendor fetch -revision a8a31eff10544860d2188dddabdee4d727545796 github.com/docker/docker

fails with:
error: pathspec 'v1.5.0' did not match any file(s) known to git.
FATAL command "fetch" failed: exit status 1
FATAL command "vendor" failed: exit status 1

fatal: reference is not a tree: a8a31eff10544860d2188dddabdee4d727545796
FATAL command "fetch" failed: exit status 128
FATAL command "vendor" failed: exit status 1

For fetching tags this might be fixed by adding a --branch <tag> to the actual clone command but setting via revision would still fail in that example.
I personally would favour to drop the --single-branch flag or give fetch a flag to enable it explicitly or even a --depth that can be set for the fetch.

@davidkaya would you have time to look at this one?

On Thursday, I got bachelor finals on Wednesday.

Got it. Thanks. Good luck with your examinations.
On Tue, 16 Jun 2015 08:34 Dávid Kaya<EMAIL_ADDRESS>wrote:

On Thursday, I got bachelor finals on Wednesday.
—
Reply to this email directly or view it on GitHub
https://github.com/constabulary/gb/issues/219#issuecomment-112229515.

@MerlinDMC if you wanted to send a PR that removes --single-branch, that'd be ok by me, I'm not convinced it's paying for itself.


docker doc fixes

Coverage remained the same at 80.108% when pulling 91b8c6166b62b340ef1cfc12bbf45e5fd0d6c9d3 on akmorrow13:master into 6665c0cec7694d8d7351ae9bae67a451e2998f36 on bigdatagenomics:master.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/mango-prb/869/
Test PASSed.


No module named misc.config

sorry to bother you but I could not find the module misc.config when trying demo.py
how can I solve this ?

I have the same problem.Have you solved it?

@wewan Hi Wei - how did you solve this?


Animate Header Logos when switching

https://user-images.githubusercontent.com/16027268/211107001-748f516b-77ca-4a11-a4d6-d314ab5db454.mp4

Looks like the logo is slightly "overshooting", not a big fan of that, but 🤷♀

Looks like the logo is slightly "overshooting", not a big fan of that, but 🤷♀

Are you referring to this overlap?
If yeah then same, I'll fix!


Fix RTD builds

Right now, it fails due to setuptools being outdated, and thus the API docs page is incomplete.

Worked around by 8a27aa10b1a8469eb44e46f6676c8acd0b3985d3


Conflicts  | Allow users to manage conflicts

I encourage you to take a look at Atom's Github plugin's UI for this, which is excellent.
In addition, even after years of using similar tools, I'm consistently confused by terminology like "resolve as ours" vs "resolve as theirs". Would it make sense to label conflict blocks based on their associated commit messages, perhaps with an optional floating window that would provide more information?


Dashboard Widget

This isn't an issue, but how could I have these show on a dashboard?

What exactly would you like to show on a dashboard?

I set up a news crawl that a client updates regularly. I'd like to set this up so the client just logs in and it's on the dashboard.

Why not simply create a regular custom dashboard widget?

You could use Quickstart Buttons to add a button on the dashboard that points to the configuration CMP.


De-minify desktop.min.js

This file is minified:
https://github.com/m-lab/m-lab.github.io/blob/master/js/desktop.min.js
It's unclear if we have the un-minified source anywhere, but minified JS should not be in source control. We should de-minifiy this using a JS formatter that can apply the formatting rules of the Google JS style guide.

I'm not able to close issues, so leaving a comment that I think PR #109 addressed this issue and I think it can be closed?


Don't package extra files

These extra files should be excluded from the gem when packaging as they cannot be used and take extra space unnecessary.

@Faq What are they needed for in a packaged gem?