Confused about ResourceID

Above you mention editing the Web.config file and provide a snippet, you have commented out the ResourceID portion and OpenID on ADFS requires a resource parameter. https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/development/custom-id-tokens-in-ad-fs#test-the-custom-claims-in-id-token
Is this meant to be commented out? The screenshot below the code snippet, doesn't correlate with the code snippet.

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

ID: 473bc6ea-017f-52f3-7e58-81ecf58d2db8
Version Independent ID: 20965612-d6a9-35ea-c030-91c09372962e
Content: Build a web application using OpenID Connect with AD FS 2016
Content Source: WindowsServerDocs/identity/ad-fs/development/enabling-openId-connect-with-ad-fs.md
Service: unspecified
GitHub Login: @billmath
Microsoft Alias: billmath

Thanks for the feedback. We have updated the document and corrected the issue you pointed out. Thanks.

#please-close

#please-close

#assign:IngridAtMicrosoft


Removed write-only object

Removed write-only object

Whatever automation found this issue is wrong. This is actually not a write-only object. The token counter will throw an exception if it reaches a limit.
https://github.com/opensearch-project/OpenSearch/blob/46a269ef21e88e3cb1398474e4bf82af4c3b3b7f/server/src/main/java/org/opensearch/action/admin/indices/analyze/TransportAnalyzeAction.java#L485


🐛 Excluded plan changes from paid subscribers graph in dashboard

refs https://github.com/TryGhost/Team/issues/1673
When a user switches plan, the paid subscribers delta chart on the dashboard displays the change as a cancellation plus a new subscription. This display is misleading and confusing - instead, plan changes should be excluded from the paid subscribers delta chart.
Awaiting https://github.com/TryGhost/Ghost/pull/15023

Codecov Report

Merging #2425 (af15d7c) into main (7e35852) will decrease coverage by 0.10%.
The diff coverage is 0.00%.

:exclamation: Current head af15d7c differs from pull request most recent head 623e5c8. Consider uploading reports for the commit 623e5c8 to get more accurate results

@@            Coverage Diff             @@
##             main    #2425      +/-   ##
==========================================
- Coverage   40.36%   40.25%   -0.11%
==========================================
  Files         604      604
  Lines       23938    23940       +2
  Branches     4158     4158
==========================================
- Hits         9663     9638      -25
- Misses      14275    14302      +27

Impacted Files
Coverage Δ

app/components/dashboard/charts/paid-breakdown.js
3.42% <0.00%> (ø)

app/services/dashboard-stats.js
9.14% <0.00%> (ø)

app/components/gh-html-iframe.js
45.45% <0.00%> (-38.64%)
:arrow_down:

app/components/gh-site-iframe.js
46.00% <0.00%> (-4.00%)
:arrow_down:

app/components/gh-file-uploader.js
91.53% <0.00%> (-3.08%)
:arrow_down:

app/components/gh-image-uploader.js
94.00% <0.00%> (-1.34%)
:arrow_down:

app/controllers/offer.js
44.23% <0.00%> (-0.93%)
:arrow_down:

app/components/modal-delete-user.js
70.00% <0.00%> (+7.50%)
:arrow_up:

Continue to review full report at Codecov.

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


1:<IP_ADDRESS> - suggestions for Resolve Duplicates use case

Section Number 1:<IP_ADDRESS> https://profiles.ihe.net/ITI/PIXm/volume-1.html#141423-resolve-duplicate-patient-identity-data-in-multiple-identifier-domains
Issue suggested edits for clarity below
Proposed Change
Recommend replacing this:
1:<IP_ADDRESS> Resolve duplicate patient identity data in Multiple Identifier Domains
When a duplicate patient identity is determined, and after the identity (and data) are merged/linked; the PIXm Manager is notified.
1:<IP_ADDRESS>.1 Use Case Description
The hospital main patient registration system had initially feeded the patient identity data to the Patient Identity Cross-reference Manager as patient persons entered the hospital for treatment [01].
After treatment the main patient registry system detects that the Charles 112 patient person was already registered with different patient identity data of Charlie 111. For example the Charles patient identity created on this episode may have had a typo in name, or different contact data). The hospital patient registration system marks the Charles patient identity data as duplicate, with preference for Charlie within the Main Hospital domain.
The hospital patient registration system updates the patient identity data by sending an Resolve Duplicate message to the Patient Identifier Cross-reference Manager
using the Mobile Patient Identity Feed [ITI-104] transaction [09]. This transaction tells the PIXm Manager that the Charles should be deprecated in preference for Charlie 111 patient.
The PIXm Manager can now do further cross-referencing using internal logic [10].
With this:
1:<IP_ADDRESS> Resolve duplicate patient identity data in Multiple Identifier Domains
When a Source determines that two patient identities exist for the same person, the Source merges/links the identities (and data), and then notifies the PIXm Manager.
1:<IP_ADDRESS>.1 Use Case Description
The Main Hospital patient registration system had initially added patient identity data to the PIXm Manager for both Charlie 111 [01] and Charles 112 [01] to the Patient Identity Cross-reference Manager.
After treatment, the registration system detects that Charles 112  was previously registered as Charlie 111. For example the Charles patient identity created on this episode may have had a typo in name, or different contact data). [ should we omit the preceding sentence?]  The registration system marks the Charles patient identity data as duplicate, with preference for Charlie within the Main Hospital domain.
The  registration system sends a Resolve Duplicate message to the Patient Identifier Cross-reference Manager
using the Mobile Patient Identity Feed [ITI-104] transaction [09]. This transaction tells the PIXm Manager that the Charles 112 should be deprecated with preference for Charlie 111.   [do we want to use ‘deprecated’ here??]
The PIXm Manager can now do further cross-referencing using internal logic [10].
Priority:

Low: Typo or other minor classification that an editor can manage. Requires no group discussion.

[do we want to use ‘deprecated’ here??] -> use subsumed with


helpless.....

please provide python example file can run standalone.
import time
import sys
import threading
from datetime import datetime
import json
sys.path.append("../..")
from common import credential
from asr import flash_recognizer
such code can run standalone?

You can refer to this https://github.com/TencentCloud/tencentcloud-speech-sdk-python/tree/master/examples


Incorrect referencing from Requirements section

In the attempt at removing the instance of enumSimple 5, I'm in the process of pulling out the contents so that enumSimple 1 can be applied to all the requirements.
In order to change the type of s7_1_req1 from Contents (which includes its corresponding table as follows
)
to Sentence that refers the user to where the table is (for now at the end of the list of requirements:
).
Unfortunately, when the this Table link is clicked from R1, the user is actually taken to the Table of Symbols at the beginning of the page.
I have referenced this issue from the commit where the I started the modification of the Requirements section.

This error in referencing is occurring because you're using the Table Of Symbols table function to create the table. It automatically assigns the reference label "TableOfSymb" (or something like that), which then references the first table of symbols.
You need to create the table using a different function / the raw Table constructor.

Issue closes as of commit 31cd381.


reopen ticket 3240

Which Category is your question related to?
Sorry to double-post but I don't know how to get a ticket re-opened without this.
https://github.com/aws-amplify/amplify-cli/issues/3240

re-opened #3240


Implement transient traits and identities

Goal
To support additional use cases, such as evaluating identities in different contexts or managing anonymous identities, we aim to enable our SDK users to:

Evaluate flags against identities without persisting them.
Evaluate flags against identities while persisting only a subset of identity traits.

Solution Proposal
Make /api/v1/identities endpoints support optional boolean "transient" attributes both for the top-level identity object and a trait object.
Don't persist identities and traits marked as transient.
In SDKs, support transient: bool and transientTraits: list[str] optional keywords for the getIdentityFlags interface.
Related issues and discussions
Customer requests and use case discussions:

#168, #77
#1840, #1839

API tasks:

https://github.com/Flagsmith/flagsmith/issues/4279
https://github.com/Flagsmith/edge-api/issues/271

SDK tasks:

https://github.com/Flagsmith/flagsmith-python-client/issues/88
https://github.com/Flagsmith/flagsmith-js-client/issues/236
https://github.com/Flagsmith/flagsmith-kotlin-android-client/issues/52
https://github.com/Flagsmith/flagsmith-flutter-client/issues/62
https://github.com/Flagsmith/flagsmith-php-client/issues/74
https://github.com/Flagsmith/flagsmith-elixir-client/issues/35
https://github.com/Flagsmith/flagsmith-ruby-client/issues/63
https://github.com/Flagsmith/flagsmith-go-client/issues/132
https://github.com/Flagsmith/flagsmith-rust-flag-engine/issues/14 + https://github.com/Flagsmith/flagsmith-rust-client/issues/22
https://github.com/Flagsmith/flagsmith-java-client/issues/152
https://github.com/Flagsmith/flagsmith-dotnet-client/issues/104
https://github.com/Flagsmith/flagsmith-nodejs-client/issues/156

@khvn26 I understand that we should implement transient traits because it is a quick and cost-effective way to cover some of the use cases related to contexts. While it could also help with anonymous identities or other use cases, we should keep the scope restricted to transient traits since that is the reason we decided to move ahead with its implementation.
Also, as mentioned in this Notion regarding Anonymous identities https://www.notion.so/flagsmith/Anonymous-identities-904943c595474ae3b792f935109fb6f6 I think that for most we should persist annonymous identities or at least offer that option for most of the real use cases.

Regarding the implementation, I would rather suggest to add a boolean attribute to the trait model, so you can specify and persist  whether it is transient or not. That would allow customers to design the behavior of flags, and would allow transient flags without changes to the SDKs. We could also allow SDKs to request a trait to be marked as transient, but that would be optional.

I would rather suggest to add a boolean attribute to the trait model, so you can specify and persist whether it is transient or no

@novakzaballa I agree with this. However, not all SDKs expose the trait model; some, mainly the server-side ones, accept a simple string to value mapping instead. I suggest we use the transientTraits: list[str] parameter for those and add a transient boolean property to the Trait model for SDKs that support them in their public interfaces.

Agreed @khvn26

As discussed here and offline, we're choosing to leave out the additional parameter in favour of extending the trait_value parameter type. In addition to current TraitValue | null type, the parameter should accept a mapping/object:
{
   transient: boolean
   value: TraitValue
}


Invoking edge function always results in unacceptableStatusCode(404)

Bug report
Describe the bug
When trying to invoke any Edge Function from supabase-swift client context (with or without invoke options) throws an error unacceptableStatusCode(404). Call does not register in the Edge Functions log browser, but it appears in the API Edge Network  log browser as a 404 (see below) using a different invocation URL format:
functions-swift
https://xxx.supabase.co/functions/v1/preview-issue

Edge Functions API documentation
https://xxx.functions.supabase.co/preview-issue

The function name is correct (preview-issue) and can be accessed using Edge Functions API, so it appears that the invocation URL for functions-swift uses an incorrect format:
https://github.com/supabase-community/supabase-swift/blob/8292bf9a8eb21ca1bcfbd249ed84e67776e5ee2f/Sources/Supabase/SupabaseClient.swift#L47-L53
To Reproduce
Invoke a Edge Function using the following signature (after setting up your Supabase Swift client:
do {
    try await client.functions.invoke(functionName: "preview-issue", invokeOptions: .init(headers: ["param": "some-string"]))
} catch {
    throw error
}

Expected behavior

Invocation succeeds and the Edge Function result returns expected response
Invocation gets registered in the Edge Functions log browser

Logs
Log ID
4edd9ee6-9cff-47c3-a476-8426515f3ad2

Log Timestamp (UTC)
2023-02-12T12:24:31.132Z

Log Event Message
POST | 404 | <IP_ADDRESS> | 79854d3a4d27777a | https://xxx.supabase.co/functions/v1/preview-issue

Log Metadata
[
  {
    "request": [
      {
        "headers": [
          {
            "accept": "application/json",
            "cf_cache_status": null,
            "cf_connecting_ip": "<IP_ADDRESS>",
            "cf_ipcountry": "GB",
            "cf_ray": "79854d3a4d27777a",
            "content_length": "0",
            "content_location": null,
            "content_range": null,
            "content_type": null,
            "date": null,
            "host": "xxx.supabase.co",
            "referer": null,
            "sb_gateway_version": null,
            "user_agent": "iOS/1 CFNetwork/1402.0.8 Darwin/22.3.0",
            "x_client_info": "functions-swift/0.2.0",
            "x_forwarded_proto": "https",
            "x_forwarded_user_agent": null,
            "x_kong_proxy_latency": null,
            "x_kong_upstream_latency": null,
            "x_real_ip": "<IP_ADDRESS>"
          }
        ],
        "host": "xxx.supabase.co",
        "method": "POST",
        "path": "/functions/v1/preview-issue",
        "port": null,
        "protocol": "https:",
        "sb": [],
        "search": null,
        "url": "https://xxx.supabase.co/functions/v1/preview-issue"
      }
    ],
    "response": [
      {
        "headers": [
          {
            "cf_cache_status": "DYNAMIC",
            "cf_ray": "79854d3a7723777a-LHR",
            "content_length": "48",
            "content_location": null,
            "content_range": null,
            "content_type": "application/json; charset=utf-8",
            "date": "Sun, 12 Feb 2023 12:24:31 GMT",
            "sb_gateway_mode": null,
            "sb_gateway_version": "1",
            "transfer_encoding": null,
            "x_kong_proxy_latency": null,
            "x_kong_upstream_latency": null
          }
        ],
        "origin_time": 37,
        "status_code": 404
      }
    ]
  }
]

System information

OS: iOS 16.1
Swift: 5.7
Xcode: 14.2
supabase-swift: 0.1.2
functions-swift: 0.2.0

Fixed on https://github.com/supabase-community/supabase-swift/releases/tag/0.1.3


Add the ability to concatenate locale files

Fixes https://jira.wixpress.com/browse/NGG-32
Uses ${locale} to determine pattern, we can change it to something else, but I think the flexibility is quite nice.

awesome! merged via 4214045


Launch date

This PR adds the two kickoff events to the website. You can preview them here, @ClaireWyatt please review them carefully and check for any mistakes (particularly with respect to affiliation, etc.):
https://899-267395254-gh.circle-artifacts.com/0/SORSE/programme/talks/event-001/index.html
https://899-267395254-gh.circle-artifacts.com/0/SORSE/programme/talks/event-002/index.html
They are also shown in the list of upcoming events and in the calendar
I also made a new post for the kickoff based on the text by @ClaireWyatt: https://899-267395254-gh.circle-artifacts.com/0/SORSE/programme/kickoff/index.html
There are still some todos. We need

[ ] the abstract by Kari Jordan
[ ] to show the introductory talk in the calendar
[ ] to adjust the order and exact timings of the talks

@ClaireWyatt, for the introductory talk, shall I make a separate event page? Or shall we just add a 15-minutes(?) slot to the calendar? I'd prefer to have an event page, but this needs a little abstract and info about the speaker.
@eileen-kuehn and @cc-a: How will the registration take place? Will one of you create an event in indico? I think it should be only one event, not two, right?
@eileen-kuehn: These events have not been submitted via indico as they are invited talks. Do you see any problems that I name them event-001 and event-002?

@Chilipp, @ClaireWyatt, the event lasts from 13:00-15:00, we do have

Welcoming words (10 mins?)
Presentation 1 (30 mins)
Presentation 2 (30 mins)

How do we make the timings? Does the first presentation start at 13:10? What is scheduled after the presentations? Does a discussion take place?

A registration link has already gone out with the announcement. We weren't able to to set up an Indico event in time.

hmm ok @cc-a. this is not what we say on the website...
But now we have to go for this. My apologies @eileen-kuehn, I did not realize that a registration link was already in the announcement email.

Apologies, we did want to go with Indico but with Claire going on annual leave from today things  were a bit rushed and nobody with access to Indico was available. We should be sticking with Indico for event registration going forward.
As Claire is unavailable would you like me to review this?
TBH I think what we use to do registration is a bit of an implementation detail and probably doesn't need to be mentioned on the website anyway...

As Claire is unavailable would you like me to review this?

yes please @cc-a, thanks :smiley:

TBH I think what we use to do registration is a bit of an implementation detail and probably doesn't need to be mentioned on the website anyway...

well, it's important in terms of the privacy notice because we have to declare what services we use and what happens with the sensible information, such as email-adresses, etc.

sounds good to me, thanks @cc-a! Do you know anything about the lengths of these sessions? Is the approach by @eileen-kuehn from above valid?

Welcoming words (10 mins)
Presentation 1 (30+10 mins)
Presentation 2 (30+10 mins)
Discussions & Networking (30 mins)

The date information in the "Add to Calendar" link for Office 365 doesn't seem to work correctly.

@cc-a, unfortunately I do not have an account there to debug it. Could you be a bit more explicit?

Timings look about right.
Calendar link tried to create an event but date/time info is missing and it defaults to the current time. Perhaps a separate issue can be created for this to avoid blocking this pr.

Perhaps a separate issue can be created for this to avoid blocking this pr.

Agreed, thanks. Can you open it? Ideally with a screenshot. I'll add the other events to the calendar.

@cc-a, I added the complementary events to the website and updated the links in my above comment. From my perspective, this is then ready to be merged and we'll make a new PR when we have the abstract by Kari Jordan. Please approve this PR if you agree to this.
I wonder whether we should highlight in the google form this is an exception and therefore deviates from our privacy notice.


"An error occurred during installation: No such plugin: cloudbees-folder"

I ran:
docker run -d --name=jenkins -p 8080:8080 -p 50000:50000 -v ~/jenkins:/var/jenkins_home jenkins

I got as far as the plugin config screen. Clicked on "Install selected plugins", got this error:
An error occurred during installation: No such plugin: cloudbees-folder

Only worked when I manually configured and deselected them all.
Docker version:
Client:
 Version:      1.13.0
 API version:  1.25
 Go version:   go1.7.3
 Git commit:   49bf474
 Built:        Tue Jan 17 09:58:26 2017
 OS/Arch:      linux/amd64

Server:
 Version:      1.13.0
 API version:  1.25 (minimum version 1.12)
 Go version:   go1.7.3
 Git commit:   49bf474
 Built:        Tue Jan 17 09:58:26 2017
 OS/Arch:      linux/amd64
 Experimental: false

Update: I removed the -v ~/jenkins:/var/jenkins_home and didn't run into any problems. Seems to be a problem with mounting the jenkins_home as a volume.

well, it depends on what you have in ~/jenkins that is breaking the installation

@carlossg There's nothing in it, it's a new folder created for the purpose of starting the container. It should not be erroring.

I ran into the same problem after installing Jenkins in Windows (not in Docker), and in my case it still happened if I deselected cloudbees. Shutting down Jenkins and restarting it fixed the issue and plugins installed fine.

I ran into this error as well with jenkins:2.32.3-alpine and without mounting any volume on Linux.

In my case the issue was the http proxy was not set.
I could see the following warning:
ci_1     | Mar 21, 2017 11:54:14 AM hudson.model.UpdateCenter updateDefaultSite
ci_1     | WARNING: Upgrading Jenkins. Failed to update the default Update Site 'default'. Plugin upgrades may fail.
ci_1     | net.sf.json.JSONException: Unquotted string 'h1'
ci_1     | 	at net.sf.json.util.JSONTokener.nextValue(JSONTokener.java:432)
ci_1     | 	at net.sf.json.JSONObject._fromJSONTokener(JSONObject.java:955)
ci_1     | 	at net.sf.json.JSONObject._fromString(JSONObject.java:1145)
ci_1     | 	at net.sf.json.JSONObject.fromObject(JSONObject.java:162)
ci_1     | 	at net.sf.json.JSONObject.fromObject(JSONObject.java:132)
ci_1     | 	at hudson.model.UpdateSite.updateData(UpdateSite.java:206)
ci_1     | 	at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:190)
ci_1     | 	at hudson.model.UpdateCenter.updateDefaultSite(UpdateCenter.java:2193)
ci_1     | 	at jenkins.install.SetupWizard.init(SetupWizard.java:168)
ci_1     | 	at jenkins.install.InstallState$3.initializeState(InstallState.java:105)
ci_1     | 	at jenkins.model.Jenkins.setInstallState(Jenkins.java:1057)
ci_1     | 	at jenkins.install.InstallUtil.proceedToNextStateFrom(InstallUtil.java:96)
ci_1     | 	at jenkins.model.Jenkins.<init>(Jenkins.java:947)
ci_1     | 	at hudson.model.Hudson.<init>(Hudson.java:85)
ci_1     | 	at hudson.model.Hudson.<init>(Hudson.java:81)
ci_1     | 	at hudson.WebAppMain$3.run(WebAppMain.java:231)

The solution was to set the proxy in JAVA_OPTS:
JAVA_OPTS=-Dhttp.proxyHost=${proxy_host} -Dhttp.proxyPort=${proxy_port} -Dhttps.proxyHost=${proxy_host} -Dhttps.proxyPort=${proxy_port}

I had the same error.
The origin of the problem was the JVM (java -version was java 7).
Once switched to Java 8 (.bash_profile), everything was resolved.

@wheelerlaw if you are saying that this command fails
docker run -d --name=jenkins -p 8080:8080 -p 50000:50000 -v ~/jenkins:/var/jenkins_home jenkins

and this command succeeds
docker run -d --name=jenkins -p 8080:8080 -p 50000:50000 jenkins

then it boils down to what permissions or content your ~/jenkins dir has. Have you checked the logs of jenkins for errors ?

@techyaura : thanks, restart works for me.

http://localhost:8080/restart worked on blueocean running in docker container running on Mac ...

Restart jenkins worked!

http://localhost:8080/restart Mac not working!

Changing this line
JAVA_CMD="$JENKINS_JAVA_CMD $JENKINS_JAVA_OPTIONS -DJENKINS_HOME=$JENKINS_HOME -jar $JENKINS_WAR"
to
JAVA_CMD="$JENKINS_JAVA_CMD -Dhudson.model.DownloadService.noSignatureCheck=true $JENKINS_JAVA_OPTIONS -DJENKINS_HOME=$JENKINS_HOME -jar $JENKINS_WAR"
in /etc/init.d/jenkins
should fix the problem...
worked on fedora 28

Same problem with Mac

Please check the NTP. If the system runs with incorrect time, this error could occur.

I met the config error after I ran the command docker run -u root --restart always -d -p 8090:8080 --name jenkins -p 50000:50000 -v jenkins-data:/var/jenkins_home -v /var/run/docker.sock:/var/run/docker.sock jenkinsci/blueocean serveral times when I was fixing docker network problem. I think there's must be something wrong with the directries in the volume.
So I delete volume jenkins-data through docker. And the error disappeared.

Changing this line
JAVA_CMD="$JENKINS_JAVA_CMD $JENKINS_JAVA_OPTIONS -DJENKINS_HOME=$JENKINS_HOME -jar $JENKINS_WAR"
to
JAVA_CMD="$JENKINS_JAVA_CMD -Dhudson.model.DownloadService.noSignatureCheck=true $JENKINS_JAVA_OPTIONS -DJENKINS_HOME=$JENKINS_HOME -jar $JENKINS_WAR"
in /etc/init.d/jenkins
should fix the problem...
worked on fedora 28

This did the trick for me, ty!

Update: I removed the -v ~/jenkins:/var/jenkins_home and didn't run into any problems. Seems to be a problem with mounting the jenkins_home as a volume.
I verified that ~/jenkins exists in my home directory, and it does.

it works for me

I set the JAVA_HOME in ~/.bash_profile like export JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.8.0_192.jdk/Contents/Home works

I faced the same issue while installing plugins in my docker container, it turned out to be a proxy issue. Changed proxy settings on my docker and it worked

restart worked for me.

restart is not work in mac.

Restart is not working on window 10

was the http proxy was not set.

modify /var/lib/docker/volumes/jenkins-data/_data/hudson.model.UpdateCenter.xml from https->http fix the problem

Changing this line
JAVA_CMD="$JENKINS_JAVA_CMD $JENKINS_JAVA_OPTIONS -DJENKINS_HOME=$JENKINS_HOME -jar $JENKINS_WAR"
to
JAVA_CMD="$JENKINS_JAVA_CMD -Dhudson.model.DownloadService.noSignatureCheck=true $JENKINS_JAVA_OPTIONS -DJENKINS_HOME=$JENKINS_HOME -jar $JENKINS_WAR"
in /etc/init.d/jenkins
should fix the problem...
worked on fedora 28

It work for me!
System Environment: centos 8
jenkins installation method:
wget http://pkg.jenkins-ci.org/redhat-stable/jenkins-2.7.3-1.1.noarch.rpm
rpm -ivh jenkins-2.7.3-1.1.noarch.rpm

Changing this line
JAVA_CMD="$JENKINS_JAVA_CMD $JENKINS_JAVA_OPTIONS -DJENKINS_HOME=$JENKINS_HOME -jar $JENKINS_WAR"
to
JAVA_CMD="$JENKINS_JAVA_CMD -Dhudson.model.DownloadService.noSignatureCheck=true $JENKINS_JAVA_OPTIONS -DJENKINS_HOME=$JENKINS_HOME -jar $JENKINS_WAR"
in /etc/init.d/jenkins
should fix the problem...
worked on fedora 28

worked for me , centos8

Hi Bros,
I also have the same issue, please help me. thanks,
************* cat docker-compose.yml************
version: '3'
services:
jenkins:
container_name: jenkins
image: jenkins:2.60.3
ports:
- "8080:8080"
- "50000:50000"
command run: docker-compose up -d
OS: "Ubuntu 20.04.3 LTS (Focal Fossa)"


Add circ_group_id on the get_items_for_bib method

child of #751
What is a circ_group_id? This is used by voyager to determine the circulation policy. In voyager it's used in circ_policy_group
What values would it have? numerical
Is any code actually using this value? We think no. We checked

orangelight
requests
marc_liberation
voyager_helpers

blocked by #844

Given that we couldn't find any use of this field, we're closing this issue.

Given that we couldn't find any use of this field, we're closing this issue.

Isn't it used here?
https://github.com/pulibrary/voyager_helpers/blob/e468d9ae29367d74ba7e09620238e801a7ce7bad/lib/voyager_helpers/liberator.rb#L914
It determines pickup location. Not sure what that governs.

Isn't it used here?
https://github.com/pulibrary/voyager_helpers/blob/e468d9ae29367d74ba7e09620238e801a7ce7bad/lib/voyager_helpers/liberator.rb#L914
It determines pickup location. Not sure what that governs.


all: first cut of README

Also add a LICENSE.

For ease of reading during review, https://github.com/cue-sh/unity/blob/readme/README.md is a rendered version of the README.

cc @mpvl @cedricgc

@mpvl @cedricgc I'm going to merge this PR because it will then allow us to kick the unity tyres with others. We can of course fix/improve/correct this README in follow-up PRs.


NVIDIA driver version bundled in Ubuntu Server container image is behind latest

Problem Description
The NVIDIA GPU driver version bundled in the "Ubuntu for Azure Batch container pools" is 460.32.03 (January 2021), which is behind the latest production version from NVIDIA (470 branch; July 2021). (See NVIDIA's driver lifecycle policy.)
Steps to Reproduce

Create a new pool using the "Ubuntu for Azure Batch container pools" VM image (Publisher: microsoft-azure-batch; Offer: ubuntu-server-container; Sku: 20-04-lts). Select a VM size in the NCv3 series. Enable container support for the pool nodes (set "Container configuration" to "Custom" in the pool creation UI).
Scale the pool up to 1 node.
Once the node reaches the "idle" state, SSH into it (this can be done easily with Batch Explorer).
Run the nvidia-smi command.

Expected Results
The GPU driver version on the node is in the 470 family, which is the latest production branch released by NVIDIA, released in July 2021.
Actual Results
The driver version is 460.32.03, released in January 2021:
batch-explorer-user@63c58fa129ae469aa7f4dbc8e4120775000000:~$ nvidia-smi
Tue Oct 26 17:18:31 2021
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 460.32.03    Driver Version: 460.32.03    CUDA Version: 11.2     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
(...)

Additional Logs
This can be additionally confirmed by manually starting an Azure VM, outside of Batch, using the "Ubuntu for Azure Batch container pools" image.
The VM's filesystem will contain the NVIDIA driver installer packages under the /opt/batch/bootstrap/ directory. The driver version can be seen to be 460.32.03, and the modification date on the installer files is in May 2021.
azureuser@batch-image-test:~$ ls -l /opt/batch/bootstrap/
total 852064
-rwxr-xr-x 1 azureuser azureuser      6379 May 11 21:30 azbatch_image_script.sh
-rw-r--r-- 1 azureuser azureuser 178089544 May 11 21:30 nc_nvidia.run
-rwxr-xr-x 1 root      root      250920763 May 11 21:38 nc_nvidia_custom.run
-rw-r--r-- 1 azureuser azureuser 183364599 May 11 21:30 nv_nvidia.run
-rwxr-xr-x 1 root      root      258650905 May 11 21:35 nv_nvidia_custom.run
-rw-r--r-- 1 azureuser azureuser   1474560 May 11 21:30 nvidia-docker.tar

azureuser@batch-image-test:~$ /opt/batch/bootstrap/nc_nvidia_custom.run --info

  Identification    : NVIDIA Accelerated Graphics Driver for Linux-x86_64 460.32.03
  Target directory  : NVIDIA-Linux-x86_64-460.32.03-custom
  Uncompressed size : 625302 KB
  Compression       : gzip
  Date of packaging : Tue May 11 21:37:00 UTC 2021
  Application run after extraction : ./nvidia-installer

  The directory NVIDIA-Linux-x86_64-460.32.03-custom will be removed after extraction.

Additonal Comments
My company is developing an integration between our software product and Azure Batch, but our product depends on a GPU driver version >= 470.42. We could potentially package a custom version of the Batch VM image with a new GPU driver installer, but for obvious reasons I would much prefer to stick to the official, verified, Microsoft-provided images.
As a note: the NVIDIA GPU driver extension for Azure Linux VMs is currently on the 470 branch, so it seems to be just the Batch-specific image that's behind on this (rather than Azure in general).

Hi, are there any updates on the status of/plans for the next Ubuntu container image release?

There was an issue building the Nvidia drivers which we believe has now been resolved in one of the newer driver releases for Linux. I can't give an exact time frame, but the driver build issue has hopefully been resolved which will unblock our build pipeline. I will update this thread when I have more definitive information.

Thank you @staer, I very much appreciate that and any further updates.

The driver should be updated to at least 470.82.01 on all the latest images. Our publishing of images doesn't directly coincide when new drivers are released though, so from time to time, the driver version may be a version or so behind.


az netappfiles account ad add -> ERROR: (BadRequest) An invalid value '' was received for KeySource"

when running "az netappfiles account ad add" i have suddenly started to get "ERROR: (BadRequest) An invalid value '' was received for KeySource"
Update: if i use rest API it works fine if i add the encryption property: https://docs.microsoft.com/en-us/rest/api/netapp/accounts/create-or-update

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

ID: 5545ff44-382e-bd41-4b15-b37e7a7196b7
Version Independent ID: 750bdcdf-1c28-db49-96aa-e09f5498ca34
Content: az netappfiles account ad
Content Source: latest/docs-ref-autogen/netappfiles/account/ad.yml
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

route to service team

Fixed with new az cli version:

azure-cli                         2.25.0

Just update Cli to new version and problem has been resolve, version before upgrade 2.24.0


View Site Manifest Button

🚀 Feature Request
Pretty simple, add a new button to navigate from /site/<siteId> to /site/<siteId>/manifest.

Use of Font Awesome Icon's component ( <FontAwesomeIcon/>) welcome.

May I take this issue?
I've sent a PR already :grinning:


[Event Request] Application “Tests-ERM”, Codeunit 134347 "ERM Document Line Tracking"

[Event Request] Application “Tests-ERM”, Codeunit 134347 "ERM Document Line Tracking"

Could you please insert the OnTestInitialize Event at the beginning of all test procedures?

Is there anything new about this issue? Still waiting for the event in BC16 CU1.


Files in dist folder still on version 2.0.3

The files in the dist folder are still on version 2.0.3. Please build these files for version 2.1.0.
Thanks

I goofed. 2.1.1 published


admin interface fails to connect

after starting with this command
docker run -d --name ejabberd -P     -e "XMPP_DOMAIN=foo.com"     -e<EMAIL_ADDRESS><EMAIL_ADDRESS>   -e "EJABBERD_AUTO_RANDPWD=true"     rroemhildjabberd

and connecting to 5280, I can see the TLS ports starting but I get no data to the browser:
02:18:05.737 [info] (#Port<0.7340>) Accepted connection <IP_ADDRESS>:51337 -> <IP_ADDRESS>:5280
02:18:05.738 [info] started: {p1_tls,{tlssock,#Port<0.7340>,#Port<0.7341>}}

You have to bind the container expose port 5280 to the outside port 5280 -p 5280:5280. Try the Quickstart example and see if this work for you.

ya I even have an ansible playbook here:
https://github.com/joshuacox/ejabberdocker-ansible-playbook
but I do not get a response on 5280 even though I can see it in the logs. I also stuck this in rancher to try it out another way, same results, viewing in the api gives me this:
{
"id": "1i4",
"type": "container",
"links": {
"self": "…/v1/projects/1a5/containers/1i4",
"account": "…/v1/projects/1a5/containers/1i4/account",
"credentials": "…/v1/projects/1a5/containers/1i4/credentials",
"hosts": "…/v1/projects/1a5/containers/1i4/hosts",
"instanceLabels": "…/v1/projects/1a5/containers/1i4/instancelabels",
"instanceLinks": "…/v1/projects/1a5/containers/1i4/instancelinks",
"instances": "…/v1/projects/1a5/containers/1i4/instances",
"loadBalancerTargets": "…/v1/projects/1a5/containers/1i4/loadbalancertargets",
"mounts": "…/v1/projects/1a5/containers/1i4/mounts",
"ports": "…/v1/projects/1a5/containers/1i4/ports",
"serviceEvents": "…/v1/projects/1a5/containers/1i4/serviceevents",
"serviceExposeMaps": "…/v1/projects/1a5/containers/1i4/serviceexposemaps",
"services": "…/v1/projects/1a5/containers/1i4/services",
"targetInstanceLinks": "…/v1/projects/1a5/containers/1i4/targetinstancelinks",
"volumes": "…/v1/projects/1a5/containers/1i4/volumes",
"stats": "…/v1/projects/1a5/containers/1i4/stats",
},
"actions": {
"update": "…/v1/projects/1a5/containers/1i4/?action=update",
"stop": "…/v1/projects/1a5/containers/1i4/?action=stop",
"restart": "…/v1/projects/1a5/containers/1i4/?action=restart",
"migrate": "…/v1/projects/1a5/containers/1i4/?action=migrate",
"logs": "…/v1/projects/1a5/containers/1i4/?action=logs",
"setlabels": "…/v1/projects/1a5/containers/1i4/?action=setlabels",
"execute": "…/v1/projects/1a5/containers/1i4/?action=execute",
},
"name": "ejabberd_ejabberd_1",
"state": "running",
"accountId": "1a5",
"build": null,
"capAdd": [ ],
"capDrop": [ ],
"command": null,
"cpuSet": null,
"cpuShares": null,
"created": "2015-06-21T05:42:47Z",
"createdTS":<PHONE_NUMBER>000,
"dataVolumes": [ ],
"dataVolumesFrom": [ ],
"description": null,
"devices": [ ],
"dns": [ ],
"dnsSearch": [ ],
"domainName": "webhosting.coop",
"entryPoint": null,
"environment": {
"XMPP_DOMAIN": "webhosting.coop",
"EJABBERD_ADMIN"<EMAIL_ADDRESS>"ERLANG_NODE": "ejabberd",
"EJABBERD_AUTO_RANDPWD": "true",
"TZ": "America/Chicago",
"EJABBERD_WEB_ADMIN_SSL": "true",
},
"externalId": "f6379b6205b6e97586cb33268f76cea380860b8b8c71440709f5b7edc17efa96",
"extraHosts": null,
"firstRunning": "2015-06-21T05:47:16Z",
"firstRunningTS":<PHONE_NUMBER>000,
"healthCheck": null,
"healthState": null,
"hostname": "jabber.webhosting.coop",
"imageUuid": "docker:rroemhild/ejabberd",
"kind": "container",
"labels": {
"io.rancher.project.name": "ejabberd",
"io.rancher.service.deployment.unit": "47f6cf69-159b-4a04-a083-23153ee36610",
"io.rancher.service.launch.config": "io.rancher.service.primary.launch.config",
"io.rancher.project_service.name": "ejabberd/ejabberd",
"io.rancher.scheduler.affinity:container_label_soft": "io.rancher.service.deployment.unit=47f6cf69-159b-4a04-a083-23153ee36610",
},
"logConfig": null,
"lxcConf": null,
"memory": null,
"memorySwap": null,
"nativeContainer": false,
"networkContainerId": null,
"networkMode": "managed",
"pidMode": null,
"ports": [ 4 items
"5222:5222/tcp",
"5269:5269/tcp",
"5280:5280/tcp",
"4560:4560/tcp",
],
"primaryIpAddress": "<IP_ADDRESS>",
"privileged": false,
"publishAllPorts": false,
"readOnly": false,
"registryCredentialId": null,
"removed": null,
"requestedHostId": "1h2",
"restartPolicy": {
"name": "always",
},
"securityOpt": null,
"startOnCreate": true,
"stdinOpen": true,
"systemContainer": null,
"transitioning": "no",
"transitioningMessage": null,
"transitioningProgress": null,
"tty": true,
"user": null,
"uuid": "de04a1bc-7092-42d8-9a1d-07f48de81deb",
"workingDir": null,
}

It seems you try to connect with http instead of https? Port 5280 is secured by default. You can set the envvar EJABBERD_WEB_ADMIN_SSL=false to disable SSL on port 5280.

Maybe the DEBUG loglevel has more information. Run with -e "LOGLEVEL=5" to enable DEBUG.

ok the errors in the log were indeed, merely, when I connected without https.  but if I
curl https://gist.github.com/joshuacox/3f359bec364e32e5f6c5|bash

it doesn't seem to be creating the admin user given this gist do I have a typo?
https://gist.github.com/joshuacox/3f359bec364e32e5f6c5

Readme typo fixed with https://github.com/rroemhild/docker-ejabberd/commit/680d6e7534bdf4b6e3f784bfa6cf580fecdbbf3b.


iOS 14 bug : swiping down the sheet do not pull down the sheet

Bug:
When you swipe down the view, it do not pull down gradually the sheet. When you swipe down enough it will close it suddenly. It was working great before and the bug appear only on iOS 14.
Code used :
`
    let transitionDelegate = SPStorkTransitioningDelegate()
    transitionDelegate.storkDelegate = navController
    transitionDelegate.customHeight = viewController.panelHeight
    transitionDelegate.confirmDelegate = navController
    navController.transitioningDelegate = transitionDelegate

    navController.modalPresentationStyle = .custom

    self.topNavigationController().present(navController, animated: true, completion: nil)`

У меня аналогичная проблема в iOS 14. Будет ли исправление данного бага?

the same

I can confirm this is also happening for me on ios 14. For me, the scroll view itself seems to be "stuck". Scrolling up does not scroll the view anymore.

It's also happening to me, you can only see the indicator that it's moving and the opacity behind the screen is being reduced. It just dimissess the view controller if dragged down enough.

If you guys have the luxury to target iOS 13, I recommend just rolling with the native modal. It was a painless switch.

@jhk115 agree

@jhk115 I agree, and for most of the part I believe we all do that. But @ivanvorobei has done an amazing job with possibilities for height customization, close button, indicator, etc. which makes us prefer to use this library.

It's also happening to me only on iOS 14, solved my problem after setting it
        if #available(iOS 11.0, *) {
            tableView.contentInsetAdjustmentBehavior = .never
        } else {
            automaticallyAdjustsScrollViewInsets = false
        }

This is happening because SPStorkPresentationController containerViewWillLayoutSubviews is setting the presented view controller's frame to frameOfPresentedViewInContainerView when pan gesture changed.

Any updates?

This is happening because SPStorkPresentationController containerViewWillLayoutSubviews is setting the presented view controller's frame to frameOfPresentedViewInContainerView when pan gesture changed.

Comment out these few lines fixes the problem. Did you find any side effects doing so? Thanks in advance.


Mocking localStorage when Unit Testing Modules using Pinia/Encrypt-Storage

Hi,
We are using Vue 3 and Pinia with Encrypt-Storage.
We are implementing some unit tests in Vue and we need to mock the localStorage behind Encrypt-Storage/Pinia.
As we are using Vitest, it seems the way to is using the following package vitest-localstorage-mock.
My questions are: Do you suggest any other way to implement the unit tests of the modules using Pinia/Encrypt-Storage ? Any code example?
Thanks,
Juan

Hi @jhuerta, hope you are doing well.
To be honest, I haven't used encrypt-storage with vitest yet.
I believe that you are performing tests of the encryption itself. Third-party package testing, just in case.
I would mock encrypt-storage and use a bypass. Mocking the value itself, or just encrypting with EncryptStorage.encryptValue and comparing the values.
I'm sorry for not answering earlier and if I didn't answer your question properly.
I'm pretty busy at work.
But I'm here and available.
Thanks.


ja: Make docs/tasks/tools/install-minikube.md follow v1.18 of the original text

This is a Feature Request

What would you like to be added
Update docs/tasks/tools/install-minikube.md to follow v1.18 of the original (English) text.
Why is this needed
content/ja/docs/tasks/tools/install-minikube.md is outdated.
Comments
/language ja
/good-first-issue
File to update
https://github.com/kubernetes/website/blob/dev-1.18-ja.1/content/ja/docs/tasks/tools/install-minikube.md
Original
https://github.com/kubernetes/website/blob/fb6364d/content/en/docs/tasks/tools/install-minikube.md
diff between translated and v1.18
https://gist.github.com/558d2d24fa80925864503e4275afd598
Note
Currently, we use dev-1.18-ja.1 branch. Please open a PR targeting the branch.
ref
https://kubernetes.io/ja/docs/contribute/localization/
If you have a question, feel free to ask us at slack.k8s.io #kubernetes-docs-ja channel

Hello @oke-py can I take this issue as my first contribution?

Of cource.

Alright thanks. I will ping you on Slack if I have some doubt as this would be my first contribution. You can assign this issue to me now.

You can assign this to yourself by adding a comment /assign.

/assign

/close
@kakts マージされるタイミングなら、closeの面倒まで見てもらえると助かります～


Could I use calico for docker container now?

I know that calico is used for k8s mostly, but for some specific scenarios, I have to configure the single container rather than pods. Obviously, docker is best for me, I would like to use calico for good performance in BGP mode.
I know that  docker run --driver calico  will fail now.
I'd like to ask could I use calico for docker? If not, can I use Calico directly in containerd?
I'm just starting to learn K8s, and K8s is a little difficult for me to deploy a lot of containers as pods cluster.
Thanks a lot.

@linhil out of curiosity, do you have a cluster of different docker containers or are you trying to set up connectivity to an existing K8s cluster from your container? I think that it could work in a container, but there is a lot of extra setup that is probably more work than learning how to set up a Kubernetes cluster (i.e. you will need to set up a separate etcd datastore and then modify the Calico configuration to talk to that datastore). I think it might be better in the long run to learn K8s rather than to try to learn enough about Calico in order to make this use case work.

I'd like to ask could I use calico for docker? If not, can I use Calico directly in containerd?

While this is possible in theory, its certainly not a scenario for beginners.

I'm just starting to learn K8s, and K8s is a little difficult for me to deploy a lot of containers as pods cluster.

If you're a beginner, may I suggest https://kind.sigs.k8s.io/docs/user/quick-start/ for setting up a k8s cluster?  Or micro-k8s, k3s or one of the other "run a k8s cluster on your laptop" tools?

Here's a tutorial for creating a kind cluster with Calico:
https://alexbrand.dev/post/creating-a-kind-cluster-with-calico-networking/

Here's a tutorial for creating a kind cluster with Calico: https://alexbrand.dev/post/creating-a-kind-cluster-with-calico-networking/

OK, I have just configured the etcd and calicoctl seperately without k8s. I'll try, thanks a lot


OpenSearch Circular dependency

Amplify CLI Version
12.13.0
Question
Describe the bug
I refer to the following official documents for configuration
https://docs.amplify.aws/react/build-a-backend/data/custom-business-logic/search-and-aggregate-queries/，
Steps 1-3 are successful, step 4 fails, execute npx ampx sandbox, the console prompt is as follows

Expected Behavior
It should not result in a circular dependency
Below is my repository link
https://github.com/1024cainiao/amplify-vite-react-template

Hi @1024cainiao,  Thank you for raising this. The link seems to be redirecting me to the same category-api repository. Could you please provide the correct repo link or share your backend.ts file so I can better understand the issue?

Hi @AnilMaktala I re-edited the link
Describe the bug
I refer to the following official documents for configuration
https://docs.amplify.aws/react/build-a-backend/data/custom-business-logic/search-and-aggregate-queries/，
Steps 1-3 are successful, step 4 fails, execute npx ampx sandbox, the console prompt is as follows
image
Expected Behavior
It should not result in a circular dependency
Below is my repository link
https://github.com/1024cainiao/amplify-vite-react-template

Hi @1024cainiao, Thanks for sharing the repo. After reviewing the backend.ts file, I noticed that at line 50, you're creating a new open-search-stack, which is leading to a circular dependency error. Try modifying it as shown below and let me know if that resolves the issue.
const openSearchStack = Stack.of(backend.data);

Hi @AnilMaktala, Thanks for your answer. Modified according to your description and the problem is solved.

@1024cainiao, Thanks for confirming. I'm glad to hear the issue has been resolved. I'll go ahead and close it now.


Use repeat section inside repeat section

I am trying to create a repeat section inside repeat section.
I got one of your fix from the below issue
https://github.com/formly-js/ngx-formly/issues/761
But when I tried to implement I am getting an error and I am not able achieve it.
Error "Property 'createControl' does not exist on type 'typeof FielsArrayType'.
Thanks in advance.

Hi,
How can I access the parent model when I am in the repeat section..?
And when I am in repeat section inside repeat section..?
Or what I am trying to achieve is..
Listing a category, different forms should be displayed based on the category.
Category 1 - form 1
Category 2 - form 2
For this basically I need the parent model inside the nested repeat.
Thanks in advance..

field.parent.model

I am getting an error.
'this.field.parent is undefined'

forgot to mention that parent feature has been added in 5.0.0-beta.2 version.

When will it be released..? Because I can't use a beta version.
Thanks

within 1 or 2 weeks we can have an RC release.

Great. Thank you.


fix user detail view (fixes #4303)

Not tested, if it works and there are travis issues, please correct them by yourself.

Fixed travis (prettify) and rebased.

@FinnStutzenstein After resting of master I found a new blocker: I can't set groups for an selected user in edit mode! Can you explain me how to fix it?


[FEATURE]Consider add support tortoise-orm?

https://github.com/tortoise/tortoise-orm

That support do you mean?

If anyone has used (or tried to use) tortoise-orm in combination with FastAPI, I'd be interested to hear about their experience.
I think it would make sense to add a reference to a blog article or similar if someone wrote one about using the two together.

I found that peewee has been introduced into FastAPI's documentation.
https://fastapi.tiangolo.com/tutorial/sql-databases-peewee/

There is a PR in progress that should make this easier: https://github.com/tortoise/tortoise-orm/pull/260

And here is a FastAPI + Tortoise ORM implementation: https://frankie567.github.io/fastapi-users/configuration/databases/tortoise/
I would really like to get it all working as I like the design of FastAPI, but isn't using it in any of my current work/projects. So any suggestions as to lowering the barrier of entry is welcome :-)

Also you can see this: https://github.com/prostomarkeloff/fastapi-tortoise

@jet10000 about the original question, yes, you can use Tortoise directly, it should work.

About Pydantic support directly in Tortoise, wow! That would be huge! :rocket:
Given that, we should definitely have a section in the docs dedicated to Tortoise after this is merged: https://github.com/tortoise/tortoise-orm/pull/276 :memo:
Having automatic Pydantic from ORM (or vice versa) has been a frequently-requested feature (although it's out of scope for FastAPI itself).
@timothycrosley sorry to spam you again, this is another example of these ideas, it might be closer than I thought!

We have finally released the first version of Tortoise ORM with pydantic serialisation support, and it is documented here: https://tortoise-orm.readthedocs.io/en/latest/contrib/pydantic.html
Could I ask that you please have a look. We are only doing serialisation from Tortoise at this stage, but plan to add Create/Update/Merge operations soonish.
(I rather wanted it to work well before we start adding more features).
We have an open issue where we are discussing next steps for this: https://github.com/tortoise/tortoise-orm/issues/315 where you are welcome to participate in.
Also, at this stage we only optimised some low-hanging fruit, and an entire sample app that we can benchmark against has not been done. I would like to be closer to feature complete before I do that — as in do an entire LCRUD sample, and benchmark it using Locust or some other scriptable benchmarking system.

Just an update, Even though what we did works fine for pydantic, fastapi handles things in specific ways:

We need a better way of handling List[] of item. (have a plan)
For create (and possibly update) we need to exclude read-only fields. https://fastapi.tiangolo.com/tutorial/extra-models/ proposes using inheritance to do that, but now we have to return multiple models, e.g. read-model & write-model. I can't think of an easy way to do this off the top of my head :thinking:
Model names must be globally unique (we didn't take that into account)

I'm fixing these in my quest to build a clean example, that can handle a bit more than the basic stuff.

@grigi that's awesome! :rocket:

[...] using inheritance [...]

Have in mind that that is only to reduce duplication. But the JSON Schemas are generated as if they were completely independent.
So, if generated models are multiple, for read, for write, etc. That's perfectly fine. The only reason to use inheritance is to avoid developer-typed code repetition. But if the model is generated that's perfectly fine.

Model names must be globally unique

I haven't been able to check how it would work with your new features, but we could think of ways of generating names for models generated on the fly or something similar, and this is probably not going to benefit only Tortoise-ORM, but others as well, e.g. someone could build a package that generates Pydantic models from SQLAlchemy models, and those would be generated as well.
So, the FastAPI side is not totally rigid :smile: If it makes sense, we can think of ways to update it.

There's a subtlety that I think it's easy to miss (but I think you caught it).
Pydantic itself doesn't do any async stuff. So, it can serialize already received data, but not fetch it using await automatically.
But if I understand correctly, the model would be generated from Tortoise to document and serialize the API and the path operation functions would serialize it with the generated model before returning, right?
So, something like:
from fastapi import FastAPI
from tortoise import fields
from tortoise.contrib.pydantic import pydantic_model_creator
from tortoise.models import Model

class Tournament(Model):
    """
    This references a Tournament
    """

    id = fields.IntField(pk=True)
    name = fields.CharField(max_length=100)
    #: The date-time the Tournament record was created at
    created_at = fields.DatetimeField(auto_now_add=True)

Tournament_Pydantic = pydantic_model_creator(Tournament)

app = FastAPI()

@app.get("/tournaments/{id}", response_model=Tournament_Pydantic)
async def read_tournament(id: int):
    tournament = await Tournament.get(id=id)
    return Tournament_Pydantic.from_tortoise_orm(tournament)

Thank you :moon:

Have in mind that that is only to reduce duplication. But the JSON Schemas are generated as if they were completely independent.

Ok, that's fine then. I did much the same.

Model names must be globally unique

I haven't been able to check how it would work with your new features, but we could think of ways of generating names for models generated on the fly or something similar, and this is probably not going to benefit only Tortoise-ORM, but others as well, e.g. someone could build a package that generates Pydantic models from SQLAlchemy models, and those would be generated as well.

That could work. The only other solution I could think of is to generate the model reference name (that needs to be unique) to be a hash. Which will work, just create somewhat messy schemas. I am doing this right now for self-referential models, but that could be solved better.
Self referential models are done by creating sub models N-levels deep, each with metadata re db query to be created. This works well to limit depth, but the depth is somewhat static now.
Using a hashed name for the exact config of the model would get rid of conflicts. e.g. Tournament_af3e7 as an internal de-duplication so we can re-use schemas more effectively?

There's a subtlety that I think it's easy to miss (but I think you caught it).
Pydantic itself doesn't do any async stuff. So, it can serialize already received data, but not fetch it using await automatically.

Yes, I ensure that all the I/O awaiting is done before I call Pydantic. I treat it much like one should treat templating. For predictable behaviour, no I/O should be done in the presentation layer.
I really would have gotten further with this, but got sick (and was basically sleeping for 2½ weeks) then the whole country gone into lockdown (and I have to help entertain the kids) So time has been limited the last, er. 5 weeks? And at least the next 3. And then existing PR's and bugs take priority :shrug:

Just an update on Tortoise's Pydantic integration.
I got some time to work on it some more, and I now generate globally unique definition indexes that is in <FQDN>.<6-char hash> format. (hash is mime32 alphabet, lowercase, so 30 bits effective)
The hash is dependant on entire model and depth-stack, so the same object can appear multiple times, but they have different contexts.
Leaf-node schemas (e.g. default model, but excluding all relations as children) is a detected special case, and given the special hash of leaf, this is to minimise the schema size. I found it reduced some schemas by ⅓ in size.
I also don't have a hash portion if the schema is entierly default, and it is the root.
@tiangolo Is such naming convention good?
Some examples:

tests.testmodels.Reporter.leaf
tests.testmodels.Event.b4oydv
tests.test_early_init.Tournament

I specify a title of just the base name, e.g. Reporter, Event, etc...
I still am going to add aliases so one can rename some entries. Then I think it will be basically feature complete.
How do we go about of adding documentation to FastAPI? I have some basic Pydantic tutorials here: https://tortoise-orm.readthedocs.io/en/latest/contrib/pydantic.html#contrib-pydantic and a simple FastAPI example here: https://tortoise-orm.readthedocs.io/en/latest/examples/fastapi.html

Exciting news!!!
And how to write test code when FastAPI and tortoise-orm cooperate?
for example:
some testcases need use the Restful API to insert data and query results by ORM.
Looking forward to very much, If I can do anything, please let me know.

The testing thing is going to be interesting.
Using the proposed system to do a request/response ONLY is going to work. but having an async context available where you can edit/check on state and mix it with the request/response tester...
the issue is the test runner creates a new event loop for every test, and the DB connection expects a single event loop.
Also, only one event loop per thread is allowed, so you'll get multiple-event-loop errors before you even got to running the tests.
Also, creating a new loop and booting up all async connections for every test is just terribly slow.
But we need to get it working first.
The solution will likely require changing the test runner...

Just for completeness sake: We have a basic test example here: https://tortoise-orm.readthedocs.io/en/develop/examples/fastapi.html#tests-py
It's not perfect (as in it doesn't "flow" nicely) But it works.

@dmontagu I have been using Fastapi with Tortoise-orm for relational stuff for last few months.
Don't really have time as of now to write blog. So some short notes of my experience:
I would usually declare the pydantic schema for the create requests and inherit it for responses(which contains id etc). Then in the views, I return a dict either using the .values() for filters or .__dict__ for single object.
Lack of timezone support sucks and I had to declare datetime fields without auto_now or auto_now_add, which I extensively used in django. Then I would have to manually modify the table and change the field type from timestamp to timestamptz and in the code, populate those fields using datetime.now(pytz.utc).
Another issue is migrations. Tried to integrate Aerich as it seemed as the only alternative but couldn't downgrade easily(https://github.com/tortoise/aerich/issues/72).
Another problem I faced was using celery with Tortoise-orm. Even with celery 5. I just couldn't make it work as celery doesn't support asyncio and using asyncio or asgiref was raising some pool closed error. As a quick workaround, I just made an internal REST endpoint in the fastapi app which calls the async related stuff and called them from the tasks. There's definitely a better way, but that's for another thread.

@anindyamanna , can you example how can i make relation correctly ? I used ForeignKeyField, but no appear column on swagger and appear error:
{
"detail": [
{
"loc": [],
"msg": "(1048, "Column 'membro_group_id' cannot be null")",
"type": "IntegrityError"
}
]
}

where is auto increment =True


Adding a rotation parameter in the visbrain_plot function

Hello,
It could be good to add a simple feature to offer views of meshes with different view points (typically azimuth and elevation).
Several strategies:

One way could consist in applying a transformation to the mesh in the visbrain_plot function. It may be a problem that the mesh remains rotated after the visualization. A possibility to compensate the rotation once the figure is closed ?
Another way could be to rotate the camera of the scene but it seems to be less obvious to retrive the good attributes in the Scene Obj

Ty @JulienLefevreMars for Issue. It would be a nice feature indeed. To be dig further after the slam and vector field meeting depending on what will be decided :)


Too long quote

Some quotes are too long for the card to contain. Provide some customization to the card might solve the problem.

To be specific, the quote is from Ken Thompson speaking about how modern programming scares him in many respects with the following explanations for  4 - 5 sentences which is very long.

hmm i guess... we can probably add a string length check.
Do lemme know If you wanna give PR.
This needs to be refactored...
https://github.com/PiyushSuthar/github-readme-quotes/blob/74a520fd76111ae2c5ef4a1b2ce6ca032431dcdc/src/fetcher/fetchQuotes.js#L11


defichain: BlockAdded does not get called (block not found)

Describe the bug
Not sure if it is appropriate to ask here, but hope to get some guidance anyway:
I've been trying to replace bitcoind with defid (defichain is bitcoin fork I believe) but indexer / badger-db does not save blocks / txs;
running online mainnet (after sync)
req:
curl -d '{"network_identifier": {"blockchain": "DFI", "network": "Mainnet"}, "block_identifier": {"index": 1}}' localhost:8080/block

resp:
{"code":4,"message":"Block not found","retriable":false,"details":{"context":
"block not found: {\"index\":1}"}}

some logs around request:
2021-02-15T13:36:56.556Z        DEBUG   bitcoind        bitcoin/node.go:56      UpdateTip: new best=be3a3f6c3979bf28d081f8da482a8f02f457d85fbb47d74273252043f2dc4f10 height=646393 version=0x20000000 log2_work=79.507669 tx=1472991 date='2021-02-15T13:36:56Z' progress=1.000000 cache=0.0MiB(257txo)
2021-02-15T13:38:19.846Z        DEBUG   bitcoind        bitcoin/node.go:56      UpdateTip: new best=b4138c1c7934665a702f44ba3275ef18ae11164093dfdebf17a7a514452ff71a height=646394 version=0x20000000 log2_work=79.507671 tx=1473004 date='2021-02-15T13:38:18Z' progress=1.000000 cache=0.0MiB(266txo)
2021-02-15T13:38:23.321Z        DEBUG   memory  utils/utils.go:62       stats   {"heap (MB)": 4433.795745849609, "max heap (MB)": 4479.408668518066, "stack (MB)": 3.59375, "system (MB)": 5066.585372924805, "garbage collections": 84}
2021-02-15T13:39:07.317Z        DEBUG   server  services/logger.go:57   POST    {"code": 500, "uri": "/block", "time": "10.537418ms"}

reading logs I see that BlockAdded does not get called
// BlockAdded is called by the syncer when a block is added.
func (i *Indexer) BlockAdded(ctx context.Context, block *types.Block) error {
	//FIXME: delete
	fmt.Printf("BlockAdded got called; block: %v\n", block)

I wonder if I missed some configuration change or there is some difference in defichain that should be respected?
To Reproduce
Steps to reproduce the behavior:
defichain uses different ports:
	// mainnetRPCPort = 8332
	// testnetRPCPort = 18332
	mainnetRPCPort = 8554
	testnetRPCPort = 18554

bitcoin-mainnet.conf
datadir=/data/bitcoind
bind=<IP_ADDRESS>
rpcbind=<IP_ADDRESS>
bantime=15
rpcallowip=<IP_ADDRESS>/0
rpcthreads=16
rpcworkqueue=1000
disablewallet=1
txindex=0
port=8555
rpcport=8554
rpcuser=rosetta
rpcpassword=rosetta

# allow manual pruning
prune=1

bitcoin.json
{
 "network": {
  "blockchain": "DFI",
  "network": "mainnet"
 },
 "online_url": "http://localhost:8080",
 "data_directory": "",
 "http_timeout": 10,
 "sync_concurrency": 8,
 "transaction_concurrency": 16,
 "tip_delay": 300,
 "disable_memory_limit": false,
 "log_configuration": false,
 "data": {
  "historical_balance_disabled": true
 }
}

bitcoin/types.go
	Blockchain string = "DFI"
	// Blockchain string = "Bitcoin"
...
	MainnetGenesisBlockIdentifier = &types.BlockIdentifier{
		// Hash: "000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f",
		Hash: "279b1a87aedc7b9471d4ad4e5f12967ab6259926cd097ade188dfcf22ebfe72a",
        }
...
	MainnetCurrency = &types.Currency{
		Symbol:   "DFI",
		Decimals: Decimals,
	}

rosetta-cli-conf/mainnet/config.json
{
  "network": {
    "blockchain": "DFI",
    "network": "mainnet"
  },
  "data_directory": "cli-data",
  "http_timeout": 300,
  "max_retries": 5,
  "max_online_connections": 1000,
  "tip_delay": 1800,
  "compression_disabled": true,
  "memory_limit_disabled": true,
  "data": {
    "initial_balance_fetch_disabled": true,
    "end_conditions": {
      "reconciliation_coverage": {
        "coverage": 0.95,
        "from_tip": true
      }
    }
  }
}

Thanks for your work on this @GrailFinder
DeFiChain's also having a repo working on the integration. WIP: https://github.com/coinbase/rosetta-bitcoin/pull/70


Allow using elements in logo attribution options

Follow-up to https://github.com/openlayers/ol3/pull/5193
This commit lets the user use an element object instead of a {src: href} object for an attribution logo when creating a map. This opens a lot of possibilities for that logo, for example setting the target to force the logo to open in a new tab when clicked.
However, there is a problem that I couldn't resolve. When using this method, the chrome debugger console shows a single failed GET request to [current url]/logo. I wasn't able to pinpoint where that request was being made. The example I created has that problem.

Please disregard all but my first comments. The problem is with keying the logo. You should not add Element logos to the logos cache (which is only for not creating an element over and over). So instead of adding your element to the cache as logos['logo'] = ..., don't add it at all.

I have added more comments inline now, which should help you fix this.

Thanks for your help. I applied your suggestions and everything seems to work correctly now.

I forgot to mention, this PR is ready for review.

Is there something more required for this to be reviewed ?  Thanks.

This looks good now, thanks @samuellapointe.

Thank you, @ahocevar.


Changes to resourcebased.md to match Core 2.0

Internal Review Page
AuthorizeAsync method returns Task<AuthorizationResult> instead of Task<bool> in 2.0.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

Closing & reopening to trigger build.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@jansivans Thank you for taking the time to address this, and congratulations on your first docs contribution!


harmonyhubjs Windows x64: file dependencies have exceeded the 255 character limit for folder path and file name

bugger..  263 characters...   limit is 255.  why are the folders so deep.. any way around this?
C:\Program Files\nodejs\node_modules\homebridge\node_modules\harmonyhubjs-client\node_modules\node-xmpp-client\node_modules\request\node_modules\har-validator\node_modules\is-my-json-valid\node_modules\generate-object-property\node_modules\is-property.npmignore

if only the word "node_modules"  was shorter, this would be a non-issue.  also if projects would pull in some of the code from other node_modules rather than linking them :)

Try to long path tool. It is very helpful.


Changing the value of private ip is not supported.

Could you update this document ?

@hisasima : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@hisasima : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


XLA:CPU incorrect values with jax.lax.cond inside jax.lax.scan

In the following code, jax.lax.scan gives an incorrect gradient while scan copy-pasted from the documentation gives the correct gradient (tested against finite difference). The correct gradient is 108 but jax returns 324.0.

import jax
import jax.numpy as jnp

def scan(f, init, xs, length=None):
  if xs is None:
    xs = [None] * length
  carry = init
  ys = []
  for x in xs:
    carry, y = f(carry, x)
    ys.append(y)
  return carry, None

def _while_loop(cond_fun, body_fun, init_val, max_iter, scan_fun):
  def _iter(val):
    next_val = body_fun(val)
    next_cond = cond_fun(next_val)
    return next_val, next_cond

  def _fun(tup, it):
    val, cond = tup
    # When cond is met, we start doing noops.
    return jax.lax.cond(cond, _iter, lambda x: (x, False), val), it

  init = (init_val, cond_fun(init_val))
  return scan_fun(_fun, init, None, length=max_iter)[0][0]

def test1(scan_fun):
  def my_pow(x, y):
    def body_fun(val):
      return val * x
    def cond_fun(val):
      return True

    return _while_loop(cond_fun=cond_fun, body_fun=body_fun, init_val=1.0,
                       max_iter=y, scan_fun=scan_fun)

  print(my_pow(3, 4), pow(3, 4))

  # Correct gradient when using scan_fun = scan
  # Incorrect gradient when using scan_fun = jax.lax.scan
  eps = 1e-5
  print(jax.grad(my_pow)(3.0, 4),
        (my_pow(3.0 + eps, 4) - my_pow(3.0 - eps, 4)) / (2 * eps))

def test2(scan_fun):
  def my_pow(x, y, max_val):
    def body_fun(val):
      return val * x
    def cond_fun(val):
      return val < max_val

    return _while_loop(cond_fun=cond_fun, body_fun=body_fun, init_val=1.0,
                      max_iter=y, scan_fun=scan_fun)

  # We asked for pow(3, 6) but due to max_val, we get pow(3, 4).
  print(my_pow(3, 6, max_val=81), pow(3, 4))

  # Correct gradient when using scan_fun = scan
  # Incorrect gradient when using scan_fun = jax.lax.scan
  print(jax.grad(my_pow)(3.0, 6, max_val=81),
        jax.grad(jnp.power)(3.0, 4))

if __name__ == '__main__':
  scan_fun = jax.lax.scan
  #scan_fun = scan

  print("test1")
  test1(scan_fun)

  print("test2")
  test2(scan_fun)

Thanks for the report!
The same doesn't seem to happen with forward-mode: I changed the calls to jax.grad to calls to `deriv:
def deriv(f):
  return lambda x, *args,  **kwargs: jax.jvp(lambda x: f(x, *args, **kwargs), (x,), (1.0,))[1]

And got this:
test1
81.0 81
108.0 108.3374
test2
81.0 81
108.0 108.0

That suggests to me there's an issue with transposition here...

Wow, this had us scratching our heads for a bit, since everything looked fine on the JAX side. Then we realized: this might be an XLA:CPU bug! Two strong lines of evidence to suggest that:

I ran it on a TPU colab and there was no discrepancy;
if we change this line to call _scan_impl_unrolled, which is a pure Python evaluation procedure for scan,  instead of _scan_impl_loop, which executes an XLA While loop, then there's no discrepancy.

So I think we've got to file this with XLA:CPU folks, as there may be a miscompile of this loop-of-cond program on CPU.
I slightly simplified the repro to this:
import jax
import jax.numpy as jnp

def deriv(f):
  return lambda x, *args: jax.jvp(lambda x: f(x, *args), (x,), (1.0,))[1]

def deriv2(f):
  return lambda x, *args: jax.linearize(lambda x: f(x, *args), x)[1](1.0)

def _while_loop(cond_fun, body_fun, init_val, max_iter):
  def _iter(val):
    return body_fun(val), cond_fun(val)

  def _fun(tup, _):
    val, cond = tup
    # jax.lax.cond(cond, _iter, _iter, val), _   # this works!
    return jax.lax.cond(cond, _iter, lambda x: (x, False), val), _

  init = (init_val, cond_fun(init_val))
  return jax.lax.scan(_fun, init, None, length=max_iter)[0][0]

def test1():
  def my_pow(x, y):
    def body_fun(val):
      return val * x
    def cond_fun(val):
      return True

    return _while_loop(cond_fun, body_fun, 1.0, y)

  x = 3.0
  n = 1

  eps = 1e-5
  print(deriv(my_pow)(x, n),
        (my_pow(x + eps, n) - my_pow(x - eps, n)) / (2 * eps))
  print(deriv2(my_pow)(x, n),
        (my_pow(x + eps, n) - my_pow(x - eps, n)) / (2 * eps))

test1()

1.0 1.001358
3.0 1.001358

Notice that jvp works, while linearize doesn't. That is, we don't even need to involve reverse-mode (and transposition).
As in the OP here, the predicate value to the conditional is always True.

Ah, another twist to the story! This is definitely an XLA bug, but it's already fixed at HEAD. That is, if you build jaxlib yourself this bug won't occur. The problem is it's not fixed in our jaxlib== binary release.
For Google-internal folks: the test in cl/356908804, basically with the above repro but set up to easily test on CPU/GPU/TPU, passes at HEAD.
So the fix for this is for us to release a new jaxlib. The workaround is to build your own jaxlib. (Unfortunately, downgrading doesn't work, as this bug seems to be present in jaxlib==0.1.60, and jaxlib==0.1.59 isn't compatible with the master version of jax so I didn't even check it.)

I forgot to mention: big thanks to @hawkinsp for guiding me through this debugging process. I learned a ton.

I set #5956 to close this issue because we're confident that the next jaxlib release will fix it (as will building jaxlib from master right now). We'll work on a jaxlib release now!

Thanks for the investigation and for the non-regression test!


feat: provision and use mTLS credentials

What this PR does / why we need it:
Adds mTLS authentication between ControlPlanes and DataPlanes using the functionality provided by https://github.com/Kong/kubernetes-ingress-controller/pull/2148
Which issue this PR fixes fix #7
Special notes for your reviewer:

~The subject for the ControlPlane certificate is an arbitrary example. Is there something we should be using here? All the nginx side will care about is that it's signed by the CA; it has no expectation for the subject.~ The control plane subject is now <controlplane.Name>.<controlplane.Namespace> as a less placeholder arbitrary subject.
This lacks any handling of certificate rotation. This seems like something we'll need but that is large enough to require its own spike about exactly how to handle it: https://github.com/Kong/gateway-operator/issues/108
With the expectation that DataPlanes and ControlPlanes can reside in any namespace, and that we need to check for existing certificates, this requires a cluster-wide Secret Get permission. Is there any way we can avoid this?
~The user-provided cluster CA Secret must live in the operator's namespace, which is hard-coded right now. Do we have any existing tooling to retrieve this (our own or something in controller-runtime)? I've hardcoded kong-system for now.~ I added a downward API envvar to the operator Deployment and access it directly to determine the CA Secret namespace.
Although the original issue includes it in requirements, this does not implement deletion because there's currently no deletion handling in the reconcilers at all. Why was that missing? Is cleanup in general tracked elsewhere?

PR Readiness Checklist:
Complete these before marking the PR as ready to review:

[x] the CHANGELOG.md release notes have been updated to reflect significant changes

Nothing much on the draft version, so handled some of the simpler items and marking it ready to try and force the others.

I'm taking the :heavy_check_mark: as implicit approval of handling rotation in a separate PR. @shaneutt did you have thoughts on the other two open items in the OP, i.e. handling deletion and the additional Secret permissions?

I'm taking the heavy_check_mark as implicit approval of handling rotation in a separate PR. @shaneutt did you have thoughts on the other two open items in the OP, i.e. handling deletion and the additional Secret permissions?

I'm OK with rotation and deletion being handled as separate issues. I might need clarification about the permissions part, if we just mean the permissions needed to manage secrets in this way at all we need those immediately in this PR or a user will have to manually modify the manifests for the operator to work at all.

I might need clarification about the permissions part, if we just mean the permissions needed to manage secrets in this way at all we need those immediately in this PR or a user will have to manually modify the manifests for the operator to work at all.

We don't currently have permissions to Secrets. To check if we already have certificates in ControlPlane/DataPlane namespaces (which can be any namespace), we need to add Get permissions, granting access to any Secret. This PR includes modifications that add a role that grants access to all Secrets in all namespaces.
This is a sensitive permission that we'd like to avoid if possible, to decrease attack surface for Secret leaks and ease installation if you don't have cluster-wide Secret permissions yourself. I don't think we can really do that without restricting the namespaces that our Deployments can live in.
Restricting namespaces may be viable (offhand I don't know of a reason they'd need to share a namespace with an application we don't already account for), but absent a single blessed namepace (which would pose problems for multi-tenant installs that shouldn't have access to other tenants' Secrets), isn't something we can immediately do with the existing manifests. You'd need something like the --watch-namespaces+chart role automation or manual kustomize work to update namespaces and duplicate the role.

Ok, then I'm :heavy_check_mark: once we have a follow-up issue in place to further discuss and try to reduce the scope of Secrets privileges.

Alright, https://github.com/Kong/gateway-operator/issues/121, and deletion?
Unrelated to that, there's apparently some dependency nonsense I need to sort out? Attempting to merge go.sum by stripping merge annotations and tidying resulted in:
github.com/kong/gateway-operator/controllers imports
	github.com/cloudflare/cfssl/signer/local imports
	github.com/google/certificate-transparency-go imports
	go.etcd.io/etcd/v3 imports
	go.etcd.io/etcd/tests/v3/integration imports
	go.etcd.io/etcd/pkg/v3/logutil: module go.etcd.io/etcd/pkg/v3@latest found (v3.5.4), but does not contain package go.etcd.io/etcd/pkg/v3/logutil

Go had already updated go.etcd.io/etcd/pkg/v3 and but had not updated and was still trying to use versions of go.etcd.io/etcd/tests/v3/integration and such. Getting those outdated packages manually fixed it.
No luck on getting the deletes question answered, it seems, so just gonna mark this ready to merge and figure that out later :shrug:


Mark as instrumental "此歌曲为没有填词的纯音乐，请您欣赏"

Chinese lyric sources with this message mean that the thing has no lyrics. OpenLyrics should treat them as such.
There's also "纯音乐，请欣赏"

Right-click -> Auto-edit -> Mark as instrumental
I'm not making automated decisions that modify user data on the basis of the particular text retrieved in lyrics. That's too error prone.
I might consider making this user-configurable (so you can decide what you want to be considered instrumental automatically), but that's a larger topic. I expect genre to be a good first approximation for this too, so I'm going to say this falls under the umbrella of #202

How is it error prone? This exact text is only present in instrumentals.

@jacquesh Maybe you could narrow the criteria to add that this is the only line?

I'm not hard-coding a comparison of retrieved lyric data (which could be literally any text data) with some arbitrary string. There are several reasons not to do that, but one is that if the text were to change slightly (which could easily happen, they add a space, put an extra newline in there somewhere, remove the comma, etc) then this matching would break out of the blue.
As I say, I'd consider adding something configurable for it but if I can, I'd rather get 80% of the way there with some other lower-variance piece of data like genre and then the remaining 20% can be covered by manual edits.

The lyric is already there. They don't have some sort of special case for instrumentals, it's just a template lyrics file. Existing ones will stay the same, and if such a change happens only new matchings would break, which isn't that horrible.

Hi @jacquesh , the message still hasn't changed. Could this be implemented?

If songlyrics.cpp compares the result against a hardcoded string, why can't netease do it as well?

Fair enough.


settings.json color pallet refresh bug

VSCode Version:Version: 1.49.0-insider (system setup)
OS Version: Windows_NT x64 10.0.19041

Steps to Reproduce:

Open Code > settings.json
semanticTokenColorCustomizations > change color > save.

As soon as you save, the color picker mouse pointer "resets" to the previous color.
Please note that workbench.colorCustomizations > change color > save works fine.

Does this issue occur when all extensions are disabled?: Yes

@hiredtocode Sorry, the steps are too compressed. What do you mean by Open Code > settings.json > F5 and semanticTokenColorCustomizations > change color > save.
What is the the color picker mouse pointer? Maybe add some screenshots to clarify. Thanks!

@aeschli I was trying to make screenshots and create a reply but it was a bit comber-sum so I decided to make a short video so it's clear for both of us to diagnose this bug. Here's the link : https://youtu.be/q-JCOE5hKu4
Let me know if it's not clear. Thanks.

@hiredtocode Thanks a lot for the video! I can reproduce the issue.

@rebornix Seems to be an issue with the color picker:

Have the settings:

{
    "json.trace.server": "verbose",
    "files.autoSave": "off",
    "editor.semanticTokenColorCustomizations": {
        "rules": {
            "*.declaration": "#000000"
        }
    }
}

hover over the color decorator, in the color picker, change the color to all black
press save while the color picker is open
color picker switches to white (value is still black)

Looking at the JSON Language Server log:

the black color information is correctly returned after the document update
the color picker then asks for the color presentation of the white color to which the JSON server response to that request with the formatted white color. The color picker seems to hold on to the white.

Nvm, verified it locally, sorry about that


split default bindings into smaller files?

the key bindings files are getting quite big like global.lua.
would it make sense to split it into smaller files, eg. global_timeline.lua, global_commands.lua.
what do you think

I think it's alright as it is!
To be honest, I think the most pertinent issue for this repository is some of the usability concerns with the auto-complete window. Some things to investigate are:

Is there a way to de-focus the window automatically if it gains focus?
A pop-up dialog could appear after the first keypress which gives basic instructions to starter users, with an option to hide it forever. It would say something like: 'Welcome to Reaper Keys! Start using by defocusing the autocomplete window, and typing some keys. To get you started, press  (Alt+X) to pull up a list of bindings that you can filter. Your first quest is to learn the timeline_operators, as these are the most used - so set the binding list to only display all the timeline_operators and try them out one by one! If a 'script is running in the background' dialog pop's up, just select 'new instance' and 'remember'. Check out the 'definitions' directory in the Reaper-Keys folder to customize Reaper Keys. I hope you make some great music!'

If you are looking for ways to help (much appreciated btw), those two issues would have the most impact on users I believe.

I agree. Those are important features.
I haven’t had time to dive into gui and windws so much. But looking fwd to it.


Update train_util.py to allow for using SGD without momentum

Using momentum increases VRAM requirement by quite a bit, since you have to keep track of past gradients.  momentum=0 might not be optimal, but is nice to have if you're using low-memory GPUs.

can you give some information regarding what is SGD  and momentum?

SGD is stocastic gradient descent optimizer here:
https://en.wikipedia.org/wiki/Stochastic_gradient_descent
https://pytorch.org/docs/stable/generated/torch.optim.SGD.html
Momentum uses past gradients to improve convergence.  It works nice, but also increases VRAM usage quite a bit.  momentum=0 uses less VRAM, allowing training on older GPUs.

@ddpasa thanks a lot for explanation

@kohya-ss what do you think?  Is this okay to merge?

It's kind of funny to call it SGDNesterov because the underlying optimizer used is just pytorch SGD, which supports SGD with or without Nesterov momentum.  The most ideal solution is to rename it to just SGD, but that would probably break too many things.


Wrong mod version

Using the 1.1.5 from modrinth shows v1.1.4 in the mod list.

curseforge too

aparently all versions show one behind.
modrinth: 1.1.4
me: 1.1.3
ect.

already posted:
https://github.com/SHsuperCM/CITResewn/issues/387


Bind-mount /dev/fuse when launching osgvo-docker-pilot via singularity

SOFTWARE-5521
Also remove the note that says they can't run payloads in a separate image; this will let them do it.

CI failures unrelated, merging


Trying to deploy a massive contract fails with no error output

Likely an issue with cpp-ethereum's RPC API.

See the blake2b example here which turns into a 64kb wasm binary:
https://github.com/jwasinger/rust-ewasm/tree/blake2b

Got this error while trying to deploy the blake2b example: Block gas limit reached
Error: Error: [ethjs-rpc] rpc error with payload {…dRawTransaction"} Error: Block gas limit reached."

Yup.  We will have to preload these "precompiles" in the genesis.


Datacenter ESU Required?

I don't think this article makes clear whether it is mandatory to use a Datacenter ESU on a physical machine that is running Server 2012 R2 Datacenter, even if it's not hosting any VMs.  Would it be acceptable to purchase a 16-core Standard ESU for a 16-core physical Windows Server 2012 R2 Datacenter server?

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

ID: f2a45ff4-73c7-9aa6-4bf2-a60e004e920b
Version Independent ID: 571b6515-1040-26a3-f56d-6c5c1ce87d90
Content: License provisioning guidelines for Extended Security Updates for Windows Server 2012 - Azure Arc
Content Source: articles/azure-arc/servers/license-extended-security-updates.md
Service: azure-arc
Sub-service: azure-arc-servers
GitHub Login: @johnmarco
Microsoft Alias: johnmarc

@simc-pk Thanks for your comment! We will review and provide an update as appropriate.

Hello @simc-pk . Apologies for the long delay in replying to this issue. In case you still need an answer, I checked with a product rep. ESUs don't require "matching" of types between standard and Datacenter. The document in question has been revised serveral times since you posted this issue, but I will take closer look at it and try to qualify this situation. In the meantime, I will now close this issue.

#please-close


replace the native windows explorer.

Is your feature request related to a problem? Please describe.
i'm always frustrated when i press the button of  downloads  in chrome and then the native windows explorer is opened,but i want the Files UWP open.
Describe the solution you'd like
just like i describe above, i wish the uwp can replace the native windows explorer.
Describe alternatives you've considered
may be modify the reg.
Additional context
the latest version in Microsoft Store

You can follow this guide for instructions on settings Files as the default https://github.com/files-community/Files/wiki/Replacing-File-Explorer-with-Files-(Unsupported).


LSNBLDR-815: Fixed display of unordered lists in rich-text blocks

Reverses #4458

I think we might be able to achieve a fix for both LSNBLDR-769 and -815 if we qualify the ul class in the two instances of the selector ".split ul" in Simplepagetool.css, such that the selector is revised to ".split ul.mainList".

I've updated my LSNBLDR-815 branch to accommodate the display of unordered lists across two columns, and it does so by changing the ".split ul" selector to ".split ul.mainList". Furthermore, I've added padding and margin to the bottom of unordered lists in Lessons; otherwise, paragraphs following those lists would not have enough whitespace separating the two.
For what it's worth, the list-style-type such for the unordered list displayed on the Lessons page does not match the display of the same list in CKEditor. This seems to be due to the nesting of user-contributed lists within the ul.mainList predefined by the Lessons tool. Because the setting of list-style-type is deferred to the browser, there doesn't seem to be an elegant way to establish true WYSIWYG with respect to these lists in Lessons. I'm wondering if rewriting the Lessons page HTML to use div elements instead of ul and li for representing page items would be a better approach long-term. (Maybe a Sakai 13 project?)

Is there a compelling reason to keep the ul.mainList and li elements as ul and li instead of using div? Using div for page items seems like we can make the styling rich-text blocks in Lessons more consistent with other Sakai tools.
With some cursory experimentation, I'm observing that this swap could happen more easily than I previously expected. I've update my LSNBLDR-815 branch to reflect this change, though I wouldn't be surprised if I overlooked something.

My latest commit repairs the add and delete item actions associated with each item and fixes the add button at the bottom of a section/column. All the repairs needed in this commit are in show-page.js.

Apparently there were a bunch of revisions in show-page.js that also needed to be made for each of the kinds of items to edit (via the pencil icon). I've since tested an edit of each kind of item (as listed in the "add content" drop down), and my code revisions now committed to this branch seem to handle the behavior of each kind of edit correctly. Sorry for the overlooking that.

Earle and Sam, thanks for tracking and reviewing this PR.


Documentation / user guide

In my opinion, as someone who knows very little about the subject of memory-mapped files, quite a bit more documentation would be useful. This mostly isn't specific to this crate, but having the documentation in one place (ideally within the module documentation) would make the topic easier to learn.

[ ] What are the main use-cases vs non-memory mapped files — performance, memory usage and behaviour differences with read-only and read-write usage. (E.g. is it useful when reading a file sequentially or only when seeking?)
[ ] What are the main costs of mem-mapped files: presumably opening, reading a page, and flushing changes?
[ ] Are there any guarantees when a memory-mapped file is read and modified by another process — e.g. if the writes are only appends, are reads safe? Is it OS-specific?
[ ] Can mem-mapped files be locked by the OS? This may be a separate topic, but pointers welcome.
[ ] How does paging work: entirely automatically in response to pointer dereferences? What's the page size (always 4kB?) & how should applications best allocate file memory to take advantage?

I have somewhat mixed feelings about this.  More documentation is always good, but it's a fine line between documenting the crate and re-writing system man pages.
For what it's worth, my opinion is that there are very few use cases which justify using file-backed memory maps. The trade-offs of mmap vs the conventional file API are subtle and widely misunderstood.

I suppose optimal mmap use cases even change depending upon whether your storage is backed by an HDD or an SSD or one of those new Intel flash things.  And folks with unlimited development budget like Google tend towards log-structured merge-trees.
I'd suggest adding references to a couple good outside resources, maybe good blog post or two on the topic, or even the mmap topic on stackoverflow.

It'd be nice if the docs could describe why some functions have been marked unsafe.
Thanks

Seconding the concerns about documenting unsafety. It would be good to document what the caller needs to ensure to keep the program memory safe.

+1 for better explanation of unsafe.
If I understand correctly creation of memory mapped buffer is unsafe primary due the ability to create shared mutable memory. But what about using only immutable Mmaps only (e.g. for reading files), is it safe? If so, shouldn't creation of Mmap::map be safe and in turn Mmap::make_mut become unsafe?

I think MAP_ANONYMOUS behave like allocations, so safe even for writing.  It's clear MAP_PRIVATE protects readers from your writes, but it's less clear if others could still modify your pages before you read them yourself.  And MAP_SHARED would probably never be safe even if read only for the current process.


Button focus hovering

Signed-off-by: Anthony Fieroni<EMAIL_ADDRESS>

Could you squash the two commits together? In the PR workflow we prefer merging commits that work by themselves, the fixups done by the contributors before merging should be squashed unless particularly relevant for the git history.

Looks like something fishy happened during rebase, you now have 4 commits instead of 1 :)
A git rebase might help.

git rebase -i HEAD~2
pick (main)
squash (correction)
git pull
git push
https://github.com/bvbfan/godot/commit/d55127396c970448e685c417a615169582ae4a66
2 parents f3bea0d + 4c0fb9f commit d55127396c970448e685c417a615169582ae4a66
How can be done without merging?

You should have used instead of:
git pull
git push

the history-rewriting variant:
git pull --rebase
git push --force

This is of course not to do in a main public branch, but for a PR-intended branch it's a fine workflow.

Yes, i mean for the branch. So it's can be correct?

Fixed.


Payment Changes

Pull request has been closed.

Thank you for this PR! Sorry it's taken a little while, somehow it slipped through my inbox. I'm taking a look at all the changes now :)

@pman-emp thank you again for the PR! I went through and left some comments — I really like a bunch of the changes, but I'm not sure about all of them. Would you mind taking 5 minutes to respond to my questions so we can get this merged in?
Thanks!

What happened with this? I would really like to merge these changes (and the ones at qj#1). Sorry if I was a little slow in responding, it's not because I didn't think they were important — just a lot on my plate at work right now!


Update inventory.md

I believe "Subscription Monitoring" is better associated with Azure Activity Log, especially that Azure Service Health is the first record in the table

@frachkid : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Regarding the 2D input

Hello,
Sorry to bother you again, may I know which joint is not needed for your 2D input? Is it head, or nose?
I understand that your input and output are both 16 joints, and nose is not predicted by the model.
Many thanks,
Shiyang

Hi, Shiyang,
Welcome~
Both 2D pose and 3D pose follow the same joint setting so that the virtual camera projection (3D pose 16x3 -> 2D pose 16x2) can be used as augmentation data directly.

Hey Kehong,
So the nose is excluded in both setting then? Thanks so much!
Cheers,
Shiyang

Hi Shiyang,
Yes. :)


Add ability to choose which MSBuild architecture to use

After #84 was fixed, our automated builds started failing. We're building Visual Studio extensions, which use the VSSDK NuGet package. As part of its build process, a 32-bit process (VSCT.exe) is invoked, which causes an error to occur. Ideally, we'd like to be able to force a 32-bit MSBuild process even if we're running on a 64-bit machine.
Would it be possible to add the ability to do something like this?
use 15.0:x86 MSBuild

The idea being it could be applied to other paths like VisualStudio\<version>:
use VisualStudio\14.0:x86 MSBuild

Would it be possible to add the ability to do something like this?

For MSBuild, yes, let me investigate and add this feature. The convention 15.0:x86 looks fine, I am just not sure about the colon in it, e.g. psake does not use it. Perhaps we should adopt this existing practice and use 15.0x86.

Sure, that works for me! The colon was inspired by the way you specify the architecture when installing packages using apt-get, but I'm not super attached to that suggestion.

For now, I am going to support only the suffix x86 which means "ensure 32-bit MSBuild".
In this way, it is going to be consistent across all versions and cover your problem case.
Problem cases with required but not yet supported suffix x64 are not yet known.

That makes sense.
Let me know if there's anything I can do to help -- I'm happy to have a stab at a pull request if you're not working on it yet.

Thank you. It's all done and being tested. So far so good. I will release this tonight, more likely.

v3.6.4
I knew it was going to happen but was waiting for a problem case. Thank you for your report.


docs: add release procedure

This is something which I had been doing for previous releases and documented here.

I am merging this after the docs build. If any issues, make a new PR ;)

I am merging this after the docs build. If any issues, make a new PR ;)


Update Module+PkgConfig.swift

Hi, thanks for the PR! Can you add some description to the PR and a unit test? I am closing the PR for now but feel free to rebase and reopen!


Radarr: fixed discover poster background color

This is a fix for issue #220.
Before:

After:

Thanks!


Added hybridaks whl file in index.json for public preview

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[x] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
The precondition is to put your code inside this repository and upgrade the version in the pull request but do not modify src/index.json.

hybridaks

hybridaks

@yonzhan I have addressed the pipeline failures in this PR and it looks green now. Can you please take another look? Thanks!