Inaccurate duration and, therefore, inaccurate progress

Current behaviour
The duration is inaccurate.
Steps to reproduce

Open the fiddle and check the duration. Everything seems right: the value from onDuration matches the duration displayed in the video controls.
Open the same video on Youtube and compare. It has an extra second.

Implications
progress never reaches 1. It gets stuck at 0,9974958217.
Environment

URL attempting to play: https://m.youtube.com/watch?v=2JrkxfDNabk
Browser: Chrome
Operating system: macOS
jsFiddle example: https://jsfiddle.net/7q14u83n/3/

Additional comments
It would be great if we could get the duration in milliseconds, for higher precision.

After doing some digging, I found the Youtube IFrame API. Reading the description for player.getDuration():

Returns the duration in seconds of the currently playing video. Note that getDuration() will return 0 until the video's metadata is loaded, which normally happens just after the video starts playing.

So this is the fault of the Youtube IFrame API. It seems possible to read off the duration of the video from the <video> component itself, and can probably be PR'd.

On further digging, that would require modification of the YT embed script, or asking YouTube to add Access-Control-Allow-Origin * which obviously isn't something anyone should do. I suspect it is impossible to access a more accurate duration, unless YouTube modifies their API to expose a higher accuracy value.

@kaylendog You're right, this is actually a problem with the Youtube IFrame API and unrelated to react-player. My bad. I'm closing the issue here.

I've noticed that after playing a YouTube clip, calling getDuration will give you an accurate duration. If you seek however, then the inaccurate duration comes back and sticks.
Although this is a bit convoluted, you could have a bit of a warm-up sequence before displaying the video where you'd mute, play, and grab an accurate duration in an onPlay callback. Then seek back to start and display the video as normal.


BLOCK_REWARD is a const in Stratum.h

// TODO: update when next Halving
#define BLOCK_REWARD<PHONE_NUMBER>ll

We may forget to update after next halving.

And the timestamp checking.
/* TODO: increase timestamp check before 2020-01-01 */
    if (userId_ > 0 && workerHashId_ != 0 && share_ > 0 &&
        timestamp_ ><PHONE_NUMBER>U /* 2016-07-06 14:55:52 UTC+0 */ &&
        timestamp_ <<PHONE_NUMBER>U /* 2020-01-01 00:00:00 UTC+0 */ &&
        jobTime    ><PHONE_NUMBER>U /* 2016-07-06 14:55:52 UTC+0 */ &&
        jobTime    <<PHONE_NUMBER>U /* 2020-01-01 00:00:00 UTC+0 */) {
      return true;
    }

Maybe we could use GetBlockSubsidy to auto compute the reward.
#include <chainparams.h>
#include "BitcoinUtils.h"

const CChainParams& chainparams = Params();
auto reward = GetBlockSubsidy(blockHeight, chainparams.GetConsensus());

It will no longer need checking timestamp, it will auto update after next halving.

coinbasevalue is a part of getblocktemplate's result. We can use it directly.

How does the LTC pool be built?

I have not tried LTC. Because its POW algorithm is different from Bitcoin, it may not be a simple link and the pool needs to be modified.

How does the ETF pool be built?

The code of supporting Ethereum (ETH) is in review. And how to build or deploy is not determinate.

ying yu tai lei . ni hui da jian etf me ? you mei you etf yuan ma

Sorry, I don't have.

Try fix it at https://github.com/btccom/btcpool/commit/72065532aa2c64235d6d669d6e91009b82cf7641
Not tested. I don't know if this will bring a lot of precision loss.

I have tested that the new calculation method will not lead to a difference in the earning of more than 1 satoshi.
When double is converted to an integer, rounding will be used, so there is a difference of up to 1 satoshi.
But the issue will keep open until the above commit was merged by master branch.


Drop gif + png, and redirect png to raster.shields.io

This PR does a few things:

Remove rasterization support from the server. This responsibility is delegated to a raster server which proxies the SVG badges and renders them.
When a raster server URL is configured, 301 redirect all .png badges to the identical URL on the raster server.
https://img.shields.io/npm/v/express.png?style=flat-square ↪https://raster.shields.io/npm/v/express.png?style=flat-square
For configured redirects, redirect to the canonical URL on the raster server.
https://img.shields.io/vso/build/totodem/8cf3ec0e-d0c2-4fcd-8206-ad204f254a96/2.png?style=flat-square
↪https://img.shields.io/azure-devops/build/totodem/8cf3ec0e-d0c2-4fcd-8206-ad204f254a96/2.png?style=flat-square
Redirect the "legacy badge old version" to the appropriate URL on the raster server.
When no raster server is configured (e.g. PRs), render an SVG containing 404 | raster badges not available for all .png badges. (Note that the raster server can be self-hosted; however, this is deferred to a later PR.)
Drop support for jpg and gif which are very infrequently used (see #3112). Render an SVG containing 410 | jpg no longer available.
Remove raster dependencies.
Move the LRUCache code out of the npm package.
A wee bit of refactoring in server.js.

Ref #3631 #3112

Warnings

:warning:

This PR modified package.json, but not package-lock.json - Perhaps you need to run npm install?

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @paulmelnikow!

:book:

Thanks for contributing to our documentation. We :heart: our documentarians!

  Generated by :no_entry_sign: dangerJS against 1cbffcc2b03303051a9c39f72b1fd9cd551c2a37

I've not read over all this, but giving it a cursory look, it seems like you're completely removing raster support from the package/CLI in this PR whereas a couple of weeks ago I think you were looking at leaving support in but converting gm to a peer dependency: https://github.com/badges/shields/issues/3587#issuecomment-504014841
Is that an oversight or has your opinion on raster support changed since we established that its only the CLI that supports them and not the library: https://github.com/badges/shields/pull/3586#discussion_r295802787 ?

I've not read over all this, but giving it a cursory look, it seems like you're completely removing raster support from the package/CLI in this PR whereas a couple of weeks ago I think you were looking at leaving support in but converting gm to a peer dependency: #3587 (comment)
Is that an oversight or has your opinion on raster support changed since we established that its only the CLI that supports them and not the library: #3586 (comment) ?

Ah, right, I forgot about that. Thanks for the reminder! 😝
I'm fine with restoring that code it and keeping it as a peer dep, though another alternative would be to swap in the more modern rasterization lib convert-svg-to-png that's being used in svg-to-image-proxy.
This also touches lru-cache. I don't want to smush your work on v3; not really sure the best way forward with these changes at the boundary of the library.
To keep this smallish, what do you think about my adding the raster capability back, using the new dependency, in a separate PR?

Come to think of it, it wouldn't be so hard to put the raster support back into gh-badges. I could revert the removal of the gm dependency and the lru-cache changes. Pretty much all the other removals (e.g. references to imagemagick in the tutorial) could stay as they are.

I don't think the change to the LRU cache makes any difference because it doesn't affect the public interface (or at least, the documented interface) of the package - its just internals.
The bits that change the documented functionality (i.e: the CLI) are best done in a separate PR targetted at the v3-dev branch (same as I've done with #3586 ).

I just remembered that raster badges are broken in the CLI, which makes this sort of moot, though I reverted it for now. I kept the lru-cache in its new location and removed internal references to it instead, as even if the CLI worked, the cache would be pointless.

I just remembered that raster badges are broken in the CLI

Are they? If I run badge build passed :green .png > mybadge.png it spits out:

Huh, after upgrading imagemagick, this is what I get, which is obviously wrong, though different from what I was seeing when I opened #1788.

Gosh, shall we ship this? 🚀

Working: https://shields-raster-staging.now.sh/badge/foo-bar-blue.png?style=flat-square

Not redirecting correctly: http://shields-staging.herokuapp.com/badge/foo-bar-blue.png?style=flat-square
It's dropping ?style=flat-square and redirecting to a nonsense static badge:
https://shields-raster-staging.now.sh/badge/badge-foo--bar--blue-lightgray.png

Also not redirecting correctly: http://shields-staging.herokuapp.com/npm/v/express.png?style=flat-square

Confirmed fixed in #3659. (If it's not fixed for you, the bad redirects are probably stuck in your cache.)


cs to review

Q
A

Fixed Tickets

License
MIT

A new inspection was created.

The inspection completed: No new issues


Format::new not const fn

I would like to be able to define a nice PREFERRED_FORMAT constant for my project, but mine is ugly because I have to manually list all of the fields. Perhaps v4l::Format::new could be changed to
const fn new(width: u32, height: u32, fourcc: FourCC) -> Self {
    Format {
        width,
        height,
        fourcc,
        field_order: FieldOrder::Any,
        stride: 0,
        size: 0,
        flags: Flags::empty(), // <- used to be Flags::from(0), which isn't const fn
        colorspace: Colorspace::Default,
        quantization: Quantization::Default,
        transfer: TransferFunction::Default,
    }
}

I think this change would make this library much more ergonomic.

Sure, why not. Please put up a pull request and let's take it from there.

Fixed by https://github.com/raymanfx/libv4l-rs/pull/20.


Helm chart | Enable Prometheus metrics for Hubble Relay

Is there an existing issue for this?

[X] I have searched the existing issues

I have installed Cilium via its Helm chart in the kube-system namespace of a kind cluster.
I want to enable Prometheus metrics for the Hubble Relay component.
I have set the hubble.relay.prometheus.enabled field in the values.yaml file to true.
values.yaml
policyEnforcementMode: always
hubble:
  metrics:
    enabled:
    - dns:query;ignoreAAAA
    - drop
    - tcp
    - flow
    - icmp
    - http
  relay:
    enabled: true
    prometheus:
      enabled: true              # appears to have no effect
  ui:
    enabled: true
prometheus:
  enabled: true
operator:
  prometheus:
    enabled: true

What I expected to happen
The hubble-relay pod and the hubble-relay-metrics service should have been annotated in a specific manner, in order to let the Prometheus server know which endpoint has been exposed for scraping.
kubectl get -nkube-system po/hubble-relay-<replica_set>-<pod> -ojson |jq .metadata.annotations
{
  "prometheus.io/port": "9966",
  "prometheus.io/scrape": "true"
}

What happened
Neither the hubble-relay pod nor the hubble-relay-metrics service have been annotated accordingly.
Running the cmd above produces null as a result.
Recommendation
If this is not a misconfiguration on my part, and providing this functionality is no longer relevant for Hubble Relay, perhaps consider removing this field from the values.yaml file, or at least mark it as deprecated to avoid further confusion in the future.
Cilium Version
cilium-cli: v0.15.20 compiled with go1.21.6 on darwin/arm64
cilium image (default): v1.14.5
cilium image (stable): v1.14.6
cilium image (running): 1.14.6

Kernel Version
Darwin Kernel Version 23.2.0: Wed Nov 15 21:53:18 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T6000 arm64
Kubernetes Version
Client Version: v1.29.1
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.27.3

Sysdump
No response
Relevant log output
No response
Anything else?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Perhaps you should add another configuration like the following:
hubble:
  relay:
    prometheus:
       serviceMonitor:
         enabled: true


[next] Maybe handling

NanNew/NanTo/NanGet... respectively v8 will bring in many Maybe(Local) types. While  I understand the basics of a Maybe monad I don't really know how to handle all these. Do I really need to check every maybe if it is empty though I didn't check the commands before these changes? What's the best practise? Or was my code already wrong because I didn't  try catched everything?
Also I cant find anything in v8 docs why these functions may fail.

Scripts and regexes can fail due to bad input. Strings fail due to max length exceeded. Dates fail due to bad input. Buffers fsil due to memory allocation error. They all used to return empty handles in these cases, handles that needed checking. So yes, your old code was technically wrong. V8 now enforces this check on all results from functions that may fail. Think of it as an explicit contract for null checking.
On May 29, 2015 11:13:38 AM EEST, "Mathias Küsel"<EMAIL_ADDRESS>wrote:

NanNew/NanTo/NanGet... respectively v8 will bring in many Maybe(Local)
types. While  I understand the basics of a Maybe monad I don't really
know how to handle all these. Do I really need to check every maybe if
it is empty though I didn't check the commands before these changes?
What's the best practise? Or was my code already wrong because I didn't
try catched everything?
Also I cant find anything in v8 docs why these functions may fail.

Reply to this email directly or view it on GitHub:
https://github.com/nodejs/nan/issues/367

Ok thanks and what about the To..Converters? If I checked e.g an argument with Is...() then I can safely do ToLocalChecked()? And why does the Object->Has() returns a Maybe, what can fail by checking if an Object has a property? Looks like maybes everywhere and writing addons will end up in a checking tangle.

Yes, if you are confident the check will pass, you can do a ToLocalChecked. Object->Has returns a
If the Maybe is nothing or the MaybeLocal is empty, it means that the API call either threw an exception or an exception was already pending. For Object->Has, I believe it can fail if you supply a null context.
Yes, that is how it will be.

Null context would probably a NAN error because the context is hidden, so Has should be safe. Ok thanks for your help. Maybe a small Maybe handling section in the docs would be great but maybe I am the only one having some issues with this ;)

For Object->Has, I believe it can fail if you supply a null context.

v8::Object::Has() does a regular property lookup that consults accessors in the prototype chain.  That means it calls into JS code if for example the property is a JS getter.
If you don't want that, there's v8::Object::HasRealNamedProperty().  It follows the prototype chain but won't call accessors.
It can still fail if there is an already pending exception, that's why it has a Maybe<bool> return value.


The described hierarchy differs from sample screenshots

I seems the bones drawn for eyes and ears in the sample app use a different hierarchy.

Dokumentdetails
⚠ Bearbeiten Sie diesen Abschnitt nicht. Er ist für die Verknüpfung von docs.microsoft.com zum GitHub-Artikel erforderlich.

ID: bfd96838-87c8-c27e-f8ee-a2db651ba463
Version Independent ID: ab4d754c-e83f-7d20-cd8c-690033684406
Content: Azure Kinect body tracking joints
Content Source: articles/kinect-dk/body-joints.md
Product: kinect-dk
GitHub Login: @qm13
Microsoft Alias: quentinm

Hi @PixelPartner Thanks for reaching out. Would you please provide a little more detail so I can pass your feedback to the content author?

Hi @PixelPartner Which sample app are you referring to? and how do they differ?

@PixelPartner Since we did not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Jruby 9k

Prep jruby-9k and reduce size of overall plugins

@mkristian I hadn't noticed this PR. I've been working on this same thing at https://github.com/torquebox/jruby-maven-plugins/pull/119. Everything is green now on java 11, and jruby 9.2. I dropped support for stuff older than that, because IMO opinion this repo seems virtually unmaintained so we should aim just for the latest stable versions. Still need to fix some stuff that I skipped, but it's looking good I believe.

@deivid-rodriguez yes, I just saw you PR
never mind. in the end I wanted to drop a few things. maybe I just pick your branch and drop what I wanted to drop ? I mean make small PRs against your branch . . .

The branch is not really ready. I think maybe better if you first drop what you want to drop, then I can rebase this to fix the rest of the stuff.

ok - I make a version-2 branch and drop things, and bump to 2.0.0-SNAPSHOT
next I wanted to replace all these http://rubygems-proxy.torquebox.org/ with mavengems wagon at least in the integration tests.

Sure. Why not master though, if I may ask?

habit - but I can do it on master. np

@deivid-rodriguez any ways merge this branch to master now

Awesome thanks! I'll rebase this on top of your changes and get it ready :+1:.

I'm not sure whether this is still relevant. In #126 I have continued to migrate to latest JRuby plus latest mavengem, as part of an overall push to update the JRuby/Maven stack (but also to address the v1/dependencies shutdown).

The update to JRuby 9k happened long ago, and in #126 I updated JRuby to <IP_ADDRESS>, but there are other parts here that could be re-applied in 3.0.1.


how to generate render_demo.gif

Hi, thanks for your nice work. Could you please tell me how to create render_demo.git to display the changes made during training?

Just render every few iterations.

In addition, the poses used in the demo are given here.


Existing stream

Motivation:
Explain here the context, and why you're making that change.
What is the problem you're trying to solve.
Modification:
Describe the modifications you've done.
Result:
Fixes #.
If there is no issue then describe the changes introduced by this PR.

Updates? Need this feature. :-|

Let me close this... People should just use Http2ChannelDuplexHandler.newStream()


various documentation changes and corrections

Labels
norelease
Introduction
Minor documentation chagnes
Changes
In addition to some minor doc corrections, this PR adds additional plotting to some of the examples.
Behavior
In the examples, scenarios will now render the initial layout, in addition to rendering the steady_state amplitudes. Some examples that require numpy now explicitly import it for completeness.

Codecov Report
Patch and project coverage have no change.

Comparison is base (5bd680e) 73.38% compared to head (b982abf) 73.38%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #111   +/-   ##
=======================================
  Coverage   73.38%   73.38%
=======================================
  Files          27       27
  Lines        2033     2033
=======================================
  Hits         1492     1492
  Misses        541      541

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Missing values raise DecodingRequiredError

There are some VINs I've ran across where the make is not available after decoding, which would raise this exception. But even more prevalent is if you are decoding a gasoline car, electrification level will be None raising this:
https://github.com/davidpeckham/vin/blob/c79f2820fee04669df5079c4b5cb6be2983521b8/src/vin/__init__.py#L261-L263

thanks!


How to add parameter to select GPU at runtime?

Hi,
how do we add a command line parameter to the select the GPU at run time, especially on amulti gpu machine?
I tried adding
@action.command()

@click.option('-g', '--gpu', help='select gpu', default=1, required=true)
def select_gpu(gpu):
    os.environ["CUDA_VISIBLE_DEVICES"]=gpu

I tried to add a similar code block for train_evaluate_predict_pipeline and pass the gpu parameter
but i keep getting invalid option during runtime. I know its not the package issue, but the documentation did not help either

I usually do it just by going along these lines:
CUDA_VISIBLE_DEVICES=1 neptune run -- train_evaluate_predict_pipeline -p fasttext_gru
and for multigpu you just do:
CUDA_VISIBLE_DEVICES=1,2 neptune run -- train_evaluate_predict_pipeline -p fasttext_gru
I haven't tried multigpu for this project yet.
Also apart from the documentation we have quite a vibrant community here https://community.neptune.ml/
drop your issue there and I am sure someone will help.

@setuc Also, you can do $ export CUDA_VISIBLE_DEVICES=1, to select particular GPU, for entire terminal session.


connection.execute returns strings for timestamp fields in postgres under rails 4.2

Under Rails 4.2 timestamp fields are being returned as strings:
Loading development environment (Rails 4.2.6)
[1] pry(main)> fp = FuelPurchase.connection.execute("select created_at from fuel_purchases limit 1").first
   (3.0ms)  select created_at from fuel_purchases limit 1
=> {"created_at"=>"2015-12-18 08:18:45"}
[2] pry(main)> fp["created_at"].class
=> String
[3] pry(main)> fp = FuelPurchase.connection.execute("select * from fuel_purchases limit 1").first
   (1.0ms)  select * from fuel_purchases limit 1
=> {"id"=>48028535,
 "vehicle_id"=>765,
 "transacted_at"=>"2015-11-19 11:24:00",
 "vehicle_mileage"=>10876,
 "natural_units"=>#<BigDecimal:29ea5e0,'14.12',4(8)>,
 "gge_equivalent"=>#<BigDecimal:1c459c28,'14.12',4(8)>,
 "ghg_estimate"=>#<BigDecimal:6ffdbeef,'125.1283336',10(12)>,
 "fuel_station_id"=>837,
 "created_at"=>"2015-12-18 08:18:45",
 "fuel_payment_type_id"=>11,
 "fuel_type_code_id"=>5,
 "has_missed_opportunities"=>"f",
 "transaction_hidden"=>"f",
 "data_load_organization_id"=>3}

Under Rails 4.0.13 they were returned as Time objects:
Loading development environment (Rails 4.0.13)
[1] pry(main)> fp = FuelPurchase.connection.execute("select created_at from fuel_purchases limit 1").first
   (2.0ms)  select created_at from fuel_purchases limit 1
=> {"created_at"=>2015-12-18 08:18:45 UTC}
[2] pry(main)> fp["created_at"].class
=> Time
[3] pry(main)> fp = FuelPurchase.connection.execute("select * from fuel_purchases limit 1").first
   (5.0ms)  select * from fuel_purchases limit 1
=> {"id"=>48028535,
 "vehicle_id"=>765,
 "transacted_at"=>2015-11-19 11:24:00 UTC,
 "vehicle_mileage"=>10876,
 "natural_units"=>#<BigDecimal:4910afdf,'14.12',4(8)>,
 "gge_equivalent"=>#<BigDecimal:764db16c,'14.12',4(8)>,
 "ghg_estimate"=>#<BigDecimal:45cb5307,'125.1283336',10(12)>,
 "fuel_station_id"=>837,
 "created_at"=>2015-12-18 08:18:45 UTC,
 "fuel_payment_type_id"=>11,
 "fuel_type_code_id"=>5,
 "has_missed_opportunities"=>false,
 "transaction_hidden"=>false,
 "data_load_organization_id"=>3}

When updating to 4.2 this will obviously break anything in existing code expecting a Time object.
It looks like other data types (integer, big decimal) are being returned as the expected data type under 4.2.6. Booleans seem to exhibiting the same problem in 4.2.6 vs 4.0.13 as well.
We're seeing this with versions 1.3.17 and 1.3.20 of the adapter.

It looks like this was possibly an intentional change in behavior for Rails 4.2 in activerecord-jdbc-adapter v1.3.18 (see 07c646968922bebcbc4bdb07b33beab2a971c5bb). Results from ActiveRecord models will still get typecast as datetimes and booleans by functionality built into ActiveRecord. However, for any raw queries against the connection adapter that don't involve ActiveRecord (eg, connection.select_all or connection.execute), these now return strings for datetimes and booleans by default under Rails 4.2 and activerecord-jdbc-adapter.
You can restore the pre-4.2 typecasting functionality for raw queries by enabling these options (in a file like config/initializers/arjdbc.rb):
ActiveRecord::ConnectionAdapters::PostgreSQLJdbcConnection.raw_date_time = false
ActiveRecord::ConnectionAdapters::PostgreSQLJdbcConnection.raw_boolean = false

However, this does affect all queries, including normal ActiveRecord results (not just the queries your explicitly making on the raw connection). I'm not exactly sure what the differences in typecasting between ARJDBC's implementation and ActiveRecord's built-in handling would be.


PermissionDispatcher works not properly on my RedMi Note4,But it's normal on HuaWei (android 7.0)。

I downloaded your PermissionsDispatcher project and build it ,but when I installed the smple app in my RedMi Note 4 (android 6.0),I found it not work properly.So I bought a HuaWei ,it worked properly.
RedMi Note4:
onCameraNeverAskAgain(just this method called )
huawei nova:
onContactsDenied:
showRationaleForContact:
showRationaleDialog:
onContactsDenied:
showRationaleForContact:
showRationaleDialog:
showContacts:
showContacts:

Does the app call MainActivityPermissionsDispatcher.showCameraWithPermissionCheck(MainActivity.this);?
https://github.com/permissions-dispatcher/PermissionsDispatcher/blob/master/sample/src/main/java/permissions/dispatcher/sample/MainActivity.java#L26

Could we get the sample?


Hello COM & Resize

Thank you for your feedback, I'm on it

All the changes have been implemented, please let me know if I missed something or there's anything else to change


[#126126973] Allow STS creds to be used to bootstrap

What
Story: Ensure all AWS IAM accounts have MFA enabled
We need to allow short-lived credentials to be used in order
to require MFA for aws users.
See https://www.pivotaltracker.com/story/show/126126973 https://www.pivotaltracker.com/story/show/136052945 and  https://www.pivotaltracker.com/story/show/136052607
The sts-generated session token needs to be passed to vagrant.
The concourse atc password can no longer be generated from
aws creds, since they are no longer static but may change each day
when short-lived credentials are regenerated.
For the bootstrap pipeline, we can use a static atc password, since the
only access is via ssh - the concourse is not exposed to the
public internet. But instead of using the AWS key as before, we now use
the AWS UserId.
We explicitly separate the two concourse passwords to make this
easier to understand and maintain in future.
How to review
Deploy a new env using the bootstrap pipeline.
Check that the concourse lite and deployer concourse passwords work as you expect.
Who can review
Anyone, but it might be nice to get a quick once-over from @alext since he's doing other changes in this area.
Note: This should only be merged after the work to migrate permanent environments to use the pass-bootstrap pipeline has been deployed.

@alext
I fixed the readme.
As discussed, we think the hacky yml 'parsing' in bash will be OK for now since we have Vault/a.n.other secret passing mechanism in the backlog.
We need to applied whatever migration is needed to move permanent envs onto the paas-bootstrap pattern before applying this change.

rebased against master following work related to migrating paas-cf to paas-bootstrap

This is ready for review again.

LGTM now. Merging


Detroit - Resources Translations

Resources translations in purple
https://docs.google.com/spreadsheets/d/1KmIs93OKQIDsKyay90MLWmItLVBCyAytJJ8s5p-_Zm8/edit#gid=290561964

Covered what was there, will handle missing Arabic in another issue


Open link in a background tab?

Version

[x] Version 1
[ ] Version 2

My Problem
In Safari 11.1.2, when I use Shift+F followed by the link hint to open a link in the new tab, the browser immediately switches to the new tab. Is there a way to open a link in a new background tab instead?
Thanks! :)

Hi. We're using window.open() for opening a tab, but the Safari docs say that if we use their openTab() we can decide on whether to open in background of foreground.
I agree that it should be configured, or just let background be default. Personally I think background feels more natural.

I believe this is fixed with version 2.0.3. At least, shift+f works for me in Safari 13.0.1 on Mojave with Vimari 2.0.3..

Thanks @akrabat, I think you're right. Will close this for now.


Release/2023 03 21

Pulls the following commits from dev into main

0cfc21f7e - fix: user export fixes (#1600)
5be0b22c5 - fix: resolve bugs from bash (#1597)
c01be416b - fix: change min/max rent inputs from number to text with only numbers (#1599) <Krzysztof Zięcina>
33b33c3ef - fix: add descriptive alt tags to listings images (#1587)  <Krzysztof Zięcina>
a4744fe4f - fix: add aria label to table (#1585)
3426a5ffd - 1525/user access issue (#1592)
0fb7f74c6 - fix: remove the due date question (#1584)
1485118dc - fix: add aria label to min/max rent fields (#1582)  <Krzysztof Zięcina>
b7c20cc6c - fix: listings export clean up (#1590)
8926d3d0f - feat: listing export (#1548)
cb1d25f1b - feat: add user csv export (#1560)

Still reviewing but noticed this tiny discrepancy in alert box colors and wrote up an issue here: #1603

Also only other thing to note that I've found is that it seems that the dev and staging environments are missing the cloudinaryCloudName env variable. Assuming this is intentional, but just wanted to call out that paper application links are still working locally for me!

@ColinBuyck thanks for catching that! Can we go with the format on the listings export, including the time zone, please?

LGTM 🎬 as long as the cloudinaryCloudName env variable will be pulled in for Prod. On Heroku, I'm seeing CLOUDINARY_NAME with the desired value but no CLOUDINARY_CLOUD_NAME as the code has always referenced. Am I correct in assuming that this is just outdated and previously unused since no part of the backend has required CLOUDINARY_CLOUD_NAME before?

@ColinBuyck, yeah it looks like that value has only ever been used by the front ends (it's not used by the backend in core). I updated the variable in staging and dev. And will do the same for prod before the release. good catch!

The linting error is from these changes, in the future we might have to add md files to the prettier ignore


Set the user-agent in the BQ storage client.

This change modifies the code which instantiates BigQuery storage client
objects to set the user-agent string at creation time. The user-agent
string specified here is merged with the default client user-agent
string (per https://github.com/googleapis/gax-java/issues/614).

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

Run Java PostCommit

Run Java PreCommit

R: @chamikaramj

This looks good to me. It seems that you force-pushed and lost the previous test executions. I'll rerun JAva postcommits.

Run Java PostCommit

Thank you. Merging.


Importing an exported "declare const" doesn't work

Bug Report

🔎 Search Terms
I searched all over. I eventually found this stackoverflow but it's unanswered so I added a bounty...
https://stackoverflow.com/questions/68133038/how-to-export-a-declared-external-value-as-a-named-export
🕗 Version & Regression Information
tsc Version 5.0.4
⏯ Playground Link
Playground link doesn't work due to this requiring multiple files.
💻 Code
This code works:
declare const ThisReallyExists: string
console.log(ThisReallyExists)

Output:
This global variable really exists, it is just in a mysterious place outside the code
This code compiles but doesn't work:
stuff.d.ts
export declare const ThisReallyExists: string

main.ts
import { ThisReallyExists } from "./stuff"
console.log(ThisReallyExists)

Output:
Could not load stuff.js no such file or directory
This is because stuff.d.ts gets removed during compilation but the import does not.
This code WOULD work if it were able to compile.
stuff.d.ts
export declare const ThisReallyExists: string

main.ts
import type { ThisReallyExists } from "./stuff"
console.log(ThisReallyExists)

Output:
tsc: ThisReallyExists cannot be used as a value because it was imported using 'import type'
🙁 Actual behavior
You are forced to inline all your declare const statements. export declare const doesn't work.
🙂 Expected behavior
Code with export declare const is able to be built.

There's import type can we maybe add import global or something?

I don't see a bug here. A .d.ts file declares types for objects that exist already at runtime, but if it doesn't really exist (no stuff.js) then your code does not match reality. Import type does not work because you're trying for import a value.

@MartinJohns declare const isn't a value, it's a typescript fiction. It can't be actually imported at runtime, just like a type can't be actually imported at runtime.
export declare const ThisReallyExists: string gets stripped by tsc, just as a  export Interface declaration does.
export declare const ThisReallyExists: string can be included in a d.ts file, because it's a pure typescript fiction, just like a export Interface or similar does.
If you put export declare const ThisReallyExists: string into a .ts file, you get basically the same error:
./stuff doesn't export ThisReallyExists

I found a sort of workaround, but it's pretty stupid...
declare const ThisReallyExists: string
export const bogusThing = ThisReallyExists;
export {bogusThing as ThisReallyExists};

Also why is:
export declare const ThisReallyExists: string

Valid typescript, if it can't be imported by anything?
It gets stripped during compilation, so it can't be imported with import, and it's not a type so it can't be imported with import types.

declare is used to describe values that exist at runtime already. TypeScript is not responsible to provide those values at runtime, you are. That's the entire point of declare. If then that value does not actually exist at runtime you end up with an error or course.

Yes I am well aware of that.
Declare is working fine. What's not working fine is trying to encapsulate it into a seperate file.

It's unfortunately pretty tricky to give a "real world" example that involves declare, but if someone can provide an example that uses declare, I can easily change it into an example that shows that export declare const is not working.

I can't really say more than that this is working as intended and that you don't seem to understand the purpose of declare.
You're providing type information for a module stuff.js, but then don't actually have such a module at runtime.

Since apparently I don't understand the purpose of declare.
Could you kindly provide a quick example of some code that uses declare export const that compiles and runs?

In this bug report I'm making the bold claim that there is no example where code exports a declare const, and imports it in another file, and that code works.
So if I counter example can be provided then this can be closed.

Have a stuff.js file with this content: export const ThisReallyExists = "abc".
Your .d.ts file says "There will be a module that exports this ThisReallyExists variable", but then you don't actually have such a module at runtime. You're basically lying to the TypeScript compiler.

ThisReallyExists is a global variable that exists outside the code. That's why we need to to use declare...
Lets look at the example in the documentation.
The global variable foo contains the number of widgets present.
/** The number of widgets present */
declare var foo: number;
console.log("Half the number of widgets is " + foo / 2);

That's the example from the documentation.
So is it possible to take this example, and make the first line and the second line in separate files, connected with an import?

The trick is not to import from stuff.d.ts but just to make sure it's part of your compilation.  Also get rid of the export because that tells TS it's a module that needs to be imported at runtime.

You're exporting / importing. Then you're dealing with modules, not with script files that contain global variables.
declare itself has nothing to do with global or not global. It's a way to declare that a value exists outside of your TypeScript code and will be/is provided at runtime (e.g. via a JavaScript file or module). In your example you declare that a module stuff.js will exist that exports a ThisReallyExists value - then proceed to not have such a module at runtime.
If you want to deal with globals, then don't import/export anything. If your .d.ts has export statements and you want to declare a global variable you can do this:
declare global {
    interface Window {
        ThisReallyExists: string;
    }
}

But again, you should not import this. A "global" variable is not to be imported. And again, also here, the value should already exist at runtime. You're telling TypeScript "this value will exist", but nothing in your code makes sure it actually does exist.

The trick is not to import from stuff.d.ts but just to make sure it's part of your compilation.

@fatcerberus interesting. How do you include something in your compilation without importing it?
Of course one way is to have everything in the same file, maybe there's some other way I don't know about though.

How do you include something in your compilation without importing it?

.d.ts are picked up from your source directory(/ies) the same as .ts files.

Any file with no imports or exports is treated as global script.

Ohhhh. This was the missing piece...


MP OpenTelemetry Media push for 2021

When:
Monday, every week
Time:
6:30am- 7am PDT- lets change it to EU time.
Twitter
_Join today's #OpenTelemetryCall to discuss & contribute to the API's technical direction. #MicroProfilers' participation ensures the continued growth & development of a well-governed, vendor-neutral #OpenSource API.
Join: https://bit.ly/calendar-zoom-minutes
#ByCommunityForCommunity #OSS_
Thanks @rstjames!

@aeiras

Let’s fix the name in the card, Ryan.

perfect, Ryan!
Thank you,

set for the year.

Thank you, Ryan!
--- for tracing on this ticket.
MP Community Thread on new space is a wonderful MP communication statement of how strong & beautiful the ecosystem is with feedback and the engagement reaching + 1200 subscribers.


Wrong date parsing when year changes

During scraping a website I encountered this issue:
Dec 14 11:00 is parsed as datetime.datetime(2015, 12, 14, 11, 0) whereas it was supposed to mean datetime.datetime(2014, 12, 14, 11, 0) because it was a post of 2014.
I think there should be parameter like only_allow_past_dates which should disable future date parsing and interpret it only as the date that has passed.

Absorbed by https://github.com/scrapinghub/dateparser/issues/36


Add parsers for hr.dat and r.dat files

I noticed parsers are missing for these two file formats that are part of the regular Wannier90 output, so I added them. To finish, I think an example r.dat file is needed and a test should be written (I drafted one as a comment). Having these additional parsers would be very useful since I could start using WannierIO.jl in AutoBZ.jl

Thanks, Lorenzo!
I am trying to migrate to artifact system for adding these large test files, I will merge this PR and add the missing test files once the migration is done.
Of course, feel free to create issues/PRs if you need additional file formats :)

Great! I will register a new release soon.


matplotlib rendering error

In nb08 this exception is raised during rendering the figure produced by plot_1D_histogram_trajectories.
When I comment out the ax.annotate call, then the figure is rendered correctly. I assume this is triggered by a rigorous check, which has been added recently. I will report it upstream.
In the meantime we can simply downgrade matplotlib for test execution.

I guess it's the plt.annotate because they changed the API. Maybe I can fix that.

On 16.11.18 10:38, Tim Hempel wrote:

I guess it's the plt.annotate because they changed the API. Maybe I can fix that.

if I omit the arrowprops it succeeds.

Bug was reported to Matplotlib (https://github.com/matplotlib/matplotlib/issues/12820), for now resolved with #181 .

I sill get this bug, in the case of saving the figure as an image (format png, jpg, tiff). Saving it as a pdf works!
The problem is the annotate function.

OK, interesting. We'll have to wait for the matplotlib developers to really fix this (it's reported, cf. post above). Good that you can save it to PDF, so I suggest you stick to this as a temporary solution (and convert to png/jpeg if necessary).

I sill get this bug, in the case of saving the figure as an image (format png, jpg, tiff). Saving it as a pdf works!
The problem is the annotate function.

Maybe this helps to find the bug. If I add to the x-position a tiny distance of 0.000000000001, than is works:
axarr[0].annotate('', xy=(objectZValues[3]+0.000000000001, objectIntensities[3]), xytext=(objectZValues[3],-.05), bbox=dict(boxstyle="round", fc="w"), arrowprops = settings.arrowProps)

Yes, this is how we temporarily fixed this bug here. Are you sure you are posting to the right repository?

@thempel oh sorry, I was redirected here.


Enhancement: Translation / Locale support for table names.

Is your feature request related to a problem? Please describe.
I'm building my admin interface with Starlette Admin, which is awesome. I recently opened a merged PR at #330 to add Turkish Language support but many of my table names, view names are in English name but some of my users will be speaking English or other Languages.
Describe the solution you'd like
Maybe we can create a locale system to distinguish user's selected language and, with a can create a dictionary map to set view and column names in different languages.
A simple example could be like this:
class CompanyView(ModelView):
    locale = {
        "en": {
            "view_label": "Companies",
            "view_name": "Company",
            "id": "ID",
            "name": "Name",
        },
        "tr": {
            "view_label": "Şirketler",
            "view_name": "Şirket",
            "id": "ID",
            "name": "İsim",
        },
        "fr": {
            "view_label": "Entreprises",
            "name": "Entreprise",
            "id": "ID",
            "name": "Nom",
        },
    }
    fields = [
        "id",
        "name",
        CollectionField(
            "status",
            fields=[
                IntegerField("id", read_only=True),
                StringField("name"),
            ],
            locale={
                "en": "status",
                "tr": "durum",
                "fr": "statut",
            }
        ),
    ]

Describe alternatives you've considered
I'm not considering any alternative, no pressure!

The best approach is to set up Babel in your project. You can get the current locale using get_locale().

Thank you for your help.
I haven't try that since it was simply an idea that could be usefull for users but looking at it again, using babel directly (without an abstraction layer inside the module) would be a great practice for the users.


src/campaign-file: Set Cache-Control header

This would allow for images to be cached on the client, and thus result in faster load on client, as well as less calls to the server being made.
Age of cache  is set to 6 months.
Test:

Open Browser's devtools
Go to network tab
Refresh page
Campaign files should be loaded through disk cache.

Ha, I was preparing something similar with the Expires header. This seems better however...
Why not include all the campaign Photos in the cached images?
campaignPhoto: 'campaignPhoto', profilePhoto: 'profilePhoto', campaignListPhoto: 'campaignListPhoto', beneficiaryPhoto: 'beneficiaryPhoto', organizerPhoto: 'organizerPhoto',

I wanted to prevent accumulating a lot of memory inside the browser's cache by caching only the data that is initially shown to user, as well as the data which is not susceptible to frequent changes.
Caching other images should probably be done on nginx/cloudfare level.

Caching a few more images in the browser is not going to take a lot of memory.
The conversation started with this issue: https://github.com/podkrepi-bg/frontend/issues/1549
Here the assumption is that it happens with very bad connections.
There is no point in caching invoices and PDFs - I agree.
But I think we should cache all the images.

Caching a few more images in the browser is not going to take a lot of memory. The conversation started with this issue: podkrepi-bg/frontend#1549 Here the assumption is that it happens with very bad connections.
There is no point in caching invoices and PDFs - I agree. But I think we should cache all the images.

MM yea. Seems like the  <Image> component from next js, also caches the images locally, so it should be fine.


README: add link to GNU tests page in documentation

parfait, merci!

probably too hard to do but I would love to be able to click on the log and to get access to the failure directly ;)


Add new site behavior.

A recent update to the site introduced new features that currently break the track decoding if used.

Added in commit 889851a69decc781075a4d5b92e68220abd9fea8.


Update to 18.1

Update to v 18.1
See INC0322897

Please open a task up in Asana for this so we can better track this through the software deployment lifecycle.

You will definitely need to walk through:

a CFX example with MPI to confirm that the custom template/cfx_assets/start-methods.ccl still work (make sure the hosts are properly being populated in the GUI)
a Fluent example with MPI to confirm Fluent Parallel Info from the template/fluxbox/menu still gives accurate information

You will also need to test that CFX pre/post visualization works with and without vis node type selected due to the CUE_GRAPHICS env var being properly set.
Bonus points, you can confirm that the CFX/Fluent MPI runs start up processes under pbs_mom in the compute nodes.

https://app.asana.com/0/425364008343147/475427362403540

That task is for migrating the apps to Owens and not updating the app on Oakley. Also you should make individual tasks for each app as their deployment lifecycles are separate.
So for each app you will have an Asana task with the following subtasks:

[ ] update code
[ ] review code
[ ] deploy to webdev02/04
[ ] test it on webdev02/04
[ ] release/tag code
[ ] deploy to webtest02/04
[ ] test it on webtest02/04
[ ] deploy to web02/04

Closing as duplicate of https://github.com/OSC/bc_osc_ansys_workbench/pull/4


Update reclass submodule with latest upstream changes

Signed-off-by: Trevor Wood<EMAIL_ADDRESS>Proposed Changes

Updates the reclass submodule to point to the upstream develop branch and pulls in the latest changes.

Just to give an update on this, we ended up forking the salt-formulas/reclass dependency to our own repo so that we can patch the fix above. That is now being used in kapitan 0.27.3 and after. :)
Closing as fixed


add UnitTestTranscriptLogger

Fixes #https://github.com/Microsoft/BotBuilder/issues/5279
Description
Add FileTranscriptLogger and change unit tests to generate transcripts
Specific Changes

add FileTranscriptLogger
added helper static on TestAdapter.CreateConversation()
changed unit tests to use FileTranscriptLogger

Testing
All of the tests are using it.

Pull Request Test Coverage Report for Build #1909

34 of 35 (97.14%)  changed or added relevant lines in 3 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.04%) to 82.478%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

libraries/botbuilder/src/unitTestTranscriptLogger.ts
23
24
95.83%

Files with Coverage Reduction
New Missed Lines
%

libraries/botframework-config/src/botConfigurationBase.ts
2
85.59%

Totals

Change from base Build #1891:
0.04%

Covered Lines:
2768

Relevant Lines:
3227

💛  - Coveralls

Pushing this until @gabog has completed his Testing Manifesto and we have a concrete overall e2e plan in place.


Add feedback forms to Alby

Add a submission form to Alby to collect feature requests and bugs.

I registered an Alby account for the "Fly High" tier from https://hellonext.co/

hellonext looks good! and with that plan we can run it on our domain, nice!
and does also support posting without signup?

Yes I made an email optional

Is this something we would want to have a design done first, or could we just start coding this?

Hellonext requires users to leave an email for posting and voting. That would be acceptable as users still can remain anonymous. But commenting requires login.
With these requirements I only found https://getalby.noorahq.com/ . Roadmap and Changelog are currently switched on but can be disabled if we want. The account includes custom domain & SSL and no limitations in terms of members, boards and contacts. What do you think?
@secondl1ght I prepared some ideas how we can add it to Alby. We can discuss them together and start coding :D

I think https://getalby.noorahq.com/ looks good and pretty easy to use, maybe we wouldn't need a feedback form in Alby but just a button that takes you to this form?

Linked PR #450


Attribute input UI

On the minting screen, users should be able to input an arbitrary set of tilte/value attributes

We decided against this


Leaked credentials

Hello.
I'm the creator of jimaku, thanks for using the API and I'm glad that you're making cool stuff with it.
Just a heads up, but in this line of code: https://github.com/GodPepe7/asb-auto-subs/blob/6cd6489472d0c795b3514c030495dfbb959b1385/src/background.ts#L130 you're leaking your API key for jimaku.cc. I've gone ahead and revoked it for you. It's best practice to not leak these tokens, since they can be used (somewhat) maliciously to upload files with your account. The API is mostly read-heavy so it's not a big issue, but in the interest of security it's best to not hardcode credentials within source code. Rather, read the API key from some type of configuration file.
Good luck with your tool!

Thanks for the hint. I changed it with 1ad45a0d33e3fe6c4c87d17f2202310416028458 to make it a user input instead.


Community - algorithms

Description

I would like the folder community / algorithm to be like a list of the textbook algorithms using qiskit.
I think we need a readme.ipynb that gives an overview and is linked to from the main index.ipynb rather than the folder that it currently goes to.
We have a really good start but let’s just think about how they go together and how you learn qiskit though textbook algorithms.
landing from the main file
3.4 Textbook Quantum Algorithms with Qiskit
Learn Qiskit from the textbook quantum algorithms, like Shor, Grover, and Deutsch-Jozsa.
Your Environment

QISKit version:
Python version:

@rraymondhp can you think about this.

I will make a plan soon. Please wait.


Replace Guava by JDK (Partly)

Replace Guava by JDK (Partly)
https://github.com/wiremock/wiremock/issues/2111
Submitter checklist

[ ] Recommended: Join WireMock Slack to get any help in #help-contributing or a project-specific channel like #wiremock-java
[x] The PR request is well described and justified, including the body and the references
[x] The PR title represents the desired changelog entry
[x] The repository's code style is followed (see the contributing guide)
[x] Test coverage that demonstrates that the change works as expected
[ ] For new features, there's necessary documentation in this pull request or in a subsequent PR to wiremock.org

@tomakehurst @oleg-nenashev
MR finished. please look how it will be possible.

@tomakehurst @oleg-nenashev
Congratulations on the release of 3.0.0 I hope you have time to look

Thanks! We need to discuss the classloader logic itself, but the replacements are good.
@pks-1981 for the WireMock 3 announcements, do you want to be credited as @pks-1981 or do you prefer a real name or another alias?
I'm happy with pks-1981)))

Thanks!


power: Move application level API's to public header

Move the API's used by applications to include/power.h file.
Signed-off-by: Ramakrishna Pallala<EMAIL_ADDRESS>

duplicate PR


chore: upgrade charts

updated chart jxgh/jx-preview from 0.0.184 to 0.0.185

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign garethjevans
You can assign the PR to them by writing /assign @garethjevans in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


How to run all tests with single trigger.

When I right click on Tests and click run all tests, I get exception with this stack trace
Test file(s):
  undefined
module.js:529
    throw err;
    ^

Error: Cannot find module '/home/user/dir1/dir2/dir3/undefined'
    at Function.Module._resolveFilename (module.js:527:15)
    at Function.Module._load (module.js:476:23)
    at Module.require (module.js:568:17)
    at require (internal/module.js:11:18)
    at /home/user/.vscode/extensions/maty.vscode-mocha-sidebar-0.10.0/node_modules/mocha/lib/mocha.js:220:27
    at Array.forEach ()
    at Mocha.loadFiles (/home/user/.vscode/extensions/maty.vscode-mocha-sidebar-0.10.0/node_modules/mocha/lib/mocha.js:217:14)
    at Mocha.run (/home/user/.vscode/extensions/maty.vscode-mocha-sidebar-0.10.0/node_modules/mocha/lib/mocha.js:469:10)
    at Object. (/home/user/.vscode/extensions/maty.vscode-mocha-sidebar-0.10.0/worker/runtest.js:57:7)
    at Module._compile (module.js:624:30)
    at Object.Module._extensions..js (module.js:635:10)
    at Module.load (module.js:545:32)
    at tryModuleLoad (module.js:508:12)
    at Function.Module._load (module.js:500:3)
    at Function.Module.runMain (module.js:665:10)
    at startup (bootstrap_node.js:201:16)

Do you have something in this path
'/home/user/dir1/dir2/dir3/undefined
It's seems like that you referencing to wrong path
Is it run successfully when you running mocha from command line

No I do not have anything in the path '/home/user/dir1/dir2/dir3/undefined'.
The path '/home/user/dir1/dir2/dir3' exists, but the path '/home/user/dir1/dir2/dir3/undefined' does not  exist.'
It runs successfully when I run mocha from command line.
Also, I can run test suits individually from mocha-sidebar.

Let me check it again maybe I broke something
On Sun, Nov 5, 2017, 9:27 PM rosesonfire<EMAIL_ADDRESS>wrote:

No I do not have anything in the path
'/home/user/dir1/dir2/dir3/undefined'.
The path '/home/user/dir1/dir2/dir3' exists, but the path
'/home/user/dir1/dir2/dir3/undefined' does not exist.'
It runs successfully when I run mocha from command line.
Also, I can run test suits individually from mocha-sidebar.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/maty21/mocha-sidebar/issues/13#issuecomment-341998152,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE_nuQP8u8niSHgaMch4zm9xDbdCp2rmks5szgwKgaJpZM4QSfbj
.

couldn't reproduce it on my pc with my tests , if you can upload not working sample it will be helpful tks

You can clone/fork the project, and open it in vscode:
https://github.com/rosesonfire/react-try-out
And use this .vscode/settings.json

{
  "editor.tabSize": 2,
  "mocha.options": {"bail": false, "fullTrace": true, "useColors": true, "useInlineDiffs": true },
  "mocha.files.glob": "dist/**/*.spec.js"
}

Then run:

npm install

Then run the tests from command line. This runs successfully:

npm run test

Then refresh the mocha-sidebar and the tests should be visible in the mocha-sidebar. Right click on the root (i.e. Tests) and click Run all tests. This triggers the exception in the output.
However, if you right click on individual tests or test-suites, and click Run test or Run tests from this level, the corresponding test(s) run successfully.

Let me know if I am doing something wrong here.

Tks :)
On Mon, Nov 6, 2017, 9:27 AM rosesonfire<EMAIL_ADDRESS>wrote:

You can clone/fork the project, and open it in vscode:
https://github.com/rosesonfire/react-try-out
And use this .vscode/settings.json
{
"editor.tabSize": 2,
"mocha.options": {"bail": false, "fullTrace": true, "useColors": true, "useInlineDiffs": true },
"mocha.files.glob": "dist/**/*.spec.js"
}

Then run:

npm install

Then run the tests from command line. This runs successfully:

npm run test

Then refresh the mocha-sidebar and the tests should be visible
in the mocha-sidebar. Right click on the root (i.e. Tests) and
click Run all tests. This triggers the exception in the output.
However, if you right click on individual tests or test-suites, and
click Run test or Run tests from this level, the corresponding
test(s) run successfully.

Let me know if I am doing something wrong here.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/maty21/mocha-sidebar/issues/13#issuecomment-342066823,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE_nuf9f7CRctYD3CEJCW4L_RR8SYbEDks5szrTtgaJpZM4QSfbj
.

find the issue
im creating object tree that represent the suits
the problem is that im creating object with test property (not the best idea need to change it to uniuqe name)
so for your problem you have test in fronend/index.spec.js
describe("test", function () {
});

as a workaround change the test to something else

Thanks, that did the trick! I changed the name of my test from "test" to something else and it is working now.

please verify that its working for you without the workaround tks :)

I updated the extension by uninstalling and then reinstalling it in vscode and tried again. I am afraid the exception was thrown again.

Test file(s):
  undefined
module.js:529
    throw err;
    ^

Error: Cannot find module '/home/user/dir1/dir2/dir3/undefined'
    at Function.Module._resolveFilename (module.js:527:15)
    at Function.Module._load (module.js:476:23)
    at Module.require (module.js:568:17)
    at require (internal/module.js:11:18)
    at /home/user/.vscode/extensions/maty.vscode-mocha-sidebar-0.10.14/node_modules/mocha/lib/mocha.js:220:27
    at Array.forEach ()
    at Mocha.loadFiles (/home/user/.vscode/extensions/maty.vscode-mocha-sidebar-0.10.14/node_modules/mocha/lib/mocha.js:217:14)
    at Mocha.run (/home/user/.vscode/extensions/maty.vscode-mocha-sidebar-0.10.14/node_modules/mocha/lib/mocha.js:469:10)
    at Object. (/home/user/.vscode/extensions/maty.vscode-mocha-sidebar-0.10.14/worker/runtest.js:57:7)
    at Module._compile (module.js:624:30)
    at Object.Module._extensions..js (module.js:635:10)
    at Module.load (module.js:545:32)
    at tryModuleLoad (module.js:508:12)
    at Function.Module._load (module.js:500:3)
    at Function.Module.runMain (module.js:665:10)
    at startup (bootstrap_node.js:201:16)

ok let me check it again
On Tue, Nov 7, 2017, 7:04 AM rosesonfire<EMAIL_ADDRESS>wrote:

I updated the extension by uninstalling and then reinstalling it in vscode
and tried again. I am afraid the exception was thrown again.
Test file(s):
undefined
module.js:529
throw err;
^
Error: Cannot find module '/home/user/dir1/dir2/dir3/undefined'
at Function.Module._
resolveFilename (module.js:527:15)
at Function.Module._load (module.js:476:23)
at Module.require (module.js:568:17)
at require (internal/module.js:11:18)
at /home/user/.vscode/extensions/maty.vscode-mocha-sidebar-0.10.14/node_modules/mocha/lib/mocha.js:220:27
at Array.forEach ()
at Mocha.loadFiles (/home/user/.vscode/extensions/maty.vscode-mocha-sidebar-0.10.14/node_modules/mocha/lib/mocha.js:217:14)
at Mocha.run (/home/user/.vscode/extensions/maty.vscode-mocha-sidebar-0.10.14/node_modules/mocha/lib/mocha.js:469:10)
at Object. (/home/user/.vscode/extensions/maty.vscode-mocha-sidebar-0.10.14/worker/runtest.js:57:7)
at Module._compile (module.js:624:30)
at Object.Module._extensions..js (module.js:635:10)
at Module.load (module.js:545:32)
at tryModuleLoad (module.js:508:12)
at Function.Module._load (module.js:500:3)
at Function.Module.runMain (module.js:665:10)
at startup (bootstrap_node.js:201:16)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/maty21/mocha-sidebar/issues/13#issuecomment-342376618,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE_nuUyfuBppHDzzJF-RV-Vdr_1uF2a5ks5sz-TEgaJpZM4QSfbj
.

fixed  for version 0.10.16 (checked also in your code :))
the problem was that for some reason the code was not published to the marketplace

I updated Mocha Sidebar again, and it is working fine now. Thanks!

I'm closing the issue tks


Support for bad/no connectivity?

Does this library have support to cache and load images from the background when the user has bad connection or loses connection so that the images are still loaded from the cache instead of showing a blank image (currently happening with the library). Where should I look for support on this functionality?
Thank you!
This is particularly for Xamarin.Forms

I echo this statement. If there is no internet connection, you can see in the stack trace that a network call is been made to fetch the image, and that it obviously fails. App doesn't crash, but it would be great if this library can detect if the phone is connected to the net, and immediately return the cached image or placeholder image, instead of trying an internet connection which will obviously failed. I'm not sure if it's possible, but I might try Xam.Plugin.Connectivity in the FFImageLoading initialization method when I override HttpClient...

@michaeldimoudis Please let me know if you got a solution either with returning the cached image or the placeholder image. How are you currently setting the placeholder image for FFImageLoading?
Thanks!

Makes sense it should not be difficult to add that functionality.

+1 Code needed for checking network on each platform is here: https://github.com/jamesmontemagno/Xamarin.Plugins/tree/master/Connectivity/Connectivity

Currently, I'm using CachedImages and I'm setting the ErrorPlaceholder, so that when there's no internet, the placeholder images are shown but what if I want to cache my images that need internet to load. I want to cache it when the user first logins with internet connectivity but when they're offline, they can still see their cached images. I'm looking for a Xamarin.Forms solution using this library.
I can't find a Forms implementation by James Montemagno. Should I just use the native Android solution provided?

Images that are loaded with the lib are automatically cached, hence available when offline. This is by default.
If you want to "preload" images this is also possible with the new Preload method.

Hi I am having a pretty big issue now, I didn't want to create a new issue. With the latest RC 2.1.0-rc1, my images are NOT getting cached anymore. On each load it downloads the images again, and if I cut my network the error placeholder image appears. My app logic hasn't changed, just updated Xamarin Forms and FFImageLoading etc... is this a known issue? Has anything major changed here? I have just tested this in the iOS emulator so far...

@michaeldimoudis this issue is now fixed in git, should be fixed soon in nugets

@molinch how do I set them available for offline use? If I don't set a placeholder for error and loading, then would they load even though there's low or no connection?

@owlstack What is implemented currently:

loading images when there is network, these images are cached, hence they will be available offline and online
if an image request is done while offline, and the image was not already cached, then the error placeholder will be displayed
in both cases while the image loads the loading placeholder is displayed

What is not yet implemented:

immediately checking network status instead of trying to start the request & see if it fails

@molinch yes I had meant I wanted to preload the images using Xamarin.Forms. Is there an example on how to use the preload method? Thanks!

Hi. Sorry,  don't want create new issue, but my problem related to this.
I try to explain behavior: I had very, very slow connection (near 0.03Mbit) but I had. I have list view with 30 items and each contains CachedImage with source as url. And also I have CachedImage with .png source, but this png don't display until I get good connection and load all images from url.
I use XF <IP_ADDRESS>29 and FFImageLoading <IP_ADDRESS>. I saw this behavior on iOS app

@martb1n I know it's annoying but that is the expected behaviour in 2.1.
This is something we want to improve for 2.2

Should be fixed in 2.1.9-pre-168-core-r. Please reopen it if doesn't work for you.


fix: specify distribution key for fs source

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?

bug: in prev impl, the distribution key is missing and we apply all state changes to vnode0 in the runtime. This behavior leads to only one fs fetch exec will work (not introducing correctness problem but low efficiency).

The root cause is that the fs fetch exec will do range scan on assigned vnodes but all data is written to one vnode.

fix: set the distribution key in the frontend before writing to catalog. Do NOTHING to existing jobs, preventing data consistency problem.

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[x] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

LGTM, btw, what is the meaning of the partition_id in FSFetcher? Does S3 support to fetch the file names with partition?

We see each file as a partition in file source. So we use file names as state table's pk and distribution key.


TLS parsing not working with mod_gnutls

Hi!
I noticed that TLS parsing doesn't work with my Apache server. I'm using mod_gnutls and it outputs this in access.log
"TLS1.3" "ECDHE_RSA_CHACHA20_POLY1305"

Log-format is
log-format %v %h %^[%d %t.%f %^%^] "%r" %s %b "%K" "%k" "%R" "%u"
date-format %Y-%m-%d
time-format %H:%M:%S

Looking at #1967 I think there is a missing 'v' in TLS1. 3 and the cipher suites uses '_' instead of '-'.

I checked the source and it is indeed a simple string check for TLSv1. 1 etc.

Thanks for reporting this. Sorry a bit confused, are you saying the issue is related to _ vs -?

okay so I just tried this and it's not outputting anything on that panel because of TLS1.3 not having the common v on it, e.g., TLSv1.3.
I could simply add TLS1.1 TLS1.2 TLS1.3  but I wonder what's the standard here... any thoughts?

I've added TLS1.1 TLS1.2 TLS1.3 to the list upstream. It will be pushed out in the upcoming release. Stay tuned.
Closing this. Feel free to reopen it if needed. Thanks

Thanks for reporting this. Sorry a bit confused, are you saying the issue is related to _ vs -?

I originally thought that GoAccess also checked for the cipher suites. Openssl uses - in the names and gnutls uses _.

It does, but only when it's given as version of it, e.g.,
"ciphersuite": 49196 resolves to TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384


Setup problems with Kuka industrial arm

Hi,
I am trying to set this package up to use with the Kuka KR16 arm but am having some problems with the controllers.
I have been trying to follow the UR5 example. I have a launch file which sets up the Gazebo, Rviz and MoveIt! with the controllers:
<?xml version="1.0"?>
<launch>
  <arg name="limited" default="false"  doc="If true, limits joint range [-PI, PI] on all joints." />
  <arg name="paused" default="false" doc="Starts gazebo in paused mode" />
  <arg name="gui" default="false" doc="Starts gazebo gui" />
  <arg name="sim" default="false" doc="If true, use the simulated joint controllers"/>
  <arg name="use_moveit" default="true"/>
  <arg name="use_rviz" default="true"/>

  <!-- startup simulated world -->
  <include file="$(find gazebo_ros)/launch/empty_world.launch">
    <arg name="world_name" default="worlds/empty.world"/>
    <arg name="paused" value="$(arg paused)"/>
    <arg name="gui" value="$(arg gui)"/>
  </include>

  <!-- send robot urdf to param server -->
  <param name="robot_description" command="$(find xacro)/xacro --inorder '$(find kuka_kr16_support)/urdf/kr16_2.xacro'" />

  <!-- push robot_description to factory and spawn robot in gazebo -->
  <node name="spawn_gazebo_model" pkg="gazebo_ros" type="spawn_model" args="-urdf -param robot_description -model robot -z 0.0" respawn="false" output="screen" />

  <!-- spawn the joint_state_controller and joint_trajectory_controller-->
  <rosparam file="$(find kr16_moveit_config)/config/ros_controllers.yaml" command="load"/>
  <node name="arm_controller_spawner" pkg="controller_manager" type="spawner" ns="kuka_kr16_2" args="joint_state_controller arm_controller" respawn="false" output="screen"/>

  <!-- Remap joint_states -->
  <remap from="/joint_states" to="/kuka_kr16_2/joint_states"/>

  <!-- Robot state publisher -->
  <node pkg="robot_state_publisher" type="robot_state_publisher" name="robot_state_publisher">
    <param name="publish_frequency" type="double" value="50.0" />
    <param name="tf_prefix" type="string" value="" />

  </node>

  <!-- Launch rviz -->
  <node if="$(arg use_rviz)"
	name="rviz" pkg="rviz" type="rviz"
	args="-d $(find jog_launch)/launch/jog.rviz"/>

  <!-- Remap follow_joint_trajectory -->
  <remap if="$(arg sim)" from="/follow_joint_trajectory" to="/kuka_kr16_2/arm_controller/follow_joint_trajectory"/>

  <!-- Launch MoveIt! -->
  <include if="$(arg use_moveit)"
	   file="$(find kr16_moveit_config)/launch/move_group.launch"/>

</launch>

I then have the jog_frame node being launched in a separate launch file as it was causing some issues in the previous launch file:
 <?xml version="1.0"?>
<launch>
  <!-- Remap joint_states -->
  <remap from="/joint_states" to="/kuka_kr16_2/joint_states"/>

  <!-- Remap follow_joint_trajectory -->
  <remap from="/follow_joint_trajectory" to="/kuka_kr16_2/arm_controller/follow_joint_trajectory"/>

  <!-- Launch jogging node -->
  <rosparam command="load" file="$(find jog_launch)/config/kr16_jog.yaml"/>
  <node name="jog_frame_node" pkg="jog_controller" type="jog_frame_node" output="screen">
    <param name="use_action" value="true"/>
  </node>

</launch>

The problem I'm having is that the jog_frame node is giving this error:
Waiting for arm_controller/follow_joint_trajectory server...
Do I need to set up a server? If so, how do i do this?
Thank

Cross-posted: waitForServer issue to ROS Answers.

@gavanderhoorn Thanks!
@m-talha Obviously it is not the problem of jog_control package as I mentioned in ROS Answers. Feel free to create new issue here, in case MoveIt! works correctly for your robot, and jog_control doesn't.

I posted a solution to this on the ROS Answers link above


WIP chore(*): bump cnab-go dep

Bumps to latest cnab-go release
Currently pending on corresponding duffle and cnab-to-oci bumps...
For the former duffle dep, https://github.com/deislabs/cnab-go/pull/97 and https://github.com/deislabs/cnab-go/pull/98 should represent the last few ports needed to remove the duffle dep from this repo...

Both PRs are now merged! 🎉

Closed in favor of https://github.com/deislabs/porter/pull/511


getUser() return value contains passwordHash and passwordSalt

The UserRecord returned by admin.auth().getUser() contains passwordHash and passwordSalt fields.
const admin = require('firebase-admin')
admin.initializeApp();
admin.auth().getUser(uid)
  .then((user) => console.log(user));

This resulted in:
UserRecord {
  uid: 'e1b2NmnasZXw0QtpYFcZ88IeK5t1',
  email<EMAIL_ADDRESS>  emailVerified: true,
  displayName: undefined,
  photoURL: undefined,
  phoneNumber: undefined,
  disabled: false,
  metadata:
   UserMetadata {
     creationTime: 'Wed, 03 Apr 2019 23:36:27 GMT',
     lastSignInTime: 'Thu, 04 Apr 2019 00:38:10 GMT' },
  providerData:
   [ UserInfo {
       uid<EMAIL_ADDRESS>       displayName: undefined,
       email<EMAIL_ADDRESS>       photoURL: undefined,
       providerId: 'password',
       phoneNumber: undefined } ],
  passwordHash: 'UkVEQUNURUQ=',
  passwordSalt: undefined,
  customClaims: undefined,
  tokensValidAfterTime: 'Wed, 03 Apr 2019 23:36:27 GMT' }

This is contrary to the documented behavior:

passwordHash
(string or undefined)
The user’s hashed password (base64-encoded), only if Firebase Auth hashing algorithm (SCRYPT) is used. If a different hashing algorithm had been used when uploading this user, as is typical when migrating from another Auth system, this will be an empty string. If no password is set, this is null. This is only available when the user is obtained from listUsers().

Is there any other way to get the password hash?

You can get passwordHash and passwordSalt using the listUsers method from admin auth  api

google does not fix this, right?

The UserRecord returned by admin.auth().getUser() contains passwordHash and passwordSalt fields.
const admin = require('firebase-admin')
admin.initializeApp();
admin.auth().getUser(uid)
  .then((user) => console.log(user));

This resulted in:
UserRecord {
  uid: 'e1b2NmnasZXw0QtpYFcZ88IeK5t1',
  email<EMAIL_ADDRESS>  emailVerified: true,
  displayName: undefined,
  photoURL: undefined,
  phoneNumber: undefined,
  disabled: false,
  metadata:
   UserMetadata {
     creationTime: 'Wed, 03 Apr 2019 23:36:27 GMT',
     lastSignInTime: 'Thu, 04 Apr 2019 00:38:10 GMT' },
  providerData:
   [ UserInfo {
       uid<EMAIL_ADDRESS>       displayName: undefined,
       email<EMAIL_ADDRESS>       photoURL: undefined,
       providerId: 'password',
       phoneNumber: undefined } ],
  passwordHash: 'UkVEQUNURUQ=',
  passwordSalt: undefined,
  customClaims: undefined,
  tokensValidAfterTime: 'Wed, 03 Apr 2019 23:36:27 GMT' }

This is contrary to the documented behavior:

passwordHash
(string or undefined)
The user’s hashed password (base64-encoded), only if Firebase Auth hashing algorithm (SCRYPT) is used. If a different hashing algorithm had been used when uploading this user, as is typical when migrating from another Auth system, this will be an empty string. If no password is set, this is null. This is only available when the user is obtained from listUsers().

Which firebase-admin version are you using?

documented behavior

Can confirm this is still an issue in this setup:
    "firebase": "9.6.4",
    "firebase-admin": "10.0.2",
    "firebase-functions": "3.16.0",

I'm also have same problem.
admin.auth().getUser  return passwordHash and passwordSalt parameter with undefined. But I can get value for those parametes using admin.auth().listUsers
How can I get passwordHash and passwordSalt values using admin.auth().getUser

This makes no sense. I just want to get a single user password hash to match using firebase admin and I need to pull the entire user list to do it. Can you imagine charging the app with millions of user entries just to get only single entity property from one position? It's also heavy for Firebase servers at all...

is there any update on this?

Hi, please can we have an update on this?


loading and running multiple models on NPU RK3588S

Is it possible to load more than one model at the same time and run inference on these models in sequence (pipeline) or in parallel (multitasking)?

Hello, is there a way to address this issue? @rpvelloso

Hello, is there a way to address this issue? @rpvelloso

Don't know. I'm still waiting for an answer...

Hello, is there a way to address this issue? @rpvelloso

Don't know. I'm still waiting for an answer...

Okay, I have encountered the same problem as you and need to run multiple models in sequence, but it has not been successful so far. The later models will close the previously opened models

Hello, is there a way to address this issue? @rpvelloso

Don't know. I'm still waiting for an answer...

Okay, I have encountered the same problem as you and need to run multiple models in sequence, but it has not been successful so far. The later models will close the previously opened models

That's what I was afraid, I haven't got a board because they didn't answer me. I guess I'll look up other NPU manufacturers

Hello, is there a way to address this issue? @rpvelloso

Don't know. I'm still waiting for an answer...

Okay, I have encountered the same problem as you and need to run multiple models in sequence, but it has not been successful so far. The later models will close the previously opened models

That's what I was afraid, I haven't got a board because they didn't answer me. I guess I'll look up other NPU manufacturers

Okay, I'll see if there are any other ways to achieve it. Good luck!

I have implemented a method of loading two models simultaneously: in the create method, regarding the ctx attribute during initialization, each model should correspond to a different ctx object, so that multiple models can be successfully initialized. As for the sequential reasoning of multiple models, I have not yet verified this aspect.

@rpvelloso Look at my reply above


Make the package download the metabolic models on install/setup

Other option is to make an executable script in the package that does this

The models are now on amazon s3


'ended' event not firing

This is not strictly speaking a Shaka issue as far as I can tell but I was hoping you might be able to provide insight.
We are having an issue where the 'ended' event on the  element is not firing when our content finishes. Actually it seems some of our content is triggering an 'ended' event sometimes and sometimes it's not but I can't figure out if there is a pattern to it. Using the Shaka sample app I loaded some content and played it until the end and no 'ended' events fired. After reloading the page and loading the same content the 'ended' events were firing.
I can see that Shaka has it's own 'streamEnded' event that fires close to the end of the content to trigger mediaSource.endOfStream(). Is there any relation between this event and the  tag 'ended' event? The streamEnded event is always firing so clearly Shaka is consistently aware that the end of the content has been reached but for some reason which I'm having a really hard time tracking down, the  tag ended condition isn't getting met. I suspect this is a content issue but that's as far as I am on this right now.

If this is in Chrome, it might be related to https://code.google.com/p/chromium/issues/detail?id=349543.

TL;DR: @ddorwin is probably right.
This is how end-of-stream works in Shaka:
When a Stream appends the final segment for its content type (audio or video), it fires an internal, non-bubbling 'streamEnded' event.  This goes to the StreamVideoSource, which owns the MediaSource object.
When all Stream objects have reported 'streamEnded', then final segments have been appended for all types, and StreamVideoSource calls MediaSource.endOfStream().  This tells the browser's video stack that we will not be providing any additional segments.
When MediaSource.endOfStream() has been called AND video.currentTime hits the end of the timeline, then the video element is supposed to fire the 'ended' event.  (If we didn't call endOfStream(), the video would simply pause at the end, waiting for more data to extend the video timeline.)
So if 'ended' isn't fired on the video, it's very likely a browser bug, and it seems @ddorwin knows a likely candidate.
You could patch Shaka to work around the Chrome bug by emitting its own event when MediaSource.endOfStream() and Math.abs(video.currentTime - video.duration) < someTinyThreshold.  This, however, would not be something we would accept as a patch.  We try not to hide browser bugs if we can help it, in particular when the impact is this small.

Great, thanks for all the info guys, this is really helpful. I hadn't seen that chrome bug. We are indeed experiencing this in chrome.
It had occurred to me to listen to this endOfStream event but I agree it's a bad solution and if we absolutely need a temp solution then we will just do it ourselves.

Which version of Chrome? One of the most recent comments says "Remaining cases of this seem to be WebAudio issues...", which would imply Shaka should not be impacted. If you can provide a repro case or more details in that bug, that would be helpful.

I'm running chrome: 46.0.2490.80 (64-bit) and chrome canary:  48.0.2550.0 canary (64-bit) also seems to behave the same for me. This is on MAC OSX 10.9.5
There is audio associated with the content though so couldn't it still be related to these unresolved webAudio issues?
In any case, I'll see if I can get some content that exhibits this issue that we can make public and then I can put reproduction steps on that issue.

Thanks @ddorwin for pointing us at the Chrome bug, and thanks @sanbornhnewyyz for offering to contribute to that report.  Since it appears this isn't a Shaka bug, I'm going to go ahead and close this issue.


Trying to get captions working on Android from feature/captions branch

Hi @cobarx I am trying to use your feature/captions branch in order to get captions showing on Android. This is more of a proof of concept and testing current implementation.
I am using the following HLS stream
http://sample.vodobox.com/planete_interdite/planete_interdite_alternate.m3u8
You can test it out here and enable the english captions
http://bitmovin.com/demos/stream-test
The video loads and plays on Android but none of the captions are visible.
Any help is greatly appreciated

@fdiep I went through and used your sample to get it working. I had forgotten to push some of my changes, plus I was using the default caption on iOS which doesn't work when there are multiple captions to choose from (like in your video).
That branch was one I built for our app where we only have one captions track, so it won't be well suited to your video if you need to be able to select between all 3. You can select the particular subtitle you want by modifying the code.
ExoPlayer:
https://github.com/react-native-community/react-native-video/blob/feature/captions/android-exoplayer/src/main/java/com/brentvatne/exoplayer/ReactExoplayerView.java#L657
Change the first 0 to the track you want. Note that ExoPlayer sees 4 tracks where track 0 is a CEA track that doesn't work as far as I can tell.
iOS:
https://github.com/react-native-community/react-native-video/blob/feature/captions/ios/RCTVideo.m#L645
Change 0 to the track you want.
We are long overdue for robust subtitle support, so I'm going to see if I can whip up a more complete implementation in the next few days. If it's alright, I'd like to use your video for testing since all my videos only have 1 track.

Thanks for the explanation @cobarx
I pulled latest from features/captions and am now getting this error
.../node_modules/react-native-video/android-exoplayer/src/main/java/com/brentvatne/exoplayer/ReactExoplayerView.java:657:
error: package FixedTrackSelection does not exist
   = new MappingTrackSelector.SelectionOverride(new FixedTrackSelection.Factory(), 0, 0);

Thanks again for the help!

Crap, was copying changes by hand and didn't get all of them. I pushed code that has the import.

I was able to build for android with no issues but I still do not see the captions. I have changed the mentioned line to this new MappingTrackSelector.SelectionOverride(new FixedTrackSelection.Factory(), 1, 0); in exoplayer/ReactExoplayerView.java
I have also tried indexes 0, 2, and 3 but none of them bring up the captions.

Are you using ExoPlayer? By default rnv uses the default Android media player which I haven't added subtitle support to.
You can change it by editing settings.gradle from:
project(':react-native-video').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-video/android')
to:
project(':react-native-video').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-video/android-exoplayer')

I've got a much more complete branch with subtitle support ready now. Check out #1049 and let me know if it works for you.


Expose intents from ClusterConfig

Adding this since it's mentioned here but didn't actually exist
The doc comment is extremely terrible and I welcome any and all suggestions ❤What should I mention in it, etc?

I don't think that this will work as it will be overwritten when the config is build we should rather have a method to manipulate the config builder in all the ways.
    /// Sets the intents to use with the cluster.
    pub fn intents(mut self, intents: Option<GatewayIntents>) -> Self {
        self.1.intents(intents);

        self
    }

I think that this should work

Gotcha, I'll do that then

Would you also like me to also update the config.shard_config function's doc comment to not refer to the non-existent method?

Yeah that would be nice


flutter drive running flavorless gradle task even when flavor is specified

It seems like the flutter drive command is ignoring the flavor argument when building for android.
Steps to Reproduce

Generate a flutter project.
Add a flavor to your android/app/build.gradle (For me, that was alpha)

flavorDimensions "app"

    productFlavors {
        alpha {
            dimension "app"
            applicationId "com.example.alpha"
            versionNameSuffix "-alpha"
        }
    }

Create a test_driver folder in the topmost folder of the app.
Add app_e2e.dart:

import 'package:e2e/e2e.dart';
import 'package:myapp/alpha-main.dart' as app;
import 'package:flutter_test/flutter_test.dart';

void main() {
  E2EWidgetsFlutterBinding.ensureInitialized();

  testWidgets("App opens", (WidgetTester tester) async {
    // Build our app and trigger a frame.
    app.main();

    // Trigger a frame.
    await tester.pumpAndSettle();
  });
}

Add app_e2e_test.dart:

import 'dart:async';

import 'package:e2e/e2e_driver.dart' as e2e;

Future<void> main() async => e2e.main();

Run flutter drive test_driver/app_e2e.dart --flavor alpha

Expected results: The gradle task assembleAlphaDebug runs to build the app
Actual results: The gradle task assembleDebug runs to build the app, and I subsequently get the error: Gradle build failed to produce an .apk file
The full logs:
Using device Android SDK built for x86.
Starting application: test_driver/agape-native-app_e2e.dart
Installing build/app/outputs/flutter-apk/app.apk...                 0.2s
Error: ADB exited with exit code 1
Performing Streamed Install

adb: failed to install
/Users/sikeyouthought/Work/Agape/myapp/build/app/outputs/flutter-apk/app.apk:
Failure [INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries,
res=-113]
Running Gradle task 'assembleDebug'...
Running Gradle task 'assembleDebug'... Done                        44.2s
Gradle build failed to produce an .apk file. It's likely that this file was
generated under /Users/sikeyouthought/Work/Agape/myapp/build, but the tool
couldn't find it.

flutter doctor output:
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, 1.19.0-2.0.pre.145, on Mac OS X 10.15.4 19E287,
    locale en-US)
[!] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    ✗ Android license status unknown.
      Try re-installing or updating your Android SDK Manager.
      See https://developer.android.com/studio/#downloads or visit visit
      https://flutter.dev/docs/get-started/install/macos#android-setup for
      detailed instructions.
[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
[✓] Android Studio (version 3.6)
[!] VS Code (version 1.45.1)
    ✗ Flutter extension not installed; install from
      https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[✓] Connected device (1 available)

! Doctor found issues in 2 categories.

Update: Happy to say that:
cd android
./gradlew app:connectedAndroidTest -Ptarget=`pwd`/../test_driver/myapp_e2e.dart

does work and does use the correct gradle task, so I am fine using that in the meantime.

Using device SM M305F.
Starting application: test_driver/app_e2e.dart
"build/app/outputs/flutter-apk/app.apk" does not exist.
Running Gradle task 'assembleDebug'...
Running Gradle task 'assembleDebug'... Done                        35.0s
Gradle build failed to produce an .apk file. It's likely that this file was generated under
/Users/tahatesser/AndroidStudioProjects/master_flutter/build, but the tool couldn't find it.
tahatesser@Tahas-MacBook-Pro master_flutter %

flutter doctor -v
[✓] Flutter (Channel master, 1.19.0-2.0.pre.214, on Mac OS X 10.15.5 19F96, locale en-GB)
    • Flutter version 1.19.0-2.0.pre.214 at /Users/tahatesser/Code/flutter_master
    • Framework revision 1d395c5e18 (21 hours ago), 2020-05-31 07:41:50 -0700
    • Engine revision 923687f0e7
    • Dart version 2.9.0 (build 2.9.0-11.0.dev 6489a0c68d)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/tahatesser/Code/sdk
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/tahatesser/Code/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.5, Build version 11E608c
    • CocoaPods version 1.9.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 45.1.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.45.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.11.0

[✓] Connected device (5 available)
    • SM M305F   • 32003c30dc19668f                     • android-arm64  • Android 10 (API 29)
    • iPhone 11  • 0EC80516-8F99-4A0C-89ED-2273579862F9 • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-13-5 (simulator)
    • macOS      • macOS                                • darwin-x64     • Mac OS X 10.15.5
      19F96
    • Web Server • web-server                           • web-javascript • Flutter Tools
    • Chrome     • chrome                               • web-javascript • Google Chrome
      83.0.4103.61

• No issues found!

Seems to be related to #24106

Since e2e package is deprecated in favor of integration_test plugin, I verified this issue using integration_test plugin's official example on latest stable and master, updated app/build.gradle to have a sample flavor and ran the test which built and ran the gradle task assembleDevDebug  properly on Android device and executed tests as expected.
Updated app/build.gradle:
buildTypes {
        release {
            // TODO: Add your own signing config for the release build.
            // Signing with the debug keys for now, so `flutter run --release` works.
            signingConfig signingConfigs.debug
        }
        flavorDimensions "version"

        productFlavors {
            dev {
                dimension "version"
                applicationIdSuffix ".dev"
                resValue "string", "app_name", "DEV app"
            }
        }
    }

Command ran : flutter drive --driver=test_driver/integration_test.dart --target=integration_test/example_test.dart  --flavor dev
Test result log:
Starting application: integration_test/example_test.dart
Installing build/app/outputs/flutter-apk/app.apk...                 6.9s
Running Gradle task 'assembleDevDebug'...
Running Gradle task 'assembleDevDebug'... Done                     32.5s
✓ Built build/app/outputs/flutter-apk/app-dev-debug.apk.
Installing build/app/outputs/flutter-apk/app.apk...                 8.7s
I/flutter ( 9238): Observatory listening on http://<IP_ADDRESS>:42327/yVCeG1ZMOIY=/
VMServiceFlutterDriver: Connecting to Flutter application at http://<IP_ADDRESS>:51651/yVCeG1ZMOIY=/
VMServiceFlutterDriver: Isolate found with number:<PHONE_NUMBER>036071
VMServiceFlutterDriver: Isolate is paused at start.
VMServiceFlutterDriver: Attempting to resume isolate
I/flutter ( 9238): 00:00 +0: Counter App opens
VMServiceFlutterDriver: Connected to Flutter application.
I/flutter ( 9238): 00:03 +1: (tearDownAll)
I/flutter ( 9238): 00:03 +2: All tests passed!
All tests passed.
Stopping application instance.
dhs@Dhss-MacBook-Pro example %

flutter doctor -v
[✓] Flutter (Channel stable, 1.22.6, on Mac OS X 10.15.4 19E2269 darwin-x64,
    locale en-IN)
    • Flutter version 1.22.6 at /Users/dhs/documents/Fluttersdk/flutter
    • Framework revision 9b2d32b605 (11 days ago), 2021-01-22 14:36:39 -0800
    • Engine revision 2f0af37152
    • Dart version 2.10.5

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.9.3

[!] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.18.1

[✓] Connected device (2 available)
    • SM A260G (mobile) • 5200763ebcfa861f • android-arm • Android 8.1.0 (API
      27)
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729 • ios
      • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)

! Doctor found issues in 1 category.

[✓] Flutter (Channel master, 1.26.0-18.0.pre.156, on Mac OS X 10.15.4 19E2269
    darwin-x64, locale en-IN)
    • Flutter version 1.26.0-18.0.pre.156 at
      /Users/dhs/documents/Fluttersdk/flutter
    • Framework revision 45508985b1 (9 hours ago), 2021-02-02 22:46:04 -0500
    • Engine revision 2c144c3eeb
    • Dart version 2.12.0 (build 2.12.0-282.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[!] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    ! CocoaPods 1.9.3 out of date (1.10.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin
        code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see
      https://guides.cocoapods.org/using/getting-started.html#installation for
      instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.18.1

[✓] Connected device (4 available)
    • SM A260G (mobile)          • 5200763ebcfa861f                     •
      android-arm    • Android 8.1.0 (API 27)
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729 • ios
      • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                               •
      web-javascript • Google Chrome 88.0.4324.96

! Doctor found issues in 1 category.

I am going ahead and closing this as fixed. If anybody disagrees, write in comments and I'll reopen.