Bugfix for Linear, H1 and L2 functions on point meshes [bugfix-point-fespace]

For Linear and H1 functions,  FiniteElementSpace was generating two dofs per point rather than one for LinearFECollection and (order 1) H1_FECollections  defined on a point mesh.
For L2 functions,  L2_FECollection did not handle the 0-dimensional (point) case, causing the following code to segfault:
// simple single element point mesh
int dim = 0, nv = 1, ne = 1, nb = 0, sdim = 2, order =1;
mfem::Mesh ptMesh(dim, nv, ne, nb, sdim);

ptMesh.AddVertex(mfem::Vertex(0,0)());

int idx[2] = {0};
ptMesh.AddElement(new mfem::Point(idx, 1));

// create a grid function using an L2 fec
mfem::L2_FECollection fec(0,dim);       //  <-- segfault here
mfem::FiniteElementSpace fes(&ptMesh, &fec);
mfem::GridFunction gf(&fes);

@rieben1, any objections to merging this?

No, im fine with merging

Thanks @v-dobrev.
I have a small update to add support for dumping point meshes in vtk format.
Should I add it to this PR, or create a separate one?
The changes are to add Geometry::POINT cases to the switch statements in:

mesh::PrintVTK()
GeometryRefiner::Refine()

Incidentally, your updates to FiniteElementSpace::GetElementDofs() were necessary to make this work.

@kennyweiss, I'm OK with adding you updates here, if you want to.

@tzanio  @v-dobrev  @rieben1  -- I pushed some new changes to allow outputting VTK meshes for Point meshes.

The new additions look good to me. Thanks, @kennyweiss !


Remove hazelcast dependency from dev service and update

Remove hazelcast dependency from dev service

[x] Remove maven hazelcast dependency
[x] Update to latest camunda verziu
[x] Switch dev service to zeebe-dev-monitor
[x] Switch to Camunda BpmnAssert API
[x] Update release action
[x] Add basic example

Zeebe-dev-monitor https://github.com/lorislab/zeebe-dev-monitor


Changes in top screen's section. Replace status with new status bar.

remove status below screen name

move up title section with buttons on all screens. https://zpl.io/aXRmvxX

Place status icon (circle, padlock) next to the logo in side menu.

No need to show status bar if trusted node connected (green padlock)

Statuses examples. Please follow each gradients from the design, so we can be sure the text is visible. https://zpl.io/aXRmA4E

Status error line example https://zpl.io/aM3jgDN

checked

different indicator colors are displayed for different nodes when the node loses connection

there is also too much text that doesn't fit in one line when the wallet is connected to a random node and doesn't receive an exchange rate

checked


static_views: don't use oversized_array

Instead, directly create a std::array of the proper size callable is now called twice, but it's fine because the second time is as part of a template argument.
Also, both calls are in a consteval function, so this is "free"

The compiler is still going to actually do the work 2x in most cases, which is the exact problem I was trying to solve with the existing code.
Only with a compiler extension like [[gnu::pure]] might we have any guarantee that the second call to callable() would actually be memoized.

Codecov Report

Merging #3 (05a7ffb) into main (9f6c8f0) will decrease coverage by 72.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #3       +/-   ##
==========================================
- Coverage   72.03%   0.00%   -72.04%
==========================================
  Files          13      13
  Lines         472     320      -152
  Branches      225     144       -81
==========================================
- Hits          340       0      -340
- Misses        120     320      +200
+ Partials       12       0       -12

Flag
Coverage Δ

Linux
0.00% <ø> (-39.66%)
:arrow_down:

Windows
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

test/np_tests.cpp
0.00% <0.00%> (-100.00%)
:arrow_down:

test/curry_tests.cpp
0.00% <0.00%> (-100.00%)
:arrow_down:

test/consteval_invoke.cpp
0.00% <0.00%> (-100.00%)
:arrow_down:

include/lefticus/tools/curry.hpp
0.00% <0.00%> (-100.00%)
:arrow_down:

include/lefticus/tools/lambda_coroutines.hpp
0.00% <0.00%> (-100.00%)
:arrow_down:

test/tests.cpp
0.00% <0.00%> (-95.95%)
:arrow_down:

test/simple_stack_string_tests.cpp
0.00% <0.00%> (-90.99%)
:arrow_down:

test/static_views_tests.cpp
0.00% <0.00%> (-87.88%)
:arrow_down:

test/simple_stack_vector_tests.cpp
0.00% <0.00%> (-81.14%)
:arrow_down:

include/lefticus/tools/simple_stack_string.hpp
0.00% <0.00%> (-41.56%)
:arrow_down:

... and 3 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9f6c8f0...05a7ffb. Read the comment docs.

So this is a case of compile time optimization. Did you do some measurements comparing the compile time/memory usage of  calling callable twice vs calling it once and allocating an oversized array ?

Yes, even for relatively simple cases the compiler clearly does the work twice, which takes more time, and uses more RAM.
https://build-bench.com/b/rH9dMw60LpnpUGGL76AcBti_uFM And as mentioned, see the compile-time comparison that was performed in #2
For reference I run through all of the reasoning behind this code in this video:
https://youtu.be/ABg4_EV5L3w

I saw your video, but I have to admit I did not understand why it was a problem to "do the work twice".
the difference in compilation time depends on the complexity of the callable. But of course that's you call, so feel free to close the PR.
By the way, great work, thanks !

I saw your video, but I have to admit I did not understand why it was a problem to "do the work twice". the difference in compilation time depends on the complexity of the callable. But of course that's you call, so feel free to close the PR. By the way, great work, thanks !

Thanks for the work. Yes, it's a real problem in real use cases. The constexpr JSON parser that I had worked on and related projects would benefit greatly from not doing the work twice.
And the remaining small cases make no difference.
So I'm going to stick with the solution I have currently. It saves time in the cases where it's needed, and doesn't hurt performance or usability in the cases where it is not needed.

Oh, as a side note - your solution cannot (in any way that I can think of) work in the case of std::vector<std::string>, which is the case I'm currently working on dealing with.


fixed performance route

Description
fixed nav issue.
Navigating to performance dashboard from the /app page gives you this:
https://chess.apps.silver.devops.gov.bc.ca/appperformance
Types of changes

Bug fix (non-breaking change which fixes an issue)

Checklist

[x] I have read the CONTRIBUTING doc
[ ] I have checked that unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments

PR Deployed at: https://chess-dev.apps.silver.devops.gov.bc.ca/pr-7


#829 - Config common library and add test for product, cart,... for checking

Update

Update the version configuration in the common-library module to ensure compatibility with other modules
Enhance test coverage by add some integration tests into the product
Add some unit tests in the cart module to verify the functionality of the common library

Now, to build a specific module in local with maven, instead of normal use:
mvn clean install -f module

use this command to run and build all the necessary module:
 mvn clean install -pl module -am

After searching about testcontainer.reuse, I got some information:
First, the testcontainers reuse need to create a file inside system, not inside project, I have tried create file with name like this:

testcontainers.properties
.testcontainers.properties

inside test/resources, root of product module or  root of yas with the content:
testcontainers.reuse.enable=true
I also tried to add the TESTCONTAINERS_REUSE_ENABLE=true inside the .env file
But the log always show reuse was request but environment does not support:

Then, I tried to create a file .testcontainers.properties inside local system and run test, it works and re-use the test container, and I found this blog about test container:

https://blog.dkwr.de/development/2023-08-18-testcontainers-spring-boot-3/#:~:text=The setting.withReuse(true) keeps the container alive between test,~%2F.testcontainers.properties file and add the following line%3A testcontainers.reuse.enable%3Dtrue
So, this is the first way to config test container for re-use.

The second way, I try to refactor the previous IT inside product module, add this config to all the IT class, to let spring re-use test container when run:

And the result is good here, when I run: mvn clean install -pl product -am:

Hi @khanhduzz, I have some suggestions for enhancement. Please take a look. Thanks!


Kitsu: fix  extra frame with frameEnd calcul using frames duration

Brief description
Updating OpenPype shot data frameEnd using Kitsu frames duration data add an extra frame with the frame range.
Description
Because frameEnd is include in shot frame range, to avoid extra frame, we should have :
frameEnd = frameStart + frames_duration - 1
frames_duration = frameEnd - frameStart + 1
with
frameStart >= frameEnd
frames_duration > 0

This PR can be closed as the fix was added to the now merged PR https://github.com/ynput/OpenPype/pull/4425

Closing as per previous comment


Broken emoji when set to editor with setText()

Description:
Hello, I found similar problem to my previous issue. When you put like on fiddle text to editor with setText or it will be set to field like a value and you will initialize emojioneArea, it will broke :asterisk: emoji and probably another too.
Instruction:

Init emojioneArea
Make a code, which set text setText() to editor.
Inspect contenteditable element or write any additional text to editor and watch logs.

Information:
Jquery: any
EmojioneArea: i think all versions, 3.3.1 for sure not work properly
jsfiddle: https://jsfiddle.net/bdp5gx8f/

#412


Revert "Remove PR test as Vercel is doing it now"

Reverts flashbots/flashbots-docs#430

nice, yeah let's add it back in for visibility of issues


Multi-processing for huge datastore

Thanks for sharing the great tool.
I am wondering if the tool supports multi-processing when saving keys and value to datastore (i.e. multi-gpu inference and saving key values). It may helps for huge datastore application.

Sorry, this toolkit  does not support multi-GPU currently. It is a good suggestion, maybe we will consider supporting this feature in the future.

Thanks for your clarification!


Logging into wifi network through the bar module results in error.

Describe the bug
Cannot connect to wifi from bar module.
To Reproduce
Try to connect to an unsaved wifi network. Password validation will fail. with the error as shown in the picture below.
 On my Pc it doesnt get picked up and i have to enter password on every reboot using nmcli

I would suggest using nm-applet until I rework the network module. Waiting on this to get merged: https://github.com/Aylur/astal/pull/13
I'll look into this further in the meantime but meaningful work will be done when that PR is merged.

No Problem. I will use nmapplet till then


Not Seeing the initital button on a dataobject

Hi,
Thank you for the addon, it looks perfect to what I need to implement.
I am using SilverStripe vesrion (version 3.1.6) and latest version of advancedworkflow
My site is build mostly on data objects.
I have assigned both object and model admin in the .yml file as described in the documentation:
MyObject:
    extensions:
        - WorkflowApplicable
MyObjectAdmin:
    extensions:
        - AdvancedWorkflowExtension

I have also assign the workflow in the workflow tab of the object.
I am using the template review and approve workflow.
While I see the button to start a workflow when editing a page, the buttons doesn't show up for the dataobject. Do I need to add code in the object level, or modify the template workflow to work with data objects?
Thank you!

Digging dipper into the code, on advancedworkflow/code/extensions/WrokflowApplicable.php on line 135 the function public function updateCMSActions(FieldList $actions) { is not called on dataobjects but called on pages. this is the funciton that adds the button I believe. does this help anybody to understand the problem?

Interesting! The ability to bind other objects was built with a non model admin interface for editing those objects; in ModelAdmin, the object editing form is put together by the GridFieldDetailForm::ItemEditForm which doesn't call getCMSActions. Will look at how to work around this

Thank you nyeholt!
I am surprised I am the first one to deal with this...
I am using also betterbuttons2 by uncle cheese. we can add actions through that interface as well.
Which action should we use?

The PR referenced above has the fix for the button / action triggering issue, so that should get things going. However, there is a separate issue to do with post-workflow-actions inside model admin that still needs to be looked at (see #204)

Sorry, I am confused. is the issue resolved?

Yes! The latest commits to master in 38c5480e6b5c9a6856938ca774f2caf2790a788d have fixed the issue :)

Will close this for now - please re-open if you're still having problems


Semantic query cache

Summary

Cache query to the vector database
Cache invalidation (TTL) is set for 24 hours
You can set another index for caching queries
Fixes
Depends on
Test plan

Screenshots

Checklist

[x] My code follows the code style of this project and passes make format.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] My change has adequate unit test coverage.

Yes, we can set TTL to 0, or disable entire caching mechanism

Where do we handle this?


blank screen after logging through Xorg module

Hi,
I am having issues connecting to RHEL 6 system using Xorg module.
I can get to the login screen but after logging in, I get a blank screen.
I am using xrdp ver 0.9.3 with xorgxrdp ver 0.2.0.
log files and the error message are attached.

That is not a log.  xrdp.log and xrdp-sesman.log will give us more helpful information.

modifying startwm,sh resolved the issue.

Type that modifying help, but didn't wrote what you change...So helpless


[WIP] Some fixes for skeleton patch related with merge & delete, undo/redo

Motivation and context

How has this been tested?

Checklist

[ ] I submit my changes into the develop branch
[ ] I have added a description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (read github docs)
[ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[ ] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

/check

@klakhov Could you please look at this patch carefully and try it?

Btw what do you think about making merge selection for sceletons more noticable like its done with box tracks?

@klakhov
I do not think it will work for skeletons, because they are not closed shapes.
We can only fill skeleton points to blue line like it is done for points shape.

We can only fill skeleton points to blue line like it is done for points shape.

@klakhov
I did so.


docs(proxy) fix minor styling issues

@murillopaula you were too fast, I shouldn't have grabbed coffee before adding the second comment :).


Completed profile hook

Reactively show a modal if the profile required fields are not completed.
The only way to close this modal is to complete the fields or log out with the button provided.
I have used nova:forms + users.edit method and add a prop requiredFieldsOnly to show only telescope.email.

Nice work :) Just one suggestion: instead of adding special logic in NovaForm for requiredFieldsOnly, maybe it could support a fields property that lets you specify which subset of fields you want to display? So if the edit form would normally show fields foo, bar, and baz, and you pass fields=["foo", "baz", "buzz"] it would only show foo and baz (that's how Autoform does it at least).
Also devel was a bit behind, sorry about that!

Ooow, I like this! Yep, I'll modify following this way!

Don't be afraid by this huge comment, it's my changelog as a little story: this is a description for you to better understand what I did, and also for me to take a step back 👍
c2d1a1a
Be in accordance with devel, 😄  ok that was the easy part.
2baf40a
Then, I ran into several bugs due to undefined settings (I run with Nova with settings.json). I found that it was due to a missing typeof in the Telescope.settings.get method. Even if it's not related to this PR, I thought it wasn't useful to do a new one.
5c424da
I switched from my requiredFieldsOnly prop to a fields prop which accepts an array of fields and will filter on it the way you described me, it does the job.
💥
The story could have be done by this time, but I realized that in some cases after submitting the modal or logging out, I got warnings displayed in my browser console.
d878b84
The first warning was related to nova:forms and I guess it was due to the update to React 15:
Warning: Unknown DOM property dataType. Did you mean datatype?. Quick typo change:
72ea1ab
The way I handled the modal was in fact an anti-pattern!  Can only update a mounted or mounting component. This usually means you called setState() on an unmounted component. This is a no-op. Please check the code for the undefined component.
Warning: setState(...): Cannot update during an existing state transition (such as within `render` or another component's constructor). Render methods should be a pure function of props and state; constructor side-effects are an anti-pattern, but can be moved to `componentWillMount`.
These warnings were caused by a really bad way of closing the modal (show prop true/false) on logout or submitting a new email. After struggling and trying a lot of different patterns, I finally wrapped the modal in a container passing to the modal to manage three different cases:

there is not a current user -> render null
there is a current user who has a complete profile -> render the modal but don't show it.
there is a current user who has no email / erased it from his profile -> render the modal and show it!

In addition to that, I added a go home callback on logout to move the user from the account route if he logs out with the modal.
Conclusion: I just f$#§ing leveled up in Meteor and React!!! :metal:
It's now time to spread love and drink beers, have a good weekend! 🍻

Wow that's awesome! Regarding the datatype thing, that's just a name I gave the prop, but maybe React treats data* properties differently? I don't really understand that error tbh. I'm also surprised that you needed to use React Komposer, if I have time I'll test out both ways as well. I could use some levelling up in React myself, too ;)

Oh ok I understand the problem with your first solution now. As soon as you submit the form, the user profile becomes complete and the modal component was being unmounted. So that's why the modal needs to stick around wether the profile is complete or not :)

So as far as I can tell, the important part is keeping the modal around, Komposer is not really required here I think.

OK I simplified it a bit, let me know what you think:
https://github.com/TelescopeJS/Telescope/commit/60f29bbfd189eed2fdb355c3758053de48f5258f
Basically the requirements are:

If there is no user object, do not mount the form.
If there is a user object, always mount the form.
If the profile is incomplete, show the modal.

Oh also it shouldn't be fields={ ["telescope.email"] }, but instead:
// return fields that are required by the schema but haven't been filled out yet
    var schema = Users.simpleSchema()._schema;
    var requiredFields = _.filter(_.keys(schema), function (fieldName) {
      var field = schema[fieldName];
      return !!field.required && !Telescope.getNestedProperty(Meteor.user(), fieldName);
    });

Also if I'm not mistaken, the way you did getFieldNames would only get fields passed as this.props.fields:
const schema = collection.simpleSchema()._schema;
relevantFields = _.filter(_.keys(schema), function (fieldName) {
   return _.contains(fields, fieldName);
});

Instead we want the intersection of this.props.fields and whichever fields are editable/insertable:
relevantFields = _.intersection(relevantFields, fields)

Yeah this way to handle the modal does the same things in a much simpler way: it is contained and control by another component without the need to compose with tracker 👌
For the fields, I guess I didn't understand the specs well, I see now. I'll update it 😅
Still gaining XP, thanks for the comments!!


Sudo

Is this a similar or duplicate feature request?

[ ] I don't know. I will go check it.
[X ] No.

Is your feature request related to a problem? Please describe.
My project directory is mounted on an EBS volume which is only accessible through root. I don't think they want me changing this.
Describe the solution you'd like
Is there a way for this extension to run sudo and gain root access, so that it can see my files? This is unusable for me without such a feature.
Describe alternatives you've considered
I don't know of any alternatives.
Does this project help you?

[x] Yes. SFTP IS AWESOME!
[ ] Yes. I want to support you.

+1

I confirm same problem. EC2 instance on AWS. I connect under one name and then I have to change it with su or use sudo, or I have to reset all files to that user.

I'd love this feature as well.

I have same problem. I tried 'sudo su -' command in 'sshCustomParams' parameter but It doesn't work.
non-working examples

"sshCustomParams": "sudo su -;"
"sshCustomParams": "\"cd \"${remotePath}\"; exec \\$SHELL -l\";sudo su -;"

+1

+1

Yes please.

Yes!

I found the solution.
Just change the directory's permission and done.

I found the solution.
Just change the directory's permission and done.

This is not a solution but security thread. In most cases people have those permissions on purpose.

I found the solution.
Just change the directory's permission and done.

This is not a solution but security thread. In most cases people have those permissions on purpose.

Hello,
"sshCustomParams": "sudo su -;", works for me!

Hello,
"sshCustomParams": "sudo su -;", works for me!

Adding to the documentation.

That solution is not working for me...
Anyway, when I'm logged using SSH and I prepend the "SU" before the commands works. Do you know how can I adjust this param (sshCustomParams) simply to do that?
Thanks in advance!


Question: any sugguestions on keeping memory usage bounded for multi-factor simulation?

Hi,
My multi-factor simulation involves hundreds of individual simulations, each individual simulation lasts from a few seconds to a few hours. when running with pypy, memory usage of worker threads (subprocesses) increase overtime, it eventually goes beyond my system's memory capacity (32GB) and triggers kernel to kill some work threads.
The figure shows  memory usage of worker threads (child0-7) grows over time:

CPython doesn't have this memory issue:

Thanks for the pointer. These graph are just imcomplete snapshots. It takes several hours to run out of memory, what shows here is the increasing trend of memory consumption for PyPy.
The chart is from memory_profiler, I guess it accounts all allocated memory of each process

Do you have any suggestions on setting pypy's gc env variables?

Given the different approaches to GC and memory management between CPython and PyPy, I'm not sure that the differences between these charts is concerning on its own. I.e. do we actually expect PyPy to return memory to the operating system such that memory_profiler would report a lower "memory used" value? Also, even after looking at the docs and code for memory_profiler, it remains unclear to me what it is actually measuring.
From the PyPy chart, it looks like each subprocess' memory consumption mostly flattens over time, but that perhaps each new simulation instance causes some marginal additional memory consumption. The questions I still have are:

Is the incremental memory consumption we see in PyPy due to a problem with PyPy? Or is it possible that the model's code is responsible for memory retention between simulation instances? That we see the floor of the CPython processes grow over time seems like a clue that something in your program may be holding onto memory (referenced objects) across simulations.

If the number of CPython processes was doubled, would your system's memory similarly become exhausted? This could be tested by using simulate_factors(..., jobs=16).

The corollary question is whether your system's memory is still eventually exhausted if fewer PyPy subprocesses are used? I.e. simulate_factors(..., jobs=4) or jobs=6.

Do the numbers you see in htop for CPython drop between simulations as we see in the CPython chart? Or does the resident size shown in htop ("RES") plateau?

Regarding PyPy GC environment variables, I workaround a different apparent bug in PyPy's garbage collector by setting PYPY_GC_NURSERY=125M. This increases the new object nursery size and transitively increases the total memory consumption, with the benefit of decreasing the number of collections and improving runtime performance for my use case. I do not have a suggestion for GC configuration for your case.
All of the above said, the problem you are experiencing could seemingly be solved if desmod spawned new simulation worker subprocesses for each simulation (or for each N simulations). I consciously chose to use persistent simulation worker subprocesses specifically with PyPy in mind. I wanted PyPy's JIT to remain "hot" between simulations, under the assumption that each simulation instance would largely have the same hot code paths. For long running simulations, optimizing for keeping PyPy's JIT hot is not as big of a concern.
I came across this in PyPy's docs (https://doc.pypy.org/en/latest/jit-hooks.html#resetting-the-jit)

releaseall()
Marks all current machine code objects as ready to release. They will be released at the next GC (unless they are currently in use in the stack of one of the threads). Doing pypyjit.releaseall(); gc.collect() is a heavy hammer that forces the JIT roughly back to the state of a newly started PyPy.

I wonder if that might have a positive effect for your case?

Hi, sorry for the long silence, this issue is gone to me after installing latest PyPy (v7.3.5).

Glad the behavior has improved with the latest PyPy. And thanks for updating this issue!


Proxy Per Azure Tenant?

I have a scenario where the client has 1 Azure AD, but has multiple forests/domains connected to this Azure AD.
I would ideally like to have 2 Proxies that would run the Proxy Service for all of these forests, rather than having 2 Proxies per Forest, as this adds up to a lot of VMs for such a small task.
Would you please consider making this forest wide service a Tenant wide service, as it seems this is the technical boundary, rather than the AD Forest?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 53684ada-fb90-0497-30d2-8c8c5d3a39ec
Version Independent ID: f6b5da43-1f40-3bdf-58cd-037632680668
Content: Azure AD password protection - Azure Active Directory
Content Source: articles/active-directory/authentication/concept-password-ban-bad-on-premises.md
Service: active-directory
Sub-service: authentication
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@mundayn  Thank you for your query. We will check it with the engineering internally and let you know accordingly.

Forwarding feedback to the product team. Thank you!

#please-close


io: Copy clears source buffer

What version of Go are you using (go version)?

$ go version
go version go1.14.2 linux/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/matus/.cache/go-build"
GOENV="/home/matus/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/matus/Code/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/matus/.local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/matus/.local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build176357012=/tmp/go-build -gno-record-gcc-switches"

What did you do?
I tried to copy bytes from buffer to Stdout, however the buffer was cleared after copy. This is not a behaviour one would expect copy but rather from move. Like when you run cp src dst on linux, you do not expect src file to be cleared.
package main

import (
	"bytes"
	"fmt"
	"io"
	"log"
	"os"
)

func main() {
	b := bytes.Buffer{}
	n, err := b.Write([]byte("foo\n"))
	if err != nil {
		log.Fatalln(err, n)
	}

	fmt.Println(b)
	io.Copy(os.Stdout, &b)
	fmt.Println(b)
}

play.golang.org

What did you expect to see?
{[102 111 111 10] 0 0}
foo
{[102 111 111 10] 0 0}

or a clear note about this behaviour in the docs.
What did you see instead?
{[102 111 111 10] 0 0}
foo
{[] 0 0}

Thank you for raising this issue. Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.
For asking questions, see:

Stack Overflow with questions tagged "go"

The Go Forum, a web-based forum

Gophers Slack, use the invite app for access. The #general channel is a good starting point.

Go Community on Hashnode with questions and posts tagged with "go"

The golang-nuts mailing list

IRC channel #go-nuts on Freenode

@davecheney this issue was not opened for asking question. I consider it a bug in a docs.

The buffer tracks both its read and write positions. The string method is simply returning you a slice of the unread data. The buffer has to keep track of the last read position otherwise if someone read from the buffer a byte at a time, the position would never advance.


GMSH: Add quad16 and hexahedron64

The patch is trivial, if you prefer a PR, let me know and I'll submit one with the diff below.
diff --git a/meshio/gmsh_io.py b/meshio/gmsh_io.py
index fc53da2..36aa8a8 100644
--- a/meshio/gmsh_io.py
+++ b/meshio/gmsh_io.py
@@ -30,6 +30,7 @@ num_nodes_per_cell = {
     'pyramid14': 14,
     'line4': 4,
     'quad16': 16,
+    'hexahedron64': 64,
     }

 # Translate meshio types to gmsh codes
@@ -52,6 +53,7 @@ _gmsh_to_meshio_type = {
         14: 'pyramid14',
         26: 'line4',
         36: 'quad16',
+        92: 'hexahedron64',
         }
 _meshio_to_gmsh_type = {v: k for k, v in _gmsh_to_meshio_type.items()}

Perhaps we can enhance this with the rest of the gmsh types (if there are any).

And yes, a PR would make things really easy for me.


Skyblock auctions rewrite & Fixes

Please describe changes

Skyblock Auctions rewrite : Now has way more options and can be faster by making simultaneous requests at once. Also included a retry and cooldown option.
It is backwards compatible, so it supports the old options... the fetch technique for every pages is by default the slower way, so might still want to update :)
sweep cache is get ( it returns a function that isn't called )
Disabled rate limit for auctions_ended because you don't need a key either ( afaik )
added J s d o c
updated index.ts ( the errors class )

Should test it first & check jsdoc because I might've made some mistakes in jsdoc
Description

[x] I've added new features. (methods or parameters)
[x] I've added jsdoc and typings.
[x] I've fixed bug. (optional you can mention a issue if there is one)
[ ] I've corrected the spelling in README, documentation, etc.
[x] I've tested my code. (npm run test)

args :
Page number - if "" or falsy, then every page is fetched; if it is an integer, then that page is fetched; if it is an array of integers, then pages x to y ( including x and y ) are fetched.
Options ( all optional ) -
noInfo : boolean, if true, then Info will not be parsed ( KIM failedPages will still exist ). do not combine with the option below
noAuctions : boolean, if true, then no auctions will be parsed ( auctions property will be an empty array ), useful for checking info only.
raw : boolean, if true, doesn't parse auctions into Auction and it stays as it is from the API. Useful for performance if low end. includeItemBytes will not suppress item bytes.
retries : number, default 3, max 100, min 0 : maximum amount of times to retry fetching a page ( if failure ) before giving up. Useful when race is enabled because EAI or ECONN_RESET tend to happen with it enabled.
cooldown: number, default 100, max 3000, min 0 : time in ms to wait for before retrying ^. Useless if retries is 0.
race: boolean, if true, multiple requests are made at the same time, which allows better speed.
includeItemBytes: boolean, if true, includes item bytes when parsing auctions. Beware of memory hogging.
}

bugs found with parsing, will fix


Cluster for Elassandra

Hello,
I'm trying to create a cluster of 4 machines with elassandra,
but we didn't find enough information to do it on https://www.elassandra.io/, please could you give me a basic level explanation of how  can I do it?,
Best regards,
Julio

Please see the cassandra doc to setup a new cluster.


In storage_sync2: failed deletions because object doesn't exist should be considered success

@LizardWizzard per your recent PR , this is not relevant as s3 API delete doesn't indicate when trying to delete a nonexistent object. @problame is it worth "ls the file" prior?

per your recent PR , this is not relevant as s3 API delete doesn't indicate when trying to delete a nonexistent object

Correct

Hmm the comment in delete_layer still references this issue. I wonder if it made sense to change the comment with the information that S3 does not error when trying to delete nonexistent files already (and if the backing storage is not s3 but the file system, i suppose one can live with the error).

yes this comment should be removed, the alternative is to always try to. "list" the object before is just a waist of resources

Note that our local fs storage has other behavior that is not consistent with real s3. For example it keeps empty "directories" while with real s3 you wont see prefixes that dont have objects in them


F# sample, Async<T> as an awaitable type

Create sample here
See #31140

@brianrourkeboll would you be able to create the samples we can show in the docs?

@Rick-Anderson Do you mean something like this?
Are there existing C# samples focusing on Task/ValueTask/Task<T>/ValueTask<T>-returning (as opposed to synchronous) endpoints? If so, I would think that any F# async samples should go alongside those. If not, I'm not sure we necessarily need to add ones for F#.
Updated treatment of Task<unit>/ValueTask<unit>(/Async<unit>)
I'm not sure it's necessarily worth calling out the updated treatment of Task<unit>/ValueTask<unit>/Async<unit> in the docs themselves—this change is more about consistency in the framework's treatment of Task<unit>/ValueTask<unit>/Async<unit> values and in bringing the framework's treatment of idiomatic F# in line with its treatment of idiomatic C#.
In F#, Task<unit>/ValueTask<unit> are idiomatically equivalent to non-generic/void-returning Task/ValueTask—in fact, there is no non-generic/void Async type in F#, and Async<unit> is used instead.
Basically, by adding support for Async<'T> in minimal APIs, a decision had to be made around how Async<unit> would be treated. The framework's treatment of Task<unit>/ValueTask<unit> were updated to be consistent with that, including in JSON serialization and OpenAPI schema generation.
I think it would probably be enough just to ensure that this change is mentioned in the release notes for 9.0.
Automatic awaiting of Async<'T>
For this change, on the other hand, in addition to including it in the release notes, it might be enough to update places like the following (surfaced here) in the docs to indicate the added support for F# Async<'T>:
https://github.com/dotnet/AspNetCore.Docs/blob/63f5d2e7f3f46fec4ccf0ef127a4c4cd730d6b25/aspnetcore/fundamentals/minimal-apis/responses.md?plain=1#L13-L17
Minimal endpoints support the following types of return values:

- 1. `string` - This includes `Task<string>` and `ValueTask<string>`.
- 1. `T` (Any other type) - This includes `Task<T>` and `ValueTask<T>`.
- 1. `IResult` based - This includes `Task<IResult>` and `ValueTask<IResult>`.
+ 1. `string` - This includes `Task<string>`, `ValueTask<string>`, and `Async<string>` (in F#).
+ 1. `T` (Any other type) - This includes `Task<T>`, `ValueTask<T>`, and `Async<T>` (in F#).
+ 1. `IResult` based - This includes `Task<IResult>`, `ValueTask<IResult>`, and `Async<IResult>` (in F#).


Refactored the server startup code

Improved the order that methods are called during server startup to match the order in which Express expects things to be configured.
Improved importing and usage of types from Express.
Added some additional exports, as they are likely needed.

These changes are working better for me.  And I think it shows a better overall structure and order of methods that developers can override and use to customize their server.
Thanks again!
Yavin Five

Excellent thank you @yavin5 !


Runtime macro article

completed decl_storage macro

[ ] Are the audience and objective of the document clear? E.g. a document for developers that should teach them about transaction fees.

[ ] Is the writing:

[ ] Clear: No jargon.
[ ] Precise: No ambiguous meanings.
[ ] Concise: Free of superfluous detail.

[ ] Does it follow our style guide?

[ ] If this is a new page, does the PR include the appropriate infrastructure, e.g. adding the page to a sidebar?

[ ] Build the page ($ cd website && yarn start). Does it render properly? E.g. no funny lists or formatting.

[ ] Do links go to rustdocs or devhub articles rather than code?

[ ] If this PR addresses an issue in the queue, have you referenced it in the description?

@joepetrowski @danforbes
I finished the first draft of the macro knowledge base article. What do you think about the approach and structure of this article.
@wheresaddie
Feel free to propose/edit about the english in the article
@JoshOrndorff (if you have time before your leave)  @bkchr
Could you take a look at the technical accuracy and what you think in general about the article. I also feel particularly weak in explaining the app_crypto! and impl_runtime_apis! sections.
Thank you for the input!

fyi: https://github.com/substrate-developer-hub/recipes/issues/217
I also PR'ed the src and macro-expanded src in docs/asset folder, but didn't find a way to nicely present them. So I am pointing to github gist now when referring to source code.

@danforbes @joepetrowski @bkchr @thiolliere
Hi, Addie has made a few nice edit/rewrite. And I want to see if we can wrap this PR up.

Dan / Joe: what do you think about the content and structure
Basti / Guillaume: what do you think about the technical correctness? I know that Guillaume is having rewrite on construct_runtime (and deprecating impl_outer_*). Once that's merge, I will update the document also.

Thanks.

I would pull out some of the implementation notes and make this a higher level overview of macros in Substrate. Then each macro (at least the decl_* ones) should have their own page with examples of how to use them. May also be a better fit for recipes.

is this something you want to do @jimmychu0807 ? otherwise I can start on this as I agree with @joepetrowski on having this extended to a conceptual overview with each macro definition existing on its own page with examples of how to implement

Sorry that I haven't worked on this. Actually I need a core-dev to verify the accuracy of the article now, and then I will rework the structure, put them into separate pages afterwards.

@thiolliere Would you help review about the implementation notes in each Macro and see if they are correct. If not, please point out the inaccuracy. Thanks.

@thiolliere  Thank you for the review and feedback 🙏

@joepetrowski @wheresaddie
Given the content has been reviewed by core-dev (and updated), let's decide how to separate all the macro details?

putting them in knowledge base, under Runtime:Runtime Macros:<macro name> (Can we have a 3rd level in our document hierarchy?)
putting them in knowledge base, under Advanced:Runtime Macros:<macro name>
putting them in recipe?

@joepetrowski @wheresaddie
Given the content has been reviewed by core-dev (and updated), let's decide how to separate all the macro details?

Putting them in knowledge base, under Runtime:Runtime Macros:<macro name> (Can we have a 3rd level in our document hierarchy?)
Putting them in knowledge base, under Advanced:Runtime Macros:<macro name>
Putting them in recipe?

I would go with 1 or 2 but will defer to @joepetrowski for the final call on this. Once we define a hierarchy, I am happy to work with you @jimmychu0807 to further document the subjects

I am merging this for now.
@joepetrowski when you have time to review and suggest how to split up this article, I am happy to come back and work on this.


Local Script file not found

When using the 1.0 action, the script process file is not found.
Run fletort/jinja2-template-action@v1
Run pip install jinja2-cli
Defaulting to user installation because normal site-packages is not writeable
Collecting jinja2-cli
  Downloading jinja2_cli-0.8.2-py2.py3-none-any.whl (6.[5](https://github.com/fletort-org/test2/actions/runs/9953817495/job/27498124154#step:7:6) kB)
Requirement already satisfied: jinja2 in /usr/lib/python3/dist-packages (from jinja2-cli) (3.0.3)
Installing collected packages: jinja2-cli
Successfully installed jinja2-cli-0.8.2
find: ‘./process_file.sh’: No such file or directory

See: https://github.com/actions/github-script/issues/322 for the resolution

Fix in 1.0.1


Remove testing constants from app.js

Remove the following debug variables.  If they are needed can they be coded into local-dev.html?
var _WebAPIServer = "https://dan-af-dev/piwebapi";
var afServer = "dan-af-dev"
var afDatabase = "Mineral Processing";
var databaseRootURLComplete;
var elementPath = '\\\\DAN-AF-DEV\\Mineral Processing\\Toll Ore Delivery\\T-101'

Is there any way reference the contents of sym-treemap-template.html and treemap.css into local-dev.html?
The reason is that as we make changes to the template html it might be good to see it reflected in the local-dev.
This is a low priority, the files can be manually updated.

Yes, we should be able to add them as references into local-dev.html.  See how local-dev.html references the scripts.

One problem with including the template into the local-dev:

If we use angular templating (e.g. replacing id="whatever" with id={{elementId}}) in the template file, the local-dev stuff will not follow suit unless we add some other templating solution locally.

That's not a huge problem, we can add some quick & dirty templating in there.

i think we're done here, reopen if not.


Syntax: Is "or" operator allowed in forloop

I have a statement
{% for enum in types.enums where enum.localName == "someEnum" or enum.localName = "someOtherEnum" %}
However when i try to execute this statement i get the following error.
 'if' expression error: dangling token
At first i thought it was a problem with if somewhere in my template. Took me a while to figure out that the "or" was causing this error. Am i doing something wrong here or is "or" not allowed in for loop.

or is allowed https://stencil.fuller.li/en/latest/builtins.html#built-in-filters but you are doing = in the second part not equality

How could have i missed it. Thanks :)


Second brunch

@MukhailoK Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.


Fix #46: Enable comments inside quasiquotes

Quasiquotes preserve now their parsed origin and tokens and syntax allow you
to access any comments from the original source.
The fix consists in tokenizing, getting the token positions, creating
the origin Origin.Parsed and setting it to term quasiquotes. Pattern
quasiquotes cannot benefit from this, because comments are only
preserved in the token level, not the tree level. Therefore, one cannot
pattern match on a quasiquote with a comment (because of unapply).
There are some tests failing because show[Structure], implemented
in TreeStructure.scala, does not handle Unquote. Therefore, it
outputs an empty string when the spliced quasiquote variable should be.
Fixing this requires changing the accessibility of Unquote and
"magically" detecting the value of that spliced variable. The actual
meta tree has all this information, but I find it difficult to map it to
the tokens. Not a trivial task. Maybe we should rethink what show[Structure]
means and what's its actual relation with tokens (not very clear to me, atm).

Maybe the good solution is to decouple Structure from tokens... But I'm unsure until which points this is correct, I understand that scala meta is trying to make quasiquotes a real compile-time construct.
My change in syntax respects how "val a = 1 // comment".parse[Source].get.syntax behaves, instead of outputting the result of the spliced variables. This increases the number of test failures from 9 to 16, but I think it's the right thing to do if we really want "quasiquotes comments" in the syntax.

Is there any update on this?

Not yet, unfortunately. Recently, I've been focusing on the scalac -> meta converter. I'll do my best to get back to this soon.

It looks like pushing this PR further will require a significant design effort that I don't have time for right now. At the moment, the main and only priority is shipping semantic API asap, so I'll close this PR for the time being.


Deep Graph Infomax demo error: HinSAGE with multiple node types

Describe the bug
In the Deep Graph Infomax demo. The function run_deep_graph_infomax if the base_model is HinSAGE with multiple node types.
To Reproduce
A minimal example to trigger the error
from stellargraph.mapper import (
    CorruptedGenerator,
    HinSAGENodeGenerator,
)
from stellargraph import StellarGraph
from stellargraph.layer import DeepGraphInfomax, HinSAGE
import pandas as pd

square_edges = pd.DataFrame(
    {"source": ["a", "b", "c", "d", "a"], "target": ["b", "c", "d", "a", "c"]}
)
square_foo = pd.DataFrame({"y": [0.5], "z": [50]}, index=["a"])
square_bar = pd.DataFrame(
    {"y": [0.4, 0.1, 0.9], "z": [100, 200, 300]}, index=["b", "c", "d"]
)
G = StellarGraph({"foo": square_foo, "bar": square_bar}, square_edges)

def run_deep_graph_infomax(
            base_model, generator, epochs, reorder=lambda sequence, subjects: subjects):
    corrupted_generator = CorruptedGenerator(generator)
    gen = corrupted_generator.flow(G.nodes())                     # <============= This line leads to an error
    infomax = DeepGraphInfomax(base_model, corrupted_generator)

hinsage_generator = HinSAGENodeGenerator(
    G, batch_size=1000, num_samples=[5], head_node_type="bar")
hinsage_model = HinSAGE(
    layer_sizes=[128], activations=["relu"], generator=hinsage_generator)
run_deep_graph_infomax(hinsage_model, hinsage_generator, epochs=10)

Observed behavior
Error message
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-5-f6c1390f7340> in <module>
     13     layer_sizes=[128], activations=["relu"], generator=hinsage_generator
     14 )
---> 15 run_deep_graph_infomax(hinsage_model, hinsage_generator, epochs=10)

<ipython-input-5-f6c1390f7340> in run_deep_graph_infomax(base_model, generator, epochs, reorder)
      3 ):
      4     corrupted_generator = CorruptedGenerator(generator)
----> 5     gen = corrupted_generator.flow(G.nodes())
      6     infomax = DeepGraphInfomax(base_model, corrupted_generator)
      7

/data/work/yunan/software/anaconda3/lib/python3.7/site-packages/stellargraph/mapper/corrupted.py in flow(self, *args, **kwargs)
    117         """
    118         return CorruptedSequence(
--> 119             self.base_generator.flow(*args, **kwargs),
    120             self.corrupt_index_groups,
    121             self.base_generator.num_batch_dims(),

/data/work/yunan/software/anaconda3/lib/python3.7/site-packages/stellargraph/mapper/sampled_node_generators.py in flow(self, node_ids, targets, shuffle, seed)
    145         if len(invalid) > 0:
    146             raise ValueError(
--> 147                 f"node_ids: expected all nodes to be of type {expected_node_type}, "
    148                 f"found some nodes with wrong type: {comma_sep(invalid, stringify=format)}"
    149             )

ValueError: node_ids: expected all nodes to be of type bar, found some nodes with wrong type: 3

Expected behavior
Should not raise any error
Comments
The original example didn't crash because there is only one node type (paper) in the Cora dataset. My proposed solution is to add one more argument node_ids to the function run_deep_graph_infomax and replace the line
gen = corrupted_generator.flow(G.nodes())

with
gen = corrupted_generator.flow(node_ids)

Hi, thanks for filing an issue, but I'm a little confused! Are you suggesting the demo could be changed to make it easier to copy paste the code to run DGI with HinSAGE?
As you note, the correct thing to do is to only pass in nodes of the type head_node_type. This can be done with, for instance, G.nodes(node_type="bar") instead of G.nodes().


v1.0.1_test-2: Unable to see Notifications in NP docker logs

With v1.0.1_test-2, Unable to see Notifications in NP docker logs
Have enabled to Listen to controller API and able to see the following prints.
But when Alarms are raised , Attribute changes are done , Obhect created ot deleted.
We are unable to see the notification prints in Docker logs.
Docker prints:
ease-number":"1.0.1","operation-name":"/v1/listen-to-controllers","response-code":204}response code:204
[05:35:07.825] WARN (1): controller stream for OpenDayLight1 already active
[05:35:07.825] WARN (1): controller stream for OpenDayLight1 already active
[05:35:07.825] WARN (1): device stream for OpenDayLight1 already active
POST /v1/notify-device-alarms 204 253.607 ms - -
callback : POST http://xxx:xxx/v1/record-service
[05:35:35.620] INFO (1): Active subscribers:
[05:35:35.622] INFO (1): /v1/notify-controller-attribute-value-changes -> MicroWaveDeviceInventory/1.1.1,
[05:35:35.624] INFO (1): /v1/notify-controller-object-creations ->
[05:35:35.625] INFO (1): /v1/notify-controller-object-deletions ->
[05:35:35.627] INFO (1): /v1/notify-device-alarms -> MicroWaveDeviceInventory/1.1.1,
[05:35:35.630] INFO (1): /v1/notify-device-attribute-value-changes -> MicroWaveDeviceInventory/1.1.1,
[05:35:35.633] INFO (1): /v1/notify-device-object-creations -> MicroWaveDeviceInventory/1.1.1,
[05:35:35.637] INFO (1): /v1/notify-device-object-deletions -> MicroWaveDeviceInventory/1.1.1,
POST /v1/remove-controller 204 269.635 ms - -

This issue most likely concerns the handling of a non-reachable controller (reconnection of np-streams to controller). Closed issues which reference this known issue:
https://github.com/openBackhaul/NotificationProxy/issues/46
https://github.com/openBackhaul/NotificationProxy/issues/28
The problem most likely is not seated in the NotificationProxy but on the Controller (SSE-Server), because the SSE-Client (in NP) should never receive a 404 code which leads to permanent closing of stream. The only valid http codes for SSE are 301, 307, 200 and 204. This may be a configuration issue on the controller.
Reference: https://javascript.info/server-sent-events#reconnection


10:34:06,114 INFO  org.apache.flink.runtime.taskexecutor.TaskExecutor            - Un-registering task and sending final execution state FINISHED to JobManager for task hoodie_stream_write (3/4)#0 ff5491c88ffc17a816e22c29b6da47be.
10:34:06,114 INFO  org.apache.flink.runtime.taskmanager.Task                     - hoodie_stream_write (1/4)#0<PHONE_NUMBER>36b8f4831890fa2934fe2c) switched from RUNNING to FINISHED.
10:34:06,115 INFO  org.apache.flink.runtime.taskmanager.Task                     - Freeing task resources for hoodie_stream_write (1/4)#0<PHONE_NUMBER>36b8f4831890fa2934fe2c).
10:34:06,115 INFO  org.apache.flink.runtime.taskexecutor.TaskExecutor            - Un-registering task and sending final execution state FINISHED to JobManager for task hoodie_stream_write (4/4)#0 5e2085d96585101e586a7ea47bc56a98.
10:34:06,115 INFO  org.apache.flink.runtime.taskexecutor.TaskExecutor            - Un-registering task and sending final execution state FINISHED to JobManager for task hoodie_stream_write (1/4)#0<PHONE_NUMBER>36b8f4831890fa2934fe2c.
10:34:06,115 INFO  org.apache.hudi.common.table.HoodieTableMetaClient            - Finished Loading Table of type COPY_ON_WRITE(version=1, baseFileFormat=PARQUET) from file:///d:/yuou/dev/ods/mmt-new/router_configure/configure_area
10:34:06,115 INFO  org.apache.hudi.common.table.HoodieTableMetaClient            - Loading Active commit timeline for file:///d:/yuou/dev/ods/mmt-new/router_configure/configure_area
10:34:06,115 INFO  org.apache.flink.runtime.executiongraph.ExecutionGraph        - hoodie_stream_write (3/4) (ff5491c88ffc17a816e22c29b6da47be) switched from RUNNING to FINISHED.
10:34:06,116 INFO  org.apache.flink.runtime.executiongraph.ExecutionGraph        - hoodie_stream_write (4/4) (5e2085d96585101e586a7ea47bc56a98) switched from RUNNING to FINISHED.
10:34:06,117 INFO  org.apache.flink.runtime.executiongraph.ExecutionGraph        - hoodie_stream_write (1/4)<PHONE_NUMBER>36b8f4831890fa2934fe2c) switched from RUNNING to FINISHED.
10:34:06,117 INFO  org.apache.hudi.common.table.timeline.HoodieActiveTimeline    - Loaded instants upto : Option{val=[==>20210923103405__commit__INFLIGHT]}
10:34:06,118 INFO  org.apache.hudi.common.table.view.FileSystemViewManager       - Creating View Manager with storage type :REMOTE_FIRST
10:34:06,118 INFO  org.apache.hudi.common.table.view.FileSystemViewManager       - Creating remote first table view
10:34:06,143 INFO  org.apache.hudi.table.marker.DirectWriteMarkers               - Creating Marker Path=file:/d:/yuou/dev/ods/mmt-new/router_configure/configure_area/.hoodie/.temp/20210923103405/70b872ee-bb13-4296-8d2b-e541ba27d704_1-4-0_20210923103405.parquet.marker.CREATE
10:34:06,145 INFO  org.apache.hudi.table.marker.DirectWriteMarkers               - [direct] Created marker file file:/d:/yuou/dev/ods/mmt-new/router_configure/configure_area/.hoodie/.temp/20210923103405/70b872ee-bb13-4296-8d2b-e541ba27d704_1-4-0_20210923103405.parquet.marker.CREATE in 3 ms
10:34:06,256 WARN  org.apache.hadoop.io.compress.zlib.ZlibFactory                - Failed to load/initialize native-zlib library
10:34:06,256 INFO  org.apache.hadoop.io.compress.CodecPool                       - Got brand-new compressor [.gz]
10:34:06,542 INFO  org.apache.hudi.io.HoodieCreateHandle                         - New CreateHandle for partition : with fileId 70b872ee-bb13-4296-8d2b-e541ba27d704
10:34:06,563 INFO  org.apache.hudi.common.util.queue.IteratorBasedQueueProducer  - starting to buffer records
10:34:06,564 INFO  org.apache.hudi.common.util.queue.BoundedInMemoryExecutor     - starting consumer thread
10:34:06,588 INFO  org.apache.hudi.common.util.queue.IteratorBasedQueueProducer  - finished buffering records
10:34:06,599 INFO  org.apache.hudi.io.HoodieCreateHandle                         - Closing the file 70b872ee-bb13-4296-8d2b-e541ba27d704 as we are done with all the records 1
10:34:07,010 INFO  org.apache.hudi.io.HoodieCreateHandle                         - CreateHandle for partitionPath  fileID 70b872ee-bb13-4296-8d2b-e541ba27d704, took 882 ms.
10:34:07,010 INFO  org.apache.hudi.common.util.queue.BoundedInMemoryExecutor     - Queue Consumption is done; notifying producer threads
10:34:07,013 INFO  org.apache.hudi.client.AbstractHoodieClient                   - Stopping Timeline service !!
10:34:07,014 INFO  org.apache.flink.runtime.taskmanager.Task                     - hoodie_stream_write (2/4)#0 (d48422b9607bf34237abcaf9cbca24a2) switched from RUNNING to FINISHED.
10:34:07,014 INFO  org.apache.flink.runtime.taskmanager.Task                     - Freeing task resources for hoodie_stream_write (2/4)#0 (d48422b9607bf34237abcaf9cbca24a2).
10:34:07,015 INFO  org.apache.flink.runtime.taskexecutor.TaskExecutor            - Un-registering task and sending final execution state FINISHED to JobManager for task hoodie_stream_write (2/4)#0 d48422b9607bf34237abcaf9cbca24a2.
10:34:07,015 INFO  org.apache.flink.runtime.taskmanager.Task                     - Sink: clean_commits (1/1)#0 (e46f7227496a98cb8360e4afa2fcdca1) switched from RUNNING to FINISHED.
10:34:07,015 INFO  org.apache.flink.runtime.taskmanager.Task                     - Freeing task resources for Sink: clean_commits (1/1)#0 (e46f7227496a98cb8360e4afa2fcdca1).
10:34:07,016 INFO  org.apache.flink.runtime.taskexecutor.TaskExecutor            - Un-registering task and sending final execution state FINISHED to JobManager for task Sink: clean_commits (1/1)#0 e46f7227496a98cb8360e4afa2fcdca1.
10:34:07,016 INFO  org.apache.flink.runtime.executiongraph.ExecutionGraph        - hoodie_stream_write (2/4) (d48422b9607bf34237abcaf9cbca24a2) switched from RUNNING to FINISHED.
10:34:07,017 INFO  org.apache.flink.runtime.executiongraph.ExecutionGraph        - Sink: clean_commits (1/1) (e46f7227496a98cb8360e4afa2fcdca1) switched from RUNNING to FINISHED.
10:34:07,018 INFO  org.apache.flink.runtime.executiongraph.ExecutionGraph        - Job insert-into_default_catalog.default_database.configure_area (63fd2fc9f76ebcbf9b7d3d47dabbdf38) switched from state RUNNING to FINISHED.
10:34:07,018 INFO  org.apache.flink.runtime.checkpoint.CheckpointCoordinator     - Stopping checkpoint coordinator for job 63fd2fc9f76ebcbf9b7d3d47dabbdf38.
10:34:07,019 INFO  org.apache.hudi.client.AbstractHoodieWriteClient              - Committing<PHONE_NUMBER>3405 action commit
10:34:07,020 INFO  org.apache.hudi.common.table.HoodieTableMetaClient            - Loading HoodieTableMetaClient from file:///d:/yuou/dev/ods/mmt-new/router_configure/configure_area
10:34:07,020 INFO  org.apache.flink.runtime.checkpoint.StandaloneCompletedCheckpointStore  - Shutting down
10:34:07,021 INFO  org.apache.hudi.common.table.HoodieTableConfig                - Loading table properties from file:/d:/yuou/dev/ods/mmt-new/router_configure/configure_area/.hoodie/hoodie.properties
10:34:07,022 INFO  org.apache.hudi.common.table.HoodieTableMetaClient            - Finished Loading Table of type COPY_ON_WRITE(version=1, baseFileFormat=PARQUET) from file:///d:/yuou/dev/ods/mmt-new/router_configure/configure_area
10:34:07,023 INFO  org.apache.hudi.common.table.HoodieTableMetaClient            - Loading Active commit timeline for file:///d:/yuou/dev/ods/mmt-new/router_configure/configure_area
10:34:07,025 INFO  org.apache.hudi.common.table.timeline.HoodieActiveTimeline    - Loaded instants upto : Option{val=[==>20210923103405__commit__INFLIGHT]}
10:34:07,026 INFO  org.apache.hudi.common.table.view.FileSystemViewManager       - Creating View Manager with storage type :REMOTE_FIRST
10:34:07,026 INFO  org.apache.hudi.common.table.view.FileSystemViewManager       - Creating remote first table view
10:34:07,028 INFO  org.apache.hudi.common.util.CommitUtils                       - Creating  metadata for null numWriteStats:1numReplaceFileIds:0
10:34:07,028 INFO  org.apache.flink.runtime.minicluster.MiniCluster              - Shutting down Flink Mini Cluster
10:34:07,028 INFO  org.apache.flink.runtime.dispatcher.StandaloneDispatcher      - Job 63fd2fc9f76ebcbf9b7d3d47dabbdf38 reached globally terminal state FINISHED.
10:34:07,028 INFO  org.apache.hudi.client.AbstractHoodieWriteClient              - Committing<PHONE_NUMBER>3405 action commit
10:34:07,029 INFO  org.apache.flink.runtime.dispatcher.DispatcherRestEndpoint    - Shutting down rest endpoint.
10:34:07,029 INFO  org.apache.flink.runtime.taskexecutor.TaskExecutor            - Stopping TaskExecutor akka://flink/user/rpc/taskmanager_0.
10:34:07,030 INFO  org.apache.flink.runtime.taskexecutor.TaskExecutor            - Close ResourceManager connection 23667cd006bb26eb958d7cd585d4d7de.
10:34:07,031 INFO  org.apache.flink.runtime.resourcemanager.StandaloneResourceManager  - Closing TaskExecutor connection a6e88966-162b-44b4-b2fd-39461a1a440c because: The TaskExecutor is shutting down.
10:34:07,040 INFO  org.apache.flink.runtime.jobmaster.JobMaster                  - Stopping the JobMaster for job insert-into_default_catalog.default_database.configure_area(63fd2fc9f76ebcbf9b7d3d47dabbdf38).
10:34:07,044 INFO  org.apache.flink.runtime.taskexecutor.TaskExecutor            - Close JobManager connection for job 63fd2fc9f76ebcbf9b7d3d47dabbdf38.
10:34:07,045 INFO  org.apache.hudi.client.AbstractHoodieClient                   - Stopping Timeline service !!
10:34:07,052 INFO  org.apache.flink.runtime.taskexecutor.slot.TaskSlotTableImpl  - Free slot TaskSlot(index:3, state:ALLOCATED, resource profile: ResourceProfile{managedMemory=16.000mb (16777216 bytes), networkMemory=8.000mb (8388608 bytes)}, allocationId: bc89ec13c8cfe5f30f33b9b92894ad6d, jobId: 63fd2fc9f76ebcbf9b7d3d47dabbdf38).
10:34:07,056 INFO  org.apache.flink.runtime.taskexecutor.slot.TaskSlotTableImpl  - Free slot TaskSlot(index:0, state:ALLOCATED, resource profile: ResourceProfile{managedMemory=16.000mb (16777216 bytes), networkMemory=8.000mb (8388608 bytes)}, allocationId: 764034c3267a443562b693e46aad20e5, jobId: 63fd2fc9f76ebcbf9b7d3d47dabbdf38).
10:34:07,057 INFO  org.apache.flink.runtime.taskexecutor.slot.TaskSlotTableImpl  - Free slot TaskSlot(index:6, state:ALLOCATED, resource profile: ResourceProfile{managedMemory=16.000mb (16777216 bytes), networkMemory=8.000mb (8388608 bytes)}, allocationId: 45b2be58c17c46712a1f99ffb71124c0, jobId: 63fd2fc9f76ebcbf9b7d3d47dabbdf38).
10:34:07,057 INFO  org.apache.flink.runtime.taskexecutor.slot.TaskSlotTableImpl  - Free slot TaskSlot(index:4, state:ALLOCATED, resource profile: ResourceProfile{managedMemory=16.000mb (16777216 bytes), networkMemory=8.000mb (8388608 bytes)}, allocationId: 3b5cadd7193ba9bd4dc2cf7ccc9667b2, jobId: 63fd2fc9f76ebcbf9b7d3d47dabbdf38).
10:34:07,057 INFO  org.apache.flink.runtime.taskexecutor.slot.TaskSlotTableImpl  - Free slot TaskSlot(index:2, state:ALLOCATED, resource profile: ResourceProfile{managedMemory=16.000mb (16777216 bytes), networkMemory=8.000mb (8388608 bytes)}, allocationId: 4a41e5491be9026da0456dd23f0709e4, jobId: 63fd2fc9f76ebcbf9b7d3d47dabbdf38).
10:34:07,058 INFO  org.apache.flink.runtime.taskexecutor.slot.TaskSlotTableImpl  - Free slot TaskSlot(index:5, state:ALLOCATED, resource profile: ResourceProfile{managedMemory=16.000mb (16777216 bytes), networkMemory=8.000mb (8388608 bytes)}, allocationId: 69e4facaa72255fa4011ad886be6e830, jobId: 63fd2fc9f76ebcbf9b7d3d47dabbdf38).
10:34:07,058 INFO  org.apache.flink.runtime.taskexecutor.slot.TaskSlotTableImpl  - Free slot TaskSlot(index:7, state:ALLOCATED, resource profile: ResourceProfile{managedMemory=16.000mb (16777216 bytes), networkMemory=8.000mb (8388608 bytes)}, allocationId: f738d448f48642d75b3bf69475df9c0a, jobId: 63fd2fc9f76ebcbf9b7d3d47dabbdf38).
10:34:07,058 INFO  org.apache.flink.runtime.taskexecutor.slot.TaskSlotTableImpl  - Free slot TaskSlot(index:1, state:ALLOCATED, resource profile: ResourceProfile{managedMemory=16.000mb (16777216 bytes), networkMemory=8.000mb (8388608 bytes)}, allocationId: 21a45995954d4f80f8e9559bd6c050c2, jobId: 63fd2fc9f76ebcbf9b7d3d47dabbdf38).
10:34:07,066 INFO  org.apache.flink.runtime.taskexecutor.DefaultJobLeaderService  - Stop job leader service.
10:34:07,067 INFO  org.apache.flink.runtime.state.TaskExecutorLocalStateStoresManager  - Shutting down TaskExecutorLocalStateStoresManager.
10:34:07,077 INFO  org.apache.flink.runtime.dispatcher.DispatcherRestEndpoint    - Removing cache directory C:\Users\zhujh\AppData\Local\Temp\3\flink-web-ui
10:34:07,080 INFO  org.apache.flink.runtime.dispatcher.DispatcherRestEndpoint    - Shut down complete.
10:34:07,084 INFO  org.apache.flink.runtime.resourcemanager.StandaloneResourceManager  - Shut down cluster because application is in CANCELED, diagnostics DispatcherResourceManagerComponent has been closed..
10:34:07,084 INFO  org.apache.flink.runtime.entrypoint.component.DispatcherResourceManagerComponent  - Closing components.
10:34:07,084 INFO  org.apache.flink.runtime.io.disk.FileChannelManagerImpl       - FileChannelManager removed spill file directory C:\Users\zhujh\AppData\Local\Temp\3\flink-io-828c2b8c-9406-42ce-a880-da7d89a25952
10:34:07,085 INFO  org.apache.flink.runtime.io.network.NettyShuffleEnvironment   - Shutting down the network environment and its components.
10:34:07,085 INFO  org.apache.flink.runtime.dispatcher.runner.SessionDispatcherLeaderProcess  - Stopping SessionDispatcherLeaderProcess.
10:34:07,086 INFO  org.apache.flink.runtime.io.disk.FileChannelManagerImpl       - FileChannelManager removed spill file directory C:\Users\zhujh\AppData\Local\Temp\3\flink-netty-shuffle-d89eeb4b-bb89-4a97-9902-3a9b68d9d6e9
10:34:07,085 INFO  org.apache.flink.runtime.dispatcher.StandaloneDispatcher      - Stopping dispatcher akka://flink/user/rpc/dispatcher_2.
10:34:07,086 INFO  org.apache.flink.runtime.taskexecutor.KvStateService          - Shutting down the kvState service and its components.
10:34:07,086 INFO  org.apache.flink.runtime.dispatcher.StandaloneDispatcher      - Stopping all currently running jobs of dispatcher akka://flink/user/rpc/dispatcher_2.
10:34:07,087 INFO  org.apache.flink.runtime.taskexecutor.DefaultJobLeaderService  - Stop job leader service.
10:34:07,087 INFO  org.apache.flink.runtime.resourcemanager.slotmanager.SlotManagerImpl  - Closing the SlotManager.
10:34:07,087 INFO  org.apache.flink.runtime.resourcemanager.slotmanager.SlotManagerImpl  - Suspending the SlotManager.
10:34:07,088 INFO  org.apache.flink.runtime.filecache.FileCache                  - removed file cache directory C:\Users\zhujh\AppData\Local\Temp\3\flink-dist-cache-a14975c7-d8f8-413c-86c0-3b9990d84ec5
10:34:07,089 INFO  org.apache.flink.runtime.taskexecutor.TaskExecutor            - Stopped TaskExecutor akka://flink/user/rpc/taskmanager_0.
10:34:07,163 INFO  org.apache.hudi.common.table.timeline.HoodieActiveTimeline    - Marking instant complete [==>20210923103405__commit__INFLIGHT]
10:34:07,164 INFO  org.apache.hudi.common.table.timeline.HoodieActiveTimeline    - Checking for file exists ?file:/d:/yuou/dev/ods/mmt-new/router_configure/configure_area/.hoodie/20210923103405.inflight
10:34:07,166 INFO  org.apache.hudi.common.table.timeline.HoodieActiveTimeline    - Create new file for toInstant ?file:/d:/yuou/dev/ods/mmt-new/router_configure/configure_area/.hoodie/20210923103405.commit
10:34:07,166 INFO  org.apache.hudi.common.table.timeline.HoodieActiveTimeline    - Completed [==>20210923103405__commit__INFLIGHT]
10:34:07,166 INFO  org.apache.hudi.common.table.HoodieTableMetaClient            - Loading HoodieTableMetaClient from file:///d:/yuou/dev/ods/mmt-new/router_configure/configure_area
10:34:07,168 INFO  org.apache.hudi.common.table.HoodieTableConfig                - Loading table properties from file:/d:/yuou/dev/ods/mmt-new/router_configure/configure_area/.hoodie/hoodie.properties
10:34:07,168 INFO  org.apache.hudi.common.table.HoodieTableMetaClient            - Finished Loading Table of type COPY_ON_WRITE(version=1, baseFileFormat=PARQUET) from file:///d:/yuou/dev/ods/mmt-new/router_configure/configure_area
10:34:07,169 INFO  org.apache.hudi.common.table.HoodieTableMetaClient            - Loading Active commit timeline for file:///d:/yuou/dev/ods/mmt-new/router_configure/configure_area
10:34:07,171 INFO  org.apache.hudi.common.table.timeline.HoodieActiveTimeline    - Loaded instants upto : Option{val=[20210923103405__commit__COMPLETED]}
10:34:07,172 INFO  org.apache.hudi.common.table.view.FileSystemViewManager       - Creating View Manager with storage type :MEMORY
10:34:07,172 INFO  org.apache.hudi.common.table.view.FileSystemViewManager       - Creating in-memory based Table View
10:34:07,184 INFO  org.apache.hudi.table.marker.DirectWriteMarkers               - Removing marker directory at file:/d:/yuou/dev/ods/mmt-new/router_configure/configure_area/.hoodie/.temp/20210923103405
10:34:07,202 INFO  org.apache.hudi.common.table.timeline.HoodieActiveTimeline    - Loaded instants upto : Option{val=[20210923103405__commit__COMPLETED]}
10:34:07,204 INFO  org.apache.hudi.table.HoodieTimelineArchiveLog                - No Instants to archive
10:34:07,204 INFO  org.apache.hudi.client.AbstractHoodieWriteClient              - Committed<PHONE_NUMBER>3405
10:34:07,204 INFO  org.apache.hudi.sink.StreamWriteOperatorCoordinator           - Commit instant [20210923103405] success!
10:34:07,204 INFO  org.apache.hudi.sink.StreamWriteOperatorCoordinator           - Executor executes action [handle write metadata event for instant<PHONE_NUMBER>3405] success!
10:34:07,213 INFO  org.apache.flink.runtime.jobmaster.slotpool.SlotPoolImpl      - Suspending SlotPool.
10:34:07,213 INFO  org.apache.flink.runtime.jobmaster.JobMaster                  - Close ResourceManager connection 23667cd006bb26eb958d7cd585d4d7de: Stopping JobMaster for job insert-into_default_catalog.default_database.configure_area(63fd2fc9f76ebcbf9b7d3d47dabbdf38)..
10:34:07,213 INFO  org.apache.flink.runtime.jobmaster.slotpool.SlotPoolImpl      - Stopping SlotPool.
10:34:07,216 INFO  org.apache.flink.runtime.rest.handler.legacy.backpressure.BackPressureRequestCoordinator  - Shutting down back pressure request coordinator.
10:34:07,216 INFO  org.apache.flink.runtime.dispatcher.StandaloneDispatcher      - Stopped dispatcher akka://flink/user/rpc/dispatcher_2.
10:34:07,219 INFO  org.apache.flink.runtime.rpc.akka.AkkaRpcService              - Stopping Akka RPC service.
10:34:07,262 INFO  org.apache.flink.runtime.rpc.akka.AkkaRpcService              - Stopping Akka RPC service.
10:34:07,262 INFO  org.apache.flink.runtime.rpc.akka.AkkaRpcService              - Stopped Akka RPC service.
10:34:07,277 INFO  org.apache.flink.runtime.blob.PermanentBlobCache              - Shutting down BLOB cache
10:34:07,278 INFO  org.apache.flink.runtime.blob.TransientBlobCache              - Shutting down BLOB cache
10:34:07,280 INFO  org.apache.flink.runtime.blob.BlobServer                      - Stopped BLOB server at <IP_ADDRESS>:65389
10:34:07,280 INFO  org.apache.flink.runtime.rpc.akka.AkkaRpcService              - Stopped Akka RPC service.

I guess it is because the cluster resource is not enough to start up all the write tasks, you can set up table option 'write.tasks' = '1' and try again.

set up table option 'write.tasks' = '1',try again,result is Only one to two pieces of data can be written。I Change to spark write write all

Closing this as we have solution working. If you are still facing issues, feel free to re-open. or if you get past the issue by some other work around, do post it here so that it could benefit others in the community. thanks!

I am facing this issue even after updating the writer.task value to 1. FYI, I am using the Flink SQL Client on AWS EMR cluster.
My Flink configuration JSON looks like this:
[
    {
      "Classification": "flink-conf",
      "Properties": {
        "taskmanager.numberOfTaskSlots":"4"
      }
    }
]

Should this configuration also have 1 in taskmanager.numberOfTaskSlots?
I am following this AWS Blog post - https://aws.amazon.com/blogs/big-data/create-a-low-latency-source-to-data-lake-pipeline-using-amazon-msk-connect-apache-flink-and-apache-hudi/
Any suggestions to resolution will be very helpful.

I created a new cluster with "taskmanager.numberOfTaskSlots":"1" and in hudi table definition, 'write.tasks' = '1', and it worked.


The noise index

Hi @hhc1997,
I have been working on reproducing the results of MSCN, and I have noticed a discrepancy with your reported results. I am using the noise index provided by DECL. Could you please share the noise indexes you used in your experiments? Additionally, I was wondering if there are any specific training tricks that I might be missing.
Thank you for your assistance.
Best regards!

Hi, @mxchen-mc,
I use the noise index files and code provided by NCR. It seems that the noise index provided by DECL is more challenging. Specifically, DECL randomly selects a given proportion of visual samples and then randomly permutes all their textual counterparts. While in NCR, although one image may have mismatched texts, it is still likely to have some correctly matched texts.


Unity Mixer Plugin import, then compile error with WebSocketSharp

Hey team, I just imported the Mixer SDK from the Unity Asset store today. Right after I imported I attempted to build my project I got this error:
Assets/MixerInteractive/Source/Scripts/InteractivityManager.cs(943,54):
error CS0246:
The type or namespace name `WebSocketSharp' could not be found. Are you missing an assembly reference?

This occurs in a few files; it would appear the WebSocketSharp dependency is missing from the SDK.
I found the WebSocketSharp repo here on GitHub; is this something we need to build ourselves to run the SDK? Is there some dependency-downloading step that I'm missing?

Update: This appears to the place where the dependency issue starts:
https://github.com/mixer/interactive-unity-plugin/blob/master/Source/InteractiveSDK/Assets/MixerInteractive/Source/Scripts/InteractivityManager.cs#L51

What platform were you building for? Or was this the editor?

Sorry for the lack of details! I'm building a project on Unity Mac. Attempting to run what was a previously running game inside the editor displays the compiler.
Also would try to compile within Visual Studio Community on Mac. Same compiler error.

Ah okay. Our MAC SDK developer is on vacation this week so I'll try my best to figure this out.
Based on what I see in the version on GitHub, looks like if you:

Go into Assets\MixerInteractive\Source\DLLs\Win32\websocket-sharp.dll
In the Inspector, check the checkbox for Mac OS X then it'll probably fix the issue.

A small update: I tried the above suggestion, but unfortunately the exact same compilation error occurred. It's almost like it had no effect on Unity, though it did update the .meta file for the dll.
I actually tried manually adding references to the .dll into both of the project .csproj files similar to how other .dll files are referenced and that enabled me to successfully build the project within Visual Studio Mac. Of course, this wasn't the actual solution as it appears Unity auto-generates the .csproj files each time you open the project, and upon auto-gen any references to the websharp .dll were gone. Very strange.

Yea Unity's use of the .csproj isn't like normal.

Any updates? Thanks!

We're going to look at it. In the meantime, this is a workaround:
https://gist.github.com/bargle/4ac1c2f65d201f1734c04177b6b5d3fe

Unfortunately that gist is fixing something related to thread-safety. Alas, the WebSocketSharp compile error is still present.

Ah, sorry wrong issue :)

Not yet. The dev was looking at something else today. I'll let him know.

Any update on how to fix this issue? I'm getting the same compilation error here

@creativedrewy if you're still having this problem what I did to fix it was not just check the checkbox enabling the dll for Mac OSX, but then I also had to change a dropdown from Windows to "Any OS".
That dropdown was on the Editor Settings tab of platform settings.


HBASE-25235 Cleanup the deprecated methods in TimeRange

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
7m 30s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 21s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 38s
master passed

+1 :green_heart:
checkstyle
2m  3s
master passed

+1 :green_heart:
spotbugs
3m 34s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 26s
the patch passed

-0 :warning:
checkstyle
0m 24s
hbase-common: The patch generated 1 new + 2 unchanged - 5 fixed = 3 total (was 7)

+1 :green_heart:
checkstyle
0m 33s
hbase-client: The patch generated 0 new + 201 unchanged - 3 fixed = 201 total (was 204)

+1 :green_heart:
checkstyle
1m  5s
The patch passed checkstyle in hbase-server

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
17m 15s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1 3.3.0.

+1 :green_heart:
spotbugs
4m  7s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 39s
The patch does not generate ASF License warnings.

52m 35s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2616/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2616

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 20c647a7020d 4.15.0-65-generic #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / d790bdedde

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2616/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-common.txt

Max. process+thread count
94 (vs. ulimit of 30000)

modules
C: hbase-common hbase-client hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2616/1/console

versions
git=2.17.1 maven=3.6.3 spotbugs=3.1.12

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 40s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 24s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
5m 26s
master passed

+1 :green_heart:
compile
2m 10s
master passed

+1 :green_heart:
shadedjars
6m 39s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 32s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m  2s
the patch passed

+1 :green_heart:
compile
1m 58s
the patch passed

+1 :green_heart:
javac
1m 58s
the patch passed

+1 :green_heart:
shadedjars
6m 40s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 24s
hbase-common generated 0 new + 15 unchanged - 1 fixed = 15 total (was 16)

+1 :green_heart:
javadoc
0m 26s
hbase-client in the patch passed.

+1 :green_heart:
javadoc
0m 39s
hbase-server in the patch passed.

_ Other Tests _

+1 :green_heart:
unit
1m 43s
hbase-common in the patch passed.

+1 :green_heart:
unit
1m  6s
hbase-client in the patch passed.

-1 :x:
unit
131m  8s
hbase-server in the patch failed.

167m 57s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2616/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2616

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 7a0d93b68d35 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / d790bdedde

Default Java
AdoptOpenJDK-11.0.6+10

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2616/1/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2616/1/testReport/

Max. process+thread count
4217 (vs. ulimit of 30000)

modules
C: hbase-common hbase-client hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2616/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  7s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 21s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m  2s
master passed

+1 :green_heart:
compile
1m 46s
master passed

+1 :green_heart:
shadedjars
7m  7s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 19s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 52s
the patch passed

+1 :green_heart:
compile
1m 50s
the patch passed

+1 :green_heart:
javac
1m 50s
the patch passed

+1 :green_heart:
shadedjars
7m  8s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 17s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 34s
hbase-common in the patch passed.

+1 :green_heart:
unit
1m  6s
hbase-client in the patch passed.

-1 :x:
unit
204m 17s
hbase-server in the patch failed.

239m 14s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2616/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2616

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 557ce92be192 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / d790bdedde

Default Java
AdoptOpenJDK-1.8.0_232-b09

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2616/1/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2616/1/testReport/

Max. process+thread count
3338 (vs. ulimit of 30000)

modules
C: hbase-common hbase-client hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2616/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  6s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 22s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 43s
master passed

+1 :green_heart:
checkstyle
2m  0s
master passed

+1 :green_heart:
spotbugs
3m 34s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 22s
the patch passed

+1 :green_heart:
checkstyle
0m 24s
hbase-common: The patch generated 0 new + 2 unchanged - 5 fixed = 2 total (was 7)

+1 :green_heart:
checkstyle
0m 31s
hbase-client: The patch generated 0 new + 201 unchanged - 3 fixed = 201 total (was 204)

+1 :green_heart:
checkstyle
1m  5s
The patch passed checkstyle in hbase-server

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
16m 57s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1 3.3.0.

+1 :green_heart:
spotbugs
4m  5s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 38s
The patch does not generate ASF License warnings.

45m 55s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2616/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2616

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 83ee0053f6be 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 7a41247ef7

Max. process+thread count
94 (vs. ulimit of 30000)

modules
C: hbase-common hbase-client hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2616/2/console

versions
git=2.17.1 maven=3.6.3 spotbugs=3.1.12

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 43s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 24s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
5m 32s
master passed

+1 :green_heart:
compile
2m 28s
master passed

+1 :green_heart:
shadedjars
8m 30s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 51s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
5m  9s
the patch passed

+1 :green_heart:
compile
2m 15s
the patch passed

+1 :green_heart:
javac
2m 15s
the patch passed

+1 :green_heart:
shadedjars
7m 58s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 29s
hbase-common generated 0 new + 15 unchanged - 1 fixed = 15 total (was 16)

+1 :green_heart:
javadoc
0m 30s
hbase-client in the patch passed.

+1 :green_heart:
javadoc
0m 50s
hbase-server in the patch passed.

_ Other Tests _

+1 :green_heart:
unit
1m 57s
hbase-common in the patch passed.

+1 :green_heart:
unit
1m 20s
hbase-client in the patch passed.

+1 :green_heart:
unit
137m 17s
hbase-server in the patch passed.

180m 22s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2616/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2616

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 3f4cf9b2939a 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 7a41247ef7

Default Java
AdoptOpenJDK-11.0.6+10

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2616/2/testReport/

Max. process+thread count
3813 (vs. ulimit of 30000)

modules
C: hbase-common hbase-client hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2616/2/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
9m 41s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 21s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m  2s
master passed

+1 :green_heart:
compile
1m 48s
master passed

+1 :green_heart:
shadedjars
7m 11s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 19s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 49s
the patch passed

+1 :green_heart:
compile
1m 45s
the patch passed

+1 :green_heart:
javac
1m 45s
the patch passed

+1 :green_heart:
shadedjars
7m  4s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m 17s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 35s
hbase-common in the patch passed.

+1 :green_heart:
unit
1m  6s
hbase-client in the patch passed.

-1 :x:
unit
205m 27s
hbase-server in the patch failed.

248m 54s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2616/2/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2616

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux e45e83b98fb7 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 7a41247ef7

Default Java
AdoptOpenJDK-1.8.0_232-b09

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2616/2/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2616/2/testReport/

Max. process+thread count
3549 (vs. ulimit of 30000)

modules
C: hbase-common hbase-client hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2616/2/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Investigate/improve overworld performance

The overworld sometimes seems 'stuttery'. It would be nice to fix this, or to investigate potential upcoming performance issues when we have more large textures or more sprites.

What if we have 500 restaurant-sized textures?
What if we have 500 sprites on the overworld?
Does it make sense to have logic for 'partially preloading' resources with our ResourceCache? Possibly a blacklist (don't load these sprites) or whitelist (only load creature sprites)?
Is it faster if the sprites share a shader?
Is it faster if the sprites don't have a shader?
Is it smoother if we get rid of the custom goop shader/goop viewport? (We don't want to get rid of it -- but this would be a starting point for investigating why it makes things jittery)

This is already notable on my android phone, where the overworld appears to stutter by at about 15 FPS.

This is already notable on my android phone, where the overworld appears to stutter by at about 15 FPS.

I investigated many potential performance bottlenecks, and here's what I found.
The outdoor overworld viewports which facilitate the goop shader impact FPS by 33% on my desktop PC.
The outline shader on Creatures impacts FPS by 18% on my desktop PC.
The creature viewport which merges all all the creature sprites into a single panel impacts FPS by 71% on my desktop PC.
The creature viewports which render the creature's body and overlay shadows and belly patterns impact FPS by 600% on my desktop PC.
The PackedSprite drawing and processing does not impact FPS.
The trees, bushes, restaurant, exit and crystal on the overworld do not impact FPS.
The RGB shader for recoloring creatures does not impact FPS.
Adding 24 unnecessary nodes to each creature does not degrade FPS. Godot can handle 1,000+ extra nodes without any problem.
Running a profiler, the Creature._physics_process function takes a significant amount of time when there are 50 creatures. This could be optimized (especially for immobile creatures) although it does not affect FPS.
Based on the result of these stress tests, the way to improve game performance is to minimize use of viewports. Our overworld scene currently has about 50 viewports. Ideally it should have 0.

-create a creature which uses a conventional sprite sheet for their torso
-create a very rough prototype (just a screenshot or a flat garbage sprite is fine)
-stress test this creature variant to ensure the performance gains are there
-make it look good
 -create 'screenshot' of neutral arms + legs pose
 -create 'screenshot' of facing away arms + legs pose
 -walking animations
 -pointing animation
 -waving animations
-stress test this creature variant again to ensure the performance gains remain

-create a creature which uses a conventional sprite sheet for their head
-create a very rough prototype (just a screenshot or a flat garbage sprite is fine)
-stress test this creature variant to ensure the performance gains are there
-make it look good
 -create 'screenshot' of facing forward
 -create 'screenshot' of facing away
 -blinking animation
 -eating animation
 -idle animations
 -emotes
-stress test this creature variant again to ensure the performance gains remain

https://godotengine.org/qa/62220/make-image-background-transparent
https://github.com/godotengine/godot/issues/32894 (make sure Viewport usage is 2D?)

This story by its current definition is an epic, which could encompass all sorts of work. I'm going to rescope it to simply "Investigate overworld performance" and create new stories for specific improvement tasks.


which jailbreak bypasss detection tweak?

Hello Dears, thank you for this amazing jailbreak utility, its indeed much better than serotonin!
So far I tried, shadow, choicy and vnodebypass all failed to bypass the detection on the following apps, NBK mobile app, Kuwait mobile ID, Weyay Bank app. they are very tricky and checking almost everything when it comes to jailbreak detection.
I think these tweaks are not supported by nathanlr jailbreak, and I did try to hide jailbreak via the settings of Nathanlr. that did work on some apps but not on these apps I mentioned.
Any guidance would be appreciated!

I'm having the same issue, although can choose the Toggle JB hide, but all the deb not worked at all apps