Resizing the window should keep the prompt at the bottom of the window

Windows Terminal version
<IP_ADDRESS>.0
Windows build number
10.0.19045.4239
Other Software
No response
Steps to reproduce

open a Windows Terminal
fill the buffer so that the prompt appears at the bottom of the window
resize the window so that it's smaller than before
enlarge the window

Expected Behavior
The prompt should stay at the bottom of the window.
Actual Behavior
The prompt has moved several lines up (scroll position appears to be correct: at the bottom of the window, but the text/prompt's position is not correct). Also notice one of the previous prompt that incorrectly appears on the top right, but I guess it should go in another issue.
https://github.com/microsoft/terminal/assets/199648/680ee2d6-eefe-46e1-87b8-3616571cfe1a
The expected behavior is the one I saw on popular terminal apps on macOS and Linux.
For example:
iTerm on mac
https://github.com/microsoft/terminal/assets/199648/6dcf7daa-b07d-43b7-b77d-9905a3ca6b3d
GNOME Terminal on Debian
https://github.com/microsoft/terminal/assets/199648/06862b6e-70fb-4337-a8da-aad169115199

Thanks for filing. We do this for consistency with the Windows Console. We have an idea of how to approach this, but it's actually a pretty big architectural change. This should definitely be linked up to #15065 though, since ConPTY is involved


need to be able to specify full path to ffmpeg

The path to ffmpeg in processor.js is hard coded to ffmpeg. When running node,js from a cron job on a shared server, ffmpeg may not be in a path available to cron and so it can not be run. For example the path to ffmpeg on my shared server is /usr/local/bin/ffmpeg. When the cron job runs, node cannot find ffmpeg because it is not in the path used by cron. I do not have root access to add ffmpeg to the PATH used by cron.
If I replace 'ffmpeg' with '/usr/local/bin/ffmpeg' in processor.js it works.
I would like a method in the api to specify the location of ffmpeg so I don't have to modify processor.js.
Thanks,
Dale

You should actually be able to set the path to ffmpeg by using the environment variable FFMPEG_PATH (see line 278 in lib/processor.js)


[Bug] New-DbaAzAccessToken - Non-Existent switch in E.g for Connect-DbaInstance when using AzAccessToken.

Environmental information

LCID             Name             DisplayName
----             ----             -----------
1033             en-US            English (United States)

SQL Server:

Not Relevant

Not Relevant

Report

Host used

[x] powershell.exe
[x] ISE
[ ] VS Code
[ ] Other (please specify)

If anything other than powershell.exe was used, please confirm that you can duplicate the issue with powershell.exe

[ ] Still buggy in powershell.exe

Errors Received

C:\Users\john.doe> Connect-DbaInstance -SqlInstance myserver.database.windows.net -Database mydb -AccessToken     Connect-DbaInstance : A parameter cannot be found that matches parameter name 'AccessToken'.
At line:1 char:79
+ ... SqlInstance myserver.database.windows.net -Database mydb -AccessToken
+                                                              ~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Connect-DbaInstance], ParameterBindingException
    + FullyQualifiedErrorId : NamedParameterNotFound,Connect-DbaInstance

Steps to Reproduce

Install-Module dbatools -RequiredVersion 1.0.23
Try running the below command"

C:\Users\john.doe> Connect-DbaInstance -SqlInstance myserver.database.windows.net -Database mydb -AccessToken
Expected Behavior

I would be prompted that AccessToken needs a value.
Actual Behavior

Powershell returned an error stating that the -AccessToken switch does not exist.
Additional Information
The latest version of Connect-DbaInstance at the master branch here indeed does not have a param/switch for AccessToken.
Yet, the following example here for New-DbaAzAccessToken shows what should supposedly be a parameter for AccessToken.

@potatoqualitee Are any updates on this item as I've noticed that the automated bot has marked it stale and will eventually change it to closed.

What is the issue again?
The AccessToken parameter was removed from Connect-DbaInstance so we can update the example in New-DbaAzAccessToken.


Disambiguation from Delivery Status Notification (=DSN too)

See https://en.wikipedia.org/wiki/Bounce_message

Thanks for your pull request! We love contributions.
However, this repository is what we call a "subtree split": a read-only copy of one directory of the main enqueue-dev repository. It is used by Composer to allow developers to depend on specific Enqueue package.
If you want to contribute, you should instead open a pull request on the main repository:
https://github.com/php-enqueue/enqueue-dev
Read the contribution guide
https://github.com/php-enqueue/enqueue-dev/blob/master/docs/contribution.md
Thank you for your contribution!


Added the delete tests functionality without testing it.

This is great! Eventually we should check for a spec directory too.


[models] Pretrained param loading design

There is currently no clear design for model checkpoint loading. Here is a proposal:

[ ] Data integrity: add the first 8 character of the SHA256 hash at the end of file name. Use this to check integrity upon download
[ ] Hosting: all pretrained models should be hosted on Github
[ ] File naming: each file should follow the naming convention architecture_imgsize-hash.pth (example: resnet50_224-64cb5b95.pth)
[ ] Architecture module: small suggestion https://github.com/frgfm/Holocron/blob/master/holocron/models/repvgg.py since this library is already in the dependencies

We have one model for now (rexnet1_0x_acp_2e017f83.pth), I can change the name to add the image size https://github.com/pyronear/pyro-vision/releases.
In your name format there is no room for an extra comment ? for the model on the repo I added acp for adaptiveConcatPooling because it has a custom head.

Mmmmh I suggest the extra comment to be put in architecture in the proposed naming so in your example it would yield:
rexnet1_0x_acp_224_2e017f83 I guess?

ok perfect

Closed by #86


Expand Propositional Logic Stub

This is a simple addition to this stub that briefly explains Modus Ponens.

[x ] I have read freeCodeCamp's contribution guidelines.
[x ] My pull request has a descriptive title (not a vague title like Update index.md)
[x ] My pull request targets the master branch of freeCodeCamp.
[x ] None of my changes are plagiarized from another source without proper attribution.
[x ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@GreatDeveloper66 👍 LGTM! 🙏


CORS issue

The engine is returning CORS issue.
In JavaScript you cannot access a resource from another server unless they enable CORS. Now because we don't want to break security, the call needs to be made server-to-server
We'll think on adding PHP into play

we moved from JS to PHP
no CORS issue
closing the bug

this issue has been fixed


Add ability to lookup past correct answers

Save them to a file. Load upon startup, then check if the answer is known before using other methods.

Solved in 498f7dc  using Azure functions rather than local storage/lookup.


Update 2017-08-29-cloud-platform-release-notes.md

corrected typos

@MattSchwabby i'd like to see this text on 'capacity' fixed.  I don't want to say we ran out of capacity as that would infer we a) are getting more possibly and b) we don't know how to run capacity mgmt and are not smart
@srveit I want Matt to weigh in on this before we push this live as it makes it look bad in public


Releasing 8.1.0

Just a meta-bug to track regression / wish list etc before 8.1.0 release

cc @amyspark @emmenlau and @JohanMabille

Thumbs up from my side, I (personally) do not have anything urgent in the pipeline. However I see there are a number of open issues regarding arm, Android and/or Apple M1 support. I can think that many of them are related in some form? Is that something that would be easy to address or nothing for the 8.1.0 release?

:+1:  from my side. Awaiting checks from our Mac and Android devs.

Heads up, I've got a report that AppleClang doesn't completely like the Arm optimizations I made in #708 and #710. I'm preparing the MR and the changes to CI to prevent it from happening again.

swizzle fixed, I think we can release when the nearbyint_as_int is fixed.

@JohanMabille I'm working on permutes/shuffles/interleaves. It'll take a while, so I'll leave it for the next release.

ok.

Thanks a lot guys, @JohanMabille two thumbs up for the release from my side!

xsimd 8.1.0 is out!


[doc] Add readme-zh for Chinese users

Thank you for the efforts!
I will hold this PR for a while as we may plan to have major updates to this open-source repo, so the readme.md is subject to change. I will leave your PR open so that people can refer to it if needed.


Update mendix-profile.md

Added a section to describe the create account from profile flow. Also updated the change password and forget account actions.

 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.


deselectAllDates with triggerSelectionDelegate: false and selectDates with triggerSelection false and keepSelection false not working after upgrading to Xcode 9 and iOS 11

I am using v7.1.2 of JTAppleCalendar

Yes, I'm using the latest.

First off, thank you so much for all the work you put into this library! I love it and so do our customers!
NOTE: this WAS working before. Upon upgrading to Xcode 9/iOS 11, this issue now happens where
deselectAllDates(triggerSelectionDelegate: false)
is not working. Also,
selectDates(from, to, triggerSelectionDelegate: false, keepSelectionIfMultiSelectionAllowed: false)
doesn't seem to work either. Let me try and explain my implementation a bit to better show you the issue.

Upon startup, the last 7 days are selected programmatically. Notice there's two synced textfields at the top showing from and to dates. This is working fine.

If I select a date outside the initial range, a new range is made with from and to equal to each other (this is the start of a new range). Notice that the synced textfields are correct, but Nov. 1 through Nov. 7 did not get deselected. This is the first issue.

The second issue is that selectDates isn't selecting a range of dates like it used to. Notice in this screenshot that we expect Mon, Oct 09 through Fri, Oct 13 to be the range, Oct 10, 11, and 12 are not selected.
Here is a link to my gist including relevant code:
https://gist.github.com/cazares/d8f8da366e0fe803a15f5bcdb865a9eb
I've been working on this all day and I can't seem to get anywhere. Any help is greatly appreciated!

hey i think the link to you code gist is not working. Got the link?

Also, did you implement a shouldSelect or shouldDeselect function?
This now gets called when you do a selection or deselection.
?

Try now. Also, no I don't implement shouldSelect or shouldDeselect, should I?

@cazares ok i'll look at your code more in detail after work.
You do not have to implement shouldSelect or shouldDeselect. I just asked to further determine the source of your issue.
Since you updated to the latest version. Did you implement the willDisplayItem function?
The one must be implemented according to this -> https://github.com/patchthecode/JTAppleCalendar/issues/553

This one?
func calendar(_ calendar: JTAppleCalendarView, willDisplay cell: JTAppleCell, forItemAt date: Date, cellState: CellState, indexPath: IndexPath)
Yes, but it's an empty implementation.

Hey I fixed the problem by doing this in willDisplay cell:
cell.isSelected = isInsideDateRange(date)
Thanks for pointing me in the right direction!

@cazares one thing. try to use the cellState.isSelected instead of cell.isSelected
on that same link -> https://github.com/patchthecode/JTAppleCalendar/issues/553 on problem # 2, i explained why.
I am working on an update soon that will allow developers to use the isSelected directly on a cell. But I have not coded it yet. I'll finish it soon.

OK. wait, i thought you were just doing a simple check to see if a cell was selected or not.
I might have been mistaken. What are you doing with the isSelected of a cell? Are you trying to select the cell by setting cell.isSelected = true ?
I am not clear what you are doing.

Yes I am just looking for different ways to deselect and select a range of cells other than deselectAllDates(triggSelectionDelegate: false) and selecctDates(from, to, triggerSelectionDelegate: false, keepSelectionIfMultiSelectionAllowed: false). These two functions were working before, but now they are not. Seems like keepSelectionIfMultiSelectionAllowed: false is not being respected.

is it possible you can join chat here? https://gitter.im/patchthecode/JTAppleCalendar
typing here is too slow.
But yes,
deselectAllDates(triggSelectionDelegate: false)

and
selectDates(from, to, triggerSelectionDelegate: false, keepSelectionIfMultiSelectionAllowed: false)

Should work. If this does not work, then I need to fix something. Let's not do a work around for something as important as this. I fix issues no matter how small they seem. And this sounds like a huge issue.

Selecting dates work by using any of the selectDate functions
Deselection works by either calling deselectAllDates or (if youre in multiselect mode) by calling a selectDate function again.

Yes I will join shortly.

I know we have a chat later, but I just wanted to mention that I found out that reverting to any version of JTAppleCalendar between 7.0.0 and 7.0.6 all work. Version 7.1.0 is the first version where my functionality breaks, all the way up to 7.1.3 (all 7.1 versions are broken).

Closing issue until user responds.
I could not reproduce this in version 7.1+


The camera that uses the 28181 protocol cannot connect to SRS after restarting.

I'm having some issues with my camera. It lost power and when I tried to turn it back on, it seems like it can't connect to SRS. I need to change its UID before it can reconnect.
TRANS_BY_GPT4

你的问题已经在Issues中存在，属于重复的问题，该Issue会被删除，请在Issues中搜索。#2716


⚠ St. Lawrence Global Observatory CKAN Sitemap has degraded performance

In d556765, St. Lawrence Global Observatory CKAN Sitemap (https://catalogue.ogsl.ca/sitemap/sitemap-1.xml) experienced degraded performance:

HTTP code: 200
Response time: 13555 ms

Resolved: St. Lawrence Global Observatory CKAN Sitemap performance has improved in c8cdb5d after 34 minutes.


Permission Denied Error for solderlog on any action

Solder Repo Hash:
Operating System and version:
Fedora 30 (Server)
PHP version:
php 7.3.7
using workaround; error_reporting(E_ALL ^ E_DEPRECATED) at top of app.php

Composer version:
Composer 1.9.0

Server type:
LEMP
Type of database:
SQLite 3

Type of hosting:
Personal Shared

Link to the affected install's public url:
https://solder.binaryaura.net

https://repo.binaryaura.net/solder

After any action settings, adding mods, modpacks, etc I get the following error:
Error in exception handler: The stream or file "/var/www/solder.binaryaura.net/TechnicSolder/app/storage/logs/solderlog-2019-08-09.txt" could not be opened: failed to open stream: Permission denied in /var/www/solder.binaryaura.net/TechnicSolder/bootstrap/compiled.php:7173

This is similar to issue #655, I went ahead and made this issue because I'm using LEMP and that thread has gone stale and still open.
I have ran the check.php as indicated in that thread, but it returned nginx, as expected.
I attempted making ../app/storage/logs 777
and making the folder it was referring to in the error with 777 as well,
neither fixed the error.
This absolutely baffles me: "Permission denied" with 775 and 777
Nginx:
nginx.conf: https://pastebin.com/g49wTnhj
php.conf: https://pastebin.com/RtA1derF
solder.binaryaura.net: https://pastebin.com/c8fpgQLs
repo.binaryaura.net: https://pastebin.com/8LngdBsw
php:
www.conf: https://pastebin.com/UMWZHXHp
summary: LEMP tutorial setup
runs under nginx
Solder:
app.php: https://pastebin.com/3gXZqshx
database.php: https://pastebin.com/XjK1VhdK
solder.php: https://pastebin.com/5eXrBNi7
summary: repo: https://repo.binaryaura.net/solder
solder: https://solder.binaryaura.net
sqlite 3
defaults
Permissions:
project directory: solder-www-perm.txt
repo directory: repo-www-perm.txt
summary: 775 and nginx:web everywhere
nginx and jadunker is in web
Any help here would be appreciated.

I inserted debug_print_backtrace() on line 7173 and got the attache backtrace. The first line says: General error: 8 attempt to write a readonly database in /var/www/solder.binaryaura.net/TechnicSolder/vendor/laravel/framework/src/Illuminate/Database/Connection.php:391

After a bit of research I found this: https://stackoverflow.com/questions/3319112/sqlite-error-attempt-to-write-a-readonly-database-during-insert
So I ran: setenforce 0 and tried again and it worked.
I would prefer not to leave it off but, I'm not too familiar with selinux though.

Make sure the app/database/production.sqlite has the right filesystem permissions.

It has 775
I believe it is a SELinux issue

Okay I'm having 2 SELinux issues. The first is the log. This is what shows on #655 as well. The solution to it was to run
sudo chcon -Rv -t httpd_sys_rw_content_t /var/www/solder.binaryaura.net/TechnicSolder/app/storage

Cheers, glad to see it's fixed now.

Second problem was very similar. Fixed via
sudo chcon -Rv -t httpd_sys_rw_content_t /var/www/solder.binaryaura.net/TechnicSolder/app/database

For anyone also having similar issues, this site helped me considerably: https://serversforhackers.com/c/battling-selinux-cast

When bringing up the Build Management Screen I get:
[2019-08-10 16:58:58] production.ERROR: Curl error for https://www.technicpack.net/api/minecraft:  [] []
[2019-08-10 16:58:58] production.ERROR: Curl error for https://launchermeta.mojang.com/mc/game/version_manifest.json:  [] []

Both of the endpoints are working for me, as expected. Is there something preventing your server from successfully making the HTTPS request?

Of coarse...
SELinux again
selinux-strikes again..txt

I guess this issue is solved now, then?

Yeah. sudo setsebool -P httpd_can_network_connect 1 Sorry for making issues like this, but the feedback helps.

Also the irc.synirc.net isn't responding

SynIRC isn't ours. Maybe it's yet another SELinux issue?

Doubtful, I'm browsing on a windows. ... I just throw-up a little in my mouth.


Add collection of out of the box themes

Built on changes from #13
Todo:

[X] Maybe add link to studiostyl.es so developers can explore more themes
[X] Fix up styles so they play nice with the new Editor Scheme support in VS 2019. Likely need to import with VS2017 scheme applied and export fresh.

@ryzngard You should pull this branch and try it out.


jsx-uses-vars: Check if a variable is used as jsx

Clear and concise description of the problem
If I use the no-unused-vars rule, when I import a react component and use it, eslint does not accurately detect that I use it in jsx. So I had to solve this problem by installing eslint-plugin-react and configuring react/jsx-uses-vars. I hope stylistic can adapt to this rule as soon as possible. Thanks

Suggested solution
Learn from eslint-plugin-react and support this rule
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Contributes

[x] If this feature request is accepted, I am willing to submit a PR to fix this issue

Tbh, I think it's not a stylistic rule but a jsx-related rule.
So eslint-plugin-react or @eslint-react/eslint-plugin is a better choice.


feat: Added Toast Notification to the whole webapp Successfully Issue 103

Pull Request Resolves [#103 ]
Title: Added Toast Notification to the whole webapp
Description

Used react-hot-toast npm library throughout the app.
First  is init in App.tsx.
With toast.success/error the operation is performed.

Related Issues
Fixes: #103
Changes Made
New feature: Added Toast Notification with react-hot-toast.
Screenshots

I certify that I have carried out the relevant code of conduct and provided the requisite screenshot for validation by submitting this pull request.
Thank You for this contribution.

did you also push changes of the like/dislike functionality of your other PR

No, i created two branch for both the issues #103 and #87 i don't know why it is showing commit's above ?

Ya i think the above pr ha both the functinality toast + like/dislike .

You can merge it without conflicts

@VaibhavArora314  Done 👍

@VaibhavArora314 finally it's done :)


Fetch hello message from server.

Fetch a 'Hello Betty!' message from the data server and adds it to the DOM.
demo = https://bettyv-step-2020.appspot.com/

Could you push the changes to the demo please?

Demo has been updated!

Can you try to wrap the text to fit the screen? It's bleeding out in mobile

(To test in mobile view, go to Chrome "view" menu > Developer > Developer Tools

Can you please push the changes to the demo site so I can verify the fix?

It should now work on the demo for mobile, but it now looks different on a desktop-screen let me know if you want that changed back.


Improve Getting started with Qiskit tutorial if needed

Part of #1518

Can be considered done when these PRs are merged

[ ] https://github.com/Qiskit/qiskit-tutorials/pull/1342
[ ] https://github.com/Qiskit/qiskit-tutorials/pull/1354


IPFS Textbook

I want to have a working textbook on what IPFS is, and how crypto works for beginners and non-technical people. Should be fun!
https://github.com/RichardLitt/ipfs-textbook

Thanks for joining us! Closing until next year's run. :)


How to Add Any Extra Character on Labels, like Percentage (%)

I want to put additional %, or any additional character on the  speedometer.
Means - in value, I can pass any numeric value and that's good.
Now, I want to display that like this - 33%
Is there any way to do that ?

I opened a Pull Request that will solve your issue, by passing the prop value as a function like: (value) => '${value}%'.
I hope that helps ^^

no this is not working

Try following style
labelStyle={{ height: 0, width: 0 }}
OR
labelWrapperStyle={{ height: 0, width: 0 }}
and add your own custom  text component


Allow tagging of version

It would be nice to have a particular version tagged similar to git. It doesn't have to be unique.
Then add revertByTag() method to repository class

great idea!


Sonoff SNZB-04P error with period of time open or closed

Hi, The Sonoff SNZB-04P doesn't work with an open or closed time period. On ewelink, I created a scene that notifies you when it is open for x minutes. Then the sensor opens and the trigger starts. However, if you close the sensor, it continues counting as if it were open. It does not cancel the open status when closing, so the scene says that the sensor is open even when it has already closed.
Iam using ewelink 5.8.0 and SNZB-04P 2.2.0 if is relevant.
Thank you

This is wrong place for ewelink app and scenes support.


[AzCopyV10][StgExp] Cannot copy file from sharesnapshot to current share

Sharesnapshot can be copied to current share with this small fix.

We absolutely should have a test case, @nakulkar-msft.

Is there any linked issue with this PR?

Is there any linked issue with this PR?

@mohsha-msft I believe that this is the issue: https://github.com/Azure/azure-storage-azcopy/issues/964

This change warrants a testcase. Check if you can add one.

So this scenario warrants an e2e test but is not currently supported. Instead, I've manually tested going from (a) ShareSnapshot to Current Share and (b) ShareSnapshot to itself, ensured that snapshots are immutable


Dismiss barHow to dismiss bar when changing tab?

I want to show a bar in tabs layout. How to dismiss bar when changing tab? (jetpack compose)

Hey there. If you're using Tabs together with the Pager from the accompanist library, you can react to page changes like this:
LaunchedEffect(pagerState) {
    // Collect from the pager state a snapshotFlow reading the currentPage
    snapshotFlow { pagerState.currentPage }.collect {
        message = null
    }
}

This will get called regardless if the page is changed by swiping the pager or by selecting a tab.
There, you can set the message to null, that will dismiss the InfoBar.

Thank you!


Experimenting with safelist of branches for Travis CI.

I'm trying to get Travis CI to only do builds on Pull Requests and on pushes to master.
The pushes to master are needed so that I can have Heroku wait for CI to pass checks before deploying to production.

Ok, upon Pull Request creation it looks like only one build was triggered in Travis CI.

And that single check passed, so I can now Merge the pull request to master.
Since Travis is set to start builds on pushed branches, and master is on the safelist, that should trigger a build on master.

Yup, it did trigger the build on master, unlike on the dev branch I used to make the change to .travis.yml
Next step is to see if a pass on that build results in a deployment to prod.

build on master passed

Yup, it deployed.
Success! No more double builds during PRs, but still automatic build/deploy on master!


Flaky: apache_beam.runners.portability.fn_api_runner.fn_runner_test.FnApiRunnerTestWithGrpcAndMultiWorkers

The apache_beam.runners.portability.fn_api_runner.fn_runner_test.FnApiRunnerTestWithGrpcAndMultiWorkers tests are flaky and causing precommit failures that seem similar.
test_pardo_windowed_side_inputs : https://ci-beam.apache.org/job/beam_PreCommit_Python_Cron/4417/console

23:32:35 Exception in thread read_grpc_client_inputs:
23:32:35 Traceback (most recent call last):
23:32:35
  File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
23:32:35     self.run()
23:32:35
  File "/usr/lib/python3.8/threading.py", line 870, in run
23:32:35     self._target(*self._args, **self._kwargs)
23:32:35
  File "/home/jenkins/jenkins-slave/workspace/beam_PreCommit_Python_Cron/src/sdks/python/test-suites/tox/py38/build/srcs/sdks/python/apache_beam/runners/worker/data_plane.py",
line 587, in <lambda>
23:32:35     target=lambda: self._read_inputs(elements_iterator),
23:32:35
 File "/home/jenkins/jenkins-slave/workspace/beam_PreCommit_Python_Cron/src/sdks/python/test-suites/tox/py38/build/srcs/sdks/python/apache_beam/runners/worker/data_plane.py",
line 570, in _read_inputs
23:32:35     for elements in elements_iterator:
23:32:35   File "/home/jenkins/jenkins-slave/workspace/beam_PreCommit_Python_Cron/src/sdks/python/test-suites/tox/py38/build/srcs/sdks/python/target/.tox-py38-cython/py38-cython/lib/python3.8/site-packages/grpc/_channel.py",
line 426, in __next__
23:32:35     return self._next()
23:32:35   File "/home/jenkins/jenkins-slave/workspace/beam_PreCommit_Python_Cron/src/sdks/python/test-suites/tox/py38/build/srcs/sdks/python/target/.tox-py38-cython/py38-cython/lib/python3.8/site-packages/grpc/_channel.py",
line 826, in _next
23:32:35     raise self
23:32:35 grpc._channel._MultiThreadedRendezvous: <_MultiThreadedRendezvous
of RPC that terminated with:
23:32:35 	status = StatusCode.UNAVAILABLE
23:32:35 	details = "Broken
pipe"
23:32:35 	debug_error_string = "{"created":"@1626071403.252458842","description":"Error received
from peer ipv4:<IP_ADDRESS>:37459","file":"src/core/lib/surface/call.cc","file_line":1066,"grpc_message":"Broken
pipe","grpc_status":14}"
23:32:35 >
23:32:35 Traceback (most recent call last):
23:32:35   File "/home/jenkins/jenkins-slave/workspace/beam_PreCommit_Python_Cron/src/sdks/python/test-suites/tox/py38/build/srcs/sdks/python/apache_beam/runners/worker/data_plane.py",
line 459, in input_elements
23:32:35     element = received.get(timeout=1)
23:32:35   File "/usr/lib/python3.8/queue.py",
line 178, in get
23:32:35     raise Empty
23:32:35 _queue.Empty

test_pack_combiners :  https://ci-beam.apache.org/job/beam_PreCommit_Python_Cron/4415/consoleFull

11:41:14 Exception ignored in: <object repr() failed>
11:41:14 Traceback (most recent call last):
11:41:14
  File "/home/jenkins/jenkins-slave/workspace/beam_PreCommit_Python_Cron/src/sdks/python/test-suites/tox/py36/build/srcs/sdks/python/target/.tox-py36-cython/py36-cython/lib/python3.6/site-packages/grpc/_channel.py",
line 444, in __del__
11:41:14     with self._state.condition:
11:41:14 AttributeError: '_MultiThreadedRendezvous'
object has no attribute '_state'
11:41:14 Traceback (most recent call last):
11:41:14   File "apache_beam/runners/common.py",
line 1223, in apache_beam.runners.common.DoFnRunner.process
11:41:14     return self.do_fn_invoker.invoke_process(windowed_value)
11:41:14
  File "apache_beam/runners/common.py", line 752, in apache_beam.runners.common.PerWindowInvoker.invoke_process
11:41:14
    self._invoke_process_per_window(
11:41:14   File "apache_beam/runners/common.py", line 816, in
apache_beam.runners.common.PerWindowInvoker._invoke_process_per_window
11:41:14     [si[global_window]
for si in self.side_inputs]))
11:41:14   File "/home/jenkins/jenkins-slave/workspace/beam_PreCommit_Python_Cron/src/sdks/python/test-suites/tox/py36/build/srcs/sdks/python/apache_beam/runners/worker/bundle_processor.py",
line 427, in __getitem__
11:41:14     self._cache[target_window] = self._side_input_data.view_fn(raw_view)
11:41:14
  File "/home/jenkins/jenkins-slave/workspace/beam_PreCommit_Python_Cron/src/sdks/python/test-suites/tox/py36/build/srcs/sdks/python/apache_beam/runners/worker/bundle_processor.py",
line 353, in __iter__
11:41:14     self._state_handler.blocking_get(self._state_key, self._coder_impl))
11:41:14
  File "/home/jenkins/jenkins-slave/workspace/beam_PreCommit_Python_Cron/src/sdks/python/test-suites/tox/py36/build/srcs/sdks/python/apache_beam/runners/worker/sdk_worker.py",
line 1184, in blocking_get
11:41:14     self._partially_cached_iterable(state_key, coder))
11:41:14
  File "/home/jenkins/jenkins-slave/workspace/beam_PreCommit_Python_Cron/src/sdks/python/test-suites/tox/py36/build/srcs/sdks/python/apache_beam/runners/worker/sdk_worker.py",
line 1290, in _partially_cached_iterable
11:41:14     data, continuation_token = self._underlying.get_raw(state_key,
None)
11:41:14   File "/home/jenkins/jenkins-slave/workspace/beam_PreCommit_Python_Cron/src/sdks/python/test-suites/tox/py36/build/srcs/sdks/python/apache_beam/runners/worker/sdk_worker.py",
line 1057, in get_raw
11:41:14     continuation_token=continuation_token)))
11:41:14   File "/home/jenkins/jenkins-slave/workspace/beam_PreCommit_Python_Cron/src/sdks/python/test-suites/tox/py36/build/srcs/sdks/python/apache_beam/runners/worker/sdk_worker.py",
line 1095, in _blocking_request
11:41:14     raise t(v).with_traceback(tb)
11:41:14 TypeError: __init__()
missing 3 required positional arguments: 'call', 'response_deserializer', and 'deadline'

Imported from Jira BEAM-12603. Original Jira may contain additional context.
Reported by: tysonjh.

There have been several fixes (see Jira). last one: https://github.com/apache/beam/pull/17537/files
However this test is still flaky. Seeing a different error this time:
Error Message
RuntimeError: Traceback (most recent call last):
  File "/home/jenkins/jenkins-slave/workspace/beam_PreCommit_Python_Commit/src/sdks/python/test-suites/tox/py38/build/srcs/sdks/python/apache_beam/runners/worker/sdk_worker.py", line 287, in _execute
    response = task()
  File "/home/jenkins/jenkins-slave/workspace/beam_PreCommit_Python_Commit/src/sdks/python/test-suites/tox/py38/build/srcs/sdks/python/apache_beam/runners/worker/sdk_worker.py", line 360, in <lambda>
    lambda: self.create_worker().do_instruction(request), request)
  File "/home/jenkins/jenkins-slave/workspace/beam_PreCommit_Python_Commit/src/sdks/python/test-suites/tox/py38/build/srcs/sdks/python/apache_beam/runners/worker/sdk_worker.py", line 596, in do_instruction
    return getattr(self, request_type)(
  File "/home/jenkins/jenkins-slave/workspace/beam_PreCommit_Python_Commit/src/sdks/python/test-suites/tox/py38/build/srcs/sdks/python/apache_beam/runners/worker/sdk_worker.py", line 634, in process_bundle
    bundle_processor.process_bundle(instruction_id))
  File "/home/jenkins/jenkins-slave/workspace/beam_PreCommit_Python_Commit/src/sdks/python/test-suites/tox/py38/build/srcs/sdks/python/apache_beam/runners/worker/bundle_processor.py", line 1003, in process_bundle
    input_op_by_transform_id[element.transform_id].process_encoded(
  File "/home/jenkins/jenkins-slave/workspace/beam_PreCommit_Python_Commit/src/sdks/python/test-suites/tox/py38/build/srcs/sdks/python/apache_beam/runners/worker/bundle_processor.py", line 225, in process_encoded
    decoded_value = self.windowed_coder_impl.decode_from_stream(
  File "apache_beam/coders/coder_impl.py", line 1446, in apache_beam.coders.coder_impl.WindowedValueCoderImpl.decode_from_stream
    def decode_from_stream(self, in_stream, nested):
  File "apache_beam/coders/coder_impl.py", line 1464, in apache_beam.coders.coder_impl.WindowedValueCoderImpl.decode_from_stream
    pane_info = self._pane_info_coder.decode_from_stream(in_stream, True)
  File "apache_beam/coders/coder_impl.py", line 1383, in apache_beam.coders.coder_impl.PaneInfoCoderImpl.decode_from_stream
    raise NotImplementedError('Invalid PaneInfoEncoding: %s' % encoding_type)
NotImplementedError: Invalid PaneInfoEncoding: 6

I'm having lots of trouble reproducing this failure...

but I'm trying to : )

may be one of those tests that fail on jenkins only (when run together w/ a bunch of tests)... i saw it today in a linked issue

i got it to reproduce a couple of times on my machine in non-cython. I'm adding logging to see what happens

nice, did you run a single test?

I got it to repro by runnig the full class of tests (FnApiRunnerTestWithGrpcAndMultiWorkers)

fwiw this is the error stack that I'm able to reproduce:
======================================================================
ERROR: test_pardo_large_input (apache_beam.runners.portability.fn_api_runner.fn_runner_test.FnApiRunnerTestWithGrpcAndMultiWorkers)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/pabloem/codes/pybeam/sdks/python/apache_beam/runners/portability/fn_api_runner/fn_runner_test.py", line 379, in test_pardo_large_input
    assert_that(res, equal_to([(i * 2) + 3 for i in range(5000)]))
  File "/home/pabloem/codes/pybeam/sdks/python/apache_beam/pipeline.py", line 597, in __exit__
    self.result = self.run()
  File "/home/pabloem/codes/pybeam/sdks/python/apache_beam/pipeline.py", line 574, in run
    return self.runner.run_pipeline(self, self._options)
  File "/home/pabloem/codes/pybeam/sdks/python/apache_beam/runners/portability/fn_api_runner/fn_runner.py", line 199, in run_pipeline
    self._latest_run_result = self.run_via_runner_api(
  File "/home/pabloem/codes/pybeam/sdks/python/apache_beam/runners/portability/fn_api_runner/fn_runner.py", line 212, in run_via_runner_api
    return self.run_stages(stage_context, stages)
  File "/home/pabloem/codes/pybeam/sdks/python/apache_beam/runners/portability/fn_api_runner/fn_runner.py", line 442, in run_stages
    bundle_results = self._execute_bundle(
  File "/home/pabloem/codes/pybeam/sdks/python/apache_beam/runners/portability/fn_api_runner/fn_runner.py", line 770, in _execute_bundle
    self._run_bundle(
  File "/home/pabloem/codes/pybeam/sdks/python/apache_beam/runners/portability/fn_api_runner/fn_runner.py", line 999, in _run_bundle
    result, splits = bundle_manager.process_bundle(
  File "/home/pabloem/codes/pybeam/sdks/python/apache_beam/runners/portability/fn_api_runner/fn_runner.py", line 1415, in process_bundle
    for result, split_result in executor.map(execute, zip(part_inputs,  # pylint: disable=bad-option-value
  File "/home/pabloem/.pyenv/versions/3.8.9/lib/python3.8/concurrent/futures/_base.py", line 619, in result_iterator
    yield fs.pop().result()
  File "/home/pabloem/.pyenv/versions/3.8.9/lib/python3.8/concurrent/futures/_base.py", line 444, in result
    return self.__get_result()
  File "/home/pabloem/.pyenv/versions/3.8.9/lib/python3.8/concurrent/futures/_base.py", line 389, in __get_result
    raise self._exception
  File "/home/pabloem/codes/pybeam/sdks/python/apache_beam/utils/thread_pool_executor.py", line 37, in run
    self._future.set_result(self._fn(*self._fn_args, **self._fn_kwargs))
  File "/home/pabloem/codes/pybeam/sdks/python/apache_beam/runners/portability/fn_api_runner/fn_runner.py", line 1407, in execute
    return bundle_manager.process_bundle(
  File "/home/pabloem/codes/pybeam/sdks/python/apache_beam/runners/portability/fn_api_runner/fn_runner.py", line 1348, in process_bundle
    raise RuntimeError(result.error)
RuntimeError: Traceback (most recent call last):
  File "/home/pabloem/codes/pybeam/sdks/python/apache_beam/runners/worker/sdk_worker.py", line 287, in _execute
    response = task()
  File "/home/pabloem/codes/pybeam/sdks/python/apache_beam/runners/worker/sdk_worker.py", line 360, in <lambda>
    lambda: self.create_worker().do_instruction(request), request)
  File "/home/pabloem/codes/pybeam/sdks/python/apache_beam/runners/worker/sdk_worker.py", line 596, in do_instruction
    return getattr(self, request_type)(
  File "/home/pabloem/codes/pybeam/sdks/python/apache_beam/runners/worker/sdk_worker.py", line 634, in process_bundle
    bundle_processor.process_bundle(instruction_id))
  File "/home/pabloem/codes/pybeam/sdks/python/apache_beam/runners/worker/bundle_processor.py", line 1003, in process_bundle
    input_op_by_transform_id[element.transform_id].process_encoded(
  File "/home/pabloem/codes/pybeam/sdks/python/apache_beam/runners/worker/bundle_processor.py", line 225, in process_encoded
    decoded_value = self.windowed_coder_impl.decode_from_stream(
  File "/home/pabloem/codes/pybeam/sdks/python/apache_beam/coders/coder_impl.py", line 1465, in decode_from_stream
    value = self._value_coder.decode_from_stream(in_stream, nested)
  File "/home/pabloem/codes/pybeam/sdks/python/apache_beam/coders/coder_impl.py", line 1008, in decode_from_stream
    return self._construct_from_components([
  File "/home/pabloem/codes/pybeam/sdks/python/apache_beam/coders/coder_impl.py", line 1009, in <listcomp>
    c.decode_from_stream(
  File "/home/pabloem/codes/pybeam/sdks/python/apache_beam/coders/coder_impl.py", line 1557, in decode_from_stream
    return self._value_coder.decode(in_stream.read(value_length))
  File "/home/pabloem/codes/pybeam/sdks/python/apache_beam/coders/coder_impl.py", line 240, in decode
    return self.decode_from_stream(create_InputStream(encoded), False)
  File "/home/pabloem/codes/pybeam/sdks/python/apache_beam/coders/coder_impl.py", line 535, in decode_from_stream
    t = stream.read_byte()
  File "/home/pabloem/codes/pybeam/sdks/python/apache_beam/coders/slow_stream.py", line 145, in read_byte
    return self.data[self.pos - 1]
IndexError: index out of range

From latest repro:
Data position is  620095
Step with error is  NameContext({'step_name': 'assert_that/Group/CoGroupByKeyImpl/Flatten/Read', 'transform_id': 'assert_that/Group/CoGroupByKeyImpl/Flatten/Read'})

Doing more research...

Errors I'm seeing:
OIOIOI DATA LEN IS  0 POS IS  1
Error in  NameContext({'step_name': 'assert_that/Group/CoGroupByKeyImpl/Flatten/Read', 'transform_id': 'assert_that/Group/CoGroupByKeyImpl/Flatten/Read'})

And afterwards
OIOIOI DATA LEN IS  682783 POS IS  682784
Error in  NameContext({'step_name': 'assert_that/Group/CoGroupByKeyImpl/Flatten/Read', 'transform_id': 'assert_that/Group/CoGroupByKeyImpl/Flatten/Read'})

I've done some more research. Oddly, the encoding size for the first set of elements that we output varies even on instances of successful tests.
I wondered if this could be because we encode every element with the current timestamp, which varies depending on test execution time - so I hardcoded a specific timestamp for all instances of the test. Encoding size still varied:
INFO:root:pabloem Adding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464646 - inst: bundle_1
INFO:root:pabloem Yielding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464646 - inst bundle_1
INFO:root:pabloem Adding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464675 - inst: bundle_4
INFO:root:pabloem Yielding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464675 - inst bundle_4
INFO:root:pabloem Adding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464679 - inst: bundle_1
INFO:root:pabloem Yielding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464679 - inst bundle_1
INFO:root:pabloem Adding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464693 - inst: bundle_4
INFO:root:pabloem Yielding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464693 - inst bundle_4
INFO:root:pabloem Adding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464658 - inst: bundle_3
INFO:root:pabloem Yielding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464658 - inst bundle_3
INFO:root:pabloem Adding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464725 - inst: bundle_4
INFO:root:pabloem Yielding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464725 - inst bundle_4
INFO:root:pabloem Adding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464684 - inst: bundle_1
INFO:root:pabloem Yielding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464684 - inst bundle_1
INFO:root:pabloem Adding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464685 - inst: bundle_3
INFO:root:pabloem Yielding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464685 - inst bundle_3
INFO:root:pabloem Adding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464719 - inst: bundle_3
INFO:root:pabloem Yielding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464719 - inst bundle_3
INFO:root:pabloem Adding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464702 - inst: bundle_1
INFO:root:pabloem Yielding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464702 - inst bundle_1
INFO:root:pabloem Adding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464694 - inst: bundle_1
INFO:root:pabloem Yielding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464694 - inst bundle_1
INFO:root:pabloem Adding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464702 - inst: bundle_4
INFO:root:pabloem Yielding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464702 - inst bundle_4
INFO:root:pabloem Adding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464673 - inst: bundle_1
INFO:root:pabloem Yielding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464673 - inst bundle_1
INFO:root:pabloem Adding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464716 - inst: bundle_1
INFO:root:pabloem Yielding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464716 - inst bundle_1
INFO:root:pabloem Adding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464684 - inst: bundle_4
INFO:root:pabloem Yielding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464684 - inst bundle_4
INFO:root:pabloem Adding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464682 - inst: bundle_1
INFO:root:pabloem Yielding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464682 - inst bundle_1
INFO:root:pabloem Adding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464702 - inst: bundle_1
INFO:root:pabloem Yielding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464702 - inst bundle_1
INFO:root:pabloem Adding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464665 - inst: bundle_3
INFO:root:pabloem Yielding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464665 - inst bundle_3
INFO:root:pabloem Adding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464703 - inst: bundle_1
INFO:root:pabloem Yielding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464703 - inst bundle_1
INFO:root:pabloem Adding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464720 - inst: bundle_3
INFO:root:pabloem Yielding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464720 - inst bundle_3
INFO:root:pabloem Adding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464669 - inst: bundle_4
INFO:root:pabloem Yielding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464669 - inst bundle_4
INFO:root:pabloem Adding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464675 - inst: bundle_1
INFO:root:pabloem Yielding Create/MaybeReshuffle/Reshuffle/ReshufflePerKey/GroupByKey/Write element. Len: 1464675 - inst bundle_1

@pabloem are you still actively working on this?

Thanks Kenn. I am not working actively on this now.
If I find some time I'll get back to it - but for now anyone else should
feel free to pick it up.
On Wed, Dec 7, 2022, 8:31 AM Kenn Knowles @.***> wrote:

@pabloem https://github.com/pabloem are you still actively working on
this?
—
Reply to this email directly, view it on GitHub
https://github.com/apache/beam/issues/21104#issuecomment-1341241215, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJ5Z3DN5XMZWS2F2HVFYXLWMC3WXANCNFSM5X4AZMYA
.
You are receiving this because you were mentioned.Message ID:
@.***>

I'll unassign you then


Error, ranger does not send notifications when orders done

I tried placing orders with price 2 and volume 3
and 1 bids bids with price 2 and volume 3
Ranger responds to my trading history
But it does not respond to orders done, it is still waiting, so trading-ui can not delete these orders from the list, when I reload the page everything is normal, so this is a feature?
In the old peatio was informed when orders done but in the Rubykube version does not seem anymore?
Thank you Rubykube team
@ysv

Fixed https://github.com/rubykube/peatio/pull/1913


unable to delete an event-subscription that targets a resource that doesn't exist

Describe the bug
Unable to delete an event-subscription that doesn't exist anymore.
I have an event subscription that targets a resource that in a deleted resource group.  When I try to delete it, via:
az eventgrid event-subscription delete --name  --source-resource-id , I get back:
Resource group 'GROUPNAME' could not be found.
When I recreate the resource group, I get:
The Resource 'Microsoft.Storage/storageAccounts/STORAGENAME' under resource group 'GROUPNAME' was not found.
When I recreate the storage account, I get:
The request url http://<IP_ADDRESS>:30013/<GUID>/132299720350923755/<GUID>/subscriptions/<GUID>/resourceGroups/<RESOURCE_GROUP>/providers/Microsoft.Storage/storageAccounts/<STORAGENAME>/providers/Microsoft.EventGrid/eventSubscriptions/<EVENTNAME>/providers/Microsoft.EventGrid/eventSubscriptions/<EVENTNAME>?api-version=2019-06-01 is not found.

The event, according to az eventgrid event-subscription list is:
{
    "deadLetterDestination": null,
    "destination": {
      "endpointType": "StorageQueue",
      "queueName": "file-changes",
      "resourceId": "/subscriptions/XXX/resourceGroups/YYY/providers/Microsoft.Storage/storageAccounts/ZZZ"
    },
    "expirationTimeUtc": null,
    "filter": {
      "advancedFilters": null,
      "includedEventTypes": [
        "Microsoft.Storage.BlobCreated",
        "Microsoft.Storage.BlobDeleted"
      ],
      "isSubjectCaseSensitive": null,
      "subjectBeginsWith": "",
      "subjectEndsWith": ""
    },
    "id": "/subscriptions/XXX/resourceGroups/YYY/providers/Microsoft.Storage/storageAccounts/AAA/providers/Microsoft.EventGrid/eventSubscriptions/BBB",
    "labels": null,
    "name": "onefuzz1",
    "provisioningState": "Succeeded",
    "resourceGroup": "GROUPNAME",
    "retryPolicy": {
      "eventTimeToLiveInMinutes": 1440,
      "maxDeliveryAttempts": 30
    },
    "topic": "/subscriptions/XXX/resourceGroups/YYY/providers/microsoft.storage/storageaccounts/ZZZ",
    "type": "Microsoft.EventGrid/eventSubscriptions"
  }

To Reproduce
Create resource group.  Create storage account.  Create event grid subscription monitoring file changes, targeting a storage queue.  Delete resource group.
Now you can't delete event grid subscription.

Expected behavior
Deleting event grid subscriptions that target resources that don't exist should be ok.
Environment summary

Additional context

eventgrid

@bmc-msft  thanks for reporting this issue. The issue described is by design and in adherence of how Azure Resource Manager (ARM) is forcing the resources models. When resource group is deleted all the resources in this resource group is deleted. This operation is stateless namely we don't remember if the resource group was created before and what resources in it was added. We cannot know if the user intension is to do full cleanup and restart over or restore.
If you still have any issue, please open an IcM/support ticket for Azure Event Grid team or reach out directly to<EMAIL_ADDRESS>thanks

It's "as designed" to be unable to delete eventgrid event subscriptions that target something that has been deleted?
Additionally, it's "as designed" to leak internal IP addresses of resources when that happens?


overloading Base.promote_type is not permitted

Several methods are added for promote_type in this package. Xref https://github.com/JuliaLang/julia/issues/54138

Can you help how to replace it? This mirrors the typejoin and other behaviour of Nothing and Missing, how to do without promote_type? (I remember that Nothing and missing used this, but I may be wrong)

Would simply overloading promote_rule instead of promote_type work?
I'm not otherwise familiar with this package, but I took a look at the implementation now, and it seems to me that it's deeply flawed. For example, this:
const Either{L, R} = Union{Const{L}, Identity{R}}

... should instead look something like:
struct Either{L, R}
  v::R
end

So, it seems to me that you're misusing Union when you should be defining a new, named, type.

Please, I ask you to be more respectful towards code you may not understand.
The types are carefully chosen and have advantages over defining structs.
As already said, the types Const and Identity behave similar to Nothing and Missing in that Union types get explicitly constructed. If you can tell me how to change the implementation without using promote_type, while not changing the type definitions, I am very happy to change it.


manifest update in url

Codecov Report

Merging #143 (909e353) into main (3b8648b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #143   +/-   ##
=======================================
  Coverage   95.18%   95.18%
=======================================
  Files           5        5
  Lines         436      436
=======================================
  Hits          415      415
  Misses         21       21

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 3b8648b...909e353. Read the comment docs.


Update Pages “about”

Automatically generated by Netlify CMS

👷 Deploy Preview for ecstatic-hugle-42f9fd processing.
🔨 Explore the source changes: d5696ce5a62cee08f9fe9ff82579e28898b83559
🔍 Inspect the deploy log: https://app.netlify.com/sites/ecstatic-hugle-42f9fd/deploys/615b4c6fa392ca00088fa221


Try to behave better when upgrading ephemeral SolrClouds

Currently a SolrCloud is treated the same during a managed upgrade, whether it is using ephemeral or persistent data.
However since all ephemeral data is lost during a pod update, the managed update logic fails to work when the ephemeral SolrCloud contains data. This is because the Solr Operator expects, after upgrading a pod, that the cluster state gets healthy before it can move on to the next pod. When the Solr replica data is deleted on pod upgrade, the collections those replicas belong to can never become healthy, since those replicas no longer exist.
What we can do is migrate all replicas on a node before upgrading it, if the SolrCloud is using ephemeral data. We control when pods are upgraded so we can make sure that the pod contains no replicas before a delete occurs.
If the ephemeral SolrCloud only contains 1 pod, then we have no choice to delete all the replicas for the pod before doing the upgrade, because there are no other pods to move them to.

I have a basic PR setup to do this, however with and without autoscaling, the cloud behaves exceedingly badly when try to use the "MigrateNode" command. It will migrate the replicas, then add more replicas on the original host to compensate. More research needed into to why this happens, and how Solr can be fixed.

Ok, so this bad behavior is entirely an issue with Solr's REPLACENODE command: SOLR-15795
Basically the command allowed Solr to use the sourceNode as the targetNode, which meant that the Solr Operator would unsuspectingly keep migrating replicas to their original node, in loop. This fix is going to be included in Solr 8.11.1, so whatever logic we write will have to be enabled via a flag until 8.11.1 is the minimum supported Solr version, which is likely a long ways off.
Another note: although SOLR-15795 will make this process actually possible, the logic from REPLACENODE is still pretty bad, and most replicas will likely end up on the same node if an empty node exists. SOLR-15803 is the next iteration of this, which will allow the REPLACENODE command to fully plan out a migration of the replicas on that node together, then execute those plans. This is not necessary for this Solr Operator feature, it will just be a major win when using it.


A simple question regarding slurm

Hey there devs,
I recently tried setting up slurm on my local machine with munge authentication, setting up the config file as well. When I try to enter my username@password asked by the script it doesn't get connected not sure why. I know its some issue from my side but any help from the devs is appreciated.
Thanks.

Could you give a bit more information perhaps some screenshots of errors (if any). Just make sure to blur any sensitive info like IP addrs.
Are you stuck during installation or when logging in through the browser?

I wanted to know that do i need to setup slurm on a remote computer? As I tried installing slurm on localhost with munge and installed all the required stuff.
When i try to do the cond setup step install locally, It asks for a ip and password, I am not sure if its slurm worker ip address or what password do I need to enter. The slurm bit is a little unclear to me. If there is a yt video or any deep documentation I would love to read it through.
I just want to figure out the slurm ip and pass part so It can install the rest of the stuff and I can start using it.
Dd_protocol manual is super good but I still have to go through a lot of commands, I mean I can do that easily but my colleagues need the gui version.
It would be great help, If you can help me with the slurm part.
Thanks for your time Jyaacoub.

Interesting... We built the system to work as a sort of controller, sending commands to a separate SLURM cluster, but I could imagine if you set it up properly that it could also work within the same system.
However, I am not sure how exactly you would need to set it up (I don't know much about system engineering). Could you not SSH into that machine from a separate computer? There could be something going on with the commands being sent to the same system you are running and it interfacing with SLURM in a weird way.
Also just to clarify: what does the connection process to SLURM look like for you? do you connect using username@localip (e.g<EMAIL_ADDRESS>followed by enter than your password?
This could also be an issue with the python library (paramiko) that is doing the connecting. Try connecting to the SLURM cluster first and see if that works using the following from the install.py file:
https://github.com/jamesgleave/DeepDockingGUI/blob/cdd947b794ae52db2bee124516c4455f2a7ef0b5/installation/install.py#L177

I will check this out thankyou very much :)


NIFI-7315 Fixed typo in bootstrap.conf for 17th argument

Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Fixed the typo for the 17th argument in the bootstrap.conf by removing an additional ".".
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] Have you verified that the full build is successful on JDK 8?
[ ] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

Thanks for fixing the typo @HorizonNet ! +1 merged to master.


crypto errors

as of the latest commits, emuiibo can no longer be built with this. It throws a bunch of crypto errors such as
"instruction requires aes"
or
"instruction requires: sha2"
I don't know if it's a bug in cargo-nx or if emuiibo needs to be updated, but I'm thinking the problems came from build.rs changes https://github.com/XorTroll/emuiibo/issues/229#issuecomment-1444985921

I'm aware of this, the tier 3 target we now use apparently didn't include crypto support
This issue isn't related to cargo-nx per se tho


Denton, Texas

Subject: [*** INSERT UNIQUE SUBJECT LINE***]
Email Addresses<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Message:
Hello,
my name is [NAME] and I live in [CITY/NEIGHBORHOOD].
I AM JOINING WITH OTHERS TO DEMAND THAT YOU, MY LOCAL OFFICIALS, WILL:
Vote no on all increases to police budgets
Vote yes to decrease police spending and budgets
Vote yes to increase spending on Health care, education and community programs that keep us safe.
Black communities across the nation are mourning the deaths of George Floyd, tortured to death by Minneapolis police, Ahmaud Arbery, a jogger who was killed while running in a residential neighborhood in Brunswick, Georgia, Breonna Taylor an EMT killed while asleep in her bed in Louisville,KY, Dreasjon Reed in Indianapolis and Tony McDade in Tallahassee. Their names are added to a devastatingly long list of Black people who have been killed at the hands of vigilantes or law enforcement. Not to mention the others whose names we don’t yet know, and may never know since they were killed without a camera recording it.
At the same time, the United States leads the world in COVID-19 cases. So far, more than 100,000 people — enough to fill a football stadium– have perished from the virus,with over one million cases confirmed, and those numbers don’t reflect all the people dying from virus-related illnesses.
It is important to state this within the context of the scourge of anti-Black police terror and the resulting uprisings taking place across the U.S.
The COVID-19 deaths and the deaths caused by police terror are connected and consequential to each other. The United States does not have a national healthcare system. Instead, we have the largest military budget in the world, and some of the most well-funded and militarized police departments in the world, too. Policing and militarization overwhelmingly dominate the bulk of national and local budgets. In fact, police and military funding has increased every single year since 1973, and at the same time, funding for public health decreased every year, crystallized most recently when the Trump administration eliminated the US Pandemic Response Team in 2018, citing “costs”.
Black communities are living in persistent fear of being killed by state authorities like police, immigration agents or even white vigilantes who are emboldened by state actors. According to the Urban Institute, in 1977, state and local governments spent $60 billion on police and corrections . In 2017, they spent $194 billion. A 220 percent increase. Despite continued profiling, harassment, terror and killing of Black communities, local and federal decision-makers continue to invest in the police, which leaves Black people vulnerable and our communities no safer.
Where could that money go? It could go towards building healthy communities, to the health of our elders and children, to neighborhood infrastructure, to education, to childcare, to support a vibrant Black future. The possibilities are endless.
We join in solidarity with the freedom fighters in Minneapolis, Louisville, and across the United States. And we call for the end to police terror.
Sincerely, The People of Denton, TX
[NAME]
[PHONE_NUMBER]
[EMAIL]
[ADDRESS]

Hi @dependent-libertarian ! Thanks for your interest in adding Denton to the site. Can you provide more detail about the city budget to make a more compelling argument, showing the disparities in numbers?
Please see our email style guide for some suggestions.
Thank you!


[Bug]: Transformer model failed to load if select gguf first but failed to load gguf model

select model: DanTagGen-gamma_ggml-model-f16.gguf
log:

The repo's name should be KBlueLeaf/DanTagGen-gamma instead of DanTagGen-gamma

It looks more like you have some issue to connect to HuggingFace.
Have checked. it can load the model correctly

I have checked my Internet and I'm sure the issue is not related to network.
By the way, according to the console log, the url I highlighted is surely wrong.
The way to reproduce this bug is to select gguf model and trigger llama-cpp-python load failed.
Only in this way transformers would get the wrong repo name.
Select transformers model directly works correctly.


Describe what a session secret is in the Auth0 auth provider

Hey, I just made a Pull Request!
Describe what a session secret is in the Auth0 auth provider
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[X] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[X] All your commits have a Signed-off-by line in the message. (more info)

Sorry, that build error was introduced just recently and is fixed by https://github.com/backstage/backstage/pull/18938


612 add Ensemble_pennylane notebook

[ ] I have added the tests to cover my changes.
[ ] I have updated the documentation and CHANGELOG accordingly.
[ ] I have read the CONTRIBUTING document.

 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.Poojith seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Looks good, Poojith! I have a handful of changes that I’d like you to make
Structural Changes

Overall wording
We should include a link to the original Pennylane tutorial, but the wording in our tutorial should be different. It can be similar since it is describing the same basic concepts, but it can’t be identical to what they have.
This tutorial would also benefit from more and longer text descriptions in general.

The draw() function
Thanks for starting the issue on this! We can work around this by removing the draw portion of the tutorial altogether. Instead, take a screenshot of the DAG that gets generated by the UI when the workflow is dispatched, and incorporate that into the tutorial.

The devices
Since we’re getting errors related to the qml devices, we should have a different approach for now. Rather than combining results from two different devices, we should combine results using different input parameters (as you have in the code now). This will mean changing the text descriptions to reflect that this is actually what we’re doing, as well as removing parts of the code where the devices are specified.

Conclusion
We’ll need some final paragraph or two summarizing what the results are showing us. You can do a visualization again, just leave it outside the covalent workflow.

Wording Changes

I know they don’t have this in the Pennylane tutorial, but can you add a short description about the Iris dataset? I.e. what the features are that we’re looking at, and how we’re trying to classify them.

Under the ‘Plot the Data’ you can note that we are doing this for visualization purposes but it is not included in the workflow

functions with ct.electron decorator → functions with the Covalent electron decorator

Missing a description of the decision() function

with the ct.lattice decorator → with the Covalent lattice decorator

Typos

acccuracy -> accuracy

In code block starting with line [57] there is a commented #p_train that can be removed

we can submit the task via the dispatch method → we can submit the workflow using Covalent dispatch

This is looking a lot better with additional text. I just have a few more minor wording changes and then we should be good to go.

In the title, ‘ensemble classification’ should be capitalized

In this tutorial we show how a quantum circuit → In this tutorial, we show how a quantum circuit

Make sure to capitalize Covalent throughout

Before starting the first code block, include text saying something like “We start by importing all the necessary packages.”

split them into training and test dataset → split them into a training and test dataset

Iris dataset is a very well known dataset used for pattern recognition  → The Iris dataset is very well known in machine learning, and used for pattern recognition

3 classes namely: → 3 classes:

using PCA → using principal component analysis

We plot the data to visualize the data → We plot the data to visualize it

Transport graph → Directed Acyclic Graph (DAG)

we can submit the workflow using Covalent dispatch → we can submit it using Covalent dispatch

using the ct.get_result method → using the Covalent get_result method

In order to calculate how well the ensemble model performs we use the predictions to calculate the accuracy of the model. → In order to calculate how well the ensemble model performs, we compare the model predictions to the actual classification values.

test set and it can be observed that the ensemble model performs better than the individual circuits →  test set, and it can be observed that the ensemble model performs better than the individual circuits.

In this tutorial we created workflow using covalent to predict →In this tutorial, we created a Covalent workflow to predict

Following are the key takeaways from the tutorial. → The key takeaways from this tutorial are:

Covalent is helpful in creating workflows that can take advantage of parallel execution of quantum circuits → Covalent helps create workflows that can take advantage of parallel execution of quantum circuits and can organize, track, and dispatch experiments.

The accuracy of ensemble model outperforms predictions from individual parameter settings. → The ensemble model outperforms both individual parameter models.

We don’t need point 3) in the key takeaways


[stable/dex] ADD annotations to grpc and web pods FIX #15451

Signed-off-by: Nicolaj Græsholt<EMAIL_ADDRESS>What this PR does / why we need it:
Adds custom annotations to the pods created by the grpc- or web-jobs. See #15451.
Which issue this PR fixes

fixes #15451

Special notes for your reviewer:
#15451 is about the grpc-job. I added custom annotations to the web-job as well for consistency.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/assign @desaintmartin

/assign @unguiculus

Thanks!
Could you rebase? A lot have changed (hopefully in the right direction) since you created the PR.
/ok-to-test

Rebased on master in beb5f5372 @desaintmartin
I'd like to document the certs.[grpc/web].pod.annotations in the README.md but I don't want to confuse it with the current Configuration list, that specifically lists "values introduced in 2.0.0".

The current Configuration should probably be Values introduced in 2.0.0, and there should be a Configuration header listing all of the parameters in the values file.. but I didn't want to bloat this PR with unrelated changes.

Rebased on master in beb5f53 @desaintmartin
I'd like to document the certs.[grpc/web].pod.annotations in the README.md but I don't want to confuse it with the current Configuration list, that specifically lists "values introduced in 2.0.0".

The current Configuration should probably be Values introduced in 2.0.0, and there should be a Configuration header listing all of the parameters in the values file.. but I didn't want to bloat this PR with unrelated changes.

Hi @figaw . Could you please change values table header from that:
The following table lists parameters introduced in v2.0.0

to that one:
Parameters introduced starting from v2

and add the values introduced in your PR to the same table?
It doesn't make much sense to have a different Configuration section in the readme. The table header mentioned above will be simply removed If somebody will be so kind to document all the chart values somewhere in future.

@vi7 of course! ...

I rebased again onto the master of helm/charts,
added descriptions of the values to the readme and bumped minor,
sorted the parameters in the list alphabetically.

Back to you!

@figaw thank you! I'm not sure I have proper permissions for this PR so.
/approve

Hi @desaintmartin ! Are you ok with the changes?

You have permissions. ;)
/lgtm
Thanks!


After installing pH7CMS using Softaculous the site isn't loading correctly... Any feedback on this issue?

Please also make sure with your web hosting that your web hosting plan meets the requirements https://ph7cms.com/doc/en/requirements

Hi !
Get back to us if you solved your issue so we can close the subjet !
Also, if you like the software then could you please give us a nice review on sourceforge ?
https://sourceforge.net/projects/ph7socialdating/
Also don't forget to "star" the repo !


docker host identification improvement and swarm mode support

First two commits addresses improvement in #475. Since contents of ServiceID changes, users has to make sure that old services match the new pattern, other wise old services has to be re-registered. This improvement simply uses docker info as suggested in #475 to fetch docker node name, which is commonly hostname. Thus there is no need to use registrator container's hostname or attach registrator to host network.
Third commit adds support of swarm node. Nothing breaks by the way. In addition to normal per container service registration adds support of registering docker swarm mode VIPs. Also populates service name from swarm service name, if not specified explicitly in SERVICE_X_NAME. In previous commits, node id in swarm mode was assigned to swarm node id, which is not very useful, as users most likely will know their host names, rather that node id in swarm cluster.

Any status on when this would be merged and added into a release? We'd like to be able to use registrator in the new 1.12 swarm mode

This would also be helpful for us as well. Any chance this will get merged soon?

can really use this...

@progrium I can email you a vagrant setup for swarmmode if you want

Got it from you via email. Though I might not find time for it. Too bad you can't share it publicly for others to try. Though I'm assuming it works. If somebody else can give it thumbs up that's good enough for me at this point. Still want to make sure this is documented before merging.

building the source repo :(
# github.com/gliderlabs/registrator/bridge
bridge/bridge.go:254: invalid operation: services[0].Spec.EndpointSpec.Mode == "github.com/docker/engine-api/types/swarm".ResolutionModeVIP (mismatched types "github.com/docker/docker/api/types/swarm".ResolutionMode and "github.com/docker/engine-api/types/swarm".ResolutionMode)
bridge/bridge.go:256: cannot use services[0] (type "github.com/docker/docker/api/types/swarm".Service) as type "github.com/docker/engine-api/types/swarm".Service in argument to b.registerSwarmVipServices
The command '/bin/sh -c cd /go/src/github.com/gliderlabs/registrator 	&& go get 	&& go build -ldflags "-X main.Version=dev" -o /bin/registrator' returned a non-zero code: 2

In my setup with docker swarm it worked. However, with time I realized that changes for docker swarm mode support shall be more deep and probably require some design decisions, since docker swarm mode does not operate on containers, but services. definitely it will be --docker-swarm-mode  flag.
On the other hand, probably I will be moving from consul and registrator in docker swarm mode. Docker swarm mode targets service discovery features of consul, making it unnecessary overhead. I don't think that in real world docker swarm mode + consul (or etcd or else) + registrator will be used.
I might look at this in next 2-3 weeks, if still be needed. But before that we can discuss your use-cases, to clarify the functionality. Because as I mentioned above, probably docker swarm mode + consul + registrartor is not effective combination.

@muradm thanks for the update.
Since none of us are using Swarm, if anybody else thinks this is worth getting in we'll need somebody else to take it over if @muradm ends up moving away from this setup.

The reason I want to use it:
use registrator for consul registration
consul template for generating dns based vhosts to make more then one service running on port 80.
I am not sure if this can be done in a different way

@MansM, I suppose that you run a number of "docker service create" with publishing port, is it right? Do you use VIP or dns-rr for service? And your consul template runs outside of docker? And your apache/nginx or what so ever runs outside of docker swarm as well, right? Could you please explain your case with details?
If that the case, I probably would move apache/nginx/or else inside docker swarm overlay network. Then each created service:
docker service create --name service1 --replicas 3 ... will get two DNS records available inside overlay network, so that ping service1 and ping tasks.service1 will work from any other service inside same overlay network. That means, you can make once your vhosts like:

vhost1 -> service1:8081
vhost2 -> service2:8082
service1 and service2 requests will be load-balanced by docker, so that you don't need to keep track of IP addresses of each specific instance.

on the path of moving from docker 1.11 to 1.12 and naturally, trying the swarm mode.
I'd still like to keep consul but registrator is not helping due to this very issue.
would be willing to test the PR if it's going to be maintained.
I believe this is the kind of issue that comes from vendor locking. docker is (unfortunately) not going to be very keen on making it easy for us to bypass its own service discovery. just like prometheus is doing its best to get metrics and so is registrator to bridge the gap with consul.
IIRC, k8s users were also suffering because of these "portless" containers a while back. but at least k8s also supports rocket.
anyway, I really appreciate the PR & would definitely use this feature if it gets merged.

Thumbs up on this PR.
Tested in my scenario with an external Haproxy that needs dynamic reloading/creation of backends being created by services in the docker swarm cluster.
Would be nice to have it merged.

This would be really useful to us too, upvote PR.

@peterthehermit  +1 ! Need it really !

+1 an awesome and much needed feature :+1:
Anything needed or missing to get this PR merged?

So whats the status of this PR currently?

To answer the question as to "why" is pretty simple:  multiple swarm clusters.  In many industries there are compliance guidelines that will practically force multiple clusters to be used.  In this scenario having an "external" service discovery helps you maintain dynamic configurations while meeting compliance.  consul templates to keep firewalls accurate and services reliable is not easily tossed aside.
As container use grows, there will be many who will be forced to separate PCI systems and general PII information in easily audit-able ways to comply with HIPPA, etc.  Unless Docker plans on re-introducing the ability to register with Consul directly, we'll need tools like Registrator to fill that need.
Anyway, add me to the "would really like to see this" as well as "about to test this" :)

Same problem here. Our current infrastructure heavily rely on consul for routing services to swarms , single docker hosts and even non-docker hosts. Additionally it acts as service discovery for our monitoring solution (prometheus). So it is an integration point we can't simply give up. We really need a migration path for our production infrastructure so I tried to combine the efforts of #476 and #520 for supporting swarm mode services here: https://github.com/gliderlabs/registrator/pull/588
Any feedback is really appreciated.

Supersceded by #588. Thanks for the initial PR though!


bump prod release trigger

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


Add User Icon to Card

Hello Christian! I'd like to suggest that the word "By" in the card footer get replaced with an svg icon. I was thinking the "user-circle" icon from Heroicons. Thoughts? I'm more than happy to work on this, just lmk. Thank you.

Sounds interesting! Do it!


dotnet tool install -g upgrade-assistant takes wrong source

dotnet tool install -g upgrade-assistant
leads to
C:\Program Files\dotnet\sdk\6.0.100-preview.7.21379.14\NuGet.targets(131,5): error : Fehler beim Abrufen von Informationen zu "upgrade-assistant" aus der Remotequelle "https://pkgs.dev.azure.com/GreenerSoftware/_packaging/fd0f674f-868a-4655-8ddd-8c3f2360dad8/nuget/v3/flat2/upgrade-assistant/index.json". [C:\Users\kugle\AppData\Local\Temp\vwazqmm3.4yh\restore.csproj]
C:\Program Files\dotnet\sdk\6.0.100-preview.7.21379.14\NuGet.targets(131,5): error :   Response status code does not indicate success: 401 (Unauthorized). [C:\Users\kugle\AppData\Local\Temp\vwazqmm3.4yh\restore.csproj]
which is the wrong nuget source

You're trying to install it in a directory that already has a NuGet.config with sources that don't have it available. You can either go to another adirectory or do dotnet tool install -g upgrade-assistant --ignore-failed-sources

Closing for now. If that doesn't work, please reopen.

Opened https://github.com/dotnet/sdk/issues/20396 to track not looking at local nuget.config entries


Welding airlocks changes their layer

About the PR
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

https://user-images.githubusercontent.com/60792108/211904335-202e78aa-1158-489e-b0d7-da67a2304ddc.mp4
Changelog

:cl: Rane

add: Welding doors will now stop mice from running under them.

you are right it is more broadly applicable than doors; I have moved everything over to the tools namespace
Currently mispredicts due to https://github.com/space-wizards/space-station-14/issues/13616 as a caution, probably want that fixed before merging

I've fixed merge conflicts for you


client.kvm.add_nic fails when a vm is added to certain existing vlan (or vxlan) with certain name

Scenario
1- Create vlan with name='test9'
In [40]: ovscl.json('ovs.vlan-ensure', {'master': 'backplane', 'vlan': 349, 'name': 'test9'})
Out[40]: 'test9'

2- Add any existing vm to this vlan, should succeed
In [41]: client.kvm.add_nic('08a46c8e-c103-49a5-8dab-c5b6cfd35d2f', 'vlan', id='349')
RuntimeError: ('invalid response: ERROR', STATE: ERROR
STDOUT:

STDERR:

DATA:
"failed to ensure vlan bridge: \"reassigning vlan tag to another bridge not allowed\""
)

Actual result
Step 2 failed because it is trying to create bridge with name= 'vlbr349'
Expected Results
This call should succeed, even when i create vlan with certain name

Version: 1.1.0-alpha @Revision: 8ae8db4f97da86af9ba5014bf3bf9d00ebf52d12

Verified on Version: 1.1.0-alpha @Revision: cb9127069375fb32a5e03ac88ab71504212487aa


Switch expression syntax should be recognized inside switch statements

To the extent possible, it would be nice if the parser could recognize if the syntax of a switch expression is erroneously used where a switch statement is expected, e.g.:
f(x) {
  switch (x) {
    0 => 'zero',
    1 => 'one',
    _ => 'other'
  }
}

Currently this produces the error Expected to find 'case' at the location of the 0, and then no further messages (because the parser gives up and skips to the end of the switch).
It would be a lot nicer if the parser:

gave a specific error message indicating that the user appears to be using switch expression syntax where a switch statement is expected, and
and continued parsing the rest of the switch expression.

(1) would allow us to associate some documentation with the error message explaining how switch statements and switch expressions are disambiguated, and the analysis server could in principle even include some suggested fixups (e.g. convert to a switch expression by enclosing in parentheses). (2) would allow code completions and other analysis server features to continue working in spite of the error.

We're hoping to introduce some extra documentation/info on dart.dev to make this more clear as well since it has been coming up a lot and I imagine these improvements won't land for a while. \cc @MaryaBelanger
In https://github.com/dart-lang/language/issues/3061 there was another motivating example:
enum Color { red, blue, green }

void main() {
  final color = Color.red;
  switch (color) {
    Color.red => "red",
    Color.blue => "blue",
    Color.green => "green",
  };
}

Which ends up with 4 different diagnostics confusing the user on what the actual problem is.


Add Support For Istio-Agent

[ ] I have searched the issues of this repository and believe that this is not a duplicate.

Describe the proposal

Resolved at #10567


Incorrect requirement (AZ Module)

AFSS is still dependent on AzureRM.  Please update.

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

ID: 61bb35a5-e2f3-1ce8-1d6e-a926374de6c8
Version Independent ID: e4b3065a-5351-26ef-cdbb-ef2eaea3f301
Content: Deploy Azure File Sync
Content Source: articles/storage/files/storage-sync-files-deployment-guide.md
Service: storage
GitHub Login: @wmgries
Microsoft Alias: wgries

@gacurtin This was fixed this morning, please elaborate what you're asking for.


Added Drupal packagist information

Hi Jens,
Thanks for the awesome list of links. I work with Drupal most of time, and there is a stable composer repo for Drupal modules. PR contains link to a page containing more information.
Thanks.

Hi!
Thank you for contributing 👍
Best, Jens


Update README.md

Shorten the landing page, include a link to the TinyStories blog post.
Description
Make minor revisions to the landing page. Include a link to the TinyStories blog post.
Checklist

[X] I am familiar with the Contributing Guide.
[X] New or Existing tests cover these changes.
[X] The documentation is up to date with these changes.

@Maghoumi given you didn't change according to 2 & 3, I just want to confirm that the open source is needed for SEO and that "Large Language Models Data Curation" is correct (instead of "Large Language Model Data Curation")

@ryantwolf Oops, I missed your original comment. I changed it to "Large Language Model Data Curation". Yes the redundant open source emphasis is for SEO as there is no other mention of it in the readme file.


fix: webhookTimeout flag description not clear enough

Related issue
This PR fixes webhookTimeout flag description not clear enough.

Related PR and issue:

https://github.com/kyverno/kyverno/pull/8493
https://github.com/kyverno/kyverno/issues/8492


Added Japanese translation.

Checklist

[x] I have made a material change to the repo (functionality, testing, spelling, grammar).
[x] I have read the Contribution Guide and my PR follows them.
[ ] I have discussed these changes via issue.
[x] I have made my changes on a new branch.
[x] My code follows the code style of this project.

Short description of what this PR does:

Added Japanese strings to the project based on #8

Thank you @munex-com !


Remove boilerplate

I was just stalking a bit.
This PR:

Removes some old boilerplate code
Suggests to use the from lamin_utils import logger logger which is pretty awesome and also used in other non-Lukas theislab projects.
Updates some Python versions in the CI

amazingg all of this is awesome ❤

Not sure why I get a test failure with:
FAILED tests/test_io/test_omop.py::test_empty_observation - AssertionError: assert 'No data found in observation. Returning edata without additional variables.' in ''
 +  where '' = <_pytest.logging.LogCaptureFixture object at 0x7facd78fd6a0>.text

:thinking:

First suspicion is that the warning is not logged anymore


Change PhpSpec test file detection to use readfile

Arises from #215. I am able to get it to work when searching for "PhpSpec" but not "PhpSpec\ObjectBehavior" for reason.

Thanks!

I am able to get it to work when searching for "PhpSpec" but not "PhpSpec\ObjectBehavior" for reason.

You mean if the file contains content PhpSpec\ObjectBehaviour, you cannot detect it via this method? I tested it now, and you're right, the following doesn't work:
filter(readfile(a:file), 'v:val =~# "PhpSpec\\ObjectBehaviour"')

However, for some reason if we use single quotes, it works (you can insert single quotes inside single quotes by doubling them):
filter(readfile(a:file), 'v:val =~# ''PhpSpec\\ObjectBehaviour''')


The TLS_OPTS variable is missing

When using the following command to generate the.env file, the TLS_OPTS variable is missing. And https will be automatically enabled in docker-compose file, which will result in https access blocked forever.
docker run --rm firezone/firezone bin/gen-env > .env

The following variables can be used when configured in the.env file.
TLS_OPTS="tls {
on_demand
}"

this is not a bug.
I think you should read the install.sh carefully, the function promptACME has asking about the parameter, and it will use in TLS_OPTS.
if you require manually update .env file and include default TLS_OPTS , you can simply rewrite the script and assign the value you want
running a command without follow the logic in script, of course you won't get the result.

Hi, I installed it according to the manual installation steps in the documentation, which does not explain this step in the documentation, suggest to modify the documentation.

agree but it also very hard to explain each function in documentation, it should be in development rather than deployment,.
I can confirm that running the script (up to 0.7.29) by default can get firezone up and running, and I also suggest dig in the install script to found out the deployment option, it can help to understand much more control.
I have rewrite it since I am using podman container instead of docker, it is a difficulty path but also an interesting path
you can provide your understanding to documentation in future, just like I also share the change in podman deployment script.
or you can change the bug to suggestion tag

I can't change the bug to suggestion tag, lol.


Missing pages describing writing and managing a revew

https://www.boost.io/doc/formal-reviews/writing-reviews.html
https://www.boost.io/doc/formal-reviews/managing-reviews.html
These pages are empty.
Until you manage to write something better, just copy the content from the current website:
https://www.boost.org/community/reviews.html
You can omit the Review Wizards section, as that should probably go to the page requested here.

This issue should be moved to the docs repo: https://github.com/boostorg/website-v2-docs


🚀 Updating from new fork : Adding Tool ➕

What type of PR is this? (check all applicable)

[ ] 🚀 Added Name
[ ] ✨ Feature
[ ] ✅ Joined Community
[ ] 🌟 ed the repo
[ ] 🐛 Grammatical Error
[x] 📝 Documentation Update
[ ] 🚩 Other

Description
#68, #70, #71

FINALLY!

Thank you @ABSphreak :)


OffsetBasedSource: allow empty sources

As one example, empty files exist.

R: anyone (@lukecwik @tgroh @bjchambers @kennknowles)

This seems worthwhile to have a test around it since its a boundary condition.

Thanks. Done, PTAL.  (Also did a little other housekeeping in the test file.)

LGTM. Interesting findbugs issue.

You'll need all subclasses to also guarantee it is @NonNull.

Yeah, reverted the change to make fraction consumed non-null. Don't love this inheritance, but I was not intending to make a backwards-incompatible change in this PR.

Thanks @kennknowles , @lukecwik --merged.


feat: extend markdownlint/style/prettier

PR Checklist

[x] Addresses an existing open issue: fixes #58
[x] That issue was marked as accepting prs
[x] Steps in CONTRIBUTING.md were taken

Overview
Simplifies .markdownlint.json just a bit with `"extends": "markdownlint/style/prettier".
Adds an explicit dependency on markdownlint as a result.

Codecov Report

Merging #175 (6c78f29) into main (14af3aa) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #175   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines            6         6
  Branches         3         3
=========================================
  Hits             6         6

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


[ACM-7674] Updated MCE operand namespace to support openshift.io/cluster-monitor…

Description
Update the MCE operator to add the openshift.io/cluster-monitoring label to the namespace where the MCE resources are deployed. The label will be added during the operator reconciling phase.
Related Issue
https://issues.redhat.com/browse/ACM-7674
Changes Made
Updated MCE operator to update the namespace object where MCE's operands are deployed with the openshift.io/cluster-monitoring label. This will allow OpenShift to detect the namespace where the PrometheusRules and ServiceMonitors will now be deployed.
Screenshots (if applicable)

Checklist

[x] I have tested the changes locally and they are functioning as expected.
[x] I have updated the documentation (if necessary) to reflect the changes.
[x] I have added/updated relevant unit tests (if applicable).
[x] I have ensured that my code follows the project's coding standards.
[x] I have checked for any potential security issues and addressed them.
[x] I have added necessary comments to the code, especially in complex or unclear sections.
[x] I have rebased my branch on top of the latest main/master branch.

Additional Notes
Add any additional notes, context, or information that might be helpful for reviewers.
Reviewers
Tag the appropriate reviewers who should review this pull request. To add reviewers, please add the following line: /cc @reviewer1 @reviewer2
/cc @cameronmwall @ngraham20
Definition of Done

[ ] Code is reviewed.
[ ] Code is tested.
[ ] Documentation is updated.
[ ] All checks and tests pass.
[ ] Approved by at least one reviewer.
[ ] Merged into the main/master branch.

/lgtm


remove author link

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #114
Test URLs:

Before: https://main--sling--aemsites.aem.live/whatson/entertainment/holiday/lifetime-christmas-movie-guide
After: https://114-authorlinks--sling--aemsites.aem.live/whatson/entertainment/holiday/lifetime-christmas-movie-guide

Not going to merge this. Per Ashley Hastings, they believe they will want to have author pages as they do today.


drain options: add skip-wait-for-delete-timeout

add skip-wait-for-delete-timeout option to fix unsuccessful deletion of pods because of waitForDelete after the node is labeled for drain.

Fixed via #89

tested via #98


Build with Visual Studio 2017

What's the impetus here?  We're very intentionally using an old version because VS 2015 introduced a new C runtime that does things like take mutexes in seemingly simple functions.  eg, some of the string functions now take a lock on the system locale to avoid race conditions.  This is, I guess, an overall win for the operating system, but it's not for us when we're dealing with ASCII or UTF-8.
We've fixed a lot of these in libgit2 by using our own functions, but I doubt that we actually found them all, so I'm a bit hesitant about upgrading our build environment.

I opened this because we talked offline about doing this, and you had said it was worth doing before. If that's not the case, then let's close it.

Haha, did I?  😀  I guess I had forgotten about that (it came up again recently in conversation which is probably why I remembered it.)
Let's benchmark the VS12 vs VS15 builds - probably the unit tests are a good enough metric, either libgit2's or LibGit2Sharp's.  I can do this when I have a few spare cycles.

@ethomson Any more thoughts on this change?


Doc imprvment for Storage

(message created by the CI based on PR content)

Yeah, this is definitely going in the right direction!
Out of curiosity, how did we end up with internal modules being explicitly listed as documented in the .rst file?

@johanste I believe it's sphinx_api_doc


build过程中遇到Undefined symbols for architecture riscv64的问题

/bin/cp: cannot stat '/root/fisco/fiscobcos/deps/src/libvrf/libffi_vrf_riscv64.a
': No such file or directory
Environment (please complete the following information):

OS: [e.g. openEuler]
FISCO BCOS Version [e.g. 2.9.1]

Additional context
Add any other context about the problem here.

是在risc V上编译吗？这里看报错是没提供这个库导致的


GSL interpolation error

I used a boost invariant(2+1D) hypersurface file from MUSIC and tried to run the code. but it's showing an error of following type:
[.......]
Reading in freezeout surface in (new) public MUSIC boost invariant format
Loading particle info from urqmd/smash pdg file (check that only 1 blank line at end of file)
...using read_resonances_conventional()
There are 327 resonances: 77 mesons, 125 baryons and 125 antibaryons
Last particle: mcid = -12110, Anti-baryon-n-2250, m = 2.250000 GeV (please check this)
Reading in 14 moment and Chapman-Enskog coefficient tables...done
gsl: interp.c:83: ERROR: x values must be strictly increasing
Default GSL error handler invoked.
Aborted (core dumped)

Hi Tribhuban,
It looks like this error occured when you test/print the df coefficients using the averaged temperature. You can check thermodynamic_quantities.dat to see if the average temperature [GeV] (first row) is what you expected.
If the value looks wrong, then your surface file and read-in format may be inconsistent so it's important to double-check the columns. I believe the MUSIC format (mode = 6) has the columns
[t x y n ds_t/t ds_x/t ds_y/t ds_n/t u^t u^x u^y t.u^n E T muB muS muC (E+P)/T pi^tt pi^tx pi^ty t.pi^tn pi^xx pi^xy t.pi^xn pi^yy t.pi^yn t2.pi^nn Pi]
If you're still having issues, you can send a snippet of the surface file and parameter file to my email<EMAIL_ADDRESS>Hope this helps,
Mike

Based on what you sent me, it looks like you're missing muS and muC above (strange and charm chemical potential). You're surface file is short by two columns, so your average temperature went nan instead of ~ 0.135 GeV.
I'm not sure what parameter in MUSIC is needed to include {muS muC} in the surface since I never used the code myself. You should ask Derek, Chun or J.F.
In the meantime you could try commenting l.738 - 739 in readindata.cpp

Mike

Thanks Micheal. I  just took a single row of 'surface.dat' file and put 0,0 in the place of muS and muC . Now it's working fine.