Add preflight check for availability of HyperV and dependent cmdlets on Powershell Core (v6)

General information

OS: Windows
Hypervisor: Hyper-V
Did you run crc setup before starting it (Yes/No)? Yes

CRC version
PS C:\Users\Erik> crc version
version: 1.0.0-beta.5+f2aa58c
OpenShift version: 4.1.14 (embedded in binary)

CRC status
# Put `crc status` output here

CRC config
# Put `crc config view` output here

Host Operating System
# Put the output of `cat /etc/os-release` in case of Linux
# put the output of `sw_vers` in case of Mac
# Put the output of `systeminfo` in case of Windows

Steps to reproduce

Run crc start in Windows Terminal (Preview) / Powershell 6.1.1

Expected
I then closed the Windows Terminal and tried again in regular PowerShell version 5.1 and had no problems. I expect it to work like that. I'm unsure whether it's the new terminal or the newer version of PowerShell 6.1.1 that's causing the issue.
Actual
Logs
You can start crc with crc start --log-level debug to collect logs.
Please consider posting this on http://gist.github.com/ and post the link in the issue.
PowerShell 6.1.1
Copyright (c) Microsoft Corporation. All rights reserved.

https://aka.ms/pscore6-docs
Type 'help' to get help.

PS C:\Users\Erik> crc setup
INFO Checking if running as normal user
INFO Caching oc binary
INFO Unpacking bundle from the CRC binary
INFO Check Windows 10 release
INFO Hyper-V installed
INFO Is user a member of the Hyper-V Administrators group
INFO Does the Hyper-V virtual switch exist
Setup is complete, you can now run 'crc start' to start a CodeReady Containers instance

PS C:\Users\Erik> crc start --log-level debug
INFO Checking if running as normal user
INFO Checking if oc binary is cached
DEBU oc binary already cached
INFO Check Windows 10 release
INFO Hyper-V installed and operational
INFO Is user a member of the Hyper-V Administrators group
INFO Does the Hyper-V virtual switch exist
Checking file: C:\Users\Erik\.crc\machines\crc\.crc-exist
? Image pull secret [? for help] **********************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************
INFO Loading bundle: crc_hyperv_4.1.14.crcbundle ...
INFO Creating VM ...
Found binary path at C:\Program Files\crc-windows-1.0.0-beta.5-amd64\crc.exe
Launching plugin server for driver hyperv
Plugin server listening at address <IP_ADDRESS>:50954
() Calling .GetVersion
Using API Version 1
() Calling .SetConfigRaw
() Calling .GetMachineName
(crc) Calling .GetMachineName
(crc) Calling .DriverName
Running pre-create checks...
(crc) Calling .PreCreateCheck
(crc) DBG | [executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive @(Get-Module -ListAvailable hyper-v).Name | Get-Unique (crc) DBG | [stdout =====>] :
(crc) DBG | [stderr =====>] : Get-Unique : The 'Get-Unique' command was found in the module 'Microsoft.PowerShell.Utility', but the module could not be loaded. For more information, run 'Import-Module Microsoft.PowerShell.Utility'. (crc) DBG | At line:1 char:45
(crc) DBG | + @(Get-Module -ListAvailable hyper-v).Name | Get-Unique
(crc) DBG | + ~~~~~~~~~~
(crc) DBG | + CategoryInfo : ObjectNotFound: (Get-Unique:String) [], CommandNotFoundException
(crc) DBG | + FullyQualifiedErrorId : CouldNotAutoloadMatchingModule
(crc) DBG |
 (crc) DBG |
 ERRO Error occurred: Error creating host: Error creating the VM. Error with pre-create check: "exit status 1"
Making call to close driver server
(crc) Calling .Close
Successfully made call to close driver server
(crc) DBG | Closing plugin on server side
Making call to close connection to plugin binary

you need to load the Hyper-V cmdlets before they can be used. PowerShell Core does not include them automagically on startup.
We might want to add a preflight check for this, but this is not an issue with CRC.

I am inclined to close this as Get-Unique is supposed to be part of the standard set of cmdlets for any PowerShell. Even if this cmdlet is not available, module auto-loading should kick in and reload this module.
Adding a check for Hyper-V cmdlets might be possible, but even those should be available, as we already check for the existence of the Hyper-V feature.
Adding a check for Get-Unique is like testing if the Command Prompt offers dir. It should work... this most likely is therefore an issue on the users end related to his setup. More info is needed.

https://github.com/code-ready/crc/blob/9a47ead42397c6ed2f59238168391329828497aa/pkg/crc/preflight/preflight_checks_windows.go#L45
We could add the check to see if the client tools are installed, but then again... this is implied with our fix function and the reported issue was for a standard cmdlet being missing.

@tofflos can you run (Get-Command -Module Microsoft.Powershell.Utility).Name inside your PowerShell 6.1.1 environment?

PS C:\Users\Erik> (Get-Command -Module Microsoft.Powershell.Utility).Name
ConvertFrom-SddlString
Add-Member
Add-Type
Clear-Variable
Compare-Object
ConvertFrom-Csv
ConvertFrom-Json
ConvertFrom-Markdown
ConvertFrom-StringData
ConvertTo-Csv
ConvertTo-Html
ConvertTo-Json
ConvertTo-Xml
Debug-Runspace
Disable-PSBreakpoint
Disable-RunspaceDebug
Enable-PSBreakpoint
Enable-RunspaceDebug
Export-Alias
Export-Clixml
Export-Csv
Export-FormatData
Export-PSSession
Format-Custom
Format-Hex
Format-List
Format-Table
Format-Wide
Get-Alias
Get-Culture
Get-Date
Get-Event
Get-EventSubscriber
Get-FileHash
Get-FormatData
Get-Host
Get-MarkdownOption
Get-Member
Get-PSBreakpoint
Get-PSCallStack
Get-Random
Get-Runspace
Get-RunspaceDebug
Get-TraceSource
Get-TypeData
Get-UICulture
Get-Unique
Get-Uptime
Get-Variable
Get-Verb
Group-Object
Import-Alias
Import-Clixml
Import-Csv
Import-LocalizedData
Import-PowerShellDataFile
Import-PSSession
Invoke-Expression
Invoke-RestMethod
Invoke-WebRequest
Measure-Command
Measure-Object
New-Alias
New-Event
New-Guid
New-Object
New-TemporaryFile
New-TimeSpan
New-Variable
Out-File
Out-String
Read-Host
Register-EngineEvent
Register-ObjectEvent
Remove-Alias
Remove-Event
Remove-PSBreakpoint
Remove-TypeData
Remove-Variable
Select-Object
Select-String
Select-Xml
Send-MailMessage
Set-Alias
Set-Date
Set-MarkdownOption
Set-PSBreakpoint
Set-TraceSource
Set-Variable
Show-Markdown
Sort-Object
Start-Sleep
Tee-Object
Test-Json
Trace-Command
Unblock-File
Unregister-Event
Update-FormatData
Update-TypeData
Wait-Debugger
Wait-Event
Write-Debug
Write-Error
Write-Host
Write-Information
Write-Output
Write-Progress
Write-Warning
Write-Verbose

I am unable to reproduce this with PowerShell core 6.0.0 (first release) and the current latest.

Get-Unique

the cmdlet exists, so there is something wrong with your setup.
Will mark this issue as invalid. If you believe this is wrong, please re-open and provide more information about your setup.


feat(zones): move KDSSubscriptions to use a table/summary

Changes Zone Subscriptions only to use a table/summary view/interaction.
We decided that there would be far more space to show things if we used our common table/summary panel pattern instead of the accordion where there is very little space to show things:

See:

https://github.com/kumahq/kuma-gui/issues/2623
https://github.com/kumahq/kuma-gui/issues/2164

~Questions:~
~1. Do we want to show the Subscription YAML, the Subscription JSON config, or both?~
~2. If we want to show both, should we add a separate [YAML] tab or use the Structured/YAML dropdown?~
Note:
I'm guessing we'll want the same layout for DPP subscriptions, I plan to do this as a follow up and there will some changes made on top of here to make the panel work in both places.
Closes https://github.com/kumahq/kuma-gui/issues/2704

Do we want to show the Subscription YAML, the Subscription JSON config, or both?
If we want to show both, should we add a separate [YAML] tab or use the Structured/YAML dropdown?

I figured we probably don't want to show the YAML, its not like you'd want to use it for anything. If that incorrect we can always add as a follow up.

K this one has had a few alterations after a first round of reviews, good to go again now 👍

LGTM do we have issues to cover the same work for dataplane and zone proxies? If not can we open them and milestone them for 2.10 please?


⚠ Bofrost.lu has degraded performance

In d3ce9fd, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2001 ms

Resolved: Bofrost.lu performance has improved in d047caa after 37 minutes.


🐛 fix: incorrect inheritance/extensions when parent class is not scanned first (fix #47)

Codecov Report

Merging #48 (57f00af) into main (916897a) will increase coverage by 0.13%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #48      +/-   ##
==========================================
+ Coverage   91.62%   91.75%   +0.13%
==========================================
  Files          22       22
  Lines         800      813      +13
==========================================
+ Hits          733      746      +13
  Misses         67       67

Impacted Files
Coverage Δ

...ftPlantUMLFramework/Internal/SyntaxStructure.swift
96.07% <ø> (ø)

...ftPlantUMLFramework/Internal/PlantUMLContext.swift
77.94% <100.00%> (+0.66%)
:arrow_up:

...ources/SwiftPlantUMLFramework/PlantUMLScript.swift
96.61% <100.00%> (+0.77%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add possibility to test Logstash Bosh templates

Add bosh-template and rake gems to install-dependencies. Add scripts for
templates testing. Add first template tests - for input_and_output.erb.conf Bosh template.
This PR is usefult for testing changes in templates e.g. those needed for issue https://github.com/cloudfoundry-community/logsearch-boshrelease/issues/8.

@hannayurkevich Thanks for contribution! Could you please also update .travis.yml in root of repo to run all tests.

@Infra-Red, I've made test rake task to run all tests so there is no need to change travis.yml.

Thanks @hannayurkevich !


Not compatible with hyper 0.11

I get Could not find `net` in `hyper`  when trying to use the mock_connector! macro with hyper 0.11.

Thanks for letting me know. Probably it's not too hard to fix, in case someone is interested to submit a PR.

I'm keen to help out with this as yup-hyper-mock is the first step in upgrading my app to hyper 0.11.
On the surface, it looks like the issue is that the NetworkConnector and NetworkStream are no longer present in hyper, so I'd have to map that onto something else.
Has anyone done any thinking about what might need to be done? Or, where might be the best place to ask for help.

I think that building a Service is the right way to go. https://github.com/Byron/yup-hyper-mock/pull/12 is my initial WIP work towards that, but I'm a bit stuck (see description there). Help wanted!

Version 3.12.0 was just released to crates.io.
Thanks again to @palfrey , who single-handedly ported this crate over, leaving no character untouched :).


Revive Pet / Mend Pet not switching properly

/cast [nopet,nodead] Call Pet 1; [@pet, dead] Revive Pet
GSE seems to rewrite my macro on the fly to allow for the different versions of Revive pet and Mend pet. This would be ok, but it seems to not revert when my pet dies, so even though my macro is written with revive pet, GSE changes it to mend pet because when the macro initializes the pet is alive... i think.
I have found a workaround, which is to create a normal macro and then put it on my action bar, and use "/click ActionBar7" within the GSE macro itself. This just feels bad.
Is there any way to keep GSE from rewriting the macro?

It’s not GSE rewriting this but WoW.  It’s not something I control or can work around.
TimothyLuke

On 30 Jul 2018, at 9:03 am, Baeon<EMAIL_ADDRESS>wrote:
/cast [nopet,nodead] Call Pet 1; [@pet, dead] Revive Pet
GSE seems to rewrite my macro on the fly to allow for the different versions of Revive pet and Mend pet. This would be ok, but it seems to not revert when my pet dies, so even though my macro is written with revive pet, GSE changes it to mend pet because when the macro initializes the pet is alive... i think.
I have found a workaround, which is to create a normal macro and then put it on my action bar, and use "/click ActionBar7" within the GSE macro itself. This just feels bad.
Is there any way to keep GSE from rewriting the macro?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

i am confused. how is wow changing what i see in gse? i type in the above into gse, and when i save it, it saves as the other version of the spell.
This is what I type:

And this is what GSE saves:

This is an exert of what GSE changes:
-- Priest
Statics.BaseSpellTable[123040] = 34433 -- Mindbender -> Shadow Fiend
Statics.BaseSpellTable[200174] = 34433 -- Mindbender -> Shadow Fiend
Statics.BaseSpellTable[205369] = 8122 -- Mind Bomb -> Physic Scream
Statics.BaseSpellTable[205351] = 8092 -- Shadow Word: Void -> Mind Blast
Statics.BaseSpellTable[204197] = 589 -- Purge the Wicked -> Shadow Word: Pain
Statics.BaseSpellTable[271466] = 62618 -- Luminous Barrier -> Power Word: Barrier
Statics.BaseSpellTable[228266] = 228260 -- Void Bolt -> Void Eruption
Statics.BaseSpellTable[205448] = 228260 -- Void Bolt -> Void Eruption

-- Hunter
Statics.BaseSpellTable[259387] = 186270 -- Mongoose Bite -> Raptor Strike

-- Warlock

-- Shaman
Statics.BaseSpellTable[192249] = 198067 -- Storm Elemental -> Fire Elemental
Statics.BaseSpellTable[157153] = 5394 -- Cloudburst Totem -> Healing Stream Totem

You will notice in the Hunter space that Mend Pet and Revive Pet are not listed.  This is WoW changing your values not GSE.
personally I use this with no issues.
/cast [mod]Revive Pet; [@pet,dead]Revive Pet; [nopet]Call Pet 1; Mend Pet

see, yours still says revive pet. mine changes to mend pet whenever i put revive pet in the GSE macros... or whenever i import anyone else's macros.

Just to clarify GSE is not making this change.  It’s not something GSE has any control overs. WoW merged Revive Pet and Mend Pet into a multi button spell.

BaeonToday at 3:51 PM
the weird part is that revive pet does both, but mend pet only mends pet, and breaks lines that use it while pet is dead... they dont even get sent, or whatever
ok, final confirmation now, confirmed working in all states,  "/use" revive pet works universally as revive or mend pet

I've forced Mend Pet to save as Revive Pet  This will also mean that the same line will do one or the other reducing a step out of macro.s

This Issue is back since today's update.


Question: how to enable bootstrap style

Hi, using the tabs and find em great.
I see on the demo (at  http://indexiatech.github.io/ember-components/#/component/component.tabs/simple)
that there is Classic style and Bootstrap style.
I'd like to use the Bootstrap look, but its not shown how to go about doing that.
Could you tell me how I would do this?
Thanks

I'll document it, just try to add configName="bs" for the main tabs component.

@asaf, thank you very much.
I did that and now the tabs have no styling at all... it appears.
Its like I don't have the config or something...
Do I need to have something else installed other than just the tabs?
Or is there something I should be adding to my brocfile?
Currently looks like this:
var EmberApp = require('ember-cli/lib/broccoli/ember-app');

var app = new EmberApp();
app.import('bower_components/bootstrap/dist/js/bootstrap.js');
app.import('bower_components/bootstrap/dist/css/bootstrap.css');
app.import('bower_components/ember-addons.bs_for_ember/dist/js/bs-core.min.js');
app.import('bower_components/ember-addons.bs_for_ember/dist/js/bs-modal.min.js');
app.import('bower_components/ember-addons.bs_for_ember/dist/js/bs-alert.min.js');
app.import('bower_components/ember-addons.bs_for_ember/dist/js/bs-button.min.js');
app.import('bower_components/ember-addons.bs_for_ember/dist/js/bs-progressbar.min.js');
app.import('bower_components/ember-addons.bs_for_ember/dist/js/bs-breadcrumbs.min.js');
app.import('bower_components/ember-addons.bs_for_ember/dist/js/bs-nav.min.js');
app.import('bower_components/d3/d3.js');
app.import('bower_components/ember-data/ember-data.js');
app.import('bower_components/jquery-cookie/jquery.cookie.js');
//app.import('bower_components/ember-components/dist/globals/main.js');
//app.import('bower_components/ember-utils/dist/globals/main.js');

//app.import('node_modules/ember-radio-button/app/components/radio-button.js');
//app.import('bower_components/ic-ajax/lib/main.js');
var mergeTrees = require('broccoli-merge-trees');
var pickFiles = require('broccoli-static-compiler');

var bootstrapTree =
pickFiles('bower_components/bootstrap/fonts', {
   srcDir: '/',
   files: [
     'glyphicons-halflings-regular.svg',
     'glyphicons-halflings-regular.ttf',
     'glyphicons-halflings-regular.eot',
     'glyphicons-halflings-regular.woff'
   ],
   destDir: '/fonts'
});

module.exports = mergeTrees([app.toTree(),bootstrapTree]);

It seems the bootstrap css requires that you wrap the content inside em-tab in an "a" element.
I had (in emblem):
    = em-tab role="presentation":  | Users
    = em-tab role="presentation":  | Organizations

and saw no styling. When I changed to:
    = em-tab role="presentation": a: | Users
    = em-tab role="presentation": a: | Organizations

.. it worked!

I apologise in advance for my ignorance.. but whats emblem?
And I'm afraid I don't recognise that code above.. where would I put that ?
Thanks

emblem is to handlebars very roughly what coffeescript is to javascript.
So... in handlebars:
{{# em-tab}}Users{{#em-tab}}

ie -- just wrap your labels in "a" tags. (I think that role="presentation" is superfluous. I copied from bootstrap doc when idx-table didn't work to try and get as close as possible to bootstrap examples.)

Ahh Brilliant!
Thanks so much for that !

glad it works... @asaf -- you might consider either an addition to the layout of em-tab, or a documentation change....

thanks for the solution.. but what if I'd like to use nav-pills instead of default? How can I add a new config?

@masciugo AFAIK the only way to do this at the moment is to override the "ember-idx-tabs" initializer and define your classes there. Would definitely be nice to have a more convenient way to do it though. :+1:


Add docstrings

Hello, please assign me to this issue. I have created PR #9
https://github.com/pberkes/empirical_copula/pull/9


DinoV2 for color classification

The results are very bad for classification. I have tried with custom dataset, with 384 features as output. which is passed as input to classifier layer.
Any suggestions on which blocks I should unfreeze to get better results.

Hi, do you use data with no label? How do you handle the dataset and labels? Thank you in advance!

I fixed the poor performance in classification task by adding Convolution Nets to learn features from the embeddings before passing to linear layers. It works quite well in my case.

The results are very bad for classification. I have tried with custom dataset, with 384 features as output. which is passed as input to classifier layer.

It would be very helpful to understand better your specific use case (the title hints at "color classification"), perhaps if you could elaborate on the nature of the dataset and problem you are trying to solve using the provided backbones.


Create unit test covering as much of namespace creation alignment,minsize,compensation logic as possible

Namespace creation takes size and alignment parameters, and we have to take care about minimal size, alignment value, compensation for libndctl creating smaller than we asked, etc. aspects.
This logic is not trivial, it's also different for LVM vs Direct modes.
It makes sense to encapsulate math and logic into separate function and have it unit tested, to reduce risk of breaking the logic.

I went on and created #391 based on current issue, but I was not really happy about the result.
The separation of calculation into isolated functions loses lot of power without taking interleave-width into account, and that we can not do without running on real HW.
So my idea now is, lets take the unit test idea back.
The result is 2 commits in #391 with cleanup and renaming changes.

#391 got merged with few improvements, but as explained above, unit test plan did not materialize. Closing this.


pull request for e2e test at 12/23/2016 22:26:11

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


feat: new option importMode

close #4
This PR adds a new option importMode for specifying how routes should be loaded.
It accepts a string either async or sync or a function to resolve the mode by the giving filepath. (default to async)
{
  importMode: 'async'
}

{
  importMode: 'sync' // all the routes are directly loaded
}

{
  importMode(path: string) { // a custom function to resolve the mode for different paths.
    if (path.match(/my-sync-pages/))
      return 'sync'
    return 'async'
  }
}

This is great, thanks again for your contribution! 😊

Released in v0.4.0 🎉


'package:flutter/src/material/dropdown.dart': Failed assertion: line 1252 pos 12: 'widget.items!.where((DropdownMenuItem item) => item.value == widget.value).length == 1': is not true.

Steps to Reproduce

Execute flutter run on the code sample
...
...

Expected results:
I wanted drop-down to work normally.
Actual results:
I got this error message, on the terminal.
════════ Exception caught by widgets library ═══════════════════════════════════
The following assertion was thrown building BlocListener<CreateOrderBloc, CreateOrderState>(state: _BlocListenerBaseState<CreateOrderBloc, CreateOrderState>#58192):
'package:flutter/src/material/dropdown.dart': Failed assertion: line 1252 pos 12: 'widget.items!.where((DropdownMenuItem<T> item) => item.value == widget.value).length == 1': is not true.
package:flutter/…/material/dropdown.dart:1252
2

Either the assertion indicates an error in the framework itself, or we should provide substantially more information in this error message to help you determine and fix the underlying cause.
In either case, please report this assertion by filing a bug on GitHub:
  [https://github.com/flutter/flutter/issues/new?template=2_bug.md]()

The relevant error-causing widget was
BlocBuilder<CreateOrderBloc, CreateOrderState>
lib\…\screens\create_order.dart:136

When the exception was thrown, this was the stack
#2      _DropdownButtonState._updateSelectedIndexpackage:
flutter/…/material/dropdown.dart:1252
#3      _DropdownButtonState.didUpdateWidgetpackage:
flutter/…/material/dropdown.dart:1238
#4      StatefulElement.updatepackage:
flutter/…/widgets/framework.dart:4974
#5      Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#6      RenderObjectElement.updateChildren
package:flutter/…/widgets/framework.dart:5807
#7      MultiChildRenderObjectElement.update
package:flutter/…/widgets/framework.dart:6357
#8      Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#9      ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#10     StatefulElement.performRebuild
package:flutter/…/widgets/framework.dart:4959
#11     Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#12     StatefulElement.update
package:flutter/…/widgets/framework.dart:4991
#13     Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#14     ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#15     StatefulElement.performRebuild
package:flutter/…/widgets/framework.dart:4959
#16     Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#17     StatefulElement.update
package:flutter/…/widgets/framework.dart:4991
#18     Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#19     SingleChildRenderObjectElement.update
package:flutter/…/widgets/framework.dart:6204
#20     Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#21     SingleChildRenderObjectElement.update
package:flutter/…/widgets/framework.dart:6204
#26     Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#27     SingleChildRenderObjectElement.update
package:flutter/…/widgets/framework.dart:6204
#28     Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#29     SingleChildRenderObjectElement.update
package:flutter/…/widgets/framework.dart:6204
#30     Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#31     SingleChildRenderObjectElement.update
package:flutter/…/widgets/framework.dart:6204
#32     Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#33     ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#34     StatefulElement.performRebuild
package:flutter/…/widgets/framework.dart:4959
#35     Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#36     StatefulElement.update
package:flutter/…/widgets/framework.dart:4991
#37     Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#38     SingleChildRenderObjectElement.update
package:flutter/…/widgets/framework.dart:6204
#39     Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#40     ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#41     Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#42     ProxyElement.update
package:flutter/…/widgets/framework.dart:5136
#43     Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#44     SingleChildRenderObjectElement.update
package:flutter/…/widgets/framework.dart:6204
#45     Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#46     ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#47     Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#48     ProxyElement.update
package:flutter/…/widgets/framework.dart:5136
#49     Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#50     SingleChildRenderObjectElement.update
package:flutter/…/widgets/framework.dart:6204
#51     Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#52     SingleChildRenderObjectElement.update
package:flutter/…/widgets/framework.dart:6204
#53     Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#54     SingleChildRenderObjectElement.update
package:flutter/…/widgets/framework.dart:6204
#55     Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#56     ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#57     Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#58     ProxyElement.update
package:flutter/…/widgets/framework.dart:5136
#59     Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#60     ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#61     StatefulElement.performRebuild
package:flutter/…/widgets/framework.dart:4959
#62     Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#63     StatefulElement.update
package:flutter/…/widgets/framework.dart:4991
#64     Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#65     ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#66     StatefulElement.performRebuild
package:flutter/…/widgets/framework.dart:4959
#67     Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#68     StatefulElement.update
package:flutter/…/widgets/framework.dart:4991
#69     Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#70     ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#71     Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#72     ProxyElement.update
package:flutter/…/widgets/framework.dart:5136
#73     Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#74     ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#75     Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#76     StatelessElement.update
package:flutter/…/widgets/framework.dart:4865
#77     Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#78     ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#79     Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#80     ProxyElement.update
package:flutter/…/widgets/framework.dart:5136
#81     Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#82     RenderObjectElement.updateChildren
package:flutter/…/widgets/framework.dart:5807
#83     MultiChildRenderObjectElement.update
package:flutter/…/widgets/framework.dart:6357
#84     Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#85     SingleChildRenderObjectElement.update
package:flutter/…/widgets/framework.dart:6204
#86     Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#87     ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#88     Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#89     StatelessElement.update
package:flutter/…/widgets/framework.dart:4865
#90     Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#91     ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#92     Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#93     ProxyElement.update
package:flutter/…/widgets/framework.dart:5136
#94     Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#95     ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#96     Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#97     ProxyElement.update
package:flutter/…/widgets/framework.dart:5136
#98     Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#99     RenderObjectElement.updateChildren
package:flutter/…/widgets/framework.dart:5807
#100    MultiChildRenderObjectElement.update
package:flutter/…/widgets/framework.dart:6357
#101    Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#102    ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#103    StatefulElement.performRebuild
package:flutter/…/widgets/framework.dart:4959
#104    Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#105    StatefulElement.update
package:flutter/…/widgets/framework.dart:4991
#106    Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#107    ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#108    Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#109    ProxyElement.update
package:flutter/…/widgets/framework.dart:5136
#110    Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#111    ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#112    StatefulElement.performRebuild
package:flutter/…/widgets/framework.dart:4959
#113    Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#114    StatefulElement.update
package:flutter/…/widgets/framework.dart:4991
#115    Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#116    SingleChildRenderObjectElement.update
package:flutter/…/widgets/framework.dart:6204
#117    Element.updateChild
package:flutter/…/widgets/framework.dart:3517

package:flutter/…/widgets/framework.dart:3517
#118    ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#119    Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#120    ProxyElement.update
package:flutter/…/widgets/framework.dart:5136
#121    Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#122    SingleChildRenderObjectElement.update
package:flutter/…/widgets/framework.dart:6204
#123    Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#124    ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#125    StatefulElement.performRebuild
package:flutter/…/widgets/framework.dart:4959
#126    Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#127    StatefulElement.update
package:flutter/…/widgets/framework.dart:4991
#128    Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#129    ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#130    StatefulElement.performRebuild
package:flutter/…/widgets/framework.dart:4959
#131    Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#132    StatefulElement.update
package:flutter/…/widgets/framework.dart:4991
#133    Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#134    ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#135    Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#136    ProxyElement.update
package:flutter/…/widgets/framework.dart:5136
#137    Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#138    ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#139    Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#140    ProxyElement.update
package:flutter/…/widgets/framework.dart:5136
#141    Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#142    ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#143    StatefulElement.performRebuild
package:flutter/…/widgets/framework.dart:4959
#144    Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#145    StatefulElement.update
package:flutter/…/widgets/framework.dart:4991
#146    Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#147    ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#148    Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#149    ProxyElement.update
package:flutter/…/widgets/framework.dart:5136
#150    Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#151    ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#152    StatefulElement.performRebuild
package:flutter/…/widgets/framework.dart:4959
#153    Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#154    StatefulElement.update
package:flutter/…/widgets/framework.dart:4991
#155    Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#156    ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#157    Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#158    StatelessElement.update
package:flutter/…/widgets/framework.dart:4865
#159    Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#160    ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#161    StatefulElement.performRebuild
package:flutter/…/widgets/framework.dart:4959
#162    Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#163    StatefulElement.update
package:flutter/…/widgets/framework.dart:4991
#164    Element.updateChild
package:flutter/…/widgets/framework.dart:3517
#165    ComponentElement.performRebuild
package:flutter/…/widgets/framework.dart:4814
#166    StatefulElement.performRebuild
package:flutter/…/widgets/framework.dart:4959
#167    Element.rebuild
package:flutter/…/widgets/framework.dart:4511
#168    BuildOwner.buildScope
package:flutter/…/widgets/framework.dart:2655
#169    WidgetsBinding.drawFrame
package:flutter/…/widgets/binding.dart:882
#170    RendererBinding._handlePersistentFrameCallback
package:flutter/…/rendering/binding.dart:367
#171    SchedulerBinding._invokeFrameCallback
package:flutter/…/scheduler/binding.dart:1145
#172    SchedulerBinding.handleDrawFrame
package:flutter/…/scheduler/binding.dart:1082
#173    SchedulerBinding.scheduleWarmUpFrame.<anonymous closure>
package:flutter/…/scheduler/binding.dart:863
(elided 6 frames from class _AssertionError, class _RawReceivePortImpl, class _Timer, and dart:async-patch)
════════════════════════════════════════════════════════════════════════════════

 Code Sample

// flutter import
 import 'package:flutter/material.dart';

void main() {
  runApp(const BugReportApp());
}

class BugReportApp extends StatefulWidget {
  const BugReportApp({Key? key}) : super(key: key);

  @override
  State<BugReportApp> createState() => _BugReportAppState();
}

class _BugReportAppState extends State<BugReportApp> {
  final TextEditingController _dropdownController = TextEditingController();
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Bug Report',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: Flex(direction: Axis.vertical, children:[
                        DropdownButton<String>(
            value: _dropdownController.text == ""
                ? null
                : _dropdownController.text,
            items: ["hello, world", "how are you", "goodbye"]
                .map((_value) => DropdownMenuItem<String>(
                        child: Text(
                      _value,
                    )))
                .toList(),
            onChanged: (_value) {
              setState(() {
                _dropdownController.text = _value ?? _dropdownController.text;
              });
            },
          ),
      ],),
    );
  }
}

Logs

@Vedsaga
Can you check the documentation example for dropdown and compare its implementation with yours and see if are missing anything to implement properly ?

@Vedsaga Can you check the documentation example for dropdown and compare its implementation with yours and see if are missing anything to implement properly ?

Yaa it was missing value parameter in the DropdownMenuItem<String>().  Now it's solved...

Closing as resolved.


YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated

python script throws me the following error:
./simple-ansible-inventory.py:241: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
raw_confs_list.append(yaml.load(fd))

It was because of a deprecation of yaml.load in pyyaml>=5.1
I replaced yaml.load by yaml.safe_load` in https://github.com/leboncoin/simple-ansible-inventory/commit/14badff930cf0915591e391acb459f89728361ce
It will work now

cool!, thanks.


[regression in 0.4] Project doesn't install anything

cppurses-0.3 installed headers and the library, but termox-0.4 doesn't have the install target.

TermOx currently uses ncurses as a git submodule, and install of ncurses is tricky without hijacking the system default install, and cmake install commands are a bit of a mystery to me with something that isn't a cmake project(ncurses). I'll be attempting to replace ncurses very soon and hopefully that will enable the cmake file to have a simple enough install command again.

TermOx currently uses ncurses as a git submodule, and install of ncurses is tricky without hijacking the system default install, and cmake install commands are a bit of a mystery to me with something that isn't a cmake project(ncurses). I'll be attempting to replace ncurses very soon and hopefully that will enable the cmake file to have a simple enough install command again.

ncurses is available as a package on most systems.

ncurses is available as a package on most systems.

I've had problems in the past with the various versions of ncurses that are installed across systems, keeping it as a submodule has fixed that, but its not quite 'right'. I'm working on a light weight alternative.

I've had problems in the past with the various versions of ncurses that are installed across systems, keeping it as a submodule has fixed that, but its not quite 'right'. I'm working on a light weight alternative.

Latest main has install target now.


'gradlew' should be 'gradle' in README.md

On line 18 of README.md there's a single letter typo, where the letter 'w' has been inadvertently appended to gradle, making it gradlew.
Line 18 of README.md is:
"gradlew build" command or use "Import Project" in Android Studio.
and it should be:
"gradle build" command or use "Import Project" in Android Studio.

Sorry, I'm dumb, it is supposed to be gradlew.


vite http proxy error

Describe the bug
[vite] http proxy error:
Error: getaddrinfo ENOTFOUND xxx.com
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:71:26)
Reproduction
"/api":{
target: "http://xxxx.com",
changeOrigin: true,
rewrite: (path) => path.replace(/^/api/, '')
},
[vite] http proxy error:
Error: getaddrinfo ENOTFOUND xxx.com
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:71:26)
System Info
"vite": "2.0.1",
"vue": "^3.0.5",

Used Package Manager
yarn
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

You are using an old version of Vite. Please test your issue against the latest version of Vite and open a new bug report if you still see this problem with a minimal reproduction as GitHub repo.


[Python] Clean up python client code, add logging.

Problem
After debugging some user issues i feel like we could add some more logs, so that we can deduce more information about what's happening inside OpenLineage.
Also, at the moment the whole process of resolving what transport we will have is distributed in three places (factory, client and utils), i moved everything to one location so it's easier to grasp.
One-line summary:
Clean up python client code, refactor logging in all python modules.
Checklist

[X] You've signed-off your work
[X] Your pull request title follows our guidelines
[X] Your changes are accompanied by tests (if relevant)
[ ] Your change contains a small diff and is self-contained
[ ] You've updated any relevant documentation (if relevant)
[ ] Your comment includes a one-liner for the changelog about the specific purpose of the change (if necessary)
[ ] You've versioned the core OpenLineage model or facets according to SchemaVer (if relevant)
[ ] You've added a header to source files (if relevant)

SPDX-License-Identifier: Apache-2.0
Copyright 2018-2023 contributors to the OpenLineage project

Probably #2655 should be merged first, to have the CI fix in a separate small PR

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

Project coverage is 84.84%. Comparing base (2cc09ec) to head (e6a84db).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2653   +/-   ##
=======================================
  Coverage   84.84%   84.84%
=======================================
  Files          59       59
  Lines        3398     3398
=======================================
  Hits         2883     2883
  Misses        515      515

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


add schema parameter to table provider factory create method

Which issue does this PR close?

Closes #4142.
Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?
TableProviderFactory::create is a public interface and change will be backward incompatible, but as this interface is in state of flux recently it would make sense to break it now

thanks @andygrove,
I've added test which should check if table schema is according to ddl provided in the crate statement. Let me know if you have some other cases to test.

@avantgardnerio may be interested in reviewing this as well

thanks @alamb, looks like #4126 did most of the job I was intending with this pr, schema can be extracted from cmd directly. so this pr at the end contributes test for part of #4126


Remove /public in URL not working if using localhost

During the creation of examples for my book on CI4 and tutorials to help the Brazilian community, I came across the need to configure the URL so that /public is not displayed without changing the default framewoprk structure.
I created a .htaccess file at the root of the application containing the following code:
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{REQUEST_URI} !^public
RewriteRule ^(.*)$ public/$1 [L]
</IfModule>

When I use a virtual host (eg http://public-htaccess.test) this code in .htaccess works normally, but if I get the same structure of the application using localhost (http://localhost/public-htaccess ) the code does not work correctly, says that the controller was not found, as he understands that the controller is public-htaccess.
Could someone tell me if it is possible to do this redirection for the use case with localhost and how would it be the correct way within the framework standards?
The documentation in this regard is not clear, so if you can give me feedback on this issue, I can also supplement the documentation with this information.
OS: Win10
Apache: 2.4.41
PHP: 7.4.5
CodeIgniter: 4.0.3
P.S.: @lonnieezell and @samsonasik can you help me?

probably add .htaccess to root project with the following content:
RewriteEngine On
RewriteRule (.*) ./public/$1

Thanks for the feedback @samsonasik!
What I really need is to remove /public from the URL, leaving it clean, and not redirect to /public explicitly. For example:
Current: http://localhost/public-htaccess/public
Required: http://localhost/public-htaccess
But I need to do it in a way that does not require any changes to the framework structure or the configuration of paths in the settings.
When I apply the code presented in this issue to a virtual host, it works perfectly, even if the root directory configured on vhost is not /public, but the application root.
But if I apply the same code using localhost/public-htaccess, it doesn't work as expected, it redirects to localhost/public-htaccess/public.
I know that via htaccess there is no way to change the root directory. In this case of localhost, the only way would be a redirect, with /public explicit in the URL?

From the way your rewrite rules were written, I believe you need to set your httpd.conf to change the ServerName to localhost/public-htaccess. Since you are rewriting your URIs, /public-htaccess is treated as a URI rather than a part of the base URL.

@jlamim could you verify if it related with https://github.com/codeigniter4/CodeIgniter4/issues/2965 and fixed by @Instrye at https://github.com/codeigniter4/CodeIgniter4/pull/2978 ?
The .htaccess example by at @willnode at https://github.com/willnode/crm-toolkit/blob/master/api/.htaccess

@jlamim Could you test with the latest code? Also check the links from @samsonasik above.

This issue is too stale and no feedback have been received so far. Closing.


Add coerce_numbers_to_str option in StringSchema

Change Summary
Adding coerce_numbers_to_str option in StringSchema typed dict definition

Related issue number

Checklist

[x] Unit tests for the changes exist
[x] Documentation reflects the changes where applicable
[x] Pydantic tests pass with this pydantic-core (except for expected changes)
[x] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

please review


Make Ipython qtconsole widget more intuitive

From<EMAIL_ADDRESS>on 2012-06-06T19:13:27Z
The ipython console is shaping up very nicely, and I'm really enjoying using this feature. However, it seems that it could be confusing to a user who is not familiar with Ipython. In particular:

You should be able to start a new client with a connected kernel directly from the Ipython widget

Possibly the naming of each tab as a "client" is confusing. Most people would expect these to be called consoles

It seems a bit clunky having to switch to the console widget for the corresponding kernel (although I understand that this was the easiest way to build from the existing system)

I guess what I would like to see is a system which hides the complexity of kernels and clients by default, but makes it easily available for more advanced users.
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=1083

From ccordoba12 on 2012-06-07T07:55:18Z
You're totally right David. I've been thinking for a while about this issue and I agree that the difference between kernels and clients is not easy to grasp if you don't know the IPython architecture and shouldn't be shown by Spyder to not confuse our users.
About your suggestions:

Yes, we have to add a menu option to open a new client directly from the ipython widget. It's in my todo list.

We could change the tabs name from "Client" to "Console". I don't see any problem with that, although I would like to know what Pierre thinks about it.

But what about the number added to distinguish one console from another? It's the kernel id of course, but that's probably not intuitive either. What do you think we should do with that? Should we just name consoles with increasing numbers?

Yes, we need to avoid showing kernel creation on the console widget while creating IPython consoles. It's on my todo list too.

Status: Accepted
Cc: pierre.raybaut
Labels: MS-v2.2

From<EMAIL_ADDRESS>on 2012-06-07T16:44:28Z
Carlos, I'm don't see a problem with having the kernel id as the console number. Although beginners won't understand what it means, I don't think it would cause any great confusion for them. Hiding this number would then be annoying for advanced users who do want to know about kernel ids.

From ccordoba12 on 2012-06-08T21:04:23Z
Ok, I see. Then just leave like that.
I'm working right now to solve these issues. I've made good progress but they've showed some more usability problems I'm trying to solve.
Labels: -Priority-Low Priority-High

From ccordoba12 on 2012-06-18T11:48:38Z
This issue was updated by revision 0cb3b361fede .
-. Change menu entry from 'Start a new IPython kernel' to 'Open an IPython
console'.
-. Don't focus the external console while creating the kernel. Instead focus
the IPython console.
Status: Started

From ccordoba12 on 2012-06-18T11:48:43Z
This issue was updated by revision c8d088eadb76 .

From ccordoba12 on 2012-06-18T11:54:50Z
David, I think I covered all your suggestions with my last commits. Please test them and if you consider this is the case, close the issue with a 'Verified',  else we could continue the discussion :-)
Owner: ccordoba12

From ccordoba12 on 2012-06-18T11:48:44Z
This issue was updated by revision 0926eb3cbb0a .

From ccordoba12 on 2012-06-18T11:48:43Z
This issue was updated by revision 46e28d7e5538 .

Remove it from the External Console options menu

From ccordoba12 on 2012-06-22T11:36:18Z
Ok, I just pushed some changes that fix the two problems you reported.
Unfortunately we can't remove the kernels from the external console and they have to there, i.e. we can't put on any other plugin. However, I think we can improve the situation for people that uses both the console and IPython console doing this:

Grouping all kernels at the beginning of the console.
Not writing the kernel name on the tab and putting it instead on the tab tooltip. This way kernels would appear as pinned tabs, like in Firefox or Chrome. Please take a look at screenshot I'm attaching to see what it could look like.

David, Jed, what do you think?
Cc<EMAIL_ADDRESS>Attachment: improvements.png

From<EMAIL_ADDRESS>on 2012-06-18T17:32:46Z
Carlos, I am using the ipython qtconsole, and I think you have made some good improvements. So far I've noticed a couple of issues:

If you close a console, and select "no" when it asks about closing the kernel, it becomes impossible to close the kernel, as you cannot close its tab.

Sometimes I run a script in its own dedicated python console instead of in the existing ipython console. In this case the console widget comes to the front, however focus does not switch to the regular python console tab, but stays on the tab for a previously opened ipython kernel. (Maybe this should be a separate issue)

From a user interface perspective, I'm still undecided about having the ipython kernel tabs within the console widget - somehow they seem to get in the way. I'm not sure that they would be any less annoying if they were attached to the ipython widget. Occasionally I do need to refer to them because that's where stderr gets redirected, so hiding them somehow wouldn't be ideal either. At this stage I don't have any suggestion that seems more satisfactory than the current arrangement, so maybe this should wait for more user feedback.

From<EMAIL_ADDRESS>on 2012-07-10T22:36:13Z
I would say at this stage the major problems have been fixed. Discussions about where to put kernel tabs are of pretty minor importance. I'm not sure that Carlos' proposal has any advantage over the current situation.
I'd be happy to consider this issue closed if nobody else objects.

From ccordoba12 on 2012-07-05T20:14:35Z
Blocking: spyderlib:1053

From<EMAIL_ADDRESS>on 2013-01-26T19:28:04Z
Status: Fixed


Bug? ConfigureApplicationCookie does not work when cookie.name = x

ConfigureApplicationCookie does not work when cookie.name = x
I have had an issue with authenticating my login, and i finally figured out that my cookie was not beeing applied when i had set
services.ConfigureApplicationCookie(options => {
  options.Cookie.Name = "MyCustomIdentityCookie";
  options.AccessDeniedPath = "/home/denied";
  options.LoginPath = "/home/loginRequired";
});

however, when using:
services.ConfigureApplicationCookie(options => {
  options.Cookie.Name = "My.Custom.Identity.Cookie";
  options.AccessDeniedPath = "/home/denied";
  options.LoginPath = "/home/loginRequired";
});

it works fine, i'm thinking this is a bug or am i wrong?

@StanlyLife is this still an issue? I'm triaging some old issues and found this one.
@JeremyLikness is this something you can help with?

@StanlyLife what type of app is this? ASP.NET Framework? ASP.NET Core? I can get it moved to the right spot if I know more details and it's still an issue.


[RFC] Certificate DB Migrations

NOTE this should wait for
https://github.com/aerogear/aerogear-unifiedpush-server/pull/502 to be merged
first

integrated on #502


[Bug] Wrong output folder when output_folder of DataAccess has a different absolute path

Search before asking

[X] I searched the issues and found no similar issues.

Component
Library/core
What happened + What you expected to happen
If a local DataAccess for a Transformer has the following  input and output folders:
input_folder = ./test
output_folder=/tmp/output

And the current execution directory is /Users/home/foo.
The output files will be generated in /Users/home/foo/tmp/output instead of /tmp/output
BTW, the metadata.json file will be in the right location.
Reproduction script
For example, execute ./transforms/universal/filter/python/src/filter_local_python.py when input_folder is ../test-data/input and output_folder is /tmp/output
Anything else
Every time
OS
Ubuntu
Python
3.10.x
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

done by https://github.com/IBM/data-prep-kit/pull/387


CustomPackets are not checked if they have been received

All CustomPackets received by the handler are not checked to see if their sequence number has been received before.

Fixed in version 1.4


Environmonet Variables Different than vscode terminal

I'm having a strange issue with environment variables being different in the runme dev cells versus the vscode terminal. I am using a tool called direnv which loads a .envrc file in the workspace. Vscode handles the env very well. Runme on the other hand is clearly loading the environment differently somehow and creating different results.
Here is how I can tell.
In my .bash_profile I don't have AWS_CONFIG_FILE but I do have AWS_PROFILE.
export AWS_PROFILE="global-profile"

In my workspace the .envrc does set AWS_CONFIG_FILE and AWS_PROFILE.
export AWS_CONFIG_FILE="/the/workspace/aws/config"
export AWS_PROFILE="workspace-profile"

Then I simply run this:
echo $AWS_CONFIG_FILE
echo $AWS_PROFILE

Output in the runme cell. TheAWS_PROFILE is the value coming from the .bash_profile and seems to be overwriting the workspace level value. The AWS_CONFIG_FILE is the value in the .envrc because it does not exist in the .bash_profile. The fact that AWS_CONFIG_FILE is actually loaded correctly shows that along the way runme is actually loading the correct environment, and then doing something extra.
/the/workspace/aws/config
global-profile

Here is the correct output if I just copy paste from the readme into the terminal. Notice the AWS_PROFILE is now the correct value originating in the workspace directories .envrc and actually exists in the AWS_CONFIG_FILE.
/the/workspace/aws/config
workspace-profile

I used the runme feature to open the same command in a terminal and have confirmed the same as above in a terminal spawned by runme. The terminal did show off the following extensions to the terminal but all the terminals showed the same including working ones.
# Terminal Environment Changes

## Extension: stateful.runme

- `PATH=/Users/me/.vscode/extensions/stateful.runme-3.10.0-darwin-arm64/bin:${env:PATH}`

One note I realized, when I do open a new terminal, direnv will run immediately and set all those env vars. It basically runs source .envrc when you cd into a directory with a .envrc.  Either way though, runme is actually reading all the variables set within .envrc and loaded by direnv, it's just overwriting them with anything set within my .bash_profile, this is backwards.
Last note on this issue, I figured I would be able to do this in one cell
export AWS_PROFILE=foobar

and actually print the value in another cell.
echo $AWS_PROFILE

But the value doesn't change.
Is there anything I can do here or is this just a bug that needs fixing?

Hi @kferrone. Thank you for reporting this. We'll take a look and get back to you.

Skip ahead of the direnv stuff. The short answer is that Runme ignores subsequent values because the ENV store already has a value for AWS_PROFILE, which is why it will ignore subsequent values by default (cell's promptEnv=auto).
The reason is that docs often come with invalid placeholder values, e.g., AWS_PROFILE=[your-profile], and Runme will, by default, put a higher value on .env or profile-loaded ENV values if present.
While this is unintuitive for "Shell-Scripters," it's not a bug; it's a feature. The short-term workaround would be to set the respective cells' prompt mode to Always as per the screenshot below. However, this will ask you to enter the respective value.
Now, not everyone is using Runme in this "docs-first" scenario. We are working on an additional mode, let's say shell, that, when set, will overwrite values in subsequent order and provide a setting to set the default behavior according to users' needs. We expect this new mode to be available in the next few weeks. I will respond to the direnv aspects separately.

In the interim, another workaround I thought of is to wrap the value into a shell expression that Runme will always "run" at face value. This should do the trick until we solve this at the core.
export MY_NAME="$(echo 'Sebastian')"

https://gist.github.com/sourishkrout/9e78330db9963b7575a84ff143709e11#file-source-01jdqjh5n66yfrp6whc5zxm0xk-md

One note I realized, when I do open a new terminal, direnv will run immediately and set all those env vars. It basically runs source .envrc when you cd into a directory with a .envrc. Either way though, runme is actually reading all the variables set within .envrc and loaded by direnv, it's just overwriting them with anything set within my .bash_profile, this is backwards.

Regarding direnv, @kferrone: Based on how Runme's implementation to seed the environment currently works, your observations make sense to me. Supporting direnv is high up on the Runme roadmap, whether that means "fixing the order" or integrating it more natively is TBD.
Is the absence of Runme <> direnv blocking you from using Runme? I'd love to help you get unblocked in the interim.


Expand the number of fonts offered  as options

This issue is a Enhancement
Related issue(s) and/or pull request(s)
Dyslexic font support:  https://github.com/readium/readium-js-viewer/pull/540
Expected Behaviour
Offer two more fonts, one serif and one sans-serif in addition to the Dyslexic font
Steps to reproduce

Add two new fonts to the build
Verify that they show up in the UI

Test file(s)
None
Product

Readium Chrome extension

latest official version available from the Chrome Web Store

from @danielweck  on 8 Dec:
There isn't a well-defined process to add / remove custom fonts yet.
It's trivial for online web fonts (absolute URL pointing to a CSS file that declares the font faces), but local fonts have to be included in the build, and that's configuration-heavy (build scripts).
As an example, see the PR diff and search for "dyslexic":
https://github.com/readium/readium-js-viewer/pull/540/files
Ideally there would be a whitelist/blacklist mechanism similar to readium-shared-js plugins, so that only one config file would need to be changed (like the include / exclude directives in plugins.cson)

Ah, cross-postings :)
I implemented this a few minutes ago.
Test here:
https://readium.firebaseapp.com

Email copy:
I've just introduced a "simple" mechanism (i.e. cheap to implement and
not convoluted, unlike some of our RequireJS scripts), so that we can
easily configure the fonts to include during the build process of the
cloud reader / Chrome app.
It basically boils down to a Javascript array defined in a central
location (font.js):
https://github.com/readium/readium-js-viewer/blob/develop/src/fonts/fonts.js#L1
...alongside the font files themselves, inside the src/fonts/ folder
(by convention, each font has its own subfolder, containing CSS, WOFF,
SVG, etc.):
https://github.com/readium/readium-js-viewer/tree/develop/src/fonts
When the command "npm run dist+sourcemap" is invoked, files from the
src/fonts/ folder are copied into the destination "dist" folders for
each target platform (which is a normal part of the build process,
nothing new here), and the unmodified fonts.js file is executed at
runtime so that each platform can configure its absolute URL scheme
(again, same principle for all other resources included in build
artifacts).
This makes it trivial to extend support for new targets, such as
Electron, Apache Cordova, etc. In fact, I will update the feature
branch to synchronize it with the latest develop codebase.

So, the current font list is:
https://github.com/readium/readium-js-viewer/blob/develop/src/fonts/fonts.js#L1
[
    {
        displayName: "Open Dyslexic",
        fontFamily: "OpenDyslexic",
        url: "OpenDyslexic/OpenDyslexic.css"
    },
    {
        displayName: "Open Sans (Google web font)",
        fontFamily: "Open Sans",
        url: "https://fonts.googleapis.com/css?family=Open+Sans"
    },
    {
        displayName: "Old Standard TT (Google web font)",
        fontFamily: "Old Standard TT",
        url: "https://fonts.googleapis.com/css?family=Old+Standard+TT"
    },
    {
        displayName: "Noto+Serif (Google web font)",
        fontFamily: "Noto Serif",
        url: "https://fonts.googleapis.com/css?family=Noto+Serif"
    },
    {
        displayName: "Bitter (Google web font)",
        fontFamily: "Bitter",
        url: "https://fonts.googleapis.com/css?family=Bitter"
    }
]

Thanks Ric. We can discuss the details of what font to use exactly. The configuration mechanism now makes this easy for anyone.


Activate Flashlight on Android Device

Is there an Option to activate the Flashlight on Android?

please use isShowFlashIcon param. closing the issue now


Investigate usage of   'react/require-default-props' & 'react/default-props-match-prop-types'

Recently, the following was added to the .eslintrc.js file to warn about new linting rules.
    'react/require-default-props': ['warn'],
    'react/default-props-match-prop-types': ['warn']

It seems like these should be errors, however, more research should be done. This issue is to investigate the new rules.
If the rules should be errors, then this issue will require code changes to conform to the new lint rules.
If the rules should be turned off, then only configuration changes will be necessary.

Link FE-494

Could I get assign to work on this?

@YimniChan I've assigned this to you.

The react/require-default-props rule should be an error.
If we do not set any default props, the undefined display should take place of the props that are not sent by the parent component. In execution, an undefined variable may cause the application to break if it is used and there are no safety precautions in place. We do not want that to occur. Furthermore, we should set a defaultProps value, and when a prop is missing, the defaultProps value will replace the undefined.
The react/default-props-match-prop-types rule should be turned off.
In the naming convention used in code, variable names usually have the same name as its props variable, even if they are not in the same file. PropTypes exports are for validating the data type is match and valid. It seems not necessary in this case. Furthermore, projects have interfaces that provide the benefit of type-checking values shape. The props that are passed around normally follow interface rules. Interface set or applies the requirement properties and their type. When we try to use the properties for the variable, the system just checks did the object we pass to the function meets the requirements listed. If the object did not meet the requirement property, it will print the error message.

@fox1t


Can't open links in a new tab

While browsing the Material UI doc website, it is not possible to do right click on a component-link and open it in a new tab.
For example, it is not posible to browse the list of components and open a new browser window/tab for each of them. Instead I am forced to manually copy the url and paste it into a new window.
Is there any shortcut to avoid this? Or is it a problem considered in the roadmap?

That's a good point. We could do it by following https://jsfiddle.net/g3thx9e9/.

I just added the linkButton property to the ListItems and made it true. Then just add the href which contains the location of that page. Since ListItem includes 'EnhancedButtonandlinkButtonis a property ofEnhancedButton`, this works perfectly fine. I have included an example below.

@oliviertassinari Have a look at it!

@aahan96 Nice finding :+1:.

@oliviertassinari - given that were using ReactRouter, which is more idiomatic, @aahan96's solution, or containerElement={<Link to="/path" />? (I admit I haven't tested either...)

@mbrookes in my own app I just have ListItem wrapped in Link:

Huh, wonder why we even have containerElement then? Perhaps ListItem used to have to be an immediate child of List?

@nathanmarks I don't think that we can use your solution as the list is implemented. We are using this HOC https://github.com/callemall/material-ui/blob/887297d3a289a0ae100d006bcc53e933b2ff6e30/src/List/MakeSelectable.js.

for everyone whos looking in 2024+ for it:
Example


set up migration context directly

it seems like the connection method migration_context was removed in Rails 7.2. As a result, --autofix raises a NoMethodError. With this change (largely borrowed from the Combustion gem), it should be possible to create a MigrationContext on Rails 6 and 7, even if the connection object doesn't provide one directly. At least, these changes work for me on Rails 7.2.

Thanks - I’m running into the same issue you describe and your branch appears to fix it for me.

Hi @indirect @tysongach,
Thank you for reporting this! I'm sorry it took me so long to fix it in the released version.
Here is the fix: https://github.com/djezzzl/database_consistency/pull/241

Thank you for using the gem! Please let me know if you find anything else or have an idea of how to improve it!

Released 1.7.27.


VirtualHost parameter inconsistently defined

The following functions have the VirtualHost parameter set to mandatory and do not provide a default value:

Add-RabbitMQMessage
Add-RabbitMQPermission
Add-RabbitMQQueue
Add-RabbitMQQueueBinding
Copy-RabbitMQMessage
Move-RabbitMQMessage
Remove-RabbitMQPermission
Set-RabbitMQPermission

The following functions have the VirtualHost parameter set to mandatory (but do provide a default value):

Clear-RabbitMQQueue
Remove-RabbitMQQueueBinding

I feel like optional with default value is the way to go for all of them, but wanted to get feedback before I submit a PR.

Agreed, makes sense to me!
Looking for $defaultVirtualHost, I only see it defined in constants.ps1, which is only called in the tests. Might switch these over to hard coded '/', or setting up a module config of sorts. A variable seems difficult to discover.

Isn't it called in the psm1?
I'm going to update the parameters to use the variable, and later if we add persistent settings that process will just need to update the variable.


[MENFORCER-142] documentation - add example for checking rules via cli

Introduce an example site with example "check specific rule via cli"

Your PR has been merged. Thanks for your contribution. You can close your PR...

Hi. When this feature could be release on public mvn repo ?
Thanks.

I would have use for this as well, when is 3.0.0-M3 released?

Waiting for this too.

Waiting for this too.

Waiting for this too.

I'm waiting for this too.

Waiting for this too.

Hi @khmarbaise ,
did you know when the next release will be build?
I will currently try to use a snapshot but it would be nice if we got a official release version.
Thanks @sparsick for your fix! ;)

HI!
I am using maven-enforcer-plugin:3.0.0-M2.
I have this in my pom.xml and it is working fine when mvn verify
<plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-enforcer-plugin</artifactId>
                <executions>
                    <execution>
                        <id>enforce-banned-dependencies</id>
                        <goals>
                            <goal>enforce</goal>
                        </goals>
                        <configuration>
                            <rules>
                                <bannedDependencies>
                                    <excludes>
                                        <exclude>x.y:logger:(,10.93)</exclude>
                                        <exclude>x.y:soap-utils:(,10.93)</exclude>
                                        <exclude>x.y:correlation-id:(,10.93)</exclude>
                                    </excludes>
                                </bannedDependencies>
                            </rules>
                            <fail>true</fail>
                        </configuration>
                    </execution>
                </executions>
            </plugin>

Is there any way to get rid of pom.xml setup and get the same behaviour with the CLI?
Thanks!

@destebanm until 3.0.0-M3 release no CLI is possible with rules.
In the master branch you can build the sources and use it till the release is done.
I do the same.

Thanks @Mazorius!
Do you know when the release is expected?

Do you know when the release is expected?

I know as much as you do. :-)

Hi!
I have built the snapshot and the CLI is working but I don´t know how to use it.
I am able to run commands like that:
mvn enforcer:enforce -Drules=alwaysFail
but I would like to run this with the CLI
        <bannedDependencies>
           <excludes>
              <exclude>x.y:logger:(,10.93)</exclude>
              <exclude>x.y:soap-utils:(,10.93)</exclude>
              <exclude>x.y:correlation-id:(,10.93)</exclude>
           </excludes>
        </bannedDependencies>

Is there any kind of documentation about how to use the CLI??
Thanks!!

I had me doubts about this feature, but the commmunity was asking for it and it didn't really do any harm, but it is kind of un-Maven-ish.
Being able to enforce rules from commandline means you cannot configure them.
Maybe this feature should be pushed to a higher level (maven-core) to solve this for plugins in general.

@destebanm yes, a documentation exists for this feature. But it also isn't release. But you can generate it by yourself with the following commands:
mvn clean verify site

Open in your browser the following file
<path to enforce project>/maven-enforcer-plugin/target/site/examples/check-specific-rule-via-cli.html

Your command looks well. No idea without debugging, why it is ignoring your setting.

Any news on the M3?
This would be really helpful


⚠ ClamAV has degraded performance

In 114f79c, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 724 ms

Resolved: ClamAV performance has improved in 9ba55ba.


Azure Container "Registry" instead of "Repository"

In chapter "Dataflow", bullet point 3, it currently reads:

...publishing ... in a non-production Azure Container Repository.

This should rather be:

...publishing ... in a non-production Azure Container Registry.

Thanks and best regards,
Chris

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

ID: 8f6e327d-b280-a35c-2588-87a19ac2a4ba
Version Independent ID: fa9b0713-771f-4792-979a-2f7a4f4445a2
Content: CI/CD for AKS apps with Azure Pipelines - Azure Guide
Content Source: docs/guide/aks/aks-cicd-azure-pipelines.yml
Service: architecture-center
Sub-service: azure-guide
GitHub Login: @RobBagby
Microsoft Alias: robbag

@candritzky
Thanks for reporting this document! @gottagetgit thank for creating a PR for this issue and your changes sent to author, Once author approval changes will be alive soon.


Checking for presence of liblinux based on IVsConnectionManager service.

Check for the presence of liblinux based on availability of IVsConnectionManager service

@gregg-miskelly @wesrupert

@itodirel FYI

LGTM

Otherwise LGTM! :shipit:

merged to upstream by accident using git extensions. fixed it.


Add the client version into the executable file

Show the version into the logs.
Add a --version option as a command into the client

Done in alph3


Radio task runs after transition to safe mode

This, combined with the enable_low_power() function only being called on the transition results in the radio remaining in listening mode.

That's frustrating, it makes sense why it is happening though.
If we had more time I'd make the state transitions work this way:

Wait for all tasks to finish
Run transition functions
Start up relevant tasks for new state

Unfortunately we are missing (1), I think we'll have to do a hacky fix unfortunately.


fix: migration guide fixes

Related issue
Closes #
Scope of work
There was a little mess in migration guide. Additions and Changes were duplicated and some data was not in the right place. Also deleted comments that will be added with proper PR
Screenshots of visual changes

Checklist

[ ] No commented blocks of code left
[ ] Run tests and docs
[ ] Self code-reviewed
[ ] Changes documented

If applicable:

[ ] I followed composition rules for my component
[ ] I tested the component in most common device sizes (can be tested in Storybook from viewport addon in top menu)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

MIgration guide updated. To be updated on release branch.


How to stop the python main.py in apollo docker?

I tried Ctrl+C, but it didn't work. At present, I can only directly shut down the terminal and then re-enter the Docker to resolve the issue.

Because an infinite loop is used in the program, ctrl+c cannot exit, and we will fix this problem later.
You can use ctrl+z to exit, if there is an exception after exiting, you can kill the process

Thank you very much for your reply


fix: Reuse of Qdrant process pool should work

This can be validated by running this config:
{
    "name": "qdrant-parallel-error",
    "engine": "qdrant",
    "connection_params": { "timeout": 30 },
    "collection_params": {
      "optimizers_config": { "memmap_threshold": 10000000 }
    },
    "search_params": [
      { "parallel": 16, "search_params": { "hnsw_ef": 128 } },
      { "parallel": 32, "search_params": { "hnsw_ef": 128 } },
      { "parallel": 64, "search_params": { "hnsw_ef": 128 } },
      { "parallel": 100, "search_params": { "hnsw_ef": 128 } }
    ],
    "upload_params": { "parallel": 16, "batch_size": 1024 }
}

I ran it 3 times and it failed every time but now it doesn't. The fix done by @qbx2 to fix the process leak also fixes this.
This doesn't impact numbers in the CI benchmarks and makes the benchmarking smoother.

@generall please review


Org Users in Production cannot use the same email for sign up as their individual user email

In staging, we allow users to sign up for 1 organization with the same email as their individual user email. In production, we do not allow for this behavior.
@galeza - please confirm that you are still seeing this behavior in prod vs staging
Ideally, production should reflect staging. Thoughts? @idjevm @joshmorel

I have tested the just now and yes:
In STG ->  Org Profile can be created once with the same email as of Individual user.
Test data used in STG and PROD<EMAIL_ADDRESS>In PROD -> Unable to create the Org with the email of the individual user.

Yeah Ideally we want production to reflect staging, but I think right now we should focus on production since we have already deployed, and then figure out staging once soft launch is done.

So the index was missing and there were many duplicates in staging :shrug: . I resolved that by tweaking duplicate org emails and added the index manually so both environments should disallow this:

I guess we should close this.

Closing this


Change format of generated layers to OME

This PR changes the format of the generated layers (segmentation, mask, sampled positions, and acquisition function) to follow the OME format V4.

This PR solves #28


BuildStream crashes when we try to use the same junction twice, but named differently

See original issue on GitLab
In GitLab by [Gitlab user @jennis] on Nov 29, 2018, 11:41
I have a BuildStream project that depends on two junctions (junctionA and junctionB). JunctionA also depends on junctionB.
Now, if in my project I declare the junction element 'junction-B.bst', and in the junctionA project I declare the junction element 'junction-B-diff-name.bst' (i.e. a junction element representing the same junction but just with a different filename) BuildStream will crash when trying to use things from junctionB via my project (e.g. junction-b.bst:foo.bst) and via junctionA's junction to junctionB (e.g. junction-A.bst:junction-B.bst:bar.bst).
I appreciate it's hard to picture what I've described above, so I've created a project which replicates this bug here:
https://gitlab.com/jennis/bstjunctionsbug
This is what happens when I try to build something that depends on the same junction in two different ways:
 $ bst build use-junctions.bst
[--:--:--][][] START   Build
[--:--:--][][] START   Loading elements
[00:00:00][][] FAILURE Loading elements
[00:00:00][][] FAILURE Build

base.bst [line 3 column 2]: Dictionary did not contain expected key 'kind'

I'm 100% sure that base.bst does contain kind. This exists in junctionB and I'm able to build it in the junctionB project.

This error is misleading/incorrect
BuildStream shouldn't crash when the junction is named differently in two projects

Important note
Bare in mind that if we change the junction element name in our project from 'junction-B.bst' to 'junction-B-diff-name.bst'
BuildStream won't crash. However, IMO I think BuildStream should be able to handle inconsistent naming.

In GitLab by [Gitlab user @jennis] on Nov 29, 2018, 11:42
changed the description

In GitLab by [Gitlab user @jennis] on Nov 29, 2018, 13:29
changed the description

In GitLab by [Gitlab user @jennis] on Nov 29, 2018, 15:12
UPDATE
After a brief discussion with [Gitlab user @juergbi], we suspect that this could be related to del source[Symbol.KIND] in loader.py

In GitLab by [Gitlab user @juergbi] on Nov 29, 2018, 15:22
I suspect this is caused by the recently merged YAML cache feature. With it _yaml.load() may return the same object for multiple calls. However, as the loader manipulates the loaded YAML (e.g., deleting the source kind keys mentioned above), this breaks.
[Gitlab user @jonathanmaw] Can you please take a look at this?

In GitLab by [Gitlab user @jonathanmaw] on Nov 29, 2018, 17:02
This does seem to be caused by the yaml cache - the yaml cache is effectively keyed by the project's name, the file's path within the project, and the raw contents of the file, all of which are identical for both junction-B.bst:base.bst and junction-B-foo.bst:base.bst.
I managed to avoid the error by deserialising the element from the pickle every time I retrieve from the cache, which was good enough to get it to work, but is poor for performance.
I'll see what other options I have for making sure that these elements are not considered identical.

In GitLab by [Gitlab user @jonathanmaw] on Nov 29, 2018, 17:17
mentioned in commit 76e3e1ac291f76d395f1e13f81720416b22801d2

In GitLab by [Gitlab user @jonathanmaw] on Nov 29, 2018, 17:20
mentioned in merge request !980

In GitLab by [Gitlab user @jonathanmaw] on Nov 29, 2018, 17:33
mentioned in commit 9c2881c74628837d3e7dac4840ff11e7c0984e32

In GitLab by [Gitlab user @jonathanmaw] on Nov 29, 2018, 17:34
That merge request ought to solve that problem, now.

In GitLab by [Gitlab user @jonathanmaw] on Nov 29, 2018, 17:49
mentioned in commit 8ad421028dfcf8f749a35fe9045e28b14249a63b

In GitLab by [Gitlab user @jonathanmaw] on Nov 29, 2018, 17:58
mentioned in commit c4ccf7f2488a9e3dcf40bf6bca4b6091f6497b17

In GitLab by [Gitlab user @jennis] on Nov 30, 2018, 17:16
mentioned in commit 61ce3dd69b78de0e104f8ac3fbfae69a7eefa2ef

In GitLab by [Gitlab user @jonathanmaw] on Dec 3, 2018, 13:24
mentioned in commit 6fcfa4524a83261746718a4e3f61fb5348bb06d7

In GitLab by [Gitlab user @jennis] on Dec 3, 2018, 13:24
mentioned in commit d0f9c7241fc0f22bf225ebf1e34e88b1e96ec5eb

In GitLab by [Gitlab user @juergbi] on Dec 3, 2018, 16:27
closed via merge request !980

In GitLab by [Gitlab user @juergbi] on Dec 3, 2018, 16:27
mentioned in commit f75810265aa8cc898ef570fd3129ae31b1e326a8

In GitLab by [Gitlab user @tristanvb] on Dec 4, 2018, 06:15
[Gitlab user @jonathanmaw], [Gitlab user @juergbi]; It appears to me that #790 might be related to this as well.
I.e. we expect specific behaviors from the nodes loaded by the ruamel.yaml library and the ChainMap we internally use for making shallow copies (deleting non-existing keys usually succeeds without raising an error); but perhaps this behavior is changed by the yaml caching ?
Maybe we need to change some code to ensure we treat the loaded yaml more like regular python dictionaries ?


Identify table

How do I tell the worksheet what the table name/range is so that I can use it in an 'f' definition?

I want to be able to do something like this (shown when I printed out the value from doing an XLSX.read() call)...but of course not explicitly set the v value.

The implicit variables hinge on the presence of "Format as Table" tables which are a part of our Pro offering


[Dashboard] [intermittent] Displays incorrect output when we access Test Grid dashboard directly

Description:
Sometimes when we access Test Grid dashboard URLs directly, it displays incorrect output. We suspect its because of browser cash and have to investigate further and identify the root cause.

Affected Product Version:
Test Grid - 0.9.0-m28

Cannot reproduce.


Stateless firewall rule config example has error

Describe the bug
The LZA code describes a stateless firewall rule configuration that fails because it is missing a protocol
To Reproduce
Create a stateless firewall rule as described here: https://github.com/awslabs/landing-zone-accelerator-on-aws/blob/main/source/packages/%40aws-accelerator/config/lib/models/network-config.ts#L5921
eg.
      - name: TESTSTATELESS
        regions:
          - *HOME_REGION
        capacity: 10
        type: STATELESS
        ruleGroup:
          rulesSource:
            statelessRulesAndCustomActions:
              statelessRules:
                - priority: 100
                  ruleDefinition:
                    actions:
                      - aws:pass
                    matchAttributes:
                      sources:
                        - <IP_ADDRESS>/16
                      sourcePorts:
                        - fromPort: 1024
                          toPort: 65535
                      destinations:
                        - <IP_ADDRESS>/16
                      destinationPorts:
                        - fromPort: 22
                          toPort: 22

This returns an error during the Deploy | Network_Prepare action:
AWSAccelerator-NetworkPrepStack-413126159926-ap-southeast-2 \| 10:29:51 PM \| CREATE_FAILED        \| AWS::NetworkFirewall::RuleGroup                  \| TeststatelessNetworkFirewallRuleGroup (TeststatelessNetworkFirewallRuleGroupD0D2CB93) Resource handler returned message: "SourcePorts, Protocols cannot exist together, parameter: [(1024, 65535), []], context: StatelessRulesAndCustomActions.StatelessRules[Priority=100].RuleDefinition (Service: NetworkFirewall, Status Code: 400, Request ID: 63966680-59e7-4b28-9c3b-288c6a127774)" (RequestToken: c7b82408-ba4e-c132-1081-0d2dc92bf9a4, HandlerErrorCode: InvalidRequest)
--
283 |

Which appears to report that there is a request being made to the provisioning API with a protocol of [] because the parameter is not supplied in the config.
Expected behavior
I expected the stateless rule to be created
Please complete the following information about the solution:

[ v1.9.0 ] Version: [e.g. v1.5.1]

To get the version of the solution, you can look at the description of the created AWS CloudFormation stack used to install the LZA (AWSAccelerator-InstallerStack). For example, "(SO0199) Landing Zone Accelerator on AWS. Version 1.5.1.". If the description does not contain the version information, you can look at the Parameters of the stack for the RepositoryBranchName as that should contain the version number.

[ ap-southeast-2] Region: [e.g. us-east-1]
[No ] Was the solution modified from the version published on this repository?
[ ] If the answer to the previous question was yes, are the changes available on GitHub?
[ No, N/A] Have you checked your service quotas for the services this solution uses?
[See above ] Were there any errors in the CloudWatch Logs?

Screenshots
If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).
Additional context
Add any other context about the problem here.

The example on line 5876 ( https://github.com/awslabs/landing-zone-accelerator-on-aws/blob/450807b2e458b5d3f042fccb2c2900d270d006a6/source/packages/%40aws-accelerator/config/lib/models/network-config.ts#L5876 ) does work, so it appear that the issue is that protocols is a mandatory parameter.


feat: add recruitment text to dev console on page load

Description

feat: add recruitment text to dev console on page load

Closes #437
Before submitting the PR, please make sure you do the following

[x] If your PR is related to a previously discussed issue, please link to it here.
[x] Prefix your PR title with feat:, fix:, chore:, or docs:.
[x] This message body should clearly illustrate what problems it solves.
[x] Make sure the commit history is linear, up-to-date with main branch and does not contain any erroneous changes

Formatting and linting

[x] Format code with pnpm format and lint the project with pnpm lint

Oof, why is GitHub default "Update branch" with a merge commit. Reminder to rebase this before merging