Replace react-dnd with react-beautiful-dnd

react-dnd is used in Contents views. I don't think we need 2 libraries that can do the same thing. I've tested and it's possible (of course) to do table row sorting with react-beautiful-dnd.

I was under the assumption that we already ripped out react-dnd TBH. Definitely +1. cc @iFlameing

@iFlameing you can use this component: https://github.com/eea/volto-blocks-form/blob/master/src/components/manage/Blocks/DragDropList/DragDropList.jsx and how it can be used to create a sortable "table" https://github.com/eea/volto-taxonomy/blob/2420d96b538634d3b02bd6f56e2a99cc9ba7be17/src/ControlPanel/TaxonomyData.jsx#L79

@tisto we removed the react-dnd from Edit view but the folder-content view still uses react-dnd.

Still valid to this day :(

@ichim-david imho this is superseded by #4756
If you agree we can close this.


Makeover for website

Changed how the landing page looked, added transparent logos, changed the background image to match the colour scheme, added a logo in the navigation bar, added sponsor logos, changed how the three lines appeared in the view, revised a few content holders.

Hi @FermatsLastAccount
I really like the background, the navbar and landing screen logos, and the sponsor logos. However, the landing screen text and icons are not fitting on the screen (in my browser, at least). Also, the 'View our works' button is missing. I am attaching some screenshots. Please review.

Thanks for your feedback :))
Do we really need the view our works button on our landing? We do have a "projects" tab for the same in our navbar.
Sure thing, will look into what is causing the problem.

Let the button be there, but rename it to something else if you feel the name is not appropriate. It makes for easy navigation.

@soham1705 @crespoter: Merging this as it fixes issue #33
New issues will be opened soon


Vue template compiler : this to _vm auto compile feature please .

What problem does this feature solve?

const COMMAND = {
TREND: {
LIST: "DATA_LIST"
}
};

data() {
    return {
        COMMAND: COMMAND.TREND
     }
}

<v-data-table
          fixed-header
          dense
          :headers="tableHeaders"
          :items="tableDataList"
          :header-props="{ 'sort-icon': 'mdi-arrow-up' }"
           :items-per-page.sync="this[COMMAND.LIST].pageSize"/>

============
Problem : Vue template compiler does not compile this to _vm

lose link to _vm

"update:itemsPerPage": function($event) {
return _vm.$set(
this[_vm.COMMAND.PAGE_INFO],
"pageSize",
$event
)
},
"update:items-per-page": [
function($event) {
return _vm.$set(
this[_vm.COMMAND.PAGE_INFO],
"pageSize",
$event
)
},
_vm.search
],
What does the proposed API look like?
"update:itemsPerPage": function($event) {
return _vm.$set(
_vm[_vm.COMMAND.PAGE_INFO],
"pageSize",
$event
)
},
"update:items-per-page": [
function($event) {
return _vm.$set(
_vm[_vm.COMMAND.PAGE_INFO],
"pageSize",
$event
)
},
_vm.search
],

Never use this in templates

@posva Thanks, but is there any way to use sync properly using CONST variable as a name to access data?

You can use a computed property or a method
Please, next time consider using the forum, the Discord server or StackOverflow for questions first. But feel free to come back and open an issue if it turns out to be a bug 🙂


[minidlna] bridge mode / host mode

Can't make work network dlna server discovering with bridge mode.
Also (need to add UPD port to readme?), https://help.ubuntu.com/community/MiniDLNA :
OPEN_TCP="8200"
OPEN_UDP="1900"

It seems, issue related to different networks <IP_ADDRESS> (container) and <IP_ADDRESS> (local).  Can you please add to the readme working bridge mode configuration?
ps. host mode works fine.

You need to run the container in host mode for it to be able to receive UPnP broadcast packets. Bridge mode will not work because it separates the container and local network.

So, we need to add --net=host to Readme?

UP. So, we need to remove -p parameter from the readme ?
https://docs.docker.com/network/host/

Note: Given that the container does not have its own IP-address when using host mode networking, port-mapping does not take effect, and the -p, --publish, -P, and --publish-all option are ignored

That sounds like a good idea. I'll update the README and also add a note about the host mode.
Thanks.

I have a question here: why does it not work?

I have a question here: why does it not work?

https://github.com/moby/libnetwork/issues/2397#issuecomment-935029813


Square brackets not in the table name of SQL query

I keep getting this error
[Illuminate\Database\QueryException]
SQLSTATE[42000]: [Microsoft][ODBC Driver 11 for SQL Server][SQL Server]Incorrect syntax near the keyword 'user'. (SQL: if exists (select * from INFORMATION_SCHEMA.TABLES where TABLE_NAME = 'user') drop table user)
[PDOException]
SQLSTATE[42000]: [Microsoft][ODBC Driver 11 for SQL Server][SQL Server]Incorrect syntax near the keyword 'user'.
I think the problem is SQL query says
"if exists (select * from INFORMATION_SCHEMA.TABLES where TABLE_NAME = 'user') drop table user" and user happens to be a keyword in SQL Server.
it should add square brackets to the table name right? as in
"if exists (select * from INFORMATION_SCHEMA.TABLES where TABLE_NAME = 'user') drop table [user]"
pls confirm if this happens to others?
(edit... btw i was using this function in Laravel 5.2)
Schema::dropIfExists('user');

Created a PR to fix this issue, its just a small fix...


Issue10 fix - Added validation of CollectionName length 1-15 characters and tests

Resubmission of Issue 10

Added validation of CollectionName parameter 1-15 characters
Added Tests for CollectionName length validation
Updated README.md to add documentation to unreleased section, and fixed bad apostrophe
Added NewLine to end of xRemoteDesktopSessionHostCommon.psm1

This change is

Hi @JimPriestley, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Jim Priestley). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

@TravisEz13 Changes from #13 are now here.

Reviewed 8 of 8 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


sfu-ws prometheus seems to have issue with - in key names.

Your environment.

Version: Release or SHA
Browser: include version
Other Information - stacktraces, related issues, suggestions how to fix, links for us to have context

What did you do?

What did you expect?
What happened?

My bad. I will fix it today


Update document

This document has not been updated in almost a year. Is it still accurate as to what services are FedRAMP Moderate/High?

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

ID: 4e27d0b1-56f9-2eb7-8fee-0c47cfbafeac
Version Independent ID: 12556227-6adc-52c1-ac60-f341ae247e51
Content: Azure Services in FedRAMP and DoD SRG Audit Scope
Content Source: articles/azure-government/compliance/azure-services-in-fedramp-auditscope.md
Service: azure-government
GitHub Login: @Jain-Garima
Microsoft Alias: gjain

Hi Byron, it is updated regularly and was updated in March 2020. thanks
From: Byron Boudreaux<EMAIL_ADDRESS>Sent: Thursday, March 26, 2020 11:59 AM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Garima Jain (AZURE<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: [MicrosoftDocs/azure-docs] Update document (#51029)
This document has not been updated in almost a year. Is it still accurate as to what services are FedRAMP Moderate/High?

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

ID: 4e27d0b1-56f9-2eb7-8fee-0c47cfbafeac
Version Independent ID: 12556227-6adc-52c1-ac60-f341ae247e51
Content: Azure Services in FedRAMP and DoD SRG Audit Scopehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-government%2Fcompliance%2Fazure-services-in-fedramp-auditscope%23feedback&data=02|01|gjain%40microsoft.com|8cf1189f18e8437e035d08d7d1b7b98b|72f988bf86f141af91ab2d7cd011db47|1|0|637208459329356457&sdata=O6uFRxWODVa2Ky46qTdiyTl5F00Y9G4P45qX3PHwwO4%3D&reserved=0
Content Source: articles/azure-government/compliance/azure-services-in-fedramp-auditscope.mdhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fazure-docs%2Fblob%2Fmaster%2Farticles%2Fazure-government%2Fcompliance%2Fazure-services-in-fedramp-auditscope.md&data=02|01|gjain%40microsoft.com|8cf1189f18e8437e035d08d7d1b7b98b|72f988bf86f141af91ab2d7cd011db47|1|0|637208459329356457&sdata=hPvcoDlPvg4arcBc%2Bd6Bc6fc5e2ZYwttFCpHZG%2BrLXA%3D&reserved=0
Service: azure-government
GitHub Login: @Jain-Garimahttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FJain-Garima&data=02|01|gjain%40microsoft.com|8cf1189f18e8437e035d08d7d1b7b98b|72f988bf86f141af91ab2d7cd011db47|1|0|637208459329356457&sdata=SklJoti%2FybL8cLqU3JZ7seNMS4QRqvSG%2B4hKv9qIkGI%3D&reserved=0
Microsoft Alias: gjain

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F51029&data=02|01|gjain%40microsoft.com|8cf1189f18e8437e035d08d7d1b7b98b|72f988bf86f141af91ab2d7cd011db47|1|0|637208459329366457&sdata=O5R12rDXHMv8IL5s3rq%2F0s7wq0dNwkqCdC4u3klXIh4%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMLOUONOB62PY5CF7L253QTRJOQWXANCNFSM4LUOZR2A&data=02|01|gjain%40microsoft.com|8cf1189f18e8437e035d08d7d1b7b98b|72f988bf86f141af91ab2d7cd011db47|1|0|637208459329366457&sdata=5Qqs1O7tInn8M6Q1pKnxlw%2BPIc2gTYtO29egPflNnOU%3D&reserved=0.

Sorry, I was looking at the date at the top of the doc that shows it was last updated on 5/17/2019…now I see the “[Last Updated: March 2020]” a little further down in the document.
Thanks for the quick response
From: Jain-Garima<EMAIL_ADDRESS>Sent: Thursday, March 26, 2020 3:01 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Byron Boudreaux<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Update document (#51029)
Hi Byron, it is updated regularly and was updated in March 2020. thanks
From: Byron Boudreaux <notifications<EMAIL_ADDRESS>Sent: Thursday, March 26, 2020 11:59 AM
To: MicrosoftDocs/azure-docs <azure-docs<EMAIL_ADDRESS>Cc: Garima Jain (AZURE) <gjain<EMAIL_ADDRESS>Mention <mention<EMAIL_ADDRESS>Subject: [MicrosoftDocs/azure-docs] Update document (#51029)
This document has not been updated in almost a year. Is it still accurate as to what services are FedRAMP Moderate/High?

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

ID: 4e27d0b1-56f9-2eb7-8fee-0c47cfbafeac
Version Independent ID: 12556227-6adc-52c1-ac60-f341ae247e51
Content: Azure Services in FedRAMP and DoD SRG Audit Scopehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-government%2Fcompliance%2Fazure-services-in-fedramp-auditscope%23feedback&data=02|01|gjain%40microsoft.com|8cf1189f18e8437e035d08d7d1b7b98b|72f988bf86f141af91ab2d7cd011db47|1|0|637208459329356457&sdata=O6uFRxWODVa2Ky46qTdiyTl5F00Y9G4P45qX3PHwwO4%3D&reserved=0
Content Source: articles/azure-government/compliance/azure-services-in-fedramp-auditscope.mdhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fazure-docs%2Fblob%2Fmaster%2Farticles%2Fazure-government%2Fcompliance%2Fazure-services-in-fedramp-auditscope.md&data=02|01|gjain%40microsoft.com|8cf1189f18e8437e035d08d7d1b7b98b|72f988bf86f141af91ab2d7cd011db47|1|0|637208459329356457&sdata=hPvcoDlPvg4arcBc%2Bd6Bc6fc5e2ZYwttFCpHZG%2BrLXA%3D&reserved=0
Service: azure-government
GitHub Login: @Jain-Garimahttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FJain-Garima&data=02|01|gjain%40microsoft.com|8cf1189f18e8437e035d08d7d1b7b98b|72f988bf86f141af91ab2d7cd011db47|1|0|637208459329356457&sdata=SklJoti%2FybL8cLqU3JZ7seNMS4QRqvSG%2B4hKv9qIkGI%3D&reserved=0
Microsoft Alias: gjain

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F51029&data=02|01|gjain%40microsoft.com|8cf1189f18e8437e035d08d7d1b7b98b|72f988bf86f141af91ab2d7cd011db47|1|0|637208459329366457&sdata=O5R12rDXHMv8IL5s3rq%2F0s7wq0dNwkqCdC4u3klXIh4%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMLOUONOB62PY5CF7L253QTRJOQWXANCNFSM4LUOZR2A&data=02|01|gjain%40microsoft.com|8cf1189f18e8437e035d08d7d1b7b98b|72f988bf86f141af91ab2d7cd011db47|1|0|637208459329366457&sdata=5Qqs1O7tInn8M6Q1pKnxlw%2BPIc2gTYtO29egPflNnOU%3D&reserved=0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F51029%23issuecomment-604624251&data=02|01|byron.boudreaux%40microsoft.com|6766f1fb7d5948f4268b08d7d1b803b7|72f988bf86f141af91ab2d7cd011db47|1|0|637208460574202734&sdata=Hkk5yc6Kq2TA121bF5fKHUrDZYWjmKK8VJmuRfnODBg%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAEAQKJ2MLS4ZX2LUONZ7KFDRJOQ6RANCNFSM4LUOZR2A&data=02|01|byron.boudreaux%40microsoft.com|6766f1fb7d5948f4268b08d7d1b803b7|72f988bf86f141af91ab2d7cd011db47|1|0|637208460574212726&sdata=eiw%2Bble%2FO06PKWvpGBkQ0d%2BA1bdMUVCQjsWT6Y3kZH8%3D&reserved=0.

@Jain-Garima Thank you for your quick response.
@Phydeauxman Thank you for your query. Will go ahead and close this issue for now, however if there are any other queries/feedback please revert back. Thank you.


Release workflow may have a problem

mases.jnet was not updated due to an error in workflow. A newer version of JNet ecosystem will be released soon to solve this issue. Ref. masesgroup/JNet#125
Originally posted by @masesdevelopers in https://github.com/masesgroup/JNet/discussions/124#discussioncomment-4909304

Update repo with changes made in masesgroup/JNet#126


When we enable the JWTTokenIssuer, we cannot  generate the JWT token with the given validity period(exp value is static one)

Description:
When we are having the following configurations in deployment.toml file, to use the org.wso2.carbon.identity.oauth2.token.JWTTokenIssuer to generate JWT tokens with the specific validity period(larger than the default value in the service provider configs) via the APIM dev portal, the exp value in the generated token is showing a value of the default value configured in the service provider configurations. It is not showing the inputted validity period.
[oauth.extensions]
token_generator = "org.wso2.carbon.identity.oauth2.token.JWTTokenIssuer"

For example, when we have the Application Access Token Expiry Time as 3600 in service provider configurations in the management console, if we generate the token with the validity period 14400s, then in the database we can see the correct jti entry with 14400s validity period.
But, when we decoded the JWT token and checked the exp value of the JWT that is showing 3600s.
Further, when we have validated the above-generated token against introspect endpoint, the result shows the correct exp value with 14400s.
Steps to reproduce:

Add the following configs in the deployment.toml file
Generate the token via devportal with the 7200s
Decode the token and check the exp value that will show as 3600s.

Affected Product Version:
APIM 3.0.0 and APIM 3.1.0

This is fixed in the APIM 3.1.0 version with a WUM update. Not adding the fixes to the public branch as the fixes are N/A (feature is removed from APIM 3.2.0 version onwards).


ImportError: No module named pyAudioAnalysis

I have added export PYTHONPATH=$PYTHONPATH:"/home/pi" in the .bashrc file,and type source ~/.bashrc. And I'm pretty sure my library is in the /home/pi folder. But it still shows " ImportError: No module named pyAudioAnalysis". Can anyone teach me?

you can simply do a pip install pyAudioAnalysis

Cannot import 'ShortTermFeatures' from 'pyAudioAnalysis'

cannot import name 'ShortTermFeatures'

Cannot import 'ShortTermFeatures' from 'pyAudioAnalysis'

just remove (from 'pyAudioAnalysis') and just write (import 'ShortTermFeatures') from audioAnalysis.py file

@omarshaban32 can you explain more? I am unable to import ShortTermFeatures from audioAnalysis.py file.

@omarshaban32 can you explain more? I am unable to import ShortTermFeatures from audioAnalysis.py file.

pyAudioAnalysis 0.2.5 changes a lot
you can write as below
from pyAudioAnalysis import audioBasicIO
from pyAudioAnalysis.audioFeatureExtraction import stFeatureExtraction
import matplotlib.pyplot as plt
[Fs, x] = audioBasicIO.readAudioFile("./train/1-100032-A-0.wav")
F, f_names = stFeatureExtraction(x, Fs, 0.050Fs, 0.025Fs)

Just make sure your files are installed properly.
Your main.py file should be place alongside pyaudioanalysis folder which contains all the python modules - audioBasicIO or ShortTermFeatures, etc.
Then you can successfully run -
from pyAudioAnalysis import audioBasicIO
from pyAudioAnalysis import ShortTermFeatures
Note -

You should check is if you're installing it for the correct version of python. The recommended is 2.7 version of python.
audioFeatureExtraction is inside ShortTermFeatures. You can call it like this -
info=ShortTermFeatures.feature_extraction()
and get ride of  import audioFeatureExtraction completely.


Furigana is buggy on Cloze cards

Cloze cards surround your cloze deletion with  which interferes with furigana parsing.
When furigana braces are set to "()"
Doing text{{c1::kanji(furi)}}text works.
Doing text{{c1::kanji(furi)::placeholder}}text works.
Doing text{{c1::kanji(furi)::placeholder(furi)}}text does NOT work.
Doing text{{c1::kanji::placeholder}}(furi)text does NOT work.
Doing text{{c1::kanji}}(furi)text does NOT work.

I think this must be resolved by doing furigana parsing more inline. That is, instead of replacing HTML contents in full, replace each furigana markup with the relevant HTML without disturbing its surroundings.

Furthermore, it'd be useful to allow the user to distinguish what's clozed in a semantically correct way. That is, the cloze could delete kanji, furigana, or both using field markup alone.

And while you're at it, change the default brace type to parenthesis.

It would be simplest to require the user to specify furigana on a kanji-to-kanji basis, so I'm going to take that route for now.

Let's examine some illustrative cases.

text{{c1::kanji(furi)::placeholder}}text => textplaceholdertext
text{{c1::kanji::placeholder(furi)}}text => textplaceholder(furi)text
text{{c1::kanji::placeholder}}(furi)text => textplaceholder(furi)text
The same 3 above but without placeholder.

Analysis:

Hide both kanji and furi. This is simple since they appear next to one another as a single text node.
Hide kanji, but show a custom placeholder with furi. This is simple for the same reasons as the previous case, but this time it's furi is only shown on the on the front side of the card instead of only on the back.
Hide kanji and show furi on both sides. This is more complex, since the furi appears in a separate text node.

One thing that may simplify this is to convert the cloze spans to text and parse those.

Okay here's a use case I hadn't considered: compounds with furi on front and back.
Font: [...](bcef)
Back: a(bc)d(ef)
My first though it to be represented with [...](bcef), but then the back side may not display properly because the furigana is applied to more than one character.


BelongsTo relation returns old relation when associate() is called with model ID

Laravel Version: 5.7.12
PHP Version: -
Database Driver & Version: -

Description:
When calling associate() with a model ID on a BelongsTo relation, the foreign key is updated but the (possibly) previously loaded relation is not reset on the child model. This means that calling the relation after using associate() with a model ID will return the old relation, which can lead to unexpected behaviour if the developer is not careful to reload the relation.
I have created a PR to fix this issue by unsetting the relation.
Steps To Reproduce:
$foo->load('bar');

$newModelId = 5;

$foo->bar()->associate($newModelId);

// $foo->bar contains the old bar, NOT the new bar, because it was previously loaded

Can you resend your PR to master?

You were too fast, done ;-)


Agent (facter?) doesn't find credentials in WinCred

Initial run on new Winserver 2008 R2 VM - new host identity correctly created w/ host factory:
C:\Users\Administrator>puppet agent -t -v
Info: Using configured environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Retrieving locales
Info: Loading facts
Enumerate credentials in WinCred failed. Error code: 1168
Info: Caching catalog for win-2re6mq9ddem.localdomain
Info: Applying configuration version '1565020354'
Notice: /Stage[main]/Conjur::Identity::Wincred/Credential[conjur-master:30443]/ensure: created (corrective)
Notice: Applied catalog in 0.14 seconds

Second run - identity not found, seems to be updating the existing credential:
C:\Users\Administrator>puppet agent -t -v
Info: Using configured environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Retrieving locales
Info: Loading facts
Conjur identity not found on system
Info: Caching catalog for win-2re6mq9ddem.localdomain
Info: Applying configuration version '1565020487'
Notice: /Stage[main]/Conjur::Identity::Wincred/Credential[conjur-master:30443]/value: changed [redacted] to [redacted]
Notice: Applied catalog in 0.03 seconds

Test code in: https://github.com/jodyhuntatx/dap-demo-env/tree/master/PUPPET_demo

Running above w/ PuppetMaster & Agent v6.7.2

For comparison - a run against the same PuppetMaster instance from a Linux node:
~/Conjur/dap-demo-env/PUPPET_demo >> docker-compose exec prod-webapp puppet agent -t
Info: Downloaded certificate for ca from puppet
Info: Downloaded certificate revocation list for ca from puppet
Info: Creating a new RSA SSL key for prod-webapp.cluster.local
Info: csr_attributes file loading from /etc/puppetlabs/puppet/csr_attributes.yaml
Info: Creating a new SSL certificate request for prod-webapp.cluster.local
Info: Certificate Request fingerprint (SHA256): 57:AA:FD:FD:10:BC:D3:69:4B:87:FB:0C:F0:73:EB:10:08:D3:7D:12:CE:96:32:D8:70:FE:69:6F:46:8E:C3:1D
Info: Downloaded certificate for prod-webapp.cluster.local from puppet
Info: Using configured environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Notice: /File[/opt/puppetlabs/puppet/cache/lib/conjur]/ensure: created
Notice: /File[/opt/puppetlabs/puppet/cache/lib/conjur/puppet_module]/ensure: created
Notice: /File[/opt/puppetlabs/puppet/cache/lib/conjur/puppet_module/config.rb]/ensure: defined content as '{md5}b3780ec739325ca060b5c74e76fe7d55'
Notice: /File[/opt/puppetlabs/puppet/cache/lib/conjur/puppet_module/identity.rb]/ensure: defined content as '{md5}6e6a3f337b9fba99b0e422b2a0769c11'
Notice: /File[/opt/puppetlabs/puppet/cache/lib/facter]/ensure: created
Notice: /File[/opt/puppetlabs/puppet/cache/lib/facter/conjur.rb]/ensure: defined content as '{md5}41be6fd2bc522f5be28eaf197eeaf86d'
Notice: /File[/opt/puppetlabs/puppet/cache/lib/puppet]/ensure: created
Notice: /File[/opt/puppetlabs/puppet/cache/lib/puppet/functions]/ensure: created
Notice: /File[/opt/puppetlabs/puppet/cache/lib/puppet/functions/conjur]/ensure: created
Notice: /File[/opt/puppetlabs/puppet/cache/lib/puppet/functions/conjur/client.rb]/ensure: defined content as '{md5}6305c573f56a6dd8810aabe636a194df'
Notice: /File[/opt/puppetlabs/puppet/cache/lib/puppet/functions/conjur/config_yml.rb]/ensure: defined content as '{md5}e58bbe1b6c25bed7f7a9bf96c7ffeda3'
Notice: /File[/opt/puppetlabs/puppet/cache/lib/puppet/functions/conjur/decrypt.rb]/ensure: defined content as '{md5}db122f2ca606cb8cf187ce535d533fb3'
Notice: /File[/opt/puppetlabs/puppet/cache/lib/puppet/functions/conjur/manufacture_host.rb]/ensure: defined content as '{md5}9e460f636128e0d7d45565d8180836da'
Notice: /File[/opt/puppetlabs/puppet/cache/lib/puppet/functions/conjur/netrc.rb]/ensure: defined content as '{md5}4b77091862ff01f2a3016c388c736b35'
Notice: /File[/opt/puppetlabs/puppet/cache/lib/puppet/functions/conjur/secret.rb]/ensure: defined content as '{md5}4d8a35b874b7214d7a3a2a2aedcbae01'
Notice: /File[/opt/puppetlabs/puppet/cache/lib/puppet/functions/conjur/token.rb]/ensure: defined content as '{md5}1af71b2ca11a01ec0ed25d18144e628f'
Notice: /File[/opt/puppetlabs/puppet/cache/lib/puppet/provider]/ensure: created
Notice: /File[/opt/puppetlabs/puppet/cache/lib/puppet/provider/credential]/ensure: created
Notice: /File[/opt/puppetlabs/puppet/cache/lib/puppet/provider/credential/wincred.rb]/ensure: defined content as '{md5}c7a85590f9f87226d74a1108e3ac3771'
Notice: /File[/opt/puppetlabs/puppet/cache/lib/puppet/provider/registry_key]/ensure: created
Notice: /File[/opt/puppetlabs/puppet/cache/lib/puppet/provider/registry_key/registry.rb]/ensure: defined content as '{md5}57d97e6cf5e20370af6caff63f575b6a'
Notice: /File[/opt/puppetlabs/puppet/cache/lib/puppet/provider/registry_value]/ensure: created
Notice: /File[/opt/puppetlabs/puppet/cache/lib/puppet/provider/registry_value/registry.rb]/ensure: defined content as '{md5}70f825ee0a196ea0e3030bafd979aec6'
Notice: /File[/opt/puppetlabs/puppet/cache/lib/puppet/type]/ensure: created
Notice: /File[/opt/puppetlabs/puppet/cache/lib/puppet/type/credential.rb]/ensure: defined content as '{md5}683259dee013d88421e096fca4585847'
Notice: /File[/opt/puppetlabs/puppet/cache/lib/puppet/type/registry_key.rb]/ensure: defined content as '{md5}833cac29fc9cbc761dfb1616d3c7cc8b'
Notice: /File[/opt/puppetlabs/puppet/cache/lib/puppet/type/registry_value.rb]/ensure: defined content as '{md5}9e7cafee6cc3a514e05b9a34c2e43292'
Notice: /File[/opt/puppetlabs/puppet/cache/lib/puppet_x]/ensure: created
Notice: /File[/opt/puppetlabs/puppet/cache/lib/puppet_x/puppetlabs]/ensure: created
Notice: /File[/opt/puppetlabs/puppet/cache/lib/puppet_x/puppetlabs/registry.rb]/ensure: defined content as '{md5}1132a6f66c4e7d549ac90f9f58bd73e2'
Notice: /File[/opt/puppetlabs/puppet/cache/lib/wincred]/ensure: created
Notice: /File[/opt/puppetlabs/puppet/cache/lib/wincred/conversion.rb]/ensure: defined content as '{md5}6fe6013230d9459d2612927a36cd3d0b'
Notice: /File[/opt/puppetlabs/puppet/cache/lib/wincred/native.rb]/ensure: defined content as '{md5}374523d071d50d332c4283bfb52318d4'
Notice: /File[/opt/puppetlabs/puppet/cache/lib/wincred/wincred.rb]/ensure: defined content as '{md5}91cc3df0325a86d1915d934833764418'
Info: Retrieving locales
Info: Loading facts
Info: Caching catalog for prod-webapp.cluster.local
Info: Applying configuration version '1565021519'
Notice: /Stage[main]/Conjur::Config::Files/File[/etc/conjur.pem]/ensure: defined content as '{md5}13f76ab141e9bd445651273f41e6a63c'
Notice: /Stage[main]/Conjur::Config::Files/File[/etc/conjur.conf]/ensure: defined content as '{md5}28a69a4b6eff0e6d04dd14d43aa1594b'
Notice: /Stage[main]/Conjur::Identity::Files/File[/etc/conjur.identity]/ensure: changed [redacted] to [redacted]
Notice: *** Secret key - encrypted:  Sensitive [value redacted]
Notice: /Stage[main]/Main/Node[__node_regexp__prod-webapp.]/Notify[*** Secret key - encrypted:  Sensitive [value redacted] ]/message: defined 'message' as '*** Secret key - encrypted:  Sensitive [value redacted] '
Notice: *** Secret key - unencrypted:  Se(re1Fr0mConjur
Notice: /Stage[main]/Main/Node[__node_regexp__prod-webapp.]/Notify[*** Secret key - unencrypted:  Se(re1Fr0mConjur ]/message: defined 'message' as '*** Secret key - unencrypted:  Se(re1Fr0mConjur '
Notice: *** DB Password - encrypted:  Sensitive [value redacted]
Notice: /Stage[main]/Main/Node[__node_regexp__prod-webapp.]/Notify[*** DB Password - encrypted:  Sensitive [value redacted] ]/message: defined 'message' as '*** DB Password - encrypted:  Sensitive [value redacted] '
Notice: *** DB Password - unencrypted:  white rabbit
Notice: /Stage[main]/Main/Node[__node_regexp__prod-webapp.]/Notify[*** DB Password - unencrypted:  white rabbit ]/message: defined 'message' as '*** DB Password - unencrypted:  white rabbit '
Notice: ******* Writing secret key to file /etc/mysecretkey ******
Notice: /Stage[main]/Main/Node[__node_regexp__prod-webapp.]/Notify[******* Writing secret key to file /etc/mysecretkey ******]/message: defined 'message' as '******* Writing secret key to file /etc/mysecretkey ******'
Notice: /Stage[main]/Main/Node[__node_regexp__prod-webapp.]/File[/etc/mysecretkey]/ensure: changed [redacted] to [redacted]
Info: Creating state file /opt/puppetlabs/puppet/cache/state/state.yaml
Notice: Applied catalog in 0.04 seconds

value stored in /etc/mysecretkey:
Se(re1Fr0mConjur

This is a run on Windows 10 Pro with user access control turned off.
C:\Users\Jody>puppet agent -t -v
Info: Downloaded certificate for ca from puppet
Info: Downloaded certificate revocation list for ca from puppet
Info: Creating a new RSA SSL key for desktop-848lp3a.localdomain
Info: csr_attributes file loading from C:/Users/Jody/.puppetlabs/etc/puppet/csr_attributes.yaml
Info: Creating a new SSL certificate request for desktop-848lp3a.localdomain
Info: Certificate Request fingerprint (SHA256): B7:F2:00:94:95:EF:F4:2A:C8:E5:4E:00:35:C8:20:9F:EA:02:12:9B:BF:9A:27:AE:D0:C6:72:AC:CD:B0:08:4C
Info: Downloaded certificate for desktop-848lp3a.localdomain from puppet
Info: Using configured environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/conjur]/ensure: created
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/conjur/puppet_module]/ensure: created
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/conjur/puppet_module/config.rb]/ensure: defined content as '{md5}b3780ec739325ca060b5c74e76fe7d55'
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/conjur/puppet_module/identity.rb]/ensure: defined content as '{md5}6e6a3f337b9fba99b0e422b2a0769c11'
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/facter]/ensure: created
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/facter/conjur.rb]/ensure: defined content as '{md5}41be6fd2bc522f5be28eaf197eeaf86d'
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/puppet]/ensure: created
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/puppet/functions]/ensure: created
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/puppet/functions/conjur]/ensure: created
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/puppet/functions/conjur/client.rb]/ensure: defined content as '{md5}6305c573f56a6dd8810aabe636a194df'
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/puppet/functions/conjur/config_yml.rb]/ensure: defined content as '{md5}e58bbe1b6c25bed7f7a9bf96c7ffeda3'
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/puppet/functions/conjur/decrypt.rb]/ensure: defined content as '{md5}db122f2ca606cb8cf187ce535d533fb3'
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/puppet/functions/conjur/manufacture_host.rb]/ensure: defined content as '{md5}9e460f636128e0d7d45565d8180836da'
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/puppet/functions/conjur/netrc.rb]/ensure: defined content as '{md5}4b77091862ff01f2a3016c388c736b35'
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/puppet/functions/conjur/secret.rb]/ensure: defined content as '{md5}4d8a35b874b7214d7a3a2a2aedcbae01'
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/puppet/functions/conjur/token.rb]/ensure: defined content as '{md5}1af71b2ca11a01ec0ed25d18144e628f'
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/puppet/provider]/ensure: created
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/puppet/provider/credential]/ensure: created
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/puppet/provider/credential/wincred.rb]/ensure: defined content as '{md5}c7a85590f9f87226d74a1108e3ac3771'
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/puppet/provider/registry_key]/ensure: created
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/puppet/provider/registry_key/registry.rb]/ensure: defined content as '{md5}57d97e6cf5e20370af6caff63f575b6a'
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/puppet/provider/registry_value]/ensure: created
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/puppet/provider/registry_value/registry.rb]/ensure: defined content as '{md5}70f825ee0a196ea0e3030bafd979aec6'
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/puppet/type]/ensure: created
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/puppet/type/credential.rb]/ensure: defined content as '{md5}683259dee013d88421e096fca4585847'
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/puppet/type/registry_key.rb]/ensure: defined content as '{md5}833cac29fc9cbc761dfb1616d3c7cc8b'
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/puppet/type/registry_value.rb]/ensure: defined content as '{md5}9e7cafee6cc3a514e05b9a34c2e43292'
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/puppet_x]/ensure: created
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/puppet_x/puppetlabs]/ensure: created
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/puppet_x/puppetlabs/registry.rb]/ensure: defined content as '{md5}1132a6f66c4e7d549ac90f9f58bd73e2'
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/wincred]/ensure: created
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/wincred/conversion.rb]/ensure: defined content as '{md5}6fe6013230d9459d2612927a36cd3d0b'
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/wincred/native.rb]/ensure: defined content as '{md5}374523d071d50d332c4283bfb52318d4'
Notice: /File[C:/Users/Jody/.puppetlabs/opt/puppet/cache/lib/wincred/wincred.rb]/ensure: defined content as '{md5}91cc3df0325a86d1915d934833764418'
Info: Retrieving locales
Info: Loading facts
The system cannot find the file specified.
Error: Facter: error while resolving custom fact "conjur": The system cannot find the file specified.
Info: Caching catalog for desktop-848lp3a.localdomain
Info: Applying configuration version '1565030092'
**
Error: Could not set 'present' on ensure: Access is denied. (file: /etc/puppetlabs/code/environments/production/modules/conjur/manifests/config/registry.pp, line: 5)
Error: Could not set 'present' on ensure: Access is denied. (file: /etc/puppetlabs/code/environments/production/modules/conjur/manifests/config/registry.pp, line: 5)
Wrapped exception:
Access is denied.
Error: /Stage[main]/Conjur::Config::Registry/Registry_key[HKLM\Software\CyberArk\Conjur]/ensure: change from 'absent' to 'present' failed: Could not set 'present' on ensure: Access is denied. (file: /etc/puppetlabs/code/environments/production/modules/conjur/manifests/config/registry.pp, line: 5)
**
Notice: /Stage[main]/Conjur::Config::Registry/Registry_value[HKLM\Software\CyberArk\Conjur\SslCertificate]: Dependency Registry_key[HKLM\Software\CyberArk\Conjur] has failures: true
Warning: /Stage[main]/Conjur::Config::Registry/Registry_value[HKLM\Software\CyberArk\Conjur\SslCertificate]: Skipping because of failed dependencies
Warning: /Stage[main]/Conjur::Config::Registry/Registry_value[HKLM\Software\CyberArk\Conjur\ApplianceUrl]: Skipping because of failed dependencies
Warning: /Stage[main]/Conjur::Config::Registry/Registry_value[HKLM\Software\CyberArk\Conjur\Account]: Skipping because of failed dependencies
Warning: /Stage[main]/Conjur::Config::Registry/Registry_value[HKLM\Software\CyberArk\Conjur\Version]: Skipping because of failed dependencies
Notice: /Stage[main]/Conjur::Identity::Wincred/Credential[conjur-master:30443]/ensure: created
Info: Stage[main]: Unscheduling all events on Stage[main]
Info: Creating state file C:/Users/Jody/.puppetlabs/opt/puppet/cache/state/state.yaml
Notice: Applied catalog in 0.13 seconds

Because of this:
Notice: /Stage[main]/Conjur::Identity::Wincred/Credential[conjur-master:30443]/value: changed [redacted] to [redacted]

I suspected the API key is getting rotated on every run. The follower workflow seems to confirm that.
On windows host win-2re6mq9ddem:
<puppet run creates creds in WinCred>

Rotate API key in conjur cli container:
root@75cf348e4b3e:/# conjur host rotate_api_key -h win-2re6mq9ddem
3y5zx0f36t1sf3dj8vpc2qmsdbz27mthwexkrdar2p0sb051pr68nw
root@75cf348e4b3e:/# conjur authn login -u host/win-2re6mq9ddem -p 3y5zx0f36t1sf3dj8vpc2qmsdbz27mthwexkrdar2p0sb051pr68nw
Logged in
root@75cf348e4b3e:/# conjur authn whoami
{"account":"dev","username":"host/win-2re6mq9ddem"}
root@75cf348e4b3e:/# conjur authn logout
Logged out

On windows host win-2re6mq9ddem:
<API key pasted into WinCred>
<puppet run pulls secrets>

Try to login w/ Conjur CLI using same API key as before:
root@75cf348e4b3e:/# conjur authn login -u host/win-2re6mq9ddem -p 3y5zx0f36t1sf3dj8vpc2qmsdbz27mthwexkrdar2p0sb051pr68nw
Unable to authenticate with Conjur. Please check your credentials.

Net-net is while the host identity is created and secrets are pulled correctly, the identity is effectively being recreated on every run, which w/ HF token simply rotates the API key on the second-nth run. At scale this will cause concurrency conflict at the Master and needs to be addressed before customers can use the Puppet Windows module in production.

This bit of discussion from Slack gives some insight into this bug

re:

suspected current:

HFT expires
host that was created with HFT can’t have puppet reapply manifest

desired:

HFT expires
host that was created with HFT can have the manifests reapplied (since identity should not be tied to the HFT expiration)

I tried the flow and on first glance it seems as though suspected current IS current, but it’s not. It only seems that way because there’s a bug in how machine identity is retrieved/persisted into wincreds.
Before digging into the wincred issue it’s worth mentioning that the logic responsible for machine identity taking precedence over the host factory token can be found here https://github.com/cyberark/conjur-puppet/blob/conjur-puppet/manifests/init.pp#L20. It shows that host factory tokens are the last to be considered.
The reason why suspected current SEEMS like current right now when you run through the flow with an expired HFT after the first successful run is because there’s a mismatch between persistence and retrieval. Suppose you have Appliance URL http://conjur.host:8080

Persistence of machine identity. The target name is taken from the appliance URL. It is transformed and stored using this logic found at https://github.com/cyberark/conjur-puppet/blob/conjur-puppet/manifests/identity/wincred.pp#L7. The target name generated for our example in windows credentials will be conjur.host:8080 . The regex strips the appliance URL of the scheme and the anything beyond the port. The regex is actually quite brittle. It’d be better to parse the appliance URL as a URI perhaps followed by concatenating the host and port.
Retrieval of machine identity. The code for selecting the right credentials in wincreds based on target name https://github.com/cyberark/conjur-puppet/blob/conjur-puppet/lib/conjur/puppet_module/identity.rb#L45. Note that it looks through all the credentials in wincreds then selects the first one that matches either of the following conditions. (1) Target name prefix-matches the appliance URL (e.g. conjur.host:8080  (target name) will match with conjur  (appliance URL)). This likely won’t ever be true because appliance URLs are parsed as URLs and so come with a scheme e.g. http://… , while target names are stripped of their schemes as shown in the persistence section above because of the regex. (2) Target name is equal to the host component of the parsed appliance URL. For our example we’d be comparing the host part of the appliance URL conjur.host with the target name conjur.host:8080 . This can only ever be true when the appliance URL  specifies no port.

You’ll see from above that for appliance URLs (with ports) the machine identity persisted (BY the conjur module from Puppet Server) can never be retrieved. This actually means that any subsequent runs beyond the initial one where machine identity is established will fail. Pre-provisioned machine identity however might work for multiple runs if you happen to have used a manually set target name that can be retrieved from the appliance URL (e.g. respectively http://conjur.host:8080 and http://conjur.host:8080 … this is actually what our README suggests).
NOTE that persistence (potentially overwriting) is only carried out by the conjur module when the server has the authn_api_key as a fact. This happens when

Manifest on server is given the literal values of the authn_api_key credentials
Manifest on server is given the host factory token. For this it will create a host and get the authn_api_key credential

Once persistence occurs authn_token takes precedence and does not invoke persistence (e.g. https://github.com/cyberark/conjur-puppet/blob/conjur-puppet/manifests/identity/wincred.pp#L4 because $conjur::api_key  can only be set on the server when authn_token is not https://github.com/cyberark/conjur-puppet/blob/conjur-puppet/manifests/init.pp#L18). authn_token
is generated on the agent and sent to the server.
To reiterate, the bug here is that whenever persistence  of machine identity is carried out by the conjur module it is highly likely that there will be a mismatch of the wincred target name used to store machine identity and the rules used to retrieve the machine identity, there are certain values of appliance URLs where this isn’t an issue. Where the mismatch IS an issue it results in machine identity not being retrievable on subsequent puppet runs. This results in an auth error where the agent says it can’t find machine identity. In the case where the manifest on the server has a host factory token then the precedence (https://github.com/cyberark/conjur-puppet/blob/conjur-puppet/manifests/init.pp#L20) of machine identity is lost and the logic falls back to using the host factory token. THIS is what makes it seems as though the suspected current IS current.
To fix this we simply need to reconcile how machine identity is stored and retrieved. For persistence this must be reflected both in the conjur module and our recommendations for the target name to use when preprovisioning machine identity.

@jodyhuntatx we believe we fixed this in #124. Do you still have an environment that you could try our local version of the plugin with to validate that you are no longer impacted by this issue? Please let us know if you'd like to try to see if your issue is resolved, either now or in a week or so once we have a new tag with the fix. If not, we'll close this issue - please report if you see any kind of problem like this again, we'll be glad to get it fixed up!


Add mongo dependency and override to core config

What type of PR is this?
Bug Fix

What does this PR do / why is it needed ?
Add mongo dependency and override to core config. This is blocking tests execution from IDE

Which issue(s) this PR fixes:

Fixes #
Other notes for reviewers:
Does this PR introduce a user-facing change?

I don't think this is the right solution since this create a "super" module in production, that affects downstream projects that depend on this module (and they might not need mongo).  Conceptually, this also goes against the idea that the system is modular.
To test on IDE, we need an IDE solution.  Maybe a local binder that overrides everything inside the IDE pure code?

I don't think this is the right solution since this create a "super" module in production, that affects downstream projects that depend on this module (and they might not need mongo). Conceptually, this also goes against the idea that the system is modular.
To test on IDE, we need an IDE solution. Maybe a local binder that overrides everything inside the IDE pure code?
Otherwise, we might want to rollback the "local execution" from using this local binder and hard code java platform until a proper solution is brought that allow local binder while also respecting modularization.

@rafaelbey core-configuration module was meant to be a module aligned with server deployment and hence it is meant to be a super module which brings together dependencies for all features for a particular deployment.

I dont agree with that design approach. If you consider all other design choices on how extensions are built, this repo just minimize if not invalidate them.
For example, all extensions define their parsers, composers, compilers, executions, etc extensions in ways that are discovered, and everywhere we make usage of this design choice.
This means, that with just adding these extensions as runtime dependencies on classpath, like in the Server, the process can operate with these extensions without further lines of code.
Hence, we should solve the local binder problem in a way that, well, is actually local, while further embrace the independence of the extensions in ways that they are "plug & play".
So, unless Im missing what value this coreconfig repo provide that the extension design does not, and Im happy to be corrected, our direction should be phase it out with solutions that work properly with the distributed design.

We don't need this anymore, do we?
(The local IDE tests need some additions - is that what we are looking to resolve?)

This PR is stale because it has been open for 30 days with no activity. Please remove stale label or add any comment to keep this open. Otherwise this will be closed in 5 days.


DBAL filter alias

Hi I'm having trouble filtering an aliased table with DBAL
I've set set name of the filter  name of the column in the grid
 (new FieldConfig())
          ->setName('indirizzo')
          ->addFilter(
            (new FilterConfig)
              ->setName('i.nome')
              ->setOperator(FilterConfig::OPERATOR_LIKE)
          ),

but gives me this error
AND (i.nome like :i.nome) ORDER BY ragsoc ASC  with params ["%sisto%"]:

Value for :i not found in params array. Params array key should be "i"

fix
I've fixed this changing your code in rows 180/181 in file DbalDataProvider.php
$fieldName_parameter = str_replace(".","_",$fieldName);
$this->src->andWhere("$fieldName $operator :$fieldName_parameter");
$this->src->setParameter($fieldName_parameter, $value);

now it works, maybe you can apply this change to future releases (sincerly I don't know how to pull a request )
hope it helps

Hi!
Thanks! Great contribution.

Released in v1.1.1


change KubePersistentVolumeFillingUp severity to informational

When thanos-store persistent volumes get full, it does not affect the query. The alert KubePersistentVolumeFillingUp  and should be treated as informational only.

/lgtm


Adding more logging and error messages when things fail

@odandia @gimballock
Hey let me know if this looks good and if you know of a way to test it.

tested with:
$ python src/examples/child_stack.py create

Generating template for environmentbase stack

Writing template to environmentbase.template

Looks good


[bug] local variable 'click' referenced before assignment

I have encountered a bug at the launch of the program where I get the following error and the program stops.
Traceback (most recent call last):
  File "main.py", line 571, in <module>
    main_menu()
  File "main.py", line 59, in main_menu
    if click:
UnboundLocalError: local variable 'click' referenced before assignment

This can be reproduced by putting the mouse pointer in the region of play or instructions button and then running the program.
Since collidepoint() will return True, the conditional statement inside gets executed.
This bug can be fixed by either moving click = False higher up or by rewriting the program and putting the event loop further down or putting the collidepoint() check inside the event of MOUSEBUTTONDOWN
The first way is easiest, however I feel the third method is "correct" way of doing it because:

there need not be checking whether the mouse is in the region of play or instructions button at that point in the program, and
it will lead to the elimination of the variable click

Of course, I would be happy to make the necessary changes.

@codephile1221, feel free to fix it.


Warning after npm start

Description
Warning after npm start
CodeSandbox/Snack link
No response
Steps to reproduce

Go to '...'
Click on '...'
Scroll down to '...'
See error

gluestack-ui Version
3.3.1
Platform

[ ] Expo
[ ] React Native CLI
[ ] Next
[ ] Web
[ ] Android
[ ] iOS

Other Platform
No response
Additional Information
Alicia — 03/12/2023 14:53
Hi guys! I am really new to programming and I am trying to build an app with gluestack. I am using the starter kit but run into this warning after I run npm start. Can anyone help check how can I resolve this issues please
Image
Alicia — 03/12/2023 15:07
I just ran npm --legacy-peer-deps and it showed
Image
Post Link: https://discord.com/channels/1050761204852858900/1123159327751028756/1180801586444894258

The issue was resolved by downgrading the metro version in the starter kit, as expo-router has a peer dependency on "metro": "^0.76.7". We have updated our starter kits.
Thanks for reporting.


Enhance unique indexable fields

Instead of having one list for each value, so a key for each, as unique index can have only one entry for each value, we can store them as a redis hash, which take less memory in redis.

It is only valid if we want uniqueness without indexing.


Clean up dealing dialog details

Split from issue #60.

The "Deal" button has the wrong enablement initially.  Toggling the hand area off and on seems to fix this.
The Deal dialog should show an error when the number of cards required by the deal exceeds the size of the deck.   This was omitted from the rewrite.
The Deal dialog should dismiss itself when the deal is complete.   Now, it requires touching outside the dialog to make it go away.
Reset button does not work.
Target boxes are placed a bit too low: the legend overlaps the hand area marker.   When there is no hand area, they are in the view but the view is not constrained by the safe area at the bottom.
Probably dealing to "hands" should not be offered if there is no hands area because hands are designed to be "taken" by individual players.

Target boxes are placed a bit too low: the legend overlaps the hand area marker. When there is no hand area, they are in the view but the view is not constrained by the safe area at the bottom.

I think this may be due to an old bug still present in PlayingSurface.  Testing that hypothesis.

The "Deal" button has the wrong enablement initially. Toggling the hand area off and on seems to fix this.

Ending the game and starting again also fixes it.  It doesn't recur.  It seems to be an artifact of a completely fresh app instance.

Items (1) and (5) are now resolved.

Item (1) was not really resolved; I had omitted the check for the presence of the deck.   Restoring the check (while still ensuring that the view is initialized) the button is improperly disabled, so still have to investigate that.
Meanwhile, items (2) and (3) are now resolved.

Concerning item (1): it was actually correct to omit the test for deck == nil and I have returned to testing only the canDeal flag.   For the moment, there is an invariant that a playing surface must always have a deck.  We could eventually change the model so that a "new" playing surface never has a deck and decks must always be added if desired.   But, I was getting myself in trouble by trying to have it both ways.
Item (6) is now addressed.
This leaves only item (4) (the reset button).   The action for the reset button was always TODO so I now need to implement it.

Work defined in this issue is now complete.


Parametric Block Non-linear form with examples

The new code provides parametric block non-linear form necessary for shortening the realization of optimization problems. The usage is exemplified with two examples in the mini-app folder mtop. Additional examples including complete topology optimization mini-app are under preparation. The current version demonstrates only the evaluation of gradients.

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#2079
@bslazarov
@tzanio
@jamiebramwell + @jandrej + @v-dobrev
03/04/21
04/29/21
⌛due 05/06/21

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

I'd like to see a consistent comment and formatting style. Some examples of individual comments throughout
//set the matrix B
//returns the derivative, with respect to the density, of the product
//Provides implementation of an integrator for linear diffusion
// Computes an example of nonlinear objective
//          Define a parallel mesh by a partitioning of the serial mesh. Refine

It would be good to unify and settle for a style of indentation and capitalization that is used in the code. Most class members and some classes miss doxygen style comment blocks.
I would prefer to have spacing on assignments, but if this passed style checking, I have no power here.
Most variable names are still cryptic. I can't make sense of mfem::BlockVector grdbv unless I read the whole code. This is not desirable.
The naming of the main addition ParametricBNLFormIntegrator on the other hand is very verbose. I have no better idea right now in terms of naming.
I know that there is a specific purpose for this implementation. And this is also the point why I don't see this as a good fit for the library. It adds a convenience layer by duplicating functionality of the BlockNonlinearForm and adding parametric fields.
Don't get me wrong, the functionality and implementation is perfectly fine. In my point of view I would rather see a, possibly breaking, interface change in BlockNonlinearForm and putting this functionality in the existing implementation. The addition right now would lead to a maintainability burden that would include 4 classes in total (BlockNLF + ParametricBNLF + Par for each).

I'd like to see a consistent comment and formatting style. Some examples of individual comments throughout
//set the matrix B
//returns the derivative, with respect to the density, of the product
//Provides implementation of an integrator for linear diffusion
// Computes an example of nonlinear objective
//          Define a parallel mesh by a partitioning of the serial mesh. Refine

It would be good to unify and settle for a style of indentation and capitalization that is used in the code. Most class members and some classes miss doxygen style comment blocks.

The comments are made consistent in the revised code.

Most variable names are still cryptic. I can't make sense of mfem::BlockVector grdbv unless I read the whole code. This is not desirable.

Comments have been added for all variables. Longer names will not improve the readability. The current examples are intended to be read step-by-step. The current naming is consistent all block vectors end with bv and the first three letters  stand for gradient, adjoint and primal.

The naming of the main addition ParametricBNLFormIntegrator on the other hand is very verbose. I have no better idea right now in terms of naming.

The name came after a discussion with Jamie. If you have shorter or more explanatory name, please, let me know.

I know that there is a specific purpose for this implementation. And this is also the point why I don't see this as a good fit for the library. It adds a convenience layer by duplicating functionality of the BlockNonlinearForm and adding parametric fields.
Don't get me wrong, the functionality and implementation is perfectly fine. In my point of view I would rather see a, possibly breaking, interface change in BlockNonlinearForm and putting this functionality in the existing implementation. The addition right now would lead to a maintainability burden that would include 4 classes in total (BlockNLF + ParametricBNLF + Par for each).

Adding the parametric form on top of the non-linear block form would require rewriting a quite significant part of MFEM. The parametric fields require additional members in the signatures of the methods in the integrators and the forms. These are irrelevant for non-parametric cases and, apart from the huge amount of work, will decrease the readability of the code. As the BNL form is intended to be used mainly for optimization, one way to avoid the propagation of dependencies in the core MFEM library is to move the form and the integrators in the miniapp directory. Let me know if such a solution will be better in this case.

If the implementation is moved in a miniapp directory I don’t see a problem with it.
I don’t know if thats feasible for you. But I don’t have the last word and I’m certainly not forcing my opinion or “deciding”. It might be good invovle @tzanio  or @v-dobrev to take a look.

I am OK with the current structure. Please also

[ ] Fix Travis
[ ] Update CHANGELOG

If the implementation is moved in a miniapp directory I don’t see a problem with it.
I don’t know if thats feasible for you. But I don’t have the last word and I’m certainly not forcing my opinion or “deciding”. It might be good invovle @tzanio or @v-dobrev to take a look.

To me, the parametric block nonlinear form makes sense to be part of the core mfem classes because it could be useful beyond the mtop miniapp, although I don't have specific use cases in mind. However, for now, I'm not strongly opposed to keep it as part of the miniapp.
@jamiebramwell, what do you think?

If the implementation is moved in a miniapp directory I don’t see a problem with it.
I don’t know if thats feasible for you. But I don’t have the last word and I’m certainly not forcing my opinion or “deciding”. It might be good invovle @tzanio or @v-dobrev to take a look.

To me, the parametric block nonlinear form makes sense to be part of the core mfem classes because it could be useful beyond the mtop miniapp, although I don't have specific use cases in mind. However, for now, I'm not strongly opposed to keep it as part of the miniapp.
@jamiebramwell, what do you think?

Sounds good to me, I just wanted to get your sign-off before adding another assembly routine that needs to be maintained.

My preference actually is to keep things in the subdirectory for now, and move to the core library if/when necessary.

Sounds good to me, I just wanted to get your sign-off before adding another assembly routine that needs to be maintained.

@jamiebramwell, I don't quite understand: which version sounds good to you? (1) Keep the parametric block nonlinear form in the miniapp or (2) make it part of the core mfem library?

Sounds good to me, I just wanted to get your sign-off before adding another assembly routine that needs to be maintained.

@jamiebramwell, I don't quite understand: which version sounds good to you? (1) Keep the parametric block nonlinear form in the miniapp or (2) make it part of the core mfem library?

I was saying moving it into the core library, but I think my opinion should get overruled by you and @tzanio .

One more TODO item:

[ ] Add a documentation PR in the web repo.

@bslazarov, is this ready for merging in next?

One more TODO item:
* [ ]  Add a documentation PR in the [web repo](https://github.com/mfem/web).

I will wait a bit for the full topopt app before adding the documentation

@bslazarov, is this ready for merging in next?

yes, please, go ahead

One more TODO item:
* [ ]  Add a documentation PR in the [web repo](https://github.com/mfem/web).

I will wait a bit for the full topopt app before adding the documentation

If this is included in v4.3, I really think there should be at least some minimal documentation. However, I will defer to the opinion of @tzanio and @v-dobrev .

One more TODO item:
* [ ]  Add a documentation PR in the [web repo](https://github.com/mfem/web).

I will wait a bit for the full topopt app before adding the documentation

If this is included in v4.3, I really think there should be at least some minimal documentation. However, I will defer to the opinion of @tzanio and @v-dobrev .

Ok, then I will add documentation for gradient evaluation :-)

Merged in next for testing...

See also https://github.com/mfem/web/issues/109


Add Fedora path

Also related to #4 maybe.

this add fedora centos red hat other fork and solve ia32 version check for linux
https://github.com/proprietary/chromium-widevine/pull/16


change dll call way

Hello, thank you so much for submitting a PR for us. Please take a moment to relax and kindly provide a description for this PR. Additionally, it would be great if you could also create a corresponding issue for this PR and ensure that your code is properly signed. Thank you for your hard work!


RELEASE: 0.1.55

@fukatani I'll merge this before your review, because this is not code and we want to bump the version quickly.


[Test] Disable some runtime tests in back deployment testing.

These tests are testing changes that aren't present in older runtimes:
test/stdlib/SwiftValueNSObject.swift
test/stdlib/SwiftObjectNSObject.swift
test/stdlib/BridgeEquatableToObjC.swift
And this test looks for some wording that's different on older runtimes. This one already does availability checks, so we change the requirements to SwiftStdlib 5.11:
test/Casting/CastTraps.swift.gyb
rdar://116339747

@swift-ci please smoke test


How do you compute the patterns?

@ranranking can you provide the code/method how you did that?

the patterns i generated with the plugin from FairSIM, i will pack some images with short introduction into the tutorial

Cool. Screenshot with parameters will do the trick :)
On Fri, Apr 26, 2024, 10:48 ranranking @.***> wrote:

the patterns i generated with the plugin from FairSIM, i will pack some
images with short introduction into the tutorial
—
Reply to this email directly, view it on GitHub
https://github.com/openSIMMO/openSIMMO.github.io/issues/31#issuecomment-2078931351,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABBE5OAPKST46OVYFAXIDH3Y7IIHNAVCNFSM6AAAAABGZCNLN2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZYHEZTCMZVGE
.
You are receiving this because you authored the thread.Message ID:
@.***>


now vs2017rc is available,can you update this plug-in?

thank you very much

Please udpate the plug-in