Fix test cases

Fixes https://github.com/asaskevich/govalidator/issues/380
Test cases were broken for two reasons:

Multiple errors gets appended into an Errors struct without any guarantee on the order, so string comparison with the expected value sometimes fails when the order doesn't match.
<EMAIL_ADDRESS>returns false instead of the expected true.

This PR fixes both, by sorting the errors array when stringifying, and removing the broken email test case.

Thank you!


WordPress 6.1 Testing

WordPress 6.1 will be here soon. Need to test the WordPres stack to make sure everything works as expected.

[x] Install the WordPress Beta Tester plugin
[x] Upgrade to WordPress nightly
[x] Test all the things both in the backend and frontend
[ ] Report any issues / open PR to fix

Been working on 6.1-nightly for a few days. So far so good...


WIP: needs commit splitting

This is in nascent condition and will be susceptible to a lot of changes.
This PR can even be pointless.

Hound's review should be ignored here as the CM addons are pulled from upstream v5.11.0

This pull request introduces 2 alerts when merging 88a7445160acf2415927bbdee35b137918ac05eb into 6a4f68b56b0ec32d813b99c11fd1a2a5212f4719 - view on LGTM.com
new alerts:

1 for Unmatchable caret in regular expression
1 for Superfluous trailing arguments

Comment posted by LGTM.com

This pull request introduces 2 alerts when merging 231602df707fd73b3bbff58471b55bf846d9699d into 6a4f68b56b0ec32d813b99c11fd1a2a5212f4719 - view on LGTM.com
new alerts:

1 for Unmatchable caret in regular expression
1 for Superfluous trailing arguments

Comment posted by LGTM.com


Error while applying custom icon

Environment
Windows build number: [Version 10.0.18363.815]
Windows Terminal version (if applicable): 0.11.1251.0

Any other software?

Nushell 0.13.0

Steps to reproduce

Install nushell in the folder C:/bin/nu/ as per the instructions on nushell.sh.
Place an icon at C:/bin/nu/nu.ico
Use the following profile:
{
    // Make changes here to the nu profile
    "guid": "{95c5a4fe-f9d7-4e85-a2d7-843317b06ad8}",
    "name": "nu",
    "commandline": "nu.exe",
    "icon": "C:/bin/nu/nu.ico",
    "hidden": false
},

Expected behavior

The icon shows up beside the name in the "new tab" dropdown. Without error.
Actual behavior

I'm getting the following error:

Interesting. What if you use \\ instead of /?

{
    // Make changes here to the nu profile
    "guid": "{95c5a4fe-f9d7-4e85-a2d7-843317b06ad8}",
    "name": "nu",
    "commandline": "nu.exe",
    "icon": "C:\\bin\\nu\\nu.ico",
    "hidden": false
},

no luck. I still get the same error.

I am using "icon" : "%PROGRAMFILES%\\Git\\mingw64\\share\\git\\git-for-windows.ico", for my Git-Bash profile, and "icon": "C:\\Tools\\PowerShell\\7\\assets\\Powershell_black.ico" for my Powershell7 profile. Both of these work.

Can you attach a copy of c:\bin\nu\nu.ico?

you can get the icon file here: http://s000.tinyupload.com/index.php?file_id=19101557016265546260
I made it myself, if that's a concern.
Program used: lunacy

So, this definitely works for me. Nice icon!
Can you run the following command, from powershell?
Get-FileHash C:\bin\nu\nu.ico

and share the output?
Thanks!

Here you go:
PS C:\Users\maximousblk> Get-FileHash C:\bin\nu\nu.ico

Algorithm       Hash                                                                   Path
---------       ----                                                                   ----
SHA256          F0758BCC516C0A81A159999DE3F282D89D726DC94BFAEABAEEA9B36CF075A3FC       C:\bin\nu\nu.ico

If it works for you, does it have something to do with my installation?

Would you mind sharing the rest of your settings file? Thanks!

// This file was initially generated by Windows Terminal 0.11.1121.0
// It should still be usable in newer versions, but newer versions might have additional
// settings, help text, or changes that you will not see unless you clear this file
// and let us generate a new one for you.

// To view the default settings, hold "alt" while clicking on the "Settings" button.
// For documentation on these settings, see: https://aka.ms/terminal-documentation
{
    "$schema": "https://aka.ms/terminal-profiles-schema",

    "defaultProfile": "{9695D2D6-65E7-4DB5-9AE9-C857416E9ABA}",

    "theme": "dark",

    // You can add more global application settings here.
    // To learn more about global settings, visit https://aka.ms/terminal-global-settings

    // If enabled, selections are automatically copied to your clipboard.
    "copyOnSelect": false,

    // If enabled, formatted data is also copied to your clipboard
    "copyFormatting": false,

    // A profile specifies a command to execute paired with information about how it should look and feel.
    // Each one of them will appear in the 'New Tab' dropdown,
    //   and can be invoked from the commandline with `wt.exe -p xxx`
    // To learn more about profiles, visit https://aka.ms/terminal-profile-settings
    "profiles": {
        "defaults": {
            // Put settings here that you want to apply to all profiles.
            "colorScheme": "Dracula",
            "closeOnExit": "graceful",
            "startingDirectory": "%USERPROFILE%",
            "fontFace": "JetBrains Mono",
            "fontSize": 12,
            "padding": "16"
        },
        "list": [
            {
                // Make changes here to the Cmder profile
                "guid": "{9695D2D6-65E7-4DB5-9AE9-C857416E9ABA}",
                "name": "Cmder",
                "commandline": "cmd.exe /k %CMDER_ROOT%\\vendor\\init.bat",
                "icon": "%cmder_root%/icons/cmder.ico",
                "hidden": false
            },
            {
                // Make changes here to the nu profile
                "guid": "{95c5a4fe-f9d7-4e85-a2d7-843317b06ad8}",
                "name": "nu",
                "commandline": "nu.exe",
                "icon": "C:/bin/nu/nu.ico",
                "hidden": false
            },
            {
                "guid": "{ced5fbe8-313c-4760-9a4b-ed66b4901125}",
                "name" : "Git Bash",
                "commandline" : "C:/Program Files/Git/bin/bash.exe -li",
                "icon" : "C:/Program Files/Git/mingw64/share/git/git-for-windows.ico",
                "startingDirectory" : "%USERPROFILE%"
            },
            {
                // Make changes here to the cmd.exe profile.
                "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
                "name": "Command Prompt",
                "commandline": "cmd.exe",
                "hidden": false
            },
            {
                // Make changes here to the powershell.exe profile.
                "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",
                "name": "Windows PowerShell",
                "commandline": "powershell.exe",
                "hidden": false
            },
            {
                "guid": "{2c4de342-38b7-51cf-b940-2309a097f518}",
                "name": "Ubuntu",
                "source": "Windows.Terminal.Wsl",
                "hidden": false
            },
            {
                "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}",
                "name": "Azure Cloud Shell",
                "source": "Windows.Terminal.Azure",
                "hidden": true
            }
        ]
    },

    // Add custom color schemes to this array.
    // To learn more about color schemes, visit https://aka.ms/terminal-color-schemes
    "schemes": [
        {
            "name": "Dracula",
            "background": "#282A36",
            "black": "#21222C",
            "blue": "#BD93F9",
            "brightBlack": "#6272A4",
            "brightBlue": "#D6ACFF",
            "brightCyan": "#A4FFFF",
            "brightGreen": "#69FF94",
            "brightPurple": "#FF92DF",
            "brightRed": "#FF6E6E",
            "brightWhite": "#FFFFFF",
            "brightYellow": "#FFFFA5",
            "cyan": "#8BE9FD",
            "foreground": "#F8F8F2",
            "green": "#50FA7B",
            "purple": "#FF79C6",
            "red": "#FF5555",
            "white": "#F8F8F2",
            "yellow": "#F1FA8C"
        }
    ],

    // Add custom keybindings to this array.
    // To unbind a key combination from your defaults.json, set the command to "unbound".
    // To learn more about keybindings, visit https://aka.ms/terminal-keybindings
    "keybindings": [
        // Copy and paste are bound to Ctrl+Shift+C and Ctrl+Shift+V in your defaults.json.
        // These two lines additionally bind them to Ctrl+C and Ctrl+V.
        // To learn more about selection, visit https://aka.ms/terminal-selection
        {
            "command": { "action": "copy", "singleLine": false },
            "keys": "ctrl+c"
        },
        { "command": "paste", "keys": "ctrl+v" },

        // Press Ctrl+Shift+F to open the search box
        { "command": "find", "keys": "ctrl+shift+f" },

        // Press Alt+Shift+D to open a new pane.
        // - "split": "auto" makes this pane open in the direction that provides the most surface area.
        // - "splitMode": "duplicate" makes the new pane use the focused pane's profile.
        // To learn more about panes, visit https://aka.ms/terminal-panes
        {
            "command": {
                "action": "splitPane",
                "split": "auto",
                "splitMode": "duplicate"
            },
            "keys": "alt+shift+d"
        }
    ]
}

Here's all of it. I currently have NuShell disabled until this issue is resolved.

I updated to nushell 0.14.0 but that doesn't seem to help. This doesn't happen with any other profile.

@DHowett-MSFT I updated windows terminal to v0.11.1333.0 (1.0rc2) but still this doesn't fix it. It's really annoying.

Does it work if you run as administrator? Do the permissions to C:\bin\nu\nu.ico allow unelevated user access? That's all I can think of.

Huh that’s a really good thought! Yeah, I’ve been coming up blank. The best we can do is add more info to the error message, but it would be ugly and full of those windows hex codes everyone hates.

Huh that’s a really good thought! Yeah, I’ve been coming up blank. The best we can do is add more info to the error message, but it would be ugly and full of those windows hex codes everyone hates.

You can add a link to the full error log below the current error messages

Does it work if you run as administrator? Do the permissions to C:\bin\nu\nu.ico allow unelevated user access? That's all I can think of. I store all my non standard icons (and a backup of my settings) in a Terminal folder in Documents to avoid permission problems.

Yes I've tried running it as administrator. I've also tried changing the location of the icon file. But it doesn't seem to help.

FIXED
This is weird. I started changing and switching back every setting on-by-one and it fixed it self!
I don't know how this happened. I changed NuShell icon to git bash icon and it worked. Then I changed it to Cmder icon. And when I switched back, the logo was set without any error.
here is the current Nushell profile:
{
    // Make changes here to the nu profile
    "guid": "{95c5a4fe-f9d7-4e85-a2d7-843317b06ad8}",
    "name": "nu",
    "commandline": "nu.exe",
    "icon": "C:/bin/nu/nu.ico",
    "hidden": false
},

And the old profile:
{
    // Make changes here to the nu profile
    "guid": "{95c5a4fe-f9d7-4e85-a2d7-843317b06ad8}",
    "name": "nu",
    "commandline": "nu.exe",
    "icon": "C:/bin/nu/nu.ico",
    "hidden": false
},

No difference right? I don't get it either.
@DHowett This is solved for the most part but the mystery still remains, how did it happen in the first place?
This can be closed. Thank You.

I have exact the same issue with yours, and I fixed it by accident, with a same way too. That is so wired. Orz...

What the heckkkk?
Maybe there was a zero width space in there? Surely that would have been shown by layout editor. Wow.
Thanks for following up. Sorry about the mystery!


Remove DatabaseHelper in favor of MongoClient

Closes #35.
Implements the solution provided by #35 and propagates the change to all the affected functions

Bro forgot the login token for CI

@Nydauron  Thanks for the PR! For now, I might keep the database handler abstraction logic (just for portability purposes in case we extend to a different database), but will definitely steal your MongoClient idea and implement that

just for portability purposes in case we extend to a different database

The reason why I just removed the DatabaseHelper class is bc imo it doesn't really achieve any beneficial abstraction. If, say, you were to change databases s.t. the query language is now, say Postgre, the abstract functions signatures in DatabaseHelper would all change, resulting in a full codebase refactor regardless.
I'll add my two cents here, but if you truly wanted an abstract helper class for databases, it's better to have something like this:
https://github.com/HackIllinois/api/blob/b2ef184b6ddbfc2a4fa3d88321237424ba8e5361/common/database/database.go#L13-L34
However, I still don't see if the gains from abstraction outweigh the costs with DatabaseHelper or in the code snippet I gave. You effectively lose ownership of the client instance once you wrap it in a derived class, and if you make an abstract base class, you have to then reimplement all fundamental features for all derivatives. If you say you had to manage multiple types of databases/keystores at runtime, I could see how an abstract class would be useful, but at this small scale, that doesn't seem like it would be the case.
To me, if you want a level of database abstraction, then ORMs are better than making your own abstract class.
Alright, rant done. Ty for looking at the PR.


TMP files in C:\Windows\Temp on Exchange mailbox servers

At least for Exchange 2016, the C:\Windows\Temp folder fills up on Exchange mailbox servers deployed via this QuickStart. The log files show errors with Unified Messaging. In Services.msc the Unified Messaging service keeps  attempting to start.
Would it be possible to disable the installation of the Unified Messaging service or to at least provide the option in the template to do so?

Here is an example of one of the Windows logs (event 1038 in the Windows Application log):
The Microsoft Exchange Unified Messaging service wasn't able to start. More information: "System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Rtc.Collaboration, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.Rtc.Collaboration, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
   at Microsoft.Exchange.UM.UMService.UMConnectionManagerHelper.TCPConnectionManager.Initialize()
   at Microsoft.Exchange.UM.UMService.UMConnectionManagerHelper.MultiConnectionManager.Initialize()
   at Microsoft.Exchange.UM.UMService.UMService.InitializeConnectionManager()
   at Microsoft.Exchange.UM.UMService.UMService.InternalStart()
   at Microsoft.Exchange.UM.UMCore.UMServiceBase.StartService()
   at Microsoft.Exchange.UM.UMCore.UMServiceBase.OnStartInternal(String[] args)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
"

Hi @rosenbluh, thanks for raising this; does the Exchange installation log report a successful installation?

I see the following line in the ExchangeSetup.log file that suggests it completes successfully, but I am not very familiar with this log file. I've redacted the domain and username in the full file so it can be uploaded.
[10/30/2019 08:17:51.0020] [1] Processing component 'Unified Messaging PostSetup' (Finalizing Setup for Mailbox role: Unified Messaging service).
[10/30/2019 08:17:51.0020] [1] Executing (non-critical):
	start-SetupService -ServiceName MSExchangeUM

Please see the attached log file.
ExchangeSetup.log

I should have mentioned this initially but I have attempted multiple deploys of this QuickStart in the past few weeks and they have all had this problem.


Wrap labels to fix screen size

Description
Update label container from row to wrap to wrap content inside the screen.
Fixes #443
Type of change

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

Screenshots
Before

After

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

@UdeshUK Please let me know if this has any conflicts with the previous PR


Hue JsonDecoderError

Home Assistant release (hass --version): 0.46.1
Python release (python3 --version): 3.5.1+
Component/platform: Hue
Description of problem: Hue is not reporting correctly the state of a bulb and there's a error on log while trying to init the hue component. Sometimes i can turn on the light, but not turn off or toggle it. At first i just let hass discover my 1gen hue bridge, but later I configure it explicitly. After using this configuration, I'm getting this error: Invalid data at row #97: start(Thu Jun 15 2017 13:01:06 GMT-0300 (-03)) > end(Thu Jun 15 2017 13:01:02 GMT-0300 (-03)).
 (see screenshot).
Expected:
Problem-relevant configuration.yaml entries and steps to reproduce:
- platform: hue
  host: <IP_ADDRESS>
  allow_unreacheable: true
  allow_hue_groups: false
  homebridge_hidden: true
  scan_interval: 12

Traceback (if applicable):
2017-06-15 12:58:46 ERROR (MainThread) [homeassistant.components.light] Error while setting up platform hue
Traceback (most recent call last):
  File "/home/usuario/hass/lib/python3.5/site-packages/homeassistant/helpers/entity_component.py", line 160, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT, loop=self.hass.loop)
  File "/usr/lib/python3.5/asyncio/tasks.py", line 392, in wait_for
    return fut.result()
  File "/usr/lib/python3.5/asyncio/futures.py", line 274, in result
    raise self._exception
  File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/home/usuario/hass/lib/python3.5/site-packages/homeassistant/components/light/hue.py", line 138, in setup_platform
    allow_in_emulated_hue, allow_hue_groups)
  File "/home/usuario/hass/lib/python3.5/site-packages/homeassistant/components/light/hue.py", line 149, in setup_bridge
    config_file_path=hass.config.path(filename))
  File "/home/usuario/.homeassistant/deps/phue.py", line 629, in __init__
    self.connect()
  File "/home/usuario/.homeassistant/deps/phue.py", line 753, in connect
    self.register_app()
  File "/home/usuario/.homeassistant/deps/phue.py", line 707, in register_app
    response = self.request('POST', '/api', data)
  File "/home/usuario/.homeassistant/deps/phue.py", line 666, in request
    return json.loads(str(result.read(), encoding='utf-8'))
  File "/usr/lib/python3.5/json/__init__.py", line 319, in loads
    return _default_decoder.decode(s)
  File "/usr/lib/python3.5/json/decoder.py", line 339, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib/python3.5/json/decoder.py", line 357, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Additional info:

Ok. I agree. ty.

We have fully refactored Philips Hue. Please report any issues as new ones after release 0.66.


Demo site is broken @ http://rapla-rapla.rhcloud.com/rapla

HTTP Status 500 - Error during initialization see logs for details: org.rapla.server.internal.ServerServiceImpl could not be initialized due to null

Thank you for this error report, i reset the data.
Rapla currently does not like it if the admin removes the parent category
usergroups. Will fix the issue in the next release.
Regards
Chrsitopher
Christopher Kohlhaas
Geschäftsführer
erdkante GmbH
Firmensitz: Piusstraße 2, 50823 Köln
Telefon: +49<PHONE_NUMBER>4
Fax:  +49<PHONE_NUMBER>8
Email<EMAIL_ADDRESS>Registergericht: Amtsgericht Köln, HRB 83659
Geschäftsführer: Martin Geuer, Christopher Kohlhaas
2016-09-12 13:28 GMT+02:00 Michael Tesch<EMAIL_ADDRESS>
HTTP Status 500 - Error during initialization see logs for details:
org.rapla.server.internal.ServerServiceImpl could not be initialized due
to null
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rapla/rapla/issues/531, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABJVUNFcIrdyGuVJAnL0yiKooiuSV5LJks5qpTdvgaJpZM4J6fFW
.

It is broken again
rapla-rapla.rhcloud.com’s server DNS address could not be found.

rapla demo site is up. But with current not stable trunk version

Thank you, it works @ http://rapla.org/rapla-demo/rapla/index
and username = admin + empty password


METRON-1467: Replace guava caches in places where the keyspace might be large

Contributor Comments
Based on the performance tuning exercise as part of METRON-1460, guava has difficulties with cache sizes over 10k.  We, unfortunately, are quite demanding of guava in this regard so we should transition a few uses of guava to Caffeine:

Stellar processor cache
The JoinBolt cache
The Enrichment Bolt Cache

Test plan:
First, spin up full-dev and ensure things continue to work.
For myself, I created a new type called dummy, added some stellar enrichments, stellar threat triage enrichments and a triage rule to ensure things continued to work with stellar (exercising the stellar processor cache and the enrichment bolt cache).
Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
For all changes:

[x] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
[x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

For code changes:

[x] Have you included steps to reproduce the behavior or problem that is being changed or addressed?

[x] Have you included steps or a guide to how the change may be verified and tested manually?

[x] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
mvn -q clean integration-test install && dev-utilities/build-utils/verify_licenses.sh

[x] Have you written or updated unit tests and or integration tests to verify your changes?

[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

[x] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

For documentation related changes:

[x] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via site-book/target/site/index.html:
cd site-book
mvn site

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.

I ran this up with vagrant and ensured:

Normal stellar works still in field transformations as well as enrichments
swapped in and out new enrichments live
swapped in and out new threat intel live

+1 LGTM


Disallow add group to favorites

Resolves #76

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

Comparison is base (2ffe5e2) 98.14% compared to head (45a130f) 98.14%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #88   +/-   ##
=======================================
  Coverage   98.14%   98.14%
=======================================
  Files          51       51
  Lines         862      862
  Branches      184      184
=======================================
  Hits          846      846
  Misses          2        2
  Partials       14       14

Files
Coverage Δ

src/utils/table.ts
97.75% <100.00%> (ø)

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


Fix error on undoing the creation of a node that you are currently renaming

Fixes #87406
I'm not 100% sure why it was checking if the tree was editing an item and prevented update in this case but it does not seems to be causing any issue to remove it and it fixes the issue. I would really like to have the opinion of the person who first added this check.
It was added here #44831 to fix #44163. I tested and can't reproduce the bug with my PR. But since the bug stated that it was not happening every time I would really like if people could test it a bit more.

The MRP from #44163 is cursed or something.
After reverting #44831 I can still reproduce that issue. It's consistent, but for some reason you need to reload the scene after first rename attempt if you want to trigger the bug again.
Then with your PR this happens:
https://github.com/godotengine/godot/assets/2223172/5e6054b8-5ff3-4042-9b7f-e779e6acd9ff
When trying to rename the node, the popup will randomly disappear. Again, it happens in the same MRP and I'm not sure how to reproduce it in another project. Seems like something causes tree update when you select a node.


Unable to convert MRCNN model to .tflite model

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): macOS High Sierra 10.13.4
TensorFlow installed from (source or binary): source
TensorFlow version (use command below):
python3 -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)" /anaconda3/lib/python3.5/site-packages/h5py/__init__.py:34: FutureWarning: Conversion of the second argument of issubdtype from floattonp.floatingis deprecated. In future, it will be treated asnp.float64 == np.dtype(float).type. from ._conv import register_converters as _register_converters b'v1.7.0-1844-ga0edcf60f7' 1.7.0
Python version: 3.5
Bazel version (if compiling from source):
bazel version Build label: 0.10.0-homebrew Build target: bazel-out/darwin-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar Build time: Wed Jan 10 02:02:06 +50057<PHONE_NUMBER>726) Build timestamp:<PHONE_NUMBER>726 Build timestamp as int:<PHONE_NUMBER>726
GCC/Compiler version (if compiling from source):
gcc --version Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk/usr/include/c++/4.2.1 Apple LLVM version 9.0.0 (clang-9<IP_ADDRESS>) Target: x86_64-apple-darwin17.5.0 Thread model: posix InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
CUDA/cuDNN version:
N/A
GPU model and memory:
N/A
Exact command to reproduce:
bazel-bin/tensorflow/contrib/lite/toco/toco   --input_file=./mobile_mrcnn.pb --input_format=TENSORFLOW_GRAPHDEF  --output_format=TFLITE --output_file=/tmp/mobilenet_v1_1.0_224.tflite --inference_type=FLOAT --input_arrays=input_image,input_image_meta --output_arrays=output_node0,output_node1,output_node2,output_node3,output_node4,output_node5,output_node6 --input_shapes=1,224,224,3:1,89

You can collect some of this information using our environment capture script:
https://github.com/tensorflow/tensorflow/tree/master/tools/tf_env_collect.sh
You can obtain the TensorFlow version with
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
Describe the problem
When trying to convert an MRCNN from a frozen graph (.pb) file to (.tflite) using the tensorflow toco script, I get an Abort trap: 6 error with no explanation. Any advice on how to debug/add unsupported ops/functionality or just what went wrong would be great.

//
// Check consistency of array fields, check name.
void CheckEachArray(const Model& model) {
for (const auto& array_entry : model.GetArrayMap()) {
const auto& array = array_entry.second;
if (array->has_shape()) {
for (int d : array->shape().dims()) {
CHECK_GE(d, 1);
}
}
// It's OK to have a buffer or an alloc, but not both.
// (Since allocs are for transient arrays without a buffer).
CHECK(!array->buffer || !array->alloc);
if (array->buffer) {
// If there is a buffer, its type should be consistent with data_type.
CHECK(array->buffer->type == array->data_type);
// The presence of a fixed buffer should imply the presence of a fixed
// shape.
CHECK(array->has_shape());
// The shape flat-size should agree with the buffer length.
CHECK_EQ(array->buffer->Length(),
RequiredBufferSizeForShape(array->shape()));
}
// Check name.  Either "name_with_suffix_8", "name_with_port:3", but not
// "name_with_both:3_8".
const string& name = array_entry.first;
auto colon_pos = name.find_first_of(":");
if (colon_pos != string::npos) {
  CHECK_EQ(name.substr(colon_pos + 1).find_first_not_of("0123456789"),
           string::npos)
      << "Array name must only have digits after colon";
}
CHECK_GT(colon_pos, 0)
    << "First character of array name must not be a colon.";

}
}`
Is the error produced when converting this instance of the CropAndResize operation? Also, are there any tools you recommend for narrowing down the error, ie. valgrind or some toco specific util?

Using the order of operations, I'm pretty sure I've been able to narrow down to which crop_and_resize operation is causing the issue (assuming it is that function), and have seen that it might be the 4th tensor param that has 0 dim. Any suggestions on how to debugs? @andrehentz @aselle @asimshankar @suharshs

After some digging, I found that it was due to
 AllocateTransientArrays(model, kDefaultTransientDataAlignment);
from
if (SupportsPreallocatedWorkspace(output_format)) {
   AllocateTransientArrays(model, kDefaultTransientDataAlignment);
   LogDump(kLogLevelModelChanged, "AFTER ALLOCATION", *model);
}

in the void Transform(const TocoFlags& toco_flags, Model* model) call in ToolMain
and not from
Import(toco_flags, model_flags, graph_def_contents); in ToolMain.
Here's my output:
... dimension 0size: 1 dimension 0size: 4 2018-05-22 21:55:46.128895: I tensorflow/contrib/lite/toco/graph_transformations/graph_transformations.cc:39] Before dequantization graph transformations: 564 operators, 1155 arrays (0 quantized) from Transform from AllocateTransientArrays allocating mrcnn_detection/map/while/NextIteration from AllocateTransientArray from TransientArraySize dimension 0size: 1 dimension 1size: 1 dimension 2size: 1 dimension 3size: 0 2018-05-22 21:55:46.141249: F tensorflow/contrib/lite/toco/tooling_util.cc:664] Check failed: dim >= 1 (0 vs. 1) Abort trap: 6
Is this expected with the while op since it is not implemented for lite yet and is it alright if I comment out the SupportsPreallocatedWorkspace(output_format) conditional block?

Nagging Assignees @aselle, @suharshs: It has been 29 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

@Cpruce
Hi Do you find any solution for this specific issues? it seems like I have a similar issue.
F tensorflow/contrib/lite/toco/tooling_util.cc:664] Check failed: dim >= 1 (0 vs. 1)

@offthewallace
My workaround was to comment out the SupportsPreallocatedWorkspace(output_format) if clause since this is likely an unintentional fault. However, I haven't continued further since my model would need several ops implemented for lite.

I apologize, but your link to the source code is now broken. Could you fix it, and I will take a look.

Hi, I have similar problem with SSD_MobileNet trained with tensorflow object detection API.

@aselle https://github.com/matterport/Mask_RCNN/blob/master/mrcnn/model.py

Nagging Assignees @aselle, @suharshs: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Thanks, I'll take a look when I can.

Hi, I have same problem with SSD_MobileNet trained with tensorflow object detection API.

I too am seeing this with ssd_mobilenet in tf od api. Same message, different location

Nagging Assignees @aselle, @suharshs: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignees @aselle, @suharshs: It has been 29 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignees @aselle, @suharshs: It has been 44 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignees @aselle, @suharshs: It has been 59 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

+1 to this question "Is this expected with the while op since it is not implemented for lite yet and is it alright if I comment out the SupportsPreallocatedWorkspace(output_format) conditional block?" I'm running into the same thing with a custom model. Thanks!

Nagging Assignees @aselle, @suharshs: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

This might be because "while" is being used.
What is happening is that the conversion is trying to calculate the size of a given tensor based on its shape, which is [1, 1, 1, 0]. That means the tensor has no elements and the memory planning code doesn't like that. It is possible that shape inference in the presence of "while" yields this type of zero-element tensor.
We are working to get some form of flow control working in TF Lite. Until then I'm afraid it will be quite hard to convert models that contain "while" ops.

Nagging Assignees @aselle, @suharshs: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

For CropAndResize op or other unsupported ops, please look at this reference
As we work toward fleshing out the builtin op library for TensorFlow Lite, we've been working on an experimental feature that allows using select TensorFlow ops from within the TensorFlow Lite runtime. The goal is to help reduce some of the friction for using models that rely on ops not yet natively supported by TensorFlow Lite (at the cost of increased binary size). This feature requires opting in during model conversion, as well as adding an additional dependency. More details can be found here.
Feedback is very much appreciated (either via GitHub or directly via tflite@tensorflow.org), and we'll be adding and refining functionality over the coming weeks. Cheers.

Thanks, @achowdhery . Did you mean for "here" in "More details can be found here." to be a link we can look at?

Closing due to lack of activity. There has been significant progress on improving conversion support over the past year.


Support for jakarta.inject.Inject

When developing plugins/extensions it is often required to annotate constructors, etc with @Inject.  At the moment, Gradle only respects javax.inject.Inject.  However, javax.inject.Inject has been replaced with jakarta.inject.Inject.
Expected Behavior
Using jakarta.inject.Inject should behave just as if javax.inject.Inject were used.
Current Behavior
An example -
@jakarta.inject.Inject
public EnhancementTask(HibernateOrmSpec ormSpec, SourceSet mainSourceSet, Project project) {
    ...
}

leads to:
An exception occurred applying plugin request [id: 'org.hibernate.orm']
> Failed to apply plugin 'org.hibernate.orm'.
   > Could not create task ':hibernateEnhance'.
      > Could not create task of type 'EnhancementTask'.
         > The constructor for type EnhancementTask should be annotated with @Inject.

Context
With the general shifting of various projects from Oracle (javax.*) to Jakarta (jakarta.*), using javax.* will become (is, depending) a legal concern.  At the moment Gradle extensions are forced to continue to use javax.* - at least in this one case, which is very low-hanging-fruit.

Hi @sebersole!
I'd like to contribute to this project so I'd like to learn more about this issue.
I know that it's needed to refactor the imports to use jakarta.inject.* instead of javax.inject.*, but what about the retro-compatibility with the extensions that are using javax.inject.*? I think that it's needed to care about it... am I right?

You can have both on the classpath.  They define different packages.

Yeah, you're right @sebersole! I totally agree with you!
Sorry the misunderstood, but I mean that it's needed to adding support to jakarta.inject.* to work as the javax.inject.* feature instead of to just replace the importing of javax.inject.* by jakarta.inject.*, am I right?
With that, I think that it will need to mark the javax.inject.* utilization as Deprecated one, am I right?

Alternatively Gradle could define it's own inject annotation, as it does with @Input, @Output, @TaskAction etc.

Does Gradle use Guice? If so, you could upgrade to Guice 6 with supports both javax.inject and jakarta.inject, see https://github.com/google/guice/wiki/Guice600


Fix cgroup config

Fixes #842
We ensure that cri-o cgroup manager is compatible with the cgroup parent sent by k8s and do the right conversions to pass the cgroups to runc.

Seems ok, but dockershim in kubelet is doing thing differently https://github.com/kubernetes/kubernetes/blob/4d409a4d9e9772193cb24944bd76b90aaca01473/pkg/kubelet/dockershim/docker_service.go#L393 and it's always converting to systemd, which might mean it has the same bug

I'm testing what happens with Docker

So, spent some time analyzing the whole stuff here https://github.com/kubernetes-incubator/cri-o/issues/842#issuecomment-327428272
The result is, @mrunalp could you cherry-pick these 2 commits from #814:

https://github.com/kubernetes-incubator/cri-o/pull/814/commits/998a649cd4f8519e3a0b01d4604407b8996c42fe
https://github.com/kubernetes-incubator/cri-o/pull/814/commits/f3565d327199bcd44f0315e5c7b694e120367188

These 2 commits + your PR here will fix all cgroup issues.

Updated.

Looks good but we may want to change the sandbox_run cgpath code to look similar to this https://github.com/kubernetes-incubator/cri-o/commit/998a649cd4f8519e3a0b01d4604407b8996c42fe to handle defaults (w/o cgroup parent)

(note to self: we need to re-work https://github.com/kubernetes-incubator/cri-o/pull/814/commits/998a649cd4f8519e3a0b01d4604407b8996c42fe to use what in this PR in order to handle cases when cgroupparent == "", can't happen with kube though but still..)

Updated.

LGTM

[retest]

@runcom This is green :)


CustomValidators.equalTo() reverse validation doesn't works

When equalControl's value changes validation doesn't works.

@Invis1ble can you show more details?

@yuyang041060120 I've created the demo http://plnkr.co/edit/zcgWZBPklcdSNbnIJOA6?p=preview
Try to add some chars into the "Retype Pasword" field. The error "Passwords missmatch" should appears. Then add the same chars into the "Password" field - the error "Passwords missmatch" should disappears, but it doesn't.
Or the second case: try to add some chars into the "Password" field. The error "Passwords missmatch" should appear, but it doesn't.

@Invis1ble I got your point. But I'm too busy these days. I will fix it as soon as possible. Thank you!

@yuyang041060120 Hello, maybe I can implement this.. But I'm little bit in stuck with it.
What you think about this solution - wrap related controls into FormGroup? Looks nice.

@Invis1ble I fixed this bug. Maybe you can try again.

@yuyang041060120 is it break backward compatibility? When I will update your library, will it breaking my existing code?

@BioSin you are right! I corrected.

@yuyang041060120 Sorry, I can't test it for now, but I think it should works.
Is it possible to use equalTo without wrapping inputs in a group?

@Invis1ble I'm afraid not. If you have any idea, maybe you can contact me.


When string values are decoded, null values are added to the end of the string.

It looks like trimming white spaces at the end was intentional - suggest the following code to trim the null values as well.
export default function(value) {
  return value.replace(/\0/g, '').trim() || null;
}

I intend to investigate.

I don’t have any examples of dBASE files that have leading or trailing null characters in them, so I can’t reproduce this problem. According to the dBASE documentation, it’s expected that character and numeric fields are “padded with blanks to the width of the field”, and the interpretation of a blank character is 0x20 (SPACE), not 0x0 (NULL). If there is a case where you have a NULL-terminated string (rather than a SPACE-padded one), you probably want to find the index of the first NULL character and then slice the string at that point, rather than just dropping the NULL characters wherever they occur. But as I don’t have any .dbf files formatted this way, it’s just speculation. If you can provide me with some test files to reproduce this behavior, I would be happy to reopen this issue and investigate.


Test/unit test for POM and API learning

Eliran will open new PR when all unit tests + POM tests will be done.


Tag 4.0.0

Hey, you forgot to tag f1c465b36eb9b91a984d8864b21376e7c37075b8 as 4.0.0
Would be kind of you to do that.

Fixed


Add a second post/file

A second file needs adding to allow the directory to be split over multiple posts.

Reason: we will hit post char limit soon.

Done.  If you edit Directory2.md it will now push up to Directory post 2
Remember you can edit the titles here (POST_TITLE and POST2_TITLE)

Yes. I assume the API needs to be provided with a title, nighed set this up (I just changed it to a var to make it easier to edit).

Just to clarify, you need to make a change to the main body too to get the title change to push, as that doesn't trigger an update.


fix paths for doc and manifest.

still errors: [Error: Empty Manifest.json in library at /home/travis/build/qooxdoo/qooxdoo-compiler/node_modules/@qooxdoo/framework/framework]


When running interactive container, the tty initialization is too long

└> docker version
Client:
 Version:      1.12.3
 API version:  1.24
 Go version:   go1.7.3
 Git commit:   6b644ec
 Built:        Thu Oct 27 19:42:59 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.3
 API version:  1.24
 Go version:   go1.7.3
 Git commit:   6b644ec
 Built:        Thu Oct 27 19:42:59 2016
 OS/Arch:      linux/amd64

Explanation for the bugs are here: https://github.com/influxdata/influxdb/issues/7354
Basically when a container is started with the flags -it, it starts with a stty with

cols = 0
rows = 0

A few millisecond later, these values are intialized by docker, but still, there is a periode where the value is 0.
Is there a way to avoid this delay to happen?
Thanks.

(related to my request in https://github.com/docker/docker/issues/10341)

@Soulou I know that's a workaround but using stty rows and stty columns before your command might do the trick. However having a "parameter" like @vincentwoo asked would be a better solution.
I'm closing this since there's not built-in solution to achieve this and we already have an issue #10341 to address this.


[ANDROID] Error with react-native 0.66.3

A problem occurred configuring project ':react-native-mmkv'.

java.lang.RuntimeException: Unsupported ABI for NDK r19+: ARMEABI

"react-native-mmkv": "^1.5.3",
"react-native": "0.66.3",

with   ndkVersion = "21.4.7075529" the error occurred

I used ndkVersion = 22.0.7026061 and was able to build the app successfully. I am not sure if this issue is ndkVersion related but you can give it a try.

This seems unrelated. Let me know if you still have the error after cleaning everything, and if the error can be reproduced in the Example app - then I'll re-open the issue.

It was fixed for me after setting up ndk.dir property in local.properties


Update NetTruyen Domain

Checklist:

[X] Updated extVersionCode value in build.gradle for individual extensions
[ ] Updated overrideVersionCode or baseVersionCode as needed for all multisrc
[ ] Referenced all related issues in the PR body (e.g. "Closes #xyz")
[ ] Added the isNsfw = true flag in build.gradle when appropriate
[ ] Have not changed source names
[ ] Have explicitly kept the id if a source's name or language were changed
[ ] Have tested the modifications by compiling and running the extension through Android Studio
[ ] Have removed web_hi_res_512.png when adding a new extension

NetTruyen is dead, please approval for new URL.


Add build badges

This PR adds a number of build badges.

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


feat: update @typescript-eslint/* + update configs

Re-submission of https://github.com/mysticatea/eslint-plugin/pull/40

Codecov Report
Base: 97.17% // Head: 97.17% // No change to project coverage :thumbsup:

Coverage data is based on head (4e0c01b) compared to base (0f90860).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #22   +/-   ##
=======================================
  Coverage   97.17%   97.17%
=======================================
  Files          39       39
  Lines         390      390
=======================================
  Hits          379      379
  Misses         11       11

Impacted Files
Coverage Δ

lib/configs/_override-ts.js
100.00% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

@eslint-community/eslint-tsc @eslint-community/core-team @eslint-community/mysticatea-eslint-plugin Since this plugin is adhering the same semantic versioning policy as ESLint, adding new rules to a plugin would be a breaking change, so this PR would need to be released in a major release I guess?


docs: inform AsyncProducer Close pitfalls

Not closing AsyncProducer before process shutting down seems a common mistake when using it.
I believe it is worth to inform users that messages can be lost if they omit to call Close() when using AsyncProducer.

I've signed CLA :)

Thanks for your contribution! 🙏🏼


Proposal: CMake var renames: AZ_PLATFORM_IMPL => PLATFORM, USER => CUSTOM

If I check this in, I plan to do so after the release is cut.
We recently made better naming for our cmake variables (BUILD_PRECONDITIONS => PRECONDITIONS, and so on).
I think instead of AZ_PLATFORM_IMPL Cmake variable, we should use just PLATFORM.
And other thing, I think CUSTOM looks better and clearer to me in naming/intent (to me it does), than USER. If you don't like this part, I can remove just this rename.
Let me know what you think!

Should we combine PLATFORM and USER_PLATFORM_NAME?

If you set it to "WIN32", it is az_win32.
If you set it to "POSIX", it is az_posix.
If you set it to "NONE", it is az_noplatform.
If you don't set it, it is "AUTO" (see below).
If it is "AUTO", then it is "WIN32" on windows, and "POSIX" on Linux/MAC/BSD (we'll do our best effort to detect via CMake)
If it is anything else, it is equal to what today is "USER_PLATFORM_IMPL_NAME" ("CUSTOM_PLATFORM_NAME" in this PR)

@vhvb1989 is restructuring how we build/link platforms now, and even if we may want some ideas from this PR, they will be in another places, so I am closing this PR without merging.


[FLINK-7778] [build] Shade Curator/ZooKeeper dependency

What is the purpose of the change
This PR shades and relocates curator&zookeeper into flink-runtime to avoid dependency conflicts, primarily with hadoop.
This PR is based on work done by @StephanEwen. I only resolved the remaining issues:

flink-mesos did not compile since it relies on the flink-runtime zookeeper dependency, which was now relocated (the process of which is not visible to flink-mesos). This was fixed by adding a relocation to flink-mesos for zookeeper that must at all times be in sync. A cleaner solution would be to create a dedicated flink-shaded-curator/zookeeper module that both flink-runtime/mesos work against.
flink-tests test execution failed since it couldn't find a relocated curator test class. The relocation pattern for curator in flink-runtime was also applied to curator-test; however the relocated version is not included in the test jar and was thus not accessible to other modules. This was fixed by adding an relocation exclusion for classes from org.apache.curator.test.
flink-yarn test execution failed since it couldn't find the unshaded guava Function class. Curator is indeed shading&relocating guava, unfortunately not all of it. As such it was needed to re-add flink-shaded-curator-recipes including the guava relocation. While it would have been possible to do the relocation in flink-runtime I instead opted for the known working solution.

Brief change log

shade&relocate zookeeper and flink-shaded-curator recipes into flink-runtime
add a relocation for zookeeper to flink-mesos, in sync with flink-runtime
remove flink-shaded-curator-test, since it is simply no longer needed
add travis checks to ensure no unshaded curator/zk make it into flink-dist
JobManagerHAJobGraphRecoveryITCase was moved to flink-runtime to resolve a ClassCastException related to ZK or smth

Verifying this change
I've only made sure that things compile and tests can be run successfully. I have not tried this in an actual cluster setting due to time constraints.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

Changes look good! @StephanEwen could you please have a look at the follow-up changes?

Looks good!
I would suggest two followups:

We can probably drop flink-shaded-curator as well, because curator shaded guava by itself in the currently used version (still needs an exclusion because they do not build the dependency reduced pom).
Add a ZooKeeperAccess util in flink-runtime for the access to ZooKeeper done in flink-mesos. That way, flink-mesos needs no direct ZK dependency.

@StephanEwen
Regarding1) Curator 2.12 does not shade all of guava. This is the curation relocation definition for guava:
<relocation>
  <pattern>com.google</pattern>
  <shadedPattern>org.apache.curator.shaded.com.google</shadedPattern>
  <excludes>
    <exclude>com.google.common.base.Function</exclude>
    <exclude>com.google.common.base.Predicate</exclude>
    <exclude>com.google.common.reflect.TypeToken</exclude>
  </excludes>
</relocation>

The excluded classes are not unused, as the Function class is used by the CuratorFramework. So we still need to shade guava unfortunately.
As for 2), I'll take a look!

I've added the ZookeeperAccess class as suggested.

@zentol I like the changes!
Last two points:

Does it make sense to add only the non relocated guava classes in flink-shaded-curator? Meaning define a filter in the shading inclusion to only add com.google.common.base.Function, com.google.common.base.Predicate, and com.google.common.reflect.TypeToken?

We can probably remove the parent project flink-shaded-curator and make the flink-shaded-curator-recipes the main project.

@StephanEwen Implemented both suggestions.

Very nice, thanks!
Merging this...


multiple addresses?

This crate looks super-cool; have you given any thought to how to allow nodes to have multiple addresses? For example, in a mixed IPv4 and IPv6 stack world, some nodes may have both an IPv4 address and an IPv6 address, and some may have only one or the other. This is a big problem deploying Cassandra in mixed-stack environments (since its gossip address can only be a single socket address).

Using quickwit in a dual stack environnement in kubernetes
2024-07-14T22:58:40.521Z  WARN chitchat::server: Failed to gossip with seed node. error=failed to send chitchat message to peer

Caused by:
    Address family not supported by protocol (os error 97) node_address=[2001:cafe:42::3:9c76]:7282


vue-scoped mode causes vite to complaint about incorrect sourcemap

vite 2.9.1
unocss 0.48.4

use unocss vue-scoped mode to build the library with vite lib mode, configured as follow:
    unoCSS({
      mode: 'vue-scoped',
      presets: [unoCSSDefaultPreset()],
      transformers: [transformerDirectives()],
    }),

will cause this warning message:
Sourcemap is likely to be incorrect: a plugin (unocss:vue-scoped) was used to transform files, but didn't generate a sourcemap for the transformation. Consult the plugin documentation for help
to reproduce this:

open https://stackblitz.com/edit/daisyui-vue-vite-unocss-msucyt?file=src%2Fmain.js,vite.config.js
execute npm run build

the problem still exists :(


Fix migration conflict in insights

CommandError: Conflicting migrations detected;
multiple leaf nodes in the migration graph:
(0007_add_section_block, 0007_add_teaser_image in insights).

Thanks for this!


cloudflare_record: check record.Priority using the API, not the schema

Following on from the changes in 2.19.0 (and 2.19.1 to actually ship the
change), a regression was introduced that is inadvertantly causing a
panic due to the d.GetOkExists failing to accurately determine when to
apply the record.Priority value to the state.
d.GetOkExists is documented as:

GetOkExists can check if TypeBool attributes that are Optional with
no Default value have been set.

While the value isn't a bool, it acts similarly as 0 in this context is
both a valid value and a zero value for the field.
To combat the panic, I've swapped the check to instead compare the value
provided by the API to determine whether or not we want to set it. This
approach wasn't initially taken as the API used to return 0 in all cases
where the value wasn't explicitly set and the underlying library would
ignore it. Hopefully, with MX records allowing 0, this is no longer an
issue going forward.
Closes #988

Worked for our repository. Crashed with 2.19.1.

Thank you @Ka1wa! Just for posterity, could you post what record type and it's configuration in case down the track we dig further into the cause?

I saw the same issue with only A records and no priority set on that block.


cargo make run rust script with rust-script fails on encrypted drive because file name too long

Describe The Bug
Running a rust script trough cargo make fails on a dual boot system with Ubuntu 24.04 LTS 6.8.0-40-generic with an encrypted disk

To Reproduce

Install Ubuntu 24.04 LTS
Encrypt Linux partition following these steps: https://jumpcloud.com/blog/how-to-encrypt-ubuntu-20-04-desktop-post-installation
Install Rust, Cargo etc.
Create a new cargo project with cargo new <project-name>
Add Makefile.toml with a task with task name <task-name> as explained in the Readme: https://github.com/sagiegurari/cargo-make?tab=readme-ov-file#rust-code
Execute Cargo make <task-name>

Error Stack
[cargo-make] INFO - Execute Command: "rust-script" "/home/user01/git/rust-script-cargo-make/target/_cargo_make_temp/persisted_scripts/9E82D59A8E20E9E9C36290BD2CBF6FCCE20B02CD6D095A42E8DED57C29E89525.rs"
error: could not write output to /home/user01/.cache/rust-script/binaries/release/deps/_9e82d59a8e20e9e9c36290bd2cbf6fcce20b02cd6d095a42e8ded57c29e89525_bf38f7868792efabca30ea61-8b0e8709f49ba593._9e82d59a8e20e9e9c36290bd2cbf6fcce20b02cd6d095a42e8ded57c29e89525_bf38f7868792efabca30ea61.a89cfab540600d1e-cgu.0.rcgu.o: File name too long

error: could not compile `_9e82d59a8e20e9e9c36290bd2cbf6fcce20b02cd6d095a42e8ded57c29e89525_bf38f7868792efabca30ea61` (bin "_9e82d59a8e20e9e9c36290bd2cbf6fcce20b02cd6d095a42e8ded57c29e89525_bf38f7868792efabca30ea61") due to 1 previous error
error: Could not execute cargo
[cargo-make] ERROR - Unable to execute rust code.
[cargo-make] WARN - Build Failed.

Code Sample
// src/main.rs
fn main() {
    println!("Hello, world!");
}

# Makefile.toml
[tasks.foo]
script_runner = "@rust"
script = '''
fn main() {
    println!("running me will fail..");
}
'''

Further information
The file name it fails on,  _9e82d59a8e20e9e9c36290bd2cbf6fcce20b02cd6d095a42e8ded57c29e89525_bf38f7868792efabca30ea61-8b0e8709f49ba593._9e82d59a8e20e9e9c36290bd2cbf6fcce20b02cd6d095a42e8ded57c29e89525_bf38f7868792efabca30ea61.a89cfab540600d1e-cgu.0.rcgu.o in this example, is 228 bytes long. This can be check with:
echo "9e82d59a8e20e9e9c36290bd2cbf6fcce20b02cd6d095a42e8ded57c29e89525_bf38f7868792efabca30ea61-8b0e8709f49ba593._9e82d59a8e20e9e9c36290bd2cbf6fcce20b02cd6d095a42e8ded57c29e89525_bf38f7868792efabca30ea61.a89cfab540600d1e-cgu.0.rcgu.o" | wc -c .
This shouldn't be a problem on a non-encryped Linux system because the maximum file name length on my system (check with getconf NAME_MAX /dev/nvme0 ; getconf PATH_MAX /dev/nvme0 is: 255. But unfortunately on encrypted systems this limit is lower (143 bytes), for background information: https://askubuntu.com/questions/728465/how-can-i-increase-ubuntus-143-byte-file-name-limit-for-encrypted-directories.
I have double checked this by creating a file with touch with the same file name length with a length of 143 bytes can be created.
When running the rust script as part of the task with the cargo-script runner it fails in the same way. Running the same with cargo-play will work:
# Makefile.toml
[tasks.foo]
env = { "CARGO_MAKE_RUST_SCRIPT_PROVIDER" = "cargo-play" }
script_runner = "@rust"
script = '''
fn main() {
    println!("running me will not fail..");
}
'''

[cargo-make] INFO - Execute Command: "cargo" "play" "/home/user01/git/rust-script-cargo-make/target/_cargo_make_temp/persisted_scripts/9D1C9C25F7714024B526BD4FEE5426D4B269A2803BFF48701DAEA9FF09D710F9.rs"
   Compiling p4rn1y4sdzkjharzweabgf5fwsrb5 v0.1.0 (/tmp/cargo-play.4RN1Y4sDZkJHaRZweAbgF5FWSRb5)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.10s
     Running `/tmp/cargo-play.4RN1Y4sDZkJHaRZweAbgF5FWSRb5/target/debug/p4rn1y4sdzkjharzweabgf5fwsrb5`
running me will not fail..
[cargo-make] INFO - Build Done in 0.36 seconds.

When moving the Rust script to an actual Rust script the behavior is the same when running through cargo make:
# Makefile.toml
[tasks.foo]
script_runner = "@rust"
script = { file = "script.rs" }

// script.rs
fn main() {
    println!("running me will not fail when not running through cargo make");
}

When running the Rust script directly with rust-script  it does work:
$ rust-script script.rs
running me will not fail when not running through cargo make

But when changing the name of the script to something with a longer name, e.g. 733788858E67B5B8B2D6E2209D3C91EA16E7E8888ECA4616F707AF276465F795.rs this script fails too when running with: rust-script 733788858E67B5B8B2D6E2209D3C91EA16E7E8888ECA4616F707AF276465F795.rs
error: could not write output to /home/user01/.cache/rust-script/binaries/release/deps/_733788858e67b5b8b2d6e2209d3c91ea16e7e8888eca4616f707af276465f795_fd11e24052838ceb05481c15-7528ac1c89df1104._733788858e67b5b8b2d6e2209d3c91ea16e7e8888eca4616f707af276465f795_fd11e24052838ceb05481c15.91dd9bcbcc6a116d-cgu.0.rcgu.o: File name too long

error: could not compile `_733788858e67b5b8b2d6e2209d3c91ea16e7e8888eca4616f707af276465f795_fd11e24052838ceb05481c15` (bin "_733788858e67b5b8b2d6e2209d3c91ea16e7e8888eca4616f707af276465f795_fd11e24052838ceb05481c15") due to 1 previous error
error: Could not execute cargo

@wallem89 sorry for late reply.
cargo-make generates a file at runtime with its name as sha256 of its content.
reason is to reuse same file over and over if content didn't change as rust compilation is slow.
i can move to a different hashing algo that is less powerful but generates shorter names.

@wallem89 i pushed a possible fix in dev branch 0.37.17 mind trying it out to see if it helps? as i have no way to validate this.

Thanks @sagiegurari for looking into this issue and providing the branch with possible fix.
I am trying to test but it is still not working or I din't manage to set cargo-make to the correct branch.
error: could not write output to /home/user01/.cache/rust-script/binaries/release/deps/_32ac41162beb9267fe10a0220917e973_236cd926da3cc1f0ec423f7f-f1dfe9adb8b3f0f3._32ac41162beb9267fe10a0220917e973_236cd926da3cc1f0ec423f7f.26f36b6d57b93943-cgu.1.rcgu.o: File name too long

error: could not compile `_32ac41162beb9267fe10a0220917e973_236cd926da3cc1f0ec423f7f` (bin "_32ac41162beb9267fe10a0220917e973_236cd926da3cc1f0ec423f7f") due to 1 previous error
error: Could not execute cargo
[cargo-make] ERROR - Unable to execute rust code.
[cargo-make] WARN - Build Failed.

If I check my cargo-make version it still shows 0.37.16:
$ cargo make --version
cargo-make 0.37.16

I (tried) to install with the following command:
cargo install --git https://github.com/sagiegurari/cargo-make cargo-make --branch "0.37.17" --force

But when done it still says:
Replaced package `cargo-make v0.37.16 (https://github.com/sagiegurari/cargo-make#0e4a95dc)` with `cargo-make v0.37.16 (https://github.com/sagiegurari/cargo-make?branch=0.37.17#2e9a505b)` (executables `cargo-make`, `makers`)

thanks. dumb question, can you do touch or something and test max file len? and maybe i can do some fallback and cut filename if failing but need some sort of estimated len to understand the size of the issue

Yes I did this during my initial investigation of the source of the issue, as I wrote:
"I have double checked this by creating a file with touch with the same file name length with a length of 143 bytes can be created."
So the maximum length is 143 bytes as also stated here: https://askubuntu.com/questions/728465/how-can-i-increase-ubuntus-143-byte-file-name-limit-for-encrypted-directories

@wallem89 sorry it took so long. can you retry again using that same branch? make sure to pull it.
i'm trying original flow and if fails, i try to cut the path to limit the full path to 130 chars. not amazing but you seem to be an edge case.

released


Variable name in challenge description is misleading.

Basic JavaScript: Understanding Case Sensitivity in Variables
https://beta.freecodecamp.org/en/challenges/basic-javascript/understanding-case-sensitivity-in-variables
Issue Description
In the example code, there is a variable named "thisVariableNameIsTooLong".  If taken literally, this sounds like the variable name is unacceptable due to some character limit.  As this is not the case, I suggest changing the name to "thisVariableNameIsSoLong" to avoid confusion (but maintain the joke).

I've not made a contribution before, so I'd like to try to take this one on.  Just made a fork.


Suggested improvement to wording of description

"This package contains a single Python module that implements platform independent file locking as a means of inter-process communication"

Hello, if you make a PR for this (with tests) we would be happy to review it, thanks!


Readiness probe failed

Using a basic configuration I get a permanent readiness probe failed :
apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
  name: pg-auth
spec:
  instances: 1
  imageName: ghcr.io/cloudnative-pg/postgresql:15
  primaryUpdateStrategy: unsupervised
  bootstrap:
    initdb:
      database: keycloak
      owner: keycloak
      dataChecksums: true
      encoding: 'LATIN1'
  storage:
    size: 10Gi

pod events:

pod logs:
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","logger":"setup","msg":"Starting CloudNativePG Instance Manager","logging_pod":"pg-auth-1","version":"1.20.1","build":{"Version":"1.20.1","Commit":"9bf74c9e","Date":"2023-06-12"}}
bootstrap-controller {"level":"info","ts":"2023-07-28T12:04:00Z","msg":"Installing the manager executable","destination":"/controller/manager","version":"1.20.1","build":{"Version":"1.20.1","Commit":"9bf74c9e","Date":"2023-06-12"}}
bootstrap-controller {"level":"info","ts":"2023-07-28T12:04:00Z","msg":"Setting 0750 permissions"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","logger":"setup","msg":"starting controller-runtime manager","logging_pod":"pg-auth-1"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","msg":"Starting EventSource","controller":"cluster","controllerGroup":"postgresql.cnpg.io","controllerKind":"Cluster","source":"kind source: *v1.Cluster"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","msg":"Starting Controller","controller":"cluster","controllerGroup":"postgresql.cnpg.io","controllerKind":"Cluster"}
bootstrap-controller {"level":"info","ts":"2023-07-28T12:04:00Z","msg":"Bootstrap completed"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","msg":"Starting webserver","logging_pod":"pg-auth-1","address":":9187"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","msg":"Starting webserver","logging_pod":"pg-auth-1","address":"localhost:8010"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","logger":"roles_reconciler","msg":"starting up the runnable","logging_pod":"pg-auth-1"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","msg":"Starting webserver","logging_pod":"pg-auth-1","address":":8000"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","logger":"roles_reconciler","msg":"setting up RoleSynchronizer loop","logging_pod":"pg-auth-1"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","msg":"Starting workers","controller":"cluster","controllerGroup":"postgresql.cnpg.io","controllerKind":"Cluster","worker count":1}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","msg":"Ignore minSyncReplicas to enforce self-healing","logging_pod":"pg-auth-1","syncReplicas":-1,"minSyncReplicas":0,"maxSyncReplicas":0}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","msg":"Refreshed configuration file","controller":"cluster","controllerGroup":"postgresql.cnpg.io","controllerKind":"Cluster","Cluster":{"name":"pg-auth","namespace":"default"},"namespace":"default","name":"pg-auth","reconcileID":"5e016f11-65bc-4b77-b250-0e926fbf7d1e","uuid":"d72b04cd-2d3e-11ee-9c9e-1e5eef60200f","logging_pod":"pg-auth-1","filename":"/controller/certificates/server.crt","secret":"pg-auth-server"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","msg":"Refreshed configuration file","controller":"cluster","controllerGroup":"postgresql.cnpg.io","controllerKind":"Cluster","Cluster":{"name":"pg-auth","namespace":"default"},"namespace":"default","name":"pg-auth","reconcileID":"5e016f11-65bc-4b77-b250-0e926fbf7d1e","uuid":"d72b04cd-2d3e-11ee-9c9e-1e5eef60200f","logging_pod":"pg-auth-1","filename":"/controller/certificates/server.key","secret":"pg-auth-server"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","msg":"Refreshed configuration file","controller":"cluster","controllerGroup":"postgresql.cnpg.io","controllerKind":"Cluster","Cluster":{"name":"pg-auth","namespace":"default"},"namespace":"default","name":"pg-auth","reconcileID":"5e016f11-65bc-4b77-b250-0e926fbf7d1e","uuid":"d72b04cd-2d3e-11ee-9c9e-1e5eef60200f","logging_pod":"pg-auth-1","filename":"/controller/certificates/streaming_replica.crt","secret":"pg-auth-replication"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","msg":"Refreshed configuration file","controller":"cluster","controllerGroup":"postgresql.cnpg.io","controllerKind":"Cluster","Cluster":{"name":"pg-auth","namespace":"default"},"namespace":"default","name":"pg-auth","reconcileID":"5e016f11-65bc-4b77-b250-0e926fbf7d1e","uuid":"d72b04cd-2d3e-11ee-9c9e-1e5eef60200f","logging_pod":"pg-auth-1","filename":"/controller/certificates/streaming_replica.key","secret":"pg-auth-replication"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","msg":"Refreshed configuration file","controller":"cluster","controllerGroup":"postgresql.cnpg.io","controllerKind":"Cluster","Cluster":{"name":"pg-auth","namespace":"default"},"namespace":"default","name":"pg-auth","reconcileID":"5e016f11-65bc-4b77-b250-0e926fbf7d1e","uuid":"d72b04cd-2d3e-11ee-9c9e-1e5eef60200f","logging_pod":"pg-auth-1","filename":"/controller/certificates/client-ca.crt","secret":"pg-auth-ca"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","msg":"Refreshed configuration file","controller":"cluster","controllerGroup":"postgresql.cnpg.io","controllerKind":"Cluster","Cluster":{"name":"pg-auth","namespace":"default"},"namespace":"default","name":"pg-auth","reconcileID":"5e016f11-65bc-4b77-b250-0e926fbf7d1e","uuid":"d72b04cd-2d3e-11ee-9c9e-1e5eef60200f","logging_pod":"pg-auth-1","filename":"/controller/certificates/server-ca.crt","secret":"pg-auth-ca"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","msg":"Installed configuration file","logging_pod":"pg-auth-1","pgdata":"/var/lib/postgresql/data/pgdata","filename":"pg_hba.conf"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","msg":"Ignore minSyncReplicas to enforce self-healing","logging_pod":"pg-auth-1","syncReplicas":-1,"minSyncReplicas":0,"maxSyncReplicas":0}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","msg":"Installed configuration file","logging_pod":"pg-auth-1","pgdata":"/var/lib/postgresql/data/pgdata","filename":"custom.conf"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","msg":"Cluster status","controller":"cluster","controllerGroup":"postgresql.cnpg.io","controllerKind":"Cluster","Cluster":{"name":"pg-auth","namespace":"default"},"namespace":"default","name":"pg-auth","reconcileID":"5e016f11-65bc-4b77-b250-0e926fbf7d1e","uuid":"d72b04cd-2d3e-11ee-9c9e-1e5eef60200f","logging_pod":"pg-auth-1","currentPrimary":"","targetPrimary":"pg-auth-1"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","msg":"First primary instance bootstrap, marking myself as primary","controller":"cluster","controllerGroup":"postgresql.cnpg.io","controllerKind":"Cluster","Cluster":{"name":"pg-auth","namespace":"default"},"namespace":"default","name":"pg-auth","reconcileID":"5e016f11-65bc-4b77-b250-0e926fbf7d1e","uuid":"d72b04cd-2d3e-11ee-9c9e-1e5eef60200f","logging_pod":"pg-auth-1","currentPrimary":"","targetPrimary":"pg-auth-1"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","msg":"Extracting pg_controldata information","logging_pod":"pg-auth-1","reason":"postmaster start up"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","logger":"pg_controldata","msg":"pg_control version number:            1300\nCatalog version number:               202209061\nDatabase system identifier:<PHONE_NUMBER>167217186\nDatabase cluster state:               shut down\npg_control last modified:             Fri 28 Jul 2023 12:03:56 PM UTC\nLatest checkpoint location:           0/2000028\nLatest checkpoint's REDO location:    0/2000028\nLatest checkpoint's REDO WAL file:<PHONE_NUMBER>00000000000002\nLatest checkpoint's TimeLineID:       1\nLatest checkpoint's PrevTimeLineID:   1\nLatest checkpoint's full_page_writes: on\nLatest checkpoint's NextXID:          0:726\nLatest checkpoint's NextOID:          16386\nLatest checkpoint's NextMultiXactId:  1\nLatest checkpoint's NextMultiOffset:  0\nLatest checkpoint's oldestXID:        716\nLatest checkpoint's oldestXID's DB:   1\nLatest checkpoint's oldestActiveXID:  0\nLatest checkpoint's oldestMultiXid:   1\nLatest checkpoint's oldestMulti's DB: 1\nLatest checkpoint's oldestCommitTsXid:0\nLatest checkpoint's newestCommitTsXid:0\nTime of latest checkpoint:            Fri 28 Jul 2023 12:03:56 PM UTC\nFake LSN counter for unlogged rels:   0/3E8\nMinimum recovery ending location:     0/0\nMin recovery ending loc's timeline:   0\nBackup start location:                0/0\nBackup end location:                  0/0\nEnd-of-backup record required:        no\nwal_level setting:                    replica\nwal_log_hints setting:                off\nmax_connections setting:              100\nmax_worker_processes setting:         32\nmax_wal_senders setting:              10\nmax_prepared_xacts setting:           0\nmax_locks_per_xact setting:           64\ntrack_commit_timestamp setting:       off\nMaximum data alignment:               8\nDatabase block size:                  8192\nBlocks per segment of large relation: 131072\nWAL block size:                       8192\nBytes per WAL segment:                16777216\nMaximum length of identifiers:        64\nMaximum columns in an index:          32\nMaximum size of a TOAST chunk:        1996\nSize of a large-object chunk:         2048\nDate/time type storage:               64-bit integers\nFloat8 argument passing:              by value\nData page checksum version:           1\nMock authentication nonce:            f4c59bd831fb5fc507caf31dcd08e4c52960e77bcc6c00fb4377ef2f147c21e0\n","pipe":"stdout","logging_pod":"pg-auth-1"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","msg":"The PID file content is wrong, deleting it and assuming it's stale","file":"/var/lib/postgresql/data/pgdata/postmaster.pid","logging_pod":"pg-auth-1","err":"file does not exist","pidFileContents":""}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","msg":"DB not available, will retry","logging_pod":"pg-auth-1","err":"failed to connect to `host=/controller/run user=postgres database=postgres`: dial error (dial unix /controller/run/.s.PGSQL.5432: connect: no such file or directory)"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","msg":"Instance is still down, will retry in 1 second","controller":"cluster","controllerGroup":"postgresql.cnpg.io","controllerKind":"Cluster","Cluster":{"name":"pg-auth","namespace":"default"},"namespace":"default","name":"pg-auth","reconcileID":"5e016f11-65bc-4b77-b250-0e926fbf7d1e","uuid":"d72b04cd-2d3e-11ee-9c9e-1e5eef60200f","logging_pod":"pg-auth-1"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","msg":"Ignore minSyncReplicas to enforce self-healing","logging_pod":"pg-auth-1","syncReplicas":-1,"minSyncReplicas":0,"maxSyncReplicas":0}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","msg":"Ignore minSyncReplicas to enforce self-healing","logging_pod":"pg-auth-1","syncReplicas":-1,"minSyncReplicas":0,"maxSyncReplicas":0}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","logger":"postgres","msg":"2023-07-28 12:04:01.714 UTC [36] LOG:  redirecting log output to logging collector process","pipe":"stderr","logging_pod":"pg-auth-1"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","logger":"postgres","msg":"2023-07-28 12:04:01.714 UTC [36] HINT:  Future log output will appear in directory \"/controller/log\".","pipe":"stderr","logging_pod":"pg-auth-1"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","logger":"postgres","msg":"2023-07-28 12:04:01.714 UTC [36] LOG:  ending log output to stderr","source":"/controller/log/postgres","logging_pod":"pg-auth-1"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","logger":"postgres","msg":"2023-07-28 12:04:01.714 UTC [36] HINT:  Future log output will go to log destination \"csvlog\".","source":"/controller/log/postgres","logging_pod":"pg-auth-1"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","logger":"postgres","msg":"record","logging_pod":"pg-auth-1","record":{"log_time":"2023-07-28 12:04:01.714 UTC","process_id":"36","session_id":"64c3aeb1.24","session_line_num":"1","session_start_time":"2023-07-28 12:04:01 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"ending log output to stderr","hint":"Future log output will go to log destination \"csvlog\".","backend_type":"postmaster","query_id":"0"}}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","logger":"postgres","msg":"record","logging_pod":"pg-auth-1","record":{"log_time":"2023-07-28 12:04:01.714 UTC","process_id":"36","session_id":"64c3aeb1.24","session_line_num":"2","session_start_time":"2023-07-28 12:04:01 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"starting PostgreSQL 15.3 (Debian 15.3-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit","backend_type":"postmaster","query_id":"0"}}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","logger":"postgres","msg":"record","logging_pod":"pg-auth-1","record":{"log_time":"2023-07-28 12:04:01.714 UTC","process_id":"36","session_id":"64c3aeb1.24","session_line_num":"3","session_start_time":"2023-07-28 12:04:01 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"listening on IPv4 address \"<IP_ADDRESS>\", port 5432","backend_type":"postmaster","query_id":"0"}}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","logger":"postgres","msg":"record","logging_pod":"pg-auth-1","record":{"log_time":"2023-07-28 12:04:01.714 UTC","process_id":"36","session_id":"64c3aeb1.24","session_line_num":"4","session_start_time":"2023-07-28 12:04:01 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"listening on IPv6 address \"::\", port 5432","backend_type":"postmaster","query_id":"0"}}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","logger":"postgres","msg":"record","logging_pod":"pg-auth-1","record":{"log_time":"2023-07-28 12:04:01.724 UTC","process_id":"36","session_id":"64c3aeb1.24","session_line_num":"5","session_start_time":"2023-07-28 12:04:01 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"listening on Unix socket \"/controller/run/.s.PGSQL.5432\"","backend_type":"postmaster","query_id":"0"}}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","logger":"postgres","msg":"record","logging_pod":"pg-auth-1","record":{"log_time":"2023-07-28 12:04:01.735 UTC","process_id":"41","session_id":"64c3aeb1.29","session_line_num":"1","session_start_time":"2023-07-28 12:04:01 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"database system was shut down at 2023-07-28 12:03:56 UTC","backend_type":"startup","query_id":"0"}}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","logger":"postgres","msg":"record","logging_pod":"pg-auth-1","record":{"log_time":"2023-07-28 12:04:01.735 UTC","user_name":"postgres","database_name":"postgres","process_id":"42","connection_from":"[local]","session_id":"64c3aeb1.2a","session_line_num":"1","session_start_time":"2023-07-28 12:04:01 UTC","transaction_id":"0","error_severity":"FATAL","sql_state_code":"57P03","message":"the database system is starting up","backend_type":"client backend","query_id":"0"}}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","msg":"DB not available, will retry","controller":"cluster","controllerGroup":"postgresql.cnpg.io","controllerKind":"Cluster","Cluster":{"name":"pg-auth","namespace":"default"},"namespace":"default","name":"pg-auth","reconcileID":"2c17ac6d-c354-402b-8ba6-99aaa2254a0c","uuid":"d738272a-2d3e-11ee-9c9e-1e5eef60200f","logging_pod":"pg-auth-1","err":"failed to connect to `host=/controller/run user=postgres database=postgres`: server error (FATAL: the database system is starting up (SQLSTATE 57P03))"}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","logger":"postgres","msg":"record","logging_pod":"pg-auth-1","record":{"log_time":"2023-07-28 12:04:01.737 UTC","user_name":"postgres","database_name":"postgres","process_id":"43","connection_from":"[local]","session_id":"64c3aeb1.2b","session_line_num":"1","session_start_time":"2023-07-28 12:04:01 UTC","transaction_id":"0","error_severity":"FATAL","sql_state_code":"57P03","message":"the database system is starting up","backend_type":"client backend","query_id":"0"}}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","logger":"postgres","msg":"record","logging_pod":"pg-auth-1","record":{"log_time":"2023-07-28 12:04:01.751 UTC","process_id":"36","session_id":"64c3aeb1.24","session_line_num":"6","session_start_time":"2023-07-28 12:04:01 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"database system is ready to accept connections","backend_type":"postmaster","query_id":"0"}}
postgres {"level":"info","ts":"2023-07-28T12:04:01Z","logger":"wal-archive","msg":"Backup not configured, skip WAL archiving","logging_pod":"pg-auth-1","walName":"pg_wal/000000010000000000000001","currentPrimary":"pg-auth-1","targetPrimary":"pg-auth-1"}
postgres {"level":"info","ts":"2023-07-28T12:04:02Z","msg":"Readiness probe failing","logging_pod":"pg-auth-1","err":"instance is not ready yet"}
postgres {"level":"info","ts":"2023-07-28T12:04:02Z","msg":"Ignore minSyncReplicas to enforce self-healing","logging_pod":"pg-auth-1","syncReplicas":-1,"minSyncReplicas":0,"maxSyncReplicas":0}
postgres {"level":"info","ts":"2023-07-28T12:04:02Z","msg":"Ignore minSyncReplicas to enforce self-healing","logging_pod":"pg-auth-1","syncReplicas":-1,"minSyncReplicas":0,"maxSyncReplicas":0}
postgres {"level":"info","ts":"2023-07-28T12:04:02Z","msg":"Ignore minSyncReplicas to enforce self-healing","logging_pod":"pg-auth-1","syncReplicas":-1,"minSyncReplicas":0,"maxSyncReplicas":0}
postgres {"level":"info","ts":"2023-07-28T12:04:02Z","msg":"Ignore minSyncReplicas to enforce self-healing","logging_pod":"pg-auth-1","syncReplicas":-1,"minSyncReplicas":0,"maxSyncReplicas":0}
postgres {"level":"info","ts":"2023-07-28T12:04:02Z","msg":"Ignore minSyncReplicas to enforce self-healing","logging_pod":"pg-auth-1","syncReplicas":-1,"minSyncReplicas":0,"maxSyncReplicas":0}
postgres {"level":"info","ts":"2023-07-28T12:04:02Z","msg":"Ignore minSyncReplicas to enforce self-healing","logging_pod":"pg-auth-1","syncReplicas":-1,"minSyncReplicas":0,"maxSyncReplicas":0}
postgres {"level":"info","ts":"2023-07-28T12:04:03Z","msg":"Readiness probe failing","logging_pod":"pg-auth-1","err":"instance is not ready yet"}
postgres {"level":"info","ts":"2023-07-28T12:04:04Z","msg":"Readiness probe failing","logging_pod":"pg-auth-1","err":"instance is not ready yet"}

@tamis-laan were you able to figure this out? what was the issue?


Sockets suddenly stopped pushing messages

What could be a possible reason for my sockets remain silent... No any messages at all even after restart of the script.
Less than 24 hours ago my sockets suddenly remain silent... No errors... Binance team said no such complains from other users...
$ ./streams-test.py
client.ping() {}
client.get_server_time() {'serverTime':<PHONE_NUMBER>677}
client.get_system_status() {'status': 0, 'msg': 'normal'}
CANCEL read_loop
made the script running for 30 seconds and I barely get 1 msg from the stream or sometimes no messages at all for the 30 sec period
It's the BTCUSDT price socket... Should be quite noisy...

What could be a possible reason for my sockets remain silent... No any messages at all even after restart of the script.
Less than 24 hours ago my sockets suddenly remain silent... No errors... Binance team said no such complains from other users...
$ ./streams-test.py
client.ping() {}
client.get_server_time() {'serverTime':<PHONE_NUMBER>677}
client.get_system_status() {'status': 0, 'msg': 'normal'}
CANCEL read_loop
made the script running for 30 seconds and I barely get 1 msg from the stream or sometimes no messages at all for the 30 sec period
It's the BTCUSDT price socket... Should be quite noisy...

It turned out I'm blocking them with my firewall... 🤣


User authentication

Changed the userId to be sent from trusted services

@cloudbeatsch
The problem with the solution as it is now, is that anyone who has anyone else's user Id, can send request on his behalf, since you extract the user id in the office part, and call ibera-services api with the id in the query string.
I guess that what we want to do is to add a few authentication schemes to the ibera-services api (office365, google, etc..), and send the user's token in the headers to the services api. only there we should extract the user Id internally before processing the request. The way you implemented it now is not secure, unless you we use client-server certificates, but then you have other issues that you'll have to install the client certificate in each client and I don't think this is what you intended...
Let me know what you think...

@amiturgman agree on the possible attack surface for userId injection. I was thinking about adding a token for the service but decided against it to keep it simple. The constraint is that only trusted services have access to the ibera-services - this must be enforced through the VPNs network security rules. As is, only the api part (server side node part) of the office  addIn can access ibera-services. The client part of the office-integration doesn't send the userId but the whole user-token as a header to the document-service. For the Android client, the idea would be to use a token between the client and the gatway, where the gateway is a trusted caller.

@cloudbeatsch so there's a missing part which is the android gateway that we didn't think/talk about... cause I thought that the android device was supposed to talk directly to the services api... (and so any other client).
This means we need to add a backend service to the android client that will be deployed as part of the solution in the App Service Environment. And will be able to communicate with the services api internally. We should also remove the public facing endpoint from the services API.
I don't know... it sounds too complicated...
Usually in such cases, the main api that everyone talks to (the services api in our case) supports a few authentication schemes, and based on the token in the header, use the correct one to resolve the user's identity. This can be done with the passport node module (you can see an example of how I did it with google auth here).
We can decide to leave it as is, for the sake of simplicity and saying that this is a POC. But as an E2E solution, the authentication must be addressed... I don't mind also leaving it as you suggested, it just that it makes things much more complicated technically-wize.

If you prefer to connect from the Android directly to the service, we should definitely move towards token based authentication  - let's add this as an issue and address once we move off the POC, ok?

@cloudbeatsch sure, thanks.


Passing thru colliders, Straffing and automatic movement on grabbing an object and holding it close to your body and trying to move forward

While holding an object close to your body I can pass thru other solid objects. If I move this object I am holding so that it is an arms length away from my body, then I wont pass thru solid objects, so I guess there is a bug in VRTK 4 that is causing this kind  of behavior.
Also if a solid object has just one collider on it you can still pass thru it, so not sure why that is happening. I even increased the source thickness to 0.75.
Also another weird thing I noticed when you place the  SolvedBodyCollisions() on the 'Diverged' Body event of Pseudobody is that as soon as you grab and object keeping the grabbed button pressed, you automatically start being pushed around in the world.
On the other hand if you do not use the Diverged event on Pseudobody and instead go with using the  PositionChange() within the Movement Events for the various Locomotors.AxisMove abilities, then as soon as the object your holding touches your pseudo body, you start getting the weird straffing towards the left or Right movement when you try to move forward.
I don't know if this happening because I am using Unity 2019.4.15f1 and Oculus Integration 20.1 as probably all this may be working with older versions of Unity and Oculus Integration, but ideally I believe it should work with any new version.
I am using VRTK's CameraRigs.OculusIntegration.
Thanks,
Chris

You need to provide steps to reproduce and follow the template for raising a bug otherwise the ticket is closed until the template style is followed


Long hibernation stress test

Added a new hibernate stress test.
Set the default iteration to 500 (Almost 10 days stress test)
Test Results
Coming soon.

@LiliDeng @lubaihua33 @abhimarathe  please review this PR. PR testing is running but deleted accidentally once, and stopped the longer resume time. It will take around 10 day run-time. I'd like to have your review in advance before I have result come out.

@juhlee-microsoft You can run less times like 5 times to check the code logic firstly.

@juhlee-microsoft You can run less times like 5 times to check the code logic firstly.

It's been 1 day and 9 hours

@juhlee-microsoft You can run less times like 5 times to check the code logic firstly.

It's been 1 day and 9 hours

@dcui and I agree to change the default cycle to 50.


signup login loader

resolved #106

Sign up is not working after loader is added, try to debug the error


Remove generated Android code

Removed generated code, add comment to the developer readme that this needs to be manually generated
I fixed the .ejs files I messed up.
LightTest.java is actually generated, but this was one of the tests that @fynngodau fixed. So I edited light.junit.ejs to reflect this change (see line 91).

Another step towards #1166

In Android Studio, I have it setup so that I can run the example app, and it works with this make style-code, but how do I execute the junit test suites?

I think we would benefit greatly from having this make style-code step as a part of the gradle build process. The following snippet in build.gradle seems like a good start, but it is not functional yet and does not compile:
task generateStyleCode {
    doLast {
        commandLine 'sh', '-c', 'make style-code'
    }
}

preBuild.dependsOn generateStyleCode

I think we would benefit greatly from having this make style-code step as a part of the gradle build process. The following snippet in build.gradle seems like a good start, but it is not functional yet and does not compile:
task generateStyleCode {
    doLast {
        commandLine 'sh', '-c', 'make style-code'
    }
}

preBuild.dependsOn generateStyleCode

The Makefile is a wrapper around Gradle... We should not let Gradle also use the Makefile. That just does not feel very clean to me.
Ideally the build system should be smart enough to pull in all needed dependencies and also to keep track of when dependencies are changed so that it can re run the code generation (and only then). I could look into https://github.com/node-gradle/gradle-node-plugin


add a function that shows what type of asset a given component has

Example
yo kickstart:has accordion // returns: js, scss, html

won't fix ... use ls components/app/ | grep foo


[heatmap] account for bounds = 0

Coverage remained the same at 69.142% when pulling 8aef9fd96a146398accf203b0be75cd16e8943f8 on mistercrunch:heatmap_bounds into e22aecb0d1244bae49d3e5b36ef2f9ddc7517c1a on apache:master.

Coverage remained the same at 69.442% when pulling a59a0c83427985d336c2ecf64e5ce37142afbb7a on mistercrunch:heatmap_bounds into c3c9ceb1cc3fc70670257f8f652f083cde2ea14d on apache:master.

Coverage remained the same at 69.442% when pulling a54e81e373ac713142673c1ca320caff17128573 on mistercrunch:heatmap_bounds into c3c9ceb1cc3fc70670257f8f652f083cde2ea14d on apache:master.

treating as a hotfix & mergin'


Use {spawn,Test} to isolate tests from each other

Both the ?WITH_SETUP(...) and ?WITH_FUN(...) macros now
use the {spawn,Test} feature of eunit to isolate tests
from each other, for example tests that links to or monitors
other processes, or tests that clutter the process dictionary.

Thanks, having that behavior was my intention in the first place.  Thanks for spotting this.  Merged.


Cross linking + relevant blog post

Learn Build status updates of commit db1dbe1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/best-practices/background-jobs.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@EdPrice-MSFT
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#Sign-Off


Unregister rule's metrics

Notes:

removed duplicated dependency in pom.xml
tried again to use tmpfs in MySQL container, using .withTmpFs(Map.of("/var/lib/mysql", "rw")) :crossed_fingers:

Thanks @pruivo. Good find with withTmpFs, we should use that in the cache-manager testsuite as well :+1:


Karel/qlknn compat

Adds a few features for running in gitlab CI, used here: https://gitlab.com/qualikiz-group/QLKNN-fortran/pipelines/82676323

Optionally specify a run command with -c
Exit on error of build, and error of running the generated testfile
Exit on single failing FRUIT test

Commit message
9ed3aec Fail fruit.sh on any error
Should've been 'pass run command to fruitsh using -c'


Josh[Fix][LoginBackend]

Fixed issues with the login component and added design to the not-found page.

Thanks!


Create a bot account for adding variants to Wikidata

Similar to the Pathway work and it Pathway bot, a designated bot account is needed to add the different genetic variants. Especially, since we will be adding multiple variant resources.

In progress: https://www.wikidata.org/wiki/User:Variantbot
TODO: adapt the CIViC bot to the latest updates
TODO: Do a test run on 50 items
TODO: Request bot permission


remove dashboard event handlers from main agent files

Type of Issue
Select the type of issue:

[ ] Bug report (to report a bug)
[ ] Feature request (to request an additional feature)
[ ] Tracker (I am just using this as a tracker)
[x] Refactor request
[ ] Documentation Ask

Thanks for creating this @anuragprat1k , was just about to create one :)