Add jet CLI for Linux

https://documentation.codeship.com/pro/getting-started/installation/
Here's the script > https://github.com/Adron/datadiluvium/blob/master/setup.sh

Done.


This seems like a downgrade in usability compared to fnm :((

1. How can i view the versions that i already installed without looking in ~/.config/nvm?
fnm showed these by running it without any argument if i remember correctly (unlike fnm/nvm ls which lists all available versions)
2. How can i remove an installed version of node?
Unlike fnm, the new nvm does not have a rm option anymore :(

Why do you need to know versions you've installed before?
What do you need rm for?

I need to know the versions i installed before so that i can remove them after i don't need them anymore - e.g. after i install a newer version (with nvm use) and i test that my projects work fine with it so i don't need the older one anymore.
See my answer to 1. above: i need rm to remove a version that i don't need anymore. Otherwise node installations will just pile up in the ~/.config/nvm folder. I thought it makes sense that if a tool provides the possibility to "install" something, it should also provide the possibility to "uninstall" it, not leaving the user with navigating folders to remove binaries and update config files (fortunately as far as i realise there's no need for the latter with nvm as nvm use will update the path so then any older version can just be removed manually from the ~/.config/nvm/ folder).

Anyway, fnm had close to perfect usability. I never understood all the renaming and dropping of arguments (rm, list installed versions) that took place :(

I said "installed" above. Should've said, "used".

@padurean i need rm to remove a version that i don't need anymore

Don't need it? Forget it! Node.js releases are tiny in relation to my storage capacity so I don't have to worry about removing previously downloaded releases while using this program.
I don't care about versions I've used before, because I never remove them. I've never needed that level of granularity. I nvm use the version I want to switch to and that's it.
If I really wanted to, I could rm -rf ~/.config/nvm, or if I had enough of nvm I'd uninstall it, going back to system node (had there been one).

FYI the previous fnm kept a cache in ~/.cache/nvm`, so your downloads still "piled up".

@padurean ...not leaving the user with navigating folders to remove binaries and update config files as the only options

Options for...? Elaborate, please. I've never done that, so you may have been inadvertently wasting your time.

@padurean I'm happy to keep the conversation going, so feel free to add your comments when you have time.
I'm closing since there's nothing actionable here, we're just exchanging opinions.


False Positive on tomcat-embed-core-9.0.52.jar for CVE-2020-0822

CVE is for the Windows Language Pack Installer of Tomcat which is clearly not part of tomcat-embedded which SpringBoot uses.
See https://nvd.nist.gov/vuln/search/results?form_type=Advanced&results_type=overview&search_type=all&cpe_vendor=cpe%3A%2F%3Aapache&cpe_product=cpe%3A%2F%3Aapache%3Atomcat&cpe_version=cpe%3A%2F%3Aapache%3Atomcat%3A9.0.52
Using 6.3.1
File Path: /Users/cbrunott/.gradle/caches/modules-2/files-2.1/org.apache.tomcat.embed/tomcat-embed-core/9.0.52/501d876042f7bff64ee42cf1849e4abea272632/tomcat-embed-core-9.0.52.jar
MD5: 1bb013f4deebe5f534ea1764aed6173d
SHA1: 0501d876042f7bff64ee42cf1849e4abea272632
SHA256:202e66bbf8b1ba9bd769dbcb8e850d2aa1999a065a1cb4e81058864e5e533b3e
Referenced In Projects/Scopes:
...

Evidence
Identifiers

<EMAIL_ADDRESS>(Confidence:Highest)
    cpe:2.3:a:apache:tomcat:9.0.52:*:*:*:*:*:*:*  (Confidence:Highest)

cpe:2.3:a:apache_software_foundation:tomcat:9.0.52:*:*:*:*:*:*:*  (Confidence:Highest)  cpe:2.3:a:apache_tomcat:apache_tomcat:9.0.52:*:*:*:*:*:*:*  (Confidence:Highest)

https://bz.apache.org/bugzilla/show_bug.cgi?id=65517 as stated in the bug the security reporter corrected is report.
I'm hoping they will fix the CPE in the next few days. It did feel weird that a security researcher from a SCA/SAST provider raise such false positive, might be a legetimate error or some way to sell their product.

no response from my mail BUT


Upgrade JARs for improved security

Looks like there is a sync issue:
https://travis-ci.org/airbnb/reair/builds/498332051?utm_source=github_status&utm_medium=notification
reports a successful build.


Add setting to validate rows against an XSD

This adds a new configuration rowValidationXSDPath, which gives a path to an XSD file. If specified, this is used to validate the XML of each row. If validation fails, the row is considered 'corrupt' and handled as usual.
This does not affect the schema inferred by or specified for XML parsing. It can be used for finer-grained validation beyond simple schema checking.
See https://github.com/databricks/spark-xml/issues/224 for some discussion.
One open question is: is a path to a file the best API? support general URIs?

Codecov Report

Merging #419 into master will increase coverage by 0.05%.
The diff coverage is 93.75%.

@@            Coverage Diff             @@
##           master     #419      +/-   ##
==========================================
+ Coverage   87.95%   88.01%   +0.05%
==========================================
  Files          14       14
  Lines         772      784      +12
  Branches       65       66       +1
==========================================
+ Hits          679      690      +11
- Misses         93       94       +1

Impacted Files
Coverage Δ

...ain/scala/com/databricks/spark/xml/XmlReader.scala
61.29% <0%> (-2.05%)
:arrow_down:

...la/com/databricks/spark/xml/util/InferSchema.scala
89.17% <100%> (+0.35%)
:arrow_up:

...m/databricks/spark/xml/parsers/StaxXmlParser.scala
97.7% <100%> (+0.09%)
:arrow_up:

...in/scala/com/databricks/spark/xml/XmlOptions.scala
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Oops, I realize there's a flaw here. The schema is read from local files, but is read from the executors. I need a different approach here, like reading it once and serializing it out to executors. Copying the files out with addFiles is possible, but, would require knowing all the dependent XSDs that are imported, which is hard.

See https://github.com/databricks/spark-xml/pull/424 for an improvement and fix.


Basemap not working in csh version

For some reason, the enviornment variable PROJ_LIB is not getting defined as part of conda activate ... in csh/tcsh/etc. (Thanks, @milenaveneziani, for pointing me to this issue.)
A solution may be to define this variable manually in the load_latest...csh script.

A solution has been found and deployed on all E3SM supported machines.  It will be included in this repo with v1.2.5.


proxy/trojan: fix writing UDP packet

#2440 #1795
Every UDP packet should have some headers.

Ref https://github.com/v2fly/v2ray-core/pull/2336#issuecomment-1435247532, maybe related?

In fact, the author made attempt to deal with the issue mentioned above in trojan outbound:
https://github.com/v2fly/v2ray-core/blob/83ea1ba3ba94c944d99cb063bc6c5f42d6cf2fff/proxy/trojan/protocol.go#L102-L114
It 1) Creates a buffer of length 8192 (maxLength = 8192); 2) Read the MultiBuffer 8192 bytes by 8192 bytes, then encode each (at most 8192 bytes) buffer into trojan UDP payloads.
This in a sense fixes the problem that trojan inbound writes the UDP payload 2048 bytes by 2048 bytes. Since a UDP payload will not exceed 8192 bytes (max 4096 bytes as you mentioned), the split UDP packet in trojan inbound will be reunited in trojan outbound.
However, even if scoped in trojan inbound -> trojan outbound, this solution is still problematic. How to ensure that the passed mb buf.MultiBuffer only contains payload of 1 UDP packet? In fact this is not guaranteed, so the UDP packet in outbound may contains payload of more than 1 UDP packets from inbound, causing misbehavior.

Ref #2336 (comment), maybe related?

Indeed. So, this PR also can't handle UDP payload larger than 2048 bytes. Can this be fixed by modifying Trojan's PacketWriter and PacketReader to make use of buf.NewWithSize(), like packetstream in #2337?

I think it will fix. I remembered that I was referencing Trojan's PacketWriter and PacketReader to implement packetstream ones, though I did not have the time and usecase to fix and test for trojan.

Codecov Report
Patch coverage: 42.85% and project coverage change: +0.03 :tada:

Comparison is base (9b52628) 39.05% compared to head (6c8ae32) 39.09%.

:exclamation: Current head 6c8ae32 differs from pull request most recent head c8f0351. Consider uploading reports for the commit c8f0351 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2446      +/-   ##
==========================================
+ Coverage   39.05%   39.09%   +0.03%
==========================================
  Files         617      617
  Lines       37036    37028       -8
==========================================
+ Hits        14465    14476      +11
+ Misses      20981    20962      -19
  Partials     1590     1590

Impacted Files
Coverage Δ

proxy/trojan/protocol.go
42.22% <42.85%> (-3.24%)
:arrow_down:

... and 14 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Audio visualiser with WAD

Hello
I would like to know how could I easily get some data from a music to create a visualizer.
I understand how to use the "pitch" (i found the answer on SO).
But is it possible to for example detect "beats" or spectrum ?

I'm sure it's possible, but I don't know exactly how to do it. You'd probably start by adding a bunch of wads to a PolyWad, so that all your audio is routed together. From there you'd have to get a bit more low level with the web audio api, and add an analyser node to the PolyWad's output so you can examine the audio data. The analyser node has a handful of methods that you can call to examine the live audio data, but I've never actually done anything interesting with it.
You can probably find some guides online that describe the process well enough, and there are probably better tools than Wad.js as well.

In the latest version of Wad (4.7.0) PolyWads can have an audio meter which reports their volume level. That should give you the data you need to build a visualizer. There's an example in the docs.


Changed chrome extension to self-host.

Sets up chrome extension to self host as filesystem (not yet providing executable command).
@rpaquay @ussuri

Two additional notes:
@rpaquay I included the refactoring of WebSocketStreams in here, but I'll revert if you prefer.  It doesn't need to subclass GenericStreams.
@ussuri I copied the full chrome_api.js to externs with some additional missing references.  It did look like the file had been intentionally paired down, though, so I can prune out unused externs if there is a reason to keep the file small (I figured there wasn't since it is not used during compilation, but just during checking).  LMK, thanks!

PTAL

Cc @rginda

lgtm after last 2 comments addressed.


Fail if the spec is not a supported version

Currently there is support for OpenAPI 2.0.
I think OpenAPI < 2.0 and > 2.0 are not compatible with 2.0 so probably the deserialization should check the version and fail gracefully

Good call. I'm thinking to support 3.0 I should start making the interface more version specific so folks can opt into 3.0


Add pom.xml for Maven

Just a quick PR so that you can verify the POM.
Please pay special attention to:

groupID;
artifactID;
your email addresses.

groupid and artifactid look fine to me.
double checked with spoofax core.
spoofax-sunshine uses org.metaborg.sunshine2 btw, but i think org.metaborg.spoofax.shell as in this PR is better.

We should look into aggregate reports for the multimodule project: https://maven.apache.org/plugins/maven-site-plugin/examples/multimodule.html


simplify powershell expression, now blank lines are stripped out

A little followup to https://github.com/Jigsaw-Code/outline-client/pull/327, made possible by the input coming into Powershell already stripped of empty lines. Also replace like '%%' with is not null, for clarity (IMO).
@clementhk FYI (and thanks again)

Tested-by: @clementhk

@trevj  I still got the same error after using the updated outline client which you updated on windows-v1.2.19. Do you know what's exactly caused this? I can connect outline via my android phone, but window 10 can't connect with outline client.


to ntop?

and how do i get the data into ntop?

Hi! I'm not entire sure if I see the background of your question correctly. If you came from my blog post - which mentioned ntop - I'm sorry to tell you that the software in this repo does not at all connect with ntop. It's a stand-alone application which uses softflowd for flow exporting. Please correct me if I'm wrong (or close the issue if that answered your question :wink: ).

question answered thx


Show poorly filled notes at the end of public lists.

[x] Depends on content
[ ] Depends on likes, tags, bookmarks
[ ] Depends on size of content text


Add support for num-uniform-shards option

Fixes #713
Checklist

[x] Documented
[x] Unit tested
[ ] release_notes.md updated

Codecov Report

Merging #714 into master will increase coverage by 0.02%.
The diff coverage is 84.09%.

@@             Coverage Diff              @@
##             master     #714      +/-   ##
============================================
+ Coverage     78.61%   78.63%   +0.02%
- Complexity      661      665       +4
============================================
  Files           113      113
  Lines          2661     2687      +26
  Branches        379      384       +5
============================================
+ Hits           2092     2113      +21
- Misses          321      323       +2
- Partials        248      251       +3


Support significant whitespace

I'd like for roundtripping to work with significant whitespace. More specifically, you can embed valid whitespace in valid JSON, but "roundtripping" seems to not actually roundtrip at all.
(Alternatively, if this won't be supported, perhaps I should just embed comments as whitespace, since you don't wanna support comments because "roundtripping won't work" (even tho it already doesn't). Just execute the JSON as whitespace to get a human-readable documentation for the JSON!)

I would prefer for this to be handled by a different library. This one is geared around Serde interop (hence the name) which is concerned with data, not so much with formatting. Sort of the same distinction between the Serde-based toml crate and the style-preserving molten crate. These use cases have different enough requirements that a separate library would be a better fit.

Can we have comments, then? They're basically whitespace/formatting.

Comments are not part of JSON. And if your input is not JSON, you should not expect to use a JSON parser to parse it. Check out #168 for previous discussion about comments.
If you need to parse JSON with comments, it may be better to find a JSON5 or other human-oriented JSON library and add a strict mode where it parses JSON with comments. As I understand it, commented JSON is valid JSON5 so it may make sense for a JSON5 library to support that. Commented JSON is not valid JSON so I don't plan to do it here.

Why not add JSON5 support as a flag?

It is a different format. According to their readme "JSON5 is not an official successor to JSON." Why not add TOML behind a flag, which also is not a Perl clone?

Because JSON and JSON5 share a common subset which is the entirety of JSON.

Why not add support for parsing the TypeScript language, which also shares a common subset with JSON?
I think ultimately it comes down to whether the Serde team has the bandwidth to maintain yet another format at the level of quality of current serde_json. Maintaining a production-quality JSON5 implementation is out of the question. Stashing a sloppy neglected implementation behind a flag in some un-advertised module may work, but is not a choice that reflects well on Serde or serde_json. I really believe for both JSON users and JSON5 users it will be better for JSON5 to happen somewhere else and be owned by someone who cares about it and has the time.

Why not accept JSON5 by default and emit strict JSON by default?
Emitting JSON5 is easier than JSON but w/e.

What we could do is offer private serde_json APIs behind a cfg flag, so a serde_json5 crate can reuse the code. Instead of making serde_json some feature-crate we could publish a serde_json_internals crate that does major version bumps on every change, but contains the same code just with everything public.

Why not accept JSON5 by default and emit strict JSON by default?

It's not about configurability and defaults, it's as @dtolnay said: We (meaning @dtolnay mainly) do not have leftover capacity to support more formats, even closely related ones. Of course we don't want to hold back anyone trying to implement another format, thus my idea above.


Translations are not returned in showToast's message

Sample screen:
https://studio.ensembleui.com/app/93ifQBH0dyAA5FO50Lri/screen/zmjMyp1I7svJhHJt1AFf
Steps to reproduce:

Create a EN translation and add this to it:

home:
  greeting: test

Create a screen:

View:
  body:
    Column:
      styles:
        padding: 24
      children:
        - Text:
            styles:
              textStyle:
                fontSize: 30
            text<EMAIL_ADDRESS>  onLoad:
    showToast:
      message<EMAIL_ADDRESS>

Message is not returned inside the toast

fixed.


[fix] Adding time grains to Table

CATEGORY
Choose one

[x] Bug Fix
[ ] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY
This PR re-adds the time grain controls back to the Table visualization type as this is needed by the include_time control. Note this is the only visualization type which uses this control (per here).
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN
CI.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

REVIEWERS
to: @etr2460

Codecov Report

Merging #8825 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #8825   +/-   ##
=======================================
  Coverage   65.88%   65.88%
=======================================
  Files         483      483
  Lines       24178    24178
  Branches     2778     2778
=======================================
  Hits        15930    15930
  Misses       8070     8070
  Partials      178      178

Continue to review full report at Codecov.

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


[README.md] General improvements

Added badges, emojis and a warning for those who want to open a new issue.

LGTM, but I personaly don't like the emojies. Also there are few things I don't like with the readme and probably some of them will change anyway soon.


Fix AXI addressing for large runtime-writable weight arrays

Set the proper BD address segment range based on the exposed address width.

Thanks Felix! I've changed the end2end tests a bit to have a testcase that covers this, so now LFC end2end tests are using runtime-writable weights instead of the TFC ones.


stack: introduce relay.macvlanIntfNumber to avoid using random number

stack: introduce relay.macvlanIntfNumber to avoid using random number

if unset, still uses the random
using random causes restarts on every Helm deploy

With #88 landing, the interface name is now static.


Reduce memory usage during postprocessing

The current implementation of postprocessing consumes memory needlessly. Two copies of each intermediate output are serialized and passed to the postprocessing function; note that the lattice argument already contains all intermediate outputs in its transport graph. For workflows with many large intermediate outputs, this inefficiency can nearly double the memory pressure on both the Covalent server and the postprocessor, potentially causing postprocessing to fail.
Some possible improvements include:

Since the Result object also has a post_process method, just send the Result object to the postprocessor and invoke Result.post_process() inside the postprocesor.

Replace the "Lattice" argument to _postprocess with just the serialized workflow function, construct a new Lattice inside the postprocessor from just the workflow function (empty transport graph), and set the self.electron_outputs attribute with the list of intermediate outputs.

Either of these would eliminate the duplicate copy of each intermediate output.

I guess the implementation has changed slightly since this issue was opened, but to summarise:
Initialising an object of Postprocessor has the lattice with it by the virtue of the following constructor:
class Postprocessor:
    def __init__(self, lattice) -> None:
        self.lattice = lattice

Also, the _postprocess function takes in *ordered_node_outputs which can be constructed from the lattice itself i.e. we have the following currently:
def _postprocess(self, *ordered_node_outputs: List[Any]) -> Any:

Now, the Result class also has the _lattice with it, owing to the following constructor:
def __init__(self, lattice: Lattice, dispatch_id: str = "") -> None:
    ....
    self._lattice = lattice
    ....

and the post_process function constructs the ordered_node_outputs by itself with the help of the underlying _lattice.
Note that, after we construct the ordered_node_outputs, the snippet that follows is an exact replica of whatever is present in _postprocess method of the Postprocessor class i.e.
https://github.com/AgnostiqHQ/covalent/blob/develop/covalent/_results_manager/result.py#L328-L336
is same as
https://github.com/AgnostiqHQ/covalent/blob/develop/covalent/_workflow/postprocessing.py#L101-L109
Clearly, there is code duplication.

To avoid code duplication, there are two potential solutions:

Use Postprocessor inside the post_process function of the Result class i.e. have

# result.py
def post_process(self) -> Any:
    ordered_node_outputs = .... # determine using self._lattice
    pp = Postprocessor(self._lattice)
    return pp._postprocess(ordered_node_outputs)

OR perhaps have...
2. Use Result inside _postprocess method of the Postprocessor class i.e.
# postprocessing.py
def _postprocess(self, result: Result) -> Any: # change the signature to accept an object of `Result` instead
    return result.post_process()

Clearly, both of them DON'T solve the issue of memory usage since using either of (1) or (2) forces us to have both objects i.e. an object of Postprocessor class as well as an object of Result class -- both of which have the lattice with them i.e. double memory consumption.

Another idea that comes to mind is to perhaps change the signature of _postprocess method of the Postprocessor class i.e. to have:
def _postprocess(self) -> Any:
    ....
    ordered_node_outputs = .... # calculate using self.lattice instead of receiving it as arguments

But then, this leads to even more code duplication since the _postprocess method of the Postprocessor class now resembles post_process method of the Result class even more...

In retrospect, we should evaluate if:
a. The current level of code duplication is acceptable or not?
b. Do we need to use Postprocessor and Result classes together in any way? Given that this won't solve memory consumption but will reduce code duplication.
c. Do we need the ability to post process from both Postprocessor and Result? This is related to (a). I ask since I am not sure if _postprocess method of the Postprocessor class is used anywhere right now, apart from tests. Perhaps we can eliminate it altogether?
Could appreciate your thoughts @cjao

Closing as this is most likely resolved by the new memory improvements.


Tiny stutters

I get tiny (perhaps 2-3 frame) stutters in this demo code on OS X El Capitan regardless of whether I compile / run with GOGC=off (so it's not GC pauses.)  Is this normal?  Can you help me narrow down what it could be, otherwise?
go version is go version go1.5.3 darwin/amd64 which as we know has concurrent GC anyway, but perhaps this is disabled by the requirement to lock OS thread.

That doesn't sound normal and should not happen for such simple examples. If it happens with GOGC=off, then it's definitely not GC.
What video card and CPU do you have? Which example are you running? Does it happen with both examples?

It's an Intel Iris 6100 on 10.11.2.  It seemed to happen on both examples.  I did a bit of diagnostics and it appears the OpenGL 4.1 demo had a bit more difficulty, frame times in the e.g. 10-12ms range frequently, sometimes breaking the 60fps border.  FWIW, I'm using an external 4k display (60Hz.)
It seemed to clear up later, so I'm not really sure this is reproducible enough to count as a meaningful Issue.  I'll keep an eye on things and see whether I can narrow it down enough to be reproducible.
It's entirely possible this was just a condition of limited resources on the host.  This issue can be closed until I can verify or reproduce.
@shurcooL -- on a side note, I tried approaching this at first with pprof and quickly realized it wouldn't be very useful since a great deal of the CPU time is in external code.  Do you have any advice for profiling within this kind of scope?

Thanks for providing the details. While I do think that hardware should be powerful enough to drive these 2 simple examples smoothly, having a 4k display is possibly giving it a harder time.
Would you be able to try the same test using a 1080p or smaller resolution screen?
I do want to point out it's not as clear cut as if you had said you're running an Nvidia GeForce 650M at a much smaller resolution. But I'm not dismissing it, just sharing observations.

on a side note, I tried approaching this at first with pprof and quickly realized it wouldn't be very useful since a great deal of the CPU time is in external code. Do you have any advice for profiling within this kind of scope?

I don't think I can suggest anything specific; I haven't had a chance (nor the need) to profile graphics code in Go very often so far, it has been quite smooth for me. You should start with the basic tools like pprof, but if they're not very helpful, I'm not sure what the next step would be. If you're running pprof on OS X, make sure you're not hitting a bug with it. I'm not sure if it's been fixed by now. https://github.com/rsc/pprof_mac_fix
According to https://github.com/rsc/pprof_mac_fix/commit/c85105ae1cc39bec94e056158c19b4f62e497b6a, it may be fixed by now, but that should be confirmed.

It is indeed fixed in OS X 10.11 El Capitan (the final public release), so pprof can be used reliably.

Closing for now, since this issue seems very specific to your hardware. We can reopen if we get a reproducer.
Thanks for reporting though because it means others can hopefully find this issue here if they encounter it!

OK! I have observed this on my hardware. Just required that I look closely enough. Seems to happen every ten seconds. I'm seeing it on a powerful rig with an Nvidia 1080 GTX and powerful CPU.

I'm using the gl41core-cube example for testing
It's visible with glfw.SwapInterval(0) and a framerate > 10,000/sec
It happens with GOGC=off
Measuring the time elapsed between frames I always see times < 1ms

I'm not sure what's going on here. I'm wondering if this is anything go specific. Given that the elapsed times between frames are consistently under 1ms and the visual artefacts don't seem correlated to any framerate drop or elapsed frame differences I'm wondering if the problem is in go-gl or at some other layer.
@shurcooL: Can you confirm, if you run the examples and stare at them that they are buttery smooth? It is only just perceptible. It seems as though the spinning cube judders slightly, maybe going backwards. I wish I had a high speed video camera to measure it...
Now I'm off to hunt an example from glfw3 in C to see if this is just a thing that happens in general and I have only just become aware of it.

Well, it happens for me in the gears example found in the glfw repository. So I guess this must be a "feature" of either glfw or my system.
I'll leave this open for a little bit, but if six months passes and nothing happens then I think this should be closed. It would be interesting to follow up upstream to see if there anyone else has complained over there.

Yes, I think I see some tiny stuttering, but only with v-sync off. It's not there with v-sync on, on a 60 Hz display.
I tried adding a printf if a given frame takes too long:
if elapsed >= 0.020 {
	fmt.Println(elapsed)
}

And surprisingly I get a few matches (not counting the first frame):
0.025746207999999937
0.03162123499999936
0.030519868999999034

Just adding more information so that maybe it helps:
Running with kernel: Darwin MacBook-Pro.local 16.3.0 Darwin Kernel Version 16.3.0: Thu Nov 17 20:23:58 PST 2016; root:xnu-3789.31.2~1/RELEASE_X86_64 x86_64
Go version: go version go1.7.4 darwin/amd64
I have not seen such a problem a so far.

I see it with vsync on or off. I also measured the frame latency, and found that the longest frames (per second) were consistently small, even when there was a tiny stutter. So I guess this is a problem elsewhere in the graphics stack than glfw. I'm going to close this for now unless anyone comes up with more information since I don't think there is anything to be done for go-gl here.


[stable/jenkins] install of ingress fails.

Is this a request for help?: NO

Is this a BUG REPORT or FEATURE REQUEST? (choose one):  BUG REPORT

Version of Helm and Kubernetes: Helm "v2.8.1"  - Kubernetes "v1.9.5"
Which chart: jenkins
What happened: install fails
helm --namespace jenkins --name jenkins -f ./values.yaml install stable/jenkins --debug
[debug] Created tunnel using local port: '35153'

[debug] SERVER: "<IP_ADDRESS>:35153"

[debug] Original chart version: ""
[debug] Fetched stable/jenkins to /root/.helm/cache/archive/jenkins-0.14.4.tgz

[debug] CHART PATH: /root/.helm/cache/archive/jenkins-0.14.4.tgz

Error: unable to recognize "": no matches for networking.k8s.io/, Kind=Ingress

What you expected to happen: install ok.
How to reproduce it (as minimally and precisely as possible): Define HostName and install.
Anything else we need to know: Applying this diff, it fixed:
# diff jenkins/templates/jenkins-master-ingress.yaml jenkins-fixed/templates/jenkins-master-ingress.yaml
2c2
< apiVersion: {{ .Values.NetworkPolicy.ApiVersion }}
---
> apiVersion: {{ .Values.Master.Ingress.ApiVersion }}
21c21
< {{- end -}}
---
> {{- end }}

I think this was fixed in this commit. My guess is that the helm client has cached an old version that does not have this fix (as I can see its trying to deploy 0.14.4).  The new version is fixed.


11075 Admiral Make sure the default remains GitLab in existing installations

Shippable/pm#11075
Make sure that if no state type has been set and it is not new, the default is GitLab.  If it is a new installation, the default should still be Amazon S3.

Verified in that the default new type is Amazon S3 and the default existing type is GitLab.


Refactor and Cleanup

Make agent color a type parameter of Agent struct.
Randomize agent starting direction in SequentialRooms
Standarize field-names terminal_reward and terminal_penalty when appropriate, in place of using different names like goal_reward, obstacle_reward, penalty, etc...
Rename Pickup action to PickUp
Specify the dimension size of 2 as the type parameter for CartesianIndex and CartesianIndices
Remove dependency on Colors.jl
Clean up imports and exports
Miscellaneous cleanup

Codecov Report

Merging #99 (93b1d3b) into master (8f67fa5) will increase coverage by 0.33%.
The diff coverage is 69.84%.

@@            Coverage Diff             @@
##           master      #99      +/-   ##
==========================================
+ Coverage   80.86%   81.19%   +0.33%
==========================================
  Files          16       16
  Lines         737      734       -3
==========================================
  Hits          596      596
+ Misses        141      138       -3

Impacted Files
Coverage Δ

src/GridWorlds.jl
100.00% <ø> (ø)

src/actions.jl
100.00% <ø> (ø)

src/makie_rendering.jl
0.00% <ø> (ø)

src/terminal_rendering.jl
0.00% <0.00%> (ø)

src/objects.jl
40.54% <33.33%> (+3.95%)
:arrow_up:

src/envs/dynamicobstacles.jl
97.50% <75.00%> (ø)

src/abstract_grid_world.jl
72.13% <100.00%> (+8.36%)
:arrow_up:

src/envs/collectgems.jl
100.00% <100.00%> (ø)

src/envs/doorkey.jl
100.00% <100.00%> (ø)

src/envs/emptyroom.jl
100.00% <100.00%> (ø)

... and 6 more

Continue to review full report at Codecov.

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


Day60: LeetCode-1897. Redistribute Characters to Make All Strings Equal - HashTable

Redistribute Characters to Make All Strings Equal
https://leetcode.com/problems/redistribute-characters-to-make-all-strings-equal/
You are given an array of strings words (0-indexed).
In one operation, pick two distinct indices i and j, where words[i] is a non-empty string, and move any character from words[i] to any position in words[j].
Return true if you can make every string in words equal using any number of operations, and false otherwise.

Example 1:
Input: words = ["abc","aabc","bc"]
Output: true
Explanation: Move the first 'a' in words[1] to the front of words[2],
to make words[1] = "abc" and words[2] = "abc".
All the strings are now equal to "abc", so return true.
Example 2:
Input: words = ["ab","a"]
Output: false
Explanation: It is impossible to make all the strings equal using the operation.


<EMAIL_ADDRESS>requires<EMAIL_ADDRESS>specfically

Describe the bug
Looks like wagmi/connectors is requiring wagmi/core 2.8.1 so upgrading to 2.9.0 creates issues.
would be nice to be able to upgrade all packages and stay with latest!
Link to Minimal Reproducible Example
No response
Steps To Reproduce
upgrade @wagmi/core to 2.9.0 and @web3modal to 4.1.11
Wagmi Version
2.8.0
Viem Version
2.9.31
TypeScript Version
No response
Check existing issues

[X] I checked there isn't already an issue for the bug I encountered.

Anything else?
No response

Should be good now.


User Manual

Need to write a user manual so that there is more information on the specific parameters used in the functions.

Added DOCUMENTATION.md which includes the general outline of the code and some key parameters. This does not sufficiently document all function input arguments but most of the input arguments are also defined in the comments by the input.

Extended documentation added for all functions in "DOCUMENTATION.md".


Projects search doesnt work with single letters

Actions before raising this issue

[X] I searched the existing issues and did not find anything similar.
[X] I read/searched the docs

Steps to Reproduce

Search for a in the searchbar of projects page and it will render all of the projects.

Expected Behavior
The search should show only projects starting with a.
Possible Solution
No response
Context
No response
Environment
No response

@syedbarimanjan sure

The search should show only projects starting with a.

No. It checks including, not starting with.

I may suggest you to implement one more filter. Now it also supports only Contains rule.
If the use-case is important for you.


feat(data): typography for loader

:tada: This PR is included in version 4.25.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


The kelemetry-chart v0.2.7 is unavailable on kubernetes v1.21.3

Steps to reproduce

Download values.yaml and configure the settings(I only changed storageClassName).
Install the chart:  helm install kelemetry oci://ghcr.io/kubewharf/kelemetry-chart --version v0.2.7  --values values.yaml
Output:

Pulled: ghcr.io/kubewharf/kelemetry-chart:v0.2.7
Digest: sha256:ae6acb3d014a5de5ff7f498fe5bcddc5b9da05122269704ad303eac888798122
Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(StatefulSet.spec): missing required field "serviceName" in io.k8s.api.apps.v1.StatefulSetSpec

Then I  configure the field "io.k8s.api.apps.v1.StatefulSetSpec.serviceName",  helm install again, the comsumers and informers CrashLoopBackOff, even after the etcds is Running.
Log:

time="2024-09-03T06:04:46Z" level=error msg="unknown flag: --aggregator-span-follow-ttl"

Expected behavior
No response
Actual behavior

Although the latest version of k8s does not have this problem, according to the documentation, I think this field "io.k8s.api.apps.v1.StatefulSetSpec.serviceName" should be configured.
The comsumers and informers CrashLoopBackOff also occurs in the latest version of kind cluster.

Kelemetry version
v0.2.7
Environment
kubernetes v1.21.3

Right, the aggregator-span-follow-ttl option has been removed a long time ago, we forgot to update the chart for that.


Build is broken after updating to latest version of Turbo geth

I updated my fork of the repo here: https://github.com/tjayrush/turbo-api-examples/commit/14f39cd4f1aa87fa440a74dee58ac277c838f856 which seems to have worked, but now the build is pretty broken.
I tried to fix it myself, but I was making wild stabs in the dark, and I was worried I would break the database. Perhaps you have some suggestions on how to fix it.
If I do this command:
jrush@Office:~/D/turbo-api-examples|master✓➤ go build cmd/supply/*.go

I get these errors:
# github.com/ethereum/evmc/v7/bindings/go/evmc
host.c:33:20: warning: unused function 'go_exported_functions_type_checks' [-Wunused-function]
# github.com/mandrigin/turbo-api-examples/supply
supply/calculate_backward.go:74:10: undefined: changeset.AccountChangeSetPlainBytes
supply/calculate_forward.go:81:8: undefined: changeset.AccountChangeSetPlainBytes
supply/calculate_forward.go:130:43: cannot use kvHolder.KV() (type ethdb.KV) as type ethdb.Tx in argument to state.GetAsOf:
	ethdb.KV does not implement ethdb.Tx (missing BucketSize method)
supply/calculate_forward.go:150:13: tx.Get undefined (type ethdb.Tx has no field or method Get)
supply/utils.go:31:18: not enough arguments in call to db.Delete
	have (string, []byte)
	want (string, []byte, []byte)

The mint example is also broken with this result:
# github.com/ethereum/evmc/v7/bindings/go/evmc
host.c:33:20: warning: unused function 'go_exported_functions_type_checks' [-Wunused-function]
# command-line-arguments
cmd/mint/main.go:75:24: not enough arguments in call to stagedsync.New
	have (stagedsync.StageBuilders, stagedsync.UnwindOrder)
	want (stagedsync.StageBuilders, stagedsync.UnwindOrder, stagedsync.OptionalParameters)
cmd/mint/mint.go:121:19: undefined: rawdb.DecompressBlockBody


version.py - single project version definition

Actual Behavior
currently the packerlicious project version is defined in:

https://github.com/mayn/packerlicious/blob/master/src/packerlicious/__init__.py#L22
https://github.com/mayn/packerlicious/blob/master/setup.py#L21

this means during a release both locations need to be updated
Expected Behavior
refactor to create a version.py file under src/packerlicious which contains the __version__ = "0.4.0" definition.

__init__.py should be changed to import this new version.py and assign __init__.py.__version__ to the value found in version.py
setup.py should open and read src/packerlicious/version.py and assign the version reference to the value found in version.py

I am doing this

have a look @mayn  PR submitted


Ghost Core upgrade notification confusing for desktop users

 = 👍
Clicking takes me here: support.ghost.org/how-to-upgrade/ 👎

Hi there @kevinSuttle Could you explain why you're giving our support page a thumbs down? I'd love to improve it.

It's not the support page I'm giving 👎, it's the fact that clicking that link in the Ghost Desktop app (where the notification appears), takes me out to the browser, instead of "upgrading" my desktop app.

Oh, I see the confusion - it's not the desktop app that is out of date (that one should update itself without even bothering you), it's the blog itself that's in need of an update. And luckily for everyone, Hannah doesn't just mess with your blog ;-)
I'm closing in the meantime, but let me know if that was in error!

Yeah, it's pretty confusing (I know the difference, but still).

We could potentially inject a little script that captures the string and changes it to something more specific (for desktop users only). Or, we could bake a quick if/else into core.
@ErisDS: Thoughts?

We're in the process of changing, upgrading, and replacing this system in Ghost.
We haven't used it in a while because it was confusing and not very useful. However, we have to get everyone to upgrade in order to get the new version of the feature!  Hence, this message would have popped up last week for anyone on <0.8.0 where they wouldn't have seen it since before 0.6.
If you want to do some sort of capture & replace in Ghost-Desktop to make the message clearer in that context that sounds like a great plan. Otherwise, once we get everyone onto 0.9 (coming soon) the messages will work differently.

@ErisDS, @felixrieseberg I'll write up a lil' message rewrite here.


New Sample reorder expand items board format

Q
A

Bug fix?
no

New sample?
yes

Related issues?

What's in this Pull Request?
This sample allow users to manage cards order in Board Views and also allow to expand and collapse images based on url or iconName option.
This sample has option "Move to Top" that allows to manage cards to top of board view as way to rearrange card positions.
Guidance
Thanks for your contribution! Sharing is caring.

WOO WOO!!! 👍👍


ZnIncomplete signal: 'Incomplete input for character decoding'

Attempt to run the following in Pharo 10.0 image (64 bit):
firesatClient := PBSPARQL new
    endpoint: 'http://localhost:3030/firesat/sparql';
    query: 'PREFIX fse:   <http://opencaesar.io/examples/firesat/disciplines/fse/fse#>
PREFIX base:   <http://imce.jpl.nasa.gov/foundation/base#>

SELECT ?assembly ?subassembly

WHERE {
	?assembly base:contains ?subassembly
}'.

Received the following error:
errorIncomplete
	^ ZnIncomplete signal: 'Incomplete input for character decoding'

Solved:
In firesat-example directory in kasm-user
Run: rm -rf build .gradle to purge gradle build and run the following:
./gradlew build
./gradlew startFuseki
./gradlew owlLoad


Clarify language in Discover feed post actions

The context menu for posts in the Discover feed includes these two actions:

Show more like this
Show less like this

This wording expresses what the service will do, not what the user is doing (wrong actor/action and tense). Better would be:

I like this suggestion (or "recommendation", but four syllables is better than six)
I don't like this suggestion

The actor is the user and the action is expressing their sentiment about a suggestion. This would also map exactly to the 🙂 and 🙁 icons.
I'm explicitly proposing the inclusion of "suggestion", because the wording "I don't like this" is ambiguous, and could refer to either the post itself or the suggestion.
The current wording uses "like this" in the sense of "similar to" but which is ambiguous in a different way. I'll describe that below but it's supplementary info to this feature request.

Whenever I see the current wording in any service that lets you rate its suggestions, I think "What is like this?" For posts on Bluesky, that could be any of:

by the same account
liked by your followed/followers
reposted by your followed/followers
account is labeled a certain way
talks about a certain thing
has an image of a certain thing...

If my general understanding of how these systems work is correct, it's not a particular case of any of those. Instead the user is flagging the suggestion to include it in a list of either good or bad ones, which are then analyzed for common factors to weight future suggestions.
Including "like this" in the action label risks the user pausing to try to understand the algorithm before taking action.

I prefer the current ones, personally, since they tell me what the feed will do/what this is used for.
"I like"/"I don't like" are very ambiguous at least to me, in terms of what happens in response to that.

"I like"/"I don't like" are very ambiguous at least to me, in terms of what happens in response to that and what my data is used for. (I.e. I don't want to downrank the post, just personally see less like it, and it's also more clear that the user won't see this info.)

These issues can be resolved with additional messaging, such as a caption accompanying the actions (e.g. "Was this post a good suggestion for you?") and feedback presented after taking the action (e.g. "Thanks. We'll use your rating to fine-tune the posts we suggest.").


test documentation previews

Don't merge.  Checking preview.

Just to clarify we want docca to show a preview of its own test/examples not other libraries.


Tooltip is not cleared for empty value if placeholder is there

Prerequisites

[ ] I have searched for similar issues in both open and closed tickets and cannot find a duplicate
[ ] The issue still exists against the latest master branch of Select2
[ ] This is not a usage question (Those should be directed to the community)
[ ] I have attempted to find the simplest possible steos to reproduce the issue
[ ] I have included a failing test as a pull request (Optional)

Steps to reproduce the issue

Enable placeholder for dropdown

select a value

Clear the value and check tooltip

Expected behavior and actual behavior
When I follow those steps, I see...
Previous selected value is in tooltip
I was expecting...
No tooltip in that case
Environment
Browsers

[ ] Google Chrome
[ ] Mozilla Firefox
[ ] Internet Explorer

Operating System

[ ] Windows
[ ] Mac OS X
[ ] Linux
[ ] Mobile

Libraries

jQuery version:
Select2 version:

Isolating the problem

[ ] This bug happens on the examples page
[ ] The bug happens consistently across all tested browsers
[ ] This bug happens when using Select2 without other pluigns
[ ] I can reproduce this bug in a jsbin

#4746 has been merged into the 4.0.6-rc.0 pre-release.


info.py: added badger os version number

Adding Badger OS version number to the info.py example.

Will close #88 and #15


Fancy Cursors with Vim mode causes cursor to behave incorrectly

In Vim mode, when transitioning from Normal mode to Insert mode, the cursors position is placed to the right of the current character that the block cursor is on. Correct behaviour is that the cursor be placed on the left.
This is a cursor visual bug only, any typed characters are placed in the correct position, upon which the cursor then updates.
Current Behaviour
https://user-images.githubusercontent.com/87576423/141073830-35f2cd50-77df-4118-b499-fe406feb970d.mov
Correct Behaviour (w/ Fancy Cursors Disabled)
https://user-images.githubusercontent.com/87576423/141073943-50878770-5907-443b-aa52-ce11ae4bdb7e.mov

I have the same problem

Also experiencing this bug

This will be fixed in Minimal 4.2

This will be fixed in Minimal 4.2

This is good news! Thank you 👍


Split FilteredInclude into a separate node type

We should be consistent between handling of single vs. multi level filtered include.  Either:

Filtered include has an array of filter name + attributes
Filter node can contain either plain text or an include node, there is no such thing as a "filtered include"

My proposal would be to have a RawInclude node which would be for including plain text, and an Include node that is for including jade.  Then as per option 2, a filter node can contain a RawInclude or another Filter or plain text

Filter node can contain either plain text or an include node, there is no such thing as a "filtered include"

That was my initial plan, but I wanted to be able to use JSTransformer's renderFile, and a separate type for filtered include seemed to be a natural solution.

That's a good point, I suppose our handling of the first filter will be special in that respect, although it seems like an implementation detail of the filter processing step (i.e. it could look at the node, see if it's a filter node, then see if it's child is an include node, then behave appropriately).

Maybe go with option 1 then?  It will make it easier to implement efficiently without generating and then discarding a whole series of plain text nodes.

How about this:

RawInclude for raw inclusion
Include for Jade inclusion; .filters can be [ IncludeFilter ] | null; IncludeFilter is just like a regular Filter but without block; filters are applied in ascending order from .filters[0].

@ForbesLindesay ping.

Lets have .filters as the empty array instead of null when there are no filters.  Other than that I'm completely happy with this.

Updated, please review.

One more problem with this approach: the exact path and therefore type of the inclusion is determined in jade-load's overridable resolve function, which means it is not possible to tell if the inclusion is RawInclude or Include at the parsing stage, unless other factors like filters are involved.
So this leaves us with two choices:

Add .jade suffix at the parsing stage and disallow overriding resolve in jade-load. In other words,  Include is used for all extensionless includes (again, unless there are filters). Changing the parser is of course always possible, but not as convenient.
Use filters as the sole determinant of the type of the inclusion, i.e. we are back to the original FilteredInclude type.

I think we should disallow changing the type at the jade-load stage.  i.e. if the node is RawInclude then we include it as plain text even if the file extension is .jade.  It's then up to the parser to decide whether something is Include or RawInclude.
In short, lets deprecate extension-less include (and extend)


b != b ?

played for the first time today. b was not yellow in the wrong position nor green in the right position.

I opened an incognito window and put in the right answer, and that one recognized the b just fine, though.

on Chromium Version 97.0.4692.71 (Official Build) for Linux Mint (64-bit)
happy to debug on that browser window (still open) if you see this before it's closed.

This same thing happened to me.

Seemed to be a case mismatch bug (particularly on mobile) that I didn't catch yesterday because there were no digits A-F in yesterday's Hexle! I've published a fix to this bug, so hopefully after a refresh/cache clear, your Hexle answer should say it's correct now.


Empty Dependency for Litellm Environment

Hi authors,
Thanks a lot for your works, and I'm trying to use this benchmark in my recent project.
However, I found that the there are no dependencies in the environment.litellm.yml file, which resulted in a failure to run the corresponding experiments on my local machine. Could you please help check if this is correct? Or did I miss something?

Hi KOU,
Thanks for being interested in our work, and many thanks for proposing this env issue.
I have changed the env setup to use pip instead of conda yml files.
Pls use the following pip command (the corresponding README file has been updated as well):
conda create -n litellm python=3.9
conda activate litellm
pip install -r env_source/requirements.litellm.txt


Fix predictions and adds requirements

Fixes https://github.com/jrosebr1/simple-keras-rest-api/issues/7 and addresses https://github.com/jrosebr1/simple-keras-rest-api/issues/11

Thanks for providing a solution the code didn't work for me without this

Thanks for the solution. This solved all of my errors due to the TF 2.0 upgrade. Seems like TF 2.0 doesn't work well with older versions of Keras.


Add lint workflow

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

1 of 13 (7.69%)  changed or added relevant lines in 1 file are covered.
57 unchanged lines in 1 file lost coverage.
Overall coverage remained the same at 71.194%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/controller/githubapp_controller.go
1
13
7.69%

Files with Coverage Reduction
New Missed Lines
%

internal/controller/githubapp_controller.go
57
71.19%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
304

Relevant Lines:
427

💛  - Coveralls


adapter class is now an R6 class

Rewrote adapter_class as an R6 class.
Honestly, I mostly did this to become familiar with how the internals of the engine are set up.

Nice! 👍
Have @robertzk review

@robertzk what else does this PR need?


Generation structure of seeding files

Hello!
Typeorm has command for generation migration files: typeorm migration:generate. Is planned the same feature in typeorm-seeding? This feature will by useful in cases when we want to fill database some data such as catalogues, lists etc.

Hi @capinemo
This is not planned yet. However, feel free to create a pull-request with it. I would be very happy to integrated it with you.

Thank you for answer!
Then i will implement this functionality.

@capinemo do you need any help ? Feel free to ask !

@nathanagez thanks!
There shouldn't be any problems yet. If i have any questions, i will ask them.

Hi! Sorry, work, family...
File generation is solved:
https://github.com/w3tecch/typeorm-seeding/compare/master...capinemo:seed_generate
But it has problem. I thought that running this files must work as typeorm - data seeded and file name saved handled file into 'migrations' table to db. If we use typeorm's table (migrations) we must use it methods, but it is protected. If we decide to realize similar logic, we will double this logic((


Utterance generation bug

I am filing this here but also cross-filed against the alexa-app.  Please feel free to close out one of them.
@matt-kruse There seems to be a bug in the server generation of utterance permutations.  For example the following:
    "utterances": ['{to|} set temperature to {64-80|number}']
generates utterances as follows:
setTempsIntent	to set temperature to {sixty four|number}
setTempsIntent	set temperature to {sixty five|number}
setTempsIntent	to set temperature to {sixty six|number}
setTempsIntent	set temperature to {sixty seven|number}
...

but what I believe should be generated is:
setTempsIntent	to set temperature to {sixty four|number}
setTempsIntent	set temperature to {sixty four|number}
setTempsIntent	to set temperature to {sixty five|number}
setTempsIntent	set temperature to {sixty five|number}
setTempsIntent	to set temperature to {sixty six|number}
setTempsIntent	set temperature to {sixty six|number}
setTempsIntent	to set temperature to {sixty seven|number}
setTempsIntent	set temperature to {sixty seven|number}
...

@matt-kruse OK I've confirmed this does not lie with the alexa-server but rather in how alexa-app uses the alexa-utterances package.  Closing this out.


Playwright - Cannot find module '/browsers.json'

Describe the bug
After deploying an app to vercel the function with playwright crashes because of a missing brwosers.json.
Reproduction
Repo not necessary since this case seems to be pretty obvious.

Install playwright-core
Install chrome-aws-lambda
deploy to vercel

In /node_modules/playwright-core/lib/utils/registry.js the browsers.json gets loaded by the following code:
// require() needs to be used there otherwise it breaks on Vercel serverless
// functions. See https://github.com/microsoft/playwright/pull/6186
const browsersJSON = require(path_1.default.join(packagePath, 'browsers.json'));

But since this browser.json won't be bundled, it is missing in the function.
System Info
Output of npx envinfo --system --npmPackages vite,@vitejs/plugin-vue --binaries --browsers:
  System:
    OS: Linux 5.11 Ubuntu 21.04 (Hirsute Hippo)
    CPU: (16) x64 Intel(R) Core(TM) i9-9900KS CPU @ 4.00GHz
    Memory: 1.23 GB / 15.54 GB
    Container: Yes
    Shell: 5.1.4 - /bin/bash
  Binaries:
    Node: 16.1.0 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 7.12.1 - /usr/local/bin/npm
  Browsers:
    Chrome: 90.0.4430.212
    Chromium: 90.0.4430.212
    Firefox: 88.0.1

Used package manager: pnpm
Logs

2021-05-13T09:34:43.740Z	undefined	ERROR	Cannot find module '/browsers.json'
Require stack:
- /var/task/index.js
- /var/task/___now_launcher.js
- /var/runtime/UserFunction.js
- /var/runtime/index.js
2021-05-13T09:34:43.740Z	undefined	ERROR	Did you forget to add it to "dependencies" in `package.json`?
RequestId: ca39298f-73b0-49a6-b904-827c5f7a70ad Error: Runtime exited with error: exit status 1
Runtime.ExitError

Before submitting the issue, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the docs.
[x] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[x] Provide a description in this issue that describes the bug.
[ ] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[x] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

Please provide a repro. The issue is not obvious to me, and I'm not sure how to setup the repo to achieve the behaviour


A kind of middleware for certain handler

Now we have nested blueprint support, which is desired by who wants to reuse. In my situation, I build a restful CRUD api for some database operations (a blueprint), but in my application different urls have different intended users i.e. they have different privileges. I want to only add the privilege check for a certain url instead of always building a new blueprint, so there has to be some mechanics to add a filter to an existing route, which can return new response or call the old handler and modify the result.
As you commented here, it's too complex for me to find a suitable way to replace the old handler, so I just write an immature implementation for blueprint. Do you have any better idea?

@fduxiao I like the idea behind this, but I think it is something that should be implemented by a Plugin, rather than by Sanic itself.

@ashleysommer alright, let me write a Plugin then.

@fduxiao Did you ever make a plugin for this? I am going to close this PR since I agree that this is not something we want in sanic core right now.


Allow users to blacklist certain folders

Hi, I've been using pylance and it's a really great tool thank you !
I really like the "Analyse workspace things" which give lot of insight.
However, I was working with a library call weight and biases (to track ml runs) and it's checkpointing my code in a folder.
Unfortunately, pylance check that folder and I get 1000+ errors....
I read #422 but I guess it was different enough to raise a new issue.
The best thing possible would be to have the possibility to blacklist this folder.
If there is a hack available please let me now.
Thanks in advance.

Pylance is built on top of Pyright, Microsoft's open-source type checker. Most of Pyright's configuration options are available directly through VS Code settings, but a few of the more esoteric/advanced configuration options are not. There is an option to "exclude" specific directories in Pyright. To do so, create a "pyrightconfig.json" file at the root of your workspace and add an "exclude" section. Specify the relative path to the folder you would like to exclude. For more details and a sample config file, see this documentation.

Thanks a lot for the detailed answer which solved the problem.

Have a great day :)


Automatically set ID when creating new projects

@odscjames How does this approach look for projects? If this is okay, I can then extend it to all records.

@Bjwebb Basically looks good, thanks! Just comment about putting it in a class/function/whatever so it can be used from future import scripts too.


Forcing Bootloader mode on SAMD21 to avoid having to press the reset button

I am using BOSSA 1.8 on Mac
It works greats but it needs the board to be placed in bootloader mode by pressing the reset button twice. My board is placed in an enclosure with no direct access to the reset button.
Could you add a line like
 stty -f /dev/cu.usbmodemfa121 1200;stty stop /dev/cu.usbmodemfa121
just before the bossac command.
This would force the board to enter into bootloader mode. I have tried the command from the terminal and it allows BOSSA to detect the board.
This is also the trick (opening closing the port at 1200 bps)used by the Arduino IDE to enter into bootloader mode (I found this trick here: [https://arduino.stackexchange.com/questions/1160/why-does-command-line-bossa-not-recognize-arduino-due]

I would love this too!

This should be in the current master using the -a switch.  I haven't tested it since I do not have a SAMD Arduino.


Add compile tests for handshake::client with Send and !Send executors

https://github.com/littledivy/fastwebsockets/commit/7ddee1af380ba104d35961e0147a50c7941dab35


Add profiling analysis

Here is a more interesting examples of the produced plots which have been generated focusing on GLRender running on an HiKey board:
https://gist.github.com/8470420d2954e1d42bcfab8c24b05620

Addressed main @bjackman comments and added some small updates required by Joel.
After #301 gets merged I think we can merge this as well ;-)

Not a strict dependency, but perhaps this should be merged after #303

The new CDF looks good to me although my judgement is very inexpert. Other than that, looks great apart from the nitpick about 'Time'.

While testing with Jankbench on HiKey I noticed this problem with plotRuntimes().
Debug output reports
2017-02-20 14:15:46,292 WARNING : Unexpected next state: D|K @ 11.602299 2017-02-20 14:15:46,293 WARNING : Unexpected next state: D|K @ 11.605174 2017-02-20 14:15:46,294 WARNING : Unexpected next state: D|K @ 11.623388 2017-02-20 14:15:46,295 WARNING : Unexpected next state: D|K @ 11.627947 2017-02-20 14:15:46,296 WARNING : Unexpected next state: D|K @ 11.634416 2017-02-20 14:15:46,297 WARNING : Unexpected next state: D|K @ 11.638789 2017-02-20 14:15:46,298 WARNING : Unexpected next state: D|K @ 11.641854 2017-02-20 14:15:46,299 WARNING : Unexpected next state: D|K @ 11.644686 2017-02-20 14:15:46,300 WARNING : Unexpected next state: D|K @ 11.646673 2017-02-20 14:15:46,301 WARNING : Unexpected next state: D|K @ 11.649564 2017-02-20 14:15:46,304 WARNING : Unexpected next state: D|K @ 11.686784 2017-02-20 14:15:46,309 WARNING : Unexpected next state: D|K @ 11.691463 2017-02-20 14:15:46,310 WARNING : Unexpected next state: D|K @ 11.693135 2017-02-20 14:15:46,312 WARNING : Unexpected next state: D|K @ 11.699686 2017-02-20 14:15:46,314 WARNING : Unexpected next state: D|K @ 11.700721
Also log says that 100% of samples fell under 40ms, but tabular data (df.T) reports a max of ~54ms.
Trace uploaded here https://drive.google.com/open?id=0B0gETIMiqtYIN2hVN2JNNjFlRDA

The reported 100% value is due to rounding at format time... there is just one sample (the max value) above the threshold... in a set of +5k samples. The actual percentage should be: 99.981%
Will fix by adding a bit of resolution to the formatting strings.
Regarding the events, I cannot find them in the trace you linked. I've used:
grep "==>" results_customers/Juri/trace.txt  | grep -v -e "[R|S|D|x] ==" | grep "D|K"

However, it's true we do not currently parse such events, which are related to UNINTERRUPTIBLE tasks being killed (quite an interesting condition)... will try to make this case covered as well.
If you can find the trace with these events and share it would be useful for testing.

Fixed synchronization with setXTimeRange for existing and new plots.

Fixed documentation according to @bjackman comments.

Perhaps the current version can still have some issues depending on specific trace events and tasks states specifically, but I would say that it's still worth to have it merged now and address small fixes in future PR.


[10.x] Add arguments to the signed middleware to ignore properties

Why
Based on this tweet from Claudio Dekker. This allows passing properties to the signed middleware to ignore properties instead of extending it and adding the keys to the $ignore property.
Also, this adds the possibility to pass the ignore parameters to the static methods: relative and absolute.
Pros of this implementation

Make the routes file easier to understand
Remove a lot of 'custom' Middleware files that individually take up a lot of 'visual' space while providing near-zero real value

Result
Middleware
// Before
Route::get('foo')->middleware('signed');
Route::get('embed')->middleware(EmbeddableSignedRoute::class);
Route::get('callback')->middleware(SignedRouteWithCallback::class);
Route::get('relative')->middleware('signed');

// After
Route::get('foo')->middleware('signed');
Route::get('embed')->middleware('signed:embed');
Route::get('callback')->middleware('signed:callback');
Route::get('callback')->middleware('signed:callback');
Route::get('relative')->middleware('signed:relative');
Route::get('relative-embed')->middleware('signed:relative,embed');

Static Methods
ValidateSignature::absolute('foo', 'bar'); // 'Illuminate\Routing\Middleware\ValidateSignature:foo,bar'
ValidateSignature::relative('foo', 'bar'); // 'Illuminate\Routing\Middleware\ValidateSignature:relative,foo,bar'

Hi there,
I guess this is an acceptable solution. Only issue I see is when you would want to ignore the relative parameter within an absolute URL. Might be a bit pedantic, but we should not forget about about developer experience and what someone can expect when using these API's.
Can we maybe update the factory-like static methods to include ignored parameters?
ValidateSignature::absolute('ignore', 'me');

Hi there,
I guess this is an acceptable solution. Only issue I see is when you would want to ignore the relative parameter within an absolute URL. Might be a bit pedantic, but we should not forget about about developer experience and what someone can expect when using these API's.
Can we maybe update the factory-like static methods to include ignored parameters?
ValidateSignature::absolute('ignore', 'me');

That's a nice idea, let me do some testing here!

@erikgaal added the implementation that you suggested, thanks! 😉 💪

The middleware already ships in the skeleton though? You don't have to extend or do anything manually.

@taylorotwell this is in cases like in the example where multiple routes will have different ignore parameters, in this case, it's needed to create new middleware classes to extend and add the needed parameters in the ignore/except.
With this PR the current behavior remains the same if people want to use it with the ignore/except property but it will also provide the other way to use it with the list of properties in the middleware definition.

I have not better solution but signed:embed kind of suggests that the embed parameter is actually the one the will be signed.
But ever Alternative I can think of (signed:except:embed,state and so on) makes it even worse 😅
Best alternative I can think of is a fluent ->signed(...) method but I don't know if this is desired.

@WendellAdriel one thought I have with this is should the passed ignore arguments override the default "except" ones totally or should they merge with them?

@taylorotwell that's a really good question.
Right now it's set to override and I think it makes sense because you can have your default configuration on the except and if you need something custom, then you can pass manually the arguments to ignore.

@WendellAdriel I guess I can see it both ways. You may define the things you always want to ignore in the middleware. If you add additional ones on route registration I would potentially expect those (the things you want to sometimes ignore) to be merged in with the things you always want to ignore.

@taylorotwell tomorrow morning my time I’ll update the PR with that then!

@taylorotwell I updated the PR with some changes to allow it to merge the arguments passed in the middleware with the ignore/except property and added a new test case for that

Thanks!

Thanks!

I’m happy to help!!! :muscle:


RE: Coverage Interfaces

This is in response to comments on accessing UCIS/UCDB. The projects pyucis and pyucis-viewer provide some level of support. pyucis can write functional coverage data in UCIS XML-interchange format, and to Mentor UCDB via the UCIS library provided by Questa. pyucis-viewer provides a simple bar-chart graphical viewer for coverage data read via pyucis.

Thanks Matthew! I was not notified about this issue, and I had not seen it. I fixed the watch settings now.
I updated the docs for adding your clarifications about pyucis and pyucis-viewer: https://github.com/umarcor/osvb/commit/96f4a5c7ac0e3d627a4ade294954137f852fff73.


When running ./gradlew --console=plain no output is produced

Expected Behavior
When ./gradlew --console=plain is run I would expect to see a log of the various tasks as they are running, i.e. the same information that is present when using --console=rich but as a simple serial log.
Current Behavior
No output is produced.
Context (optional)
In automated environment gradle is being run as a sub-process of another system and that is timing out.  It would be useful to have a log of the tasks completed.
Steps to Reproduce
./gradlew --console=plain
Gradle version
8.1.1
Build scan URL (optional)
https://gradle.com/s/nbn6g3nga7bdm
Your Environment (optional)

Gradle 8.1.1
Build time:   2023-04-21 12:31:26 UTC
Revision:     1cf537a851c635c364a4214885f8b9798051175b
Kotlin:       1.8.10
Groovy:       3.0.15
Ant:          Apache Ant(TM) version 1.10.11 compiled on July 10 2021
JVM:          1.8.0_345 (Azul Systems, Inc. 25.345-b01)
OS:           Linux 5.19.0-50-generic amd64

Sorry that you're having trouble with Gradle!
Your issue appears to be a question about how to use Gradle. Your question might be answered in Gradle documentation or on our community Slack or forums. Find links to these resources on help.gradle.org.
If you think you have come across a Gradle bug, please file a new issue describing the problem and how to reproduce it.
If you think Gradle is missing a feature, please file a new issue describing your use case for the feature.

Your build scan actually has a list of tasks as an output. Please, provide a proper isolated reproducer in you think you found a bug.


Generate preparation files from sample sheets

The majority of the files changed are gzipped files I added for testing. Most of the interesting code is in prep.py and in seqpro.py. The later is a script interface that takes sample sheets and generates Qiita prep files.
cc @unique-identifier, @antgonza @charles-cowart

Thanks for the review @antgonza, tests are passing and comments have been addressed.

Thank you, one more comment. Do we need another reviewer?

Thanks for the suggestions, that makes a lot of sense. I've applied the change and tests are pssing. One reviewer should be fine, if you are OK then feel free to merge.

Thanks so much @antgonza!

On Aug 20, 2021, at 3:26 PM, Antonio Gonzalez @.***> wrote:
Merged #4 into master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Hosting redundant files

Is there a reason to host .psd files and bootstrap?

The psd files take up a lot of space and slow down uploads of a new branch
Bootstrap isn't too big but unless there's a reason to keep it here, we should switch to the CDN

If you want to host the psd files for future development, I'll instead make a site-resources or something repo so it doesn't get carried around with the site.

Yeah, we should have a separate repo for graphic sources and similar things.
I'm not sure whether bootstrap is a problem. Our build script can pull bootstrap from somewhere, so we don't need to put it to git.

I'll make the resources repo, guess we'll keep bootstrap around

Ok done, moved the psd files to site-resources, any other useful files there that are useful for site can be uploaded there.
cc @HSkogmo


build: Update to header 1.3.256

Update known-good
Generate source
cube.cpp: Move X11 includes after vulkan.hpp because Xlib.h defines macros True and False which conflict with ids used inside vulkan.hpp

CI Vulkan-Tools build queued with queue ID 3881.

CI Vulkan-Tools build queued with queue ID 3881.

CI Vulkan-Tools build # 1067 running.

CI Vulkan-Tools build # 1067 passed.

Sadly, my include-order hack does not work for builds with #define VK_USE_PLATFORM_XLIB_KHR
https://github.com/KhronosGroup/Vulkan-Hpp/issues/1608

Superseded by #830


Newlines issue

Hi,
I was checking text content for the note and generated HTML and it seems like newlines and breaks are not preserved.
I think they should be per code. Didn't find any issue here https://github.com/threeplanetssoftware/apple_cloud_notes_parser/blob/master/lib/AppleNote.rb#L641
But basically if I have empty line I expect  tag, but somehow I'm not getting it. I'll try to modify code and see if I can make it work, but just wanted to let you know.

sorry, it's not true. I'm just confused. Because brother displays everything correctly, but somehow in the Safari web inspector I don't see those tags. Closing for now.


Adding CoreBluetoothMock

This PR adds the following library: https://github.com/NordicSemiconductor/IOS-CoreBluetooth-Mock

Thank you!


Add ARM support

Issue #: Fixes #125
Description of changes:
Adds support for the ARM a1 instance class to the AMI builder.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@mcrute Hi there. I'm trying to use your script to create Arm AMI. But it looks like aws-cli isn't able to find the base image.
$ aws ec2 describe-images \
                --output text \
                --filters \
                        Name=owner-id,Values=137112412989 \
                        Name=virtualization-type,Values=hvm \
                        Name=root-device-type,Values=ebs \
                        Name=name,Values=amzn2-ami-minimal-hvm-* \
                        Name=architecture,Values=arm64 \
                        Name=state,Values=available \
                --query 'max_by(Images[], &CreationDate).ImageId'
None

This is just the first step of building arm image. Am I using it wrong? Thanks.

@left4taco what region are you trying to use for AMI building? A1 instances are not available in all regions yet and you won't be able to build the AMI in an unsupported region.

@mcrute I'm using us-west-2 Oregon. A1 instances are available in this region.
It turned out that aws ec2 describe-images command in Makefile is using the default one of the system, instead of the one specified in eks-worker-al2.json. Problem solved. Thanks.


JavaScript timer not running correctly when PyWebIO app is in the background.

I have a JavaScript timer in my PyWebIO app that, when is left in the background for a while (not active tab in user's browser), and then is made active again after a while, the countdown timer is glitching and is inaccurate.

This looks like a browser limitation, if you want to use js timing, please use the time difference instead of accumulating/subtracting a counter variable


Increase nmap_command length to 8096 to accommodate large masscan port listings

--top-ports 100 doesn't work in masscan, so each port and/or range needs to be specified.
https://github.com/rackerlabs/scantron/blob/32a68b3a6c91e50b33f998df2cba49773446a02a/master/django_scantron/models.py#L90

Try changing column type from CharField to TextField to accommodate large masscan commands.

index row size 3936 exceeds maximum 2712 for index "django_scantron_nmapcommand_nmap_command_key"
HINT:  Values larger than 1/3 of a buffer page cannot be indexed.
Consider a function index of an MD5 hash of the value, or use full text indexing.```

https://github.com/rackerlabs/scantron/pull/22


Getting "The server encountered an error. You may have inputted an invalid query." error when I try out the url in the initial api response

Trying out the url provided in the usage response (https://s.vercel.app/api?url=https://google.com&width=1280&height=720) is still giving me "The server encountered an error. You may have inputted an invalid query." error .

Can you try again? It is working for me now.

Yep its working now , thanks ! @RemiixInc


Jaeger tracing not working due to missing InitJaeger

Jaeger traces are not being sent from the cmd-forwarder-vpp instance--testing with all-in-one Jaeger deployment in k8s and JAEGER_AGENT_HOST set to point to the Jaeger agent.
Image:          ghcr.io/networkservicemesh/cmd-forwarder-vpp:v1.0.0

The other cmd-forwarder implementations invoke InitJaeger() in main.go but this is missing from cmd-forwarder-vpp.

Additionally, the daemonset in deployments-k8s needs to set dnsPolicy: ClusterFirstWithHostNet to lookup cluster services (like jaeger-agent).


Prevent 'examples' and 'test-support' publishing

Hi @johanhaleby
This should fix #138
I hope skipNexusStagingDeployMojo will work out (I do not know how to test it for sure)
The reason why I used skipNexusStagingDeployMojo for 'test-support' instead of just excluding it like 'examples' is because I think 'test-support' is needed when you publish (because you need to verify/execute tests)

Thanks a lot! If this works it's really great. It's something that can be really useful in other projects as well where I delete test/example projects manually on each release.

But just so I understand it correctly, what does <skipNexusStagingDeployMojo>true</skipNexusStagingDeployMojo> actually do? I want to upload the artifacts to maven central when I make a release. Will this not prevent it?

But just so I understand it correctly, what does <skipNexusStagingDeployMojo>true</skipNexusStagingDeployMojo> actually do?

Hi @johanhaleby
Setting skipNexusStagingDeployMojo to true for 'test-support' module prevents the module from being published to remote repository. I found this solution here.
The situation with 'example' module is different. It simply gets ignored when you specify -P release, because whenever you specify a list of desired profiles explicitly (with -P), all profiles which were activeByDefault get deactivated. So, the special examples-module profile which I created to switch on/off 'example' module gets deactivated with explicit -P release.
To sum up, with this PR, when you build or package locally (or on CI) without specifying explicit profiles, example module is included, because it's activeByDefault. When you perform release with -P release and nexus-staging-maven-plugin, neither example nor test-support get published.
The reason why test-support is not handled by custom profile like example is: you need test-support module, when you will build occurrent-project for publishing a release to Maven Central, but at the same time you do not want it to be published. You can't simply turn it off the same way like you can turn off 'example'. So, to prevent 'test-support' from being published, I used skipNexusStagingDeployMojo=true
How it was tested
The above statements were tested by publishing to local Nexus OSS. Here is the quick recipe:

docker run -d -p 8081:8081 --name nexus sonatype/nexus3 to quickly get Nexus OSS up and running
docker exec -it nexus bash -c 'cat /nexus-data/admin.password' to get a temp password for admin user
Go to http://localhost:8081/ and do some mouse clicks to perform initial configuration
Change $distributionManagement.snapshotRepository.url in your pom.xml to be http://localhost:8081/repository/maven-snapshots/, and comment-out gpg plugin
Execute mvn -P release clean deploy. Yes, this command, because OSS version of Nexus does not support staging feature. You will find published components on http://localhost:8081/service/rest/repository/browse/maven-snapshots/org/occurrent/
To conduct more tests, sign in as admin to local Nexus, go to http://localhost:8081/#browse/browse:maven-snapshots:org , select the root folder and delete it with a button

@gavvvr Thank you so much for this PR. It'll not only help Occurrent, but also several of my other open-source libraries. Releasing for example REST Assured, will also be much easier :)


Issue with Asserts?

I have a following tests that passes with "UnitTestEx.Xunit" Version="2.1.1"
		// Arrange
		using var test = CreateApiTester<Startup>();

		// Act
		var result = test
			.Controller<SampleController>()
			.Run(c => c.Get("thisIsATest"))
			.AssertOK()
			.AssertJson("{\"data\": \"this_is_a_test\"}");

but this also passes and shouldn't
		// Act
		var result = test
			.Controller<SampleController>()
			.Run(c => c.Get("thisIsATest"))
			.AssertOK()
			.Assert(new { foo="bar"});

Published NuGet package v2.1.2.


Allow setupFiles and setupTestFrameworkScriptFile to be asynchronous

Feature request
What is the current behavior?
Currently, setupFiles and setupTestFrameworkScriptFile can only setup environment synchronously.
What is the expected behavior?
It would be great if it Jest would run the test after awaiting any Promise that is the default export of any setupFile or setupTestFrameworkScriptFile the before running each test.

Is there anything that prevents you to await this code in beforeEach() hook?

Mostly cleanliness and DRY code. Nothing prevents me from doing a beforeEach() as that's what I'm doing now. However, I need to copy and paste the beforeEach() setup to each unit-test file. The point of setupFiles and setupTestFrameworkScriptFile is, as far as I understand, that common environment setup to all unit tests can be done in a centralized place.

We'll not be adding this for now as the complexity isn't really worth it. The recommended solution is to create a test utils file and use it like so:
const TestUtils = require('TestUtils');
beforeEach(TestUtils.setup);

OK, I understand your position. Thanks for having a look at it. ❤

Note that it's possible to put a beforeAll hook in your setupTestFrameworkScriptFile which avoids needing to put one in each test suite.

Oh wow, @tamlyn, it really worked for me! My god, for years I didn't know about this solution!


[Bug] Maximum call stack size exceeded if HMR not active

Description
I created an app with CRNA, then ejected to normal RNA, then followed this tutorial to allow typescript code, at the end when running in device the app returned error Maximum call stack exceeded, however it fixes when i activate HMR from the app menu.
Reproduction Steps
I've linked a repo, just clone, install deps, start React-Native packager and run in Android with react-native run-android, the red screen with error should show, if nothing shows (not even text) then close the app in emulator and open again.
Lastly to make that red screen go away, open the app menu with Ctrl + M (in linux, idk how to in OSX), and activate HMR.
Actual screen of error:

Sample Code
Repo mentioned above: https://github.com/luchillo17/react-native-error-repo
Additional Information

React Native version<EMAIL_ADDRESS>React version<EMAIL_ADDRESS>Platform: Android (don't have Mac for test in IOS)
Development Operating System: Ubuntu 17.04
Build tools: I've installed most android sdk versions:

+1

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.


Program cannot be opened after 1 use

I can use your program very well, thanks for your hard work!
Just 1 problem that the program can not be reopened after one download task.
Description of my user journey:

downloaded your zip and unziped it.
click YoutubeDownloader.exe to open it and download some playlist
can not reopen YoutubeDownloader.exe. (I clicked it and my mouse pointer showes a sand clock for about 0.1 sec. After that, nothing happened.)

My environment:

win10 enterprise edition with english language interface
use it with SSR since I am in China

My solution:
I delete my old folder and then unzip to install again. This trick always workes. However,  I am wondering why this happend? Anyone have the same issue with me?

Hi.
What version of the program did you launch that works?

The issue happened on  version 1.6.1.  I updated to 1.7.2 today and downloaded severl playlists. The issue do not show up anymore

Great then :)


OnComplete event called more than once for React JS

@svemula09 What version do you use? I just checked it out and it calls for me one time.
Probably some options may lead to the issue. If you are using the latest version, could you share your survey JSON and JavaScript code with us?
Thank you,
Andrew

My Code:
`import React, {PropTypes} from 'react';
import * as Survey from 'survey-react';
import {browserHistory} from 'react-router';
import {Modal} from 'react-bootstrap';
import {Segment} from 'semantic-ui-react';
import {connect} from "react-redux";
import {bindActionCreators} from "redux";
import * as PersonalSuggestionsActions from './PersonalSuggestions.actions';
class PersonalSuggestionsPage extends React.Component {
constructor() {
super();
this.surveyJSON =
{
  pages: [
    {
      name: "InitialInformation1",
      questions: [
        {
          type: "text",
          name: "age",
          title: "Age",
          isRequired: true,
          validators: [
            {
              type: "numeric",
              text: "Please choose an age ranging from 10 - 120",
              minValue: "10",
              maxValue: "120"
            }
          ],
          inputType: "number",
          placeHolder: "age"
        },
        {
          type: "radiogroup",
          name: "relationship",
          title: "Relationship status",
          isRequired: true,
          choices: [
            {
              value: "single",
              text: "Single"
            },
            {
              value: "married",
              text: "In a relationship"
            }
          ]
        }
      ]
    },
    {
      name: "InitialInformation2",
      questions: [
        {
          type: "radiogroup",
          name: "children",
          title: "Do you have children?",
          isRequired: true,
          choices: [
            {
              value: "yes",
              text: "Yes"
            },
            {
              value: "no",
              text: "No"
            }
          ]
        }
      ]
    },
    {
      name: "InitialInformation3",
      questions: [
        {
          type: "radiogroup",
          name: "adultDependents",
          title: "Do you have adult dependents?",
          isRequired: true,
          choices: [
            {
              value: "yes",
              text: "Yes"
            },
            {
              value: "no",
              text: "No"
            }
          ]
        }
      ]
    }
  ]
};
this.survey = new Survey.Model(this.surveyJSON);
this.survey.showProgressBar = "top";
this.customCSS = {
  "root": "",
  "header": "panel-heading",
  "body": "panel-body",
  "footer": "ui basic left-padded",
  "navigationButton": "ui  button mBackground",
  "navigation": {
    "complete": "",
    "prev": "",
    "next": ""
  },
  "progress": "ui progress warning",
  "progressBar": "m-bar",
  "pageTitle": "",
  "row": "",
  "question": {
    "root": "",
    "title": "",
    "comment": "form-control",
    "indent": 20
  },
  "error": {
    "root": "alert alert-danger",
    "icon": "glyphicon glyphicon-exclamation-sign",
    "item": ""
  },
  "checkbox": {
    "root": "form-inline",
    "item": "checkbox",
    "other": ""
  },
  "comment": "form-control",
  "dropdown": "form-control",
  "matrix": {
    "root": "table table-striped"
  },
  "matrixdropdown": {
    "root": "table"
  },
  "matrixdynamic": {
    "root": "table",
    "button": "button"
  },
  "multipletext": {
    "root": "table",
    "itemTitle": "",
    "itemValue": "form-control"
  },
  "radiogroup": {
    "root": "form-inline",
    "item": "radio",
    "other": ""
  },
  "rating": {
    "root": "btn-group",
    "item": "btn btn-default"
  },
  "text": "form-control",
  "window": {
    "root": "modal-content",
    "body": "modal-body",
    "header": {
      "root": "modal-header panel-title",
      "title": "pull-left",
      "button": "glyphicon pull-right",
      "buttonExpanded": "glyphicon pull-right glyphicon-chevron-up",
      "buttonCollapsed": "glyphicon pull-right glyphicon-chevron-down"
    }
  }
};

this.sendDataToServer = this.sendDataToServer.bind(this);

}
sendDataToServer(survey) {
debugger;
this.props.handleOnHide(false);
const surveyData = Object.assign({}, survey.data);
const resultAsString = JSON.stringify(surveyData);
window.dataLayer = {
"questionaireResults" : resultAsString
};
console.log(resultAsString);
this.props.actions.onQuestionnaireCompletion(surveyData)
  .then(() => { browserHistory.push('/recommendations/products'); });

}
render() {
return (

<Modal.Header closeButton>
Tell us about yourself
</Modal.Header>
<Modal.Body >

<Survey.Survey model={this.survey} onComplete={this.sendDataToServer}  css={this.customCSS}/>

</Modal.Body>

);
}
}
PersonalSuggestionsPage.propTypes = {
state: PropTypes.object.isRequired,
actions: PropTypes.object.isRequired,
handleOnHide: PropTypes.func.isRequired
};
PersonalSuggestionsPage.defaultProps = {};
function mapStateToProps(state, ownProps) {
return {
state: state
};
}
function mapDispatchToProps(dispatch) {
return {
actions: bindActionCreators(PersonalSuggestionsActions, dispatch)
};
}
export default connect(mapStateToProps, mapDispatchToProps)(PersonalSuggestionsPage);
`

File attached. Please verify - Thank you for responsive so quickly
PersonalSuggestionsPageCopy.txt

@svemula09 Thank you for provided code.
I've tried your surveyJSON, but in our example onComplete is called only once.
I've created react+redux+survey sample application to test your code. But have no success:

some inports are absent (import * as PersonalSuggestionsActions from './PersonalSuggestions.actions';)
after component created I got an empty page w/o any errors

I attached sample project: sample.zip


install tf 1.4 or up in Virtualenv still suffers this problem, uninstall enum and install enum34 do not help.

@csjunxu can you please elaborate on your issue? Please file out the template above and comment with any additional information.

It has been 15 days with no activity and the awaiting response label was assigned. Is this still an issue?


Add --indent and --tab command line options

Attempt to implement --indent and --tab command line options as suggested in https://github.com/01mf02/jaq/issues/152
Let me know if there is a better way to do this, I am a beginner at rustlang.

This is nice. Thanks a lot!


⚠ Bofrost.at has degraded performance

In f4dd339, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1964 ms

Resolved: Bofrost.at performance has improved in 740d7df.


Consider making Position(And possibly Range?) IComparable and adding more operator overloads

It is fairly common to want to check whether a position appears before or after another and it would be nice to have them be easily comparable(like this) instead of having to check the line and character separately.
Here is an example of where this might be useful.

I think that makes sense.
Should we apply the same thing to Range as well?

Should we apply the same thing to Range as well?

We haven't found the need for it yet. Maybe not given Roslyn doesn't do that either, https://github.com/dotnet/roslyn/blob/master/src/Compilers/Core/Portable/Text/LinePositionSpan.cs.

Thanks @david-driscoll


Update usage.md

Thanks Mitchell! I've merged your change as c8a46b92583b023d0b222f8dd553dbc656223300 to have a slightly preferable commit message on my side, but hopefully I used the correct syntax to credit you appropriately.


HandTracking precision

I have been developing gesture recognition function.
But I find when I'm moving hand, sometimes the landmarks don't track the hand.
Specially  gesture 'One',  when I move 'One' to the front of my face, the index finger always is missing, Mediapipe landmarks represent it as 'fist' not 'one'. when the fingers have crossed or overlapped, the tracking precision is lower.
Do you plan to improve the precision in that case? and did you also meet the problem when you developed the gesture? if there is some advice?
Thank you

Just out of curiosity, do you start with a closed fist and then make the one gesture? If so then most likely this has to do with the fact that it retrieves bounding boxes based on the previous landmark. It has a belief that the bounding box is much smaller and because of this, the entire hand is not fed into the network making it look like the landmark detector is less accurate than it actually is at least for this specific case.
A naive solution would be to have the palm detector run on every frame and this would improve the accuracy but at the great cost of inference time since the palm detector seems to be way more computationally expensive.
Try seeing if you still have a problem with the one gesture starting from an open hand position.

@pablovela5620
I have the palm detector run on every frame on your suggestion.
The palm rect was right on every frame, and the landmarks still didn't track the hand pose.

This is something we will address in future versions of hand tracking model


feat(node-sdk): add spanProcessors option

Which problem is this PR solving?
Since registered span processors are chained together via that active multispanprocessor, it makes sense to expose the option as an array of span processors. As such this change also deprecates the spanProcessor option in favor of the new, more flexiblespanProcessors option.
use case: suppose you are happy with the default batchspan processor, but rather not override any of its hooks and just add a subsequent processor that does something e.g. extracts baggage and adds the baggage entries to spans (side note: an off the shelf baggage extractor span processor might be nice!).
Fixes # (issue)
Short description of the changes
add a spanProcessors config option. convert the original/deprecated spanProcessor config to an array of one if used. we now loop over the spanProcessors and register them to the tracer provider.
n.b. if someone so happens to set both spanProcessor and spanProcessors it will default to using the latter, non deprecated option
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] The main span processor test now tests that an array is passed in successfully.

Checklist:

[x] Followed the style guidelines of this project
[x] Unit tests have been ~added~ modified
[x] Documentation has been updated

This is now ready for review. As per today's SIG this adds the spanProcessors (array) option to node-sdk

Related to https://github.com/open-telemetry/opentelemetry-js/issues/4451, it would be good to add LogProcessors as well.


feat: move custom text and links to settings

Everything LGTM. Tested out on the dev forum. Just found one link that needs to be fixed.


Replace client-sessions to avoid nuxt-oauth breaking

client-sessions dependency seems largely ignored and unmaintained. Is there a different dependency that can be used instead?
One of the reasons for this is that major browsers will soon ignore cookies with SameSite=None and unset Secure attribute.

Cookie “nuxtSession” will be soon rejected because it has the “sameSite” attribute set to “none” or an invalid value, without the “secure” attribute. To know more about the “sameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite

Luckily, it was pushed off in Chrome to a later release. But it seems to me that it will still happen in Firefox relatively soon.

@SpyTec Would this resolve the issue?
https://github.com/SohoHouse/nuxt-oauth/pull/63

@hamishhossack I believe it would. client-sessions doesn't support sameSite: none though, so if this is made user-configurable with client-sessions it needs to have a note about none being unsupported.
client-sessions had their last release 3 years ago on NPM. So I'd still advocate for replacing client-sessions

@SpyTec After some discussion we decided that we want to keep encrypted cookies. We can look at another lib if this also meets these standards.

client-sessions doesn't support sameSite: none though, so if this is made user-configurable with client-sessions it needs to have a note about none being unsupported.

Agreed.

@SpyTec @samtgarson https://www.npmjs.com/package/iron-session
Not adopted by many yet, but a good approach.