faq建设

FailbackClusterInvoker类错误码改造。
What is the purpose of the change
Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #10536 (517a79e) into 3.1 (bb7f942) will decrease coverage by 0.24%.
The diff coverage is 83.33%.

@@             Coverage Diff              @@
##                3.1   #10536      +/-   ##
============================================
- Coverage     64.74%   64.50%   -0.25%
- Complexity      373      394      +21
============================================
  Files          1331     1331
  Lines         56509    56509
  Branches       8369     8370       +1
============================================
- Hits          36587    36451     -136
- Misses        15978    16096     +118
- Partials       3944     3962      +18

Impacted Files
Coverage Δ

...bo/rpc/cluster/support/FailbackClusterInvoker.java
78.46% <83.33%> (ø)

...mmon/serialize/fastjson2/FastJson2ObjectInput.java
0.00% <0.00%> (-62.50%)
:arrow_down:

...mon/serialize/fastjson2/FastJson2ObjectOutput.java
0.00% <0.00%> (-56.25%)
:arrow_down:

...on/serialize/fastjson2/FastJson2Serialization.java
57.14% <0.00%> (-28.58%)
:arrow_down:

...nt/metadata/ServiceInstanceHostPortCustomizer.java
65.78% <0.00%> (-21.06%)
:arrow_down:

...n/serialize/fastjson2/Fastjson2CreatorManager.java
46.66% <0.00%> (-20.00%)
:arrow_down:

...e/dubbo/rpc/protocol/tri/transport/WriteQueue.java
64.28% <0.00%> (-14.29%)
:arrow_down:

...che/dubbo/registry/client/NopServiceDiscovery.java
44.44% <0.00%> (-11.12%)
:arrow_down:

...va/org/apache/dubbo/remoting/TimeoutException.java
22.22% <0.00%> (-11.12%)
:arrow_down:

...erialize/support/DefaultSerializationSelector.java
50.00% <0.00%> (-10.00%)
:arrow_down:

... and 34 more

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


Enable replaceWhere when DPO (dynamic partition overwrite) is enabled in the Spark configuration

Description
This PR changes how replaceWhere and DPO interact with each other.
Current behavior:

DPO + replaceWhere always throws an error

Behavior in this PR:

DPO in spark session configuration + replaceWhere = data overwritten according to replaceWhere
DPO as DataFrameWriter option + replaceWhere = throw error

Testing
Updates and adds a test to DeltaSuite.

hey @koertkuipers I opened this PR to implement the behavior we discussed on #371 if you want to take a look

hey @koertkuipers I opened this PR to implement the behavior we discussed on #371 if you want to take a look

looks great.
maybe also update the class scaladoc for WriteIntoDelta?
i dont think replaceWhere can be uses for SQL INSERT OVERWRITE right? so no additional tests needed for this?

@koertkuipers yep, just for dataframe writes. I'll update the class doc thanks!


pending GAS transaction for > 3 days

I sent 4.64224 GAS, on 2018-03-29 | 18:23:56, from Binance to Kucoin at AceWB7eDJsDZiJ99cUx6xbE341B9hs1v8s and it still has only 4 confirmations from 6 minimum required. Txid:89b27789d08720386e738d3661d022e52826aa0097c9add798c0516981fdb328
https://neoscan.io/transaction/89b27789d08720386e738d3661d022e52826aa0097c9add798c0516981fdb328

actually more than 4 days

The transaction is there. This has nothing to do with the block explorer.

yes...  :|  thnx


Release Google.Cloud.BigQuery.DataPolicies.V1 version 1.5.0

Changes in this release:
New features

Add IServiceCollection extension methods for client registration where an IServiceProvider is required. (commit 022fab2)

Created release for Google.Cloud.BigQuery.DataPolicies.V1-1.5.0


When possible, guess the content-type of the file being sent

Refined PR #285 by rasky to pass all tests
A possible solution to "Content Type of file uploaded in multipart/form-data request" #271 when using the form mode.

Merged, thanks!


Fixes for AmgX solver class memory leaks

Partial fixes for issue https://github.com/mfem/mfem/issues/2027 .
Still does not fix the problem, but plugs a leak in the the AmgX solver class

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#2047
@artv3
@tzanio
@tzanio + @barker29
02/12/21
⌛due 02/26/21
⌛due 03/05/21

Hi @artv3 I have just run my problem based on this branch but it also returns the issue similar.

Hi @artv3 I have just run my problem based on this branch but it also returns the issue similar.

Hi @nghiakvnvsd , would you be able to provide more of the valgrind ouput? It might also help to build both mfem + hypre in debug mode to get line numbers. Generating the valgrind info may take while but would be super useful.
The memory leak addressed here is the only one I've been able to track down.
One other thing to try in your code is instead of using
   OperatorPtr K;
On line 167 is to use HypreParMatrix K. I'm not sure if new is being used on line 182 when doing     amgx.SetOperator(*K.As<HypreParMatrix>());
@tzanio , @barker29 what do you guys think? I think there is a memory leak somewhere but I'm not sure where.

Proferssor @nghiakvnvsd can you try the latest branch again? I just pushed some adjustments, I had the free in the the wrong place....
I was able to replicate the error on my end, and with the latest push I don't seem to run out of memory anymore.
Thanks for checking out our work! Definitely has helped make it more robust!

Professor @nghiakvnvsd can you try the latest branch again? I just pushed some adjustments, I had the free in the wrong place....
I was able to replicate the error on my end, and with the latest push I don't seem to run out of memory anymore.
Thanks for checking out our work! Definitely has helped make it more robust!

It worked for me. Thank you very much for your help!!!

Professor @nghiakvnvsd can you try the latest branch again? I just pushed some adjustments, I had the free in the wrong place....
I was able to replicate the error on my end, and with the latest push I don't seem to run out of memory anymore.
Thanks for checking out our work! Definitely has helped make it more robust!

It worked for me. Thank you very much for your help!!!

Wonderful! If the code in this PR looks good, could I get an approval?

Merged in next for testing...


updated Mathscape Master

updated Mathscape Master and #3992

Close #3992

Checklist:

[x] I have mentioned the issue number in my Pull Request.
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md

@MohitGupta121 sir kindly review and merge this PR


Cannot read property 'init' of undefined

Hello.
I am getting the error 'Cannot read property 'init' of undefined' when running the app.

@alihaddadkar it means — you didn't install correctly tipsi-twitter.
Check linking, check pods.
Until tipsi-twitter is undefined — you didn't get job done


[Bug]: Puppeteer keeps crashing

Bug description
Steps to reproduce the problem:

Run npm install
Run npm start
Only occurs on my mac book, but not on my other computer

Puppeteer version
17.1.3
Node.js version
16.0.0
npm version
7.10.0
What operating system are you seeing the problem on?
macOS
Relevant log output
/path/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:285
            return Promise.reject(new Error(`Protocol error (${method}): Session closed. Most likely the ${__classPrivateFieldGet(this, _CDPSession_targetType, "f")} has been closed.`));
                                  ^

Error: Protocol error (Target.activateTarget): Session closed. Most likely the page has been closed.
    at CDPSession.send (/path/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:285:35)
    at next (/path/node_modules/puppeteer-extra-plugin-stealth/evasions/sourceurl/index.js:34:41)
    at CDPSession.send (/path/node_modules/puppeteer-extra-plugin-stealth/evasions/sourceurl/index.js:67:18)
    at Page._Page_screenshotTask (/path/node_modules/puppeteer/lib/cjs/puppeteer/common/Page.js:2634:59)
    at /path/node_modules/puppeteer/lib/cjs/puppeteer/common/Page.js:2006:93

Is you macbook using M1 (or arm64) processor?

Any update with this bug ?

@sahdbashkdbj I am not sure it's the bug, very likely the binary is for the wrong platform architecture. Waiting for the reporter to provide the details about their macbook and a repro.

I'm experiencing this same issue on a google cloud run instance.

Hi, I'm experiencing this same issue on MacBook Air M2

@d3ric3
Did you find something for it? Any work around, I'm facing the same issue on my mac m2

@Abhishek-Nebel updating the puppeteer npm package to version 22.5.0 help to reduce the crash issue on my M2. I notice there is a latest version 22.12.1. You may try switching between the puppeteer npm package version. At the moment I am only using my program at Windows 11 and Ubuntu, working fine at these OS.


Mob pathing seems to be causing lag now

Description
Apparently the server gets alot of lag whenever there are alot of killer tomatos about. I think something may be broken with mob pathing as the server noticeably slows down whenever they start pathing.
Reproduction
spawn alot of killer tomatos
watch lag happen as they path

do you have a profile

sorry i dont know what a profile means

apparently shadowcommander was notified of this by an admin in VC the other day and they may have more info about this

I'm gonna take this with a heap of salt without some level of proof.

Ill try to get a recording of it. Ive personally seen it happen twice so far and people in the round have also been affected by the lag. Only thing i can think of causing it would be the 50+ kliller tomatos since the lag noticabally stoped as soon as they were killed.

Is getting 50 killer tomatos a regular occurrence because 50 of them pathing isn't going to be fast and they should be removed or nerfed if that's the case.

Its been happening quite often over the past few days on the times ive been on. Id say in the past 20 rounds ive seen 50+ tomatos in about 5 of them

this issue seemed to be caused by the massive (50++) amounts of killer tomatos. It seems to be resolved.


Example grammar for xsd regex fails to match quantifiers

This is an issue in the example grammar xsd-regex (https://github.com/antlr/grammars-v4/tree/master/xsd-regex).
Curly braces, when following an atom, should be matched as a quantifier, but instead they are matched as atoms.
E.g. x{0} parses as 4 atoms, but should parse as one atom with a quantifier.
This can be seen when attempting to use the 'quantifier' rule to parse {0} in the antlr lab. The console message returned is
1:0 mismatched input '{' expecting {'+', '?', '*', '{'}
I believe the problem is that the curly brace characters are not listed in Char rule in the lexer grammar:
Char : ~('.' | '\\' | '?' | '*' | '+' | '(' | ')' | '|' | '[' | ']')
Adding these appears to resolve the issue:
Char : ~('.' | '\\' | '?' | '*' | '+' | '(' | ')' | '|' | '[' | ']' | '{' | '}')

This sounds like a problem with the grammar. You should re-create the issue in grammars-v4 and close this issue out. The grammars are completely separate from the parser generator and http://lab.antlr.org/.

Thanks Ken, apologies for posting to the wrong repo. Closing.


Style fixes for RegExp engine.

JerryScript-DCO-1.0-Signed-off-by: László Langó<EMAIL_ADDRESS>

@ruben-ayrapetyan, I've updated the PR, please check.

@ruben-ayrapetyan, I've updated the PR, please check.

Looks good to me

Looks good to me.

@galpeter, updeted, please check

lgtm


Enhancements: Refactor cache_instances under GQL module for better Debugging

TLDR: Improper repr of classes present under  backend/dataall/base/api/gql
repr of the classes present under backend/dataall/base/api/gql
points to the cache_instance function present under backend/dataall/base/api/gql/_cache.py.
due to this one cannot navigate to the proper function or class while navigating through the stack frames.

Creating new class named CacheInstances which implements the new dunder method provided by python for instance creation.
CacheInstances is inherited by the classes such as ObjectType, QueryField, MutationField, Enum, Union, InputType.
`
class CacheInstances:
class_instances = {}
  def __new__(cls, name, scope='default', *args, **kwargs):
      obj = super().__new__(cls)
      if scope not in cls.class_instances:
          cls.class_instances[scope] = {}
      cls.class_instances[scope][name] = obj
      return obj

  @classmethod
  def get_instance(cls, name, scope='default'):
      try:
          return cls.class_instances[scope].get(name, None)
      except KeyError as e:
          print(f'scope: {scope} not found in class instances')
          raise e

`
`class GraphqlEnum(CacheInstances):
def __init__(self, name, values = None):
    self.name = name
    self.values = values

def gql(self, with_directives=True):
    n = '\n'
    # return f"enum {self.name}{{{n}{n.join(self.values)}{n}}}"
    return f'enum {self.name}{{{n}{n.join([v.name for v in self.values])}{n}}}'

`
P.S. Don't attach files. Please, prefer add code snippets directly in the message body.

Hi @anilsoni7, I have noticed that issue too and thanks for reporting it.
We are currently exploring (see #958) a migration from ApiGateway to AppSync and in that case all of the custom gql logic will be removed (aka all the code under gql/ and the definition of the types). So maybe the best approach here is to wait a bit for a decision on the AppSync migration and act a bit later.

@petrkalos should we revisit this issue as candidate for 2.7?

@dlpzx yes I think so


A solution to prevent zombie containers locally and in CI

Description
This PR adds mechanisms on the build scripts to cleanup docker containers when there is a cancellation, either from the user by sending SIGINT / SIGTERM or when the process inside the container ends with an error.
It also propagates the environment variables from Jenkins which are used by the process tree killer to identify runaway processes so processes inside the container are killed when the Jenkins job is stopped.
With this patch we catch SIGINT and SIGTERM and install a handler on atexit which cleans (stops) docker containers which were created during execution of the build.
We also switch to python docker API for better management of running containers.
@aaronmarkham @marcoabreu @lebeg @KellenSunderland
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

LGTM, let's get the host AMIs changed.

I was hoping to see some usage info. 1) how to make a zombie; 2) how to kill it - I'd be happy to test this out.

I added info in the readme. Do you see it in the patch?

Done. I don't know why the PR is not updated.

any ideas? is a github problem?

I can't reopen the PR, had some troubles with PR not updating and Jenkins, new pR:
https://github.com/apache/incubator-mxnet/pull/12381

Github is having issues today.  https://status.github.com/messages


Not wanting the rank column to be sorted

Hi,
The first column of my tables is the rank column, which should always be 1,2,3,4,5,6,... event when I sort the other columns.  How could I have this column fixed so it stays like this after sorting with other columns ?
Thank you
Pat

we dont support this kind of feature, but how about implement a custom sort function via
sortFunc
you can check this to see how to custom sort function.
or another advance solution is maybe you can use remote mode and handle the sorting on your application instead of in the react-bootstrap-table, thus, you can control the data.
remote mode is a feature to let you to do the data change(sort, filter, paging, search etc) on your application.
check this to learn how to use remote mode https://github.com/AllenFang/react-bootstrap-table/blob/master/examples/js/remote/remote-store-sorting.js
BTW, you can only assign the sorting to use remote mode.
let me know if you have any question.


Sync Stage with Main

We've had a few hotfixes and reverts happening in PROD due to last-minute changing requirements. This will get our stage in sync with main.
Test URLs:

Before: https://stage--express--adobecom.hlx.page/express/pricing?lighthouse=on
After: https://main--express--adobecom.hlx.page/express/pricing?lighthouse=on

We need to clear stage asap before staging the floatingCTA updates. So I might merge it without having enough approvals. This is also low risk


Modal does not recognise dark: prefix, dismissible prop is unknown

Describe the bug
Hi Team,
First of all, I'm really enjoying this fantastic library, so thank you for your hard work.
The only bug I'm experiencing is that Modal does not recognise dark mode unlike the other flowbite components.
It does not recognise dark: prefix in className prop either.
Also, dismissible prop does not accept a boolean.
To Reproduce
Steps to reproduce the behavior:

Clone repo

git clone git@github.com:ksi9302/fb-modal-bug.git

toggle dark className from App.tsx

uncomment dismissible prop

Expected behavior
Dark mode works, dismissible prop recognised
Screenshots

System information:

Device: PC Desktop
Resolution: 2K
OS: Windows 11
Browser: Chrome
Version: 109.0.5414.75 (Official Build) (64-bit)

Project information:

Tailwind: 3.2.4
Flowbite: 18.0.27
Flowbite React: 0.3.7
Type: Vite /CRA

"devDependencies": {
"@types/react": "^18.0.26",
"@types/react-dom": "^18.0.9",
"@vitejs/plugin-react": "^3.0.0",
"tailwindcss": "^3.2.4",
"typescript": "^4.9.3",
"vite": "^4.0.0"
}
Additional context
My project uses vite, but the example app is created with CRA, the behaviour is alike.

For anyone looking for a workaround for the darkMode issue, you can dynamically pass the scheme to the className.
<Modal         className={scheme === "dark" ? "dark" : ""} ...       >

It isn't a bug. You need to wrap your application up with the <Flowbite></Flowbite> component to use the theme system, which will apply the dark/light mode.
https://flowbite-react.com/theme

Thanks for the clarification @rluders, since other components received dark class, I thought the Modal would do the same.
Is dismissible prop not working a bug still?

@ksi9302 also, not a bug. You are probably looking at main code and using 0.3.7 version.
0.3.7 doesn't support dismissible, this feature will be released by the end of this month.
https://github.com/themesberg/flowbite-react/blob/v0.3.7/src/lib/components/Modal/Modal.tsx#L48

@ksi9302 Check the last release 0.3.8


rollout docs

Ⅰ. Describe what this PR does

Introduction
installation
basic usage

/lgtm

/approve

/lgtm


Add overload support by mangling method names

Refit now support method overloading.
The methods dictionary is built using mangled method name instead of using the method name only.
I'm not quite sure about the Mangle method position (currently in RequestBuilder type).
Closes #82.

@nekresh What is the state of this merge?

I think this PR looks fine.

@nekresh can you please rebase this on master?


proposal: reflect: add NewAtPtr, ValueAt

The function reflect.NewAt works very slowly. Because it calls ptrTo to convert type to a pointer type, ptrTo uses sync.Map internally to find a pointer type data. There is no way to pre-create a pointer type and reuse it. Also some cases needs to create a value directly at pointer. The following functions solve this problem.
// NewAtPtr returns a Value representing a pointer to a value of the
// specified pointer type, using p as that pointer.
func NewAtPtr(typ Type, p unsafe.Pointer) Value {
	if typ == nil {
		panic("reflect: NewAtPtr(nil)")
	}
	fl := flag(Ptr)
	t := typ.(*rtype)
	if t.Kind() != Ptr {
		panic("non-pointer type")
	}
	return Value{t, p, fl}
}

// At returns a Value representing a value of the
// specified type, using p as that pointer.
func ValueAt(typ Type, p unsafe.Pointer) Value {
	if typ == nil {
		panic("reflect: At(nil)")
	}
	if p == nil {
		return Value{}
	}
	t := typ.(*rtype)
	fl := flagIndir | flagAddr
	fl |= flag(t.Kind())
	return Value{t, p, fl}
}

Code: https://github.com/yazver/go/blob/reflect-newatptr/src/reflect/value.go#L2406-L2433
Tests: https://github.com/yazver/go/blob/reflect-newatptr/src/reflect/all_test.go#L7358-L7393.
Benchmark tests for two cases:

Create indirect Value from unsafe.Pointer (ValueAt 10 times faster then NewAt);
Create Value of a pointer to Value from unsafe.Pointer (NewAtPtr 10 times faster then NewAt);

Running tool: go test -benchmem -run=^$ github.com/yazver/go-test/reflect -bench ^(BenchmarkNewAt|BenchmarkNewAtPtr|BenchmarkValueAt|BenchmarkNewAtAddr|BenchmarkNewAtPtrAddr|BenchmarkValueAtAddr)$

goos: darwin
goarch: amd64
pkg: github.com/yazver/go-test/reflect
BenchmarkNewAt-12           	124112732	         9.98 ns/op	       0 B/op	       0 allocs/op
BenchmarkNewAtPtr-12        	321658622	         3.48 ns/op	       0 B/op	       0 allocs/op
BenchmarkValueAt-12<PHONE_NUMBER>	         0.759 ns/op	       0 B/op	       0 allocs/op
BenchmarkNewAtAddr-12       	178886904	         6.83 ns/op	       0 B/op	       0 allocs/op
BenchmarkNewAtPtrAddr-12<PHONE_NUMBER>	         0.698 ns/op	       0 B/op	       0 allocs/op
BenchmarkValueAtAddr-12     	128124268	         9.77 ns/op	       0 B/op	       0 allocs/op
PASS
ok  	github.com/yazver/go-test/reflect	9.813s

Sources of tests:
func BenchmarkNewAt(b *testing.B) {
	v := reflect.ValueOf(new(int))
	t := v.Type().Elem()
	ptr := unsafe.Pointer(v.Pointer())
	for i := 0; i < b.N; i++ {
		_ = reflect.NewAt(t, ptr).Elem()
	}
}

func BenchmarkNewAtPtr(b *testing.B) {
	v := reflect.ValueOf(new(int))
	t := v.Type()
	ptr := unsafe.Pointer(v.Pointer())
	for i := 0; i < b.N; i++ {
		_ = reflect.NewAtPtr(t, ptr).Elem()
	}
}

func BenchmarkValueAt(b *testing.B) {
	v := reflect.ValueOf(new(int))
	t := v.Type().Elem()
	ptr := unsafe.Pointer(v.Pointer())
	for i := 0; i < b.N; i++ {
		_ = reflect.ValueAt(t, ptr)
	}
}

func BenchmarkNewAtAddr(b *testing.B) {
	v := reflect.ValueOf(new(int))
	t := v.Type().Elem()
	ptr := unsafe.Pointer(v.Pointer())
	for i := 0; i < b.N; i++ {
		_ = reflect.NewAt(t, ptr)
	}
}

func BenchmarkNewAtPtrAddr(b *testing.B) {
	v := reflect.ValueOf(new(int))
	t := v.Type()
	ptr := unsafe.Pointer(v.Pointer())
	for i := 0; i < b.N; i++ {
		_ = reflect.NewAtPtr(t, ptr)
	}
}

func BenchmarkValueAtAddr(b *testing.B) {
	v := reflect.ValueOf(new(int))
	ptr := unsafe.Pointer(v.Pointer())
	t := v.Type().Elem()
	for i := 0; i < b.N; i++ {
		_ = reflect.ValueAt(t, ptr).Addr()
	}
}

the double loop in the benchmark looks weird, also it violates the pointer safety rules

the double loop in the benchmark looks weird, also it violates the pointer safety rules

Accepted it and fixed.

What kind of code would use these new functions?

What kind of code would use these new functions?
For example It allows more fast access to the struct fields by pre-cached offsets.

src := reflect.ValueAt(srcFieldType, unsafe.Pointer(uintptr(srcPtr)+srcOffset))
dest := reflect.ValueAt(destFieldType, unsafe.Pointer(uintptr(destPtr)+destOffset))
dest.Set(src)

Have you attempted to make the current APIs faster?
Also, if you find reflect to be too slow for your use case in general, you could always give up safety and use more unsafe directly instead of reflect. You appear to be using unsafe pointer arithmetic already.

Have you attempted to make the current APIs faster?

I don't see way to do it. NewAt uses ptrTo and it is very heavy internally.

Also, if you find reflect to be too slow for your use case in general, you could always give up some safety and use more unsafe directly instead of reflect. You appear to be using unsafe pointer arithmetic already.

Go does't have a function that allows to copy arbitrary count of bytes. If some memory copy function were there, it would most likely solve the problem. And one way, that i know, to copy the variable of unknown type is to use Set(), that is required the indirect Value and which can only be obtained in the following way: reflect.NewAt(typ, ptr).Elem().

With the copy function and a few unsafe casts to array of byte, you can actually copy an arbitrary amount of bytes.

The only difference between this API and the existing API is which type gets passed in.
NewAt(typ, p) == NewAtPtr(PtrTo(typ), p).
And the issue is that PtrTo sometimes requires a map lookup.
But that map lookup is only needed for types that are not themselves already in the binary.
If type T gets reflect information in the binary, then we also write out *T in the binary.
You'd only see this if you constructed T itself at runtime, or if you were using **T or something like that.
What is the context in which this occurs?
If T is constructed at runtime, the data is writable, so we could fill in the *T link once and reuse it instead of using the map.
(That's not true for a *T built into the binary - there we can't write the link to **T.)
So it seems like in whatever important case we have, we could make PtrTo faster instead of adding new API here.
But would that address the case where you are seeing this?
(That is, again, what is the context in which this occurs?)

I was curious how hard this would be, so I wrote https://golang.org/cl/254237 to record pointer types in the ptrToThis field of newly created dynamic types.  It would be interesting to know what effect this has on the benchmarks here.

Actually that code is slower.  Never mind.

Maybe we should re-expand ptrToThis to be a full pointer. I don't know how much this specific field would expand the reflect data.
But the more important question is again, what is the context in which this slow execution occurs? /cc @yazver

Does anyone want to describe a time when the speed of NewAt was too slow?
We think we know how to make it faster but it would be nice to understand what we would be making faster, if anything, to justify the added complexity and slight size overhead.

We think we know how to optimize NewAt if it is too slow. But we need to see a use case to understand the tradeoff there.
On the new API topic (this issue), based on the discussion above this seems like a likely decline.

No change in consensus, so declined.


[GOBBLIN-510] Decouple JobExecutionLauncher and JobExecutionDriver

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-510] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-510

Description

[x] Here are some details about my PR, including screenshots (if applicable):
Today JobExecutionLauncher and JobExecutionDriver is coupled. It means when JobExecutionLauncher invokes launchJob, a JobExecutionDriver is immediately return. This is not good for gobblin cluster because the Launcher might running in manager node but the actual driver logic is running on worker node. We need some refactoring to allow us decouple these two.

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

@htran1 Please review?


chore: replace headers class

Purpose
Replace the header class for something that follows the spec a little more correctly
Changes
getAll() & raw() and all of the URLSearchParams methods are removed
Additional information

ideally i would like to remove some more own test in node-fetch as the fetch-headers package has it's own test that are run against WPT - but i tough of keeping them for now just to make sure things still works.
https://github.com/node-fetch/node-fetch/issues/1119#issuecomment-100222049
also... this will sort of revert #672
(content-encoding should be case case insensitive and not normalized - so this is now being done in the fetch method now instead)

[x] I updated & removed some unit test(s)

fix #1119

jimmywarting:replace-headers-class


Add CHANGELOG

I'd be great to add CHANGELOG just like network role does in https://github.com/linux-system-roles/network/blob/main/CHANGELOG.md
This will require doing releases to be able to gather several changes into one batch.

Fixed by #73


SanJose_PastPerfectMapper(PastPerfectXMLMapper)

Mapper dependency: #369

Some general links to know:

Development contribution process
"CIC all tasks" list view
"CIC current sprint" status view

Specific to this mapper:

List of collections, by mapper type: https://registry.cdlib.org/?mapper_type=sanjose_pastperfect
Endpoints:

https://s3.amazonaws.com/pastperfectonline/xmlfiles/museum_112/inmemrecs.xml

Rikolti MVP project board cheat sheet:

Please @ CDL developers liberally, in the comments.
When picking up an "issue," please indicate:

a) Assignees: self assign;
b) Sprint: select the current sprint cycle;
c) Date started: indicate the start date -- see right side fields

CIC developers will likely need to create PRs (and possibly additional issues). When doing so, please also indicate the following:

a) Repository: Rikolti;
b) Milestone: "4 CIC work" (these details are required in order for them to surface in the Rikolti MVP project board); and
c) link the PR to the associated issue.

When requesting review, please:

a) include a comment & @ CDL developers; and
b) Date delivered: indicate the date delivered (field on the right)

History San Jose is switching to the cloud based PastPerfect Web Edition (from desktop). Hold on this until their migration is complete.


Allow ability to do an in-place override (not extend) of interface properties

Search Terms

override interface
override interface replace
Suggestion

It would be nice to be able to override (not extend) third party libraries' interfaces to change the types/signatures of the interface properties.
Use Cases

Sometimes they make mistakes or define interfaces in ways that force me to constantly use as to typecast. I'd rather short-circuit it in one place so it works across my project.
Examples

Reference: https://stackoverflow.com/questions/51562792/how-to-override-a-typescript-interface-without-extending
Checklist
My suggestion meets these guidelines:
(Honestly I'm in no position to make these judgment calls, as I don't know the inner workings of this library - why ask these quesitons?)

[X] This wouldn't be a breaking change in existing TypeScript / JavaScript code
[X] This wouldn't change the runtime behavior of existing JavaScript code
[ ] This could be implemented without emitting different JS based on the types of the expressions (not sure what this means)
[ ] This isn't a runtime feature (e.g. new expression-level syntax) (???)

I think a core problem here is: in the case of multiple overrides of the same property, how would the type-checker decide which override takes precedence?


Fix anchor.js

It doesn't work when you have the address with nativeCol = 0

Col and row are always >= 1
But rigth, that's good pull request

@wwojtkowski could i please you for write a test that's failed this code before changes?

Col and row are always >= 1
But rigth, that's good pull request

I cannot agree with you. Rows are always >= 1 but not col.
I have Excel's file where I have images in the first column in every row.
In the Anchor class nativeCol has 0 value but nativeRow has proper value (>=1).
Before my fix, all images from worksheet have nativeRow = 0 and nativeCol = 0 - which is a very serious bug.

@wwojtkowski ok, thanks for the explanation :)
I want to merge it, but it's required to cover changes by tests

@Siemienik , I have error with the word 'anchor' when call openFile, may it be the same problem? :)
TypeError: Cannot read property 'anchors' of undefined
    at DrawingXform.reconcile (C:\web\my_prj\node_modules\exceljs\lib\xlsx\xform\drawing\drawing-xform.js:94:11)
    at Object.keys.forEach.name (C:\web\my_prj\node_modules\exceljs\lib\xlsx\xlsx.js:103:22)
    at Array.forEach (<anonymous>)
    at XLSX.reconcile (C:\web\my_prj\node_modules\exceljs\lib\xlsx\xlsx.js:95:33)
    at PromiseLib.Promise.all.then (C:\web\my_prj\node_modules\exceljs\lib\xlsx\xlsx.js:389:16)

But it appears in the ONLY Excel file that is important for my task!
And there are some interesting things I found:

If I copy all worksheet and paste to new workbook, it works.
If I run in Excel "check compatibility" function and do correct operation - it works!


feat(pagination): move configuration settings to separate file

Current coverage is 85.62% (diff: 100%)

Merging #1212 into development will not change coverage

@@           development      #1212   diff @@
=============================================
  Files               35         35
  Lines             1280       1280
  Methods            228        228
  Messages             0          0
  Branches           213        213
=============================================
  Hits              1096       1096
  Misses             184        184
  Partials             0          0

Powered by Codecov. Last update 7b0d98a...12185d1


Automatic Type Acquisition does not work

VSCode Version: 1.43.2
OS Version: macOS Catalina 10.15.4 (19E266)

Steps to Reproduce:
$ mkdir test-jest-types
$ cd test-jest-types
$ npm init -y
$ npm i --save-dev jest
$ echo "describe('xxx')" > index.test.js
$ code --disable-extensions .

Now open the index.test.js file in VSCode, see there is TS error because jest type acquisition did not work and describe is missing type annotation.

Does this issue occur when all extensions are disabled?: Yes
I would like if the ATA work without the need for workarounds such as:

Creating a jsconfig.json or tsconfig.json with explicitly saying i want jest type definitions
Installing npm i --save-dev @types/jest as a dependency of the project
Installing the types globally npm i -g @types/jest

There are no import of jest in your file - therefore nothing will trigger ATA.
In your case you need to force ATA using typeAcquisition in jsconfig.json
See https://code.visualstudio.com/docs/nodejs/working-with-javascript#_typings-and-automatic-type-acquisition
"typeAcquisition": {
    "include": ["jest"]
}

For some reason, jsconfig.json does not work correctly for me. It removes the errors, but it defaults all types to any, 😞. Only working solution is to explicitly install the @types/jest myself.
with jsconfig.json https://prnt.sc/rpgmuf
with npm i --save-dev @types/jest https://prnt.sc/rpgkyl


Prevent user from moving forward to next question during the guided assistant process until request has been completed

From @yfzwinnie on November 2, 2018 22:29
Copied from original issue: Microsoft/Access2Justice#756

@KellyeDC  - I don't think this is needed for pilot.


Add atomic modifyRepairRun method to storage

Also, marking updateRepairRun as deprecated. The next step is to
replace all uses of that method with the new one, and then remove
updateRepairRun from IStorage.
I think that the postgress storage version can probably be implemented in a better way, using transactions rather than locks. But the current approach should be correct.

As you said, we could also utilise Postgres functions and LANGUAGE sql or plpgsql. In general, if using databases that will live longer, and be extended during the lifetime, it makes sense to use database functions for everything. Using database side functions creates an abstraction layer that is usable for separating DBA and developer concerns, making it easy to optimise the database side separately from the code, change the schema, add support for sharding, etc. easier.


Case-sensitivity for Postgres

I started using KnexJS today and it became apparent that all references passed to KnexJS are case-sensitive by default for PostgreSQL.
For example knex('SomeTable')... doesn't work for me but knex('sometable')... does. The same goes for column names. This behaviour seemed a little unexpected to me since queries using the 'pg' package directly would have accepted both of those formats.
I tried looking up the documentation to verify that knex is indeed case-sensitive for Postgres but couldn't find any information. Additionally, is there anyway to toggle this case sensitivity behaviour in Knex?

@phao5814 This is not a KnexJS-specific functionality, PostgreSQL as a database is case-sensitive.
For example knex('SomeTable')... doesn't work for me is not an accurate depiction of what is happening. If you have table that matches case of "SomeTable" exactly, it will work. If case is different, it won't. Same should be the case when using 'pg' directly.

@kibertoad Apologies if my initial comments were misleading - I'm still new to DBs in general so I may struggle to verbalise what I mean.
What I was trying to convey is that I believe in Postgres, identifiers that are not double-quoted are folded to lower case in PostgreSQL as outlined in this SO post.
This means that when I write queries in pgAdmin and in 'pg', 'SELECT SomeTable ....' would be automatically converted to 'SELECT sometable ...'.
I just found it inconsistent to suddenly see 'this relation does not exist' errors in Knex when I used table and column names with different casing.

Knex adds quotes to all identifiers to make them case sensitive. If you really want to change how quotes are added around identifiers, you can pass custom wrapIdentifiers implementation to knex configuration.
Anyways I don't think that is a good idea to override. Better would be to use identifier names correctly and in a case sensitive manner, so that if you have lowercase names in the database, then you would write them in code as lowercase.


.github: Handle missing app-emulation/hv-daemons

LTS channel has no such package, so the action for finding the kernel update was failing. Fix it by updating the package only if it exists.

Argh, this wasn't enough, follow-up PR incoming…

Please see https://github.com/flatcar/scripts/pull/2326.


Callback construction doesn't work upon server restart / 1.2.0 breaks things

I updated this package and things started breaking:
For example, this 'callback cbKey' construction breaks as soon as the server restarts (actually this was always an issue)
      @callbacks[cbKey] = callback

    _id = mailQueue.insert
      uid:      @uid
      opts:     opts
      to:       opts.to
      subject:  opts.subject
      template: opts.template
      sendAt:   opts.sendAt
      isSent:   false
      tries:    0
      callback: cbKey

The @callback[] array will be lost after restart, which means all the references in the collection to the callback will be incorrect, causing errors and mails not being send out! Bad idea
But you included a new check on line 84 _self.callbacks[letter.callback]. It now causes this error:
I20161031-14:19:17.276(1)? Trying to send email to<EMAIL_ADDRESS>again for NaN time(s)
I20161031-14:19:17.277(1)? Exception in defer callback: TypeError: _self.callbacks[letter.callback] is not a function
I20161031-14:19:17.277(1)?     at packages/ostrio_mailer.js:216:47
I20161031-14:19:17.278(1)?     at [object Object]._.extend.withValue (packages/meteor.js:1122:17)
I20161031-14:19:17.278(1)?     at packages/meteor.js:445:45
I20161031-14:19:17.278(1)?     at runWithEnvironment (packages/meteor.js:1176:24)

when I log out 'error' from (error, success, recipient) -> I get:
{ error: [TypeError: Cannot read property 'length' of null] }
which I suspect refers to the same line/issue - as email gets delivered fine using 1.1.0 and I don't see any changes in the API.

Hey @satyavh ,
Thank you for report, actually updated version was hanging around my SSD for last few month, waiting for release. Your message was a good reason.
Could you please update to v1.2.1, and check this issue on your end?

@satyavh added a notice/explanation for send's callback - https://github.com/VeliovGroup/Meteor-Mailer/commit/17b635b37c904e024fdb43d743c66787bf107609

It's a little better, but I still have this error that I didn't have with 1.1.x
I20161031-15:43:33.092(1)? Email wasn't sent to<EMAIL_ADDRESS>[TypeError: Cannot read property 'length' of null]
I20161031-15:43:33.092(1)? Trying to send email to<EMAIL_ADDRESS>again for 1 time(s)

I have no idea where this error comes from. Perhaps you see it:
My init:
  Meteor.mail = new Meteor.Mailer
    login: "[.....]"
    host: "[.....]"
    connectionUrl: "[.....]"
    accountName:  "[.....]"
    intervalTime: 5
    verbose: true

Send function:
    Meteor.mail.send
      to: accountName + '<' + invite.email + '>',
      subject: name + " invited you to join " + accountName + " at PostSpeaker."
      replyTo: "[...]"
      message: "You've been made an " + invite.role + " by " + name + '. Click here to setup your account and get started.'
      inviter: name
      teamName: accountName
      role: invite.role
      inviteUrl: baseUrl + 'invitation/' + invite.token
      preview: "You've been invited to join " + accountName + " at PostSpeaker by " + name + ". Open this email to continue setting up your account."
      btnText: "Get started"
      template: Assets.getText 'Invitation.html'

I've logged out the options and all fields are correctly set. This exact code works find in 1.1.x

@satyavh reproduced, solved. See v1.2.2. Please let me know how it works on your end

Email gets send now, so that's cool!
However the template {{ }} do not get populated

Also, the email often gets send twice

@satyavh

However the template {{ }} do not get populated

Can not reproduce, and don't see you using placeholders in your template
Works on my end, testing right now on mailing service, doesn't sent twice

What do you mean you don't see me using placeholders in my template? I definitely have placeholders in my template and they were working fine in 1.1 :-)
About the sending twice, I'll dive into it. But it def happens for me

Sending twice might be caused by Meteor.defer / the interval. Sending takes time, and while it is sending the interval (queueTry ) might run again, causing it to be sent twice. Something like that...

@satyavh intervalTime: 5, 5 seconds may be not enough to complete SMTP session.
Could you please show you template with placeholders and how you define helpers?

what Assets.getText 'Invitation.html' returns?
console.log Assets.getText 'Invitation.html'

Found it, line 163/169, your regex doesn't support camelCase and excludes quite a lot of characters. I feel this is a better regex, excepting anything between {{ and }}
matchStr  = string.match /\{{2}\s?([\s\S]+?)\s?\}{2}/g
alternatively:
matchStr  = string.match /{{2}\s?([a-zA-Z0-9-_]+)\s?}{2}/g

Okay, I guess never used it with uppercase letters. Thank you for investigation.
Tested, updated and published as v1.2.3

Awesome, it works like a charm again!

@satyavh thank you sir for the help with investigation.


Filtering two columns that represent that same model but two different relationships

Summary of problem or feature request
I have a problem with using filter columns when both columns represent a different relationship to the same Model. The search will not create a query where it joins twice to the same table.
I have tickets that have both a reporter relationship and an assignee relationship. Both are of the User model. I have two filter columns where I want to be able to filter on tickets that are created by one user but assigned to a different user. I can filter on one column, but not on a second. Filtering on other columns, for example reporting user + title of ticket works perfectly.
Code snippet of problem
My query in the controller
            $tickets = Ticket::with(['reporter', 'assignee', 'municipality', 'status'])->select('tickets.*');
            return $datatables->eloquent($tickets)->make(true);

My datatables build up. (all columns can be filterd via an input in the tfooter)

var ticketTable = $('#tickets-list').DataTable({
            serverSide: true,
            processing: true,
            order: [[ 6, "desc" ]],
            ajax: '/tickets/data',
            rowId: 'id',
            columns: [
                {data: 'title'},
                {data: 'reporter.name'},
                {data: 'assignee.name'},
                {data: 'municipality.name'},
                {data: 'status.name'},
                {
                    data: 'created_at',
                    render: function(d){
                        return moment(d).format("YYYY-MM-DD HH:mm");
                    }
                },
                {
                    data: 'updated_at',
                    render: function(d){
                        return moment(d).format("YYYY-MM-DD HH:mm");
                    }
                }
            ]
        })

The query that is used in the end. Even though I filtered both reporter and assignee. It refuses to join for assignee_user_id.
select `tickets`.* from `tickets` left join `users` on `tickets`.`reporter_user_id` = `users`.`id` where LOWER(`users`.`name`) LIKE '%%user%%' and LOWER(`users`.`name`) LIKE '%%admin%%' and `tickets`.`deleted_at` is null order by `updated_at` desc

I wrote my own query that works when performed on the database:
select `tickets`.*
from `tickets`
left join `users` `reporter` on `tickets`.`reporter_user_id` = `reporter`.`id`
left join `users` `assignee` on `tickets`.`assignee_user_id` = `assignee`.`id`
where
	LOWER(`reporter`.`name`) LIKE '%%user%%'
	and LOWER(`assignee`.`name`) LIKE '%%admin%%'
	and `tickets`.`deleted_at` is null order by `updated_at` desc

But I don't really get how to get Laravel-datatables to use it that way.
System details

Operating System: MacOS Sierra 10.12.6
PHP Version: 7.1.10
Laravel Version: 5.5.*
Laravel-Datatables Version:  8.3.1
Datatables Version: 1.10.16

There is a known issue when using same table joins when using eager loading. In this regard, I suggest you use the join statement you created and just convert it to Laravel query format.
See https://datatables.yajrabox.com/eloquent/joins for ref.


Switch places of subtitles DNS and Proxy settings

Proxy settings titles was placed in the DNS misconfiguration part, and the DNS settings title was placed in the proxy configuration part. This changes moves the places of the titles so that they both present the section they intend to.

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Thanks for your contribution!


Figure out how to run tests without SwiftPM trying to build all targets

If you run swift test now, SwiftPM first tries to build all targets (even though the only tests target has a single dependency on the SwiftCrossUI target). This has the outcome of meaning that you need to have all backend system dependencies present (e.g. gtk4, qt@5) on your computer to run swift test (very annoying). Due to this, I've disabled the swift test step in macOS and Linux CI until a solution is found.

I ran into a similar issue with one of my repos, never found a solution, so curious if you find one.

My only idea so far is to make Package.swift remove all non-tested targets when a TEST environment variable is present so that you can run TEST=1 swift test, but that's pretty hacky.


Dark mode button doesn't remember setting on restart

The dark mode setting is reset upon restarting the game. Just clicking "save and exit world" and re-entering doesn't do this, it only happens when the game is completely restarted. Like my other opened issue, this is on 1.19 and the ATM8 modpack.

This seems to be an issue with 1.1.1.  Reverting to 1.1.0 fixes the problem.

This problem seems to have returned in 1.19.2-1.1.3.  I updated and on load the client, the GUI was back to normal.  I changed it to the dark mode I prefer, restarted the client and it was back to normal again.
FYI, Forge 43.2.14


Implementation of Stack [Java]

Hi,I'm a GSSoC participant.
I wish to add the implementation of Stack in Java with time and space complexity.

Hello admin , I want to contribute on this issue.
I will do this as per your guidelines.
Please assign this issue to me.
This is regarding to GSSOC'21.

@tarun26091999 @rudrakshi99 @plazzy99 @nakul-19, I would like to contribute to the above problem in CPP and java. am a GSSoC'21 participant. Kindly assign this to me.


Fix Mach-O import when no segment contains the header

Certain Mach-O files don't have a segment that contains the header. In this case, MachoProgramBuilder.setupHeaderAddr is supposed to create an area in the "OTHER" address space for the header. setupHeaderAddr keeps track of the lowest file offset for each segment that it looks at to find the one with the lowest start address.  It then adds the "HEADER" memory block as 0 to the lowest start address.
Before, if there were any segments that were empty (segment.getFileOffset() == 0 && segment.getFileSize() == 0), then setupHeaderAddr would mistakenly set the lowest start address to 0 instead of ignoring the segment.  This would cause MemoryMapDB.checkFileBytesRange to throw an IllegalArgumentException.
With this change, setupHeaderAddr ignores empty segments.
This change passes all of the unit and integration tests.  There are no explicit tests for MachoProgramBuilder.

Can you attach a file that highlights the issue?

I don't have one that I can share at the moment. However I believe that any DWARF file from a .dSYM directory will exhibit the problem if loaded into Ghidra by itself.
I'll see if I can find a small example file somewhere.

Problem
Opening a DWARF file that contains only symbols crashes with:
java.lang.IllegalArgumentException: Length must be > 0, got 0
java.io.IOException: java.lang.IllegalArgumentException: Length must be > 0, got 0
	at ghidra.app.util.opinion.MachoLoader.load(MachoLoader.java:107)
	at ghidra.app.util.opinion.AbstractLibrarySupportLoader.doLoad(AbstractLibrarySupportLoader.java:887)
	at ghidra.app.util.opinion.AbstractLibrarySupportLoader.loadProgram(AbstractLibrarySupportLoader.java:98)
	at ghidra.app.util.opinion.AbstractProgramLoader.load(AbstractProgramLoader.java:131)
	at ghidra.plugin.importer.ImporterUtilities.importSingleFile(ImporterUtilities.java:395)
	at ghidra.plugin.importer.ImporterDialog.lambda$okCallback$7(ImporterDialog.java:336)
	at ghidra.util.task.TaskBuilder$TaskBuilderTask.run(TaskBuilder.java:306)
	at ghidra.util.task.Task.monitoredRun(Task.java:134)
	at ghidra.util.task.TaskRunner.lambda$startTaskThread$0(TaskRunner.java:106)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: java.lang.IllegalArgumentException: Length must be > 0, got 0
	at ghidra.program.database.mem.MemoryMapDB.checkFileBytesRange(MemoryMapDB.java:743)
	at ghidra.program.database.mem.MemoryMapDB.createInitializedBlock(MemoryMapDB.java:714)
	at ghidra.app.util.MemoryBlockUtils.createInitializedBlock(MemoryBlockUtils.java:227)
	at ghidra.app.util.opinion.MachoProgramBuilder.setupHeaderAddr(MachoProgramBuilder.java:1025)
	at ghidra.app.util.opinion.MachoProgramBuilder.build(MachoProgramBuilder.java:142)
	at ghidra.app.util.opinion.MachoProgramBuilder.buildProgram(MachoProgramBuilder.java:110)
	at ghidra.app.util.opinion.MachoLoader.load(MachoLoader.java:97)
	... 11 more

As explained above, the problem is that the lowest file offset becomes zero in setupHeaderAddr. Then, when it tries to create a new header block in the "OTHER" space, it passes the length for this new block as zero. Since a block has to have non-zero size, loading the file produces the above error.
Repro
This error is 100% reproducible with the following steps.
Steps:

Download and unzip tiny_app_unsigned_dSYM_only.zip. Inside there is one file called tiny_app_unsigned which is a DWARF file that contains only symbols. (The __PAGE_ZERO, __TEXT, __DATA_CONST, and __DATA segments are empty).
Start Ghidra.
Create a new non-shared project.
Import the tiny_app_unsigned file using File -> Import file...
It should correctly discover that it's a Mac OS X Mach-O file for AARCH64.
Click "OK".

Expected result: File is loaded.
Actual result: The error above.
This Pull Request fixes the problem by ignoring the empty segments.
Please let me know if you need any more information.

Thanks, I am able to reproduce and see that your change fixes the primary issue.  I am seeing a lot of other undesirable things once the binary loads, so I'll probably add additional fixes.


add mutationobserver-shim and remove dataset to support ie10

Not sure if my method is perfect but as far as I can tell it works as before but also works in IE10.

Let me give it a deeper look, but looks great!
I wrote down in my TODO list to reply your issue, but I have been very busy lately :(
I think it is good to have IE10 (and lower, maybe) support, but I don't know if the size increase of the bundle is worth to ship it to all users. I was thinking about creating another bundle version with higher browser compatibility for those developers who need it.
I will give it a look as soon as possible and will tell you what my thoughts are.
Thank you! 😁

Would wrapping the require in a condition work.
    if (this.ie10) {
      require('mutationobserver-shim');
    }

If so the module could have a config option added, something like
export const IE10 = new InjectionToken<boolean>('IE10');

@NgModule({
  declarations: [LazyLoadImagesDirective],
  exports: [LazyLoadImagesDirective]
})
export class LazyLoadImagesModule {
  public static forRoot(ie10?: boolean): ModuleWithProviders {
    return {
      ngModule: LazyLoadImagesModule,
      providers: [
        {
          provide: IE10,
          useValue: ie10
        }
      ]
    };
  }
}

I'm just not entirely sure if that would work in terms on not including mutationobserver-shim in the final build

Yes, that wouldn't execute the mutationobserver-shim but wouldn't prevent it from being added to the bundle.
I have been thinking about this case and I came up with two solutions.
One solution would be to create a different bundle including the Mutation Observer for the users who want broader compatibility, supporting IE10 with the polyfill. So the users would have to require this special bundle instead of the regular one.
And the solution that I like the most, which is to use getAttribute to avoid the unsupported datasetproperty, and then let the users to require the MutationObserver polyfill that they want. They will have to code it like this:
import 'mutationobserver-shim';
import { LazyLoadImagesModule } from 'ngx-lazy-load-images';

I think that the second solution is better because we let the users to choose the polyfill that they want. I have been searching for the best polyfill and I didn't see any clear winner as I saw with the IntersectionObserver polyfill.
What do you think?

I think the second solution would be best as it gives the necessary flexibility and removes the need for you to maintain an extra bundle.

Yes, I think so too. Would you mind updating the PR to adequate to this solution? :)

OK that's done

I think that the only changes that we need to keep are the ones from onImageAppearsInViewport(), right? I prefer to not do any style modifications to the current code.

Yes that's correct, I have prettier turned on so that's changed the style a bit.


feat(jiva): add version compatibility framework

This commit adds version compatibility framework for adding replica to
controller and vice-versa.
From now on we will only allow upgrades in Replica -> Controller order else controller or replica will reject the requests.
replica will only allow controller with old or same version whereas controller will only allow replica with latest or same version.
Signed-off-by: Utkarsh Mani Tripathi<EMAIL_ADDRESS>

closing this PR as this is not solving the problem. Will be reopened if any change in data path required.


Change device name for integration

No way to add two identical devices. I have two sm-T813. If I integrate bother I get a duplicate device created in HA.  Need to be able to change the device name before integration.

Are you login with same account?

You can avoid this issue by logging in with another user. But I agree, we need this option.

I'm not sure I understand your answer. I have two tablets that are the same and a phone that is different.  I log in as the same user as I am the same user.  You may want to check out how Areila handles it.  I used it until HA recommended your app do to the changes in HA.

I see, you don't need to use different users. I'll add a possibility to change device name.

Will be presented in 1.0.0.
You'll need to remove Mobile App integration from Home Assistant and restart server. Then just open HA Client and it will ask you to create an integration again with ability to set device name.


Please update for the new Edge

Hi
Please update the page for the New Microsoft Edge browser.

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

ID: 2010f5ac-1080-addd-1fb3-5b05db26c1f6
Version Independent ID: 1aa18d6a-5846-7989-b844-fc8ad027921b
Content: Azure AD Connect: Seamless Single Sign-On
Content Source: articles/active-directory/hybrid/how-to-connect-sso.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

@grzegorzwierzbicki, thank you for reaching out. We are looking into this and would get back to you soon on this thread.

@billmath Could this be incorporated to the document ?

This has been added.  Thanks!
#please-close


FEATURE - support smartlinks configuration in Fiori apps

As a developer,
I want to deliver my application with pre-configured targets for the included smart links,
so that I can create/modify smart link configurations in my changes folder and deliver together with my app.
Description
This feature request should enable a user to add a smart links configuration to an application. With those pre-configured targets from the system, changes can be done directly and included before deployment.
Technical Design

New module @sap-ux/app-config-writer
Include in @sap-ux/create module as add smartlinks-config command

Acceptance Criteria
GivenWhenThen format (https://martinfowler.com/bliki/GivenWhenThen.html)
Given I have an existing application with system configuration in ui5-deploy.yaml
when I execute @sap-ux/create add smartlinks-config command
then a smartlinks configuration will be added to the application
Given I have an existing application without ui5-deploy.yaml
when I execute @sap-ux/create add smartlinks-config command
then I can enter system details and a smartlinks configuration will be added to the application
Given I have a smartlinks configuration in the application
when I start flp preview
then changes can seen with those targets considered.
Notes

Under the webapp/appconfig folder a fioriSandboxConfig.json is created, containing links e.g.:

{
  "services": {
    "ClientSideTargetResolution": {
      "adapter": {
        "config": {
          "inbounds": {
            "firstLink": {
              "semanticObject": "SmartLinkNavigation",
              "action": "tofirstlink",
              "title": "Navigate to First Link",
              "signature": {
                "parameters": {},
                "additionalParameters": "allowed"
              },
              "resolutionResult": {}
            },
            ...
          }
        }
      }
    }
  }
}

This is then referenced as custom middleware fiori-tools-servestatic in ui5/ui5-mock/ui5-local.yaml, e.g.:

    ...
    - name: fiori-tools-servestatic
      beforeMiddleware: fiori-tools-proxy
      configuration:
        paths:
          - path: /appconfig
            src: appconfig

Tasks

[x] Create new module
[x] Include in @sap-ux/create
[x] Unit Tests added
[ ] Test Cases defined

@johannes-kolbe could you add a little more information about what files will be modified or added, maybe a snippet with an example?

@tobiasqueck Added more information about the modified files and a snippet of the expected fioriSandboxConfig.json and changes to ui5.yaml

@Klaus-Keller For the integration into @sap-ux/create, should a possibility to "remove" the smartlinks configuration be available too? The question arises, if yes, what exactly should be removed/modified then..

@johannes-kolbe, for @sap-ux/create it is technically not required to have also a remove option. If it does not really make sense, you can skip it. Perhaps align with Christoph.

@johannes-kolbe @Klaus-Keller I would consider a remove as a prio 2 topic at this point, as an existing configuration doesn't influence something negatively. And update option via "add" is available.


Compressed FGB files are recommended or not?

Hello,
Compressed FGB files seem to have the advantage of smaller file size as shown in the gzipping example below.
Is it recommended, however, with regard to reading speed performance or not? I think that *.fgb.gz may be read by using Feature: Compression Streams (Chrome Platform Status), for example.
$ wget https://raw.githubusercontent.com/flatgeobuf/flatgeobuf/master/test/data/UScounties.fgb
$ gzip -k UScounties.fgb
$ ls -lh
-rw-r--r-- 1 kkdd  staff    13M  5  6 13:22 UScounties.fgb
-rw-r--r-- 1 kkdd  staff   7.6M  5  6 13:22 UScounties.fgb.gz

@kkdd well the answer is - it depends. If you have unlimited bandwidth compression is never useful right?
More serious answer:
It would probably make sense to compress when you transfer over anything else than local disk / RAM. However, compression have another problem and that is that it usually does not support random access, so it is only useful if you want to read the whole thing. There are ways to use compression also for semi-random access but not something readily available. https://github.com/lz4/lz4 is very interesting both because it is very fast and I think it can support semi random access but it needs to be implemented in places like GDAL for which I've made an issue a long time ago (https://github.com/OSGeo/gdal/issues/2201) but it needs a serious time investment. But if you don't want to bother with what might be in the future, gzip is absolutely fine for full payload compression.

Thank you for your explanation.


fix dependencies on package.json

the packages listed as "dev" actually are required for usage.

This will fix the issue https://github.com/micahblu/gulp-connect-php/issues/1.

Thanks!


The srt file greyed out when I tried to load downloaded subtitle

The CC button also greyed out. How do I supposed to load downloaded subs?

Did you long pressed the file open button?

Did you long pressed the file open button?

Thank you! Omg very unintuitive approach


Remove unnecessary kiosk files from CDN path

Updated the deployment script to not push the index.html and GameList.json files to the CDN.

@EdKaim resolve conflict?

I messed up the merge and will reissue once it's fixed.


[BACKLOG-24049] As a Pentaho user I would like to delegate ETL work i…

…tem execution to Worker Nodes in a synchronous fashion, to that I can scale out 'Open' / 'Open in new window' action as well

This fixes scale.sh to work well regardless of being part on a "vanilla" pdi-client , or a pdi-core

To be merged alongside https://github.com/pentaho/pentaho-ee/pull/1299
@pentaho/rogueone please review

Build Skipped
:white_check_mark: There was nothing to build. The changes are probably excluded by the build rules. If this is an error, please contact your system administrator.


Current kv::Object interaction model is flawed

Similar to #446
Now all kv::Objects have three types of member functions which should be called from other objects:

"Getters" - they only return some value without changing anything internally in any object
E.g. - Door::IsState, Movable::GetDir, MapObject::GetOwner
"Setters" - functions which are not supposed to do anything except change some variable inside object - no other objects should be involved, no objects should be removed. Most probably such functions are not virtual, but probably that isn't a strict rule.
E.g. - MapObject::SetOwner, MaterialObject::SetPassable, MaterialObject::SetSprite
"Actions" - they represent some default action for an object like pushing, rotating, etc. Because different objects may behave differently on the same action actions are virtual functions.
E.g. - Door::Open, MapObject::AttackBy, MapObject:Delete, MapObject::Bump

Note that Object::Process or MapObject::Represent does not belong to any of these categories, because they should not be called from another objects - they are called only from specific classes (like ObjectProcessor or Game).
1 & 2 types are fine, the issue is the third one.
Usual flow of some member functions:
void kv::FooObject::DoSomething()
{
    // Do a lot of inner work
    // Maybe check some variables
    // Somehow get IdPtr to other object
    IdPtr<kv::BarObject> bar = GetBarInSomeWay();
    // Calling an action
    bar->BarAction();
    // Do a lot of other work
    // Maybe even call other actions
}

But nothing can be said for sure about BarAction. There isn't any restriction for implementations of actions in subclasses - an actions is just basically a notifier about some event. How to react to this event is completely up to object itself. So after BarAction call the caller does not know ANYTHING about world anymore. The action can explictly or implicitly delete the caller or change its variables or anything else.
For now it works well, but it is because the code is very simple and small. Later it will become a big issue. So some better way should be devised.
There are actually a lot of ways to handle the issue, they will be described later.

Just do nothing about it.

Objects interations can be quite complex, but in reality only few of them do anything complex.
It is quite possible to subsist a certain amout of time without any bugs which can be caused by the issue.
Pros:

Nothing should be done
Cons:
After certain amount of time codebase will become quite big and subtle bugs will appear. Moreover, because it is not a BYOND the bugs most possibly will result in crashes. It will be impossible to manually find out all places where a bug could happen.

2. Use event based system instead of function calls
In terms of Qt it would be queued connections instead of direct ones.
Pros:

Caller function will be finished before a next one will be called
Easy to debug or prevent loops

Cons:

Impossible to pass pointers to game objects reliably - an object can be removed already
Long function which will request a lot of actions should be divided into separate part (i.e. async code overall) - not easy to code, debug & understand such stuff
Hard to implement

3. Postpone the real deletion of objects until the end of the tick
Just mark objects as deleted, and clean up them only when they are not used by anyone else for sure.
Pros:

Only minimum changes are required, overall code should look the same
Relatively easy to implement

Cons:

Impossible to delete objects in order to prevent their multiple activation/usage (e.g. current implementation of projectiles deletes bullets after they hit something). Can be somewhat neutralized by some IsDeleted() function.
All functions should be written in a reenterable manner, so before and after any 'action' call objects should be in the valid state. Moreover, after an 'action' call the caller should not assume anything about own state. It is not that hard, but unfortunately impossible to enforce this rule - so some random weird errors will appear with time.


Create distribution_lib for TF backend

Add Mesh and Layout helper functions

Codecov Report
Patch coverage: 40.00% and project coverage change: -17.64% :warning:

Comparison is base (1bc3827) 73.68% compared to head (f5ab436) 56.05%.
Report is 1 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #18479       +/-   ##
===========================================
- Coverage   73.68%   56.05%   -17.64%
===========================================
  Files         330      331        +1
  Lines       31923    31937       +14
  Branches     6234     6236        +2
===========================================
- Hits        23524    17901     -5623
- Misses       6873    12623     +5750
+ Partials     1526     1413      -113

Flag
Coverage Δ

keras
56.05% <40.00%> (-17.57%)
:arrow_down:

keras-numpy
56.05% <40.00%> (-0.01%)
:arrow_down:

keras-tensorflow
?

keras-torch
?

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

Files Changed
Coverage Δ

keras/backend/__init__.py
64.10% <ø> (-23.40%)
:arrow_down:

keras/backend/tensorflow/distribution_lib.py
35.71% <35.71%> (ø)

keras/backend/tensorflow/__init__.py
100.00% <100.00%> (ø)

... and 164 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


tests/bsim/bluetooth/audio/test_scripts/cap_broadcast_ac_12.sh failing in main

Describe the bug
One BT audio CAP Broadcast AC test is failing in main:
tests/bsim/bluetooth/audio/test_scripts/cap_broadcast_ac_12.sh
in its "Execute_AC_12 48_4_1" step
To Reproduce
Make sure you have bsim installed and are ready to build targeting the nrf52_bsim

tests/bsim/bluetooth/audio/compile.sh
tests/bsim/bluetooth/audio/test_scripts/cap_broadcast_ac_12.sh

Expected behavior
No test failures
Impact
Failures in CI, blocking PRs
Logs and console output
...
d_00: @00:00:58.014617  [5800]: Stream 0x84d4240 sent with seq_num 5800
d_01: @00:00:58.077226  Received BASE with 1 subgroups from broadcast sink 0x854a3a0
d_01: @00:00:58.077226  Metadata updated
d_01: @00:00:58.077226  type 2 len 2
d_01: @00:00:58.617227  Received BASE with 1 subgroups from broadcast sink 0x854a3a0
d_01: @00:00:58.617227  Metadata updated
d_01: @00:00:58.617227  type 2 len 2
d_00: @00:00:59.014617  [5900]: Stream 0x84d4240 sent with seq_num 5900
d_01: @00:00:59.157227  Received BASE with 1 subgroups from broadcast sink 0x854a3a0
d_01: @00:00:59.157227  Metadata updated
d_01: @00:00:59.157227  type 2 len 2
d_01: @00:00:59.697227  Received BASE with 1 subgroups from broadcast sink 0x854a3a0
d_01: @00:00:59.697227  Metadata updated
d_01: @00:00:59.697227  type 2 len 2
d_00: @00:01:00.000722  TESTCASE NOT PASSED at exit (test return (1) indicates it was still in progress)
d_01: @00:01:00.008038  TESTCASE NOT PASSED at exit (test return (1) indicates it was still in progress)

Environment (please complete the following information):

OS: Ubuntu 24.04
Toolchain (e.g Zephyr SDK, ...): Host gcc 14
Commit SHA or Version used: main after f970b066d210af56ab6159b2c22e825230c212b9

Additional context
Failure started after https://github.com/zephyrproject-rtos/zephyr/pull/80228 got merged
f970b066d210af56ab6159b2c22e825230c212b9

Failures in CI, blocking PRs

Just to be clear: It's only blocking a few PRs :)
This issue is seen in a few PRs (https://github.com/zephyrproject-rtos/zephyr/pull/79931, https://github.com/zephyrproject-rtos/zephyr/pull/80691).
The issue is that the host stops receiving data from the controller.
It receives exactly 8 SDUs, which corresponds to the number of buffers configured for the test: CONFIG_BT_CTLR_ISO_RX_BUFFERS=8
The issue is timing related it seems, and modifying the number of octets sent or simply add a small k_sleep in the receiver "fixes" the issue.
I have only seen it happen on the nRF52 BSIM, and have not been able to reproduce with the nRF53 BSIM nor on target.


chore: fix the deprecated message of yq.

"Flag --tojson has been deprecated, please use -o=json instead"

@zhangcheng Thank you, 2.2.1 release has been published with the update.


Add __init__.py in cucim.core

Hopefully addresses some import issues seen around modules in this package.
cc @grlee77

Feel free to try this command if you are comfortable merging 🙂

@gpucibot merge


Fix typo: pupup -> popup

Fix typo: pupup -> popup

I like pupup :dog2:

Pleas

@emilk I suggest not doing this - it gives potential contributors a bad impression. There is also a burden to write small PRs.
I start with small PRs to decide whether it's worth putting effort into merging larger PRs, generally sorting my outstanding changes in increasing size and complexity.
I imagine others do the same to avoid wasting time, or at least to estimate how easy it is to get fixes upstreamed. Typo PRs are actually a good way to welcome new contributors.
For what it's worth, I wasted a few seconds wondering whether pupup was a typo, or if it meant something, did a find/replace, and checked that the code still worked. I wasn't looking for typos, I just encountered it and figured I'd save some others a bit of confusion. I made the change while making another functional change (#1091), but I think it is bad practice to bundle unrelated changes together.

@HackerFoo You make a good point, and I apologize. I agree that it is good to fix spelling and grammar (code readability is super important), and keeping changes separate is also a good idea. Though I would prefer for the change to be a separate commit in a bigger PR rather than a separate PR. Of course, this is my personal preference (and one that I have gone back and forth on over the years). I also haven't clearly stated my preference in the contributor guidelines, so that's on me.
There is also the context of people making commits with a single minor spelling fix in some unimportant file just to be able to be credited as contributors to a project, a behavior that just adds noise to the open source world.
Anyway, I changed the pupup -> poup in https://github.com/emilk/egui/commit/199bbef77bf59f9f5fa48346c715d827559e00cb#diff-eb4801118508476c267604aae155912ad2f8cae54490b4bc6d6ed9d0a3a38730


[Bug]: Gnosis Wallet not displaying on Modal

Current Behavior
The title is half true. Let me explain; After adding the gnosis wallet to the list, opening my Dapp and starting the modal I can't see the Gnosis Safe as an option. But, if I go to gnosis-safe app and open my Dapp from there it will be in the list and connects as expected.
Expected Behavior
I was expecting the same behaviour as V1, where it displays in the list indicating to the user that we have support and once the user clicks it would ask them to go to the gnosis-safe app so they can do the usual procedure through gnosis app.
Steps To Reproduce

Install<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Instantiate the gnosis module (no params was passed down)
Do the onboard wallets / chains setup as usual
Open onboard modal to select a wallet

Onboard Version
2.0.9
Node Version
v16.13.2
What browsers are you seeing the problem on?
Chrome
Relevant log output
No response
Anything else?
No response

Hey Bruno, yes this is one of main differences between version 1 and version 2. We believe to improve the UX of connecting a wallet, that it is better to only show wallets that the user can successfully connect to. To indicate support for Gnosis safe, could you add an icon to your app somewhere that links them to your app via Gnosis safe instead?

I see, but the suggested path would break the idea of a better UX, no? because, I have the modal with the wallets but I also have somewhere else let's say an icon to the gnosis safe to redirect you to the gnosis safe app. I am assuming I can't add anything in the modal at this point. For example, if I start that module with whitelistedDomains:[] and head to gnosis safe app I see exactly what I was expecting in the first place and that is why I opened the issue.
Here is a screenshot of the nice warning message and an explanation of what should be done with the above config and opening inside gnosis-safe-app. 😄

This should be documented properly. Seems like this provider is intended to be used only when the app is a safe-app.

Hello, The same problem until now that Gnosis Wallet not displaying on Modal, but it is working when using gnosis-safe app
I see that if we did the same warning message in the screenshot, it is going to be bizarre because we should see this warning message when we are not in the gnosis-safe app, not the opposite. I am working on it, but I did not find until now the way to add a warning message when selecting wallet in blocknative V2.


Can't build from source - codegen error

Environment

Deploy method:  built from sources
Jitsu version:  for instance 1.42.8
OS: for instance  Ubuntu 20.04 / Windows 10

Description
Can build server but having an issue building configurator.
$ ./local-build-configurator.sh -d false

============================================
=    Building go Configurator backend...   =
============================================

rm -f configurator
rm -rf ./build
go get<EMAIL_ADDRESS>go generate
error processing flags: flags --generate, --templates aren't supported in new config style, please use --old-style-config or update your configurationmain.go:72: running "oapi-codegen": exit status 1
Makefile:29: recipe for target 'go_generate' failed
make: *** [go_generate] Error 1
Building go configurator backend failed

Steps to reproduce
follow build form source doc
Expected behavior
build configurator
Actual behavior
codegen error

Hi @keedle !
What version of go do you use?
I cannot reproduce the problem with:
go version go1.18.4 linux/amd64 on Ubuntu 20.04
go version go1.19.1 darwin/arm64 on Mac OS 12.6

Hi @absorbb ,
go version go1.19.1 linux/amd64 on Ubuntu 20.04 just tried to build and it failed log attached ☹ Maybe I'm missing a step or something?
ubuntu@server:/var/www$ git clone https://github.com/jitsucom/jitsu.git
Receiving objects: 100% (51656/51656), 30.38 MiB | 24.23 MiB/s, done.
Resolving deltas: 100% (35665/35665), done.

ubuntu@server:/var/www$ cd jitsu/
ubuntu@server:/var/www/jitsu$ chmod +x local-build-server.sh
ubuntu@server:/var/www/jitsu$ chmod +x local-build-configurator.sh
ubuntu@server:/var/www/jitsu$ chmod +x local-build-jitsu.sh
ubuntu@server:/var/www/jitsu$

ubuntu@server:/var/www/jitsu$ go version
go version go1.19.1 linux/amd64
ubuntu@server:/var/www/jitsu$ ./local-build-server.sh -d false

=====================================
=    Downloading javascript sdk...  =
=====================================

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 19913    0 19913    0     0   5337      0 --:--:--  0:00:03 --:--:--  5335

=====================================
=       Building go Server...       =
=====================================

rm -f eventnative
rm -rf ./build/dist/eventnative
rm -rf ./build/dist
echo "Using path /home/ubuntu/go/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/local/go/bin"
Using path /home/ubuntu/go/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/local/go/bin
go mod download
GOARCH=amd64 go build -ldflags "-X main.commit=`git rev-parse --short HEAD` -X main.builtAt=`date -u +%FT%T.000000Z` -X main.tag=$( case master in ( master ) git describe --tags ;; ( * ) echo master ;; esac )" -o eventnative
mkdir -p ./build/dist/web/
mv eventnative ./build/dist
mkdir -p ./build/dist/web/
test -e ../javascript-sdk/lib.js && cp ../javascript-sdk/lib.js ./build/dist/web/ || echo "\n\033[31m!!! WARNING:\033[m lib.js wasn't found at ../javascript-sdk/lib.js. Please build JS SDK first, or embedded tracking will not work!\n"
mkdir -p ./build/dist/web/
cp ./web/dist/web/* ./build/dist/web/
cp ./web/welcome.html ./build/dist/web/

=====================================
=        SUCCESSFUL BUILD           =
=====================================
ubuntu@server:/var/www/jitsu$ ./local-build-configurator.sh -d false

============================================
=    Building go Configurator backend...   =
============================================

rm -f configurator
rm -rf ./build
go get<EMAIL_ADDRESS>go generate
error processing flags: flags --generate, --templates aren't supported in new config style, please use --old-style-config or update your configurationmain.go:72: running "oapi-codegen": exit status 1
Makefile:29: recipe for target 'go_generate' failed
make: *** [go_generate] Error 1
Building go configurator backend failed
ubuntu@server:/var/www/jitsu$

@keedle
there may be newest version of oapi-codegen already installed on you system.
You can check with:
oapi-codegen -version
if it is v1.11 you can downgrade with
go install<EMAIL_ADDRESS>command and build jitsu.
we need to upgrade build scripts to support new version of oapi-codegen to close this ticket.


HTTP cache missing

I updated a Dashchan extension to support LynxChan. Doing that, I found out that some features, e.g. watching a thread's post count, don't work properly:

client makes a request to read /foo/res/2342.json to display a thread
user watches thread
client makes repeated request to read the post count, which result in the same request to fetch /foo/res/2342,json
server returns 304: not modified
client extension throws this error up the chain, Dashchan is confused because it doesn't know the post count and displays "-1" in the UI instead.

Proposed solution (would help to implement it):
Use HttpResponseCache in DashChan's HTTP abstraction to cache results, so that repeated requests to the same resource still return the proper data.

I don't think it's necessary to implement cache, as it will be needed to store responses somewhere. Instead, Dashchan caches the objects received from extension. I actually don't understand how it's possible, 304 is returned only when you pass a proper HttpValidator (which provides If-Modified-Since and If-None-Match headers), and threads watcher and posts page use different HttpValidator objects, so these entities shouldn't cross.
I'm planning to merge threads watcher with the data source for posts page, so this particular problem won't exist. Implementing an additional HTTP cache is definitely overkill.


Upgrade to i18n_extension: ^6.0.0

Hi,
I tried to add the Visual Editor, but it looks that some libraries are quite old, is it possible to upgrade i18n_extension to ^6.0.0?
Without this I got some incompatibilities with other libraries.

HI @vd3d. Late reply, holidays season. I'm usually not eager to update to x.0.0 versions because of potentially hidden bugs. I'll have a look by end of week to see what is the current state of affairs and if there.

Hi @adrian-moisa , you're right. The version 6 is maybe too young.
But I've tested the version 5.0.1 and it looks stable.

@adrian-moisa Any update on this? I'm not being able to update other packages due to this.


Add theme Eventually

Add theme Eventually

Hey!
You're theme.toml seems to be missing the demoite, even though you seem to have one. Can you please add that?

I have added the demo-site link. Thanks for the response. Hope to see the theme in the repo soon.

Hey!
You're theme.toml seems to be missing the demoite, even though you seem to have one. Can you please add that?

I commit+push the theme repository as mentioned. Do i need to commit anything here as well? Sorry for the trouble, I am just a beginner, hope you will understand.

@hugo-sid Is there any problem with the theme? What is process for making my theme appear in hugo website?


Add PA and ML to 2.0.1 manifest

Signed-off-by: Zelin Hao<EMAIL_ADDRESS>Description
Add PA and ML to 2.0.1 manifest
Issues Resolved
Part of #2165
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #2171 (3580885) into main (c1b847d) will increase coverage by 5.43%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##               main     #2171      +/-   ##
=============================================
+ Coverage     94.56%   100.00%   +5.43%
=============================================
  Files           204         6     -198
  Lines          4253       105    -4148
  Branches         29        19      -10
=============================================
- Hits           4022       105    -3917
+ Misses          225         0     -225
+ Partials          6         0       -6

Impacted Files
Coverage Δ

...workflow/opensearch/build_artifact_check_plugin.py

src/test_workflow/dependency_installer.py

...est_workflow/bwc_test/bwc_test_suite_opensearch.py

tests/jenkins/jobs/BuildArchive_Jenkinsfile

...ts/jenkins/jobs/BuildUploadManifestSHA_Jenkinsfile

src/test_workflow/perf_test/perf_args.py

...bwc_test_start_properties_opensearch_dashboards.py

src/jenkins/TestManifest.groovy

...workflow/integ_test/integ_test_start_properties.py

src/manifests_workflow/component_opensearch.py

... and 188 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 c1b847d...3580885. Read the comment docs.


The Dart process still remains even after the process is completed

Thanks for this amazing development.
I don't know if this is directly related to the Dart language, but during development using Dart, after debugging and checking the screen in the local environment, the process remains even after the screen is closed and debugging is completed.
I recently investigated the cause of my laptop's high battery drain and CPU load, and found that there were several Dart processes left that should have been terminated as described above, some of which remained for more than 100 hours after termination.
I'm sorry if a similar event has already been reported as an issue.

Thanks for taking time to report an issue. We will need more information to diagnose it.
What are these processes that are left behind? Are they your processes which failed to quit even though you stopped the debugging session (e.g. using STOP button in the IDE) or are these auxiliarly processes that IDE launches (e.g. Dart analysis server, Dart development service etc).

@myConsciousness can you kindly supply the requested information?

Sorry I was hard to find the time to come here.
In case you're wondering, I'm using a Macbook with an M1 silicon chip. I don't know the details of this event, because I only saw it after some event happened, but I think it is reproducible, because this event has been happening on my local machine since I published this issue.
I am using the Dart language with VSCode to do Flutter development. I have noticed that when I run flutter run and exit the emulator after checking the screen, the Dart process that was running in the emulator seems to remain. In fact, this has been happening frequently in the past week, and I have to manually kill the process after finishing the screen check using the emulator.

I think if you not close vscode, the dart will be remaining there cause the language server is still working.  Not sure if it's correct.

Sorry @myConsciousness but without more detail, and a set of repro steps, this is too unclear for us to investigate. From your description this could be a potential issue in anything from VSCode to the flutter tool to the Dart core libraries.

Closing as unactionable


Set vagrant name

Without this, vagrant still refers to the vm as 'default'
I only hit this because I was trying to run multiple copies of game on locally inside vagrant, and needed to distinguish them.
To run multiples locally, you also have to manually edit the 2 port mappings to map to known empty ports, else they will conflict with each other

This change is

Reviewed 4 of 4 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Ensure CNAME is set after each build

Ahhh, so it whipes the entire folder rather than modifies it, and hence the file CNAME must be set explicitly via this action. Doh


[Analytics] Add custom event for new/existing users for complete user profile forms

Make a distinction between returning and new users to the user profile forms for analytics research.

Resolved by making the routes unique.


how to toggle picker visibility from diff component

I have gone through these following points

[x]   Check latest documentation: https://docs.nativebase.io/
[x]   Check for existing open/closed issues for a possible duplicate before creating a new issue: https://github.com/GeekyAnts/NativeBase/issues
[x]   Use the latest NativeBase release: https://github.com/GeekyAnts/NativeBase/releases
[x]   Check examples from NativeBase KitchenSink https://github.com/GeekyAnts/NativeBase-KitchenSink

Issue Description
I can't toggle the Picker visibility through different component , say onButtonPress, I have tried using ref so I can access the _setModalVisible method , but I can't access it , is there anyway I can achieve this?

The functionality you mention here is not the default behaviour for pickers and hence isn't a part of this library. And since we're using the native picker for android, it won't work on android anyway.
So I'd suggest that you do the implementation yourself.


Fix issue with minus and fraction.

Formula such as $1-\frac{2}{3}$ make the minus very hard to read. Find a way to add spaces around operators.

Coloring should make this readable.

I have added spaces around most operators. I might have not thought of some corners cases so feel free to open an issue for that.

You need to pick another font. It will fix it.


Fix an incorrect casting in PutOperation

The change should be self explanatory. This was detected when testing out large blobs.
Also added a unit test.
Reviewer: Casey

LGTM, merging


module 'mxnet.symbol' has no attribute 'sum'

Hi all,
it might be an easy fix. i'm trying to run the neural-style example but getting the above error right after parsing the input images on the run.py at line 118. I did a dir(mx.sym) and indeed, sum is not listed as a attribute. Is this a typo in the code?
thanks,
Laszlo
edit_1:
had to change line 118 and 120 from:
mx.sym.sum
to:
mx.sym.numpy.sum
not sure of the consequences of this yet.
edit_2:
not sure if this problem is relating to the above (that's why I didn't open a new issue). But I'm now getting a 'Shapes of operands are not the same' error. check failed: shape1 == shape2. And as a result python crashes.

You need to pull the most recent code

I pulled it about 6 hours ago. Was there any change since? I'll pull again to try. thanks

I am facing the same problem. Does anyone have solutions right now?
Thank you very much!!!

pull the most recent code and compile

It was my mistake, I mixed up between versions. I by the way used the windows prebuilt libs but mixed up the sources and that was the problem. its all working as it should. thanks

I'm closing this as its resolved.

@piiswrong
it doesn't work!

@piiswrong
After recompiling, the error still exist.
Traceback (most recent call last):
  File "run.py", line 166, in <module>
    style_loss, content_loss = get_loss(gram, content)
  File "run.py", line 118, in get_loss
    gram_loss.append(mx.sym.sum(mx.sym.square(gvar - gram[i])))
AttributeError: 'module' object has no attribute 'sum

I search the source code, but can't find any lines that define the class symbol.sum

@yech1990
just pulled the repo, and did a clean compile in linux, run the neural example and I can confirm that there is no problems with it. I think you have different libs mixed up like i did before. Try to remove all your mxnet and recompile.

@lasandcris
I did that, but still failed.
Do you change the model with GPU? The GPU is disabled in my script.

@yech1990
yes, I did:
python run.py --gpu -1
this executes the processing on the cpu - and sets all the other variables to default.


Options for combat roll confirmation

When confirming a combat roll it would be nice to have just a basic input for focus being spent and extra damage to add in the calculation. The focus cost doesn't have to be automated yet but having that query show on the chat card is an easy way to remember to deduct the correct amount.
Also, there are a lot of powers that add extra damage based on variable focus spent, and inputting how much extra damage should be factored into the calculation would be very useful.

I very much second this request - it would make the math a lot easier for some of more 'numbers-challenged' players :-)
Thanks!

Hi there, apologies for the late response. I am tracking this issue in #26, so I will close this in favor of that, but I will copy/paste your comment so nothing gets lost. Thank you for your input!


Docs update quickstart iceberg

What is the purpose of the pull request
Fix typos for Iceberg sourceFormat
Brief change log
Fix typos for Iceberg sourceFormat in how-to docs
Verify this pull request
Minor/trivial

LGTM 👍


feat: add Remix Fly Stack

going to need to some fine tuning on the readme
Signed-off-by: Logan McAnsh<EMAIL_ADDRESS>

Sweet! I haven't run through this a second time, but you've addressed all the things I had brought up the first time so I say this is good to merge when you're ready 👍


[WIP] Added HelpBubble component to display inline documentation in the UI

Closes #705
Adding a HelpBubble.vue component using popper.js
It's currently only displayed next to the "Regenerate API Key" button in Account Settings to show what it might look like.
CSS can be modified if needed and message content to be defined.

This looks pretty good- a few thoughts:

The popper component shows up as a div inside the modal, which does some strange things (like add a scroll bar) on my screen. It would be nice if it could be show up in front of the modal, and not affect spacing, etc. in the modal. I think this would be just a CSS change.

The little "i" does look good in this instance, but I'm concerned what will happen if this pattern is used across all fields in the UI, especially on the EditPage. Maybe we can play around with having the popper show up when hovering over the label, but only after a ~1 second delay?