There are no more files. - NAV 2018 CU2 DE

I got an error when running a new container with this parameter. First I thought it is because the database backup was not already converted to NAV 2018 CU2, but this backup is converted to nav 2018 cu2. It was nav 2016 before. Any idea?
PS C:\Users\vmadmin> docker run -e accept_eula=Y  -e username="vmadmin"
-e password="Password123"  -e databaseusername="sa"
-e databasepassword="Password123"  -v C:\temp:c:\run\my -e UseSSL=N
-h test18cu22  -e licensefile="c:\run\my\fin.flf"
--env ExitOnerror=N  --name test18cu22
-e bakfile=c:\run\my\test18cu1konv.bak `
microsoft/dynamics-nav:2018-cu2-de
Initializing...
Starting Container
Hostname is test18cu22
PublicDnsName is test18cu22
Using NavUserPassword Authentication
Starting Local SQL Server
Starting Internet Information Server
Using Database .bak file 'c:\run\my\test18cu1konv.bak'
Creating Self Signed Certificate
Self Signed Certificate Thumbprint 4BE0D1679B66C3349D608A53F2557EBD06C4292E
Modifying NAV Service Tier Config File with Instance Specific Settings
Starting NAV Service Tier
Using license file 'c:\run\my\fin.flf'
Import NAV License
No Dynamics NAV application has been mounted. Contact your system administrator.
at , C:\Run\SetupLicense.ps1: line 29
at , C:\Run\navstart.ps1: line 125
at , C:\Run\start.ps1: line 102
at , : line 1
TimeGenerated : 2/13/2018 3:38:58 PM
EntryType     : Warning
Message       : Type: Microsoft.Dynamics.Nav.Types.NavServerNotFoundException
SuppressMessage: False
DiagnosticsSuppress: False
SuppressExceptionCreatedEvent: False
FatalityScope: None
Message: No Dynamics NAV application has been mounted.
Contact your system administrator.
StackTrace:
at Microsoft.Dynamics.Nav.Management.ServerInstanceConnect
ion.DoOpenAdminConnection(IAdminService adminService)
at Microsoft.Dynamics.Nav.Management.ServerInstanceConnect
ion.EstablishAdminConnection()
at Microsoft.Dynamics.Nav.Management.ServerInstanceConnect
ion.InternalValidate()
at
Microsoft.Dynamics.Nav.Management.NavCommand.ProcessRecord()
Source: Microsoft.Dynamics.Nav.Management
HResult: -2146233088
----------------------------------
Type: System.ServiceModel.FaultException`1[[Microsoft.Dynamics.
Nav.Types.ServerFault, Microsoft.Dynamics.Nav.Types,
Version=<IP_ADDRESS>, Culture=neutral,
PublicKeyToken=31bf3856ad364e35]]
Action: http://www.microsoft.com/Dynamics/NAV/51/ServerFault
Message: No Dynamics NAV application has been mounted.
Contact your system administrator.
StackTrace:
              Server stack trace:
                 at System.ServiceModel.Channels.ServiceChannel.HandleReply
            (ProxyOperationRuntime operation, ProxyRpc& rpc)
                 at
            System.ServiceModel.Channels.ServiceChannel.Call(String
            action, Boolean oneway, ProxyOperationRuntime operation,
            Object[] ins, Object[] outs, TimeSpan timeout)
                 at System.ServiceModel.Channels.ServiceChannelProxy.Invoke
            Service(IMethodCallMessage methodCall, ProxyOperationRuntime
            operation)
                 at System.ServiceModel.Channels.ServiceChannelProxy.Invoke
            (IMessage message)

              Exception rethrown at [0]:
                 at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnM
            essage(IMessage reqMsg, IMessage retMsg)
                 at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke
            (MessageData& msgData, Int32 type)
                 at Microsoft.Dynamics.Nav.Types.IAdminService.OpenAdminCon
            nection(ConnectionRequest connectionRequest)
                 at Microsoft.Dynamics.Nav.Management.ServerInstanceConnect
            ion.DoOpenAdminConnection(IAdminService adminService)
            Source: mscorlib
            HResult: -2146233087

TimeGenerated : 2/13/2018 3:39:06 PM
EntryType     : Error
Message       : Server instance: NAV
Tenant ID:
User:
Type: System.IO.IOException
Message:
There are no more files.

StackTrace:
at System.IO.__Error.WinIOError(Int32 errorCode, String
maybeFullPath)
at System.IO.Directory.DeleteHelper(String fullPath,
String userPath, Boolean recursive, Boolean
throwOnTopLevelDirectoryNotFound)
at System.IO.Directory.Delete(String fullPath, String
userPath, Boolean recursive, Boolean checkHost)
at Microsoft.Dynamics.Nav.Runtime.TempPathHelper.RemovePat
h(String path)
Source: mscorlib
HResult: -2147024878

TimeGenerated : 2/13/2018 3:39:06 PM
EntryType     : Error
Message       : Server instance: NAV
Tenant ID:
User:
Type: System.IO.IOException
Message:
There are no more files.

StackTrace:
at System.IO.Directory.DeleteHelper(String fullPath,
String userPath, Boolean recursive, Boolean
throwOnTopLevelDirectoryNotFound)
at System.IO.Directory.Delete(String fullPath, String
userPath, Boolean recursive, Boolean checkHost)
at Microsoft.Dynamics.Nav.Runtime.TempPathHelper.RemovePat
h(String path)
Source: mscorlib
HResult: -2147024878

TimeGenerated : 2/13/2018 3:39:05 PM
EntryType     : Warning
Message       : Server instance: NAV
Tenant:
The service could not remove service principal names
because the service account could not be found in Active
Directory.
Account: NT AUTHORITY\SYSTEM
Service principal names:
DynamicsNAV/test18cu22:7045
DynamicsNAV/test18cu22:7045

Not really - you could try to spin up a SQL container and restore the database manually in that - and then run the NAV container using the SQL container as a database server.

the backup is working inside the container. The database is there after spinning up this container. Only the nav service tier could not start up. I can access it with the development environment and when I set up a different machine without backup file option and restore it after it, it is working too. Only when I pass it as an option the service tier setup fails. But not problem, I will do more investigation.
Thanks freddy
Rene
Outlook for Androidhttps://aka.ms/ghei36 herunterladen

From: Freddy Kristiansen<EMAIL_ADDRESS>Sent: Wednesday, February 14, 2018 7:09:58 AM
To: Microsoft/nav-docker
Cc: Rene Gayer; Author
Subject: Re: [Microsoft/nav-docker] There are no more files. - NAV 2018 CU2 DE (#160)
Not really - you could try to spin up a SQL container and restore the database manually in that - and then run the NAV container using the SQL container as a database server.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/nav-docker/issues/160#issuecomment-365506445, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AgiBnWzkKpvQHoCcH67zttDY5k2GDamKks5tUni2gaJpZM4SD3bx.

Strange.
In case you have a .bak file with this behavior, which can be shared, I would like to have a look to see what is happening. It might not be the last time we see this.

Hi, I think this should be possible, thank you! However, let me do some more test today. If these tests are not helpful, I will provide you a link to download today.
Do you know if someone already has done successfully runs with custom backup files?
I am not sure if it is the backup. I am also looking into issues with providing too many parameters which don’t make sense for this run. Like, I thought “sqlusername” and password would configure database authentication, but it is only used for external SQL server. Maybe some scripts are running into different sections when they passed, but don’t make sense for the remaining passed options.. ?!
/Rene
Von: Freddy Kristiansen<EMAIL_ADDRESS>Gesendet: Mittwoch, 14. Februar 2018 08:12
An: Microsoft/nav-docker<EMAIL_ADDRESS>Cc: Rene Gayer<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Betreff: Re: [Microsoft/nav-docker] There are no more files. - NAV 2018 CU2 DE (#160)
Strange.
In case you have a .bak file with this behavior, which can be shared, I would like to have a look to see what is happening. It might not be the last time we see this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/nav-docker/issues/160#issuecomment-365516037, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AgiBnQTyhATVcSA4LJkBXDiyPVKjzJ7eks5tUodFgaJpZM4SD3bx.

Yes, I have done that. My full run is a bit more complex, but the relevant params are
$name = "nsys17111"
$image = "2017-cu5-de"
$bakfile = "C:\temp\newsystem_170110100_CU05_TFE.bak"

$params = @("run",
    "--name", "$name",
    "--hostname", "$name",
    "-e", "accept_eula=y",
    "-e", "username=admin",
    "-e", "password=***",
    "-v", "c:\temp:c:\temp",
    "-e", "bakfile=$bakfile"
    "microsoft/dynamics-nav:$image"
)

Write-Host $params
& 'C:\Program Files\Docker\docker.exe' $params

For your reference the full script looks like this (it downloads the correct dlls from our TFS, creates a gMSA for that container and runs the container)
$name = "nsys17111"
$image = "2017-cu5-de"
$bakfile = "C:\temp\newsystem_170110100_CU05_TFE.bak"
$navrelease = "100"
$nsysrelease = "170110000"

[Reflection.Assembly]::LoadWithPartialName("System.Web") | Out-Null

$CodeServerPath = [System.Web.HttpUtility]::UrlEncode("$/RMT/Dynamics NAV 2017 DLL/$nsysrelease/Kumulativ")
$Url = "http://s00-tfs1.global.fum:8080/tfs/AxiansInfoma/RMT/_api/_versionControl/itemContentZipped?repositoryId=&path=$CodeServerPath"
$filename = "c:\temp\$name.$nsysrelease.zip"
$path = "c:\temp\$name.$nsysrelease"

if (Test-Path $filename) {
    Remove-Item $filename
}
if (Test-Path $path) {
    Remove-Item -Recurse $path
}

wget -Uri $Url -UseDefaultCredentials -OutFile $filename

Expand-Archive -Path $filename -DestinationPath $path

cmd /c C:\scripts\psexec.exe -u ***\*** -p ~ -h powershell "& c:\scripts\Remove-gMSA.ps1 -ContainerName $name" --% 2>&1

cmd /c C:\scripts\psexec.exe -u ***\*** -p ~ -h powershell "& c:\scripts\New-gMSA.ps1 -ContainerName $name" --% 2>&1

$params = @("run",
    "--rm",
    "--security-opt", "`"credentialspec=file://$name.json`"",
    "--name", "$name",
    "--hostname", "$name",
    "-e", "accept_eula=y",
    "-e", "accept_outdated=y",
    "--network", "MyTransparentNetwork",
    "-e", "auth=Windows",
    "-e", "username=admin",
    "-e", "password=***",
    "-e", "clickonce=y",
    "-e", "folders=`"c:\run\my=https://github.com/tfenster/nav-docker-samples/archive/grant-user-access.zip\nav-docker-samples-grant-user-access`"",
    "-e", "DevDomain=FUM-GLOBAL",
    "-e", "DevGroup=GRP_INFOMA_DEV_ALL",
    "-v", "c:\temp:c:\temp",
    "-v", "`"$path\kumulativ:C:\Program Files\Microsoft Dynamics NAV\$navrelease\Service\Add-ins\Infoma`"",
    "-e", "customWebSettings=`"Productname=newsystem`""
    "-e", "bakfile=$bakfile"
    "microsoft/dynamics-nav:$image"
)

Write-Host $params
& 'C:\Program Files\Docker\docker.exe' $params

Hi, „dmaster“ :D
Thank you for your reply.
Our bak file history is
. The database was nav 2016 before
. we made a backup
. tried to run a Docker container with it -> error, sure – server and database version did not match (feature request: [I know I can modify the scripts;] – option to run database conversion during spinning up a container)
. did database conversion and a new backup
. tried to run a Docker container with it again -> error, “…no more files”
I am not sure if it is the backup because it successfully restored. I deliberately used an easy combination of options. This scenario was the only reason why I posted it.
Maybe it is some combination which doesn’t work, and I thought maybe someone already had this issue.
I am still looking for it, and I will try your script as well.
/Rene
Von: Tobias Fenster<EMAIL_ADDRESS>Gesendet: Mittwoch, 14. Februar 2018 10:46
An: Microsoft/nav-docker<EMAIL_ADDRESS>Cc: Rene Gayer<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Betreff: Re: [Microsoft/nav-docker] There are no more files. - NAV 2018 CU2 DE (#160)
Yes, I have done that. My full run is a bit more complex, but the relevant params are
$name = "nsys17111"
$image = "2017-cu5-de"
$bakfile = "C:\temp\newsystem_170110100_CU05_TFE.bak"
$params = @("run",
"--name", "$name",

"--hostname", "$name",

"-e", "accept_eula=y",

"-e", "username=admin",

"-e", "password=***",

"-v", "c:\temp:c:\temp",

"-e", "bakfile=$bakfile"

"microsoft/dynamics-nav:$image"

)
Write-Host $params
& 'C:\Program Files\Docker\docker.exe' $params
For your reference the full script looks like this (it downloads the correct dlls from our TFS, creates a gMSA for that container and runs the container)
$name = "nsys17111"
$image = "2017-cu5-de"
$bakfile = "C:\temp\newsystem_170110100_CU05_TFE.bak"
$navrelease = "100"
$nsysrelease = "170110000"
[Reflection.Assembly]::LoadWithPartialName("System.Web") | Out-Null
$CodeServerPath = [System.Web.HttpUtility]::UrlEncode("$/RMT/Dynamics NAV 2017 DLL/$nsysrelease/Kumulativ")
$Url = "http://s00-tfs1.global.fum:8080/tfs/AxiansInfoma/RMT/_api/_versionControl/itemContentZipped?repositoryId=&path=$CodeServerPath"
$filename = "c:\temp$name.$nsysrelease.zip"
$path = "c:\temp$name.$nsysrelease"
if (Test-Path $filename) {
Remove-Item $filename

}
if (Test-Path $path) {
Remove-Item -Recurse $path

}
wget -Uri $Url -UseDefaultCredentials -OutFile $filename
Expand-Archive -Path $filename -DestinationPath $path
cmd /c C:\scripts\psexec.exe -u ** -p ~ -h powershell "& c:\scripts\Remove-gMSA.ps1 -ContainerName $name" --% 2>&1
cmd /c C:\scripts\psexec.exe -u ** -p ~ -h powershell "& c:\scripts\New-gMSA.ps1 -ContainerName $name" --% 2>&1
$params = @("run",
"--rm",

"--security-opt", "`"credentialspec=file://$name.json`"",

"--name", "$name",

"--hostname", "$name",

"-e", "accept_eula=y",

"-e", "accept_outdated=y",

"--network", "MyTransparentNetwork",

"-e", "auth=Windows",

"-e", "username=admin",

"-e", "password=***",

"-e", "clickonce=y",

"-e", "folders=`"c:\run\my=https://github.com/tfenster/nav-docker-samples/archive/grant-user-access.zip\nav-docker-samples-grant-user-access`"",

"-e", "DevDomain=FUM-GLOBAL",

"-e", "DevGroup=GRP_INFOMA_DEV_ALL",

"-v", "c:\temp:c:\temp",

"-v", "`"$path\kumulativ:C:\Program Files\Microsoft Dynamics NAV\$navrelease\Service\Add-ins\Infoma`"",

"-e", "customWebSettings=`"Productname=newsystem`""

"-e", "bakfile=$bakfile"

"microsoft/dynamics-nav:$image"

)
Write-Host $params
& 'C:\Program Files\Docker\docker.exe' $params
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/nav-docker/issues/160#issuecomment-365549933, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AgiBnaeDoy0Rh9zRpCeAMrPV05ddBRqhks5tUqtmgaJpZM4SD3bx.

I have the exact same issue on nav2018-cu2-nl with the following scenario:

Created container with the Cronus database (no bakfile parameter)
Some objects were imported, compiled etc.
Created a backup of this database.
Created a new container based on this bakfile.

Could you try to specify a license file with -e licensefile= ?

@freddydk I used our NAV 2018 dev license.

But was that specified in the launch of the container?

Yes!

Could you download the container log using the new get-navcontainereventlog and attach it?

Currently rerunning the scenario, I'll attach the event log asap.

Ok, so the "There are no more files" is an error which occurs under cleanup - meaning that the cause is in the eventlog further up - and for some reason, it doesn't always get printet - but you have to get it using the cmdlet.
So the headline "there are no more files" can be the heading for a lot of different errors, not the error itself.

Thanks Freddy, if I get the error again I will retrieve the event log and post my findings here.

thank you freddy ! sometimes it could be so easy...


primary display of bibliographic data

At present, for each bibliographic item, the display shows
AUTHOR
TITLE
JOURNAL (if of type 'article')
URL (if available)
As a result, it's easy to see which items are of type 'article', but not to distinguish other types. I would suggest showing
AUTHOR
TITLE
JOURNAL (if of type 'article'); PUBLISHER + YEAR (if of type 'book'); BOOKTITLE + YEAR (if of type 'incollection'); "preprint " + YEAR (if of type 'unpublished' or 'techreport')
URL (if available)

Is this note phase 4? We are now past due date for phase 3 and this seems a useful but minor additional requirement (and would fit into a wider discussion of presentation and configuration ...)

This is done. Config method changed.


Oksana Server Configuration

This PR adds the ability to configure how the Oksana server is configured. Currently, the only option available for configuration is the port number. The port number defaults to 8080 if no port number configuration is provided.
Here is an example of how to configure the port number that Oksana serves traffic:
func main() {
    o := oksana.New()

    // index handler
    o.GET("/", func(c *oksana.Context) error {
        return c.JSON(200, "Hello World!")
    })

    o.Start(oksana.Configuration{
        Port: "9999",
    })
}

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@d5d3b0b). Click here to learn what that means.
The diff coverage is 14.28%.

@@            Coverage Diff            @@
##             master       #1   +/-   ##
=========================================
  Coverage          ?   83.03%
=========================================
  Files             ?        6
  Lines             ?      112
  Branches          ?        0
=========================================
  Hits              ?       93
  Misses            ?       18
  Partials          ?        1

Impacted Files
Coverage Δ

oksana.go
73.33% <14.28%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d5d3b0b...e34d6d0. Read the comment docs.


Selection in Related Product doesn't redirect to that page

Describe the bug
Under the Related Products , Selection of the Product changes only the url but the product is yet the same,
To Reproduce
Steps to reproduce the behavior:

Go to the website and select any product.
Scroll down and under related products select any product.
You can see only the url is changing not the Product.

Expected behavior
The product shown also change accordingly but it is not happening and must be changed.
Screenshots
As we select the Tata Sappan Product (Product/4) the above url is changing but not the product (it's still
showing Good life product which is Product/3 ) and this has to be changed.

@MAVRICK-1 Please assign this issue to me.

@aditya-chari25 go ahead


Handling Jittery and Noisy Pose Data - Especially Hand Landmarks

Hi there,
First, I'd like to thank you for the fantastic work on this package. I've been processing video data using pose estimations from both MediaPipe and OpenPose, and while these tools generate good results, I frequently encounter issues with jittery and noisy data over time. This is particularly challenging when dealing with hand landmarks, where the data tends to be less stable and more prone to fluctuations throughout the video.
I noticed that your package includes a normalization function, and I was wondering if this function could be used to mitigate some of the jitter and noise in the pose data extracted from video frames. If so, could you provide some guidance on how best to apply it? Alternatively, if you have other recommendations for dealing with this issue in video processing, I'd greatly appreciate your advice.
Looking forward to your suggestions and any potential updates to the documentation that could help with this.
Thank you!

Hi! there is no jitter normalization function.
If you want to work with poses, and get more consistent results, consider post-processing using something like https://omnimotion.github.io/ - I came up with "how" (see https://github.com/qianqianwang68/omnimotion/issues/5) but never implemented it


Cast usize values to u64

In order to resolve compilation errors in my application, I needed to cast usize values to u64. I also encounter this error when compiling this repository locally with rustc 1.43.1 (8d69840ab 2020-05-04).

Thank you, this is because of multer breaking changes, please upgrade async-graphql to 1.12.18.


⚠ Bofrost.be has degraded performance

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

HTTP code: 200
Response time: 1656 ms

Resolved: Bofrost.be performance has improved in 2b7c601 after 11 minutes.


There should be a way of using password based encryption and not requiring to store the password variable in memory (in the HawkBuilder singleton instance)

This could be implemented by adding functionality to the Hawk class like resetPassword() and setPassword(String) when required, that would then set the password for the HawkBuilder instance. Or maybe put/get methods that take an extra password parameter.
This would be useful in apps that need to quickly put or get some secure info using Hawk and do not want the password used in encryption exposed to attackers (A rooted attacker could read the HawkBuilder object instance from memory and get the password variable value).

Assign it to me, I'll do it over the weekend.

We need to consider performance, instead of calling a reset password, hawk should do that out of box in the init phase. using password to generate key is very expensive cost.

no action is taken.


Tanndev-CI version links are still wrong

Bug Report
The relative url works fine when viewed in an issue, but not in email.
Screenshots

This issue is resolved in version 2.7.0-beta.1

This issue is resolved in version 2.6.3


refactor(vue/checkbox): use v-model:checked for two-way binding & reactivity context

refactor v-model to v-model:checked for two-way binding
use useMachine context to solve reactivity issues

Thanks


layouts with queries

Currently we can't write queries in our layout components because gatsby doesn't support this.

waiting for https://github.com/gatsbyjs/gatsby/pull/1503

using a fork while waiting for merge.


Calculate scale-factors

Estimate the biggest scale factor that we can put on our best computer: this will be your reference scale factor, e.g. 1.0, and then we should have 3 smaller scale factors, e.g., at 0.1, 0.2, and 0.5 of the full-size in order to evaluate the evolution of the performance

This can be defined with the parameter --scale, when using the ./dsdgen commands.
For example:
./dsdgen -scale 1 -dir ./tmp -suffix .csv -delimiter "^" -parallel 4 -child 1 -quiet n -terminate n &


Q1 2025: Joe's Goals

You'd think Q5 comes after Q4, but actually it's this. And 'this' is a plan that, as usual, I will continue to update throughout the quarter as I tick things off, plan things, and so on.
So, what am I planning to do in Q1 2025? Well...
Better beta programs

[ ] Figure out, and start using, a method for beta waitlists
[ ] Create an email flow to support users on beta programs
[ ] Plan out and create a smooth comms pipeline that goes Beta -> Launch
[ ] Use all of the above to support the launch of error tracking
[ ] Use all of the above to support the launch of messaging
[ ] Roll beta promotion into weekly digest (below)

Optimize email marketing for cross-sell (Joe)

[ ] Completely rebuild all email flows to better focus on cross-sell
[ ] In particular focus on pushing replay adoption by D5
[ ] Launch the weekly digest to promote cross-product activation
[ ] Create an email onboarding branch to unblock users with ingestion issues by D28
[ ] Strongly focus the startup programs on encouraging warehouse adoption
[ ] Re-jig how case studies are used to bring out the cross-sell angle

Sidequest: Stay on top of paid ads

[ ] Continue managing our digital agency and just generally plug the gap here
[ ] Make sure we have a tie-in campaign to support the billboard ads
[ ] Hire an Ads Person With Good Taste

Sidequest: Plan out future hiring for the Words & Pictures team

[ ] Onboard Kevan, and The Ads Person With Good Taste
[ ] Plan the next hires. A PMM? A Startup specialist? Boring Partnership Manager? Email Marketer?

Sidequest: Don't get distracted by boring partnerships

[ ] Do the AWS partnership and basically nothing else unless it's obviously amazing
[x] Good lord, partnerships are so boring

Personal goals and Q4 Feedback
I collected some great 360 feedback in Q4 which I detailed here. As a personal goal I want to continue focusing on some of this stuff in order to improve. Quick summary below to avoid repeating the previous issue, while still keeping it visible and current.
Keep doing
Things that people liked and which they encouraged me on were...

Working across a lot of areas. There was feedback that people appreciate the breadth and volume of my work.
Bringing organization to chaos. It's scary, but apparently I'm one of the more organized people?
Leadership. There was feedback that people like my management style and hiring plans, so keep that up.
Writing. It gets better the braver and weirder I make it, apparently.

Stop doing
Things that people gave constructive feedback on were...

Avoid being so noisy in projects. I had feedback that I don't give enough space for others, which I really want to solve for.
Worry less. That's easier said than done, but I can at least not let my anxieties be infectious, right?

Looks good!

Missed opportunity to call these Joals?
Better beta programs -> Betah programs?


A11y_AzureDataStudioSQL_Add Database reference_System Database_ScreenReader:Voice Over does not announces required when user navigates on Database name edit box with the help of tab key.

“Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.”
GitHubTags: #A11yMAS;#A11yTCS;#A11ySev2;#SH_AzureDataStudioSQL-MAC-Feb2021;#SQL Azure Data Studio;#MAC;#FTP;#DesktopApp;#WCAG3.3.1;#VoiceOver;#AINotInScope;
Environment Details:
Application Name: Azure Data Studio
Mac OS Version: Big Sur Version 11.2.2
Screen reader: Voice Over
Repro Steps:

Launch the application-Azure Database Project and install extension SQL Database Projects.
Navigate to SQL Database Project Home Screen with heading "Projects".
Tab to connections select your server and connect to it.
Few databases will appear under your connection then right click on any database
Tab till "Create project from database" and hit enter.
New database project will get created under "Projects" tab and tab till "Database references"
Right Click and hit enter on "Add Database references".
Select "System Database" radio button.
Start the Voice Over,
Navigate to Database name edit box with Capslock + Right Arrow key or Tab and check the result.

Actual:
Voice Over does not announces required when user navigates on Database name edit box with the help of tab key .
Similar issue is observed in below scenarios:
Add Database reference- Data tier application
Add Database reference- Projects
Expected:
Voice Over should announce required when user navigates on Database name edit box with the help of tab key .
User Impact:
Screenreader user will not able to know that it is a required field.

Verified the bug in the environment
Application Name: Azure Data Studio
macOS: Ventura 13.2
Issue is fixed and does not reproduced. Please find the not repro attachment below.
Screen Recording (3).webm
Github Tags:#Closed;


History of query results / tabs for each

@depombo:

This allows showing the result of a query made of multiple queries and visualizing the tables by clicking on it.

@aguillenv:

So we have small tasks here:
[ ] Add tabs to the editor and keep track of the result for each one
[ ] When clicking on table names (or a button close to it) open a new tab with the generated select query
[ ] Update install/uninstall behaviour to open a new tab
[ ] Keep the history of queries+results obtained per tab per session

@dfellis:

Shouldn't we open a new issue in the monorepo instead of continuing to use this one?
@aguillenv how is your fourth checklist item different from your first one?

@aguillenv:

Shouldn't we open a new issue in the monorepo instead of continuing to use this one?

Oh, I thought it was already in the monorepo. I'll transfer the issue.

@aguillenv how is your fourth checklist item different from your first one?

Add tabs to the editor and keep track of the result for each one

This one will just to introduce tabs to the editor. Each tab will show one result table of what you executed in each one.

Keep the history of queries+results obtained per tab per session

This one will keep the history per tab of all queries executed in it. Maybe with a UI like we talked about with some collapsible components.
With just tabs we do not have "history", right?


switch validation error: "type: NO" converted by yaml parser to "type: False"

If you have type: NO (for normally open) in a switch config, the yaml processor parses NO as the word "no" which it converts to boolean False. (Entering type: "NO" fixes it.)
So we either need to do a post validation fix to convert type=False to type="NO", or we need to update the validator enum() to fix it.. something like that

fixed


Remove ansible-toolset

ansible-toolset doesn't seem to exist anymore, so I'm removing it from the awesome tools list.

Thanks a lot! 👍


Remove border from images

Hi, how can i remove the border around the image ?

Hi, images don't have borders, maybe you are referring to a default separatorColor of the Grid?

Hi, images don't have borders, maybe you are referring to a default separatorColor of the Grid?


added cheatsheet translations: data-visualization in Chinese (Simplified, zh_CN)

Thank you @taoruicn. To help me publish this, can you please add a pdf copy of the cheatsheet. Also, do you have a twitter account that I can mention to thank you in public for the translation?

Sorry I do not have a twitter account.

Thank you @taoruicn. I've added the cheatsheet to https://www.rstudio.com/resources/cheatsheets/. Please let me know if you'd like me to use your full name on the website to give you credit. I'll be happy to change it. For now, I've used you github account name.


Automated cherry pick of #9183: fix(region): inspect invalid guest template

Cherry pick of #9183 on release/3.6.
#9183: fix(region): inspect invalid guest template

Codecov Report

Merging #9185 (5602db8) into release/3.6 (b9d30c0) will increase coverage by 11.68%.
The diff coverage is 1.96%.

@@               Coverage Diff                @@
##           release/3.6    #9185       +/-   ##
================================================
+ Coverage         5.86%   17.54%   +11.68%
================================================
  Files              828       90      -738
  Lines           129133     9009   -120124
================================================
- Hits              7577     1581     -5996
+ Misses          120876     7253   -113623
+ Partials           680      175      -505

Flag
Coverage Δ

aFlag
17.54% <1.96%> (+11.68%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/monitor/alerting/conditions/nodataquery.go
0.99% <0.00%> (ø)

pkg/monitor/alerting/conditions/suggestquery.go
2.00% <2.00%> (ø)

pkg/lbagent/models/modelsets.go

pkg/compute/models/scheduledtask_label.go

pkg/hostman/monitor/qmp.go

pkg/compute/models/dns_zones.go

pkg/compute/models/scaling_activity.go

pkg/compute/models/helper.go

pkg/cloudcommon/db/resourcebase.go

pkg/compute/models/guesttemplate_resource.go

... and 685 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a24d3c4...5602db8. Read the comment docs.


Download Response Not working

The download response isn't working as expected, when the download is initiated, the page goes blank.
the response is expected to return the send method, but does not.
here is how i used the response
$fname = $storepath.$order->order_reference . "_ticket.pdf";
Services::response()->download($fname, NULL);
so i altered the download method to return return $response->send(); instead of return $response;
i initially thought the send would be returned from the codeigniter class.

Why don't use this :
Services::response()->download($fname, NULL)->send();
It's logical for me to use special method to send the result. Since you can use several methods on the DownloadResponse.

Why don't use this :
Services::response()->download($fname, NULL)->send();
It's logical for me to use special method to send the result. Since you can use several methods on the DownloadResponse.

Have you returned the DownloadResponse class?
Please implement as follows.
<?php namespace App\Controllers;

use CodeIgniter\Controller;
use CodeIgniter\Config\Services;

class Sample extends Controller
{
    public function donwload()
    {
        $fname = __FILE__;
        return Services::response()->download($fname, NULL);
    }
}

@ytetsuro you make a point. But then a simple download helper would be nice.

Yes, the response must be returned. This gives it a chance to run through any filters before being sent.
I'll double check the docs on that and make sure they reflect the current process since the recent change.


Update README.md

This change reflects the default definition.yaml that is output for the azure-simple template.

#1142

LGTM


Enforce requested clustering column order on REST API

Fixes #1841
Checklist

[ ] Changes manually tested
[x] Automated Tests added/updated
[ ] Documentation added/updated
[x] CLA Signed: DataStax CLA

From quick look I think partition key columns would also have same issue. Could add second IT method, or make this one use 2 partition and 2 clustering keys in "wrong" order (in column definitions).

From quick look I think partition key columns would also have same issue. Could add second IT method, or make this one use 2 partition and 2 clustering keys in "wrong" order (in column definitions).

This is not an issue as ordering of partition key columns has no siginficance semantically - they are hashed together and order doesn't matter.

Ah right. So may just look unexpected (ordering for creation statement), but functionally does not matter. Makes sense.


Fix sholl_frequency for NA neurite_type

With this change, sholl_frequency returns an empty list for a neurite_type that is not present in the morphology.
Fixes #987

Codecov Report

Merging #990 (13646db) into master (d120263) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master      #990   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           36        36
  Lines         2332      2334    +2
=========================================
+ Hits          2332      2334    +2

Good point, I added this case in the Note section of the docstring.

LGTM!


docs(understanding-deis): document database lifecycle

closes deis/postgres#34

The backup and restore doc is still TODO in master.

I don't know enough about minio to comment on how minio should be properly backed up to persistent disk, so I left that out in this PR.

Object storage should generally be transparent to the process of restoring a postgres backup, no?

@slack yes, generally it is completely transparent. The user doesn't need to know anything about the underlying object storage layer we provide unless they swap it out with S3.


”Brâncovenești”, ”Idicel”, ”Idicel-Pădure”, ”Săcalu de Pădure”, ”Vălenii de Mureș” are listed in the drop-down menu

Description:
When user writes ”Brâncovenești”, ”Idicel”, ”Idicel-Pădure”, ”Săcalu de Pădure”, ”Vălenii de Mureș” the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Brâncovenești"

Expected results
The location appears in the drop-down menu as "Sat Brâncovenești, MUREȘ (Brâncovenești)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Idicel"

Expected results
The location appears in the drop-down menu as "Sat Idicel, MUREȘ (Brâncovenești)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Idicel-Pădure"

Expected results
The location appears in the drop-down menu as "Sat Idicel-Pădure, MUREȘ (Brâncovenești)".

Step 6
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 7
Write in the search bar "Săcalu de Pădure"

Expected results
The location appears in the drop-down menu as "Sat Săcalu de Pădure, MUREȘ (Brâncovenești)".

Step 8
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 9
Write in the search bar "Vălenii de Mureș"

Expected results
The location appears in the drop-down menu as "Sat Vălenii de Mureș, MUREȘ (Brâncovenești)".


An exception has been thrown during the rendering of a template ("Warning: Undefined array key "_builder"").

When I try to use the {{ gotenberg_asset('public/...') }} I get this error
An exception has been thrown during the rendering of a template ("Warning: Undefined array key "_builder"").
I have no idea what to do. I just installed the bundle, it works with url, i tried with html, works without assets, now breaks when loading assets.
Any help ?
Symfony 6.4.15, and latest gotenberg bundle

Hi, could you provide more context? or code?
I tried to reproduce but I don't get the same exception.
To help you out, first, have you configured assets_directory in your configuration file?
By default, the assets are fetched from the assets folder.
Documentation on assets
Documentation on configuration
If you haven't set this up, you can fetch an image located in the public folder by doing this  directly in your Twig template.
<img  src="{{ gotenberg_asset('../public/img/logo.png') }}"/>


[BUG] How to deal with crashed volumes?

Describe the bug
Sometimes my attached volumes crash (I guess?) and pods stay running and all operations throw an I/O error.
I don't know why they crash as there is very little information, and don't know what to do when this happens.
I suppose longhorn should deal with this but it isn't happening, as pods stay running with the crashed volume.
To Reproduce
No idea.
Expected behavior
Longhorn either acts upon this issue automatically or a clear way to fix this.
Support bundle for troubleshooting
Can send privately.
Environment

Longhorn version: 1.6.2
Impacted volume (PV):
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): Helm
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: k3s 1.30

Number of control plane nodes in the cluster: 3
Number of worker nodes in the cluster: 0

Node config

OS type and version:
Kernel version:
CPU per node:
Memory per node:
Disk type (e.g. SSD/NVMe/HDD):
Network bandwidth between the nodes (Gbps):

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
Number of Longhorn volumes in the cluster:

Additional context

I guess doing a livenessProbe that checks that all mounted volumes are writable is a workaround.

Also to add, when this happens a full scale down + scale up is necessary, to force longhorn to remove and re-mount the volume. (encrypted volumes)

Longhorn should restart all workload pods if it detects a volume crash when https://longhorn.io/docs/1.6.2/references/settings/#automatically-delete-workload-pod-when-the-volume-is-detached-unexpectedly is enabled. Is it enabled in your environment? Note the caveat that the pod must have a controller (so Longhorn doesn't delete workload pods that can never come back).

Longhorn should restart all workload pods if it detects a volume crash when https://longhorn.io/docs/1.6.2/references/settings/#automatically-delete-workload-pod-when-the-volume-is-detached-unexpectedly is enabled. Is it enabled in your environment? Note the caveat that the pod must have a controller (so Longhorn doesn't delete workload pods that can never come back).

It is enabled yes, and the pod is on a deployment. But in this scenario longhorn does not delete the pod and even a manual pod delete does not fix the issue. Only a scale down and scale up

Can we have a support bundle to check the details? Maybe the volumes aren't crashing (at least in the way Longhorn is watching for)?

Can we have a support bundle to check the details? Maybe the volumes aren't crashing (at least in the way Longhorn is watching for)?

For sure! How can i send it privately?

Please send it to<EMAIL_ADDRESS>Thanks!

Please send it to<EMAIL_ADDRESS>Thanks!

Thanks, sent. Subject -> Issue #9085 - Support bundle

Got it, will take a look when time allows today.

Analysis
Logs included with node, namespace, and pod names removed.
We don't have all the logs we would want, but I think we have enough to piece together what is happening here. TLDR, there seems to be a race involving the auto-delete-pod-when-volume-detached-unexpectedly functionality. I'm not sure yet whether it can only affect encrypted volumes.
I found one volume that is probably demonstrating the behavior @davidfrickert described.
At 2024-07-24T22:43:51Z its engine crashed.
2024-07-25T00:43:51.969968559+02:00 [pvc-c5052541-db99-480e-9c96-17df67d839a1-e-b901152a] time="2024-07-24T22:43:51Z" level=error msg="R/W Timeout. No response received in 8s" func="dataconn.(*Client).loop" file="client.go:154"

At 2024-07-24T22:44:14Z it was finished reattaching to the appropriate node.
2024-07-25T00:44:14.862406218+02:00 [pvc-c5052541-db99-480e-9c96-17df67d839a1-e-b901152a] time="2024-07-24T22:44:14Z" level=info msg="Starting with replicas [\"tcp://<IP_ADDRESS>:10153\"]" func=cmd.startController file="controller.go:196"
2024-07-25T00:44:16.970613210+02:00 [longhorn-instance-manager] time="2024-07-24T22:44:16Z" level=info msg="Process pvc-c5052541-db99-480e-9c96-17df67d839a1-e-b901152a has started at localhost:10041" func="process.(*GRPCHealthChecker).WaitForRunning" file="healthchecker.go:33"

Its remountRequestedAt field was set to 2024-07-24T22:44:13Z. This looks appropriate for the situation.
We don't have longhorn-manager logs, but longhorn-csi-plugin logs can help us understand what happened next.
At 2024-07-24T22:41:41Z (before the incident) it was staged and published for the pod with UID ee22bee4-e011-4790-acbe-281515ee3fb3.
2024-07-25T00:41:35.383281870+02:00 time="2024-07-24T22:41:35Z" level=info msg="NodeStageVolume: req: {\"secrets\":\"***stripped***\",\"staging_target_path\":\"/var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/87776498c5cc3d46c6dd8d81ec2762916577ddb84179bd951a126f2158f8b904/globalmount\",\"volume_capability\":{\"AccessType\":{\"Mount\":{\"fs_type\":\"ext4\"}},\"access_mode\":{\"mode\":1}},\"volume_context\":{\"encrypted\":\"true\",\"fromBackup\":\"\",\"nodeSelector\":\"storage\",\"numberOfReplicas\":\"1\",\"staleReplicaTimeout\":\"2880\",\"storage.kubernetes.io/csiProvisionerIdentity\":\"1711492103312-8081-driver.longhorn.io\"},\"volume_id\":\"pvc-c5052541-db99-480e-9c96-17df67d839a1\"}" func=csi.logGRPC file="server.go:132"
2024-07-25T00:41:36.982083823+02:00 time="2024-07-24T22:41:36Z" level=info msg="NodeStageVolume: rsp: {}" func=csi.logGRPC file="server.go:141"
2024-07-25T00:41:37.025636070+02:00 time="2024-07-24T22:41:37Z" level=info msg="NodePublishVolume: req: {\"secrets\":\"***stripped***\",\"staging_target_path\":\"/var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/87776498c5cc3d46c6dd8d81ec2762916577ddb84179bd951a126f2158f8b904/globalmount\",\"target_path\":\"/var/lib/kubelet/pods/ee22bee4-e011-4790-acbe-281515ee3fb3/volumes/kubernetes.io~csi/pvc-c5052541-db99-480e-9c96-17df67d839a1/mount\",\"volume_capability\":{\"AccessType\":{\"Mount\":{\"fs_type\":\"ext4\"}},\"access_mode\":{\"mode\":1}},\"volume_context\":{\"csi.storage.k8s.io/ephemeral\":\"false\",\"csi.storage.k8s.io/pod.name\":\"some-pod-5cf5d746d-btccv\",\"csi.storage.k8s.io/pod.namespace\":\"some-namespace\",\"csi.storage.k8s.io/pod.uid\":\"ee22bee4-e011-4790-acbe-281515ee3fb3\",\"csi.storage.k8s.io/serviceAccount.name\":\"default\",\"encrypted\":\"true\",\"fromBackup\":\"\",\"nodeSelector\":\"storage\",\"numberOfReplicas\":\"1\",\"staleReplicaTimeout\":\"2880\",\"storage.kubernetes.io/csiProvisionerIdentity\":\"1711492103312-8081-driver.longhorn.io\"},\"volume_id\":\"pvc-c5052541-db99-480e-9c96-17df67d839a1\"}" func=csi.logGRPC file="server.go:132"
2024-07-25T00:41:41.612730807+02:00 time="2024-07-24T22:41:41Z" level=info msg="NodePublishVolume: rsp: {}" func=csi.logGRPC file="server.go:141"

At 2024-07-24T22:44:24Z, we were asked to publish it for a different pod with UID fbfcd704-5026-4d2f-bc97-414f1508e1bf. Since the global mount point was corrupted (after volume crash), we manually unstaged and staged it before publishing. There are some error logs indicating that this did not work correctly, but apparently we still returned success.
2024-07-25T00:44:24.992526017+02:00 time="2024-07-24T22:44:24Z" level=info msg="NodePublishVolume: req: {\"secrets\":\"***stripped***\",\"staging_target_path\":\"/var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/87776498c5cc3d46c6dd8d81ec2762916577ddb84179bd951a126f2158f8b904/globalmount\",\"target_path\":\"/var/lib/kubelet/pods/fbfcd704-5026-4d2f-bc97-414f1508e1bf/volumes/kubernetes.io~csi/pvc-c5052541-db99-480e-9c96-17df67d839a1/mount\",\"volume_capability\":{\"AccessType\":{\"Mount\":{\"fs_type\":\"ext4\"}},\"access_mode\":{\"mode\":1}},\"volume_context\":{\"csi.storage.k8s.io/ephemeral\":\"false\",\"csi.storage.k8s.io/pod.name\":\"some-pod-5cf5d746d-8thzc\",\"csi.storage.k8s.io/pod.namespace\":\"some-namespace\",\"csi.storage.k8s.io/pod.uid\":\"fbfcd704-5026-4d2f-bc97-414f1508e1bf\",\"csi.storage.k8s.io/serviceAccount.name\":\"default\",\"encrypted\":\"true\",\"fromBackup\":\"\",\"nodeSelector\":\"storage\",\"numberOfReplicas\":\"1\",\"staleReplicaTimeout\":\"2880\",\"storage.kubernetes.io/csiProvisionerIdentity\":\"1711492103312-8081-driver.longhorn.io\"},\"volume_id\":\"pvc-c5052541-db99-480e-9c96-17df67d839a1\"}" func=csi.logGRPC file="server.go:132"
2024-07-25T00:44:24.992544918+02:00 time="2024-07-24T22:44:24Z" level=info msg="NodePublishVolume is called with req volume_id:\"pvc-c5052541-db99-480e-9c96-17df67d839a1\" staging_target_path:\"/var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/87776498c5cc3d46c6dd8d81ec2762916577ddb84179bd951a126f2158f8b904/globalmount\" target_path:\"/var/lib/kubelet/pods/fbfcd704-5026-4d2f-bc97-414f1508e1bf/volumes/kubernetes.io~csi/pvc-c5052541-db99-480e-9c96-17df67d839a1/mount\" volume_capability:<mount:<fs_type:\"ext4\" > access_mode:<mode:SINGLE_NODE_WRITER > > secrets:<key:\"CRYPTO_KEY_PROVIDER\" value:\"secret\" > secrets:<key:\"CRYPTO_KEY_VALUE\" value:\"YBXxrKKeNxEENvNVbiodAlVfT\" > volume_context:<key:\"csi.storage.k8s.io/ephemeral\" value:\"false\" > volume_context:<key:\"csi.storage.k8s.io/pod.name\" value:\"some-pod-5cf5d746d-8thzc\" > volume_context:<key:\"csi.storage.k8s.io/pod.namespace\" value:\"some-namespace\" > volume_context:<key:\"csi.storage.k8s.io/pod.uid\" value:\"fbfcd704-5026-4d2f-bc97-414f1508e1bf\" > volume_context:<key:\"csi.storage.k8s.io/serviceAccount.name\" value:\"default\" > volume_context:<key:\"encrypted\" value:\"true\" > volume_context:<key:\"fromBackup\" value:\"\" > volume_context:<key:\"nodeSelector\" value:\"storage\" > volume_context:<key:\"numberOfReplicas\" value:\"1\" > volume_context:<key:\"staleReplicaTimeout\" value:\"2880\" > volume_context:<key:\"storage.kubernetes.io/csiProvisionerIdentity\" value:\"1711492103312-8081-driver.longhorn.io\" > " func="csi.(*NodeServer).NodePublishVolume" file="node_server.go:84" component=csi-node-server function=NodePublishVolume
2024-07-25T00:44:25.030050353+02:00 time="2024-07-24T22:44:25Z" level=warning msg="Staging target path /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/87776498c5cc3d46c6dd8d81ec2762916577ddb84179bd951a126f2158f8b904/globalmount is no longer valid for volume pvc-c5052541-db99-480e-9c96-17df67d839a1" func="csi.(*NodeServer).NodePublishVolume" file="node_server.go:159" component=csi-node-server error="<nil>" function=NodePublishVolume
2024-07-25T00:44:25.030058730+02:00 time="2024-07-24T22:44:25Z" level=warning msg="Calling NodeUnstageVolume for volume pvc-c5052541-db99-480e-9c96-17df67d839a1" func="csi.(*NodeServer).NodePublishVolume" file="node_server.go:161" component=csi-node-server function=NodePublishVolume
2024-07-25T00:44:25.014099719+02:00 time="2024-07-24T22:44:25Z" level=info msg="Volume pvc-c5052541-db99-480e-9c96-17df67d839a1 using user and longhorn provided ext4 fs creation params: -b4096" func="csi.(*NodeServer).getMounter" file="node_server.go:841"
2024-07-25T00:44:25.030050353+02:00 time="2024-07-24T22:44:25Z" level=warning msg="Staging target path /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/87776498c5cc3d46c6dd8d81ec2762916577ddb84179bd951a126f2158f8b904/globalmount is no longer valid for volume pvc-c5052541-db99-480e-9c96-17df67d839a1" func="csi.(*NodeServer).NodePublishVolume" file="node_server.go:159" component=csi-node-server error="<nil>" function=NodePublishVolume
2024-07-25T00:44:25.030058730+02:00 time="2024-07-24T22:44:25Z" level=warning msg="Calling NodeUnstageVolume for volume pvc-c5052541-db99-480e-9c96-17df67d839a1" func="csi.(*NodeServer).NodePublishVolume" file="node_server.go:161" component=csi-node-server function=NodePublishVolume
2024-07-25T00:44:25.030061458+02:00 time="2024-07-24T22:44:25Z" level=info msg="NodeUnstageVolume is called with req volume_id:\"pvc-c5052541-db99-480e-9c96-17df67d839a1\" staging_target_path:\"/var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/87776498c5cc3d46c6dd8d81ec2762916577ddb84179bd951a126f2158f8b904/globalmount\" " func="csi.(*NodeServer).NodeUnstageVolume" file="node_server.go:553" component=csi-node-server function=NodeUnstageVolume
2024-07-25T00:44:25.051886148+02:00 time="2024-07-24T22:44:25Z" level=info msg="Trying to cleanup mount point /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/87776498c5cc3d46c6dd8d81ec2762916577ddb84179bd951a126f2158f8b904/globalmount/pvc-c5052541-db99-480e-9c96-17df67d839a1" func=csi.cleanupMountPoint file="util.go:371"
2024-07-25T00:44:25.051901900+02:00 time="2024-07-24T22:44:25Z" level=info msg="Trying to force unmount potential mount point /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/87776498c5cc3d46c6dd8d81ec2762916577ddb84179bd951a126f2158f8b904/globalmount/pvc-c5052541-db99-480e-9c96-17df67d839a1" func=csi.unmount file="util.go:349"
2024-07-25T00:44:25.059852839+02:00 time="2024-07-24T22:44:25Z" level=info msg="No need for unmount not a mount point /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/87776498c5cc3d46c6dd8d81ec2762916577ddb84179bd951a126f2158f8b904/globalmount/pvc-c5052541-db99-480e-9c96-17df67d839a1" func=csi.unmount file="util.go:361"
2024-07-25T00:44:25.059870872+02:00 time="2024-07-24T22:44:25Z" level=info msg="Cleaned up mount point /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/87776498c5cc3d46c6dd8d81ec2762916577ddb84179bd951a126f2158f8b904/globalmount/pvc-c5052541-db99-480e-9c96-17df67d839a1" func=csi.cleanupMountPoint file="util.go:377"
2024-07-25T00:44:25.059906431+02:00 W0724 22:44:25.059825    5394 mount_helper_common.go:34] Warning: mount cleanup skipped because path does not exist: /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/87776498c5cc3d46c6dd8d81ec2762916577ddb84179bd951a126f2158f8b904/globalmount/pvc-c5052541-db99-480e-9c96-17df67d839a1
2024-07-25T00:44:25.075699269+02:00 time="2024-07-24T22:44:25Z" level=info msg="Volume pvc-c5052541-db99-480e-9c96-17df67d839a1 closing active crypto device /dev/mapper/pvc-c5052541-db99-480e-9c96-17df67d839a1" func="csi.(*NodeServer).NodeUnstageVolume" file="node_server.go:594" component=csi-node-server function=NodeUnstageVolume
2024-07-25T00:44:25.082249893+02:00 time="2024-07-24T22:44:25Z" level=info msg="Closing LUKS device pvc-c5052541-db99-480e-9c96-17df67d839a1" func=crypto.CloseVolume file="crypto.go:126"
2024-07-25T00:44:25.101684350+02:00 time="2024-07-24T22:44:25Z" level=warning msg="Calling NodeStageVolume for volume pvc-c5052541-db99-480e-9c96-17df67d839a1" func="csi.(*NodeServer).NodePublishVolume" file="node_server.go:167" component=csi-node-server function=NodePublishVolume
2024-07-25T00:44:25.101709031+02:00 time="2024-07-24T22:44:25Z" level=info msg="NodeStageVolume is called with req volume_id:\"pvc-c5052541-db99-480e-9c96-17df67d839a1\" staging_target_path:\"/var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/87776498c5cc3d46c6dd8d81ec2762916577ddb84179bd951a126f2158f8b904/globalmount\" volume_capability:<mount:<fs_type:\"ext4\" > access_mode:<mode:SINGLE_NODE_WRITER > > secrets:<key:\"CRYPTO_KEY_PROVIDER\" value:\"secret\" > secrets:<key:\"CRYPTO_KEY_VALUE\" value:\"YBXxrKKeNxEENvNVbiodAlVfT\" > volume_context:<key:\"csi.storage.k8s.io/ephemeral\" value:\"false\" > volume_context:<key:\"csi.storage.k8s.io/pod.name\" value:\"some-pod-5cf5d746d-8thzc\" > volume_context:<key:\"csi.storage.k8s.io/pod.namespace\" value:\"some-namespace\" > volume_context:<key:\"csi.storage.k8s.io/pod.uid\" value:\"fbfcd704-5026-4d2f-bc97-414f1508e1bf\" > volume_context:<key:\"csi.storage.k8s.io/serviceAccount.name\" value:\"default\" > volume_context:<key:\"encrypted\" value:\"true\" > volume_context:<key:\"fromBackup\" value:\"\" > volume_context:<key:\"nodeSelector\" value:\"storage\" > volume_context:<key:\"numberOfReplicas\" value:\"1\" > volume_context:<key:\"staleReplicaTimeout\" value:\"2880\" > volume_context:<key:\"storage.kubernetes.io/csiProvisionerIdentity\" value:\"1711492103312-8081-driver.longhorn.io\" > " func="csi.(*NodeServer).NodeStageVolume" file="node_server.go:376" component=csi-node-server function=NodeStageVolume
2024-07-25T00:44:25.134830433+02:00 time="2024-07-24T22:44:25Z" level=info msg="Volume pvc-c5052541-db99-480e-9c96-17df67d839a1 using user and longhorn provided ext4 fs creation params: -b4096" func="csi.(*NodeServer).getMounter" file="node_server.go:841"
2024-07-25T00:44:25.971419628+02:00 time="2024-07-24T22:44:25Z" level=info msg="Volume pvc-c5052541-db99-480e-9c96-17df67d839a1 device /dev/longhorn/pvc-c5052541-db99-480e-9c96-17df67d839a1 contains filesystem of format crypto_LUKS" func="csi.(*NodeServer).NodeStageVolume" file="node_server.go:462" component=csi-node-server function=NodeStageVolume
2024-07-25T00:44:25.971454040+02:00 time="2024-07-24T22:44:25Z" level=info msg="Volume pvc-c5052541-db99-480e-9c96-17df67d839a1 requires crypto device /dev/mapper/pvc-c5052541-db99-480e-9c96-17df67d839a1" func="csi.(*NodeServer).NodeStageVolume" file="node_server.go:490" component=csi-node-server function=NodeStageVolume
2024-07-25T00:44:25.991091784+02:00 time="2024-07-24T22:44:25Z" level=info msg="Device /dev/longhorn/pvc-c5052541-db99-480e-9c96-17df67d839a1 is already opened at /dev/mapper/pvc-c5052541-db99-480e-9c96-17df67d839a1" func=crypto.OpenVolume file="crypto.go:100"
2024-07-25T00:44:25.994747077+02:00 time="2024-07-24T22:44:25Z" level=info msg="Formatting device /dev/mapper/pvc-c5052541-db99-480e-9c96-17df67d839a1 with fsType ext4 and mounting at /var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/87776498c5cc3d46c6dd8d81ec2762916577ddb84179bd951a126f2158f8b904/globalmount with mount flags []" func="csi.(*NodeServer).nodeStageMountVolume" file="node_server.go:313" component=csi-node-server function=NodePublishVolume
2024-07-25T00:44:26.016767886+02:00 I0724 22:44:26.016472    5394 mount_linux.go:452] `fsck` error fsck from util-linux 2.37.4
2024-07-25T00:44:26.016798630+02:00 /dev/mapper/pvc-c5052541-db99-480e-9c96-17df67d839a1 is mounted.
2024-07-25T00:44:26.016804541+02:00 e2fsck: Cannot continue, aborting.
2024-07-25T00:44:26.016808408+02:00
2024-07-25T00:44:26.016812328+02:00
2024-07-25T00:44:26.125601329+02:00 time="2024-07-24T22:44:26Z" level=info msg="Mounted volume pvc-c5052541-db99-480e-9c96-17df67d839a1 on node some-node does not require filesystem resize" func="csi.(*NodeServer).NodeStageVolume" file="node_server.go:543" component=csi-node-server function=NodeStageVolume
2024-07-25T00:44:26.125735416+02:00 time="2024-07-24T22:44:26Z" level=info msg="Mounted volume pvc-c5052541-db99-480e-9c96-17df67d839a1 on node some-node via device /dev/mapper/pvc-c5052541-db99-480e-9c96-17df67d839a1" func="csi.(*NodeServer).NodeStageVolume" file="node_server.go:546" component=csi-node-server function=NodeStageVolume
2024-07-25T00:44:26.125771114+02:00 time="2024-07-24T22:44:26Z" level=info msg="Trying to ensure mount point /var/lib/kubelet/pods/fbfcd704-5026-4d2f-bc97-414f1508e1bf/volumes/kubernetes.io~csi/pvc-c5052541-db99-480e-9c96-17df67d839a1/mount" func=csi.ensureMountPoint file="util.go:295"
2024-07-25T00:44:26.199670275+02:00 time="2024-07-24T22:44:26Z" level=info msg="NodePublishVolume: rsp: {}" func=csi.logGRPC file="server.go:141"

At 2024-07-24T22:44:28Z we unpublished it for the first pod.
2024-07-25T00:44:28.521067527+02:00 time="2024-07-24T22:44:28Z" level=info msg="NodeUnpublishVolume: req: {\"target_path\":\"/var/lib/kubelet/pods/ee22bee4-e011-4790-acbe-281515ee3fb3/volumes/kubernetes.io~csi/pvc-c5052541-db99-480e-9c96-17df67d839a1/mount\",\"volume_id\":\"pvc-c5052541-db99-480e-9c96-17df67d839a1\"}" func=csi.logGRPC file="server.go:132"
2024-07-25T00:44:28.557756657+02:00 time="2024-07-24T22:44:28Z" level=info msg="NodeUnpublishVolume: rsp: {}" func=csi.logGRPC file="server.go:141"

At 2024-07-25T16:30:43Z, it was fully unstaged and unpublished. This was probably the complete scale down mentioned.
The syslog shows an attempt to remove the block device associated with the volume at 2024-07-24T22:43:56Z, but I/O errors against the device continued until the moment the scale down occured.
Jul 25 00:43:56 some-node systemd-homed[1377]: block device /sys/devices/platform/host22/session43/target22:0:0/22:0:0:1/block/sdq has been removed.
Jul 25 00:44:25 some-node kernel: dmcrypt_write/2: attempt to access beyond end of device#012sdq: rw=2049, sector=97345544, nr_sectors = 8 limit=0
Jul 25 00:44:30 some-node kernel: dmcrypt_write/2: attempt to access beyond end of device#012sdq: rw=38913, sector=101954432, nr_sectors = 8 limit=0
Jul 25 00:44:30 some-node kernel: dmcrypt_write/2: attempt to access beyond end of device#012sdq: rw=38913, sector=101954440, nr_sectors = 8 limit=0
Jul 25 00:44:30 some-node kernel: dmcrypt_write/2: attempt to access beyond end of device#012sdq: rw=38913, sector=101954448, nr_sectors = 8 limit=0
Jul 25 00:44:30 some-node kernel: dmcrypt_write/2: attempt to access beyond end of device#012sdq: rw=38913, sector=101954456, nr_sectors = 8 limit=0
Jul 25 00:44:30 some-node kernel: dmcrypt_write/2: attempt to access beyond end of device#012sdq: rw=38913, sector=101954464, nr_sectors = 8 limit=0
Jul 25 00:44:30 some-node kernel: dmcrypt_write/2: attempt to access beyond end of device#012sdq: rw=38913, sector=101954472, nr_sectors = 8 limit=0
Jul 25 00:44:30 some-node kernel: dmcrypt_write/2: attempt to access beyond end of device#012sdq: rw=38913, sector=101954480, nr_sectors = 8 limit=0
Jul 25 00:44:30 some-node kernel: dmcrypt_write/2: attempt to access beyond end of device#012sdq: rw=38913, sector=101954488, nr_sectors = 8 limit=0
Jul 25 00:44:30 some-node kernel: Aborting journal on device dm-9-8.
Jul 25 00:44:30 some-node kernel: dmcrypt_write/2: attempt to access beyond end of device#012sdq: rw=38913, sector=100958208, nr_sectors = 8 limit=0
Jul 25 00:44:30 some-node kernel: Buffer I/O error on dev dm-9, logical block 12615680, lost sync page write
Jul 25 00:44:30 some-node kernel: JBD2: I/O error when updating journal superblock for dm-9-8.
Jul 25 04:01:34 some-node kernel: PMS ReqHandler: attempt to access beyond end of device#012sdq: rw=12288, sector=50430208, nr_sectors = 8 limit=0
Jul 25 04:01:34 some-node kernel: EXT4-fs error (device dm-9): __ext4_find_entry:1682: inode #1572865: comm PMS ReqHandler: reading directory lblock 0
Jul 25 04:01:34 some-node kernel: dmcrypt_write/2: attempt to access beyond end of device#012sdq: rw=14337, sector=32768, nr_sectors = 8 limit=0
Jul 25 04:01:34 some-node kernel: Buffer I/O error on dev dm-9, logical block 0, lost sync page write
Jul 25 04:01:34 some-node kernel: EXT4-fs (dm-9): I/O error while writing superblock
...
Jul 25 18:29:54 some-node kernel: PMS ReqHandler: attempt to access beyond end of device#012sdq: rw=12288, sector=50430208, nr_sectors = 8 limit=0

Theory
When automatically deleting the pod, Kubernetes starts up a new one before the old one is fully torn down. Since the new one is being created, Kubernetes never actually calls NodeUnstageVolume for the old one. We do it manually anyway, but fail to do it correctly. The exact nature of the failure has something to do with the extra layers associated with the encrypted device and the fact that the encrypted device is still mounted by the old pod. We report success to Kubernetes, but under the hood, the new pod is still using the bad/incorrect/failed block device. Simply deleting the pod again may cause the same behavior to occur. Scaling down ensures the volume goes through NodeUnstage and NodeUnpublish cleanly before NodeState and NodePublish are called again.

I will try to reproduce it in my environment.

https://github.com/longhorn/longhorn-manager/pull/1079 implemented the automatic restage behavior. https://github.com/longhorn/longhorn-manager/pull/1079#issue-1012796365 suggests that it should not work for encrypted volumes, but an attempt appears to be being made here. Maybe https://github.com/longhorn/longhorn-manager/pull/2644 introduced a behavioral change?

really appreciate the effort researching this issue @ejweber
I only use encrypted volumes so I don't know if this can happen on non-encrypted volumes. I've also seen the auto delete feature work correctly before so it is probably a race of some sort as you think

Also, https://github.com/longhorn/longhorn/issues/8473 might be related?

Recreate

Deploy examples/crypto/secret-crypto-global.yaml.
Deploy examples/crypto/storageclass-crypto-global.yaml.
Deploy this manifest.

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: test-pvc
  namespace: default
spec:
  accessModes:
    - ReadWriteOnce
  storageClassName: longhorn-crypto-global
  resources:
    requests:
      storage: 2Gi
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: test
  labels:
    app: test
  namespace: default
spec:
  selector:
    matchLabels:
      app: test # has to match .spec.template.metadata.labels
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        app: test
    spec:
      restartPolicy: Always
      containers:
      - image: alpine:latest
        name: test
        command: ["sh", "-c", "while true; date; do touch /var/lib/test; sleep 1; done"]
        volumeMounts:
        - name: test-volume
          mountPath: /var/lib/test
      volumes:
      - name: test-volume
        persistentVolumeClaim:
          claimName: test-pvc

Either delete the instance-manager running the volume's engine (~50% recreate rate) or exec into the instance-manager pod and kill the engine process (~100% success rate).

The success rate difference seems to be because the volume reattaches very quickly if the instance-manager pod remains alive and more slowly if it does not. NodePublishVolume fails immediately when the volume is not attached. Due to exponential backoff, etc., it is possible that the NodeUnpublishVolume call for the old pod succeeds before the NodePublishVolume for the new pod has the chance to cause an error similar to https://github.com/longhorn/longhorn/issues/9085#issuecomment-2258766723.

Not the result of https://github.com/longhorn/longhorn-manager/pull/2644. It was not backported to v1.5.x, but the issue is still reproducible there.


Rewrite ViewSchema.checkCompatibility to leverage discrepancies

Description
Updates ViewSchema.checkCompatibility to leverage the getFieldDiscrepancies codepath.
This also puts in place infrastructure to allow viewing the document when the only differences between view and stored schema are extra optional fields in the stored schema on nodes that the view schema author has declared are OK.

It's probably feasible to split optional field work into a different PR and make this one more about using the new compatibility logic. I can do that if this space is difficult for the reviewer to reason about, or if we're concerned about risk of this change.
I am aware of a few ways that the new compatibility logic is not totally equivalent to the old one, but only places where it is stricter and probably doesn't matter in practice (e.g. it doesn't detect all types of never fields as equivalent, but realistic customers probably aren't going around and declaring such things anyway).
Another thing which we used to allow but now do not is upgrading from an object node schema to a map node schema over the union of all the object fields' types. This is probably not something people are particularly yearning for, and TBH I'm not totally convinced we have the test coverage which verifies this actually works beyond it being theoretically sound.
One thing to watch out for is that a lot of our test coverage for 'the new code path' being equivalent to 'the old code path' comes from implementing an isRepoSuperset based on getFieldDiscrepancies and asserting it is equivalent to the previous compatibility logic's allowsRepoSuperset. Because the new compatibility check no longer directly uses isRepoSuperset, this coverage doesn't directly reply. As such, I wrote a test suite explicitly for ViewSchema which should cover what we need (but reviewer: please verify this!)


Open SAMP wiki

Is possible to be made when you mark up something and press key to open samp wiki for that specific selection. Example: PutPlayerInVehicle then i press Ctrl+F1 and opens http://wiki.sa-mp.com/wiki/PutPlayerInVehicle

I believe that is possible through a Python script bound to a key, I'll look into it.

Thanks and i hope it can be done.

Something like this should work (quick code notes for when I get home later)
import sublime, sublime_plugin
import webbrowser

class OpenWikiOnString(sublime_plugin.TextCommand):

	def run(self, edit):
		query = self.view.sel()[0]
		webbrowser.open_new("http://wiki.sa-mp.com/wiki/" + query)

Then just bind this class to a shortcut in the keyboard config.


11_Bombardment/rust

Thank you!

Ah yes it needs a readme.md if you can add that we can merge it!

sure i can do that


Quickly tapping on a URL in a message highlights the message rather than opening the URL

This is incredibly annoying.  We should require a longer tap to highlight the message, or somehow play with the order that the taps are processed.  We obviously shouldn't break long-tap to select.

still very annoying! i have ios users constantly complaining about this and getting discouraged from opening links at all :(
any idea where in the code to find the tap processing logic?


Import your SAP Build project into SAP Web IDE

In https://developers.sap.com/tutorials/build-import-webide.html the old Web IDE is being used.
As well workflow and screenshots are outdated, i.e. BUILD plugin is now activated from Features and there is no "repository" drop down to select from.
Seems like destinations should not be created manually anymore, as now they are created automatically (https://help.sap.com/viewer/2c656257ea5740328a299638fb65975b/CF/en-US/4be99e779fcb4ff9a8e5179b74bd72cc.html)

Fixed these issues, although I had to contact the BUILD team, as there's a permissions problem with the link to the SAP Employee instructions for resetting a BUILD password.

@rbrainey Is this resolved? If so can you close?

I'm good with it if you are.


Add refutations for entries of most_wanted.md found by searching for small magmas

This adds a number of refutations for entries in most_wanted.md found by searching for magmas over Fin N, with N=2..5.
The Lean proofs are generated by a Python script and use (several versions of) a template I came up with. Note that these were my first steps with Lean and certainly not ideal.
Also note that for some other entries, there are already proofs in other files of this repository.

Could you please follow the other steps here https://github.com/teorth/equational_theories/blob/main/CONTRIBUTING.md#automated-proofs, including adding your python source and a brief explanation of how these were generated?

Sorry for missing that. I have updated the branch accordingly.

Is this subsumed by https://github.com/teorth/equational_theories/pull/111

Also, it’s not really efficient to prove and state each antiimplication separately. See https://github.com/teorth/equational_theories/blob/main/equational_theories/SmallMagmas.lean how to express all facts about a single magma in one theorem. And likely the decideFin! tactic used there helps in your case too!

Is this subsumed by #111?

Partially. Basically all theorems involving Fin 2, Fin 3 and Fin 4 should be redundant. But finsearch.py can go beyond 4 as can be seen by the theorems involving Fin 6. There should be no counter example with a smaller magma.

But finsearch.py can go beyond 4 as can be seen by the theorems involving Fin 6.

Good point. It would be good to see if they actually find new anti-implications that way, though.

Is there some easy way to check if any of the refutations in the theorems are already present somewhere else? Do we have a list of all known (non)implications?

You can run lake exe extract_implications. But as mentioned above I suggest you produce your data as non-lean files first, and then convert to lean using essentially the same script that I linked above; this will prune the facts based on known implications and on non-implications from the same file.

Thanks for the feedback. I have updated the PR as requested.
I have copied generate_lean.py from All4x4Tables as I needed to make some modifications.

Anything that needs to happen for this to be merged?

Sorry, maybe I should have just pressed the button. There is a small merge conflict now, though.

Sorry, maybe I should have just pressed the button. There is a small merge conflict now, though.

Fixed


⚠ Empornium has degraded performance

In 1d40f32, Empornium ($EMP) experienced degraded performance:

HTTP code: 200
Response time: 14610 ms

Resolved: Empornium performance has improved in 1c3608e after 11 minutes.


Update containers in other DockerSwarm stacks

As far as I can tell, Shepherd is only trying to update containers that share the same Docker stack with it.
Can I have the same instance update containers in other stacks too? Or, if I take it to the extreme, other docker swarms?

That's not true. Shepherd updates services by name, which means you can update any service in your swarm.
Updating services in other swarms could be possible via somehow forwarding the unix or tcp socket from a node in the other swarm, but that is going to be a big mess.


Fix s1s2 crashes

this one should default the temperate score values in case ghg_s1s2 or ghg_s3 is missing.
pls have a look at the code and check whether it makes sense

I ran some tests (in Jupyter Notebook) that showed that the proposed solution stops the program from crashing. However, the S1S2S3 score for the companies without ghg data came out as NaN, vs the expected fallback value. Will investigate further if this could be due to other factors.

hmm, if I run the test locally it seems to work fine. Which notebook are you running?

I ran "1_analysis_example.ipynb". I'll try some of the others as well.

I can successfully print a correct calculation when running the code inside VS Code. So there seems to be an issue with my Jupyter sessions. So the propsed fix is ok by me.

The call to _check_column is also done later in the program when aggregating to portfolio level when using any other method than WATS. Therefore I propose that we update the documentation to explain the need for ghg data for all companies + that the error message also states that ghg data is needed for most aggregation methods.

great! let's merge it then and make a new version (1.0.1)


new people landing page and updating profile page

In this PR:

new people landing page - existing one has been renamed so we don't lose data
updates to profile page

Still to do:

fix breadcrumbs on profile page
add fixed tile block to people landing page
migrate all profile pages to new people landing page

@sarahframe I just had a look at this locally. Am I right in thinking that the existing people pages (e.g. https://cdh.princeton.edu/people/rebecca-sutton-koeser/) aren't being migrated? I can't find them in the CMS. Is there a way we can keep them?

@sarahframe I just had a look at this locally. Am I right in thinking that the existing people pages (e.g. https://cdh.princeton.edu/people/rebecca-sutton-koeser/) aren't being migrated? I can't find them in the CMS. Is there a way we can keep them?

All the people and profile pages are still there. They are under People on the left hand side

Ah I understand now. Thanks. I noticed another thing, will tag you in the slack channel though.


OSX - Not scroll bar or cursorline in correct window

The scrollbar just doesn't exist in the right window. It works fine in the left window.
Also the cursorline doesn't go to the right window.
There seems to be a ton of weirdness with splits that I can't document right now

Hi @Bretley ,
Thanks for logging the issue! Ya, there were a bunch of issues here - most of them coming from this PR: #805
The biggest issue was Neovim sends us the windows position as an array of [row, col], but we were treating that was [x, y] (which is the opposite), so the measurements were wrong. This broke the buffer scroll bar, the cursor line, and any sort of UI that depends on these measurements (like error squiggles).


where does one find the logs in case of local docker log driver?

File: config/containers/logging/local.md

The actual store is somewhere in the /var/lib/docker directory on the host where the daemon runs, however, those files are not for consumption by external tools, as is called out by this note on that page;

The local logging driver uses file-based storage. The file-format and storage mechanism are designed to be exclusively accessed by the Docker daemon, and should not be used by external tools as the implementation may change in future releases.

To access the logs, use the docker container logs <your container> (or the  docker logs <your container> shorthand) subcommands, or the equivalent API endpoint (https://docs.docker.com/engine/api/)


Install latest prelease version

Expected: dotnet add package mypackage -prerelease:latest
Is this possible with dotnet add ?

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

ID: ff30b638-44e3-077c-3cad-b61d1314c303
Version Independent ID: 784413e1-77f5-f2e6-a8f4-56a73fe2d3bf
Content: dotnet add package command - .NET Core CLI
Content Source: docs/core/tools/dotnet-add-package.md
Product: dotnet-core
Technology: dotnet-cli
GitHub Login: @tdykstra
Microsoft Alias: tdykstra

cc @rrelyea @nkolev92

That's not available yet, but we have a tracking issue for that:https://github.com/NuGet/Home/issues/4699
Our amazing intern @martinrrm has a PR in review and he'll have it ready for .NET 5.

Closing this issue, as the request is tracked by https://github.com/NuGet/Home/issues/4699


Question - Potential Conflict on Decky Installation

Which should we be using? Desktop installed from here, or Decky Plugin (are they the same?)
Decky gets stuck for a VERY long time on second library for me.

@aggietallboy yeah they are the same but, send me your log to see why it gets stuck

Apolgies -- super noob on steamdeck, just got on Friday -- where are the logs?

@aggietallboy its in the Downloads folder for the NonSteamLaunchers log and then for the decky plugin I think it's like home/deck/homewbrew/plugins/logs/NonSteamLaunchers or something like that


implementation trust authentication

Codecov Report

Merging #5464 into hba will decrease coverage by 0.07%.
The diff coverage is 25.31%.

@@             Coverage Diff              @@
##                hba    #5464      +/-   ##
============================================
- Coverage     82.18%   82.11%   -0.08%
  Complexity    11239    11239
============================================
  Files          1357     1361       +4
  Lines         44289    44356      +67
  Branches       5574     5582       +8
============================================
+ Hits          36398    36421      +23
- Misses         5278     5313      +35
- Partials       2613     2622       +9

Impacted Files
Coverage Δ
Complexity Δ

...io/crate/operation/auth/AuthenticationService.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...c/main/java/io/crate/action/sql/SQLOperations.java
81.11% <0%> (-0.58%)
5 <0> (ø)

...a/io/crate/operation/auth/TrustAuthentication.java
0% <0%> (ø)
0 <0> (?)

...io/crate/operation/auth/AuthorizationListener.java
0% <0%> (ø)
0 <0> (?)

...o/crate/operation/auth/UserServiceFactoryImpl.java
0% <0%> (ø)
0 <0> (?)

sql/src/main/java/io/crate/plugin/SQLModule.java
100% <100%> (ø)
2 <0> (ø)
:arrow_down:

...ava/io/crate/protocols/postgres/PostgresNetty.java
84.94% <100%> (+0.16%)
19 <0> (ø)
:arrow_down:

...io/crate/protocols/postgres/ConnectionContext.java
72.56% <20.68%> (-7.21%)
33 <0> (+2)

...ain/java/io/crate/protocols/postgres/Messages.java
75% <40%> (-1.88%)
24 <1> (+1)

...o/crate/operation/auth/AuthenticationProvider.java
58.33% <58.33%> (ø)
3 <3> (?)

... and 36 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 01ea721...86e8338. Read the comment docs.


feature: 提出插件管理页面的安装操作入口 (closed #807)

Codecov Report

Merging #817 (745e52d) into V2.2.16-rc1 (94c8007) will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           V2.2.16-rc1     #817   +/-   ##
============================================
  Coverage        71.05%   71.05%
============================================
  Files              294      294
  Lines            21596    21596
============================================
  Hits             15345    15345
  Misses            6251     6251

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 94c8007...745e52d. Read the comment docs.


Update Zigbee2MQTT 1.42.0-2 from 1.41.0-1 crashes VirtualBox VM

Description of the issue
While running the update, HA crashes. It creates the backup and the new folder in addons, then just dies.
Restart of VirtualBox VM required
Addon version
1.42.0-2
Platform
Core 2024.12.0
Supervisor 2024.11.4
Operating System 14.0
Frontend 20241127.4
Logs of the issue (if applicable)
2024-12-06 17:09:50.021 INFO (MainThread) [supervisor.backups.manager] Backup 39db6845 starting stage addon_repositories
2024-12-06 17:09:50.021 INFO (MainThread) [supervisor.backups.manager] Backup 39db6845 starting stage docker_config
2024-12-06 17:09:50.021 INFO (MainThread) [supervisor.backups.manager] Creating new partial backup with slug 39db6845
2024-12-06 17:09:50.024 INFO (MainThread) [supervisor.backups.manager] Backup 39db6845 starting stage addons
2024-12-06 17:09:50.053 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on 45df7312_zigbee2mqtt
2024-12-06 17:09:50.084 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon 45df7312_zigbee2mqtt
2024-12-06 17:09:50.084 INFO (MainThread) [supervisor.backups.manager] Backup 39db6845 starting stage finishing_file
2024-12-06 17:09:50.088 INFO (MainThread) [supervisor.backups.manager] Creating partial backup with slug 39db6845 completed
2024-12-06 17:09:50.089 INFO (MainThread) [supervisor.docker.addon] Updating image zigbee2mqtt/zigbee2mqtt-amd64:1.41.0-1 to zigbee2mqtt/zigbee2mqtt-amd64:1.42.0-2
2024-12-06 17:09:50.089 INFO (MainThread) [supervisor.docker.interface] Downloading docker image zigbee2mqtt/zigbee2mqtt-amd64 with tag 1.42.0-2.
2024-12-06 17:09:51.205 INFO (MainThread) [supervisor.addons.addon] Add-on '45df7312_zigbee2mqtt' successfully updated
2024-12-06 17:09:51.254 INFO (SyncWorker_0) [supervisor.docker.manager] Cleanup images: ['zigbee2mqtt/zigbee2mqtt-amd64:1.42.0-1']
2024-12-06 17:09:51.862 INFO (SyncWorker_0) [supervisor.docker.manager] Cleanup images: ['zigbee2mqtt/zigbee2mqtt-amd64:1.41.0-1']
2024-12-06 17:10:02.271 INFO (SyncWorker_5) [supervisor.docker.manager] Cleaning addon_45df7312_zigbee2mqtt application
2024-12-06 17:10:03.198 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-amd64 with version 1.42.0-2
2024-12-06 17:10:03.995 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name='Task-2082' coro=<Addon.watchdog_container() done, defined at /usr/src/supervisor/supervisor/addons/addon.py:1491> exception=AddonsJobError('Rate limit exceeded, more than 10 calls in 0:30:00')>
Traceback (most recent call last):
File "/usr/src/supervisor/supervisor/addons/addon.py", line 1505, in watchdog_container
await self._restart_after_problem(event.state)
File "/usr/src/supervisor/supervisor/jobs/decorator.py", line 291, in wrapper
raise on_condition(
supervisor.exceptions.AddonsJobError: Rate limit exceeded, more than 10 calls in 0:30:00
2024-12-06 17:10:18.016 ERROR (SyncWorker_2) [supervisor.docker.manager] Container addon_45df7312_zigbee2mqtt is not running
2024-12-06 17:10:33.501 ERROR (SyncWorker_0) [supervisor.docker.manager] Container addon_45df7312_zigbee2mqtt is not running
2024-12-06 17:10:37.784 INFO (SyncWorker_5) [supervisor.docker.manager] Cleaning addon_45df7312_zigbee2mqtt application
2024-12-06 17:10:38.215 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-amd64 with version 1.42.0-2
2024-12-06 17:10:38.255 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host <IP_ADDRESS>:8099 ssl:default [Connect call failed ('<IP_ADDRESS>', 8099)]
2024-12-06 17:10:38.701 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name='Task-2191' coro=<Addon.watchdog_container() done, defined at /usr/src/supervisor/supervisor/addons/addon.py:1491> exception=AddonsJobError('Rate limit exceeded, more than 10 calls in 0:30:00')>
Traceback (most recent call last):
File "/usr/src/supervisor/supervisor/addons/addon.py", line 1505, in watchdog_container
await self._restart_after_problem(event.state)
File "/usr/src/supervisor/supervisor/jobs/decorator.py", line 291, in wrapper
raise on_condition(
supervisor.exceptions.AddonsJobError: Rate limit exceeded, more than 10 calls in 0:30:00
2024-12-06 17:10:51.198 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host <IP_ADDRESS>:8099 ssl:default [Connect call failed ('<IP_ADDRESS>', 8099)]
2024-12-06 17:10:57.297 WARNING (MainThread) [supervisor.addons.manager] No update available for add-on 45df7312_zigbee2mqtt
2024-12-06 17:11:10.818 INFO (SyncWorker_5) [supervisor.docker.manager] Cleaning addon_45df7312_zigbee2mqtt application
2024-12-06 17:11:11.251 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-amd64 with version 1.42.0-2
2024-12-06 17:11:11.746 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name='Task-2322' coro=<Addon.watchdog_container() done, defined at /usr/src/supervisor/supervisor/addons/addon.py:1491> exception=AddonsJobError('Rate limit exceeded, more than 10 calls in 0:30:00')>
Traceback (most recent call last):
File "/usr/src/supervisor/supervisor/addons/addon.py", line 1505, in watchdog_container
await self._restart_after_problem(event.state)
File "/usr/src/supervisor/supervisor/jobs/decorator.py", line 291, in wrapper
raise on_condition(
supervisor.exceptions.AddonsJobError: Rate limit exceeded, more than 10 calls in 0:30:00
2024-12-06 17:11:24.410 INFO (SyncWorker_5) [supervisor.docker.manager] Cleaning addon_45df7312_zigbee2mqtt application
2024-12-06 17:11:24.963 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-amd64 with version 1.42.0-2
2024-12-06 17:11:25.484 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name='Task-2420' coro=<Addon.watchdog_container() done, defined at /usr/src/supervisor/supervisor/addons/addon.py:1491> exception=AddonsJobError('Rate limit exceeded, more than 10 calls in 0:30:00')>
Traceback (most recent call last):
File "/usr/src/supervisor/supervisor/addons/addon.py", line 1505, in watchdog_container
await self._restart_after_problem(event.state)
File "/usr/src/supervisor/supervisor/jobs/decorator.py", line 291, in wrapper
raise on_condition(
supervisor.exceptions.AddonsJobError: Rate limit exceeded, more than 10 calls in 0:30:00
2024-12-06 17:11:34.755 ERROR (SyncWorker_4) [supervisor.docker.manager] Container addon_45df7312_zigbee2mqtt is not running
2024-12-06 17:11:42.831 INFO (SyncWorker_4) [supervisor.docker.manager] Cleaning addon_45df7312_zigbee2mqtt application
2024-12-06 17:11:43.281 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-amd64 with version 1.42.0-2
2024-12-06 17:11:43.356 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host <IP_ADDRESS>:8099 ssl:default [Connect call failed ('<IP_ADDRESS>', 8099)]
2024-12-06 17:11:43.808 ERROR (MainThread) [asyncio] Task exception was never retrieved

Further, trying to stop container hangs...
VBoxManage controlvm "homeassistant" poweroff
0%...10%...20%...
The only way out is to kill the process.

I experience the same exact issue. The update has remained in my update list since release

No one seemed bothered, even to say it's you, dummy.


RDBES: RS_Sampler update of codes

Please see attached spreadsheet for the 4 code updates.
RS_Sampler updates.xlsx

@HenrikK-N  Sampled by Control needs clarification. Imagery to Imaging or Digital imaging.

CodeType description needs to be embellished

RDBES core group: Needs to discuss the EM/Imagery debacle and see if they are both needed.
Control	-  Sampled by control agency
ElectronicMonitoring  -  Sampled by electronic monitoring
Imagery	-   Sampled using images
Observer	-  Sampled by scientific observer
Self-Sampling	-  Sampled through self-sampling

Wrote to David Currie for update

@HenrikK-N  can we also add this CodeType to the Core group meeting agenda? thanks

ElectronicMonitoring to be removed,
Imagery stays, update with WGTIFD 2019 report description, and reference it in the Long description.
Self-Sampling to be updated to SelfSampling. Description to be updated to: Sampled by the fisher.

Done


C1-2758-2 when transferring

I've been trying to transfer h-encore over to my vita for two days now.
I did everything by tutorial several times, no luck.
Same with auto h-encore, the same error when i try to transfer.
Every step before that was fine, but no matter what it doesn't want to transfer.
Neither wi-fi nor usb transfers work.
My official firmware version is 6.68, and Vita itself is an old fat 3G+Wi-fi version.
I also tried rebuilding the database and formatting several times, still no luck.

Your memory card can be broken. Try to use another memory card.

Same issue here (fat model, 3.65). I tested the memory card and it works fine, so it must be something else.

I am using two different memory cards on two different systems, and both are resulting in the same C1-2758-2 error.  Guide was followed, as well as a video to ensure I was following the correct steps.  3.68 OFW on a Fat and Slim, setup on my PSN account, same error on each.
Please let me know what else I can provide to assist with further troubleshooting.

Same issue here; Japanese PS Vita Slim on 3.65.
Using Linux and followed both the official readme.md tutorial and the vita.hacks.guide tutorial; both exhibited the same C1-2758-2 error upon attempting to transfer. Also tried rebuilding database, removing the memory card, reinserting the memory card; compiling different versions of QCMA, no dice :(

Sorry to comment on a two year old issue, but i am having the same issue

Sorry to comment on an issue that half an decade ago. But this is still happening today.
I was following the tutorial step by step exactly and got the same error during transferring the packaged h-encore while I had no problem transfer any other Apps between my Vita and Fedora system.
Initially I thought it was permission issue. But exactingly all content shared the same permission setup as the rest of qcma backed up apps. Hence no clue what could cause this.
Eventually I had to dig out another Win machine to workaround the problem, just as OP.


[FEAT] Context Type Automatic Detection

Is your feature request related to a problem? Please describe.
Pardon if this is already implemented, but the ability to override the context type in a similar fashion to other type mappings.
Describe the solution you'd like
Maybe ContextTypeMapper or even just ContextType
Describe alternatives you've considered
Currently using presetConfig.typesPluginConfig.contextType and it's working very well, but wanted to call this out.

Good idea @RichiCoder1 ! Do you have a suggestion on the file name? 🙂

Maybe just schema.context.ts? And warn if there are multiple matches with first winning?
Would export Context. So basically an automatic schemas/base/schema.context.ts#Context.

Nice! I think we are onto something here 🙌
Maybe the export could be ResolversContext to be more explicit?
There's also fieldContextTypes option in typescript-resolvers which could be used to set context on the field level...
So, I'm thinking each module could declare its own schema.context.ts file. For example:
If schema/user/schema.context.ts has Query_userResolversContext, then it'd be mapped to fieldContextTypes: ['Query.user#./schema/user/schema.context.ts#Query_UserResolversContext']

Just to be certain this is what I'm also looking for. This would mean that the ResolversContext type definition in schema.context.ts will be imported by types.generated.ts and hence propagated. Correct?
Curious if this could also result in generating a context "resolver" file similar to what graphql-yoga would expect. But I suppose that's a feature on top of that as well.

Hi @karloluis ,

This would mean that the ResolversContext type definition in schema.context.ts will be imported by types.generated.ts and hence propagated. Correct?

Yes! That's correct.
You could already use the context type like this when creating GraphQL Yoga server:
const yoga = createYoga<{}, ResolverContext>({
  context: { ... }, // <-- Context object/function is typed to `ResolverContext`
});

Each GraphQL server may have a different type for its context "resolver", so I'm not sure we should generate it. 🙂

Any updates here? Is there any way to specify the context type with this plugin? The docs state to use  {config:  contextType: 'MyCustomContext'}} but not clear how to integrate that with this plugin's defineConfig()... should the results of defineConfig() be updated with contextType, or is there another way?

It's been a few months and I decided to update to version 0.8.0. Hurray! 🎉
Looking back at the configs I am still stuck on how to configure a default ContextType. My generated types look as follows:
export type QueryResolvers<
  ContextType = any,
  ParentType extends ResolversParentTypes['Query'] = ResolversParentTypes['Query'],
> = { ... }

With the use of generates."src/graphql".presetConfig.typesPluginConfig.contextType: "./context.ts#Context" I expected ContextType = any to change to reference the exported type from the file. Sadly that didn't happen and after tinkering around for a bit I have not been able to figure things out.
Is my understanding that the any type should reference the Context type incorrect? Could I be missing something with regards to the ts-resolver plugin?

Yes, that's correct @karloluis.
Here's an example repo: https://github.com/eddeee888/graphql-server-template/

The context config is here: https://github.com/eddeee888/graphql-server-template/blob/bcf63ee72f59d656257f770978c6ca45cdf4287b/codegen.ts#L12...
Which points to this type

Well that's awkward. After tinkering with the file a bit more and testing the typesSuffix option to validate that the options were in fact picked up it suddenly started working whereas a few runs ago it didn't seem to do any changes!
I suspect my runtime for codegen was somehow faulty. Maybe bad YAML indentation.


Feat/v2 I suggest adding voice input and output

Clear and concise description of the problem
Feat/v2 I suggest adding voice input and output
Suggested solution
Feat/v2 I suggest adding voice input and output
Alternative
No response
Additional context
No response
Validations

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

Duplicate of #228


WIP: UTF-8: Add support for parsing UTF8 metric and label names

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: ywwg:x: Federico TorresFederico Torres seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


DELETE Volume API Support for AWS

Issue/Feature Description:
Delete Volume from multi-cloud AWS block driver support for AWS Volume
Why this issue to fixed / feature is needed(give scenarios or use cases): DELETE AWS Volumes API
How to reproduce, in case of a bug:
Other Notes /  Environment Information: (Please give the env information, log link or any useful information for this issue)

PR merged


fix: Split css file into base, toolbar, document, mapping-detail and …

…mapping-list
Fixes: #1193

Hi @seanforyou23, could you review how we split AtlasMap CSS into some component groups? I remember you suggested to have base CSS with only common things defined and let others inherit it, but I don't know how it actually looks like.

moved conversation back to the Issue


Add an in-game button for reporting bugs.

Description
As discussed in the February 5th 2022 maintainer meeting, we should have an in-game button à la subnautica to report bugs.

Subnautica button GDC talk
Have a /vg/-like button to create issues on GitHub on a separate repo, so the main one is not spammed
In-game window
Make sure it has feedback so we dont get duplicate bug reports
What do we grab:

Round information
Commit the server is at

How do we fix it not leaking current-round information?

Only send at end of round.
Cache the reports into local SQLite DB (game server) while the round is going on in case the server crashes, then send them through the server, not the watchdog.

https://github.com/schneidmaster/gitreports.com

Is it worth also taking a screenshot at the time the issue button is pressed, or add an option to add a screenshot from the game?

Is it worth also taking a screenshot at the time the issue button is pressed, or add an option to add a screenshot from the game?

Screenshots would be really helpful in many cases, we should definitely have them as an option imo


Add check for unicode in TAXII Miner

2018-04-18T16:24:22 (4743)basepoller._polling_loop INFO: Polling PNFP-FSISAC-3
2018-04-18T16:24:24 (4743)taxii._check_collections INFO: PNFP-FSISAC-3 - message binding: ['urn:taxii.mitre.org:message:xml:1.1']
2018-04-18T16:24:24 (4743)taxii._check_collections INFO: PNFP-FSISAC-3 - poll service found
2018-04-18T16:24:24 (4743)taxii._incremental_poll_collection INFO: PNFP-FSISAC-3 - polling datetime.datetime(2018, 3, 20, 11, 12$
2018-04-18T16:24:25 (4743)taxii._handle_content_blocks ERROR: PNFP-FSISAC-3 - exception in _handle_content_blocks
Traceback (most recent call last):
 File "/opt/minemeld/engine/0.9.44/local/lib/python2.7/site-packages/minemeld/ft/taxii.py", line 539, in _handle_content_blocks
   co = self._decode_observable(o)
 File "/opt/minemeld/engine/0.9.44/local/lib/python2.7/site-packages/minemeld/ft/taxii.py", line 595, in _decode_observable
   return self._decode_object_properties(op, odict=odict)
 File "/opt/minemeld/engine/0.9.44/local/lib/python2.7/site-packages/minemeld/ft/taxii.py", line 763, in _decode_object_propert$
   ov = ov.get('value', None)
AttributeError: 'unicode' object has no attribute 'get'
2018-04-18T16:24:25 (4743)basepoller._poll ERROR: Exception in polling loop for PNFP-FSISAC-3: 'unicode' object has no attribute$
Traceback (most recent call last):
 File "/opt/minemeld/engine/0.9.44/local/lib/python2.7/site-packages/minemeld/ft/basepoller.py", line 721, in _poll
   performed = self._polling_loop()
 File "/opt/minemeld/engine/0.9.44/local/lib/python2.7/site-packages/minemeld/ft/basepoller.py", line 597, in _polling_loop
   for nitem, item in enumerate(iterator):
 File "/opt/minemeld/engine/0.9.44/local/lib/python2.7/site-packages/minemeld/ft/taxii.py", line 470, in _incremental_poll_coll$
   end=cend
 File "/opt/minemeld/engine/0.9.44/local/lib/python2.7/site-packages/minemeld/ft/taxii.py", line 414, in _poll_collection
   stix_objects
 File "/opt/minemeld/engine/0.9.44/local/lib/python2.7/site-packages/minemeld/ft/taxii.py", line 539, in _handle_content_blocks
   co = self._decode_observable(o)
 File "/opt/minemeld/engine/0.9.44/local/lib/python2.7/site-packages/minemeld/ft/taxii.py", line 595, in _decode_observable
   return self._decode_object_properties(op, odict=odict)
 File "/opt/minemeld/engine/0.9.44/local/lib/python2.7/site-packages/minemeld/ft/taxii.py", line 763, in _decode_object_propert$
   ov = ov.get('value', None)
AttributeError: 'unicode' object has no attribute 'get'

This should have been fixed with #278, let's wait for validation.