Uncomment and fix tests

currently two in tests/* are commented out. this issue represents the task of uncommenting them, ensuring that they continue to be relevant to tide's api, and getting them to pass. this might be fixed by one or two prs

[ ] wildcard
[ ] response

"tests/wildcard.rs" and "tests/response.rs" were fixed.
Maybe, this issue can close.

Thanks @yusuke-ota!


astctl: Common command class

We should use a common class for commands to reduce code overlap.
The class should also handle the timeout issue

This should probably be done at the same time as #15

This should probably be done at the same time as #15


⚠ ClamAV has degraded performance

In 6c1b5fe, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 207 ms

Resolved: ClamAV performance has improved in 58b52ce.


ARM builds are coming from the wrong forest (should be jdk8u)

From Stuart Monteith
According to:
https://ci.adoptopenjdk.net/job/openjdk_build_arm64_linux/11/consoleFull
You are building against:
http://hg.openjdk.java.net/aarch64-port/jdk8
This should be:
http://hg.openjdk.java.net/aarch64-port/jdk8u
which is the currently maintained tree.

@gdams has fixed this.


How to look at another video player?

Hi. I want to open in the totem or bomi, but it says error. In vlc normally opens,but it is not my favorite player

Hi!
Well, I don't know how I can help you. That's not a very detailed issue explanation...
Also, please don't use the issue tracker for personal issues that are unrelated to the application.
Did you try setting the right path to either of those players in the settings menu under the player section?
which totem or which bomi should return the path of those players.
Is it working without the GUI?
livestreamer -p /path/to/player twitch.tv/CHANNEL best

Dont'w work
http://storage8.static.itmages.ru/i/15/1031/h_1446301450_3311641_a8ea1f0be3.png

This looks like you're having some codec issues, etc, and totem is unable to play the video stream. VLC has bundled all that stuff, that's why I think it's working for you...
Sorry, but I can't help you with your issue.. :worried:
I'm closing the thread now, since this has nothing to do with either Livestreamer Twitch GUI nor Livestreamer.


commandLineRenderer.jsx has changed in Adobe After Effects 2022

Describe the bug
The unpatched commandLineRenderer.jsx supplied with Adobe After Effects v22 has changed from previous versions. As per the official documentation there are now additional options:

-OMtemplate & -RStemplate for Output Module & Render Settings
-mfr as a replacement for -mp for multi-frame rendering.

The patched commandLineRenderer.jsx supplied with nexrender mostly works with AE 2022 after being applied, but it doesn't allow the above options, which is a shame as I'd like to try out the new multi-frame rendering and also see if it is compatible with M1-native beta of After Effects.
Information about environment

Which version of nexrender are you using? 1.32.0
What kind of the setup do you have? (server+worker or cli) Custom worker that requires the nexrender core library
Are you using pre-built binaries or globally installed npm packages? npm packages
Which kind (and version) of operating system you are running it in? MacOS 10.15 (Catalina) & 11 (Big Sur)

Expected behavior
In an ideal world, the patched commandLineRenderer.jsx would offer the same options as AE 2022's unpatched version. I've used nexrender enough that I'm happy to write such a patch and submit it as a PR.
But I also see a backwards-compatibility problem: a patched version of the v22.0 script won't then work with After Effects v18.x. So I guess you will also need version detection on the patcher, and different versions of the patched commandLineRenderer.jsx in assets to apply. But I'm not quite confident to dive into that without discussing here first...
An alternative thought was if there is any other way of patching the renderer that is futureproof and version-agnostic, but I don't know enough about AE's internals to say for sure.

Update: I have now added a PR for this: #656

@chrisapplegate thank you for the PR
it's indeed hard to find a way for that to work for both versions
i might need some time to think about it as well

Assuming this can be closed?

The latest patch for this does not work with After Effects Beta which doesn't include a year label that's expected.


release v1.0.0

Merge into master

Well done!

I pushed the v1.0.0 tag, which should be triggering a deploy to PyPi, with pre-generated swig files so it's not necessary to have swig installed.

Test coverage is looking good.

It was higher, but then I had added new features.  Can always add more tests, time to start on version 1.1


Allow overwriting of the 'platform' parameter (close #476)

Adapted the code to the same behaviour of the Android tracker where the platform parameter p can be overwritten by the developer.

Unfortunately NS_TYPED_ENUM wasn't enough to fix the problem.
I've adopted a different solution that seems to be quite defensive.

@paulboocock  I've also added in the description of this PR a draft section for the documentation describing this feature.
Please, could you give a quick review to that too?
Thanks!


Change shortcuts for line comment, stream comment, reset zoom and transparent mode

Change shortcuts for the following actions:

Line Comment : Ctrl+Q change to Ctrl+/
Stream Comment : Ctrl+Shift+Q change to Ctrl+Shift+/
Reset Zoom: Ctrl+/ change to Ctrl+0
Transparent Mode: Ctrl+0 change to nothing (I guess that nobody uses this action).

I believe that new shortcuts are more convenient and more widely used, aren't they?

Sorry, I don't think they are.

@XhmikosR  Ctrl+/ for line comment is used by Eclipse, IntelliJ IDEA / Android Studio, NetBeans and XCode (Command+/) in default settings.

Sure, but for my use case Ctrl+Q is standard and I'm used to it.

That being said, if more people want this, I can always revisit. I'm mostly interested about the comment shortcuts which have been like this for years. The others are OK.

@popov895 I use the transparent mode regularly and I often activate it using the shortcut too. I'm quite sure I'm not the only one who does his either.
Is it possible that instead of removing the key binding, you remap it to something else?

Transparent Mode: Ctrl+0 change to nothing (I guess that nobody uses this action).

source

Most applications I use that allow zooming use Ctrl++, Ctrl+-, and Ctrl+0 for zoom in, out, reset. I think that this is sort of an "industry standard". I'm talking most browsers, most photo editing apps etc.

Yes, I know of this de-facto set of key combinations.
My point is that rather than removing the shortcut, kindly consider
remapping it to some other combination.
Thank you.
On 6 Aug 2017 21:34, "Gregory Netsas"<EMAIL_ADDRESS>wrote:

Most applications I use that allow zooming use Ctrl++, Ctrl+-, and Ctrl+0
for zoom in, out, reset. I think that this is sort of an "industry
standard". I'm talking most browsers, most photo editing apps etc.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/XhmikosR/notepad2-mod/pull/197#issuecomment-320534304,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHNbgqyDRBHSLznigpJr2-4p3De88nBHks5sVjFXgaJpZM4ORvNS
.


Moving to an MIT licensed OTP library?

I am looking at unifying the OTP interface. Having to specify TOTP or HOTP is no fun. A better alternative is to have a generic otp action that works with either. This is how browserpass does it.
I haven't started writing any of the code because I wanted to get opinions on switching to gokyle/twofactor. My reasons for wanting to switch are:

MIT licensed
Fewer 3rd party dependencies (only one: https://godoc.org/rsc.io/qr)
Simpler API that has one entry point for HOTP and TOTP.

We generally prefer MIT licensed libaries. Having fewer dependencies also sounds good.
If the library you suggested supports the existing OTP use cases we should probably switch to it.


AUX channel type

Hi all,
I am using B-Alert X24 EEG System and it has 24 channels which 20 of them are EEG type and one of them is ECG type but I do not know the types of rest of them which are 'AUX1 (Raw)', 'AUX2 (Raw)', 'AUX3 (Raw)'. Do you know by any chance what can be the type of AUX?
Thanks!

@Sonia2016 can you read the raw file and type?:  raw.info['ch_names']. It should provide you with all the channel names.

@Sonia2016 can you read the raw file and type?: raw.info['ch_names']. It should provide you with all the channel names. I guess those are stim/resp channels.

Thanks @dasdiptyajit ! Unfortunately, I do not have types of my channels in raw.info. The reason is that I've created the raw.info by myself based on the .txt data created by B-Alert. I am not quite sure what do you mean by stim/resp channels, are the types of channels if yes how should I name it in the raw.info?

you can pick any name you like. It's just the channel type that will matter
as it is liked to physical units like Volts that are used for plotting.

@Sonia2016 'AUX1 (Raw)', 'AUX2 (Raw)', 'AUX3 (Raw)' could be auxiliary channels (e.g., typically ECG/EOG channels) or other external trigger channels such as stimulus or response. You should try to look at the technical specification of your EEG system. Anyhow, the naming/tagging doesn't matter much as long as you use the channels in a right way with proper physical units that @agramfort has already mentioned.

@Sonia2016 'AUX1 (Raw)', 'AUX2 (Raw)', 'AUX3 (Raw)' could be auxiliary channels (e.g., typically ECG/EOG channels) or other external trigger channels such as stimulus or response. You should try to look at the technical specification of your EEG system. Anyhow, the naming/tagging doesn't matter much as long as you use the channels in a right way with proper physical units that @agramfort has already mentioned.

Thanks so much, @dasdiptyajit ! I Placed the mastoid channels (AUX1-AUX2) directly on the bone behind right and left ears. As well as two channels (AUX3 and AUX4) on collar bone which I think one of them has automatically been replaced by ECG. Can I still consider AUX1 and two as EOG considering the fact that they are both attached behind the ears?

use the set_channel_types method of raw to set properly your channel types.
If your pb is solved please close the issue

@Sonia2016 I would additionally select one frontal EEG channel (e.g., Fp1/Fp2) to use it as EOG channel since the sensor located close to the eyes has more chances to pick up eye blinks.

Thanks @dasdiptyajit! that was very helpful!


Suggestion: Export Selection as NBT

There is a /nbt export file command, right? Well, when I'm making datapacks it comes up a lot that I include a structure file as a .nbt file. Usually, I just do this by using a structure block and then saving it and then going and getting the file manually. But it would be a lot easier if the command was more like I could do something like /nbt export area -296 88 -630 -299 84 -624 and then I could just open the file in chat like you have for the file option. Or maybe, if you do /nbt export area -296 88 -630 and there's a structure block at that position, it will export whatever selection that has.

This currently isn't really in the scope of this mod - you could try suggesting this to a mod like World Edit however (World Edit already has this for schematics, so it seems natural to add a structure variant if that doesn't already exist)


The confirmation should be sent after name change and role assignment

https://github.com/Cheukting/registration_desk/blob/bd0dbb4154b070f2eed4dee65c474d35f2465f94/bot.py#L146-L148
This part should probably move down after the role assignment. In the rare case when name change results in a failure, we are still getting the confirmation that the user is successfully registered. One such case is that Discord restricts the nickname to <=32 characters. So if a user has a very long name, they would have got the message that they are successfully registered, but in fact they are not and cannot see any channels.

Done!


URI comparisons should be case-insensitive on the URI scheme portion

(Migrated from https://openrdf.atlassian.net/browse/SES-649)
This is a problem when you are getting data from different sources which use different ways of formatting their URIs (all of them correct). For example: http://demo.com#abc and HTTP://demo.com#abc are equal. I could live with an option where we can say "strict" uri compliance (+normalization i.e. all lowercase for example) in exchange for a bit of performance loss during upload into the repository. See http://www.ietf.org/rfc/rfc3987.txt Quick summary is (for IRI or URI) - schema (ftp: of http:of mailto:...) is case insensitive - host name (following schema + '//', and occasionally after '@' [mailto://user@host/) is case insensitive - the rest is case sensitive

Per RDF 1.1 Concepts and Abstract Syntax:

Two IRIs are equal if and only if they are equivalent under Simple String Comparison according to section 5.1 of RFC3987. Further normalization MUST NOT be performed when comparing IRIs for equality.

That suggests that normalising the scheme case here would be a bug. The spec is clear that using an uppercase HTTP: isn't recommended ("Interoperability problems can be avoided by minting only IRIs that are normalized "), but it's the producers responsibility to change.

Good find Joseph, thanks.


iOS installation failing due to missing dependencies during 'pod install'; add guidance on Ruby minimum version

OS Platform and Distribution
MacOS Sonoma
Compiler version
No response
Programming Language and version
Use of Cocoapods to install dependencies for an iOS project
Installed using virtualenv? pip? Conda?(if python)
No response
MediaPipe version
No response
Bazel version
No response
XCode and Tulsi versions (if iOS)
No response
Android SDK and NDK versions (if android)
No response
Android AAR (if android)
None
OpenCV version (if running on desktop)
No response
Describe the problem
Followed iOS setup at https://ai.google.dev/edge/mediapipe/solutions/setup_ios.  Default ruby version on MacOS (2.6) causes install failure; no guidance on expected or minimum Ruby version.
Complete Logs
$ cd mediapipe-samples/examples/text_classification/ios
$ pod install

Analyzing dependencies
Adding spec repo `trunk` with CDN `https://cdn.cocoapods.org/`
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require': cannot load such file -- ffi_c (LoadError)
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /Library/Ruby/Gems/2.6.0/gems/ffi-1.17.0-x86_64-darwin/lib/ffi.rb:5:in `rescue in <top (required)>'
	from /Library/Ruby/Gems/2.6.0/gems/ffi-1.17.0-x86_64-darwin/lib/ffi.rb:2:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /Library/Ruby/Gems/2.6.0/gems/ethon-0.16.0/lib/ethon.rb:3:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /Library/Ruby/Gems/2.6.0/gems/typhoeus-1.4.1/lib/typhoeus.rb:2:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/cdn_source.rb:440:in `download_typhoeus_impl_async'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/cdn_source.rb:372:in `download_and_save_with_retries_async'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/cdn_source.rb:365:in `download_file_async'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/cdn_source.rb:338:in `download_file'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/cdn_source.rb:53:in `refresh_metadata'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source.rb:31:in `initialize'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/cdn_source.rb:30:in `initialize'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:315:in `new'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:315:in `block in source_from_path'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:322:in `source_from_path'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:331:in `block in aggregate_with_repos'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:331:in `map'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:331:in `aggregate_with_repos'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:26:in `aggregate'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:60:in `all'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/user_interface/error_report.rb:173:in `repo_information'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/user_interface/error_report.rb:77:in `stack'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/user_interface/error_report.rb:24:in `report'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/command.rb:66:in `report_error'
	from /Library/Ruby/Gems/2.6.0/gems/claide-1.1.0/lib/claide/command.rb:396:in `handle_exception'
	from /Library/Ruby/Gems/2.6.0/gems/claide-1.1.0/lib/claide/command.rb:337:in `rescue in run'
	from /Library/Ruby/Gems/2.6.0/gems/claide-1.1.0/lib/claide/command.rb:324:in `run'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/command.rb:52:in `run'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/bin/pod:55:in `<top (required)>'
	from /usr/local/bin/pod:23:in `load'
	from /usr/local/bin/pod:23:in `<main>'
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require': dlopen(/Library/Ruby/Gems/2.6.0/gems/ffi-1.17.0-x86_64-darwin/lib/2.6/ffi_c.bundle, 0x0009): tried: '/Library/Ruby/Gems/2.6.0/gems/ffi-1.17.0-x86_64-darwin/lib/2.6/ffi_c.bundle' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/Library/Ruby/Gems/2.6.0/gems/ffi-1.17.0-x86_64-darwin/lib/2.6/ffi_c.bundle' (no such file), '/Library/Ruby/Gems/2.6.0/gems/ffi-1.17.0-x86_64-darwin/lib/2.6/ffi_c.bundle' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')) - /Library/Ruby/Gems/2.6.0/gems/ffi-1.17.0-x86_64-darwin/lib/2.6/ffi_c.bundle (LoadError)
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /Library/Ruby/Gems/2.6.0/gems/ffi-1.17.0-x86_64-darwin/lib/ffi.rb:3:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /Library/Ruby/Gems/2.6.0/gems/ethon-0.16.0/lib/ethon.rb:3:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /Library/Ruby/Gems/2.6.0/gems/typhoeus-1.4.1/lib/typhoeus.rb:2:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/cdn_source.rb:440:in `download_typhoeus_impl_async'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/cdn_source.rb:372:in `download_and_save_with_retries_async'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/cdn_source.rb:365:in `download_file_async'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/cdn_source.rb:338:in `download_file'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/cdn_source.rb:53:in `refresh_metadata'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source.rb:31:in `initialize'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/cdn_source.rb:30:in `initialize'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:315:in `new'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:315:in `block in source_from_path'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:322:in `source_from_path'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:331:in `block in aggregate_with_repos'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:331:in `map'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:331:in `aggregate_with_repos'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:26:in `aggregate'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:60:in `all'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/user_interface/error_report.rb:173:in `repo_information'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/user_interface/error_report.rb:77:in `stack'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/user_interface/error_report.rb:24:in `report'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/command.rb:66:in `report_error'
	from /Library/Ruby/Gems/2.6.0/gems/claide-1.1.0/lib/claide/command.rb:396:in `handle_exception'
	from /Library/Ruby/Gems/2.6.0/gems/claide-1.1.0/lib/claide/command.rb:337:in `rescue in run'
	from /Library/Ruby/Gems/2.6.0/gems/claide-1.1.0/lib/claide/command.rb:324:in `run'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/command.rb:52:in `run'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/bin/pod:55:in `<top (required)>'
	from /usr/local/bin/pod:23:in `load'
	from /usr/local/bin/pod:23:in `<main>'
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require': cannot load such file -- ffi_c (LoadError)
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /Library/Ruby/Gems/2.6.0/gems/ffi-1.17.0-x86_64-darwin/lib/ffi.rb:5:in `rescue in <top (required)>'
	from /Library/Ruby/Gems/2.6.0/gems/ffi-1.17.0-x86_64-darwin/lib/ffi.rb:2:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /Library/Ruby/Gems/2.6.0/gems/ethon-0.16.0/lib/ethon.rb:3:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /Library/Ruby/Gems/2.6.0/gems/typhoeus-1.4.1/lib/typhoeus.rb:2:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/cdn_source.rb:440:in `download_typhoeus_impl_async'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/cdn_source.rb:372:in `download_and_save_with_retries_async'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/cdn_source.rb:365:in `download_file_async'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/cdn_source.rb:338:in `download_file'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/cdn_source.rb:53:in `refresh_metadata'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source.rb:31:in `initialize'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/cdn_source.rb:30:in `initialize'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:315:in `new'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:315:in `block in source_from_path'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:322:in `source_from_path'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:53:in `block in sources'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:53:in `map'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:53:in `sources'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/command/repo/add_cdn.rb:38:in `block in run'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/user_interface.rb:64:in `section'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/command/repo/add_cdn.rb:36:in `run'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/sources_manager.rb:45:in `create_source_with_url'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/sources_manager.rb:22:in `find_or_create_source_with_url'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/installer/analyzer.rb:179:in `block in sources'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/installer/analyzer.rb:178:in `map'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/installer/analyzer.rb:178:in `sources'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/installer/analyzer.rb:1081:in `block in resolve_dependencies'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/user_interface.rb:64:in `section'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/installer/analyzer.rb:1080:in `resolve_dependencies'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/installer/analyzer.rb:125:in `analyze'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/installer.rb:422:in `analyze'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/installer.rb:244:in `block in resolve_dependencies'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/user_interface.rb:64:in `section'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/installer.rb:243:in `resolve_dependencies'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/installer.rb:162:in `install!'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/command/install.rb:52:in `run'
	from /Library/Ruby/Gems/2.6.0/gems/claide-1.1.0/lib/claide/command.rb:334:in `run'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/command.rb:52:in `run'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/bin/pod:55:in `<top (required)>'
	from /usr/local/bin/pod:23:in `load'
	from /usr/local/bin/pod:23:in `<main>'
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require': dlopen(/Library/Ruby/Gems/2.6.0/gems/ffi-1.17.0-x86_64-darwin/lib/2.6/ffi_c.bundle, 0x0009): tried: '/Library/Ruby/Gems/2.6.0/gems/ffi-1.17.0-x86_64-darwin/lib/2.6/ffi_c.bundle' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/Library/Ruby/Gems/2.6.0/gems/ffi-1.17.0-x86_64-darwin/lib/2.6/ffi_c.bundle' (no such file), '/Library/Ruby/Gems/2.6.0/gems/ffi-1.17.0-x86_64-darwin/lib/2.6/ffi_c.bundle' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')) - /Library/Ruby/Gems/2.6.0/gems/ffi-1.17.0-x86_64-darwin/lib/2.6/ffi_c.bundle (LoadError)
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /Library/Ruby/Gems/2.6.0/gems/ffi-1.17.0-x86_64-darwin/lib/ffi.rb:3:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /Library/Ruby/Gems/2.6.0/gems/ethon-0.16.0/lib/ethon.rb:3:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /Library/Ruby/Gems/2.6.0/gems/typhoeus-1.4.1/lib/typhoeus.rb:2:in `<top (required)>'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/cdn_source.rb:440:in `download_typhoeus_impl_async'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/cdn_source.rb:372:in `download_and_save_with_retries_async'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/cdn_source.rb:365:in `download_file_async'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/cdn_source.rb:338:in `download_file'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/cdn_source.rb:53:in `refresh_metadata'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source.rb:31:in `initialize'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/cdn_source.rb:30:in `initialize'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:315:in `new'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:315:in `block in source_from_path'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:322:in `source_from_path'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:53:in `block in sources'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:53:in `map'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-core-1.15.2/lib/cocoapods-core/source/manager.rb:53:in `sources'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/command/repo/add_cdn.rb:38:in `block in run'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/user_interface.rb:64:in `section'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/command/repo/add_cdn.rb:36:in `run'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/sources_manager.rb:45:in `create_source_with_url'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/sources_manager.rb:22:in `find_or_create_source_with_url'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/installer/analyzer.rb:179:in `block in sources'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/installer/analyzer.rb:178:in `map'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/installer/analyzer.rb:178:in `sources'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/installer/analyzer.rb:1081:in `block in resolve_dependencies'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/user_interface.rb:64:in `section'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/installer/analyzer.rb:1080:in `resolve_dependencies'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/installer/analyzer.rb:125:in `analyze'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/installer.rb:422:in `analyze'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/installer.rb:244:in `block in resolve_dependencies'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/user_interface.rb:64:in `section'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/installer.rb:243:in `resolve_dependencies'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/installer.rb:162:in `install!'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/command/install.rb:52:in `run'
	from /Library/Ruby/Gems/2.6.0/gems/claide-1.1.0/lib/claide/command.rb:334:in `run'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/lib/cocoapods/command.rb:52:in `run'
	from /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.15.2/bin/pod:55:in `<top (required)>'
	from /usr/local/bin/pod:23:in `load'
	from /usr/local/bin/pod:23:in `<main>'

Looks like I was able to fix this by using non-system versions of pod (and ruby)

Installing rbenv via homebrew
Using rbenv to build and install the current stable ruby version
Alter bash_profile to init rbenv on startup
Install cocoapads via homebrew
Use the homebrew version of pod to install the xcodeproject dependencies

This should be called out in the installation steps, if the system version of pod is always going to fail

Hi @monkeyswarm,
Thank you for the confirmation. Could you please let me know if you still require support on this issue, or if we can close it as resolved?


Home navigation bar: remove "Libraries", and add "Contribute"

Actual Behaviour

The navigation bar on the home menu right now is:
"Download" - "Start" - "Reference" - "Libraries" - "Learn" - "Community"
Expected Behaviour
With the p5.js global track from the Contributors Conferenfce 2019, we  propose we change the navigation bar, deleting "Libraries", and adding "Contribute", maybe remixing the order to:
"Download" - "Start" - "Learn" - "Reference" - "Community" - "Contribute"
Would you like to work on the issue?
Yes!
We think that the "Contribute section" in the https://p5js.org/community/ section of the website is great, but we want to expand it and feature it as a whole section on the website, where we can help foster a p5.js global community.
We will add a new issue to this repository to explain the details of it.

Maybe "Contribute" is not the right phrasing, maybe it implies money,
maybe a better option is "Get involved" :)

thanks @montoyamoraga! we're actually revamping the homepage completely to include all page links similar to the other pages.  more here

closed with https://github.com/processing/p5.js-website/commit/86b0cc04124b8ccad500bbd047157a540df3c78e


[Android]组件scroller因为某些原因我要再外层套两层div，然后scroller就滑不了了

There is nothing we can do without a demo.
Try Weex 0.28.
If this still bothers you and you find a solution, you could give us a PR if you can, I am very happy to talk with you implemenation detail or review you PR in mailing list. Currently, I am a little busy, I can't focus on this issue.
I have a busy schedule and I can't read Github issue every day, but I check mailing list every day. I am sorry if this bothers you.


Nginx reverse proxy no such file or directory

I'm fairly certain this is a configuration issue on my end, but here goes: I'm suddenly getting errors from nginx when I visit my Droppy (mydomain.com/droppy/). The page loads, but the formatting looks off, with icons and text all overlayed on each other.
It seems nginx is looking in /var/www/droppy/ for css and js files, but that location doesn't exist. Prior to this, Droppy was running fine for months. I've been over my nginx.conf and droppy.conf, and nothing is amiss. My Droppy config is identical to the one you provide, except that I access Droppy from a subfolder.  Out of curiosity, where are those files actually served from?
I've tried updating Droppy, and then I tried re-installing it, but I'm still seeing the same errors. Here's one as an example:
request: "GET /droppy/!/res/client.js HTTP/1.1", host: "mydomain.com" 2017/08/22 17:36:57 [error] 12547#0: *170 open() "/var/www/droppy/!/res/style.css" failed (2: No such file or directory)

So you solved it?
Client files are served on the /!/res/ path, which is populated by static entries from these lines:
https://github.com/silverwind/droppy/blob/master/server/resources.js#L108-L170

I thought I had solved it. I think many node modules have become uninstalled, possibly when I reinstalled node to correct another issue last week. When I reinstalled droppy, these were not installed. I just installed handlebars manually. Is there a command I can execute that will install all dependencies?

Try
npm cache clean --force
npm uninstall -g droppy
npm install -g --production droppy

Alternatively, you can try to go to the installation directory and run a manual dependency installation there:
cd $(dirname $(realpath $(which droppy)))
npm install --production

Finally, you could also try running of the git version, but in that case, you need development dependencies to build dist/cache.json (achieved by omitting --production):
git clone https://github.com/silverwind/droppy
cd droppy
npm install
./droppy build
./droppy.js start -c ... -f ...

I tried the first set of commands you gave, and it seemed to install everything. However, I'm running into the same issue. I'm still not sure what is causing this, but I noticed that I can access Droppy fine from the local network IP, which circumvents nginx entirely. When I access via my domain, I just get a blank gray/black page, and errors in nginx's error.log about .css and .js files.
I haven't touch my nginx config in months, I can't imagine what would be different all of a sudden.  I really don't think this is a problem with Droppy per se, as I'm seeing the same thing from the web app Calibre-web. I noticed none of the PHP-based web apps I am running have this problem, though. Shrugs I think I'll declare it a lost cause for now.

Can you post the relevant sections of your location block? I'm pretty certain something must be wrong there. A common fault is when you forget the trailing slash in proxy_pass or the location declaration itself. Make sure both have trailing slashes.

location /droppy/ {
proxy_pass http://droppy-upstream/;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Real-Port $remote_port;
proxy_http_version 1.1;
proxy_cache off;
proxy_buffering off;
proxy_redirect off;
proxy_request_buffering off;
  proxy_buffer_size 64k;
  proxy_buffers 8 32k;
  proxy_ignore_client_abort on;
  proxy_connect_timeout 7200;
  proxy_read_timeout 7200;
  proxy_send_timeout 7200;

add_header Strict-Transport-Security "max-age=15552000; includeSubDomains";
add_header X-Content-Type-Options nosniff;
add_header X-Frame-Options "SAMEORIGIN";
add_header X-XSS-Protection "1; mode=block";
add_header X-Robots-Tag none;
add_header X-Download-Options noopen;
add_header X-Permitted-Cross-Domain-Policies none;
add_header Access-Control-Allow-Origin *;
    }

Droppy-upstream is specified in nginx.conf as localhost:8989

Looks alright. What URL does the browser show on the broken page /droppy or /droppy/? Do observe any redirects with curl -i <url>?

Browser shows URL with the trailing slash. Curl - i doesn't show any redirects. Also, I expected to see some errors in the Chrome developer console, but there are none.

Do you have a root statement somewhere outside the location block? If so, try removing it.

I removed the root statement and reloaded the nginx configuration, but Droppy still isn't loading properly, and I'm still seeing the same errors in the nginx error log. I will probably reinstall nginx this weekend to see if that helps (I want to compile it with Pagespeed support, anyway). Hopefully, that will help.

Okay. I'm pretty certain that something outside the location block must be interferring. I'd suggest you remove or comment out everything except droppy's location and then try again. Once it's working, add stuff back in.

Thank you for your help, you were correct. I had suspected the issue was related to enabling browser caching, I just didn't think I would find it in the config for another virtual host. I guess enabling browser caching for Droppy is no good. Here's the problem:
location ~*  \.(jpg|jpeg|png|gif|ico|css|js|pdf)$ {
expires 7d;
}

Of course the issue is that I'm specifying all locations, when it should be restricted to just one. I've disabled it for now, it's nice to have things back to normal. Thanks again.

Spoke too soon. Getting authentication errors for all of my users, and I know the passwords are good. May be a permission issue on my system, I'll investigate further. I do get the login page now though, I wasn't getting that before.

Setting cache headers alone shouldn't lead to issues like you described. Your issue had to do with request routing, so I suspect it was a rewrite, alias or root statement that interferred.
Nginx location blocks are kind of tricky and do unexpected things sometimes. I generally recommend to use a server and dedicated subdomain for each service you run.

The issue was that I had a location that matched all locations in one of the configs in /.. /sites-enabled/, and that statement caches js, css, and various other statics files.
I need to redo my nginx, it does have some issues (complains about server blocks anywhere other than nginx.conf). If it was properly configured this would  not have been an issue.
Thank you for your help despite this not being an issue with Droppy. I appreciate the time you took to help.


problems in function inverse_kinematics_np

In the 58th line of common/skeleton.py, the order of  "l_hip, r_hip, sdr_r, sdr_l = face_joint_idx" is different from the comment "right hip, left hip, right shoulder, left shoulder", whether this will influence the processed data?
Meanwhile, in the 74th line of the common/skeleton.py, "root_quat = qbetween_np(forward, target)" is the rotation from forward to the [0,0,1], whether it should be the rotation from [0,0,1] to the forward?

Hi, thanks for pointing out this. The first one seems a bug exactly. I guess it’s not major problem, but it may still cause few discontinuities for root angle. However since many experiments have been done on this version, I could not update this anymore. I will highlight this issue to note others. For the second one, as long as you keep the same rule when you extract features and recovering motions, it should be fine.


[Snyk] Security upgrade web-ext from 4.3.0 to 8.3.0

Snyk has created this PR to fix 6 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):

packages/react-devtools-extensions/package.json

Note for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Arbitrary Code Execution SNYK-JS-THENIFY-571690
  208

Regular Expression Denial of Service (ReDoS) SNYK-JS-SEMVER-3247795
  159

Missing Release of Resource after Effective Lifetime SNYK-JS-INFLIGHT-6095116
  141

Regular Expression Denial of Service (ReDoS) SNYK-JS-HTTPCACHESEMANTICS-3248783
  63

Prototype Pollution SNYK-JS-MINIMIST-2429795
  59

Regular Expression Denial of Service (ReDoS) SNYK-JS-MINIMATCH-3050818
  45

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.


MTL-1695 Edge work

Summary and Scope

Relates to: MTL-1695

Issue Type

Bugfix Pull Request

This CSI just deprecates a function that was yanked out of the CSM 1.3 docs.
See: https://github.com/Cray-HPE/cray-site-init/pull/255
Prerequisites

[ ] I have included documentation in my PR (or it is not required)
[ ] I tested this on internal system (if yes, please include results or a description of the test)
[ ] I tested this on a vshasta system (if yes, please include results or a description of the test)

Risks and Mitigations

Note that this would also revert the revert PR: #622 .


Add param skipSigChk to skip signature check in committer

Description
Skip VerifySignature in committer
Rationale
apiserver already done the verify job, verify in committer could be removed.
Example
Changes
interface TxExecutor and its implementations.

Already confirmed the approach with Ryan, no need to repeat the signature verification process.


Added toBeString

What
feature - Added toBeString matcher

Why
#36

Notes
Housekeeping

[X] Unit tests
[X] Documentation is up to date
[X] No additional lint warnings
[X] Add yourself to contributors list (yarn contributor)

Codecov Report

Merging #48 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #48   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           6      8    +2
  Lines          33     42    +9
  Branches        5      6    +1
=====================================
+ Hits           33     42    +9

Impacted Files
Coverage Δ

src/matchers/toBeString/index.js
100% <100%> (ø)

src/matchers/toBeString/predicate.js
100% <100%> (ø)

Continue to review full report at Codecov.

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

@stofolus all looks good just the failing error message needs tweaking :smile:

I'm closing this because this has already been added


For python2and3

The googlesearch package is now available in both Python2 and Python3 , I imported urllib.request package for python3 and urlib2 put it as it is for python2 . And in line number 47 and 49 __next__()  and next() method for python3 and python2 respectively from bs4 lib , so i made it compatible for both the version of python . And it executed tox successfully with zero errors.
if int(sys.version.split('.')[0]) > 2:
    import urllib.request as ur          #  for Python3
else :
    import urllib2 as ur                    # for Python2

import lib2to3

In googlesearch.py
line number 47 :
totalText = soup.select(GoogleSearch.TOTAL_SELECTOR)[0].children.__next__()
Here __next__() is in python3 version of bs4
Where in line number 49 :
totalText = soup.select(GoogleSearch.TOTAL_SELECTOR)[0].children.next()
Here next() is in python2 bs4
In tests/test_googlesearch.py
Line number  18 : I commented it.
self.assertTrue(len(response.results)== 15, "number of results is " + str(len(response.results)) + " instead of " +str(num_results))
Basically It fails , why because , You will query something and got response But According to test case only valid when you got 15 or more results came , Some of the fetched may also less than 15. Hence I commented it.
Finally i checked with tox command. It replies me as
py27: commands succeeded
  congratulations :)

@anthonyhseb

Hello @rakeshsagalagatte, thank you for the contribution, I tried to pull you commit locally for testing, however I couldn't get to work well enough.
The goal would be to have Python 3 added in Tox, and that both tests pass. I was trying to achieve this but couldn't with the little time I had available. Would you be interested in attempting to fix this.
There is another problem in the library, in that the CSS queries may be outdated, I'll try to work on that whenever I can.

Can I you share the error here please.


swift-inspect: update instructions for Windows

Remove the reference to DEVELOPER_DIR and update the instructions to
actually be usable with a released snapshot (and official releases).
The development setup should mimic the actual layout further and is a
separate issue.  This requires a new snapshot with
apple/swift-installer-scripts#128 included.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please smoke test


Support assembly_info step

Format:
assembly_info:
  patch: true
  file: AssemblyInfo.*
  assembly_version: "2.2.{build}"
  assembly_file_version: "{version}"
  assembly_informational_version: "{version}"

Should support patching of both AssemblyInfo.cs and AssemblyInfo.vb files.

Done.


In bundle declaration emit, refuse to rewrite nonrelative references …

…to files outside the common source directory
Fixes #39547
Taken with a reintroduction of the flag added in this PR (pending bikeshedding of the flag name), this should allow the user in #39547 to not just have less-broken bundled-up declarations (as this PR allows), but entirely functional ones which should be directly consumable by typescript itself.

@weswigham is this ready to merge?

@weswigham is this ready to merge?

Yeah, lemme merge it~

Yeah, lemme merge it~


Unable to build Java functions

The build-step-export step fails with:
2018/10/24 19:30:12 Error: failed to parse arguments map[narg:0x4d91d0 runImage: launchDir:/workspace]

Looks like https://github.com/buildpack/lifecycle/pull/30 will fix this once the images are published

The above fixed solved the problem.


Remove version: Jackett.Jackett version 0.21.235

404 - release deleted
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/Jackett/Jackett/releases/download/v0.21.235/Jackett.Installer.Windows.exe
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 918)


gyp: libsass.gyp not found when building from git

In package.json
  "devDependencies": {
    "css-loader": "*",
    "file-loader": "*",
    "jsx-loader": "*",
    "node-sass": "git://github.com:sass/node-sass.git#HEAD",
    "react-hot-loader": "^1.2.3",
    "sass": "*",
    "sass-loader": "*",
    "style-loader": "*",
    "url-loader": "*",
    "webpack": "*",
    "webpack-dev-server": "*"
  },

><EMAIL_ADDRESS>postinstall /node_modules/node-sass
> node scripts/build.js

` /node_modules/node-sass/vendor/darwin-x64-14/binding.node ` exists.
 testing binary.
Problem with the binary.
Manual build incoming.

Sorry, it seems that you have blocked @haf from the repository. You'll have to unblock him if you want answers to this.
In general, we're very sad to see the way that you handle your users.

                                                                                Sorry that was unintentional from me. I just didn't want to be getting more emails as he appeared to be opening multiple issues for release requests.                                                                                Sent from my BlackBerry 10 smartphone.                                                                                From: enjoymSent: Monday, March 23, 2015 8:52 AMTo: sass/node-sassReply To: sass/node-sassSubject: Re: [node-sass] gyp: libsass.gyp not found when building from git (#788)Sorry, it seems that you have blocked @haf from the repository. You'll have to unblock him if you want answers to this.

In general, we're very sad to see the way that you handle your users.
—Reply to this email directly or view it on GitHub.


bug: Cannot type in response variations in Send a Response.

Describe the bug

I'm running from command line, I don't see any obvious error messages in the trace.
Version
Version:  1.4.0-nightly.237101.f01cb52
Electron: 8.2.4
Chrome: 80.0.3987.165
NodeJS: 12.13.0
V8: 8.0.426.27-electron.0
Browser

[X] Electron distribution
[ ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[ ] macOS
[X] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Go to any trigger.
Click on + to add a new shape.
Scroll down to 'Send a response'
Click in 'Response Variations'
Begin typing
See error below.

Screenshots

I can't repro this, would you please:

Attach a video?
Add steps you follow to run from command line?

Do other features of the app work? It seems like the local server is down.

@hatpick :
If I create a new bot it works.  If I open an older bot (i'm using something from Tai called LargeOrchBot) it fails.
Feel free to close, this may be some interim build problem.


Ability to chunk download from object store

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
When downloading large objects (> 300MBs) using object_store crate, I often hit timeout using the default configuration (30 seconds connection timeout). Interestingly, when increasing the timeout, the download speed is actual lower (not sure if it's the same for everyone?).

Describe the solution you'd like
I am thinking if it makes sense to chunk a file into smaller ranges (say, 100MB each), and in parallel, download each range with different connection and reconcile them under the same interface.

Describe alternatives you've considered
Not sure if such a capability can be composed using the existing interfaces.

Additional context

I originally submitted this issue in the datafusion repo which I think is the wrong repo. Quote reply from @alamb

Thank you @trungda
I think it would be very interesting to build a "parallel downloader" ObjectStore implementation, though I am not sure it necessairly belongs in the core object_store crate (though it could be added if there is enough interest)
There might also be some interesting ideas to explore around "racing reads" to avoid latency
There are many good ideas in this paper, BTW: https://dl.acm.org/doi/10.14778/3611479.3611486
I think you could compose this kind of smart client from the existing interfaces

It should be relatively straightforward to achieve this using buffer_ordered from the futures crate, we may just need to document how to do this

Maybe it would make a good example

I can write an example. Using buffered is what we are doing to download multiple files concurrently. Something like this:
let parallelism = 10;
let mut downloaders = Vec::new();
for path in paths.iter() {
  downloaders.push(download(path)); <----This downloads the whole file.
}
let mut buffered = stream.buffered(parallelism);
while let Some(_) = buffered.next().await {}

But it's not obvious for me how to use the stream interface with bufferred, i.e., how can we reconcile different streams (from different parts of the file)  into one stream, but is it something really needed?

how can we reconcile different streams (from different parts of the file) into one stream

I was imagining that it would look something like making multiple calls to ObjectStore::get_ranges for each file


Error occured while proccesing the data

Can't start syncing my feeds from my Miniflux instance on my arm64 SBC at home, an error occures: "Error occured while proccesing the data"
API URL: http://<IP_ADDRESS>:7001/v1/
API Key: NhQtw9WgfUCIE3RP5yzTWoEvOZhrt1UwPeI0gm2Tq38=
Miniflux version: 2.0.51
Miniflux API
API Endpoint = http://<IP_ADDRESS>/v1/ (didn't work with localhost too)
Username = admin
Password = Your account password
Logs:
3012202315.log
FluxNews version: 1.3.3
I am using Docker-compose stack of miniflux/miniflux:latest [sha256:583afb597db848] and postgres:15 [sha256:1aa6a6a531189f2] in the backend. Works fine in the browser.

Hi, it looks like the feed icon is too big to be stored (or retrieved) in the database.
In the other issue I am currently optimizing the processing of large amounts of data, one part of this is to change the processing of the feed icons.
This change will also solve your problem.
As soon as I have created a new release, I will let you know here.

The new relase has just been released, the storage of the feed icons has been revised there and the problem should be fixed.

Just got 1.3.4 from F-Droid, works fine now.


Pagination

NHS design system guidance
NHS design system discussion
Related
GOV.UK Design System guidance
GOV.UK Design System discussion
Examples on the NHS App

Examples

Journeys used on

Book a vaccination
GP health record
Appointments

Overview
Pagination is used to display test results in Your GP health record but pagination is used irrelevant of how many results are returned. It doesn't use a contents list to group pages (as per design system guidance), instead it uses a double pagination pattern which could be confusing for users. Pages are generated when there are no results and there is no indication that a page is empty until a user arrives there.
Objective
Addressing this issue requires determining user needs around viewing and navigating test results. Fixing it would ensure we are adhering to the design system and reducing friction in the user experience.
Activities

[ ] Explore possible solutions including correct use of pagination
[ ] Test with users
[ ] Update test results designs


Carousel on page load

Thanks for your work! I have an issue where if the carousel is on autoplay, it takes a second or two to load on the page. Is there a way to check if carousel is loaded so i can do something like if carousel is loaded, just display, else display the first image or some sort of loading indicator. I am not sure if I missed something but i believe I went through all of the props and options.

Thanks for your suggestion, I fixed that issue. A slight issue I have now is I have a sticky header that displays behind the carousel when scrolling. I was thinking it might be a z-index issue, do you have any suggestions so that the header will display over the carousel. Thanks again

There should be some parent element with position: relative, and you can put sticky header as a child element there with position: absolute and top:0,left:0, right:0. Smth like that.

i got it, thanks

Cool, thanks!


Add platform toggle to code examples

Add dynamic platform toggle to code examples.

@infotexture This doesn’t have a preview Netlify dist for some reason.
The basic functionality is there, but we probably want to clean the styling.
The other thing is that the toggle generation gets triggered if pre has filepath. But for eg Brew instructions we don’t want both as it’s macOS only. So we may need to add platform or outputclass to mark some codeblocks as single platform examples.

This doesn’t have a preview Netlify dist for some reason.

Could that be because the branch is currently based on feature/357 instead of master? 🤔
Once #385 is merged, rebasing this on master might be enough to trigger the deploy preview.
We have so many code samples that are not platform-specific (and so few that are), but from what I see here I'm not yet sure when this code is applied, and whether that logic is likely to result in any "false positives" where we wouldn't want this code to run.
If platform or output classes are required in the DITA source, given the ratio of universal to platform-specific examples, I'd prefer to only mark those for which this treatment would be useful (as opposed to vice-versa).

@infotexture See https://deploy-preview-386--dita-ot.netlify.app/dev/topics/first-build-using-dita-command.html for example of use. The only place this is currently triggered is codeblock with a nested filepath.

On mobile at the moment, I don’t see either of the code blocks, only the tab links.

Yeah, it seems to not work on mobile Safari :(

🤔
Weird. For a while I saw the same as in the screen capture, but then it disappeared and now it works... ? So a reload fixed it for me. @infotexture Could you try again?

@infotexture What sort of triggers we should use for this. Few things come to mind:

For <codeblock outputclass="multi-platform"> where JavaScript will turn all / into \ in <filepath> and possibly ${foo} into %foo%.
For <choicetable outputclass="multi-platform"> that has @platform in the <chrow> children, show the table as tabs.

I'd be fine with using something like outputclass="multi-platform" to trigger this.
That said, I'm still seeing the same behavior on desktop browsers (Safari 13.1, Firefox 77.0b9, and Chrome 81.0.4044.129):
The unmodified codeblocks load briefly on initial page load, then disappear, and are replaced with the tabs.  When the page is reloaded, both codeblocks and tabs appear.
See example from Firefox below:

Also still reproducible in private browsing window on Safari mobile: codeblocks missing on initial pageload, appear on reload.

The delay in initial load to convert the codeblock into platform toggle should happen only when the SPA is loaded for the first time. On following page navigations the platform toggle should be there (near) immediately. The reload issue needs to be debugged.

Ok, now the source requires multi-platform @outputclass in order to render the platform selector. Tested with Chrome and Firefox on MacOS, and Safari and Firefox on iOS. This preview no longer has any content that triggers the platform selector. When this is merged, we can see where we might want to enable the platform selector.


Polymer 3 import

When I am importin using
import flatpickr from 'flatpickr';
It is giving error
Uncaught SyntaxError: The requested module '../../flatpickr/dist/flatpickr.js' does not provide an export named 'default'
I tried all different types of import
Polymer 3
flatpicke4.5.2
Google Chrome
Windows

@sandeepbaikan this is an issue with polymer. flatpickr is distributed to millions of npm users without problems, and I use it myself in ES2015 module environments without problems.
Unless you know of some solution I can apply to help you out, there isn't much I can do :(


Processors for vector and raster derivatives

This adds initial processors for vector and raster derivatives. The vector derivatives are very basic and not all that pleasing. There is now an issue for that #120. The range of processors should also be expanded. See issue #121. This PR closes #39.

@drh-stanford, @jrgriffiniii @escowles  When you have some time, please take a look.

This looks good to me -- just a few comments.

Fixed up issues. Depends on #124.

This looks great — can you rebase now that #124 is merged?

Rebased.


ANT task should allow arguments to modify the task execution #22

Hybris ANT task should allow arguments to modify the task execution, defaults for startupProbe #22
The assemble script has been updated to allow parameters in the ANT tasks excuted

LGTM

/lgtm


Remove second parameter from get()

This parameter is used only with the very first call of the get method. You can pass different parameters for a single dependency as many times as you want, but they would be used just once because all the dependencies in the container are singletons. Ability to use this argument disorientates and leads to errors.

https://github.com/yiisoft/di/pull/105/files#diff-00897e77b93946555bcac5b95e73e3a9R22

Done in https://github.com/yiisoft/di/commit/736926c8d498b77d8a148c49b19c8e8f8d59f9aa


Problem integration with iOS client

Hello
can you detail the configuration for Web client credentials and iOS credential
we are working on a mobile cloud app, and we are facing issue with the connection between iOS clients and Endpoints
it makes 3 weeks, that we are trying many things, but no result (Android is fine, iOS still have authentification issue)
this will help a lot,
thank you.
"Modify kMyClientId and kMyClientSecret in ViewController.m to include the web client ID and client secret you registered...."
This is what I have when I use the WEB_CLIENT_ID and WEB_SECRET_ID

When we use the IOS_CLIENT_ID with the WEB_CLIENT_SECRET
I can see the OAUTH CONSENT screen

and when I click "Allow" I have this screen which disappear quickly

I checked stackoverflow, many threads, but no solution....
can you please put screen shot about your backend config and iOS client config
thank you.


Use the exact CC-0 license text

The license for this repository isn't being detected because the license file contain additional text, not part of the license. Specifically, it contains a disclaimer between CC and us, the downstream user, disclaiming liability for our use of the license. That text isn't part of the license itself, doesn't need to be included in the license file, and shouldn't be included in the license file if we want GitHub to detect the license.
This PR removes that extra text by using the exact text from choosealicense.com, which GitHub should then detect.

@mlinksva any objections? 😄

No objection.
Ideally we could detect with or without the license creator (CC) disclaimer, usefully marked as optional by https://spdx.org/licenses/CC0-1.0.html ... but until then (possibly forever), standardizing on the text we've been propagating to others is fine.


Reboot Buttons not functioning

When I "Press" the "Reboot" buttons for a node it returns the following error: "Failed to call service button/press. connection lost". When I look in the Home Assistant logs it says:
This error originated from a custom integration.

Logger: homeassistant.helpers.script.websocket_api_script
Source: custom_components/eero/button.py:92
Integration: eero (documentation, issues)
First occurred: 2:05:16 PM (1 occurrences)
Last logged: 2:05:16 PM

websocket_api script: Error executing script. Unexpected error for call_service at pos 1: 'EeroButtonEntity' object has no attribute 'key'
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 468, in _async_step
    await getattr(self, handler)()
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 703, in _async_call_service_step
    response_data = await self._async_run_long_action(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 665, in _async_run_long_action
    return long_task.result()
           ^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 1957, in a
```sync_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 1997, in _execute_service
    return await cast(
           ^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 235, in handle_service
    return await service.entity_service_call(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 845, in entity_service_call
    response_data = task.result()  # pop exception if have
                    ^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1192, in async_request_call
    return await coro
           ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 889, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/button/__init__.py", line 124, in _async_press_action
    await self.async_press()
  File "/config/custom_components/eero/button.py", line 96, in async_press
    await super().async_press()
  File "/usr/src/homeassistant/homeassistant/components/button/__init__.py", line 139, in async_press
    await self.hass.async_add_executor_job(self.press)
  File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/eero/button.py", line 92, in press
    getattr(self.resource, self.key)()
                           ^^^^^^^^
AttributeError: 'EeroButtonEntity' object has no attribute 'key'

This is fixed in 1.4.2, please update and confirm.

Seems to work. Thanks so much, @schmittx!


(null) return value

Hey, I get a (null) return when trying to use this
$ ips2crash WiFiLQMMetrics-2022-11-21-074919.ips
(null)
$

If you can send me the .ips file (dev.packages at gmail dot com), I can check the origin of the issue.


Saeed/ma 1442

https://openedx.atlassian.net/browse/MA-1442

Thanks for the pull request, @saeedbashir! I've created OSPR-950 to keep track of it in JIRA. JIRA is a place for product owners to prioritize feature reviews by the engineering development teams.
Feel free to add as much of the following information to the ticket:

supporting documentation
edx-code email threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will still be done via the GitHub pull request interface. As a reminder, our process documentation is here.
We can't start reviewing your pull request until you've   submitted a signed contributor agreement   or indicated your institutional affiliation   and   added yourself to the AUTHORS file . Please see the CONTRIBUTING file for more information.

@aleffert We need to keep track of either post has any results in it or not. For example post has results but after applying filter post has zero results but we still want to show header view to user to change filters. That's why I'm using instance variable.

Makes sense. :+1:

Merged this myself so it can get into the release candidate build. Cherry-picked in the relevant commit to master and rc/2.0.0

@aleffert changes of this pull request are missing in rc/2.0.0 and in master. Should I merge these changes manually?

@saeedbashir Ah. I see what happened. As best I can tell it was on the rc, but I had forgotten to push to master. Should be resolved. Thanks for bringing this to my attention.


Documentation on parameters and their default values

We are finding your module very useful!  it would be very good to have more information about the parameters, which ones are required, what the defaults are, etc.
thanks,
Connie Woodward, data manager, Suwannee River Water Management (Florida, USA)

The resolution of #2 should cover this.


TestPlugin: Avoid generating warnings in client codes from old style …

…casts
When -Wold-style-cast is enabled

We avoid new casts due to old compilers. However, the failure from the old Watcom compiler is interesting. Did you look at that?

 I appologize about the early pull request. I will look into it during the day.
However, I think I was not clear enough in the short description. Sorry about that. So my problem is, if I turn on the -Wold-style-cast warning flag in my project, then I get warnings about old style casts generated by the UT_PTR_SET macro.
If I understand you correctly, the acceptable solution for C++ is a function template instead of a new reinterpret_cast. Is that the correct way?

Uhm, no worry about early pull requests. It is good as it allows for discussion.
Templates are not good either. Because CppUTest is used in some embedded products, we try to keep the level of C++ used to be 'old' so that we support these compilers. So, in CppUTest itself, I don't think we use the 'new' C++ style casts. I would be tempted to merge it (I understand your problem) but it seems the travis build failed because of it. I don't understand very well why, but you might wanna check that first.

Coverage remained the same at 99.876% when pulling b34b92333fd3fdcda84c1dd0fed39af8b9dc7215 on bukulin:master into<PHONE_NUMBER>153fc11cf772b0d22b96f48762b5f6 on cpputest:master.

It failed linking.  There doesn't seem to be any problem with any code.
I suspect one binary perhaps grew too large.  The tests are distributed over several binaries, and it is possible for one of them to break the +/- 640k limit.

Sorry.  Looking at it a second time, I see a problem with the code :-(

.../CheatSheetTest.cpp(15): Error! E784: col(34) reinterpret_cast expression must be pointer or integral object
.../CheatSheetTest.cpp(15): Note! N630: col(34) source conversion type is 'void (* * )( void )'
.../CheatSheetTest.cpp(15): Note! N631: col(34) target conversion type is 'void * *'
Error: Compiler returned a bad status compiling '/home/travis/build/cpputest/cpputest/tests/CppUTest/CheatSheetTest.cpp'

I had an assumption about a vexing parse, but not that is the situation. I think, maybe the Watcom compiler handles pointers to functions and pointers to variables slightly differently.
Unfortunately I do not have any experience with the Watcom compiler, but I try to figure it out.

I wish I could help you there.  But even though it was me who added the Watcom stuff (to be able to test some form of 16 bit code), much of my work with Watcom was by trial and error.

An old architecture, but the compiler has been kept up-to-date ;-)

Oh, has it. We'll then need to add a really old compiler to the build too.

Perhaps we need to redefine "old" ?

Sometimes companies are required to be able to build firmware from, say, 20 years ago.  They have kept the old code.  They even have a copy of the old build tools archived somewhere.  But sadly, they have no more machine to run it on... And this is really happening! :-)

I know what you mean, have a VM at work to run one of our old compilers on since the installer can't even start on most of our computers anymore.  We're still using that compiler on active projects too unfortunately, don't know when it will truly become retired.
Even if someone resurrects an old project with an older compiler, wouldn't they be trying to use the version of CppUTest that was around back then?  In my opinion, the unit test framework is effectively one of the build tools.  I understand maintaining compatibility, but seems like that eventually becomes too much of a burden and the supported environment should be updated to be one that can support newer functionality.
Specific to this issue, I do like the new-style casts myself, the different ones makes it a bit easier to avoid accidental effects by ensuring that you can only perform certain types of casting within each one.

Actually, I don't see any other solution for the problem then a big, fat chunk of #ifdef-s, but I do not like that at all. Do you have any other idea?

@bukulin An #if might work, especially for public interfaces.
However, it would be good to first figure out the Watcom thing. If it is due to no support for reinterpretted_cast then I guess it would be a good way to check. But I'm not quite sure why the Watcom compiler is failing.


[Client] Hardware integration: Install touch screen

Install eleduino touch screen ... when available.
Also, this will probably be a good moment to create an independent BSP layer.

Let start by creating the BSP layer.

Done in commit d5fa45a.

Touch screen installed and ready: commit d3948af.
Let test it a bit more to see if everything is OK.

No problem so far, although sometimes the screen does not detect our touches right after switching on the RPi and we have to disconnect and connect again the screen to the USB port. Or is it OS faults? One way or the other, I would rather carry on with this Beta and come back to this once we have slimmed down our Yocto image (issue #3) ... and if the problem persists.


[bug]: Inpainting, unable to paint on touch devices

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Windows
GPU
cuda
VRAM
24GB
What happened?
When using the inpainting feature of the web UI, I am unable to draw the mask on a touch screen. It does register a finger tap and draw a circle the size of the brush. But dragging a finger does not result in a paint stroke.
Screenshots

Additional context
I understand that mobile support is sort of on the back burner at the moment, but right now the web UI is pretty usable on tablets/chromebooks with touch screens. I tested this on the latest stable releases of Firefox and Chrome with identical results.
Contact Details
marcus.llewellyn#2923

Shouldn't be a difficult addition, just need to think about edge cases a bit. I have an iPad to test it on so that makes it easier too.

Submitted this PR
If there's any specific edge cases to test, please let me know.

Submitted this PR If there's any specific edge cases to test, please let me know.

Link is not working anymore, and i don't have an installed dev version. Not sure how its implemented right now. Is it simple dragging? Double-tap then drag or tap and hold then drag might be good option. Or maybe a button to stop drawing. Up to you, ofc, just a reminder that on mobile devices (if thats eventually planned) you also need to scroll the page, and maybe drawing on a simple drag, will make scrolling troublesome. Especially if image is a vertical rectangle, and fills the whole screen:)
Btw right now its possible to use on mobile devices with small code adjustments, and unpinned side panels. A little bit tricky, but somehow works.


Barbarian rage not applying on path of Wild Magic.

Not sure if this is related to the recent dnd5e system update, but it seems that the rage effect is no longer working. Error message from console below. If I right click and hit "toggle status effect" it throws up an error stating I need to reload foundry. Happy to get more details if needed! When I  tried applying the effect to a fighter, it threw an error about it not being a barbarian, but did work. If I delete the subclass from the actor, it also applies again, so I suspect it's either how the new system is handling subclasses, or it's that subclass in particular. Character imported with DDB-Importer
Uncaught (in promise) TypeError: barbarianClass.data.data.subclass.toLowerCase is not a function
[Detected 2 packages: dfreds-convenient-effects, socketlib]
    _addResistancesIfTotemWarrior https://<IP_ADDRESS>:30000/modules/dfreds-convenient-effects/scripts/effects/dynamic-effects-adder.js:140
    _addRageEffects https://<IP_ADDRESS>:30000/modules/dfreds-convenient-effects/scripts/effects/dynamic-effects-adder.js:118
    addDynamicEffects https://<IP_ADDRESS>:30000/modules/dfreds-convenient-effects/scripts/effects/dynamic-effects-adder.js:22
    addEffect https://<IP_ADDRESS>:30000/modules/dfreds-convenient-effects/scripts/effects/effect-handler.js:101
    toggleEffect https://<IP_ADDRESS>:30000/modules/dfreds-convenient-effects/scripts/effects/effect-handler.js:30
    _executeLocal https://<IP_ADDRESS>:30000/modules/socketlib/src/socketlib.js:192
    executeAsGM https://<IP_ADDRESS>:30000/modules/socketlib/src/socketlib.js:90
    toggleEffect https://<IP_ADDRESS>:30000/modules/dfreds-convenient-effects/scripts/effect-interface.js:114
    onEffectClick https://<IP_ADDRESS>:30000/modules/dfreds-convenient-effects/scripts/app/convenient-effects-controller.js:246
    jQuery 8
    _initClickListeners https://<IP_ADDRESS>:30000/modules/dfreds-convenient-effects/scripts/app/convenient-effects-app.js:107
    activateListeners https://<IP_ADDRESS>:30000/modules/dfreds-convenient-effects/scripts/app/convenient-effects-app.js:42
    _render https://<IP_ADDRESS>:30000/scripts/foundry.js:3090
    render https://<IP_ADDRESS>:30000/scripts/foundry.js:3021
    _handleConvenientEffectsClick https://<IP_ADDRESS>:30000/modules/dfreds-convenient-effects/scripts/controls.js:40
    _onClickTool https://<IP_ADDRESS>:30000/scripts/foundry.js:51831
    jQuery 2
        dispatch
        handle
[dynamic-effects-adder.js:140:53](https://<IP_ADDRESS>:30000/modules/dfreds-convenient-effects/scripts/effects/dynamic-effects-adder.js)
    onEffectClick https://<IP_ADDRESS>:30000/modules/dfreds-convenient-effects/scripts/app/convenient-effects-controller.js:246
    AsyncFunctionThrow self-hosted:642
    (Async: async)
    onEffectClick self-hosted:1121
    jQuery 8
    _initClickListeners https://<IP_ADDRESS>:30000/modules/dfreds-convenient-effects/scripts/app/convenient-effects-app.js:107
    activateListeners https://<IP_ADDRESS>:30000/modules/dfreds-convenient-effects/scripts/app/convenient-effects-app.js:42
    _render https://<IP_ADDRESS>:30000/scripts/foundry.js:3090
    AsyncFunctionNext self-hosted:638
    (Async: async)
    render https://<IP_ADDRESS>:30000/scripts/foundry.js:3021
    _handleConvenientEffectsClick https://<IP_ADDRESS>:30000/modules/dfreds-convenient-effects/scripts/controls.js:40
    _onClickTool https://<IP_ADDRESS>:30000/scripts/foundry.js:51831
    _onClickTool self-hosted:1121
    jQuery 2

Okay, thanks for reporting this. I'll fix it in the next release

Fixed in v2.6.1


Update example webhook URLs after 'example-' prefixing

cc @erikbern
I will also delete the old apps from our org. (It's a minor bit of a deployment awkwardness that an app rename involves manual delete.)

Thanks!
Yeah I agree it's a bit annoying when you get stray apps from renaming


How to use --no-initial together with --clean ?

Hi,
I'm trying to use cpx 'index.html' 'build' --no-initial --watch --clean. My desired behavior is:

Don't perform any copy after execution. Don't perform clean until the first copy (delayed by --no-initial, triggered by user saving the file).

However, it seems like --clean won't be blocked/delayed by --no-initial parameter. Instead, it will always do the clean right after executing the command.
My use case is that I need to override the destination file (read-only) when user first hit "Save" (override on every "Save" is better) , meaning that I want to perform copy index.html (edited) -> build/index.html (read-only) while watching.
I saw we have options for not overriding, but it seems during watching it won't override by default either.

And when the destination file is read-only. Verbose mode will only display one line:

Copy: index.html --> build

Without telling the result, either error message like "failed to copy file" or success like below:

Copied: index.html --> build/index.html

Thank you for the report.
Granted, this is confusing.
cpx should delay the cleaning until at the first copy if --no-initial is given.
Also, should print proper error messages.
I will fix this issue within a few days.

I'm sorry for the delay.
I have rethought this.
I'm going to make throwing the error "--clean and --no-initial cannot be combined."
Because:

If --clean option was given, cpx removes all matched files with the given pattern in the destination directory. This option intends to clean old files which are removed from the source directory.
E.g.: In cpx aaa/**/*.js bbb --clean case, cpx removes bbb/**/*.js files then it does copy all source files.
If --no-initial option was given, cpx does not copy all files. It copies only changed files on each change. This option intends to not do useless copies on the assumption that someone has not changed the source files since the previous copy.

Those 2 options are incompatible. --clean requires copying all source files (or remove only files which are removed from the source directory) at initialization, --no-initial requires to do nothing at initialization.
This is a breaking change, so I will make this change at the end of this year; Node 0.x supports are dropped.


Change version to 1.4.3-SNAPSHOT

They do on my env. But don't know if I can properly reproduce it.


AnimateGroup question, not a bug

Hi,
Simple question regarding the AnimateGroup. Is it possible to play PNG seq in a loop?
Thx

nope, it's not a sprite animation. it's css style with transition animation.

ok, thx


disable_resource_variables is deprecated

Click to expand!
Issue Type
Bug
Source
source
Tensorflow Version
tf 2.6.0
Custom Code
Yes
OS Platform and Distribution
Linux Ubuntu 16.04
Mobile device
No response
Python version
3.8.10
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
A bug happened!
I was running my code normally but then all of sudden I received a warning that disturbing my code from compiling and my program completely stop T.T
My source code was written in tf v1 and I've been running it on tf v2 so apparently I need 'tf.disable_resource_variables()' for my programme to work.

Standalone code to reproduce the issue
I received this WARNING.
"WARNING:tensorflow:From /home/mdee/.local/lib/python3.8/site-packages/tensorflow/python/compat/v2_compat.py:101: disable_resource_variables (from tensorflow.python.ops.variable_scope) is deprecated and will be removed in a future version.
Instructions for updating:
non-resource variables are not supported in the long term"
This is exactly what I received and I read from the tensorflow.org website that if my code needs tf.disable_resource_variables() to be called to work properly, I should file a bug.
Please let me know how can I run my code smoothly again.

Relevant log output
No response

Hi @maidang-ee !
Could you share a minimal stand alone code to replicate the issue.
Thank you!

Hi @mohantym!
Thank you for getting back to me.
Absolutely, I will attach some parts of the code.
I'm not sure if they are useful but please let me know if you need anything more.
I really appreciate it.
Since my research is at the critical time so I really need the code to work again ASAP!!!

< I used this command to make the script written in tf v1 to run on tf v2>

<This part line 101 is what the warning is about>
Thank you again and I'm looking forward to hearing from you soon.

Hi @mohantym,
Just a quick update.
I got my program to work again.
Thank you for spending time on looking at my issue.
You have a good day!

Ok @maidang-ee !
Closing this issue it seems to be resolved from above comment.


 I think other people might be interested in having this ability as well so I'm going to take a shot at adding in this as a feature.

In the interests of keeping the plugin lean and not including convenience features which meet the needs of only very specific usage case I am going to close this Issue and associated PR.


New meeting attendance functionality

There seems to be new functionality recently where the meeting attendance report is automatically added to the meeting chat at the conclusion of the meeting and also if viewing the meeting in the Calendar tab the report is shown there too. This documentation appears to be out of date with the most recent functionality.

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

ID: 9a8b1087-ae40-6813-16bc-a69c90e50d19
Version Independent ID: b808e843-80d8-4a96-c6ed-e8175968eb73
Content: Microsoft Teams meeting attendance report - Microsoft Teams
Content Source: Teams/teams-analytics-and-reports/meeting-attendance-report.md
Service: msteams
GitHub Login: @SerdarSoysal
Microsoft Alias: serdars

Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@nickp85 thank you for pointing this out. I'm working on updating the article. Just a quick question. Is the report still downloadable according to the article. So just a note adding that the report is shown when in meeting, on chat, etc?

Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


API limit information is not exposed

Most valid responses from the API return with headers which contain useful information about the current state of API limits.
Without this info, it makes it very difficult to anticipate 429 Too Many Request errors if two competing systems are using the same user account through the API.

Most of users don't need headers information. So this SDK by default doesn't return it.
For those who need headers, try this: https://github.com/ringcentral/RingCentral.Net/blob/master/RingCentral.Tests/LowLevelApiTest.cs#L59-L70

I've added doc: https://github.com/ringcentral/RingCentral.Net#how-to-access-headers

Thanks for the quick response Tyler!
Although I agree that technically we can access the headers if we handle all response processing ourselves, I feel like the point of the SDK is being missed if that's truly the solution.
Not only does it mean that there will be different implementations for each project, it also removes half of the SDK's value since it would only be used to prepare the requests at that point.
It's almost as if a car didn't have a fuel gauge and instead of adding one, the car manufacturer suggested that users just make their own engine for the car that supports fuel gauges.

And just to touch on your point about most users not needing the headers, with API limits as low as RingCentral's, I'd have to disagree.
If the info is important enough for every response to contain it, it seems like it should be important enough to officially support.

Are you suggesting something like this:
var r = await rc.Restapi().Account("~").Extension("~").Get();
var headers = r.headers
var extInfo = r.body

?

Exposing the raw headers isn't ideal since we'd still need parse them manually.
I was imagining some sort of property named something like ApiLimits that all the response objects have. That ApiLimits object would look something like this:
struct ApiLimitsInformation {
  public string LimitGroup { get; set; }
  public TimeSpan LimitWindow { get; set; }
  public int TotalLimit { get; set; }
  public int RemainingCalls { get; set; }
}

Let me know if that doesn't make sense. I'm happy to clarify in some other way if needed!

There is another way, not sure you like it. https://github.com/ringcentral/RingCentral.Net/blob/master/RingCentral.Tests/AfterCallTest.cs
It's listener pattern so for each http call you can get headers.

It still requires us to parse the headers ourselves and it's also not idomatic C#.
Here's an boiled down example of why I think it's important to give access to it via the response objects.
var listOfCallIds = this.getSomeArrayFullOfTelephonyIds();
var responses = new List<SomeType>();

foreach (var callId in listOfCallIds) {
  var response = await this._rc.Restapi().Account("~").Extension("~").CallLog(callId).Get();
  responses.Add(response);

  if (response.ApiLimits.RemainingCalls < 1) {
    // Wait some time to avoid getting rate limited
    await Task.Delay(1000 * 61);
  }
}

The overall idea is good. But I don't like the idea of adding ApiLimitsInformation to the response object. Because that information doesn't belong to the object. And the information is temporary only.  RemainingCalls only makes sense at that moment, it will become out-of-date very soon.

It still requires us to parse the headers ourselves and it's also not idomatic C#.

Yes it does. But you can handle it in a central place (in the event handler) instead of modify code every where.
It is idomatic C#. Check this: C# events.
I am not saying it's the best solution for you. It's just an option FYI.

Some code snippets currently in my mind:
var rateLimitTracking = new Dictionary<string, int>{
{ 'Light', 10 }
{ 'Medium', 10 }
{ 'Heavy', 10 }
{ 'Auth', 10 }
}
void EventHandler(object sender, HttpCallEventArgs eventArgs)
{
   var rateLimitGroup = eventArgs.httpResponseMessage.Headers
        .First(i => i.Key == "X-Rate-Limit-Group").Value.First();
   var rateLimitRemaining =int.Parse(eventArgs.httpResponseMessage.Headers
        .First(i => i.Key == "X-Rate-Limit-Remaining").Value.First());
    rateLimitTracking[rateLimitGroup] = rateLimitRemaining
}
rc.AfterHttpCall += EventHandler;

var listOfCallIds = this.getSomeArrayFullOfTelephonyIds();
var callLogs = new List<CallLogInfo>();
foreach (var callId in listOfCallIds) {
  var callLog = await rc.Restapi().Account("~").Extension("~").CallLog(callId).Get();
  responses.Add(callLog);
  if (rateLimitTracking["Heavy"] < 1) {
    // Wait some time to avoid getting rate limited
    await Task.Delay(1000 * 61);
  }
}

I can add an experimental feature. Add rateLimitTracking to RestClient. So that as end user you don't need to parse headers.

New feature added in 4.0.0-beta3
Usage: https://github.com/ringcentral/RingCentral.Net/blob/master/RingCentral.Tests/RateLimitsTest.cs

New users should use the Rate Limit Extension


Borders for i3 workspace switcher

Is your feature request related to a problem? Please describe.
Currently, there are no options to enable borders for i3 workspace switcher module. This is what I'm hoping to achieve:

Why does polybar need this feature?
People are used to this appearance since this option is there in i3-bar and plasma panels etc. Implementing this feature would be give a consistent UX without annoying the user about the tiny missing feature.
Describe the solution you'd like
A config parameter for [modules/i3] name border=true would be a good start. Additionally, setting border width and spacing between the workspaces would be very much appreciated.

We will not be adding this feature.
Polybar's goal is not to look like i3bar or plasma panels. In fact, one of polybar's key characteristics is that it is almost entirely based on rendered text (except for the tray), adding such borders would break from this.


Fluent is awesome! (Not an Issue!)

Just wanted to say that Fluent is absolutely awesome.
Thank you so much for creating it.
I've got it setup with SS 3.3.0-RC2 using the Fluent Master branch and it's working flawlessly.
It's about the 4th translation module I've tried and the only one that has allowed seamless translation of custom DataObjects in a way that doesn't break templates or the back end CMS at all. When you already have a single language site already setup and don't want to re-do hours and hours of work that's super important.
It's absolutely wonderful.
I don't like the YAML setup file... it's extremely difficult to work out how many spaces should be where but once you get it working ok the rest of it is astonishing. The YAML thing goes for all YAML files. Why doesn't it just read what's on the line? Why does one space or two spaces make such a vast difference? Idiotic. </rant over>
Fluent + SilverStripe = amazing. Thank you!

Haha, thanks. :)
I thought about going the way subsites did and make everything configurable in the CMS, but my main goal with fluent was to keep it simple and light, and extra interface probably wouldn't achieve that.
Thanks for testing it out, and let me know if you get any bugs working with 3.3.

I suggest setting up your IDE with a plugin to support .editorconfig, then you'll have a lot fewer issues working with yaml.


⚠ Spryr has degraded performance

In 95032c6, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 5693 ms

Resolved: Spryr performance has improved in 5e0a896 after 22 minutes.


Disable MySQL binary logs

We don't need them and they take up space.

Bump, this seems to be interesting :)


Corrected a problem with the acceptance test action.

acceptance_test.yml did not run properly.
It seems the replacement for ::set-output (i.e. >> $GITHUB_OUTPUT) does not accept newlines in the data.
This was a problem with multi-line commit messages.
Just replaced newlines by spaces.

Do you mean this line?
https://github.com/MobilityData/gtfs-validator/blob/528ac92ec1a1d20789318129871e188b83e68c8e/.github/workflows/acceptance_test.yml#L39
Removing the double quotes?

Check https://github.com/MobilityData/gtfs-validator/pull/1584

Approved it.


npm audit

npm audit fix
replace istanbul with nyc as istanbul is no longer maintained
update elasticsearch to latest version with 1.7 support

Coveralls works: https://coveralls.io/github/Enrise/node-esclient?branch=SAAS-109_npm_audit