Better flow support?

Based on #240
Currently something like this works
/* @flow */
import React from 'react';
import styled from 'styled-components';

type Props = {
  bold?: bool,
};

const Text = styled.span`
  color: ${props => props.theme.colors.black};
  font-family: ${props => props.theme.fontFamily};
  font-size: ${props => props.theme.fontSize.text};
  font-weight: ${props => props.bold ? props.theme.fontWeight : 'normal'};
  line-height: ${props => props.theme.lineHeight};
`;

export default (props: Props) => <Text {...props} />;

Would it be better if we could do something like so?
Props = {
  bold?: bool,
};

const default Text = styled.span(Props)`
  color: ${props => props.theme.colors.black};
  ...
`;

//or

const default Text = styled.span({bold?: bool})`
    color: ${props => props.theme.colors.black};
  ...
`;

Just kinda annoying to make another stateless. Thoughts?

/cc @styled-components/typers

I plan to look into this for the flow-typed libdef, I don't have any great ideas so far tho. Also, relevant discussions in flowtype/flow-typed#745

This would be really great. I managed to make it work by this:
//@flow
import styled from 'styled-components';
import type { ComponentType } from 'react';

const Text: ComponentType<{bold: boolean, style: Object}> = styled.span`
   font-weight: ${props => props.bold ? props.theme.fontWeight : 'normal'};
`

But then I have an issue with .extend and other functions.

Hey, is there any major changes between 3 and 4 version? Could we use https://github.com/flow-typed/flow-typed/tree/master/definitions/npm/styled-components_v3.x.x definitions for 4.x?


Missing Link Symbol in Vivaldi

The link symbol is not rendered while using Vivaldi and Violentmonkey.

Let me try changing the fonts to match Firefox and see if that works.

The underlying issue is that Vivaldi does not have a built-in emoji font.
I was able to see the link symbol in Firefox because it falls back to the Twemoji Mozilla font.
I was able to get the link symbol working in Vivaldi after installing the Noto Emoji font through my Linux distribution's package manager.
If I was going to fix the link symbol then I have these options:

Use @font-face with unicode-range: to download an emoji font for the link symbol. Example
Ask users to separately install an emoji font on their computer. Example
Use an SVG. SVG. Inlining.

While I can force the link emoji to start working, each of these options has its own problems.

Each of these assets has its own licensing.
I would be asking to install a 3MB font for a 4KB script.
Users might not successfully install a font on their own.

A simple option is to change the symbol to a character which is in a web safe font.
The trade-off here is that I lose the nice link symbol but the solution is much simpler and smaller.
I think the correct solution is to change the link symbol 🔗 to a common character like '#'.


Events of ApimAllAlert table gets dropped due to size of 'message' column

Description:
Events of ApimAllAlert table gets dropped giving the following error, due to the size of the 'message' attribute of the event exceeding the respective table column size.

Error in adding events to 'ApimAllAlert' store: Data truncation: Data too long for column 'message' at row 1. Hence, dropping event

Since the ApimAllAlert table is created by the first siddhi app that gets deployed, this can be avoided by adding the following entry to all alerts siddhi apps.
@store(type = 'rdbms', datasource = 'APIM_ANALYTICS_DB', field.length = "message:3000")
define table ApimAllAlert (type string, tenantDomain string, message string, severity int, alertTimestamp long);

Fixed for 3.0 in https://github.com/wso2/analytics-apim/pull/697


ci: extract bundle size into workflow

Current dependencies on/for this PR:

#374  👈
main

This stack of pull requests is managed by Graphite.


[Improvements] Add option to choose file types allowed

Is your feature request related to a problem? Please describe
In my case: users can only send PNG, JPEG JPG, but he can select PDF or others types from the device
Describe the solution you'd like
Add option to choose file types allowed like dropzone JS: DropzoneJS Doc - AcceptedFiles

PR Ready - #83

Release in v.0.5.7


i do not want set only props to be set by chocolate

 Time = new EventTime{Start = x.StartDate, End = x.EndDate},

    public class EventTime
    {
        public DateTimeOffset Start { get; init ; }
        public DateTimeOffset End { get; init; }

        public TimeSpan? StartsIn => DateTimeOffset.UtcNow < Start  ? Start - DateTimeOffset.UtcNow : null;
        public TimeSpan? EndsIn => DateTimeOffset.UtcNow > Start && DateTimeOffset.UtcNow < End ? End - DateTimeOffset.UtcNow : null;
    }

  "bodyText": "{\"StatusCode\":500,\"Detail\":null,\"BodyJson\":\"{\\\"Message\\\":\\\"System.InvalidOperationException: No compatible constructor found for input type type `EventTime`.\\\\r\\\\nEither you have to provide a public constructor with settable properties or a public constructor that allows to pass in values for read-only properties.There was no way to set the following properties: StartsIn, EndsIn.\\\\r\\\\n   at HotChocolate.Utilities.Serialization.InputObjectConstructorResolver.GetCompatibleConstructor(Type type, IReadOnlyDictionary`2 properties)\\\\r\\\\n   at HotChocolate.Types.InputObjectType.OnCompleteType(ITypeCompletionContext context, InputObjectTypeDefinition definition)\\\\r\\\\n   at HotChocolate.Types.TypeSystemObjectBase`1.CompleteType(ITypeCompletionContext context)\\\\r\\\\n   at HotChocolate.Configuration.TypeInitializer.<CompleteTypes>g__CompleteType|32_0(RegisteredType registeredType)\\\\r\\\\n   at HotChocolate.Configuration.TypeInitializer.ProcessTypes(TypeDependencyKind kind, Func`2 action)\\\\r\\\\n

The problem are the StartsIn and EndsIn properties not the init properties
HotChocolate picks up all properties, these properties would also be in the type itself. If they have no setter we look for a constructor. If there is no constructor we throw.
A options would be to ignore the properties without and constructor parameter completely
You can work around this issue in multiple ways:
    public class EventTime
    {
        public DateTimeOffset Start { get; init ; }
        public DateTimeOffset End { get; init; }

        public TimeSpan? StartsIn() => DateTimeOffset.UtcNow < Start  ? Start - DateTimeOffset.UtcNow : null;
        public TimeSpan? EndsIn() => DateTimeOffset.UtcNow > Start && DateTimeOffset.UtcNow < End ? End - DateTimeOffset.UtcNow : null;
    }

or
  public class EventTime
    {
        public DateTimeOffset Start { get; init ; }
        public DateTimeOffset End { get; init; }
        [GraphQLIgnore]
        public TimeSpan? StartsIn => DateTimeOffset.UtcNow < Start  ? Start - DateTimeOffset.UtcNow : null;
        [GraphQLIgnore]
        public TimeSpan? EndsIn => DateTimeOffset.UtcNow > Start && DateTimeOffset.UtcNow < End ? End - DateTimeOffset.UtcNow : null;
    }

or
    public class EventTimeInput : InputObjectType< EventTime>
    {
       protected override void Configure(IInputObjectTypeDescriptor< EventTime>)
       {
           descriptor.Ignore(x => x. StartsIn);
           descriptor.Ignore(x => x. EndsIn);
       }
    }

thanks for workarounds,
current behavior - if developer will try to set the properties ever let throw exception, even if he will never will do that. In C# TimeSpan? get_StartsIn() is internal impl of property, workaround suggested (on of) is TimeSpan? StartsIn(), so there is no difference in workaround and consider readonly props as readonly methods. But yes - if developer will try to set readonly method than throw.
So workarounds will work for me, but I do not see why would graphql try to set readonly methods one case (readonly props) and not in other (read only methods). while dropping an opinion about dev intetion, could just follow formal rule consier read only props as readonly methods (which these actually are)

@dzmitry-lahoda
So the reason why we try to infer the readonly properties is because this is valid and will work:
    public class EventTime
    {
        public EventTime(DateTimeOffset start, DateTimeOffset end) {
            Start = start;
            End = end;
        }

        public DateTimeOffset Start { get; }
        public DateTimeOffset End { get; }
    }

readonly methods one case (readonly props) and not in other (read only methods).

This code create properties and not methods:
public TimeSpan? StartsIn => DateTimeOffset.UtcNow < Start  ? Start - DateTimeOffset.UtcNow : null;

which will compile to
public TimeSpan? StartsIn
    {
         get {
               return DateTimeOffset.UtcNow < Start  ? Start - DateTimeOffset.UtcNow : null;
               }
    }

where as
public TimeSpan? StartsIn() => DateTimeOffset.UtcNow < Start  ? Start - DateTimeOffset.UtcNow : null;

is and stays a method

so i can fix
   public class EventTime
    {
        public EventTime(DateTimeOffset start, DateTimeOffset end) {
            Start = // do the calculation, ignore aregument
            End =  // do the calculation, ignore aregument
        }

        public DateTimeOffset Start { get; }
        public DateTimeOffset End { get; }
    }

i believe in MSIL
DateTimeOffset Start { get; } - is property with private setter
DateTimeOffset Start => the property with no setter at all (only backing field)
but still could be same on of two options
eventually in MSIL, property is get_FooBar method, tagged with custom attribute may be, if I recall correctly, so it is method with get_ prefix.
option could be if there are props with public setter, neither having constructor with args - than do nothing until i try set the property. i think behaviour of json serializes could be event more relaxed - ignore issue and allow to debug on json data level.
my propblem is next - i do not want gql to set these, i set them manually, why would it throw?


vartime remark

Add remark for bits() method documentation.

Perhaps add something like "and will operate in constant-time for a fixed index"?


running in docker

code is adjusted to run in docker container.
Main logic has not been changed, one can still run code using local python 2.7
Some issues I faced also has been resolved, see commits 91a11b8652cb3303ceb89cff8efa928e4496fce3 and c8924c2c565d0b9d1e085d48bbab477d906a6b79

closed after successful rebase and merge


Does log_every_n_steps work in validation_step?

I find that golbal_step is the training_step, if i want to log something every k validation_steps, how to implement？
log_every_n_steps works in trains_loop but does not work in validation loop.
Should add global_traing_step, global_val_step and global_test_step?
self.log only support on_step and on epoch, can this api support k_steps or k_epoch (training, validation and test)?

@Maybewuss  one thing you could do is use the check_val_every_n_epoch Trainer flag, so you do the validation every k training epochs. But if you would like to do the validation every time, but only log every k epochs, you could give the k value in the __init__ of your model and store it in, for example, self.log_every_k. Then do in the training_epoch_end and in the validation_epoch_end something like if self.current_epoch % self.log_every_k == 0:.
If you want to do it for steps (batches) instead of epochs, do the same, but check the value in training_step and validation_step, maybe comparing it with the batch_idx.

PL supports it, but it is not meaningful to log metrics on step in validation.
Maybe you are trying to log some images or other type of data samples?
In this case, you can do
def validation_step(self, batch_idx, batch):

    if (batch_idx + 1) % self.trainer.log_every_n_steps:
        self.logger.experiment.log_method(samples ... )

PL supports it, but it is not meaningful to log metrics on step in validation.
Maybe you are trying to log some images or other type of data samples?
In this case, you can do
def validation_step(self, batch_idx, batch):

    if (batch_idx + 1) % self.trainer.log_every_n_steps:
        self.logger.experiment.log_method(samples ... )

Thanks


Failed to execute goal io.helidon.build-tools:helidon-maven-plugin:2.1.2:jlink-image

Hi,
I got the erro below when I ran the command: mvn package -Pjlink-image
...
[INFO] Including 17 Java dependencies: java.base, java.datatransfer, java.desktop, java.instrument, java.logging, java.management, java.naming, java.prefs, java.security.sasl, java.sql, java.transaction.xa, java.xml, jdk.attach, jdk.internal.jvmstat, jdk.jdi, jdk.jdwp.agent, jdk.unsupported
[INFO] Including debug support: jdk.jdwp.agent
[INFO] Creating base image: target\helidon-quickstart-mp-jri
[INFO] Installing 132 application jars in target\helidon-quickstart-mp-jri\app
[INFO]   checking index in CDI beans archive helidon-quickstart-mp.jar
[INFO]   creating missing index for CDI beans archive helidon-microprofile-server-2.2.0.jar
[INFO]   creating missing index for CDI beans archive jersey-weld2-se-2.32.jar
[INFO]   creating missing index for CDI beans archive helidon-health-checks-2.2.0.jar
[INFO]   creating missing index for CDI beans archive helidon-microprofile-fault-tolerance-2.2.0.jar
[INFO]   creating missing index for CDI beans archive openapi-ui-1.1.4.jar
[INFO] Creating startup class list for helidon-quickstart-mp.jar
[INFO] Creating Class Data Sharing archive for helidon-quickstart-mp.jar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  02:33 min
[INFO] Finished at: 2021-01-22T10:41:03-03:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal io.helidon.build-tools:helidon-maven-plugin:2.1.2:jlink-image (jlink-image) on project helidon-quickstart-mp: Image generation error: io.helidon.build.util.ProcessMonitor$ProcessTimeoutException: Creating Class Data Sharing archive for helidon-quickstart-mp.jar timed out
[ERROR]     OpenJDK 64-Bit Server VM warning: Pre JDK 6 class not supported by CDS: 49.0 javax/inject/Provider
[ERROR]     [2.179s][warning][cds] Preload Warning: Verification failed for org.jboss.weld.environment.se.Weld
[ERROR]     [2.184s][warning][cds] Preload Warning: Verification failed for io.helidon.microprofile.cdi.HelidonContainerImpl
[ERROR]     OpenJDK 64-Bit Server VM warning: Pre JDK 6 class not supported by CDS: 49.0 javax/inject/Provider
[ERROR]     [2.194s][warning][cds] Preload Warning: Cannot find javax/inject/Provider
[ERROR]     OpenJDK 64-Bit Server VM warning: Pre JDK 6 class not supported by CDS: 49.0 javax/inject/Provider
[ERROR]     [2.196s][warning][cds] Preload Warning: Cannot find javax/enterprise/inject/Instance
[ERROR]     OpenJDK 64-Bit Server VM warning: Pre JDK 6 class not supported by CDS: 49.0 javax/inject/Provider
[ERROR]     [2.199s][warning][cds] Preload Warning: Cannot find javax/enterprise/inject/se/SeContainer
[ERROR]     OpenJDK 64-Bit Server VM warning: Pre JDK 6 class not supported by CDS: 49.0 javax/inject/Provider
[ERROR]     [2.415s][warning][cds] Preload Warning: Cannot find javax/enterprise/inject/spi/CDI
[ERROR]     OpenJDK 64-Bit Server VM warning: Pre JDK 6 class not supported by CDS: 49.0 javax/inject/Provider
[ERROR]     [2.423s][warning][cds] Preload Warning: Cannot find org/jboss/weld/inject/WeldInstance
[ERROR]     OpenJDK 64-Bit Server VM warning: Pre JDK 6 class not supported by CDS: 49.0 javax/inject/Provider
[ERROR]     [2.429s][warning][cds] Preload Warning: Cannot find org/jboss/weld/AbstractCDI
[ERROR]     OpenJDK 64-Bit Server VM warning: Pre JDK 6 class not supported by CDS: 49.0 javax/inject/Provider
[ERROR]     [2.439s][warning][cds] Preload Warning: Cannot find io/helidon/microprofile/cdi/HelidonContainerImpl$HelidonCdi
[ERROR]     [7.303s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy1
[ERROR]     [24.931s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy4
[ERROR]     [24.932s][warning][cds] Preload Warning: Cannot find javax/inject/Scope
[ERROR]     OpenJDK 64-Bit Server VM warning: Pre JDK 6 class not supported by CDS: 49.0 javax/inject/Scope
[ERROR]     [24.932s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy6
[ERROR]     [24.946s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy7
[ERROR]     OpenJDK 64-Bit Server VM warning: Pre JDK 6 class not supported by CDS: 49.0 javax/inject/Named
[ERROR]     [24.946s][warning][cds] Preload Warning: Cannot find javax/inject/Named
[ERROR]     OpenJDK 64-Bit Server VM warning: Pre JDK 6 class not supported by CDS: 49.0 javax/inject/Qualifier
[ERROR]     [24.947s][warning][cds] Preload Warning: Cannot find javax/inject/Qualifier
[ERROR]     [24.947s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy8
[ERROR]     [24.947s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy9
[ERROR]     [25.105s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy10
[ERROR]     [25.105s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy11
[ERROR]     [25.105s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy12
[ERROR]     [25.106s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy13
[ERROR]     OpenJDK 64-Bit Server VM warning: Pre JDK 6 class not supported by CDS: 49.0 javax/inject/Provider
[ERROR]     [26.305s][warning][cds] Preload Warning: Verification failed for org.jboss.weld.manager.BeanManagerImpl
[ERROR]     OpenJDK 64-Bit Server VM warning: Pre JDK 6 class not supported by CDS: 49.0 javax/inject/Inject
[ERROR]     [27.226s][warning][cds] Preload Warning: Cannot find javax/inject/Inject
[ERROR]     OpenJDK 64-Bit Server VM warning: Pre JDK 6 class not supported by CDS: 49.0 javax/inject/Singleton
[ERROR]     [27.486s][warning][cds] Preload Warning: Cannot find javax/inject/Singleton
[ERROR]     OpenJDK 64-Bit Server VM warning: Pre JDK 6 class not supported by CDS: 49.0 javax/inject/Provider
[ERROR]     [27.886s][warning][cds] Preload Warning: Verification failed for org.jboss.weld.bean.builtin.BeanManagerProxy
[ERROR]     [28.405s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy15
[ERROR]     [28.422s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy16
[ERROR]     [28.427s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy17
[ERROR]     [28.445s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy18
[ERROR]     OpenJDK 64-Bit Server VM warning: Pre JDK 6 class not supported by CDS: 49.0 javax/inject/Provider
[ERROR]     [28.940s][warning][cds] Preload Warning: Cannot find org/jboss/weld/environment/se/WeldContainer
[ERROR]     [28.957s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy20
[ERROR]     [29.061s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy21
[ERROR]     [29.065s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy22
[ERROR]     OpenJDK 64-Bit Server VM warning: Pre JDK 6 class not supported by CDS: 49.0 javax/inject/Named
[ERROR]     [29.828s][warning][cds] Preload Warning: Verification failed for org.jboss.weld.resolution.ResolvableBuilder
[ERROR]     [30.049s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy23
[ERROR]     [30.635s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy24
[ERROR]     [30.723s][warning][cds] Preload Warning: Cannot find io/helidon/microprofile/metrics/$Proxy25
[ERROR]     [30.827s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy26
[ERROR]     [30.827s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy27
[ERROR]     [30.827s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy28
[ERROR]     [30.827s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy29
[ERROR]     [30.828s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy30
[ERROR]     [30.828s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy31
[ERROR]     [30.828s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy32
[ERROR]     [30.857s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy33
[ERROR]     [30.885s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy34
[ERROR]     [30.915s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy35
[ERROR]     [30.944s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy36
[ERROR]     [31.032s][warning][cds] Preload Warning: Cannot find io/helidon/microprofile/metrics/$Proxy37
[ERROR]     [31.032s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy38
[ERROR]     [31.056s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy39
[ERROR]     [31.067s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy40
[ERROR]     [31.130s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy41
[ERROR]     [31.264s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy42
[ERROR]     [31.452s][warning][cds] Preload Warning: Cannot find io/helidon/microprofile/faulttolerance/$Proxy43
[ERROR]     [31.582s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy44
[ERROR]     [31.586s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy45
[ERROR]     [31.587s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy46
[ERROR]     [31.595s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy47
[ERROR]     [31.720s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy48
[ERROR]     [31.969s][warning][cds] Preload Warning: Cannot find io/helidon/microprofile/jwt/auth/$Proxy49
[ERROR]     [31.969s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy50
[ERROR]     [32.048s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy51
[ERROR]     [33.296s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy52
[ERROR]     [33.643s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy53
[ERROR]     [34.202s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy54
[ERROR]     [34.203s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy55
[ERROR]     [34.253s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy56
[ERROR]     [34.253s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy57
[ERROR]     [34.254s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy58
[ERROR]     [34.292s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy59
[ERROR]     [34.292s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy60
[ERROR]     [34.309s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy61
[ERROR]     [34.310s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy62
[ERROR]     [34.656s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy63
[ERROR]     [34.657s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy64
[ERROR]     [34.657s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy65
[ERROR]     [34.657s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy66
[ERROR]     [34.808s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy67
[ERROR]     [34.808s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy68
[ERROR]     OpenJDK 64-Bit Server VM warning: Pre JDK 6 class not supported by CDS: 49.0 javax/inject/Provider
[ERROR]     [45.336s][warning][cds] Preload Warning: Cannot find org/jboss/weld/bean/builtin/InstanceImpl
[ERROR]     OpenJDK 64-Bit Server VM warning: Pre JDK 6 class not supported by CDS: 49.0 javax/inject/Provider
[ERROR]     [45.450s][warning][cds] resolve_indy for class org/jboss/weld/environment/se/WeldSEBeanRegistrant has encountered exception: java.lang.UnsupportedClassVersionError Unsupported major.minor version for dump time 49.0
[ERROR]     OpenJDK 64-Bit Server VM warning: Pre JDK 6 class not supported by CDS: 49.0 javax/inject/Provider
[ERROR]     [45.456s][warning][cds] Preload Warning: Verification failed for org.jboss.weld.bootstrap.events.configurator.BeanConfiguratorImpl$CreateCallback
[ERROR]     OpenJDK 64-Bit Server VM warning: Pre JDK 6 class not supported by CDS: 49.0 javax/inject/Provider
[ERROR]     [45.457s][warning][cds] resolve_indy for class io/helidon/microprofile/config/ConfigCdiExtension has encountered exception: java.lang.UnsupportedClassVersionError Unsupported major.minor version for dump time 49.0
[ERROR]     [45.457s][warning][cds] resolve_indy for class io/helidon/microprofile/config/ConfigCdiExtension has encountered exception: java.lang.UnsupportedClassVersionError Unsupported major.minor version for dump time 49.0
[ERROR]     [45.457s][warning][cds] resolve_indy for class io/helidon/microprofile/config/ConfigCdiExtension has encountered exception: java.lang.UnsupportedClassVersionError Unsupported major.minor version for dump time 49.0
[ERROR]     [45.457s][warning][cds] resolve_indy for class io/helidon/microprofile/config/ConfigCdiExtension has encountered exception: java.lang.UnsupportedClassVersionError Unsupported major.minor version for dump time 49.0
[ERROR]     [45.457s][warning][cds] resolve_indy for class io/helidon/microprofile/config/ConfigCdiExtension has encountered exception: java.lang.UnsupportedClassVersionError Unsupported major.minor version for dump time 49.0
[ERROR]     [45.457s][warning][cds] resolve_indy for class io/helidon/microprofile/config/ConfigCdiExtension has encountered exception: java.lang.UnsupportedClassVersionError Unsupported major.minor version for dump time 49.0
[ERROR]     [45.670s][warning][cds] Preload Warning: Verification failed for org.jboss.weld.resolution.InterceptorResolvableBuilder
[ERROR]     [45.690s][warning][cds] Preload Warning: Verification failed for org.jboss.weld.resolution.DecoratorResolvableBuilder
[ERROR]     [46.248s][warning][cds] Preload Warning: Cannot find org/microprofileext/openapi/swaggerui/StaticResourcesService$Proxy$_$$_WeldSubclass
[ERROR]     [46.261s][warning][cds] Preload Warning: Cannot find org/microprofileext/openapi/swaggerui/OpenApiUiService$Proxy$_$$_WeldSubclass
[ERROR]     [46.299s][warning][cds] Preload Warning: Cannot find io/helidon/examples/quickstart/mp/GreetResource$Proxy$_$$_WeldSubclass
[ERROR]     OpenJDK 64-Bit Server VM warning: Pre JDK 6 class not supported by CDS: 49.0 javax/inject/Provider
[ERROR]     [46.318s][warning][cds] resolve_indy for class org/jboss/weld/AbstractCDI has encountered exception: java.lang.UnsupportedClassVersionError Unsupported major.minor version for dump time 49.0
[ERROR]     [49.433s][warning][cds] resolve_indy for class io/helidon/microprofile/config/ConfigCdiExtension has encountered exception: java.lang.UnsupportedClassVersionError Unsupported major.minor version for dump time 49.0
[ERROR]     [49.487s][warning][cds] resolve_indy for class io/helidon/microprofile/config/ConfigCdiExtension has encountered exception: java.lang.UnsupportedClassVersionError Unsupported major.minor version for dump time 49.0
[ERROR]     [49.548s][warning][cds] resolve_indy for class io/helidon/microprofile/config/ConfigCdiExtension has encountered exception: java.lang.UnsupportedClassVersionError Unsupported major.minor version for dump time 49.0
[ERROR]     [52.493s][warning][cds] Preload Warning: Cannot find jdk/proxy2/$Proxy72
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

The repository is here:
https://github.com/tivrfoa/helidon-openapi-swagger-ui
Windows 10 64 bits
/helidon-quickstart-mp
$ javac --version
javac 16-ea
$ java --version
openjdk 16-ea 2021-03-16
OpenJDK Runtime Environment (build 16-ea+32-2190)
OpenJDK 64-Bit Server VM (build 16-ea+32-2190, mixed mode, sharing)

Bulding with docker works:
docker build -t helidon-quickstart-mp-jri -f Dockerfile.jlink .
REPOSITORY                                                                    TAG                      IMAGE ID       CREATED         SIZE
helidon-quickstart-mp-jri                                                     latest                   1be88682d1fd   2 minutes ago   199MB

docker run -it helidon-quickstart-mp-jri
2021.01.22 14:15:58 INFO io.helidon.common.LogConfig Thread[main,5,main]: Logging at initialization configured using classpath: /logging.properties
2021.01.22 14:15:58 INFO org.jboss.weld.Version Thread[main,5,main]: WELD-000900: 3.1.4 (Final)
2021.01.22 14:15:58 INFO org.jboss.weld.Bootstrap Thread[main,5,main]: WELD-ENV-000020: Using jandex for bean discovery
2021.01.22 14:15:58 INFO org.jboss.weld.Bootstrap Thread[main,5,main]: WELD-000101: Transactional services not available. Injection of @Inject UserTransaction not available. Transactional observers will be invoked synchronously.
2021.01.22 14:15:59 INFO org.jboss.weld.Event Thread[main,5,main]: WELD-000411: Observer method [BackedAnnotatedMethod] private io.helidon.microprofile.openapi.OpenApiCdiExtension.processAnnotatedType(@Observes ProcessAnnotatedType<X>) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2021.01.22 14:15:59 INFO org.jboss.weld.Event Thread[main,5,main]: WELD-000411: Observer method [BackedAnnotatedMethod] public org.glassfish.jersey.ext.cdi1x.internal.ProcessAllAnnotatedTypes.processAnnotatedType(@Observes ProcessAnnotatedType<?>, BeanManager) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2021.01.22 14:16:00 INFO io.helidon.tracing.tracerresolver.TracerResolverBuilder Thread[main,5,main]: TracerResolver not configured, tracing is disabled
2021.01.22 14:16:00 WARNING io.helidon.microprofile.tracing.TracingCdiExtension Thread[main,5,main]: helidon-microprofile-tracing is on the classpath, yet there is no tracer implementation library. Tracing uses a no-op tracer. As a result, no tracing will be configured for WebServer and JAX-RS
2021.01.22 14:16:00 INFO io.helidon.microprofile.security.SecurityCdiExtension Thread[main,5,main]: Authentication provider is missing from security configuration, but security extension for microprofile is enabled (requires providers configuration at key security.providers). Security will not have any valid authentication provider
2021.01.22 14:16:00 INFO io.helidon.microprofile.security.SecurityCdiExtension Thread[main,5,main]: Authorization provider is missing from security configuration, but security extension for microprofile is enabled (requires providers configuration at key security.providers). ABAC provider is configured for authorization.
2021.01.22 14:16:00 INFO io.helidon.microprofile.server.ServerCdiExtension Thread[main,5,main]: Registering JAX-RS Application: HelidonMP
2021.01.22 14:16:01 INFO io.helidon.webserver.NettyWebServer Thread[nioEventLoopGroup-2-1,10,main]: Channel '@default' started: [id: 0x48e366c4, L:/<IP_ADDRESS>:8080]
2021.01.22 14:16:01 INFO io.helidon.microprofile.server.ServerCdiExtension Thread[main,5,main]: Server started on http://localhost:8080 (and all other host addresses) in 3640 milliseconds (since JVM startup).
2021.01.22 14:16:01 INFO io.helidon.common.HelidonFeatures Thread[features-thread,5,main]: Helidon MP 2.2.0 features: [CDI, Config, Fault Tolerance, Health, JAX-RS, Metrics, Open API, Security, Server, Tracing]
^C2021.01.22 14:17:17 INFO io.helidon.webserver.NettyWebServer Thread[nioEventLoopGroup-2-1,10,main]: Channel '@default' closed: [id: 0x48e366c4, L:/<IP_ADDRESS>:8080]
2021.01.22 14:17:17 INFO io.helidon.microprofile.server.ServerCdiExtension Thread[helidon-cdi-shutdown-hook,5,main]: Server stopped in 73 milliseconds.
Server stopped in 73 milliseconds.
2021.01.22 14:17:18 INFO org.jboss.weld.Bootstrap Thread[helidon-cdi-shutdown-hook,5,main]: WELD-ENV-002001: Weld SE container 758b65d9-c925-4be5-a315-1b60f9783e97 shut down

Bulding with docker works:
docker build -t helidon-quickstart-mp-jri -f Dockerfile.jlink .
REPOSITORY                                                                    TAG                      IMAGE ID       CREATED         SIZE
helidon-quickstart-mp-jri                                                     latest                   1be88682d1fd   2 minutes ago   199MB

docker run -it helidon-quickstart-mp-jri
2021.01.22 14:15:58 INFO io.helidon.common.LogConfig Thread[main,5,main]: Logging at initialization configured using classpath: /logging.properties
2021.01.22 14:15:58 INFO org.jboss.weld.Version Thread[main,5,main]: WELD-000900: 3.1.4 (Final)
2021.01.22 14:15:58 INFO org.jboss.weld.Bootstrap Thread[main,5,main]: WELD-ENV-000020: Using jandex for bean discovery
2021.01.22 14:15:58 INFO org.jboss.weld.Bootstrap Thread[main,5,main]: WELD-000101: Transactional services not available. Injection of @Inject UserTransaction not available. Transactional observers will be invoked synchronously.
2021.01.22 14:15:59 INFO org.jboss.weld.Event Thread[main,5,main]: WELD-000411: Observer method [BackedAnnotatedMethod] private io.helidon.microprofile.openapi.OpenApiCdiExtension.processAnnotatedType(@Observes ProcessAnnotatedType<X>) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2021.01.22 14:15:59 INFO org.jboss.weld.Event Thread[main,5,main]: WELD-000411: Observer method [BackedAnnotatedMethod] public org.glassfish.jersey.ext.cdi1x.internal.ProcessAllAnnotatedTypes.processAnnotatedType(@Observes ProcessAnnotatedType<?>, BeanManager) receives events for all annotated types. Consider restricting events using @WithAnnotations or a generic type with bounds.
2021.01.22 14:16:00 INFO io.helidon.tracing.tracerresolver.TracerResolverBuilder Thread[main,5,main]: TracerResolver not configured, tracing is disabled
2021.01.22 14:16:00 WARNING io.helidon.microprofile.tracing.TracingCdiExtension Thread[main,5,main]: helidon-microprofile-tracing is on the classpath, yet there is no tracer implementation library. Tracing uses a no-op tracer. As a result, no tracing will be configured for WebServer and JAX-RS
2021.01.22 14:16:00 INFO io.helidon.microprofile.security.SecurityCdiExtension Thread[main,5,main]: Authentication provider is missing from security configuration, but security extension for microprofile is enabled (requires providers configuration at key security.providers). Security will not have any valid authentication provider
2021.01.22 14:16:00 INFO io.helidon.microprofile.security.SecurityCdiExtension Thread[main,5,main]: Authorization provider is missing from security configuration, but security extension for microprofile is enabled (requires providers configuration at key security.providers). ABAC provider is configured for authorization.
2021.01.22 14:16:00 INFO io.helidon.microprofile.server.ServerCdiExtension Thread[main,5,main]: Registering JAX-RS Application: HelidonMP
2021.01.22 14:16:01 INFO io.helidon.webserver.NettyWebServer Thread[nioEventLoopGroup-2-1,10,main]: Channel '@default' started: [id: 0x48e366c4, L:/<IP_ADDRESS>:8080]
2021.01.22 14:16:01 INFO io.helidon.microprofile.server.ServerCdiExtension Thread[main,5,main]: Server started on http://localhost:8080 (and all other host addresses) in 3640 milliseconds (since JVM startup).
2021.01.22 14:16:01 INFO io.helidon.common.HelidonFeatures Thread[features-thread,5,main]: Helidon MP 2.2.0 features: [CDI, Config, Fault Tolerance, Health, JAX-RS, Metrics, Open API, Security, Server, Tracing]
^C2021.01.22 14:17:17 INFO io.helidon.webserver.NettyWebServer Thread[nioEventLoopGroup-2-1,10,main]: Channel '@default' closed: [id: 0x48e366c4, L:/<IP_ADDRESS>:8080]
2021.01.22 14:17:17 INFO io.helidon.microprofile.server.ServerCdiExtension Thread[helidon-cdi-shutdown-hook,5,main]: Server stopped in 73 milliseconds.
Server stopped in 73 milliseconds.
2021.01.22 14:17:18 INFO org.jboss.weld.Bootstrap Thread[helidon-cdi-shutdown-hook,5,main]: WELD-ENV-002001: Weld SE container 758b65d9-c925-4be5-a315-1b60f9783e97 shut down

It failed because it took too long: Image generation error: io.helidon.build.util.ProcessMonitor$ProcessTimeoutException: Creating Class Data Sharing archive for helidon-quickstart-mp.jar timed out.
We did raise the hard-coded timeouts in the upcoming version of the jlink-image tool (from 60s to5min) however they should be configurable with the plugin. I've filed an enhancement for that here: https://github.com/oracle/helidon-build-tools/issues/342

It failed because it took too long: Image generation error: io.helidon.build.util.ProcessMonitor$ProcessTimeoutException: Creating Class Data Sharing archive for helidon-quickstart-mp.jar timed out.
We did raise the hard-coded timeouts in the upcoming version of the jlink-image tool (from 60s to5min) however they should be configurable with the plugin. I've filed an enhancement for that here: https://github.com/oracle/helidon-build-tools/issues/342

It failed because it took too long: Image generation error: io.helidon.build.util.ProcessMonitor$ProcessTimeoutException: Creating Class Data Sharing archive for helidon-quickstart-mp.jar timed out.
We did raise the hard-coded timeouts in the upcoming version of the jlink-image tool (from 60s to5min) however they should be configurable with the plugin. I've filed an enhancement for that here: oracle/helidon-build-tools#342

Thank you! Would you like me to close this issue? Please feel free to close it if you prefer.

It failed because it took too long: Image generation error: io.helidon.build.util.ProcessMonitor$ProcessTimeoutException: Creating Class Data Sharing archive for helidon-quickstart-mp.jar timed out.
We did raise the hard-coded timeouts in the upcoming version of the jlink-image tool (from 60s to5min) however they should be configurable with the plugin. I've filed an enhancement for that here: oracle/helidon-build-tools#342

Thank you! Would you like me to close this issue? Please feel free to close it if you prefer.


Topic/mac2

Hello everyone
Can someone merge the branch topic/mac2 with the master ?
There are only few modifications for compatibility, hence this should be fast.
Thanks in advance
Francois

Hi everyone,
I just merged this on topic/python which is now the next candidate for the release.
If everyone is fine with that I will close this pull request.
Olivier.

Hello Olivier,
Please wait for the release, there are some things I'd like to check and/or correct.
François


tslib v1.13.0 has breaking change

tslib v 1.13.0 is causing a compile error due to a breaking change
Compiling...
Using tsc v2.5.3
common/temp/node_modules/tslib/tslib.d.ts(37,78): error TS2304: Cannot find name 'PropertyKey'.
common/temp/node_modules/tslib/tslib.d.ts(37,103): error TS2304: Cannot find name 'PropertyKey'.
We have created an issue with tslib to try and get this fixed, if not we will need to roll back and be fixed to v 1.11.2. As a temporary workaround if you have this issue is to update your local package.json files to reference "1.11.2" instead of "^1.11.1"
Raised TSLib Issue
https://github.com/microsoft/tslib/issues/115

As this is the 2nd time in recent history and looking at how the tslib project is now structured, it appears that it's going to remain busted for us as we are currently targeting es3 as our base module to ensure that we don't accidently break our SDK user base that has users that are currently still relying on ES3 based browsers.
As such, I'm going to completely break our dependency on tslib, without the normal corresponding code bloat (as size is still a major concern). But I'm attempting to do this in a backward compatible way so that we don't break

CDN only users
Older TypeScript users ( < 3.x)
More modern TypeScript users (i.e. 3.x)
Anyone how is currently user any version of tslib

as previously we broke users using TypeScript and a newer version of tslib then we needed to be pinned to (v1.10.1 from memory
This is also a major consideration for breaking the dependency, so we don't break anyone who wants/needs to use a version of tslib > 1.11.2 (the last known good version that we can compile with)

@MSNev Could you release a version still using tslib at least for esm version? The recent change create pollution in global object.

Created #1280 to investigate how we could possibly stop exposing the global functions.

Is it just the __extends() or __assign() or are you seeing something else in the global scope

Both __extends and __assign but nothing else.

Which modules / files are you ingesting (using) [i.e. just the AISku or the individual components, if the later which ones).

I am only using "@microsoft/applicationinsights-web" module (and indirectly its dependencies).
I would prefer tslib version to be fixed to 1.11.2 even if it would potentially create duplicated version of tslib in my projects because, since I am using rollupjs, it would be the same result as with 2.5.5 except that it would not pollute the global object (but I understand that it could cause some trouble in a different configuration than mine to have different versions of tslib in the same project).
I see your issue here https://github.com/microsoft/tslib/issues/115 , if the problem is only with "es3" target in a major version, I would suggest to drop support for this target and change it to "es5" (all alive browsers including IE11 support it since more than 10 years now).

Looking at the generated code the /dist/ folder looks like we could safely stop exposing these methods, but, for the /dist-esm/ we can't, without declaring this as a breaking change and requiring users to provide their own versions of these methods.
Unfortunately, we can't just fix it @ 1.11.2 as this breaks some consumers such as the discussion in #1242. So that's not really an option.
Likewise we also have users who's end-users are still using IE7/IE8 (i.e. medical organizations that are still using XP), so while it would be great to be able to re-target @ es5 we would also need to beef up our testing infrastructure to ensure that we don't break any es3 users.... However, our current test infra actually doesn't work on IE at all let alone IE running in IE7/8 mode.
So for now that is not currently an option either...
On the upside, these methods are only exposed via the applicationinsights-shims module, so we only have a single location to make the change (once we identify a safe way to achieve this).

You may can re-bind "tslib" to a local module with some post-build script after typescript transpilation. For example:
import * as tslib_1 from "tslib";

to
import * as tslib_1 from "./tslib.js";

or maybe bind it to your own tslib compatible module:
import * as tslib_1 from "@microsoft/applicationinsights-shims";

It would maybe break sourcemaps however.
Thanks for your answers :).

Included in v 2.5.5 which is now fully deployed


RDS dbinstance: Check only major version if AutoMinorVersionUpgrade is true

Description of your changes
If a rds dbinstance is deployed with AutoMinorVersionUpgrade set to true, and aws updates the minor version, the controller thinks there is a change. In this pull request, the isUpToDate method is updated to check only the major version of the db in this case.

Fixes #832
I have:

[x] Read and followed Crossplane's contribution process.
[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested
Tested manually

I have autoMinorVersionUpgrade: true set on an RDSInstance that I've deployed as Postgres 15.2. If I manually upgrade the instance in the console to 15.3 via the AWS console (as AWS would presumably do in the next maintenance window), then the CR just goes into a Synced: False status and just see this sort of error on the CR.
Message:               update failed: cannot modify RDS instance: api error InvalidParameterCombination: Cannot upgrade postgres from 15.3 to 15.2

Is there something I've missed here as the PR seems to suggest that this shouldn't be the case now? @haarchri


feat(configFactory): be able to access junit-context during config of the server

This is in WIP status for now, waiting for review and indication if this is ok for @lanwen
Closes #9

yea, looks good, thx for the PR, please continue

If this is ok for you, could you say to me what you would like me to add to this PR to be accepted?

I've added one unit test about this new feature. If this is enough from your point of view, you can merge it 👍

please rebase on master, fixed an issue with the build

Rebase done on master, I let you decide if all is ok for you.
I will try to work on #16 if possible 😉

great, thank you, will release that shortly


DAWN-674 ⁃ System contracts are described by Ricardian Contracts.

Each call in the eosio.system contract needs to be described by a standalone Ricardian Contract with full legal language and with clear placeholders indicating where variables like ﹍from-party﹍ and ﹍to-party﹍ go.
Some items that we have gathered about proxy voting:

There two types of proxies.  One is a general proxy.  A general proxy is written in such a way that it gives the proxy holder the right to vote as he or she sees fit on any business that may come up at a meeting.  A limited proxy includes on the proxy the business that is to be voted on and a place for the member to tell the proxy holder the way to vote on the business.  The proxy holder is legally required to cast the vote the way he has been designated by the member. (5)

The proxy should include the name of the association, the word proxy under it, and a statement that ____________ is the person’s proxy for the meeting, and then a place for the member to sign and date the proxy.  If the proxy is a limited proxy it would also include any issues that are to be voted on at the meeting and a place for the member to check “yes” or “no” or a place to vote for any candidates being considered for office.   A proxy also may include when it expires. (5)

In Riddicks Rules of Procedure, it states that “Proxy voting gives the power of attorney to a member to cast the votes for another legal vote holder.” (3)

In a Guide for Voting, it states that “The word proxy has two meanings.  One meaning is the power of attorney given to another person to act in one’s stead.  The other meaning designates the person who holds the power of attorney.   (4)

The most important rule is that the proxy permission must be in writing (1)

The proxy form is clear and simple so that the intent of the owner is clear (1)

When it comes to decision-making in your building, attending meetings in person is always best. But should the need arise, shareholders and unit owners are permitted to vote in board elections and other matters of corporate governance by proxy or absentee ballot. (2)

Proxies are written statements by a shareholder or unit owner authorizing another person (the proxy holder) to vote his shares or common interests at a shareholders or special meeting. (2)

Boards often rely upon the collection of proxies to fulfill the quorum requirement at the annual shareholders meeting or any special meetings. (2)

It's a good idea to remind shareholders or unit owners in writing before the meeting to send in their proxies, if they will be unable to attend, so they can be counted toward the quorum. (2)

The cardinal rules regarding issuance of a proxy are that the document must be in writing, and it must be dated and signed by the record owner or his attorney in fact. Unless indicated otherwise, the term of a proxy is 11 months from its issuance. If multiple proxies are issued by the same shareholder, the only valid one is that which was issued latest in time. (2)

Proxies signed by any person other than the owner of record are invalid unless accompanied by documentary evidence such as a duly executed Power of Attorney, Letters Testamentary or Letters of Administration that this person is signing as attorney in fact. (2)

If the record owner dies or is found incompetent after issuing of a proxy, the proxy is valid unless the association's secretary has been notified in writing prior to the meeting. (2)

A shareholder or unit owner who changes his mind can issue a new proxy reflecting his revised preference. A proxy can also be revoked by written notice to the association's secretary. Or, a shareholder or unit owner can revoke the proxy by attending the meeting and casting a ballot that reflects the new preference. The ballot will supersede the previously issued proxy; however, merely attending the meeting, without actually casting a ballot, will not serve to revoke the proxy. (2)

Commonly Stated Problems:

There are two big problems [with proxy].  The first is that the members who don’t attend the meeting do not hear the discussion and may have marked their proxy based on misinformation or no information at all.  The second problem is that one person can collect many proxies, and if they are general proxies, can influence the outcome of the vote.  Members are basically giving their rights away to another to decide for them. (5)
Shareholders and unit owners should be told how the proxy holders intend to vote, so that the issuance of proxies becomes a process of informed consent. (2)
If the shareholder or unit owner whose proxy is being sought is not comfortable with one or more of the designated proxy holders, he may make the appropriate deletions (initializing the changes) or simply substitute his own designated proxy holder. (2)
It's important to be aware that pre-dated proxy forms reflecting the day of the meeting or the day before the meeting are sometimes circulated. These proxies are illegal because they curtail the right to revoke a proxy before the meeting. (2)

In its simplest form, a Proxy Voting Authorization could be, but should be very clear as to dates and intent:
{Name of the company or association}
{Date of notice}
I, _______________________ (member), authorize ______________________ (person to represent my vote) to vote ___________________ (my selection on the matter of the vote), on my behalf (in proxy) on the subject of ______________________.
{Date proxy vote counted}
{Date proxy voting expires}
References:
(1) https://www.boardeffect.com/blog/board-meeting-proxy
(2) https://cooperator.com/article/voting-by-proxy/full
(3) Floyd M Riddick and Miriam H. Butcher, Riddick’s Rules of Procedure,Maryland: Madison books, page 155
(4) Joyce L. Stephens,  Guide for Voting,  Florida: Fredrick Publishers, 1993  page 51
(5) http://www.parli.com/newsletter/proxy-voting
Other references:
http://www.x12.org/forms/member-proxy-authorization-form
https://www.sec.gov/rules/final/ia-2106.htm
https://medium.com/legalthingsone/ricardian-contracts-legally-binding-agreements-on-the-blockchain-4c103f120707

On hold pending completion of work on system contract.

@wanderingbort @heifner I am presuming that most of this task has been incorporated and that the remaining uncovered portion is OBE.  If I don't hear from you I will presume that is the case.

Some of this has been implemented and the rest is OBE (Overcome By Events).


elasticsearch image not available

Expected behavior
to download elasticsearch image
Actual behavior
error while download
Information about the Issue
(HTTP code 404) unexpected - {"message":"manifest for elasticsearch:latest not found"}
Steps to reproduce the behavior

...
...

Dupe of #4171.


event.body is empty when using kafka-connector

I am using kafka-connector to trigger a function but the body is always empty. I set RAW_BODY to true but it is still empty.
Is there another way I can try to solve this issues ?
here is the log of the function request:
{
    "body": {},
    "headers": {
      "host": "transform.openfaas-fn.svc.cluster.local:8080",
      "user-agent": "Go-http-client/1.1",
      "transfer-encoding": "chunked",
      "accept-encoding": "gzip",
      "x-forwarded-for": "<IP_ADDRESS>:58756",
      "x-forwarded-host": "gateway.openfaas:8080"
    },
    "method": "POST",
    "query": {},
    "path": "/"
  }
}

Hi the template you should be using is node12, can you switch please?
I don't believe that this template supported the raw body anyway.
Alex

Which one is it ? its not under this organization

I would encourage all users to make use of the documentation that we've provided and Google.
https://docs.openfaas.com/cli/templates/#nodejs-12-node12-of-watchdog-template
node12 is an official template and also in the template store. Please read the documentation.

Ofcourse I did read the documentation but the information is all over the place. Its really hard to follow.
I am using of-watchdog, in incubator you have templates listed which are using of-watchdog, there you have only node10.
You have another organization which is really confusing, that contains the old watchdog templates. There you have node12 template. I compared both code and the only difference is node12 std watchdog version uses Promises to handle the function code. The rest is the same.
This problem happens when using both of the templates with of-watchdog. I've added ENV buffer_http="true" to the dockerfile without any luck.

I solved my problem by bypassing the bodyparser. If anyone has the same problem, you can find more info here: https://stackoverflow.com/questions/18710225/node-js-get-raw-request-body-using-express/21222540#21222540

Of course I did read the documentation but the information is all over the place. Its really hard to follow.

I'm sorry I have no idea what you are talking about there. Can you elaborate?
The information is only in one place, in the docs which you can access from openfaas.com - the page below says to use the node12 template and that node10 is deprecated by nodejs.org.
https://docs.openfaas.com/cli/templates/#nodejs-12-node12-of-watchdog-template

I solved my problem by bypassing the bodyparser. If anyone has the same problem, you can find more info here: https://stackoverflow.com/questions/18710225/node-js-get-raw-request-body-using-express/21222540#21222540

We have already solved this problem, if you read the documentation more carefully you will see a RAW_BODY parameter which is only available on the node12 template. The effect of it? To bypass the body parser.
See below:
https://docs.openfaas.com/cli/templates/#nodejs-12-node12-access-to-the-raw-body


Linux distros that work best for maximo-docker?

Hello, can you explain which Linux distro you tested docker with? Would Red Hat 7 work? I apologize if this is a silly question because docker should really abstract the OS level right?

I've tested on Ubuntu 16.04, Docker for Windows and Mac. I'd recommend Ubuntu because its performance is better than Windows and Mac due to without Hypervisor layer like Hyper-V.

I have also ran it on Ubuntu 16.04 with good results.


Tooltip hover over bars (feasibility)

Would it be easy to give bar charts a feature analogous to PointLabelTooltip? Hovering over a bar would make the tooltip appear.

You can do this with the LineLabelTooltip:
N = 10
bars = plt.bar(np.arange(N), np.random.normal(size=N))

for i, bar in enumerate(bars.get_children()):
    tooltip = mpld3.plugins.LineLabelTooltip(bar, label=str(i))
    mpld3.plugins.connect(plt.gcf(), tooltip)

mpld3.display()

It could be worth having a BarTooltip plugin that makes this easier.

Thanks for the tip.

Hi Aflaxman,
I was struggling to add tooltips to the bars using PointHTMLTooltip. After replacing it by LineLabelTooltip and understanding that bars are composed by rectangle patches it worked!
Thank you very much for that...
One more question though... How can add a customizable ccs for the LineLabelTooltip plugin? I would like to format the tooltips as left arrows (.tooltip .tooltiptext::after).
I PointHTMLTooltip I can pass the css but in LineLabelTooltip this option is not available...
Thanks

Replacing LineLabelTooltip by LineHTMLTooltip and wrapping the label in tooltip html tags worked.
Like:
label="
"+ thisLabel + ""


Move flake8 tests to top first

It's rather annoying to have all of the actual code tests pass, only for CI to fail due to flake8 complaining.
This PR rearranges the order of tests so Travis executes the flake8 tests first. This should help speed up PRs that pass code tests but fail flake8.
I also update the README to remove the "unmaintained" status of the project, since I'm now the maintainer.

CI tests were run on this branch here: https://travis-ci.org/pipermerriam/flex/builds/492300752


Can't read devices: Telnet with password don't supported

Sometimes suddenly can't connect to the xiaomi multimode gateway, prompt：Can't read devices: Telnet with password don't supported

Traceback (most recent call last):
File "/config/custom_components/xiaomi_gateway3/core/gateway3.py", line 546, in _get_devices
shell = TelnetShell(self.host)
File "/config/custom_components/xiaomi_gateway3/core/shell.py", line 56, in init
raise Exception("Telnet with password don't supported")
Exception: Telnet with password don't supported

@AlexxIT Boss, please help me see what the problem is

getting the same error today

https://github.com/zvldz/mgl03_fw/tree/main/firmware
downgrade firmware its working back

@mytering thank you, I will try it

@mytering when I entering the third command, there is no thing show up. None list I can choosee

@mytering what port did you use to connect to your gateway?
When I try to connect to my gateway via PuTTY with port 22 I get the username/password prompt. But when only entering admin for rlxlinux login and no password I get a Login incorrect error.

try 123123 the newer firmware had a password

Thanks for the quick reply!
123123 was the password that previously worked for me, but it seems that they've changed the password to "admin" with firmware update 1.5.0_0027 :/

Duplicate #370


Initial date value

How do I set the initial value for the DatePickerInput. When I try to do this, when I try to open a modal with a date picker, I get undefined is not a function?

Feel free to check out the docs for the DatePickerInput. It has a working example.

[here I am trying to pass the initial value for the date
     useEffect(() => {
        if (item) {
            setValue("date", dayjs(item.date) || undefined, { shouldValidate: false });
        }
    }, [item]);

                     <Controller
                        control={control}
                        name="date"
                        rules={{ required: true }}
                        render={({ field: { onChange, value } }) => (
                            <DatePickerInput
                                label="Дата"
                                value={value}
                                locale="ru"
                                mode="outlined"
                                inputMode="start"
                                withDateFormatInLabel={false}
                                onChange={onChange}
                            />
                        )}
                    />
```](url)

My recommendation would be to get a simplistic example working such as the one in the docs. This would rule out the issue is with your setup in particular.

in the documentation, I see that they are passing undefined, but I don’t see that it shows how to pass any date

I updated the snack https://snack.expo.dev/@fitzwabs/react-native-paper-dates-input


Cluster-autoscaler: add get nodes function to cloud provider interface

This is needed to compare the list of nodes created by the cloud provider with the list of nodes registered in Kubernetes.
Ref: #2228 #2229
cc: @jszczepkowski @andrewsykim @piosz @fgrzadkowski

This change is

LGTM (after resolving comments)


[SPARK-44983][SQL] Convert binary to string by to_char for the formats: hex, base64, utf-8

What changes were proposed in this pull request?
In the PR, I propose to re-use the Hex, Base64 and Decode expressions in the ToCharacter (the to_char/to_varchar functions) when the format parameter is one of hex, base64 and utf-8.
Why are the changes needed?
To make the migration to Spark SQL easier from the systems like:

Snowflake: https://docs.snowflake.com/en/sql-reference/functions/to_char
SAP SQL Anywhere: https://help.sap.com/docs/SAP_SQL_Anywhere/93079d4ba8e44920ae63ffb4def91f5b/81fe51196ce21014b9c6cf43b2666698.html
Oracle: https://docs.oracle.com/en/database/oracle/oracle-database/19/sqlrf/TO_CHAR-number.html#GUID-00DA076D-2468-41AB-A3AC-CC78DBA0D9CB
Vertica: https://www.vertica.com/docs/9.3.x/HTML/Content/Authoring/SQLReferenceManual/Functions/Formatting/TO_CHAR.htm

Does this PR introduce any user-facing change?
No. This PR extends existing API. It might be considered as an user-facing change only if user's code depends on errors in the case of wrong formats.
How was this patch tested?
By running new examples:
$ build/sbt "sql/test:testOnly org.apache.spark.sql.expressions.ExpressionInfoSuite"

and new tests:
$ build/sbt "test:testOnly *.StringFunctionsSuite"

Was this patch authored or co-authored using generative AI tooling?
No.

All GAs passed. Merging to master.
Thank you, @HyukjinKwon @cloud-fan for review.


Interactions in converters

Summary
Pull request adding interaction support to converters
Checklist

[x] If code changes were made then they have been tested.

[ ] I have updated the documentation to reflect the changes.
[ ] I have run task pyright and fixed the relevant issues.

[ ] This PR fixes an issue.
[x] This PR adds something new (e.g. new method or parameters).
[ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
[ ] This PR is not a code change (e.g. documentation, README, ...)

Why is this needed? Application Commands have their own converters.

It might be better to utilise OptionConverter since that is designed for application commands, instead of retroactively applying to ext.commands.

[x] If code changes were made then they have been tested.

I'm also not too sure if you did in fact test this, since the pyright issues show this will not work in some cases.

OptionConverter already takes in an interaction argument though, in its convert method.

OptionConverter already takes in an interaction argument though, in its convert method.

As in, providing default converters.


The timeout set by httpsm may be not work on client side using SSL

In SSLNetVConnection.cc ,we see this:
int
SSLNetVConnection::sslStartHandShake(int event, int &err)
{
  if (TSSystemState::is_ssl_handshaking_stopped()) {
    Debug("ssl", "Stopping handshake due to server shutting down.");
    return EVENT_ERROR;
  }
  if (sslHandshakeBeginTime == 0) {
    sslHandshakeBeginTime = Thread::get_hrtime();
    // net_activity will not be triggered until after the handshake
    set_inactivity_timeout(HRTIME_SECONDS(SSLConfigParams::ssl_handshake_timeout_in));
  }

In these code ,we reset the inactivity_timeout to SSLConfigParams::ssl_handshake_timeout_in
but the default value of SSLConfigParams::ssl_handshake_timeout_in is 0,this means we set the inactivity_timeout to 86400 seconds(1 day).
In my opinion,  this code should be used only on server side.
Classicly,we set the inactivity timeout of sslnetvc before it's handshake,but now we reset it,in some situation, for example,bad net work,we can't read the packet, the vc will never be trigger with a write signal, then the vc will not be closed for 1 day,it may cause lot of CLOSE_WAIT.

Sorry for my bad english~

This was fixed in #6781, thank you!


config capture-all-dns via env ISTIO_META_DNS_CAPTURE_ALL

Please provide a description of this PR:
support config capture-all-dns via env ISTIO_META_DNS_CAPTURE_ALL

Hi @liuxu623. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

can you give more info why? This will not work in many environments

@howardjohn We'd like to make CNI and init-container use same iptabels rules, but CNI capture-all-dns is true, we couldn't set capture-all-dns when use init-container.

And sometimes app may use other DNS Server not in /etc/resolv.conf，this PR can config capture dns traffic to other DNS Server.


Update to openjdk 12ea19

Motivation:
We should test against latest EA releases.
Modifications:
Update to openkdk 12ea19
Result:
Use latest openjdk 12 EA build on the CI.

Let me merge this now... Its just a java version bump.


[RV_DM] rv_dm_jtag_dtm_hard_reset_vseq

This test verify that after performing the operation of hard reset the debug module still responds correctly. This test was failing in regression due to this mistake so i modified it.

@jdonjdon


task(#536): add bookings to review badge onto navbar

IMPORTANT: Always create an issue before a PR and provide enough information so that others can review

Explain the details for making this change.
What existing problem does the pull request solve?

Adds a badge next to the bookings -> review link with the counts of bookings the logged in user has to review.

Test plan (required)
Demonstrate the code is solid.  Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI.

nothing significant code changes = no new code to cover

Closing issues
List all issues this PR resolves

closes #536

Pre-Merge checklist
Complete these items before requesting reviews

[x] Static Analysis Rules Validated
[x] All commits follow naming conventions

Sub-tasks Checklist

[x] UI Implementation
[ ] UI Test
[x] Backend Implementation
[ ] Backend Tests
[ ] Integration Tests
[ ] System Tests
[ ] Documentation

The code makes me think that there'd be no badge if there are no bookings to review, but in your screenshot the badge says 0.
Will the red badge be there if the user has no bookings assigned to them for review?

Yeah, I kind of disabled the v-if check so I can take a quick screenshot. But you're absolutely right, the badge will only show up when there are items to review.


[webapi] Geolocation Denied Automation

Impacted tests(approved): new 0, update 3, delete 0
Unit test platform: Crosswalk for Android 16.44.395.0
Unit test result summary: pass 3, fail 0, block 0

@Honry I have upgraded copyright following your comments

LGTM


feat: Create a relationship schema

What does this PR do?
Related ticket
Fixes #75
Type of change

[ ] Chore
[ ] Bug fix
[x] New feature
[ ] Documentation update

Check list

[x] Unit tests for any smart contract change
[ ] Contracts and functions are documented

Codecov Report

Merging #155 (132447f) into dev (77a4e2b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #155   +/-   ##
=======================================
  Coverage   96.62%   96.62%
=======================================
  Files           8        8
  Lines         148      148
  Branches       37       37
=======================================
  Hits          143      143
  Misses          4        4
  Partials        1        1

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


fix a bug

fix: fs.createReadStream may throw error ENOENT: no such file or directory, when multi process handle same log file

Great fix proposal, could we make this a non blocking invocation and still avoid dead-lock conditions? Maybe fs.stat() could be handy at this point as a promise to avoid the nature of compressing getting an additional overhead.

now , i  replaced fs.existsSync with try catch


adds a test case for testing module location in file manager

Description
Adds a test case for adding module location in JCT file manager.
Issues
contribution towards #270

Codecov Report

Merging #272 (3d45d06) into main (1cb4e14) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #272   +/-   ##
=======================================
  Coverage   71.17%   71.17%
=======================================
  Files          74       74
  Lines        2560     2560
  Branches      238      238
=======================================
  Hits         1822     1822
  Misses        671      671
  Partials       67       67

Since this flow hits this line of code: https://github.com/ascopes/java-compiler-testing/blob/main/java-compiler-testing/src/main/java/io/github/ascopes/jct/filemanagers/impl/JctFileManagerImpl.java#L97, do we want to test that the modules get detected correctly too?
This might be a bit more complicated to test, since ModuleFinder is part of the JRE and looks for nested directories that contain a module-info.class inside them.
What you could do to avoid having to make a bunch of files and classes in the test case is make a static mock of ModuleFinder... this is a bit involved but bare with me.
So we want to:

mock ModuleFinder.of() to return a fake stub that we control so we can manipulate how it behaves and verify certain method calls are made.
mock the fake stub module finder so .findAll returns some set of module references we control.
make a fixture so we can make ModuleReference objects easily.

The fixture is going to be the easiest one. There is a static class called Fixtures in the helpers package in the tests. We want to make a method to take a Path that we provide and return some ModuleReference that we mock.
Something like this should work:
static ModuleReference someModuleReference(Path path) {
  var ref = mock(ModuleReference.class);
  when(ref.location()).thenReturn(path.toUri());
  return ref;
}

The mocking of ModuleFinder will be a bit more complex.
// Replace ModuleFinder's static methods
// with some that we programmatically stub.
try (var moduleFinderMock = mockStatic(ModuleFinder.class)) {

  // This will be what we return from
  // ModuleFinder.of(...);
  var moduleFinder = mock(ModuleFinder.class);

  // Make a stub.
  // When I call ModuleFinder.of(...)
  // Then return our ModuleFinder mock.
  moduleFinderMock
      .when(() -> ModuleFinder.of(any())
      .thenReturn(moduleFinder);

  // Stub the result of .findAll()
  // When I call .findAll()
  // Then return a set of module references
  // to some module paths we make.
  var modulePath1 = somePath();
  var modulePath2 = somePath();
  var modulePath3 = somePath();

  when(moduleFinderMock.findAll())
      .thenReturn(Set.of(
          someModuleReference(modulePath1),
          someModuleReference(modulePath2),
          someModuleReference(modulePath3)
      ));

  // Your logic in this PR goes here <--

What we can then do is assert that the expected paths are present in the result by getting the module container group for the location in the file manager, and then querying the result.
It might be simpler to also consider mocking the construction of the ModuleContainerGroupImpl class and just verify that .addModule() is called with the arguments you expect via Mockito.
This is probably going to be the most complex class in the API to mock since there is a tonne of integration with lots of other moving parts here. The other place that does a lot of this which may be of interest to see how I dealt with testing that is at https://github.com/ascopes/java-compiler-testing/blob/main/java-compiler-testing/src/main/java/io/github/ascopes/jct/compilers/impl/JctJsr199Interop.java, the corresponding tests are at https://github.com/ascopes/java-compiler-testing/blob/main/java-compiler-testing/src/test/java/io/github/ascopes/jct/tests/unit/compilers/impl/JctJsr199InteropTest.java#L148

@ascopes  Thank you so much for your valuable inputs! :)

Just a note that #279 changes the structure of some stuff that interacts with code in this PR to try and simplify some of these interactions a bit from a testing perspective. If you see any conflicts as a result of that, then that is my fault and just shout if you need help resolving anything. Probably won't be for a little while until it gets merged as there are still tests to write for it and I am working all week so I may not have time to finish it just yet.

closed per #270 comments


Fix 500 error on repos with no tags

#11846 Introduced feature to show exact tag on commit view. However if a repo has no tags at all git prints out a separate and unhandled error " No names found, cannot describe anything.":
https://github.com/go-gitea/gitea/blob/bc4f7ba69b01c6f10f6ea26325bf61485adaa0ff/modules/git/commit.go#L490
Adding --always to the command makes it always use the error in the style of "fatal: no tag exactly matches" even if there are no tags at all.
Fixes #11869
Fixes #11868

I wonder why we even call GetTagName when no tags exist?

I believe we don't know if a repo has tags or not in this context and if you can run a single command to both find that out and print the tag if so it's better than running two (one to look for tags in general, one to check commit for tag).

You're right. This does fix the issue by causing git to trigger the other (expected) error:
$ git describe --tags --exact-match --tags HEAD
fatal: No names found, cannot describe anything.
$ git describe --tags --exact-match --tags --always HEAD
fatal: no tag exactly matches '148269db9f5ce7e81c29136a73069ad518dad779'

I think we actually want to ignore errors printed to stderr for both GetBranchName and GetTagName, that way we're also not dependant on matching error strings.

Yes I suspect a more robust error handling not relying on a string is better (I know we do this in a lot of places with git).
This was just quick fix to avoid 500 for many commits

There's no other way to handle git errors I'm afraid. That's why I spent so long to force them to always be in English.

In some cases we do care about the error but in this case we probably don't. If there are no tags, we don't care about why git can't find them. I was thinking about either adding a boolean flag ignoreErrors to GetTagName and GetBranchName that would omit passing err if given.

Thanks for the fix, really annoying


Update gulp tasks to output both unminified and minified in one file.

:+1: Thanks!

When this is merged we should change the main property of bower.json to have the unminifed files listed there as that is recommended by bower: https://github.com/bower/bower.json-spec

@Dervisevic :+1:


Optimize random location picking

Interesting way of retrieving a specified amount of random items from a collection!
I'm not sure though if GUID is the right choice here, since it reprecents something unique, not random.
Although I like the Take, OrderBy would execute deferred but evaluate eagerly, so we would still have to order the entire collection, regardless of how many we extract - I made this mistake at some coding challenge ;-(
Originally posted by @Flash0ver in https://github.com/Flash0ver/F0.Minesweeper/pull/17#discussion_r522248410

Closing: implemented two more location pickers via issue #65 in PR #93.


[BUG] $post->meta() dont load values of clone field type

Expected Behavior
When use $post->meta('clone_field') need to get all values from that clone field type and their children like below
array(
	'key' => 'value',
	'key2' => 'value2',
)

Actual behavior
Now if we use $post->meta('clone_field') the returned value is null like below.
NULL

Steps to reproduce behavior

I just upgrade my timber 1.0 to 2.0 and i discovery this, i have several ACF groups who act as template schema for certain component with clone field by acf

Notes
No response
What version of Timber are you using?
2.0
What version of WordPress are you using?
Wordpress 6.4.2
What version of PHP are you using?
PHP 8.1.26
How did you install Timber?
Installed or updated Timber through Composer

I discovered another bug, actually this bug is global, it doesn't take well the values of a field type group
I mean that any group type field has a number of children and they do not appear when you use $post->meta('field_group')
NULL is always returned to us, to overcome this aspect we must use $post->meta('GROUP_CHILDREN'), 'GROUP' means the name of the field, 'CHILDREN' means the name of the child in that group

Hi @fgdaniel ,
When creating a ACF field group for posts, add a group field named 'group', add a sub field named test, fill in the value and them in the index.php:
$timber_post = Timber::get_post(); var_dump($timber_post->meta('group'));
I do get the correct values of the sub fields. Do you run Timber::init(); ?

Hi @Levdbas
Here is my entire code with comments
<?php
/*
Template Name: eBooks - Template
 */
use Timber\Timber;

global $paged;
if ( ! isset($paged) || ! $paged) {
	$paged = 1;
}
$context          = Timber::context();
$post             = Timber::get_post();
$context['post']  = $post;
$context['posts'] = Timber::get_posts(array(
	'post_type'              => 'ebooks',
	'posts_per_page'         => 12,
	'paged'                  => $paged,
	'no_found_rows'          => false,
	'update_post_term_cache' => false,
	'update_post_meta_cache' => false,
));
$context['hero']  = $post->meta('hero'); // RETURN NULL
// $context['hero']  = get_field('hero'); // RETURN ALL FIELDS ON THIS GROUP

query_monitor_debug($post->meta('hero'));
// RETURN NULL

query_monitor_debug(get_field('hero'));
// RETURN Array
// (
//     [] =>
//     [titlu] => eBook-urile GoostoMix, ghidurile tale pentru sănătate
//     [descriere] => Un ajutorul nesperat de care ai nevoie în viața de zi cu zi și în momentele lipsite de inspirație. eBook-urile GoostoMix sunt un adevărat ajutor.
//     [background] => Array
//         (
//             [ID] => 12250
//             [id] => 12250
//             [title] => ebooks-jumbotron-bg
//             [filename] => ebooks-jumbotron-bg.jpg
//             [filesize] => 64066
//             [url] => https://dev.itup.ro/goostomix2/wp-content/uploads/2023/09/ebooks-jumbotron-bg.jpg
//             [link] => https://dev.itup.ro/goostomix2/ebooks/attachment/ebooks-jumbotron-bg/
//             [alt] =>
//             [author] => 1
//             [description] =>
//             [caption] =>
//             [name] => ebooks-jumbotron-bg
//             [status] => inherit
//             [uploaded_to] => 12116
//             [date] => 2023-09-11 08:29:45
//             [modified] => 2023-09-11 08:29:45
//             [menu_order] => 0
//             [mime_type] => image/jpeg
//             [type] => image
//             [subtype] => jpeg
//             [icon] => https://dev.itup.ro/goostomix2/wp-includes/images/media/default.png
//             [width] => 1088
//             [height] => 500
//             [sizes] => Array
//                 (
//                     [thumbnail] => https://dev.itup.ro/goostomix2/wp-content/uploads/2023/09/ebooks-jumbotron-bg-150x150.jpg
//                     [thumbnail-width] => 150
//                     [thumbnail-height] => 150
//                     [medium] => https://dev.itup.ro/goostomix2/wp-content/uploads/2023/09/ebooks-jumbotron-bg-300x138.jpg
//                     [medium-width] => 300
//                     [medium-height] => 138
//                     [medium_large] => https://dev.itup.ro/goostomix2/wp-content/uploads/2023/09/ebooks-jumbotron-bg-768x353.jpg
//                     [medium_large-width] => 768
//                     [medium_large-height] => 353
//                     [large] => https://dev.itup.ro/goostomix2/wp-content/uploads/2023/09/ebooks-jumbotron-bg-1024x471.jpg
//                     [large-width] => 1024
//                     [large-height] => 471
//                     [1536x1536] => https://dev.itup.ro/goostomix2/wp-content/uploads/2023/09/ebooks-jumbotron-bg.jpg
//                     [1536x1536-width] => 1088
//                     [1536x1536-height] => 500
//                     [2048x2048] => https://dev.itup.ro/goostomix2/wp-content/uploads/2023/09/ebooks-jumbotron-bg.jpg
//                     [2048x2048-width] => 1088
//                     [2048x2048-height] => 500
//                     [featured-image] => https://dev.itup.ro/goostomix2/wp-content/uploads/2023/09/ebooks-jumbotron-bg.jpg
//                     [featured-image-width] => 540
//                     [featured-image-height] => 248
//                 )

//         )

// )

Timber::render( 'archive/ebooks.twig', $context );

I attach some images for better understand
Image with query monitor logs: https://imgur.com/i2cRZ3t
Image with ACF Custom Fields details on Post Edit: https://imgur.com/Ccf2Fls
Image with eBook fields acf group: https://imgur.com/G3DA514
Image with Component Hero acf group: https://imgur.com/JafBSRh
On timber 1.0 when you call $post->meta('acf_field') who has several children fields the return value are an array with that specific childrens, now only NULL return,

OMG i was stupid, the problem was Timber\Timber::init(); i dont include it... RIP... now works fine..... i'M VERY SORRY FOR MY SUPPORT REQUEST... i know i'm stupid...


sep/025: Add task to fix sepolia fp upgrade

Description
Adds task to fix the Sepolia FP upgrade, since the old one (https://github.com/ethereum-optimism/superchain-ops/pull/374) referenced a wrongly newly deployed DelayedWETH implementation.
Also adds a framework for creating reusable verification scripts.
Tests
Additional context

Metadata
Towards https://github.com/ethereum-optimism/optimism/issues/13033

fyi the 025 task number is used and now executed by https://github.com/ethereum-optimism/superchain-ops/pull/410

I just realized that this task may have become obsolete by https://github.com/ethereum-optimism/superchain-ops/pull/410 - in this case, I'll change this task to only add the verification framework, but will delete the task sep/026 itself. @mds1 @Inphi @mbaxter

Rebased on top of the framework-only PR https://github.com/ethereum-optimism/superchain-ops/pull/429 and squashed commits. Reduces the diff to only the actual task 026.

Going to switch the FDG and PDG implementations to new MT-variants that @mbaxter deployed

FDG: 0x833a817ef459f4ecdb83fc5a4bf04d09a4e83f3f
PDG: 0xbbd576128f71186a0f9ae2f2aab4afb4af2dae17


Sam to provide the necessary approved design assets to dev team

In order for the team to get started, Sam needs to deliver the approved design assets to the dev team no later than end of day Monday July 27.
There will be five pages:

Home
Who We Are
What Is ThreeFold
Our Philosophy
Ecosystem

We will re-use assets as much as possible.
For context, here is the working mockup: https://www.figma.com/file/jhZQXxc1kmlX5RfhTPDhuE/ThreeFold-Web-Presence-Architecture?node-id=1%3A2

Here are the updated design files from Zia to the Figma document. He is providing the AI files shortly.
The pages are very basic and only have text and images with a few buttons. If the 5 short pages are too much to create in 2 days, then I can combine into a one-pager for now and we remove everything else. Please let me know estimate and whether I need to provide an updated one-pager before the AI file comes over from Zia. Thank you!


What's the benefits of using YARN as kuber's scheduler?

Sorry to say that but I found no benefits in kubernetes-yarn integration ... If we just make yarn as kuber's scheduler ....
Or, in this case, yarn can run hadoop jobs in dockers created by kuber??

@resouer YARN-1964 adds support for running docker containers natively in YARN - it is orthogonal to Kubernetes-YARN. Also YARN-1964 is completely unrelated to spark.

OK, I think I have got your basic idea. Thanks a lot!


Set Per-Challenge Options

Following up on #66
Options that would be good to have per-challenge

Default zoom level
Min - Max zoom level
Default tile layer (select from MapRoulette choices)
Custom tile layer (enter URL template)
Text for 'False Positive' button
Initial UI state (collapsed or expanded)
Initial popup state (visible or hidden)
Custom popup text / markdown (perhaps use placeholders to populate with property values)

Also, a contact email (this should be settable at project level and perhaps overridable at challenge level)

The custom tile layers are definitely the highest value item in this list

The options that were not included in #102 where:
Initial popup state (not sure what this is actually)
Text for false positive
Custom popup text / markdown (would need a little more information about this)
Initial UI state (I am guessing this is collapsing the sidebar in the UI, but not 100% sure)

Ignore last PR, it was supposed to be for issue #92

@mgcuthbert the initial popup state is whether the leaflet information popup for the geojson geometry is by default not visible (the default now) or visible. In some cases where challenges rely on the feature properties it may be preferable to have these expanded / visible by default.
For custom popup text, this is regarding the same leaflet feature popup. Folks may want to override the default display of the feature properties with the value of one particular property.
Initial UI state is in fact whether sidebar(s) are collapsed or expanded.

Ok perfect, thanks for the clarification. All that makes sense.

Changed ticket to a checklist. I think the remaining items are really nice to have but not immediately essential. Labeling P2


Can't work in my system

I cloned this repo and put in my .config/nvim/pack/plugins/start/ and used the default configuration and i get the default colors of neovim without any theme even lualine is the default theme.
You need any log of me i be grateful to help i really like this project.

I assume you activated the theme as well? I use Plug to install and it all works perfectly for me.
local neopywal = require("neopywal")
neopywal.setup()
vim.cmd.colorscheme("neopywal")

Honestly i could not replicate the issue, it seems to work fine for me when i install the plugin on that exact same path and run :colorscheme neopywal.
And about lualine, honestly i couldn't even get lualine to load with that ~/.config/nvim/pack method at all, so i am not sure how i am supposed to test it, but one thing you can try to do is changing the theme lualine option to auto instead of explicitly setting it to neopywal. That should make lualine try to load which ever theme is avaliable at the moment, and running :colorscheme neopywal should tell it to load that theme automatically.

Sorry i just forget to add vim.cmd.colorscheme("neopywal") in the config


Improve clicking outside of fields (MenuField, MultiSelectField, etc) when on Dialog/Drawer

See example using MenuField within Drawer
https://github.com/user-attachments/assets/04ab1f34-f54e-4359-83de-f2044c95ac71
See also discussion regarding MultiSelectField with Dialog
Likely the culprit is the event.stopPropagation() but there is also some coordination with Popover to not break when doing so.

Any news about this?

Any news about this? I want to hide a popover when someone clicks outside, but it doesn't seem to work inside a Drawer.

@sergejbog News flash: This just in... fixed in 0.75.3 via #499.
I originally had stopped event propagation to handle some unexpected triggering of nested models (Menu/Dialog/Drawer, etc), but I could not identify any reasons to keep these in the current state.
Please let me know if you spot any regressions, but I did a fair bit of manual validation and couldn't identify anything, and fixes the Menu click outside use case
https://github.com/user-attachments/assets/acf469fd-96de-4141-93af-3c94e544fb30


Readuce minimum direct memory size from 75m to 16m

@jonmv @bjorncs @hmusum PR
Netty is very hungry for buffers and is not shy.
So for small nodes it is hard to constrain memory usage when most of it is due to the fixed component.
The default stems from 2004/2005 when heap size default was 1536m....


ng g route should also add the route to the RouteConfig

Tasklist:

[ ] add a angular-cli/router-config.ts to the scaffold. This is part of the project. The content of this file should have a comment at the top to say to not touch this file, and export a CliRouteConfig (open to name suggestions).
[ ] add a README.md to the angular-cli directory to explain that this is generated code. We will use this for other things such as providers and third party libraries.
[ ] import the CliRouteConfig in the default src/app/__name__.ts. The code should look something like [1].
[ ] ng generate route needs to add the route info to the router-config.ts. This includes importing the new route and adding it to the CliRouteConfig array.
[ ] ng generate route should have a flag --no-route-generation (open to suggestions) that avoid the addition of it to the CliRouteConfig array.
[ ] README.md documentation for this.
[ ] e2e tests for it.

[1]
@Component({
  selector: '<%= htmlComponentName %>-app',
  providers: [],
  templateUrl: 'app/<%= htmlComponentName %>.html',
  directives: [ROUTER_DIRECTIVES],
  pipes: []
})
@RouteConfig([

].concat(CliRouteConfig))
export class <%= jsComponentName %>App {
  defaultMeaning: number = 42;

  meaningOfLife(meaning?: number) {
    return `The meaning of life is ${meaning || this.defaultMeaning}`;
  }
}

I'm hesitant to have the configuration of routes in a separate file. Is that a convention that we want to convey via the CLI?
This solution does not scale enough to provide the ability to create routes anywhere else in the application, only at the root. There are going to be cases where internal components need to configure their own routes and that should be accomplishable via the CLI.

I second the routes-anywhere concern voiced by @Brocco. Perhaps having child routes is fine as a future enhancement though, as top level routes cover the most common scenarios.
But I agree that we need a place for cli-generated code that is completely under our control. That location needs to be part of the project, so angular-cli/ sounds as good as any.
As an aside, we already have a config/ folder that seems to be used for ember-cli env and path location config. Perhaps we want to piggyback on it?
I do have a recommendation though: since altering/regenerating that file involves complex, error prone typescript code parsing, we should instead generate it from json based config file. Not to mention that, were a user to inadvertently alter this file, the cli would possibly mangle the file due to flimsy parsing rules.
We will also need something similar to configure app-wide providers (like the ones ng install should manage), so I strongly feel we should move to config-based file generation instead of code parsing.
Consider a angular-cli.json file, that among other configuration items, contains this:
(...)
routes: [
 {
    routePath:'/hero/...',
    component: 'HeroRoot'.
    componentPath: './hero/hero-root.component'
  }
],
(...)

From this it is trivial to generate the needed router-config.ts, perhaps even using a blueprint:
import {HeroRoot} from './hero/hero-root.component';

let CliRouteConfig = [
  {path:'/hero/...', name: 'HeroRoot', component: HeroRoot}
];

default export CliRouteConfig;

Child routes is not a concern for this issue, it's a separate issue that we need to address when doing child routes anyway.
We cannot piggyback on config/ because it's outside the src/ directory.
We cannot use JSON for this as it is not IDE friendly, unfortunately. That was my first idea.
The other solution is changing the app.ts itself. This requires parsing TypeScript and figuring out where. @zackarychapple I can help you with that if you want to go down that route.
Alternatively, we can have the simple solution first (external file), then implement the app.ts as a phase 2 project. WDYT?

I think that directly modifying components directly is the appropriate approach here.
It hides nothing from the user and they do not need to look into a different file to see the routes that are available inside a given component.

I think perhaps I didn't explain myself properly. My strategy was to use the json file to generate the typescript file. There would always be a real code file that the IDE could use and trace.
The only difference is that, when you needed to alter it, you'd re-generate it from the json data. This is much, much better than altering by parsing typescript.
Unless I'm missing something here, having the external file will always imply parsing typescript, since that file is a typescript file and it needs to import the routable components.

I made a proof of concept PR to demo what I was suggesting. See #292.
Running ng new testproj gives you the following two new files:
./src/angular-cli/route-config.ts
// DO NOT EDIT THIS FILE
// IT IS AUTO GENERATED BY ANGULAR-CLI

export const CliRouteConfig = [

];

./angular-cli.json
{
  "routes": []
}

After running ng g route hero, they have the following content:
./src/angular-cli/route-config.ts
// DO NOT EDIT THIS FILE
// IT IS AUTO GENERATED BY ANGULAR-CLI
import HeroRoot from '../app/hero/hero-root.component';

export const CliRouteConfig = [
{path:'/hero/...', name: 'HeroRoot', component: HeroRoot},
];

./angular-cli.json
{
  "routes": [
    {
      "routePath": "/hero/...",
      "component": "HeroRoot",
      "componentPath": "../app/hero/hero-root.component"
    }
  ]
}

This approach has the following benefits:

fully blueprint based
doesn't need any modification of the build process
always has 'real' code files and thus is IDE/manual compilation safe
no messy TS file parsing,
route-config.ts is never read and always re-generated (thus there is risk of breaking the project after adding a route like what happened to @hansl once while testing ng install),
route config parameters kept safe and separately, easy to access during an update procedure
also allows deleting of routes with no TS parsing (much harder to accurately delete code than to add code)
easy to add parameters and operate over other routes. This is important because we will need to support all route definition parameters in this functionality, because users cannot edit it directly. For instance, setting a default route needs to change all others to not be default, and this is needed to initially populate the router outlet.

As a consideration to seamlessly support child routes, route-config.ts could be on the same directory as the file that imports it, instead of being in the separate ./src/angular-cli/ dir.
This way child routes would simply have their own config. It would be trivial to implement child routes using dynamic paths as @Brocco has been implementing.

@filipesilva for child routes would we expect something like this? ng generate route VillanRoot for HeroRoot or maybe ng generate route VillianRoot > HeroRoot.  Thoughts?

I hadn't thought about that until you asked really!
I guess the most important bit is that it needs to be something that unambiguously describes something else as the parent. It also needs to specify the relative location (to ./src) of the parent route, since you can perfectly well have it any depth and even repeated classes.
The parent must default to our defined root component.
As per @Brocco's work on dynamic paths, it should support specifying a path for the component itself and also default to a certain folder if path isn't specified (both for the generated element and the parent). We should use the helper functions he made for this purpose.
Using the normal ember-cli command args, then I suppose the most intuitive approach is:
ng generate route app/folder1/folder2/Villain --parent=app/folder1/folder2/HeroRoot

Where the following two should be equivalent:
ng generate route Villain
ng generate route app/Villain --parent=app/app


JSInterop "always on" in TestContext

Pull request description
Closes #237
PR meta checklist

[x] Pull request is targeting at DEV branch.
[x] Pull request is linked to all related issues, if any.
[x] I have read the CONTRIBUTING.md document.

Content checklist

[x] My code follows the code style of this project and AspNetCore coding guidelines.
[x] My change requires a change to the documentation.

[ ] I have updated the documentation accordingly.

[x] I have updated the appropriate sub section in the CHANGELOG.md.
[x] I have added, updated or removed tests to according to my changes.

[x] All tests passed.

Documentation will be updated later when the other related changes are done.


⚠ Minecraft has degraded performance

In 116726e, Minecraft (https://www.minecraft.net) experienced degraded performance:

HTTP code: 200
Response time: 1005 ms

Resolved: Minecraft performance has improved in 364dcf3.