ERT Restore fails using Postgres DB

CFOPS ERT restore is failing when the backend is postgres. We did a manual restore using the cfops backup data and it worked. Issue appears to be with the cfops restore. We believe it is the lack of the "--clean" option in the pg_restore command. The cfops restore resulted in the cc being unable to start. 1st instance of CC showed starting, 2nd instance of CC showed stopped, and CC worker showed failing.
We later tried a manual restore and it worked. Below are the working steps that we used:
ERT Restore log:
ert.log.gz
error:
2016/04/27 10:50:21 E0427 10:50:21.097533 6309 execute_list.go:15] Process exited with: 1. Reason was:  ()
2016/04/27 10:50:19 D0427 10:50:19.678913 6309 execute_list.go:12] PGPASSWORD=270a0e10f2739c8f /var/vcap/packages/postgres-9.4.2/bin/pg_restore -h localhost -U vcap -x -p 2544 -c -d uaa /tmp/archive.backup
Note: No "--clean" option
Working manual steps:
bosh stop cloud_controller-partition-d46fdf5eca88a5c00fc7 0
bosh stop cloud_controller-partition-d46fdf5eca88a5c00fc7 1
ccdb
<EMAIL_ADDRESS>  030df4fe78359255
./pg_restore -U vcap -p 2544 -d ccdb --clean /tmp/ccdb.sql
bosh stop uaa-partition-d46fdf5eca88a5c00fc7 0
bosh stop uaa-partition-d46fdf5eca88a5c00fc7 1
uaadb
<EMAIL_ADDRESS>                       270a0e10f2739c8f
./pg_restore -U vcap -p 2544 -d uaa --clean /tmp/uaadb.backup
./pg_restore -U vcap -p 2544 -v -d console --clean /tmp/consoledb.backup
Note: Includes "--clean" option
NFS Remote restore:
cat nfs_server.backup | ssh vcap@host "tar xvzf - -C /var/vcap/store"
mysql/0  <IP_ADDRESS>
mysql -h localhost -u root -p < /tmp/mysql.backup
mysql -u root -p -h localhost

flush flush privileges;

bosh start uaa-partition-d46fdf5eca88a5c00fc7 0
bosh start uaa-partition-d46fdf5eca88a5c00fc7 1
bosh start cloud_controller-partition-d46fdf5eca88a5c00fc7 0
bosh start cloud_controller-partition-d46fdf5eca88a5c00fc7 1

I built out a lab with postgres, and ran the backup restore. I did not have any pg_restore errors in the log, but seeing the cloud controller fail to start.
+----------------------------------------------------------------+----------+--------------------------------------------------------------+--------------+
| Job/index                                                      | State    | Resource Pool                                                | IPs          |
+----------------------------------------------------------------+----------+--------------------------------------------------------------+--------------+
| ccdb-partition-3f2d3e1323bb74aa36a1/0                          | running  | ccdb-partition-3f2d3e1323bb74aa36a1                          | <IP_ADDRESS> |
| clock_global-partition-3f2d3e1323bb74aa36a1/0                  | running  | clock_global-partition-3f2d3e1323bb74aa36a1                  | <IP_ADDRESS> |
| cloud_controller-partition-3f2d3e1323bb74aa36a1/0              | starting | cloud_controller-partition-3f2d3e1323bb74aa36a1              | <IP_ADDRESS> |
| cloud_controller_worker-partition-3f2d3e1323bb74aa36a1/0       | failing  | cloud_controller_worker-partition-3f2d3e1323bb74aa36a1       | <IP_ADDRESS> |
| consoledb-partition-3f2d3e1323bb74aa36a1/0                     | running  | consoledb-partition-3f2d3e1323bb74aa36a1                     | <IP_ADDRESS> |
| consul_server-partition-3f2d3e1323bb74aa36a1/0                 | running  | consul_server-partition-3f2d3e1323bb74aa36a1                 | <IP_ADDRESS> |
| diego_brain-partition-3f2d3e1323bb74aa36a1/0                   | running  | diego_brain-partition-3f2d3e1323bb74aa36a1                   | <IP_ADDRESS> |
| diego_cell-partition-3f2d3e1323bb74aa36a1/0                    | running  | diego_cell-partition-3f2d3e1323bb74aa36a1                    | <IP_ADDRESS> |
| diego_cell-partition-3f2d3e1323bb74aa36a1/1                    | running  | diego_cell-partition-3f2d3e1323bb74aa36a1                    | <IP_ADDRESS> |
| diego_database-partition-3f2d3e1323bb74aa36a1/0                | running  | diego_database-partition-3f2d3e1323bb74aa36a1                | <IP_ADDRESS> |
| doppler-partition-3f2d3e1323bb74aa36a1/0                       | running  | doppler-partition-3f2d3e1323bb74aa36a1                       | <IP_ADDRESS> |
| etcd_server-partition-3f2d3e1323bb74aa36a1/0                   | running  | etcd_server-partition-3f2d3e1323bb74aa36a1                   | <IP_ADDRESS> |
| ha_proxy-partition-3f2d3e1323bb74aa36a1/0                      | running  | ha_proxy-partition-3f2d3e1323bb74aa36a1                      | <IP_ADDRESS> |
| loggregator_trafficcontroller-partition-3f2d3e1323bb74aa36a1/0 | running  | loggregator_trafficcontroller-partition-3f2d3e1323bb74aa36a1 | <IP_ADDRESS> |
| mysql-partition-3f2d3e1323bb74aa36a1/0                         | running  | mysql-partition-3f2d3e1323bb74aa36a1                         | <IP_ADDRESS> |
| mysql_proxy-partition-3f2d3e1323bb74aa36a1/0                   | running  | mysql_proxy-partition-3f2d3e1323bb74aa36a1                   | <IP_ADDRESS> |
| nats-partition-3f2d3e1323bb74aa36a1/0                          | running  | nats-partition-3f2d3e1323bb74aa36a1                          | <IP_ADDRESS> |
| nfs_server-partition-3f2d3e1323bb74aa36a1/0                    | running  | nfs_server-partition-3f2d3e1323bb74aa36a1                    | <IP_ADDRESS> |
| router-partition-3f2d3e1323bb74aa36a1/0                        | running  | router-partition-3f2d3e1323bb74aa36a1                        | <IP_ADDRESS> |
| uaa-partition-3f2d3e1323bb74aa36a1/0                           | running  | uaa-partition-3f2d3e1323bb74aa36a1                           | <IP_ADDRESS> |
| uaadb-partition-3f2d3e1323bb74aa36a1/0                         | running  | uaadb-partition-3f2d3e1323bb74aa36a1                         | <IP_ADDRESS> |
+----------------------------------------------------------------+----------+--------------------------------------------------------------+--------------+
cloud_controller-partition-3f2d3e1323bb74aa36a1-0-3430133b0907.zip
cloud_controller_worker-partition-3f2d3e1323bb74aa36a1-0-589f5057db19.zip

Saw this in logs:
cloud_controller_worker_ctl.err.log:[2016-05-13 15:31:40+0000] Sequel::DatabaseError: PG::UndefinedTable: ERROR:  relation delayed_jobs does not exist
cloud_controller_worker_ctl.err.log:[2016-05-13 15:31:40+0000] PG::UndefinedTable: ERROR:  relation delayed_jobs does not exist
cloud_controller_worker_ctl.err.log:[2016-05-13 15:31:40+0000] Delayed::FatalBackendError: Delayed::FatalBackendError
cloud_controller_worker_ctl.err.log:[2016-05-13 15:31:40+0000] Sequel::DatabaseError: PG::UndefinedTable: ERROR:  relation delayed_jobs does not exist
cloud_controller_worker_ctl.err.log:[2016-05-13 15:31:40+0000] PG::UndefinedTable: ERROR:  relation delayed_jobs does not exist

Wondering if we can try pg_restore without the -x option in cfops? Is the only difference between manual working method and cfops.

Not sure what all is included in typical pg_dump but looks like -x is there to prevent restoring roles.  Which seems like it should be there if restoring from scratch... Let me know if you have a place to test this and can add a draft release without this option.

I have my lab until Monday, so can test over the weekend. If that doesn't work I can ask for a 1 day extension.


Add property "ConfigurationSource" to Get-DnsClientServerAddress

Summary of the new feature / enhancement
There currently isn't a commandlet which exposes the configuration source of DNSClientServerAddresses. This makes it cumbersome to test or swap configuration sources.
Proposed technical implementation details (optional)
Please consider adding a property "ConfigurationSource" to Get-DnsClientServerAddress. This property should clearly indicate the ConfigurationSource of the DnsClientServerAddress ie. Static, DHCP, Auto, whatever.

I don't think this is part of this project. The DnsClient module looks like part of original the PowerShell Desktop
C:\Windows\System32\WindowsPowerShell\v1.0\Modules\DnsClient>dir
 Volume in drive C is Local Disk
 Volume Serial Number is ACF6-E72D

 Directory of C:\Windows\System32\WindowsPowerShell\v1.0\Modules\DnsClient

07/05/2022  09:00    <DIR>          .
08/11/2023  16:02    <DIR>          ..
07/05/2022  08:56             1,964 DnsClient.psd1
07/05/2022  08:56            17,850 DnsClientPSProvider.Format.ps1xml
07/05/2022  08:56             4,788 DnsClientPSProvider.Types.ps1xml
07/05/2022  08:56            61,640 DnsCmdlets.Format.ps1xml
07/05/2022  08:56            22,151 DnsCmdlets.Types.ps1xml
07/05/2022  08:56            23,188 DnsConfig.Format.ps1xml
07/05/2022  08:56             1,100 DnsConfig.Types.ps1xml
07/05/2022  08:56            38,912 dnslookup.dll
07/05/2022  08:56             4,504 MSFT_DnsClient.cdxml
07/05/2022  08:56             4,130 MSFT_DnsClientCache.cdxml
07/05/2022  08:56             3,854 MSFT_DnsClientDohServerAddress.cdxml
07/05/2022  08:56             1,306 MSFT_DnsClientGlobalSetting.cdxml
07/05/2022  08:56             3,613 MSFT_DnsClientServerAddress.cdxml
07/05/2022  08:56             5,188 PS_DnsClientNRPTGlobal_v1.0.0.cdxml
07/05/2022  08:56             1,704 PS_DnsClientNrptPolicy_v1.0.0.cdxml
07/05/2022  08:56            18,650 PS_DnsClientNRPTRule_v1.0.0.cdxml
              16 File(s)        214,542 bytes

Sorry, that's a bit over my head. I do know that Get-DnsClientServerAddress is an operable commandlet in my terminal running PS 7.4.5

Sorry, that's a bit over my head. I do know that Get-DnsClientServerAddress is an operable commandlet in my terminal running PS 7.4.5

Yes, if you look at the module path when running 7.4.5
$env:PSModulePath

You should see that the directory C:\Windows\System32\WindowsPowerShell\v1.0\Modules is included. So PowerShell 7 will run the commands provided by PowerShell Desktop.

Get-DnsClientServerAddress | gm  show that the command returns CIM objects, which don't includedthe source (as far as I can see) , if I missed something and one of the properties does indicate the source it's easy to change the formatting to show it.
I thought there might be a route via Get-NetIPConfiguration  but that seems to just return the objects via CIM.
As @rhubarb-geek-nz  notes, these tools are provided by Windows not as part of the PowerShell 7 language, so a request to change the functions (or what CIM/WMI return for these classes) needs to go there.

As this is part of the modules shipped in Windows this would need to be raised in the Feedback Hub in Windows so am closing this as Resolution-External as unfortunately we can't resolve this like you are asking.

FYI Co-pliot thinks that you should be able to check for DHCP via
$dnsServers = Get-DnsClientServerAddress -InterfaceAlias "YourNetworkInterface"
$dnsServers | ForEach-Object {
    if ($_.AddressOrigin -eq "Dhcp") {
        Write-Output "The DNS server is obtained via DHCP."
    } else {
        Write-Output "The DNS server is statically assigned."
    }
}

You should be able to get DHCP/Static using this or similar code
Get-NetIPInterface -AddressFamily IPv4  | ForEach-Object {
    Write-Output $_.InterfaceAlias
if ($_.Dhcp -eq "Enabled") {
        Write-Output "The DNS server is obtained via DHCP."
    } else {
        Write-Output "The DNS server is statically assigned."
    }
}

Thanks @kilasuit. An IP interface can have DNS configured statically while IP/NM/GW are DHCP. The method you propose does not account for this split configuration. Split configuration is the very reason the feature I suggested is needed.


Require separate entry of first and last name to facilitate data entry?

in order to upload contact information of adopters into our email program the first and last name need to be separated. i can do this manually but i thought it might be good to set it up that way when users sign up. thoughts?

Seems reasonable to me -- we'd have to deal with splitting existing users' names.

great, i'm hoping we can implement this! and by "we" i mean you guys :)

Submitted #167 which will:

Update the forms to have separate inputs for first and last name.
Split existing users names into first and last on the first space (everything up to the first space will be the first name, the remainder will be the last name)
I didn't make last name required because many of the existing users just put the first name in the existing field, please let me know if you'd like me to make it required and, if so, what value to use for existing users' names

Thanks, Jesse! I agree last name should not be required.

Pushed up these changes, let me know what you think!

looks great, thank you!! i'm gonna close this. yippee!


Improve TRS querying implementation

Is your feature request related to a problem? Please describe.
When using query parameters on the TRS list tools endpoint, the filters are implemented Java-side. This can be relatively slow, especially if the final result set has few records.
Galaxy is querying TRS using the description parameter, and there is a noticeable delay as it searches.
Describe the solution you'd like
As much as possible, have Postgres do the filtering. For some of the filter params, it may not be possible, but it should be possible for some.
Probably need to use CriteriaBuilder.
┆Issue is synchronized with this Jira Story
┆Fix Versions: Dockstore 1.9.X
┆Issue Number: DOCK-1598
┆Sprint: Backlog
┆Issue Type: Story

This is obvious and my code may be too specific to the way that branch is, but I I did filter workflows using a CriteriaQuery here


Integrate LM Format Enforcer

It would be really powerful to be able to integrate LM Formate Enforcer with Ollama. It already supports llama.cpp as well.

what's the stance on this? lm format enforcer claims it beats the Outlines lib, so that's a big deal

Closing this out for now with our structured outputs PR - already digging into some constrained decoding work - will check this out and keep in mind! Thank you!

Closing this out for now with our structured outputs PR - already digging into some constrained decoding work - will check this out and keep in mind! Thank you!

Is that this PR?

Closing this out for now with our structured outputs PR - already digging into some constrained decoding work - will check this out and keep in mind! Thank you!

Is that this PR?

Oops forgot to tag it #7900


Investigate shared coordinates for structured grids

Seb knows that vtk has some features for interlacing the separate x/y/z arrays without having to copy. He and Bane will discuss offline.

vtkSOADataArrayTemplate is not currently fully implemented in VTK and needs substantial work to leverage. Closing this issue until future consideration. In the meantime, we will continue to memcopy vtkStructuredGrid points


Debugger stops after 1 second of launching

We have written the needed d
Issue Type: Bug
The debugger does not start and immediately stops after 1 second of launching. The debug icons are visible for that brief time (like pause, step over, step into, etc). It does not work with and without a launch.json file. I use the default python debugger configuration ("python current file (workspace)").
This issue appeared today and was not present last week.
 Please paste.

I am running into the same problem, updated VS Code this morning.

Do you see the same behavior if you set a breakpoint on a line of your program and the start debugging?

Yes, I have set multiple breakpoints.
Usually, the debugger opens up a new terminal, changes into the (conda) environment, and executes the program, with all the logging data visible in the terminal.  This is not happening at all.

Yes, breakpoints have no effect on the behaviour.

Thanks :)

Solved by installing previous version of the python extension.
Also discussed here:
https://github.com/microsoft/vscode-python/issues/18453


docs: update community page

This change happened a while ago, but didn't land on the website.
We took this change in a PR to express here https://github.com/expressjs/express/pull/5619


Update the documentation on how to setup an IDE (maybe eclipse, atom, vscode?)

I can take on setting up vscode if you like?

@pmuir Feel free :+1:

I've setup Pycharm + Go.
Pretty straightforward. Where are we going to place the documentation on github? Could you please point me to the location?
The steps were pretty simple:

Download the pycharm TAR / EXE
Launch it and add the project.
On opening any Go file, there;s a prompt asking me to install the Go plugin.
After an installation and restart, i get another prompt asking me to set the GOPATH. I do the same.
and now code complete works :)

Added https://github.com/almighty/almighty-core/pull/87 for vscode.

For just debugging: https://github.com/almighty/almighty-core/blob/8da9223e071a50cb96d5c58009abcb8d57a6e11a/docs/development/debugging.adoc#debugging


HDDS-11196. Improve SCM WebUI Display.

What changes were proposed in this pull request?
There are several areas in SCM WebUI that need optimization:
JVM Properties display: The current display of JVM Properties as a long string diminishes readability. We should present this information in a more user-friendly format.
before modification

after modification

DN list lacks DN version and UUID: The DN list currently does not show DN versions and UUIDs. These details are crucial during upgrades; for instance, with 100 machines, after upgrading 10, it's essential to quickly identify inconsistencies in DN versions. While UUIDs typically appear in SCM logs, locating specific DNs through UUIDs is challenging. Displaying this information on the page would allow us to swiftly understand relevant DN details.
before modification

after modification

SCM HA display: The SCM HA information is currently shown as a string, unlike OM's clear list format. It should be displayed in a list format similar to OM for improved clarity.
before modification

after modification

What is the link to the Apache JIRA
JIRA: HDDS-11196. Improve SCM WebUI Display.
How was this patch tested?
(Please explain how this patch was tested. Ex: unit tests, manual tests, workflow run on the fork git repo.)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this.)

@adoroszlai Can you help review this pr? Thank you very much!

@smitajoshi12 Please help take a look.

Can you Highlight version UUID on screenshots and  Node status screenshot is not clear can you attach clear screenshot

Non-HA

HA

Thank you @slfan1989 for the improvement, @dombizita and @smitajoshi12  for the reviews.

@ivandika3 @dombizita @smitajoshi12 Thank you very much for reviewing the code!


panic loop with (double) external add_decl_doc

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Checked that your issue isn't already filed.
Reduced the issue to a self-contained, reproducible test case.

Description
Lean goes into an infinite panic loop when trying to add documentation to an external declaration twice.
Steps to Reproduce
In a new Lean file, write:
/-- Test -/
add_decl_doc Nat

/-- Test -/
add_decl_doc Nat

Expected behavior: [What you expect to happen]
No error.
Actual behavior: [What actually happens]
stderr is filled with a never-ending stream of panic messages.
Reproduces how often: [What percentage of the time does it reproduce?]
Versions
You can get this information from copy and pasting the output of lean --version,
please include the OS and what version of the OS you're running.
leanprover/lean4:nightly-2022-12-13  on linux
Additional Information
Zulip thread: https://leanprover.zulipchat.com/#narrow/stream/270676-lean4/topic/add_decl_doc.20.20panic.20loop
Sebastian says one add_decl_doc is enough on his machine.

A related but not identical panic, that only requires a single add_decl_doc, is:
in 1957_1.lean:
import Lean

open Lean Meta

/-- The environment extension to track `@[ext]` lemmas. -/
initialize extExtension :
    SimpleScopedEnvExtension (Name × Array (DiscrTree.Key true)) (DiscrTree Name true) ←
  registerSimpleScopedEnvExtension {
    addEntry := fun dt (n, ks) => dt.insertCore ks n
    initial := {}
  }

initialize registerBuiltinAttribute {
  name := `ext
  descr := "Marks a lemma as extensionality lemma"
  add := fun _ _ _ => pure ()
}

and in 1957_2.lean:
import 1957_1

@[ext]
class HasSup (α : Type u) where
  sup : α → α → α

/-- Supremum of a set -/
add_decl_doc HasSup.sup
-- PANIC at Lean.MapDeclarationExtension.insert Lean.Environment:587:2: assertion violation: env.getModuleIdxFor? declName |>.isNone -- See comment at `MapDeclarationExtension`
-- PANIC at Lean.EnvExtensionInterfaceUnsafe.getState Lean.Environment:319:4: invalid environment extension has been accessed

Assuming we do keep panic! the way it is, this means we should be more careful to think about what inhabited instance will get used and the safety of doing so. But I also agree with the point that panic! should perform some kind of non-local control flow rather than continuing with a value that is almost certainly wrong and likely to cause downstream errors.


FEATURE-66 - early support for multiarray

Description
Support for multiarray configuration. I think that few thinks should be done better so comments are very welcomed!
Issues
List the issues impacted by this PR:

Issue ID

66

Checklist:

[x] I have performed a self-review of my own code
[x] I have run 'make check' to ensure my code does not have any formatting, vetting, linting, or security issues
[x] I have run 'make test' to ensure new and existing unit tests pass locally with my changes
[x] I have not allowed coverage numbers to degrade
[x] I have maintained at least 90% code coverage
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

[x] I've deployed this version to cluster with multiarray setting and things seems to work well.
[x] Correct config propagation test should be made. Will have a look at it today.

Can one of the admins verify this patch?

run e2e test

run e2e test

run e2e test

Thanks @hoppea2 🙂 ,
I tried to think of a test that could be made to automatically test if config propagation could be made, but couldn't figure it out. So I've looked at what I've done and there was an issue so that's fixed. Vxflexos config is propagated correctly, karavi-metrics-powerflex.yaml file is also propagated correctly.
If you have an idea how to test config propagation with unit tests, I'd really apreciate it.
Also, not sure where could I find the documentation that should be changed. Can I ask you to point me to correct direction, please?

@TomasKohout, I've verified that no documentation changes will be required for this enhancement.

@gallacher thanks a lot! :+1:
Do you know, what is wrong with E2E tests? I'm not able to check it for myself. :slightly_smiling_face:

run e2e test

Hi guys,
I'm on planned vacation until 15th of June and I don't have a notebook with me (which is a good thing to be honest 😃). I'll have a look and provide enhancements after I'm back, but feel free to adjust whatever you want if you feel so!

Hi Tomas,
We are actively testing multi-array changes, we have found an issue where even though we have multiple array, the list of client has only one entry, hence we are not able to get metrics for volumes created in array for which we do not have entry in client list. Yet to determine the cause.

Hi @alikdell ,
I've added your changes and slightly changed the logging. Could you have a look if it's ok for you, please? :slightly_smiling_face:

Hi @alikdell ,
I've added your changes and slightly changed the logging. Could you have a look if it's ok for you, please? 🙂

Thanks, I will take a look. I also notice some checks are failing

Yep, I've started to work on it, but it will be done tomorrow. I have some business to do elsewhere today. 🙂

run e2e test

Hi @TomasKohout , I just want to make sure this logging comment is addressed to help debugging any issues with connectivity in a multi-array environment: https://github.com/dell/karavi-metrics-powerflex/pull/104/files#r648390746 Thanks!

@tdawe done. :slightly_smiling_face:

e2e pass

LGTM

You're very welcome! Thank you for such a good CR guys. 🙂

You're very welcome! Thank you for such a good CR guys. 🙂

Thank you


type object 'ConnectionRequest' has no attribute 'owner_uri'

Just installed mssql-cli for the first time, and I am seemingly unable to connect to my DB. Please note that sqlcmd DOES connect to the DB and I am able to query it.
Also note, if I omit the --enable-sqltoolsservice-logging argument, the tool provides no output and seemingly hangs.
OS: MacOS Catalina 10.15.7
Python 2.7.16
~ mssql-cli -S <IP_ADDRESS> -U someuser -P somepass --enable-sqltoolsservice-logging

Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
   at Microsoft.SqlTools.Utility.Logger.Close() in D:\a\1\s\src\Microsoft.SqlTools.Hosting\Utility\Logger.cs:line 79
   at Microsoft.SqlTools.ServiceLayer.Program.Main(String[] args) in D:\a\1\s\src\Microsoft.SqlTools.ServiceLayer\Program.cs:line 27
Traceback (most recent call last):
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 174, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/Library/Python/2.7/site-packages/mssqlcli/main.py", line 122, in <module>
    main()
  File "/Library/Python/2.7/site-packages/mssqlcli/main.py", line 115, in main
    run_cli_with(mssqlcli_options)
  File "/Library/Python/2.7/site-packages/mssqlcli/main.py", line 52, in run_cli_with
    mssqlcli.connect_to_database()
  File "/Library/Python/2.7/site-packages/mssqlcli/mssql_cli.py", line 278, in connect_to_database
    owner_uri, error_messages = self.mssqlcliclient_main.connect_to_database()
  File "/Library/Python/2.7/site-packages/mssqlcli/mssqlcliclient.py", line 91, in connect_to_database
    owner_uri, error_messages = self._execute_connection_request_with(connection_params)
  File "/Library/Python/2.7/site-packages/mssqlcli/mssqlcliclient.py", line 180, in _execute_connection_request_with
    response = connection_request.get_response()
  File "/Library/Python/2.7/site-packages/mssqlcli/jsonrpc/contracts/request.py", line 67, in get_response
    return self.response_error(error)
  File "/Library/Python/2.7/site-packages/mssqlcli/jsonrpc/contracts/connectionservice.py", line 22, in response_error
    u'ownerUri': cls.owner_uri,
AttributeError: type object 'ConnectionRequest' has no attribute 'owner_uri'

Running from source works.

how you solve the issue?

how you solve the issue?

Same issue :) Same question as @sbreakey

@mingrw
https://github.com/dotnet/core/issues/1930
So for me I'm running fedora, and
sudo dnf remove compat-openssl

fixed the issue

I don't have root permission to remove compat-openssl.. Any other solution? Thanks!


Fix ValueError for test_summarization

resolve unable to create tensor issue for PYTEST-t5 test_summarization

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


feat: Defaults to MySQL 8

I would really like to turn this on, but maybe we should wait until https://wandb.atlassian.net/browse/WB-9250 is resolved? Anni said he was going to put Maddy on it this week.

@davidwallacejackson its enabled in aws https://github.com/wandb/terraform-aws-wandb/pull/20

@davidwallacejackson its enabled in aws wandb/terraform-aws-wandb#20

Fair enough lol

This PR is included in version 1.1.0 :tada:


MAINT: Delete the apt-get lists after installing packages

Cleaning up the apt cache and removing /var/lib/apt/lists helps keep the image size down. Since the RUN statement starts with apt-get update, the package cache will always be refreshed prior to apt-get install.
Clean up must be performed in the same RUN step, otherwise it will affect image size.

@dipinknair - @MaxJPRey's change will precisely do that, reduce the image size


Need to use glint --build

Noticed this while working on https://github.com/embroider-build/addon-blueprint/pull/89
rollup (using tsc?), reported:
error TS2688: Cannot find type definition file for 'ember__test-helpers'.
  The file is in the program because:
    Entry point for implicit type library 'ember__test-helpers'

but lint:types was not.
to make glint behave in the same way, I changed lint:types to do glint --build, which now behaves the same as tsc.
cc @dfreeman @chriskrycho @simonihmig

Hm, interesting... but isn't --build supposed to be when you use TypeScript project references, which we don't?
For the record, this is related to to the build issue mentioned above: https://github.com/embroider-build/addon-blueprint/pull/96

but isn't --build supposed to be when you use TypeScript project references, which we don't?

i am not sure tbh. In any case the behavior is different, which is very surprising if the flag ever was meant only for project references.

this is related to to the build issue mentioned above: #96

yeah, sorta, without --build, we get inconsistent results between tsc --build and glint (glint alone, sometimes errors, sometimes doesn't)
The --build flag also gives you access to --clean and --force, which is good for when you can't trust the default behavior 😢

from Discord:

the default should not use --build, caches being the complicated beasts that they are, just as we wouldn’t have tsc --build be the default.
If there is a difference in behavior between how the two things interpret the graph of modules, that would be a bug!

I'll need to do more digging to figure out what was going on with sans --build

Re-opening due to: https://discord.com/channels/480462759797063690/786312479620726804/1067969274091667556

isn't --build supposed to be when you use TypeScript project references, which we don't?

This is exactly right; it doesn't make sense to use --build (with glint or tsc) in a non-composite setup 😄

Closing again :sweat_smile: do to: https://github.com/typed-ember/glint/issues/525#issuecomment-1405075979
And actual issue report here: https://github.com/pnpm/pnpm/issues/5986


Test runner breaks when group handler is async

Description
Japa seems not to support async handler current and breaks with the following unexpected behaviours:

All test running within the group with the async handler fails without any specific error,
Pinning all tests within the group with group.tap((test) => test.pin()) results in all tests running (not just the tests within the pinned group).
Pinning only one tests within a group with the async handler runs few random tests with the pinned tests still failing.

Package version
    "@japa/api-client": "^1.2.0",
    "@japa/assert": "^1.3.4",
    "@japa/preset-adonis": "^1.0.15",
    "@japa/run-failed-tests": "^1.0.7",
    "@japa/runner": "^2.0.7",

Error Message & Stack Trace
As seen below, the failed test was the only pinned test within a group with async handler but few other random tests ran while the pinned test still failed.
unit / Pagination Service (tests/unit/pagination_service.spec.ts)
  ✔ should return same pagination values if they are valid (1ms)
  ✔ should use `1` as `page` value if not provided (0ms)
  ✔ should use `20` as `per_page` value if not provided (0ms)
  ✔ should use `50` as `per_page` value if provided value is greater `50` (0ms)
{"level":30,"time":1653300409042,"pid":27492,"hostname":"Ndianabasi-Mac.lan","name":"backend-v1","msg":"started server on <IP_ADDRESS>:4444"}

functional / Authentication (tests/functional/auth.spec.ts)
  ✔ User login should be successful (130ms)

tests/functional/workspace_users/update_users.spec.ts
  ✖ A superadmin can create and associate a user in any workspace (108ms)

Relevant Information
Example of what I am trying to achieve with async group handler is generating a fake file only once for the all tests within a group:
test.group('Workspace Users | create', async (group) => {
  group.each.setup(async () => {
    await Database.beginGlobalTransaction()
    return () => Database.rollbackGlobalTransaction()
  })

  const role = () => faker.helpers.arrayElement(['designer', 'admin', 'manager'])
  const fakeAvatar = await file.generatePng('1mb')

  test('A superadmin can create and associate a user in any workspace', async ({
    assert,
    client: apiClient,
    route,
  }) => {

...

    const response = await apiClient
      .post(route('WorkspaceUsersController.store', [workspace.id]))
      .field('full_name', newUser.fullName)
      .field('email', newUser.email)
      .field('role', role())
      .file('avatar', fakeAvatar.contents, { filename: fakeAvatar.name })
      .loginAs(superadmin)

...

  })
})

Group handler isn't meant to be async. The code you are writing should be wrapped either inside a helper function or inside hooks

Okay. Will there be any adverse implications of making Group handlers async?

It leads to the code I do not wish to write. The main goal of the group callback is to group tests and not run actions with top level code.

Okay. I will be closing this.


Redis Modules Identification missing for "searchlight" version of search module

When we do a check for capabilities we should also check for the module named "searchlight" which is present instead of "search"  in certain deployments

We already have the constant for it:
DEFAULT_REQUIRED_MODULES = [
    {"name": "search", "ver": 20600},
    {"name": "searchlight", "ver": 20600},
]

There are two call to validate_modules like:
validate_modules(installed_modules, [{"name": "search", "ver": 20810}])

My concern is the version number in the defaults being 20600 versus the 20810 being used in index.py
Potentially I simple fix would be to have a way to do an OR in, e.g. passing a flag (bool):
def validate_modules(
    installed_modules: Dict[str, Any],
    required_modules: Optional[List[Dict[str, Any]]] = None,
) -> None:

or, introduce an alias like:
DEFAULT_REQUIRED_MODULES = [
    {"name": "search", "alias": "searchlight", "ver": 20600},
]

assuming that it is safe to equate "search" and "searchlight"
@tylerhutcherson @justin-cechmanek @rbs333

Following up on this thread -- the simple solution is to provide the additional searchlight module+version as another item in the list passed to validate_modules. That method does a check to see if either/or of the items in the provided list are present. Otherwise, an exception is raised.

Fixed here --> https://github.com/redis/redis-vl-python/pull/227

I'm seeing the following issue
It's Mac M1 Pro.
Redis is running on Docker, I also tried directly.
I'm on the latest package 0.3.4
ERROR - app.services.events.event_manager.EventManager: Unexpected error in __event_listener: Required Redis db module search >= 20600 OR searchlight >= 20600 not installed. See Redis Stack docs at https://redis.io/docs/latest/operate/oss_and_stack/install/install-stack/.


Add MLST results to staramr report

Add the ability to detect the MLST type for the input fasta files and integrate this into the staramr report.

Finished in #77


Subscribe to RSS feeds as well as hEntry feeds

I'm not sure everyone agrees with this model, but this is what I'm most looking for in an indie reader. I want to use the "subscribe" model for as many things as I can, whether the publisher is using RSS, or marks up their pages with hEntry and other microformats, or some other option (email newsletters?).
It would also make it easier for me to move towards an indie reader or reading sites via their microformatted posts if I could read them in the same place as my existing feeds.

I have the same "vision". The data formats should be irrelevant to the user and the reader should be smart enough to find whatever it's looking for: RSS, Atom, h-Atom, or even weirder things like maybe fragments?
Newsletter/emails would also be great. Maybe that means creating an email endpoint for each user in the reader?

I agree, the underlying data format shouldn't matter, h-entry, RSS, email, are all reasonable inputs. I like the idea of being able to subscribe to email newsletters from the reader! I'll see what I can do with that.


crash on OOB array access

The following program crashes on microbit and in the simulator, even though it's perfectly legal JavaScript:
let arr: number[] =[]
for (let i = 0; i < 32; ++i) {
    if (!arr[i])
        arr[i] = i
}

cc @pelikhan @tballmsft - comments?
Related issue: #1053

Adding default values to arrays should solve these issues.

Also a[I] access above is beyond the length of the array. Do we want to support default values for these as well?

Yes we should have a runtime that is resilient to invalid input.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Abhijith Chatra<EMAIL_ADDRESS>Sent: Sunday, January 8, 2017 5:51:05 PM
To: Microsoft/pxt
Cc: Peli de Halleux; Mention
Subject: Re: [Microsoft/pxt] crash on OOB array access (#1054)
Also a[I] access above is beyond the length of the array. Do we want to support default values for these as well?

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fpxt%2Fissues%2F1054%23issuecomment-271198805&data=02|01|jhalleux%40microsoft.com|40294a2a60d74aa6af6408d43831fa87|72f988bf86f141af91ab2d7cd011db47|1|0|636195234694571655&sdata=VntW6OY38lfGLjZ3zcI4T%2FFDNPtBjZJcQPuzPMlAtRA%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAD-4KaUQCa0o08F8NVPeq1FbbdbNGAO3ks5rQZKJgaJpZM4LdwAL&data=02|01|jhalleux%40microsoft.com|40294a2a60d74aa6af6408d43831fa87|72f988bf86f141af91ab2d7cd011db47|1|0|636195234694571655&sdata=bXULvnC3IWlmcHvT26h6rlWUBFocq%2FQhRod0t0JxSgI%3D&reserved=0.

I think the primary goal should be to stay true to JavaScript semantics, which also happens to be resilient to invalid input.
Of course we're still gonna crash (OOM) if someone does arr[100000] = 1...

Fixed


User Management UI

Purpose
This adds the User Management UI to ops
Changes

Add UI table to list all existing users
Ability to search for users on the table (fuzzy search)
Pagination for table when 25+
Can add a new user
Can edit a user's info (username is always uneditable, as an admin, I can edit any user's name, as the user that is currently logged in, I can change my own password)
I can delete a user

Note/Asks for reviewers:

I would like an extra check on the safety of entering and updating a user's password and make sure this is good from a security POV.

Checklist

[ ] Applicable documentation updated (guides, quickstart, postman collections, tutorial, fidesdemo, database diagram.
If docs updated (select one):

[ ] documentation complete, or draft/outline provided (tag docs-team to complete/review on this branch)
[ ] documentation issue created (tag docs-team to complete issue separately)

[ ] Good unit test/integration test coverage
[ ] This PR contains a DB migration. If checked, the reviewer should confirm with the author that the down_revision correctly references the previous migration before merging
[ ] The Run Unsafe PR Checks label has been applied, and checks have passed, if this PR touches any external services

Ticket
Closes #357
Closes #358
Closes #359
Closes #360

Hey @LKCSmith great start! I've spent some time functionally testing this afternoon and found the following to address:

User is prompted to login inconsistently on view change — were you experiencing this during development?
No error message in UI for user creation 422s (e.g. password not strong enough) — this should ideally show the same way as if a username or password is omitted, with a different message
View users permission omitted from list — I suspect this was an oversight in the design? What happens is that new users created are not able to view users in the system, even if they are able to create them
[image:F936A5FB-F44A-46B0-A465-6A13A13BCFE5-32382-000008917E502A12/Screenshot 2022-05-13 at 18.06.30.png]
Login screen asks for email, should read username for now — not directly related to this PR but would be nice to correct
Privileges toggles not working correctly (unless this is intentional and I'm not across the decision?)

Viewing policies auto toggles viewing datastore connections
Create policies auto triggers approve subject requests
Can’t remove dependencies ^

@seanpreston
User is prompted to login inconsistently on view change — were you experiencing this during development?
I wasn't, and I am not experiencing this locally this morning either. Are you noticing a specific navigation around the app that causes this? I've tried jumping around all over but couldn't trigger this bug.
No error message in UI for user creation 422s (e.g. password not strong enough) — this should ideally show the same way as if a username or password is omitted, with a different message
Will work on this now 🙂
View users permission omitted from list — I suspect this was an oversight in the design? What happens is that new users created are not able to view users in the system, even if they are able to create them
Added, although I don't think that alone resolves the issue. I also added a checkbox for 'View users'. Should this as well as 'View roles' be automatically checked for each user created?
Login screen asks for email, should read username for now — not directly related to this PR but would be nice to correct
Fixed!
Privileges toggles not working correctly (unless this is intentional and I'm not across the decision?)
Viewing policies auto toggles viewing datastore connections
Create policies auto triggers approve subject requests
Can’t remove dependencies ^

I'm not experiencing these bugs locally either. Maybe you can demonstrate to me on a call?

Absolutely crushing it, Laura.  Great work! 🎉
I think the functional testing Sean and Allison did is quite thorough. In addition to what they've found, I've noticed the following things:

Logging in, then navigating around User Management pages triggers logout sporadically (and then you need to log in twice)
Clicking links in the breadcrumbs nav triggers a full page reload (should use Next link component to avoid that)
Spacing issues throughout the layout (mostly just padding tweaks for eyecandy – not critical path)
Submit button for creating a user should read 'Create' instead of 'Save'
There shouldn't be a placeholder in the login screen
Can't tab through inputs in the Delete User modal for some reason
Password input for new users is a bit laggy (this may indicate state mismanagement on some level)
Username is not passed to dropdown menu

Of these, the only critical bug is the sporadic logout issues. However, since the functionality is there, I'm comfortable merging, provided we address this bug this week (something I'm happy to take on today / tomorrow). The rest of these don't need to be addressed in these PR either – I'm just dropping them here for future reference.
I also have a number of stylistic / cleanup related nitpicks w/r/t the code. I began to make individual comments to address them, but I think in this case it might be more efficient for me to clean them up on my own after this PR is merged, and then we can do a bit of a post mortem next week and review some of the changes I made.
And to be clear, when doing PR reviews in general, it's generally my opinion that any syntax or style things that come up are more a function of the scope of work and the time constraint around it than of somebody's personal coding style. So don't feel like any changes I make are because mistakes were made or that there were glaring oversights. I totally recognize that it's more just the sheer volume of code leaves plenty of spaces for bugs to hide and makes cleanup difficult + time-consuming :)
Finally, I'd like to address the scope of this PR – I think going forward we'll want to try to break features down into smaller, more manageable PRs so that we don't get into a place of overwhelm like this again. That would help with both finding bugs, general feelings of overwhelm, and also give more time and space to do cleanup.
Again, amazing job with this! Very happy to see it land. 🥳


Add  'azure/modtm' provider

Description

Type of Change

[ ] Non-module change (e.g. CI/CD, documentation, etc.)
[ ] Azure Verified Module updates:

[ ] Bugfix containing backwards compatible bug fixes

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[ ] Feature update backwards compatible feature updates.
[ ] Breaking changes.
[ ] Update to documentation

Checklist

[ ] I'm sure there are no other open Pull Requests for the same update/change
[ ] My corresponding pipelines / checks run clean and green without any errors or warnings
[ ] I did run all  pre-commit checks

fixes https://github.com/Azure/terraform-azurerm-avm-res-network-networkwatcher/issues/54


Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble

Version of the custom_component

Installation method (hacs / manual)
hacs
Installation method of hass (venv, docker, hassio,...)
Configuration
HACS

## Describe the bug

We connect stopped working, tried removing it and set it up again and stuck here:
Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble

## Debug log

Logger: homeassistant.util.package
Source: util/package.py:123
First occurred: June 9, 2024 at 12:01:56 PM (3 occurrences)
Last logged: June 9, 2024 at 12:02:00 PM

Unable to install package weconnect==0.59.5: ERROR: Cannot install weconnect==0.59.5 because these package versions have conflicting dependencies. ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

```text

Logger: aiohttp.server
Source: /usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py:421
First occurred: 3:54:15 PM (3 occurrences)
Last logged: 4:18:33 PM

Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 452, in _handle_request
    resp = await request_handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_app.py", line 543, in _handle
    resp = await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_middlewares.py", line 114, in impl
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 83, in forwarded_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 85, in ban_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 242, in auth_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 32, in headers_middleware
    response = await handler(request)
               ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 73, in handle
    result = await handler(request, **request.match_info)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 81, in with_admin
    return await func(self, request, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 70, in wrapper
    return await method(view, request, data, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 172, in post
    return await self._post_impl(request, data)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 179, in _post_impl
    return await super()._post_impl(request, data)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 84, in _post_impl
    result = await self._flow_mgr.async_init(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1262, in async_init
    flow, result = await self._async_init(flow_id, handler, context, data)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1282, in _async_init
    flow = await self.async_create_flow(handler, context=context, data=data)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1418, in async_create_flow
    handler = await _async_get_flow_handler(
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2776, in _async_get_flow_handler
    await _load_integration(hass, domain, hass_config)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2753, in _load_integration
    await async_process_deps_reqs(hass, hass_config, integration)
  File "/usr/src/homeassistant/homeassistant/setup.py", line 561, in async_process_deps_reqs
    await requirements.async_get_integration_with_requirements(
  File "/usr/src/homeassistant/homeassistant/requirements.py", line 54, in async_get_integration_with_requirements
    return await manager.async_get_integration_with_requirements(domain)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/requirements.py", line 176, in async_get_integration_with_requirements
    await self._async_process_integration(integration, done)
  File "/usr/src/homeassistant/homeassistant/requirements.py", line 192, in _async_process_integration
    await self.async_process_requirements(
  File "/usr/src/homeassistant/homeassistant/requirements.py", line 274, in async_process_requirements
    self._raise_for_failed_requirements(name, missing)
  File "/usr/src/homeassistant/homeassistant/requirements.py", line 302, in _raise_for_failed_requirements
    raise RequirementsNotFound(integration, [req])
homeassistant.requirements.RequirementsNotFound: Requirements for volkswagen_we_connect_id not found: ['weconnect==0.59.5'].

I've worked around it by editing custom_components/volkswagen_we_connect_id/manifest.json and updating the dependency on weconnect to the latest version (0.60.3) which seems to work fine.

Ok, can you post how your edits looked like so I can copy it? :)

You just need to update the requirements key:
  "requirements": ["weconnect==0.60.3", "ascii_magic>=2.0.0"],

After newest update v0.2.3, I have problem with weconnect package version.:
Setup failed for custom integration 'volkswagen_we_connect_id': Requirements for volkswagen_we_connect_id not found: ['weconnect==0.60.3'].

@prezervos works for me 🤷 and weconnect 0.60.3 is definitely published on pypi – there might be something about your particular setup that's preventing it being found (network problem, other add-ons with clashing dependencies). I didn't realise there was a new version - 0.2.3 just showed up in HACS for me just now (I was on 0.2.0) and the update worked fine.

@dewet22 Thank you for info. I will edit the version in manifest to 0.60.2, this is installed currently .

Awesome, thx for the help everyone and for a great addon!

After newest update v0.2.3, I have problem with weconnect package version.:
Setup failed for custom integration 'volkswagen_we_connect_id': Requirements for volkswagen_we_connect_id not found: ['weconnect==0.60.3'].

same here. had to downgrade to 0.60.2

Version 0.2.3 was made because of conflicts betweeen version 0.2.2 and home Assistant Core version 2024.6.x - Have you upgraded your home assistant core to version 2024.6.x - if not, that could be the reason

Yes I am still on 2024.5.x. I'll try to upgrade.

I can also confirm that upgrading to 2024.6.x fixed the issue.


Add icons down-right-from-square, up-right-from-square, and file-arrow-curved-right and remove some

Pull Request
🤨 Rationale
Added down-right-from-square, up-right-from-square, and file-arrow-curved-right icons. Removed share-square (use the up-right-from-square icon instead) and file-export (use the file-arrow-curved-right icon instead) icons.
👩💻 Implementation
Followed the contributing process

🧪 Testing
Manual Storybook review
✅ Checklist

[x] I have updated the project documentation to reflect my changes or determined no changes are needed.

@NIbokeefe - Could you confirm that these icons are correct? Also, could you update the names in the Nimble_Iconography.ai file to reflect the naming that we're using here?

@fredvisser Confirmed these icons are correct and names are updated on the Nimble_Iconography document.

This closed #1237


Retz restarts job without a need, making them fail

We have some jobs that are running for some time, and then it seems as if Retz thinks they are dead and submits them again, causing the second instance to fail with a "Task has duplicate ID" error, and the second instance to be unreachable while actually running fine. Please find the log below and specifically the behavior around job 22566:
...
2017-08-28 10:34:12.874 INFO  [qtp1797188415-682668] io.github.retz.web.WebConsole - 200 GET http://retz.marathon.mesos:10015/job/22569 null from <IP_ADDRESS> retz-client-0.2.11 (0.2.11) Java/1.8.0_121
2017-08-28 10:34:12.874 INFO  [qtp1797188415-682618] io.github.retz.web.WebConsole - 200 GET http://retz.marathon.mesos:10015/job/22566 null from <IP_ADDRESS> retz-client-0.2.11 (0.2.11) Java/1.8.0_121
2017-08-28 10:34:12.874 INFO  [qtp1797188415-682627] io.github.retz.web.WebConsole - 200 GET http://retz.marathon.mesos:10015/job/22568 null from <IP_ADDRESS> retz-client-0.2.11 (0.2.11) Java/1.8.0_121
2017-08-28 10:34:12.874 INFO  [qtp1797188415-682366] io.github.retz.web.WebConsole - 200 GET http://retz.marathon.mesos:10015/job/22567 null from <IP_ADDRESS> retz-client-0.2.11 (0.2.11) Java/1.8.0_121
2017-08-28 10:34:42.876 INFO  [qtp1797188415-682366] io.github.retz.web.WebConsole - 200 GET http://retz.marathon.mesos:10015/job/22566 null from <IP_ADDRESS> retz-client-0.2.11 (0.2.11) Java/1.8.0_121
2017-08-28 10:34:42.876 INFO  [qtp1797188415-682517] io.github.retz.web.WebConsole - 200 GET http://retz.marathon.mesos:10015/job/22568 null from <IP_ADDRESS> retz-client-0.2.11 (0.2.11) Java/1.8.0_121
2017-08-28 10:34:42.876 INFO  [qtp1797188415-682567] io.github.retz.web.WebConsole - 200 GET http://retz.marathon.mesos:10015/job/22567 null from <IP_ADDRESS> retz-client-0.2.11 (0.2.11) Java/1.8.0_121
2017-08-28 10:34:42.876 INFO  [qtp1797188415-682675] io.github.retz.web.WebConsole - 200 GET http://retz.marathon.mesos:10015/job/22569 null from <IP_ADDRESS> retz-client-0.2.11 (0.2.11) Java/1.8.0_121
2017-08-28 10:35:07.540 INFO  [Thread-652910] i.g.retz.scheduler.RetzScheduler - Offer rescinded: 48a30380-c479-4639-83e2-a2d24463d8a8-O1221388
2017-08-28 10:35:07.540 INFO  [Thread-652911] i.g.retz.scheduler.RetzScheduler - Offer rescinded: 48a30380-c479-4639-83e2-a2d24463d8a8-O1221389
2017-08-28 10:35:07.540 INFO  [Thread-652912] i.g.retz.scheduler.RetzScheduler - Offer rescinded: 48a30380-c479-4639-83e2-a2d24463d8a8-O1221390
2017-08-28 10:35:07.540 INFO  [Thread-652913] i.g.retz.scheduler.RetzScheduler - Offer rescinded: 48a30380-c479-4639-83e2-a2d24463d8a8-O1221391
2017-08-28 10:35:07.541 INFO  [Thread-652914] i.g.retz.scheduler.RetzScheduler - Offer rescinded: 48a30380-c479-4639-83e2-a2d24463d8a8-O1221392
2017-08-28 10:35:07.541 INFO  [Thread-652915] i.g.retz.scheduler.RetzScheduler - Offer rescinded: 48a30380-c479-4639-83e2-a2d24463d8a8-O1221393
2017-08-28 10:35:07.541 INFO  [Thread-652916] i.g.retz.scheduler.RetzScheduler - Offer rescinded: 48a30380-c479-4639-83e2-a2d24463d8a8-O1221394
2017-08-28 10:35:07.541 INFO  [Thread-652917] i.g.retz.scheduler.RetzScheduler - Offer rescinded: 48a30380-c479-4639-83e2-a2d24463d8a8-O1221395
2017-08-28 10:35:07.542 INFO  [Thread-652918] i.g.retz.scheduler.RetzScheduler - Offer rescinded: 48a30380-c479-4639-83e2-a2d24463d8a8-O1221396
2017-08-28 10:35:07.542 INFO  [Thread-652919] i.g.retz.scheduler.RetzScheduler - Offer rescinded: 48a30380-c479-4639-83e2-a2d24463d8a8-O1221398
2017-08-28 10:35:07.542 INFO  [Thread-652920] i.g.retz.scheduler.RetzScheduler - Offer rescinded: 48a30380-c479-4639-83e2-a2d24463d8a8-O1221399
2017-08-28 10:35:07.543 INFO  [Thread-652921] i.g.retz.scheduler.RetzScheduler - Offer rescinded: 48a30380-c479-4639-83e2-a2d24463d8a8-O1221400
2017-08-28 10:35:07.850 INFO  [pool-3-thread-1] i.g.retz.scheduler.RetzScheduler - Offer stock renewal: 7 offers available (10 declined from stock)
2017-08-28 10:35:08.074 INFO  [pool-3-thread-1] io.github.retz.db.Database - TaskId of id=22566: retz-abc-run-id-22566 / retz-abc-run-id-22566
2017-08-28 10:35:08.119 INFO  [pool-3-thread-1] io.github.retz.db.Database - Job (id=22566) status updated to STARTING
2017-08-28 10:35:08.120 INFO  [pool-3-thread-1] i.g.retz.scheduler.RetzScheduler - 1 accepted, 0 declined (6 offers back in stock)
2017-08-28 10:35:08.122 INFO  [Thread-652923] i.g.retz.scheduler.RetzScheduler - Status update of task retz-abc-run-id-22566: TASK_LOST / Task launched with invalid offers: Offer 48a30380-c479-4639-83e2-a2d24463d8a8-O1221396 is no longer valid (REASON_INVALID_OFFERS)
2017-08-28 10:35:08.188 INFO  [pool-3-thread-1] io.github.retz.scheduler.JobQueue - Scheduled retry 2/5 of Job(taskId=retz-abc-run-id-22566), reason='Task launched with invalid offers: Offer 48a30380-c479-4639-83e2-a2d24463d8a8-O1221396 is no longer valid'
2017-08-28 10:35:08.234 INFO  [pool-3-thread-1] io.github.retz.db.Database - Job (id=22566) status updated to QUEUED
2017-08-28 10:35:08.813 INFO  [pool-3-thread-1] i.g.retz.scheduler.RetzScheduler - Offer stock renewal: 1 offers available (12 declined from stock)
2017-08-28 10:35:09.039 INFO  [pool-3-thread-1] io.github.retz.db.Database - TaskId of id=22566: retz-abc-run-id-22566 / retz-abc-run-id-22566
2017-08-28 10:35:09.085 INFO  [pool-3-thread-1] io.github.retz.db.Database - Job (id=22566) status updated to STARTING
2017-08-28 10:35:09.086 INFO  [pool-3-thread-1] i.g.retz.scheduler.RetzScheduler - 1 accepted, 0 declined (0 offers back in stock)
2017-08-28 10:35:09.089 INFO  [Thread-652925] i.g.retz.scheduler.RetzScheduler - Status update of task retz-abc-run-id-22566: TASK_ERROR / Task has duplicate ID: retz-abc-run-id-22566 (REASON_TASK_INVALID)
...

Our Retz users still see the output stream from the first instance of the job (because the job is actually still running, as it seems), but querying its status shows FAILED.

I pushed my code of the redesign of task reconciliation to the master branch as a04817c7263a (now it's just HEAD). As it is not a simple procedure to reproduce a situation that causes offer reconciliation, I'm hoping if you could test the change in your environment if it's not so difficult as for me.

@kuenishi I tested it on my environment, and it works for us 🎉 🎉 🎉 Thank you for the improvement!!

Thank you for your fix! Very nice!
One question on that: I have an environment with three nodes. Node A runs a compute job and when I restart node B I see the following output:
2017-09-12 17:46:31.744 WARN  [Thread-30] i.g.retz.scheduler.RetzScheduler - Slave lost: 2b2708b0-9189-4457-b7b6-6425175213a6-S1
2017-09-12 17:46:31.799 INFO  [Thread-32] i.g.retz.scheduler.RetzScheduler - Status update of task abcd-id-2930: TASK_RUNNING / Reconciliation: Latest task state (REASON_RECONCILIATION)
2017-09-12 17:46:31.823 ERROR [pool-3-thread-1] i.g.retz.mesosc.MesosHTTPFetcher - No matching directory at framework=6126772b-3a46-478c-b1ef-5b0585e73a16-0001, executor=, container=21c9c9b7-b349-4bd9-9eae-3ccaed422d3a
2017-09-12 17:46:31.826 WARN  [pool-3-thread-1] i.g.retz.mesosc.MesosHTTPFetcher - 1 retry happening for frameworkId=6126772b-3a46-478c-b1ef-5b0585e73a16-0001, executorId=, containerId=21c9c9b7-b349-4bd9-9eae-3ccaed422d3a
2017-09-12 17:46:31.857 ERROR [pool-3-thread-1] i.g.retz.mesosc.MesosHTTPFetcher - No matching directory at framework=6126772b-3a46-478c-b1ef-5b0585e73a16-0001, executor=, container=21c9c9b7-b349-4bd9-9eae-3ccaed422d3a
2017-09-12 17:46:31.858 WARN  [pool-3-thread-1] i.g.retz.mesosc.MesosHTTPFetcher - 2 retry happening for frameworkId=6126772b-3a46-478c-b1ef-5b0585e73a16-0001, executorId=, containerId=21c9c9b7-b349-4bd9-9eae-3ccaed422d3a
2017-09-12 17:46:31.879 ERROR [pool-3-thread-1] i.g.retz.mesosc.MesosHTTPFetcher - No matching directory at framework=6126772b-3a46-478c-b1ef-5b0585e73a16-0001, executor=, container=21c9c9b7-b349-4bd9-9eae-3ccaed422d3a
2017-09-12 17:46:31.880 WARN  [pool-3-thread-1] i.g.retz.mesosc.MesosHTTPFetcher - 3 retry happening for frameworkId=6126772b-3a46-478c-b1ef-5b0585e73a16-0001, executorId=, containerId=21c9c9b7-b349-4bd9-9eae-3ccaed422d3a
2017-09-12 17:46:31.891 ERROR [pool-3-thread-1] i.g.retz.mesosc.MesosHTTPFetcher - 3 retries on fetching sandbox URI failed
2017-09-12 17:46:31.899 INFO  [pool-3-thread-1] io.github.retz.db.Database - Job (id=2930) status updated to STARTED

As reported by @ksauzz, the job actually keeps running (although the timestamp is updated as well, same problem as described in https://github.com/retz/retz/issues/158#issuecomment-328785294), but I am wondering about the WARN and ERROR messages from the MesosHttpFetcher. The containerId mentioned in the log is the id of the process that is running on node A and I can access the sandbox just fine via the Mesos web interface. Do you know what is happening here?

@tgpfeiffer Those logs happened from status update of job A caused by task reconciliation . Both error and warn lines indicates that executor id is somehow empty, which is used to find out directory path of sandbox via Mesos /state endpoint. Executor id is automatically named according to task ids...
Ha, and I found "Note that most of the other fields in the returned TaskStatus message will not be set: for example, reconciliation cannot be used to retrieve the labels or data fields associated with a running task." in the document. You're right, it's another bug.

I think I have fixed this in https://github.com/retz/retz/commit/619b27d5423f6dfa83a40d728aef27b3b93a7eaa with a test in following commit. Feel free to open another issue if that ERROR logs still happen.


Add noticePublicationDate field to view role

Also check set of milestone and contract fields

Pull Request Test Coverage Report for Build 137

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.294%

Totals

Change from base Build 136:
0.0%

Covered Lines:
422

Relevant Lines:
425

💛  - Coveralls

Pull Request Test Coverage Report for Build 137

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.294%

Totals

Change from base Build 136:
0.0%

Covered Lines:
422

Relevant Lines:
425

💛  - Coveralls


Add more default ENV vars for better out of the box security

Considering the bitnami defaults, i would suggest to override and "expose" some of the variable they support. Most of them are not listed on https://hub.docker.com/r/bitnami/openldap
You find a reference on https://github.com/bitnami/containers/blob/main/bitnami/openldap/2.6/debian-12/rootfs/opt/bitnami/scripts/libopenldap.sh
env:
  # do not allow non binding by default
  LDAP_ALLOW_ANON_BINDING: no
  # do not create any users by default
  LDAP_USERS: ''
  LDAP_PASSWORDS: ''
  # this is the default, but probably just to be safe (argueable)
  LDAP_CONFIG_ADMIN_ENABLED: no

Currently, this charts deploys default users and passwords on all instances, which might be exploited since they are documented. What are your thoughts?

Sorry i found https://github.com/jp-gouin/helm-openldap/blob/master/templates/configmap-env.yaml and understood that you already cared about all that, since users/passwords is empty by default (good job).
Leaves us with
env:
  # do not allow non binding by default
  LDAP_ALLOW_ANON_BINDING: no
  # this is the default, but probably just to be safe (argueable)
  LDAP_CONFIG_ADMIN_ENABLED: no

What are your thoughs about those?

Hi @EugenMayer , yep this sounds good. Would you like to submit a PR ?

I will, sure. On thing that i found to be in a similar matter is https://github.com/jp-gouin/helm-openldap/blob/master/values.yaml#L144 - i would suggest to deactivate debug by default (no hard feelings here). Should i include the latter?

Yep you can include it , also Bitnami debug is not the same as openldap log level debug

Yep you can include it , also Bitnami debug is not the same as openldap log level debug

Logging every connection and so fort - that LDAP_LOGLEVEL and not BITNAME_DEBUG in the first place? Currently, the default deployment seems very verbose, i would say at least not how i would run it in production. For sure i would switch on the log-level during debugging issues, very helpfull.
What do you expect the chart to be out of the box, rather geared towards devs/sandboxing or prod?

Just tested it, LDAP_LOGLEVEL really is handling the connection logs. Since 256 is the default in the bitname chart too, it seems your default is sensible and what is expected - i leave it alone and judge this as "it's just me being strange" :)
I create the PR right away, thanks for the discussion / help / insight


Need python packages in run_ner.py

Dear @EmilyAlsentzer
Your clinicalBERT is a great work and I want to reimplement it.
The run_ner.py requires python packages, such as 'modeling', 'optimization', and 'tokenization'.
Can you share the packages ?
Thank you

All of those packages come from the original BERT repo: https://github.com/google-research/bert. Since we adapted this code from the kyzhouhzau/BERT-NER repo, this code is in tensorflow. Hope this helps!


ci(build-and-test): ignore CodeCov errors

Changed so that the CodeCov uploader does not throw an error when the upload fails.
This avoids problems when private repositories want to build using this workflow, but do not want to use CodeCov.
Signed-off-by: Keisuke Shima<EMAIL_ADDRESS>

Ah, since I edited the PR title, could you fix the commit title? They should be the same when there is only one commit.


SyncTrayzor file downloading status window missing

Hi, my PC does not display the SyncTrayzor file downloading status window as per the GitHub image at https://github.com/canton7/SyncTrayzor.
Is there a setting for this, or is it because I am using it on Windows 10, Ver 1709, 16299.64
STray ver 1.1.18, with ST 0.14.40,
Thanks

No, that should work. Single click the tray icon while a large file is downloading.
On 28 November 2017 00:32:48 GMT+00:00, jaggeri<EMAIL_ADDRESS>wrote:

y PC does not display the SyncTrayzor file downloading status window as
per the GitHub image at https://github.com/canton7/SyncTrayzor.
Is there a setting for this, or is it because I am using it on Windows
10, Ver 1709, 16299.64 - the one in github looks like Win 7
STray ver 1.1.18, with ST 0.14.40,
Thanks

--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/canton7/SyncTrayzor/issues/424

Hi Antony,
It works !
I think I had  high CPU % and mouse lag and did not wait for the window to pop up after my left mouse click
Operator error again !  : ) he he
Thank you


Allow running the plugin as a script.

I have reorganized the plugin script to allow running the code as a
script so that it's easier to develop the code.
Signed-off-by: Warren Turkal<EMAIL_ADDRESS>

Also, does this code have a license? I don't see a license file.

But nice addition, merging then.
Will add license too.


⚠ Bofrost.be has degraded performance

In bb42ae9, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1897 ms

Resolved: Bofrost.be performance has improved in 8b01ac6 after 5 hours, 22 minutes.


aldryn-search 0.4.0 status?

aldryn-search 0.4.0 is out on PyPi, but the source here hasn't been updated. Has the official repo moved? Is Aldryn no longer publishing the source? On the PyPi page a non-existent repo is listed instead of this one.

Sorry, I forgot to push the code. I pushed it now and made a 0.4.1 release that fixes the wrong url in the pypi metadata.


Entry not found in cache while deploying azure functions

<Please be sure to remove any private information before submitting.>
Repro steps:
<Enter steps to reproduce issue>
Action: azureFunctions.deploy
Error type: Error
Error Message: Entry not found in cache.
Version: 0.14.0
OS: win32

@dilipprasad can you give more detailed repro steps? Does this happen consistently or does deploy work for you most of the time?