Agents failing and restarting

Agents installed as service at swarm.

Hi @Yumash,
can you give us more information about your environment (provider, docker version, OS...)

Sure
Docker version 18.09.1, build 4c52b90
Ubuntu 16.04
Local network (<IP_ADDRESS>/24)
One of manager nodes has outer IP on separate interfaces (eth0). Local network for all nodes including manager is on interface eth1.

Thanks, how many nodes do you have in your cluster?

16 - 14 nodes, 2 managers

How did you deploy Portainer?

docker service create  --name portainer --publish 9000:9000  --replicas=1  --constraint 'node.hostname == mynode220'  --mount type=bind,src=/data/portainer,dst=/data     portainer/portainer

And you deploy the agent manually?

Yes, according to instructions from here

I have the same issue !
when a agent on host-10-191-51-47 failed like this

the failed log:
2019/04/17 07:17:55 [DEBUG] - Agent details: map[NodeName:host-10-191-51-47 Mode:swarm NodeRole:worker AgentPort:9001], 2019/04/17 07:17:55 [DEBUG] - Using cluster address: tasks.agent, 2019/04/17 07:17:55 [DEBUG] - Using advertiseAddr: <IP_ADDRESS>, 2019/04/17 07:17:55 [DEBUG] - Generating TLS files..., 2019/04/17 07:17:55 [DEBUG] - Using agent port: 9001, 2019/04/17 07:17:58 [DEBUG] - Serf configured with AdvertiseAddr: <IP_ADDRESS>, 2019/04/17 07:17:58 [INFO] serf: EventMemberJoin: df27812e9582 <IP_ADDRESS>, 2019/04/17 07:17:58 [DEBUG] - Will join cluster via: tasks.agent, 2019/04/17 07:17:58 [INFO] serf: EventMemberJoin: 3a4136e241f9 <IP_ADDRESS>, 2019/04/17 07:17:58 [INFO] serf: EventMemberJoin: d31ba3add5e0 <IP_ADDRESS>, 2019/04/17 07:17:58 [INFO] serf: EventMemberJoin: e96972e8dcf6 <IP_ADDRESS>, 2019/04/17 07:17:58 [INFO] - Starting Portainer agent version 1.2.1 on <IP_ADDRESS>:9001 (cluster mode: true), 2019/04/17 07:23:51 httputil: ReverseProxy read error during body copy: local error: tls: bad record MAC, 2019/04/17 15:22:33 http error: Unable to execute cluster operation (err=local error: tls: bad record MAC) (code=500), panic: interface conversion: interface {} is map[string]interface {}, not []interface {}, , routine 20688 [running]:, github.com/portainer/agent/http/proxy.responseToJSONArray(0xc003c4f4d0, 0xc005128980, 0x10, 0x0, 0x0, 0x0, 0xc00496be58, 0x452780), 	/home/tony/workspaces/go/src/github.com/portainer/agent/http/proxy/response.go:47 +0x304, github.com/portainer/agent/http/proxy.(*ClusterProxy).copyAndExecuteRequest(0xc00020c118, 0xc0003d5c00, 0xc00441ce80, 0xc00664f020, 0xc005128a00), 	/home/tony/workspaces/go/src/github.com/portainer/agent/http/proxy/cluster.go:101 +0x123, created by github.com/portainer/agent/http/proxy.(*ClusterProxy).executeRequestOnCluster, 	/home/tony/workspaces/go/src/github.com/portainer/agent/http/proxy/cluster.go:79 +0x87,
and the other agent logs are same:
 2019/04/18 02:19:53 [INFO] serf: attempting reconnect to df27812e9582 <IP_ADDRESS>:7946, 2019/04/18 02:17:50 [INFO] serf: attempting reconnect to df27812e9582 <IP_ADDRESS>:7946, 2019/04/18 02:17:17 [INFO] serf: attempting reconnect to df27812e9582 <IP_ADDRESS>:7946, 2019/04/18 02:16:14 [INFO] serf: attempting reconnect to df27812e9582 <IP_ADDRESS>:7946, 2019/04/18 02:15:11 [INFO] serf: attempting reconnect to df27812e9582 <IP_ADDRESS>:7946, 2019/04/18 02:13:38 [INFO] serf: attempting reconnect to df27812e9582 <IP_ADDRESS>:7946, 2019/04/18 02:12:35 [INFO] serf: attempting reconnect to df27812e9582 <IP_ADDRESS>:7946, 2019/04/18 02:11:02 [INFO] serf: attempting reconnect to df27812e9582 <IP_ADDRESS>:7946
the IP <IP_ADDRESS> is the IP of the failed agent

Was getting this error too. For me it was enough just to stop the stack, delete the portainer_data volume and redeploy the stack.

I can confirm this. Stopping stack and deleting portainer data folder did the job. Maybe related to: https://github.com/portainer/portainer/issues/2730

This could be related to another agent instability issue that we have open here: #2535

Closing as duplicate of #2399


Error adding layer importing a file

STR

Open a map.
Add new layer by dropping a dataset file within the add layer modal.
Layer gets imported, but a JS error appears at the console on the rerendering:

tracker.js:26
Uncaught Error: TrackJS Caught: Cannot read property 'remove' of undefined
wrapError @ tracker.js:26
d.util.hasFunction.f.(anonymous function) @ tracker.js:4

cc @xavijam

Yes, that happens to me, it is related with the Notifier, I'll take a look later.
cc @nobuti


Update fabric-sdk-java to 2.2.15

Updates org.hyperledger.fabric-sdk-java:fabric-sdk-java from 2.2.5 to 2.2.15.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.hyperledger.fabric-sdk-java", artifactId = "fabric-sdk-java" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.hyperledger.fabric-sdk-java", artifactId = "fabric-sdk-java" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #244.


Add initializer from NSURL

This adds support for playing MPMediaItem from its asset URL.

Thanks! I will update the pod in the day.


added folder structure

Created folder structure for group project (assets folder, html, css and javascript files

approve file structure


Updated documents on features coming in version and developer role

Coverage remained the same at 91.452% when pulling 19b62ba1b4f9c778a39444b47a27c614169f594b on zhicaizack:devuserdoc into 3e20235f7a491bc2f32ac11aa5167635d0c766fa on CS2113-AY1819S1-T16-1:master.


Updated episode list url

Fixes vn-ki/anime-downloader#198

I don't think it's that easy. The new API seems to have different behavior. Did you test this change?


Modify footer copyright behavior

Make it to where it displays Copyright (c) 2014-(current year), Cardshifter.

I will do it in my branch so you don't need to do it in master or develop.

Awesome thanks!


resolve.extensions ignored

Do you want to request a feature or report a bug?
BUG

What is the current behavior?
Ignores resolve.extensions option
If the current behavior is a bug, please provide the steps to reproduce.
// webpack.config.js

module.exports = {
  resolve: {
    extensions: ['.js']
  }
}

Create a dir Test
Put into Test dir these files: Test.scss and `Test.js``
import Test from 'Test/Test'; // bundle.js

Output
WARNING in ./Routes/Home/Home.scss
    Module parse failed: Test/Test.scss Unexpected token (1:5)
    You may need an appropriate loader to handle this file type.
    | html {
    |   background: red;
    | }

What is the expected behavior?
Ignore files with non white-listed extensions
If this is a feature request, what is motivation or use case for changing the behavior?
It is a bug
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.

Node: 6
WebPack: 2.2.0-rc.4

Could you tell me whats in your Home/Home.scss file, and with which loader it's loaded?

I don't want to load that file,
I manage css outside from webpack.
import Test from 'Test/Test' should import Test.js and ignore the rest, but, it tries to load both js and scss and it breaks because there is no scss loader.

WARNING in ./Routes/Home/Home.scss
The warnings origins from Home/Home.scss. There is propably a @import there.

hi @sokra, there is no import for Home.scss... there is just the import Home from 'Home/Home' which is without extension and is indendeed for es module but webpack tries to load both js and scss.

@hitmands, I tried to reproduce your example, but it correctly imported Test/Test.js for me. If you still have this issue, please create a repository that reproduces your issue.


ssm-session-manager-plugin: add "aarch64-darwin" support

Motivation for this change
Allow support for aarch64-darwin platforms.
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

That installs x86_64 binaries on aarch64-darwin systems, the binary still can be run with rosetta emulation. I assume that's better than nothing for macos users but doesn't look valid from nix point of view.
@SuperSandro2000 So can we depend on that or that will be reverted?
@martinbaillie feature request for reference https://github.com/aws/session-manager-plugin/issues/9

I don't know, so far no one complained.

I run rosetta-free deliberately, so consider this a complaint.


Discussion: Customers should be Users?

from @tavando:

Customers: I wanted to keep customers separate from users - not all users are customers. Customer is when you buy something. Moreover, you would have to add fields to existing user profile and it can collide with other fields from other addons for example

From @edalzell:

How are you going to handle customers logging in to see order status, change account info? You can diff permissions for roles so customer don't have any access to CP, only their order?
I can understand leaving this one the way it is though...just gotta work through the login side of things. Their access should be all front end anyway so maybe it's not a big deal.

Example: account.html
``
{{ statamify:customer }}
My Orders
{{ relate:orders sort='date:desc' }}
{{ if no_results }}
There are no orders yet
{{ else }}

{{ title }}
{{ date }}
{{ status replace="_| " }}
{{ summary.items | length }} {{ if (summary.items | length) == 1 }}item{{ else }}items{{ /if }}
{{ summary.total.grand | statamify:money }}

{{ /if }}
{{ /relate:orders }}
``
Example: order.html
``
{{ statamify:customer }}
{{ collection:orders :slug:is='page.slug' :user:is='user' }}

  {{ if no_results }}

     {{ redirect to='/account' }}

  {{ else }}

Order {{ title }} Summary

   {{ summary.items }}

    {{ name }} {{ if variant }} {{ variant | statamify:attrs }}{{ /if }}

{{ quantity }}

{{ price | multiply:quantity | statamify:money }}

   {{ /summary.items }}

SUBTOTAL: {{ summary.total.sub | statamify:money }}
SHIPPING: {{ summary.total.shipping | statamify:money }}
TOTAL: {{ summary.total.grand | statamify:money }}

Shipping informations

{{ shipping }}
{{ first_name }} {{ last_name }}{{ if company }}, {{ company }}{{ /if }}
{{ if phone }}{{ phone }}{{ /if }}
{{ address }}{{ if address_2 }}, {{ address_2 }}{{ /if }}
{{ statamify:location :country='country' }}
{{ city }} {{ postal }} {{ if region }}, {{ region }}{{ /if }}
{{ country }}
{{ /statamify:location }}

Shipping Method:   {{ shipping_method.name }}

{{ /shipping }}

Billing informations

{{ billing }}
{{ if billing_diff }}
{{ first_name }} {{ last_name }}{{ if company }}, {{ company }}{{ /if }}
{{ if phone }}{{ phone }}{{ /if }}
{{ address }}{{ if address_2 }}, {{ address_2 }}{{ /if }}
{{ statamify:location :country='country' }}
{{ city }} {{ postal }} {{ if region }}, {{ region }}{{ /if }}
{{ country }}
{{ /statamify:location }}
{{ else }}
The same as shipping details
{{ /if }}

``
More or less..


Don't use fork method if it's not available on the platform

fork is sort of discouraged right now as it can be unsafe and deadlocks. Python 3.14 will use spawn which is the default on Windows already. Perhap we should move to spawn here as well?

Hm interesting! I can update to spawn method, the tests will just be a little slower.
Let's ask @Jokeren or @peterbell10 about this.

It might be torchinductor related tests, Peter is indeed the right person to ask


chore: respect provider when determining whether on IC or not

Attempting a PR from a different repo to test #2001
Jira: SDK-279
Previously: dfx only allowed to access the main IC net with two reserved strings for --network.
New: main IC net can also be accessed by an alias that looks like this: "staging": { "providers": [ "https://ic0.app" ], "type": "persistent" }

Closed in favour of #2022


qutebrowser broken on nixos-unstable

 ❯ qutebrowser --backend webengine                                                                          [23:55:13]
Cannot mix incompatible Qt library (version 0x50900) with this library (version 0x50901)
[1]    6745 abort      qutebrowser --backend webengine

Technical details

System: 17.09pre112691.abdb58e407 (Hummingbird)
Nix version: nix-env (Nix) 1.11.13
Nixpkgs version: 17.09pre112691.abdb58e407
Sandboxing enabled: yes

Confirmed here. Same message.
Any way around this?

Seems like this is fixed in the latest unstable. Can anyone else confirm?

Installing the version from nixpkgs-unstable-small did not fix the problem, unfortunately.

Could you try just upgrading your system?

Well, my system is on stable. My user environment is using nixpkgs-unstable-small. I guess I'm gonna have to wait.

I've been getting the same issue for the past week or so, on the master branch, running the virtualbox package's VirtualBox binary. The QT packages are 5.9.1 now, updated from 5.9.0, but I'm failing to see how exactly the latter are interfering with the former. Are the binaries in these packages in need of wrappers to pin down the QT environment?

It is fixed for me on nixpkgs "17.09pre113138.96457d26dd".

Yeah, works on on master. Thanks!


Add parallelization to Inform stage to speed things up

Currently I am just using one processor, and if you're training a bunch of trees it does this in series.  Given that you might want to train upwards of 100 trees, this can be very slow.  Add in some mpi4py logic (as already included in the runMLZ script) to farm out tree training to n processes in parallel to speed this up.

And for reference, the runMLZ script is here: https://github.com/enourbakhsh/MLZ/blob/master/mlz/runMLZ

closing and recreating because I didn't have secret set up properly to copy to project tracker


Why does pub2rmd mode not work?

Hello, has pub2rmd mode been removed or replaced with a new command?

Tha mode was an experiment or proof of concept.
Since found a publickey with that mode is twice difficult than get the original privatekey then i decided to remove it.
I will not add it again

Clearly, thank you for sharing a wonderful product, I am immensely grateful to you for this, and if I suddenly find one of the puzzles, I will definitely share it with you, good luck...


adblocking

tldr; i wont implement adblocking for now
Since adblocking wont be a official feature to be implemented in my desktop app i can only recommend AdGuard to block most of the ads on youtube, youtube music and other websites.
Try AdGuard: https://adguard.com/?aid=32949
or try AdGuard VPN: https://adguard-vpn.com/?aid=32949
Adguard:
✅ Blocks all kinds of ads and trackers
✅ Removes annoying web elements
✅ Saves traffic and speeds up page loading
✅ Works for both browsers and apps
✅ Maintains site functionality and appearance
... for more information visit the links above
You'll support me if you buy from that link.
Trustpilot reviews: https://www.trustpilot.com/review/adguard.com

Anyway, take it easy, I'm uninstalling the app

Hi, won't it be easy to implement the uBlock to the app as an extension since (I assume) it's a browser?

adblocking will be supported unofficially by using plugin system, it will take time tho until its available as plugin

waiting ....

waiting...........

waiting.....................

waiting...................

waiting...........................

waiting...........................

waiting............................

waiting............................

guys this issue is only to exist to remind me that this is a possibility for a feature but its not on my priority list

You don't have to add ad blocking, how about that plugin system

This is a solo project the developer does not owe you built-in adblock or a plugin system, spamming "waiting..." is not productive nor helpful, the developer'll get around to whatever they want whenever they want, if they even want to at all, remember that developers have no obligation to do anything you ask of them. Also remember there is a difference between requesting a feature and pestering someone with spam.

This is a solo project the developer does not owe you built-in adblock or a plugin system, spamming "waiting..." is not productive nor helpful, the developer'll get around to whatever they want whenever they want, if they even want to at all, remember that developers have no obligation to do anything you ask of them. Also remember there is a difference between requesting a feature and pestering someone with spam.

I apologize, I just wanted my "waiting..." to be another sign of support for the feature. I can see why it is annoying or rude. I will be more mindful.

I've added ad-skipping plugin in my fork, If you are interested I would happily PR it for everyone to use.


Detect PDF and convert to text to aid coinlecting.

PDF files can hide text in deflate streams and such, essentially obfuscating any crypto currency addresses. By converting to text we save a great deal of trouble in parsing PDF files. Philosophical point does this violate our principle of not parsing files?

All pdf files (as detected by pyton-magic) are converted to text before processing.


e2e: fail on errors

It would be more user friendly to fail on errors when running e2e tests.
Here is an example of how does make e2e behaves before and after this fix:

Before

$ make test-e2e
test/e2e/e2e.sh
dra-example-driver-cluster
NAME                                       STATUS   ROLES           AGE    VERSION
dra-example-driver-cluster-control-plane   Ready    control-plane   4d4h   v1.31.0
dra-example-driver-cluster-worker          Ready    <none>          4d4h   v1.31.0
node/dra-example-driver-cluster-worker condition met
Error from server (AlreadyExists): error when creating "demo/gpu-test1.yaml": namespaces "gpu-test1" already exists
Error from server (AlreadyExists): error when creating "demo/gpu-test1.yaml": resourceclaimtemplates.resource.k8s.io "single-gpu" already exists
Error from server (AlreadyExists): error when creating "demo/gpu-test1.yaml": pods "pod0" already exists
Error from server (AlreadyExists): error when creating "demo/gpu-test1.yaml": pods "pod1" already exists
Error from server (AlreadyExists): error when creating "demo/gpu-test2.yaml": namespaces "gpu-test2" already exists
Error from server (AlreadyExists): error when creating "demo/gpu-test2.yaml": resourceclaimtemplates.resource.k8s.io "multiple-gpus" already exists
Error from server (AlreadyExists): error when creating "demo/gpu-test2.yaml": pods "pod0" already exists
Error from server (AlreadyExists): error when creating "demo/gpu-test3.yaml": namespaces "gpu-test3" already exists
Error from server (AlreadyExists): error when creating "demo/gpu-test3.yaml": resourceclaimtemplates.resource.k8s.io "single-gpu" already exists
Error from server (AlreadyExists): error when creating "demo/gpu-test3.yaml": pods "pod0" already exists
Error from server (AlreadyExists): error when creating "demo/gpu-test4.yaml": namespaces "gpu-test4" already exists
Error from server (AlreadyExists): error when creating "demo/gpu-test4.yaml": resourceclaims.resource.k8s.io "single-gpu" already exists
Error from server (AlreadyExists): error when creating "demo/gpu-test4.yaml": pods "pod0" already exists
Error from server (AlreadyExists): error when creating "demo/gpu-test4.yaml": pods "pod1" already exists
Error from server (AlreadyExists): error when creating "demo/gpu-test5.yaml": namespaces "gpu-test5" already exists
Error from server (AlreadyExists): error when creating "demo/gpu-test5.yaml": resourceclaimtemplates.resource.k8s.io "multiple-gpus" already exists
Error from server (AlreadyExists): error when creating "demo/gpu-test5.yaml": pods "pod0" already exists
pod/pod0 condition met
pod/pod1 condition met
pod/pod0 condition met
pod/pod0 condition met
pod/pod0 condition met
pod/pod1 condition met
pod/pod0 condition met
test ran successfully

After

$ make test-e2e
test/e2e/e2e.sh
dra-example-driver-cluster
NAME                                       STATUS   ROLES           AGE    VERSION
dra-example-driver-cluster-control-plane   Ready    control-plane   4d4h   v1.31.0
dra-example-driver-cluster-worker          Ready    <none>          4d4h   v1.31.0
node/dra-example-driver-cluster-worker condition met
Error from server (AlreadyExists): error when creating "demo/gpu-test1.yaml": namespaces "gpu-test1" already exists
Error from server (AlreadyExists): error when creating "demo/gpu-test1.yaml": resourceclaimtemplates.resource.k8s.io "single-gpu" already exists
Error from server (AlreadyExists): error when creating "demo/gpu-test1.yaml": pods "pod0" already exists
Error from server (AlreadyExists): error when creating "demo/gpu-test1.yaml": pods "pod1" already exists
make: *** [Makefile:120: test-e2e] Error 1

/cc @klueska

I'm fine either way. I'll let @kannon92 / @byako decide (since Alexey had a similar comment on the original PR adding the e2e tests).


feat(incidents): implements MVP for incidents module

Fixes #2039
Fixes #2038
Fixes #2037
Changes proposed in this pull request:

adds permissions for incidents
adds routing for incidents
adds repository for incidents
adds ability to create, view, and list incidents

LGTM


Consider error diagnostic when SqlClient used when invariant globalization enabled.

Is your feature request related to a problem? Please describe.
In the ASP.NET repo we have updated our API, Worker, and gRPC templates to use invariant globalization. Initially we enabled invariant globalization for those project templates regardless of whether the publishing target was native AOT or not but received feedback that this created friction for SQL client users. As a result we are opting out of invariant globalization non-native-AOT usage.
For native AOT users (where invariant globalization is the default) we believe that there is an opportunity for the SQL client team to raise a diagnostic alert to let them know that they should disable invariant globalization if their project happens to have it enabled.
Describe the solution you'd like
A extend/create Roslyn analyzer which warns if the project in which SqlClient is invoked from has Invariant Globalization enabled that a diagnostic error is raised. This would shift detection of this issue left for the developer instead of crashing at runtime.
Describe alternatives you've considered
We considered disabling invariant globalization for AOT scenarios, but for API scenarios we believe invariant globalization is a better initial choice. Given this it doesn't really make sense for us to have an analyzer for AOT usage in the ASP.NET repo, epecially since SqlClient's lack of support for invariant globalization isn't an ASP.NET specific issue (we understand that there are good reasons for SqlClient to depend on globalization support).
Additional context
Here is the original PR where we enabled invariant globalization: https://github.com/dotnet/aspnetcore/pull/47066
Here is a customer issue reporting the usability problem to us: https://github.com/dotnet/aspnetcore/issues/48186
Here is out PR opting out of invariant globalization for non-AOT scenarios: https://github.com/dotnet/aspnetcore/pull/48238

@mitchdenny thanks for the suggestion. We will discuss this internally and will update you later.

Will SqlClient ever support invariant globalization? The new AWS lambda runtime doesn't have icu, so needs invariant globalization and this then means SqlClient can't be used there

Will SqlClient ever support invariant globalization? The new AWS lambda runtime doesn't have icu, so needs invariant globalization and this then means SqlClient can't be used there

Unlikely. It would take a lot of effort and testing to ensure every part of the code behaves correctly in globalization invariant mode when processing all different types of data. Currently, I don't see that rising in priority over other things any time soon.
This issue (the analyzer check), however, seems relatively easy. We are going to look into it and see what it would entail.

Also relates to:  this topic  #1913


Where are the results of evaluations?

Thanks for this work. Sorry for simple question but I couldn't find any benchmark docs similar to HELM. Where can I find the results evaluated by this library?

The result is in the result dictionary, and the result is in the main. py file

I mean, do you have the benchmark results published somewhere online or in this repo? Can I see the results without running the code just like in HELM benchmark website?

We are working on uploading systematic evaluations to https://github.com/EleutherAI/lm-evaluation-harness/tree/master/results. You can also find evaluations using this library in our Pythia and GPT-NeoX-20B papers


Message searching

Is there a way to bulk search messages?
E.g. get the last 100 messages, this is also a partial attempt to make a bulkDelete command

yes but I mean how do I get the messages from an input node? Using the messageManager and info I can get the message object if I know the ID, but in the case of bulk delete, or just generally wanting to see the last 100 messages then I cannot without going through the discordClient node


[toc] Provide a helper / default support for handle click on toc item / anchor & pausing update?

Context
Typically when there's a sticky table of contents, user expects to be able to click on the item to get to a certain section of page.
With current behavior of toc, it is not guaranteed that when item is clicked, the observe mechanism will see the same item as active. For example, the "scrolled-to" section might be only 40% of screen, and the next section is 30% of screen -> the active item now might be the next section, not the clicked-on one.
Explore a possibility to add default support / helper to debounce click on the anchor / toc item.
Things to consider:

This support should live in the toc action itself rather than createTocStore, because someone might not be using store
What if user turns of anchor option, no support (let users handle) or expose a helper (what does this helper look like)?

resolved with https://github.com/vnphanquang/svelte-put/commit/8d02c832ee9c61f6edf913fc29e75020db286497


port NumSpiroCenters and NumBridgeheadAtoms descriptors to C++

See #278 for more info

first version committed here: 6be8acdaf7

With this implementation issue #278 can also be closed.


Copy-Paste Gadget refuses to copy AE2 cables

Building Gadgets Version
1.0.7
Describe the bug
For whatever reason, the copy paste gadget does not copy the AE2 cables at all, not even listing them inside the materials list, as if they are air blocks.
To Reproduce
Have a random AE2 setup with any configuration, any cables will not be copied over.
Expected behavior
For the whole selected area to have their respective counterparts copied over and listed inside the materials list.
Screenshots

Log Files
Not exactly a crash related issue, but i will post latest and debug log below.
debug.log
https://gist.github.com/coaber/0b1a6aac6ae95c3f96116c2acf2093e7
latest.log
https://gist.github.com/coaber/9d503313fe0b2d1532c277ce1518aaba
NOTE ON RUBIDIUM
Running Embeddium 0.3.19 for reference to this note, unrelated to issue.

Unfortunately because AE2 cables are multiblocks - as in they can have a cable, export bus, and terminal all in one block space - they store this data on nbt. Copy paste gadget doesn’t support copying nbt - and it’s not easy to figure out what items are needed to place that multiblock.
Someday I’d like to support stuff like this but it’s a far future addition ;)


add weak_type framework to abstract eval

This has no user-visible effect as written, but puts in place the framework whereby standard abstract evaluation rules can specify how weak types propagate

Replaced by #4850


feat: add check_asset_is_staked func

Summary
Summary about this PR

Closes #issue

@wow-sven  Please check by this function


Added methods to get timestamp and the password from the passkey.

Added methods to get timestamp and the password from the passkey instead of hardcoded values.
Also added a sanitizer for phone number.
Implemented originally  here.
Added support for Android Studio 3

@kisese The suggestions have been applied.Thanks


New version: Nutstore.Nutstore version 7.1.8

Created by 🥟 Dumplings in workflow run #6436.

Log
Updated: 7.1.7 → 7.1.8
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

/azp run

/azp run


Rename xDai to Gnosis Chain

Overview
xDai is now Gnosis Chain, so we need to update it in the UI.
Requirements

Change the name to Gnosis Chain in config-service
Change the shortName from xdai to gc in config-service
Add a redirect from old xdai: URLs to gc:
Check for any other places where we could be using the shortName xdai in the code
Local storage can keep using XDAI for prefixes to avoid migrating data
Check that hardware wallets still work (networkName in the onboard config)

Links
Slack: https://gnosisinc.slack.com/archives/CQB729LLF/p1639987902410700

Here's a reference for the redirection. We'll need to look closer at the localStorage approach because I think we reference the chains config for it.

For reference: the chain info was update in the ethereum-lists repo https://github.com/ethereum-lists/chains/blob/master/_data/chains/eip155-100.json


Simplify hero service for vue comparison

Stripped it down to more closely parallel the vue version.
No error handling in either version
The profile and logout weren't used (or if they are, belong in a different service) and not in the vue version.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: wardbell sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

wrong branch


when "editor.tabCompletion": "on", after press "Tab", do not hide suggestion widge.

when "editor.tabCompletion": "on", after press "Tab", do not hide suggestion widget.
So that if I want to insert the third best suggestion, just press three times "Tab", it is visible, not need to remember how many times to press.
It will be more convenient.

This issue lacks

copy-paste friendly source code samples
complete sequence of short-cuts or command that you have tried

This issue lacks
* copy-paste friendly source code samples

* complete sequence of short-cuts or commands that you have tried

1, VSC setting, use no short-cut
{
"editor.quickSuggestions": {
"comments": "on",
"strings": "on"
},
"editor.acceptSuggestionOnEnter": "off",
"editor.tabCompletion": "on",
"editor.acceptSuggestionOnCommitCharacter": false
}
2, for example, sample code

IntelliJ IDEA

ust an example, maybe the third suggestion in your list is not "addr", but anyway, I just want to get the third suggestion. And after "space" is input, then the widget hides .

This should be working when just pressing Tab repeatedly. Even without the UI we should be cycling through all the suggestions. Can you try if that works for you


Create Proven Header Payloads

Create ProvenHeader class which will inherit from BlockHeader.
Add following payloads:
provhdr - ProvenHeadersPayload which contains list of up to 2000 proven headers.
sendprovhdr - SendProvenHeadersPayload which informs the peer that we are only willing to sync using the proven headers and not the old type of headers.
getprovhdr - GetProvenHeadersPayload which requests proven headers using a similar mechanism as the getheaders protocol message.
For more info see: https://github.com/stratisproject/Research/blob/master/CoreSyncingAndProvenHeaders/ProvenHeaders.md

Please don't forget to include full comments on every field and every class

Depends on https://github.com/stratisproject/StratisBitcoinFullNode/issues/2141

Fixed


⚠ Bofrost.de has degraded performance

In 1affa91, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1527 ms

Resolved: Bofrost.de performance has improved in 31e3020 after 1 hour, 10 minutes.


Get the current window scene from SwiftUI

If you want support multiple screens, and use frame tags or Popovers.popover(tagged:), you need to specify the window scene. The problem is, getting a view's window scene in SwiftUI is weird.
My current workaround (involves 0.5 second hardcoded delay): https://github.com/aheze/Popovers/blob/5fcaa9d9eb2ed077cd43e323b5a772a04bd6e1be/Sources/PopoverFrameTag.swift#L67-L114
You can then use this in your app's root view via injectWindowScene.
https://github.com/aheze/Popovers/blob/8e22ac703bb847463cd863c22bfd5a3047be5c00/Sources/PopoverFrameTag.swift#L130-L138
WindowGroup {
    ContentView()
        .injectWindowScene() /// Make the window scene available to all subviews. Not ideal, but it works (usually).
}

struct ContentView: View {
    @EnvironmentObject var windowSceneModel: WindowSceneModel

    /// ...

    Text("Hello").frameTag("Your Frame Tag Name", in: windowSceneModel.windowScene)
}

The hardcoded delay especially is annoying. Typing out @EnvironmentObject var windowSceneModel: WindowSceneModel every time you want to access the window scene is ok, but it's still kind of long.
Does anyone know how to get a view's window in SwiftUI? Preferably, something like this:
struct ContentView: View {
    var body: some View {
        Text("Hello")
            .frameTag("Your Frame Tag Name")
    }
}
public extension View {
    func frameTag(_ tag: String) -> some View {
        let windowScene = theWindowSceneThatHostsThisView /// Something like this? So no more need to specify the window scene manually.
        return self.modifier(FrameTagModifier(tag: tag, windowScene: windowScene))
    }
}

Would something like this work?
struct WindowSceneReader: UIViewRepresentable {

    /// A closure that's called when the window is found.
    var found: ((UIWindowScene?) -> Void)

    func makeUIView(context: Context) -> UIView {
        let view = UIView()

        /**
         The 0.5 second delay is needed to wait until the window is first initialized.
         However, it's hardcoded. Does anyone know how to work around this?
         */
/// Use windowSceneDelegate to pass an initialized windowScene to found(...)
/// From https://stackoverflow.com/questions/62652555/how-to-get-uiwindow-value-in-ios-14-main-file
        var window: UIWindow? {
            guard let scene = UIApplication.shared.connectedScenes.first,
                  let windowSceneDelegate = scene.delegate as? UIWindowSceneDelegate,
                  let window = windowSceneDelegate.window else {
                return nil
            }
            return window
        }

        DispatchQueue.main.async {
            found(window?.windowScene)
        }

        return view
    }

    func updateUIView(_ uiView: UIView, context: Context) { }
}

@sans-connaissance thanks, that would indeed get the main window. But I need the current window that hosts the view. Around 99% of the time this is the same as the main window... but if your app supports multiple windows (iPadOS), it will be different. Should have been more clear, sorry.
/// Multiple copies of this view can be created if your app supports multiple windows.
struct ContentView: View {
    var body: some View {
        Text("Hello!") /// <- what window scene is this embedded in?
    }
}

But anyway, I think ShezHsky's #5 PR fixes this issue. I'm still checking over it to see if it will work out, but will update this thread when I'm done.
https://github.com/aheze/Popovers/pull/5/files#diff-a1c21266189878135a0f3c0581755fcd2da315bfa06f0e3c1d8de478d85d48f3

Thanks for taking a look! This issue and your comment helped me to better understand the window and view relationship in SwiftUI projects.

Fixed in #5.

WindowSceneReader is very useful on visionOS when you have multiple windows and want to lock the window resize ratio.


Added support for USDC signatures for mainnet deployments

In continuation of the previous PR's conversation (https://github.com/zkBob/zkbob-client-js/pull/140#discussion_r1234881055) I added support for USDC pools deployed on the mainnet and other chains.

USDCSigner class added
DepositType.AuthUSDC  ( ==  usdc) config type added

@k1rill-fedoseev could you take a look?


Add llvmlite version pinning in requirements.txt

Motivation and Context
Currently installing typed_python using pip installl -e  . (standard Python package editable install) will install an importable version of typed_python but one that doesn't build and that causes pytest failures whenever Entrypoint is used (RuntimeError: LandingPadInst needs to be in a function with a personality.) - pinning llvmlite to be compatible with the pip lockfile fixes this.
Approach
N/A, change trivial
How Has This Been Tested?
pytest from repo root has only performance-related flaky test failures.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

NB - new versions of pipenv have deprecated the pipenv lock --requirements syntax used in the PR checks, and use pipenv requirements instead


Entity array index.

Are entity indexes currently working only as dictionary lookups? In some cases, anything short of an array is pretty bad for performance. (Example: building game with 2D - 3D arrays of blocks, games with a lot of pathfinding or querying of tile grid data.)
Can Entitas generate arrays of entities to allow querying them?
Maybe syntax would look like that:
[EntityArrayIndex(0)]
int x;
[EntityArrayIndex(1)]
int y;

Or sometimes better like that:
public sealed class PositionComponent : IComponent
{
    [EntityArrayIndex3]
    IntVector3 value;
}

public struct IntVector3 : IArrayIndex3
{
    public int x, y, z;

    public GetArrayIndex3 (out x, out y, out z)
    {
        x = this.x;
        y = this.y;
        z = this.z;
    }
}

Which allows you to get 3D array index (in this case) from a component. Will generate method:
var e = GetEntityWithPosition(x, y, z)  var e = GetEntityWithPosition(new IntVector3(x, y, z));

Maybe this is silly but here it is:
public struct IntVector3 : IArrayIndex3
{
    public int x, y, z;

    public Entity IArrayIndex3:GetEntityFromArray3 (Entity[,,] entities)
    {
        return entities[x, y, z]
    }
}

Sometimes you want to have more than one entity with the same index (which is possible with the current lookup system, as far as I understand) so maybe in those cases, an array can internally be an array of lists of entities, but I'm not sure how to differentiate between the two in API.
[ListArrayIndex(0)] vs [ArrayIndex(0)] (?)

Yes, in performance critical areas that makes sense. Our indices used for pathfinding are also based on arrays. We implemented our custom array IEntityIndex and added a few custom EntityIndexAttributes to generate.
I currently can't squeeze in this feature though and would recommend implementing a custom solution.
As a start you can implement IEntityIndex and use the CustomEntityIndex attribute for generation.

Thank you. I'll look into it. I'm not actually gonna be using Entitas for a while until I finish my current game. I'm thinking about my next game, so I hope that maybe you'll find the time to implement this by then (prob 4 months at least).

But currently, Entitas supports that kind of thing via IEntityIndex? Just not as a single attribute? In that case that won't be a problem, as long as it is integrated with Entitas and I don't need to hack that kind of solution in.

Will close, implement IEntityIndex and use [CustomEntityIndex] for custom entity indices.


An option to quick clone a repo to a preset temp folder or /tmp

I would like to be able to quickly skim a repo using vscode without having to select a location for where the repo should sit. Quick Clone should be feasible if the cloning happens to a temp folder.
I am developing an extension for GitHub to quickly open with vscode, so it would be cool if the feature was extended to URLs as well.

Does the GitHub Repositories extension provide what you are looking for here? There is no actual clone, but you can instantly browse, search, edit, etc.


Adding an delay to champion selection

It would be nice if there was either the ability to add a delay to champion selection. Therefore we could just skip the spectator delay by just starting the champion selection 3 minutes later.
Otherwise a good workaround would be if its possible to record the champion selection and play it later while its still recording. Since champion selections in tournament draft mode last for 5-10 minutes (assuming an average draft lasts 7 minutes).
Currently we could start the champion selection recordung as soon as the "real" champion selection was finished. We might be able to skip the first minute where the first two bans go through and we can end the champ selection as soon as the last swap was finished.
This brings us to average 6 minutes cs-duration. Lets say we start this 30 seconds before the players go ingame. After this and the default delay (3:30m) we still have to wait another 2:30 minutes before we can start the game.
The problem with this is that most of the time players have to start the next game around 5 minutes after the previous game. Being 6 minutes behind is to long.
I suggest allowing to play a replay of cs that is still recording or adding a textfield where you can enter the amount of seconds that the cs should be delayed.

It is already possible to record the champ select and replay at a later time

This is not what I suggested. I suggest being able to play a replay while it's still recording.

A i see, we will have a look into that


Questions about your workflow and plan for the future

Really cool ! Thanks a lot for all this work !
I use nuxt in many projects, and a build web extension with https://github.com/antfu/vitesse-webext
I plan to rewrite some projects with nuxtlabs/ui, and the web extension. Your repo is just what I need :)
I want to know about your workflow.
How do you follow the nuxtlabs/ui developement ? Do you watch every new commit on nuxtlabs/ui, or have you automatized some stuffs ? Do you plan to match exactly the same architecture and component ? And of course, will you follow all update made in nuxtlabs/ui ?
Thanks again.

You're welcome, @ManUtopiK . The plan is to regularly update nuxt-ui-vue after each nuxtlabs-ui release but major issues will be resolved immediately.

Great news !
The release of nuxtlabs/ui is currently v2.7.0 and your repo is v0.0.3.
It will be nice to write somewhere (in the README.md ?) the version or commit of nuxtlabs/ui it match.

Yeah, that sounds like a great idea.

The dream come true :ok_hand:
Thanks a lot!


As a developer, when the player builds the truck, the end game condition needs to trigger.

eg: roll credits

Duplicate of #68


Add Import/Export to Swagger Spec

Add SQL Import/Export functionality to swagger spec with examples.
SDK PR: https://github.com/Azure/azure-sdk-for-net/pull/2887
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] Validation errors from the Linter extension for VS Code have all been fixed for this spec. (Note: for large, previously checked in specs, there will likely be many errors shown. Please contact our team so we can set a timeframe for fixing these errors if your PR is not going to address them).
[ ] The spec follows the patterns described in the Swagger good patterns document unless the service API makes this impossible.

No modification for NodeJS

 https://github.com/Azure/azure-sdk-for-python/pull/1020

 https://github.com/Azure/azure-sdk-for-ruby/pull/706


Fix Volunteer Info

Allow admins to edit volunteer's information
Only allow editing for “total hours”, “court required hours”, and “notes” fields
Change the checkbox of the court-required hours into a textbox
Add Pagination

Still didn't figure out the state issue :( It is related to the API call in UserManager that is dealt with via loading in User table, but for some reason, the loading didn't work in pagination.  I'll look more later, lmk if you figure something

Looking great overall! Great progress!
Two issues in addition to pagination:

When an admin modified a volunteer's info, the edits were not reflected until the page was refreshed.
When an admin filtered a volunteer by name, the filter did not seem to work.

Please see this report for more details: https://go.playerzero.app/share/63534995c201c3f2d8548cb0

@bphoebew For the filtering (Yi's 2nd point), take a look atfilteredAndSortedVolunteers() in  EventAttendance.jsx.  The search functionality there is pretty clean

The 2nd issue is fixed!
The first one still remains.

This is fantastic!!!! It looks perfect right now!


Messages not loading until force-quit; new messages not appearing

When opening messages on iPad OS the messages do not open. I can force quite the app, to get the messages to load after quitting a few times, but it does not load right away until I quit.
The first time I click into any app I get a loading page. Then when I force quit the app it brings the messages back up. When the messages are displayed I can not get new messages until I quit the app again. The sometimes I get the loading screen and have to quit again in order to get the message stream to load.
I am getting this error on the current version in the app store and in the test flight versions since I knew iPad OS was new and wasn't sure if that was causing the issues.
Let me know if you have any questions or need anything else.

Hmm! Thanks @jphilipsen05 for the report. That is a pretty bad set of symptoms.

The first time I click into any app I get a loading page. Then when I force quit the app it brings the messages back up.

Small clarification: do you mean the first time you click into any given conversation?
So to see if I can retell the story -- please say whether I've gotten this right:

You open up the app.
You tap on some PM conversation (like in the screenshot), or stream, etc. -- one you haven't looked at in the app before.
It gives you the loading animation shown in the screenshot.... and stays that way for a long time.

I guess you didn't actually say the last part. :slightly_smiling_face: The loading animation is normal if it doesn't yet have all of the messages... but it shouldn't take long to get them, and then it should get replaced by the actual messages. How long did the loading animation continue before you gave up: a second or two, ten seconds, longer?

You force-quit the app, and relaunch it.
You tap on the same PM conversation or stream as before.
This time, you get the messages.

When the messages are displayed I can not get new messages until I quit the app again.

Oh and I almost forgot this part, which is a different and also quite bad symptom. So if I understand the story right -- again, please say whether I've correctly understood:

[... The steps above, leading to ...]
This time, you get the messages.
But: then the other person / another person in the conversation sends a new message...
and it doesn't show up.
You force-quit the app, and relaunch it again.
You tap on the same PM conversation or stream as before.
Now that new message appears, along with the previous messages.

Your story outline is correct. I have waited minutes to get the message to come up. I had it open for 10 minutes before I finally decided to stop seeing if it would come up.
So yes your story and actions are correct. The only part I would add in your second list of points is:

You force-quite the app, and relaunch it again
You tap on the same PM conversation or stream as before
Not that new message appears, along with the previoius messages

on occasion I have to force quit again because it shows the loading screen in the screen shot provided. This part is 50/50 on showing the conversation or loading page.

I have waited minutes to get the message to come up. I had it open for 10 minutes before I finally decided to stop seeing if it would come up.

Cool -- that is very thorough, then :slightly_smiling_face: and definitely helps narrow the possibilities for debugging.

Also I can look on my iPhone and it is instant and works as expected.

Hmm good to know.
FWIW I tried this on an iPhone XR running iOS 13 -- logged out to clear the data, then logged in, and went to a stream and the messages loaded promptly. Also went to a PM conversation and ditto. But it is good to confirm that it works for you on an iPhone -- that makes it less likely that it's a difference between your server, user, etc. and mine, and more likely that the different OS is involved.
(On the iPhone where it works properly for you, is it running iOS 13?)
I'll see about trying this on iPadOS.

I'll see about trying this on iPadOS.

Hmm -- I got out an iPad mini 4 running iPadOS 13.1.2 (17A860), and the issue doesn't reproduce for me: messages load promptly as usual, even after logging into an account I hadn't used there before (so it's always the first time I'm looking at a given conversation.)

two servers I'm working off of and both have the same issue. They are cloud hosted through zulipchat.com

Cool; that's quite helpful information too. Narrows the set of variables involved for debugging.

Still a mystery what the cause is, but given that it didn't reproduce on my iPad it seems less likely it's related to iPadOS (and more to some unknown other variable involved :-/ ). I've edited the title.

Also just to further narrow the variables involved: I went and re-attempted the repro on that same iPadOS device, this time with an org on zulipchat.com. (Previous testing was with a different service, chat.zulip.org.) Still didn't repro -- messages loaded promptly as usual.

So I noticed that your version of iPadOS was different then mine so I updated to 13.1.3 (17A878). That seemed to take out the loading issue so I don't have to force quit to see the messages anymore. Now the only issue is as follows.

Open pm or stream
read messages
Send or receive new message
message does not show up
have to go out of the converstaion and then back in and they are the new messges that are sent/received now show up.

So it appears the loading issues was in the earlier version of iPadOS 13.1 (17A844). However it seems to still be an issue that messages do not load in real time whil the chat window is up. However when I do get the message from someone I do get a 1 new message notification at the top, but no message at the bottom that reflects the notification.
It is better with the update, but not as snappy as the phone still.
thanks for looking into this!

So I noticed that your version of iPadOS was different then mine so I updated to 13.1.3 (17A878). That seemed to take out the loading issue so I don't have to force quit to see the messages anymore. [...] So it appears the loading issues was in the earlier version of iPadOS 13.1 (17A844).

Huh! Good to know, then -- and glad that fixed it. Glad also that you mentioned the exact version, which reminded me to do the same :slightly_smiling_face: and made that difference apparent.
I'll look specifically at repro'ing the other symptom, then, where new messages aren't appearing.

I'll look specifically at repro'ing the other symptom, then, where new messages aren't appearing.

Tried this one, and it works correctly for me -- the issue didn't reproduce. This was on the same iPad mini 4, now running iPadOS 13.1.3 (17A878) (I'd updated it after this morning's experiments), using zulipchat.com.
What version of the app are you running? I tried both 26.9.132 which is the current production release, and 26.11.134 which is the current beta.

I am currently on v26.11.134.
I just deleted it and downloaded the one from the app store which is v26.9.132
The loading page came back, and I still can't see the messages I send. When I do send the message though it comes up immediately on my other clients. I just still can't see it in the iPad app. I also only loaded one of the two zulip servers to make sure it wasn't something with the multiple servers effecting it.
So after going back to 26.9.132 I am back to the same symptoms as before I upgraded my iPad.

I have the exact same problem.  All of it exactly.

PLEASE help!  I really need this bug fixed so that I can use Zulip.

Thanks @juddflamm for the additional report! That is fascinating that it's also on an iPad... given that we have many more people using Zulip on an iPhone than an iPad and we haven't yet heard of this issue happening there, that certainly adds some evidence that it's specific to iPads.
From your helpful screenshot I see you're on an iPad Pro, 3rd gen (i.e. 2018), 12.9". That contrasts with my iPad mini 4 where I was unable to reproduce the issue -- it'd be odd for this issue to somehow depend on the specific physical device model, but who knows. @jphilipsen05 , what model of iPad are you using?

OK, and I've now reproduced the issue! I used the iOS simulator, simulating the same model of iPad Pro as that last report.
More investigation to do, but that gives us a very nice start.

Detailed debugging in a chat thread. Things learned so far:

Simulated devices where the issue reproduces:

iPad Pro (12.9-inch) (3rd generation)
iPad Air (3rd generation)
iPad (7th generation)
(All of these are the latest of their respective lines.)

Simulated devices where it doesn't:

iPad mini 4 -- i.e. the same as my physical device where it didn't
iPad mini (5th generation) -- interesting because that's a 2019 model, the newest of its line just like the ones where it did. And even has an A12 chip just like the iPad Air (3rd gen), and unlike the A10 in the iPad (7th gen).
(All simulated devices were running iOS 13.2 (17B84); the latest version, same as @juddflamm's real device.)

The issue is probably in our communication with the webview where we show the message list, and not in our communication with the server or maintaining our local data-store.

In particular, when you send a message we normally show it in the message list immediately (a "local echo"), before hearing from the server. In an issue like #3567 where the problem really is in our communication with the server, the symptom is that that local-echo version hangs out indefinitely, complete with a little spinner -- not that the message doesn't show up.
If, for some reason, when we try to pass updates to the code inside the webview we always fail, that'd explain the symptoms exactly.
This is also an area where it makes perfect sense that an issue would interact with the OS version... and it's still a little puzzling that it depends on the device model, but it's not a huge surprise if Apple has some model-specific hacksconditionals somewhere in the browser and/or WKWebView implementation.

Likely relevant is our #3572 , which is about the mechanism we use to pass updates to the code inside the webview:

Stop using postMessage on WebView component
This method is extremely useful, which is why we use it -- but it isn't documented, and the component's maintainer has a dim view of it. That makes it perilous to keep using; it's already suffered one breaking change -- apparently by accident! (see fade1d3 and #3564 ) -- between versions ^4 and ^5.
Fortunately it's really just a thin wrapper around the equivalent of injectJavascript. So we can implement something just like that wrapper, and switch to using that.

I think the next debugging step will likely look a lot like a simple version of the said wrapper. So the fix may involve going ahead and switching to that wrapper, i.e. resolving #3572.
Done with detailed investigation for the day, but that's the direction I expect to pick up next.

Thanks @juddflamm for the additional report! That is fascinating that it's also on an iPad... given that we have many more people using Zulip on an iPhone than an iPad and we haven't yet heard of this issue happening there, that certainly adds some evidence that it's specific to iPads.
From your helpful screenshot I see you're on an iPad Pro, 3rd gen (i.e. 2018), 12.9". That contrasts with my iPad mini 4 where I was unable to reproduce the issue -- it'd be odd for this issue to somehow depend on the specific physical device model, but who knows. @jphilipsen05 , what model of iPad are you using?

I’m on an iPad Pro 3rd gen also.

And we have a fix! Details in commit f34c98c4d, which also appears in this issue thread just above here.
In short, the difference that triggered the issue turns out to be that on certain models of iPad, the user-agent string now contains no mention at all of iPad or iOS -- instead, every part of it is verbatim something you'll find on a Mac desktop. Reportedly this is intended as a way of getting websites to give the device their desktop version rather than a mobile version, which is understandable. That also explains why it doesn't happen on the iPad mini, even the 2019 model with a fully-updated OS.
In our case, though, this code never runs on desktop browsers in the first place, and the only platform variation we care about is between iOS and Android. So we'd had the following line:
const platformOS = window.navigator.userAgent.match(/iPhone|iPad|iPod/) ? 'ios' : 'android';

And we use that flag in one place, which is to deal with exactly the postMessage mechanism I mentioned above: that library dispatches the events on the window object on one platform and document on the other, and so we need to know which platform we're on in order to adapt.
The fix is just a couple of lines, and drops any mention of the user-agent in favor of getting the iOS-vs-Android flag injected from the RN environment -- which is a closer match anyway to the variation we're using the flag to compensate for.
I'll make a release with this fix shortly, and I expect to send it out for all users today. If all goes smoothly, it will most likely reach the App Store tomorrow morning.

I'll make a release with this fix shortly, and I expect to send it out for all users today. If all goes smoothly, it will most likely reach the App Store tomorrow morning.

Sent.
Thanks again @jphilipsen05 and @juddflamm for reporting this issue! The details you both provided were very helpful in tracking it down.

OK, and version 26.14.137 is out to the App Store! That has yesterday's fix for this issue.
@jphilipsen05 @juddflamm Please update and try it out, and let us know if that resolves it for you. Thanks again for the reports!

@gnprice
Thank you so much for getting that fixed. I updated my app on the iPad and I am able to see conversations, reply to them and get responses without re-loading the app now.
Thanks!


Polluting ~/.eclipse

Every time I'm updating DBeaver it creates a new (i.e. org.jkiss.dbeaver.product_4.2.0_620785679_linux_gtk_x86_64) ~6MB directory inside ~/.eclipse directory without removing the previous one.
I deleted all ~10 old directories without any consequences, so I'm sure the old ones are not needed. Let's find a way to not waste all that space.

This is standard Eclipses-specific behavior.
This directory is created if DBeaver installed in Program Files (because default Windows security policies restrict programs to write into Program Files). And it is used as a cache for extracted bundles.
Simple removing previous version cache isn't a very good idea. You may have multiple DBeaver versions installed on the same machine.
I can create some special button/checkbox in Windows installed for previous versions cache cleanup.

I'm using DBeaver in Ubuntu so a checkbox in the Windows version's installer won't help.

You may have multiple DBeaver versions installed on the same machine.

Maybe I might, but the fact is I don't have multiple versions. When I'm installing the *.deb package it replaces the old version of DBeaver with the new version.
I understand though. If this is an Eclipse internals related issue I guess I'll just continue manually deleting the old versions once in a while.
Nonetheless, it could be a good idea to investigate this same issue exists in other Eclipse-based popular software, because maybe there is an easy solution.

Well, potentially we can add extra command to deb installer and remove all .eclipse/dbeaver files before installation.


Upgrade Graal native-image support to 19.2.0 (once released)

We are still on 19.0.0 - we should upgrade to latest version once released

[ ]  Upgrade dependencies

[ ] Create new docker image for native-image build

We have upgraded Graal and docker images. svm still on 19.1 - waiting for release.


Changing .nc DEM no data values to zero

HI there,
Last time while processing, I used a simple script to change no data values in dem (.nc) to 0 in order to cover the whole area of the scenes extent.
The script i run was following and it worked
import xarray as xr
import numpy as np
file_path = 'dem.nc'
output_path = 'dem_updated.nc'
ds = xr.open_dataset(file_path) # Load dem
ds['z'] = ds['z'].where(~np.isnan(ds['z']), 0)
ds.to_netcdf(output_path) # Save
print(f"Modified NetCDF file saved to {output_path}")
However, this time when I run again another processing, I tried this way and several other ways to change nodatavalues to zeros including using "jq" tool, but its failing again in geocode step with the same error that last time was solved with the above script.
Is there a nicer and more straight forward way to do it ? Thanks a alot.....
Also, when I try to use other DEM formats than .nc, it fails to process...Any comments on that ?

Typically, this indicates that your DEM coverage is insufficient. As mentioned earlier, PyGMTSAR offers the ability to download three different DEMs with two resolution options (1 arcsecond ~30m and 3 arcseconds ~90m), allowing you to select a DEM that fully covers your area almost anywhere.

Thanks.
Yes ,
fillna.(0) also solves the problem at the time of running the dem downloading code. Some issues with my system. Resolved already now.
Thanks a bunch!


Update README.md

Fixes the name of the repository to be cloned for project setup.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Expose Image element from surfaces

Images can be usable in the HTML document

Covered by pull request #44.


Update Composer dependencies (2021-08-31-00-08)

Visual regression test passed!
View the visual regression test report


GHC 8.4 support

This is currently blocked on OneTuple missing a Semigroup instance. I've emailed John Dorsey about this and will update here when he responds.

If John Dorsey does not respond, you could move to the competing package Only, which supports GHC 8.4

No response from John sadly.
On Mon, 9 Apr 2018, 12:27 George Wilson<EMAIL_ADDRESS>wrote:

If John Dorsey does not respond, you could move to the competing package
Only, which supports GHC 8.4
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/DavidM-D/indexed-list-literals/issues/1#issuecomment-379627380,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0U3OfobDkjWs0zOVYL3Ylw_FItTEqFks5tmuMwgaJpZM4SyD3Q
.

Apologies for the slow response, I didn't receive a notification for this issue. Feel free to email directly if something like this happens again.

Thanks!


Version <IP_ADDRESS> does not recognize Joystick commands

Describe the bug
In the beta update, the two-button commands I use on my joystick (Logitch Extreme 3D) by MobiFlight stopped working, despite appearing in the InputConfigWizard, when I activate DEBUG the error message appears.
I downgraded to the stable version (9.2.0) and it started working again.

Hi Marcelo, I checked on my end and I can say that for my joystick the input events are detected correctly and also the according config is detected correctly.
I reviewed the changes and i cannot find anything.
Can you please post the log from 9.2.0 where it is able to execute the event.
And can you please attch your config

The image below shows the DEBUG reports of the two buttons I use on my Joystick, working with the stable version of MobiFlight 9.2.

0

I cannot reproduce it yet.

I was able to reproduce it and it is fixed.

Thanks!!!


Bundle filePath missing concrete example filePath for a concrete file

Type of issue
Missing information
Description
I arrived at this page looking for the filePath format, the documentation here has an example of loading a file from the bundle but it is a parameter and not a real path.
A concrete example would be a project structure image and a concrete path of how to obtain the file in the image. Eg. a font from "Resrouces/Fonts/MyFont.ttf".
Page URL
https://learn.microsoft.com/en-us/dotnet/maui/platform-integration/storage/file-system-helpers?view=net-maui-8.0&tabs=android
Content source URL
https://github.com/dotnet/docs-maui/blob/main/docs/platform-integration/storage/file-system-helpers.md
Document Version Independent Id
5b7e12aa-3c09-0f82-2fa2-a39c2c8065d8
Article author
@davidbritch
Metadata

ID: 5b7e12aa-3c09-0f82-2fa2-a39c2c8065d8
Service: dotnet-mobile
Sub-service: dotnet-maui

Going to https://learn.microsoft.com/en-us/dotnet/api/microsoft.maui.storage.filesystem.openapppackagefileasync?view=net-maui-8.0 shows that just the name should be used. So the parameter name is misleading? Trying it now.

Hi @Michal-MK
There isn't an example for reading from a file from its project location (e.g. Resources/Fonts/MyFont.ttf), from your app package/bundle because the app package/bundle has no concept of the file layout within the single project. Instead, the single project file resources are placed in different locations in the app package on each platform.

@davidbritch not sure what that means, I used one path for both AN and iOS and it opened the file in the bundle.
I also never mentioned single project but yes we are using a single project approach.
await using var standardFont = await FileSystem.OpenAppPackageFileAsync(FontName);
await using var iconFont = await FileSystem.OpenAppPackageFileAsync(iconFontName);

Names literally being:
const string FontName = VariantService.IsVariantHu
    ? "MuseoSansCyrl_300-1.0.0.ttf"
    : "Gotham-Book-1.0.0.ttf";

string iconFontName = $"IconsFont-{DeviceInfo.Platform}-{MauiProgram.IconsFontVersion}.ttf";

So either I do not understand what you were saying or the paths are in fact platform agnostic. And just the file name is necessary (as I said in the first comment). So feel free to correct me or use the sample I provided here since it works for me.

Tested on MAUI 8.0.21 btw.

Hi @Michal-MK
Thanks for your response. So yeah, we're on the same page now - I've got your meaning so will get the doc updated. Thanks!

@davidbritch I feel like the docs should also mention the fact that the filesystem is flattened, and directories as such do not exist. Also what happens when there are two files with the same name in different directories?


[BUG] expect_row_values_to_have_recent_data with dbt utils 1.0.0

Is this a new bug in dbt-expectations?

[X] I believe this is a new bug in dbt-expectations
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
expect_row_values_to_have_recent_data is failing with the following error
'dbt_utils' is undefined
This happen when we migrate to elementary_data 0.6.6
Expected Behavior
The test should not fail
Steps To Reproduce
Install dbt utils 1.0.0 or 0.9.6
dbt_exepctation 0.8.0
elementary-data 0.6.6
Relevant log output
Environment
- OS:linux
- Python:3.9
- dbt:1.3.1
- dbt-expectations:0.8.0

Which database adapter are you using with dbt?
Note: dbt-expectations currently does not support database adapters are than the ones listed below.

[ ] Postgres
[X] Snowflake
[ ] BigQuery

Additional Context

Hi @olivierdet, as of dbt-expectations release 0.8.0, we no longer have a dependency on dbt-utils. Make sure you run dbt clean && dbt deps to remove old versions and download the 0.8.0 release.
Have you checked with elementary_data if this is caused by something on their end?
It would also help if you provided more of the error log, and also the contents of your packages.yml file.

Hello,
Yes, I've run the clean and deps.
Here you'll find my package
packages:
  - package: dbt-labs/dbt_utils
    version: 1.0.0
  - package: tnightengale/dbt_meta_testing
    version: 0.3.6
  - package: Snowflake-Labs/dbt_constraints
    version: [">=0.5.0", "<0.6.0"]
  - package: calogica/dbt_expectations
    version: 0.8.0
  - package: elementary-data/elementary
    version: 0.6.6

Here the log message :
16:45:18.883710 [debug] [MainThread]: Flushing usage events
16:45:19.443596 [error] [MainThread]: Encountered an error:
Compilation Error in test dbt_expectations_expect_row_values_to_have_recent_data_fact_admin_site_event_tracking_event_at__day__1___event_at_modules_datetime_date_today_modules_datetime_timedelta_14_ (models/lakehouse/core/fact_admin_site_event_tracking.yml)
  'dbt_utils' is undefined

  > in macro default__test_expect_row_values_to_have_recent_data (macros/schema_tests/table_shape/expect_row_values_to_have_recent_data.sql)
  > called by macro test_expect_row_values_to_have_recent_data (macros/schema_tests/table_shape/expect_row_values_to_have_recent_data.sql)
  > called by macro type_timestamp (macros/utils/data_types/data_type.sql)
  > called by test dbt_expectations_expect_row_values_to_have_recent_data_fact_admin_site_event_tracking_event_at__day__1___event_at_modules_datetime_date_today_modules_datetime_timedelta_14_ (models/lakehouse/core/fact_admin_site_event_tracking.yml)

I will also check with elementary package. I see that there are also contributor for this package.

Looks like this error comes from the inclusion of the elementary package then. We no longer use dbt_utils at all. It's possible they've overridden the expect_row_values_to_have_recent_data test and are still using dbt_utils in their version.

Hi @clausherther and @olivierdet, looking into it now.
Will report my findings shortly.

Hi,
We were able to recreate and understand why it happens.
To support both dbt 1.0-1.2 and 1.3 and above, we created our own macros that call dbt if version>1.3 and dbt_utils if version<1.3.
One of these macros is named type_timestamp, which uses dbt_utils.
We import dbt_utils, so I don't fully understand why it is undefined, but it sure happens although everything is installed properly:

Anyway, we are thinking of a temp workaround for you @olivierdet, and will figure out the best solution for this. Also trying to understand if this is a bug in how dbt searches macros in packages, so we could report to them if needed.

@Maayan-s thanks for digging into this! I removed dependencies on dbt-utils b/c managing the chained relationship between dbt-date, dbt-utils and dbt-expectations got too much. Once dbt-core contained all the necessary date macros, I was able to remove dbt-utils from dbt-date and downstream. For type_timestamp we actually have a local version in dbt-expectations b/c the dbt-core version returns an imprecise value, I filed an issue on dbt-core for that.
I don't super understand how the dbt elementary-data package works. How come this issue surfaces in a dbt-expectations macro?

Hi @olivierdet @clausherther @Maayan-s, I'll try to elaborate on why we believe that happens.
The way dbt works is that upon compiling, it iterates over all the macros in the project.
That includes macros of packages as well.
dbt will work out the dependencies of each package and compile the dependencies first until it compiled all the macros throughout the project. For instance, for a user that uses elementary, it'll first compile dbt-utils which is a dependency package, and only then elementary itself.
For a user that installs both dbt-expectations and elementary as @olivierdet,
and given that dbt-expectations's macros don't currently use package-scoping for the macro lookups (using type_timestamp() rather than dbt.type_timestamp().

It could happen that type_timestamp() will resolve to elementary.type_timestamp() which in return will do the following lookup {% set macro = dbt.type_timestamp or dbt_utils.type_timestamp %} as @Maayan-s explained.
The problem here is that dbt_utils's macros were not yet loaded (compiled) into the context object and therefore caused a crash when trying to access it.
We were able to fix it by immediately returning the macros that we override and are likely to appear on other packages, we're releasing a hotfix now.
Hopefully that's clearer.

Got it, thanks for explaining. Yes, the dependencies are an issue for us as well.
The elementary package is no different than any other in how it works, this is why I do think that there is a bug in how dbt handles collisions in macro names.
dbt-core, dbt-utils, elementary and dbt-expectations all have a macro named type_timestamp, and for some reason on a test from dbt-expectations it chooses to use the elementary macro. On the macro itself, the dbt-utils macro is referenced and is not found although it is installed.
When I changed locally the code of dbt-expectations to explicit macro refs (type_timestamp -> dbt_expectations.type_timestamp) it fixed the issue.
Would be happy to open a PR and change it here as well :)
Anyway, we are changing the names of our macros to prevent this from our side as well.

@clausherther
Changing locally the code of dbt-expectations to explicit macro refs (type_timestamp() -> dbt_expectations.type_timestamp()) will prevent this from happening with other packages in the future.
Happy to open a PR if thats ok with you.

Ah, good to know, thanks both @Maayan-s and @elongl!
I'll change our references to be explicit, should probably do that for the dbt-core macros then as well? i.e. dbt.type_int() to be safe?

Yes, that's is generally the recommended practice 👌🏽
Thanks for your help! Much appreciated.

Ok, merged the PR and released as part of 0.8.1, which should hopefully be on dbt package hub with the next hour or so. Thanks for everyone's help in tracking this down! 👍

Hello, I try to install the dbt_expectation 0.8.2, but I’ve got exactly the same issue :-(
Compilation Error in test dbt_expectations_expect_row_values_to_have_recent_data_fact_admin_site_event_tracking_event_at__day__1___event_at_modules_datetime_date_today_modules_datetime_timedelta_14_ (models/lakehouse/core/fact_admin_site_event_tracking.yml)
  'dbt_utils' is undefined

  > in macro now (macros/calendar_date/now.sql)
  > called by macro default__test_expect_row_values_to_have_recent_data (macros/schema_tests/table_shape/expect_row_values_to_have_recent_data.sql)
  > called by macro test_expect_row_values_to_have_recent_data (macros/schema_tests/table_shape/expect_row_values_to_have_recent_data.sql)
  > called by macro current_timestamp (macros/utils/cross_db_utils/current_timestamp.sql)
  > called by test dbt_expectations_expect_row_values_to_have_recent_data_fact_admin_site_event_tracking_event_at__day__1___event_at_modules_datetime_date_today_modules_datetime_timedelta_14_ (models/lakehouse/core/fact_admin_site_event_tracking.yml)

Same issue here, looks as though the current_timestamp() here is getting resolved as an expected macro from dbt-utils or something? As it was pre-1.0.0

@gary-beautypie ugh, I missed that in dbt-date yesterday, thanks for catching that. To be clear, this is only an issue if used in conjunction with dbt-utils. I'll merge your PR later today and release a patch on dbt-date.

Ok, I released both updates that address the dbt.* issues in dbt-date in 0.7.2, which should be on dbt package hub in the next hour or so. The current release of dbt-expectations (0.8.2) should just pull that in once available. Thanks everyone!
(Leaving this open for now.)

dbt-date 0.7.2 seems so have resolved this for me 👌 thanks!


Metal backend on iOS seems to be crashing with ubershader material provider

I am following the sample code related to loading GLTF models directly on my iOS device. From what I have found so far the only way to do this on mobile is to use createUbershaderLoader and pass the result to the AssetLoader. The other option - createMaterialGenerator seems to be available only on the desktop targets.
Using the ubershader with OpenGL backend works fine, but when I switch to Metal I get a flavor of this assert and then a crash:
validateFunctionArguments:3531: failed assertion `Fragment Function(main0): missing sampler binding at index 6 for materialParams_baseColorMapSmplr[0].'
The problem seems to be unrelated to specific gltf file. I tried with several - I got the same assert.
The Metal backend works fine with .filamesh and .filamat files but In this case I am not using  the ubershader and the asset loader.
So my question is: is this a known bug with the uberhader and Metal and is there any workaround which doesn't involve falling back to using .filamesh and .filamat data?

Device: iPhone XR
OS: iOS 12.1
Backend: Metal

cubo.zip

Thanks for the report. @prideout can correct me on this, butcreateMaterialGenerator should work on mobile too. To use it, you'll also need to link against the filamat library . Nonetheless, createUbershaderLoader should work with Metal. I'll take a closer look.

Ah, I now see that we only build gltfio_core on mobile, so we are in fact limited to createUbershaderLoader.

@stomanovski This should be fixed now, please pull and rebuild. Let us know if you have any other issues.

Thank you @bejado! Loading GLTF assets with Metal works. One of my test cases is setting:

With the latest code GLTF assets work on Metal now - thank you @bejado !
I think there is still metal specific issue though. When I call view->setPostProcessingEnabled(false) my app crashes with this assert:
validateDepthStencilState:3794: failed assertion `MTLDepthStencilDescriptor sets depth test but MTLRenderPassDescriptor has a nil depthAttachment texture'
The OpenGL backend correctly renders in both cases. With the default value (true) Metal works fine as well.
Kudos to the filament team for being so quick on fixing issues!

@romainguy Let me know if you want me to file a separate bug for this.

@stomanovski Thanks, I've opened up a separate issue for that: #1215

@stomanovski As a temporary workaround, you can leave post processing enabled but disable all passes:
view->setAntiAliasing(View::AntiAliasing::NONE);
view->setToneMapping(View::ToneMapping::LINEAR);
view->setDithering(View::Dithering::NONE);
view->setAmbientOcclusion(View::AmbientOcclusions::NONE);

Thank you @bejado! This looks like good workaround for my case.


Allow the Batch and Chain onQueue method to accept Backed Enums

Continuing the journey of better enums support in L11 ...
This PR improves the PendingChain and PendingBatch's onQueue method to accept Backed Enums directly as the queue parameter.
Before:
Bus::chain($jobs)
    ->onQueue(QueueName::long->value)->dispatch();

With this PR, you can now pass the Backed Enum directly:
Bus::chain($jobs)
    ->onQueue(QueueName::long)->dispatch();

@onlime what about UnitEnum
@param \UnitEnum|\BackedEnum|string|null $queue

@onlime what about UnitEnum ? @param \UnitEnum|\BackedEnum|string|null $queue

Hi @zakariaarrid I guess it's "too early" to support this now, as all the previous PRs were just about BackedEnum and there must be some reason for it (but don't ask me, I am just following Laravel's current practices...):

#53330
#53079
#53096
#52935

The enum_value() helper supports both BackedEnum and UnitEnum, so honestly I don't see any reason against adding \UnitEnum to all docblocks. But for consistency, this should be done in all the other spots as well.
So maybe someone can comment about this backed mystery.


Why I cannot retrieve computed fields along with collections?

Say I have 2 entities, Product and Tag, where Product has an one-to-many relationship with Tag.
Using the array hydration mode, this query correctly returns the product fields with all tags (as one array):
SELECT p as product, tags FROM app:Product p LEFT JOIN p.tags tags

[
    'product' => [
        'name' => 'Product #1',
        'tags'   => [
            [
                'name' => 'tag-1'
            ],
            [
                'name' => 'tag-2'
            ]
        ]
    ]
]

But this returns one single tag in the array:
SELECT p as product, tags, SUM( 0 ) as computedValue FROM app:Product p LEFT JOIN p.tags tags

    'product' => [
        'name' => 'Product #1',
        'tags'   => [
            [
                'name' => 'tag-1'
            ]
        ],
    ],
    'computedValue' => '0'
]

Why is that?
Using PHP 7 and  "doctrine/orm": "~2.5.5",

I'm so dumb. To get the expected result, it's needed to group by product.id and tags.id.


CLOSE_WAIT connection status after disconnect clients

Many connection still open with CLOSE_WAIT status after client disconnect
[root@SUPV6743 ~]# netstat -nap | grep :3000 | awk '{print $6}' | sort -n | uniq -c
14698 CLOSE_WAIT
73 ESTABLISHED
1 LISTEN
Thanks!

Had a dig around in this one today. Found that primus ping messages were not being correctly returned, and websockets not correctly closed by the server. These two things would have quickly blasted out many open connections.
This may also improve performance somewhat (see #4).

The connections works well now! Don't see more CLOSE WAIT connections.
thanks!

Hi!
I still saw the issue:
2567 CLOSE_WAIT
150 ESTABLISHED
1 LISTEN
BTW; I has stats about GO perf, numbers of GOROUTINES and more... I has captured using
https://github.com/yvasiyarov/gorelic
I see that GC take more time every minutes that application is running, the same in numbers of Go Routines and others.
I can share with you.
Let me know... thanks in advance!

Hello, i tested and i see that the websocket reconnect every 1.2 min only see one annunce and one ping message and close

yes I see the same issue... and if you check into webrtc of chrome see many connections chrome://webrtc-internals/
Now almost I see this message, that be new:
2015/07/07 04:17:19 ERROR - http.HandleFunc: websocket: version != 13
If I open the conections now to
http://<IP_ADDRESS>:3000/rtc.io/primus.js
The response is perfect but If I try to open Websocket fail.. in base to the error into the Gorilla lib, has some issues with the websocket upgrade
https://github.com/gorilla/websocket/blob/master/server.go#L97
hope this help in something

Some stats from GO process... take a look into File Descriptors used after some time...

Hrmm. Thanks for the extra details. Will have another tinker around.

Are you able to send me what the agent string is in the /announce message? It is just truncated in @gonzafirewall screenshot. I just want to make sure I am testing with the same version as you.
In terms of the Gorilla lib it looks like your websocket client is not sending Sec-WebSocket-Version: 13 Are you able to send me a dump of the full client request? What is the client that is trying to connect? The browser versions that implement Websocket V13 is highlighted below:

Hi, here the logs from my Desktop.
/announce|{"id":"cde7244f-cdb4-4c8e-a36d-00403cb18c18"}|{"browser":"chrome","browserVersion":"43.0.2357","id":"cde7244f-cdb4-4c8e-a36d-00403cb18c18","agent":"signaller@2.5.1","room":"aHR0cDovL2hscy5jYXN0dG8ubWUvbGl2ZS9oVkZwVTlDZnM0VmNBNDRHb0xHRi9wbGF5bGlzdC5tM3U4"}

I think the issue with WebSocket version, is why when we use into production with real users, some can be using older version of the browsers and IE, I think we can dismiss this message.
The main issue to check now, is the perf, the amount of FD opened... and the GC time, that always increase... after some minutes stop to response correctly the websocket part, something extrange is the amount of time that the same ID be into the announce. But at the moment of the capture, was only me using 2 tabs to simulate the p2p connection.

Something more info that I can provide to help? just let me know?
THhnks in advance!

It looks like the application built upon rtc.io is sending additional messages on top of announce. In that snippet you sent. There is one announce and several custom /to messages -- I imagine something is trying several paths to broker a connection?
In terms of FD - from what I can tell one FD is opened per websocket. I also create one goroutine per websocket. So that would go some ways to explain the growth in FD's and Goroutines. Does the application ever send any leave commands? Is there any reason why the application would open a websocket and never close it once webrtc peers are established?

P.S. the maximum number of file descriptors that can be opened in linux can be tuned somewhat -- http://www.cyberciti.biz/faq/linux-increase-the-maximum-number-of-open-files/


error message

error: value createFromConnectionString is not a member of object com.microsoft.azure.eventhubs.EventHubClient
any suggestions?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: fd4b0492-b73e-881d-92ef-a9e9d841cd05
Version Independent ID: 3ca1bc50-7003-0766-b14e-a96b100516da
Content: Tutorial: Stream data into Azure Databricks using Event Hubs
Content Source: databricks/scenarios/databricks-stream-from-eventhubs.md
Service: azure-databricks
GitHub Login: @lenadroid
Microsoft Alias: saperla

@gregoryjkramer  Since this issue is not related directly to the doc, I would recommend you to create a thread on the forums - Microsoft Q&A or Stack Overflow
Once you post your issue on forums, it will have visibility across the community which is a better suited audience for such types of issues.

kind of cool that you're doing thing this way now!


expansion of member ordering

PR checklist

[ ] Addresses an existing issue: #0000
[ x ] New feature, bugfix, or enhancement

[ x ] Includes tests

[ x ] Documentation update

Overview of change:
I have expanded the member ordering rules to include other kinds (abstract, readonly), as well as including decorators, and getter and setter methods. Because I am an angular developer, I also have a rule for methods prefixed with ng, as it helps to group angular lifecycle methods together.
Is there anything you'd like reviewers to focus on?
I only wrote one test, I need to write others to cover the additional options.
CHANGELOG.md entry:
[enhancement], [rule-change]

Thanks for your interest in palantir/tslint, @neilsoult! Before we can accept your pull request, you need to sign our contributor license agreement - just visit https://cla.palantir.com/ and follow the instructions. Once you sign, I'll automatically update this pull request.

anyone is free to take this work and do what they will.

I'll go ahead and close this PR for housekeeping. If anybody wants to publish the rule as their own npm package, that's always an option!

I've created a plugin based on this PR that extends member-ordering with decorators support.
You can find it here: https://github.com/Greenek/tslint-plugin-decorator-member-ordering


remove unnecessary Dockerfile

Dockerfile is a leftover from the past when the repo had a sample controller
code.

Thanks!
/lgtm


[viewster] use head request to extract api token

since the request is made to extract the api token from the cookies and the content of the page is not needed it's better to use a head request it contain the api token and it load faster.
curl -I http://www.viewster.com/movie/1200-19447-000/riese/
HTTP/1.1 200 OK
Content-Length: 8067
Content-Type: text/html; charset=utf-8
Date: Fri, 31 Jul 2015 13:47:26 GMT
ETag: W/"1f83-bDxeKhrgGokQXHvrrNfaOA"
Last-Modified: Fri, 31 Jul 2015 13:47:26 GMT
Server: Microsoft-IIS/8.5
Set-Cookie: api_token=JTpk1J%2BcyUSgplJ4UWUcug%3D%3D; Max-Age=604800; Path=/; Expires=Fri, 07 Aug 2015 13:47:26 GMT
X-Powered-By: Express
X-Powered-By: ASP.NET
Connection: keep-alive

Cherry picked in 30a453884e6a4d228ced4cdddcfa8e79a768755a, thanks.


Aggregating on nested fields using Elasticsearch doesn't work

PHP Version
8.2.22
Shopware Version
<IP_ADDRESS>
Affected area / extension
Platform(Default)
Expected behaviour
Aggregating products on a nested field should return the correct aggregation.
Note that this probably needs some logic similar to the loop in the FilterAggregation:
                while (isset($nestedResult[$aggregation->getName()])) {
                    $nestedResult = $nestedResult[$aggregation->getName()];
                }

Perhaps we can add such a loop to hydrate in the ElasticsearchEntityAggregatorHydrator?
Actual behaviour
Warnings are reported:
09:56:14 CRITICAL  [elasticsearch] Warning: Undefined array key "value"

In ElasticsearchEntityAggregatorHydrator.php line 106:

  [ErrorException]
  Warning: Undefined array key "value"

Exception trace:
  at /var/www/html/vendor/shopware/platform/src/Elasticsearch/Framework/DataAbstractionLayer/ElasticsearchEntityAggregatorHydrator.php:106
[...]

And the aggregation isn't working.
How to reproduce
<?php
$context = $this->salesChannelContextFactory->create('token', '019179ff505c713da78aea4b6032ab54');
$criteria = new Criteria();
$criteria->addState(Criteria::STATE_ELASTICSEARCH_AWARE);
$criteria->addAggregation(new MaxAggregation('visibilities.visibility', 'visibilities.visibility'));
$products = $this->salesChannelProductRepository->search($criteria, $context);

Seems to be the same as https://issues.shopware.com/issues/NEXT-8354.

[public] Shopware automated response: This issue is linked to the internal issue https://shopware.atlassian.net/browse/NEXT-38032.
This link is only intended for Shopware employees and for internal use only.
[created from NEXT-38032, comment 489697]

What's the github issue about this? Can't seem to find it.


Increase the possibility of setting constants

I propose to expand the possibilities of setting constants.
For example partitionSize = (7 * 24 * time.Hour).Nanoseconds() is the constant, but compiler think that it's not constant.
One solution, that I can see - check reflect.Kind type of all variables in the expression. If all types are primitives - it's constant.

It's non constant because of the method call to Nanoseconds(), not because of time.Hour,
Having const inputs into a function doesn't guarantee that it's side effect free and the result is const.
Side note: const partitionSize = int64(7 * 24 * time.Hour) works.


Retry System Errors

The following system errors should be automatically retried:
mesos-lost, nfs, pull-timeout, pre-timeout, post-timeout, system-timeout, ingest-timeout, pull, unknown, database
Update the code to default the should_be_retried field to true for these errors and add code in the database updater to update existing installations.

mesos-lost and nfs errors have been removed


Core resource allocation using time-slice

Hi, I came across this repos from tkestack/gpu-manager. I saw that in gpu-manager, vcuda was used for core resource sharing, I wonder why it was changed to time-slicing. In my opinion, the ability to execute parallel would be more optimized compared to time slicing. Could you please share more about this design decision? Thank you very much.

If you want to use core resource sharing, you need to put all different tasks into the same context, such technics is called MPS, but there are many issues on MPS, so we can't apply that in production environment.

Hi, thanks for your prompt reply. I think this project is still using hami core right? I take a look at the source code and it seems like the sharing method is by allocating cores for each kernel launch not the nvidia time slicing method right? Have you ever try benchmarking the performance?

yes, hami-core is not using nvidia time slicing method, it implements its own time slicing strategy by blocking kernel submission of certain tasks periodically. the performance introduced is less than 5%

I mean the performance comparation between nvidia time slicing and the custom time slicing when there are multiple containers launch kernel at the same time. Theoretically, I think the custom method should be better since it allow parallel kernel launching while nvidia time slicing does not?

both nvidia and custom don't support parallel kernel launching

em... i'm not sure if we can use nvidia time slicing in HAMi-core,  we can discuss that if you have a plan

I think for nvidia time slicing we only need to config the node but it is not as flexible since we have to specify the number of replicas and whenever this config is changed, gpu-operator has to be restarted so I guess it is not production ready as well. I am just curious about the performance comparison in practice. But if both cannot execute kernel launch in parallel, then probably nvidia time slicing will have better performance since all containers have full access to the resources. In that case, we are somewhat trading performance for better governance right?

i think i get what nvidia time-slicing means, it simply throw that task into GPU, and let them compete with each other. It doesn't guarantee how many compute power it can use. it equals to submit all vGPU tasks without specify nvidia.com/gpucores.

I see, but I still haven't figured why we should limit the core utilization when we are not able to run in parallel anyway. It's either we let them run in parallel and enforce core utilization quotas or we let them run sequentially with the entire core resources right? In that case we should enforce the quotas by execution time spent for each process I suppose, not sure if it is possible though.


Question about running run_pipeline.py

Hi, I'm currently using jetson agx orin to run T-MAC and I'm confused about  this:
in README i was instructed to run run_pipeline.py, which falls into the llama.cpp/build/main, i'm not sure the relation between T-MAC and llama.cpp and i'm not sure if this is running the optimizations in T-MAC or simply testing llama.cpp? As i inspect T-MAC is integrated into llama.cpp so i suppose llama.cpp is used to transform gguf file and then T-MAC is applied, i'm not sure if this is correct
I've already run the run_pipeline.py and due to the above reason i dont know how to proceed

T-MAC is only a kernel library to accelerate mixed precision GEMM. llama.cpp is a framework for inference. The current end-2-end inference is implemented by integrating T-MAC kernels into llama.cpp.

Ok I got it. So can i suppose that i can get the result you show in README when running run_pipeline.py? For example using python tools/run_pipeline.py -nt 12 -o /path/to/BitNet-3B-b1.58 -m hf-bitnet-3b on my jetson agx orin and getting the more than 20 tokens/s as a result?

Sure


Ensure the updates with crashes reverts the change to scriptInfo

@typescript-bot cherry-pick this to release-5.5


Codespaces devcontainer

Notes for Reviewers
This PR fixes #5904
Signed commits

[x] Yes, I signed my commits.

Thanks for this, @sivanaikk 👍

Reviewing, as I was researching this to see if we could use devcontainers to ease contributor onboarding the projects.

There is UI integration test that is failing, us of syntax error in indexui_spec.js.
However, I don't think this changes are related to the tests run.

Syncing with master to re-run with passing indexui_spec.js.

@sivanaikk  Let's discuss this on the Meshery Dev call. Please add this as an agenda item in the meeting minutes if you would. :)

@sivanaikk Let's discuss this on the Meshery Dev call. Please add this as an agenda item in the meeting minutes if you would. :)

Just added it to the Meeting agenda. Thank you 🙌

@sivanaikk Let's discuss this on the Meshery Dev call. Please add this as an agenda item in the meeting minutes if you would. :)

@sivanaikk Are you still working on it?

Closing due to inactivity


chore(docs-app): allow switching to newer versions

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feature for the docs app
What is the current behavior? (You can also link to an open issue here)
You cannot switch to a newer version from an older version in the docs app.
What is the new behavior (if this is a feature change)?
For docs app versions that contain this commit, switchting is possible. The docs app
will request the new versions-data.json file from the snapshot folder and fill the version switcher with
this data.
Does this PR introduce a breaking change?
No
Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
~[] Tests for the changes have been added (for bug fixes / features)~
~[ ] Docs have been added / updated (for bug fixes / features)~

Other information:
With this patch, the docs app will request available versions data from the snapshot,
which are now stored in a separate versions-data.json file.
This only affects docs apps that contain this commit, so older doc apps
will still only display the versions up to their own version.

:+1: This is a much needed improvement.

@Narretz and I had a chat about this. We came up with new idea that doesn't require a change to the docs app and will work with older versions too.
It involves rewrite rules on the code.angularjs.org server...