[BUG] vSphere v7.0.3 VM-Import VMs Don't Have Corresponding CD/DVD(s) (that were connected to VM on vSphere) Imported

Describe the bug
If there is a CD/DVD attached to the VM in vSphere v7.0.3 (like a .iso file), the VM imported into Harvester does not carry that CD/DVD iso into Harvester -> it will not build a "Volume" with Source "VM Image"
To Reproduce
Steps to reproduce the behavior:

Have vSphere v7.0.3 accessible
Have a VM in vSphere with a CD/DVD attached / connected (like a .iso)
Build a VM Import for Harvester
Import VM, the VM will import successfully, but no CD/DVD .iso gets translated to be at parity w/ vSphere v7.0.3

Expected behavior
Analyze VM on vSphere side, if CD/DVDs connected, queue up importing CD/DVDs as Images & Volume (source type VM Image) into Harvester possibly?
Workaround

manually upload any CD/DVD iso(s) (or variants) from vSphere into Harvester separately

Environment

Harvester ISO version: v1.3.2-rc2
Underlying Infrastructure: bare-metal

it is by design since iso is not really persistent storage for the VM. I am not even sure if exporting a VM as an OVF will contain the iso itself.


Setting the retry policy implicitly in the HDInsight SDK

The retry policy we defined was not applied automatically. This change is to make the policy automatically applied when creating the client. This will help with transient errors even when the client did not specify a retry policy explicitly. The users will still be able to override this after initializing the client.

Can one of the admins verify this patch?

@azuresdkci add to whitelist


feat: ExpressJS support

Express Adapter

Also would like having this approved first, so that I can make Fastify docs in the manner that we agree on here

@markflorkowski Can you also take a look once you have time?

Wait actually this should probably be a separate package, thoughts @juliusmarminge ?

If you plan on making adapter for next a separate package, then I guess every adapter, that requires custom code to work, have to be in separate package. For instance, Fastify requires custom adapter and can be moved to separate package

Wait actually this should probably be a separate package, thoughts @juliusmarminge ?

Why do you think so?


Issue/4402 resource actions joint table (#4725)

Pull request opened by the merge tool on behalf of #4725

Merged into branches iso5 in c134581e0d37d999c8a63f7ed947d18f3a3fc933


Update CRD

Updated CRD Dependencies
generate kube apis for KubeArmorHostPolicy CRD like #343

Codecov Report

Merging #358 (96d7c6c) into master (4040bd6) will decrease coverage by 0.16%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #358      +/-   ##
==========================================
- Coverage   36.90%   36.73%   -0.17%
==========================================
  Files          21       21
  Lines        8978     9057      +79
==========================================
+ Hits         3313     3327      +14
- Misses       5306     5365      +59
- Partials      359      365       +6

Impacted Files
Coverage Δ

KubeArmor/enforcer/runtimeEnforcer.go
35.08% <0.00%> (-4.28%)
:arrow_down:

KubeArmor/enforcer/appArmorEnforcer.go
38.69% <0.00%> (-3.00%)
:arrow_down:

KubeArmor/enforcer/SELinuxEnforcer.go
0.00% <0.00%> (ø)

KubeArmor/core/kubeUpdate.go
44.37% <0.00%> (+0.17%)
:arrow_up:

KubeArmor/monitor/systemMonitor.go
33.33% <0.00%> (+0.40%)
:arrow_up:

KubeArmor/common/common.go
48.87% <0.00%> (+1.68%)
:arrow_up:

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 4040bd6...96d7c6c. Read the comment docs.


Provide an easy way to more categories / apps in the marketplace

with having more apps coming we need to be able to categorize them we can maybe do tags on them too?
categories = {
{ category_name: ...
  apps_list:...,
},

}

allow option to deactivate  solution so it looks disabled in the ui (will be used to show the upcoming solutions that we didn't implement yet)

Commit_ID 95bdc98e5e111086860aeb4af8031a2953f08541, Branch development


Inconsistent window_size description in google-authenticator tool

From @pv2b on July 28, 2015 10:15
When enrolling a new user into google-authenticator, using the google-authenticator tool, this question is asked:
By default, tokens are good for 30 seconds and in order to compensate for
possible time-skew between the client and the server, we allow an extra
token before and after the current time. If you experience problems with poor
time synchronization, you can increase the window from its default
size of 1:30min to about 4min. Do you want to do so (y/n)
I was curious as how this works, it turns out that if you choose "y", the following is dropped into the configuration file:
" WINDOW_SIZE 17
This would seem to mean that there are 17 concurrently valid codes, each of them valid for 30 seconds. That would mean a window of 17/2 minutes = 8m30s, a.k.a. +/- about 4 minutes.
If you choose "n", then nothing is written to the file, and the default in the PAM module is used, which is 3 (pam_google_authenticator.c - window_size function). This means a window of 3/2 minutes = 1m30s, a.k.a. +/- 30-60 seconds.
The problem is that the question above confuses window size with maximum acceptable time difference. The 1m30s referred to is a window size, and the ~4 minutes is a maximum acceptable time difference. The maximum acceptable time difference is approximately half the window size.
This could be resolved either by changing the descriptive text of the question, or by changing the behaviour to reduce the WINDOW_SIZE.
Copied from original issue: google/google-authenticator#510

@dene14 that appears to be a bug. This code makes no sense since it only runs when !use_totp.

From @mikesoule on October 14, 2015 23:53
+1 @pv2b Thanks for posting this!

From @dene14 on March 7, 2016 23:34
Additionally I would like to note that adding --minimal-window flag make WINDOW_SIZE value equal to "-1" which prevent any valid code from being accepted. Or please tell how it's supposed to work.

Sorry for the delay on this.
The new phrasing is:
By default, tokens are good for 30 seconds. In order to compensate for
possible time-skew between the client and the server, we allow an extra
token before and after the current time. If you experience problems with
poor time synchronization, you can increase the window from its default
size of +-1min (window size of 3) to about +-4min (window size of
17 acceptable tokens).
Do you want to do so? (y/n)

Is that good enough? Suggestions welcome.

Hi. The phrasing you suggested is still not accurate.

By default, tokens are good for 30 seconds.

No, by default, the window size is 3, which means that any given token is valid during a time frame of 1 minute 30 seconds. From the perspective of the user, assuming perfect time sync between the server and client, a token is valid for 1 minute after it first appears on the screen of the mobile app, and 30 seconds after it's disappeared.
Better phrasing might be: "A new token is generated every 30 seconds by the mobile app."
In fact, how about this as a suggested phrasing?
A new token is generated every 30 seconds by the mobile app. In order to compensate for
possible time-skew between the client and the server, we allow an extra
token before and after the current time. This allows for a time skew of up to 30 seconds between authentication server and client. If you experience problems with
poor time synchronization, you can increase the window from its default
size 3 permitted code (one previous code, the current code, the next code) to 17 permitted codes (the 8 previous codes, the current code, and the 8 next codes). This will permit for a time skew of up to 4 minutes between client and server.

That sounds much clearer. I'll take care of it tomorrow.

Perhaps keep the "by default" part, as the STEP_SIZE can be modified so that it's not just 30 seconds (some tokens are 60 seconds, for instance).


How to use with Cypress/Mocha?

Background:
The mocha-json parser can't be used with old versions of mocha and cypress because the option to output json report to a file was added recently.
Mocha also junit/xunit compatible reporters:

https://github.com/michaelleeallen/mocha-junit-reporter
https://mochajs.org/#xunit

If we were to use any of this which parser should we select in this action?

For anyone else wondering, the unit reporter of cypress and java-junit parser works (Ref : https://github.com/OctopusSamples/junit-cypress-test/commit/fc6b78f0a84b7325b8138fd5a24d0208d4e0ca55)

I tried making a copy of the mocha json reporter, and fixing it to use one json file per test file... but the result was the following:
Cannot read property 'startsWith' of undefined

(with no traceback, grr)
Using java-junit works, but only after I made a copy of mocha-junit-reporter, because the parser dies on suites that have no tests, such as the parent suites of nested suites.


Mocking - Integrate WireMock for downstream REST api dependencies

e.g.
You are developing a REST api GET:/api/v1/persons/p001

and to build up the person details, this service needs to get address details of this person from another REST service
i.e. Get the address details for p001 using API GET:/api/v1/addresses/pid/p001

Many times while designing an integration test we need to mock GET:/api/v1/addresses/pid/p001 to provide response as e.g.
GET:/api/v1/addresses/pid/p001
Response:
{
   "personId": "p001",
   "address": {
          "line1" : "10 Downing Street"
    }
}

Then the GET person will respond with:
GET:/api/v1/persons/p001
Response:
{
   "personId": "p001",
   "name": "Peter",
   "age": 33,
   "address": {
          "line1" : "10 Downing Street"
    }
}

Release version 1.1.31
See working examples here:
https://github.com/authorjapps/zerocode-hello-world/blob/master/src/test/resources/wiremock_tests/mock_via_wiremock_then_test_the_end_point.json


BUG: sealos upgrade cluster

Sealos Version
4.3.0
How to reproduce the bug?

1.23.8  upgrade to 1.24.0
What is the expected behavior?
No response
What do you see instead?
No response
Operating environment
- Sealos version:
- Docker version:
- Kubernetes version:
- Operating system:
- Runtime environment:
- Cluster size:
- Additional information:

Additional information
No response

fixed in https://github.com/labring/sealos/pull/3588

v4.3.1+


expand discussion of binary repo setup for in-place import

See discussion on https://trello.com/c/SsE1sGqR/184-in-place-import-doc-is-unclear. Staged at https://ci.openmicroscopy.org/job/OMERO-DEV-merge-docs/ws/src/omero/_build/html/sysadmins/in-place-import.html#additional-setup-requirements.

Re no-one - grammarly says this is uncommon, and it is best to stick to the two words version (no one). Btw I know this was not changed in this PR, but it is in the same doc.

Downloading this service file is a loss of time, cannot read it, cannot open it in Chrome or sublime text, why is it there ? How am I supposed to consume this information ?

Not planning to fix the service file issue.

Reads nice. Ready to merge FMPOV


Display the low quantity fixed fee and/or attrition requirements.

For low quantity of some parts, JLC assembly charges a fixed fee, these JLC minimum (eg 20 pieces for resistor is common) are not the same as LCSC minimum (eg 100 pieces for resistor is common).

Examples...

For qty≤20,charges a fixed fee $0.0380 https://jlcpcb.com/parts/componentSearch?searchTxt=0603WAF5101T5E
For qty≤5,charges a fixed fee $3.8045   https://jlcpcb.com/parts/componentSearch?searchTxt=6TPE330ML
For qty≤15,charges a fixed fee $0.2220 https://jlcpcb.com/parts/componentSearch?searchTxt=C20526

it would be good to have this JLC minimum shown in your tool with the pricing.
Also some parts have an attrition requirement, it would be useful to see this as well if the data is available, example below showing the attrition requirement for a part in the JLC quote process.

NB: Their explanation of attrition isn't great, it works like this... Total_Parts_Charged = max( BOM + Attrition, MOQ ) * Price

Unfortunately, JLCPCB does not provide this information in their component table where we source the data from.
To acquire the data, we either have to scrape the page or make requests from the client to the JLC website. Fortunately, the data are available via a GET request on the following URL:
https://jlcpcb.com/shoppingCart/smtGood/getComponentDetail?componentCode=C23186

It gives you JSON with these relevant keys:
"leastNumber": 20,
"leastNumberPrice": 0.0380,
"lossNumber": 6,

I won't be able to implement the functionality in the next two weeks.

So the implementation is available at http://jlcparts-dev.honzamrazek.cz/. Could you test it and let me know if you spot any bugs? I will merge it to upstream if after I get your confirmation it works correctly.

I'm not seeing it, where should I be looking?

Try it again - there was a problem with CORS on the deployed page I didn't notice.

Works, but the calculation appears incorrect for the item I checked...

Ouch, the quantity is sometimes returned as string and then Javascript concatenates instead of adding /o. It should be fixed now.

Cool I checked some random ones and they seem ok to me :+1:

Ok, so I deployed it on the main page.


Auto-hide menubar on Linux

I confirm (by marking "x" in the [ ] below: [x]):

[x] This is not a troubleshooting question. Troubleshooting questions go here: http://www.mattermost.org/troubleshoot/.
[x] This doesn't reproduce on web browsers (such as in Chrome). If it does, issue reports go to the Mattermost Server repository.
[x] I have read contributing guidelines.

Summary
Most Electron apps on Linux have an option to autohide the menubar, typically in the View or Window menus. Mattermost would fit in better if it did, too.
Steps to reproduce

OS: Pop!_OS 17.10, elementary OS 0.4 Loki, any other Linux-based OS.
Desktop App: 4.0.0
Sever: 4.0.0 (4.0.1)

Install Mattermost on a Linux-based system, see the menubar. :wink:
Expected behavior
There is a "Toggle Menu Bar" or "Always Show Menu Bar" option on Linux, like in Atom or Slack.
Observed behavior
The menubar is always visible and not hideable
Other
Opening as this is separate and distinct from #457; that deals with Windows specifically, whereas adding widgets to the titlebar is not something supported in Electron on Linux as far as I know.

Thank you for this suggestion @cassidyjames!
@yuya-oc Can you help apply "Linux" and "Feature" labels on this ticket.

Would love to see this as well. The menu bar is just taking up screen estate and looking ugly compared to the mattermost-desktop application.

Closing via feature request here: https://mattermost.uservoice.com/forums/306457-general/suggestions/36842089-desktop-auto-hide-menubar-on-linux.


Small fixes for 3.11.2 patch release

Closing in favour of https://github.com/nf-core/rnaseq/pull/1008


Feature: Add 'all' sensors

Would be nice to be able to see a list of all new shows/movies as an easier way to discover new content.
The API is the same, just changes the path from my/ to all/

I will !


Blazor Serverside App Service Linux problem SignalR

Describe the bug
When running latest Blazor i got weird behavior in Azure App Service with Linux. After only couple of seconds switching tabs or not active window it seems like SignalR timeout rror: Connection disconnected with error 'Error: WebSocket closed with status code: 1006 .
App Service Linux (this one getting error)
https://blazornb.azurewebsites.net/ListBanks
App Service Windows (This works)
https://blazornbwin.azurewebsites.net/ListBanks
Uncaught Error: Server returned handshake error: Handshake was canceled.
    at e.processHandshakeResponse (blazor.server.js:1)
    at e.processIncomingData (blazor.server.js:1)
    at e.connection.onreceive (blazor.server.js:1)
    at WebSocket.i.onmessage (blazor.server.js:1)
blazor.server.js:1 [2019-07-12T06:53:56.148Z] Error: Connection disconnected with error 'Error: Server returned handshake error: Handshake was canceled.'.
e.log @ blazor.server.js:1
blazor.server.js:15 [2019-07-12T06:53:56.149Z] Error: Server returned handshake error: Handshake was canceled.
e.log @ blazor.server.js:15
blazor.server.js:1 Uncaught (in promise) Error: Cannot send data if the connection is not in the 'Connected' State.
    at e.send (blazor.server.js:1)
    at e.sendMessage (blazor.server.js:1)
    at blazor.server.js:1
    at new Promise (<anonymous>)
    at e.invoke (blazor.server.js:1)
    at Object.<anonymous> (blazor.server.js:15)
    at blazor.server.js:15
    at Object.next (blazor.server.js:15)
    at blazor.server.js:15
    at new Promise (<anonymous>)
blazor.server.js:15 [2019-07-12T06:53:59.150Z] Error: TypeError: window.Blazor.reconnect is not a function
e.log @ blazor.server.js:15
blazor.server.js:15 [2019-07-12T06:54:02.150Z] Error: TypeError: window.Blazor.reconnect is not a function
e.log @ blazor.server.js:15
(anonymous) @ blazor.server.js:8
(anonymous) @ blazor.server.js:8
(anonymous) @ blazor.server.js:8
a @ blazor.server.js:8
blazor.server.js:15 [2019-07-12T06:54:05.152Z] Error: TypeError: window.Blazor.reconnect is not a function

To Reproduce
Steps to reproduce the behavior:

Install latest Blazor on Dotnet core 3.0.100-preview6-012264
Run this code https://github.com/mrweiland/NorthbricksBlazorServerSide
Package the framework within package. (this because azure app service have problem adding site extensions that works with dotnet core previews)
Setup azure app service on Linux
Browse to page - wait 1 minut - switch from page.

Expected behavior
No timeout.....
Screenshots

Additional context
If i run without IIS locally it works - when i compile and run with iis web express i got same behavior as app service.
λ  dotnet --info
.NET Core SDK (reflecting any global.json):
 Version:   3.0.100-preview6-012264
 Commit:    be3f0c1a03

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.17763
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\3.0.100-preview6-012264\

Host (useful for support):
  Version: 3.0.0-preview6-27804-01
  Commit:  fdf81c6faf

.NET Core SDKs installed:
  2.1.602 [C:\Program Files\dotnet\sdk]
  2.1.604 [C:\Program Files\dotnet\sdk]
  2.1.700 [C:\Program Files\dotnet\sdk]
  2.1.701 [C:\Program Files\dotnet\sdk]
  3.0.100-preview6-012264 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]

  Microsoft.AspNetCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.0.0-preview6.19307.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.0.0-preview6-27804-01 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.0.0-preview6-27804-01 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Thanks for contacting us, @mrweiland.
@bradygaster, does SignalR work for AppService & Linux combination?
@mrweiland, can you also please try to run your app with Azure SignalR service? This is the recommended configuration.

@ajaybhargavb, can you please file a manual verification item for this scenario (Blazor Server App deployed to Azure AppService on Linux)? Thanks

@mkArtakMSFT checking with @vijayrkn on this - one thing i do know is that preview 7 will not work until the service team publishes a new NuGet that fixes an API breaking change. @chenkennt knows about this and is working to get that out. We had a way to make this work for Linux but I need to verify with Vijay when this will go out.

The work to make it work for Linux is not complete yet but should be available in an upcoming VS release.

Does this have anything to do with the signalr service?

Does this have anything to do with the signalr service? It just looks like a normal blazor hosted application on app service for linux.

Apologies for inferring that, when I saw this comment from @mkArtakMSFT i presumed ASRS was involved in the discussion (or that it might become a part of the discussion).

@mrweiland, can you also please try to run your app with Azure SignalR service? This is the recommended configuration.

We should still be investigating if there's an issue running SignalR on App Service for Linux. Azure SignalR is the recommended configuration but we should work on App Service for Linux.

@anurse - left commentary over here after talking with the devs and trying out the scenario.

Hello, reviving this. I'm trying to host an ASP.NET Core Mvc app that uses SignalR, on a Azure Linux Web App (B1 tier). The setup works perfectly in my local machine.
However, when deployed, I get this error message on the console:
WebSocket connection to 'wss://XXXXXX/myhub?id=XXXXX' failed: Error during WebSocket handshake: Unexpected response code: 503

Which .NET Core version are you trying? Would you be willing to share your code?

@jcmontx I'd suggest opening a new issue rather than attaching to this existing one. This issue is for Blazor usage and you're referencing an MVC app using SignalR. The root cause may end up being the same, but it's easier to diagnose that if we're looking at these separately. Adding in the details @bradygaster asked for in the new issue would help :).

@bradygaster I was using ASP.NET Core 2.0 BUT on top of .NET Core 2.2.
@anurse yes, I know. It was not my intention to detract from the main issue.

Appreciate that, @jcmontx - could you open a new issue? We'll triage that one independently as @anurse pointed out.


In the c++ client implementation,Why is object data acquired from the metadta?

Describe your problem
In the c++ client, get_objet is based on get_metadata, and the object is acquired from the buffer section of the metadata, which
contradicts the statement in the document that:

Vineyard represents all kinds of data as vineyard objects, for any vineyard object, it consists of two parts:
A set of blobs where the payload of the data lives in;
A hierarchical meta tree that describes the type, layout, and properties of the data.
The decoupling design of data payload and data layout brings three benefits:

it suggests that the metadata and payload are stored separately,
metadata and payload are still stored in different places. Although in the client-side, object are acquired from the metadata, they are stored in a separate place in the server, metadata are stored in the metastored, and payloads are stored through the Apache-Array.

which contradicts the statement in the document that:

Actually get includes two part: get_metadata(), then get_buffers() that involves in the returned metadata.

Closing as answered.


Add aria-hidden to zoom controls

Add aria-hidden to zoom controls to revents screen readers from announcing the characters "plus" and "minus" on hover
Fix: #7433
@Malvoz fyi

Add aria-hidden to zoom controls to prevent screen reader from reading

To clarify this prevents screen readers from announcing the characters "plus" and "minus" on hover (applicable to users that use screen readers and mouse). The linked issue does describe that but thought I'd clarify because the comment made it sound like it'd prevent screen readers from announcing "zoom in"/"zoom out". 😋

Can the title of this PR be renamed to "Add aria-hidden to the +/- characters of zoom controls" or something along those lines? It's just that it's currently quite a scary title from an accessibility perspective 😄


Issue to use global scope when use docker swarm mode and v2plugin

Hi Team,
When I trying to use kuryr-libentwork(which is a remote driver) in docker swarm mode, it looks good when I run it with "local" scope in NetworkDriver. But when I run it in "global" capability, it can't works and it show the "swarm" scope. Is it supported run in "global" capability when I use docker swarm mode with v2plugin?
Here is some info:
Docker Version:
# docker version
Client:
 Version:      1.13.1-cs2
 API version:  1.26
 Go version:   go1.7.5
 Git commit:   ad32da7
 Built:        Thu Feb 23 16:40:08 2017
 OS/Arch:      linux/amd64

Server:
 Version:      1.13.1-cs2
 API version:  1.26 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   ad32da7
 Built:        Thu Feb 23 16:40:08 2017
 OS/Arch:      linux/amd64
 Experimental: false

Here is the log , it runs normal when it is local scope:
# docker network ls
NETWORK ID          NAME                DRIVER              SCOPE
08da057d698b        bridge              bridge              local
526a0b195163        docker_gwbridge     bridge              local
83f849eb1d60        host                host                local
ouqu3ermkxba        ingress             overlay             swarm
772b4aa8d77b        limao_swarm_kuryr   kuryr:latest        local
1f88364d0ab8        none                null                local

Here is the log, it can't works when I use "global" scope, it shows it is "swarm" scope and can't even show the Driver name(The network name is limao_kuryr1):
# docker network create --driver=kuryr --ipam-driver=kuryr --subnet <IP_ADDRESS>/24  --gateway <IP_ADDRESS> --ip-range  <IP_ADDRESS>/24 -o neutron.net.uuid=55aec833-7838-482f-be9e-b205e5c6f2c4 limao_kuryr1

# docker network ls
NETWORK ID          NAME                DRIVER              SCOPE
3aa3c903c45f        bridge              bridge              local
526a0b195163        docker_gwbridge     bridge              local
83f849eb1d60        host                host                local
ouqu3ermkxba        ingress             overlay             swarm
qazi7mnpl7br        limao_kuryr1                            swarm
1f88364d0ab8        none                null                local

I use global scope, but it shows "swarm" scope here:
# docker network inspect limao_kuryr1
[
    {
        "Name": "limao_kuryr1",
        "Id": "qazi7mnpl7brjxho4kbb62nu7",
        "Created": "0001-01-01T00:00:00Z",
        "Scope": "swarm",
        "Driver": "",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "kuryr:latest",
            "Options": null,
            "Config": [
                {
                    "Subnet": "<IP_ADDRESS>/24",
                    "IPRange": "<IP_ADDRESS>/24",
                    "Gateway": "<IP_ADDRESS>"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Containers": null,
        "Options": null,
        "Labels": null
    }
]

Thanks.

Loop @mavenugo @anusha-ragunathan .
I see [1] has merged in 1.13.1, but looks like it still can't work with scope global plugin v2, I aslo tried to use [2] for test, and the only thing I modify is to change scope from local to global, I get similar problem with that test netplugin.
Can 1.13.1 support v2 network plugin with global scope? Thanks for your help.
[1]https://github.com/docker/docker/pull/30145
[2]https://github.com/mavenugo/test-docker-netplugin

@LipingMao in swarm-mode, the global scoped drivers are displayed as swarm scoped to indicate the fact that there is no external kv-store required and swarm-manager handles the creation and management of networks. So, when you see swarm scoped network in swarm-mode, it is a good thing.
The driver name should also show up properly. I don't know why it is failing on you.
Can you pls share how you install the plugin and also the output of docker plugin ls ?

@LipingMao : [2] above has not been updated to global/swarm scope.
You can use https://hub.docker.com/r/aragunathan/global-net-plugin as a mock globally scoped network plugin (source at https://github.com/anusha-ragunathan/global-net-plugin)

@mavenugo  @anusha-ragunathan
Thanks for you quick response and support first.
@mavenugo
I install the kuryr-libentwork v2plugin by docker plugin install --alias kuryr limao/kuryr-libnetwork-v2plugin . when I configure kuryr-libentwork works in local scope, it works fine, but when I configure it to global scope it can't works. here is the output of docker plugin ls:
# docker plugin ls
ID                  NAME                DESCRIPTION                          ENABLED
f77444226596        kuryr:latest        kuryr-libnetwork plugin for Docker   true

@anusha-ragunathan I tested your repo, it can work in my environment.
I think I may find the problem, in kuryr-libentwork, we has not implyment the following two NetworkDriver API: AllocateNetwork / FreeNetwork
I think that may be why my kuryr-libentwork v2plugin can only work in local scope but can't work in global scope. Is this must when enable globally scoped network plugin?
Kuryr-libentwork implyment the apis in [1], but I did not find AllocateNetwork and FreeNetwork in that document. Did I miss anything?
Thanks again for your help  @mavenugo and @anusha-ragunathan
[1] https://github.com/docker/libnetwork/blob/master/docs/remote.md

@mavenugo  @anusha-ragunathan
BTW,
I can reproduce the same problem by change the scope in [1] from local to global in main.go, and re-build it. Then it will have the same problem with kuryr-libnetwork. If I use that plugin to create network, I can't see DRIVER name.
For example:
docker network ls
NETWORK ID          NAME                DRIVER              SCOPE
...
qazi7mnpl7br        limao_test                            swarm
...
[1] https://github.com/mavenugo/test-docker-netplugin

@LipingMao yes. its a doc issue. PTAL : https://github.com/docker/libnetwork/blob/master/driverapi/driverapi.go and implement the APIs as mentioned in the comments.
Also, PTAL overlay driver as an example of how this is used.
I will fix the docs asap.

+1. Seeing this issue with global scoped plugins in swarm mode.

@LipingMao : Yes, the 2 new APIs need to be implemented for swarm-mode.
@mavenugo : https://github.com/docker/libnetwork/issues/1649 was created a while back :)

Hi, I'm getting the following error when I set capability_scope to "global" with the latest Docker-CE. ("local" works fine.) I simply created /etc/kuryr/kuryr.conf file and started a container with kuryr/libnetwork:latest image.
Error response from daemon: rpc error: code = 3 desc = legacy plugin kuryr of type NetworkDriver is not supported in swarm mode```

[DEFAULT]
bindir = /usr/libexec/kuryr
capability_scope = global
log_dir = /var/log/kuryr
log_file = kuryr.log
[neutron]
project_name = admin
password = password
username = admin
auth_url = http://<IP_ADDRESS>:35357/v2.0
auth_type = password```
Any idea?

Legacy network plugins (aka pluginv1) is not supported in swarm mode. This is expected.

Do you mean the latest kuryr-libnetwork does not support pluginv2? I also tried https://review.openstack.org/#/c/449038/ this patch to build rootfs and then "docker plugin create" -> "docker plugin enable" but didn't work.

@hyunsun  from you log message , it looks like you are still using legacy plugin not pluginv2. I'm working on the patch https://review.openstack.org/#/c/449038/ , it works in my local environment, if you have any problem when you try kuryr-libnetwork pluginv2, Can you help to add comments(with reproduce steps) on that patch?  or you can ping us in kuryr team irc : openstack-kuryr , my irc: limao , I can debug with you to see what happened.

Ah..sorry I'm not familiar with Swarm mode. how can I set pluginv2?
These are the commands I used.
I have the above kuryr.conf under the /etc/kuryr.
$ cd kuryr-libnetwork
$ git review -d 449038
$ contrib/docker/v2plugin/v2plugin_rootfs.sh
$ sudo docker plugin create kuryr/kuryr-libnetwork-v2plugin ./
$ sudo docker plugin ls
ID                  NAME                                     DESCRIPTION                          ENABLED
f57a831f01f1        kuryr/kuryr-libnetwork-v2plugin:latest   kuryr-libnetwork plugin for Docker   false
$ sudo docker plugin enable f57a831f01f1
$ sudo docker plugin ls
ID                  NAME                                     DESCRIPTION                          ENABLED
f57a831f01f1        kuryr/kuryr-libnetwork-v2plugin:latest   kuryr-libnetwork plugin for Docker   true
$ sudo docker network create --driver kuryr test-net
Error response from daemon: rpc error: code = 3 desc = legacy plugin kuryr of type NetworkDriver is not supported in swarm mode

I'll join the irc channel.

@hyunsun  I think the error here maybe because the driver name should be like this:
docker network create --driver kuryr/kuryr-libnetwork-v2plugin:latest test-net
I followed your steps and this command can work in my environment.
BTW, the configuration file of kuryr is depend on how you want to deploy kuryr , it can works in vm-nested or direct with neutron lay2 agent, we can discuss this in irc channel if you have problem.

@LipingMao It works! Thanks :D

Hi @LipingMao,
I'm getting another error when I create a service with kuryr driver network.
$ sudo docker network create --driver=kuryr/libnetwork2:latest --ipam-driver=kuryr/libnetwork2:latest --subnet=<IP_ADDRESS>/24 --gateway=<IP_ADDRESS> kuryr-net

Error log from the plugin.
2017-07-11 09:21:06.950 12 INFO kuryr_libnetwork.controllers [-] Creating subnetpool with the given pool CIDR
2017-07-11 09:21:20.221 12 ERROR kuryr_libnetwork.utils [-] Unexpected error happened: Subnet with pool f96b5ff6-4065-4eed-9854-3a54122f90c9 does not exist.: KuryrException: Subnet with pool f96b5ff6-4065-4eed-9854-3a54122f90c9 does not exist.
2017-07-11 09:36:28.115 13 INFO kuryr_libnetwork.controllers [-] Subnet already deleted.
2017-07-11 09:36:28.121 13 CRITICAL kuryr [-] Unhandled error: IOError: write error
2017-07-11 09:36:28.121 13 ERROR kuryr IOError: write error
2017-07-11 09:36:28.121 13 ERROR kuryr

Any idea?
BTW, where is the right place for me to post a question?

@hyunsun Thanks for you use kuryr-libnetwork, I do not think here is the right place to discuss kuryr-libnetwork related question. kuryr-libnetwork is a openstack sub project, so you can report your problem in https://bugs.launchpad.net/kuryr-libnetwork . And we have irc channel #openstack-kuryr. You can also send mail to openstack mail list<EMAIL_ADDRESS>with [kuryr] in your subject. or you can send me mail directly<EMAIL_ADDRESS>if you are not sure how to do. Thanks.

@LipingMao thanks for the information.

@mavenugo Is it anyhow possible to ping a container on the overlay from another VM which is participant in swarm?


Future Tests

These aren't on the roadmap yet
Positive Tests

[ ] Max, min values of floats. Only ones with limited ranges?
[ ] Texture of different types (normal,opaque) using same texture at the same time
[ ] Alpha_blend, alpha_mask w/ double sided
[ ] Alpha modes tested with different alpha factors (1, 0, 0.8)
[ ] Name field with special cases (null string, duplicated)
[ ] Support of at least eight morphed attributes
[ ] jpeg textures
[ ] Different types of URI (web url, texture in bin, glb)
[ ] Occlusion, roughness, and metallic textures in both a single packed texture as well as each with its own texture.

Negative Tests

[ ] Outside of range for attributes that have float values
[ ] Model missing a top level feature. E.g. Missing material, or node, etc… (Won't render anything)

Would like to request a test case using accessor.normalized as well.

The byte and short accessors here are normalized: https://github.com/bghgary/glTF-Asset-Generator/tree/generated-assets/GeneratedAssets/Primitive_Attribute
We somehow lost the note about this in the README. @stevk @kcoley Can you add this back? Thanks!

I can work on adding the note.  We will also need to push out an update to the generated assets branch since the normalized bytes and shorts were miscomputed in v0.3.  The corrected values are currently available on the develop branch.  I'll work on an update for both of these changes.

Awesome, thanks!

No problem!
Here is an updated release with the proper normalized byte and short values and the updated README.  The models have also been changed to the +z forward convention:
https://github.com/bghgary/glTF-Asset-Generator/releases/tag/v0.3.1

Consolidated list with #63


This angular2-webpack saved my day

I have migrated my app to your angular2-webpack to check if this seed will get along with some module I am trying to use: KnexJS. Happly, it works.
Before this decision, I have tried to implement this module (KnexJS) with angular-cli / official angular quickstarter and AngularClass starter. KnexJS module doesn`t works as expected on those starters.
npm install knex;
npm install @types/knex;

The problem I faced is explenaid on stackoverflow question. May you help us understand why those webpack starters dont work with this module as your preboot/angular2-webpack does very well.
Knex is an SQL ORM to node, but it can be built using a JavaScript build tool such as browserify or webpack. In fact, the documentation from it uses a webpack build.

All the solutions named here (and my starter) are frontend starters and knex is a server side library. It is not supposed to be used on any of them.

Knex has function that let us create sql string with the use of toString(). So, there is a use on browser too. One use of it is to take advantage of websql.

Forming database queries on the client-side sounds like a major security risk to me, or is websql a local storage thing? Looks like the W3C abandoned the spec in 2010.


Update Menu & DisclosureGroup usage for Mac Catalyst 17.0

Closes #521
As of 17.0, disclosure triangles in Catalyst appear white whereas they used to be much darker, making this issue more visible:

Before
After

iOS (No change)

Catalyst

Popups (Catalyst)

Open questions for reviewers:

Does the padding look too large in the disclosure groups?
Should we also apply these fixes to the disclosure groups in the Popups component?

This is ready for review once again. Lowered the amount of padding and applied it to the disclosures in Popups.

@des12437 @dfeinzimer Since this is a behavior change that might be fairly noticeable, we should include it in the GitHub release notes.

Not a bad idea!


Only display hero article once on landing

- I think this is not an optimal use of the hero article preview. The article in the hero section should not be displayed in other sections.
- let's make the hero article only appear once on the landing

:wave


[PubSub] Failed precondition when using ordering key.

Seems like Publisher doesn't batch messages correctly based on ordering key. When calling .publish(...) multiple times with different ordering keys I get the following error:
Status { code: FailedPrecondition, message: "In a single publish request, all messages must have no ordering key or they must all have the same ordering key. [code=539b]", source: None }
Per the Publisher documentation it looks like it is supposed to be able to handle different ordering keys just fine: "Each item is added with a given key. Items added to the empty string key are handled in random order. Items added to any other key are handled sequentially."
I don't know if this is a documentation issue or an implementation issue, but at least I could not find anything in the documentation stating that multiple different ordering keys is not supported by a single Publisher. I guess the workaround for now would be to use one Publisher per ordering key.

We have investigated and found that this is an implementation issue and will correct it.
Although the number of requests has increased, the error can be suppressed by setting the bundle_size to 1 in the PublisherConfig, so please use this as a work-around.
 let topic = client.topic("test-topic2");
 let publisher = topic.new_publisher(Some(
        PublisherConfig {
                bundle_size: 1,
                ..Default::default()
        }
));

Thank you for the suggested workaround


Added instructions to clone the repo

Because my Leiningen knowledge wasn't deep enough to know if this would
be automatically done for me with lein clonings watch. :smile:

Great, thank you!


export optimized as well as debug libraries if found

Fixes #86.
Before: http://ci.ros2.org/job/ci_windows/994/
After: http://ci.ros2.org/job/ci_windows/997/

Reading over the code looks ok, but I have some major conflicts locally so I didn't run it on my mac. I'm happy with the changes if CI is. The Windows CI is probably enough, but do you intend to run CI for Linux/OS X?

I ran all platform with both build types successfully. Since only Windows has a relevant change (from didn't work before to works now) I didn't link them all.


Second picture in Gellary is skipped

Hi, there is an obvious bug with the Lightbox Gallery mode, which was found not only in my sample website but also in the official website.
http://dimsemenov.com/plugins/magnific-popup/
When you click any of the thumbnails in the Gallery and, only when your cursor is ON the shown picture, hit the right arrow key of your keyboard.  Then, the next picture is always skipped at this time only and the third picture comes up.  From this point, arrow keys work appropriately and no picture is skipped.
This does not occur if you hit arrow keys while your cursor is OFF the magnified picture.
I'd appreciate it if somebody could fix this as soon as possible.

There is a similar open issue form long time ago: #158.
https://github.com/dimsemenov/Magnific-Popup/issues/158

I was able to surpress this problem by removing "title" from the thumbnail.  When I say the cursor is "grabbing" the thumbnail, it was the situation that a picture title of the thumbnail is shown underneath the cursor.
Here is my code.  I removed the title from this.


added brief overview of Aries

Signed-off-by: Tomisin Jenrola<EMAIL_ADDRESS>Title:
Added a "What is Aries?" doc
Description:
Part of https://github.com/hyperledger/aries-framework-go/issues/2005
Closes https://github.com/hyperledger/aries-framework-go/issues/2006
Summary:
Overview on Aries. Initial steps towards documenting key concepts about the project.

Thanks @talwinder50 , I have them listed here https://github.com/hyperledger/aries-framework-go/issues/2005. Do you mean I should add them in this file so they can later have a link to their respective documentation once created?

Thanks @talwinder50 , I have them listed here #2005. Do you mean I should add them in this file so they can later have a link to their respective documentation once created?

Yes that will be great

Added 👍


Release 6.0.0 is missing some downloads

Release 6.0.0 (https://github.com/wildfly-extras/wildfly-camel/releases/tag/6.0.0) is missing user guide and wildfly patch downloads.

That was quick :grinning: Thanks.


installation error for development_simple branch

I tried to install jumpscale on development_simple branch but got this error:
    Installed /opt/code/github/threefoldtech/jumpscale_core
    Running post install task
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/opt/code/github/threefoldtech/jumpscale_core/setup.py", line 135, in <module>
        'cmds/js_doc',
      File "/home/travis/virtualenv/python3.5.2/lib/python3.5/site-packages/setuptools/__init__.py", line 131, in setup
        return distutils.core.setup(**attrs)
      File "/opt/python/3.5.2/lib/python3.5/distutils/core.py", line 148, in setup
        dist.run_commands()
      File "/opt/python/3.5.2/lib/python3.5/distutils/dist.py", line 955, in run_commands
        self.run_command(cmd)
      File "/opt/python/3.5.2/lib/python3.5/distutils/dist.py", line 974, in run_command
        cmd_obj.run()
      File "/opt/code/github/threefoldtech/jumpscale_core/setup.py", line 52, in run
        msg="Running post install task")
      File "/opt/python/3.5.2/lib/python3.5/distutils/cmd.py", line 336, in execute
        util.execute(func, args, msg, dry_run=self.dry_run)
      File "/opt/python/3.5.2/lib/python3.5/distutils/util.py", line 301, in execute
        func(*args)
      File "/opt/code/github/threefoldtech/jumpscale_core/setup.py", line 21, in _post_install
        from Jumpscale import j
      File "/opt/code/github/threefoldtech/jumpscale_core/Jumpscale/__init__.py", line 177, in <module>
        j.core.jsgenerator.generate(methods_find=True)
      File "/opt/code/github/threefoldtech/jumpscale_core/Jumpscale/core/generator/JSGenerator.py", line 53, in generate
        jsmodpath = os.path.join(os.fspath(dpath2), ".jumpscalemodules")
    AttributeError: module 'os' has no attribute 'fspath'

Whoever looks into this should be aware that jumpscale 9.5.1 uses python3.6. Just the configuration of travis needs to be adapted

haa ok so that's the reason, thanks, I'll retry with a proper python version


Gitea can't run with template errors - Docker

Description
Updated to the latest docker image and now Gitea wont launch. Seems to be complaining about "DefaultTheme" function thats not defined
Was previously running v1.21.11 which had no issues with
These are the logs
chown: /data/ssh/ssh_host_dsa_key: Operation not permitted
chown: /data/ssh/ssh_host_dsa_key.pub: Operation not permitted
chown: /data/ssh/ssh_host_ecdsa_key: Operation not permitted
chown: /data/ssh/ssh_host_ecdsa_key.pub: Operation not permitted
chown: /data/ssh/ssh_host_ed25519_key: Operation not permitted
chown: /data/ssh/ssh_host_ed25519_key.pub: Operation not permitted
chown: /data/ssh/ssh_host_rsa_key: Operation not permitted
chown: /data/ssh/ssh_host_rsa_key.pub: Operation not permitted
Server listening on :: port 22.
Server listening on <IP_ADDRESS> port 22.
2024/07/06 08:43:06 cmd/web.go:242:runWeb() [I] Starting Gitea on PID: 15
2024/07/06 08:43:06 cmd/web.go:111:showWebStartupMessage() [I] Gitea version: 1.22.1 built with GNU Make 4.4.1, go1.22.5 : bindata, timetzdata, sqlite, sqlite_unlock_notify
2024/07/06 08:43:06 cmd/web.go:112:showWebStartupMessage() [I] * RunMode: prod
2024/07/06 08:43:06 cmd/web.go:113:showWebStartupMessage() [I] * AppPath: /usr/local/bin/gitea
2024/07/06 08:43:06 cmd/web.go:114:showWebStartupMessage() [I] * WorkPath: /data/gitea
2024/07/06 08:43:06 cmd/web.go:115:showWebStartupMessage() [I] * CustomPath: /data/gitea
2024/07/06 08:43:06 cmd/web.go:116:showWebStartupMessage() [I] * ConfigFile: /data/gitea/conf/app.ini
2024/07/06 08:43:06 cmd/web.go:117:showWebStartupMessage() [I] Prepare to run web server
2024/07/06 08:43:06 routers/init.go:116:InitWebInstalled() [I] Git version: 2.45.2 (home: /data/gitea/home)
2024/07/06 08:43:06 ...s/setting/session.go:77:loadSessionFrom() [I] Session Service Enabled
2024/07/06 08:43:06 ...s/storage/storage.go:176:initAttachments() [I] Initialising Attachment storage with type: local
2024/07/06 08:43:06 ...les/storage/local.go:33:NewLocalStorage() [I] Creating new Local Storage at /data/gitea/attachments
2024/07/06 08:43:06 ...s/storage/storage.go:166:initAvatars() [I] Initialising Avatar storage with type: local
2024/07/06 08:43:06 ...les/storage/local.go:33:NewLocalStorage() [I] Creating new Local Storage at /data/gitea/avatars
2024/07/06 08:43:06 ...s/storage/storage.go:192:initRepoAvatars() [I] Initialising Repository Avatar storage with type: local
2024/07/06 08:43:06 ...les/storage/local.go:33:NewLocalStorage() [I] Creating new Local Storage at /data/gitea/repo-avatars
2024/07/06 08:43:06 ...s/storage/storage.go:186:initLFS() [I] Initialising LFS storage with type: local
2024/07/06 08:43:06 ...les/storage/local.go:33:NewLocalStorage() [I] Creating new Local Storage at /data/git/lfs
2024/07/06 08:43:06 ...s/storage/storage.go:198:initRepoArchives() [I] Initialising Repository Archive storage with type: local
2024/07/06 08:43:06 ...les/storage/local.go:33:NewLocalStorage() [I] Creating new Local Storage at /data/gitea/repo-archive
2024/07/06 08:43:06 ...s/storage/storage.go:208:initPackages() [I] Initialising Packages storage with type: local
2024/07/06 08:43:06 ...les/storage/local.go:33:NewLocalStorage() [I] Creating new Local Storage at /data/gitea/packages
2024/07/06 08:43:06 ...s/storage/storage.go:219:initActions() [I] Initialising Actions storage with type: local
2024/07/06 08:43:06 ...les/storage/local.go:33:NewLocalStorage() [I] Creating new Local Storage at /data/gitea/actions_log
2024/07/06 08:43:06 ...s/storage/storage.go:223:initActions() [I] Initialising ActionsArtifacts storage with type: local
2024/07/06 08:43:06 ...les/storage/local.go:33:NewLocalStorage() [I] Creating new Local Storage at /data/gitea/actions_artifacts
2024/07/06 08:43:06 routers/init.go:138:InitWebInstalled() [I] SQLite3 support is enabled
2024/07/06 08:43:06 routers/common/db.go:23:InitDBEngine() [I] Beginning ORM engine initialization.
2024/07/06 08:43:06 routers/common/db.go:30:InitDBEngine() [I] ORM engine initialization attempt #1/10...
2024/07/06 08:43:06 cmd/web.go:194:serveInstalled() [I] PING DATABASE sqlite3
2024/07/06 08:43:06 cmd/web.go:194:serveInstalled() [W] Table system_setting Column version db default is , struct default is 1
2024/07/06 08:43:07 cmd/web.go:194:serveInstalled() [W] Table project Column card_type db default is 0, struct default is
2024/07/06 08:43:07 cmd/web.go:194:serveInstalled() [W] Table project Column card_type db nullable is false, struct nullable is true
2024/07/06 08:43:07 routers/init.go:144:InitWebInstalled() [I] ORM engine initialization successful!
2024/07/06 08:43:07 ...er/issues/indexer.go:76:func1() [I] PID 15: Initializing Issue Indexer: bleve
2024/07/06 08:43:07 ...xer/stats/indexer.go:41:populateRepoIndexer() [I] Populating the repo stats indexer with existing repositories
2024/07/06 08:43:07 ...er/issues/indexer.go:153:func2() [I] Issue Indexer Initialization took 5.934102ms
2024/07/06 08:43:07 ...xer/stats/indexer.go:87:populateRepoIndexer() [I] Done (re)populating the repo stats indexer with existing repositories
2024/07/06 08:43:07 ...s/actions/cleanup.go:36:cleanExpiredArtifacts() [I] Found 0 expired artifacts
2024/07/06 08:43:07 ...s/actions/cleanup.go:60:cleanNeedDeleteArtifacts() [I] Found 0 artifacts pending deletion
2024/07/06 08:43:07 ...ates/htmlrenderer.go:140:wrapTmplErrMsg() [F] Gitea can't run with template errors: template error: custom:custom/body_outer_pre:5 : function "DefaultTheme" not defined
----------------------------------------------------------------------
{{ else if and (ne DefaultTheme "gitea") (ne DefaultTheme "arc-green") }}
                   ^^^^^^^^^^^^              ^^^^^^^^^^^^
----------------------------------------------------------------------
Received signal 15; terminating.

Gitea Version
1.22
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Running with Docker
docker-compose.yaml
version: "3.3"

services:
  homepage:
    container_name: ${CONTAINER_NAME}
    image: ${IMAGE}
    restart: ${RESTART_STATE}
    ports:
      - ${EXTERNAL_PORT_1}:${INTERNAL_PORT_1}
      - ${EXTERNAL_PORT_2}:${INTERNAL_PORT_2}
    environment:
      - USER_UID=1004
      - USER_GID=1001

    volumes:
      - type: volume
        source: data_vol
        target: /data
        volume:
          nocopy: true

volumes:
  data_vol:
    driver_opts:
      type: "nfs"
      o: "addr=${NFS_ROOT_SHARE},nolock,rw"
      device: ":${NFS_MNT_SHARE}/${CONTAINER_NAME}"

.env
CONTAINER_NAME=gitea
IMAGE=gitea/gitea:latest
TIME_ZONE=Australia/Melbourne

Database
None

reference this PR #27419 to edit your custom/body_outer_pre.tmpl file

Updated the theme names to "gitea-light" and "gitea-dark" however the same error is still showing
Saying that Gitea can't run with template errors: template error: custom:custom/body_outer_pre:5 : function "DefaultTheme" not defined

https://docs.gitea.com/installation/upgrade-from-gitea

The new "theme function": please refer to this:
https://github.com/go-gitea/gitea/blob/2dc69934673e97508a18cdfae5dfcc4a625a6c56/templates/base/head.tmpl#L2

That file doesnt exist in my gitea folder
I have removed any default ui settings in app.ini
still having the same error

It exists.

The solution if anyone finds this is to open that file (for me, running in docker, the path inside the container was /config/gitea/templates/custom/body_outer_pre.tmpl), and change occurrences of DefaultTheme to .DefaultTheme.


update init service registry

Please provide a description of this PR:
make pushContext HostnameAndNamespace init obey the rule oldest first and k8s first.

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
786044b4f6c981b2dbef0e352ec512dec8e570d9
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
02ee705817e4122ca5f11d21adf0e6f9b9783480
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Recreate the "School Calendar" page. Keep their button, but also embed a google calendar under it

https://support.google.com/calendar/answer/41207?hl=en


Move ui watt deployment to our internal deployment repo

Description

References

#0000

Codecov Report

Merging #784 (6534577) into main (82b3bf2) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #784   +/-   ##
=======================================
  Coverage   62.00%   62.00%
=======================================
  Files          14       14
  Lines         229      229
  Branches       20       20
=======================================
  Hits          142      142
  Misses         82       82
  Partials        5        5

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Faster/Smaller output with gifsicle

I've added an option to provide fast output by using gifsicle instead of convert. This is orders of magnitude faster than using convert, however the quality suffers. Nevertheless, it may be useful when speed is more important than quality.
Additionally, I've piped the default output through gifsicle. This reduces the file size marginally. This is an additional dependency, so it might be preferable to allow printing to STDOUT, for piping purposes rather than including this optimization directly in the script.

Don't want to add a dependency, but I'm going to consider allowing outputting to STDOUT in my  next round of working on this.


Exclude example folder from npm module.

Currently for version 2.0.2 on including this npm pakage, Example folder is also added.
Now this folder is almost 185MB in size.
Is it really necessary to include this folder for creating a build, or can we delete it?

Indeed, it is not, I'll remove it as soon as I can, sorry about that!

Hi @jerinjohnk ,
Finally got back to work (🤔😅😇), and looking into this.
Is there a reason you would use version 2.0.2 instead of 2.0.5 ? 🤔
Because 2.0.5 does not include the example package, so you should use this version instead.

My bad. Looks like my colleague had fixed the version coz of some node_module changes we made for this. Will update it to latest one.


Navigation Standardization

The navigation should be standardized across the application. Currently the navigation is different on the home page and the log pages and need to be reconciled.

Resolved by the following changes:

Changing Back to Home to be more accurate
Standardizing Home, Edit/View Log, and Add Entry button row across views
Navigating backwards when canceling a Log Entry view
Adding a Cancel button on the New Log view which navigates to home


Show a split view to allow navigation/inspection of different test messages

Added in https://github.com/microsoft/vscode/commit/57af60a7b7f4774f007c78997763af5e2c67ceaa

@connor4312 What should I see if this is working correctly? Sorry, not too familiar with the test explorer 😅

The split view allows you to view/browse test messages for any retained run. (Runs without messages will be shown with a green ✔ icon and no children)
It's an extension of the previous message peek; it should show when any test fails.
You should be able to click on messages to navigate to them and peek.
There are context menu actions on the runs and test messages, which should work as their tooltips/labels indicate


Cannot access btrfs drive from Windows

Environment
Windows build number: Microsoft Windows [Version 10.0.21337.1010]
Your Distribution version: Release:        10
Whether the issue is on WSL 2 and/or WSL 1: Linux version 5.4.91-microsoft-standard-WSL2 (oe-user@oe-host) (gcc version 9.3.0 (GCC)) #1 SMP Mon Jan 25 18:39:31 UTC 2021

Steps to reproduce

give wsl a disk wsl --mount \\.\PHYSICALDRIVE1 --bare
format it in btrfs sudo mkfs.btrfs /dev/sdc
mount the filesystem sudo mount -o ssd,noatime,space_cache,commit=120,compress /dev/sdc /mnt/test
optional, be incredibly liberal with permissions chown $USERNAME:$USERNAME /mnt/test; chmod ugo+rwx /mnt/test
attempt to open \\wsl$\Debian\mnt\test in explorer

WSL logs: wsl.etl.log
Expected behavior

Windows has access to the btrfs drive.
Actual behavior

"is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
Attempt to access invalid address."
The exact same issue was reported on the original blogpost about --mount but the fix is sshfs-specific

Thanks for the reporting this @Hashbrown777.
So I see the chmod command running on /mnt/test, but the explorer error message is about /mnt/sneak. Can you share the output of ls -la /mnt/sneak to validate that the permissions on that folder are correct ?
On top of that, when mounting disks manually with mount, the non-elevated mount namespace needs to be used for the mountpoint to be accessible in the Windows explorer.
More details here.

Hi @OneBlue
Unfortunately it has to be done with root

The access to the directory tree higher up is fine, explorer can open the directory fine once umounted, atop this I mounted directly to /sneak and ~/sneak and both fail.

Ah yes, test was just a part of the cutdown steps for others to repro, sneak is what I was actually calling it (and in the real case it's mounted from luks-cryptopen's dev-mapper but the repro steps say dev-sdc; but this isn't a part of the issue if you follow the repro steps yourself).

@Hashbrown777 : Makes sense.
Have you tried mounting your drive under /mnt/wsl as suggested here ?
(detailed explanations on the issue).

@OneBlue
Same issue unfortunately

Interesting, because it looks like you can access the parent folder, let's validate that this isn't a permission issue.
Can you share the output of:
ls -la /mnt/wsl

If your WSL user doesn't have access to that folder, adding: -o "uid=$USER" should do the trick

@OneBlue I think the easiest way for you check these suggestions is to test them yourself
.{
	$mount = '/mnt/wsl/test'
	$device = '~/test.img'

	'Mount?'
	pause
	bash -c (@"
		sudo rm -rf $mount $device 2>/dev/null
		fallocate -l 1G $device
		sudo mkfs.btrfs -f $device
		sudo mkdir $mount
		sudo chown -R `$USER $mount
		chmod ugo+rwx $mount
		sudo mount \
			-o ssd,noatime,space_cache,commit=120,compress \
			~/test.img \
			/mnt/wsl/test
		sudo chown -R `$USER $mount
		chmod ugo+rwx -R $mount
		ls -la $mount $mount/..
		df -T | grep 'btrfs'
	"@ -replace '\r','')

	'Test access?'
	pause
	explorer "\\wsl\$(
		wsl -l `
		| %{ $_ -replace '\x00','' } `
		| ?{ $_ -match '^.+(?=\s+\(Default\)$)' } `
		| %{ $Matches.Values }
	)$($mount -replace '/','\')"
	explorer "\\wsl\$(
		wsl -l `
		| %{ $_ -replace '\x00','' } `
		| ?{ $_ -match '^.+(?=\s+\(Default\)$)' } `
		| %{ $Matches.Values }
	)$($mount -replace '/','\' -replace 'test$','')"

	'Unmount?'
	pause
	bash -c "sudo umount $mount;rm $device"
}

This will

create a file device
format it with btrfs
mount it at the given location
make sure everyone has access and it's owned by the user
show the permissions of the mount and its parent
attempt to open the folder in explorer (fails, opens 'Documents')
opens the parent in explorer (to let you click on test yourself, generating the error message)
unmounts and cleans up

Let me know if you make any progress, ta

@Hashbrown777 : Indeed I can repro the same behavior.
I'll have a deeper look and update this issue when I'll have more info.

@Hashbrown777: The root cause is an issue in the plan9 server running inside WSL.
The problem was that when a mountpoint is accessed, the code would check for the device on which the file is, and fail if no matching mountpoint is found in /proc/self/mountinfo (and that appears to be the case for btrfs mounts). The reason for that logic is to prevent access to drvfs shares ( /mnt/X ) from the linux 9p server.
So we made a code change to not disallow file accesses on this scenario, which solves this issue.
The fix will now work its way through the Windows release pipeline and will eventually reach a future insider build.

The fix is incoming, but will be in the next Insider switch.

Do we know when this might be coming? Is the fix in the [wsl] kernel we can compile ourselves?

Still non-functional in Win 11 21H2 Insider Build 22000.168
Any updates?

@Hashbrown777: Unfortunately the fix still hasn't made it to insider builds. It will hopefully be in the next one.

Yesterday I received a Windows Subsystem for Linux WSLg Preview - 1.0.27 update, and it's working now.
So now the host machine has access to the btrfs mounts via P9, but I can't see a way to let other machines on the network see it. I'm guessing there's no way for the host to re-share, forward, or expose WSL2 shares?
I was hoping to leverage the efficiency you guys have made with the direct P9 and not have to host samba or tunnel through ssh..
We can access WSL2 mounts via \\wsl.localhost\: is this a planned enhancement to be able to do something like \\wsl.otherHost\?
I'm having other issues with disks disconnecting, and such, but they're not related to this issue.

There aren't any plans to do something like that right now. \wsl.localhost only resolves in the current machine and isn't at all exposed at the networking level.
Exposing this to other machines would require an actual networking protocol, with all the authentication & security requirements that this would imply.
Overall if you wish to share a wsl mountpoint to other machines, I'd recommend looking at ssh tunnels or samba as you mentioned (nfs and sftp might also be valid options, maybe with better performance if you want to remotely  access those mountpoints from wsl).

@OneBlue Sorry to comment on a closed issue, but did this fix make it to non-insider builds (running 22000.376)? I'm experiencing the same error. Using a raid1 mirror if that matters.

@peeler: Yes the fix should be on that build.  If you're seeing this issue can you detail repro steps and share logs ?

Thanks for the quick response! https://aka.ms/AAfe74a
The terminal commands are as follows:
wsl --mount \\.\PHYSICALDRIVE0 --bare
wsl --mount \\.\PHYSICALDRIVE1 --bare

Start Ubuntu 20.04:
$ cd /mnt/wsl
$ mkdir mymnt
$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0   256G  0 disk
sdb      8:16   0 339.8M  1 disk
sdc      8:32   0   7.3T  0 disk
└─sdc1   8:33   0   7.3T  0 part
sdd      8:48   0   7.3T  0 disk
└─sdd1   8:49   0   7.3T  0 part
sde      8:64   0   256G  0 disk /
$ sudo btrfs filesystem show
Label: 'btrfs1'  uuid: 33d49740-da04-403b-b6df-89dcc63a4dc3
        Total devices 2 FS bytes used 1.91TiB
        devid    1 size 7.28TiB used 1.91TiB path /dev/sdd1
        devid    2 size 7.28TiB used 1.91TiB path /dev/sdc1
$ sudo btrfs device scan
$ sudo mount /dev/sdc1 mymnt/
$ ls -l
total 20
drwxr-xr-x 1 jpeeler jpeeler 188 Jan  5 20:08 mymnt
-rw-r--r-- 1 root    root    197 Jan  5 21:43 resolv.conf
$ ls -l mymnt/
... (files are present)

When navigating to \\wsl.localhost\Ubuntu-20.04\mnt\wsl\mymnt, get the error "attempt to access invalid address."

This happens to me as well!

Thanks for the logs @jpeeler.
Actually, it turns out that the fix is not on your build yet, sorry for the miscommunication.
To work around this, you could install the latest WSL from the store, which has the fix.

Yes, that did solve the problem.
Unfortunately, using the same hardware with an older (but up to date) install I get the error as presented on https://github.com/microsoft/WSL/issues/7527. If you're willing to continue to assist, I can upload logs there just as I did here.

Interesting, can you share the output you get with logs ? I'd be curious to have a look at it.

Thanks for the logs @jpeeler.
Actually, it turns out that the fix is not on your build yet, sorry for the miscommunication.
To work around this, you could install the latest WSL from the store, which has the fix.

I had this issue as well and can confirm installing WSL Preview fixed the issue. I can now see the @ and @home etc. from within File Explorer (whereas before I could only access those directories via WSL itself.)
Thank you!


fix: Disables implicit Cookies url decoding

Tentatively closes https://github.com/corazawaf/coraza/issues/920.

I still think we split the function instead of using using a Boolean constant

Kind of agree but that would require to copy the code. Another option could be:
type kvEscape func(string) string

var (
	urlUnescape  kvEscape = QueryUnescape
	NoEscape      kvEscape = func(s string) { return s }
)

...

q := ParseQuery(out, '&', urlUnescape)

We could split the API with private function
func ParseQuery(string)
func ParseQueryWithoutUnescape(string)

func doParseQuery(string, bool)

Thank you all for the inputs!
I went for the doParseQuery avoiding public booleans and I did a minor refactor to QueryUnescape to improve a bit the readability. I can not notice meaningful differences in benchmarks:
QueryUnescape
Before:
goos: darwin
goarch: arm64
pkg: github.com/corazawaf/coraza/v3/internal/url
BenchmarkQueryUnescape-10    	 4639016	       252.8 ns/op	      78 B/op	       7 allocs/op
PASS
ok  	github.com/corazawaf/coraza/v3/internal/url	1.526s

After:
goos: darwin
goarch: arm64
pkg: github.com/corazawaf/coraza/v3/internal/url
BenchmarkQueryUnescape-10    	 4720306	       249.2 ns/op	      78 B/op	       7 allocs/op
PASS
ok  	github.com/corazawaf/coraza/v3/internal/url	1.515s

ParseQuery (same QueryUnescape)
Before:
goos: darwin
goarch: arm64
pkg: github.com/corazawaf/coraza/v3/internal/url
BenchmarkParseQuery-10    	 2169714	       544.6 ns/op	     627 B/op	       5 allocs/op
PASS
ok  	github.com/corazawaf/coraza/v3/internal/url	1.835s

After:
goos: darwin
goarch: arm64
pkg: github.com/corazawaf/coraza/v3/internal/url
BenchmarkParseQuery-10    	 2197615	       544.0 ns/op	     627 B/op	       5 allocs/op
PASS
ok  	github.com/corazawaf/coraza/v3/internal/url	1.842s

Merging, mind that in the next release, I would write a line about this engine behavior change


Enhance idle member API

Closes #619

Will be taken care of in another PR. The initial author has been MIA.


bug: Cookie and confidentiality agreement content should be regulated

Bug Definition
Cookie and confidentiality agreement content should be regulated
discord username: alicangunduz#0001
## Bug environment
https://musahit-harita-frontend.vercel.app/cerez.pdf
https://musahit-harita-frontend.vercel.app/gizlilik.pdf
Describe how you are producing the bug step by step

Go to https://musahit-harita-frontend.vercel.app/gizlilik.pdf   ,  https://musahit-harita-frontend.vercel.app/cerez.pdf
Read this
Bug appears

Expected Behaviour
afetharita should be replaced and new articles should be added if necessary.
Screen shots

This issue is duplicated with #15

@alicangunduz, @sevilayerkan is right. we can continue with #15 ❤


implement more intuitive zoom gesture behaviour

fixes #283
This works nicely in chrome on android, here's a comparison between the old behaviour on the left and the version of this PR on the right:
chrome-old-new.webm
Note how the two touch locations now remain pinned to the underlying image locations.
Unfortunately this doesn't work entirely yet, since the behaviour in Firefox on android is now more annoying (this is fixed in a later commit, check the update below):
ff-new.webm
The problem here lies with the onpointermove events. When both pointers are moving simultaneously, it can happen that firefox only sends updates for one of the pointers for a while, which means that when the other pointer finally does get an update, it arrives as a large instantaneous jump. Chrome apparently sends a more even rate of updates. Note that I've only tested this on my android phone, I don't know what the behaviour on other browsers on other operating systems would be, but I could imagine a similar problem arising for more setups than just firefox on android.
I saw that the manuelstofer/pinch-zoom library listens to touchmove events rather than pointermove events, and when testing that library the zoom appeared smooth in all browsers. I'm guessing that the update rate is more consistent for touch events.
Since I believe that the experience on firefox is now worse than it was before this PR, I'm only sending the PR as a draft to see what you think about this and to then possibly later switch to touch events depending on what comes out of our discussion.
Feel free to ask if anything is unclear!

I just tried using touchmove instead of pointermove for the two-finger movements and the zoom is now just as smooth in mobile firefox as it is in mobile chrome:
ff-and-chrome-mostly-working.webm
One remaining problem is when a finger is removed and the other continues to move the image around. There we get a sudden jump. I am tempted to completely separate the mouse and touch handling, i.e. getting rid of the pointer* events. The two-input case is only relevant for touch anyway, as you can't have two mouse inputs. For the one-input case, such edge cases might be easier to handle if the logic for the touch case is separate.

Thank you for the nice feedback! Yeah the way that Firefox sends lower update rates on pointer events than on touch events wasn't an issue before because it was kinda hidden by the fixed delta zooming, but now with the smooth approach it does make a difference 😅
I merged the current main branch in to my branch, thanks for fixing the jumping issue when letting go of one finger!

Hi Pascal, I tested on my device based on this link deployed preview from your code. It looks awesome. I just had one minor thing to ask for. Can you add changeset to your PR by running pnpm changeset command and input your change as below before we merge in? Thanks :)

done, is the changeset okay like this?

thanks for merging!
also, i just found a small detail that I want to improve about the double tap zoom behaviour, so don't spend too much effort on releasing everything yet 😅. PR incoming in a few minutes 😁

No worries. It's automatically executed by Github action. It's just a matter of few clicks from my side. The reason I asked for changset because it will collect you as contributor in Changelog 😊

okay it's not gonna be today, looks a bit more tricky than I expected :D

Take your time buddy 😊 I noticed it's rather late in Zurich. Thanks for your meaningful collaboration, good night and catch you later 😊


Responsive issue on home-page (front-end)

From 960px width - 600px width, the footer text is displayed in the middle of the page.

This has been fixed in the latest version of www.jsonschema.net


Feature/consensus/whitelist validators

Setting a whitelist of validators who can participate in consensus.

Thanks for all your helpful comments! Now merging..


px4 cmake error with gazebo

ubuntu 14.04 // gazebo 7.3.1
I downloaded gazebo7 as specified here: http://gazebosim.org/tutorials?tut=ros_wrapper_versions#Gazebo7.xseries
but then when I try to do make posix_sitl_default gazebo
I get this error:
[  1%] [  2%] CMake Error at CMakeLists.txt:23 (find_package):
  By not providing "Findgazebo.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "gazebo", but
  CMake did not find one.

  Could not find a package configuration file provided by "gazebo" with any
  of the following names:

    gazeboConfig.cmake
    gazebo-config.cmake

  Add the installation prefix of "gazebo" to CMAKE_PREFIX_PATH or set
  "gazebo_DIR" to a directory containing one of the above files.  If "gazebo"
  provides a separate development package or SDK, be sure it has been
  installed.

We're not aware that our install instructions wouldn't work. I can re-check later on my machine.

Installing libgazebo7-dev fixed the problem for me. I also needed to install libopencv-dev and protobuf-compiler to be able to build the simulation.

Thanks @antoinealb for the comment. protobuf-compiler and libopencv-dev are already in the list of packages that need to be installed, and I've added a comment that libgazebo7-dev is needed in https://github.com/PX4/Devguide/pull/44.

FYI, I report the same error during a ROS package is built.
After libgazebo9-dev installed by  sudo apt install libgazebo9-dev command, it disappeared.
Environment
Ubuntu 18.04 in x86
ROS Melodic, 'catkin build' environment
PX4 and Gazebo installed


Improved performance by caching bounding rectangle values

Each element calculates it's own bounding rectangle values once. These values are absolute values to the beginning of the page (left: 0, top: 0). While scrolling the cached values are used to calculate the position relatively to the current scroll position, window width & height and in-view offset settings. The cache will be updated on resize and load events to keep track of new element positions.
This reduces javascript execution time on scroll events by removing the call of getBoundingClientRect on each element.

Each element calculates it's own bounding rectangle values once. These values are absolute values to the beginning of the page (left: 0, top: 0).

@derbaeuerle I think you might be mistaken about that. The values are actually relative to the viewport.

@derbaeuerle Ah, I see what you meant. My main concern with this would be correctly updating the cached offsets. We'd need to update them on DOM mutations, which isn't something we're watching for in IE9-10. So, this would effectively break the library in those browsers without a polyfill.


Possible documentation error of recorder file

CARLA version: 0.9.13
Platform/OS: Linux
Problem you have experienced: Documentation does not fit to code.
What you expected to happen: When recording a vehicle turn, the yaw angle in the recorded vehicle position should change. However, it stays close to 0, and the roll is changing; if interpreting the last element of the rotation as roll - according to this docu.
Steps to reproduce: Record a file while a certain car is performing a turn, and check the binary recorder file.
Other information (documentation you consulted, workarounds you tried): https://carla.readthedocs.io/en/latest/ref_recorder_binary_file_format/#packet-6-position
I suppose that the actual rotation angle order in the recorder file is (roll, pitch, yaw) instead of (pitch, yaw, roll). According to https://github.com/carla-simulator/carla/blob/8854804f4d7748e14d937ec763a2912823a7e5f5/Unreal/CarlaUE4/Plugins/Carla/Source/Carla/Recorder/CarlaRecorder.cpp#L158 the recorder does not write a Carla rotation object (which would be (pitch, yaw, roll)) to the recorder file, but the Euler angles of a FTransform, or rather FQuat. Here, the order is (roll, pitch, yaw); see https://github.com/CarlaUnreal/UnrealEngine/blob/68061ec34a1503dd995dbf37d28607bfef220eea/Engine/Source/Runtime/Core/Private/Math/UnrealMath.cpp#L493.
It seems to be only an error in the documentation of the recorder file (https://carla.readthedocs.io/en/latest/ref_recorder_binary_file_format/#packet-6-position). Since the data is written and read in the same way, there is no "bug" in the code, and everything seems to work fine.
Thanks for looking into this!

You are right. We will be fixing this soon


Custom Notifications

I searched around issues and did not see this posted anywhere.  I am trying to use custom notifications, which seem to work fine from the console, etc. however I am NOT able to get them to work when they are in a gcode file.  For example, when I send the following command in the console, I get a notification on my phone.  If I put the same line in a gcode file, I do not get the notification.  I do get other notifications like status changed, progress %, etc. though fine.  Its just an issue with custom notifications in gcode files i am having issues with.
M117 $ MR $:$printer_name Printer Status|Layer change. Progress $progress ETA $a_eta
(no space in the actual code between $s, github formatting)
Do custom notifications have any certain requirements in the actual gcode file to work?  I am using the latest android version on the play store, even updated it this morning with no change. (v2.4.0 - 6/22/23)
mobileraker
v0.4.0-15-g584ac52
M82 ;absolute extrusion mode
START_PRINT BED_TEMP=65 EXTRUDER_TEMP=230
;Nozzle diameter = 0.4
;Filament type = PLA
;Filament name = PLA
;Filament weight = [4.31984818359375]
;M190 S65
;M109 S230
M117 $ MR $:$printer_name Printer Status|Layer change. Progress $progress. ETA: $a_eta (no space in the actual code between $s, github formatting)
M117 Printing
G92 E0
G92 E0
G10
;LAYER_COUNT:17
SET_PRINT_STATS_INFO TOTAL_LAYER=17
;LAYER:0
SET_PRINT_STATS_INFO CURRENT_LAYER=1
M117 $ MR $:$printer_name Printer Status|Layer change. Progress $progress. ETA: $a_eta (no space in the actual code between $s, github formatting)
M117 Layer 1 / 17
M107
G1 F300 Z0.4
G0 F7500 X110.041 Y110.084 Z0.4
;TYPE:SKIRT
G1 F300 Z0.2

Hey 👋,
I am SO sorry for my late reply somehow all of the recent issues for the companion went under the radar.
In case the issue still persits for you, could you please upload a Gcode file for me to have a look at?

Will do. Right in the middle of printing some back to back parts for my wife that don't contain the code but I'll get something uploaded here shortly.

Untitled.zip
I am essentially trying to use custom notifications to alert me when layer changes happen for really long prints that do not really align to the %s i am able to select within the application(time estimates, layer counts, etc).  If there is a better way to alert of layer change using the application, please let me know.
I did not get any of the notifications in the gcode file as it progressed through the layers. I am able to send them from the console fine and get a notification every time.

Thanks for that,
Based on my analysis, it seems that the issue with your GCode file is due to the presence of two M117 lines. To resolve this, kindly delete the second M117 and attempt the test again. It's worth noting that when I tested a GCode file with only one M117 notification line, it worked as expected.

Appreciate the response. I can confirm notifications from the gcode work when i remove the double M117.
That being said, removing the second M117 and only using the Custom Nofitication M117 breaks the layer information on my LCD Screen.

I was under the assumption two M17 messages with the same arguments caused issues, not that you can't have two M117s.
https://github.com/Clon1998/mobileraker_companion/blob/main/docs/Custom_Notifications.md

I am currently testing using SET_DISPLAY_TEXT MSG= to set the LCD Screen instead of M117. I will report back if that ends up working with the Custom Notifications as well.

Appreciate the response. I can confirm notifications from the gcode work when i remove the double M117.
That being said, removing the second M117 and only using the Custom Notification M117 line breaks the layer information on my LCD Screen.

I was under the assumption two M17 messages with the same arguments caused issues, not that you can't have two M117s.
https://github.com/Clon1998/mobileraker_companion/blob/main/docs/Custom_Notifications.md
Is it possible to change the custom notification from M117 to something less used?

I also thought having two m117 would not cause any Problem. However, it seems like Klipper Just skips the first message in case there are two.

So I have not been successful yet with using the klipper display text.  Here is my current GCODE file and my gcode macro in klipper.  The screen updates fine, however custom notifications don't work now.
Untitled.zip
[gcode_macro DISPLAY_PRINT_TIME]
gcode:
{% set cur_layer = printer.print_stats.info.current_layer|int %}
{% set tot_layer = printer.print_stats.info.total_layer|int %}
SET_DISPLAY_TEXT MSG="Layer {cur_layer} / {tot_layer}"

I am not sure what else to try to get my screen and custom notifications to work at the same time.

I ended up flipping the section in the GCODE and got the notifications to work again, however now my screen is back to being messed up.
DISPLAY_PRINT_TIME
M117 $MR$:$printer_name|Layer changed. $progress $eta
So definitely something going on with multiple M117 commands. Not sure if its cause they are back to back, some "timeframe" that has to pass, etc

Not sure what else to try at this point. Even this way the notification does not work.  I have yet to add dwell commands between the commands as I have no idea if that will do anything other than just add delays, etc.  DISPLAY_PRINT_TIME was renamed to DISPLAY_LAYER_INFO
Untitled.zip

Not sure what else to try at this point. Even this way the notification does not work. I have yet to add dwell commands between the commands as I have no idea if that will do anything other than just add delays, etc. DISPLAY_PRINT_TIME was renamed to DISPLAY_LAYER_INFO
Untitled.zip

Interesting and also confusing...
Sadly, I don't have access to my own printer until the end of September ( I know... I am crazy enough to keep working on an app without access to a machine lol).
I will confirm with some other users if they have the same problem regarding custom notifications in GCode files since you are the first one that raises the issue.
Could you do me a favor and try this for me:

Prepare a 4-10 min print/GCode that includes only the m117 for the custom notifications for the layer change
Delete any existing mobileraker.log file
Restart the mobileraker companion
start the print, wait until its done
Provide me the entire mobileraker.log

Afterward do the same with a Gcode File that includes both M117 lines, the one for the custom notifications and the one that you want to use for your LCD.
I'm hoping that the log will provide me with additional clues as to what's happening here.
Also, I still owe you some background as to why I am using M117 for custom notifications. Basically, there are two ways to implement such a system. There are two methods for this type of system. The first is a pull-based approach, which I am not using. This method involves the companion asking the printer for updates at regular intervals, such as every second. The second method, which I am using, is a push-based approach. With this method, the companion subscribes for updates from the printer. Whenever an update is available, the printer itself notifies the companion.
However, this does not solve the problem of injecting custom data you as a user can provide to the companion. To achieve that I opted to use the M117 messages because the companion is notified whenever this value changes. However, it could very well be that Klipper ignores multiple M117 codes and only uses the last one it reads until another

Will do. I am not able to locate any mobileraker.log file on my klipper box.  Do I need to enable something first in order to generate a log file?

Will do. I am not able to locate any mobileraker.log file on my klipper box. Do I need to enable something first in order to generate a log file?

There are multiple locations the logs might be written to.

~/printer_data/logs/
/tmp/
Location defined during the installation of the companion via MOBILERAKER_LOG_PATH

I was not able to find any mobileraker.log using the "locate" command on my debian klipper box.

Ohh wait, you are running mobileraker in a container do you?

Ohh wait, you are running mobileraker in a container do you?

I am on debian and used KIAUH to get everything up and running.

Ohh wait, you are running mobileraker in a container do you?

I am on debian and used KIAUH to get everything up and running. I have a printer_data folder, various venv folders, etc.  I don't see any logs, etc in those locations.

Alright, I need to test the kihau installation once more but I thought I ensured the mobileraker log is written to the default log location of moonraker, Klipper, Mainsail...

Alright, I need to test the kihau installation once more but I thought I ensured the mobileraker log is written to the default log location of moonraker, Klipper, Mainsail...

I went ahead and completely uninstalled and reinstalled everything with KIAUH and I now have a log file for mobileraker in my printer folder.  Either having multiple printers before was causing an issue with logs being created OR since i have had KIAUH around for a while and while upgrading, adding new features, etc something got messed up.  I will go ahead and see about getting this tested for you and report back.

Attached are both tests that i just ran today. I did not get any custom notifications for either of these prints.
logs.zip
gcode.zip

Thanks for your efforts!
I will have a look at them hopefully during the weekend.

Nvm I already looked at the logs.
So I was right, klipper/moonraker skips multiple M117. The companion only received the last one.
Therefore, there is very little I can do to resolve your issue. However, you might want to have a look at klipper's delayed_gcodes. It should enabled you to send the 2nd M117 after a delay of e.g. 2 sec.

Appreciate the constant feedback and assistance on this. I'll look into the delayed gcode stuff and see what that provides. Thanks again! I'll go ahead and close this as it seems to be unrelated to mobileraker and is actually a klipper/mainsail limitation. Given your experience and expertise, please let me know if you feel I should bring this up to the attention of the Klipper or Mainsail folks.


[fix](txn insert) fix txn_insert case

when connect to observer, if the first load sql throw exception before execute(such as unpected label), the txn is not began

run buildall


Edited and added a new css

some changes are modified in  form.jsx
created form.css  is used for increasing opacity should be merged with form.jsx

Thank you so very much for contributing to this project 🎉
Ok, I have a couple of reviews for this pull request.

The way you added the css file is not proper, unfortunately. If you want to extend styles in tailwindcss there is a way to do this. If you look in the tailwind.config.js file, you will see an example of what I am talking about. To read more about this, or for a better understanding, you can check this section of their docs.

The color of what you have added also does not look okay when you compare it with the entire look of the site. I see you added a brown kind of a bg color. This does not look very good on the site because it does not really match the theme. What I'd recommend is that you increase the opacity o the input as we discussed before instead. And looking at the line of code, we have it set to shadow-lg. Tailwind outer shadows go up to 2xl.

Bottom conclusion is, you revert your changes, and simply change the shadow-lg set to the div right after the form element to shadow-xl or something bigger than that just to see how it will look like. If you need any help, feel really free to ask.

Hello @Aravind6369792164 Are you still interested in working on this issue? If not, I will close it.

I'm sorry but I will have to close this PR. I has been stagnating for a while. Feel free to checkout more issues you may want to work on. Thank you nonetheless for your contribution.


Update index.js

fix missing variable error in try catch

https://github.com/sindresorhus/p-limit/issues/39#issuecomment-674003190


Update API documentation for saturation and relative stake

Context
#1980, ADP-431
With cardano-node 1.20.0, the relative_stake field is now relative to the total stake, not the active stake. This makes the saturation calculation correct (tracked by #1980), but it also provides an opportunity to clarify concepts in the API docs.
1.20.0 also made changes to from which snapshot the relative_stake is reported. I believe

-
1.19.0 node + wallet
1.20.0 node + wallet

saturation in ranking
active (taken at end of e-2)
live

wallet api saturation field
non-sensical
correct (and live)

relative_stake snapshot
active (taken at end of e-2)
live

relative_stake relative to
"active" (delegated) stake
total stake

Relevant upstream PRs:

https://github.com/input-output-hk/cardano-ledger-specs/pull/1854
https://github.com/input-output-hk/ouroboros-network/pull/2603

Decision
Review and revise the API documentation.
Acceptance Criteria

[ ] API documentation for relative_stake, saturation, and non_myopic_member_rewards must be correct
[ ] API documentation for relative_stake,  saturation and non_myopic_member_rewards should be helpful

Development

#1980
QA
Docs updated in #1980. Some context on the individual changes is provided in that PR.

lgtm


[AIRFLOW-6121] [API-21] Rename cloud_build service

Make sure you have checked all steps below.
Jira

[ ] My PR addresses the following Airflow Jira issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-XXX
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a Jira issue.
In case you are proposing a fundamental code change, you need to create an Airflow Improvement Proposal (AIP).
In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

Description

[ ] Here are some details about my PR, including screenshots of any UI changes:

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[ ] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[ ] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain docstrings that explain what it does
If you implement backwards incompatible changes, please leave a note in the Updating.md so we can assign it to a appropriate release

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@7bebe8d). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master     #541   +/-   ##
=========================================
  Coverage          ?   84.24%
=========================================
  Files             ?      672
  Lines             ?    38085
  Branches          ?        0
=========================================
  Hits              ?    32086
  Misses            ?     5999
  Partials          ?        0

Impacted Files
Coverage Δ

airflow/gcp/operators/cloud_build.py
100% <100%> (ø)

...flow/contrib/operators/gcp_cloud_build_operator.py
100% <100%> (ø)

airflow/gcp/example_dags/example_cloud_build.py
100% <100%> (ø)

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 7bebe8d...0b247f9. Read the comment docs.


Maestro tests for both: iOS and Android 2 folders with all test cases…

… and 2 folders with regression test

Summary

Test Plan

What's required for testing (prerequisites)?
What are the steps to reproduce (after prerequisites)?
Compatibility

OS
Implemented

iOS
✅❌

Android
✅❌

Checklist

[x] I have tested this on a device and a simulator
[ ] I added the documentation in README.md
[ ] I updated the typed files (TS and Flow)

prerequisites - Maestro Studio has to be installed locally
Test flow is written in a yaml document
To run the associated Flow please provide your Test Case/Test folder path followed by the maestro test command (eg. at VSC)
martagorecka@INV-0152 maestro_tests % maestro test ios/tc1_pager_basic_example.yaml


centos image: yum install bc

This is needed by the coverage build.
Signed-off-by: Greg Greenway<EMAIL_ADDRESS>Fixes #2731

@htuch It's because of https://github.com/envoyproxy/envoy/blob/master/test/run_envoy_bazel_coverage.sh#L80. And git blame points at you :P


Twitter -- not clear documentation re:images

It's not clear if the send the image, the page should be in
a) the same block as the text, and if there
-- directly after, or with
-- soft linebreak
b) sibling block
c) child block of the text (=grandchild of the block with {[[Tweet]]}}

added the following:


Error on local lint check

Environment

Qiskit Nature version: 218c7f9fc20fbe48e804162184960cbe0de2f37c
Python version: 3.8.8
Operating system: RHEL 8.5

What is happening?
Errors when running make lint.
How can we reproduce the issue?
make lint
python -m pylint -rn --ignore=gauopen qiskit_nature test tools
************* Module qiskit_nature.drivers.second_quantization.gaussiand.gaussian_log_result
qiskit_nature/drivers/second_quantization/gaussiand/gaussian_log_result.py:208:40: I1101: Module 'math' has no 'factorial' member, but source is unavailable. Consider adding this module to extension-pkg-allow-list if you want to perform analysis based on run-time introspection of living objects. (c-extension-no-member)
qiskit_nature/drivers/second_quantization/gaussiand/gaussian_log_result.py:248:31: I1101: Module 'math' has no 'sqrt' member, but source is unavailable. Consider adding this module to extension-pkg-allow-list if you want to perform analysis based on run-time introspection of living objects. (c-extension-no-member)
qiskit_nature/drivers/second_quantization/gaussiand/gaussian_log_result.py:298:31: I1101: Module 'math' has no 'sqrt' member, but source is unavailable. Consider adding this module to extension-pkg-allow-list if you want to perform analysis based on run-time introspection of living objects. (c-extension-no-member)
************* Module qiskit_nature.problems.second_quantization.lattice.lattices.hyper_cubic_lattice
qiskit_nature/problems/second_quantization/lattice/lattices/hyper_cubic_lattice.py:16:0: E0611: No name 'pi' in module 'math' (no-name-in-module)
************* Module qiskit_nature.problems.second_quantization.lattice.lattices.triangular_lattice
qiskit_nature/problems/second_quantization/lattice/lattices/triangular_lattice.py:16:0: E0611: No name 'pi' in module 'math' (no-name-in-module)

------------------------------------------------------------------
Your code has been rated at 9.99/10 (previous run: 9.99/10, +0.00)

make: *** [Makefile:43: lint] Error 2

What should happen?
No error.
Any suggestions?
No response

The CI is checking make lint for Python versions 3.7 through 3.10 on Ubuntu, Mac OS and Windows. So I assume that this is some problem in your local setup. Especially, given the fact that your pylint appears to be unable to resolve imports from the builtin math module.
Please try ensuring that your development tools are up-to-date:
python -m pip install -U -c constraints.txt -r requirements-dev.txt

If the error persists, please provide more details:

make sure that your virtual environment is active
pip list
maybe add some sanity output check to the make lint target like printing which python etc.

Thanks, I did run python -m pip install -U -c constraints.txt -r requirements-dev.txt and make sure my virtual environment was active and verify that make lint is using the correct python.


How do I make my logo bigger?

My logo looks too small in the header, how can I make it appear bigger? The site is at https://wrongsyntax.github.io

wow, thanks, I faced the same problem at first.

I'll make it configurable.

I'll make it configurable.

Thanks a lot.  Just wanted to use your template to build a tech blog and my background is not software engineering so it would be lovely if there is a more detailed guide.