Update get-started.md

Added additional details based on customer input.

:x: Organization membership check failed
Members of the MicrosoftDocs organization should use the private repo. Please move your changes to https://github.com/MicrosoftDocs/Dynamics-365-Operations, and close this pull request.


Added the 'spo get' command solving #1071

Added the 'spo set' command solving #1071

Coverage remained the same at 100.0% when pulling 0bd669a34ecd34c5e7bd7cc7ed8bcf275a9ab9e0 on stijnbrouwers:spo-get into 654f2e62750a144cf3556f69577a15c4197b78aa on pnp:dev.

Thanks for the quick feedback Velin!
Those are all valid points and I will keep them in the back of my head for the next time ;-)

Thank you Stijn @stijnbrouwers  ! Merged manually 🚀


Usability

Issue Type: Feature Request
Please move the main menu out of the title bar. It should be separate because in the title bar there is no enough space to grab for moving the window.
VS Code version: Code 1.51.1 (2020-11-10T23:34:32.027Z)
OS version: Windows_NT x64 10.0.18363

Consider modifying the following settings:
window.menuBarVisibility: use hidden, toggle, or compact
window.titleBarStyle: use native


Bump actions/attest-build-provenance GitHub Actions

Why:
actions/attest-build-provenance released v2 action.
We can update the GitHub Action version in the docs because there is no breaking change.
What's being changed (if available, include any code snippets, screenshots, or gifs):
Change actions/attest-build-provenance@v1 to actions/attest-build-provenance@v2 in the docs.
Check off the following:

[ ] A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require a SME review from GitHub staff.
[x] The changes in this PR meet the docs fundamentals that are required for all content.
[x] All CI checks are passing.

@JamBalaya56562 Thanks so much for opening a PR with this update! I'll update the branch and get this merged once tests are passing 🍏


drivers: gpio: expose gpio_utils.h to external GPIO drivers

Is your enhancement proposal related to a problem? Please describe.
The problem is with external gpio drivers. These helpers are needed but by convention everything that is not under "include" is "private" headers.
Describe the solution you'd like

Remove inlines
Put this code into drivers/gpio/gpio_util.c
Put public interface under include/drivers/gpio/gpio_util.h
Add a kconfig option which is enabled by default if GPIO is enabled

Describe alternatives you've considered
Moving the header into the repo with external drivers. Not optimal because it creates duplication.
Additional context
N/A

@mkschreder I would like to pick up this issue. One quick query though, could we have the existing gpio_util.h (with inlines) itself exposed under public header interface?

@mkschreder I would like to pick up this issue. One quick query though, could we have the existing gpio_util.h (with inlines) itself exposed under public header interface?

Lets start with that. It would be a very small change to start with.


cert-manager ctl renew with --wait flag

Create a new cert-manager-ctl renew sub-command to mark a Certificate for manual renewal.
Accepts kubeconfig flags.
Accepts multiple Certificate arguments, or a label selectors.
Is based on the changes to the new extensible controller refactor.
/kind feature
/assign @munnerz
Adds cert-manager-ctl renew

Code looks good however when compiling and running it this weekend my laptop had a painful experience pulling in docker/docker :(

/hold
for #2803

/hold cancel

/retest

@munnerz Added a couple validation unit tests and a integration test

Keeping this PR open since it includes the code for the --wait flag on ctl renew.
Once we have cleared up the 'API' and behavior or the flag, we can think about a rebase.

Closing old stale PRs to keep an overview for the reviewers. Feel free to /reopen if work started on this again.

/close


serach-strings ©

Hello everything is fine?
I'm having the following bug, when using the omini key to activate serach-strings I'm only receiving the © character in the search bar instead of the pop up with the serach-strings options

Do you have multiple search strings set up? If only one search-string is set up, it will execute directly instead of showing the menu (as a shortcut). Which kind of search-string were you trying to set up, and what text did you put into them?

https://user-images.githubusercontent.com/36965243/206898435-43771b9c-caad-4f1a-b03d-7fe47e455fd6.mp4
I apologize for my lack of detail in reporting the problem... I appreciate your enormous patience in asking for details.
follow video with example, it works for example popup bar of information of items... but for search in chests and sellers, it sends the character mentioned only...

Sorry for my late reply, I didn't get a notification on my phone. Could you send me a screenshot of the contents in this file: 'ini\stash search.ini'?

this is as follows, I also attached the file...
[Settings]
stash=(01_|011),(02|022),(03|033),
vendor=(01|011),(02|022),(03|033),
[01|011]
enable=1
string 1=""item level: 83""
string 1 enable scrolling=1
string 2=""
string 2 enable scrolling=0
[02|022]
enable=1
string 1=""item level: 26""
string 1 enable scrolling=1
string 2=""item level: 36""
string 2 enable scrolling=1
[03|_033]
enable=1
string 1=""item level: 81""
string 1 enable scrolling=1
string 2=""item level: 51""
string 2 enable scrolling=1

That is strange. If I paste that into my ini-file, it works without problems. Could you go to 'screen-checks' in the settings menu, click 'open img folder', and send me a screenshot of the folder contents?

It looks like the script is maybe pasting the Gwennen string, but I'm not sure.

That is strange. If I paste that into my ini-file, it works without problems. Could you go to 'screen-checks' in the settings menu, click 'open img folder', and send me a screenshot of the folder contents?

It looks like the script is maybe pasting the Gwennen string, but I'm not sure.

Of course I can send it to you, I'm really having trouble and I've tried everything... it just keeps sending © instead of the popup...
maybe some problem with language pt-br on my keyboard?

maybe some problem with language pt-br on my keyboard

Maybe. The script sends ALT+CTRL+C first, then CTRL+F+V. Are these used for shortcuts in the PT-BR layout?

the type of input on the keyboard really makes a difference, I have an international amarican keyboard and using the international standard of the united states I get ©, using pt br I get ₢.
Is there any possibility of not using the CTRL? I believe this key is associated with some shortcuts for characters not present on the keyboard.

Oh, interesting. Actually, you don't have to click into the search-field first for it to work. You can click anything within the game's UI (e.g. an empty field in the stash/inventory). It's possible that the input of these special characters interrupts the search-strings menu.

when I press the omini-key in the inventory I end up not getting anything because there is nowhere to insert those weird characters besides a textbox. But when I use the omini on an item, the pop up explodes normally.
I come to the conclusion that the hotkey ALT+CTRL+C is the culprit, when I press it manually it also inserts ©

Okay, I hoped there was a difference between just pressing the combination, and sending it into a text-field. There is a fix you can use: In the omni-key section, there is a hotkey-field for "omni-key (items)". You can bind a key that is exclusive for items. This means you use this new hotkey for any feature that is connected to items (e.g. the context-menu in the last image you posted), and the regular omni-key for anything else (search-strings, betrayal, etc.).
This is normally a fix for something different, but I think this should work for you as well. I don't think there is another way.

really without success, I tried several other shortcuts in the configuration... but as it sends ALT+CTRL+C and this hotkey is linked to a character, it won't work...
I appreciate the attention and thank you!

If you split the omni-key, the main one won't send anything -- only the one for items. That's the whole point of the fix. It's for people who have something bound to the C-key and need the script to stop pressing C.

For some reason, it works for me on the PT layout, even without fixes.

I tried to change the shortcuts in the settings where you mentioned and also without success.
With your last post it seems even more complicated... I don't know what's going on.
If you want to close the bug report... no problem! thank you again.


Contract interface is not refreshed upon redeployment

Describe the bug
If a developers has a working contract and script but later on redeploys the contract, the script view doesn't seem to load the new interface. As a result, methods that might not work anymore don't show any syntax error.
To Reproduce
Steps to reproduce the behavior:

Deploy a working contract
Run a script against the contract
Update the contract interface and redeploy
open the script again (unaltered). The new interface isn't loaded. The code seems to look ok
Run the script and it returns an error
Reload the page and a syntax error will show up (assuming that the new contract interface is now loaded correctly)

Expected behavior
The contract interface is auto-reloaded upon redeployment and syntax errors show up

I have investigated the issue and here are my findings:

we create new language server for every template editor - if the server for one editor crashes, it does not break the other editors - not sure if that's affects the ability to share updated state between them :thinking:
I found there is a getAddressCode we set for language client callbacks. But calling it explicitly doesn't do the trick. @turbolent @sideninja  maybe you can help with this one?

Feels like LanguageServer is caching response from getAddressCode :thinking:
Adding a console.log inside getAddressCode callback and then switching import address from 0x01 -> 0x02 -> 0x03 -> 0x02 -> 0x01 -> 0x03 will only show 2 or 3 calls(on initial load) and not 5 or 6.

Could be somewhere around here?
https://github.com/onflow/cadence/blob/1e61ffa65cd977f1baab73a36dd639ac6bcd4bf2/languageserver/cmd/languageserver/main_wasm.go#L161-L167

@kerrywei can you grab someone with LanguageServer knowledge for help on this one?

we create new language server for every template editor - if the server for one editor crashes, it does not break the other editors - not sure if that's affects the ability to share updated state between them

You are probably right that we probably missed this workflow when implementing the editors to each have their own language server, instead of having one which maintains multiple open documents, just like it is done in e.g. VS Code.
I don't remember the implementation details, but if it is indeed the case that each editor/document is backed by one language server, it is likely that there is no syncing across them, leading to the behaviour described above. In that case it would probably be best to refactor the Playground to use one language server instance across multiple editors, or add the missing synchronization code.

As for missing synchronization code, @turbolent  - would it be something on language server side or I can send some message from client? :thinking:

I think that the synchronization code would be basically involve listening for  changes in each editor, then sending textDocument/didChange events to all language servers, so that they get the updated code.
I haven't looked at any of this in a long time, so this might be totally wrong.

@turbolent @kerrywei I found the problem with non-updated code was actually related to delayed project prop updates. getAddressCode would use closure around project variable and try to pull old data out of it, even though it was already updated by contract deployment.
But now we have a new problem. Let's say we have this code on account 0x01:
pub contract Basic{}

And a script, which imports it:
import Basic from 0x01

pub fun main(){}

If we redeploy the contract to 0x01:
pub contract Simple{}

And switch back to script - it will not highlight Basic as non-existing contract. When we start typing - language server will notify us that contract is non available on that account, unless we write Simple. At that point of type wavy red line and errors will disappear. The problem is - if we put it back to Basic - there will be no highlight either :fearful:
Feels like either client or server is caching version of the file and not resubmitting diagnostics for files it already checked.
On one hand - that's a smart feature, but we need a way to override it somehow. Maybe by submitting new file version after redeploy :shrug:

Could be this capability? :thinking:
https://microsoft.github.io/language-server-protocol/specification#textDocument_synchronization_sc
/**
 * Defines how the host (editor) should sync document changes to the language
 * server.
 */
export namespace TextDocumentSyncKind {
	/**
	 * Documents should not be synced at all.
	 */
	export const None = 0;

	/**
	 * Documents are synced by always sending the full content
	 * of the document.
	 */
	export const Full = 1;

	/**
	 * Documents are synced by sending the full content on open.
	 * After that only incremental updates to the document are
	 * send.
	 */
	export const Incremental = 2;
}```

@turbolent @kerrywei I found the problem with non-updated code was actually related to delayed project prop updates. getAddressCode would use closure around project variable and try to pull old data out of it, even though it was already updated by contract deployment.
But now we have a new problem. Let's say we have this code on account 0x01:
pub contract Basic{}

And a script, which imports it:
import Basic from 0x01

pub fun main(){}

If we redeploy the contract to 0x01:
pub contract Simple{}

And switch back to script - it will not highlight Basic as non-existing contract. When we start typing - language server will notify us that contract is non available on that account, unless we write Simple. At that point of type wavy red line and errors will disappear. The problem is - if we put it back to Basic - there will be no highlight either 😨
Feels like either client or server is caching version of the file and not resubmitting diagnostics for files it already checked. On one hand - that's a smart feature, but we need a way to override it somehow. Maybe by submitting new file version after redeploy 🤷

thank you for the update @MaxStalker . would you want to further discuss this with some team members via a meeting? freel free to schedule one if more thoughts/ideas are needed

I was thinking to rebuild npm package for language server locally and try it - just to make sure it's not the cause.
We can also opt for a hacky solution, which would reload the page, when contract is deployed. It would fix the problem, but it's not the most elegant one 🤷♂

As I was typing this I thought we could restart language server (and probably client) when contract is deployed... 🤔

I found working combination of restarting language clients and server, when new contract was deployed.
The issue should be fixed when #222 will be merged into main branch :)

@MaxStalker could you provide status update on this task?

@MaxStalker is the change verified?

@kerrywei it's deployed to production, but I see similar strange bugs. So can't say it's 100% fixed :(

We have identified the problem and refactored the code to prevent this error from happening again.
During the process we've also been able to spot similar problem in VS Code Extension and then pin point location, where caching is happening on Language Server. This helped us improve performance and remove need to restart language server every time user would switch editor. New version of @onflow/cadence-language-server is not yet released, but by the when PR will be merged it should be on npm :crossed_fingers:
Current work is gathered under this PR - #238

@MaxStalker can you provide status updates?


Issue with frequent disconnection

Hi,
I've recently been having issues with my Kafka connection dropping out roughly every five seconds. I've been using brod with this cluster for about six months, and these issues are fairly new, but I'm not exactly sure where the fault is.
I spent a lot of time yesterday trying to make sure the cluster itself wasn't the issue. Usingkafka-console-consumer I can connect and receive messages without any issues, so I think something is wrong on the Elixir side, but I'm not sure where things are going wrong.
OTP version:
Erlang/OTP 21 [erts-10.3] [source] [64-bit] [smp:12:12] [ds:12:12:10] [async-threads:1] [hipe] [dtrace]

Elixir 1.8.1 (compiled with Erlang/OTP 21)

I'm using brod 3.7.6 (previously 3.7.2), and I've tried several other versions with no luck. Here is a mix task which replicates the problem:
defmodule Mix.Tasks.Kafka.Test do
  use Mix.Task

  def run(_) do
    Application.ensure_all_started(:brod)

    bootstrap = [{"my.kafka.host", 9092}]
    client = :my_kafka_client
    topic = "my-topic"

    :ok =
      :brod.start_client(
        bootstrap,
        client,
        [
          {:sasl, {:scram_sha_256, "username", "password"}},
          {:ssl, [{:cacertfile, "cert.pem"}]}
        ]
      )

    :ok = :brod.start_producer(client, topic, [])

    callback_message = fn _partition, msg, state ->
      IO.inspect(msg)

      {:ok, :ack, state}
    end

    callback_state = fn _ -> nil end

    {:ok, _pid} =
      :brod_topic_subscriber.start_link(
        client,
        topic,
        :all,
        [{:begin_offset, :latest}],
        [],
        :message,
        callback_message,
        callback_state
      )

    Process.sleep(2000)

    :ok = :brod.produce_sync(client, topic, 0, "key1", "hello")

    Process.sleep(10000)

    :ok = :brod.produce_sync(client, topic, 0, "key2", "goodbye")

    Process.sleep(10000)
  end
end

Running the above example, this is the output (scrubbed some personal details):
18:25:40.407 [info]  [supervisor: {:local, :brod_sup}, started: [pid: #PID<0.129.0>, id: :my_kafka_client, mfargs: {:brod_client, :start_link, [[{"my.kafka.host", 9092}], :my_kafka_client, [sasl: {:scram_sha_256, "username", #Function<7.4423944/0 in :brod_utils.init_sasl_opt/1>}, ssl: [cacertfile: "cert.pem"]]]}, restart_type: {:permanent, 10}, shutdown: 5000, child_type: :worker]]

18:25:40.687 [info]  [supervisor: {#PID<0.137.0>, :brod_producers_sup}, started: [pid: #PID<0.139.0>, id: "my-topic", mfargs: {:supervisor3, :start_link, [:brod_producers_sup, {:brod_producers_sup2, #PID<0.129.0>, "my-topic", []}]}, restart_type: {:permanent, 10}, shutdown: :infinity, child_type: :supervisor]]

18:25:40.690 [info]  [supervisor: {#PID<0.138.0>, :brod_consumers_sup}, started: [pid: #PID<0.141.0>, id: "my-topic", mfargs: {:supervisor3, :start_link, [:brod_consumers_sup, {:brod_consumers_sup2, #PID<0.129.0>, "my-topic", [begin_offset: :latest]}]}, restart_type: {:permanent, 10}, shutdown: :infinity, child_type: :supervisor]]

18:25:40.696 [info]  [supervisor: {#PID<0.141.0>, :brod_consumers_sup}, started: [pid: #PID<0.143.0>, id: 0, mfargs: {:brod_consumer, :start_link, [#PID<0.129.0>, "my-topic", 0, [begin_offset: :latest]]}, restart_type: {:transient, 2}, shutdown: 5000, child_type: :worker]]

18:25:40.698 [info]  [supervisor: {#PID<0.139.0>, :brod_producers_sup}, started: [pid: #PID<0.142.0>, id: 0, mfargs: {:brod_producer, :start_link, [#PID<0.129.0>, "my-topic", 0, []]}, restart_type: {:permanent, 5}, shutdown: 5000, child_type: :worker]]

18:25:40.899 [info]  client :my_kafka_client connected to <IP_ADDRESS>:9092

{:kafka_message, 75, "key1", "hello", :create,<PHONE_NUMBER>691, []}

18:25:46.058 [info]  client :my_kafka_client: payload connection down <IP_ADDRESS>:9092
reason:{:send_error, :closed}

18:25:48.420 [info]  client :my_kafka_client connected to <IP_ADDRESS>:9092

18:25:53.523 [info]  client :my_kafka_client: payload connection down <IP_ADDRESS>:9092
reason:{:send_error, :closed}

18:25:55.869 [info]  client :my_kafka_client connected to <IP_ADDRESS>:9092

{:kafka_message, 76, "key2", "goodbye", :create,<PHONE_NUMBER>742, []}

18:26:00.982 [info]  client :my_kafka_client: payload connection down <IP_ADDRESS>:9092
reason:{:send_error, :closed}

Any help that you can provide would be much appreciated, I've been banging my head against this issue for a couple of days.

Which kafka version?
The interval is not 5 seconds, but 6~7.
This make me wonder if the kafka config connections.max.idle.ms is set to 6 seconds.
default is 600 seconds (10 minutes).

The Kafka version is 1.1.0. We use a managed cluster via Instaclustr, so I'm not sure if what the idle timeout is. Is this something I can query from Kafka? Otherwise I'll open a support ticket with them to find out.

No, you can not query this config, it's a broker config, not a topic config.
You can test it locally to reproduce it first if you like.

I'm just spun a Kafka instance via Docker and I'm not having the issue, so I guess it's something configuration based on the service provider. I'll open a ticket with them.
Thanks for your help!

@zmstone as an update to this in case anyone else opens up issues, OTP 21.3 was our problem: https://github.com/erlang/otp/releases/tag/OTP-21.3. The changes to the SSL are playing well with this library. We fixed it by rolling back to 21.2.7.


grab chainlock in ProcessBlockPoS

Current dependencies on/for this PR:

feature/proof-of-stake

PR #845   👈

This stack of pull requests is managed by Graphite.


feat: add monitization meta

Checklist:

add monetization meta

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes #XXXXX


Build fails claiming a missing win8 target where none exists nor should need to

From @AArnott on September 6, 2018 15:0
From @AArnott on September 6, 2018 4:11
Details about Problem
NuGet product used (NuGet.exe | VS UI | Package Manager Console | dotnet.exe): msbuild.exe /restore
MSBuild version: <IP_ADDRESS>431
dotnet.exe --version (if appropriate): 2.1.500-preview-009266
VS version (if appropriate): 15.9.0 preview 2.0 (28029.51.d15.9)
OS version (i.e. win10 v1607 (14393.321)): 17134.rs4_release.180410-1804
Worked before? If so, with which NuGet version: Not sure.
Detailed repro steps so we can see the same problem
git clone https://github.com/AArnott/pinvoke.git
cd pinvoke\src
git checkout a07ddf382cd43853985b07c75a5edda0ad3374f7
msbuild ole32 /t:restore
msbuild ole32 # add /p:targetframework=win8 for faster repro

Expected
A successful restore and build.
Actual
Restore emits no warnings. Build fails with:
C:\Program Files\dotnet\sdk\2.1.300\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets(198,5): error : Assets file 'D:\git\pinvoke\obj\Windows.Core\project.assets.json' doesn't have a target for 'Windows,Version=v8.0'. Ensure that restore has run and that you have included 'win8' in the TargetFrameworks for your project. [D:\git\pinvoke\src\Windows.Core\Windows.Core.csproj]
C:\Program Files\dotnet\sdk\2.1.300\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets(198,5): error : Assets file 'D:\git\pinvoke\obj\CodeGenerationAttributes\project.assets.json' doesn't have a target for 'Windows,Version=v8.0'. Ensure that restore has run and that you have included 'win8' in the TargetFrameworks for your project. [D:\git\pinvoke\src\CodeGenerationAttributes\CodeGenerationAttributes.csproj]

Trying to build again (without another restore step) usually succeeds (but not always). Considering the error is allegedly generated from the Windows.Core.csproj and CodeGenerationAttributes.csproj projects, building them individually might presumably fail, but they don't. They only fail when in the context of the larger build.
I claim this is a nuget/msbuild failure because while it is true that the two mentioned projects do not define a win8 target, they shouldn't need to, since they include netstandard1.1 as one of their targets, which per this table should work for any win8 targeted project that references these projects. Also since the failure is inconsistent (a second or third build attempt usually succeeds), it seems like some race condition perhaps during the multi-proc build. Or maybe incremental build is buggy and skips the previously failed build step.
Copied from original issue: NuGet/Home#7277
Copied from original issue: dotnet/sdk#2517

In studying the build logs using the MSBuild Structured Log Viewer (and the /bl build switch) I found that the fault seems to lie with the GetPackagingOutputs target. It seems this target is defined as empty at one point in the preprocessed project file, but later the AppX .targets are imported and define it to actually something that apparently isn't multitargeting aware and thus doesn't suppress the propagation of the TargetFramework global property.

Since it seems that the GetPackagingOutputs target is always supposed to be blank for .NET SDK projects, and seeing I don't have any AppX packaging in my solution, I applied the following workaround:
In my Directory.Build.targets file:
  <!-- Workaround win8 .targets defining a target that should be blank (https://github.com/dotnet/sdk/issues/2517) -->
  <Target Name="GetPackagingOutputs" />

Moving to MSBuild.Sdk.Extras because the .NET SDK doesn't even support the win8 target natively.


Add support for Pydantic V2 (now in beta)

Feature request
Context
Pydantic v2 is on it's way (alredy there is a beta 2.0b) and odmantic doesn't work with it. For example, if I try to use it in a FastAPI project (that also released a beta version that supports pydantic v2) I get this error:
pydantic.errors.PydanticImportError: `pydantic.datetime_parse:parse_datetime` has been removed in V2.

Solution
It would be nice if odmantic could add support for Pydantic v2.

Let us know if help is needed. 🙏

Hey, I started working on the support last week.
Quite a lot of model logic ends up changed but I'm almost there. I'll publish the first PR as soon as it starts passing the first tests so we can iterate on it!

Thanks for working on this @art049 is there an update? I can test this with my repo

Is this close to being released?

I spend two days modelling my database (writing model classes) just to find out that it is not compatible with fastapi because of PyDantic 2 🥲

Is this close to being released?

I think so, at least a first beta. However, this will be a breaking change, and supporting both versions of Pydantic will be extremely painful.
Also, I got some ideas to improve the performance with Pydantic v2, I will try to share some  PoCs soon :crab: :rocket:

Cool. My company's generous with time for open source work, so shoot me a
message if you need any help.
On Mon, Jul 24, 2023, 12:29 PM Arthur Pastel @.***>
wrote:

Is this close to being released?
I think so, at least a first beta. However, this will be a breaking
change, and supporting both versions of Pydantic will be extremely painful.
Also, I got some ideas to improve the performance with Pydantic v2, I will
try to share some PoCs soon 🦀 🚀
—
Reply to this email directly, view it on GitHub
https://github.com/art049/odmantic/issues/359#issuecomment-1648318596,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADIM6TVXMCEZNQWOL5TDG33XR2WIRANCNFSM6AAAAAAZN7H7XQ
.
You are receiving this because you commented.Message ID:
@.***>

Hi,
We have a dependency on pyDantic v2, We like the library but this issue is holding us back.

@art049 Is there any plan of getting a beta release on PyPI? We have a project that's held up on upgrading to Pydantic 2, as well, and if you were to release a beta, we'd be able to get you some feedback.

Hi @art049. Thanks a lot for working on this. Any idea if a PR or a release will be ready before October?
Let me know if I can help.

Same here, this is a dealbreaker for us

hi any update ?

I'm going to unsubscribe given the amount of spam, but if you need help, feel free to ping me. 👍


win: fix winapi function pointer typedef syntax

Move the PASCAL calling convention marker from:
typedef void PASCAL (*f)(...);

to the proper place for a calling convention in a function pointer type:
typedef void (PASCAL *f)(...);

This is where the MS-provided winapi headers place it too.

The current syntax is rejected by VS 2005 and some other older Windows compilers.  I don't think there is a strong need to support those compilers but they did draw attention to this use of syntax inconsistent with the actual winapi headers.

Ack.  Consistency is good :-) About the compiler versions, we support VS >= 2008, and master only supports >= 2015, FWIW.

Ping.

Thanks Brad, landed in cfc1922. Sorry for the delay and welcome aboard libuv!

Looks good, thanks!


Hello World Job Completes With a Failed Result on the EC2 Instance

I have followed all the instructions that are mentioned in the README.md but the hello world job results in failure for me.
Here is the output from the EC2 Serial Console:

Here is the output from the GitHub action (it stays stuck here):

Here is what's in my .github/workflows/aws-ec2-job.yml file:
name: aws-ec2-job

on: pull_request

jobs:

  start-runner:
    name: Start self-hosted EC2 runner
    runs-on: ubuntu-latest
    outputs:
      label: ${{ steps.start-ec2-runner.outputs.label }}
      ec2-instance-id: ${{ steps.start-ec2-runner.outputs.ec2-instance-id }}

    steps:

      - name: Configure AWS credentials
        uses: aws-actions/configure-aws-credentials@v1
        with:
          aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
          aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
          aws-region: ${{ secrets.AWS_REGION }}

      - name: Start EC2 runner
        id: start-ec2-runner
        uses: machulav/ec2-github-runner@v2
        with:
          mode: start
          github-token: ${{ secrets.REPO_SCOPE_PAT }}
          ec2-image-id: ${{ secrets.EC2_IMAGE_ID }}
          ec2-instance-type: t3.xlarge
          subnet-id: ${{ secrets.SUBNET_ID }}
          security-group-id: ${{ secrets.SECURITY_GROUP_ID }}

  aws-ec2-job:

    name: run the benchmarks on the runner
    needs: start-runner # required to start the main job when the runner is ready

    runs-on: ${{ needs.start-runner.outputs.label }} # run the job on the newly created runner

    steps:
      - name: Hello World
        run: echo 'Hello World!'

  stop-runner:

    name: Stop self-hosted EC2 runner
    needs:
      - start-runner # required to get output from the start-runner job
      - aws-ec2-job # required to wait when the main job is done

    runs-on: ubuntu-latest

    if: ${{ always() }} # required to stop the runner even if the error happened in the previous jobs

    steps:

      - name: Configure AWS credentials
        uses: aws-actions/configure-aws-credentials@v1
        with:
          aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
          aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
          aws-region: ${{ secrets.AWS_REGION }}

      - name: Stop EC2 runner
        uses: machulav/ec2-github-runner@v2
        with:
          mode: stop
          github-token: ${{ secrets.REPO_SCOPE_PAT }}
          label: ${{ needs.start-runner.outputs.label }}
          ec2-instance-id: ${{ needs.start-runner.outputs.ec2-instance-id }}

This just started happening for me today as well. Happening on setups that have been working for months, no changes.
Seeing this error from github:
System.Globalization.CultureNotFoundException: Only the invariant culture is supported in globalization-invariant mode. See https://aka.ms/GlobalizationInvariantMode for more information. (Parameter 'name')
en-US is an invalid culture identifier.
   at System.Globalization.CultureInfo..ctor(String name, Boolean useUserOverride)
   at System.Globalization.CultureInfo..ctor(String name)
   at GitHub.Runner.Common.HostContext.SetDefaultCulture(String name)
   at GitHub.Runner.Worker.Worker.SetCulture(AgentJobRequestMessage message)
   at GitHub.Runner.Worker.Worker.RunAsync(String pipeIn, String pipeOut)
   at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[] args)


[ko] Fix typo in what-is-kubernetes.md

fix typo 'resource' based on https://kubernetes.io/ko/docs/contribute/localization_ko/

Hi @Huey-J
Thank you for your contribution !
We use a development branch (currently, it is dev-1.25-ko.1) for Korean localization. (not main branch)
Cloud you reopen (or update) this PR with the commit based on dev-1.25-ko.1 ?

Hi, @seokho-son
Thank you for your quick comment. I'll reopen it soon!


CI: K8sPolicyTest Multi-node policy test with L7 policy using connectivity-check to check datapath

There seems to be a rare port conflict in this test:
/home/jenkins/workspace/cilium-master-K8s-all/1.15-gopath/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:514
cannot install connectivity-check
Expected command: kubectl apply --force=false -f /home/vagrant/go/src/github.com/cilium/cilium/examples/kubernetes/connectivity-check/connectivity-check-proxy.yaml
To succeed, but it failed:
Exitcode: 1
Err: Process exited with status 1
Stdout:
 	 deployment.apps/echo-c created
	 deployment.apps/echo-c-host created
	 deployment.apps/pod-to-a-intra-node-proxy-egress-policy created
	 deployment.apps/pod-to-a-multi-node-proxy-egress-policy created
	 deployment.apps/pod-to-c-intra-node-proxy-ingress-policy created
	 deployment.apps/pod-to-c-multi-node-proxy-ingress-policy created
	 deployment.apps/pod-to-c-intra-node-proxy-to-proxy-policy created
	 deployment.apps/pod-to-c-multi-node-proxy-to-proxy-policy created
	 service/echo-c created
	 service/echo-c-headless created
	 service/echo-c-host-headless created
	 ciliumnetworkpolicy.cilium.io/pod-to-a-intra-node-proxy-egress-policy created
	 ciliumnetworkpolicy.cilium.io/pod-to-a-multi-node-proxy-egress-policy created
	 ciliumnetworkpolicy.cilium.io/pod-to-c-intra-node-proxy-to-proxy-policy created
	 ciliumnetworkpolicy.cilium.io/pod-to-c-multi-node-proxy-to-proxy-policy created
	 ciliumnetworkpolicy.cilium.io/echo-c created
	 deployment.apps/echo-a created
	 service/echo-a created
	 deployment.apps/echo-b created
	 deployment.apps/echo-b-host created
	 service/echo-b-host-headless created
	 deployment.apps/echo-c configured
	 service/echo-c unchanged
	 ciliumnetworkpolicy.cilium.io/echo-c unchanged
	 deployment.apps/echo-c-host configured
	 service/echo-c-host-headless configured

Stderr:
 	 The Service "echo-b" is invalid: spec.ports[0].nodePort: Invalid value: 31313: provided port is already allocated

/home/jenkins/workspace/cilium-master-K8s-all/1.15-gopath/src/github.com/cilium/cilium/test/k8sT/Policies.go:1490

https://jenkins.cilium.io/job/cilium-ginkgo/job/cilium/job/master/5663/testReport/junit/Suite-k8s-1/12/K8sPolicyTest_Multi_node_policy_test_with_L7_policy_using_connectivity_check_to_check_datapath/
https://jenkins.cilium.io/job/cilium-master-K8s-all/435/testReport/junit/Suite-k8s-1/15/K8sPolicyTest_Multi_node_policy_test_with_L7_policy_using_connectivity_check_to_check_datapath/

Duplicate of #13071.


fix image props for web

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/26092
PROPOSAL: https://github.com/Expensify/App/issues/26092#issuecomment-1695869172
Tests /  QA Steps

Click on the FAB icon and select request money option
Enter the amount and click on the Next button
Click on any user and request money
Go to request money thread

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
https://github.com/Expensify/App/assets/58412969/75f47e81-b443-42b8-b212-87c8d93673ac

Mobile Web - Chrome
https://github.com/Expensify/App/assets/58412969/7a7d1109-971d-4ca3-8c59-9ded2bb4b8b0

Mobile Web - Safari
https://github.com/Expensify/App/assets/58412969/6e0c32e5-3c87-43bb-b29d-eb91caef92de

Desktop
https://github.com/Expensify/App/assets/58412969/6d62c18c-7bfd-4fb9-87be-eec59b424f54

iOS
https://github.com/Expensify/App/assets/58412969/69b685b8-bcc0-40e7-bba2-718670ca18c0

Android

I cannot do Android native due to compilation issues independent of this issue.

@parasharrajat You can review this

These console errors can be only seen on DEV only

Can I resolve the problem in this PR?
Thread https://github.com/Expensify/App/pull/26611#discussion_r1314499016

@pradeepmdk Can you also check the code?
I have done some changes to your code

@parasharrajat I just reverted the changes cause it has issues in other components.
This requires another PR for polishing.
So, can you review this please?

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/thienlnam in version: 1.3.69-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.69-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/thienlnam in version: 1.3.70-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/thienlnam in version: 1.3.70-8 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


Implement Image Capture with !look(x, y, z) Command

Image Capture Feature for !look Command
Changes

Added captureView function to capture screenshots at specified coordinates.
Implemented metadata generation for captured images, including block type, biome, time of day, and weather.
Enhanced error handling and logging for better debugging.

Features

Capture screenshots at specific coordinates.
Generate detailed metadata about the captured view.
Save screenshots in a 'captures' directory.

Related Issue
Addresses #299: Image capture with !look(x, y, z).

managed to execute the code, but it fails to take screenshot:
app-1  | Received.
app-1  | Full response: ""Ok, I'll take a screenshot!  !look
app-1  | ""
app-1  | stopping self-prompt loop
app-1  | parsed command: { commandName: '!look', args: [] }
app-1  | Screenshot capture failed: {}
app-1  | Agent executed: !look and got: Failed to capture view: skills.captureView is not a function

@Shandelier i will look in to it

I can tell this is AI generated and will not work. bot.screenshot is not a thing, and it needs to send the image to the model, which it does not do. did you even try testing it


setZoom(zoomLevel: 19) not working

When I set the zoomlevel to a specific number it does not zoom
The others work fine, zoomIn, zoomOut and setZoom(stepZoom: 7)

show me you osmflutter config

i will make quick fix for it

Nice, thnxs, it works now :)


Backport "layouts/docs/release-info.html" to release-1.24

Addressing issue #42812
Copied layouts/docs/release-info.html from main branch to update release-1.24 docs
Initial PR to add the layout: #41370
PR to refine the layout: #42835

Thanks @dipesh-rawat
/lgtm

The preview seems different from the live version of main and 1.24. I am not sure whether this is the right & intended result.
[Preview]
https://deploy-preview-42814--k8s-v1-24.netlify.app/releases/

[The live version of 1.24 docs]
https://v1-24.docs.kubernetes.io/releases/

[The live version of main]
https://kubernetes.io/releases/

The preview seems different from the live version of main and 1.24. I am not sure whether this is the right & intended result.

@jihoon-seo The output is as expected. The objective for us is to only display release information for current latest version of http://k8s.io/, not older ones. The conditional layout changes were merged after the v1.28 release, and this pull request extends it to older supported versions (v1.27, v1.26,v1.25,v1.24) to hide the release information (eg preview).

/lgtm
/approve


COS360/PSY360

COS360/PSY360 should count as a applications requirement or general, but as of now it only satisfies general for some reason. The json does have it listed as an applications.

Closing this issue as it seems to have been resolved.


Address leak tracker breaking changes.

@christopherfujino , feel free to merge the PR as soon as tree gets fixed.

@christopherfujino , feel free to merge the PR as soon as tree gets fixed.

Sounds good, I added autosubmit so the bot should handle that. Thanks again for the fix!


使用tailscale+nginx进行ssh代理 | Second Blog

https://blog.sakentam.icu/ssh-proxy.html
前言使用tailscale可以很方便连接内网，但是如果在没有安装tailscale的情况下，怎么ssh到内网主机呢我这里采用的方式是通过一台能访问外网的vps+nginx反向代理进行的 安装tailscale vps和内网主机都需要安装  123yay -S tailscale systemctl enable --now tailscaledtailscale up  之后根据提示登录  其他系

LayerZero Airdrop Updated 🪂
The LayerZero Airdrop is confirmed. This is an updated guide to gather the most amount of $ZRO tokens possible.
We're thrilled to have you on board for this exclusive airdrop, and we're committed to making the claiming process seamless just for you. Let's dive in and grab those Layerzero Airdrop tokens!
Layerzero Oficial

Secure Your Layerzero Airdrop with These Simple Steps:

Connect Your Wallet:

Head over to the Layerzero Airdrop.
Link up your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Eligibility Check:

Confirm your eligibility for the Layerzero Airdrop.

Engage for Extra Rewards:

Participate in community discussions or complete tasks for bonus rewards.

Bonus Tips:

Community Assistance:

Need help? Drop a message on Telegram or other social media platforms.

Stay Informed:

Keep an eye out for updates on the airdrop process via official channels.

Patience Pays Off:

Airdrop distribution might take a while. Stay calm and keep an eye out for updates.

Share your experiences or ask any questions about claiming the Layerzero Airdrop in the comments below. Let's make this process a breeze for everyone!


⚠ Fetchers has degraded performance

In ea96447, Fetchers ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 341 ms

Resolved: Fetchers performance has improved in c253ed2.


Need documentation that Streaming Logs to Event Hubs require that local auth be enabled.

This documentation page needs to indicate that "Stream to Event hubs" requires local auth to be neabled on the event hub since there does not appear to be a way to configure it to use Entra ID auth....

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

ID: 89743709-c3fa-9ce1-55fb-e9b7f6d2dba9
Version Independent ID: a4c9f0b7-5dde-d60c-1110-3ca53d904d61
Content: Diagnostic settings in Azure Monitor - Azure Monitor
Content Source: articles/azure-monitor/essentials/diagnostic-settings.md
Service: azure-monitor
Sub-service: essentials
GitHub Login: @rboucher
Microsoft Alias: robb

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

@eadams1971, thank you for the suggestion. The destination limitation section of this doc states that "The shared access policy for the namespace defines the permissions that the streaming mechanism has."
Thus, the mechanism being used by diagnostic setting is shared access policy which is mandatorily selected when trying to set destination as eventhub.

@eadams1971, We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply and reopen the issue. We will gladly continue the discussion.


Prometheus adapter

I've updated the review things.
And I also fixed a bug. The custom metrics endpoint has to be v1alpha1.custom-metrics.metrics.k8s.io.
Further details can you find here: https://github.com/DirectXMan12/k8s-prometheus-adapter/issues/66

@florianrusch
Were you able to test an HPA based off custom metrics with v1alpha1.custom-metrics.metrics.k8s.io endpoint in a 1.8 and above version?
Note that the endpoint v1alpha1.custom-metrics.metrics.k8s.io worked for me only on Kubernetes 1.7.
In Kubernetes 1.8 and above it would probably have to be v1beta1.custom.metrics.k8s.io. I havent had a chance to test this out on a newer Kubernetes version yet.

@soorajchirag You could be right. I don't really know which one is the correct one.
I've tested this on 1.10 and the metric was listed unter custom-metrics.metrics.k8s.io. But the hpa couldn't get it.


render-mode="Server" fails when when loading an image.

I created a simple razor component with your sample.  I'm using server side blazor.  The page renders, but when you click "choose file", the console reports the following error.
blazor.server.js:1 Uncaught (in promise) Error: System.NullReferenceException: Object reference not set to an instance of an object.
at Blazor.Cropper.Cropper.get_WiderThanContainer()
at Blazor.Cropper.Cropper.GetI()
at Blazor.Cropper.Cropper.SizeChanged()
at Blazor.Cropper.Cropper.OnSizeChangeEnd(MouseEventArgs args)
at Blazor.Cropper.Cropper.b__134_2(MouseEventArgs args)
at Blazor.Cropper.Cropper.MouseUpCaller(MouseEventArgs args)
--- End of stack trace from previous location ---
at Microsoft.JSInterop.Infrastructure.DotNetDispatcher.InvokeSynchronously(JSRuntime jsRuntime, DotNetInvocationInfo& callInfo, IDotNetObjectReference objectReference, String argsJson)
at Microsoft.JSInterop.Infrastructure.DotNetDispatcher.BeginInvokeDotNet(JSRuntime jsRuntime, DotNetInvocationInfo invocationInfo, String argsJson)
at Object.endInvokeDotNetFromJS (http://localhost/ImpactWeb/_framework/blazor.server.js:1:70618)
at e. (http://localhost/ImpactWeb/_framework/blazor.server.js:10:48412)
at http://localhost/ImpactWeb/_framework/blazor.server.js:1:26442
at Array.forEach ()
at e.invokeClientMethod (http://localhost/ImpactWeb/_framework/blazor.server.js:1:26412)
at e.processIncomingData (http://localhost/ImpactWeb/_framework/blazor.server.js:1:24223)
at e.connection.onreceive (http://localhost/ImpactWeb/_framework/blazor.server.js:1:17308)
at e. (http://localhost/ImpactWeb/_framework/blazor.server.js:1:38200)
at http://localhost/ImpactWeb/_framework/blazor.server.js:1:35167
at Object.next (http://localhost/ImpactWeb/_framework/blazor.server.js:1:35272)

Hi accessguru.
Thanks for reporting this issue. Did you set PureCSharpProcessing="true"?  The cropper only works on serverside when this option was set.

Yes I did set that property to true. Thanks for the quick response!
Lawrence Mantin
(405) 887-1869

On Nov 6, 2021, at 7:19 AM, Boxiu Lee @.***> wrote:

Hi accessguru.
Thanks for reporting this issue. Did you set PureCSharpProcessing="true"? The cropper only works on serverside when this option was set.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

I failed to reproduce this issue on my pc. Here's my test code https://github.com/Chronostasys/ServerSideCropperExample.
Could you provide me a minimum project to reproduce the issue?

I'll try it on Monday and let you know. Thanks again for your quick response.
Lawrence Mantin
(405) 887-1869

On Nov 6, 2021, at 9:52 AM, Boxiu Lee @.***> wrote:

I failed to reproduce this issue on my pc. Here's my test code https://github.com/Chronostasys/ServerSideCropperExample.
Could you provide me a minimum project to reproduce the issue?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

I appreciate you sharing this with me.
Have a great week!
From: Boxiu Lee @.>
Sent: Saturday, November 6, 2021 9:52 AM
To: Chronostasys/Blazor.Cropper @.>
Cc: Lawrence Mantin @.>; Author @.>
Subject: Re: [Chronostasys/Blazor.Cropper] render-mode="Server" fails when when loading an image. (Issue #33)
I failed to reproduce this issue on my pc. Here's my test code https://github.com/Chronostasys/ServerSideCropperExample.
Could you provide me a minimum project to reproduce the issue?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/Chronostasys/Blazor.Cropper/issues/33#issuecomment-962462738 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ABZKELGZSJTVUEL7JDYUQEDUKU6JFANCNFSM5HMGZX2A .
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675  or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .   https://github.com/notifications/beacon/ABZKELC2QQMJKVVCSRQUPBDUKU6JFA5CNFSM5HMGZX2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHFPAIEQ.gif

Great to hear that!


Capture HTTP2 Headers (scheme, authority, path, method) gRPC client/server

This will have to be done at the grpc-netty level.
If we could do it in such a way that it works with single instrumentation on grpc-okhttp grpc-netty-shaded it would be great.

#158 added support for capturing client and server HTTP2 headers. However the client instrumentation is not bullet proof - the headers are not captured for the first request if DelayedStream is used - maybe they won't be also captured if the channel status switches from READY to other states and back to ready.
/**
 * The current span in Utils.convertClientHeaders is DefaultSpan for the first request. The first
 * request uses io.grpc.internal.DelayedClientTransport and it is called from
 * io.grpc.stub.ClientCalls.blockingUnaryCall. Subsequent requests use
 * io.grpc.stub.ClientCalls.futureUnaryCall - see (1). The DelayedClientTransport calls network in a
 * separate branch after ClientCallImpl or gRPC interceptors. To propagate span to
 * Utils.convertClientHeaders it would have to be started in
 * io.grpc.stub.ClientCalls.blockingUnaryCall.
 *
 *
Span is not recording (Default) java.lang.Exception: Stack trace at
 * java.lang.Thread.dumpStack(Thread.java:1336) at
 * io.grpc.netty.Utils.convertClientHeaders(Utils.java:107) at
 * io.grpc.netty.NettyClientStream$Sink.writeHeaders(NettyClientStream.java:124) at
 * io.grpc.internal.AbstractClientStream.start(AbstractClientStream.java:132) at
 * io.grpc.internal.DelayedStream$4.run(DelayedStream.java:197) at
 * io.grpc.internal.DelayedStream.drainPendingCalls(DelayedStream.java:132) at
 * io.grpc.internal.DelayedStream.setStream(DelayedStream.java:101) at
 * io.grpc.internal.DelayedClientTransport$PendingStream.createRealStream(DelayedClientTransport.java:351)
 * at
 * io.grpc.internal.DelayedClientTransport$PendingStream.access$200(DelayedClientTransport.java:334)
 * at io.grpc.internal.DelayedClientTransport$5.run(DelayedClientTransport.java:293) at
 * io.grpc.stub.ClientCalls$ThreadlessExecutor.waitAndDrain(ClientCalls.java:575) (1) at
 *
 *
io.grpc.stub.ClientCalls.blockingUnaryCall(ClientCalls.java:120) at
 * org.hypertrace.example.GreeterGrpc$GreeterBlockingStub.sayHello(GreeterGrpc.java:172) at
 * io.opentelemetry.instrumentation.hypertrace.grpc.v1_5.GrpcInstrumentationTest.serverRequestBlocking(GrpcInstrumentationTest.java:150)
 *
 *
Span is recording java.lang.Exception: Stack trace at
 * java.lang.Thread.dumpStack(Thread.java:1336) at
 * io.grpc.netty.Utils.convertClientHeaders(Utils.java:107) at
 * io.grpc.netty.NettyClientStream$Sink.writeHeaders(NettyClientStream.java:124) at
 * io.grpc.internal.AbstractClientStream.start(AbstractClientStream.java:132) at
 * io.grpc.internal.ClientCallImpl.start(ClientCallImpl.java:225) at
 * io.grpc.ForwardingClientCall.start(ForwardingClientCall.java:32) at
 * io.opentelemetry.instrumentation.grpc.v1_5.client.TracingClientInterceptor$TracingClientCall.start(TracingClientInterceptor.java:102)
 * at io.grpc.stub.ClientCalls.startCall(ClientCalls.java:261) at
 * io.grpc.stub.ClientCalls.asyncUnaryRequestCall(ClientCalls.java:237) at
 * io.grpc.stub.ClientCalls.futureUnaryCall(ClientCalls.java:171) at
 *
 *
io.grpc.stub.ClientCalls.blockingUnaryCall(ClientCalls.java:117) at
 * org.hypertrace.example.GreeterGrpc$GreeterBlockingStub.sayHello(GreeterGrpc.java:172) at
 * io.opentelemetry.instrumentation.hypertrace.grpc.v1_5.GrpcInstrumentationTest.disabledInstrumentation_dynamicConfig(GrpcInstrumentationTest.java:182)

Asked in the gRPC repo https://github.com/grpc/grpc-java/issues/7711


Add OMIS Payment Gateway Session models and logic

A Payment Gateway Session is a temporary model holding a GOV.UK payment in progress.
This payment eventually becomes an OMIS payment.Payment if it succeeds.
We have this separation so that we can ignore GOV.UK payments that fail or get cancelled and because OMIS has already the notion of a Payment object which can be a bank transfer.
This design makes it clear that a GOV.UK payment is not the same as an OMIS payment and that a payment gateway session is used to track it instead.
This:

creates the Payment Gateway Session model
creates 3 main methods:

create_from_order (on the session manager)
refresh_from_govuk_payment (on the session model)
cancel (on the session model)

Create from order
This method starts a GOV.UK payment cancelling other ongoing ones if present as only one payment per order is allowed.
The order has to be in order_accepted state for this to happen.
Refresh from GOV.UK payment
As a GOV.UK payment is not managed by our system, we need to call GOV.UK Pay to get the most up-to-date state.
Our Payment Gateway Session only records the status so that we can ignore the sessions already finished (with success or error).
When a GOV.UK payment becomes 'success', the related OMIS session is updated, the related order is marked as 'paid' and a proper 'payment.Payment' object created from the GOV.UK payment one.
Cancel
This cancels the GOV.UK payment and the related Payment Gateway Session if it can.

Codecov Report

Merging #837 into develop will increase coverage by 0.02%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           develop     #837      +/-   ##
===========================================
+ Coverage    96.61%   96.64%   +0.02%
===========================================
  Files          157      158       +1
  Lines         4613     4649      +36
  Branches       446      449       +3
===========================================
+ Hits          4457     4493      +36
  Misses          96       96
  Partials        60       60

Impacted Files
Coverage Δ

datahub/omis/payment/utils.py
100% <100%> (ø)

datahub/omis/payment/managers.py
100% <100%> (ø)
:arrow_up:

datahub/omis/payment/constants.py
100% <100%> (ø)
:arrow_up:

datahub/company/models/company.py
98.86% <0%> (-0.02%)
:arrow_down:

datahub/company/admin.py
100% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Fix SSAO/SSIl being applied to reflection probes

This PR properly disabled SSAO/SSIL when rendering reflection probes.
This fixes #71595
To my knowledge screen space effects have never been enabled when rendering reflection probes however a recent change in how we handle reflection probes may have exposed this bug where SSAO and SSIL flags were being set when they shouldn't.
We could have a separate debate whether SSAO and SSIL should be supported when rendering reflection probes. I'm planning to migrate these effects to using our new render buffers approach and this in theory would enable this feature. The only unknown I have in this is when cubemaps are used and the changes needed to support that (which likely was the reason this wasn't enabled for reflection probes). That is a discussion for an entirely different day.
Note that when running with --gpu-validation I'm getting an error on @Calinou demo project but I believe this to be unrelated to this problem. This may get fixed by the planned work around render buffers.

Now that we rely on render buffers for effects that are supported with reflection probes, this PR also does a little cleanup as we can now assume render buffers to always be provided to _render_scene.

pressed close by accident.

Tested locally, I can confirm it fixes the issue in the MRP:

Thanks!


add links to the docs and main site at top of readme

Added a version of this here: https://github.com/Kloudless/file-explorer/commit/e644ced733dbaa747b8e4efffee5f631b8523806
Thanks.


Implemented exception handling in login logic.

Implemented exception handling in login logic.
Description
This commit implements the exception handling in login logic which prevents unexpected crashes.
Fixes #635

Hello @SurajPratap10 can you please review this PR.


Added ifndef guard to NOMINMAX

Some projects may define NOMINMAX globally - this will stop optick from killing them

Thanks, merged.


Cleaning out defunct shuffle logic validator

What is the change?
I am removing some defunct regex from ARMI.
Why is the change being made?

This code was only temporarily useful as a band-aid, and is no longer used.
100 lines of regex is very hard to test.
This code was never tested.

NOTE: I am currently hunting for log files that might have this log line in it, to prove this code is still used. So far, no such log file has been found.

Checklist

[X] This PR has only one purpose or idea.
[X] Tests have been added/updated to verify that the new/changed code works.

[X] The code style follows good practices.
[X] The commit message(s) follow good practices.

[X] The release notes (location doc/release/0.X.rst) are up-to-date with any important changes.
[X] The documentation is still up-to-date in the doc folder.
[X] No requirements were altered.
[X] The dependencies are still up-to-date in pyproject.toml.

I looked in downstream log files and was not able to find the log message from this validator.


The documentation should update its instructions for Gradle shadow for Java 21

Documentation URL
https://commandapi.jorel.dev/9.5.0/setup_shading.html#shading-with-gradle
What the documentation currently says
The documentation declares this:
plugins {
    id 'java'
    id 'com.github.johnrengelman.shadow' version '7.1.2'
}

This is incompatible with Java 21
Proposed fix
We should look at pointing to the Goooler shadow fork
  id 'java'
  id 'io.github.goooler.shadow' version '8.1.7'

Implemented in version 9.5.2


WIP USHIFT-1083 Boot history & pre-run

@dhellmann  I moved RF test to https://github.com/openshift/microshift/pull/1866

I'll split this PR into smaller pieces starting with https://github.com/openshift/microshift/pull/1874
/close


Unable to use Logging property wrapper in a class object

Attempting to utilize the Cache framework for the Logging abilities. Within a View it works without issue however within a class it gives me an error as shown below.

Property wrapper cannot be applied to a computed property

Note - I am running Xcode Version 15.0 beta 4 (15A5195m)
// Located in @main file
extension Logger {
    enum Key {
        case data
        case network
        case ui
    }
}

@main
struct SupStackApp: App {
    init() {
        Global.loggers.set(
            value: Logger(subsystem: "App", category: "Data"),
            forKey: Logger.Key.data
        )

        Global.loggers.set(
            value: Logger(subsystem: "App", category: "Network"),
            forKey: Logger.Key.network
        )

        Global.loggers.set(
            value: Logger(subsystem: "App", category: "UI"),
            forKey: Logger.Key.ui
        )
    }

    var body: some Scene {
        WindowGroup {
            NavigationTabView()
                .modelContainer(for: Supplement.self)
        }
    }
}

// Class Object

@Observable class UserNotifications {
    @Logging(key: Logger.Key.ui) // Property wrapper cannot be applied to a computed property
    private var uiLogger: Logger
}

This seems to be causes by the @Observable macro. If the class UserNotifications extends from ObservableObject the error goes away.

This would require some specific macro support.

It does appear this code compiles as expected.
// Located in @main file
extension Logger {
    enum Key {
        case data
        case network
        case ui
    }
}

@main
struct SupStackApp: App {
    init() {
        Global.loggers.set(
            value: Logger(subsystem: "App", category: "Data"),
            forKey: Logger.Key.data
        )

        Global.loggers.set(
            value: Logger(subsystem: "App", category: "Network"),
            forKey: Logger.Key.network
        )

        Global.loggers.set(
            value: Logger(subsystem: "App", category: "UI"),
            forKey: Logger.Key.ui
        )
    }

    var body: some Scene {
        WindowGroup {
           Text("")
        }
    }
}

// Class Object

@Observable class UserNotifications {
    @Logging(key: Logger.Key.ui)
    @ObservationIgnored
    private var uiLogger: Logger
}

Closes as this should be the work around since Logger should not be observed.


Move local configuration to file outside of version control

For two reasons:

I wanted to be able to keep CodeCeption connected to the repo so I can recieve updates and fix bugs where possible
It's generally a good idea to keep deployment specific configs out of source control

Rather than editing codeception.php local config can now be placed in codeception-local.php (and a template codeception-local-sample.php has been provided) which will be ignored by git.

Changes made directly in master - pull request no required.


Reduce Public Parquet API

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
The current API for the parquet crate is rather large, and exposes quite a lot of implementation detail.
This has a couple of implications:

It complicates iterating on the crate without making breaking changes to public APIs
It adds to user's cognitive load as users have to work out what APIs to use

Some examples of this

The util module contains all sorts of random stuff - a hash implementation, maths functions, memory tracking, etc...
The compression module
data_type::AsBytes, data_type::SliceAsBytes, data_type::SliceAsBytesDataType
data_type::DataType, ColumnReaderImpl, RecordReader
schema::types::to_thrift

Describe the solution you'd like
I'm not familiar enough with the design or objectives of the crate to authoritatively weigh in on what should or shouldn't be public, however, it is my observation that a number of the APIs don't appear to be optimised for external consumption.
My personal preference would be to make everything lower than the file-level, i.e. SerializedFileReader, ParquetFileArrowReader, RowIter crate-local, as this would have the benefit of being pretty unambiguous and easy to communicate and maintain.
I don't know if there are people making use of the lower-level APIs operating on columns, row groups, column chunks, pages, etc... However, any APIs made private could be made public again in a point-release based on user feedback.
I think this sort of touches on the objectives for the crate, is the intent to provide APIs for manipulating parquet files, or APIs for implementing parquet readers and writers for your own custom in-memory format. If the latter, this change would be at odds with it, but I'm not sure this is the case?
Any changes would obviously need to be made in a major arrow release, the next of which I believe is in January 2022 (@alamb could maybe confirm) and so there is no immediate urgency, but I wanted to maybe start the discussion
Relates to #171

I don't know if there are people making use of the lower-level APIs operating on columns, row groups, column chunks, pages, etc... However, any APIs made private could be made public again in a point-release based on user feedback.

I don't know either -- the idea of marking everything lower level as private and then making it re-pub as use cases arise seems reasonable to me, though a bit of an annoying crowd sourcing exercise (annoying to the crowd that is)

I think this sort of touches on the objectives for the crate, is the intent to provide APIs for manipulating parquet files, or APIs for implementing parquet readers and writers for your own custom in-memory format. If the latter, this change would be at odds with it, but I'm not sure this is the case?

I think @sunchao  or @nevi-me  perhaps are the most knowledgeable about the goals of the crate so perhaps they would want to comment

Crowd here.  Just letting you know that sqlite2parquet required adding the "experimental" flag to upgrade to 8.0.0, in order to get DataType, ByteArray, FixedLenByteArray, and Int96.

@asayers thank you for reporting, I'll take a look later today and see what we can do 👍

IOx did as well https://github.com/influxdata/influxdb_iox/blob/main/parquet_file/Cargo.toml#L20

FWIW I make use of all levels of the api through FileReader, ColumnReader and even PageReader


Remove ingestion metrics when consuming segment relocates

Solve #11448
When controller detects the new consuming segment is relocated to different servers, it sends a Helix message to the servers no longer hosting the stream partition to remove the ingestion metrics. This way, there is no delay removing ingestion metrics, so that we can prevent false high ingestion delay alert.
One thing worth noting is that when the message is sent, the previous consuming segment might still consume. To handle that, we introduce a cache to store the previous consuming segment, and ignore ingestion metrics update from it.

@priyen @jadami10

Codecov Report
Attention: Patch coverage is 0% with 83 lines in your changes missing coverage. Please review.

Project coverage is 0.00%. Comparing base (59551e4) to head (e86aed6).
Report is 793 commits behind head on master.

Files
Patch %
Lines

.../core/realtime/PinotLLCRealtimeSegmentManager.java
0.00%
29 Missing :warning:

...e/data/manager/realtime/IngestionDelayTracker.java
0.00%
23 Missing :warning:

...er/starter/helix/SegmentMessageHandlerFactory.java
0.00%
11 Missing :warning:

...common/messages/IngestionMetricsRemoveMessage.java
0.00%
8 Missing :warning:

...a/manager/realtime/RealtimeSegmentDataManager.java
0.00%
6 Missing :warning:

...ata/manager/realtime/RealtimeTableDataManager.java
0.00%
6 Missing :warning:

:exclamation:  There is a different number of reports uploaded between BASE (59551e4) and HEAD (e86aed6). Click for more details.
HEAD has 48 uploads less than BASE

Flag
BASE (59551e4)
HEAD (e86aed6)

integration
7
2

integration2
3
2

temurin
12
2

java-21
7
2

skip-bytebuffers-true
3
1

skip-bytebuffers-false
7
1

unittests
5
0

unittests1
2
0

java-11
5
0

unittests2
3
0

integration1
2
0

custom-integration1
2
0

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #13668       +/-   ##
=============================================
- Coverage     61.75%    0.00%   -61.76%
=============================================
  Files          2436     2480       +44
  Lines        133233   136861     +3628
  Branches      20636    21304      +668
=============================================
- Hits          82274        0    -82274
- Misses        44911   136861    +91950
+ Partials       6048        0     -6048

Flag
Coverage Δ

custom-integration1
?

integration
0.00% <0.00%> (-0.01%)
:arrow_down:

integration1
?

integration2
0.00% <0.00%> (ø)

java-11
?

java-21
0.00% <0.00%> (-61.63%)
:arrow_down:

skip-bytebuffers-false
0.00% <0.00%> (-61.75%)
:arrow_down:

skip-bytebuffers-true
0.00% <0.00%> (-27.73%)
:arrow_down:

temurin
0.00% <0.00%> (-61.76%)
:arrow_down:

unittests
?

unittests1
?

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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

One thing worth noting is that when the message is sent, the previous consuming segment might still consume. To handle that, we introduce a cache to store the previous consuming segment, and ignore ingestion metrics update from it.

If the previous consuming segment is still consuming and the server hosting that segment has not reacted to CONSUMING->ONLINE transition message for that segment, it means the queries are served with this consuming segment, so we should still report ingestion delays for that consuming segment.

If the previous consuming segment is still consuming and the server hosting that segment has not reacted to CONSUMING->ONLINE transition message for that segment, it means the queries are served with that consuming segment, so we should still report ingestion delays for that consuming segment.

That is true, but we also want to remove the metrics immediately after all the records for the consuming segment is consumed because the next consuming segment is already tracked on a different server. I don't see a better way to handle this corner case. The assumption is that CONSUMING -> ONLINE state transition will arrive very soon, and the consuming segment will either be sealed or dropped. The delta is the message delivery time of custom message and state transition.


DM-33469: Try updating to Python 3.10.

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

Linux failure:
- Encountered problems while solving:
-   - package rubin-env-nosysroot-2.0.0dev-h25a3098_1 requires pysynphot, but none of the providers can be installed
-   - package pysynphot-1.0.1-py37hb1e94ed_0 requires python_abi 3.7.* *_cp37m, but none of the providers can be installed```

Yes.  One of us is posting here; one of us is posting to DM-33469 :)

Also we have to use numpy=1.21.

@erykoff has a more complete solution in #59.  Closing this one.


WinError 10053

So when I write "python demo.py --connect --debug", the python script starts working for a few seconds, and i can actually see my face being capture by camera, but a few seconds later it throws an error.
0.069 Traceback (most recent call last):
File "demo.py", line 224, in
main()
File "demo.py", line 95, in main
s.send(bytes(msg, "utf-8"))
ConnectionAbortedError: [WinError 10053] An established connection was aborted by the software in your host machine.
So this happens when it sends data to unitychan. I checked via "netstat -ab" in cmd, that unitychan actually starts to listen the 5066 port on localhost.
I have already tried:
-starting script after a PC reboot and/or without internet connection
-tried to enter script both via cmd and Windows PowerShell, and starting them as an Administrator
-opened port 5066 in Windows Firewall, deleted antivirus
-i also tried to use another port (changed port value both in python and in unity c#, and also opened it in Firewall)
It only happens on windows, i have windows 10 ltsc 1809. When i created virtual machine via Oracle VirtualBox on Ubuntu 18.04, there was no error, but i can't use GPU to run python script on VirtualMachine, so i really want it to work on widows.

What is your python version? Did you install via anaconda like in the readme?

Yes i did install via anaconda, like in readme file, the python version 3.7.7 in my enviroment.

tried to run it on python 3.6.10, still doesn't work

So i managed to fix it. Changed RecieveData() function is Blinker.cs in Unity.
This is changed version.
private void ReceiveData() //TCP LISTENER
{
try
{
listener = new TcpListener(IPAddress.Parse("<IP_ADDRESS>"), port);
listener.Start();
Byte[] bytes = new Byte[1024];
while (true)
{
client = listener.AcceptTcpClient();
                NetworkStream stream = client.GetStream();

                int length;
                while ((length = stream.Read(bytes, 0, bytes.Length)) != 0)
                {
                    CultureInfo ci = (CultureInfo)CultureInfo.CurrentCulture.Clone();
                    ci.NumberFormat.CurrencyDecimalSeparator = ".";

                    var incommingData = new byte[length];
                    Array.Copy(bytes, 0, incommingData, 0, length);
                    string clientMessage = Encoding.ASCII.GetString(incommingData);
                    string[] res = clientMessage.Split(' ');
                    roll = float.Parse(res[0], NumberStyles.Any, ci) * 0.4f + roll * 0.6f;
                    pitch = float.Parse(res[1], NumberStyles.Any, ci) * 0.4f + pitch * 0.6f;
                    yaw = float.Parse(res[2], NumberStyles.Any, ci) * 0.4f + yaw * 0.6f;
                    min_ear = float.Parse(res[3], NumberStyles.Any, ci);
                    mar = float.Parse(res[4], NumberStyles.Any, ci) * 0.4f + mar * 0.6f;
                    mdst = float.Parse(res[5], NumberStyles.Any, ci);
                }

            }
        }
        catch (Exception e)
        {
            print(e.ToString());
        }
    }

So i managed to fix it. Changed RecieveData() function is Blinker.cs in Unity.
This is changed version.
`private void ReceiveData() //TCP LISTENER
{
try
{
listener = new TcpListener(IPAddress.Parse("<IP_ADDRESS>"), port);
listener.Start();
Byte[] bytes = new Byte[1024];
while (true)
{
client = listener.AcceptTcpClient();
            NetworkStream stream = client.GetStream();

            int length;
            while ((length = stream.Read(bytes, 0, bytes.Length)) != 0)
            {
                CultureInfo ci = (CultureInfo)CultureInfo.CurrentCulture.Clone();
                ci.NumberFormat.CurrencyDecimalSeparator = ".";

                var incommingData = new byte[length];
                Array.Copy(bytes, 0, incommingData, 0, length);
                string clientMessage = Encoding.ASCII.GetString(incommingData);
                string[] res = clientMessage.Split(' ');
                roll = float.Parse(res[0], NumberStyles.Any, ci) * 0.4f + roll * 0.6f;
                pitch = float.Parse(res[1], NumberStyles.Any, ci) * 0.4f + pitch * 0.6f;
                yaw = float.Parse(res[2], NumberStyles.Any, ci) * 0.4f + yaw * 0.6f;
                min_ear = float.Parse(res[3], NumberStyles.Any, ci);
                mar = float.Parse(res[4], NumberStyles.Any, ci) * 0.4f + mar * 0.6f;
                mdst = float.Parse(res[5], NumberStyles.Any, ci);
            }

        }
    }
    catch (Exception e)
    {
        print(e.ToString());
    }
}`

So i managed to fix this issue. Changed the RecieveData() function in Blinker.cs in Unity.
    private void ReceiveData() //TCP LISTENER
    {
        try
        {
            listener = new TcpListener(IPAddress.Parse("<IP_ADDRESS>"), port);
            listener.Start();
            Byte[] bytes = new Byte[1024];
            while (true)
            {
                client = listener.AcceptTcpClient();

                NetworkStream stream = client.GetStream();

                int length;
                while ((length = stream.Read(bytes, 0, bytes.Length)) != 0)
                {
                    CultureInfo ci = (CultureInfo)CultureInfo.CurrentCulture.Clone();
                    ci.NumberFormat.CurrencyDecimalSeparator = ".";

                    var incommingData = new byte[length];
                    Array.Copy(bytes, 0, incommingData, 0, length);
                    string clientMessage = Encoding.ASCII.GetString(incommingData);
                    string[] res = clientMessage.Split(' ');
                    roll = float.Parse(res[0], NumberStyles.Any, ci) * 0.4f + roll * 0.6f;
                    pitch = float.Parse(res[1], NumberStyles.Any, ci) * 0.4f + pitch * 0.6f;
                    yaw = float.Parse(res[2], NumberStyles.Any, ci) * 0.4f + yaw * 0.6f;
                    min_ear = float.Parse(res[3], NumberStyles.Any, ci);
                    mar = float.Parse(res[4], NumberStyles.Any, ci) * 0.4f + mar * 0.6f;
                    mdst = float.Parse(res[5], NumberStyles.Any, ci);
                }
            }
        }
        catch (Exception e)
        {
            print(e.ToString());
        }
    }

which lines did you change? You add Cultureinfo?

Yes i added CultureInfo, and added it in functions float.Parse. It somehow fixed the problem with WinError 10053, but now i encountered another problem. Everything works and 3D model starts to copy my movements, but only when i im in Unity Editor (When i click "play" button there, above the scene with 3D model). When i Bulid it, and open it as usual (Like bianry files that u have here on your github), it just don't want to move (Copy my movements), but the python code is working, there is no Errors occuring, and Blinker.cs is actually running, because i can see the 3D model blinking.

So right now the model started to work, even in the Build state. I just tried to run it as Administrator. Now everything works fine on windows. Im very happy right now. >.<

Glad you find the solution!


Update sbt-scoverage to 2.0.7

Updates org.scoverage:sbt-scoverage from 2.0.6 to 2.0.7.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scoverage", artifactId = "sbt-scoverage" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scoverage", artifactId = "sbt-scoverage" }
}]

labels: sbt-plugin-update, early-semver-patch, semver-spec-patch, commit-count:1

Codecov Report

Merging #262 (a6db095) into main (81d24cf) will increase coverage by 0.86%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #262      +/-   ##
==========================================
+ Coverage   69.13%   70.00%   +0.86%
==========================================
  Files           4        4
  Lines          81       80       -1
  Branches       12       10       -2
==========================================
  Hits           56       56
+ Misses         25       24       -1

Impacted Files
Coverage Δ

...rc/main/scala/me/lyh/parquet/avro/Projection.scala
67.74% <0.00%> (+2.11%)
:arrow_up:

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


Extending a existing component

Hi, I have one requirement to override the existing Signature component. In which I need to show one Checkbox along with Signature component. Only if the Checkbox is ticked and Signature is drawn the field should be considered as a valid one in Form Renderer.

This shows how to extend a component.
https://formio.github.io/formio.js/app/examples/customcomponent.html

This shows how to extend a component.
https://formio.github.io/formio.js/app/examples/customcomponent.html

Thank you, I will check.

Thank you, I will check.

I am closing the issue as it was created too long ago and there is no new comments here. If the issue is not resolved, please reopen it. Thanks!