text:
Fix button CSS classes

There are still some buttons that are using btn-lg and not button-large.
All buttons should use materialize's btn-large.

Fixed in #299

repo: OperationCode/operationcode


text:
Add install guide per language.

Need to make it easier for our veterans to install and get coding. Ideas? @dinjas @nanoxd @nellshamrell

Tracking these efforts in the Getting Started milestone. https://github.com/OperationCode/operationcode/milestones/Getting Started

source: gharchive/issue

authors: davidmolina rickr

license: MIT

license_type: permissive

license_source: github-api


text:
[BUG] Users and Roles CRD not been deployed

Hi,
When deploying using the current Helm chart into repository, Operator version is not applying the latest CRD definitions (users, roles and rolebindings).
Command to check:
kubectl get crd after helm installation per documentation

The chart is only updated on release and there has not been a release yet since that feature was added.

authors: danielbichuetti max-frank


text:
Detecting migrations for custom get_func implementations

With the changes in version 3 that creates migrations I've encountered an issue with a custom trigger class that implement get_func to generate the trigger (it's for audit and so the trigger uses the fields currently defined on the model). If the fields on the model change then get_func will be different but it won't currently have migrations created (pgtrigger ls will show it as outdated though).
What's the best way to handle this? I've tried the following, which seems to work, but I'm wondering if I should approach it differently or whether it's something pgtrigger should handle internally:
class PatchedEvent(pghistory.trigger.Event):
    def __init__(self, *args, func=None, **kwargs):
        super().__init__(*args, **kwargs)
        self._init_vals = [args, kwargs, func]

    def get_init_vals(self):
        args, kwargs, func = self._init_vals
        if not func:
            func = self.get_func(self.event_model.pgh_tracked_model)
        return [args, {**kwargs, "func": func}]

    def get_func(self, model):
        ...

@davecoates let me revisit the problem here to shed some light on it (apologies if you already knew all of what I'm about to explain):
Django's migration system serializes things at a point in time so they can be reconstructed. If you pass a model as an argument to a trigger, it will be serialized like this in the migration:
operations=[migrations.AddTrigger(name="something", model="myapp.MyModel")]

The problem with this is when MyModel changes, the serialization of the trigger doesn't change. So the migration system doesn't detect that anything has changed in the trigger.
The best approach is to make it so that the trigger takes arguments that will cause the serialization to change. Your approach should work if the kwargs has all of the fields of the model serialized in it. The automatic trigger serialization code doesn't handle classes with **kwargs in the __init__, which is why you get this error.
I believe there's actually a subtle bug in pghistory that's affecting you though, even with your current updated code. The Snapshot objects in pghistory don't serialize the proper stuff like the example I just laid out.
I don't know the full context of the trigger you're doing and what events are being tracked, but I'd recommend turning on PGTRIGGER_INSTALL_ON_MIGRATE to True for now in your settings to make sure triggers are properly updated after migrations. My plans to address this are:

I can handle *args and **kwargs for custom triggers automatically. It should be straightforward and prevent people from having to do serialization stuff in custom triggers
Next week my plans are to finally blast through a lot of the outstanding pghistory tickets now that pgtrigger has stabilized more. Although I haven't reproduced it, I do think there's a bug with the Snapshot stuff that doesn't completely work with migrations. I'll tag you in an issue over on pghistory once I get around to reproducing it.

Will keep this open for now until I create the proper issues or address it

Just confirmed that there isn't a bug in the snapshot stuff in pghistory. The condition is tracked in the migrations even when no fields are specified, so the trigger continues to be migrated properly.
I still plan to follow up on 1) so that you can use **kwargs. In the meantime an immediate approach you can take is to explicitly list the arguments of the trigger:
def __init__(
        self,
        *,
        name=None,
        operation=None,
        condition=None,
        when=None,
        label=None,
        snapshot=None,
        event_model=None,
        func=None
    ):

I think the above would be a better way of handling it for now, assuming it works for your use case

Thanks for the explanation - that helps. I'm a bit confused about pghistory Snapshot though - won't this suffer from a stale 'insert' trigger if you add a new field to a model? The 'update' trigger will be fine because condition changes but for insert nothing would change in the arguments passed to pghistory.trigger.Event.
I tried with an example from the docs by decorating a model with @pghistory.track(pghistory.Snapshot("test_model.snapshot"))
The initial migration created fine and after adding a new field the 'update' trigger was dropped and recreated but the insert was left untouched. Have I missed something here?
Apologies if this has progressed into pghistory territory - when I opened this I was thinking about the general case with pgtrigger. As a hypothetical say there was a bug in the trigger code for pgtrigger.SoftDelete that required a change in the string returned from get_func - what would be best way to handle that in regards to generating migrations in projects that were already using the buggy version?

The initial migration created fine and after adding a new field the 'update' trigger was dropped and recreated but the insert was left untouched. Have I missed something here?

No you are absolutely correct! Thanks for bringing this to my attention. I'm dedicating next week to pghistory and will plan on addressing this.

As a hypothetical say there was a bug in the trigger code for pgtrigger.SoftDelete that required a change in the string returned from get_func - what would be best way to handle that in regards to generating migrations in projects that were already using the buggy version?

If I understand, you're effectively asking about the same type of issue uncovered with pghistory, right? That is, if the underlying SQL changes but the class instantiation doesn't change, how does the migration system know to update it?
I think one way for me to solve this is to introduce a hash argument that's supplied to the __init__ of the base trigger class. It's a totally useless argument that users shouldn't supply, but it's there for migration serialization and for the equality operator of those migration objects.
Triggers already have a unique hash that's computed based on the SQL and stored alongside the trigger object (it's how pgtrigger ls knows what is outdated), so it's a pretty easy addition that can help make the migration integration more robust. It should also solve the issue of pghistory without any substantial changes.

I'm going to go ahead and integrate this into django-pgtrigger and mark this as a bug.
Basically what I'm going to do is design a test case around your use case - a custom trigger that implements get_func with no real changes to the __init__. When the function changes, it should result in migrations being re-generated using that hash approach I just mentioned.
I'm going to try to do this in a way so that it doesn't break the API, probably by adjusting the migration operation so that it takes the hash instead of the trigger class itself. Will see what I'm able to come up with and will let you know!

If I understand, you're effectively asking about the same type of issue uncovered with pghistory, right? That is, if the underlying SQL changes but the class instantiation doesn't change, how does the migration system know to update it?

Yep exactly that

I think one way for me to solve this is to introduce a hash argument that's supplied to the init of the base trigger class. It's a totally useless argument that users shouldn't supply, but it's there for migration serialization and for the equality operator of those migration objects.

That sounds good and sounds like it would resolve my issue without needing to implement get_init_vals

I'm going to try to do this in a way so that it doesn't break the API, probably by adjusting the migration operation so that it takes the hash instead of the trigger class taking the hash as an argument. Will see what I'm able to come up with and will let you know!

Excellent, thank you

@davecoates this has been fixed in version 4.5. When triggers are serialized to migrations, a different trigger compilation object is serialized instead of the main trigger class. This object is basically just a representation of the raw SQL.
The nice thing about this approach:

Custom trigger classes can be changed without worrying about breaking previous migrations. You can even change the class name of the trigger and it will work fine.
The SQL can be versioned more easily. For example, if something needs to fundamentally change in how triggers are installed one day, previous migrations can still be reversed and reference the old trigger definition.
Issues like what was happening in pghistory are fixed. When the underlying SQL changes, the trigger will be migrated.

One caveat with this approach is that it re-creates all triggers when you make migrations. I didn't have too many ways to get around this, but thankfully I don't see a reason this would need to happen again. You should be able to fake the migration, although it's usually harmless to run it and update all the triggers.
The pgtrigger test suite dynamically makes models/migrations and updates them to verify things work. Along with this, I tested out this change with a few projects of mine. I serialized triggers the old way, switched versions, and then made migrations again. Things look good, so I'm going to mark this as fixed.

I've briefly tried this and seems to work great, thanks 👍

authors: davecoates wesleykendall


text:
[OUDS] Drop Percy

Description
Percy is installed and configured for Boosted. Percy is a visual testing tool as a service that captures screenshots and compares them to baseline images to detect visual changes and regressions. It was used occasionally in the past, but its usage has diminished significantly. This decline is mainly due to the limitations on usage and the requirement for it to be run manually on the main branch.
Given these factors, it is proposed that this development dependency be removed from OUDS Web.
The goal of this issue is straightforward: remove the Percy dependency and eliminate all references to Percy in the project's files.

Closed by https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/pull/2581

license: mit

license_source: bigquery


text:
Do not expose thrift port by default

The CassandraCluster service expose the thrift port in additional to the CQL port. Thrift is disabled by default in Cassandra 3.11.4 and will altogether be removed in Cassandra 4.0. The thrift port should not be exposed, at least not by default.

I think I have removed them in another PR
Sébastien
Le 10 juil. 2019 à 21:44, John Sanda <notifications@github.commailto:notifications@github.com> a écrit :
The CassandraCluster service expose the thrift port in additional to the CQL port. Thrift is disabled by default in Cassandra 3.11.4 and will altogether be removed in Cassandra 4.0. The thrift port should not be exposed, at least not by default.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/Orange-OpenSource/cassandra-k8s-operator/issues/44?email_source=notifications&email_token=ACEKVY6S7K5UK6L3QYBWT5TP6Y33PA5CNFSM4H7STKJKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G6N77AQ, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACEKVY5WUGFX4KPYKP6VKTLP6Y33PANCNFSM4H7STKJA.

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

@allamand thanks for the reference!
Since it is a headless service, the ports are not used. Considering this, does it make sense for the service to expose them? I am not sure what the standard practice is for headless services with respect to ports.
As it stands right now, if a cluster uses a non-default value for one of the ports, the service ports will be incorrect.

@jsanda I removed ports from headless service and from the pod generated by the statefulset, so ports may not be exposed at all, I think this is sufficient.
But you are right, for now, the ports must match the one exposed by the docker image, for now this is done with our associate cassandra base image, and we may rely on an InitContainer to configure that in futur to adapt from "any" cassandra base image

@jsanda @allamand, we need those ports to be exposed in the headless service when we use Istio. That's how istio figures out what ports need to be proxyfied. In short, it doesn't hurt to have them in the headless service and help us when we use istio. Otherwise we would have to guess if istio is enabled and expose them only in that case but I don't feel the effort worths it.

@cscetbon thanks for the explanation. Currently those ports are hard coded. Shouldn't the ports values come the cluster configuration, i.e., what is defined in cassandra.yaml?

@jsanda I don't think so. In containers you don't really need to configure those ports to have different values as listeners are not really listening on those ports and port forwarding is intensively used automatically by kubernetes/docker. There are no real reasons to use different ports IMHO.

I think so

authors: Orange-cscetbon allamand cscetbon jsanda


text:
ODS - Component - Cards: Small Card

[x] #109
[x] #110

@mccart77  the most important issue to resolve here is the typograty token correspondance between ios and android. Follow the issue in here: #144

repo: Orange-OpenSource/ods-flutter


text:
Impossible to start a new instance on an existing SQL Server Database

Context :
Sql Server 13.0
Windows 11
VS 2019 16.11.22
Orchard freshly cloned from https://github.com/OrchardCMS/Orchard.git
Empty Database created on the server
Starting the Orchard.Web project leads to http://localhost:30321/OrchardLocal/ with the "Get Started" page. Choosing "Use an existing SQL Server, SQL Express database" and filling the "Connection string".
After validation, this error pops up in Visual Studio on line 36 of OrchardCMS\src\Orchard\Data\FetchRequest.cs :
NHibernate.Exceptions.GenericADOException : 'could not execute query
[ select contentpar0_.Id as Id12_0_, contentpar1_.Id as Id13_1_, contentfie2_.Id as Id11_2_, contentpar0_.Name as Name12_0_, contentpar0_.Hidden as Hidden12_0_, contentpar0_.Settings as Settings12_0_, contentpar1_.Name as Name13_1_, contentpar1_.Settings as Settings13_1_, contentpar1_.ContentFieldDefinitionRecord_id as ContentF4_13_1_, contentpar1_.ContentPartDefinitionRecord_id as ContentP5_0__, contentpar1_.Id as Id0__, contentfie2_.Name as Name11_2_ from Settings_ContentPartDefinitionRecord contentpar0_ left outer join Settings_ContentPartFieldDefinitionRecord contentpar1_ on contentpar0_.Id=contentpar1_.ContentPartDefinitionRecord_id left outer join Settings_ContentFieldDefinitionRecord contentfie2_ on contentpar1_.ContentFieldDefinitionRecord_id=contentfie2_.Id ]
[SQL: select contentpar0_.Id as Id12_0_, contentpar1_.Id as Id13_1_, contentfie2_.Id as Id11_2_, contentpar0_.Name as Name12_0_, contentpar0_.Hidden as Hidden12_0_, contentpar0_.Settings as Settings12_0_, contentpar1_.Name as Name13_1_, contentpar1_.Settings as Settings13_1_, contentpar1_.ContentFieldDefinitionRecord_id as ContentF4_13_1_, contentpar1_.ContentPartDefinitionRecord_id as ContentP5_0__, contentpar1_.Id as Id0__, contentfie2_.Name as Name11_2_ from Settings_ContentPartDefinitionRecord contentpar0_ left outer join Settings_ContentPartFieldDefinitionRecord contentpar1_ on contentpar0_.Id=contentpar1_.ContentPartDefinitionRecord_id left outer join Settings_ContentFieldDefinitionRecord contentfie2_ on contentpar1_.ContentFieldDefinitionRecord_id=contentfie2_.Id]'
Then, on the "Get Started" page, another error is displayed :
Setup failed: could not execute query
[ select contenttyp0_.Id as Id5_, contenttyp0_.Name as Name5_ from Orchard_Framework_ContentTypeRecord contenttyp0_ where contenttyp0_.Name=@p0 ]
Name:p1 - Value:Site
[SQL: select contenttyp0_.Id as Id5_, contenttyp0_.Name as Name5_ from Orchard_Framework_ContentTypeRecord contenttyp0_ where contenttyp0_.Name=@p0]
If I look at the Database, there's only one table : Orchard_Framework_DataMigrationRecord
So Orchard had access to the database and even created a table but there is nothing there like Orchard_Framework_ContentTypeRecord or Settings_ContentPartDefinitionRecord
I'm clueless on how to fix that.
Thank you in advance for your help.

Can you check the log file after the first error?

Sure here you go :
2023-06-16 09:31:57,048 [6] Orchard.Data.Migration.DataMigrationManager - Default - Error while running migration version 0 for Settings. [http://localhost:30321/OrchardLocal/]
System.Reflection.TargetInvocationException: Une exception a été levée par la cible d'un appel. ---> NHibernate.Exceptions.GenericADOException: could not execute query
[ select contentpar0_.Id as Id12_0_, contentpar1_.Id as Id13_1_, contentfie2_.Id as Id11_2_, contentpar0_.Name as Name12_0_, contentpar0_.Hidden as Hidden12_0_, contentpar0_.Settings as Settings12_0_, contentpar1_.Name as Name13_1_, contentpar1_.Settings as Settings13_1_, contentpar1_.ContentFieldDefinitionRecord_id as ContentF4_13_1_, contentpar1_.ContentPartDefinitionRecord_id as ContentP5_0__, contentpar1_.Id as Id0__, contentfie2_.Name as Name11_2_ from Settings_ContentPartDefinitionRecord contentpar0_ left outer join Settings_ContentPartFieldDefinitionRecord contentpar1_ on contentpar0_.Id=contentpar1_.ContentPartDefinitionRecord_id left outer join Settings_ContentFieldDefinitionRecord contentfie2_ on contentpar1_.ContentFieldDefinitionRecord_id=contentfie2_.Id ]
[SQL: select contentpar0_.Id as Id12_0_, contentpar1_.Id as Id13_1_, contentfie2_.Id as Id11_2_, contentpar0_.Name as Name12_0_, contentpar0_.Hidden as Hidden12_0_, contentpar0_.Settings as Settings12_0_, contentpar1_.Name as Name13_1_, contentpar1_.Settings as Settings13_1_, contentpar1_.ContentFieldDefinitionRecord_id as ContentF4_13_1_, contentpar1_.ContentPartDefinitionRecord_id as ContentP5_0__, contentpar1_.Id as Id0__, contentfie2_.Name as Name11_2_ from Settings_ContentPartDefinitionRecord contentpar0_ left outer join Settings_ContentPartFieldDefinitionRecord contentpar1_ on contentpar0_.Id=contentpar1_.ContentPartDefinitionRecord_id left outer join Settings_ContentFieldDefinitionRecord contentfie2_ on contentpar1_.ContentFieldDefinitionRecord_id=contentfie2_.Id] ---> System.Data.SqlClient.SqlException: Nom de colonne non valide : 'ContentPartDefinitionRecord_id'.
Nom de colonne non valide : 'ContentPartDefinitionRecord_id'.
à System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction)    à System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)    à System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)    à System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()    à System.Data.SqlClient.SqlDataReader.get_MetaData()    à System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted)    à System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest)    à System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
à System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
à System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
à NHibernate.AdoNet.AbstractBatcher.ExecuteReader(IDbCommand cmd)
à NHibernate.Loader.Loader.GetResultSet(IDbCommand st, Boolean autoDiscoverTypes, Boolean callable, RowSelection selection, ISessionImplementor session)
à NHibernate.Loader.Loader.DoQuery(ISessionImplementor session, QueryParameters queryParameters, Boolean returnProxies, IResultTransformer forcedResultTransformer)
à NHibernate.Loader.Loader.DoQueryAndInitializeNonLazyCollections(ISessionImplementor session, QueryParameters queryParameters, Boolean returnProxies, IResultTransformer forcedResultTransformer)
à NHibernate.Loader.Loader.DoList(ISessionImplementor session, QueryParameters queryParameters, IResultTransformer forcedResultTransformer)
--- Fin de la trace de la pile d'exception interne ---
à NHibernate.Loader.Loader.DoList(ISessionImplementor session, QueryParameters queryParameters, IResultTransformer forcedResultTransformer)
à NHibernate.Loader.Loader.ListIgnoreQueryCache(ISessionImplementor session, QueryParameters queryParameters)
à NHibernate.Loader.Hql.QueryLoader.List(ISessionImplementor session, QueryParameters queryParameters)
à NHibernate.Hql.Ast.ANTLR.QueryTranslatorImpl.List(ISessionImplementor session, QueryParameters queryParameters)
à NHibernate.Engine.Query.HQLQueryPlan.PerformList(QueryParameters queryParameters, ISessionImplementor session, IList results)
à NHibernate.Impl.SessionImpl.List(IQueryExpression queryExpression, QueryParameters queryParameters, IList results)
à NHibernate.Impl.AbstractSessionImpl.List(IQueryExpression queryExpression, QueryParameters parameters)
à NHibernate.Impl.AbstractQueryImpl2.List()
à NHibernate.Linq.DefaultQueryProvider.ExecuteQuery(NhLinqExpression nhLinqExpression, IQuery query, NhLinqExpression nhQuery)
à NHibernate.Linq.DefaultQueryProvider.Execute(Expression expression)
à NHibernate.Linq.DefaultQueryProvider.Execute[TResult](Expression expression)
à Remotion.Linq.QueryableBase1.GetEnumerator()    à Orchard.Data.FetchRequest2.GetEnumerator() dans C:\Travail\OrchardCMS\src\Orchard\Data\FetchRequest.cs:ligne 36
à System.Linq.Enumerable.WhereSelectEnumerableIterator2.MoveNext()    à System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable1 source, Func2 keySelector, Func2 elementSelector, IEqualityComparer1 comparer)    à Orchard.Core.Settings.Metadata.ContentDefinitionManager.<AcquireContentPartDefinitions>b__20_0(AcquireContext1 ctx) dans C:\Travail\OrchardCMS\src\Orchard.Web\Core\Settings\Metadata\ContentDefinitionManager.cs:ligne 151
à Orchard.Caching.Cache2.CreateEntry(TKey k, Func2 acquire) dans C:\Travail\OrchardCMS\src\Orchard\Caching\Cache.cs:ligne 57
à Orchard.Caching.Cache2.AddEntry(TKey k, Func2 acquire) dans C:\Travail\OrchardCMS\src\Orchard\Caching\Cache.cs:ligne 27
à Orchard.Caching.Cache2.<>c__DisplayClass3_0.<Get>b__0(TKey k) dans C:\Travail\OrchardCMS\src\Orchard\Caching\Cache.cs:ligne 19    à System.Collections.Concurrent.ConcurrentDictionary2.AddOrUpdate(TKey key, Func2 addValueFactory, Func3 updateValueFactory)
à Orchard.Caching.Cache2.Get(TKey key, Func2 acquire) dans C:\Travail\OrchardCMS\src\Orchard\Caching\Cache.cs:ligne 17
à Orchard.Caching.DefaultCacheManager.Get[TKey,TResult](TKey key, Func2 acquire) dans C:\Travail\OrchardCMS\src\Orchard\Caching\DefaultCacheManager.cs:ligne 33    à Orchard.Caching.CacheManagerExtensions.Get[TKey,TResult](ICacheManager cacheManager, TKey key, Boolean preventConcurrentCalls, Func2 acquire) dans C:\Travail\OrchardCMS\src\Orchard\Caching\ICacheManager.cs:ligne 13
à Orchard.Core.Settings.Metadata.ContentDefinitionManager.AcquireContentPartDefinitions() dans C:\Travail\OrchardCMS\src\Orchard.Web\Core\Settings\Metadata\ContentDefinitionManager.cs:ligne 143
à Orchard.Core.Settings.Metadata.ContentDefinitionManager.b__19_0(AcquireContext1 ctx) dans C:\Travail\OrchardCMS\src\Orchard.Web\Core\Settings\Metadata\ContentDefinitionManager.cs:ligne 131    à Orchard.Caching.Cache2.CreateEntry(TKey k, Func2 acquire) dans C:\Travail\OrchardCMS\src\Orchard\Caching\Cache.cs:ligne 57    à Orchard.Caching.Cache2.AddEntry(TKey k, Func2 acquire) dans C:\Travail\OrchardCMS\src\Orchard\Caching\Cache.cs:ligne 27    à Orchard.Caching.Cache2.<>c__DisplayClass3_0.b__0(TKey k) dans C:\Travail\OrchardCMS\src\Orchard\Caching\Cache.cs:ligne 19
à System.Collections.Concurrent.ConcurrentDictionary2.AddOrUpdate(TKey key, Func2 addValueFactory, Func3 updateValueFactory)    à Orchard.Caching.Cache2.Get(TKey key, Func2 acquire) dans C:\Travail\OrchardCMS\src\Orchard\Caching\Cache.cs:ligne 17    à Orchard.Caching.DefaultCacheManager.Get[TKey,TResult](TKey key, Func2 acquire) dans C:\Travail\OrchardCMS\src\Orchard\Caching\DefaultCacheManager.cs:ligne 33
à Orchard.Caching.CacheManagerExtensions.Get[TKey,TResult](ICacheManager cacheManager, TKey key, Boolean preventConcurrentCalls, Func2 acquire) dans C:\Travail\OrchardCMS\src\Orchard\Caching\ICacheManager.cs:ligne 13    à Orchard.Core.Settings.Metadata.ContentDefinitionManager.AcquireContentTypeDefinitions() dans C:\Travail\OrchardCMS\src\Orchard.Web\Core\Settings\Metadata\ContentDefinitionManager.cs:ligne 128    à Orchard.Core.Settings.Metadata.ContentDefinitionManager.GetTypeDefinition(String name) dans C:\Travail\OrchardCMS\src\Orchard.Web\Core\Settings\Metadata\ContentDefinitionManager.cs:ligne 44    à Orchard.ContentManagement.MetaData.ContentDefinitionManagerExtensions.AlterTypeDefinition(IContentDefinitionManager manager, String name, Action1 alteration) dans C:\Travail\OrchardCMS\src\Orchard\ContentManagement\MetaData\IContentDefinitionManager.cs:ligne 24
à Orchard.Core.Settings.Migrations.Create() dans C:\Travail\OrchardCMS\src\Orchard.Web\Core\Settings\Migrations.cs:ligne 85
--- Fin de la trace de la pile d'exception interne ---
à System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
à System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
à System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
à System.Reflection.MethodBase.Invoke(Object obj, Object[] parameters)
à Orchard.Data.Migration.DataMigrationManager.Update(String feature) dans C:\Travail\OrchardCMS\src\Orchard\Data\Migration\DataMigrationManager.cs:ligne 115
I have found a workarround by starting with a SqlServer CE then droping the database with SqlCe40ToolBox.zip then restoring that database on our Sql Server instance. I then had to tweak Settings.txt in App_Data and I think I suppressed the mappings.bin also. Not so simple but it eventually does work.

authors: ceddup sebastienros

repo: OrchardCMS/Orchard


text:
OFFI-126: Adding several Stripe API endpoints and basics of Subscription

OFFI-126

I forgot to mention this, but any breaking change should be documented in https://github.com/OrchardCMS/OrchardCore.Commerce/blob/main/docs/releases/3.0.0.md. Also at this point there is no need to leave [Obsolete] methods, because we will immediately release 3.0.0 after NEST-537.

source: gharchive/pull-request

authors: sarahelsaig wAsnk


text:
Mod packaged improperly

          I left a comment on ESO.UI. The files aren't in their own "folder" when installing through Minion. The LibRandomMount, Localization folders and the manifest and LUA files get installed in the addons folder. ESO doesn't recognize the addon as being installed. I have moved my files in to a folder named RandomMount.

I also think that having the extra API versions in the manifest are making it state that it's out of date. If you change that text file to say 101037 101038 it removers the "out of date" in the addons list.
Originally posted by @sshogrin in https://github.com/Oricul/eso-RandomMount/issues/6#issuecomment-1604303115

I've corrected this and re-uploaded 3.7.

It's also not pulling out the random mount when you have a companion out or when grouped.

authors: Oricul sshogrin

repo: Oricul/eso-RandomMount


text:
Malformed HTML when tags are in translated strings

Example
{{gettext("Anything else we should know? (optional)")}}
Result

To Do
1) Remove tags from gettext strings
2) Manually edit existing messages.po files

Here are the strings that need manual edits: https://github.com/micahalcorn/company-website/commit/3f5ee845dfae152fd791ff52c54d5a554b9360d1

I am on it!

I think we got all these fixed. Thanks @evra6965 for your help!

authors: evra6965 micahalcorn wanderingstan

repo: OriginProtocol/company-website


text:
Update supported network detection

Detection of supported networks needs to be updated for mainnet. Right now we'll generate an error if PRODUCTION_DOMAIN is set and we are not on one of the testnets.
Perhaps a separate environment variable should be added to determine if we are in staging vs production.
@micahalcorn I think this might need a p0 tag?

Looking at this.
We currently determine production based on env var NODE_ENV:
https://github.com/OriginProtocol/origin-dapp/blob/master/webpack.config.js#L10

@wanderingstan I think I was using PRODUCTION_DOMAIN in the past so that my Heroku URL would behave like the production environment. But that's probably not necessary.

PR here: https://github.com/OriginProtocol/origin-dapp/pull/601

authors: micahalcorn tomlinton wanderingstan

repo: OriginProtocol/origin-dapp


text:
Packer base

Выполнено ДЗ № 6 "Модели управления инфраструктурой Packer"

[x] Основное ДЗ
[x] Задание со *

В процессе сделано:

Создан образ reddit-base
Создана виртуальная машина на основе созданного образа.
Установлено правило сетевого экрана для порта tcp/9292
Выполнено самостоятельное задание с параметризацией парамеров.
(*) Выполнено задание по сборке образа reddit-full с установкой юнита systemd для puma
(*) Выполнено задание по созданию скрипта для автоматизации создания виртуальной машины на основе образа reddit-full

Как запустить проект:

Скорректировать файл ubuntu16.json и создать на основе variables.json.example файл с параметрами проекта GCP и собрать образ следующей командой.

packer build ubuntu16.json

Далее создать на основе образа виртуальную машину.
2. Скорректировать файл immutable.json и создать образ по аналогии с предыдущим пунктом. Затем создать ВМ.
Как проверить работоспособность:

После создания ВМ перейти по ссылке public_vm_ip:9292

PR checklist

[x] Выставил label с номером домашнего задания
[x] Выставил label с темой домашнего задания
...

merge packer branch to master


text:
cloud-bastion

Getting acquainted with Yandex.Cloud infrastructure
Connection data
bastion_IP = 158.160.129.53
someinternalhost_IP = 10.131.0.30

Сonnect through VPN
cat << EOF > secret
test
6214157507237678334670591556762
EOF
sudo openvpn --config cloud-bastion.ovpn --auth-user-pass secret
ssh -i ~/.ssh/appuser -J appuser@158.160.129.53 appuser@10.131.0.30

Create aliases
1. Config file to ssh

    nano ~/.ssh/config

    Host someinternalhost
        Hostname 10.131.0.30
        User appuser
        ProxyJump bastion
    Host bastion
        User appuser
        Hostname 158.160.129.53

    ssh someinternalhost

2. Alias "~/.bashrc"

    echo "alias someinternalhost='ssh -i ~/.ssh/appuser -J appuser@158.160.129.53 appuser@10.131.0.30'" >> ~/.bashrc
    source ~/.bashrc

    someinternalhost

Add certificate returned and "nip.io":
Domain: bast.158.160.129.53.nip.io

Response: {
    "type": "urn:ietf:params:acme:error:rateLimited",
    "detail": "Error creating new order :: too many certificates already issued for \"nip.io\". Retry after 2024-01-05T08:00:00Z: see https://letsencrypt.org/docs/rate-limits/",
    "status": 429
}

student Ilya Korytov


text:
Update sbt-scalajs, scalajs-compiler, ... to 1.5.0

Updates

org.scala-js:sbt-scalajs
org.scala-js:scalajs-compiler
org.scala-js:scalajs-library
org.scala-js:scalajs-test-bridge

from 1.2.0 to 1.5.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (1.2.0).
You might want to review and update them manually.
bench/yarn.lock
monix/yarn.lock
outwatch/yarn.lock
reactive/yarn.lock
repairdom/yarn.lock
snabbdom/yarn.lock
tests/yarn.lock
util/yarn.lock

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-js" } ]

labels: library-update, semver-minor, old-version-remains

Superseded by #501.

repo: OutWatch/outwatch


text:
sealevel: implement sol_sha256 syscall

Implement the sha256 hash syscall and tests.

sol_sha256 syscall and a testcase has been added in this commit: https://github.com/Overclock-Validator/radiance/commit/2995be3ab12d9ccbc4aadafe7ccd1d067c02c118

repo: Overclock-Validator/radiance