Introduce Builtin.bindMemory and SIL bind_memory.

Required for SE-0107: UnsafeRawPointer.

@swift-ci Please test and merge.

@swift-ci Please smoke test and merge.

This passed full swift-ci testing on OSX and Linux. But the linux bots are too backed up right now to do the auto-mege.

Just an FYI for everyone. Part of the reason that things are so backed up is that (I believe) a few days ago Ted made the incremental linux smoke test bot non-incremental to work around a build issue. Thus the smoke tests were taking significantly longer than previously. I fixed this.
Michael

On Jul 18, 2016, at 1:18 PM, Andrew Trick<EMAIL_ADDRESS>wrote:
This passed full swift-ci testing on OSX and Linux. But the linux bots are too backed up right now to do the auto-mege.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/apple/swift/pull/3573#issuecomment-233445553, or mute the thread https://github.com/notifications/unsubscribe-auth/AAee36HPxwkeHlipYD9z93WBFEL3p9qMks5qW999gaJpZM4JO5el.

Thanks Michael. Ted's fix was after I requested someone from the working group to simply clear the workspace because I don't have permission to do it and at the time no one seemed to be monitoring  the builds.


Some build dependencies disappeared, updating to newer versions

What this PR does / why we need it:
Reference new build dependencies to fix the build.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:
NONE

/close
Duplicate of #2315


ModuleNotFoundError: No module named 'videoanalyst.data.target'

I ran into this problem when I ran your code.
could you update the complete code?
thank you.

Sorry, I updated the code again. I am not very skilled at github uploading, which leads to failure.

thank you,it's ok.


Hint Text Color

Is there a way to set the hint text color?

I am afraid not, the implementation of the hint is using the Windows API to set style as cuebanner, and there is no way for you to change the fore colour. If you want to do that, just rewrite the class and implement the hint effect manually.


Failed to download junit report

Current behavior

After running an espresso test, the test results are generated. Recently from 0.99.2 version of saucectl, the report generation fails inconsistently.

Desired behavior

JUnit reports should be generated if tests pass.

Config to reproduce

SauceLabs-ReportBug.pdf

Attached is a console output of the saucectl espresso test run

Versions

saucectl version 0.99.2

@gauthampaimk I couldn't determine the root cause for the behavior you are seeing, but I made some changes (to the logging) that should help us troubleshoot this better. Would be great if you could update saucectl to version https://github.com/saucelabs/saucectl/releases/tag/v0.99.4 and run with it for a little while. Should you run into the same issue again, please attach the newly generated logs :)


driver: loapic: add DTS binding for local APIC

As highlighted in #26393, local APIC still used Kconfig based CONFIG_LOAPIC_BASE_ADDRESS. This patch set adds DTS support to local APIC. I/O APIC already uses DTS. Similar to I/O APIC:

I have added a device tree entry in the relevant .dtsi files.
I have also added a binding for rules.

Several Intel x86 architecture define a maximum set of LVT entries for local APIC, hence the reason for adding num-irqs.

Hi @nisarumar, and thanks for the PR! Just checking that you didn't close this by accident?

Hi @kartben,
No this was not by accident. It was failing some test. I will check and re-open soon. Thanks for checking in.

Gotcha! Feel free to leave the PR in Draft state to iterate on it and get CI to run and provide feedback, and only put it out of draft when it's ready for review. Cheers!


Frame Filter POC

To register a frame filter:
# so extension gems don't need to require the entire debugger to register the filter
require "debug/frame_filter"

DEBUGGER__.register_frame_filter do |path|
  # returning true here makes the debugger include the frame
  !path.match?(/library/) # e.g. this rejects any frame with path that matches /library/
end

The filters are applied to:

Control flow commands. For example, pressing step will skip frames with library in its path.
backtrace command. So frames with library in its path will not be displayed in the output. But the displayed frames will keep the original index.

I'm thinking adding backtrace all to show all frames.

The filters are not applied to:

frame, up and down commands. I figure precise frame operations should still be available.

Example
Scripts
# library.rb

def wrapper
  yield
end

def foo
  10
end

# target.rb
# DEBUGGER__.register_frame_filter do |path|
#   !path.match?(/library/)
# end

require_relative "library"

def bar
  20
end

result = wrapper do
  foo + bar
end

puts(result)

Command: $ exe/rdbg -e "b 11 ;; c" target.rb
Without Filtering
You can see the step enters into methods defined in library.rb

With Filtering
Step now ignores methods from library.rb. And frames from library.rb are also hidden without changing the original index.

Rails Example
(It's a demo app so the code is very simple with not many application frames)
Filtering Script:
backtrace_cleaner = Rails.backtrace_cleaner

DEBUGGER__.register_frame_filter do |path|
  !backtrace_cleaner.clean([path]).empty?
end

Without Filtering
The debugger steps right into Rails internal:

With Filtering
Stays inside application code:

This spec is not ractor-safe so I can't accept this spec.
Also it should be discussed that we need to allow

so extension gems don't need to require the entire debugger to register the filter

Also it should be discussed that we need to allow

I don't have strong opinion on this. But I thought it's something that you'd prefer? So do you think it's better to activate the debugger before extensions adding anything to it?

This spec is not ractor-safe so I can't accept this spec.

Can you let me know how to make it ractor-safe? Is it because it uses a singleton class' instance variable?

Would it be safer if we store the registered filters in DEBUGGER__::CONFIG?

Registering the data is safe on ractors, but Proc is not safe on multi-ractors.
Registering patterns are not enough?
like:
() set bt-exclude /gem_path/
() set bt-include  /specific_gem_name/

I see. Inserting patterns can probably work. I just need to find a way to extract them from Rails' backtrace cleaner 🤔
From your example I assume you want it to be a config option and can be set/update with the set command? If that's the case, are you ok with supporting an array of values? That'll require adding add and remove action to the set command because ideally we should support multiple patterns.
Not directly related
I think the set command could be renamed as config with a bit different format so it can be more flexible:
config # list all configs, same as `set`
config key # same as `set key`
config set key value # same as `set key=value`
config unset key

# for multi-value configs
config add key value
config remove key index

same as git config?

@ko1 yes, pretty similar to git and many CLI tools' config syntax.

sorry, I don't know other tools (because I'm not sure recent tools). Could you list some?

I just need to find a way to extract them from Rails' backtrace cleaner 🤔

It is good example. At least Rails is not a ractor-safe, so it is convenient to collaborate this feature. hmm.

sorry, I don't know other tools (because I'm not sure recent tools). Could you list some?

GitHub's CLI gh
❯ gh config -h
Display or change configuration settings for gh.

Current respected settings:
- git_protocol: the protocol to use for git clone and push operations (default: "https")
- editor: the text editor program to use for authoring text
- prompt: toggle interactive prompting in the terminal (default: "enabled")
- pager: the terminal pager program to send standard output to

USAGE
  gh config <command> [flags]

CORE COMMANDS
  get:        Print the value of a given configuration key
  set:        Update configuration with a value for the given key

INHERITED FLAGS
  --help   Show help for command

LEARN MORE
  Use 'gh <command> <subcommand> --help' for more information about a command.
  Read the manual at https://cli.github.com/manual

Allow to pattern to write a method call like :send:foo is one idea.

my misunderstand. git config has different style.
git config foo # get foo
git config foo bar # set foo as bar
git config --unset foo

Allow to write a method call in patterns like :send:foo is one idea.

I don't get this. can you explain more?

@ko1 I've updated the implementation to use patterns instead of procs.

I added: 6b525f7f1303c4404c70598831522e9b52b415eb

set -> config
skip_path configuration

I think frame filtering can apply to CatchBreakpoint as well. It's not uncommon to see Rails using Exception for flow control (e.g. using NameError in ActiveSupport). So catch Exception would frequently enter the Rails internal too.

I think frame filtering can apply to CatchBreakpoint as well. It's not uncommon to see Rails using Exception for flow control (e.g. using NameError in ActiveSupport). So catch Exception would frequently enter the Rails internal too.

Sorry, I can't catch. What will be filtered? Ignoring exception when it is raised at skip_path?

@ko1 yeah.
but of course exceptions are different than backtrace and normal frames, directly ignoring them could cause more confusion (as people don't always aware settings of the tools they use).

For this purpose, we need to introduce different configuration,
skip_frame_path
skip_raise_path
for example. anyway, current skip_path is ambiguous so I rename it to skip_frame_path.

@ko1 the current skip_path doesn't skip on frame control commands. is that intentional?


JS model loader doesn’t understand union type alias in ceylon.ast.core

ceylon compile-js ceylon.ast.samples ceylon.ast.core ceylon.ast.create && ceylon compile-js ceylon.ast.samples

Running this in the ceylon.ast repository on the version-1.3.1 branch, under the 1.3.1 distribution (e. g. from release or built from the 1.3.1 tag) produces 34 errors of the kind:

error: specified expression must be assignable to declared type of 'expression': 'Expression&AssigningExpression' ('Expression') is not assignable to 'AssigningExpression' ('unknown')
error: argument must be assignable to parameter 'operand' of 'NotOperation': 'EqualOperation' is not assignable to 'NegatingExpression' ('unknown')

It seems the model loader isn’t loading ceylon.ast’s precedence aliases (*ingExpression). @jvasileff reports that ceylon compile-dart, which also uses the JS model loader, has the same problem.
This blocks the ceylon.ast 1.3.1 release.

Removing the “t-regression” tag, this is even reproducible in 1.2.2 as @jvasileff reported. No idea why I didn’t discover it during the 1.3.0 release.

Whatever triggers the bug is not obvious:
import ceylon.ast.core { ... }

void breaks(NegatingExpression e1) {
    Expression e2 = e1;
    // specified expression must be assignable to declared type of 'e2':
    // 'NegatingExpression' ('unknown') is not assignable to 'Expression'
}

void works(EquatingExpression e1) {
    Expression e2 = e1;
}

Is it about the alias depth? Negating is one level above Equating. Can you try Comparing (below Equating) and Conjoining (above Negating)?

Yup, ConjoiningExpression also gives an error while Comparing doesn’t.

It might have to do with how NegatingOperation is used, and therefore loaded. If you hack the js model to make it look like EquatingExpression ($alias:{comp:"u",l:[{pk:".",nm:"ComparingExpression"},{pk:".",nm:"EqualityOperation"}]), it still fails.

After debugging in Eclipse, it's clear that there is a circularity problem. Here's what happens during model loading:

loadTypeAlias(EquatingExpression)
for EquatingExpression's extended type, this triggers loads of ComparingExpression -> ExistsNonemptyExpression -> ... -> PrePostfixingExpression, which then needs:
class Primary -> ... -> class UIdentifier -> method transform -> ... -> interface Transformer
and eventually class AndOperation, where we have the children attribute of type [ConjoiningExpression | NegatingExpression].
So, we load ConjoiningExpression & NegatingExpression
And then, attempt to form the tuple [ConjoiningExpression | NegatingExpression]

At this point, note that there is a very deep stack of partially loaded type aliases, which, except for ConjoiningExpression and NegatingExpression, all still have extendedType == null.
In order to form the tuple [ConjoiningExpression | NegatingExpression]:

Unit.getTupleType(ConjoiningExpression, NegatingExpression)
ModelUtil.unionType(ConjoiningExpression, NegatingExpression)
ModelUtil.addToUnion(..., NegatingExpression)
((Type)NegatingExpression).isSubtypeOf(ConjoiningExpression)
((Type)NegatingExpression).resolveAliases()

Now, since the declarations (type aliases) needed for NegatingExpression's extended type aren't fully loaded, resolveAliases() results in unknownType, which is cached!
In the end, the TypeAlias NegatingExpression has extendedType.resolvedAliases == unknownType.

Thanks for investigating this! I managed to boil it down to a shorter example:
// module tmp
shared class UIdentifier() {
    shared void transform(Transformer t) {}
}
shared class AndOperation(children) {
    shared [ConjoiningExpression, NegatingExpression] children;
}
shared interface Transformer {
    shared formal void transformUIdentifier(UIdentifier that);
}
shared alias ConjoiningExpression => AndOperation|UIdentifier;
shared alias NegatingExpression => UIdentifier;

// module tmp2
import tmp {
    UIdentifier,
    AndOperation
}
shared void run() {
    value ui = UIdentifier();
    value ao = AndOperation([ui, ui]);
}

I think @lucaswerkmeister's reduction is a slightly different case where the class's parameter's type winds up with a bad resolvedAliases type, whereas in the original case, it was the type alias's extended type that had a bad resolvedAliases type.
A further reduction of this second scenario is:
shared class C([ConjoiningExpression, String] children) {}
// resolved type of children becomes: [unknown, String] (type)

shared alias ConjoiningExpression => C|String;

and
import tmp {...}

void run() {
    C(["", ""]);
}

Note that this one is sensitive to ordering; renaming the alias can cause the error to disappear.

The alias in this last example is correctly loaded: A union type with C and String...

The alias in this last example is correctly loaded

But, when is it correctly loaded? IIRC, there is an attempt to use it before the extended type is set.

Ah, that would be the problem then. Something to do with the circular reference, then.

Sorry this took such a long time @lucaswerkmeister


Native Aot for Avalonia.Xaml.Behaviors

I publish the app with Native aot, It will no work when  I use Avalonia.xaml.behaviors. I try to add   in rd.xaml, but it  will failed to publish. How can i do if I wont to use  avalonia.xaml.behaviors

Don't use Behaviors that rely on reflection.

Don't use Behaviors that rely on reflection.

Thank you


Frame-y scrolling for application

Could someone confirm if scrolling the personList is very laggy or is it just my computer. The scrolling of other things i.e. command box is smooth.

Seems fine on my end

Seems fine on my end

Sad times, we will see if anyone else has the issue... If not i'll close this

Seems to be fixed somehow with the recent PRs


Bluetooth: Mesh: Move dfu mbt models into their own elements

Tests: Bluetooth: Tester: Mesh DFUM and BLOB should have own elements
Moving the blob client, dfd server and dfu server to their own elements and increasing the CONFIG_BT_MESH_TX_SEG_MAX to 8 to fit new composition data into composition data page status message.
Standalone mesh blob client and DFU distributor/update server models requires one element and those elements only contain the main models and the models they extend to.
Referring to MshMBT_v1.0 Section 6.1: The BLOB Transfer Client model defines the messages listed in Table 6.1 , and requires one element: the BLOB Transfer Client Main element. The BLOB Transfer Client Main element contains the BLOB Transfer Client main model.
And referring to MshDFU_v1.0 Sections 6.1.1 and 6.2.1:
6.1.1
The Firmware Update Server model adds the state instances listed in Table 6.1 and Table 6.2 and the messages listed in Table 6.3 to the model it extends, and requires one element: the Firmware Update Main element. The Firmware Update Main element contains the Firmware Update Server main model and all the models that the main model extends.
6.2.1
The Firmware Distribution Server model adds the state instances listed in Table 6.7 and Table 6.8 and the messages listed in Table 6.9 to the model it extends, and requires one element: the Firmware Distribution Main element. The Firmware Distribution Main element contains the Firmware Distribution Server main model and all the models that the main model extends.

Bluetooth: Mesh: Check that required models exists on the same element
Referring to MshDFU_v1.0 Sections 6.1.1, 6.2.1 and  7.1.1 model descriptions: DFU/DFD server/clients extend BLOB Transfer root models and DFD server requires Firmware Update Client on the same element. For this reason we need to make sure that those main models or root models exist on the same element. And also firmware update client can not be forced to be in the first element.

For all model extention call return the error code in case of an error.

@sjanc, could you please look at this PR?

Tried to shorten error log messages without losing explanation for what the actual problem is. The key point is "not being on the same element", just saying "missing" might not give the message, or puzzle people. I am OK with removing all err logs anyway :+1:

Tried to shorten error log messages without losing explanation for what the actual problem is. The key point is "not being on the same element", just saying "missing" might not give the message, or puzzle people. I am OK with removing all err logs anyway 👍

It is not necessary at all. If there is a problem, the log messages anyway print files names, etc. Even if MINIMAL is enabled, simply searching by string globally one can easily locate the log strings in code base. I feel, we shouldn't treat log messages as a way to educate users about what is the right thing to do. Instead, use them to actually print error codes or some useful information. This keeps application footprint low at development stage itself.

@sjanc PTAL


EmrEtlRunner: add lint command which validates Iglu resolver, enrichments and storage targets

Basic algorithm:

Lint iglu-resolver.json using the embedded schema repo
Configure full Iglu client using iglu-resolver.json
Lint enrichments using #2

Depends on a new iglu-ruby-client: https://github.com/snowplow/iglu-ruby-client

Storage target linting dependent on release of R88 (@chuwy's)

Should this be broken down into two commands:

lint resolver
lint enrichments

?

Hey @BenFradet - that sounds good I think. Do we add lint all to simplify things for a CI/CD script?

We could, would we need generate all as well for #3105 ?

Yep that would be nice

follow up #3364


Update obsolete container repository names

You may disregard these recommendations if you used the Edit on GitHub button from dvc.org to improve a doc in place.

❗ Please read the guidelines in the Contributing to the Documentation list if you make any substantial changes to the documentation or JS engine.
🐛 Please make sure to mention Fix #issue (if applicable) in the description of the PR. This causes GitHub to close it automatically when the PR is merged.
Please choose to allow us to edit your branch when creating the PR.
Thank you for the contribution - we'll try to review it as soon as possible. 🙏

@casperdcl, who said fear? rm .git/hooks/* 😈

If you prefer to use the implicit latest tags 😬  it's as easy as performing the following replacements:

iterativeai/cml:0-dvc2-base1-gpu by iterativeai/cml:latest-gpu
iterativeai/cml:0-dvc2-base1 by iterativeai/cml:latest or just iterativeai/cml

Look, ma! Like in ray.io! 🙃

# head_image: "rayproject/ray-ml:latest-gpu"

# worker_image: "rayproject/ray-ml:latest-cpu"


Fix handling of symbolic links

Signed-off-by: Daniel J Walsh<EMAIL_ADDRESS>

Fixes: https://github.com/containers/libpod/issues/2057

/approve
LGTM

/lgtm


[incubator/kafka]  Error: error validating "": error validating data: found invalid field terminationGracePeriodSeconds for v1beta1.StatefulSetSpec

Is this a request for help?: NO

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
Version of Helm and Kubernetes:
Running on GKE
Kubernetes Version:
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.7", GitCommit:"dd5e1a2978fd0b97d9b78e1564398aeea7e7fe92", GitTreeState:"clean", BuildDate:"2018-04-19T00:05:56Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9+", GitVersion:"v1.9.7-gke.5", GitCommit:"9b635efce81582e1da13b35a7aa539c0ccb32987", GitTreeState:"clean", BuildDate:"2018-08-02T23:42:40Z", GoVersion:"go1.9.3b4", Compiler:"gc", Platform:"linux/amd64"}

Helm version:
Client: &version.Version{SemVer:"v2.6.2", GitCommit:"be3ae4ea91b2960be98c07e8f73754e67e87963c", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.6.2", GitCommit:"be3ae4ea91b2960be98c07e8f73754e67e87963c", GitTreeState:"clean"}

Which chart:
[incubator/kafka]
What happened:
helm install incuabor/kafka gives the following error:
Error: error validating "": error validating data: found invalid field terminationGracePeriodSeconds for v1beta1.StatefulSetSpec

What you expected to happen:
Chart installs kafka.
How to reproduce it (as minimally and precisely as possible):
helm install --name kafka --namespace kafka incubator/kafka

Anything else we need to know:
Issue #3396 was reporting a similar error.

Solved my self.
After updating helm to version
Client: &version.Version{SemVer:"v2.10.0", GitCommit:"9ad53aac42165a5fadc6c87be0dea6b115f93090", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.10.0", GitCommit:"9ad53aac42165a5fadc6c87be0dea6b115f93090", GitTreeState:"clean"}

it worked.


A not-started future that is cancelled still runs.

I found an issue with Future. Basically if future is cancelled before running on an executor it will still run. Here is a snippet that exposes the problem, I'm using a single thread executor:
        ExecutorService es = Executors.newSingleThreadExecutor();

        Future<Void> f = Future
                .run(es, () -> {
                    // We will only see this line
                    System.out.println("Starting Future 1");
                    Thread.sleep(1000);
                    // Will never get here as the future will be cancelled during Thread.sleep()
                    System.out.println("Done Future 1");
                })
                .onComplete(t -> System.out.println("Future 1 result " + t));

        Future<Void> f2 = Future
                .run(es, () -> {
                    // Note, this should never be printed
                    System.out.println("Starting Future 2 ");
                    Thread.sleep(1000);
                    System.out.println("Done Future 2");
                })
                .onComplete(t -> System.out.println("Future 2 result " + t));

        // Cancel f2 BEFORE it runs on the executor
        f2.cancel(true);
        f.cancel(true);
        es.shutdown();

The ouput is as follows:
Starting Future 1
Starting Future 2
Done Future 2
Future 2 result Failure(java.util.concurrent.CancellationException)
Future 1 result Failure(java.util.concurrent.CancellationException)

I only expected to see Starting Future 1 as f2 is cancelled before executor gets to run it.

You are right, there is an issue like described above. I did some digging,
f2 has no execution thread assigned, when cancel statement is executed. Future is marked as Cancelled tho.
Now, f is cancelled and thread interrupted. Executor starts execute f2 regardless.
I'm guessing we do not care if result of tryComplete is true or false, and in the end we start it. And can't do nothing about it.
As of today cancel works only for currently running tasks, and one that are completed.


Lbox To L2k-noCnstrParams proof

We finally prove that the translation from lambda-box terms to L2k is semantics-preserving, i.e we get the same evaluations. We also verify that it preserves correct terms as was previously defined in L2k, meaning that constructors are always applied to their declared number of arguments, and that is preserved by evaluation. I think this closes the last remaining hole in the verification pipeline, but I don't see how to integrate this into a complete pipeline correctness theorem.

@intoverflow there seems to be an issue with opam not recognizing an argument in the CI build, can you have a look?

@intoverflow it seems we'll need a new image with opam 2.1 at least


#308 - Removed code from ctors in ImmutableProps

@rultor merge

@rultor merge

@driver733 OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@driver733 Done! FYI, the full log is here (took me 3min)


Build aws-iam-authenticator for linux/arm64 and arm32v7

Helllo:
Would we be able to release this binary for linux/arm64 and linux/arm32v7 architecture?
Currently, I see we only have the following:

aws-iam-authenticator_0.5.3_darwin_amd
aws-iam-authenticator_0.5.3_linux_amd
aws-iam-authenticator_0.5.3_windows_amd64.exe

My team uses this binary as dependency for another project, and we would like to start supporting ARM architecture, such that the following URL resolves:
https://github.com/kubernetes-sigs/aws-iam-authenticator/releases/download/v${AWS_IAM_AUTH_VERSION}/aws-iam-authenticator_${AWS_IAM_AUTH_VERSION}_linux_arm64

I think this PR will resolve this issue: https://github.com/kubernetes-sigs/aws-iam-authenticator/pull/425
I am just waiting for it to be merged and released.

This PR should solve https://github.com/kubernetes-sigs/aws-iam-authenticator/pull/431

This release helped solved our issue: https://github.com/kubernetes-sigs/aws-iam-authenticator/releases/tag/v0.5.5
Thank you for the help. Closing this issue.


Vuex: keep inspected mutation selected if there is a new mutation

Version
5.0.3
Browser and OS info
Chrome / Windows 10
Steps to reproduce

Create a Vuex enabled App
In a created component, create an setInterval that updates the state via a mutation at a regular interval
Try to inspect the Vuex state

What is expected?
If an entry in the vuex log is explicitly clicked on to be inspected, it shouldn't be changed due to a mutation.
What is actually happening?
When a mutation occurs the 'inspected' Vuex item is updated to the latest value

I added a screen capture of what is occurring here: https://imgur.com/a/QfKAI9N

The screen capture

IMHO Seems more like a bug than an enhancement, since viewing state is pretty much unusable, and it’s also a regression of behaviorfrom prior dev tools version.

I have to agree with @jacobg
Our only solution at the moment is to disable the time based features of our app in order to get any use out of the Vuex tab.

@jacobg Git agrees with me that the inspected mutation was always reset to the last one when a mutation was received, even 2 years ago 😸

@Akryum Thanks for resolving. I thought I remember in the old version I could look at state even when new mutations come in. Perhaps the state was getting updated with new mutations. The current version changes to Loading State spinner when new mutation comes in.

@jacobg I think your are talking about something different, OP was about selecting a mutation other than the last one and keeping it selected when a new mutation is received.


[FLINK-4490] [distributed coordination] Decouple the JobManage's slots from the 'Instance'

To allow for a future dynamic slot allocation and release model, the slots should not depend on 'Instance'.
In this change, the Slots hold most of the necessary information directly (location, gateway) and
the interact with the Instance only via a 'SlotOwner' interface.
The ResourceID, which has been introduces a while back, is a unique identifier for a TaskManager that is  also constant for the lifetime of that particular TaskManager process. Where previously, the JobManager comparted Instance objects for referential equality to determine if two slots refer to the same TaskManager, the code now always refers to the ResourceID instread.
*Side note: I suggest to promote the ResourceID to TaskManagerID at some point.
This also reworks the InstanceConnectionInfoto the TaskManagerLocation, which contains in addition to IP/hostname/port also the ResourceID.
All logic of the Scheduler and ExecutionGraph remains unchanged.

Looking into it now

Really good changes @StephanEwen. +1 for merging.
I had only some minor comments.
I guess that replacing the ActorGateways in the Slots and preparing the Scheduler to work with futures, are the next follow-up tasks.

We can do either that follow-up, or we can add an RPC gateway in the flip-6 branch and remove the ActorGateway after merging the feature and master branch.
Will address the comments and merge...

Was manually merges as of eac6088a75e813a015b778f4cfc4cce0cf2a53ce


Type a UID instead of just generate it.

Hello! I'm facing a big issue here.
I'm migrating a huge database to my Strapi, but I need to keep our old UIDs, there is a way to enable write on the UID field, instead of just generating it automatically? If I could just copy and paste our old IDs on the field, would save my life lol. @Dulajdeshan

+1 for this - would be very nice to have an editable option for the UUID field, instead of just regenerate.

Hi @etekweb @adrknapp I have added an option to disable auto generation of UUID. Hope it will solve your issues.
Happy Coding 😃 !!


openBinaryFile: does not exist (No such file or directory)

I frequently get openBinaryFile: does not exist (No such file or directory) error from this rule - for bash script files which clearly do exist!
I suspect it may be due to some Bazel concurrency issue, or something like that.
Using v0.1.1 on Bazel 6.0.0.
shellcheck_test(
    name = "shellcheck_test",
    size = "small",
    data = glob(
        [
            "**/*.bash",
            "**/*.sh",
        ],
        exclude = [
            "**/bazel-bin/**",
            "**/bazel-out/**",
            "site/**",
            ".venv/**",
        ],
    ),
    tags = ["lint"],
)

will regularly fail with something like this:
$ bazelisk test //...
INFO: Analyzed 15 targets (9 packages loaded, 34 targets configured).
INFO: Found 10 targets and 5 test targets...
INFO: From Testing //:shellcheck_test:
==================== Test output for //:shellcheck_test:
bazel-enola/tools/git/install-hooks.bash: bazel-enola/tools/git/install-hooks.bash: openBinaryFile: does not exist (No such file or directory)
================================================================================
INFO: Elapsed time: 0.623s, Critical Path: 0.08s
INFO: 5 processes: 3 internal, 2 linux-sandbox.
INFO: Build completed, 1 test FAILED, 5 total actions
//connectors/demo:src/test/java/dev/enola/demo/ModelTest        (cached) PASSED in 0.6s
//core/lib:src/test/java/dev/enola/core/IDsTest                 (cached) PASSED in 0.8s
//core/proto:core_buf_proto_lint                                (cached) PASSED in 0.0s
//tools/proto:src/test/java/dev/enola/tools/proto/TextProtoValidatorTest (cached) PASSED in 0.7s
//:shellcheck_test                                                       FAILED in 0.1s
  /home/vorburger/.cache/bazel/_bazel_vorburger/8278ca71b7724cd0429873b01f58f5d3/execroot/_main/bazel-out/k8-fastbuild/testlogs/shellcheck_test/test.log

Executed 1 out of 5 tests: 4 tests pass and 1 fails locally.

Re-running Bazel makes it go away. Which one shouldn't have to do, of course.

It looks like it may have been an issue with including bazel-enola directory in your test. Closing as I am not sure this is an issue in `rules_shellcheck. Feel free to open a new issue.


PR to fix cone bug #24

I opened a new PR to fix the cone bug (with the other one I opened I was having too many merging problems).
The cone has no lower bound.

Bugs fixed!!


test reading data with spaces

closes #11
This PR modifies the existing test for the function readFiles. The files in the input directory now contain a lot of unnecessary spaces. The test makes sure that the input is read correctly despite all these unnecessary spaces.

Add folder tests/testthat/test_data/no_spaces/ with isotope measurement files that do not contain spaces.
Add spaces to csv files in folder tests/testthat/test_data/
test compares the data read from the files with spaces to the data from the files without spaces.

@ikroener This is a very small PR and there is not much to review. I assigned it to you so that you can get the hang of things and decide if you want to be involved in more reviews in the future.

Thanks for your comment and the helpful suggestion. I changed the spacing in one of the files to be less consistent. Merging this as soon as CI passes.


Support alphanumeric characters in the monadic syntax

It seemed to compile just fine :) so no conflicts I think?

I love it.

Let's try it out on the reason CI


Submit event is triggered twice #4955

When a form is submitted by clicking on the "submit" button, the script submits the form again.
When there is an on('submit') or on('beforeSubmit'), the function is executed twice.

Docs added long time ago. Closing.

Docs added long time ago. Closing.


Externalize concatjs

Currently concatjs lives in an internal directory. It seems that there is nothing prohibitivly internal about it except for the parent directory. Would it be possible to move concatjs up a dir into the root, or make a "go" dir at the root and put it in there? Crossing visibility always makes me a little uncomfortable

What's the use case?
Andrew Z Allen<EMAIL_ADDRESS>schrieb am Mo., 5. März 2018 um
08:49 Uhr:

Currently concatjs lives in an internal directory. It seems that there is
nothing prohibitivly internal about it except for the parent directory.
Would it be possible to move concatjs up a dir into the root, or make a
"go" dir at the root and put it in there? Crossing visibility always makes
me a little uncomfortable
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/rules_typescript/issues/164, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAAcKBtFcfp5Kd4vtha1UeLT3Hvdd6kPks5tbO3zgaJpZM4Sb2hf
.

From the documentation section titled "Serving TypeScript for Development
https://chrome.google.com/webstore/detail/chromevox/kgejglhpjiefppelpmljglcjbhoiplfn
"

Teach your real frontend server to serve files from Bazel's output
directory. This is not yet documented. Choose this option if you have an
existing server used in development mode, or if your requirements exceed
what the ts_devserver supports. Be careful that your development round-trip
stays fast (should be under two seconds).

It seems the majority of the logic required to teach a server how to do
this is contained in the concatjs folder and being able to import it would
be useful.
From the comment at the top of the concatjs.go
https://github.com/bazelbuild/rules_typescript/blob/master/internal/concatjs/concatjs.go#L28
file:
"""
// Example usage:
// http.Handle("/app_combined.js",
// concatjs.ServeConcatenatedJS("my/app/web_srcs.MF", ".", [], [], nil))
"""

To be clear, you can already do this today, right? but you have to import from the /internal package?
Or does the go third_party vendoring require that it be in some predictable path?

My understanding of internal packages is that they are equivalent to //visibility:private (and transposed as such by gazelle). Is this a misunderstanding on my part?
https://golang.org/doc/go1.4#internalpackages

The actual visibility is here:
https://github.com/bazelbuild/rules_typescript/blob/master/internal/concatjs/BUILD#L3
(we don't use gazelle here because this is synced from google3)
I agree this package should be reusable in other Go devservers.

Just to confirm this, it is 100% not possible to use this outside of the rules_typescript repo.
Here is the error when I attempt to load it via your BUILD files.
ERROR: /home/achew22/go/src/REDACTED/BUILD:19:1: Target '@com_github_bazelbuild_rules_typescript//internal/concatjs:concatjs' is not visible from target '//REDACTED/server:go_default_library'. Check the visibility declaration of the former target if you think the dependency is legitimate

When I try to load it with build_file_generation = "on" (which replaces the generated BUILD files) and uses Gazelle to generate new ones, I get the error:
ERROR: /home/achew22/go/src/REDACTED/BUILD:19:1: Target '@com_github_bazelbuild_rules_typescript//internal/concatjs:go_default_library' is not visible from target '//REDACTED/server:go_default_library'. Check the visibility declaration of the former target if you think the dependency is legitimate

WRT how to keep Google3's BUILD files compatible with the OSS stuff, I think I have a theory. I'll TAL @ it and follow up over email.


AutoScalingGroup timeout: Status Reason: 'kubernetes.io/cluster/clustername' is not a valid tag key.

Description
Testing the Complete and the IRSA examples I get an error that the AutoScalingGroup can't create instances:
Versions
❯ terraform version
Terraform v1.1.3
on linux_amd64

provider registry.terraform.io/hashicorp/aws v3.72.0
provider registry.terraform.io/hashicorp/cloudinit v2.2.0
provider registry.terraform.io/hashicorp/helm v2.4.1
provider registry.terraform.io/hashicorp/null v3.1.0
provider registry.terraform.io/hashicorp/tls v3.1.0

Reproduction
Clone repo and test the examples.
Code Snippet to Reproduce

Expected behavior
Auto Scaling group creates instances
Actual behavior

Terminal Output Screenshot(s)
module.eks.module.self_managed_node_group["spot"].aws_autoscaling_group.this[0]: Still destroying... [id=spot-20220117114248850100000023, 9m50s elapsed]
module.eks.module.self_managed_node_group["refresh"].aws_autoscaling_group.this[0]: Still creating... [9m50s elapsed]
module.eks.module.self_managed_node_group["spot"].aws_autoscaling_group.this[0]: Still destroying... [id=spot-20220117114248850100000023, 10m0s elapsed]
module.eks.module.self_managed_node_group["refresh"].aws_autoscaling_group.this[0]: Still creating... [10m0s elapsed]
╷
│ Error: "refresh-20220117122547139700000001": Waiting up to 10m0s: Need at least 1 healthy instances in ASG, have 0. Most recent activity: {
│   ActivityId: "a8b5f9a0-2397-c9ec-a78e-25f731576957",
│   AutoScalingGroupARN: "arn:aws:autoscaling:eu-west-1:*snip*:autoScalingGroup:a6153771-becc-4c1c-89da-44d7e9044423:autoScalingGroupName/refresh-20220117122547139700000001",
│   AutoScalingGroupName: "refresh-20220117122547139700000001",
│   Cause: "At 2022-01-17T12:35:19Z an instance was started in response to a difference between desired and actual capacity, increasing the capacity from 0 to 1.",
│   Description: "Launching a new EC2 instance.  Status Reason: 'kubernetes.io/cluster/exirsatest' is not a valid tag key. Tag keys must match pattern ([0-9a-zA-Z\\\\-_+=,.@:]{1,255}), and must not be a reserved name ('.', '..', '_index'). Launching EC2 instance failed.",
│   Details: "{\"Subnet ID\":\"subnet-006ccbc3820532b53\",\"Availability Zone\":\"eu-west-1c\"}",
│   EndTime: 2022-01-17 12:35:20 +0000 UTC,
│   Progress: 100,
│   StartTime: 2022-01-17 12:35:20.69 +0000 UTC,
│   StatusCode: "Failed",
│   StatusMessage: "'kubernetes.io/cluster/exirsatest' is not a valid tag key. Tag keys must match pattern ([0-9a-zA-Z\\\\-_+=,.@:]{1,255}), and must not be a reserved name ('.', '..', '_index'). Launching EC2 instance failed."
│ }
│
│   with module.eks.module.self_managed_node_group["refresh"].aws_autoscaling_group.this[0],
│   on ../../modules/self-managed-node-group/main.tf line 260, in resource "aws_autoscaling_group" "this":
│  260: resource "aws_autoscaling_group" "this" {
│
╵

Additional context
You can see I tried renaming the folder to exirsatest and that didn't help.
By removing the keys below keys unblocked the ASG but is not a fix of course.
kubernetes.io/cluster/exirsatest
k8s.io/cluster/ex-irsatest

please paste a config of module which you using

❯ git clone https://github.com/terraform-aws-modules/terraform-aws-eks.git
Cloning into 'terraform-aws-eks'...
remote: Enumerating objects: 4176, done.
remote: Counting objects: 100% (843/843), done.
remote: Compressing objects: 100% (457/457), done.
remote: Total 4176 (delta 508), reused 620 (delta 381), pack-reused 3333
Receiving objects: 100% (4176/4176), 1.42 MiB | 535.00 KiB/s, done.
Resolving deltas: 100% (2716/2716), done.
❯ cd terraform-aws-eks/examples/irsa_autoscale_refresh
❯ terraform init
Initializing modules...
Downloading registry.terraform.io/terraform-aws-modules/iam/aws 4.9.0 for aws_node_termination_handler_role...
- aws_node_termination_handler_role in .terraform/modules/aws_node_termination_handler_role/modules/iam-assumable-role-with-oidc
Downloading registry.terraform.io/terraform-aws-modules/sqs/aws 3.2.1 for aws_node_termination_handler_sqs...
- aws_node_termination_handler_sqs in .terraform/modules/aws_node_termination_handler_sqs
- eks in ../..
- eks.eks_managed_node_group in ../../modules/eks-managed-node-group
- eks.eks_managed_node_group.user_data in ../../modules/_user_data
- eks.fargate_profile in ../../modules/fargate-profile
- eks.self_managed_node_group in ../../modules/self-managed-node-group
- eks.self_managed_node_group.user_data in ../../modules/_user_data
Downloading registry.terraform.io/terraform-aws-modules/iam/aws 4.9.0 for iam_assumable_role_cluster_autoscaler...
- iam_assumable_role_cluster_autoscaler in .terraform/modules/iam_assumable_role_cluster_autoscaler/modules/iam-assumable-role-with-oidc
Downloading registry.terraform.io/terraform-aws-modules/vpc/aws 3.11.3 for vpc...
- vpc in .terraform/modules/vpc

Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/helm versions matching ">= 2.0.0"...
- Finding hashicorp/aws versions matching ">= 2.23.0, >= 3.63.0, >= 3.72.0"...
- Finding hashicorp/null versions matching ">= 3.0.0"...
- Finding hashicorp/tls versions matching ">= 2.2.0"...
- Finding hashicorp/cloudinit versions matching ">= 2.0.0"...
- Installing hashicorp/helm v2.4.1...
- Installed hashicorp/helm v2.4.1 (signed by HashiCorp)
- Installing hashicorp/aws v3.72.0...
- Installed hashicorp/aws v3.72.0 (signed by HashiCorp)
- Installing hashicorp/null v3.1.0...
- Installed hashicorp/null v3.1.0 (signed by HashiCorp)
- Installing hashicorp/tls v3.1.0...
- Installed hashicorp/tls v3.1.0 (signed by HashiCorp)
- Installing hashicorp/cloudinit v2.2.0...
- Installed hashicorp/cloudinit v2.2.0 (signed by HashiCorp)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
❯ terraform apply --auto-approve

and it should timeout/fail when creating the ASGs

All three Auto Scaling groups have the issue from the example:

it looks fine per https://github.com/awsdocs/amazon-eks-user-guide/issues/38#issuecomment-578485872 but the regex doesn't have forward slashes
@brenwhyte are you able to file a ticket with AWS to get their input?

I can, I'll get on that in 2 secs. I noticed on an earlier cluster that tags are the same, so this did work previously.
Lets see what AWS Support say.

Has same errors with  'self-managed-node-group'  example:
AutoScalingGroupName: "worker-group-2-20220117194210164800000003", │   Cause: "At 2022-01-17T19:49:11Z an instance was started in response to a difference between desired and actual capacity, increasing the capacity from 0 to 1.", │   Description: "Launching a new EC2 instance.  Status Reason: 'k8s.io/cluster/self-test-eks-lU3GjdcB' is not a valid tag key. **Tag keys must match pattern ([0-9a-zA-Z\\\\-_+=,.@:]{1,255}), and must not be a reserved name ('.', '..', '_index')**. Launching EC2 instance failed.", │   Details: "{\"Subnet ID\":\"subnet-0f4c15ddb73b04b7a\",\"Availability Zone\":\"us-east-1a\"}", │   EndTime: 2022-01-17 19:49:12 +0000 UTC, │   Progress: 100, │   StartTime: 2022-01-17 19:49:12.43 +0000 UTC, │   StatusCode: "Failed", │   StatusMessage: "'k8s.io/cluster/self-test-eks-lU3GjdcB' is not a valid tag key. Tag keys must match pattern ([0-9a-zA-Z\\\\-_+=,.@:]{1,255}), and must not be a reserved name ('.', '..', '_index'). Launching EC2 instance failed." │ } │ │   with module.eks.module.self_managed_node_group["1"].aws_autoscaling_group.this[0], │   on .terraform/modules/eks/modules/self-managed-node-group/main.tf line 260, in resource "aws_autoscaling_group" "this": │  260: resource "aws_autoscaling_group" "this" {

The EKS managed node groups can no longer be created either.
Is this probably a similar problem?

Error: error creating EKS Node Group (<eks_cluster_name>:<eks_node_group_name>): InvalidRequestException: 'k8s.io/cluster-autoscaler/enabled' is not a valid tag key. Tag keys must match pattern ([0-9a-zA-Z\-+=,.@:]{1,255}), and must not be a reserved name ('.', '..', 'index') { RespMetadata: { StatusCode: 400, RequestID: "" }, Message: "'k8s.io/cluster-autoscaler/enabled' is not a valid tag key. Tag keys must match pattern ([0-9a-zA-Z\\-+=,.@:]{1,255}), and must not be a reserved name ('.', '..', '_index')" }

this seems to be a change on the AWS side since these examples were working without issue. is anyone able to file a ticket with AWS support to get their feedback?

By the way, it does not occur in 18.1.0, but in 18.2.0.

Yes, the problems seem to be related to the instance_metadata_tags      = "enabled". Once disabled the problem disapears

Hmm, interesting. Thanks for identifying that

I'm seeing the same issue. However, disabling instance_metadata_tags = "disabled" seemed to correct the issue for me as well.

This issue has been resolved in version 18.2.1 :tada:

ok, we've changed the default behavior to disabled - disappointing that AWS has different tag requirements but we will leave it up to users to manage for now


[CONTROLLER/CLOUD] supports huawei nat rule multi fixes ips

This PR is for:

Server

supports huawei nat rule multi fixes ips
Checklist

[ ] Added unit test.

Backport to branches

main

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.zhengya seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Any way to write Frontend routes

Hi Great Package i always looking for after CI
I have question is there any way i can write index(frontend controller) like www.xyz.com can access XYZContoller index function and www.xyz.com/about can access XYZContoller about function.
Thanks in advance.

Take a look at https://github.com/tighten/ziggy


StreamX 1.3.0 roadmap

At present, StreamX has completed the hosting of flink tasks. This part of the work is very important and difficult. Thanks to all the developers for their hard work, but this is only the initial stage, and we will focus on streaming-warehouse and cloud native, the following is the roadmap of the next stage of StremaX:
mind link: https://docs.qq.com/mind/DRUF0d1ZiTkhIaENv
Roadmap for 11/2022 ~ 07/2022:

Documentation

[ ] #603
[ ] #604

Streaming Warehouse

[ ] #605 #563
[ ] #606
[ ] #607
[ ] #608
[ ] #609
[ ] #610
[ ] #611

StremaX Console

[ ] Batch task scheduling integration, integration with other scheduling frameworks such as DolphinsCheduler
[ ] #612
[ ] #613
[ ] Convergence thread definition, unified thread pool use entry
[ ] The log information output is improved to make the error information clearer and clearer
[ ] Add more task operations (task replication, view real-time deployment logs, etc.)
[ ] The front-end Vue framework is upgraded to Vue 3, the structure is reorganized, and the modules are divided
[ ]  Improve the management of current task dependencies (maven cannot be specified at present)
[ ] Improved task configuration management, divided into common configuration, resource configuration, advanced configuration, etc., front-end collocation display
[ ] Standalone mode support
[ ] Flink Session module management
[ ] Support more alarm methods such as DingTalk and WeChat  #579

Cloud Native

[ ] Storage adaptation s3, oss, etc.
[ ] StremaX Docker image is provided, which supports running on k8s, further reducing user usage costs

Core Framework

[ ] More flink-shims corresponding to flink are provided, the module is provided as a plug-in and a third-party dependency, and users can download and use it as needed
[ ] Datastream connector reorganizes the module and puts it in a new module

Awesome ,Let's work together

Awesome ,Let's work together

cool, looking forward to our cooperation👌


bootstrap logic in server side

This PR is for bootstrap logic in server side, will add more test and add some more logic

items to add:
tests
buffer io test together with chunk size
purge enable/disable
session recycle
topology retrieve to verify


castxml: set correct -DCLANG_RESOURCE_DIR

This change fixes #66456
According to the comment in CastXML CMakeLists.txt this variable should point to the directory that contains include/stddef.h. This change fixes the variable, so now built package contains the file.
$ nix-build -A castxml
/nix/store/ry5fhfvi7ixn47a7i9pripn1fq1kbxwr-CastXML-0.2.0
$ ls result/share/castxml/clang/include/stddef.h
result/share/castxml/clang/include/stddef.h

I have tested it by doing
$ nix-shell -I nixpkgs=$NIXPKGS -p castxml python37Packages.pygccxml

and running all the testcases from issue #66465
NIXPKGS points to my local clone of nixpkgs git tree.

@teto Can you review it and test that it fixes your NS-3 package?

@GrahamcOfBorg eval

@link2xt seems like it fixed it !

thanks for looking into this


runtime output for the 'esm' bundler does not refresh

So this is a follow up from this discord convo!
https://discord.com/channels/722131463138705510/723573901862371449/1222612734835953764
Quick recap. Refresh was not triggering for us. We use a custom esbuild-based bundler, our ESM implementation was originally based on the 'esm' spec published by snowpack here:
https://github.com/FredKSchott/esm-hmr
In particular, we were implementing the behavior of import.meta.hot.data as described in this document, where it is reset before the module is imported and any refresh callbacks are called.
https://github.com/FredKSchott/esm-hmr?tab=readme-ov-file#importmetahotdata
However, the 'esm' transform in solid-refresh actually implements the vite interpretation, where import.hot.meta.data persists between reloads:
https://vitejs.dev/guide/api-hmr#hot-data
This matters for this line in particular, where the registry is stored in the hot.data object. for esm-compliant bundlers this means the registry it blown away every update.
https://github.com/solidjs/solid-refresh/blob/main/src/runtime/index.ts#L289
Since the snowpack and this spec itself is EOL I don't necessarily think that solid-refresh needs to change to support it. 'esm-hmr' support could instead be completely dropped or deprecated. We updated our HMR implementation to match vite's instead internally.
(pour one out for documented standards...)

Honestly I'm a bit neutral. The only reason I still continued implementing, this despite knowing Snowpack has been dead for almost 2 years, is that there are other bundlers that follows the spec (I forgot which) and so this whole "esm" thing is just a fallback if ever a bundler happens to be providing this support, the same way I have "standard" for bundlers like Parcel


where is test_with_STL_kmeans.py?

Sorry for the confusion. It should be "Run 'kmeans_demo.ipynb' to test with K-Means clustering."


Fixes 3656: add api to list template errata

Summary

Adds API for listing content template errata: /templates/:uuid/errata (similar to the list errata endpoint for snapshots)
Includes optional query parameters search, limit, type, and severity
Depends on this tang PR to add in the CVEs

Testing steps

Add a custom repository with errata and a RH repository and let them snapshot (this will snapshot a small RH repo: OPTIONS_REPOSITORY_IMPORT_FILTER=small go run cmd/external-repos/main.go import && go run cmd/external-repos/main.go nightly-jobs)
Create a template with those repositories, selecting the latest date
Make a request to the /templates/:uuid/errata endpoint with the template uuid and you should see the template's errata (should include errata from both of the snapshots in the template) in a response similar to this:

{
    "data": [
        {
            "id": "018fbf80-9d1e-7458-b10b-9b39b3b652a7",
            "errata_id": "RHSA-2020:3602",
            "title": "Important: Ansible security and bug fix update (2.9.13)",
            "summary": "An update for ansible is now available for Ansible Engine 2\n\nRed Hat Product Security has rated this update as having a security impact\nof Important. A Common Vulnerability Scoring System (CVSS) base score,\nwhich gives a detailed severity rating, is available for each vulnerability\nfrom the CVE link(s) in the References section.",
            "description": "Ansible is a simple model-driven configuration management, multi-node\ndeployment, and remote-task execution system. Ansible works over SSH and\ndoes not require any software or daemons to be installed on remote nodes.\nExtension modules can be written in any language and are transferred to\nmanaged machines automatically.\n\nThe following packages have been upgraded to a newer upstream version:\nansible (2.9.13)\n\nBug Fix(es):\n* CVE-2020-14365 ansible: dnf module install packages with no GPG signature\n\nSee:\nhttps://github.com/ansible/ansible/blob/v2.9.13/changelogs/CHANGELOG-v2.9.rst\nfor details on bug fixes in this release.",
            "issued_date": "2020-09-01 19:10:30",
            "updated_date": "2020-09-01 19:10:25",
            "type": "security",
            "severity": "Important",
            "reboot_suggested": false,
            "cves": [
                "CVE-2020-14365"
            ]
        },
        ...

To test that the correct snapshot's errata are shown, you can update the custom repository with a different URL and let it snapshot
Edit the template date to include this latest snapshot and view the errata again. The errata list should reflect the latest snapshot's errata
Edit the template to remove the custom repository and then view the errata again, you should only see the errata from the RH repository's snapshot

Checklist

[ ] Tested with snapshotting feature disabled and pulp server URL not configured if appropriate

need to update this to return a list of CVEs, i think that would require a change in tang.
also, this endpoint refers to errata which is consistent with the similar endpoint to list snapshot errata, but the task says to use advisories. should i refer to these as errata or advisories?

https://issues.redhat.com/browse/HMS-3656

/retest

Hi
ACK from me
API works[1], UI has problems not related to this PR[2]
@jlsherrill Merge on ACK
[1]
In [3]: app.content_sources.rest_client.templates_api.get_template('0bcf3753-e81f-48cc-b40c-64a7210f27d9')
2024-06-03 16:22:01.786 [    INFO] [iqe.base.rest_client] REST: METHOD=GET, request_id=9c84f4e7-4f68-475b-b393-d4cff9d904d5, params=[]
Out[3]:
{'arch': 'x86_64',
 'date': '2024-06-03T04:00:00Z',
 'description': 'my 1st template mk II',
 'name': 'test1 el8',
 'org_id': '3340851',
 'repository_uuids': ['bd473a30-69f3-4ffe-b86e-c7c433a20540',
                      '6168cd88-f36d-4224-aec2-6dfd8eee7a37'],
 'rhsm_environment_id': '0bcf3753e81f48ccb40c64a7210f27d9',
 'uuid': '0bcf3753-e81f-48cc-b40c-64a7210f27d9',
 'version': '8'}

In [4]: app.content_sources.rest_client.templates_api.list_template_errata('0bcf3753-e81f-48cc-b40c-64a7210f27d9',limit=10,offset=30)
2024-06-03 16:22:14.893 [    INFO] [iqe.base.rest_client] REST: METHOD=GET, request_id=<>, params=[('limit', 10), ('offset', 30)]
Out[4]:
{'data': [{'cves': [],
           'description': 'Ansible is a simple model-driven configuration '
                          'management, multi-node\n'
                          'deployment, and remote-task execution system. '
                          'Ansible works over SSH and\n'
                          'does\n'
                          'not require any software or daemons to be installed '
                          'on remote nodes.\n'
                          'Extension\n'
                          'modules can be written in any language and are '
                          'transferred to managed\n'
                          'machines\n'
                          'automatically.\n'
                          '\n'
                          'The following packages have been upgraded to a '
                          'newer upstream version:\n'
                          'ansible\n'
                          '(2.8.1)\n'
                          '\n'
                          'Bug Fix(es):\n'
                          '\n'
                          'See:\n'
                          'https://github.com/ansible/ansible/blob/v2.8.1/changelogs/CHANGELOG-v2.8.rst\n'
                          'for details on bug fixes in this release.',
           'errata_id': 'RHBA-2019:1433',
           'id': '018fddef-c58c-793e-92ce-8b2bf013864f',
           'issued_date': '2019-06-11 08:15:49',
           'reboot_suggested': False,
           'severity': 'None',
           'summary': 'Ansible 2.8.1 release for Ansible Engine 2',
           'title': 'Ansible 2.8.1 release for Ansible Engine 2',
           'type': 'bugfix',
           'updated_date': '2019-06-11 08:15:49'},
          {'cves': [],
           'description': 'Ansible is a simple model-driven configuration '
                          'management, multi-node\n'
                          'deployment, and remote-task execution system. '
                          'Ansible works over SSH and does not require any '
                          'software or daemons to be installed on remote '
                          'nodes. Extension modules can be written in any '
                          'language and are transferred to managed machines '
                          'automatically.\n'
                          '\n'
                          'The following packages have been upgraded to a '
                          'newer upstream version: ansible (2.8.0)\n'
                          '\n'
                          'Bug Fix(es):\n'
                          '\n'
                          'See:\n'
                          'https://github.com/ansible/ansible/blob/v2.8.0/changelogs/CHANGELOG-v2.8.rst\n'
                          'for details on bug fixes in this release.',
           'errata_id': 'RHEA-2019:1251',
           'id': '018fddef-c5e8-7c20-aa84-7b5abeabb8d6',
           'issued_date': '2019-05-21 10:06:22',
           'reboot_suggested': False,
           'severity': 'None',
           'summary': 'Ansible 2.8.0 release for Ansible Engine 2 on RHEL8',
           'title': 'Ansible 2.8.0 release for Ansible Engine 2 on RHEL8',
           'type': 'enhancement',
           'updated_date': '2019-05-21 10:06:22'},
          {'cves': [],
           'description': 'Gorilla_Erratum',
           'errata_id': 'RHEA-2012:0058',
           'id': '018fde45-ae93-7ff2-93b7-0ad017c2a0cc',
           'issued_date': '2013-01-27 16:08:09',
           'reboot_suggested': False,
           'severity': '',
           'summary': '',
           'title': 'Gorilla_Erratum',
           'type': 'enhancement',
           'updated_date': ''},
<snip>
          {'cves': [],
           'description': 'Bear_Erratum',
           'errata_id': 'RHSA-2012:0057',
           'id': '018fde45-ae8d-7e8e-a92e-a615cfa29cf4',
           'issued_date': '2013-01-27 16:08:05',
           'reboot_suggested': False,
           'severity': 'Moderate',
           'summary': '',
           'title': 'Bear_Erratum',
           'type': 'security',
           'updated_date': ''},
<snip>
          {'cves': [],
           'description': 'Kangaroo_Erratum',
           'errata_id': 'RHBA-2012:1030',
           'id': '018fde45-ae96-7533-a918-f60e2f80d5ee',
           'issued_date': '2012-01-08 10:40:38',
           'reboot_suggested': False,
           'severity': '',
           'summary': '',
           'title': 'Kangaroo_Erratum',
           'type': 'bugfix',
           'updated_date': ''},
          {'cves': [],
           'description': 'acme-package_Erratum description',
           'errata_id': 'RHSA-2009:1425',
           'id': '018fde45-ae90-7e2d-bc2b-c5193913bcf8',
           'issued_date': '2009-05-20 00:00:00',
           'reboot_suggested': False,
           'severity': 'Low',
           'summary': '',
           'title': 'acme-package_Erratum',
           'type': 'security',
           'updated_date': ''}],
 'links': {'first': '/api/content-sources/v1/templates/0bcf3753-e81f-48cc-b40c-64a7210f27d9/errata?limit=10&offset=0',
           'last': '/api/content-sources/v1/templates/0bcf3753-e81f-48cc-b40c-64a7210f27d9/errata?limit=10&offset=30',
           'prev': '/api/content-sources/v1/templates/0bcf3753-e81f-48cc-b40c-64a7210f27d9/errata?limit=10&offset=20'},
 'meta': {'count': 38, 'limit': 10, 'offset': 30}}

[2] https://issues.redhat.com/browse/HMS-4242


[Explanations on offline data]

Hi, I have question on offline data specification.
When I loaded the one of npz file, I noticed that all the keys like 'action' or 'reward' or 'terminal' have size of 1001.
Did you just put dummy 'action', 'reward', 'terminal' for the first element?
I mean if the original sequence is O_0, a_0, r_0, t_0, O_1, a_1, r_1, t_1, ... (O: image, a: action, r: reward, t: terminal), is the offline data formed as O_0, a_-1, r_-1, t_-1, O_1, a_0, r_0, t_0, ... (a_-1, r_-1, t_-1 are some dummy values) ?
Thanks.

Yes, that is correct. The first entry of action, reward, and terminal are indeed "dummy" zero values.


Unable to login to hue after upgrading to 4.7.1

Using helm chart we upgraded hue from  20220308-140101 to 4.7.1, when we open the login page it is showing some errors. The errors in hue pod is.
Unknown column 'axes_accessattempt.trusted' in 'field list.
Steps to reproduce it?
Install hue with version 20220308-140101 and then using helm upgrade to 4.7.1 version.

sorry got to know we are downgrading it which causes the problem