How hidden PHP version?

As security, I need to hidden the PHP version, but I don't where will be to set the 'expose_php Off' of 'php.ini' in the container php-fpm or workspace? Somebody was trying to do that, can share your setting? Thanks a lot for you.

@carveybunt Hiding the version doesn't do a lot to increase your security, but the ini files all exist in the php-fpm folder. Change the ini file for the version you're running and rebuild php-fpm.

@jonpage999 Thank you. I'll try it later，because I thought it was in the workspace container, so I tried to modify php.ini in the workspace container without success, so I went to ask for help.


[stable/kubernetes-dashboard] Add priority class

What this PR does / why we need it:
This adds priorityClassName as an option on podSpec to allow for setting pod priority
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

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

[X] DCO signed
[X] Chart Version bumped
[X] Variables are documented in the README.md
[X] title of the PR contains starts with chart name e.g. [stable/chart]

/assign @desaintmartin


Add Support for the API of Poll 2.0 Features

As the title, this pull request adds support for poll 2.0 API.

Thats great! For future, try to use my scripts for API generation, that does that automatically.
/API/download_api_docs.sh
/API/generate_wrappers.rb

Oh I'm sorry that I didn't know the existence of these scripts. Do I need to revert my manual changes?

Will be more consistent if we keep generated sources generated. Moreover, we will keep script correctness updated. Thanks

It seems the destination folder in the API generating script is wrong and I fixed it.
And BTW it seems there's room for improvement for the auto-generated API, for example the poll type would be better represented as a enum instead simply a string. Moreover, it is not conforming to the official Swift API Design Guidelines that:

Acronyms and initialisms that commonly appear as all upper case in American English should be uniformly up- or down-cased according to case conventions:
var utf8Bytes: [UTF8.CodeUnit]
var isRepresentableAsASCII = true
var userSMTPServer: SecureSMTPServer

An example of the violation would be the generated variable name correctOptionId, which should be correctOptionID according to the guide.

Why are there so many conflicts....

It seems the destination folder in the API generating script is wrong and I fixed it.
And BTW it seems there's room for improvement for the auto-generated API, for example the poll type would be better represented as an enum instead simply a string. Moreover, it is not conforming to the official Swift API Design Guidelines that:

Acronyms and initialisms that commonly appear as all upper case in American English should be uniformly up- or down-cased according to case conventions:
var utf8Bytes: [UTF8.CodeUnit]
var isRepresentableAsASCII = true
var userSMTPServer: SecureSMTPServer

An example of the violation would be the generated variable name correctOptionId, which should be correctOptionID according to the guide.

Good catch, but for script it will be impossible to distinguish acronyms and initialisms. So for now I just translate snake_case to swift friendly camelCase.
Lets keep generated API clean, without additional logic. This helps us to maintain our API wrappers updated (methods, models, docs).
If you want improve framework by some additional helpers, you could write them and add to PR separately.
About conflicts, I'll check.

Please use this git patch for your branch.
`From 6fda1b359f8e67d5f7d6da4c3eebddee823114fd Mon Sep 17 00:00:00 2001
From: givip<EMAIL_ADDRESS>Date: Mon, 3 Feb 2020 18:18:06 +0400
Subject: [PATCH] Fix

API/generate_wrappers.rb                                 | 9 +++++++--
Sources/Telegrammer/Bot/Telegram/Models/PollAnswer.swift | 4 ++--
2 files changed, 9 insertions(+), 4 deletions(-)
diff --git a/API/generate_wrappers.rb b/API/generate_wrappers.rb
index 287013d..5c41112 100755
--- a/API/generate_wrappers.rb
+++ b/API/generate_wrappers.rb
@@ -213,8 +213,10 @@ def convert_type(var_name, var_desc, var_type, type_name, var_optional)
suffix = is64bit ? '64' : ''
return "Int#{suffix}?"
when ['Integer', false]

  is64bit = var_name.include?("user_id") || var_name.include?("chat_id") || var_desc.include?("64 bit integer") ||

  					(type_name == 'User' && var_name == 'id')

  is64bit = var_name.include?("user_id") ||

             var_name.include?("chat_id") ||

             var_desc.include?("64 bit integer") ||

             (type_name == 'User' && var_name == 'id')
  suffix = is64bit ? '64' : ''
  return "Int#{suffix}"

when ['Float number', true], ['Float', true]
@@ -242,6 +244,9 @@ def convert_type(var_name, var_desc, var_type, type_name, var_optional)
end
elsif var_type.start_with?(array_prefix) then
var_type.slice! array_prefix

       if var_type == 'Integer' then

           var_type = 'Int'

       end
  	# Present optional arrays as empty arrays
  	if var_optional then
  		return "[#{var_type}]?"

diff --git a/Sources/Telegrammer/Bot/Telegram/Models/PollAnswer.swift b/Sources/Telegrammer/Bot/Telegram/Models/PollAnswer.swift
index 04f470e..3c707e5 100644
--- a/Sources/Telegrammer/Bot/Telegram/Models/PollAnswer.swift
+++ b/Sources/Telegrammer/Bot/Telegram/Models/PollAnswer.swift
@@ -23,10 +23,10 @@ public final class PollAnswer: Codable {
public var user: User
 /// 0-based identifiers of answer options, chosen by the user. May be empty if the user retracted their vote.

public var optionIds: [Integer]

public var optionIds: [Int]

public init (pollId: String, user: User, optionIds: [Integer]) {

public init (pollId: String, user: User, optionIds: [Int]) {
self.pollId = pollId
self.user = user
self.optionIds = optionIds
--
2.17.1

`

I first ran git apply and committed, which resulted the commit above. Then I tried git rebase, getting the following:

Error Message
First, rewinding head to replay your work on top of it...
Applying: Add Some of The New Poll Attributes
Applying: Add PollAnswer
Applying: Add PollAnswerHandler
Applying: Add All Left New Poll Properties
Applying: Fix Destination in API Generating Script
Using index info to reconstruct a base tree...
M	API/generate_wrappers.rb
Falling back to patching base and 3-way merge...
Auto-merging API/generate_wrappers.rb
No changes -- Patch already applied.
Applying: Update Generated API
Using index info to reconstruct a base tree...
M	Sources/Telegrammer/Bot/Telegram/Methods/Bot+deleteChatPhoto.swift
M	Sources/Telegrammer/Bot/Telegram/Methods/Bot+getUpdates.swift
M	Sources/Telegrammer/Bot/Telegram/Methods/Bot+kickChatMember.swift
M	Sources/Telegrammer/Bot/Telegram/Methods/Bot+restrictChatMember.swift
M	Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendAudio.swift
M	Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendInvoice.swift
M	Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendPoll.swift
M	Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendSticker.swift
M	Sources/Telegrammer/Bot/Telegram/Methods/Bot+setChatDescription.swift
M	Sources/Telegrammer/Bot/Telegram/Methods/Bot+setChatPhoto.swift
M	Sources/Telegrammer/Bot/Telegram/Methods/Bot+setChatTitle.swift
M	Sources/Telegrammer/Bot/Telegram/Methods/Bot+setWebhook.swift
M	Sources/Telegrammer/Bot/Telegram/Models/Animation.swift
M	Sources/Telegrammer/Bot/Telegram/Models/Audio.swift
M	Sources/Telegrammer/Bot/Telegram/Models/Chat.swift
M	Sources/Telegrammer/Bot/Telegram/Models/ChatMember.swift
M	Sources/Telegrammer/Bot/Telegram/Models/ChatPhoto.swift
M	Sources/Telegrammer/Bot/Telegram/Models/Document.swift
M	Sources/Telegrammer/Bot/Telegram/Models/File.swift
M	Sources/Telegrammer/Bot/Telegram/Models/InlineQueryResultAudio.swift
M	Sources/Telegrammer/Bot/Telegram/Models/InlineQueryResultCachedAudio.swift
M	Sources/Telegrammer/Bot/Telegram/Models/PassportFile.swift
M	Sources/Telegrammer/Bot/Telegram/Models/PhotoSize.swift
M	Sources/Telegrammer/Bot/Telegram/Models/Sticker.swift
M	Sources/Telegrammer/Bot/Telegram/Models/StickerSet.swift
M	Sources/Telegrammer/Bot/Telegram/Models/Video.swift
M	Sources/Telegrammer/Bot/Telegram/Models/VideoNote.swift
M	Sources/Telegrammer/Bot/Telegram/Models/Voice.swift
.git/rebase-apply/patch:284: trailing whitespace.

.git/rebase-apply/patch:352: trailing whitespace.

warning: 2 lines add whitespace errors.
Falling back to patching base and 3-way merge...
Auto-merging Sources/Telegrammer/Bot/Telegram/Models/Voice.swift
CONFLICT (content): Merge conflict in Sources/Telegrammer/Bot/Telegram/Models/Voice.swift
Auto-merging Sources/Telegrammer/Bot/Telegram/Models/VideoNote.swift
CONFLICT (content): Merge conflict in Sources/Telegrammer/Bot/Telegram/Models/VideoNote.swift
Auto-merging Sources/Telegrammer/Bot/Telegram/Models/Video.swift
CONFLICT (content): Merge conflict in Sources/Telegrammer/Bot/Telegram/Models/Video.swift
Auto-merging Sources/Telegrammer/Bot/Telegram/Models/Sticker.swift
CONFLICT (content): Merge conflict in Sources/Telegrammer/Bot/Telegram/Models/Sticker.swift
Removing Sources/Telegrammer/Bot/Telegram/Models/PollType.swift
Auto-merging Sources/Telegrammer/Bot/Telegram/Models/PhotoSize.swift
CONFLICT (content): Merge conflict in Sources/Telegrammer/Bot/Telegram/Models/PhotoSize.swift
Auto-merging Sources/Telegrammer/Bot/Telegram/Models/PassportFile.swift
CONFLICT (content): Merge conflict in Sources/Telegrammer/Bot/Telegram/Models/PassportFile.swift
Auto-merging Sources/Telegrammer/Bot/Telegram/Models/File.swift
CONFLICT (content): Merge conflict in Sources/Telegrammer/Bot/Telegram/Models/File.swift
Auto-merging Sources/Telegrammer/Bot/Telegram/Models/Document.swift
CONFLICT (content): Merge conflict in Sources/Telegrammer/Bot/Telegram/Models/Document.swift
Auto-merging Sources/Telegrammer/Bot/Telegram/Models/ChatPhoto.swift
CONFLICT (content): Merge conflict in Sources/Telegrammer/Bot/Telegram/Models/ChatPhoto.swift
Auto-merging Sources/Telegrammer/Bot/Telegram/Models/ChatMember.swift
CONFLICT (content): Merge conflict in Sources/Telegrammer/Bot/Telegram/Models/ChatMember.swift
Auto-merging Sources/Telegrammer/Bot/Telegram/Models/Chat.swift
CONFLICT (content): Merge conflict in Sources/Telegrammer/Bot/Telegram/Models/Chat.swift
Auto-merging Sources/Telegrammer/Bot/Telegram/Models/Audio.swift
CONFLICT (content): Merge conflict in Sources/Telegrammer/Bot/Telegram/Models/Audio.swift
Auto-merging Sources/Telegrammer/Bot/Telegram/Models/Animation.swift
CONFLICT (content): Merge conflict in Sources/Telegrammer/Bot/Telegram/Models/Animation.swift
Auto-merging Sources/Telegrammer/Bot/Telegram/Methods/Bot+setWebhook.swift
Auto-merging Sources/Telegrammer/Bot/Telegram/Methods/Bot+setChatTitle.swift
Auto-merging Sources/Telegrammer/Bot/Telegram/Methods/Bot+setChatPhoto.swift
CONFLICT (add/add): Merge conflict in Sources/Telegrammer/Bot/Telegram/Methods/Bot+setChatPermissions.swift
Auto-merging Sources/Telegrammer/Bot/Telegram/Methods/Bot+setChatPermissions.swift
Auto-merging Sources/Telegrammer/Bot/Telegram/Methods/Bot+setChatDescription.swift
Auto-merging Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendSticker.swift
Auto-merging Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendPoll.swift
Auto-merging Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendInvoice.swift
Auto-merging Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendAudio.swift
Auto-merging Sources/Telegrammer/Bot/Telegram/Methods/Bot+restrictChatMember.swift
Auto-merging Sources/Telegrammer/Bot/Telegram/Methods/Bot+kickChatMember.swift
Auto-merging Sources/Telegrammer/Bot/Telegram/Methods/Bot+getUpdates.swift
Auto-merging Sources/Telegrammer/Bot/Telegram/Methods/Bot+deleteChatPhoto.swift
error: Failed to merge in the changes.
Patch failed at 0006 Update Generated API
hint: Use 'git am --show-current-patch' to see the failed patch
Resolve all conflicts manually, mark them as resolved with
"git add/rm <conflicted_files>", then run "git rebase --continue".
You can instead skip this commit: run "git rebase --skip".
To abort and get back to the state before "git rebase", run "git rebase --abort".

@CaptainYukinoshitaHachiman If you are not agains, I'll add this changes by myself

It's OK.

Oh, The reason is that we are not updating version 0.5.4 anymore. We should add those updates to version 1.0.0.
I'll update that


image/api load into the flow

Feature Request
It would be great to be able to load images or other format into the playground or all via the api
Motivation
it would great in order to connect with other api such as stable diffusion
Your Contribution
No response

Langflow already supports handling image data, as it is now multi-modal and can handle images, with more formats to be supported soon [1]. Additionally, Langflow is designed to be agnostic to any model, API, or database, which means it can integrate with external APIs such as Stable Diffusion [2].
To continue talking to Dosu, mention @dosu.

thanks any documentation, nodes available or general information beside what you shared?

thats fine and there is not issue for me, back to my question is how to you display the image in the flow, playground

not relevant answer, I'm asking about displaying the image previously generated with an api for example


[Bug] TC-DGGEN-2.3 PIXIT.DGGEN.ENABLEKEY is not used by the TH

Describe the bug
Running TC-DGGEN-2.3 using the TH yaml script, the script does not use the PIXIT.DGGEN.ENABLEKEY value. Instead the script uses the default value, leading to a constraint issue.
Steps to reproduce the behavior
Run TC-DGGEN-2.3 using the yaml script.
Expected behavior
The script uses the  PIXIT.DGGEN.ENABLEKEY value and not the default value.
Log files
TC-DGGEN_2-3_2024_03_06_08_55_48.log
PICS file
No response
Screenshots
No response
Environment
2.10-beta3+spring2024
Additional Information
No response

You can add     "PIXIT.DGGEN.ENABLEKEY":"hex:xxxxxxxxxx..."     to  " test parameters "

@CoekaertsJasper Did adding the PIXIT value to test parameters help resolve the issue ?

@CoekaertsJasper any update ?

Closing as the originator seems to have lost interest.


Metrics View to ignore specific Instruments

According to the spec, Views should allow users to customize specific Instruments or ignore specific ones, I cannot find any way to ignore Instruments using current implementation, am I missing something?, is there any way to achieve this right now or any plan to support it in the future?

You can drop events from the metric instrument by:
import { MeterProvider, View, DropAggregation } from '@opentelemetry/sdk-metrics';

const meterProvider = new MeterProvider({
  views: [
    new View({
      instrumentName: '<your-instrument-name>',
      aggregation: new DropAggregation(),
    }),
  ],
});

Thank you @legendecas exactly what I was looking for.


SE-0399: repeat each (repeat each t) parses as function call

Issue Kind
Parse of Valid Source Produced Invalid Syntax Tree
Source Code
func variadic<each T>(element: repeat each T) {
  _ = repeat each (repeat each element)
}

Description
swift-syntax twin of https://github.com/apple/swift/issues/69003.

Tracked in Apple’s issue tracker as rdar://116573588


Inconsistencies in Example Code Execution

Thank you for providing this repository. However, I've encountered some issues while trying to run the example code.
It seems that certain variables or module paths are inconsistent, which prevents the code from executing correctly. For instance:
In ullme/models/bidirectional_modelings/modeling_bidirectional_llama.py, line 29 references src.models, but src does not seem to exist.
Additionally, the README mentions running python -m genc.main, but genc.main is also missing.
Could you please provide a working example of the training pipeline? This would greatly help in understanding and utilizing the code. Thank you for your assistance!

I appreciate your interest in our work. We updated the codebase to be compatible with HF 4.6!


PHP 70/71/72

Is there a change to make this PHP 70 / 71 / 72 ready?

Acknowledge receipt of your issue.

Fixed by http://pecl.php.net/package/jsonnet/1.3.0


graylog: 3.3.0 -> 3.3.1

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/graylog/versions.
meta.description for graylog is: "Open source log management solution"
meta.homepage for graylog is: "https://www.graylog.org/"
meta.changelog for graylog is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 3.3.1 with grep in /nix/store/j4bb2x70kccf3vcixyr0am28i1c4jp92-graylog-3.3.1

directory tree listing: https://gist.github.com/7745841b8196352e7c9ca655710875c4

du listing: https://gist.github.com/499e78d6b3d13d6f11b4e8c22b807fde

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
graylog

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/j4bb2x70kccf3vcixyr0am28i1c4jp92-graylog-3.3.1 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A graylog https://github.com/r-ryantm/nixpkgs/archive/cb053733b57b733919a4815f8f25ead9f3a8e20b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/j4bb2x70kccf3vcixyr0am28i1c4jp92-graylog-3.3.1
ls -la /nix/store/j4bb2x70kccf3vcixyr0am28i1c4jp92-graylog-3.3.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

1 package built:
- graylog

Maintainer pings
cc @fadenb for testing.

I just created #90597 to replace this one.
Closing this as the other one also bumps plugin versions.


Update Readme to point to v1 Tailwind documentation

Tailwinds has now released v2. Upgrade this repo to Tailwinds v2 isn't really necessary, but this readme points to the default Tailwinds docs, which is for V2. Things like customising colours has now changed, and took me some time to realise I was reading the wrong docs for this repo.

Thanks!

Thanks!


Make Ollama interface, parameters, and messages public

This Pull request fixes #118 by making the relevant data structures public and (where possible) sendable.

Thanks


Fix compilation warnings

/Users/mat/Data/Workspace/forks/PsychicHttp/src/PsychicHttpServer.cpp: In member function 'esp_err_t PsychicHttpServer::start()':
/Users/mat/Data/Workspace/forks/PsychicHttp/src/PsychicHttpServer.cpp:116:51: warning: missing initializer for member 'httpd_uri::user_ctx' [-Wmissing-field-initializers]
  116 |       .handler = PsychicHttpServer::requestHandler};
      |                                                   ^
/Users/mat/Data/Workspace/forks/PsychicHttp/src/PsychicHttpServer.cpp:116:51: warning: missing initializer for member 'httpd_uri::is_websocket' [-Wmissing-field-initializers]
/Users/mat/Data/Workspace/forks/PsychicHttp/src/PsychicHttpServer.cpp:116:51: warning: missing initializer for member 'httpd_uri::handle_ws_control_frames' [-Wmissing-field-initializers]
/Users/mat/Data/Workspace/forks/PsychicHttp/src/PsychicHttpServer.cpp:116:51: warning: missing initializer for member 'httpd_uri::supported_subprotocol' [-Wmissing-field-initializers]
/Users/mat/Data/Workspace/forks/PsychicHttp/src/PsychicHttpServer.cpp: In member function 'PsychicEndpoint& PsychicHttpServer::on(const char*, int, PsychicHandler*)':
/Users/mat/Data/Workspace/forks/PsychicHttp/src/PsychicHttpServer.cpp:232:57: warning: missing initializer for member 'httpd_uri::handle_ws_control_frames' [-Wmissing-field-initializers]
  232 |       .supported_subprotocol = handler->getSubprotocol()};

On a general note, it would be nice to add -Wall -Wextra everywhere in the compilation flags and make sure we run a local build to check, because this is really frustrating getting warnings from libraries in final projects, locations that we do not have control over.

Adding those extra build flags to the platformio example as well.


Add support for different naming conventions to DataObject converter

Inspired by #201.
This adds the ability to generate converters with the following conventions:

Upper Camel Case (UpperCamelCase)
Lower Camel Case (lowerCamelCase)
Kebab Case (kebab-case)
Snake Case (snake-case)

e.g. the following DataObject will generate a converter that serializes exampleName as example-name:
@DataObject(generateConverter = true, caseFormat = CaseFormat.KEBAB)
public class KebabCaseDataObject {
  private String exampleName;
  ...
}

In addition, the @DataObjectProperty annotation enables custom naming ~conventions~ on a per-field basis.
e.g.
  @DataObjectProperty("listOfFoo")
  private List<Object> fooList;
  @DataObjectProperty("map-of-bar")
  private Map<String, Object> barMap;
  @DataObjectProperty("string_of_baz")
  private String bazString;

Unfortunately it was necessary to wrap Case with the CaseFormat enum as annotation defaults must be compile-time constant. (Funnily enough, Case used to be an Enum)
Not certain that "CaseFormat" is the most apt name, however, so let me know if you have a better one. (Perhaps NamingConvention?)

looks good, there are few things I'd like to be changed.
I think we should keep one enum for cases, so can you modify the existing use a single enum (the one you created) instead of having two ? We will change the vertx code where it's used.

The redundant enum pains me as well, however, I created a separate Case enum because:

Use classes instead of enum because MVEL does not like enum with abstract methods
https://github.com/vert-x3/vertx-codegen/commit/fa84d57c1c64938c439e9e71181c659da2c6bccd

Is this no longer an issue?

I've replaced @DataObjectProperty(case: CaseFormat) with a more pragmatic @DataObjectProperty(value: String) — akin to Jackson's 'JsonProperty'.

@rgmz it's not longer an issue we are moving away from MVEL, so please proceed

can we make two separate PR, one first for specifying the case of the data object entirely and another one after for enabling per property naming, that will allow to make the review of the PR easier.

@vietj Done & done: #211
(I removed the @DataObjectProperty changes from this branch; let me know if you want me to push a clean branch altogether with only those specific changes.)

Hi all, any progress?

@eutkin actually no sorry, we could merge it I think

@vietj It's been a while; give it another look (when you have the time) and let me know if there are any other changes you'd like made.

@vietj, @rgmz i am waiting this feature at long ago :)

@eutkin good to know, let's target 3.7.1

Re-created this PR as the original branch became orphaned and I couldn't fix the merge conflicts.
#259

Why is this closed, PR has not been merged?

"Re-created this PR as the original branch became orphaned and I couldn't fix the merge conflicts."

so there is a new PR

we will likely merge it in 4 as we want to use data object for doing basic operations like database row mapping to data objects


Refactor module name to match repo

github.com/alluxio/k8s-operator to github.com/Alluxio/k8s-operator for consistency with actual repo name.
running into errors when trying to use as dep
go get<EMAIL_ADDRESS>
go<EMAIL_ADDRESS>parsing go.mod:
	module declares its path as: github.com/alluxio/k8s-operator
	        but was required as: github.com/Alluxio/k8s-operator

is anyone using v1.0.1 as a go dependency? bc this would cause a minor conflict if they try to upgrade in the future

is anyone using v1.0.1 as a go dependency? bc this would cause a minor conflict if they try to upgrade in the future

No need to worry about it.


vs2010: Fix implementation of strcasestr

A haystack which is shorter than the needle resulted in negative value
for length_haystack which was forced to a very large unsigned value.
The resulting buffer overflow while reading the haystack would crash
text2image when it was called with a short font name.
Signed-off-by: Stefan Weil<EMAIL_ADDRESS>

thanks

https://github.com/amitdo/text2tif/blob/master/port/strcasestr.cpp
This is based on a more updated version of the EFL code. You might want to compare it with your version.

It's nearly identical to my implementation. Instead of
length_haystack = length_haystack - length_needle + 1;
for (i = 0; i < length_haystack; i++)

I used the shorter
length_haystack -= length_needle;
for (i = 0; i <= length_haystack; i++)

OK :-)

The lesson we should learn from this is:
If you take a piece of code from another codebase and copy it into your codebase, you need to follow the other codebase for updates and bug fixes.


ModuleNotFoundError: No module named 'finrl.neo_finrl.env_stock_trading'

from finrl.apps import config
from finrl.neo_finrl.preprocessor.yahoodownloader import YahooDownloader
from finrl.neo_finrl.preprocessor.preprocessors import FeatureEngineer, data_split
from finrl.neo_finrl.env_stock_trading.env_stocktrading import StockTradingEnv
from finrl.drl_agents.stablebaselines3.models import DRLAgent
from finrl.plot import backtest_stats, backtest_plot, get_daily_return, get_baseline
When trying to import these modules. I got the following ModuleNotFound:
ModuleNotFoundError                       Traceback (most recent call last)
~\AppData\Local\Temp/ipykernel_16444/220411286.py in
2 from finrl.neo_finrl.preprocessor.yahoodownloader import YahooDownloader
3 from finrl.neo_finrl.preprocessor.preprocessors import FeatureEngineer, data_split
----> 4 from finrl.neo_finrl.env_stock_trading.env_stocktrading import StockTradingEnv
5 from finrl.drl_agents.stablebaselines3.models import DRLAgent
6 from finrl.plot import backtest_stats, backtest_plot, get_daily_return, get_baseline
ModuleNotFoundError: No module named 'finrl.neo_finrl.env_stock_trading'

Please change neo_finrl to finrl_meta. We have renamed it. Sorry for any inconvenience caused.

Thanks for responding. It's same error for finrl_meta

ModuleNotFoundError                       Traceback (most recent call last)
~\AppData\Local\Temp/ipykernel_15892/1582257264.py in
2 from finrl.neo_finrl.preprocessor.yahoodownloader import YahooDownloader
3 from finrl.neo_finrl.preprocessor.preprocessors import FeatureEngineer, data_split
----> 4 from finrl.finrl_meta.env_stock_trading.env_stocktrading import StockTradingEnv
5 from finrl.drl_agents.stablebaselines3.models import DRLAgent
6 from finrl.plot import backtest_stats, backtest_plot, get_daily_return, get_baseline
ModuleNotFoundError: No module named 'finrl.finrl_meta'

Have you updated to the newest version of FinRL? It seems that the codes are still using neo_finrl instead of finrl_meta.

It works fine after updating.

I am still getting the same issue. I am using 0.31 version
from finrl.apps import config
from finrl.neo_finrl.preprocessor.yahoodownloader import YahooDownloader
from finrl.neo_finrl.preprocessor.preprocessors import FeatureEngineer, data_split
from finrl.finrl_meta.env_stock_trading.env_stocktrading import StockTradingEnv
from finrl.drl_agents.stablebaselines3.models import DRLAgent
from finrl.plot import backtest_stats, backtest_plot, get_daily_return, get_baseline

ModuleNotFoundError                       Traceback (most recent call last)
~\AppData\Local\Temp/ipykernel_4544/2828755724.py in
2 from finrl.neo_finrl.preprocessor.yahoodownloader import YahooDownloader
3 from finrl.neo_finrl.preprocessor.preprocessors import FeatureEngineer, data_split
----> 4 from finrl.finrl_meta.env_stock_trading.env_stocktrading import StockTradingEnv
5 from finrl.drl_agents.stablebaselines3.models import DRLAgent
6 from finrl.plot import backtest_stats, backtest_plot, get_daily_return, get_baseline
ModuleNotFoundError: No module named 'finrl.finrl_meta

Maybe you are following the instructions in the documents? For tutorials in the latest version, please see the notebooks on Github instead of the documents. We are currently updating the documents. The document's code examples may be incompatible with the latest version now. Sorry for any inconvenience caused.

Hello,
Is this a possible moduel renaming error? Thank you for your replies.
ModuleNotFoundError: No module named 'finrl.apps'

Please use the latest codes, we did not update pypi very often.  Yes, some renaming issues.

No module named 'finrl_meta'

No module named 'finrl_meta'

It seems like they renamed finrl_meta to meta. I replaced all instances of finrl_meta with meta and that solved my problem.

Hi pinhaocheng!

Thanks so much for this answer. You just solved a headache I had for a whole day! Blessings to you.

Hi, May I ask what is the recent module name for finrl_meta ? I tried using meta but would get the same error. Thanks


fix: use raw ref for PR branch to avoid confusion bw upstream and fork

same PR as https://github.com/codecov/codecov-cli/pull/237 but for the nodejs uploader
when we upload a report for CI in a PR, we associate the report with the destination repo but we take the branch name from the source repo. so if i make a PR from my fork's main branch to an upstream repo's main branch, we upload the coverage report for the upstream repo's main branch and update the coverage with junk from my un-merged PR
this PR instead will upload refs/pull/#/merge as the branch for PRs. it's slightly less nice for same-repo PRs because in order to populate coverage for your feature branches you'll need CI running on push as well as PR, but avoids invalidating coverage for projects that use a super common fork/merge workflow
docs on the environment variables used here: https://docs.github.com/en/actions/learn-github-actions/variables

it's slightly less nice for same-repo PRs because in order to populate coverage for your feature branches you'll need CI running on push as well as PR

Is this documented anywhere?

@thomasrockhu-codecov y'know, that's a great question. could you point me to how to update docs and maybe suggest a place for it if one comes to mind?

@matt-codecov I think since this is a pretty big paradigm shift, I'd like to pull in @trent-codecov and/or @katia-sentry for their take
for those of you joining us, I don't know the impact this will have on users that don't already run CI on push AND pr events

PR comments should still work for same-repo PRs, i think their coverage will just appear stale in the Codecov website's branch UI because the coverage reports will be filed under refs/pull/#/merge instead of the branch name.
a relevant note from the corresponding codecov-cli PR:

it may be a little while before a fix actually ships. i am away for a couple weeks soon and there are still a few things to work out:

is the same change needed for other CI providers?
is there something we can do on the backend to make this change transparent for same-repo PRs?
if not, what can we do to minimize disruption to that workflow? (doc updates, UI banners, etc)

that said, we're eager to fix this. if it's not solidified before i leave i'll see if any teammates have space to drive it home.

linking https://community.codecov.com/t/codecov-reporting-coverage-from-someone-elses-pr-rather-than-main-repos-main/4411/2

@matt-codecov any update on this?

just got back from PTO. an alternate approach was noted on the corresponding CLI PR https://github.com/codecov/codecov-cli/pull/237 which i'll look into when i get time again

not continuing with this; the issue is fixed in https://github.com/codecov/codecov-cli and we are working towards deprecating this uploader


🌐  Add Dutch translation for docs/nl/docs/features.md

Added Dutch translation to docs/nl/docs/features.md

Thanks for the help! @maxscheijen @svlandeg :sparkles:


Switch to upwind fluxes in gkylzero

In G2, we have a Lua side option to choose between the default penalty fluxes or upwind (or recovery, though that is very experimental). I propose we actually deprecate penalty fluxes
The reason to deprecate penalty fluxes are as follows:

The upwind fluxes are far, far more stable than the penalty fluxes. There are simulations which do not run at any feasible resolution with penalty fluxes that run stably at reasonably coarse resolutions with upwind fluxes.
Eliminates the need for the maxs_by_cell data structure in CPU and GPU implementation, and thus eliminates a reduction operation from the time-stepping. The only reduction which needs to be performed now is the scalar reduction to obtain the stable time-step.

The documented down sides:

Upwind fluxes are more expensive by at least a factor of 2, perhaps slightly more in higher dimensions (this is obviously not a reasonable downside when there are lots of simulations which flat. out. do. not. work with penalty fluxes).
The upwind fluxes kernels are prohibitively large for p>1 in higher dimensionality.
We currently do not understand whether there is an optimal set of nodes to evaluate the upwind direction at for the Serendipity basis for p >= 2. For tensor bases (Serendipity p=1, or Tensor p>1) there is a natural choice of the complete Gauss-Legendre basis and this choice seems to work remarkably well (see above note about how much more stable upwind fluxes are), but the choice of nodes requires experimentation.

Because the upwind flux kernels are prohibitively large for p>1 in 5D and 6D and our current lack of understanding of node location choices for Serendipity p>=2, THIS BRANCH ELIMINATES THE P=2 SERENDIPITY KERNELS.
These kernels can be added back in (take a few hours to generate with Maxima).
This commit breaks the ctest_hyper_dg because the Vlasov-Maxwell kernels are different now with the upwind fluxes.
The new implementation is valgrind clean and works on GPUs! In fact the GPU performance is virtually unaffected by upwind fluxes (while the CPU implementation is a bit slower) such that the GPU performance increase looks better now (was a factor of 25 before for weibel_4d, now it's a factor of 50).

Can you fix the unit test? We can merge the branch into main then. Simply print the answer and copy/paste them into the unit test so it can compare with the new correct results.
As to the larger kernels: we need to move to an hybrid approach in the 5D/6D p=2 case, in which we do the interpolation to quad nodes with mat-vec multiply. This will eliminate huge amount of the code. The performance might not be that much worse. All we would need to do is store the interp matrix and then reuse it in dgemv BLAS kernels. We would need to think on how to do this on the GPUs, though. Perhaps it is not too hard and we can use cuBLAS.
One other option is the following: we generate interpolation kernels that interpolate to quad nodes on faces. Then we can call this from all the places we need: we need them in the LBO upwind kernels, the Vlasov upwind kernels and the GK upwind kernels. I think this will significantly reduce the overall size of the kernels as they will now be in a different function. Then, we can also experiment with the node layouts so they get automatically applied to all the various surface updates we wish to use them in.

A new kernel which interpolates to quad nodes on faces is a good idea. It's common infrastructure to Vlasov (including different flavors of Vlasov like Vlasov-Maxwell and Vlasov-Poisson), GK, and LBOs (GK and Vlasov). Right now the entirety of the slow down between upwind and penalty is within this interpolation, so the question is: can we do better than the massive unrolled interpolation (for certain polyOrders and dimensionalities).
The answer is almost certainly yes. For lower dimensions/polynomial orders the unrolled loop is beneficial. Higher maybe not so much.
It is interesting to me that the GPU seems to have paid less of a penalty for the upwind fluxes than the CPU side, with the performance of the GPU weibel 4d problem being minimally affected (and thus the relative performance difference between CPU and GPU looks even better!)

"THIS BRANCH ELIMINATES THE P=2 SERENDIPITY KERNELS"
do you mean for 5D and 6D?
For lower dim, although we don't understand it, they conserved energy in every test I have tried (both in VM and GK).

It occurs to me how confusing this comment was. I meant only for 5D. I have kept the p=2 lower dimensional kernels.
Since gkylzero and the upwind fluxes work out of the box on GPUs, there are some stress tests I would like to do for highly nonlinear Vlasov-Maxwell simulations with the node placements currently in the code. I've talked with @nmandell and I find it highly probable if we can diagnose why certain node configurations work (and when the node configurations fail) I think we have a paper we could write since I know of no other DG code that does upwinding this way and we preserve the computational advantages of our orthonormal, modal basis.


Formatting in playground should be undoable

You should be allowed to undo a format (Ctrl/Cmd+Shift+F) in playground with Ctrl/Cmd+Z. This works in VS Code. It would be particularly useful when the formatter has a bug as in #720

It's more than undoing I think, because its the save gesture that puts the code in the url. I fight this in VSCode too, end up needing the "save without formatting" gesture.

We don't currently format on Ctrl+S in the playground so I don't think we need that gesture (yet).
VS Code does have one:

We don't currently format on Ctrl+S in the playground so I don't think we need that gesture (yet).

I did explicitly think about not doing that so if there was a formatter bug it could be shared.

Yeah, I don't think we need format-on-save in playground. If we did then we'd need save-without-formatting and/or option to enable/disable it as VS Code does. But I don't see a lot of value. Format-on-save is useful to configure in a repo that enforces formatting, but I don't think we need it in a playground.
So I would just fix this literal issue: have the separate format gesture make an undoable edit and call it good.

estimate: 2


Revert "Sema: Simplify AST representation of key path literals as functions."

Reverts apple/swift#61213

@swift-ci smoke test


withOptions forgets about old link resolvers

Describe the bug
Might be that I'm using the library wrong, but I think the behavior of HtmlRenderer#withOptions changed at some point to not include the link resolvers of the old renderer.
Please provide as much information about where the but is located or what you were using:

[ ] Parser
[x] HtmlRenderer
[ ] Formatter
[ ] FlexmarkHtmlParser
[ ] DocxRenderer
[ ] PdfConverterExtension
[ ] extension(s)

To Reproduce
Create a custom link resolver, and pass it to a HtmlBuilder.Builder instance. Later set some options using withOptions. The link resolver is now gone as the builder with an that takes both an old builder and more options don't set the custom Builder options for the new builder.
Here is a link to the source file where we use Flexmark and are having options.
Here we set the link resolver:
https://github.com/SpongePowered/Ore/blob/master/app/models/project/Page.scala#L199
Here we remove it by calling withOptions:
https://github.com/SpongePowered/Ore/blob/master/app/models/project/Page.scala#L220
Not really possible to show that the link resolver disappeared without using a debugger.

@Katrix, I will double check. It is possible since that part of the code was changed.

@Katrix, this actually never worked because builder state other than extensions and options were never inherited.
Added transferring state between builders and unloading extensions to allow changing configured extension api points based on option changes.
This required a breaking change of moving com.vladsch.flexmark.Extension to com.vladsch.flexmark.util.builder.Extension
Fix for this is available. Repo updated, maven updated but may take a while to show up in maven central.

Fix: IntelliJ Migration contained in [migrate flexmark-java 0_40_x to 0_42_0], to use:

copy to IntelliJ application settings to migrations subdirectory
if you have the project which you want to migrate open, then close it
open the project in IntelliJ Ultimate or Community
update the flexmark-java dependency version to 0.42.0 (or later) and make sure the new library is downloaded/updated in the project.
use menu Refactor > Migrate...
select migrate flexmark-java 0.42.x to 0.50.0
press Run
in the refactoring preview tool window that opens hit Do Refactor


Cannot hide caption button on titlebar

Describe the bug
Following https://github.com/castorix/WinUI3_CustomCaption,
Override x:Key="WindowChromeStyle" to hide caption buttons, so I can add my custom caption with appropriate height and style.
But when updating to wasdk ver 1.4-preview1, I cannot hide the caption button anymore.
Steps to reproduce the bug
Update wasdk to ver 1.4-preview1 with above source
Expected behavior
No response
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.4 Preview 1: 1.4.230628000-preview1
Windows version
No response
Additional context
No response

@Scottj1s @pratikone @rkarman Looks like a 1.3 to 1.4 regression beware; any thoughts on why the captions/etc. are no longer pulling from app resource dictionaries?
WAS 1.3.230502000

WAS 1.4.230628000-preview1

Simpler repro (file, new, WinUI packaged...)
MainWindow.xaml
<?xml version="1.0" encoding="utf-8"?>
<Window
    x:Class="winui_1_3.MainWindow"
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
    xmlns:local="using:winui_1_3"
    xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
    xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
    mc:Ignorable="d">

    <StackPanel Orientation="Horizontal" HorizontalAlignment="Center" VerticalAlignment="Center">
        <Button x:Name="myButton" Click="myButton_Click">Click Me</Button>

        <Grid x:Name="AppTitleBar">
        </Grid>
    </StackPanel>

</Window>

MainWindow.xaml.cs
    public MainWindow()
    {
        this.InitializeComponent();

        ExtendsContentIntoTitleBar = true;
        SetTitleBar(AppTitleBar);
    }

App.xaml
...
    <Application.Resources>
        <ResourceDictionary>
            <ResourceDictionary.MergedDictionaries>
                <XamlControlsResources xmlns="using:Microsoft.UI.Xaml.Controls" />
                <!-- Other merged dictionaries here -->
            </ResourceDictionary.MergedDictionaries>

            <SolidColorBrush x:Key="WindowCaptionButtonBackground" Color="Green" Opacity="0.4"/>
            <SolidColorBrush x:Key="WindowCaptionButtonBackgroundPointerOver" Color="Yellow" Opacity="0.5"/>
            <SolidColorBrush x:Key="CloseButtonBackgroundPointerOver" Color="Magenta" Opacity="0.8"/>

        </ResourceDictionary>
    </Application.Resources>
...

I do remember them mentioning that they would be consolidating windowing related things with AppWindow. I think it was with the intent that things that should logically be in AppWindow/AppWindowTitleBar would use the same behaviour as those.
If this is true then as a complete and utter guess, it would be possible that not everything is hooked up yet. From your screenshots, the 1.4 custom title bar looks a little larger and sharper. The older implementation of the custom title bar didn't work properly with scaling larger than 100%, but AppWindowTitleBar's implementation did.
I guess one way to test this out is to remove the minimise and maximise buttons. Since I believe that Window's custom title bar implementation still kept all 3 buttons, but AppWindowTilteBar's implementation removed them properly.

Yeah, 1.4 Preview 1 is acting more like it is using AppWindowTitleBar's implementation rather than Window's implementation from 1.3.
Using the code:
MainWindow::MainWindow()
{
    InitializeComponent();

    auto win_native = try_as<IWindowNative>();
    HWND native_handle{};
    win_native->get_WindowHandle(&native_handle);

    DWORD ws = static_cast<DWORD>(GetWindowLongPtrW(native_handle, GWL_STYLE));
    DWORD nws = ws & (~WS_MINIMIZEBOX) & (~WS_MAXIMIZEBOX);
    SetWindowLongPtrW(native_handle, GWL_STYLE, nws);
    ExtendsContentIntoTitleBar(true);
}

to initialise the window, 1.3 gives:

where 1.4 gives:

As reference, a Windows API application using AppWindowTitleBar.ExtendsContentIntoTitleBar looks like:

This was from a little sample that was messing around with the Visual Layer.

It's also messed up with Drag and Maximizable when ExtendsContentIntoTitleBar=true. In 1.3, I can use ExtendsContentIntoTitleBar = true, then hide caption button to disable Maximization, but in 1.4, I cannot disable maximization when ExtendsContentIntoTitleBar=true.
Actually, better winUI3 should support api to hide fully the default titlebar (since the custom titlebar is not fully supported yet), then I can easily to add the custom titlebar and its behavior (drag, maximize,...) by windows native api.

You shouldn't need to do anything weird to disable maximise. As an example, using AppWindowTitleBar for 1.3, removing the WS_MAXIMIZEBOX style results in the maximise button being greyed out and unclickable.

There is a bug with 1.4 where it will show it in the greyed out colours, but the button will still be clickable. But when this is fixed, all you should have to do is get the presenter from AppWindow and tell it not to be maximisable.
    MainWindow::MainWindow()
    {
        InitializeComponent();

        auto presenter = AppWindow().Presenter().as<Microsoft::UI::Windowing::OverlappedPresenter>();
        presenter.IsMaximizable(false);

        ExtendsContentIntoTitleBar(true);
    }

I used SetWindowLongPtr in my previous post, but the whole point of that was to explicitly show that AppWindowTitleBar respected the window styles. OverlappedPresenter.IsMaximizable and OverlappedPresenter.IsMinimizable modify the styles and these would be how you would modify this.
For the drag region, since 1.4 could be thought of as effectively forwarding Window.ExtendsContentIntoTitleBar to AppWindowTitleBar.ExtendsContentIntoTitleBar, this means that using the means described in Title bar customization to put interactive content would be how you would set the drag region. However, there are hints in the 1.4 .winmd files that this will change.
For 1.4 Preview 1, SetDragRectangles is defined as:
[deprecated("Use Microsoft.UI.Input.InputNonClientPointerSource.ConfigureRegion instead of SetDragRectangles.  For more info, see MSDN.", deprecate, Microsoft.Foundation.WindowsAppSDKContract, 1.4)] HRESULT SetDragRectangles([in] UINT32 __valueSize, [in] [size_is(__valueSize)] Windows.Graphics.RectInt32* value);

in idl. However, this InputNonClientPointerSource doesn't exist in 1.4 Preview 1. Checking 1.4 Experimental 1 results in:
            [contract(Microsoft.Foundation.WindowsAppSDKContract, 1.4)]
            [exclusiveto(Microsoft.UI.Input.InputNonClientPointerSource)]
            [experimental]
            [uuid(E1675231-4078-5F25-83B2-DA8FA52590FB)]
            interface IInputNonClientPointerSource : IInspectable
            {
                HRESULT ConfigureRegion([in] Microsoft.UI.Input.NonClientRegionKind region, [in] UINT32 __rectsSize, [in] [size_is(__rectsSize)] Windows.Graphics.RectInt32* rects);
                HRESULT ClearAllRegions();
                HRESULT ClearRegion([in] Microsoft.UI.Input.NonClientRegionKind region);
                HRESULT QueryRegion([in] Microsoft.UI.Input.NonClientRegionKind region, [out] UINT32* __resultSize, [out] [retval] [size_is(, *__resultSize)] Windows.Graphics.RectInt32** result);
                [eventadd] HRESULT CaptionTapped([in] Windows.Foundation.TypedEventHandler<Microsoft.UI.Input.InputNonClientPointerSource*, Microsoft.UI.Input.NonClientRegionCaptionTappedEventArgs*>* handler, [out] [retval] EventRegistrationToken* token);
                [eventremove] HRESULT CaptionTapped([in] EventRegistrationToken token);
                [eventadd] HRESULT ConfigurationChanged([in] Windows.Foundation.TypedEventHandler<Microsoft.UI.Input.InputNonClientPointerSource*, Microsoft.UI.Input.NonClientRegionConfigurationChangedEventArgs*>* handler, [out] [retval] EventRegistrationToken* token);
                [eventremove] HRESULT ConfigurationChanged([in] EventRegistrationToken token);
                [eventadd] HRESULT Hover([in] Windows.Foundation.TypedEventHandler<Microsoft.UI.Input.InputNonClientPointerSource*, Microsoft.UI.Input.NonClientRegionHoverEventArgs*>* handler, [out] [retval] EventRegistrationToken* token);
                [eventremove] HRESULT Hover([in] EventRegistrationToken token);
            }

So it looks like this will be the way to configure the title bar drag region in the future.

We have demonstrated the 1.4 regression, now we pray we can make enough noise to get someone's attention. 🙂

The reason I do this because I want the title bar like this:

In ver1.3: I can hide default titlebar by set ExtendsContentIntoTitleBar and collapse resource caption in app resource, then add my titlebar by win api.
In ver1.4: I cannot pull caption resource, so I tried:
            ((OverlappedPresenter)this.AppWindow.Presenter).SetBorderAndTitleBar(true, false);
But it has redundant edge line at the top of titlebar:

Is setting the button colours via AppWindowTitleBar not working?
Since you still haven't really explained exactly what you are trying to do, I have to make the assumption off of your last post that you are just making the title bar constantly dark coloured.

While the rest of the custom title bar hasn't been set here, as you can see, the close button has been set to black. The code for this was a relatively simple:
	void main_window::set_caption_button_colour()
	{
		auto title_bar = m_appwindow.TitleBar();

		if (AppWindowTitleBar::IsCustomizationSupported() && title_bar.ExtendsContentIntoTitleBar())
		{
			auto black_colour = Colors::Black();
			auto white_colour = Colors::White();
			auto dark_grey = Colors::DarkGray();

			title_bar.ButtonBackgroundColor(IReference(black_colour));
			title_bar.ButtonForegroundColor(IReference(white_colour));
			title_bar.ButtonInactiveBackgroundColor(IReference(black_colour));
			title_bar.ButtonInactiveForegroundColor(IReference(dark_grey));
		}
	}

IIRC, this should work even on Windows 10 since this is working with full customisation. The restriction for simple customisation should be down to setting the colours requires using DwmSetWindowAttribute, and the colours are only available starting with Windows 11.
Anyway, the problem you are seeing is an underlying Windows problem. When you have the WS_THICKFRAME style (aka resizable) without the WS_CAPTION style, then Windows paints that line at the top of the window.

@DarranRowe, what Iam trying to do is custom not only title bar but caption button with other size(margin, width, height, image,...), you can see my title bar and caption button will have smaller height compared to default

Right, I can see how using that method to override the title bar would be easier than having to set things up using DWM.
I hope this issue is fixed for you quickly.

With winappsdk 1.4, WinUI 3 custom titlebar uses appwindow titlebar under the hood. As a result, it is more stable, design wise consistent and other thing. But, it also means it is less customizable and follows strict guidelines which appwindow titlebar enforces. One of them is caption buttons cannot be hidden. You can create a feature request for this which would be a separate issue from this.
If you want to go experiemental, try removing WS_MAXIMIZEBOX style and see if it removes maximize button. I remember discussing this with appwindow titlebar owners and they mentioned that some functionality will break due to missing maximize button. But you can try it.
Another approach would be to set caption button colors to match background. However, it cannot be set to transparent by design.
Last one is to roll out own custom titlebar but use https://learn.microsoft.com/en-us/windows/windows-app-sdk/api/winrt/microsoft.ui.input.inputnonclientpointersource to do NC heavy lifting


[NEW]: Elon Musk facing 258 billion $ raketeering lawsuit for Dogecoin

Date
2023-04-03
Description
Investors accused Musk, the world's second-richest person according to Forbes, of deliberately driving up Dogecoin's price more than 36,000% over two years and then letting it crash.
Links
https://www.reuters.com/legal/elon-musk-seeks-end-258-billion-dogecoin-lawsuit-2023-04-01/
Agreement

[X] I irrevocably agree to release my contribution under the CC-BY 3.0 License

Attribution name
@NHOball
Personal link
No response

Just leaving a note that I'm aware of this, but holding off on posting until the motion to dismiss is considered. If the judge rejects the motion, I'll probably post it. Class actions are so tricky — there are so many of them that I'm still trying to establish a good metric on when to include them on the site.

It is factual to say that he was sued. It is factual to say that he is requesting the suit be dismissed. The former is newsworthy; the latter will always happen and thus is not itself newsworthy. Unfortunately, a judge letting the suit proceed is not newsworthy because the amount in the suit is not relevant: the judge could let it go ahead knowing that the likely judgement or settlement is 1% of the asked-for amount.


{AppConfig} Migrating AppConfig to use official data plane SDK

Description

This PR will adopt the official python SDK for App Configuration for all data plane operations.
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

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

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

Hi @recao, could you please help in reviewing this PR?

AppConfig

Hi @bim-msft, this PR is ready for your review.


PROD.OUTLOOK.COM as sender

Hi all
The subscriber receives the email via PROD.OUTLOOK.COM as sender.
If we as a company, do want to be the sender and not PROD.OUTLOOK.COM, is there a setting to change this? Or is each email sent to a subscriber being sent via PROD.OUTLOOK.COM?
Many thanks
Brani

Thanks for your comment, @BraniBKA. This issue has been assigned to the doc author for review.


experiments/config

can you explain ___16gpu, _8gpu, _lt, _otb, otb, 8gpu   in experiments configs  stand for respectively?
Thank you!

Sorry, i don't  read the README carefully.


Improve MMI DriveSerialNumber administrative Performance

Fixes #37
Improve MMI drive SerialNumber Performance query from ~18000ms to ~150ms. This issue stems from a Microsoft.Management.Infrastructure issue where querying via "ASSOCIATORS OF" executes very slowly on some machines. This issue only occurs when executing with administrative privileges. See a related topic  about this strange behavior. I found that restricting the WQL query with WHERE ResultClass = Win32_DiskPartition corrects the issue.
One new test class was added which required the tests project reference two additional projects (DeviceId.Windows.Mmi and DeviceId.Windows.Wmi). If performance tests of this nature are unwanted, I'm happy to remove it. Thanks!

Absolutely brilliant work finding the issue and solving it. Thanks so much for the PR.
I'm a bit unwell at the moment but I'll get this merged and released as soon as I'm feeling better (hopefully in the next couple of days).
Cheers!


Effort required to support for RT600?

Hi,
This is more of a question; I would like to know if you would have an estimate for the amount of work needed to support the RT600 series? I'm not requesting it, just curious to know about your feeling for the effort needed. I think the main difference apart from peripherals is the M33 architecture (ARMv8), but I have just glanced at the data sheet.
I do understand that the additional DSP co-processor is completely different to the core CPU, and would probably better be implemented in it's own crate.
Thanks,
Max
https://www.nxp.com/products/processors-and-microcontrollers/arm-microcontrollers/i-mx-rt-crossover-mcus/i-mx-rt600-crossover-mcu-with-arm-cortex-m33-and-dsp-cores:i.MX-RT600

The rt600, specifically the rt685 has a different core (m33) and peripheral set than the rt1xxx series. The xtensa hifi4 core is an even more interesting task as there’s a forked rust compiler required to even attempt this from espressif and xtensa like its name suggests is a highly configurable core so it’d likely require some patches to support it well.
I think the m33 core would be mostly feasible. Get a ral output and merged with the existing ones were sensible. There’s a lot of unique peripherals for this part though, the powerquad dsp, the many many flexcomms, two dmacs, yeah it’s quite the chip! The evk board has a lot of nice audio interfaces already setup as well and those would be great to tinker with. I’ve gotten audio from the on board codec with C, the nxp samples, and zephyr. In rust this would be quite the achievement.
It would be an amazing experience to program this in rust though! At the moment even Zephyr doesn’t support it that well beyond the m33 core. Supporting this part fully would be a boon and open some doors, the hifi cores are used in many many places that you may not realize. Like intel uses them in many parts as can seen in the SoF project.

Thanks for the great summary! I did not realize that the Xtensa core would require a compiler fork, but I understand it now that you point it out. I also didn’t know that the Espressif chips used similar cores!
As you mention, I had that exact dev board in mind for an audio project. Sounds like quiet an undertaking to get it all working in Rust. I’ll let you know if I dive in, but most likely not.

Found the forked compiler, adding it here for future reference: https://github.com/esp-rs/rust

It still might be worth getting the arm core supported even if the xtensa isn’t initially. They would require separate images anyways.


ci:  Added step to check if tags given in ok to test are present in the tags.js file

Description

Added step to check if tags given in ok to test are present in the tags.js file

Type of change

Chore (housekeeping or task changes that don't impact user perception)

Testing

TBP with tags

How Has This Been Tested?

[ ] Manual
[ ] Cypress

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

Summary by CodeRabbit

Tests

Integrated a new step to validate tags during the integration tests, ensuring only predefined tags are used.

/ok-to-test<EMAIL_ADDRESS>

/ok-to-test<EMAIL_ADDRESS>

/ok-to-test<EMAIL_ADDRESS>

Add all the links to the runs where you tested this.

Also don't see any comment for any failed scenario, please test all the possible scenarios before merging.

TBP pass multiple tags - https://github.com/appsmithorg/appsmith/actions/runs/7419317281/job/20188631044
TBP pass (@tag.All) - https://github.com/appsmithorg/appsmith/actions/runs/7419707023
TBP fail (@tags.ALL) - https://github.com/appsmithorg/appsmith/actions/runs/7419698363/job/20189685508
TBP fail (@tag.all) - https://github.com/appsmithorg/appsmith/actions/runs/7419715559
TBP fail (@tag.ALL) - https://github.com/appsmithorg/appsmith/actions/runs/7419720703

TBP pass multiple tags - https://github.com/appsmithorg/appsmith/actions/runs/7419317281/job/20188631044
TBP pass (@tag.All) - https://github.com/appsmithorg/appsmith/actions/runs/7419707023
TBP fail (@tags.ALL) - https://github.com/appsmithorg/appsmith/actions/runs/7419698363/job/20189685508
TBP fail (@tag.all) - https://github.com/appsmithorg/appsmith/actions/runs/7419715559
TBP fail (@tag.ALL) - https://github.com/appsmithorg/appsmith/actions/runs/7419720703

Added tbp workflows with different scenarions
cc @sarojsarab

So the current changes are for TBP workflow, make changes in integration-tests-command.yml for ok-to-test

So the current changes are for TBP workflow, make changes in integration-tests-command.yml for ok-to-test

TBP I haven't changed, I tested via tbp. Changes are moved to integration-tests-command.yml


fix(mpr): Return the original/raw hanging protocol when fetching and preserving the current active protocol.

Context
Fixes #3665

Changes & Results
Return the original/raw hanging protocol when fetching and preserving the current active protocol.

Testing
See #3665

Checklist
PR

[x] My Pull Request title is descriptive, accurate and follows the
semantic-release format and guidelines.

Code

[x] My code has been well-documented (function documentation, inline comments,
etc.)

Public Documentation Updates

[x] The documentation page has been updated as necessary for any public API
additions or removals.

Tested Environment

[x] OS: Windows 11
[x] Node version: 16.14.0
[x] Browser: Chrome: 117.0.5938.89

I'm not sure how this solves the issue (I couldn't fine other _originalProtocol that is relevant in this context) but it solves the issue, great job

Thanks. I can try to answer that... HangingProtocolService._setProtocol is called to change to mpr. But for the localizer case an error is thrown and caught on line 968. An Object.assign(...) is used to restore the service state when the error occurs which now includes _originalProtocol but it didn't before my change.


[Package Request]: Grocy - ERP beyond your fridge

Package Requested

[X] I would like someone else to build the manifest.
[ ] I would like help so I can submit the manifest.
[X] I have performed a search and couldn't find this package.
[X] I have checked that the installer for this package is not a script file
[ ] I think there is a new version available and I have provided the URL.

Please provide the following information
Publisher: Bernd Bestel
Publisher Url: https://grocy.info/
Package Name: Grocy
Description: ERP beyond your fridge - grocy is a web-based self-hosted groceries & household management solution for your home.
Package Version: 2.3.1
Installer URL: https://github.com/grocy/grocy-desktop/releases
Current Package Identifier (for new versions):

released. close


Clicking on Miami-Dade county in FL does not work

summary: While the data is there, the website doesn't properly redirect to miami when it's clicked
expected result: You can view miami data
actual result:

environment (device, browser, mobile / web): browser
link: http://localhost:3000/state/FL
screenshot (you can copy/paste images directly in):

this now appears to be working!


Work on four more render nodes

Contains
Refactoring, cleanup and documentation of four render nodes:

PrePostCompositeNode
SimpleBlendMaterialsNode
LightShaftsNode
InitialPostProcessingNodes

Longer term PrePostComposite and InitialPostProcessing  will see more refactoring work, mostly to split them into smaller, more specialized nodes.
How to test

Run Terasology
Create a new game or Load an existing one
verify nothing is wrong with the rendered image

Notes
I can't see bloom producing any effect, but this seems to be the case also in develop. As I proceed with the refactoring it will become possible and necessary to revamp the debug mode to show the exact contribution of each effect to the final picture - if any. In this case it will allow to verify if the bloom effect is too subtle to notice given the in-game circumstances or if it is completely absent.

Hooray Jenkins reported success with all tests good!

Hey everybody! I could use a review here! I already have another three refactored nodes waiting in the wings!

Aiiee! So much to review, in the midst of GCI, and Xmas on top :D
Things are quieting down some in NYC now I think, so I might be able to at least do some testing soon. Returning home on Wednesday the 28th.

I can vouch for this testing out on my Win8 tablet. World looks fine, lightshafts still work, etc. Changed graphic settings while in-game no problem.
@emanuele3d if you don't hear from any of @tdgunes @indianajohn or @Avalancs in the near future feel free to just hit the merge button yourself and move on to the next PR :-)

Hi @emanuele3d
Sorry, I don't have access to a PC that is able to run until tomorrow, but I'll be sure to test when I get the chance!

I looked over the code here and was able to understand why all of the changes were being made. I also tested this on both of my machines (and VR mode) and everything seems to work as before.
Thumbs up on this end.

Thank you for the thumbs up @indianajohn. I feel much more confident about a set of changes if at least two pair of eyes have reviewed it. Given @Avalancs seemed to be on the verge of reviewing this I will wait another 24 to give him the chance. If not, I'll merge as you suggest @Cervator.

Hi @emanuele3d !
I have a weird bug, not sure if it is related. No matter if the outlines are on or off, I get thick black lines between blocks in a single direction:

I'll try if I get the same with the develop branch, or if some other settings matter

Tweaking the settings, it disappeared after I disabled "Parallax Mapping"

@Josharias was working on Parallax Mapping but the latest I knew on the matter (from some months ago) was that it wasn't working. So, I don't think this has changed much. Have you checked if the problem also occurs in develop?

Thanks for the review all! (heya @tdgunes I see you there! Thanks and let us know sometime if you got that OSVR headset to work!)
Merged and did one final test, all seems well. That line issue along block edges is oooolld yeah :-)

Yay!

Yay!


Clarify/fix helper.derive docs

Trying to use a derived helper, a couple of things got me hung up from the docs.
I wanted my derived helper to search on a new index. The helper.derive function states The signature of the function is SearchParameters -> SearchParameters. However, there is no mention in the docs of a setIndex method for SearchParameters (though it seems to work, and what I need to use).
Furthermore, the docs refer it firing the results event, when it should be result. PR here: https://github.com/algolia/algoliasearch-helper-js/pull/476

Ultimately advanced features of the helper like derive aren't encouraged as we will have a more straightforward way of debugging if it's done using InstantSearch. For that reason we won't add more documentation.


Colorspace clarification

Hello, I've been using the colormap library in the three.js 3D renderer.
Starting with version 152, three.js applies an automatic gamma encoding on colors.
With this automatic encoding, the same scene using the viridis color ramp renders differently:
Before:

After:

My understanding is that now three.js applies gamma encoding (i.e converts from sRGB to linear) on the colormap colors because it expects them to be in the sRGB color space. Obviously this is not the case.
Does it mean that colors generated by colormap are already in linear space ?

I won't be able to help you here unfortunately. But the library is very simple and straightforward, it simply lerps color values between min and max colors. The way that sequence of colors is treated after (like gamma-correction, remapping or whatsoever) is out of scope of this library. So feel free to check the code and possibly post the solution here if you wish 🙏🏼


handle doc 404s

Received a report that a link to /docs/typescript was 500ing rather than 404ing. This fixes it. An alternative/additional fix would be to set up redirects every time we make a change to the structure of the docs, but I think that would be a bad use of time at least until 1.0
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. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[ ] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[ ] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpx changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

Gah, it doesn't fix it. If you try to hit a non-prerendered page, it will fall back to the serverless function, which attempts to read a non-existent file from the filesystem. Might have to do a gross workaround

There was an issue opened for this recently, which I was having trouble finding. Turns out because it was opened in the Svelte repo. I've moved it here: #4086.

So... we could certainly work around this, but it wouldn't be that pretty, and it would just be masking the real issue which is that the endpoint shouldn't be deployed anyway.
I think the solution is to add export const prerendered to endpoints, and exclude prerendered endpoints from the generated route manifests.

Guess I should have read the comments before approving :grin:
Are there any non-prerendered pages on the SvelteKit site? Maybe you could use adapter-static with the fallback option?
Or you might be able to do something like:
	if (process.env.NODE_ENV === 'production' && !$prerendering) {
		return { status: 404 };
	}

adapter-static is an option, but only because we happen not to have any dynamic pages yet — i'd rather fix the underlying issue. deploying a 'real' app also means we get custom error pages instead of the minimalist Vercel black-on-white status code

have gone with the temporary workaround since prerendered endpoints might be a bit of a rabbit hole (e.g. i think we would want to do https://github.com/sveltejs/kit/issues/4112 first)

gah, still 500ing https://kit-svelte-dev-h9zzmhvx6-svelte.vercel.app/docs/foo

It should be loading /docs.json from prerendered files, but isn't 🤔

closing this in favour of #4093


Doesn't work on 1.16.5 server

Server will not detect newest versions of craftgpt plugin

The latest version, 0.2.9 should have fixes for older MC versions.


Flow auto layout not applied

Describe the bug
In a Hilla react application, there's a view in a subfolder flow, that does not contain a Hilla @layout.tsx. The same application has a Flow layout class annotated with @Layout("/flow").
When running the application both in dev and prod mode, the Flow layout is not applied to the Hilla view.
View config is defined as following:
export const config: ViewConfig = {
    menu: {
        title: "Hello React in Flow Layout",
    },
    title: "Hilla in Flow"
};

If I add to the configuration flowLayout: true, then the page is shown correctly.
The application works as expected with Hilla 24.6.0.beta1.
The issue could be related to the changes from #2915
Expected-behavior
Flow auto layout is applied, when available for a view and there is no Hilla layout.
Reproduction
Link to the platform PR whose validation fails because of this issue: https://github.com/vaadin/platform/pull/7051
Failing module: https://github.com/vaadin/platform/tree/main/vaadin-platform-react-hybrid-test
React View: https://github.com/vaadin/platform/blob/main/vaadin-platform-react-hybrid-test/src/main/frontend/views/flow/hello-hilla.tsx
Flow layout: https://github.com/vaadin/platform/blob/main/vaadin-platform-react-hybrid-test/src/main/java/com/vaadin/platform/react/test/views/FlowLayout.java
System Info
Hilla: 24.6.0.beta2
Flow: 24.6.0.beta3

fixed in #2934


Visualization of mfem example result or execution flow of any example

Hi,
I would like to know if there is any possibility of viewing the solution at every step of  discretization for any sample like example1p. Want to visualize the process of discretization to finite space given the mesh.
I have referred to example22p and example25p, observed that after computation is complete, the solution is passed to glvis server through socket to visualized in form of time series. Instead of that approach, is there a way to visualize the solution or output at every step of solving the equations.

Take a look at examples 9/9p and 10/10p -- they display (i.e. send to GLVis) the solutions in time dependent simulations right after each time step (or every n-th time step) is computed.

Sure, will have a look at them and will test it. Thanks for your response.


Update spring-starter-* packages to a better name

Now we have two packages with name prefix spring-starter. This doesn't align with neither spring-boot-starter- nor spring-cloud-starter-, and is very confusing to developers.
We should find better names for them.

Closing this issue.
Because it's not active for a long time.
If anyone have similar issue, please create issue in new repo: https://github.com/Azure/azure-sdk-for-java/issues


Closes: #1

Updateed validations.py python script.
Fixed the behavior of validate_user function in validations.py.
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot I signed it!


button width problem..(wrap_content)

hello rey,
i created button from your library, but the Width problem is there.
Suppose text is -- "BUTTON"
for that it works fine with proper paddings.
but when the text is "BUTTON DISPLAY"
the button width is exactly the width of the above text.
i tried to change attribute - 'rd_leftPadding' but didn't work out.

To avoid this problem, if i use "weightSum" mechanism, then it works, but wrap_content doesn't work at all... it uglifyies the button

I have same problem!
Is there any solution?


[Grammar Adjustment] Tutorials - MeshMap Snapshots

Current State:

Link to website: MeshMap Snapshot
Currently, the text in the sentences below have some grammar or spelling errors.

Desired State:
3. Use the multi-step connection wizard to authorize Meshery to access your GitHub repositories (you may need to sign into GitHub).
6. You will establish a secret for the Meshery GitHub app and a new workflow to be invoked when a new snapshot is needed.
6.1 Customize the workflow on event trigger to match your needs.

Contributor Guides and Resources

📚 Instructions for contributing to documentation

Meshery documentation site and source

🛠 Meshery Build & Release Strategy
🎨 Wireframes and designs for Layer5 site in Figma (open invite)
🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

Discuss: It could be that the word on in point 6.1 is in the current format because its purpose is to convey a state (i.e inside a code block)

Hey @sandramsc, I am new to the community and would like to work on this simple issue.

@PersonaMate Welcome to the community, I have assigned this to you.

@sandramsc,
Discuss:
It could be that the word on in point 6.1 is in the current format because its purpose is to convey a state (i.e. inside a code block)
..... So should I leave it as it is or make it normal? (For 6.1)

Bump

@vishalvivekm Hi, what's your view on this on this one?

@PersonaMate, any progress on this?


Added Operation Performing Palindrome Problem

removed-exe
Hacktoberfest! 🎊🎈
🎉 Have you read the Contributing Guidelines? 🤔
Yes
Please review @Kushal997-das

Hi there!
I am the Mentor of this project.
Although this repo is not part of Hacktoberfest 2024, we have some great alternatives for you. Welcome to SkillShow, a repository focused on skill enhancement!
Guidelines:

Please adhere to the existing guidelines.
No additional rules, thanks!
Check it out here: SkillShow.

Note: Start by creating an issue. Once it’s assigned to you, feel free to open a pull request (PR). Directly opening a PR will lead to an invalid label.
Looking forward to your contributions!


Extract tenant ID from dedicated label instead of lookup key

Note: PR is based on fix/source-key-generation to avoid conflicts, will rebase onto master once that is merged
Summary
For each query result, the corresponding tenant ID is required for the purpose of mapping to customers in the target system. Currently, that information is extracted from the source key (lookup key for products, discounts etc) - this is untidy, as in theory the lookup key could contain arbitrary values and we shouldn't rely on the tenant ID being available at a specific position therein.
To fix this, I instead extract the tenant ID from a dedicated tenant_id label in the query result. This seems to have been the plan from the start, looking at some of the existing code. A tenant label was supposed to be present in all queries, it just ended up not being used (as the source key was used instead).
I changed the label name to tenant_id instead of tenant primarily for this reason: as far as I can see, a tenant_id label with the correct value is already present in all the queries that are set up in appuio-cloud-reporting, appuio-managed-kubernetes-reporting, and appuio-managed-openshift-reporting. Likely, it was assumed that the label is required (since it originally should have been), and so it was included in each query. If I haven't overlooked anything, this change should therefore not break our existing setup, even though it is technically a breaking change.
Checklist

[x] Categorize the PR by setting a good title and adding one of the labels:
bug, enhancement, documentation, change, breaking, dependency
as they show up in the changelog
[x] Update tests.

For APPUiO Cloud the tenant is the organization. tenant_id is the Project Syn tenant which is not correct on shared clusters.

For APPUiO Cloud the tenant is the organization. tenant_id is the Project Syn tenant which is not correct on shared clusters.

I thought so too, but actually all the APPUiO Cloud queries explicitly rename the appuio_io_organization label to tenant_id. So the content of the label is correct - it has to be, since it's literally what's used in the 3rd position of the product identifier as of right now.

I see. Did not remember correctly then https://github.com/appuio/appuio-cloud-reporting/blob/fd1d44ebd9311658cee9fb82b9e889838071c248/pkg/db/seeds/appuio_cloud_memory.promql#L92
Did you check "appcat:billing" too?

I checked all the queries in the production databases of appuio cloud, appuio managed kubernetes, and appuio managed openshift. The appcat queries are in the appuio cloud reporting DB, right? Or is there another DB I've missed?

Oh I see... oh, that's annoying >.<

Possible solutions:

add a relabeling rule to the query to make the tenant_id label match the organization again
drop this change entirely and accept the weird constraint on product keys
what do you think?

A relabel rule can be applied already before merging the other changes, it won't break anything to have an additional label. So i'd go for that.

update: tenant_id ends up correct in mimir
https://insights.appuio.net/explore?orgId=1&left={"datasource":"c2b8470c-3134-4e70-b6c4-a21b5e7d2d45","queries":[{"refId":"A","datasource":{"type":"prometheus","uid":"c2b8470c-3134-4e70-b6c4-a21b5e7d2d45"},"editorMode":"code","expr":"appcat:billing\n","legendFormat":"__auto","range":true,"instant":true}],"range":{"from":"now-1h","to":"now"}}
The recording rule actually already does the appropriate relabeling to update the tenant_id. But of course we also set tenant_id automatically somewhere for all our timeseries. In mimir, that winds up getting renamed to __tenant_id__ since there already is a conflicting label. Not sure why that doesn't happen when querying via openshift monitoring.

Not sure why that doesn't happen when querying via openshift monitoring.

We add cluster_id, tenant_id and the corresponding display names as externalLabels in Prometheus, so they're automatically added whenever Prometheus sends anything to an external system (Alertmanager, remote write, ...), but they don't show up if you query Prometheus locally

Well, they aren't sent to Mimir, according to our observations.
See also https://vshn.chat/channel/aldebaran?msg=pNdEHN2oZsPxXLTRW (and thread)

After discussion in the Daily, we will not move forward with this change. I've documented the findings here: https://wiki.vshn.net/pages/viewpage.action?pageId=355369468


accordion initial open state

Describe the feature in detail (code, mocks, or screenshots encouraged)
First and foremost, thank you for your effort of making the web a little bit more sane! :D I really enjoy working with bits-ui melt and shadcn-svelte.
I would like to build an accordion with the multiple prop set but I want to start with all items expanded. It seems that currently there is no straight forward way to do this. At least I could not find anything in the docs.
I imagine something like an "open" prop on the Accordion.Item or Accordion.Trigger.
Thanks again!
What type of pull request would this be?
Enhancement
Provide relevant links or additional information.
No response

Hey there, you need to pass all the values of the items you want to be open as the value prop to Accordion.Root
<script>
	import { Accordion } from 'bits-ui'
	const items = ['a','b','c']
</script>

<Accordion.Root bind:value={items}>
	<!-- ... -->
</Accordion.Root>

Hey, thanks for the prompt reply. I came to the same solution yesterday after looking at the types more closely. I think what confused me was that in the docs the type of value is string | undefined.


Compatibility with 32-bit Firmwares

Hi! I'm trying to get WiiProxy to work with my SP Racing F3 running Betaflight 3.2.4 but I'm facing some issues:
getting IMU data works flawlessly but all the other functions like IDENT and ATTITUDE get no response from the board.
This is the code I used to test:
    def get(self, cmdnumber: int):
        command = self._construct_payload(cmdnumber)
        self._write(command)
        print(command)
        buf = self._read(18)
        return buf

When I run:
controller.get(102)
I get the correct output
b'$M<\x00ff' (input)
b'$M>\x12f\xfb\xff\x04\x00\x03\x02\x01\x00\xfe\xff\xff\xff\xf4\xfe\xaa\xff\x9e\xfeJ' (output)

But when I run:
controller.get(108)
I get no response from the board:
b'$M<\x00ll'
Does it produce the same result when run on an original MW board or is it a problem only with the new 32bit systems?
Unfortunately my old MultiWii board is broken so I can't test it with that:(

A few things have changed with 32-bit firmware.
Here's the new list of MSP codes:
https://github.com/betaflight/betaflight/blob/42b2e4077f3b5ad74363557feff632c5a8c2305a/src/main/interface/msp_protocol.h#L244


SelectStatement does not allow EmptyStatement or SingleLineComment before first case

Select

    ;test
    Case 1
EndSelect

result
Line 2, column 5: Expected " ", "Case", "EndSelect", "\t", or "_" but "\n" found.

Fixed with 82dbfc92ef547c4e45184854ee28db9a8da16842


Fixing self._root_path to fall back to os.getcwd()

I was hitting an error like below:
TypeError                                 Traceback (most recent call last)
<ipython-input-2-c4a32dfb6df1> in <module>
----> 1 cfme_data.management_systems

/var/ci/workspace/kkulkarn-9315/integration_tests/cfme/utils/config_data.py in __getattr__(self, key)
     14
     15     def __getattr__(self, key):
---> 16         self.config = self.settings[key.upper()]
     17         return self.config
     18

/var/ci/cfme_venv3/lib64/python3.7/site-packages/dynaconf/utils/functional.py in inner(self, *args)
      8     def inner(self, *args):
      9         if self._wrapped is empty:
---> 10             self._setup()
     11         return func(self._wrapped, *args)
     12

/var/ci/cfme_venv3/lib64/python3.7/site-packages/dynaconf/base.py in _setup(self)
    124         settings_module = os.environ.get(environment_variable)
    125         self._wrapped = Settings(
--> 126             settings_module=settings_module, **self._kwargs
    127         )
    128         self.logger.debug("Lazy Settings _setup ...")

/var/ci/cfme_venv3/lib64/python3.7/site-packages/dynaconf/base.py in __init__(self, settings_module, **kwargs)
    188         self._defaults = kwargs
    189         self.logger.debug("Initializing Dynaconf (%s)", self._store)
--> 190         self.execute_loaders()
    191
    192     def __call__(self, *args, **kwargs):

/var/ci/cfme_venv3/lib64/python3.7/site-packages/dynaconf/base.py in execute_loaders(self, env, silent, key, filename)
    855             self.logger.debug("Dynaconf executing: %s", loader.__name__)
    856             loader.load(self, env, silent=silent, key=key)
--> 857         self.load_includes(env, silent=silent, key=key)
    858         self.logger.debug("Loaded Files: %s", deduplicate(self._loaded_files))
    859

/var/ci/cfme_venv3/lib64/python3.7/site-packages/dynaconf/base.py in load_includes(self, env, silent, key)
    866             from IPython import embed
    867             embed()
--> 868             self.load_file(path=includes, env=env, silent=silent, key=key)
    869             # ensure env vars are the last thing loaded after all includes
    870             last_loader = self.loaders and self.loaders[-1]

/var/ci/cfme_venv3/lib64/python3.7/site-packages/dynaconf/base.py in load_file(self, path, env, silent, key)
    894                     # continue the loop.
    895                     continue
--> 896                 filepath = os.path.join(self._root_path, _filename)
    897                 self.logger.debug("File path is %s", filepath)
    898                 # Handle possible *.globs sorted alphanumeric

/usr/lib64/python3.7/posixpath.py in join(a, *p)
     78     will be discarded.  An empty last part will result in a path that
     79     ends with a separator."""
---> 80     a = os.fspath(a)
     81     sep = _get_sep(a)
     82     path = a

TypeError: expected str, bytes or os.PathLike object, not NoneType

To fix this I had to use os.getcwd() . I think one could use ROOT_PATH_FOR_DYNACONF but I feel os.getcwd() is sensible default.
Please review.
Thanks.

There is a discussion about it going on on #193
Before 2.0.0 os.getcwd was the default root path, then we faced some problems, some users reported they do not wanted the file search to start on the current path but in the scripts path.
On 2.0.0 we changed to use the path where the program is located to build the search tree and do not use . as default.
This is something we need to discuss more to get to a decision.
In meantime I think we can solve this bug by checking for None before calling the function.

Thanks Bruno. so you suggest checking self._root_path, _filename both against None?

@kedark3 jsut now saw that this is only for the load_file method when called directly, so I think your fix is ok!
Just for curiosity, are you calling settings.load_file(...) directly? what is your use case?

@rochacbruno so actually as you may see the traceback in PR description, I was running on Jenkins and my Settings were using LazySettings as follows:
 self.settings = LazySettings(
            ENV_FOR_DYNACONF=env,
            INCLUDES_FOR_DYNACONF='{}/*.yaml'.format(<path>)
        )

so when I would initialize settings, it was failing there. So Adding ROOT_PATH_FOR_DYANCONF solved the problem but I thought it would make sense to fall back on os.getcwd() hence proposed the fix. Thanks for quick merge!!

A possible way to load different files on demand is
from dynaconf import settings

other_settings = settings.from_env('development', SETTINGS_FILE_FOR_DYNACONF='path/to/otherfile.*')

The above will clone the current settings object in a new instance pointing to the new file provided.

@kedark3 nice! thanks for reporting


0.9.2 Build Errors

TARGET = x86_64-linux-musl. Build always fails with the following:

In file included from ./tm.h:30:0,
from ../../src_toolchain/gcc/cp/cvt.c:30:
../../src_toolchain/gcc/config/elfos.h:102:21: warning: invalid suffix on literal; C++11 requires a space between literal and string macro [-Wliteral-suffix]
fprintf ((FILE), "%s"HOST_WIDE_INT_PRINT_UNSIGNED"\n",
^
../../src_toolchain/gcc/config/elfos.h:170:24: warning: invalid suffix on literal; C++11 requires a space between literal and string macro [-Wliteral-suffix]
fprintf ((FILE), ","HOST_WIDE_INT_PRINT_UNSIGNED",%u\n",
^
In file included from ./tm.h:51:0,
from ../../src_toolchain/gcc/cp/cvt.c:30:
../../src_toolchain/gcc/defaults.h:126:24: warning: invalid suffix on literal; C++11 requires a space between literal and string macro [-Wliteral-suffix]
fprintf ((FILE), ","HOST_WIDE_INT_PRINT_UNSIGNED",%u\n",
^
g++ -c  -DIN_GCC_FRONTEND -g -O2 -DIN_GCC  -DCROSS_DIRECTORY_STRUCTURE  -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings   -DHAVE_CONFIG_H -I. -Icp -I../../src_toolchain/gcc -I../../src_toolchain/gcc/cp -I../../src_toolchain/gcc/../include -I../../src_toolchain/gcc/../libcpp/include -I/mnt/2/musl-cross-make/src/musl-cross-make-0.9.2/build-x86_64-linux-musl/obj_toolchain/./gmp -I/mnt/2/musl-cross-make/src/musl-cross-make-0.9.2/build-x86_64-linux-musl/src_toolchain/gmp -I/mnt/2/musl-cross-make/src/musl-cross-make-0.9.2/build-x86_64-linux-musl/obj_toolchain/./mpfr/src -I/mnt/2/musl-cross-make/src/musl-cross-make-0.9.2/build-x86_64-linux-musl/src_toolchain/mpfr/src -I/mnt/2/musl-cross-make/src/musl-cross-make-0.9.2/build-x86_64-linux-musl/src_toolchain/mpc/src  -I../../src_toolchain/gcc/../libdecnumber -I../../src_toolchain/gcc/../libdecnumber/bid -I../libdecnumber -I../../src_toolchain/gcc/../libbacktrace   -o cp/except.o -MT cp/except.o -MMD -MP -MF cp/.deps/except.TPo ../../src_toolchain/gcc/cp/except.c
In file included from ./tm.h:30:0,
from ../../src_toolchain/gcc/cp/except.c:27:
../../src_toolchain/gcc/config/elfos.h:102:21: warning: invalid suffix on literal; C++11 requires a space between literal and string macro [-Wliteral-suffix]
fprintf ((FILE), "%s"HOST_WIDE_INT_PRINT_UNSIGNED"\n",
^
../../src_toolchain/gcc/config/elfos.h:170:24: warning: invalid suffix on literal; C++11 requires a space between literal and string macro [-Wliteral-suffix]
fprintf ((FILE), ","HOST_WIDE_INT_PRINT_UNSIGNED",%u\n",
^
In file included from ./tm.h:51:0,
from ../../src_toolchain/gcc/cp/except.c:27:
../../src_toolchain/gcc/defaults.h:126:24: warning: invalid suffix on literal; C++11 requires a space between literal and string macro [-Wliteral-suffix]
fprintf ((FILE), ","HOST_WIDE_INT_PRINT_UNSIGNED",%u\n",
^
In file included from ../../src_toolchain/gcc/cp/except.c:1023:0:
cfns.gperf: In function ‘const char* libc_name_p(const char_, unsigned int)’:
cfns.gperf:101:1: error: ‘const char_ libc_name_p(const char_, unsigned int)’ redeclared inline with ‘gnu_inline’ attribute
cfns.gperf:26:14: note: ‘const char_ libc_name_p(const char_, unsigned int)’ previously declared here
cfns.gperf: At global scope:
cfns.gperf:26:14: warning: inline function ‘const char_ libc_name_p(const char_, unsigned int)’ used but never defined
make[3]: *_* [Makefile:1065: cp/except.o] Error 1
make[3]: Leaving directory '/mnt/2/musl-cross-make/src/musl-cross-make-0.9.2/build-x86_64-linux-musl/obj_toolchain/gcc'
make[2]: *** [Makefile:5745: all-gcc] Error 2
make[2]: Leaving directory '/mnt/2/musl-cross-make/src/musl-cross-make-0.9.2/build-x86_64-linux-musl/obj_toolchain'
make[1]: *** [Makefile:154: obj_toolchain/gcc/.lc_built] Error 2
make[1]: Leaving directory '/mnt/2/musl-cross-make/src/musl-cross-make-0.9.2/build-x86_64-linux-musl'
make: *** [Makefile:156: all] Error 2
==> ERROR: A failure occurred in build().
Aborting...>

Arch Linux. GCC_CONFIG += --enable-languages=c results in a sucessful build. GCC_CONFIG += --enable-languages=c,c++ does not.

Arch Linux. GCC_CONFIG += --enable-languages=c results in a sucessful build. GCC_CONFIG += --enable-languages=c,c++ does not.

Arch Linux. GCC_CONFIG += --enable-languages=c results in a sucessful build. GCC_CONFIG += --enable-languages=c,c++ does not.

I'm also getting this weird behavior when compiling for TARGET=i486-linux-musl

I just had a config.mak issue.
I simply  did try to build with i686-linux-musl, but I've compiled
i686-linux-musl successfully with the i686-linux-gnu-gcc package from
ubuntu.
You should add a explanation of the config.mak about which crosscompiler is
needed/how to build a crosscompiler for example i486.
richfelker<EMAIL_ADDRESS>schrieb am Sa., 15. Sep. 2018, 09:21:

This issue should have been fixed by commit d08c2e8
https://github.com/richfelker/musl-cross-make/commit/d08c2e8e026990a66a798d52b375cdd4c683f91f.
@TheDevMinerTV https://github.com/TheDevMinerTV: can you elaborate on
what you're seeing to confirm if it's the same? What version of mcm are you
using, and what gcc version are you trying to build?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/richfelker/musl-cross-make/issues/16#issuecomment-421537663,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Acdmj-A84RXxtCWyYb2OocypLC6aoyOOks5ubKpdgaJpZM4J5qJs
.

 #Uploadfilter #Artikel13 #SaveYourInternet" unterschrieben und
wollte dich fragen, ob du auch mitmachst.
Unser Ziel ist es, 6.000.000 Unterschriften zu sammeln und dafür brauchen
wir Unterstützung.
Tobias

WTF change.org?
Who asked you?


Update to Bevy 0.15

Hi, I needed this for a new project, so I went ahead and updated to 0.15 release candidate.

Still need to update README.
Wasn't sure on your preference on this since it includes the Bevy compatibility table and if you prefer waiting to cut a new release. I'm happy to update this now if you like.

Removed Msaa::Sample4 from the examples.
Msaa::Sample4 is now a Component instead of a Resource so it would have to be added to the Camera entity itself. We could use an Observer to add it when the Camera spawns or build it into the library itself by default.

Replaced ManualEventReader (InputState) with EventReader.
ManualEventReader seems to have been removed in 0.15. I'm not familiar with ManualEventReader and what benefits it might have provided the library.

Merged, thank you! I got the README update. Will publish new version shortly


Added IntelliJ plugin integration to README.md

Hi, I did add a link to the IntelliJ plugin.

Merged in 3c4d32c with some cleanup in 305e576. Thanks!


How to do a scroll down (go to the top; go to the centre) on the page?

Hi,
just a simple question: How to do a scroll down to the bottom of the page properly? (this question is also for the go to the top/center of the page). My tests are needed to click on some element, but this element is located of the bottom of the page.
I tried to do like:
public void ScrollDownToTheBottomOfThePage()
{
 Browser.ExecuteJavaScript<??>("window.scrollTo(0, document.body.scrollHeight - 150)");
}

But I don't understand what I should put into ExecuteJavaScript that my action would happen correctly.

Can you use Find.Element and then .Click?
Pretty sure web driver automatically scrolls when you do that...

Yes, you are right, but what if I want to see the actions of clicking in a browser?

It should be visible to you while it happens?

Just for the test purpose, it shouldn't be visible for me, actually :)

Right. So you want the Visible property of the IWebElement returned from Find.Element to be true?

Try this (without the click and changed for C#): http://stackoverflow.com/a/12042268

robdmoore, thank you

Did that work for you? Feel free to post the final C# code so other people that find this know how to do it

Well, I just wanted to observe the scroll down action in Browser while the tests are running. I've tried that piece of code that you sent me, but it didn't work, got some error, I tried it in a bit simple way (without scrolling to the particular element on the page, just scrolled down to the bottom of the page) and it works for me:
        public void ScrollDownToTheBottomOfThePage()
        {
            var js = String.Format("window.scrollTo(0, document.body.scrollHeight - 150)");
            Execute.Script(js);
        }