cmake std filesystem 错误

vs2019
Windows 7
cmake: 3.16.0
develop分支
错误：
CMake Error at build/cmake/select_filesystem.cmake:57 (check_include_file_cxx):
  Unknown CMake command "check_include_file_cxx".
Call Stack (most recent call first):
  CMakeLists.txt:135 (include)

57行加上：
include (CheckIncludeFileCXX)
解决之后：
Looking for C++ include filesystem
Looking for C++ include filesystem - found
Looking for C++ include experimental/filesystem
Looking for C++ include experimental/filesystem - found
C++ Filesystem header:      <filesystem>
Performing Test CXX17_BUILTIN
Performing Test CXX17_BUILTIN - Failed
Performing Test CXX17_FLAG
Performing Test CXX17_FLAG - Failed
CMake Warning at build/cmake/select_filesystem.cmake:115 (message):
  nana requires C++17??, but your compiler does not support it.
Call Stack (most recent call first):
  CMakeLists.txt:135 (include)

__cplusplus < 201703L 在msvc下似乎要加：
/Zc:__cplusplus /std:c++latest
改成：
set (CMAKE_REQUIRED_FLAGS       "/Zc:__cplusplus /std:c++latest ${CMAKE_CXX_FLAGS}")
可以正常编译。
参考链接：
https://devblogs.microsoft.com/cppblog/msvc-now-correctly-reports-__cplusplus/

Using "set" to specify the C++ standard is not portable nor is it a modern cmake best practice.
The C++ standard is already being expressed in a compiler independent manner, so whatever is going wrong must be some cmake nuance or a compiler bug. Please upload CMakeError.log and CMakeOutput.log.
It's redundant to  specify target_compile_features twice with a different set of constraints, and it might be causing problems here. In the top level cmake file you'll see this.

  add_library(nana)
  add_library(nana::nana ALIAS nana)
  target_compile_features(nana PUBLIC cxx_std_17)

  #  need after cxx_std_14 or cxx_std_17 ??
  target_compile_features(nana
          PUBLIC cxx_nullptr
          PUBLIC cxx_range_for
          PUBLIC cxx_lambdas
          PUBLIC cxx_decltype_auto
          PUBLIC cxx_defaulted_functions
          PUBLIC cxx_deleted_functions
          PUBLIC cxx_auto_type
          PUBLIC cxx_decltype_incomplete_return_types
          PUBLIC cxx_defaulted_move_initializers
          PUBLIC cxx_noexcept
          PUBLIC cxx_rvalue_references
          )

That second target_compile_features block may be the problem. Try commenting it out and try again, and if that doesn't work, uncomment it and then comment out the "cxx_std_17" line.
References:

https://crascit.com/2015/03/28/enabling-cxx11-in-cmake/
https://resharper-support.jetbrains.com/hc/en-us/community/posts/360003534559-Unable-to-set-C-standard-in-a-Visual-Studio-2019-cmake-open-folder-style-project
https://github.com/microsoft/vscode-cpptools/issues/1990

Did you try the msbuild or the vcxproj method to compile nana?
https://ci.appveyor.com/project/qPCR4vir/nana
ppetraki@vanguard:~/Sandbox/hacking/nana-develop$ ls build/vc2019/
nana.sln  nana.vcxproj  nana.vcxproj.filters

Tks.
I only test it, i don't know much about cmake.
1.cpp
#if !defined (__cplusplus) || (__cplusplus < 201703L)
                #error NOCXX17
                #endif
                int main() {}

cl 1.cpp /std:c++17, will output:

用于 x86 的 Microsoft (R) C/C++ 优化编译器 19.22.27905 版
版权所有(C) Microsoft Corporation。保留所有权利。
1.cpp
1.cpp(2): fatal error C1189: #error:  NOCXX17

Hi, thank you for testing and reporting!
This was a hot fix for others peoples problems, but thank to report this new problem. I will try to fix it.
For your concrete problem: if you don't know cmake well, then it is best for you to use the provided VS sln and projects in Nana and Nana-demo repositories.

Now @ppetraki, this is in a .cmake file for Filesystem selection. This is not to set the global c++ flag, that is set directly with the cmake command you pointed.
What would be a better alternative to ˋset (CMAKE_REQUIRED_FLAGS ...)ˋ?

@qPCR4vir  CMAKE_REQUIRED_FLAGS is a internal cmake option.
If someone wants to be C++17 (or 20) from top to bottom to get all the compiler optimizations then they're going to have to do something like this. https://gitlab.kitware.com/cmake/cmake/issues/17146 , or hack the project.
IMHO you must distinguish between required language support and required libraries. If Nana 1.x is working to stay as a C++11 AND UP project, then the target_compile_features line should be std_cxx_11.
https://crascit.com/2015/03/28/enabling-cxx11-in-cmake/
https://cmake.org/cmake/help/v3.12/manual/cmake-compile-features.7.html
Right now it's a PUBLIC requirement, which means it's transitive. Worse, if I try to override it, it kinda ignores me. Working with an older nana branch, when setting std_cxx_11 and deleting all those extra compile options. It removed the --std= entirely from the command line, which means it's floating to the latest version that the compiler supports. I would be reasonable to expect that if I declare that 11 is the min, then the project self-configures to use boost, and if it isn't there, it fails. It overrode my intent.
https://pabloariasal.github.io/2018/02/19/its-time-to-do-cmake-right/

For example, the property COMPILE_OPTIONS encodes a list of options to be passed to the compiler when building the target. If a target must be built with all warnings enabled, for instance, this list should contain the option -Wall. This is a private property used only when building the target and won’t affect its users in any way.
On the other hand, the property INTERFACE_COMPILE_FEATURES stores which features must be supported by the compiler when building users of the target. For instance, if the public header of a library contains a variadic function template, this property should contain the feature cxx_variadic_templates. This instructs CMake that applications including this header will have to be built by a compiler that understands variadic templates.

Again the emphasis is on language support, not additional libraries provided by newer versions of the language. That is a library dependency, of which you have quite a few already.
Supporting boost, gnu c++, clang c++, and msvc++ is going to require you to code to the lowest common denominator for "filesystem support". See, https://www.bfilipek.com/2019/05/boost-to-stdfs.html . Not everything from boost made it into std::filesystem. Apparently it isn't even consistent across versions of std::filesystem per the clang bug I just filed against 1.7.3.  https://github.com/qPCR4vir/nana/issues/37
Also see,
"Portable linking for C++17 std::filesystem" https://gitlab.kitware.com/cmake/cmake/issues/17834
and
https://github.com/vector-of-bool/CMakeCM/blob/master/modules/FindFilesystem.cmake
To get out of std::fs config hell. You could set a new floor version like c++20 for Nana when you commit to 2.x. Make it a breaking change even. The project is small and the community around it is nimble enough to tolerate that.
We don't all get to move up to the latest version of C++ in our established projects, even if it the standard is backwards compatible. The whole fear of the unknown FUD keeps many projects at the C++ std they were conceived with. Sure we can edit the subproject, but now we get to maintain it too.
So to recap, what you really have today "per the cmake code", is a C++17 project, that can go backwards to as far as C++11, iif the developer changes the minimum required version. At which point you must use boost. Or, you can stay on 17 and either user the std or boost, depending on the whether the fslib provided by your compiler suite fully complies with the standard, and if it doesn't, you get to use boost.
The CI doesn't even appear to be testing a range of C++ versions so... users are going to be the first ones to find out that when this breaks. One day, someone is going to add lambda arguments that use auto to libNana and it's going to break on C++11 because the CI didn't catch it. That's "language support". You've conflated language support with additional libraries provided by the standard and it's made a huge config matrix to test which frankly, isn't creating a lot of value for your project and is hurting it in real ways. I can't even build it out of the box as a straight C++17 project anymore (1.7.3 RC).
We just want to get the bits off the disk and into memory.
So how do we move forward from here as the cats already out of the bag?

Nana 1.x will have to continue to walk the line of a C++11 capable project, but is primary developed and tested on C++17. A CI regression suite must be established ensure 11 and 14 can build with Boost etc.
Do a better job of determining the suitability of the std::fs library provided by the target platform and fail at project configuration time if no suitable fallback is available (e.g. Boost).
Shim filesystem support and use the minimum API set available between boost and the std, code whatever helpers we need and keep them in our namespace.
Strongly consider committing to a single build system, you have like 4 now, which compounds the problem of proper fs detection and support.
Plan for a Nana-2.x branch that can start at C++20 (module support?) . At which point you should be able to drop the option for boost filesystem entirely.

Hi @ppetraki,
Thank, interesting - it is very valuable what you said. I wish I had more time to continue this, really. I will try to respond. Some of the links are very enjoyable, but none have any relation with CMAKE_REQUIRED_FLAGS. This is not only a common and the recommended, but  the only way to use check_cxx_source_compiles (I think). So, don't worry, no fire here. I would like very much if after carefully reading the relevant link about check_cxx_source_compiles and the link abot MSVC @bstaint provided in the original post you may sugest a better variant for our select_filesystem.cmake: the "error" come from a fail in line 104 and in line 110 , because MS uses other flags. The irony is that VC have had good support for filesystem for long time. But with VC I always use our slns and projects. This is a very concrete issue. The rest of what you write is another history. So...
People said: simple things have to be simple to do, which almost means common things have to be simple to do. Some time ago the common thing was c++11, and the nana "trivial" build was for c++11. But now it is c++17 and we are in the transition to that. Still, one have the possibility to do complex things.. at the cost of some difficulties. You certainly can continue to use c++11 and nana but with some care in the build system configuration, and is not our priority anymore.

library dependency, of which you have quite a few already

sorry? what dependency?

Supporting boost, ...

we have never supported boost. We had no interest in that. Boost can very well support by self and don't need our support. We have (ab)used boost to implement the sdt::filesystem some compilers (libraries) don't provide in some platforms (gcc/MinGW). Years ago this was difficult, but doable. But the c++ std evolved and diverged from boost. And the nana own filesystem implementation evolved too but in the std direction. Now we prefer to use nana implementation if no std is available rather than boost.
And yes, the first thing we will do with c++20 version of nana is to eliminate all the "legacy" c++11 code and update to c++17, and then begin to experiment and adopt all the 4 big thing in c++20. It will be a lot of fun.

Strongly consider committing to a single build system, you have like 4 now,

hmm, good idea... but some people will like to kill you

Hi @ppetraki,

[select filesystem discussion]

The cmake script vector-of-bool wrote succinctly captures the discovery of std filesystem support without having to resort to platform specific define checks for C++17 support.
https://github.com/vector-of-bool/CMakeCM/blob/master/modules/FindFilesystem.cmake
Adopting this would dramatically cut down on the complexity of "select filesystem" code and reduce overall maintenance. I would draw the line with a platform supported by cmake if "set(CMAKE_CXX_STANDARD 17)" didn't do the right thing on said platform. That would require updating the min cmake version to make that work. As opposed to what you have now, which is brittle.
Also, it's not shown in the users posting, but the cxx_std_17 check would have failed at the very beginning of the project configuration if the compiler was judged to be unable to support C++17.

But now it is c++17 and we are in the transition to that. Still, one have the possibility to do complex things.. at the cost of some difficulties. You certainly can continue to use c++11 and nana but with some care in the build system configuration, and is not our priority anymore.

I've never seen a library that rolls it minimum language standard forward in the same major release version. If it's not a priority then please consider dumping the mention of 11/14 support from the front page, it's really confusing.

library dependency, of which you have quite a few already

sorry? what dependency? .. ah, you probable mean the std c++ lib and the OS (win32, X11 and related basic OS support for paint, threads, mouse, fonts, etc.)

Correct.

Supporting boost, ...

we have never supported boost. We had no interest in that. Boost can very well support by self and

Then I'm confused again, there are ifdefs and cmake logic around boost filesystem in the current codebase. If you don't support it then it shouldn't be there.

And yes, the first thing we will do with c++20 version of nana is to eliminate all the "legacy" c++11 code and update to c++17, and then begin to experiment and adopt all the 4 big thing in c++20. It will be a lot of fun.

 Codeblocks is cross platform, so that matrix is multiplied by 3, and cmake basically supports everything. You easily have 10 build variations across IDEs and platforms today. IMHO once you hit 2.x, "one" build system should be the official version that the CI checks all the build/link type variations and the rest is community supported. You want to be the GUI business, not the build system business right?

Hi!
I have simplified the script, eliminating the direct c++17 test, and now test only fs.
Could you please test again with MSVC and clang(https://github.com/qPCR4vir/nana/issues/36, https://github.com/qPCR4vir/nana/issues/37), etc., before I merge back to the RC?
Here: https://github.com/qPCR4vir/nana/tree/fs
A key point for MSVC will be
set (CMAKE_REQUIRED_FLAGS "${CMAKE_REQUIRED_FLAGS_ORIGINAL} /std:c++17")
Please change  /std:c++17 until it compile correctly.
In my tests I have (Ubuntu/gcc 8.3):
-- Performing Test CXX_std__cpp17_FS_stdcppfs - Success
-- C++: -std=c++17; Filesystem library:   stdc++fs

and (MinGW/gcc 9.2)
-- Performing Test CXX_std__cpp17_FS_BuiltIn - Success
-- C++: -std=c++17; Filesystem library: builtin

output:
Performing Test CXX_std__cpp17_FS_BuiltIn
Performing Test CXX_std__cpp17_FS_BuiltIn - Failed
Performing Test CXX_std__cpp17_FS_stdcppfs
Performing Test CXX_std__cpp17_FS_stdcppfs - Failed
Performing Test CXX_std__cpp17_FS_cppfs
Performing Test CXX_std__cpp17_FS_cppfs - Failed
Performing Test CXX_std_cpp17_FS_BuiltIn
Performing Test CXX_std_cpp17_FS_BuiltIn - Success
C++: /std:c++17; Filesystem library: builtin

Thank!

There is still a bug where the root cmakefile's c++ std will be overwritten by the filesystem check because you directly manipulate those variables without previously saving it's state. cmake's handles this with, https://cmake.org/cmake/help/v3.0/module/CMakePushCheckState.html.
Without this, the project's --std will always be dragged back to c++17 after you check for fs support.
This is how v.o.b addressed it, making his cmake script project and state independent.

There is still a bug where the root cmakefile's c++ std will be overwritten by the filesystem check because you directly manipulate those variables without previously saving it's state. cmake's handles this with, https://cmake.org/cmake/help/v3.0/module/CMakePushCheckState.html.

Could you elaborate on that?

Without this, the project's --std will always be dragged back to c++17 after you check for fs support.

No, no. Here we don't change "the project's --std " we only change the cmake test variables which do not affect the project. Ok, we can set back like in line set (CMAKE_REQUIRED_LIBRARIES ${CMAKE_REQUIRED_LIBRARIES_ORIGINAL}) the set (CMAKE_REQUIRED_FLAGS "${CMAKE_REQUIRED_FLAGS_ORIGINAL}") too. But this don't affect the project.
The only project state we change is like in: target_link_libraries     (nana PUBLIC  stdc++fs)
And when it find a working fs, it is good that it change this variables (so next user test will be consistent with this). If this make an error, that is good, and said the user it have some conflict. If std fs need some flags the user dont want, he have to set NANA_CMAKE_NANA_FILESYSTEM_FORCE and the std he want and avoid std fs.

This is how v.o.b addressed it, making his cmake script project and state independent.

It's pretty clear. You just go ahead and write into _REQURIED_FLAGS etc  without saving the original state. The push/pop functions provided by CMakePushCheckState protect those vars. It's been around since 3.0.2 so it's probably a good idea to use it.

write into _REQURIED_FLAGS etc without saving the original state.

we save before change: line 97, 98: set (CMAKE_REQUIRED_FLAGS_ORIGINAL ${CMAKE_REQUIRED_FLAGS})

The push/pop functions provided by CMakePushCheckState protect those vars. It's been around since 3.0.2 so it's probably a good idea to use it.

we would need to complicate the logic even more to decide when we want to leak the variables changed and when not, which is what we are doing manually. This variables are global for some reason (to be used by downstream-test), not just local arguments. CMakePushCheckState make actually it locals.


3.2.7: use of pkg_resources is deprecated

[tkloczko@pers-jacek NeuroM-3.2.7]$ grep -r pkg_resources
doc/source/conf.py:from pkg_resources import get_distribution

From https://setuptools.pypa.io/en/latest/pkg_resources.html

Use of pkg_resources is deprecated in favor of importlib.resources, importlib.metadata and their backports (importlib_resources, importlib_metadata). Some useful APIs are also provided by packaging (e.g. requirements and version parsing). Users should refrain from new usage of pkg_resources and should work to port to importlib-based solutions.

Good catch. I missed it when I replaced it in the package code. Should be good now with #1104

Thank you 😄 🙇♂


Skip css function call when the template literal is pure

skipPureString
Consider the following snippet
const flex = css`
  display: flex;
`;

const Container = styled.div`
  ${flex}
`;

Since the flex css is actually a pure template literal (i.e. no interpolations), we could omit the css function call to save us some bytes and prevent an unneeded function call. The below snippet is identical to the above.
const flex = 'display: flex;';

const Container = styled.div`
  ${flex}
`;

But sometimes we would want to keep the css tagged template, like when we want IDE syntax highlighting support, or prettier support. Then it results in an additional css call.
Most of the time, it shouldn't really matters. The footprint is minimal and performance cost is also unnoticeable. But in the other way around, it also wouldn't harm to let babel plugin to skip the css tag for us, a free optimization.
I'm calling this feature skipPureString, and so is the feature flag in babel config options. The naming is totally TBD, as at the time I couldn't come up with a better name 😅.
Note that the order of this feature is placed immediately below the minify step, so that the content of the tag can still be minified.
This feature should be fully backward-compatible (unless someone decided to use undocumented feature or api, like type checking a css return value) since it skips all of the unsure tagged templates with expressions in them. Because of that, the feature is turned on by default.
TODOs, Caveats

[x] Add tests
[ ] Update documentation in styled-components-website
[ ] Since we will skip the css tag by default, we could actually encourage the use of css whenever possible, for syntax highlighting, prettier, minifier support out of the box.
[ ] The only caveat I can think of is that if someday we implement additional feature in css and makes skipping it somehow unfeasible. We could just remove this feature then?

Close it until I found a better way to do this.


Limit FS permissions to desktop only

This limits the filesystem access to Desktop and Downloads.
Everything still works for me but you can now only upload from Desktop. Should we add xdg-videos as well?
Suggested as a fix for #12

This works well for watching and allows uploading from Desktop or Videos directory but might be a bit limited if you are a content creator and have external storage etc.

One of the things that I have seen LBRY developing towards is not just hosting videos, but things like 3D models and music as well. With this in mind, do you think access to Documents and Music directories should be added as well?

For the time being, I am going to close this.
There are too many file types that LBRY allows that limiting the upload directories just doesnt make sense.


Add support/mapping for OpenTracing span.kind

We should support mapping of span.kind to the Instana span SDK equivalent for proper translation.  Supported types are server, producer, consumer and client.

This was fixed in https://github.com/instana/golang-sensor/pull/20


[CI/CLN] Unify import order and add flake8 test

Imports are not necessarily well-structured at the moment. This should be fixed. PyQCA/flake8-import-order should be added to the tests/CI to ensure correct import order from then on.

Is this blocked or is it just no one has picked it up yet?

No one has picked it up and I pushed it away because I always deemed other stuff to be more important.
All imports should probably be absolute. I'm not even sure if this is the case right now. If not, changing it might cause issues with the documentation build.
The rules for import order should be noted in the documentation as well.


feat: Allow by-name component access. #148

Allows for:
from h2o_wave import Q, ui, main, app

@app('/')
async def serve(q: Q):
    q.page['wizard'] = ui.form_card(box='1 1 2 4', items=[
        ui.text_xl(name='text_name', content='Wizard'),
        ui.textbox(name='textbox_name', label='Textbox'),
        ui.inline(items=[
            ui.button(name='back', label='Back'),
        ]),
    ])
    # Instead of q.page['wizard'].items[0].text_xl.content = 'foo'
    q.page['wizard'].text_name.content = 'foo'
    q.page['wizard'].textbox_name.label = 'foo'
    q.page['wizard'].back.label = 'foo'

    q.page['header'] = ui.header_card(box='4 6 4 1', title='Header', subtitle='Subtitle', secondary_items=[
        ui.button(name='button_name', label='Button'),
    ])
    q.page['header'].button_name.label = 'foo'

    q.page['example'] = ui.form_card(box='5 1 4 5', items=[
        ui.buttons([
            ui.button(name='primary_button', label='Primary', primary=True),
        ]),
    ])
    q.page['example'].primary_button.label = 'foo'

    await q.page.save()

Needs discussion

issue description: Requires modification to server-side interpreter.

@lo5 can you elaborate what you meant here? AFAIU, the whole UI state is stored client-side meaning, there is not much to be done at the server-side interpreter unless I am missing something. Apart from guarding the accessors.

page[, 'upload_progress'].caption = 'foo' # Scans all cards on page for upload_progress
page[, 'stats_table', 'search_bar'].caption = 'foo' # Scans all cards on page for search_bar inside stat_table

Wondering whether these would be useful - cc @Far0n @pascal-pfeiffer @vopani @srini-x for feedback.
Closes #148

Wondering whether these would be useful

definitely yes imho

definitely yes imho

Can you expand with some examples?

Can you expand with some examples?

I have no concrete example at hand, but I found these .items[x] accesses alsways a bit wonky and "hard to read".

I found these .items[x] accesses always a bit wonky and "hard to read" and error prone (due to only getting Ref type information)

Oh, I should have made the question more clear then. Let me rephrase. The problem you just described is already implemented in this PR: q.page['card_name'].<component_name>.<prop_to_mutate>. I am more interested in the proposals:

page[, 'upload_progress'].caption = 'foo' # Scans all cards on page for upload_progress - When would I want to update all the components with the same name?
page[, 'stats_table', 'search_bar'].caption = 'foo' # Scans all cards on page for search_bar inside stat_table - do I need a hierarchy, when I can access the components directly by name?

he problem you just described is already implemented in this PR

ah lol sry my bad.
    page[, 'upload_progress'].caption = 'foo' # Scans all cards on page for upload_progress - When would I want to update all the components with the same name?
    page[, 'stats_table', 'search_bar'].caption = 'foo' # Scans all cards on page for search_bar inside stat_table - do I need a hierarchy, when I can access the components directly by name?

That's nothing I find that useful as of now (no use case comes to mind).

I mean there are certainly use-cases for some sort of batch processing of components like enabling/disabling or resetting, but at least personally I didn't miss that feature yet.

can you elaborate what you meant here?

Given two scripts S1 and S2, say:

S1 creates the card and sets card.items[0].caption = 'foo'
S2 sets card.items[0].caption = 'bar'

The final caption will be bar.
Instead, say there was a way to name the item upload_progress:

S1 creates the card and sets card.upload_progress.caption = 'foo'
S2 sets card.upload_progress.caption = 'bar'

For this to work, the server needs to be aware that upload_progress is the name of a card, can iterate through the cards, and patch the correct card. Currently the patch algo can handle only slice-access by integer index: https://github.com/h2oai/wave/blob/master/card.go#L111-L116

More thoughts: this is tricky to do primarily because card.go has no awareness of items or even what attributes a card has. One way to do this brute-force is to scan nested attributes for a name when the map case fails, but that can be expensive in the worst case, and I don't know if .name is guaranteed to be a component name universally.
The other option is to merge your PR, but with the caveat that by-name access is not supported for scripts, or for the uni-/multicast apps.

Thanks for implementing this @mturoci . This will be super handy when updating single items on a page.
I can't say anything about the technical implementation, but I am wondering if it works on any hierarchy level of the component?
Does any process enforce name uniqueness? If not, how would that be resolved? Would that go into the direction of your second question?

page[, 'upload_progress'].caption = 'foo' # Scans all cards on page for upload_progress - When would I want to update all the components with the same name?

The other option is to merge your PR, but with the caveat that by-name access is not supported for scripts, or for the uni-/multicast apps.

I would like to avoid this if possible. Thanks for the pointers, will see what I can do.

wondering if it works on any hierarchy level of the component?

It should. If you check my example above, I target a button what is within items > inline > button.

Does any process enforce name uniqueness? If not, how would that be resolved? Would that go into the direction of your second question?

There is no enforcement from Wave side currently (https://github.com/h2oai/wave/issues/1493). The name uniqueness needs to be preserved only within the "card" scope. This means that q.page['card1'].items can have the same named items as q.page['card2']. However, if 2 or more components with the same name are present within the same card, only the first one in order gets updated currently.
Generally speaking, I think we should enforce unique names per card as it makes sense for getting the outputs via q.args and also React depends on this. Currently, it's more of an "unwritten rule".

Seems like I managed to find the optimal solution to support scripts, broadcast, multicast as well without any serious perf degradation. In fact, it should run a bit faster now.
@geomodular could you please review the Go code to make sure it's idiomatic?
The parts I am not so sure about:

Unsafe type casts.
Is fillNameComponentMap function okayish since it mutates passed hashmap, thus is not a pure function.
I believe map[string]interface{} only stores pointers to the actual objects rather than values. Is this correct?

Thanks for the review @geomodular!

If by unsafe you mean without the type checking, then I'd say it's better to check

Yes, that's exactly what I meant, especially the fillNameComponentMap part which has a lot of casts. The thing is though that all the types are expected and an err should be thrown if any of them doesn't match. Custom err is more readable than panic ofc, just not sure if worth it.
All the comments were addressed. Updated the go version via go mod edit -go 1.19  and go mod tidy.

This is a killer feature, can't wait to try it out.
Thanks for working on it! 🙏

Available in nightly, feedback / bug reports encouraged since this spans all the components throughout Wave.

This is a killer feature, can't wait to try it out.

Glad to hear that!


Add geohaiku.com

Add www.geohaiku.com, a small demo/toy which displays a (seemingly random) haiku based on your geographic (i.e. GPS) location.

Thanks for the pull request, but we have decided not to feature it. The site is a bit too simple, and of too little interest for general usage. Sorry.

That's understandable. If I get a chance to update the site with a bit more info (I think I made it way too minimalistic), I might re-submit this in the future.


[bug] Hunger bar looks odd

Describe the bug
The final hunger bar is still shown with the money, but the border is removed.
To Reproduce
Steps to reproduce the behavior:

Join in a way that enables the mod
Look at the hunger bar

Expected behavior
The hunger bar is either completely hidden or the border is included on the final hunger icon.
Screenshots

Desktop (please complete the following information):

OS: Windows

Additional context
I could understand the point of leaving the final hunger icon around to show if hunger is applied, though it's purpose alluded me for a while. Though, if there could be an option to completely hide it, I would appreciate it. Also, if it is going to stay, please add the background back please.

ShowierData is aware of this but doesnt know how to fix it

I think it has to do with the background of the hunger bar being a separate render. It actually renders the entire empty bar all at once (if I recall correctly) and it might help if the sprite for the background hunger bar is not removed but changed to a different version containing only the last one.

Bc it seems like the texture for full hunger was removed and so was the background texture, causing the weird visual bug.

I checked the source and noticed that hunger is actually getting shrunk to width 0, which is interesting. I don't know if this method could fix this bug, but it might be possible to change textures.


How do we map salesforce object field names to our app?

Dear SalesForce .Net community,
How does the API know what fields are mapped to what? using the field name as object name?
For example,

Where Field Label is Transaction ID
and Field Name is Transaction_TxnID
do I simply do this:
Transaction_TxnID {get;set;}
and the API does the rest? Or do I need to go though some other kind of mapping?

Hi @v50minasyan
Based on the doc: http://www.salesforce.com/us/developer/docs/fundamentals/salesforce_creating_on_demand_apps.pdf

Note: Within the platform, Field Name is actually stored with __c appended to the end as
a suffix (for example, Job_Description__c). This identifies it as a custom field

When using fields in formulas, you can't just refer to a field by its name. Instead, you need to refer to it by
its merge field name, also called its API name. The format of the API name is typically the name of the field
but with underscores instead of spaces. For custom fields, the API name is suffixed with two underscores
and the letter “c,” like this: Open_Date__c. This naming convention in the platform helps distinguish
between standard and custom fields.

Look at the test projects, where you have sample queries:
 _client.QueryAsync<Account>("SELECT id, name, description FROM Account");

But this query is for already existing object on the salesforce platform.
Custom objects have some fields, that are added by default like CreatedDate. They doesn't have the suffix.
If your object is custom, and your field is custom, you probably should have query like
_client.QueryAsync<Opportunity>("SELECT Transaction_TxnID__c FROM Opportunity__c");

This will fill up your class properties by JSON deserialization.
So I think yes - you should have a class property like:
string Transaction_TxnID__c {get;set;}

Just use dynamic type, and see what properties it has ;)
The other kind of query is using reflection:
_client.QueryByIdAsync<Opportunity>("Opportunity__c", id);

It will look for all properties in your class:
  fields = string.Join(", ", typeof(T).GetRuntimeProperties().Select(p => p.Name));

And list them as columns for the select, so your DTO should not have any additional properties. I can consider this behavior as a bug, but you may want to use Automapper to separate the API's dto from your actual logic.

Thanks for answering, @tomajar!

This is pretty cool: - thanks tomajar
fields = string.Join(", ", typeof(T).GetRuntimeProperties().Select(p => p.Name));
Also, I found the SalesForce developer console to be a big help. When I click browse object there it gives the exact name I was looking for.

Excellent.


Links (Ctrl + K) do not work in Products, Engagement and Findings

Bug description
You can't click on inserted links within Products, Engagements and Findings. You are not forwarded to the inserted URL.
Steps to reproduce
Steps to reproduce the behavior:

Create a Product, Engagement or Finding
Create a Link (Ctrl + K)
Try to click on the Link to get redirected --> You don't get redirected

Expected behavior
You should be forwarded to the link
Deployment method (select with an X)

[X] Docker Compose

Environment information

DefectDojo version: v. 2.14.0-dev ( 70b8ece9 )  and also in release 2.13.1

Browsers

Firefox Version 104.0
Google Chrome Version 104.0.5112.101

Screenshots
Engagement (you can't click onto the link, thus it is marked orange):

Product:(you can't click onto the link, thus it is marked orange)

Also links provided from scanners are not clickable anymore.

can confirm, it's a bug. don't know what's going on.

It looks like this problem was introduced here: https://github.com/DefectDojo/django-DefectDojo/commit/eab684362098113555378fc6100e1b27cbaa11dd

@damiencarol , the problem is https://github.com/DefectDojo/django-DefectDojo/commit/e1ef1348cea1e0e5fa4f96b6728eb1c3f1c9507d
If you use DefectDojo 2.13.1 with bleach 4.1.0, the links work fine.

I think we will revert it for this release


Replace more GenericVector and PointerVector by std::vector

I am still looking for a better code pattern as a replacement for PointerVector.


Rename puppet to interactive_parser

Based on #869

Might is be possible to not push the generated file?

I agree it might be better not to. I think I had a reason for including it, but I can't remember what it was.


Add ENOTSUP constant for riscv64 musl

Previously:

https://github.com/rust-lang/libc/pull/2595
https://github.com/rust-lang/libc/pull/1971
https://github.com/rust-lang/libc/pull/448

but not of these added the constant for riscv64 musl and rustc itself seems to use it nowadays.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Amanieu (or someone else) soon.
Please see the contribution instructions for more information.

@bors r+

:pushpin: Commit 1c5bc66f7b31529282d79f0ba843d95b238cedca has been approved by Amanieu

:hourglass: Testing commit 1c5bc66f7b31529282d79f0ba843d95b238cedca with merge 4f88b8d4ce64b4348fe71fb28bc167984433af91...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13
Approved by: Amanieu
Pushing 4f88b8d4ce64b4348fe71fb28bc167984433af91 to master...


Default project option and API support

It would be amazing to determine the default project globally so users don't have to pick a project.
And is there an API support in plans?

At this point we don't have this in plan to add API support.
You want every user to set up the default project for their account ?

I mean, I dont want my users to select a project everytime they want to see issues or stuff. I want to set the global project

At the moment we don't have in plan, I'll put it in the board so we can have a look at it.


Enhance readme documentation

Changes

Update readme file

@amoscatelli and @dearrudam could you review this, please?

@gastaldi could you review/merge this one?

Although it looks okay, I'd prefer to have this information in https://github.com/quarkiverse/quarkus-jnosql/blob/master/docs/modules/ROOT/pages/index.adoc instead (which is published in https://docs.quarkiverse.io/quarkus-jnosql/dev/index.html consequently).

https://docs.quarkiverse.io/quarkus-jnosql/dev/index.html

I will update this one as well. Thank you.

Although it looks okay, I'd prefer to have this information in https://github.com/quarkiverse/quarkus-jnosql/blob/master/docs/modules/ROOT/pages/index.adoc instead (which is published in https://docs.quarkiverse.io/quarkus-jnosql/dev/index.html consequently).

I updated both; I will include more documentation at this index as next step.

LGTM thank you all


Promise is not defined error in 0.19.0

Latest release is failing builds for me, seeing the error below in 0.19.0. This error is not present in 0.18.0.
ERROR in ./~/css-loader!./app/main.css
Module build failed: ReferenceError: Promise is not defined
    at LazyResult.async (/Users/chris/IdeaProjects/SW2.0/survivejs/node_modules/css-loader/node_modules/postcss/lib/lazy-result.js:152:31)
    at LazyResult.then (/Users/chris/IdeaProjects/SW2.0/survivejs/node_modules/css-loader/node_modules/postcss/lib/lazy-result.js:75:21)
    at processCss (/Users/chris/IdeaProjects/SW2.0/survivejs/node_modules/css-loader/lib/processCss.js:174:5)
    at Object.module.exports (/Users/chris/IdeaProjects/SW2.0/survivejs/node_modules/css-loader/lib/loader.js:22:2)
 @ ./app/main.css 4:14-75 13:2-17:4 14:20-81

Here's the webpack config:
var path = require('path');
var HtmlwebpackPlugin = require('html-webpack-plugin');
var webpack = require('webpack');

var ROOT_PATH = path.resolve(__dirname);

module.exports = {
  entry: path.resolve(ROOT_PATH, 'app'),
  output: {
    path: path.resolve(ROOT_PATH, 'build'),
    filename: 'bundle.js'
  },
  devtool: 'eval-source-map',
  devServer: {
    historyApiFallback: true,
    hot: true,
    inline: true,
    progress: true
  },
  module: {
    loaders: [
      {
        test: /\.css$/,
        loaders: ['style', 'css'],
        include: path.resolve(ROOT_PATH, 'app')
      }
    ]
  },
  plugins: [
    new webpack.HotModuleReplacementPlugin(),
    new HtmlwebpackPlugin({
      title: 'Kanban app'
    })
  ]
};

And package.json:
{
  "name": "survivejs",
  "version": "0.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "start": "webpack-dev-server",
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "css-loader": "^0.19.0",
    "html-webpack-plugin": "^1.6.1",
    "node-libs-browser": "^0.5.3",
    "style-loader": "^0.12.4",
    "webpack": "^1.12.2",
    "webpack-dev-server": "^1.11.0"
  }
}

The problem might be that they removed Promise polyfill in postcss 5.0. Perhaps we should push this upstream?

@bebraw PostCSS 5.0 does not support node 0.10, but you can polyfill the Promise API yourself:
https://github.com/jakearchibald/es6-promise

@ben-eb Alright. Thanks for the info.

Thanks, works after upgrading node to 4.1.1, didn't realise I was so far behind.

@chrismcband It might be good to resolve, or at least document this, regardless. Great to hear you got it to work, though.

Thanks, upgrading node to 4.1.1 did help. Note for OS X users: Homebrew does not have the updated formula, so it is pretty useless to run "brew upgrade". I had to download an official package from Node.js website.

Wow... I thought I was going crazy and it did not cross my mind that I had to update node, but that worked and I'm very happy now :)
ps. I updated through Homebrew just fine, just ran "brew update" first and then "brew upgrade node".

Same here, upgraded node through homebrew just fine. In my case it was still showing the old node version, but that was just a $PATH issue where I had an older version of node installed as part of a boxen installation.

Same here, upgraded node to latest version 4.1.1 and works as expected

How exactly do you pollyfill Promise to make this work? I tried this and it just produced a different error about an object not being a function.
// I added this to the top of my `webpack.config.js`
if (global.Promise == null) {
    global.Promise = require('es6-promise')
}

@AsaAyers https://github.com/jakearchibald/es6-promise#auto-polyfill

Thanks @ben-eb

You rock @gregkbarnes!  My app would still not deploy on Azure after upgrading to 4.1.2, your polyfill example fixed the issue.

@gregkbarnes that worked for me too. seems like that needs to be added. thanks for the help!

@gregkbarnes Thanks! It's worded.

saved my day...

I'm getting this on node v5.3.0...

@sokra are you happy to close this issue and mark as wontfix? What are your thoughts on support for older versions of Node?

If it is an older node version issue it could be solved setting a minimal engine version in the package.json.
For example, adding the following field to the package.json file would prevent installing this module on environments with node versions below to 0.12.0:
"engines": {
  "node": ">=0.12.0"
}

You are not supporting old versions but at least it is explicit which ones are.

@dreyescat Good idea. Would you like to make a PR?

I spent several hours trying to understand what was going on with weird error messages like:
Uncaught Error: Cannot find module "!!./../../node_modules/css-loader/index.js!./main.css"

Adding this in gulpfile.js helped:
// Support for Node 0.10
// See https://github.com/webpack/css-loader/issues/144
require('es6-promise').polyfill();

Ensuring this or the node version directly in css-loader would be great.

Closing given the related PR was merged.

Thank you, @ben-eb!


fix: update to eye v9.9.17

fix: update to eye v9.9.17

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

npm package (@latest dist-tag)
GitHub release
v12.8.11

Your semantic-release bot :package::rocket:


Dutch translation

Starting out a Dutch translation - thinking on having it translated as a start, and then organizing community to review and keep it up to date. Any thoughts?

first setup, work in progress: https://www.jgroenen.nl/community-translations-standard/nl/
repo: https://github.com/jgroenen/community-translations-standard

I created a pull request

I translated the criteria. Having some problems with the other files, since they are defining the GOVERNANCE of the standard as it was under the Foundation for Public Code.
Also, not fully clear if they need to describe the governance of the standard itself (upstream) and/or the governance of the Dutch translation.

I moved it to www.standaardvoorpubliekecode.nl (which redirects to https://codefor.nl/community-translations-standard/nl/)
I am now using a local Jekyll theme, to remove some of the Foundation for Public Code branding.

https://github.com/codefornl/community-translations-standard/releases/tag/0.8.0-nl-0.1.0


fix(charset_filter): Update is_extended_cjk to compatible with Unicode 15.

See also:
CJK Unified Ideographs Extension H
Other CJK ideographs in Unicode, not Unified

@lotem Request for review.


When add one logger locally, how to make it valid by docker-compose command ?

Please make sure you are familiar with the SIP process documented
(here)[https://github.com/apache/superset/issues/5602]. The SIP number should be the next number after the latest SIP listed here.
[SIP-<number>] Proposal for
Motivation
Description of the problem to be solved.
Proposed Change
Describe how the feature will be implemented, or the problem will be solved. If possible, include mocks, screenshots, or screencasts (even if from different tools).
New or Changed Public Interfaces
Describe any new additions to the model, views or REST endpoints. Describe any changes to existing visualizations, dashboards and React components. Describe changes that affect the Superset CLI and how Superset is deployed.
New dependencies
Describe any npm/PyPI packages that are required. Are they actively maintained? What are their licenses?
Migration Plan and Compatibility
Describe any database migrations that are necessary, or updates to stored URLs.
Rejected Alternatives
Describe alternative approaches that were considered and rejected.

Hi there @zjpopo. It doesn't seem like you added any details about what you're trying to do, and instead included a blank improvement proposal. I'll close this for now, but if you're able to explain a bit more of what you're trying to accomplish, and what's taking place when you try, we can take this to a Q&A Discussion.


⚠ Secret Website 3 has degraded performance

In a45f9d7, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 2609 ms

Resolved: Secret Website 3 performance has improved in 4b10456.


Preview strikethrough

Strikethrough uses two tildes. Scratch this.
sublime build 3126
MLP v2.4.5

Hum... Quickly looked into it and unfortunately, Sublime Text doesn't support <strike> tags.


Refactor current-content

Description
Fixes #...
Notes (out of scope, known isues, hints for reviewing code, ...)  (optional)
...
Test cases

[ ] Case 1:

Given I am the usual user
When I go to [this page](branch link)
And I click on ...
Then I see ...
And

[ ] Case 2:

Given I am the usual user
When ...

[auto-generated message] E2E test report on: https://algorea-static.s3.eu-central-1.amazonaws.com/branch/refactor-current-content/playwright-report/index.html

[auto-generated message] E2E test report on: https://algorea-static.s3.eu-central-1.amazonaws.com/branch/refactor-current-content/playwright-report/index.html

[auto-generated message] E2E test report on: https://algorea-static.s3.eu-central-1.amazonaws.com/branch/refactor-current-content/playwright-report/index.html


#2 Block: Adds base block styles.

Summary
Adds block styles for the various view types.
Relevant Technical Choices

Update webpack config to add postCSS for the web stories list block scripts only.
Updates to use two chunk groups for editor and front-end styles.
Adds postCSS to work with SCSS like syntax and uses following plugins to use some of the SASS like features.

postcss-advanced-variables
postcss-preset-env
postcss-nested
postcss-scss

To-do

Resolve stylelint issues, make stylelint understand scss syntax in .css files.

Maybe we can update the lint task to use --syntax 'scss' for these style files.

Fixed lint errors, remove scss syntax.

Fixed lint errors, remove scss syntax.

Reverted package-lock changes, waiting for the checks to complete.

Reverted package-lock changes, waiting for the checks to complete.

One small nitpic about moving icon but otherwise we are looking good.

One small nitpic about moving icon but otherwise we are looking good.

I've updated the PR, moved the svg to icons directory,

I've updated the PR, moved the svg to icons directory,


[#128841821] Filter "next agreement" behaviour by status

A bolt-on to story https://www.pivotaltracker.com/story/show/128841821
This PR causes the "next agreement" behaviour of the views surrounding countersigning to obey any current status filter applied to the list view that the agreement was accessed from.
(This is exactly the sort of behaviour the functional tests would be ideal to test, but I don't know if that would be worth my time...)
This necessitated a redesign of the next_agreement view - as previously designed, retrieving an agreement (A)'s "next" agreement when filtered by a status other than A's current status would fail because the view would fail to find A in the status-filtered API listing it requests (which it needs to do to be able to determine which one is "next"). So instead we now fetch an unfiltered listing (annotated with statuses) and perform any "filtering" ourselves.

:+1: let's do this as-is and add the individual approved and countersigned options if a user need arises.


fix: add phase reason cancel if schedule end behavior is cancel

Pull Request Test Coverage Report for Build<PHONE_NUMBER>1
Details

0 of 4 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 9.471%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

billing/subscription/service.go
0
4
0.0%

Totals

Change from base Build<PHONE_NUMBER>5:
0.0%

Covered Lines:
10263

Relevant Lines:
108363

💛  - Coveralls


Feature: Auto-Tilt on Zoom

Add optional Auto-Tilt feature to keep the horizon in view at top of screen while zooming in/out. This provides better perspective than zooming straight down with a top-down perspective. Should apply something similar to the "tilt3D" function to adjust camera position and pitch while centered on zoom point. Involves updating the ScreenSpaceCameraController.js file

Actually Google Maps (Satellite view) does this now, they have a nice system where it remembers what pitch your camera was the last time you were zoomed in at that altitude, and it auto-tilts the camera back to that angle when zooming in and out, zooming out always goes to top-down view, unlike Cesium which zooms straight out to awkward angle. I would do similar to Google Maps but make it configurable


matching(X, y) should print a warning if y is a table and y only has one column

See https://github.com/alan-turing-institute/MLJ.jl/issues/937 for motivation.

Codecov Report

Merging #460 (943c038) into dev (9ea2c81) will decrease coverage by 0.37%.
The diff coverage is 0.00%.

:exclamation: Current head 943c038 differs from pull request most recent head fcd1975. Consider uploading reports for the commit fcd1975 to get more accurate results

@@            Coverage Diff             @@
##              dev     #460      +/-   ##
==========================================
- Coverage   75.17%   74.79%   -0.38%
==========================================
  Files          12       12
  Lines        1019      988      -31
==========================================
- Hits          766      739      -27
+ Misses        253      249       -4

Impacted Files
Coverage Δ

src/model_search.jl
70.19% <0.00%> (-3.81%)
:arrow_down:

src/metadata.jl
77.64% <0.00%> (-2.15%)
:arrow_down:

src/loading.jl
61.90% <0.00%> (-0.45%)
:arrow_down:

src/MLJModels.jl
100.00% <0.00%> (ø)

src/registry/src/Registry.jl
0.00% <0.00%> (ø)

src/registry/src/check_registry.jl
0.00% <0.00%> (ø)

src/builtins/Transformers.jl
96.40% <0.00%> (+0.15%)
:arrow_up:

src/builtins/ThresholdPredictors.jl
92.04% <0.00%> (+0.55%)
:arrow_up:

src/utilities.jl
16.12% <0.00%> (+0.97%)
: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 9ea2c81...fcd1975. Read the comment docs.

cc: @Carlos-Trebbau


wrong error message in xts --version?

@pgundlach,
I have just downloaded XTS for Windows and I get:
> xts --version
Usage: [parameter] command
-h, --help                   Show this help
-c, --config=NAME            Read the config file with the given NAME.
                             Default: 'publisher.cfg'
    --jobname=NAME           The name of the resulting PDF file (without
                             extension), default is 'publisher'
    --systemfonts            Use system fonts
    --verbose                Put more debugging information into the protocol
                             file
    --dummy                  Don't read a data file, use '<data />' as input
    --dumpoutput=FILENAME    Complete XML dump of generated PDF file

Commands
      list-fonts             List installed fonts
      clean                  Remove auxiliary and protocol files
      new                    Create simple layout and data file to start.
                             Provide optional directory.
      run                    Load layout and data files and create PDF
                             (default)
      version                Print version information
{"level":"error","ts":1681729417.645211,"caller":"xts/main.go:330","msg":"Unknown option version","stacktrace":"main.main\n\t/Users/patrick/work/software/bag/xts/xts/main.go:330\nruntime.main\n\t/opt/homebrew/Cellar/go/1.20.1/libexec/src/runtime/proc.go:250"}

I think the last line might be an error.
Just in case it helps. Many thanks for your help and your excellent work.

Actually this looks correct (runxts version instead of xts --version), but I should a) not log in JSON anymore at this point and for the most common commands/options (help and version) be more tolerant.

Oh, I see, I've mixed them up.... I think I stick with the command version (xts version) as it exits after printing the version information.

BTW: if you are brave enough to try XTS and have a priority wish... just let me know. Can't promise anything since this is a side project, but I'd be happy to get input.


Abstract usage of _beginthreadex in PlatformAgnostic class

PlatformAgnostic::Threads::Utility::BeginThread exports the
functionality we use consistently in Chakra. In particular the
"security" and "thread address" parameters are missing. See MSDN for
details.
The Windows implementation just calls _beginthreadex. On Linux we use
PAL's CreateThread, but in the future we would like to use pthread
directly. Future patches will enable the functionality on !Windows,
for now it remains disabled.

Thanks @xanlpz! This is a very good start. Couple points of feedback:

Since it's a static function in a class that's already within a namespace, I prefer just making it a regular function- PlatformAgnostic::Threading::Create is my preferred name
For the init_flag parameter, I prefer we use an enum instead of an int- so that we have a platform agnostic type for the flags.
Currently, you return uintptr_t for the return value- I think this is fine, I was just wondering if there is ever the case where a thread "handle" is not uintptr_t, but say a struct? Which is a roundabout way of asking, should we typedef the return value?
Minor stylistic point- generally, we prefer to be explicit about our types- so we prefer unsigned int to just regular unsigned
I suspect that the Windows builds are failing because ChakraRuntimePlatformAgnostic is not defined in our MSBuild props files. I think you're better off just adding a project reference (scroll towards the bottom of that file and see how Chakra.Common.Codex.vcxproj is defined). The bigger problem is that PlatformAgnostic today has a dependency on Runtime.Base 😞 - so I think for now, just let ch continue to use _beginthreadex since that code is already in #ifdef _WIN32. That particular behavior of ch is not crucial.

(sorry for the delay, was on holidays!)
Thanks for the comments! New patch up. In detail:
1): done
2): done
3): to be honest I'm not entirely sure. I guess this also depends on what we want to do on Linux at some point? Maybe a typedef is safer for the future, but maybe we can just change it when we actually need to (I'm assuming it's fine to completely change these APIs at any moment)
4): done
5): ouch, yeah. So I reverted the code in all three binaries, because they were all giving similar problems (although rl and the tests are not even built on Linux atm). So just a couple of files changed in the project in the end.

1 )

Currently, you return uintptr_t for the return value- I think this is fine, I was just wondering if there is ever the case where a thread "handle" is not uintptr_t, but say a struct? Which is a roundabout way of asking, should we typedef the return value?

Agree with @digitalinfinity and we might use a typedef here
i.e. How about ThreadHandle naming?
We could have other minor issues / discussions on this though, but
this is a new start on Thread interface and we may improve it over time.
So; The rest LGTM. @xanlpz Thanks for the effort!

Alright, so introduced a typedef for the return type (it's basically pointless atm but I guess that's to be expected) and cleaned up some class namespacing inside the methods while I was at it.

@xanlpz LGTM, could you please rebase ?

@xanlpz any progress on this? [squash + rebase]

OK, I think it should be up to date now (somehow previous rebases were missing some commits from master)

@dotnet-bot test this please.

@dotnet-bot test this please.

@xanlpz Thanks for the effort!


Add unit test for SHAHashAnalyzer

Addresses #101.
SHAHashAnalyzer now matches SHA- 1, 224, 256, 384, and 512 hashes. Also added a unit test.
Let me know if there're any necessary changes! 😄

Pull Request Test Coverage Report for Build 125

33 of 34 (97.06%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.02%) to 61.111%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pastepwn/analyzers/tests/shahashanalyzer_test.py
32
33
96.97%

Totals

Change from base Build 124:
1.02%

Covered Lines:
847

Relevant Lines:
1386

💛  - Coveralls


⚠ ClamAV has degraded performance

In ea58221, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 124 ms

Resolved: ClamAV performance has improved in d1bc1c1 after 15 minutes.


[webview_flutter_platform_interface] - Added limitsNavigationsToAppBoundDomains to WebSettings

Added limitsNavigationsToAppBoundDomains that is an optional setting for iOS 14+.
PR is the first PR replacement of #4339
List which issues are fixed by this PR. You must list at least one issue.
(flutter/issues/89530)
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the relevant style guides and ran the auto-formatter. (Note that unlike the flutter/flutter repo, the flutter/plugins repo does use dart format.)
[x] I signed the CLA.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Sorry for the churn, but based on your latest update in the main PR I don't think we have a clear picture of what the implementation should actually look like after all, so I'm going to close this for now; I think there's a good chance we'll end up wanting something different at this layer by the time that discussion resolves.
Once we have an end-to-end design that works for the creation-time-only version, we can re-split a platform interface PR.


Reduce sleep time to something bearable

Hello, great script.
Really saved me a lot of trouble after a day of frustration trying to install GVM.
I have a suggestion, though.
You could reduce the sleep 300 to a minute or half a minute. No need to wait 5 minutes between downloads.

Hey, nice to hear that the script did help you.
Well I think, it should be basically ok to reduce the wait time to one or two minutes.
Nevertheless, some people - including me - experienced issues with their downloads getting blocked when requesting the feeds "too fast". We came up with this high value, as the install process takes quite a long time anyway (mainly because feed downloads are limited to risible ratios), but at least prevents IP blocking.


Won't let me install requirements

I get this error when trying to install everything. It worked once but once i tried to remove an error, it stopped working completely.
Collecting cltl.brain
Using cached cltl.brain-0.0.dev6.tar.gz (253 kB)
Preparing metadata (setup.py) ... done
Using cached cltl.brain-0.0.dev5.tar.gz (255 kB)
Preparing metadata (setup.py) ... done
Using cached cltl.brain-0.0.dev4.tar.gz (255 kB)
Preparing metadata (setup.py) ... done
ERROR: Cannot install -r requirements.txt (line 1) because these package versions have conflicting dependencies.
The conflict is caused by:
cltl-brain 0.0.dev7 depends on iribaker>=0.2
cltl-brain 0.0.dev6 depends on iribaker>=0.2
cltl-brain 0.0.dev5 depends on iribaker>=0.2
cltl-brain 0.0.dev4 depends on iribaker>=0.2
To fix this you could try to:

loosen the range of package versions you've specified
remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies

You only need the latest version dev7. Can you try with changing requirements.txt to install dev7?

I have tried changing the requirements but I'm not sure what you mean by that... I've also tried installing it with pip3 but it won't work, it keeps runnin into errors.

ERROR: Could not find a version that satisfies the requirement iribaker>=0.2 (from cltl-brain) (from versions: 0.1.1.macosx-10.11-x86_64, 0.1.2.macosx-10.11-x86_64, 0.1.2, 0.1.3, 0.2)
ERROR: No matching distribution found for iribaker>=0.2

When you reinstall are you doing this in a clean environment? Can you check with pip list to see what versions of cltl brain are installes?
Piek
Verstuurd vanaf mijn iPhone
Op 11 dec. 2021 om 13:03 heeft Pauline-cloud @.***> het volgende geschreven:

ERROR: Could not find a version that satisfies the requirement iribaker>=0.2 (from cltl-brain) (from versions: 0.1.1.macosx-10.11-x86_64, 0.1.2.macosx-10.11-x86_64, 0.1.2, 0.1.3, 0.2)
ERROR: No matching distribution found for iribaker>=0.2
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/leolani/cltl-chatbots/issues/8#issuecomment-991618309, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAUDKLHZK7ZPUATJT5TGZH3UQM4ZVANCNFSM5JZVRJNQ.

It seems as if you install a version over another version. If cltl-brain is alteady installed you should use update.
Piek
Verstuurd vanaf mijn iPhone
Op 11 dec. 2021 om 13:05 heeft Vossen, P.T.J.M. @.***> het volgende geschreven:
 When you reinstall are you doing this in a clean environment? Can you check with pip list to see what versions of cltl brain are installes?
Piek
Verstuurd vanaf mijn iPhone
Op 11 dec. 2021 om 13:03 heeft Pauline-cloud @.***> het volgende geschreven:

ERROR: Could not find a version that satisfies the requirement iribaker>=0.2 (from cltl-brain) (from versions: 0.1.1.macosx-10.11-x86_64, 0.1.2.macosx-10.11-x86_64, 0.1.2, 0.1.3, 0.2)
ERROR: No matching distribution found for iribaker>=0.2
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/leolani/cltl-chatbots/issues/8#issuecomment-991618309, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAUDKLHZK7ZPUATJT5TGZH3UQM4ZVANCNFSM5JZVRJNQ.

Yeah, i've tried makin new environments by doing venv2 and venv3 but the same issues pop up

pauline@MacBook-Pro-van-Pauline cltl-chatbots % pip list
Package              Version

anyio                3.4.0
appnope              0.1.2
argon2-cffi          21.3.0
argon2-cffi-bindings 21.2.0
attrs                21.2.0
Babel                2.9.1
backcall             0.2.0
bleach               4.1.0
certifi              2021.10.8
cffi                 1.15.0
charset-normalizer   2.0.9
debugpy              1.5.1
decorator            5.1.0
defusedxml           0.7.1
entrypoints          0.3
idna                 3.3
ipykernel            6.6.0
ipython              7.30.1
ipython-genutils     0.2.0
jedi                 0.18.1
Jinja2               3.0.3
json5                0.9.6
jsonschema           4.2.1
jupyter-client       7.1.0
jupyter-core         4.9.1
jupyter-server       1.13.1
jupyterlab           3.2.5
jupyterlab-pygments  0.1.2
jupyterlab-server    2.8.2
MarkupSafe           2.0.1
matplotlib-inline    0.1.3
mistune              0.8.4
nbclassic            0.3.4
nbclient             0.5.9
nbconvert            6.3.0
nbformat             5.1.3
nest-asyncio         1.5.4
notebook             6.4.6
packaging            21.3
pandocfilters        1.5.0
parso                0.8.3
pexpect              4.8.0
pickleshare          0.7.5
pip                  21.3.1
prometheus-client    0.12.0
prompt-toolkit       3.0.24
ptyprocess           0.7.0
pycparser            2.21
Pygments             2.10.0
pyparsing            3.0.6
pyrsistent           0.18.0
python-dateutil      2.8.2
pytz                 2021.3
pyzmq                22.3.0
requests             2.26.0
Send2Trash           1.8.0
setuptools           59.0.1
six                  1.16.0
sniffio              1.2.0
terminado            0.12.1
testpath             0.5.0
tornado              6.1
traitlets            5.1.1
urllib3              1.26.7
wcwidth              0.2.5
webencodings         0.5.1
websocket-client     1.2.3

What happens if you clone cltl-knowledge representation as a separate project and follow the readme instructions of the brain, so not cltl-chatbots.
Piek
Verstuurd vanaf mijn iPhone
Op 11 dec. 2021 om 13:15 heeft Pauline-cloud @.***> het volgende geschreven:

Yeah, i've tried makin new environments by doing venv2 and venv3 but the same issues pop up
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/leolani/cltl-chatbots/issues/8#issuecomment-991622139, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAUDKLCIECSD2MGYS5KGHR3UQM6G3ANCNFSM5JZVRJNQ.

Is this from within venv?
Verstuurd vanaf mijn iPhone
Op 11 dec. 2021 om 13:16 heeft Pauline-cloud @.***> het volgende geschreven:

@.*** cltl-chatbots % pip list
Package Version

anyio 3.4.0
appnope 0.1.2
argon2-cffi 21.3.0
argon2-cffi-bindings 21.2.0
attrs 21.2.0
Babel 2.9.1
backcall 0.2.0
bleach 4.1.0
certifi 2021.10.8
cffi 1.15.0
charset-normalizer 2.0.9
debugpy 1.5.1
decorator 5.1.0
defusedxml 0.7.1
entrypoints 0.3
idna 3.3
ipykernel 6.6.0
ipython 7.30.1
ipython-genutils 0.2.0
jedi 0.18.1
Jinja2 3.0.3
json5 0.9.6
jsonschema 4.2.1
jupyter-client 7.1.0
jupyter-core 4.9.1
jupyter-server 1.13.1
jupyterlab 3.2.5
jupyterlab-pygments 0.1.2
jupyterlab-server 2.8.2
MarkupSafe 2.0.1
matplotlib-inline 0.1.3
mistune 0.8.4
nbclassic 0.3.4
nbclient 0.5.9
nbconvert 6.3.0
nbformat 5.1.3
nest-asyncio 1.5.4
notebook 6.4.6
packaging 21.3
pandocfilters 1.5.0
parso 0.8.3
pexpect 4.8.0
pickleshare 0.7.5
pip 21.3.1
prometheus-client 0.12.0
prompt-toolkit 3.0.24
ptyprocess 0.7.0
pycparser 2.21
Pygments 2.10.0
pyparsing 3.0.6
pyrsistent 0.18.0
python-dateutil 2.8.2
pytz 2021.3
pyzmq 22.3.0
requests 2.26.0
Send2Trash 1.8.0
setuptools 59.0.1
six 1.16.0
sniffio 1.2.0
terminado 0.12.1
testpath 0.5.0
tornado 6.1
traitlets 5.1.1
urllib3 1.26.7
wcwidth 0.2.5
webencodings 0.5.1
websocket-client 1.2.3
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/leolani/cltl-chatbots/issues/8#issuecomment-991622301, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAUDKLBSAXG62VFDXOUTNNLUQM6IZANCNFSM5JZVRJNQ.

Yes it is from within venv
i'll try doing the cltl-knowledge

i've installed everything, made a Graphdb rep with the name sandbox, and tried pip3 install cltl.brain but then this happens
ERROR: Cannot install cltl-brain==0.0.dev4, cltl-brain==0.0.dev5, cltl-brain==0.0.dev6 and cltl-brain==0.0.dev7 because these package versions have conflicting dependencies.
The conflict is caused by:
cltl-brain 0.0.dev7 depends on iribaker>=0.2
cltl-brain 0.0.dev6 depends on iribaker>=0.2
cltl-brain 0.0.dev5 depends on iribaker>=0.2
cltl-brain 0.0.dev4 depends on iribaker>=0.2
To fix this you could try to:

loosen the range of package versions you've specified
remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies
(venv) pauline@MacBook-Pro-van-Pauline cltl-knowledgerepresentation %

This i got from Selene who built cltl-brain:
“ And when installing requirements, I out iribaker on top of the requirements.txt file and it worked”
Can you try that?
Piek
Verstuurd vanaf mijn iPhone
Op 11 dec. 2021 om 13:50 heeft Pauline-cloud @.***> het volgende geschreven:

i've installed everything, made a Graphdb rep with the name sandbox, and tried pip3 install cltl.brain but then this happens
ERROR: Cannot install cltl-brain==0.0.dev4, cltl-brain==0.0.dev5, cltl-brain==0.0.dev6 and cltl-brain==0.0.dev7 because these package versions have conflicting dependencies.
The conflict is caused by:
cltl-brain 0.0.dev7 depends on iribaker>=0.2
cltl-brain 0.0.dev6 depends on iribaker>=0.2
cltl-brain 0.0.dev5 depends on iribaker>=0.2
cltl-brain 0.0.dev4 depends on iribaker>=0.2
To fix this you could try to:

loosen the range of package versions you've specified
remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies
(venv) @.*** cltl-knowledgerepresentation %
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/leolani/cltl-chatbots/issues/8#issuecomment-991632592, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAUDKLATOF5Q6U7H65Z5NUDUQNCJTANCNFSM5JZVRJNQ.

What do you mean by 'out'? The requirements file only contains a dot.

When outing iribaker it downloads and successfully installs, but i am not sure what the next step should be..

What are you installing precisely? Cltl-chatbots has detailed instructions what to do. Are you following these?
Piek
On 11 Dec 2021, at 15:30, Pauline-cloud<EMAIL_ADDRESS>wrote:
When outing iribaker it downloads and successfully installs, but i am not sure what the next step should be..
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/leolani/cltl-chatbots/issues/8#issuecomment-991663627, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAUDKLHEAMQ7VKLSZ6RD6YTUQNN7LANCNFSM5JZVRJNQ.

I've followed the instructions for the cltl-knowledgerepresentation through to the end, with iribaker in the requirements.txt and that successfully installed (this page https://github.com/leolani/cltl-knowledgerepresentation/blob/main/README.md with the instructions), but then i'm not sure what to do next. I also tried to add iribaker at the top of the requirements.txt from clil-chatbots but then i get this error:
ERROR: Cannot install -r requirements.txt (line 2) and iribaker because these package versions have conflicting dependencies.
The conflict is caused by:
The user requested iribaker
cltl-brain 0.0.dev7 depends on iribaker>=0.2
To fix this you could try to:

loosen the range of package versions you've specified
remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies
(venv) pauline@MacBook-Pro-van-Pauline cltl-chatbots %

I assume they need a newer version of the iribaker, and i've tried installing iribaker seperately, but installing iribaker 0.2 is not functioning it says that there is no matching distribution

How do you add it to the requirements? With an explicit version constraint or just like that?
Piek
On 11 Dec 2021, at 15:45, Pauline-cloud<EMAIL_ADDRESS>wrote:
I've followed the instructions for the cltl-knowledgerepresentation through to the end, with iribaker in the requirements.txt and that successfully installed (this page https://github.com/leolani/cltl-knowledgerepresentation/blob/main/README.md with the instructions), but then i'm not sure what to do next. I also tried to add iribaker at the top of the requirements.txt from clil-chatbots but then i get this error:
ERROR: Cannot install -r requirements.txt (line 2) and iribaker because these package versions have conflicting dependencies.
The conflict is caused by:
The user requested iribaker
cltl-brain 0.0.dev7 depends on iribaker>=0.2
To fix this you could try to:

loosen the range of package versions you've specified
remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies
(venv) @.*** cltl-chatbots %
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/leolani/cltl-chatbots/issues/8#issuecomment-991668657, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAUDKLFNG65PPFUF4O7N2YDUQNPZTANCNFSM5JZVRJNQ.

I add it like
iribaker
because if i put it like iribaker==0.2, iribaker2, iribaker=0.2 or any other combination it simply states the same error
ERROR: No matching distribution found for iribaker==0.2

And leaving it out the requirements does not help either?
On 11 Dec 2021, at 15:56, Pauline-cloud<EMAIL_ADDRESS>wrote:
I add it like
iribaker
because if i put it like iribaker==0.2, iribaker2, iribaker=0.2 or any other combination it simply states the same error
ERROR: No matching distribution found for iribaker==0.2
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/leolani/cltl-chatbots/issues/8#issuecomment-991672008, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAUDKLBE4WYZBORCB36SIZLUQNRALANCNFSM5JZVRJNQ.

no because then we run back to this error again:
ERROR: Could not find a version that satisfies the requirement iribaker>=0.2 (from cltl-brain) (from versions: 0.1.1.macosx-10.11-x86_64, 0.1.2.macosx-10.11-x86_64, 0.1.2, 0.1.3, 0.2)
ERROR: No matching distribution found for iribaker>=0.2

Can we zoom and you share your screen?
Piek Vossen is inviting you to a scheduled Zoom meeting.
Topic: Combots Lecture
Time: This is a recurring meeting Meet anytime
Join Zoom Meeting
https://vu-live.zoom.us/j/99158476452?pwd=VGVTLy9SRGtEY2FZTDh0L25ZcUF6QT09
Meeting ID: 991 5847 6452
Passcode: 653080
On 11 Dec 2021, at 15:59, Pauline-cloud<EMAIL_ADDRESS>wrote:
no because then we run back to this error again:
ERROR: Could not find a version that satisfies the requirement iribaker>=0.2 (from cltl-brain) (from versions: 0.1.1.macosx-10.11-x86_64, 0.1.2.macosx-10.11-x86_64, 0.1.2, 0.1.3, 0.2)
ERROR: No matching distribution found for iribaker>=0.2
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/leolani/cltl-chatbots/issues/8#issuecomment-991673164, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAUDKLCBCL4ULU5EXGIIFSDUQNRN5ANCNFSM5JZVRJNQ.

(venv2) pauline@MacBook-Pro-van-Pauline cltl-chatbots % pip install iribaker==0.2
Collecting iribaker==0.2
Using cached iribaker-0.2.tar.gz (2.3 kB)
Preparing metadata (setup.py) ... error
ERROR: Command errored out with exit status 1:
command: /Users/pauline/cltl-chatbots/venv2/bin/python3.9 -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/kb/ft284ty931v48ykk5_gk52p80000gn/T/pip-install-watvnoq8/iribaker_538f81b97a15456ab2440cb24354c731/setup.py'"'"'; file='"'"'/private/var/folders/kb/ft284ty931v48ykk5_gk52p80000gn/T/pip-install-watvnoq8/iribaker_538f81b97a15456ab2440cb24354c731/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(file) if os.path.exists(file) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' egg_info --egg-base /private/var/folders/kb/ft284ty931v48ykk5_gk52p80000gn/T/pip-pip-egg-info-28xya9nf
cwd: /private/var/folders/kb/ft284ty931v48ykk5_gk52p80000gn/T/pip-install-watvnoq8/iribaker_538f81b97a15456ab2440cb24354c731/
Complete output (26 lines):
running egg_info
creating /private/var/folders/kb/ft284ty931v48ykk5_gk52p80000gn/T/pip-pip-egg-info-28xya9nf/iribaker.egg-info
writing /private/var/folders/kb/ft284ty931v48ykk5_gk52p80000gn/T/pip-pip-egg-info-28xya9nf/iribaker.egg-info/PKG-INFO
Traceback (most recent call last):
File "", line 1, in
File "/private/var/folders/kb/ft284ty931v48ykk5_gk52p80000gn/T/pip-install-watvnoq8/iribaker_538f81b97a15456ab2440cb24354c731/setup.py", line 3, in
setup(name='iribaker',
File "/Users/pauline/cltl-chatbots/venv2/lib/python3.9/site-packages/setuptools/init.py", line 159, in setup
return distutils.core.setup(**attrs)
File<EMAIL_ADDRESS>line 148, in setup
dist.run_commands()
File<EMAIL_ADDRESS>line 966, in run_commands
self.run_command(cmd)
File<EMAIL_ADDRESS>line 985, in run_command
cmd_obj.run()
File "/Users/pauline/cltl-chatbots/venv2/lib/python3.9/site-packages/setuptools/command/egg_info.py", line 292, in run
writer(self, ep.name, os.path.join(self.egg_info, ep.name))
File "/Users/pauline/cltl-chatbots/venv2/lib/python3.9/site-packages/setuptools/command/egg_info.py", line 656, in write_pkg_info
metadata.write_pkg_info(cmd.egg_info)
File<EMAIL_ADDRESS>line 1117, in write_pkg_info
self.write_pkg_file(pkg_info)
File "/Users/pauline/cltl-chatbots/venv2/lib/python3.9/site-packages/setuptools/dist.py", line 167, in write_pkg_file
write_field('Summary', single_line(self.get_description()))
File "/Users/pauline/cltl-chatbots/venv2/lib/python3.9/site-packages/setuptools/dist.py", line 151, in single_line
raise ValueError('Newlines are not allowed')
ValueError: Newlines are not allowed
WARNING: Discarding https://files.pythonhosted.org/packages/df/50/e5137ce88cb647803e3ad7bb4ee5fb125e29c4277a180319e5949d2ba401/iribaker-0.2.tar.gz#sha256=18ccd1211124fc239f3cb6ed96006417357920f36054d917304d930cc117d8e8 (from https://pypi.org/simple/iribaker/). Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.
ERROR: Could not find a version that satisfies the requirement iribaker==0.2 (from versions: 0.1.1.macosx-10.11-x86_64, 0.1.2.macosx-10.11-x86_64, 0.1.2, 0.1.3, 0.2)
ERROR: No matching distribution found for iribaker==0.2

Hoi Pauline,
Kun je dit in de requirements.txt proberen?
cltl.brain==0.0.dev7
cltl.reply-generation==0.0.dev8
cltl.triple-extraction==0.0.dev5
emissor==0.0.dev5
jsonpickle==2.0.0
opencv-python==<IP_ADDRESS>
python_on_whales==0.31.0
pillow==8.4.0
spacy==3.2.0
tqdm==4.62.3
ipykernel==6.5.0
matplotlib==3.4.3
matplotlib-inline==0.1.3
seaborn==0.11.2
torch==1.10.0
torchaudio==0.10.0
torchvision==0.11.1
Verstuurd vanaf mijn iPhone
Op 11 dec. 2021 om 16:24 heeft Pauline-cloud @.***> het volgende geschreven:

(venv2) @.*** cltl-chatbots % pip install iribaker==0.2
Collecting iribaker==0.2
Using cached iribaker-0.2.tar.gz (2.3 kB)
Preparing metadata (setup.py) ... error
ERROR: Command errored out with exit status 1:
command: /Users/pauline/cltl-chatbots/venv2/bin/python3.9 -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/kb/ft284ty931v48ykk5_gk52p80000gn/T/pip-install-watvnoq8/iribaker_538f81b97a15456ab2440cb24354c731/setup.py'"'"'; file='"'"'/private/var/folders/kb/ft284ty931v48ykk5_gk52p80000gn/T/pip-install-watvnoq8/iribaker_538f81b97a15456ab2440cb24354c731/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(file) if os.path.exists(file) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' egg_info --egg-base /private/var/folders/kb/ft284ty931v48ykk5_gk52p80000gn/T/pip-pip-egg-info-28xya9nf
cwd: /private/var/folders/kb/ft284ty931v48ykk5_gk52p80000gn/T/pip-install-watvnoq8/iribaker_538f81b97a15456ab2440cb24354c731/
Complete output (26 lines):
running egg_info
creating /private/var/folders/kb/ft284ty931v48ykk5_gk52p80000gn/T/pip-pip-egg-info-28xya9nf/iribaker.egg-info
writing /private/var/folders/kb/ft284ty931v48ykk5_gk52p80000gn/T/pip-pip-egg-info-28xya9nf/iribaker.egg-info/PKG-INFO
Traceback (most recent call last):
File "", line 1, in
File "/private/var/folders/kb/ft284ty931v48ykk5_gk52p80000gn/T/pip-install-watvnoq8/iribaker_538f81b97a15456ab2440cb24354c731/setup.py", line 3, in
setup(name='iribaker',
File "/Users/pauline/cltl-chatbots/venv2/lib/python3.9/site-packages/setuptools/init.py", line 159, in setup
return distutils.core.setup(attrs)
File @./3.9.9/Frameworks/Python.framework/Versions/3.9/lib/python3.9/distutils/core.py", line 148, in setup
dist.run_commands()
File @./3.9.9/Frameworks/Python.framework/Versions/3.9/lib/python3.9/distutils/dist.py", line 966, in run_commands
self.run_command(cmd)
File @./3.9.9/Frameworks/Python.framework/Versions/3.9/lib/python3.9/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/Users/pauline/cltl-chatbots/venv2/lib/python3.9/site-packages/setuptools/command/egg_info.py", line 292, in run
writer(self, ep.name, os.path.join(self.egg_info, ep.name))
File "/Users/pauline/cltl-chatbots/venv2/lib/python3.9/site-packages/setuptools/command/egg_info.py", line 656, in write_pkg_info
metadata.write_pkg_info(cmd.egg_info)
File @.**/3.9.9/Frameworks/Python.framework/Versions/3.9/lib/python3.9/distutils/dist.py", line 1117, in write_pkg_info
self.write_pkg_file(pkg_info)
File "/Users/pauline/cltl-chatbots/venv2/lib/python3.9/site-packages/setuptools/dist.py", line 167, in write_pkg_file
write_field('Summary', single_line(self.get_description()))
File "/Users/pauline/cltl-chatbots/venv2/lib/python3.9/site-packages/setuptools/dist.py", line 151, in single_line
raise ValueError('Newlines are not allowed')
ValueError: Newlines are not allowed
WARNING: Discarding https://files.pythonhosted.org/packages/df/50/e5137ce88cb647803e3ad7bb4ee5fb125e29c4277a180319e5949d2ba401/iribaker-0.2.tar.gz#sha256=18ccd1211124fc239f3cb6ed96006417357920f36054d917304d930cc117d8e8 (from https://pypi.org/simple/iribaker/). Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.
ERROR: Could not find a version that satisfies the requirement iribaker==0.2 (from versions: 0.1.1.macosx-10.11-x86_64, 0.1.2.macosx-10.11-x86_64, 0.1.2, 0.1.3, 0.2)
ERROR: No matching distribution found for iribaker==0.2
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/leolani/cltl-chatbots/issues/8#issuecomment-991681575, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAUDKLEYS4YVFWFZHNIH2S3UQNUMDANCNFSM5JZVRJNQ.

Helaas hetzelfde probleem weer.
ERROR: Could not find a version that satisfies the requirement iribaker>=0.2 (from cltl-brain) (from versions: 0.1.1.macosx-10.11-x86_64, 0.1.2.macosx-10.11-x86_64, 0.1.2, 0.1.3, 0.2)
ERROR: No matching distribution found for iribaker>=0.2

Thomas found this:
I think this is this issue:
https://github.com/pypa/setuptools/issues/2893
Try to up- or downgrade setuptools (I think 58.x and 59.5.0) works
Piek
Verstuurd vanaf mijn iPhone
Op 11 dec. 2021 om 16:47 heeft Pauline-cloud @.***> het volgende geschreven:

Helaas hetzelfde probleem weer.
ERROR: Could not find a version that satisfies the requirement iribaker>=0.2 (from cltl-brain) (from versions: 0.1.1.macosx-10.11-x86_64, 0.1.2.macosx-10.11-x86_64, 0.1.2, 0.1.3, 0.2)
ERROR: No matching distribution found for iribaker>=0.2
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/leolani/cltl-chatbots/issues/8#issuecomment-991689614, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAUDKLHYJ5UGXHGKBTHBEH3UQNXCJANCNFSM5JZVRJNQ.


Sample data for new application space on Wonka and Slugworth

Created by: @bayegan Feb 12 2022 at 15:43 CET
Last updated: Jun 03 2022 at 19:39 CET
ClickUp ID: IK-2234
To enable developers/IK employees to have test data that does not intervene with automation tests running on Wonka and Slugworth, create a new set of test data under a different Application Space for Wonka and Slugworth.
Acceptance criteria:
Test data will be wiped out regularly, consider this when assigning IDs to the test data set
What modifications are needed to be done in the system? Identify that (discuss with team)
New application space for Wonka
Test data under this application space
New application space for Slugworth
Test data under this application space

Commented by: @indyboox Jun 03 2022 at 09:22 CET
@bayegan I remember we talked about it at that time and I took some notes but none were indicating details on what kind of data we want there. Shall I bring this up in an afternoon huddle so that I can align with the requirements here?


External call causing rank error

I'm going to try to do this without posting all my code...  I have an external code which for the first GP solve returns this:
        if not x0:
            constraints = [
                            self.CDp0 >= .03,
                            self.CDp**2 >= self.CDp**2 * self.M**2 + self.CDp0**2,
                            self.CD >= self.CDp + 1.*(self.CL**2)/(np.pi*self.e*self.AR),
                            self.tau_w <=0.20
                          ]
            return ConstraintSet(constraints)

and when I run, I get this:
Beginning signomial solve.
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-491-7de7ae3319bf> in <module>()
    255 m=Model(objective, constraints)
    256
--> 257 sol=m.localsolve()
    258 # sol = m.solve()
    259 # aircraft = Aircraft()

/Users/codykarcher/Dropbox (MIT)/Research/gpkit/gpkit/constraints/prog_factories.pyc in solvefn(self, solver, verbosity, skipsweepfailures, *args, **kwargs)
     78         else:
     79             self.program, solvefn = genfunction(self, verbosity-1)
---> 80             result = solvefn(solver, verbosity-1, *args, **kwargs)
     81             solution.append(result)
     82         solution.program = self.program

/Users/codykarcher/Dropbox (MIT)/Research/gpkit/gpkit/constraints/signomial_program.pyc in localsolve(self, solver, verbosity, x0, rel_tol, iteration_limit, **kwargs)
    110                 nearest_feasible = feasibility_model(gp, "max")
    111                 self.gps.append(nearest_feasible)
--> 112                 result = nearest_feasible.solve(solver, verbosity=verbosity-1)
    113                 result["cost"] = None
    114             x0 = result["variables"]

/Users/codykarcher/Dropbox (MIT)/Research/gpkit/gpkit/geometric_program.pyc in solve(self, solver, verbosity, *args, **kwargs)
    180             sys.stdout = self.solver_log   # CAPTURED
    181             solver_out = solverfn(c=self.cs, A=self.A, p_idxs=self.p_idxs,
--> 182                                   k=self.k, *args, **kwargs)
    183             self.solver_out = solver_out
    184         finally:

/Users/codykarcher/Dropbox (MIT)/Research/gpkit/gpkit/_cvxopt.pyc in cvxoptimize(c, A, k, *args, **kwargs)
     43         g = log(matrix(c))
     44         F = spmatrix(A.data, A.row, A.col, tc='d')
---> 45         solution = gpsolver(k, F, g)
     46         return dict(status=solution['status'],
     47                     primal=solution['x'],

/Users/codykarcher/.local/lib/python2.7/site-packages/cvxopt/cvxprog.pyc in gp(K, F, g, G, h, A, b, kktsolver, **kwargs)
   2159         else: return f, Df, H
   2160
-> 2161     return cp(Fgp, G, h, dims, A, b, kktsolver = kktsolver, options = options)

/Users/codykarcher/.local/lib/python2.7/site-packages/cvxopt/cvxprog.pyc in cp(F, G, h, dims, A, b, kktsolver, xnewcopy, xdot, xaxpy, xscal, ynewcopy, ydot, yaxpy, yscal, **kwargs)
   1964
   1965     sol = cpl(c, F_e, G_e, h, dims, A_e, b, kktsolver_e, xnewcopy_e,
-> 1966          xdot_e, xaxpy_e, xscal_e, options = options)
   1967
   1968     sol['x'] = sol['x'][0]

/Users/codykarcher/.local/lib/python2.7/site-packages/cvxopt/cvxprog.pyc in cpl(c, F, G, h, dims, A, b, kktsolver, xnewcopy, xdot, xaxpy, xscal, ynewcopy, ydot, yaxpy, yscal, **kwargs)
    780             singular_kkt_matrix = False
    781             if iters == 0:
--> 782                 raise ValueError("Rank(A) < p or "\
    783                     "Rank([H(x); A; Df(x); G]) < n")
    784

ValueError: Rank(A) < p or Rank([H(x); A; Df(x); G]) < n

However, if I explicitly add the constraints like this in the GP:
constraints += [
                CDp0 >= .03,
                CDp**2 >= CDp**2 * M**2 + CDp0**2,
                CD >= CDp + 1.*(CL**2)/(np.pi*e*AR),
                tau_w <=0.20
               ]

and do a GP solve, it works fine.  Any thoughts?

This is a reappearance of issue #659, which had been resolved.

Went away after changing to:
            constraints = [
                            self.CDp0 >= .03,
                            self.CDp**2 >= self.CDp**2 * self.M**2 + self.CDp0**2,
                            self.CD >= self.CDp + 1.*(self.CL**2)/(np.pi*.9*10)
                          ]

And moving the tau constraint out to the GP.

I bet this was that tau_w was not declared as a variable, as in #666


How to refresh cursor more often?

Hi there.
Is there a way to refresh the cursors more often? it makes huge jumps and it hardly ever refreshes.... Is this something i have to do manually myself by polling location often?

The update frequency of the GPS position is not determined by ffwdme itself but by the runtime/OS. ffwdme just uses the watchposition method: https://github.com/ffwdme/ffwdme.js/blob/master/src/core/geolocation.js#L95-L99
Can you tell me which device you are using?

I was trying this from my mac while driving in the car, as I did not have an ipad at hand. Ideally though this will be used from an ipad..

Ok, a Mac will update the GPS position very slowly. Using an iPad with active GPS sensor, the position should update about twice a second while moving.
For testing on a Mac, you may want to look at the GeoProvider package: https://github.com/ffwdme/ffwdme.js/tree/master/src/debug/geoprovider
It provides tools to record and replay positions for local development.

Thanks I Will look into that!


Generate AdditionalConfiguration.php compatible with TYPO3 8.7, fixes #632

The Problem/Issue/Bug:
Resolves: https://github.com/drud/ddev/issues/632
How this PR Solves The Problem:
Manual Testing Instructions:
Automated Testing Overview:

Related Issue Link(s):
Release/Deployment notes:

Awesome, thanks so much!


BUG: Fix Unable to build documentation with Chinese

What do these changes do?
Fix Unable to build documentation with Chinese

Related issue number

Fixes #517
outcome

Thanks for your contribution!
Since we are using make html_zh_cn for Linux and macOS, I'd prefer use the same command for windows.
To do that, you may want to have a look at doc/make.bat. I think there's a bug that causes #517.
What do you think?

Thanks for your contribution!
Since we are using make html_zh_cn for Linux and macOS, I'd prefer use the same command for windows.
To do that, you may want to have a look at doc/make.bat. I think there's a bug that causes #517.
What do you think?

Sorry, I've been trying for a long time, but I haven't been able to find the bug in  doc/make.bat and fix it.

That's fine. Would you mind if someone else take over this issue?

That's fine. Would you mind if someone else take over this issue?

Sure, no problem.

That's fine. Would you mind if someone else take over this issue?

Sure, no problem.


Chapter 01 - 'Tap Me' crash on launch

I bought the book on paperback and cloned this repo to check out the sample code. Running the Tap Me app crashes on launch due to the snapshot function in SceneDelegate.swift.
There is a reference to florian's desktop which crashes.
https://github.com/objcio/thinking-in-swiftui-sample-code/blob/master/Chapter 01/Tap Me/Tap Me/SceneDelegate.swift#L55
Temporary fix for now is to comment out the snapshot() call in SceneDelegate.swift.

Ouch 😬
Should be fixed on master!


Change the colour of Text in Buttons

Fixes Issue #47
Screenshot

/hold till we get confirmation on changing the color from JJ I believe

Hey @shivam-sharma7, as mentioned in this issue https://github.com/kubesimplify/website/issues/47, we need to change the text colour of the email field only and not everywhere in the website. Please update the style accordingly.
Also change the colour of "Subscribe" text to maintain consistency in the design. Please see the attached image for reference.

cc @anubha-v-ardhan @AvineshTripathi

Hey @shivam-sharma7, as mentioned in this issue #47, we need to change the text colour of the email field only and not everywhere in the website. Please update the style accordingly.
Also change the colour of "Subscribe" text to maintain consistency in the design. Please see the attached image for reference.

Colour to be used for text: #1B2731 / rgb(27, 39, 49)
cc @anubha-v-ardhan @AvineshTripathi

done 👍

LGTM
cc @anubha-v-ardhan

Thanks for contributing @shivam-sharma7 & for reviewing @AvineshTripathi 🙂

Thanks for contributing @shivam-sharma7 & for reviewing @AvineshTripathi 🙂

My pleasure


Problem with the camera

Hi, I just gave a look to the published version of the website and i discovered a problem. The website asked me to use the camera but it doesn't work.
I'm attaching a screenshot of the problem. As you can see the camera box shows a black box with a disabled camera. If i click the camera button, the system takes the photo but the result i get is: "a white and black logo (61.73%)".
This problem persists even if i refresh or i reload the application.
Is this issue only on my side?

I tried with both solutions and still it doesn't work. Tomorrow I'll try fix this problem on my browser
If I succeed I'll let you know on discord to avoid to send lots of replies here in this section

I tried many times and i solved the problem. It was my browser issue


iOS MetalKit & ARKit example's problem

I think current iOS ar sample has a problem.
it calls the render function in ar session didUpdateFrame callback.
it will affect the tracking performance.
I would like to calls the render function in MTKView's draw callback.
But, unfortunately it failed call render in MTKView draw callback.(black screen and error messages).
Can you describe why cannot call the filament render in MTKView draw callback?
Cheers.

What were the error messages? Filament manages it’s own Metal context / objects and is not designed to work with a MTKView.

Note that the render function doesn't do the actual rendering, this happens on a different thread. The render function should be very cheap in the ar case.

This might be a synchronization issue. Note that ARSession calls didUpdateFrame on the main dispatch queue (see delegateQueue). I'm not sure what queue MTKView.draw gets called on.

the error message is here.
Execution of the command buffer was aborted due to an error during execution. Ignored (for causing prior/excessive GPU errors) (IOAF code 4)

If I don't add FullScreenTriangle(https://github.com/google/filament/blob/master/ios/samples/hello-ar/hello-ar/FilamentArView/FullScreenTriangle.h), then it works with MTKViewDelegate.
But, with FullScreenTriangle it don't work in MTKViewDelegate.

It's hard to say what the issue is without seeing the rest of your project. Why do you need to use a MTKView? The samples use a simple UIView subclass that overwrites layerClass to return a CAMetalLayer (see FilamentView).
My best guess is that the error is related to the camera feed. You can try replacing mCameraFeedTexture with a placeholder texture and see if that works.

Yes, I attached the sample code for that.
hello-ar.zip
And the reason to use MTKView is simple, just I wanted to follow the standard ARkit-metal architecture provided by Apple.

The errors you see are because drawInMTKView is called before any camera frames have been captured. You can add the following if check at the beginning of drawInMTKView to prevent rendering before a camera frame is ready:
- (void)drawInMTKView:(nonnull MTKView *)view {
    ARFrame *frame = self.session.currentFrame;

    if (!frame.capturedImage) {
        return;
    }

    ...
}

It works.
Thanks for your comment.


Edit on Github link tweaks, disable search.

Swaps the in-page-footer edit link for one in the header, replacing the vuepress default to the project root to the specific page in question.
Also disables search for now, since it's of questionable utility here.

That's seems to be more discoverable.