Using icons inside of a touchable component

putting the <Icon.. inside of a <TouchableHighlight> will throw this error
Touchable child must either be native or forward setNativeProps to a native component

render() {
  return (
    <TouchableHighlight onPress={()=> this._onButtonPress()}>
        <Icon name="ChevronDown" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="#999" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round" />
    </TouchableHighlight>
  );
}

I tried following this example to setNativeProps, but I still end up with
null is not an object (evaluating this._root.setNativeProps)

Here's an example of my <Icon>
import React from 'react';
import SvgIcon from 'react-native-svg-icon';
import SVGIcons from '../lib/SVGIcons';

export default class Icon extends React.Component {
  setNativeProps = (nativeProps) => {
    this._root.setNativeProps(nativeProps);
  }

  render() {
    return (
      <SvgIcon ref={component => this._root = component} {...this.props} svgs={SVGIcons} />
    );
  }
}

Here's my SVGIcons
import React from 'react';
import { Polyline } from 'react-native-svg';

export default {
  ChevronDown: <Polyline points="6 9 12 15 18 9" />,
  ChevronUp: <Polyline points="18 15 12 9 6 15" />
}

Is there already a way to do this that I'm missing? Or is this something that would need to be added in?

This is just an unfortunate issue of React Native. The safest approach is to always put a <View> as the first child, then put your <Icon> in that.

Yeah, I noticed that. I had a few of my Icons inside of a <Text> which shows some other weird side affects.
After messing with this, I found a workaround that works... I don't know if it's good or not. If I just don't do anything in the setNativeProps, and remove the ref from the component, then it seems to work. This probably is a react native issue though.
import React from 'react';
import SvgIcon from 'react-native-svg-icon';
import SVGIcons from '../lib/SVGIcons';

export default class Icon extends React.Component {
  setNativeProps = (nativeProps) => {
    // do nothing here, and that seems to work
  }

  render() {
    return (
      <SvgIcon {...this.props} svgs={SVGIcons} />
    );
  }
}

I'm rolling with this for now so I'll close it. Hopefully someone else comes up with a better solution later.


Support for generic app SQS handlers

In my app, I need to handle SQS webhooks the code for which is part of the same repo. How could I extend the current TF package to:

Deploy the code as another lambda not integrated to APIGW
Reuse the code zip that is generated if possible

Thanks!

I'm going to close this issue because it has been inactive for 30 days ⏳. This helps to find and focus on the active issues.


geemap.py: dos2unix

#1693

It seems very line of the file is touched, but I can't see what content has been actually changed.

See https://linux.die.net/man/1/dos2unix
Every line is CRLF → LF. There are no other changes.

Does this mean all other files need to be changed to? This seems like rewriting the entire codebase, and it will make the git history uncessary large.  Are there any other workaround?
Or can your write a script to automatically pull the source code from GitHub and run dos2unix locally to make the format compatible with Google's internal build system? Otherwise, when others contribute to this PR, they do not necessary use 'LF' rather than 'CRLF'. This means we need to rewrite the codebase over and over again.

Does this mean all other files need to be changed to? This seems like rewriting the entire codebase, and it will make the git history uncessary large. Are there any other workaround?

It's only two files and I'm not worrying about thee CSV.
find . -type f | egrep -v '[.]git/' | xargs file | grep CRLF
./geemap/geemap.py:                                                 Python script, Unicode text, UTF-8 text executable, with CRLF line terminators
./geemap/data/template/ee_api_docs.csv:                             Algol 68 source, Unicode text, UTF-8 text, with very long lines (2281), with CRLF line terminators

Or can your write a script to automatically pull the source code from GitHub and run dos2unix locally to make the format compatible with Google's internal build system? Otherwise, when others contribute to this PR, they do not necessary use 'LF' rather than 'CRLF'. This means we need to rewrite the codebase over and over again.

There is a setting we can add that will make sure it is always unix style LF in the repo. I will do that in a separate PR.


DBZ-2238 Fix test failure - MySqlSourceTypeInSchemaIT#shouldPropagateSourceTypeAsSchemaParameter

https://issues.redhat.com/browse/DBZ-2238

@Naros Nice catch! One question, would not be the easiest fix to modify the regexs to look like .*\.c1 to include the dot in the pattern?

would not be the easiest fix to modify the regexs

Actually it would have and since I need to remove the system-out debugging, I'll go that route.  For whatever reason that didn't dawn on me when I saw what was creating the random failures.

@jpechane, I applied your advice and cleaned up the changes.  Thanks for spotting that!

@Naros Applied, thanks!


Create CODE_OF_CONDUCT.md

Add code of conduct based on contributor covenant v1.4.
Signed-off-by: Eric Ernst<EMAIL_ADDRESS>

@egernst Can you add a subsystem to the commit message?

we're looking @ creating a mailing list for CoC issues, so this PR will need updating

This reads great but please note line length in the update. Best practice for .md files is 78 characters.

Medium will be a copy paste anyway (not md). thanks for the heads up.
On Aug 29, 2017, at 5:16 PM, Ianeta Hutchinson <notifications<EMAIL_ADDRESS>wrote:
This reads great but please note line length in the update. Best practice for .md files is 78 characters.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/clearcontainers/shim/pull/59#issuecomment-325806710, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATPXWyWMZJ6TYo9Y1sVtC5NP-KjeE9cbks5sdH-igaJpZM4PAj2R.

updated with new mail address

@iphutch - can you take another look?

lgtm

@egernst - looks like jenkins is asleep (we've seen this a few times but have no idea what is wrong).
Could you force a rebase and re-push to wake it up?

kicked it -- we'll see soon.  Thanks @jodh-intel


Improvements & fixes to the FileResourceHandler

The file resource handler could not serve anything outside user.dir and it should accept a File argument.

Thanks


Automate release

Fixes #512
Fixes #511
Fixes #530
Fixes #537
Fixes #490
Fixes #381
Summary
To release all of our software, you can now:

checkout master
run make VERSION_ADDITIONAL=RC1 release to perform the release

If you don't have the right github tokens / s3 tokens / github repo access / etc, the script will fail and should report the access you're missing.
Release Endpoints

pachd -- is built w the additional version specified, tagged, and pushed to docker hub
job-shim -- the same thing happens
manifests

the versioned (etc/kube/pachyderm-versioned.json) and unversioned (etc/kube/pachyderm.json) manifests are updated and committed in the pachyderm repository
the versioned manifest is published to the website, which means its:

copied and committed to the www repo
uploaded to S3, so that its available at https://pachyderm.io/manifest.json

pachctl

Is updated via homebrew (the homebrew repo is updated / committed / pushed)
Is available via for install on linux via a one liner: curl -o /tmp/pachctl.deb -L https://pachyderm.io/pachctl.deb && dpkg -i /tmp/pachctl.deb

Which means that the deb file gets committed to www repo / uploaded to S3

Versioning

We simplified versioning a lot. Now versions look like 1.0.1-foo
We no longer tag builds on travis (tagging is only done at release time via the release make task)
We can put any RC or other string we want
or if no AdditionalVersion is supplied, it'll contain the commit hash that was used to compile it

This has the nice side effect that when doing make launch it'll always be a released version, and when doing make launch-dev it will always contain the hash of the repo when the image was built.

Last step is me testing on my machine right?

Haha. Yup. Todos from testing on JD's machine:

Update setup.md to include linux one liner
Fail (and stop) if goxc not configured (missing GH token)
Fail if sha256sum not found
Update www script to upload single file
Make sure we can supply a blank string (for no additional version)
Remove commented lines in release task ... and output message to ask user to push to complete release

Ok, did each of the things above.
The one exception is that uploading a single file doesn't work for larger files. I've opened an issue on the www repo to track this.
Also ... it made me very happy to remove most of the docs under the release instructions.
Once the builds pass again, I'd like you to run the script locally again @jdoliner , but this time test a point release, so:

increment the micro version in src/client/version/version.go
run make point-release

Then we'll have v1.0.2 released. If you'd rather test a pre-release, I'm ok w that too. In that case, no code changes, just:
make VERSION_ADDITIONAL=RCblah release

And fixed #600 while I was in there. Now we have true separation between pachctl installs (without go!) and pachyderm cluster deployment!


udp: callbacks are effectively synchronous

From https://github.com/iojs/io.js/pull/1313#issuecomment-89425847:

Libuv loops over the write requests in the completed queue.
For every request, it hands it off to io.js
io.js calls into JS land
JS land calls uv_udp_send() again (dgram.send())
The write succeed immediately and uv_udp_send() pushes the request onto the completed queue, the same queue it's currently iterating over.

Commit 4189122 introduced this.  The (very lightly tested) patch below fixes it:
diff --git a/deps/uv/src/unix/udp.c b/deps/uv/src/unix/udp.c
index 941c0ae..177ad43 100644
--- a/deps/uv/src/unix/udp.c
+++ b/deps/uv/src/unix/udp.c
@@ -133,10 +133,8 @@ static void uv__udp_io(uv_loop_t* loop, uv__io_t* w, unsigned int revents) {
   if (revents & UV__POLLIN)
     uv__udp_recvmsg(handle);

-  if (revents & UV__POLLOUT) {
+  if (revents & UV__POLLOUT)
     uv__udp_sendmsg(handle);
-    uv__udp_run_completed(handle);
-  }
 }

Running QUEUE_SPLIT on handle->write_completed_queue before dispatching the callbacks in uv__udp_run_completed does not have the desired effect.
I'm not sure if a better fix that maintains the throughput benefits of calling uv__udp_run_completed() repeatedly is possible.
Refs: https://github.com/iojs/io.js/pull/486
Refs: https://github.com/iojs/io.js/pull/1258
Refs: https://github.com/iojs/io.js/pull/1313
/cc @saghul

@bnoordhuis I've been looking at this a bit, and I can't see how the diff you pasted fixes it, because we'd never call uv__udp_run_completed then (on close aside).
Why do you think splitting the queue doesn't solve it? We could do that at the top of uv__udp_run_completed and at the end, check if write_completed_queue is empty. If so, we don't stop the io handle for POLLOUT, because there are pending callbacks for next iteration. Or is there any other problem?
Alternatively, we could decrement send_queue_size and send_queue_count after calling the send callback, but that would prevent the write to be attempted synchronously, so there would probably be a throughput penalty.
I can try to experiment a bit, is there an easy way to test this?

I don't recall the details but I remember that QUEUE_SPLIT didn't have any effect.  If you revert https://github.com/nodejs/io.js/commit/18d457bd3408557a48b453f13b2b99e1ab5e7159, benchmark/net/dgram.js should start busy-looping again.

I'll give it a shot, thanks!

Fixed by https://github.com/libuv/libuv/pull/371.


Feature/attribute card

Mushroom
Hi!
I just discovered your project and I like it a lot. But I was missing a way to show some more information(attributes) of an entity. So I just went tinkering around and made this Attribute card.
It is based on the entity-card, so you might see some similarities.
Not a 100% happy with the design but it's functional.
I have no idea if you are at this point in time looking for anything like this but I thought might as well try :)

Hi 🙂 thanks for the PR. Why do not use the template card to do this?
type: custom:mushroom-template-card
entity: climate.thermostat
primary:  '{{ state_attr(entity, "name") }}'
secondary:  '{{ state_attr(entity, "température") }}°C'

What about this ?
type: custom:mushroom-template-card
entity: climate.thermostat
primary:  '{{ state_attr(entity, "name") }}'
secondary:  '{{ state_attr(entity, "temperature") }}°C - {{ state_attr(entity, "battery") }}%'

The problem with an attribute card is that attributes are not normalized is Home Assistant so it can be difficult to have rules for everyone. Also, it can be difficult to format/translate.
That's why we recommend to use template card for this custom use-cases.
We already discussed about attributes in the issue #109.


A function with a return type of void can't be awaited without a warning

🔎 Search Terms
await promise void "'await' has no effect on the type of this expression" function return type parameter
🕗 Version & Regression Information

This changed between versions 3.6.3 and 3.7.5

⏯ Playground Link
https://www.typescriptlang.org/play/?ts=5.5.0-dev.20240507#code/MYewdgzgLgBAJiAyiAtgUygCwJZgOYwC8MAhhAJ5jAwAUwJANgwEYnADWAXLQJREB8MAG4hscPoUEBvAFAxSAdxLZY9Jqw40eMgL4yZCZOiy48NMpWpaBMWfID09mADpXunkA
💻 Code
const doSomething = async (callback: () => void) => {
  await callback()
}

doSomething(async () => {
  // ...
})

🙁 Actual behavior
There is a warning at the "await" saying
'await' has no effect on the type of this expression.(80007)

But the return type might be a promise.
🙂 Expected behavior
No warning
Additional information about the issue
No response

There is an error at the "await" saying

There is no error. It's a hint, and that's working as intended, see #34508.

Looking through the comments in #34508 and remembering that I've seen several duplicates recently, I'm baffled why so many people seem to think this is an error.  It's not.  It's just the language service trying to be helpful by offering you a refactor; you're free to ignore it.

Yeah, void return type is basically saying "I'm not going to do anything with the return value of this function". If it happens to return a promise and you await it, that's observable.

Ah, that makes sense. I was thinking in terms of "void | Promise<void> is redundant, because anything Promise<void> accepts is also accepted by void".
(And "error" was a typo, I meant "warning", I'll correct it)

It’s not even a warning really - it’s more of a suggestion “here’s a thing that might or might not be wrong that you could think about changing”

It’s not even a warning really - it’s more of a suggestion “here’s a thing that might or might not be wrong that you could think about changing”

That same "suggestion" style is also used when you use parameters without types if TypeScript isn't set up strict enough, for example. Most of the time, following the suggestion would be good - I'd see them as warnings.

Most of the time, following the suggestion would be good

That's actually the case here too. If you want to await your value, then you should represent this intention in your types as well.


musl: 1.1.11 -> 1.1.15, add security patch.

Motivation for this change
Update to latest (Aug 2015 -> July 2016), and apply recommended upstream patch for security issue present in all versions.
(see http://www.openwall.com/lists/oss-security/2016/10/19/1 for more information)
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

I did test using nox-review but it only built the musl package.  I'm not sure if there are more useful things to check that use musl.

Well I tried checking the bootstrap tools on Linux, but with or without this change I'm unable to evaluate 'test' attribute:
$ nix-build pkgs/top-level/release.nix -A stdenvBootstrapTools.x86_64-linux.test -Q --show-trace
error: while evaluating the attribute ‘buildCommand’ of the derivation ‘test-bootstrap-tools’ at /home/will/misc/2016/dec/nixpkgs-musl/pkgs/stdenv/linux/make-bootstrap-tools.nix:188:5:
while evaluating anonymous function at /home/will/misc/2016/dec/nixpkgs-musl/pkgs/stdenv/linux/default.nix:6:1, called from /home/will/misc/2016/dec/nixpkgs-musl/pkgs/stdenv/linux/make-bootstrap-tools.nix:176:21:
assertion failed at /home/will/misc/2016/dec/nixpkgs-musl/pkgs/stdenv/linux/make-bootstrap-tools.nix:183:19

Quick investigation suggests this is due to 5c6234a7d3f0b430d7dc941dc1ab059c42729611, although maybe I'm invoking things wrong under the new system.
Anyway, looks like 'dist' seems to work for both x86_64-linux and i686-linux, with the contained 'busybox' binary seemingly working fine.

The evaluation errors above are resolved in https://github.com/NixOS/nixpkgs/pull/21189 .
Rebasing onto that gets test working for x86_64-linux and i686-linux! 🎉

@dtzWill, sorry for commenting on an old thread but what was the reason for adding --disable-gcc-wrapper in https://github.com/NixOS/nixpkgs/pull/21023/files#diff-6419c747d225d6615bb68bce4fcf42ecR25 ? I didn't see it mentioned in the CVE.

It's not related to the CVE, but was added as part of upgrading to 1.1.14 as originally done in another PR: https://github.com/NixOS/nixpkgs/pull/16217/files#diff-6419c747d225d6615bb68bce4fcf42ecR23 .
Removing that flag doesn't seem to change behavior of normal build (it decides to not build any wrappers) I'll see what happens when cross-compiling.
Are you looking to enable and install the wrapper?

Well I was mistaken my current big evaluation rebuilds compilers and binutils and all sorts of things... but only musl the once!
Was hoping I could tease out a reason for the change in terms of breakage but seems to be fine for me :).
I think the idea is that we'll provide our own cc-wrapper (or gcc-cross-wrapper) anyway and so musl shouldn't bother.
Hope that helps at least explain the history and reasoning of the change.

Thanks for looking into this @dtzWill. It's no huge deal, but I would vote for leaving off --disable-gcc-wrapper and letting musl build musl-gcc. It's handy for building static binaries. When I commented that line out locally and nix-env installed musl, I did get musl-gcc.

Hmm, my tree (including some of the expression for musl) has some differences that would explain the difference no worries.  I mean sounds good to me either way, I don't have a particular preference so I'd err on going with the answer that works best for everyone-- which sounds like removing it!
Would you mind submitting a PR to do so? :)

Submitted a PR: https://github.com/NixOS/nixpkgs/pull/22212.


Add canary configuration to smoke test matrix

This PR adds new entries to the smoke test matrix definition to run all the public cloud tests against a Canary/EUAP region (specifically eastus2euap).
Passing smoke test pipeline here (for new canary jobs, AzureChinaCloud seems to be having a transient issue but I'll keep an eye on it): https://dev.azure.com/azure-sdk/internal/_build/results?buildId=572805&view=results
Resolves Azure/azure-sdk#1879

AzureChinaCloud seems to be having a transient issue but I'll keep an eye on it):

This tends to time out frequently due to the linked template and the latency in requesting it from GitHub.   Daniel was looking into it at one point, but I'm not sure where that ended up.

AzureChinaCloud seems to be having a transient issue but I'll keep an eye on it):

This tends to time out frequently due to the linked template and the latency in requesting it from GitHub. Daniel was looking into it at one point, but I'm not sure where that ended up.

Yeah, it seemed like it was getting a 404 for some asset in github. I re-ran the failed job, so we'll know in a few minutes. In any case, it seemed independent of my changes.

As a follow-on to some of this, I'm thinking about moving towards using some of the devops looping primitives along with parameters, as opposed to using matrix (as @weshaggard pointed out we're starting to do in other places). But I thought it would be better to stand up canary testing first within the existing config format, before making larger changes.

I added a minor update based on some feedback from @mikeharder to only add a single canary instance to the matrix (sparse matrix coverage), in order to not cause resource stress regarding the build agent pool.

It should also be pointed out that the .NET smoke tests are currently testing against older packages instead of the latest packages in the repo, see issue https://github.com/Azure/azure-sdk-for-net/issues/14418.

/azp list

/azp run net - smoke-tests


Fixed error getting h2 HEADERS frame after stream is closed

#0  0x000000000052f24e in Ptr<HdrStrHeap>::operator bool (this=0x30) at /home/bcall/dev/yahoo/build_8/_build/ats_build/../../trafficserver/lib/ts/Ptr.h:112
#1  0x000000000060ceba in HdrHeap::HeapGuard::HeapGuard (this=0x2ab532e75158, heap=0x0, str=0x7cfda4 ":method") at /home/bcall/dev/yahoo/build_8/_build/ats_build/../../trafficserver/proxy/hdrs/HdrHeap.h:279
#2  0x000000000067236f in HdrHeap::duplicate_str (this=0x0, str=0x7cfda4 ":method", nbytes=7) at ../../../../trafficserver/proxy/hdrs/HdrHeap.cc:315
#3  0x000000000067d8cf in mime_str_u16_set (heap=0x0, s_str=0x7cfda4 ":method", s_len=7, d_str=0x2ab579b7e108, d_len=0x2ab579b7e122, must_copy=true) at ../../../../trafficserver/proxy/hdrs/MIME.cc:2903
#4  0x000000000067ab59 in mime_field_name_set (heap=0x0, field=0x2ab579b7e108, name_wks_idx_or_neg1=-1, name=0x7cfda4 ":method", length=7, must_copy_string=true) at ../../../../trafficserver/proxy/hdrs/MIME.cc:1747
#5  0x000000000054fecf in MIMEField::name_set (this=0x2ab579b7e108, heap=0x0, mh=0x2ab579b7e0b8, name=0x7cfda4 ":method", length=7) at /home/bcall/dev/yahoo/build_8/_build/ats_build/../../trafficserver/proxy/hdrs/MIME.h:763
#6  0x0000000000614688 in MIMEFieldWrapper::name_set (this=0x2ab532e753b0, name=0x7cfda4 ":method", name_len=7) at ../../../../trafficserver/proxy/http2/HPACK.h:71
#7  0x0000000000614fdb in HpackIndexingTable::get_header_field (this=0x2ab558f80440, index=3, field=...) at ../../../../trafficserver/proxy/http2/HPACK.cc:275
#8  0x00000000006160c1 in decode_indexed_header_field (header=..., buf_start=0x2ab5596f8ff0 "\203Ї", buf_end=0x2ab5596f9010 "0", indexing_table=...) at ../../../../trafficserver/proxy/http2/HPACK.cc:746
#9  0x0000000000616797 in hpack_decode_header_block (indexing_table=..., hdr=0x2abc37dfc640, in_buf=0x2ab5596f8ff0 "\203Ї", in_buf_len=32, max_header_size=131072, maximum_table_size=4096)
    at ../../../../trafficserver/proxy/http2/HPACK.cc:909
#10 0x000000000060c005 in http2_decode_header_blocks (hdr=0x2abc37dfc640, buf_start=0x2ab5596f8ff0 "\203Ї", buf_len=32, len_read=0x0, handle=..., trailing_header=@0x2abc37dfc700: false, maximum_table_size=4096)
    at ../../../../trafficserver/proxy/http2/HTTP2.cc:616
#11 0x000000000060de9b in Http2Stream::decode_header_blocks (this=0x2abc37dfc400, hpack_handle=..., maximum_table_size=4096) at ../../../../trafficserver/proxy/http2/Http2Stream.cc:140
#12 0x000000000061dae6 in rcv_headers_frame (cstate=..., frame=...) at ../../../../trafficserver/proxy/http2/Http2ConnectionState.cc:326
#13 0x00000000006208c7 in Http2ConnectionState::main_event_handler (this=0x2abf5c1e0010, event=2253, edata=0x2ab532e75900) at ../../../../trafficserver/proxy/http2/Http2ConnectionState.cc:922
#14 0x00000000005347f2 in Continuation::handleEvent (this=0x2abf5c1e0010, event=2253, data=0x2ab532e75900) at /home/bcall/dev/yahoo/build_8/_build/ats_build/../../trafficserver/iocore/eventsystem/I_Continuation.h:160
#15 0x000000000061878f in send_connection_event (cont=0x2abf5c1e0010, event=2253, edata=0x2ab532e75900) at ../../../../trafficserver/proxy/http2/Http2ClientSession.cc:58
#16 0x000000000061ad93 in Http2ClientSession::do_complete_frame_read (this=0x2abf5c1dfd40) at ../../../../trafficserver/proxy/http2/Http2ClientSession.cc:496
#17 0x000000000061af84 in Http2ClientSession::state_process_frame_read (this=0x2abf5c1dfd40, event=100, vio=0x2ab7412a2170, inside_frame=false) at ../../../../trafficserver/proxy/http2/Http2ClientSession.cc:533
#18 0x000000000061a532 in Http2ClientSession::state_start_frame_read (this=0x2abf5c1dfd40, event=100, edata=0x2ab7412a2170) at ../../../../trafficserver/proxy/http2/Http2ClientSession.cc:426
#19 0x0000000000619bc7 in Http2ClientSession::main_event_handler (this=0x2abf5c1dfd40, event=100, edata=0x2ab7412a2170) at ../../../../trafficserver/proxy/http2/Http2ClientSession.cc:312

I wasn't getting this crash a couple weeks ago.  The only change in http2 that has happened was:

commit 0e817411a3a55d5acc6fd62ba41167904f4c5c8d
Author:     Masakazu Kitajo<EMAIL_ADDRESS>AuthorDate: Wed Aug 15 12:27:48 2018 +0900
Commit:     Bryan Call<EMAIL_ADDRESS>CommitDate: Fri Aug 31 09:09:19 2018 -0700
Clear up evnets and timers for a H2 stream before destroying its mutex

(cherry picked from commit bb428f89c647e5d27e29e5faa86cc6eafe350324)

Frequency that I am seeing this in production:

21:59:38 e10:/home/y/logs/trafficserver$ grep bcall diags.log
[Sep 10 20:23:40.450] {0x2ac729347700} ERROR: bcall - received HEADERS frame on closed stream
[Sep 10 20:40:53.813] {0x2ac72bd74700} ERROR: bcall - received HEADERS frame on closed stream
[Sep 10 20:51:25.193] {0x2ac72a8ce700} ERROR: bcall - received HEADERS frame on closed stream
[Sep 10 21:07:16.042] {0x2ac72a68a700} ERROR: bcall - received HEADERS frame on closed stream
[Sep 10 21:18:06.846] {0x2ac729e5b700} ERROR: bcall - received HEADERS frame on closed stream
[Sep 10 21:29:37.729] {0x2ac72b3a2700} ERROR: bcall - received HEADERS frame on closed stream
[Sep 10 21:52:32.162] {0x2ac72b1ff700} ERROR: bcall - received HEADERS frame on closed stream

Frequency that I am seeing these errors:
[Sep 11 00:08:19.849] {0x2ac729ffe700} ERROR: bcall - received HEADERS frame on closed stream
[Sep 11 01:25:19.364] {0x2ac72ab73700} ERROR: bcall - received HEADERS frame on closed stream
[Sep 11 01:26:02.033] {0x2ac72a9d0700} ERROR: bcall - received HEADERS frame on closed stream
[Sep 11 01:49:32.324] {0x2ac7291a4700} ERROR: bcall - received HEADERS frame on closed stream
[Sep 11 02:28:08.578] {0x2ac729b15700} ERROR: bcall - received HEADERS frame on closed stream
[Sep 11 04:04:28.325] {0x2ac72ba2e700} ERROR: bcall - received HEADERS frame on closed stream
[Sep 11 05:22:41.283] {0x2b58281a1700} ERROR: bcall - received HEADERS frame on closed stream
[Sep 11 05:48:26.088] {0x2b58072d9700} ERROR: bcall - received HEADERS frame on closed stream
[Sep 11 05:51:17.040] {0x2b582868a700} ERROR: bcall - received HEADERS frame on closed stream
[Sep 11 06:13:31.668] {0x2b580590a700} ERROR: bcall - received HEADERS frame on closed stream
[Sep 11 06:21:00.458] {0x2b580761f700} ERROR: bcall - received HEADERS frame on closed stream
[Sep 11 06:57:01.435] {0x2b5805b4e700} ERROR: bcall - received HEADERS frame on closed stream
[Sep 11 07:18:16.392] {0x2b5805604700} ERROR: bcall - received HEADERS frame on closed stream
[Sep 11 07:26:06.985] {0x2b582868a700} ERROR: bcall - received HEADERS frame on closed stream
[Sep 11 07:36:44.999] {0x2b5805706700} ERROR: bcall - received HEADERS frame on closed stream
[Sep 11 07:41:50.455] {0x2b5806179700} ERROR: bcall - received HEADERS frame on closed stream

I started to see those logs again, so it is not #4114
18:54:57 e10:/home/y/logs/trafficserver$ tail -F diags.log  | grep bcall
[Sep 11 19:16:13.624] {0x2ae229d2f700} ERROR: bcall - received HEADERS frame on closed stream
[Sep 11 19:26:55.796] {0x2ae229b2b700} ERROR: bcall - received HEADERS frame on closed stream
[Sep 11 19:33:19.979] {0x2ae22bd8a700} ERROR: bcall - received HEADERS frame on closed stream
[Sep 11 19:42:22.068] {0x2ae2292bc700} ERROR: bcall - received HEADERS frame on closed stream
[Sep 11 19:45:46.183] {0x2ae234202700} ERROR: bcall - received HEADERS frame on closed stream

@bryancall It seems to me that streams are not removed from stream_list when ATS send RST_STREAM frames. This explains the find_stream mystery @shinrich pointed out.
I have no idea what changes led the crash and how the crash is occurred, but here's my assumption:
I assume stream is not nullptr and the stream state is CLOSED, because your patch checks those.
Because newly created streams cannot be CLOSED state here, the stream should be receiving second HEADERS frame on CLOSED state. This suggests that cstate.is_valid_streamid(stream_id) was true and stream == nullptr was true too.
If stream->has_trailing_header() was false an  Http2Error had been returned, but it hadn't. So the requests should have trailing headers. Can you confirm this?
If ATS sent a RST_STREAM frame before receiving trailing headers (second HEADERS frame), it would reach here with the conditions (valid stream id and closed state) because we can find the stream from stream_list. But I don't understand how it crashes with an stream that is still alive.

@maskit @shinrich and I were discussing rcv_reset_stream_frame().  It is possible that we are sending a RST_STREAM for some reason and have closed the connection, but I haven't looked into that .
The stream is not a nullptr and it is in the CLOSED state.  The header heap on the stream is nullptr and we are trying to add a header to it when we segfault.
I tested with the 8.0.x branch from a commit back on 9/8 and it also has this issue, so it has been around for awhile:
# Test 2
git co -b 8.0.x_test_2 43bb6982283832c1cc882169aef31db64d199786 # Date:   Wed Aug 8 13:40:24 2018 -0600
git cp 57b37465912d755a6299fe0f923ec0533c131e93 # protect against HEADERS frame on closed stream
git cp f2295e8355f1ee4abff357e3070fc79d1df8c86b # adds Error logs
git cp dc8d9a4656c9a299c0f39a36f2529a554de6bfd8 # local 7.1.x compatiblity layer

I will add the appropriate  comment after figuring out why this is happening.

This is a look at the Http2Stream:


Issue opening URL's

I am trying to run the tool, I filled in the URL file and the tool just keep opening yahoo for some reason.
Am I doing something wrong?

No it's working fine.. it's called referer spoofing..your views will be coming from Yahoo's


Configure RN version via Gradle property

This will not work this way because at the time of publishing to maven central, you need to have a fixed RN version set.


[Access Request] Table 83 - Item Journal Line

Hi Al team,
I would like to access the following variables from the extension object
protected var
        ItemJnlLine: Record "Item Journal Line";

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Remove Pending Tests

To ensure a cleaner build environment to test things with Vim, ensuring 100% passing tests would be needed.

This change is

Going to check this out before passing it up into the Vim universe.


Allow optional payment text in payment rows in print receipt

Up to 2 lines
Supported by ISL protocol only (Daisy prints comments)
Emulate with comments in Tremol and Datecs X

I used your consoleread function.  if I print 123, may read return ?23; I found readfile  api return buff(0) =229 ，this ls not right.  why ？ thanks


(Re)define signs/highlight on ColorScheme

Fixes https://github.com/neomake/neomake/issues/922.

@mhinz
Thanks!
It got a bit messier.. :/
Do you still approve? :)


chore: bdd-spring-1576751410 to 0.0.1

chore: Promote bdd-spring-1576751410 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Explanation text on the Worbli account creation page

We need to put the following explanation text on the Account page in the view where they are creating a new Worbli account:
Choose your desired Worbli account name (6-12 characters, must start with a letter and can only contain letters and numbers 1-5). Note: high profile trademarked names such as "google", "facebook", etc. are not allowed and accounts that have chosen such names will be frozen.


SCIM User listing and Filtering return false results when filtered or listed across all the user stores with the limit is set more than 100.

When the limit (count) is set more than 110, the expected result is to retrieve first 110 users from all user stores.
Assume a scenario with the primary has 200 users who matches the filter or for listing. When we set the count to 110, we should get 110 from primary store and it should be the end of listing or filter. But the primary store only returns 100 users. As a result pagination fails. This happens due to a property [1] declared in the user-mgt.xml.
[1] - "Property name="MaxUserNameListLength"

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


The dependency graph could not be satisfied (https://github.com/IBM-Swift/HeliumLogger.git)

I'm getting that error when trying to do
swift package generate-xcodeproj
The xcode project is not updating after adding a coachDB package dependency.
Any idea??

Can you paste your full Package.swift here please?

`import PackageDescription
let package = Package(
name: "Kitura-Starter",
targets: [
Target(name: "Kitura-Starter", dependencies: [])
],
dependencies: [
.Package(url: "https://github.com/IBM-Swift/Kitura.git", majorVersion: 1, minor: 3),
.Package(url: "https://github.com/IBM-Swift/HeliumLogger.git", majorVersion: 1, minor: 3),
.Package(url: "https://github.com/IBM-Swift/Swift-cfenv.git", majorVersion: 1, minor: 8),
.Package(url: "https://github.com/IBM-Swift/SwiftyJSON.git", majorVersion: 15),
.Package(url: "https://github.com/IBM-Bluemix/cf-deployment-tracker-client-swift.git", majorVersion: 0, minor: 6),
.Package(url: "https://github.com/IBM-Swift/Kitura-CouchDB.git", majorVersion: 0, minor: 25)
],
exclude: ["Makefile", "Package-Builder"])
`

Thanks. You've specified version 0.25 of Kitura-CouchDB which is a very old version that used a different HeliumLogger.
Change your Package.swift to specify version 1.3 of Kitura-CouchDB, then rm -rf Packages and run swift package generate-xcodeproj again.

How can I specify a minimum version and just get the latest? (kind of like cocoapods)

Swift Package Manager doesn't support that model, I'm afraid.

And how should I get notified which is the latest version? Or where can I check?

Also, do you know of any good documentation/tutorial on using CouchDB with Kitura?

Swift Package Manager versioning is based on git tags and SemVer. So, for Kitura-CouchDB you can check the releases page to see the most recent version.

Thank you very much for everything

There's a tutorial here written by @akrabat.


A problem regarding Kolnovel source

Source information
kolnovel
Steps to reproduce
I have a problem when reading from Kolnovel source. When I click on a chapter it shows some random words between every paragraph.
As in this chapter for example:

The yellow lines are the actual text in the original site. But the blue lines are just random words between every paragraph that doesn't make any sense.
This problem is not in the original source.
Here is the same chapter in the original site:
Classroom of the elite ch 144
Expected behavior
I want to read without these random words between paragraphs
Actual behavior
This problem is with all novels from this source and all chapters.
I tried some other arabic sources and it was fine.
LNReader version
1.1.15
Android version
Android 6
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 1.1.15.
[X] I have updated all installed extensions.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Might be fixed with this but i'm not sure since i can't read


Verify that live requests for multiple recommendations can be saved (Closes #23)

[ ] Install VCR gem

[ ] Create a helper that can be included in tests to use REAL login info. It should/would be included during debugging mode ONLY when running your specs (perhaps via ENV variable later)


openai_object

Confirm this is an issue with the Python library and not an underlying OpenAI API

[X] This is an issue with the Python library

Describe the bug
I am
from openai import openai_object
it reports the error:
ImportError: cannot import name 'openai_object' from 'openai'
my openai version is 1.8.0
I wonder if there exist a version problem
To Reproduce
1.from openai import openai_object
2.ImportError: cannot import name 'openai_object' from 'openai'
Code snippets
No response
OS
Linux
Python version
Python v3.8
Library version
openai v1.8.0

This has been removed from the library in v1

This has been removed from the library in v1.

So are there any other interfaces that replace this class?

The SDK has been completely rewritten, so I suggest getting familiar with the new setup. There may or may not be a directly comparable class depending on your exact needs.

how about downgrade to 0.28.0 ?


iamb causes a lot of disk write

Possibly in the mmapped ~/.config/iamb/profiles/bq/matrix/matrix-sdk-state/db, as I see no active write operations in strace.
iotop-c shows around 1 M/s write all the time.
I suppose that's not healthy for my SSD.

Confirmed this is still present in 0.0.9-alpha.1

It looks like this is rooted in the default behavior of the Sled datastore used by the matrix-sdk crate if you write to it too often.  Maybe cache more in memory and flush to disk only periodically?

Can't reproduce it on latest dev build.

Can confirm, the sled worker threads no longer show up in iotop on iamb 0.0.9-alpha.1 (999399a) and I'm not seeing elevated disk I/O.

Still seeing this on a2a708f1ae1dc8d08620f1b302b2cafb159cb40a in iotop-c

@ErrorNoInternet I updated the SDK in #200 , which now uses SQLite instead of sled. Testing on my laptop at ec81b72, I'm seeing long periods of inactivity, with the occasional spike up to ~70 K/s. Can you check if a more recent build improves things for you?

Ah I had to compile it manually with cargo and that worked. The Nix flake (nix run github:ulyssa/iamb) was out of date somehow. Seeing basically zero disk usage now :)


Type 'ImagePickerOptions' not found.

Error: Type 'ImagePickerOptions' not found.
../…/lib/image_picker_android.dart:174
ImagePickerOptions options = const ImagePickerOptions(),
^^^^^^^^^^^^^^^^^^
Error: Couldn't find constructor 'ImagePickerOptions'.
../…/lib/image_picker_android.dart:174
ImagePickerOptions options = const ImagePickerOptions(),
^^^^^^^^^^^^^^^^^^
Error: 'ImagePickerOptions' isn't a type.
../…/lib/image_picker_android.dart:174
ImagePickerOptions options = const ImagePickerOptions(),
^^^^^^^^^^^^^^^^^^

Fixed as of now.


the code

It is written in rust so I don't understand it. This is an issue. My suggestion is that you change it to better help me use this.

Deal with it.


B-21464

Agility ticket
Summary
Is there anything you would like reviewers to give additional scrutiny?
this article explains more about the approach used.
Verification Steps for the Author
These are to be checked by the author.

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Have the Agility acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

[ ] Has the branch been pulled in and checked out?
[ ] Have the BL acceptance criteria been met for this change?
[ ] Was the CircleCI build successful?
[ ] Has the code been reviewed from a standards and best practices point of view?

Setup to Run the Code

Instructions for starting storybook
Instructions for starting the MilMove application
Instructions for running tests

How to test

Access the
Login as a

Frontend

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, Edge).
[ ] There are no new console errors in the browser devtools.
[ ] There are no new console errors in the test output.
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.
[ ] This change meets the standards for Section 508 compliance.

Backend

[ ] Code follows the guidelines for Logging.
[ ] The requirements listed in Querying the Database Safely have been satisfied.

Database
Any new migrations/schema changes:

[ ] Follows our guidelines for Zero-Downtime Deploys.
[ ] Have been communicated to #g-database.
[ ] Secure migrations have been tested following the instructions in our docs.

Screenshots

Test coverage on server failed.
Last run: Thu 14 Nov 2024 03:44:48 PM UTC
Refer to this report to see coverage details for the server app.
Documentation for test coverage can be found at this link.

Test coverage on server failed.
Last run: Tue 03 Dec 2024 05:14:28 AM UTC
Refer to this report to see coverage details for the server app.
Documentation for test coverage can be found at this link.

Test coverage on client failed.
Last run: Mon 16 Dec 2024 07:26:35 PM UTC
Refer to this report to see coverage details for the client app.
Documentation for test coverage can be found at this link.


unable to confirm turso group destroy operation

turso group destroy command puts my terminal in a weird state that turns enter into ^M and Ctrl+C into ^C.
╰──> turso group destroy test-group
Group test-group, all its replicas and databases will be destroyed.
Are you sure you want to do this? [y/n]: y^M^C

killing the command process returns my terminal to the correct state.
This is on mac.

Using -y is a working workaround

Seems to be fixed now.


Documentation lacks many steps

Project did not work until

install gcloud
login gcloud with default credentials (?)
login with my account
set current project in gcloud
install ngrok

I understand in Google office you are already has the environment, but many people do not . It would be nice to add these steps to documentation

If you are using ngrok, you shouldn't need gCloud since that's only used for deploying the App Engine instance. But the README does instruct you to download the CLI if you haven't done so already.
If you're using ngork, that should be installed as a project dependency and run as part of the npm run start:local command.

have you tried without gcloud ? project fails somewhere inside smart home library
Andrew

On 12 Aug 2019, at 16:15, Nick<EMAIL_ADDRESS>wrote:
If you are using ngrok, you shouldn't need gCloud since that's only used for deploying the App Engine instance. But the README does instruct you to download the CLI if you haven't done so already.
If you're using ngork, that should be installed as a project dependency and run as part of the npm run start:local command.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Can you be more specific about where it fails, such as what error you're seeing and how you're running the sample?

Closing as obsolete.

Closing as obsolete.


Fix Ionicons vertical alignment

Just implemented the solution from https://github.com/oblador/react-native-vector-icons/issues/301#issuecomment-337564538
Closes #566 / #301

Thank you for your contribution! I however cannot accept it in the current form as I'd need you to fix the generation script instead of the actual output. Would you mind adding whatever you did to scripts/ionicons.sh?

Would you mind updating the PR or should I close it?

Hi @oblador,
Apologies for the delay. I have now updated the ionicons.sh file to handle the generation of the font file with the vertical alignment fix.

ftxdumperfuser is not a common command (Apple Font Tools Suite?), there should probably some kind of check/warning/error/documentation that can help a user to make sure all dependencies are installed?

Is there an update to this fix?

Superseded by #1484


fix fh bug in predict_in_sample of ARIMA models

Reference Issues/PRs
Fixes #1106
What does this implement/fix? Explain your changes.
check order d of _PmdArimaAdapter._forecaster_model_ (i.e. fitted ARIMA model) and get in-sample forecasts of start from d instead of 0 when start=0, and append zeros to the pred and pred_interval
Does your contribution introduce a new dependency? If yes, which one?
no
PR checklist

For all contributions

[ ] I've added myself to the list of contributors.
[ ] Optionally, I've updated sktime's CODEOWNERS to receive notifications about future changes to these files.
[ ] I've added unit tests and made sure they pass locally.

For new estimators

[ ] I've added the estimator to the online documentation.
[ ] I've updated the existing example notebooks or provided a new one to showcase how my estimator works.

Hm, I see - is your suggestion to pad with zeroes at the time points where predictions cannot be obtained, can you confirm?

Question: would the observed values not be a better choice in this case?

Hm, I see - is your suggestion to pad with zeroes at the time points where predictions cannot be obtained, can you confirm?

yes

Question: would the observed values not be a better choice in this case?

Yes, I'll modify the behavior

would you mind linting your contribution properly?
We use black, you can do this manually (e.g., look at linter output), or have a look at the contribution guidelines for setting up precommits.

@mloning  agreed. I checked the issue in pmdarima, and this should not be a problem of sktime.  But I still think the package should be able to provide in-sample forecasts for all observations, as implemented arima in R.
close the pull request and the issue.

@AngelPone I agree that we should provide in-sample forecasts, I'm not sure how this is done though, pmdarima seems like the right place to implement that, but why is the linked issue closed?

I closed it because pmdarima can't give forecasts when start<d(thus sktime can't too), and it should not be an issue in sktime. Besides, I have no idea how to solve it if padding with actual data isn't the right way.


Establish etcd/client APIs

I like the architecture overall.

@yichengq @xiang90 I addressed everything I felt was actionable. Please check back over this.

@xiang90 @yichengq this is ready

@bcwaldon I did not take a line by line review. I review the core part, and it lgtm. And we already discussed about the API. I still have a few concerns around endpoint picking and cluster updating. But it may out of the scope of this pr. it is already large enough.


tokenizer.model

I fine-tuned an llm based on the llama skeleton and used convert_hf_checkpoint and quantize to complete the quantification. However, when generating, the tokenizer.model file is missing. How can I operate or generate it?

Which model are you going to inference, if it's a Llama 3+ model, we already copied it to the right place in convert_hf_checkpoint.
https://github.com/pytorch-labs/gpt-fast/blob/c9f683edd4f89d3e81ed8f52387e866a245e3226/scripts/convert_hf_checkpoint.py#L118-L126


StarterPlayerScripts not working after I accidentally moved it out of StarterPlayer

I moved it back in and hit Play Solo.
Character obviously loaded, but none of the StarterPlayerScripts were being given to me, not even CameraScript and ControlScript!
I saved and reloaded. Problem remains. Please fix this!
Steps to reproduce:

Create new place (DON'T USE ONE OF YOUR EXISTING PLACES LOL)
Drag StarterPlayerScripts out of StarterPlayer
Drag back in
Play Solo
Watch in sheer horror as your newly spawned character has no soul to guide it.

I just did this again in a new place, it happened again.

For some reason, in Play Mode it gives me the scripts but not in Play Solo.
Just incase I'm using Play Solo I made a script to clone them incase they don't get put in automatically.

The same thing happens to me. I can't seem to find a way to fix it. I'll email<EMAIL_ADDRESS>and inform them of the issue.

This issue was moved to GitBlox/Core-Scripts#19

tHAT me cUM in u LOL.


Why not just js-ipld-eth?

hey @kumavis and @diasdavid

Why not just one module js-ipld-eth?
Is it useful to distinguish them? Maybe there's something i'm not seeing?
Having to make 6 different ipld format modules (assign a code, parsers, etc) because ethereum's data is not self-describing does not necessarily mean that it is good for developers to think of these as 6 different things.
i claim that a new developer would find more utility from a js-ipld-eth package that has all six inside, than 6 individual packages plus a seventh tying them all together.

js-ipld-eth/account-snapshot
js-ipld-eth/transaction

// vs

js-ipld-eth-account-snapshot
js-ipld-eth-transaction

(btw, i personally dont care very much :) you two know best!)

If the question is: 'multiple repos vs single repo', I'm fine either way :)
It might make it easier for @kumavis, since they share the same codebase, avoiding to create 'yet another repo' to export that shared base.
@kumavis your call! :)

sure, would likely be easier to maintain. but im not available to work on making this change atm.

This is happening! https://github.com/ipld/js-ipld-ethereum/issues/4


Finished breaking apart primary data into smaller chunks

This looks fine to me, but I'd wait until the Travis checks pass.

Changes Unknown when pulling fc6a084d11115e2ea92ad3a4b6d252eda74beb69 on thongsav-usgs:master into ** on USGS-R:master**.


feat(service): support ErrorProduces

What this PR does / why we need it:
Add ErrorProduces into Definition. ErrorProduces is used to generate data for error. If this field is empty, it stands for this field equals to Produces. In some cases, succeessful data and error data should be generated in different ways.
e.g.
An API  returns a file (Content-Type is application/java-archive), but it may returns an error with NotFound. You can set Definition as:
Produces: []string{"application/java-archive"},
ErrorProduces: []string{"application/json"},

If a file existing, the API returns a file with Content-Type: application/java-archive, and carries data by response body. If an error occurs, it returns an error json with Content-Type: application/json.
Which issue(s) this PR fixes (optional, close the issue(s) when PR gets merged):
Fixes #169
Special notes for your reviewer:
/cc @ddysher
Release note:

NONE

I have a problem if I set the return type of json type, but returned text in handle. This will find the problem at runtime or when compiling?

@zjj2wry
There are some rules:

If you returns []byte or string, there is no check for your data.
If you returns a struct, it will be converted to target data type (here is json).

@kdada there's conflict

curious how other framework handles such case? i don't recall explicitly specifying error producer while using other frameworks.

Other frameworks let yourself to judge how to write data back to response. But we have different behaviors to handle APIs. Producers must know which content type is desired. In most time, success data and error data have same content type, then a Produces is enough. But in some cases, e.g. download APIs,  They need a certain type for files and another type for errors.

/lgtm

Other frameworks let yourself to judge how to write data back to response. But we have different behaviors to handle APIs. Producers must know which content type is desired. In most time, success data and error data have same content type, then a Produces is enough. But in some cases, e.g. download APIs, They need a type for files and another type for errors.

sgtm


pattern_auto_discovery_period in pulsar.Client is not used.

This took me a little while to track down but im pretty sure its an actual bug. This seems simple enough to fix and I'd be willing to take on the PR to fix it. I've prototyped that change locally and its 1 line in the code and 1-2 lines in the unit test.
The Client class has a subscribe function. It has a parameter called pattern_auto_discovery_period
This value is unused and the value will always default to 60 seconds (because that is what is in the cpp files).
Here is a POC that shows the problem
import pulsar
import multiprocessing as M
import time
import re
import _pulsar

mode = "non-persistent" # ?? nothing received

TOPIC = f"{mode}://public/default/my-topic/whatever"
TOPIC2 = f"{mode}://public/default/my-topic/something"
TOPIC_WILD = f"{mode}://public/default/my-topic/.*"

def callback( consumer , msg ):
    print(f"Got topic {msg.topic_name()} {msg.data()}\n", flush=True)
def main():

    sub_mode = _pulsar.RegexSubscriptionMode.NonPersistentOnly

    time.sleep( 2 )
    client = pulsar.Client('pulsar://localhost:6650')
    # This topic will be found right away becuase i created it first!
    producer = client.create_producer(TOPIC)

    client.subscribe(  re.compile(TOPIC_WILD) , subscription_name="subname111",message_listener=callback ,  regex_subscription_mode=sub_mode , pattern_auto_discovery_period=100 )
    # This topic will not be found until 60 seconds into the run regardless of pattern_auto_discovery_period
    producer2 = client.create_producer( TOPIC2 )

    for k in range(0,120):
        time.sleep(1 )
        o = f"some data {k}"
        if k % 2 == 0:
            producer.send( o.encode() )
        else:
            producer2.send( o.encode() )
    client.close()
if __name__ == "__main__":
    main( )

Here is a screenshot of the pattern discovery happening at 60 seconds.

There is a unit test that is supposed to be testing for this: test_topics_pattern_consumer
However, this test has a bug as well. Since all the producers are made before the subscribe call the topics are all found right away.

        producer1 = client.create_producer(topic1)
        producer2 = client.create_producer(topic2)
        producer3 = client.create_producer(topic3) ##### MOVE THIS after the subscribe to demonstrate auto-recovery!

        consumer = client.subscribe(
            re.compile(topics_pattern),
            "my-pattern-consumer-sub",
            consumer_type=ConsumerType.Shared,
            receiver_queue_size=10,
            pattern_auto_discovery_period=1,
        )

        # wait enough time to trigger auto discovery
        time.sleep(2)

Just ran into this issue myself, are there any plans on fixing this? It's been almost a year now since it was reported.


:arrow_up: Upgrade Apache Ranger from 2.3.0 to 2.4.0

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

[X] I have searched in the issues and found no similar issues.

Why do we need to upgrade this artifact?
Regular Updates
Artifact Name
https://mvnrepository.com/search?q=ranger-plugins-common
Target Version
2.4.0
Notable Changes
https://cwiki.apache.org/confluence/display/RANGER/Apache+Ranger+2.4.0+-+Release+Notes
Are you willing to submit PR?

[ ] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to fix.
[X] No. I cannot submit a PR at this time.

Bumping Ranger to 2.4.0 solely fails 20 of all tests.
  org.apache.kyuubi.plugin.spark.authz.AccessControlException: Permission denied: user [bob] does not have [select] privilege on [default/src/key]

Please consider reopening #4585 to solve conflicts in overlapping IDs and resources in the policy file. All tests pass with new generated policy file in #4585 as it merges duplicate policies.

Closed via https://github.com/apache/kyuubi/pull/4675

Thanks for closing this issue for me.


Introduce Primary Keys for the missing tables

Description:

The following list APIM tables lack primary keys, causing replication operations to result in delays.

am_alert_emaillist_details
am_alert_types_values
am_api_scopes
am_api_scopes
mb_binding
mb_durable_subscription
mb_expiration_data
api_destination_summary
api_fault_summary
api_last_access_time_summary
api_request_summary
api_resource_usage_summary
api_response_summary
api_throttled_out_summary
api_version_usage_summary

By @chamilad from https://wso2.org/jira/browse/APIMANAGER-5939

:pinched_fingers:


Update underlying html5-template readOnly

https://github.com/advisories/GHSA-gxr4-xjj5-5px2/dependabot
Fix GitHub Advisory Database GitHub Reviewed CVE-2020-11022
Potential XSS vulnerability in jQuery

DONE.


Add Image and Text entity reading.

Code review changes made on top of PR https://github.com/vircadia/vircadia-web-sdk/pull/146 .

Tested in PR146.


⚠ Processors has degraded performance

In 9d6db8b, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 73 ms

Resolved: Processors performance has improved in 580eb5b.


EVCache Touch method throw NoSuchMethodError exception

Here are the jar files version:
EVCache Client: 4.104
spymemcached: 2.12.3
I use the EVCache.touch(key, 120000) to refresh the time. But it throws the below exception.
java.lang.NoSuchMethodError: net.spy.memcached.OperationFactory.touch(Ljava/lang/String;ILnet/spy/memcached/ops/OperationCallback;)Lnet/spy/memcached/ops/KeyedOperation;
net.spy.memcached.EVCacheMemcachedClient.touch(EVCacheMemcachedClient.java:322)
com.netflix.evcache.pool.EVCacheClient.touch(EVCacheClient.java:1099)
com.netflix.evcache.EVCacheImpl.touchData(EVCacheImpl.java:755)
com.netflix.evcache.EVCacheImpl.touch(EVCacheImpl.java:712)
com.netflix.evcache.EVCacheImpl.touch(EVCacheImpl.java:663)
...
Do I use the wrong jar files?

Nobody response. :(
I use the set to reset the data.

We are still using spymemcached-2.11.4. Can you please try with this jar?
https://bintray.com/netflixoss/maven/EVCache/4.118.0#files/com%2Fnetflix%2Fevcache%2Fevcache-client%2F4.118.0
https://bintray.com/netflixoss/maven/download_file?file_path=com%2Fnetflix%2Fevcache%2Fevcache-client%2F4.118.0%2Fevcache-client-4.118.0.pom

I fail to download the 4.118 version. Let's wait the 5.x version.

I see the jars in jcenter. We have both 4.x and 5.x here.
http://jcenter.bintray.com/com/netflix/evcache/evcache-client/

We update to 4.127. It still throws this exception. After rollback the spymemcached to 2.11.4, it's fine.


Constantly Closing

Description
Over the past several days my files app has been crashing very often.
Steps To Reproduce
It doesn't seem like it is a specific thing that is happening. What I am working on is moving documents into folders.
Requirements
Fix crash that occurs when Files closes unexpectedly.
Files Version
<IP_ADDRESS>
Windows Version
Edition	Windows 11 Home Version	23H2 Installed on	2024-06-24 OS build	22631.4169 Experience	Windows Feature Experience Pack 1000.22700.1034.0
Log File
debug.log

Thanks for the report, can you see if this is an issue in the preview version. https://files.community/download

I don't see anything in the log file, but before trying to debug this further, please let us know if it's still an issue in v3.7.6.

Using apps, preview panel open, crashing periodically.
App: <IP_ADDRESS>
Version: 10.0.19045.4894
debug.log

Does closing the preview pane solve the issue? In the event that it does, this issue is most likely resolved with #16156.

@natasha1188 @adamjameskramer


ADD new move

For example:
#include "stdio.h|"               press  "                    #include "stdio.h"|
#include <stdio.h|>             press  >                   #include <stdio.h>|
etc...

This feature was added in the latest commit 3d3ddb8cdf100f1ccc7a77c20bd4a8223a31dfa5. Thank you for the feedback.

Fix these bugs in c283288e75b83f11f9cbc227e997e02cc24ffc9c. Feel free to give me more feedback.

Oh... I see. Could you please open a new issue? This is different to the previous issues.


Unable to update container to :latest via watchtower

Checklist

[ ]  I am not using Home Assistant. Or: a developer has told me to come here.
[X] I have checked the troubleshooting section and my problem is not described there.
[X] I have read the changelog and my problem is not mentioned there.

Deploy method
Docker
Z-Wave JS UI version
<IP_ADDRESS>d7bf4
ZwaveJS version
10.5.0
Describe the bug
When running watchtower to update cointainers, I get the following error:
Could not do a head request for "zwavejs/zwavejs2mqtt:latest", falling back to regular pull.
Reason: registry responded to head request with "404 Not Found", auth: "not present"

This did not happen before. The first occurence started on Jan 28th. It seems related to these changes. For example, pihole had the same error but they fixed it. The issue also contains links to instructions on how to solve it.
To Reproduce
Set up a container with :latest via docker-compose.yaml
version: "3.7"

services:
  zwavejs2mqtt:
    container_name: zwavejs2mqtt
    image: zwavejs/zwavejs2mqtt:latest
    restart: unless-stopped
    tty: true
    stop_signal: SIGINT
    environment:
      - TZ=Asia/Singapore
    env_file:
      - ./secrets.env
    devices:
      - /dev/ttyUSB0:/dev/ttyUSB0 # Z-Wave
    volumes:
      - ./store:/usr/src/app/store
    ports:
      - "8091:8091" # Web interface.
      - "3000:3000" # zwave-js websocket server.

Set up watchtower to auto-update via docker-compose:
version: "3"

services:
  watchtower:
    image: containrrr/watchtower:latest
    container_name: watchtower
    restart: unless-stopped
    env_file:
      - ./common.env
    environment:
      - WATCHTOWER_SCHEDULE=0 0 3 * * *
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - ./run:/run

Expected behavior
Container should auto-update.
Additional context
No response

@nitobuendia Could you try using the new tag? zwavejs/zwave-js-ui:latest

@robertsLando Happy to try. I've changed the container now. However, I may not have a confirmed update until the container needs to be updated. Thanks!

@nitobuendia You are welcome! Feel free to reopen in case the bug persists. BTW I neer used watchower my own so I dunno what could be the root cause as long as a docker pull works

@robertsLando I believe the issue comment I linked addresses that:

This is due to a new format of the manifest that is produced with the new version of docker buildx. (...) If you are responsible for creating said image, you can look at the upstream bug for ways to opt-out of the unsupported manifest until it's supported: https://github.com/docker/buildx/issues/1509#issuecomment-1378538197

You can see an example on how this was handled for a different container like pihole.
In any case, I will update with the results as stated.

So the fix should be as easy as: https://github.com/pi-hole/docker-pi-hole/pull/1290/files

this is an issue with watchtower
disabling provenance is an ugly workaround.
If watchtower don't want to fix it, then I'd suggest looking at an alternative.
suggest we close this ticket
from a philosophical basis, while @robertsLando and co work super hard to keep things stable, I'd suggest you might not want to auto update the runtime. you'd be better with using something like renovate to keep your docker compose manifest files updated with pinned releases, then you'll always have a history of what was running rather than letting watchtower autoupdate the runtime

Thanks for the follow up @chrisns 🙏🏼

@robertsLando This seems to work fine with the new image. It updated today with no issues.


#34610 Fix invalid range "t-5" in string transliteration [iOS]

Fix invalid range "t-5" in string transliteration [iOS] for M1 pod install issue.
Summary
This should fix pod install error for M1 machines.
Changelog
[iOS] [Fixed] - Fix ios pod install error
Test Plan
Run pod install on M1 machine.

Hi @Romick2005, thanks for fixing this issue. I left a comment with a suggestion to improve readability. Please, update also the tests.

Hi @cipolleschi, thank you for review! Done some changes to make you happier!


Add a config flash.use_autoscaler_without_s3

What problem does this PR solve?
Issue Number: ref https://github.com/pingcap/tiflash/issues/6827
Problem Summary:
Caused by https://github.com/pingcap/tiflash/pull/7110
Some environment has deployed auto scaler without running S3, we need a special config when upgrading
What is changed and how it works?
Add a config flash.use_autoscaler_without_s3, default is false.
When tiflash deployed with config as following, it will still handle the disagg request by ExchangeSender/ExchangeReceiver rather than reading from S3.
...
flash.use_autoscaler: true
flash.use_autoscaler_without_s3: true
...

Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/merge

/merge

/run-integration-test

/rebuild

/run-integration-test

/merge

/merge

/run-integration-test

/merge


kwctl run: handle new context aware policies

We have formalized how context aware policies have to be handled with this new RFC.
As a result of that, we have to change how kwctl run handles context aware policies.
By default, when running a context aware policy, kwctl will not allow the policy to access Kubernetes resources.
The user can allow access to Kubernetes resources by using a new boolean flag --allow-context-aware. When this flag is enabled the policy will be granted access only to the resources mentioned inside of its metadata (the new contextAwareResources data).
Admission criteria
When running a policy that has contextAwareResources inside of its metadata:

By default:

[x] Do not allow access to any Kubernetes resource (basically run the policy with an empty allow list)
[x] Print a warning message stating that the policy uses context aware data, but it will not have access to it. Hint the usage of the --allow-context-aware flag

When using the --allow-context-aware flag:

[x] Print a big warning stating which Kubernetes resources the policy will have access to
[x] Allow access only to the resources mentioned inside of the contextAwareResources field of policy's metadata

Done via https://github.com/kubewarden/kwctl/pull/431


docs: use mkdocs and document pr/mr workflow

To test this PR run
docker run --rm -it -p 8000:8000 -v ${PWD}:/docs squidfunk/mkdocs-material

And go to localhost:8000 in you web browser

Codecov Report

Merging #122 (b483761) into main (67f845f) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##             main     #122   +/-   ##
=======================================
  Coverage   45.08%   45.08%
=======================================
  Files          23       23
  Lines        1546     1546
=======================================
  Hits          697      697
  Misses        822      822
  Partials       27       27

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


multi-lined download status

A PR for getting a multi-line download status: Expect to see something like this on downloading Chromium for supported platforms:
Create directory structure
========
Downloading browser for mac      16%
Downloading browser for win      11%
Downloading browser for linux     7%
========

@Mogztter - it basically works, still some fine tuning necessary => move cursor after download status-lines when finished OR -- perhaps better -- change PRE/POST condition in such a way, that cursor is at line after multi-line area. So that further logs to come will not overwrite status-line area.
Nonetheless, it basically works.

Just a minor, while important, improvement:
Create directory structure
===========================
Downloading browser for mac      16%
Downloading browser for win      11%
Downloading browser for linux     7%
===========================
^

TTY cursor is now a position indicated by caret (^) after each status line update. Whatever happens then, this modification ensures that follow-up log statements within the TTY are not overwriting the update-status block. One notable exception though would is of course kill -9, i.e. process killing.

@Mogztter - this PR supersedes #488, however, there is no dependency on #488. So we can drop #488 in favor of this one.

Thanks, I will give it a try on my macOS laptop 🍎

It's working great but using a single line is probably less confusing (especially if you press  in the terminal):
Downloading browser [mac:  1%]

Downloading browsers [linux:  1%, mac:  1%, win:  1%]

@Mogztter - proper single-line download status now, I guess ready to be merged with master.
Btw, I wonder what the best GIT strategy now is. My approach would be:

rebase this branch on master (i.e. change git history is such a way as if this branch has been taken from current master), resolving potential merge conflicts while doing so.
Squash commit on this branch into one commit
merge (done by you)

Is that the right way to do?

@wh81752 Yes, you can use an interactive rebase: git rebase -i origin/master (in this case, origin is https://github.com/Mogztter/asciidoctor-web-pdf) to squash all commits. You can also reword the first commit (while doing the rebase) to accurately describe what you did.
Then, force push on your branch. You need to force push because commits have changed.
If all goes well, you will have a pull request with a single commit.

@Mogztter  - here we go,  ready to merge.###

Thanks and merged!


Separate ios launch

Switch to using the now-published-separately idevice-app-launcher package for launching iOS apps. This includes a fix that means we properly stop the app if it runs into native crashes rather than keeping the phone stopped in the debugger, and we also now bubble up those crashes to the BuildInfo so be reported to clients if they ask.

Minor comments. LGTM!

:+1:


Correct way of measuring free5gc UPF throughput with iperf ?

Hi,
I am trying to measure the throughput of UPF alone with iperf any one help me.
Thanks.

@mohammedyaqub
I think the method of https://github.com/free5gc/free5gc/issues/360 should be work for your case.
Thanks.


fix: remove xml cache

What does this PR do?
module-scope cache causes problems for long-lived IDE usage.  this just removes it (goal is to compare the perf tests for EDA, which has a lot of decomposed stuff, to see if it matters at all)
What issues does this PR fix or reference?
@W-15952068@

the xml cache was specifically for CustomLabels. Create a project with 2000 CustomLabels and do a convert. You'll see the perf difference. With each individual custom label the entire CustomLabels file is re-read so performance, especially on windows, is pretty terrible without the cache.

the perf tests agreed with you 😄 .  I wanted to see.  Closed in favor of https://github.com/forcedotcom/source-deploy-retrieve/pull/1348


Fix acl lint issues

There is a ton of lint/vet fixes in this PR. There is still one left, as that one is in a dependency and not in sarama.

🤔Looks like CI failure is legit.

Yup, this is where error is coming from, I only changed bunch of names -> https://github.com/Shopify/sarama/pull/1393/files#diff-39b065607d3d0839bdc97f997d6a430cR469
Maybe I changed something else, will try to fix it in next couple days :)

No idea why the test is failing, also PR is too big. Gonna close it and then bring these changes in smalls chunks.


Don't Merge! PR real time test for source branch full build

Docs Build status updates of commit fb9a1b5:
:clock10: Full build: the average full build time is 5 min(s) 58 sec(s), this is based on the last 642 build(s) for this repository.

Docs Build status updates of commit fb9a1b5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


fix: fixed inconsistent text alignment

Notes for Reviewers
This PR fixes this issue (not sure why the issue was created in a different repository)
Files modified

site/src/components/Faq/faqSection.style.js
site/src/components/Faq/faqSection.style.js

Signed commits

[x] Yes, I signed my commits.

Let me know if I missed something!

The commit is gpg signed, not sure why the DCO is failing:


Use this library for the Home Assistant project

I think it is easy to implement things like 'battery' and 'device_tracker' for VanMoof into Home Assistant with this library. https://www.home-assistant.io
I have some experience with developing an integration in HA. Maybe we can pull this off, what do you think?

I would be in huge favor for this! I've been thinking about making a pi somewhere close to where i park my bike and then with the help of this code and mqtt send this to my HA instance. However im not sure if the pi will just connect once the bike is within reach and start sending as only 1 app can be connected and i would like to use my moofer app as well. Or could it be possible to make the data being pulled from the Vanmoof servers ? that would be the optimal solution

any progress perhaps? i'm able to connect my vanmoof with an esp-board and esphome and get some data, but I haven't got a clou to use it for Home Assistant

What data where you able to extract? With an mqtt component or directly through esphome we can fetch the data to ha and create some sensors

[12:25:24][I][ble_client:170]: Service UUID: 0x1800
[12:25:24][I][ble_client:171]:   start_handle: 0x1  end_handle: 0xb
[12:25:24][I][ble_client:383]:  characteristic 0x2A00, handle 0x3, properties 0xa
[12:25:24][I][ble_client:383]:  characteristic 0x2A01, handle 0x5, properties 0xa
[12:25:24][I][ble_client:383]:  characteristic 0x2A04, handle 0x7, properties 0x2
[12:25:24][I][ble_client:383]:  characteristic 0x2AA6, handle 0x9, properties 0x2
[12:25:24][I][ble_client:383]:  characteristic 0x2AC9, handle 0xb, properties 0x2
[12:25:24][I][ble_client:170]: Service UUID: 0x1801
[12:25:24][I][ble_client:170]: Service UUID: 6ACC5500-E631-4069-944D-B8CA7598AD50
[12:25:24][I][ble_client:171]:   start_handle: 0xd  end_handle: 0x1a
[12:25:24][I][ble_client:383]:  characteristic 6ACC5501-E631-4069-944D-B8CA7598AD50, handle 0xf, properties 0x2
[12:25:24][I][ble_client:383]:  characteristic 6ACC5502-E631-4069-944D-B8CA7598AD50, handle 0x11, properties 0x8
[12:25:24][I][ble_client:383]:  characteristic 6ACC5561-E631-4069-944D-B8CA7598AD50, handle 0x89, properties 0x52
[12:25:24][I][ble_client:383]:  characteristic 6ACC5562-E631-4069-944D-B8CA7598AD50, handle 0x8c, properties 0x5a
[12:25:24][I][ble_client:383]:  characteristic 6ACC5563-E631-4069-944D-B8CA7598AD50, handle 0x8f, properties 0x52
[12:25:24][I][ble_client:383]:  characteristic 6ACC5564-E631-4069-944D-B8CA7598AD50, handle 0x92, properties 0x5a
`

Can the data be used for calculating battery status etc?

update: i gave up the idea of using an esp-board and bought an old pi and I managed to periodically read the battery status in home assistant with this addition https://github.com/thomasbaetge/Vanmoof-MQTT

I'm also interested in that! I am currently trying to figure out if the connection is stable enough to get the data consistently out of the bike. The 1.8.1 sleep feature seems to break that idea without manually turning on the bike or just using the bike in general.

True, to fix that I also added a automation to switch on/off the power supply to wake up the bike. As long as it is plugged in, I can now automatically check and charge during the night

Any update on this? Did anyone got it working?

I used an esp-wroom-32 board to scan for Bluetooth devices and read the MAC adress of the bike than used an BLE client sensor to read the data.

@speedy-c Can you provide any details on this?

I didn't save the original yaml but I use https://esphome.io/components/sensor/ble_client.html  which resulted in the follow logfile. Hope this helps.
[17:43:16][C][ble_sensor:019]: BLE Sensor 'VanMoof battery level'
[17:43:16][C][ble_sensor:019]:   State Class: ''
[17:43:16][C][ble_sensor:019]:   Unit of Measurement: '%'
[17:43:16][C][ble_sensor:019]:   Accuracy Decimals: 0
[17:43:16][C][ble_sensor:019]:   Icon: 'mdi:battery'
[17:43:16][C][ble_sensor:020]:   MAC address        : ----
[17:43:16][C][ble_sensor:021]:   Service UUID       : 0x180F
[17:43:16][C][ble_sensor:022]:   Characteristic UUID: 0x2A19
[17:43:16][C][ble_sensor:023]:   Descriptor UUID    : 00000000-0000-0000-0000-000000000000
[17:43:16][C][ble_sensor:024]:   Notifications      : NO
[17:43:16][C][ble_sensor:025]:   Update Interval: 60.0s
[17:32:10][D][esp32_ble_tracker:723]: Found device ----- RSSI=-77
[17:32:10][D][esp32_ble_tracker:744]:   Address Type: RANDOM
[17:32:10][D][esp32_ble_tracker:746]:   Name: 'ES3------'
[17:49:01][I][ble_client:085]: Attempting BLE connection to -----
[17:49:01][I][ble_sensor:033]: [VanMoof battery level] Connected successfully!


feat(remix-dev,remix-serve): include publicPath in server build manifest

in dev we already read the config, so just pass config.publicPath and config.assetsBuildDirectory along to remix-serve to use, in production we'll read the buildPath in remix-serve/cli.ts and pass those same fields, but this time from the build itself

Looks good, we don't really have testing setup for remix-serve (in dev or production), how did you verify this all works?
Any idea why some of the tests are failing?

confirmed running locally using node ... works both in development (both remix watch and remix dev) and production

published an experimental (0.0.0-experimental-6f3ef540b) and it works


Remove deprecate_constant to separate method

The deprecate_constant method has only been moved to ActiveSupport::Deprecation::DeprecatedConstantAccessor in ActiveSupport5.2. This means that Rails versions prior to 5.2 will not be able to use SolidusSupport versions >=0.8.0.
Related Issue: #54

@Azeem838 Rails 5.2 has not been supported for a while now, so I'm closing this issue, but I'm happy to reopen in case this is still a problem 👍


excel to json

@mnoergaard I'm guessing the example shows a 'typical' way people would have previously encoded meta data?  can write a short matlab code that write this as json

done


ENH make change percentiles plot to histogram

This PR should address the plotting concerns in #94, including:

change the plot to a histogram
add title to the chart
label axes
remove plotly tools (I do not think panning or zooming are particularly useful on this plot)

Sample below:

Note that it seems git's diffing algorithm gave some weird results starting around 398/433 starting with function updateSimilarity(similarityData, state){ . To the best of my knowledge, I did not modify anything below that.

Thanks!!

@justinshaffer, what do you think about this plot type for alpha diversity?

Feedback from the comms team:
"

Can the labels be things like “richness” or “evenness” or “diversity” and have those clearly laid out to what that is in the text?
The axis is labeled Relative Frequency but the paragraph talks about Relative Abundance & diversity value. This seems to be introducing a new concept not yet explained
The axis label Faith’s PD makes it challenging to understand what it is referring to. Perhaps use Faith’s Phylogenetic Diversity as a subheading with Richness as the main axis title.

I get that the participant is supposed to see what their alpha-diversity is compared to the two countries that were studied. I just don’t get the how or what it means in comparison. They need to be able to walk away knowing how the information provided directly relates to them and how to interpret it with the least information given as possible."

@wasade Thanks! I think it's clear and looks good. I'm not sure what the rate of histogram-understanding is, so I suggest to make things super clear, for example by changing the x-axis label to 'proportion of individuals', or even better to percentages, and the y-axis to additionally include a second line of text or similar, that clarifies lower values are less diverse and higher values are more diverse (e.g., "<-- lower diversity / higher-diversity -->"). It's also tempting to place additional markers other than 'You' for fun, but I understand using things implying 'sick' or 'healthy' is dangerous. But what about the average for like, healthy infants or something - just to highlight that increases in Faith's PD are associated with age, at least early on? Just thoughts - I think it's good as is!

@gwarmstrong, any update here?

Here are some updates to the wording on the plot!

Looks great, George!
Is there a way to include the metric name in the x-axis title above or
below what you have currently? Or is the metric name now in the plot title
(e.g., 'Richness')? If that's the case I think it works as is!
Justin
On Thu, Mar 11, 2021 at 2:46 PM George Armstrong @.***>
wrote:

Here are some updates to the wording on the plot!
[image: Screen Shot 2021-03-11 at 2 45 42 PM]
https://user-images.githubusercontent.com/19470970/110865459-80970780-8278-11eb-9d16-c4f8386d65ed.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/biocore/microsetta-interface/pull/97#issuecomment-797100328,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADSDCGH5AWFM64KOJ7SH72LTDE23ZANCNFSM4YVXQHAA
.

--
Justin Shaffer, PhD
IRACDA Postdoctoral Fellow
Rob Knight Group
Department of Pediatrics, School of Medicine
University of California, San Diego
justinshafferbio.wordpress.com

The metric is Faith's PD. I could Include it in the x axis title, like so:

Hi George,
Thanks! I think that is more clear.
Sorry if I'm providing contradicting suggestions, but I think the title
should read 'Microbial Alpha-Diversity by Country', as my understanding is
that richness and Faith's PD are both distinct alpha-diversity metrics. I
think species richness is technically defined as 'the count of the number
of species', so could be equivalent to 'observed_otus' or
'number_of_distinct_features', and when visualizing those metrics I think
we should use 'richness' in their place. I think many folks may use
'alpha-diversity' and 'richness' interchangeably, and arguably for this
type of education it might be better to lean on the side of 'easier to
understand' than 'technically correct'. It's probably worth getting other's
opinions as I'm a stickler for terminology and jargon.
Justin
On Thu, Mar 11, 2021 at 4:32 PM George Armstrong @.***>
wrote:

The metric is Faith's PD. I could Include it in the x axis title, like so:
[image: Screen Shot 2021-03-11 at 4 31 55 PM]
https://user-images.githubusercontent.com/19470970/110873765-539e2100-8287-11eb-915f-5ce7529c1cd3.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/biocore/microsetta-interface/pull/97#issuecomment-797149185,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADSDCGGZQKS42HGOGDXDTVTTDFHKBANCNFSM4YVXQHAA
.

--
Justin Shaffer, PhD
IRACDA Postdoctoral Fellow
Rob Knight Group
Department of Pediatrics, School of Medicine
University of California, San Diego
justinshafferbio.wordpress.com

All good! I think that explanation makes sense. Here is the plot produced with the latest updates:

Awesome! Looks great. Nice work!
On Thu, Mar 11, 2021 at 5:02 PM George Armstrong @.***>
wrote:

All good! I think that explanation makes sense. Here is the plot produced
with the latest updates:
[image: Screen Shot 2021-03-11 at 5 01 11 PM]
https://user-images.githubusercontent.com/19470970/110875971-7a5e5680-828b-11eb-92f7-47bf2b13939d.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/biocore/microsetta-interface/pull/97#issuecomment-797159472,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADSDCGFML4U56WMC64MC5HDTDFKYPANCNFSM4YVXQHAA
.

--
Justin Shaffer, PhD
IRACDA Postdoctoral Fellow
Rob Knight Group
Department of Pediatrics, School of Medicine
University of California, San Diego
justinshafferbio.wordpress.com

Thank you both!!! This is great!

While we're here, I do want to make one more plug for cumulative density. In the cumulative histogram below, compared the histograms shown so far, someone can much more easily see the percentage of samples that have a higher/lower alpha diversity compared to their sample, by looking at the y coordinate of their "You" line. E.g., this sample's alpha diversity is greater than about 60% of US samples and ~55% of UK samples, which at least more directly answers a question I might have when looking at this plot. It is pretty hard to get this from the probability density histogram. Also, the plot is just prettier when the alpha diversity values are not present in all bins (e.g., left tail of the histograms shown above).
@justinshaffer any ideas on how we could make the cumulative density aspect more approachable for general participants?

One concern I have here is the cumulative plots don't align on the right side which makes it look like an artifact of the visualization, although I agree it is prettier in that it is smoothed. Is the histogram possible to express with some type of smoothing function maybe?

Hi George,
Sure thing!

Yes why are the colors not aligned on the right-hand side of the plot?
Does this matter?
I agree with everything you said re: this being much easier to pull
something meaningful out of. Sorry this may be dumb but I don't look at
these often - is it really the case that 60% of the blue data is to the
left of the 'You' line - rather than to the right of it? I'm squinting my
eyes and I think the left-hand tails are artifactually making the left-hand
part of each dataset seem smaller than what is on the right-hand side.
I think all we would need to include with this figure for folks to
understand is a small bit of text describing essentially what you already
wrote - you could squeeze this into the x-axis label if preferred -
something like: 'For each country, the point where your line crosses the
curve indicates the % of people whose samples are less diverse than yours!'

Justin
On Fri, Mar 12, 2021 at 10:31 AM George Armstrong @.***>
wrote:

While we're here, I do want to make one more plug for cumulative density.
In the cumulative histogram below, compared the histograms shown so far,
someone can much more easily see the percentage of samples that have a
higher/lower alpha diversity compared to their sample, by looking at the y
coordinate of their "You" line. E.g., this sample's alpha diversity is
greater than about 60% of US samples and ~55% of UK samples, which at least
more directly answers a question I might have when looking at this plot. It
is pretty hard to get this from the probability density histogram. Also,
the plot is just prettier when the alpha diversity values are not present
in all bins (e.g., left tail of the histograms shown above).
@justinshaffer https://github.com/justinshaffer any ideas on how we
could make the cumulative density aspect more approachable for general
participants?
[image: Screen Shot 2021-03-12 at 10 19 45 AM]
https://user-images.githubusercontent.com/19470970/110981851-a2e26100-831c-11eb-8600-22bc73c611d7.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/biocore/microsetta-interface/pull/97#issuecomment-797672668,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADSDCGADCX6IA266SPIJ4QDTDJFX3ANCNFSM4YVXQHAA
.

--
Justin Shaffer, PhD
IRACDA Postdoctoral Fellow
Rob Knight Group
Department of Pediatrics, School of Medicine
University of California, San Diego
justinshafferbio.wordpress.com

Yes why are the colors not aligned on the right-hand side of the plot? Does this matter?

I had not figured out a way to extend the colors to the right for a cumulative histogram in Plotly yet. I can work more on figuring this out if it matters, but if it is not supported by Plotly then the this ticket gets a lot more open-ended.

I agree with everything you said re: this being much easier to pull something meaningful out of. Sorry this may be dumb but I don't look at these often - is it really the case that 60% of the blue data is to the left of the 'You' line - rather than to the right of it? I'm squinting my eyes and I think the left-hand tails are artifactually making the left-hand part of each dataset seem smaller than what is on the right-hand side.

So the "left seeming smaller than the right" might be confounding area under the curve. It is not necessarily the case that 60% of the are under the cdf is left over the 'You' line. Instead, the blue USA bar having a height of 60% at the 'You' line indicates that 60% of samples from USA have an alpha diversity <= the x-value at the 'You' line. The height of the bar is cumulative frequency, not a count of samples.

That makes sense - thanks for the clarification!
On Tue, Mar 16, 2021 at 12:15 PM George Armstrong @.***>
wrote:

Yes why are the colors not aligned on the right-hand side of the plot?
Does this matter?
I had not figured out a way to extend the colors to the right for a
cumulative histogram in Plotly yet. I can work more on figuring this out if
it matters, but if it is not supported by Plotly then the this ticket gets
a lot more open-ended.
I agree with everything you said re: this being much easier to pull
something meaningful out of. Sorry this may be dumb but I don't look at
these often - is it really the case that 60% of the blue data is to the
left of the 'You' line - rather than to the right of it? I'm squinting my
eyes and I think the left-hand tails are artifactually making the left-hand
part of each dataset seem smaller than what is on the right-hand side.
So the "left seeming smaller than the right" might be confounding area
under the curve. It is not necessarily the case that 60% of the are under
the cdf is left over the 'You' line. Instead, the blue USA bar having a
height of 60% at the 'You' line indicates that 60% of samples from USA have
an alpha diversity <= the x-value at the 'You' line. The height of the bar
is cumulative frequency, not a count of samples.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/biocore/microsetta-interface/pull/97#issuecomment-800536060,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADSDCGHV7WYFSCIWR7VAGGTTD6U6NANCNFSM4YVXQHAA
.

--
Justin Shaffer, PhD
IRACDA Postdoctoral Fellow
Rob Knight Group
Department of Pediatrics, School of Medicine
University of California, San Diego
justinshafferbio.wordpress.com

It would be nice to have this merged as it's one of the few result types we have for skin/oral samples. please let me know if this will be completed or if it should be closed off


Update roadmap.md

Update roadmap, mark ExpansionTile as done (in https://github.com/flet-dev/flet/pull/2140)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Roadmap will be updated as part of https://github.com/flet-dev/website/pull/177


[Agent] fix intercept class package name  is incorrect

Please answer these questions before submitting pull request

Why submit this pull request?
[x] Bug fix
[ ] New feature provided
[ ] Improve performance

Coverage remained the same at 19.513% when pulling 66e3eb0765913be0c918686c6472fc50cc52e739 on ascrutae:fix/toolkit-issue into 7f83f4278921fa29f901868c0d4db0813defa9d3 on apache:master.


[Example] ggml: fix error about empty stream-stdout

Hello, I am a code review bot on flows.network.
It could take a few minutes for me to analyze this PR. Relax, grab a cup of coffee and check back later. Thanks!

Change merge target to dev branch.


Replace no longer maintained, or hijacked http://extension.remotedev.io

Hello,
Looks like the advertised http://extension.remotedev.io/ domain has been hijacked or is no longer being maintained, at least from my location in Germany. Right now, it loads an OnlyFans page, probably not the intended browser extension to be installed 😄

Haha yikes 😄 Thanks, wasn't aware of it, will fix


Document offboard / straight pass through startup

This will be popular for ROS users.
Sending:
set_actuator_control_target
Receiving:
rc_channels

Being implemented here: https://github.com/PX4/Firmware/pull/3433
@julianoes This serves as interface of the Snapdragon Flight to hardware

Still needed?

We just need to document it. It has been working for ages.

I would vote to remove it since Snappy now supports PWM output and Spektrum input and it's kind of a clunky setup.

The offboard actuator control interface, even if not used for Snapdragon is very popular with ROS people and others who implement their controllers offboard.

@mhkabir fair enough :)

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 30 days. Feel free to reopen this issue if you deem it appropriate.
(This is an automated comment from GitMate.io.)


Update exported games to use non-deprecated url

https://lichess.org/api#operation/apiGamesUser

#254 fixes this.


Wrong owner address of a Token account?

I wrote the following function to get the current owners of an NFT token
async function getOwners(connection: Connection, mint: string) {
    const pubKey = new PublicKey(mint);
    let rawData = await connection.getTokenLargestAccounts(pubKey);

    let data = await Promise.all(
        rawData.value.map(async (v) => {
            let info = await connection.getAccountInfo(v.address);
            return {
                address: v.address.toString(),
                owner: info.owner.toString(),
                amount: v.uiAmount,
            };
        })
    );
   return data;
}

When I call ie.g. with mint = "5Nt1LMqbdJcJxxTAVgrB2ToND4dbcirBNfqSiWvtWFH7" I get the following result
[
    {
        address: "DGma6jkfapL9S1fA7KXqdbq8CQ3jexMQQohcEePy49zg",
        owner: "TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA",
        amount: 1,
    },
    {
        address: "GRc8SkMHd6vrGRACrVU171iWL4xH8nLT342xZrhQmpR1",
        owner: "TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA",
        amount: 0,
    },
];

I can see in Solana explorer for example that the owner of DGma6jkfapL9S1fA7KXqdbq8CQ3jexMQQohcEePy49zg is BLPJzsS4PBNoR1LSff2tvPxpeepj2NKopMqRd684xcbB which is what I expect.
Sorry if the issue is just a confusion of my part. Appreciate if you could redirect me to the right channel if so.

Try this instead
let info = await connection.getParsedAccountInfo(v.address);
const owner = info.value.data.parsed.info.owner;

It woks! Thanks!


USE GET Method , parameters : testEmptyArray=[] .

USE GET Method , example: parameters : testEmptyArray=[] . <-- if empty array, never extend to collect , is bug?
print screen:
https://www.dropbox.com/s/kufkxw3dc54s8fg/螢幕截圖 2015-08-04 23.33.19.jpg?dl=0

I tested this and it worked fine.
let task = HTTPTask()
task.GET("http://vluxe.io", parameters: ["array": []], completionHandler: { (response: HTTPResponse) in
    println("response is \(response.description)")
})

I am not sure how you are getting that error, can you share any sample code?

yes, it worked, but different with browser future.
test.php:
if (empty($_GET['data'])){
	print_r("data is null");
}else{
	print_r("data len: ".count($_GET['data'])."
");
	for($i = 0; $i < count($_GET['data']); ++$i) {
		print_r("[$i]: ".$_GET['data'][$i]."
");
	}
}

Browser Test ：
request: http://yafeeling.azurewebsites.net/test.php?data[]
response:
**data len: 1
[0]: **
SwiftHttp:
response : data is null
(should be： data len: 1 right?)
func testGetRequest() {

        let request = HTTPTask()
        request.GET("http://yafeeling.azurewebsites.net/test.php", parameters: ["data":[]], completionHandler: {(response: HTTPResponse)  in
            if let err = response.error {
                println("Failure")
            }
            if let data = response.responseObject as? NSData {
                let str = NSString(data: data, encoding: NSUTF8StringEncoding)!
                println("str:\(str)") //output: data is null
            }
        })

    }

Ah I see. It doesn't send the empty array like you are expecting. It doesn't send the key as it doesn't have any values in it. I guess I could see how that might not be the desired behavior in some cases, but in others it makes sense, don't send a value you don't need. I will keep it in mind as I work on the Swift 2 changes.

thank you .
the project is good.
really appreciate it

Can this be reopened? Unfortunately, some APIs have strict request parameters that may require an empty array. Rather than changing multiple APIs/putting in requests for them to change to remove keys which have no values (which I would ideally want!) - I think it may be a good idea to allow this in yours.
Thumbs up on everything else though, I love it :)

yeah that is a fair point. I believe the best option would be a setting that is checked when serializing to do whichever is needed.

I add a way to do this in version 3.0.0 (just released). At the beginning of your app set:
HTTPParameterProtocolSettings.sendEmptyArray = true

and an empty array will be sent along if the array value doesn't have anything in it.


User/Pass

I cloned the repository but I don't know what the password is...
help me

yes

I suggest starting here https://webmin.com/docs/modules/webmin-users/#:~:text=A standard%2C out-of-,that is all you need.
This module doesn't touch auth or users