Compatibility with Laravel 5.0

Hello, it seems like this can not be used with Laravel 5.0 or i might be missing something. It would be great if it can be used with Laravel 5.0.
Thank you

Just a heads up, Laravel 5.0 hasn't been supported for over three years now. Please consider upgrading to at least 5.5 and preferably 5.8 to get the most recent (security) updates.

@Lucky-Loek FYI Laravel-AdminLTE is not working yet on version 5.8.
jeroennoten/laravel-adminlte v1.24.0 requires laravel/framework ~5.1.12|~5.2.0|~5.3.0|~5.4.0|~5.5.0|~5.6.0|~5.7.0 -> satisfiable by laravel/framework[5.1.x-dev, 5.2.x-dev, 5.3.x-dev, 5.4.x-dev, 5.5.x-dev, 5.6.x-dev, 5.7.x-dev]

@Lucky-Loek thank you for answer. I also prefer to upgrade but im not able to change workplace environment.

Only Laravel 5.1.12 and higher is supported by this package.

@jeroennoten can you add Laravel 5.8 to the list? I would love to upgrade to the latest version.


Mm 38590 allow disabling retrospective

Summary
This pull request will introduce a per-playbook configuration that allows disabling the retrospective functionality for subsequent runs created using that playbook.

Added Enable retrospective toggle to playbook edit form. When disabled, Retrospective reminder interval and Retrospective template settings are disabled.

https://user-images.githubusercontent.com/4368372/143478922-c2571983-33f2-415d-9a8f-516c29ba4eee.mov

When a run is finished, no prompt occurs after finishing a run to start a retrospective

https://user-images.githubusercontent.com/4368372/143480152-c7266e72-2605-4c56-96b9-6142defb3a7a.mov

When viewing the playbook run details, the retrospective field should be replaced with a message indicating, “Retrospectives were disabled for this playbook run.”

https://user-images.githubusercontent.com/4368372/143480250-01a13aca-980c-4312-b212-4ba53f106c7a.mov

When viewing playbook preview, a retrospective section is omitted

https://user-images.githubusercontent.com/4368372/143480343-f26be205-6ca8-4fdb-8130-2f59d2375869.mov
Ticket Link
https://mattermost.atlassian.net/browse/MM-38590
Checklist

[ ] Telemetry updated
[ ] Gated by experimental feature flag
[ ] Unit tests updated

Hello @gbochora,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

@abhijit-singh For the video above labelled When viewing playbook preview, a retrospective section is omitted -- I was chatting with @gbochora and we weren't sure if maybe you wanted the section to be there but to say something like "The retrospective step has been disabled" -- so that users might realize that that's a thing and then go and turn it on.
Let us know, thanks!

@cpoile @gbochora  That's a good idea but I think it is okay to completely hide retrospective from the preview page for now as not everyone viewing that page might have permission to edit the playbook and the playbook admin will have intentionally disabled it at some point.
This could also be done as a separate effort after we have the enable/disable functionality in place if feel it'll add significant value.

@agarciamontoro I've merged with master and pushed changes.


feat(vm): add tooltip and an overflow to VM card

Pull Request Test Coverage Report for Build 1282

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 53.614%

Totals

Change from base Build 1274:
0.0%

Covered Lines:
8100

Relevant Lines:
13272

💛  - Coveralls


TypeError: Cannot read property 'length' of undefined

I'm getting the same error, I'm getting data from a server
The error shows up whenever I select an item from the dropdownList
It's giving me this error:
ERROR TypeError: Cannot read property 'length' of undefined
    at AngularMultiSelect.webpackJsonp.../../../../angular2-multiselect-dropdown/angular2-multiselect-dropdown/multiselect.component.js.AngularMultiSelect.onItemClick (multiselect.component.js:58)
    at Object.eval [as handleEvent] (AngularMultiSelect.html:36)
    at handleEvent (core.es5.js:11892)
    at callWithDebugContext (core.es5.js:13184)
    at Object.debugHandleEvent [as handleEvent] (core.es5.js:12772)
    at dispatchEvent (core.es5.js:8792)
    at core.es5.js:9384
    at HTMLLIElement.<anonymous> (platform-browser.es5.js:2683)
    at ZoneDelegate.webpackJsonp.../../../../zone.js/dist/zone.js.ZoneDelegate.invokeTask (zone.js:414)
    at Object.onInvokeTask (core.es5.js:4119)

I am currently running this code:
dropdownList: Array<{}> = [];
dropdownSettings = {};

ngOnInit(){
      this.onGet(); --> Gets the data from the server (method is below)

      this.dropdownSettings = {
        singleSelection: false,
        text:"Select Countries",
        selectAllText:'Select All',
        unSelectAllText:'UnSelect All',
        enableSearchFilter: true,
        classes:"myclass custom-class",
        limitSelection: 6,
        badgeShowLimit: 3
      };

  }

onGet(){
    this.brokerService.getFilters()
    .subscribe(
      (dropdownList: any[]) => {
        this.dropdownList = dropdownList; -->The this.dropdownList is now a json object array (exact same format as the static one given your tutorial
        console.log(this.dropdownList); // (confirms it's the exact same format)
        },
      (error)=> console.log(error)
    );
  }

please create a plunker. So that it would be clear. Not an issue from component.

[(ngModel)]  might also be missing in your code while using the component tag. Please check.

I realized deleted that tag from initial testing. It works now, thank you so much for the fast response!

just declaring the selectedItems simple solved my problem . selectedItem=[] creating the problem


BUG: Workspace diagram / flowchart data is not save

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
when the use is create some diagram in the workspace and try to saved data is they give an message data save but when the user re access their file the data is not present their  only text data is saved but
please assign me this issue i want to work on it
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

check the site ... if u save the work then only it will be saved @CoderSwarup

@subhadeeproy3902  check this video data is not save

I didnt know this, alryt u can check on this
although over here its saving and coming nicely .... still if user experience is getting hampered then try to fix this ....
thanks for sharing this too ! @CoderSwarup


Re-add Support for SQLAlchemy <1.4

Support for SQLAlchemy 1.3 was removed in version 0.0.203 by change #6086. Re-adding support.

Description: Imports SQLAlchemy Row at class creation time instead of at init to support SQLAlchemy <1.4. This is the only breaking change and was introduced in version 0.0.203 #6086.

A similar change was merged before: https://github.com/hwchase17/langchain/pull/4647

Dependencies: Reduces SQLAlchemy dependency to > 1.3
Tag maintainer: @rlancemartin, @eyurtsev, @hwchase17, @wangxuqi

Should be fixed!

@hwchase17 Friendly bump! Hoping to get this merged before the holiday weekend! 🙏

@hwchase17 Friendly bump! Hoping to get this merged before the holiday weekend! 🙏

I will review now. Just kicked off tests.

@bradcrossen pls have a quick look and confirm you are OK w / this. it looks like the first import was not needed. i cleaned it up for you.

That is fine with me! Thanks!


Add figsize option to animate like in plot

Currently all animations come out with square size. It'd be nice to be able to control the size with --figsize like in the plot command.

Done!


For timezone CEST market never opens in live trading + tick.Time is possibly incorrect

My local PC is in timezone CEST where I use the IBController (Mono/Linux).
In LocalMarketHours.cs
public bool IsOpen(TimeSpan time, bool extendedMarket)
return time >= _marketOpen
&& time < _marketClose;
always returns false because _marketOpen and _marketClose is set to 00:00:00 (?).
time is also in my local time, which is not correct?
I added -6 hours to get to NY time in InteractiveBrokersBrokerage.cs (_brokerTimeDiff) to change the tick.Time.

This may be an issue loading data from the market-hours-database. This code is located in the SecurityExchangeHoursProvider here
The only time those two values should be equal to zero is when the market is closed all day (Saturday/Sunday for equities).

A nice test would be to change your computer's time zone and see if you experience the same behavior.

It reads the file alright but
in LocalMarketHours.cs
private static readonly IReadOnlyDictionary<DayOfWeek, LocalMarketHours> Open = new ReadOnlyDictionary<DayOfWeek, LocalMarketHours>(
Enum.GetValues(typeof(IsoDayOfWeek)).Cast()
.ToDictionary(x => x, x => new LocalMarketHours(x, TimeSpan.Zero, TimeSpan.FromTicks(Time.OneDay.Ticks - 1)))
);
TimeSpan.Zero results in _marketOpen to be 00:00:00
it doesn't seem to put the hours from securityexchangehoursprovider into LocalMarketHours?

That private static is a definition for exchanges that are considered always open. If you place a breakpoint in the SecurityExchangeHoursProvider here you should be able to intercept the request to get your exchange hours.
Market open as 00:00:00 sounds like forex hours during a weekday. What security types are you trying to run?

Security types: all equities (leveraged ETFs) like UPRO, TQQQ, NUGT etc.
I tried to change the timezone on my PC, didn't have any effect.

I had the same issue on a different project. The solution ended up being using DateTimeOffset instead of DateTime.

Internally we use Jon Skeet's NodaTime library for dealing with time zones. The issue here is the source of time in the InteractiveBrokersBrokerage implementation uses DateTime.Now instead of the local machine settings agnostic DateTime.UtcNow + a time zone conversion to NewYork (or whatever the desired output time zone may be)


Discord broken

Your Discord page is broken
Please fix it
https://discord.gg/jrbPvKW

The discord links are periodically cleaned out as to not reach the limit. This one however will not expire: https://discord.gg/WFnyMfh


pkg/memtier/tracker_idlepage.go: fix code complexity

Closing based on our discussion on complexity goals.


Handling additional tif files in the input directory

This is a bug with a current workaround. So not urgent to address, but good to pick up when we update any filename parsing.

As part of the filename refactor (see https://github.com/fractal-analytics-platform/fractal-tasks-core/issues/189), there is an extra edge-case we missed:
Depending on the microscope type, there is some metadata in the input folder. For example, the Yokogawa creates a few camera specification files. Those are named something like:
DC_sCMOS #1_CAM1.tif
DC_sCMOS #2_CAM2.tif
SC_BP445-45_20x_M01_CH01.tif
SC_BP525-50_20x_M01_CH02.tif
SC_BP600-37_20x_M01_CH03.tif
SC_BP676-29_20x_M01_CH04.tif

(with slight variations depending on camera, objectives & laser paths being used).
These images do not need to be parsed into the OME-Zarr. For the time being, they can just be ignored. This didn't really come up in the synthetic test cases and the test cases that contained PNGs. But if we have TIF images (directly from the microscope) and select them with the glob "*.tif", then the parsing now fails for them:
2022-11-21 12:48:34,430; INFO; START create_zarr_structure task
Traceback (most recent call last):
  File "/net/nfs4/pelkmanslab-fileserver-common/data/homes/fractal/joel/fractal_v1/fractal-demos/examples-v1/server/FRACTAL_ROOT/.fractal/fractal-tasks-core0.4.0/venv/lib/python3.8/site-packages/fractal_tasks_core/create_zarr_structure.py", line 386, in <module>
    run_fractal_task(
  File "/data/homes/fractal/joel/fractal_v1/fractal-demos/examples-v1/server/FRACTAL_ROOT/.fractal/fractal-tasks-core0.4.0/venv/lib/python3.8/site-packages/fractal_tasks_core/_utils.py", line 89, in run_fractal_task
    metadata_update = task_function(**task_args.dict())
  File "/net/nfs4/pelkmanslab-fileserver-common/data/homes/fractal/joel/fractal_v1/fractal-demos/examples-v1/server/FRACTAL_ROOT/.fractal/fractal-tasks-core0.4.0/venv/lib/python3.8/site-packages/fractal_tasks_core/create_zarr_structure.py", line 113, in create_zarr_structure
    filename_metadata = parse_filename(fn.name)
  File "/data/homes/fractal/joel/fractal_v1/fractal-demos/examples-v1/server/FRACTAL_ROOT/.fractal/fractal-tasks-core0.4.0/venv/lib/python3.8/site-packages/fractal_tasks_core/lib_parse_filename_metadata.py", line 98, in parse_filename
    raise ValueError(f"Something wrong with {filename=}, {TFLAZC=}")
ValueError: Something wrong with filename='SC_BP445-45_20x_M01_CH01', TFLAZC='CH01'

Those files should be ignored. We could hard-code it for the Yokogawa by providing an exception list, e.g.:
Ignore files starting with DC_sCMOSor SC_.
A nice implementation could be: If we run into the ValueError for the parsing like above, but files fit one of the patterns, ignore them.
Not yet sure how this will look on other microscopes.

Workaround: Move the DC & SC files to a separate folder
Or create a link to the image files & MeasurementData/Details files to a new folder (ln old_folder/BEGINNING_FILENAME* new_folder)

First solution: let's switch back to the previous behavior (for any invalid name, print a log and skip it).
Later on we can add something like an ignore_pattern variable.

Fixed in 0.4.6 (https://fractal-tasks-core.readthedocs.io/en/stable/changelog.html).


added new card element spelltext (smaller em)

created a new element named spelltext that prints at a smaller em - this shouldn't affect anything current - as its a new card element - and would only be noticed when actually used by someone.

New mantained fork https://github.com/crobi/rpg-cards/issues/159

Closing, since there hasn't been any activity for over three years. @GHMusicalCoder, please feel free to resolve conflicts and reopen if this is important to you, and I'll work with you to get this merged.


CAMEL-20303 - Camel-Sql: Add ObjectInputFilter String pattern paramet…

…er in JdbcAggregationRepository to be used in unmarshall operations
Description

Target

[x] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[x] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[x] I checked that each commit in the pull request has a meaningful subject line and body.

[x] I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

If I merge this commit into camel v3.14.10 to fix the same issue, what do I need to be aware of, are there any incompatibilities? @oscerd

The only thing you need to consider is just that this has never been compiled with JDK 8. For 3.x it has been compiled with JDK 11 and for 4.x with JDK 17. So it could be possible it doesn't work with JDK 8.


Move knex-schema-inspector to ESM based distribution

I think this Gist from Sindre and the comments beneath summarize it perfectly
https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c
My personal favorite: There's more and more JavaScript runtimes nowadays (node/deno/bun/workers/functions etc). ESM is standard JS, CJS is NodeJS common.
This is a breaking change, and should be released as a major version

Another benefit of moving to ESM in the output bundle is that you can prevent TS from adding massive amounts of cruft for CJS/ESM compatibility. I'm seeing about a 25% reduction in size of the dist folder 🎉

Please do not move to ESM only yet. Many modules aren't ready yet and specially Electron does not support it yet.
Maybe in an year of so 😃 when the community is ready.

My suggestion would be to use one of the bundlers that can create both CJS and ESM bundled automatically. That should satisfy needs of both camps :)

Another perspective: https://twitter.com/matteocollina/status/1560658851682168834?t=yyNsYZFH_Lyr4d2yhQeb6Q&s=19
let's talk it through properly :)

I've been following various threads along the same sentiment for a while with great interest. Even in this one (in the replies as well as the main thread) I'm seeing a common line of thinking "Yes, we should move to ESM, but no, don't push people to ESM" which I used to agree with, but is becoming a bit of a chicken-egg problem. We see the same in the other comment replied on this PR:

Please do not move to ESM only yet. Many modules aren't ready yet and specially Electron does not support it yet.
Maybe in an year of so 😃 when the community is ready.

People (like the folks behind Electron) won't put in the effort to support ESM if no push is made to move to ESM from the community in the first place 🤔 It becomes a catch-22:

Electron doesn't support ESM, so therefore I can't/won't use ESM.
Nobody uses ESM, so Electron doesn't see the need to support ESM
🔁

My suggestion would be to use one of the bundlers that can create both CJS and ESM bundles automatically. That should satisfy needs of both camps :)

Fair compromise! I am a little worried about the maintenance overhead though. I've had quite a lot of headaches recently in trying to support both targets in other packages (mostly around compatibility with various bundlers), which made me decide to just bite the bullet and go full ESM. To me, there's a handful of ways forwards:

Merge this PR, and tell people to deal with it. (Very hostile, I agree that it will drive some users away, basically what Sindre has been doing with his vast pool of libraries)
Merge this PR, and put out an open call for other devs to maintain a dual-build. (Causes some friction at first, but hopefully causes other people to step up and help)
Don't merge this PR, and wait for somebody to come along and develop the dual-build setup
Leave everything as-is, and launch the ESM version as a separate forked library

Is not that the Electron guys don't want to support ESM - they do! But is is currently impossible https://github.com/electron/electron/issues/21457#issuecomment-1099904505

Is not that the Electron guys don't want to support ESM - they do! But is is currently impossible electron/electron#21457 (comment)

Ohhh but that's talking about ESM as the entrypoint, it's not necessarily talking about not supporting ESM in general!

Yes indeed it is more about the main entry point. In renderers using esm is just fine.

Closing this as it's clearly a point of contention and not a hill I'm willing to die on.


description of Lean.PrettyPrinter.Delaborator.Delab is outdated

Delaborators have the type Lean.PrettyPrinter.Delaborator.Delab. This
is an alias for DelabM Syntax, where DelabM is the delaboration monad.

This is not correct. Delab is an alias of DelabM Term.
This issue is caused by upstream change at  Jun 28, 2022.
see: https://github.com/leanprover/lean4/commit/a78302243c26395199ca2b71f33edebbba0883bf#diff-39fa64847f93933be08a768b4b399ba3aeed990740b0182f872201131db36b17

This description may be intended one.


Crash on Reload Spigot 1.8

Hello,
Everytime when i do /reload the server crashes.
its PermissionsEx.
Crash log :
http://pastebin.com/ApjgF8tr

The /reload command is a vanilla command which has been broken for more than 4 years.
Don't use it.  Reload plugins individually as needed.  /pex reload, /ess reload, etc.


x/pkgsite: searching for "new" symbols causes page to hang and eventually return 500 internal server error

What is the URL of the page with the issue?
https://pkg.go.dev/search?q=new&m=symbol
What is your user agent?
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Screenshot

What did you do?

Go to https://pkg.go.dev/
Search for "new" in the search box
Click the "Symbols" tab

What did you see happen?
The page hangs for about 30 seconds and then the first time I did it showed the branded 500 error. The second time I tried it it showed the plaintext error.
What did you expect to see?
The first 25 items that were called "new" only. The reason I was searching for "new" in the first place was to get an idea of how many stdlib types were using plain "packagename.New()" instead of "packagename.NewOtherType()". I expected to see stdlib packages (since they are usually ranked above all third-party packages) like log.New()

Related Issues

x/pkgsite: "500 Internal Server Error" in "versions" tab for stdlib package that exists in master only #58594 (closed)

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

seems to work for me?

I think this is the same as #64422


Update autoupdate paths for notepadplusplus.json

Notepad++ download repository path has changed.
This commit updates it to the new path.
P.S. There does not seem to be an https path for those downloads.
This should be changed back to https when it (hopefully) becomes available again.
For now, the hashes could at least be extracted from github instead, using https.

duplicate of https://github.com/lukesampson/scoop-extras/pull/2962 https://github.com/lukesampson/scoop-extras/pull/3123


updates README - styles

I want to add this clarification about the style prop. I wasted a bit of time because I had to assume the prop was styles, before finally realising it is style so I've enhanced the example with a real use case
Fixes #[issue number].
Changes proposed:

Upgrade Path (for changed or removed APIs):
Acceptance Checklist:

[ ] All commits have been squashed to one.
[ ] The commit message follows the guidelines in CONTRIBUTING.md.
[ ] Documentation (README.md) and examples have been updated as needed.
[ ] If this is a code change, a spec testing the functionality has been added.
[ ] If the commit message has [changed] or [removed], there is an upgrade path above.

Published new documentation version.


Found a (slightly) better way to silence failed email delivery errors.

Coverage increased (+0.008%) to 92.658% when pulling 2da755f53752b29371f834fa5898670c3bb6a872 on silence-failed-emails into c92e28fbd1f0e6b207780ae4595a202c59f024eb on master.


Fix min/maxHeight format on tendermint-rpc txSearch

I tried doing tx.minHeight=123 and it failed.
After reading https://docs.tendermint.com/master/rpc/#/Websocket/subscribe I managed to find the proper syntax. We also need to use AND in buildQuery.
Here is an example of a successful query with min and max height against tendermint 0.34 / cosmos-sdk 0.41.3:
send_packet.packet_connection='connection-9' AND tx.height>=7669 AND tx.height<=7669

minHeight is an invention of the LCD API, which only supports equality in its query requests. The deamon translated those to >=/<= before sending the request to Tendermint.
In @cosmjs/stargate and @cosmjs/cosmwasm-stargate we already use the correct query format before sending the Query to Tendemint: https://github.com/cosmos/cosmjs/blob/v0.24.0-alpha.25/packages/stargate/src/stargateclient.ts#L221-L223
buildQuery already concatenates the individual components via AND:
export function buildQuery(components: BuildQueryComponents): string {
  const tags = components.tags ? components.tags : [];
  const tagComponents = tags.map((tag) => `${tag.key}='${tag.value}'`);
  const rawComponents = components.raw ? [components.raw] : [];

  return [...tagComponents, ...rawComponents].join(" AND ");
}

So I am not sure what is left in this ticket.

Ah, I guess I ended up in launchpad when looking for how to build queries. Guess this is done, and it was user error.
Thanks


Weave scope running in eks throws error messages

What you expected to happen?
I have installed scope using helm into an eks cluster. Everything seems to work fine but my logs get spammed with error messages from weave scope agent.
What happened?
weave/weave-scope-agent-weave-scope-xkxx4[weave-scope-agent]: <probe> WARN: 2019/08/30 12:20:16.948717 No node name and cannot obtain local pods, reporting all (which may impact performance): Get http://<IP_ADDRESS>:10255/pods/: dial tcp <IP_ADDRESS>:10255: connect: connection refused

How to reproduce it?
Install weave scope using the helm chart with default values.
Anything else we need to know?
aws eks cluster
Versions:
weave-scope helm version: 1.1.2
weave-scope image version: tag: master-c99a5e6d
kubectl version 1.13

This is caused by the config. Can you take it up with the maintainer of the helm chart?
Ideally they would make changes in line with #3569

Looks like you've made a PR for the helm chart - thanks!

I was quite happy about the quick response from you so I thought it might be a good idea to help you out here.

My understanding is that this issue has been addressed fully by https://github.com/helm/charts/pull/16796.
@runningman84 feel free to reopen if that is not true. And thanks for your contribution! :)


test: 💍 fix api key test + mock implementation

JIRA Link
N/A
Changelog / Description
postgres api key test was failing async due to a error in the postgres mock. The spec did not fail due to not returning the expect
Checklist -

[ ] New Feature ?
[ ] Updated swagger annotation (if API structure is changed) ?
[X] Unit Test (if possible) ?
[ ] Updated the Readme.md (if required) ?

:tada: This PR is included in version 2.2.0-alpha.6 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.4.0-alpha.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


freshplayerplugin suddenly consume overr 100% cpu and hang

os:openSUSE 13.2
firefox: 14.0.5
chrome-beta: 40.0.2214.38 beta (64-bit)
freshplayerplugin:2.0-32.1
i have already edit file /etc/freshwrapper.conf and edit pepperflash_path's value to '/opt/google/chrome-beta/PepperFlash/libpepflashplayer.so' to make sure freshplayerplugin is using the same ppapi flash as chrome-beta
test link: http://v.youku.com/v_show/id_XODQ3NjM0MjA0.html
when the flash video begins to play, i run pidstat command to watch plugin-container's cpu usage. at first  this process uses about 50% cpu and the video plays as expected. but after about one minute, i find the flash's video hangs and cpu usage is over 100%.
then i open the same link and play with chrome-beta. everything is ok.

@MALLER-LAGOON what system configuration do you think it is ? i have changed freshplayerplugin repo from https://build.opensuse.org/package/show?project=home%3Aandykimpe%3Afreshplayerplugin&package=freshplayerplugin to https://build.opensuse.org/package/show?project=home%3AKenzy%3Apackages&package=freshplayerplugin, but this doesn't help. i also have tried to enable/disable gpu acceleration on video context menu but still doesn't help. or how can i debug this wrapper ? any logs for me to deep into ?

but buddy, have u tried to compile the freshplayer from this github?
the repos that u linked me are very outdated.
also you can try with this application, which download the source code from the master branch of this github, compile it and install it properly to the user from the console.
its very important that u read and follow the instructions to this works properly.
i do it in that way, and i can ensure you, the freshplayer works a lot more stable than a flashplayerplugin-nonfree from the oficial repo of Debian.

@MALLER-LAGOON  as you requested, freshplayerplugin from home:Kenzy:packages updated freshplayerplugin source codes to commit c5694f0 which is commited on Feb 2, 2015. but still the same problem exists. i have tried to tune some parameters (such as enable_3d, comment flash_command_line) but didn't help.

 Although there were memory leaks, which are now fixed.
Can you build a debug build (cmake -DCMAKE_BUILD_TYPE=Debug .. && make) and run a sudo perf top when those high CPU load occur?
(perf is a profiler, and usually a part of linux-tools package. perf top outputs a live list of most CPU expensive functions. It's like top, but more specific. Most probably you'll need to run perf as root.)

right now i cloned freshplayerplugin ( commit 9a3e1f0) and build a debug build on my own machine which can reproduce this issue , but still any videos on http://www.youku.com will hang after about 1minute. the following is sudo perf top snapshot when video hangs.

did u try setting the storage to unlimited?

@MALLER-LAGOON i can not find any similar configurations with local storage. would you please tell me which one it is ?

do a right click on the flash frame-->settings-->local storage.

@MALLER-LAGOON also tried and same problem

this is my debug informations
WARNING: content window passed to PrivateBrowsingUtils.isWindowPrivate. Use isContentWindowPrivate instead (but only for frame scripts).
pbu_isWindowPrivate@resource://gre/modules/PrivateBrowsingUtils.jsm:25:14
injectController@resource://gre/modules/MozSocialAPI.jsm:49:20
exports.Utils.yield@resource://gre/modules/addons/XPIProvider.jsm -> jar:file:///home/bruce/.mozilla/firefox/i7tqmpwq.default-1418924289071/extensions/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D.xpi!/bootstrap.js -> jar:file:///home/bruce/.mozilla/firefox/i7tqmpwq.default-1418924289071/extensions/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D.xpi!/lib/utils.js:380:12
INIParser.prototype.process@resource://gre/modules/addons/XPIProvider.jsm -> jar:file:///home/bruce/.mozilla/firefox/i7tqmpwq.default-1418924289071/extensions/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D.xpi!/bootstrap.js -> jar:file:///home/bruce/.mozilla/firefox/i7tqmpwq.default-1418924289071/extensions/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D.xpi!/lib/filterStorage.js:870:7
exports.IO.readFromFile/onProgress@resource://gre/modules/addons/XPIProvider.jsm -> jar:file:///home/bruce/.mozilla/firefox/i7tqmpwq.default-1418924289071/extensions/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D.xpi!/bootstrap.js -> jar:file:///home/bruce/.mozilla/firefox/i7tqmpwq.default-1418924289071/extensions/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D.xpi!/lib/io.js:97:15
exports.IO.readFromFile/<@resource://gre/modules/addons/XPIProvider.jsm -> jar:file:///home/bruce/.mozilla/firefox/i7tqmpwq.default-1418924289071/extensions/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D.xpi!/bootstrap.js -> jar:file:///home/bruce/.mozilla/firefox/i7tqmpwq.default-1418924289071/extensions/%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D.xpi!/lib/io.js:182:11
TaskImpl_run@resource://gre/modules/Task.jsm:330:41
Handler.prototype.process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:865:23
this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:744:7
NOT SANDBOXED
[fresh 11017] not implemented: PPB_OpenGLES2DrawBuffers(Dev);1.0
[fresh 11017] [PPB] {fake} ppb_video_capture_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {zilch} ppb_network_monitor_update_network_list
[fresh 11017] [PPB] {zilch} ppb_text_input_interface_set_text_input_type instance=10, type=PP_TEXTINPUT_TYPE_DEV_NONE
[fresh 11017] [PPB] {zilch} ppb_flash_set_instance_always_on_top instance=10, on_top=1
[fresh 11017] [PPB] {fake} ppb_video_capture_close
[fresh 11017] [PPB] {fake} ppb_video_capture_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {zilch} ppb_network_monitor_update_network_list
[fresh 11017] [PPB] {zilch} ppb_text_input_interface_set_text_input_type instance=11, type=PP_TEXTINPUT_TYPE_DEV_NONE
[fresh 11017] [PPB] {zilch} ppb_flash_set_instance_always_on_top instance=11, on_top=1
[fresh 11017] [PPB] {fake} ppb_video_capture_close
[fresh] [warning] handle_tcp_connect_stage2, evdns returned code 3, count = 0 (localhost:843)
[fresh] [warning] ppb_tcp_socket_get_local_address, not connected
[fresh] [warning] ppb_tcp_socket_get_remote_address, not connected
[fresh 11017] [PPB] {fake} ppb_video_capture_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {zilch} ppb_network_monitor_update_network_list
[fresh 11017] [PPB] {zilch} ppb_text_input_interface_set_text_input_type instance=12, type=PP_TEXTINPUT_TYPE_DEV_NONE
[fresh] [warning] handle_tcp_connect_stage2, evdns returned code 3, count = 0 (localhost:8909)
[fresh] [warning] ppb_tcp_socket_get_local_address, not connected
[fresh] [warning] ppb_tcp_socket_get_remote_address, not connected
[fresh 11017] [PPB] {fake} ppb_video_capture_close
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {zilch} ppb_udp_socket_bind udp_socket=1547, addr=0x7f2e04bfd9b0, callback={.func=0x7f2e06254c00, .user_data=0x7f2e018ce0b0, .flags=0}
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh] [warning] handle_tcp_connect_stage2, evdns returned code 3, count = 0 (localhost:843)
[fresh] [warning] ppb_tcp_socket_get_local_address, not connected
[fresh] [warning] ppb_tcp_socket_get_remote_address, not connected
[fresh] [warning] handle_tcp_connect_stage2, evdns returned code 3, count = 0 (localhost:8909)
[fresh] [warning] ppb_tcp_socket_get_local_address, not connected
[fresh] [warning] ppb_tcp_socket_get_remote_address, not connected
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh] [warning] handle_tcp_connect_stage2, evdns returned code 3, count = 0 (localhost:843)
[fresh] [warning] ppb_tcp_socket_get_local_address, not connected
[fresh] [warning] ppb_tcp_socket_get_remote_address, not connected
[fresh] [warning] handle_tcp_connect_stage2, evdns returned code 3, count = 0 (localhost:8909)
[fresh] [warning] ppb_tcp_socket_get_local_address, not connected
[fresh] [warning] ppb_tcp_socket_get_remote_address, not connected
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {zilch} ppb_udp_socket_bind udp_socket=4688, addr=0x7f2e04bfd9b0, callback={.func=0x7f2e06254c00, .user_data=0x7f2e018ceec0, .flags=0}
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh] [warning] handle_tcp_connect_stage2, evdns returned code 3, count = 0 (localhost:843)
[fresh] [warning] ppb_tcp_socket_get_local_address, not connected
[fresh] [warning] ppb_tcp_socket_get_remote_address, not connected
[fresh] [warning] handle_tcp_connect_stage2, evdns returned code 3, count = 0 (localhost:8909)
[fresh] [warning] ppb_tcp_socket_get_local_address, not connected
[fresh] [warning] ppb_tcp_socket_get_remote_address, not connected
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh] [warning] handle_tcp_connect_stage2, evdns returned code 3, count = 0 (localhost:843)
[fresh] [warning] ppb_tcp_socket_get_local_address, not connected
[fresh] [warning] ppb_tcp_socket_get_remote_address, not connected
[fresh] [warning] handle_tcp_connect_stage2, evdns returned code 3, count = 0 (localhost:8909)
[fresh] [warning] ppb_tcp_socket_get_local_address, not connected
[fresh] [warning] ppb_tcp_socket_get_remote_address, not connected
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh] [warning] handle_tcp_connect_stage2, evdns returned code 3, count = 0 (localhost:843)
[fresh] [warning] ppb_tcp_socket_get_local_address, not connected
[fresh] [warning] ppb_tcp_socket_get_remote_address, not connected
[fresh] [warning] handle_tcp_connect_stage2, evdns returned code 3, count = 0 (localhost:8909)
[fresh] [warning] ppb_tcp_socket_get_local_address, not connected
[fresh] [warning] ppb_tcp_socket_get_remote_address, not connected
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh] [warning] handle_tcp_connect_stage2, evdns returned code 3, count = 0 (localhost:843)
[fresh] [warning] ppb_tcp_socket_get_local_address, not connected
[fresh] [warning] ppb_tcp_socket_get_remote_address, not connected
[fresh] [warning] handle_tcp_connect_stage2, evdns returned code 3, count = 0 (localhost:8909)
[fresh] [warning] ppb_tcp_socket_get_local_address, not connected
[fresh] [warning] ppb_tcp_socket_get_remote_address, not connected
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
WARNING: content window passed to PrivateBrowsingUtils.isWindowPrivate. Use isContentWindowPrivate instead (but only for frame scripts).
pbu_isWindowPrivate@resource://gre/modules/PrivateBrowsingUtils.jsm:25:14
injectController@resource://gre/modules/MozSocialAPI.jsm:49:20
[fresh 11017] [PPB] {fake} ppb_video_capture_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {zilch} ppb_network_monitor_update_network_list
[fresh 11017] [PPB] {zilch} ppb_text_input_interface_set_text_input_type instance=13, type=PP_TEXTINPUT_TYPE_DEV_NONE
[fresh 11017] [PPB] {fake} ppb_video_capture_close
WARNING: content window passed to PrivateBrowsingUtils.isWindowPrivate. Use isContentWindowPrivate instead (but only for frame scripts).
pbu_isWindowPrivate@resource://gre/modules/PrivateBrowsingUtils.jsm:25:14
injectController@resource://gre/modules/MozSocialAPI.jsm:49:20
[fresh 11017] [PPB] {fake} ppb_video_capture_enumerate_devices
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices
[fresh 11017] [PPB] {zilch} ppb_network_monitor_update_network_list
[fresh 11017] [PPB] {zilch} ppb_text_input_interface_set_text_input_type instance=14, type=PP_TEXTINPUT_TYPE_DEV_NONE
[fresh 11017] [PPB] {fake} ppb_video_capture_close
[fresh 11017] [PPB] {fake} ppb_audio_input_enumerate_devices

I'm trying to reproduce the issue in virtual machine with OpenSUSE 13.2 installed, but with no success.
As a wild guess, try to temporarily rename /usr/lib64/gtk-2.0/2.10.0/engines/liboxygen-gtk.so. In my experiments it showed some errors when run under Valgrind.

From debug log you attached, I can say your system have troubles resolving localhost. Is ping localhost works on your machine?
It could be you don't have <IP_ADDRESS>	localhost line in your /etc/hosts. That can cause errors in other network-related applications too.

From debug log you attached, I can say your system have troubles resolving localhost. Is ping localhost works on your machine?
It could be you don't have <IP_ADDRESS> localhost line in your /etc/hosts. That can cause errors in other network-related applications too.

no, i can ping localhost, i also have <IP_ADDRESS> localhost line in my /etc/hosts

try to temporarily rename /usr/lib64/gtk-2.0/2.10.0/engines/liboxygen-gtk.so

i tried and didn't fix my problem.

i also diabled all plugins except this one, disabled all extensions, cleaned all caches and cookies etc ,still didnt' solve my problem.

maybe this is the right place to write this
When l played the game http://www.kongregate.com/games/KintoGames/bit-dungeon
with the freshplayerplugin and clicked somewhere to walk with the character, the game is freezed a bit and then the charakter is near the place where it should walk.
l switched back to flashplugin-installer and l can watch the character starting to walk.
l don't use hardware accelerating.

again i git-pulled and compiled, and found this problem is gone with  52b52e735206ff72f8f8c057b8e83e165da54d76 !

Is it fixed in the ppa, too?

and found this problem is gone

Good to hear that (because I have no idea how to reproduce it and therefore, to fix). Could you also check the most recent version from master branch? I've put there some changes, hope they're not breaking it again.


change node_.get() to this in src/runtime/module.cc

Thanks for contributing to TVM!   Please refer to guideline https://docs.tvm.ai/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from Reviewers by @ them in the pull request thread.

@zhiics @wweic @kevinthesun  pls take a look.


Popover component IE compatibility

Each popover component was sending Events to close other popovers when opening. Since the new Event('hide') syntax is not supported in IE11, this change will increase cross-browser compatibility. Without this, you can get errors if a popover is expanded when another popover tries to expand. This would fix Issue #846 .

Coverage decreased (-0.4%) to 95.87% when pulling 3e12f62559f26a0435da1eea53de3f68ca122eb4 on rmc00:ie11-event-no-polyfill into 1a1edf3b35e30ef4e4d283816a342d00f48ff909 on mseemann:master.

Coverage increased (+0.2%) to 96.522% when pulling f787068a0a8d9a693ae756b7d8261ecdf547b953 on rmc00:ie11-event-no-polyfill into 1a1edf3b35e30ef4e4d283816a342d00f48ff909 on mseemann:master.

Coverage increased (+0.2%) to 96.507% when pulling 1f3d67aa21b938fb85638dac4dcc4a190e1b5c0b on rmc00:ie11-event-no-polyfill into 1a1edf3b35e30ef4e4d283816a342d00f48ff909 on mseemann:master.

@tb Thanks for your feedback. You're correct about how I was creating the CustomEvent before, so I've gone back to the new CustomEvent('hide') syntax, which should hopefully resolve your concern, and I added a small polyfill for that constructor based on this one from MDN.

Coverage increased (+0.2%) to 96.507% when pulling bc74889e9628bdc2dd1dda1fa09acea315f060cb on rmc00:ie11-event-no-polyfill into 1a1edf3b35e30ef4e4d283816a342d00f48ff909 on mseemann:master.

@mseemann @tb Thanks for the feedback on handling polyfills. I went ahead and removed the polyfill from the E2E app. I can add the polyfill into a polyfills.ts file in the popover package if you'd like. At least this way, the IE11 bug can be resolved by adding the CustomEvent polyfill into applications, which I don't think could be done with regular events before.

@mseemann @tb Is it possible to merge this PR? I'd love to move forward with this if possible. I think I've addressed all feedback -- please let me know if that is not the case.

@mseemann I think its fine, it comes down to change Event to CustomEvent. However we might need to mention including https://www.npmjs.com/package/custom-event-polyfill

ok. i have to increase the versions for select and fab-menu too - because of the umd bundle problem.

published


Loading config message in forked instances

Hi,
I was adding the required update to my library to allow coverage of forked node instances and noticed that each instance was displaying on the console the fact that istanbul was loading its configuration from a file.
I could silence this output by using the silent option of my forked process, but looking at the source of istanbul, I was wondering if it was a console forgotten by mistake ?
The line seems to be here: https://github.com/gotwarlost/istanbul/blob/master/lib/config.js#L425
Could that output be removed or at least made optional (via the verbose argument maybe) ?
Thanks in advance.

Do you want to send a PR for this? Seems fair that the line should only be printed in verbose mode.

Sure, I'll do it tonight after work.

done: https://github.com/gotwarlost/istanbul/pull/442
thanks.

Merged.

tks !


ENG-1726 - Add disabled attribute to text element docs

Description

Adds documentation for the disabled attribute for the TextElement

Testing required outside of automated testing?

[x] Not Applicable

Screenshots (if appropriate):

[ ] Not Applicable

Rollback / Rollforward Procedure

[x] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

:tada: This PR is included in version 1.16.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


and the symbol (@)

We are not using the @ symbol but a unicode symbol which looks just like it. This way the addresses cannot be scraped as email addresses and spammed. It seems that your default browser font is missing this unicode character. Unfortunately we don't have any control over installed fonts, and selecting a font specifier that will work cross-platform for some symbols is very hard. If you provide your platform (browser and operating system) I'll see if I can come up with something.

debian os
seamonkey browser

I don't have a Debian platform handy but it did display on Ubuntu 14.04 with the latest Seamonkey. I'm assuming that the default font for this page is freesans on Linux (this is what we've specified). I've checked with LibreOffice and the character &xFF20; displays fine in FreeSans, so I would recommend installing or updating that font. It's possible that Debian stable version of FreeSans is a bit older and may be lacking some of these extended characters. I don't have an easy way of checking that currently.


Scrollbar thumb drag gestures now produce one start and one end scroll notification

The scroll notification events reported for a press-drag-release gesture within a scrollable on a touch screen device begin with a ScrollStartNotification, followed by a series of ScrollUpdateNotifications, and conclude with a ScrollEndNotification. This protocol can be used to defer work until an interactive scroll gesture ends. For example, you might defer updating a scrollable's contents via network requests until the scroll has ended, or you might want to automatically auto-scroll at that time.
In the example that follows the CustomScrollView automatically scrolls so that the last partially visible fixed-height item is completely visible when the scroll gesture ends. Many iOS applications do this kind of thing. It only makes sense to auto-scroll when the user isn't actively dragging the scrollable around.
It's easy enough to do this by reacting to a ScrollEndNotifcation by auto-scrolling to align the last fixed-height list item (source code).
https://github.com/flutter/flutter/assets/1377460/a6e6fc77-6742-4f98-81ba-446536535f73
Dragging the scrollbar thumb in a desktop application is a similar user gesture. Currently it's not possible to defer work or auto-scroll (or whatever) while the scrollable is actively being dragged via the scrollbar thumb because each scrollbar thumb motion is mapped to a scroll start - scroll update - scroll end series of notifications.  On a desktop platform, the same code behaves quite differently when the scrollbar thumb is dragged.
https://github.com/flutter/flutter/assets/1377460/2593d8a3-639c-407f-80c1-6e6f67fb8c5f
The stream of scroll-end events triggers auto-scrolling every time the thumb moves. From the user's perspective this feels like a losing struggle.
One can also detect the beginning and end of a touch-drag by listening to the value of a ScrollPosition's isScrollingNotifier. This approach suffers from a similar problem: during a scrollbar thumb-drag, the isScrollingNotifier value isn't updated at all.
This PR refactors the RawScrollbar implementation to effectively use a ScrollDragController to manage scrolls caused by dragging the scrollbar's thumb. Doing so means that dragging the thumb will produce the same notifications as dragging the scrollable on a touch device.
Now desktop applications can choose to respond to scrollbar thumb drags in the same that they respond to drag scrolling on a touch screen. With the changes included here, the desktop or web version of the app works as expected, whether you're listing to scroll notifications or the scroll position's isScrollingNotifier.
https://github.com/flutter/flutter/assets/1377460/67435c40-a866-4735-a19b-e3d68eac8139
This PR also makes the second ScrollPosition API doc example work as expected when used with the DartPad that's  part of API doc page.
Desktop applications also see scroll start-update-end notifications due to the mouse wheel.  There is no touch screen analog for the mouse wheel, so an application that wanted to enable this kind of auto-scrolling alignment would have to include a heuristic that dealt with the sequence of small scrolls triggered by the mouse wheel. Here's an example of that: source code. This version of the app does not auto-align in response to small changes, wether they're triggered by dragging the scrollbar thumb of the mouse wheel.
Related sliver utility PRs: https://github.com/flutter/flutter/pull/143538,  https://github.com/flutter/flutter/pull/143196, https://github.com/flutter/flutter/pull/143325.

Hmm, this makes me wonder if folks that wanted to do this would be better off listening to the isScrollingNotifier on the position?

See https://github.com/flutter/flutter/pull/146654#discussion_r1625026881

This PR seems cause a regression issue when there is a nested ListViews:)
Here is the sample code to test. In the demo, I'm trying to scroll to the right, but it doesn't work all the time and vertical thumb bar looks highlighted even when I scroll horizontally.
https://github.com/flutter/flutter/assets/36861262/0e2cece3-0c13-4b8a-b56b-80dc261e07d9

import 'package:flutter/material.dart';

void main() => runApp(const CarouselExampleApp());

class CarouselExampleApp extends StatelessWidget {
  const CarouselExampleApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      debugShowCheckedModeBanner: false,
      home: Scaffold(
        appBar: AppBar(
          title: const Text('Sample'),
        ),
        body: const CarouselExample(),
      ),
    );
  }
}

class CarouselExample extends StatefulWidget {
  const CarouselExample({super.key});

  @override
  State<CarouselExample> createState() => _CarouselExampleState();
}

class _CarouselExampleState extends State<CarouselExample> {
  @override
  Widget build(BuildContext context) {
    return ListView(
      children: <Widget>[
        Container(
          width: 200,
          height: 200,
          color: Colors.amber[50],
        ),
        Center(
          child: ConstrainedBox(
            constraints: const BoxConstraints(maxHeight: 200),
            child: ListView(
              scrollDirection: Axis.horizontal,
              children: List.generate(20, (int index) {
                return ConstrainedBox(constraints: BoxConstraints.tightFor(width: 200), child: Card.outlined(child: SizedBox(width: 200, height: 200, child: Center(child: Text('Item $index')),),),);
              }),
            )
          ),
        ),
        Container(
          width: 200,
          height: 200,
          color: Colors.amber[100],
        ),
        Container(
          width: 200,
          height: 200,
          color: Colors.amber[200],
        ),
      ],
    );
  }
}

CC: @Piinks

@QuncCccccc can you put that in a new issue and cc @HansMuller?
I know there are some other regressions around this as well, should we consider reverting it until all of the issues are resolved?


Exposes surf's with_http_client

Description
Exposed Surf's with_http_client to allow users to more granularity in their HTTP clients. One use case is creating a isahc HttpClient with HTTP basic auth
let http_client = isahc::HttpClientBuilder::new().authentication(Authentication::basic()).build()?;
let client =<EMAIL_ADDRESS>"database").with_auth("user", "pass").with_http_client(http_client);

Maintenance considerations
If the project moves away from surf this function will need to be under a surf feature. This function does make moving away from surf a semver major change, looking at https://github.com/Empty2k12/influxdb-rust/pull/92 it appears a sermver breaking change when moving away from surf is planned.
Checklist

[X] Formatted code using cargo fmt --all
[X] Linted code using clippy cargo clippy --all-targets --all-features -- -D warnings

NOTE: There are a couple existing errors trait objects without an explicit dyn are deprecated.

[X] Updated README.md using cargo readme -r influxdb -t ../README.tpl > README.md
[X] Reviewed the diff. Did you leave any print statements or unnecessary comments?
[X] Any unfinished work that warrants a separate issue captured in an issue with a TODO code comment

@Empty2k12 thoughts?

Thanks for your PR!
Please merge/rebase main. The compilation failure should go away. Also, #92 has been merged.

Exposed under the "surf" feature. Do you prefer a separate function with_http_client (as is), or a separate new new_with_http_client?

I think I prefer the former. Is there a reason why we don't make a client-agnostic Client::with_http_client(c: HttpClient) that just replaces self.client directly?

I think I prefer the former. Is there a reason why we don't make a client-agnostic Client::with_http_client(c: HttpClient) that just replaces self.client directly?

Fair point!


Adding support to enable tracing in tsi.

I want to get Travis sorted out completely before merging this.

I think Travis is now sorted out enough so we should be able to merge this - if @jboeuf would be kind enough to pull from master in order to update this PR.

I'd actually put Ruby being up as the threshold for things being
operational enough to start taking C core changes.
On Thu, Feb 26, 2015 at 10:18 PM Nicolas Noble<EMAIL_ADDRESS>wrote:

I think Travis is now sorted out enough so we should be able to merge this

if @jboeuf https://github.com/jboeuf would be kind enough to pull
from master in order to update this PR.

—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/854#issuecomment-76345338.

(I realize the likelyhood of this change breaking things is low, but I want
to be consistent here)
On Thu, Feb 26, 2015 at 10:21 PM Craig Tiller<EMAIL_ADDRESS>wrote:

I'd actually put Ruby being up as the threshold for things being
operational enough to start taking C core changes.
On Thu, Feb 26, 2015 at 10:18 PM Nicolas Noble<EMAIL_ADDRESS>wrote:

I think Travis is now sorted out enough so we should be able to merge
this - if @jboeuf https://github.com/jboeuf would be kind enough to
pull from master in order to update this PR.
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/854#issuecomment-76345338.

Hm, fair enough.
On Thu, Feb 26, 2015 at 10:21 PM, Craig Tiller<EMAIL_ADDRESS>wrote:

I'd actually put Ruby being up as the threshold for things being
operational enough to start taking C core changes.
On Thu, Feb 26, 2015 at 10:18 PM Nicolas Noble<EMAIL_ADDRESS>wrote:

I think Travis is now sorted out enough so we should be able to merge
this

if @jboeuf https://github.com/jboeuf would be kind enough to pull
from master in order to update this PR.

—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/854#issuecomment-76345338.

—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/854#issuecomment-76345537.

I pulled from master and travis is happy now...

Can you merge head once more and push: tests are to where I'm happy with them now.

Done.


Update setup.cfg with Pydantic range

Earth-2 MIP Pull Request
Description

Limiting range of Pydantic to 1.0. 2.0 is not supported right now
Fixes: https://github.com/NVIDIA/earth2mip/issues/26
Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.
[x] The CHANGELOG.md is up to date with these changes.
[x] An issue is linked to this pull request.

Dependencies

/blossom-ci


'selectHighlights' doesn't select highlights

VSCode Version: 1.40.2
OS Version: Ubuntu 16.04

Does this issue occur when all extensions are disabled?: Yes
This is the action bound to ctrl-shift-l by default.
There seems to be a mismatch between the action name (editor.action.selectHighlights) and its textual description (Select All Occurrences of Find Match). The behaviour seems to correspond to the latter.
For background, I am using a Haskell LSP plugin. When my cursor is on a variable or function name, all occurrences in the file are highlighted. This is the same information I get from the references view. But when I call selectHighlights, the editor seems to do a dumb text search - i.e. other entities, in other scopes, with the same name, are also selected. This is useless.
So is there actually any way to select all currently highlighted strings in the editor?

This is a bug, not a feature request!


ci(nvmrc): use .nvmrc for ci

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


AppState changes to active when app receives notification in killed state

I am able to receive notification in all 3 states (killed/foreground/background).
The data gets printed in console when the notification arrives, however I was not receiving any data from the notification when clicked on it from the notification tray.

When I just send data, I can see the data getting printed in console the moment I send the notification but no icon in the notification array,

const payload = {
  data: {
    title: 'Hi',
    body: 'body',
    message: 'Message',
  }
}

When I just send data with notification, I can see icon in the notification array, but when I click on it, there is no data passed to the application in background and killed state

const payload = {
  data: {
    title: 'Hi',
    body: 'body',
    message: 'Message',
  },
  notification: {
    title: 'Hi',
    body: 'body',
    message: 'Message',
  }
}

Updated: When I just send data with custom_notification, I can see icon in the notification array with data getting printed in the console as soon as the notification arrives in the notification tray, but when I click on it, there is no data passed to the application in background and killed state.

const payload = {
  data: {
    custom_notification: {
      title: 'Hi',
      body: 'body',
      message: 'Message',
    }
  },
}

So, finally I decided to save data in asyncStorage whenever I receive the notification and if the user clicks on it I retrieve the notification data from storage. For this I heavily rely on appState.
The main problem here is that, when app is in killed state, I manage to store the data, but my function is unable to run as the AppState gets set as active when the notification arrives in killed state. Now when I click on the notification the AppState still remains active and my handler does not run at all.
RN: 0.45.1, FCM: 13.3.1

what OS?

Its Android, testing on 8.0
On 23-Feb-2018 8:55 PM, "Libin Lu"<EMAIL_ADDRESS>wrote:

what OS?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/evollu/react-native-fcm/issues/808#issuecomment-368039877,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AG8x8L2b2YJOba9oWqaj9fkg-TKJ31HRks5tXthSgaJpZM4SQZm-
.

const payload = {
  data: {
    custom_notificaiton: {
      title: 'Hi',
      body: 'body',
      message: 'Message',
      key: 'val',
      key2: 'val2'
    }
  }
}

@evollu it was typo above, I am using custom_notification. So the app is working fine.  But there is one issue alone now. Let's say that the app is in killed state, and then I receive a notification, I tap on it and I get to the desired screen. Now if I receive any notification background/foreground and click on the notification, the tap on the notification does not take me to any screen.
2nd scenario: App is in killed state, now I open the app from the app icon from the phone's launcher. I receive a notification whether the app is in foreground/background, tapping the notification takes me to the  desired screen. I kill the app receive a notification, tap it, and it works but this breaks the future notifications that receive in foreground/background.

are you handling the navigation logic in both getInitialNotification and notification callback?

Yes, basically when I get the notification, and if the app is running in
background/foreground/killed state, the notification data gets printed from
on Notification handler, so here I store the data in asyncStorage. Now
when I click on the notification (this click event is captured by on
Notification listener), I just get keys inside the notification payload,
opened_from_tray, fcm: {action: null}, , so when opened_from_tray is
present I fetch the data from storage and then handle the navigation.
Similarly when the app is in killed state, notification arrives data is
stored in storage. Later when user clicks on the notification, app becomes
active, and the click is registered in getInitialNotification listener
which contains opened_from_tray key, and then again I fetch data from
storage and route accordingly.
On Sat 24 Feb, 2018, 10:22 PM Libin Lu<EMAIL_ADDRESS>wrote:

are you handling the navigation logic in both getInitialNotification and
notification callback?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/evollu/react-native-fcm/issues/808#issuecomment-368241826,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AG8x8NOts18R7ZqD5HI87HOsu7jTOFBBks5tYD5IgaJpZM4SQZm-
.

custom notification should contain your data when you tap on the notification. have you tried with example app?

I have taken the listener code from your example app only. The only difference is you send remote notifications from within the app, I am testing it from a php script and Firebase console:
PHP script: custom_notification's value is received as a stringified JSON string in the console on its arrival. But I click on it, the app only gets 3 keys inside notif:
fcm: {
 action: null,
body: null,
},
opened_from_tray: true,

$url = 'https://android.googleapis.com/gcm/send';
$fields = array(
        'registration_ids'  => $registrationIDs,
        "data" => array(
          "priority"=> "high",
          "show_in_foreground" => true,
          'deeplink'=>'deeplink',
          'page_url'=>'some_url',
          'image'=>'image.png',
          'type' => 'DEEPLINK',
          'source' => 'notification',
          'title'=> 'Blog',
          "custom_notification" => array(
            'body' => 'Blog content',
            "sound" => "default",
            "vibrate" => 300,
            "lights" => true,
            "show_in_foreground"=> true,
          )
        ),
);

I am not sure exactly how I can create the payload as data: { custom_notification: value} from firebase console.

Check if you have received notification in getInitialNotification event in this scenario.
FCM.getInitialNotification().then(notif => {
alert(JSON.stringify(notif));
});
Let us know then we can check it further.

@sfm2222 it works as written in iOS with this payload, I get opened_from_tray: true with the data on clicking the notification. But in Android I do not get any data when I click on notification, I get it when the notification arrives, so I store it in storage.
FCM.getInitialNotification always returns this in android alone:

@evollu still i'm getting below msg only in android if i opened app .How to fix this
{
  "content_available": false,
   "notification": {
       "title": "hello",
       "body": "yo"
   },
   "data": {
       "extra":"juice"
   },
  "to":"cbGVdEcQcl5pXvT8wBqo1e8I_nALw7czQaymhDRa1ol0IZD4KV2GVqmDANy6_oJcphyIizEkF9LLtyf18FnYXvd6buARv60y8MLlGds-jpQUvqOPs7Xiat0DV-HiPwmNSPRmZAbn"
}

{ opened_from_tray: 1, fcm: { action: 'android.intent.action.MAIN' } }

{ opened_from_tray: 1, fcm: { action: 'android.intent.action.MAIN' } } is expected for android. When you launch your app though icon, system pass this as initial notification.
you can ignore this.

@evollu I Understood.but if i sent below payload while app in closed/killed state.After opening app i'm not getting that notification data.How to get that data or How to get hidden notification data ?
{
  "content_available": true,
   "data": {
       "extra":"juice"
   },
"to":"cbGVdEcQcl5pXvT8wBqo1e8I_nALw7czQaymhDRa1ol0IZD4KV2GVqmDANy6_oJcphyIizEkF9LLtyf18FnYXvd6buARv60y8MLlGds-jpQUvqOPs7Xiat0DV-HiPwmNSPRmZAbn"
}

so console.log("INITIAL NOTIFICATION", notif) gives  you { opened_from_tray: 1, fcm: { action: 'android.intent.action.MAIN' } }?
is your react activity your main activity? some people have the issue when they use a splash screen as main

@evollu yes i am getting this log from console.log(). i am not using any splash screen...
Main activity
package com.agencyauto;

import android.content.Intent;

import com.facebook.react.ReactActivity;

public class MainActivity extends ReactActivity {

    @Override
    public void onNewIntent(Intent intent) {
        super.onNewIntent(intent);
        setIntent(intent);
    }
    /**
     * Returns the name of the main component registered from JavaScript.
     * This is used to schedule rendering of the component.
     */
    @Override
    protected String getMainComponentName() {
        return "AgencyAuto";
    }
}

Manifest xml
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="com.agencyauto">

    <uses-permission android:name="android.permission.INTERNET" />
    <uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW"/>
    <uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED" />
    <uses-permission android:name="android.permission.VIBRATE" />

    <application
      android:name=".MainApplication"
      android:label="@string/app_name"
      android:icon="@mipmap/ic_launcher"
      android:allowBackup="false"
      android:theme="@style/AppTheme">
      <meta-data android:name="com.google.firebase.messaging.default_notification_icon" android:resource="@mipmap/ic_launcher"/>

      <service android:name="com.evollu.react.fcm.MessagingService" android:enabled="true" android:exported="true">
        <intent-filter>
          <action android:name="com.google.firebase.MESSAGING_EVENT"/>
        </intent-filter>
      </service>

      <service android:name="com.evollu.react.fcm.InstanceIdService" android:exported="false">
        <intent-filter>
          <action android:name="com.google.firebase.INSTANCE_ID_EVENT"/>
        </intent-filter>
      </service>
      <activity
        android:name=".MainActivity"
        android:label="@string/app_name"
        android:launchMode="singleTop"
        android:configChanges="keyboard|keyboardHidden|orientation|screenSize"
        android:windowSoftInputMode="adjustResize">
        <intent-filter>
            <action android:name="android.intent.action.MAIN" />
            <category android:name="android.intent.category.LAUNCHER" />
        </intent-filter>
      </activity>
      <activity android:name="com.facebook.react.devsupport.DevSettingsActivity" />

      <receiver android:name="com.evollu.react.fcm.FIRLocalMessagingPublisher"/>
      <receiver android:enabled="true" android:exported="true"  android:name="com.evollu.react.fcm.FIRSystemBootEventReceiver">
          <intent-filter>
              <action android:name="android.intent.action.BOOT_COMPLETED"/>
              <action android:name="android.intent.action.QUICKBOOT_POWERON"/>
              <action android:name="com.htc.intent.action.QUICKBOOT_POWERON"/>
              <category android:name="android.intent.category.DEFAULT" />
          </intent-filter>
      </receiver>
    </application>

</manifest>

App Gradle
apply plugin: "com.android.application"

import com.android.build.OutputFile

/**
 * The react.gradle file registers a task for each build variant (e.g. bundleDebugJsAndAssets
 * and bundleReleaseJsAndAssets).
 * These basically call `react-native bundle` with the correct arguments during the Android build
 * cycle. By default, bundleDebugJsAndAssets is skipped, as in debug/dev mode we prefer to load the
 * bundle directly from the development server. Below you can see all the possible configurations
 * and their defaults. If you decide to add a configuration block, make sure to add it before the
 * `apply from: "../../node_modules/react-native/react.gradle"` line.
 *
 * project.ext.react = [
 *   // the name of the generated asset file containing your JS bundle
 *   bundleAssetName: "index.android.bundle",
 *
 *   // the entry file for bundle generation
 *   entryFile: "index.android.js",
 *
 *   // whether to bundle JS and assets in debug mode
 *   bundleInDebug: false,
 *
 *   // whether to bundle JS and assets in release mode
 *   bundleInRelease: true,
 *
 *   // whether to bundle JS and assets in another build variant (if configured).
 *   // See http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Build-Variants
 *   // The configuration property can be in the following formats
 *   //         'bundleIn${productFlavor}${buildType}'
 *   //         'bundleIn${buildType}'
 *   // bundleInFreeDebug: true,
 *   // bundleInPaidRelease: true,
 *   // bundleInBeta: true,
 *
 *   // whether to disable dev mode in custom build variants (by default only disabled in release)
 *   // for example: to disable dev mode in the staging build type (if configured)
 *   devDisabledInStaging: true,
 *   // The configuration property can be in the following formats
 *   //         'devDisabledIn${productFlavor}${buildType}'
 *   //         'devDisabledIn${buildType}'
 *
 *   // the root of your project, i.e. where "package.json" lives
 *   root: "../../",
 *
 *   // where to put the JS bundle asset in debug mode
 *   jsBundleDirDebug: "$buildDir/intermediates/assets/debug",
 *
 *   // where to put the JS bundle asset in release mode
 *   jsBundleDirRelease: "$buildDir/intermediates/assets/release",
 *
 *   // where to put drawable resources / React Native assets, e.g. the ones you use via
 *   // require('./image.png')), in debug mode
 *   resourcesDirDebug: "$buildDir/intermediates/res/merged/debug",
 *
 *   // where to put drawable resources / React Native assets, e.g. the ones you use via
 *   // require('./image.png')), in release mode
 *   resourcesDirRelease: "$buildDir/intermediates/res/merged/release",
 *
 *   // by default the gradle tasks are skipped if none of the JS files or assets change; this means
 *   // that we don't look at files in android/ or ios/ to determine whether the tasks are up to
 *   // date; if you have any other folders that you want to ignore for performance reasons (gradle
 *   // indexes the entire tree), add them here. Alternatively, if you have JS files in android/
 *   // for example, you might want to remove it from here.
 *   inputExcludes: ["android/**", "ios/**"],
 *
 *   // override which node gets called and with what additional arguments
 *   nodeExecutableAndArgs: ["node"],
 *
 *   // supply additional arguments to the packager
 *   extraPackagerArgs: []
 * ]
 */

project.ext.react = [
    entryFile: "index.js"
]

apply from: "../../node_modules/react-native/react.gradle"

/**
 * Set this to true to create two separate APKs instead of one:
 *   - An APK that only works on ARM devices
 *   - An APK that only works on x86 devices
 * The advantage is the size of the APK is reduced by about 4MB.
 * Upload all the APKs to the Play Store and people will download
 * the correct one based on the CPU architecture of their device.
 */
def enableSeparateBuildPerCPUArchitecture = false

/**
 * Run Proguard to shrink the Java bytecode in release builds.
 */
def enableProguardInReleaseBuilds = false

android {
    compileSdkVersion 23
    buildToolsVersion '27.0.3'

    defaultConfig {
        applicationId "com.agencyauto"
        minSdkVersion 16
        targetSdkVersion 22
        versionCode 1
        versionName "1.0"
        ndk {
            abiFilters "armeabi-v7a", "x86"
        }
    }
    splits {
        abi {
            reset()
            enable enableSeparateBuildPerCPUArchitecture
            universalApk false  // If true, also generate a universal APK
            include "armeabi-v7a", "x86"
        }
    }
    buildTypes {
        release {
            minifyEnabled enableProguardInReleaseBuilds
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
        }
    }
    // applicationVariants are e.g. debug, release
    applicationVariants.all { variant ->
        variant.outputs.each { output ->
            // For each separate APK per architecture, set a unique version code as described here:
            // http://tools.android.com/tech-docs/new-build-system/user-guide/apk-splits
            def versionCodes = ["armeabi-v7a":1, "x86":2]
            def abi = output.getFilter(OutputFile.ABI)
            if (abi != null) {  // null for the universal-debug, universal-release variants
                output.versionCodeOverride =
                        versionCodes.get(abi) * 1048576 + defaultConfig.versionCode
            }
        }
    }
}

dependencies {
    compile project(':react-native-fcm')
    compile project(':react-native-vector-icons')
    compile fileTree(dir: "libs", include: ["*.jar"])
    compile "com.android.support:appcompat-v7:23.0.1"
    compile "com.facebook.react:react-native:+"  // From node_modules
}

// Run this once to be able to run the application with BUCK
// puts all compile dependencies into folder libs for BUCK to use
task copyDownloadableDepsToLibs(type: Copy) {
    from configurations.compile
    into 'libs'
}

apply plugin: 'com.google.gms.google-services'

@balapkm you need to store the notification payload when it arrives in sleep/killed state using AsyncStorage and then when the user actually clicks on it, read it from AsyncStorage.
If you add a listener for killed state you will notice that the app receives the payload in killed state but when the user clicks on the notification the payload gets lost.

@sahil290791 Now it's working fine.Thank you very much.
@evollu Thank you very much for your response

@sahil290791 Can you help me how to listen to notification and store it using AsyncStorage when app is killed? And what shall be the payload structure for that, whether custom_notification or only data or only notification we have to send?
I tried the example but the problem is that the app is not storing data in killed state.
Actually I want to accumulate all the notification and show all the notification as one notification... But it has taken too much time of mine...
Please help me...

@Louies89 this is how I am handling it in iOS/Android, the below logic has worked for me so far.
I compile my android app using SDK 26, for that I had to use react-native-fcm/sdk-26 branch and I have tested it on devices running Android 5+ onwards till Android 9 beta.
Let me know if you have any queries, this might not be the best way of handling notifications.
class Home extends Component {
  constructor() {
    this._onTokenRegister = this._onTokenRegister.bind(this);
    this._onPushNotification = this._onPushNotification.bind(this);
    this._handleAppStateChange = this._handleAppStateChange.bind(this);
    this.handleNotificationFromKilledState = this.handleNotificationFromKilledState.bind(this);
  }

  async componentDidMount() {
    registerAppListener(this._onPushNotification, this._handleOpenURL);
    AppState.addEventListener('change', this._handleAppStateChange);
    this.handleNotificationFromKilledState();

    try {
      await FCM.requestPermissions({ badge: false, sound: true, alert: true });
    } catch (e) {
      Sentry.captureException(e);
    }
    this._registerDevice();
  }

  handleNotificationFromKilledState() {
    FCM.getInitialNotification().then((notif) => {
      if (notif && notif.opened_from_tray) {
        if (!isUndefined(notif.title)) {
          this._onPushNotification(notif);
        } else {
          AsyncStorage.getItem('lastNotification').then((data) => {
            const notification = isEmpty(data) ? {} : JSON.parse(data);
            if (!isUndefined(notification.title)) {
              this._onPushNotification(notification);
            }
          });
        }
      }
    });
  }

  _handleAppStateChange() {
    if (AppState.currentState === 'active') {
      if (Platform.OS === 'android') {
        this.handleNotificationFromKilledState();
      }
  }

  _registerDevice() {
    NetInfo.getConnectionInfo().then((isConnected) => {
      if (isConnected) {
        FCM.getFCMToken().then((token) => {
          this._onRegistered(token);
        });
      }
    });
  }

  _onTokenRegister(token) {
    if (typeof (token) === 'object' && token.token) {
      this._onRegistered(token.token);
    }
  }

  _onPushNotification(notification) {
    AsyncStorage.removeItem('lastNotification');
    // if the app is in foreground and receives a notification
    // I show it as an alert
    if (notification.source === 'SAMPLE') {
      if (notification.foreground) {
        Alert.alert(
          notification.title,
          notification.message,
          [{ text: 'Show', onPress: () => this._gotoNotification(notification) }]
        );
      } else {
        this._gotoNotification(notification);
      }
    }
  }

  _onRegistered(deviceToken) {
    NetInfo.getConnectionInfo().then((isConnected) => {
      if (isConnected) {
        const requestData = {
          device_id: DeviceInfo.getUniqueID(),
          device_token: deviceToken,
          token_type: 'fcm',
        };
        const successCB = json => this._registerDeviceResponse(requestData, json);
        const errorCB = e => this._registerDeviceError(e);
        const postURL = `example.com`;
        makePostRequest(postURL, requestData, successCB, errorCB);
      }
    });
  }

  _registerDeviceError(e) {
    Sentry.captureException(e);
  }

  _registerDeviceResponse(requestData, response) {
    if (response.success) {
     // handle success part
    }
  }

  _handleOpenURL = (event) => {
   // custom logic for handling routing
    const url = parseOpenLink(event.url);
    if (url && url.path) {
      if (url.isInternal) {
        const data = Object.assign({}, url.data);
       // navigation
      }
    }
  };

  render() {
    // component
  }
}

import firebase from 'react-native-firebase';
import FCM, {
  FCMEvent, RemoteNotificationResult, WillPresentNotificationResult, NotificationType, NotificationActionType,
  NotificationActionOption, NotificationCategoryOption } from 'react-native-fcm';

let notifOpened = false;

AsyncStorage.getItem('lastNotification').then((data) => {
  if (data) {
    if (AppState.currentState !== 'uninitialized') {
      notifOpened = false;
      AsyncStorage.removeItem('lastNotification');
    }
  }
});

export function registerKilledListener() {
  // this listener will be triggered even when app is killed
  FCM.on(FCMEvent.Notification, (notif) => {
    if (!notif.opened_from_tray) {
      notifOpened = false;
      // this stores notification payload in storage
      // which can be read later when the user clicks on the notification
      AsyncStorage.setItem('lastNotification', JSON.stringify(notif));
    }
  });
}

export function registerAppListener(openPushNotification, handleOpenURL) {

  // channel creation can be skipped if you are not compiling app using SDK 26
  const channel = new firebase.notifications.Android.Channel('default',
  'Notification', firebase.notifications.Android.Importance.Max)
    .setDescription('Receive notifications');

  // Create a channel
  firebase.notifications().android.createChannel(channel);

  // this callback will be triggered only when app is in background
  FCM.on(FCMEvent.Notification, (notif) => {
    if (Platform.OS === 'ios'
      && notif._notificationType === NotificationType.WillPresent && !notif.local_notification) {
      notif.finish(WillPresentNotificationResult.All);
      return;
    }
    if (notif.opened_from_tray) {
      // opened_from_tray is only true when a user clicks on the notificaiton
      // so that's how we know if someone clicked on the notification

      // fetch the last stored notification from storage
      AsyncStorage.getItem('lastNotification').then((data) => {
        const notification = isEmpty(data) ? {} : JSON.parse(data);

        // just a check to make sure that both killedState and foreground listener
        // are not opening the same notification
        if (!isUndefined(notification.title) && !notifOpened) {
          notifOpened = true;
          openPushNotification(notification);
        }
      });
    }

    if (Platform.OS === 'ios') {
      switch (notif._notificationType) {
        case NotificationType.Remote:
          notif.finish(RemoteNotificationResult.NewData);
          break;
        case NotificationType.NotificationResponse:
          notif.finish();
          break;
        case NotificationType.WillPresent:
          notif.finish(WillPresentNotificationResult.All);
          break;
      }
    }
  });

  FCM.on('FCMNotificationReceived', (notif) => {
     // listener for notifications when app is active
    if (AppState.currentState === 'active' && !isUndefined(notif.title) && Platform.OS === 'android' && !notifOpened) {
      const notification = Object.assign({}, notif, { foreground: true });
      notifOpened = true;
      openPushNotification(notification);
    }
  });
}

@sahil290791 perhaps I should merge sdk-26 into main as it is getting stable

@sahil290791
Thank you a lot for the code. :+1:  :)
I am working in some other things, Once I will start FCM part, I will go through your code, and let you know if anything has to be updated or I will get some other way also. :)


Element labels are offset from elements when using ketcher.setMolecule(molfile)

Steps to Reproduce

Use ketcher.setMolecule(molfile) with a molfile string

Expected behavior
The structure appears with atom labels next to the corresponding atoms.
Actual behavior
The structure appears with atom labels vertically offset from the atoms. Once one of the atoms is moved, the labels re-adjust and the offset is fixed.
Desktop (please complete the following information):

OS: macOS Monterey 12.4
Browser Google Chrome
Version 101.0.4951.64 (Official Build) (x86_64)

https://user-images.githubusercontent.com/22535087/171460184-e37268e5-9d84-4d57-bfa3-e9c31653d369.mp4
Ketcher version v2.4.0.

Dear @ericmuckley ,
please attach original file to reproduce your issue locally.
Regards,
Andrei

ketcher.txt
When I read the text in this file as a string called molfile, and then use the command ketcher.setMolecule(molfile), the element labels appear offset from their actual locations.

Hi Andrei,
I just upgraded to version 2.5.0 and the issue is still happening.
The molecule is generated using ketcher.setMolecule(molfile) where molfile is the contents of the ketcher.txt file I attached above. Is there anything else I can try?
https://user-images.githubusercontent.com/22535087/173117255-87575609-7e64-4ba0-8b6a-b263752d3287.mov

Dear @ericmuckley
We could not reproduce, even on exactly the same environment, this error, perhaps the problem is local
Maybe the problem will be fixed in the next versions of the catcher


get this working for Fedora 32

Hi,
this is not a real issue. I have try to get this running on Fedora 32 and at the end it runs but it toke me 3 days of work. So I created this Github repo with my steps and some help links to get this working faster.
@nagadomi I did not know where the best place is to put these infos (README or Wiki). Can you do this, please?

I'm not going to link all waifu2x related articles, but the wiki can be edited by anyone.
I also publish torch.distro with CUDA 10 support  https://github.com/nagadomi/distro . I think this will make installation easier.

Ok then I will add this to the Wiki.
I understand your point you can not link all releated that are to many and as result you will have a repo full of links.
But my intention was to complete your installation section in your README. Why do you don't link to your torch7 repo if there are any fixes, which helps to get this working? I found your repo also after I was done and CUDA 10 was not the problem. The problem was to find a gcc version to compile torch7 with CUDA, because CUDA is only supported for a gcc version less then 8.
Anywhy this is not a real issue so I will close it.


[MRG] Renaming HostRequest to_user --> host and from_user --> surfer

This got me all confused when reviewing Aapeli's pull request, so I went ahead and refactored it (as briefly mentioned in the slack channel)
This will need frontend work as well
Also, unsure if the migrations will work as the test is broken on my machine, so well see
Backend checklist

[x] Formatted my code by running autoflake -r -i --remove-all-unused-imports src && isort . && black . in app/backend
[ ] Added tests for any new code or added a regression test if fixing a bug
[x] All tests pass
[ ] Run the backend locally and it works
[x] Added migrations if there are any database changes, rebased onto develop if necessary for linear migration history

Frontend checklist

[ ] Formatted my code with yarn format && yarn lint --fix
[ ] There are no warnings from yarn lint
[ ] There are no console warnings when running the app
[ ] Added any new components to storybook
[ ] Added tests where relevant
[ ] All tests pass
[ ] Clicked around my changes running locally and it works
[ ] Checked Desktop, Mobile and Tablet screen sizes

No problem. It will need frontend changes anyway.

Btw, there's no need to change the tag number in protos if the meaning and type stay the same and you're just changing the name

Had no idea, thanks!

Done/ready for front end post #1623

Ready for review and then frontend implementation

From #1623? Yes

This seems fine, just needs frontend work

I can then do the frontend bit

I'm not sure why gitlab isn't running? But I updated the names @aapeliv


Please Upgrade packages for node 6.0.0

As you may know, graceful-fs <4.0.0 is no longer compatible with nodejs 6.0.0
Please update packages

<EMAIL_ADDRESS><EMAIL_ADDRESS>
and after down stream update adam-lynch/graceful-ncp#2

<EMAIL_ADDRESS>

Greeting. I have reimplement a nwjs-builder, which is built for node.js 4.x+, including node.js 6.x. It's basically compatible with the most used nwbuild options like -v, -p and -r, added with some other options like --with-ffmpeg and --side-by-side, and has fixed some pending issues of nwjs/nw-builder.
I am glad if you can try it out, and feedback is always welcome :)

I cannot access nwjs-builder url.
Error 503 backend read error

Sorted on phoenix branch


fix: spelling error for @parameter

Good catch, thanks!

Love this theme, so thanks for maintaining!

No problem! I'm glad you like it 😄


7.1.1: Crash when tagging events in offline mode

Environment

iOS: 15.5
StreamingTagSwift: 7.1.1
Network connectivity: Offline (Airplane mode)

Problem
When sending events to the tagger while offline the library crashes.
Example:
let tagger: ReplayStreamingTagger

…

DispatchQueue.main.async {
  tagger.notifyEvent(eventState: someState, position: somePosition)
}

crashes.
When catching this in the debugger it seems there is a dispatch_sync on the sessionQueue call used on the queue it's already on. See here:

This is a regression from 7.1.0 where the same call worked.

Hi @toto,
We fixed this issue in our future release. It's actually in internal validation, we will release it as soon as possible !


DiscoverDevices issues Win 10

Hi,
I am quite sure this was working months ago....maybe Windows update broke it. I have no idea.

Visual Studio 2019 Project targeting .NET 4.6.1, latest inthehand 4.0.20 according to nuget.  <IP_ADDRESS> according to dll properties.

This code no longer finds anything discoverable and in fact only executes for 1-4 seconds (I expect DiscoverDevice to take 10 seconds by default?).  bdlist is always empty.
        var bc = new BluetoothClient();
        var bdlist = bc.DiscoverDevices();                           // this function only runs for a couple seconds, 0 to 4

On the same computer I have my old project running visual studio 2017, targeting .NET 4.5, 32feet.NET version v3.5.0 according to nuget.
This code returns discoverable devices.
    var bc = new BluetoothClient();
    var bdlist = bc.DiscoverDevicesInRange();                    // takes 10 seconds

The two cases above are running on the same computer. I can switch between VS 2017  and 2019.  The first case never find any bluetooth devices, the second case always does.

The visual studio 2019 project, I downgraded to the 32feet.net dll version 3.5.0.  Does not work.

Any idea what is going on here?
Appreciate your help.
Chris

Have you changed the InquiryLength property at all? This will affect how long the discovery takes and if too short it may not pick up devices you are expecting to find. Also does the PairedDevices property return anything or is this also empty?

Hi Peter,
Good news, adding debug output led me to follow some exceptions and figure out what is going on.  I have found the cause, although I am not entirely sure what to do about it.
This software is used for testing product, The new version (Visual Studio 2019) is a lot more asynchronous (async, await, etc).  It is attempting to open serial ports for communication in another task at the same time as the Bluetooth scan starts in another thread.
This hasn't been a problem but I notice that two new serial ports have appeared in the device manager called 'Standard Serial over Bluetooth link (COM12)' and COM13.  Attempting to open these results in System.IO exceptions. No big deal one would think.
But if these happen (in another task) after calling DiscoverDevices (in its own task) this seems to cause DiscoverDevices to abort/return before finishing.
So at this point I can find a way to work around whatever is happening beneath the hood. Unfortunately calling SerialPort.GetPortNames only returns COM12, COM13, etc... so I am not entirely sure yet how I will figure out which ones are 'bluetooth' and skip them.
Thanks for your quick reply.
Chris

I'm not sure why the COM ports are affecting discovery - I'll have to try and recreate this and dig into it. You may find this post and the accompanying Gist useful which shows how to get details of Bluetooth virtual COM ports
https://inthehand.com/2020/11/22/bluetooth-virtual-com-ports/


Mixed Content adding TextPlugin

When adding a new Text Plugin to django CMS the iframe url is loading http when the site is served over https. Other django cms plugins are working. The server serving this is redirecting all http requests to https.
Here you can see the ifram is a relative src.

I think this is going to be related to this issue: Unsafe script warnings when saving/publishing through the front end #4432


Stack with invalid name

Before you start, we need a little bit more information from you:
Use Case (delete as appropriate): Using Portainer at Home, Using Portainer in a Commercial setup.
Have you reviewed our technical documentation and knowledge base? Yes/No

Question:
I have had the same stack in play on portainer for a few years now, when I had created it, it allowed the use of an uppercase in the name and it's not till now that I went to go remove it however I cannot. Cannot remove it, cannot stop it, cannot do anything with it because it errors stating "Frigate" is not a valid project name. I've tried searching around for a solution but since you cannot rename stacks I don't know what to do.

@SonomaGTS
Please see here for more information:  https://github.com/portainer/portainer/issues/8154#issuecomment-1365559281
Workaround: You can downgrade to 2.15 to delete Stack and re-create.
Workaround: You can downgrade to 2.13 to stop/start/delete and re-create.
Closing.
Thanks!


monitor: add assembler/stage duration

Allow a user to see the duration for each step in the osbuild pipeline.
This allows a user to optimize the build system for the best performance
and identify performance bottlenecks.
Signed-off-by: Major Hayden<EMAIL_ADDRESS>

I think this would be very useful. Though I think we should attach it as metadata to the result object rather than write it to the log. This would fit with the work you are doing, right @gicmo?

Like this idea a lot! :timer_clock: But personally I would just make it part of the respective monitor class, i.e. LogMonitor, and then, once we have it, the JsonMonitor. The begin, finish method are called at the beginning and end of the pipeline, and the stage/assembler, result methods are called before and after a single stags/assembler. We can do all the time book keeping in the monitor(s).

@gicmo I was trying to put it in LogMonitor but I think finish() is called after the output pipe is closed (I may be wrong on that). I wasn't sure which method I could use for the duration calculation and for printing it to the output.

@gicmo I was trying to put it in LogMonitor but I think finish() is called after the output pipe is closed (I may be wrong on that). I wasn't sure which method I could use for the duration calculation and for printing it to the output.

For the whole pipeline, it should really be begin and finish. They are currently not defined on LogMonitor, so they need to be added. They should work, if not it is a bug and I will fix it ;D

@gicmo Okay, that helps a bit. I'll take a look at this later today (hopefully).

Requires #493 to merge first.


Tetrisclock fix

Description
So it turns out that the app was broken for like 3 months. Whoops!

The pieces can now move and rotate in move directions.
Movement odds have been fixed, and more options have been created

Editor's note: I don't know how to remove the changes for the other file. Please ignore them until I figure it out.

I think you may want to rebase your fork of the community repo. Alternatively just remove the current fork and create a new one.