[stable/prometheus-operator] how to use an existed Persistent Volume Claim

Is this a request for help?:
yes
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT

Version of Helm and Kubernetes:
helm: v2.11.0
k8s: v1.11.2
Which chart:
stable/prometheus-operator
What happened:
I have already created PV and PVC, and I want to use the existed PVC for prometheus server. But in prometheus-operator, I found that value.yaml only has volumeClaimTemplate configuration.  In prometheus-operator storage's user-guide, it seems like volumeClaimTemplate is to create PVC dynamic. So I wander how to use PVC which I have created, like volumeMounts in prometheus.
link
https://github.com/coreos/prometheus-operator/blob/master/Documentation/user-guides/storage.md
volumeClaimTemplate:
    description: PersistentVolumeClaim is a user's request for and claim
     to a persistent volume

What you expected to happen:
I want to use PVC that I have created

You should only create the PV (not the PVC) beforehand.  prometheus-operator can automatically create a PVC based on an existing PV.
For example, my default-values.yaml:
prometheus:
  prometheusSpec:
    storageSpec:
      volumeClaimTemplate:
        spec:
          # Name of the PV you created beforehand
          volumeName: MY-PREEXISTING-PV
          accessModes: ["ReadWriteOnce"]
          # StorageClass should match your existing PV's storage class
          storageClassName: gp2
          resources:
            requests:
              # Size below should match your existing PV's size
              storage: 500

Keep in mind, if you do a helm delete on your chart, the PVC will not be cleaned up.

You should only create the PV (not the PVC) beforehand. prometheus-operator can automatically create a PVC based on an existing PV.
For example, my default-values.yaml:
prometheus:
  prometheusSpec:
    storageSpec:
      volumeClaimTemplate:
        spec:
          # Name of the PV you created beforehand
          volumeName: MY-PREEXISTING-PV
          accessModes: ["ReadWriteOnce"]
          # StorageClass should match your existing PV's storage class
          storageClassName: gp2
          resources:
            requests:
              # Size below should match your existing PV's size
              storage: 500

Keep in mind, if you do a helm delete on your chart, the PVC will not be cleaned up.

Thank you so much. I found that the root  reason is that the storage which I used don't support dynamic storage volume. I will close this issue.

Hi,
I got it working with this hack - use the SAME names and labels for your existing PV and PVC.
If you would like to keep the data of the current persistent volumes, it should be possible to attach existing volumes to new PVCs and PVs that are created using the conventions in the new chart. For example, in order to use an existing Azure disk for a helm release name called prometheus-operator the following resources can be created:
Create the disk references before deploying the operating
`apiVersion: v1
kind: PersistentVolume
metadata:
name: pvc-prometheus-operator-prometheus-0
spec:
storageClassName: "standard"
capacity:
storage: 64Gi
accessModes:
- ReadWriteOnce
gcePersistentDisk:
pdName: gke-dev-romiko-aae-pvc-c8971937-85f8-2566-b80e-710dfbc17cbb
fsType: ext4
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
labels:
app: prometheus
prometheus: prometheus-operator-prometheus
name:  prometheus-prometheus-operator-prometheus-db-prometheus-prometheus-operator-prometheus-0
spec:
storageClassName: "standard"
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 64Gi`
In Prometheus Helm Value files
prometheus:         prometheusSpec:       storageSpec:         volumeClaimTemplate:           spec:             storageClassName: standard             resources:               requests:                 storage: 64Gi

 romiko  DESKTOP-JDAU614  mnt  c  Windows  System32  %  k get pvc
NAME                                                                                STATUS   VOLUME                                 CAPACITY   ACCESS MODES   STORAGECLASS   AGE
prometheus-prometheus-operator-prometheus-db-prometheus-prometheus-operator-prometheus-0   Bound    pvc-prometheus-operator-prometheus-0   64Gi       RWO            standard       4m25s
pv-claim-grafana                                                                           Bound    pv-grafana                             10Gi       RWO            standard       47m
 romiko  DESKTOP-JDAU614  mnt  c  Windows  System32  %  k get pv
NAME                                   CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                                                                                STORAGECLASS   REASON   AGE
pv-grafana                             10Gi       RWO            Retain           Bound    service-compliance/pv-claim-grafana                                                                           standard                47m
pvc-prometheus-operator-prometheus-0   64Gi       RWO            Retain           Bound    service-compliance/prometheus-prometheus-operator-prometheus-db-prometheus-prometheus-operator-prometheus-0   standard                4m29s
 romiko  DESKTOP-JDAU614  mnt  c  Windows  System32  % 

@Romiko I also did this myself and it works. Although when I helm upgrade the release, I get this and can't figure it out:
Error: error validating "": error validating data: ValidationError(Prometheus.spec.storage.volumeClaimTemplate): unknown field "selector" in com.coreos.monitoring.v1.Prometheus.spec.storage.volumeClaimTemplate

are you able to helm upgrade your release ?

@Romiko I also did this myself and it works. Although when I helm upgrade the release, I get this and can't figure it out:
Error: error validating "": error validating data: ValidationError(Prometheus.spec.storage.volumeClaimTemplate): unknown field "selector" in com.coreos.monitoring.v1.Prometheus.spec.storage.volumeClaimTemplate

are you able to helm upgrade your release ?

The indentation for selector in the example in the default values seems to be off by two spaces.
It should be:
    storage: {}
    # volumeClaimTemplate:
    #   spec:
    #     storageClassName: gluster
    #     accessModes: ["ReadWriteOnce"]
    #     resources:
    #       requests:
    #         storage: 50Gi
    #     selector: {}  <----- indentation adjusted by two spaces

@Romiko Thanks for advise about labels! I successfully replaced pv/pvc to others with different storage class without touching helm.

@Romiko Thanks for advise about labels! I successfully replaced pv/pvc to others with different storage class without touching helm.


Async function calling does not work in nested chat [Bug]:

Describe the bug
Nested chat does not work with async tool usage
Steps to reproduce
Convert Scenario 2 example of nested chat available here to use async functions: https://microsoft.github.io/autogen/docs/notebooks/agentchat_nestedchat/
Use the following steps:
a) change function definition of check_harmful_content to be async
b) change user_proxy.initiate_chat to await user_proxy.a_initiate_chat
Observed Behavior:
The system gets stuck after triggering nested chat but before tool usage. After a timeout period returns with the error message:
RuntimeError: This event loop is already running
sys:1: RuntimeWarning: coroutine 'ConversableAgent.a_execute_function' was never awaited

in the line in ConversableAgent
  _, func_return = loop.run_until_complete(self.a_execute_function(function_call))
Temporary work around:
import nest_asyncio
nest_asyncio.apply()

Model Used
gpt-4-turbo-preview
Expected Behavior
Async function calling works even in nested chat
Screenshots and logs
No response
Additional Information
No response

@qingyun-wu

我的界面和别人不一样 而且没有任何反应


macOS: do not require admin group to change default version?

Maybe? Cf. https://github.com/r-lib/rig/issues/157
At least we should document this, and give a better error message.

There is a better error message now:
rig@Gabors-MacBook-Pro-3 rig % ./target/debug/rig default 4.3-arm64
[ERROR] Could not change the default R version. :( To be able to
        change the default R version, you need to be an admin.
        See the 'Users & Groups' section in the 'System Settings' app.


Support shortcut keys

Can the plug-in support shortcut keys? For example, in Excel, pressing Ctrl + D will copy the contents of the upper cells,
Also, can I use the arrow keys to move between cells

its a pending task, for sure!
added to the roadmap :)

I would love to have the arrow keys to jump between cells as well, would be nice if you could prioritize this feature. Its the only feature missing for me to make the jump from notion databases to obsidian databases.
Editing the tags / cells of huge databases is a huge pain without shortcuts.
Arrow keys to move between cells and Enter to edit the cell would be the best.
Just copy the UX and Shortcuts of Notion - people are used to it and dont need to change their muscle memory. :)

Sure it will be helpful. This will arrive as soon as we can. Copy that features is not trivial.
Some request has more priority right now like mobile version. Any help will be welcome!

Any hint on where to start? I also would like to have this/these feature(s).

Hi @mostlikely , its not in my plans in short terms but surely I will dev this. Currently working on formulas

I think he meant that he is willing to help on this issue @RafaelGB, and he asked for some tips on where he could start when it comes to developing this feature. (I'm sorry if I got it wrong)

oh I see, You need to generate new commands on the main js
You already have 1 example on registerCommands() function.  Then we need to vincúlate the action of those commands to the current database that is open with hotkeys. There are some examples on obsidian kanban plugin

On MacOSX I discovered that this can be done but not consistently for all fields:
Enter a field for editing (there should exist a next field to the right of this field), hit ESC.
To change to the next field on the right: Hit TAB two times (you won't see anything happening), then ENTER.
Magically the you can now type in the next field (at least in most cases I tried).

By default, the framework used by the plugin (https://tanstack.com/table/v8/docs/guide/introduction) has tabulation detection, but just with the opened inputs. We have to investigate how to use that tabulation properly.
The core idea is to use tabindex

just wanted to +1 arrow key navigation as a desired feature :)

[ ] add row
[ ] Enable/Disable filter
[ ] Open filter modal


Fix: Replace the wrong symbol '+' with '=' in formulation related to chain rule

Replace the wrong symbol '+' with '=' in formulation related to chain rule.
Wrong Origin:
$$\frac{\partial h_t}{\partial w_h}= \frac{\partial f(x_{t},h_{t-1},w_h)}{\partial w_h} +\frac{\partial f(x_{t},h_{t-1},w_h)}{\partial h_{t-1}} \frac{\partial h_{t-1}}{\partial w_h}.$$
Revision:
$$\frac{\partial h_t}{\partial w_h}= \frac{\partial f(x_{t},h_{t-1},w_h)}{\partial w_h} =\frac{\partial f(x_{t},h_{t-1},w_h)}{\partial h_{t-1}} \frac{\partial h_{t-1}}{\partial w_h}.$$

Sorry, I think I got some wrong understandation for the formulation, because both $h_{t - 1}$ and $w_h$ is related to $w_h$，according to chain rule，there should be:
$$\frac{\partial f(g(x), h(x))}{\partial x} = \frac{\partial f(g(x), h(x))}{\partial g(x)} \frac{\partial g(x)}{\partial x} + \frac{\partial f(g(x), h(x))}{\partial h(x)} \frac{\partial h(x)}{\partial x}$$
So the origin formulation is exactly right. Sorry for my disturbtion.


Unstable schema discovery in Unity project with Rider IDE

Version and Environment Details
Rider 2022.3.2
Plugin version: 3.4.0
Describe the bug
when first create the .graphqlconfig file and execute it to generate schema.graphql file, GraphQL panel can discover the schema correctly and everything looks good when write queries.

When close the IDE and reopen it, the previous dicovered schema will be changed to 'Default project-wide schema', and all the types in the schema file will have 'Unknown field "xxx": The parent selection or operation does not resolve to a valid schema type'

errors in .graphql files

Here is the my configuration file:

I'm not sure if it's because of the special project structure of unity project. The file structure looks like this in Rider:

actually the path is ProjectName/Assets/..., Assets folder is not the project root.
the methods I tried to solve this:

invalidate caches
file association in Rider settings
put .graphconfig and schema.graphql file under ProjectName/Assets/
put all  .graphconfig and .graphql files under ProjectName/Assets/GraphQL/

the first method doesn't work, and the last 3 ones only work temporarily: when reopen the IDE or sometimes even switch beteen unity engine and Rider or create a new .graphql file to write a new query, same errors will occur again

Hey! As a quick solution please try to click on your .graphqlconfig and choose Tools > Start Index

I'm glad that it helped! Though let's leave that issue as opened for now, perhaps we will be able to solve it somehow in the future.


Wrong error message if external method without implementation is called

The program below produce a little bit strange error message at the run time.
class C {
  external int m();
}

main() {
  C().m(); // NoSuchMethodError: No static method 'm' declared in class 'C'.
}

Why m is static in the error message here?
Tested on Dart SDK version: 3.2.0-191.0.dev (dev) (Fri Sep 22 13:04:22 2023 -0700) on "windows_x64"

This would be a compile-time error with dart compile js, but it occurs with a plain dart and dart compile exe. Let's try 'area-front-end' anyway — @johnniwinther or @chloestefantsova, please redirect it to backends if needed!

@askeksa @mkustermann @sigmundch How do dart2wasm, the VM and dart2js/dartdevc handle unregnized external methods?

We generate a call to https://github.com/dart-lang/sdk/blob/0a0bae399f1d55f77ac176b183c7f745520a2356/sdk/lib/_internal/wasm/lib/errors_patch.dart#L128-L132

@askeksa @mkustermann @sigmundch How do ... the VM ...  handle unregnized external methods?

The VM should throw a NSM error, see here

Making a non-implemented external function be a runtime error, is a holdover from Dart 1. It really should be a compile-time error today.
It's the backend compiler giving the error, not the front end, because it's the one who knows whether the implementation is there, but it still knows before runtime.

I'd like to integrate this with the Target interface so we can trigger the error reporting from the CFE, if possible.


Double clicking on full zoomed in view should reset the view

We are working on a project where we are allowing double click to zoom-in on an image. In case the image is already in full zoomed-in state & then if user double clicks on it then it should reset the view of the image.

I would like to take this up for a fix. @prc5 will you please let me know if this is an expected behavior. Have already gone through the library, will make the changes once you approve on the behavior.

+1 for this behaviour

this is now available  👍
<TransformWrapper
       options={{
         maxScale: 6,
         limitToBounds: false,
         limitToWrapper: false,
         wrapperClass: classes.myWrapperClass,
         contentClass: classes.myWrapperClass,
         centerContent: true
       }}
       doubleClick={{
         mode: 'reset'
       }}>
       <TransformComponent>
         <img src={imageUrl} className={classes.image} />
       </TransformComponent>
     </TransformWrapper>


TypeInitializationException

Hi,
our IdentityServer V3 instance was running fine, but this morning it suddenly started to rise System.TypeInitializationException for every request made to the .well-known/openid-configuration route.
Once restarted the site in IIS, the issue was gone.
Later i'll add some other details about the architecture we are using, untill then, do you have any clues about what happened ?
These are the information logged
System.TypeInitializationException
The type initializer for 'Thinktecture.IdentityServer.EntityFramework.Entities.EntitiesMap' threw an exception.
   at Thinktecture.IdentityServer.EntityFramework.Entities.EntitiesMap.ToModel(Scope s)
   at System.Linq.Enumerable.WhereSelectListIterator`2.MoveNext()
   at WriteArrayOfScopeToXml(XmlWriterDelegator , Object , XmlObjectSerializerWriteContext , CollectionDataContract )
   at System.Runtime.Serialization.CollectionDataContract.WriteXmlValue(XmlWriterDelegator xmlWriter, Object obj, XmlObjectSerializerWriteContext context)
   at System.Runtime.Serialization.XmlObjectSerializerWriteContext.SerializeAndVerifyType(DataContract dataContract, XmlWriterDelegator xmlWriter, Object obj, Boolean verifyKnownType, RuntimeTypeHandle declaredTypeHandle, Type declaredType)
   at System.Runtime.Serialization.XmlObjectSerializerWriteContext.SerializeWithXsiTypeAtTopLevel(DataContract dataContract, XmlWriterDelegator xmlWriter, Object obj, RuntimeTypeHandle originalDeclaredTypeHandle, Type graphType)
   at System.Runtime.Serialization.DataContractSerializer.InternalWriteObjectContent(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
   at System.Runtime.Serialization.DataContractSerializer.InternalWriteObject(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
   at System.Runtime.Serialization.XmlObjectSerializer.WriteObjectHandleExceptions(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
   at System.Runtime.Serialization.XmlObjectSerializer.WriteObject(XmlDictionaryWriter writer, Object graph)
   at System.ServiceModel.Dispatcher.DataContractSerializerOperationFormatter.SerializeParameterPart(XmlDictionaryWriter writer, PartInfo part, Object graph)
   at System.ServiceModel.Dispatcher.DataContractSerializerOperationFormatter.SerializeParameter(XmlDictionaryWriter writer, PartInfo part, Object graph)
   at System.ServiceModel.Dispatcher.DataContractSerializerOperationFormatter.SerializeBody(XmlDictionaryWriter writer, MessageVersion version, String action, MessageDescription messageDescription, Object returnValue, Object[] parameters, Boolean isRequest)
   at System.ServiceModel.Dispatcher.OperationFormatter.OperationFormatterMessage.OperationFormatterBodyWriter.OnWriteBodyContents(XmlDictionaryWriter writer)
   at System.ServiceModel.Channels.Message.OnWriteMessage(XmlDictionaryWriter writer)
   at System.ServiceModel.Channels.BufferedMessageWriter.WriteMessage(Message message, BufferManager bufferManager, Int32 initialOffset, Int32 maxSizeQuota)
   at System.ServiceModel.Channels.TextMessageEncoderFactory.TextMessageEncoder.WriteMessage(Message message, Int32 maxMessageSize, BufferManager bufferManager, Int32 messageOffset)
   at System.ServiceModel.Channels.HttpOutput.SerializeBufferedMessage(Message message, Boolean shouldRecycleBuffer)
   at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)
   at System.ServiceModel.Channels.HttpPipeline.EmptyHttpPipeline.SendReplyCore(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.HttpRequestContext.OnReply(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.RequestContextBase.Reply(Message message, TimeSpan timeout)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.Reply(MessageRpc& rpc)

Odd -- not a lot of info in that exception.

Do you have any updates or any more info to go on?


[Foundation for Emails] Missing Primary Button Styles

How can we reproduce this bug?
In Gmail the primary button background color doesn't render for me. If I replace the class on the <button> to secondary it always loads as expected. I looked in to the .scss files and noticed there isn't any styles for table.button.primary
Write out the HTML (or Inky code) that causes the issue.
<button href="${urlSigninToAccount}" class="primary  radius  text-center  large">Sign In To Your Account</button>
What did you expect to happen?
For the button to render with the primary color.
What happened instead?
The button didn't have a background color in Gmail
What email clients does this happen in?
Gmail and maybe others. I haven't tested it all yet.

The primary color for buttons is the default color for buttons. So there is no .primary class. If you change the primary color in your _settings.scss you'll see the change. You can also create custom CSS classes to style the buttons.


Can this repository be archived?

I'm reading this repo for the first time, since I received a security email about some old dependencies.
Is this repo still useful?

I moved it to the attic - there was no code in it, and it hasn't been touched for 2 years.


When you cant detect properly from registry.

Define the global variables if the XML is being used.
/C

Approved and merged


A way to migrate data when updating app

Is your feature request related to a problem? Please describe.
When developing our app, we use 3 environments : dev, preproduction, production. Often there is :
• a need to alter the schemas to add required fields => after push, existing data have this field set to null
• a need to add a new data schema that should be populated at first (ie app parameters) => after push the dynamoDB table is empty
It seems to be missing a feature in amplify cli to migrate the databases so we can achieve seamless push in new environments
Describe the solution you'd like
It would be great to have the ability to describe migrations of data in the amplify folder so that the migrations are executed upon push
Describe alternatives you've considered
• Using dynamoDB interface to input the data by hand => difficult if there is a lot of data
• Using a custom external script to trigger mutations with the data needed to modify or input => sometimes you want to disable mutations on this particular schema (i.e. for a list of Countries) so you cannot do this easily. This also requires more boilerplate code.
• using a custom script with aws js sdk => seems the way to go for now
Additional context
Some great things exist with other frameworks, I will only link there some I have used : for meteor, for laravel
I think version numbering is a must have for such functionality
If you have other alternatives, please comment here, I would be happy to test other solutions

Is there any comment on this from the Amplify team? Or suggested steps for migrating DB information (are Data Pipeline or Custom CSV functions our only option?)

Migrations mechanism also could help with GSI updates issues .

Not sure if this helps anyone but I created a process for running migrations via an npm run command:
` Javascript
const common = require('./common.js');
const AWS = require('aws-sdk');
const migrations = [
// ensure migratons are in date order (oldest at the top)
require('./migrations/20200201-lea-180')
];
global.fetch = require('node-fetch');
/**

This file is used to data migrations and only data migrations. Schema changes are handled by amplify.

In order to run a migration:

Add the file into the migrations folder (copy the template)

Require the reference to the BOTTOM of the migrations array above

Best practice, Make no changes to schema that are going to cause backwards compatibility issues.
e.g no deleting columns/tables

Yes, I realise this will create technical debt with rouge unused columns everywhere but Amplify is changing the schema itself
We can run clean up at a later date when we know the data that you are migrating has been changed.

NOTE: The schema only changes in Appsync not dynamoDB itself, do not expect new columns to appear.
*/
const environmentName = common.getCurrentEnv();

(async () => {
AWS.config.update({region: 'eu-west-2'});
// if running local use this
let credentials = new AWS.SharedIniFileCredentials({profile: 'PROFILENAME'});
// if CI then use env vars
AWS.config.credentials = credentials;
let dbConnection = new AWS.DynamoDB({apiVersion: '2012-08-10'});
try {
// Make sure there is a migrations table
console.log('Getting migration table');
let migrationTableName = await common.findTable(dbConnection, 'Migration-' + environmentName, null, true, true);
// If it doens't exist, create it
if (!migrationTableName) {
  console.log('Migration table not found...creating');
  migrationTableName = await createMigrationTable(dbConnection, 'Migration-' + environmentName)
  console.log('Migration created');
}

// Get all migrations that have been ran
const previousMigrationsRaw = await common.getAllItems(dbConnection, migrationTableName);
const previousMigrations = previousMigrationsRaw.map((migration) => migration.migrationName.S);
const successfulMigrations = [];
let rollBack = false;

for (const migration of migrations) {
  // Do I run the migration?
  if (previousMigrations.some((m) => m === migration.name)) {
    console.log('Already ran migration: ' + migration.name);
  } else {
    console.log('Running migration: ' + migration.name);

    // Try to run migration
    try {
      await migration.up(dbConnection, environmentName);
      successfulMigrations.unshift(migration);
      console.log('Successfully ran: ', migration.name);
    } catch (e) {
      console.error('Up Error: ', migration.name, e);
      console.error('Breaking out of migration loop');
      // Push the failed migration so we can run the down
      successfulMigrations.unshift(migration);
      rollBack = true;
      break;
    }
  }
}

// Was there an error? if so run all downs
if (rollBack) {
  console.error('Attempting to revert ' + successfulMigrations.length + ' migrations');
  for (const migration of successfulMigrations) {
    console.error('Attempting to revert ' + migration.name);
    try {
      // Need to down all
      await migration.down(dbConnection, environmentName);
    } catch (e) {
      console.error('Down Error: ', migration.name, e);
    }
  }
} else {
  // Save migration completion
  console.log('Saving migrations to server', successfulMigrations);
  for (const migration of successfulMigrations) {
    await common.putItem(dbConnection, migrationTableName, {
      'migrationName': {
        S: migration.name
      },
      'migrationDate': {
        S: new Date().toISOString()
      }
    });
  }
}

} catch (e) {
console.error(e);
}
})();
async function createMigrationTable (dbConnection, tableName) {
var params = {
AttributeDefinitions: [
{
AttributeName: 'migrationName',
AttributeType: 'S'
},
{
AttributeName: 'migrationDate',
AttributeType: 'S'
}
],
KeySchema: [
{
AttributeName: 'migrationName',
KeyType: 'HASH'
},
{
AttributeName: 'migrationDate',
KeyType: 'RANGE'
}
],
TableName: tableName,
BillingMode: 'PAY_PER_REQUEST'
};
// Call DynamoDB to create the table
await dbConnection.createTable(params).promise();
return tableName;
}
`
Not the cleanest code but now I just have a folder which contains js files that export a name and an up and a down function which talk to dynamoDB directly. as in the docs: https://docs.amazonaws.cn/en_us/amazondynamodb/latest/developerguide/GettingStarted.JavaScript.html
Note: I still need to figure out how to get it running in the pipeline but it works when I trigger in the Terminal

Really?? No comment on this? I don't understand how you're supposed to make any changes if you have an app in production, other than completely ejecting Amplify and managing your stacks et. al. completely yourself once you have live data and users in your app - which isn't a completely unreasonable idea, but I have not seen any mention of this being a purely development-stage only tool.

It's really a surprise that on amplify team member provides any useful information for this request. The feature is a MUST-HAVE feature for a data related solution.
It seems the data model evolution and data migration in amplify are completed forgotten.

I've switched to using Postgraphile w/ graphile-migrate for my backend, once you get the hang of writing your schema (playing around with graphile-starter helped a lot) it's really very nice. Forward-only migrations seem to be working well for me, and a real relational database means I can offload most of the work from the client to the server - a core premise of GraphQL is supposed to be eliminating client data processing, as it get's the data in exactly the format it wants. I still use Amplify to manage my Auth and S3, and for that purpose it works very well.

No responses yet ?

Trying.

Amazon make these amazing tools, and have devrel people producing really useful content in how to get the tools running, and then there is a clear lack of functionality like this. It makes me wonder how many serious amplify appsync sites are actually commercially in production?

Not by any means a scalable/robust migration system for a team but fwiw I have been using an AWS::CloudFormation::CustomResource with a a setupVersion and a setup lambda function.
        "Version": {
          "Ref": "setupVersion"
        },
        "ServiceToken": {
          "Ref": "function..."
        }

Then I've been making idempotent changes on version change via the lambda...works ok for dynamo/etc since you can't make substantial changes anyways but wouldn't be great for sql changes.

My approach has been the same as @cdunn. To elaborate a little, here are some more implementation details:
I have created a lambda called MigrationService. In the resources section of the template, I have the following custom resource:
"CustomMigrationService": {
      "DependsOn": [
        "AmplifyResourcesPolicy",
        ...
      ],
      "Type": "Custom::MigrationService",
      "Properties": {
        "ServiceToken": {
          "Fn::GetAtt": [
            "LambdaFunction",
            "Arn"
          ]
        },
        "TriggerVersion": 5
      }
    }

The most important thing in this custom resource is the TriggerVersion. If it is incremented, then the lambda will be executed upon deployment. So if you deployed with version 1, then made changes to your code and redeployed without incrementing the TriggerVersion, your lambda will not be executed.
Be sure to give the lambda the necessary access so it can make all the necessary migrations. I have done that by editing the AmplifyResourcesPolicy section and adding statements to the AmplifyResourcesPolicy > Properties > PolicyDocument > Statement. E.g.:
{
              "Effect": "Allow",
              "Action": [
                "cognito-idp:AddCustomAttributes",
                "cognito-idp:AdminAddUserToGroup",
                "cognito-idp:ListUsers"
              ],
              "Resource": [
                {
                  "Fn::Join": [
                    "",
                    [
                      "arn:aws:cognito-idp:",
                      {
                        "Ref": "AWS::Region"
                      },
                      ":",
                      {
                        "Ref": "AWS::AccountId"
                      },
                      ":userpool/",
                      {
                        "Ref": "authcognitoUserPoolId"
                      }
                    ]
                  ]
                }
              ]
            },

or
{
              "Effect": "Allow",
              "Action": [
                "dynamodb:Get*",
                "dynamodb:BatchGetItem",
                "dynamodb:List*",
                "dynamodb:Describe*",
                "dynamodb:Scan",
                "dynamodb:Query",
                "dynamodb:Update*",
                "dynamodb:RestoreTable*"
              ],
              "Resource": [
                {
                  "Ref": "storageddbBlogArn"
                },
                {
                  "Fn::Join": [
                    "/",
                    [
                      {
                        "Ref": "storageddbBlogArn"
                      },
                      "index/*"
                    ]
                  ]
                }
              ]
            }

Next up, the handler of the lambda needs to account for the creation of the custom resource. Here's the skeleton of my code:
exports.handler = async (event) => {
    const cfnCR = require('cfn-custom-resource');
    const physicalResourceId = "physicalResourceId-MigrationService-112233"
    const { sendSuccess, sendFailure } = cfnCR;

    if (event.RequestType === "Delete") {
        const result = await sendSuccess(physicalResourceId, {}, event);
        return result;
    }

    try {
       // your code here

        const result = await sendSuccess(physicalResourceId, {}, event);
        return result;
    } catch (err) {
        // your code here
        const result = sendFailure(err, event);
        return result;
    }
};

Probably the most important thing here is to handle the Delete event.
Lastly, I've implemented versioning so I do not rerun migration scripts. (Keeping scripts idempotent and re-runnable is always a great idea however, it could get expensive if you have a long list of migration scripts so skipping the ones that have already executed comes in handy. If you have few re-runnable scripts you can potentially skip this.)
In my case, i have 3 environments so I store the latest deployed version number in a dynamodb table. When the lambda is triggered it will pull the latest deployed version number on that environment and will then load+run the migration scripts that have higher version.
My migration scripts folder structure is:
migrationScripts
| component
| version.js
(I have separated the project into a few components that could be deployed independently but you might not need that)
It would have been nice if there was a built-in feature to help with the migration but the good news is that this approach works (given adequate access) for any AWS resource change and not only data.

@dabit3 any official statement on this? Is amplify am dev tool only? Please make it clear in the docs that amplify is not suitable for production apps. Many people spend a lot of time on this only to find out that most basic features are missing. Plus, no official statement for more than a year. This is just sad 👎

@dabit3 any official statement on this? Is amplify am dev tool only? Please make it clear in the docs that amplify is not suitable for production apps. Many people spend a lot of time on this only to find out that most basic features are missing. Plus, no official statement for more than a year. This is just sad 👎

Bumping this

Bumping this

Yeah, I've been searching everywhere for an understandable way to do this.

I would really like to understand what the Amplify team's recommendation is on this... what are best practices, etc.

@dabit3 any official statement on this? Is amplify a dev tool only? Please make it clear in the docs that amplify is not suitable for production apps. Many people spend a lot of time on this only to find out that most basic features are missing. Plus, no official statement for more than a year 👎

Totally agree with you. It's easy to set up projects from scratch.
But in long term, when there's a need to changes, we eventually are in hell.
Amplify hide very much implementation details, so it's lack of production-grade features.

Glad I ran into this early in my evaluation. It'd have been catastrophic to hit a wall like this in production.

This is also an issue for me.  One key requirement is to have rollback support.  Our dev team uses multiple independent environments and we often push other branches during code reviews, then push another branch, effectively removing previously added resources.

No response to this for so long really sucks. @josefaidt I see you've added this to your project board recently... perhaps a quick reply to at least give us some info would be nice?

Hey - wanted to drop a note in from the Amplify team. We're looking into some data / schema migration workflows right now, though because this space is really large, we won't address every single use case initially. Soon, we'll launch a mechanism to explicitly opt in to breaking changes during push. After that we'll look into more sophisticated migration workflows.
Question to the community, is this feature valuable already if we enforce to only allow data migrations if the schemas between the environments are exactly the same?
One of our core design challenges right now is to provide a smooth migration experience when it's not so obvious. For example, renamed models or fields, changed field types and nullability all within one "deployment step".

I wonder if there could be some schema markup to help with this...where you make use of temporary @was, or @isNow
Old Schema
type Dog @model {
id: ID!
name: String!
breed: String!
favoriteToy: String!
}
New Schema
type Animal @model @was('Dog'){
id: ID!
name: String!
type: String! isNow("Dog")
breed: String!
favoriteObject: String! @was("favoriteToy")
}
@isNow basically fills in the field with a value...maybe could be hooked up to a lambda, or simple logic
@was basically moves renames the object
Both of these would only work when the field didn't exist...so the migration only happens the first time it is encountered...and after all environments are migrated, you can safely remove them...

Hey - wanted to drop a note in from the Amplify team. We're looking into some data / schema migration workflows right now, though because this space is really large, we won't address every single use case initially. Soon, we'll launch a mechanism to explicitly opt in to breaking changes during push. After that we'll look into more sophisticated migration workflows.
Question to the community, is this feature valuable already if we enforce to only allow data migrations if the schemas between the environments are exactly the same?
One of our core design challenges right now is to provide a smooth migration experience when it's not so obvious. For example, renamed models or fields, changed field types and nullability all within one "deployment step".

One of my use cases is that I need to make a change to the schema that involves a breaking change to the data that is already in the schema. For instance, a field that was previously not required becomes required and we need to backfill some data into existing records in order for AppSync to not complain.
What I am looking for is the capability to execute a series of migration scripts during or after the amplify deployment, where the scripts have an 'up' and a 'down' capability in case of rollback.  The ideal solution would keep track of which scripts have been executed, execute the 'up' method during migration events, and have some way of rolling back a migration and triggering the 'down' event in the event that the deploy fails for some reason.
Ideally Amplify would provide the infrastructure and scaffolding for this and all I would need to do would be to run an amplify command to create a new migration script and then fill in the details of the up and down.

This is related to #7672
@renebrandel please keep us posted about your implementation schedule.
We are implementing some custom approach but it's a lot of effort.

@renebrandel
Any update on this? Or can someone lead me to a best practices guide on this issue? I can't find anything in the docs and I often run into issues after Schema updates (Simply creating a non nullable field which doesn't currently exist within a db table).
I'm hoping to start testing my application with live users and I'm certain migrations are necessary for that.
Am I going to have to write my own custom migration mechanism or has the team got something in the works?

Hi @Taylor-S For your particular use case, you should be able to use the @default directive in your new field. https://docs.amplify.aws/cli/graphql/data-modeling/#assign-default-values-for-fields
But migration use case are obviously much larger than just that. We're currently working on a @mapsTo directive that allows you to rename an existing field/model to a new name.

@renebrandel , Awesome! That directive will definitely help me out. Obviously I'm very new to graphql and amplify. :)
Glad to hear the team has something in the works. I'll keep an eye out for the update. Thanks for the quick reply

Hi everyone, while we haven't yet addressed all of the concerns mentioned in this thread, we are excited to announce a new @mapsTo directive to help with certain scenarios. It is available in the latest version of the CLI (7.6.14) as a developer preview. To try it out, you don't need to do anything except start using the directive in your schema.
This directive can be used to rename a GraphQL type but retain the original table and data. Usage looks like:
type Article @model @mapsTo(name: "Blog") {
  id: ID!
  title: String!
}

Where "Blog" is the original name of the "Article" type that contains data you want to retain. For more details, check out the docs PR here: https://github.com/aws-amplify/docs/pull/3890/files

That's not a solution when you need to populated

Hi everyone, while we haven't yet addressed all of the concerns mentioned in this thread, we are excited to announce a new @mapsTo directive to help with certain scenarios. It is available in the latest version of the CLI (7.6.14) as a developer preview. To try it out, you don't need to do anything except start using the directive in your schema.
This directive can be used to rename a GraphQL type but retain the original table and data. Usage looks like:
type Article @model @mapsTo(name: "Blog") {
  id: ID!
  title: String!
}

Where "Blog" is the original name of the "Article" type that contains data you want to retain. For more details, check out the docs PR here: https://github.com/aws-amplify/docs/pull/3890/files

That's not a solution when you need to populate your tables and then start working on the app.

Any updates on it?

@renebrandel, @alphonse92 - have you considered some sort of bulk import/export tool for data migrations?
I understand the difficulty in developing a mature, universal migration framework, however.....
If we could extract large swaths of data from dynamo, say into an RDBS, we could:

Extract a swath of data from Dynamo.
Process the migration.
amplify push to execute a destructive schema update.
Re-insert the data back in a large swath.

This is definitely the old school way to process a migration, but it can be used in 100% of cases.   Would surely plug the gap in Amplify's migration capabilities in a hurry.

I found this while looking for a solution to this problem and it works well.
https://github.com/technogise/dynamo-data-migrations
It is a cli for creating and managing migrations. I has up and down commands to execute migrations and rollback and it it keeps track of what has been applied and the migration order.
There are 2 caveats for this tool:

It has no concept of amplify environments. There is on log (table) of events for the whole AWS region. You can work around this by making per environment migration scripts or just update all databases at once. I can also imagine making an amplify specific fork that introduces this concept and looks at the user:Stack tags
It uses the V2 js library. You can either work with the V2 library or just ignore it and use the V3 code inside of each up and down migration function.

5 Years still no updates? Bumping this. Please have a look at this!


feat(ui/divider): add hairline divider

Checklist

[x] Fix linting errors
[x] Tests have been added / updated (or snapshots)

Change information
add hairline divider

Will the description text be affected when using a 0.5px divider

Will the description text be affected when using a 0.5px divider?

Yes. I used the new css, which no longer affects the description text. There should be no need to display text in vertical mode, so I just changed normal mode.

nice work~ thx


docker support

Hi,
thanks for this, it would be great if you can support docker image.
thanks

I don't really know what I'm doing, but let me know if the Dockerfile that I just committed works for you.

awesome, i got it working. so am accessing it with
http://localhost:8080/nasa i get the rss
do i have to do anything when rate limit hits? or will it auto change to another instance?
thanks

Glad that it works!
I'd recommend choosing multiple public instances from the list at https://github.com/zedeus/nitter/wiki/Instances. You can verify that each one is working by running a command like this:
nitter-rss-proxy -user nasa -instances https://nitter.it/

(or whatever equivalent is needed to pass those -user and -instance flags to your Docker image).
Then pass the instances that you chose as a comma-separated list when you run the proxy, e.g.
nitter-rss-proxy -instances https://nitter.it/,https://nitter.ca/,...

The proxy will cycle through the instances as it handles requests, and if an instance times out or reports an error, it'll automatically move on to the next one in the list.

i dont think i can pass -user or -instance in docker-compose. not as enviroment :(
can it be implemented in main.go getting list from https://github.com/zedeus/nitter/wiki/Instances
just a suggestion.
thanks

I don't know anything about docker-compose, but do any of the answers at https://stackoverflow.com/questions/37366857/how-to-pass-arguments-to-entrypoint-in-docker-compose-yml help?
I'd rather not make the program automatically get a list of instances for a variety of reasons (it'd add a network dependency on GitHub, the proxy would need to parse that webpage, some instances are flaky or buggy and there would probably still need to be a way to manually exclude them, etc.).

here is my docker-compose.yml
nitterproxy:
    container_name: nitterproxy
    image: nitterproxy
    ports:
      - 8080
    restart: always
    build:
      context: ./nitterproxy
    command: [nitterproxy -instances https://nitter.it/,https://nitter.ca/]

how do i test it now?
if i go to image console and run nitterproxy -instances https://nitter.it/,https://nitter.ca/
i get this error
sh: nitterproxy: not found

The Dockerfile that I committed installs the executable at /nitter-rss-proxy. Does changing the final line of your docker-compose.yml to something like this work?
  command: [ '/nitter-rss-proxy', '-addr', '<IP_ADDRESS>:8080', '-instances', 'https://nitter.it,https://nitter.ca' ]

It seems weird to me that running /nitter-rss-proxy on the console wouldn't work, but this is beyond my knowledge. The Dockerfile seems pretty trivial and works on Google Cloud Run, so hopefully someone with more knowledge about docker-compose would be able to tell you what needs to be changed in your docker-compose.yml file.

here is my docker-compose.yml
nitterproxy:
    container_name: nitterproxy
    image: nitterproxy
    ports:
      - 8080
    restart: always
    build:
      context: ./nitterproxy
    command: [nitterproxy -instances https://nitter.it/,https://nitter.ca/]

how do i test it now? if i go to image console and run nitterproxy -instances https://nitter.it/,https://nitter.ca/ i get this error sh: nitterproxy: not found

Because the Dockerfile has an ENTRYPOINT entry, the command: ... line in your docker-compose.yml is appended after the ENTRYPOINT line. (more info)
You should change the command keyword in your docker-compose.yml to entrypoint.
nitterproxy:
    container_name: nitterproxy
    image: nitterproxy
    ports:
      - 8080
    restart: always
    build:
      context: ./nitterproxy
    entrypoint: ["/nitter-rss-proxy", "-instances", "https://nitter.it/,https://nitter.ca/"]


plugin conflict

using the 1.7.0 legacy build for 1.10.2 i get a conflict with wallet drop.  somehow its stopping wallet drop from issuing currency for mob kills even with features turned off in config.  im assuming that its not actually turning off the feature of job warriors properly for wallet drop to work correctly. originally thought they would work side by side since wallet drop is able to drop the currency as items on ground at mob kill. also im on java 1.8_144 with spongeforge-1.10.2-2477-5.2.0-BETA-2698 and walletdrop-5.2.0-0.2.3.
any suggestions would be helpful.
also note that for a moment i had wallet drop  currency items dropping . after restarting the server it stopped doing this.

Send your totaleconomy.conf and jobs.conf files in gists please.

https://gist.github.com/pyscho974/ed25b5029cae8601a4d0e09a50e33ca7  is no jobs config due to the settings still seems is something blocking wallet drop from issuing currency.
tested wallet drop and it does work just not with total economy for some strange reason.

Any console errors?

I would be very confused by TE influencing mob kill rewards properly triggered...
As Erigitic mentions the server logs would be very helpful.
Please attach them to the gist.

hmm just started up my test bed again..  strange that it wont show up in chat now. have mine to put the message into chat.
not boasting another plugin but with economy lite had no issues to wallet drop..  but wasnt the desired plug in.
yes mark im generating new log files on my test bed to see if i can find something ive over looked.
no one had even noticed a money pay on the live server.

https://gist.github.com/pyscho974/87ca03bc2c762ba6cc4061f386f290f5 this is the log file.. im having issues reading threw it.. but at 15:11:04 time stamp i set balance to zero and killed several mobs. i gained currency but not exactly sure why its not outputting the action in game as currency earned. starting to think its maybe spongeforge or wallet. i do appreciate the time to look at this tho and assist me on it.  originally used older version of spongeforge when i first tested most the compatibility . even rolling back to economy lite was not working like used to which is why thinking when i updated sponge it broke things that i wasnt noticing lol

Glad to help. I'd let the developer of Wallet Drop know just in case it is something on their end.

Habe you tried using TEs "kill" jobSet node instead?

well i would have but was just way to many mobs to list and seems i wasnt able to set mobs other then vanilla to work in it. maybe user error on my part. but wallet drop somehow listed every mob in the pack automatically. and it did this based on each dimension so a config for each separately

Afaik non-vanilla mobs should work too. If you list their names/ids correctly.
The trait support currently PR'd should help you as it includes a debugging feature that tells you the string to use.

whats pr'd?  im really slow at learning new things with all this lol. i spend a few days just trying to understand what i currently got. and always learning more it seems to what already using. but space astronomy 2 pack has so many mobs its way to much to have to type out lol

Pull-Request-ed

There's a pull request by me currently waiting for approval which includes additional debugging tools?


feat: add =md to flag for list commands to allow md output

Description
This adds a new flag option on Maru to output md when listing tasks. Usage:
maru run --list=md
maru run --list-all=md

Related Issue
Fixes #N/A
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Other (security config, docs update, etc)

Checklist before merging

[x] Test, docs, adr added or updated as needed
[X] Contributor Guide Steps followed

tested locally looks good!


Fix the fully qualified class name for the command line

Fix the fully qualified class name for the command line by adding org.apache., otherwise, when trying to find storm.starter.WordCountTopology, storm will complain:
Error: Could not find or load main class storm.starter.WordCountTopology

Because what needs to be passed is
org.apache.storm.starter.WordCountTopology

I tested this on a:
Cluster type, HDI version
Storm on Linux (HDI 3.6)

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

@emres : Thanks for your contribution to the Azure documentation! The author, @Blackmist, has been notified to review your proposed change.

Thanks for catching this @emres !
This is OK to merge. #sign-off


Updates home and browse ui, adds sub-headers

This PR closes #16. This PR updates the home page and browse user interfaces. It also adds sub-headers and styles the add button.

Looks great!


Hide date

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Events all show numeric date to the left.
Expected behaviour
For users that only show 1 day of events at a time, it would be nice to hide this date and just show the events.
Possible Solutions
Add toggle to display date (just as there is for month and day).
Context / Reason
For users that only show 1 day of events at a time, it would be nice to hide this date and just show the events.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Having a 'Today' and 'Tomorrow' designation might be nice, but that may be a better case for markdowncard+template.

Looks like dateSize: 0 may be what I'm after.

Hi, could you possibly attach a screenshot of which date you are referring to, there are multiple locations that the dates are shown.


Correct module name.

As mentioned in issue #115 this is due to an oversight in pull request #112 my apologies.

Thank you!


Contract testing

Hmm sonarqube didn't detect the new code.. probably need to define a new sourceSet to scan or something


Fix query filtering of "\r" containing values in Solr

Issues:

[x] Solr: https://github.com/solariumphp/solarium/issues/1104

Thx to @thomascorthals we could fix this issue via replacing \r\n and \r with \n this is working because we are in control how the data get indexed.
For more information see: https://github.com/solariumphp/solarium/issues/1104#issuecomment-1821719852


RFC: parser should allow empty (tactic) lists

After you write by or ·  (focus on 1 goal), you often look at the goal state for a while before deciding what tactic to apply next. It is annoying that these two pieces of syntax are illegal by themselves, since they require a nonempty sequence of tactics to follow. This has 2 negative consequences:

A distracting parser error is shown
Potential other errors are not shown

Suggestion: can the parser allow by or ·  (focus) followed by an empty sequence of tactics? The elaborator can still throw an warning/error of course.
The following MWE shows some examples of parser errors even though there is a "more important" error to show in both cases.
example (p : Prop) : p ∧ 3 := by

example (p q : Prop) : p ∧ q := by
  rw [doesntExist]
  constructor
  ·
  done

@digama0 also suggested that the parser allows an empty list in the following cases:

def foo : type where
mutual end
variable
universe
export Foo ()
open Foo ()
open Foo hiding
open Foo renaming
open
attribute [attr]
do {}
do
if cond then <-- this one should probably be a warning, unindented code after if cond then is almost certainly a bug

Related RFC: #3556
Community Feedback
The Zulip thread shows a lot of support.
Impact
Add :+1: to issues you consider important. If others benefit from the changes in this proposal being added, please ask them to add :+1: to it.

Potential problematic interaction: https://github.com/leanprover/lean4/pull/3215#issuecomment-1920888466


Running wcfclient in a docker and the server outside the sample doesn't works

Hello,
I need to run a wcf server not in a docker and the wcf client in a docker.
I check this configuration with your example:

The server runs on my PC as console
Run the client in a container, set the env HOST to the ip address of my PC,
I have this exception: EndpointNotFoundException.
Both in a container is OK
Can you help to me to manage this configuration?
Thanks

Hello,
I use Docker Desktop and probably it's this the reason of the problem described above.
From docker doc:
https://docs.docker.com/docker-for-windows/networking/
.......
_Use cases and workarounds
There are two scenarios that the above limitations affect:
I WANT TO CONNECT FROM A CONTAINER TO A SERVICE ON THE HOST
The host has a changing IP address (or none if you have no network access). From 18.03 onwards our recommendation is to connect to the special DNS name host.docker.internal, which resolves to the internal IP address used by the host. This is for development purpose and will not work in a production environment outside of Docker Desktop for Windows.
The gateway is also reachable as gateway.docker.internal._
.....
I understood that there some limitations on Docker Desktop to connect from container to out,
but it's not clear to me the workaround suggested.

@domenicocanavero This is an issue that is specific to the windowsservercore OS base image that the wcf image is based on. Please post this to the windows containers forum.


Built-in auto docs localization and redirection

Summary

@valaria247
I haven't seen any open source documentation has this feature built-in except people use translate extensions on browsers.
(that's rare or annoying otherwise does not care to translate as long as able to understand the main idea of page)
Also quite difficult task for non-profit projects and startup owners to make available local versions for their sites and docs.
However this feature must retain static site deployment capability and configurable to exclude languages that already translated manually. There're various translate services offer free APIs and other facilities etc.
Automatically detect visitor IP or country using third party service and redirect to local version of site too great if possible to implement somehow.
I aware that is difficult task due static deployment also i have seen some developers succesful efforts to bring various things to static through many ways so if you guys invent something then it'll be great for everyone and others definitely get benefit from that.

@mtlynch
Thanks for filing this issue, @valaria247!
This repo is for the documentation website. Feature requests for Gridsome go to:
https://github.com/gridsome/gridsome/issues
This is also a very largely-scoped feature request, which makes it unlikely to be implemented. Geolocating visitors by IP and then using public translation APIs to translate text to different languages is pretty outside of Gridsome's scope.
I'm not an official Gridsome representative, just giving my personal opinion. You're welcome to re-file this on the core Gridsome repo if you'd like.

Above @valaria247 include two different feature requests

Geolocating visitors by IP or country and redirect to local site.
This feature belong to both manual translated languages and machine translations because when user visit to site then it display in english by default and no server side redirection similar gmail etc then user needs to find the annoying button somewhere and pick native language from long drop down list.

Convert pages to different languages that untranslated manually.
This helps for newly launched sites (until translate manually), small businesses or unpopular projects to display local versions of their blogs, docs, home page etc easily.

Motivation
Why are we doing this? What is the expected outcome?
To make available localization for every single site in world wide web and provide same value for all languages as well.
Static sites are the first stage or otherwise cheapest deployment method that even use by most individuals or newbies personal sites and big companies homepages.
Currently 6800+ repositories depend on gridsome and many other get benefits from that. It's fine even if you take year or more to implement that slowly.

https://github.com/gridsome/gridsome/issues/23

One of cool feature request i have ever seen to bring static deployment to next level. Love it. :)
We everyone know that is quite difficult but try it somehow.


Liquid haskell runtime error when built from nixpkgs but not hackage

Describe the bug

This bug has originally been reported by @octalsrc in the liquid haskell repo https://github.com/ucsd-progsys/liquidhaskell/issues/2428 together with a minimal reproducer https://github.com/octalsrc/liquid-haskell-test

Liquid Haskell works when cabal downloads and builds its
dependencies directly from Hackage, but fails when the dependencies
are provided through nixpkgs.
The cabal.project.freeze file in this repository was generated based
on the failing-environment.nix shell environment:
$ nix-shell --pure failing-environment.nix
(nix-shell) $ cabal freeze

Despite both the Hackage-based and nixpkgs-based environments adhering
to that same freeze file, the Hackage environment works and the
nixpkgs environment fails.
Both environments use the same GHC, cabal, and Z3, determined by the nixpkgs snapshot used in ./pkgs.nix.
Steps To Reproduce
Working version (Hackage)
The example file src/MyLib.hs can be successfully checked using the
following procedure:
$ nix-shell --pure working-environment.nix
(nix-shell) $ cabal clean && cabal build
...
**** LIQUID: SAFE (1 constraints checked) **************************************

In this environment, nixpkgs provides GHC 9.10.1, cabal, and Z3.
Then cabal builds the Haskell libraries, specified by
cabal.project.freeze, by fetching their sources from Hackage.
Failing version (nixpkgs)
The example file src/MyLib.hs fails to check using the following procedure:
$ nix-shell --pure failing-environment.nix
(nix-shell) $ cabal clean && cabal build
...
**** LIQUID: ERROR *************************************************************
<no location info>: error:
    :1:1-1:1: Error
  crash: SMTLIB2 respSat = Error "line 3 column 11916: Sort mismatch at argument #1 for function (declare-fun not (Bool) Bool) supplied sort is Int"

This environment uses the same GHC, cabal, and Z3 as the working environment, but the liquidhaskell library and its dependencies are built as Nix packages using the Nix build tool.
The Nix build tool downloads some of the libraries pre-built from
cache.nixos.org and builds the others by invoking cabal.  The
library sources come initially from Hackage, but some are modified by
rules in this big file from nixpkgs.  Ultimately, their versions
match those of the cabal.project.freeze file (which was generated
based on them).
Despite the fact that both environments satisfy cabal.project.freeze---both consist of Hackage-sourced libraries with matching versions---they have different behavior.  In the first, the MyLib.hs example typechecks, and in the second, it does not.
Notify maintainers
@maralorn @sternenseemann @cdepillabout

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

Thanks for opening this; I've just been using the direct-from-Hackage installation method in the meantime, and haven't had time to look into the possible causes.


please follow redirect

Hi, I'd like to download electron from a location on our corporate sonatype nexus.
The uri returned by nexus gives a redirect (302). Redirect is not followed. package is therefore not downloaded even if it exists.
I get the following error:
npm i<EMAIL_ADDRESS>--save-dev --reg
http://internalrepository.addr.corp:8081/nexus/content/groups/build.milestones.npm/
(node:11289) fs: re-evaluating native module sources is not supported.
If you are using the graceful-fs module, please update it to a more
recent version.

><EMAIL_ADDRESS>postinstall /home/me/wing/node_modules/electron
> node install.js

/home/me/wing/node_modules/electron/install.js:46
  throw err
  ^

Error: Failed to find Electron v1.4.15 for linux-x64 at
http://internalrepository.addr.corp:8081/nexus/service/local/repositories/3rd-party.releases.manual-uploads.hosted/content/io/atom/electron/download/electron/electron/1.4.15/electron-1.4.15-linux-x64.zip
    at Request.<anonymous>
(/home/I301937/wing/node_modules/nugget/index.js:169:61)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:188:7)
    at Request.onRequestResponse
(/home/I301937/wing/node_modules/request/request.js:1074:10)
    at emitOne (events.js:96:13)
    at ClientRequest.emit (events.js:188:7)
    at HTTPParser.parserOnIncomingClient [as onIncoming]
(_http_client.js:474:21)
    at HTTPParser.parserOnHeadersComplete (_http_common.js:99:23)
    at Socket.socketOnData (_http_client.js:363:20)
    at emitOne (events.js:96:13)

However _http://internalrepository.addr.corp:8081/nexus/service/local/repositories/3rd-party.releases.manual-uploads.hosted/content/io/atom/electron/download/electron/electron/1.4.15/electron-1.4.15-linux-x64.zip_ does exist.
FYI: I use the following env variables to specify a different electron uri:
ELECTRON_CUSTOM_FILENAME="electron-1.4.15-linux-x64.zip"
ELECTRON_MIRROR="http://internalrepository.addr.corp:8081/nexus/service/local/repositories/3rd-party.releases.manual-uploads.hosted/content/io/atom/electron/download/electron/electron/1.4.15"

next is changing how downloading works and now uses got which follows redirects


Add govuk-nav-prototype application

We need to access the draft-content-store in our prototype to display
draft taxonomies without publishing the taxonomy live (doing so could break user journeys and we don't want that).
Currently we can't access the draft-content-store from the "outside" (e.g: heroku) so we decided to add the prototype alongside other apps.
Trello: https://trello.com/c/9leIHFaX/230-deploy-prototype-to-govuk-infrastructure
Paired with @alecgibson

@surminus I've addressed your comments - could you please re-review?

If you want to be able to deploy the application through Jenkins you'll need to add your application to yet another list here.
This will also create stuff in CI which will allow you to run tests in Jenkins and deploy automatically to Integration on master assuming you have a Jenkinsfile in the repo.

@surminus thanks - I've added that  too.


#reports/logbrowser/search . Fix info popup: "deletion of 'blank' complete" in modal popup

attach proper name field to delete

popup.

committed in saved-search-dropdown-api-logs
dc7f8c8c975b4e269297704a4154268392afd449

out for pull request with #281


Changes to improver-weighted-blending CLI to use new weights functionality

Addresses #658
Description: this change includes the following:

Changes to improver-weighted-blending CLI arguments and functionality, including wrapper for weights creation plugins
Changes to CLI tests (removed some, added one for "dict" option)
Updates to unify_forecast_reference_time (also moved) and new rationalise_blend_time_coordinates function
Migration of metadata updates to the improver.blending.weighted_blending.cube_metadata function, and added new unit tests
Updates to ChooseWeightsLinear to output weights with the required dimensionality from a dictionary
Updates to WeightedBlendAcrossWholeDimension function to throw an error if blending over a scalar coordinate, plus updated unit test
Moved constant dictionary to improver.constants

Testing:

[x] Ran tests and they passed OK
[x] Added new tests for the new feature(s)

I'm not sure we have a bats test for the case where only one cube is passed in. We should probably have one as the code to handle this is in the CLI.


Support for the yeelight w1 Bulb

Feature request
Support for the w1 Bulb from Yeelight

What problem does this feature solve?
The W1 Bulb ist a cheap rgbw spotlight bulb (GU10) from Yeelight. I bought the bulb to throw light at my ceiling at intense moments (lightning/explosions)
But the Bulb is not yet supportet by the yeelight wizard. Also, after adding the bulb manualy, has a bug that if the bulb is disconnected, she stays in music mode, which HyperHDR dosn't handle correctly.
What does the proposed API look like?
How should this be implemented in your opinion?
By adding the light to the wizard.
Her the logfiles:
2024-01-24T18:13:40.122Z [WEBSOCKET] (HyperAPI.cpp:1133) response: [{"devices":[{"cache-control":"max-age=3600","domain":"lan","hostname":"yeelink-light-colorc_miapABBB","id":"yeelight://<IP_ADDRESS>:55443","ip":"<IP_ADDRESS>","location":"yeelight://<IP_ADDRESS>:55443","other":{"bright":"100","color_mode":"2","ct":"4000","date":"","ext":"","fw_ver":"16","hue":"200","id":"0x000000001b4083a7","model":"colorc","name":"","power":"off","rgb":"14414847","sat":"14","support":"get_prop set_default set_power toggle set_bright set_scene cron_add cron_get cron_del start_cf stop_cf set_ct_abx adjust_ct set_name set_adjust adjust_bright adjust_color set_rgb set_hsv set_music udp_sess_new udp_sess_keep_alive udp_chroma_sess_new"},"port":55443,"server":"POSIX UPnP/1.0 YGLC/1","st":"","usn":""}],"ledDeviceType":"yeelight"}]
And the Logs from the error:
024-01-24T18:54:21.747Z [LEDDEVICE4_YEELIGHT] (LedDeviceYeelight.cpp:959) 2|  <IP_ADDRESS>| writeCommand()      : {"id":3,"method":"set_music","params":[1,"<IP_ADDRESS>",35667]}
2024-01-24T18:54:21.747Z [LEDDEVICE4_YEELIGHT] (LedDeviceYeelight.cpp:959) 1|  <IP_ADDRESS>| writeCommand():     : Wait 1000ms, elapsedTime: 1ms < quotaTime: 1000ms
2024-01-24T18:54:22.748Z [LEDDEVICE4_YEELIGHT] Yeelight device '<IP_ADDRESS>' signals error: '(-5001) invalid params'
2024-01-24T18:54:23.248Z [LEDDEVICE4_YEELIGHT] (LedDeviceYeelight.cpp:959) 2|  <IP_ADDRESS>| setMusicMode() rc   : 0, isInMusicMode[0]
2024-01-24T18:54:23.249Z [LEDDEVICE4_YEELIGHT] (LedDevice.cpp:354) Stopping refresh timer
2024-01-24T18:54:23.249Z [LEDDEVICE4_YEELIGHT] Device 'yeelight' is disabled due to an error: 'All Yeelights in error - stopping device!'
Are you willing to work on this yourself?
I am not good enough to write code, but it seems to be the same issue like this one:
https://github.com/hyperion-project/hyperion.ng/issues/1372
Thank you for your work, and time to look at my "problem"

Okay, after tinkering for a while, I was able to implement the changes in a fork, tested them, and created a pull request

OK, thank you. I will take a look later.

Sorry to revive this, but is the W1 currently supported in the release version?

It should work in v20. I merged @ratawhisk changes and added auto-resume feature.


Haste-cabal leaves a file in source directory

Haste-cabal (With no extra flags passed to hastec or gcc) leaves a Main.js file in my source directory. Since this is build artifact, I would expect this to be generated in the dist/build/app.js directory.

I looked into the verbose output generated by haste-cabal and it appears that with the -no-link option set, an "executable" is still generated by hastec. This then ends up in the source directory since the -o flag to place it in the target directory is not passed to the -no-link command.


typo?

I run  help mr.makeSincPulse and got the following discription:
 makeSincPulse Create a slice selective since pulse.

Is since or sinc ? Thanks

also
 help mr.makeAdc
 makeAdc Create a ADC readout event.

should Create an ADC readout event.?


i need your help!!!

2016-03-14 22:53:57.387 哈哈哈[8097:472586] +[BundleInjection load] <IP_ADDRESS> (see project's main.(m|mm)
2016-03-14 22:53:57.390 哈哈哈[8097:472699] Injection attempting connection to: <IP_ADDRESS>:31442
2016-03-14 22:53:57.391 哈哈哈[8097:472699] Connected to "Injection" plugin, ready to load x86_64 code.
objc[8097]: Class ViewController is implemented in both /Users/lidongxu/Library/Developer/CoreSimulator/Devices/BCDBDD48-277A-4176-A7AF-897407D65AE6/data/Containers/Bundle/Application/53D0710E-5E75-4E0C-8CA6-019AB9DB6C9F/哈哈哈.app/哈哈哈 and /Users/lidongxu/Desktop/哈哈哈/iOSInjectionProject/build/Debug-iphonesimulator/InjectionBundle2.bundle/InjectionBundle. One of the two will be used. Which one is undefined.
14 injections performed so far.
2016-03-14 22:54:05.046 哈哈哈[8097:472586] Ignore any warning, Swizzled ViewController 0x10bdd4348 -> 0x1019c8ad8

You can ignore this warning. Are things injecting OK?

i have same error

how is it not working?

Is this the same as https://github.com/johnno1962/injectionforxcode/issues/93

@johnno1962  it's work my code in viewdidload not work,when i change method it's work

@dimohamdy Excuse  can you copy your method?

@johnno1962  ok  yes #93 is helped me, thank you very much

Cool :+1:


[clarification]: Clarification on Handling Embedded Types in Metamodel Generation

Specification
https://github.com/jakartaee/data/blob/main/spec/src/main/asciidoc/repository.asciidoc#type-safe-access-to-entity-attributes
I need clarification on ...
Hello,
I've been exploring the metamodel specifications and have encountered a scenario requiring further clarification regarding handling embedded types during generation. Specifically, I am concerned about the disambiguation mechanism (if any) for embedded types used across different entities.
To illustrate, consider the following Java classes:
@Entity
public class Person {
    @Id
    private String id;
    @Column
    private String name;
    @Column
    private Address address; // Embedded Address
}

@Entity
public class Order {
    @Id
    private UUID id;
    @Column
    private String name;
    @Column
    private Address delivery; // Another instance of Embedded Address
}

@Embedded
public class Address {
    private String city;
}

In the example above, both Person and Order entities contain an embedded Address type. My question revolves around how the metamodel generation process distinguishes between these two instances of the Address class. Is there a specific mechanism to handle such cases of embedded types to avoid ambiguity? What best practices should be followed to ensure that the metamodel remains clear and consistent when dealing with embedded types across multiple entities?
Additional information
No response

Not sure I see where ambiguity could arise. What are you thinking of here?

Given the same entities of the previous sample:
How do you generate this metadata class?
Mainly because:
var name = _Person.address.city.name():// it must generate "address.city"
var name2 = _Order.delivery.city.name();// it must generate "delivery.city"

I mean, if it were a constant, it wouldn't get the proper path:
var name = _Person.Address.city.name():// it must generate "address.city"
var name2 = _Order.Address.city.name();// it must generate "delivery.city"

My point is that our spec covers only the basic attributes, but what happens if it is not a basic attribute?

This is also covered in the spec by this bullet point:

• The name of the field, ignoring case, must match the name of an entity attribute, with the _ character in the field name delimiting the attribute names of hierarchical structures or relationships, such as embedded classes.

[Note that it's a little bit hard to find that, since it's in section <IP_ADDRESS>, but the natural place to look for it is section <IP_ADDRESS>. But it's there.]

@otaviojava yes, I believe so, best check with @njr-11.

In this case, there is an issue, right?
It should be:
public static volatile Attribute<Person> name;

Yes, that's a bug in the documentation. That line of the example is incorrectly leaving out <Person>.

In this case, there is an issue, right?
It should be:
public static volatile Attribute<Person> name;

Yes, that's a bug in the documentation. That line of the example is incorrectly leaving out <Person>.

Ok, I will create a PR to fix it.


Upgrade to fp-ts 2.0

It upgrades fp-ts to 2.0. Related to #8.
I defined a logger with an interface
interface Logger<M, A> {
  (a: A): HKT<M, void>
}

The problem is that HKT<M, void> is a "phantom" type and any Logger implementation returns a Kind<M, void> instead, resulting in a type error.
My solution is a logger "constructor" that "attaches" (virtually) _URI and and _A to a simple Kind<M, void> object.
const getLogger = <M extends URIS, A>(l: (a: A) => Kind<M, void>) => l as (a: A) => Kind<M, void> & { _URI: M, _A: void }

It is the first time I play with fp-ts HKTs, so I do not know if there is a better way. What do you think, @gcanti?
TODO

[ ] bump version
[ ] update README

@mstn sorry for being so late, there's a draft in the 0.3.0 branch

@gcanti what's blocking you from releasing 0.3.0 ? I'm extremely bad at higher order typing stuff but am an old hand at javascript w/ some scala experience if there's a way I can reasonably help.

(loving fp-ts by the way, it's making me super nostalgic for scalaz - in a good way!)

what's blocking you from releasing 0.3.0 ?

@jfhbrook well nothing, my draft is 22 hours old though, and it's quite different from @mstn 's solution.
@mstn basically I used the same technique used in OptionT, EitherT, ReaderT, etc... so index.ts works like a LoggerT and LoggerIO is a logger specialized to IO computations

Oh wow, didn't even notice the timestamps - just thought you coincidentally replied to an issue around the same time I was digging into it. Stoked to see you're on it! And yeah, if you need a test drive or anything I'm in general trying to hack on typescript on weekends, just lmk,.

@gcanti thanks, Your solution looks better than mine :) Feel free to close this pr if you feel like it

Closing in favor of https://github.com/gcanti/logging-ts/pull/17
@mstn thanks for reviewing


Fix relative path in services-local.yaml

Not sure if I missed something in the setup, but I followed this blogpost and running docker-compose -f services-local.yml build failed since those build commands points to projects two levels up, when they're actually located just one level up.

Hi, this is correct, since you run docker-compose from Pacco/compose directory, meaning that you need to go 2 levels up.


Adding .sub_labels

Fixes dobtco/screendoor-v2#1228

This looks great in the screenshots you've provided, but without dvl-core it looks a little screwy. Remember that formrenderer-base does not depend on dvl-core, and even though there are barely any visual styles in this repo, the layout should still render properly. (This is important for embeds.)

Check out the updated version, lmk if you have questions. If you haven't been already, you can preview by opening examples/index.html.

Made some CSS fixes, please review.

Am I crazy or did my previous comment disappear? here's what it was:
===
Are these CSS tweaks for formrenderer, or Screendoor?

You'll notice that for better or worse, formrenderer uses px values in its CSS. I'd like to either stick with this, or rework the entire file to use rem or em units.

There is a layout error:

I think this is OK in this instance. All labels are in relative units (line-height: 1.5), so .label_sub should as well.

.fr_item_spacer has a padding equal to the height of the label, and a line-height equal to the heights of the inputs, which are also set in relative units:

Fixed.

Cool, that last change wasn't compiled FYI. (You can also run grunt watch to watch your files and compile when they're changed.)
And there is still this issue:

Alright, fixed and rebased.


Fix SR_Triangles and SR_Triangles_Object_Space shader warnings

https://github.com/microsoft/MixedRealityToolkit-Unity/issues/6609
The original change that added these shaders had a few warnings:
https://github.com/keveleigh/HoloToolkit-Unity/commit/6fa80b156b0c6138efd64d82c585f1e742812016#diff-424c2d8798826167e9e8bbc3c1a6dd70
In particular, there was some code that added while loop that would always end up running once (i.e. it would be equivalent to just not having the loop). This gives a warning in Unity, and the MRTK should be warning-free. This work just unrolls the loop manually (i.e. recognizing that it is only ever run once, just getting rid of the loop)

/azp run


fix shields.io badges for sub-components

Currently the shields.io badges on the sub-component demo pages are broken. In this PR I've added the "parent-name" property for each demo page so the badges are pulled correctly.
I also noticed a weird description in "px-map-marker-direction-demo" but I don't see that one in the dropdown so maybe it's pre-release? We can talk offline.

@randyaskin yep, that description was a placeholder -- the component wasn't ready to release yet, but we decided to keep the demo page in there for when it is. Will be sure to update the description too. Thanks!

@talimarcus can you review/merge if its ready? thanks.

looks good


Linux version

What's the Problem?
Whenever I'm on Linux I really miss having "Files" as my Files-Browser. I haven't found a replacement for it that looks just as good and with all of its functionality right out of the box (not even Nautilus + Extensions + Themes).
Would it be too much? To ask for a Linux version?
Solution/Idea
Making 'Files' compatible with Linux would be awesome!
Being able to download a '.flatpak' or '.deb' of it or simply compile it from the github source like many other projects do.
Alternatives
If you guys have any suggestions on how to replicate the 'Files' experience on Linux I'm all ears.
Priorities
Definitely a 'Could'. It would make me very happy to be able to use the same file browser on both operating systems.
Files Version
Always the latest whenever I'm on Windows.
Windows Version
No response
Comments
I'm only asking this because I got enamored with your project! I like it a lot. ; )
Thank you for your time and forgive me in advance if what I'm asking for is too stupid.

I like this file manager a lot.
However, Linux has a ton of file managers already. So Linux support would be a waste of developer time (in my opinion). The most similar file manager to this one would probably be the Deepin file manager. You might wanna give that one a try.


Remove extraneous files in NextCloud

Remove extraneous files.  The original commit added the .yaml files, but did not remove the .yml files.  No differences between the two, so removed the .yml
Thank you for wanting to submit a Pull Request to the Civo Kubernetes Marketplace repository!
If your pull request concerns an existing Marketplace application, please make sure you have:

[X] Notified the Maintainer of the application in this pull request so that they are aware of your proposal. - Will email maintainer after PR submitted
[X] Outlined the changes you are proposing, and the reasons these are required (e.g. stability, compatibility with new versions of Kubernetes implementations, etc).
[X] Tested that the application works with the proposed updates applied (including a screenshot) - No actual yaml changes in app.

lgtm


Spelling and grammar revisions in documentation (and some code)

I've corrected a large number of spelling errors and grammatical errors
within the documentation and within some of the codebase (i.e. comments
and in option descriptions for CMake and Boost.ProgramOptions)
Some letter transpositions, some misspelled words, some duplicated
words, some grammatically-incorrect phrasing (verb tenses and some
split-infinitives).
The change is not 100% comprehensive, but I believe that the
documentation reads somewhat better now than previously.

Thanks Michael! LGTM.


animation helpers redux

[no promises on this, just tracking possible solutions]
glamor used to have a keyed function that would let you define rules that would be replaced when it was redefined on the same key. this made it possible to 'reclaim' rules that weren't being 'used', with the onus on the developer to manage these keys. It was meant to be a helper for people wanting to use css for animations (not just @keyframes). however, it crippled glamor's internal design, and made it hard to optimize for the larger set of use cases.
That said, there is a small set of use cases  where it useful (eg - aphrodite/#141), so maybe we can make a separate module that does just this?

no-op


WIP: action implementation

This is a WIP implementation of the actions listed here:
https://build.fhir.org/ig/HL7/fhir-medmorph/ValueSet-us-ph-plandefinition-action.html
There are quite a few things that need some work or are up in the air about implementation.  Lots of comments throughout the code as well.
One thing I'll note here is that I realized extract-research-data could be filtered down through the FHIR query, rather than filtered down through the client code, a bit late and implemented it strangely.  I will likely go back and switch it up to make a fhirpath query, granted that's even possible.
Other things that aren't exactly clear:
check-trigger-codes: what exactly is being triggered?
checkParticipantRegistration: the planDef can define multiple conditions (per action!), and there are multiple participants. If this is really supposed to be checkReportability, then will the same thing apply but without the check between participants?
validateReport: each action supports a profile parameter, so we could potentially validate the report based on that.  There are multiple outputs allowed, each with multiple profiles allowed, so are we validating the entire bundle across all the profiles?  We could do it on a resourceType basis by making multiple outputs and binding them each to a different resourceType.  This is how I tentatively implemented it, by cycling through all the outputs and checking the profile.
Technically profile can be an array, but I'm not sure how that would work.
encryptReport: I wasn't sure what we wanted for encryption.  Base64 encoding it and tossing it into a binary resource is simple enough.  Should we introduce a library for some type of encryption?
extractResearchData:  Like I mentioned, I'll probably go back and switch it to make a more complicated FHIR query, rather than do the filtering ourselves inside the client.

Re: updating the wiki to reflect what's in context, let's do that once we have a relatively stable set of things we want to include

One piece that is missing here is the "Extensibility" component.  https://github.com/mcode/medmorph-backend/wiki/Reporting-Workflow#extensibility
There are a couple ways to do this, and tbh we may wind up switching things around over time, but basically we need a way for content IGs to specify additional codes or override the implementation of existing codes.
I think the easiest way is to instead of having all these functions be at the top-level, have them be properties of an object, ex
function checkTriggerCodes(context) {
  ....
}

becomes -->
const baseIgActions = {
  "check-trigger-codes": context => { ... },

  "do-the-other-thing": ...
}

That way content IGs can "extend" that in one line, and if we need to make it more complicated like an ES6 class we can do that later.


The Iconography  link in the README is wrong

Describe the bug
The Iconography link is wrong.
What is the expected behavior?
The  Iconography link must display the  Iconography page.
What are the steps to reproduce?

Go to the README.md: https://github.com/pxblue/icons
Click on Iconography link

Screenshots or links to minimum reproduction example
https://brightlayer-ui.github.io/style/iconography

The issue with this link: https://github.com/brightlayer-ui/icons/blob/master/design/README.md
Please read the instructions in the Design  folder before creating or submitting new icons.

@mberthouzoz We are currently in the process of a branding overhaul which will cause some temporary linking issues. We will have this fixed shortly, but in the meantime, you can access the files you are looking for by replacing brightlayer-ui with pxblue in the url.

This issue can be closed in the coming week, after the migration is complete.

Closing this issue, after migration links are working fine.


cudatext: 1.165.2 -> 1.166.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for cudatext is: "Cross-platform code editor"
meta.homepage for cudatext is: "https://cudatext.github.io/"
meta.changelog for cudatext is: "https://cudatext.github.io/history.txt"
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.166.0 with grep in /nix/store/833himzcj6gy06vy80gc83rrr6nlj24k-cudatext-1.166.0
found 1.166.0 in filename of file in /nix/store/833himzcj6gy06vy80gc83rrr6nlj24k-cudatext-1.166.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

3 x86_64-linux rebuild(s)
0 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
cudatext
cudatext-gtk
cudatext-qt

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/833himzcj6gy06vy80gc83rrr6nlj24k-cudatext-1.166.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cudatext https://github.com/r-ryantm/nixpkgs/archive/3eb0359cc67152f016b81f1be714a74f37c2b638.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/833himzcj6gy06vy80gc83rrr6nlj24k-cudatext-1.166.0
ls -la /nix/store/833himzcj6gy06vy80gc83rrr6nlj24k-cudatext-1.166.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

cudatext
cudatext-gtk

Maintainer pings
cc @sikmir for testing.

Replaced with #177734


Bad practice(?)

Detecting the rootlessness of the jailbreak at runtime should be avoided, instead the latest theos and rootless.h should be used.
The only point of this would be to support Xina, and for that the better solution is to just use rootful paths as it correctly binpatches most of them. More obscure paths still need to be redirected manually, but 99% of tweaks do not use these.

Hi opa, yes I am aware of the new rootless macros.
I agree that tweaks being rootless at compile-time rather than runtime is best practice - performance and design wise, however I do require this for the time being for compatibility reasons. Even though I chose not to provide support for Xina, I still consider it a valid userbase to at least try and have Shadow functional without breaking other platforms. Unfortunately, even with the binpatching there have been random (inconsistent) issues with Shadow before I implemented runtime rootless. Shadow does primarily deal with file paths, so I suppose it may be more sensitive to the binpatching.
I do believe the detection method used here should be (for the most part) solid and reliable, without causing any issues for now.

I have updated the macros with a xina support flag, not upstreamed yet but I will make a PR to theos soon
https://github.com/opa334/headers/blob/master/rootless.h

So the main issue I have with that and the original rootless.h is that it queries the filesystem - and that is slow. RootBridge does not rely on any file system checks and even stores the rootless result in memory through its object..


node steam tradebot not accepting offers

Errors help me thank you

offers.acceptOffer({tradeOfferId: offer.tradeofferid});
console.log('Accepted trade offer #'+offer.tradeofferid+' by '+name+' ('+offer.steamid_other+')');

Lol, that's a first one.
When will people stop randomly downloading software expecting to double click on it and hoping for easy money...

Thanks for your help FroxenHaxor

node.js platform
mysql error
leaked bot code

Ready to be closed @BlueRaja.

:+1:

This is so funny ... anyway to fix that error make sure the database tables contains data LOL.

the database is all well

Im 100% sure it isnt cause i haf samw problem. Still bot and site are broken dont even mess with them. Just build your own one.

For three days now I try to somehow correct the error and add to the already really know

I know I've been guilty of this myself but per the rules the only person who should have replied here is BlueRaja to close this. If it's not a bug report just ignore it and let someone close it.
Besides, it's not like someone who doesn't bother to try and learn c# before starting a project like this, nor read the rules before posting is going to read a comment that doesn't give a super easy solution. Someone ban neoxdany so we can all move on and await an actual bug report.

It's not even that this isn't a bug report, it's not even for this project.  He's using Node-steambot, which isn't even C#.

Apologies and thanks
LOCK please


Is it normal? Downloading from kick.

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm asking a question and not reporting a bug or requesting a feature
[X] I've looked through the README
[X] I've verified that I'm running yt-dlp version 2023.07.06 (update instructions) or later (specify commit)
[X] I've searched known issues and the bugtracker for similar questions including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Please make sure the question is worded well enough to be understood
https://drive.google.com/file/d/1VSy3zjUBosUdWeHDK8HbfsSGo4tFcnQv/view?usp=sharing
Seems like it freezing on every segment.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
/

And overall download is very slow.

It's OK if you need to share a video to demonstrate the issue but then ALSO share a verbose log as text. There wasn't even a URL I could copy/paste to reproduce this
However, I did grab an m3u8 link from kick and try to reproduce this, and I couldn't. My download speed was about as fast as I'd expect for HLS.
Without more information it's impossible to diagnose what's causing your slow speed. You could try adding -4 to your command to force ipv4. You could try adding -N 8 to your command to download 8 fragments concurrently. Whatever you do, if you want more help, then share a verbose log


Prepare to switch to Redis on PaaS

https://www.pivotaltracker.com/story/show/181796569
This adds similar code to ^1. Since this app didn't
previously load CloudFoundry config - and the config
code was also very different to other apps - there are
some initial commits to lay a foundation first.
The config module is still different to other repos due
to the heavy use of NOTIFY_ENVIRONMENT to avoid
duplication. I think it would be too subjective to change
the approach in this PR - leaving as-is for now.

Closing due to a major oversight: this app doesn't use Redis 😝


Use #9D550F orange for selection

http://www.color-hex.com/color/9d550f
It's nice to see what I'm selecting :smile:

Thanks!


Rename gem verify to gem verify_signatures

Closes #35, see issue for more context.
Renames gem verify the_gem to gem verify_signatures the_gem.  Please note that gem verify still works, since the gem client generally accepts command substrings as long as they are unambiguous.
Renames gem install --[no-]verify the_gem to gem install --[no-]verify-signatures.
🎩

Replaced by #51


feat: Limit Python version to less than 3.9

@l0b0 , I am still on Python 3.6.9  with my ubuntu 18.04. Isn't this PR going to cause problems to me ? I am planning to upgrade my machine at the end of this year.

@l0b0 , I am still on Python 3.6.9 with my ubuntu 18.04. Isn't this PR going to cause problems to me ? I am planning to upgrade my machine at the end of this year.

No, it doesn't force you to use a recent version - it just means Poetry will refuse to install dependencies with Python <3.6 or >=3.9. And if you use pyenv it'll use 3.8.6 for just this repo, which is handy.


Orbit is alive!!!! Full revert back to when Orbit worked

In Foundation v5.2, Orbit was overhauled to include CSS animations. Everyone has been plagued with issues ever since. This release rolls back Orbit to its former glory.
I also went through all of the commits to Orbit since 5.2 and tried to add all of the bug fixes and features back in. The only known feature that was not added back in was the ability to completely turn off the Orbit timer. The code base was too different to easily merge that feature back in.

orbit does not work anymore!!!

Orbit is dead!!!


How to get message timestamp

Hi~ kafka-rust is awesome.
But how can i get timestamp of message from struct Message ?

Did you manage to look into this?

Hi, I'm stuck with this, anybody has a solution? I'm using the more advanced client.fetch_messages method btw


Feat/codec metrics

Motivation
To go along with adding TCP Events received, this PR adds TCP Events sent, as well as adds the node/router plaintext Messages sent and received.
It also changes the transactions per block to be a gauge rather than a counter (which we already registered it as here, since a counter cannot decrease, thus fixing the transaction metrics in Grafana
Test Plan
Transaction Graph test below

@joske I believe we will also have to update the TPS stat in the Grafana dash, should it just be the avg() rather than the sum(rate())?


Compile for Windows and macOS?

Hello --
I just stumbled across your excellent library, and I'm curious to try to compile as well for macOS and Windows (using mingw).
I think it should be possible, with some tweaks. Has anyone tried either of these?

I have not heard of any attempts to port to mac or Windows. There is one thing to check before attempting it. Linux allows direct access to the Bluetooth adapter via HCI_CHANNEL_USER. See the bind operation at around line 8190 in hcisock() function in btlib.c. If you cannot open a socket and bind to HCI_CHANNEL_USER then btferret cannot work. I think I have tried this on Windows 10 and it failed. If it does work, let me know and I'll think about the linux-specific functions that may cause problems.

Thanks, I'll try to look into it. My ultimate goal is to have the same (or mostly same) code across various platforms I support.


Metabase v0.41.4 not working

Affected module
Ingestion
Describe the bug
Metabase v0.41.4 is failing on test connection. Need to reproduce it and check if any changes need to made
ref: https://openmetadata.slack.com/archives/C02B6955S4S/p1662541141484339
Version:

OS: [e.g. iOS]
Python version:
OpenMetadata version: 0.11.5
OpenMetadata Ingestion package version: [e.g. openmetadata-ingestion[docker]==XYZ]

Additional context
Add any other context about the problem here.

We tested the Metabase v0.41.4 on our side and it is working fine.
Closing this due to inactivity from the user and can re-open it once we get some reply