Running a "FreeSpec" causes "Test framework quit unexpectedly" error

When I run any "FreeSpec" (no matter if it's nested or not) from IntelliJ (no matter if it's the whole spec or a single test), I get a "Test framework quit unexpectedly" error with the following versions:
OS: MacOS 10.15.6
Java: 14
IntelliJ: 2020.2.1
KoTest: 4.2.2
KoTest Plugin: 1.1.16-IC-2020.1
Running the same "FreeSpec" from gradle works without any problems, so I guess it must have something to do with the plugin.
On the contrary, when I run a "StringSpec" from IntelliJ everything works as expected.
If I downgrade KoTest to 4.2.0.RC2, running the "FreeSpec" from IntelliJ works again.

Can you paste me the end of the classpath string.
Should look something like this:
io.kotest.engine.launcher.MainKt --spec
com.sksamuel.kotest.assertions.AssertionCounterFreeSpecTest --testpath
container should not need to have an assertion --reporter teamcity
On Thu, 27 Aug 2020 at 04:04, Thomas Krause<EMAIL_ADDRESS>wrote:

When I run any "FreeSpec" (no matter if it's nested or not) from IntelliJ
(no matter if it's the whole spec or a single test), I get a "Test
framework quit unexpectedly" error with the following versions:
OS: MacOS 10.15.6
Java: 14
IntelliJ: 2020.2.1
KoTest: 4.2.2
KoTest Plugin: 1.1.16-IC-2020.1
Running the same "FreeSpec" from gradle works without any problems, so I
guess it must have something to do with the plugin.
On the contrary, when I run a "StringSpec" from IntelliJ everything works
as expected.
If I downgrade KoTest to 4.2.0.RC2, running the "FreeSpec" from IntelliJ
works again.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kotest/kotest-intellij-plugin/issues/92, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFVSGWC5EHHFPKZYVS3MI3SCYOTDANCNFSM4QMX5NKQ
.

Sure, here you go: io.kotest.engine.launcher.MainKt --spec de.db.dbcs.dpp.BugSpec --reporter teamcity

That looks fine, shouldn't cause the Test framework quit unexpectedly error.
Are you sure there's no earlier versions of kotest floating about in the
build ?
On Thu, 27 Aug 2020 at 10:50, Thomas Krause<EMAIL_ADDRESS>wrote:

Sure, here you go: io.kotest.engine.launcher.MainKt --spec
de.db.dbcs.dpp.BugSpec --reporter teamcity
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kotest/kotest-intellij-plugin/issues/92#issuecomment-682033959,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFVSGQ7345JN5NR2RNTR5LSCZ6EHANCNFSM4QMX5NKQ
.

Yeah, I'm pretty sure. I did both a ./gradlew clean and ./gradlew build --refresh-dependencies. Also deleted the build directory of the project and deleted the IntelliJ run configurations and let them be recreated.
Is there any other spot that requires cleanup I might be missing?

No, I don't think it's cleanup. This error might happen if your test was
throwing an error at instantiation time.
Can you do something like
class Foo : FreeSpec() {
init {
"a" - {
"b" { }
}
}
}
And see what happens on that test ?
On Thu, 27 Aug 2020 at 16:11, Thomas Krause<EMAIL_ADDRESS>wrote:

Yeah, I'm pretty sure. I did both a ./gradlew clean and ./gradlew build
--refresh-dependencies. Also deleted the build directory of the project
and deleted the IntelliJ run configurations and let them be recreated.
Is there any other spot that requires cleanup I might be missing?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kotest/kotest-intellij-plugin/issues/92#issuecomment-682192784,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFVSGV3SB3CXRUJ2PZ2O6TSC3DWZANCNFSM4QMX5NKQ
.

This results in the same "Test framework quit unexpectedly" error. Also, it doesn't matter which part of the test I execute - I tried all three possibilities:
io.kotest.engine.launcher.MainKt --spec de.db.dbcs.dpp.Foo --reporter teamcity
io.kotest.engine.launcher.MainKt --spec de.db.dbcs.dpp.Foo --testpath a --reporter teamcity
io.kotest.engine.launcher.MainKt --spec de.db.dbcs.dpp.Foo --testpath a -- b --reporter teamcity

HI, I have the same problem, I use
intellij 2020.2.1
kotest plugin 1.1.16-IC-2020.1
kotest: 4.2.0
Java 14
kotlin 1.4.0
OS: MacOS 10.15.5

Try 4.2.2 Ruth.
On Fri, 28 Aug 2020, 06:29 Ruth<EMAIL_ADDRESS>wrote:

HI, I have the same problem, I use
intellij 2020.2.1
kotest plugin 1.1.16-IC-2020.1
kotest: 4.2.0
Java 14
kotlin 1.4.0
OS: MacOS 10.15.5
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kotest/kotest-intellij-plugin/issues/92#issuecomment-682474208,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFVSGRRU2FBEBJ2M4WNPCDSC6IIJANCNFSM4QMX5NKQ
.

@sksamuel it is as @Obirah says, same problem, with 4.2.0.RC2 it works, from 4.2.0.RC3 upwards it does not work anymore

@sksamuel will this be fixed soon? This is a very very irritating error...

@Obirah can you try 4.2.3?
Just came out moments ago. I tried it and so far I do not have that problem anymore :)

Ah cool, everything works, yes. Thank you for the information. :)

Yay.
On Tue, 1 Sep 2020 at 08:19, Thomas Krause<EMAIL_ADDRESS>wrote:

Ah cool, everything works, yes. Thank you for the information. :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kotest/kotest-intellij-plugin/issues/92#issuecomment-684847294,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFVSGSK7HIFKKDVLLV2O3TSDTYHDANCNFSM4QMX5NKQ
.


Open two projects with 100% CPU usage in the latest version

VSCode Version: 1.29.0
OS Version: MacOS 10.12.6

Steps to Reproduce:
1.Open two proiects
2.

Does this issue occur when all extensions are disabled?: Yes/No

Same problem here, even when only one project is opened.

VSCode Version: 1.29.0
OS: Arch Linux

Additional observations: The CPU usage goes up after a few minutes and stays at 100%. At the same time, several keyboard shortcuts stop working as expected (could be realated to #62994 ). Restarting VSCode helps, but only for a short period of time.

I experience the same problem here
VSCode Version: 1.29.0
OS: Windows 10 Pro

Can you get the full command line args of those processes using ps ax or the vscode Process Explorer?


New giftlist flow

Video of the flow this enables: https://drive.google.com/open?id=1nRKHRxehSR3n6xVwTLCKwDso0qm8XdtG
I cut pretty deep (perhaps too deep?) in the existing giftlist demo. I worry that I cut out some parts that were used as a testbed for existing development paths, particularly around some of the muxers. @mmandlis let me know your thoughts when you're back - I wonder if there's some opportunities to streamline this with some of the platform features, and in that way bring back some of the usefulness as a testbed?
There are two tests that have been disabled here. I'll file issues for both of them. They're big enough changes that I'm not sure this PR should be blocked on them, although that'd be better for repo health.

Subissues filed:

#1076
#1077
#1078

I agree, restoring at least one of the tests will be important. I'm going to focus on the selenium test (it exercises more of the flow), and will discuss the other with @mmandlis when she's back.


Updates for finishing classification tasks without getting stuck in SGD

updates to get SVC, MLP, and GP to not get stuck w/ skewed data by limiting total number of allowed iterations before solver terminates.
Added adaboost configuration json file.

I apologize, but I didn't put the max_iter variable in the root_variables key in the JSON files which were modified.  I can do another pull request, but think it might be easier if you made the changes directly?  I can do either, let me know what you prefer.

No problem, I can make the change on master.
Also, it looks like the GaussianProcessClassifier defaults to max_iter_predict=100. Is there a reason we should raise it to 5000?

I'm going to commit the SVM fix, and roll back the gp and mlp changes for now.

Ok, great, good point about the GP and MLP, better to leave it out.  Users can provide their own json configuration files if they wish to alter the default behavior.


add upsider to end user

Signed-off-by: Taylor Waggoner<EMAIL_ADDRESS>Signed-off-by: Taylor Waggoner<EMAIL_ADDRESS>

Howdy, @micnncim, @rara-tan, @vladfr! Once all three of you have accepted the CNCF Organization invitation, I'll approve this PR and get you added.

Thank you all for joining! Approving and merging this ✅


Remote sync with support for recursive subfolders

I'm developing some plugins for FacturaScripts available here on github, and I've found a "big" problem, I explain my case for a better understood, because I think that is a better way for work in big projects.
I use this structure of folders for development "/home/shawe/Projects" that contains "/home/shawe/Projects/FS_2015", "/home/shawe/Projects/plugin_1", "/home/shawe/Projects/plugin_2", ...
And for testing, the folder FS_2015 is synced to "/var/html" and the plugins are synced to "/var/html/plugins/plugin_X", with this I can work without lose nothing by error testing the changes, like delete plugin.
The problem is that remote-sync don't support "remote sync project upload/download/diff files/folders", doing a remote sync of every folder inside this level. Similar to do a manual "remote sync upload/download/diff file/folder" on every folder. The remote sync also is only working well if I "Open in new window" for every subfolder in my project folder, causing a big lose of time.
You can see on NetBeans that every subproject loaded on your workspace (aka Project Folder) have this type of sync for every subproject, and with your package using localhost as hostname we can have the same feature that is very usefull, but require this style of recursive sync by folder with different configuration.
For me, I think that only is needed add some extra commands for get this feature, that maybe can be do it with only adding some little changes.

Duplicate with #160


[WIP] Debug and test mv-lookup

Summary
It should be mv-lookup issue.

Close it, since it should be fixed by https://github.com/scroll-tech/halo2/pull/83. Thanks for @kunxian-xia!


Sample Issue (Checking)

Create a text file and push it to the repository.

give it to me

give it to me

This is a sample issue just to check the working correctly, It is not for counting. The event will start from 9PM today.

Hi verma, just make a commit once. We need for checking the correctness of working in git


Question about batch size vs num frames

Hello again,
I have one last question that I'm still unclear about. In this implementation, the size of the input being fed into the network is (B x C x H x W) with B being the number of frames correct? Or is it actually (B x F x C x H x W) with F being the number of frames?

Hi @cyrilzakka
The initial input shape is of BF x C x H x W, batch_size and num_frames flattened together.
Before the transformer encoder phase, all the computations are independent among each frame.
The idea behind flattening batch_size and num_frame is that pytorch's conv2d operations take input of (batch, channel, height, width).
In order to make computations separate and avoid the use of 'for loops', we flatten batch_size and num_frames.

Thanks for the answer! Would you mind pointing me at the line of code responsible for converting B x F x C X H X W to BF x C X H X W and then back prior to the transformer?

https://github.com/sukjunhwang/IFC/blob/cfa38e3f31bbcf48b3426c413deeb558d37edceb/projects/IFC/ifc/ifc.py#L396-L405
Given the code above, all frames in all batched videos go into "images" list.
So, it is already the same to flattening B and F.
https://github.com/sukjunhwang/IFC/blob/cfa38e3f31bbcf48b3426c413deeb558d37edceb/projects/IFC/ifc/ifc.py#L192
Therefore, the shape of "video" tensor would be BF x 3 x H x W -- 3 denoting BGR

Thank you for your time!


[5.1] Add the ability to fill a collection with a range of data

This adds a new method to Collection which allows us to fill it with data, for a given range. This can either be prepended or appended.
My given use case for this is with an Eloquent query. I may take 30 results but due to a lack of data, have 0/1 row(s). If my UI requires 30 steps of data, I could loop it and fill the void, but this is a much cleaner, integrated solution.

Why don't you use the name range for it?

I thought about this, fill seems more apt, but if range is preferred, I'll change it.

pad seems to make more sense

I was thinking more array_fill.

CS fixed @GrahamCampbell :)

Yeah but why are you not using the same params and order as array_fill? Isn't it easier to do:
    public function fill($start, $num, $value)
    {
        $this->items = array_fill($start, $num, $value);

        return $this;
    }

This is more flexible in that you're able to start from a different index.

:+1: for pad.
array_fill does something different than this function. It just adds a certain amount of elements, whereas array_pad adds elements up to a certain amount of total elements.

Ok, yeah, pad makes more sense then.

That trailing boolean argument just feels wrong.

That trailing boolean argument just feels wrong.

Padding before or after data is pretty nice though, it's very similar to sortBy, which takes a bool.

Why don't you use array_pad? Then we could add padding before, by just passing a negative amount.

I'll have a play :)

If we keep it simple, how does this look?
/**
 * Pads a collection with items.
 *
 * @param  int    $amount
 * @param  mixed  $value
 * @return $this
 */
public function pad($amount, $value = null)
{
    $this->items = array_pad($this->items, $amount, $value);

    return $this;
}

From looking at the other methods, it should be:
return new static(array_pad($this->items, $amount, $value));

Heh, I noticed that just as I went back to it.
If everyone agrees on this, then I'll re-push it :)

Perhaps extend collection to add the method you need.


Request: Generate for Nest.js 8

Can you provide a little more detail on this issue? Does it not work at all on Nest8? Are there bugs when it does?

Can you provide a little more detail on this issue?


Dataset issues

Hello, I would like to ask if the dataset you gave ISCX VPN, USTC_TFC public dataset is processed at the flow level or at the package level. Looking forward to your reply, thank you!

Hello, I would like to ask if the dataset you gave ISCX VPN, USTC_TFC public dataset is processed at the flow level or at the package level. Looking forward to your reply, thank you!

Hi, the processing is done at both levels, the flow-level directory is for flow-level data, while the one in the corresponding root directory is for packet-level.


llamactl deploy error  where deploy in remote serverapi

clienthost$  llamactl -s http://serverapihost:4501 -t 20 deploy ./python_fullstack.yaml
Error: Not Found

serverapihost$  python -m llama_deploy.apiserver
INFO:     Started server process [988]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://<IP_ADDRESS>:4501 (Press CTRL+C to quit)
INFO:     <IP_ADDRESS>:45480 - "POST /deployments/create HTTP/1.1" 404 Not Found

Can you double check the version of llama_deploy you're using? /deployments/create was added later so my best guess would be you're running an earlier version.

hi, dockerhub image : llamaindex/llama-deploy:v0.2.1
cliente llama-deploy==0.2.1

I can't reproduce it, here is what I'm doing, from the root of the repo.
$ cd examples/quick_start
$ docker run -p 4501:4501 -v .:/opt/quickstart -w /opt/quickstart llamaindex/llama-deploy:v0.2.1
dadddad7b79b3d099afcaae132470e603dca82c32edbd7b1f68bebd5831d4b87
$ llamactl --version
llamactl, version 0.2.1
$ llamactl deploy ./quick_start.yml
Deployment successful: QuickStart

Can you try to do the same and let me know if it works?


feat: disable year and month navigation if min date specified

Can you provide a Plunker with this in action?

I found som bug, I fix it. Here is the plunker http://plnkr.co/edit/q4fuEcFqGSgzs85RsblW?p=preview

Overall, I like this PR, although I would like to have a second opinion here.

I'm not sure if we want to disable viewing dates outside of the enabled date range. Users may fond it useful to lookup dates/days even though they can't select them.

Closing as outdated - feel free to file a new PR implementing this feature on top of current master if desired.


header file missing since update of V4R package

Looking at the latest builds of v4r_ros_wrappers, e.g. at https://lcas.lincoln.ac.uk/jenkins/job/ros-indigo-singleview-object-recognizer_binarydeb_trusty_amd64/8/console we see that a header is missing:
fatal error: v4r/recognition/singleview_object_recognizer.h: No such file or directory
 #include <v4r/recognition/singleview_object_recognizer.h>
                                                          ^
compilation terminated.

This only happens since V4R has been re-released to version 1.0.10 (or maybe already 1.0.9, not sure). Right now we have a broken repository due to this bug.

OK, this is showing again with V4R 1.1.0. This was wrongly reported in V4R: https://github.com/strands-project/v4r/issues/36 but belongs here...

fixed now


Fractional amount should be displayed instead of "0" if user clicks on max button having CELO balance <0.001 in the account

Frequency: 100%
Repro on build version: Test Flight Build V1.22.4, Android Internal Build V1.22.4
Repro on devices: iPhone 12(14.7.1), Samsung Galaxy M31(10.0), Redmi Note 8(10.0), One plus 7t(11.0), Samsung Galaxy A8+ (8.0)
Pre-condition:
1.User must have “<0.001” balance displayed on the CELO screen in their account.
2.User must be on the withdraw CELO screen and must have copied a valid account address.
Repro Steps:
1.Tap and paste account address.
2.Tap on “Max” button in “Amount CELO” field & observe 0 appears.
3.Enter 0.00008 amount in “Amount CELO” field & Observe review button gets enabled.
Current Behavior: When user clicks on max button “0” is seen in the amount field
Expected Behavior: Fractional amount should be seen after clicking on max button instead of 0
Impact: Bad user experience
Investigation :When user enters “0.0008” fractional amount then the review button gets enabled and after confirmation the transaction fails.
Attachment: Zero Balance Issue.mp4

Hey @MuckT, We have verified this issue using Test Flight build V1.29.2 & Android Internal build V1.29.2 & observed that the issue is still reproducible.
Devices: iPhone 13 mini(15.1.1), Samsung Galaxy A9 Pro(8.0)
Attachment: Zero balance.mp4
Thanks!!


OS no longer builds with rustc nightly 1.37.0: error: language item required, but not found: eh_personality

Hi,
First, many thanks for the series, it's amazing! I came to do the latest post today, but my OS no longer builds, presumably due to a compiler upgrade because nothing else has changed.
Compiler:
nightly-x86_64-apple-darwin unchanged - rustc 1.37.0-nightly (d3e2cec29 2019-06-26)
Error:
error: language item required, but not found: eh_personality``
The internet seems to think this is something to do with needing panic=abort? I have that in my target json file. I added it under [profile.dev] but that results in a different error:
error: linking with cc failed: exit code: 1

Hi @mt-inside
This behaviour is probably due to the nightly toolchain, which is unstable by nature. From time to time, a a nightly build my fail either on your main project or either on one of the dependencies because it is broken.
Two "solutions" : downgrade your nightly toolchain to a previous working version (using rustup); or wait for a future nightly build to solve the issue.
Hope it helps.

@mt-inside

First, many thanks for the series, it's amazing!

Thanks, I'm glad that you like it! :)

I came to do the latest post today, but my OS no longer builds, presumably due to a compiler upgrade because nothing else has changed.

That's strange. I just tried building it with the latest nightly and it worked without errors. We also have a CI job that tries to build the project with the latest nightly once a day. Here is the build with the exact nighly that you're using and it seems like it worked fine too: https://dev.azure.com/phil-opp/blog_os/_build/results?buildId=1698
So it seems like something in your code is slightly wrong. My guess is that maybe the panic=abort syntax in your target JSON is "panic": "abort" instead of the correct "panic-strategy": "abort"?

Hmm.
Yep, I've got
    "panic-strategy": "abort", in my JSON
It won't build on stable, fails to parse bootloader = {version = "^0.5", features = ["map_physical_memory"]}
And new nightly (rustc 1.37.0-nightly (8ebd67e4e 2019-06-27)), same problem. There's no line number on the errors, is there anything I can do to dig further?
I've modified the code slightly from the blog but not a huge amount. It's here if anyone wants to try: https://github.com/mt-inside/mtos
I'll try to build it on a clean machine soon.

I tried your project and it compiled and ran fine for me using bootimage run. Have you tried a cargo clean before building?
Versions:
> rustc --version --verbose
rustc 1.37.0-nightly (8ebd67e4e 2019-06-27)
binary: rustc
commit-hash: 8ebd67e4ee394cad9441a801f2022724ae7e07db
commit-date: 2019-06-27
host: x86_64-unknown-linux-gnu
release: 1.37.0-nightly
LLVM version: 8.0

> cargo version --verbose
cargo 1.37.0-nightly (4c1fa54d1 2019-06-24)
release: 1.37.0
commit-hash: 4c1fa54d10f58d69ac9ff55be68e1b1c25ecb816
commit-date: 2019-06-24

> cargo xbuild --version
cargo-xbuild 0.5.12

> bootimage --version
bootimage 0.7.5

Ok, right, my mistake (obviously).
It'd been a while since I'd worked on this, and I forgot how to build it. bootimage build works fine, cargo build doesn't. I at least assumed cargo build was a subset; that it would build the library then bootimage would build the disk image around it.
Sorry for wasting your time :/ And thanks so much for taking the time to help me out!

No worries!
cargo build doesn't work because it tries to build your OS for your host system by default (e.g. as a macOS userspace executable). You need to pass --target x86_64-unknown-raw.json as argument to compile for a bare-metal target. This will still not work because cargo isn't able to build the sysroot (the core and compiler_builtins crates) on its own yet. So you need a tool like cargo-xbuild that builds the sysroot for you. So a working command that only builds the kernel should be cargo xbuild --target x86_64-unknown-raw.json.
I agree that this isn't really intuitive. For this reason I updated the blog recently to add support for more standard-like build commands. We still need cargo-xbuild for now, but we no longer need to pass the --target argument (since we override the default target) and instead of bootimage run we now can do cargo xrun. The same is true for testing. With https://github.com/rust-lang/rfcs/pull/2663 merged, we will support the normal cargo build/cargo run/etc build commands, so that this confusion should go away.

I think we can close this issue. Let me know if you have other questions!


[Backport] [2.4] Support OpenSSL Provider with default Netty allocator (#5460)

Backport of https://github.com/opensearch-project/OpenSearch/pull/5460 to 2.4

Codecov Report

Merging #5500 (97d8145) into 2.4 (e15a7f8) will increase coverage by 0.04%.
The diff coverage is 18.51%.

@@             Coverage Diff              @@
##                2.4    #5500      +/-   ##
============================================
+ Coverage     70.56%   70.61%   +0.04%
- Complexity    58300    58323      +23
============================================
  Files          4696     4697       +1
  Lines        278890   278913      +23
  Branches      40737    40738       +1
============================================
+ Hits         196809   196961     +152
+ Misses        65698    65572     -126
+ Partials      16383    16380       -3

Impacted Files
Coverage Δ

...search/transport/Netty4NioServerSocketChannel.java
0.00% <0.00%> (ø)

.../java/org/opensearch/transport/NettyAllocator.java
45.45% <0.00%> (ø)

...va/org/opensearch/common/bytes/BytesReference.java
74.28% <100.00%> (-7.54%)
:arrow_down:

.../index/shard/IndexShardNotRecoveringException.java
0.00% <0.00%> (-50.00%)
:arrow_down:

...h/action/ingest/SimulateDocumentVerboseResult.java
60.71% <0.00%> (-39.29%)
:arrow_down:

...cluster/coordination/PublishClusterStateStats.java
33.33% <0.00%> (-37.51%)
:arrow_down:

...java/org/opensearch/threadpool/ThreadPoolInfo.java
56.25% <0.00%> (-37.50%)
:arrow_down:

...ensearch/client/indices/DetailAnalyzeResponse.java
20.54% <0.00%> (-34.25%)
:arrow_down:

.../java/org/opensearch/index/reindex/RemoteInfo.java
50.45% <0.00%> (-28.45%)
:arrow_down:

.../opensearch/client/indices/GetMappingsRequest.java
47.05% <0.00%> (-23.53%)
:arrow_down:

... and 456 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Weird result when doing multishot read on STDIN

This is related to #1185.
I'm setting up a buffer ring, then doing io_uring_prep_read_multishot on fd 0. When data is available, a CQE is received. The data is received correctly in the first available buffer in the buffer ring, however, cqe->flags is 0, and does not have IORING_CQE_F_BUFFER set, nor the buffer id in the upper word, even if it is non-zero.
I can detect the absence of IORING_CQE_F_MORE and switch automatically to reissuing single shot read ops, but the first read is cloberred because I have no way of knowing in which buffer it is.
I hope this is clear enough.

What kernel are you running?

Oh I see it, must be a recent(ish) kernel. I'll post the fix. If you want me to include you in the Reported-by: tag in the commit, please post what name and email you'd like me to use to properly attribute the bug report to you.

Sorry I'm on 6.8.0.
My name: Sharon Rosner
email<EMAIL_ADDRESS>Thanks!

Thanks! Commit is here:
https://git.kernel.dk/cgit/linux/commit/?h=io_uring-6.12&id=c9d952b9103b600ddafc5d1c0e2f2dbd30f0b805
and should go upstream within a week and then make its way back to the stable kernels. 6.8 doesn't have a current stable series, so might be worthwhile to update to 6.10-stable once the commit has been queued up for that series.


Render dropdown above the input if there is not room below

Dropdown should be rendered above the input whether there're no space below it.
Example:
Scroll down to the Select2
http://plnkr.co/edit/uvXvxEeuOHgvimHH6U6z?p=preview
It works in the Select2 examples https://select2.github.io/examples.html

Duplicate of #148

Closing as already addressed in the library by #1212


I found that you may used test-split-data for validation and test in the same time.

It seems to be something wrong. And the split of DSIFN Dataset is really weird，
the test set is too small.

Hi @Rit-Shi
Hey, thanks for pointing out this mistake. I will correct this. The test and val splits of the DSIFN dataset should be interchanged. Instead, you may use val split as the test set when training.
Best,
Chaminda

OK, I see. Thank you for your reply！


Set errorformat for use in quickfix window

Seems like it's necessary to repeat the errorformat used in the
Syntastic plugin, because the option assignment needs to have the spaces
escaped.
Maybe there's a better way to do this so that the string isn't repeated twice?

Good improvement!
I don't know the syntastic issue about errorformat, but it is better than no errorformat config.
I'll review the patch.

Seems good.  Thanks!


Selection Issues

When trying to select a feature directly from the Add-in using the Select button in the Modify tab, the features on the map aren't being selected.

After selecting a feature using the core Select tool, and then unselecting the feature, the "Save Edits" button still exists in the symbol editor in the Symbol and Label panes. This is ok. However, when clicking on this button after features are no longer selected, an empty error dialogue pops up:

Not sure if this is supposed to work or not, but when selecting a feature on the map, and navigating to the Enter Coordinates pane in the Add-in, and entering a new set of coordinates, and selecting Save Edits, the symbol doesn't move to the new coordinate location, rather the Save Edits button seems to freeze.

@tlauver update: this is likely only an issue with Pro 1.3. I'm running on 1.3.5820. Not sure why this has changed between the versions.

I tested this (on 1.4) and wasn't able to repro the phantom message box - but the "Save Edits" button definitely shouldn't be showing up when nothing selected so looking into this.

Addressed in #123 to address (from original issue comments):

Clear selection if nothing selected by tool + Disable Save Edits button if nothing selected
Disable Enter Coords tab if editing

@csmoore validated fixed, closing.


Training Code

Thanks a lot for your brilliant work!
Is there any plan to release the training code?

Plan to release our training code and post-processed DeepFashion-MultiModal dataset in early next month. Stay tuned!


Documentation: Update peter-schorn-soft-player://login-callback redirect URI must be configured in Spotify Dashboard

This information was missing in the documentation. Other than that, great app, seem to work! :)

This redirect URI is only required if you are using Soft Player, not this server. I will update the documentation for Soft Player.


[Draft] Add minicpmv finetune script

Hi All,  I developed the fine-tuning code for minicpmv based on the provided Chat code. Tested to run successfully on 8XA100 GPU environment. The currently implemented code only supports single image.
I hope this will help model users.

Certainly! Here's a polished and structured GitHub Pull Request (PR) description for adding the fine-tune script to the MiniCPM-V project:

# Add MiniCPM-V Fine-Tuning Script

## Description

Hi all,

I have developed and added the fine-tuning code for MiniCPM-V based on the provided Chat code. This implementation has been tested successfully in an 8xA100 GPU environment. Currently, the code supports fine-tuning with a single image.

I hope this contribution will be helpful for model users aiming to fine-tune MiniCPM-V for their specific needs.

## Type of Change

- [x] New feature (non-breaking change which adds functionality)

## Implementation

The fine-tune script leverages the existing Chat code base but modifies it to handle fine-tuning tasks for MiniCPM-V. The current implementation is designed to process single images effectively.

### Main Features

1. **Fine-Tuning on Single Image**: The script is focused on enabling fine-tuning for a single image.
2. **Tested with 8xA100 GPUs**: Ensures that the script is effective in a high-performance GPU environment, offering reliable results.

### Example Usage

Here's a basic example of how you can use the fine-tuning script:

```bash
python finetune_minicpmv.py --image_path path/to/image --output_dir path/to/output

Prerequisites

Ensure you have access to an environment with 8xA100 GPUs or equivalent.
Necessary dependencies and libraries should be installed as indicated in the project's documentation.

Checklist

[x] I have written and conducted tests that showcase the fine-tuning script works as intended.
[x] I have run all necessary pre-commit checks.
[x] My changes generate no new warnings.
[x] I have updated the required documentation to reflect these additions.
[x] I have added my name to the CONTRIBUTORS.md or verified it already exists there.

Additional Notes

This fine-tuning script is a valuable addition for users needing to tailor MiniCPM-V to their particular datasets and tasks.
Future enhancements might include support for batch processing of multiple images and optimizations for different hardware setups.

End of PR description

This PR description includes:

1. **Description**: Outlines the purpose of the PR and provides context for the changes.
2. **Type of Change**: Specifies it as a new feature.
3. **Implementation**: Details what the changes are, main features, and how to use the new functionality.
4. **Checklist**: Confirms that all development and testing prerequisites have been met.
5. **Additional Notes**: Provides extra information and potential future directions.

Feel free to adjust any details to match any specific templates or practices your project may have!


Count applied & failed canonical user commands

Blocks #1204

Yes, this seems like it would be directly related. But I don't think this is strictly needed for this issue unless this story is dependent upon those counts first.

There are 4 permutations of status and canonicity to be indexed

applied and canonical
failed and canonical
applied and non-canonical
failed and non-canonical


MI VS Code docs

Description:
With the new MI VS Code plugin, we can replace/add the existing integration pages.

Need to identify the pages to be replaced/changed
Need to decide on a method to add the new content

Closing as completed. @DinithiDiaz hope this is fine to close.


Fix coordinated omission

Thank you, @arturo-salinas! I will have a look. 🔍

It looks like there is an issue in the way the ClOrdID(11) field is used to convey the send time:
philadelphia (bug-coordinated-omission) λ java -jar examples/initiator/philadelphia-initiator.jar localhost 4000 50000 10000
Warming up...
Benchmarking...
Results (n = 50000)

   50.00%:<PHONE_NUMBER>76.10 µs
   90.00%:<PHONE_NUMBER>76.10 µs
   99.00%:<PHONE_NUMBER>76.10 µs
   99.90%:<PHONE_NUMBER>76.10 µs
   99.99%:<PHONE_NUMBER>76.10 µs
  100.00%:<PHONE_NUMBER>76.10 µs

What about just putting the nanosecond timestamp directly to the ClOrdID(11) field to avoid the arithmetic on the receiving side?

Yes, the arithmetic was wrong because the warming and benchmark phases were mixed up. One solution is to reset the index after the warming phase but your suggestion is much better. I implemented. Thank you!
java -jar philadelphia-initiator.jar localhost 4000 50000 10000

Warming up...
Benchmarking...
Results (n = 50000)

   50.00%:     361.22 µs
   90.00%:  127139.84 µs
   99.00%:  170917.89 µs
   99.90%:  178388.99 µs
   99.99%:  179568.64 µs
  100.00%:  179961.86 µs

Yes, the arithmetic was wrong because the warming and benchmark phases were mixed up. One solution is to reset the index after the warming phase but your suggestion is much better. I implemented. Thank you!
java -jar philadelphia-initiator.jar localhost 4000 50000 10000

Warming up...
Benchmarking...
Results (n = 50000)

   50.00%:     361.22 µs
   90.00%:  127139.84 µs
   99.00%:  170917.89 µs
   99.90%:  178388.99 µs
   99.99%:  179568.64 µs
  100.00%:  179961.86 µs

On what platform did you get these numbers? 😃 I get quite a bit more reasonable ones on my laptop:
philadelphia (bug-coordinated-omission) λ java -jar examples/initiator/philadelphia-initiator.jar localhost 4000 50000 10000
Warming up...
Benchmarking...
Results (n = 50000)

   50.00%:      19.18 µs
   90.00%:      37.60 µs
   99.00%:      53.57 µs
   99.90%:      80.19 µs
   99.99%:     222.46 µs
  100.00%:     318.72 µs

Thank you, @arturo-salinas! 🙌


pull request for e2e test at 01/08/2017 09:15:10

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


Load pins from iree-requirements.txt in setup.py.

Without this, pip installs require the unqualified iree-compiler package.
With this, pip installs require the iree-compiler>=[version pin] package (note that get_version_spec here is inserting the >=, even if the requirements file has ==)
This helps for https://github.com/nod-ai/sharktank/tree/main?tab=readme-ov-file#install-development-packages with these instructions:
# Clone and install editable iree-turbine dep in deps/
pip install -f https://iree.dev/pip-release-links.html --src deps \
  -e "git+https://github.com/iree-org/iree-turbine.git#egg=shark-turbine"

Closing this since it's stale.


How to add magnetic sensor?

Not sure what you mean by that. Does LinkerKit have a magnetic sensor?

Hi, yes it does! I'm trying to add a sensor and a buzzer. It seems like the
buzzer operates the same way as an LED, but I don't seem to know how to
configure the magnetic sensor. I thought it would be the same as a button,
just on or off, but not sure how to proceed.
On Fri, Aug 2, 2019 at 10:49 AM Helge Heß<EMAIL_ADDRESS>wrote:

Not sure what you mean by that. Does LinkerKit have a magnetic sensor?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SwiftyLinkerKit/SwiftyLinkerKit/issues/1?email_source=notifications&email_token=AACR2ANVB7XGMUGDXGTRC6DQCRCQ5A5CNFSM4IHXY77KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3N6ZZA#issuecomment-517729508,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACR2APB3NDYLDGRMQXFLALQCRCQ5ANCNFSM4IHXY77A
.

I don't have such and I'm not much of a hardware guy either :-) I think they usually have a Python sample which can be ported over? That's what I think I did for the 7-segment.

Okay no problem. I will send a pull request if I figure it out!
On Fri, Aug 2, 2019 at 11:10 AM Helge Heß<EMAIL_ADDRESS>wrote:

I don't have such and I'm not much of a hardware guy either :-) I think
they usually have a Python sample which can be ported over? That's what I
think I did for the 7-segment.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SwiftyLinkerKit/SwiftyLinkerKit/issues/1?email_source=notifications&email_token=AACR2AN2AMHCE7BHW2Y7QOTQCRE5TA5CNFSM4IHXY77KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3OAVYA#issuecomment-517737184,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACR2AO4JOIAUZK7M2BKTU3QCRE5TANCNFSM4IHXY77A
.


Limitations: we recommend ensuring only one health probe per port is configured to all load balancing rules per backend instance.

As per this ICM: https://portal.microsofticm.com/imp/v3/incidents/details/480234707/home, The Azure load balancer product group recommends ensuring only one health probe per port is configured to all load balancing rules per backend instance. We are currently evaluating the longer-term fix for this issue, which may include adding validation to ensure this configuration is blocked, as it is an unsupported use case.
As per my understanding, this is a limitation that we need to ensure that only one health probe per port is configured to all load balancing rules per backend instance.
Please check and update from your side.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 0e1e7cb2-c5a7-7122-c729-dc259db99a40
Version Independent ID: 45c6fd72-5114-fcda-0bab-2d80ac6bed33
Content: Azure Load Balancer health probes
Content Source: articles/load-balancer/load-balancer-custom-probe-overview.md
Service: load-balancer
GitHub Login: @mbender-ms
Microsoft Alias: mbender

@vikedesai
Thanks for your feedback! We will investigate and update as appropriate.

@vikedesai
Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can take a look at it accordingly.
@mbender-ms
Can you please check and add your comments on this doc update request as applicable.

#please-close


vim-configurable: rename from vim_configurable

Motivation for this change
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

could you reference the document that mandate it please ?

Dashes are now valid as part of identifiers and attribute names.

https://nixos.org/manual/nix/stable/release-notes/rl-1.2.html?highlight=dash#release-12-2012-12-06
most of the packages that use _ in the name are probably pre-2012
this isn't a upstream package so the below doesn't apply to this

Dashes in the package name should be preserved in new variable names, rather than converted to underscores or camel cased — e.g., http-parser instead of http_parser or httpParser. The hyphenated style is preferred in all three package names.

https://nixos.org/manual/nixpkgs/stable/#sec-package-naming

could you reference the document that mandate it please ?

any objections to merging?

Looks like useless churn to me, especially as it's a nixpkgs specific function. If we have to change it, maybe we can can change it to vimWrapper to align it with neovim wrapper ? maybe it's not a wrapper though if it changes vim compilation options though.

I expect a number of people use vim_configurable today for customization.  Even with the alias, these types of changes are best accomplished as a holistic upgrade across all legacy packages to the new convention.  That way users can follow a single rule rather than having to consider variants that might change piecemeal over releases.
The quoted text does not seem to imply that there is imminent need for this remediation, although the new-style convention does appear more prominently.  Is this part of a broader effort to do a cleanup or is there some other motivation?

is there some other motivation?

https://github.com/NixOS/nixpkgs/issues/145344#issuecomment-965058781

Then why vim_configurable rather vim.configurable or vim-configurable?

Is this still considered or abandoned?

Superseded by https://github.com/NixOS/nixpkgs/pull/204438


Provide a utility to extract features from texts?

Congratulations on the wonderful work!
I can't wait to try the model. Do you have plan to provide a utility to extract vectors for some sample texts. Just as the extract_features.py in the BERT repo? Or is there other ways to easily run the model against some raw texts?

Good point. This example snippet is a use case of extracting features (seq_out will be what you want). We might also add a python file to specifically do that in the future.


Team page updates

Team page updates

Checklist:

[ ] I have manually tested all workflows
[ ] I have performed a self-review of my own code
[ ] I have added automated tests for my code

@ajinkyaa Please check the CI tests that are failing for this PR.

@supriya3105 I think someone from ror side to work on this. Those are failing because new routes addition for teams page.


Keep original request

Before a copy was used, this patch
uses the original request can be useful
in case of using gorilla as it keeps
a context thanks to the pointer of the
request.

Sorry for the Huge delay . I had issues with gorilla/context but it seems to be fixed on the gorilla side


feat: reduce icon file size

Description
Current, the transpiled .js file of each of our icons contains some boilerplate to support extremely old browsers that don't understand the ...spread operator:
function _extends() { _extends = Object.assign ? Object.assign.bind() : function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }

This code is not necessary at all, yet it is included in every single icon file, and will be incorporated many times over into the final build. This doesn't actually impact bundle size much in practice because so much redundancy gets heavily compressed by gzip before being sent over the wire. But it's still adding complexity to these files that isn't needed, so I'd like to remove it.
Before: 3,102,133 bytes for 2,320 items
After: 2,179,463 bytes for 2,320 items
Deploy Preview
TBD
Merge Checklist

[ ] If your update includes visual changes, have they been reviewed by a designer? Send them a link to the Netlify deploy preview, if applicable.
[ ] Does your change adhere to the documented style conventions?
[ ] Do any prop types have missing descriptions in the Props API tables in the documentation site (check deploy preview)?
[ ] Were your changes tested using all available themes (see theme switcher in the header of the deploy preview, under the "Settings" icon)?
[ ] Were your changes tested in the example app?
[ ] Is there adequate test coverage for your changes?
[ ] Consider whether this change needs to reviewed/QA'ed for accessibility (a11y). If so, please request an a11y review for the PR in the #wg-paragon Open edX Slack channel.

Post-merge Checklist

[ ] Verify your changes were released to NPM at the expected version.
[ ] If you'd like, share your contribution in #show-and-tell.
[ ] 🎉 🙌 Celebrate! Thanks for your contribution.

Thanks for the pull request, @bradenmacdonald!
What's next?
Please work through the following steps to get your changes ready for engineering review:
:radio_button: Get product approval
If you haven't already, check this list to see if your contribution needs to go through the product review process.

If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.

This process (including the steps you'll need to take) is documented here.

If it doesn't, simply proceed with the next step.

:radio_button: Provide context
To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

Dependencies

This PR must be merged before / after / at the same time as ...

Blockers

This PR is waiting for OEP-1234 to be accepted.

Timeline information

This PR must be merged by XX date because ...

Partner information

This is for a course on edx.org.

Supporting documentation
Relevant Open edX discussion forum threads

:radio_button: Get a green build
If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.
:radio_button: Let us know that your PR is ready for review:
Who will review my changes?
This repository is currently maintained by @openedx/paragon-working-group.  Tag them in a comment and let them know that your changes are ready for review.
Where can I find more information?
If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

Overview of Review Process for Community Contributions
Pull Request Status Guide
Making changes to your pull request

When can I expect my changes to be merged?
Our goal is to get community contributions seen and reviewed as efficiently as possible.
However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

The size and impact of the changes that it introduces
The need for product review
Maintenance status of the parent repository

:bulb: As a result it may take up to several weeks or months to complete a review and merge your PR.

Closing for now in favor of https://github.com/openedx/paragon/pull/3284 which has incorporated these same changes.


-w Write un success file event when there is a error

What is the purpose of your issue?

[*] Bug
[ ] Feature Request
[ ] Question
[ ] Other

Description

While there is this bug #820 I was trying to use -w and -s to write file that I managed to download so when I run it again it would take less time than the --overwrite skip option. But it write it in the success file.
The commande line that I used: spotdl -l ./playlistname.txt --overwrite skip -w _skip.txt -sk _skip.txt
Log

Not going to be fixed. Try v3 instead,  own an issue of your like new functionality and reference it under new features.


ibis_table.execute(limit=None) does not set limit to None

Hi-
The limit for table.execute() states that it is set by default to 'None'. However, the limit seems to be set at 10,000 by default, and remains set at 10,000 even when I expressly type 'limit=None' as a parameter.
However if I expressly change the limit to a certain number, such as 200,000,000,000 it does successfully download all the rows of my ginormous table.
For example, with verbose mode enabled:
# create ibis object from distinct vars table
distinct_vars = con.table('global_variants', database='grch37')

SELECT * FROM grch37.`global_variants` LIMIT 0

# limit table to just the columns we need to output to vcf
distinct_df = distinct_vars[['chrom', 'pos', 'ref', 'alt']]

# download table from ibis table connection object to local memory
distinct_df = distinct_vars.execute(limit=None)

SELECT *
FROM grch37.`global_variants`
LIMIT 10000

# download table from ibis table connection object to local memory
 distinct_df = distinct_vars.execute(limit=30000)

SELECT *
FROM grch37.`global_variants`
LIMIT 30000

Thanks -- I shall investigate

This is no wfixed in upstream


Add dep check to travis build

This change is

test-me-please

womp womp :/ no dep in the travis environment, it seems.

@raybejjani this change is just to make sure that Gopkg files are not committed to repo malformed. Added this info to commit message.
I wonder if dep install script will work on travis.

Coverage decreased (-0.004%) to 42.003% when pulling 0956b0ad73f5be2e54137dde26721942e52788ac on nebril:add-dep-check into b2ff83adff68a557e12119ebb2cdf9d89a6cf017 on cilium:master.

Files being patched don't exist in 1.3 dropping needs backport 1.3 tag.


Devicelab failure: timed out waiting for app to launch

For example:
2020-10-13T09:43:33.468252: stdout: [ +268 ms] [100%] Connecting to remote debug server
stdout: [        ] -------------------------
2020-10-13T09:43:33.505865: stdout: [  +37 ms] (lldb) command source -s 0 '/tmp/0F665124-2212-4DE0-A65A-3A5A8324DC71/fruitstrap-lldb-prep-cmds-87b7be763fbf79fb324179b431f26198d2338da2'
stdout: [        ] Executing commands in '/tmp/0F665124-2212-4DE0-A65A-3A5A8324DC71/fruitstrap-lldb-prep-cmds-87b7be763fbf79fb324179b431f26198d2338da2'.
2020-10-13T09:43:33.505961: stdout: [        ] (lldb)     platform select remote-ios --sysroot '/Users/flutter/Library/Developer/Xcode/iOS DeviceSupport/13.1.3 (17A878)/Symbols'
2020-10-13T09:43:33.506096: stdout: [        ]   Platform: remote-ios
stdout: [        ]  Connected: no
2020-10-13T09:43:33.506262: stdout: [        ]   SDK Path: "/Users/flutter/Library/Developer/Xcode/iOS DeviceSupport/13.1.3 (17A878)/Symbols"
2020-10-13T09:43:33.506327: stdout: [        ] (lldb)     target create "/Users/flutter/.cocoon/flutter/dev/integration_tests/platform_interaction/build/ios/iphoneos/Runner.app"
2020-10-13T09:43:36.760753: stdout: [+3254 ms] Current executable set to '/Users/flutter/.cocoon/flutter/dev/integration_tests/platform_interaction/build/ios/iphoneos/Runner.app' (arm64).
stdout: [        ] (lldb)     script fruitstrap_device_app="/private/var/containers/Bundle/Application/AEF078C8-955B-4FD2-9ED4-CE7B28F7CC9B/Runner.app"
2020-10-13T09:43:36.974998: stdout: [ +214 ms] (lldb)     script fruitstrap_connect_url="connect://<IP_ADDRESS>:62737"
2020-10-13T09:43:36.975311: stdout: [        ] (lldb)     script fruitstrap_output_path=""
2020-10-13T09:43:36.975794: stdout: [        ] (lldb)     script fruitstrap_error_path=""
2020-10-13T09:43:36.976224: stdout: [        ] (lldb)     target modules search-paths add /usr "/Users/flutter/Library/Developer/Xcode/iOS DeviceSupport/13.1.3 (17A878)/Symbols/usr" /System "/Users/flutter/Library/Developer/Xcode/iOS DeviceSupport/13.1.3 (17A878)/Symbols/System" "/private/var/containers/Bundle/Application/AEF078C8-955B-4FD2-9ED4-CE7B28F7CC9B" "/Users/flutter/.cocoon/flutter/dev/integration_tests/platform_interaction/build/ios/iphoneos" "/var/containers/Bundle/Application/AEF078C8-955B-4FD2-9ED4-CE7B28F7CC9B" "/Users/flutter/.cocoon/flutter/dev/integration_tests/platform_interaction/build/ios/iphoneos" /Developer "/Users/flutter/Library/Developer/Xcode/iOS DeviceSupport/13.1.3 (17A878)/Symbols/Developer"
2020-10-13T09:43:36.990976: stdout: [  +14 ms] (lldb)     command script import "/tmp/0F665124-2212-4DE0-A65A-3A5A8324DC71/fruitstrap_87b7be763fbf79fb324179b431f26198d2338da2.py"
2020-10-13T09:43:36.995190: stdout: [   +4 ms] (lldb)     command script add -f fruitstrap_87b7be763fbf79fb324179b431f26198d2338da2.connect_command connect
stdout: [        ] (lldb)     command script add -s asynchronous -f fruitstrap_87b7be763fbf79fb324179b431f26198d2338da2.run_command run
2020-10-13T09:43:36.995296: stdout: [        ] (lldb)     command script add -s asynchronous -f fruitstrap_87b7be763fbf79fb324179b431f26198d2338da2.autoexit_command autoexit
stdout: [        ] (lldb)     command script add -s asynchronous -f fruitstrap_87b7be763fbf79fb324179b431f26198d2338da2.safequit_command safequit
2020-10-13T09:43:36.995347: stdout: [        ] (lldb)     connect
2020-10-13T09:43:37.025240: stdout: [  +29 ms] (lldb)     run
2020-10-13T09:44:07.054785: stdout: [+30030 ms] error: process launch failed: timed out waiting for app to launch
2020-10-13T09:44:07.054899: stderr: [        ] Could not run build/ios/iphoneos/Runner.app on 87b7be763fbf79fb324179b431f26198d2338da2.
2020-10-13T09:44:07.054953: stderr: [        ] Try launching Xcode and selecting "Product > Run" to fix the problem:
2020-10-13T09:44:07.055108: stderr: [        ]   open ios/Runner.xcworkspace
2020-10-13T09:44:07.055470: stdout: [        ] Installing and launching... (completed in 38.5s)
2020-10-13T09:44:07.059515: stdout: [   +4 ms] "flutter drive" took 54,621ms.
2020-10-13T09:44:07.064924: stderr: [   +5 ms] Application failed to start. Will not run test. Quitting.
2020-10-13T09:44:07.065435: stderr: [        ]
stderr:            #0      throwToolExit (package:flutter_tools/src/base/common.dart:14:3)
stderr:            #1      DriveCommand.runCommand (package:flutter_tools/src/commands/drive.dart:244:9)

Many questions:

What actual process here is failing?
do we know some possible reasons?
Would retrying work, or is this a "phone in a bad state" problem?

@xster @jmagman

The tree is closed on this, and repeated re-runs, and reverts probably won't get it open again, so I'm marking this P0, and adding to the infra ticket queue.

Haven't seen this issue before. Seems like an Xcode error surfacing through ios-deploy. Did we create a devicelab specific provisioning profile that may have expired?
@godofredoc

Do we have access to the machine? Worth trying the ios-deploy command directly (seen in the logs just above where you copy pasted).

Lowering to P1, I reverted the last commit which was causing the tree-blocking failures. Though the number of iOS failures this week is still quite large

I bet lldb didn't exit and is still attached, so the second attempt can never attach and it times out.

The first failure is the old Connection closed before full header was received chestnut, THEN it times out trying to attach the second time.
2020-10-13T11:10:58.049126: stdout: [  +26 ms] (lldb)     run
2020-10-13T11:10:58.176178: stdout: [ +127 ms] success
2020-10-13T11:10:58.176327: stdout: [        ] Application launched on the device. Waiting for observatory port.
2020-10-13T11:10:58.188815: stdout: [  +12 ms] Attempting to forward device port 64291 to host port 61344
2020-10-13T11:10:58.189274: stdout: [        ] executing: /Users/flutter/.cocoon/flutter/bin/cache/artifacts/usbmuxd/iproxy 61344:64291 --udid 43ad2fda7991b34fe1acbda82f9e2fd3d6ddc9f7
2020-10-13T11:10:59.203876: stdout: [+1014 ms] Forwarded port ForwardedPort HOST:61344 to DEVICE:64291
2020-10-13T11:10:59.254275: stdout: [  +50 ms] HttpException: Connection closed before full header was received, uri = http://localhost:61344/ws
2020-10-13T11:11:01.271949: stdout: [+2017 ms] HttpException: , uri = http://localhost:61344/ws
2020-10-13T11:11:03.287616: stdout: [+2015 ms] HttpException: , uri = http://localhost:61344/ws
2020-10-13T11:11:05.303009: stdout: [+2015 ms] HttpException: , uri = http://localhost:61344/ws
2020-10-13T11:11:07.318346: stdout: [+2015 ms] HttpException: , uri = http://localhost:61344/ws
2020-10-13T11:11:09.329968: stdout: [+2011 ms] Failed to connect directly, falling back to log scanning
2020-10-13T11:11:14.348626: stdout: [+5018 ms] Failed to connect with log scanning
2020-10-13T11:11:14.348830: stdout: [        ] Installing and launching... (completed in 22.6s)
2020-10-13T11:11:14.349157: stderr: [        ] Error running application on iPhone.
2020-10-13T11:11:14.351664: stdout: [   +2 ms] "flutter run" took 32,784ms.

and the next try times out:
2020-10-13T11:18:07.019349: stdout: [        ] (lldb)     connect
2020-10-13T11:18:07.048593: stdout: [  +29 ms] (lldb)     run
2020-10-13T11:18:37.078992: stdout: [+30031 ms] error: process launch failed: timed out waiting for app to launch

platform_view_ios__start_up_37ebe3d_3.log

Good find. That's what @DanielEdrisian noticed as well in https://github.com/flutter/flutter/issues/67333. Our agent code should probably look for orphaned debuggers and explicitly kill them before trying each time.

I think it would be better if this could be handled by the tool, since this presumably would affect everyone developing flutter on iOS?

The simulator codepath is different, it doesn't attach with lldb, it can log scan directly from the host.

How would you handle it on the tool? I don't think it would be right to actually do anything besides surfacing a better warning? Having an existing run through CLI/ios-deploy/lldb or through Xcode/lldb isn't really telling what the intentions are. Might be leftovers, might be user actually debugging native code/plugins/custom engines.

The debugger is missing a detach when the attach succeeds, but the VM service connection fails.  I have the fix, I just need to spend 10x the time to unit test it.

This fix won't actually make the tests pass since something is causing it to not connect to the VM service--it will just prevent the timeout on retry.


DIGITAL CLOCK

Project title
DIGITAL CLOCK
Project Description
A web-app based Digital Clock.
Stack:
And in order to tick the check box just but x inside them for example - [x] like this. Please delete options that are not relevant.

[x] Html
[x] CSS
[x] JavaScript

/assign


refactor IpcContract test into setUp and individual components

This is part of an ongoing process to clean up tests and run end to end USDC tests. This PR is intended to be a straightforward refactor of the file contracts/test/sdk/IpcContract.t.sol so that:

this PR is simple to review
the PR Expand IpcContract.t.sol to test handleIpcMessage #698 can simply focus on adding additional tests

This seems to be included in https://github.com/consensus-shipyard/ipc/pull/698. Please reopen if I missed something and this is not actually duplicative, @snissn.


Update to 2.8.0

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Revert "stats: update method names of counter"

Reverts lyft/envoy-mobile#1134

Can you elaborate on the intent here? Also the PR description needs sign off


Funnel not exposed to internet

I deployed the code with Funnel to Fly and it could not be accessed from the internet from outside of my Tailnet.
I noticed that the DNS did not even resolve so there's no way it could even try to connect.
Tailscale has a green note saying FUNNEL.

That's weird. Do you have the right node attribute set on that node?

@Xe are you referring to the following?

Is your tclip node tagged? If it's tagged it won't match autogroup:member.

Yep it’s tagged but I also put tag:pastebin in the ACL and also on the pastebin box.

Hi @vysecurity - sorry for the delay here. I'm going to close this issue for now as it's been a while, however if you are still having this issue on the latest version of tclip could you reopen and share more details here on your setup so we can reproduce? Adding -tsnet-verbose / TSNET_VERBOSE may also help surface more logs.
On the other hand if this is an issue with your tailnet / not specifically tclip, please feel free to open a ticket with support and we can take a look.!


Expose Msg with Msg(...)

I'm writing a component based on your component and I need that your component expose Msg as Msg(..) as is explained in this issue https://github.com/elm-lang/error-message-catalog/issues/215

Hello Gabriel! I'm a bit reluctant about exposing the whole Msg subtypes because then any internal change in the Msg implementation would imply a major version update when publishing the package as explained here: https://medium.com/@ghivert/designing-api-in-elm-opaque-types-ce9d5f113033.
Maybe I can expose some helper functions like isTransitioning : Toasty.Msg -> Bool to let you extract the internal message.
Would that help with what you are trying to achieve?

Hi @pablen!, I ended creating those helpers functions, and I think it is ok. I was trying to create my own toast component which was just exactly as yours but without having to pass the config register to each function. Here you can see the code and how I exposed those helper functions.
If you think there is an approach better to achieve the same thing, please let me know it :)

Oh, so I think I misunderstood what you were trying to do here.
In your case I think those helper functions are a bit redundant because you can use the Success, Warning and Error types as constructor functions without the need of defining new helper functions.
You can take a look at the demo code, you'll notice I'm using those types in such a way: https://github.com/pablen/toasty/blob/e8c0a8f49fd99d47b58540403cf53969f7c81e1d/examples/src/App.elm#L50-L61
Also, look a few lines above how I defined a single addToast helper function to avoid having to pass the config record around every time: https://github.com/pablen/toasty/blob/e8c0a8f49fd99d47b58540403cf53969f7c81e1d/examples/src/App.elm#L37-L39
I think you'll be good to go with this!


Export node order

This exports node order as an inputLabel attribute.
(For example, this allows special handling for the case of side-by-side nodes.)

Hello, I'm curious if anyone is currently reviewing and merging PRs?  And also if anyone has assumed responsibility for cutting new releases?  From the contributor activity charts, looks like @cpettitt or @lutzroeder might be the persons to talk to.
Or if one of the 375 forks is more active or has supplanted this repo as the primary dagre implementation?

@cliffsun91, @rustedgrail, @RohitPaul0007, @lutzroeder. It would be great if you review and merge the open PRs. Thanks in advance.


Visibility's Viewshed service script not producing expected results.

Widget
Visibility
Version of widget
WAB 2.2/ArcMap 10.4.1
Bug or Enhancement
Using a local, projected (World Azimuthal Equidistant) raster dataset (TIF) as a source elevation dataset. I can run the tool without warning or errors, but:

The tool does not produce a viewshed, only fullwedge and wedge datasets.
The features produced are about 1600 miles from the location of their input Observers.

DTED source used is from https://github.com/Esri/military-tools-geoprocessing-toolbox/tree/dev/testdata/Elevation/Source/SRTM30M
Repo Steps or Enhancement details

Open ArcMap (I used 10.4.1)
Project n36.dt1 to World Azimuthal Equidistant using Project Raster. My output was n36prj.tif.
Open Viewshed from \stemapp\widgets\Visibility\gpservices\Viewshed\Viewshed.tbx
Select single observer point, use default parameters, click OK.

Executing: Viewshed "Feature Set" 3000 40 120 20 1000 in_memory\viewshed in_memory\wedge in_memory\fullwedge
Start Time: Mon Jan 09 14:45:45 2017
Running script Viewshed...
Completed script Viewshed...
Succeeded at Mon Jan 09 14:45:46 2017 (Elapsed Time: 0.81 seconds)

So the tool produces three output feature classes: viewshed, wedge, and fullwedge.
Viewshed is emtpy:

Wedge and fullwedge have one result each:

However the resulting wedges are nowhere near the surface, and therefore not near the selected observer location.

@mfunk I was getting the same results while testing today.

Assuming it's something in the .PY I'm going to check it out. @kgonzago  which branch should I pull from to work on a fix for Visibility widget?

@mfunk Master branch.

Making a few changes and so far tool output looks good. Still need to test as a service, then see if it works in the widget.

'projecting' input points to same SR as elevation.
symbology (.LYR) for all three output layers.
Error if input surface is NOT projected.

@kgonzago needs to merge #769, but afterwards I'd like @Dbarnes1 to verify the fix once it is done.


CYF-South Africa | Jordy Mukandayi | Wireframe | Week 1

Learners, PR Template
Self checklist

[ ] I have committed my files one by one, on purpose, and for a reason
[ ] I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
[ ] I have tested my changes
[ ] My changes follow the style guide
[ ] My changes meet the requirements of this task

Changelist
Briefly explain your PR.
Questions
Ask any questions you have for your reviewer.

Needs Review

@JordyMu your work was missed because it had no label. Please label your work with Needs Review, so mentors can find it.
Mentors look at this view to see what work they have to do: https://github.com/CodeYourFuture/Module-User-Focused-Data/pulls?q=is%3Apr+is%3Aopen+label%3A"Needs+Review"


Refactor Email Send Logic

Move email send logic from mobile app to a cloud service.

You mean the feedback form submit?

Yes

Does this actually need to be moved? Would be posting to AWS which then posts to eforms.

Since MachForms handles the actual sending of the email, this may not be required, let's revisit

Can the send feature in the app itself be async so user aren't blocked on the UI while the network request is made?

Closing this issue, created a new issue #157 to look into a non-blocking UI


Fix lucia-auth peer dependency for adapter-mongoose and adapter-prisma

Closing this in favor of #323


Fix: routing and deep linking

fixes #130

fix deep linking
fix navigator routing

currently due to wrong/non working auth logic, redirection was stuck at auth
even if publicKey was generated, stored and retreived, it was not getting fetched properly
thus the code was assuming the user to not have auth and redirect to login on any link render
thus this logic was fixed and retrievePublicKey was used instead of useAuth

overall code cleanup
fixed screens

Good job @bhavyagosai! If you just redo the change in the comment. Gonna merged it tomorrow


Added the MIT License badge and changed the license section

Related Issue
Closes: #108
Description of Changes
Changed the Licenses section and Added MIT Licenses badge
For example:

Added a new function to handle XYZ.
Updated the ABC module to fix the bug.
Refactored code in the DEF class for improved performance.
-->

Checklist:

[x] My code adheres to the established style guidelines of this project.
[x] I have conducted a self-review of my code.
[x] I have included comments in areas that may be difficult to understand.
[x] I have made corresponding updates to the project documentation.
[x] My changes have not introduced any new warnings.

Screenshots
Please provide any necessary screenshots to illustrate the changes made.

@abhijeet141 Please review this

@abhijeet141 Please review this, GSSoC'23 is coming to an end and I want some point to sustain in top 100. Please.

@1Shubham7 Actually this repo is not getting evaluated on the leaderboard


Header block

Adds a HeaderBlock component: issue #3839

@tomhazledine I guess this can be closed now?


Remove generic comments

A bit of clean-up

Hmm, I vaguely remember some kind of standard tooling relying on comments or the first statement not being in the first line in those includes. Or maybe it was just a nightmare. 😰

Halloween must be close 🎃 👻
Most classes don't have these comments and have been fine for years. These are just leftovers.


libinput-gestures: 2.38 -> 2.39

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/libinput-gestures/versions.
meta.description for libinput-gestures is: '"Gesture mapper for libinput"'.
Compare changes on GitHub

Checks done (click to expand)

built on NixOS
/nix/store/hpxvpwg2p71d9kdv835shplmxmidbl53-libinput-gestures-2.39/bin/.libinput-gestures-wrapped passed the binary check.
/nix/store/hpxvpwg2p71d9kdv835shplmxmidbl53-libinput-gestures-2.39/bin/libinput-gestures passed the binary check.
2 of 2 passed binary check by having a zero exit code.
0 of 2 passed binary check by having the new version present in output.
found 2.39 with grep in /nix/store/hpxvpwg2p71d9kdv835shplmxmidbl53-libinput-gestures-2.39
directory tree listing: https://gist.github.com/a403ca598245b2e78a78d9b15d75bc7a
du listing: https://gist.github.com/8f72e6a2dd1ffa546aaaf21a076a50c8

Outpath report (click to expand)

Outpath difference report
3 total rebuild paths
1 package rebuilds
1 x86_64-linux rebuilds
1 i686-linux rebuilds
0 x86_64-darwin rebuilds
1 aarch64-linux rebuilds
First ten rebuilds by attrpath
libinput-gestures

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hpxvpwg2p71d9kdv835shplmxmidbl53-libinput-gestures-2.39 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A libinput-gestures https://github.com/r-ryantm/nixpkgs/archive/28c4e861f2c010ef667d54faea52fe9470fa5fd9.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hpxvpwg2p71d9kdv835shplmxmidbl53-libinput-gestures-2.39
ls -la /nix/store/hpxvpwg2p71d9kdv835shplmxmidbl53-libinput-gestures-2.39/bin

cc @teozkr for testing.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: libinput-gestures
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on aarch64-linux (full log)
Attempted: libinput-gestures
Partial log (click to expand)
'README.md' -> '/nix/store/k7svhjkd4clwkc0zg032gggh0sqab00m-libinput-gestures-2.39/share/doc/libinput-gestures/README.md'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/k7svhjkd4clwkc0zg032gggh0sqab00m-libinput-gestures-2.39
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/k7svhjkd4clwkc0zg032gggh0sqab00m-libinput-gestures-2.39/bin
patching script interpreter paths in /nix/store/k7svhjkd4clwkc0zg032gggh0sqab00m-libinput-gestures-2.39
/nix/store/k7svhjkd4clwkc0zg032gggh0sqab00m-libinput-gestures-2.39/bin/libinput-gestures: interpreter directive changed from "/usr/bin/env python3" to "/nix/store/16wqq9ihrkdim3x8xs1lkxa3f4l3p3ir-python3-3.6.6/bin/python3"
/nix/store/k7svhjkd4clwkc0zg032gggh0sqab00m-libinput-gestures-2.39/bin/libinput-gestures-setup: interpreter directive changed from "/bin/bash" to "/nix/store/dsyc1z7ck08ga7l0b1jcxx35wj69qcii-bash-4.4-p23/bin/bash"
checking for references to /build in /nix/store/k7svhjkd4clwkc0zg032gggh0sqab00m-libinput-gestures-2.39...
/nix/store/k7svhjkd4clwkc0zg032gggh0sqab00m-libinput-gestures-2.39

Success on x86_64-linux (full log)
Attempted: libinput-gestures
Partial log (click to expand)
'README.md' -> '/nix/store/hpxvpwg2p71d9kdv835shplmxmidbl53-libinput-gestures-2.39/share/doc/libinput-gestures/README.md'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/hpxvpwg2p71d9kdv835shplmxmidbl53-libinput-gestures-2.39
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/hpxvpwg2p71d9kdv835shplmxmidbl53-libinput-gestures-2.39/bin
patching script interpreter paths in /nix/store/hpxvpwg2p71d9kdv835shplmxmidbl53-libinput-gestures-2.39
/nix/store/hpxvpwg2p71d9kdv835shplmxmidbl53-libinput-gestures-2.39/bin/libinput-gestures-setup: interpreter directive changed from "/bin/bash" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/bash"
/nix/store/hpxvpwg2p71d9kdv835shplmxmidbl53-libinput-gestures-2.39/bin/libinput-gestures: interpreter directive changed from "/usr/bin/env python3" to "/nix/store/bwfygfcdvis9wd1c1v51xwnwhw1hx0a0-python3-3.6.6/bin/python3"
checking for references to /build in /nix/store/hpxvpwg2p71d9kdv835shplmxmidbl53-libinput-gestures-2.39...
/nix/store/hpxvpwg2p71d9kdv835shplmxmidbl53-libinput-gestures-2.39


ECDH support for longer coordinates

Work in progress. It's not very intrusive change to allow these and it would make KBPGP more compatible with GnuPG.
History behind this PR:
During go-crypto development, I've discovered that GnuPG will accept longer numbers when encoding coordinates for ECDH public point - it does not have to match curve param P length. Of course this works as long as the points are correct, so this is essentially comes down to zero-padding the numbers. KBPGP is very strict about this right now, checking if MPI that it is reading is exact length as P bit length.
The same payloads in test, tried in gpg2:
» gpg2
gpg: Go ahead and type your message ...

-----BEGIN PGP MESSAGE-----
Version: Keybase OpenPGP v2.0.58
Comment: https://keybase.io/crypto

wcA0A6pi0WoSlxTXEgWzBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/ZTuFZa3
go5bAv8SLZd5vTQzjQiqiXfaQUX3dQu+zytgEeiugIshlJ7JykTPGhdQFVSiKQYe
a4RKpgbn8SkNhyIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAaR1kL+5vnf9E0wv
vGDKg1jo0uEGYVodxTwk8QuqbxWiCT/jOH9kybjECSPlkDkbUIOezOfaTlwde0Wo
XUNWZ/WrMOJHerpQvMvPNjEwMSGnsIZPh8/Hafj7j8OauMG5EWgCrzsxv1mgsRXP
QkNog/5dM9JIAcT8RpDaFecdhRag6ZPuRKmNuhiFtR7o0spcqX2UkJ3FPB7UydX3
ch9PkTNL1BVD++JqYQE9eaIqlCTAsHwCgO6pQkQqPUvB
=y7cW
-----END PGP MESSAGE-----

gpg: encrypted with 521-bit ECDH key, ID AA62D16A129714D7, created 2016-10-15
      "nist key tester<EMAIL_ADDRESS>purpleschala

The test failure is related to https://github.com/keybase/kbpgp/issues/133

BTW, rebase to get the tests to pass...

Thank you! Please hold on with the merge, I want to test few other payloads in both GnuPG and KBPGP, then I will also commit the compiled code.

Hm, I should also check how it works with encoding public keys.

Let's close this for now so it doesn't get merged by mistake - the alternative one is probably better.


Using absolute paths to uploaded images

Tried to find a way to replace the relative with absolute paths when uploading images.
The hack I'm using is to change the upload_attachment.json, but this requires changing the codebase.
Anyone knowns a better way?

Sorry for late.
You can customize its path with changing attachment_upload_to in django-summernote settings.


Ingest API (Part 3)

Created by: @pepe-zamarripa Aug 02 2022 at 14:39 CET
Last updated: Aug 02 2022 at 14:41 CET
ClickUp ID: IK-3706
Given
The GO SDK Ingest API
When
Customer wants to ingest data
Then
A python SDK ingest API should be available.
Please update the wiki when feature complete: https://www.notion.so/indykite/SDK-feature-comparison-8d8333a604fc4327b0a9c14ad02f42e8
The GO interface can be found here: https://buf.build/indykite/indykiteapis.
Use the following command to generate the required proto bufs: https://github.com/indykite/jarvis-sdk-python/blob/master/gen_proto.sh
echo "Generating protobufs ..."
buf generate buf.build/indykite/indykiteapis
buf generate buf.build/envoyproxy/protoc-gen-validate
echo "Rewriting the imports..."
packages=("indykite" "validate")
for package in  $ {packages[@]}; do
       find jarvis_sdk/indykite/. -name '*.py' -exec sed -i -e "s/from  $ {package}/from jarvis_sdk. $ {package}/g" {} ;
done
echo "Done"

Commented by: @pepe-zamarripa Aug 02 2022 at 14:41 CET
@martasd when you come back from vacations, we need to update the title and the content of the ticket, so we can differentiate the scope during each sprint. cc @bayegan

Closing - duplicate of https://github.com/indykite/jarvis-sdk-python/issues/73

Hi @pepe-zamarripa. Why did you reopen this issue?

Hi @martasd! I re-opened the issue because its status is blocked.


Rescanning images should use a queuing system

If a large number of images are rescanned at once on a LAMP server with PHP as a FastCGI (didn't test other configurations), this will cause runaway memory usage. Concrete5 5.7 also becomes very unresponsive to queries during this time and does not allow visitors to load any webpages. Some hosts have automated processes which kill scripts that grow too large as well, and since rescanning uses third party libraries outside of PHP, the memory_limit directive does not limit the memory usage.
Much like the "Index Search Engine - All" automated job, having a progress bar and queuing the job in small chunks will prevent these issues from occurring.
I only know enough about this stuff to get myself in trouble, so forgive me if I am wrong or misunderstand how this all works :-).

I don't think that this should be a queue-able job, as it isn't something that is a job really,
If we made something new like "queue-able tasks" which uses the same backend would be nice.
Off the top of my head this could be used for file rescanning as stated above, moving files between storage locations, mass editing of page properties, etc.
Just what I think, even if we don't go for a whole new system, I could port this over to jobs, the downside, is that rescanning can be destructive, which kinda scares me sometimes.

IIRC the "Empty trash" function is implemented as a queue-able task. Maybe we could take the same approach for the image rescanning function...

Hey guys!
I tried a gallery addon, and it had the same problem, it ran my VPS memory out and forcefully rebooted. Is there any kind of garbage collection that goes on when the function(s) are called to generate thumbnails or re-sizing? It almost seems like the task is not cleaning up memory after each image; only once the whole batch is done.

Alright so update.
I now limit imagemagick's memory use to 512 mb. Concrete5 is NOT happy about it. If I rescan files and hit that memory limit, the following error occurs:
{"error":{"message":"The identifier fID is missing for a query of Concrete\Core\File\File"},"errors":["The identifier fID is missing for a query of Concrete\Core\File\File"]}
When I increase it to 768, it works fine, unless I try rescanning more files at once.
Here's my server's imagemagick settings:
262144000 RESOURCETYPE_AREA
-1 RESOURCETYPE_DISK
6000 RESOURCETYPE_FILE
2097152000 RESOURCETYPE_MAP
768000000 RESOURCETYPE_MEMORY

I'm experiencing the same problem however on a shared hosting. Would you know how to fix this?

@arvi use smaller images. That's the biggest factor. Also, if you have a lot of images on a webpage and you clear the cache, it will have to regenerate all those images when you visit that webpage again.
This is the most annoying problem in C5 for me right now.

This is fixed in the 5.7.x branch and will be in <IP_ADDRESS>

Thanks @aembler


additional parameters to be upload

I have a similar issue as https://github.com/flowjs/ng-flow/issues/33
but the different is the parameter I pass was dynamic.
I have tried many options, but all failed, the parameter's value in the html dom are correct;
but submit the upload, it always post {{topic.id}} to web server.
option 1:
flow-init="{target: '/upload/',  query: { id: '{{topic.id}}' } }"
option 2:
flow-init="{target: '/upload/?id={{topic.id}}' }"

this issue is resolved. it is caused by the flow-init is invoked before topic.id value popup.
so I put topic to angular resolve to make it invoked firstly.


Fix error in on_member_unban and in on_ready

Fixes some errors that I found (probably due to typos)

Yep, they were typos.  Thanks 👍


Parser Radius Proxy

Hi,
I am having trouble getting the AP name when I use a Radius Proxy NPS in front of NPS with "analyze_influx.php", I changed the array from value 16 to 11 always returns me 0 when it enters case 2 (accept code 2). I have identified that it is a problem in the NPS log that does not register NAS Identifier: MAAP22-222 in field 11 when it is of type accept, have any solutions for this?

Sorry, never heard of that problem or a Radius Proxy. You can send me the logs and I can try to figure it out but if it's a config thing for the NPS or proxy I probably can't help you.
But you might be interested in another tool I'm developing: Electron Radius Parser. It will parse Radius files by dragging the log files onto the program, or it will look automatically if run from the NPS server


Separate decoding of complex values into specific method

Change Summary
Separates decoding of complex values into a specific method in settings sources to allow for easier customisation of complex environment variable parsing whilst retaining the ability to parse nested and non-complex fields.
Related issue number
Feature request #126

please review

Thanks @dbendall


Connector code should be deprecated

During the hackathon, the extraneous code in the foursquare connector made it confusing to developers where they should put new extensions to functionality.
Let's get rid of old connector code for connectors that are clearly synclet-based now.

This is on the board as "deal with dormant locker code"

Ahh, perfect.
On Thursday, December 1, 2011 at 9:19 PM, Matt Zimmerman wrote:

This is on the board as "deal with dormant locker code"

Reply to this email directly or view it on GitHub:
https://github.com/LockerProject/Locker/issues/479#issuecomment-2986467

I've been picking away at this in connector directories where there's mixed old and new code, but I'm not super comfortable yet removing all the older connectors entirely, just fyi, making progress!

all of the connectors that have synclets and package.json's are now cleansed of old unused code :)


misc style fix

putting table style back on the styleguide context, by wrapping side nav on the page
deleting margin on styleguide page

Merged in #141.


Report import error in evidently.report package in databricks notebook

/databricks/python/lib/python3.9/site-packages/sklearn/__check_build/../../scikit_learn.libs/libgomp-d22c30c5.so.1.0.0: cannot allocate memory in static TLS block
Error goes away on copying code to a new notebook and reappears after some time.

It is some weird error arising because import sequence. Seems like sklearn needs to be imported first. Closing issue


jstree.open_node() and jstree.select_node() after jstree.load_node(['a', 'b_childOf_a', 'c_childOf_b', 'd_childOf_c']) fails

When loading an hierarchy of nodes, in load_node() callback open_node throws an error.
jstree.load_node(['a', 'b_childOf_a', 'c_childOf_b', 'd_childOf_c'], function() {
    jstree.open_node('childOf_d'); // throws an error: "Cannot create property 'children' on boolean 'false'"
    jstree.select_node('childOf_d'); // doesn't select the node, but opens parent nodes

    setTimeout(function() {
        jstree.open_node('childOf_d'); // doesn't throw, but doesn't open the node either
    });
})

jstree.open_node('childOf_d') does nothing when called after all parent nodes have loaded, but are still closed. I would expect it to open all nodes up to 'childOf_d'
jstree.select_node('childOf_d') opens all parent nodes, but doesn't select the node in the above context.

Sorry, but can you provide a functional demo? If not - I will have a look when I have time to reproduce myself. I am only asking because there are many things that could have gone wrong - duplicate IDs, etc - I just need your data to make sure we are seeing the same issue.
Best regards,
Ivan

Throw this file in jstree/demo/basic/  or any other folder in jstree/demo/.
Note the async simulation of returning data! Without it the error is not throwsn, but the rest is valid.
<!DOCTYPE html>

	<meta charset="UTF-8">
	<title>jstree select_node and open_node fails after load_node - bugs</title>

	<link rel="stylesheet" href="./../../dist/themes/default/style.min.css" />

jstree.open_node() and jstree.select_node() after jstree.load_node(['a', 'b_childOf_a', 'c_childOf_b', 'd_childOf_c']) fails
    #1363

    <button id="select_t5" type="buttton">load_node & select_node(t5)</button>
    <button id="open_t5" type="buttton">load node & open_node(t5)</button>

I think this is an issue with massload, as if you remove massload plugin, everything starts to work properly.

Looks great, thanks! :-)

Sorry for taking so long to respond and thank you for the detailed demo - it helped a lot - thank you for taking the time to prepare it.

 Thanks again for a great library! :-)

I think this is an issue with massload, as if you remove massload plugin, everything starts to work properly.

Hi,
I think there is a similar problem with 'state' plugin. select_node is not working.
When I remove 'state' plugin it works.


Remove -e flag from docker login

Builds are failing because CI is not able to login to docker
because -e (email) flag is deprecated.

Signed-off-by: Akash Srivastava<EMAIL_ADDRESS>

Fixes #3707.


Set wrapperPlugins without writing code

The latest announcement advertises this driver as drop-in compatible. I understand that I have to add the jar to my project and change the protocol prefix to jdbc:aws-wrapper: in the JDBC connection URL. But how do I set wrapperPlugins without changing my code? The docs do not suggest any method for that. Can I add the connection plugin manager parameters as URL parameters to the JDBC connection URL?

Hello @visit1985
Thank you for reaching out! wrapperPlugins parameter could be specified by one of the following way.

You can change code of your application.

Properties properties = new Properties();
properties.setProperty("wrapperPlugins", "failover,efm");
Connection connection = DriverManager.getConnection("jdbc:aws-wrapper:postgresql://....", properties);

You can add wrapperPlugins parameter to connection string.

Connection connection = DriverManager.getConnection(
     "jdbc:aws-wrapper:postgresql://....?wrapperPlugins=failover,efm", "user", "password");

I hope that answers your question.

Maybe this could be written somewhere more obvious in the documentation on the plugins.


RichPayloadEventSourceEtwPayloadSerializationTest investigate failure

failed with OutOfMemoryException once in the past 30 days.
After this OOM, test run continued! and other tests passed.
logs_10559249.zip
So it's either this test that might lead to OOM or there is some infra problem. Needs further investigation
Test method Microsoft.ApplicationInsights.Extensibility.Implementation.RichPayloadEventSourceTest.RichPayloadEventSourceEtwPayloadSerializationTest threw exception:
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.

Stack trace
    at Microsoft.ApplicationInsights.Extensibility.Implementation.RichPayloadEventSourceTest.RichPayloadEventSourceEtwPayloadSerializationTest()

I'm skeptical that's the real bug.
I've seen a lot of OOM exceptions suddenly this month.


Build Failure: ServiceMesh_CILIUM_SERVICE_MESH not declared by package smp (typecheck)

Current Behavior
➜  meshery-cilium git:(master) make
golangci-lint run
WARN [runner] The linter 'golint' is deprecated (since v1.41.0) due to: The repository of the linter has been archived by the owner.  Replaced by revive.
internal/config/config.go:24:19: ServiceMesh_CILIUM_SERVICE_MESH not declared by package smp (typecheck)
		"name":     smp.ServiceMesh_CILIUM_SERVICE_MESH.Enum().String(),
		                ^
internal/config/config.go:31:18: ServiceMesh_CILIUM_SERVICE_MESH not declared by package smp (typecheck)
		"name":    smp.ServiceMesh_CILIUM_SERVICE_MESH.Enum().String(),
		               ^
internal/config/operations.go:10:40: ServiceMesh_CILIUM_SERVICE_MESH not declared by package smp (typecheck)
	CiliumOperation = strings.ToLower(smp.ServiceMesh_CILIUM_SERVICE_MESH.Enum().String())
	                                      ^
make: *** [check] Error 1

Expected Behavior
Adapter should build and run.

Contributor Guides and Resources

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation

Meshery documentation site and source

🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

@leecalcote  SMP needs a new release to reflect the latest changes. After that, we just have to update its package version in this repo.

@iamsdas, let's do it.
@gyohuangxin ready to make a Service Mesh Performance release?

@leecalcote Yes. But can you review this PR which was pending for a while. I think it will be useful if we implement it in the new release.

@gyohuangxin We can merge your PR and make a new release.

@navendu-pottekkat Thank you!

@iamsdas has the new SMP release been incorporated into this adapter?

Fixed


Custom app icons are missing

It would be nice to fall back to the custom app's built-in icon if there's not a custom Comfy one.

Will look into adding this

Resolved via fbbc5fb27fdf0a42bf09a1d7e7cec26fe752e26b


Improve documentation on configuration option eslint.validate

At the moment the docs regarding eslint.validate say:

This is an old legacy setting and should in normal cases not be necessary anymore. Defaults to ["javascript", "javascriptreact"].

In my case, typescript files are not linted in VSCode if I don't specify this explicitely in eslint.validate. I'm wondering if this is already a "non-normal case". Could this be specified in more detail in which cases validate is not needed ("normal cases") and when it is needed?

@some-user123 validation of TypeScript files should happen automatically if ESLint is configured correctly. Can you please provide me with a GitHub repository I can clone that demos what you are experiencing.

@some-user123 validation of TypeScript files should happen automatically if ESLint is configured correctly. Can you please provide me with a GitHub repository I can clone that demos what you are experiencing.

Sure, please find the repo here: https://github.com/some-user123/vscode-eslint-issue-1159
yarn lint will complain about test.ts. In VSCode I don't see any error, unless I add a .vscode/settings.json with
{
  "eslint.validate": ["typescript"]
}

Also noticeable: If I remove this settings.json linting in VSCode still works -- until the next restart.

Sure, please find the repo here: https://github.com/some-user123/vscode-eslint-issue-1159
yarn lint will complain about test.ts. In VSCode I don't see any error, unless I add a .vscode/settings.json with
{
  "eslint.validate": ["typescript"]
}

Also noticeable: If I remove this settings.json linting in VSCode still works -- until the next restart.

Is the provided information sufficient? Do you need anything else?

@some-user123 missed it. I will have a look.

I tried to use the repository but it doesn't work. The repository depends on many node modules that seem to be gloablly installed on your system (e.g. typescript, eslint-plugin-vue, @vue/typescript/recommended). Can you please provide me with a repository that is self contained otherwise it is very hard to tell why things aren't working (we might use different versions of the modules)

Thanks for looking into it.
I don't have globally installed modules except npm and yarn. Typescript is referenced in app1/package.json. I should have pointed out more clearly that the repo uses yarn workspaces.
Steps to reproduce:

git clone ...
yarn install --frozen-lockfile
yarn lint

$ yarn lint
yarn run v1.22.10
$ eslint "**/*.{ts,tsx,js,jsx,vue}"

...\vscode-eslint-issue-1159\app1\test.ts
  1:1   warning  Unexpected console statement                        no-console
  1:13  warning  Replace `"Am·I·linted?")⏎` with `'Am·I·linted?');`  prettier/prettier

✖ 2 problems (0 errors, 2 warnings)
  0 errors and 1 warning potentially fixable with the `--fix` option.

Done in 3.48s.

Open folder in VSCode, open app1/test.ts.

Hve you tried eslint.workingDirectories. In setups with multiple project folders ESLint needs to know the working directories. A good indication for the setting is also that validating in a terminal requires a cd to work.

The validate setting got un-deprecated a while back.


Fix miscellaneous bugs

@RedHatProductSecurity/corgi-devs Please review. The commit messages have more details, but these changes are needed to fix incorrect results in the API, errors in our monitoring email, and so on.

I would hold off on any changes for now - things are in a lot of motion ... should calm down soon.

I'm fine with the other changes in this PR, apart from the changes related to the root_component condition.


How can i get cordinates?

I split the 360-degree image into 18 conventional images.
I want to get coordinates of each image.
Is it possible?

You mean coordinate on equirectangular? https://github.com/fuenwang/Equirec2Perspec/blob/master/Equirec2Perspec.py#L71
The lon and lat is the coordinate.

I want to know corners' cordinates on equirectangular.
When i get the lon and lat lots of numbers appear.

The lon and lat is the coordinate of h x w x 3 which is consistent with  the perspective images. So you can just use lon[0, 0, :] and lat[0, 0, :] ...... to get the coordinate of corners.

Thanks! I solved it :)


Getting Error while running gradlew build

Getting below error while running gradlew build command as per  https://github.com/linkedin/datahub/tree/master/metadata-ingestion step#2
./gradlew :metadata-events:mxe-schemas:build

Looks like the build is happening on a windows machine.
I was able to replicate similar error on a windows machine.
@mars-lan is this the first use case of building on windows ??

Most likely https://github.com/linkedin/rest.li/issues/287

Unfortunately, it seems that rest.li team has little interest in supporting Windows (see https://github.com/linkedin/rest.li/issues/287). Will close this for now and encourage DataHub users to build on Mac & Linux instead.


update composer.json

use the laravel version 5.2

This is not necessary at the moment. I prefer to keep it compatible as long as possible.