Routing problem with certain prefix length

Dear developer:
Hello !
I'm encountered with a problem. I'm using a Debian host as a soft router for several devices. My ISP is China Mobile corp. and I'm able to acquire IPv6 addresses and prefixes. However, the prefix length I receive is usually ::/60. At such circumstance, dhcpcd will assign a ::/64 prefix to my LAN interface br0, but adding a route to ::/60 network into the route table, which is always marked Unreachable. If I manually add a route to the correct ::/64 network via br0, everything works just fine. Beside this, the route added is set as via lo, the localhost interface, which ought to be br0, the interface of LAN who is asking for an IPv6 address to be assigned with. I'm confused if dhcp client can deal with such sitiation and route the network prefix it assigns instead of what it receives from ISP.
My dhcpcd version is 7.1.0 from Debian's apt source, and my system is Debian 5.10. I use PPPoE for Internet access. I want to acquire an IPv6 prefix for my LAN interface br0, and add the routing rule: to the assigned ::/64 net segment via br0 to the route table of Debian host. The corresponding part of dhcpcd configuration is as follow:
slaac private
interface ppp0
ipv6rs
iaid 1
ia_pd 2 br0

I'm not quite familiar with network setups, so I tend to believe this problem is caused by my misunderstanding or wrong configuration. If so, I really need some hint. If any information missing please let me know. Thank you very much !

Maybe I should post some log here:
root@server:~# ifconfig
> br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
           inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
           inet6 fe80::4c9b:8773:1f42:1f0c  prefixlen 64  scopeid 0x20<link>
           inet6 2409:8a14:11b3:1c8d::1  prefixlen 64  scopeid 0x0<global>

root@server:~# ip -6 route
> unreachable 2409:8a14:11b3:1c80::/60 dev lo proto dhcp metric 201 pref medium
> 2409:8a14:11b3:1c8d::/64 dev br0 metric 1024 pref medium

log from dhcpcd, I marked the lines that may be useful by [> xxxx <]:
Oct 11 22:11:17 server dhcpcd[3940]: br0: IAID 26:7e:08:96
Oct 11 22:11:17 server dhcpcd[3940]: br0: soliciting a DHCPv6 lease
Oct 11 22:11:17 server dhcpcd[3940]: ppp0: IAID 00:00:00:01
Oct 11 22:11:17 server dhcpcd[3940]: ppp0: IA type 25 IAID 00:00:00:02
Oct 11 22:11:17 server dhcpcd[3940]: ppp0: rebinding prior DHCPv6 lease
Oct 11 22:11:17 server dhcpcd[3940]: ppp0: soliciting an IPv6 router
Oct 11 22:11:17 server dhcpcd[3940]: ppp0: soliciting an IPv6 router
Oct 11 22:11:17 server dhcpcd[3940]: ppp0: Router Advertisement from fe80::8a66:39ff:fe8d:f050
Oct 11 22:11:17 server dhcpcd[3940]: ppp0: adding address 2409:8a14:110b:45a1:xxxx:xxxx:xxxx:xxxx/64
Oct 11 22:11:17 server dhcpcd[3940]: ppp0: Router Advertisement from fe80::8a66:39ff:fe8d:f050
Oct 11 22:11:17 server dhcpcd[3940]: ppp0: adding address 2409:8a14:110b:45a1:xxxx:xxxx:xxxx:xxxx/64
Oct 11 22:11:17 server dhcpcd[3940]: ppp0: adding route to 2409:8a14:110b:45a1::/64
Oct 11 22:11:17 server dhcpcd[3940]: ppp0: adding default route via fe80::8a66:39ff:fe8d:f050
Oct 11 22:11:17 server dhcpcd[3940]: ppp0: adding route to 2409:8a14:110b:45a1::/64
Oct 11 22:11:17 server dhcpcd[3940]: ppp0: adding default route via fe80::8a66:39ff:fe8d:f050
Oct 11 22:11:18 server dhcpcd[3940]: ppp0: REPLY6 received from fe80::8a66:39ff:fe8d:f050
Oct 11 22:11:18 server dhcpcd[3940]: ppp0: renew in 86400, rebind in 138240, expire in 259200 seconds
Oct 11 22:11:18 server dhcpcd[3940]: ppp0: REPLY6 received from fe80::8a66:39ff:fe8d:f050
> Oct 11 22:11:18 server dhcpcd[3940]: lo: adding reject route to 2409:8a14:11b3:1c80::/60 <
> Oct 11 22:11:18 server dhcpcd[3940]: ppp0: delegated prefix 2409:8a14:11b3:1c80::/60 <
> Oct 11 22:11:18 server dhcpcd[3940]: br0: adding address 2409:8a14:11b3:1c8d::1/64 <
Oct 11 22:11:18 server dhcpcd[3940]: ppp0: renew in 86400, rebind in 138240, expire in 259200 seconds
> Oct 11 22:11:18 server dhcpcd[3940]: lo: adding reject route to 2409:8a14:11b3:1c80::/60 <
Oct 11 22:11:18 server dhcpcd[3940]: ppp0: delegated prefix 2409:8a14:11b3:1c80::/60
> Oct 11 22:11:18 server dhcpcd[3940]: br0: adding address 2409:8a14:11b3:1c8d::1/64 <

7.1.0 is really old. You might wanna try 9.4.1 from Debian/Testing.

Upgrading has successfully solve the problem. Thank you so much !
If not too complicated, whould you mind explaining why it is necessary to add the [unreachable IPv6 ::/60 prefix] to the route table ?

By adding a reject route we can tell any incoming request for a route in our prefix we haven't assigned - such as a request to 2409:8a14:11b3:1c8e::1 - that it doesn't exist faster because your router doesn't have to try and find the non-existant host,

I get it. Thank you again !


Fixes minor typos in README

Signed-off-by: Thien Nguyen<EMAIL_ADDRESS>

This is mainly to check my signature on commits.

This looks good. All checks pass and @tnguyen-ornl is covered under the UT-Battelle MLA.


[otp_ctrl] DAI rd/wr access between digest and reset

Hi Michael,
I thought we talked about this but could not find any email/issues related to it. So I filed this one for tracking. Please feel free to mark it as duplicated if you find the original thread.
The issue comes as the sequence below:

lock partition (say CreatorSwPartition) with CSR write
Issue Partition CreatorSw read/write via DAI interface
Issue reset

During sequence 2), current RTL allows read/write to happen without any error. Do you plan to add some error report for sequence 2? Shall we block the write access?
Thanks,
Cindy

Yes, we have already discussed this I think.
The behavior you describe is due to how the OTP is structured internally.
I.e. the read/write access locks are determined based on the digest values that are read upon initialization of the OTP controller.
Hence, in order to take effect, a reset is required.
I currently don't plan to change this behavior since it would make the internal structure more complex and less secure (i.e., the DAI would need additional connections to the partition controllers to change values inside the buffer registers).
Hence, I have added some additional guidance to the programmers model that highlights this behavior here:
https://docs.opentitan.org/hw/ip/otp_ctrl/doc/index.html#locking-partitions
Does that make sense?

Yes, we have already discussed this I think.
The behavior you describe is due to how the OTP is structured internally.
I.e. the read/write access locks are determined based on the digest values that are read upon initialization of the OTP controller.
Hence, in order to take effect, a reset is required.
I currently don't plan to change this behavior since it would make the internal structure more complex and less secure (i.e., the DAI would need additional connections to the partition controllers to change values inside the buffer registers).
Hence, I have added some additional guidance to the programmers model that highlights this behavior here:
https://docs.opentitan.org/hw/ip/otp_ctrl/doc/index.html#locking-partitions
Does that make sense?

Thanks Michael for clarifying. I forget to check the spec. Make senses. I think the spec is clear and I will close this issue.

Thanks Michael for clarifying. I forget to check the spec. Make senses. I think the spec is clear and I will close this issue.


Etcd: Update gopkg.in/yaml.v2 to v2.2.8

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

/approve


Fix the number of params on CSLReferences

This is to fix a complilation error with the newer pandoc.

Codecov Report

Merging #13 (574e196) into main (88ca589) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #13   +/-   ##
=======================================
  Coverage   74.71%   74.71%
=======================================
  Files           7        7
  Lines         439      439
=======================================
  Hits          328      328
  Misses        111      111

Continue to review full report at Codecov.

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


Problem install .Net Core on Raspberry Pi Model B

I tried to install .Net Core on my Raspberry Pi Model B device with OS "Raspbian Jessie Lite".
I used the installation instructions here: https://www.microsoft.com/net/core#debian
I had a problem with a missing library libunwind:
pi@raspberrypi:~ $ sudo curl -sSL https://raw.githubusercontent.com/dotnet/cli/rel/1.0.0-preview1/scripts/obtain/dotnet-install.sh | bash /dev/stdin --version 1.0.0-preview1-002702 --install-dir ~/dotnet
dotnet_install: Error: Unable to locate libunwind. Install libunwind to continue

I tried to find it alone, but I could not.
pi@raspberrypi:~ $ sudo apt-get install libunwind
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package libunwind

This device model (Raspberry Pi Model B) is not supported?

I believe the package name for libunwind is libunwind8.

@svick Thank you!
But I have another problem:
pi@raspberrypi:~ $ sudo curl -sSL https://raw.githubusercontent.com/dotnet/cli/rel/1.0.0-preview1/scripts/obtain/dotnet-install.sh | bash /dev/stdin --version 1.0.0-preview1-002702 --install-dir ~/dotnet
dotnet-install: Downloading https://dotnetcli.blob.core.windows.net/dotnet/beta/Binaries/1.0.0-preview1-002702/dotnet-dev-debian-x<IP_ADDRESS>-preview1-002702.tar.gz
dotnet-install: Extracting zip
dotnet-install: Adding to current process PATH: /home/pi/dotnet. Note: This change will be visible only when sourcing script.
dotnet-install: Installation finished successfuly.
pi@raspberrypi:~ $ sudo ln -s ~/dotnet/dotnet /usr/local/bin
pi@raspberrypi:~ $ dotnet
-bash: /usr/local/bin/dotnet: cannot execute binary file: Exec format error
pi@raspberrypi:~ $ sudo dotnet
/usr/local/bin/dotnet: 1: /usr/local/bin/dotnet: Syntax error: redirection unexpected

What is the problem ?

That's the same error as https://github.com/dotnet/cli/issues/3197: it fails, because there are no binaries for ARM.
I think if you want to use .Net Core on that machine, you will need to build and publish your code on another machine and then copy it to the Pi.

Correct. .NET Core 1.0 doesn't have ARM support. It is in the roadmap and we have many community members working with us on adding ARM support so I hope we'll have something soon.

I think if you want to use .Net Core on that machine, you will need to build and publish your code on another machine and then copy it to the Pi.
So it works to run an ASP.NET Core app on Raspberry Pi but not building the source code?

@OskarKlintrot, I'm not imagine how to do it.
For example, on another computer I'm doing:
mkdir app
cd app
dotnet new
dotnet restore
dotnet build

As a result, I get app.dll file.
How to run it on Raspberry, if вotnet does not work?
dotnet run app.dll?
pi@raspberrypi:~/test $ dotnet run app.dll
-bash: /usr/local/bin/dotnet: cannot execute binary file: Exec format error

Note: On raspberн not installed mono. I want to run the .net core programs without mono.

@neyromant: Neither do I. I really hoped ASP.NET Core would work without Mono on RPi.

@OskarKlintrot, I think, what you need is a ASP.Net Core Standalone Application.
When you remove "type": "platform" from your Microsoft.NETCore.App dependency, and add a runtimes section at the root level of your project.json, you can call dotnet publish -c Release -r {yourRuntime}.
After that you get an export, which run on the platform you specified without installing dotnet cli. There should be a binary with the name of your project you can call to start your app, but I never tried it on a Raspberry Pi.
Dont forget, you still need the right glibc, libunwind, and libicu.
Example for the runtimes section:
{
  "runtimes": {
    "win7-x64": {},
    "centos.7-x64": {},
    "ubuntu.14.04-x64": {},
    "osx.10.11-x64": {}
  }
}

A list of current valid rid's, which can be used in the runtimes section can be found here.
Hope that helps.

Thanks for answers.
But, apparently, has no runtime for linux arm: https://github.com/dotnet/corefx/blob/master/pkg/Microsoft.NETCore.Platforms/runtime.json
I saw only arm runtimes for windows (ex. "win8-arm"), but for linux only x64.

@neyromant check it once again, recent commit added linux arm runtimes

@neyromant did you manage to run the dotnet core app on raspberry pi ?

@arkadiuszwojcik , @ahmed-sherien  No. I created a simple project:
Program.cs:
using System;
namespace TestConsole
{
    public class Program
    {
        public static void Main(string[] args)
        {
            Console.WriteLine("Hello, world!");
            Console.WriteLine("This is a .net core app!");
        }
    }
}

project.json:
{
  "version": "1.0.0-*",
  "buildOptions": {
    "emitEntryPoint": true
  },

  "dependencies": {
    //"Microsoft.NETCore.Runtime.CoreCLR-arm": "1.0.1-beta-23225",
    "Microsoft.NETCore.Runtime.CoreCLR": "1.1.0",
    "Microsoft.NETCore.DotNetHostPolicy": "1.2.0-beta-001299-00",
    //"System.Console": "4.3.0"
    "system.console": {
      "version": "4.4.0-beta-24911-08"
    }
  },

  "frameworks": {
    "netcoreapp1.0": {
      "imports": "dnxcore50"
    }
  },

  "runtimes": {
    "win10-x64": {},
    "linux-arm": {}
  }
}

dotnet build

Project TestConsole (.NETCoreApp,Version=v1.0) will be compiled because inputs were modified
Compiling TestConsole for .NETCoreApp,Version=v1.0

Compilation succeeded.
    0 Warning(s)
    0 Error(s)

Time elapsed 00:00:00.9394322

When compiling for ARM linux i get an error:
dotnet build -r linux-arm

Project TestConsole (.NETCoreApp,Version=v1.0) will be compiled because expected outputs are missing
Compiling TestConsole for .NETCoreApp,Version=v1.0

Compilation succeeded.
    0 Warning(s)
    0 Error(s)

Time elapsed 00:00:00.9334337

Failed to make the following project runnable: TestConsole (.NETCoreApp,Version=v1.0) reason: Expected coreclr library not found in package graph. Please try running dotnet restore again.

@neyromant
Doing dotnet restore with linux-arm shows:

System.Diagnostics.Process 4.1.0 provides a compile-time reference assembly for System.Diagnostics.Process on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with linux-arm.
System.Globalization.Extensions 4.0.1 provides a compile-time reference assembly for System.Globalization.Extensions on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with linux-arm.
System.IO.FileSystem.Watcher 4.0.0 provides a compile-time reference assembly for System.IO.FileSystem.Watcher on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with linux-arm.
System.IO.MemoryMappedFiles 4.0.0 provides a compile-time reference assembly for System.IO.MemoryMappedFiles on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with linux-arm.
System.Net.NameResolution 4.0.0 provides a compile-time reference assembly for System.Net.NameResolution on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with linux-arm.
...

Suggest that those dependencies has no build yet


My .vue file no longer highlighted

After updating the latest version, my Vetur plug doesn't seem to work anymore
Version: 1.37.1
Commit: f06011ac164ae4dc8e753a3fe7f9549844d15e35
Date: 2019-08-15T16:16:34.800Z
Electron: 4.2.7
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Darwin x64 17.3.0

The extension's repo has this FAQ section by @octref. Maybe it can help you.

Likely because VS Code messed up the upgrading extension process and installation is complete. Try the link by @gjsjohnmurray above. Thanks!


Allow a Set command for HybridKubernetes.

ARM (Control Plane) API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!

[ ] New resource provider.
[ ] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix OpenAPI spec quality issues in S360.
[ ] Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
[X] Other, please clarify:

Extending Powershell interface to allow a Set- command (using PUT REST API method) to perform updates that an Update- (PATCH REST API method) cannot perform.

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[X] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[X] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

Waiting for permission to add tags to filter though then expected to add BreakingChange-Approved-BugFix tag.


Change Fault Station Clustering

Current fault station clusters into 8 clusters using K-means clustering. DBSCAN also provides a large cluster with 100s of stations. Need to improve the clustering, using a combination of DBSCAN and NN to provide a sample of smaller cluster groups of stations that are closer to respective fault lines
It is a prerequisite for forming the rings and

DBSCAN clustering completed for station clustering. Also added HDBSCAN, OPTICS, and KMEANS. Avoided Agglomerative and other hierarchical clustering methods.

All cloud and graph clustering sequences were complete and results were obtained.


Error Running production flutter web  on mobile device ( android & ios)

hello, i've found bug running production flutter web on mobile device ,
this is screenshoot mobile device

if you need to run on the web , here the link : https://beta.goleg.web.id/
step reproduce the issue

Click on informasi dapil

but on desktop version it normal

done, in flutter web there was a bug when using custom current location

done, in flutter web there was a bug when using custom current location


Dark theme

A dark theme for those of us who work at night.
For common pages I use DarkReader, but this can't be used at extension pages. A dark theme could do the job.

Thanks @dbautistav for the report I'll take a look at darkreader and see what the extension would look like and create a dark theme. If you have examples of dark themes that you consider good please share them! :smile:

Hey @jsargiot!

Based on these screenshots, here are some suggestions:

The blue-ish parts (top and bottom frames, some labels) when in dark theme could be something like: #89696A.
The most light parts (like the main status bar status, time, size, type), when dark: #1B1B1A.
The "Headers"/"Body"/"Response" frames when dark: #1F1F1E.
Text color on dark background: #CDCAC5.
Red buttons when dark theme: #DAAEA9.

Those colors were "extracted" from screenshots with Gpick. Someone with better color theory knowledge than mine could easily improve the theme.

Dark theme has been added to restman on commit 79b87cc.


More invalid SyntaxError cases to consider

Misspelling some keywords (when there are enough clues). Examples inspired by https://www.youtube.com/watch?v=o0DTRGEPif8

[ ] misspelled keyword

fro i in range(10):

[ ] Missing keywords

for i range(10):

[x] Also, in the console, try to catch an issue warnings for redefining print as in

print = 42

The first two errors are now flagged as missing a comma or operator between two names. This is not correct in these specific cases but should be appropriate in general. Closing for now and will consider revisiting if there is a report from actual users.


How to add greater than filter in apache superset?

Has superset changed its folder locations and interface? From a youtube tutorial, I found these options available in filter box:

But what my filter looks like is:

I want to apply a filter box which gives me flexibility to apply a filter over ranges. For example, this is my table:

I want to add a filter where it should display only those table results where videos>=100 and videos<=10000. Although filter allows me to select multiple value but what it doesn't allow me is to apply ranges, and as you know there are so many values between these two ranges, it gets very inefficient to apply these filters.
I tried to apply the filter as shown below:

But how it works is this way:

When we look at time filter:

It works well and offers tons of customization, I was just curious if we can dynamically filter time then why not other values. Please do let me know if you have something for this.
Additional context
Add any other context or screenshots about the feature request here.

Agree, this would be great if dynamic filters added to Superset. I am not sure if it works for your problem, but you can try to use CASE function to the range you need to filter. In order to do this, just add a new column in datasource editor with required SQL,
then use this column in FIlter View.
CASE
    WHEN condition1 THEN result1
    WHEN condition2 THEN result2
    WHEN conditionN THEN resultN
    ELSE result
END;

Oh amaing @aussat Thanks a lot will try this out.

Any update how we can add  less than greater than filter in Filter Box so we can apply it on the dashboard, we do get to add these filters in other charts, but not in Filter Box

@junlincc
Any chance this might be possible soon?

Although we can filter columns by range in explore chart screen, it is weird that we cannot filter columns by range in dashboard filters. Any progress?

Although we can filter columns by range in explore chart screen, it is weird that we cannot filter columns by range in dashboard filters. Any progress?

Hi all
I agree this is a missing functionality.
It can be requiered to offer the user the possiblity to zoom on specific ranges of some numerical fields.
For example I need it for some bubble charts.

@aonurdemir @vialcollet the new native filters feature is currently under heavy development, and we've already implemented a range filter which adds this feature (greater than, less than and range). Expect the feature to be in testable state fairly soon, but general availability is probably still a few months away.

while you are waiting for the new features, you could try using jinja template to create range filter as workaround.
we dont have an exact tutorial for it yet, but you can refer to ..
https://www.youtube.com/watch?v=AcnNlIkfCiI
https://www.youtube.com/watch?v=dE1QlhunWMs
@vialcollet

Hello,
This feature is not in 1.3.2, any idea when will it be added?

Is there any update for this in superset 2.0 ?

@erfanu25 please take a look at the Numerical Range Filter in Dashboard Native Filters which has been available for quite some time.


future of Sphinx Search

The Sphinx Search project has been inactive for the last 7 months. A rather unusual long period!
I wonder if it's time to move to another solution: solr, ES, ...

Just because something has been updated, doesn't mean it's no longer useful! Of course, if there are flaws in Sphinx that are causing problems for you, then definitely evaluate other options - but I know I'm using Sphinx without problems in several projects. Seven months isn't that long (and indeed, there was a commit just the other day: https://github.com/sphinxsearch/sphinx/commit/e93969e20920737a24ad9b55651bb9b72fd81174) - and I put more value in stability and function, rather than the frequency of updates.
Use what's best for your projects and your colleagues - Sphinx, ElasticSearch, Solr, whatever - but that's not really a Thinking Sphinx issue :)

I hope you are right, as I like Sphinx Search.


Continue Your OData Exploration with EPM

Tutorials: https://developers.sap.com/tutorials/odata-02-exploration-epm.html
Sadly, access via WebGui has been disabled on 08.09.2023, see https://blogs.sap.com/2017/12/05/new-sap-gateway-demo-system-available/ .Therefore the first unit of this tutorial is not relevant and I recommend to update it. I was thinking about using Eclipse for checking the hierarchy visually, but you might have a better idea (as Eclipse is slowly but steadily being dropped off by SAP, too).

@qmacro can you please respond to the user's feedback?  Thank you.


Define if message signature is to be required for this release

Currently, it appears that the demo API node has a minimal implementation for message signature verification. While a message signature is required, the system is actually accepting any valid elliptic curve signature—even if it belongs to a different message.
We need to decide whether to include this feature in the next release. If we choose to include it, I suggest that we implement it fully. This means:

Verifying that the signature is valid for the specific message.
Ensuring that the signer’s address is a DID of a device registered in ioID for the targeted project.
Dropping the message if these conditions are not met.

Alternatively, we could remove the requirement for a signature in the demo API node to reduce unneeded friction for users.
cc @guo

supported already


Tool name

We need to think about a new name because WCFlow is too toilets oriented :smile: (no go from the hierarchy!) ... I have a few things in mind.

I thought about a character of the Aïda opera. The easiest to pronounce is "Radames".
Because it's a layer on top of AiiDA, we could use "Pacha", because the opera was ordered by Ismaïl Pacha, the Egypt Pacha at the time.

I'm currently leaning towards "Pacha"
For the command line, we could use verdi subcomands: verdi reherse for generating the preview and verdi orchestrate  for launching the workflow.

I think ethiopia is too close to the country name that everyone will mispell it when importing.

What do you mean by too close? It's just the country name.

With @agoscinski on this topic, also liked PACHA. CFLOW and CLIFF are also taken😅 https://pypi.org/project/cflow/
https://pypi.org/project/cliff/
CWFLOW as available, though.

As @DropD mentionned, I'd be fine not pretending it's an Acronym but I still like

the integration in the AiiDA story
that it starts with ETH
We could even spell it ETHiopiiA to reflect these points.

@agoscinski @GeigerJ2 @DropD
Would you be fine to rename the tool to ETHiopiiA once for all? I'd mention the "acronym" in a sentence like "if you really like acronyms, could stand for ... "

I will highly dislike typing it as command line tool and as python import. I think the writing is also not so clear from the pronunciation so many people will mistype it from hearing the name. How it is derived from the name looks a bit ridiculous, but this we never have to expose to the public. I am much more a fan of something shorter, simpler like ethope, athope, etope, atope (a bit like biotope).

And if you don't like my shorter suggestion here some chatgpt suggetions which don't sound bad

Zephyros – Named after the Greek god of the west wind, symbolizing the dynamic nature of weather and climate processes.
StratoFlow – Inspired by the stratosphere, evoking layers of atmosphere and data flow.
NimbusCore – "Nimbus" refers to clouds, suggesting weather, while "Core" implies a solid, central processing engine.
Tempestia – Suggests powerful, dynamic weather systems (tempests), alongside seamless orchestration.
HorizonLoop – Implies the broad view of climate processes, with the "loop" referencing automated workflows.
CirrusEngine – Named after high-altitude clouds, signaling light, agile workflows for atmospheric modeling.
Fluxterra – Combining "flux" (the flow of data) with "terra" (Earth), highlighting the planetary and dynamic nature of the project.
AerisForge – "Aeris" means air, and "Forge" suggests the crafting or creation of workflows.
CycloneOps – Evokes powerful natural systems like cyclones while referencing the operational and automated nature of the workflows.
SolsticeFlow – "Solstice" marks significant points in the Earth's climate, symbolizing change and cycles, tied with seamless workflow handling.

and abbreviated

Zephyr
Strato
Nimbus
Tempest
Horizon
Cirrus
Flux
Aeris
Cyclo
Solis

Sure we can do a 0.0.0-dev release. Just wait @DropD response

There's even an easy logo, which is the name in egyptian Arabic: خمسين

Sirocco is now on pypi.


Remove discord.js

That library is now rewriting with Typescript.
I will edit it Under developing

That library is now rewriting with Typescript.
I will edit it Under developing

That library is now rewriting with Typescript.
I will edit it Under developing

Okay

That library is now rewriting with Typescript.
I will edit it Under developing

Okay


wasm-pack test --headless --chrome fails in docker container

🐛 Bug description
While running wasm-pack-test --headless --chrome in an docker container the test fails with following error:
[2023-12-29T14:15:05Z DEBUG wasm_bindgen_test_runner::headless] POST /session {"desiredCapabilities":{"goog:chromeOptions":{"args":["--whitelisted-ips=","--port=41795","--verbose","headless","disable-dev-shm-usage","no-sandbox"]}},"requiredCapabilities":{}}
[2023-12-29T14:15:05Z DEBUG wasm_bindgen_test_runner::headless] got: {"sessionId":"7ab4c03796d4d4a3120bbc76daeac47e","status":13,"value":{"message":"unknown error: cannot find Chrome binary\n  (Driver info: chromedriver=114.0.5735.90 (386bc09e8f4f2e025eddae123f36f6263096ae49-refs/branch-heads/5735@{#1052}),platform=Linux <IP_ADDRESS>-microsoft-standard-WSL2 x86_64)"}}

using the wasm-pack version 0.12.1.
The non --headless version works.

Full log (`RUST_LOG=wasm_bindgen_test_runner wasm-pack test --chrome --headless`)
[INFO]: 🎯  Checking for the Wasm target...
warning: function `set_panic_hook` is never used
 --> src/utils.rs:1:8
  |
1 | pub fn set_panic_hook() {
  |        ^^^^^^^^^^^^^^
  |
  = note: `#[warn(dead_code)]` on by default

warning: `wasm` (lib) generated 1 warning
warning: `wasm` (lib test) generated 1 warning (1 duplicate)
    Finished dev [unoptimized + debuginfo] target(s) in 0.01s
[INFO]: ⬇  Installing wasm-bindgen...
warning: function `set_panic_hook` is never used
 --> src/utils.rs:1:8
  |
1 | pub fn set_panic_hook() {
  |        ^^^^^^^^^^^^^^
  |
  = note: `#[warn(dead_code)]` on by default

warning: `wasm` (lib) generated 1 warning
warning: `wasm` (lib test) generated 1 warning (1 duplicate)
    Finished test [unoptimized + debuginfo] target(s) in 0.01s
     Running unittests src/lib.rs (target/wasm32-unknown-unknown/debug/deps/wasm-305b5e1823605350.wasm)
no tests to run!
     Running tests/web.rs (target/wasm32-unknown-unknown/debug/deps/web-7841cbe865bd89c1.wasm)
Set timeout to 20 seconds...
[2023-12-29T14:15:05Z DEBUG wasm_bindgen_test_runner::headless] executing "/home/node/.cache/.wasm-pack/chromedriver-365490088b2eefa3/chromedriver" "--port=43979"
Running headless tests in Chrome on `http://<IP_ADDRESS>:43979/`
Try find `webdriver.json` for configure browser's capabilities:
Ok
[2023-12-29T14:15:05Z DEBUG wasm_bindgen_test_runner::headless] POST /session {"desiredCapabilities":{"goog:chromeOptions":{"args":["--whitelisted-ips=","--port=41795","--verbose","headless","disable-dev-shm-usage","no-sandbox"]}},"requiredCapabilities":{}}
[2023-12-29T14:15:05Z DEBUG wasm_bindgen_test_runner::headless] got: {"sessionId":"7ab4c03796d4d4a3120bbc76daeac47e","status":13,"value":{"message":"unknown error: cannot find Chrome binary\n  (Driver info: chromedriver=114.0.5735.90 (386bc09e8f4f2e025eddae123f36f6263096ae49-refs/branch-heads/5735@{#1052}),platform=Linux <IP_ADDRESS>-microsoft-standard-WSL2 x86_64)"}}
[2023-12-29T14:15:05Z DEBUG wasm_bindgen_test_runner::headless] POST /session/7ab4c03796d4d4a3120bbc76daeac47e/url {"url":"http://<IP_ADDRESS>:43947"}
[2023-12-29T14:15:05Z DEBUG wasm_bindgen_test_runner::headless] DELETE /session/7ab4c03796d4d4a3120bbc76daeac47e/window
[2023-12-29T14:15:05Z WARN  wasm_bindgen_test_runner::headless] failed to close window http://<IP_ADDRESS>:43979/session/7ab4c03796d4d4a3120bbc76daeac47e/window: status code 404
driver status: signal: 9 (SIGKILL)
driver stdout:
    Starting ChromeDriver 114.0.5735.90 (386bc09e8f4f2e025eddae123f36f6263096ae49-refs/branch-heads/5735@{#1052}) on port 43979
    Only local connections are allowed.
    Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
    ChromeDriver was started successfully.

driver stderr:
    [1703859305.789][SEVERE]: bind() failed: Cannot assign requested address (99)

Error: http://<IP_ADDRESS>:43979/session/7ab4c03796d4d4a3120bbc76daeac47e/url: status code 404
error: test failed, to rerun pass `--test web`

Caused by:
  process didn't exit successfully: `/home/node/.cache/.wasm-pack/wasm-bindgen-b04961754c8ad633/wasm-bindgen-test-runner /workspaces/gcc-output-map-web-renderer/src/wasm/target/wasm32-unknown-unknown/debug/deps/web-7841cbe865bd89c1.wasm` (exit status: 1)
note: test exited abnormally; to see the full output pass --nocapture to the harness.
Error: Running Wasm tests with wasm-bindgen-test failed
Caused by: Running Wasm tests with wasm-bindgen-test failed
Caused by: failed to execute `cargo test`: exited with exit status: 1
  full command: cd "/workspaces/gcc-output-map-web-renderer/src/wasm" && CARGO_TARGET_WASM32_UNKNOWN_UNKNOWN_RUNNER="/home/node/.cache/.wasm-pack/wasm-bindgen-b04961754c8ad633/wasm-bindgen-test-runner" CHROMEDRIVER="/home/node/.cache/.wasm-pack/chromedriver-365490088b2eefa3/chromedriver" WASM_BINDGEN_TEST_ONLY_WEB="1" "cargo" "test" "--target" "wasm32-unknown-unknown"

🤔 Expected Behavior
The test should succeed as they do with the non --headless version.
👟 Steps to reproduce

alternatively build with with Dockerfile

Dockerfile
ARG VARIANT="16"
ARG RUSTUP_VERSION="1.26.0"
FROM node:${VARIANT}

ARG RUSTUP_VERSION
ENV RUSTUP_VERSION $RUSTUP_VERSION

RUN apt-get update \
      && apt-get upgrade -y \
      && apt-get install -y \
      vim

USER node

RUN curl -L --proto '=https' --tlsv1.2 --output /tmp/rustup-init \
      "https://static.rust-lang.org/rustup/archive/${RUSTUP_VERSION}/x86_64-unknown-linux-gnu/rustup-init" \
      && chmod +x /tmp/rustup-init \
      && /tmp/rustup-init -y \
      && rm /tmp/rustup-init

RUN /home/node/.cargo/bin/cargo install \
      wasm-pack

Start docker container docker run --rm -it node:16 bash

Setup environment

# install deps
apt update
apt install -y libnss3

# install rust
curl -L --proto '=https' --tlsv1.2 --output /tmp/rustup-init \
      "https://static.rust-lang.org/rustup/archive/1.26.0/x86_64-unknown-linux-gnu/rustup-init" \
      && chmod +x /tmp/rustup-init \
      && /tmp/rustup-init -y \
      && rm /tmp/rustup-init
source "$HOME/.cargo/env"
export USER=root

# install wasm-pack
cargo install wasm-pack

# follow quickstart
cd /tmp && wasm-pack new hello-wasm
cd /tmp/hello-wasm
wasm-pack build

Run test (which fails as indicated)

wasm-pack test --headless --chrome

🌍 Your environment
wasm-pack version: 0.12.1
rustc version: 1.75.0 (82e1608df 2023-12-21)

Docker (Debian 10 - buster)
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Docker Host (WSL)
$ uname -a
Linux DESKTOP-P63NNCI <IP_ADDRESS>-microsoft-standard-WSL2 #1 SMP Thu Oct 5 21:02:42 UTC 2023 x86_64 Linux
$ cat /etc/*release
3.18.2
NAME="Rancher Desktop WSL Distro"
ID="rancher-desktop-wsl-distro"
PRETTY_NAME="Rancher Desktop WSL Distribution"
VERSION_ID="0.42"
BUILD_ID="964afb744b08a220ffd06e66e83e38c8fa8b7372"
HOME_URL="https://rancherdesktop.io/"
SUPPORT_URL="https://rancher-users.slack.com/channels/rancher-desktop"
BUG_REPORT_URL="https://github.com/rancher-sandbox/rancher-desktop-wsl-distro/issues/new"

Findings

This error seems to be related to chromedriver beeing started without --whitelisted-ips=.
I do not know on how to pass arguments to the chrome driver to verify this.

~The firefox headless fails aswell, thought with a SIGKILL~ Expected behavior
driver status: signal: 9 (SIGKILL)
driver stdout:
<PHONE_NUMBER>482       geckodriver     INFO    Listening on <IP_ADDRESS>:36377

Seems to be related to #1126

Installing the correct googledriver and chrome version from google chrome labs will fix this. I will leave this issue open, as I believe two things would improve user friendliness:

Add a hint or some additional documentation that the browser needs to be installed (https://rustwasm.github.io/docs/wasm-pack/commands/test.html).
Maybe a friendly error message to indicate the browser is not installed.

Otherwise seems to work as expected.
Thank you for the team here for the work ❤

Updated the Dockerfile to install the correct chromedriver and chrome version, which then allows running: wasm-pack test --chrome --chromedriver "$(which chromedriver)" --headless.


Post immediate completions through the I/O executor

As per https://cppalliance.org/boost-release/2022/11/16/KlemensBoost181.html immediate completions should post through the I/O executor, then dispatch to the token's executor. We currently post to the token's executor.

With Boost 1.82, that should be dispatch(get_associated_immediate_executor(h), std::move(self))


unknown packet ID(18)

So we have new packet ID 18.
http://agar.gcommer.com/index.php?title=Protocol#Reset_all_.28opcode_18.29 says that packet resets the known cells like ID 20.. but in main_out.js there is 2 more parameters for reset.
case 18:                 E = [];                 q = [];                 K = {};                 A = [];                 break;             case 20:                 q = [];                 E = [];                 break;

why have you closed this issue?

Ball destroy reason server-forced added.


Setup K8s infrastructure for Helm e2e tests

Part of the #27
This PR runs Helm install in CI as a basic check to verify if chart can be deployed successfully on a real cluster.
Uses KinD, - Kubernetes in Docker which is lightweight way to setup K8s cluster for a quick CI/testing purposes. See:

https://github.com/kubernetes-sigs/kind
https://kind.sigs.k8s.io/

Test which one is more KinD-stable?

[x] CircleCI (https://circleci.com/gh/StackStorm/stackstorm-ha/458)
[x] TravisCI (https://travis-ci.org/StackStorm/stackstorm-ha/jobs/537943346)

Alright, Helm chart e2e CI test blueprint works in both CircleCI and TravisCI with K8s deployed by KinD.
Deployment within KinD is not happy about persistent volumes coming from the official MongoDB-HA Helm chart and so I had to disable persistence.
I also tried TravisCI to verify if it's something KinD environment specific or CI platform related. Travis has similar problems or workarounds comparing to CircleCI so we'll stick with Circle as initially chosen CI for other tasks.
Overall it's great that we can run quick Helm e2e tests in something like CircleCI instead of spinning real K8s cluster in cloud.

Good for now, I'll continue adding Helm e2e tests in another PR


feat(k8s): add support for update of Ingress status

Codecov Report

Merging #16 into master will decrease coverage by 0.51%.
The diff coverage is 53.33%.

@@            Coverage Diff             @@
##           master      #16      +/-   ##
==========================================
- Coverage   50.19%   49.68%   -0.52%
==========================================
  Files          27       27
  Lines        1753     1753
==========================================
- Hits          880      871       -9
- Misses        762      771       +9
  Partials      111      111

Impacted Files
Coverage Δ

cli/ingress-controller/flags.go
83.52% <ø> (-0.75%)
:arrow_down:

cli/ingress-controller/main.go
21.25% <0%> (-0.14%)
:arrow_down:

internal/k8s/main.go
88.09% <100%> (+0.29%)
:arrow_up:

internal/ingress/status/status.go
70.22% <68.18%> (-4.21%)
:arrow_down:

Continue to review full report at Codecov.

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


Fix README Typo

Tiny PR but just saw something and had 2 minutes to fix it.

Fixes a typo in the README file

Checklist:

[X] Documentation
[x] Tests N/a
[X] Ready to be merged

Deploy preview for govuk-react processing.
Building with commit 650fa927fcfa844f1634f0e53d1f18ef628626a8
https://app.netlify.com/sites/govuk-react/deploys/5dc4290fe98920000817e1fb

I can’t remember why I didn’t merge this sorry. If you reopen I will merge


Minor Fixing Compile Error on vs2012 express

Thanks For This Great Library . There Were One Build Error Using vs2012 express compiler that it can't initialize class members outside of constructor.  Minor Fix in  "struct Context" in imgui's gizmo.inl.
.

You're changing 3rdparty software, you should send PR to original author:
https://github.com/CedricGuillemet/ImGuizmo
I'll accept PR, but it will be overwritten next time whan I integrate, so make sure you send PR to original repository.

Done

👍


[Bug] Invalid file label overflows if many file extensions are supported

Is there an existing issue for this?

[X] I have searched the existing issues

Have you updated FilePond and its plugins?

[X] I have updated FilePond and its plugins

Describe the bug
We have an input with a lot of allowed file types:
accept="application/vnd.openxmlformats-officedocument.presentationml.presentation,application/pdf,application/vnd.openxmlformats-officedocument.spreadsheetml.sheet,application/vnd.openxmlformats-officedocument.wordprocessingml.document,application/msword,application/vnd.ms-excel,application/vnd.ms-powerpoint,application/vnd.oasis.opendocument.spreadsheet,application/vnd.oasis.opendocument.text,application/x-7z-compressed,application/gzip,application/vnd.rar,application/zip,image/bmp,image/gif,image/jpeg,image/png,image/tiff,text/csv,text/plain,application/rtf,video/mp4,video/3gpp,video/quicktime,video/x-msvideo,video/x-ms-wmv"

We use the FilePondPluginFileValidateType plugin to validate the selected document type. However, when the list of supported extensions grows too large, it overflows the item:

We can overwrite the label with a shorter error message, but there's not enough space to actually display a list of supported file types. This could be addressed by, for example, allowing the text to wrap and the item to grow vertically with the error message. Or at least to hide the overflowing content with text-overflow: ellipsis.
Reproduction
Create an input that allows a large number of file formats (see above). Create a FilePond instance with the FilePondPluginFileValidateType plugin. Drag and drop a file type that is not supported onto the FilePond instance.
Environment
- Device: Mac Mini
- OS: macOS 13.4
- Browser: Firefox Developer Edition

I'll resolve the text wrapping in FilePond v5

@rikschennink Thanks! Yeah, I've overwritten the long label with that property. Though it will be nice to be able to use longer labels, and the default value shouldn't cause layout issues.


Add status bar to show session information

The status bar should contain number of torrents in the session, total DL/UL rate, etc.

The status bar will be an good feature. Optionally, the download/upload rate may also be shown in title bar (Settings- Show download/upload rate in title bar).


Styling improvements for [sectionId] pages

Fixed text overflowing prev/next buttons - #177
Style improvements for learning outcomes as per #229

tailwind colours

Hey, great work 👍 , I have two minor changes regarding the coloring of elements and one thing that we will leave for another issue (the movement due to border size changes.
Other than that, should be good to go.

Hey, great work 👍 , I have two minor changes regarding the coloring of elements and one thing that we will leave for another issue (the movement due to border size changes.
Other than that, should be good to go.

Hey, great work 👍 , I have two minor changes regarding the coloring of elements and one thing that we will leave for another issue (the movement due to border size changes.
Other than that, should be good to go.

Thanks for this! I've committed those changes. Yeah border behaviour definitely not ideal - I'll have a look at the border movement.


Increase backgill resources and adding logs

Increase resources for cache_maintenance job - backfill action.
Adding logs each 100 datasets in backfill

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Codecov Report
Patch coverage: 97.14% and project coverage change: +9.37 :tada:

Comparison is base (3e100ad) 87.77% compared to head (5742c19) 97.14%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1031      +/-   ##
==========================================
+ Coverage   87.77%   97.14%   +9.37%
==========================================
  Files          94        4      -90
  Lines        4146       70    -4076
==========================================
- Hits         3639       68    -3571
+ Misses        507        2     -505

Flag
Coverage Δ

jobs_cache_maintenance
97.14% <97.14%> (?)

jobs_cache_refresh
?

jobs_mongodb_migration
?

libs_libcommon
?

services_admin
?

services_api
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ache_maintenance/src/cache_maintenance/backfill.py
94.44% <94.44%> (ø)

jobs/cache_maintenance/tests/conftest.py
95.45% <95.45%> (ø)

.../cache_maintenance/src/cache_maintenance/config.py
100.00% <100.00%> (ø)

...obs/cache_maintenance/tests/test_backfill_cache.py
100.00% <100.00%> (ø)

... and 93 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Laravel 8.61.0 Shift

This pull request includes updates for the recent minor version release of Laravel as well as updates to your package dependencies. Feel free to commit any additional changes to the shift-ci-v8.61.0 branch.
Before merging, you need to:

Checkout the shift-ci-v8.61.0 branch
Review all pull request comments for additional changes
Run composer update
Test your application (no tests?)

:warning: The Shift build servers run PHP 8. If you are still running PHP 7.4 or lower you should run composer update locally to ensure you have the proper versions of your dependencies to reflect your PHP 7 environment.


Support for private comments

PR Checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Other... Please describe:

What is the current behavior?
Issue Number: #84
What is the new behavior?
Comments now support a "private" state.
By default, private comments:

Are displayed with an eye-closed icon (see https://code.visualstudio.com/api/references/icons-in-labels#icon-listing). This icon can be changed with the setting code-review.privateCommentIcon.
Are not exported. The export can be forced with the setting code-review.reportWithPrivateComments.

Does this PR introduce a breaking change?

[x] Yes
[ ] No

The extension now depends on VSCode v1.52 in order to use ThemeColor in TreeItem (see https://code.visualstudio.com/updates/v1_51#_codicon-colors-in-trees).
Other information

I will release it later on today


Plots plugin

Plots plugin still not loading. I used the poggit build and the one this repo.

Confirmed.  It needs that part for here.
2017-06-05 [12:59:46] [Server thread/INFO]: Enabling MyPlot v1.1.4
2017-06-05 [12:59:46] [Server thread/CRITICAL]: ErrorException: "Missing argument 2 for MyPlot\spoondetector\SpoonDetector::printSpoon(), called in phar://C:/Users/Aericio/Desktop/Minecraft PE/plugins/MyPlot.phar/src/MyPlot/MyPlot.php on line 451 and defined" (EXCEPTION) in "/MyPlot.phar/src/MyPlot/spoondetector/SpoonDetector" at line 46
2017-06-05 [12:59:46] [Server thread/INFO]: Disabling MyPlot v1.1.4
2017-06-05 [12:59:46] [Server thread/INFO]: Enabling MyPlot v1.1.4
2017-06-05 [12:59:46] [Server thread/CRITICAL]: ErrorException: "Missing argument 2 for MyPlot\spoondetector\SpoonDetector::printSpoon(), called in phar://C:/Users/Aericio/Desktop/Minecraft PE/plugins/MyPlot.phar/src/MyPlot/MyPlot.php on line 451 and defined" (EXCEPTION) in "/MyPlot.phar/src/MyPlot/spoondetector/SpoonDetector" at line 46
2017-06-05 [12:59:46] [Server thread/INFO]: Disabling MyPlot v1.1.4

Tested locally, added , spoon.txt to line 451 and it ran fine.
2017-06-05 [13:10:30] [Server thread/INFO]: Preparing level "world"
2017-06-05 [13:10:30] [Server thread/INFO]: Starting GS4 status listener
2017-06-05 [13:10:30] [Server thread/INFO]: Setting query port to 19132
2017-06-05 [13:10:30] [Server thread/INFO]: Query running on <IP_ADDRESS>:19132
2017-06-05 [13:10:30] [Server thread/INFO]: Default game type: Survival Mode
2017-06-05 [13:10:30] [Server thread/INFO]: Done (1.282s)! For help, type "help" or "?"
2017-06-05 [13:11:00] [Server thread/INFO]: Loading pocketmine.yml...
2017-06-05 [13:11:00] [Server thread/INFO]: Loading server properties...
2017-06-05 [13:11:00] [Server thread/INFO]: Selected English (eng) as the base language
2017-06-05 [13:11:00] [Server thread/INFO]: Starting Minecraft: PE server version v<IP_ADDRESS>
2017-06-05 [13:11:00] [Server thread/INFO]: Opening server on <IP_ADDRESS>:19132
2017-06-05 [13:11:01] [Server thread/INFO]: This server is running PocketMine-MP version 1.6.2dev "Unleashed" (API 3.0.0-ALPHA5)
2017-06-05 [13:11:01] [Server thread/INFO]: PocketMine-MP is distributed under the LGPL License
2017-06-05 [13:11:01] [Server thread/INFO]: Loading recipes...
2017-06-05 [13:11:01] [Server thread/INFO]: Loading resource packs...
2017-06-05 [13:11:01] [Server thread/INFO]: Loading DevTools v1.11.2
2017-06-05 [13:11:01] [Server thread/INFO]: Enabling DevTools v1.11.2
2017-06-05 [13:11:01] [Server thread/INFO]: Loading source plugin MyPlot v1.1.4
2017-06-05 [13:11:01] [Server thread/INFO]: [DevTools] Registered folder plugin loader
2017-06-05 [13:11:01] [Server thread/INFO]: Enabling MyPlot v1.1.4
2017-06-05 [13:11:01] [Server thread/NOTICE]: [MyPlot] Loading...
2017-06-05 [13:11:01] [Server thread/NOTICE]: [MyPlot] Enabled!
2017-06-05 [13:11:02] [Server thread/INFO]: Preparing level "world"
2017-06-05 [13:11:02] [Server thread/INFO]: Starting GS4 status listener
2017-06-05 [13:11:02] [Server thread/INFO]: Setting query port to 19132
2017-06-05 [13:11:02] [Server thread/INFO]: Query running on <IP_ADDRESS>:19132
2017-06-05 [13:11:02] [Server thread/INFO]: Default game type: Survival Mode
2017-06-05 [13:11:02] [Server thread/INFO]: Done (1.743s)! For help, type "help" or "?"

Okay. I'll add it back.

[12:18:58] [Server thread/CRITICAL]: ClassNotFoundException: "Class spoondetector\SpoonDetector not found" (EXCEPTION) in "/src/spl/BaseClassLoader" at line 144
I am getting the same error.

@alexbgameson download from poggit.


integration3: rates suddenly slowing down

Initially sensors and attitude_estimator_q run with 250 Hz as the MPU publishes at, however, after a seemingly random time, everything slows down and the uorb calls (or polls) seem to end in timeouts.
To debug use the branch https://github.com/PX4/Firmware/tree/integration3_ratedebug.
When it's running fine at the beginning, it should say:
[08500/00]  32:08.397  HAP:33:pub sensor combined, interval: 3990  2241  sensors.cpp

Then after a while:
[08500/00]  34:10.061  HAP:33:pub sensor combined, interval: 181481  2241  sensors.cpp

My most recent finding is that the measure call from DevObj stop, and thus we get timeouts because the sensors are not publishing anymore.

How can I best reproduce this?

@mcharleb The usual
(cd /home/linaro && ./mainapp path/to/mainapp.config); exit

@mcharleb I continued debugging the timeout issue.
Firstly, I think we should be using CLOCK_MONOTONIC in the schedule because CLOCK_REALTIME can skew which is probably not what we want, right?
Can you make sure pthread_cond_timedwait() uses also CLOCK_MONOTONIC internally?
https://github.com/PX4/DriverFramework/commit/ae0c88bee59830bc7896b3c2fdcfd6833ec127af
Also, I found that pthread_cond_timedwait would hang if the time was too small, e.g. < 100 us.
The workaround for now is to do a work item immediately when it's less than 100 us away.
Can you please inspect pthread_cond_timedwait() and see what could be going wrong here?
https://github.com/PX4/DriverFramework/commit/d1b963adef91991fa8b314b307a1651afb8b5a88
The state after the above two fixes was that sensors would run at a constant 4000 us interval (so at the 250 Hz that the gyro driver publishes.
However, the attitude_estimator_q would have intervals around 5000 to 8000 us every now and then (at around 1Hz).
I discovered that the open(mavlink_fd, ...) call raised a couple of px4_ioctl somehow and slowed down the attitude_estimator_q loop down.
I've disabled the open call for now and it lets the attitude_estimator_q run at 250 Hz like sensors.
https://github.com/PX4/Firmware/commit/d82ed390bc45ea6fa463dde730105962d5fd9cd6
Unfortunately, after these changes, there is still trouble, however it's harder to reproduce.
I ran the setup for a longer period of time and saw that both sensors and attitude_estimator_q got timeouts after some time (in one case 18minutes after starting).
From what I can see is that the callback in DriverFramework.cpp is not called anymore.
I'm digging into this later but it would be helpful if somebody could look at it in parallel.
A debug branch with printfs is pushed to integration3_ratedebug2.

FYI @liamstask

@jywilson FYI

The timeouts I am seeing are definitely still relating to pthread_cond_timedwait() getting called with an abstime too close. The current workaround of scheduling work closer than 100 us rightaway, gets us to a state where the DriverFramework runs fine for about 30mins but might still suddenly crash at some point. This happens presumably through timing jitter because the sensor read happens after getting the current time. I am going to improve the workaround by checking the time again just before calling pthread_cond_timedwait().
I think pthread_cond_timedwait() needs to be fixed internally. If the timeout time has already been reached, it needs to return straightaway instead of block indefinitely.
@mcharleb, @jywilson please comment on this.
Also, I've once been getting a DSP reset saying:
[72536.749505] ADSP subsystem failure reason: SFR Init: wdog or kernel error suspected.

To reproduce this, use the branch integration3_ratedebug2 and let it run for a long time until you see sensors and attitude_estimator_q complaining about long timeouts.
If you don't want to wait too long, play with the MIN_RESCHEDULE_TIME_US define. The lower it's chosen, the more often I expect timeouts.

I've added a 2nd workaround which makes sure that pthread_cond_timedwait() is never called with a timeout closer than 100us in the future.
Still, after some time, we always get the case where pthread_cond_timedwait() just never returns. This happens even with a timeout far away (4000us) in the future.


Undefined function lightline#update

Starting up neovim with colorscheme gruvbox shows an error:
Error executing vim.schedule lua callback: Vim:E117: Unknown function: lightline#disable

I tried debugging this, but it has a super weird behavior. The error comes from this part:
  local has_lightline, _ = pcall(vim.fn["lightline#update"])
  if has_lightline then
    local ll_filled = vim.fn['lightline#colorscheme#fill'](lightline_theme)
    vim.g['lightline#colorscheme#gruvbox#palette'] = ll_filled
    vim.schedule(function()
      vim.fn['lightline#disable']()
      vim.fn['lightline#enable']()
    end)
  end

If I comment out the vim.schedule(…) call then I get no error. I also do not get the error if I manually invoke :colorscheme gruvbox after startup.
I do not have lightline installed and the lightline#update function is not defined after startup. But it seems like it is defined shortly between the code loading and the first scheduled callbacks executing.
Adding print calls does not help; it seems like this code is run twice where the first run is never actually logged.
I grepped all my installed plugins for lightline#update and this is the only match. I don't understand what could cause this, honestly. Perhaps vim.fn is in a weird state during startup…?
> nvim --version
NVIM v0.6.0-dev+390-g3beea1fe1

Fixed in https://github.com/ellisonleao/gruvbox.nvim/commit/d00787254c5417dda002c94028bdf6b0079bd3e9


NFAuth file not showing up

Netflix add-on version
lastest version
Operative systems used
Android
Kodi version used
Kodi 20 (Nexus)
Description of the bug
When trying to log in with authentication key, after putting the file in download and tried root, when choosing the option of logging in with auth key it does not find the file. only shows the folders but no nfauth file. but in a normal file explorer i find the file. do you know what i did wrong or if it is a bug`?
Steps to reproduce the behavior
No response
Debug log - mandatory
i do not think the log is neccessary
Possible fix
No response
Additional context
No response
Screenshots
No response

this is not addon bug
you have wrong android permissions set to your Kodi app that hide files


Add need reminders

We might end up switching to using sidekiq-cron to manage these workers
instead.
Implements https://github.com/OfficeMomsandDads/scheduler/issues/193

If this commit with sidekiq-cron looks good, then I can squash down these commits. I initialized the cron job in the remind_worker.rb file, not sure if that's the best way to do it or not. I also added a check to ensure a reminder won't be sent if a new shift was just recently created, because that would have notified them as well.

From our call with Sarah:
Needs are sometimes created multiple days in advance. With that in mind, we should send reminders once a day until the day of the need, at which point we can send them hourly (as it is defined now).

@benjaminwood Take a look at these recent commits and let me know what you think. There's separate logic now for sending both daily and hourly reminders. I added a couple specs for the daily ones.

@benjaminwood I know this has already been approved, but there were a few changes since then and I just want to make sure you feel good about merging it. If so I will.


unexpected error in running checks

Observed behaviour
running the following checks I get these errors:
(at the FB workshop at AtypI)

com.google.fonts/check/050 with (('font[3]', 'test/mada/Mada-Light.ttf'),)
Whitespace and non-breaking space have the same width?

ERROR: The condition FontBakeryCondition:missing_whitespace_chars had an error: AttributeError: 'TTFont' object has no attribute 'getBestCmap'
File "/root/fontbakery-n7s/Lib/fontbakery/checkrunner.py", line 413, in _evaluate_condition
return None, condition(**args)
Result: ERROR

com.google.fonts/check/050 with (('font[4]', 'test/mada/Mada-Medium.ttf'),)
Whitespace and non-breaking space have the same width?

ERROR: The condition FontBakeryCondition:missing_whitespace_chars had an error: AttributeError: 'TTFont' object has no attribute 'getBestCmap'
File "/root/fontbakery-n7s/Lib/fontbakery/checkrunner.py", line 413, in _evaluate_condition
return None, condition(**args)
Result: ERROR

com.google.fonts/check/050 with (('font[5]', 'test/mada/Mada-Regular.ttf'),)
Whitespace and non-breaking space have the same width?

ERROR: The condition FontBakeryCondition:missing_whitespace_chars had an error: AttributeError: 'TTFont' object has no attribute 'getBestCmap'
File "/root/fontbakery-n7s/Lib/fontbakery/checkrunner.py", line 413, in _evaluate_condition
return None, condition(**args)
Result: ERROR

com.google.fonts/check/050 with (('font[6]', 'test/mada/Mada-SemiBold.ttf'),)
Whitespace and non-breaking space have the same width?

ERROR: The condition FontBakeryCondition:missing_whitespace_chars had an error: AttributeError: 'TTFont' object has no attribute 'getBestCmap'
File "/root/fontbakery-n7s/Lib/fontbakery/checkrunner.py", line 413, in _evaluate_condition
return None, condition(**args)

Expected behaviour
Resources and exact process needed to replicate
running against master on the test/mada font in the fontbakery repository. fonttools is installed but apparently there is an issue with fonttools integration. (running in a lxc test vm).
Thanks !

fontTools CHANGELOG at https://pypi.org/project/FontTools/ states:
3.19.0 (released 2017-11-06)
[ttLib] Added getBestCmap() convenience method to TTFont class
 and cmap table class that returns a preferred Unicode cmap
 subtable given a list of options (#1092).

@n7s, maybe for some reason you are using an older version of fontTools?
Installing Font Bakery should have caused a pretty recent version of fontTools to be installed automatically as well, so that is a bit weird.
Nicolas, could you please let me know which version of fontTools you have?

well... maybe this is the problem:
https://github.com/googlefonts/fontbakery/blob/master/requirements.txt#L1
This should definitely be >=3.19!

ok. I have just updated the requirements.txt file to address the issue.
Please consider fetching the latest code from git master and then re-running pip install -r requirements.txt

OK. I have just verified this on @n7s 's laptop here during the FontBakery workshop at Atypi 2018. It is now fixed :-)


[Issue] Manifest generation error

Hi all
I follow the instruction .
When i deploy a simply like below
kind: Secret
apiVersion: v1
metadata:
  name: example-secret
  annotations:
    avp_path: "path/to/mysecret"
type: Opaque
stringData:
  mykey_invault: <mykey_invault>

Argo side appear error shows..
rpc error: code = Unknown desc = Manifest generation error (cached): argocd-vault-plugin generate ./ failed exit status 1: Error: Must provide a supported Vault Type Usage: argocd-vault-plugin generate  [flags] Flags: -c, --config-path string path to a file containing Vault configuration (YAML, JSON, envfile) to use -h, --help help for generate -s, --secret-name string name of a Kubernetes Secret containing Vault configuration data in the argocd namespace of your ArgoCD host (Only available when used in ArgoCD) Must provide a supported Vault Type
What i am missing ? any hints?

Must provide a supported Vault Type Did you set a valid Vault type as an environment variable as documented here https://github.com/IBM/argocd-vault-plugin#backends?

My guess is that the secret is not being mounted on the repo-server pod. You can check that by execing into the pod and running printenv to see if AVP_TYPE is set

@gogovan-vincentngai What version are you running?

@gogovan-vincentngai What version are you running?

Argocd ? 2.0.0

Sorry, of the plugin

@werne2j  i am using this https://github.com/IBM/argocd-vault-plugin/releases/download/v0.7.0/argocd-vault-plugin_0.7.0_linux_amd64
After i inject all those AVP_xxxx env var direcrly
it is working expected
but seems the mount secret envfrom secret part is not work

@gogovan-vincentngai So sounds like there is no issue with the plugin then. Will close the issue.

Hi, I have the same issue:
Unable to create application: application spec is invalid: InvalidSpecError:
Unable to generate manifests in ira: rpc error: code = Unknown desc = argocd-vault-plugin generate ./
failed exit status 1: Error: Must provide a supported Vault Type Usage: argocd-vault-plugin generate  [flags] Flags:
-c, --config-path string path to a file containing Vault configuration (YAML, JSON, envfile) to use -h, --help help for
generate -s, --secret-name string name of a Kubernetes Secret containing Vault configuration data in the argocd namespace of your ArgoCD host (Only available when used in ArgoCD)
I ran the following manually on argocd-repo-server pod:
argocd@argocd-repo-server-6bc4999f9-7pt9x:~$ argocd-vault-plugin generate ./
Error: Must provide a supported Vault Type
Usage:
argocd-vault-plugin generate  [flags]
Flags:
-c, --config-path string   path to a file containing Vault configuration (YAML, JSON, envfile) to use
-h, --help                 help for generate
-s, --secret-name string   name of a Kubernetes Secret containing Vault configuration data in the argocd namespace of your ArgoCD host (Only available when used in ArgoCD)
I have AVP_TYPE and all other required env on the repo-server pod:
argocd@argocd-repo-server-6bc4999f9-7pt9x:~$ printenv | grep AVP
AVP_SECRET_ID=c4..
AVP_TYPE=vault
AVP_AUTH_TYPE=approle
AVP_ROLE_ID=73..

Oh My God, it missed the double quotes.

@ira-gordin-sap Hi, what was your error? I got the same error but I can exec argocd-vault-plugin generate ./ but the argocd UI throws this error Error: Must provide a supported Vault Type Usage.
I'm using environment variables for the plugin configuration

@jhonsfran1165 My error was the following: "Must provide a supported Vault Type Usage".

@jhonsfran1165 same here, did you find a solution?

@yaochaoutokyo that error happens when the plugin does not get a valid AVP_TYPE. So make sure you are providing a type we support, and make sure that environment variable exists in the repo server or in a secret that Argo CD can read. If you have any new problems please create a new issue so we can better help.

Hi everybody,
I have followed the instruction on How to Use HashiCorp Vault and Argo CD for GitOps on OpenShift  and Solving ArgoCD Secret Management with the argocd-vault-plugint
The secret is:
kind: Secret apiVersion: v1 metadata:   name: argocd-vault-plugin-credentials   namespace: argocd type: Opaque stringData:     AVP_VAULT_ADDR: 'http://vault:8200'     AVP_VAULT_TOKEN: 'root'     AVP_TYPE: 'vault'     AVP_AUTH_TYPE: 'token'
Threre are all environment variables on argocd-repo-server, but I have the following error:
rpc error: code = Unknown desc = Manifest generation error (cached): argocd-vault-plugin generate ./ failed exit status 1: (0x1682740,0xc0004ec6b0)Error: ToYAML: could not convert replaced template into : error unmarshaling JSON: while decoding JSON: Object 'Kind' is missing in '{"resources":["example-secret.yaml"]}' Usage: argocd-vault-plugin generate <path> [flags] Flags: -c, --config-path string path to a file containing Vault configuration (YAML, JSON, envfile) to use -h, --help help for generate -s, --secret-name string name of a Kubernetes Secret containing Vault configuration data in the argocd namespace of your ArgoCD host (Only available when used in ArgoCD) ToYAML: could not convert replaced template into : error unmarshaling JSON: while decoding JSON: Object 'Kind' is missing in '{"resources":["example-secret.yaml"]}'
example-secret.yam is:
kind: Secret apiVersion: v1 metadata:   name: example-secret   annotations:     avp_path: "secret/data/vplugin/supersecret" type: Opaque stringData:   username: <username>   password: <password>
Can anyone help me?

I'm facing exact same issue as @dargentieri posted. Can anyone help?


Remove deprecated protobuf packages

What this PR does / why we need it:
Removes the following deprecated protobuf packages.

github.com/gogo/protobuf
github.com/golang/protobuf

Uses the recommended alternative google.golang.org/protobuf package.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Type of changes
Please delete options that are not relevant.

[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)
[ ] This change requires a documentation update

Feature/Issue validation/testing:
Please describe the tests that you ran to verify your changes and relevant result summary. Provide instructions so it can be reproduced.
Please also list any relevant details for your test configuration.

[ ] Test A

[ ] Test B

Logs

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Checklist:

[ ] Have you added unit/e2e tests that prove your fix is effective or that this feature works?
[ ] Has code been commented, particularly in hard-to-understand areas?
[ ] Have you made corresponding changes to the documentation?

Release note:

NONE

/lgtm
/approve


fix: remove event highlighting

Events, once marked as active, do not update to become inactive when they are done. I've updated the script to check again at the end of the event.
I've also added polling to check every 10 minutes to see if there is an active event.
I updated the active event animation in order to keep the event details legible. The previous opacity animation reduced readability during part of the animation. The animation I implemented is quite a departure from the previous one so if someone wan't to change this or suggest something subtler, please go ahead.

Deploying preview to https://xHain-hackspace-xhain-website-pr-54.surge.sh

Love it. Many thanks.

Seems broken now on mobile for me. No scroll to current day and I can not open the details of a event.

I tested, and checked again, and I don't have any issues. Are you coming tomorrow and can you show me?

Im not in Berlin today but here is a screen recording: https://github.com/xHain-hackspace/xhain-website/assets/45048474/1f6a6785-2066-4bfd-95d1-5eb469c511b4


revert back to qt

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Fixes https://github.com/conda-forge/qtwebkit-feedstock/issues/20

win-64 fails because mamba doesn't see the the latest qt build for that platform for some reason. I asked about it in https://github.com/conda-forge/qt-feedstock/pull/214#issuecomment-1031568440

There were problems with the latest qt build for win_64 as detailed in https://github.com/conda/infra/discussions/514 and https://github.com/conda-forge/qt-feedstock/pull/214#issuecomment-1031568440 so now we are stuck here too until someone can rebuild qt for windows.

@conda-forge-admin please rerender

https://github.com/conda/infra/discussions/514 was finally resolved, I think we should merge this in order to allow https://github.com/conda-forge/qgis-feedstock/pull/227 to proceed.

Thanks @izahn !


Cloudflare not accepting referral codes

{"result":null,"success":false,"errors":[{"code":1070,"message":"We are no longer accepting referral codes. Please continue to sign up with a free account."}],"messages":[]}\n

https://support.cloudflarewarp.com/hc/en-us/articles/360025588054-How-do-referrals-work

Note: Cloudflare will conclude the referral program for WARP+ on November 1, 2024. At that time, new referral codes will no longer be provided. When your device consumes existing referral allotment you will automatically migrate to the WARP free plan. You will not lose connectivity.

All key generators will stop working. :(


Flush the SDL_QUIT event when Cmd+W is detected in SDL_KEYDOWN as well

On macos 11.2.3 with sdl 2.0.14 the keyup handler for cmd+w was not enough. Maybe the quit event started to be triggered from the keydown handler? In any case, flushing the quit event there too helped.
Attempts to fix #238.

I guess this is a workaround to a problem of SDL2 but I am okay with this as it aligns with user expectations. Thank you.

Thank you!
Yes, it is weird that SDL2 connects cmd+w with quit by default. Maybe there is something in lite-xl that tells Mac that the application is a multi-window application, which handles closing independent windows by quit... Or it is just that a game has just one window and making a difference between cmd+w and cmd+q does not make sense ;-)


chore: ignore partial hit from coverage

Issue or need
After reviewing coverage, seems there's a partial hit. This is highly probable due to the issue of coverage reporting not being the same for unit tests and E2E tests.

Proposed changes
Ignore that for now

Quick reminders

🤝 I will follow Code of Conduct
✅ No existing pull request already does almost same changes
👁 Contributing docs are something I've taken a look at
📝 Commit messages convention has been followed
💬 TSDoc comments have been added or updated indicating API visibility if API surface has changed.
🧪 Tests have been added if needed. For instance, if adding new features or fixing a bug. Or removed if removing features.
⚙ API Report has been updated if API surface is altered.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#957  👈
#956
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @davidlj95 and the rest of your teammates on  Graphite


Automated test infrastructure

I think we need some kind of automated testing for Arachne for analysis zip files.
I would like to create zip files that should work when loaded into Arachne but I need a way to add them into an automated test process. Can we use githhub actions to run the "test" R projects I or others create?
Manual testing takes a lot of time and errors could be caught earlier with automated tests.
Are there ideas on how to do this?

@ttemnikova can you please share your ideas?


Update ui split pane

Fixes #155
Currently, Appointment in a split pane shows the details but is not in a sorted order.
We could consider displaying a sorted appointment list from earliest to latest
As of now, this is how the UI is shown

However, all fields need to be constraint to a reasonable length as this would prevent the tags from wrapping.
It follows the longest tag before wrapping, thus a bug can be induce by keying in a long text, and reducing the
UI screen size, which will make some of the tags overflow as shown in the image.

Superseded by #161


Indicate which projects have milestones due next

As an analyst
I want to see which projects have a milestone report due next quarter
So that I can plan capacity and prepare the milestone reports.
Description:
if needed
Acceptance Criteria:
Private Zenhub Image
Private Zenhub Image
Private Zenhub Image

[ ] Date comes from the latest SOW table (original, or from change request if exists)
[ ] use dates for milestones from Sow Tab 2. It is the next date out of all the dates.
[ ] If report for upcoming milestone is uploaded then remove message
[ ] If a date passes and no milestone report is uploaded for that due date, then it is marked as late. Icon is https://fontawesome.com/icons/triangle-exclamation?f=classic&s=solid colour D8292F
[ ] Show next milestone report due date even if they have missed the past milestone date

Implementation Details

Hey team! Please add your planning poker estimate with Zenhub @marcellmueller @rafasdc @VB-at-Bis

Please add your planning poker estimate with Zenhub @AntBush


Inspect if we need to delete empty constructors from annotation class or expect/actual mechanism

@OptIn(ExperimentalMultiplatform::class)
@OptionalExpectation
expect annotation class Entity()

@OptIn(ExperimentalMultiplatform::class)
@OptionalExpectation
expect annotation class Id()

For now, empty constructor should not be deleted.

Same for usual expected classes:
expect class Foo

actual class Foo
val foo = Foo()  // <-- error: expect class doesn't have a default constructor


Keypairs should not be backed up by default

I recently moved to a new device and was surprised to see my keypairs show up on the new device with no action taken on my part.  This means that keys were sent to google and only the key passphrase was protecting them. I consider this a security vulnerability.
Keypair backup should be disabled by default.  Users should be warned when enabling keypair backup that their keys are being disclosed and the potential for passphrase weaknesses.
Keypair backups are performed here:
https://github.com/connectbot/connectbot/blob/master/app/src/main/java/org/connectbot/service/BackupAgent.java#L47
	FileBackupHelper pubkeys = new FileBackupHelper(this, "../databases/" + PubkeyDatabase.DB_NAME);
	addHelper(PubkeyDatabase.DB_NAME, pubkeys);

Keep in mind this is only backing up the public keys. However, I could still see reasoning for wanting to avoid that.
@kruton for input.

Private keys live in this SQLlite DB as well.  See PubkeyDatabase class.  https://github.com/connectbot/connectbot/blob/master/app/src/main/java/org/connectbot/util/PubkeyDatabase.java

I encountered this same problem.  I was shocked to see my private keys on my new Android device realizing third parties, Google in this case, had access to my keys.
I agree with cruvolo where keys should not be backed up by default.

Thank you for addressing this.


Log unused JSON-RPC Request Fields

Description
As part of PR 2690 we allowed all fields in a JSON-RPC call that are not recognized to be ignored.  This was done to support other libraries that would occasionally send "extra" fields (like "type" in eth_estimateGas).  While this increases compatibility, there is a risk we may be unaware of properties that we may want in the future.
To help this, as a node operator I want unknown properties to be appeneded to the console (at info level), including what the field and value is and what type it was trying to be added to.  The particular call would be nice but may be hard to marshal.
One possible approach is to add @AnySetter methods in key places and logging the results.  (for context a stackoverflow question: https://stackoverflow.com/a/31164723/8020)
Acceptance Criteria
Calling any JSON-RPC with an unexpected field will result in the console log notifying me at INFO level.

@shemnon can i work on this issue?

sure


ui/update_dmonitoring: Improve readability of r_xyz matrix initialization

This PR introduces temporary variables to initialize the r_xyz matrix, enhancing readability and maintainability.

@ZwX1616 can you review? I think this is worth merging.


Polylines not displayed correctly at long zoom distance on iOS

I have seen this in my app which uses WKWebView and also with the default Materials example when loaded in iOS Safari.

Navigate to the default sandcastle example (https://sandcastle.cesium.com/?src=Materials.html) in Safari on iOS 13.5.1 or 13.4 (perhaps others).
From the "Polyline materials" selection, choose "Polyline Outline".
Observe that the polyline is just a large blocky red line. It is not a while line with red outline as it should be.
Select any of the other 2 polyline types.
Observe that the lines cannot be seen at all.
Re-select "Polyline Outline".
Zoom in tightly on the giant red polyline. At sufficient zoom you will notice that it does correctly render as white with red outline.
Switch to either of the other 2 choices and notice that you can now see the polyline at this tighter zoom. If you zoom out the line will disappear.

Sandcastle example: https://sandcastle.cesium.com/?src=Materials.html
Browser: iOS Safari
Operating System: iOS 13.4 and 13.5.1

Is this related to or the same as https://github.com/CesiumGS/cesium/issues/6735 @likangning93 ?

I should probably add that I am using 1.67 currently as it does not present this issue. One of my colleagues reported to me that it was the latest he found that still worked.

@sparsematrix that information helps a lot. If you're able to do a git bisect to determine exactly which commit caused this issue, that'd help narrowing it down. That's what I would do next.

Closing this issue as we have not heard from the original poster in a while and do not have sufficient information to move forward. Please feel free to re-open it to continue the discussion if necessary.

You have sufficient information. I apologize that I have a greater than full time job and have not yet had time to perform a binary search on commits and determine which one broke it. Your sandcastle example is literally broken. You should need no more information than that.

Re-opened as #9232

@sparsematrix  My apologies. I see that we have already confirmed that this is a bug. Re-opening issue to continue the discussion.

Here is the result of my git bisect testing:
c5ac4558cd4b740f26ad22c7531b5c5c5c1c62f2 is the first bad commit
commit c5ac4558cd4b740f26ad22c7531b5c5c5c1c62f2
Author: Kevin Ring<EMAIL_ADDRESS>Date:   Tue Mar 31 15:12:03 2020 +1100
Fix texture coordinates everywhere instead of in just the one place.

Source/Shaders/Materials/PolylineArrowMaterial.glsl |  1 -
Source/Shaders/PolylineFS.glsl                      | 10 ++++++----
Source/Shaders/PolylineVS.glsl                      |  4 +++-

Thanks for taking the time to look further into this @sparsematrix
@kring any ideas?

Not much @sparsematrix and @hpinkos. That commit was part of a major rework of polyline rendering with the log depth buffer, which fixed a bunch of problems. Since it seems to be working on other platforms (certainly various desktop platforms and on the Android devices I've tried), it could indicate an iOS bug, or it could indicate we're doing something dodgy that other platforms just happen to let us get away with. But nothing jumps out at me as far as the latter, and I don't have an iOS device to debug it on.
One thing to try: disable the logarithmic depth buffer and see if that helps. Here's a version of the Materials Sandcastle with log depth disabled.

Here's the PR that commit was part of:
https://github.com/CesiumGS/cesium/pull/8706

One thing to try: disable the logarithmic depth buffer and see if that helps. Here's a version of the Materials Sandcastle with log depth disabled.

@kring Thanks for taking a look. I've given that version a shot on an iPad and it shows the same issue as the regular Materials Sandcastle.

@kring not sure if any of this helps...
Here's how it looks in 1.67 in my app. To get this display there is a PolylineOutline drawn and then a PolylineArrow drawn along the same path to get the appearance of both outline and arrows. The line color is magenta and the outline is black:

Moving to commit d631c21, which is just before the breaking commit. The outline issue is not present but PolylineArrow no longer draws at all in iOS (still works in Chrome) regardless of zoom level:

Moving to the breaking commit c5ac455. When zoomed out I only see the outline color. Zooming in tight at this commit results in the correct appearance of both the outline and arrow (seemingly fixing the arrow issue seen in d631c21):

I have updated one of my iPads to the latest iOS (14.4.1) and confirmed that it is still an issue there with the Sandcastle example.

I have confirmed that this issue remains in iOS 14.5.1

Updated to iOS 15.4.1 and Cesium 1.92.
Here's my latest results in Safari/WKWebView:

Polyline Outline appears to work as expected now
Polyline Arrow does not display
Polyline Dash does not display (https://sandcastle.cesium.com/?src=Polyline Dash.html)

Remaining issues appear to be covered by https://github.com/CesiumGS/cesium/issues/9827 and setting orderIndependentTranslucency to false does appear to resolve the issue.


Release tags

Please consider using release tags, then people can get notified when a new release is ready and update in time.

Please subscribe to https://github.com/plausible/analytics

But I suppose the container often also has the needed updates? It's not just the application it ships, it ships a whole environment which needs to be maintained as well. That release is about 6 months old. Whatever is running in that container needs a rebuild from time to time, correct? That's why I was assuming some kind of container tag I could track. Then I know when to pull in the latest one.

We release every 6 months or so, with notes on how to upgrade etc. No need to follow anything else

What I mean is that the container is a Linux environment, it's not just the Plausible software, and just like any Linux environment you get regular security updates. It's not uncommon to rebuild containers every week or at least when there are security updates available (not just for the software you're packaging and distributing).


Add mixpanel to sponsors

Is your feature request related to a problem?
Need to add Mixpanel since they hosted 10/17 event in sf
Describe the solution you'd like
Mixpanel logo on event sponsor section
Describe alternatives you've considered
N/A
Additional context

Can I take this issue?

Yes its yours @ejbryant28

This was done!


Installation on Windows11

I created virtual environment on Win11 by conda to install polyply, all dependencies are satisfied, but polyply cound't be run.
While the same operation was used on Linux, it worked.
Did OS affect the installation?

In principle polyply is installable independent of the OS. However, for example number acceleration might not be available. Does the installation print any errors or what exactly fails when you run it on windows?

There is no error in installation.

when Running Polyply:
"Polyply 'is not an internal or external command, nor is it a executable program Or batch files".
By the way, same error encountered when installing martinize2 on Win11 (still worked on Linux)

My guess would be that it is not correctly exposed as executable, because the library is obviously installed and there. Perhaps @pckroon has an idea what is going on here, because he uses windows more often than I do.

It has to do with the PATH variable. See, e.g., also https://www.tutorialexample.com/a-simple-guide-to-add-conda-command-into-windows-path-environment-python-tutorial/

I think that's not the reason. Because my conda command could be used normally and the conda path in this tutorial was added successfully before.

Besides, I tried to execute these two programs directly in conda/Scripts folder, the error above still existed.

It is absolutely an issue with your PATH variable. Conda might be in your path, but martinize2/polyply (obviously) are not. I'm not sure the main entrypoints get installed in Scripts or somewhere else.

I fould when I run
python martinize2
or
python polyply
it run

Humm that is indeed interesting. If no one objects I will transfer the issue onto the discussion page, because to me this is less related to polyply installation than the individual setup of the conda environment on windows machines. But this could still be useful for others


Update build configuration to reflect KGP improvements

I did a bit of a cleanup of the build scripts.
Removed what wasn't necessary, centralized all dependencies in the root version catalog, and applied a more specific configuration to the JVM target.

Just as a note for potential improvement: I've seen you build and deploy using multiple runners.
You could simplify it by using only the MacOS host, which can build for all targets.

Once this PR is merged, I'll submit another one with a bit of code cleanup. No feature changes, just cleanup.
And after preparation PR, I'll port the algorithm variant.


sched/wdog: fix signature for wdentry_t

gcc 8.2.1. doesn't allow lazy function pointer casting anymore. When building
px4-firmware 'make omnibus_f4sd_default' it complains:
wdog/wd_start.c:151:20: error: cast between incompatible function types from 'wdentry_t'
Changing the signature for wdentry_t will break cdcacm_rxtimeout(). To fix
this we use a va_list there.
Related to https://github.com/PX4/Firmware/issues/12283

Thanks @bruenn, we try to stay in sync with the upstream NuttX project. Could you contribute this to upstream NuttX (https://bitbucket.org/nuttx/nuttx/src/master/) and then we'll either backport the commit or pick it up the next time we upgrade.

I send a bug report to upstream:
https://bitbucket.org/nuttx/nuttx/issues/159/sched-wdog-fix-signature-for-wdentry_t

I pushed a rebased version here: https://github.com/MaEtUgR/NuttX/tree/arm-gcc-9
To investigate further and get things running on ARM GCC 9 see https://github.com/PX4/Firmware/pull/13375

FYI when testing to compile on ARM GCC 9.2 with the latest NuttX version in use on master (https://github.com/PX4/NuttX/commit/fdf1837077104e80912a2c46ff159fdacc8b06f9) I don't see this problem popping up anymore. I'm assuming it was fixed in upstream NuttX and we merged it since.


Vim Support

Is your feature request related to a problem? Please describe.
I really enjoy learning on freeCodeCamp, but without vim keybindings, it really slows you down, and I know other people would appreciate vim mode in freeCodeCamp.org aswell.
Describe the solution you'd like
Add a setting into the platform, where users can turn on vim mode.
Describe alternatives you've considered
Alternatives - Using vim locally, then copying and pasting things over. This makes  it not worth it, as the duration of one level/challenge in a course is quite short.
Additional context
Think of it, there are so many developers that use freeCodeCamp, who primarily use Vim. I think the community would really appreciate this.

Our platform is specifically designed for new learners, which is why we've removed functionality such as Emmet or autocomplete.
Building in Vim keybinds would be contradictory to this, IMHO.

I guess it depends on what you mean by Vim mode.
If it is just the keybindings, having that be customizable would be a nice feature, but I'm not sure how realistic that is. There are already access to keyboard shortcuts like Shift + Alt + ↓ so remapping that wouldn't introduce anything new.
But I agree, it would be contradictory if it added anything beyond remapping existing keybindings.

I would have to agree with Naomi. When I was first learning how to use VIM, I accidentally got myself stuck in command mode and needed the teacher's help so I can actually write the shell script. It seems like a huge barrier to go through, and this is on top of campers learning how to code. I don't think this is a good idea at all.

Sure, if it got toggled by accident, that would be very confusing. But I'm sure someone asking for Vim mode would know how to use it.
The question is if it gives the camper access to "tools" that we have disabled intentionally to force a more manual interaction with the editor. However, I would argue that remapping existing keybindings does not do that.