Vue3

Does any tried that with VueJs3 ?
I am getting only : createElement is not a function when trying adding a styled component into the template.

will there be any work on this issue?

I think new api of vue 3 brings the h or createElement function outside the render scope:
https://v3.vuejs.org/guide/migration/functional-components.html#_3-x-syntax
It require maybe a version for vue 3 only.

https://github.com/UX-and-I/vue3-styled-components

Are there any plans to support vue3 in the official library?

You can use vue3-styled-components.

Yes I know, but since we are developing a big size enterprise project I would be happy to use the official library

Hi @Blackfaded ,
since vue3 made a lot of breaking changes it will be necessary to create a next version of this package.
At this moment I have no read completely and no real great experience with vue3 cause at work we still use te v2.
So maybe in the future, when my skills where ready to do that in the proper way, I'll try to update it.
Maybe I can give it a try in these days but for sure it will not production-ready solution.
Open source (as license say) has also no warranty on software and if there are some updates, features, improvements from the community I will happy to merge the work into the official one.
If you want to give a try, refer to https://github.com/UX-and-I/vue3-styled-components.
Is based on this package, but the vue component is written with vue3 API.
Thank you <3

Hi,
Would funding/sponsorship help styled-components get first class support for Vue 3?

Hi @Blackfaded ,
since vue3 made a lot of breaking changes it will be necessary to create a next version of this package. At this moment I have no real experience with vue3 cause at work we still use te v2.
So maybe in the future, when my skills where ready to do that in the proper way, I'll try to update it. Maybe I can give it a try in these days but for sure it will not production-ready solution.
Open source (as license say) has also no warranty on software and if there are some updates, features, improvements from the community I will happy to merge the work into the official one.
If you want to give a try, refer to https://github.com/UX-and-I/vue3-styled-components. Is based on this package, but the vue component is written with vue3 API.
Thank you <3

Hi there. I think it would be a huge boon to the Vue community to have a fully-featured CSS-in-JS library (specifically with the Styled Components API). Mind if I take a stab at this? I'd like to see if I can get us back to the full feature-set of this library with Vue 3 support.
Thanks.

@MatthewZito do you need any assistance? I’d like to help if I can

@MatthewZito do you need any assistance? I’d like to help if I can

Absolutely. I plan on doing the work in a new repository - at least until we hear from @liqueflies on whether they want to continue this project or if we should continue with a new one altogether. I'll have it stood up on my account in a few - feel free to start a discussion over there so we can coordinate.
Quick note - it looks like the aforementioned Vue 3 fork has been inactive for almost 1 year. They also note this in the README:
"This is a very quick, as-is-port of vue-styled-components, meaning it will only provide the functionality we need, until vue-styled-components hopefully has found its own path to Vuejs 3"
That is, I believe it's safe to say they don't intend on implementing the remainder of the existing Vue 2 Styled Components API.
@liqueflies I don't want to step on your hard work here; if you feel there's a better direction please let us know.

Thanks for being patient, everyone - I'm relocating across the country next week so life has been a bit all over the place.
@liqueflies I've opened a PR for Vue 3 support. Let me know if you'd prefer this be on a next branch. Thanks
#139

Hello @MatthewZito! Any update regarding the issue?

Hello @MatthewZito! Any update regarding the issue?

I recently published this on my NPM account, as it seems this project is not being actively maintained and we haven't heard from the original author in quite some time.
Feel free to try it out!
There's a couple of issues with the TypeScript types that I'll be fixing later today, but thus far everything seems to be in working order. I think I'll continue working on this project under the forked repo on my account.

bump, any update for the official package for support?

I don't think its happening. I've since migrated to React where tooling/libraries/etc aren't just broken for years.

A very painful direction indeed!

bump, any update for the official package for support?

Doubtful. I opened a PR to merge full Vue 3 support over a year ago and I never heard back from the maintainer. Even pinged him on LinkedIn. I've published the package on NPM but I'm also very busy and likely won't be working on it much beyond what I have right now (which is, at the least, full-parity support with the original package).

Hello people,
I was notified about this conversation and I need to clarify what I have already answered above time ago.
I started to port SC from vue in 2018 (5 years ago!), using the core (with core I mean the logic behind the style and class computation, not the framework) of react SC at that moment.
That was a sort of self-challenge for me, I published the package under my name and I wrote to the creators of SC if this was good for them. They invited me to move my repo under the "styled-components" organization to get more visibility and help from the community.
After that, I started for each change from the core to bridge to vue SC but it was so painful, so I tried to ask if was possible to move the "core" into a separate package (from the main repo) and just create the "vue" component that uses the core logic.
Read here if interested: https://github.com/styled-components/styled-components/issues/588#issuecomment-287300504
I lost my potential time doing this and the community started to make fixes and PRs about vue SC and when it was possible I managed and merged.
Now I have no knowledge of vue3 to make this "reviewer" work, cause I moved to react too.
I am sorry for the "no reply" but my last years were overwhelmed by my main work, and I want to start here to answer each one of you:
@lloydjatkinson No, I don't want to be founded.
This is not my job and I do open source for passion!
The "community" is not just people that "uses" software, but people collaborating and helping with that.
I think the best way is to search for people who are involved to be "maintainers" of the package and let them guide the lib.
@exbotanical I am very sorry If I didn't reach out.
I looked on Linkedin inbox but I didn't find you in my messages, what's your username/name there?
Congrats on your work, I really want to say that I could review and merge but for the same reasons I wrote above, I am not comfortable with vue3. Maybe you are interested in being a maintainer?
We can reach out to the org and ask them if this is ok?
In general: merging the PR from @exbotanical is the same as using its NPM package. Same code, same result.
So my suggestion for now it's to use that package!
I think vue-styled-components will grow only if more people (not only one) take their time to actively maintain the repo.
I am open to hearing something from you if interested, as I said for me the right way is to make a PR on the main repo only with the "vue" component into the monorepo.
This is my suggestion and what I was trying to achieve before vue3, but at that time was not possible.
I think maybe now the main repo should be pluggable, so maybe the work should be smaller than re-write everything.
And yes of course If I can help let's discuss and I will try to do my best with the time I have.
Thank you for reading and understanding.
Lorenzo

@exbotanical I am very sorry If I didn't reach out. I looked on Linkedin inbox but I didn't find you in my messages, what's your username/name there? Congrats on your work, I really want to say that I could review and merge but for the same reasons I wrote above, I am not comfortable with vue3. Maybe you are interested in being a maintainer? We can reach out to the org and ask them if this is ok?

Sorry! I must have been thinking of someone or something else because I double-checked my LinkedIn and didn't see any sent messages to you :laughing: My bad.
I'd be happy to co-maintain or guide a new maintainer if they'd like to use my fork. Let's see if anyone is interested and go from there. Great to hear from you, hope all is well.

@exbotanical I am very sorry If I didn't reach out. I looked on Linkedin inbox but I didn't find you in my messages, what's your username/name there? Congrats on your work, I really want to say that I could review and merge but for the same reasons I wrote above, I am not comfortable with vue3. Maybe you are interested in being a maintainer? We can reach out to the org and ask them if this is ok?

Sorry! I must have been thinking of someone or something else because I double-checked my LinkedIn and didn't see any sent messages to you 😆 My bad.
I'd be happy to co-maintain or guide a new maintainer if they'd like to use my fork. Let's see if anyone is interested and go from there. Great to hear from you, hope all is well.

To me the best way is to create a next branch and a next alpha version to test it out.
Then the right way is to work into the main styled-components repository in order to not get mad with vue integration.
I will be unreachable till next week, when back I can make a next branch and npm version

@exbotanical I am very sorry If I didn't reach out. I looked on Linkedin inbox but I didn't find you in my messages, what's your username/name there? Congrats on your work, I really want to say that I could review and merge but for the same reasons I wrote above, I am not comfortable with vue3. Maybe you are interested in being a maintainer? We can reach out to the org and ask them if this is ok?

Sorry! I must have been thinking of someone or something else because I double-checked my LinkedIn and didn't see any sent messages to you 😆 My bad.
I'd be happy to co-maintain or guide a new maintainer if they'd like to use my fork. Let's see if anyone is interested and go from there. Great to hear from you, hope all is well.

To me the best way is to create a next branch and a next alpha version to test it out. Then the right way is to work into the main styled-components repository in order to not get mad with vue integration.
I will be unreachable till next week, when back I can make a next branch and npm version

Sounds great! I'll take some time this week to go through my fork and double-check that I have everything ready for a next release. After some thought, I would be comfortable maintaining this if you're still interested in a hand-off. Let's sync up when you get back.

any updates here?

Hey there, wonderful people! I'm thrilled to share that I've revamped a version specifically tailored for Vue3. You can explore it right here: https://github.com/v-vibe/vue-styled-components. Plus, I've put together comprehensive documentation for your convenience: https://vue-styled-components.com/. Rest assured, I'm committed to nurturing and enhancing this repository for the long haul!


Updated the Bedrock rag template

Updates the bedrock rag template.

Removes pinecone and replaces with FAISS as the vector store
Fixes the environment variables, setting defaults
Adds a main.py test file quick sanity testing
Updates README.md with correct instructions

@rlancemartin
Let me know if there is any feedback.


Fix  tag's href to redirect to correct URL

Current Behavior:
After Smallify, on clicking the URL the link that opens is https://smallify.live/smallify.live/alias
Expected Behavior:
After Smallify, on clicking the URL the link that should open is https://smallify.live/alias

Pls assign this issue to me ,I can fix this!!

Pls assign this issue to me ,I can fix this!!

Thanks! Assigned the issue to you.

Can i work on this issue?

I can fix this. Please assign it to me

Fixed it already

Hi @anshrusia200, Thanks but the issue was already assigned to someone else. You can still try fixing other issues


Cast link with embeds

Checklist

[x] I've searched the project's issues.

❓ Question
I'm trying to cast links via farcaster-py with embeds. I guess it involves the 'embeds' List param of the post_cast method, but I can't get it working - can anyone help?
📎 Additional context
https://a16z.github.io/farcaster-py/reference/#farcaster.client.Warpcast.post_cast

Hmm, it seems to work now, maybe there was an issue with the link I was testing with before!


Thoughts on cookstyle

I'm curious what everyone's thoughts are on applying cookstyle to this cookbook to match other cookbooks in the Chef ecosystem. It's a pretty big change as things go from double to single quotes which also aligns with the default rubocop rules.

@tas50 certainly open to it but I would rather focus on things like having custom resources and other improvements but certainly support if you want do this sooner rather than later.


File operations do not defend against symlink traversal, permitting trivial escape from read-write mounts

(I have been asked to report this bug via the public issue tracker.)
wazero does not appear to defend against symlink traversal in its filesystem APIs.
Since the WASI filesystem API permits creating symlinks, this allows for trivial access to the full filesystem from any program with a read-write mount. For example:
package main

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

func main() {
	if err := os.Symlink("../../../../../../etc/passwd", "a"); err != nil {
		log.Fatal(err)
	}
	f, err := os.Open("a")
	if err != nil {
		log.Fatal(err)
	}
	b, _ := io.ReadAll(f)
	fmt.Println(string(b))
}

Run this program with read-write access to some directory:
wazero run -mount=restricted:/ main.wasm

It prints out the contents of /etc/passwd. /etc/passwd hasn't been exciting for a couple decades, admittedly, but this can be used to read or write any file anywhere on the filesystem that the account running wazero has access to.

We need to decide if the issue is traversing the root at all, or if the issue is creating new symlinks that do.
What does WASI specify? Does it even specify this at all?
W.r.t. security, I don't speak for the team, but I'd like to say that I consider (1) sandboxing WASI a much (much!) harder effort than (2) sandboxing Wasm. And I feel that the level of effort that was put into (1) is lower than (2), both within wazero development, but also in terms of WASI and Wasm design to begin with.
So if you really care about security, yeah, you maybe shouldn't be using WASI preview.

Note that simply preventing creating symlinks that traverse the root isn't going to suffice: An attacker can create a symlink that doesn't traverse the root (a/b/c/d/../../../etc/passwd), and then rename the containing directory (rename a/b/c/d => d).
Preventing creation of symlinks with any .. elements might suffice to prevent creating new escapes.

Just leaving the code pointer here:
https://github.com/tetratelabs/wazero/blob/dc058c074d0bcce9b0e2da2619669d4ab443fb54/internal/sysfs/dirfs_supported.go#L36-L42
We can probably enforce some minimal rules here, like that running path.Clean(link) doesn't change link, and that link doesn't start with ../.
It's likely that these checks should be inside join. I find the rational that ../ should for path be supported rather jarring:
https://github.com/tetratelabs/wazero/blob/dc058c074d0bcce9b0e2da2619669d4ab443fb54/internal/sysfs/dirfs.go#L87-L99
I mean: do we even need symlinks to evade the "root" at this point?

if we do I think we might have to skip some wasi tests (but that might be ok)

Would you mind testing b36a8c8952a230afaab2067672a1818f23c347e1, @neild, @evacchi?
I think all our current tests pass. This only allows creating symlinks that go down, not up (returns EFAULT otherwise, which seems appropriate).

Having slept through this (not much admittedly), b36a8c8 has two issues with it.
Symlink must check that the cleaned path doesn't start with / either; also, it doesn't need to modify the path, I think. Leaving the path as is is fine, as long as the symlink always points down.
For join, we need to make a judgement call.
Lexically cleaning the path with path.Clean violates semantics: /a/../b is only the same as /b if /a exists and is a directory or a symlink to a directory.
Not lexically cleaning the path, however, is an issue if (e.g.) /a is a symlink to our root, because then ../b evades the root.
BTW, unless I'm missing something, I don't think the openat family of calls protects against any of these issues. The only complete solution would be for our file system to implement path resolution all by itself.

So, our options seem to be:

semantically wrong path resolution (path.Clean, b36a8c8952a230afaab2067672a1818f23c347e1 is a start)
root escapes in the presence of symlinks (even if we don't allow creating symlinks at all)
a bunch of syscalls on every file system access to do path resolution ourselves (openat family of syscalls may help here)

In general the doc we should be reading about path resolution semantics we should be reading is:
https://github.com/WebAssembly/wasi-filesystem/blob/main/path-resolution.md#host-implementation
I hate it that I didn't find it sooner, but I hadn't worked on WASI filesystem directly myself before.

Bit tangential perhaps but if you know ahead of time what your filenames will be, and what permissions you want to give your wasm application on them, you can implement quite a strict filesystem like this:
https://github.com/superseriousbusiness/gotosocial/blob/53ee6aef0885b4055ef95bf4f20ee78fd381e333/internal/media/util.go#L34-L77
And then give a config like this:
https://github.com/superseriousbusiness/gotosocial/blob/53ee6aef0885b4055ef95bf4f20ee78fd381e333/internal/media/ffmpeg.go#L242-L256
Or like this:
https://github.com/superseriousbusiness/gotosocial/blob/53ee6aef0885b4055ef95bf4f20ee78fd381e333/internal/media/ffmpeg.go#L158-L192
That's how we locked this down as much as possible in GtS anyway, though it may not apply for your use-case.

Yep. I have this extreme example I used for a tool that reads from a single file (because it wants to seek, so doesn't like stdin, but is willing to output to stdout):
https://github.com/ncruces/RethinkRAW/blob/master/pkg/dcraw/fs.go

As discussed above, this is working as specified in the documentation.
I opened #2323 to track implementing path resolution, which would fix this.


ALTREP

Limitation at the current prototyping phase: #[savvy_init] simply exposes and executes the function as it is. It's user's responsibility to make sure the function is callable from C. No error can be emitted. Probably, #[savvy_init] should generate the same wrapper as #[savvy], or, rather, #[savvy] should automatically detect the initialization function by checking if DllInfo is used.

Example implementation: https://github.com/yutannihilation/savvy-altrep-test


how can I rebuild the 201702: initial release?

Hello, in my project I need to download the release version 201702: initial of the xtensa-config. However, I can't download from the server. Could you tell me how can I rebuild it?
Thanks!

I'm not sure what exactly you want to rebuild. There's only one source file in this repository: make-overlay.sh, you can't rebuild it. The 201702 release has an archive attached to it: sample_controller_linux.tgz, it's built by the Xtensa Processor Generator (XPG), you need to have XPG access to rebuild it (but if you have XPG access you can just download it from the XPG, it's a standard configuration).


Disable bitcode for Mac target for Xcode 7.1 compatibility

If bitcode is enabled for Mac target, the build would fail. Additionaly ENABLE_BITCODE set to YES only for iOS target, the setting would not be appeared in Xcode 7.1 for watchOS and tvOS target anymore (since they must be bitcode-enabled?).

:+1:

Thanks very much for the PR, @ikesyo!


sonic-pi crashes

Crashes at startup, [GUI] - Critical error! Could not boot Sonic Pi Server.
Report
Sonic Pi Boot Error Report
System Information

Sonic Pi version: 3.1.0
OS: NixOS 20.03 (Markhor)

GUI Log
/home/andrey/.sonic-pi/log/gui.log
[GUI] - Detecting port numbers...
[GUI] - GUI OSC listen port 4558
[GUI] -    port: 4558 [OK]
[GUI] - Server OSC listen port 4557
[GUI] -    port: 4557 [OK]
[GUI] - Server incoming OSC cues port 4559
[GUI] -    port: 4559 [OK]
[GUI] - Scsynth port 4556
[GUI] -    port: 4556 [OK]
[GUI] - Server OSC out port 4558
[GUI] - GUI OSC out port 4557
[GUI] - Scsynth send port 4556
[GUI] - Erlang router port 4560
[GUI] -    port: 4560 [OK]
[GUI] - OSC MIDI out port 4561
[GUI] -    port: 4561 [OK]
[GUI] - OSC MIDI in port 4562
[GUI] -    port: 4562 [OK]
[GUI] - Init script completed
[GUI] - using default editor colours
[GUI] - launching Sonic Pi Server:
[GUI] - starting UDP OSC Server on port 4558...
[GUI] - UDP OSC Server ready and listening
[GUI] - Ruby server pid registered: 8405
[GUI] - waiting for Sonic Pi Server to boot...
............................................................
[GUI] - Critical error! Could not boot Sonic Pi Server.
[GUI] - stopping UDP OSC Server...
[GUI] - UDP OSC Server no longer listening

Do you have a working Jack setup? That is required for SonicPi to start. See: https://github.com/NixOS/nixpkgs/pull/82043#issuecomment-636470268
I start sonic-pi like this: #!/usr/bin/env bash jackd -d alsa -d hw:1 & pid=$! sleep 1 sonic-pi pkill jackd wait $pid
The -d hw:1 is the audio card used and depends on your hardware setup.


[web]: Printing does not work

Describe your issue and include the command you're running, flutter_web version, browser version.
Printing from a printer does not work. The print preview on 'Slide puzzle' is completely blank, and there is only 1 out of 1 pages to print.
This applies to almost every example at https://flutter.github.io/samples/ .
Given that flutter can make use of the browser in a standards compliant way, I suspect this can be addressed eventually. I now see that https://github.com/flutter/flutter/issues/32249 also deals with this.

Also looking for a solution to this problem

@goodmansasha I will close the issue to avoid duplication, as #32249 contains the details, please continue to follow it there.

The print function is not working on web flutter.
Future createWidget() async{
final jsonResponse = json.decode(_element);
debugPrint(jsonResponse.topWidget);
for(var i in jsonResponse.topWidget){
debugPrint(i);
}
}

print works one time and doesnt work another time its the same exact code nothing changed except time 😕
:D frankly last night I have discovered that the current version of master channel for web has isssues with dart
for loops, list operations assignments and await doesnt work as excpected all the time


Error when running online demo main.py

I'm getting this error when I try to execute python3 main.py within ~/temporal-shift-module/online_demo folder..
Open camera...
<VideoCapture 0x7f2f0b2370>
Build transformer...
/usr/local/lib/python3.6/dist-packages/torchvision-0.5.0a0+85b8fbf-py3.6-linux-aarch64.egg/torchvision/transforms/transforms.py:220: UserWarning: The use of the transforms.Scale transform is deprecated, please use transforms.Resize instead.
  "please use transforms.Resize instead.")
Build Executor...
/home/bm/temporal-shift-module/online_demo/mobilenet_v2_tsm.py:95: TracerWarning: Converting a tensor to a Python index might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  x1, x2 = x[:, : c // 8], x[:, c // 8:]
Traceback (most recent call last):

  File "main.py", line 386, in <module>
    main()

  File "main.py", line 282, in main
    executor, ctx = get_executor()

  File "main.py", line 96, in get_executor
    return torch2executor(torch_module, torch_inputs, target)

  File "main.py", line 52, in torch2executor
    graph, tvm_module, params = torch2tvm_module(torch_module, torch_inputs, target)

  File "main.py", line 31, in torch2tvm_module
    torch.onnx.export(torch_module, torch_inputs, buffer, input_names=input_names, output_names=["o" + str(i) for i in range(len(torch_inputs))])

  File "/home/bm/.local/lib/python3.6/site-packages/torch/onnx/__init__.py", line 148, in export
    strip_doc_string, dynamic_axes, keep_initializers_as_inputs)

  File "/home/bm/.local/lib/python3.6/site-packages/torch/onnx/utils.py", line 66, in export
    dynamic_axes=dynamic_axes, keep_initializers_as_inputs=keep_initializers_as_inputs)

  File "/home/bm/.local/lib/python3.6/site-packages/torch/onnx/utils.py", line 416, in _export
    fixed_batch_size=fixed_batch_size)

  File "/home/bm/.local/lib/python3.6/site-packages/torch/onnx/utils.py", line 296, in _model_to_graph
    fixed_batch_size=fixed_batch_size, params_dict=params_dict)

  File "/home/bm/.local/lib/python3.6/site-packages/torch/onnx/utils.py", line 135, in _optimize_graph
    graph = torch._C._jit_pass_onnx(graph, operator_export_type)

  File "/home/bm/.local/lib/python3.6/site-packages/torch/onnx/__init__.py", line 179, in _run_symbolic_function
    return utils._run_symbolic_function(*args, **kwargs)

  File "/home/bm/.local/lib/python3.6/site-packages/torch/onnx/utils.py", line 657, in _run_symbolic_function
    return op_fn(g, *inputs, **attrs)

  File "/home/bm/.local/lib/python3.6/site-packages/torch/onnx/symbolic_helper.py", line 129, in wrapper
    return fn(g, *args)

  File "/home/bm/.local/lib/python3.6/site-packages/torch/onnx/symbolic_opset9.py", line 1311, in slice
    raise RuntimeError('Unsupported: ONNX export of Slice with dynamic inputs. DynamicSlice '

RuntimeError: Unsupported: ONNX export of Slice with dynamic inputs. DynamicSlice is a deprecated experimental op. Please use statically allocated variables or export to a higher opset version.

I get the same issue too when running the online demo on the Jetson TX2.

Hi @WSPluta, Have you get the solution of this problem?

Have same issue. Rolling back torch==1.2.0 and torchvision==0.4.0 works for me.

Don't know if this helps, but the onnx exporter takes an opset argument. Perhaps try:
 torch.onnx.export(torch_module, torch_inputs, buffer, input_names=input_names, output_names=["o" + str(i) for i in range(len(torch_inputs))], opset_version=11)

@WSPluta, @Ragavendrams @dionsaputra
hi, have you get solution of this problem? I got the same issue.

I run online demo without using onnx

@dionsaputra Thanks for your reply. Could you tell me how you make it  or could you kindly give me any instruction or tips on running without onnx?  Should I delete code related to onnx in main.py ? I am not familiar with onnx.

@poincarelee Yes, you can remove anything related with onnx and load the model using normal pytorch library

Thanks a lot. Your advice is a great idea, I will have a try on it.

I  have solved this problem. The solution is to export torch model with opset 10 instead of default opset 9, TVM does not really support some operators in opset 9. Additionally,  using a tool "onnx-simplifier" would be great help.

@poincarelee Could you tell me how you use "onnx-simplifier"?

you can search for it in github and then refer to the last part of  readme such as "pip install onnx-simplifier" and thus import it in your script, it's simple to use this tool.

thank you!
I try to use onnx-simplifier like below
from onnxsim import simplify

In torch2tvm_module, I add onnx-simplifier after the onnx.load_model
onnx_model = onnx.load_model(buffer)
onnx_model, _ = simplify(onnx_model)

However, in simplify function, I have met new error.
onnx.onnx_cpp2py_export.checker.ValidationError: Graph must be in single static assignment (SSA) form, however ‘698’ has been used as output names multiple times.

Did you have seen this error?

I havn't met with this error. Maybe you need to check that the torch model be exported to opeset 10?
Add "opset 10" to the onnx export function and try again.

I already try "opset 10".
I think that the version of packages may arise this error.
My environment as follows:
pytorch: 1.5.0
torchvision: 1.7.0
onnx: 1.7.0
tvm: 0.6.0
CUDA: 10.2
cuDNN: 8.0.0
OpenCV: 4.1.1
Are these quite different from yours?

My environment:
Pytorch=1.4.0
Torchvision=0.5.0
Onnx=1.7.0
Onnx-simplifier=0.2.9
Opencv=<IP_ADDRESS>
Incubator-tvm=0.6
cuda=10.1
cudnn=7.6
the version of pytorch, torchvision,onnx, tvm may matters.

Thanks a lot.
I change my Pytorch to 1.4.0, but still have a problem.
Open camera...
[ WARN:0] global /home/nvidia/host/build_opencv/nv_opencv/modules/videoio/src/cap_gstreamer.cpp (933) open OpenCV | GStreamer warning: Cannot query video position: status=0, value=-1, duration=-1
<VideoCapture 0x7f456ba3b0>
Build transformer...
/usr/local/lib/python3.6/dist-packages/torchvision-0.6.0a0+b68adcf-py3.6-linux-aarch64.egg/torchvision/transforms/transforms.py:211: UserWarning: The use of the transforms.Scale transform is deprecated, please use transforms.Resize instead.
  "please use transforms.Resize instead.")
Build Executor...
/home/nvidia/temporal-shift-module/online_demo/mobilenet_v2_tsm.py:95: TracerWarning: Converting a tensor to a Python index might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  x1, x2 = x[:, : c // 8], x[:, c // 8:]
WARNING:root:Attribute momentum is ignored in relay.sym.batch_norm
WARNING:root:Attribute momentum is ignored in relay.sym.batch_norm
WARNING:root:Attribute momentum is ignored in relay.sym.batch_norm
WARNING:root:Attribute momentum is ignored in relay.sym.batch_norm
WARNING:root:Attribute momentum is ignored in relay.sym.batch_norm
WARNING:root:Attribute momentum is ignored in relay.sym.batch_norm
Traceback (most recent call last):

  File "main.py", line 393, in <module>
    main()

  File "main.py", line 289, in main
    executor, ctx = get_executor()

  File "main.py", line 103, in get_executor
    return torch2executor(torch_module, torch_inputs, target)

  File "main.py", line 59, in torch2executor
    graph, tvm_module, params = torch2tvm_module(torch_module, torch_inputs, target)

  File "main.py", line 40, in torch2tvm_module
    relay_module, params = tvm.relay.frontend.from_onnx(onnx_model, shape=input_shapes)

  File "/usr/local/lib/python3.6/dist-packages/tvm-0.6.0-py3.6-linux-aarch64.egg/tvm/relay/frontend/onnx.py", line 1497, in from_onnx
    mod, params = g.from_onnx(graph, opset)

  File "/usr/local/lib/python3.6/dist-packages/tvm-0.6.0-py3.6-linux-aarch64.egg/tvm/relay/frontend/onnx.py", line 1325, in from_onnx
    op = self._convert_operator(op_name, inputs, attr, opset)

  File "/usr/local/lib/python3.6/dist-packages/tvm-0.6.0-py3.6-linux-aarch64.egg/tvm/relay/frontend/onnx.py", line 1425, in _convert_operator
    sym = convert_map[op_name](inputs, attrs, self._params)

  File "/usr/local/lib/python3.6/dist-packages/tvm-0.6.0-py3.6-linux-aarch64.egg/tvm/relay/frontend/onnx.py", line 793, in _impl_v10
    ends = params[get_name(inputs[2])].asnumpy()

KeyError: ''

emm, put ''import onnx" before "import torch" and try again, if not work, reinstall tvm  using "git clone -b 0.6 " command in the readme. You'd better post the code how you use onnx-simplifier, seems still op problems.

Thank you for your help! You are my hero!
When I import onnx before import torch, online demo is working.
here is my code
import numpy as np
import os
from typing import Tuple
import io
import tvm
import tvm.relay
import time
import cv2
import onnx
import torch
import torchvision
import torch.onnx
from PIL import Image, ImageOps
import tvm.contrib.graph_runtime as graph_runtime
from mobilenet_v2_tsm import MobileNetV2
from onnxsim import simplify

SOFTMAX_THRES = 0
HISTORY_LOGIT = True
REFINE_OUTPUT = True

def torch2tvm_module(torch_module: torch.nn.Module, torch_inputs: Tuple[torch.Tensor, ...], target):
    torch_module.eval()
    input_names = []
    input_shapes = {}
    with torch.no_grad():
        for index, torch_input in enumerate(torch_inputs):
            name = "i" + str(index)
            input_names.append(name)
            input_shapes[name] = torch_input.shape
        buffer = io.BytesIO()
        torch.onnx.export(torch_module, torch_inputs, buffer, input_names=input_names, output_names=["o" + str(i) for i in range(len(torch_inputs))], opset_version=10)
        outs = torch_module(*torch_inputs)
        buffer.seek(0, 0)
        onnx_model = onnx.load_model(buffer)
        onnx_model, _ = simplify(onnx_model)
        relay_module, params = tvm.relay.frontend.from_onnx(onnx_model, shape=input_shapes)
    with tvm.relay.build_config(opt_level=3):
        graph, tvm_module, params = tvm.relay.build(relay_module, target, params=params)
    return graph, tvm_module, params

Hi guys, sorry for the painful experience when working on the online demo. I believe the version mismatch could be the problem here.
Is there anyone interested in sending a pull request to help the others set up the environment later, according to the solution above? Thanks!

@tonylins Hi, I have written a file in my repository forked from yours, but I don't know how to pull request.

https://github.com/poincarelee/temporal-shift-module/tree/poincarelee-running-online-demo

hello!
can i run this demo on my personal-pc? without jetson nano ?
if yes then how ?
I  am facing he following error... i have done the above solutions..

people who are trying to run it on personal PC's(on cpu) can email at<EMAIL_ADDRESS>I will soon make a file and share here the complete process.
The above comments helped me a lot in resolving issues.
Regards.

Hi @poincarelee, how did you install onnx-simplify? I get an error with the onnxruntime dependency:
pip3 install 'onnx-simplifier==0.2.9'

Collecting onnx-simplifier==0.2.9
  Using cached https://files.pythonhosted.org/packages/19/f1/4b188f4dacc45b69e48605f5232a9f22616656fd189dcc04369b516d818b/onnx-simplifier-0.2.9.tar.gz
Collecting onnx (from onnx-simplifier==0.2.9)
Collecting onnxruntime>=1.2.0 (from onnx-simplifier==0.2.9)
  Could not find a version that satisfies the requirement onnxruntime>=1.2.0 (from onnx-simplifier==0.2.9) (from versions: )
No matching distribution found for onnxruntime>=1.2.0 (from onnx-simplifier==0.2.9)

did you compile onnxruntime from source?

Hi, I have updated the repo to use onnx-simplifier and some other minor changes. It should now eliminate the error. Feel free to reopen if the error persists. Thanks!

Hi, when I am install onnxsimplifier, I remove requirement 'onnxruntime >= 1.2.0' in setup.py as the readme shown.
But I fail to run the demo and it shows the error like it:

people who are trying to run it on personal PC's(on cpu) can email at<EMAIL_ADDRESS>I will soon make a file and share here the complete process.
The above comments helped me a lot in resolving issues.
Regards.

hi, @Nauman007, can you share the file with me? i was trying to run it on pc(on cpu)

people who are trying to run it on personal PC's(on cpu) can email at<EMAIL_ADDRESS>I will soon make a file and share here the complete process.
The above comments helped me a lot in resolving issues.
Regards.

hi, @Nauman007, can you share the file with me? i was trying to run it on pc(on cpu)

@tonylins I am using Jetson tx2 Hi, when I am install onnxsimplifier, I remove requirement 'onnxruntime >= 1.2.0' in setup.py as the readme shown. But I fail to run the demo and it shows the error like it:
Open camera...
<VideoCapture 0x7f05923cf0>
Build transformer...
/usr/local/lib/python3.6/dist-packages/torchvision-0.3.0-py3.6-linux-aarch64.egg/torchvision/transforms/transforms.py:209: UserWarning: The use of the transforms.Scale transform is deprecated, please use transforms.Resize instead.
Build Executor...
/home/nvidia/Downloads/temporal-shift-module-master/online_demo/mobilenet_v2_tsm.py:95: TracerWarning: Converting a tensor to a Python index might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  x1, x2 = x[:, : c // 8], x[:, c // 8:]
Traceback (most recent call last):

  File "main.py", line 389, in <module>
    main()

  File "main.py", line 285, in main
    executor, ctx = get_executor()

  File "main.py", line 99, in get_executor
    return torch2executor(torch_module, torch_inputs, target)

  File "main.py", line 55, in torch2executor
    graph, tvm_module, params = torch2tvm_module(torch_module, torch_inputs, target)

  File "main.py", line 35, in torch2tvm_module
    from onnxsim import simplify

  File "/home/nvidia/.local/lib/python3.6/site-packages/onnxsim/__init__.py", line 1, in <module>
    from onnxsim.onnx_simplifier import simplify

  File "/home/nvidia/.local/lib/python3.6/site-packages/onnxsim/onnx_simplifier.py", line 11, in <module>
    import onnxruntime as rt  # type: ignore

ModuleNotFoundError: No module named 'onnxruntime'

Did you find a solution?
Thanks

@tonylins I am using Jetson tx2 Hi, when I am install onnxsimplifier, I remove requirement 'onnxruntime >= 1.2.0' in setup.py as the readme shown. But I fail to run the demo and it shows the error like it:
Open camera...
<VideoCapture 0x7f05923cf0>
Build transformer...
/usr/local/lib/python3.6/dist-packages/torchvision-0.3.0-py3.6-linux-aarch64.egg/torchvision/transforms/transforms.py:209: UserWarning: The use of the transforms.Scale transform is deprecated, please use transforms.Resize instead.
Build Executor...
/home/nvidia/Downloads/temporal-shift-module-master/online_demo/mobilenet_v2_tsm.py:95: TracerWarning: Converting a tensor to a Python index might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  x1, x2 = x[:, : c // 8], x[:, c // 8:]
Traceback (most recent call last):

  File "main.py", line 389, in <module>
    main()

  File "main.py", line 285, in main
    executor, ctx = get_executor()

  File "main.py", line 99, in get_executor
    return torch2executor(torch_module, torch_inputs, target)

  File "main.py", line 55, in torch2executor
    graph, tvm_module, params = torch2tvm_module(torch_module, torch_inputs, target)

  File "main.py", line 35, in torch2tvm_module
    from onnxsim import simplify

  File "/home/nvidia/.local/lib/python3.6/site-packages/onnxsim/__init__.py", line 1, in <module>
    from onnxsim.onnx_simplifier import simplify

  File "/home/nvidia/.local/lib/python3.6/site-packages/onnxsim/onnx_simplifier.py", line 11, in <module>
    import onnxruntime as rt  # type: ignore

ModuleNotFoundError: No module named 'onnxruntime'

Did you find a solution?
Thanks


Implement folder feature to organize bills

Please do work for this task in a branch named issue-23


Request for option to wrap area in a tag other than

<Dropzone> always wraps your stuff in a <div>. It would be nice if it were configurable in case you want to use another tag (think <tbody>).

Mind creating a PR for that?


Need for package requirements & version.

torch==1.10.0
torch-geometric==2.2.0
torch-scatter==2.1.0
torch-sparse==0.6.16

Thanks for your kindly remind. Our environment (conda) config file has been uploaded to the main branch (see the file named "environment_config.yml"). You may create the same experimental environment on your own server.


How to Call function entity By passing entity Object Custom

i need to create request like
POST https://ebiztest.aoa.org/PersonifyDataServices/PersonifyDataAoaCustom.svc/AddCustomerCreditCard HTTP/1.1
Content-Type: application/xml;charset=utf-8
ActivityId: WPF7WML
Authorization: Basic YW9hX3NzbzpTdDM0bTNkSDRtJA==
Host: ebiztest.aoa.org
Content-Length: 716
Expect: 100-continue

<?xml version="1.0" encoding="utf-16"?>
<CustomerCreditCardInput xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <InternalKey />
  <NavigationKey />
  <MasterCustomerId>00101247</MasterCustomerId>
  <SubCustomerId>0</SubCustomerId>
  <ReceiptType>Visa</ReceiptType>
  <CreditCardNumber>4111111111111111</CreditCardNumber>
  <ExpirationMonth>11</ExpirationMonth>
  <ExpirationYear>2020</ExpirationYear>
  <Cvv2>123</Cvv2>
  <NameOnCard>raja</NameOnCard>
  <BillingAddressStreet />
  <BillingAddressCity />
  <BillingAddressState />
  <BillingAddressPostalCode />
  <BillingAddressCountryCode />
  <AddedOrModifiedBy />
</CustomerCreditCardInput>

ENTITY
<FunctionImport Name="AddCustomerCreditCard" ReturnType="Edm.String" m:HttpMethod="POST">
<Parameter Name="CustomerCreditCardInput" Type="Edm.String" Mode="In"/>
</FunctionImport>

For functions and actions please have a look at examples here:
https://github.com/object/Simple.OData.Client/blob/master/Simple.OData.Client.IntegrationTests/TripPinTests.cs
(search for "Function" or "Action" in the code).
Here are some examples for OData V3:
https://github.com/object/Simple.OData.Client/blob/master/Simple.OData.Client.Tests.Net40/FunctionTests.cs

Hi Vagif Abilov
i have One function(

AddCustomerCreditCard

) which accept `

CustomerCreditCardInput

`Entity and which return

CustomerCreditCardOutput

Here is odata service url : https://ebiztest.aoa.org/PersonifyDataServices/PersonifyDataAoaCustom.svc
user = "aoa_sso";
password = "St34m3dH4m$";
Function name : AddCustomerCreditCard
Input Entity : CustomerCreditCardInput
OutPut Entity : CustomerCreditCardOutput
Please suggest how to execute  those entities

I will check this out and come back to you later.

Thank you

i am waiting for your replay

Sorry this is not my main job project, I'll come back to you as soon as I can.

Hi, I tried this now but am getting an exception when executing the HTTP request. Will look into it tonight.

Ok thanks
can you give that code i'll also try

Here's the example:
class CustomerCreditCardInput
{
public string MasterCustomerId { get; set; }
public int SubCustomerId { get; set; }
public string ReceiptType { get; set; }
public string CreditCardNumber { get; set; }
public short ExpirationMonth { get; set; }
public short ExpirationYear { get; set; }
public string Cvv2 { get; set; }
public string NameOnCard { get; set; }
}
[Fact]
public async Task IssueFunction()
{
var client = new ODataClient(new ODataClientSettings()
{
UrlBase = "https://ebiztest.aoa.org/PersonifyDataServices/PersonifyDataAoaCustom.svc",
Credentials = new NetworkCredential(..removed_credentials...),
});
var result = await client
    .Unbound()
    .Action("AddCustomerCreditCard")
    .Set(
        new CustomerCreditCardInput()
        {
            MasterCustomerId = "00101247",
            SubCustomerId = 0,
            ReceiptType = "VISA",
            CreditCardNumber = "4111111111111111",
            ExpirationMonth = 11,
            ExpirationYear = 2020,
            Cvv2 = "123",
            NameOnCard = "raja"
        })
    .ExecuteAsScalarAsync<string>();

}

Hi again,
I can confirm that this is a bug in a current version (failure to serialize action parameters for OData V3). I will let you know when it's fixed.

Hi
I have another doubt on set attribute
how to send dynamic  string or Object

Let us come back to it when I fix the bug. I have identified the problem and should be able to have a fix within a few days.

The fix will be released as a part of 4.24.

Should work in 4.24.


Write prunning configs if --full is present.

Closes #7923

Save prune config to reth.toml.
warn if prune config present but run with --full.

Changed code structure from previous commit.

added method to save config for reth_config::Config.
moved concerned logic to a new static method in LaunchContext.
added tests.


General cross-platform code to create a Numpy dtype for a given Cython struct?

Say I have the following C struct (in dlist.h):
typedef struct {
  double dx, dy, dz;  // relative vector coordinates.
  long i, j;          // involved atoms. vector points from i to j.
  double gx, gy, gz;  // derivative of energy towards relative vector coordinates.
} dlist_row_type;

My corresponding Cython struct is:
cdef extern from "dlist.h":
    ctypedef struct dlist_row_type:
        double dx, dy, dz
        long i, j
        double gx, gy, gz

I'm currently creating a compatible Numpy dtype as follows:
cdef dlist.dlist_row_type _dlist_row_tmp
delta_dtype = np.asarray(<dlist.dlist_row_type[:1]>(&_dlist_row_tmp)).dtype

This is a reasonable cross-platform solution but it involves a temporary variable. Is there a way to get thisdtype without a temporary variable? Thanks!

I wouldn't know any, but this is clearly a question rather than a ticket. You should rather ask it on the cython-users or numpy mailing lists.


Close button X Off-Centered

The "X" in the close button is off-centered

appears to be an issue with specificity: the button styles are lower in the dom than the closebutton

I attempted to fix it by removing the spread operator on props in CloseButton, {...others} to be specific.
reloaded the page and the issue was gone. class names were still in the Button then CloseButton order (class="Button-0-2-82 CloseButton-0-2-137").  not entirely sure if that addressed the issue

I can't repro that solution, it's still broken for me.


Passing a URL with brackets to curl

your CURL example isn't working, reference: https://stackoverflow.com/questions/8333920/passing-a-url-with-brackets-to-curl
😄

Fixed, see:
https://gastronomycon.matchyourtie.com/
https://github.com/ugobriasco/gastronomycon-server/wiki/Gastronomycon-API-v1.0-reference


Modify the JSON output of kpod ps

Changed the JSON output to hold the actual type of the data.
For example the creation time of a container will be of form time.Time.
The human readable output modifies all the fields to type string, which
is not helpful when the JSON output wants to be used for further processing.
Signed-off-by: umohnani8<EMAIL_ADDRESS>

@rhatdan @baude @mrunalp PTAL. If this gets accepted, I will make the same changes to kpod history and images.

LGTM here, though @baude should take a look before we think about merging this

Travis is unhappy otherwise code changes LGTM, but echo @mheon, I'd like a 👍 from @baude before submit.

Travis is finally happy!

LGTM! Good work

[retest]

[retest]

Looks like tests are failing, because RHEL7.3 system is attempting to use overlay2.  Usually this happens because crio.conf is hard coded to ovleray2, rather then "".

@rhatdan I didn't touch crio.conf and when I checked, the storage driver is set to "" ¯_(ツ)_/¯

It seems to be happening on all PRs - did something that landed earlier break something? Or are the builders themselves just broken?

Rebasing to latest master should fix the jenkins tests.

LGTM. Tests are passing so I will merge.


TEST CASES #TEAM 4

Description
TASK : Test cases for Order system(#3).
FEATURE : Order System(#4)
Implementing the test cases which will cover all the components that are there under order system from displaying an order to the all the way to closing the ticket . It will eliminate errors in the code and will assure the proper functioning of the code towards the team’s feature.
Example (optional)
Test case on displaying ticket : It will test  the data is displayed and also make sure that the ticket is closed after the timer.
Test case for status :It will make sure that the status is displayed and can be changed.
DEPENDENCIES
List any tasks on which this ticket relies. If there is already an existing ticket, reference it using #xx. If a task needs to be implemented, and the issue does not already exist, make a new ticket and leave it unassigned for someone else to take on. Ensure other team members are aware of the issue.

[x] Dependency 1 : The quality of code written .
[x] Dependency 2 : Does the code fulfil the purpose for the task it is written .

Milestones
List of steps that need to be completed for this task.

[x] Test on Docket Display (Aug. 25)
[ ] Test the Order Display button (Aug. 26)
[ ] Test Order ticket Display(Aug. 27)
[ ] Test order actions (Aug. 28)

Completion Deadline: Aug. 29
MEMBER

Lakshay(LAKSHAYATREJA) (Lakshay)

Download
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
In the installer menu, select "gcc."

completed initial test on docket Game Unit Tests #265: Commit 554412f pushed by LAKSHAYATREJA


Support LINE Profile+

Motivation
Profile API endpoint (https://api.line.me/v2/profile) doesn't support LINE Profile+. If we want to retrieve LINE Profile+, we should use ID token verification https://api.line.me/oauth2/v2.1/verify.
Changes
All of following include breaking changes.

Modify UserInformationEndpoint

https://api.line.me/v2/profile -> https://api.line.me/oauth2/v2.1/verify

Remove AppId / AppSecret properties, because these are alias properties
Modify class prefix

LineXxx -> LineOAuthXxx

Set only openid as the initial value of the Scope property


Add click

Pull Request
Description
Add click arguments
How Has This Been Tested?
added a unittest test

[ ] Yes

Checklist:

[ ] My code follows OCF's coding style guidelines
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked my code and corrected any misspellings

Codecov Report

Merging #1 (6383875) into main (8aec8c4) will increase coverage by 10.25%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##             main       #1       +/-   ##
===========================================
+ Coverage   85.27%   95.52%   +10.25%
===========================================
  Files           4        4
  Lines         129      134        +5
===========================================
+ Hits          110      128       +18
+ Misses         19        6       -13

Impacted Files
Coverage Δ

pvconsumer/app.py
90.16% <100.00%> (+24.09%)
:arrow_up:

Continue to review full report at Codecov.

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


Completely remove certification

And then there were none...

Move the rest of the *.go files out of certification

Signed-off-by: Brad P. Crochet<EMAIL_ADDRESS>

As a library caller, this PR would not allow me to extract artifacts, such as the preflight.log, from my execution. The artifacts package needs to be made available so that a library caller can manipulate the context with the appropriate ArtifactWriter.

How would a library caller retrieve their artifacts if the artifact writer definitions are all internal

Should library users with to retrieve the artifacts, I would propose that a (future) API could be added to reach internal and get a tar to get the artifacts.

Should library users wish to retrieve the artifacts, I would propose that a (future) API could be added to reach internal and get a tar to get the artifacts. I currently view artifacts as a preflight-specific implementation detail, and not a general purpose thing for library users.

This doesn't work for me. If a library caller gets an error or failing result, (i.e. they don't pass), they have nothing they can do to troubleshoot the problem.
I don't see it as strictly internal functionality because of this. I also don't see it as a CLI-specific implementation detail.

I also don't see a reason to remove the formatters. The API isn't complicated, and it does a single thing - and guides developers on how they can implement their own.
With this said, I don't think it's strictly necessary. If you want it removed, you'll need to update doc/LIBRARY.md to remove the reference to it.

Should library users wish to retrieve the artifacts, I would propose that a (future) API could be added to reach internal and get a tar to get the artifacts. I currently view artifacts as a preflight-specific implementation detail, and not a general purpose thing for library users.

This doesn't work for me. If a library caller gets an error or failing result, (i.e. they don't pass), they have nothing they can do to troubleshoot the problem.
I don't see it as strictly internal functionality because of this. I also don't see it as a CLI-specific implementation detail.

I think I can meet you halfway here. While I don't think the current implementation is necessary to be exposed, I do think that some mechanism to retrieve the artifacts would be useful to a library user. So, what I would propose is moving forward here, but then being thoughtful about what API we want to expose. Does that work for you? I do agree that the library user should have the opportunity to review them, I just don't think they necessarily need to write them, which is more what this artifacts implementation currently does.

I also don't see a reason to remove the formatters. The API isn't complicated, and it does a single thing - and guides developers on how they can implement their own.
With this said, I don't think it's strictly necessary. If you want it removed, you'll need to update doc/LIBRARY.md to remove the reference to it.

I can come along with this. I'll pull them back out.

@bcrochet
Re: Artifacts

So, what I would propose is moving forward here, but then being thoughtful about what API we want to expose

This is fine - but we've got no roadmap planned on this. So, what do we do to bridge the gap until then?
I think I would have less of an issue with moving the artifacts into an internal package if executing Preflight (either policy) and having a failing or erroring result could be debugged without it. But as of today, the results for certain checks themselves tell the user top refer to the artifacts for information on how to troubleshoot.. Let alone the embedding of the preflight.log as an artifact for library callers.

As I proposed elsewhere, I think the API to artifacts should just be a 'SaveXXX', like 'SaveTar', or 'SaveFs', 'SaveDir'. Or, 'Save(opt ArtifactOption)'. I don't think the writing of artifacts is something that the library user should be relying on the library to do. If a library user wants to add artifacts, they do so to their own artifacts payload without having to reach into the library to do it. Now, to GET the artifacts that the library generates, that makes sense.

I do agree that the library user should have the opportunity to review them, I just don't think they necessarily need to write them, which is more what this artifacts implementation currently does.

While some of the implementation makes reference to "Write", It's really just a semantic. We can call these methods anything we want. The FilesystemWriter "writes" to the fs, but the MapWriter is just building a map. The WriteFile method in the ArtifactWriter interface just maintains the verbiage used historically. IIRC, the previous artifacts directory had the same function.

I get that, however, I don't think it's necessary to expose that from the library. As I previously stated, I think the library should provide the capability to get to the artifacts generated, but not be responsible for writing to the library user's artifacts.

I can get on board with this. Expose our current formatters that we've implemented, but still allow for creating your own formatter.
This tells me that these should probably be separate PRs.

However you want to do this is fine by me.

I get that, however, I don't think it's necessary to expose that from the library. As I previously stated, I think the library should provide the capability to get to the artifacts generated, but not be responsible for writing to the library user's artifacts.

Maybe we're not in the seeing each other regarding this point. The ArtifactWriter isn't something that the library caller consumes. It's effectively a choice the library caller makes, telling preflight how to write its artifacts in a way that the library caller can consume. "Write my artifacts here, and I'll retrieve them later".
As an example, if a library caller wanted to... say write an S3 Uploader ArtifactWriter - they could do that, then embed the artifact writer in the context and preflight would write its artifacts however the caller wishes.

Just to close the discussion loop here, I believe we landed on leaving the artifacts implementation on this branch as is for the moment, while @bcrochet reaches an alternative implementation that may be a bit more clearly defined for our use case.
The artifacts implementation as it exists in this branch would, therefore, move to the top level and outside of the certification module (as it is not needed).
Regarding logging, I believe we landed on exposing a few of our formatting functions as opposed to the internal formatter logic itself. Formatting, in itself, can be done however the user sees fit, and so we only intend to provide the execution our results formatting that we use as a baseline
@bcrochet please correct me if I've captured this incorrectly, it's been several days since our discussion!


[R-package] Very large l2 when training model

Description
Hi, I am using lightGBM to determine feature importances from an in-house dataset that is very sparse in nature. When training the model on this sparse dataset, I noticed that the training l2 error is very large in the order of 10^73 and the feature importance results do not agree with my domain knowledge.
I also tried running the same dataset using xgboost and the training RMSE is much smaller in the range of 0.4-0.6. Furthermore, the feature importance results make a lot more sense to me. Finally, I also compared the Gain computed from lightGBM and xgboost (see the scatter plot below) and they do not agree very well with each other. I wonder if lightGBM does any manipulation/preprocessing to the dataset which resulted in the spurious large training l2 error?
As an additional note, I ran the same feature importance code previously on the older version of lightGBM (v2.3.4) and got results that are similar to xgboost. I only started getting this weird phenomenon when I upgraded to version3+ of lightGBM.
Reproducible example
The in-house dataset testData.rds can be downloaded from here
And here is the R code:
library(Matrix)
library(ggplot2)
library(xgboost)
library(lightgbm)

# LGB portion
testData = readRDS("testData.rds")
lgbParams = list(boosting_type = "gbdt", objective = "regression",
                 learning_rate = 0.01)
inp = lgb.Dataset(data = testData[, -1],
                  label = testData[, 1])
set.seed(42)
model = lightgbm(data = inp, params = lgbParams, nrounds = 1000,
                 eval_freq = 100, verbose = 1, num_threads = 20)
oup1 = lgb.importance(model)

# XGB portion
xgbParams = list(booster = "gbtree", objective = "reg:squarederror",
                 eta = 0.01, tree_method = "hist")
inp = xgb.DMatrix(data = testData[, -1],
                  label = testData[, 1])
set.seed(42)
model = xgboost(data = inp, params = xgbParams, print_every_n = 100,
                nrounds = 1000, verbose = 1, nthread = 20)
oup2 = xgb.importance(model = model)

# Compare LGB and XGB Gain and plot
oupCompare = oup1[oup2, on = "Feature"]
ggplot(oupCompare, aes(Gain, i.Gain)) +
  geom_point() + xlab("LGB Gain") + ylab("XGB Gain") +
  theme_classic(base_size = 24) + scale_x_log10() + scale_y_log10()

Output from lightGBM:
[LightGBM] [Warning] Auto-choosing row-wise multi-threading, the overhead of testing was 0.081095 seconds.
You can set `force_row_wise=true` to remove the overhead.
And if memory is not enough, you can set `force_col_wise=true`.
[LightGBM] [Info] Total Bins 104040
[LightGBM] [Info] Number of data points in the train set: 43791, number of used features: 408
[LightGBM] [Info] Start training from score<PHONE_NUMBER>91896526252176302135050240.000000
[1] "[1]:  train's l2:1.36747e+73"
[1] "[101]:  train's l2:1.2623e+73"
[1] "[201]:  train's l2:1.18071e+73"
[1] "[301]:  train's l2:1.10743e+73"
[1] "[401]:  train's l2:1.04192e+73"
[1] "[501]:  train's l2:9.82944e+72"
[1] "[601]:  train's l2:9.29686e+72"
[1] "[701]:  train's l2:8.79174e+72"
[1] "[801]:  train's l2:8.3274e+72"
[1] "[901]:  train's l2:7.92462e+72"
[1] "[1000]:  train's l2:7.55389e+72"

Output from xgboost:
[1]	train-rmse:0.663716
[101]	train-rmse:0.504467
[201]	train-rmse:0.462098
[301]	train-rmse:0.442670
[401]	train-rmse:0.429328
[501]	train-rmse:0.419056
[601]	train-rmse:0.410899
[701]	train-rmse:0.403912
[801]	train-rmse:0.397756
[901]	train-rmse:0.391985
[1000]	train-rmse:0.386239

Comparison of Gain feature importance from xgboost vs lightGBM:

Environment info
> sessionInfo()
R version 4.0.3 (2020-10-10)
Platform: x86_64-conda-linux-gnu (64-bit)
Running under: Ubuntu 18.04.2 LTS

Matrix products: default
BLAS/LAPACK: /home/john/miniconda3/lib/libopenblasp-r0.3.15.so

locale:
 [1] LC_CTYPE=en_SG.UTF-8       LC_NUMERIC=C               LC_TIME=en_SG.UTF-8        LC_COLLATE=en_SG.UTF-8
 [5] LC_MONETARY=en_SG.UTF-8    LC_MESSAGES=en_SG.UTF-8    LC_PAPER=en_SG.UTF-8       LC_NAME=C
 [9] LC_ADDRESS=C               LC_TELEPHONE=C             LC_MEASUREMENT=en_SG.UTF-8 LC_IDENTIFICATION=C

attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base

other attached packages:
[1] ggplot2_3.3.3   lightgbm_3.2.1  R6_2.5.0        xgboost_<IP_ADDRESS> Matrix_1.3-2

loaded via a namespace (and not attached):
 [1] magrittr_2.0.1    tidyselect_1.1.0  munsell_0.5.0     colorspace_2.0-0  lattice_0.20-41   rlang_0.4.10
 [7] fansi_0.4.2       dplyr_1.0.5       tools_4.0.3       grid_4.0.3        data.table_1.14.0 gtable_0.3.0
[13] utf8_1.2.1        DBI_1.1.1         withr_2.4.1       ellipsis_0.3.1    digest_0.6.27     assertthat_0.2.1
[19] tibble_3.1.0      lifecycle_1.0.0   crayon_1.4.1      farver_2.1.0      purrr_0.3.4       vctrs_0.3.6
[25] glue_1.4.2        compiler_4.0.3    pillar_1.5.1      generics_0.1.0    scales_1.1.1      jsonlite_1.7.2
[31] pkgconfig_2.0.3

Ok, I took a look.
I was able to reproduce this behavior on my system ({lightgbm}  3.2.1  installed from CRAN, R 4.05, macOS).
[LightGBM] [Warning] Auto-choosing row-wise multi-threading, the overhead of testing was 0.212046 seconds.
You can set `force_row_wise=true` to remove the overhead.
And if memory is not enough, you can set `force_col_wise=true`.
[LightGBM] [Info] Total Bins 104040
[LightGBM] [Info] Number of data points in the train set: 43791, number of used features: 408
[LightGBM] [Info] Start training from score<PHONE_NUMBER>318345225632202477835124736.000000
[1] "[1]:  train's l2:7.61155e+74"
[1] "[101]:  train's l2:7.44365e+74"
[1] "[201]:  train's l2:7.2954e+74"
[1] "[301]:  train's l2:7.15143e+74"
[1] "[401]:  train's l2:7.0124e+74"
[1] "[501]:  train's l2:6.87951e+74"
[1] "[601]:  train's l2:6.75179e+74"
[1] "[701]:  train's l2:6.62947e+74"
[1] "[801]:  train's l2:6.51303e+74"
[1] "[901]:  train's l2:6.39489e+74"
[1] "[1000]:  train's l2:6.28377e+74"

I then tried building {lightgbm} from latest master, and found that the problem seems to have been fixed.
[LightGBM] [Warning] Auto-choosing col-wise multi-threading, the overhead of testing was 0.378029 seconds.
You can set `force_col_wise=true` to remove the overhead.
[LightGBM] [Info] Total Bins 104040
[LightGBM] [Info] Number of data points in the train set: 43791, number of used features: 408
[LightGBM] [Info] Start training from score 0.408969
[1] "[1]:  train's l2:0.432521"
[1] "[101]:  train's l2:0.262002"
[1] "[201]:  train's l2:0.226265"
[1] "[301]:  train's l2:0.211681"
[1] "[401]:  train's l2:0.202313"
[1] "[501]:  train's l2:0.194707"
[1] "[601]:  train's l2:0.188175"
[1] "[701]:  train's l2:0.18244"
[1] "[801]:  train's l2:0.177234"
[1] "[901]:  train's l2:0.172524"
[1] "[1000]:  train's l2:0.168078"

So I'm not sure what the root cause is, but I suspect that one of the stability fixes we've made recently for the R package fixed this. Maybe one or all of these:

#4155
#4246
#4247
#4252
#4265

I'm very sorry for the inconvenience, but could you try building {lightgbm} from source on latest master and see if that solves the problem for you as well?
git clone --recursive git@github.com:microsoft/LightGBM.git
cd LightGBM
sh build-cran-package.sh
R CMD INSTALL lightgbm_<IP_ADDRESS>.tar.gz

I'll start a separate conversation with other maintainers about doing a new release to CRAN soon.

Hi @jameslamb, I followed your code to install the latest version of lightGBM and I am getting exactly the same l2 training error as you posted. Thanks so much for the help and looking forward to lightGBM v3.3.0 on CRAN soon!

Ok great! Very sorry for the inconvenience.
Thanks again for the excellent bug report with a detailed reproducible example. Made it easy for me to test fixes.
You can subscribe to #4310 to be notified when the next release is out.


Improve and update the MRTCore apps

This change does the following:

For all the samples, set/correct the platform min version to 17763.
For the packaged samples, update to NuGet v8.0.1
For all the samples, ensure they build and run on x86 and x64 (Debug and Release). For arm64 (Debug and Release), just building is verified as part of this change.
For the .NET samples, don't override the .NET 5 targeting packages anymore: the version we get with the latest .NET 5 is newer

Verified
For all these sample apps, I verified that they build and run for x86 and x64, for both Debug and Release. For arm64, I just verified that they build for Debug and Release. Verifying that they run on arm64 will be done separately.

WinUI C++ sample app
WinUI C# sample app
Console unpackaged sample app
WinForms unpackaged sample app
WPF

LGTM, the only thing I would suggest is adding a note to the first section of the readme that the unpackaged samples are an experimental feature. Maybe:
Note: The unpackaged sample apps reference an experimental version of the Windows App SDK. Unpackaged app deployment is not currently supported for use by apps in production environments.

LGTM, the only thing I would suggest is adding a note to the first section of the readme that the unpackaged samples are an experimental feature. Maybe:
Note: The unpackaged sample apps reference an experimental version of the Windows App SDK. Unpackaged app deployment is not currently supported for use by apps in production environments.

Done! But I added a link as well. If you think it's better left out, please lmk.


form element focus-out

How would you recommend I implement the equivalent of a focus-out event on a form element?  I see the onChange event, but that is obviously fired on every keystroke; I'm looking to just fire an event when the user leaves a field.  Thanks

@dbinetti if you drop down to the raw element you should be able to add that yourself.  Does that work?

that's basically what I've done.  thanks!

I can confirm this does not work, as expected:
{{#form.element invisibleLabel="Value Amount"
  controlType="number"
  size="sm"
  value=amount
  onChange=(action (mut amount))
  as |el|
}}
  {{el.control focus-out=(action "amountChanged")}}
{{/form.element}}

My amountChanged:
amountChanged() {

  debug(`${this.toString()}; amountChanged()`);

},

ember-bootstrap: 2.8.0
ember-cli: 2.18.2
node: 10.16.0
os: darwin x64

I believe camelCase just might, at least a quick search through some code revealed the following
{{component el.control focusIn=(action "onFocus" "toe-height") focusOut=(action "onBlur")}}

That did it! I could've sworn I tried that combination. Oh boy, I must be truly losing my mind these days. :D Thanks for the tip @basz

:-) know the feeling. you're welcome


New version: PaddedMatrices v0.1.1

Registering package: PaddedMatrices
Repository: https://github.com/chriselrod/PaddedMatrices.jl
Created by: @chriselrod
Version: v0.1.1
Commit: 7a404072bd5b99abc42f5a277348ba4f8531864c
Reviewed by: @chriselrod
Reference: https://github.com/chriselrod/PaddedMatrices.jl/commit/7a404072bd5b99abc42f5a277348ba4f8531864c#commitcomment-38745204

Block.


Error with autosave

Error: Service Unavailable
Error: Service Unavailable
    at Request.<anonymous> (https://homebrewery.naturalcrit.com/homebrew/bundle.js:73949:19)
    at Request.Emitter.emit (https://homebrewery.naturalcrit.com/homebrew/bundle.js:1898:20)
    at XMLHttpRequest.xhr.onreadystatechange (https://homebrewery.naturalcrit.com/homebrew/bundle.js:74258:10)
{
  "status": 503,
  "method": "PUT",
  "url": "/api/update/w5XP6_TMcsPI"
}

Looks like this was a temporary busy moment on the server. Let us know if it happens again.


-subtle color background utility classes don't support opacity

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
It's easy to change the opacity of a .bg-secondary div with the bg-opacity-50 class.. however I noticed that the bg-*-subtle classes do not support changing the opacity. It would be useful if they did. I assume the subtle colors would need RGB values added as CSS custom properties for this to be enabled
If support for this isn't planned perhaps should add a note to the docs mentioning that bg-opacity classes don't work with -subtle colors.
Reduced test cases
Stackblitz demo:
https://stackblitz.com/edit/bootstrap-subtle-opacity?file=index.html
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
No response
What version of Bootstrap are you using?
v5.3.0

Right now we're not generating any -rgb variables for these colors, but we could. That feels like a slightly larger lift than a patch release, so removing the assigned project from here for now. @coliff Do you want to take a stab at something here?


Where to go for basic help?

I'm new to Python and installed the SDK for F5. I tried a few examples to learn by and most won't work.
The example to get pools works fine but I tried the create and load examples and both throw errors. Using ver. 11.5.1 on the LTM, Python 3.6 and the latest SDK. Am I missing something and is there a better place to go to ask questions?
As an example this works fine.
pool_collection = mgmt.tm.ltm.pools.get_collection()
pools = mgmt.tm.ltm.pools
for pool in pool_collection:
print (pool.name)
This throws errors.
mypool = mgmt.tm.ltm.pools.pool.create(name='mypool' , partition='Common')
Thank you,
Dave

@KDaveC what's the error you're receiving?

Here's the error's I'm seeing.
Traceback (most recent call last):
File "C:\python\test3.py", line 11, in
mypool = mgmt.tm.ltm.pools.pool.create(name='mypool' , partition='Common')
File "C:\Users\dave\AppData\Local\Programs\Python\Python36-32\lib\site-pack
ages\f5\bigip\resource.py", line 933, in create
return self._create(**kwargs)
File "C:\Users\dave\AppData\Local\Programs\Python\Python36-32\lib\site-pack
ages\f5\bigip\resource.py", line 887, in _create
kwargs = self._check_for_python_keywords(kwargs)
File "C:\Users\dave\AppData\Local\Programs\Python\Python36-32\lib\site-pack
ages\f5\bigip\resource.py", line 459, in _check_for_python_keywords
for key, val in kwargs.iteritems():
AttributeError: 'dict' object has no attribute 'iteritems'

iteritems is  a 2.x remnant, I don't think it exists in 3.x. @caphrim007 as this is in the resource (and also in the todict mixin) it's a much larger issue than just the pool.

@jasonrahm yes, this method should be using the iteritems() method provided by the six library as is done in other areas of the sdk

@KDaveC this bug is now fixed.
To answer the original question though, the available resources for help are

this github repo for bugs and feature reqs
the docs at http://f5-sdk.readthedocs.io/en/latest/
the openstack slack team https://f5-openstack-slack.herokuapp.com/

and one final note, python3 support is still a work-in-progress. So there is the chance (as you've seen here) that there are still bugs in it.
Here's the bug tracking py3 support
https://github.com/F5Networks/f5-common-python/issues/287

@KDaveC I plan to write a series of articles on using the sdk, what topics would be most helpful to you?

Thank you for the quick responses. Sorry, another noob question. How do I go about getting the update. I tried pip with -U and it said everything was up-to-date.
As for articles there are a lot of us out there that did not take any or very little programming in school so anything that better explains how to get started. A lot of the fundamentals are foreign especially with respect to object oriented languages. I also noticed that a lot is written for Python2 and of course someone just starting out is going to learn version 3 so it would be helpful to note where things might be different.

the update is on our development train, so you would need to clone from here until our next release. re: articles, I'll try and write them for 2.x and 3.x, which will be good for me since I haven't touched 3.x yet.

@KDaveC the command to update your local code from the development code where we made the change is the following
pip install --upgrade git+https://github.com/F5Networks/f5-common-python.git

@caphrim007 I'm using Windows 7 and found that I could get that to run when removing the +.
pip install --upgrade git https://github.com/F5Networks/f5-common-python.git
It downloads but then I get another error. Cannot determine archive format of C:\Users\dave\AppData\Local\Temp\pip-7p6uhza7-build

@KDaveC the + is required or else pip does not know how to process it.

@caphrim007 I tried that first and got the below error.
Error [WinError 2] The system cannot find the file specified while executing c
ommand git clone -q https://github.com/F5Networks/f5-common-python.git C:\Users
dave\AppData\Local\Temp\pip-79p0l_pn-build
Cannot find command 'git'

@KDaveC The error says exactly what the problem is
"Cannot find command git"
You need git installed to get code from github
https://git-scm.com/download/win

Thank you very much. Once again not being a developer the fundamentals are often missing. I got it updated and all the basics seem to be working now. I did find one more possible issue. When printing a description for a pool with a null value I get an error. I verified that the value didn't exist with print (pool_1.raw)
print (pool_1.description)
Traceback (most recent call last):
File "<pyshell#10>", line 1, in
print (pool_1.description)
File "C:\Users\A465286\AppData\Local\Programs\Python\Python36-32\lib\site-packages\f5\bigip\mixins.py", line 127, in getattr
raise AttributeError(error_message)
AttributeError: '<class 'f5.bigip.tm.ltm.pool.Pool'>' object has no attribute 'description'

Thank you again for the information. This should be a enough to keep me busy for a while..


Homepage improvements

Homepage revisions

spacing reduced in upper sections
placeholder image added to the masthead where a GUI screenshot will go (we will need a GUI screenshot that shows charts and data to replace the placeholder image currently here)
combined the 2 testimonials into a carousel further up on the page
organized testimonials into the frontmatter section of the homepage markdown file

Unrelated fixes/improvements

improved the dev script to eliminate random crashes due to VuePress memory usage (see #1819 in the VuePress repo)
fixed a spacing issue on a tiny breakpoint range for the main navigation

@subnetmarco fixed the build error and launched. It was the carousel plugin I was using. I tried 4 separate ones before I found one that played well with VuePress' build process and SSR. Build error is completely gone now and no warnings either.


Unable to use Mixpanel/AppExtension in iOS Extension who's target uses use_frameworks!

I'm having a problem including Mixpanel/AppExtension with my iOS extension's target's dependency definition in my podfile when using Cocoapods 0.39.0.  This specifically happens when I also have told that target to use_frameworks!.
When I run pod install I get errors:
2016-02-16 19:23:09.511 ruby[70533:7934883] warning:  The file reference for "Mixpanel.framework" is a member of multiple groups ("Products" and "Products"); this indicates a malformed project.  Only the membership in one of the groups will be preserved (but membership in targets will be unaffected).  If you want a reference to the same file in more than one group, please add another reference to the same path.
Integrating client project
Sending stats
Pod installation complete! There are 2 dependencies from the Podfile and 1 total pod installed.

[!] [Xcodeproj] Generated duplicate UUIDs:

PBXFileReference -- /mainGroup/children/children:displayName:Mixpanel.framework,explicitFileType:wrapper.framework,includeInIndex:0,isa:PBXFileReference,name:Mixpanel.framework,path:Mixpanel.framework,sourceTree:BUILT_PRODUCTS_DIR,,displayName:Mixpanel.framework,explicitFileType:wrapper.framework,includeInIndex:0,isa:PBXFileReference,name:Mixpanel.framework,path:Mixpanel.framework,sourceTree:BUILT_PRODUCTS_DIR,,displayName:Pods_TestExtension.framework,explicitFileType:wrapper.framework,includeInIndex:0,isa:PBXFileReference,name:Pods_TestExtension.framework,path:Pods_TestExtension.framework,sourceTree:BUILT_PRODUCTS_DIR,,displayName:Pods_TestShareExtension.framework,explicitFileType:wrapper.framework,includeInIndex:0,isa:PBXFileReference,name:Pods_TestShareExtension.framework,path:Pods_TestShareExtension.framework,sourceTree:BUILT_PRODUCTS_DIR,,displayName:Products,isa:PBXGroup,name:Products,sourceTree:<group>,/Products/children/displayName:Mixpanel.framework,explicitFileType:wrapper.framework,includeInIndex:0,isa:PBXFileReference,name:Mixpanel.framework,path:Mixpanel.framework,sourceTree:BUILT_PRODUCTS_DIR,/Products/Mixpanel.framework

I've created a sample project that demonstrates the issue:
https://github.com/obuseme/TestExtension
Clone that and run pod install with Cocoapods 0.39.0 and you'll see the error.
This is likely related to https://github.com/CocoaPods/CocoaPods/issues/4370
Is there a solution short of upgrading to Cocoapods 1.0.0? (I'm kind of not ready to do that)
Thanks

Any reason you don't want to upgrade to 1.0.0? We're using it here with no issues.
Regardless, I downgraded my cocoapods install back to 0.39.0, and I was able to reproduce your behavior. If you don't want to upgrade you can disable deterministic UUIDs on 0.39.0 with an environment variable.
Here are my results with your test project and your version of cocoapods:
➜  TestExtension-master $ COCOAPODS_DISABLE_DETERMINISTIC_UUIDS=YES pod install
[!] Unable to load a specification for the plugin `/Library/Ruby/Gems/2.0.0/gems/cocoapods-deintegrate-1.0.0.beta.1`
Updating local specs repositories

CocoaPods 1.0.0.beta.3 is available.
To update use: `gem install cocoapods --pre`
[!] This is a test version we'd love you to try.

For more information see http://blog.cocoapods.org
and the CHANGELOG for this version http://git.io/BaH8pQ.

Analyzing dependencies
Downloading dependencies
Using Mixpanel (2.8.3)
Generating Pods project
Integrating client project
Sending stats
Sending stats
Pod installation complete! There are 2 dependencies from the Podfile and 1 total pod installed.


[TH2-4817] [TH2-5067] Add search direction for group request. Add streams filter for gRPC group request

@OptimumCode I have incremented version of gRPC interface because the CI to build gRPC optionally hasn't been completed yet

The last changes look OK for me


Restore-DbaDatabase, -RestoredDatabaseNamePrefix not working

Is this:
Just place "x" to indicate selection (e.g. "[x]")

[ ] feature
[x] bug:

Current development
Restore-DbaDatabase -SqlInstance aninstance -Path '\\path_to\restoretemp$' -DatabaseName dbname -MaintenanceSolutionBackup -XpDirTree -NoRecovery -WithReplace
and
Restore-DbaDatabase -SqlInstance aninstance -Path '\\path_to\restoretemp$' -DatabaseName dbname -MaintenanceSolutionBackup -XpDirTree -NoRecovery -WithReplace -RestoredDatabaseNamePrefix 'prettyprefix'
end up with the same result, dbname being restored, while I think it should become prettyprefixdbname
Mind that I'm passing -withreplace because the pre-check on existing db on the destination is not done on the prefixed name but on the databasename.

That's by design
DatabaseName beats everything.
 L575-578
Could shove in a warning message to let people know what's about to happen if both are specified?

Ok, I'll retire the "bug" spec and ask for a feature then :P
From the params description is in-spec of what you're saying but DatabaseName it's also used to filter through all the backup files in the dir.
Being able to specify a fixed target name when you need to do 1:1 restores could be beneficial because pre-filtering the file set outside this cmdlet requires basically reimplementing a nice amount of the same code (or is there something that can be used instead already?)

Yes, currently if you specify a DatabaseName we filter all the backups passed in down to that single database.
If you don't then we will try to restore every database passed in. That's what the prefix is there for. So if you wanted to clone all the user dbs on an instance then you could do:
Get-DbaBackupHistory -SqlInstance MyServer  | Restore-DbaDatabase -SqlInstance MyServer -DestinationFilePrefix Clone -RestoredDatababaseNamePrefix Clone
to avoid anything that already exists.
There's a couple of solutions that spring to mind for multiple dbs:

Change databaseName to an array of strings, and modify the filtering. Then that could be used with the -RestoredDatababaseNamePrefix

Allow a complex Old to New name mapping. Would end up being something like the FileMapping parameter where it would want a hashtable to work

the more I think of it the more I like best a get-me-whatever that scans files, that I can accumulate/edit before passing it down to restore-dbadatabase .... else the params on restore-dbadatabase will pile up with each and everyone's need.

I can think of way to handle that with some code reuse. Get-DbaBackupFile
as a function name? Coukd then use the trustDbBackupHistory functionality
to save double scanning?
On Thu, 13 Jul 2017, 10:02 Simone Bizzotto<EMAIL_ADDRESS>wrote:

the more I think of it the more I like best a get-me-whatever that scans
files, that I can accumulate/edit before passing it down to
restore-dbadatabase .... else the params on restore-dbadatabase will pile
up with each and everyone's need.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/sqlcollaborative/dbatools/issues/1657#issuecomment-315017972,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFWoZg-hKkjgvnYt9ckTCDUGIVAHxgIIks5sNd1CgaJpZM4OVVCA
.

yup, something like that. Also, being able to have something that pre-digests something restore-dbadatabase can handle will allow high-level functionality, as caching the scan. Maybe at this point open a feature req issue and close this, so you can get it tracked.

Take 1 lashed up here - https://github.com/sqlcollaborative/dbatools/tree/Get-DbaBackupInformation
It needs some TLC before a PR, but want to make sure I'm on the right track before going to far, usage examples:
Get-DbaBackupInformation -SqlInstance localhost\sqlexpress2016 -Path C:\dbatools\ -DatabaseName blogtest, restoretime -Recurse | Restore-DbaDatabase -SqlInstance localhost\sqlexpr
ess2016 -DestinationFilePrefix BIT -DestinationFileSuffix BT -RestoredDatababaseNamePrefix BIT -TrustDbBackupHistory
Will scan everything, filter down to those listed dbs and then push through restore. Uses TrustDB to avoid a second scan of files.
Get-DbaBackupInformation -SqlInstance localhost\sqlexpress2016 -Path C:\dbatools\ -DatabaseName blogtest, restoretime -XpDirTree | Restore-DbaDatabase -SqlInstance localhost\sqlexpr
ess2016 -DestinationFilePrefix BIT -DestinationFileSuffix BT -RestoredDatababaseNamePrefix BIT -TrustDbBackupHistory
Same thing, but uses XpDirTree
-SourceInstance works in the same manner
It outputs Sqlcollaborative.Dbatools.Database.BackupHistory objects, so you could shove a Where-Object  between it and the restore to really go to town on the filtering
Or it could be saved somewhere and then pushed in at a later point in time.
That the sort of thing you were thinking of?

hey @niphlod - let me know where we are at. In general, is the command ready / have we concluded this an enhancement or bug?

It'll be an enhancement. Basically it's allowing another way to build up
backuphistory and pass it into the restore stuff.
The function I pushed up is working, but doesn't meet style guidelines and
could do with some more error catching, But does the basics of what it's
supposed to.
Main thing I want to add is a way of persisting the information (so someone
can scan a load of files overnight and then restore from that during the
day to save scanning them repeatedly).
So just wanted a 'Yeah, this is in scope' type reply before putting more
time into it,
On Sun, 16 Jul 2017 at 14:07 Chrissy LeMaire<EMAIL_ADDRESS>wrote:

hey @niphlod https://github.com/niphlod - let me know where we are at.
In general, is the command ready / have we concluded this an enhancement or
bug?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/sqlcollaborative/dbatools/issues/1657#issuecomment-315608143,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFWoZmSW2pO5cucqduOtgJ0g6RMaN836ks5sOgr-gaJpZM4OVVCA
.

Sweet, k thanks! I'll move this out of bagofbobbish.

@Stuart-Moore : sorry for checking back with a not-so-sweet delay, but YESS, I sooooo like it!
(incidentally, "opening" this up also enables scanning on one instance and restoring into another, changing paths that do not need to be uniquely accessible (i.e. when you are shipping manually backups between shares and you do not leverage something like DFS or azure shares))

@Stuart-Moore : do you need any help in bringing this to life ?

funnily enough I was playing with it the other day. Let me dig some notes
out and see where I got to.
Now we have a formal type it's a bit easier to make everything tie together
On Tue, 3 Oct 2017 at 20:41 Simone Bizzotto<EMAIL_ADDRESS>wrote:

@Stuart-Moore https://github.com/stuart-moore : do you need any help in
bringing this to life ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sqlcollaborative/dbatools/issues/1657#issuecomment-333955560,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFWoZgzBCte0-FlslG_q2ipPN58vjlx7ks5soo36gaJpZM4OVVCA
.

haha, no problem man, just happy to lend an hand if you need it (also, factorizing in a single place the "logic" for the restore checks could prove beneficial)

Yes. Was thinking while cleaning the kitchen that doing this right would
remove a lot of stuff from the main function. Everything eventually coming
in to get-filtered as a dbatools history object.
And I’ve been playing with redoing the filtering as a reverse tree walk.
Makes it easier to cope with recovery forks if we need to, and makes one of
the anomalies less awkward as well.
Times the issue. But hopefully this migration project should be dead one
way or another in a fortnight
On Tue, 3 Oct 2017 at 20:52, Simone Bizzotto<EMAIL_ADDRESS>wrote:

haha, no problem man, just happy to lend an hand if you need it (also,
factorizing in a single place the "logic" for the restore checks could
prove beneficial)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sqlcollaborative/dbatools/issues/1657#issuecomment-333958396,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFWoZhkRkxTEiR83DnPIDOufvla4zXQiks5sopCFgaJpZM4OVVCA
.

Get-DbaBackupInformation is back in as a new PR.
Once it's in I'll start looking at using it as new input parser for Restore-DbaDatabase.

OK, all of this is now 'in'
Just need to look at replacing the Get-DbaBackupHistory filtering with the new stuff, but will shove that in as a new issue


Running kube-spawn setup without the overlay module loaded results in failure

We should try to load the module if it's not available. Also, the tip given doesn't apply for this case.
> sudo GOPATH=$GOPATH SYSTEMD_NSPAWN_PATH=$(which systemd-nspawn) CNI_PATH=$GOPATH/bin ./kube-spawn setup --image=coreos --nodes=3
2017/07/27 10:48:20 Checking base image
2017/07/27 10:48:20 k8s/kubelet already downloaded, skipping...
2017/07/27 10:48:20 k8s/kubeadm already downloaded, skipping...
2017/07/27 10:48:20 k8s/kubectl already downloaded, skipping...
2017/07/27 10:48:20 k8s/kubelet.service already downloaded, skipping...
2017/07/27 10:48:20 k8s/10-kubeadm.conf already downloaded, skipping...
Image resized.
Resize '/var/lib/machines' of 'max'
2017/07/27 10:48:20 Error running node: unable to create overlayfs on "/home/iaguis/work/go/src/github.com/kinvolk/kube-spawn/.kube-spawn": overlayfs is not available. Try to pass a directory with a different filesystem (like ext4 or XFS) to --kube-spawn-dir.

I thought we already added the autoloading overlay module: https://github.com/kinvolk/kube-spawn/blob/master/cmd/kube-spawn/init.go#L81
But it was actually done only init, not in setup. :-(
As setup is called before init, the autoloading doesn't happen before the requirement checks in setup.
I'll fix it by adding EnsureRequirements() to setup as well.


Add feature row normalization to representation graphs

Could be useful when density of metadata is inconsistent.

Added as a pre-process (instead of in the repr graphs) in https://github.com/jfkirk/tensorrec/pull/43
Closing


Chat DB download missing user chats

Bug Report
Description
Bug Summary:
I as the Admin downloaded the entire database and opened the .db file in SQLite viewer.
I could see all the users registered on the host, but the db did not have their chats in it when I opened it.
The chat session history is needed for audit purposes and reporting.
I set the permissions for user role to "downt allow chat deletion".
Are all the prompts and responses for all users supposed to be logged in the SQLite db?
Steps to Reproduce:
Downloaded the db a couple of times, but no luck finding other user role chats.
I was able to see their chats when downloading the JSON with all chats, but this is less useful vs having the chat session history in a db.
Expected Behavior:
I was hoping to see all the chats for all users in the db after the download.
Actual Behavior:
I am only seeing my own chats.
Environment

Open WebUI Version: [0.1.120]

Operating System: macOS

Reproduction Details
Confirmation:

[ y] I have read and followed all the instructions provided in the README.md.
[ y] I am on the latest version of both Open WebUI and Ollama.
[ n/a] I have included the browser console logs.
[ n/a] I have included the Docker container logs.

Logs and Screenshots
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Docker Container Logs:
[Include relevant Docker container logs, if applicable]
Screenshots (if applicable):
[Attach any relevant screenshots to help illustrate the issue]
Installation Method
[Describe the method you used to install the project,: Docker

I would try copying it from the container manually to verify there's no user chats showing in it:
docker cp open-webui:/app/backend/data/webui.db .

Can you also share how and what query you're using to extract user chats?

Thanks @justinh-rahb the file copy works fine on CLI per your command above. It yields the same result as the "download the database" command from the GUI. Both methods do not show user chats other than my own. I am using SQLite Browser to view the files, I have not yet started creating SQL to query the db as I dont have the full db yet...
In the admin role, I have set the "chat delete" off so that users have not been able to delete their own chats.
Any thoughts?

@justinh-rahb I am assuming that all chats from all users are always supposed to be stored in the SQLite db?

I see different user_ids listed in your screenshot, you're saying these are all you? My eyes are telling me a different story.


Add Livedata

Sometimes it is necessary to inspect scalar values within an epoch.
This commit replaces tqdm with a modification to support livedata.
This should also be benchmarked a large-scale models. In simple MNIST examples I get no significant overhead.

There is a plan to more generally support trigger_step() with user-specified data. Some discussion were in #39. The idea is that a Callback should define what it needs every step and what to do with it, not only to print them.

But the problem with any before/after step design is that this needs explicit addition sess.run. Here in this implementation it is simply extracted from the graph, when it is already computed.

It will not need an extra sess.run. The trainer should know what all callbacks need, and fetch those tensors together with train_op in one sess.run.

So you mean, for some basic statistics of scalars you prefer callbacks instead of simple tf.collections? Is was first thinking about add this functions to TrainerConfig with regEx.
It seems like flake8 is really bothersome wrt. to xrange, though it is caught in the correct way.

In fact I'd prefer no logic been implemented inside trainer if they can be done outside. The current epoch-wise logging is also done outside.

I understand the current design. But within epochs you need to pass the data to tqdm or midifications of it. Another idea would be a TrainingStepCallback which contains the code of the most-inner loop from the training-main-loop. This would probably also help to change training-logic to GAN training. What do you think?

I can consider an option to disable tqdm, so that users can have more control over what to display within steps.

Please leave the PR as-is or close it for now. We'll revisit it and can adopt the live data monitor when trigger_step is ready.

Any clever idea to adapt this feature as a step-trigger? Overriding just the default? Or replacing the tqdm callback?

Now that tqdm is a callback, this can probably be implemented as a callback as well. And then users get to choose what to use.

Do you think this tqdm feature works for the case here?

I am not sure if the progress bar really has to be a progress.

What do you mean?

@ppwwyyxx very nice refactoring!
I added these extra_fetches to Progressbar directly using postfix.
It would be really cool, if tqdm could display both: examples/sec and sec/example.
https://github.com/tqdm/tqdm/issues/341


Sharepoint Online File upload limit through APIs

What type of issue is this?
Question
What SharePoint development model, framework, SDK or API is this about?
SharePoint REST API
Target SharePoint environment
SharePoint Online
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[ ] 💥 Microsoft Edge
[X] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details

browser version
SPFx version
Node.js version
etc

Issue description
We are using the following configurations to setup sharepoint APIs integrations and use them in our application.
https://docs.microsoft.com/en-us/sharepoint/dev/solution-guidance/security-apponly-azureacs
When we try to upload a large file using these APIs into sharepoint, we are getting following message:
[title=SharePoint returned a 400 HTTP error, message=SharePoint returned the following error code: -1, Microsoft.SharePoint.Client.InvalidClientQueryException, detail=The request message is too big. The server does not allow messages larger than 262144000 bytes.]
Is there a possibility to increase the upload size limit for this particular process in sharepoint online?

Can you checked out this page for guidance on uploading large files using the chunked file upload method?
https://docs.microsoft.com/en-us/sharepoint/dev/solution-guidance/upload-large-files-sample-app-for-sharepoint


Fix for teardown eventing

Signed-off-by: aavarghese<EMAIL_ADDRESS>Error when running teardown-infra to teardown Knative Eventing resources.
>> Delete Knative Eventing from HEAD
~/knative/eventing-kafka-broker ~/knative/eventing-kafka-broker
./hack/../test/e2e-common.sh: line 67: cd: eventing: No such file or directory
ERROR: Failed to set up Eventing

Proposed Changes

Release Note

Docs

/test channel-reconciler-tests-sasl-ssl_eventing-kafka-broker_main


app.Map() changed behavior or stopped working as intended

Since I switched to beta 8 of MVC I have problems getting app.Map() to work.
Here is the Configure method of my Startup class:
public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
    app.Map("/modules/someModule", builder =>
    {
        app.UseMvc();
    });
}

This code worked as expected in Version 5.2.3, e.g. I had to enter the URL http://localhost:5000/modules/someModule/api/values to access the example ValuesController. However in the new beta 8 I get a 404 response this way and the resource is located under http://localhost:5000/api/values instead. The app.Map() does not seem to do anything at all at the moment.
I am running the testproject under version 1.0.0-beta8 of the .NET Core and x64 architecture. Also I am using the Kestrel server as host. This is my project.json:
{
  "commands": {
    "kestrel": "Microsoft.AspNet.Server.Kestrel"
  },
  "dependencies": {
    "Microsoft.AspNet.Mvc": "6.0.0-beta8",
    "Microsoft.AspNet.Server.Kestrel": "1.0.0-beta8"
  },
  "exclude": [
    "node_modules"
  ],
  "frameworks": {
    "dnxcore50": { }
  },
  "publishExclude": [
    "**.user",
    "**.vspscc"
  ],
  "version": "1.0.0-*"
}

This code:
public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
    app.Map("/modules/someModule", builder =>
    {
        app.UseMvc();
    });
}

Should be:
public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
    app.Map("/modules/someModule", builder =>
    {
        builder.UseMvc();
    });
}

I feel so stupid now... sorry for the issue...

Hah, I had to read @davidfowl 's code THREE times until I saw the difference! :smile:

I'm here because I did the same thing.  Triple Doh!


Adds a couple of missing broadcast methods

Namely:

cancel_transfer_from_savings
escrow_aprove
fill_transfer_from_savings
pow2
transfer_from_savings
transfer_to_savings

The full list of all (new) methods in steem and supported here would
be:

[ ] author_reward
[x] cancel_transfer_from_savings
[ ] comment_payout_update
[ ] curation_reward (Maybe it's broken, here we call it curate_reward)
[ ] custom_binary
[ ] decline_voting_rights
[x] escrow_approve
[x] fill_transfer_from_savings
[ ] hardfork
[x] pow2
[ ] reset_account
[ ] set_reset_account
[ ] shutdown_witness
[x] transfer_from_savings
[x] transfer_to_savings

This closes #45.

@yamadapc can you merge it?


PHPLIB-654 Remove deprecated terminology

PHPLIB-654
Tests against my test version, which I'll remove before merging.

Updated to reflect review feedback. Waiting for https://github.com/mongodb/mongo-php-driver/pull/1221 to be merged before merging.

Build failures are addressed in #835, merging despite failing CI.