ERROR in ./node_modules/formik-mui/dist/Autocomplete.js

I have used formik-mui in a project. i m facing the following errors.
Compiled with problems:
ERROR in ./node_modules/formik-mui/dist/Autocomplete.js 2:0-57
Module not found: Error: Can't resolve '@mui/material/Autocomplete' in 'C:\Users\User\Documents\React\membership\node_modules\formik-mui\dist'
Did you mean 'index.js'?
BREAKING CHANGE: The request '@mui/material/Autocomplete' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
ERROR in ./node_modules/formik-mui/dist/Checkbox.js 2:0-49
Module not found: Error: Can't resolve '@mui/material/Checkbox' in 'C:\Users\User\Documents\React\membership\node_modules\formik-mui\dist'
Did you mean 'index.js'?
BREAKING CHANGE: The request '@mui/material/Checkbox' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
ERROR in ./node_modules/formik-mui/dist/CheckboxWithLabel.js 2:0-49
Module not found: Error: Can't resolve '@mui/material/Checkbox' in 'C:\Users\User\Documents\React\membership\node_modules\formik-mui\dist'
Did you mean 'index.js'?
BREAKING CHANGE: The request '@mui/material/Checkbox' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
ERROR in ./node_modules/formik-mui/dist/CheckboxWithLabel.js 3:0-62
Module not found: Error: Can't resolve '@mui/material/FormControlLabel' in 'C:\Users\User\Documents\React\membership\node_modules\formik-mui\dist'
Did you mean 'index.js'?
BREAKING CHANGE: The request '@mui/material/FormControlLabel' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
ERROR in ./node_modules/formik-mui/dist/InputBase.js 2:0-51
Module not found: Error: Can't resolve '@mui/material/InputBase' in 'C:\Users\User\Documents\React\membership\node_modules\formik-mui\dist'
Did you mean 'index.js'?
BREAKING CHANGE: The request '@mui/material/InputBase' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
ERROR in ./node_modules/formik-mui/dist/RadioGroup.js 2:0-53
Module not found: Error: Can't resolve '@mui/material/RadioGroup' in 'C:\Users\User\Documents\React\membership\node_modules\formik-mui\dist'
Did you mean 'index.js'?
BREAKING CHANGE: The request '@mui/material/RadioGroup' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
ERROR in ./node_modules/formik-mui/dist/Select.js 2:0-52
Module not found: Error: Can't resolve '@mui/material/FormControl' in 'C:\Users\User\Documents\React\membership\node_modules\formik-mui\dist'
Did you mean 'index.js'?
BREAKING CHANGE: The request '@mui/material/FormControl' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
ERROR in ./node_modules/formik-mui/dist/Select.js 3:0-58
Module not found: Error: Can't resolve '@mui/material/FormHelperText' in 'C:\Users\User\Documents\React\membership\node_modules\formik-mui\dist'
Did you mean 'index.js'?
BREAKING CHANGE: The request '@mui/material/FormHelperText' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
ERROR in ./node_modules/formik-mui/dist/Select.js 4:0-50
Module not found: Error: Can't resolve '@mui/material/InputLabel' in 'C:\Users\User\Documents\React\membership\node_modules\formik-mui\dist'
Did you mean 'index.js'?
BREAKING CHANGE: The request '@mui/material/InputLabel' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
ERROR in ./node_modules/formik-mui/dist/Select.js 5:0-45
Module not found: Error: Can't resolve '@mui/material/Select' in 'C:\Users\User\Documents\React\membership\node_modules\formik-mui\dist'
Did you mean 'index.js'?
BREAKING CHANGE: The request '@mui/material/Select' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
ERROR in ./node_modules/formik-mui/dist/SimpleFileUpload.js 3:0-52
Module not found: Error: Can't resolve '@mui/material/FormControl' in 'C:\Users\User\Documents\React\membership\node_modules\formik-mui\dist'
Did you mean 'index.js'?
BREAKING CHANGE: The request '@mui/material/FormControl' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
ERROR in ./node_modules/formik-mui/dist/SimpleFileUpload.js 4:0-50
Module not found: Error: Can't resolve '@mui/material/InputLabel' in 'C:\Users\User\Documents\React\membership\node_modules\formik-mui\dist'
Did you mean 'index.js'?
BREAKING CHANGE: The request '@mui/material/InputLabel' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
ERROR in ./node_modules/formik-mui/dist/SimpleFileUpload.js 5:0-40
Module not found: Error: Can't resolve '@mui/material/Input' in 'C:\Users\User\Documents\React\membership\node_modules\formik-mui\dist'
Did you mean 'index.js'?
BREAKING CHANGE: The request '@mui/material/Input' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
ERROR in ./node_modules/formik-mui/dist/SimpleFileUpload.js 6:0-58
Module not found: Error: Can't resolve '@mui/material/FormHelperText' in 'C:\Users\User\Documents\React\membership\node_modules\formik-mui\dist'
Did you mean 'index.js'?
BREAKING CHANGE: The request '@mui/material/FormHelperText' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
ERROR in ./node_modules/formik-mui/dist/Switch.js 2:0-45
Module not found: Error: Can't resolve '@mui/material/Switch' in 'C:\Users\User\Documents\React\membership\node_modules\formik-mui\dist'
Did you mean 'index.js'?
BREAKING CHANGE: The request '@mui/material/Switch' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
ERROR in ./node_modules/formik-mui/dist/TextField.js 2:0-51
Module not found: Error: Can't resolve '@mui/material/TextField' in 'C:\Users\User\Documents\React\membership\node_modules\formik-mui\dist'
Did you mean 'index.js'?
BREAKING CHANGE: The request '@mui/material/TextField' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
ERROR in ./node_modules/formik-mui/dist/ToggleButtonGroup.js 2:0-67
Module not found: Error: Can't resolve '@mui/material/ToggleButtonGroup' in 'C:\Users\User\Documents\React\membership\node_modules\formik-mui\dist'
Did you mean 'index.js'?
BREAKING CHANGE: The request '@mui/material/ToggleButtonGroup' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.

following is my package.json
"dependencies": {
"@emotion/react": "^11.13.3",
"@emotion/styled": "^11.13.0",
"@mui/icons-material": "^6.1.4",
"@mui/lab": "^6.0.0-beta.12",
"@mui/material": "^6.1.4",
"@testing-library/jest-dom": "^5.17.0",
"@testing-library/react": "^13.4.0",
"@testing-library/user-event": "^13.5.0",
"date-fns": "^4.1.0",
"formik": "^2.4.6",
"formik-material-ui": "^4.0.0-alpha.2",
"formik-mui": "^5.0.0-alpha.1",
"react": "^18.3.1",
"react-dom": "^18.3.1",
"react-scripts": "5.0.1",
"web-vitals": "^2.1.4",
"yup": "^1.4.0"
the same project with same packagae.json is working fine in codesandbox, but as i run it from vs code it give error. Any help will be highly appreciated.

Hi @dhawebadmin
If you create a minimal reproduction I can take a look
It's probably a build tool issue maybe related to esm
Ciaran

Thanks for your reply. I have added you to the codesandbox. However i have resolved it with a temp workaround by adding following
webpack.config.js
module -> rules -> oneOf
add this:
{
test: /.m?js/, // fix:issue: https://github.com/webpack/webpack/issues/11467
resolve: {
fullySpecified: false,
},
},
as mentioned in https://github.com/webpack/webpack/issues/16660


NEO sent to GUI has not arrived.

NEO-GUI File Version:  2.2.6442.408 downloaded via link at NEO.ORG.
Windows 7.
NEO-GUI is syncd (1416734/1416734) took 48 hours even with Chain zip!
Sent 1 X NEO plus 0.025 fee from Coinspot (status is COMPLETED) to NEO-GUI 36 hours ago. Used copy to Clipboard for receive address.
NEO-GUI version number: 2.2.6442.408 from NEO.ORG download page.
Windows 7 32 bit.
Transaction appears at Neotracker but does not appear in NEO-GUI - shows zero balance.
My receive address: AGjoFEQ1UHzNaa9fw3hjmEi8GjvY9RLxva
How long should this transaction take?
When I search the address at Neotracker under the heading First transaction it states UNSPENT.
What does UNSPENT mean?
If the address can be seen in all the Block Explorers why doesn't it appear or show in my NEO-GUI!?
That one NEO is gathering GAS at its current (wherever that may be) location.
I hope you can help.
Many thanks and greetings from Australia.
Paul

Surely I am not the only person on earth who has faced this issue and  requires assistance to remedy the problem.

Click "Rebuild index" in the menu and wait for ¬30 minutes to see if that solves it

Thank you lerider. Tried that a few days ago but did not show the missing NEO.
I have sent NEO emails direct, I have posted on the Reddit NEO Forum and your respnse is the only response so far. Again, thank you. NEO Project must have the answer but until they respond it appears hopeless.

NEO support is gorgeous! No one here..

Problem solved! I dont know how, but NEO and GAS in my NEO-gui wallet.
I`m just have done one thing:

Made a new second wallet-adress in NEO-gui.
Sent from first adress 1 NEO to second adress, by online wallet neotracker.io
And about few hours 1 NEO was in my second adress and GAS in first adress)))
At last, i have sent from secont to first by NEO-gui wallet, and NEO appear in first instantly! Now i`m try to send 10 NEO from Bitfinex, and less then 1 minute NEO in NEO-gui !!!
Thats all..

Thank you for your response lxcosmo.
The issue here is that I am trying to find out how to recover /re-claim NEO already sent to my NEO-Gui wallet which has not arrived!.
I have set up another NEO-GUI (version 2.3.6458..) and successfully sent all my NEO to the new wallet without a problem and the NEO's are now happily generating GAS.
How do I recover the NEO that has not arrived in my first wallet?

To Yippyiyo:
Sorry bro, i dont know. I think you need to wait for synchronize NEO-gui..

Hi @Yippyiyo I have read your issue. If you can find you asset in your address by checking explorer, it's certain that the asset does exits in that address. The only problem is that neo-gui doesn't show it properly. You need to re-index your wallet and wait for 20 minutes or so and check again. I have no idea why you sync so slow, you need to check your web situation. If you use accelerate package, normally it takes 10 minutes or so to complete all sync process. I hope it can help you well.

Many thanks PeterLinX. I have "rebuilt index" probably a dozen times over the past 10 days or so. Still shows ZERO Neo and Zero Gas. When I use REBUILT INDEX there is no activity to suggest it is doing that. Should there be some activity noticeable?
Regarding the length of time to sync the zip file CHAIN.ACC was about 840 MB and the current size is 1.8 GB.
Again thank you. Any other ideas?

I really do not understand why this issue has not been resolved.
Is it really such a difficult challenge for the NEO developers to figure out how to move a coin, living a happy life earning GAS in the Blockchain, to the intended address? Perhaps the NEO developers should figure out why this happened in the first place!!
Come on NEO!! Extract the digit and resolve this issue!
This has dragged on far too long!

Send me a message on Slack and I will help you resolve it, easier
communication.
Username: @lerider
2017-10-12 15:29 GMT+08:00 Yippyiyo<EMAIL_ADDRESS>
I really do not understand why this issue has not been resolved.
Is it really such a difficult challenge for the NEO developers to figure
out how to move a coin, living a happy life earning GAS in the Blockchain,
to the intended address? Perhaps the NEO developers should figure out why
this happened in the first place!!
Come on NEO!! Extract the digit and resolve this issue!
This has dragged on far too long!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/neo-project/neo-gui/issues/74#issuecomment-336044765,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFp9GC0u9ANZ3lPhzP4MSx_1R0MCjWl8ks5srb_GgaJpZM4Pph37
.

Thank you very much Lerider.
I will contact you.

hey guys i have the same issue but down the bottom where it says Height and Connections mine just says 0/0 how come everyone elses all has numbers i found my Neo on Neo tracker but wont turn up in my wallet

Lerider,
I am not a Slack user and do not belong to a Slack wok space. Apparently I need to be invited to be able to respond.
Alternatively I can provide you with my email address or we can do it here. - may help others with similar issues?
Which ever you are happy with suits me.
Thank you.

@Donksy28 Hi, maybe you need to wait for a second and then the wallet will sync as everybody else.

@Yippyiyo is your problem resolved? Maybe you can use the latest version of neo-gui and try it again. Your problem is not complicated and you can solve it as what I told you.

I left it open for 24 hours + and nothing i have not looked at it for
awhile it was pissing me off
On Thu, 19 Oct 2017 at 4:16 pm, Peter Lin<EMAIL_ADDRESS>wrote:

@Yippyiyo https://github.com/yippyiyo is your problem resolved? Maybe
you can use the latest version of neo-gui and try it again. Your problem is
not complicated and you can solve it as what I told you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/neo-project/neo-gui/issues/74#issuecomment-337810139,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AfQEUlHCerigiOOrH1wFsnvV_BEBiTRsks5stukzgaJpZM4Pph37
.

@Donksy28 If you are using latest version of neo-gui, I think the only reason which causes the problem is your network problem. Maybe you need vpn to solve it. For now, neo blockchain and neo-gui are working well.

Thank you for the many replies but the problem persists
I copied the .db3 file from the original NEO-GUI and placed it into a new wallet in the latest NEO-GUI I set up, expecting that the missing neo would be imported. NO LUCK there!
AGjoFEQ1UHzNaa9fw3hjmEi8GjvY9RLxva   It is still cruising around in cyberspace!
I have emailed NEO.ORG but they seem not to care? Offers to assist here are never followed up on when I reply to those offers,
WTF is going on here!?

...btw I copied my .DB3 file from the original NEO-GUI the NEO was sent to, into a new wallet in the latest NEO-GUI, but everything (Neo and Gas) has remained as ZERO!
W T F IS WROMG WITH NEO THAT THIS REMAINS UNRESOLVED SINCE THIS THREAD WAS OPENED?????????????????????

My lost NEO has arrived.
What I did:
Imported the address "sent to" .db3 file  into the new NEO-GUI wallet.
Took a while but at last I have the missing NEO.

I'm having a similar problem with sending GAS from my NEO wallet to an external address. In the neotracker.io it states that the amount is UNSPENT. How do I fix this? it's been stuck for weeks now


expected<void, Error> is unusable due to final

Required information
Since the final keyword was added to all expected classes the specialization expected<void, Error> is unusable since it inherit from them.
No one has noticed this until now so we have 2 solutions.

Remove expected<void, Error> specialization
Remove the final keyword.

@elfenpiff I noticed it end of last week. There is a third option, having an detail::expected_impl<E> and let expected<E> and expected<void, E> derive from it


Getting a nested array when multiple rows are linked to a single entry

Why
I want to use an Entity with a 1-to-many data structure relationship, but it seems that it is currently not possible.
Suggestion
By using php.net:PDO::FETCH_NAMED, it seems that if there are multiple values, they will be stored in an array.
This might also be helpful: phpdelusions.net::FETCH_NAMED

Good! Could you create a test for that?

Got it. I try to write a test.


[FLINK-31749][hotfix][doc] Update Hadoop formats datastream doc

@MartijnVisser As dicsussed, I removed the output format that is not supported with DataStream and tested the code for input format, it was not updated so I updated it.
PTAL.

@MartijnVisser I recently learned what the criteria for hotfix changes are. This PR definitely complies. As we already discussed the removal of hadoop outputFormat for DataStream in the ticket, I can self-merge.

@MartijnVisser I recently learned what the criteria for hotfix changes are. This PR definitely complies. As we already discussed the removal of hadoop outputFormat for DataStream in the ticket, I can self-merge.


allow services without packages

I noticed that at least the Postman service reflector feature will not work without package name when using this library.
I have no idea how this is supposed to work, but I was running through this tutorial: https://blog.logrocket.com/communicating-between-node-js-microservices-with-grpc/ and noticed the issue.
The reflection server works properly, at least for the examples, when there is no package after this is added.

⚠ Repository Archived
Thank you for your contribution. This repository has been archived and is no longer maintained.
As a result:
This issue is now being closed.
Please note that no further updates or support will be provided.
We encourage you to fork the repository if you’d like to continue development independently. Thank you for your understanding! 🙏


frostdb: add leveled compaction

This PR implements simple leveled compaction of parts into level 1 parts as described in #223, which are guaranteed to never be overlapping. This will hopefully improve our memory usage during compactions and avoid the spikes we've seen in our clusters. Please refer to the individual commits for details. I've tried to split it up into 1) The addition of leveled compaction, 2) Handling out-of-order inserts which should only happen very rarely but it is an edge case we need to handle.

Converting to draft until I investigate why this has made some things so much worse.

By "much worse" I was referring to benchmark performance. However I think this compaction strategy already makes things better. Based on my investigation, we were never actually running a compaction on main during these benchmarks. This is because we would never unset pruned on a granule in cases where only parts with uncompleted txns were found (this is the case of compacting during WAL replays). Since pruned was already set, the granule would never be compacted.
It turns out the inserts are actually very well batched. Here is a comparison of main with and without our current compaction strategy (simply adding a t.abort(granule) in the case of len(bufs) == 0 in compactGranule):
name           old time/op    new time/op     delta
Query/Types-8    3.77ms ± 1%   641.41ms ±93%  +16929.55%  (p=0.000 n=10+10)
Query/Merge-8    12.4ms ± 1%     27.9ms ± 2%    +124.03%  (p=0.000 n=9+9)
Query/Range-8    4.04ms ± 0%    14.10ms ± 1%    +249.33%  (p=0.000 n=8+10)

name           old alloc/op   new alloc/op    delta
Query/Types-8    5.69MB ± 0%  5353.70MB ±91%  +93949.13%  (p=0.000 n=10+10)
Query/Merge-8    74.9MB ± 0%    162.8MB ± 0%    +117.36%  (p=0.000 n=9+10)
Query/Range-8    16.3MB ± 0%     58.5MB ± 0%    +258.73%  (p=0.000 n=10+10)

name           old allocs/op  new allocs/op   delta
Query/Types-8     93.4k ± 0%   2495.5k ±359%        ~     (p=0.720 n=10+9)
Query/Merge-8      301k ± 0%       204k ± 0%     -32.32%  (p=0.000 n=9+10)
Query/Range-8     57.7k ± 0%       7.8k ± 0%     -86.49%  (p=0.000 n=10+10)

Now compare the leveled compaction strategy with the our current compaction strategy:
name           old time/op    new time/op    delta
Query/Types-8     641ms ±93%      42ms ± 6%  -93.46%  (p=0.000 n=10+10)
Query/Merge-8    27.9ms ± 2%    22.3ms ± 1%  -19.81%  (p=0.000 n=9+10)
Query/Range-8    14.1ms ± 1%    10.3ms ± 0%  -27.25%  (p=0.000 n=10+10)

name           old alloc/op   new alloc/op   delta
Query/Types-8    5.35GB ±91%    0.39GB ± 0%  -92.63%  (p=0.000 n=10+10)
Query/Merge-8     163MB ± 0%     119MB ± 0%  -26.90%  (p=0.000 n=10+10)
Query/Range-8    58.5MB ± 0%    36.7MB ± 0%  -37.27%  (p=0.000 n=10+10)

name           old allocs/op  new allocs/op  delta
Query/Types-8    2.50M ±359%     0.02M ± 0%  -99.33%  (p=0.004 n=9+9)
Query/Merge-8      204k ± 0%      203k ± 0%   -0.13%  (p=0.000 n=10+10)
Query/Range-8     7.80k ± 0%     7.54k ± 0%   -3.32%  (p=0.000 n=10+10)

The leveled compaction strategy still performs worse than no compactions but is definitely better than the current compaction strategy. For reference here is no compactions vs leveled compaction:
name           old time/op    new time/op    delta
Query/Types-8    3.77ms ± 1%   41.94ms ± 6%  +1013.38%  (p=0.000 n=10+10)
Query/Merge-8    12.4ms ± 1%    22.3ms ± 1%    +79.65%  (p=0.000 n=9+10)
Query/Range-8    4.04ms ± 0%   10.26ms ± 0%   +154.13%  (p=0.000 n=8+10)

name           old alloc/op   new alloc/op   delta
Query/Types-8    5.69MB ± 0%  394.45MB ± 0%  +6829.39%  (p=0.000 n=10+10)
Query/Merge-8    74.9MB ± 0%   119.0MB ± 0%    +58.89%  (p=0.000 n=9+10)
Query/Range-8    16.3MB ± 0%    36.7MB ± 0%   +125.03%  (p=0.000 n=10+10)

name           old allocs/op  new allocs/op  delta
Query/Types-8     93.4k ± 0%     16.7k ± 0%    -82.18%  (p=0.000 n=10+9)
Query/Merge-8      301k ± 0%      203k ± 0%    -32.41%  (p=0.000 n=9+10)
Query/Range-8     57.7k ± 0%      7.5k ± 0%    -86.94%  (p=0.000 n=10+10)

My explanation for this is that QueryTypes worsened a lot because distinct performance improvements cannot be taken advantage of after reshaping the data during compaction (still to be confirmed). Merge and Range I am not quite sure of, but it's probably due to a similar explanation.
I think that I will add some improvements to this PR that I thought about when replaying WALs (writing l1s iteratively from a single merged row group of all l0s) and advocate to merge this given its improvement over our current compaction strategy.
It's clear that we have to do more work when it comes to "shaping" parts so that the scan level can reach the non-compacted latencies, but that is left for future work. The important part is that this compaction is an improvement over our current compaction strategy.

This is now ready for a look! Add a commit with the new "cursor" strategy which simplifies things a bit. The performance hit from no compactions has also been mitigated:
name           old time/op    new time/op    delta
Query/Types-8    3.77ms ± 1%   11.07ms ± 3%   +193.88%  (p=0.000 n=10+10)
Query/Merge-8    12.4ms ± 1%    20.4ms ± 0%    +63.69%  (p=0.000 n=9+7)
Query/Range-8    4.04ms ± 0%    8.32ms ± 1%   +106.15%  (p=0.000 n=8+9)

name           old alloc/op   new alloc/op   delta
Query/Types-8    5.69MB ± 0%   92.23MB ± 0%  +1520.17%  (p=0.000 n=10+8)
Query/Merge-8    74.9MB ± 0%    93.8MB ± 1%    +25.26%  (p=0.000 n=9+10)
Query/Range-8    16.3MB ± 0%    27.0MB ± 0%    +65.72%  (p=0.000 n=10+10)

name           old allocs/op  new allocs/op  delta
Query/Types-8     93.4k ± 0%     24.2k ± 0%    -74.13%  (p=0.000 n=10+9)
Query/Merge-8      301k ± 0%      204k ± 0%    -32.12%  (p=0.000 n=9+10)
Query/Range-8     57.7k ± 0%      8.4k ± 0%    -85.44%  (p=0.000 n=10+10)

Before merging, I'd like to add some logging/metrics.

I made some modifications (level 1 target size and size to split granule) and ran these new compaction changes on a local parca instance ingesting profiles from demo and it stabilized performance significantly. In the following graphs, I ran the old compactor until a block rotation and then ran the new compactor. The new compactor starts at 12:05 on the graph, so basically where all curves drop back down midway through:
Here is the p50 of Query (Merge/Single):

p50 of QueryRange:

p90 latencies are also relatively more stable:

The downside is that the active block is rotated earlier than with the old compactor since the old compactor recompacted everything.

In general, we also distribute the parts evenly to avoid excessive compactions:

This probably means that we could probably be doing more compactions while not affecting query latency/stability. I think I'm fine merging this as a first version and then iterating with the parameters to find what works for us.

I think I'd appreciate a last review/sanity check for the metrics etc... and can merge on approval.


Adds unadvirtual.edu.co domain file

@billbravo Please provide us with a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.

The university domain is www.unad.edu.co and the students email domain is unadvirtual.edu.co. If you go to the university web portal www.unad.edu.co and click on the top-right option "Correo(Email)" > "Estudiantes(Students)" it will redirect you http://outlook.com/unadvirtual.edu.co. That's the students email provider.

@billbravo Thank you for the clarification. Pull request merged.


sound support

1. Which version of kreait/firebase-php are you using?
4.9.0
2. Which version of PHP are you using?
7.2
3. What's the issue?
Does the package support push notification with sound, and so what do I need to set them up.

You can add any property that is supported by the FCM HTTP specification, including sound, so: yes :)
You can find the specification here: https://firebase.google.com/docs/cloud-messaging/http-server-ref


[Frontend QOL] Pricing Calculator

Is your feature request related to a problem? Please describe.
Not related to a problem.  The equations are basic, shouldn't be a huge undertaking. However it would be convenient to have basic presets and have sections filled automatically based on session data.
Describe the solution you'd like
A few fields for putting in values for these fields, let me know if I am missing anything crucial.
Number of Players
Number of Hours
Cost per Hour
Number of Courts
Number of Shuttles Used
Cost per Shuttle
Total Cost per Player = ((Number of Hours x Cost per Hour x Number of Courts) + (Number of Shuttles Used x Cost per Shuttle)) / Number of Players
This is a rough idea of what the prototype should look like.

@Kirixi this is for u bb


feat: Add Wallet Assets

It would be useful to have the assets associated with the wallets, for example, their logo, as is done in chain-registry

This is fatastic work. My suggestion would be to remove logo_URIs, and only keep images

This is fantastic work. My suggestion would be to remove logo_URIs, and only keep images

Yes it is a very good idea, we can compact it into the images field, how about if we also add an additional information to indicate the type of image though? For example "logo", "banner", "logotype" and "logomark", what do you think?

Yes it is a very good idea, we can compact it into the images field, how about if we also add an additional information to indicate the type of image though? For example "logo", "banner", "logotype" and "logomark", what do you think?

Yes, I like this. But there are so many different ways a logo can be presented, so I'd like to define what each of these mean.
E.g., I have a CMS that allows for 6 different logo images for each project: 3 color varieties (light mode, dark mode, and all white) of logo_asset (which, I think is same as what you call logomark), and 3 color varieties of logotype (which is the logo asset + text).
Also, whenever there are multiple variants of the logotype, I opt for the one that has the text to the right of the logo asset, and omit the one with text below the logo asset. If allowing for both varieties of a single logo, we should allow for a way to specify which is which.

Yes it is a very good idea, we can compact it into the images field, how about if we also add an additional information to indicate the type of image though? For example "logo", "banner", "logotype" and "logomark", what do you think?

Yes, I like this. But there are so many different ways a logo can be presented, so I'd like to define what each of these mean.
E.g., I have a CMS that allows for 6 different logo images for each project: 3 color varieties (light mode, dark mode, and all white) of logo_asset (which, I think is same as what you call logomark), and 3 color varieties of logotype (which is the logo asset + text). Also, whenever there are multiple variants of the logotype, I opt for the one that has the text to the right of the logo asset, and omit the one with text below the logo asset. If allowing for both varieties of a single logo, we should allow for a way to specify which is which.

Yes, I agree, about the image's categories:

Logo, I mean logo "icon" + text
Logo type, I mean only text
Logo mark, I mean only logo "icon"

If we wanna handle text direction, we can add a property "direction", that can be helpful for accessibility if someone need to use it for rtl

Yes, I agree, about the image's categories:

Logo, I mean logo "icon" + text
Logo type, I mean only text
Logo mark, I mean only logo "icon"

If we wanna handle text direction, we can add a property "direction", that can be helpful for accessibility if someone need to use it for rtl

I see. My logotype definition was icon + text, so I hope I don't cause confusion there. I generally like your definitions.
On direction, all I meant was where the text is positioned relative to the icon(--not how it's read; ltr vs rtl).

could have something like this within the schema within an image object? I think we'll be able to make use of the same definitions for the Chain Registry.
"logo_layout": {
  "type": "string",
  "enum": [
    "logo",
    "logomark",
    "logotype"
  ],
  "description": "logomark == icon only; logotype == text only; logo == icon + text."
}

"logo_layout": {
"type": "string",
"enum": [
"logo",
"logomark",
"logotype"
],
"description": "logomark == icon only; logotype == text only; logo == icon + text."
}

Yes, we add the following one inside the 'images' array:
{
  "layout": {
    "type": "string",
    "enum": [
      "logo",
      "logomark",
      "logotype"
    ],
    "description": "logomark == icon only; logotype == text only; logo == icon + text."
  },
  "text_position": {
    "type": "string",
    "enum": [
      "top",
      "bottom",
      "left",
      "right"
    ],
    "description": "Indicates in which position the text is placed, in case the layout is 'icon' type, it's required only in this case."
  },
}

I only changed the field name from "logo_layout" to "layout", just to be generic, right now we're using it for logo but maybe in the future we wanna use it for other use cases.
Just to avoid confusion (maybe a 'direction' field can be tricky), we can create a "text_position" field, that can be use for "logo" layout and it's required only in this use case.

Yes, we add the following one inside the 'images' array:
{
  "layout": {
    "type": "string",
    "enum": [
      "logo",
      "logomark",
      "logotype"
    ],
    "description": "logomark == icon only; logotype == text only; logo == icon + text."
  },
  "text_position": {
    "type": "string",
    "enum": [
      "top",
      "bottom",
      "left",
      "right"
    ],
    "description": "Indicates in which position the text is placed, in case the layout is 'icon' type, it's required only in this case."
  },
}

I only changed the field name from "logo_layout" to "layout", just to be generic, right now we're using it for logo but maybe in the future we wanna use it for other use cases.
Just to avoid confusion (maybe a 'direction' field can be tricky), we can create a "text_position" field, that can be use for "logo" layout and it's required only in this use case.

I think the text_position is a bit overkill, but I also really like. I'm happy with what you've suggested and would like to implement the same into the Chain Registry to help implement this as a standard.

Yes, we add the following one inside the 'images' array:
{
  "layout": {
    "type": "string",
    "enum": [
      "logo",
      "logomark",
      "logotype"
    ],
    "description": "logomark == icon only; logotype == text only; logo == icon + text."
  },
  "text_position": {
    "type": "string",
    "enum": [
      "top",
      "bottom",
      "left",
      "right"
    ],
    "description": "Indicates in which position the text is placed, in case the layout is 'icon' type, it's required only in this case."
  },
}

I only changed the field name from "logo_layout" to "layout", just to be generic, right now we're using it for logo but maybe in the future we wanna use it for other use cases.
Just to avoid confusion (maybe a 'direction' field can be tricky), we can create a "text_position" field, that can be use for "logo" layout and it's required only in this use case.

I think the text_position is a bit overkill, but I also really like. I'm happy with what you've suggested and would like to implement the same into the Chain Registry to help implement this as a standard.

Thank you! I'll update the schema

@JeremyParish69 Done


Add riak_core_security:find_unique_user_by_metadata

This functions identically to find_one_user_by_metadata but returns
{error, not_unique} if there are multiple users with matching
metadata.

+1

+1 with a note to self to revisit our find_one caller to see if we can replace it with this.


Inquiry on evaluation

Thanks for your great work!
Recently When I prepared dl3dv according to the project workflow, I found that I couldn't perform evaluation (it would stop at Testing: | | 0/? [00:00<?, ?it/s]). However, when I used dl3dv_tiny, it worked pretty well.
Also when I evaluate using the re10k_subset provided by pixelsplat (https://drive.google.com/drive/folders/1joiezNCyQK2BvWMnfwHJpm2V77c7iYGe), it also stops at Testing: | | 0/? [00:00<?, ?it/s]. I checked and found that the dataset format is correct. I would like to humbly ask where the error might have occurred.
I would appreciate a lot if you could provide a detailed process for converting dl3dv, or how to check whether the converted torch chunk is valid? Looking forward to your reply, it is very very important to me.

Hey @Dubhe-forever, thanks for your appreciation.
You might refer to my answers in #4 for potential solutions. I will also find time to double-check the processed codes shortly. Cheers.

Hey @Dubhe-forever, thanks for your appreciation.
You might refer to my answers in #4 for potential solutions. I will also find time to double-check the processed codes shortly. Cheers.

@donydchen Thanks a lot for your reply! It works！ : )


[oracle-cloud] Update common files for branch master

Update common files

Closing this in favor of #239


minor tweaks to DES vocabularies for refresh HTTP/HTTPS

Tweak of 5 DES vocabularies to see if the HTTP/HTTPS issue can be fixed be reloading.
Also changed the order of a dqv:Dimension ; a skos:Concept ; to a skos:Concept ; a dqv:Dimension ; in data quality vocabularies.
@KellyVance and @johnmckellar - I don't believe any of these vocabularies are used by GSQ and hopefully they can be updated for DES usage.
cc @UbuntuScott @nicholascar

Just have to tweak Observed Properties to include a few additional values for further testing.

@johnmckellar and @KellyVance - If none of the vocabs are used by GSQ are we good to approve and merge - with a push to VocPrez?

I'll leave the final OK to Vance.

From: Dan Brough @.>
Sent: Wednesday, 11 May 2022 9:19 AM
To: geological-survey-of-queensland/vocabularies @.>
Cc: John McKellar @.>; Mention @.>
Subject: Re: [geological-survey-of-queensland/vocabularies] minor tweaks to DES vocabularies for refresh HTTP/HTTPS (PR #436)
@johnmckellarhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_johnmckellar&d=DwMCaQ&c=tpTxelpKGw9ZbZ5Dlo0lybSxHDHIiYjksG4icXfalgk&r=yrEF0yvgWdSigQanb8WqdzwPELVOZ7NVcIEPeATM1gUhq9tWQm4O86Kb5JWNt4MD&m=GwGA1qK_u6VAogfX_v_POaEaVSd2RqopLYsjRdKWu4M&s=NvwE4Zb4nJVnNH33BcATdiFjJEwmNR-CKj_LSIptl0s&e= and @KellyVancehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_KellyVance&d=DwMCaQ&c=tpTxelpKGw9ZbZ5Dlo0lybSxHDHIiYjksG4icXfalgk&r=yrEF0yvgWdSigQanb8WqdzwPELVOZ7NVcIEPeATM1gUhq9tWQm4O86Kb5JWNt4MD&m=GwGA1qK_u6VAogfX_v_POaEaVSd2RqopLYsjRdKWu4M&s=V_oY9WQHlKDoLQSN5CZxPX56iBsc0yedGzPUmVe_jh0&e= - If none of the vocabs are used by GSQ are we good to approve and merge - with a push to VocPrez?
—
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_geological-2Dsurvey-2Dof-2Dqueensland_vocabularies_pull_436-23issuecomment-2D1123003779&d=DwMCaQ&c=tpTxelpKGw9ZbZ5Dlo0lybSxHDHIiYjksG4icXfalgk&r=yrEF0yvgWdSigQanb8WqdzwPELVOZ7NVcIEPeATM1gUhq9tWQm4O86Kb5JWNt4MD&m=GwGA1qK_u6VAogfX_v_POaEaVSd2RqopLYsjRdKWu4M&s=R0lkQ2gajI7DfQvEczDuxCUgzg7zMshsc5go3ZC92Og&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AMXRW2WOKFUDABNS2FN2UA3VJLVHLANCNFSM5VNK4WAA&d=DwMCaQ&c=tpTxelpKGw9ZbZ5Dlo0lybSxHDHIiYjksG4icXfalgk&r=yrEF0yvgWdSigQanb8WqdzwPELVOZ7NVcIEPeATM1gUhq9tWQm4O86Kb5JWNt4MD&m=GwGA1qK_u6VAogfX_v_POaEaVSd2RqopLYsjRdKWu4M&s=d5uma5JgVylx97MkPG3pCEBo55iJKAc_ZR9rMmvlC3E&e=.
You are receiving this because you were mentioned.Message ID: @.***>

The information in this email together with any attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. There is no waiver of any confidentiality/privilege by your inadvertent receipt of this material.
Any form of review, disclosure, modification, distribution and/or publication of this email message is prohibited, unless as a necessary part of Departmental business.
If you have received this message in error, you are asked to inform the sender as quickly as possible and delete this message and any copies of this message from your computer and/or your computer system network.


Requests to docker daemon fail after curl update

It seems that curl 7.5x changed how URLs were handled for unix sockets, which prevents the kill request used in init.sh from succeeding (the docker daemon responds instead with a 404).
There's some discussion around the change at https://github.com/moby/moby/issues/17960#issuecomment-247568819, but briefly in older versions of curl http:/containers/xyz resulted in a request for /containers/xyz, and in newer versions it results in a Host: containers header and a request for /xyz

I was just bit by this as well on docker 18.09 / API version 1.39.
the cURL path has changed, apparently.


Run failed: Node Code Execution run failed: Failed to parse result

Self Checks

[X] This is only for bug report, if you would like to ask a question, please head to Discussions.
[X] I have searched for existing issues search for existing issues, including closed ones.
[X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
[X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
[X] Please do not modify this template :) and fill in all the required fields.

Dify version
0.6.15
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
I started dify version 0.6.15 with docker. I set the environment variable for the code node.  Run the following command to check the environment variables of the sanbox container:
[root@cturf165 docker]# docker exec -it docker-sandbox-1 env
PATH=/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOSTNAME=831f3c73466a
TERM=xterm
SANDBOX_PORT=8194
CODE_MAX_NUMBER_ARRAY_LENGTH=10000000
TEMPLATE_TRANSFORM_MAX_LENGTH=80000000
CODE_MAX_STRING_LENGTH=80000000
HTTPS_PROXY=http://ssrf_proxy:3128
CODE_MAX_NUMBER=922337203685477580700
CODE_MAX_STRING_ARRAY_LENGTH=300000
ENABLE_NETWORK=true
CODE_MAX_OBJECT_ARRAY_LENGTH=300000
CODE_MIN_NUMBER=-922337203685477580800
WORKER_TIMEOUT=15
API_KEY=dify-sandbox
GIN_MODE=release
HTTP_PROXY=http://ssrf_proxy:3128
LANG=C.UTF-8
GPG_KEY=A035C8C19219BA821ECEA86B64E628F8D684696D
PYTHON_VERSION=3.10.14
PYTHON_PIP_VERSION=23.0.1
PYTHON_SETUPTOOLS_VERSION=65.5.1
PYTHON_GET_PIP_URL=https://github.com/pypa/get-pip/raw/e03e1607ad60522cf34a92e834138eb89f57667c/public/get-pip.py
PYTHON_GET_PIP_SHA256=ee09098395e42eb1f82ef4acb231a767a6ae85504a9cf9983223df0a7cbd35d7
HOME=/root

I built an app using chatflow and the content of its DSL file named "test.yml" is as follows:
app:
  description: ''
  icon: "\U0001F916"
  icon_background: '#FFEAD5'
  mode: advanced-chat
  name: test
kind: app
version: 0.1.0
workflow:
  environment_variables: []
  features:
    file_upload:
      image:
        enabled: false
        number_limits: 3
        transfer_methods:
        - local_file
        - remote_url
    opening_statement: ''
    retriever_resource:
      enabled: true
    sensitive_word_avoidance:
      enabled: false
    speech_to_text:
      enabled: false
    suggested_questions: []
    suggested_questions_after_answer:
      enabled: false
    text_to_speech:
      enabled: false
      language: ''
      voice: ''
  graph:
    edges:
    - data:
        isInIteration: false
        sourceType: code
        targetType: iteration
      id:<PHONE_NUMBER>067-source-1722488343394-target
      source: '1722480460067'
      sourceHandle: source
      target: '1722488343394'
      targetHandle: target
      type: custom
      zIndex: 0
    - data:
        isInIteration: true
        iteration_id: '1722488343394'
        sourceType: code
        targetType: answer
      id:<PHONE_NUMBER>130-source-1722488502069-target
      source: '1722488455130'
      sourceHandle: source
      target: '1722488502069'
      targetHandle: target
      type: custom
      zIndex: 1002
    - data:
        isInIteration: false
        sourceType: start
        targetType: code
      id:<PHONE_NUMBER>479-source-1722480460067-target
      source: '1722480438479'
      sourceHandle: source
      target: '1722480460067'
      targetHandle: target
      type: custom
      zIndex: 0
    nodes:
    - data:
        desc: ''
        selected: false
        title: "\u5F00\u59CB"
        type: start
        variables: []
      height: 54
      id: '1722480438479'
      position:
        x: 282
        y: 282
      positionAbsolute:
        x: 282
        y: 282
      selected: false
      sourcePosition: right
      targetPosition: left
      type: custom
      width: 244
    - data:
        code: "def main() -> dict:\n    original_strings_with_empty = [\"apple\",\
          \ \"\", \"cherry\", \"date\", \"\", \"fig\", \"grape\", \"honeydew\", \"\
          kiwi\", \"\", \"mango\", \"nectarine\", \"orange\", \"papaya\", \"quince\"\
          , \"raspberry\", \"strawberry\", \"tangerine\", \"ugli fruit\", \"vanilla\
          \ bean\", \"watermelon\", \"xigua\", \"yellow passionfruit\", \"zucchini\"\
          ] * 5\n\n    # \u6269\u5C55\u6BCF\u4E2A\u5B57\u7B26\u4E32\u52303000\u4E2A\
          \u5B57\u7B26\uFF0C\u901A\u8FC7\u91CD\u590D\u539F\u59CB\u5B57\u7B26\u4E32\
          \u7684\u5B57\u7B26\n    extended_strings = []\n\n    for s in original_strings_with_empty:\n\
          \        if s:  # \u68C0\u67E5\u5B57\u7B26\u4E32\u662F\u5426\u975E\u7A7A\
          \n            # \u8BA1\u7B97\u9700\u8981\u91CD\u590D\u7684\u6B21\u6570\uFF0C\
          \u4F7F\u7528ceil\u51FD\u6570\u786E\u4FDD\u957F\u5EA6\u81F3\u5C11\u4E3A3000\n\
          \            repeat_times = 600\n            # \u91CD\u590D\u5B57\u7B26\u4E32\
          \u5E76\u5207\u7247\u4EE5\u786E\u4FDD\u957F\u5EA6\u6B63\u597D\u4E3A3000\n\
          \            extended_s = (s * repeat_times)[:2000]\n            extended_strings.append(extended_s)\n\
          \        else:\n            # \u5982\u679C\u5B57\u7B26\u4E32\u4E3A\u7A7A\
          \uFF0C\u8FD9\u91CC\u5047\u8BBE\u4E0D\u5904\u7406\u7A7A\u5B57\u7B26\u4E32\
          \uFF0C\u76F4\u63A5\u4FDD\u6301\u4E3A\u7A7A\n            extended_strings.append(s)\
          \ \n    \n    return {\n        \"result\": extended_strings,\n    }"
        code_language: python3
        desc: ''
        outputs:
          result:
            children: null
            type: array[string]
        selected: false
        title: "\u4EE3\u7801\u6267\u884C"
        type: code
        variables: []
      height: 54
      id: '1722480460067'
      position:
        x: 680
        y: 282
      positionAbsolute:
        x: 680
        y: 282
      selected: true
      sourcePosition: right
      targetPosition: left
      type: custom
      width: 244
    - data:
        desc: ''
        height: 209
        iterator_selector:
        - '1722480460067'
        - result
        output_selector:
        - '1722488455130'
        - result
        output_type: array[string]
        selected: false
        startNodeType: code
        start_node_id: '1722488455130'
        title: "\u8FED\u4EE3"
        type: iteration
        width: 681
      height: 209
      id: '1722488343394'
      position:
        x: 962
        y: 282
      positionAbsolute:
        x: 962
        y: 282
      selected: false
      sourcePosition: right
      targetPosition: left
      type: custom
      width: 681
      zIndex: 1
    - data:
        code: "\ndef main(arg1: str) -> dict:\n    return {\n        \"result\": arg1,\n\
          \    }\n"
        code_language: python3
        desc: ''
        isInIteration: true
        isIterationStart: true
        iteration_id: '1722488343394'
        outputs:
          result:
            children: null
            type: string
        selected: false
        title: "\u4EE3\u7801\u6267\u884C 2"
        type: code
        variables:
        - value_selector:
          - '1722488343394'
          - item
          variable: arg1
      extent: parent
      height: 54
      id: '1722488455130'
      parentId: '1722488343394'
      position:
        x: 117
        y: 85
      positionAbsolute:
        x: 1079
        y: 367
      selected: false
      sourcePosition: right
      targetPosition: left
      type: custom
      width: 244
      zIndex: 1001
    - data:
        answer: '

          {{#1722488455130.result#}}'
        desc: ''
        isInIteration: true
        iteration_id: '1722488343394'
        selected: false
        title: "\u76F4\u63A5\u56DE\u590D"
        type: answer
        variables: []
      extent: parent
      height: 107
      id: '1722488502069'
      parentId: '1722488343394'
      position:
        x: 421
        y: 85
      positionAbsolute:
        x: 1383
        y: 367
      selected: false
      sourcePosition: right
      targetPosition: left
      type: custom
      width: 244
      zIndex: 1002
    viewport:
      x: -650.5
      y: 62
      zoom: 1

The code of Code Execution Node 1 is as follows:
def main() -> dict:
    original_strings_with_empty = ["apple", "", "cherry", "date", "", "fig", "grape", "honeydew", "kiwi", "", "mango", "nectarine", "orange", "papaya", "quince", "raspberry", "strawberry", "tangerine", "ugli fruit", "vanilla bean", "watermelon", "xigua", "yellow passionfruit", "zucchini"] * 5

    extended_strings = []

    for s in original_strings_with_empty:
        if s:
            repeat_times = 600
            extended_s = (s * repeat_times)[:3000]
            extended_strings.append(extended_s)
        else:
            extended_strings.append(s)

    return {
        "result": extended_strings,
    }

And then I run the app. The app crashes. The error message is as follows:
Run failed: Node Code Execution run failed: Failed to parse result
Then I change the code of Code Execution Node 1 to set the character length to 2000.
def main() -> dict:
    original_strings_with_empty = ["apple", "", "cherry", "date", "", "fig", "grape", "honeydew", "kiwi", "", "mango", "nectarine", "orange", "papaya", "quince", "raspberry", "strawberry", "tangerine", "ugli fruit", "vanilla bean", "watermelon", "xigua", "yellow passionfruit", "zucchini"] * 5

    extended_strings = []

    for s in original_strings_with_empty:
        if s:
            repeat_times = 600

            extended_s = (s * repeat_times)[:2000]
            extended_strings.append(extended_s)
        else:

            extended_strings.append(s)

    return {
        "result": extended_strings,
    }

The application is running properly.
Then I change the code of Code Execution Node 1 to make the original_strings_with_empty have less elements.
def main() -> list:
    original_strings_with_empty = ["apple", "", "cherry", "date", "", "fig", "grape", "honeydew", "kiwi", "", "mango", "nectarine", "orange", "papaya"] * 5

    extended_strings = []

    for s in original_strings_with_empty:
        if s:
            repeat_times = 600
            extended_s = (s * repeat_times)[:3000]
            extended_strings.append(extended_s)
        else:
            extended_strings.append(s)

    return {
        "result": extended_strings,
    }

The application is also running properly.
According to my understanding, I have configured the environment variables correctly, but the application still reports an error. It cannot handle a string array with  more than 3000 elements per string.
✔ Expected Behavior
The application is running properly.
❌ Actual Behavior
Run failed: Node Code Execution run failed: Failed to parse result
In the template_transformer.py file of the dify source code, there is a function named extract_result_str_from_response. Debugging the code that triggers the Run failed: Node Code Execution run failed: Failed to parse result error. It is found that the input parameter response format of extract_result_str_from_response is incorrect.
The incorrect response is as follows:
<<RESULT>>{
    "result": [
        "appleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleappleapple",
      ................................................ (A lot of content is omitted here for simplicity)
        "ugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruitugli fruit",
        "vanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla beanvanilla bea

As you can see, the content of the response variable is not complete, there is no << RESULT >> at the end, and the content of "result": is also incomplete.
The content of the response variable is obtained by the following statement
response = post(str(url), json=data, headers=headers, timeout=CODE_EXECUTION_TIMEOUT)
I run the preceding test code in the dify-sandbox-1 container. The code is all working fine. So I think that maybe the POST request is truncated.

This issue is extremely critical, and it occasionally arises. I hope it can be resolved promptly. TOT

Resolved #41


ZendViewRenderer: cannot set layout from within a .phtml template script

When Zend\View\Helper\Layout helper called from inside a .phtml scope throws "getRoot: no view model currently registered as root in renderer". Error is thrown at "../vendor/zendframework/zend-view/src/Helper/Layout.php:64" because root is not set so setTemplate() fails.
REPRO:
put this line into any non-layout template script:
$this->layout('layout/non-default.php');

Obviously the layout path/map has to be set in config/autoload/templates.global.php
RESEARCH DONE:
The root ViewModel present is null when the helper tries to set template thus it fails. I suspect, that the root cause is that the ViewModel is fetched through DIC/ServiceManager, and at this point it it is already cached with null root. It was probably created in an other run.
I have no idea how to resolve this, sorry.
Could anybody with broader conceptual overview check this?
Thanks.

There are a few ways to resolve this.
First, and easiest: set a default layout in your configuration:
return [
    /* ... */
    'templates' => [
        /* ... */
        'layout' => 'layout::default',
    ],
];

Doing so ensures that the layout view model is injected in the renderer at instantiation.
The next approach is to provide a layout at the time you call render(); the documentation details two ways to do this.
Finally, within your template, you can inject a root view model manually prior to calling layout() in your template:
use Zend\View\Model\ViewModel;

$this->viewModel()->setRoot(new ViewModel());
$this->layout(/* ... */;

// OR, in one go:
$this->viewModel()->setRoot(
    (new ViewModel())->etTemplate(/* layout you want to use */)
);

Yes, outside the template these are clearly working.
But do not actually work within the template neither with your last two solutions.
These solutions only mitigate the exception but do not succeed in modifying the parent template, that is the layout. What you are injecting is only valid in the PhpRenderer::render scope, but it gets lost when the ZendViewRenderer::renderModel loop iterates, eg. when it bubbles up to render the layout. So setting the layout in the template / PhpRenderer::render scope is not successful. Could you please validate this scenario?
Obviously this is not a blocking issue, but would be very elegant to be able to use it just like with the regular ZF2 MVC.

@djozsef Ah, right; once you've called render(), if there is no root view model in place, then the current view model is root, which means no layout. As such, my first two were what you need to do. To recap:

provide a default layout in your configuration. If you do this, you can change the layout without an issue.

provide a layout when you call render(); this can be done by providing a layout variable, which can either be the string name of the layout to use, or the layout view model to use:
$renderer->render('template::name', ['layout' => 'use::this::layout', /* other variables */]);
$renderer->render('template::name', ['layout' => $layoutViewModel, /* other variables */]);

The takeaway is: you must have a layout in place before you call the helper in the template. Otherwise, it will raise an exception, as you've already noted.
Now, for the long explanation.
The reason is because once we pass off rendering to the PhpRenderer, all it does is look at the view model it has received. If that view model has children, it does a depth-first approach, rendering from the deepest child on out to the root view model. When you call layout() from any of the descendants, what the helper does is traverse back up the tree until it gets to the root view model, and then changes the template name on it.
In the case you've indicated, no layout was provided. This means that the current view model is the root, and when you call layout(), it cannot traverse upwards; there is no root view model at this time. As such, you've created an exceptional situation, and it properly errors.
Again, the takeaway: set a default layout in your configuration or provide a layout when you render.
Believe it or not, the only difference between this and the zend-mvc workflow is that in Expressive, we're not providing a default layout view model. The reason is simple: if we make that the default, then there's no way to render layout-less templates. A number of developers were quite interested in being able to do exactly that (e.g., to deliver rendered HTML snippets over XHR), which led to this implementation.

@weierophinney Thanks for summing up the full story. Given a deeper thought this is absolutely fine like this. Maybe we should include it in the docs.

Sotty, i try the expressive now, and this error occurred for me, but your informations and the readdocs not are clear for my, where make this modification? which files?

@IgorDePaula Not sure if it helps you but the docs have moved to their final location at https://zendframework.github.io/zend-expressive/features/template/zend-view/#layouts

@IgorDePaula You cannot set the layout from within a template when using ZendViewRenderer. You have to pass the layout's name to the render() method along with the view data in the same structure (array or ViewModel). So in your middleware where you render the HTML output you would do something like this:
public function __invoke(ServerRequestInterface $request, ResponseInterface $response, callable $next = null)
{
    $viewData = array(
        "layout" => "templates/app/layout.phtml",
        "title" => "Hello World Title",
        "text" => "Lorem ipsum dolor sit amet ..."
    );
    $html = $renderer->render("templates/app/home.phtml", $viewData)
    return new HtmlResponse($html);
}

I written this form, but thw getting start recommend the sue of layout view
helper. This hour occurred thw error.
Em 19/02/2016 19:26, "József Dubravszky"<EMAIL_ADDRESS>escreveu:

@IgorDePaula https://github.com/IgorDePaula You cannot set the layout
from within a template when using ZendViewRenderer. You have to pass the
layout's name to the render() method along with the view data in the same
structure (array or ViewModel). So in your middleware where you render
the HTML output you would do something like this:
public function __invoke(ServerRequestInterface $request, ResponseInterface $response, callable $next = null){    $viewData = array(        "layout" => "templates/app/layout.phtml",         "title" => "Hello World Title",         "text" => "Lorem ipsum dolor sit amet ..."    );    $html = $renderer->render("templates/app/home.phtml", $viewData)    return new HtmlResponse($html);}
—
Reply to this email directly or view it on GitHub
https://github.com/zendframework/zend-expressive-skeleton/issues/68#issuecomment-186413497
.

I do all on this page

I got now. I needed disable many settings.


[scoped] Fix scoped prefixed UrlGeneratorInterface on RedirectToRouteRector

Fixes https://github.com/rectorphp/rector-symfony/issues/691

Fixed 🎉 /cc @biozshock


Add checkbox for namespace selector on Policy Server Create/Config page

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
No response
Expected Behavior
Allow the user to select a namespace or not
Steps To Reproduce
No response
Environment
- OS:
- Architecture:

Anything else?
No response


creaing the project in darkmode,provide a "button"  for darkmode and make project in darkmode as well

Description
will create a "darkmode" botton in navbar,which will change the background to black.
It do will change the backroung to black but I will also assign a theme to whole website for all pages,I will give same hover effect and box shdow effect in dark mode also for all pages.
Things I will do:-
create a "Darkmode " Buttton.
2)Create a dark mode for all pages.
3)make hover and transition effect to all cards and items(items which have hover or any other effect now will have effect in darkmode
also).
screenshot is for blue theme but if you want it can be in red theme as well..
https://github.com/user-attachments/assets/3dcf6f91-912a-4d79-b36b-28a2925714fb
Screenshots
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I'm a GSSoC'24-Extd contributor
[X] I'm a Hacktoberfest'24 contributor
[X] I am willing to work on this issue (optional)

If you have not merged the "Darkmode" conflict, then plz see to my video of darkmode
I can make it better.


Update index.html

add-links-and-lists

required

This is a link to GitHub!

This is a link to GitHub!

This is a link to GitHub!


[6.4.x] BZ-1322398 - Performance regression in starting a process which conta…

…ins a human task

merged into 6.4.x


Refs 114: Character sprite scaling fix

In order to solve problems listed in
https://github.com/mapedorr/popochiu/pull/141
room's method update_character_scale function name had been changed as it's private no more.
unfortunately in next PR:
https://github.com/mapedorr/popochiu/pull/142
one of references in popochiu_region restored the outdated name.
Following PR covers fix of:

above mentioned bug and
avoids transfer of characters' position to the next room (via character's position_stored variable)

LGTM, merging


Debugger fail

I have been unable to use the debugger for a couple of days, in this case debug50, and only get the following error message: Unable to launch debugger.
Version: 1.95.2
Commit: e8653663e8840adaf45af01eab5c627a5af81807
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Embedder: codespaces

This issue seems to be ongoing since 1.95 - I have had to revert to 1.94.2 to get the debugger to work with chrome.


Update install.sh

Take a snapshot after install.txt has run.

Looks good to me, I like the idea of taking a snapshot after running install.sh. Does the OS automatically take a snapshot on initial install, or do you think we might also want to take a snapshot both at the beginning of install.sh, and at the end.

The OS doesn't take a snapshot at the initial install. I put it in as a safeguard in case something in the install script breaks things by surprise.


Update whitenoise to 6.5

There's an encoding issue that affects iOS/Safari and I'm hoping this change resolves it (see whitenoise docs).

I was looking into this but I don't have experience with Heroku, pre-commit, or tox.
It seems like these are the necessary changes, using python 3.12 as the example:
[tox.ini] envlist = py312,lint
[.pre-commit-config.yaml]  language_version: python3.12
[runtime.txt] python-3.12.3
[ci.yml] python-version: "3.7"
[README.md] * Python 3.12+ (I actually don't know if this is necessary?)
I'm still new at all of this, so it might be naive to think changing 5 lines is enough.

That is pretty much exactly what I would do. However I suspect there may be some incompatible dependencies. After trying that upgrade and updating your dependencies things may require some additional changes.


Error in running gan_language.py

Hi, I have the following error in running gan_language.py. Any solution to this? I am using tensorflow v0.9
loaded 10000000 lines in dataset
Traceback (most recent call last):
File "gan_language.py", line 89, in
fake_inputs = Generator(BATCH_SIZE)
File "gan_language.py", line 65, in Generator
output = ResBlock('Generator.1', output)
File "gan_language.py", line 56, in ResBlock
output = lib.ops.conv1d.Conv1D(name+'.1', DIM, DIM, 5, output)
File "/auto/cmb-panasas2/ylu465/program/deeplearning/improved_wgan_training-master/tflib/ops/conv1d.py", line 93, in Conv1D
data_format='NCHW'
File "/auto/cmb-panasas2/ylu465/anaconda/envs/dl_env/lib/python2.7/site-packages/tensorflow/python/ops/nn_ops.py", line 1204, in conv1d
data_format=data_format)
File "/auto/cmb-panasas2/ylu465/anaconda/envs/dl_env/lib/python2.7/site-packages/tensorflow/python/ops/gen_nn_ops.py", line 394, in conv2d
data_format=data_format, name=name)
File "/auto/cmb-panasas2/ylu465/anaconda/envs/dl_env/lib/python2.7/site-packages/tensorflow/python/framework/op_def_library.py", line 703, in apply_op
op_def=op_def)
File "/auto/cmb-panasas2/ylu465/anaconda/envs/dl_env/lib/python2.7/site-packages/tensorflow/python/framework/ops.py", line 2319, in create_op
set_shapes_for_outputs(ret)
File "/auto/cmb-panasas2/ylu465/anaconda/envs/dl_env/lib/python2.7/site-packages/tensorflow/python/framework/ops.py", line 1711, in set_shapes_for_outputs
shapes = shape_func(op)
File "/auto/cmb-panasas2/ylu465/anaconda/envs/dl_env/lib/python2.7/site-packages/tensorflow/python/framework/common_shapes.py", line 230, in conv2d_shape
input_shape[3].assert_is_compatible_with(filter_shape[2])
File "/auto/cmb-panasas2/ylu465/anaconda/envs/dl_env/lib/python2.7/site-packages/tensorflow/python/framework/tensor_shape.py", line 108, in assert_is_compatible_with
% (self, other))
ValueError: Dimensions 1 and 512 are not compatible

solved by upgrade tensorflow from 0.9.0 to 1.0.1


Fix capitalization in SVG

Fixes the lowercase I in "Pulumi insights" in the timeline on the About page.

Much better ;)


DefaultHttp2RemoteFlowController reentry infinite loop

Motivation:
DefaultHttp2RemoteFlowController.writePendingBytes does not support reentry but does not enforce this constraint. Reentry is possible if the channel transitions from Writable -> Not Writable -> Writable during the distribution phase. This can happen if the user flushes when notified of the channel transitioning to the not writable state, and may be done if the user wants to fill the channel outbound buffer before flushing.
Modifications:

DefaultHttp2RemoteFlowController.writePendingBytes should protect against reentry

Result:
DefaultHttp2RemoteFlowController will not allocate unexpected amounts or enter an infinite loop.

@nmittler - PTAL

LGTM after addressing netkins commen

Am 13.07.2016 um 02:31 schrieb Scott Mitchell<EMAIL_ADDRESS>Motivation:
DefaultHttp2RemoteFlowController.writePendingBytes does not support reentry but does not enforce this constraint. Reentry is possible if the channel transitions from Writable -> Not Writable -> Writable during the distribution phase. This can happen if the user flushes when notified of the channel transitioning to the not writable state, and may be done if the user wants to fill the channel outbound buffer before flushing.
Modifications:
DefaultHttp2RemoteFlowController.writePendingBytes should protect against reentry
Result:
DefaultHttp2RemoteFlowController will not allocate unexpected amounts or enter an infinite loop.
You can view, comment on, or merge this pull request online at:
https://github.com/netty/netty/pull/5525
Commit Summary
DefaultHttp2RemoteFlowController reentry infinite loop
File Changes
M codec-http2/src/main/java/io/netty/handler/codec/http2/DefaultHttp2RemoteFlowController.java (32)
Patch Links:
https://github.com/netty/netty/pull/5525.patch
https://github.com/netty/netty/pull/5525.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@Scottmitch LGTM

4.1 (9de90d0)


bug: syntax highlighting is applied to comments

(Pascal source code)

Pascal commenting rules are literally the worst, feel free to try and implement them @ https://github.com/mattgodbolt/compiler-explorer/blob/master/static/modes/pascal-mode.js
Sent from my iPhone

On 14 Apr 2019, at 14:52, creaothceann<EMAIL_ADDRESS>wrote:
(Pascal source code)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Batch version delete

Delete specific blob versions via batch

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


feat: add new hotkeys

Add a new hotkey to fix the hotkey conflict on Windows/Linux.

Alt/Option + Shift + P

Add a new /lpt trigger

closes #12

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


UpdateIndex is incremented too often / script runs twice

see Issue #3

Oh sorry, the second update of README.md was only for my fork ...
I forgot that you hadn't merged the pull request yet...

@tm-107 No problem, I just reverted the commit, but it's not important to me to mention my battery / solar details. Actually it would be cool to give more details that it works with ESP8266 or mini or bitShake or Hichi IR, Cerbo or Cerbo-S or Rasberry or anything else.
By the way very nice solar pv installation. Sounds very similar to mine: 4x HM-1500, 4x HM-800, 3x HM-300


Create gh-page for the project

Hey, i want to help <3

Awesome @cbsorrilha \o/
The project already has a simple page, but if you want to improve it some how, feel free to do that. Open a issue with your suggestion.
In the near future I will add more components, so the page will need update and your help will be more than welcome. ;)


Cannot run multiple scripts (which are at the same location) in parallel

Hello,
Thanks for your cool project which is very useful !
It seems that, we cannot have a set of scripts that could be instantiated multiple times & run concurrently from the same location.

It seem that dotnet-script/src/Dotnet.Script.Core/Commands/ExecuteScriptCommand.cs GetLibrary method have an hardcoded 'default single name' for all scripts of the same location path which is : script.dll.
Is there a specific reason for that or are you able to use the scriptFileName or a GUID as unique identifier for example for your next release ?
Thanks a lot !

This is now fixed in v1.1.0 by #596. You can now run multiple scripts from the same folder in parallel.
Only if you run both scripts not cached and at the very same time, it could break because the they still share the same folder for building the assembly. This can not be changed, because it is required for OmniSharp to work.


Automated cherry pick of #746

Cherry pick of #746 on release-0.4.
#746: issuer/route53: fix delete for 'NotExist' errors

/lgtm
/approve


Update Composer dependencies (2021-05-20-00-06)

Visual regression test passed!
View the visual regression test report


unmached ] removed in auth.login function call doc

small change, an umached ] in the function call docs for auth.login.
probably left over from when it was used to wrap optional parameters.

Merged in a10cbbbc17d4244812ef713437fa44207fe1a223, thanks.


$channelAction, $roleAction, $emojiAction, $stickerAction

Featuring Type
Function
So, what is it about?
All these functions would work for the 'channelUpdate,' 'roleUpdate,' 'emojiUpdate,' and 'stickerUpdate' events, allowing us to obtain the specific action taken with that channel/role/emoji/sticker
In all these options, add the 'separator' parameter, which will separate the actions if more than one was performed on that channel/role/emoji/sticker
Code of Conduct

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

Isn't that what $new(eventname) / $old(eventname) does?

Yes, that's true, but what if someone wanted to make a different message for each change?

Yes, that's true, but what if someone wanted to make a different message for each change?

You can do that, just use the function/event multiple times.

Already exists as said functions.


Update use-mail-flow-rules-to-see-what-your-users-are-reporting-to-mi…

…crosoft.md
Per document -https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/submit-spam-non-spam-and-phishing-scam-messages-to-microsoft-for-analysis?view=o365-worldwide#submit-false-positives-to-microsoft it is<EMAIL_ADDRESS>to Submit false positives to Microsoft

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/3780


add slides

This looks great - thank you for helping to document and evaluate Pond's cryptographic security!


Limit the number of jobs JobSubmitter can submit per cycle

For cases the agent pulls a lot of work (>20k jobs in one cycle), JobSubmitter is taking a long time
to go through it's cycle of:

determining possible site locations
submitting them with the condor plugin
updating WMBS database
which in the end was not marking jobs as 'executing' in WMBS and bringing inconsistencies to the job tracking.

The idea with this patch is to limit each JobSubmitter cycle to 1k jobs maximum.

@ticoann please review

Hi Alan, I am not sure this can control how many jobs will be submitted in one cycle cache could build up for multiple cycle and if the available slot opens up suddenly it could submit many more jobs.
It might be better to check the length of whole dictionary here (not just one package)
https://github.com/dmwm/WMCore/blob/master/src/python/WMComponent/JobSubmitter/JobSubmitterPoller.py#L724
and if that exceed 1000 just brake out whole loop, not just inner loop.
What do you think?

refreshCache() is the source place for these jobs, that's why I put these changes there.
I guess your suggested check would work as well, the problem is that it would assign
site locations for all jobs available (refreshCache()), and this operation takes quite some
time.
I tested this patch in vocms0230, you can check the JobSubmitter logs between the following
timestamps:
2015-03-03 16:23:03,327
2015-03-03 16:31:48,077
where you can see it does not submit more than the slice size.
Maybe we could improve this slice size and make it configurable via parameter?

Hi Alan, I
refreshCache() is source place for the jobs but it is just filling up the cache not directly related to controlling the number of jobs to submit. Although in most cases,  Submiter will just empty the cache in the same polling cycle but it doesn't guarantee the number of jobs submitted will under the slice size.
i.e.
The first polling cycle, refreshCache() fills up the cache of 1000, but nothing gets submitted. next cycle it fills up 1000 more and suddenly slots available so it can submit all 2000 together.
But I guess if the db returns data in the same order every time. Cache won't get bigger.
However, in that case, it might be better control the number of jobs directly from the query.
https://github.com/dmwm/WMCore/blob/master/src/python/WMCore/WMBS/MySQL/Jobs/ListForSubmitter.py#L14
Something like following, (not completely sure about syntax)
In Oracle
where ROWNUM <= 1000;
in mysql
limit 1000

Patch updated and testing it now.

Seangchan, only now revisiting your 1st comment and the code I could understand your point... :-)
I'll update this patch along that line and keep the sql query with no limits. Sorry for the mess!

Ok, that should be it. At some point we should separate that code in diff functions to get rid of those ugly flag/breaks :-P
Tested in vocms0230

@ticoann does this patch looks ok for you now?

@amaltaro , sorry to get only into this now. This looks useful for Tier0 replays. For the larger ones we can be limited by JobSubmitter cycle time. For instance, we have a big repack replay going on with 70k jobs in the queue. Cycle time of the JobSubmitter (5 minutes) limits submission speed, so this patch should help.
One question though, is this safe against different job priorities or even changes in job priorities. Are we still guaranteed that priority is observed ? If we just arbitrarily limit how many jobs we look at this could become a problem...

That's true, with this patch you could decrease the JobSubmitter cycle. However, the main idea is that the component don't try to submit too many (several thousands) jobs in the same cycle, otherwise it can take several hours.
This patch doesn't really care about the job prios or type of tasks, though it seems to be a good idea to first sort by workflow prio and then by task prio. Anyways, I'd rather prefer making a new PR for that (master branch only).

This has been applied to all agents. However, something tells me I can improve this patch a bit.
Don't merge yet @ticoann , I'll try to improve it tomorrow.

Seangchan, I was checking how to improve a bit this patch and that would be by iterating over jobsToSubmit in the end of assignJobLocation(). However, that seems a bit dirt IMO...
Since this patch is in all the production agents for weeks now and we've not seen issues so far, if you agree I'd simply merge it for now. What do you think?

Is this need to be merged to master too?

Yep! A patch to 1.0.5_wmagent will be needed as well. I will take care of it on monday.


Deploy tor bridgedb orchestra integration

This is about merging and deploying this: https://github.com/ooni/orchestra/pull/88.
It's currently blocked by:
ooni/probe-engine#629
ooni/probe-engine#643
This is a follow up issue to: https://github.com/ooni/backend/issues/396

This is a follow up issue from: https://github.com/ooni/backend/issues/396

Hey folks, a brief update from Tor's side: wolpertinger should be up and running and is currently returning our (public) default bridges. I don't think it's a good idea to use OONI to probe our entire private bridge pool because we cannot tell the difference between a censor and a user running OONI. This makes it too easy for a censor to get private bridges. We may use wolpertinger to test some private bridges but we're currently planning on setting up bridgestrap on a VPS in a few countries and use it to probe most of our private bridges. Since we control these instances, we don't need to worry about censors pretending to be users.

Added this issue to the next Sprint, so we can take a look with @hellais at the orchestra deployment. My understanding, in any case, @NullHypothesis is that the API we previously agreed with should not change in any detail and you're just telling us that the service will return public default bridges only. Do I understand correctly? Thank you!

This has been merged and deployed.

Just as a side note, while it is deployed, we don't actually have a valid "bridges-api-key" so we aren't actually retrieving bridges from the distributor.
I guess we should discuss with @cohosh if it's still useful for us to test private bridges and if so get a bridges-api-key for wolpertinger.

Also cc'ing @meskio here because of his work on bridge distribution and testing.
Very cool! I agree with the comment by @NullHypothesis above, that for now it is most useful for us to use this to make sure OONI is up to date with Tor Browser's built-in bridges. We have some tentative plans to be more agile with our built-in bridges and our circumvention settings in Tor Browser, and this will help facilitate that. We can re-evaluate this in the future, and I'll let @meskio chime in as well if there are other bridges he thinks we should add.
I opened an issue to track the creation of an API key for you and have started working on it: https://gitlab.torproject.org/tpo/anti-censorship/bridgedb-admin/-/issues/1

Oh on that note, can one of you reply with an email address (and a PGP public key) I can use to send the private token?

I didn't even know wolpertinger existed :) One of the things I'm currently doing is a public API that provides the built-in bridges (and it doesn't require an api-key):
https://bridges.torproject.org/moat/circumvention/builtin
Is not yet in production, but I don't expect it to change. And  hopefully will get in production this month.
Anyway, I guess for OONI makes more sense to use wopertinger and with it we can decide if we want to provide.
I'm happy to hear that this channel exists with OONI, I'll give it some thinking if we can provide more bridges than the default ones. But the default is a good start.

@cohosh we list the GPG keys of every team member here: https://ooni.org/about/. (My public key is also available via GitHub: https://github.com/bassosimone.gpg)


Can't install because gradient has been removed

Spinner depends on gradient and gradient repo has been removed from GitHub.

Spinner is an old project that was poor in conception and poor in execution. I have no plans to maintain the project, but I may remake it from scratch with a better design philosophy when Fidget2 is released.
Feel free to fork it and make whatever changes you need, but good luck working with code that makes me cringe just thinking about it.


Create WebPushChannel2023

It should supersede WebPushSubscription2022
This should follow updates to latest 0.2 of the protocol.
Few suggestions:

reuse notify:sendTo (former target) and just define it as Push Endpoint from the PUSH API
advertise vapidPublicKey in the Subscription Resource description where Subscription Client will make Subscription Request. Discovery Resource also includes that description.

@uvdsl

#160 centralizes all custom references in one shared json file, all W3C and IETF references are already available at https://www.specref.org/ so they don't have to be defined by us.
This PR also provides a very generic Terminology section that can be included, it just references the Solid Notifications Protocol where most of the terms are originally defined.


🚀 Feature: Make "Password Protection" for shares mandatory

🔖 Feature description
It would be great to have the option (i.e. in Administration settings) to make the "Password Protection" field for shares mandatory.
🎤 Pitch
This way it would be possible to force your users to set Passwords for every share they create.

I'm using Pingvin to share pictures with family and friends and a lot of those users are not very tech-savvy.
This results in shares with personal photos being created without any security options (like password protection) set, that's why I was wondering if Password Protection could be defined as mandatory.
I know this is more of a "personal problem" so I'd understand if that's not a feature you see for your app, but I wanted to give it a try anyway 😉

Okay yeah this makes sense. Generally I implement features for Pingvin Share if I personally need them or multiple users want it, so I'll wait to implement this. If somebody else wants to see this feature feel free to upvote (👍) this issue.
I hope you understand that :)


Allow mail server port to be included in mail host name

By default the SMTP port will be 25. You should be able to override that by append ":port" to the mail server name. E.g.
smtp.mailtrap.io:2525

The autotests use this functionality


feat(dx): warn when passing undefined/null locations

This PR attempts to improve the warnings and error handling for a common problem encountered during development.
Background
There's an error message I've encountered several times on Vue Land:

TypeError: Cannot use 'in' operator to search for 'path' in undefined

This comes from router.resolve(), e.g.:

Playground

That's a silly example, it's rarely quite so obvious when someone is having this problem in a real application.
These two issues are both hitting the same problem (the first one is in the wrong repo):

https://github.com/vuejs/vue-router/issues/3735
https://github.com/vuejs/router/issues/992

You get something similar with null instead of undefined.
router.push(undefined) gives the same error, as that uses router.resolve().
Most commonly this is hit via useLink(). Here's a simple example of that:

Playground

Again, I've made it obvious what the problem is with to: undefined, but real code is rarely so blatant.
It is possible to hit this same error via RouterLink, but in that case we get a prop validation warning, making it a bit easier to figure out what the problem is:

Playground

The mistake in that example is a typo in patn: '/about'.
But even with the prop validation warning, it can be difficult to identify exactly which component has the problem. If we could inspect the components using Vue Devtools it'd be much easier, but that isn't currently an option because rendering bombs out.
The Vuetify problem
Someone on Vue Land was hitting this error, but without any warnings to indicate what they were doing wrong. They weren't using RouterLink, they were using Vuetify's breadcrumb component.
The ultimate cause of the problem was an undefined in their data that they hadn't taken into account. But this isn't quite as simple as it sounds.
There's this problematic line in Vuetify:

https://github.com/vuetifyjs/vuetify/blob/c8503b1e0d9669bfc384ba563d5211922ea33e80/packages/vuetify/src/composables/router.tsx#L68

The problem here is that props.to can be undefined. While the Vuetify composable does check that, it only checks the initial value. In the application we encountered on Vue Land, the to prop was populated initially, only becoming undefined after some new data loaded.
It isn't obvious to me how Vuetify could fix this problem in their own code. There doesn't seem to be a way to disable the useLink() composable when the prop is undefined and re-enable it when the value is defined.
This PR doesn't attempt to address that problem directly, it just aims to improve the warnings/errors to ease debugging.
What's changed

router.resolve() no longer throws an error in dev. It logs a warning instead. This allows Vue Devtools to be used to debug the problem.
useLink() logs warnings. This is usually a bit more helpful than the warning in router.resolve(), as it has more context to work with.
Vue Devtools will show an error label if props.to is invalid, making it much easier to find a rogue RouterLink in a long list:

In cases where RouterLink has an undefined or null value for to, this will lead to 3 warnings being shown: one for prop validation, one for useLink() and one for router.resolve(). I couldn't see an easy way to avoid that, but I think that's much better than not having the warnings.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 91.02%. Comparing base (13303bd) to head (0b483f9).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2158      +/-   ##
==========================================
+ Coverage   90.90%   91.02%   +0.12%
==========================================
  Files          24       24
  Lines        1121     1137      +16
  Branches      347      352       +5
==========================================
+ Hits         1019     1035      +16
  Misses         63       63
  Partials       39       39

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


call to Braiins API is returning error

Getting an error when selecting Braiins pool specific tags.
Error
Cannot retrieve data from Braiins Pool, check you API token: error decoding response body: missing field confirmed_reward at line 1 column 492.
Solution
Probably an change to their response body. Will investigate.

Fixed in version 0.2.0