Update write-once.md

This pull request is based on wrong branch. Pls re-submit base on 'dev' branch. Thank you.

@Tancy done


Undefined body when sending beacon_blocks_by_root

Describe the bug
Undefined body when sending beacon_blocks_by_root
May-12 18:18:27.604[network]         ^[[34mdebug^[[39m: Req  sending request method=beacon_blocks_by_root, encoding=ssz_snappy, client=Lighthouse, peer=16...B4kUTv, requestId=911947, body=undefined

Expected behavior
Should print the root hex instead

@twoeths is this still an issue?


Implement versioning system

This is a tricky one that I would love help brainstorming ideas for.
Requirements
Ultimately we need to:

Allow users to specify a version in the schema URL (e.g. https://yazi-rs.github.io/schemas/vX.X.X/theme.json).
Allow users to simply go off of the latest release (e.g. https://yazi-rs.github.io/schemas/latest/theme.json).
Allow users to use schemas that match the latest commit (not sure what the URL would look like, maybe just what it is now - https://yazi-rs.github.io/schemas/theme.json - but that will cause issues when we initially implement this as right now that schema reflects the latest release. It could be https://yazi-rs.github.io/schemas/main/theme.json?).

Ideas

A folder for each version (/schemas/latest/, schemas/v0.2.3/, schemas/main/)

PROS: As simple as it gets, near zero to no changes needed to the schema deploy workflow. Schemas from past versions can easily be edited too.
CONS: Gets overwhelming quickly, many different schema files containing mostly the same thing in different directories is kinda redundant and too large.

...

A folder for each version (/schemas/latest/, schemas/v0.2.3/, schemas/main/)

If we want to do version control, it seems we can only do it this way. I don't have a better idea...

Continuation of https://github.com/yazi-rs/schemas/issues/15#issuecomment-1974247970
I have some questions:

If we adopt this version control, what is the scheme URL contained in https://github.com/sxyazi/yazi/blob/main/yazi-config/preset/yazi.toml?
And what is the URL contained in https://github.com/sxyazi/yazi/blob/v0.2.3/yazi-config/preset/yazi.toml?
Why do you think version control would have less "debt" than my proposal (if I understand your meaning correctly)?

If we adopt this version control, what is the scheme URL contained in https://github.com/sxyazi/yazi/blob/main/yazi-config/preset/yazi.toml?

And what is the URL contained in https://github.com/sxyazi/yazi/blob/v0.2.3/yazi-config/preset/yazi.toml?

Both of these would be https://yazi-rs.github.io/schemas/latest/yazi.json. We can put a note in the docs or add a line to the comment that explains how to pin a version or use the schema of the most recent commit to main.

Why do you think version control would have less "debt" than my proposal (if I understand your meaning correctly)?

It just seems like a poor patchwork solution to a wider problem. It would work, but not in all cases, and ultimately I think we do want some sort of versioning system to handle the things I've mentioned previously: pinning a version, latest release vs most recent commit.

Both of these would be https://yazi-rs.github.io/schemas/latest/yazi.json.

I'm a bit confused, are you saying to use the latest release's scheme URL in the latest main (HEAD)? Wouldn't that still cause issues like https://github.com/yazi-rs/schemas/issues/15#issuecomment-1970620310?

It just seems like a poor patchwork solution to a wider problem. It would work, but not in all cases, and ultimately I think we do want some sort of versioning system to handle the things I've mentioned previously: pinning a version, latest release vs most recent commit.

I'm not sure when it wouldn't work though, don't we still need to do this "patchwork" if we want to make "most recent commit" work? It seems like we're back to my proposal, or are there better ways to catch up with the latest main branch commit?

I'm a bit confused, are you saying to use the latest release's scheme URL in the latest main (HEAD)? Wouldn't that still cause issues like https://github.com/yazi-rs/schemas/issues/15#issuecomment-1970620310?

"latest" in that URL means latest release. "main" means most recent commit to main.

I'm not sure when it wouldn't work though, don't we still need to do this "patchwork" if we want to make "most recent commit" work? It seems like we're back to my proposal, or are there better ways to catch up with the latest main branch commit?

What do you mean? The schemas can exactly match the latest release and/or most recent main commit with no issues with this versioning system. Your proposal was to add some things and remove them later and added additional work to get the timing. This versioning eliminates that.

"latest" in that URL means latest release. "main" means most recent commit to main.

I know, want I say is using latest(rather than main) in this main file https://github.com/sxyazi/yazi/blob/main/yazi-config/preset/yazi.toml?

What do you mean? The schemas can exactly match the latest release and/or most recent main commit with no issues with this versioning system. Your proposal was to add some things and remove them later and added additional work to get the timing. This versioning eliminates that.

My proposal only considers the latest main branch (this target) and the latest release (the previous target). Things added first will not/should not be removed; what needs to be removed are fields that have been removed. Let's say:
Yazi 0.1 (latest release, the previous target)
has two fields, field1 and field2:
# yazi.toml
field1
field2

The schema looks like:
# our-scheme.json
field1
field2

Yazi 0.2 (HEAD, this target):
This upcoming target removes the existing field2 and adds a new field3:
# yazi.toml
field1
field3

We will add the new field3 to the schema file and add a comment for field2:
# our-scheme.json
field1
field2  # TODO: remove this field once Yazi 0.2 is released
field3 <-- added

This way, neither Yazi 0.1 nor Yazi 0.2 will throw an error. When we actually release Yazi 0.2, we remove field2, and field3 just stays there.
In short, before this target is released, we only add; after it is released, we only remove.

If someone on Yazi v0.1 uses field3 they will NOT get an error even though that property isn't supported yet. That is considered a bug in the schema in my view.

Yep this is a potential issue with it, but it's much easier than version control - with version control, if we want to catch up with the latest changes in the main branch, we also need to do the same steps (or is there a better way?)
It also doesn't require switching URLs, if the latest main yazi.toml (this target) includes the main scheme URL (or is it latest?), when this target is released and becomes the previous target, do we need to modify it to a fixed URL so that there are no issues when users obtain the scheme of a previous version via a tag, such as https://github.com/sxyazi/yazi/blob/v0.2.3/yazi-config/preset/yazi.toml?
That is also my question in https://github.com/yazi-rs/schemas/issues/17#issuecomment-1974256444, I don't think it makes sense for both this target and the previous target to use the same latest scheme.
Having too many schemes is not conducive to our management and can confuse users. Therefore, this is a trade-off sacrificing consistency for lower costs, as we just to ensure eventual consistency.

Yep this is a potential issue with it, but it's much easier than version control - with version control, if we want to catch up with the latest changes in the main branch, we also need to do the same steps (or is there a better way?)

What do you mean the "same steps"?

It also doesn't require switching URLs, if the latest main yazi.toml (this target) includes the main scheme URL (or is it latest?), when this target is released and becomes the previous target, do we need to modify it to a fixed URL so that there are no issues when users obtain the scheme of a previous version via a tag, such as<EMAIL_ADDRESS>
latest as in latest release, main as in main branch. The preset configs in the yazi-config/preset directory will have latest as the version, which emulates the current behavior. This is a "sane" default, but it allows for people - as I've previously mentioned - to pin versions if needed or bump up to nightly/main branch schemas.

I don't think it makes sense for both this target and the previous target to use the same latest scheme.

This is what we currently have though lol.


Order class constants alphabetically

As per @limlam's suggestion, class constants should be ordered alphabetically.

May be worth checking if there is a fixer rule we can add to help with this.


you can open multiple instances of lockbook and workspace using "show tab bar"

"show tab bar" in the menu bar. This happens on macOS, but I suspect it may also happen on iOS and iPadOS.
This feature should just be disabled.

Fixed in https://github.com/lockbook/lockbook/pull/2731


Add link to side-nav in /index.html

I signed it!

Thanks, I'd already caught this in 0caab471320d66b550515c0ec0ddaa920d91c522, I just forgot to merge back from gh-pages. Silly Lewis.


CVE fix for release-2.8

regarding: https://issues.redhat.com/browse/ACM-10133

/hold

/retest-required

/lgtm

/unhold


Extract accordion data to objects and dry up the tree and accordion logic

This PR extracts accordion data to objects and removes duplicated logic.  I also added test coverage for those actions.
I'm not sure if ApplicationController::Feature is the correct name for the class, but this is the technique we should be using.

Wow. This is great stuff. Thanks for tackling it. Even if it's only to demonstrate a way out, it's great to have code to look at.  :heart:

I think we can use this data to eliminate the copy/pasted set_active_elements and set_elements_and_redirect_unauthorized_user too.

Alright.  set_active_elements has one implementation now.  I suspect we can do the same thing with set_elements_and_redirect_unauthorized_user, but I need to study that more.

Ya, I am very sure we can use this same data to dry up set_elements_and_redirect_unauthorized_user, but that should happen in a different PR.  I'd like to get this merged, so I'm looking for feedback! :)

Looks like the build errored, not failed.  I'm closing and reopening to kick off a build.

@tenderlove I like it.  What do you think?  @dclarizio @h-kataria @Fryguy

Also I'm looking for suggestions on the name ApplicationController::Feature.  It's not a controller, so I'm not sure putting it under ApplicationController is a good idea.  Also, I'm not entirely clear on what to call this collection of data.  Is Feature right?  This data obviously has something in common.  What is it?

It's like a ProductFeatureUIElements thing.  Based on a feature, this the accordion, tree, instance filter, image filter to use.  Naming is hard.

I like UIElement.  Maybe UIElements::ProductFeature?  I assume we have more UI elements we'll want to model.

@tenderlove
These are accordions with trees in them, so perhaps UIElements::AccordionTrees would be good? . . . yes, they are based on features that are checked by role_allows calls, but they are not specifically features.
This looks great, would love to start identifying more like this.  Thx, Dan

really cool :+1:

I like this a lot.  I'm fine with any name that is close...   Vmdb::UIElements::AccordionTree or something like that.
:+1:

@tenderlove : This looks really great, but I am a bit concerned how this goes together with the TreeBuilder stuff.
I mean, I was trying to exctract the tree and tree node building into a separate classes and it was done on many places almost except for these files and this area of vm/cloud/ifra.
So we have now 2 ways to move on and each is applied at a part of the controllers. I was thinking of doing the trees first and when having all the trees converting then wrapping them in something that would represent the accordions.
Also I would like to remove the redundancy I see in:
+        :role        => "images_accord",
+        :name        => :images,
+        :accord_name => "images",
+        :tree_name   => :images_tree,
+        :title       => "Images by Provider",
+        :container   => "images_tree_div"),

the naming is almost regular, I know that I saw some irregularity I think it was in the Filter trees I mean I would like to keep only the name and skip the accord_name, tree_name.
Also all the trees that go throu the TreeBuilder already use a single partial for rendering the tree while the trees in vm/infra/cloud go through a set of slightly different partials. Unifying this (applying the TreeBuilder to the vm/infa/cloud) would allow to go through the single partial, remove the extra partials and unify the naming of name/accord_name/tree_name/container...

This looks really great, but I am a bit concerned how this goes together with the TreeBuilder stuff.

I guess we could integrate with the tree builder class.  From a quick glance, it seems the tree builder class knows what @sb is, and that worries me.  I'd like to insulate that from the rest of the system.  Maybe we can extract it?
Also it's not obvious to me

I fully agree on @sb. I just was not able to get rid of it in one go so I started by passing it in.

@tenderlove : maybe you could help me remove the @sb from the TreeBuilder. I need it there for 3 things:

Adding the trees to the @sb in add_to_sandbox. Maybe that could be moved outside of the TreeBuilder back to the controllers?
When building tree nodes I need to know the my_server_id and my_zone which is used to highlight the current zone and server in the tree.
Working with methods from the Sandbox mixin -- management of trees in the view state

@tenderlove : on the redundancy. If I am seeing it right, the images_filter are the only two accordion/tree pair that do not respect the naming scheme between name, accord_name, tree_name so by renaming them to match the rest all over the other controllers we could remove 3 keys from your feature hash I believe.

Adding the trees to the @sb in add_to_sandbox. Maybe that could be moved outside of the TreeBuilder back to the controllers?

Ya I think we can do that.  My only concern is that we have many subclasses of the tree builder which means it'll be harder to find them all and push that functionality back to the controller.  I'll try it out and send a WIP pr.

When building tree nodes I need to know the my_server_id and my_zone which is used to highlight the current zone and server in the tree.

I think we can just pass those in.  I'll look though.

Working with methods from the Sandbox mixin -- management of trees in the view state

I'll look in to this as well.

on the redundancy. If I am seeing it right, the images_filter are the only two accordion/tree pair that do not respect the naming scheme between name, accord_name, tree_name so by renaming them to match the rest all over the other controllers we could remove 3 keys from your feature hash I believe.

Ya, that's what I saw too.  I'd like to rename them, but I don't know what all those names do, so I chose to keep it fully backwards compatible.  If you know how to fix it, do you want to fork this PR and send a new one with the fixes?

I hope that the @sb usage would be mainly in the base class. I wanted to extract the tree-building into the subclasses -- have the code specific for building the particular tree in the subclass. Then I wanted to have other presentation details in the subclass -- the locals_for_render are the beginning of that idea.
Then I was trying to extract code for building tree nodes into separate classes. Now I have an ugly class with a big case statement -- TreeNodeBuilder, but I hope it's only a start. It's not straightforward to put the nodes buiding responsibility under the TreeBuilder because one tree can contain nodes of several types and vice versa, same node types can live under different trees.
After having the tree building extracted into it's own classes and having just a couple of partials for the rendering (now we have a bunch of partials that render particular trees and therefor the details of various trees are split between views and controller method's case statement branches) I was thinking about generalizing the accordions by creating an entity what would represent them. After having the accordions I would like to represent an explorer as an entity what would wrap several accordions and other behavior. So what you did -- a set of Features is sort of where I would like to get, but I was thinking about going from the partials up, removing partial views, generalizing them and getting up to the controllers.
You did it exactly the opposite from the controllers and did not touch the views.
Please, don't get me wrong I love the changes you did. I am just a bit concerned about having one part done partly in one way and other part partly done in another way so I would love to get some common understanding and agreement.
I am trying to convert the trees in VM/Infra/Cloud and will be happy to cooperate with you on identifying patterns that we can apply over all the controllers.
On the @sb -- I wanted to have some clearly defined interface for the @sb that I see as a view state object. I started by extracting some methods into the Sandbox mixin.

Did not find any issues when testing in the UI.

Yay! :tada:  :heart:


Version bump

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


Adjust subject mapping

Here  is the wanted mapping. For that  it was necessary to change the implementation such that now one Serlo-subject can map to several AMB-subjects.
Thanks to @eliflores, @AndreasHuber and @hugotiburtino  for helping.

Could you please deploy a new version from this branch?

Have you considered test cases for this?
While wanting to suggest a small refactor, I noticed that a test case assuring it's still behaving the same way would be cool.


How to remote mount on MAC OSX

Just thought I'd add this awesome, probably unknown, function in Rclone, that I found by trying the MOUNT button in RcloneBrowser!...
-Install Rclone and RcloneBrowser, all working as per normal, before doing this!...
-Create EMPTY folder on MAC hdd to MOUNT google drive in eg /FJ-FUSE-MOUNT
-Go to https://osxfuse.github.io/ and install FUSE
-It will ask, give permission to Benjamin Fleischer program, allow
-RcloneBrowser> Remotes> MOUNT(Button> point to /FJ-FUSE-MOUNT)
-BOOM… NOW “fcj/” (remote) folder appears, use it JUST like normal OSX folder!!

Showed solution in original post


Fix TESSELLATED_ENDER_PEARL craft

Fix ENCHANTED_LAPIS_LAZULI_BLOCK craft

Also, is it when this change is accepted, then all my fixes to recipes in the future will be auto accepted?

Updated the info link.

Why does my pull request have "conflicts"? i just edit some item name to be correct

Added a recipe to the flower of truth

Fixed a lot of recipes


[cppcheck] Variable 'Element_Level_Final' is assigned a value that is never used.

https://github.com/MediaArea/MediaInfoLib/blob/master/Source/MediaInfo/File__Analyze.cpp#L2835

to be removed


feat(linter): add fixer for @typescript-eslint/consistent-type-imports

This rule's fixer is complicated, I do line by line copy as possible.
https://github.com/typescript-eslint/typescript-eslint/blob/7b13dae347075d467ea95d0f986b38c3048906a2/packages/eslint-plugin/src/rules/consistent-type-imports.ts

#3984  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @mysteryven and the rest of your teammates on  Graphite

This is a big ask, but can you test this in https://github.com/oxc-project/oxlint-ecosystem-ci manually?
The repos are cloned locally, you can check git diff after the fix.
More over, I think we should add idempotence test to the fixer: run fix, then run fix agin on the fixed code, the result should be the same.

Merge first, integrate with ecosystem ci later.


Support for Applying Tags to Web Applications

This may very well already be supported and I'm just not seeing it, but I'm not getting how to apply tags in the dynatrace_web_application resource or any other related resource.
I see user tags, but I believe that's related to RUM. I'm referring to the tags when you click on the "tags and dection rules" arrow of the application's main page in the UI. Am I just not looking in the right way or is this currently not supported? If not, could it be? Thanks!

Hi @ekleiner14,
Thanks for reaching out, tag configuration is managed via separate resources. The resource dynatrace_autotag_v2 is for automatically applied tags and dynatrace_custom_tags is for manual tagging.
Both options will work for web applications and beyond, I've included a couple of basic examples below. I hope that helps!
resource "dynatrace_autotag_v2" "AutoExample" {
  name = "AutoExample"
  rules {
    rule {
      type                = "ME"
      enabled             = true
      value_normalization = "Leave text as-is"
      attribute_rule {
        entity_type = "APPLICATION"
        conditions {
          condition {
            case_sensitive = true
            key            = "WEB_APPLICATION_NAME"
            operator       = "BEGINS_WITH"
            string_value   = "Example"
          }
        }
      }
    }
  }
}

resource "dynatrace_custom_tags" "ManualExample" {
  entity_selector = "entityId(APPLICATION-1234567890000000)"
  tags {
    filter {
      context = "CONTEXTLESS"
      key     = "ManualExample"
    }
  }
}


Documentation for sandboxing mechanism

I noticed the documentation for how the sandbox works is just a stub currently. I would really like to know more about it, so this issue is just to track progress.

I read https://bytecodealliance.org/articles/announcing-the-bytecode-alliance and am enthousiastic
I played around with rust / wasmpack before and tried the hello world and capabilities system in wasmtime.
I understand how proper wasm modules only get access to certain resources and capabilities their parent gives them
However, compiled(jitted) code all runs in 1 (operating system) process so it can potentially do system calls and access all memory in the process

One thing I would really like to get clarified is how the sandbox (and possibly the just-in-time compilation of wasm to machine code) will protect against the following scenario:

I create a bit of c code that has a buffer overflow in a function
I compile this c code to wasm
I say my wasm module doesn't need any capabilities and only expose a string -> string function
I create an additional module that will call the vulnerable module with a payload that overflows the buffer with some machine code for the target architecture
this machine code isn't generated by the jit, didn't come from a valid wasm module
so it can do things like memory access and syscalls and isn't bound to what the wasm module received as inputs
I somehow find a way to have the instruction pointer jump to this malicious code (as I would be able to do in c)

My guess is that either the overflowing wouldn't work (how is this protected given that c is compilable into wasm), or there is no way to get the overflowed malicious code to execute (how would wasmtime protect against this?), but I would like some nice documentation explaining this.

Hello! I recently started adding some content to the security-sandboxing document, and it answers this question, at least at a high level.
All "pointers" in C are compiled into wasm as indices into linear memory, which you can think of as just an array of bytes, with bounds checking. So while your vulnerable C code may store beyond the ends of the nominal array, it can't access any memory outside the wasm instance's memory.
Also, all control transfers in wasm are checked, at compile time or runtime, to ensure they go to known branch/jump destinations. Among other things, this means that even if you load a machine-code payload, you can't make the program jump to it.
Does this clarify things? If not, please let us know as we're interested in expanding the documentation to answer questions people have!

better late than never :)
Yes, that document clarifies things a lot. Many thanks!


Implement cosmwasm_vm Move Bind

Summary
Summary about this PR

Closes #issue
https://github.com/rooch-network/rooch/issues/2690
Enhance native_from_json to support option type
Add base64 native implementation
RuntimeObject adds get_field and scan_fields methods

TODO

The Backend implementation of cosmwasm-vm is replaced by mock_backend with move_backend

@jolestar help review.

cc @steelgeek091

Merge this PR frist, and discuss the refactoring on the dev meeting

OK


Add ability to return translator (docchi)

I want to scrape only for videos which are not translated by ai. Is it possible?

Yes, feature will be added in future update ;)

Released<EMAIL_ADDRESS>

Wow, that was fast. Thanks a lot! <3


Base pointer is zero in the process_ret function and causing PROTECTION_VIOLATION

Error
In test process!
In test process!
In test process!
In test process!
In test process!
In test process!
In test process!
In test process!
In test process!
In test process!
In test process!
In test process!
In test process!

Error code: PROTECTION_VIOLATION
ExceptionStack {
    instruction_pointer: 0x2160e1,
    code_segment: 0x8,
    cpu_flags: 0x206,
    stack_pointer: 0x400042d8,
    stack_segment: 0x10
}
InterruptDescription {
    vector: 14,
    mnemonic: "#PF",
    description: "Page Fault",
    irqtype: "Fault",
    source: "Any memory reference."
}

Page fault while accessing 0xffffffffffffffe8

Root Cause
When a process is finished and jumps to the process_ret function, the rbp value is 0x0.
The process_ret function has the following generated assembly:
00000000002160e0 <_ZN5rxinu10scheduling7process11process_ret17hc68f08b81b5fa6b7E>:
  2160e0:	58                   	pop    %rax
  2160e1:	48 89 45 e8          	mov    %rax,-0x18(%rbp)
  2160e5:	48 8b 7d e8          	mov    -0x18(%rbp),%rdi
  2160e9:	e8 f2 f2 ff ff       	callq  2153e0 <_ZN35_$LT$alloc..boxed..Box$LT$T$GT$$GT$8from_raw17hfba216aa9a4cbfcdE>
  2160ee:	48 89 45 f0          	mov    %rax,-0x10(%rbp)
  2160f2:	48 8b 45 f0          	mov    -0x10(%rbp),%rax
  2160f6:	48 8b 38             	mov    (%rax),%rdi
  2160f9:	48 8b 40 08          	mov    0x8(%rax),%rax
  2160fd:	ff 50 20             	callq  *0x20(%rax)
  216100:	48 89 45 f8          	mov    %rax,-0x8(%rbp)
  216104:	48 8b 45 f0          	mov    -0x10(%rbp),%rax
  216108:	48 8b 38             	mov    (%rax),%rdi
  21610b:	48 8b 40 08          	mov    0x8(%rax),%rax
  21610f:	48 8b 75 f8          	mov    -0x8(%rbp),%rsi
  216113:	ff 50 28             	callq  *0x28(%rax)
  216116:	48 8d 7d f0          	lea    -0x10(%rbp),%rdi
  21611a:	e8 d1 60 ff ff       	callq  20c1f0 <_ZN4core3ptr13drop_in_place17h3f6ea748fd98a16cE>
  21611f:	c3                   	retq

The page fault happens at instruction 0x2160e0 because we attempt to access memory located at -0x18(%rbp), which translates to value stored at (0x0 - 0x18).
Using gdb, we can see that this value is:
(gdb) p/x 0x0 - 0x18
$2 = 0xffffffffffffffe8

Note:  This is a Day 1 scheduling error that is being revealed now that our bootloader properly protects this memory location.

Fixed in #60


Pushing applications with cflinuxfs4

The tile generator is currently hard-coded to push applications specifying the cflinuxfs3 stack if it is available.
https://github.com/cf-platform-eng/tile-generator/blob/8cbcfb26a0dd7df3469b0bad361f5a562babd0a7/tile_generator/templates/jobs/deploy-all.sh.erb#L220-L227
It would be nice to be able to use cflinuxfs4 when it is available.
Prefer cflinuxfs4
One option would be to do something similar to what currently exists and use cflinuxfs4 if it is available, falling back to
cflinuxfs3. For example:
function get_stack() {
	latest_stack="$($CF stacks | grep 'cflinuxfs' | sort -Vr | head -n1 | awk '{print $1}')"
	if [ -z "$latest_stack" ]; then
		echo >&2 "Using default stack"
	else
		echo >&2 "Using $latest_stack stack"
		echo "-s $latest_stack"
	fi
}

This has some potential to break tiles that don't work on cflinuxfs4, though that could be a good thing if it encourages adoption of cflinuxfs4.
It might also not work if operators were on a version of TAS 3.0 that has cflinuxfs4 but does not have a buildpack with support for cflinuxfs4  that is used when pushing the app.
https://docs.vmware.com/en/VMware-Tanzu-Application-Service/3.0/tas-for-vms/runtime-rn.html#jammy-jellyfish-stack-support-beta-17
Default stack
Another option is to use the configured default stack. This means that the operator would control the stack used, though teams that are shipping tiles may prefer to have their applications use the latest stack that is available.
With the release of TAS 4.0 operators can choose to set cflinuxfs4 as the default stack:
https://docs.vmware.com/en/VMware-Tanzu-Application-Service/4.0/tas-for-vms/runtime-rn.html
Specified by tile developers
Another option would be to allow tile developers to specify the stack that should be used at build time.

+1 on this need


Free the compression methods in s_server and s_client

This causes a minor (64 bytes on my machine) mem leak in s_server/s_client.
1.0.2 only.

Ping.  want me to merge for you?

Merged. Thanks!


ISPN-13064 WildFly OpenSSL 2.1.4

https://issues.redhat.com/browse/ISPN-13064

there are 52(unrelated?) failures. I've triggered a new run.

PR for 12.1 is missing :)


Allow custom mongo connection settings

Some connection settings cannot (as far as I know) be set as part of the connection string. This include ssl-specific settings, such as sslCA, sslCert, sslKey, sslPass. Full list available at: http://mongodb.github.io/node-mongodb-native/2.2/reference/connecting/connection-settings/
It would be great if it was possible to specify this connection settings object to be used in a migration. My colleague has made a fork of your project and made changes to allow this: https://github.com/razvanc92/mongration/tree/connection-options
If you see this as relevant in general, we will make a pull request back to your project.

@abondoa I know it's a little bit late, but it's interesting. I think a PR for that would be welcome.
However, I'm planning on review mongration code a little bit this week, maybe update it to use newer client and etc, and maybe I can rewrite to use a config object instead of a config connection string. So, maybe this review/refactor/rewrite would bring those configuration to the table.
But, I think you can open a PR to that while I'm not doing this.


Fixed dependency version conflicts/convergence

Due to issues that we have experienced with dependency conflicts we apply the DependencyConvergence rule of the maven-enforcer-plugin to all of our builds.
I have added some transitive dependency exclusions and explicit dependency declarations that are necessary to use izpack in our builds.

Closing for inactivity.
Please reopen or send a new pull request if this is still relevant for you.


Can't install pod

I've installed the cocoa pods prerelease.
Successfully installed cocoapods-0.36.3
When I run pod install for the "Player" pod, it gives me this error
[!] Invalid Podfile file: undefined local variable or method `‘Player’' for #. Updating CocoaPods might fix the issue.
Also, are there any tutorials on how to integrate it with my app? I'm a complete noob to swift.

hey @krumjahn i'll look into this cocoapod issue you're seeing. until then, you can just copy the Player.swift file into your project.

hey @krumjahn submitted a new version to cocoa pods. please make sure you've got use_frameworks! in your podfile
source ‘https://github.com/CocoaPods/Specs.git'
platform :iOS, ‘8.0’
use_frameworks!

pod ‘Player’


generator-jhipster-entity-audit resets my custom existng code and configuration into the initial state generated by jhipster

I have a new Jhipster application build with generator version 8.7.1 on windows 10

.yo-rc.json
{
  "generator-jhipster": {
    "applicationType": "monolith",
    "authenticationType": "oauth2",
    "baseName": "SimpleApplication",
    "buildTool": "maven",
    "cacheProvider": "ehcache",
    "clientFramework": "react",
    "clientTestFrameworks": [],
    "clientTheme": "darkly",
    "clientThemeVariant": "dark",
    "creationTimestamp":<PHONE_NUMBER>341,
    "databaseType": "sql",
    "devDatabaseType": "postgresql",
    "devServerPort": 9060,
    "enableHibernateCache": true,
    "enableSwaggerCodegen": false,
    "enableTranslation": true,
    "entities": ["SimpleEntity"],
    "feignClient": null,
    "jhipsterVersion": "8.7.1",
    "languages": ["en", "ru"],
    "lastLiquibaseTimestamp":<PHONE_NUMBER>000,
    "messageBroker": false,
    "microfrontend": null,
    "microfrontends": [],
    "nativeLanguage": "en",
    "packageName": "com.stukans.buddy",
    "prodDatabaseType": "postgresql",
    "reactive": false,
    "searchEngine": false,
    "serverPort": null,
    "serverSideOptions": [],
    "serviceDiscoveryType": false,
    "skipUserManagement": false,
    "syncUserWithIdp": false,
    "testFrameworks": [],
    "websocket": false,
    "withAdminUi": true
  }
}

entities.jdl
entity SimpleEntity {
  id UUID
}

The problem is when JDL entities are created and I want to introduce entity auditing I'm executing jhipster-entity-audit command all existing files (created by hipster) are being reverted to their initial state (for example some Java class, pom.xml, logback configuration, application.yaml files etc.), so I have to go through 60+ files manually and check what exactly was reverted and change it back to my code. This takes time and is not very convenient.
In the executor log I see this message "So we assume this is application regeneration.":

entities.jdl
Run `npm audit` for details.
     info Found .yo-rc.json in Git from E:/Projects/JHipster/simple-application. So we assume this is application regeneration. Therefore automatic Git commit is not done. You can do Git commit manually.
✔ Spring Boot application generated successfully.
  Run your Spring Boot application:
  ./mvnw (mvnw if using Windows Command Prompt)
✔ React application generated successfully.
  Start your Webpack development server with:
  npm start

Congratulations, JHipster execution is complete!
If you find JHipster useful consider sponsoring the project https://www.jhipster.tech/sponsors/

Thanks for using JHipster!

Is this the default behavior, or am I doing something wrong?
Thanks in advance!

This is the default behavior every jhipster generation will always generate the full project.
To help migrations you should try avoid changing generated files by adding additional files with customizations:
https://www.jhipster.tech/tips/035_tip_combine_generation_and_custom_code.html.
Use jhipster upgrade or jhipster-migrate to apply changes.
Something like:
jhipster-migrate --target-cli-options "--blueprints entity-audit"


Research / Investigate Using the Azure Monitor Baseline Alert (AMBA)

We should look into using the Azure Monitor Baseline Alert (AMBA), in particular the Platform Monitoring Packs for:

Azure Firewall
Private DNS Zones
vWAN

Further we should explore Azure resource specific monitoring guidance for:

Express Route
Virtual Network Gateways / VPN Gateways
Subscriptions

Acceptance Criteria

Generated by Zenhub AI

[ ] Scenario: Research and investigate using the Azure Monitor Baseline Alert (AMBA)
Given the need to research and investigate AMBA
When the team explores the available monitoring packs for specific resources
Then the team should provide a summary of findings, including recommendations for implementing AMBA for the mentioned resources

Based on the Cloud Adoption Framework - ALZ Monitoring Guidance, we first need to import relevant policies and initiatives from the AMBA repository.
Recommendations
I recommend that we first focus on the Patterns and Scenarios monitors, as there are Policy Initiatives for:

Identity
Management
Connectivity
Landing Zones

For example, the Connectivity Alerts monitor network components such as Azure Firewalls, ExpressRoute, VPN, and Private DNS Zones. The Management Alerts monitors Azure Automation, Recovery Service Vaults, Storage Account availability, and Log Analytics.

One of the pre-requisites to deploying this solution, is that the following Azure resource providers must be registered on all subscriptions in scope:

Microsoft.AlertsManagement
Microsoft.Insights

On spot-checking, some subscriptions did not have the Microsoft.AlertsManagement resource provider registered. This may be something we want to add to the Azure Landing Zone Vending module, to ensure all newly created subscription have these Providers registered.

Here is an Azure Resource Graph (ARG) query that lists all Subscriptions that are missing the Microsoft.AlertsManagement or Microsoft.Insights Providers:
resourcecontainers
| where type == "microsoft.resources/subscriptions"
| project subscriptionId, subscriptionName = name
| join kind=leftouter (
    resources
    | where type hasprefix "Microsoft.AlertsManagement" or type hasprefix "Microsoft.Insights"
    | summarize count() by subscriptionId
) on subscriptionId
| extend missingProviders = iff(isnull(count_), "Microsoft.AlertsManagement, Microsoft.Insights", "")
| where missingProviders != ""
| project subscriptionId, subscriptionName, missingProviders

Successfully deployed the AMBA in FORGE.

Suggested Adjustments
Based on the resulting resources, I have the following suggetions:

Do NOT include any email addresses in the ALZMonitorActionGroupEmail field (as this gets applied in every single Action Group)

We want to set up the Action Groups, Alert Processing Rules, and Alert Log Rules, but allow each respective Ministry Team configure them to use their own email addresses.
This means there will be some manual post-deployment work for the Platform team, since the parameter is an all-or-nothing. So we're going to have to update our own Action Groups post-deployment

The ALZMonitorResourceGroupName field controls the Resource Group name that is deployed into every Subscription! Currently set to bcgov-managed-lz-forge-amba-monitoring but could be shortened.

Activity Log Alert Rules

The Landing Zones all receive Activity Log Alert Rules for:

Storage Account Delete
NSG Delete
Resource Health Unhealthy
Service Health Advisory Event
Service Health Incident
Service Health Planned Maintenance
Service Health Security Incident

The Connectivity Platform receives Activity Log Alert Rules for:

Firewall Delete
NSG Delete
VPN Gateway Delete
Service Health Incident
Service Health Planned Maintenance
Service Health Security Incident

The Management Platform receives Activity Log Alert Rules for:

Storage Account Delete
NSG Delete
Log Analytics Workspace Delete
Log Analytics Workspace Key Regenerated
Service Health Incident
Service Health Planned Maintenance
Service Health Security Incident

Updated the alzArm.param.json file, by removing the value for the ALZMonitorActionGroupEmail property (ie. it should now be an empty array).
Although the What-If workflow shows that this property will be removed...

... and in the actual deploy workflow, it shows as an empty array...

... and completing the Remediation steps, the Action Groups still contain the originally applied email address.
Opened a GitHub Issue (What is the supported method to update the Action Group Email property?) to confirm the recommended approach for updating this property at scale.

According to the latest comments on the above mentioned GitHub Issue:

Action group settings like Emails Logic App, Azure Function, Arm Roles, Event Hubs, Webhooks are not part of the policy compliance since it is not really possible to control the entire list. Should you need to update, you need to:

remove the existing action group(s) and/or the alert processing rule(s)
deploy amba-alz again with the updated template file
run the remediation for the notification assets.
There's absolutely no need to remove the entire amba-alz deployment.

AMBA has now been deployed in LIVE, but with no email configured for the ALZMonitorActionGroupEmail property

Current State
Currently, the AMBA has been deployed in FORGE and LIVE. The FORGE environment had the ALZMonitorActionGroupEmail property set to<EMAIL_ADDRESS>We have been unsuccessful in getting the Deployment Cleanup process to work.

[!NOTE]
Refer to the following GitHub Issue for more details on challenges with the PowerShell script: [Question/Feedback]: What is the supported method to update the Action Group Email property?

At this point, we are closing this task, as AMBA has been implemented. The challenges with the cleanup PowerShell script will need to be re-examined when there is an update released for the AMBA, and/or when Terraform is supported.
Worst-case scenario, we would have to manually remove the Azure Policy assignments, and manually clean up the deployed resources.


Fix subchart warnings on ingress annotations

When using ingressdb as a subchart and providing a value for ingress.annotations you get warnings of the form:
Warning: Merging destination map for chart 'influxdb'. The destination item 'annotations' is a table and ignoring the source 'annotations' as it has a non-table value of: <nil>
Providing an empty table fixes this.

Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[ ] Chart Version bumped
[ ] Variables are documented in the README.md
[ ] Title of the PR starts with chart name (e.g. [stable/chart])

/check-dco


Discussion: What are comments worth?

Outline
I think we need to have a discussion about how we — as a group — value comments on Github. In the last month many people spoke about about this, in various ways. For instance:
@dckc wrote in #261:

@zsluedem has left several "drive-by" comments that I consider counter-productive. For example: #259 (comment)

@viraculous said in the same issue:

The question is , what are the parameters of identifying solid contributions? @AbnerZheng sometimes solid contributions maybe passive and unrecognized. I personally think that all newbees should be on boarded in a nursery group where they are educated on ethical values of the cooperative and also the criteriology of liquid democracy on budgeting and participation. They should be made aware of the implications of being unethical in budgeting and rewards. This is because a lot of more bad actors are yet to come.

@AbnerZheng writes in #246:

I don't think just comment or adding label has any contribution to the work. So I set negative percentage to adjust @blovedaquila vote.

To which @BelovedAquila responded:

@AbnerZheng this is a cooperative platform. And a cooperative is of the believe that no matter how little ones participation might seemly be, it still counts to certain percentage of total contribution done. Every participate counts, a participation being little doesn't void it from being a participation.

Besides this, countless other frustrated discussions can be found.
Goal
We should define a standard for how much weight (in terms of rewards) comments should carry.
Execution
Once we agree on the standard or guideline or rule of thumb, we can integrate this into the RAM (RChain Active Member) onboarding process, like many people have suggested.  — I consider implementation to be outside the scope of this issue. This is just the discussion.
cc @Mervyn853 @traviagio @lapin7 (and many more!)

My personal take on this...
Personally, I think too much weight is currently put on comments. This incentivises everyone to just "chip in their 2 cents" which is often well-intended but not necessarily helpful.
The standard should be:
**Comments are worthless unless they comprise delivered work**

Or something similar to that.
Why?
The reason for this, is that doing the primary work is much harder than it seems to as an outsider. We should lean towards over-valuing the primary contributor, rather than leaning towards under-valuing his work (by bleeding much of his credit/rewards away to bystanders).
The time it costs to do the primary work in most cases is measured in hours, whereas writing comments is a matter of minutes. Also, doing the primary work requires much more energy and
In practice this could mean:

Between 85-90% of the reward goes to whoever did the 'real work'... which is probably in most cases only 1 or 2 people per issue

The standard is that good, thoughtful comments are worth something in the tune of 1%-of-total, as opposed to 5% or 10% of total, as is now quite often the case.

Other "secondary contributions" such as reviewing things, commenting in a document or proof-reading should also carry less weight, and fit within the "10-15% of budget" space.

A thoughtful compromise needs to be found for people that (for instance) do editing work on a document, or otherwise provide a "second pair of eyes" service to the primary contributor(s).

Anyway... those are just my thoughts. Happy to hear what everyone thinks!

At first I don't know too much about reward thing so I put comments everywhere(It's not because I want the reward, but I just want to get involved with the issue I am interested~!
Back here, I think for the "Advice type" issue , we should reward the one who give the advice we take.Sometimes we take two or three persons's advice ,then we vote for the percentage of the reward.
For the "Need to Do " issue, reward the persons who actually do it and finish it .
That's two types of issues I come across.

@pmoorman am glad such issue is been brought up and i agree with you this

Personally, I think too much weight is currently put on comments. This incentives everyone to just "chip in their 2 cents" which is often well-intended but not necessarily helpful.
For me I think there should be some percentage of rewards for helpful comments ,and it should be within "10-15% of budget'' space just as you said.

why:
. comments add value to the work that is been done.
how: some one with a better understanding,or idea of the issue can make a helpful comment that will improve the performance,quality or standard of work been done
**.**comments aids in  good management of the work.
how: advice's from different collaborators are been given through comment.
**.**comment helps the project or work that is been done to meet up to standard.
**.**there are some issues that only needs helpful comments for it to be solved just like this.
these are my points why comments should have some percentages of budget space.

maybe 'comments' is too broad and should have categories that are weighted
as to the nature of them?
On Sat, Feb 3, 2018 at 8:09 AM, kaka56<EMAIL_ADDRESS>wrote:

@pmoorman https://github.com/pmoorman am glad such issue is been
brought up and i agree with you this
Personally, I think too much weight is currently put on comments. This
incentives everyone to just "chip in their 2 cents" which is often
well-intended but not necessarily helpful.
For me I think there should be some percentage of rewards for helpful
comments ,and it should be within "10-15% of budget'' space just as you
said.
why:
. comments add value to the work that is been done.
how: some one with a better understanding,or idea of the issue can make a
helpful comment that will improve the performance,quality or standard of
work been done
**.**comments aids in good management of the work.
how: advice's from different collaborators are been given through comment.
**.**comment helps the project or work that is been done to meet up to
standard.
**.**there are some issues that only needs helpful comments for it to be
solved just like this.
these are my points why comments should have some percentages of budget
space.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rchain/Members/issues/284#issuecomment-362810775, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AEEe8m0AahJ49BxjdwcpndupVIGblReVks5tRGh-gaJpZM4R4GzU
.

Comments are vital
some comments are boosters,
some are idea creators,
some are insightful,
Some are problem solving,
some are helpful and
**some! Are

_Not.**_

So measures need be created as regards to each comments to know where it falls and how it would or should be rewarded.
Though I count every participation useful

Comments are neither worthless nor vital.
Getting feedback on work is valuable, but work can get done with no comments.
The point about hours vs. minutes is perhaps the most relevant. A comment that represents hours of review or years of experience is perhaps something I would vote to reward financially, but in other cases I expect collaboration is its own reward.

Am truly impressed about this issue. Many school of thought about comment valuation, hope we arrive at a consensus. I agree with @dckc "comments are neither worthless or vital". I think that worth of comments can be estimated from a normative view that is comments valued through a proportional voting system by participants, based on perceived value of a comment in getting work done with a statutory percentage to the person who raised the issue. e.g, I raise an issue, a mandatory percentage of the to total budget lets say 20% and a redistribution of 80% to all now based on votes per participants. and then from a positive view, where comments are hierarchically categorized and defined as @pythonical , @BelovedAquila  and valued by member through a consensus with also a mandatory % for the person who raised the issue. @pmoorman, I dont think 85-90% is fair enough and further more is likely to reduce member participation and the spirit of Cooperativism. 70-75% on average is fair. this is because, there are some other measures of participation not taken into account but still may have been helpful. This is what i think.

imo, until we have to get robust tracking for impact of small stuff like comments, question answering, fixing minor errata, ..., first,
we could say, everyone has to donate x< amount, every y, distributed to z< people he found helpful, and track that

@Viraculous writes

a statutory percentage to the person who raised the issue ... 20% goes to me for raising the issue

Careful! That's likely to move us out of the frying pan of frivolous comments and into the fire of frivolous issues.
It hardly takes hours to raise an issue. Work worth rewarding financially takes hours, usually.

@dckc I get your point but I was just citing example. The percentage could be far less than 20% maybe  5% or less to be fair. They could be checks to reward on issue raised. The issue can be ranked in other of perceived relevance maybe rewarded according within a statutory range 1-5%. 95% now goes for redistribution.

I was just about to change the title of this issue to "Establish norms for financial reward for comments" but the description says:

I consider implementation to be outside the scope of this issue. This is just the discussion.

throws up hands in frustration
The goal stated one paragraph period is "We should define a standard for how much weight (in terms of rewards) comments should carry." Our standard is CONTRIBUTING.md, no? The goal is reached when that document is edited to reflect the outcome of this discussion, no? You want a separate issue for that? That doesn't seem SMART to me.

@dckc this whole "setting a scope" thing is a lot harder than I thought!  I've just updated the headline & description in line with your comment above.
With "execution" I was more thinking about concerns such as "how do we make sure all (new) members see & understand this message".
That should be, in my opinion, another thing. The goal for this discussion should be — taking Dan's suggestion here:

The goal is reached when the CONTRIBUTE.md document is edited to reflect the outcome of this discussion

Ah. I read too much into what you wrote. Thanks for clarifying.

I suggest this discussion has reached a point of diminishing returns.


Bug: Adaptor reports windows OS as posix. Fails on importing HTTPClientInterface

Expected Behaviour
I expect to be able to render with the adaptor.
Current Behaviour
When I run a job I get this error:
2024/06/12 10:09:36-07:00 ADAPTOR_OUTPUT: STDOUT: cannot import name 'HTTPClientInterface' from 'openjd.adaptor_runtime_client' (C:\Program Files\Python311\Lib\site-packages\openjd\adaptor_runtime_client\__init__.py)
2024/06/12 10:09:36-07:00 ADAPTOR_OUTPUT: STDOUT: Traceback (most recent call last):
2024/06/12 10:09:36-07:00 ADAPTOR_OUTPUT: STDOUT: (null)  File "C:\Program Files\Python311\Lib\site-packages\deadline\cinema4d_adaptor\Cinema4DClient\plugin\DeadlineCloudClient.pyp", line 26, in <module>
2024/06/12 10:09:36-07:00 ADAPTOR_OUTPUT: STDOUT:     from deadline.cinema4d_adaptor.Cinema4DClient.cinema4d_client import main
2024/06/12 10:09:36-07:00 ADAPTOR_OUTPUT: STDOUT: (null)  File "C:\Program Files\Python311\Lib\site-packages\deadline\cinema4d_adaptor\Cinema4DClient\__init__.py", line 3, in <module>
2024/06/12 10:09:36-07:00 ADAPTOR_OUTPUT: STDOUT:     from .cinema4d_client import Cinema4DClient
2024/06/12 10:09:36-07:00 ADAPTOR_OUTPUT: STDOUT: (null)  File "C:\Program Files\Python311\Lib\site-packages\deadline\cinema4d_adaptor\Cinema4DClient\cinema4d_client.py", line 14, in <module>
2024/06/12 10:09:36-07:00 ADAPTOR_OUTPUT: STDOUT:     from openjd.adaptor_runtime_client import (
2024/06/12 10:09:36-07:00 ADAPTOR_OUTPUT: STDOUT: (null)ImportError: cannot import name 'HTTPClientInterface' from 'openjd.adaptor_runtime_client' (C:\Program Files\Python311\Lib\site-packages\openjd\adaptor_runtime_client\__init__.py)
2024/06/12 10:09:36-07:00 ADAPTOR_OUTPUT: STDERR: QFileSystemWatcher: Removable drive notification will not work if there is no QCoreApplication instance.
2024/06/12 10:09:36-07:00 ADAPTOR_OUTPUT: STDOUT: (null)Failed to watch these AWS Deadline Cloud configurations: ['C:\\Users\\deadline-worker\\.aws']
2024/06/12 10:09:37-07:00 ADAPTOR_OUTPUT: STDOUT: (null)Traceback (most recent call last):
2024/06/12 10:09:37-07:00 ADAPTOR_OUTPUT: STDOUT: (null)  File "C:\Program Files\Python311\Lib\site-packages\deadline\cinema4d_adaptor\Cinema4DClient\plugin\DeadlineCloudClient.pyp", line 42, in PluginMessage
2024/06/12 10:09:37-07:00 ADAPTOR_OUTPUT: STDOUT: (null)    return parse_argv(sys.argv)
2024/06/12 10:09:37-07:00 ADAPTOR_OUTPUT: STDOUT: (null)           ^^^^^^^^^^^^^^^^^^^^
2024/06/12 10:09:37-07:00 ADAPTOR_OUTPUT: STDOUT: (null)  File "C:\Program Files\Python311\Lib\site-packages\deadline\cinema4d_adaptor\Cinema4DClient\plugin\DeadlineCloudClient.pyp", line 35, in parse_argv
2024/06/12 10:09:37-07:00 ADAPTOR_OUTPUT: STDOUT: (null)    main()
2024/06/12 10:09:37-07:00 ADAPTOR_OUTPUT: STDOUT: (null)    ^^^^
2024/06/12 10:09:37-07:00 ADAPTOR_OUTPUT: STDOUT: (null)NameError: name 'main' is not defined. Did you mean: 'min'?
2024/06/12 10:09:38-07:00 ADAPTOR_OUTPUT: STDOUT: MaxonEnd: 06/12/24 at 17:09:37
2024/06/12 10:09:38-07:00 openjd_fail: Error encountered while starting adaptor: Cinema4D encountered an error and was not able to complete initialization actions.
2024/06/12 10:09:38-07:00 ERROR: Entrypoint failed: STDOUT: MaxonEnd: 06/12/24 at 17:09:37
2024/06/12 10:09:38-07:00
2024/06/12 10:09:38-07:00 openjd_fail: Error encountered while starting adaptor: Cinema4D encountered an error and was not able to complete initialization actions.

The first error thrown is a failure to import HTTPClientInterface in this file: https://github.com/OpenJobDescription/openjd-adaptor-runtime-for-python/blob/mainline/src/openjd/adaptor_runtime_client/init.py
The problem is that import is not supposed to happen on a Windows because of the check on line 10.
Reproduction Steps
Start a Windows CMF worker.
Install C4D
Install Python 3.11.4
pip install deadline-cloud-for-cinema4d and the worker agent
Add C4D and python to path
Configure the worker agent
Set DEADLINE_CLOUD_PYTHONPATH, DEADLINE_CINEMA4D_EXE, and g_additionalModulePath
Run "C:\Program Files\Maxon Cinema 4D 2024\resource\modules\python\libs\win64\python.exe" -m ensurepip
"C:\Program Files\Maxon Cinema 4D 2024\resource\modules\python\libs\win64\python.exe" -m pip install pywin32
"C:\Program Files\Maxon Cinema 4D 2024\resource\modules\python\libs\win64\python.exe" -m pip install xxhash
Submit a job and try to render it.
Code Snippet
n/a

Fix is in here: https://github.com/aws-deadline/deadline-cloud-for-cinema-4d/pull/44 but has not been released yet

I updated my adaptor to the latest release and I'm no longer getting this error.


reshape of an immobile element type aborts instead of throwing

#include "plf_hive.h"
#include <mutex>

int main() {
    plf::hive<std::mutex> h;
    for (int i=0; i < 9; ++i) h.emplace();
    try { h.reshape({2, 2}); } catch (...) {}  // calls std::terminate
}

At the philosophical level, I question whether "throw an exception" is really the best behavior here to begin with; would it make sense to just put a requires constraint on the reshape member function so that it wouldn't exist at all for immobile types? Or, is it still useful that you can reshape a hive of mutexes in the degenerate case where the reshape has no runtime effect?
Right now this program std::terminates because https://github.com/mattreecebentley/plf_hive/blob/7b7763f/plf_hive.h#L3584 happens to say throw; — I think it's just a simple typo for throw std::whatever_exception("message");.

For similar reasons, shrink_to_fit fails with a template error message if the element type is immobile. This is fine; but consider using static_assert(std::is_move_constructible_v<element_type>) somewhere near the top level of shrink_to_fit, to prove to the programmer that this error is intentional.
int main() {
    plf::hive<std::mutex> h;
    h.shrink_to_fit();  // compiler error
}

Yes, both of these are defined with preconditions in the paper of
T shall be Cpp17MoveInsertable into hive,
therefore logically they might be defined in a requires statement.
However, looking at libstdc++'s shrink_to_fit implementation (which has
the same precondition in N4910) it also throws rather than
static_asserts or requires.
My guess is that this is because in degenerate cases shrink_to_fit will
not need to reallocate. @jwakely, is that the case?
In terms of reshape, it makes more sense to throw, as in many cases (eg.
going from more restrictive block capacities to less restrictive block
capacities) reallocation of elements will never be necessary.
I will re-write the reshape throw to be std::length_error.
On 24/04/2022 10:17 am, Quuxplusone wrote:

For similar reasons, |shrink_to_fit| fails with a template error message
if the element type is immobile. This is fine; but consider using
|static_assert(std::is_move_constructible_v<element_type>)| somewhere
near the top level of |shrink_to_fit|, to prove to the programmer that
this error is intentional.
|int main() { plf::hivestd::mutex h; h.shrink_to_fit(); // compiler
error } |
—
Reply to this email directly, view it on GitHub
https://github.com/mattreecebentley/plf_hive/issues/10#issuecomment-1107657949,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABE4FIRQVCWUUEZZFESM7GTVGRZGLANCNFSM5UFJEHPQ.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Libstdc++'s shrink_to_fit doesn't throw for non-movable types, it just gives an error somewhere deep inside the implementation.


Support for player cards

Hi, I'd really like to use this library but one of the sites I want to embed content from, Bandcamp, isn't seemingly supported. For example, when trying to unfurl one of my albums:
>>> print(pyunfurl.unfurl('https://sockpuppet.us/album/novembeat-2020')['html'])

        Novembeat 2020, by Sockpuppet

16 track album

        sockpuppet.bandcamp.com

From what I can tell (having not delved too deeply into the code) it seems that the "player" card data is being ignored, and it's falling back to using just the image. Would it be possible to add support for player cards as well?

I must have missed this issue, you are correct it currently only falls back to the image.
Do you have some examples of how best to display media?

I believe with player cards it just provides you a URL to embed via iframe, and it's up to the card provider to provide the ideal experience.

To use the example in the URL I provided above, here's the relevant OpenGraph:
            <meta name="medium"         content="video">
            <meta name="video_height"   content="120">
            <meta name="video_width"    content="400">
            <meta name="video_type"     content="application/x-shockwave-flash">
            <meta property="og:video"
                content="https://bandcamp.com/EmbeddedPlayer/v=2/album=1223510543/size=large/tracklist=false/artwork=small/">
            <meta property="og:video:secure_url"
                content="https://bandcamp.com/EmbeddedPlayer/v=2/album=1223510543/size=large/tracklist=false/artwork=small/">
            <meta property="og:video:type" content="text/html">
            <meta property="og:video:height" content="120">
            <meta property="og:video:width" content="400">

and if you just do the naive thing and do something like:
Novembeat 2020, by Sockpuppet

you get a perfectly serviceable player.
I don't know how universal that is though, given the og:video:type. Presumably if you get something other than text/html there you'd want to use a <video> tag instead, or something.


We should remove the namespace Microsoft.AspNetCore.Http.Endpoints

The only thing in this namespace is the extension methods GetEndpoint() and SetEndpoint(). Endpoint is defined in Microsoft.AspNetCore.Http. We should move these extension methods there too.

@davidfowl

Yep

Assigning to me to confirm and mark accepted.


Add new ":assert" directive to Calc

Allowing something like :assert notnull(set.class) and if the expression is false, then an error is thrown and execution stops for that script.
Need an "AssertException"

Syntax is :assert expr [ , message ] where the expression is evaluated, if the result is true, execution continues at the next statement, if false, the message (if present) or a generic message is displayed and execution stops.


How to reproduce the result in table6 and table7?

Hi, thanks for sharing your code. I'm wondering how to reproduce the result in table6 and table7. Could your offer your preprocessed json file, config file and dataset file?

Hi, I think I used almost the same configuration of 3dpw.yml.

Hi, I think I used almost the same configuration of 3dpw.yml.

Thanks for your reply. Could you offer the annotation files you preprocessed about MuPoTS and CMU-Panoptic dataset? If not, Could you share the code you use to preprocess the annotation files?

I didn't preprocess MuPoTS. For CMU-Panoptic, I followed Jieng's work


[Feature Request] Add Customizable Graph Position Options and Visibility Toggle for Enhanced Visualization

Thank you for your work on this plugin. It has been extremely helpful for Obsidian's local graph feature.However, I would like to move the graph to the top right corner of the note interface, similar to the publish layout.
Here is a small adjustment I made to your Styles.css file:

/* https://github.com/mgmeyers/obsidian-style-settings */
/* @settings
name: Graph Banner
id: graph-banner
settings:
  - id: hide-graph-banner
    title: Hide Graph Banner
    type: class-toggle
    addCommand: true
  - id: graph-banner-type-select
    title: Select graph type
    type: class-select
    allowEmpty: false
    default: banner-graph
    options:
      - banner-graph
      - hanging-graph
  - id: banner-height
    title: Banner Height
    description: The height of the banner. (e.g. 20vh, 200px)
    type: variable-text
    default: 20vh
  - id: banner-width
    title: Banner Width
    description: The width of the banner. (e.g. 20vh, 200px)
    type: variable-text
    default: 400px
*/

body {
  --banner-height: 20vh;
  --banner-width: 400px;
}

body.hide-graph-banner .graph-banner-content {
  display: none !important;
}

.banner-graph .graph-banner-content {
  width: auto;
  height: var(--banner-height);
  margin-bottom: 16px;
}

.hanging-graph .cm-sizer>div.view-content.graph-banner-content,
.hanging-graph .mod-header>div.view-content.graph-banner-content {
  display: block;
  position: fixed !important;
  right: 50px;
  top: 50px;
  z-index: 2;

  border-radius: 10px;
  border: 1px solid var(--background-modifier-border);
  width: var(--banner-width);
  height: var(--banner-height);
  margin-bottom: 16px;
}

I added two types of graph display modes:

banner-graph - retains the original display.
hanging-graph - positions the graph at the top-right corner of the note interface.

Additionally, I also added a CSS class toggle control using the Style Settings plugin to manage the visibility of the graph banner. The .hide-graph-banner class can be toggled using Obsidian commands, which could be useful with the Commander plugin.
I'd love it if you could consider adding this CSS modification to your plugin. I think it would offer an even richer visualization experience. Thanks again for all your hard work on this plugin!

Of course, if my modifications do not align with your original design intent, then let it remain unchanged. I will use it as it is.

I discovered through developer mode that in reading mode, the functions prototype.detach and Node.prototype.setChildrenInPlace would delete the mod-header element, causing the graph-banner to disappear. To solve this issue, I overrode these two functions to skip the check for the mod-header element and load them in onload(). This way, in my reading mode, the graph-banner can always be displayed. Since I am not very knowledgeable about computers, these modifications were made with the help of GPT, so I cannot guarantee that there won't be any issues, but so far, testing has not revealed any problems.
Node.prototype.detach = function() {
  if (this.classList && this.classList.contains('mod-header')) {
      // console.log('Skipping detach for mod-header:', this);
      return;
  }
  this.parentNode && this.parentNode.removeChild(this);
};

Node.prototype.setChildrenInPlace = function(t) {
  for (var e = this.firstChild, n = new Set(t), r = 0, o = t; r < o.length; r++) {
      for (var i = o[r]; e && !n.has(e); ) {
          var s = e;
          e = e.nextSibling;
          // console.log('Node classList:', s.classList);
          if (s.nodeType === 1 && s.classList.contains('mod-header')) {
              // console.log('Skipping node with mod-header:', s);
          } else {
              this.removeChild(s);
          }
      }
      i !== e ? this.insertBefore(i, e) : e = e.nextSibling;
  }
  for (; e; ) {
      s = e;
      e = e.nextSibling;
      if (s.nodeType === 1 && s.classList.contains('mod-header')) {
          // console.log('Skipping node with mod-header:', s);
      } else {
          this.removeChild(s);
      }
  }
};

Thought process is absolutely in the right direction. Would love to use the plugin with these enhancements

+1


add perfdash in CDK

Added perfdash components (excluding configmap) in CDK.
Added a section in the README for perfdash.

PTAL

@hakuna-matatah Please note that I have created an internal CR for the ConfigMap. We need to merge and apply that before we merge this PR.

@hakuna-matatah Please note that I have created an internal CR for the ConfigMap. We need to merge and apply that before we merge this PR.

Yup, thanks for moving that to internal.

@hakuna-matatah  PTAL

This PR should hold merging until the ConfigMap has been created out-of-the-band.

Rebased on top of the latest HEAD. The last commit is the change since last review.
The changes is not fully tested due to https://github.com/awslabs/kubernetes-iteration-toolkit/issues/313. I will need some help to figure out what's going on with #313.

@hakuna-matatah PTAL


chore(LinearAlgebra/Basic): change a CommSemiringinstance to a Semiring instance

Generalize mem_map_equiv and likes to Semiring (previously used CommSemiring instances).

I need this for an other project.

I found one more lemma that can be generalized and pushed a fix.
bors d+

!bench

bors merge

bors merge


Change the config type to definition

This PR renames the _config field used in templates to #config.
The redis example module was refactor to showcase how to use nested packages for templates.
Fix: #273

LGTM.


quickstart on Mac OSX not working

exception in initAndListen: IllegalOperation: Attempted to create a lock file on a read-only directory: /data/db, terminating
 Database connection has failed! Make sure your database is running.
How can I fix this issue? I'm using quickstart on Mac OSX
Thank you!!

Can you give us an update please.
Based on last version of files.

If anyone else is having issues with Quickstart on MacOS:
sudo mkdir -p /data/db/strapi
sudo chown -R $USER /data/db/strapi

This will create a folder off your /User folder (which is what was causing the issue for me). Then update docker-compose.yaml under 'db':
    volumes:
      - /data/db/strapi:/data/db

Then run docker-compose up.

HI,
We just released a full rebuild of our docker image 🎉
We are closing the issues and open PRs to start fresh.
If you feel like something is missing or want to add things feel free to open new PRs ! 💯


Add option to claim "Full Stack Developer Certification" to options

We want to create one more certification view - the "Full Stack Developer Certification."
This can be claimed with a single click from the settings interface upon having already earned the following certifications. The button for claiming this should be below the new certifications and above the legacy certifications. And should have the following text:
Once you've earned the following freeCodeCamp certifications, you'll be able to claim this The Full Stack Developer Certification:

Responsive Web Design
Algorithms and Data Structures
Front End Libraries
Data Visualization
APIs and Microservices
Information Security and Quality Assurance

[ Claim your Full Stack Developer Certification ]

I have started working on this issue. I will do the following for now, suggestions are welcome:

Add the section for the Full Stack Developer Certification at the required position.
The section will contain heading and the text about the certification.

These user stories all look good. Thanks for doing this!
Note that these are certifications - not certificates. The distinction is that certifications have an evaluation criteria (in freeCodeCamp's case, required projects.)

OK, I understand.


[Do Not Merge][terra-tabs] Migrate docs to terra-framework-docs

Summary

Migrate docs to terra-framework-docs

Closes #
Deployment Link

https://terra-framework-deployed-pr-#.herokuapp.com/
Testing

Additional Details

Thank you for contributing to Terra.
@cerner/terra

closed in https://github.com/cerner/terra-framework/pull/1550


[Node.js SDK] Session.endConversation() causes [400] Bad Request and no username

Bot Info

SDK Platform: Node.js
SDK Version: 3.15.0
Active Channels: Skype
Deployment Environment: Local via ngrok

Issue Description
An endConversation causes a '400' POST and after this the session.message.user.name is undefined.
Error: POST to 'https://smba.trafficmanager.net/apis/v3/conversations/29%3A12fMgeiJDkMJmp5SXwnHt7tJf7sl3sst22-FBErf-7mY/activities' failed: [400] Bad Request
Code Example
// in a middleware function
return {
	botbuilder: (session, next) => {

		if (session.message.text) {
			const match = /test/i.exec(session.message.text);
			if (!match) {
				return next();
			}
			return session.endConversation(message);
		}
		return next();
	}
};

Reproduction Steps

Connect to bot using Skype via ngrok.
type 'test'. Notice a breakpoint in the middeware function will have a populated session.message.user.name.
The bot will emit an error, see below.
The next time a message is recieved in the middleware session.message.user.name is undefined.

Expected Behavior
No error and the user address
Actual Results
Error: POST to 'https://smba.trafficmanager.net/apis/v3/conversations/29%3A12fMgeiJDkMJmp5SXwnHt7tJf7sl3sst22-FBErf-7mY/activities' failed: [400] Bad Request

Here is the options var for ChatConnector.prototype.postMessage right before the error:
{
	"method": "POST",
	"url": "https://smba.trafficmanager.net/apis/v3/conversations/29%3A12fMgeiJDkMJmp5SXwnHt7tJf7sl3sst22-FBErf-7mY/activities",
	"body": {
		"type": "endOfConversation",
		"code": "completedSuccessfully",
		"localTimestamp": "2018-06-08T09:46:49.900Z",
		"from": {
			"id": "28:1c62f3fd-9eed-45e4-b9dd-c6c32cd0600e",
			"name": "<Some Name>"
		},
		"recipient": {
			"id": "29:12fMgeiJDkMJmp5SXwnHt7tJf7sl3sst22-FBErf-7mY"
		}
	},
	"json": true
}

Hi @SeanSobey,
Please review the docs listed here as they should help in understanding what is happening.
In short, because the conversation is ended, per the text match in the middleware, there is nothing to be reported back when "The next time a message is received". The dialog stack has been cleared at this point and a 400 error is returned.
My suggestion is to build the .endConversation into the dialog flow as demonstrated in the docs. I'm closing this as I believe this solves your problem. Please reopen if you have additional related questions.
Steve.

Hi @stevkan, thanks for your reply.
My example was based off the Middleware.dialogVersion included in the SDK which also results in a 400 error:
bot.use(Middleware.dialogVersion({
	version: 0.0,
	resetCommand: /^reset$/i
}))

Note this only happens in Skype not via the Emulator, Slack or Messenger. This still appears to be a bug?

Hi @SeanSobey, I just saw you had responded. Let me take another look and will get back to you.

@stevkan this still appears to be an active bug, has anyone been able to confirm?

Hi @SeanSobey,
Yes, I was able to confirm your results.  I will mark this as a bug for further consideration.
Thanks,
Steve.

yeah we're experiencing the same issue

wonder if this is related to
https://github.com/Microsoft/BotBuilder/issues/3576

Thank you for opening an issue against the Bot Framework SDK v3. As part of the Bot Framework v4 release, we’ve moved all v3 work to a new repo located at https://github.com/microsoft/botbuilder-v3. We will continue to support and offer maintenance updates to v3 via this new repo.
From now on, https://github.com/microsoft/botbuilder repo will be used as hub, with pointers to all the different SDK languages, tools and samples repos.
As part of this restructuring, we are closing all tickets in this repo.
For defects or feature requests, please create a new issue in the new Bot Framework v3 repo found here:
https://github.com/microsoft/botbuilder-v3/issues
For Azure Bot Service Channel specific defects or feature requests (e.g. Facebook, Twilio, Teams, Slack, etc.), please create a new issue in the new Bot Framework Channel repo found here:
https://github.com/microsoft/botframework-services/issues
For product behavior, how-to, or general understanding questions, please use Stackoverflow.
https://stackoverflow.com/search?q=bot+framework
Thank you.
The Bot Framework Team


querystringify is unused

I added this to try to remove the vulnerability warning but it did not seem to work.
@singingwolfboy do you have the warning on your fork too? And do you know how to get rid of it?
Thanks.


Fixed relative paths of include codes in "multiprocessing guide"

https://github.com/pola-rs/polars-book/pull/197#issuecomment-1295766655
Fixed relative paths of include codes in "multiprocessing guide".
It now renders the code correctly.

🙏