Created 7666a4fa branch

Thanks
On Thu, 30 Mar 2023, 8:01 pm Noble Osinachi, @.***>
wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/NobleOsinachi/test/pull/66
Commit Summary

4f662fd
https://github.com/NobleOsinachi/test/pull/66/commits/4f662fd040f8f612ee4811a1e00b8935b661f9f6
Created 5bdcdbab branch
836efdf
https://github.com/NobleOsinachi/test/pull/66/commits/836efdf5401d096eb512e1d0164ea11e7ce6f3e4
Created 57cb267c branch
3e322ee
https://github.com/NobleOsinachi/test/pull/66/commits/3e322ee93b58f559c74f6973ece2513556f96494
Created 84d638bf branch
2b879a3
https://github.com/NobleOsinachi/test/pull/66/commits/2b879a38a72f2a00f925622f89222e3d871f9239
Created 10e2e7a4 branch
2305fb9
https://github.com/NobleOsinachi/test/pull/66/commits/2305fb9c6f8ba943c3c2c10851e42653623f83e3
Created 3e48015c branch
9502211
https://github.com/NobleOsinachi/test/pull/66/commits/95022115b841e1dcd693fc13d76d818efe519f2a
Created e0fd8a99 branch
ac81344
https://github.com/NobleOsinachi/test/pull/66/commits/ac8134404c2fb8c5882a6bd47fca81fc429d86be
Created 5f23ca68 branch
26c70da
https://github.com/NobleOsinachi/test/pull/66/commits/26c70da0f9d827ee358c4483928bafc875d33835
Created 4f26a861 branch
1871ce0
https://github.com/NobleOsinachi/test/pull/66/commits/1871ce0db853c57603ff081ee3471ab036a9571b
Created 37731066 branch
d4d689e
https://github.com/NobleOsinachi/test/pull/66/commits/d4d689ed28e16e91b0f03321d970c13a4e78af16
Merge branch 'main' of github.com:NobleOsinachi/test into 37731066
d5d947c
https://github.com/NobleOsinachi/test/pull/66/commits/d5d947c1c72f13b9e9cbbef62df734e34dc4ed5a
Created 04e9c437 branch
84563cb
https://github.com/NobleOsinachi/test/pull/66/commits/84563cb25a1e2d20f7422f1f2adb26f86bf92347
Merge branch 'main' of github.com:NobleOsinachi/test into 04e9c437
544c7a1
https://github.com/NobleOsinachi/test/pull/66/commits/544c7a1eb3def3585c7c4e028b3568f632828c15
Created 81871489 branch
3d38aa1
https://github.com/NobleOsinachi/test/pull/66/commits/3d38aa11cd80f56e6ccd0c923d3ed594316a0d9d
Created db423816 branch
1796b4c
https://github.com/NobleOsinachi/test/pull/66/commits/1796b4cb5addb237f2b2c6c682b7747c84cb7d65
Merge branch 'main' of github.com:NobleOsinachi/test into db423816
d4fe72a
https://github.com/NobleOsinachi/test/pull/66/commits/d4fe72af02ad8e785451065ce180701c9bca38af
Created 7f2b43d4 branch
fe62d4b
https://github.com/NobleOsinachi/test/pull/66/commits/fe62d4b34c791ee8d34a4f846c5cf38b308ef7d3
Merge branch 'main' of github.com:NobleOsinachi/test into 7f2b43d4
b3d872e
https://github.com/NobleOsinachi/test/pull/66/commits/b3d872e62e134a65b4c568135f01cf1a528c7159
Reconcile collaborator details
3d8d257
https://github.com/NobleOsinachi/test/pull/66/commits/3d8d257e7dd668bef9136d1c3860d8313ea65e50
Merge branch 'main' of github.com:NobleOsinachi/test into 7f2b43d4
62932be
https://github.com/NobleOsinachi/test/pull/66/commits/62932be4dd3c02191eda5c2038c28294d8e09955
Created a004ba86 branch
e850864
https://github.com/NobleOsinachi/test/pull/66/commits/e8508641b2601a2fc5e102e158960943b7c7d799
Merge branch 'main' of github.com:NobleOsinachi/test into a004ba86
8e41a69
https://github.com/NobleOsinachi/test/pull/66/commits/8e41a69a57bcf87a07114d742c2be31e321f87d0
Created 79888887 branch
1666956
https://github.com/NobleOsinachi/test/pull/66/commits/1666956888a10876cddc9ca878f507e3cf6e8d9f
Created ddef5575 branch
0aacb44
https://github.com/NobleOsinachi/test/pull/66/commits/0aacb444a9dc3db1f6ddfdd7c6a65a65ea1384da
Created 82218125 branch
6577954
https://github.com/NobleOsinachi/test/pull/66/commits/6577954d6c326f402e1ba17aee7cdb46cce2357f
Created e1f79281 branch
e2cdf1c
https://github.com/NobleOsinachi/test/pull/66/commits/e2cdf1c452f24d788f566207d9ecb76e6506802c
Created 592e95c9 branch
aae690f
https://github.com/NobleOsinachi/test/pull/66/commits/aae690f4a16c55b0d55ba9feefdd34e704c88d0d
Created 610b067c branch
8fb8cca
https://github.com/NobleOsinachi/test/pull/66/commits/8fb8ccadd864a82e6f81834318d2755f04b2034b
Created cfda5766 branch
e8034c9
https://github.com/NobleOsinachi/test/pull/66/commits/e8034c992c2a92cd410213304a1d3cc658f1ed4b
Created a3095c3f branch
272380c
https://github.com/NobleOsinachi/test/pull/66/commits/272380cacba1ec347d1a7c4761ab65a86e73dd96
Merge branch 'main' of github.com:NobleOsinachi/test into a3095c3f
81db173
https://github.com/NobleOsinachi/test/pull/66/commits/81db17348e8c7da2f1a1d5edb44a4ed13aef4767
Created 9e364eb7 branch
e2f0ec7
https://github.com/NobleOsinachi/test/pull/66/commits/e2f0ec75290a445cc77457fcb4b24d6cb92815f9
Created 4b571996 branch
1c46295
https://github.com/NobleOsinachi/test/pull/66/commits/1c46295f5677c0ca9700c402813e0e3fe9ad15dc
Created 7fe1c3f0 branch
6543915
https://github.com/NobleOsinachi/test/pull/66/commits/654391578c4efe8baeac30a9f9a303bf0c118224
Created 15fdcd73 branch
6f237a4
https://github.com/NobleOsinachi/test/pull/66/commits/6f237a40d6186a42c939875453f3f38cc620fb0a
Created b206aefa branch
c1ce2a8
https://github.com/NobleOsinachi/test/pull/66/commits/c1ce2a8904976080ee4125b319af994e75f5f1f9
Created 04b7bac3 branch
b5aa8bc
https://github.com/NobleOsinachi/test/pull/66/commits/b5aa8bc7f2b4b32152ee62b8ee26f1d009887088
Created a4a1477f branch
83cf103
https://github.com/NobleOsinachi/test/pull/66/commits/83cf103747767157d88ffb423afe9689ae579aa6
Created 1add9ba3 branch
109be0c
https://github.com/NobleOsinachi/test/pull/66/commits/109be0c21b7e88148e41c2f93a5140609fc89d56
Created 2e1bdf21 branch
8c025af
https://github.com/NobleOsinachi/test/pull/66/commits/8c025aff3b8e22be3196fd863c9cd46bfd75e18c
Created 7666a4fa branch

File Changes
(12 files https://github.com/NobleOsinachi/test/pull/66/files)

M collaborators.txt
https://github.com/NobleOsinachi/test/pull/66/files#diff-84360665308c67e1a3b6aa83b06e5e4e450d6e175121ddcb56ffef91d1992e71
(85)
A scripts/04b7bac3-174a-41b8-a5c6-e3a2cbf0dea9.ps1
https://github.com/NobleOsinachi/test/pull/66/files#diff-56561c53dbaa36a1c9a237793349ff9e0f29259170b03c1c934d6f6170f67979
(37)
A scripts/15fdcd73-4e9e-4869-aee0-c244a2bb9534.ps1
https://github.com/NobleOsinachi/test/pull/66/files#diff-132da1c9ff317d2ad681e6b5315661289cc5a0bb3e6e315787581c896346ca61
(34)
A scripts/1add9ba3-071c-4c25-8033-6cdee6a3c5dd.ps1
https://github.com/NobleOsinachi/test/pull/66/files#diff-83ec86042398edc22d69260789891d68e59c642713452d28e78112f0f86ac661
(34)
A scripts/2e1bdf21-c62c-4e1b-97ef-9fcd5e3f5878.ps1
https://github.com/NobleOsinachi/test/pull/66/files#diff-3e5f13b9acb65e7d71ce57ac7205dc71b02ebb51d8d11b5974b7769cfe84f4b6
(34)
A scripts/4b571996-85e9-4ca9-bad3-8956c4ce3ae1.ps1
https://github.com/NobleOsinachi/test/pull/66/files#diff-6553d8099ef7d6e5e49933eabd14fc3e2379652af1d50a7fe330e2c4a1194cab
(34)
A scripts/7666a4fa-407f-465e-9f9b-427a3e0f0bd9.ps1
https://github.com/NobleOsinachi/test/pull/66/files#diff-fa7c727c217b16ea2ddc8cafb96b575e7e2a15d3e5991cf390aab3e4cbe5b4b9
(34)
A scripts/7fe1c3f0-db89-4433-8327-9ab7d8a07eae.ps1
https://github.com/NobleOsinachi/test/pull/66/files#diff-0c05d33e3a1df68545a39f3a3e40f09dd6fdd6660e8f232cc54316608605a722
(34)
A scripts/9e364eb7-eb8e-4d22-888a-326f24c4869b.ps1
https://github.com/NobleOsinachi/test/pull/66/files#diff-45930d44d7175bea1fcba5835de78e0b84571398bceb70db118453eff21c474c
(34)
A scripts/a4a1477f-fd53-4cb0-aa1b-e938e2523176.ps1
https://github.com/NobleOsinachi/test/pull/66/files#diff-87ad28edcb150bbd82f14a886ae603762a1b77f5579c13c7c4958d1b15d2285e
(34)
A scripts/b206aefa-1bf1-464e-9782-d4c2d143a0ef.ps1
https://github.com/NobleOsinachi/test/pull/66/files#diff-4d6511b49d78dcf4a67f8efa7f6ecc7689ba7f724d904566188512a98e5d525b
(34)
A scripts/b8d860f0-cb79-406c-8f1e-f2eb495a5b29.ps1
https://github.com/NobleOsinachi/test/pull/66/files#diff-15a2fd101a462a95a484c3c66971b937c823329f3f7715821a850b01f00dbc1d
(34)

Patch Links:

https://github.com/NobleOsinachi/test/pull/66.patch
https://github.com/NobleOsinachi/test/pull/66.diff

—
Reply to this email directly, view it on GitHub
https://github.com/NobleOsinachi/test/pull/66, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANRS6AEITSOGBHGDEV73JXDW6XKA7ANCNFSM6AAAAAAWNWLEBI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Merge master into release for 1.3 release

@caslan @gregg-miskelly @wesrupert @DustinCampbell

Let's wait on this merge if that's OK. This release really needs the Dual OmniSharp work.

Abandoning for now. No sense in making this merge until we update clrdbg package references.

I'd like to be more intentional about when we merge to release. Please see the mail I sent about releases late last week. We should at least have a conversation about when the right time is to merge for all parties involved (not just the debugger).

Apologies.


Added authless flag for connection without user/pass or apikey

Added in 4bbf0c6 to not force authentication details


modal serve command line

It supports a --timeout flag which is really only useful for tests

happy to address comments async


Created new world , now restart script don't work

Hey guys. I had a perfectly working auto restart with a Cron job for every 8 hours on my server. Gave countdown and advised everyone of a restart commencing .    Created a new world , it auto restarts it as scheduled. But immediately restarts. No prompt or anything anymore. :( My mscsctl has the proper setup and nothing changed in it. Dunno what's breaking it. Any advise is greatly appreciated. Thanks guys

If you edited the section I mentioned in msctl, can you post it here?

I can. And yes I did. And it worked ever since.  No issues at all.   Then created new worldnusing mscs create.  And it don't work no more but it all remains the same
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Joshua Clark @.>
Sent: Saturday, April 10, 2021 5:04:50 PM
To: MinecraftServerControl/mscs @.>
Cc: TheRanker @.>; Author @.>
Subject: Re: [MinecraftServerControl/mscs] Created new world , now restart script don't work (#284)
If you edited the section I mentioned in msctl, can you post it here?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MinecraftServerControl/mscs/issues/284#issuecomment-817191989, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABM56HCRYUYBIPNOK7WOTKLTICR5VANCNFSM42WUFU5A.

Does your cron call each world separately?
mscs restart <world>

Or do you restart all of them in one command?
mscs restart

My Cron calls the world mscs restart NewVal33
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Joshua Clark @.>
Sent: Saturday, April 10, 2021 5:59:36 PM
To: MinecraftServerControl/mscs @.>
Cc: TheRanker @.>; Author @.>
Subject: Re: [MinecraftServerControl/mscs] Created new world , now restart script don't work (#284)
Does your cron call each world separately?
mscs restart
Or do you restart all of them in one command?
mscs restart
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MinecraftServerControl/mscs/issues/284#issuecomment-817198362, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABM56HFWKSQX2XG72KXQHF3TICYLBANCNFSM42WUFU5A.

Precious worldnis disabled

From: Joshua Clark @.>
Sent: Saturday, April 10, 2021 5:59:36 PM
To: MinecraftServerControl/mscs @.>
Cc: TheRanker @.>; Author @.>
Subject: Re: [MinecraftServerControl/mscs] Created new world , now restart script don't work (#284)
Does your cron call each world separately?
mscs restart
Or do you restart all of them in one command?
mscs restart
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MinecraftServerControl/mscs/issues/284#issuecomment-817198362, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABM56HFWKSQX2XG72KXQHF3TICYLBANCNFSM42WUFU5A.

restart | reload | force-restart | force-reload)
# Grab the latest version information.
updateVersionsJSON
# Figure out which worlds to restart.
if [ "$#" -ge 1 ]; then
for arg in "$@"; do
if isWorldEnabled "$arg"; then
WORLDS="$WORLDS $arg"
elif isWorldDisabled "$arg"; then
printf "Unable to start the requested worlds: world '$arg' is disabled.\n"
printf "Please enable the world first with '$PROG enable $arg'.\n"
exit 1
else
printf "Unable to restart the requested worlds: world '$arg' not recognized.\n"
printf "  Usage:  $PROG $COMMAND   <...>\n"
exit 1
fi
done
else
WORLDS=$(getEnabledWorlds)
fi
if [ -z "$WORLDS" ]; then
printf "Unable to restart worlds: no enabled worlds found.\n"
exit 1
fi
# Restart each world requested, start those not already
# running.
printf "Restarting Minecraft Server:"
for WORLD in $WORLDS; do
printf " $WORLD"
if serverRunning $WORLD; then
if [ $(queryNumUsers $WORLD) -gt 0 ]; then
sendCommand $WORLD "say The server initiated a server auto-restart."
sendCommand $WORLD "say The server will auto-restart in 3 minute..."
sleep 60
sendCommand $WORLD "say The server will auto-restart in 2 minute..."
sleep 60
sendCommand $WORLD "say The server will auto-restart in 1 minute..."
sleep 60
sendCommand $WORLD "say The server is now restarting."
fi
sendCommand $WORLD "save-all"
sendCommand $WORLD "save-off"
if [ "$(echo "$COMMAND" | cut -d '-' -f1)" = "force" ]; then
forceStop $WORLD
else
stop $WORLD
fi
sleep 5
fi
start $WORLD
done
printf ".\n"
;;

Define Home and Path
HOME=/opt/mscs
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
Run mscs restart. remove# to activate
0 */8 * * *  mscs restart NewVal33

I hope you don't mind, but I edited your post with the script to have code tags so it's easier to read

restart is in 3 mins.. i just tossed ur edit into the msctl . lol

Are there any users logged into the world when it restarts?
There is a line to check if there are any users first otherwise it just restarts immediately.
if [ $(queryNumUsers $WORLD) -gt 0 ]; then

it restarts
thats not hte issue.
just no prompts are given

no notifications was given. :(

i normally have an idea what might be causing it.. but i only created a new world.. and it dont work no more :(
the crontab runs it job. restarts.. but the restart script isnt prompting any notifications of restart.

I don't see anything wrong with your modifications, it should still work.
There is some some indentation using tabs not spaces, but that shouldn't affect it.
Can you try running mscs send "say This is a test message" and see if the message shows up?

i can confirm that do indeed work.

Well dang, that's the exact same command that outputs the messages.
Maybe the tabs vs spaces does matter? Although it should matter, might as well try changing those tabs to spaces.
Also, you can send to all active worlds using mscs broadcast <command> if you wanted to.

it worked before.. perfectly.. never got edited changed or modified in any way at all.  but will not work on my new world.
commands work. thats not an issue.

You created a new world, that is the difference. I wanted to check if a simple send command worked and that a test message would show up on this new world.
Just so I have this correct, if you run mscs restart NewVal33 it restarts in 3 minutes but has no prompts in-game?
Does the the restart process, plus messages, work on another world?

root@vmi527064:~# mscs restart NewVal33
find: Failed to restore initial working directory: /root: Permission denied
The cached copy of the version manifest is up to date.
Use the force-update option to ensure a new copy is downloaded.
Restarting Minecraft Server: NewVal33

finally an error that could be used to resolve it.

find: Failed to restore initial working directory: /root:
is the main cause of all of this.

Well dangit. I have to go in a few minutes so I won't be able to help.
One last thing I can think of, revert your changes and copy the msctl script from where you downloaded it to /usr/local/bin/, then try the restart command again.
As for the find command error, I'm not sure what that means.
Sorry I couldn't help fix it before I leave for the weekend.

im not reverting any changes man.. 30 palyers on this server

I'm just talking about the changes the msctl script.
Did you make other changes to it?

i never made ANY CHANGES.. NONE

did i make any other changes??? i never made a change yet ffs.

No need to get upset.
You added those additional sleep and sendMessage commands in the restart | reload | force-restart | force-reload section of the msctl script.
I was just suggesting that you copy over the original msctl script and try that to see if it worked with the prompts, although it would be only a 1 minute warning instead of 3.
I am sorry I am not able to help any further. I will check back when I get home in a few days.

ive added thaty month ago man

i went and re-assigned a chown for minecraft:minecraft... for the resposatory i downloaded 4 weeks ago... and the current mscs folder its operating out of. ...  didnt resolve anything.

and zanik .. i also downloaded and installed your msc-gui  ... all done and on the system..  no clue how to run it, view it.. see it, ,, operate it,, comamnd it... nothing . not a stitch of info anywhere on what to do with the thing onces you run your little install.  right now its sitting on the server.. doing nothing. cause no documentation on how to use it, or even what to do with the bloody thing once its installed.  pretty sad man.   Updated on Mar 6, 2016 given its been 5 years now and you didnt even include any help in using the bloody thing? its useless.

Sorry, here are the docs
https://minecraftservercontrol.github.io

Sorry, here are the docs
https://minecraftservercontrol.github.io
The link is kinda hidden on the main repo page

Ummm. U have no useage direction of that service. No commands no idea how to run it or what to do with it.  U have installation and info of what it's for... Nothing to do with it after installation. .

I didn't notice you said mscs-gui, I thought you were talking about the mscs script only.
mscs-gui is not in a complete state so there is no documentation and there haven't been much interest in it either.

I'll most on that GitHub for advice.  But this mscs restart isn't giving notifications. Cause it says the initial folder has no permissions.  Just not properly.    Make a uninstall and reinstall will fix. But I don't know how to do that with mscs on Ubuntu 20.04
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Joshua Clark @.>
Sent: Sunday, April 11, 2021 3:26:06 PM
To: MinecraftServerControl/mscs @.>
Cc: TheRanker @.>; Author @.>
Subject: Re: [MinecraftServerControl/mscs] Created new world , now restart script don't work (#284)
I didn't notice you said mscs-gui, I thought you were talking about the mscs script only.
mscs-gui is not in a complete state so there is no documentation and there haven't been much interest in it either.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MinecraftServerControl/mscs/issues/284#issuecomment-817346338, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABM56HDXIUBIW24VELOPNPDTIHPDNANCNFSM42WUFU5A.

cd into the directory where you cloned/downloaded the script and run `sudo make clean, that should remove the files

And just do the get clone part again after? Don't need to do the full setup or anything ? As the clone isn't in the same folder as mscs is running from
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Joshua Clark @.>
Sent: Sunday, April 11, 2021 3:34:46 PM
To: MinecraftServerControl/mscs @.>
Cc: TheRanker @.>; Author @.>
Subject: Re: [MinecraftServerControl/mscs] Created new world , now restart script don't work (#284)
cd into the directory where you cloned/downloaded the script and run sudo make clean, that should remove the files
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MinecraftServerControl/mscs/issues/284#issuecomment-817347613, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABM56HB6EXSQCHSMRLQT7NDTIHQD5ANCNFSM42WUFU5A.

Correct, you would just be re-installing the script files from the folder where you downloaded the script.
The /opt/mscs folder is your data folder.
The makefile copies the script files to /usr/local/bin and some other files elsewhere, you can see what it does in the Makefile https://github.com/MinecraftServerControl/mscs/blob/main/Makefile
Looking the makefile closer, I think you could just run sudo make update and that should re-copy the files again.

Ok. So the repo I've downloaded before was in home/theranker/Minecraft.  And opt/mscs. And in the /use/bin.
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Joshua Clark @.>
Sent: Sunday, April 11, 2021 3:43:30 PM
To: MinecraftServerControl/mscs @.>
Cc: TheRanker @.>; Author @.>
Subject: Re: [MinecraftServerControl/mscs] Created new world , now restart script don't work (#284)
Correct, you would just be re-installing the script files from the folder where you downloaded the script.
The /opt/mscs folder is your data folder.
The makefile copies the script files to /usr/local/bin and some other files elsewhere, you can see what it does in the Makefile https://github.com/MinecraftServerControl/mscs/blob/main/Makefile
Looking the makefile closer, I think you could just run sudo make update and that should re-copy the files again.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MinecraftServerControl/mscs/issues/284#issuecomment-817349002, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABM56HFTJ2JPNPLT6ZYRNYLTIHREVANCNFSM42WUFU5A.

@TheRanker, @Zanix and myself are not paid to help you. You have paid nothing for the work we have done. Your attitude is unwanted. MSC-GUI is a Proof -Of-Concept and is not meant for production servers.
I'm closing this issue as not our bug. User error.

I've banned @TheRanker from commenting for 7 days.  Additional abuse beyond that period will result in a permanent ban. I will not put up with this kind of abuse.


merge: stage to master

:tada: This PR is included in version 0.48.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Gracefully handle attachments on android

Attachment messages are always put at the end of the list, with no content.
Once you get into this state, there is no way out because android does not support deleting messages.
We should fix this ASAP  so that we can release on the app store and sales folks have already started using this. We can add full attachment support later.

Steps to reproduce

Create an image on iPhone
Continue creating messages
See that the message is blank (which might be OK) but it always shows at the bottom of the list

closed by https://github.com/getditto/demoapp-chat/pull/57


Sentence doesn't make sense

[The following sentence doesn't make sense: "
Each column (also known as an attribute) within a table represents a column in that table."
]

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

ID: 5b903798-2033-be36-079a-babe7586981e
Version Independent ID: d588611a-a950-134e-6738-10e8f3899f25
Content: Tables and metadata in Microsoft Dataverse - Power Apps
Content Source: powerapps-docs/maker/data-platform/create-edit-metadata.md
Service: powerapps
Sub-service: dataverse-maker
GitHub Login: @Mattp123
Microsoft Alias: matp

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

Thank you for reaching out. Documentation has been fixed.


Periodically seeing "unclosed face definition" in debug buffer

Hello,
Let me first start by saying thank you for the wonderful software.  kak-lsp is the part of the kakoune ecosystem that, for me, makes the editor feel on par with the tools integrations provided by something like vscode.
I currently only use kak-lsp with Typescript (via typescript-language-server).  Everything seems to work as expected, however sometimes I don't see the info box popup as expected (when I have :lsp-autohover-enable).
Given the following code:
const layer = {
  src: "dark.png",
  log: true
};

When I place my cursor over any part of the layer variable name, then I end up seeing the following in the *debug* buffer:
error running command 'eval -client client0 -verbatim -- lsp-show-hover 3.11 %§{InfoBlock}const layer: {
    src: string;
    log: boolean;
}{InfoDefault}§ %§§': 1:1: 'eval': 1:2: 'evaluate-commands': 1:1: 'info': unclosed face definition

It seems pretty clear to me that this is due to my language server (typescript-language-server) wanting to send back text that includes {...}, which then causes Kakoune to interpret it as a markup string.  I'll also note that I've seen this happen with using Deno as a language server as well.  My guess is that it happens with any language server that ever wants to return some text with something like {Foo bar baz} in it.
So my question is....am I correct in that this is just a lack of character escaping issue?  And....any recommendation as to how to deal with it?  I found the kakoune docs for how to actually escape them, but I'm not sure exactly if kak-lsp has any support for doing this...maybe this isn't considered the domain of kak-lsp?

Simple escaping issue - the argument to lsp-show-hover must be a valid markup string. Thanks for reporting!
we still don't have a typescript server in the default config. We should probably add at least the most popular one, I'm not sure which one that is

Hot damn that was fast turn around! Thank you so much @krobelus!


Update sbt-typelevel-no-publish to 0.5.2

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

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

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

labels: sbt-plugin-update, early-semver-major, semver-spec-minor, version-scheme:early-semver, commit-count:1

Superseded by #250.


custom work

Description
Reference issue
Fixes #...

I think it's a bad idea to commit so many large movie files to this repo. Please find a way to make this PR not include large, unnecessary video files, it will greatly increase the library size; alternatively, since this is just an "example", you could move the code and all the videos to an unrelated repository.

Thanks for your interest in helping with ion-sdk-go! I don't mean to be harsh but - In general, this PR adds a lot of small changes that I think would be better if you split up into smaller PRs that were more related - like changing log.Error to log.Debug without a good explanation/justification. Maybe those kinds of changes are appropriate, but they don't belong in one-big-lump PR together!
In my humble opinion, each Example you submit (or modify) should be its own PR.

@leewardbound i am sorry, this PR was submitted my mistakes. i didn't release this got submitted

No worries, I am sorry if I came off tough, hope the feedback was helpful 😊

yes. i submitted a new PR. that is genuine :) hope that helps


Doesn't work with YouTube Music

Summary
The addon can't differentiate and marks all music as ads. This is a very specific use case only on music.youtube.com.
Reproduction
Steps to reproduce the behavior:

Go on music.youtube.com
Click on any music track

Expected Behavior
The music plays and the ads are skipped.
Actual Behavior
The music gets muted and sped up.
Screenshots

Environment

OS: Windows 10
Firefox Version: 126.0.1
Addon Version: 1.58

Thanks for the detailed description! I pushed a fix that should solve the issue in the current version 1.59. Let me know if that solves it for you as well.

Seems fixed. I can click on any music and only the ads are skipped. Great work!


bump compiletest

@bors r+

:pushpin: Commit 93027da5ed4ce1e98b39ec9b35ca93961ef8a723 has been approved by RalfJung

:hourglass: Testing commit 93027da5ed4ce1e98b39ec9b35ca93961ef8a723 with merge c85ba0a16677c455d5e424510f94e40c255aafc5...

:sunny: Test successful - checks-travis, status-appveyor
Approved by: RalfJung
Pushing c85ba0a16677c455d5e424510f94e40c255aafc5 to master...


No support for precondition in lifecycle

terrascan version: 1.18.3
Operating System: Windows

Description
When I'm trying to scan TF I got error:
Unsupported block type; Blocks of type "precondition" are not expected here
What I Did
I have different preconditions in resources and data sources and It works since terraform 1.2
lifecycle {
    precondition {
      condition     = "condition" == true
      error_message = "`condition` must be `true`."
    } }

I run command:
terrascan scan --non-recursive -i terraform -t azure  --show-passed -v

Fails inside trunk for me with the following error:
trunk_cli_version: 1.19.0
title: terrascan exited with exit_code=1
report:
  - terrascan exited with exit_code=1
  - linter:
      command: |
        /Users/maximveksler/.cache/trunk/tools/terrascan/1.18.11-6e9db740d172cf99f6895c7ca051b76b/terrascan scan -i terraform --iac-file terraform/modules/aws/s3/main.tf --output sarif
      stdin_path: (none)
      run_from: /private/var/folders/7r/1vmh1cxs2cbgm__r8cr62z0c0000gn/T/trunk-501/v1y1OR
      timeout: 10m
      rerun: (cd /private/var/folders/7r/1vmh1cxs2cbgm__r8cr62z0c0000gn/T/trunk-501/v1y1OR; env -i PATH=/Users/maximveksler/.cache/trunk/tools/terrascan/1.18.11-6e9db740d172cf99f6895c7ca051b76b:/Users/maximveksler/.cache/trunk/tools/terrascan/1.18.11-6e9db740d172cf99f6895c7ca051b76b HOME=/Users/maximveksler /Users/maximveksler/.cache/trunk/tools/terrascan/1.18.11-6e9db740d172cf99f6895c7ca051b76b/terrascan scan -i terraform --iac-file terraform/modules/aws/s3/main.tf --output sarif)
      affects_cache:
        []
      direct_configs:
        []
      exit_status: exited
      exit_code: 1
      stdout: (none)
      stderr: |
        2024-01-14T16:42:31.698+0200	error	cli/run.go:141	scan run failed{error 26 0  failed to load iac file '/private/var/folders/7r/1vmh1cxs2cbgm__r8cr62z0c0000gn/T/trunk-501/v1y1OR/terraform/modules/aws/s3/main.tf'. error:
        /private/var/folders/7r/1vmh1cxs2cbgm__r8cr62z0c0000gn/T/trunk-501/v1y1OR/terraform/modules/aws/s3/main.tf:109,5-17: Unsupported block type; Blocks of type "precondition" are not expected here.
        }

    parser: |
      (none)


How to update a device's certificate in IoT Hub?

Once the certificate has been updated on the device, how do I update the device's thumbprints in IoT Hub? The Azure Portal doesn't seem to allow editing the Primary or Secondary thumbprint of a device, is there a command line option? Or is it feasible somehow from the Azure Portal?
I expect it should be possible to update the thumbprints during a device's lifetime, without deleting and re-creating it in IoT Hub (and thus losing its device/module twin data, etc), for various reasons, for example:

Certificate expired
Private key is suspected to be compromised

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

ID: 94792ff1-5976-90f4-5092-0d8d8ff01635
Version Independent ID: d65482d2-64cc-56b1-c52a-b3ddde07b205
Content: Manage device certificates - Azure IoT Edge
Content Source: articles/iot-edge/how-to-manage-device-certificates.md
Service: iot-edge
GitHub Login: @kgremban
Microsoft Alias: kgremban

Hello @ckarrasalithya Please refer to the REST API document for these operations.
Docs IoT Hub Reference Certificates Overview

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.
Please also do visit Microsoft Q&A the home for technical questions and answers at Microsoft.


Issue with nested Boxes in 5.1.0

from box import Box

parent_box = Box()

keys = ["a", "b", "c"]

for key in keys:
    sub_box = parent_box[key] = Box()
    sub_box["test"] = "test"
    print(sub_box)

print()
print(parent_box)

Output with version 5.1.0:
{'test': 'test'}
{'test': 'test'}
{'test': 'test'}

{'a': {}, 'b': {}, 'c': {}}

Output with version 4.7.3:
{'test': 'test'}
{'test': 'test'}
{'test': 'test'}

{'a': {'test': 'test'}, 'b': {'test': 'test'}, 'c': {'test': 'test'}}

I will write out a bit more detail about why this happens in a bit and make sure it is better covered in the wiki, just wanted to reply quick that this is happening as designed and won't be able to be changed. However it can be prevented if you pass in box_intact_types=[Box]   to parent_box = Box(box_intact_types=[Box])
What happens is every time an object of type dict or list is added to the box, it has to be destructively recreated to ensure everything is linked up properly within the box to use all its special sauce, unless specifically told otherwise.
sub_box = parent_box[key] = Box()  is equal to:
temp_var = Box()   # id ...336

# link that pointer to another variable
sub_box = temp_var  # id ...336

# copy object with id ...336 and create new pointer
parent_box[key] = temp_var  # id ...825

The possible workaround are

use box_intact_types
use default_box if applicable
avoid chained assignment when adding objects to box


Broken build for ledger-kusama

Using the current master branch seems to break the zemu tests.
The error:
launcher: failed to emulate syscall 0x600070c5
vnc_server: readall: connection closed

Going back one commit, it works without problem.
This has been seen i when running zemu test in ledger-kusama repo.

Ok, that's interesting! in speculos code we should we able to find what 0x600070c5 is

Ok, that's interesting! in speculos code we should we able to find what 0x600070c5 is

it seems here:
https://github.com/LedgerHQ/speculos/blob/239171e29a831fe601f6968b7dd34bccc60d818a/sdk/bolos_syscalls_1.6.h#L224

it seems here:
https://github.com/LedgerHQ/speculos/blob/239171e29a831fe601f6968b7dd34bccc60d818a/sdk/bolos_syscalls_1.6.h#L224

that is strange... SYSCALL_os_setting_get_ID_IN

that is strange... SYSCALL_os_setting_get_ID_IN

Same for ledger-polkadot...
I m not sure how to fix this. Do we need to update speculos emulator ?

Same for ledger-polkadot...
I m not sure how to fix this. Do we need to update speculos emulator ?

Well it seems to work fine if I build the app using make buildS instead of just make.

Well it seems to work fine if I build the app using make buildS instead of just make.

Closing this.
What was happening is that make built both nano s and nano x but the nano x version was replacing the nano s version and I didn't see it.
Maybe we could have a verbose mode. It would help to have a better view of what is being build and the verbose mode would be use for debugging the script.


lowering: support new interface of messaging

If messaging exposes the "getSelf" method, call it to obtain
the account to use to lower "return", passing the principal where
the program will be sent.
This allows the messaging interface to choose the correct return
address, based on who is executing the program.
This is related to https://github.com/Stanford-Mobisocial-IoT-Lab/thingengine-core/pull/42

Yeah this patch needs to go in first, before the tests in thingengine-core can pass

Pull Request Test Coverage Report for Build 271

2 of 3 (66.67%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.009%) to 78.323%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/ast/api.js
2
3
66.67%

Totals

Change from base Build 270:
-0.009%

Covered Lines:
6141

Relevant Lines:
7512

💛  - Coveralls


[ALLUXIO-2619]i changed the line62 into '/** Logic time out. */'

https://alluxio.atlassian.net/browse/ALLUXIO-2619)

https://alluxio.atlassian.net/browse/ALLUXIO-2619

alluxio-bot, check this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15169/
Test PASSed.


Openbazaar fails to start with protobuf < 3.2.0

On a Ubuntu 16.04 install, I run the following command:
python openbazaard.py start --testnet
I receive the following error:
Traceback (most recent call last):   File "openbazaard.py", line 11, in <module>     from api.ws import WSFactory, AuthenticatedWebSocketProtocol, AuthenticatedWebSocketFactory   File "/home/ben/OpenBazaar-Server/api/ws.py", line 17, in <module>     from dht.node import Node   File "/home/ben/OpenBazaar-Server/dht/node.py", line 8, in <module>     from protos import objects   File "/home/ben/OpenBazaar-Server/protos/objects.py", line 17, in <module>     import countries as countries__pb2   File "/home/ben/OpenBazaar-Server/protos/countries.py", line 36, in <module>     type=None),   File "/home/ben/.local/lib/python2.7/site-packages/google/protobuf/descriptor.py", line 652, in __new__     _message.Message._CheckCalledFromGeneratedFile() TypeError: Descriptors should not be created directly, but only retrieved from their parent.
This is a known issue for people using protobuf 3.
https://github.com/ethereon/caffe-tensorflow/pull/105
Solution is to upgrade to latest version using this command:
pip install --upgrade protobuf --user

I just tried with protobuf 3.3.0 and it still has the same error.


Formatter undocumented deviation: wrapping with annotation only and comment

Black formatting
class Animatable(Protocol):
    """Protocol for objects that can be animated."""

    animation_data: bpy.types.AnimData  # TODO(jonathan): Change to Optional when fake-bpy-module is updated

Ruff formatting
class Animatable(Protocol):
    """Protocol for objects that can be animated."""

    animation_data: (
        bpy.types.AnimData
    )  # TODO(jonathan): Change to Optional when fake-bpy-module is updated

Ruff 0.0.289 with line-length 100
I prefer Black formatting

I can see how Black's formatting may seem better but Black's code exceeds the configured line width of 100, whereas Ruff's formatting stays in the limit.
Black is also a bit inconsistent here because it uses the same formatting as ruff if you change this to an assignment:
animation_data = (
    bpy.types.AnimData
)  # TODO(jonathan): Change to Optional when fake-bpy-module is updated

I propose that we stick to Ruff's layout because:

It is more consistent with other syntax
It stays within the configured line length

Closing as duplicate of ##7322


Moved files to agree with ToC reorganization.

This PR should be merged before napari/napari.github.io#299
Description
Creates new docs structure to agree with the new ToC organization. This also touches docs/copy_docs.py::update_toc, to make sure it doesn't skip toc items.
Type of change

[ ] Bug-fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

References
Addresses #3390
How has this been tested?
To test locally, you can:

Clone both napari/napari and napari/napari.github.io
Go into the napari/napari folder and run$ pip install -e '.[all]'
$ make docs

View changes rendered in "_build/html"
Run python docs/copy-docs.py (this will copy the appropriate sources into the napari/napari.github.io folder and update the napari/napari.github.io/_toc.yml file
Go into the napari/napari.github.io folder and run$ yarn dev

Confirm that this command renders the appropriate outputs.

Note that napari/napari.github.io#299 needs to also be merged to render the full documentation reorganization.
Final checklist:

[x] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If I included new strings, I have used trans. to make them localizable.
For more information see our translations guide.

There are a number of files here that appear to be deleted instead of moved. What's the reason for that?

There are a number of files here that appear to be deleted instead of moved. What's the reason for that?

A few files were actually just empty, with include directive to other files - see, for example https://raw.githubusercontent.com/napari/napari/main/docs/developers/code_of_conduct.md
I deleted those and left only the actual files to remove redundancy.

Sorry @GenevieveBuckley if i pulled trigger too fast on this merge. let me know if you still have any concerns, my bad that i was a bit quick here

I think it's ok, no worries here

Thank you folks - now, I am hoping at some point the copy-docs script will be triggered and we'll get some new files committed to napari.github.io - when that happens, it would be better to merge https://github.com/scipy/scipy/issues/3983 as soon as possible so the organization is coherent and all files show up in the page.

It looks like the workflows errored out 😢
Copy Doc Sources
https://github.com/napari/napari/runs/4448191147?check_suite_focus=true
While it seems like this one passed, there's an error at the bottom of the update repo step:
fatal: unable to access 'https://github.com/napari/napari.github.io/': The requested URL returned error: 403
remote: Permission to napari/napari.github.io.git denied to napari-docs.
fatal: unable to access 'https://github.com/napari/napari.github.io/': The requested URL returned error: 403

@sofroniewn did we remove access for the napari-docs account after the ninja merge in https://github.com/napari/napari.github.io/pull/285?
Build & Publish Docs
I'm not too familiar with how it works, but it has to do with xvfb:
xvfb-run: error: Xvfb failed to start

Hm that was not related to my changes, perhaps it has to do with the build errors/segmentation faults I am seeing locally?
Also, might be related to #3497

@sofroniewn did we remove access for the napari-docs account after the ninja merge in napari/napari.github.io#285?

yup we removed, so i'm guessing i need to add it back? maybe @codemonkey800 we need to look into this together tomorrow. seems like blocking permissions was too optimistic. i can add them back

I think re-adding would be the fastest (but temporary) solution for now. But I do think this is something we'll need to tackle in #3529

So after updating the accounts and secrets, it looks like the build passed this time:
https://github.com/napari/napari/actions/runs/1556261973
https://github.com/napari/napari.github.io/commit/6081028bb14473bd845f4a38973ea7bdfeceeb21
However, it looks like the TOC isn't using the newly added properties:
https://github.com/napari/napari.github.io/blob/6081028bb14473bd845f4a38973ea7bdfeceeb21/_toc.yml

Yay! Thanks for checking that, @codemonkey800 ! Will continue on napari/napari.github.io#299.


Install on OS X 10.11 without wrestling eventmachine build

The package detection and configuration for eventmachine on OS X 1.0.9 has gotten smarter and doesn't need extra flags any longer for the native extension to build.
See eventmachine/eventmachine#668 for details.

@sj26 I had to remove the Gemfile.lock after updating bundler; looks like the bundler bug was also tripping up other open PRs for mailcatcher on Travis. Not sure what the story is about the .lock file being version-controlled, I think general rule is gems don't bring it along, but that might be different for command line tools? Tell me if any other change is needed before you see mergability.

Gemfile.lock has been removed in 433fad4e and we're now using new travis build infrastructure in 0c1a1e41.


Add reference step to set up selfservice payment

@bahmady I tried to copy the style of the previous steps, but please change if it doesn't meet the style guide or you think that it could be clearer.

@soniaturcotte thanks for doing this.

Also, I think we need to change
"Create a payment link

Sign in to your GOV.UK Pay account.
Select Create a payment link in the Dashboard."

to
"Create a payment link
Sign in to your GOV.UK Pay account.
Select Create and manage payment links in the Dashboard."

I've made a couple of changes based on going through creating a payment link. Let me know what you think.

@soniaturcotte shall I merge this? are the Pay docs deployed manually or by CI?

We have CI, I've merged. Thanks both!
On 20 June 2018 at 11:37, Bean<EMAIL_ADDRESS>wrote:

@soniaturcotte https://github.com/soniaturcotte shall I merge this? are
the Pay docs deployed manually or by CI?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/alphagov/pay-tech-docs/pull/101#issuecomment-398704453,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AS3CWerZMEfjNNxc7rKPCWtJ2WspFc6eks5t-iXXgaJpZM4Utbv5
.


Upstream Changes of 2.53b

This addresses #29 :
I have tried to merge the upstream changes as well as I could.
The main changes were a bit of docu and the License header in each file (it is now seperated from the file description).
Hope nothing else broke :)

thanks for the effort!
there is a lot the google guys missed in the documentation which I added by hand and your pull request reverses stuff that we put in :) (e.g. changes to  docs/QuickStartGuide.txt)
As I only want some of the changes anyway I did it by hand already, but forgot to commit ... sorry!

Welp sorry for the mess then ;)
It could be nice to have the upstream commits in afl++ in case they start adding things

yeah that would be. but dunno how that could be done without starting a new repository.
but lets see if they really add something. I kinda doubt that. the next step would be to basically rework how afl works


Form is refreshing after submit

Hi, I have a simple stateless form component and after I click Login button my page is refreshed.
How can I prevent my page from refreshing?
I use redux form 6 rc1
import React, { Component } from 'react';
import { Field, reduxForm } from 'redux-form';

const validate = values => {
  const errors = {};

  if (!values.email) {
     errors.email = 'Required'
   } else if (!/^[A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,4}$/i.test(values.email)) {
     errors.email = 'Invalid email address'
   }

   return errors;
}

const LoginForm = (props) => {
  const { handleSubmit } = props;
  return(
    <form onSubmit={handleSubmit}>

        E-mail
        <Field name="email" component="input" type="text" />
        <button type="submit" className="button button--green">Login</button>

    </form>
  );
}

export default reduxForm({
  form: 'login',
  validate
})(LoginForm);

same here

@wedranb Do you receive form values in handleSubmit?
I got a lot of weird getters and setters instead of values. What is even more interesting is that looks like arguments are mutating, because pay attention to object "preview" on top, it's differs from what we see after revealing this object in console

@NeXTs I get the same thing.

Then you could temporarily use values.preventDefault() at least to prevent page refreshing
but I still can not handle this issue with values, that's madness

That is very bizarre. I'm not seeing that at all. For example, the submit validation example doesn't exhibit this behavior. handleSubmit really should be doing the preventDefault() for you.
You don't see this if you go back to 6a15?

Sure, I've tried many various releases, neither 6a15 or 6a6 helps
I've tried react-hot-loader v1, then v3, then come back to v1
I managed my dependencies to be exactly like in your example, but without luck
I have a hunch that this is due to the react-router or redux-auth-wrapper, checking right now

@erikras Well, I'm tired
Somehow by playing with various releases I handled weird getters/setters in arguments, so there are always that object from 'preview' now.

Please take a look at this example in your free time, I have no more ideas what could be wrong as for this moment.
npm i
npm start
visit: http://localhost:3000/example
there would be single input field and submit button by clicking which I got response that I attached as image.
component path
src/components/Example.js

Hm, looks like redux-form differs between that one in examples and published into npm or something
@erikras In theory if I set up<EMAIL_ADDRESS>example on my local machine, then go to /examples/material-ui and do
npm uninstall redux-form -S
npm i<EMAIL_ADDRESS>-S
npm start
this should works seamlessly, as soon as plugin's sources expected to be same, right?
but it does not, I get various errors. first of all react-hot-reload suddenly became unhappy

after commenting whole if (module.hot) {...} block, I get next error
MaterialUiForm.js:68 Uncaught TypeError: Cannot read property 'label' of undefined
here -> here
and console.log of field argument in renderTextField shows this

@NeXTs The source code that is identical to the npm published lib is going to be under the specific tag for that version. https://github.com/erikras/redux-form/tree/v6.0.0-rc.1/ That goes for the examples as well.
I have already made changes to the examples in the v6 branch that will make it not work with the version published on npm.

ok nevermind, things became much better after updating<EMAIL_ADDRESS>from alpha to beta version.
@wedranb try npm i<EMAIL_ADDRESS>this should help

I'm having the same page reload after submitting with "redux-form": "6.0.0-rc.4"
Is it normal we have to trigger event.preventDefault() manually ?
If i don't do this, I get a url which looks like this after the page reload:
/register?username=Jon&email=Jon%40do.com&age=42

I suppose you have also incorrectly use onSubmit function.
you should pass your submit function from parent component to form component named exactly onSubmit, but inside form component you should do onSubmit={handleSubmit}
so that your submit function wrapped in redux-form's submit function which prevents form submittion and does all other necessary job

Thanks a lot 👍  I clearly missed that part in the documentation

You're welcome!
If you'd only knew how much time I spent on it... :D

I had the same issue with my page refreshing on form submit.
That was caused by me using passing handleSubmit instead of onSubmit in mapDispatchToProps. It was not very clear from docs for me that it would be the case.

I still can't resolve the issue. I don't understand solution too well since I'm new to React. Can someone provide their code or a deeper explaination? Thanks!

@aspdev91, https://github.com/lakesare/memcode/search?utf8=✓&q=onSubmit
so we pass onSubmit in props to our component, BUT use this.props.handleSubmit in our component to get what we passed.

Thank you, but I still can't quite resolve it.. It says onSubmit is undefined. I am not exporting the code to any other modules or using hot reloading etc. Thanks!
`
class Form extends Component {
handleSubmit(values){
console.log(values);
}
componentDidMount() {
this.refs.name            // the Field
.getRenderedComponent() // on Field, returns ReduxFormMaterialUITextField
.getRenderedComponent() // on ReduxFormMaterialUITextField, returns TextField
.focus()                // on TextField
}
render() {
const { handleSubmit, pristine, reset, submitting } = this.props
return (

Submit
Clear

)
}
}
export default reduxForm({
form: 'example',
},null,{ onSubmit})(Form)`

@aspdev91, you must define onSubmit function somewhere. I don't feel like this belongs to this issue, you should ask a question on stackoverflow maybe.

not somewhere but in parent's component where you define this Form, like
<Form onSubmit={() => console.log('yaa')} />

I get the same problems (refreshing, if I don't manually call preventDefault and some weird object instead of the formdata).
I'm using<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>and for hot-reloading<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(webpack 2.1.0-beta.22)
the object I get instead of the data contained in the Form looks flatly like this
Proxy {dispatchConfig: Object, _targetInst: ReactDOMComponent, nativeEvent: Event, type: "submit", target: form.entireForm__app-components-FileUploadFrame-styles__dzso_…}
and has a lot of getters/setters inside
For submitting I do
<form className={styles.entireForm} onSubmit={handleSubmit}>
....
  <button className={styles.submitButton} type="submit">Submit</button>
</form>

Thank you in advance for any help/advice

@AndreasHoermandinger pay attention to https://github.com/erikras/redux-form/issues/1270#issuecomment-239636759

@NeXTs I got
  render() {
    const { handleSubmit } = this.props;

Is this the problem? (in the examples only functions are used, I am using a class)
where handleSubmit is passed to props from the parent, still happens. I circumvented this by preventDefault and selecting the fields, but according to what's written in the docs that should not happen

@NeXTs I am still seeing this issue on latest redux form in ie11.
parent component has
<LoginForm onSubmit={this.handleSubmit} />

and form component has
const LoginForm = (props) => {
  const { handleSubmit, submitting, error } = props
  return (
    <form onSubmit={handleSubmit} className="Login-Form">

@kellyrmilligan at ie11 only?

yep, as far as I can tell. I haven't had a good chance to look, but where is it calling prevent default on the submit event?

I see where it is doing this now. will check to see if the event is different in IE11 for some  reason.

it looks like nothing is actually working in ie11, this is on browserstack anyway. no validations are running, etc.

@kellyrmilligan It looks as though the prop name in your parent component is incorrect.
<LoginForm onSubmit={this.handleSubmit} />
should be
<LoginForm handleSubmit={this.handleSubmit} />

I was struggling with this issue as well but really reading https://github.com/erikras/redux-form/issues/1270#issuecomment-239636759 helped me out.
It appears reduxForm takes your passed onSubmit prop, wraps it and injects it into the wrapped form component as handleSubmit. See: https://github.com/erikras/redux-form/blob/master/src/reduxForm.js#L319
Gotchas:

onSubmit is also still passed as a prop it seems. If you use that as your handler to the form tag, then you are passed the dom event to the handler func instead of the map of form values.
If you pass the handler using a prop names handleSubmit (instead of onSubmit) then handler appears to be called with the event similar to the above.
If you leave off both onSubmit and handleSubmit from your form, the submission with correctly throw "reduxForm.js:125 Uncaught Error: You must either pass handleSubmit() an onSubmit function or pass onSubmit as a prop(…)"

Quick breakdown of the goods and bads for clarity:
<SampleForm onSubmit={showResults} /> // Good
<SampleForm whatever={showResults} /> // correctly throws error for missing expected prop
<SampleForm handleSubmit={showResults} /> // Bad under normal assumptions.  Won't error, form causes the page reload. Sadness ensues`

Then inside of the SampleForm class:
<form onSubmit={props.handleSubmit}>  // Good assuming handleSubmit wasn't directly passed in mistakenly.
<form onSubmit={props.onSubmit}> // Bad, but won't error, form causes the page reload.

Hopefully that breakdown saves some headscratching.

Has anyone been able to see if ie11 is working?  My form works everywhere but there

I could not get this to work. Ended up using event.preventDefault() in my mapDispatchToProps

Guys, the main reason for the confusion here is that redux-form actually injects handleSubmit via a prop. You do not need to pass it in as a prop - if you do, you will overwrite redux-form's function.
Instead, you only need to pass in an onSubmit prop which will automatically get called by redux-form after validation is successful with the form values. If you do not have validation then your onSubmit function will be called immediately. I'll admit that this is pretty confusion.
Here is a reference to an article that made me realize that. Check out the code sample.

just got back to testing this out again. can't pin down what change made the fix, but in between 6.1.1 and 6.2, ie11 was throwing an error in 6.1.1 const must be initialized, and it was in a for loop that was a polyfill for object.assign. it was for (const key in source), and now it's for (var key in source). so whatever you did, thanks!
I can now actually use this library :)
in the compiled reduxForm.js, it's line 13. this seems like a change in babel pherhaps? or corejs?

https://github.com/erikras/redux-form/issues/1270#issuecomment-239636759 solved it for me. I moved the submit function out of the form class into the parent class and supplied it as onSubmit property, although I find it very counter intuitive that this necessary. You should be able to do the same thing within the form class itself. But this leads to the page refreshing (even on submit failure)

I had the same problem, inside your handlesubmit function put evt.preventDefult, so your function should look like: handleSubmit(evt) { evt.preventDefault() ....

Please, don't pass onSubmit prop through. Rename that if you need it, but make it undefined on the form component. It makes sense when you get it but until you do, there goes your evening..
Better yet, replace it with something like
onSubmit() {
  alert('Do NOT use <form onSubmit={props.onSubmit}>, if you do you'll get cancer! Use <form onSubmit={props.handleSubmit}> instead');
}

This had me stumped for a while.  I finally resolved it by passing the default handleSubmit prop my own handleSubmitForm function
import React, {Component} from 'react';
import {Field, reduxForm} from 'redux-form';
class MyForm extends Component {
constructor(props) {
super(props);
this.handleMyFormSubmit = this.handleMyFormSubmit.bind(this);
}
handleMyFormSubmit({val1, val2}) {
console.log("Form values", val1, val2;
}
render () {
const {handleSubmit} = this.props;
return (

Submit

);
}
}
export default   reduxForm({
form: 'myForm',
destroyOnUnmount: false,        // <------ preserve form data
forceUnregisterOnUnmount: true,  // <------ unregister fields on unmount
validate
})(Signin);

This is an extremely confusing problem, and required quite a few re-reads through the comments above. This should definitely be rethought, refactored, or at least have updated documentation that clarifies this problem. If anyone gets to the end here and still doesn't understand I'll try another explanation.
If you were like me, then your first thought from reading the docs might be to try:
someFuncInsideComponent(values) {
  console.log('got the values')
}

render() {
  return (
    <form onSubmit={this.someFuncInsideComponent}>
    ...

This will cause the refresh problem. That is because you are not supposed to put your function inside onSubmit. You need to write <form onSubmit={handleSubmit}> and only that. This is because redux-forms injects the handleSubmit function, and has nothing to do with your code.
In order to run a function with the form results, it needs to sit outside the component where you declare <form>. It also needs to be passed in as onSubmit={yourOuterFunc}. It might look something like:
someFunction(values) {
  console.log('got the values')
}

render() {
  return (
    <MyCustomForm onSubmit={this.someFunction}/>
  )
}

Where inside MyCustomForm you have declared the line above <form onSubmit={handleSubmit}>.
The confusing bit is that both the inner and outer function must both use onSubmit, but the inner one needs to be written a specific way. I feel like the examples above where they explicitly call handleSubmit inside their form control makes a lot more sense when read, and lets you handle the values inside your form control, and not be forced to use a parent function.

I had the same issue, wasted some hours trying to figure out, I think it should have more visible since you have to do EXACTLY like @NeXTs said

I also needed to declare onSubmit function in my form class and found the solution of @mcverter working fine. As this is what most people here are looking for I believe this should be the recommended solution.

why the hell https://github.com/erikras/redux-form/issues/1270#issuecomment-260159552 is not in docs?
spent a few hours on this

I agree with @Stas-Buzunko. It should be made clear in the docs that the handler needs to be passed in from outside the form component. I had assumed that this functioned the way most other components do and I could just pass this.handlerFunction() to onSubmit.

+1 for making this clear in the docs and examples, I also spent an hour or so on it :-)

PRs are welcome.

+1 for marking this clear in the docs. I expected that it works like all others props that I can set. I sped fool day to resolve this problem. Oh...

Had the similar issue with onSubmit and handleSubmit.
component:
render() {
    const { handleSubmit, onSubmit } = this.props;
    return (

      <form onSubmit={handleSubmit(onSubmit)}>...</form>);
}

container
import { bindActionCreators } from 'redux';
import { reduxForm } from 'redux-form';
import { connect } from 'react-redux';

const mapDispatchToProps = dispatch =>
  bindActionCreators({
    onSubmit: submitForm,
  }, dispatch);

export default connect(undefined, mapDispatchToProps)(reduxForm({
  form: 'formName',
})(MyComponent));

action creator
import { formActionType } from '../constants/actionTypes'; //  'SUBMIT_FORM'

export const submitForm = values => ({
  type: formActionType.SUBMIT_FORM,
  payload: values,
});

Hope that the example I've provided can help someone to save some time.
My question is how this part handleSubmit(onSubmit) can be improved in my code. Thanks!

@gustavohenke if I were to submit a PR, would FAQs be the most appropriates section for this common problem?

I haved faced the same problem and that's my fault to inject wrong name in Redux form.
Thank you :) :)

I solved this issue by throwing a 'Submission Error' in my action creator. Because my API would send a status '200' when there was an issue with the user's login input, the form would submit and then refresh because my authentication would kick it back.
The example from the Redux-Form api is here.
I went ahead an put it in my action creator in the second ' .then ' statement I set up.
.then(response => {
  if (the input is valid) {
                    dispatch(loginSuccess())

                } else {
                   dispatch(renderErrorMessage(however you pass the error message from the response))
                    throw new SubmissionError(login_response.error_message) <--stops the form from submitting and allow me to display my error message

}
}

This I bound my form handler to the handleSubmit:
 <form onSubmit={handleSubmit(this.handleFormSubmit.bind(this))}>

I had no issues with my data not being accessible in my action creator/in the component.

This all works fine on certain browsers, but in IOS safari it still refreshes the page. Anybody have a solution for this?

Confirmed broken, also on android... I have a really basic form:
<form onSubmit={this.props.handleSubmit(onSubmit)}>
	...
	<button type="submit" onSubmit={kers}>Submit</button>
</form>

handleSubmit

Thanks, this solved my problem.

Guys, another one here spending hours in this.
For the sake of simplicity, flexibility, modularity, and good practices, I just WANNA declare the submit handler INSIDE the child form component, and not pass it as a prop from the parent component.
Well, as you see, no way to do it.
This is not good coding.
The parent is a main app component that will be abstracted to include, then, different child components with different functionalities as needed, and has nothing to do with form onsubmit handlers.
This leads to non-semantic code.

@dsldiesel
<form onSubmit={props.handleSubmit(formData => {
  // this is your submit function
})}>
  {/* ... */}
</form>

@iamandrewluca Thanks!
Interesting, this is a workaround.
I'd sware this is not known by other coders above who complaint as I did :)

@dsldiesel This is not a workaround :slightly_smiling_face:
https://redux-form.com/8.2.2/docs/api/props.md/#-code-handlesubmit-eventorsubmit-function-code-


Clean up yaml files to ensure they pass the linter

As a developer, I want to make sure my files pass the linter. At present the linter is working by not passing the yaml files.

[ ] Edit all scripting files for style conformation
[ ] Once yaml files pass linter, push changes to main branch

PR #129


Using both 'web' & 'auth:api' middlewares at the same time for Broadcast Events

Laravel Version: 5.4
PHP Version: 7.2
Database Driver & Version: mysql

I am using Laravel Event Broadcast and Pusher to utilize websockets both on my API and Web. If I try them individually, both work. What I mean is:
Broadcast::routes(['middleware' => 'web']); // this works for my Laravel website

Broadcast::routes(['middleware' => 'auth:api']); // this works for my api

However, if I want to use both at the same time like this:
Broadcast::routes(['middleware' => ['auth:api', 'web']]); // doesn't work

... it crashes for both, which I suspect that it is assuming I am trying to enable for both auth:api && web middlewares.
Is there a way to use an OR kind of statement for this (auth::api || 'web')? What if I want to use both at the same time and if it passes one middleware, it bypasses the middleware.

I have found this comment in a Laravel Echo issue, but couldn't replicate it at all.
What I tried is creating a new Middleware called Broadcast and do this accordingly:
class BroadcastMiddleware() {

  public function handle() {
    $web = Auth::guard('web')->user();
    if ($web) {
        return response()->json($web);
    }

    $api = Auth::guard('api')->user();
    if ($api) {
        return response()->json($api);
    }
    return response()->json('Unauthorized.', 500);
  }
}

And also tried setting up a route for /broadcast/auth
Route::post('/realtime/auth', function(){
    return true;
})->middleware('broadcast');

However, using above code, it's returning User model; however instead Laravel's broadcasting/auth return something like: auth:"374f7ff42b7da877aa35:c29addedec281b418331a61dc3cfc74da8b108222565fa4924a8..."
Did any of you faced with a similar issue? How can I overcome this and actually use either of them (web/auth:api)?
Also please note that I am using Laravel Passport for my api.

Here on StackOverflow, I have added my way of solving this, however I'd like to hear any improvements or any other (more elegant) ways of achieving this. Hope it helps someone

I am using Laravel Event Broadcast and redis to utilize websockets both on API  (Android App ) and Web.
The solution not worked for me ( i can't connect with web @ api) in the same time.
I can only connect Android app (api) with  Broadcast::routes(['middleware' => 'auth:api']); in BroadcastServiceProvider.
Or connect from Web withBroadcast::routes()
But I want to use both at the same time.
I tried all those solutions but not working for me, i created the middleware, the route in web.php
but not working.
I need a help please, If anyone have a solution that work
@sentiasa   thanks.

@slim1616 I can't really comment without knowing your code. What is the error you are getting?
This guy's solution seems the nice way to go, in fact I didn't try it personally - https://stackoverflow.com/a/52271897/4705339
Otherwise I am not really sure why my code on SO doesn't work for you.

@sentiasa Hello,
I follow all the steps but not working :(

middleware :
` public function handle()
{
 $web = Auth::guard('web')->user();

if ($web) {
return response()->json(\Illuminate\Support\Facades\Broadcast::auth($request));
}
return response()->json('Client can not be authenticated.', 500);
}`

in web.php  i added route :

Route::post('/guard/broadcast/auth', function(\Illuminate\Support\Facades\Request $req){

		    return true;
		})->middleware('broadcast');

in BroadcastServiceProvider :
Broadcast::routes(['middleware' => 'auth:api']);

laravel-echo-server.json :
"authEndpoint": "/guard/broadcast/auth",

result :
with web all work but with Api not worked and i have this error :
⚠ [21:49:55] - 7cMngQlPZYtVyhsdAAAF could not be authenticated to private-unique_3_0 {     "message": "",     "exception": "Symfony\\Component\\HttpKernel\\Exception\\HttpException",     "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Handler.php",     "line": 203,     "trace": [         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Handler.php",             "line": 175,             "function": "prepareException",             "class": "Illuminate\\Foundation\\Exceptions\\Handler",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/app/Exceptions/Handler.php",             "line": 49,             "function": "render",             "class": "Illuminate\\Foundation\\Exceptions\\Handler",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",             "line": 83,             "function": "render",             "class": "App\\Exceptions\\Handler",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",             "line": 55,             "function": "handleException",             "class": "Illuminate\\Routing\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/View/Middleware/ShareErrorsFromSession.php",             "line": 49,             "function": "Illuminate\\Routing\\{closure}",             "class": "Illuminate\\Routing\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",             "line": 151,             "function": "handle",             "class": "Illuminate\\View\\Middleware\\ShareErrorsFromSession",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",             "line": 53,             "function": "Illuminate\\Pipeline\\{closure}",             "class": "Illuminate\\Pipeline\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php",             "line": 63,             "function": "Illuminate\\Routing\\{closure}",             "class": "Illuminate\\Routing\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",             "line": 151,             "function": "handle",             "class": "Illuminate\\Session\\Middleware\\StartSession",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",             "line": 53,             "function": "Illuminate\\Pipeline\\{closure}",             "class": "Illuminate\\Pipeline\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/AddQueuedCookiesToResponse.php",             "line": 37,             "function": "Illuminate\\Routing\\{closure}",             "class": "Illuminate\\Routing\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",             "line": 151,             "function": "handle",             "class": "Illuminate\\Cookie\\Middleware\\AddQueuedCookiesToResponse",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",             "line": 53,             "function": "Illuminate\\Pipeline\\{closure}",             "class": "Illuminate\\Pipeline\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/EncryptCookies.php",             "line": 59,             "function": "Illuminate\\Routing\\{closure}",             "class": "Illuminate\\Routing\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",             "line": 151,             "function": "handle",             "class": "Illuminate\\Cookie\\Middleware\\EncryptCookies",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",             "line": 53,             "function": "Illuminate\\Pipeline\\{closure}",             "class": "Illuminate\\Pipeline\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",             "line": 104,             "function": "Illuminate\\Routing\\{closure}",             "class": "Illuminate\\Routing\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Router.php",             "line": 667,             "function": "then",             "class": "Illuminate\\Pipeline\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Router.php",             "line": 642,             "function": "runRouteWithinStack",             "class": "Illuminate\\Routing\\Router",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Router.php",             "line": 608,             "function": "runRoute",             "class": "Illuminate\\Routing\\Router",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Router.php",             "line": 597,             "function": "dispatchToRoute",             "class": "Illuminate\\Routing\\Router",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php",             "line": 176,             "function": "dispatch",             "class": "Illuminate\\Routing\\Router",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",             "line": 30,             "function": "Illuminate\\Foundation\\Http\\{closure}",             "class": "Illuminate\\Foundation\\Http\\Kernel",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/barryvdh/laravel-debugbar/src/Middleware/InjectDebugbar.php",             "line": 65,             "function": "Illuminate\\Routing\\{closure}",             "class": "Illuminate\\Routing\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",             "line": 151,             "function": "handle",             "class": "Barryvdh\\Debugbar\\Middleware\\InjectDebugbar",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",             "line": 53,             "function": "Illuminate\\Pipeline\\{closure}",             "class": "Illuminate\\Pipeline\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/fideloper/proxy/src/TrustProxies.php",             "line": 57,             "function": "Illuminate\\Routing\\{closure}",             "class": "Illuminate\\Routing\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",             "line": 151,             "function": "handle",             "class": "Fideloper\\Proxy\\TrustProxies",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",             "line": 53,             "function": "Illuminate\\Pipeline\\{closure}",             "class": "Illuminate\\Pipeline\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php",             "line": 31,             "function": "Illuminate\\Routing\\{closure}",             "class": "Illuminate\\Routing\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",             "line": 151,             "function": "handle",             "class": "Illuminate\\Foundation\\Http\\Middleware\\TransformsRequest",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",             "line": 53,             "function": "Illuminate\\Pipeline\\{closure}",             "class": "Illuminate\\Pipeline\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php",             "line": 31,             "function": "Illuminate\\Routing\\{closure}",             "class": "Illuminate\\Routing\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",             "line": 151,             "function": "handle",             "class": "Illuminate\\Foundation\\Http\\Middleware\\TransformsRequest",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",             "line": 53,             "function": "Illuminate\\Pipeline\\{closure}",             "class": "Illuminate\\Pipeline\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ValidatePostSize.php",             "line": 27,             "function": "Illuminate\\Routing\\{closure}",             "class": "Illuminate\\Routing\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",             "line": 151,             "function": "handle",             "class": "Illuminate\\Foundation\\Http\\Middleware\\ValidatePostSize",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",             "line": 53,             "function": "Illuminate\\Pipeline\\{closure}",             "class": "Illuminate\\Pipeline\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/CheckForMaintenanceMode.php",             "line": 62,             "function": "Illuminate\\Routing\\{closure}",             "class": "Illuminate\\Routing\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",             "line": 151,             "function": "handle",             "class": "Illuminate\\Foundation\\Http\\Middleware\\CheckForMaintenanceMode",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",             "line": 53,             "function": "Illuminate\\Pipeline\\{closure}",             "class": "Illuminate\\Pipeline\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",             "line": 104,             "function": "Illuminate\\Routing\\{closure}",             "class": "Illuminate\\Routing\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php",             "line": 151,             "function": "then",             "class": "Illuminate\\Pipeline\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php",             "line": 116,             "function": "sendRequestThroughRouter",             "class": "Illuminate\\Foundation\\Http\\Kernel",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/public/index.php",             "line": 55,             "function": "handle",             "class": "Illuminate\\Foundation\\Http\\Kernel",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/server.php",             "line": 21,             "function": "require_once"         }     ] } Client can not be authenticated, got HTTP status 419 ⚠ [21:49:56] - 7cMngQlPZYtVyhsdAAAF could not be authenticated to presence-unique_3_0 {     "message": "",     "exception": "Symfony\\Component\\HttpKernel\\Exception\\HttpException",     "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Handler.php",     "line": 203,     "trace": [         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Handler.php",             "line": 175,             "function": "prepareException",             "class": "Illuminate\\Foundation\\Exceptions\\Handler",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/app/Exceptions/Handler.php",             "line": 49,             "function": "render",             "class": "Illuminate\\Foundation\\Exceptions\\Handler",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",             "line": 83,             "function": "render",             "class": "App\\Exceptions\\Handler",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",             "line": 55,             "function": "handleException",             "class": "Illuminate\\Routing\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/View/Middleware/ShareErrorsFromSession.php",             "line": 49,             "function": "Illuminate\\Routing\\{closure}",             "class": "Illuminate\\Routing\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",             "line": 151,             "function": "handle",             "class": "Illuminate\\View\\Middleware\\ShareErrorsFromSession",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",             "line": 53,             "function": "Illuminate\\Pipeline\\{closure}",             "class": "Illuminate\\Pipeline\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php",             "line": 63,             "function": "Illuminate\\Routing\\{closure}",             "class": "Illuminate\\Routing\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",             "line": 151,             "function": "handle",             "class": "Illuminate\\Session\\Middleware\\StartSession",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",             "line": 53,             "function": "Illuminate\\Pipeline\\{closure}",             "class": "Illuminate\\Pipeline\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/AddQueuedCookiesToResponse.php",             "line": 37,             "function": "Illuminate\\Routing\\{closure}",             "class": "Illuminate\\Routing\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",             "line": 151,             "function": "handle",             "class": "Illuminate\\Cookie\\Middleware\\AddQueuedCookiesToResponse",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",             "line": 53,             "function": "Illuminate\\Pipeline\\{closure}",             "class": "Illuminate\\Pipeline\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/EncryptCookies.php",             "line": 59,             "function": "Illuminate\\Routing\\{closure}",             "class": "Illuminate\\Routing\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",             "line": 151,             "function": "handle",             "class": "Illuminate\\Cookie\\Middleware\\EncryptCookies",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",             "line": 53,             "function": "Illuminate\\Pipeline\\{closure}",             "class": "Illuminate\\Pipeline\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",             "line": 104,             "function": "Illuminate\\Routing\\{closure}",             "class": "Illuminate\\Routing\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Router.php",             "line": 667,             "function": "then",             "class": "Illuminate\\Pipeline\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Router.php",             "line": 642,             "function": "runRouteWithinStack",             "class": "Illuminate\\Routing\\Router",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Router.php",             "line": 608,             "function": "runRoute",             "class": "Illuminate\\Routing\\Router",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Router.php",             "line": 597,             "function": "dispatchToRoute",             "class": "Illuminate\\Routing\\Router",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php",             "line": 176,             "function": "dispatch",             "class": "Illuminate\\Routing\\Router",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",             "line": 30,             "function": "Illuminate\\Foundation\\Http\\{closure}",             "class": "Illuminate\\Foundation\\Http\\Kernel",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/barryvdh/laravel-debugbar/src/Middleware/InjectDebugbar.php",             "line": 65,             "function": "Illuminate\\Routing\\{closure}",             "class": "Illuminate\\Routing\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",             "line": 151,             "function": "handle",             "class": "Barryvdh\\Debugbar\\Middleware\\InjectDebugbar",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",             "line": 53,             "function": "Illuminate\\Pipeline\\{closure}",             "class": "Illuminate\\Pipeline\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/fideloper/proxy/src/TrustProxies.php",             "line": 57,             "function": "Illuminate\\Routing\\{closure}",             "class": "Illuminate\\Routing\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",             "line": 151,             "function": "handle",             "class": "Fideloper\\Proxy\\TrustProxies",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",             "line": 53,             "function": "Illuminate\\Pipeline\\{closure}",             "class": "Illuminate\\Pipeline\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php",             "line": 31,             "function": "Illuminate\\Routing\\{closure}",             "class": "Illuminate\\Routing\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",             "line": 151,             "function": "handle",             "class": "Illuminate\\Foundation\\Http\\Middleware\\TransformsRequest",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",             "line": 53,             "function": "Illuminate\\Pipeline\\{closure}",             "class": "Illuminate\\Pipeline\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php",             "line": 31,             "function": "Illuminate\\Routing\\{closure}",             "class": "Illuminate\\Routing\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",             "line": 151,             "function": "handle",             "class": "Illuminate\\Foundation\\Http\\Middleware\\TransformsRequest",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",             "line": 53,             "function": "Illuminate\\Pipeline\\{closure}",             "class": "Illuminate\\Pipeline\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ValidatePostSize.php",             "line": 27,             "function": "Illuminate\\Routing\\{closure}",             "class": "Illuminate\\Routing\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",             "line": 151,             "function": "handle",             "class": "Illuminate\\Foundation\\Http\\Middleware\\ValidatePostSize",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",             "line": 53,             "function": "Illuminate\\Pipeline\\{closure}",             "class": "Illuminate\\Pipeline\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/CheckForMaintenanceMode.php",             "line": 62,             "function": "Illuminate\\Routing\\{closure}",             "class": "Illuminate\\Routing\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",             "line": 151,             "function": "handle",             "class": "Illuminate\\Foundation\\Http\\Middleware\\CheckForMaintenanceMode",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php",             "line": 53,             "function": "Illuminate\\Pipeline\\{closure}",             "class": "Illuminate\\Pipeline\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php",             "line": 104,             "function": "Illuminate\\Routing\\{closure}",             "class": "Illuminate\\Routing\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php",             "line": 151,             "function": "then",             "class": "Illuminate\\Pipeline\\Pipeline",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php",             "line": 116,             "function": "sendRequestThroughRouter",             "class": "Illuminate\\Foundation\\Http\\Kernel",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/public/index.php",             "line": 55,             "function": "handle",             "class": "Illuminate\\Foundation\\Http\\Kernel",             "type": "->"         },         {             "file": "/Users/tech/Desktop/Qlearning/Qlearning/server.php",             "line": 21,             "function": "require_once"         }     ] } Client can not be authenticated, got HTTP status 419
thanks for your help

If you just want as me to be able to present user interfaces when loged in with api (dekstop app with some views costumized but not every) you can just have
Route::prefix('1stparty/web')->middleware('scopes:*')
     ->group(base_path('routes/web.php'));

localhost/settings will in example show users name and will check if he is loged in
this will change it to:
localhost/api/1stparty/settings and will still work

Hi! It's my solution. You can use something like this
BroadcastServiceProvider.php
Route::post('broadcasting/auth', function () {
   $url = request()->hasHeader('Authorization') ? '/api' : '/web';

   $proxy = Request::create($url . '/broadcasting/auth', 'POST', request()->toArray());
   $proxy->headers = request()->headers;

   return app()->handle($proxy)->content();
});

Broadcast::routes(['prefix' => 'web', 'middleware' => ['web']]);
Broadcast::routes(['prefix' => 'api', 'middleware' => ['auth:api']]);


Load result file into context on failure, in case it contains error msg.

When an Ansible script returns a failure, this job was failing to read the result file that the playbook wrote out and store the contents in the context.  It would be useful  to load the contents even on failure so the playbook can return an error message in the context, alerting the caller of why the playbook failed.

@RackHD/corecommitters please review.

Jenkins, ok to test

+1

:+1:


Improvement forbidden mv rewriter when select stmt's from clause not have mv

…mt's from clause not have mv (#27638)
forbidden mv rewriter when select stmt's from clause not have mv
Proposed changes
pick from #27638
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall