Camerstream lost, but no connect retry from go2rtc

I have 3 cameras, one stream is lost. No Error in the log.
I see two tcp connections go2rtc to the left cameras.
If I open with go2rtc gui the missing on, nothing happens. ( Black screen :-) )
No logfile error, I see no tcp connections try to the missing camera.
Restart of go2rtc, all 3 cameras are working well.
Any Idea ?

You need to start with the go2rtc version and stream info.

Sorry, I am new in go2rtc, what mean  "go2rtc version and stream info."
"go2rtc version 1.9.4 (a4885c2) linux/amd64"

You can check stream from from go2rtc WebUI

I try to write it in my first comment.
All trys only with the go2rtc web at port 1984
0 Stream used at the third camera, one at camera 1 and 2. Web gui left side.
When I click on the right side on the stream link, the stream window open and no stream was displayed ( black ).
No Error log writen by go2rtc, no Network Connection displayed with netstat to the camera ip.
Restart go2rtc, stream link display the Stream instandly.

Stream info. And stream probe.

Same issue as stated here: https://github.com/AlexxIT/WebRTC/issues/631
The issue arised to me because of the webrtc 3.6.0 update, which comes with go2rtc 1.9.4.
I downgraded to webrtc 3.5.2 which has go2rtc 1.8.4, and i works flawlessly since a day with my reolink doorbell wifi.
With the new webrtc 3.6.0, every few hours a reconnect/progress circle is shown in front of the last picture, which freezed.
But i never reconnects.
How can i provide a log and help debug?

@AlexxIT 3.5.2 with go2rtc 1.8.4 works wihtout any reconnect issue since ~4 days.
So it seem there is an issue 1.9.4.
Is it possible for you to downgrade the included go2rtc to 1.8.4 until the issues with newer versions are sorted?

You can use any version you want. If you are sure it is compatible with the new integration version.
https://github.com/AlexxIT/WebRTC/blob/121d7558d0a2f1d19452f7b51a6237e048153528/custom_components/webrtc/utils.py#L28

I have the same issue with  1.9.4 recently update from 1.8.4  2 weeks ago
go2rtc version 1.9.4 (a4885c2) linux/amd64

Works fine with 1.8.4
api:
  origin: '*'
ffmpeg:
  h264/rk: -c:v h264_rkmpp_encoder -g 50 -bf 0
  h265/rk: -c:v hevc_rkmpp_encoder -g 50 -bf 0
hass:
  config: /config
log:
  format: text
rtsp:
  default_query: video
  password: CHANGEME
  username: frigate
streams:
  camera1: ffmpeg:rtsp://root:CHANGEME@192.168.xxx.yyy:554/stream=0#video=copy#audio=copy
  camera1-LD: ffmpeg:rtsp://root:CHANGEME@192.168.xxx.yyy:554/stream=1#video=copy#audio=copy
  camera2: ffmpeg:rtsp://root:CHANGEME@192.168.xxx.yyy:554/stream=0#video=copy#audio=copy
  camera2-LD: ffmpeg:rtsp://root:CHANGEME@192.168.xxx.yyy:554/stream=1#video=copy#audio=copy
webrtc:
  candidates:
  - 192.168.xxx.yyy:8555
  - stun:8555
  listen: :8555

Seems like the reconnection problem when using ffmpeg is pretty common. I think bug in v1.9.3 or v1.9.4

@AlexxIT just let us know which go2rtc version we should try to give you feedback and we can narrow down the problematic version.

Frigate uses v1.9.2 version

Just some curious thing!
I have downgraded a week ago to 3.5.2 which has go2rtc 1.8.4 in it.
Now i wanted to upgrade again to 3.6.0 and go2rtc 1.9.4 (current release) and ust opened the 1984 port on my HA maschine.
You know what... 1.9.4 is running with 3.5.2 !?!?

I dont know why, but it seems webrtc 3.5.2 runs without an issue with go2rtc 1.9.4.
So i will now upgrade to webrtc 3.6.0 with go2rtc 1.9.4, reboot my maschine, check port 1984 that go2rtc 1.9.4 runs and see how it goes.

Ok, so after upgrading to 3.6.0 with 1.9.4 the stream is gone over night.
I have now changed the util file to 1.9.2 and restarted GA but on port 1984 it says 1.9.4.
How can force a go2rtc downgrade?

I'll check this when have time.

thx, here are results of my tests with an reolink doorbell wifi cam.
I have always checked the go2rtc version with the webinterface running on port 1984.
On the following combinations the issue happens:
picture in HA freezes after few minutes, reconnect circle is spinning and reconnects fails

webrtc 3.6.0 with go2rtc 1.9.2
webrtc 3.6.0 with go2rtc 1.9.0

With the following combination it runs now for a few hours without an issue:
• webrtc 3.5.2 with go2rtc 1.9.4
Just let me know when i should test something or provide logs.

@AlexxIT updated my post above (tested with newer go2rtc versions). But sadly webrtc camera 3.6.0 has the issue for me, regardless which version of go2rtc.
Because HA 2024.11 has now native go2rtc implemented, i switched from webrtc camera to default dashboard live camera feed (which internally now uses go2rtc in HA). Will see how it goes...

+1
go2rtc 1.9.4 works, the issue is somehow caused by webrtc 3.6.
I am now with webrtc 3.5.2 modified to use go2rtc 1.9.4 and no reconnect issues.

Since using the HA internal go2rtc combined with default dashboard HA camera card, I did not had the issue again.
In parallel I am using a second go2rtc installation (via addon) so I can use the streams on my TV with pipup APK.
Working nice together.
So yes, the issue is webrtc camera 3.6.0.


Unable to extract http://www.le.com url

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2017.05.01. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[x ] I've verified and I assure that I'm running youtube-dl 2017.05.01

Before submitting an issue make sure you have:

[ ] At least skimmed through README and most notably FAQ and BUGS sections
[x ] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

youtube-dl.exe --verbose http://www.le.com/ptv/vplay/29207824.html
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', 'http://www.le.com/ptv/vplay/29207824.html']
[debug] Encodings: locale cp936, fs mbcs, out cp936, pref cp936
[debug] youtube-dl version 2017.05.01
[debug] Python version 3.4.4 - Windows-2012ServerR2-6.3.9600
[debug] exe versions: none
[debug] Proxy map: {}
ERROR: An extractor error has occurred. (caused by KeyError('playstatus',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp0io2aq9r\build\youtube_dl\extractor\common.py", line 429, in extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp0io2aq9r\build\youtube_dl\extractor\leeco.py", line 149, in _real_extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp0io2aq9r\build\youtube_dl\extractor\leeco.py", line 125, in _check_errors
KeyError: 'playstatus'
Traceback (most recent call last):
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp0io2aq9r\build\youtube_dl\extractor\common.py", line 429, in extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp0io2aq9r\build\youtube_dl\extractor\leeco.py", line 149, in _real_extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp0io2aq9r\build\youtube_dl\extractor\leeco.py", line 125, in _check_errors
KeyError: 'playstatus'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp0io2aq9r\build\youtube_dl\YoutubeDL.py", line 760, in extract_info
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp0io2aq9r\build\youtube_dl\extractor\common.py", line 442, in extract
youtube_dl.utils.ExtractorError: An extractor error has occurred. (caused by KeyError('playstatus',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Thanks for the report. le.com videos will be fixed in the next version.


Did not show chatbot-ui windows

after showing this, nothing happens, and no new windows opened.

the Chinese part is when i "ctrl+c", it asks whether to end（y/n）

i made a mistake, it should be opened in a browser


More tag chips visible in "quick tags" section

When tag chips in "quick tags" overflow the screen border, we should make them denser by using short versions.
Example:
    Data model:              [quick tags]: [english][music][literature][cars][travelling]...
    What user is seeing:     [quick tags]: [english][music][lite  | screen border
    What user should see:    [quick tags]: [eng][mus][lit][car].. | screen border

Maybe add a toggle switch between the full and short version of the tags?

I think, we should add such a preference in the Settings screen (#77).


Add cocoapod spec

Update project_before to be a blank project (no reference to cococapods/carthage)
Fix #89
Fix #72

I made a new target using the example app and configured it via the gem.
diff --git a/Demo/EarlGreyExample/Podfile b/Demo/EarlGreyExample/Podfile
index 50bb01a..4c78682 100644
--- a/Demo/EarlGreyExample/Podfile
+++ b/Demo/EarlGreyExample/Podfile
@@ -38,6 +38,13 @@ target TEST_TARGET_SWIFT do
   pod 'EarlGrey'
 end

+target 'NewGem' do
+  project PROJECT_NAME
+
+  inherit! :search_paths
+  pod 'EarlGrey'
+end
+
 post_install do |installer|
   require 'earlgrey'
   # For each test target, you need to call the EarlGrey script's edit method once.
@@ -45,4 +52,6 @@ post_install do |installer|
   configure_for_earlgrey(installer, PROJECT_NAME, TEST_TARGET, SCHEME_FILE)
   # For the 'EarlGreyExampleSwiftTests' target.
   configure_for_earlgrey(installer, PROJECT_NAME, TEST_TARGET_SWIFT, SCHEME_FILE_SWIFT)
+
+  configure_for_earlgrey(installer, PROJECT_NAME, 'NewGem', 'NewGem.xcscheme', {swift:true})
 end

everything appears to be working.

I got this error on trying out the new gem that isn't present on doing a clean pod install on the EarlGreyExample project. Are you seeing this as well?
Analyzing dependencies
Downloading dependencies
Using EarlGrey (1.0.0)
Generating Pods project
Checking and Updating EarlGreyExample for EarlGrey.
[!] An error occurred while processing the post-install hook of the Podfile.

[!] The plist file at path `/EarlGrey/Demo/EarlGreyExample/EarlGreyExample/project.pbxproj` doesn't exist.

@tirodkar try gem uninstall -aIx earlgrey; gem install earlgrey

@tirodkar any update? did the gem command fix the issue?

gem uninstall -aIx earlgrey; gem install earlgrey

The command fixed it. I'm testing this out with other open source apps as well, which is taking a little bit of time for setup.

This looks good right now. I'll merge it in today after brushing one last time through the code. Thanks.

cool!

I did a partial review of the flow for CocoaPods with a test project and the demo and it worked fine. I haven't checked the Carthage changes yet. LGTM for the CocoaPods part.

Similar to the Carthage before/after project, do you think it would be necessary to add in a CocoaPods test proj as well?

Similar to the Carthage before/after project, do you think it would be necessary to add in a CocoaPods test proj as well?

I already have before/after for both Carthage & CocoaPods.
fixtures
   ├── carthage_after
   ├── cocoapods_after
   └── project_before

Project
Description

project_before
Baseline unconfigured project. Not configured with either cocoapods or carthage.

carthage_after
Project configured with carthage.

cocoapods_after
Project configured with cocoapods.

Fixed merge conflict.

The Pod install ran fine with simple test projects that I ran this on. This seems to be fine from my side, any issues I experienced were because of https://github.com/google/EarlGrey/issues/125.

LGTM from my end. @sid-github if you don't have any comments @tirodkar let's merge this in. Thanks.

Fixed.

Awesome, this PR LGTM.

a teeny tiny comment. LGTM! Please merge right after the comment is addressed.

Updated.


Add option to provide location information when listing tests

Description
When you run swift --list-tests it just provides a list of tests. It would be really useful for the Visual Studio Code swift extension if we could have an option to output more information about the tests, specifically which file they are in and location within that file.
eg
swift --list-tests --extended could return a JSON file
[
   {
        "name": "MyModuleTests/TestName/testName",
        "file": "Tests/MyModuleTests/TestName.swift",
        "line": 45
    },
    {
    ...
    },
]

Expected behavior
No response
Actual behavior
No response
Steps to reproduce
No response
Swift Package Manager version/commit hash
No response
Swift & OS version (output of swift --version && uname -a)
No response

Closing this in favour of https://github.com/apple/sourcekit-lsp/issues/611


Extend the output format with a tree view

Currently, the output format of checkpointctl is in a table format. However, due to the limitations of horizontal space and the need to display multiple checkpoints, it would be beneficial to add a tree view format. This offers several advantages:

The tree format takes advantage of unlimited vertical space, which is more suitable for displaying detailed information.
The tree format can be used with multiple checkpoints, allowing for the presentation additional details for each checkpoint.
A built-in terminal pager, (e.g: systemctl status), would enhance the usability of the output.

Here's an example of how the output could look:
containername
├── IMAGE: registry/name:latest
├── ID:<PHONE_NUMBER>34
├── RUNTIME: runc
├── CREATED: 2023-05-19T08:44:58.018444733Z
├── ENGINE: CRI-O
├── IP: <IP_ADDRESS>
├── CHECKPOINT SIZE:
├── ROOT FS DIFF SIZE:
├── NAMESPACES:
│   ├── UTSNS
│   │   ├── NODENAME: hostname01
│   │   └── DOMAINNAME: (none)
│   └── IPC
└── PROCESSES
    └── [1]  bash
        ├── [7]  counter.py
        └── [8]  tee

Suggested by @adrianreber

It might be useful to to also be able to render the out in JSON format (e.g., similar to podman inspect). This would eable easier integration with other tools to further process the output of checkpointctl.


switching phone on adroid

I use the authenticator app on Android, mfa is required for my work, we use office products so I want with a Microsoft solution.
I'm not getting a new phone (another android) and need to move the app over, how do I do this? Why is there a method for doing for ios and nothing for android? I'm missing something right?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 8b52a210-1be6-4e5f-d95c-8ea7b87919ca
Version Independent ID: 02a43ebb-7471-d7ff-4f7e-84c9f7a66326
Content: Backup and recover with Microsoft Authenticator app - Azure Active Directory
Content Source: articles/active-directory/user-help/user-help-auth-app-backup-recovery.md
Service: active-directory
Sub-service: user-help
GitHub Login: @eross-msft
Microsoft Alias: lizross

@nhoj01
Thanks for your feedback! We will investigate and update as appropriate.

@eross-msft are we missing documentation for doing this with Android, or is there no way to do this with Android?
I'm not sure whether this should be a product feedback or doc feedback.

@MarileeTurscak-MSFT  We currently don't offer an Android solution; however, this is very actively being worked on and should be released sometime in the near future, though I have no specific date as this moment.

Thanks @eross-msft and @nhoj01 ,
I heard the same from the product group, that they are actively working on this and that a release is pending in the near future.
@nhoj01 you can check the release notes for updates. https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/whats-new
We will proceed to close this out but will update the comments when this feature is launched.

You can also check for updates on aka.ms/identityblog


add sequelize backend

@tschellenbach @nparsons08 do you guys have any code example to share about this? Even something generic and not yet specific to sequelize would be nice

https://github.com/sequelize/sequelize
should be pretty similar to our support for Waterline. Did anybody ask for this?

@tschellenbach @tbarbugli a Sequelize example would be helpful for @colinramsay and I

I have a little bit of experience with Sequelize but don't have time for this right now. It could also a nice community contribution if somebody would like to submit a PR.

@dwightgunning Could you at least provide some gguidance on how would one go about adding more 3rd-party backend orm support.
+1 for Sequelize but I would like to try myself for FaunaDB and TypeORM.


[stable/ambassador] Prometheus exporter resource configuration support

What this PR does / why we need it:
There is no way to configure the prometheus exporter resource in the current chart. This will give the support for adding resource requests and limits to the prometheus exporter as well
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/ok-to-test
/assign

@Flydiverny review changes are updated

/lgtm


Secret Manager Config Source

This is a proof of concept of a Secret Manager config source for Quarkus.
You can see how it works in application.properties where users may directly load secrets into application properties like this:
# You can load secrets from Google Cloud Secret Manager with the ${sm//<SECRET_ID>} syntax (defaults to latest version).
# Other formats will be provided and documented such as: ${sm//project_id/secret_id/version}
my.database.password=${sm//integration-test}

Based on the PR #77 by @madsop
We can wait for that PR to be merged in first and then I can clean this one up.
FYI - @meltsufin

@dzou the other PR is merged, I'm waiting for the rebase to review this one ;)

@dzou the other PR is merged, I'm waiting for the rebase to review this one ;)

Great, I'll get on this one shortly!

Just did the rebase.
This implementation adds a config source extensions via the "SmallRye" framework, which is what Quarkus uses to parse the application.properties.
Docs on ConfigSource and ConfigSourceFactory: https://github.com/eclipse/microprofile-config/blob/master/spec/src/main/asciidoc/configsources.asciidoc
Right now i'm working on an issue with the SecretManagerConfigSourceFactory. This appears to be incompatible with unit tests because the SecretManagerClient is not provided via @Inject but manually created. I'm trying to figure out how to access the application context's beans from that class, but am a little stuck.
We could also introduce a property like quarkus.gcp.secretmanager.enabled=false to disable the secret manager config source loading for unit tests (or if the user doesn't want this feature).

This appears to be incompatible with unit tests because the SecretManagerClient is not provided via @Inject but manually created

You can use Arc (or CDI) to programmatevely retrieve the SecretManagerClient from the bean container:
From an extension we often directly access Arc, the CDI implementation.
Arc.container().instance(SecretManagerClient.class)

But be careful that config is init in a very early stage.

Thanks for the tip. Should be ready for review now.

Apologies for the delay, thank you for the thorough review. I will respond to the feedback tomorrow!

You support different ways to define the secrets:

sm://myProject/mySecret/myVersion
sm://projects/myProject/secrets/mySecret/version/myVersion

I wonder if the second form is really needed? Or maybe this is already used on other framework and you propose it for consitence sake ?

Good question -- Yes the long form sm://projects/myProject/secrets/mySecret/version/myVersion is useful to have because it is the fully qualified resource name that Secret manager uses (if you call SecretVersionName.toString() this is the resulting string form you get). I think this is useful to have if somehow there is a use-case where the user directly copies and pastes this fully-qualified name in.

@radcortez this PR adds a config source from Google Cloud Secret Manager, can you have a look at the MP Config part ?

Sure!

LGTM.
I'll merge it next week, I want to play with it a little before merging ;)

Sounds good!

@dzou running the main integration test via mvn quarkus:dev with my GCP project leads to this exception being thrown:
java.io.IOException: Scopes not configured for service account. Scoped should be specified by calling createScoped or passing scopes to constructor.
	at com.google.auth.oauth2.ServiceAccountCredentials.refreshAccessToken(ServiceAccountCredentials.java:402)
	at com.google.auth.oauth2.OAuth2Credentials.refresh(OAuth2Credentials.java:157)
	at com.google.auth.oauth2.OAuth2Credentials.getRequestMetadata(OAuth2Credentials.java:145)
	at com.google.auth.oauth2.ServiceAccountCredentials.getRequestMetadata(ServiceAccountCredentials.java:603)
	at com.google.api.gax.rpc.internal.QuotaProjectIdHidingCredentials.getRequestMetadata(QuotaProjectIdHidingCredentials.java:64)
	at com.google.auth.Credentials.blockingGetToCallback(Credentials.java:112)
	at com.google.auth.Credentials$1.run(Credentials.java:98)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:834)

@dzou running the main integration test via mvn quarkus:dev with my GCP project leads to this exception being thrown:
java.io.IOException: Scopes not configured for service account. Scoped should be specified by calling createScoped or passing scopes to constructor.
	at com.google.auth.oauth2.ServiceAccountCredentials.refreshAccessToken(ServiceAccountCredentials.java:402)
	at com.google.auth.oauth2.OAuth2Credentials.refresh(OAuth2Credentials.java:157)
	at com.google.auth.oauth2.OAuth2Credentials.getRequestMetadata(OAuth2Credentials.java:145)
	at com.google.auth.oauth2.ServiceAccountCredentials.getRequestMetadata(ServiceAccountCredentials.java:603)
	at com.google.api.gax.rpc.internal.QuotaProjectIdHidingCredentials.getRequestMetadata(QuotaProjectIdHidingCredentials.java:64)
	at com.google.auth.Credentials.blockingGetToCallback(Credentials.java:112)
	at com.google.auth.Credentials$1.run(Credentials.java:98)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:834)

I see. I got the same error when trying with a service account. It seems like we have to add the GCP OAuth2 scopes in certain cases with service accounts. PR here: https://github.com/quarkiverse/quarkus-google-cloud-services/pull/84

I merged #84, can you rebase onto master ?

I merged #84, can you rebase onto master ?

Done!

@dzou thanks, it's OK now.
Can you squash your commits (at least except the merge one) please ?

Can you squash your commits (at least except the merge one) please ?

@loicmathieu What's your stance of the "squash and merge" option on GitHub? We've been using it on our repos forever and it works great for us allowing us not to worry about squashing and rebasing on PRs.

@meltsufin

What's your stance of the "squash and merge" option on GitHub?

This is a good question ;)
I think rebase and merge (the default) is better if the developer have a clean history as it keep the history (important for complex features). Squash and merge will create a single commit on the base branch but loosing the original commits (messages and all) so the history will be clear but will lack informations.
I didn't have a strong opinion, on Quarkus repo we enforce squasing the commits and using rebase and merge so I do the same on my own repo by habbit.

Squash and merge will create a single commit on the base branch but loosing the original commits (messages and all) so the history will be clear but will lack informations.

If you're doing the merge on GitHub it allows you to edit the commit before it's made. So, we usually take that opportunity to cleanup the commit message before it goes in.

No worries, let me do the rebase. I have to learn how to do it anyways :smiley:

Ok, should be good now. Sorry I didn't realize this is what you mean when you asked for rebase; will remember moving forward.

Thanks I'll merge it now.


Feat/oauth2 daos.lua & api.lua to new db

This change has some previous groundwork, then the commit itself which deals with oauth2, and then some cleanup. Each part has its own separate commit, with explanations. I recommend reviewing the PR commit-by-commit.

Reviewed commit-by-commit. I think the overall port of Oauth2 looks good! I think the fix for the Cassandra migrations is the only blocker.

@kikito Regarding the "sneaky" loop, my suggestion then is to add a comment above the pairs() loop with something like
-- If the daos list is declared as an array, we assume below that pairs()
-- will traverse them in order and initialize the schemas
-- such that foreign field relationships are resolved correctly

...or use this order-safe iterator instead? :) (couldn't resist! (untested of course) )
local function each_dao(daos)
  local phase = 1
  local ak = 1
  local hk = next(daos)
  return function()
    if phase == 1 then
      local v = daos[ak]
      ak = ak + 1
      if v == nil then
        phase = 2
      else
        return v
      end
    end
    --- phase == 2:
    while type(hk) == "number" then
      hk = next(daos, hk)
    end
    if hk == "tables" then
      hk = next(daos, hk)
    end
    v = daos[hk]
    hk = next(daos, hk)
    return v
  end
end


NavigationView: fix space reservation for top and bottom footer

Description

This PR makes Navigation View free the space for top and bottom footer if it's not being used.
Motivation and Context

Previously, Navigation View would reserve space for top and bottom footer even if they're not being used. It also will draw Separator line between main items and bottom footer even when footer is not present.
This PR addresses that.
NOTE: This PR only fixes the space reservation and not properly adjusts all the margins/paddings to correctly display all elements. It will be addressed in another PR.
How Has This Been Tested?

Manually.
Screenshots (if appropriate):

With toggle, back, autosuggestbox and settings on:

Without:

/azp run

Can I close #4193 then since it aims at doing the same?

@chingucoding I didn't know you've already done it.. We can go with your solution if you can also remove space reservation for top footer when toggle or back button is not present?:)

@beervoley Can you share repro code, I'm not sure what you are referring too.

/azp run

@chingucoding it's just a simple NavigationView without back or toggle button:

this space on top shouldn't be reserved
check my changes in this PR, it's about removing minHeight again :)

@chingucoding I didn't know you've already done it.. We can go with your solution if you can also remove space reservation for top footer when toggle or back button is not present (look at my changes) ?:)

If we close this PR, I would copy those changes into my PR of course.

converted to draft because @chingucoding has PR open with tests already. It only needs couple of small fixes.

@chingucoding I didn't know you've already done it.. We can go with your solution if you can also remove space reservation for top footer when toggle or back button is not present (look at my changes) ?:)

If we close this PR, I would copy those changes into my PR of course.

yes, that would be great. Once you add the changes and we get the pipelines pass, I will close this PR :)

Closed because this bug will be addressed in https://github.com/microsoft/microsoft-ui-xaml/pull/4193


Interface and EqsysInitializer mismatch with ion temperature

When using non-zero ion temperatures the interface seems to miss cases where a temperature profile is given and density is constant, which leads to an unhelpful error message from the kernel.
Also the EqsysInitializer does not output an error for N_i and W_i when the ion density structure has changed between simulations.

It's unclear if this is still an issue...


404 when clicking on "chat on gitter" badge in README

Just gonna remove it, I never look in it TBH. Can't remember who put it there.


Provide type/schema for the obo_synonym attribute of Term

This has some useful info (e.g. which synonyms are common names in ncbitaxon), and we are now using it in AHIDA.

Closed via #13


MaxDOP_Configuration_Check.sql gives me an incorrect result

Hi
I try some run on different server and found that the result isn't correct.
I got:
@@SERVERNAME: MSSQL01
@EffectiveMaxDOP: 2 (YES TRUE)
@NumaNodeCount: 1 (NO I GOT 2 NUMA... see the image)
SELECT * FROM sys.dm_os_nodes

but from SSMS I got a single one?

Which is the correct?
I see you count distinct on this...

And also from server log:

SQL Server detected 4 sockets with 4 cores per socket and 4 logical processors per socket, 16 total logical processors; using 16 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
Automatic soft-NUMA was enabled because SQL Server has detected hardware NUMA nodes with greater than 8 physical cores.

@LogicalProcessorPerNumaNodeCount: 16 (NO ARE 8... see the above)
MaxDOP is already within recommended range: 8 (NO IT's 2)
I'm little confused,
Thanks Alen

Hi @acappelletti , thank you for your submission.
Please note that the calculation is NOT done per node_id, but it's done per memory_node_id. That's the one that matters.
That's also why in SSMS you get a single NumaNode0 in the processor tab. You only have one in your case.

Yes, @acappelletti , that's correct.
The "memory_node_id" is the physical memory slot which is what matters.


Added trading as to thank you and view submission

There is a requirement to show trading as on the thank you and view submission page .
How to review
Launch any survey from go launcher with 2 test cases 1 with a trading as string set to something different to ru , and with zero length string as trading as . if there is a trading as it will be displayed on the thank you page after ru name in parenthesis . If there is an empty string then there should be no
parenthesis. Repeat for a survey that show view submission and validate same cases in the view submission page. e.g test_view_submitted_response

LGTM


"Auto-add bundle components to orders, post-purchase": update for line item groups

A merchant wrote in:
https://tasks.mechanic.dev/auto-add-bundle-components-to-orders-post-purchase

in your template you look for bundles with bundle_parent_sku but in new native shopify bundles they are using line-item-group
https://shopify.dev/docs/api/admin-graphql/2024-07/objects/LineItem#field-lineitemgroup
can you support with an update for this please?

using new native bundles shopify only passes down the line item sku in the order json, and not the parent bundle sku ( line-item-group).

@tekhaus Can you investigate?

I am fairly certain that this would need to be a completely separate task, to work with native bundles versus bundles configured in the task as is done here.
I'll investigate further and post back here.

Native bundles are entirely controlled by whichever bundles app the merchant has installed. When a native bundle is on an order, then it gets expanded automatically in the cart/checkout to show the components, and those appear as line items on the resulting order, so there is no need to add them post-purchase.
Perhaps further qualification is needed from the merchant on the exact use case, since the one covered by the task already seems to be handled natively.


Report definitions only working correctly in the Private tenant space [BUG]

When creating a report definition in any other tenant space that is not private, the report definition will download the wrong dashboard.
One is able to create a report definition in any tenant space successfully, but when downloading the generated report, it downloads the wrong thing.

The above image shows the pdf that downloaded when I tried to download the report created in the report definition of the Admin tenant space. It generates the above because the dashboard that I tried to download is not available in the private tenant space, hence it cannot find it. Any advice if there is a fix for this?

My user has reports_full_access.
he URL is also changed when clicking on the Dashboard under source that is created via the report definition:
Suppose to look like this:
http://<IP_ADDRESS>:5601/app/dashboards?_**security_tenant=admin_tenant**_#/view/7adfa750-4c81-11e8-b3d7-01146121b73d?_g=(time:(from:'2022-11-09T06:03:14.060Z',to:'2022-11-10T06:03:14.060Z'))&_a=(description:'Analyze%20mock%20flight%20data%20for%20OpenSearch-Air,%20Logstash%20Airways,%20OpenSearch%20Dashboards%20Airlines%20and%20BeatsWest',filters:!(),fullScreenMode:!f,options:(hidePanelTitles:!f,useMargins:!t),query:(language:kuery,query:''),timeRestore:!t,title:'%5BFlights%5D%20Global%20Flight%20Dashboard',viewMode:view)
Mine looks like this:
http://<IP_ADDRESS>:5601/app/dashboards?_**security_tenant=POST**_#/view/7adfa750-4c81-11e8-b3d7-01146121b73d?_g=(time:(from:'2022-11-09T06:03:14.060Z',to:'2022-11-10T06:03:14.060Z'))&_a=(description:'Analyze%20mock%20flight%20data%20for%20OpenSearch-Air,%20Logstash%20Airways,%20OpenSearch%20Dashboards%20Airlines%20and%20BeatsWest',filters:!(),fullScreenMode:!f,options:(hidePanelTitles:!f,useMargins:!t),query:(language:kuery,query:''),timeRestore:!t,title:'%5BFlights%5D%20Global%20Flight%20Dashboard',viewMode:view)
Pay attention to what happens with the security tenant part.

duplicate of #535


Contribution of the QoD-API spec v0.8.0

PR for the issue #42
The QoD-API spec 0.8.0 contains following changes based on QoD API-spec v0.1.0:

Two APIs (latency & throughput) combined to one, 0.8.0 replaces 0.1.0
ueAddr (ipv4) changed to ueId (ipv4, ipv6, msisdn, externalid)
asAddr (ipv4) changed to asId (ipv4, ipv6)
Portspec contains now a schema
Protocol (in & out) removed
QoS profiles renamed
Basepath changed
Some formal changes/fixes

The separated API specs (latency and throughput) have been removed.

If you remove the references to protocolIn and protocolOut there is no longer any reference to the protocol. What protocol are you taking into account in this case ?

@patrice-conil

If you remove the references to protocolIn and protocolOut there is no longer any reference to the protocol. What protocol are you taking into account in this case ?

All protocols are allowed in both directions

these are good changes. Completely agree with the need for merging QoS and QoD API spec.
Thank you for updates.
Few inputs listed below

parameter name update suggestion to make it more developer friendly
change "asId" to "applicationServerEndpoint"

Make uePorts part of ue ID
Make asPorts part of applicationServerEndpoint(new name for asId)
Sample:
"ueId": {
"externalId"<EMAIL_ADDRESS>"msisdn": "123456789",
"ipv4addr": "<IP_ADDRESS>/24",
"ipv6addr": "2001:db8:85a3:8d3:1319:8a2e:370:7344",
"port": {
"ranges": [
{
"from": 5010,
"to": 5020
}
],
"ports": [
5060,
5070
]
}
},
"asId": {
"ipv4addr": "<IP_ADDRESS>/24",
"ipv6addr": "2001:db8:85a3:8d3:1319:8a2e:370:7344",
"uePorts": {
"ranges": [
{
"from": 5010,
"to": 5020
}
],
"ports": [
5060,
5070
]
}
},
makes it clear which ports are associated to what and nice way to group related data.

Introduce fallbackQos incases where preferred qos setting fails, rather than default, we can offer an alternate option as supported by SCEF.

update response message for 201 response code of POST /session to just provide SessionId and Status instead of passing all the input data.

In the GET /sessions response, lets add a status field to let the caller of the API know of the current status of the session.
Status could be one of the following:

pending_active
active
failed
deleted
pending_delete
terminated

The API spec does not support PUT API. Any specific reason for not having it?
What happens if some parameter as passed in create session changes like, application server ip or something else?

Why not send notification for all status change events rather than just SESSION_TERMINATED?

@emil-cheung within call on Friday Joachim mentioned that you have done a review with your colleagues. Would be great if you add your comments and/or approval.

@emil-cheung

the idea was that you pass all IDs you have and the service can take, what it needs. It means different implementations can need different identifier, but the API call can remain unchanged
I think using a free string without a discovery capability is just a "guessing game"

@emil-cheung
I think we may need a discussion on how to handle dual-stack UEs. Issues I see are:

The API consumer may want both IPv4 and IPv6 flows prioritised, or only one
If the API consumer only wants the IPv4 flow prioritised, but all they know is the private address, then they will anyway need to provide some additional parameter to identify the UE (such as MSISDN)

Restricting the UE identifier to a single parameter would rule out these scenarios. If an API consumer supplies multiple inconsistent parameters, then clearly the API should return an error - it is not for the API provider to guess what the API consumer really wanted. If the API consumer does not want to risk such rejection, then the API definition allows them to specify only a single parameter.

@emil-cheung

I guess this point is answered by @eric-murray and @akoshunyadi ... multiple identifier are allowed and make sense in certain scenarios, the documentation should explain this. If the the API provider detects inconsistencies it will reject the request.
Forward compability for upcoming changes would be great but at the current point we have several issues open which will anyway bringn breaking changes, e.g. the discovery function (#7). Therefore I wouldn't introduce a wildcard now into the qos parameter but later a solution which can be used in conjunction with the discovery function.

@emil-cheung Are your comments resolved by the discussion?
@akoshunyadi Can you please your branch with HEAD of main so that it is possible to merge without conflict?

Hi,
Sorry, because of some technical issues I had to create new PR for the 0.8.0
https://github.com/camaraproject/QualityOnDemand/pull/54
KR
From: Herbert Damker @.>
Sent: 2022. október 19., szerda 11:18
To: camaraproject/QualityOnDemand @.>
Cc: Hunyadi, Akos @.>; Mention @.>
Subject: Re: [camaraproject/QualityOnDemand] Contribution of the QoD-API spec v0.8.0 (PR #43)
@emil-cheunghttps://github.com/emil-cheung

I guess this point is answered by @eric-murrayhttps://github.com/eric-murray and @akoshunyadihttps://github.com/akoshunyadi ... multiple identifier are allowed and make sense in certain scenarios, the documentation should explain this. If the the API provider detects inconsistencies it will reject the request.
Forward compability for upcoming changes would be great but at the current point we have several issues open which will anyway bringn breaking changes, e.g. the discovery function (#7https://github.com/camaraproject/QualityOnDemand/issues/7). Therefore I wouldn't introduce a wildcard now into the qos parameter but later a solution which can be used in conjunction with the discovery function.

@emil-cheunghttps://github.com/emil-cheung Are your comments resolved by the discussion?
@akoshunyadihttps://github.com/akoshunyadi Can you please your branch with HEAD of main so that it is possible to merge without conflict?
—
Reply to this email directly, view it on GitHubhttps://github.com/camaraproject/QualityOnDemand/pull/43#issuecomment-1283690980, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQF3B2KZCTKPFMVHFXWKUUTWD64FFANCNFSM6AAAAAAQR3A5KY.
You are receiving this because you were mentioned.Message ID: @.***>


⚠ ClamAV has degraded performance

In e2f07e9, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 191 ms

Resolved: ClamAV performance has improved in 504c84d.


restricted_nameservers resolution fails when --accept-routes is false

Why
This request is for when --accept-routes is false the restricted_nameservers: should not be used.
To me, it's reasonable that restricted_nameservers are DNS servers that are hosted on a private network. When using --accept-routes it makes sense that you can expect that you're on the private network and should have access to the restricted DNS hosts.
If --accept-routes is false, you want to be on the "raw" Internet, either from an exit node or from your current connection. using restricted_nameservers here doesn't make sense as it fails in my example below.
Description
I have Split DNS setup:
dns_config:
  nameservers:
    - <IP_ADDRESS>
    - <IP_ADDRESS>
  restricted_nameservers:
    example.ca:
      - <IP_ADDRESS>

Internal to the <IP_ADDRESS>/24 network, example.ca will resolve to <IP_ADDRESS>
external to the <IP_ADDRESS>/24 network, example.ca will resolve to $Public_IP
When I connect to an exit node and I'm away from the <IP_ADDRESS>/24 network, I use tailscale up --login-server=https://headscale.example.ca --exit-node=<IP_ADDRESS> --reset This does not include a route to <IP_ADDRESS> so any DNS resolution for example.ca will fail. I'm looking for a solution that will allow me to continue to resolve example.ca. My suggestion is above but anything that works would be fine.

I am not so sure if this is good idea, what if you never use subnet gateways but want another tailscale node to be your nameserver?

Why not put the tailscale node as a nameserver instead of a restricted_nameserver in that case @sjansen1?
When you connect to the tailscale network all of the tailscale nodes will be available (assuming no ACLs) so putting one as the nameserver shouldn't be a problem as far as I understand it.
Do you have any suggestions for the problem I'm having? if --accept-routes is false DNS fails for my restricted_nameservers because they're on a private IP and reslove private addresses. I'd like the option to resolve the public IPs.

Sorry i have no idea for a solution because i use subnet routers for reaching out to our nameservers. I have different problems like tailscale is unable to bootstrap (start) if required nameserver are in a network that is provided over tailscale and the person is present at the location where the subnets are, but thats something different i am struggle with.


attach userStakeBalance to "staking" instead of the pool

currently the pool as a field called "userStakedBalances[]" which is wrong. It should be attached to the "staking". In addition, if we are going to introduce aura gauges this will also help make the distinction

Discussed with FE team:
The GqlPool model should still have userWalletBalances[] and userStakedBalances[] where the userStakedBalances[] are balances from the "preferred" gauge only.
Internally, we should still attach the stakedBalances[] to the staking object but attach it to the pool when loading. Maybe we also need to expose it on the staking object, but not yet.


Disable this test on Windows; it seems to not progress

I assume there's a common underlying problem for this and a lot of other concurrency tests that are disabled on Windows.

@swift-ci Please smoke test

@swift-ci Please smoke test macOS


test PR with Github API

Please pull this in!

Docs Build status updates of commit 0291cd2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

node-azure-tools.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[BUG]

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[ ] I did not answer truthfully to all the above checkboxes.

Bloxstrap Version
v2.8.1
What problem did you encounter?

Bloxstrap Log
N/A

nvm i realized i downloaded the wrong version


Fix Stack so that it appears correctly in StackSwitcher, etc

Summary
I am currently in the process of migrating from relm 0.4 to 0.5 and Stack is not displaying correctly.
This behavior does not seem to be documented in GTK4, but it appears that StackPage does not appear in StackSwitcher or StackSidebar unless the title is specified using the add_titled method. Therefore, StackPageInfo should be used as in relm 0.4.
Checklist

[x] cargo fmt
[x] cargo clippy
[x] cargo test
[x] updated CHANGES.md

Since I am a non-English speaker, please make appropriate changes to the wording I have added to CHANGES.md

Looks good, but I would really like to avoid such a workaround solution. The returned widget should give you all you need to set the title of the page...
Arguably, the bug is not on Relm4's side. I understand your motivation, but I'm hesitant to merge this, especially since this a breaking change.

Hmmm. I certainly feel differently about handling this issue on the part of Relm4.
https://relm4.org/book/stable/component_macro_reference.html?highlight=return#returned-widgets
You are referring to this macro, right?
Does this approach allow for dynamic addition of items using FactoryVecDeque?

Ah, I finally figured out how to use the returned_widgets argument. Thanks!


Seperating Racial Categories

@AaronGullickson
Should I separate Alaskan Natives from the AIAN category? I can do it but I am afraid that the sample size might be too small

@matthew-guerra You will not have a big enough sample size to separate Alaskan Natives.


[Form Provider Refactor] PrivateNotesEditPage

Coming from https://github.com/Expensify/App/issues/25397#issuecomment-1743272245, we created a new Form provider that works with functional components and we need to refactor all usages of the old Form component.
This issue is specific to refactoring src/pages/PrivateNotes/PrivateNotesEditPage.js
cc @kowczarz @cdOut
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~019146cfb545848865
Upwork Job ID:<PHONE_NUMBER>782385152
Last Price Increase: 2023-10-19

SWM will work on this, no need for a proposal

Hello! I'm Kamil Owczarz from Software Mansion, the expert agency and I would like to work on this task.

@kowczarz is working on other forms at the moment. We'll get to this one soon!

@luacmartins would it help to bump this to weekly in the meantime?

@peterdbarkerUK I'm finishing the pr, it should be ready in following hours

Let's keep this daily for now!

No regression tests or payments needed, I'm officially a full-blown bureaucrat. I'm sure my grandparents would be proud of me.
Thanks for the work here guys ;)


Handle duplicate passes in the MLIR explorer.

This commit is intended to address https://github.com/metagraph-dev/mlir-graphblas/issues/21 .
Additionally, this commit also removes the pinned version number for black in our environment yaml files.

Pull Request Test Coverage Report for Build 687472267

0 of 38 (0.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-1.4%) to 59.225%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

mlir_graphblas/explorer.py
0
38
0.0%

Files with Coverage Reduction
New Missed Lines
%

mlir_graphblas/explorer.py
1
0%

Totals

Change from base Build 687264271:
-1.4%

Covered Lines:
382

Relevant Lines:
645

💛  - Coveralls


Track 'n' Trace

If we carry an ESP sniffer around all day, and it logs all the signals that it finds, then that is some kind of record of all of the people that we have been near to, or at least, all of those who are broadcasting a WiFi (or Bluetooth?) signal, which, given the number of folk with WiFi enabled phones is probably a reasonable proportion.
While that information is not a lot of use on its own as a track and trace system, it could possibly be the beginnings of one...

This area is for reporting issues. I don't see any in your comment.

This area is for reporting issues. I don't see any in your comment.

So where is the area for raising discussions?
Though if you can't see any issue in a deadly global pandemic, you're probably not worth discussing things with.


Update manage-default-network-access-policies-virtual-machines.md

Update to leverage SdnDiagnostics module rather than powershell script to configure port profile

@alkohli

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


[UI] Launchscreen

Avoid duplicates

[x] This issue has not already been raised before
[x] If you are proposing a new feature, please do so in CWA-Wishlist

Suggested Enhancement

The launch time of the app is quite low, but in certain circumstances, it can happen that the launch takes some seconds. To improve the user journey from the beginning on, I would add the CWA logo to the launch screen. Maybe just copying the layout and style of the privacy protection window. A top up would be to add the navbar in the launchscreen, this is a little bit „old“ practice, but maybe it fits. Currently it is just blank and not really „pretty“.

Thanks for this suggestion. We have a similar issue for Android devices, so we'll take it up as a wishlist item to come up with a proper load screen in case loading the app takes longer than expected.


Add JSON Serialization for GateTabulation.

This is useful for precomputing the GateTabulation for Quantum Volume metrics.

@mpharrigan would you be able to take a look at this guy, please?

Sounds good, thanks! AFAICT the test failure is unrelated to this change...
Out of curiosity, outside of Cirq what should repr be used for? Debugging info?

As far as I understand it repr should give you some idea of what type of object you're dealing with while str tells you more about the data within


Cannot run docker compose

Hi,
Thank you for your upload.
When I installing the docker (through the installation script you provided), it throws some warnings and errors:
Creating example_postgres_1
ERROR: Invalid volume spec "db/postgres-setup.sql/docker-entrypoint-initdb.d/setup.sql": volumeabs: Invalid volume destination path: 'db/postgres-setup.sql/docker-entrypoint-initdb.d/setup.sql' mount path must be absolute.
Waiting 20 seconds for the postgres container to finish initializing (Hit ENTER to continue right away) - Continuing with app database setup:
WARNING: There is a boolean value in the 'environment', 'labels', or 'extra_hosts' field of a service.
These sections only support string values.
Please add quotes to any boolean values to make them strings (eg, 'True', 'false', 'yes', 'N', 'on', 'Off').
This warning will become an error in a future release.
WARNING: There is a boolean value in the 'environment', 'labels', or 'extra_hosts' field of a service.
These sections only support string values.
Please add quotes to any boolean values to make them strings (eg, 'True', 'false', 'yes', 'N', 'on', 'Off').
This warning will become an error in a future release.
WARNING: There is a boolean value in the 'environment', 'labels', or 'extra_hosts' field of a service.
These sections only support string values.
Please add quotes to any boolean values to make them strings (eg, 'True', 'false', 'yes', 'N', 'on', 'Off').
This warning will become an error in a future release.
Creating example_postgres_1
ERROR: Invalid volume spec "db/postgres-setup.sql/docker-entrypoint-initdb.d/setup.sql": volumeabs: Invalid volume destination path: 'db/postgres-setup.sql/docker-entrypoint-initdb.d/setup.sql' mount path must be absolute.
WARNING: There is a boolean value in the 'environment', 'labels', or 'extra_hosts' field of a service.
These sections only support string values.
Please add quotes to any boolean values to make them strings (eg, 'True', 'false', 'yes', 'N', 'on', 'Off').
This warning will become an error in a future release.
WARNING: There is a boolean value in the 'environment', 'labels', or 'extra_hosts' field of a service.
These sections only support string values.
Please add quotes to any boolean values to make them strings (eg, 'True', 'false', 'yes', 'N', 'on', 'Off').
This warning will become an error in a future release.
WARNING: There is a boolean value in the 'environment', 'labels', or 'extra_hosts' field of a service.
These sections only support string values.
Please add quotes to any boolean values to make them strings (eg, 'True', 'false', 'yes', 'N', 'on', 'Off').
This warning will become an error in a future release.
Stopping example_redis_1 ... done
I tried to run it with sudo, it says:
WARNING: There is a boolean value in the 'environment', 'labels', or 'extra_hosts' field of a service.
These sections only support string values.
Please add quotes to any boolean values to make them strings (eg, 'True', 'false', 'yes', 'N', 'on', 'Off').
This warning will become an error in a future release.
WARNING: There is a boolean value in the 'environment', 'labels', or 'extra_hosts' field of a service.
These sections only support string values.
Please add quotes to any boolean values to make them strings (eg, 'True', 'false', 'yes', 'N', 'on', 'Off').
This warning will become an error in a future release.
WARNING: There is a boolean value in the 'environment', 'labels', or 'extra_hosts' field of a service.
These sections only support string values.
Please add quotes to any boolean values to make them strings (eg, 'True', 'false', 'yes', 'N', 'on', 'Off').
This warning will become an error in a future release.
ERROR: Couldn't connect to Docker daemon - you might need to run docker-machine start default.
the docker machine is running. Similar warnings are rising when I try to run the compose

Sorry for not responding in time... actually this repo is very old, and a lot of stuff changed in docker-world since then. Nonetheless, I updated this repo to reflect how I get things done today.
Be sure to check the updated README

Try: "./db/postgres-setup.sql:/docker-entrypoint-initdb.d/setup.sql". The colon was missing.


Gradle UpdateJavaCompatibility recipe does not work with Micronaut's generated format.

A Micronaut 3.x app generated by Micronaut Launch uses the following format in build.gradle for Java compatibility settings:
java {
    sourceCompatibility = JavaVersion.toVersion("1.8")
    targetCompatibility = JavaVersion.toVersion("1.8")
}

Using JavaVersion.toVersion as we do is not properly detected and updated by the UpdateJavaCompatibility recipe.

Hi @jeremyg484 👋
I see a couple of possibilities here, so what would you ideally like to see?
I could see trying to attempt to keep the method invocation directly (JavaVersion.toVersion("11")) or convert it to the enum type by default (JavaVersion.VERSION_11).

Hi @shanman190, thanks for the quick response!
I think either would ultimately be fine, but I would lean toward keeping the same format (unless the declarationStyle option is set differently) as it would be consistent with what we are also generating for new Micronaut 4 apps created with https://micronaut.io/launch


Align the whole file

I was wondering if there was a way to auto-format an entire file with Valign instead of having to place my cursor on the segment to be aligned?

Unfortunately, there is not. This package's goal was intended to format as needed—incase you did not want some part formatted.
I would think that would be done by a beautifier instead.
But that makes it break on anything grammar specific.
{
  'key => value': true
}

In every case dealing with strings it will find the first match and not align as intended.
If you have any recommendations on how to achieve this without grammar (or little grammar), let me know.

Darn I had a plugin I had written for Brackets that would parse a whole file and align end of line comments as well as operators; It wouldn't align the var statements though... But since I switched to atom I deleted it. Thanks for the reply though. I will have to figure out coffee scripting eventually.


Error_CheckModeration

I tried to use the new feature  --experimental-use-full-context   by upgrading the repo and to installl locally. But I get the following error upon execution:
[Translator] System Instruction: Translate zh to en
[Error_CheckModeration] 2024-10-22T20:38:46.040Z Status 500 Error 500 Unexpected error {
  message: 'Unexpected error',
  type: 'server_error',
  param: null,
  code: null
}

I wonder if this is caused by a mistake in my repo upgrade or something in the main repo

Is this the full output? What is what is the full command? Are you able to provide the file?
You also try to turn off moderator
--no-use-moderator

Any follow ups?

I have reached insufficient quota. I get insufficient quota error.
Which I guess it means that it works now, right?
I'll try after I have toped up my credit again.
Meanwhile, here is the sub I was testing on:
https://drive.google.com/file/d/1bo-LJ7dmZFzKLuraLipDhN4f4PBn4cAa/view?usp=sharing

The input file works, ok, so should be issues you need to resolve from the endpoint you are using.

Closing to cleanup and error is caused by external server side endpoint.


Adding Vilniaus Licejus (licejus.lt)

@KirylKrutsko First stage of verification passed, official domain is licejus.lt as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@KirylKrutsko Pull request merged. Thank you!


Updated Billing

Updated Billing with autobuilds parallel info.

@shaunmulligan can you confirm which is correct? Second commit I included autobuilds in the Pro and Team plan.


Define an earliest insertion point

This is to deal with the fact that LLVM's coroutine lowering can't handle
instructions with side-effects well that are inserted before the coro.begin.

@swift-ci Please test

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - 37005baa2cb3429a6cf57248673bb15451e0ea0e

Build failed
Swift Test OS X Platform
Git Sha - 37005baa2cb3429a6cf57248673bb15451e0ea0e

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - 1c1c9f2141cfb6ff7b46a8cac225914b8a993af7

@swift-ci Please smoke test linux


support flutter run  --debug-port for iOS devices

An in-progress PR here: https://github.com/flutter/flutter/pull/4424.
@chinmaygarde @tvolkert

This should be fixed now.


Grammar changes and minor corrections

Mostly English as a Second language grammar nuances, as well as some code corrections and corrections to mistakes in instructions.

Hi  pfeerick,
Thanks for your great work!
Franz


Thread fetching revert

Summary
Thread fetching revert

@lindy65 https://mattermost.atlassian.net/browse/MM-17468


cmd: move app cmd from main pkg to a dedicated pkg

Summary
Moving app cmd from main package to a dedicated one

Problem Definition
App's cmd is now located in the main package which makes it impossible to import for usage in celestiaorg/test-infra repo for testing utilities. It brings the heavy copy-cat and maintenance in both repos

Proposal
Is this doable from the app side to move the cmd init, srvexec cmd from main package to smt like appcmd ?

For Admin Use

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

Can you clarify which functions you'd need from the app cmd? So they can be refactored out into a library. I mean the app cmd has to be in the main package. Otherwise it would not be executable.

Mainly, I need a NewRootCmd()  as I need to feed it into cosmos/sdks server's cmd executor cmd.Execute

I see. That would also mean that we can get rid of the NewRootCmd currently in https://github.com/celestiaorg/test-infra/pull/27 ?
Feel free to submit a PR if Evan does not see any blocker for this.


[Microbatch] Use behavior flag to gate microbatch functionality

In #308 we began gating the microbatch functionality behind an environment variable. However, for a better user experience, we're moving to using a project flag in dbt-core (https://github.com/dbt-labs/dbt-core/pull/10799). In dbt-adapters, project flags can be interpreted by behavior flags. Thus we need to update dbt-adapters to use a behavior flag for gating the microbatch functionality instead of using an environment variable.

Opened a new issue in dbt-labs/docs.getdbt.com: https://github.com/dbt-labs/docs.getdbt.com/issues/6447


Prediction for a single block for SAM not working

Minimal reproducible example:
import bioimageio.core
from bioimageio.core.digest_spec import get_test_inputs, get_test_outputs

model_description = bioimageio.core.load_description("diplomatic-bug/staged/1")
inputs = get_test_inputs(model_description)
inputs = inputs.as_single_block()
with bioimageio.core.create_prediction_pipeline(model_description) as pp:
    prediction = pp.predict_sample_block(inputs)

falis with
Traceback (most recent call last):
  File "/home/pape/Work/my_projects/micro-sam/mre_bioio.py", line 9, in <module>
    prediction = pp.predict_sample_block(inputs)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pape/Work/bioimageio/core-bioimage-io-python/bioimageio/core/_prediction_pipeline.py", line 124, in predict_sample_block
    output = output_meta.with_data(
             ^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pape/Work/bioimageio/core-bioimage-io-python/bioimageio/core/sample.py", line 256, in with_data
    blocks={
           ^
  File "/home/pape/Work/bioimageio/core-bioimage-io-python/bioimageio/core/sample.py", line 257, in <dictcomp>
    m: Block(
       ^^^^^^
  File "<string>", line 9, in __init__
  File "/home/pape/Work/bioimageio/core-bioimage-io-python/bioimageio/core/block.py", line 40, in __post_init__
    assert s == halo.left + (slice_.stop - slice_.start) + halo.right, (
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: (2, SliceInfo(start=0, stop=-1), Halo(left=0, right=0))

needs further invesitagion. my guess is that we do not yet correctly handle data dependent axis sizes (data dep axis size is encoded as -1 in some places...)


AddExtension for E10s extension throws exception

Meta -
OS: Win 10 x64
Selenium Version:
3.5
Browser:
Firefox 55
Expected Behavior -
AddExtension should add E10s extension
Actual Behavior -
"Error installing extension"

Sorry wrong group !


flaky CI macos: stat reports year 1677

Our MacOS CI seems to have developed a new flaky test. At first glance it looks like invalid (uninitialized?) memory got interpreted as a (negative? constant?) datetime, excessively far in the past (year 1677).
failures:

---- test_stat::test_symlinks stdout ----
---- test_stat::test_symlinks stderr ----

failures:
    test_stat::test_symlinks

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 3276 filtered out; finished in 0.42s

--- TRY 3 STDERR:        coreutils::tests test_stat::test_symlinks ---
thread 'main' panicked at tests/by-util/test_stat.rs:160:46:
assertion failed: `(left == right)`

Diff < left / right > :
<644 -rw-r--r-- 8<PHONE_NUMBER>2 1000010 81a4 regular file 0 wheel 1 190683 / /etc/localtime 4096 114 0 root 1970-01-01 00:00:00.000000000 +0000 -9223372036 2163-07-19 13:09:58.799152000 +0000<PHONE_NUMBER> 2024-05-14 22:35:48.350259563 +0000<PHONE_NUMBER>
>644 -rw-r--r-- 8<PHONE_NUMBER>2 1000010 81a4 regular file 0 wheel 1 190683 / /etc/localtime 4096 114 0 root 1677-09-21 00:12:43.145224192 +0000 -9223372037 2163-07-19 13:09:58.799152000 +0000<PHONE_NUMBER> 2024-05-14 22:35:48.350259563 +0000<PHONE_NUMBER>

This seems to happen very often, at least these PRs: https://github.com/uutils/coreutils/pull/6390#issuecomment-2119011079 https://github.com/uutils/coreutils/pull/6418

Closing this ticket as the issue no longer shows up.


Replace Tic Tac Toe example

This http://codepen.io/alex-dixon/full/JogOpQ/ example doesnt fullfill user stories, i can beat the game.
Here, I'm the 'x' one.

I agree to this.. Here is another scenario (I am also 'x')

Confirmed. If anyone has a completed version of this zipline that fulfills the user story they would like to volunteer I think it should be swapped out.

@ltegman you can use mine if you'd like, although I'm not sure if you want the extra features on there. My tic tac toe game

Just a note that this is a little unfair to Alex's Zipline since it was originally a "Bonus User Story." At some point (fairly recently?) the text was modified.

@denmch is right. The user story for the challenge is different that what is in the video. This has been noted several times before in #7186 and #5294. I'm not sure what we plan on doing to account for the updates in the site.
/cc: @FreeCodeCamp/issue-moderators

I've updated this issue. It is clear that this version has a lot of faults. We need a new version to replace this one.

@erictleung Have you taken a look at http://codepen.io/chrisdziewa/full/dYKaGJ/ as a replacement?

@BerkeleyTrue looks good to me 👍
@raisedadead I think you have access to the FCC codepen? Can we use http://codepen.io/chrisdziewa/full/dYKaGJ/ as the example game?

@BerkeleyTrue and @erictleung updated the official pen. Closing as resolved. Thanks.


Create the front-end code

Create the front-end code  based on #1

Just the style (css, html and a very basic js script).
It's DONE!


i18n(ko-KR): update api-reference.mdx

Description (required)

update api-reference.mdx
#9422

Related issues & labels (optional)

Closes #
Suggested label:

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

ko
reference/api-reference.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Pool Fee ignored when payout is calculated

Description
Pool does not calculate and will not keep the OP fee. Instead, it will send all the remaining coins to the miners.  "rewardRecipients" is set to 1%
Steps to Reproduce
build v40, find block, pay to miners.
Expected behavior
Pool needs to remove the OP fee from the block amount before calculating the miner payments.
Actual behavior
Pool calculates and sends all the coins from the block to it's miners, including dev fee. Pool fee is ignored.
Reproduces how often
Every time.
Version
v40
Additional Information
changing setting variable "rewardRecipients" to "RewardRecipients" may work. Currently in testing.
UPDATE: case is not the problem.

@ZhiKosta What coin are you mining? Paste your config. (minus anything sensitive)

Hey there, I just checked back my testnet logs. Using same address used for coinbase rewards and pool fee rewardRecepients never worked (as long as i remember dealing with MC)
I only found this issue yesterday since i put actual fee's on.
But since you ask, here is the proof:
https://explorer.bitcoingold.org/insight/block/00000000de2db420c7127300c9480160af065ad347c7f6336a88b8ecb28c07df
block mined
https://explorer.bitcoingold.org/insight/tx/2c792867abb7d6362780becc0f1bd12f3cd68d2c70a5d537a6fe8ba241b38c38
block paid
                       "id": "btg",                         "enabled": true,                         "enableInternalStratum": false,                         "coin": "bitcoin-gold",                         "networks": "main",                         "address": "GLuatJRozfXt1vwY9SGLiqxXaVeSBbSP2p",                         "rewardRecipients": [                             {                             "address": "GLuatJRozfXt1vwY9SGLiqxXaVeSBbSP2p",                             "percentage": 1                             }                         ],
This never worked, even on testnet. Only way your pool gets paid is using different wallet address for fee and coinbase.
I've managed to get Oliver before he went to bed. He'll look at this issue when he finds some time. In the mean time, i would love to know if you can confirm this.

Miningcore intentionally does not include the poolAddress in the payout but does calculate the rewards to reserve the respective percentage, it's not sending all of the reward to the miners one of those addresses will be a change address within your own wallet -- it's behaving as intended.
https://github.com/coinfoundry/miningcore/blob/bf5015a/src/Miningcore/Blockchain/Bitcoin/BitcoinPayoutHandler.cs#L195-L216
        public virtual async Task<decimal> UpdateBlockRewardBalancesAsync(IDbConnection con, IDbTransaction tx, Block block, PoolConfig pool)
        {
            var blockRewardRemaining = block.Reward;

            // Distribute funds to configured reward recipients
            foreach(var recipient in poolConfig.RewardRecipients.Where(x => x.Percentage > 0))
            {
                var amount = block.Reward * (recipient.Percentage / 100.0m);
                var address = recipient.Address;

                blockRewardRemaining -= amount;

                // skip transfers from pool wallet to pool wallet
                if (address != poolConfig.Address)
                {
                    logger.Info(() => $"Adding {FormatAmount(amount)} to balance of {address}");
                    await balanceRepo.AddAmountAsync(con, tx, poolConfig.Id, poolConfig.Template.Symbol, address, amount, $"Reward for block {block.BlockHeight}");
                }
            }

            return blockRewardRemaining;
        }

OK. i confirmed that if you use your coinbase wallet to receive pool fee with it, you actually get the calculated amount as a change sent to a change address associated with your wallet.
I got this wrong only because i expected that pool will send the amount to the miners but leave the pool fee value in the same address. (using it as  address to send the change in instead of hashing new one)
I hope this help someone else who is wondering about the same. Thank you @bitspill for the insights!


DK2 sensor distortion calibration - indices incorrect

Raising issue purely as a result of code inspection (also I don't even have a DK2)
https://github.com/thaytan/OpenHMD/blob/db16fb8254fdfbc5fcc372845232eb9d3be0b360/src/drv_oculus_rift/rift-sensor.c#L468
This comment states:
/*
 * k = [ k1, k2, p1, p2, k3, k4 ] for DK2 distortion
 */

Code reads:
			k[0] = k1; k[1] = k2;
			k[1] = p1; k[2] = p2;
			k[4] = k3;

Questioning correctness of k[1] = p1; and k[2] = p2; ... should be [2] and [3]?

Well spotted!


Support for subshells breaks escaped parentheses

Running the following code with deno:
import $ from 'https://deno.land/x/dax/mod.ts';

await $`echo \( foo bar \)`;

An error will be produced:
error: Uncaught (in promise) "Unexpected character.\n  ( bar )\n  ~"

The expected output is:
( foo bar )

Given the following content of deno.json:
{
  "tasks": {
    "paren": "echo ( foo bar )",
    "paren2": "echo \\( foo bar \\)",
    "paren3": "echo \\(\nfoo bar\n\\)"
  }
}

And running deno task paren2 and deno task paren3 both produce the expected output:
$ deno task paren2
Task paren2 echo \( foo bar \)
( foo bar )

$ deno task paren3
Task paren3 echo \(
foo bar
\)
( foo bar )

Support for escaped parentheses was added in https://github.com/denoland/deno_task_shell/pull/99, but it seems that https://github.com/dsherret/dax/pull/232 broke it.
Related:

https://github.com/dsherret/dax/pull/232
https://github.com/denoland/deno_task_shell/pull/99
https://github.com/denoland/deno_task_shell/issues/97

It seems that it requires double-escaping. The following code works:
import $ from 'https://deno.land/x/dax/mod.ts';

await $`echo \\( foo bar \\)`;


Add @editor or @openfiles context method

Request
Create a method which is similar to @workspace, but is limited to scanning each file which is open in the editor. A scan of additional files in the repository should not happen, as all relevant files will be open in the editor, with the primary file being discussed being the one given the editors current focus, and each additional reference being open in the editor but not provided the editors focus.
Reasoning
In large repositories the @workspace method rarely finds the correct files, even when provided function and class names, file names, or even relative or fully qualified paths. Even when the files required to reference are the only files open in the editor and this is told to copilot. Often telling it the files are open can lead to a response that "copilot is an AI which cannot access your files", which is clearly not the case, but somehow when too much content exists Copilot I think "taps out" and gives up. In these cases the references used can be completely unrelated to the discussion and result in suggestions which have relatively low relevance.
The ability to force the references to be scanned from only the editors open files, and each file, could be extremely helpful in providing the user the ability to easily increase the relevance of suggestions. I'm fairly confident this should be a worthwhile feature if it works as described. I can simulate what I presume should be a fairly similar effect by creating a single temporary file and copying chunks of relevant code from multiple files into the temp file, then using this as the only reference for a discussion. While this works it is time consuming to do for the user, leads to extra files that need to be cleaned up later, or worse, repeated blocks of code in non temporary files which might be missed during "cleanup" after the conversation.

@TylerLeonhardt this is about having a #workspace-like variable that limits semantic embeddings to open files (similar to copilot completion's default behavior). Does that fall into your area?

@TrevorBenson you should be able to use #editor when talking about the active editor or #selection for your selection in that editor. Additionally there's #file:.... to include certain files.
@digitarald honestly, not sure. Feels like it would be more @roblourens as it feels closer to #editor and #selection than @workspace, but maybe it goes to any of the @workspace people...

@TrevorBenson you should be able to use #editor when talking about the active editor or #selection for your selection in that editor. Additionally there's #file:.... to include certain files.
@digitarald honestly, not sure. Feels like it would be more @roblourens as it feels closer to #editor and #selection than @workspace, but maybe it goes to any of the @workspace people...

I was not aware # was an alternative symbol to @, searching the copilot chat docs I can't seem to find #edtitor, #file, or other hashtag methods, described in the copilot chat docs.
However, I tried the #editor option and it does not seem to achieve the goal. With three open files in the editor and either: nothing highlighted; a section of code highlighted; the entire file highlighted, only the active file in the editor is used as a reference. The other open files in the editor are not used as a reference.
I also tried #file:path/to/file.py and #file: path/to/file.py and #file path/to/file.py. Each time only the foreground file in the editor is used as a reference, the file from the path is never part of the references used to formulate a response. :shrug:

@roblourens correct me if I'm wrong, I think if you include context via a variable (#) it doesn't show up in the references because the references are only things that were implicitly used.
If you use a variable, it's definitely used to formulate a response.

If you use a variable, we will try to use it, but it may not fit into the context window if the file is too big.
And yeah, I would like to make #file easier to use, for example we could show references for all the open files in the suggest widget, and an #openFiles variable might make sense too.

If you use a variable, we will try to use it, but it may not fit into the context window if the file is too big.

I definitely understand that files that are quite large can exceed the number of tokens that can be handled in a single request, as I've seen this with even a single file.

And yeah, I would like to make #file easier to use, for example we could show references for all the open files in the suggest widget, and an #openFiles variable might make sense too.

Yes, anything that provides more clarity to the user on what files will be chosen or can be influenced to be chosen, would be a very welcome enhancement.
Thanks


VIP interface isn't needed after kube-vip v0.4.1

After kube-vip v0.4.1, since the kube-vip can use the VIP based on the default route automatically, the VIP interface parameter is not required anymore.
Related issue:
https://github.com/harvester/harvester/issues/1681
Dependency: https://github.com/harvester/harvester/pull/1805

@johnliu55tw The VIP interface configurations deleted include VLAN configurations. Does it affect the original function?

@johnliu55tw The VIP interface configurations deleted include VLAN configurations. Does it affect the original function?

@yaocw2020 I think it's related to https://github.com/harvester/harvester-installer/pull/175. cc @FrankYang0529

@yaocw2020 Will this work when upgrading from 1.0.0? If the existing managedChart still contains those values.

@johnliu55tw The VIP interface configurations deleted include VLAN configurations. Does it affect the original function?

@yaocw2020 I think it's related to #175. cc @FrankYang0529

Since we should redesign network architecture for https://github.com/harvester/harvester/issues/1390, I think it's okay to revert all changes in https://github.com/harvester/harvester-installer/pull/175.

@johnliu55tw The VIP interface configurations deleted include VLAN configurations. Does it affect the original function?

@yaocw2020 I think it's related to #175. cc @FrankYang0529

Since we should redesign network architecture for harvester/harvester#1390, I think it's okay to revert all changes in #175.

As for what issue 1390 requests, the management NIC should also be VLAN. We may not need to revert all changes but consider more about other components.

@yaocw2020 Will this work when upgrading from 1.0.0? If the existing managedChart still contains those values.

No. Those values can not be reserved.


polymorphism issue in 5.6 with NSwagStudio code gen

We are currently using NSwagStudio to generate dto based on our Swashbuckle generated Swagger definitions.
We have one polymorphic class hierarchy in our api and prior to 5.6.x everything worked fine.  NSwagSudio generated code using a Newtonsoft JsonConverter to deserialize into the correct derived class based on the discriminator field.
We just tried moving to 5.6.x and that code generation broke.  The issue seems to be that the discriminator field information is no longer generating in the components schemas section of the swagger json.  Instead the discriminator information is now being generated in the paths responses section.
Is there a way with 5.6 to continue to have the discriminator generate in the components section so that NSwag can continue to generate the proper serialization code for us?

I have tested the latest version with NSwag and it’s client generation appears to work correctly for polymorphic types.
For me to troubleshoot further, could you please create a minimal project to demonstrate the issue and post to GitHub. Then I can pull it down and switch between Swashbuckle versions to understand your issue better

I put a sample at https://github.com/pmiddleton/SwashbuckleTest
It is set to build vs 5.5.1 and show what we expect the output to be.  Load it up and use NSwagStudio to view the output.  Notice that the shape class looks like this.
[Newtonsoft.Json.JsonConverter(typeof(JsonInheritanceConverter), "discriminator")]
[JsonInheritanceAttribute("Rectangle", typeof(Rectangle))]
[JsonInheritanceAttribute("Circle", typeof(Circle))]
[System.CodeDom.Compiler.GeneratedCode("NJsonSchema", "<IP_ADDRESS> (Newtonsoft.Json v<IP_ADDRESS>)")]
public partial class Shape
{
    [Newtonsoft.Json.JsonProperty("sides", Required = Newtonsoft.Json.Required.DisallowNull, NullValueHandling = Newtonsoft.Json.NullValueHandling.Ignore)]
    public int Sides { get; set; }
}

You can then switch the nuget references to 5.6.3 and uncomment the attributes on the shape class and uncomment the new 5.6.x setup calls in AddSwaggerGen  in the setup class.  I had to do a build clean / rebuild all for the nuget to update correctly.
Then run again and see that the output from NSwagStudio looks like this.
[System.CodeDom.Compiler.GeneratedCode("NJsonSchema", "<IP_ADDRESS> (Newtonsoft.Json v<IP_ADDRESS>)")]
public partial class Shape
{
    [Newtonsoft.Json.JsonProperty("shapeType", Required = Newtonsoft.Json.Required.Always)]
    [System.ComponentModel.DataAnnotations.Required(AllowEmptyStrings = true)]
    public string ShapeType { get; set; }

    [Newtonsoft.Json.JsonProperty("sides", Required = Newtonsoft.Json.Required.DisallowNull, NullValueHandling = Newtonsoft.Json.NullValueHandling.Ignore)]
    public int Sides { get; set; }
}

The JsonConverter information is missing.
I am just missing a step in the configuration to get the output the same?
Thanks,
Paul

I have also encountered this problem with 5.6. @pmiddleton's example is a very concise solution which demonstrates the difference in the generated swagger.json files.
The full files are below, but it seems that the discriminator objects in the JSON have been moved from components > schemas > <Object>s to paths > <URL> / get / responses / schema.
Full 5.5.1 file:
{
    "openapi": "3.0.1",
    "info": {
      "title": "Shape",
      "version": "v1"
    },
    "paths": {
      "/api/Shape/GetShape": {
        "get": {
          "tags": [
            "Shape"
          ],
          "responses": {
            "200": {
              "description": "Success",
              "content": {
                "text/plain": {
                  "schema": {
                    "oneOf": [
                      {
                        "$ref": "#/components/schemas/Rectangle"
                      },
                      {
                        "$ref": "#/components/schemas/Circle"
                      }
                    ]
                  }
                },
                "application/json": {
                  "schema": {
                    "oneOf": [
                      {
                        "$ref": "#/components/schemas/Rectangle"
                      },
                      {
                        "$ref": "#/components/schemas/Circle"
                      }
                    ]
                  }
                },
                "text/json": {
                  "schema": {
                    "oneOf": [
                      {
                        "$ref": "#/components/schemas/Rectangle"
                      },
                      {
                        "$ref": "#/components/schemas/Circle"
                      }
                    ]
                  }
                }
              }
            }
          }
        }
      }
    },
    "components": {
      "schemas": {
        "Shape": {
          "required": [
            "discriminator"
          ],
          "type": "object",
          "properties": {
            "discriminator": {
              "type": "string"
            },
            "sides": {
              "type": "integer",
              "format": "int32"
            }
          },
          "additionalProperties": false,
          "discriminator": {
            "propertyName": "discriminator"
          }
        },
        "Rectangle": {
          "allOf": [
            {
              "$ref": "#/components/schemas/Shape"
            },
            {
              "type": "object",
              "properties": {
                "area": {
                  "type": "integer",
                  "format": "int32"
                }
              },
              "additionalProperties": false
            }
          ]
        },
        "Circle": {
          "allOf": [
            {
              "$ref": "#/components/schemas/Shape"
            },
            {
              "type": "object",
              "properties": {
                "radius": {
                  "type": "integer",
                  "format": "int32"
                }
              },
              "additionalProperties": false
            }
          ]
        }
      }
    }
  }

Full 5.6.3 file:
{
    "openapi": "3.0.1",
    "info": {
      "title": "Shape",
      "version": "v1"
    },
    "paths": {
      "/api/Shape/GetShape": {
        "get": {
          "tags": [
            "Shape"
          ],
          "responses": {
            "200": {
              "description": "Success",
              "content": {
                "text/plain": {
                  "schema": {
                    "oneOf": [
                      {
                        "$ref": "#/components/schemas/Rectangle"
                      },
                      {
                        "$ref": "#/components/schemas/Circle"
                      }
                    ],
                    "discriminator": {
                      "propertyName": "discriminator"
                    }
                  }
                },
                "application/json": {
                  "schema": {
                    "oneOf": [
                      {
                        "$ref": "#/components/schemas/Rectangle"
                      },
                      {
                        "$ref": "#/components/schemas/Circle"
                      }
                    ],
                    "discriminator": {
                      "propertyName": "discriminator"
                    }
                  }
                },
                "text/json": {
                  "schema": {
                    "oneOf": [
                      {
                        "$ref": "#/components/schemas/Rectangle"
                      },
                      {
                        "$ref": "#/components/schemas/Circle"
                      }
                    ],
                    "discriminator": {
                      "propertyName": "discriminator"
                    }
                  }
                }
              }
            }
          }
        }
      }
    },
    "components": {
      "schemas": {
        "Circle": {
          "type": "object",
          "allOf": [
            {
              "$ref": "#/components/schemas/Shape"
            }
          ],
          "properties": {
            "radius": {
              "type": "integer",
              "format": "int32"
            }
          },
          "additionalProperties": false
        },
        "Shape": {
          "required": [
            "discriminator"
          ],
          "type": "object",
          "properties": {
            "discriminator": {
              "type": "string"
            },
            "sides": {
              "type": "integer",
              "format": "int32"
            }
          },
          "additionalProperties": false
        },
        "Rectangle": {
          "type": "object",
          "allOf": [
            {
              "$ref": "#/components/schemas/Shape"
            }
          ],
          "properties": {
            "area": {
              "type": "integer",
              "format": "int32"
            }
          },
          "additionalProperties": false
        }
      }
    }
  }

So, it's my understanding that the use of discriminator in the prior version was actually incorrect, according to the Swagger / OpenAPI specification. Specifically, if you look at the Discriminator example from the Swagger docs, you can see that the discriminator property should be used inline with the oneOf keyword rather than being defined on the schema(s) that are referenced by the oneOf construct:
components:
  responses:
    sampleObjectResponse:
      content:
        application/json:
          schema:
            oneOf:
              - $ref: '#/components/schemas/simpleObject'
              - $ref: '#/components/schemas/complexObject'
            discriminator:
              propertyName: objectType

In fact, the docs specifically state that ...

The discriminator is used with anyOf or oneOf keywords only.

So, while this doesn't really help you, I wanted to first help you understand the rationale for the change. As NSwag needs the discriminator to be defined elsewhere, I think it may be using the spec incorrectly. Of course NSwag is an end-to-end toolchain, so it doesn't always matter if it's misinterpreting the Swagger / OpenAPI spec so long as it's consistent in doing so across it's tool chain.
With that said, I can kind of understand why it needs to things the way it does. So, rather than baking what I believe to be invalid spec generation into Swashbuckle, I'd prefer to keep the Swashbuckle behavior as is, but provide you with a simple Schema filter workaround that will tweak the generated schema to meet the needs of NSwag. Does that sound reasonable?

OK - here's the workaround as promised. With this approach, you can annotate your source classes exactly as described in the NSwag docs for inheritance, and Swashbuckle will automatically pick up the subtypes specified with KnownType, and generate schema definitions that will in turn be interpreted correctly by the NSwag client generator tooling:
// Startup.cs
services.AddSwaggerGen(c =>
{
    // Tell Swashbuckle to emit inheritance hierarchies using "allOf"
    c.UseAllOfForInheritance();

    // Tell Swashbuckle to identify subtypes using the KnownTypeAttribute (as per NSwag)
    c.SelectSubTypesUsing(baseType => baseType.GetCustomAttributes<KnownTypeAttribute>().Select(attr => attr.Type));

    // Wire up a schema filter to apply the Discriminator info on the base schema (as per NSwag)
    c.SchemaFilter<NSwagDiscriminatorSchemaFilter>();
});

// NSwagDiscriminatorSchemaFilter.cs
public class NSwagDiscriminatorSchemaFilter : ISchemaFilter
{
    public void Apply(OpenApiSchema schema, SchemaFilterContext context)
    {
        var jsonConverterAttribute = context.Type.GetCustomAttribute<JsonConverterAttribute>(false);

        if (jsonConverterAttribute?.ConverterType == typeof(JsonInheritanceConverter))
        {
            var discriminatorName = jsonConverterAttribute.ConverterParameters[0].ToString();

            // Add the discriminator property
            schema.Properties.Add(discriminatorName, new OpenApiSchema { Type = "string" });

            // Flag it as required
            schema.Required.Add(discriminatorName);

            // Add "discriminator" metadata
            schema.Discriminator = new OpenApiDiscriminator
            {
                PropertyName = jsonConverterAttribute.ConverterParameters[0].ToString()
            };
        }
    }
}

Thank you for this.  I will give it a try tomorrow and let you know.
Will this work around work long term for future swashbuckle versions?  I will open an issue with NSwag and see if they can conform to the specification.

Thank you very much @domaindrivendev for your explanation and provided workaround. I had to tweak your Schema filter example to work for my particular setup, but managed to get it working easily enough.
@pmiddleton, I have already created an issue in the NSwag repository and quoted @domaindrivendev's comments there:
https://github.com/RicoSuter/NSwag/issues/3099#issuecomment-705357940

Thanks @domaindrivendev - I just got this working and the fix works.  Thank you for the help.

I used the above work around to generate a C# client but the consumer of the new client still cannot infer the concrete type.  It gets back a base type with no apparent information about what concrete type it is.  Would someone possibly post their swagger.json so I can see what you're getting after the above workaround?


Clarify difference between surface material and surface override material

This closes https://github.com/godotengine/godot/issues/82496https://github.com/godotengine/godot/issues/82496.

Thanks!

Cherry-picked for 4.1.3.


Configurable datadog.conf hostname

We'd like to be able to set the hostname in datadog.conf. Even when passing the fqdn in via docker run -h the agent was still only using the machine name as the hostname in the infrastructure list and not the entire fqdn. We've had some other minor hostname issues, so we prefer being able to set this explicitly in some cases.
Thanks!

We would also love this feature, any ETA?

Hey @bshelton229 and @daveey sorry for the delay here.
This was implemented by #98 and documented by #99
Thank you for pushing for the change!


testing with single package solution in pypi

Why are these changes needed?
Modify requirements.txt to use single package release on pypi
Related issue number (if any).

We will no longer maintain the notebooks branch. All work will continue to start with dev


Upgrade to AWS SDK V2

Hi ! Thanks for creating this project !
I used specific SSO configuration that is not supported by the AWS SDK v1
and thought it would be great to update this dependency.
Tests have been migrated to use SDK v2 but they are still missing something as I
get segmentation faults instantly when running the tests.
I'll try to fix them but wanted to make you aware of this contribution !

feat: upgrade AWS SDK to v2
tests: adapt tests to SDK v2

Closing in favour of https://github.com/tedsmitt/ecsgo/pull/50


[5.7] Removed index from AuthorizeRequests

In a previous commit you removed index method from authorizeResource() so there is no use to keep mention of it in the AuthorizeRequests trait ?

Eh, will just leave it since we're on a patch release in case there is some unexpected breakage removing it.

Do you want me to merge on another branch (or maybe wait another release) ?

@Grafikart feel free to send in a pr to master


document active query dumps

Fixes #11216.
@abarganier, let me know if I shouldn't have this on the debug zip page yet. I can save that for a separate PR if that part is further out.

This change is

@taroface thanks for the updates - I've not yet completed the work to pull these files into debug.zip but I hope to next week. I will keep you posted 👍

@abarganier This should be ready for your review!


UI AI Search on custom tables

Hi, it would be helpful an example with AI search on a custom table (e,g, with data imported by Json files).
I can see the backend code for a similar scope but it's not used on UI.
Thanks

Hi, creating a search on Postgresql tables is the next feature. It is currently in development. The import works with Csv files that use Jackson for the import. Jackson is used by Spring for Json too.
I will update this issue as soon as the feature good enough to be used. Then a UI will be available.

Thank you. I tried searching on postgresql with http://localhost:8080/rest/table/search?query=.... and it works relatively well after I imported my json on a new table! I hope to try that use on UI soon, your work is great!

In addition to asking in response for all the objects that correspond to a specific filter on a column, it would be useful to be able to exploit any links between rows in the DB too (for example father/son column, in queries like: what is the parent object of xxxx?).

Hello,
please have a look at the readme. The feature to turn a question in a sql query is implemented. The frontend shows the query result in a table. The feature is documented in the article.

The solution is shown in the acticle.


Trace files from Instruments can only be dragged, not opened

Repro: click on the big "Browse" button and select a trace from Instruments.app.
Expected: it should open fine, just like it does when you drag and drop it in.
Unexpected: it says the file format is unsupported.

Hey @aparrapo, sorry you're running into issues.
Can you provide reproduction steps w/ your xcode version and/or a file that fails to import?

Hi @jlfwong, I have a multi-threaded app, but nothing too complex. I run the Instruments' time profiler on a 30sec job and then save the .trace file via File -> Save.
I'm using XCode 10.0 beta.
I'm afraid I cannot share .trace file as it's something I'm running at work, but if the info above is not enough I can try recreating a simpler version that I can upload :)

Ah yeah, I haven't tested anything w/ the XCode 10.0 beta at all. XCode 9 Instruments should be working just fine. Let's move this discussion to #163 since this is an unrelated change to the one reported in this issue.