Notification web_hook payload transforms "<" to unicode characters

Describe the bug
on dynatrace_notification resource, payload of nested_schema web_hook transforms "<" to unicode characters
To Reproduce
Steps to reproduce the behavior:

Create a dynatrace_notification resource of web_hook type and use "<" on the payload.
Go to dynatrace website to find the new created resource and will find "\u003c" on the message notification

Expected behavior

Create a dynatrace_notification resource of web_hook type and use "<" on the payload.
Go to dynatrace website to find the new created resource and will find "<" on the message notification

Additional context
Changing value via website works as expected with "<"
Thanks in advance!

Hello @estif95, I am unable to reproduce the issue you're describing. We haven't made any changes in resource dynatrace_notification for months. Therefore it's likely that this has been an issue on the Dynatrace REST API side that has been resolved recently.
What version of Dynatrace are you using Terraform with? I am currently testing against v1.266.116.
The resource I am testing with looks like this:
resource "dynatrace_notification" "dynatrace_webhook_notification" {
  web_hook {
    name                   = "tf_dynatrace_webhook_notification"
    accept_any_certificate = true
    active                 = false
    alerting_profile       = "c21f969b-5f03-333d-83e0-4f8f136e7682"
    notify_event_merges    = true
    payload                = "web-hook-payload < web-hook-payload"
    url                    = "https://webhook.site/40bf4d43-1a50-4ebd-913d-bf50ce7c3a0a"
    header {
      name  = "http-header-name-01"
      value = "http-header-value-01"
    }
    header {
      name  = "http-header-name-02"
      value = "http-header-value-02"
    }
  }
}

Hello, thanks for reviewing and answering the issue! Reviewing the problem again it seems a Terraform behaviour with jsonencode function and unicode characters. I managed to deploy your snippet code and it works as expected. We were sending a complex json payload with multiple double quotes and single quotes "" ''. Closing the issue as is not related with dynatrace provider.
Thanks again and sorry for inconveniences!

Thanks for clarifying!


Handlebars error: Could not find component or helper

Hi. I am trying to use the component in my template, after installing it via NPM.
  {{async-button action="save" default="Save" pending="Saving..."}}

However, when running the app, I get this error:
Uncaught Error: <my@view:search-map::ember831> Handlebars error: Could not find component or helper named 'async-button'

Any idea why?

what version of ember, ember-cli, handlebars, etc... ?

Ah, I suspect it's my Handlebars version?
DEBUG: Ember                     : 1.9.1
ember.js:3935 DEBUG: Ember Data                : 1.0.0-beta.14.1
ember.js:3935 DEBUG: Handlebars                : 2.0.0
ember.js:3935 DEBUG: jQuery                    : 1.11.2

what version of ember-cli ?

0.1.7

@sbsurf - How did you install?  Is ember-cli-async-button in your package.json?

Sorry guys. I guess I forgot to restart the app after running the install. Thanks for the quick help. Really appreciate it.

No problem, glad you got it fixed.


blog post: preface

This a a first take on tailoring slightly the README for the purposes of a blog post. Your review is only required for the (new) "preface" part, the rest of the README is almost unchanged and the IDM part of it will be probably shortened in the final version.
This PR is for communication only, I am not planning (unless you think it is a good idea) on merging it to master.

Since this PR was posted, a new section was added at the end—"Conclusion". Please feel free to check that out as well. Thank you!

I made some changes in the main content; please take the latest commit.

Thanks everyone for your participation.


Object selector gui

This replaces the old and too large object-classification GUI with a new custom widget. closes #26
The widget is also used for the new object-selection GUI:

Tests pass locally:
(bio39) C:\structure\code\napari-accelerated-pixel-and-object-classification>pytest
================================================= test session starts =================================================
platform win32 -- Python 3.9.15, pytest-7.2.0, pluggy-1.0.0
PyQt5 5.15.7 -- Qt runtime 5.15.6 -- Qt compiled 5.15.6
rootdir: C:\structure\code\napari-accelerated-pixel-and-object-classification
plugins: anyio-3.6.2, napari-0.4.17, napari-plugin-engine-0.2.0, npe2-0.6.1, qt-4.2.0
collected 9 items

napari_accelerated_pixel_and_object_classification\_tests\test_functions.py ....                                 [ 44%]
napari_accelerated_pixel_and_object_classification\_tests\test_widgets.py .....                                  [100%]

================================================== warnings summary ===================================================
..\..\..\Users\haase\mambaforge\envs\bio39\lib\site-packages\vispy\app\backends\_qt.py:93
  C:\Users\haase\mambaforge\envs\bio39\lib\site-packages\vispy\app\backends\_qt.py:93: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead.
    if LooseVersion(QT_VERSION_STR) >= '5.4.0':

..\..\..\Users\haase\AppData\Roaming\Python\Python39\site-packages\setuptools\_distutils\version.py:346
  C:\Users\haase\AppData\Roaming\Python\Python39\site-packages\setuptools\_distutils\version.py:346: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead.
    other = LooseVersion(other)

napari_accelerated_pixel_and_object_classification/_tests/test_functions.py::test_object_segmentation
napari_accelerated_pixel_and_object_classification/_tests/test_functions.py::test_probability_mapper
napari_accelerated_pixel_and_object_classification/_tests/test_functions.py::test_annotation_to_cluster_id
napari_accelerated_pixel_and_object_classification/_tests/test_functions.py::test_annotation_to_cluster_id
napari_accelerated_pixel_and_object_classification/_tests/test_widgets.py::test_pixel_training_and_prediction
napari_accelerated_pixel_and_object_classification/_tests/test_widgets.py::test_pixel_training_and_prediction
napari_accelerated_pixel_and_object_classification/_tests/test_widgets.py::test_pixel_training_and_prediction
napari_accelerated_pixel_and_object_classification/_tests/test_widgets.py::test_pixel_training_and_prediction
  C:\Users\haase\mambaforge\envs\bio39\lib\site-packages\pyopencl\__init__.py:270: CompilerWarning: Non-empty compiler output encountered. Set the environment variable PYOPENCL_COMPILER_OUTPUT=1 to see more.
    warn("Non-empty compiler output encountered. Set the "

napari_accelerated_pixel_and_object_classification/_tests/test_widgets.py::test_feature_selector
  C:\structure\code\napari-accelerated-pixel-and-object-classification\napari_accelerated_pixel_and_object_classification\_tests\test_widgets.py:91: FutureWarning: Public access to Window.qt_viewer is deprecated and will be removed in
  v0.5.0. It is considered an "implementation detail" of the napari
  application, not part of the napari viewer model. If your use case
  requires access to qt_viewer, please open an issue to discuss.
    f = FeatureSelector(viewer.window.qt_viewer, "original gaussian_blur=1")

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=========================================== 9 passed, 11 warnings in 27.94s ===========================================


Sync with more recent commits from other docs repo

Motivation
Sync commits from previous docs repo.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Local Docusaurus builds
Related PRs
N/A

/land


Size of string is wrong

When string initializer is parenthesized, its size becomes 1:
const char str[] = {"foo"};

int main() {
    return sizeof(str);
}

Above code should return 4, but 1.

Thanks! This is a bad bug.


[App Configuration] Add the a message when a register has 0 results.

Name of feature to enhance

Currently, if our registers fetch o results they just show a blank page with nothing written on them.
Update this behaviour to function as the mock-up suggest.

Describe the enhancement

[ ] Add a section on the register configs to capture a message to be displayed in case the register has 0 items to display.
[ ] This message should have a title & body. Both of these should be configurable.
[ ] This page should also have a button to add the resource expected on the register. This button however should have the following properties.

[ ] Should be configurable i.e can be hidden or shown.
[ ] Should have a property to configure the text to be shown?
[ ] Should have an actions property to configure the Questionnaire load.

Configuration section sample
{
	"noResults": {
		"id": "noResults",
		"visible": true,
		"title": {
			"display": "{{title}}"
		},
		"body": {
			"display": "{{body}}"
		},
		"button": {
			"id": "noResultsButton",
			"visible": true,
			"display": "{{text}}",
			"actions": [
				{
					"trigger": "ON_CLICK",
					"workflow": "LAUNCH_REGISTER",
					"id": "householdRegister",
					"questionnaire": {
						"id": "82952",
						"title": "{{add.family}}",
						"saveButtonText": "ADD FAMILY",
						"setPractitionerDetails": true,
						"setOrganizationDetails": true
					}
				}
			]
		}
	}
}

Design Mockups

NB: - This should part of the register configs and not a config on it's own.

Technical Scoping:

Create a new domain/mode data class

NoResultsConfig(val title:String = "", val message: String = "",val actionButton: NavigationMenuConfig? = null)

Update RegisterConfiguration by adding new property noResults of type NoResultsConfig
Update the RegisterScreen Composable view by rendering a Column of view above views (The bold text - title; the text in the middle - message and a button that uses actionButton) when paginItems is empty.
Otherwise render the RegisterCardList.

Proposed JSON
{
  "noResults": {
    "title": "{{title}}",
    "message": "{{body}}",
    "actionButton": {
      "id": "noResultsButton",
      "visible": true,
      "display": "{{text}}",
      "actions": [
        {
          "trigger": "ON_CLICK",
          "workflow": "LAUNCH_REGISTER",
          "id": "householdRegister",
          "questionnaire": {
            "id": "82952",
            "title": "{{add.family}}",
            "saveButtonText": "ADD FAMILY",
            "setPractitionerDetails": true,
            "setOrganizationDetails": true
          }
        }
      ]
    }
  }
}

NOTE: Should be part of RegisterConfiguration

@dubdabasoduba  Can I please get a link to Figma for this design mockup?


Safe co-iteration across an axis for 1+ arrays

This should help with #62. The main idea is that we can get the convenience of checking compatible indices like in eachindex(A...), but for specific axes. Possible concerns may be:

I decided to have indices(x) always return iterable indices instead of a tuple of indices. So the default behavior is like eachindex. This does two things for us:

The behavior of for i in indices(args...) ... end is more predictable becaues i can always point to a single value of the array(s).
It makes it very easy to incorporate/extend for other array/array-like types. If the behavior is unique to each axis then only indices(x) needs to be specified. If the behavior is unique for the array then only indices(x, i) needs to be specified.

I didn't implement any special behavior for combining/optimizing known range first/last/step although it was mentioned in #62. I figured even a minimal range type would be meaty enough for an independent PR.

If people don't find the first point compelling enough to depart from behavior like axes I can change it. I just thought it was a really interesting idea. I'm also happy to implement a range if it's seen as immediately necessary for this PR.

I didn't implement any special behavior for combining/optimizing known range first/last/step although it was mentioned in #62. I figured even a minimal range type would be meaty enough for an independent PR.

I would like to see this.
I'd like to add that instead of the pattern matching, I'd like the iterators to also track an is-dense along the lines of https://github.com/SciML/ArrayInterface.jl/pull/61.
Then that would provide all the information I'd need to implement the optimizations I talked about, i.e.:

Possibility of flattening some subset of loops, CartesianIndexing -> LinearIndexing style.
Realizing that stride values must necessarily be equal between arrays, to avoid spilling integer registers.

I'd like to add that instead of the pattern matching, I'd like the iterators to also track an is-dense along the lines of #61.

Are you referring to something that does something like stridelayout(::Type{T}) -> (contig, batch, striderank) for each axis, or just flattening out the results of indices when possible?

I forgot to add axesdense to the list of returns: stridelayout(::Type{T}) -> (contig, batch, striderank, axesdense).
So that'd mean consolidating the axesdense information.
The reason I want that info from the axis iterator rather than to read it directly from the arrays is:
A = rand(10, 5);
for i in 1:3, j in 1:4
    A[i,j] *= 2
end

A is dense, but that doesn't mean these loops could be flattened.

Are you thinking of something like this?
is_dense(::Type{T}, i::Int) where {T} = nothing
is_dense(::Type{<:Array}, i::Int) = true
@inline function is_dense(::Type{<:Union{Transpose{T,A},Adjoint{T,A}}}) where {T,A<:AbstractMatrix{T}}
    return is_dense(A, (2, 1)[i])
end
@inline function is_dense(::Type{<:PermutedDimsArray{T,N,I1,I2,A}}, i::Int) where {T,N,I1,I2,A<:AbstractArray{T,N}}
    return is_dense(A, I1[i])
end

I don't really see how an iterator along each dimension in isolation can incorporate the density since it requires knowing about the previous dimensions and strides.

Something like:
is_dense(::Type{T}, i) where {T} = last(stridelayout(T))[i]

I don't really see how an iterator along each dimension in isolation can incorporate the density since it requires knowing about the previous dimensions and strides.

You're right. Given what I said:
A = rand(2,3,4);
B = PermutedDimsArray(rand(4,3,2), (3,2,1));
for k in indices((A,B),3), j in indices((A,B),2), i in indices((A,B),1)
    # do something with A[i,j,k] and B[i,j,k]
end

These each of these should be dense, even though we obviously can't flatten the loops.
However, we could flatten them if we only had A or if we only had B.
That is, is_dense by itself does not provide enough information, but I think it does in conjunction with stridelayout.
I.e., in querying whether we can flatten two loops, we need to check:

That they share the same order among all arrays indexed by them (provided by stridelayout)
That the loop with the smaller stride is_dense/covers the full axis for each of them (information must be provided by the stride-iterator).

This sounds a lot like what Slice is for. Would it make sense to wrap whatever we get from indices into something like Base.Slice or should we have a unique type that's "co-slicing"?

Okay, if that's the understood meaning of Slice.
Simply doing that, and then checking stridelayout to see if all the sliced dimensions are dense sounds like a good approach to me.
Meaning indices only has to accumulate statically known first/last/step.

One last question and I think I can get something more polished together. Base.Slice only accepts AbstractUnitRange. Do you need OptinallyStaticRange to be capable of having different step sizes?

Maybe add
struct OptionallyStaticUnitRange{T,F,L} <: AbstractUnitRange{T}
    start::F
    stop::L
end

maybe_slice(r) = r
function maybe_slice(r::OptionallyStaticRange{T,F,::Val{1},L}) where {T,F,L}
    Base.Slice(OptionallyStaticUnitRange{T,F,L}(first(r), last(r)))
end

Then you could use maybe_slice(reduce(_pick_range, inds)).

I would really love if we had a common interface where someone could do this with a new type
function Base.length(r::NewRangeType{T}) where where{T}
    if isempty(r)
        return zero(T)
    else
        return ArrayInterface.unsafe_length(first(r), step(r), last(r))
    end
end

But that turns into a lot of code very quickly and I should probably save that for a different PR. Would it be okay if I just do a unit range thing for now and then we can see how everyone feels about a more aggressive range focused PR later that could include OptionallyStaticStepRange?

I would really love if we had a common interface where someone could do this with a new type

Do you mean, define an interface such that length will work in that manner?
Defining your own abstract type that they could subtype (along with defining first, etc) would be easiest, otherwise wouldn't you need a PR on base Julia to do this with traits without committing type piracy? Or am I missing something?
The OptionallyStaticStepRange is fine.
Are we going to make it so that the type promises to be a full slice? Or do you want to still wrap the returns in Base.Slice?

Do you mean, define an interface such that length will work in that manner?
Defining your own abstract type that they could subtype (along with defining first, etc) would be easiest, otherwise wouldn't you need a PR on base Julia to do this with traits without committing type piracy? Or am I missing something?

I think it would ultimately need to be in base but there are a lot of little problems with how ranges are implemented in base and we'd need to start by getting the known_* methods there first.

Are we going to make it so that the type promises to be a full slice? Or do you want to still wrap the returns in Base.Slice?

I think it might be good to still wrap the return in Base.Slice because then things like getindex(A, indices(...)) can know that it represents and inbounds collection.

I think this looks good. Are you happy with it?

With this final change I think it's good. Now you can use indices like eachindex but it will give you a slice so you now it spans the fully array of each.


AGPUSH-1325 : add page parameter builder function

@edewit and now the Java Sender , to be merged after https://github.com/aerogear/aerogear-unifiedpush-server/pull/517

landed


lib.packagesFromDirectoryRecursive: mark directories with recurseIntoAttrs

Split off #359984, at this requires fixes in the BSD package sets.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] Tested, as applicable:

[x] tests in lib/tests

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[x] (Function updates) Added a release notes entry if the change is significant

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I've been trying my hardest to nuke freebsd.ports. I think it's a bit of a code smell to have in nixpkgs, since it's hard to make it play nice with the rest of the tree... If we can't get rid of it now then I suppose it should be fixed, but I'm making a :grimacing: face.

Doesn't this break everyone's usage of packagesFromDirectoryRecursive? I love how simple and useful that function is, but turning its inputs from a set to a function seems counter-intuitive for most use cases. Couldn't this be a separate lib function instead of breaking packagesFromDirectoryRecursive?

The scope-related machinery is optional, and not used by default; there might be a misunderstanding rather anything “breaking.”

It's very likely that I misunderstood the diff. I thought the optional newScope attribute defaulted to a throw, making it effectively mandatory and forcing every usage of packagesFromDirectoryRecursive to define a scope.

I see! Thank you for explaining; since this doesn't alter packagesFromDirectoryRecursive's current behaviour, feel free to disregard my concerns.


Define interface for crypto

Description
Defining a new trait for crypto stuff
Checklist

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)
[x] My code follows the code style of this project.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.
[ ] CHANGELOG is updated.

I don't get the reason behind separating bls from crypto module but if you are trying to decouple it I think using bls implementation directly in the code base is wrong pass while we have crypto interfaces for that matter. in test files it might be right to use bls concrete implementation while I think even there we better off with dummy, default or mock implementation or even use crypto to proxy to bls implementation rather than directly using it and barely introducing crypto interfaces.
I found the links below helpful about interfaces https://www.integralist.co.uk/posts/go-interfaces/#interfaces-in-go https://www.efekarakus.com/golang/2019/12/29/working-with-interfaces-in-go.html https://blog.chewxy.com/2018/03/18/golang-interfaces/

Yes, the test looks to be not beautiful after this PR. The main reason behind this PR, is to give type to address. Now address in 20 bytes, we can add one more bytes (type bytes) to assign a type to an address. In future we can support another more algorithm  other than BLS.


add button shortcode feature

the theme could be better if it has a button shortcode feature, something like this:
https://learn.netlify.com/en/shortcodes/button/

What would you do with the buttons?
Do you want to use it to the external link?

yes

I added the button shortcode
https://zzodocs.netlify.com/docs/shortcodes/button/

ok great I tested this feature it and added this shortcode to my post
{{< button href="https://google.com"  >}}download{{< /button >}}
but doesn't appear any button

Can you try this?
{{< button href="https://google.com" color="primary">}}download{{< /button >}}

Can you try this?

yes I tried and it works great thanks :1st_place_medal:

Did you update the theme?

yes I updated

Try force refresh the browser

also, I tried this trick and it works too :+1:
it was my mistake sorry

great!
So, the button is as you expected one?
Can we close this issue now?

yes it's great thanks


Add support for generic load/store on byte-addressed buffers

Introduction
The HLSL *ByteAddressBuffer types originaly only supported loading/storing uint values or vectors of the same, using Load/Load2/Load3/Load4 or Store/Store2/Store3/Store4. More recent versions of dxc have added support for generic Load<T> and Store<T>, which adds a two main pieces of functionality for users.
The first and more fundamental feature is that T can be a type that isn't 32 bits in size (or a vector with elements of such a type), thus exposing a capability that is difficult or impossible to emulate on top of 32-bit load/store (depending on what guarantees *StructuredBuffer makes about the atomicity of loads/stores).
The secondary benefit of having a generic Load<T> and Store<T> is that it becomes possible to load/store types like float without manual bit-casting, and also becomes possible to load/store struct types so long as all the fields are loadable/storable.
This change adds generic Load<T> and Store<T> to the Slang standard library definition of byte-address buffers, and tries to bring those same benefits to as many targets as possible. In particular, the secondary benefits become available on all targets, including DXBC: byte-address buffers can be used to directly load/store types other than uint, including user-defined struct types, so long as all of the fields of those types can be loaded/stored.
The ability to load/store non-32-bit types depends on target capabilities, and so is only available where direct support for those types is available. For 16-bit types like half this includes both Vulkan and D3D12 DXIL with appropriate extensions or shader models.
The implementation is somewhat involved, so I will try to explain the pieces here.
Standard Library
The changes to the Slang standard library in hlsl.meta.slang are pretty simple. We add new Load<T> and Store<T> generic methods to *ByteAddressBuffer, and route them through to a new IR opcode.
Right now the generic Load<T> and Store<T> do not place any constraints on the type T, although in practice they should only work when T is a fixed-size type that only contains "first class"
uniform/ordinary data (so no resources, unless the target makes resource types first class). Our front-end checking cannot currently represent first-class-ness and validate it (nor can it represent fixed-size-ness), so these gaps will have to do for now.
Rather than directly translate Load<T> or Store<T> calls into a single instruction, we instead bottleneck them through internal-use-only subroutines. The design choice here is intended to ensure that for some large user-defined type like MassiveMaterialStruct we only emit code for loading all of its fields once in the output HLSL/GLSL rather than once per load site. While downstream compilers are likely to inline all of this logic anyway, we are doing what we can to avoid generating bloated code.
Emit and C++/CUDA
Over in slang-emit-c-like.cpp we translate the new ops into output code in a straightforward way. A call like obj.Load<Foo>(offset) will eventually output as a call like obj.Load<Foo>(offset) in the generated code, by default.
For the CPU C++ and CUDA C++ codegen paths, this is enough to make a workable implementation, and we add suitable templated Load<T> and Store<T> declarations to the prelude for those targets.
Legalization
For targets like DXBC and GLSL there is no way to emit a load operation for an aggregate type like a struct, so we introduce a legalization pass on the IR that will translate our byte-address-buffer load/store ops into multiple ops that are legal for the target.
Scalarization
The big picture here is easy enough to understand: when we see a load of a struct type from a byte-address buffer, we translate that into loads for each of the fields, and then assemble a new struct value from the results. We do similar things for arrays, matrices, and optionally for vectors (depending on the target).
Bit Casting
After scalarization alone, we might have a load of a float or a float3 that isn't legal for D3D11/DXBC, but that would be legal if we just loaded a uint or uint3 and then bit-casted it. The legalization pass thus includes an option to allow for loads/stores to be translated to operate on a same-size unsigned integer type and then to bit-cast.
To make this work actually usable, I had to add some more details to the implementation of the bit-cast op during HLSL emit and, more importantly, I had to customize the way that the byte-address buffer load/store ops get emitted to HLSL so that it prefers to use the existing operations like Load/Load2/Load3/Load4 instead of the generic one, whenever operating on uints or vectors of uint.
Translation to Structured Buffers
Even after scalarizing all byte-address-buffer loads/stores, we still have a problem for GLSL targets, because a single global buffer declaration used to back a byte-address buffer can only have a single element type (currently always uint), so the granularity of loads/stores it can express is fixed at declaration time. If we want to load a half from a byte-address buffer, we need a dedicated buffer declaration in the output GLSL with an element type of half.
The solution we employ here is to translate all byte-address buffer loads into "equivalent" structured-buffer ops when targetting GLSL. We add logic to find the underlying global shader parameter that was used for a load/store and introduce a new structured-buffer parameter with the desired element type (e.g., half) and then rewrite the load/store op to use that buffer instead. We copy layout information from the original buffer to the new one, so that in the output GLSL all the various buffers will use a single binding and thus alias "for free."
We don't want to create a new global buffer for every load/store, so we try to cache these "equivalent" structured buffers as best as we can. For the caching I ended up needing a pair to use as a key, so I tweaked the KeyValuePair<K,V> type in core so that it could actually work for that purpose.
Because we are working at the level of IR instructions instead of stdlib functions at this work I had to add new IR opcodes to represent structured-buffer load/store that only (currently) apply to GLSL.
Layout
In order to translate a load/store of a struct type into per-field load/store we need a way to access layout information for the types of the fields. Previously layout information has been an AST-level concern that then gets passed down to the IR only when needed and only on global parameters, so layout information isn't always available in cases like this, at the actual load/store point.
As an expedient move for now I've introduced a dedicated module that does IR-level layout and caches its results on the IR types themselves. This approach only supports the "natural" layout of a type, and thus is usable for structured buffers and byte-address buffers (or general pointer load/store on targets that support it), but which is not usable for things like constant buffer layout.
We've known for a while that the Right Way to do layout going forward is to have an IR-based layout system, and this could either be seen as a first step toward it, or else as a gross short-term hack. YMMV.
Details
The GLSL "extension tracker" stuff around type support needed to be tweaked to recognize that types like int16_t aren't actually available by default. I switched it from using a "black list" of unavailable types at initialization time over to using a "white list" of types that are known to always be available without any extensions.
Tests
There are two tests checked in here: one for the basic case of a struct type that has fields that should all be natively loadable, and one that stresses 16-bit types. Each test uses both load and store operations.
Future Directions
Right now we translate vector load/store to GLSL as load/store of individual scalars, which means the assumed alignment is just that of the scalars (consistent with HLSL byte-address buffer rules). We could conceivably introduce some controls to allow outputting the vector load/store ops more directly to GLSL (e.g., declaring a buffer of float4s), which might enable more efficient load/store based on the alignment rules for buffers.
The IR layout work has a number of rough edges, but the most worrying is probably the assumption that all matrices are laid out in row-major order. Slang really needs an overhaul of its handling of matrices and matrix layout, so I don't know if we can do much better in the near term.
At some point the IR-based layout system needs to be reconciled with our current AST-base layout, and we need to figure out how "natural" layout and the currently computed layouts co-exist (in particular, we need to make sure that the IR-based layout and the existing layout logic for structured buffers will agree). This probably needs to come along once we have moved the core layout logic to operate on IR types instead of AST types (a change we keep talking about).
As part of this work I had to touch the implementation of bit-casting for HLSL, and it seems like that logic has some serious gaps. We really ought to consider a separate legalization pass that can turn IR bitcast instructions into the separate ops that a target actually supports so that we can implement uint64_t<->double and other conersions that are technically achievable, but which are hard to express in HLSL today.

Something I wasn't totally clear on was on glsl structured buffer/buffer comment
"We copy layout information from the original buffer to the new one, so that in the output GLSL all the various buffers will use a single binding and thus alias "for free.""
I can bind to different types of buffer to the same binding?

I can bind to different types of buffer to the same binding?

Sorta kinda. There's a bunch of distinct buffer types in HLSL that all map to the same kind of buffer declaration in the output GLSL, including all of the *StructuredBuffer and the *ByteAddressBuffer types. From a GLSL language and Vulkan API standpoint those are all "shader storage buffers."
The Vulkan SPIR-V rules allow for multiple global shader parameters that have the same binding, and it is okay to access multiple parameters that overlap like that so long as the type of the parameter in GLSL/SPIR-V is consistent with the descriptor that actually got bound via the API.
What we are doing in the Slang IR here is a little slippery in terms of layout, in that the layout information for a structured buffer might have extra data about the layout of the elements, which a layout for byte-address buffer would lack, but this pass occurs late enough in the compiler that no code would look for or use that additional information (and I'm not even sure we represent that information in the IR layout representation today).


Minorfixes matike

Coverage increased (+0.02%) to 69.308% when pulling e4e74a2d038a5d5314b336232457c3e6247b67a8 on minorfixes-matike into 4888b03cdeffde143dbb7faa03932a454bd01cc4 on master.

LGTM.


Fix the jq error caused by containers list ordering

This pr fixes the following jq issue.
oc get csv -n openstack-operators    -l operators.coreos.com/openstack-operator.openstack-operators -o=jsonpath='{.items[0]}' | jq '(.spec.install.spec.deployments[1].spec.template.spec.containers[1].env[] | select(.name=="RELATED_IMAGE_RABBITMQ_IMAGE_URL_DEFAULT")) |= (.value="<IP_ADDRESS>:5001/podified-antelope-centos9/openstack-rabbitmq:2fb21c9cd4251727b2f260ca5d6f2ebb")'
jq: error (at <stdin>:0): Cannot iterate over null (null)

The container list got changed from 1 to 0 breaking the set_openstack_containers role due to update in kubeproxy or operator sdk. Shifting it to 0 fixes the issue.
As a pull request owner and reviewers, I checked that:

[ ] Appropriate testing is done and actually running

Closing in favor of https://github.com/openstack-k8s-operators/ci-framework/pull/1231


examples/clock: works with Firefox but not Chrome

Environment
go version go1.16.5 darwin/amd64
macOS 10.14.6
chrome 91.0.4472.164
firefox 90.0.1
To replicate
git clone git@github.com:jfyne/live-examples.git
cd live-examples/clock
go build .
cd ..
clock/clock

Point browser at http://localhost:8080/clock
What I expected
Incrementing clock
What I saw
With Firefox, everything is OK.
With Chrome, current time is displayed, but does not increment.
tcpdump shows that websocket messages are being sent every second:
$ sudo tcpdump -i lo0 -nn -s0 -A tcp port 8080
...
08:47:28.831040 IP6 ::1.8080 > ::1.50406: Flags [P.], seq 1:269, ack 810, win 6359, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 268: HTTP: HTTP/1.1 101 Switching Protocols
<EMAIL_ADDRESS>;.G.;.G.HTTP/1.1 101 Switching Protocols
Connection: Upgrade
Sec-Websocket-Accept: J1GHBBuREgeNFGWhZQUIYbi8YQ4=
Sec-Websocket-Extensions: permessage-deflate; client_no_context_takeover; server_no_context_takeover
Upgrade: websocket
Date: Thu, 22 Jul 2021 07:47:28 GMT

08:47:28.831077 IP6 ::1.50406 > ::1.8080: Flags [.], ack 269, win 6367, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 0
`..f<EMAIL_ADDRESS>/.....(.....
;.G.;.G.
08:47:28.831177 IP6 ::1.8080 > ::1.50406: Flags [P.], seq 269:288, ack 810, win 6359, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 19: HTTP
<EMAIL_ADDRESS>/...v.....;.....
;.G.;.G...{"t":"connect"}..
08:47:28.831197 IP6 ::1.50406 > ::1.8080: Flags [.], ack 288, win 6367, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 0
`..f<EMAIL_ADDRESS>B.....(.....
;.G.;.G.
08:47:29.834266 IP6 ::1.8080 > ::1.50406: Flags [P.], seq 288:471, ack 810, win 6359, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 183: HTTP
<EMAIL_ADDRESS>B...v...........
;.K.;.G..~..{"t":"patch","d":[{"Path":[0,0],"Action":2,"HTML":"\u003ctitle\u003e 08:47:29 \u003c/title\u003e"},{"Path":[1,0],"Action":2,"HTML":"\u003ctime\u003e08:47:29\u003c/time\u003e"}]}..
08:47:29.834302 IP6 ::1.50406 > ::1.8080: Flags [.], ack 471, win 6364, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 0
`..f<EMAIL_ADDRESS>......(.....
;.K.;.K.
08:47:30.839156 IP6 ::1.8080 > ::1.50406: Flags [P.], seq 471:654, ack 810, win 6359, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 183: HTTP
<EMAIL_ADDRESS>....v...........
;.O.;.K..~..{"t":"patch","d":[{"Path":[0,0],"Action":2,"HTML":"\u003ctitle\u003e 08:47:30 \u003c/title\u003e"},{"Path":[1,0],"Action":2,"HTML":"\u003ctime\u003e08:47:30\u003c/time\u003e"}]}..
08:47:30.839203 IP6 ::1.50406 > ::1.8080: Flags [.], ack 654, win 6361, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 0
`..f. .@.......................................v.p!......(.....
;.O.;.O.
08:47:31.842699 IP6 ::1.8080 > ::1.50406: Flags [P.], seq 654:837, ack 810, win 6359, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 183: HTTP
`......@.....................................p!....v...........
;.S.;.O..~..{"t":"patch","d":[{"Path":[0,0],"Action":2,"HTML":"\u003ctitle\u003e 08:47:31 \u003c/title\u003e"},{"Path":[1,0],"Action":2,"HTML":"\u003ctime\u003e08:47:31\u003c/time\u003e"}]}..
08:47:31.842764 IP6 ::1.50406 > ::1.8080: Flags [.], ack 837, win 6358, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 0
`..f. .@.......................................v.p"g.....(.....
;.S.;.S.

I don't see any errors in browser console, although network shows stuck at "101 Switching Proto..."

Additional info
With both Chrome and Firefox, closing the browser tab logs the following at the server side:
2021/07/22 08:47:01 ws closed with status (-1): writing to socket error: failed writeTimeout: json: error calling MarshalJSON for type json.RawMessage: invalid character 'i' in literal false (expecting 'l')

I suspect an error message starting with the word "fail" has been put in RawMessage field without being quoted, e.g. see https://play.golang.org/p/w9Vuc8Ko_fN
EDIT: now raised separately as #26

I can't replicate this although sometimes I see something similar happening in Firefox. I will keep trying

Just to bump this. I'm not sure if I should create an additional issue. But I am seeing a failures for buttons as well. Following nearly identical process I ran buttons on chrome and inc and dec are throwing error client side:
patch.ts:35 unhandled patch, path target undefined


add service account impersonation

Signed-off-by: Brad Wadsworth<EMAIL_ADDRESS>Description of your changes
Allow ImpersonateServiceAccount as an authentication source and specify a service account to impersonate. Configuration docs have also been updated.
Fixes #204
I have:

[X] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested
Tested on a Workload Identity enabled GKE cluster with a GCP service account for the provider pod and a GCP service account to impersonate. The new option was able to create a GCS bucket using account impersonation.

Require status checks changed please rebase this PR.

Any update on this being merged?

Any movement on this PR?
Looking to do the same thing.


Dashboard application running on AWS, secured with Azure AD + OpenID Connect

(Milestone)
Wellcome staff with the necessary Active Directory account privileges can use the dashboard for the same functions they currently use in the on-premise version.

Question: What cachebusting functionality will still be required from the dashboard?

@jtweed @kenoir we now have a limited but functioning dashboard app - can we get this registered so that it appears on the Azure portal? What's the process for this?
Having it visible like this is a good spur to progressing it (you can all see what we're doing) and obviously exercises our rapid/continuous delivery approach.
From our end it will be something like this:
https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-v2-aspnet-core-webapp
But I assume that D&T will need to register the app(s).
We'll actually need 3 apps - prod, stage, and the hybrid version that uses prod source material (i.e., prod storage API content) with stage Dds code (e.g., staging a change in what goes into Manifests).
But one will do for now, we can start with the production one.
Question - who needs to see it?
Is it like the Goobi app that really only a few people ever use, so lives in the special Azure portal for devs? I don't know who has access to that.
Right now, I can send wt-havana dashboard links to lots of people (within Wellcome), post them on shared Slack etc, to show how the digital objects are structured or demonstrate something for discussion. This has proved fairly useful on occasion.
You can't do any damage to source data in the dashboard. It isn't the origin of any data; you can trigger reprocessing but you can't edit things. It's a window on how METS becomes IIIF. So it could have wider availability than Goobi.

I think that @kenoir can create these. They should be linked to wellcome.ac.uk accounts, so that @aray-wellcome and co can access without needing dev accounts.
@aray-wellcome will know who should have access.

@kenoir @tomcrane The way DDS is set up now, anyone on my team can view it but only some of us had the logins that give us the ability to bust cache and force re-ingests.
I'd like to keep the ability of everyone on my team to be able to view the dashboard, if possible so it'd be:
Me
Harkiran Dhindsa
Branwen Lloyd-Evans
Christy Henshaw
Holly Peel
Rosie Curran
Emilie Bell
Daila Malafronte
Paul Horn
Cassidy Philips
If access to the prod dashboard gives everyone the power to reingest and bust cache as well, that's fine.

Added basic AzureAD authentication to dashboard and deployed to AWS. Currently setup to only let Wellcome Cloud users in. There are no role/claims based restrictions yet.
PRs:

https://github.com/wellcomecollection/iiif-builder/pull/6
https://github.com/wellcomecollection/iiif-builder-infrastructure/pull/2

Have example dashboard endpoint, secured by AzureAD at: https://dds-stage.dlcs.io/Home/Index/b18402768 (url will be altered eventually).
This proves that we can:

Access Wellcome S3 buckets
Pull secrets from SecretManager
Get data from DLCS
Access deployed RDS DB


Institution/ Ministry - Deactivate Program

User Story
As an Institution or Ministry User, I may need to deactivate a program. This could be due to no longer offering it, or creating it in error resulting in a new revised program being created.
Current Behaviour
Programs exist forever and institution users just update the program name/description to indicate it should not be used.
Expected Behaviour
Institution users AND Ministry users can "deactivate" a program:

This will change the flag beside each program to indicate it has a different status.

Programs with this flag will no longer be visible to students or PSIs in dropdowns for applications/PIRs. (Applications, PIR)

Attached offerings will not be affected.

Active applications attached to the offerings under this program will not be affected.

Deactivated programs cannot be "reactivated". (PSIs can make a new program)

Deactivated programs can not have new offerings added to it.

Bulk upload will ignore deactivated programs if they match SABC Program codes.

Update to "Edit" button on Program Details to a Drop-down selection with new pop-up modal:

Acceptance Criteria

[ ] Add new state for programs: Inactive
[ ] Update status flag for programs to show the "Inactive" flag in dashboards.
[ ] Update edit button on Program details screen to drop down with two options: Edit Program, Deactivate. (No change to functionality of "Edit Program")
[ ] New pop up when user selects "Deactivate"
[ ] Update new program creation validation to ignore any deactivated programs. (i.e. so that the same SABC Program Code can be re-used on the new Programs)
[ ] Update bulk upload to ignore deactivated programs when assigning offerings.

@CarlyCotton - really like this ticket, I think it will be great improvement.

Likely for the Devs to sort out during implementation, but are we sure changing the status to 'inactive' doesn't muck up the student's NoA, the IER, others back end stuff?
Can users deactive a program when it is still in 'pending' status?
What happens to attached students who need to change study information mid-application? Like they need to change study period info which is initiated by the school assigning them to new programs & offerings via dropdown menus? I think we're fine with business process where they'll have to assign them to entirely new program/offering, right?
What happens to offerings which are cloned during scholastic standing - they should still be added to the deconmissioned program. We just basically disable the UX/UI button for 'add offering' as well as the Bulk Upload route.
Should programs with effective dates which 'expire' automaticaly change to 'inactive' status? What happens to them currently when they reach their effective end date (I believe they stop appearing in student dropdowns, but still appear as active in th Institution's program inventory.

Some other things for us to consider that might need seperate tickets:

This doesn't solve the issue of "D restrictions", i.e. how to shut down a program to new entrants while letting existing affiliated students continue to submit new, future applicaitons to that program.
We'll likely need an equivalent way of decomissioning offerings, but let's learn from this ticket first and see if any tweaks are needed

Likely for the Devs to sort out during implementation, but are we sure changing the status to 'inactive' doesn't muck up the student's NoA, the IER, others back end stuff?

Interested to hear more from them re impacts on existing applications or anything else.

Can users deactive a program when it is still in 'pending' status?

I think they should - this would be helpful if they made one that they didn't expect to be pending. It'll save time for ministry users and institutions for them to just deactivate.

What happens to attached students who need to change study information mid-application? Like they need to change study period info which is initiated by the school assigning them to new programs & offerings via dropdown menus? I think we're fine with business process where they'll have to assign them to entirely new program/offering, right?

If it's in draft, I expect it to handle like other changes to designation/offerings and just removes the drop down selection and forces a new selection. I'll clarify this in the expected behaviour.

What happens to offerings which are cloned during scholastic standing - they should still be added to the deconmissioned program. We just basically disable the UX/UI button for 'add offering' as well as the Bulk Upload route.

I think this is a good distinction - not blocking the add offering, but disabling it from a UI standpoint and ignoring them during bulk upload.

Should programs with effective dates which 'expire' automaticaly change to 'inactive' status? What happens to them currently when they reach their effective end date (I believe they stop appearing in student dropdowns, but still appear as active in th Institution's program inventory.

They currently continue to show a status of "Approved" and are not visible in new application drop-downs. They are not able to have the expiry extended through another review process, but right now if they had a SABC program code to reuse they wouldn't be able to re-create.

We'll likely need an equivalent way of decomissioning offerings, but let's learn from this ticket first and see if any tweaks are needed

This is something I considered. Offerings can be "decommissioned" by changing it to private and they eventually drop off based on PY cycle. The concept of private programs could start resolving D restrictions.

@CarlyCotton questions from DEVs:

Should we capture the user deactivating the program (Institution or Ministry)?
If the Ministry is deactivating it, should we add a note to the Institution notes?

@andrewsignori-aot

Please keep a record of who made the change, this doesn't need to be displayed on the Program.
Yes please! If Ministry users could be asked to add an Institution Note with a type of "Program" when doing the deactivate. (if this is a large functionality add please let me know and we can consider it for future enhancement)

@CarlyCotton
Regarding number 1, I believe that makes sense too. We did it in other areas.
Regarding number 2, we have some framework in place and by default every time that Ministry does an action "on behalf" of the institution we try to insert a related note.
I will add these two items to the technical details.
Thanks for the clarifications 😉

@CarlyCotton
I added item 1 as a technical AC and item 2 as a business AC: "When the Ministry is deactivating, include a basic Notes section (not part of the mockup) to save a note to the institution's notes under the Program category."

@CarlyCotton regarding the Ministry approving an offering-related change request (Application Offering Change and Bulk Offering change) should the Ministry be allowed to approve a request for an inactive program?
Should the student be able to approve an Application Offering Change for an inactive program?

@CarlyCotton for implementation we are splitting this ticket into two. The first ticket will change in the UI changes and the second one in applying the constraints (#2930).

@andrewsignori-aot

regarding the Ministry approving an offering-related change request (Application Offering Change and Bulk Offering change) should the Ministry be allowed to approve a request for an inactive program?
Should the student be able to approve an Application Offering Change for an inactive program?

A change to an offering itself should be able to be actioned regardless of the program being active/inactive. There needs to be a way for these to be actioned out of the pending offering queue and we don't want to auto-decline simply because the program is inactive. (It is possible that a change needs to be made on the offering with applications attached, which we want to keep functioning as normal. Just no NEW applications to these. (Possibility of future re-activation enhancements would also be affected by auto-declining.)
Request A Change process
At this time we don't want the schools to be able to select the deactivated program from the Request A Change feature.
If there are pending requests (waiting on student or ministry action) to change an application into a program that becomes deactivated, we don't want to stop that process. If it was already "in motion" before the deactivation, it can continue "in motion".

@andrewsignori-aot

regarding the Ministry approving an offering-related change request (Application Offering Change and Bulk Offering change) should the Ministry be allowed to approve a request for an inactive program?
Should the student be able to approve an Application Offering Change for an inactive program?

A change to an offering itself should be able to be actioned regardless of the program being active/inactive. There needs to be a way for these to be actioned out of the pending offering queue and we don't want to auto-decline simply because the program is inactive. (It is possible that a change needs to be made on the offering with applications attached, which we want to keep functioning as normal. Just no NEW applications to these. (Possibility of future re-activation enhancements would also be affected by auto-declining.)
Request A Change process At this time we don't want the schools to be able to select the deactivated program from the Request A Change feature. If there are pending requests (waiting on student or ministry action) to change an application into a program that becomes deactivated, we don't want to stop that process. If it was already "in motion" before the deactivation, it can continue "in motion".

Thanks for the clarification @CarlyCotton.
Regarding editing an offering we have:

Scenario A, "no application is associated with the offering", the institution can freely edit the offering and programs are not involved in this.
Scenario B, "some application is associated with the offering" which will create new "versions" of the same offering for history and for the Ministry approval. For this scenario we should allow the system to create the new offerings under the program even if it is deactivated, right?

@andrewsignori-aot

Scenario A, "no application is associated with the offering", the institution can freely edit the offering and programs are not involved in this.
Scenario B, "some application is associated with the offering" which will create new "versions" of the same offering for history and for the Ministry approval. For this scenario we should allow the system to create the new offerings under the program even if it is deactivated, right?

Scenario A - exactly
Scenario B - it's fine for biz if the system creates a new offering on a deactivated program.

@HRAGANBC checking Keycloak, we have been creating the new roles just under admins groups. Related to the below AC
"Make this feature/role available to all Groups within Ministry KeyCloak configs"
can we create just under the aest-business-administrators till we have further clarifications on the roles?
@CarlyCotton @Joshua-Lakusta FYI

@CarlyCotton there is a minor difference between Institution and Ministry program actions.

The institution will display "Edit program" while the Ministry will see "View program".
When program are no longer editable, for instance, when an offering is added, the menus also display "View program".
Can we have the action button named as "Program actions" for both the Ministry and institutions, as shown below?
Also I will disable the "Deactivate" button and the program page will be displayed as read-only. Does it make sense?

@andrewsignori-aot The changes look great. Business is good with the Deactivate being blocked out and the switch from "Edit program" to "View Program" once deactivated.

As agreed with @CarlyCotton even though not explicitly mentioned in the AC, the program view for inactive programs is read-only for now for consistency and to avoid further updated in a no longer active program.


[WIP] Add DocumentFragment.prototype.getElementById

Based on a patch by @Zirro from IRC, with my own tests added. However, this does not work, because the functions in Element-impl.js that update the _ids collection do not care about DocumentFragment containers.
I'm unsure how to proceed. I guess one route is to have totally separate implementations of getElementById for Document and DocumentFragment, with the DocumentFragment version doing a whole traversal. That seems relatively easy. Alternately we could try to develop some kind of caching system, and a notation of "root" i.e. furthest ancestor.
Thoughts welcome.

I guess one route is to have totally separate implementations of getElementById for Document and DocumentFragment, with the DocumentFragment version doing a whole traversal.

That'd be very okay with me, really. Implement first, speed up later.
However:

However, this does not work, because the functions in Element-impl.js that update the _ids collection do not care about DocumentFragment containers.

Do we not have the elementAttached thing which we could use for that? Does that bubble to the documentfragment?

Hmm, I kind of assumed attached only worked on documents, not document fragments. But I didn't check.

@domenic a couple of notes on gEBID implementation... Nodes/Elements attached to a DocumentFragment always have their isConnected property set to 'false'. So the isConnected thing only works for real Documents (nodeType 9).
Also recall that the HTML5 spec allows for duplicated ID in the same document, thus I believe that would be true also for DocumentFragment (nodeType 11). Does 'jsdom' allow duplicated ID in the same document ?

Updated with separate Document and DocumentFragment implementations. It seems to work. Anyone up for reviewing?
I'll try nwsapi on top of this next. BTW @dperini, sorry for not answering your question. Yes, just like in a browser, multiple elements can have the same ID in jsdom.

Commit msg has WIP still 😁


Apply-PnPProvisioningTemplate Access Denied

Hi, I need deploy a template from DEV envieroment to PRD, when i test the import into TST envieroment, the process is successfull but when the same template is importe en PRD, the follow error appers

and in tracelog file the error is

the PRD enverioment is a root site collection

Hi,
Thanks for your feedback. This is an engine related issue/request. Could you please insert this item, if still needed, in the PnP-Sites-Core repository (https://github.com/SharePoint/PnP-Sites-Core/issues/)? Thanks. I will close this item, because out of context.


Gets lost in node_modules

I embed a node app in the same directory as the go code.
pkger spins forever then crashes.
Is there a way to exclude some paths?
Attempted to build pkger but wasn't successful.
C:\work1\dev\server\goMods\jobServer\slicerQ (default)
λ pkger -include C:\work1\dev\server\goMods\jobServer\slicerQ\jsClient\dist
2020/05/28 17:36:02 here.Dir: C:\work1\dev\server\goMods\jobServer\gui\node_modules\highlight.js\lib\languages: here.cache: C:\work1\dev\server\goMods\jobServer\gui\node_modules\highlight.js\lib\languages: [go list -json] fork/exec go.js: %1 is not a valid Win32 application.: : {"file"

Same problem here, I want it to look only into folders like cmd, pkg and not any other directory.
Currently it fails with open ... : permission denied as it's reading directories that it should not.

I'd also welcome an option (e.g., -exclude) for ignoring particular directories while parsing.
there already exists a list of ignored directories (interestingly including node_modules), but there seemingly is no option for manually specifying such directories. the fs traversal mechanism resides here: https://github.com/markbates/pkger/blob/992ea93a2ade0cff2d9e4ac4e767eb858a4d27bd/parser/parser.go#L175-L228

Same.  Running it in a mono repo with tonnes of other stuff like front ends.  I run pkger in the root of the backend go project.
It takes 5 minutes, then returns error about trying to parse node_modules which is in ../XX/node_modules in relation to the cwd
I don't know what it's doing or why it's trying to search the root project when I'm running the command in a folder.  My presumption would be that it just creates the pkger.go file and then allows you to specify static files, but it's trying to do something automated that isn't clear in the readme.


RC4 - Variable changes made inside the function assigned to ionScroll output event don't get updated on the view.

Ionic version:  (check one with "x")
[ ] 1.x
[x ] 2.x
I'm submitting a ...  (check one with "x")
[x ] bug report
[ ] feature request
[ ] support request
Current behavior:
Variable changes made inside the function assigned to ionScroll, ionScrollStart or ionScrollEnd output events don't get updated on the view. The change doesn't occur when scrolling starts, continues or ends. However, if I click on a component that emits an event, after scrolling stopped, the variable change occurs.
Expected behavior:
The changes made to the variables to be updated on the view as expected.
Steps to reproduce:
See the plunker below:
http://plnkr.co/edit/WGgNm4px3S5cWOKVWqrc?p=preview
Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
 ordova CLI: 6.3.1
Ionic Framework Version: 2.0.0-rc.4
Ionic CLI Version: 2.1.17
Ionic App Lib Version: 2.1.7
Ionic App Scripts Version: 0.0.47
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 10
Node Version: v4.4.4
Xcode version: Not installed

A possible workaround for your problem:
http://plnkr.co/edit/mLH7yt2scKpHWpbFavmd?p=info
I imported ChangeDetectorRef and called detectChanges() inside your toggleFab method.

The problem is deeper, the angular's changeDetector doesn't do it's job anymore.
Some of my components does not update until 30 seconds if I don't call a changeDetect manually after specifics functions.
It's ruining all the concept of angular T_T

I also noticed same issues after we upgrade ionic2 from rc3 to rc5 and angular 2 from 2.1.1 to 2.2.1. Can ionic 2 wrap the event to the zone if angular 2 does not want to do it by default globally? It is really inconvenient for the developers to manually wrap the event handler in the zone.


Questions regarding Eureka client cache behavior

Eureka client cache gets refreshed every 30 sec (eureka.client.registryFetchIntervalSeconds). If the server doesn't protect the registry in the event of a network outage, does the client cache gets wiped out on the next registry fetch?  I do know that the client only attempts to fetch the delta from the last retrieval, so if there's nothing to compare to, I'd think that the aforementioned statement would be correct, but want to confirm.

When the client is given multiple Eureka server URLs, and it registers with the first one, but later can't connect to it, does it purge the cache before going to the second Eureka server in the list?

The cache won't get wiped if it cannot connect via the network. For #2 AFAIK, no.

The cache won't get wiped if it cannot connect via the network
@spencergibb Please confirm that "it" means Eureka server. Just so that we're on the same page, The scenario I described is that Eureka server is running in peer-peer mode and self-preservation is off, so during a network outage between peers (not between client and server), the registry got wiped out.

"It" is the eureka client.

@spencergibb In that case, my 1st question remains. If client loses connectivity with server, it makes sense to not purge the cache. But if client can connect to server, and finds an empty registry, or otherwise changed if not empty, what does it do? Since it fetches delta every time, does the delta also consist of deletions?

If the version doesn't match to get a delta it will do full refresh. Otherwise, the deltas handle deletions.

Can you explain the concept of the version? I don't remember seeing it mentioned in Spring docs or Netflix Wiki. From your response, it sounds like the server returns a version with the registry, but even if that's true, I'm not clear how the version might change.

Closing due to age of the question. If you would like us to look at this issue, please comment and we will look at re-opening the issue.


Roll Flutter Engine from ab034478aeab to 5cbc8f79d791 (4 revisions)

https://github.com/flutter/engine/compare/ab034478aeab...5cbc8f79d791
2023-02-27<EMAIL_ADDRESS>Actually print out if xcrun metal fails (flutter/engine#39926)
2023-02-27<EMAIL_ADDRESS>[Impeller] Add texture->texture blits to device capabilities (flutter/engine#39924)
2023-02-27<EMAIL_ADDRESS>Remove unused flag skia_canvaskit_enable_particles (flutter/engine#39925)
2023-02-27<EMAIL_ADDRESS>Fix shader doc references (flutter/engine#39855)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC chinmaygarde@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


The documentation link on crates.io doesn't work

It looks like the documentation link in Cargo.toml is broken. It is "https://docs.rs/crate/stm32f1xx-hal" but I think it should be "https://docs.rs/stm32f1xx-hal" without crate.
Or you can just leave the documentation key out. Crates.io auto-generates a link to docs.rs if none is specified.
I'm not sure if this is the only problem though because the documentation doesn'tseem to have been generated on docs.rs at all for this crate.

Looks like the link was fixed in 67aa99e but the docs generation is still broken, most likely because the required changes to Cargo.toml ([package.metadata.docs.rs]) have not been published to docs.rs yet. @therealprof should we push a new version or is there something else that needs fixing before we do that?

No I think you're right. I already saw the fix but was waiting for the change to be published. I think docs.rs pulls from crates.io so the docs should show up after publishing.

@TheZoq2 Yeah, we should also bump the stm32f1 version.


How to disable Facebook Comments?

Hi,
I would love to know if it is possible  to disable the facebook comments area.
Thanks

Check your config (_config.yml) there is a string called fb-comment and it is set by default to true, simply change it to false.


about the data translating tool im2rec, is there any option to add new images to the existing rec file?

Hi,
I have about 50G images for training, and it takes me about 2 hours to translate the images to rec file.
And I will receive thousands of new images period by period, then include them in the new training.
So i need to re-generate the rec file. Is there any way i can just add the new images to the existing rec file instead of re-create the rec file from the very beginning? That will save a lot of time.
Thanks a lot.

@GoodJoey : Could you also post this on discuss.mxnet.io? You will get a wider audience there.
@sandeep-krishnamurthy : Could you tag this "question"

Closing the issue. Please ask usability questions at discuss.mxnet.io for faster response


Fix all prompt formats

As discussed here, all llama 2 endpoints templates prompt formats are off. The ground truth can be found in RayLLM. In RayLLM, we test for "prompt format consistency with the following format:
llama2_prompt_format = PromptFormat(
    system="<<SYS>>\n{instruction}\n<</SYS>>\n\n",
    assistant=" {instruction} </s><s>",
    trailing_assistant="",
    user="[INST] {system}{instruction} [/INST]",
    default_system_message="",
    system_in_user=True,
)

https://github.com/anyscale/ray-llm/blob/9fb9f710dd717429c54968d1c23d2f7b60e7d8f9/tests/test_aviary/common/test_prompt_format_consistency.py#L4
This format is also aligned with llm-forge.
Only the endpoints templates are different.
CC @mjconnor @akshay-anyscale

please also copy to endpoints_v2

@akshay-anyscale This PR includes the changes to the v2 folder already! So there is nothing left to change

great thanks!


Use new restful starring endpoints

Use the new restful starring endpoint
For dockstore/dockstore#2395

Need webservice change


Set sidebar status from build result

Use the new experimental_updateStatus API to set the sidebar status as build results come in.

It's not totally clear what statuses we should be setting (success or unknown for passing/accepted tests?). There are a lot of details to work through, but the wiring is there.

Note to run this right now you need to install the addon into a sandbox on the release/7.2 branch, like so:
  addons: [
    '@storybook/addon-links',
    '@storybook/addon-essentials',
    '@storybook/addon-onboarding',
    '@storybook/addon-interactions',
    {
      name: '/Users/tom/GitHub/chromaui/addon-visual-tests/dist/index.js', // or similar
      options: {
        projectId: '64acdc2151cdda2cb8b7eaaf',
        projectToken: 'chpt_4c07aba6aed67ce',
      },
    },
  ],

📦 Published PR as canary version: 0.0.6--canary.11.393cf3c.0

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

I moved the memoization to the use effect, can you take a look @ndelangen?


fix: Instances stuck restarting for non-interruptible, long-running queries

If we have the restartedAt annotation, and the pod is older than this annotation, and the pod has been not ready for over 30 seconds, delete the pod.
This case is applicable to queries that do not handle the smart or fast postgres shutdown procedures. For example executing a PL/Python function that's long running is not interrupted even by fast shutdown, and instead needs immediate shutdown.

Working on a test for this


AsyncApp, check static file modified use error api.And when dev, use adapter when read should set content_length, otherwise block

whitenoise 4.0 could modify api.

Closing this off given that 0.6 is moving to a framework-agnostic suite of API tools, and will no longer include the server. See https://discuss.apistar.org/t/api-star-as-a-framework-independant-tool/614 and #624.


It's a maze game involving numerous levels, with a caveat that includes gateways. Gateways act like portals, instantly teleporting the main character from one location in the maze to another.
How do you play your game?
WASD to move.
Code
Check off the items that are true.

[x] The game was made using the Sprig editor.
[x] The game is placed in the in the /games directory.
[x] The code is significantly different from all other games in the Sprig gallery (except for games labeled "demo").
[x] The game runs without errors.
[x] The name of the file/game contains only alphanumeric characters, -s, or _s.
[x] The game name is not the same as the others from gallery

Thanks for your PR!

Hi @Cosmin-Mare!
Thanks for the quick response. I have added more levels and a death option! Please take a look as soon as you can!

@Cosmin-Mare Sorry, when testing the code I let the level start at 11. Now, that is fixed and the game begins at the first level. It should take longer than 1 minute to complete!


Full ontology tree experiment parent name filtered no root

Let's get this merged in so we can re-ground the reader output before the experiment?
fyi @MihaiSurdeanu  @Fan-Luo

This branch is not meant for checking into master and I should delete the PR.  It is the base branch for the grounding experiments.  useW2V = true cannot be used in the master branch because we can't test or run with w2v.  Full caching cannot be used with the grounding experiments because the ontology caching was highly optimized and doesn't support the operations needed for the experiments.  If master needs to be cacheable, then the compact ontology representation needs to be reworked.  I believe the code here was hacked so that the vector file could still be cached while the ontologies wouldn't be.  It might not be possible to use a configuration setting for parents on/off and still cache in as an efficient manner as previously.  The code used for the recent reading is in DART-42k* and includes some of this code.  It should be able to reground.

OK -- so then we'll need to reground?  I looked on the DART4-42k* branches and it seems that DART4-42k-B and DART4-42k-B1532 both have the parentName grounding implemented,
(a) was the latest output we sent to Ben run with one of these branches and if so, was this non-leaf node grounding activated? thanks!

I think so -- since we got "conflict" as one of the groundings -- thanks!

It was at least intended that grounding was activated and to the flattened version at that, and not to the props at all.  I did some checks that indicated that the settings were effective.

Awesome, thanks!
On Wed, Dec 25, 2019 at 7:26 AM Keith Alcock<EMAIL_ADDRESS>wrote:

It was at least intended that grounding was activated and to the flattened
version at that, and not to the props at all. I did some checks that
indicated that the settings were effective.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/clulab/eidos/pull/730?email_source=notifications&email_token=ABJCPCPEOZBQPZSZHYU3OQDQ2NUPVA5CNFSM4J67ZXRKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHUMZOA#issuecomment-568904888,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJCPCK3LZLH6BPDIVWTV7LQ2NUPVANCNFSM4J67ZXRA
.


Virtualbox image is missing nixos nix-channel

Issue description
Virtualbox image is missing nixos nix-channel.
Steps to reproduce

Download NixOS 18.09.1819.76aafbf4bf4 VirtualBox image.

[demo@nixos:~]$ sudo nix-channel --list
[sudo] password for demo:

[demo@nixos:~]$ nix-channel --list

Technical details
[demo@nixos:~]$ nix-shell -p nix-info --run "nix-info -m"
these paths will be fetched (20.03 MiB download, 217.86 MiB unpacked):
  /nix/store/4m253khy42mqrv3l3kih6ar75fvi0wl5-bash-interactive-4.4-p23-dev
  /nix/store/9qrxkya37d0ajls3yygy0ry268p805v7-stdenv-linux
  /nix/store/b0yc8vswfzcanhdm6dgmfmdcgjmxvxa0-binutils-2.30
  /nix/store/nwy73lby94rv8jql92xhxp0wx6gxwjb2-gcc-wrapper-7.3.0
  /nix/store/p3rksdhjr1sr5rvg99vb20cki03ay29g-binutils-wrapper-2.30
  /nix/store/vnqkf6mb6ja0lrfb9frvhnlr3pfs2sfr-expand-response-params
copying path '/nix/store/4m253khy42mqrv3l3kih6ar75fvi0wl5-bash-interactive-4.4-p23-dev' from 'https://cache.nixos.org'...
copying path '/nix/store/b0yc8vswfzcanhdm6dgmfmdcgjmxvxa0-binutils-2.30' from 'https://cache.nixos.org'...
copying path '/nix/store/vnqkf6mb6ja0lrfb9frvhnlr3pfs2sfr-expand-response-params' from 'https://cache.nixos.org'...
copying path '/nix/store/p3rksdhjr1sr5rvg99vb20cki03ay29g-binutils-wrapper-2.30' from 'https://cache.nixos.org'...
copying path '/nix/store/nwy73lby94rv8jql92xhxp0wx6gxwjb2-gcc-wrapper-7.3.0' from 'https://cache.nixos.org'...
copying path '/nix/store/9qrxkya37d0ajls3yygy0ry268p805v7-stdenv-linux' from 'https://cache.nixos.org'...
 - system: `"x86_64-linux"`
 - host os: `Linux 4.14.90, NixOS, 18.09.1819.76aafbf4bf4 (Jellyfish)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.1.3`
 - channels(demo): `""`
 - channels(root): `"nixos-18.09.1819.76aafbf4bf4"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

It should have root channels installed. You have to use sudo -i with nix-channel unfortunately:
sudo -i nix-channel --list

(That issue was fixed in https://github.com/NixOS/nix/pull/2400 & will hopefully be available for 19.03)


Force currentTimestamp to all trades sorted and remove btcex

Removing btcex
Force timestamp to currentTimestamp() to avoir different timezones from exchanges
the matTrade method sorts the trades according to their IDs or their timestamp, so we shouldn't have to worry about order, and using the currentTimestamp() allows us to have consistency in the data we will send to WS clients

@JamesGDiaz


Integration with Actions addon?

It would be nice to integrate with the actions addon so request data could be made visible within the actions tab.

This is an interesting request. @kettanaito if we want to improve the addon by providing a panel to visualize the requests, would that be doable with https://mswjs.io/docs/extensions/life-cycle-events#tracking-a-request ?
This is an example of a panel from the miragejs addon, where they show the request and response:

Hey.
You can track requests and responses as they happen using the Life-cycle API that you've linked. Add-ons like the above is precisely why such API was designed. Give it a try and let me know if there's any challenges it imposes.

Hey.
You can track requests and responses as they happen using the Life-cycle API that you've linked. Add-ons like the above is precisely why such API was designed. Give it a try and let me know if there's any challenges it imposes.

Thank you @kettanaito! I will make some experimentations in a near future

@coler-j I made some experimentations with addon actions and here are my findings.
You can use actions in preview.js for unhandled requests:
// .storybook/preview.js
import { action } from '@storybook/addon-actions'
import { initialize } from 'msw-storybook-addon'

initialize({
  onUnhandledRequest: (request) => {
    // very likely add an if here for requests which you don't care to track, e.g. images or fonts
    action('unhandled request')(request)
  }
})

And it looks like this:

And for the story, you can call the action in the callback of the MSW handler:
import { action } from '@storybook/addon-actions'

YourStory.parameters = {
  msw: [
    rest.get(YOUR_URL, (request, response, ctx) => {
      action('get request')(request) // register the action to appear in addon-actions:
      return response(ctx.json(mockData))
    }),
  ],
}

which would look like this:

I think the idea to create a panel for the add-on may be more suitable than utilizing onUnhandledRequest callback. We could hook into the request:unhandled life-cycle event instead inside the add-on, as we have access to the worker/server instance.
But first of all, we need to consider the usefulness of such a panel compared to the Network tab of the browser's devtools.


Create symbol_squeezenet.py

model compression techniques
compress SqueezeNet to less than 1MB(461x smaller than AlexNet)

model compression techniques
compress SqueezeNet to less than 1MB(461x smaller than AlexNet)

Have you checked the results?

FastPoor is much faster than this net, and similarly has near Alexnet performance. The key is compression but not structure.

@antinucleon What I recommend is to create a better name for fast_poor, like fit_net and have a documentation on what it is on the classification folder. We can also optionally include this in, if people want to compare

@tqchen Where is fast_poor

@winstywang  I will give a result about this net, maybe days later.

let us have a update on this. I am going to merge this in if people are OK with it. but it would be great if @qiaohaijun can post the results check in first.

Without further applying Deep Compression [1] on the SqueezeNet network, the model size reduction compared with the AlexNet is 50x. The proposed Fire module is very similar to a mini version of GoogLeNet's Inception module. Is it possible to compress and accelerate Inception-v4 or Inception-ResNet-v2 using the SqueezeNet method?
[1] S. Han, H. Mao, and W. Dally. Deep compression: Compressing DNNs with pruning, trained quantization and huffman coding. arxiv:1510.00149v3, 2015.

FastPoor is here.

In the provided file symbol_squeezenet.py the variable num_classes is not used;
should it be put in  conv10 module as num_filter=1000?

Moreover, in this version the output size is 9000, but the classes are only 1000!
I think that the global average method

http://arxiv.org/abs/1312.4400
should be implemented as a mx.symbol.GlobalAveragePooling symbol

I have resolved this issue by looking at the size of each output layer with infer_shape, ex.
arg_shape, output_shape, aux_shape = conv1.infer_shape(data=(1,3,224,224))
If you look at the size given in the paper, the lines that you need to change is
conv1 = mx.symbol.Convolution(data=data, kernel=(7,7), stride=(2,2), num_filter=96, pad=(2,2))
and
conv10 = mx.symbol.Convolution(data=dropout_fire9, kernel=(1,1), num_filter=1000)

Btw, we still need a new operator 'average pooling', otherwise the output size won't match the label size

I would like to commit this file with the corrected version, how can I do that?

@tmatas  sorry so late, I am training the new network, using your suggestion


DockPanel.ActiveDocument is one step behind with DockingMdi style

The DockPanel.ActiveDocument value holds the previous active document when switching between documents with keyboard shortcuts (Ctrl+Tab, Shift+Ctrl+Tab) or by selecting document from the Window menu.
Steps to reproduce:

Load the WinFormsUI.Docking.sln.
Open MainForm in the designer.
Add ActiveDocumentChanged event handler to the dockPanel control.
Edit the created event handler to look like this:

    if (this.dockPanel.ActiveDocument != null)
        System.Diagnostics.Debug.WriteLine(this.dockPanel.ActiveDocument);

Build and run.
Create 3 empty documents (File -> New). The Visual Studio Output window should contain 3 lines, the last one being "DockSample.DummyDoc, Text: Document3". (http://imageshack.us/photo/my-images/600/32047518.png)
Go to the Window menu and select "1 Document1". The active tab changes to the "Document1", but there is no new line in the Output window, meaning the event handler wasn't invoked. (http://imageshack.us/photo/my-images/405/78826564.png)
Go to the Window menu again and select "2 Document2". This time the event handler was invoked, but the last line shows, that the ActiveDocument property contains the previous active document (Document1). (http://imageshack.us/photo/my-images/19/64776299.png)
The above step can be repeated multiple times, but the ActiveDocument property will always be one step behind.
Now activate some other window (Toolbox for example). The event handler is immediately invoked and the Output window contains the line with the correct ActiveDocument property value. (http://imageshack.us/photo/my-images/834/19438604.png)

The issue is not present when activating tab with a mouse button.
Testing environment: latest DockPanel Suite source (commit 7154d18125f9f49e91de9e60f84f2171bfc73f6f), Windows 7 x64, Visual Studio 2008.

hi i m getting the similar error
i m trying to switch the current tab to next next open tab
this.DockPanel.ActiveDocument = totalActiveTab[i];
to open the next tab open but its giving an error
can some one please say where i  am making mistake

@Raviraj2017 what you asked has nothing to do with the original issue. Post a new one please.


CODEOWNERS, PR template

PR template
CODEOWNERS
Cleanup

@Arriven may we ask with @Amet13 to have Triage role in the repo? According to https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository doc this role allows to manage issues and pull requests

@Arriven relates to https://github.com/Arriven/db1000n/pull/187#pullrequestreview-901101286 as well

@Arriven can we discuss providing certain restricted access to the repo? How can I reach you out?
email or telegram?


ROX-13519: Enable search on API tokens

Description
A detailed explanation of the changes in your PR.
Feel free to remove this section if it is overkill for your PR, and the title of your PR is sufficiently descriptive.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
TODO(replace-me)
Use this space to explain how you tested your PR, or, if you didn't test it, why
you did not do so. Valid reasons include, for example, "CI is sufficient",
"No testable changes". Feel free to attach JSON snippets, curl commands,
screenshots.
In addition to reviewing your code, reviewers must also review your testing
instructions and make sure they are sufficient.

/test all

/test all

Will be tackled in https://github.com/stackrox/stackrox/pull/4968 .


[SPARK-14157][SQL] Parse Drop Function DDL command

What changes were proposed in this pull request?
JIRA: https://issues.apache.org/jira/browse/SPARK-14157
We only parse create function command. In order to support native drop function command, we need to parse it too.
From Hive manual, the drop function command has syntax as:
DROP [TEMPORARY] FUNCTION [IF EXISTS] function_name;
How was this patch tested?
Added test into DDLCommandSuite.

cc @yhuai @andrewor14

Test build #54177 has started for PR 11959 at commit f0c43b9.

Test build #54177 has finished for PR 11959 at commit f0c43b9.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class DropFunction(

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54177/
Test PASSed.

Let me submit a PR for parsing TOK_DESCDATABASE and TOK_DROPDATABASE.

Test build #54245 has started for PR 11959 at commit b0f449d.

Test build #54245 has finished for PR 11959 at commit b0f449d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54245/
Test PASSed.

Test build #54251 has started for PR 11959 at commit 0038563.

Test build #54251 has finished for PR 11959 at commit 0038563.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54251/
Test PASSed.

Test build #54259 has started for PR 11959 at commit 021e7c7.

Test build #54259 has finished for PR 11959 at commit 021e7c7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54259/
Test PASSed.

Test build #54268 has started for PR 11959 at commit db23480.

Test build #54268 has finished for PR 11959 at commit db23480.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54268/
Test PASSed.

ping @yhuai

LGTM. Merging to master. Thanks!


How to change the LCN number

Hi,
Can someone help me out how to change the lcn number. I tried below all the possible commands but it's not changing. I am able to change the service name but lcn number is not changing
tsp -I file input.ts -P svrename XYZ -l 71 -n "test2" -O file output.ts - Using service name
tsp -I file input.ts -P svrename 0x0468 -l 71 -n "test2" -O file output.ts - Using service ID
tsp -I file input.ts -P svrename 58 -l 71 -n "test2" -O file output.ts - Using LCN number
tsp -I file input.ts -P svrename xyz -l "40" -O file output.ts - Using service name
Please can anyone help me out on this.

What do you mean by "it's not changing"? How do you see the output LCN values?
The LCN is unfortunately defined by no standard. The LCN can be defined in a number of different ways, using private descriptors. Sometimes, it is not even defined at all. The most common way to define it is to use the EACEM-defined private descriptor named logical_channel_number_descriptor. This is what the plugin svrename is processing.
So, if the input file contains a NIT with EACEM-defined logical_channel_number_descriptors, then the rename operation will modify them with the new LCN value. If any other operator-specific method is used to specify LCN values, then you cannot change them.
To check the content of the NIT, please post the output of:
tstables input.ts -p 0x10 -t 0x40

What do you mean by "it's not changing"? How do you see the output LCN values?
The LCN is unfortunately defined by no standard. The LCN can be defined in a number of different ways, using private descriptors. Sometimes, it is not even defined at all. The most common way to define it is to use the EACEM-defined private descriptor named logical_channel_number_descriptor. This is what the plugin svrename is processing.
So, if the input file contains a NIT with EACEM-defined logical_channel_number_descriptors, then the rename operation will modify them with the new LCN value. If any other operator-specific method is used to specify LCN values, then you cannot change them.
To check the content of the NIT, please post the output of:
tstables input.ts -p 0x10 -t 0x40

Please find the NIT dats:
Descriptor 1: unknown (0x83, 131), 96 bytes
0000:  04 5C 80 41 03 F5 80 15 03 F9 80 17 05 1E  ..A..........
000E:  80 74 04 98 80 70 05 66 80 1A 05 4E 80 6A  .t...p.f...N.j
001C:  05 84 80 72 05 62 80 73 04 6E 80 2D 04 5E  ...r.b.s.n.-.^
002A:  80 2C 04 1F 80 49 04 05 80 51 04 06 80 46  .,...I...Q...F
0038:  04 10 80 4A 04 20 80 47 05 2C 80 80 05 6A  ...J. .G.,...j
0046:  80 4C 04 28 80 1C 05 18 80 71 04 99 80 6F  .L.(.....q...o
0054:  04 2A 80 75 04 D0 80 76 05 28 80 86        .*.u...v.(..
- Descriptor 2: Satellite Delivery System (0x43, 67), 11 bytes
Orbital position: 75.0 degree, east
Frequency: 12.16000 GHz
Symbol rate: 45.0000 Msymbol/s
Polarization: linear - vertical
Modulation: DVB-S2, 8PSK, alpha=0.35.
Please help me out on this...

Please post the complete NIT or (preferably) attach the binary NIT.
The descriptor 0x83 is probably a private LCN descriptor. But it appears as "unknown". So there is no preceding private data specifier (PDS). We can be only sure after getting the complete NIT.
The most probable cause (and I have already seen that) is that the operator's signalisation is incorrect. In DVB sytems, it is incorrect to have a private descriptor (> 0x7F) without being preceded by the appropriate PDS descriptor. There are several different private descriptors with tag 0x83 and at least two of them are different implementations of an LCN descriptor (one is defined by EACEM and one is defined by Eutelsat). So, in a conformant DVB system, descriptor 0x83 without preceding PDS descriptor is undefined.
But some operators use such incorrect signalisation when their own STB's are coded to directly interpret private descriptors their own way, without checking PDS descriptors. In short, an operator uses incorrect signalisation with incorrect STB's, making a working but non-standard system.
If this is the case, no standard tool such as TSDuck can properly handle the LCN. But we need to get the full NIT to make sure that this hypothesis is correct.


[AKS] az aks create/update: enable mooncake support for managed prometheus addon

Related command
az aks create -n kaveeshcli22 -g kaveeshcli --location westeurope --enable-azure-monitor-metrics --azure-monitor-workspace-resource-id "{full_id}" --grafana-resource-id "{full_id}"
az aks create -n kaveeshcli22 -g kaveeshcli --disable-azure-monitor-metrics
az aks update -n kaveeshcli22 -g kaveeshcli --enable-azure-monitor-metrics --enable-windows-recording-rules
Description

Enabling Managed Prometheus addon for AKS in mooncake

Testing Guide
Scenario (managed prometheus support in mooncake):

Set context to AzureUSGovernment az cloud set --name AzureChinaCloud
Use the command with the grafana-resource-id parameter similar to az aks create -n kaveeshcli22 -g kaveeshcli --location westeurope --enable-azure-monitor-metrics --azure-monitor-workspace-resource-id "{full_id}" --grafana-resource-id "{full_id}" and it should result in a succees

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

AKS


Error with rar file

Thanks for the great work!
I found when searching subtitles with rar file, it always getting this error:
    info: Failed the read enough data.
    TRACE_BACK: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/main.py", line 484, in start
    sub_data_bytes, info_dict, self.single
  File "/usr/local/lib/python3.6/site-packages/main.py", line 397, in extract_subtitle
    sub.write(file_handler.read(sub_name))
  File "/usr/local/lib/python3.6/site-packages/rarfile.py", line 772, in read
    return f.read()
  File "/usr/local/lib/python3.6/site-packages/rarfile.py", line 2010, in read
    raise BadRarFile("Failed the read enough data")
rarfile.BadRarFile: Failed the read enough data

具体是在搜索哪个字幕的时候遇到的呢，因为我下了很多rar都可以的
2017年11月12日 +0800 PM1:22 Chao Ruan<EMAIL_ADDRESS>
Thanks for the great work!
I found when searching subtitles with rar file, it always getting this error:
info: Failed the read enough data.
TRACE_BACK: Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/main.py", line 484, in start
sub_data_bytes, info_dict, self.single
File "/usr/local/lib/python3.6/site-packages/main.py", line 397, in extract_subtitle
sub.write(file_handler.read(sub_name))
File "/usr/local/lib/python3.6/site-packages/rarfile.py", line 772, in read
return f.read()
File "/usr/local/lib/python3.6/site-packages/rarfile.py", line 2010, in read
raise BadRarFile("Failed the read enough data")
rarfile.BadRarFile: Failed the read enough data
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

can you give more details, like searching which episode or movie, choosing which subtitle to download


Party size information on match row

Requires a backend change to supply this data at player_matches/player_caches level

Data added in https://github.com/odota/core/pull/1501


Next alarm not showing

On version 2.2.2 using a Pixel 4XL on Android 11, the next alarm on the widget doesn't show and I can't find the option to bring it back. It was there prior to the recent updates (which are nice and appreciated).

@revdeac06 you can find the option to show the next alarm inside the Glance section.
In case you've already enabled the glance provider, could you please share the popup that is shown?
Thank you

@revdeac06 you can find the option to show the next alarm inside the Glance section.
In case you've already enabled the glance provider, could you please share the popup that is shown?
Thank you

That fixed it, sorry that I didn't see that option.

That fixed it, sorry that I didn't see that option.


Claimable balance example contract (demonstrates timelock).

What
Example ledger timestamp access (https://github.com/stellar/soroban-examples/issues/72)
As the relevant part is pretty small/trivial, I also took this as an opportunity to try a slightly different storage style and also tried to add more test coverage than the other examples.
Why
Adding more Soroban examples
Known limitations
N/A

@dmkozh This PR was closed automatically because the dev branch was deleted. Can you reopen this against the main branch?


NVM not loading default version properly

Open a new terminal window and the default version is not loaded, cfr. https://github.com/creationix/nvm/issues/758
Perhaps a clue in https://stackoverflow.com/questions/24585261/nvm-keeps-forgetting-node-in-new-terminal-session can be found.

Switched to zsh+nvm plugin.


Where is Utils.formatUrl coming from?

I can't find any similar packages

@planktonrobo that is an arbitrary code example snippet that is not part of this lib.  I'll consider removing it to avoid confusion in the future. Thanks.


[Feature] Scatter with Marginal Histogram

What problem does this feature solve?
It presents an integrated presentation of data - scatter plot with marginal histogram. Examples from other application are below.

Matplotlib
Matlab
R ggplot2

What does the proposed API look like?
Both scatter and histogram as already in place.  The question is how to integrate them in single display.

https://github.com/ecomfe/echarts-stat?tab=readme-ov-file#histogram

Thanks! The example looks almost perfect. I'm just wondering if the histogram can be made smaller—essentially more "marginal" in comparison to the scatter plot.

Thank you for the quick response. I’ll give it a try.


Return value of worker_init_fn is ignored by MPRS

🐛 Describe the bug
def abc(x):
    return -1

def worker_init(dp, worker_info):
    return dp.map(abc)

pipe = dp.iter.IterableWrapper(range(10))

rs = MultiProcessingReadingService(num_workers=1, worker_init_fn=worker_init)
dl = DataLoader2(pipe, reading_service=rs)

for x in dl:
    print(x)

Output:
0
1
2
3
4
5
6
7
8
9

Expected:
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1

Notice that worker_init_fn MUST return a datapipe, and process_init_fn also accounts for that, but MPRS simply ignores it. The signature of the function heavily implies that worker_init_fn should be able to modify the datapipe in a per-worker manner; and arguably this would be a useful feature.
Versions
main & torch nightly

Seems like a severe bug. Let me take a look

Find the culprit, sending a patch shortly.


Control component log verbosity

This PR adds flags in both the CRs to let the cluster-admin control the verbosity of the RTE and of the scheduler plugin containers.
The operator will translate the flag into the proper command-line setting.
The API won't allow maximum granularity for the log level rather it provides much more readable, sufficient, and self-explanatory options.

/cc @fromanirh

so far, flawless. Please make sure this code is exercised by at least one e2e test (existing or new), and please make sure to address the CI failure.

/hold
depend on https://github.com/openshift-kni/numaresources-operator/pull/91

/hold cancel

needs rebase

/lgtm
let's move forward and do the code movement in a later PR


feat(v2): don't output server.bundle.js to disk

Motivation
https://webpack.js.org/api/node/#custom-file-systems
Don't output server.bundle.js to disk. Use memory temporarily instead when running.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan

No more server.bundle.js in my build folder

This is OK to merge


PMM-7 fixed PMM-T1003 test for docker way flow

https://pmm.cd.percona.com/blue/organizations/jenkins/pmm2-upgrade-tests/detail/pmm2-upgrade-tests/16488/pipeline/