apkNotificationMessageKeyUpgradeVersionConflict: APK specifies a version code that has already been used.

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description

as far as i understand versionCode is not updated in
gradle(       task: 'bundle',       build_type: 'Release',       properties: {         "versionCode" => track_version_codes[0] + 1       }     )
print track_version_codes[0] + 1 - displays correct version
Command executed

fastlane playstore
Environment

✅ fastlane environment ✅
Stack

Key
Value

OS
10.14.6

Ruby
2.4.2

Bundler?
true

Git
git version 2.21.1 (Apple Git-122.3)

Installation Source
~/.rvm/gems/ruby-2.4.2/bin/fastlane

Host
Mac OS X 10.14.6 (18G3020)

Ruby Lib Dir
~/.rvm/rubies/ruby-2.4.2/lib

OpenSSL Version
OpenSSL 1.1.1d  10 Sep 2019

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
11.3.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
#     https://docs.fastlane.tools/plugins/available-plugins
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane

default_platform(:android)

platform :android do
  desc "Runs all the tests"
  lane :test do
    gradle(task: "test")
  end

  desc "Submit a new Beta Build to Crashlytics Beta"
  lane :beta do
    gradle(task: "clean assembleRelease")
    crashlytics

    # sh "your_script.sh"
    # You can also use other beta testing services here
  end

  desc "Deploy a new version to the Google Play"
  lane :deploy do
    gradle(task: "clean assembleRelease")
    upload_to_play_store
  end
  lane :playstore do |options|
    track_version_codes = google_play_track_version_codes(track: 'internal')

    gradle(
      task: "clean"
    )

    gradle(
      task: 'bundle',
      build_type: 'Release',
      properties: {
        "versionCode" => track_version_codes[0] + 1
      }
    )

    upload_to_play_store(
      track: 'internal',
      skip_upload_apk: true,
      skip_upload_images: true,
      skip_upload_screenshots: true,
      aab: "/Users/bon/work/ff/android/app/build/outputs/bundle/release/app.aab",
      version_code: track_version_codes[0] + 1
    )
  end
end

`./fastlane/Appfile`
json_key_file("./deploy-key.json") # Path to the json secret file - Follow https://docs.fastlane.tools/actions/supply/#setup to get one
package_name("io.fanfinder.app") # e.g. com.krausefx.app

fastlane gems

Gem
Version
Update-Status

fastlane
2.145.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.1.0

executable-hooks
1.6.0

bundler-unload
1.0.2

rubygems-bundler
1.4.5

bundler
1.17.3

CFPropertyList
3.0.2

public_suffix
2.0.5

addressable
2.7.0

atomos
0.1.3

aws-eventstream
1.1.0

aws-partitions
1.297.0

aws-sigv4
1.1.1

jmespath
1.4.0

aws-sdk-core
3.94.0

aws-sdk-kms
1.30.0

aws-sdk-s3
1.61.2

babosa
1.0.3

claide
1.0.3

colored
1.2

colored2
3.1.2

highline
1.7.10

commander-fastlane
4.4.6

declarative
0.0.10

declarative-option
0.1.0

digest-crc
0.5.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

dotenv
2.7.5

emoji_regex
1.0.1

excon
0.73.0

multipart-post
2.0.0

faraday
0.17.3

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

faraday_middleware
0.13.1

fastimage
2.1.7

gh_inspector
1.1.3

jwt
2.1.0

memoist
0.16.2

multi_json
1.14.1

os
1.1.0

signet
0.14.0

googleauth
0.12.0

httpclient
2.8.3

mini_mime
1.0.2

uber
0.1.0

representable
3.0.4

retriable
3.1.2

google-api-client
0.36.4

google-cloud-env
1.3.1

google-cloud-errors
1.0.0

google-cloud-core
1.5.0

google-cloud-storage
1.26.0

json
2.3.0

mini_magick
4.10.1

multi_xml
0.6.0

plist
3.5.0

rubyzip
1.3.0

security
0.1.3

naturally
2.2.0

simctl
1.6.8

slack-notifier
2.3.2

terminal-notifier
2.0.0

unicode-display_width
1.7.0

terminal-table
1.8.0

tty-screen
0.7.1

tty-cursor
0.7.1

tty-spinner
0.9.3

word_wrap
1.0.0

nanaimo
0.2.6

xcodeproj
1.16.0

rouge
2.0.7

xcpretty
0.3.0

xcpretty-travis-formatter
1.0.0

generated on: 2020-04-17

The docs will give you the impression that this is how you set an Android application's version code. It is not. You must still set up the build.gradle scripts to use it correctly.

@doctorpangloss i've spent more than hour trying to configure this, lol

If you are trying for a flutter app you can give
 gradle(
      task: "clean bundle",
      build_type: "Release",
      properties: {
        "flutter.versionCode" => 500,
        "flutter.versionName" => "2.0.0",
      }
    )


🐛 BUG: ProxyWorker request logs

Which Cloudflare product(s) does this pertain to?
Workers Runtime
What version(s) of the tool(s) are you using?
3.13.0
What version of Node are you using?
18.18.0
What operating system are you using?
Windows 10
Describe the Bug
With wrangler 3.13.0, I'm now seeing the following in my logs regularly when developing:
[wrangler:inf] GET /cdn-cgi/ProxyWorker/pause 204 No Content (0ms)
[wrangler:inf] GET /cdn-cgi/ProxyWorker/pause 204 No Content (12ms)
[wrangler:inf] GET /cdn-cgi/ProxyWorker/pause 204 No Content (1ms)
[wrangler:inf] GET /cdn-cgi/ProxyWorker/play 204 No Content (1ms)

Is this intended? Should these be debug logs instead? These logs do not appear in 3.12.0 or prior.
Please provide a link to a minimal reproduction
No response
Please provide any relevant error logs
No response

@Cherry we've identified some issues with the latest version of Wrangler (3.13.0) and are working on fixes. In the meantime, we recommend staying on Wrangler 3.12.0 (npm install wrangler@latest should point to 3.12.0).

we have published a new version of Wrangler (3.13.1) that reverts the change that was causing issues. You should be able to update and not see these logs.

This has been fixed in #4175. Since this bug is only present in that branch and not main, I will close this issue now. Thanks for reporting!


TRUST4 fails with uninformative error after assembly.

I think for the --ref option should be "--ref ./mourse/mouse_IMGT+C".


make the footer inlined

Fix #625
Display the footer inlined with automatic vertical pipes.

Hmm - my thinking is that this might be a little bit too opinionated for others. The intuitive default (to me anyway) is that the footer is block-level content rather than inline. Maybe this could be a short piece of sample documentation instead of hardcoding CSS in the theme?

Hmm - my thinking is that this might be a little bit too opinionated for others. The intuitive default (to me anyway) is that the footer is block-level content rather than inline. Maybe this could be a short piece of sample documentation instead of hardcoding CSS in the theme?

sure I just wrote the PR not to forget it. Let me see if I can set it somewhere as an example

Hmm - my thinking is that this might be a little bit too opinionated for others. The intuitive default (to me anyway) is that the footer is block-level content rather than inline.

Well... I actually see an improvement in what this PR proposes... :wink:
Probably a totally subjective view as well...

ahah then should we invite new reviewers to the party?

as it's easier to start from a block-level and add css pipes and inline rules than the other way around

That's what I was thinking as well. Though if we can find some other themes that use behavior like this, something we can use as a guideline or principle to point to, then I'd be happy to discuss making it the default. Either way, documenting it is a nice start 🙂

I think it's better to keep it that way and describe exactly how the trick can be performed as it's easier to start from a block-level and add css pipes and inline rules than the other way around.

Either way, documenting it is a nice start 🙂

I agree, let's go with docs as a first step!
@12rambau do you plan to use this very same branch/PR to work on the docs or should I close this one?

I'll create another one for convenience


User editor broken on v1.1.0

The individual user entries on the user editor page can't be opened for some reason. Clicking one of the entries throws TypeError: can't convert config to string in the developer console.

This seems to be due to a breaking change in jQuery. See https://github.com/twbs/bootstrap/issues/30553 and https://github.com/jquery/jquery/issues/4665. This shouldn't affect the official Docker builds on Docker Hub and the jQuery devs are apparently going to fix this for jQuer y 3.5.1 so let's just wait for that. I should probably think about locking the dependency versions in package.json to specific versions instead of using the "compatible with" semver numbers.


[Request]: dependency problem with newer http package versions

Plugin
package_info_plus
Use case
dependency problem with newer http package versions
Proposal
please support newer http package versions

please support newer http package versions

Could provide an explanation on what do you mean? package_info_plus supports a wide range of http package versions already.

Closing due to no activity


Release with updated lxml dep

Hi,
I'm working on adding Python 3.13 support to an application that depends on Twill, it would be nice if you could make a release that include https://github.com/twill-tools/twill/commit/43fb4597b92387944e95a10c87c324818bfe0b1c .
Thanks!

Released as version 3.2.5 now.
Unfortunately, I cannot guarantee full Python 3.13 compatibility yet since it is still in beta (so things might break) and the tests need Quixote which does not support it. But I plan to replace Quixote and create a version that officially supports Python 3.13 as soon as it's released.

Thanks for the quick response! I'll let you know if we find any issue.


你好，我有一些结构的问题

KeyError: "RetinaNet: 'poolformer_s12 is not in the models registry'"

Hello, may I ask if you have solved this problem later. I'm getting the same error when I run it.
Thank you!

Hello, I have resolved this issue. One of the modules is a private library that needs to be downloaded from its git. It cannot be downloaded directly from the global library, so there will be no errors

Thanks for your reply!


gha: simplify env matrix

This simplifies the matrix logic a little bit.

@dtrifiro does this work because there's only one version of python installed for each matrix entry?

I updated the actions so that proto3 and core tests also run as part of the 3.8 job. I'd have preferred to have them run as a separate matrix entry, but I guess this will do for now.

Fair enough. I'll try and offload proto3 and core so separate matrix entries.

Sorry, no time to get back to this.


Performance improvements for HTTP proxy.

Description
This PR includes several performance improvements for the HTTP proxy.

Introduce a token cache that does not require generating new tokens for every request. A token can be created in a fixed time interval. Hardwired to 10s for the time being.

Introduce a sync pool for buffers so that the proxy does not constantly allocate and free memory from the operating system. This significantly improves both latency as well as the overhead of garbage collection.

Adapt the transport parameters to allow a larger number of connections to be shared in the underlying transport.

Properly configure http/2 between the proxies.

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "stats",
    "component": "trireme-lib",
    "pr-id": "593",
    "commit-sha": "675079ee393874a397f1a4913002e2179faebdcd"
  },
  {
    "project": "stats",
    "component": "enforcerd",
    "pr-id": "710",
    "commit-sha": "bb40edde26823c8a576940f330509a6defffd590"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "stats",
    "component": "trireme-lib",
    "pr-id": "593",
    "commit-sha": "675079ee393874a397f1a4913002e2179faebdcd"
  },
  {
    "project": "stats",
    "component": "enforcerd",
    "pr-id": "710",
    "commit-sha": "0a392382ea308318836c45529bd3b11f93a7b087"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "stats",
    "component": "trireme-lib",
    "pr-id": "593",
    "commit-sha": "4472dd6fc0ac545827b511fb92fcbdf530bf41a9"
  },
  {
    "project": "stats",
    "component": "enforcerd",
    "pr-id": "710",
    "commit-sha": "0a392382ea308318836c45529bd3b11f93a7b087"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "stats",
    "component": "trireme-lib",
    "pr-id": "593",
    "commit-sha": "e92457cfb7ee8b8729a2eb94d937e6b55967646f"
  },
  {
    "project": "stats",
    "component": "enforcerd",
    "pr-id": "710",
    "commit-sha": "0a392382ea308318836c45529bd3b11f93a7b087"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "stats",
    "component": "trireme-lib",
    "pr-id": "593",
    "commit-sha": "097b8b99fc6c1533671105c1714fadce49338ac0"
  },
  {
    "project": "stats",
    "component": "enforcerd",
    "pr-id": "710",
    "commit-sha": "0a392382ea308318836c45529bd3b11f93a7b087"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "stats",
    "component": "trireme-lib",
    "pr-id": "593",
    "commit-sha": "dd83879fda5174d96b11cfc63d64a3871685d353"
  },
  {
    "project": "stats",
    "component": "enforcerd",
    "pr-id": "710",
    "commit-sha": "0a392382ea308318836c45529bd3b11f93a7b087"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "stats",
    "component": "trireme-lib",
    "pr-id": "593",
    "commit-sha": "492d0be6cf01a7beb59c0c4662dcafe40d30b2d6"
  },
  {
    "project": "stats",
    "component": "enforcerd",
    "pr-id": "710",
    "commit-sha": "0a392382ea308318836c45529bd3b11f93a7b087"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "stats",
    "component": "trireme-lib",
    "pr-id": "593",
    "commit-sha": "f95b5eb6ec9e50dfd6308ccfd97a957d87a53f01"
  },
  {
    "project": "stats",
    "component": "enforcerd",
    "pr-id": "710",
    "commit-sha": "0a392382ea308318836c45529bd3b11f93a7b087"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "stats",
    "component": "trireme-lib",
    "pr-id": "593",
    "commit-sha": "ca17122ba3bba74e4fd5e09a39c0102ea87ee488"
  },
  {
    "project": "stats",
    "component": "enforcerd",
    "pr-id": "710",
    "commit-sha": "0a392382ea308318836c45529bd3b11f93a7b087"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "stats",
    "component": "trireme-lib",
    "pr-id": "593",
    "commit-sha": "ca17122ba3bba74e4fd5e09a39c0102ea87ee488"
  },
  {
    "project": "stats",
    "component": "enforcerd",
    "pr-id": "710",
    "commit-sha": "1864fdd57c31623392518c432ee3811c3fc6d2a1"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "stats",
    "component": "trireme-lib",
    "pr-id": "593",
    "commit-sha": "d252c32551c1ba77cab2032968e1cae4cc7e3ab1"
  },
  {
    "project": "stats",
    "component": "enforcerd",
    "pr-id": "710",
    "commit-sha": "1864fdd57c31623392518c432ee3811c3fc6d2a1"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "stats",
    "component": "trireme-lib",
    "pr-id": "593",
    "commit-sha": "d252c32551c1ba77cab2032968e1cae4cc7e3ab1"
  },
  {
    "project": "stats",
    "component": "enforcerd",
    "pr-id": "710",
    "commit-sha": "1864fdd57c31623392518c432ee3811c3fc6d2a1"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "stats",
    "component": "trireme-lib",
    "pr-id": "593",
    "commit-sha": "e07c9d99bff1ecf8efb812253c51790a47eec023"
  },
  {
    "project": "stats",
    "component": "enforcerd",
    "pr-id": "710",
    "commit-sha": "2a82ac4fe3a2f5e89553deab1794a24f2fc07462"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "stats",
    "component": "trireme-lib",
    "pr-id": "593",
    "commit-sha": "d9bac24d27593ff807ca29b0149733d3fbe0bd56"
  },
  {
    "project": "stats",
    "component": "enforcerd",
    "pr-id": "710",
    "commit-sha": "2a82ac4fe3a2f5e89553deab1794a24f2fc07462"
  }
]


Remaining time

Is it possible to add calculation of remaining time, so user can see how much time left based on approx download speed connection?

You can add this by using the DownloadProgressMonitor and DownloadSpeedMonitor and calculate it with both their values. Have a look at the modified example in Program.cs:
var remainingTime = (progressMonitor.GetTotalFilesizeInBytes(download) - progressMonitor.GetCurrentProgressInBytes(download)) / speedMonitor.GetCurrentBytesPerSecond();
Console.WriteLine("Remaining time: " + remainingTime + " sec.");

This answer was really helpful.
Thank you.

Please be aware that / speedMonitor.GetCurrentBytesPerSecond() in case when connecting estabilisging take some time (slow connections / firewall popoup which require use reaction) may come with 0 value what throw System.DivideByZeroException unhandled exception for this math operation.


Small changes based on feedback from Nazareth resolves #14 #15 #16

looks good @lucymonie. I think @skibinska covers jsonview in the giphy workshop. But I don't think it's a problem to mention it twice. The two workshops don't need to depend on each other. Should I merge or wait for nori and ewelina?

Please go ahead and merge @emilyb7. I got feedback from Nazareth that this would be helpful for this part of the workshop. I had completely forgotten than I had JSONView installed. I don't think it's a problem if it's mentioned twice as they can both be standalone workshops.


KAFKA-17330: New share-coordinator module. Added record schemas.

What

Introduced a new module share-coordinator to house relevant implementation code and resources.
Modified settings.gradle and build.gradle to accommodate the module.
Added ShareSnapshot[Key, Value], ShareUpdate[Key, Value] message record schemas.
Introduced a trivial impl of ShareCoordinatorShard class to establish dependencies with other modules (:group-coordinator, :metadata). The actual impl for this class will be done in future PRs.

Why

The share coordinator component has been introduced as part of KIP-932 (QFK). This component is will be responsible for managing persistence for various data related to share partitions into a dedicated internal topic.
To keep all this functionality contained, we want to create a separate module in line with group and transaction coordinators.

Testing

No impl code yet, clean build locally.

unrelated test failure
https://ci-builds.apache.org/job/Kafka/job/kafka-pr/job/PR-16877/1/testReport/


Expect: 100-continue

Is it supported in aiohttp.web server?
$> curl -v -include --form<EMAIL_ADDRESS>http://<IP_ADDRESS>:8080/uploader/123/
*   Trying <IP_ADDRESS>...
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 8080 (#0)
> POST /uploader/123/ HTTP/1.1
> User-Agent: curl/7.35.0
> Host: <IP_ADDRESS>:8080
> Accept: */*
> Content-Length: 408460805
> Expect: 100-continue
> Content-Type: multipart/form-data; boundary=------------------------9fa6693db84f46b3
>
* Done waiting for 100-continue
< HTTP/1.1 200 OK

Nginx + Django response looks like this:
> POST /accounts/login/ HTTP/1.1
> User-Agent: curl/7.35.0
> Host: ***
> Accept: */*
> Expect: 100-continue
> Content-Type: application/x-www-form-urlencoded
> Content-Length: 96
>
< HTTP/1.1 100 Continue
< HTTP/1.1 403 FORBIDDEN

Nginx responses with HTTP/1.1 100 Continue first.

I don't understand your question clean, sorry.
aiohttp.web has no embedded support for 100 but you can make response with 100 Continue status code by hands if needed.

No, if I make a response:
return Response(status=100)

aiohttp just closes connection. Curl output:
* Done waiting for 100-continue
< HTTP/1.1 100 Continue
HTTP/1.1 100 Continue
< CONTENT-LENGTH: 0
CONTENT-LENGTH: 0
< CONNECTION: keep-alive
CONNECTION: keep-alive
< DATE: Fri, 30 Jan 2015 16:12:43 GMT
DATE: Fri, 30 Jan 2015 16:12:43 GMT
* Server Python/3.4 aiohttp/0.14.4 is not blacklisted
< SERVER: Python/3.4 aiohttp/0.14.4
SERVER: Python/3.4 aiohttp/0.14.4

* Recv failure: Connection reset by peer
* Closing connection 0
curl: (56) Recv failure: Connection reset by peer

Working code is:
 request.transport.write(b"HTTP/1.1 100 Continue\r\n")

It is possible to handle authomatically in Request?

@tumb1er what is your use case for 100-continue ?

If it's like SIP protocol, it's to notify the client that the request is received, response will arrive.

@fafhrd91 it's only an observation of how curl works with post requests.
From here:

Upon receiving a request which includes an Expect request-header
field with the "100-continue" expectation, an origin server MUST
either respond with 100 (Continue) status and continue to read
from the input stream, or respond with a final status code. The
origin server MUST NOT wait for the request body before sending
the 100 (Continue) response. If it responds with a final status
code, it MAY close the transport connection or it MAY continue
to read and discard the rest of the request.  It MUST NOT
perform the requested method if it returns a final status code.

that is wrong reason for feature. by implementing this response you close ways to use this feature properly. i prefer no to have it rather have wrong implementation.

So every aiohttp user MUST now implement Expect: header processing by himself, to make aiohttp library HTTP/1.1 compatible?
I think, with Request.post() method behavior mentioned by RFC is clear enougth.
def handle(request):
  # First, check all request properties without reading a payload
  if check_headers_and_path(request) != "ok":
    # if not OK, send 417, or 403 or whatever else... (server MUST continue reading
    # or response with final status code)
    return Response(status=417)
  # if ok, request.post() sends 100-continue if necessary
  # (without any other movements from aiohttp users)
  # and continue reading payload (that is what server
  # MUST do if 100-continue is sent)
  yield from request.post()
  # do "perform request method" as in RFC
  result = do_usefull_stuff(request)
  return Response(text=result, status=200)

you can create middleware that for that.

well, you example already has different use case. so make pull request for your use case.


Specialize UI pipeline on "hdr-ness"

Objective
The UI pass in HDR breaks currently because the color attachment format does not match the HDR ViewTarget.
Solution
Specialize the UI pipeline on "hdr-ness" and select the appropriate format (like we do in the other built in pipelines).

bors r+


TrackingEventProcessor and Thread creation

The TrackingEventProcessor currently relies on a ThreadPoolExecutor (Commit 3f1a73d7c2 changed this from ExecutorService) and I'd like to propose changing it back to ExecutorService in a fashion that allows injecting a different implementation of ExecutorService.
This would improve the usability of the TrackingEventProcessor in different situations where it's up to the circumstances which implementation detail to use, e.g. when test code tries to verify the number of active threads (as is happening) a ThreadPoolExecutor could be used just for tests or in a Java-EE Environment where usually a ManagedExecutorService is required to spin-off threads.
Could you advise if this sounds reasonable. I'd take care creating a pull request if this has a chance.

I pushed a draft about this; see 1aa8bf63.
An ExecutorService could be registered with the configuration with a reasonable default. Further thoughts?

It's a fair point that a configurable ExecutorService implementation is better than a hard-coded ThreadPoolExecutor. In fact, I was already planning to replace the ThreadPoolExecutor, but then with either a CachedThreadPool or a ThreadFactory.
In fact, I am not sure if the ExecutorService is the right abstraction here. The TrackingProcessor will be configurable with a maximum amount of concurrent threads that could be running simultaneously. It will start attempt to claim tokens until all tokens are claimed or until the number of threads has been reached.
The ExecutorService is an abstraction that focuses on (relatively) short lived tasks that need to be executed. Not that it wouldn't work, but I'd prefer to have a configurable ThreadFactory instead.

This issue relates to #221. Please continue discussion under that issue.


[CI] Image for stable-v0.5.10 failed to release based on MeshKit error function use

See failure details - https://github.com/meshery/meshery-istio/actions/runs/968488719
Screenshots

Fixed by @dhruv0000


Add support for html.twig as HTML language

Vim uses html.twig for Twig files by default. I'm not sure if this should replace twig or not, so I left the previous line in.
This would fix #9

Sorry, submitted this too quickly. It did not fix the problem.

The tailwindcss LSP have filter which filetype return autocomplete items, only change the client not help and it's not open source https://github.com/bradlc/vscode-tailwindcss/issues/65. Maybe it's worth to create a new one.

If you want an ugly hacky way to add support you can add html.twig to line 6091 here:


1.56.1 missing from https://pecl.php.net/package/gRPC

What version of gRPC and what language are you using?
What operating system (Linux, Windows,...) and version?
What runtime / compiler are you using (e.g. python version or version of gcc)
What did you do?
Please provide either 1) A unit test for reproducing the bug or 2) Specific steps for us to follow to reproduce the bug. If there’s not enough information to debug the problem, gRPC team may close the issue at their discretion. You’re welcome to re-open the issue once you have a reproduction.
What did you expect to see?
What did you see instead?
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
See TROUBLESHOOTING.md for how to diagnose problems better.
Anything else we should know about your project / environment?

1.56.2 is also missing!

1.57.0 and 1.58.0 are present.


IsCyclical="false" is causing the content to be blank/not show up

Could you please provide a sample?

seems to only be blank with iscyclical = false when I bind something to the selectedItem. But isn't blank on iscyclical = true with a binding to a selectedItem. I have the card view in the aboutpage.xaml.
https://github.com/brettnguyen/TestPanView

Could just be the way I am binding but I was confused when it worked for true but not false. Thank you for any help or feedback.

Hi, could you please try to use selectedIndex instead of selectedItem? Maybe it will solve the problem

Will try when I’m home

Hi, could you please try to use selectedIndex instead of selectedItem? Maybe it will solve the problem

this change worked thank you for the help


Copy correct Ztunnel build

Please provide a description of this PR:
bin/build_ztunnel.sh was copying the debug binary regardless of BUILD_ZTUNNEL_PROFILE.
I've tested this with make build and make docker. Not sure how else I can test this.

@ericvn I see what you mean. It seems like the directory gets created somewhere in the Makefile. Regardless. It doesn't hurt to have it there. I'll updated so it doesn't have the trailing debug.


fix for #2586 (Relationship Type not updating on reciprocal) & new unit test

Critical Changes
Changes
Issues Closed
#2586

Thank you so much @tet3!!

@tet3 Very much appreciate the contribution - thank you!

@smarovich @davidhabib Let's be sure we call out in the release notes (edit Changes?) to thank Thomas for his speedy fix for this issue. Thanks again @tet3!


Get variable references working properly with Webstorm

Hi there,
I've installed the Semantic UI package via NPM, with a view to building our own stylesheets.
On initial install, and after setting the /src folder as a resource root, it seems that lots of the variables still can not be fully referenced by PHPStorm:

Is there a known setup / configuration for this?
I have posted the same issue on Jetbrains' forum, here:

https://intellij-support.jetbrains.com/hc/en-us/community/posts/115000631310-Working-with-Semantic-UI-full-build-LESS-variables

Thanks,
Dave

I believe the IDE suggestions on your link are correct. We use non-standard extensions for some less files .variables .overrides and .config.

Hey Jack,
Thanks for the reply.
It's a shame they're not saved as
.less.variables
.less.overrides
.less.config

then it would be really easy to override in PHPStorm.
I can probably hack the build files, as we'll be sticking with one build, but would be nice to have in core.

Hi @davestewart, did Elena’s suggestion to register these files as LESS work?

Hi @Banandrew - not yet had the time to look back into it!

@jlukic - I'm going to start looking into this over the weekend.
Is there a reason for the non-standard extensions?
Would there ever be the chance to submit a PR to change them to something IDEs could better-recognise?

OK, after some initial investigation, it looks like PHPStorm doesn't support 2-levels of file extension, therefore .less.variables is still associated as a .variables file.
Therefore, the files would need to be something like:

.variables.less
-variables.less

The gulp tasks are mainly built using wildcards, so this wouldn't be too difficult to change:
  gulp
    .watch([
      source.config,
      source.definitions   + '/**/*.less',
      source.site          + '/**/*.{overrides,variables}',
      source.themes        + '/**/*.{overrides,variables}'
    ], function(file) {
...

However, having less files as less really does make a difference!

I'm going to look at updating the scripts and files now...

OK, so I finally got this working, but it meant completely modifying the installed files.
For the CSS, I had to:

rename all .overrides and .variables files in site/ and themes/ with a .less extension
rename theme.config to theme.config.less
update all imports in all "less"-like files in src/

For the gulp tasks, I had to:

update any references to .overrides or .variables to include the new .less extension
replace the gulp-util replaceExtension util with my own that supported multi-part extensions

Once all this was done, I was able to build files from scratch.
I'm not sure why this isn't the default setup with Semantic, as it's so much easier to edit files now they work properly in the IDE.

Hi,
I want to include Semantic-UI also in my PHPStorm Project.
@davestewart could you explain more how you did this?
And does the Semantic-UI Team provides a solution for this?
Greetings David

@Dave811 just using freely-available filename find and replace tools and then PHPSTorm's find and replace (probably using regexps).
I did all this in a branch, and made sure I committed at each successful step so I could roll back if I screwed anything up!
Not much more info than that, apart from just go for it :)

@davestewart it's not a recommended way, but instead of renaming all of your files, you can just add the *.overrides and *.variables to the file type in (my case WebStorm) PHPStorm.
File -> Settings... -> Editor -> File Types
Select "Less Style Sheet" in the "Recognized File Types" field
Then use the "+" in the "Registered Patterns" field to add ".overrides" and ".variables"


CI is broken

CI is broken after my last pull request.
https://travis-ci.org/github/bitwalker/timex
Sorry to bring it to the room.
I'm trying to address the reason and will update the progress here.
Current state:
At this point, I noticed that all builds running on MacOS failed. However, it is strange that they used to work, oddly with OTP for ubuntu installed.

update:
I think I have found the reason. It seems Travis does not support erlang prebuilt on osx.
But why was the CI working before?
It was macos in the Travis CI config, instead of osx. So it was mistakenly interpreted as ubuntu
I'll open a PR on this issue.

CI is fixed now that we've migrated to Cirrus


AllergyIntolerance does not have 'event' property

Looks like it has been changed to 'reaction'

Fixed on upgrade to DSTU2


extract GitCheckout type to a testing module

extract GitCheckout type to a testing module
Summary:
This will be used to set up the sapling tests.
Test Plan: Rely on CI.
Reviewers: suo
Subscribers:
Tasks:
Tags:
ghstack-source-id: a75ae0a9e9f27def8ceb1fafe79606a6481b5a9b
Pull Request resolved: https://github.com/suo/lintrunner/pull/51

Stack created with Sapling. Best reviewed with ReviewStack.

#39
-> #45
#44
#43
#42

Already merged with https://github.com/suo/lintrunner/pull/39


Fix incorrect docs about ol.source.Raster

As requested in #5121.

The job never started on travis. Merging anyway


validate ttl is a positive number in ShortenerDto class

the ttl field in ShortenerDto class is considered valid if it's value is a number, including a negative number, which is an invalid state.
this pr restricts ttl to only positive numbers.

That's a nice catch!
Thank you @tcdsv 💯


Appstudio update test-component-pac-oody

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-oody-on-pull-request has successfully validated your commit.


WIP Refactor VivViewer

This is....a big one.  I'm requesting comment because I don't know exactly how this will fit in with Vitessce.  I've tried side-by-side viewing in the Viv demo and it works very well.  At a high level this PR:

Makes VivViewer accept a list of views (subclasses of VivView), viewStates, and layerProps (props for the layers returned by instances of VivView) so we can have different configurations (side-by-side with same or different picture, picture-in-picture etc.).
Adds documentation from documentationjs like http://chgw.gehlenborglab.org/docs/

A few things I think you all can comment on:

What should the prop given to VivViewer for viewStates be called?  It has always been prefixed by initial but it also communicates height/width, which can update (and needs to).
Does this API make sense?  Should layerProps/viewState exist entirely within the views?

Once this is agreed upon at a high level (i.e the "Draft" part of the PR is done) I will:

Implement helper components like PictureInPictureViewer, SingleImageViewer, and SideBySideViewer inheriting from VivViewer that simply take in props (i.e without instantiating some subclass of VivView) and manage the classes/state/layers for you.
Write comprehensive tests based on the agreed upon API

Does this sound good?  I think @manzt is the primary stakeholder here, but feel free to comment at however high a level you want @mccalluc.
Fixes #107 and fixes #111.

Ok @mccalluc, let me see what @manzt has to say, and let me incorporate that with what you're saying, and then I'll push to s3 and re-request your view.

@mccalluc  and @manzt Would y'all be willing to re-review and comment?  Demo is here: https://vitessce-data.s3.us-east-1.amazonaws.com/demos/viv/refactor_vivviewer/index.html and documentation is here: https://vitessce-data.s3.us-east-1.amazonaws.com/demos/viv/refactor_vivviewer/docs/index.html.  Thanks!

@manzt I found useEffect to be slower than my componentDidUpdate for resizing events.  I think the reason was that I am passing in height/width within the object in views and this nested structure doesn't play well.  I would be open to other suggestions - the code is here if you want to look at it side-by-side with the class component https://github.com/hubmapconsortium/vitessce-image-viewer/blob/56c809dab056168232db1c4c0ba0fd404b4cbb7d/src/viewers/VivViewer.js

@mccalluc I will add some documentation as to how this all fits together.  I can also change the name of the LinkedDetailViewer if @manzt agrees.  I couldn't come up with anything good, but SideBySideViewer is much more human readable, so I'd take it.
As for the code snippets, I think it's ok to keep them even if they are hard to maintain - I have seen other libraries do this in their docs (https://deck.gl/#/documentation/overview/upgrade-guide?section=tile3dlayer and http://guido.io/zarr.js/#/getting-started/nested-arrays?id=creating-nestedarrays are two examples I can think of) and I find it extremely helpful for getting started.  Even if they grow a bit out of date, the props (colormap, sliderValues etc.) API has remained largely unchanged even as components have been added and I think it is helpful for people to see everything declared all at once.  That being side I can clean it up a bit.

@mccalluc I addressed most of your comments in the recent push.  The only two things are 1) I do think people can use non side-by-side by using overview/detail (and all the options within those two are configurable).  Does that answer your concerns about that?  As for the generated docs, I don't think I can style the markdown inline code (if that is what you mean) but I do think that there are customizations available with his package.  It seems a little out of scope, but it is possible.  Maybe we file an issue?

@manzt I think I also addressed most of what you had to say.  The last thing that you both seem to have commented on is naming.  I proposed something here but would be open to other suggestions.


"use_underscores" useless?!?

I use tyro.extras._subcommand_app.SubcommandApp() and it seems that use_underscores passed to app.cli() doesn't change anything.

To clarify, is the missing behavior you're describing:

When use_underscores=False, for a function some_subcommand() to be converted to some-subcommand in the CLI?
When use_underscores=True, for a function some_subcommand() to be converted to some_subcommand in the CLI?

If so I agree there's some missing functionality!

When use_underscores=False, for a function some_subcommand() to be converted to some-subcommand in the CLI?

And this will be not done.


Fix ownership of select_enum instruction

This instruction was given forwarding ownership in the original OSSA implementation. That will obviously lead to memory leaks. Remove ownership from this instruction and verify that it is never used for non-trivial types.

@swift-ci test

Right, there are 2 places in SILGen where select_enum is generated. We could replace it with a utility function (which creates switch_enum). It would allow us to remove IRGenSILFunction::visitSelectEnumInst. The same for select_enum_addr.

Right, there are 2 places in SILGen where select_enum is generated. We could replace it with a utility function (which creates switch_enum). It would allow us to remove IRGenSILFunction::visitSelectEnumInst. The same for select_enum_addr.

I'm in favor of removing select_enum. I noticed it was in active use and didn't want to experiment further at the moment.


Update pman to<PHONE_NUMBER>bc

Note
This will be the latest PR regarding the runtime that requires refs/pman. The runtime will be moved to owncloud/ocis/ocis.
Pman's changelog:
source

pman now catches SIGHUP, preventing leaving zombie processes when losing control of a terminal
encountered the good old halting problem with the way ocis initializes extensions. A bandaid is a time.Sleep added to delay shutdown and wait for the last write. Logically, there is a case scenario when writers write (or, fail to write) after the shutdown reads and deletes entries, ending up in an empty db file and an orphan process.
fixes https://github.com/owncloud/ocis/issues/1173 by a global recovery handler.
adds support for setting RUNTIME_PORT on your environment. NOTE: When combined with oCIS it requires changes in the source, as currently the runtime port is hardcoded in oCIS to 10666
no more file management for tracking extension+PID tuples.

While the sync solution is only a bandaid and a more robust solution is due, we'll get this rolling first, track it and move along while is not an issue. It needs to be tested in slow machines.
This has been tested with the following diff on oCIS:
diff --git a/ocis/go.mod b/ocis/go.mod
index bda423ae..dfbf75c9 100644
--- a/ocis/go.mod
+++ b/ocis/go.mod
@@ -39,6 +39,7 @@ require (

 replace (
 	github.com/gomodule/redigo => github.com/gomodule/redigo v1.8.2
+	github.com/refs/pman => ../../../refs/pman
 	github.com/owncloud/ocis/accounts => ../accounts
 	github.com/owncloud/ocis/glauth => ../glauth
 	github.com/owncloud/ocis/konnectd => ../konnectd
diff --git a/ocis/go.sum b/ocis/go.sum
index a67c3209..0adb6770 100644
--- a/ocis/go.sum
+++ b/ocis/go.sum
@@ -1279,6 +1279,7 @@ github.com/stretchr/testify v1.4.0/go.mod h1:j7eGeouHqKxXV5pUuKE4zz7dFj8WfuZ+81P
 github.com/stretchr/testify v1.5.1/go.mod h1:5W2xD1RspED5o8YsWQXVCued0rvSQ+mT+I5cxcmMvtA=
 github.com/stretchr/testify v1.6.1 h1:hDPOHmpOpP40lSULcqw7IrRb/u7w6RpDC9399XyoNd0=
 github.com/stretchr/testify v1.6.1/go.mod h1:6Fq8oRcR53rry900zMqJjRRixrwX3KX962/h/Wwjteg=
+github.com/stretchr/testify v1.7.0/go.mod h1:6Fq8oRcR53rry900zMqJjRRixrwX3KX962/h/Wwjteg=
 github.com/studio-b12/gowebdav v0.0.0-20200303150724-9380631c29a1 h1:TPyHV/OgChqNcnYqCoCvIFjR9TU60gFXXBKnhOBzVEI=
 github.com/studio-b12/gowebdav v0.0.0-20200303150724-9380631c29a1/go.mod h1:gCcfDlA1Y7GqOaeEKw5l9dOGx1VLdc/HuQSlQAaZ30s=
 github.com/subosito/gotenv v1.1.1/go.mod h1:N0PQaV/YGNqwC0u51sEeR/aUtSLEXKX9iv69rRypqCw=
diff --git a/ocis/pkg/runtime/runtime.go b/ocis/pkg/runtime/runtime.go
index de5061a4..711f377d 100644
--- a/ocis/pkg/runtime/runtime.go
+++ b/ocis/pkg/runtime/runtime.go
@@ -80,10 +80,12 @@ func New(cfg *config.Config) Runtime {
 // Start rpc runtime
 func (r *Runtime) Start() error {
 	go r.Launch()
-	return service.Start()
+	return service.Start(
+		service.WithLogPretty(r.c.Log.Pretty),
+	)
 }

-// Launch ocis default ocis extensions.
+// Launch oCIS default extensions.
 func (r *Runtime) Launch() {
 	var client *rpc.Client
 	var err error

Gotchas

Note that if the runtime (a.k.a process thst runs ocis server is killed with SIGKILL children processes will be left orphan)
If spamming starting a server and interrupting the startup, sometimes a race condition-like scenario happens.

superceded by https://github.com/owncloud/ocis/pull/1483

superceded by https://github.com/owncloud/ocis/pull/1483


Improve the Linux/MacOS auto install scripts, once again

@nsde, merge (?)

@nsde, merge (?)

Okay, if everything's done, I'll merge :)

I can't actually merge, so I'm just gonna do this manually :)

I can't actually merge, so I'm just gonna do this manually :)

:concernedtater:

Why not? You should have pull request rights.

It's not about the permission. There was a merge conflict.

Well that can be solved here as well 😛


Added tray icon for application.

I added tray icon feature when window is minimalized. I used default windows form icon.

I think that this is currently totally unnecessary function.


How to link glew dir in CMakeLists.txt

This is a CMakeLists.txt file on my computer rewriting something.
`cmake_minimum_required(VERSION 3.13.0)
project(SPH)
set(GLEW_INCLUDE_DIRS C:/glew-2.1.0/include)
set(GLEW_LIBRARY_DIR C:/glew-2.1.0/lib)
find_package(OpenGL REQUIRED)
find_package(GLEW REQUIRED)
find_package(GLUT REQUIRED)
find_package(glm REQUIRED)
add_executable(sph "")
target_include_directories(sph PRIVATE ${GLM_INCLUDE_DIRS} ${GLEW_INCLUDE_DIRS} ${GLUT_INCLUDE_DIR})
target_link_libraries(sph PRIVATE GLUT::GLUT GLEW::GLEW OpenGL::GL)
add_subdirectory(src)
add_subdirectory(resources)`
When I built it, CMake build error was casued with this text.
CMake Error at C:/Program Files/CMake/share/cmake-3.27/Modules/FindPackageHandleStandardArgs.cmake:230 (message):   Could NOT find GLEW (missing: GLEW_INCLUDE_DIRS GLEW_LIBRARIES) Call Stack (most recent call first):   C:/Program Files/CMake/share/cmake-3.27/Modules/FindPackageHandleStandardArgs.cmake:600 (_FPHSA_FAILURE_MESSAGE)   C:/Program Files/CMake/share/cmake-3.27/Modules/FindGLEW.cmake:238 (find_package_handle_standard_args)   CMakeLists.txt:8 (find_package)
I don't know what the problem is.

Cheers for sending through the issue!
find_package(GLEW REQUIRED) is going to set the GLEW_INCLUDE_DIRS and GLEW_LIBRARY_DIR variables, so from my understanding, the lines where you specify those variables aren't going to have much of an effect.
When running cmake try setting up the CMAKE_PREFIX_PATH like so:
cmake -Bbuild -DCMAKE_PREFIX_PATH=C:/glew-2.1.0

This variable should help cmake find GLEW. You can also add to the path variable if you need to help cmake find GLUT and glm
For some more info: https://cmake.org/cmake/help/latest/variable/CMAKE_PREFIX_PATH.html


New: drone (drone.io)

Motivation for this change
Build drone.io package.
(only cli functionality tested, no server mode)
Also go-bindata-assetfs packaged, as build requirement
Things done

[x] Tested using sandboxing
(nix.useChroot on NixOS,
or option build-use-chroot in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

i think there is a typo:
error: attribute ‘asl2’ missing, at /home/travis/build/NixOS/nixpkgs/pkgs/development/tools/continuous-integration/drone/default.nix:36:15

@garbas fixed -- asl20 really ;)

@avnik looks like travis fails on darwin. does drone.io work on osx? we should at least disable it as a platform if we dont know how to fix it

@garbas It have cycled reference on osx. I haven't any idea why, and haven't any OSX to check. In theory cli should work everywhere to manipulate remote server.
If you haven't any ideas -- I set platform to linux.

@avnik you can use travis and this PR to trigger builds on darwin. it would be nice to have things also working on osx if it is not too hard to do.

@garbas But I haven't any ideas what to fix, I need to string ./result-bin/bin/drone at least, to see what happens. Is  a single-binary package actually.
But go framework create both  $out and $bin.
(we can discuss on irc I think)

FWIW I wonder if this (used on other go packages) would help:

https://github.com/NixOS/nixpkgs/issues/18131
https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/security/sudolikeaboss/default.nix

@avnik as @grahamc mentioned (thanks for pointing it out!), you could add something like that:
  postInstall = stdenv.lib.optionalString stdenv.isDarwin
    "install_name_tool -delete_rpath $out/lib -add_rpath $bin $bin/bin/drone";

and it would work. I have just tested it on my OS X 10.11.6 installation

yaay ... lets get this in nixpkgs!

On Sat, Oct 29, 2016 at 11:39:03AM -0700, Rok Garbas wrote:

yaay ... lets get this in nixpkgs!

Will take a look tomorrow (as well, as update drone to current snapshot)

I fixed darwin support (at least put suggested fixes in).
Also update everything to today' snapshot.
Let's look, what CI says.
if CI is ok, would be nice, if someone test it as well (I am not used drone atm activelly)

@avnik tnx!


Error in android-native

C:\Dev\Projetos\Kha\Invasion\build\android-native-build\Invasion\app\src\main\jni\SDKs\Kha\Kore\Backends\OpenGL2\Sources\Kore\RenderTargetImpl.cpp
Error:(78, 31) error: 'GL_DEPTH24_STENCIL8' was not declared in this scope
Error:(89, 31) error: 'GL_DEPTH32F_STENCIL8' was not declared in this scope
Error:(102, 45) error: 'GL_DEPTH_STENCIL_ATTACHMENT' was not declared in this scope

I probably broke it, will take a look.

Fixed in #40. And thanks, i didn't even know there is an android-native target until today :sweat_smile:


Fixing broken links back to the gh repo

(my $main_file = "lib/$module.pm" ) =~ s!::!/!g;
(my $distbase = $module) =~ s!::!-!g;
my $distlink = $distbase;

I noticed on metacpan that the links to the github repo were broken due to the module being AI::Ollama::Client and the repo AI-Ollama. I figured I could raise an issue, or just provide a fix. As I'm not sure if you want to correct this by renaming the repo to include -Client or keep things how they are now - if you want to stick with as-is. This simple fix should work. I hope I caught all the references.
I just added this line and updated github references from distlink/distbase to distrepo
(my $distrepo = $distbase) =~ s!-Client$!!g;

Thank you for reminding me of this! The error is with me, naming the repo before really naming the module!
I'll rename the repo to fit the (CPAN) reality :)


Update trigger_beta_build and daily Slack status jobs to handle jdk(head) version branching

Fixes https://github.com/adoptium/temurin-build/issues/3856

Correct EA trigger jenkins job to correctly find and build jdk(head) version tags
Correct daily Slack status to report correct jdk(head) version build status

@sxa i've upgraded super-linter to 6.6.0, as the current version 5.0.0 was "hanging" in the groovy-linter.
Seems fine with 6.6.0

Noting that there is probably some doc that needs updating based on all the changes from this new process.
yep, already updated: https://github.com/adoptium/temurin-build/wiki/Setting-up-new-build-jobs,-mirrors,...-when-a-new-openjdk-version-is-branched-from-jdk(head)


Use OSSL_STORE in apps, generalizing and simplifying load_key() etc.

This is the continuation of #11745, a further spin-off of PR #11470 according to https://github.com/openssl/openssl/pull/11470#discussion_r416669564.
This adds a flexible apps-internal function load_key_cert_crl() now used load_key(), load_pubkey(), and load_cert(), making use of OSSL_STORE.
This also adds the app-internal functions get_passwd(), cleanse(), and clear_free() to be used also in apps/cmp.c etc.
This PR also updates the help texts and the documentation of those apps using load-key() etc.

Using OSSL_STORE for loading private keys in DER format gives a couple of strange failures of
make test TESTS=test_ec
at least for the following ED25519 Private-Key:
-----BEGIN PRIVATE KEY-----
MC4CAQAwBQYDK2VwBCIEINTuctv5E1hK1bbY8fdp+K06/nwoy/HU++CXqI9EdVhC
-----END PRIVATE KEY-----
ED25519 Private-Key:
priv:
    d4:ee:72:db:f9:13:58:4a:d5:b6:d8:f1:f7:69:f8:
    ad:3a:fe:7c:28:cb:f1:d4:fb:e0:97:a8:8f:44:75:
    58:42
pub:
    19:bf:44:09:69:84:cd:fe:85:41:ba:c1:67:dc:3b:
    96:c8:50:86:aa:30:b6:b6:cb:0c:5c:38:ad:70:31:
    66:e1

The loader reports on apps/openssl pkey -in pkey-f.d -inform der -text ambigous results with a matchcount of 10 and the following console output:
Unable to load key
C0:B7:87:51:D2:7F:00:00:error:rsa routines:(unknown function):RSA lib:crypto/rsa/rsa_ameth.c:142:
C0:B7:87:51:D2:7F:00:00:error:asn1 encoding routines:(unknown function):wrong tag:crypto/asn1/tasn_dec.c:1135:
C0:B7:87:51:D2:7F:00:00:error:asn1 encoding routines:(unknown function):nested asn1 error:crypto/asn1/tasn_dec.c:698:
C0:B7:87:51:D2:7F:00:00:error:asn1 encoding routines:(unknown function):nested asn1 error:crypto/asn1/tasn_dec.c:630:Field=params.p, Type=DSA
C0:B7:87:51:D2:7F:00:00:error:dsa routines:(unknown function):interrupted or cancelled:crypto/dsa/dsa_ameth.c:416:
C0:B7:87:51:D2:7F:00:00:error:asn1 encoding routines:(unknown function):wrong tag:crypto/asn1/tasn_dec.c:1135:
C0:B7:87:51:D2:7F:00:00:error:asn1 encoding routines:(unknown function):nested asn1 error:crypto/asn1/tasn_dec.c:698:
C0:B7:87:51:D2:7F:00:00:error:asn1 encoding routines:(unknown function):nested asn1 error:crypto/asn1/tasn_dec.c:630:Field=privateKey, Type=EC_PRIVATEKEY
C0:B7:87:51:D2:7F:00:00:error:elliptic curve routines:(unknown function):EC lib:crypto/ec/ec_asn1.c:991:
C0:B7:87:51:D2:7F:00:00:error:elliptic curve routines:(unknown function):decode error:crypto/ec/ec_ameth.c:455:
C0:B7:87:51:D2:7F:00:00:error:asn1 encoding routines:(unknown function):ASN1 lib:crypto/asn1/d2i_pr.c:62:
C0:B7:87:51:D2:7F:00:00:error:asn1 encoding routines:(unknown function):ASN1 lib:crypto/asn1/d2i_pr.c:62:
C0:B7:87:51:D2:7F:00:00:error:asn1 encoding routines:(unknown function):ASN1 lib:crypto/asn1/d2i_pr.c:62:
C0:B7:87:51:D2:7F:00:00:error:asn1 encoding routines:(unknown function):ASN1 lib:crypto/asn1/d2i_pr.c:62:
C0:B7:87:51:D2:7F:00:00:error:STORE routines:(unknown function):ambiguous content type:crypto/store/loader_file.c:1386:

How can this be fixed?

  It turns out that d2i_PrivateKey (and thereby d2i_PrivateKey) doen't work as advertised for PKCS#8-wrapped keys!  The manual says this (italics mine, for emphasis):

d2i_PrivateKey() decodes a private key using algorithm type. It
attempts to use any key specific format or PKCS#8 unencrypted
PrivateKeyInfo format. The type parameter should be a public key
algorithm constant such as EVP_PKEY_RSA. An error occurs if the decoded
key does not match type.  d2i_PublicKey() does the same for public
keys.

However, looking at actual code, you'll notice that when it has decoded a PKCS#8 structure, *it doesn't care about type at all!
https://github.com/openssl/openssl/blob/90fc2c26df23811be080093772b2161850385863/crypto/asn1/d2i_pr.c#L46-L65
Of course, the file loader is implemented according to documentation :wink:

Try and see what happens if you add this patch:
diff --git a/crypto/asn1/d2i_pr.c b/crypto/asn1/d2i_pr.c
index c7346f5424..3ddc56d408 100644
--- a/crypto/asn1/d2i_pr.c
+++ b/crypto/asn1/d2i_pr.c
@@ -58,6 +58,8 @@ EVP_PKEY *d2i_PrivateKey_ex(int type, EVP_PKEY **a, const unsigned char **pp,
                 goto err;
             EVP_PKEY_free(ret);
             ret = tmp;
+            if (EVP_PKEY_type(type) != EVP_PKEY_base_id(ret))
+                goto err;
         } else {
             ASN1err(0, ERR_R_ASN1_LIB);
             goto err;

Try and see what happens if you add this patch:

Great, this fixes the test failures - thanks @levitte

@levitte, hope you can finish up #11756 providing OSSL_STORE_attach() soon
such that this PR can be finalized and merged also in #11470.

This PR meanwhile reflects also the extended load_key() and load_pubkey() features in the apps and their documentation.
@FdaSilvaYY, thanks for your yesterday's review. Maybe you wanna have a look also at this addendum.

@levitte, if you can approve this today we should be able to get this along with #11756 into alpha2.
It would also simplify #11470.

I've partly squashed the commits and
simplified the TODOs to be executed when rebasing on #11756.

I again caught the unrelated Travis failure "No space left on device",
which is annoying. Looks like the machine needs some disk cleanup.

Unfortunately, I was not well yesterday, and won't be able to look before this evening today.  Considering that #11756 has only been approved today, time is running very short anyway.
I will look this evening.

That being said, we've internally decided to make fairly frequent alphas, with about three weeks' interval between them, so the wait for alpha3 isn't going to be huge.  I think it's better to iron out whatever there is to iron out than to rush it in for alpha2.  Do you agree?

Thanks @levitte for your comments on the timing of this PR.
I agree that it's not a problem if it does not make it into alpha2, mostly because it's not strictly needed anymore for #11470, which I'll be able to merge in about two hours.

Your #11756 has been approved already yesterday, so you should be able to merge it already in half an hour from now, so that should make it into alpha2 easily :)
As soon as this is in, I can rebase #11755 on it and execute the TODOs I placed there, such that you can have a look at its (in my view) final version this evening.

#11756 is in now :wink:

Rebased on merged #11756, so ready for being reviewed.

Travis is pointing out a few nits a well...
https://travis-ci.org/github/openssl/openssl/jobs/686681493#L624-L654

Generally speaking, I like what I see.

Travis is pointing out a few nits a well...
https://travis-ci.org/github/openssl/openssl/jobs/686681493#L624-L654

These were exactly the TODOs to be executed on merge of #11470 and #11755.
Done.

Generally speaking, I like what I see.

Pleased to hear.
All comments addressed.

I like your approach very much. Isn't it worth having this API not on the apps level but on the level of the libcrypto?

I like your approach very much. Isn't it worth having this API not on the apps level but on the level of the libcrypto?

Please no.

I like your approach very much. Isn't it worth having this API not on the apps level but on the level of the libcrypto?

Please no.

It just causes the cut'n'pasting these functions when needed :(

I like your approach very much. Isn't it worth having this API not on the apps level but on the level of the libcrypto?

Please no.

What would make sense IHMO is a slight abstraction (without the stdin feature, and more general password input) of
int load_key_cert_crl(const char *uri, int maybe_stdin,
                      const char *pass, const char *desc,
                      EVP_PKEY **ppkey, X509 **pcert, X509_CRL **pcrl)

for convenient library-level use of the OSSL_STORE API, for instance:
int load_key_cert_crl(const char *uri, BIO *bio,
                      const UI_METHOD *ui_method, void *ui_data, const char *desc,
                      EVP_PKEY **ppkey, X509 **pcert, X509_CRL **pcrl)

where either the uri or the bio would be used as input.

I like your approach very much. Isn't it worth having this API not on the apps level but on the level of the libcrypto?

Please no.

It just causes the cut'n'pasting these functions when needed :(

Indeed. Any why not even more directly jusable
EVP_PKEY *OSSL_STORE_load_key(const char *uri, BIO *bio, const char *desc,
                              const UI_METHOD *ui_method, void *ui_data);
X509 *OSSL_STORE_load_cert(const char *uri, BIO *bio, const char *desc,
                           const UI_METHOD *ui_method, void *ui_data);
X509_CRL *OSSL_STORE_load_key(const char *uri, BIO *bio, const char *desc);

Then we can also obsolete/replace/integrate
X509 *X509_load_http(const char *url, BIO *bio, BIO *rbio, int timeout);
X509_CRL *X509_CRL_load_http(const char *url, BIO *bio, BIO *rbio, int timeout);

BTW, is it possible with OSSL_STORE to set a timeout value in case HTTP-based fetching is used?

BTW, is it possible with OSSL_STORE to set a timeout value in case HTTP-based fetching is used?

There is a ctrl function, isn't there?

I really don't think that application specific routines belong in libcrypto.  If you absolutely want to make them into a public library, it should be a separate one.

I really don't think that application specific routines belong in libcrypto. If you absolutely want to make them into a public library, it should be a separate one.

I agree with this position.

I really don't think that application specific routines belong in libcrypto.
If you absolutely want to make them into a public library, it should be a separate one.

This brings us back to a discussion started pretty exactly four years back: #6986.
In my view also the OSSL_STORE would better be placed in such an application-level lib.
And of course various other rather high-level features that do not really belong to libcrypto,
such as OCSP, S/MIME, and CMP.

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

In my view also the OSSL_STORE would better be placed in such an application-level lib.

I disagree, especially in light if it being used internally in a few places in libcrypto, but also because it's a central ENGINE (and soon provider) interface.

And of course various other rather high-level features that do not really belong to libcrypto,
such as S/MIME, TS, HTTP, OCSP, and CMP.

I agree completely!  There's a lot that's been shoved into libcrypto that's more like protocol libraries (interestingly, we have a separate libssl, go figure!) or application utility libraries.

In my view also the OSSL_STORE would better be placed in such an application-level lib.

I disagree, especially in light if it being used internally in a few places in libcrypto, but also because it's a central ENGINE (and soon provider) interface.

Given this insight I agree.

Pushed - thanks!


Feat/roc 9694

LR vs LR- Fast Track: Screen to capture Defendant hearing requirements
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/ROC-9694
Change description
LR vs LR- Fast Track: Screen to capture Defendant hearing requirements
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x ] No

Please add tests to civil-service code changes where you can.

closing this PR to save some resource for jenkins

Reopening the request after giving demo to Alana, she is fine with change and I can deploy it to production.


/language hi /good-first-issue

This is a Bug Report

Problem:
Proposed Solution:
Page to Update:
https://kubernetes.io/...

/language hi
/good-first-issue

@EternalCoderss can u please describe what issue exactly are you facing
/triage needs-information

/remove-good-first-issue

/remove-help

/close


windows: Add runhcs-wcow-hypervisor runtimeclass to the default config

As part of the effort of getting Windows hypervisor isolated container support working for the CRI entrypoint here, add the runhcs-wcow-hypervisor handler to the default config. This sets the correct SandboxIsolation value that the Windows shim uses to differentiate process vs. hypervisor isolation. This additionally allows io.microsoft.container* annotations for the wcow-process runtime and io.microsoft.virtualmachine* annotations for the vm based runtime.
Note that for K8s users this runtime handler will need to be configured by creating the corresponding RuntimeClass resources on the cluster as it's not the default runtime. This needs a change in the shim that actually sets the HyperV field on the runtime spec to work properly.
PS C:\Users\TestVMAdmin\Desktop> .\crictl.exe pods
POD ID              CREATED             STATE             NAME       NAMESPACE      ATTEMPT      RUNTIME
363319e093c7a       11 minutes ago      Ready             pod        default        1            runhcs-wcow-hypervisor

PS C:\Users\TestVMAdmin\Desktop> hcsdiag list
363319e093c7a688d8d18ad17f5d384e60cb805ba7bf128ea93f0613af5483e9@vm
    VM,                         Running, C2C42EC1-5040-5D0A-AC86-F4BACF6B75CB, containerd-shim-runhcs-v1.exe

cc @kevpar @marosset @jsturtevant @jterry75

Given that this is part of #6862, will this runtime class work as-is once added, or does it depend on other (yet to come) feature work?

@kevpar It needs a small change in the shim to set the HyperV runtime spec field that's mentioned in the description. Just posted the shim PR here https://github.com/microsoft/hcsshim/pull/1388

LGTM pending CI. Should we wait till the hcsshim change is in before merging?

@kevpar I just checked it in, but if you mean wait until we vendor in a tag that contains it here that would be fine with me (and make sense)

Gonna leave this on draft until we get an hcsshim tag with the work to make use of this in https://github.com/microsoft/hcsshim/commit/18f47614a2a08233b53edc47d27a7c68d4802c9f

Need to rebase this finally 🐳, checked in a shim tag that will allow this.


Bug: Can't create multiple triggers to same function

☕ Purpose
Based on #14 this PR aims to allow users to create multiple triggers to the same function. It moves from creating a static name interpolating the trigger with the function name, to using the CronJobTrigger resource (which is unique) instead.
🧐 Checklist

[x] Changed naming pattern.
[x] Updated the tests.

@andresmgot I'm going to take a look on that next week, them I'll comment on this PR, okay?

sure, thanks!


[FLINK-5643] Fix NPE in StateUtil

Introduces a null check to deal with state futures which have a null value.

Forwarding review from #3213. Merging this PR.


Changes made to accommodate review comments

I seems to have lost the changes made under my previous PR. Hence created this new PR with the changes suggested by Shelley in my previous PR.
Previous PR
https://github.com/AdoptOpenJDK/openjdk-tests/pull/472

#472 seems to hold those changes.


[Designer] Bug Adpative card values disappears when switch between tabs in MS Teams

Copied bug from: https://github.com/microsoft/AdaptiveCards/issues/7492
Details from original post:
Problem Description
when user types somthing and before clicking submit button if he changes the chat Adpative card values disappears in MS Teams when he comes back to the chat
Card JSON
{
"$schema": "http://adaptivecards.io/schemas/adpative-card.json",
"type": "AdpativeCard",
"version":"1.3",
"body":[
{
"type": "Input.text",
"lable": "Comments"
}
],
"actions":[
"type": "Action.Submit",
"tittle": "Submit",
"data" :{
   "id":"Test"
}
]
}

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

ID: 3fb4394d-25b1-8752-3996-fe3a2934732d
Version Independent ID: 6d391381-89d0-117c-27cc-00043bd26a36
Content: Cards reference - Teams
Content Source: msteams-platform/task-modules-and-cards/cards/cards-reference.md
Product: msteams
GitHub Login: @surbhigupta12
Microsoft Alias: surbhigupta12

@midhunkumar22 - We will investigate on it and get back to you.

@midhunkumar22 - We are able to repro that issue , We have raised bug for the same and concerned team is looking into it. We will inform you once we get any update.

@midhunkumar22 -Currently, App Studio is deprecated. As such this use-case is no longer supported, since its successor Teams Developer Portal is not embeddable in a Teams tab.


Added missing ng-change

This documentation was missing the ng-change event.

I'm not seeing anything where ng-change is being used in the pagination directive.  I do not believe this is valid.

Hm yea, I think ng-change can be used as a typical use case because ng-model supports ng-change on the same element.
Perhaps instead of mentioning it as a setting, we can mention that ng-change can be used on the pagination element (along with any ngModel formatter directive)?

@wesleycho @chrisirhc There seems to be no reference to access any way to get an event. I'm using the ng-change and can provide a demo if you want to see it working. The ng-change comes coupled with ng-model.

That sounds like a different issue, one worth filing an issue about.

It seems like there is a selectPage(page.number) method that is set as ng-click on every element. But again this is not documented.

Those sound like different issues - in that case, you should file an issue about them. @chrisirhc asked to make a modification to the wording for this PR, get that fixed up and we can merge this :) .

Done :)

Landed as df0bc00522c264963db9e086f758d42247d35070, thanks!


Holy guacamole !

This is amazing!  Now we just need to get it all working on my test set here:
https://github.com/clovett/dgml
Are you open to some joint collaboration?  If so you can email me at email alias "chris", you can probably guess the rest of my email address given my website: http://lovettsoftware.com.
Are you using https://github.com/msaglJS/msagl-js  the graph layout?

Hi,
Thanks for the kind words, but i'm not quite sure what you are suggesting or reporting...
Have you found any specific bugs?
Collaboration? About what?
vscode-dgmlviewer is using Cytoscape.Js - https://js.cytoscape.org/ for rendering the graph.

yes there are lots of bugs if you try and render any of the DGML files I have posted in https://github.com/clovett/dgml.  For example, see the http://lovettsoftware.com/#posts/GraphModel/ specification for details about grouping, aliasing, styling, etc.

I'm aware that the vscode-dgmlviewer only renders a small set of the features specified:

https://schemas.microsoft.com/vs/2009/dgml/dgml.xsd
https://docs.microsoft.com/en-us/previous-versions/visualstudio/visual-studio-2015/modeling/customize-code-maps-by-editing-the-dgml-files?view=vs-2015#to-link-a-document-or-url-to-a-code-element"
http://lovettsoftware.com/#posts/GraphModel/#_top

Many of the issues are related to the limitations of the JavaScript graph libraries, especially the layout of the nodes is a very complex problem as you are probably aware of and i have not found the ultimate perfect library yet.
In the early version of the vscode-dgmlviewer extension it used https://visjs.github.io/vis-network/docs/network/ for rendering the graph. That library could not render grouped nodes, so it was replaced with https://js.cytoscape.org/  that can render grouped nodes. But this library is not perfect either as your examples clearly show. The change of the rendering library was a lengthy, complicated and frustrating process, so doing that once more is probably not going to happen unless someone else has time and energy for that (in my mind) huge task.
But some of the issues your examples illustrate can be fixed, so I have created the issues #193,  #194 and #195. I would appreciate any help improving the vscode-dgmlviewer a lot so feel free to have a look at the code and create a pull request if you have any fixes.


Should Cal2DTriangleArea() add fabs to the return value ?

I am not sure about theory here.
But Cal2DTriangleArea() 's equation is 2D triangle area by coordinates formula except it doesn't have absolute operation.
Should it be fabs( ((v1.x - v0.x)*(v2.y - v0.y) ..... / 2);?

The UVAtlas codebase is quite old, so it's challenging to dig into the history here.
It looks like the callers of this helper function do the fabs instead of it being done in the function itself which would probably have made more sense.


test: refactor browser test utils

Description
Currently runBrowserTests utility is relying on json reporter output browser.json, which is causing a cryptic CI error in https://github.com/vitest-dev/vitest/pull/6512. I rewrote this part to use assertions based on vitest state API.
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[ ] It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
[ ] Ideally, include a test that fails without this PR but passes with it.
[ ] Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

[ ] Run the tests with pnpm test:ci.

Documentation

[ ] If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

[x] Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

We use the json reporter to also indirectly test it. I think if you see cryptic errors, you can change the assertions themselves. Tests already print the stdout and stderr when failed.

We use the json reporter to also indirectly test it.

Yeah, if that's important, we can keep it for runner.test.ts, but I don't think we need to do it from runBrowserTests itself. I reverted the second commit and how does it look?

We use the json reporter to also indirectly test it.

Yeah, if that's important, we can keep it for runner.test.ts, but I don't think we need to do it from runBrowserTests itself. I reverted the second commit and how does it look?

Looks good to me 👍🏻


Explicitly deleting the _temporary folder in a table location which i…

…s created by cascading

:+1:


German translations

Okay, the only things left to do are Eureka Anemos and Byakko Ex. Those are too much right now for me. Gonna do that later xD
Hope there aren't many issues and everything works now + you can adjust the bracket issue I'm having any time ^^

There's plenty more to translate, but this is a giant chunk towards it, so I'm going to go ahead and merge this.


Re-added Champion Profile

Fixed things, and added save for champion and skin

If you could change the indentation to 4 spaces that would be helpful, as that is what the rest of Ace's source uses, also change ts export default (<PluginDescription)>{ ... };
to
...
};
export default plugin;```
for consistency and typechecking reasons.

You forgot to export the plugin in index.ts, Travis shouldn't be saying passed


message catalogue for core node become failed when i18n info directory exists

Before you hit that Submit button....
This issue tracker is for problems with the Node-RED runtime, the editor or the core nodes.
If your issue is:

a general 'how-to' type question,
a feature request or suggestion for a change,
or problems with 3rd party (node-red-contrib-) nodes

please use the mailing list, slack team or ask a question on Stack Overflow and tag it node-red.
That way the whole Node-RED user community can help, rather than rely on the core development team.
So you have a real issue to raise...
To help us understand the issue, please fill-in as much of the following information as you can:
What are the steps to reproduce?

Create nodes/core/<category>/locales directory (in order to put info texts for core nodes).

What happens?

lookup of message catalogue become to fail (e.g. Invalid JSONata expression: E\xpected ")" before end of expression become node-red/change:change.errors.invalid-expr).

What do you expect to happen?

Message catalogue lookup succeeds.

Please tell us about your environment:

[x] Node-RED version: 0.18.2
[x] node.js version: v7.8.0
[x] npm version: 5.5.1
[x] Platform/OS: MacOSX
[x] Browser: Safari

Closed by #1616


Bad train/test split

In https://github.com/davidsandberg/facenet/blob/master/facenet/src/facenet.py#L540
You have split based on classes. I think it should be split within each class instead.

Hi,
I have added the possibility (split_mode==SPLIT_IMAGES) to split the data based on images instead of classes. It looks like it works ok but i haven't ran the training for any longer time yet.
Depending on how the split_ratio is set it can happen that the number of images for some classes becomes very few, and then it will be impossible to use the class for validation. The code becomes a bit more complex due to this and i think there may be cases where this split gives strange validation results.


Add touch drag to crosshairs tool

Please check if the PR fulfills these requirements

[ ] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bug fix

What is the current behavior? (You can also link to an open issue here)
Crosshairs tool doesn't work with touch

What is the new behavior (if this is a feature change)?
Crosshairs tool works with touch

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Other information:

@catalinaduplat if you can resolve an existing conflicts, I will merge this ASAP

Ok, I updated the branch and there are no conflicts


rewrite calls

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 94.07%. Comparing base (986fc71) to head (6e15a39).
Report is 5 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1453       +/-   ##
===========================================
+ Coverage   73.79%   94.07%   +20.28%
===========================================
  Files          30        8       -22
  Lines       10886      388    -10498
===========================================
- Hits         8033      365     -7668
+ Misses       2853       23     -2830

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Synchronizes search parameters in SQL

Description
When we update or create search parameters in SQL, we need to reflect the changes in the C# dictionary that maps a search parameter's URI to its ID.
Before this PR, we were only doing this in the UpsertStatuses() method in SqlServerSearchParameterStatusDataStore.cs, which successfully updated the C# dictionary for the calling instance but not any other instances. This was causing us to see the error: The given key 'http://hl7.org/fhir/SearchParameter/Patient-917dd1e1bf838a9c5893706650d088c6f1ff' was not present in the dictionary..
This PR:

Adds a SyncStatuses method that is called from the SearchParameterStatusManager, which synchronizes dbo.SearchParam with the SqlServerFhirModel dictionary, _searchParamUriToId
Adds a new schema file that makes the GetSearchParamStatuses stored proc return search parameter ID in addition to the UpsertSearchParamStatuses stored proc
Creates a SQL-only ResourceSearchParameterStatus class to track the search parameter ID in SQL

Related issues
Addresses AB#82454 and #1974.
Testing
Ran two instances locally, created a new search parameter, and created a resource that the new search parameter targets.
FHIR Team Checklist

✅ Update the title of the PR to be succinct and less than 50 characters
✅ Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
✅ Tag the PR with the type of update: Bug, Dependencies, Enhancement, or New-Feature
✅ Tag the PR with Azure API for FHIR if this will release to the managed service
✅ Review squash-merge requirements

Semver Change (docs)
Patch (new schema version)

Next Steps
Remove the C# dictionary that tracks the URI to ID mapping a replace it with a table in SQL. Storing this info at the data store layer will prevent us from having to worry about synchronizing across instances. I created a work item to track this: AB#82593
FYI @feordin


#006 Release site functionality

[x] Update the version. ****
[x] Push /release the changes to the PyPI and do the first test in any other environment.

released this functionality at: https://pypi.org/project/PYRJrenderer/0.0.3/


[Docs] Enhance documentation on styling or using frontend frameworks

Currently, it's not clear how I would use a frontend framework like Bootstrap with lona.
Could the documentation on this be improved, to include a full example of how lona would be used with something like bootstrap, tailwind(if possible, likely needs custom integration due to the css being compiled), bulma etc?

@laundmo: I updated lona_bootstrap_5 and will release after the next Lona release, because the new widgets depend on some new Lona API (#34 ).
Do you think an example integration like this plus https://lona-web.org/end-user-documentation/frontends.html and https://lona-web.org/end-user-documentation/html.html#frontend-widgets are enough information?

not really.
the issue is there the docs show all the concepts individually but never how they can work together coherently. adding a page explaining the basics of creating something like lona bootstrap would really tie things together.
our maybe just improving the docs pages you linked.
i think the underlying issue is that you obviously know the big picture of how it fits together, but its less obvious to anyone else reading the docs.

I see. I will add an article to the cookbook section named "Integrating a third party library", explaining the steps i have taken to create lona_bootstrap_5

I agree that a page showing all the setup code together would be really helpful. The documentation for custom frontends is kind of far down, and I feel some users won't take the time to make it there. I would be happy to help here! I plan on using this for a personal project.

@steezeburger Some help would be great! :) Sorry that it takes me so long, there was much bug fixing required the last days. This is the next thing i will work on

@laundmo, @steezeburger: I started a cookbook article. Could you give some feedback if this is the right direction?


Add changelog for meta-mender/thud-v2019.03.

Travis is extremely slow today. These are pretty standard changes, so will just merge to unblock the release.


Verify email validation

We have added validation for email addresses at the model level. We should verify that the view/controller is allowing the model to handle validations and that errors are being properly bubbled up to the UI.
Related to Pivotal ticket https://www.pivotaltracker.com/story/show/133918961

verified this in #234


Fix Epsilon

I was reading some theory about RL and found your git.
While I was playing with the second project, I found that it wasn't doing much improvement because of the random action.
I modified to an e-greedy and now it works pretty fine.
:D

Thanks for the update. The code is only for a demonstration, as it does follow the RL rule and doesn't have an extra code, I will close this pull request. Thanks again for your contribution.


Add iOS Generation

I added generation for iOS with new agrument for platform. Cloned all structures and examples from android, didn't know what to do with them.
There are few moments requiring improvements imo, I don't know Rust enough to resolve them myself.
Tests will be in another PR because I want them (PRs) to be atomic.
Example of generated files:
Source file:
[[Src1]]
  [lorem]
    en = Lorem %d ipsumkekum
    ru = Лорем %d ипсумкекум

  [ooo]
    en = Ooooo %@ ooooO
    ru = Ооооо %@ ооооО

en.lproj/Localizable.strings:
"lorem" = "Lorem %d ipsumkekum";
"ooo" = "Ooooo %s ooooO";

Also there is a problem that parsing transforms %@ to %s, on iOS we need it to stay %@

Was going to merge this, but noticed that CI has failed due to some android-gen tests not passing:
https://github.com/appKODE/utas/actions/runs/6110195317/job/16627470978?pr=32
Is this fixable?


Validation: Added Missing Descriptions

Added missing metadata descriptions and added missing preserve views to hyperlinks.

Docs Build status updates of commit 91bae4b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Skype/UCMA/informational-performance-counters.md
:bulb:Suggestion

Details

Skype/UCMA/get-started-with-ucma-5-0-development.md
:white_check_mark:Succeeded

Skype/UCMA/high-availability-and-failover-in-ucma-5-0.md
:white_check_mark:Succeeded

Skype/UCMA/high-availability-and-recovery.md
:white_check_mark:Succeeded

Skype/UCMA/impersonating-a-user.md
:white_check_mark:Succeeded

Skype/UCMA/in-meeting-during-the-conference.md
:white_check_mark:Succeeded

Skype/UCMA/incoming-message-dispatching.md
:white_check_mark:Succeeded

Skype/UCMA/incoming-messages-performance-counters.md
:white_check_mark:Succeeded

Skype/UCMA/infrastructure-enhancements.md
:white_check_mark:Succeeded

Skype/UCMA/installing-ucma-5-0-sdk.md
:white_check_mark:Succeeded

Skype/UCMA/instantmessagingcall.md
:white_check_mark:Succeeded

Skype/UCMA/instantmessagingmcusession.md
:white_check_mark:Succeeded

Skype/UCMA/inviting-a-new-participant.md
:white_check_mark:Succeeded

Skype/UCMA/localownerpresence.md
:white_check_mark:Succeeded

Skype/UCMA/managed-sip-stack-performance-counters.md
:white_check_mark:Succeeded

Skype/UCMA/managing-ucma-5-0-applications.md
:white_check_mark:Succeeded

Skype/UCMA/mcu-call-establishment-and-handling.md
:white_check_mark:Succeeded

Skype/UCMA/tonecontroller-quickstart.md
:white_check_mark:Succeeded

Skype/UCMA/transactions-performance-counters.md
:white_check_mark:Succeeded

Skype/UCMA/triggering-sdp-renegotiations.md
:white_check_mark:Succeeded

Skype/UCMA/troubleshooting-media-connectivity-issues.md
:white_check_mark:Succeeded

Skype/UCMA/trusted-conference-users.md
:white_check_mark:Succeeded

Skype/UCMA/trusted-conferencing-user-audio-routes.md
:white_check_mark:Succeeded

Skype/UCMA/trusted-conferencing-user-conversation-model-api.md
:white_check_mark:Succeeded

Skype/UCMA/trusted-conferencing-user-conversation-model.md
:white_check_mark:Succeeded

This comment lists only the first 25 files in the pull request.

Skype/UCMA/informational-performance-counters.md

Line 1048, Column 6: [Suggestion: disallowed-html-attribute - See documentation] HTML attribute 'style' on tag 'col' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 1239, Column 6: [Suggestion: disallowed-html-attribute - See documentation] HTML attribute 'style' on tag 'col' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 97978f7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Skype/UCMA/get-started-with-ucma-5-0-development.md
:white_check_mark:Succeeded

Skype/UCMA/high-availability-and-failover-in-ucma-5-0.md
:white_check_mark:Succeeded

Skype/UCMA/high-availability-and-recovery.md
:white_check_mark:Succeeded

Skype/UCMA/impersonating-a-user.md
:white_check_mark:Succeeded

Skype/UCMA/in-meeting-during-the-conference.md
:white_check_mark:Succeeded

Skype/UCMA/incoming-message-dispatching.md
:white_check_mark:Succeeded

Skype/UCMA/incoming-messages-performance-counters.md
:white_check_mark:Succeeded

Skype/UCMA/informational-performance-counters.md
:white_check_mark:Succeeded

Skype/UCMA/infrastructure-enhancements.md
:white_check_mark:Succeeded

Skype/UCMA/installing-ucma-5-0-sdk.md
:white_check_mark:Succeeded

Skype/UCMA/instantmessagingcall.md
:white_check_mark:Succeeded

Skype/UCMA/instantmessagingmcusession.md
:white_check_mark:Succeeded

Skype/UCMA/inviting-a-new-participant.md
:white_check_mark:Succeeded

Skype/UCMA/localownerpresence.md
:white_check_mark:Succeeded

Skype/UCMA/managed-sip-stack-performance-counters.md
:white_check_mark:Succeeded

Skype/UCMA/managing-ucma-5-0-applications.md
:white_check_mark:Succeeded

Skype/UCMA/mcu-call-establishment-and-handling.md
:white_check_mark:Succeeded

Skype/UCMA/tonecontroller-quickstart.md
:white_check_mark:Succeeded

Skype/UCMA/transactions-performance-counters.md
:white_check_mark:Succeeded

Skype/UCMA/triggering-sdp-renegotiations.md
:white_check_mark:Succeeded

Skype/UCMA/troubleshooting-media-connectivity-issues.md
:white_check_mark:Succeeded

Skype/UCMA/trusted-conference-users.md
:white_check_mark:Succeeded

Skype/UCMA/trusted-conferencing-user-audio-routes.md
:white_check_mark:Succeeded

Skype/UCMA/trusted-conferencing-user-conversation-model-api.md
:white_check_mark:Succeeded

Skype/UCMA/trusted-conferencing-user-conversation-model.md
:white_check_mark:Succeeded

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@lindalu-MSFT
The Content & Learning team is fixing build validation errors on docs.microsoft.com for the rest of H2. This will eliminate potential accessibility, security, and usability issues. This PR includes only build validation fixes and does not change other content. Please review within five business days and merge or comment in the PR with any changes you’d like to see. Thank you!


add  color with the entity value

Hi ! thanks for uoy job :)
Can you add  color with the entity value?
exemple with mini graph card :
color_thresholds:

color: '#1da4f2'
value: 5
color: '#11f13a'
value: 28
color: '#f0da11'
value: 31
color: '#ef5a0f'
value: 36
color: '#ef1d0f'
value: 40

thanks

Yes please allow the color to be controlled by thresholds. I would like to use this card with the sensors I have on my pool like pH which has an optimal range. I am using the Gauge card with segment but would love to use this instead:
segments:
- from: 0
color: '#db4437'
- from: 6.8
color: '#ffa600'
- from: 7.1
color: '#43a047'
- from: 7.7
color: '#ffa600'
- from: 8.1
color: '#db4437'

@swingerman any chance to get this feature implemented ? almost 2 years now :)

@swingerman any chance to get this feature implemented ? almost 2 years now :)

There is a chance in the coming weeks. I am affected by the war in Ukraine, unfortunately...

Please check v0.1.6-beta.4
You can set severity this way:
severity:
  - value: 20
    color: red
  - value: 50
    color: yellow
  - value: 80
    color: green

color can be in almost any format (defined in readme)

Hi is it a way to include range ?
From 0 to 20 color Red
from 20 to 70 yellow
grater than 70 green
??

Yes. Each severity step defines a color above it's value. The color changes if there is severity set with a higher value.
See above.