Android can't receive push notification

I configured the push notification and I tried it via Flurry Push.
And, I got the push notification on iOS. But I can't receive the message on Android.
I tested the push notification via Firebase and I got the message and show it well on Android. But, via Flurry Push, the message is not shown.
I did,

I didn't,

And, I used the following code.
Flurry.builder
      .withCrashReporting(true)
      .withLogEnabled(true)
      .withLogLevel(LogLevel.debug)
      .withMessaging(true)
      .build(
        androidAPIKey: "XXXXXXXXXXXXXXXXXXXXX",
        iosAPIKey: "XXXXXXXXXXXXXXXXXXXXX",
      );

Do I miss something?

@dev-yakuza From my experiences of getting the Firebase Cloud Messaging to work, the "newly added" app in the Firebase Project Settings, you need to cold-start run the app 2 or more times to "activate" the messaging feature.

@dev-yakuza BTW, how did you test your app and found the Flurry messaging is not working? You need to test it by providing the token or Ad ID, as you asked in another ticket, https://github.com/flurry/flutter-flurry-sdk/issues/15.

@poting-oath

@dev-yakuza BTW, how did you test your app and found the Flurry messaging is not working? You need to test it by providing the token or Ad ID, as you asked in another ticket, #15.

I just used the real device. I mean, I deployed the app to the Google Play Store beta.
And, I really sent the message via Flurry push.

@dev-yakuza From my experiences of getting the Firebase Cloud Messaging to work, the "newly added" app in the Firebase Project Settings, you need to cold-start run the app 2 or more times to "activate" the messaging feature.

Is this way for the emulator? In the real device, do users need to reboot devices? 🤔
I did,

deployed the app to the beta of Google Play Store.
Send the message via Flurry push(not test sending, really send the message).
The message is not shown
I tried to send the message via Firebase.
I got the message.
And I thought that the settings is OK, so I tried to send the message via Flurry again.
But the message is not shown.

@poting-oath
I got the push token from #15, and I tried to send the message with it via Flurry push.

It looks like the message is sent well, but I couldn't see it.
I tried to use the example code on #15 and I got the log like the following.
I/flutter ( 6774): Flurry Messaging Type: onNotificationReceived
I/flutter ( 6774):     Title: 1
I/flutter ( 6774):     Body: 1
I/flutter ( 6774):     ClickAction: null
I/flutter ( 6774):     Data: {fl.Data: {"fl.VariantID":0,"fl.InstanceID":0,"fl.CampaignID":-1}}

So, it looks like the message is received well, but not shown on the notification bar.
I tested it on the emulator and real device with the example code and without the code and foreground and background app.
But, all of them don't show the message.
What am I missing? 😭

@dev-yakuza Looks like the messaging is received successfully. Make sure the app is in the Background mode, and onNotificationReceived returns false if you provide the listener.
     @override
     bool onNotificationReceived(Message message) {
         printMessage('onNotificationReceived', message);
         return false;
     }

And make sure your app allows Notification (with permission). Also try to make the Title and Body with more words (not sure whether it will cause any issue or not by the Android platform.)

@dev-yakuza I think your app's Notification has been grabbed completely by Firebase since your codes use
await Firebase.initializeApp();
...
static FirebaseAnalytics analytics = FirebaseAnalytics.instance;

@poting-oath
Thanks for your info. I tried to remove the code and send the message via Flurry.
But it is not working too. 😭

@poting-oath
I decide to use Firebase for messaging. Thanks for your time. 🙇

Unfortunately Firebase cannot be use together with Flurry because it overrides the platform!


What are the advantages of gathering facts beforehand ?

Is your feature request related to a problem? Please describe
I have been modifying a local version of pyinfra in order to solve different issues (some of them posted as github issues here), and I came to the conclusion that there is not much advantages in gathering facts before operations.
Actually, most of the limitations and weird behaviors I see would be solved by gathering facts along the way.
I would be interested to discuss to pros and cons and contribute in modifying the way pyinfra work if necessary.
Describe the solution you'd like
I have a small list of the advantages of gathering facts before operations that requires them:

Since there is no need to come up with a list of facts to gather beforehand, the whole problem of ordering operations goes away. Especially, the code that browse the stack to come up with operation order is unnecessary, and this code does not output the correct order in several cases.
There is no need for the preserve_loop_order magic anymore. It was anyway very counter-intuitive to have operations in loops not executed in the expected order.
Most usage of assume_present arguments becomes unnecessary since facts will reflect the correct state of the machine right before an operation is performed.
The execution flow is easier to understand, for example, simple things like creating a directory and checking if that directory exists would simply works.
The whole concept of nested operations is moot or becomes very limited. It seems the main use case was to run an operation, get the output and perform more operations based on the output. But with facts gathered along the way, the output of the command is available immediately and conditional logic can be written directly within the main python script (instead of the callback).
The is no need to support dynamic facts, since facts are dynamic by default.
We can still operate a cache to make sure facts are not gathered unnecessary and, just like ansible, provide ways to invalidate the cache for arbitrary operations like server.shell.

Thank you for writing this up @julienlavergne - this has recently been on my mind also. I'm going to document the context of why this is the case below (this will be long I think :)), and give my thoughts.
Firstly, let's split the problem into two distinct parts:

Ordering operations correctly
Gathering facts on operations (pre-execution vs. execution)

Historical Context
Prior to v2, pyinfra relied on line-number ordering and pre-execution fact gathering to achieve it's high performance. The reason for this is that operations were generated on hosts sequentially, rather than in parallel. As facts were required, they were gathered in parallel on all hosts (whether or not they need the specific fact). For example:
# inventory.py
web_servers = ["web-01", "web-02"]
db_servers = ["db-01", "db-02"]

# deploy.py
if host in inventory.get_group("web_servers"):
    files.file(path="web-file")
else:
    files.file(path="db-file")

To generate the commands to execute the following would happen (v0.x, v1.x):

Connect to all 4 servers in parallel
For each server sequentially:
a. execute deploy.py with host set to that server
b. as facts are required (files.File), load them on all 4 servers in parallel
Now we have our operation order & commands to run
Execute all the operations in parallel across the hosts

Because facts were loaded in parallel (2.a), each iteration of 2 got quicker and quicker as most/all facts were pre-cached for the current host. This is why facts were(are) gathered before execution.
The above example also highlights why operation order is generated from line numbers - because the same code (deploy.py) is executed for multiple hosts, the order in which operations are called is inconsistent. In the above example the user expects execution flow to behave like:

Execute files.file(path=web-file) on web-01 & web-02
Wait for completion of 1
Execute files.file(path=db-file) on db-01 & db-01

By taking operation order as they are called this would not be possible. Note: this does not affect deploys against a single host target, where operation call order would work.
What can we do now?
Back to v2 and your points above, I'll split my thoughts into the two problems above:
Operation ordering

Since there is no need to come up with a list of facts to gather beforehand, the whole problem of ordering operations goes away. Especially, the code that browse the stack to come up with operation order is unnecessary, and this code does not output the correct order in several cases.
There is no need for the preserve_loop_order magic anymore. It was anyway very counter-intuitive to have operations in loops not executed in the expected order.

Unfortunately I don't think we can avoid this without breaking operation execution flow, particularly where there are multiple code paths for different hosts involved in a deploy. The line/stack ordering enforces "correct" ordering - except loops and context processors. The general assumption being that deploy files are generally "simplified Python" consisting of operation calls, conditional statements and functions. I'm not a fan of this gotcha and would be keen to investigate alternatives!
While I don't see a way to remove the line ordering mechanism, I would like to have it automatically handle loops and context processors if possible. In v0.x pyinfra would modify the ast of deploy code before execution to achieve ordering without line numbers and that may be a workable solution. Alternatively it might be possible to modify the loop detection code to automatically re-order them as expected.
Fact gathering

The whole concept of nested operations is moot or becomes very limited. It seems the main use case was to run an operation, get the output and perform more operations based on the output. But with facts gathered along the way, the output of the command is available immediately and conditional logic can be written directly within the main python script (instead of the callback).

Because of the operation ordering issue, it's still not possible to provide output from an operation immediately. The deploy code must be run once before any operations are actually executed to generate the order, which unfortunately makes it impossible to have the output included.

Most usage of assume_present arguments becomes unnecessary since facts will reflect the correct state of the machine right before an operation is performed.

I would absolutely love to remove this, it's a real pain and a massive gotcha. v2 makes it entirely possible to do by having operations (re)collect facts at execution time. The only drawback is the list of changes pre-execution may not be correct; ie if you do a dry run deploy first you expect the number of commands proposed to match those executed, and collecting facts at execution may break this. One option could be to display "up to X" commands per operation, because we can make reasonable assumptions that certain facts will change (files) and others will not (system OS).
Thoughts
Collecting some thoughts below on the more general philosophy of pyinfra and how it works.
I do think the "dry run" pyinfra offers is a powerful tool that has a lot of unused potential. On a basic level pyinfra could support terraform style approval steps. Even more interesting would be the idea of creating a diff file that can then be moved somewhere else for execution - pyinfra needn't even be the tool doing the execution.
The whole two-stage deploy mechanism has consistently provided complexity over the last 7(!) years, but has also enabled writing almost-normal Python code to generate operations that execute in a similar way to tools like Ansible. I've yet to encounter something that wasn't possible (but have seen things not possible in other tools). Examples & documentation would help a lot here I think.
Today pyinfra seems to be a hybrid of a Ansible/SaltStack-like mostly-state-base ddeployment tool and Fabric/Parallel-SSH command execution tool. This is definitely both an advantage in terms of high flexibility but also a disadvantage because it comes with some gotchas that make it "almost like Python" at times.

I hope this provides some context, please let me know if anything doesn't make sense and would love to hear thoughts from any pyinfra users on the above. Ultimately I think any changes to these systems are on the table assuming enough support and technical possibility :)

Coming back on your example:

Connect to all 4 servers in parallel
For each server sequentially:
a. execute deploy.py with host set to that server
b. as facts are required (files.File), load them on all 4 servers in parallel
Now we have our operation order & commands to run
Execute all the operations in parallel across the hosts

The flow I am referring to is the following:
In parallel on all 4 servers:

Connect the the host
Execute deploy.py, which gather facts and run commands along the way

If I take the different points you mention, I think they can call be supported with this flow:

Dry Run: Seems to be trivially supported by running the deploy.py without executing the commands. You can even have a dry_run variable set to true for that purpose that user can inspect in order to adjust the execution in case of dry run.
Speed: It is not slower than the current flow, since everything is done in parallel.
Multiple code paths for different hosts: It does no matter what deploy.py contains for different hosts, the execution is totally independent on every hosts.
Operation order is correct per host according to expected python execution order, and it supports all python features. There is no attempt to synchronize operations across hosts except at the end, if one host finish before others, very well.

Multiple code paths for different hosts: It does no matter what deploy.py contains for different hosts, the execution is totally independent on every hosts.
Operation order is correct per host according to expected python execution order, and it supports all python features. There is no attempt to synchronize operations across hosts except at the end, if one host finish before others, very well.

The problem with doing this is it breaks a number of scenarios in which the order across multiple costs is essential. Really anything involving a control / worker node setup. For example bootstrapping an Elasticsearch cluster might look like:

Install ES apt package on all four nodes control-1, data-1, data-2, data-3
Setup config on all fur nodes
Start ES with some init config on control-1
Wait for this to complete, then start ES on the three data nodes

There are many similar examples of this where operations on one node must complete before operations on another. The operation order as it currently exists handles this.

Pyinfra is not the right tool for that. I am doing similar things on my side, and there is better ways to do it than pyinfra.
Setup/configuration and actually deploying/running an application are two different things that comes with their own challenges and pyinfra is not equipped at all to deal with the challenges of bringing a cluster of applications up.
Typically, bringing up an ES cluster need to deal with scenarios where you add/remove nodes to the cluster, handle failure cases if the master fails, rollback to a previous working state etc..
Regardless, if such a case happen, pyinfra could expose an interface to synchronize the execution across all hosts at any time during execution. asyncio does provide the necessary synchronization mechanisms for that.
I imagine this is not going to be a very popular feature. I have the feeling that mass configuration of multiple independent host in parallel is much more common.

I can absolutely say pyinfra works incredibly well for the ES use case, it's one of the places it was first used at scale within a company environment to manage tens of large (300+ node) clusters.
I am aware of its use in production today for all sorts of setups including ES, MariaDB and Kubernetes clusters. The operation ordering is relied upon to provide consistent idempotent deployment of these services. Because of this ops like adding/removing nodes can be achieved simply by updating the inventory and re-running.

I think at least the following would be difficult with single-run execution:

the 'same'[1] operation on each host:

cannot be displayed as a group in the summary output (a)
cannot be interactively be approved/disapproved as a group (b)

synchronization of inter-host dependent operation is more difficult (c)
generating a diff file for later execution (d)

The 'same'[1] operation cannot be grouped in the output (a)
We could use some command line ANSI magic to update previously printed operations for hosts that have now also hit them. This might look something like:
--> Starting operation: Apt/Packages (packages=['vim'])
    [host-1] No changes
    [host-2] *executing* <insert loading animation here>

--> Starting operation: Apt/Packages (packages=['vim'], present=False)
    [host-1] *executing* <insert loading animation here>
    [host-2] *waiting for execution* <insert loading animation here>

...2 seconds later...
--> Starting operation: Apt/Packages (packages=['vim'])
    [host-1] No changes
    [host-2] Success

--> Starting operation: Apt/Packages (packages=['vim'], present=False)
    [host-1] Success
    [host-2] Success

The 'same'[1] operation cannot be interactively approved/disapproved as a group (b)
While not ideal, this could be solved with a synchronization key:
burn_server_op_name = 'Set server on fire'
if host in inventory.get_group("flammable_nodes"):
  pyinfra.operations.server.burn_server(name=burn_server_op_name, appoval_needed=True)
else:
  pyinfra.operations.skip(name=burn_server_op_name)

--> Starting operation: Burn server (key='Set server on fire')
    Do you want to continue with 'Set server on fire' with the following changes:
    [host-1] Success: <some information about the planned execution>
    [host-2] Success: <some information about the planned execution>
    [host-3] Skipped
    Continue? [y/N]

The key could just be name, or it could be something separate like key or sync_key.
Inter-host dependent operations (c)
As @julienlavergne pointed out this could be solved using a synchronization API:
if host in inventory.get_group("control_nodes"):
  # control stuff (1)
else:
  # data stuff

pyinfra.wait(key = "Wait for control-1")

if host not in inventory.get_group("control_nodes"):
  # data stuff that depends on (1) ("start ES on the three data nodes")

asyncio.Event doesn't need key because it's used in the same execution context. The different host runs of pyinfra however do not share the same context (I think?).
I think using a key is fine, but we could move per-host code into the same context like so:
control_done_event = asyncio.Event()

async def deploy(host):
  if host in inventory.get_group("control_nodes"):
    # control stuff (1)
    control_done_event.set()
  else:
    # data stuff
    await control_done_event.wait()
    # data stuff that depends on (1) ("start ES on the three data nodes")

Where this file is executed once and then deploy is called for each host. This calling for each host could event be delegated to the the deploy file itself:
await asyncio.gather(deploy(host) for host in hosts_to_execute_magic_variable)

Although I don't know how pyinfra would be able to figure out which host an operation is being executed for.
Generating a diff file for later execution (d)
For this one I cannot really think of a solution.

[1] I guess operations called with different arguments are considered the same.
P.S. Amazing project, thanks for all the hard work! :heart:

I’m convinced, it has become clear the disadvantages and confusion of the current execution strategy outweigh the advantages.
To remedy this I am proposing that pyinfra v3 will switch to executing operations and facts live. It will also be able to retain diff functionality simply by collecting facts twice if so desired. I’ve started working on this in #996, is working but tests/etc are not.


Remove references to Gaurav Chaurasia from Han Liu's webpage

This removes metadata like author name, facebook username, and google scholar account ID. Also removes statcounter website tracker which is used by Gaurav Chaurasia in his website.

Please accept this file change so that traffic to your webpage is not counted in my webpage's analytics.

Thank you for your commit!


Change setup info to https github link

I could only clone the starter with
gatsby new PROJECTNAME https://github.com:greglobinski/gatsby-styled-blog-starter.git

You are right, https is a recommended way. Done, thanks.


PT Run input not active when PowerToys run is started the first time

Microsoft PowerToys version
0.47.0
Running as admin

[X] Yes

Area(s) with issue?
PowerToys Run
Steps to reproduce
Pressing my hotkey Alt + Space does not make the run command active. I have to actually use the mouse and click the input box to type.
✔ Expected Behavior
An active input box
❌ Actual Behavior
Input box isn't active by default.
Other Software
QuickLook V3.6.11
Logitech Options +

Only the first time, every time I load up Windows.
Thanks,
John Kappa
Designer & Creative Artist
Mobile +61 (0) 419 519 823 / Instagram
https://www.instagram.com/johnkappa/
perceptiondesign.com http://www.perceptiondesign.com/ / johnkappa.com
On Thu, 7 Oct 2021 at 01:23, Jaime Bernardo @.***>
wrote:

Also, is this only on the first time or every time?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/13643#issuecomment-936330056,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKTH2PNECML5TSUK4JDBSQLUFRLVJANCNFSM5FNPKRXA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@j-kappa It seems like you are replying using email, but the attachment won't be sent through email. Please login to github.com and drag and drop your report to the comment to upload it. Thanks!

PowerToysReport_2021-10-11-19-33-27.zip

Had the same problem — Fixed it somehow just a moment ago after filing the duplicate bug report (#14469). My solution: Although I activated “Always run as Administrator” in the general settings of PT, windows never actually started it as admin. I had to manually activate it via the Windows file properties of the .exe at C:\Program Files\PowerToys (standard install location). Now it first launch of search field of PT Run works as expected. It should be noted, that my current windows installation had some severe permission and rights issues some time ago, which I fixed via trial and error (power user ≠ power knowledge). Surely the main error source in my case.

PowerToysReport_2021-11-21-19-33-36.zip

One thought, what is the keyboard hook system. Is this the low level or register?

According to the bug reports we've received, it should be registered hotkey for @j-kappa.
@Bugrakca  was using the registered hotkey but has since changed to the centralized keyboard hook.
[2021-11-21 13:50:38.7309] [INFO] [S:\src\modules\launcher\PowerLauncher\ViewModel\MainViewModel.cs::762]
Registered global hotkey

[2021-11-21 19:33:07.9637] [INFO] [S:\src\modules\launcher\PowerLauncher\ViewModel\MainViewModel.cs::751]
Using the Centralized Keyboard Hook for the HotKey.

i know with islands we had issues with forcing first time focus but with the shift over to wpf, i thought this issue was solved.  My theory was flipping to reg'ed hooks versus low level caused this.

I restore the defaults but it is still the same.  Here's my zip file. Version: 0.51.1
PowerToysReport_2021-12-05-14-57-05.zip

I can repro this with .53

Repo case:
https://github.com/microsoft/PowerToys/issues/14606#issuecomment-1012177157

I have the same issue.
PowerToysReport_2022-02-28-21-29-03.zip

I have the same issue on v0.56.
https://user-images.githubusercontent.com/33951993/156915201-c06ff8da-1f2c-44b6-adc3-bb6da97a62a7.mp4
1

Run is one of the best features in Power Toys and this old issue prevents a reliable usage of it. Sometimes we wait 3 or more seconds to realize that the cursor is not there and that we are typing to nowhere.

Confirming that v0.57 fixed this issue for me. Thanks @jaimecbernardo this fix is much appreciated!

After v0.57.0 the problem has not recurred.

It looks like v0.57.0 has fixed the bug for me too.
Thank you!

After v0.57.0 the problem was solved.
Thanks.

Thank you! Working like a charm!


feat: D support

Grammar: https://github.com/gdamore/tree-sitter-d
I will attempt a PR, but i'll need to figure out the code base first

i'll work on this later today


Shake telling me to replace import that is necessary.

In PR #11542, which splits off a Data.List.InsertNth file from Data.List.Basic I am experiencing the following CI error
/usr/bin/env LEAN_ABORT_ON_PANIC=1 lake exe shake --gh-style
info: [1/3] Building Shake.Main
info: [2/3] Compiling Shake.Main
info: [3/3] Linking shake
Warning: ./././Mathlib/Data/List/Lemmas.lean:[7](https://github.com/leanprover-community/mathlib4/actions/runs/8366890818/job/22908083269?pr=11542#step:23:8):1: warning: unused import (use `lake exe shake --fix` to fix this, or `lake exe shake --update` to ignore)
Warning: ./././Mathlib/Data/List/Lemmas.lean:[8](https://github.com/leanprover-community/mathlib4/actions/runs/8366890818/job/22908083269?pr=11542#step:23:9):1: warning: import #[Mathlib.Data.List.Basic] instead
./././Mathlib/Data/List/Lemmas.lean:
  remove #[Mathlib.Data.List.InsertNth]
  add #[Mathlib.Data.List.Basic]
Error: The process '/usr/bin/env' failed with exit code 1

But this is definitely not right. insertNth_succ_cons, for example, is used in Lemmas, and was moved to the new file, so it is necessary to import the file, and if the old file is imported instead, there is an error.
I am just going to run the recommended command, but someone should get to the bottom of this error.

Here is me trying to run the lake exe shake --update command as I was told to.
boltonbailey@starlight mathlib4 % lake exe shake --update
info: [1/3] Building Shake.Main
info: [2/3] Compiling Shake.Main
info: [3/3] Linking shake
There are out of date oleans. Run `lake build` or `lake exe cache get` first
boltonbailey@starlight mathlib4 % lake exe cache get
Attempting to download 2821 file(s)
Downloaded: 2821 file(s) [attempted 2821/2821 = 100%] (100% success)
Decompressing 4333 file(s)
unpacked in 3293 ms
boltonbailey@starlight mathlib4 % lake exe shake --update
There are out of date oleans. Run `lake build` or `lake exe cache get` first
boltonbailey@starlight mathlib4 % lake build
... Starts building thousands of files

It is a bit annoying that I have to build all of this to fix this problem.

If you run shake with out of date oleans, it will give very wrong answers, so yes it is a prerequisite that you have up to date oleans. Usually you would already have them available assuming you are fixing a shake error reported in CI, because CI has to build the oleans before running shake anyway.

Hmm, that's interesting. As you can see, I did run lake exe cache get. Shouldn't that have retrieved the oleans I needed to make this error message not appear?

This issue is stale, closing. (Lots of things have changed in shake since this was written, if it still occurs please give a new reproduction.)


Undefined constant 'STDIN' when run 'tenants:seed' command on production mode

When the SeedDatabase Job has been called on production, the "undefined constant 'STDIN'" has fired.
If you added the --force option on this command and another commands like that are running programmatically, it will be great.
This line of code

https://github.com/archtechx/tenancy/blob/3.x/assets/config.php#L197

Thank you


Add Kubernetes Dashboard installation

this could be useful to see the entire cluster information via GUI. see https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/

there seems to be big change for secret generation, https://itnext.io/big-change-in-k8s-1-24-about-serviceaccounts-and-their-secrets-4b909a4af4e0

addressed by https://github.com/fujitatomoya/ros_k8s/commit/15f4e79d4eb1100f775509b990b025e2372215e3


[Marker.io] Mobile/tablet: I think we should correct the order of locations under locations filter

Steps to reproduce:

click filter
notice location values and order
3 ) compare with desktop or the locale modal

Actual result: order on mobile is different
Expected result:
It should be same as that of desktop or locale modal as countries on those are ordered based on importance

Reported by: Vinod<EMAIL_ADDRESS>- Contact via Marker.io
Source URL: https://na13-prezzee.webflow.io/en-us/case-studies
Issue details: Open in Marker.io
Device typetabletBrowserSafari 17.7Screen Size768 x 1024OSiOS 17.7Viewport Size768 x 985Pixel Ratio@2x

needs to be done "blogs" page too


can not use in ob mobile could you solve it？

can not use in ob mobile could you solve it？
the message is that
"Failed to load plugin sheet-plus"

I see the same

Currently, this feature does not fully support mobile devices. We recommend using it on a PC for the best experience.

tjank u for u reply，parhaps i just I hope don't have to migrate all the functions to your phone, just read it, simply fill in the numbers or text, slide to select + sum, average, and save it. This will be much more user-friendly and can be used on all platforms. In the past, the old version of Excel could be opened on the mobile phone and read the file, but the swiping was not smooth, and the summing could not be selected efficiently.

fix 1.3.1


[FLOC-3247] Retry the Docker installation step.

Fixes https://clusterhq.atlassian.net/browse/FLOC-3247

Some tests failed but only after the code this PR changes ran.  However, none of the tests actually triggered the retry logic either so I wouldn't say CI has demonstrated this change is achieving the desired result.

Yes. I was going to say, it would be nice to see this code take effect. However, the code does work in the non-error case, so presumably it could only be incorrect in the failure case. Since that is no worse than currently, and the code change looks correct, I think this is okay to merge once this is green.

Woo.  Your logic is lovely.  Merging.  Thank you.


App crash

pod version GoogleMaps (3.8.0)
https://stackoverflow.com/questions/52182577/ios-google-maps-sdk-crashing?rq=1

Hi @kushalpal17, sorry that you are seeing a crash in your app. Since it's not related to this library (iOS utils), the open issue in https://issuetracker.google.com/113978690 would be the best place to receive support.


How to use this plugin on node + vite bundle when using with type module

Newbie here. Sorry for disturbing.
Trying to use this plugin with node using vite as bundler
after npm install ..
¿how do i proceed to use the plugin?
Tried with
import { showToast } from 'bootstrap';
or
import bootstrap from 'bootstrap' ;
but on build always get same error:
error during build: RollupError: "default" is not exported by "node_modules/bootstrap/dist/js/bootstrap.esm.js", imported by...
Been googling around but cannot figure out how to find the answer
Thank you very much

Hi, you can import ist class as done in the demo page https://shaack.com/projekte/bootstrap-show-toast/

Hi @cancrexo, because showToast is not an ES6 module you could just import the file with import "./src/bootstrap-show-toast.js", then you should be able to bootstrap.showToast().
<script type="module">
    import "./src/bootstrap-show-toast.js"

    document.getElementById("button-show-simple").addEventListener("click", function () {
        bootstrap.showToast({body: "Hello Toast!"})
    })
</script>


Armor Weird ness and blocks

whene if got EnderZoo-1.7.10-<IP_ADDRESS> installed
http://postimg.org/image/k0rcvp7bx/
Weird Armor rendering and you can see lines on the brick stairs.
Whene i install EnderZoo-1.7.10-<IP_ADDRESS> everything is normal.
p.s   using EnderIO-1.7.10-<IP_ADDRESS>2_beta.jar too
Forge is <IP_ADDRESS>0
Log http://paste.ee/p/eFAgF

I'm getting this problem as well. It seems that when items rendered a certain way, every pixel is drawn as a separate block.
Problem introduced after updating Ender Zoo from <IP_ADDRESS> (apparently past .25) to <IP_ADDRESS>.
Displays fine on initial world load, but doing a search in NEI triggers it.
Before, no issue: http://i.imgur.com/E50ZCny.png
After, glitched: http://i.imgur.com/4T8gekv.png

I've been trying to track down which mod was causing this for a few days now lol. Never suspected Ender Zoo. Snow biomes were looking terrible with this bug! Thanks for the fix, much appreciated:)


Scroll gets stuck when using scrollbar or dragging touch

Duplicate Check

[x] I have searched the opened issues and there are no duplicates

Describe the bug
When running the app in standalone mode, the scrollbar gets stuck and unresponsive (it makes little jumps each time you drag it). The same happens when you touch scroll by swiping up or down, it moves an step and stops abruptly.
Note 1: Scrolling works fine and smoothly in WEB BROWSER mode, it only happens when running as an standalone app.
Note 2: Scrolling with the mousewheel also works fine.
Code sample
Code
import flet as ft

def main(page: ft.Page):
    page.title = "GridView Example"
    page.theme_mode = ft.ThemeMode.DARK
    page.padding = 50
    page.update()

    images = ft.GridView(
        expand=1,
        runs_count=5,
        max_extent=150,
        child_aspect_ratio=1.0,
        spacing=5,
        run_spacing=5,
    )

    page.add(images)

    for i in range(0, 60):
        images.controls.append(
            ft.Image(
                src=f"https://picsum.photos/150/150?{i}",
                fit=ft.ImageFit.NONE,
                repeat=ft.ImageRepeat.NO_REPEAT,
                border_radius=ft.border_radius.all(10),
            )
        )
    page.update()

ft.app(main)

To reproduce

Run GridView example from Flet Docs in standalone mode
Try to move the scrollbar or drag touch the screen to scroll through the grid
Notice how it doesn't scroll smoothly and does little jumps / stucks each time an scroll action is triggered from the scrollbar or touch dragging.

Expected behavior
Smooth scroll when using the scrollbar or dragging touch (in this case with a touch screen on windows)
Screenshots / Videos

Screen capture:
https://github.com/user-attachments/assets/c26519b1-d525-405b-8ca1-6c2b917ae263

Operating System
Windows
Operating system details
Windows 11
Flet version
0.24.1
Regression
Yes, it used to work in a previous Flet version (please specify the version in additional details)
Suggestions
No response
Logs
Logs
[Paste your logs here]

Additional details
In 0.23 the scrollbar worked smoothly but the touch dragging still had this bug.
In 0.24 neither of the two works.

Yes bro same thing happens to me

I am also getting this issue - would be nice to have a fix

@Siva-Rajan-R @HenryNomeland provide specifications (OS, Flet version etc).

this is true I am on Windows 11 64 bits I code with the latest versions python, flet, I can add to this recent bug the fact of not being able to use the mouse in horizontal scroll

adding to that thank you in advance for your incredible library

Comment
The same for me.
Android: On Android, in the Flet app, it works smoothly.
Windows 11: On Windows 11 in the desktop version, scrolling jumps only once by a small amount when moving up or down. The same thing happens when I try to scroll with my finger on the touch screen.
Operating System
Windows
Operating system details
Windows 11
Flet version
0.24.1

@HenryNomeland windows os flet 0.24.1

Same for me.
While dragging it stops, and only jums when you click other place of the scroll.
https://github.com/user-attachments/assets/136dafb4-5631-495d-8eed-c07354e15417
Operating system details
Windows 11
Flet version
0.24.1

PR here


Traefik dashboard basic auth keeps asking

This is my first server where I am running demyx so I might be missing something. I have ran the host install a couple times to make sure I have the correct credentials. However, every time after I enter the username and password, the prompt pops up again and I don't get access to the Traefik dashboard.
Any troubleshooting ideas would be much appreciated.

I think it's due to the password being too long. Will have a fix in 1.3.0, so until then try removing a lot of the characters in the generated password.

I think it's due to the password being too long. Will have a fix in 1.3.0, so until then try removing a lot of the characters in the generated password.

Thanks for your reply! Are you suggesting trial and error to figure out how many characters of the password to use? Or is there a way to change the autogenerated password?

You can directly edit the file that the demyx container uses. Edit DEMYX_HOST_AUTH_PASSWORD by using the commands:
demyx host edit && demyx host restart

In the next release, I will automatically restart the demyx container after demyx host edit gets executed.

This issue is still a problem as i clean installed on 12/19/2020 and had the same problem until i found this closed issue and the manual password change resolved the loop, was this issue supposedly fixed??

Hi @johnkennyuk the issue isn't fixed it, sorry. It will be fixed in version 1.3.0.

Thanks


Please remove * in .dockerignore

this will lead COPY command in Dockerfile not work.

AFAIK the Docker build is working just fine as we do include the bin.


[Windows] Encoding feature request / Potential bug with using CLI

Hello,
I've had issues getting translateLocally to output into my desired encoding on Windows 10.
No matter if I use CMD, Powershell or Git after converting the console to UTF-8, it doesn't output in UTF-8 or breaks the translation.
I have also tried the new Powershell that is in UTF-8 mode on default. No difference.
Interestingly, the language pair used seems to impact what encoding is set.
For example;
echo "Hola, cómo estás?" | ./translateLocally -m es-en-tiny -o output.txt
Results in an UTF-8 encoded txt with "Hello, cousy are you?" (Broken translation but correct encoding)
echo "Hello, how are you?" | ./translateLocally -m en-es-tiny -o output.txt
Results in an ANSI encoded txt with "Hola, cómo estás?" (Perfect translation but wrong encoding)

Ticking the box to use UTF-8 for worldwide language support fixes all of these problems. Unfortunately, that is not an option as this is meant to work out of the box for the users..

Any ideas of what is going on here?
I am not sure how translateLocally picks what the encoding will be. Does it just automatically read what the OS uses?

Hmmmm, that seems to be a windows only issue ;/ See the output on a Linux box:
% echo "Hola, cómo estás?" | ./translateLocally -m es-en-tiny
Hey, how are you?

The translations are not broken, likely because translateLocally expects UTF-8 input but it gets fed UTF-16 which is the default on windows.
Also, if you are outputting English, ANSI is a subset of UTF-8 so you're not seeing the difference there. On Linux we output UTF-8:
% echo "Hello, how are you?" | ./translateLocally -m en-es-tiny -o output.txt
% file output.txt
output.txt: Unicode text, UTF-8 text
% cat output.txt
Hola, cómo estás?

I don't have a windows machine, but there's some SO topic, does this make sense to you?:
https://stackoverflow.com/questions/71400245/how-can-i-best-use-utf-8-for-text-in-windows-program-development

Smells like stdin/stdout isn't opened with the correct encoding https://peps.python.org/pep-0528/
Native messaging should be OS independent.

It might be we have to use setConsoleOutputCP and setConsoleCp
https://lists.qt-project.org/pipermail/development/2020-May/039421.html
https://learn.microsoft.com/en-us/windows/console/setconsolecp
https://learn.microsoft.com/en-us/windows/console/setconsoleoutputcp
This is easy enough to test but i don't currently have a windows machine to build on

@Godnoken i've pushed a small fix that may or may not work. Once GithubCI automatically builds everything, it will perform the release and you can grab the new windows executable from here and let me know if it behaves any differently: https://github.com/XapaJIaMnu/translateLocally/releases/tag/latest

It's ok, I love ifdefs. I also need to try harder to test qt5 before I push... I also tried to move the windows builds to qt6. It didn't work a year ago, hopefully someone fixed the vcpkg packages...

As long as the CLI you use is set to UTF-8, translation is now correct & encoding works as it should on the fixed Qt5 build.
As for downsides of defaulting, I wouldn't know any, but I doubt I'd be qualified to answer that question, hehe.
Many many thanks for the quick fix, been struggling with this for a while now thinking that the problem wasn't on translateLocally's end.

Using translateLocally with the standard CMD or Powershell (set to ASCII) doesn't work, but I assume that it should break.
When you say doesn't work, do you mean that the old behaviour is preserved in this case?

When you say doesn't work, do you mean that the old behaviour is preserved in this case?

Not exactly..
echo Hello, how are you? | .\\translateLocally -m en-es-tiny -o output.txt ->
CMD: Hola, cómo estás?
PowerShell: ^ Same
echo Hola, cómo estás? | .\\translateLocally -m es-en-tiny -o output.txt ->
CMD: Hello, c mo est s?
PowerShell: Hello, c?mo est.

Could you also post what exactly you set in the powershell or the CMD so that i can add it to the README?

PowerShell: $OutputEncoding = [Console]::InputEncoding = [Console]::OutputEncoding = [System.Text.UTF8Encoding]::new()
CMD: chcp 65001


Webserver not working in Ubuntu 16.04

When I try to use: dasht-server
I get the following response:
http://<IP_ADDRESS>:54321
/home/otis/Developer/dotfiles/vendor/dasht/bin/dasht-server-http: 81: shift: can't shift that many
2016/11/21 22:33:01 socat[28881] E write(6, 0x24d4870, 1294): Broken pipe
awk: write failure (Broken pipe)
awk: close failed on file /dev/stdout (Broken pipe)

Cheers.

Interesting.  Could you please add set -x; in front of line 80 and re-run the script?
I need to see the value of $url and why it apparently lacks printable characters.
Also, what operating system and what version of awk, shell, coreutils are you using?

Hey @sunaku do you mean like this?
  IFS='?&'
  set -x
  set -- $url

This does not seem to work?
OS: Ubuntu 16.04
awk: mawk 1.3.3 Nov 1996, Copyright (C) Michael D. Brennan
shell: fish, version 2.3.1
coreutils: Version: 8.25-2ubuntu2
Sorry would try to be more help with the debugging but this is way above and beyond any shell scripts I have worked with.

Thanks for the information. :+1:   Let's try an alternative debugging approach:

Append an x to the end of the first line of bin/dasht-server-http so that it looks like this:
 #!/bin/sh -ex

Run dasht-server in a terminal

Visit http://<IP_ADDRESS>:54321/ in a browser

Look at the terminal where you ran dasht-server and provide all the output you see.

Hey with the -ex flag I get the following:
http://<IP_ADDRESS>:54321
+ awk
  /^GET [[:print:]]+ HTTP\/1.+\r$/ { print $2 }
  /^\r$/ { exit } # reached end of HTTP request

+ awk
  /^GET [[:print:]]+ HTTP\/1.+\r$/ { print $2 }
  /^\r$/ { exit } # reached end of HTTP request

Cheers.

Hey @sunaku just wanted to see if there had been any progress on this?

Alright, I had to set up Ubuntu 16.04.1 LTS in a VM just to debug this for you! :grimacing:  Stay tuned.

Okay, I've got it! :triumph: It's a subtle difference between Void's gawk and Ubuntu's mawk.  Here's a workaround:
sudo apt-get install gawk

I'll delve into the differences later, when I have more motivation, or feel free to investigate and report back.

Hey @sunaku, not sure if this is related but none of the links are working, if I inspect the link and manually navigate to something like: file://home/otis/.local/share/dasht/docsets/Bash.docset/Contents/Resources/Documents/bash/Commands-For-Killing.html#//apple_ref/Function/yank%20%28C%2Dy%29 it works, it is just clicking does not seem to work.

That's not related to this issue, but is instead a result of your browser's default security policy. :policeman:  See the manual http://sunaku.github.io/dasht/man/man1/dasht-server.1.html#browser-refuses-to-load-file-links for more information and suggested workarounds.

Hey @sunaku,
Awesome! Sorry only just saw your message about setting up a custom VM much appreciated!!!
Cheers.


Clear the .sprites folder before generating tres files

So I recently altered the output of Texture Packer sprite sheet (removed some unneeded files) however the importer plugin didn't wipe these out of the .sprites folder.
My fix was to manually delete all the .tres files and let GoDot rebuild them. But it'd be nice for it to "sync" properly.

I see your point - but really want to keep the file system interactions as low as possible - especially when it comes to overwriting or deleting files.


Swagger Code Gen, generates "java.io.File" instead of the custom Speech Service API "File" object

Describe the bug
[Java]

Swagger for the Speech Services API  used ""$ref": "#/definitions/File" which result of "File" object got generated referencing package
java.io.File, instead of SpeechServiceApi custom  "File" object.  this  will affect  getTranscriptionFilesAsync()+getTranscriptionFiles**()  almost every method used  PaginatedFiles  as response  will be effected.

it's a swagger api code-gen bug.

To Reproduce
Steps to reproduce the behavior:

Go to https://editor.swagger.io.
Click File, then click Import URL.
Enter the Swagger URL for the Speech Services API: https://westus.dev.cognitive.microsoft.com/docs/services/speech-to-text-api-v3-0/export?DocumentFormat=Swagger&ApiName=Speech to Text API v3.0.
Click Generate Client and select Java.
go to generated files models/PaginatedFiles.java
`import java.util.Objects;
import java.util.Arrays;
import com.google.gson.TypeAdapter;
import com.google.gson.annotations.JsonAdapter;
import com.google.gson.annotations.SerializedName;
import com.google.gson.stream.JsonReader;
import com.google.gson.stream.JsonWriter;
import io.swagger.annotations.ApiModel;
import io.swagger.annotations.ApiModelProperty;
===> import java.io.File;
import java.io.IOException;
import java.util.ArrayList;
import java.util.List;

/**

PaginatedFiles
*/
@javax.annotation.Generated(value = "io.swagger.codegen.languages.JavaClientCodegen", date = "2021-01-01T09:06:00.195Z")
public class PaginatedFiles {
@SerializedName("values")
===>  private List values = null;`
.

Expected behavior
I expect the name to be different than File like TransactionFile , since it's not a generic File.
Version of the Cognitive Services Speech SDK
https://westus.api.cognitive.microsoft.com/speechtotext/v3.0/transcriptions
Batch API.
Platform, Operating System, and Programming Language

OS: [e.g. Windows, Linux, Android, iOS, ...] - MacOS
Hardware - x64, x86, ARM, ... x64
Programming language: C#, C++, Java, JavaScript, Objective-C, Python: Java

Additional context
After I changed Swagger API #/definitions/File  to  #/definitions/ TransactionFile  then I was able to get the transcription files
before that once I receive resposne  of  public void onSuccess(PaginatedFiles result,
result have real java.io.File (so there is no "Kind" property.
"$ref": "#/definitions/File" to   "$ref": "#/definitions/TransactionFile"
and "File": {       "title": "File",       "type": "object",       "properties": {         "kind": {           "description": "The kind of this file.",           "enum": [               "DatasetReport",               "Audio",               "LanguageData",               "PronunciationData",               "AcousticDataArchive",               "AcousticDataTranscriptionV2",               "Transcription",               "TranscriptionReport",               "EvaluationDetails"           ],
to
"TransactionFile": {       "title": "File",       "type": "object",       "properties": {         "kind": {           "description": "The kind of this file.",           "enum": [               "DatasetReport",               "Audio",               "LanguageData",               "PronunciationData",               "AcousticDataArchive",               "AcousticDataTranscriptionV2",               "Transcription",               "TranscriptionReport",               "EvaluationDetails"           ],
`defaultApi.getTranscriptionFilesAsync(transid, 1000, 0, 100, new ApiCallback() {
@Override
public void onFailure(ApiException e, int statusCode, Map<String, List> responseHeaders) {
			 	e.printStackTrace();
				 System.out.println("failure");
			 }

			 @Override
			 public void onSuccess(PaginatedFiles result, int statusCode, Map<String, List<String>> responseHeaders) {
				 System.out.println("success");
				 System.out.println("result"+result.getValues().get(0)==null);
				 result.getValues().stream().forEach(file -> {
					 try {
						 System.out.println("File"+file);
						 file.getKind();
					 } catch (Exception e) {
						 e.printStackTrace();
					 }
				 });

			 }`

*I think this is  bug in Swagger(OpenAPI) codegen  look here:
https://github.com/OpenAPITools/openapi-generator/issues/6017

@bexxx Can you please check, or know who could best comment?

Closing this item since the bug has been already reported to openapi-generator (https://github.com/OpenAPITools/openapi-generator/issues/6017) and a workaround exists (change #/definitions/File to #/definitions/ TransactionFile). Please open a new issue if you need further support on Speech SDK topics.


Azure Tests - Add ARM templates for recording VCR Cassettes

(Taking an incremental and simpler approach to #2243)
(test code only)

Adds two scripts that easily provision or delete all ARM templates in the test templates folder, and also allow you to specify specific templates.  [provision.sh and cleanup.sh]
Adds templates to support existing unit tests, and tweaks tests to use the resources deployed by those templates. [vm.json, storage.json, emptyrg.json]
Re-records all cassettes from the new resources

So now a developer can easily delete/record/modify any previously recorded Unit Tests reliably.  This should unblock people to start writing more unit tests without fear of how we'll maintain them.
This will make it possible to do things like #2230 (convert to json) - since there is a reliable way to recreate cassettes.

Build failure is related to new Azure API version caused by a change in dependency version - Will fix that.

Definitely, that would be a good param to add.  I also think a global parameters file it passes to each deployment that can include that along with other common things (passwords) would be useful.  Most ARM templates you might copy have parameters so it would reduce the need to edit them.


Can't change base URI

Hi!
Thank you very much for this awesome tool! Huginn is really great.
I'd like to host Huginn on a server (through Apache or Nginx), and use _https://hostname/huginn-sub/_ instead of _https://hostname/_.
However I can't find a way to change the base URL of Huginn. Setting DOMAIN to _https://hostname/huginn-sub_ doesn't work, as all generated URL are absolute and begin with /.
Is there a way to achieve that?

I think there are some (or many) places where Huginn is running at '/', especially in Ajax calls.
We'll need to fix them before we can mount Huginn anywhere except at a root.

Thanks @neurolit!  For now, could you use a subdomain?

I'm going to close this issue. Please reopen if you have further questions.

I believe, this is what causes my problems here. Have you had time to make progress regarding changing the base URL?

I don't think supporting this is a priority at the moment. I'd recommend using a subdomain instead if you can't allocate a full domain.


gen_pass: Generate a password from random and uses tr

What OS have you tested this on? Just running:
/dev/urandom tr -dc .\$_A-Z-a-z-0-9 | head -c21; echo

in OSX throws a permissions error.

There are good password generators around. This is system dependent. It should be closed.

Closing... don't think this is needed in OMZ

(appreciate the idea though!)

Thanks for this on-demand local custom plugin :)


Handshake Failures with Post-Quantum Certificates on SCTP & DTLS 1.2

I was testing a client & server application making use of Post Quantum certificates and Kyber768 group, it ran perfectly well on a standard TLS 1.3 connection. However, I am facing problems when using an SCTP socket with DTLS 1.2. Specifically, the handshake fails due to no shared cipher between the client and the server.

With DTLS: SSL routines:tls_post_process_client_hello:no shared cipher:ssl/statem/statem_srvr.c:2307:

With TLS:

Question: Is DTLS 1.2/1.3 support available for Post-Quantum certificates?
Edited: From the documentation, it does seem like PQ certificates can still not be used with DTLS. Are there any plans to add support for DTLS in the future?

I'm currently developing DTLS 1.3 for OpenSSL in order to use PQC for DTLS. Key exchange providers can only be used with (D)TLS1.3 in OpenSSL. Let me know if you want to contribute to the development.

Sounds very interesting, @fwh-dc . Where in GH are you doing that work? Any concrete issues one could take a look at to gauge whether one could contribute?

I am doing the implementation in openssl's github. There are still some remaining features waiting to be implemented. Feel free to reach out if you're interested. I can give some additional info to help get started.
Issue: https://github.com/openssl/openssl/issues/13900
Feature branch: https://github.com/openssl/openssl/tree/feature/dtls-1.3

That's great to hear, @fwh-dc . I'd like to contribute to this feature addition to openssl. It would be helpful if you could share some information about the current progress and the features that still need to be implemented. In the meantime, I'll review this branch and understand the existing code.

Ok, I'm preparing some text and I'll let you know when I have posted it. I think I will do it in the OpenSSL DTLS 1.3 issue.

I've added some notes to https://github.com/openssl/openssl/issues/13900


std::error_code and <system_error>

There's currently no good video material of the <system_error> library for handing back error codes. I would very much appreciate a 10 - 20 minute video explaining how everything works and everything fits together, starting from the idea.
I found this blog from Andrzej very convincing:
https://akrzemi1.wordpress.com/2017/07/12/your-own-error-code/
It would also be very interesting link to the new stdlib proposal from herb sutter: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p0709r1.pdf

Also if you could talk about std expected from C++23, it would be great


client.getVersion is not a function

Hi I have installed hbase module with  sudo npm install hbase --no-optional .
I was running follwing code
var hbase = require('hbase');
var client = new hbase.Client({
host: 'myIP',
port: 8080
});
console.log("Got Client"+ client)
client.getVersion( function( error, version ){
console.log( version );
} );
Rest service is running on host and port . But getting following error
client.getVersion is not a function
at Object. (/home/sohanvir/Desktop/hbase-node.js:10:9)
at Module._compile (module.js:410:26)
at Object.Module._extensions..js (module.js:417:10)
at Module.load (module.js:344:32)
at Function.Module._load (module.js:301:12)
at Function.Module.runMain (module.js:442:10)
at startup (node.js:136:18)
at node.js:966:3

Please take a look at the client test. I've fixed the documentation but I wont be able to update its online version for now.

Thanks for your fast response .. It working .


Update Snappy imports to use new canonical path

The Snappy path has recently changed: https://github.com/golang/snappy/issues/12
This PR updates the imports in reader.go and writer.go respectively.

yeah, it's b0rked alright. a speedy merge would be appreciated.

Ah sorry, I though I already merge this. I must've overlook it. @anandkunal @rojer thanks btw.

actually, looks like you need to drop one "snappy" at the end, it's now: github.com/golang/snappy


Suggestion to further improve connection and statement registration

I spent some time messing with the Debian luadbi package trying to get it work
with LUA 5.2 before I realised that this work had already been performed
recently.  I arrived at a similar solution to the issue but there are a couple
of advantages to the way I did it that could be useful to apply.

Firstly, I have factored out the code that is used to register the LUA for
connection and statement objects into a single function.  This means any
further changes can be made in one place.

Secondly, I have amended the registration code to no longer create global
variables or pollute the package.loaded table.  This also allows the Connect
method to be simplified and not contain conditional code based on the LUA
version.

I have tested this with LUA 5.1 and LUA 5.2 against SQLite3 and DB2 and it is
working nicely for me.  However, please note that I have never used the LUA C
API before this week so there may be subtle problems with the code I haven't
noticed.

I thought it was worth sharing though.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 14 Jun 2015 at 5:19
Attachments:

[luadbi improve LUA object registration.patch](https://storage.googleapis.com/google-code-attachments/luadbi/issue-30/comment-0/luadbi improve LUA object registration.patch)

Still evaluating this patch - it survives the unit tests I just checked in under 5.2. That being said the tests are also new, I'd prefer to be through and try 5.1 and some of my applications.

Patch appears to work nicely, committed.


error in the admin searchfield

Hi !
I like your app, simple and perfect.
I just want you know you have an error in the admin.py search_fields :
user_user should be user__username
i wanted to pull request but i don't know how to do :)
Bye and thanks to share !

@BenZay Thank you, I fixed the problem. Install the new version of the package :)
pip uninstall DjangoBan
pip install DjangoBan


React App (CRA 2.x.x) crashes in production build

The (minified) production build of a React app made with create-react-app will crash when it tries to load the ARK Pay package. This does not happen in a (unminified) dev environment.
It is most likely an incompatibility with CRA's default webpack configuration of the minifier/uglifier (link to a similar issue). The CRA user has no control over these settings though.
Expected Behavior
ARK Pay should be compatible with the build settings used by create-react-app.
Current Behavior
When the App attempts to load a component that imports the ARK Pay package, the app will crash and display the following error in the console:
index.umd.js:909 Uncaught (in promise) TypeError: Super expression must either be null or a function
Steps to Reproduce (for bugs)

Create a project with npx create-react-app my-app
Implement ARK Pay
Create a production build with npm run build
Deploy and view App

Context
I encountered this issue while trying to implement ARK Pay on ScanBlocks.io
Your Environment
Relevant versions:
"@arkecosystem/pay": "^0.1.12"
"react-scripts": "2.1.8"

Thanks for opening this issue! A maintainer will review this in the next few days and explicitly select labels so you know what's going on.
If no reviewer appears after a week, a reminder will be sent out.

I've found a workaround in using react-app-rewired, a tool that lets you manipulate parts of the webpack config of your create-react-app without having to eject the project.
By changing the minimizer plugin to uglifyjs-webpack-plugin, the error in the production build is gone.

config-overrides.js

const UglifyJsPlugin = require('uglifyjs-webpack-plugin');

module.exports = function override(config, env) {
  config.optimization = {
    minimizer: [new UglifyJsPlugin()]
  };

  return config;
};

Of course this is not a real solution to the problem though. A user shouldn't have to do this to make ARK Pay work in their CRA v2.x.x project.

This issue has been closed. If you wish to re-open it please provide additional information.


AST get changed after ast.syntax.parse due to elimination of semicolon

Welcome to the Ammonite Repl 1.0.0
(Scala 2.12.2 Java 1.8.0_131)
If you like Ammonite, please support our development at www.patreon.com/lihaoyi
@ import scala.meta._
import scala.meta._
@ q"System.nanoTime; { val foo = 2; println(foo) }"
res1: Term.Block = Term.Block(
  List(
    Term.Select(Term.Name("System"), Term.Name("nanoTime")),
    Term.Block(List(Defn.Val(List(), List(Pat.Var.Term(Term.Name("foo"))), None, Lit.Int(2)), Term.Apply(Term.Name("println"), List(Term.Name("foo")))))
  )
)
@ res1.syntax.parse[Term]
res2: Parsed[Term] = Success(
  Term.Block(
    List(
      Term.Apply(
        Term.Select(Term.Name("System"), Term.Name("nanoTime")),
        List(Term.Block(List(Defn.Val(List(), List(Pat.Var.Term(Term.Name("foo"))), None, Lit.Int(2)), Term.Apply(Term.Name("println"), List(Term.Name("foo"))))))
      )
    )
  )
)

Thank you for reporting! This appears to be a duplicate of  the top issue in https://github.com/scalameta/scalameta/issues/567#issue-195539795 The pretty-printer should emit a blank line when the following line starts with a curly brace, this is a case where scala's attempt to be whitespace insignificant backfires.

@Atry, thanks for reporting! @olafurpg, thanks for the analysis! I'm closing this issue in favor of #567, since it indeed looks like a duplicate.
Issues like that increase my personal priority of https://github.com/scalameta/scalameta/issues/994. Our current implementation of the prettyprinter is so brittle that fixing this issue (which should be really simple) is really annoying.


add_local_tile not adding any tile atleast no tile is getting displayed

Environment Information

0.7.5:
3.7:
Ubuntu

Description
Add local tile layer not working.No local tile is getting displayed
What I Did
import os
import leafmap
m = leafmap.Map()
file1 = os.path.join('/DISK003/SPATIAL_ANALYTICS', 'landuse.tif')
m.add_local_tile(file1,  layer_name="Local COG")
m
Paste the command(s) you ran and the output.
If there was a crash, please include the traceback here.

Are you using it locally or on cloud environments?

locally on ubuntu

Leafmap relies on localtileserver to load local raster datasets. Try the following example with your own dataset without using leafmap. If it doesn't work, then it is a localtileserver issue. You should report it to localtileserver.
from localtileserver import get_leaflet_tile_layer, TileClient
from ipyleaflet import Map

# First, create a tile server from local raster file
tile_client = TileClient('~/Desktop/TC_NG_SFBay_US_Geo.tif')

# Create ipyleaflet tile layer from that server
t = get_leaflet_tile_layer(tile_client)

# Create ipyleaflet map, add tile layer, and display
m = Map(center=tile_client.center())
m.add_layer(t)
m

thanks for the direction.I ran the command and found that the problem remains and it is proved that the problem is with localtileserver.I will close this bug and open a bug in localtileserver.
Regards,
Kaustav


fix: pass router location prop to nested paths

This PR fixes the location prop on <Router /> not being passed to nested paths.
I came across this issue when trying to implement a modals/overlay system similar to React Router v4 in which location is captured and stored as previousLocation to use on the underlying UI that needs to still display the old location.
Currently this setup won't work with path nesting because the location prop is not passed to the cloned nested children that get wrapped in another <Router />, only the primary prop is passed along.
Example:
<React.Fragment>
  <Router location={previousLocation}>
    <NestedComponent path="/">
      <Dash path="/" />
      <Test path="test" />
    </NestedComponent>
  </Router>

  <Router>
    <TestModal path="test" />
  </Router>
</React.Fragment>

In the example above <Dash /> and <Test />'s location prop should match previousLocation.
I am assuming this was just overlooked and should be considered a bug, as I can't see any reason why location shouldn't be passed along.
Cheers.

@ryanflorence I realize you maintain a busy schedule. Have you had time to look over this? Cheers.

Help me make sure I understand.
If we don't pass the location down, then when you pass a location to the top level router, the sub routers don't get it, which breaks your modal (and probably animations, too).
Confirm/Deny?

Only the nested (child) routers in the router where the location prop is defined (not sibling routers).
So in my example the Modals are rendering fine (animations and all), but the background content (the top  in the example), it's children are not using the provided location.
See this example video: https://youtu.be/DPuDJsPy6Pk.
Notice how when I click the click, the view that says in this case "Dashboard" changes to say "Test".
Let me know if this clarifies, I can put an example together for you to view yourself.

@ryanflorence I don't want to be a bother, but I'm hoping you can look at this PR again.
If needed, here is an example to see the problem yourself. https://codesandbox.io/s/m9o93kpjxy.
Do you need any help maintaining this project? I'd like to volunteer my help and time if needed. I currently am using a fork of this project that includes my PR along with some other fixes like #83 so our project is actually usable. There are lots of PRs here I feel are appropriate to merge and don't step out of the original goal of the project. Ultimately, I'm trying to gauge whether or not this project is going to be maintained to some degree of predictability, or if it would be wise to go another direction in our project.
Cheers.

Adding +1 to this. When trying to implement a modal over last location, the new path will display in both instances of the router.
      <>
        // Router[location=<currentLocation>] -> Component[path=...] -> Router (inherits <currentLocation>)
        {this.renderRouter(location)}

        // Router[location=<previousLocation>] -> Component[path=...] -> Router (inherits <currentLocation>)
        {isModal && previousLocation && this.renderRouter(previousLocation)}
      </>

Using fix from @erictaylor makes each dynamic <Router /> aware of the location provided and renders both routes correctly. The URL displays the new route and layers it in a modal above the old route.
Not sure if this raises any accessibility concerns but without this feature I don't see any other option except to switch to react-router for this.

Thanks for your patience on this 🙃


Add customization option for color preview of FormBuilderColorPickerField

Close: #19
Problem
Color preview of FormBuilderColorPickerField was not correctly laid out (missing padding) in form fields with OutlineInputBorder. Also, currently there is no option to provide a custom color preview.
Solution description
This PR swaps the current color preview (a colored Container) with a colored circular icon, which is correctly formatted (as suffixIcon expects an icon).
Screenshots or Videos
Without changes:

With changes (top: default, bottom: custom preview provided with code below):

FormBuilderColorPickerField(
...,
colorPreviewBuilder: (color) => Padding(
                    padding: EdgeInsets.all(8),
                    child: Container(
                      color: color,
                      height: 24,
                      width: 24,
                    ),
                  ),
)

Thanks a lot for this feature. I think that is related with #19

Hey, I just checked, the field "colorPreviewBuilder" does not exist in the FormBuilderColorPickerField widget, is there any other way to change the shape of the color picker?

Temporary fix until they deploy into pub.dev,
Add the package to pubsec using the following:
   form_builder_extra_fields:     git:       url: https://github.com/flutter-form-builder-ecosystem/form_builder_extra_fields       ref: main


No option to hide nsfw content after you click show

This is a followup for #5772, or at least for the gallery item, on explore is still is not blurred :D

lets change the show button, no hover effect, just simple button with background
when you click show, button changes to hide content

you can test here: https://canary.kodadot.xyz/rmrk/gallery/18883932-9A78FF2AECF9BED171-DOTINSIDER-POLKADOTINSIDER-0000000000000001
updated in figma handoff: https://www.figma.com/file/JXNtryaNYhY0XJNArzvPQx/Handoff?type=design&node-id=1287%3A18959&mode=design&t=2KWtprPqfstWkfBj-1

👋


Users are getting logged out from the wallet after a recent update

I have seen three reports since update 3.28.0 of users reporting that they have gotten logged out from the wallet after an update.
The expected behavior of the wallet is that the user gets their wallet locked after an update.
Has any change been made that could have resulted in this?
Can this be rolled back? Users do not appreciate it.
When testing this myself I find the wallet only ever locks me out. I have not been able to test more then a single update forward. from 3.27.0 -> 3.28.0 and from 3.28.0 -> 3.29.0
Perhaps the issue occurs when the upgrade is done from a much older wallet to todays version.

I have confirmation that one user was on Chrome and another one was on Firefox. Third user unknown.

Hmm, not sure how to debug this one. There is only one place in the code where we clear chrome.storage, when the user signs out
https://github.com/hirosystems/stacks-wallet-web/blob/6a9298d7e62b233b3dd2adb561cebd12149c9e8d/src/app/common/hooks/use-key-actions.ts#L48-L54
Perhaps we can simulate an upgrade through multiple versions to test this

I will check with users if I can get more details.

I will check with users if I can get more details.

let me know sir , how can i help !

(chrome) User 1
Timeline:
dec. 5th build 3.27.0 ready according to github
Chrome user 1 reported using the wallet up to the time of the issue, I am assuming it was already on 3.27.0 (or the automatic update would have failed for the previous 5-6 days). Not sure if it is relevant but the user was using multiple chrome profiles with different wallet accounts, all logged out at this point.
dec. 11 4PM GMT, automatic logout issue
dec. 13th build 3.28.0 ready according to github
So now I am not so sure it is actually caused by a wallet update. There was no wallet update on dec. 11th.

Hmm, not sure how to debug this one. There is only one place in the code where we clear chrome.storage, when the user signs out
https://github.com/hirosystems/stacks-wallet-web/blob/6a9298d7e62b233b3dd2adb561cebd12149c9e8d/src/app/common/hooks/use-key-actions.ts#L48-L54
Perhaps we can simulate an upgrade through multiple versions to test this

I am not sure if 'chrome.storage' is being cleared with this bug. I haven't been able to verify because the users likely already altered chrome.storage by re-enter the seed (or another seed) after the logout and before contacting us.
3.27.0 has this fix
close other frames when wallet locks (8788e01)
Any chance that introduced a bug that could cause this?

Any chance that introduced a bug that could cause this?

I wouldn't have thought so, as it only closes the window. I wonder if it's a routing issue, and somehow they're just viewing the welcome screen (appearing as though it's signed out), but it isn't really 🤔

@314159265359879 is your impression that we've resolved this by now?

user 1, couldn't have been the update, maybe something with the use of multiple profiles (on Chrome) but I have not been able to reproduce this as of yet.
user 2, turned out to have unknowingly/mistakenly click log out instead of lock.
user 3, unknown
user 4, similar to user 2
So perhaps user 2 and user 4 form a pattern. I have this issue https://github.com/hirosystems/stacks-wallet-web/issues/3037 for a small addition to the log out warning.

Thanks for the update anyhave .
Am already left stacks , almost months.
Don't care much.
On Thu, 9 Feb, 2023, 1:33 pm Werner, @.***> wrote:

user 1, couldn't have been the update, maybe something with the use of
multiple profiles (on Chrome) but I have not been able to reproduce this as
of yet.
user 2, turned out to have unknowingly/mistakenly click log out instead
of lock.
user 3, unknown
user 4, similar to user 2
So perhaps user 2 and user 4 form a pattern. I have this issue #3037
https://github.com/hirosystems/stacks-wallet-web/issues/3037 for a
small addition to the log out warning.
—
Reply to this email directly, view it on GitHub
https://github.com/hirosystems/stacks-wallet-web/issues/2953#issuecomment-1423782021,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYFQLGR6KMZNRT5SYFVGLCLWWSQDNANCNFSM6AAAAAATF6ZOSY
.
You are receiving this because you commented.Message ID:
@.***>


@conda-forge-admin, please add user @drbixx

Additional comment:
No response

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added user @drbixx in conda-forge/astromatic-stiff-feedstock#5.


Reduce max reconnect interval

As I said earlier, two out of three of my devices lose network connection when they go to sleep. If, after a long idle time, the device is turned on, the integration updates the state for as much as 5 minutes. This is a very very long period to use integration in automations. For example, the old Android TV integration restored the connection within 15-30 seconds.

I would even reduce this time to 15 seconds.

Could discovery help? I.e. as soon as Home Assistant sees the device and the device is unavailable, force a reconnect?
Curious, what reconnection delay does the cast integration have?

Could discovery help? I.e. as soon as Home Assistant sees the device and the device is unavailable, force a reconnect?

Don't even know. I think that if the device has already been added or discovered once, then the discovery mechanism will not work twice.

Curious, what reconnection delay does the cast integration have?

Almost instant.

Each attempt to connect has a timeout of 60 seconds. Don't you need to decrease that too? Another user just complained privately to me on discord that for their Xiaomi device that becomes unavailable when turned off, if they restart home assistant the HA start up is delayed because of the 60 seconds delay. I guess you must be experiencing that too?

restart home assistant the HA start up is delayed because of the 60 seconds delay. I guess you must be experiencing that too?

I don't have this behavior on my instance.

I think ssl_context.load_cert_chain is blocking. It's unrelated to your change but your change will make it worse. We first need to make that async before reducing the reconnect interval. Or better reuse the SSLContext across the reconnect attempts.

I committed 2ddfd17 to reuse the SSLContext across the reconnect attempts so I'll go ahead and merge this.

@tronikos Can you make a new release with this change? I'd include this in the new HA release.

Made v0.0.9. Can you bump the version in HA?

Sure


Filter "The suspension reason is to short, please give a reason for suspension."

When the suspension reason is too short (at least 5 characters? need to test), the error The suspension reason is to short, please give a reason for suspension. is returned.

The minimum length is 5 characters.


[DCOS-2409] Improved error message for dcos task log <completed_task>

one minor comment, and then LGTM once tests pass.

Master is failing, and I think #297 fixes it, so this is blocked on #297

@mgummelt #297 is now merged


JAVA-3057 Allow decoding a UDT that has more fields than expected

I've had hard time trying to replicate this issue. Attempts to ignore schema updates on control connection did not replicate the problem. In fact, DefaultCodecRegistry will always attempt to create new codec if it does not find corresponding one in the cache (source). Cache key takes into account UDT name, but also names and types of fields.
This triggered my attention to the way application attempts to read UDT from row. Leveraging row.getUdtValue(...) will again register new codec (source). However, trying to read the data with given UdtCodec will indeed expose the issue. Since there is a public API method to read the column using certain codec, I think that this issue is valid.
Below is the integration test that exposes the problem. Shall we add it to the PR?
/**
 * @jira_ticket JAVA-3057
 */
@Test
public void should_decoding_udt_be_backward_compatible() {
    CqlSession session = sessionRule.session();
    session.execute("CREATE TYPE test_type_1 (a text, b int)");
    session.execute("CREATE TABLE test_table_1 (e int primary key, f frozen<test_type_1>)");
    // insert a row using version 1 of the UDT schema
    session.execute("INSERT INTO test_table_1(e, f) VALUES(1, {a: 'a', b: 1})");
    UserDefinedType udt = session
            .getMetadata()
            .getKeyspace(sessionRule.keyspace())
            .flatMap(ks -> ks.getUserDefinedType("test_type_1"))
            .orElseThrow(IllegalStateException::new);
    TypeCodec<?> oldCodec = session.getContext().getCodecRegistry().codecFor(udt);
    // update UDT schema
    session.execute("ALTER TYPE test_type_1 add i text");
    // insert a row using version 2 of the UDT schema
    session.execute("INSERT INTO test_table_1(e, f) VALUES(2, {a: 'b', b: 2, i: 'b'})");
    Row row = session.execute("SELECT f FROM test_table_1 WHERE e = ?", 2).one();
    // Try to read new row with old codec. Using row.getUdtValue() would not cause any issues,
    // because new codec will be automatically registered (using all 3 attributes).
    // If application leverages generic row.get(String, Codec) method, data reading with old codec should
    // be backward-compatible.
    UdtValue value = (UdtValue) row.get("f", oldCodec);
    assertThat(value.getString("a")).isEqualTo("b");
    assertThat(value.getInt("b")).isEqualTo(2);
    assertThatThrownBy(() -> value.getString("i")).hasMessage("i is not a field in this UDT");
}

Awesome, thank you for doing that work for me Lukasz! I added it in a new integration test since I couldn't find another existing one that fit. Also rebased.
The case we ran into this issue had to do with the object mapper since it holds on to schema somewhere, and uses that to generate the cql queries for example. But this test is great too!

I'm a bit reluctant to remove the safeguard of decoding a UDT whose set of fields is different from what we expect.  If we have a mismatch there it seems like we can't say anything with certainty about what's actually in the UDT in that case.
It seems like the best case we can do from a client perspective in this case is something like the following:

Try to read the UDT
If the read fails because of the indicated exception try a schema refresh (since def on server might have changed since schema was originally loaded)
Try to read again with new UDT def.  If this fails again you've just got bad data and there's nothing you can do about it.

Am I missing something here?

That will work in some cases, but a few things that make me feel like the current approach is better:

I'm hesitant to do a schema refresh in the request path of the driver, it will cause that request to look latent from the caller's perspective. The closes thing I can think of is preparing a statement on an UNPREPARED response but that particular case seems warranted.
A refresh in that code path isn't enough, the codec is likely be cached in the CachingCodecRegistry and there's (currently) no way to invalidate that. For example when using the object mapper it validates the schema against your POJOs by default and ends up caching the codec at init time. You can't even re-register your UdtCodec on an error since it hits the collides check and doesn't get re-registered - changing that will be a fair bit more invasive.

whose set of fields is different from what we expect.

The only changes you can make to a UDT are to add fields, and this code path deals specifically with having more fields than we expect. Additionally, given Cassandra is byte buffers all over the place, there's nothing stopping a user from trying to read bytes with the wrong codec except for schema verification, and that's what protects us from the general "wrong UDT definition" case. I think that means we can assume users only make "sane" changes to a UDT while a client app is running (i.e. UDT field additions) and so the "right" thing to do is ignore fields that were added that we don't recognize, to make it easier to roll out a UDT change across the writer apps and reader apps.

Let me know if you want to chat about this over a call, it took me a couple hours to page in enough context about this to be able to respond to you, would be nice to resolve this before it gets paged out again :)

@absurdfarce , was wondering if you could give this a second look?  I recall that we discussed that we had some thoughts about whether we could provoke a schema refresh in this case, but I think we should strongly consider just merging this as is, because it seems relatively safe and unbreaks applications that hit this case (e.g. as mentioned in #1942)

Preemptively rebased and updated the commit message to include Bret as a reviewer 🙏 so it should be good to merge once I get the 👍


fix: forward push received app in foreground events to 3rd party callbacks

Part of: https://linear.app/customerio/issue/MBL-138/[bug]-ios-customers-receive-callbacks-from-3rd-party-sdks-for-pushes
When a push is received while app in foreground, send the push event to other push event handlers in host app. Giving customers the opportunity to process the push event. Previously, only non-CIO pushes would be sent to other push event handlers.
Notes:

CIO SDK waits for all push handlers to call completion handler for push processing. Not calling completion handler may result in push not being shown while app is in foreground.

Push event handlers must call async completion handler for CIO SDK to handle push events. Test function test_givenMultiplePushHandlers_givenCioPushDelivered_givenOtherPushHandlerDoesNotCallCompletionHandler_expectCompletionHandlerDoesNotGetCalled reproduces scenario.
Waiting for completion handler prevents premature termination of push processing logic by iOS. Apple documentation states completion handler must be called after processing push event. https://developer.apple.com/documentation/usernotifications/unusernotificationcenterdelegate/usernotificationcenter(_:willpresent:withcompletionhandler:)

The SDK now determines if a push should be shown for non-CIO pushes and fixes bug in PushEventHandlerProxy.

This change had to be made as part of waiting for all push handlers to complete async operation.
Behavior before: The push handler that called the async completion handler first would be the one that decides if the push is displayed on the device.
After behavior: The SDK uses Apple's default of not displaying push. The SDK will display the push if at least 1 of the push handlers decides to display push.
This aligns with Apple's default behavior of not displaying a push unless at least one push handler decides to display it.https://developer.apple.com/documentation/usernotifications/unusernotificationcenterdelegate/usernotificationcenter(_:willpresent:withcompletionhandler:)

Stack:

#634
#633
#601
#590
#584 ⬅
#583

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

✓ Commit merged in pull request #634


Corrected login and signup page #59 issue

I have corrected the issues mentioned in #59 issue which consists of:-

Radio button at Signup page for Student/Counsellor role
Password length validation
Login page corrected

Also, I noticed there is no API on a Login page to send the form data, I would love to work on that too. I would create another Issue and work on it. Do let me know!

Hello @Sar-thak-3 for solving this issue but we have already created server API calls we are facing problem in cors update


[Bug]: JSDOM environment does not detect open handles

Version
29.7.0
Steps to reproduce
Jest node environment detects open handles and bad things that happen after tests are done.
The tests below will fail:
test("error after tests are done", () => {
  setTimeout(() => {
    throw new Error("after tests are done");
  }, 100);
});

test("open handles", () => {
  setInterval(() => {}, 100);
});

test("console usage after tests are done", () => {
  setTimeout(() => {
    console.info("after tests are done");
  }, 100);
});

Unfortunately, when using JSDOM environment, these tests do not fail.
Expected behavior
All Jest environments should detect open handles and bad things that happen after tests are done.
Actual behavior
Jest JSDOM environment does not detect open handles and bad things that happen after tests are done.


GTM2: Please add to

Please add immediately following the opening <body> tag across all templates:

Updated:
`

`


test: fix conversion test for invalid values

Sometimes just "Conversion for PLN 1" is returned. Probably a race condition which makes this test flaky.
See https://travis-ci.org/xxczaki/cash-cli/builds/457357097 where it fails 2 times because of the race condition problem.

I think we have a very flaky test here. Let's see if this happens again.

In this case we should check the test script.

Pull Request Test Coverage Report for Build 277

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

Totals

Change from base Build 273:
0.0%

Covered Lines:
56

Relevant Lines:
56

💛  - Coveralls

Probably an issue with the test library or output of the library (streamed response).


Remove invariant from accepted languages.

@stiliev knew exactly what the issue was. There's two different options to fix this. I opted for what I felt like was the least intrusive (remove InvariantCulture from the list of accepted languages). I felt like that's a more conservative approach than setting the default culture to en-US, which may introduce unintended consequences.

https://github.com/Microsoft/vsts-agent/issues/253


sonarqube integration

This is an attempt to enable the use of SonarQube.com for quality analysis #116.
To set the values for the needed environment variables in Travis follow this documentation:

SONAR_ORGANIZATION: name of the organisation in Sonarqube
SONAR_TOKEN: the token generated in Sonarqube
GITHUB_TOKEN: (to be able to run sonar on pull requests) github personal access token doc

Coverage remained the same at 85.612% when pulling 946f0135d72693745b3c110d84dcf9a7f65a1f4e on dzlab:sonarqube into 3463dd9bbafab56bddeebb46adc1ec8cd57369ed on liquigraph:master.

Thanks for your contribution.
I will take a look into this PR at the weekend if no one else does this before.
I integrated sonar some time ago for another project by using the maven way. Maybe https://github.com/innoq/spring-boot-actuator-extensions/blob/master/.travis.yml and can help as a source of inspiration as well https://github.com/innoq/spring-boot-actuator-extensions/blob/master/bin/travis.sh

Yep maven sonar plugin is a second option to integrate with SonarQube.com.
Travis CI also documented how to set it up and use it.

Hey, shall we merge and see? @mvitz :)

What could possibly go wrong? ;-)
Keep in mind that we (in this case you) need to create a sonarqube account and add the required configuration keys to it and to travis.

@fpavageau would you have any time to look at this? 👼

Finally merged, merry xmas 🎅 🍾 🕺 https://github.com/liquigraph/liquigraph/commit/86eb4d087c2d996982cf3dab726a514376ffe20a


Create kube-dns in kube-system namespace by default

Kubernetes documentation points to creating kube-dns in the kube-system namespace. Should we try to match that pattern?

Why not? Makes sense. Will try this out tomorrow and merge if it's working alright. Thank you!

Thanks a lot!

Thank you!


feat: port RepresentationTheory.GroupCohomology.Basic

This file seems hard to fix and it's very slow :( I also won't have much of a chance to look at it for the next 2 days, so if anyone wants to help I'd be very grateful.

I am back to working on this so if anybody else wants to look at it then please let me know - I don't want to waste someone's time. If I have to give up I'll post on Zulip about it.

bors r+


update annotation

Ⅰ. Describe what this PR does
update annotation
Ⅱ. Does this pull request fix one issue?

Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #459 (c13e23b) into master (90fc759) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #459   +/-   ##
=======================================
  Coverage   19.92%   19.92%
=======================================
  Files          56       56
  Lines        2098     2098
=======================================
  Hits          418      418
  Misses       1635     1635
  Partials       45       45

Impacted Files
Coverage Δ

pkg/utils/charts.go
0.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 90fc759...c13e23b. Read the comment docs.


Improve the coverage of bit_length testing

Which issue does this PR close?

The follow-up PR of #13221
Rationale for this change

What changes are included in this PR?

Add tests for String, LargeString, and DictionaryString
Add the issue tracking link.

Are these changes tested?
yes

Are there any user-facing changes?
no

The CI fail doesn't relate to this PR. It could be fix by https://github.com/apache/datafusion/pull/13340

Thanks @alamb and @austin362667  for reviewing


Changes needed in some buttons

I guess due to the increase in font size the text got wrapped. We need to fix this issue found in some places like in settings page

Have tested this specific use case in Litmus-ui v1.1.2 its working appropriately. This issue is not specific to Litmus-ui and must be addressed in Litmus.


LUCI tasks are pending and not being scheduled

It looks like the builds have been stuck for ~30 minutes

For example https://ci.chromium.org/p/flutter/builders/prod/Mac_android microbenchmarks/1396

We have mac ios bots in idle status, not running tests. And there are no pending task in the pool. Checking to see if any failure in backend when scheduling those prod tests.
Linux and Mac android bots are running tasks. (Linux ones are running a dev branch row)

(Manually merged https://github.com/flutter/flutter/pull/83940 to unblock the tree.)

Actually the ios ones are expected: all ios tasks have been finishing running.
So the long queue time is expected: they are running the dev row with high priority.

I will monitor for a while before closing.

Closing as all tests have been schedule as expected.

Tree went green, thanks!


UDP TCP TLS and HA

This personal blog post has the reasons choices made during implementation often have the reverse effect desired update format into docs to help in decision tree form to help customers make the best choice
https://www.rfaircloth.com/2020/05/21/performant-and-reliable-syslog-udp-is-best/

Added to docs per https://github.com/splunk/splunk-connect-for-syslog/pull/573


Make Helpers class a property of Client

This would open up possibilities for multiclient applications to have independent logging for each client. In my honest opinion this also makes more sense architecture wise, as all properties in Helpers class are bound to client and there is no need for putting them into separate class

I disagree with your analysis. All properties/members of Helper class are absolutely not bound to Client, and perfectly fine as static.
The only problem I recognize is about logging.
Now there are two reasons I will not move Log to Client:

I need to be able to log from various methods that are not Client-bound, like Session, Encryption and TL serialization
I don't feel the need to particularly help those developers that want to use multiple Clients in their program, as mass-managing fake user profiles goes against Telegram TOS


add install via chocolatey

@chantisnake do we need to update the latest version on chocolatey whenever we release a new one?

no, I will take care of it.

Hm, so we do have 😅 Thank you ❤

It's the line I removed the right line?

It is @chantisnake. Thank you! 🙌


feat: rpm upgrade test with other changes

add upgrade workflow in Jenkins pipeline
upgrade test validation for rpm Package

Thanks @cdurai-netapp looks good. I don't think the upgrade test does this yet, but one area we've seen upgrade fail is when pollers are already running, and then an upgrade is started. Can you add a test for that? I don't recall if the upgrade stops existing, leaves them running, etc.


Parallel parquet reading by row group - third try

Parquet reader parallelized by row group.
In this version the number of row groups is divided by the number of available worker partitions, so that each remote call processes an equal share of the row groups.
Given that Parquet compressed data will have many more rows than columns any time it is of large total size, datasets are not split into columns splits, but read in a single column group.  Thus, each row group will only be scanned once.
The code path updated in this PR only applies to Parquet files that are NOT in a partitioned directory.
Parallelization of partitioned parquet files would be best done based on parallelizing the reading of partitioned bins, not row groups.
Flag parameter have been added to _read_parquet_columns() to control the return of lengths, dtypes metadata in order to avoid the superfulous creation of remote objects that would contain redundant data, because these data can be obtained from just the first remote job.

@jpdna Can we keep it to 1 PR per patch? It is hard to go between PRs for comments and commit history. Instead of opening a new PR each time it is updated, let's keep this one.

Sure, sorry for confusion.  it was actually concern about losing the ealier
discussion because i needed to force push my new version as i manually had
started from master again that motivated this inelegant proliferation.  But
if it is better to force push over an existing PR branch then i will do
that, or at least ill ask before considering opening a new pr on same issue
again.
On Tue, Jul 16, 2019, 3:33 PM Devin Petersohn<EMAIL_ADDRESS>wrote:

@jpdna https://github.com/jpdna Can we keep it to 1 PR per patch? It is
hard to go between PRs for comments and commit history. Instead of opening
a new PR each time it is updated, let's keep this one.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/modin-project/modin/pull/737?email_source=notifications&email_token=ABYUKQHZ6OXQ3JOSNUTZSJLP7YPATA5CNFSM4IEGMNP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2B466Q#issuecomment-511954810,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABYUKQCIAY64QKURV6FNNMLP7YPATANCNFSM4IEGMNPQ
.

Closing as stale. Please feel free to reopen and continue development!


add instances for monad-tracer

To add instances for monad-tracer because of utility.

I'm not sure if most of the instances here really work.
The variants of inSpan, inSpan', inSpan'' in this module still require MonadUnliftIO, and most of the provided instances in this PR can't support MonadUnliftIO.
For the ones that do support it, like ReaderT, there is a tradeoff with these instances you are proposing where using ReaderT Tracer IO a wouldn't be use the Tracer because it is lifted to the base of the stack.
I think I would rather deprecate this module since it doesn't really fit with the rest of the library's design.

The variants of inSpan, inSpan', inSpan'' in this module still require MonadUnliftIO, and most of the provided instances in this PR can't support MonadUnliftIO.

Oh I see! You are right.

For the ones that do support it, like ReaderT, there is a tradeoff with these instances you are proposing where using ReaderT Tracer IO a wouldn't be use the Tracer because it is lifted to the base of the stack.

Yes, but users needs to define an orphan instance when this library does not serve instance MonadTracer m => MonadTracer (ReaderT r m). And users can define instance MonadTracer (ReaderT Tracer m) on necessary (maybe an OVERLOADS pragma required).
And so I think that this library should expose the instance.

@iand675 No chance to pull this?

Sorry for the delay! Since the reader instance is overlappable I guess we can merge this.

Thanks for review.


Slice done without anything when i have a quick star

Hi, I followed your instructions in the Quick Start, but encountered the following errors. Could you please tell me how to resolve them?

I found that the file exists, but it doesn't contain any sub .wav files. Everything is fine now.


Upgrade Kratos to v0.9.9+

Is your feature request related to a problem? Please describe.
I don't want to have to manually set the admin account password when installing Pixie Cloud. This manual step complicates installing Pixie using a GitOps processes (see Slack thread).
Describe the solution you'd like
Pixie uses Kratos v0.5.4-alpha.1. Upgrade to v0.9.9+. Once Kratos is upgraded, we can use the new Kratos feature which allows us to import user credentials.
Context
There are a LOT of breaking UI changes that need to be addressed. I attempted to upgrade this, but it was not simple.

We are now using Kratos 0.10.1


self::$grav is undefined

$this->config = self::$grav['config'];

@loganfreeman I also have this issue. It seems to appear only in production environments for me. the plugin works fine in localhost development though in production it fails
@kalebheitzman I would take a look at how other plugins call grav and it's config

@Vivalldi are there any plugins you would recommend specifically that I look at? Thanks.

So the grav object is a protected attribute of the plugin class. So in the login plugin it calls $this->grav['config'] which calls the config container

I have just installed datetools as it was required by the event plugin. Then on loading my site after the install it appears i also have a similar issue
Access to undeclared static property: Grav\Plugin\DateTools::$grav
It seems to throw the error at the following point in the datetools.php
$this->config = self::$grav['config'];
I can set enabled: false in the .yaml file and my site works again .
Perhaps i should have opened another thread for this issue. if so let me know and i will create a new one.
regards jimmy

This is fixed with v1.0.3. Pushing the release today.


This role doesn't exist

rbx.setRank(2601636,483090613,9)
Says role doesn't exist
http://prntscr.com/nfsnrz

Try doing rbx.setRank({ group: <groupId>, target: <userId>, rank: 9 }) instead.

Try doing rbx.setRank({ group: <groupId>, target: <userId>, rank: 9 }) instead.

Thank you, suufi! This is works.