Improve Transaction success rate

Describe the bug
When the network is under high load, I frequently see instances where transactions fail to confirm, with a message like 'Transaction may fail to confirm in 30.01 seconds' .
Additional context
The default settings in the web3 js library aren't necessarily the best for production usage.
Here's some context: https://twitter.com/GenesysGo/status/1502726745149030405
I think if we add retries and a longer timeout window, we can achieve a lower transaction failure rate.
This would entail  modifications to //core/base/src/signer.ts to be more inline with
https://solanacookbook.com/guides/retrying-transactions.html#an-in-depth-look-at-sendtransaction

It's up to apps or wallets to handle retries with application-specific logic. This isn't in scope for wallet-adapter, but you could build a library that does this.


⚠ Bofrost.es has degraded performance

In 1980161, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1811 ms

Resolved: Bofrost.es performance has improved in 872ffc1 after 9 minutes.


rtop crashed for some external def

Reason # external a: int = "";
Fatal error: exception Invalid_argument("index out of bounds")

i.e. when you type external a: int = "";

rtop simply doesn't support external unfortunately, afaik. Maybe that'll change one day...
I'll keep this one open

Reason # external a: int = "";
Line 1, characters 12-15:
Error: External identifiers must be functions


[1.12.2] Pouches can delete items.

Minecraft: 1.12.2
Forge: <IP_ADDRESS>47
Mods: 5
jei_1.12.2-<IP_ADDRESS>1
mysticallib-1.12.2-1.7.0
mysticalworld-1.12.2-1.8.2
Patchouli-1.0-20
Roots-1.12.2-3.0.26
=====
GIF:
https://cdn.discordapp.com/attachments/377171551155650560/697297524796424394/rootspouchbug.gif
This occurs wit any pouch.
Open it with either a key press or right-click and put in for example... 32 Sand Blocks, close it... and reopen it and store some more sand blocks on the same stack & close it. Now... when you reopen it... you'll noticed that your stacksize of Sand Blocks is still 32.
This also happens with any herb materials pouch in the other slots.

Hm. This ... means something isn't firing somewhere.

Oh, but the fix is in the unreleased 3.1 branch. So yeah, this should be fixed when 3.1 comes out.

Can confirm in 3.0.25 as well... Looks like shift clicking protects the stack, so that should be a usable workaround until the fix comes out.

Yeah, I'm going to aim to get a 3.1 release out soon even if I don't have the modifier overhaul/staff library change

@DoomRater is it resolved in 3.1 though?

Everything looks good in the 3.1 alpha6 build I have here.


DirtyDiff listener leak?

Found this in the console after typing for while...
/Users/jrieken/Code/vscode/out/vs/base/common/event.js:113 [5gh] potential listener LEAK detected, having 398 listeners already. MOST frequent listener (299):
LeakageMonitor.check @ /Users/jrieken/Code/vscode/out/vs/base/common/event.js:113
/Users/jrieken/Code/vscode/out/vs/base/common/event.js:114     at TextModel.onDidChangeContent (file:///Users/jrieken/Code/vscode/out/vs/editor/common/model/textModel.js:230:39)
    at file:///Users/jrieken/Code/vscode/out/vs/workbench/parts/scm/electron-browser/dirtydiffDecorator.js:871:71
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)

Setting a breakpoint shows a fishy amount of listeners...

verified via review


About tdesign-vue-next RoadMap

Currently design-vue-next is in Alpha stage
The community and official documents do not have a detailed RoadMap and its iteration plan. I would like to consult whether the current Alpha version is available for production and the subsequent iteration plan.
TKS

https://github.com/Tencent/tdesign-vue-next/projects/1


Cannot build on any branch, ios

Hi!
I am using flutter 3.7.7 and was trying out both the demo github and this pubspec, but both do not seem to compile on ios.
Sometimes I get a Error (Xcode): Undefined symbol: _OBJC_CLASS_$_BROTHERSDK, but other times it seems like the plugin does not install properly on both the master and ios without b branch.
Is there something I am missing, such as xcode version?

Hi @kyeshmz !
Thanks for reaching out about this. In the case of iOS you'll need to follow our setup steps outlined here (https://www.youtube.com/watch?v=AcFnd-6hSew) because there are currently a few setup steps that we have not figured out yet how to automate.
Also for iOS bear in mind that you'll need to use a physical device during development because the native libraries we currently use don't compile for the emulator.
Thanks again for reaching out, I hope this helps but don't hesitate to reach out if there is anything else I can help with,

I am running everything on a real device, is the libBROTHERSDK.a linking still needed even if we are submitting to the app store?

It seems to not work on xcode 14.3 / flutter 3.7.10 / with xcode build failing with ```Error (Xcode): Undefined symbol: OBJC_CLASS$_BROTHERSDK

Hi @kyeshmz ,
Sorry to hear you are still facing build issues. That Undefined symbol normally means the target membership for BROTHERSDK.h and libBROTHERSDK.a for those components (https://youtu.be/AcFnd-6hSew?t=117)
One thing I have seen happened after doing the setup if Xcode is closed this gets reset on the next build. So usually leaving Xcode open while building after the configuration is completed ensures that membership is not reset (the membership checks remain toggled).
That said, I run Xcode 13.3.1 / Flutter 3.7.5 so can't rule out it might be a specific issue on the newer version of Xcode yet either.
Could I trouble you to try configuring the Xcode side of things once more, leaving Xcode running and building from it to see if we can rule out the configuration reset.
With regards to libBROTHERSDK.a, if you are submitting to the store you should not have them as we have seen other submissions get rejected because of it so I recommend using the ios-no-type-b branch. Unless you are targeting Brother's TypeB printers you won't need that anyways.

So it seems like I can run it once every 10 times in xcode, but not in any other debugging environment like vscode.

Apologies for the late response @kyeshmz. Glad to hear you got it working.
I am told that the new typeB libraries from Brother solve this issue, if that's the case we'll likely upgrade to using that version during the hackathon and have no need for the no-type-b branch moving forward.


Physical Properties Title Page

Although the title page is fairly complete, we don't do the best job of stating that the convolution form of the relationships is only necessary when the physical properties are dispersive. I also found a couple typos I should fix.

I fixed this and it is merged to master now.


Is the project still alive?

@maciejtreder I saw that your last commit was on April, 24. Is your project still alive?

Hello @mattmeye Unfortunately recent time I don't have a lot of time to maintain this project and add new functionalities. But, AFAIK it is still working with the recent Angular release.


Arithmetic visitors

Write visitors for arithmetical operators.

[x] Addition
[x] Substraction
[x] Product
[x] Quotient
[ ] Null/Missing handling
[x] Type check
[x] Precedence

Issue completed, except null which is transferred in a specific issue (#10)


fix: lazily evaluate default in foldExit

Noticed when debugging the other day that the default route is always evaluated, even if the main route evaluates

Codecov Report

Merging #789 (af579a3) into main (2d26f13) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #789   +/-   ##
=======================================
  Coverage   51.75%   51.75%
=======================================
  Files          68       68
  Lines        2085     2085
  Branches       63       63
=======================================
  Hits         1079     1079
  Misses       1006     1006

Impacted Files
Coverage Δ

zio-http/src/main/scala/zhttp/http/HExit.scala
76.00% <ø> (ø)

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 2d26f13...af579a3. Read the comment docs.

This is by design. Primary reason would be performance. Why would you need this to be lazily evaluated?

This is by design. Primary reason would be performance. Why would you need this to be lazily evaluated?

Interesting, wouldn't it be more performant not to do this? It's doing extra work on each request for potentially no reason

It depends how you use it. In this context, calling by name has a bit of memory overhead and using it in hot paths can turn out to be counter productive.

Makes sense. Happy to close


jbang: 0.103.2 -> 0.104.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/jbangdev/jbang/releases.
meta.description for jbang is: Run java as scripts anywhere
meta.homepage for jbang is: https://https://www.jbang.dev/
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.104.0 with grep in /nix/store/3amvj0f1xh329vkldfnv893v0lisjyda-jbang-0.104.0
found 0.104.0 in filename of file in /nix/store/3amvj0f1xh329vkldfnv893v0lisjyda-jbang-0.104.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
jbang

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3amvj0f1xh329vkldfnv893v0lisjyda-jbang-0.104.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The 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 jbang https://github.com/r-ryantm/nixpkgs/archive/6b1ab3aa4b20fb1b05c98f237e56fdaee91ce98f.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/3amvj0f1xh329vkldfnv893v0lisjyda-jbang-0.104.0
ls -la /nix/store/3amvj0f1xh329vkldfnv893v0lisjyda-jbang-0.104.0/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 run on x86_64-linux 1

1 package built:

jbang

Maintainer pings
cc @moaxcp for testing.

Result of nixpkgs-review pr 218855 run on aarch64-darwin 1

1 package built:

jbang


Provide an interface to MLPerf Inference submitters to use CM based submission generation

Currently, MLPerf submission generation via CM happens only when the results are also generated via CM. It'll be good to have this option for those who generate MLPerf inference results via custom automation.
@anandhu-eng Lets work on cleaning up this documentation. Some suggestions.

For txt, json or any non-code files lets use - rather than _ in the file names for consistency.
We need to add a sample cm-sut-info.json  file. I think we can upload it inside the generate-mlperf-inference-submission CM script folder and link it.
We need to separate out system_name and platform_name - so need to have one more entry in the cm-sut-info.json. Platform name will be the SUT name appearing in the inference results git repository whereas system name will be the name appearing in the official results table.
We should also add a real output of the tree command.

This is now completed. https://docs.mlcommons.org/inference/submission/


Restructured structs to save on memory

In Go, structs are stored in memory "as-is", that is, in the order that they are written. Due to padding, this ends up leaving a bit of memory unused. It is possible (and pretty easy) to re-organize structs so as to optimize them for memory usage.
This is a pretty small PR that just optimizes some of the structs. It may be undesirable for aesthetic reasons, but in my opinion it's a pretty painless improvement.
Here is the data, if you're interested (obtained via the go lsp):

Struct
Old size (bytes
New size (bytes)

Token
32
16

DebuggerToken
72
48

ResolvedToken
64
40

Instruction
40
32

Breakpoint
24
16

Great catch. Thanks for the contribution!


Centralize

This PR closes #1087
I have centralize the user data and also fixed the aditya bug. It was not a that much big issue so I also refactored somewhat the login and signup page by taking out the OAuth function and making them more reusable and short.

Hey @narayan954 Please try to merge my all PRs asap. Today is the last day. And I think leaderboard will only update once at 5PM

Hey @narayan954 Please try to merge my all PRs asap. Today is the last day. And I think leaderboard will only update once at 5PM

Hi @Palakkgoyal Actually us maintainers have time till tomorrow to merge, but I'll merge it by eve.... I'm currently outdoors.Will try to merge asap

Oh Okay. Thanks for being so supportive.

hi @Palakkgoyal can you please resolve conflicts? Thanks

Resolved merge conflict.


⚠ Turnos 24x7 has degraded performance

In cfb0282, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 1006 ms

Resolved: Turnos 24x7 performance has improved in 5c7794e.


Doesn't work in VS Code

thank you for reading this issue before, am tried to installing this extension on my VS Code. It's done properly. But, when am try to running my code. vs code said : You don't have an extension for debugging Kotlin. Should we ..... ?
what I suppose to do with that ? there is any more guide for me to solve this ?

This plugin does not provide language server or debugging capabilities. This is ONLY a syntax highlighter. https://github.com/mathiasfrohlich/vscode-kotlin#features


Changing the B letter in the loader screen?

Hi @bchiang7 ,
I am trying to change the letter in the Loading screen from B to an O. How can I do this? I cannot see any B in the loader.js file. Where is the animation in the codebase?
Thanks

Hey @ojsimon, the logo is an SVG I made then exported from Sketch. It lives here https://github.com/bchiang7/v4/blob/master/src/components/icons/loader.js

@bchiang7 is there an easy way to remove the loader completely and just go straight to the homepage?

You would need to modify layout.js to not use the loading state

Hi, can you help me with the svg of letter A or suggest me a guide.
Thanks!

I know this is already closed but I was able to replace the letter B with text element on svg instead of path.
        <text x="26" y="57" fill="currentColor" fontSize="50px" fontFamily="Consolas, serif">
          x
        </text>

You can do this on both components/icons/ loader.js and logo.js.


Fix #68: Make inventory default's size dependent on selected type

Default inventory sizes are configurable in the SmartInventory#getDefaultDimensions() method. I used the SlotPos class to store the default row and column size, might be better to replace it with own class (or maybe just an array of 2 integers).

Thanks for your work :)


[Cosmos] Remove unused files

Remove unused murmur hash and consistent hashing ring files
Run local tests against proper emulator port

/azp run python - cosmos - tests

@annatisch What's the difference between the tests that ran when I opened the PR and the ones that ran when you triggered the pipeline via the bot?

@southpolesteve - it should be live vs emulator.
However it looks like there's currently an issue without our engineering system (the OSName error). I will re-trigger once that's been resolved on our side :)

/azp run python - cosmos - tests


Add dotcomboom.somnolescent.net

👋 🐍
Webring icon is in the footer:

Also, you'll have to add some headers in to deal with CORS in order for us to read your twtxt file for the hallway.


Figure out how to route documents to a different data stream in Elasticsearch

Elastic introduced rhe reroute processor with https://github.com/elastic/elasticsearch/pull/76511 and it is available since 8.8.0.
I want to explore how to use the new Elasticsearch rerouting capabilities to support new use cases and bring more value to end users.

Basic example of a pipeline that routes document based on Kubernetes labels:
---
description: Pipeline for Kubernetes container logs
processors:
  - reroute:
      dataset:
        - '{{kubernetes.labels.elastic_co/dataset}}'
        - '{{data_stream.dataset}}'
      namespace:
        - '{{kubernetes.labels.elastic_co/namespace}}'
        - '{{data_stream.namespace}}'

The dataset and namespace can be a single value or and array. It will use the first valid value in the list.


Add test

cypress or jest?

Or https://testing-library.com/docs/react-testing-library/intro/, https://github.com/testing-library/react-testing-library


plsss update YTSytemAppearance

i know its not the right place but can you please update YTSytemAppearance so that it works with the latest yt version? :)

@binnichtaktiv Your device OS version? Your YouTube version? How does it not work?

@binnichtaktiv Your device OS version? Your YouTube version? How does it not work?

iOS 13.3 latest yt version 17.05.2. YTSystemAppereance should change automatically to darkmode if iOS darkmode is enabled right? Or do I misunderstand something

@binnichtaktiv YT app should toggle between light and dark mode automatically as you toggle system light or dark mode.

@binnichtaktiv YT app should toggle between light and dark mode automatically as you toggle system light or dark mode.

Yeah but it doesn’t do that automatically

@binnichtaktiv YT app should toggle between light and dark mode automatically as you toggle system light or dark mode.

Yeah but it doesn’t do that automatically

Did you selected 'Use device theme' in YT Settings?

@binnichtaktiv YT app should toggle between light and dark mode automatically as you toggle system light or dark mode.

Yeah but it doesn’t do that automatically

Did you selected 'Use device theme' in YT Settings?

Nevermind got it working after messing around with it. Idc what the problem was😅


improve unsorted imports

Please provide a description of this PR:
improve unsorted imports

@AllenZMC: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
18c8cba47588a8be758b4761eea651cbedf34e21
link
true
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@AllenZMC: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
18c8cba47588a8be758b4761eea651cbedf34e21
link
true
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

This is auto generated. If you want to change it you would need to change the generation logic.

@howardjohn Fixed.

/cc @hzxuzhonghu


Add GC9A01 Driver

Add GC9A01 Driver

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for your contribution.

Merged in this commit: cda2b912fbaef410fe0f47bbaa3c4509da51e8e0


Log improvements

From my TODO list:

[x] switch to a structured logger (like zap)
[x] include X-Request-Id generated in service/middleware/requestid.go
[x] add a log line when adding files
[x] add --log-level CLI flag to set log level

zap is included since 9447a8d76830e2674b54dbbbd5de1b73ee1e52c5, but I don't like the formatting default console encoding:
2022-03-17T13:40:10.806+0100    INFO    exec/docker_client.go:66        image already present   {"image": "texlive/texlive:latest"}
2022-03-17T13:40:10.806+0100    INFO    service/service.go:80   starting server {"addr": ":2201"}
2022-03-17T13:40:16.904+0100    INFO    tex/document.go:107     adding file     {"request-id": "0767bf4c-a8ee-4832-836f-df6a7d096224", "filename": "chapter/input.tex"}
2022-03-17T13:40:16.905+0100    INFO    tex/document.go:107     adding file     {"request-id": "0767bf4c-a8ee-4832-836f-df6a7d096224", "filename": "input.tex"}
2022-03-17T13:40:16.905+0100    INFO    tex/document.go:151     found \documentclass    {"request-id": "0767bf4c-a8ee-4832-836f-df6a7d096224", "filename": "input.tex"}
2022-03-17T13:40:16.905+0100    INFO    tex/document.go:107     adding file     {"request-id": "0767bf4c-a8ee-4832-836f-df6a7d096224", "filename": "doc.tex"}
2022-03-17T13:40:16.905+0100    DEBUG   exec/docker.go:29       running latexmk {"request-id": "0767bf4c-a8ee-4832-836f-df6a7d096224", "args": ["-cd", "-silent", "-pv-", "-pvc-", "-pdfxe", "input.tex"]}
2022-03-17T13:40:16.961+0100    DEBUG   exec/docker_client.go:188       container is ready      {"id": "dcaeabe514afd96bebd6fd8fe0cd83d36fb725bc9bf01f911e6158d926eb141a", "work-dir": "/tmp/texd-483222946"}
2022-03-17T13:40:18.364+0100    DEBUG   tex/document.go:298     fetching result {"request-id": "0767bf4c-a8ee-4832-836f-df6a7d096224"}

My primary issues are:

The timestamp should be removed or at least shortened to "seconds since startup" (like logrus).
There's no color. I like color in dev mode.
Fields are not aligned.

These issues can be easily addressed using either a custom zapcore.EncoderConfig, or by providing a custom encoder (zap.RegisterEncoder). More importantly, this can be addressed later.

Let's switch to the log/slog package for structured logging.

I don't object, but need to find time to do the conversion. Fancy a PR?


zoom effecting text size

prevent incresing textsize during zoom sticker
need to manage text size during zoom sticker

I think that is not possible because after add text sticker it makes a canvas so. it is not possible.


XVim didn't show in Xcode 8.2

Operation
Update Xcode to 8.2
remake XVim
and there is no XVim active in xcode, and no XVim Menu in Xcode Editor Menu list
Environments

Xcode Version [  8.2  ]
XVim branch and revision [  master   ]
Keyboard Language [  us-ascii   ]
Input source language [ zh-CN   ]

sorry for this issue. It's my mistake.
I have to recodesign the Xcode after upgrade to new version.


WordCountInteractiveQueriesRestService does not close its state store iterators

We discovered this while trying to follow this particular example for ways to interactively query the state store. The iterator is not being closed and the memory footprint of the application would grow while the REST api is being queried.

It's the users responsibility to close iterators returned from IQ calls. This is documented in the corresponding JavaDocs IIRC (note, that it was not documented in some older releases unfortunately).


Bank account

issueのタイトル
[#81]口座情報の取得
技術的な実装詳細

実装課題

新規ライブラリ導入の理由(メリット)・背景・ドキュメント等

リリース時の注意点

pylint実行時の点数
-　bank_account(1.44/10)
残っているエラーの詳細
-No config file found, using default configuration
************* Module app.module.bank_account
C:130, 0: Final newline missing (missing-final-newline)
C:  1, 0: Missing module docstring (missing-docstring)
R:  8, 4: Method could be a function (no-self-use)
E: 17, 4: Method should have "self" as first argument (no-self-argument)
E: 22,26: Instance of 'ACCOUNTINFORMATION' has no 'fetch_balance' member (no-member)
E: 32, 4: Method should have "self" as first argument (no-self-argument)
E: 37,26: Instance of 'ACCOUNTINFORMATION' has no 'fetch_balance' member (no-member)
E: 47, 4: Method should have "self" as first argument (no-self-argument)
E: 52,26: Instance of 'ACCOUNTINFORMATION' has no 'fetch_balance' member (no-member)
E: 60, 4: Method should have "self" as first argument (no-self-argument)
E: 65,26: Instance of 'ACCOUNTINFORMATION' has no 'fetch_balance' member (no-member)
E: 73, 4: Method should have "self" as first argument (no-self-argument)
E: 78,26: Instance of 'ACCOUNTINFORMATION' has no 'fetch_balance' member (no-member)
E: 87, 4: Method should have "self" as first argument (no-self-argument)
E: 91,26: Instance of 'ACCOUNTINFORMATION' has no 'fetch_balance' member (no-member)
E: 98, 4: Method should have "self" as first argument (no-self-argument)
E:102,26: Instance of 'ACCOUNTINFORMATION' has no 'fetch_balance' member (no-member)
E:110, 4: Method should have "self" as first argument (no-self-argument)
E:114,26: Instance of 'ACCOUNTINFORMATION' has no 'fetch_balance' member (no-member)
UI変更
変更前のキャプチャ
変更後のキャプチャ
動きがある場合(GIF動画など)
その他・備考

APIキーは登録機能がすでにありますのでその機能を使って
呼び出すようにしてください。
dbファイルはgithubに上げれないようにしています。

APIキーは登録機能がすでにありますのでその機能を使って
呼び出すようにしてください。
dbファイルはgithubに上げれないようにしています。


PowerShell example fails Create and manage Azure budgets

The PowerShell example fails with error New-AzConsumptionBudget : Operation returned an invalid status code 'BadRequest' . The badrequest is only revealed as an error only available when you set the Debug flag.
New-AzConsumptionBudget -ResourceGroupName RGBudgets -Amount 60 -Name PSBudgetRG -Category Cost -StartDate 2018-06-01 -EndDate 2018-11-01 -TimeGrain Monthly -Debug

The error only shows when the debug flag is set,
Cost Management supports only Enterprise Agreement, Web direct and Microsoft Customer Agreement offer
types. Subscription 9f241d6e-16e2-4b2b-a485-cc546f04799b is not associated with a valid offer type.
Apparently it is not supported.
The work around is not explained (REST or Template might work.)

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

ID: 09acb09f-6171-fdd8-a5d4-0d036b467c5a
Version Independent ID: 1bffb9cc-b99e-c000-eb9e-47981e27eedc
Content: Tutorial - Create and manage Azure budgets
Content Source: articles/cost-management-billing/costs/tutorial-acm-create-budgets.md
Service: cost-management-billing
GitHub Login: @bandersmsft
Microsoft Alias: banders

@brucedkyle Thanks for the question. We are investigating this issue and will get back to you soon.

@brucedkyle This appears to be an issue with the API version. The same is discussed here - https://github.com/Azure/azure-powershell/issues/11642 per the link the fix would come in effect by end of the year.

Thanks to @SadiqhAhmed-MSFT  Looking forward to this feature working as expected.


Support for different UA providers

Still a few details missing, like fixing the tests, and actually smoke test it.
@alecxe you can check how it is looking
Feel free to ask anything and suggest any changes.

Applied changes of review. Still missing the tests.
@alecxe I fixed the README. Feel free to clone the fork and push to this branch whatever changes to the readme you want.

This is looking awesome so far @0xfede7c8!

Should I change anything to the tests? I thought I did but as we are mantaining compatibility it should work right?
How should I run the tests to try?

@0xfede7c8 yeah, it's important to see that the existing tests pass as is.
Apologies as we don't really have test/dev environment setup instructions for contributors here.
You should be able to just call pytest after installing dev requirements with pip install -r dev-requirements.txt. pytest would use pytest.ini options and auto-discover tests automatically. Lmk if it works.

Tests passing. Fixed some stuff that is discovered while testing.

Ok, it seems that I need to make some tests to cover the new providers.

The tests on travis fail (https://travis-ci.org/github/alecxe/scrapy-fake-useragent), but they pass locally. I suspect the mock for fake-useragent does not work there for some reason and, hence, fake-useragent fails to get the user-agents. I'll keep trying to make it work but lmk if you have ideas what is going on. Thanks.

fake-useragent can make use of a cache in /tmp/something. I can be that? Try deleting that and running locally again.

fake-useragent can make use of a cache in /tmp/something. I can be that? Try deleting that and running locally again.

Bingo. Yes, it was an incorrect mock that was then cached and reused :) Thanks!
All tests passed. Does it all look good to you and would work for your use case? Once I get a thumbs up from you, I'll go ahead and merge and upload to PyPI - lmk.
Thanks a lot for doing this!

It's good for my use case! Thanks for the help!


Release/1.9.0

Description
Creating a release PR 1.9.0. This is mainly to deploy the Events Building Block. Contributions BB and Catalog won't be deployed now.
Fixes #609
Review Time Estimate
Please give your idea of how soon this pull request needs to be reviewed by selecting one of the options below. This can be based on the criticality of the issue at hand and/or other relevant factors.

[ ] Immediately
[ ] Within a week
[x] When possible

Type of changes
Please select a relevant option:

[x] Bug fix (non-breaking change which fixes an issue).
[x] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).
[ ] Other (any another change that does not fall in one of the above categories.)

Checklist:
Please select all applicable options:

[ ] I have signed the Rokwire Contributor License Agreement (CLA). (Any contributor who is not an employee of the University of Illinois whose official duties include contributing to the Rokwire software, or who is not paid by the Rokwire project, needs to sign the CLA before their contribution can be accepted.)
[x] I have updated the CHANGELOG.
[ ] I have read the Contributor Guidelines.
[ ] I have performed a self-review of my own code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] My change requires updating the documentation.
[ ] I have made necessary changes to the documentation.
[ ] I have added tests related to my changes.
[ ] My changes generate no new warnings.
[ ] New and existing unit tests pass locally with my changes.
[ ] Any dependent changes have been merged and published in downstream modules.

@wenjzhu, please share any feedback that you may have. Thanks.

@wenjzhu, please share any feedback that you may have. Thanks.

Thanks you all for the reviews.

Thanks you all for the reviews.


Add auto complete to package selection in Edit Dialog for channels

@joaquimrocha this is fixed now

LGTM. Thanks @ashu8912 .
I have updated your commits' messages and will merge after CI runs.


Tidy up some Core shared source files

With the addition of the small shim GeneratorPageableHelpers in https://github.com/Azure/autorest.csharp/pull/3702, we can remove some unused methods from the PageableHelpers shared source file.  In addition the LowLevelPageableHelpers class appears to be empty, so removing this file.

API change check
API changes are not detected in this pull request.


Bug Report - Darth Vedant669 |<PHONE_NUMBER>.0329714

please fix the counting bug. Evaluating maths takes to long to tick

Fixed in here: https://github.com/FusionSid/Why-Bot/commit/7e70409c7d7a793e73818e2071c8801e99e0fc35


Generate text representation of occurence on demand

Presently, you need to call the build() method to be able to fetch toText's value.

Added in 3.1.0


OpenAPI specifications for our internal and external backend APIs

Proposed changes
What changed

Why did it change

Issue tracking

PYI-XXXX

Checklists
Environment variables or secrets

[ ] No environment variables or secrets were added or changed

[ ] Documented in the README
[ ] Added to deployment repository
[ ] Added to local startup repository

Other considerations

[ ] Update README with any new instructions or tasks

Also I wasn't sure where our shared-attributes lambda fits into this? I guess it would occur during the /event/cri/start endpoint so I imagine it would be long there but with a better lambda name as it might be doing a bit more than just the shared attributes stuff?


⚠ Bofrost.lu has degraded performance

In ba5de57, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1836 ms

Resolved: Bofrost.lu performance has improved in f563f36 after 16 minutes.


[stable/postgresql] pod not starting

Is this a request for help?:
YES
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT

Version of Helm and Kubernetes:
Client: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.3", GitCommit:"2bba0127d85d5a46ab4b778548be28623b32d0b0", GitTreeState:"clean", BuildDate:"2018-05-21T09:17:39Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.3", GitCommit:"2bba0127d85d5a46ab4b778548be28623b32d0b0", GitTreeState:"clean", BuildDate:"2018-05-21T09:05:37Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Which chart:
stable/postgresql
DEPLOYED        postgresql-2.3.1        10.5.0          default
What happened:
CrashLoopBackOff on start
nami    INFO  postgresql successfully initialized
INFO  ==> Starting postgresql...
nami    ERROR Unable to start com.bitnami.postgresql: pg_ctl: could not start server
Examine the log output.

Also, there is no straightforward way to see other logs other than this.
Hints on how to inject a sidecar for debugging purposes would also be welcomed.
What you expected to happen:
Pod running and serving connections
How to reproduce it (as minimally and precisely as possible):
helm install stable/postgresql
Anything else we need to know:
Running on Docker for Windows Version 18.06.1-ce-win73 (19507)
Why this chart is based on bitnami image and not the official postgres image is something that I would appreciate clarifying.

Having the same issue upon restart. Maintainers please help!!!
Have you got persistance enabled?

Cannot believe that after two weeks nobody bothers to fix this...

I am trying to reproduce the error in different platforms but no luck, it seems an issue related to Docker for Windows managing securityContext and volumes
##
## Init containers parameters:
## volumePermissions: Change the owner of the persist volume mountpoint to RunAsUser:fsGroup
##
volumePermissions:
  image:
    registry: docker.io
    repository: bitnami/minideb
    tag: latest
    pullPolicy: Always
  securityContext:
    runAsUser: 0

## Pod Security Context
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
##
securityContext:
  enabled: true
  fsGroup: 1001
  runAsUser: 1001

replication:
  enabled: true
  user: repl_user
  password: repl_password
  slaveReplicas: 1

Looking through the internet I found this issue https://github.com/docker/for-win/issues/2048 that seems to be the same, but without any response

@carrodher  I don't believe this is related to Windows. I'm having this problem on GCP using GCEPersistentDisk.
Using the default values, the chart installs well the first time. However, if I:

helm install
helm delete --purge
helm install again without completely deleting the pvc first, this error will happen.

Without digging too deep yet, I imagine this has to do with the permissions but there isn't an obvious error to follow.
Welcome to the Bitnami postgresql container
Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-postgresql
Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-postgresql/issues

nami    INFO  Initializing postgresql
postgre INFO  ==> No injected postgresql.conf file found. Creating default postgresql.conf file...
postgre INFO  ==> No injected pg_hba.conf file found. Creating default pg_hba.conf file...
postgre INFO  ==> Deploying PostgreSQL with persisted data...
postgre INFO  ==> Configuring PostgreSQL...
postgre INFO  ==> Configuring replication parameters...
postgre INFO  ==> Configuring permissions for config files...
postgre INFO
postgre INFO  ########################################################################
postgre INFO   Installation parameters for postgresql:
postgre INFO     Persisted data and properties have been restored.
postgre INFO     Any input specified will not take effect.
postgre INFO   This installation requires no credentials.
postgre INFO  ########################################################################
postgre INFO
nami    INFO  postgresql successfully initialized
INFO  ==> Starting postgresql...
nami    ERROR Unable to start com.bitnami.postgresql: pg_ctl: could not start server
Examine the log output.

I am experiencing the same thing in EKS. If I attempt a deployment with the same name as a previously deleted release, postgres will fail to start if a persistent volume remains from the previous deployment.

Same issue here. I even fail when I delete all previous pv and pcv.
Any ideas?

Hi @bholzer

I am experiencing the same thing in EKS. If I attempt a deployment with the same name as a previously deleted release, postgres will fail to start if a persistent volume remains from the previous deployment.

According to what you say it should be related with previous PVC that were not removed when deleting the Helm chart and do not have the right permissions.
Could you please check the existing PVCs after deleting the previous chart? E.g. (chart named "my-release")
$ helm delete --purge my-release
release "my-release" deleted
$ kubectl get pvc
NAME                           STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS
data-my-release-postgresql-0   Bound    pvc-626c5604-0e73-11e9-be88-42010a8e00c9   8Gi        RWO            standard

You can remove the previous PVCs by running:
$ kubectl delete pvc data-my-release-postgresql-0
persistentvolumeclaim "data-my-release-postgresql-0" deleted

After that you should be able to install PostgreSQL without issues.

@alexandruast it sounds like others are having problems with pre-existing PVC in cloud providers but no one has addressed your original issue where Postgres won't start with persistence enabled on Docker for Windows (D4W). I've been seeing the same failure and while I don't have a full answer, here is some extra information that might help and a possible workaround. (Sorry for the long post. This is in part for my own peace of mind to get everything I've found written down in one place)

Also, there is no straightforward way to see other logs other than this.
Hints on how to inject a sidecar for debugging purposes would also be welcomed.

There is a related open ticket on the bitnami repo this chart is based on: bitnami/bitnami-docker-postgresql#91. In that ticket @juan131 mentioned nami logs to /opt/bitnami/postgresql/logs/postgresql.log. With that information, I was able to get the logs from the failed run with:
>kubectl exec vocal-dachshund-postgresql-0 cat /opt/bitnami/postgresql/logs/postgresql.log
2019-01-04 20:49:01.744 GMT [86] FATAL:  data directory "/opt/bitnami/postgresql/data" has wrong ownership
2019-01-04 20:49:01.744 GMT [86] HINT:  The server must be started by the user that owns the data directory.

I don't know how to use a sidecar to read these logs, but running that command should help identify the root cause of your problem. I'm betting it's the same failure as mine as we are both using Docker for Windows.
Docker for Windows has a known limitation for its hostpath storage class. By default D4W mounts volumes to %userprofile%\.docker\Volumes. When running helm install stable/postgresql you should see it create a folder in that directory that mathes the pod name. Unfortunately D4W is unable to correctly assign permissions to volumes mounted in this way. You can find a better explanation at docker/for-win#1669.
That issue also mentions the same error I was seeing The server must be started by the user that owns the data directory. To get around this, @pgayvallet suggests setting the PV to use a mount path on the Linux VM host outside of /host_mnt (the directory on the Linux VM which maps to Windows .docker/Volumes).
You can follow his instructions or create these Kubernetes objects to make a volume that should work:
kind: PersistentVolume
apiVersion: v1
metadata:
  name: pgdata
  labels:
    type: local
spec:
  storageClassName: hostpath
  capacity:
    storage: 8Gi
  accessModes:
    - ReadWriteOnce
  hostPath:
    path: "/tmp"
---
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: pgdata
spec:
  storageClassName: hostpath
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 8Gi

Once the PV and PVC exist, you should be able to install this chart with the command: helm install stable/postgresql --set persistence.existingClaim=pgdata
...
The catch is that because doing this mounts the volume to the Linux VM /tmp/ directory, it will stick around until the Linux VM is blown away. So all future deployments will use the same mounted volume which can cause problems with permissions etc. D4W intentionally locks down the Linux VM so you can't SSH into it. I've found a roundabout way to gain access to it and clear the /tmp/ directory manually but it's not pretty. I can provide the method if anyone thinks it would be useful. Otherwise, you can delete the Moby Linux VM and have D4W recreate it at startup.


Update api docs to add option for deleting a single IP

As added in #505.  This updates the docs to go along with that PR.

Awesome, thanks! 👍

@roymarantz I updated the docs as requested.  Does this look better?

👍


Mit branch

@iboulolo Please provide us with:

the school official website URL
the school street address, including city and country
an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course.

@iboulolo You might miss my previous comment. Please react.

@iboulolo I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the aforementioned issue. Thank you for your understanding!


Compile Error "invalid initialization of non-const reference"

os:
centos 7.2
gcc-c++:
g++ (GCC) 4.8.5 20150623 (Red Hat 4.8.5-39)
ProgramOptions.hxx resp current commit:
7ab12da5cc8f42bb710fb9e7ed26baf322a0b067
use -std=c++11  but:
L112:23: error: invalid initialization of non-const reference of type ‘std::ostream& {aka std::basic_ostream<char>&}’ from an rvalue of type ‘<brace-enclosed initializer list>’
    : m_stream{ stream } {

This seems to be a compiler issue. I was able to reproduce it with g++-4.8.5.
I pushed a workaround in commit be2fc7552eac83e766a00a4963b841d5daf3723d but from what I've seen, g++-4.8.5 is not able to handle some of the SFINAE machinery needed to get .bind working. If that is the case for you as well, I recommend you not to use .bind or upgrade to a newer compiler.

thanks


feat: Implement Tracking in Go

This PR

Implement Tracking in Go

Related Issues

Fixes #291
Notes
Follow-up Tasks

How to test

View example in client_example_test.go

Thanks @dinhlockt02 , this will be included in the next release!


Add real videos

cc @will-moore adding here two videos available at the moment, for ease of checking the layout with real content.
Feel free to cherry-pick the commits, I will close the PR then, or, we might decide otherwise later.

@will-moore I wonder why do the videos in the layout suggested in https://github.com/ome/www.openmicroscopy.org/pull/370  (this PR is on top of the https://github.com/ome/www.openmicroscopy.org/pull/370) are appearing black until you click on them to play.
Whereas in the layout which was in https://github.com/ome/www.openmicroscopy.org/pull/361, the videos were showing an image representing the first frame. I do not think this is because of the videos themselves. See screenshot below for https://github.com/ome/www.openmicroscopy.org/pull/361 and compare with https://snoopycrimecop.github.io/www.openmicroscopy.org/events/ome-community-meeting-2020/day1/ for the present, black one.


Quotes around case options

I have been going over the git logs and this seems to be something that has flip flopped.
In manifests/init.pp the operating system names in the case statement are no longer in quotes (they were removed in commit 2da0666f90519518a56513c0aeb7ca25b3f0bcc0
Before that the quotes were added in commit a17ae4a7dff16af67d4f474f8cd2b544a6714d5c
I use puppet 3.8 in Debian 7 and as soon as I change the puppet configuration to have parser = future not having the quotes breaks the module.

a new version v2.0.0 has been published at https://forge.puppet.com/meltwater/cpan .
Thanks


blossom-reva

with this art piece I first wanted to make penrose tiles, so I started out with rhombuses (but the decision-making/math was too confusing, w/ very few resources)
I realized that the rhombuses looked like flowers, so I wanted to make something that looks like a pretty flower garden.
then I played around with them, turning them into rows of flowers (I got this really cool 3-d effect at one point!)
I decided to make rings of flowers and then once I created one ring, I played around with for loops to create multiple rings of different sizes and layouts.
overall, the process took me over 2 weeks (with some breaks in between, probably in total 8 hrs)
now, the art piece looks like blooming flowers, with the outermost flowers being the biggest and the innermost one the smallest (kind of like fireworks but flowerworks)

Nice work being persistent and thanks for the submission! I think this is still a bit short. Though not a perfect measure a minimal artwork would be around 100 lines.
How far did you get with the Penrose tiling?

Note: I added some more comments in my latest update
I didn't get very far because the penrose math I found required object oriented programming or complex algorithms (that were not working in blot for me).
Can you clarify what revisions you would like me to make?

hey! @leomcelroy I made some revisions, is it better now?

I think it looks pretty nice in many generations but the placement of the shapes can be a bit haphazard with them overlapping. It's definitely possible to do a tiling and I would strongly encourage persisting with that. I can help out where you get stuck. Can you share an image of what your are aiming for?

I updated the code so that they don't overlap as much, thanks for catching that! Is it better now?

I've updated the code so it looks more like an organized garden rather than flower arrangement, is it better now?

I'm not sure how to open another pull request, but I've uploaded code for my penrose tiles to this one. For the math/algorithm behind it, I looked at a book called L-system Fractals by Mishra which was a very cool read!

Nice! Can you show a few productions to demonstrate the sort of patterns this can make. With that this should be good to go.
Let's close this PR and you can open a new one the same way you opened this the first time, that way we won't also pull in the outdated files when we merge.


fix: Inject istio annotation

Description
Changes proposed in this pull request:

...
...
...

Related issue(s)

This PR was only a workaround. The final solution is here: https://github.com/kyma-project/warden/issues/238


Controller only updates an Instance's status, but not its spec

Judging from the code, the controller only updates the Instance's status during provisioning. The newly added async support, for example, sets the spec.OSBLastOperation, but never actually posts the update to the API server.
Also, the spec.OSBDashboardURL is never stored (neither for sync, nor async broker responses).

I've just noticed #757, which makes half of this issue moot. But it still applies to the OSBDashboardURL.

I can move it to status myself. Just need someone to give me the go-ahead.

@luksa thanks a lot :-)


[feature] root-level inputs should be greedy when using moon in non-monorepo situation

Is your feature request related to a problem? Please describe.

Describe the solution you'd like
Documentation of task inputs states that:

If not defined or inherited, then all files within a project are considered an input (**/*), excluding root-level tasks.

This makes sense when trying to define tasks in a monorepo situation, where there are multiple projects, including the root-level one. But it was unexpected when I setup moon in a single-project configuration, without additional workspace.
If the only project defined is the root project, it should behave the same way as a regular workspace, rather than be treated specially as a "root-level" (because it's the only level).

Describe alternatives you've considered
I can specify inputs manually, but this is inconsistent between monorepo and non-monorepo projects.

Additional context
I was writing some automation that generates my moon configuration, for both monorepo and non-monorepo projects, and got tripped up by this.

Fixed in 1.29

Thank you Miles! Your responsiveness and support continues to be unmatched. 🙇


CupertinoDynamicColor extending Color is confusing

CupertinoDynamicColor should not extend Color. More generally we should treat Color as a sealed class. Instead, it should either wrap or generate a Color object. There are several non-obvious gotchas associated with extending Color:

Setting CupertinoDynamicColor to a Paint and reading it back will silently change the type. This applies to anything else that takes and returns a Color (you need to know the implementation to really know).
In order to interpret Paint.color correctly the engine must convert it (there's currently a bug in the Web engine because it assumed Color was not extended; the fix is smelly).

More generally, when you pass CupertinoDynamicColor as a Color to anything then read it back, it immediately becomes unsafe code, as it requires a runtime downcast from Color, which may or may not succeed (e.g. it will succeed in the BoxDecoration case, but not in the Paint case, or when you pipe it through Color.lerp). However, if all we do is turn CupertinoDynamicColor to a Color in the end, then a CupertinoDynamicColor.toColor would suffice and the intent would be much clearer in code.
This also has a global performance impact as it makes Color a virtual class. For example, color.value requires dynamic dispatch. In the future, when Dart gains unboxed types, we won't be able to unbox Color because of unknown object size.
I realize that changing type hierarchy is a breaking change, but I think in this case it's worth it.
/cc @LongCatIsLooong @ferhatb

I think a combination of union types (https://github.com/dart-lang/language/issues/145) and sealed classes (https://github.com/dart-lang/language/issues/11 but at the language level) would have prevented this issue. This is how:

Sealed classes: the Color class would be marked as sealed and therefore CupertinoDynamicColor would not have been able to extend it in the first place.
Union types: one of the requirements for introducing CupertinoDynamicColor was to not break existing API. This means that Cupertino classes that used to take Color should continue to be able to take Color. Union types would allow us to change the signature from Color to Color | CupertinoDynamicColor. The implementation would switch on the type and implement the appropriate logic.

Other classes that are in danger to being broken in this way but luckily haven't been broken yet:

Path - the engine maintains private fields in this class, and extending it will break the engine in an obscure way.
Rect, RRect, Radius, Offset, Size - these classes are in the same category as Color. In other languages these would be "data classes" (Kotlin), structs (Rust, C), or final classes (Java).

This is similar to String, int, bool, and double classes from dart:core, for which the Dart runtime has intrinsics. To do that the languages seals them in the language spec itself. We'd like to implement similar intrinsics for some of our dart:ui classes but can't.
/cc @leafpetersen

ColorSwatch, which has been around for years and is the basis for MaterialColor, also extends Color.
Maybe it's not ColorSwatch or CupertinoDynamicColor that's broken, but Paint.color.

In that case ColorSwatch and MaterialColor are confusing too (and probably would also fail if we had a similar test to the one we have for cupertino). Although they actually do not override anything from Color (CupertinoDynamicColor does), so I'm not sure why they need to extend Color at all. They just end up sharing the problem of not surviving transformations, such as lerp or Paint.color.
I think this would be my preferred class hierarchy:
sealed class Color;

abstract class ThemeColor {
  Color toColor();
}

class ColorSwatch implements ThemeColor;
class MaterialColor extends ColorSwatch;
class CupertinoDynamicColor implements ThemeColor;

Whenever you want to pass a ThemeColor to the engine (via dart:ui) you first call toColor. On the engine side we want to be able to assume things about object representations defined in dart:ui.
However, with ColorSwatch and MaterialColor in the mix, I realize this would be a much more breaking change.

Chatted with @HansMuller in person. Looks like changing this will make things more painful on the framework side. So instead, we'll create a specialized private class inside the engine for Color, which won't be extensible in the framework, and use that instead.
It doesn't solve the issue with color transformations, but it should be enough for making engine-side optimizations without introducing correctness bugs.


ARTEMIS-3174: Set new connection on ServerSession during reattachment

During session reattachment, also set the new connection on the
"session" member of the ServerSessionPacketHandler. Until now,
the connected ServerSessionImpl instance still referenced the old
connection although it had already been transferred on the new connection.

Could you possibly add a test to validate this fix and mitigate any regressions in the future?

That would be good of course. The only problem is that I'm not familiar with the testing structure of Artemis/how to set up mocks for testing etc. It would help if you could point me into a direction for where to place the test and how to achieve what I want to test.
The test would need to:

Set up an Artemis core client connection to a broker with a confirmationWindowSize != -1
Simulate connection loss to broker, the client has to detect the connection failure ("Connection failure to ... has been detected")
After less than the connectionTTL (default 60 seconds), allow connection to broker again -> client fails over
Client tries to reattach all the sessions, server transfers the sessions
Afterwards, check if the remotingConnection is set correctly (has the new connectionID) on every object connected to the session

It could even be simplified to a "component test" only on the broker where you have a session with an "old" connection, and then do a "ServerSessionPacketHandler.transferConnection" suppyling a new connection. Afterwards, check if the all the objects related to the sessionHandler (itself, the channel, the serverSession) have the new connection assigned.
If you provide me with enough details, I might be able to write the test. Otherwise, it would maybe be easier if you write the test as you know the code in more detail.

Like most functionality in the broker there was an existing test that was simple to modify so I added a test and merged this PR. Thanks for the contribution, @meierhofer08!

Ok perfect, thank you for merging and ensuring that there is a test for the change!


gstreamer: common base classes

This is a minimal refactor to consolidate common gstreamer decoder, encoder and vpp test code into base classes so they can be shared between vaapi and msdk (and va) plugin tests without slash.requires and other plugin specific settings leaking across subclasses (e.g. see https://github.com/intel/vaapi-fits/pull/284#pullrequestreview-653824960).  NOTE: this does not include transcoder consolidation (will submit in separate PR).

cc: @Bin-CI this should be enough to integrate gst-va first-pass.

I think those function also can move into gstreamer as base class function
unit.py:
  def get_supported_format_map
  mapformat(format):
  mapformatu(format):
  map_best_hw_format(format, hwformats):
  map_transpose_direction(degrees, method):
encodepy:
  class EncoderTest(BaseEncoderTest):
    def map_profile(self):
    def map_format(self):
    def map_formatu(self):

These functions are supposed to return specific values supported by the plugin.  Each plugin does not always have the same supported values.  For example, vaapi plugin might support a new format before the other plugins support it.  They might be the same right now, but this will not always be true.
I will consider a design where common ones can be shared in one place and plugin can override as needed.  This can be done in another PR later.  For now, each plugin should implement their own.


Move "Actions" Button in Drawer to Top

Despite being a common action (common actions go in the bottom drawer menu), "Actions" should be the first action in the top drawer menu.

Commit: https://github.com/johneastman/todo/commit/78e382bd041fa3b938ec917655e6394d893f201d


thread monstrous xD

I use this code:
node_modules/.bin/webtorrent-hybrid seed data/my_movie.mp4 --announce 'ws://example.com:6881/announce'

And let it work for a while, number of thread jump from 700 (my normal number of thread of every day usage Ubuntu desktop) to 4k6 threads xD, when do ctrl - c, it go back to normal ~700, will try dig into code and report here.

This library uses electron-webrtc under the hood for it's WebRTC implementation. This is not a very efficient library as it basically starts an entire instance of Chrome. Sorry, no way to fix this until there's a better WebRTC library in Node.js that we can switch to.


SharpVulkan.SharpVulkanException: 'A Vulkan error of type [ErrorDeviceLost] occurred.'

Rarely on a start, we get the following error:
SharpVulkan.SharpVulkanException: 'A Vulkan error of type [ErrorDeviceLost] occurred.'

Might be related to the texture rendering fixes I made here: https://github.com/phr00t/xenko/commit/87fc17d947ac042a177847de2a2f70d65f19820b -- specifically skipping a descriptor update write when one may be expected. Might be more reliable to use the 1x1 texture suggested by xen2 to pass along until the real texture comes around.
Simply running the game again is likely to work, so might be related to threading issues.
Here is some documentation on lost devices (4.2.3, scroll down a bit): https://www.khronos.org/registry/vulkan/specs/1.0/html/vkspec.html#devsandqueues-devices

This commit hopefully resolves this problem: https://github.com/phr00t/xenko/commit/e213ee9a0bdd386e481deae83c69413337caf75a
Will monitor for a bit... if I don't have issues, I'll consider this issue closed.

I was ALMOST ready to close this issue, since it does seem to be happening much more rarely... until this happened:
Xenko.Graphics.dll!Xenko.Graphics.Texture.InitializeImage(Xenko.Graphics.DataBox[] dataBoxes) Line 382	C#

Xenko.Graphics.dll!Xenko.Graphics.Texture.InitializeFromImpl(Xenko.Graphics.DataBox[] dataBoxes) Line 172	C#
Xenko.Graphics.dll!Xenko.Graphics.Texture.InitializeFrom(Xenko.Graphics.Texture parentTexture, Xenko.Graphics.TextureDescription description, Xenko.Graphics.TextureViewDescription viewDescription, Xenko.Graphics.DataBox[] textureDatas) Line 516	C#
Xenko.Graphics.dll!Xenko.Graphics.Texture.New(Xenko.Graphics.GraphicsDevice graphicsDevice, Xenko.Graphics.TextureDescription description, Xenko.Graphics.TextureViewDescription viewDescription, Xenko.Graphics.DataBox[] boxes) Line 1109	C#
Xenko.Rendering.dll!Xenko.Streaming.StreamingTexture.StreamingTask(int residency) Line 351	C#
mscorlib.dll!System.Threading.Tasks.Task.Execute()	Unknown
mscorlib.dll!System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state, bool preserveSyncCtx)	Unknown
mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state, bool preserveSyncCtx)	Unknown
mscorlib.dll!System.Threading.Tasks.Task.ExecuteWithThreadLocal(ref System.Threading.Tasks.Task currentTaskSlot)	Unknown
mscorlib.dll!System.Threading.Tasks.Task.ExecuteEntry(bool bPreventDoubleExecution)	Unknown
mscorlib.dll!System.Threading.ThreadPoolWorkQueue.Dispatch()	Unknown

Made another commit that will hopefully address this: https://github.com/phr00t/xenko/commit/b71444afb0959f5c797947db0a4813ccef786b29
Monitoring...

Made yet another set of changes, which helped shadow maps, and may improve this issue further: https://github.com/phr00t/xenko/commit/f9d8a8c538f2330a2b5752288c18f44d6ed3517f
Haven't experienced this crash in awhile. Going to close for now. If it happens, I'll reopen.


'Logger' object has no attribute 'fileno'

When I run this the GPT Loader is failing with the message:
'Logger' object has no attribute 'fileno'
I believe I have all the dependencies.
Any idea what could cause this?

Yes, see THIS

Thank you - sorry I should have checked closed issues.
It works fine now, thanks for building this.

it's fine don't worry!


Add funding rates params

To have funding rates history of an unique coin, i want to add the future param :
    getFundingRates(futureName) {
        console.log('getFundingRates', futureName);
        if (futureName === null) {
            return this.requestWrapper.get('funding_rates');
        } else {
            return this.requestWrapper.get(`funding_rates?future=${futureName}`);
        }
    }

Thanks for pointing out the missing params! Fixed in v1.1.10, should be available shortly one the build passes.


Move mixer check annotation to model with defaults

Follow up refactoring for https://github.com/istio/istio/pull/11795

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: howardjohn
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: andraxylia
If they are not already assigned, you can assign the PR to them by writing /assign @andraxylia in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @howardjohn. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: costinm, howardjohn
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS [costinm]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@howardjohn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
0f27e7ec8a71185bc4213d2ddd587969de69c95b
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
0f27e7ec8a71185bc4213d2ddd587969de69c95b
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
0f27e7ec8a71185bc4213d2ddd587969de69c95b
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
0f27e7ec8a71185bc4213d2ddd587969de69c95b
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
0f27e7ec8a71185bc4213d2ddd587969de69c95b
link
/test istio-integ-k8s-tests

prow/e2e_pilotv2_auth_sds.sh
0f27e7ec8a71185bc4213d2ddd587969de69c95b
link
/test istio_auth_sds_e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
0f27e7ec8a71185bc4213d2ddd587969de69c95b
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
0f27e7ec8a71185bc4213d2ddd587969de69c95b
link
/test istio-integ-k8s-tests

prow/e2e_pilotv2_auth_sds.sh
0f27e7ec8a71185bc4213d2ddd587969de69c95b
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
0f27e7ec8a71185bc4213d2ddd587969de69c95b
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

New changes are detected. LGTM label has been removed.

/ok-to-test

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
0f27e7ec8a71185bc4213d2ddd587969de69c95b
link
/test istio-integ-k8s-tests

prow/e2e_pilotv2_auth_sds.sh
0f27e7ec8a71185bc4213d2ddd587969de69c95b
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
0f27e7ec8a71185bc4213d2ddd587969de69c95b
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
2984fd0523690e9919376661d91763b137621ac2
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e_pilotv2_auth_sds.sh
0f27e7ec8a71185bc4213d2ddd587969de69c95b
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
0f27e7ec8a71185bc4213d2ddd587969de69c95b
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
2984fd0523690e9919376661d91763b137621ac2
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
2984fd0523690e9919376661d91763b137621ac2
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
0f27e7ec8a71185bc4213d2ddd587969de69c95b
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
2984fd0523690e9919376661d91763b137621ac2
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
2984fd0523690e9919376661d91763b137621ac2
link
/test istio-integ-k8s-tests

prow/e2e_pilotv2_auth_sds.sh
2984fd0523690e9919376661d91763b137621ac2
link
/test istio_auth_sds_e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
2984fd0523690e9919376661d91763b137621ac2
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
2984fd0523690e9919376661d91763b137621ac2
link
/test istio-integ-k8s-tests

prow/e2e_pilotv2_auth_sds.sh
2984fd0523690e9919376661d91763b137621ac2
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
2984fd0523690e9919376661d91763b137621ac2
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@duderino can this be merged?


issue when implementing image caption model

I trained the model, following your instructions. But for some reason, the model produces the same caption for different images. It is as if it is ignoring the initial state supplied to the GRU layer. Can you please help me out

actually, the model gives the same caption for every image. Elaborating on my intuition that the model is "ignoring" the initial sate. When I give start_word as another word(instead of 'sos'), different captions are generated. In fact generate captions works fine, the problem is it does not generate according to images. on the contrary caption generation of caption only depends on start word

I can see this is your first issue on github so I am going to be extremely nice. You cannot expect anyone to help you with a question like this. Look at the date when the tutorial was made - it was YEARS ago! You cannot expect me to remember the details anymore. So I would have to spend hours investigating this problem, and in the end my experience has always been, that it is the user who made problems, so I wasted my time trying to solve non-existent problems. You are coming across as very inconsiderate and selfish when you are posting a question like this. In the future when you post a question on github, stackoverflow, or somewhere else, you need to be very specific about exactly what you have done to the code and data, how you run it, and what the result is. And I would also recommend that you write proper English and capitalize and punctuate your sentences properly. You can't even put a tiny bit of effort into writing a legible question with proper syntax that makes it easy for me to read and maybe answer it, but you expect me to spend hours solving your problems. It really ticks me off when people are being so selfish and inconsiderate.

Pardon my inexperience.
https://api.accredible.com/v1/frontend/credential_website_embed_image/badge/22999930
On Mon, Oct 26, 2020, 6:27 PM Hvass-Labs<EMAIL_ADDRESS>wrote:

I can see this is your first issue on github so I am going to be extremely
nice. You cannot expect anyone to help you with a question like this. Look
at the date when the tutorial was made - it was YEARS ago! You cannot
expect me to remember the details anymore. So I would have to spend hours
investigating this problem, and in the end my experience has always been,
that it is the user who made problems, so I wasted my time trying to solve
non-existent problems. You are coming across as very inconsiderate and
selfish when you are posting a question like this. In the future when you
post a question on github, stackoverflow, or somewhere else, you need to be
very specific about exactly what you have done to the code and data, how
you run it, and what the result is. And I would also recommend that you
write proper English and capitalize and punctuate your sentences properly.
You can't even put a tiny bit of effort into writing a legible question
with proper syntax that makes it easy for me to read and maybe answer it,
but you expect me to spend hours solving your problems. It really ticks me
off when people are being so selfish and inconsiderate.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Hvass-Labs/TensorFlow-Tutorials/issues/125#issuecomment-716528158,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APIUDEHD7OON56HYRM24L53SMVW2XANCNFSM4SLCHMSA
.

@John-p-v1999 fork this repo and commit your work to your fork, push it to github and link to it or just make a gist and also link it it... @Hvass-Labs wants to see some code, and in general it is good practice to provide your code so you can either be helped along or an actual bug is found and fixed.


[Bug] Flink Batch Mode Wrong Status On K8s

Search before asking

[X] I had searched in the issues and found no similar issues.

Java Version
1.8
Scala Version
2.12.x
StreamPark Version
2.1.1
Flink Version
1.16.2
deploy mode
kubernetes-application
What happened
flink BATCH mode job finished and was shut down, the StreamPark FlinkJobStatusWatcher "Failed to visit remote flink jobs on kubernetes-native-mode cluster" and "The deployment is deleted and enters the task failure process."
the batch mode job finished, and the StreamPark job status should be finished instead of failed.
Error Exception
FLINK JOB
2023-08-17 08:19:07,826 INFO  org.apache.flink.runtime.taskmanager.Task                    [] - jobxxxxxxxxxx[3]: Committer (1/1)#0 (ad262c7f219e51660922d308b391fabd_306d8342cb5b2ad8b53f1be57f65bee8_0_0) switched from RUNNING to FINISHED.
2023-08-17 08:19:07,826 INFO  org.apache.flink.runtime.taskmanager.Task                    [] - Freeing task resources for jobxxxxxxxxxx[3]: Committer (1/1)#0 (ad262c7f219e51660922d308b391fabd_306d8342cb5b2ad8b53f1be57f65bee8_0_0).
2023-08-17 08:19:07,826 INFO  org.apache.flink.runtime.taskexecutor.TaskExecutor           [] - Un-registering task and sending final execution state FINISHED to JobManager for task jobxxxxxxxxxx[3]: Committer (1/1)#0 ad262c7f219e51660922d308b391fabd_306d8342cb5b2ad8b53f1be57f65bee8_0_0.
2023-08-17 08:19:07,897 INFO  org.apache.flink.runtime.taskexecutor.slot.TaskSlotTableImpl [] - Free slot TaskSlot(index:0, state:ACTIVE, resource profile: ResourceProfile{cpuCores=0.5, taskHeapMemory=25.600mb (26843542 bytes), taskOffHeapMemory=0 bytes, managedMemory=230.400mb (241591914 bytes), networkMemory=64.000mb (67108864 bytes)}, allocationId: 385c45ca65336c338c22d293bbc1654c, jobId: abf7b7864513fcd9042aba91c3e6fc15).
2023-08-17 08:19:07,899 INFO  org.apache.flink.runtime.taskexecutor.DefaultJobLeaderService [] - Remove job abf7b7864513fcd9042aba91c3e6fc15 from job leader monitoring.
2023-08-17 08:19:07,899 INFO  org.apache.flink.runtime.taskexecutor.TaskExecutor           [] - Close JobManager connection for job abf7b7864513fcd9042aba91c3e6fc15.
2023-08-17 08:19:08,033 INFO  org.apache.flink.kubernetes.taskmanager.KubernetesTaskExecutorRunner [] - RECEIVED SIGNAL 15: SIGTERM. Shutting down as requested.
2023-08-17 08:19:08,041 INFO  org.apache.flink.runtime.blob.TransientBlobCache             [] - Shutting down BLOB cache
2023-08-17 08:19:08,041 INFO  org.apache.flink.runtime.state.TaskExecutorStateChangelogStoragesManager [] - Shutting down TaskExecutorStateChangelogStoragesManager.
2023-08-17 08:19:08,042 INFO  org.apache.flink.runtime.state.TaskExecutorLocalStateStoresManager [] - Shutting down TaskExecutorLocalStateStoresManager.
2023-08-17 08:19:08,043 INFO  org.apache.flink.runtime.filecache.FileCache                 [] - removed file cache directory /tmp/flink-dist-cache-23ab1433-3bbd-4414-a8fe-052419dd4206
2023-08-17 08:19:08,044 INFO  org.apache.flink.runtime.io.disk.FileChannelManagerImpl      [] - FileChannelManager removed spill file directory /tmp/flink-netty-shuffle-2b627284-abfd-4dbe-96f6-f64eadf084b8
2023-08-17 08:19:08,045 INFO  org.apache.flink.runtime.blob.PermanentBlobCache             [] - Shutting down BLOB cache
2023-08-17 08:19:08,045 INFO  org.apache.flink.runtime.io.disk.FileChannelManagerImpl      [] - FileChannelManager removed spill file directory /tmp/flink-io-c3cd4782-e21e-438f-b32f-f618a9feb579
2023-08-17 08:19:08,494 INFO  akka.remote.RemoteActorRefProvider$RemotingTerminator        [] - Shutting down remote daemon.
2023-08-17 08:19:08,495 INFO  akka.remote.RemoteActorRefProvider$RemotingTerminator        [] - Shutting down remote daemon.
2023-08-17 08:19:08,496 INFO  akka.remote.RemoteActorRefProvider$RemotingTerminator        [] - Remote daemon shut down; proceeding with flushing remote transports.
2023-08-17 08:19:08,497 INFO  akka.remote.RemoteActorRefProvider$RemotingTerminator        [] - Remote daemon shut down; proceeding with flushing remote transports.
2023-08-17 08:19:08,602 INFO  akka.remote.RemoteActorRefProvider$RemotingTerminator        [] - Remoting shut down.
2023-08-17 08:19:08,603 INFO  akka.remote.RemoteActorRefProvider$RemotingTerminator        [] - Remoting shut down.

StreamPark
16:19:12.423 [pool-8-thread-1] DEBUG org.apache.streampark.flink.kubernetes.watcher.FlinkJobStatusWatcher - [StreamPark] [FlinkJobStatusWatcher]: Status monitoring process begins - pool-8-thread-1
2023-08-17 16:19:12 | INFO  | ForkJoinPool-1-worker-0 | org.apache.hc.client5.http.impl.classic.HttpRequestRetryExec:113] Recoverable I/O exception (org.apache.hc.core5.http.NoHttpResponseException) caught when processing request to {}->http://<IP_ADDRESS>:30699
16:19:12.424 [ForkJoinPool-1-worker-0] WARN org.apache.streampark.flink.kubernetes.watcher.FlinkJobStatusWatcher - Failed to visit remote flink jobs on kubernetes-native-mode cluster, and the retry access logic is performed.
16:19:12.493 [ForkJoinPool-1-worker-0] ERROR org.apache.streampark.flink.kubernetes.KubernetesRetriever - [StreamPark] Get flinkClient error, the error is: java.lang.RuntimeException: org.apache.flink.client.deployment.ClusterRetrieveException: Could not get the rest endpoint of ods-grading-grading-record-trustworthy-test
16:19:12.493 [ForkJoinPool-1-worker-0] INFO org.apache.streampark.flink.kubernetes.watcher.FlinkJobStatusWatcher - Query the local cache result:false,trackId TrackId(kubernetes-application,flink-cluster,ods-grading-grading-record-trustworthy-test,100071,abf7b7864513fcd9042aba91c3e6fc15,100000).
16:19:12.627 [ForkJoinPool-1-worker-0] INFO org.apache.streampark.flink.kubernetes.watcher.FlinkJobStatusWatcher - The deployment is deleted and enters the task failure process.

Screenshots
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!(您是否要贡献这个PR?)

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi zhaolipan, Thank you for your feedback. Regarding the issue of state tracking in Flink on Kubernetes, we will fix it in a refactored Flink Kubernetes V2 module. Please refer to https://github.com/apache/incubator-streampark/issues/2879

If you want to use flink on k8s, you need to deploy streampark to k8s, otherwise you need to use ingress and merge several PRs from my forked project.


Adding $keys to getAttributes() method

Adding ability to select custom attributes from the model.

No plans to add this.


Fix node creation issues

Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

Codecov Report

Merging #144 (bc64cf6) into master (1873240) will decrease coverage by 0.02%.
The diff coverage is 57.89%.

@@            Coverage Diff             @@
##           master     #144      +/-   ##
==========================================
- Coverage   79.01%   78.99%   -0.03%
==========================================
  Files          39       39
  Lines        1339     1347       +8
  Branches      317      318       +1
==========================================
+ Hits         1058     1064       +6
- Misses        209      211       +2
  Partials       72       72

Impacted Files
Coverage Δ

...kages/pipeline-editor/src/PipelineEditor/index.tsx
45.89% <57.14%> (+1.06%)
:arrow_up:

...es/pipeline-editor/src/PipelineController/index.ts
94.82% <60.00%> (-1.06%)
:arrow_down:

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 1873240...bc64cf6. Read the comment docs.


[core] Support add partition for paimon

Purpose
Currently paimon can not support add partition in flinksql, due to add partition not need commit transaction，so make hms sync to achieve it.

Linked issue: close #xxx

Tests

API and Format

Documentation

I'm not sure whether Paimon need this feature.
@JingsongLi  cc

I think you should use MetastoreClient to add partition. The implementation can be in AbstractCatalog.

I think you should use MetastoreClient to add partition. The implementation can be in AbstractCatalog.

Yes, move to AbstractCatalog maybe better, would change as it. Thanks @JingsongLi


service routing 404 through consul

Saylor 2019/7/16 15:40:36
Using consul as service registry, there is a problem of service routing 404
my services

When I use gateway port to access nl-bomc-rbac service, it doesn't work properly.

my gateway and consul config

Please dont use screen shots, for us to help we need a sample that reproduces the problem.

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


DOC: update windows instructions and move conda/mamba

Relates to #18806
This makes the instructions gotcha about building conda env on Windows more visible and move the note about mamba up too.

The doc build failed for an unrelated reason, that would be good to fix first in a separate PR. Seeing the rendered html here is useful.

Builds locally now, let's see. I think it was just due to the indentation.
I also adjusted 2 other small things while I was there. Added a subheading in the build from source section and also swapped the pip/conda order in the last section to have the same order as the other section.

I'm wondering whether we should instead start shipping lock files like scikit-learn does. I think this tweak isn't an improvement, and a lot of folks are still going to miss it. Removing the possibility of running into this problem in the first place is probably better. WDYT?

I am all for using lock files. I've always been doing that at previous companies for prod. I remember some discussions (and never followed up) saying conda-lock was still in the work? Is it good now to use? I've personally only experienced lock files through Poetry.

Thanks, I can see what changes now. The warning goes together specifically with this line:
mamba env create -f environment.yml

The warning was right under it, and now you've moved it far away. That seems wrong. I think you could either do nothing, or change .. note:: to .. warning:: - but leaving it in its current place.

But the main idea was to move it so that we also see it in the case of building for simply using SciPy and not development.

But the main idea was to move it so that we also see it in the case of building for simply using SciPy and not development.

At that point there is no need to use environment.yml at all, that is only for development purposes.

Yes, in the "use" part we say that one can either use the environment file or manually install the minimal set of deps. And the list includes compilers. That's why I wanted to make the section more visible because otherwise a user is not going to read further (and another problem was that because the conda tab was not selected, you would really miss it if you don't continue and click the tab.)


Record value extraction fails when the store definition doesn't match with RDBMS table

Description:
Record value extraction doesn't work if event table doesn't have full set of columns in SiddhiApp.
Let's say if a table in RDBMS database has 10 columns but event table in Siddhi App has only 5 columns.
The record value extraction in RDBMSIterator class is done by ordinal but the ordinal will not match if the column order in siddhi event table not match with column order  in RDBMS table.
Suggested Labels:
rdbms
OS, DB, other environment details and versions:
Oracle
Steps to reproduce:

Create a table in RDBMS with 10 columns
Define a event table in a siddhi app pointing to the table crated in the previous step, but don't map all columns in the event table.

Fix issue with PR: https://github.com/wso2-extensions/siddhi-store-rdbms/pull/83


Python: parse_message_2 produces id_cred_r as array

The 2nd return value of parse_message_2, id_cred_r, currently has values like [10] or [162, 2, 96, 8, 161, 1, 165, 1, 2, 2, ...]. What it represents is the binary value of ID_CRED_R, a byte string, and it should be represented as such in Python.
(Haven't had a look at the Python implementation yet, might manage a PR.)

Something similar was fixed in 0e2b07bae3f39ae5048cf17269664f35a81658ee already. I think the general rule should be that binary data in return values should not be Vec but PyBytes. (In function arguments it can be convenient to have them as Vec<[u8]> from an API PoV; from a performance PoV it may just as well be a &[u8] if that works). PR available, let's see if CI likes it.


Docker image CI uses node 16

Node 16 is deprecated and emits warnings. The only remaining action that can't be updated to node 20 is the docker-login action. Azure's docker-login action has an issue and PR for this, but it's not merged. I believe we should move to the container-registry-login action by SeptBlast.

That container registry login action produced error, see https://github.com/Erb3/sveio/actions/runs/8630574277/job/23657115694


1.1

More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.
Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Please do not open PRs from release branches into trunk. They will not be merged.


feat: oauth add passkey after signup (popup flow)

Pull Request Checklist

[ ] Did you add new tests and confirm existing tests pass? (yarn test)
[ ] Did you update relevant docs? (docs are found in the site folder, and guidelines for updating/adding docs can be found in the contribution guide)
[ ] Do your commits follow the Conventional Commits standard?
[ ] Does your PR title also follow the Conventional Commits standard?
[ ] If you have a breaking change, is it correctly reflected in your commit message? (e.g. feat!: breaking change)
[ ] Did you run lint (yarn lint:check) and fix any issues? (yarn lint:write)
[ ] Did you follow the contribution guidelines?

PR-Codex overview
This PR introduces a new user signup event in the AlchemySigner and updates various components to handle this event, alongside some refactoring in the useAuthModal and related hooks.
Detailed summary

Added newUserSignup event to AlchemySignerClientEvents.
Emitted newUserSignup on successful user signup in AlchemySignerWebClient.
Refactored closeAuthModal in useAuthModal to improve readability.
Updated CompletingOAuth to simplify auth step setting.
Adjusted AuthModal to handle signup logic with useNewUserSignup.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

do we need to update the ui-demo app to default back to using pop-up now?

done in #1140 before merging (here and here)


Fix CI for patches by applying the new standardrb rules

What are you trying to accomplish?
CI is failing on lint for everyone, regardless of changes. This gets through that in a small, temporary way.

While working on supporting splatted keyword
args I discovered that the linter was failing me on changes I didn't make.
When I ran standardrb locally, it was quite content, so I was a bit confused. Then I read [.github/workflows/lint.yml] and realized that view_component runs a bundle update prior to running standard; which bumps the standardrb version and the corresponding rubocop set.
This was introduced by @camertron in
e7eec9869fc13e401401c687573a98f1b0ed57a8 7+ months ago to fix an error in CI.
What approach did you choose and why?
It's unclear to me why bundle install was not working, so I decided that rather than swapping that back I would trust @camertron's instincts and roll-forward by updating the Gemfile.lock so folks' local matches CI (for now), and applying the changes it recommended.
I am not including a change to the Changelog because this seems internal and unnecessary to communicate to package consumers.
Anything you want to highlight for special attention from reviewers?
I'd be down to just try bundle install rather than bundle update if that seems like a good idea to other folks with more context.

It's unclear to me why bundle install was not working

I changed it to bundle update exactly because of situations like this. Since we have a Gemfile.lock checked into version control, we miss testing against new dependency releases. Running bundle update in CI ensures we test against newer releases. The other option would be to stop version tracking Gemfile.lock, but that's considered good practice these days.

I am not including a change to the Changelog because this seems internal and unnecessary to communicate to package consumers.

I get that, but we'd like every change to have an accompanying changelog entry.

This PR should fix the PVC tests: https://github.com/ViewComponent/view_component/pull/1579

Since we have a Gemfile.lock checked into version control, we miss testing against new dependency releases

If possible, we should omit tooling like standardrb from being updated like that, to prevent the case of it introducing "breaking changes".