Grafana has failed to load its application files during LOGIN

After running "docker-compose up" and start to open http://IP:3000, Grafana does not load.
Error message, after waiting a while:

If you're seeing this Grafana has failed to load its application files

This could be caused by your reverse proxy settings.

If you host grafana under subpath make sure your grafana.ini root_path setting includes subpath

If you have a local dev build make sure you build frontend using: npm run dev, npm run watch, or npm run build

Sometimes restarting grafana-server can help

Can you paste the output of your Grafana logs docker log grafana please?
Are you hosting this behind a reverse proxy or bare defaults?
Have you tried restarting Grafana?

The same Grafana error is happening with : stefanprodan/swarmprom

This looks to be an issue with https://labs.play-with-docker.com and how it reverse proxies to the backend Grafana service.
I haven't really had too much of a chance to look deeper in to this, but it might be the case that it's not something that we will even be able to fix. This definitely works when deploying on cloud services like AWS, Azure, GCP and of course your own PC/Server.

I'm not entirely sure if there's some sort of rate-limiting or something on their reverse proxy.
Unfortunately this isn't a dockprom or Grafana issue specifically. I suggest you lodge an upstream ticket for play-with-docker.

@nightah play-with-docker author here. PWD is using a custom reverse proxy indeed to forward traffic to the underlying container given the supplied URL. What I don't understand is why grafana needs some special configuration to work behind reverse proxies. I've checked the documentation but besides setting the server domain url config parameter I don't see anything else that we can configure.
Can you help me understand what's grafana doing behind the scenes that affects this?. I don't see any errors neither in the browser nor the application logs.

@marcosnils what reverse proxy are you using for play-with-docker?
I've tried playing with Grafana and setting the server domain too but it doesn't resolve the issue.

@nightah it's fixed already. One of our firewall rules was preventing grafana assets to download propertly.

Hi,
I have the same result when login after installing https://dl.grafana.com/oss/release/grafana-5.4.2-1.x86_64.rpm on CentOS7 on AWS.
Would this log line be an indication of a problem:
t=2019-03-20T18:30:47+0000 lvl=eror msg="Can't read alert notification provisioning files from directory" logger=provisioning.notifiers path=/etc/grafana/provisioning/notifiers error="open /etc/grafana/provisioning/notifiers: no such file or directory"
Logs:
t=2019-03-20T18:30:47+0000 lvl=info msg="Starting Grafana" logger=server version=6.0.2 commit=3f4c2e7 branch=HEAD compiled=2019-03-19T13:06:06+0000
t=2019-03-20T18:30:47+0000 lvl=info msg="Config loaded from" logger=settings file=/usr/share/grafana/conf/defaults.ini
t=2019-03-20T18:30:47+0000 lvl=info msg="Config loaded from" logger=settings file=/etc/grafana/grafana.ini
t=2019-03-20T18:30:47+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.data=/var/lib/grafana"
t=2019-03-20T18:30:47+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.logs=/var/log/grafana"
t=2019-03-20T18:30:47+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.plugins=/var/lib/grafana/plugins"
t=2019-03-20T18:30:47+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.provisioning=/etc/grafana/provisioning"
t=2019-03-20T18:30:47+0000 lvl=info msg="Path Home" logger=settings path=/usr/share/grafana
t=2019-03-20T18:30:47+0000 lvl=info msg="Path Data" logger=settings path=/var/lib/grafana
t=2019-03-20T18:30:47+0000 lvl=info msg="Path Logs" logger=settings path=/var/log/grafana
t=2019-03-20T18:30:47+0000 lvl=info msg="Path Plugins" logger=settings path=/var/lib/grafana/plugins
t=2019-03-20T18:30:47+0000 lvl=info msg="Path Provisioning" logger=settings path=/etc/grafana/provisioning
t=2019-03-20T18:30:47+0000 lvl=info msg="App mode production" logger=settings
t=2019-03-20T18:30:47+0000 lvl=info msg="Writing PID file" logger=server path=/var/run/grafana/grafana-server.pid pid=11983
t=2019-03-20T18:30:47+0000 lvl=info msg="Initializing HTTPServer" logger=server
t=2019-03-20T18:30:47+0000 lvl=info msg="Initializing SqlStore" logger=server
t=2019-03-20T18:30:47+0000 lvl=info msg="Connecting to DB" logger=sqlstore dbtype=sqlite3
t=2019-03-20T18:30:47+0000 lvl=info msg="Starting DB migration" logger=migrator
t=2019-03-20T18:30:47+0000 lvl=info msg="Initializing InternalMetricsService" logger=server
t=2019-03-20T18:30:47+0000 lvl=info msg="Initializing SearchService" logger=server
t=2019-03-20T18:30:47+0000 lvl=info msg="Initializing PluginManager" logger=server
t=2019-03-20T18:30:47+0000 lvl=info msg="Starting plugin search" logger=plugins
t=2019-03-20T18:30:47+0000 lvl=info msg="Initializing RenderingService" logger=server
t=2019-03-20T18:30:47+0000 lvl=info msg="Initializing AlertingService" logger=server
t=2019-03-20T18:30:47+0000 lvl=info msg="Initializing DatasourceCacheService" logger=server
t=2019-03-20T18:30:47+0000 lvl=info msg="Initializing HooksService" logger=server
t=2019-03-20T18:30:47+0000 lvl=info msg="Initializing LoginService" logger=server
t=2019-03-20T18:30:47+0000 lvl=info msg="Initializing QuotaService" logger=server
t=2019-03-20T18:30:47+0000 lvl=info msg="Initializing ServerLockService" logger=server
t=2019-03-20T18:30:47+0000 lvl=info msg="Initializing UsageStatsService" logger=server
t=2019-03-20T18:30:47+0000 lvl=info msg="Initializing UserAuthTokenService" logger=server
t=2019-03-20T18:30:47+0000 lvl=info msg="Initializing CleanUpService" logger=server
t=2019-03-20T18:30:47+0000 lvl=info msg="Initializing NotificationService" logger=server
t=2019-03-20T18:30:47+0000 lvl=info msg="Initializing ProvisioningService" logger=server
t=2019-03-20T18:30:47+0000 lvl=eror msg="Can't read alert notification provisioning files from directory" logger=provisioning.notifiers path=/etc/grafana/provisioning/notifiers error="open /etc/grafana/provisioning/notifiers: no such file or directory"
t=2019-03-20T18:30:47+0000 lvl=info msg="Initializing TracingService" logger=server
t=2019-03-20T18:30:47+0000 lvl=info msg="Initializing Stream Manager"
t=2019-03-20T18:30:47+0000 lvl=info msg="HTTP Server Listen" logger=http.server address=<IP_ADDRESS>:3000 protocol=http subUrl= socket=

I just download grafana-7.3.5.linux-amd64.tar.gz，then
tar xf grafana-7.3.5.linux-amd64.tar.gz
cd grafana-7.3.5
./bin/grafana-server web
then vist http://ip:3000/ ，I see the same error message.I didn't modify the config file ,nor use any reserve proxy either


AQL: GeoJSON returning as a string

My Environment

ArangoDB Version:        3.4.0 RC4
Storage Engine:             RocksDB
Deployment Mode:       Single Server
Deployment Strategy:   ArangoDB Starter
Configuration:
Infrastructure:               own
Operating System:        Windows 7
Used Package:

Component, Query & Data
Affected feature: Geo queries and/or documentation
AQL query (if applicable):
Let geoPoint1 = {"coordinates":[-122.084,37.421997], "type":"Point" }
FOR geo IN Geo
    Let geoPoint2 = geo.location
    Let geoDistance = GEO_DISTANCE(geoPoint1, geoPoint2)
    FILTER geoDistance != null && geoDistance  <= 30000
    RETURN { "distance" : geoDistance, "location": geo.location}

AQL explain (if applicable):
Query String:
Let geoPoint1 = {"coordinates":[-122.084,37.421997], "type":"Point" }
FOR geo IN Geo
Let geoPoint2 = geo.location
Let geoDistance = GEO_DISTANCE(geoPoint1, geoPoint2)
FILTER geoDistance != null && geoDistance  <= 30000
RETURN { "distance" : geoDistance, "location": geo.location}
Execution plan:
Id   NodeType          Est.   Comment
1   SingletonNode        1   * ROOT
10   IndexNode           12     - FOR geo IN Geo   /* geo index scan, projections: location /
5   CalculationNode     12       - LET geoDistance = GEO_DISTANCE({ "coordinates" : [ -122.084, 37.421997 ], "type" : "Point" }, geo.location)   / simple expression /   / collections used: geo : Geo /
6   CalculationNode     12       - LET #4 = (geoDistance != null)   / simple expression /
7   FilterNode          12       - FILTER #4
8   CalculationNode     12       - LET #6 = { "distance" : geoDistance, "location" : geo.location }   / simple expression /   / collections used: geo : Geo */
9   ReturnNode          12       - RETURN #6
Indexes used:
By   Type   Collection   Unique   Sparse   Selectivity   Fields           Ranges
10   geo    Geo          false    true             n/a   [ location ]   (GEO_DISTANCE({ "coordinates" : [ -122.084, 37.421997 ], "type" : "Point" }, geo.location) <= 30000)
Functions used:
Name           Deterministic   Cacheable   Uses V8
GEO_DISTANCE   true            true        false
Optimization rules applied:
Id   RuleName
1   move-calculations-up
2   move-filters-up
3   remove-unnecessary-calculations
4   move-calculations-up-2
5   move-filters-up-2
6   geo-index-optimizer
7   reduce-extraction-to-projection
Dataset:
No results are returned because geoDistance is null. The issue is because geoPoint2 is being returned purely as a string rather than a GeoJSON object.
Replication Factor & Number of Shards (Cluster only):
None
Steps to reproduce

Problem:
geoPoint2 is a string not a GeoJSON. To fix this query I had to wrap the string with JSON_PARSE as follows:
Let geoPoint2 = JSON_PARSE(geo.location)
Then it works as expected.
Expected result:
According to the documentation here: https://www.arangodb.com/arangodb-training-center/geojson-tutorial/
We should not have to convert the location string to GeoJSON.
Checking my Geo index I have:
<IP_ADDRESS>:8529@diggieDog> db.Geo.getIndexes();
[
  {
    "fields" : [
      "_key"
    ],
    "id" : "Geo/0",
    "selectivityEstimate" : 1,
    "sparse" : false,
    "type" : "primary",
    "unique" : true
  },
  {
    "bestIndexedLevel" : 17,
    "fields" : [
      "location"
    ],
    "geoJson" : true,
    "id" : "Geo/462717",
    "maxNumCoverCells" : 8,
    "sparse" : true,
    "type" : "geo",
    "unique" : false,
    "worstIndexedLevel" : 4
  }
]

Where does it say you can use a string ? Maybe the tutorial is unclear, but only JSON is supported not strings

perhaps it was my mistake. I'm using the java driver to create my geoJSON which I saved as a string.
Any idea on how to save a geo JSON using the java driver?


Using client-go 2.0 with k8s 1.5

I'm trying to use 2.0 branch of client-go to access resources on a 1.5 k8s cluster. Looking at compatibility matrix I expect this to work.
Looks like it is not the case Failed to list *v1beta1.StatefulSet: the server could not find the requested resource.
It there a way to list alpha/beta/stable resources using a single client? The client-go 2.0 is missing v1alpha1.StatefulSet definition.

1.4 server only has v1alpha1.statefulset: https://github.com/kubernetes/kubernetes/tree/v1.4.0/pkg/apis/apps
1.5 server only has v1beta1 statefulset: https://github.com/kubernetes/kubernetes/tree/v1.5.0/pkg/apis/apps
client-go 2.0 is tracking kubernetes 1.5 release, so it only has v1beta1 statefulset.

Failed to list *v1beta1.StatefulSet: the server could not find the requested resource

Regarding the error you observed, could you try kubectl apiversions to see what resources are supported by your apiserver?

@caesarxuchao this basically means there is no way to support multiple versions of Kubernetes (1.3, 1.4, 1.5) using client-go 2.0?
If the client kept v1alpha1 definitions then user could use either v1alpha1 or v1beta1 depending on the server (kubernetes).

Unfortunately, not by using the /kubernetes package. You can try the dynamic client in /dynamic, depending on what you intend to do.
We should update the meaning of + in the compatibility matrix, adding "alpha/beta features might be missing in client-go".

If the client kept v1alpha1 definitions then user could use either v1alpha1 or v1beta1 depending on the server (kubernetes).

client-go shares same version API types with kubernetes, it's difficult to maintain multiple versions. We plan to distribute the client generator in the future, then it's possible to generate clients for deprecated API.


Added Weather app using node.js

Hi @rsriniva ,
Please take a look and let me know if anything else is required.
Thanks

@rsriniva Completed all the changes. Please review and approve.


GEODE-3042: Quick doc of new string-based partition resolver

@dschneider-pivotal @davebarnes97 @pivotal-eshu @joeymcallister and all of the Geode community:  Please review this PR with world-record speed, as it is likely the last item holding up making a 1.2 release candidate.

Thanks Dave and Eric.  I've created https://issues.apache.org/jira/browse/GEODE-3063 to address further documentation for this new feature.  I'm going to merge this in.


[NSNotificationCenter] Implement observation with optional queues.

Please review!
Pending fix of OperationQueue.

This looks good to me although we could use some tests as well. To @phausler for review.

Looks good to me
@swift-ci Please test

Oops, yes.

Let us know when you've added a test case for this and we'll get it merged.

Hey all, sorry for the delay in this. The above commit adds the tests; however it is incorrectly named: NSOperation has a bug that is beyond the scope of this PR IMO, with terrible queue handling. Will be filing a PR to fix soon, so this PR can depend on that.

Ok so you're saying here that this test won't pass until the other PR is merged?

@parkera yes; or I need to rewrite the test to not relay on OperationQueue.current – but I can't think of a good way to test this without basically doing the work needed to fix OperationQueue. Please review the tests as you like; I will do my best to fix soon.

Test looks good to me.

Docs/Status.md should be updated as well. 😉

This pull request has gone stale. If you can rebase against master and re-run the tests, feel free to reopen this pull request.


[Feature Request] Timeline

Existing Component
No
Component Name
Timeline
Description
Is it possible to have timeline component ?
It could be very useful.
Thanks

Sorry, we have no plan to add this.


Broken image in ebay.listing

Description:
$subject
https://central.ballerina.io/ballerinax/ebay.listing/1.5.1#Client

Steps to reproduce:
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

Closing as this is a duplicate of https://github.com/ballerina-platform/ballerina-library/issues/6424


Add UTIL function to convert datetime  to RFC3339.

This would introduce new package dependencies, so it is not going to be added in the next release.


Present new Series Links on Works pages

With https://github.com/wellcomecollection/platform/issues/5426 I have introduced Series Links (partOf relations with no id) to the API.
Now present them on screen

@paul-butcher Can this be closed?


net-mgmt/telegraf: Round Interval setting not working

Plugin: os-telegraf 1.7.5
System: OPNsense 19.7.1-amd64
Description:
The 'Round Interval' setting does not work.
How to reproduce:
Enable 'Round Interval' in Services -> Telegraf -> Genral -> Round Interval.
Solution:
There is a typo in the template file that generates the telegraf.conf.
See: https://github.com/opnsense/plugins/blob/master/net-mgmt/telegraf/src/opnsense/service/templates/OPNsense/Telegraf/telegraf.conf#L17 vs. https://github.com/opnsense/plugins/blob/master/net-mgmt/telegraf/src/opnsense/mvc/app/models/OPNsense/Telegraf/General.xml#L14
I am working on a PR to fix this.

This issue has been automatically timed-out (after 180 days of inactivity).
For more information about the policies for this repository,
please read https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md for further details.
If someone wants to step up and work on this issue,
just let us know, so we can reopen the issue and assign an owner to it.


Simplify custom component structure/class names

Problem
We need to get rid of complex and long custom component class names like class Components::Card::Cell::Card < Component::Cell::Static. Even if #36 fixes the base class name, the Components::Card::Cell::Card part still sucks. This also addresses the folder structure app/matestack/components/card/cell/card.rb
How should it be better?
If I want to create a custom component, called "card", it should work like this:
--> Usage
app/matestack/pages/my_page.rb
class Pages::MyPage < Page::Cell::Page (Matestack::Page --> #36 )
  def response
    components {
       custom_card some_option: "foo"
    }
  end
end

--> Definition
app/matestack/components/card.rb
class Components::Card < Component::Cell::Static (Matestack::StaticComponent --> #36 )
  def response
    components {
       div class: "card" do
          plain "this is a fancy styled card component"
       end
    }
  end
end

If the card component requires additional assets (js, css, haml), they should be stored right next to the related ruby file:
app/matestack/components/card.rb
app/matestack/components/card.scss (optional)
app/matestack/components/card.js (optional)
app/matestack/components/card.haml (optional)
If the component should live in a namespace, a simple folder creates this namespace:
--> Usage
app/matestack/pages/my_page.rb
class Pages::MyPage < Page::Cell::Page (Matestack::Page --> #36 )
  def response
    components {
       custom_gallery_card some_option: "foo"
    }
  end
end

--> Definition
app/matestack/components/gallery/card.rb
class Components::Gallery::Card < Component::Cell::Static (Matestack::StaticComponent --> #36 )
  def response
    components {
       div class: "card" do
          plain "this is a fancy styled card component"
       end
    }
  end
end

This should also affect core component naming and folder structure!

#64


SVS-132: Fail to bind (connected mode) when solution contains a VB.Net project but the server doesn't have the plugin

@Evangelink It's quite difficult to review this PR due to the formatting changes. :-(


Add command to run user boot scripts and update compute docs

overview
Add command to run user boot scripts during start. This is most immediately related to networking issues with the Stanford team
changelog

(feature) Run user boot scripts during start
(docs) Update compute readme

Good docs 10/10 would read again


Fix a typo in button name Meida to Media

Fix a typo in button name Meida to Media

Fix a typo in button name Meida to Media

Thank you for your contribution. We have fixed this issue and synced to GitHub.

Thank you for your contribution. We have fixed this issue and synced to GitHub.


Update CodeCov settings

Fix codecoverage precision.
Due to unstable work on CodeCov tool and precission
issues we need to exclude more folders from scanner:

./@here/olp-sdk-dataservice-api/test
tests
scripts
docs

Relates-TO: OLPEDGE-1657
Signed-off-by: Yaroslav Stefinko<EMAIL_ADDRESS>

Codecov Report

Merging #213 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master    #213   +/-   ##
======================================
  Coverage    90.1%   90.1%
======================================
  Files          57      57
  Lines        1540    1540
  Branches      181     181
======================================
  Hits         1387    1387
  Misses         93      93
  Partials       60      60

Continue to review full report at Codecov.

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


Update Approvers and Reviewers

Changes
Update Approvers and Reviewers
Submitter Checklist

[ ] Includes tests if functionality changed/was added
[ ] Includes docs if changes are user-facing
[x] Set a kind label on this PR
[ ] Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.
Release Notes
NONE

/approve
/lgtm

/retest


Session crashes when setting "connection_timeout" too high

linked to https://github.com/chStaiger/iBridges-Gui/issues/266
Maximum for "connection_timeout" in irods_environment.json is<PHONE_NUMBER> which translates to 292 years.
Add extra check and catching of OverflowError: timestamp too large to convert to C _PyTime_t when session is created.
Maybe we can also give the hint in the docs and in the error catching  that 1 week  corresponds to 604800 seconds.

Should this be something that is fixed in iBridges though? I suppose we can at least update the readthedocs, but otherwise shouldn't this be handled in the PRC? The only thing we do is change the default timeout, which does not give an error.

@d-w-moore do we need to add a too large, but not infinite, number to this test?
https://github.com/irods/python-irodsclient/blob/527417da41a997198e514e0e211b5422585a97a0/irods/test/connection_test.py#L150-L163

We should certainly add the info to the FAQ which number translates to which timeframe and that the maximum number is the number of seconds of 292 years :)

@chStaiger I see that a new branch was created, are you making the adjustments?

@d-w-moore do we need to add a too large, but not infinite, number to this test?
https://github.com/irods/python-irodsclient/blob/527417da41a997198e514e0e211b5422585a97a0/irods/test/connection_test.py#L150-L163

Probably ... what I wonder is - what should be our goal here for the PRC.  The error-dump below shows me that the error occurs in the lower-level socket code. Should PRC become a gatekeeper for this case and artificially limit the value.  If so, we chould have an 'Infinite' or LARGEST_CONNECTION_TIMEOUT constant as a hard-limit, and/or additionally document it in the README
>>> s=h.make_session(connection_timeout =<PHONE_NUMBER>)
>>> s.connection_timeout
9308512000
>>> s.collections.get('/tempZone/home/rods')
Traceback (most recent call last):
  File "/home/daniel/python-irodsclient/irods/session.py", line 322, in server_version
    return tuple(ast.literal_eval(reported_vsn))
  File "/usr/lib/python3.8/ast.py", line 59, in literal_eval
    node_or_string = parse(node_or_string, mode='eval')
  File "/usr/lib/python3.8/ast.py", line 47, in parse
    return compile(source, filename, mode, flags,
  File "<unknown>", line 0

    ^
SyntaxError: unexpected EOF while parsing

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/daniel/python-irodsclient/irods/session.py", line 328, in __server_version
    conn = next(iter(self.pool.active))
StopIteration

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/daniel/python-irodsclient/irods/pool.py", line 70, in get_connection
    conn = self.idle.pop()
KeyError: 'pop from an empty set'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/daniel/python-irodsclient/irods/manager/collection_manager.py", line 22, in get
    query = self.sess.query(Collection).filter(*filters)
  File "/home/daniel/python-irodsclient/irods/session.py", line 286, in query
    return Query(self, *args, **kwargs)
  File "/home/daniel/python-irodsclient/irods/query.py", line 45, in __init__
    if self.sess.server_version >= col.min_version:
  File "/home/daniel/python-irodsclient/irods/session.py", line 324, in server_version
    return self.__server_version()
  File "/home/daniel/python-irodsclient/irods/session.py", line 331, in __server_version
    conn = self.pool.get_connection()
  File "/home/daniel/python-irodsclient/irods/pool.py", line 17, in method_
    ret = method(self,*s,**kw)
  File "/home/daniel/python-irodsclient/irods/pool.py", line 87, in get_connection
    conn = Connection(self, self.account)
  File "/home/daniel/python-irodsclient/irods/connection.py", line 62, in __init__
    self._server_version = self._connect()
  File "/home/daniel/python-irodsclient/irods/connection.py", line 245, in _connect
    s = socket.create_connection(address, timeout)
  File "/usr/lib/python3.8/socket.py", line 793, in create_connection
    sock.settimeout(timeout)
OverflowError: timestamp too large to convert to C _PyTime_t
>>>
>>>

Testing looks dicey but only because of the Python lib's inconsistency in types of error thrown:
import irods.helpers as h
import sys

largest =   LARGEST_PYTHON_TIMEOUT =<PHONE_NUMBER>.854775 # https://stackoverflow.com/questions/45704243/value-of-c-pytime-t-in-python
too_large = LARGEST_PYTHON_TIMEOUT*(1.0+sys.float_info.epsilon)
way_too_large = int(LARGEST_PYTHON_TIMEOUT*(93.0/92))

def f(timeout):
  s=h.make_session(connection_timeout = timeout)
  try:
    print('timeout-del = ',timeout, end=' ')
    s.collections.get('/tempZone/home/dan0')
  except Exception:
    print ('** EXCEPTION')
    raise
  else:
    print('ok')

for t in [largest,too_large, way_too_large]:
   try:
      print ('============================================================')
      f(t)
   except Exception as e:
      print('excinfo',type(e))

gives:
$ python conntimeout.py
============================================================
timeout-del =<PHONE_NUMBER>.854774 ok
============================================================
timeout-del =<PHONE_NUMBER>.854776 ** EXCEPTION
excinfo <class 'ValueError'>
============================================================
timeout-del =<PHONE_NUMBER> ** EXCEPTION
excinfo <class 'OverflowError'>

Can’t we just catch both in PRC?   Is that weird / confusing?

Can’t we just catch both in PRC? Is that weird / confusing?

We can do that. It was just confusing that the tour of Error depends on the amount by which we exceeded the threshold

Agreed.  But, seems well behaved enough for us to react consistently and protect our PRC users (hi!).

note comments at the top of 3.12...
https://github.com/python/cpython/blob/3.12/Include/cpython/pytime.h
are gone in 3.13...
https://github.com/python/cpython/blob/3.13/Include/cpython/pytime.h
with more words now at
https://github.com/python/cpython/blob/3.13/Doc/c-api/time.rst

also, just for the record...
clamping our PRC session timeout to 292 years seems... sufficient :)

@chStaiger I see that a new branch was created, are you making the adjustments?

Yes, I will update the doc and will insert some error catching.

@chStaiger I see that a new branch was created, are you making the adjustments?

Yes, I will update the doc and will insert some error catching.

I propose that we don't do any error catching for now. After we update the docs, almost no one should run into the issue.

Yes, I just threw a warning and corrected the number. PR will follow asap.

Yes, I just threw a warning and corrected the number. PR will follow asap.

Even that I wouldn't do, especially if it going to get handled in the PRC or future versions of CPython. We could make another item in the FAQ?


Add precision != 0 check when making decimal type

Which issue does this PR close?

Closes #3665.
Rationale for this change

The precision of decimal type should not be zero, which we should check it.
What changes are included in this PR?

Add precision != 0  check
Update the error message to make it more readable
Add tests.

Are there any user-facing changes?

Thank you for review @alamb .

Can you please file a ticket in arrow-rs if you think it should be fixed there as well?

I've filed https://github.com/apache/arrow-rs/issues/2852 to discuss a better way to solve this problem.


Cannot open a BAX file from disk

If the app is opened and it doesnt auto load the last bax file, opening an existing bax file selected from disk will crash the app.

Recently tested and is no longer an issue.


Failed to import -<EMAIL_ADDRESS>

Failing module

GitHub: https://github.com/yisibl/resvg-js
npm: https://www.npmjs.com/package/@resvg/resvg-js

import SVGSpriter from<EMAIL_ADDRESS>
Error message
After running deno run I got this:
error: Import 'https://esm.sh/v117/<EMAIL_ADDRESS>failed: 500 Internal Server Error
    at https://esm.sh/v117/svg-sprite@2.0.2/X-ZS8q/deno/svg-sprite.mjs:2:602

Additional info

esm.sh version: v117
Deno version: 1.32.5

the error is
npm: package '@resvg/resvg-js-darwin-universal'

Hmm.
Probably has something to do with this: https://github.com/yisibl/resvg-js/issues/153
Not sure how to resolve it.
But I will poke around.
Thanks.


feat: add 1.4.1 contracts for Zilliqa EVM Testnet

Closes https://github.com/safe-global/safe-deployments/issues/618

@ElvisKrop could you please solve conflicts?


add option agentInstallAll, to control if install cluster-proxy addon…

… agent to all clusters
sometimes, we do not want install cluster-proxy to all clusters, but there is no this option

@qiujian16 @yue9944882  Plz review

should we also update the helm chart?
/approve

should we also update the helm chart?
/approve

@qiujian16 Yes, I have update.  And what should I do for e2e?

@qiujian16 @yue9944882 Plz merging this pr. Thx!

/lgtm

sorry, I missed this...


NEW: repeat pipe

Added a repeat pipe which returns subsequent copies of the input pipe's elements, e.g, {1,2} => {1,1,2, 2}. It may be simple, but I wanted to play around with your neat pipes library ;)
FYI: I'm also working on a batch pipe, returning fixed sized batches of consecutive input pipe elements up to the last batch which may contain less than the specified batch size (i.e., the remaining elements).

Thanks for your PR.
Just to make sure I understand the use case for repeat, would you have in mind an example of usage in practice?
Does the range library have something equivalent? (the range view called repeat does something different)

I just checked it, the ranges library actually has sth similar (if I"m not wrong, see here: https://github.com/ericniebler/range-v3/blob/master/test/view/repeat.cpp).
For a simple use case: honestly, I did not think about any. The simplest one is probably just to replicate input elements N times into the output pipe. For sure, this could also be achieved y demuxing into N pipes and then combining them again using join (I guess). If there is no need, I'm fine. Again, I was just looking towards playing around with the pipes library :)


glib-networking: build .so on macOS

GIO needs modules to be named .so. This patch does that for us. Should
be included in the next release.
Fixes #41071

@grahamcofborg build gimp

Sorry missed that! Is it okay to add the patch for release-18.09 though?

If it applies, I do not see why not. The patch looks fairly straightforward.


Possible bug with the street function in the ImpostorTemplate

This seems to be an issue with the generation from within the ImpostorTemplate
julia> impostor_template(4, DataFrame; locale=["pt_BR", "en_US"])
4×5 DataFrame
 Row │ country                   state      city            district                 street
     │ String?                   String31   String31        String31                 String
─────┼─────────────────────────────────────────────────────────────────────────────────────────────────────────────
   1 │ United States of America  Nebraska   Lincoln         Lincoln District         Rua Ian Oliveira
   2 │ United States of America  Missouri   Jefferson City  Jefferson City District  Alameda Maria Clara Fernandes
   3 │ Brazil                    São Paulo  Sorocaba        Bairro de Sorocaba       Bobby Fisher Street
   4 │ United States of America  Maine      Portland        Portland District        Alvarez Avenue

Propably the street function is not receiving the locales properly.

Closing as #14 has been merged.


Paper of fast-euclidean-clustering

Does your implementation correspond to FEC?
But it seems your implementation is totally different from his.

Well, when I came up with this idea, I wasn't aware of that preceding work and accidentally picked the same name for the algorithm. Anyway, the both are almost identical with subtle differences on parameters. I'm not sure if I should rename this project.

@unageek Thanks. I think several projects have borrowed your idea such as https://github.com/YevgeniyEngineer/LiDAR-Processing, https://github.com/nubot-nudt/ElC-OIS.


Error when running server (encoding.js)

When running jskos-server (npm run start) an error occurs.
Problem: in the file jskos-server/node_modules/whatwg_url/dist/encoding.js in line 2 "new TextEncoder();" "TextEncoder" is not defined.
Solution: add following string to line 2: "const { TextEncoder, TextDecoder } = require("util");"
(Source:  https://stackoverflow.com/questions/19697858/referenceerror-textencoder-is-not-defined)

I don't think the solution helps. This is a dependency of a dependency. We can't simply change a line of code inside of that. The node_modules folder is recreated on every machine when installing dependencies via npm install or npm ci.
Since we haven't encountered this issue anywhere else yet (neither in tests, nor in local installations, nor in our various public instances), I need a lot more context in order to figure this out. In particular, I need as much information about your environment as possible. OS, Node and npm versions, are you using Docker and if yes, which version, etc. I need to reproduce this issue so I need anything you can give me. Thanks!

It would also be very helpful to get the full error stack, in order to see where in OUR code the error occurred.

This is the full error code:
/home/david/Dokumente/jskos-server/node_modules/whatwg-url/dist/encoding.js:2
const utf8Encoder = new TextEncoder();
^
ReferenceError: TextEncoder is not defined
at Object. (/home/david/Dokumente/jskos-server/node_modules/whatwg-url/dist/encoding.js:2:21)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Module.require (internal/modules/cjs/loader.js:692:17)
at require (internal/modules/cjs/helpers.js:25:18)
at Object. (/home/david/Dokumente/jskos-server/node_modules/whatwg-url/dist/url-state-machine.js:5:34)
at Module._compile (internal/modules/cjs/loader.js:778:30)
[nodemon] app crashed - waiting for file changes before starting...

Environment:

Ubuntu 20.04 on a VM (VirtualBox).
Jskos-server: 1.2.12 (master)
node: 10.19.0
npm: 6.14.4

node: 10.19.0

You need at least Node.js 12 to run jskos-server. I wouldn't recommend using Node.js 10 since it's long out of maintenance already. I would recommend using fnm to manage Node versions and install at least Node.js 14 to run our software.
However, this issue made me realize that this is not documented anywhere. That's my fault; I'll update the documentation!

npm install/npm ci will now throw an error if you try to use it with an unsupported Node.js version.


Bug: Fix animation getting stuck when swipeThreshold not reached

Hi,
We are currently experiencing issues with the swipe animation getting stuck if the swipeThreshold has not been reached. Have tested the following PR which resolves the issue: https://github.com/maxs15/react-native-modalbox/pull/278
Would be great if you could look into this and see if it can be merged in to resolve this issue. #

Released in v2.0.0


Dimension error in forward pass

I am receiving the following error when I try to run the train script:
File "train.py", line 266, in <module>
    main()
  File "train.py", line 263, in main
    train(transformer, training_data, validation_data, crit, optimizer, opt)
  File "train.py", line 124, in train
    train_loss, train_accu = train_epoch(model, training_data, crit, optimizer)
  File "train.py", line 55, in train_epoch
    pred = model(src, tgt)
  File "/home/ubuntu/miniconda3/envs/cuda/lib/python3.6/site-packages/torch/nn/modules/module.py", line 206, in __call__
    result = self.forward(*input, **kwargs)
  File "/home/ubuntu/attention-is-all-you-need-pytorch/transformer/Models.py", line 179, in forward
    enc_outputs, enc_slf_attns = self.encoder(src_seq, src_pos)
  File "/home/ubuntu/miniconda3/envs/cuda/lib/python3.6/site-packages/torch/nn/modules/module.py", line 206, in __call__
    result = self.forward(*input, **kwargs)
  File "/home/ubuntu/attention-is-all-you-need-pytorch/transformer/Models.py", line 76, in forward
    enc_output, slf_attn_mask=enc_slf_attn_mask)
  File "/home/ubuntu/miniconda3/envs/cuda/lib/python3.6/site-packages/torch/nn/modules/module.py", line 206, in __call__
    result = self.forward(*input, **kwargs)
  File "/home/ubuntu/attention-is-all-you-need-pytorch/transformer/Layers.py", line 18, in forward
    enc_input, enc_input, enc_input, attn_mask=slf_attn_mask)
  File "/home/ubuntu/miniconda3/envs/cuda/lib/python3.6/site-packages/torch/nn/modules/module.py", line 206, in __call__
    result = self.forward(*input, **kwargs)
  File "/home/ubuntu/attention-is-all-you-need-pytorch/transformer/SubLayers.py", line 68, in forward
    return self.layer_norm(outputs + residual), attns
  File "/home/ubuntu/miniconda3/envs/cuda/lib/python3.6/site-packages/torch/nn/modules/module.py", line 206, in __call__
    result = self.forward(*input, **kwargs)
  File "/home/ubuntu/attention-is-all-you-need-pytorch/transformer/Modules.py", line 52, in forward
    ln_out = (z - mu.expand_as(z)) / (sigma.expand_as(z) + self.eps)
  File "/home/ubuntu/miniconda3/envs/cuda/lib/python3.6/site-packages/torch/autograd/variable.py", line 681, in expand_as
    return Expand.apply(self, tensor.size())
  File "/home/ubuntu/miniconda3/envs/cuda/lib/python3.6/site-packages/torch/autograd/_functions/tensor.py", line 106, in forward
    result = i.expand(*new_size)
RuntimeError: The expanded size of the tensor (24) must match the existing size (64) at non-singleton dimension 1. at /home/ubuntu/cuda-ubuntu-16.04-ec2/pytorch/torch/lib/THC/generic/THCTensor.c:323

Hi @angusturner ,
Thanks for the report!
Would you mind to provide your parameter settings?
Is it fine to train with WMT16 data provided in the README?
Thank you!

same issue here. z is supposed to be of size  bz x len_q x (n_head * v_dim), however, mu will be of size: bz x (n_head * v_dim), so we need to insert a singleton dimension at second dim.
so change below:
mu.unsqueeze(dim=1).expand_as(z)
```.

I followed README here, and get the same error when I run 'python train.py -data data/multi30k.atok.low.pt -save_model trained -save_mode best -proj_share_weight
'

Hi @suhmily!
Thanks for the explanation!
However, to make use of the newest api, I just made a small patch.
Now the code can be run under PyTorch 2.0. Please take a look!
Thanks,
Yu-Hsiang


Hard-coded S3 Config

The S3 config is hard-coded in a script. It is supposed to be read from the system environment set by end-user. I think even if the end-user sets another config for the S3 to use another S3 storage, this hard-coded config will overwrite the system environments. A default value for the S3 config can be set, but it should be overwritten by the value set by the end-user.
https://github.com/FLARE-forecast/FCRE-forecast-code/blob/5aa09779396edcf0eaa5d4658ef4f012164c7488/main_workflow.R#L22

Fixed a while ago


Add support for person_profiles in react-native-posthog

Is your feature request related to a problem?
I would like to be able to use the person_profiles property to set as identified_only in my react native app
Describe the solution you'd like
To add support for the person_profiles in the react native packages
Describe alternatives you've considered
None
Related sub-libraries

[ ] All of them
[ ] posthog-web
[ ] posthog-node
[x] posthog-react-native

Can be done with https://github.com/PostHog/posthog-js-lite/issues/290


Add non request statements to Client

This would allow for example to add helper methods to the Client which do some conversion from/to the RPC messages.

Codecov Report

Merging #165 into master will decrease coverage by 4.13%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #165      +/-   ##
==========================================
- Coverage   93.02%   88.88%   -4.14%
==========================================
  Files          31       31
  Lines         301      315      +14
  Branches        6        6
==========================================
  Hits          280      280
- Misses         21       35      +14

Continue to review full report at Codecov.

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


[DOC]: Update Model Cards to Model Card ++ format

How would you describe the priority of this documentation request
High
Please provide a link or source to the relevant docs
https://github.com/nv-morpheus/morpheus-experimental/blob/branch-23.07/anomalous-auth-detection/README.md
Describe the problems in the documentation
Model cards need to specifically address bias, explainability, privacy, safety and security per Nvidia's model card ++ format.
Model creators should update their own model cards.

[ ] anomalous-auth-detection @tzemicheal
[ ] appshield-dga-detection @raykallen
[ ] asset-clustering @avinashvem
[ ] dga-detection @gbatmaz
[ ] ids-detection @tzemicheal
[ ] log-sequence-ad @tzemicheal
[ ] operational-technology @gbatmaz
[ ] phishing-url-detection @gbatmaz
[ ] string-resemblance-grouping @shawn-davis

(Optional) Propose a correction
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I have searched the open documentation issues and have found no duplicates for this bug report

@raykallen Is this completed?


export parser.term.js

It helps to have these terms exported when we have to analyze the tree for the linter.
It will also help to have something similar of what is coding in prometheus: https://github.com/prometheus/prometheus/blob/fac7a4a0504404fa5d4c5abb8fcc9750bd5cbda7/promql/parser/parse.go#L424

/assigned to @juliusv

it will also improve the autocompletion by doing this:
import { AggregateExpr } from 'lezer-promql';

tree.type.id === AggregateExpr

instead of doing this:
tree.name === "AggregateExpr"

If you can wait before merging this PR. I'm currently translating this code: https://github.com/prometheus/prometheus/blob/master/promql/parser/parse.go#L433 and I'm not sure anymore it will be super helpful to have these constants exported ...

Ok, will wait...

Should be fine at the end. Sorry for the delay and the mess
I'm still not able to iterate over the tree, but it will be a nice improvement to have these constant exported. It will reduce the number of magic string used.

and I think we should do like you said in a previous PR. Removing the map exported from the file promql.term.js and instead exporting multiple constants, one per list. Like that:
export const matchOpTerms = [
        "=",
        "!=",
        "=~",
        "!~"
];
export const binOpTerms: [
        "^",
        "*",
        "/",
        "%",
        "+",
        "-",
        "==",
        ">=",
        ">",
        "<",
        "<=",
        "!=",
        "and",
        "or",
        "unless"
];

If you are ok with that, should I open another PR to make the changes ? or it is ok if I'm pushing the changes here ?

Fine to do it here, I think!

thanks :). Should be fine now !

:+1:


Bug: Duplicate JSONString in the docs

What are you trying to achieve?
.
Steps to reproduce the problem
JSONString docs are duplicated:
https://docs.saleor.io/docs/3.x/api-reference/scalars/json-string
https://docs.saleor.io/docs/3.x/api-reference/scalars/jsonstring
This could be because graphene.JSONString and custom JSONString exist.
What did you expect to happen?
.
Logs
No response
Environment
.

Was fixed in the docs.


Fix the DRS version in documentation and service-info.

Fix the DRS version in the documentation and the service-info response to "1.3.0experimental"
Add a note on the admin endpoints indicating they are beyond the DRS specification

Codecov Report

Merging #75 (cd2e61d) into develop (3d5cf79) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop      #75   +/-   ##
==========================================
  Coverage      65.06%   65.06%
  Complexity       241      241
==========================================
  Files             51       51
  Lines            873      873
  Branches          60       60
==========================================
  Hits             568      568
  Misses           294      294
  Partials          11       11

Impacted Files
Coverage Δ

...tarterkit/drs/constant/DrsServiceInfoDefaults.java
100.00% <ø> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add support for Craft 3.1's environmental settings

Following https://docs.craftcms.com/v3/extend/environmental-settings.html

Thanks Ben.
Would you like to take ownership of this package?  We don't use Postmark and I'm happy to transfer it to you.


Using Adaptive Lighting on IKEA bulbs affects dimming on IKEA wireless dimmer

Issue

I recently switched to a RaspBee & Homebridge setup in order to use Adaptive Lighting (thank you, by the way!), but when it's in use, my little square IKEA dimmer isn't able to adjust the brightness - instead it changes the temperature of the lights while the brightness stays the same.
I have two light bulbs grouped together that the dimmer switch exclusively controls. The switch is set up in Phoscon to provide the dimmer functionality.
When a specific color temperature is set, the dimming works as expected.
If there's any more debugging I can do to help, let me know!
Log Messages

[12/15/2020, 7:18:25 PM] [Hue] Den on/off switch Off: homekit button long press
[12/15/2020, 7:18:25 PM] [Hue] Den Ceiling Light 1: set homekit brightness from 81% to 0%
[12/15/2020, 7:18:25 PM] [Hue] Den Ceiling Light 1: homekit adaptive lighting color temperature changed from 317 mired to 416 mired
[12/15/2020, 7:18:25 PM] [Hue] Den Ceiling Light 1: set homekit color temperature from 416 mired to 317 mired
[12/15/2020, 7:18:25 PM] [Hue] Den Ceiling Light 2: set homekit brightness from 81% to 0%
[12/15/2020, 7:18:25 PM] [Hue] Den Ceiling Light 2: homekit adaptive lighting color temperature changed from 317 mired to 416 mired
[12/15/2020, 7:18:25 PM] [Hue] Den Ceiling Light 2: set homekit color temperature from 416 mired to 317 mired
[12/15/2020, 7:18:25 PM] [Hue] Den Ceiling Light 1: set homekit color temperature from 317 mired to 416 mired
[12/15/2020, 7:18:25 PM] [Hue] Den Ceiling Light 2: set homekit color temperature from 317 mired to 416 mired
[12/15/2020, 7:18:26 PM] [Hue] Den Ceiling Light 2: set homekit brightness from 0% to 79%
[12/15/2020, 7:18:26 PM] [Hue] Den Ceiling Light 2: homekit adaptive lighting color temperature changed from 416 mired to 319 mired
[12/15/2020, 7:18:26 PM] [Hue] Den Ceiling Light 2: set homekit color temperature from 319 mired to 416 mired
[12/15/2020, 7:18:26 PM] [Hue] Den Ceiling Light 2: set homekit color temperature from 416 mired to 319 mired
[12/15/2020, 7:18:31 PM] [Hue] Den Ceiling Light 2: set homekit brightness from 79% to 81%
[12/15/2020, 7:18:31 PM] [Hue] Den Ceiling Light 2: homekit adaptive lighting color temperature changed from 319 mired to 317 mired
[12/15/2020, 7:18:31 PM] [Hue] Den Ceiling Light 2: set homekit color temperature from 317 mired to 319 mired
[12/15/2020, 7:18:31 PM] [Hue] Den Ceiling Light 2: set homekit color temperature from 319 mired to 317 mired
[12/15/2020, 7:18:39 PM] [Hue] Den on/off switch On: homekit button long press
[12/15/2020, 7:18:39 PM] [Hue] Den Ceiling Light 1: set homekit brightness from 0% to 100%
[12/15/2020, 7:18:39 PM] [Hue] Den Ceiling Light 1: homekit adaptive lighting color temperature changed from 416 mired to 290 mired
[12/15/2020, 7:18:39 PM] [Hue] Den Ceiling Light 1: set homekit color temperature from 290 mired to 416 mired
[12/15/2020, 7:18:39 PM] [Hue] Den Ceiling Light 2: set homekit brightness from 81% to 100%
[12/15/2020, 7:18:39 PM] [Hue] Den Ceiling Light 2: homekit adaptive lighting color temperature changed from 317 mired to 290 mired
[12/15/2020, 7:18:39 PM] [Hue] Den Ceiling Light 2: set homekit color temperature from 290 mired to 317 mired
[12/15/2020, 7:18:39 PM] [Hue] Den Ceiling Light 1: set homekit color temperature from 416 mired to 290 mired
[12/15/2020, 7:18:39 PM] [Hue] Den Ceiling Light 2: set homekit color temperature from 317 mired to 290 mired
[12/15/2020, 7:18:41 PM] [Hue] Den Ceiling Light 1: set homekit brightness from 100% to 80%
[12/15/2020, 7:18:41 PM] [Hue] Den Ceiling Light 1: homekit adaptive lighting color temperature changed from 290 mired to 318 mired
[12/15/2020, 7:18:41 PM] [Hue] Den Ceiling Light 1: set homekit color temperature from 318 mired to 380 mired
[12/15/2020, 7:18:41 PM] [Hue] Den Ceiling Light 2: set homekit color temperature from 290 mired to 310 mired
[12/15/2020, 7:18:42 PM] [Hue] Den Ceiling Light 1: set homekit color temperature from 380 mired to 318 mired
[12/15/2020, 7:18:44 PM] [Hue] Den Ceiling Light 2: set homekit color temperature from 310 mired to 290 mired

It does change the brightness to 0% / 100% when I start to hold the button and later setting it back to its original brightness (more or less?) when I've released the button. Though it's a little strange, this seems like expected behavior, since it does the same thing when Adaptive Lighting isn't on - except the brightness level does change:
[12/15/2020, 7:37:31 PM] [Hue] Den on/off switch Off: homekit button long press
[12/15/2020, 7:37:31 PM] [Hue] Den Ceiling Light 1: set homekit brightness from 40% to 0%
[12/15/2020, 7:37:31 PM] [Hue] Den Ceiling Light 2: set homekit brightness from 40% to 0%
[12/15/2020, 7:37:33 PM] [Hue] Den Ceiling Light 2: set homekit brightness from 0% to 26%
[12/15/2020, 7:37:33 PM] [Hue] Den Ceiling Light 1: set homekit brightness from 0% to 26%

Debug Files

homebridge-hue.json.gz

homebridge.log.gz

Phoscon created rules on the gateway to handle the button events sent by the dimmer.  These rules use group commands to update the brightness when the button is held.  I cannot tell from the Homebridge logs, but I think deCONZ reports the target brightness (over web socket notifications), before the lights have actually adjusted their brightness.  Homebridge Hue picks this up, and sends light commands to update the colour temperature.  These messages reach the lights just before the group command to update the brightness.  Due to the bug in the light firmware, they ignore the brightness command, because they're still transitioning the colour temperature.
I don't think I can do anything about this.  IKEA needs to fix their light firmware.  You can probably work around the issue by using HomeKit automations (so Homebridge Hue sends the command to change the brightness) or by directly controlling the group from the switch (so the deCONZ API only reports the brightness after the lights have changed), instead of using the gateway rules created by Phoscon.


Feature request: Add option to have x-axis represent time

Great work first of all, this is much appreciated. 👍
Are there plans to allow the x-axis to update over time, like the Arduino Serial plotter does?
Right now the x-axis never updates. It just ranges from 0 to the initially defined width.
For signals that don't change much over time, it's useful to know the approximate time since startup that the most recent value plotted occurred.
Or at a minimum allow the mouseover tool tip to show the time value for the value of the x-coordinate if it's too difficult to scale the x-axis.
Perhaps allow for a specific log format to represent (time (e.g., millis()), value) to be plotted so that independent of when the plotter was launched, the x-axis can represent the time values being logged.

Thank you for your feedback.
For the moment, there is no plan on this, but I’ll consider this for the enhancement in future.

Closing it for now.


upload hangs

When trying to upload, I get a "connecting to..." message, then it just sits there. In order to get it to work, I have to do several uninstall/reinstall cycles. Any ideas?

duplicate with  #199 ?


feat(.github/ISSUE_TEMPLATE): add bug and feature templates

Description
Since the contributions are increasing it might be helpful to have a templates to apply a bug report or feature request.
If this pr will be merged when someone want to open a pr can choose between:

bug report
feature request
blank issue (by config we can also remove this possibility)

If for example the user want to apply a bug report this is the form that he/she/they have:

He/she/they have to fill out all the required elements in order to submit.
How to try the templates
Just use my fork: https://github.com/Wabri/community.sap_install/issues/new/choose
Example of submit
You can find at this link => https://github.com/Wabri/community.sap_install/issues/121

Additional infos
To start using it you will need to merge to main, I'll change if this can be useful.
Question
Can be useful also for the other repositories?

Title standardisation through automation
I've added an automation that fill the title by following this standard:
[Bug] <role_name> on <os_family>: <short_description>

and
[Feature] <role_name> on <os_family>: <short_description>

The role name and os family is written only if applicable.
Checks
For now I've added a couple of checks for the titles:

the object of the title [Bug] or [Feature] should be link with labels bug or enhancement. Example (see the comment in the issue linked): https://github.com/Wabri/community.sap_install/issues/141
the title should include a short description. Example (see the comment in the issue linked): https://github.com/Wabri/community.sap_install/issues/139

Title update itself
Once the user create a issue that follow the standard, the automation will fill with the information found in the issue description. For example an issue with this title [Bug]: something dont work become [Bug] sap_ha_pacemaker_cluster on RHEL: something dont work with sap_ha_pacemaker_cluster taken from the issue description same for RHEL.
Here an example: https://github.com/Wabri/community.sap_install/issues/140

If you have suggestions and improvements just ping me.


[PROPOSAL] Simplify OpenSearch distribution branching strategy

What/Why
What are you proposing?
We should change the branching strategy used across the OpenSearch Project to track two releases instead of three. We should make this change when we do the next major version release (3.0) of the distribution.
This change applies to all repositories that are part of the OpenSearch distribution (core, dashboards, plugins, etc). Some repositories, such as clients, have independent release cycles and are not impacted by this change.
Background
Currently, we track three releases in parallel:

3.0 (the next major release) on the main branch
2.x (the next minor release) on the 2.x branch
1.3.x (the next maintenance release) on the 1.3 branch

This strategy optimizes for being able to incubate and develop breaking changes for the next major release for an extended period of time, as that code would be on the main development branch. The cost of this strategy is that all non-breaking changes intended for the next minor release require an extra step of backporting to the 2.x branch. The previous 2.5+ years have shown us that we have incubated very few breaking changes on the main branch for an extended period. While we have automation that makes backports to the 2.x branch very low effort for the majority of changes, it is not perfect (e.g. automation hits conflicts requiring manual resolution, flaky tests may fail, it takes time even when everything works perfectly). I believe the cost of these paper cuts, multiplied by thousands of changes across scores of repos, outweigh the benefits of the current approach. I also have no reason to believe things would be different for the 3.x→4.0 cycle than it was for the 2.x→3.0 cycle.
Proposal
The proposal is to track only two releases in parallel. After the 3.0 release, we will have the following branches:

main tracking the 3.x version (the next minor release)
2.<last>.x tracking the next maintenance release of the 2.<last> version

At the time of a minor release, we will cut a release branch (e.g. 3.1) from the main branch. Development for the following minor release will continue on main and the 3.1 version will be built from the 3.1 branch.
At the time of a maintenance release, we will cut a release branch (e.g. 2.19.1) from the 2.19.x branch. The maintenance release will then be built from the 2.19.1 branch.
What users have asked for this feature?
This is a change to development and will not impact users. Developers frequently complain about friction introduced by backports.
What problems are you trying to solve?
This proposal is an attempt to reduce development friction by optimizing for what we routinely do (develop new features in a backward compatible way targeted toward the next minor release) at the expense of what we do not do (incubate breaking changes for an extended period in a snapshot build of the next major release).
What is the developer experience going to be?
The vast majority of code changes are intended to be released in the next minor version. With this proposal, such changes will require only one PR to commit the change to the main branch. This is in contrast to the procedure today, which requires committing the change to main and triggering a backport to the 2.x branch.
Are there any security considerations?
No.
Are there any breaking changes to the API
No.
Why should it be built? Any reason not to?
We should do this to improve the developer experience across dozens of repos.
The downside is that we will have no dedicated place to stage future 4.0 changes or routinely build 4.0 snapshot distributions. If someone wants to incubate a breaking change they would need to create a separate branch and regularly rebase it against main. We would have no automated mechanism to build a complete 4.0 distribution containing breaking changes in multiple components.
What will it take to execute?
This is a change in branching convention that will have to be coordinated across all repos that are part of the distribution. Some release tooling in opensearch-build may need to be updated to handle the new convention.

This is a great proposal, as the amount of backport PRs we did in 2.x is huge.
Will we continue releasing patch releases often such as 3.1.1 after 3.1 before 3.2? Feels like we want that to be reserved to urgent high severity security issues and just do 3.1, 3.2, 3.3, etc.

Will we continue releasing patch releases often such as 3.1.1 after 3.1 before 3.2? Feels like we want that to be reserved to urgent high severity security issues and just do 3.1, 3.2, 3.3, etc.

Patches of the current minor version (e.g. 3.1.1) only happen for high severity issues. If a 3.1.1 release is necessary it would be built from a 3.1.1 branch created off of the 3.1 branch with only the high severity fixes cherry picked. This proposal does not change that policy.

And we won't need a 3.x branch.

That's correct. With this proposal we track two releases which means only two active branches: main and 2.19.x. At the time of any release (either regularly scheduled or a patch) we cut a release branch from the appropriate branch, but we don't continue to maintain release branches after the release.

I have a very minor preference for renaming main to 3.x because it's the branch that we cut 3.x releases from (i.e. 3.1, 3.2, etc.)
At the end of the day, it wouldn't change anything functionally. It would just feel a little closer to "Developing directly on 2.x", which of course is something we decided not to do during the 2.x line (but we're advocating for here).
As I said -- it's a very minor preference. If we decide to keep the name of the branch as main, I still think that avoiding a backport for every single PR (and the main -> 2.x BWC dance) is a great idea.

I am on the same page with Andrew's proposal.
Overall it should simplify the process not only on code developer side, but also on infra and automation as we do not need to maintain a specific next version build that breaks very often due to instability of the code.
Thanks.

I have a very minor preference for renaming main to 3.x because it's the branch that we cut 3.x releases from (i.e. 3.1, 3.2, etc.)

This would be very surprising to anyone coming to the project and would make the main branch a moving target for dozens of repos.

This would be very surprising to anyone coming to the project and would make the main branch a moving target for dozens of repos.

I don't understand the second clause. I'm suggesting that instead of having a branch named main, it would literally be called 3.x -- nothing moving. Since other repos (mostly?) take a dependency on built artifacts (which are versioned) rather than branches, I don't understand how it would impact them one way or another.

@msfroh I think @dblock is saying it would be surprising that the default branch would be a moving target, because it would change with every major version. The convention is that the name of the default branch is fixed (main or mainline or master etc) and always represents development on the latest version. @dblock please correct me if I'm wrong.

@andrross thanks, you said exactly what I was thinking

@msfroh I think there is value in making it obvious which version number is associated with main and I think it breaks 'standard' convention to remap HEAD to a version'ed branch instead of main as @andrross points out.
Cheap alternative, what would you think of a small piece of automation that kept a 3.x branch in lockstep with main on ever push?

@andrross Thanks starting this discussion - I'm in full support of creating a 3.0.0 release.
In conjunction with this major release revisiting the release methodology and messaging might be a good exercise, as once upon a time we did -alpha releases.  At the very least do a pass over the release process and confirm if we are making any changes.  I'd love to see a blog post 😄

Cheap alternative, what would you think of a small piece of automation that kept a 3.x branch in lockstep with main on ever push?

I don't think that would be of much benefit to anyone. If I cared enough, I could create a branch named 3.x in my local repository setup to track the main branch from the project whenever I git pull. (Or I could name my local branch whatever I want, like zorgoth_destroyer_of_worlds.)  In practice, I'm happy to go along with the consensus of sticking to the main name.


Switch to Horizontal Scroll View

Basically, instead of handing everything ourselves we should switch to a horizontal scroll box and hide the scroll bar. This will also fix the (ios) issue of dragging on the image then accidentally dragging down in a scrollview which cancels the scroll.

Finished.


[SPARK-47049][BUILD] Ban non-shaded Hadoop dependencies

What changes were proposed in this pull request?
This PR aims to ban non-shaded Hadoop dependencies (including transitive ones).
Why are the changes needed?
SPARK-33212 moved to shaded Hadoop dependencies at Apache Spark 3.2.0. This PR will make it sure that we don't have any accidental leftovers.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.

Could you review this, please, @sunchao ?

Thank you, @sunchao . Yes, it's irrelevant to this.
Merged to master.


feat(io.vavr.control): add a model that expresses the return value of functions

use LogicalResult model to expresses return value of logical
function,
use ProcessResult model to expresses return value of
instruction function.

Codecov Report

Merging #2624 (7ebaab2) into master (0b7a72c) will decrease coverage by 0.08%.
The diff coverage is 74.73%.

@@             Coverage Diff              @@
##             master    #2624      +/-   ##
============================================
- Coverage     92.81%   92.73%   -0.09%
- Complexity     5338     5380      +42
============================================
  Files            89       92       +3
  Lines         12743    12872     +129
  Branches       1609     1631      +22
============================================
+ Hits          11828    11937     +109
- Misses          727      738      +11
- Partials        188      197       +9

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/io/vavr/control/ProcessResult.java
70.37% <70.37%> (ø)
12.00 <12.00> (?)

src/main/java/io/vavr/control/LogicalResult.java
79.48% <79.48%> (ø)
7.00 <7.00> (?)

src/main/java/io/vavr/control/Results.java
100.00% <100.00%> (ø)
1.00 <1.00> (?)

src/main/java/io/vavr/collection/Queue.java
95.76% <0.00%> (-0.69%)
202.00% <0.00%> (ø%)

src/main/java/io/vavr/collection/Stream.java
98.30% <0.00%> (-0.35%)
270.00% <0.00%> (+6.00%)
:arrow_down:

src/main/java/io/vavr/collection/HashSet.java
95.72% <0.00%> (-0.04%)
140.00% <0.00%> (ø%)

...rc/main/java/io/vavr/collection/LinkedHashSet.java
96.58% <0.00%> (-0.03%)
145.00% <0.00%> (ø%)

src/main/java/io/vavr/collection/TreeSet.java
97.85% <0.00%> (-0.02%)
166.00% <0.00%> (-2.00%)

src/main/java/io/vavr/collection/Vector.java
99.38% <0.00%> (-0.01%)
211.00% <0.00%> (-4.00%)

src/main/java/io/vavr/collection/BitSet.java
98.02% <0.00%> (-0.01%)
82.00% <0.00%> (ø%)

... and 15 more

Continue to review full report at Codecov.

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

This PR is to provide a prototype implementation for the discussion of the issue #2625

I see that in the v2.0.0 branch, the inheritance of Value has been removed.
If I want to continue to improve, should I develop based on v2.0.0 or master?
Looking forward to your reply.

Thank you for your engagement, I really appreciate it!
Before a PR, there needs to be a discussion on the why and how a requested feature strategically fits into Vavr.
I took a look at your source code. You follow the general Vavr style (e.g. factory methods etc), that is great. But I don't see a place for this change in the Vavr core library, maybe because I don't fully understand the domain of application, yet.
Please let's move the further discussion to #2625, I will close this PR for now.
- Daniel


Error: Module 'FirebaseCore' not found

When trying to run the app on my iPhone Xs using Xcode I get this error. What should I do?

Try Building. Xcode doesn't see modules from CocoaPods until after the first build.

I'm getting the same error for both "FirebaseCore" and "MaterialComponents" when building.

Hi Glenn,
Thank you for checking this out!
I tried to reproduce this issue locally, and I can only spot it  when openning the ShowcaseApp.xcodeproj directly. Have you tried to open ShowcaseApp.xcworkspace instead?
Another thing worth to try is to install the pods using update mode:
pod install --repo-update
Please let us know how it goes.
Thanks!
Julie from ML Kit team

@miworking Julie thanks for the response. I don't see any file called ShowcaseApp.xcworkspace when I download the project, only the ShowcaseApp.xcodepro. Where do you see this xcworkspace file?

ShowcaseApp.xcworkspace should be created after running pod install --repo-update.

@paulb777 thank you, this seemed to be the problem. I used the following commands to install successfully:
git clone https://github.com/firebase/mlkit-material-ios.git
cd mlkit-material-ios/ShowcaseApp
pod install --repo-update


Add colour stripping support

Currently the ANSI colour codes are stripped out for when routing to a file, but no option is given to strip out the colours otherwise
This can cause some tools like Jenkins to have a messy output, if they don't have ANSI control code support (which Jenkins doesn't have by default, and needs this plugin to add it)

Added in fcd2b71a108f7fa60ed11c072dc3f91e1bd95b56


Wizard Towers

Wizard towers should spawn in magical biomes. Loot should include the affinity tomes from Ars Magica, as well as other Ars Magica related loot. Nothing overly valuable, unless we make it a chore to get, such as by defeating a boss in an arena.

Do we want to gate their loot by age of progression? or are we no longer presuming we can do that?

I want to presume we can, but it might require a mod like Progression or HQM being updated.

I'm tempted to risk progression

Ok, I'm going to start  building tower dungeons if we get some progressive systems working I'll adjust them.
Thinking a simple fortified base w/ elemental spawner for defense, with a series of tower components, and two or three different caps each of with a different spawn'd wizard in residence.

tower components should probably include potion set ups, inlay circles, libraries, nether portals, magical plant gardens, apprentice quarters, processing rooms, ornimental exotic materials studies, any other ideas?

Maybe cages for live specimens, a pool of blood (crude storage of a magical substance), liquid essence fountains...

Ars Magica has been removed, should we still make this?

There are more magic mods than just Ars Magica.+

That was the idea.


Developer Portal Related Updates

Update all the Developer links to point to https://developer.thenewboston.com/ rather than https://thenewboston.com/developer.
Once that is done, remove any existing "Developer Portal" related code (API's, Living Whitepaper, Projects, etc...) from this repository since it has already been moved over to https://github.com/thenewboston-developers/Developer-Portal and we will be using that repo for all developer related example, documentation, and guides from now on.

I think we forgot to move SDKs and Libraries page. I'll create a PR for it. 👍


Source of prebuilt APKs

Where are you getting prebuilt APKs for apps like ReVanced from? They don't officially provide them, mostly because Google stopped the Vanced project because of their prebuilt APKs. This feels a bit sketchy to me.

Thank you for your inquiry about the prebuilt APKs in our app. I appreciate your concern, and I'm happy to provide some clarity on this matter.

APK Sources: Every user can access the APK providers' sources. Simply tap and hold on the provider name in the provider table to view this information.

ReVanced Patched APKs: The providers for these are mainly contributions from active users. I've collected these over time and carefully investigated them to determine which ones I trust the most.

Update Me App's Role: It's important to note that Update Me is not the builder or patcher of these APKs. Our app functions as a collection of links that are scraped daily to provide the most recent mods.

Motivation: As a modded APK user myself, I created this app to simplify the process of finding newer versions of modded apps like YouTube, Spotify, etc. It's a tool designed to make this process easier for anyone who wants to use it.

Transparency: I want to assure you that this is a non-profit project. I do not get paid for this service. Furthermore, the code for Update Me, including the scraping script, is open-source and available for everyone to review and suggest improvements.

I hope this explanation addresses your concerns.


CI and jar downloaded from repository

Hello,
In my teams, we have the dreaded :  "The artifact was found in the local repository but you have explicitly stated that it should be downloaded from a remote one". I know there is already some closed issue on this and, for spring cloud contract dev team, it's a normal behavior. However I want to explain our current problem and why we really don't know how to solve this on our side.
The context is we have a Jenkins CI with shared maven repository. As soon as we build and deploy a contract producer jar, it's pushed on this shared maven repository (on install) and on the nexus remote repository (on deploy). For the consumer, we have set the repositoryRoot (because the stub jar could not be in local repo).
However as soon as we build one consumer, we have the error.
for example, this is the state of the repository for a producer service :
drwxr-xr-x 2 10000 10000 4096 Feb  9 11:06 **20180209-110444-931e7c44b2**
-rw-r--r-- 1 10000 10000  353 Feb  9 11:06 maven-metadata-local.xml
-rw-r--r-- 1 10000 10000 1529 Feb  9 11:07 maven-metadata-nexus-xxx.xml
-rw-r--r-- 1 10000 10000   40 Feb  9 11:07 maven-metadata-nexus-xxx.xml.sha1
-rw-r--r-- 1 10000 10000 1529 Feb  9 11:14 maven-metadata-remote0.xml
-rw-r--r-- 1 10000 10000   40 Feb  9 11:14 maven-metadata-remote0.xml.sha1
-rw-r--r-- 1 10000 10000  253 Feb  9 11:14 resolver-status.properties

the directory contains:
-rw-r--r-- 1 10000 10000      280 Feb  9 11:06 _remote.repositories
-rw-r--r-- 1 10000 10000     2683 Feb  9 11:06 **producer-service-20180209-110444-931e7c44b2-stubs.jar**
-rw-r--r-- 1 10000 10000 47240293 Feb  9 11:06 producer-service-20180209-110444-931e7c44b2.jar
-rw-r--r-- 1 10000 10000    14166 Feb  9 11:05 producer-service-20180209-110444-931e7c44b2.pom

To make the consumer builds correctly and remove the error, we have to delete the repository by hand. After deleting and relaunching the CI for the consumer, it downloads the stubs .... recreate the same 20180209-110444-931e7c44b2 directory which contains now:
-rw-r--r-- 1 10000 10000  193 Feb  9 11:38 _remote.repositories
-rw-r--r-- 1 10000 10000 2683 Feb  9 11:38 **producer-service-20180209-110444-931e7c44b2-stubs.jar**
-rw-r--r-- 1 10000 10000   40 Feb  9 11:38 producer-service-20180209-110444-931e7c44b2-stubs.jar.sha1

For information, the stubs jar is again present with the same size and same SHA (only the file date is of course more recent because it was now downloaded from remote as expected).
So is there a possibility to configure Spring Cloud contract to avoid this problem ?
BTW, if we look ath this line : https://github.com/spring-cloud/spring-cloud-contract/blob/748e512f4d92d67dd6d40e994163788592e7b612/spring-cloud-contract-stub-runner/src/main/java/org/springframework/cloud/contract/stubrunner/AetherStubDownloader.java#L174 it seems to say that if we tell to download repositoryRoot and there is any jar in local repository, it will fail. It seems a bit hard in our context: we want to download it from remote if not present and no error if already present (or even force the download).
Thanks a lot for your time on this matter :)

As you said you're not the first to have this problem. I guess it's high time to make this parametrizable. Obviously, you have to know what you're doing and you take responsibility for it but I guess we should allow an option to disable this check. WDYT about it?

I think it could be a great idea for make our life easier :)
Just to fully understand, why it's not normal from your point view ? (especially compared to the scenario I present you ).

I looked at the code to propose a PR but I think I don't enough skill to really understand and do something interesting :(

For 1.2.x, since I don't want to break the backward compatibility of the API, I've added assertion of

stubrunner.snapshot-check-skip system property
STUBRUNNER_SNAPSHOT_CHECK_SKIP environment variable

if either of them is set then we WILL NOT check if the jar is local or remote. So in Jenkins in each job just set the env var STUBRUNNER_SNAPSHOT_CHECK_SKIP and your builds should stop failing.
The rationale to introduce this change was that when building the project locally, you could have your build passing even though it shouldn't due to the fact that the remote stubs were ignored for some reason, and the local ones where picked. Now you'll be able to switch it off. In master I'll add the standard Spring / Maven / Gradle plugin mechanism to toggle this flag.

No problem. Seems a simple solution to make our life better :)
In which version, will it be available on mvn repository ?

1.2.4.RELEASE - should be out quite soon.

@marcingrzejszczak Thank you for this option! May I know when you want to make this a plugin parameter that can be set in pom?

AFAIR it's already there in 2.0.0.M7 milestone

So its only for 2.x and not for 1.x releases?
  For 1.x (and 2.x too), you can set an env var on the machine, or pass the system property via e.g. surefire https://maven.apache.org/surefire/maven-surefire-plugin/examples/system-properties.html
<project>
  [...]
  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-surefire-plugin</artifactId>
        <version>2.20.1</version>
        <configuration>
          <systemPropertyVariables>
            <stubrunner.snapshot-check-skip>true</stubrunner.snapshot-check-skip>
            [...]
          </systemPropertyVariables>
        </configuration>
      </plugin>
    </plugins>
  </build>
  [...]
</project>

Hey @marcingrzejszczak ,
        <configuration>
          <systemPropertyVariables>
            <stubrunner.snapshot-check-skip>true</stubrunner.snapshot-check-skip>
            [...]
          </systemPropertyVariables>
        </configuration>

Can you say when this fix is available for version 1.2.3?
Will this fix available before 2.0.0 release?
What Spring cloud version is needed to get the 2.0.0 milestones?
Thanks in advance 👍

Can you say when this fix is available for version 1.2.3?

Currently, there's no date - https://github.com/spring-cloud/spring-cloud-release/milestones  . I guess we'll first do 2.0.0 GA and then the 1.2.3 one. But we'll have some internal discussions to maybe release SR3 before Finchley cc @spencergibb @ryanjbaxter @dsyer

Will this fix available before 2.0.0 release?

Answered above

What Spring cloud version is needed to get the 2.0.0 milestones?

Finchley.M8 should have it. In which case you can use the plugin property too.


Excess deaths

First, I must say, these projections are really great.
A number of people are looking into excess deaths to determine when exactly the epidemic really started. This project is using official numbers released by governments (which is fine), but maybe another set of projections can be added using excess deaths data. Are there any plans to implement something like this? It would be interesting to see how this affects the projections.
(This is my assumption asking this question: This project uses death data from countries to estimate infection numbers, then predict effective R values, which can be used to generate projections on these numbers. I might be totally wrong about this, correct me if I am. Releasing the code #2 would be helpful to make it clear what approach is taken here.)

I agree that our projections of reported deaths is an underestimate. There are a lot of existing analysis done on excess deaths, so I recommend you take a look at those. Off the topic of my head, I know the NYT, Financial Times, and The Economist have written articles about it.


bug: [android] getDuration causes MEDIA_ERROR_UNKNOWN

Calling getDuration instantly after loading source causes MEDIA_ERROR_UNKNOWN
See logs: https://github.com/bluefireteam/audioplayers/runs/6538159265
Code to Reproduce
See executing integration tests on android:
https://github.com/bluefireteam/audioplayers/pull/1128
Log Errors
Attempt to call getDuration in wrong state: mPlayer=0x787da258ce90, mCurrentState=4
E/MediaPlayerNative(12460): error (-38, 0)
E/MediaPlayer(12460): Error (-38,0)
E/flutter (12460): [ERROR:flutter/lib/ui/ui_dart_state.cc(198)] Unhandled Exception: MediaPlayer error with what:MEDIA_ERROR_UNKNOWN {what:-38} extra:MEDIA_ERROR_UNKNOWN {extra:0}
E/flutter (12460): #0      MethodChannelAudioplayersPlatform._doHandlePlatformCall (package:audioplayers_platform_interface/method_channel_audioplayers_platform.dart:175:9)
E/flutter (12460): #1      MethodChannelAudioplayersPlatform.platformCallHandler (package:audioplayers_platform_interface/method_channel_audioplayers_platform.dart:148:7)
E/flutter (12460): #2      MethodChannel._handleAsMethodCall (package:flutter/src/services/platform_channel.dart:404:55)
E/flutter (12460): #3      MethodChannel.setMethodCallHandler.<anonymous closure> (package:flutter/src/services/platform_channel.dart:397:34)
E/flutter (12460): #4      _DefaultBinaryMessenger.setMessageHandler.<anonymous closure> (package:flutter/src/services/binding.dart:380:35)
E/flutter (12460): #5      _DefaultBinaryMessenger.setMessageHandler.<anonymous closure> (package:flutter/src/services/binding.dart:377:46)
E/flutter (12460): #6      _invoke2.<anonymous closure> (dart:ui/hooks.dart:190:15)
E/flutter (12460): #7      _rootRun (dart:async/zone.dart:1426:13)
E/flutter (12460): #8      _CustomZone.run (dart:async/zone.dart:1328:19)
E/flutter (12460): #9      _CustomZone.runGuarded (dart:async/zone.dart:1236:7)
E/flutter (12460): #10     _invoke2 (dart:ui/hooks.dart:189:10)
E/flutter (12460): #11     _ChannelCallbackRecord.invoke (dart:ui/channel_buffers.dart:42:5)
E/flutter (12460): #12     _Channel.push (dart:ui/channel_buffers.dart:132:31)
E/flutter (12460): #13     ChannelBuffers.push (dart:ui/channel_buffers.dart:329:17)
E/flutter (12460): #14     PlatformDispatcher._dispatchPlatformMessage (dart:ui/platform_dispatcher.dart:589:22)
E/flutter (12460): #15     _dispatchPlatformMessage (dart:ui/hooks.dart:89:31)
E/flutter (12460):

Platforms

Android

OS: android
OS version: system-images;android-30;google_apis;x86
Device: emulator
flutter version: 3.0.0
audioplayers version: master
release or not release: test

Is there any update on this issue as I'm facing the same issue, can be produced at multiple situations. If open player and navigate back before player is initialized fetching complete stream produces same error, play then pause/stop before all stream content is fetched produces same issue.

Thanks, it did resolved the error in one place which is when playing/pausing before buffering. But it is still occur in below scenario,
If you navigate to audio page and click on play button, audio will start to  buffer, if you navigate back audio player to previous page before audio file is fetched, it throws exception. This is not much a problem but it happens.

@Usama-Ishfaq101 can you raise a new issue, if it still occurs, with as much detail as needed?


add support for EPOLL_EXCLUSIVE

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

#778

official commit: http://hg.nginx.org/nginx/rev/6acaa638fa07


[fix] opendata: support subdir

Coverage increased (+0.002%) to 79.497% when pulling 0d5667755d5e3be31b626ee542dacd8fbf6674dc on tany:fix-subdir into 7248c780327973e55a001f4760981b28be176817 on shirasagi:master.


Add gradle tasks related to zipping sample projects

@m4gr3d mentioned that having the vendor repo's sample projects available on the asset library would be super handy for users of the XR Editor. I think it makes most sense to host the zips of these in the vendor repo releases. This PR adds some gradle tasks to generate/clean those.
I'll add the zipped projects to the 3.0.1 release if we agree on this approach.

Fixed the zipSamples task to also include the root directory in the zip, rather than just the contents. I've attached zips of the samples to the 3.0.1 release.


OCSP responder certificates are not actually linted, to date (fix needed)

I think I found a problem in an already existing lint, and a more general problem in a core component of Zlint.
Let me start from the more general problem. I think we all agree that it is (would be) a good thing to be able to also lint OCSP responder certificates, since there are specific requirements for them in the CABF baseline requirements (all of them). For a start, an OCSP responder cert must contain the ocsp-nocheck extension, so I was happy to see that there already exists a lint [1] that checks for this. However, I did some tests with real OCSP responder certs, both good and bad, and I found with dismay that that lint is actually never invoked (and therefore it's as if it didn't exist). After a bit of digging, I understood that that no OCSP responder cert is really linted by Zlint, to date, for the simple reason that a lint that refers to the BRs is considered not applicable (NA) if the certificate to be linted is not a ServerAuthCert. This is the consequence of this code excerpt from lint/base.go:
func (l *CertificateLint) Execute(cert *x509.Certificate, config Configuration) *LintResult {
	if l.Source == CABFBaselineRequirements && !util.IsServerAuthCert(cert) {
		return &LintResult{Status: NA}
	}

The problem stems from the fact that, normally, an OCSP responder cert does NOT contain the serverAuth EKU (even less the AnyKeyUsage EKU), which is the test done by util.IsServerAuthCert(). And besides, that is forbidden since CABF BR 2.0.0.
The same check is re-done (uselessly) in the lint [1], and would cause the lint to be skipped regardless of the above issue in lint/base.go.
I think this problem should be fixed soon.
Does anyone have any suggestions? Otherwise I can see if I can come up with something....

[1] https://github.com/zmap/zlint/blob/master/v3/lints/cabf_br/lint_ocsp_id_pkix_ocsp_nocheck_ext_not_included_server_auth.go

Good catch @defacto64
Right, so this is tricky for quite a few reasons.

CABF/BR, in general, operates on server certificates so we certainly do not want to remove the check from the framework as this would imply that every individual lint would be responsible for performing this check themselves.
The requirement is, itself, quite awkward. It is a requirement on an OCSP certificate in a sea of server certificate requirements.
Indeed, if I do a case insensitive grep for ocsp I find lint_ocsp_id_pkix_ocsp_nocheck_ext_not_included_server_auth.go and possibly lint_ocsp_id_pkix_ocsp_nocheck_ext_not_included_server_auth.go.

We have hundreds of lints for server certificates and one-to-two (that I saw) lints for OCSP certificates.
I tried a quick-and-dirty hack that says okay, fine, they all have to be server certificates EXCEPT this one lint.
if l.Source == CABFBaselineRequirements {
    _, ocspCertLint := l.Lint().(*cabf_br.OCSPIDPKIXOCSPNocheckExtNotIncludedServerAuth)
    if !util.IsServerAuthCert(cert) && !ocspCertLint {
        return &LintResult{Status: NA}
    }
}

This, however, is an import cycle as the cabf_br package refers to the lint package for items such as lint.RegisterLint. lint.Metadata, lint.Result, and so on.

Perhaps I will have to think on it further, but off the top of my head in order to get this lint operational our options include.

Create a sub-category (cabf_br::ocsp).
Create a new (optional) interface wherein an individual lint could choose to override the framework's effective check.

I will say that I (personally) have no appetite for #1 as it creates a whole new category for, effectively, a single lint.
#2 is somewhat more appetizing as I can see it being used by other lints with similar awkward nuances. Something perhaps akin to...
type Overrider interface {
	LintInterface
	OverrideFrameworkCheck(c *x509.Certificate) *LintResult
}
...
...
...
override, ok := l.Lint().(Overrider)
if ok {
	result := override.OverrideFrameworkCheck(cert)
	if result != nil {
		return result
	}
} else {
	if l.Source == CABFBaselineRequirements && !util.IsServerAuthCert(cert) {
		return &LintResult{Status: NA}
	}
	if l.Source == CABFSMIMEBaselineRequirements && !((util.IsEmailProtectionCert(cert) && util.HasEmailSAN(cert)) || util.IsSMIMEBRCertificate(cert)) {
		return &LintResult{Status: NA}
	}
}

I've hacked up something (with terrible names and little consideration for implications) at #842.

I think I see how the thing works. Please correct me if I am wrong.
If a linter implements the Overrider interface, the framework check is skipped.
However, in this case I understand that the linter can perform its job either within the OverrideFrameworkCheck function itself (by returning a LintResult) or return nil and then do its job within the usual Execute function. Right?
If so, what's the use of this double option? Wouldnt it suffice to just check if the linter implements the Overrider interface, skip the the framework check in case, and let the linter do its job via the Execute function alone, as usual?

That is certainly an option! I admit that I didn't put too much thought into the details just yet, just spit balling on ideas that could accomplish the goal without having to tear up too much just for one (or several) lints.
type AGoodAndDescriptiveName interface {
    func Override()
}

...
...
...
if _, ok := lint.(AGoodAndDescriptiveName); !ok {
    // framework check
}
lint.Execute(cert)

Hey @christopher-henderson, I'm curious what other cases could be solved by this interface check. I'm wondering if a bool or other flag value in the CertificateLint struct could accomplish the same thing for this one lint by simply returning nil. Something to consider I think unless there is good reason as you've metnioned in a previous comment. The main reason is that I am not seeing that this interface accomplishes anything that having a flag to bypass the NA check and modifying CheckApplies can't accomplish. Having an additional interface and optional method just seems more complicated than its worth to me. Let me know if I am missing anything here, since otherwise it seems like your solution will do the trick.

@toddgaunt-gs adding a default-false field to CertificateLint is indeed another option.

Yes, a default-false booean in LintMetadata seems simpler. Could be like follows:
SkipFrameworkCheck bool
Then, the framework check in base.go could be modified like this:

func (l *CertificateLint) Execute(cert *x509.Certificate, config Configuration) *LintResult {
    if !l.SkipFrameworkCheck {
        if l.Source == CABFBaselineRequirements && !util.IsServerAuthCert(cert) {
            return &LintResult{Status: NA}
        }
        if l.Source == CABFSMIMEBaselineRequirements && !((util.IsEmailProtectionCert(cert) && util.HasEmailSAN(cert)) || util.IsSMIMEBRCertificate(cert)) {
            return &LintResult{Status: NA}
        }
    }
    lint := l.Lint()
    err := config.MaybeConfigure(lint, l.Name)
    if err != nil {
	return &LintResult{
		Status:  Fatal,
		Details: err.Error()}
    }
    ...and so on...

How about that?


Retire rules that are better suited for Chefspec FC009/FC037/FC038

FC009/FC037/FC038 detect typos/mistakes in code by dumping every possible method for each version of chef and then comparing cookbook code against that list. This is flawed for many reasons:
Requires constantly updating chef metadata
Doesn’t work if you’re using an old version of foodcritic but new functionality from a new chef release
Fails on the windows resources that are in the cookbook
This test made sense when it was developed, but at this point a converge of the recipe using Chefspec is far more likely to find the issue we’re hoping to discover here
Signed-off-by: Tim Smith<EMAIL_ADDRESS>

So this actually requires a lot of fundamental reworking that I'm not prepared to do now (or maybe ever). This might just stick around until we one day port these rules all over to rubocop


Line coordinates can be None

There's a condition where .lly or .ury can return None, causing errors during calculations:
  File ".../freki/readers/base.py", line 221, in blocks
    line_dy = coefficient * self._line_dy()
  File ".../freki/readers/base.py", line 194, in _line_dy
    line_diffs = [a.lly - b.ury for a, b in zip(lines[:-1], lines[1:])]
  File ".../freki/readers/base.py", line 194, in <listcomp>
    line_diffs = [a.lly - b.ury for a, b in zip(lines[:-1], lines[1:])]
TypeError: unsupported operand type(s) for -: 'NoneType' and 'float'

(I've also seen it the other way around: float + None)

This is likely because it's possible to have Lines without tokens, e.g. in freki.base.tokens_to_lines().

It's still possible to have None as a coordinate, but the code that creates Lines seems to have been fixed (e.g. it only creates a line if there's a non-empty collection of tokens)


[incubator/ethereum] Add Chart for Deploying Private Ethereum Network

PR adds chart to incubator for deploying a private Ethereum network to Kubernetes (fixes #2088).
The chart is comprised of 3 components:

Bootnode (ethereum/client-go:alltools-v1.7.3)

Used for Geth node discovery. Geth nodes will connect to the bootnode to initially find their peers.
This chart only supports running 1 replica which obviously isn't HA. If we wanted more replicas, we'd need to use something like this https://github.com/jpoon/bootnode-registrar, but want to limit amount of custom code needed for this generic chart.

EthStats (ethereumex/eth-stats-dashboard:latest)

Ethereum Network Statistics.
Geth nodes will report its statistics to the dashboard
Accessable through a k8s service (default: LoadBalancer)
Geth only supports reporting status to ONE EthStats, so replica count is NOT configurable for this deployment

Geth (ethereum/client-go:v1.7.3)

Geth is deployed in two different manners: miner, transaction
Miner nodes are meant for mining and will consume all container's CPU
Transaction nodes have mining disabled and are meant to be used to respond to API (websocket/rpc) queries. By default, these are exposed with a ClusterIP

After deploying this chart, you will end up with something like this:

For general instructions on how to deploy a private Ethereum network, see this.

/ok-to-test

/lgtm

As mentioned in my last comment, as we no longer have any keys in the values.yaml the default deployment will fail which is what the tests are seeing: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/charts/3220/pull-charts-e2e/5033/

@unguiculus @mattfarina, what should we do about the failing test? see my last comment about why its failing. leave it as is?

You need to rework the chart. It can't be merged as long as CI doesn't pass.

Before I proceed with re-working the chart, I just wanted to walk-through my thinking.

Geth requires publicKey + privateKey + accountSecret. Without these values defined, it will exit with an error code.
As per CR comments, it's clear no keys should be checked in.
CI needs to pass which means the Chart needs to be successfully deployed

It seems then that the only option is to add a series of if undef geth.account.publicKey || eth.account.privateKey || geth.account.secret then NOP to the start-up scripts. IOW, I wouldn't actually start-up Geth.
Is that OK?

Ping @unguiculus

You need to do it as you suggested.

@jpoon is it possible to generate a random keypair and secret if none is provided? Would this be a good way to make the tests pass?

@linki that would be optimal but I couldn't figure out a way to do that with Helm.

@jpoon @linki newer versions of sprig (included in Helm) support generating private keys: http://masterminds.github.io/sprig/crypto.html

Ooohhh that is helpful. Thanks @prydonius. Do you know of any easy way to extract the public key from the genPrivateKey fx?
Aside: I see you have now moved to SF! Hope things are all well since OpenHack @ AMS.

@jpoon hmm, not sure actually, I haven't actually used this myself! I'm guessing this might just be for generating self signed certs (the Service Catalog chart uses this). @technosophos @mattfarina any ideas if it's possible to get the public key here?

Aside: I see you have now moved to SF! Hope things are all well since OpenHack @ AMS.

Hah, actually I'm still in London - just never got around to updating my GitHub profile ;). Might be moving back sometime in May, though! Hope you're doing well!

@unguiculus thank you for adding support for test values (https://github.com/kubernetes/charts/pull/4157)! Updated PR to add test keys and clarify documentation on how to generate those keys.

@jpoon @unguiculus do you want to move this directly into stable? Doesn't look like there's any reason not to?

/lgtm

What's the criteria for stable? I can move it over there if you both agree.

@jpoon it should meet all the technical and documentation requirements listed here: https://github.com/kubernetes/charts/blob/master/CONTRIBUTING.md#technical-requirements. In particular, "Do not leverage alpha features of Kubernetes", as incubator used to be used for a lot of charts implementing PetSet ;).

Sweet. Moved it over to stable.

helm create with Helm 2.8+ gives you a better _helpers.tpl and adds a chart partial. Would you mind updating?

@unguiculus done.

/lgtm

/hold cancel


Tracking of Calendar items / appointments doesn't seem to be working on the latest version of Outlook Desktop.

A Client of ours recently switched over from the COM Outlook add in to the new style. Tracking emails is working correctly for them.
However, they do not seem to have the 'Add-in > Dynamics' button visible from anywhere on the calendar or new appointment windows to make the Dynamics flyout appear, therefore they are unable to track Calendar entries this way.
Is there a back-end configuration we are missing to get this working again for them? I'm not sure what I may be missing, I searched all around and tried to customize the Ribbon. I got the Add-in > Dynamics button to appear on the main calendar screen, but it was greyed out so it still didn't cause the flyout to appear.
Just let me know if I may be missing something, thanks!
-Tyler

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

ID: c077b498-3ecf-1edb-6393-4a8dc65190c5
Version Independent ID: 613d3b32-bf86-01f8-e339-31ba17573432
Content: Link and track an email or appointment to a specific row in your app (Dynamics 365 apps)
Content Source: ce/outlook-app/User/track-message-or-appointment.md
Service: dynamics-365-cross-app
GitHub Login: @mduelae
Microsoft Alias: mkaur

Any Update on this? Our client is really wanting to know how to set regarding on calendar items from Outlook using the latest Web CRM Plugin.
-Tyler

Thanks for contacting us. Unfortunately, we're unable to handle Support requests for the product here. This is only to report issues with the help topics.
To contact Support, consider one of the options described here: https://docs.microsoft.com/dynamics365/get-started/support/
Closing this issue.


update crystal version

this shouldn't be merged into master but pulled into a different branch

Superseded by #10