How to get an archived release of JDK 17 of Panama or Loom?

Any ideas how to get an archived version of Panama OpenJDK?
I'm trying to get the following archived jdk (Panama for jdk17)
https://jdk.java.net/panama/17/
- name: Set up Oracle Open JDK Panama
      uses: oracle-actions/setup-java@v1
      id: download-jdk
      with:
        website: jdk.java.net
        release: 'panama'

This will get the latest.
Thank you,
Carl

Hi @carldea
We're planning to add support for OpenJDK EA archives (ex. to confirm a regression between 2 EA builds) but what would be the use-case for supporting older EA builds of projects (loom, panama, ...)?

I have code in two branches that requires the following respectively.

Panama JEP 412 (JDK 17)
Panama JEP 419 (JDK 18+)

It would be nice to build and test against them with it’s corresponding archive release. Since JDK 17 is an LTS, this would allow developers to code against those incubator modules and still work. E.g. I can use jextract tool to generate code for JDK17 JREs.
as JEP 424 (Preview) is coming soon it’s likely JDK 19+
Or should we not encourage people to continue using or relying on incubator modules (set in time at a major release)?

LTS or not, we should avoid encouraging developers to keep using an API (either in Preview, or from an Incubator module) if an updated version is available.

@delabassee ,
No worries, we can close this issue, if you want.
When blogging with code examples it's difficult for the reader to reproduce or follow along unless they download the exact build archive release. It's more about testing and trying out the newer APIs.
I actually just found out about where to get the archived release (JEP 412) such as the following link:
https://jdk.java.net/panama/17/


Support Django

Hello!
Nice plugin!
Does this plugin have the ability to add Django?

Star! :-)

Hey @WCN-llc, thanks.
Yes, it does, you can add any Python library you want by using the Nx executors (e.g. npx nx run <myproject>:add --name numpy.
You can also use npx nx build <myproject> to generate the .whl artifact file with all external + local dependencies and use it in a Docker container, serverless functions, etc.
I wrote this article about it: https://medium.com/better-programming/poetry-python-nx-monorepo-5750d8627024

Hey @WCN-llc, thanks.
Yes, it does, you can add any Python library you want by using the Nx executors (e.g. npx nx run <myproject>:add --name numpy.
You can also use npx nx build <myproject> to generate the .whl artifact file with all external + local dependencies and use it in a Docker container, serverless functions, etc.
I wrote this article about it: https://medium.com/better-programming/poetry-python-nx-monorepo-5750d8627024

@lucasvieirasilva
Thank you so much, friend! :-)


test travis rolling variable apply 2 3-4s

@fschlimb I think we need to drop this PR, needn't we?

Looks like it. @ehsantn?


IOError: org.apache.log4j.spi.LoggingEvent; class invalid for deserialization

Version: logstash-5.0.0
Operating System: CentOS Linux release 7.2.1511
Config File (if you have sensitive info, please remove it):
input {
log4j {
mode => "server"
host => "<IP_ADDRESS>"
port => 4567
type => "log4j"
}
}
filter {
}
output {
elasticsearch {
action => "index"          #The operation on ES
hosts  => "localhost:9200"   #ElasticSearch host, can be array.
index  => "logstash-1"         #The index to write data to.
user => logstash_internal
password => changeme
}
}
Sample Data:
Steps to Reproduce:
when i use log4j in java to print something, the logstash error log is

org/jruby/ext/jruby/JRubyObjectInputStream.java:58:in `read_object'
/opt/logstash/logstash-5.0.0/vendor/bundle/jruby/1.9/gems/logstash-input-log4j-3.0.3-java/lib/logstash/inputs/log4j.rb:105:in `handle_socket'
/opt/logstash/logstash-5.0.0/vendor/bundle/jruby/1.9/gems/logstash-input-log4j-3.0.3-java/lib/logstash/inputs/log4j.rb:160:in `run'
[2016-11-07T16:10:45,022][DEBUG][logstash.inputs.log4j    ] Closing connection {:client=>"<IP_ADDRESS>:62896", :exception=>#<IOError: org.apache.log4j.spi.LoggingEvent; class invalid for deserialization>}

It sounds like logstash is connecting just fine (the subject of this issue says "can't connect to logstash").
As for your error output, I don't know what to make of it. It is looking for a class org.apache.log4j.spi.LoggingEvent but is thinking it can't deserialize them?
What version of log4j are you using to send?

I am using log4j-1.2.17, when i downgrade the logstash to 2.4.0, everything is ok

I too is facing the same problem. I tried with the same parameters as @clevertension, log4j 1.2.17 and logstash 5.0.0. There is no error shown in the stdout and subsequent logs to the port gets exceptions. Downgrading to logstash 2.4 works.

some problem +1

Based on @zvving commenting on this and #13 within 3 minutes of eachother, I am closing this as a duplicate of #13.

@jordansissel OK, tks!
Now how to provisional fixed it, or must to downgrading to 2.4 ?

As a workaround, I am seeing several reports in this ticket that downgrading to Logstash 2.4 works. If you need a solution now, please downgrade to Logstash 2.4.

I think I have found the problem. There is a bug in log4j 2 where the "log4j 1.2" API provided by log4j2 has the LoggingEvent class that is not serializable, so Logstash rejects it.  I have details in this ticket: https://github.com/logstash-plugins/logstash-input-log4j/issues/36#issuecomment-263421638
Fixing this may require a new release of Logstash because I had to patch logstash itself to make this work.

A workaround for Logstash 5.0.0 and 5.0.1:
There's a file logstash-core/lib/jars.rb with this line:
require_jar('org.apache.logging.log4j', 'log4j-1.2-api', '2.6.2')

If you comment it out, log4j input works successfully for me with Logstash 5.0.1.
Here's the patch:
--- old/logstash-core/lib/jars.rb	2016-11-28 16:07:07.208906014 -0800
+++ new/logstash-core/lib/jars.rb	2016-11-28 16:07:09.266844854 -0800
@@ -1,5 +1,5 @@
 require 'jar_dependencies'
-require_jar('org.apache.logging.log4j', 'log4j-1.2-api', '2.6.2')
+#require_jar('org.apache.logging.log4j', 'log4j-1.2-api', '2.6.2')
 require_jar('org.apache.logging.log4j', 'log4j-api', '2.6.2')
 require_jar('org.apache.logging.log4j', 'log4j-core', '2.6.2')
 require_jar('com.fasterxml.jackson.core', 'jackson-core', '2.7.4')

You can apply it with patch -p1 if you are familiar with the patch tool.
This patch is probably not supported and we should have this bug fixed for Logstash 5.1.0

One more thing about this issue: I got no log message on the logstash side for this problem until I raised the level to DEBUG.
I think that's wrong. When an input plugin refuses to work (and closes the connection), because it can't handle the data someone's sending it, it should clearly not do so "silently", but should definitely log an ERROR message.
Should I open another ticket for this?

I got no log message on the logstash side for this problem until I raised the level to DEBUG.

This is a lose-lose scenario. Here's the two options I've been faced with in the past:

Logstash logs too much and annoys users. Annoyed users file tickets.
Logstash logs too little and annoys users. Annoyed users file tickets.

Both scenarios cannot be solved simultaneously because one solution cause problems for the other.
If we make it log more by default, someone will ask me this "Why is logstash so noisy when a bad connection hits log4j input?" and we'll go back in circles.
The reason the log message is hidden by default is because there are a variety of reasons a connection could be faulty -- a network or security scan, a corrupt client, a bad network, incompatible client, unexpected data, etc.
I'm not sure how to solve "log just this specific problem where logstash has a bug in the log4j input" but also keep the corrupt client, network scan, etc from being logged by default.

Logstash logs too little and annoys users. Annoyed users file tickets.

Well, I am not annoyed but simply puzzled.

The reason the log message is hidden by default is because there are a variety of reasons a connection could be faulty -- a network or security scan, a corrupt client, a bad network, incompatible client, unexpected data, etc.

In a production environment (where I never, ever would want to set the log level to DEBUG), I would be interested in all of those reasons, why my application logs are lost.
So my only chance right now, is to make logstash really noisy.

In Logstash 5 it is possible to set the log level of individual components,
so you should be able to put the log4j input specifically at debug level.
On Tue, Nov 29, 2016 at 2:01 AM Norbert Pomaroli<EMAIL_ADDRESS>wrote:

Logstash logs too little and annoys users. Annoyed users file tickets.
Well, I am not annoyed but simply puzzled.
The reason the log message is hidden by default is because there are a
variety of reasons a connection could be faulty -- a network or security
scan, a corrupt client, a bad network, incompatible client, unexpected
data, etc.
In a production environment (where I never, ever would want to set the log
level to DEBUG), I would be interested in all of those reasons, why my
application logs are lost.
So my only chance right now, is to make logstash really noisy.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/logstash-plugins/logstash-input-log4j/issues/35#issuecomment-263527506,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIC6mUtL_bHTcPOE1qKkTeZzoCs1NFxks5rC_gDgaJpZM4Kq8fF
.

The same issue in 5.1.1 :/
If you comment it out in the now-called "logstash-core_jars.rb", it works just fine again.

Confirm fix (comment out one line, logstash-core_jars.rb)
Will Logstash 5.2.0 have fix ?

This issue is impacting us as well.  We would like to know what release this is going to be fixed on too.

Have same trouble with 5.1.2. But when comment require_jar line in logstash-core_jars.rb catch next exception:
[root@logstash-test logstash]# bin/logstash --log.level trace --path.settings /opt/logstash/config/
NameError: missing class name (`org.apache.logging.log4j.Level')
  get_proxy_or_package_under_package at org/jruby/javasupport/JavaUtilities.java:54
                      method_missing at file:/opt/logstash-5.1.2/vendor/jruby/lib/jruby.jar!/jruby/java/java_package_module_template.rb:14
                             Logging at /opt/logstash/logstash-core/lib/logstash/logging/logger.rb:6
                            LogStash at /opt/logstash/logstash-core/lib/logstash/logging/logger.rb:5
                              (root) at /opt/logstash/logstash-core/lib/logstash/logging/logger.rb:4
                             require at org/jruby/RubyKernel.java:1040
                              (root) at /opt/logstash/logstash-core/lib/logstash/util/loggable.rb:1
                             require at org/jruby/RubyKernel.java:1040
                              (root) at /opt/logstash/logstash-core/lib/logstash/util/loggable.rb:2
                             require at org/jruby/RubyKernel.java:1040
                              (root) at /opt/logstash/logstash-core/lib/logstash/settings.rb:1
                             require at org/jruby/RubyKernel.java:1040
                              (root) at /opt/logstash/logstash-core/lib/logstash/settings.rb:2
                             require at org/jruby/RubyKernel.java:1040
                              (root) at /opt/logstash/lib/bootstrap/environment.rb:70

Looks like this will be fixed by https://github.com/elastic/logstash/pull/6309 which should be come with 5.2.0.
@jordansissel can you confirm?

@jakommo It is, and checking the commit gives a more deterministic way of verifying the change was incorporated into the released branch.
https://github.com/elastic/logstash/commit/69c3bc21d4a1674da01d24bd20424eb401daefaf


Vue driver support for kebab-case

Added support to handle kebab-case props in the Vue driver
According Vue style guide best practices the props on template components should be passed in in kebab-case format.
Vue docs reference: https://vuejs.org/v2/style-guide/#Prop-name-casing-strongly-recommended.
Issue reference: https://github.com/paypal/paypal-checkout-components/issues/1338#issuecomment-777005173
Associated PR: https://github.com/paypal/paypal-checkout-components/pull/1650

Codecov Report

Merging #351 (894b53e) into master (68bf604) will increase coverage by 0.02%.
The diff coverage is 100.00%.

:exclamation: Current head 894b53e differs from pull request most recent head 38a0d09. Consider uploading reports for the commit 38a0d09 to get more accurate results

@@            Coverage Diff             @@
##           master     #351      +/-   ##
==========================================
+ Coverage   95.56%   95.58%   +0.02%
==========================================
  Files          17       17
  Lines         992      997       +5
==========================================
+ Hits          948      953       +5
  Misses         44       44

Impacted Files
Coverage Δ

src/drivers/vue.js
100.00% <100.00%> (ø)

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 68bf604...38a0d09. Read the comment docs.


Bug preventing widgets from being initialized after each async fragment

For progressive rendering, I tried to use <init-widgets immediate/> and moved the <lasso-body /> to the top of HTML, but unfortunately it didn’t work. The Widgets are initialized after the DOM ready event, instead of the end of async fragment.
I tried to run https://github.com/marko-js-samples/marko-progressive-rendering on my local machine but the widgets are also not initialized earlier. The widget behaviors are always attached after the DOM ready event despite of the options we chose. This is quite weird since it works properly on the demo (https://marko-progressive-rendering.herokuapp.com/).

Thanks for opening the issue @abiyasa. The logic for looking up the widgets context for each completed async fragment was incorrect. This resulted in widgets not being initialized until the final chunk (where the logic was correct).
The issue has been fixed.
New version published<EMAIL_ADDRESS>Please let me know if you find any issues with the latest version. Thanks again!

Thanks @patrick-steele-idem for fixing the bug. I've updated the marko-progressive-rendering to use v5.0.6 and it works now :+1:


feat(devices): filter device list by name

The list device API supports filtering the list by a device's name. This commit adds the support in the get_all_devices method.

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


Add support legacy dataspace value

In case of legacy dataspace value is passed down by framework/av/media code.
Tracked-On: OAM-119899

Improper Commit Message
Valid Commit Message
Improper Jira Status,
jira status not in ['In Progress','Implemented']

Android CI has started Engineering Build for this issue ,Please check the linked Tracked-On issue/Android CI Web  for more details.

Android CI has started Engineering Build for this issue ,Please check the linked Tracked-On issue/Android CI Web  for more details.

FAILURE: Android CI has completed Engineering Build for this issue.Please check the linked Tracked-On issue/Android CI Web  for more details.

FAILURE: Android CI has completed Engineering Build for this issue.Please check the linked Tracked-On issue/Android CI Web  for more details.

Android CI has started Engineering Build for this issue ,Please check the linked Tracked-On issue/Android CI Web  for more details.

FAILURE: Android CI has completed Engineering Build for this issue.Please check the linked Tracked-On issue/Android CI Web  for more details.

Android CI has started Engineering Build for this issue ,Please check the linked Tracked-On issue/Android CI Web  for more details.

Close this pull due to ci built fail with this outdated patch. Re-commit the patch in https://github.com/projectceladon/external-mesa/pull/123 on new code base.

FAILURE: Android CI has completed Engineering Build for this issue.Please check the linked Tracked-On issue/Android CI Web  for more details.


How hard would it be to use gRPC as our transport layer (for Datastore or PubSub)?

Now that gRPC is open-source, I was wondering how much effort it might be to add it to gcloud-python as the transport layer. Currently, I believe it would be supported for the Datastore and PubSub services...
Obviously we'd have to look at package distribution (as pip install grpc has some extra dependencies) but it'd be cool to add support for this as I suspect we'd see better performance.

I don't see any docs for it (either in the repo, or linked from the PyPI page).  I don't really have any notion of what its API would be like.

I'd love to be stable on other things before. This screams of churn (though I don't have much faith in our transport layer, httplib2).

This would be lovely, but would probably require the Google API Frontend service to support gRPC in the first place.

@nathanielmanistaatgoogle Would you have some time to chat about feasibility of using gRPC in a stable project?

Just an FYI  for Datastore -- v1beta2 does not support grpc. The next Datastore release will, however the gcd tool will likely not support it in the short term.

@pcostell Thanks for the heads up. When do you expect the next release to come out?

We are pretty close, so hopefully soon.

FYI, Cloud Pub/Sub will enable gRPC soon too.

Great to hear from both. Will there be a formal announcement / something for us to look out for?

Datastore will have an announcement, I'll make sure to file bugs against the gcloud-* libs to upgrade once it is ready.

Awesome! Thanks

All three APIs now use gRPC when available.


Better typesafety for ContentValues constructors

Our type safety when constructing models from ContentValues was lacking. This PR improves the situation:
There are now two constructors generated in each model class for constructing from ContentValues. One takes the values and a list of properties to read from the values, which is used to type-safely read each value from the ContentValues--if anything is of the wrong type or can't be coerced, a ClassCastException will be thrown. The other constructor just takes a single ContentValues and calls the two-arg constructor with the PROPERTIES array for that model.
This PR also increases type safety by making ValueCastingVisitor explicitly throw a ClassCastException when type coercion fails. We used to rely on the cast to (TYPE) in the get() method to throw this, but that won't work when get() is called with a property of unknown type (e.g. Property<?>).

LGTM


Upload to testflight fails constantly

Using fastlane  2.93.1 xcode 9.4 and upload_to_testflight(), Fastlane upload fails for both:
DAV:
unable to verify WebDAV transport: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target An error occurred while connecting to the transport host https://itmsdav.apple.com: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target Could not start delivery: all transports failed diagnostics Return status of iTunes Transporter was 1: unable to verify WebDAV transport: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target \nAn error occurred while connecting to the transport host https://itmsdav.apple.com: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target \nCould not start delivery: all transports failed diagnostics The call to the iTMSTransporter completed with a non-zero exit status: 1. This indicates a failure.
non-DAV:
Could not start delivery: all transports failed diagnostics Return status of iTunes Transporter was 1: Could not start delivery: all transports failed diagnostics The call to the iTMSTransporter completed with a non-zero exit status: 1. This indicates a failure.
I'd be happy to provide a certificate if this is a proxy related error but what where?

@Kollerb04 I have never seen this error message before 😱

Are you able to successfully upload an IPA manually using Xcode or Application Loader?
What were the versions of fastlane and Xcode the last time this worked?
Did the network you are on change any security setting (or something) that could effect?
Does uploading work if you are outside of the network that uploading failed on?

@joshdholtz
1.I guess yes
2.9.3 and fastlane 2.93.1
3.I'm afraid yes
4. Actually DAV upload worked on the outside nework, yes.
So where do I supply the ssl certificate for this?

@Kollerb04 There isn't a place to supply an SSL certificate. I don't know anything about your network setup or if you are within a company network but sounds like to me like your network admins could potentially be blocking something here if this used to work and still works outside of the network 😬 The best bet is to probably talk to them to open stuff up to get things resolved.


Feature/on popup event

Also includes #19 (not really possible to cleanly merge to minified files being included).
Adds the ability to configure an "onPopup" event that is configurable via the options.

Sorry for taking so long to merge, thank you for coding this!

No problem, I know what that's like, I should make another one that updates the docs because I'm a jerk and didn't do that...

If you want to add the onPopup feature to the options there, that would be awesome.  I'll merge once you post.

Sure, I'll do that tomorrow.


Error while searching for extension

From last couple of weeks I am seeing this a lot
When I search for an extension it shows this error for a sec or so and then it shows the actual results

VS Code Version: 1.88 insider and 1.87
OS Version: Windows 11

Steps to Reproduce:

Search for extension
initially showing the error while typing

and after a sec. or so it shows the actual results

@abhijit-chikane Can you please try again with the latest VS Code and let us know if you are still able to reproduce this error?

I don't see this error now
I think we can close this
Thanks!🎉


Multi-point lines on tablet

I did not find how to add several points when drawing a line with a tablet? i.e. what is replacing the alt key?

The line-editing must be redesigned so this is more accessible, not just on tablets. For a workaround, you can select a point, and then use the duplicate button:

(there's an analogous button in desktop view)

That's a very useful trick, thanks a lot!


Integration not showing all devices (like before)

I am using always latest version of this integration and I've noticed that since one month or so many devices are missing.
Most of all we have three smartphones and none of them is listed as a Technicolor's entity.
My router is a (stock unrooted) DGA4331.

I still am having this issue although I am always updating both the integration and Home Assistant. 🥲

@Cr4z33 Hi.
Sorry for the late response.
Still an issue?

Hi @shaiu I confirm it is.


Laravel 7 installation

Q
A

Bug?
no

New Feature?
no

Framework
Laravel

Framework version
7.0.4

Package version
2.4.5

PHP version
7.4.0

Actual Behaviour
Apparently laravel is using Illuminate/routin version 7 and dingo requires version 5 || 6
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Conclusion: don't install dingo/api v2.4.5
    - Conclusion: don't install dingo/api v2.4.4
    - Conclusion: don't install dingo/api v2.4.3
    - Conclusion: don't install dingo/api v2.4.2
    - Conclusion: don't install dingo/api v2.4.1
    - Conclusion: don't install dingo/api v2.4.0
    - Conclusion: don't install dingo/api v2.4.0-rc2
    - Conclusion: remove laravel/framework v7.0.4
    - Installation request for dingo/api ^2.4 -> satisfiable by dingo/api[v2.4.0, v2.4.0-rc1, v2.4.0-rc2, v2.4.1, v2.4.2, v2.4.3, v2.4.4, v2.4.5].
    - Conclusion: don't install laravel/framework v7.0.4
    - dingo/api v2.4.0-rc1 requires illuminate/routing ^5.5 || ^6.0 -> satisfiable by illuminate/routing[5.5.x-dev, 5.6.x-dev, 5.7.17, 5.7.18, 5.7.19, 5.7.x-dev, 5.8.x-dev, 6.x-dev, v5.5.0, v5.5.16, v5.5.17, v5.5.2, v5.5.28, v5.5.33, v5.5.34, v5.5.35, v5.5.36, v5.5.37, v5.5.39, v5.5.40, v5.5.41, v5.5.43, v5.5.44, v5.6.0, v5.6.1, v5.6.10, v5.6.11, v5.6.12, v5.6.13, v5.6.14, v5.6.15, v5.6.16, v5.6.17, v5.6.19, v5.6.2, v5.6.20, v5.6.21, v5.6.22, v5.6.23, v5.6.24, v5.6.25, v5.6.26, v5.6.27, v5.6.28, v5.6.29, v5.6.3, v5.6.30, v5.6.31, v5.6.32, v5.6.33, v5.6.34, v5.6.35, v5.6.36, v5.6.37, v5.6.38, v5.6.39, v5.6.4, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.6.9, v5.7.0, v5.7.1, v5.7.10, v5.7.11, v5.7.15, v5.7.2, v5.7.20, v5.7.21, v5.7.22, v5.7.23, v5.7.26, v5.7.27, v5.7.28, v5.7.3, v5.7.4, v5.7.5, v5.7.6, v5.7.7, v5.7.8, v5.7.9, v5.8.0, v5.8.11, v5.8.12, v5.8.14, v5.8.15, v5.8.17, v5.8.18, v5.8.19, v5.8.2, v5.8.20, v5.8.22, v5.8.24, v5.8.27, v5.8.28, v5.8.29, v5.8.3, v5.8.30, v5.8.31, v5.8.32, v5.8.33, v5.8.34, v5.8.35, v5.8.36, v5.8.4, v5.8.8, v5.8.9, v6.0.0, v6.0.1, v6.0.2, v6.0.3, v6.0.4, v6.1.0, v6.10.0, v6.11.0, v6.12.0, v6.13.0, v6.13.1, v6.14.0, v6.15.0, v6.15.1, v6.16.0, v6.17.0, v6.17.1, v6.18.0, v6.2.0, v6.3.0, v6.4.1, v6.5.0, v6.5.1, v6.5.2, v6.6.0, v6.6.1, v6.6.2, v6.7.0, v6.8.0].

Expected Behaviour
Install the thing
Steps to Reproduce
composer require dingo/api
Possible Solutions
udate Illuminate/rouing to version 7!

There's a PR for this https://github.com/dingo/api/pull/1715

Dingo currently doesn't support version 7, stay tuned, will be shortly done.

You can test now, please see
https://github.com/dingo/api/issues/1721

@specialtactics Can install v3.0.0-rc2 but I'm using spatie/laravel-fractal and it requires https://github.com/spatie/fractalistic which uses "league/fractal": "^0.19.0"
This package requires ^0.17
composer require dingo/api "^3.0.0"
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for league/fractal (locked at 0.19.2) -> satisfiable by league/fractal[0.19.2].
    - dingo/api v3.0.0-rc1 requires league/fractal ^0.17 -> satisfiable by league/fractal[0.17.0].
    - dingo/api v3.0.0-rc2 requires league/fractal ^0.17 -> satisfiable by league/fractal[0.17.0].
    - Conclusion: don't install league/fractal 0.17.0
    - Installation request for dingo/api ^3.0.0 -> satisfiable by dingo/api[v3.0.0-rc1, v3.0.0-rc2].

Installation failed, reverting ./composer.json to its original content.

@bbashy That's completely unrelated to this package.

Completely unrelated? Your package installs an old version of a package. How do I get around that?

@bbashy Yes you're right, because fractal is in v0. for major, it doesn't have like it does for non-dev versions, it will need to be updated.

@bbashy Updated & tagged

Thanks, I got past that one now. New issue;
composer require dingo/api "3.0.0-rc3" -vv
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Dependency resolution completed in 0.083 seconds
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - dingo/api v3.0.0-rc3 requires dingo/blueprint ^0.4 -> satisfiable by dingo/blueprint[v0.4.0].
    - Conclusion: remove phpdocumentor/reflection-common 2.0.0
    - Conclusion: don't install phpdocumentor/reflection-common 2.0.0
    - phpdocumentor/reflection-docblock 3.1.0 requires phpdocumentor/reflection-common ^1.0@dev -> satisfiable by phpdocumentor/reflection-common[1.0, 1.0.1].
    - phpdocumentor/reflection-docblock 3.1.1 requires phpdocumentor/reflection-common ^1.0@dev -> satisfiable by phpdocumentor/reflection-common[1.0, 1.0.1].
    - phpdocumentor/reflection-docblock 3.2.0 requires phpdocumentor/reflection-common ^1.0@dev -> satisfiable by phpdocumentor/reflection-common[1.0, 1.0.1].
    - phpdocumentor/reflection-docblock 3.2.1 requires phpdocumentor/reflection-common ^1.0@dev -> satisfiable by phpdocumentor/reflection-common[1.0, 1.0.1].
    - phpdocumentor/reflection-docblock 3.2.2 requires phpdocumentor/reflection-common ^1.0@dev -> satisfiable by phpdocumentor/reflection-common[1.0, 1.0.1].
    - phpdocumentor/reflection-docblock 3.2.3 requires phpdocumentor/reflection-common ^1.0@dev -> satisfiable by phpdocumentor/reflection-common[1.0, 1.0.1].
    - phpdocumentor/reflection-docblock 3.3.0 requires phpdocumentor/reflection-common ^1.0.0 -> satisfiable by phpdocumentor/reflection-common[1.0, 1.0.1].
    - phpdocumentor/reflection-docblock 3.3.2 requires phpdocumentor/reflection-common ^1.0.0 -> satisfiable by phpdocumentor/reflection-common[1.0, 1.0.1].
    - phpdocumentor/reflection-docblock 4.1.0 requires phpdocumentor/reflection-common ^1.0@dev -> satisfiable by phpdocumentor/reflection-common[1.0, 1.0.1].
    - phpdocumentor/reflection-docblock 4.1.1 requires phpdocumentor/reflection-common ^1.0@dev -> satisfiable by phpdocumentor/reflection-common[1.0, 1.0.1].
    - phpdocumentor/reflection-docblock 4.2.0 requires phpdocumentor/reflection-common ^1.0.0 -> satisfiable by phpdocumentor/reflection-common[1.0, 1.0.1].
    - phpdocumentor/reflection-docblock 4.3.0 requires phpdocumentor/reflection-common ^1.0.0 -> satisfiable by phpdocumentor/reflection-common[1.0, 1.0.1].
    - phpdocumentor/reflection-docblock 4.3.1 requires phpdocumentor/reflection-common ^1.0.0 -> satisfiable by phpdocumentor/reflection-common[1.0, 1.0.1].
    - Can only install one of: phpdocumentor/reflection-common[1.0, 2.0.0].
    - Can only install one of: phpdocumentor/reflection-common[1.0.1, 2.0.0].
    - Installation request for phpdocumentor/reflection-common (locked at 2.0.0) -> satisfiable by phpdocumentor/reflection-common[2.0.0].
    - Installation request for dingo/api 3.0.0-rc3 -> satisfiable by dingo/api[v3.0.0-rc3].
    - Conclusion: don't install phpdocumentor/reflection-docblock 5.1.0|install phpdocumentor/reflection-docblock 3.1.0|install phpdocumentor/reflection-docblock 3.1.1|install phpdocumentor/reflection-docblock 3.2.0|install phpdocumentor/reflection-docblock 3.2.1|install phpdocumentor/reflection-docblock 3.2.2|install phpdocumentor/reflection-docblock 3.2.3|install phpdocumentor/reflection-docblock 3.3.0|install phpdocumentor/reflection-docblock 3.3.2|install phpdocumentor/reflection-docblock 4.1.0|install phpdocumentor/reflection-docblock 4.1.1|install phpdocumentor/reflection-docblock 4.2.0|install phpdocumentor/reflection-docblock 4.3.0|install phpdocumentor/reflection-docblock 4.3.1
    - Conclusion: remove phpdocumentor/reflection-docblock 5.1.0|install phpdocumentor/reflection-docblock 3.1.0|install phpdocumentor/reflection-docblock 3.1.1|install phpdocumentor/reflection-docblock 3.2.0|install phpdocumentor/reflection-docblock 3.2.1|install phpdocumentor/reflection-docblock 3.2.2|install phpdocumentor/reflection-docblock 3.2.3|install phpdocumentor/reflection-docblock 3.3.0|install phpdocumentor/reflection-docblock 3.3.2|install phpdocumentor/reflection-docblock 4.1.0|install phpdocumentor/reflection-docblock 4.1.1|install phpdocumentor/reflection-docblock 4.2.0|install phpdocumentor/reflection-docblock 4.3.0|install phpdocumentor/reflection-docblock 4.3.1
    - dingo/blueprint v0.4.0 requires phpdocumentor/reflection-docblock ^3.1|^4.1 -> satisfiable by phpdocumentor/reflection-docblock[3.1.0, 3.1.1, 3.2.0, 3.2.1, 3.2.2, 3.2.3, 3.3.0, 3.3.2, 4.1.0, 4.1.1, 4.2.0, 4.3.0, 4.3.1, 4.3.2, 4.3.3, 4.3.4].
    - Can only install one of: phpdocumentor/reflection-docblock[4.3.2, 5.1.0].
    - Can only install one of: phpdocumentor/reflection-docblock[4.3.3, 5.1.0].
    - Can only install one of: phpdocumentor/reflection-docblock[4.3.4, 5.1.0].
    - Installation request for phpdocumentor/reflection-docblock (locked at 5.1.0) -> satisfiable by phpdocumentor/reflection-docblock[5.1.0].

Installation failed, reverting ./composer.json to its original content.

Don't really understand that well enough to know what the solution is.

@bbashy You can need to update all packages involved, ie.
composer update dingo/api phpdocumentor/reflection-docblock
Your version of reflection dockblock is locked at 5.1, which is more up to date than what blueprint supports. The above could potentially work, alternatively I could allow version 5 in dingo blueprint, but I'm not sure what repercussions that would have. I will try anyway since I think doc generation is not overly working at the moment.

@bbashy Try again plz

Thanks, able to install it now;
composer require dingo/api "^3.0"
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 3 installs, 0 updates, 0 removals
  - Installing doctrine/annotations (v1.8.0): Downloading (100%)
  - Installing dingo/blueprint (v0.4.1): Downloading (100%)
  - Installing dingo/api (v3.0.0-rc3): Downloading (100%)
dingo/api suggests installing tymon/jwt-auth (Protect your API with JSON Web Tokens.)
Writing lock file


Implement the Conformance Service Info

To be able to pass the FIDO Alliance Conformance Tests the Onboarding Server must implement the Conformance Service Info to provide the Device with the required token used to notify the successful onboarding to the Dasboard API as described in the Step by Step documentation.

Closing this one in favour of https://github.com/fdo-rs/fido-device-onboard-rs/issues/624 because I've seen it sync-ed  downstream first


Refactor command to parse and valiate params

This PR's base is #75, so 75 should be merged first.

@stephenwithav great effort thanks a lot.


Print Ruby warnings to the console as generated by double_entry

Print Ruby warnings to the console during our test run. We don't want this gem producing warning as that would frustrate projects downstream.
If we notice any warnings, they should be fixed.

+1

+1


why did you split your network into two stages to train? what is the different between all to train and split train?

The stages were separated to allow the first stage to learn fully before the second stage is added. Thanks to this approach the second stage doesn't start lerning before the first stage is able to make sensible predictions.
Marek


Adds ShadowCasterVisitor as easy override by user

Allows either override with user provided visitor, false (disable any visitor) or defaut visitor (which handles lights, subscene with rtt, transparent nodes)

do we need this feature now ?

It fixes a bug in transparent shadow casting ?

I was talking about the visitor stuff, but ok never mind

On osgjs side we still need the visitor to remove transparent material otherwise default rendering on par with osgjs material won't give good results.
( it doesn't add new code, the visitor is the old one we had before. it's just allowing user control/overwrite of that part )


Trigger with cb_sink does not appear to redraw the screen

Hi, I have a custom view which is basically like a select view but with my own formatting. I want to do a redraw of the view whenever the the user submits new content to the view through and EditView. I tried using cb_sink() right after setting the content in my set_content() method, but the custom view stays unchanged. Below is the code for my draw() method for my custom view, as well as my on submit code and set_content(). My first time posting an issue, so let me know if anything is unclear or if you need more information.
impl View for ListView {
    fn draw(&self, printer: &Printer) {
        self.scroll.draw(printer, |printer, i| {
            let item = &self.content[i];
            let right = item.right_text();
            let left = item.left_text();

            let style = if self.selected == i {
                let fg = PaletteColor::Primary.resolve(&printer.theme.palette);
                ColorStyle::new(
                    ColorType::Color(fg),
                    ColorType::Palette(PaletteColor::Highlight))
            }
            else {
                ColorStyle::primary()
            };
            printer.with_color(style, |printer| {
                printer.print_hline((0,0), printer.size.x, " ");
                printer.print((0,0), &left);
                let offset = HAlign::Right.get_offset(right.len(), printer.size.x);
                printer.print((offset,0), &right);
            });
        });
    }
}

let cmd_line = EditView::new()
    .filler(" ")
    .on_submit(|s, command| {
        s.call_on_id("cmd_line", |view: &mut CmdlineView| {
            view.process_command(command);
        });
        s.focus_id("tab_view").expect("FATAL: unable to focus onto id tab_view");
        s.cb_sink().send(Box::new(Cursive::noop)).unwrap();
    });

impl <T: 'static + ListItem> ListView <T> {
    pub fn set_content (&mut self, content: Vec<T>) {
        self.content = content;
        self.cb_sink.send(Box::new(Cursive::noop)).unwrap();
    }
}

Hi, and thanks for the report!
In your case, you might not even need cb_sink in the on_submit: the view should already be re-drawn after any event. As for the set_content function, I would need a bit more context to see how you are calling it.

Hey, thanks for the quick reply. Below is the function that calls set_content:
impl CmdlineView
    fn process_command(&mut self, command: &str) {
        self.clear();
        if self.search_mode {
            let search_term = &command[1..];
            let results = match self.search_engine.search(Some(search_term.to_string())) {
                Ok(results) => results,
                Err(_) => Vec::new(),
            };

            self.call_on_id("video", |view: &mut ListView<_>| {
                view.set_content(results);
            });
        }
        else {
        }
        self.search_mode = false;
        self.enabled = false;
    }
}

The perform_search method just performs some search functions and then calls set_content to set the content of the custom ListView. CmdlineView is a container view I made to group all the associated data of a command line together.
I did a little more digging and it seems like self.call_on_id doesn't seem to be working properly. The program isn't entering that part at all. Is there an issue with the way I'm using call_on_id? Below is the list view being creating in main:
    let a = TabView::new()
        .tab(String::from("video"), ListView::new(b.clone(), cb.clone()).with_id("video"))
        .tab(String::from("channel"), ListView::new(b.clone(), cb.clone()).with_id("channels"))
        .tab(String::from("channel"), ListView::new(b.clone(), cb.clone()).with_id("channels"))
        .with_id("tab_view");

TabView is a custom view which holds the ListView.

That's probably the problem: call_on_id wants the exact type you used with_id on. So it would have to be TabView here, and you'll need to get to the ListView in the closure (or expose the method on TabView).

So I would have to use call_on_id on a Cursive type, then within that closure use call_on_id on TabView, and then within that closure call_on_id on ListView<_>? Correct me if I'm wrong (First rust program ever I'm writing so I may not be understanding everything properly). This is what I've changed it to in CmdlineView:
            self.cb_sink.send(Box::new(|s| {
                s.call_on_id("tab_view", |view: &mut TabView| {
                    view.call_on_id("video", |list_view: &mut ListView<_>| {
                        list_view.set_content(results);
                    });
                });
            })).unwrap();

Still doesn't appear to work. Here's the TabView definitions btw.
pub struct TabView {
    tabs: Vec<Tab>,
    selected: usize,
}

pub struct Tab{
    label: String,
    view: Box<dyn View>,
}

Ah, if you implement TabView as a custom "view group", then you will need to implement a few more methods, like dispatch call_on_any to the children.
If you do that (or if it's already done), you may be able to call .with_id on the child view instead of TabView itself. This way, you could directly call_on_id the child view without explicitly going through the TabView.

Thanks I think I got it working. So by implementing call_on_any in the view group, it forwards any call_on calls to it's children.

Exactly! You can check the implementation from other view groups like LinearLayout:
    fn call_on_any<'a>(
        &mut self,
        selector: &Selector<'_>,
        mut callback: AnyCb<'a>,
    ) {
        for child in &mut self.children {
            child
                .view
                .call_on_any(selector, Box::new(|any| callback(any)));
        }
    }

Thanks :) I think I understand call_on_id now. I will be closing this issue then


Do we need a init system?

See  https://github.com/Yelp/dumb-init

Maybe, probably. Otherwise we likely need some different way of starting apps.
In this current baseimage draft and our current app we use CMD or ENTRYPOINT to start our apps with sh.
According to this: https://pracucci.com/graceful-shutdown-of-kubernetes-pods.html the alpine linux shell, /bin/ash does not propagate signals to its children. So the java app does not see the SIGTERM and thus frameworks like spring boot and camel do not gracefully shut down.
We need to verify this behaviour and find a solution, where dumb-init could be one.
@davidsteinsland

We use the exec form to start Java apps, which means they get pid 1. So there shouldn't be any issues regarding signals, but I'll test anyway.

Verified that heap dump is possible when running the java process with PID > 1.
Fails  with PID 1.  Docker > 1.13 has the --init flag which can be set on the the docker hosts
which will run the container with https://github.com/krallin/tini.
However we still need to include jmap, jstack etc to this baseimage, I think.

Yeah we need this then. Maybe we should set HeapDumpOnOutOfMemoryError and HeapDumpPath as default flags as well. That way NAIS can automate retrieval of these?
Regarding the jmap, jstack etc utils, they are part of the JDK and not the JRE. So we either need to base the baseimages of the JDK (increasing layer size) or include them through some other mechanism.

@gtcno are you planning to add the --init flag when starting docker containers in NAIS? I made a branch adding dumb-init to java-8, however I guess this is not needed if you guys add the tinit functionality.
Then we only need to add the openjdk:8-jdk-alpine to java-8. The difference in layer is 22MB which is not huge (although it does compound in the NAV docker registry). However, being able to make heapdumps is useful. @davidsteinsland thoughts?

It wasn't possible to add the --init flag globally in NAIS, so we add the dumb-init to our baseimages for now.


javax.servlet.ServletContainerInitializer class cast issues when running standalone client

Tomcat: 8.0.5
Java: 1.8.0_05
OS: Mac OSX 10.8.5
After mvn install graphity-ldp then graphity-browser
Deploy war graphity-browser/target/client-1.0.12-SNAPSHOT.war
Starting webapp gives:
org.apache.catalina.startup.ContextConfig.processServletContainerInitializers Failed to process JAR found at URL [/graphity] for ServletContainerInitializers for context with name [{1}]
java.io.IOException: java.lang.ClassCastException: Cannot cast com.sun.jersey.server.impl.container.servlet.JerseyServletContainerInitializer to javax.servlet.ServletContainerInitializer

If someone is having this issue, please try building the project with mvn -Pstandalone package (should produce a .war). That is what NetBeans does and works fine for me.

@ianwdunlop would be awesome if you could give https://hub.docker.com/r/atomgraph/web-client a try :)


Handle conjunctions

We need to be able to handle conjunctions like "the Mississippi and Missouri Rivers".

And lakes also, e.g.,

When a second fault line, the Saint Lawrence rift, formed approximately 570 million years ago,[15] the basis for Lakes Ontario and Erie were created, along with what would become the Saint Lawrence River

From https://en.wikipedia.org/wiki/Great_Lakes

Even with the current set of rules, in the sentence "The Mississippi and Missouri Rivers", both the rivers will be identified although separately. Basically conjunctions like these won't go undetected. Example

hi @Govind9 I'd like to play the system myself once you have it properly refactored. I also want to consider these cases in the context of unit cases.


Random Invalid memory access

I've been getting these Invalid Memory Access errors on and off for a while now. Was hoping 0.21.0 might fix it, but no. I also can't reproduce it (yet), without most of my (relatively large) project included.
I'm more or less looking for directions on what I should look at or try or anything. The following happens when running our tests. But it only happens when running a group of tests, not this specific test by itself. I realize that would indicate that there's some weird state between our tests, but I honestly believe that it's more likely some weird internal crystal state.
Invalid memory access (signal 11) at address 0x0
[4350066123] *CallStack::print_backtrace:Int32 +107
[4349863703] __crystal_sigfault_handler +55
[4355360435] sigfault_handler +35
[140736329518010] _sigtramp +26
[140736327863527] snprintf +32
[4350191284] *Float32#to_s_internal<Pointer(UInt8)>:(Int32 | UInt64) +68
[4350192307] *Float32#to_s<IO::Memory>:Nil +659
[4350487278] *IO::Memory@IO#<<<(Float32 | Int32)>:IO::Memory +62
[4355298551] *Project::Query::AvgFloatCell(Project::Tests::Fakes::Any)@Project::Query::AvgCellHelper(T)#write<IO::Memory, Project::Query::Context>:Nil +119
[4349985628] *assert_output_cell<Project::Query::Cell(Project::Tests::Fakes::Any)+, Float32>:Nil +188

assert_output_cell is doing:
def assert_output_cell(cell : OutputCell, expected)
  io = IO::Memory.new()
  cell.write(io) # this is what causes the cell's float value to be written to IO
  io.to_s.should eq(expected.to_s)
  io.close()
end

This seems to be crashing when a when we call io << some_float in our code. Not sure how that could be related to state in our tests or even accessing released memory or anything like that.
If I change the code a little and add, say puts "doh" inside the constructror of that cell, it now crashes a earlier in that same tests:
[4493552795] *CallStack::print_backtrace:Int32 +107
[4493349975] __crystal_sigfault_handler +55
[4498847315] sigfault_handler +35
[140736329518010] _sigtramp +26
[4493627144] *Slice(T)::new:read_only<Pointer(UInt8), Int32, Bool>:Slice(UInt8) +24
[4493593625] *String#to_slice:Slice(UInt8) +41
[4493594569] *String#to_s<IO::FileDescriptor>:Nil +25
[4493682504] *IO::FileDescriptor@IO#<<<String>:IO::FileDescriptor +24
[4493682437] *IO::FileDescriptor@IO#puts<String>:Nil +21
[4493352953] *puts<String>:Nil +41
[4498785494] *Project::Query::AvgFloatCell(Project::Tests::Fakes::Any)@Project::Query::AvgCellHelper(T)#initialize<Project::Query::LiteralFloatValue(Project::Tests::Fakes::Any), Project::Tests::Fakes::BoolPredicate>:Nil +70
[4498785413] *Project::Query::AvgFloatCell(Project::Tests::Fakes::Any)@Project::Query::AvgFloatCell(T)::new<Project::Query::LiteralFloatValue(Project::Tests::Fakes::Any), Project::Tests::Fakes::BoolPredicate>:Project::Query::AvgFloatCell(Project::Tests::Fakes::Any) +117
[4493471634] ~procProc(Nil)@spec/query/cells/avg_spec.cr:12 +66

It seems to imply my memory is completely messed up.
Could it possibly not be printing the right backtrace (and if so, any way to get the right one?)

Can you provide some code that we can run to reproduce this error?

Ok..that took a while, but I got something. I'm probably doing something silly. But I think it should still not segfault (???)
It's super sensitive. If you inline assert_to_s so that instead of having each test call it, you just do the same inside the test (cells.cells[0].write(IO::Memory.new)), it will pass.  If you don't pass expected (a parameter that isn't even used in this distilled version) ...it'll pass.  If I rename write to to_s and call that instead...it'll pass.
module Test
  struct Cells(T)
    getter cells : Array(Cell(T))
    def initialize(@cells) end
  end

  abstract class Cell(T)
    abstract def write(io : IO)
  end

  class SumInt(T) < Cell(T)
    @total = 0
    def write(io : IO)
      io << @total
    end
  end

  class SumFloat(T) < Cell(T)
    @total = 0_f32
    def write(io : IO)
      io << @total
    end
  end

  class AvgInt(T) < Cell(T)
    @total = 0
    @count = 1

    def write(io : IO)
      io << @total / @count
    end
  end

  class AvgFloat(T) < Cell(T)
    @total = 0_f32
    @count = 1

    def write(io : IO)
      io << @total / @count
    end
  end
end

def builder(cell)
  wrap = Array(Cell(Int32)).new(1)
  wrap << cell
  return Cells(Int32).new(wrap)
end

def assert_to_s(cell : Cell, expected)
  cell.write(IO::Memory.new())
end

require "spec"

include Test

describe "segfault" do
  it "int literal" do
    cells = builder(AvgInt(Int32).new())
    assert_to_s(cells.cells[0], 5)
  end

  it "float literal" do
    num = 90.0_f32
    cells = builder(AvgFloat(Int32).new())
    assert_to_s(cells.cells[0], num)
  end

  it "filtered true int field" do
    cells = builder(AvgInt(Int32).new())
    assert_to_s(cells.cells[0], 2)
    assert_to_s(cells.cells[0], 2.5)
  end

  it "int literal" do
    cells = builder(SumInt(Int32).new())
    assert_to_s(cells.cells[0],  4)
  end

  it "float literal" do
    cells = builder(SumFloat(Int32).new())
    assert_to_s(cells.cells[0], 90.01_f32)
  end
end

/cc @asterite

Still need more info @matiasgarciaisaia ?

Closing as duplicate of #2665 (generics inheritance is still broken)


android scroll is not smoth?

I have a flat list. Inside of that flat list I have added the image zoom view. This is working perfectly in iOS. where as in android when I tried to swipe the page to view the next image the view get stuck.
I have to do lot of swipe to actually swipe the image. I feel that in android the scroll is not smooth.
Please let me know how to add the smooth scroll to view.

@ios-dev-newbie Did you find any solution for this issue ?

@mohammedibrahim  Sorry, I didn't get time to do research on it. But feel free to look at this solutions.
https://github.com/facebook/react-native/issues/9836#issuecomment-379043158. I hope it works fro you. Let me know if you find anything else.

face the same problem, if anyone have solutions, please at me

@marconett that's great! And i just released a new version 2.2.15.

react-native-image-zoom-viewer 2.2.15
react-native-image-pan-zoom 2.1.8

Hi @ascoders , I am still facing this issue in Android, I have a home screen like Instagram, when I scroll down the list it works well in iOS, but in Android when I scroll the list specially, the image on which I am using your code, list does not scroll. I am using the latest version of your package
"react-native-image-pan-zoom": "^2.1.11",
renderToHardwareTextureAndroid is already there in your file mentioned above by @marconett . But no help.
Please assist me.

FYI, setting renderToHardwareTextureAndroid={true} causes Android 6 and Android 7 devices to crash. My image was 2500px by 3000px so maybe that was too much for the GPU to hold in memory in these older phones.

I'm using Animated.View to make smooth scroll, but it seems not perfect in android. Can anyone help?

How did you manage to do with Animated.View

Thanks for the suggestion @marconett, but adding the prop renderToHardwareTextureAndroid={true}  didn't solve the problem. Images zoom and scroll perfectly in a FlatList on IOS but when I put my fingers on the image to scroll on Android, it's not working...
Any suggestions, please?

Thanks for the suggestion @marconett, but adding the prop renderToHardwareTextureAndroid={true}  didn't solve the problem. Images zoom and scroll perfectly in a FlatList on IOS but when I put my fingers on the image to scroll on Android, it's not working...
Any suggestions, please?

I'm using ImageZoom inside a FlatList and I couldn't scroll images on android but working fine on ios. Is their any suggestions please. I changed renderToHardwareTextureAndroid={true} but didnt work fine


Make dev-overview.html clear about options for each host platform

Our homepage for the development environment setup process, http://zulip.readthedocs.io/en/latest/dev-overview.html, should be clear about which options one should look at if one's host machine is OS X, Linux, etc.  The short story is probably that one needs to use Vagrant on Windows, Vagrant and docker work for Mac, and the other options are various ways to install on various Linux platforms.

I would like to take this up

Awesome, go for it!

Hi @zeddmaxx how is this issue going? Are you having any trouble, and do you need help?

@brainwane  I tried to make the dev-overview clear about the options for each host platform by creating a pull request #1829  Can you please let me know where I'm going wrong?


requireAsync: () => import()  SyntaxError: Unexpected token import

💬 Questions and Help
Thanks for your SSR example!
But as soon as i added to main.js
import routes from '../client/routes.js';
with
import loadable from '@loadable/component';
const Cat = loadable(() => import('./Cat.jsx'));
export default [
    {
        path: '/cat',
        exact: true,
        component: Cat
    },
]

immediately get error:
...............................
[nodemon] starting `babel-node src/server/main.js`
/home/....../loadable-components/examples/server-side-rendering/src/client/routes.js:32
  requireAsync: () => import(
                      ^^^^^^
SyntaxError: Unexpected token import

Read carefully the README of the project ?

yes

Search if your answer has already been answered in old issues?

yes, and webpack has been upgraded to "webpack": "4.28.4":
"@babel/cli": "^7.1.2",
    "@babel/core": "^7.3.4",
    "@babel/node": "^7.0.0",
    "@babel/plugin-syntax-dynamic-import": "^7.2.0",
    "@babel/preset-env": "^7.3.4",
    "@babel/preset-react": "^7.0.0",
    "@loadable/babel-plugin": "^5.6.0",
    "@loadable/webpack-plugin": "^5.5.0",
    "babel-loader": "^8.0.4",
    "css-loader": "^2.1.0",
    "mini-css-extract-plugin": "^0.5.0",
    "nodemon": "^1.18.5",
    "npm-run-all": "^4.1.5",
    "webpack": "4.28.4",
    "webpack-cli": "^3.1.2",
    "webpack-dev-middleware": "^3.4.0",
    "webpack-node-externals": "^1.7.2"

May I ask you a more complex example with routes?

babelrc's setting
plugins: [
'@babel/plugin-syntax-dynamic-import',
'@loadable/babel-plugin'
]

This is a major issue of webpack's dependency - acorn.

https://github.com/webpack/webpack/issues/8656
https://npm.community/t/packages-with-peerdependencies-are-incorrectly-hoisted/4794

It, actually, should work with 4.28.4, but something went wrong.
In short - wipe your yarn.lock, should help.

Thank a lot, but it's going hard :(
don't help,
wait for best times

Try to locate your caches(/node_modules/.cache/), or enforce babel-loader to have those - and then wipe without mercy.

The above error went away after I added to "plugins":
"dynamic-import-node"
from airbnb/babel-plugin-dynamic-import-node

Hmm, yes it could be needed but you should not need it. Because on the server, we call requireSync and not requireAsync.

Maybe, but it works

@valorloff: I had the same (or very similar) issue and adding babel-plugin-dynamic-import-node solved my problem as well.

The syntax should just be fine, if you got this issue you are probably doing something wrong. I repeat babel-plugin-dynamic-import-node is not required to run Loadable Components.

You should build your server-side code with webpack, then it will take care of replacing dynamic import by require for you. Most of time this is better to build your code with webpack because you import assets in your code.

did you mean "with babel" ?

if you look at SSR example's:
"scripts": {
    "dev": "nodemon src/server/main.js",

this code unbabelised, perhaps this is why an error
SyntaxError: Unexpected token import  occurs

Nop, build your server-side code with webpack.

https://github.com/smooth-code/loadable-components/blob/master/examples/server-side-rendering/webpack.config.babel.js#L50
There is no dynamic import in the server, just in the client part, builded by webpack for client and for node. Two targets.

You mean replace
externals:
    target === 'node' ? ['@loadable/component', nodeExternals()] : undefined,

with
externals:  ['@loadable/component', nodeExternals()],
?

as soon as you import routes with dynamic imported components on server,
above error occurs. Why I can't use "dynamic-import-node" in this case?

I shown you in the previous comment. But if it works fine with the babel plugin, then it is fine.

no, without dynamic-import-node routes on server with dynamic components don't works. I mean app, based on this SSR example

The example works without the plugin, it is a fact. It also works in all web applications we are building at Smooth Code. So it is an issue on your side. I close it.


Quick start installation instructions

On a call with @aimalz and @drewoldag, we observed that it would be nice to have a "quick start" section to the installation instructions for new users that want to hit the ground running.
Would also be a good exercise to make sure we can even condense a minimal set of installation instructions (or if installation process is too complicated for this).

Looking to try using RAIL for the first time in a while. Would it be useful for me to take this on as a new user and record what the minimum setup I need to get running would be?

Absolutely, that would be fantastic.

I just wanted to leave a comment here summarizing a discussion that's been happening outside of GitHub, the consensus of which is that we actually want more than one quick start guide to which users will be directed from an initial starting point outlining the main ways we expect people to use RAIL, specifically providing different instructions for those who anticipate jumping straight to scalable pipelines versus those who will start by running exploratory tests in notebooks.

I can take it from an exploratory notebook perspective since that's my interest. Should we break this issue into different ones @aimalz?

Also, I put a zipped tar file on s3df with test versions of the various rail packages as laid out above.~echarles/xfer/rail_stuff.tgzHave a look.  For the new packages I used the Lincc package template, but removed some stuff (docs & pylintrc files & a few src files that didn’t match up with typical rail usage) & put a few things in pyproject.toml On May 22, 2023, at 1:00 PM, Eric Charles @.> wrote:Have a look at my post in #desc-pz-rail about basic idea on how to get started. On May 22, 2023, at 12:41 PM, Bryce Kalmbach @.> wrote:
I can take it from an exploratory notebook perspective since that's my interest. Should we break this issue into different ones @aimalz?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

While we're at this, we should follow these instructions to ensure pz-rail and pz-rail-hub have non-blank project descriptions on PyPI.

@eacharles, @sschmidt23 - Alex and I were just outlining some quickstart instructions for command line users. How do we envision users ultimately using rail_pipelines?
eg, I'm trying to run the goldenspike pipeline in rail_pipelines, so I:

$ python -m site
copy the (path-to-site-packages) that gets printed
$ ceci (path-to-site-packages)/rail/pipelines/examples/goldenspike/goldenspike.py

Is there a more streamlined route for the user to take? Is there (or will there be) some kind of command-line-accessible notion of rail's path?

So, that I was imanging was that rail_pipelines would be a repository for two types of things.

python pipeline files, that allow you do load a pipeline into a python session or a notebook easily, run a few tests, and export the configuration to a yaml file
python yaml files for some standard pipelines, that you can use to run a notebook with ceci

For the first I think that there is an example notebook in rail_pipelines  Basically you can do
<usual conda setup>
pip install pz-rail-pipelines
<Open a notebook, import a pipeline, play around with it, and save the config to pipe.yml>
ceci pipe.yml --input <some_big_file> --outdir <output>

for the second, I think you could do something like this:
git clone https://github.com/LSSTDESC/rail_pipelines.git
cd rail_pipelines
<usual conda setup>
pip install -e .
ceci src/rail/configs/goldenspike.yml --input <some_file> --outdir <some_dir>

Of course you could try and use python -m site to run with pip install pz-rail-pipelines but I would recommend doing as source install so that you can edit the pipeline config file  as needed.
We need to decide now we want store the yml files for the pipelines.   I.e., do they go somewhere in the src directory tree and get installed with the package.

Does this work:
mamba create -y -n rail python=3.10 h5py healpy scikit-learn somoclu numpy scipy astropy==5.3
conda activate rail
git clone <rail_hub>
cd rail_hub
pip install -e .

On Jun 13, 2023, at 11:11 AM, Olivia R. Lynn @.***> wrote:
Documenting some trouble (plus solutions) I ran into when installing RAIL locally on a summer research student's laptop (an M1 Mac using Miniforge) -
The steps that ultimately worked:
conda create -y -n rail python=3.10 h5py healpy scikit-learn somoclu
conda activate rail
pip install pz-rail-hub
conda install numpy
conda install scipy
pip install astropy==5.3
Reasons:
conda install h5py -> an issue with tables
conda install healpy -> issue with healpy from pip
pip install cmake -> arose from pip having trouble installing xgboost, but only needed to be run the one time
conda install numpy scipy -> assuming pz-rail-hub messes with the dependencies grabbed from prev conda scikit-learn. I don't fully understand but this was necessary when double checking these install instructions on her machine
upgrade astropy from 5.1 to 5.3 -> came from an issue running goldenspike: concatenate() got an unexpected keyword arg ‘dtype’
—
Reply to this email directly, view it on GitHub https://github.com/LSSTDESC/RAIL/issues/328#issuecomment-1589802979, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADRIGIW3DK4IMSIZBNOWHCTXLCUOBANCNFSM6AAAAAAWZGZB7U.
You are receiving this because you were mentioned.


tws earphone connect to iphone without mfi?

It seems for ios platform, the device that wants to connect to iPhone must be mfi certified. However, I read from other places (https://apple.stackexchange.com/questions/393007/who-needs-to-join-the-apple-mfi-program) saying for ble 4.0+ device, mif is not required. Recently I wanted to develop an ios app that can manipulate a tws earphone. Just send some simple message to the earphone. I wonder if there is a react-native module that can achieve this without mfi, so I don't need to set up UISupportedExternalAccessoryProtocols because the earphone is not mfi certified.

BLE is not part of the MFi process, that is correct.  No, this library is specific for MFi, if you want to use BLE you want to use another library.


Correct unbranched alkane SMARTS to match the description given

Must restrict to only carbon and allow for terminal alkanes

@greglandrum Can you take another look at this?

@greglandrum Can you take another look at this?

@levineds sorry I was so slow there. I just made a PR against your branch with my very minor suggested change and a merge to the current status of master. If you merge that PR, this one will automatically update and I will approve and merge it.

Thanks, Greg. Merged now.

Thanks, Greg. Merged now.

Great. I will merge this after the CI builds finish

Thanks for the contribution @levineds


Eks cluster fix first deploy due to OIDC

what

set a non-empty value for eks_cluster_identity_oidc_issuer as the default for module.eks (remote-state module).

why

that value must not be empty when passed to the cloudposse/eks-iam-role/aws module for aws-ebs-csi-driver and vpc-cni addons

that will never exists on first deployment because the component itself create the OIDC provider

references

#797

This fix was one of two or three methods I could have implemented as a fix. If this is rejected I can provide another solution.


test_gpu_write_parquet_simple failure on gpuCI

Over in https://github.com/dask/dask/pull/9388 we observed dask/dataframe/io/tests/test_parquet.py::test_gpu_write_parquet_simple failed with
09:49:43 E           MemoryError: Parquet data was larger than the available GPU memory!
09:49:43 E
09:49:43 E           See the notes on split_row_groups in the read_parquet documentation.
09:49:43 E
09:49:43 E           Original Error: std::bad_alloc
09:49:43
09:49:43 /opt/conda/envs/dask/lib/python3.9/site-packages/dask_cudf/io/parquet.py:265: MemoryError

in this gpuCI build

Full treacback:
09:49:43 ________________________ test_gpu_write_parquet_simple _________________________
09:49:43 [gw2] linux -- Python 3.9.13 /opt/conda/envs/dask/bin/python
09:49:43
09:49:43 cls = <class 'dask_cudf.io.parquet.CudfEngine'>
09:49:43 fs = <fsspec.implementations.local.LocalFileSystem object at 0x7ff4bc75f1f0>
09:49:43 pieces = [('/tmp/pytest-of-jenkins/pytest-589/popen-gw2/test_gpu_write_parquet_simple0/part.0.parquet', None, None)]
09:49:43 columns = ['a', 'b', '__null_dask_index__'], index = ['__null_dask_index__']
09:49:43 categories = [], partitions = [], partitioning = None
09:49:43 schema = __null_dask_index__: int64 not null
09:49:43 a: string not null
09:49:43 b: string not null
09:49:43 -- schema metadata --
09:49:43 pandas: '{"index_columns": ["__null_dask_index__"], "column_indexes": [{"' + 553
09:49:43 open_file_options = None
09:49:43 kwargs = {'dataset': {'format': <ParquetFileFormat read_options=<ParquetReadOptions dictionary_columns=set() coerce_int96_timestamp_unit=ns>>, 'partitioning': 'hive'}, 'filters': None, 'read': {'open_file_options': {}}}
09:49:43 read_columns = None, ignored = set(), strings_to_cats = False
09:49:43 read_kwargs = {'open_file_options': {}}, check_file_size = 500000000
09:49:43 paths = ['/tmp/pytest-of-jenkins/pytest-589/popen-gw2/test_gpu_write_parquet_simple0/part.0.parquet']
09:49:43 rgs = [None]
09:49:43
09:49:43     @classmethod
09:49:43     def read_partition(
09:49:43         cls,
09:49:43         fs,
09:49:43         pieces,
09:49:43         columns,
09:49:43         index,
09:49:43         categories=(),
09:49:43         partitions=(),
09:49:43         partitioning=None,
09:49:43         schema=None,
09:49:43         open_file_options=None,
09:49:43         **kwargs,
09:49:43     ):
09:49:43
09:49:43         if columns is not None:
09:49:43             columns = [c for c in columns]
09:49:43         if isinstance(index, list):
09:49:43             columns += index
09:49:43
09:49:43         # Check if we are actually selecting any columns
09:49:43         read_columns = columns
09:49:43         if schema and columns:
09:49:43             ignored = set(schema.names) - set(columns)
09:49:43             if not ignored:
09:49:43                 read_columns = None
09:49:43
09:49:43         if not isinstance(pieces, list):
09:49:43             pieces = [pieces]
09:49:43
09:49:43         # Extract supported kwargs from `kwargs`
09:49:43         strings_to_cats = kwargs.get("strings_to_categorical", False)
09:49:43         read_kwargs = kwargs.get("read", {})
09:49:43         read_kwargs.update(open_file_options or {})
09:49:43         check_file_size = read_kwargs.pop("check_file_size", None)
09:49:43
09:49:43         # Wrap reading logic in a `try` block so that we can
09:49:43         # inform the user that the `read_parquet` partition
09:49:43         # size is too large for the available memory
09:49:43         try:
09:49:43
09:49:43             # Assume multi-piece read
09:49:43             paths = []
09:49:43             rgs = []
09:49:43             last_partition_keys = None
09:49:43             dfs = []
09:49:43
09:49:43             for i, piece in enumerate(pieces):
09:49:43
09:49:43                 (path, row_group, partition_keys) = piece
09:49:43                 row_group = None if row_group == [None] else row_group
09:49:43
09:49:43                 # File-size check to help "protect" users from change
09:49:43                 # to up-stream `split_row_groups` default. We only
09:49:43                 # check the file size if this partition corresponds
09:49:43                 # to a full file, and `check_file_size` is defined
09:49:43                 if check_file_size and len(pieces) == 1 and row_group is None:
09:49:43                     file_size = fs.size(path)
09:49:43                     if file_size > check_file_size:
09:49:43                         warnings.warn(
09:49:43                             f"A large parquet file ({file_size}B) is being "
09:49:43                             f"used to create a DataFrame partition in "
09:49:43                             f"read_parquet. This may cause out of memory "
09:49:43                             f"exceptions in operations downstream. See the "
09:49:43                             f"notes on split_row_groups in the read_parquet "
09:49:43                             f"documentation. Setting split_row_groups "
09:49:43                             f"explicitly will silence this warning."

09:49:43                 )
09:49:43             open_file_options = {}
09:49:43
09:49:43         # Multiple sources are passed as a list. If a single source is passed,
09:49:43         # wrap it in a list for unified processing downstream.
09:49:43         if not is_list_like(filepath_or_buffer):
09:49:43             filepath_or_buffer = [filepath_or_buffer]
09:49:43
09:49:43         # a list of row groups per source should be passed. make the list of
09:49:43         # lists that is expected for multiple sources
09:49:43         if row_groups is not None:
09:49:43             if not is_list_like(row_groups):
09:49:43                 row_groups = [[row_groups]]
09:49:43             elif not is_list_like(row_groups[0]):
09:49:43                 row_groups = [row_groups]
09:49:43
09:49:43         # Check columns input
09:49:43         if columns is not None:
09:49:43             if not is_list_like(columns):
09:49:43                 raise ValueError("Expected list like for columns")
09:49:43
09:49:43         # Start by trying construct a filesystem object, so we
09:49:43         # can apply filters on remote file-systems
09:49:43         fs, paths = ioutils._get_filesystem_and_paths(filepath_or_buffer, **kwargs)
09:49:43
09:49:43         # Use pyarrow dataset to detect/process directory-partitioned
09:49:43         # data and apply filters. Note that we can only support partitioned
09:49:43         # data and filtering if the input is a single directory or list of
09:49:43         # paths.
09:49:43         partition_keys = []
09:49:43         partition_categories = {}
09:49:43         if fs and paths:
09:49:43             (
09:49:43                 paths,
09:49:43                 row_groups,
09:49:43                 partition_keys,
09:49:43                 partition_categories,
09:49:43             ) = _process_dataset(
09:49:43                 paths,
09:49:43                 fs,
09:49:43                 filters=filters,
09:49:43                 row_groups=row_groups,
09:49:43                 categorical_partitions=categorical_partitions,
09:49:43             )
09:49:43         elif filters is not None:
09:49:43             raise ValueError("cudf cannot apply filters to open file objects.")
09:49:43         filepath_or_buffer = paths if paths else filepath_or_buffer
09:49:43
09:49:43         filepaths_or_buffers = []
09:49:43         if use_python_file_object:
09:49:43             open_file_options = _default_open_file_options(
09:49:43                 open_file_options,
09:49:43                 columns,
09:49:43                 row_groups,
09:49:43                 fs=fs,
09:49:43             )
09:49:43         for i, source in enumerate(filepath_or_buffer):
09:49:43             tmp_source, compression = ioutils.get_reader_filepath_or_buffer(
09:49:43                 path_or_data=source,
09:49:43                 compression=None,
09:49:43                 fs=fs,
09:49:43                 use_python_file_object=use_python_file_object,
09:49:43                 open_file_options=open_file_options,
09:49:43                 **kwargs,
09:49:43             )
09:49:43
09:49:43             if compression is not None:
09:49:43                 raise ValueError(
09:49:43                     "URL content-encoding decompression is not supported"
09:49:43                 )
09:49:43             if isinstance(tmp_source, list):
09:49:43                 filepath_or_buffer.extend(tmp_source)
09:49:43             else:
09:49:43                 filepaths_or_buffers.append(tmp_source)
09:49:43
09:49:43         # Warn user if they are not using cudf for IO
09:49:43         # (There is a good chance this was not the intention)
09:49:43         if engine != "cudf":
09:49:43             warnings.warn(
09:49:43                 "Using CPU via PyArrow to read Parquet dataset. "
09:49:43                 "This option is both inefficient and unstable!"
09:49:43             )
09:49:43             if filters is not None:
09:49:43                 warnings.warn(
09:49:43                     "Parquet row-group filtering is only supported with "
09:49:43                     "'engine=cudf'. Use pandas or pyarrow API directly "
09:49:43                     "for full CPU-based filtering functionality."
 We only
09:49:43                 # check the file size if this partition corresponds
09:49:43                 # to a full file, and `check_file_size` is defined
09:49:43                 if check_file_size and len(pieces) == 1 and row_group is None:
09:49:43                     file_size = fs.size(path)
09:49:43                     if file_size > check_file_size:
09:49:43                         warnings.warn(
09:49:43                             f"A large parquet file ({file_size}B) is being "
09:49:43                             f"used to create a DataFrame partition in "
09:49:43                             f"read_parquet. This may cause out of memory "
09:49:43                             f"exceptions in operations downstream. See the "
09:49:43                             f"notes on split_row_groups in the read_parquet "
09:49:43                             f"documentation. Setting split_row_groups "
09:49:43                             f"explicitly will silence this warning."
09:49:43                         )
09:49:43
09:49:43                 if i > 0 and partition_keys != last_partition_keys:
09:49:43                     dfs.append(
09:49:43                         cls._read_paths(
09:49:43                             paths,
09:49:43                             fs,
09:49:43                             columns=read_columns,
09:49:43                             row_groups=rgs if rgs else None,
09:49:43                             strings_to_categorical=strings_to_cats,
09:49:43                             partitions=partitions,
09:49:43                             partitioning=partitioning,
09:49:43                             partition_keys=last_partition_keys,
09:49:43                             **read_kwargs,
09:49:43                         )
09:49:43                     )
09:49:43                     paths = rgs = []
09:49:43                     last_partition_keys = None
09:49:43                 paths.append(path)
09:49:43                 rgs.append(
09:49:43                     [row_group]
09:49:43                     if not isinstance(row_group, list)
09:49:43                     and row_group is not None
09:49:43                     else row_group
09:49:43                 )
09:49:43                 last_partition_keys = partition_keys
09:49:43
09:49:43             dfs.append(
09:49:43                 cls._read_paths(
09:49:43                     paths,
09:49:43                     fs,
09:49:43                     columns=read_columns,
09:49:43                     row_groups=rgs if rgs else None,
09:49:43                     strings_to_categorical=strings_to_cats,
09:49:43                     partitions=partitions,
09:49:43                     partitioning=partitioning,
09:49:43                     partition_keys=last_partition_keys,
09:49:43                     **read_kwargs,
09:49:43                 )
09:49:43             )
09:49:43             df = cudf.concat(dfs) if len(dfs) > 1 else dfs[0]
09:49:43
09:49:43             # Re-set "object" dtypes align with pa schema
09:49:43             set_object_dtypes_from_pa_schema(df, schema)
09:49:43
09:49:43             if index and (index[0] in df.columns):
09:49:43                 df = df.set_index(index[0])
09:49:43             elif index is False and df.index.names != (None,):
09:49:43                 # If index=False, we shouldn't have a named index
09:49:43                 df.reset_index(inplace=True)
09:49:43
09:49:43         except MemoryError as err:
09:49:43 >           raise MemoryError(
09:49:43                 "Parquet data was larger than the available GPU memory!\n\n"
09:49:43                 "See the notes on split_row_groups in the read_parquet "
09:49:43                 "documentation.\n\n"
09:49:43                 "Original Error: " + str(err)
09:49:43             )
09:49:43 E           MemoryError: Parquet data was larger than the available GPU memory!
09:49:43 E
09:49:43 E           See the notes on split_row_groups in the read_parquet documentation.
09:49:43 E
09:49:43 E           Original Error: std::bad_alloc
09:49:43
09:49:43 /opt/conda/envs/dask/lib/python3.9/site-packages/dask_cudf/io/parquet.py:265: MemoryError

cc @charlesbluca @rjzamora

Also popped up  in https://github.com/dask/dask/pull/9390 too. So this seems consistent

I'll try to figure out what is going on here. Does gpuci uses cudf/dask_cudf nightly?

Thanks @rjzamora! Yes, it should install those packages from the RAPIDS nightly channel

This seem to have been fixed. Thank you, mystery person or machine.


[Bug] Loading component breaks when strategy is 'overlay'

Do you want to request a feature or report a bug?
Bug
Bug Report
Using strategy overlay for the loading component breaks the app with following issue as shown in image, it was working before i updated to<EMAIL_ADDRESS>Screenshots or link to CodePen/Plunker/JSfiddle

What is the expected behavior?
To just work or at least not blow up my app.
What is the motivation / use case for changing the behavior?
It's a bug.
Which version of Angular and Material, and which browser and OS does this issue affect?
Did this work in previous versions of Angular / Material? Yes

Other information

If i remove the loading component strategy, it uses the default which is replace, that's my current workaround.

In the error image note that for a few transforms, for example the 75% one tries to transform: rotateX(...) rotate(...), note the last rotate, shouldn't be rotateY or rotateZ?

Try node 6.11.x. V9 isn't supported

So this is an issue with node version?

Possibly just caught my eye. Test with the supported version and see if that helps

No difference except i had to re-build deps.

This CSS keyframe comes directly from the mat-progress-spinner so im not sure if there is much we can do.. we havent seen this error before so if you can create a plnkr or stackblitz to replicate it it would be appreciated to try and debug it.

Soo should i transfer this bug into Material repo?

Currently using overlay in one of my projects will not hide the passed into ng-template through transclusion

I have exactly the same problem. I did not find a solution. I'm waiting for a post update.

Can you both make a Plunker or Stackblitz so we can test?

So i actually think we fixed this a while back because i cant replicate it
https://github.com/Teradata/covalent/pull/973/files#diff-0d22f546d39ab49964181c6d6344e8a8R209
Can you all install the nightly build to test it?

@emoralesb05  You can see my problem in the doc site actually. In the [tdLoading] until template syntax with booleans section, the mask doesnt overlay the elements inside of ng-template

Ah, thats actually a change we did.. it only adds a background if its circle.. if its linear then it behaves that way since we wanted to follow the loading MD spec a bit more.

@luchillo17 can you try our latest release? this should probably be fixed in that one.

@emoralesb05 my bad, missed that point in the rc.0 release

for my part the latest version fixed the bug. Thx all

Awesome, thanks for letting us know @KerMiiTT


Persian translation

Hi,
I noticed that this great player didn't have a Persian translation yet. So in this pull request, I translated MediaElement to Persian.
Best regards,
WmaTeam

Coverage remained the same at 73.832% when pulling f9ac8c52fcef7db07a1bc3acfa047cea2337855a on wmateam:i18n_fa into 460cc41475baa203a78374eb75e40c20ae60cbc6 on mediaelement:master.

Thanks. Just don't perform any changes on the build folder, please. It may cause conflicts when trying to running grunt

Oh sorry. I was looking at the past commit. Checking this right now

PR merged. Thanks. Please star both https://github.com/mediaelement/mediaelement and https://github.com/mediaelement/mediaelement-plugins to continue improving the package and giving it more popularity; also tell your friends/coworkers/etc. that have a GitHub account to do the same to support the project, if you don't mind. It would be greatly appreciated it.

Thank you my friend.


Add an effectful example

I am looking for how purscript effect system could work with vue setup hook in a non intrusive way.

My guess is that vue "ref" function is effectful, so this gonna be helpful https://book.purescript.org/chapter10.html#effectful-functions

https://github.com/jonasbuntinx/purescript-react-realworld/ can be a source of inspiration of how to deal with hooks in the purescript context

https://gist.github.com/i-am-the-slime/eb0f9168e17277b4ff37de25dfe6816e

Effectful example in POC: 4d91e4c831b239fb5228afdca0a6e541c79a456a

My guess is that vue "ref" function is effectful, so this gonna be helpful https://book.purescript.org/chapter10.html#effectful-functions

The ref function is not side-effect free because it uses reactive, which uses a effectful function mutating reactiveMap.

Fixed on 8f0bd65f74990ab555f93222bc4f52518daf64fa, changing Ref logic, it will be just a reference to the reactive object to be used inside Effect monad.

There still a problem, how set/get would know how to address the ref

I'm still considering this composition api approach, I'm seeing that composition api hides a lot of side-effects


Building a multipartstream from an uri stream fails to include the uri content due to the uri stream not being seekable.

Environment: Tested with PHP 7.0.14 and PHP 5.6.29 (installed via brew) on macOS Sierra (10.12.2).
When using Mailguns SDK which uses the multipart-stream-builder I ran into the problem of local file attachments being handled correctly by the multipart stream builder, however uri attachments did not.
Looking at the source code the cause of this seems to be the fact that the stream generated from an URI is not seekable, which causes (string) $data['contents'] at https://github.com/php-http/multipart-stream-builder/blob/master/src/MultipartStreamBuilder.php#L98 to return en empty string due to the stream's to string method:
public function __toString()
    {
        try {
            $this->seek(0);
            return (string) stream_get_contents($this->stream);
        } catch (\Exception $e) {
            return '';
        }
    }

To reproduce the issue:
    public function testMultipartStreamBuilderWithURI()
    {
        $builder = new \Http\Message\MultipartStream\MultipartStreamBuilder;
        $url = 'https://assets-cdn.github.com/images/modules/site/home-hero.jpg';
        $stream = fopen($url, 'r');
        $builder->addResource(basename($url), $stream);
        $body = $builder->build();
        $contents = $body->getContents();

        $uriContents = file_get_contents($url);
        $this->assertContains($uriContents, $contents);
    }

I am not sure if the psr7 stream method __toString should be altered, or alternatively one could change the build method (https://github.com/php-http/multipart-stream-builder/blob/master/src/MultipartStreamBuilder.php#L98) to something along the lines of:
if ($data['contents']->isSeekable())
{
    $streams .= (string) $data['contents'];
}
else {
    $streams .= $data['contents']->getContents();
}

Thank you for a great issue. You are correct. There is currently no support for non-seekable streams. Diactoros will throw an exception and Guzzle will give an empty body.
Would you mind creating a PR with your test and solution?

Not at all, happy to contribute.

Fixed by #27


Cannot set the who_can_join with "Anyone can Ask"

I am trying to set the Anyone can ask flag in the Join the group permission. But there is no way to set that in GAM.

Correct command should be:
gam update group  who_can_join can_request_to_join
have you tried that?

That command sets the field to "Anyone in the organization can ask"

There are five choices in that field and only four commands.
Public  -> anyone_can_join
Anyone in the organization  -> all_in_domain_can_join
Only invited users  -> invited_can_join
Anyone can ask  -> ??
Anyone in the organization can ask  -> can_request_to_join

Marcelo,
The API describes four possible values:
https://developers.google.com/admin-sdk/groups-settings/v1/reference/groups#resource
Scroll down to whoCanJoin
Both of these choices are reported as can_request_to_join in the API
Anyone can ask -> ??
Anyone in the organization can ask -> can_request_to_join
Ross
On Wed, Feb 8, 2017 at 3:20 PM, marcelo-at-medialocate <
<EMAIL_ADDRESS>wrote:

There are five choices in that field and only four commands.
Public -> anyone_can_join
Anyone in the organization -> all_in_domain_can_join
Only invited users -> invited_can_join
Anyone can ask -> ??
Anyone in the organization can ask -> can_request_to_join
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jay0lee/GAM/issues/427#issuecomment-278495310, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIU8L0vY7NccjDKm5f7yFhz_4dJ8O59Hks5rak2rgaJpZM4L7UOz
.

--
Ross Scroggs
<EMAIL_ADDRESS>

you may need to make groups public to the Internet in your global groups settings for this to work:
https://support.google.com/a/answer/167097


Wmiinet util

Unmanaged APIs for wminet-util.dll
Summary
Documents the functions found in WMINet_Utils.dll. Preview pages are found at https://review.docs.microsoft.com/en-us/dotnet/framework/unmanaged-api/wmi/?branch=pr-en-us-3601.
Suggested Reviewers
//cc @mairaw, @AlexGhiondea, @danmosemsft

@mairaw, I've addressed all of your comments. Thanks.


Sign-in, sign-up and Create campaign buttons/links not working.

Needs API development.

Now the links will function as intended.


phone otp code resend not working

Describe the bug
A clear and concise description of what the bug is.
When I try to resend the otp code using the following code it gives this error:
error:
flutter: verification: AuthException(message: {"code":"unexpected_failure","message":"Unable to process request"}, statusCode: 500, errorCode: null)
code:
onPressed: () async {
                  try {
                    final response = await supabase.auth.resend(
                      phone: widget.phoneNumber,
                      type: OtpType.sms,
                    );

                    print('response: $response');
                  } catch (e) {
                    print('verification: $e');
                  }
                },

Expected behavior
It should resend the code but it gives an unexpected error
Version (please complete the following information):
├── supabase_flutter 2.6.0
│   ├── supabase 2.3.0
│   │   ├── functions_client 2.3.2
│   │   ├── gotrue 2.8.4
│   │   ├── postgrest 2.1.4
│   │   ├── realtime_client 2.2.1
│   │   ├── storage_client 2.0.3

Are there any auth logs in the Supabase dashboard? A 500 status code is uncommon and more often not a client issue.

It was a problem with my phone otp provider and I have fixed it. Apparently my phone number was blocked by the provider for a short time for asking to resend the code too much.


MapRoulette integration seems to be storming challenge-fetches

Description
While testing for the 2.3 release we came upon a showstopper: Chrome literally ran out of resources while the MR integration was running.
<IP_ADDRESS>-1715031385843.log

Screenshots
see above.
Version
2.3.0-pre.0
What browser are you seeing the problem on? What version are you running?
Chrome v124
The OS you're using
MacOS 14.4.1
Steps to reproduce
Click the MapRoulette integration on.
Pan around a bit, then use the geocoder to find a completely new place to go and head there (Not sure if this is necessary)?
Observe the console log after you navigate away- there will be TONS of fetches being complained about.
The browser URL at the time you encountered the bug
http://<IP_ADDRESS>:8080/#map=17.00/42.37817/-71.11120&background=Bing&datasets=fbRoads,msBuildings&disable_features=boundaries
(this is from after navigating away from Seattle, where MR tasks weren't showing up)
The auto-detected useragent string for your browser (leave blank if you're manually filling this form out)
No response

#1410 fixed this right?

Right you are, closing.


Update Packages for v11

Packaged data does load in the new version, we'll need to update the layout and loading methods.

Fixed as of v0.8.3


Converted rest handler for explain from JS to C++.

@danielhlarkin Jenkins failed: http://c1.triagens-gmbh.zz:8080/job/arangodb-ci/job/PR-2907/2/artifact/FAILED_test_cluster_community_mmfiles_linux_shell_client.log

@fceller I think the tests are failing for reasons unrelated to the changes now. The tests which fail on Jenkins pass locally. One is due to cluster timeout and the other is because a collection truncate fails (I would guess also related to cluster traffic). Could you let me know if anything looks suspicious and, if not, re-run?

@danielhlarkin agreed

LGTM


feat: add howardjohn/kubeconfig-proxy

howardjohn/kubeconfig-proxy: Tunnel Kubectl requests over kubectl proxy to avoid round trips to API server
$ aqua g -i howardjohn/kubeconfig-proxy

Check List

[x] Read CONTRIBUTING.md

[x] Read OSS Contribution Guide

[x] All commits are signed

This repository enables Require signed commits, so all commits must be signed

[x] Avoid force push
[x] Do only one thing in one Pull Request
[x] Execute cmdx s to scaffold code
[x] Install and execute the package and confirm if the package works well

How to confirm if this package works well
Reviewers aren't necessarily familiar with this package, so please describe how to confirm if this package works well.
Please confirm if this package works well yourself as much as possible.
Command and output
root@786bfb502949:/workspace# kubeconfig-proxy --help
kubeconfig-proxy is a tool to open a persistent tunnel to an api server to improve kubectl speed

Usage:
  kubeconfig-proxy [command]

Available Commands:
  completion  Generate the autocompletion script for the specified shell
  help        Help about any command
  proxy       register the current context to be proxied
  server      start proxy server

Flags:
  -h, --help   help for kubeconfig-proxy

Use "kubeconfig-proxy [command] --help" for more information about a command.

If files such as configuration file are needed, please share them.
Reference

https://github.com/howardjohn/kubeconfig-proxy/blob/main/README.md

Thank you always!

v4.333.0 is out 🎉
https://github.com/aquaproj/aqua-registry/releases/tag/v4.233.0


Codelens text is not visible unless mouse is clicked in the document

VSCode Version:
Version: 1.52.0
Commit: 940b5f4bb5fa47866a54529ed759d95d09ee80be
Date: 2020-12-10T22:43:50.597Z
Electron: 9.3.5
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.4.0-54-generic snap

OS Version:
Operating System: KDE neon 5.20
KDE Plasma Version: 5.20.4
KDE Frameworks Version: 5.76.0
Qt Version: 5.15.2
Kernel Version: 5.4.0-54-generic
OS Type: 64-bit
Processors: 16 × AMD Ryzen 7 3800X 8-Core Processor
Memory: 62,8 GiB of RAM
Graphics Processor: AMD VERDE

Codelens text is not shown unless mouse is clicked. Moving mouse around has no effect.
Here is the screencast I took:

Steps to Reproduce:
Actually it was working as expected untill Vscode became unresponsive and I terminated it via system monitor/process table by killing all instances of code. When I restarted it, release notes for 1.52.0 was on display. It behaved as in the gif then on, even after several reloads and computer restart. I checked all codelens related settings on, still no change.
Here is the CodelensProvider:
import { CancellationToken, CodeLens, CodeLensProvider, EventEmitter, Range, TextDocument } from 'vscode';

export class CodelensProvider implements CodeLensProvider {
  private _onDidChangeCodeLenses: EventEmitter<void> = new EventEmitter<void>();

  public constructor() {
    this._onDidChangeCodeLenses.fire();
  }

  public provideCodeLenses(document: TextDocument, token: CancellationToken): CodeLens[] | Thenable<CodeLens[]> {
    const lenses = [];
    for (let i = 0; i < 5; i++) {
      const range = new Range(i, i, i, i);
      lenses.push(new CodeLens(range));
    }
    return lenses;
  }

  public resolveCodeLens(codeLens: CodeLens, _token: CancellationToken) {
    codeLens.command = {
      title: `Example Code Lens`,
      tooltip: "Tooltip provided by sample extension",
      command: "codelens-sample.codelensAction",
    };
    return codeLens;
  }
}

And I registered it for all languages on activation:
const codelensProvider = new CodelensProvider(new Range(0, 0, 0, 0));
languages.registerCodeLensProvider("*", codelensProvider);

Does this issue occur when all extensions are disabled?:
Yes, nothing changes.

Codelens text is not shown unless mouse is clicked. Moving mouse around has no effect.

Cannot reproduce. Works for me without mouse interaction and btw it is very, very unlicked due to the mouse because there no such code like "update after click". Are you sure you extension is responsive and not blocked by another extension which then would prevent resolvingCodeLens from being called successfully?

@jrieken Hi,
Here is the development repo for the code I use: https://github.com/snnsnn/vscode-aid-extension. It has launch script to run in debug mode and npm scripts, I also added aid-1.0.0.vsix to repo in case you want to try it.
What extension does is, listens for onDidChangeTextEditorSelection  and updates itself accordingly to be above the active line. As you see in the gif below, codelens is not visible after line change, unless focus is moved to another window (firefox) and returned back.

So, this is not good: https://github.com/snnsnn/vscode-aid-extension/blob/6aae721c8ab2236b8cc5c63bc0d4be0c44fef710/src/CodelensProvider.ts#L28
It seems that your provider doesn't resolve code lenses in some cases and that's a problem. It should esp not rely on the active editor to resolve code lenses because code lenses can be resolved without the document showing in an editor.
Please change your provider so that it always returns a valid code lens and then check if your problem still exists


vanilla-extract 🍰

Thank you so much for your article and repo, you mentioned that you wanted to extend the tutorial to use vanilla-extract - is there any update on that? 😄 I'm setting up a component lib that adheres to a design system that I have and I wanted to build the lib with vanilla-extract or maybe even StyleX. I'm just curious as a complete library-developer newbie what are the considerations that I have to think about if i wanted to integrate those CSS-in-JS solutions?
Thanks again!
Edit:
I'm also curious about serving fonts via the component library, in my case the library is very opinionated - not like other generic libraries such as MUI where you bring your own font family.

I still want to try vanilla extract in this context, I think it should be relatively simple to do. Maybe I can find some time for it in the next weeks.
Regarding the fonts, my current approach is to ship a global css file with my component library. This is also the place where I add some normalize styles. I build the styles in a different build step like so:
"build": "tsc --p ./tsconfig-build.json && vite --config ./vite-build.config.ts build && vite --config ./vite-build-css.config.ts build --emptyOutDir false",

You can look at this project (the "components" package in the monorepo) to find out more: https://github.com/receter/sys42
The project/package is experimental and is still under heavy development. I am planing to use this as a base for the design system/component library we use at Userbrain.


Remove check on message ordering

#24

I'm putting this PR in the fridge. It takes very careful logic to implement this without breaking mandatory message ordering.


add Windows and macOS CI jobs for prototype tests

Closes #5550.
Apart from adding Windows and macOS jobs, this also migrates the prototype tests from CircleCI to Github Actions since CircleCI has no convenient way to setup a Python environment on all three platforms. There is the Python orb, but it is not supported on Windows. Thus, we would need a rather complicated workflow (think current regular unittest setup, but simplified a little) with very little gain.
The prototype tests don't require a GPU or a beefy machine and thus the OSS version of Github Actions is sufficient. As an added benefit, Github Actions is free for OSS projects and thus helps keeping the CI costs down (see #5479).

@pmeier can you add caching installed deps to speed up tests when re-run

Yup, can do. Still, since we can only cache third-party dependencies other than  PyTorch core, we will shave off very little. The most time is spent installing PyTorch, building torchvision and running the tests.

You can cache pytorch with a daily key and thus drop the cache every day and thus reruning tests during the same day will be faster


chore(requirements): update django-auth-ldap to v1.2.11

See http://pythonhosted.org/django-auth-ldap/changes.html#v1-2-11-2017-04-22-testing-and-debugging-cleanup

Jenkins, test this please.

Codecov Report

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

@@            Coverage Diff             @@
##           master    #1289      +/-   ##
==========================================
- Coverage   87.07%   87.04%   -0.03%
==========================================
  Files          45       45
  Lines        3929     3929
  Branches      681      681
==========================================
- Hits         3421     3420       -1
- Misses        337      338       +1
  Partials      171      171