Collection not being updated correctly until a page refresh

Version info

**Angular: 4.3.6
**Firebase: 4.6.0
**AngularFire: 5.0.0-rc.3
Other (e.g. Ionic/Cordova, Node, browser, operating system):
How to reproduce these conditions
This issue can be recreated here:
https://stackblitz.com/edit/angularfirebase-basic-crud-delete-error

Steps to set up and reproduce

Use the first input field and the add button to add 3 users to the firebase database. You should see 2 identical lists below it once you have entered 3 users.

The first list will also allow you to update and delete the database. The second list is just read-only.

Click on the delete button on the second item in the second list.

Sample data and security rules
N/A
Debug output
N/A
Expected behavior

Both lists below the top input field should have 2 items in the list.

Actual behavior

Only the bottom list updates correctly, the middle list shows 1 item even though only 1 of the 3 items was deleted.

Can someone enlighten me why i am seeing this behaviour? The only difference between the lists is in the html. The middle list is bound to the original Users collection. The second list is bound to a separate identical list. I cannot figure out why the middle list deletes 2 values after one delete. When you refresh the page however, the correct items are shown in both lists.
Thanks in advance.

Your stackblitz link is broken

Ah sorry about that, this is no longer an issue now.
Thanks.

I'm experiencing the same problem, how did you solve it? I have a list page and an edit one, if I edit the record and go back to the list it doesn't update until a refresh. Strange fact: if i open the list and the edit page in different windows it works fine.


nest_lc parameters being used internally in the wrong order

This also applies to mcmc_lc. Somewhere internally, sncosmo is re-ordering the order of the parameters and not applying that to the plots or to the 'est_model'. So if the user puts the parameters in the wrong order when calling nest_lc or mcmc_lc, the returned model and parameters are incorrect.
# hacking the sncosmo internal grid for the model
model = sncosmo.Model(source='hsiao')
phase = np.linspace( -20,85, 106 )
wave  = np.linspace( 1000,25000, 1501 )
flux  = model.flux( phase, wave )

# make the source, apply dust, set it to the right z
source = sncosmo.StretchSource( phase,wave,flux )
dust   = sncosmo.CCM89Dust()
dust.set( r_v=2.8 )
model  = sncosmo.Model(source=source, effects=[dust], effect_names=['host'], effect_frames=['rest'])
model.set(z=z)
res, fitted_model = sncosmo.nest_lc(data, model,
        ['t0', 'amplitude', 's', 'hostebv'],
        guess_amplitude_bound=True,
        bounds={'s':(0.5,2), 'hostebv':(-1,1)})

Should be fixed now. I didn't address mcmc_lc() though because the return value is about to change to match fit_lc() and nest_lc().


Fix InvalidCastException in Animation_Batches

Addresses the Animation_Batches crash from issue #208
It seems to be fixed (and the sample overall seems to then work fine) by just removing the "(ContainerVisual)" cast.
I'm a little unsure about submitting this change because I don't really understand the context (how did it get this way to begin with? did it work on an older version of the API?) but here's a PR anyway.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Thanks for finding this! I accepted the pull request.


RFC: Improve Sensor Testing Insfrastructure

Introduction
In the latest Sensor WG Meeting (240819), it was discussed the current state of sensor testing and there was interest in improving this to make it more effective without implying a significant effort.
In the context of migrating Sensor drivers to the Sensor model V2 (Asynchronous, Read/Decode APIs) it becomes more important to have a solution in place to keep track of regressions, as well as validate the porting process along the way.
Problem description
Currently, there are two main approaches for testing sensor drivers:

Build-all sensors Testsuite -> https://github.com/zephyrproject-rtos/zephyr/tree/main/tests/drivers/build_all/sensor
Sensor Emulator Test-suites -> https://github.com/zephyrproject-rtos/zephyr/tree/main/tests/drivers/sensor

The issues with only relying on these two approaches:

Build-all sensors:

Build-time only verification (for sensors with no emulator).

Sensor Emulator Test-suites

Requires developing and maintaining an emulator + test-suite per sensor driver (non-negligible effort).
Limited number of emulators in-tree (and all most of them are based on Sensor model v1 -> Fetch/Get approach).
There have been bugs identified for some of the emulators themselves.

In general, there are challenges with the existing :

We've identified some issues not covered by none of the above. Some examples:

#72059
#72840
#72815
#71227

The existing testing infrastructure does not cover Read-Stream/Decode APIs nor triggers (or at least not in a significant way).
The rate at which users contribute new sensors is very high (+10 PRs introducing new drivers at this moment).

Proposed change
HIL Testing Infrastructure in CI
Incorporate HIL sensor testing infrastructure in CI, in which run-time sensor operations are performed and verified. This implies test-beds provided by vendors and trusted community members are deployed and maintained operational.
To achieve this, we'd need to:

[ ] Coordinate with the Testing WG and understand what options we have.
[ ] Contact Sensor Vendors and trusted community members to provide and maintain a test-bed with supported sensors.
[ ] Start deploying and adding test-beds nodes in CI infrastructure.

Testing Approach

Go with generic tests (akin the existing generic sensor samples??) that is applicable to all sensors that support that type.
Evaluate the following parameters

Sensor Polling (read/decode with results validation)
Attributes (e.g: change ODR or resolution and verify it is effective)
Triggers (to the extend that is possible in a static setup, e.g: Watermark, Stationary, FIFO Full).
Preferrably, evaluate the sensor on all supported transports (e.g: BME280 both SPI and I2C).

Concerns and Unresolved Questions

Having enough vendors and community members to provide testing setup.
Whether we use the Sensor Shell for this or stick to the aforementioned generic testsuites.

Alternatives
Not doing any change in sensor testing and keep on catching bugs as people report them.

@hakehuang we'd like to loop-in the Testing WG to understand what options we have in making this happen. Could you provide in your thoughts?

I completely agree with the HIL testing approach for sensors.

The sensor build_all test actually has a generic test which will run against any sensor driver that has a paired emulator (https://github.com/zephyrproject-rtos/zephyr/blob/main/tests/drivers/build_all/sensor/testcase.yaml#L32). The idea when we wrote it was to reduce the friction of testing. When you add a new driver instead of driver + emulator + test you just write driver + emulator.
Here's an example of a driver which only implements the V2 API https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/sensor/bosch/bma4xx/bma4xx.c
Downstream in ChromeOS I'm also looking at test libraries which can run either by HIL or emulators. The idea is that you write the tests in a library which you can link against either an emulated environment or a hardware binary. When you run/flash you should see the same behavior. The idea was to run the same test in CI then a nightly run on hardware.

We're also working with the Fuchsia team on an open source sensor trace/playback system which should be RTOS agnostic. So we're hoping to be able to run a HIL test while capturing the data and replay it in CI emulation.

I completely agree with the HIL testing approach for sensors. I know @bperseghetti might have some thoughts on this as well.

I think that having real hardware testing is critical for the health and reliability of sensors in Zephyr.
While I'm a big simulation/emulation fan in general, I think the risks are too great of "writing a test to the answers you know" and the amount of time to write them vs what they provide might not be a good cost value for the majority of sensors. With real hardware testing you sometimes might even find quirks/discrepancies from the assumed correct datasheets or implementations that look great in code but just don't function properly on device.
I think for us one of those learning experiences was the icm42688, we were able to write a rudimentary test for it for HIL and it was the only way we could work through getting it to properly function with streaming API and adjusting the FS/ODRs.

@hakehuang we'd like to loop-in the Testing WG to understand what options we have in making this happen. Could you provide your thoughts?

I basically agree with this proposal. can you attend in next week TWG meeting, and we can have discussion on how to support those.
HIL Testing Infrastructure in CI
Incorporate HIL sensor testing infrastructure in CI, in which run-time sensor operations are performed and verified. This implies test-beds provided by vendors and trusted community members are deployed and maintained operational.
To achieve this, we'd need to:
Coordinate with the Testing WG and understand what options we have.
-> the emulator solution in HIL running on bus simulator is far from enough. it has many assumptions. so it is only fit for sensor API change regression. and not fit for sensor driver modelling testing.
-> using qemu / renode with adding sensor support could be an option as the driver modelling can be added but need sensor vender support this.
-> real board testing, we can affording weekly testing on sensors we have from TWG prospective. but we need have those sensor available. this task can be  further allocated to each vender, and we allow them to upload results as well.
Contact Sensor Vendors and trusted community members to provide and maintain a test-bed with supported sensors.
Start deploying and adding test-beds nodes in CI infrastructure.
Testing Approach
Go with generic tests (akin the existing generic sensor samples??) that is applicable to all sensors that support that type.
Evaluate the following parameters
Sensor Polling (read/decode with results validation)
Attributes (e.g: change ODR or resolution and verify it is effective)
Triggers (to the extend that is possible in a static setup, e.g: Watermark, Stationary, FIFO Full).
-> NXP can offer to testing sensors function in weekly regression, providing NXP platform is supported, or sensor team to port to NXP platform.  we can send test report to sensor group

@yperess , I basically agree with this proposal. can you attend in next week TWG meeting, and we can have discussion on how to support those.

Yup, I'll be there.

Yup, I'll be there.

Thanks, I will add this to agenda.

@KeHIntel might be interested in seeing some activity around this as well perhaps

FYI - The meeting just started

To do all this I think we need two things, some information about each sensor... what channels does it have, what sample rates, what ranges? We also, in my view, need a way of easily describing the board farm and what sensors are on which boards where the boards themselves are unlikely to have the sensor driver we want to test.

the sensor shall be build in board or expanded by interface (I2C/SPI)? I think we should support both.
we can define a list of tests with, as long as we have sensor connected by adding a fixture requirement in the test cases.

fixture_sensor_<sensor_name>
not using the platform_allowed, so as long as  a fixture is available to that board, then we can run that tests.
so for on board sensor this requires to add fixture_sensor_ as well. and for expand sensor, we need add  a extra config to config the i2s/spi/uart to connect with.
with above, same test cases can move to any platform as long as it build-in or expandable.


Replaces unordered_map by map in tfidfvectorizer

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (fa5e2a2) 82.40% compared to head (aa8b1d4) 82.40%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #126   +/-   ##
=======================================
  Coverage   82.40%   82.40%
=======================================
  Files          52       52
  Lines        6665     6665
=======================================
  Hits         5492     5492
  Misses       1173     1173

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


firefox: html5 drag and drop doesn't work x11 kde/plasma6

Describe the bug
I am on nixos unstable on kde plasma and I install firefox via nix-shell as
$ nix shell nixpkgs#firefox
$ which firefox
/nix/store/fypz1h78smaq2qsizi0w4rr6xwkqq7r1-firefox-126.0/bin/firefox

services.desktopManager.plasma6.enable = true;
Steps To Reproduce
Steps to reproduce the behavior:

Install firefox (mine says 126.0 (64-bit))readlink -f $(which firefox)
/nix/store/fypz1h78smaq2qsizi0w4rr6xwkqq7r1-firefox-126.0/bin/firefox

Install kde plasma 6, switch to x11 on sddm.
go to

https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/drag_event
https://sortablejs.github.io/Sortable/#grid
https://lukasoppermann.github.io/html5sortable/index.html
one of the above urls and try to drag an element.

fails to drag the element

Expected behavior
Expect the element can be dragged/dropped.
Additional context
I am on kde plasma 6, using x11 not wayland.
Drag drop on the same plasma6 x11 works in microsoft-edge (or chrome/chromium).
Works on kde plasma6 wayland.
But sadly I cannot use wayland because of a different issue with the external monitor going to sleep on laptop lid close. here
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.30, NixOS, 24.05 (Uakari), 24.05.20240515.33d1e75`
 - multi-user?: `yes`
 - sandbox: `relaxed`
 - version: `nix-env (Nix) 2.18.2`
 - nixpkgs: `/nix/store/0qd773b63yg8435w8hpm13zqz7iipcbs-source`

Add a :+1: reaction to issues you find important.

Never mind, I disabled all extensions and it works on x11, not an issue with the firefox package it seems


Add support for bulk insert

Fixes #1888

What's the memory usage like with ~100 or more batches?
Is it more or less the same as with JDBC batching?
Just wondering.

What's the memory usage like with ~100 or more batches?
That depends on the values being bound and the JDBC driver implementation.

The batch handling in Querydsl is currently more sophisticated and safe, but since this is an explicit override internal optimization shouldn't be expected.

Could you also add a verification test for useLiterals?

What do you mean by verification test?

A test case with useLiterals enabled, just so that also has coverage.


deps<EMAIL_ADDRESS>

@ErisDS Are you able to update npm? I think there were issues some time back.

@mgutz yeah I believe so - gonna make a couple more amends first and then will publish a new version

👍

@ErisDS please let us know if you can up the version at the earliest.

@ktkaushik v1.0.0 is now available

@ErisDS 👍  thanks


[Algo] Shell Sort [C++]

https://en.wikipedia.org/wiki/Shellsort

Can you assign this to me, please?

GitMate.io thinks possibly related issues are https://github.com/NITSkmOS/Algorithms/issues/250 ([Algo] Quick Sort [C++]), https://github.com/NITSkmOS/Algorithms/issues/222 ([Algo] Radix Sort [C++]), https://github.com/NITSkmOS/Algorithms/issues/258 ([Algo] Merge Sort [C++]), https://github.com/NITSkmOS/Algorithms/issues/20 ([Algo]: Add Bubble Sort in C++), and https://github.com/NITSkmOS/Algorithms/issues/62 ([Algo] Insertion Sort [C++]).


Modify the Quick Reference Guide build script so that it did not depend on the presence of tdwgutility:UseWithIRI

As originally raised in https://github.com/tdwg/dwc/issues/252

The "housekeeping" class http://rs.tdwg.org/dwc/terms/attributes/UseWithIRI is used in the "Normative Document" to categorize terms that should be grouped together in the UseWithIRI section. However, that class itself is NOT part of Darwin Core (and doesn't appear on the Quick Reference Guide itself). The tdwgutility:UseWithIRI term and all the other ones in that namespace were moved out of Darwin Core so they could be managed more nimbly as needed. Can we remove  http://rs.tdwg.org/dwc/terms/attributes/UseWithIRI-2017-10-06 as a row in the "Normative Document" without breaking anything? It doesn't belong there.

The consensus was that this was a desirable ultimate goal, but since it would require a significant revision of the Quick Reference Guide build script, it should be put of and not block completing the milestone https://github.com/tdwg/dwc/milestone/10

@baskaufs I have a solution for this that I have tested locally. In the test, I removed the line in term_versions.csv for UsWithIRI, then run build.py and do a git diff on docs/terms/index.md and confirm that there are no changes.
Does build/build-termlist.py depend on there being a row on term_versions.csv for UseWithIRI? That script is not as easy to test because it gets its data from GitHub rather than the local copy.

@tucotuco build-termlist.py is unaffected by changes to term_versions.csv . The data it gets from GitHub does not include that file.
The place where this pseudo-version gets added is in the generate_term_versions.py script here:
https://github.com/tdwg/dwc/blob/1d52ee818dd315b8595c8bf3824d9451c719f1c5/build/generate_term_versions.py#L122-L137
The output term_version.csv file is only used by the QRG build.py script as far as I know. I had been assuming that the http://rs.tdwg.org/dwc/terms/attributes/UseWithIRI-2017-10-06 line was necessary to group the IRI terms in this code block here:
https://github.com/tdwg/dwc/blob/1d52ee818dd315b8595c8bf3824d9451c719f1c5/build/build.py#L214-L228
So I don't understand how the script worked without it. Is there something in the page template that groups the IRI terms without the need for this grouping step?
If generating the QRG guide works without that line, then we could just comment out lines 122-137 in generate_term_versions.py and it would be gone in the future. The only situation that would matter would be if people actually looked to the term_version.csv as an authoritative list of all parts of the vocabulary (since tdwgutility:UseWithIRI is NOT actually part of the vocabulary). My guess is that now that the List of Terms doc is there, people who want that kind of information would go there since it's easier to read. So fixing this issue isn't that critical, but if you've verified that the QRG build script doesn't actually need that line in term_version.csv, we should just get rid of it.

@baskaufs Indeed, the build.py script in its current form does rely on the existence of the UseWthIRI row in term_versions.csv. just where you pointed out. I wasn't clear in that the solution was a modification to build.py to enable removing the row without ill effect. Now that I know there should not be any side effects, I have pushed this solution in cc2fb477e90743519bd10f8bb997299676f907b0.

I pushed one more commit https://github.com/tdwg/dwc/commit/2ba97527c5599a05b3c0f257447854e128688ccd in order to remove the upstream code that generated the fake class IRI. I also added a note in the list of instructions for updating about the qrg-list.csv that controls the order of terms. That had previously been omitted.

Excellent.


smartctl needs the full device path

In contrast to the diskinfo command, smartctl needs the full device path, not just geom.

other issues have incorporated this (and more) to improve the smart dashboard. Closing.


Update install guide and create update guide

I've setup my own Mastodon instance (https://ultrix.me) using these modified instructions, and I can verify they worked. I also wrote a guide for updating your instance, which I have also verified to work.
up-and-running.md:

Added verification for $5/mo Linode instance
Updated Docker Compose install link
Updated links to Mastodon documentation
Added instructions for creating a temporary swap file
Remove mention of "ssl_certificate" line because it doesn't exist now
Switched to python-certbot-nginx because it worked for me and the other client didn't

updating.md:

Added instructions for updating Mastodon instance

readme.md::

Updated links to Mastodon documentation
Added link to new update page

Sorry for the late response on this. Merging because it looks good to me. I think we should try and migrate away from this repo though because I don't maintain it :)

@ummjackson If you want, you can transfer the repo to me. I'm by no means a sysadmin, but I'm actively maintaining an instance using the guide, so I think I could keep it updated.
Instructions for transferring a repository: https://help.github.com/articles/transferring-a-repository-owned-by-your-personal-account/


ARROW-3509: [C++] Standardize on using Field in Type/Array

I think there is potentially more consolidaion on the builders but this seems like a reasonable place to make the PR.

@emkornfield could you rebase so GHA jobs are unskipped?

@bkietz done.

The arrow/compute changes are OK here. The rebase shouldn't be too complicated when I get there

Is it typical for GHA to be queued for hours?

Not typical, but it's certainly the case today.

Perhaps someone ran a SQL query and determined that our builds are costing Microsoft a lot of money (only half joking)

@emkornfield looks like you missed a (now deprecated) usage of children() : arrow/json/test_common.h:108:57 https://github.com/apache/arrow/pull/7132/checks?check_run_id=667758585#step:6:765

@bkietz yeah, I just pushed what I hope will catch the rest.


PP-7968: Add cloudfront domain to the content security policy

Frontend needs to download custom branding images and scss files from our cloudfront.
The domain could be an environment variable but hard coding this here for now to prove an end to end sense check but this domain will be provided through the environment by TF before reaching production.

This has been pushed to AWS test ECR with PP-7968-custom-branding tag


⚠ ClamAV has degraded performance

In 3f63ac3, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 195 ms

Resolved: ClamAV performance has improved in 88eb269.


Execution of scripts does not work

Moreover, when executing hello-world i get:

Relates to https://github.com/kbss-cvut/s-pipes-editor-ui/issues/27


React Native 0.29 - mixins: [NativeMethodsMixin]

I'm getting a flow warning for every file in react-native now i've upgraded to 0.29.
node_modules/react-native/Libraries/Text/Text.js:89
 89: const Text = React.createClass({
                  ^ super of React component. Cannot inherit
182:   mixins: [NativeMethodsMixin],
                ^^^^^^^^^^^^^^^^^^ statics of function type

Please provide a working example for NativeMethodsMixin in react native

What are the versions of both Flow and React Native that you are using and could you provide us with a complete code example that reproduces the error?

Resolved by adding the followings into .flowconfig:
.flowconfig
[options]
module.name_mapper='NativeMethodsMixin' -> '<PROJECT_ROOT>/node_modules/react-native/Libraries/Renderer/shims/NativeMethodsMixin.js'


Add Footer NEEDED 🟢

Webapplications is currently missing a footer. For the time being, this project is a single-page application. Degian and integrate a footer with the following message: Made with 💙 by the Before I Die Community and from here create a link that links back to this project repository for now.

Add animation to the heart by using font awesome open source-free icons. Font awesome.

An example of what one could do for the heart animation from the font-awesome website ⬇
https://github.com/BeforeIDieCode/BeforeIDieAchievements/assets/120526253/3f1e2eb8-de28-47b3-bfec-61c0c7742550

I would like to work on this issue

Hi Girish! Thank you for your enthusiasm and offer to work on this issue. The contributor @lefty93 happened to just send a pull request and I have merged it into the main branch. Please see #19 for further details of the footer being added.
The current footer at the moment that has been added. ⬇

That being said, please feel free to contribute your text and info to "What you want to do before you Die?' and/or contribute to the other open issues (I will be adding more every day), please feel free to add more open issues with your own ideas and also I have created a Roadmap with ideas to add to the project that are both short term and long term focused on building upon this project to get ideas from for creating open issues. Thanks for your enthusiasm, and have a great day and looking forward to seeing your contributions! 😇


Fix borderRadius Android

Fixes borderRadius on Android. Based on @bsinc's solution https://github.com/facebook/react-native/issues/3198

Thanks for your PR! Tried your code with a background color that's not white and and it would add an outline (on iOS too). Is there a way to solve this properly?

Hi @oblador! It seems like to apply this workaround we'd need to add background color prop to avoid the different color in the outline. I'm not sure how to evaluate the magnitude of underlying problem described in react-native/#3198, so I can't make a definite recommendation. Do you think it makes sense to introduce this or is it better to wait for a fix in react-native?
Something like:
const fixCircleClipping = {
     ...
     borderColor: this.props.backgroundColorOfParentElement
};

@pavloko Right, that might be an acceptable workaround for now as it doesn't seem to happen in core any time soon. Would you mind updating the PR @enstulen?

I've patched in the backgroundColorOfParentElement change in an up to date fork. Would you like a new PR for this issue?

Has there been any progress on this one? @enstulen @pavloko @ddaeschler @oblador

@AndrewTHuang facing this now, maybe wasn't fixed yet

Is this still an issue? Appears to be fixed by https://github.com/facebook/react-native/commit/30044fd531c22c4c5e8f1ede206fa7c2c3fd3aa8?

Closing as I believe it's fixed in RN 0.50 and no replies to the contrary

Seems like this issue still exists


[firebase_messaging] MissingPluginException when building for macOS

Describe the bug
When building for macOS and using the firebase messaging plugin the app gives a MissingPluginException error
To Reproduce

Create a macOS project
Add and use firebase messaging plugin

Expected behavior
No crash
Additional context
Flutter Doctor:
[✓] Flutter (Channel dev, v1.13.0, on Mac OS X 10.15.1 19B88, locale en-US)
• Flutter version 1.13.0 at /Users/nickmowen/Library/Android/flutter
• Framework revision 09126abb22 (8 days ago), 2019-12-03 17:43:00 -0800
• Engine revision<PHONE_NUMBER>
• Dart version 2.7.0 (build 2.7.0-dev.2.1 a4d799c402)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
• Android SDK at /Users/nickmowen/Library/Android/sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-29, build-tools 29.0.2
• Java binary at: /Applications/Android Studio 3.6 Preview.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 11.2.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 11.2.1, Build version 11B500
• CocoaPods version 1.8.4
[✓] Android Studio
• Android Studio at /Applications/Android Studio 3.6 Preview.app/Contents
• Flutter plugin version 42.0.2
• Dart plugin version 192.7761
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
[✓] Connected device (1 available)
• macOS • macOS • darwin-x64 • Mac OS X 10.15.1 19B88

Hi @NickM-27
can you please provide your flutter run --verbose?
Thank you
possible duplicate of https://github.com/FirebaseExtended/flutterfire/issues/1606

@NickM-27 which version did you use? Maybe upgrade you firebase_messaging version, because I had that with another firebase feature package and after the update it was solved.

@Ahmadre Definitely not, I have tried 6.0.3, 6.0.7, and the new 6.0.8. I have seen similar components with changelogs that include "support for macos" and I am guessing that this one just does not have it yet.

@NickM-27 Hey, please edit your comment with debug log because it's linking a lot of issues.

Closing this issue as we're tracking macOS support on #1653 instead.


Tkn 247 unit test coverage auth

@BankiLouis - I'll merge this. It looks like the issue is that theres a removal of a dep in a file and there's no unit test etc.


Dockerfile to run CDT.cloud blueprint

CDT.cloud has several dependencies regarding the system it runs in, such as clangd, potentially a build tool like CMake, etc.
Therefore, it might be helpful to provide a dockerfile that defines those requirements and harmonizes the environment that we use for testing. Also this could be the starting point to deploy CDT.cloud in a kubernetes based cloud infrastructure.
See also the corresponding discussion thread.

Implemented with #14


Add eol to letsencrypt provided files [Issue #110]

Some LE tools like simp_le create the cert files with no end-of-line. This change adds an eol if non exists.
If a file does not exist, sed throws an error on STDERR. It might be a good idea to check for file existence first like in the "self-signed" and "custom" case.
This fixes Issue #110 .

Thank you @Reldeis

I've just discovered that this patch unlink the files in the 'live' directory of LE config dir, in particular:

under the 'live' path there are symlinks to the archive directory, for continuity between updates
the patch sed -i -e '$a\' /etc/letsencrypt/live/$(hostname)/cert.pem cause the unlink in the 'live' directory and the creation of a new file not linked to the one in the archive directory

@Reldeis : does this may breaks future updates of letsencrypt certificates ?

I can't recreate this on my machine in a quick test. The files created with the standard LE binary already have the eol, so the  files are not changed.
I'll look into it.
@tomav I will change it the way Dominik suggested in #110. That way the LE created files are never touched and no unlinking should happen

Thanks for the fast update. Anyway for future reference the problem arise even in case EOLs are presents in the files, the problem being simply the use of the switch '-i' to sed itself.

yes i see where the problem was. On my host (Ubuntu 14.04) the links stay in tact.
However i fixed it in #118 by simply not changing the LE created *.pem files


Add to npm installation

Please add npm support as bower seems to get dated.

Okay, I'll schedule it next.

Sorry, do you have any update on this? Thanks.


How to select tab item programmatically ?

Thanks for your great open source.
I tried to use this method to select other tab programmatically.
[self.vc.tabBar selectedTabItem:1 animated:YES];
It works. But the selected image of previous tab still  remains.

this should be fixed in 0.1.5. Also similar UITabBarController, the best way to programmatically switch tabs is using:
[self.vc setSelectedViewController:viewControllerAtIndex1 animated:YES];


keep Godoc up to date

Now due to the inconsistency between Godoc and Github, it is hard to automate model installation via go mod.
So please ensure Godoc is up to date with the latest API version.

AFAIK there isn't an official release for the main branch yet. API is not considered stable.

AFAIK there isn't a stable official release for the main branch yet

:point_up: This.
We've had a lot of churn since 0.3.1, and 0.4.0 is due soon, at which point the godocs will be pretty much up-to-date.
You can also get docs for the main branch from here


Update dependency @types/uglify-js to v3.17.5

This PR contains the following updates:

Package
Type
Update
Change

@types/uglify-js (source)
devDependencies
patch
3.17.2 -> 3.17.5

Configuration
📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Self-Hosted Renovate Bot. Find all logs here.

 You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.


Refs2 acdc integration

for acdc integration.
needs also the PR in leaflet and epi-workspace.
the auth feature result is now relayed to the acdc address defined in the product.
restored control of application back to the DrugDetailsController but:

No data is passed back to the DrugDetailsController (this will probably have to be done via event because of the modal), since you are unsure on how to display this. the result is simply written to the console for confirmation.
Because of the new way you store data in the batches, and because there is no api to retrieve the latest batch info without knowing what the latest is, the ssi stored on batch creation is the only that will be read. this means that updating the auth feature ssi on a batch level does not work atm

merged for testing and  release in 1.5.0


chore(main): release 0.1.0

:robot: I have created a release beep boop
0.1.0 (2024-12-17)
Bug Fixes

ci (43f8368)
ci (16f9012)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.1.0
:sunflower:


Gauge table in concept file doesn't accept |-------------| after the header.

Expected behavior
Gauge table in concept file should accept |-------------| after the header
Actual behavior
Gauge table in concept file doesn't accept |-------------| after the header
Steps to reproduce

Create a concept file with a gauge table like below

And the JSON Path Assertions for the response should be equal to the following

     |JSON Path                           |Expected Result                                                                   |
     |------------------------------|----------------------------------------------------------------|
     |$.title                                   |Expert API Automation using MaxSoft ATA Framework      |
     |$.userId                               |osan                                                                                |
     |$.archived                            |true                                                                                |
     |$.book.bookTitle                 |Expert API Deck3                                                                   |

Create a spec and provide the concept name as a step name
Run that spec.
You will get an error that |-------------| has taken as a data record.

Gauge version
Gauge version: 0.9.7
Commit Hash: bc9784c

Plugins
-------
csharp (0.10.1)
flash (0.0.1)
html-report (4.0.2)
java (0.6.6)
ruby (0.4.2)
screenshot (0.0.1)
spectacle (0.1.2)
xml-report (0.2.0)

I think this is an issue for https://github.com/getgauge/gauge itself, as the parsing of parameters/steps is a core feature and not a responsibility of the runner

@zabil Any update on this?

Can you share an example that's a valid concept and spec file? You can insert the samples as a comment.

Concept
`
Date Created    : 11/29/2017
Version   		: 1.0.0
Owner      		: Osanda Deshan
Description  	: This is a concept file with following syntax for each concept.
Invoke PI API in Staging Environment using valid username and password and save the access token inside the text file

Given that a user needs to invoke "Get Staging PI Token"
And the user set the request attributes as follows

Attribute Value In JSON Template
Attribute Value To Be Set

#username
osa

#password
Password1

When the user invokes the API
Then the status code for the request is "201"
And the JSON Path Assertions for the response should be equal to the following

JSON Path
Expected Result

$.status
success

And save the access token in the response which is located inside the JSON Path of "$.data"
`

Spec
`
Get Staging PI Token Specification
Date Created    : 11/29/2017
Version   		: 1.0.0
Owner      		: Osanda Deshan
Description  	: This is an executable specification file which follows markdown syntax. Every heading in this file denotes a scenario. Every bulleted point denotes a step.
tags: get_pi_token, staging_token
Invoke PI API in Staging Environment using valid username and password and save the access token inside the text file
tags: get_pi_token, staging

Invoke PI API in Staging Environment using valid username and password and save the access token inside the text file

`

@osandadeshan A sample project may help us debug further. I was unable to see this with my test setup.

MaxSoft-IntelliAPI-Demo.zip
Please check this

@osandadeshan I can see the error too. But what seems to be weird is that the first table in your  concept seems to have the correct implementation. The second one seems to accept the dashes as a row too.
Is it possible to share the code snippet for the step with the table. I feel that it may be a implementation detail. (I don't need the whole code, just how you are using the table may be helpful).

@nehashri This is function which fires from the above step implementation
// Use this method to validate the content of the response using JSON Path Assertions     public void jsonPathAssertionEquals(Table table){         List<TableRow> rows = table.getTableRows();         List<String> columnNames = table.getColumnNames();         for (TableRow row : rows) {             if (row.getCell(columnNames.get(1)).substring(0, Math.min(row.getCell(columnNames.get(1)).length(), FILE_SYNTAX_CHARACTER_COUNT)).toLowerCase().equals(FILE_SYNTAX)) {                 jsonPathAssertionEquals(row.getCell(columnNames.get(0)), TextFile.read(CURRENT_DIRECTORY + row.getCell(columnNames.get(1)).substring(FILE_SYNTAX_CHARACTER_COUNT, row.getCell(columnNames.get(1)).length()-1)));             } else {                 jsonPathAssertionEquals(row.getCell(columnNames.get(0)), row.getCell(columnNames.get(1)));             }         }     }

This issues seems to be replicable when the above sample projects spec file is copied over.

@nehashri Thanks for the response. Let me know when this is available in a release.

@osandadeshan You can add an empty line after table as a workaround for now.

@negiDharmendra You mean like this?
* And the JSON Path Assertions for the response should be equal to the following
     |JSON Path     |Expected Result|
     |--------------|---------------|
     |$.status      |success        |

* And save the access token in the response which is located inside the JSON Path of "$.data"


RGB mode is not working

I followed all the instructions, the depth mode is working perfectly but I have a problem with the rgb mode. I don't get any color view, So I'm unable to get rgb images and use them.
Could you please tell me what's wrong? Thank you in advance.

Are you using the Astra or the Astra Pro? (rgb is not accessible on the astra pro using openni2 right now)
Did you download the latest openni2 binaries/sources for the Astra?

I'm using the Astra Pro, does this mean that it's impossible for me to use rgb right now?

Take this with a grain of salt, since I did not use an Astro Pro since months.
As far as I know the Astra Pro has a different kind of RGB camera not accessible from the Openni2 framework BUT you can access it just like a normal camera/webcam (v4l2), the point is that there is now sync/registration out of the box.

Thank you @mauriliodc ! I'll try to access it with the driver of a normal webcam.


Tests are flaky (and slow)

The dotmesh repo's CI tests often fail, yet retrying them makes them pass.
This wastes our time and causes frustration.
Let's try and improve that.

[ ] https://github.com/dotmesh-io/ops/issues/15
[ ] https://github.com/dotmesh-io/dotmesh/issues/69
[x] https://github.com/dotmesh-io/ops/issues/16
[x] https://github.com/dotmesh-io/dotmesh/issues/279
[ ] https://github.com/dotmesh-io/ops/issues/17
[ ] https://github.com/dotmesh-io/dotmesh/issues/278
[ ] https://github.com/dotmesh-io/dotmesh/issues/181
[ ] https://github.com/dotmesh-io/dotmesh/issues/282
[ ] https://github.com/dotmesh-io/dotmesh/issues/298

We want to finish off what we're in the middle of, and then put this aside for now.


Subsetting Data Query By Date

Alex, I’ve read through your incredibly helpful documentation and have enjoyed working with the module you’ve put together, but I’ve had a lot of difficulty trying to limit the the price data to only the most recent 180 days. Is there anyway you could tell me or show how I would go about implementing that condition onto a product query so when I submit a query for asin(s) it’s only returning the last 180 days? Not the most recent 180 listings but the earliest (first) price listing for each day of a product for the last 180 days. I’d like return 180 records for each  product, one price per day. Do I use the LISTPRICE key and could I combine that query with one sales rank per day as well?
It may be just my primary language and experience is with R but I was hoping you would shed some light on the matter as there is very little online information/guidance on Keepa.

Hello @ThomasPepperz,
I process recent price history from keepa as well and need to reformat the data such that it has one entry for each day.  Multiple entries for a single hour and one for a period of weeks isn't helpful for me either, but it's important to note that this is the way the data is stored at keepa.  It's an efficient method of storage as the price or sales rank is only stored when there is a change, thereby eliminating duplicate entries.
You won't be able to isolate the product query history to the last 180 days, but you can just trim the data after the query.  As for getting a price per day, here's how I do it:
import numpy as np
import pytest
import os
import keepaAPI
import datetime

FAKEKEY = '8ueigrvvnsp5too0atlb5f11veinerkud47p686ekr7vgr9qtj1t1tle15fffkkm'

PRODUCT_ASIN = '0439064872' # yes, it's harry potter
api = keepaAPI.API(FAKEKEY)
request = api.ProductQuery(PRODUCT_ASIN, history=True)

# product data
values = request[0]['data']['USED']
timedates = request[0]['data']['USED_time']

import datetime
from dateutil import rrule
import pandas as pd

# list of days from now to 180 days in the past
ndays = 180
past = datetime.datetime.today() - datetime.timedelta(days=180)
past = past.replace(hour=0, minute=0, second=0, microsecond=0)
target_days = list(rrule.rrule(rrule.DAILY, count=ndays, dtstart=past))

# convert original datetimes to dates and make it unique
dates = [value.replace(hour=0, minute=0) for value in timedates]
dates, idx = np.unique(dates, return_index=True)
valuesbydate = values[idx]

# get the value of the product with one entry per target day
date_values = np.empty(len(target_days))
date_values[:] = np.nan
mask_a = np.isin(dates, target_days)
mask_b = np.isin(target_days, dates)
date_values[mask_b] = valuesbydate[mask_a]

# fill the na values using pandas
# you could do this manually with a loop that carries the values
# forward when "NAN" is encountered
ts = pd.Series(date_values, target_days)
ts = ts.fillna(method='ffill')

filled_values = ts.values  # <-- what you're looking for
target_days  # < associated dates

The code isn't pretty or fast, but it works.

Understandable, it's not a super popular module and most people are just using the web-interface to get their price research done.  It's a powerful tool, and maybe I'll add more examples online.
I'm not exactly getting paid for this work, so sometimes it's tough to find time to add to the docs.  Let me know if you come up with a solution that works for you and maybe I can add it to the documentation or wiki.

Alex,
If you don't have a cryptocurrency account, you can make one here: https://www.coinbase.com/join/57e1bb4357e9cd0082793ae9
Whenever you get the chance, send me your Ethereum address or post it on here<EMAIL_ADDRESS>and I'll send you a tip for all your trouble. I appreciate your documentation you've produced as well as your response to my issue.

In response to your second question, I'd store the prices and dates as entries in a dictionary:
products = {}
products['1111111111'] = [dates, values]
products['2222222222'] = [dates2, values2]

Each product will have a unique entry and can be rapidly accessed.
As for the coinbase invitation, while I appreciate the gesture, I simply don't have enough time right now to devote to cryptocurrency.  Maybe sometime in the future...
Regardless, I wish you luck with learning Python.  It's a flexible language with lots of libraries and it's probably going to stick around for a while, so it's worth investing some time in.
If you need any additional suggestions or hints, let me know at<EMAIL_ADDRESS>

Hello,
When I followed the code provided above, keepaAPI apparently does not exist.
>>> import keepaAPI Traceback (most recent call last):   File "<stdin>", line 1, in <module> ModuleNotFoundError: No module named 'keepaAPI'
Is there anyway to solve this problem?
Best regards,
nakazas


yubikey-agent: init at 0.1.3

This PR is failing, if anyone can help; I'd really appreciate it.
# github.com/go-piv/piv-go/piv
In file included from vendor/github.com/go-piv/piv-go/piv/pcsc_unix.go:30:
/nix/store/wdhrxbxf175g3qwv22fcm5zda2734a7y-pcsclite-1.8.26-dev/include/PCSC/winscard.h:41:10: fatal error: pcsclite.h: No such file or directory
   41 | #include <pcsclite.h>
      |          ^~~~~~~~~~~~
compilation terminated.

I tried patching, but permissions fail, which I guess it because it's an input.
  # Permission Denied
   postPatch = ''
     substituteInPlace ${stdenv.lib.getDev pcsclite}/include/PCSC/winscard.h \
       --replace "pcsclite.h" "PCSC/pcsclite.h"
   '';

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/pcsc-error-compiling-yubikey-agent/8084/1

It seems https://github.com/go-piv/piv-go doesn't properly use pkgconfig to ask for the include path, but instead hardcodes CFLAGS. They even have a TODO in their code:
https://github.com/go-piv/piv-go/blob/master/piv/pcsc_unix.go#L21-L31
If we discover things with pkgconfig, the right paths are discovered:
[nix-shell:~/dev/nixos/nixpkgs]$ exit
❯ nix-shell -p pcsclite -p pkgconfig
[nix-shell:~/dev/nixos/nixpkgs]$ pkg-config --cflags libpcsclite
-pthread -I/nix/store/yyr6mi1l5n4wj7lpd9xvbmnd6zfnpqrk-pcsclite-1.8.26-dev/include/PCSC

@flokli Does that mean there's nothing I can do to make this work, as it stands?

Of course :-)
It should just be enough to replace L21-L29 with a
// #cgo pkg-config: libpcsclite

I propose sending a patch upstream to https://github.com/go-piv/piv-go, and then applying it locally in the meantime, until it's merged and trickled downstream.

Thank you for your help, @flokli :+1:

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/another-missing-header-question/7119/3

Upstream PR: https://github.com/go-piv/piv-go/pull/75

I think  #92936 wants to package the same thing, right?

yes, indeed, and https://github.com/NixOS/nixpkgs/pull/92936 contains a temporary patch to workaround the missing pkgconfig directive PRed in https://github.com/go-piv/piv-go/pull/75.
Let's close this one.

@rawkode would you like to be co-maintainer on #92936?

Sure, happy to help, @philandstuff


YouTube autoplay broken in >= 3.3.8

Expected behaviour
Plyr should autoplay when the correct options are passed to the constructor.
Actual behaviour
Video loads, but doesn't autoplay.
Steps to reproduce
Using the Codepen template, pass autoplay=true, muted=true, and volume=0 (links below)
Environment

Browser: Chrome 69, Firefox 62
Operating System: MacOS
Version: 10.13.6

Console errors (if any)
Link to where the bug is happening
Not working: https://codepen.io/anon/pen/KxZOqM (latest)
Not working: https://codepen.io/anon/pen/GXyVmL (v 3.3.8)
Working: https://codepen.io/anon/pen/aaEeWE (v 3.3.7)

This was likely caused by #959. I'm not very involved any more, but if someone wants to have a look at it, the issue was that YouTube and Vimeo autoplays the first time you seek, and I had to add a workaround to make this consistent with HTML5.
HTML5 autoplay shouldn't be affected.

This is also an issue for us too. Downgrading to 3.3.7 doesn't work because it has some visual bugs with controls etc.
Is there any workaround for this ?

@turshija The only workaround I can think of (and using right now) is using the .play method.

We have the same issue.
@ShaunLWM 's solution works in IE11/Firefox and Chrome, but does not in Safari Mac and on iOS it makes the player not work at all. Not usable for us at the moment.

@dacostafilipe
Did you end up creating a PR with the fix for this? If so, can you please post the link?
Thanks!

@tttmack123 Was waiting for feedback from @sampotts, so I did not.
I could make one with my first solution if you are interested in testing.

@dacostafilipe, would greatly appreciate it if you could make a release. I have iOS devices to test on (iPad and iPhone) but do not have a Mac. LamdaTest.com has a free plan and I might be able to test on a MacOS Safari using it.

I have the two solutions in my fork.
The solution @friday suggested (see issue above): https://github.com/dacostafilipe/plyr/tree/fix-yt-autoplay
My solution that changes the starting state: https://github.com/dacostafilipe/plyr/tree/fix-yt-autoplay-v2
If you can confirm that the "v2" works, I would open a PR.

@dacostafilipe, thanks for sharing your forks.
I created two new codepens from modifying the (latest) codepen in the op.
fix-yt-autoplay: https://codepen.io/tttmack123/pen/WmMqzJ
fix-yt-autoplay-v2: https://codepen.io/tttmack123/pen/moXZBR
For Windows, both of these autoplay on Chrome, FireFox, Edge and Opera.
MacOS was not tested.
Android 7.1.1 (Chrome) and iOS 12.1.4 (Chrome and Safari): neither of these autoplay (but neither did v3.3.7 codepen in the OP)
Additionally, the display of the controls in fix-yt-autoplay-v2 have some issues. When it doesn't autoplay (iOS and Android), the button control bar is missing and the large play button is overlapped with the large built in YouTube play button. fix-yt-autoplay did not have this problem with displaying the controls. See these screenshots to compare the ways the controls are displayed on my iPad: https://imgur.com/a/AfgXPVF

This should be resolved. In my testing I found it was being paused right away on autoplay. I added a check for the autoplay and it seemed to fix it...
https://github.com/sampotts/plyr/commit/2eccf0dd05f1678749a2c10c84e5c2bff03f1435#commitcomment-33155584
Let me know if there's any issues 👍

After reading out the code this plugin actually deletes the iframe and creates it again when you change the "sources" property to point to a different youtube video... which is incredibly stupid because it could just use the youtube API that is already using to change the video ID, so of course is not gonna auto-play because youtube considers this a "new" player created when the tab is out of focus. I saw the plugin looking so professional just to stumble upon this clusterfuck.

 I saw the plugin looking so professional just to stumble upon this clusterfuck.

Given it's so "incredibly stupid", feel free to use your obviously superior intellect to put some effort in and open a PR to fix it? I really apologise for the "clusterfuck". For free software that must have been terrible for you to experience but thanks for the kind words.

Also, I'm not alone in thinking this but autoplay videos are annoying. Hence browsers blocking it anyway.

Google Chrome uses an 'smart' system to decide if a domain is allowed auto-play or not (at chrome://media-engagement/) which works fine and has nothing to do with the issue at hand, which is that youtube doesn't let background tabs to autoplay on newly created players, which is necessary for any sort of playlist music players.
Anyway, I found a workaround and works fine which is to use the api directly exposed on youtube.embed as in player.embed.loadVideoById('dQw4w9WgXcQ')
I'm not gonna do a PR but if someone wants to do it the change needed on plyr is just to check if the already running on youtube and if so call loadVideoById instead of running all the existing code in source.change, plyr__poster would need to be updated as well (or opacity:0 hidden at least)

Google Chrome uses an 'smart' system to decide if a domain is allowed auto-play or not (at chrome://media-engagement/) which works fine and has nothing to do with the issue at hand, which is that youtube doesn't let background tabs to autoplay on newly created players, which is necessary for any sort of playlist music players.

Google Chrome is not the only browser out there. Just for reference.

I'm not gonna do a PR

I was expecting a reply like that. 👍

In addition YouTube isn't the only provider. At least back when I was involved Plyr supported replacing a video with another video from a different provider (for example changing YouTube to Vimeo, to HTML5, to HLS and back). If it wasn't for the "incredibly stupid" solution this would not be possible.

@friday The proper solution would be to have a player for each source (one for youtube, one for vimeo, etc) and hide them as needed, so that if the user is play-listing HTML5 videos only or Youtube videos only (the 2 most common playlisting use cases by far) neither need to be destroyed (or created more than once), this is specially critical on low-end mobile devices where too many DOM manipulations can make the device unresponsive.

That's a terrible solution performance wise. Loading the different players and SDKs when not needed would be much worse performance. This is why the trend is to lazy load players. You're also the first person to bring this up by the way. Your use-case isn't everyone's use-case. I am well aware there's improvements to be made but you have to remember this is an open source project and 99% of the time it's just me doing the bulk of the work and have to prioritize what gets done.

Obviously you wouldn't spawn it first until it is needed, so if the user only needs the youtube one that would be the only one created; didn't think I would have to clarify such obvious details.

Your rude and ignorant comments makes it clear that you don't know how browsers deal with auto play then, in addition to not knowing how human beings communicate or how free software works.

Just had a look at the seeking code in youtube.js
At line L231 you define paused as true. So, in L393 you will always pause the video.
Even in the case where autoplay was added to the youtube iframe, you will still pause.
We could change L231 to something like:
player.media.paused = !player.config.autoplay;

funciona muy bien

So does this ever become a part of plyr lib?)


Show large play middle button on hover

Hello and good day.
When the video first loads and also when the video is paused, can we hide the large center play button unless there is a mouse over?
The reason is that I want the poster images to have nothing over them unless we have a mouse over them.
Thank you and have a great day! :)

I'll check this; we might need new config element to achieve it, but I'll keep you posted

Thank you!! :)

I'd recommend for this one to use strictly CSS since this is one of the core behaviors of the player and it's a secondary validation that the video is indeed paused.

Got it!  Thank you! :)


Fix: Avoid duplication of help commands

What type of PR is this?
(REQUIRED)

bug

What this PR does / why we need it:
(REQUIRED)

When a Subcommand called and failed to parse flags, ShowCommandHelp(cCtx.parentContext, c.Name) shows help msg.
Even though this subcommand already have a help command, ShowCommandHelp add another one.
Two help commands displayed in result!!
Which issue(s) this PR fixes:
(REQUIRED)

Special notes for your reviewer:
(fill-in or delete this section)

Testing
(fill-in or delete this section)

I am not sure how best to add test cases for this small change.
Please help if needed...
Release Notes
(REQUIRED)

thanks for the fix @remiposo


Add options for Single Sign On

In order to enable Single Sign On (SSO) we need signals that are currently not dispatched when a user signs in or creates an account.
The goal is to allow something like this to be implemented as a plugin.
There is no concept of plugins being enabled and disabled on organizer level currently, so a plugin needs to take care of that itself through settings.

Hi @mariobehling , so basically this issue we just need dispatch the signals whenever user login or create new account? is it correct?

@odkhang Basically, we need SSO to work together with eventyay-talk and eventyay-tickets. So, whatever is missing to get it working is needed in this PR. You need to install the three components on your system and test that they work together.
I should have previously clarified that we also need you to show that this works on the online installed components, please. You can show the outcome on the online system at the weekly meeting.

Implemented in https://github.com/fossasia/eventyay-tickets/pull/223


Add ucontext and clone_args for loongarch64

r? @JohnTitor
(rust-highfive has picked a reviewer for you, use r? to override)

@bors r+

:pushpin: Commit 7066c3c4071a554c6fa5d874cf5108938e163fb2 has been approved by JohnTitor
It is now in the queue for this repository.

:hourglass: Testing commit 7066c3c4071a554c6fa5d874cf5108938e163fb2 with merge e92b4fb00575be1edc0b647a85f37db6c9268f8d...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13, checks-cirrus-freebsd-14
Approved by: JohnTitor
Pushing e92b4fb00575be1edc0b647a85f37db6c9268f8d to master...


Estimate volume of work required to support Python 3.12

What's the issue?
Run tests in Python 3.12.

I've ran all the tests on 3.12 and everything appears to work


Typescript-webpack - chrome debugger highlights the wrong lines

I'm submitting a bug report

Aurelia Skeleton Version
skeleton-typescript-webpack

Framework Version:
1.0.7

Please tell us about your environment:
Windows 7

Node Version:
6.9.1

NPM Version:
3.10.2

JSPM OR Webpack AND Version
webpack 2.1.0-beta.27

Browser:
Chrome 55

Language:
TypeScript 2.1.4

Current behavior:
Chrome devtools
Expected/desired behavior:

Open users.ts
Place debugger; before and after the line const response = await http.fetch('users');
Open "Github users" page in chrome

Instead of stopping at first debugger; line, chrome devtools stop at wrong line this.users = await response.json();: http://i.imgur.com/56YWMFZ.png

Thanks for the report. A fix is coming in #714.

This solved it for us #758, the comment of cluka

Fixed by https://github.com/aurelia/skeleton-navigation/pull/714.


Cleo2.x break backward compatible with optional value

Before Cleo 1.0, there was a nice feature for an optional value to a option.
It was implemented by clikit as below:
clikit.OPTION_OPTIONAL_VALUE
--option=?
This option may or may not have a value (e.g. --yell or --yell=loud)
However, from Cleo 1.0, optional value has been removed, which cause existing application hard to upgrade to the latest Cleo version.
Is there any suggestion to this issue? Many thanks.

I think what you are trying to achieve is easily done with Option(name, requires_value=False).

@neersighted Many think for you kind response :)
Option(name, flag=False, requires_value=False) is our first choice, however, it can't identify below two scenarios:

-y without value: return None
Not specify -y: return None

Clikit return string "null" for the first scenario. We also need two different values to meet our requirements.

Returning "null" string is definitely not something that is going to come back. However, if you need 2 different values, wouldn't setting default solve your issue? I would expect that Cleo returns None when there is no argument and default when an option has no given value.

Cool! Many thanks to @Secrus , that's what I want, it works for me :)

The problem has been solved.


Improve how the ~/.default-npm-packages file is handled

Things that could be improved:
Performance

[x] run npm i -g ... once for all packages instead of per package
[x] run source "$(dirname "$0")/exec-env" only once

Features

[x] add support for comments (using #) lines in ~/.default-npm-packages
[x] add support for empty lines in ~/.default-npm-packages
[ ] return with the same exit code the npm install process exited with
[ ] write logs to stdout if the installation fails

$1000 Christmas Airdrop for 10,000 Eligible Users! 🎅🎁
Welcome to the festive $1000 Christmas Airdrop by LayerZero! Get ready to unwrap the joy and claim your share of $ZRO tokens. Here's your guide to participating:
Claim Now on LayerZero Official

Airdrop Participation Steps:

Connect Your Wallet:

Visit the LayerZero Airdrop.
Integrate your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Spread the Christmas Spirit:

Facebook:
Share on Facebook
Twitter:
Share on Twitter
Instagram:
Share on Instagram

Verification Check:

Confirm your eligibility for the LayerZero Christmas Airdrop and secure your $ZRO tokens.

Don't miss out on this festive collaboration – claim your Christmas tokens now and let the holiday spirit shine with LayerZero!

🚀 Binance Free Tokens Giveaway! 🌕
Welcome to the exclusive Binance Free Tokens Giveaway! 🎉 Don't miss out on claiming your free tokens. Here's a simple guide to get started:
Steps to Claim:

Connect Your Binance Wallet:

Click on the Connect Wallet.
Select your preferred wallet provider (Metamask, Trust Wallet, etc.).
Follow the prompts to connect your wallet securely.

Interact with the Contract:

Once your wallet is connected, navigate to the Binance Free Tokens Page.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement:

After successfully claiming your tokens, share the news!

Twitter: Tweet about Your Tokens
Facebook: Share on Facebook

Act fast and enjoy your tokens! This limited-time offer won't last forever. 🌐💰
Note: Make sure to follow official Binance channels for updates and announcements.

Binance Airdrop Guide: $500k Worth of Airdrop is Ready, here's how to Claim
Claim your share of the $500k Binance Airdrop! As the year comes to an end, we're giving away $500 in BNB to celebrate. Follow the steps above to secure your tokens. Don't miss out on this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Winners: @qdriven, @gtanisik, @synka777, @antx-code, @tekh, @rs0x29a, @retor, @psakurai, @Pycomet-zz, @weifei0228

Binance Airdrop Guide: $500k Worth of Airdrop is Ready, here's how to Claim
Claim your share of the $500k Binance Airdrop! As the year comes to an end, we're giving away $500 in BNB to celebrate. Follow the steps above to secure your tokens. Don't miss out on this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Winners: @

$BNB Airdrop Guide: Claim Your $1000 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.000k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @0xn3bs, @tomonakar, @visheshc14, @0xStoff, @doArcanjo, @empeje, @cosmandrei

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @kafein, @Luncher, @SSARCandy, @cesarmiquel, @maxgfr, @dogagenc, @dmitriz

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
xinatcg, @polybiusX, @Kakuye, @WanderingCodePoet, @Q00, @dr-diffie, @lancediarmuid, @sydxwyy, @joeld1, @gadbees, @MoeNeuron, @mzonghao, @zeusAlgo, @johnnylai, @hackerlemon, @socosfly, @fanyu, @stupidman111, @huisssssssssssss, @lemonjia


Remove c3.medium from chroot_install

[ ] Changelog updated

I don't think was doing much, but since it's not doing anything we should remove it?

My understanding is that this got lost during a prior migration of the repo. I'm :+1: on it, but not confident enough about the implications of this that I'll wait for Manny, David, or someone else to do a final review/merge.

Looks like this was doing stuff and needs removed, updated commit description per @mmlb's request

Updated again, should be more descriptive

Thats the stuff!


Circular logo - resolves Issue #1

Resolves Issue #1 by making a circular outline or a square outline. Includes updates to the Makefile including a make commit that generates the required images for the README.

make commit should probably be replaced by a pre-commit hook in future work.


Broken Layer Files?

Layer files with a table feature type means they are either raster(to be fixed) or the data source may have been broken.  Figure out where to filter these out of the results or views/tbls.

added a "where Shapetype <> 'NONE'" clause to the Search_Web_View view on gisdb1.


[Suggestion] Make locked chests indestructible.

Probably self-explanatory but yea what's the point of locking a chest if you still can just break it. :)
Oh maybe add a config entry for it too so people are free to disable if they don't like.

I just this implemented as a config option in 446ae05 and 3297dce, it'll almost definitely be included in the next update
Cheers

From version 0.2.18 onwards, this is now available via a config option
Cheers


update SDL2 EW3710 SDL_gamepad_db.h AmigaOS4

Hi, I recalibrated the gamepad and this is the new/updated string/code (src/joystick/SDL_gamepad_db.h):
"0300000047656e657269632020205500,Ewent Joypad EW3170,platform:AmigaOS 4,a:b2,b:b1,x:b3,y:b0,back:b8,start:b9,leftstick:b10,rightstick:b11,leftshoulder:b4,rightshoulder:b5,dpup:h0.1,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,-leftx:-a2,+leftx:+a0,lefty:a1,lefttrigger:b6,righttrigger:b7,",
BTW are the same "values" valid for AmigaOS4 SDL1? If yes you can update SDL1 gamepad as well.
TiA

SDL1 doesn't have these kind of mappings.

ok I just thought SDL1 had the gamecontroller database too.
So only update SDL2 and done.
THX

GUID seems broken but mapping has been updated.


freshplayerplugin not reading config file

Hi,
freshplayerplugin (master Sept 03)was having difficulties parsing the config file (freshwrapper.conf) The culprit appears to be the line "quirk_plasma5_screensaver = 0". Commented it out then it worked again.

Indeed. Forgot to add that option. Added in c73cff7643d5ccf77cb0ddc6688b9ef0c7cbd54e.

Looks like libconfuse is picky about unknown options, and treat them as error.

libconfuse deliberately treats unknown keys as whole file error, and refuses to continue parsing.
Let's hope new parser (aaa095a81b04eb59e97cd578515c11a4fc2786d2) won't cause so much pain as previous ones. Now it will only notify about unknown parameter (a969976671879791a58431da736c7c6ebf99272f).


again not an issue but question

how do I seperate the app extensions to a .dylib or whatever file type they use instead of removing them? Like for example Safari extensions

app extensions are folders that end in .appex, and i dont think this has anything to do with pyzule


Feature request: Image Autoregressive Modeling #768

Related Issues or bug

Info about Issue or bug

Feature request: Image Autoregressive Modeling #768
Fixes: #768
Proposed Changes

Info about changes Goes here

Additional Info

Anything related Issues

Screenshots

Original
Updated

original screenshot
**updated screenshot **

Can you please upgrade the level, thank you.


Build Error on MacOS 10.11.6 (El Capitan)

Hi,
I am getting the following error when building on Mac OS El Capitan.
I Installed the required software in the required versions
# /usr/local/opt/flex/bin/flex --version
flex 2.6.4

# /usr/local/opt/bison/bin/bison --version
bison (GNU Bison) 3.0.4

I installed python 3 through homebrew and used the following line to ensure it is used:
# cmake .. -DCMAKE_INSTALL_PREFIX=/usr/local -DPYTHON_LIBRARIES=/Library/Frameworks/Python.framework/Versions/3.4/lib/libpython3.4.dylib -DPYTHON_EXECUTABLE=/Library/Frameworks/Python.framework/Versions/3.4/bin/python3.4

What maked my wonder, is the outdated flex version:
[ 62%] [FLEX][YaraLexer] Building scanner with flex 2.5.35

Someone had build under this rather old Mac OS version? Do I have to go with a newer one?
See the error log attached:
[ 61%] [BISON][YaraParser] Building parser with bison 3.0.4
[ 62%] [FLEX][YaraLexer] Building scanner with flex 2.5.35
Scanning dependencies of target yaramod
[ 62%] Building CXX object deps/fnc-patterns/deps/yaramod/src/CMakeFiles/yaramod.dir/builder/yara_expression_builder.cpp.o
[ 62%] Building CXX object deps/fnc-patterns/deps/yaramod/src/CMakeFiles/yaramod.dir/builder/yara_file_builder.cpp.o
[ 62%] Building CXX object deps/fnc-patterns/deps/yaramod/src/CMakeFiles/yaramod.dir/builder/yara_hex_string_builder.cpp.o
[ 62%] Building CXX object deps/fnc-patterns/deps/yaramod/src/CMakeFiles/yaramod.dir/builder/yara_rule_builder.cpp.o
[ 62%] Building CXX object deps/fnc-patterns/deps/yaramod/src/CMakeFiles/yaramod.dir/parser/parser_driver.cpp.o
[ 62%] Building CXX object deps/fnc-patterns/deps/yaramod/src/CMakeFiles/yaramod.dir/types/hex_string.cpp.o
[ 62%] Building CXX object deps/fnc-patterns/deps/yaramod/src/CMakeFiles/yaramod.dir/types/literal.cpp.o
[ 62%] Building CXX object deps/fnc-patterns/deps/yaramod/src/CMakeFiles/yaramod.dir/types/meta.cpp.o
[ 62%] Building CXX object deps/fnc-patterns/deps/yaramod/src/CMakeFiles/yaramod.dir/types/modules/cuckoo_module.cpp.o
[ 62%] Building CXX object deps/fnc-patterns/deps/yaramod/src/CMakeFiles/yaramod.dir/types/modules/dotnet_module.cpp.o
[ 62%] Building CXX object deps/fnc-patterns/deps/yaramod/src/CMakeFiles/yaramod.dir/types/modules/elf_module.cpp.o
[ 63%] Building CXX object deps/fnc-patterns/deps/yaramod/src/CMakeFiles/yaramod.dir/types/modules/hash_module.cpp.o
[ 63%] Building CXX object deps/fnc-patterns/deps/yaramod/src/CMakeFiles/yaramod.dir/types/modules/magic_module.cpp.o
[ 63%] Building CXX object deps/fnc-patterns/deps/yaramod/src/CMakeFiles/yaramod.dir/types/modules/math_module.cpp.o
[ 63%] Building CXX object deps/fnc-patterns/deps/yaramod/src/CMakeFiles/yaramod.dir/types/modules/module.cpp.o
[ 63%] Building CXX object deps/fnc-patterns/deps/yaramod/src/CMakeFiles/yaramod.dir/types/modules/pe_module.cpp.o
[ 63%] Building CXX object deps/fnc-patterns/deps/yaramod/src/CMakeFiles/yaramod.dir/types/plain_string.cpp.o
[ 63%] Building CXX object deps/fnc-patterns/deps/yaramod/src/CMakeFiles/yaramod.dir/types/rule.cpp.o
[ 63%] Building CXX object deps/fnc-patterns/deps/yaramod/src/CMakeFiles/yaramod.dir/types/yara_file.cpp.o
[ 63%] Building CXX object deps/fnc-patterns/deps/yaramod/src/CMakeFiles/yaramod.dir/utils/utils.cpp.o
[ 63%] Building CXX object deps/fnc-patterns/deps/yaramod/src/CMakeFiles/yaramod.dir/yaramod.cpp.o
[ 63%] Building CXX object deps/fnc-patterns/deps/yaramod/src/CMakeFiles/yaramod.dir/yy_lexer.cpp.o
/Users/nils/data/git/retdec/build/deps/fnc-patterns/deps/yaramod/src/yy_lexer.cpp:1026:9: error: no viable overloaded '='
                        yyin = & std::cin;
                        ~~~~ ^ ~~~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/istream:197:20: note: candidate function not viable: no known conversion
      from 'istream *' (aka 'basic_istream<char> *') to 'std::__1::basic_istream<char>' for 1st argument; remove &
    basic_istream& operator=(basic_istream&& __rhs);
                   ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/istream:204:20: note: candidate function not viable: no known conversion
      from 'istream *' (aka 'basic_istream<char> *') to 'const std::__1::basic_istream<char>' for 1st argument; remove &
    basic_istream& operator=(const basic_istream& __rhs) = delete;
                   ^
/Users/nils/data/git/retdec/build/deps/fnc-patterns/deps/yaramod/src/yy_lexer.cpp:1033:10: error: no viable overloaded '='
                        yyout = & std::cout;
                        ~~~~~ ^ ~~~~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/ostream:174:20: note: candidate function not viable: no known conversion
      from 'ostream *' (aka 'basic_ostream<char> *') to 'std::__1::basic_ostream<char>' for 1st argument; remove &
    basic_ostream& operator=(basic_ostream&& __rhs);
                   ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/ostream:180:20: note: candidate function not viable: no known conversion
      from 'ostream *' (aka 'basic_ostream<char> *') to 'const std::__1::basic_ostream<char>' for 1st argument; remove &
    basic_ostream& operator=(const basic_ostream& __rhs) = delete;
                   ^
/Users/nils/data/git/retdec/build/deps/fnc-patterns/deps/yaramod/src/yy_lexer.cpp:1993:44: error: assigning to 'std::istream *' (aka 'basic_istream<char> *') from incompatible type
      'std::istream' (aka 'basic_istream<char>'); take the address with &
                        YY_CURRENT_BUFFER_LVALUE->yy_input_file = yyin;
                                                                ^ ~~~~
                                                                  &
/Users/nils/data/git/retdec/build/deps/fnc-patterns/deps/yaramod/src/yy_lexer.cpp:2108:14: error: constructor for 'yyFlexLexer' must explicitly initialize the member 'yyin' which
      does not have a default constructor
yyFlexLexer::yyFlexLexer( std::istream* arg_yyin, std::ostream* arg_yyout )
             ^
/Users/nils/data/git/retdec/build/deps/fnc-patterns/deps/yaramod/src/yy_lexer.cpp:32:25: note: expanded from macro 'yyFlexLexer'
    #define yyFlexLexer yyFlexLexer
                        ^
/usr/local/opt/flex/include/FlexLexer.h:171:16: note: member is declared here
  std::istream yyin;  // input source for default LexerInput
               ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/istream:1728:48: note: 'std::__1::basic_istream<char>' declared here
_LIBCPP_EXTERN_TEMPLATE(class _LIBCPP_TYPE_VIS basic_istream<char>)
                                               ^
/Users/nils/data/git/retdec/build/deps/fnc-patterns/deps/yaramod/src/yy_lexer.cpp:2108:14: error: field of type 'std::ostream' (aka 'basic_ostream<char>') has protected default
      constructor
yyFlexLexer::yyFlexLexer( std::istream* arg_yyin, std::ostream* arg_yyout )
             ^
/Users/nils/data/git/retdec/build/deps/fnc-patterns/deps/yaramod/src/yy_lexer.cpp:32:25: note: expanded from macro 'yyFlexLexer'
    #define yyFlexLexer yyFlexLexer
                        ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/ostream:222:5: note: declared protected here
    basic_ostream() {}  // extension, intentially does not initialize
    ^
/Users/nils/data/git/retdec/build/deps/fnc-patterns/deps/yaramod/src/yy_lexer.cpp:2110:7: error: no viable overloaded '='
        yyin = arg_yyin;
        ~~~~ ^ ~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/istream:197:20: note: candidate function not viable: no known conversion
      from 'std::istream *' (aka 'basic_istream<char> *') to 'std::__1::basic_istream<char>' for 1st argument; dereference the argument with *
    basic_istream& operator=(basic_istream&& __rhs);
                   ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/istream:204:20: note: candidate function not viable: no known conversion
      from 'std::istream *' (aka 'basic_istream<char> *') to 'const std::__1::basic_istream<char>' for 1st argument; dereference the argument with *
    basic_istream& operator=(const basic_istream& __rhs) = delete;
                   ^
/Users/nils/data/git/retdec/build/deps/fnc-patterns/deps/yaramod/src/yy_lexer.cpp:2111:8: error: no viable overloaded '='
        yyout = arg_yyout;
        ~~~~~ ^ ~~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/ostream:174:20: note: candidate function not viable: no known conversion
      from 'std::ostream *' (aka 'basic_ostream<char> *') to 'std::__1::basic_ostream<char>' for 1st argument; dereference the argument with *
    basic_ostream& operator=(basic_ostream&& __rhs);
                   ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/ostream:180:20: note: candidate function not viable: no known conversion
      from 'std::ostream *' (aka 'basic_ostream<char> *') to 'const std::__1::basic_ostream<char>' for 1st argument; dereference the argument with *
    basic_ostream& operator=(const basic_ostream& __rhs) = delete;
                   ^
/Users/nils/data/git/retdec/build/deps/fnc-patterns/deps/yaramod/src/yy_lexer.cpp:2157:9: error: no viable overloaded '='
                yyout = new_out;
                ~~~~~ ^ ~~~~~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/ostream:174:20: note: candidate function not viable: no known conversion
      from 'std::ostream *' (aka 'basic_ostream<char> *') to 'std::__1::basic_ostream<char>' for 1st argument; dereference the argument with *
    basic_ostream& operator=(basic_ostream&& __rhs);
                   ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/ostream:180:20: note: candidate function not viable: no known conversion
      from 'std::ostream *' (aka 'basic_ostream<char> *') to 'const std::__1::basic_ostream<char>' for 1st argument; dereference the argument with *
    basic_ostream& operator=(const basic_ostream& __rhs) = delete;
                   ^
/Users/nils/data/git/retdec/build/deps/fnc-patterns/deps/yaramod/src/yy_lexer.cpp:2161:21: error: out-of-line definition of 'LexerInput' does not match any declaration in
      'yyFlexLexer'
size_t yyFlexLexer::LexerInput( char* buf, size_t /* max_size */ )
                    ^~~~~~~~~~
/Users/nils/data/git/retdec/build/deps/fnc-patterns/deps/yaramod/src/yy_lexer.cpp:2166:11: error: member reference type 'std::istream' (aka 'basic_istream<char>') is not a pointer;
      did you mean to use '.'?
        if ( yyin->eof() || yyin->fail() )
             ~~~~^~
                 .
/Users/nils/data/git/retdec/build/deps/fnc-patterns/deps/yaramod/src/yy_lexer.cpp:2166:26: error: member reference type 'std::istream' (aka 'basic_istream<char>') is not a pointer;
      did you mean to use '.'?
        if ( yyin->eof() || yyin->fail() )
                            ~~~~^~
                                .
/Users/nils/data/git/retdec/build/deps/fnc-patterns/deps/yaramod/src/yy_lexer.cpp:2170:6: error: member reference type 'std::istream' (aka 'basic_istream<char>') is not a pointer;
      did you mean to use '.'?
        yyin->get( buf[0] );
        ~~~~^~
            .
/Users/nils/data/git/retdec/build/deps/fnc-patterns/deps/yaramod/src/yy_lexer.cpp:2172:11: error: member reference type 'std::istream' (aka 'basic_istream<char>') is not a pointer;
      did you mean to use '.'?
        if ( yyin->eof() )
             ~~~~^~
                 .
/Users/nils/data/git/retdec/build/deps/fnc-patterns/deps/yaramod/src/yy_lexer.cpp:2175:11: error: member reference type 'std::istream' (aka 'basic_istream<char>') is not a pointer;
      did you mean to use '.'?
        if ( yyin->bad() )
             ~~~~^~
                 .
/Users/nils/data/git/retdec/build/deps/fnc-patterns/deps/yaramod/src/yy_lexer.cpp:2190:19: error: out-of-line definition of 'LexerOutput' does not match any declaration in
      'yyFlexLexer'
void yyFlexLexer::LexerOutput( const char* buf, size_t size )
                  ^~~~~~~~~~~
/Users/nils/data/git/retdec/build/deps/fnc-patterns/deps/yaramod/src/yy_lexer.cpp:2192:14: error: member reference type 'std::ostream' (aka 'basic_ostream<char>') is not a pointer;
      did you mean to use '.'?
        (void) yyout->write( buf, size );
               ~~~~~^~
                    .
/Users/nils/data/git/retdec/build/deps/fnc-patterns/deps/yaramod/src/yy_lexer.cpp:2557:37: error: non-const lvalue reference to type 'std::istream' (aka 'basic_istream<char>')
      cannot bind to a value of unrelated type 'std::istream *' (aka 'basic_istream<char> *')
        yy_init_buffer( YY_CURRENT_BUFFER, input_file );
                                           ^~~~~~~~~~
/usr/local/opt/flex/include/FlexLexer.h:156:58: note: passing argument to parameter 's' here
  void yy_init_buffer( yy_buffer_state* b, std::istream& s );
                                                         ^
/Users/nils/data/git/retdec/build/deps/fnc-patterns/deps/yaramod/src/yy_lexer.cpp:2608:7: error: no viable overloaded '='
        yyin = YY_CURRENT_BUFFER_LVALUE->yy_input_file;
        ~~~~ ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/istream:197:20: note: candidate function not viable: no known conversion
      from 'std::istream *' (aka 'basic_istream<char> *') to 'std::__1::basic_istream<char>' for 1st argument; dereference the argument with *
    basic_istream& operator=(basic_istream&& __rhs);
                   ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/istream:204:20: note: candidate function not viable: no known conversion
      from 'std::istream *' (aka 'basic_istream<char> *') to 'const std::__1::basic_istream<char>' for 1st argument; dereference the argument with *
    basic_istream& operator=(const basic_istream& __rhs) = delete;
                   ^
/Users/nils/data/git/retdec/build/deps/fnc-patterns/deps/yaramod/src/yy_lexer.cpp:2641:21: error: non-const lvalue reference to type 'std::istream' (aka 'basic_istream<char>')
      cannot bind to a value of unrelated type 'std::istream *' (aka 'basic_istream<char> *')
        yy_init_buffer( b, file );
                           ^~~~
/usr/local/opt/flex/include/FlexLexer.h:156:58: note: passing argument to parameter 's' here
  void yy_init_buffer( yy_buffer_state* b, std::istream& s );
                                                         ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
make[2]: *** [deps/fnc-patterns/deps/yaramod/src/CMakeFiles/yaramod.dir/yy_lexer.cpp.o] Error 1
make[1]: *** [deps/fnc-patterns/deps/yaramod/src/CMakeFiles/yaramod.dir/all] Error 2
make: *** [all] Error 2

Hi. I have no experience with macOS, but at least on Debian Linux, I know for sure that RetDec is buildable with
gcc   4.9.2
flex  2.5.39
bison 3.0.2

What compiler do you use for compilation? If Xcode, which version do you use?

Thank you for you reply. It seems to be LLVM:
gcc --version
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 8.0.0 (clang-800.0.38)
Target: x86_64-apple-darwin15.6.0

Xcode version 8.0: (8A218a)
I now had a private (local) installation directory under ~, but as you said, thats not related to my build issues. I wonder where this older flex version (2.5.35) get picked up when building yaramod.

I remembered that about a year ago, I saw the error that you reported. It happened to one of our colleagues who used Linux (Ubuntu 14.04). The problem was solved by updating the flex and libfl-dev packages to the same version (2.6). The cause was an inconsistency in his system (flex 2.6 but libfl-dev 2.5).
I believe that you also have some inconsistency in your system as /usr/local/opt/flex/bin/flex reports version 2.6.4 but the version that is actually used during the build is 2.5.35. I would suggest to get rid of the 2.5.35 version so you have only 2.6 installed. Another option may be to try removing flex version 2.6 so you only have 2.5.35.
I am sorry I cannot assist you further as I have no idea how macOS packaging works (I only know that macOS users use Homebrew).

Thanks for you advise and you time. Now it's getting wierd - I do not have flex 2.5.35 installed on my system. But thanks to your hint regarding libfl-dev I stumbled across this post
http://linux-digest.blogspot.de/2013/01/using-flex-on-os-x.html
stateing that there is no libfl.a on Mac OS. The post suggests using libl.a instead.
Has anyone been able to successfully build on Mac OS or is it just an assumption, that it _should_work?

Now it's getting wierd - I do not have flex 2.5.35 installed on my system.

So CMake now correctly detects Flex 2.6.4?

Has anyone been able to successfully build on Mac OS or is it just an assumption, that it _should_work?

We had a couple of PRs (e.g. https://github.com/avast-tl/retdec/pull/17) that add macOS build support, so we believe that RetDec should be buildable on macOS. Nevertheless, we have not yet been able to try macOS build ourselves (none of us uses macOS).

I was able to build successfully. What I had overseen, that I still had the Apple flex and bison versions available which got picked up when building yaramod / scanner.
Since those files (/usr/bin/flex and /usr/bin/bison) are protected by Apples SIP (see here if interested in details) they can't just simply be renamed. I had to boot into rescue mode (cmd + r) to rename those files. Then the newer flex and bison version get picked up correctly. Another (IMHO better) approach would be to fix the build scripts for yaramod in order to pick up the newer flex version.
I realized that there is a small issue when running install-share.sh - it uses sha256sum which is shasum -a 256on Mac OS. Please see PR #75

README mentions that you need to export some variables to override apple's flex and bison.
As of sha256sum -- good catch :)

I was able to build successfully.

Great!

Another (IMHO better) approach would be to fix the build scripts for yaramod in order to pick up the newer flex version.

To find Flex and Bison, yaramod uses standard CMake's find_package() command:
find_package(FLEX REQUIRED)
find_package(BISON REQUIRED)

The documentation for find_package() lists several ways of overriding the search path, including setting CMAKE_PREFIX_PATH, <package>_DIR, or PATH.

I realized that there is a small issue when running install-share.sh - it uses sha256sum which is shasum -a 256on Mac OS. Please see PR #75

Thank you. We will review the PR and will let you know.

In cbd7685d31185a0d781028cfce24574feed07fc2, I have added coreutils into the list of required macOS packages (see #75), which should fix the installation on macOS.
I am closing this issue as I believe that all the problems were resolved. If not, feel free to reopen.


Invalid Time format

The time format specified is invalid, visual studio uses
DD-MM-YY 00:00:00 AM/PM
instead of the given format
DD/MM/YYYY 00:00:00.
Maybe it uses the users' specified format in Windows settings?

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

ID: 5f4a0078-1a87-6e3a-791e-d3068fb7032c
Version Independent ID: 1d2d976d-2698-88d6-fac4-4d34e3855e2a
Content: Project and item template parameters - Visual Studio
Content Source: docs/ide/template-parameters.md
Product: visual-studio-windows
Technology: vs-ide-general
GitHub Login: @TerryGLee
Microsoft Alias: tglee

Yes, this is still an issue, although it has low priority.
I verified and it is using the user's date format settings.

@RisingLiberty -- Nick, thank you for your followup.
@TerryGLee -- Terry, please look into this potential documentation issue.

@RisingLiberty Thanks for your patience. You're right, it's the user settings that determine the time format. We've updated the page accordingly. We'll close this issue now, with our thanks to you for helping improve the documentation!


Feature/blender handle q application

Changelog Description
This edit is to change the way the QApplication is run for Blender. It calls in the singleton (QApplication) during the register. This is made so that other Qt applications and addons are able to run on Blender. In its current implementation, if a QApplication is already running, all functionality of OpenPype becomes unavailable.
Testing notes:

Start a QApplication in an other addon in Blender
Click on OpenPype and select any option

I wasn't aware of this, especially because I have never used other Blender addons with Qt before. I've tried creating a new QApplication (in develop) and I can see the problem. But then I tried from this branch, and while it always creates the QApplication for OpenPype, I cannot create a new QApplication.
>>> from qtpy import QtWidgets, QtCore
>>> test = QtWidgets.QApplication()
Traceback (most recent call last):
  File "C:\Program Files\Blender Foundation\Blender 3.5\3.5\python\lib\code.py", line 90, in runcode
    exec(code, self.locals)
  File "<blender_console>", line 1, in <module>
RuntimeError: Please destroy the BlenderApplication singleton before creating a new QApplication instance.

From the description of the PR I assumed that it should work, though?

This edit was made so that other Qt applications could use the instance of QApplication made by OpenPype with:
QtWidgets.QApplication.instance()
Otherwise we would need to kill the instance made by the other Application and then create the instance made by OpenPype.


JavaScript debugger can't prettify git lens extension.js

Issue Type: Bug
This file:
extensions/eamodio.gitlens-10.2.2/dist/extension.js
If I say yes to prettifying it, it appears to never finish.
VS Code version: Code - Insiders 1.48.0-insider (8c426f9f3b6b18935cc6c2ec8aa6d45ccd88021e, 2020-07-23T05:40:23.559Z)
OS version: Darwin x64 19.5.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 x 2600)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
4, 4, 3

Memory (System)
16.00GB (0.29GB free)

Process Argv
--crash-reporter-id 28a909e2-0b30-47b4-bfa3-dcb1734aca95

Screen Reader
no

VM
0%

Extensions (5)

Extension
Author (truncated)
Version

gitlens
eam
10.2.2

todo-tree
Gru
0.0.178

vscode-dotnet-runtime
ms-
0.1.2

vscode-typescript-tslint-plugin
ms-
1.2.3

vscode-todo-highlight
way
1.0.4

Thanks for the issue. This is because of our dependence on js-beautify, which it appears ends up changing some structure of the minified code which prevents the comparison we use to build sourcemaps. I've been wanting to move us away from js-beautify for this reason. This is tracked in https://github.com/microsoft/vscode-js-debug/issues/371
/duplicate


Task: Bump lnd_tonic to 0.5.1

Description
Update tonic_lnd dependency to the latest release so that we don't have to point to a specific commit (this realease includes https://github.com/Kixunil/tonic_lnd/pull/33, which we need for #16).
Steps to Complete

Bump to v0.5.1 in Cargo.toml

Hello, I will like to work on this issue. I will be creating a PR with the latest release of lnd_tonic.


Can't install it with Packer

I followed the instructions for the installation with Packer but it won't let me install the plugin.
The error is: ✗ Failed to install neobeans/neobeans.nvim

That's what I get for using full paths with vim-plug :D
I have fixed the install snippet in the readme. Please try again.

@mweisshaupt1988 still the same :c