Dispatch an event when a popup is displayed

I'd like to trigger a callback function to run when a popup is displayed using on('popup') (or something equivalent). Is this currently possible? Or would it be a new feature request?
Perhaps the Popup.show() function could call dispatchEvent() to trigger its own event?
https://openlayers.org/en/latest/apidoc/module-ol_Observable-Observable.html#dispatchEvent

I was able to achieve what I needed with the following code:
popup.show(evt.coordinate, content);
popup.dispatchEvent('popup');

Then, elsewhere I can do:
popup.on('popup', function (event) {
    console.log('Event: popup');
});

@mstenta glad to see you've a solution, I'd be happy to add an event, maybe show and hide?

Yea that could be helpful! I'll reopen this.
Is it as straightforward as adding two lines?  this.dispatchEvent('show'); and this.dispatchEvent('hide'); in the corresponding methods of Geolocate class? If so I'll make a PR.

Hi, i understand the code not realy. I search for a solution to fill the Popup with content from a ajax request, without JQuery. The problem is, in this moment i must send all the content for all the popups by the first call of the website. That is too much data. I will fill the Popup on the click event with data from the server. The content for the Popup come from a xhttp request. Thats not so easy, because a xhttp request dont return a value.
Where and in what place do you use this?
popup.show(evt.coordinate, content);
popup.dispatchEvent('popup');

popup.on('popup', function (event) {
    console.log('Event: popup');
});

@makrolika Yes, that's where I am executing the request in my case (within the popup.on() callback). I am using jQuery.getJSON(), so you will need to adapt that for your case.
This is where we are doing it in farmOS:
https://github.com/farmOS/farmOS/blob/0e6b7c125aa4af00b923febb561ad0a96714d4db/modules/farm/farm_area/js/farmOS.map.behaviors.areas.js#L28
And in farmOS-map (which is our custom OpenLayers-based map library that is used by farmOS), we create the popup and dispatch the custom farmOS-map.popup event here:
https://github.com/farmOS/farmOS-map/blob/master/src/instance/methods/popup.js#L17
Hope that helps!

OK, thanks, that is also a special solution for a external software named FarmOS. I will not use this software to realized my idea. Is there a default solution to realized it? I will start a new Issue for my question.
https://github.com/walkermatt/ol-popup/issues/217

OK, thanks, that is also a special solution for a external software named FarmOS.

The way we did it in farmOS is just an example you can refer to. You don't need farmOS to do something similar in your code.
I assume that somewhere in your code you are running popup.show(...); - you just need to add popup.dispatchEvent('popup'); right after that, so that elsewhere code can be triggered when a popup is opened. Then, you add a callback function that runs when that event is dispatched, and inside that function you execute your HTTP request and put what you want into the popup content.
Hope that makes sense. The overall approach is simple, but you will need to figure out how it fits into your current code.

Please read my new Issue: https://github.com/walkermatt/ol-popup/issues/217
It works without popup.dispatchEvent(), but it is right? I don't understand why i am using popup.dispatchEvent(). It is needed, when i call the xhttp request in a outside function?

Hi mstenta, have you found a solution for your question?
I have found a solution for my first question https://github.com/walkermatt/ol-popup/issues/217 and for my new second question https://github.com/walkermatt/ol-popup/issues/321. Both have to do with the popup.show function. In the second i searched for a trigger event, when the popup is really displayed.


Remove fix leftover that caused cyclic load issues

This PR removes an attempt that was leftover in the #67714 PR which was merged a few hours ago.
The code removed was causing issues like this one:
Loading resource: res://Nodes/Technical/Jukebox.tscn
ERROR: Another resource is loaded from path 'res://Nodes/Technical/Jukebox.tscn::1' (possible cyclic resource inclusion).
   at: set_path (core/io/resource.cpp:75)
ERROR: Another resource is loaded from path 'res://Nodes/Technical/Jukebox.tscn::2' (possible cyclic resource inclusion).
   at: set_path (core/io/resource.cpp:75)
ERROR: Another resource is loaded from path 'res://Nodes/Technical/Jukebox.tscn::3' (possible cyclic resource inclusion).
   at: set_path (core/io/resource.cpp:75)
ERROR: Another resource is loaded from path 'res://Nodes/Technical/Jukebox.tscn::4' (possible cyclic resource inclusion).
   at: set_path (core/io/resource.cpp:75)
ERROR: Another resource is loaded from path 'res://Nodes/Technical/Jukebox.tscn::5' (possible cyclic resource inclusion).
   at: set_path (core/io/resource.cpp:75)
ERROR: Another resource is loaded from path 'res://Nodes/Technical/Jukebox.tscn::6' (possible cyclic resource inclusion).
   at: set_path (core/io/resource.cpp:75)
ERROR: Another resource is loaded from path 'res://Nodes/Technical/Jukebox.tscn::AnimationLibrary_3jtqj' (possible cyclic resource inclusion).
   at: set_path (core/io/resource.cpp:75)

It was an attempt to fix #61386.

Thanks!


Allow users to upvote (or downvote) reviews based on helpfulness

It would be nice to allow users to vote on how helpful they found reviews, so we can show the more helpful reviews on a course or professor at the top. This way they won't get stuck at the bottom and never seen, which could happen currently.
I would always show the option to vote, but if a user attempts to while not logged in, we should open the login/signup modal.

This got merged a while ago, but never closed for some reason. It'd be nice to start ranking reviews, with a score based on recency as well as how many people found it helpful, but I'll add a separate issue for that.


Fix NPE if timestamp is optional in DB

Correct the typo Timesamp...

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.i076004 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Issue with timer on arabic version.

We have issue with timer on arabic version while showing preroll. You can contact me for more details by Skype (bernikowich) or here.

Could you give us some more details? What specific issue are you seeing, how to do you replicate it, what browsers are you using?

Here is the image. We use not the latest version (not 2.1.0), but we'll update it tomorrow. I will notify you if something changes.

@shawnbuso Hello,
Do you have any news on the provided issue? It still exists though we updated SDK to 3.1.0. Do you have any ideas when it can be fixed?
Thank you!

Could you send me the ad tag you're using so I can test on my end? Thanks!

Please, try this one https://pubads.g.doubleclick.net/gampad/ads?sz=640x480&iu=/176111452/app_mena_arabic&impl=s&gdfp_req=1&env=vp&output=vast&unviewed_position_start=1&url=[referrer_url]&description_url=[description_url]&correlator=[timestamp]


Contribution of new Stripe module supporting Apple Pay, Google Pay, SCA (incl. 3D Secure)

Ciao ragazzi,
for my own purposes I had to develop a new Stripe module, which supported SCA (Strong Customer Authentication) because of the European Union PSD2 (Payments Service Directive 2).
The new module is based on PaymentIntent and as a nice add-on it comes with Apple Pay and Google Pay.
Is there any interest in the new module and if so, should it replace the old Stripe module or should it be an entirely new module?
I'm looking forward to receiving your comments.
Tanti saluti
Florian

A new module for Stripe is preferred. Really looking forward to your PR

@thiennn Any suggestions for the name?

SimplCommerce.Module.PaymentStripeV2 ?

SimpleCommerce.Module.PaymentStripeRev

Short update on this issue: The module will be called SimplCommerce.Module.PaymentStripeV2 as suggested by thienn. In the meantime I added already the persistence layer for the stripe session-ids. The only part still missing is the PaymentBackgroundService, which will finalize the payment, if the call-back is not triggered by the user's browser.
Hopefully I will have some time these days to finish the development ...

@fhebel Thanks for doing this. I have noticed Stripe are sending out email warnings for using the existing payment module.

Hi @horseyhorsey,
would you be willing to help me testing the new module once I finished coding? You know, I believe the developer is the worst tester for his own code.
Thanks in advance.
Best regards,
Florian

@fhebel Yes sure, I would need to test before going live anyway, no problem.

One issue has still to be solved: for registration of Apple Pay one needs to provide a url like e.g.
https://demo.simplcommerce.com/.well-known/apple-developer-merchantid-domain-association
(.well-known/apple-developer-merchantid-domain-association in the root path) containing some kind of guid.
Unfortunately the .Net Core PhysicalFileProvider interprets the full stop in ".well-known" as hidden file or directory and doesn't offer it for download.
Advice is welcome!

@horseyhorsey Ready for testing (#928)

Sorry, only just caught this message last night. Looks like September 14th is deadline for SCA.
This is too hard for me to test without making work. Spent a good hour or so trying to build it then I decided to roll my own. There are changes to the database and additions I don't the see the point of when already has a payment table that can deal with "Failed attempts".
Personally for me StripeV2 is very much like the module we have but we will create order after payment and cater for some webhook to create the order.

Hi @horseyhorsey,
actually the deadline for SCA was already on 14th of September 2019 ...
The implementation of the StripeV2 module is totally different because it's based on Stripe.net version 37.8.0 using Sessions and PaymentAttempts.
The need for the additional table comes from the fact that the new process is divided into the following steps:

We create a so-called Session server-side (with call-back urls for success & failure)
The user is redirected to the stripe.com site specifying the Id of the previously created session
If we're lucky we get a call-back to handle the status of the payment

So it's really important to keep track of that session otherwise our customer might have paid and SimplCommerce is not aware and doesn't create an order for the customer. This is the job of the background service.
Regarding the db schema changes it's really easy. If you use mssql then a simple "dotnet ef database update" will do the trick, otherwise you have to issue the command "dotnet ef migrations add AddPaymentAttempts" first.
I hope that helps.
Best regards,
Florian

Oh, Thought it was this year, better get it finished tonight then!  I forgot to point out we're using MySql for the database work I'd have to do.
My implementation is a simple migration using their checkout page and webhooks which developed locally using the new session. I can create the order / payment before the user is directed to the success page

I voluntarily chose the client-and-server approach (https://github.com/stripe-samples/checkout-one-time-payments) for two reasons:

It offers the complete functionality
It is less prone to be tampered with (successful checkout without having received the payment)

@horseyhorsey Anyway, you might want to share your solution as well?

Sorry. We dumped Stripe last night and just use Paypal now.


Pods not found when using a mixed-case datacenterName

Given this spec:
apiVersion: k8ssandra.io/v1alpha1
kind: K8ssandraCluster
metadata:
  namespace: test
  name: k8s-cluster
spec:
  cassandra:
    serverVersion: 4.1.0
    clusterName: Cql_Cluster
    datacenters:
      - metadata:
          name: k8s-dc1
        datacenterName: Cql_DataCenter1
        size: 1
        racks:
          - name: Cql_Rack1
        storageConfig:
          cassandraDataVolumeClaimSpec:
            storageClassName: standard
            accessModes:
              - ReadWriteOnce
            resources:
              requests:
                storage: 100Mi

The cluster errors out with:
no pods in READY state found in datacenter k8s-dc1

This is because cass-operator sanitizes the Cassandra pod's DC label with CleanupForKubernetes (no caps, no underscores):
cassandra.datastax.com/datacenter: cql-datacenter1

But k8ssandra-operator uses the unsanitized version to build its selector:
cassandra.datastax.com/datacenter: Cql_DataCenter1

We need to use the same sanitization function in k8ssandra-operator.
We should also consider switching to CleanLabelValue() in both operators, because this is what cass-operator uses for the cluster and rack labels. Right now we have inconsistent formats:
cassandra.datastax.com/cluster: Cql_Cluster
cassandra.datastax.com/datacenter: cql-datacenter1
cassandra.datastax.com/rack: Cql_Rack1

I think I poo-pooed here when using the sanitized name for the labels :(
Let's move to CleanLabelValue() overall, even if I hate having multiple ways of naming things...

I filed k8ssandra/cass-operator#622.
I'll keep this open until I can re-test with the cass-operator fix.

I'll keep this open until I can re-test with the cass-operator fix

Actually we still need to sanitize the name in k8ssandra-operator, so this gets its own PR.

I'll keep this open until I can re-test with the cass-operator fix

Actually we still need to sanitize the name in k8ssandra-operator, so this gets its own PR.

isn't in this particular case (and the line of the code) simply taking wrong field ? instead of "datacenterName()" it should take "Name" (which complies with k8s rules) and cass-operator uses for the label ?


Allow the location of the X509Certificate to be configured

Description
In SigningCredentialsResolver, the path to the signing certificate is hard-coded to be Directory.GetParent(Directory.GetCurrentDirectory()).FullName + some configured value. This has some weird issues where by default, when running locally, I end up having to place the certificate in C:\Users\ALEHEI\hub\resource-registry-2\srcaccesstoken. Note the ending srcaccesstoken - this is because the path is joined by string concatenation and not using any of the Path methods.
Beyond that, the fact that I cannot specify the path as a global path is also a problem. This means I can't just have 1 of the certificates on my machine, I have to copy it to every repo (and fix/update gitignore).
So there's 2 things I'd like changed here:

[ ] fix path handling so that I don't end up with weird paths like this
[ ] allow configuring the location as a global path

Additional Information
No response

The hard coded value can be overridden by adding a configuration section to appsettings.json or any other configuration source. This should work:
{
    "AccessTokenSettings": {
        "AccessTokenSigningKeysFolder": "/accesstoken/",
        "AccessTokenSigningCertificateFileName": "mycert.pfx"
    }
}

Keeping the issue to consider changing from string concatenation to Path.Combine, and the option to configure base path as well. This would need to be backwards compatible.

Except you can't configure it to be outside of your project directory. So I can't have 1 certificate on my machine and just setup an environment variable that all projects will use, because they all hardcode the path to start with the current working directory.

Except you can't configure it to be outside of your project directory. So I can't have 1 certificate on my machine and just setup an environment variable that all projects will use, because they all hardcode the path to start with the current working directory.

I acknowledged that brifely in my comment.


Allow passing color to TextSettings

This will allow to fix problem described in ManimCommunity/manim/pull/2341

Thanks for the contribution. I will have a closer look at this at latest by the end of the week. I hope you can wait until then and I apologise for probably not being able to do it sooner.
The approach you are using is similar to what MarkupText does. (Actually, that was the reason why I wrote that class roughly a year ago. I was regularly having trouble with t2c and co.) I think, it should be the final goal to merge Text and MarkupText into one single non-LaTeX text class. But I am not sure there is a consensus on that. And your contribution definitely improves the existing Text class.

Thanks for the PR. This looks good to me. Using https://gnome.pages.gitlab.gnome.org/gtk/Pango/struct.Attribute.html seems like a better idea to me rather than using PangoMarkup. I guess I will work on it later.

I think that PangoAttribute has its advantages. My concern is rather on the end-user side of it. I think it would be good to get rid of the archaic syntax we have inherited, also because it does not really allow overlapping formatting. Using PangoMarkup is an easy solution, because it offers a solution on the backend and on the frontend.

I think that PangoAttribute has its advantages. My concern is rather on the end-user side of it.

Probably we should this a better API than the current one. I mentioned PangoAttribute because it would be better than creating XML kinda strings ourselves and then passing it to pango.

I've noticed another problem, this time with gradient. It is a problem for both Text and MarkupText, namely the following code
class Test1(Scene):
    def construct(self):
        self.add(
            Text(
                "gradiented office isn't perfect",
                t2g={"office": (GREEN, RED)},
            ).move_to(UP))
        self.add(
            MarkupText(
                'gradiented <gradient from="GREEN" to="RED">office</gradient> isn\'t perfect',
            ).move_to(DOWN))

when run with current main branch results in

I've changed the implementation of gradient in text to set colors individually on each letter but this exposed another problem, namely the same code now results in

As you can see the ff ligature is no longer present. This is again problem with ManimPango as text2svg draws each group of formatted letters individually. Hence this code:
class Test2(Scene):
    def construct(self):
        self.add(
            Text(
                "gradiented office isn't perfect",
                t2s={"f": NORMAL},
            ))

results in

The tests are failing because windows is missing some fonts. I don't think it is caused by my changes, as I didn't touch fonts.

AFAICS, the error mentioned above (gradiented office) is explained in the docs for MarkupText: one can use <gradient from="RED" to="YELLOW" offset="2,1">example</gradient> to start the gradient two letters earlier and end it one letter earlier
I admit that this is only a workaround. However, as long as we do not have gradients built-in to Pango, we must do them at the SVG level and there just seems to be no way to reliably know how many glyphs you really get from a certain text.

The tests are failing because windows is missing some fonts. I don't think it is caused by my changes, as I didn't touch fonts.

I think the change which deletes the SVG file on the error raised has caused the issue. I think removing that could fix the errors.

AFAICS, the error mentioned above (gradiented office) is explained in the docs for MarkupText: one can use <gradient from="RED" to="YELLOW" offset="2,1">example</gradient> to start the gradient two letters earlier and end it one letter earlier

You're right, I didn't notice that. I think instead of requiring offsets, as a workaround we could set colors directly with markup in strings passed to pango. So for example we could replace <gradient from"WHITE" to="RED">ab</gradient> with ab before sending it to pango. This will of course still be workaround since ligatures will be a single color (of the second letter I think), but as you said we can't do better without built-in gradients.

I will have a look at the tests failing on windows tomorrow.

I will have a look at the tests failing on windows tomorrow.

The tests failed because the order of execution of tests has changed. There is some kind of cache in Pango that gets interfered in these tests. Can you rebase on https://github.com/ManimCommunity/ManimPango/pull/67 and check if that works?

@marcin-serwin Can you rebase again with main?

I will release a new version after the CI is fixed #68 . Thanks.

I have released 0.4.0 now, it should have this change.


Initial Report and Code

What group number are you? I'm not sure if I should be peer reviewing your group because I don't see a group number anywhere.

Group 8! Sorry

Review from Group 7

OpenMPI scaling looks promising to perform better on large amounts of nodes.

In the strong scaling study, you define strong scaling but not scaling 'efficiency'. But the graph plotted efficiency and not the speedup itself.

A better spread of the number of threads, bigger graphs and multiple runs when timings would probably paint a better average picture in the scaling studies.

Elaborating on the MPI implementation in the report would help us understand how communication pattern and parallelism works in your solution.

A comment or two on the OpenMPI profiling can give you hints about your load balancing.

Review from Group 6
Strength:

Looks you did quite detailed profiling
Detailed scaling study is good.
Nice comparison for study for both OpenMP and

Things to be improved:

It would be nice if you can include the performance comparison based on non-tuning (baseline) state.


Update LWRP Options for Filebeat 5.2

Hello,
We recently upgrade our Filebeat version to 5.2 and everything appears to be working fine. Today when we tried to update the prospector configuration option for close_timeout, I noticed there was not LWRP option for that. Instead there is close_older which is now deprecated in version 5.2.
Instead of just creating a pull request to the changes I need, I want to open the discussion to get opinions on methods to include the latest Filebeat options with previous options.

👍
And for those that are having SSL issues with 5.2.2 "ERR Failed to publish events caused by: EOF" the easiest fix is to change change the tls attribute to ssl (in a wrapper cookbook), as TLS was renamed to SSL in Filebeat 5.0.
https://discuss.elastic.co/t/filebeat-err-failed-to-publish-events-caused-by-eof/65105

@jamiebuxxx Will add recent filebeat versions configuration parameters to LWRP.
Perhaps we can filter options for various filebeat versions.
https://github.com/vkhatri/chef-filebeat/blob/master/libraries/provider_prospector.rb#L37
Will check it out. Sorry for the extreme delay in response.

@vkhatri No worries. Thanks for checking this out. I think filter options per versions would be a good idea. And creates a template for future version upgrade.

Looks like there are three categories of options to maintain in LWRP.
- options for all filebeat versions
- options added by a filebeat version
- options deprecated by a filebeat version

This is currently applicable to prospectors added using LWRP. Prospectors added using node attribute node['filebeat']['prospectors'] does not use LWRP, may be it should.

Thats a good point about adding prospectors via the node attribute. It should the the LWRP whenever possible. Even if it just loop of a hash of entries in the node attribute.

Maintaining filebeat version specific attributes will require a lot of effort and continuous maintenance. I found it is easier to leave it up to the user to choose the right LWRP options.
However, new attributes have been added to the LWRP.
The cookbook release v1.0.0 will no longer actively support/test filebeat 1.x.
Also, prospectors via node attribute now using LWRP.
Filebeat configuration documentation is kept minimal as possible and users are encouraged to reference filebeat documentation instead. IMO, attributes/config.rb provides sufficient reference to get started.
Fixed in master. Keeping this issue open for some more time.

Release cookbook version v1.0.0.

Thanks for updating this @vkhatri! This is really awesome and looking forward to using the new options.


Zijian/fix index error msg

fix #243

Codecov Report

Merging #247 into master will increase coverage by 0.21%.
The diff coverage is 54.05%.

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


ci: check that all device config files have a .json extension

fixes: #7097

@zwave-js-bot automerge


Nonce too low error

Summary of Bug
This is an error we've been seeing sporadically for a while, it looks like it's not dangerous at all, a simple restart fixes it, but I would like to know why it happens in the first place.
5:00PM ERR sendTransaction failed error="nonce too low" module=ethCommiter tx_hash=0x9a29ff7ea9c26def63ced06a3cc59f906b8d4157ef85f4be336379f9bbe9ea25 tx_hash_ret=0x0000000000000000000000000000000000000000000000000000000000000000

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

So two things:

Injective solved this via the eth mempool feature, which I believe we now have support for.
Having to restart is not ideal. Operators are not going to be watching peggo -- they're going to have it run via systemd or some other service monitor process. I feel like we should gracefully exit if peggo cannot recover on its own.

It's very dangerous for me though.
after this error happen it's will try to send tx until it's successful ( also don't know why it resend ) and when everything work it's will send all tx ( which is before failed because "Nonce too low" )  in one go and cause heavily lost.
may be cause has been mention here


[FR]: Copy inline tags to frontmatter

Issue validation

[X] My issue is not a question relative to Material Mkdocs nor Mkdocs (You can open a discussion to get more help!)
[X] I checked the issue to prevent duplicate

Workflow
Obsidian plugin 💠
Is your feature related to a problem ?
With some publishing websites like Quartz and anything that uses Hugo, it's only possible to use tags if they are in frontmatter and inline tags doesn't work.
What solution do you want to see ?
I think Publisher Plugin should have an option to add inline tags to frontmatter while processing file content.
Describe the alternative you've considered
No response
OS
Linux
Anything else?
This can be done by:

Getting inline tags app.metadataCache.getFileCache(app.workspace.getActiveFile())?.tags?.map(t => t.tag.replace('#', '').replace('/', '_')).
Appending tags to frontmatter tags key if it exists, or creating a new one with inline tags if it doesn't.

Instead of writing a code that does this from scratch I think metaedit API can be utilized, this way by using update, createYamlProperty, getPropertiesInFile and getPropertyValue.
P.S. dataview can also get file tags, but it doesn't separate frontmatter and inline tags as far as I know.
app.plugins.plugins.dataview.api.page(app.workspace.getActiveFile().path).file.tags

Excellent idea !! I never add this idea. I will take a look about the metaedit API and implement this asap


files copied into container ought to have a uid/gid mapping

as of 0e884ec4d8fbb9c36dd40fa246e85b55dabc4574
vbatts@valse ~/src/appc/acbuild/examples/acserver (master *) $ ./build-acserver.sh
Building acserver...
Beginning build with an empty ACI
Setting name of ACI to example.com/acserver
Copying host:acserver to aci:/bin/acserver
Copying host:/home/vbatts/opt/gopath/src/github.com/appc/acserver/templates to aci:/templates
Adding port "http"="tcp"
Adding mount point "acis"="/acis"
Setting exec command [/bin/acserver]
Writing ACI to acserver-latest-linux-amd64.aci
vbatts@valse ~/src/appc/acbuild/examples/acserver (master *) $ tar tvf acserver-latest-linux-amd64.aci
drwxr-xr-x 1000/1001         0 2015-11-06 05:12 rootfs
drwxr-xr-x 1000/1001         0 2015-11-06 05:12 rootfs/bin
-rwxr-xr-x 1000/1001   7158435 2015-11-06 05:12 rootfs/bin/acserver
drwxrwxr-x 1000/1001         0 2015-11-06 04:58 rootfs/templates
-rw-rw-r-- 1000/1001      2464 2015-11-06 04:58 rootfs/templates/index.html
-rw-r--r-- root/root       345 2015-11-06 05:12 manifest

Yeah those mappings should exist. It shouldn't be hard to implement, I'll look into it.


Can views be snapped?

Is it possible that views are scrollable by one view max everytime user swipes?

This is currently not supported, but I'm about to improve code related to snapping and I might add this as well.


Revlin/1.4.x svg

When AngularJS runs within an SVG file there's an issue with handling URL parts... I tried to address this, but please check out the code

I signed it!


Issue 439 - Install script for local Docker-based CLI

Resolves #439

I'm not sure if we want the one-review-required label on this since there are significant documentation changes.


smile-Ev

I made a smiley face that's super customizable. you can edit values for everything and move stuff around. I have a lot of experience coding and I've been to five hackathons + done a lot of projects.

I think this may be a bit too simple at the moment. What are some ways to make a face like this more beautiful and intricate?

I'm going to close this for housekeeping but please resubmit when you are ready!


Bot crashes

Expected Behavior
The bot should not crash
Actual Behavior
After successful login, and the bot starting it crashes.
Your FULL config.json (remove your username, password, gmapkey and any other private {
"auth_service": "google",
"username": "",
"Removed pw/gmap",
"encrypt_location": "",
"websocket_server": false,
"tasks": [
  {
    "type": "HandleSoftBan"
  },
  {
    "type": "SleepSchedule",
    "config": {
      "enabled": true,
      "time": "20:51",
      "duration":"8:01",
      "time_random_offset": "00:20",
      "duration_random_offset": "00:56"
    }
  },
  {
    "type": "CollectLevelUpReward"
  },
  {
    "type": "IncubateEggs",
    "config": {
      "longer_eggs_first": true
    }
  },
  {
    "type": "UpdateLiveStats",
    "config": {
      "enabled": true,
      "min_interval": 10,
      "stats": ["username", "uptime", "stardust_earned", "xp_earned", "xp_per_hour", "stops_visited"],
      "terminal_log": true,
      "terminal_title": true
    }
  },
  {
    "type": "TransferPokemon"
  },
  {
    "type": "NicknamePokemon",
    "config": {
      "enabled": false,
      "nickname_template": "{iv_pct}_{iv_ads}"
    }
  },
  {
    "type": "EvolvePokemon",
    "config": {
        "evolve_all": "none",
        "first_evolve_by": "cp",
        "evolve_above_cp": 500,
        "evolve_above_iv": 0.8,
        "logic": "or",
        "evolve_speed": 20,
        "use_lucky_egg": false
    }
  },
  {
    "type": "RecycleItems",
    "config": {
      "min_empty_space": 15,
      "max_balls_keep": 150,
      "max_potions_keep": 50,
      "max_berries_keep": 70,
      "max_revives_keep": 70,
      "item_filter": {
        "Pokeball":       { "keep" : 100 },
        "Potion":         { "keep" : 10 },
        "Super Potion":   { "keep" : 20 },
        "Hyper Potion":   { "keep" : 30 },
        "Revive":         { "keep" : 30 },
        "Razz Berry":     { "keep" : 100 }
      }
    }
  },
  {
    "type": "CatchVisiblePokemon"
  },
  {
    "type": "CatchLuredPokemon"
  },
  {
    "type": "SpinFort"
  },
  {
    "type": "MoveToFort",
    "config": {
        "lure_attraction": true,
        "lure_max_distance": 10000
    }
  },
  {
    "type": "FollowSpiral",
    "config": {
      "diameter": 8,
      "step_size": 73
    }
  }
],
"map_object_cache_time": 5,
"forts": {
  "avoid_circles": true,
  "max_circle_size": 50,
  "cache_recent_forts": true
},
"walk_max": 2.16,
"walk_min": 1.16,
"action_wait_min": 1,
"action_wait_max": 4,
"debug": false,
"test": false,
"health_record": true,
"location_cache": true,
"distance_unit": "mi",
"reconnecting_timeout": 15,
"catch_randomize_reticle_factor": 1.0,
"catch_randomize_spin_factor": 1.0,
"min_ultraball_to_keep": 10,
"logging_color": true,
"catch": {
  "any": {"catch_above_cp": 0, "catch_above_iv": 0, "logic": "or"},
  "// Example of always catching Rattata:": {},
  "// Rattata": { "always_catch" : true }
},
"catch_throw_parameters": {
  "excellent_rate": 0.05,
  "great_rate": 0.25,
  "nice_rate": 0.20,
  "normal_rate": 0.1,
  "spin_success_rate" : 0.5
},
"release": {
  "any": {"release_below_cp": 0, "release_below_iv": 0, "logic": "or"},
  "// Example of always releasing Rattata:": {},
  "// Rattata": {"always_release": true},
  "// Example of keeping 3 stronger (based on CP) Pidgey:": {},
  "// Pidgey": {"keep_best_cp": 3},
  "// Example of keeping 2 stronger (based on IV) Zubat:": {},
  "// Zubat": {"keep_best_iv": 2},
  "// Also, it is working with any": {},
  "// any": {"keep_best_iv": 3},
  "// Example of keeping the 2 strongest (based on CP) and 3 best (based on IV) Zubat:": {},
  "// Zubat": {"keep_best_cp": 2, "keep_best_iv": 3}
},
"vips" : {
     "Any pokemon put here directly force to use Berry & Best Ball to capture, to secure the capture rate!": {},
    "any": {"catch_above_cp": 1200, "catch_above_iv": 0.9, "logic": "or" },
    "Lapras": {},
    "Moltres": {},
    "Zapdos": {},
    "Articuno": {},

    "// S-Tier pokemons (if pokemon can be evolved into tier, list the representative)": {},
    "Mewtwo": {},
    "Dragonite": {},
    "Snorlax": {},
    "// Mew evolves to Mewtwo": {},
    "Mew": {},
    "Arcanine": {},
    "Vaporeon": {},
    "Gyarados": {},
    "Exeggutor": {},
    "Muk": {},
    "Weezing": {},
    "Flareon": {}

}

}
Output when issue occurred
Traceback (most recent call last):
File "pokecli.py", line 609, in
main()
File "pokecli.py", line 104, in main
bot.tick()
File "/root/pgo2/pokemongo_bot/init.py", line 483, in tick
if worker.work() == WorkerResult.RUNNING:
File "/root/pgo2/pokemongo_bot/cell_workers/follow_spiral.py", line 117, in work
if dist <= 1 or (self.bot.config.walk > 0 and step_walker == None):
AttributeError: 'Namespace' object has no attribute 'walk'
2016-08-16 09:50:14,022 [sentry.errors] [ERROR] Sentry responded with an error: 'module' object has no attribute 'HTTPSHandler' (url: https://app.getsentry.com/api/90254/store/)
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/raven/transport/threaded.py", line 174, in send_sync
super(ThreadedHTTPTransport, self).send(data, headers)
File "/usr/local/lib/python2.7/dist-packages/raven/transport/http.py", line 47, in send
ca_certs=self.ca_certs,
File "/usr/local/lib/python2.7/dist-packages/raven/utils/http.py", line 44, in urlopen
class ValidHTTPSHandler(urllib2.HTTPSHandler):
AttributeError: 'module' object has no attribute 'HTTPSHandler'
2016-08-16 09:50:14,022 [sentry.errors.uncaught] [ERROR] [u"AttributeError: 'Namespace' object has no attribute 'walk'", u'  File "pokecli.py", line 609, in ', u'  File "pokecli.py", line 104, in main', u'  File "pokemongo_bot/init.py", line 483, in tick', u'  File "pokemongo_bot/cell_workers/follow_spiral.py", line 117, in work']
Steps to Reproduce

Other Information
OS:
Debian 7, python 2.7
Branch:
Master
Git Commit:
52495aee0cd0882077270c9c3ed9445bcee31f4d
Python Version:
2.7.3
Any other relevant files/configs (eg: path files)

#4042 #4077

You are on the master branch. The dev branch fixes this. Master should be updated soon, so please stand by. Also update by running cd PokemonGo-Bot then git pull whenever the merge happens.


Option to toggle menu on mouse hover

Suggested by KerTin Ong in the marketplace comments

released in v2.0.0


testing: fix TestPrivateNetDefaultConnectivity

Search all interfaces for IPv4 addresses that could for connections by the
client. Skip the test if no address is found.

@iaguis @krnowak
Please verify that it works for you now

Works for me now and the test passes :)

LGTM

Works for me too, LFAD.


Mark .rodata maps as readonly and freeze on load

This commit marks .rodata maps as BPF_F_RDONLY_PROG when loaded to
prevent a BPF program mutating them.
Initial map data is populated by the loader using the new BpfLoader::set_global() API.
The loader will mark a map as frozen using bpf_map_freeze to prevent map data
being changed from userspace.
Related to #117

thanks! will address these comments over the weekend

@alessandrod comments addressed. ptal when you have some time...

You should do the opposite, iterate on globals as the number of globals is always going to be stricly smaller than the number of symbols
And also if a global can't be found in the symbol table, you should error out

Whichever way we cut it it's going to be ~somewhat bad.
I've implemented this approach with a couple of caveats:

I have to make one full pass over symbols_by_index to turn them in to what is effectively symbols_by_name. This means that a lookup for whether a global is in the symbols table is fast.
I do a self.maps.iter_mut().find() to get the Map where the section index is the same as the symbol I'm working with. A hashmap is no good here since some sections (i.e ".maps" may have more than one map in them) but typically those we're patching with data do not.

Almost there! See comments


Is ruby good for potential deployment?

Hello.
I found your project very interesting. Thanks!
I wonder if Ruby is the correct language for this in a final approach. I'm not a developer and have nothing against this interesting language at all, but I think it would provide overhead issues.
I'm an user of an eink Android device and I love KOreader. Unfortunately, there's no native support for GoldenDict dictionaries. They use sdcv to support StarDict dictionaries, like everything else.
But I miss information in advanced learning dictonaries, as pronunciation and able to hear words to improve my spoken English.

You're probably right, although this has solved my immediate problem (which was to be able to consult Goldendict dictionaries via the command-line over SSH).
What language would you suggest? KOreader appears to be written in Lua. Do you know if it's possible to create plugins to support different dictionary formats?

Sincerely...
I have no idea!!
I just found the following:
https://github.com/koreader/crengine/tree/master/tinydict
https://github.com/koreader/sdcv
You can ask their devs at the issue tracker, forum or gitter
https://gitter.im/koreader/koreader
http://www.mobileread.com/forums/forumdisplay.php?f=276


bump to hippo-openapi 0.9, hippo v0.14.1

This makes spin compatible with Hippo v0.18.1. Backwards compatibility with older versions of Hippo (i.e. the ones that are deployed via the fermyon installer) is not guaranteed.

I'll let y'all handle the merging of this PR - once merged we should move quickly to cut a new release of Spin and update fermyon/installer to bump spin/hippo

Does this also make it safe to merge #611 or should that wait until the installer is updated?

Ooh, good catch! Yes, #611 could be merged at the same time. Hippo 0.18.1 implements the status code checks.

As a heads up, a new release of Hippo will soon come out with changes to the API endpoints. Someone on the team pointed out that the API endpoints were not following REST best practices, and we figured it'd be better to break the API now rather than later.
As a result, a new version of hippo-openapi (0.10) will be released soon accommodating those changes. I'd suggest holding off on a spin release until that version is out.

closing in favour of https://github.com/fermyon/spin/pull/678.


Exception not thrown on syntax error

Environment details

OS: MacOS
Node.js version: 12.18
npm version: 6.14.4
@google-cloud/bigquery version: 5.3.0

Steps to reproduce
  it("throws on bigquery syntax error", async () => {
    const bq = new BigQuery({ projectId: "REDACTED" })

    const [job] = await bq.createQueryJob({
      query: `DECLARE foo DEFAULT ( SELECT 1 );
      SELECT 1 FROM XYZ`,
      timeoutMs: 5000,
      location: "US"
    })

    const [rows] = await job.getQueryResults()

    assert.strictEqual(rows.length, 0)
  })

Expected result:
Invalid value: Table name "XYZ" missing dataset while no default dataset is set in the request. at [2:1]
Actual result
No exception is thrown, rows.length = 0

Thanks for the report. How do you usually make this call when you receive that error? A quick search showed that error reported a table is created: https://copycoding.com/d/bigquery-error-table-name-xyz-missing-dataset-while-no-default-dataset-is-set-in-the-request-at-x-y

Hi the table name is irrelevant. It was a trivial example to show that the sql contains a syntax error but an exception is not thrown.  Taking out the DECLARE will cause an exception...so it may be related to that.

Is everything working as intended then? The example from your first post didn't end up being invalid in terms of syntax, it just didn't return results. When we pop a syntax error in there, it throws as expected.

The example has a syntax error because table XYZ does not exist.

I believe a syntax error is one in the formatting of the query. The XYZ error is apparently being processed and the fact that the table does not exist is being ignored by the server. We just pass along what they give us, good or bad. Do you expect an error there based on experience with another library or way of calling the API?

It should generate an error in JS.  Pasting the query into the BigQuery web console generates an error.  Removing the DECLARE statement causes the JS to throw an exception.

I actually have a similar problem but not with table name but with an incorrect field name. There's no error thrown, just an empty result. In the Google Console the job did error.

The issue here is that scripting statements like this generate child jobs for each statement. When you call job.getQueryResults using the original parent job, what's returned is the result of the last statement that executed. So, in the case of your example, it returns the empty results from the DECLARE statement's execution.
To obtain the results of all statements in the script, you must enumerate the child jobs and call jobs.getQueryResults on each of them. You can access the list of child jobs by setting the parentJobId option in a bigquery.getJobs call.
Here is how you would access the error from the SELECT statement:
const bq = new BigQuery({ projectId: "REDACTED" });

 [job] = await bq.createQueryJob({
   query:
   `DECLARE foo DEFAULT ( SELECT 1 );
   SELECT 1 FROM XYZ`,
   timeoutMs: 5000,
   location: "US"
 });

 const [rows] = await job.getQueryResults();

 const [childJobs] = await bq.getJobs({parentJobId: job.id});

 for (const job of childJobs) {
   console.log('Job: ', job.id);
   console.log('Error: ', job.metadata.errorResult);
 }

// Output:
//
// Job:  script_job_123...
// Error:  { reason: 'invalid',
//   location: 'xyz',
//   message: 'Table name "xyz" missing dataset while no default dataset is set in the request.' }
//
// Job:  script_job_678...
// Error:  undefined

Documentation for this concept is here.


Partial blurry Font (Menu, Navigator, Code)

Since the last update I have issues with blurry fonts in parts of the VS Window, especially when it is out of focus. Moving the Cursor over the affected area it get partially away. See the attached image.
Graphics Card is an Nvidia GTX 1070 with driver Version 398.36

VSCode Version: 1.26.1
OS Version: Windows 10 1803

Steps to Reproduce:

Start vscode
open a project
don't move mouse

Does this issue occur when all extensions are disabled?: Yes

I'm experience the same issues after the most recent update

Work-around
After closing all Visual Studio Code windows, I opened a terminal and ran code.exe --disable-gpu
So far haven't observed the blurring effect after disabling the gpu.

Workaround fixed it for me, GTX 1080, driver version: 398.82 VSC: 1.26.1 W10x64

Duplicate of https://github.com/Microsoft/vscode/issues/51789

Okay.. disabling FXAA fixed it for me too... thanks


azure-sdk-for-go 최신버전 사용 시 driver build 실패

(카푸치노 공개 행사 이후에 하면 좋을 것 같습니다.)

펼치기 / 숨기기
============ build azure ... ============
# github.com/Azure/azure-sdk-for-go/services/resources/mgmt/2017-05-10/resources
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/resources/mgmt/2017-05-10/resources/deploymentoperations.go:120:2: not enough arguments to return
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/resources/mgmt/2017-05-10/resources/deploymentoperations.go:120:15: client.Send undefined (type DeploymentOperationsClient has no field or method Send)
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/resources/mgmt/2017-05-10/resources/deploymentoperations.go:213:2: not enough arguments to return
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/resources/mgmt/2017-05-10/resources/deploymentoperations.go:213:15: client.Send undefined (type DeploymentOperationsClient has no field or method Send)
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/resources/mgmt/2017-05-10/resources/deployments.go:100:2: not enough arguments to return
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/resources/mgmt/2017-05-10/resources/deployments.go:100:15: client.Send undefined (type DeploymentsClient has no field or method Send)
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/resources/mgmt/2017-05-10/resources/deployments.go:190:2: not enough arguments to return
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/resources/mgmt/2017-05-10/resources/deployments.go:190:15: client.Send undefined (type DeploymentsClient has no field or method Send)
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/resources/mgmt/2017-05-10/resources/deployments.go:278:2: not enough arguments to return
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/resources/mgmt/2017-05-10/resources/deployments.go:278:15: client.Send undefined (type DeploymentsClient has no field or method Send)
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/resources/mgmt/2017-05-10/resources/deployments.go:278:2: too many errors
# github.com/Azure/azure-sdk-for-go/services/compute/mgmt/2018-06-01/compute
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/compute/mgmt/2018-06-01/compute/availabilitysets.go:108:2: not enough arguments to return
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/compute/mgmt/2018-06-01/compute/availabilitysets.go:108:15: client.Send undefined (type AvailabilitySetsClient has no field or method Send)
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/compute/mgmt/2018-06-01/compute/availabilitysets.go:184:2: not enough arguments to return
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/compute/mgmt/2018-06-01/compute/availabilitysets.go:184:15: client.Send undefined (type AvailabilitySetsClient has no field or method Send)
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/compute/mgmt/2018-06-01/compute/availabilitysets.go:259:2: not enough arguments to return
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/compute/mgmt/2018-06-01/compute/availabilitysets.go:259:15: client.Send undefined (type AvailabilitySetsClient has no field or method Send)
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/compute/mgmt/2018-06-01/compute/availabilitysets.go:334:2: not enough arguments to return
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/compute/mgmt/2018-06-01/compute/availabilitysets.go:334:15: client.Send undefined (type AvailabilitySetsClient has no field or method Send)
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/compute/mgmt/2018-06-01/compute/availabilitysets.go:448:2: not enough arguments to return
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/compute/mgmt/2018-06-01/compute/availabilitysets.go:448:15: client.Send undefined (type AvailabilitySetsClient has no field or method Send)
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/compute/mgmt/2018-06-01/compute/availabilitysets.go:448:2: too many errors
# github.com/Azure/azure-sdk-for-go/services/network/mgmt/2018-04-01/network
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/network/mgmt/2018-04-01/network/applicationgateways.go:105:20: client.Send undefined (type ApplicationGatewaysClient has no field or method Send)
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/network/mgmt/2018-04-01/network/applicationgateways.go:206:20: client.Send undefined (type ApplicationGatewaysClient has no field or method Send)
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/network/mgmt/2018-04-01/network/applicationgateways.go:282:20: client.Send undefined (type ApplicationGatewaysClient has no field or method Send)
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/network/mgmt/2018-04-01/network/applicationgateways.go:362:2: not enough arguments to return
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/network/mgmt/2018-04-01/network/applicationgateways.go:362:15: client.Send undefined (type ApplicationGatewaysClient has no field or method Send)
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/network/mgmt/2018-04-01/network/applicationgateways.go:436:2: not enough arguments to return
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/network/mgmt/2018-04-01/network/applicationgateways.go:436:15: client.Send undefined (type ApplicationGatewaysClient has no field or method Send)
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/network/mgmt/2018-04-01/network/applicationgateways.go:511:2: not enough arguments to return
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/network/mgmt/2018-04-01/network/applicationgateways.go:511:15: client.Send undefined (type ApplicationGatewaysClient has no field or method Send)
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/network/mgmt/2018-04-01/network/applicationgateways.go:620:15: client.Send undefined (type ApplicationGatewaysClient has no field or method Send)
/root/go/pkg/mod/github.com/!azure/azure-sdk-for-go@v42.2.0+incompatible/services/network/mgmt/2018-04-01/network/applicationgateways.go:620:15: too many errors
chmod: cannot access 'azure-driver-v1.0.so': No such file or directory
mv: cannot stat './azure-driver-v1.0.so': No such file or directory

장기적인 관점에서 봤을 때
azure-sdk-for-go v42.2.0 과 그 이후 버전에 대해서도 Azure 드라이버 빌드가 잘 되었으면 좋겠습니다.

내용 확인 해보시고, 카푸치노 이전, 이후 스케줄링 부탁드려요~

Reopened in https://github.com/cloud-barista/cb-spider/issues/328


PR changes which glyphs are displayed

it duplicates most of additional glyphs feature.

fixed by only generating the # glyph in additionaGlyphs in v.2.1.4


[Windows] Styles with positional attributes are applied twice, resulting in incorrect positioning.

Description
LottieView is implemented as:
<View style={[aspectRatioStyle, sizeStyle, style]}>
    <AnimatedNativeLottieView style={[
            aspectRatioStyle,
            sizeStyle || { width: '100%', height: '100%' },
            style,
          ]}
    />
</View>

Here we can see the incoming style property is applied twice, once to outer view and again to the native control. This means that if the style contains positional settings, such as { left: 50 }, they first cause the outer View container to be translated relative to its parent, and then the animation itself to be translated further.
Steps to Reproduce
<View style={{ backgroundColor: "blue"}}>
    <LottieView style={ { left: 50, width: 50, height: 50, backgroundColor: "red" } } />
</View>

Expected behavior: Animation is positioned 50 units way from the left side of the surrounding blue box, and the red color is only behind the animation.

Actual behavior: Red box is positioned 50 units from the left of the surrounding blue box top-left corner, animation is positioned a further 50 units to the right.

Versions
lottie-react-native: 5.1.5
react: 18.0
react-native: 0.69.3
react-native-windows: 0.69.19
Tested on Windows only
Thoughs on a fix
The View wrapper is needed to support attributes like backgroundColor or accessibility props that aren't directly supported on the native control. Since the View already has the sizing and positioning styles applied, could the native control just be set to fill 100% of the space of the View container?
<View style={[aspectRatioStyle, sizeStyle, style]}>
    <AnimatedNativeLottieView style={StyleSheet.absoluteFill} />
</View>

This should get fixed in v6. I will close this for now.
Feel free to reopen it.

same issue here in v6,
my code:
<View
      style={{
        paddingHorizontal: 30,
        paddingTop: insets.top ,
        flex:1,
        paddingBottom: insets.bottom + 10,
        backgroundColor: colors.background,
      }}
    >
      <LottieView
      source={require("../../../../assets/lottie/error.json")}
      style={{width: 100, height: 100, backgroundColor: "blue"}}
      autoPlay
      loop
    />
</View>


Goaccess live-html-report returns JSON only

Hello everyone, so I'm new to goaccess, And now I'm using it with html-report and I'm loving it, so now what I want is to use live-html-report but I don't get the idea why I'm receiving only JSON data on the websocket or Is that how's the server is supposed to work ?
so my command is : goaccess -f access.log --log-format=COMBINED --time-format=%T --date-format=%d/%b/%Y --live-html-report --port=9870
And my HTML client code that receives data from the websocket is :
<!DOCTYPE html>

Connecting...

So once I'm connected with the websocket, the data that I receive is only JSON and the output is like this :
{
	"general": {
		"start_date": "14/Jun/2020",
		"end_date": "20/Nov/2020",
		"date_time": "2020-11-21 11:09:42 +0100",
		"total_requests": 23614,
		"valid_requests": 23614,
		"failed_requests": 0,
		"generation_time": 3,
		"unique_visitors": 519,
		"unique_files": 1830,
		"excluded_hits": 0,
		"unique_referrers": 2089,
		"unique_not_found": 20,
		"unique_static_files": 323,
		"log_size": 5320508,
		"bandwidth":<PHONE_NUMBER>,
		"log_path": [
			*************
		]
	},
	"visitors": {
		"metadata": {
			"bytes": {
				"total": {
					"value":<PHONE_NUMBER>
				},
				"avg": {
					"value": 36664124,
					"percent": "2.22"
				},
				"max": {
					"value":<PHONE_NUMBER>,
					"percent": "89.27"
				},
				"min": {
					"value": 10906,
					"percent": "0.00"
				}
			},
.....
And What I want is, Instead of sending only the parsed data as JSON over the websocket, I want to send the full HTML report (with it's HTML, CSS And Java Script) like when I'm generating a static one using the command goaccess access.log -a > report.html.
So my question is, is there's any way to send the full HTML report over the websocket ?
Also if there's any enhancement on the HTML client code that accepts data from the websocket I would also love it.

Hello, it should be --real-time-html and the output file. e.g.,
goaccess access.log --real-time-html -o report.html --log-format=COMBINED --port=9870

Thanks for your answer, even with this method it's still sends me data as JSON. And FYI, I have a configuration file that I'm using when I'm outputting a static HTML report which contains the following:
date-format %d/%b/%Y
time-format %T
log-format COMBINED
log-file access.log
geoip-database GeoLite2-City.mmdb
color-scheme 3
config-dialog false
hl-header true
html-prefs {"theme":"bright","perPage":20,"layout":"horizontal","showTables":true,"visitors":{"plot":{"chartType":"bar"}}}
html-report-title Statistics
real-os true
agent-list true
output output\report.html

And I even tried to use this configuration file with --real-time-html but still no luck.

Could you please post a screenshot of what you are getting when opening the report.html file?

Yeah Yeah of course, sorry for not posting one from the start.
Here's my configuration file and when I'm starting goaccess with the conf file:

And here is when I'm starting goaccess with in-line parameters :

Either ways I'm using to start goaccess  with --real-time-html I'm getting the same output on the browser, but tbh sometimes when I'm starting it with the conf file( the same conf file in the picture above ) I get disconnected directly once I get connected.
And here's my output on the browser when it's working:

A closer look:

And here's my source code :

I even tried to change the line 8 on the HTML file which contains the following Javascript instruction :     var socket = new WebSocket('ws://localhost:9870/report.html');  and tried to remove the report.html from the websocket address and I'll have the following :      var socket = new WebSocket('ws://localhost:9870');  but still no luck.
But after you've said :

Could you please post a screenshot of what you are getting when opening the report.html file?

I did take a look on the report.html directly from the hard-drive and when I refresh the page, the file actually does change (Take a look at the last time updated in both pictures):

And last but not least, I even tried with gwsocket and I always get data in JSON format.
So my question is, is there's any way to send the full report.html over the websocket.
FYI, I'm working at the moment with Windows 10 And MSYS And I've compiled all the sources, which means I didn't download any pre-built binary release, And gwsocket is working normally without any errors and it's working like a charm when I'm outputting a static HTML report.
And finally thank you so much for your time and efforts.

Sorry, I misread your question. Yes, the websocket server in goaccess will only output JSON data. You can't get HTML. Is there any particular reason why you want to get HTML code? JSON should give you a lot more flexibility to build whatever you are looking for with the data.

JSON should give you a lot more flexibility to build whatever you are looking for with the data.

Yes exactly, Thanks a lot for your time.


WIP: Asynchronous geoparquet reader

Implementing an asynchronous GeoParquet file reader using ParquetRecordBatchStream.
TODO:

[x] Initial implementation in src/io/parquet/reader.rs
[x] Fix trait bounds
[x] Refactor to have both read_geoparquet and read_geoparquet_async functions parse the GeoParquet metadata using the same function
[ ] Bring in object-store crate to read from URL (if it gets complicated, maybe split it into a separate PR)
[ ] Document new function
[x] Add unit tests

Addresses #492
P.S. This is my first ever Rust PR, so take it easy :see_no_evil:

Thanks! I pushed a commit with the following changes:

Fixed the trait bounds, as mentioned above.
Removed the calls to unwrap in favor of the ? (try) operator. unwrap means essentially "assert there was no error", while ? means "continue if there was no error; otherwise propagate the error upwards, immediately returning an error from this function". The ? takes a bit of time to get used to but ends up having really clean code with excellent error handling.
Removed the explicit types. If you use rust-analyzer, which I recommend, the inferred types are inlaid, so you don't need to explicitly define them everywhere:

Added a new feature flag for parquet_async. The async Parquet reader brings in more dependencies than the sync Parquet reader, so it's good to have an option for users to use only the sync version. To complete this process, we need to conditionally compile parquet and async parquet functions only when those feature flags are on.  We currently compile the parquet mod only when the parquet compilation flag is on: https://github.com/geoarrow/geoarrow-rs/blob/50d4acaf7a75e0d355cb6365d59b2933d1f695e2/src/io/mod.rs#L19-L20
I think the best way forward here is to create a new file src/io/parquet/reader_async.rs and in src/io/parquet/mod.rs conditionally compile reader_async.rs only when cfg(feature = "parquet_async"). Note that the parquet/async syntax in the Cargo.toml means "activate the async feature from within the parquet dependency.

Removed the calls to unwrap in favor of the ? (try) operator. unwrap means essentially "assert there was no error", while ? means "continue if there was no error; otherwise propagate the error upwards, immediately returning an error from this function". The ? takes a bit of time to get used to but ends up having really clean code with excellent error handling.

Oh good, my iDE was giving me squiggly red lines under the ? and suggesting to use .unwrap, but I think it was because I was activating the parquet_async feature flag by commenting out the optional statements in cargo.toml locally to get rust-analyzer to work on the file. I think I've set things up a bit better now, so will stick with the ? operator!

Removed the explicit types. If you use rust-analyzer, which I recommend, the inferred types are inlaid, so you don't need to explicitly define them everywhere:

Yep, I've got rust-analyzer set-up, but my IDE (Pulsar) only shows those inferred types when I hover over them. Ok to remove them if you prefer it that way.

Added a new feature flag for parquet_async. The async Parquet reader brings in more dependencies than the sync Parquet reader, so it's good to have an option for users to use only the sync version. To complete this process, we need to conditionally compile parquet and async parquet functions only when those feature flags are on.  We currently compile the parquet mod only when the parquet compilation flag is on: https://github.com/geoarrow/geoarrow-rs/blob/50d4acaf7a75e0d355cb6365d59b2933d1f695e2/src/io/mod.rs#L19-L20

I think the best way forward here is to create a new file src/io/parquet/reader_async.rs and in src/io/parquet/mod.rs conditionally compile reader_async.rs only when cfg(feature = "parquet_async"). Note that the parquet/async syntax in the Cargo.toml means "activate the async feature from within the parquet dependency.

Thanks for setting up that new feature flag! I was wondering yesterday too if async should be enabled by default with the parquet feature or hidden behind a sub-feature flag. I've moved the geoparquet_reader_async function to reader_async.rs at commit 37b0f6cb9e7d09a7bae5160aaf6671f7ffd5a2df, and also the parse_geoparquet_metadata to geoparquet_metadata.rs. Gonna refactor things a bit more later and add some unit tests if possible.

Given how 'big' this PR already is, I'm tempted to bring in object-store in a separate PR. I see that you're already doing some stuff with FlatGeobuf x object-store in #494.

The nice thing is that object store integration can be as little as just documentation. This is because ParquetObjectReaderimplementsAsyncFileReader`. So following this example a user can just do
let storage_container = Arc::new(MicrosoftAzureBuilder::from_env().build().unwrap());
let location = Path::from("path/to/blob.parquet");
let meta = storage_container.head(&location).await.unwrap();
println!("Found Blob with {}B at {}", meta.size, meta.location);

let reader = ParquetObjectReader::new(storage_container, meta);
read_geoparquet_async(reader, options)

Yeah let's work out the Python bits in a different PR. In particular, I think it makes sense to have both an async def read_parquet_async for power users building a web server or something on top of geoarrow, but also a def read_parquet that handles stuff automatically under the hood.
I'm also not exactly sure what public Python API is ideal, so we should come back to that.

Any piece of code that you put in a docstring is automatically a doctest. So it needs to compile and run (and pass) unless you annotate it with notest.


Gemini API should be confirmed

what is this service for?
Its this Gemini Crypto or Gemini Google?

Gemini crypto? No, its Google Gemini's api.

the gemini.ai domain in the link is ASSOCIATED with a crypto business, its very missleading.

I see the confusion. The link is to api.gemini.ai, which doesn’t exist, its
a dummy url. The gemini api doesn’t allow/require a baseurl, so its
basically not relevant. You can confirm this in the code looking at:
workflow/core/api/engines/llm_engines/gemini_llm_engine
On Tue, 10 Dec 2024 at 8:13 AM Pentium10 @.***> wrote:

the gemini.ai domain in the link is ASSOCIATED with a crypto business,
its very missleading.
—
Reply to this email directly, view it on GitHub
https://github.com/MarianoMolina/project_alice/issues/14#issuecomment-2531271700,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADZMG4UZNQSQZX574G2SXB32E3EEJAVCNFSM6AAAAABTGPUQICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZRGI3TCNZQGA
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


Stop leaking memory during serialization

Prior to this commit, serializing a pony object would leak memory.
By using "pool alloc" rather than "pony alloc", we were directly
allocating memory that would need to be manually freed. What we
wanted to do was use "pony alloc" so that the GC would track
usage of the memory and free it when needed.

This fixes #1413


Adding missing --join flags to cross-network example

Fixes #4106.

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/a3b71c4cf04f6d330e46d00673413e3917857d5f/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/fe28ad9f32078907d06a266f5a7357cfcd5486d0/


Missing ~/.config/aws-login/templates.json file is not handled gracefully.

The following checks have been done.

[X] I could not find another bug report that covers what I discovered.
[X] This report does not request new features or enhancements.

What is the current behavior?
The use subcommand produces an error if no existing AWS CLI profiles are found and the profile templates file does not exist.
$ aws-login use
Could not get a list of existing AWS CLI profiles.
  No such file or directory (os error 2)

What is the expected behavior?
The subcommand should detect this scenario and display a more elegant error message.
$ aws-login use
There are no profiles available.

Some additional context.
No response

I am unable to reproduce this issue anymore and I suspect that it has something to do with #14.


Empty request body parsing error for automatic persisted queries

@oprypkhantc I was giving the new persisted queries a go to test the implementation, since I wasn't able to do so prior.  In doing so, I'm running into the following issue.
InvalidArgumentException: Syntax error in body: ""

/srv/www/vendor/thecodingmachine/graphqlite/src/Http/WebonyxGraphqlMiddleware.php:70

This is part of the process method for the middleware, which looks for the request body contents.  For reference, the process method is as follows:
    public function process(ServerRequestInterface $request, RequestHandlerInterface $handler): ResponseInterface
    {
        if (! $this->isGraphqlRequest($request)) {
            return $handler->handle($request);
        }

        // Let's json deserialize if this is not already done.
        if (empty($request->getParsedBody())) {
            $content = $request->getBody()->getContents();
            $data = json_decode($content, true);

            if ($data === false || json_last_error() !== JSON_ERROR_NONE) {
                throw new InvalidArgumentException(json_last_error_msg() . ' in body: "' . $content . '"'); // @codeCoverageIgnore
            }

            $request = $request->withParsedBody($data);
        }

        $context = $this->config->getContext();
        if ($context instanceof ResetableContextInterface) {
            $context->reset();
        }
        $result = $this->standardServer->executePsrRequest($request);
        //return $this->standardServer->processPsrRequest($request, $this->responseFactory->createResponse(), $this->streamFactory->createStream());

        return $this->getJsonResponse($this->processResult($result), $this->decideHttpCode($result));
    }

Was this overlooked?  We need an integration test for persisted queries for sure.  Am I missing something here?

I don't think it's related. This happens way before persisted queries. What is the body and content-type you're sending?
I'd say we need an integration test for the HTTP implementation as a whole. For that, we could do what Apollo Server did and use JS graphql-http server audits: https://github.com/graphql/graphql-http/blob/main/src/audits/server.ts
It'd be nice to just use those as those should be a reference anyway, and those would be true integration tests.

What's nice about graphql-http's serverAudits is that they fully test the compliance with graphql-over-http, so it might find other problems as well.

Seems like all GET requests through WebonyxGraphqlMiddleware are broken. It always attempts to parse the body, which isn't present for GET requests. Again, not related to persisted queries, but graphql-http would have covered that.
An improvement for WebonyxGraphqlMiddlewareTest would be sufficient too.

I've played around with graphq-http audits and sure enough one of the 13 failed tests was this:
● Integration tests › MAY accept application/x-www-form-urlencoded formatted GET requests

    Response status code is not 200: An error occurred: Syntax error in body: ""

@oprypkhantc Yea, the body is empty for a GET request, naturally.  And, the WebonyxGraphqlMiddleware processes the request very early.  Do you know if webonyx/graphql-php needs/expects a request body?  I'm assuming not if this persisted queries are supported.  The middleware is basically assuming webonyx needs a json decoded request body as the parsedBody on the request object.  It might be that all of that logic is unnecessary and can be removed?

Probably unnecessary. I'm pretty sure webonyx handles parsing the RequestInterface all on their own and they definitely don't require request bodies for GET requests.
It'd be nice to offload the whole HTTP handling thing to webonyx/graphql-php, since most of the parsing is already being done on their side. They don't, however, convert ExecutionResults into responses. They have an open issue for that, so maybe it's worth it to just contribute to webonyx/graphql-php instead of writing tests/fixing things here.
If we could offload this to webonyx then we'd not have to worry about fixing this, or testing it, or writing integration tests for the HTTP layer. For now, just adding a few tests to WebonyxGraphqlMiddlewareTest should be plenty though.

So, I was able to run our integration tests for graphql with the request body parsing disabled and all tests are passing.  That parsing and body validation check seems entirely unnecessary.
I am, however, getting the following error now:

GraphQL Request must include at least one of those two parameters: "query" or "queryId"

When making a GET request with a query key on queryParams property.  That's a webonyx error.
I agree with primarily offloading the request handling to webonyx.  I do think it's a good idea that we maintain some minimal integration test coverage for requests though.  I don't think we need anything too extensive, but having some coverage there is wise.

When making a GET request with a query key on queryParams property. That's a webonyx error.

The query parameter must be a top-level query parameter, i.e. /graphql?query=query { __typename }

So, I was able to run our integration tests for graphql with the request body parsing commented out and all tests are passing. That parsing and body validation check seems entirely unnecessary.

It seems like at least 15 of graphql-http tests fail when I comment out that body parsing part, so it seems like it is indeed needed :( Here's one of those:
audit('2C94', 'MUST accept POST requests', async () => {
      const res = await fetchFn(await getUrl(opts.url), {
        method: 'POST',
        headers: { 'content-type': 'application/json' },
        body: JSON.stringify({ query: '{ __typename }' }),
      });
      ressert(res).status.toBe(200);
    }),

Response status code is not 200. Response: [400] {"errors":[{"message":"GraphQL Request must include at least one of those two parameters: \"query\" or \"queryId\""}]}
Changing the check to if (empty($request->getParsedBody()) && $request->getMethod() !== 'GET') { helps.

It seems like at least 15 of graphql-http tests fail when I comment out that body parsing part, so it seems like it is indeed needed :(

Yea, so our boot stack is probably setting the parsedBody already, as we have to parse it for some authorization concerns.  I don't know why that should be necessary though for webonyx.

They don't do any body parsing for requests that implement ServerRequestInterface, and all of the requests that go through WebonyxGraphqlMiddleware are ServerRequestInterface, so webonyx literally never parses request bodies.
The implementation I used (laminas/laminas-httphandlerrunner + laminas/laminas-stratigility) doesn't parse the body either, so I believe that's why the fix is there.

Not sure what you mean by "top-level" here. You mean appended to the actual request URL, as opposed to being a request param on the request object? And why?

You mentioned it being under the queryParams property, so I assumed your query params look like this: queryParams[query]=query { __typename } instead of query=query { __typename }. The latter works for me.

You mentioned it being under the queryParams property, so I assumed your query params look like this: queryParams[query]=query { __typename } instead of query=query { __typename }. The latter works for me.

Here is an except of the dumped request object:
0 => Laminas\Diactoros\ServerRequest^ {#8591
        -attributes: []
        -uploadedFiles: []
        -serverParams: []
        -cookieParams: []
        -queryParams: array:4 [
            "query" => """
                query testAutomaticPersistedQueries {\n
                            company {\n
                                id\n
                                legalEntity {\n
                                    companyName\n
                                }\n
                            }\n
                        }
                """
            "variables" => []
            "operationName" => "testAutomaticPersistedQueries"
            "hash" => "cf5def5f484a49ea52906f038c0176e057a5b305b8a7d87638acfa4581c2c362"
        ]
        -parsedBody: null
        -method: "GET"

Got it. I'm not sure why you're not getting a 200. Here's the test server I use: https://gist.github.com/oprypkhantc/fe173460cce4ccc0e258749b67989479
If you start that with php -S <IP_ADDRESS>:8085 and do GET http://localhost:8085/graphql?query=query{__typename} you'll get a 200 with this response:
{
  "data": {
    "__typename": "Query"
  }
}

See #427 as possibly related issue.

So, I don't know if this is a Laminas ServerRequestInterface implementation bug, or there is something else I'm missing here.  Basically, Laminas' ServerRequest object, which implements the PSR interface and what we use and is mostly used by this lib, has the method withQueryParams, which is just an immutable method, as you'd expect.  That's what gives you the output for the queryParams in the dump above.
However, when digging into webonyx, the query params are build like so...
\parse_str(\html_entity_decode($request->getUri()->getQuery()), $queryParams);

As you can see, it's getting them from the initial Uri, which is initialized at construction and includes the query params properly when appended to the uri string.  Either I'm misunderstanding the purpose of queryParams on the ServerRequestInterface, there is a flaw in the PSR design, such that query params are spread out across multiple objects, making them unreliable, or there is a Laminas implementation issue in the spec.
Any ideas on this?  I can obviously instantiate a new ServerRequest object from a built concatenated string and force this to work.  But, now I'm wondering what's going on with all this...


Page header styling updates

This PR cleans up the page header styles and applies them to the new components. It also adds the SidebarToggle component from the old page header. :arrow_left: :arrow_right:

Looks nice 👍

So g👀 d! ✨


netease-cloud-music-gtk: 2.0.3 -> 2.2.0

Description of changes
The current version of this package in Nixpkgs doesn't launch, but is fixed after update:

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 247062 run on aarch64-darwin 1

Result of nixpkgs-review pr 247062 run on aarch64-darwin 1

1 package built:

netease-cloud-music-gtk

What's wrong on darwin? Did you test x86_64-darwin?

The package does build, but with no opening window on macOS.