scan_string() return token_type::parse_error; when parse ansi file

With VS2015 IDE  when I run below demo code to read json file, scan_string function return token_type::parse_error at line 2186.
{
ofstream out_json("C:\test.json");
    json jsDefault = json();
    jsDefault["name"] = "默认";
    jsDefault["param"] = json();
    json jsArray = json::array({ jsDefault });

    json jsObj = json();
    jsObj["select"] = "默认";
    jsObj["items"] = jsArray;

    out_json << std::setw(4) << jsObj;

    out_json.close();

    ifstream in_json("C:\\test.json");
    json jsNewObj = json();
    in_json >> jsNewObj;
}

Could you please try the develop version and paste the full exception message? On MSVC, we had several issues regarding the encoding of the strings: the library only supports UTF-8 encoded strings.

@nlohmann I'm already using the develop branch, the scan_string function parse error with return token_type::parse_error
{
    if (JSON_UNLIKELY(not next_byte_in_range({0x80, 0xBF})))
    {
        return token_type::parse_error;//line 2186
    }
    break;
}

Looks like you need to convert your non-ascii strings jsDefault["name"] and jsObj["select"] to utf-8 before you put them in the json object.

@gregmarr  Yes! But this project should support this.

The project supports UTF-8. Could you try adding a u8 prefix to your string literals, e.g. jsDefault["name"] = u8"默认";?

@nlohmann add u8 prefix not work correct.
#include "json.hpp"

#include <fstream>

using namespace std;
using json = nlohmann::json;

int main()
{
    ofstream out_json("C:\\test.json");

    json jsDefault = json();
    jsDefault["name"] = u8"默认";
    jsDefault["param"] = json();
    json jsArray = json::array({ jsDefault });

    json jsObj = json();
    jsObj["select"] = u8"默认";
    jsObj["items"] = jsArray;

    out_json << std::setw(4) << jsObj;

    out_json.close();

    ifstream in_json("C:\\test.json");
    json jsNewObj = json();
    in_json >> jsNewObj;
    string strJson = jsNewObj.dump(4);

    return 0;
}

Output file c:\test.json text.
{
    "items": [
        {
            "name": "默认",
            "param": null
        }
    ],
    "select": "默认"
}

And string strJson = jsNewObj.dump(4); text is:
{
    "items": [
        {
            "name": "榛樿",
            "param": null
        }
    ],
    "select": "榛樿"
}

Can you please attach your code and the JSON file (best as a ZIP archive) so I can check this myself?

Here is VS2015 test project you can try it.
TestJson.zip

I don't have MSVC. Can you please execute the code on your side and attach the generated JSON file please?

Check the attach file.
test.zip

I can parse the file without problems:
#include <iostream>
#include <fstream>
#include "json.hpp"

using json = nlohmann::json;

int main(int argc, char* argv[]) {
    std::ifstream f("test.json");
    json j;
    f >> j;
    std::cout << j << std::endl;
}

Not error,decode string is not same as src string.

In https://github.com/nlohmann/json/issues/812#issue-270235887 you mentioned a parse error. I cannot reproduce this with the file. I think your input is not UTF-8 encoded. The library only supports UTF-8.

No u8 prefix will report parse error.Afert add u8 prefix no error but decoded string not same as source string.

I didn't know how to check it, but i think use outfile<<jsonobj and infile>>jsonobj method with same file could be same.

The thing is that the library does not check whether stored strings are UTF-8 encoded. That's why, serialization may produce non-compliant JSON text. When such a text is parsed, a parse error occurs reporting the non-valid UTF-8.

Can you add this feature to reduce discuss about self save file but parse error with invalid UTF-8 char? This will take a lot of your time taocpp json has this feature.

I won't do re-encoding, but maybe throwing an exception when non-UTF-8 encoded text is dumped is discussed in #838.

It would be better to save your time if you implement convert to UTF-8 encode when dump to file. I guess when more user use this library and more same question will be disussed.

This seems to be MSVC-specific code.


.tekton/pull-request: run conditionally

Don't run the pipeline if the only changed files are

*.md
.github/*
renovate.json

Note that a similar attempt was made in https://github.com/konflux-ci/build-definitions/pull/524, which took the approach of enumerating every file/directory which should trigger the pipeline (maybe files.all wasn't available at the time). This PR takes the opposite approach.

Tested the expression in https://playcel.undistro.io/ with variations of the following input
# Here is the input data in YAML or JSON format.

event: push
target_branch: gh-readonly-queue/main/

body:
  pull_request:
    draft: false

files:
  all:
  - "README.md"
  - "renovate.json"
  - ".github/workflows/checkton.yaml"

As @arewm found out, making the Konflux pipeline a not-required check means that if you press the Merge when ready button, github will not wait for the pipeline to finish.
There have been many requests for GitHub to make the "required check is skippable" behavior sane (https://github.com/orgs/community/discussions/13690), but until that happens, we can't go with this approach.

Perhaps this could be an enhancement in Pipelines as Code, mark skipped Pipelines as successful?

https://github.com/openshift-pipelines/pipelines-as-code/issues/1746 if anyone wants to follow up with comments.

openshift-pipelines/pipelines-as-code#1746 if anyone wants to follow up with comments.

Nice, thanks for filing that. For our use case, we can probably add something to the pipeline to skip just the e2e-tests task, as that's the main one we really care about.
But this does seem like it could be a useful generic PaC feature


Update POWERLEVEL9K_BACKGROUND_JOBS default colors

The default POWERLEVEL9K_BACKGROUND_JOBS_BACKGROUND and POWERLEVEL9K_BACKGROUND_JOBS_FOREGROUND colors are hardly visible. I would suggest to update them as follows, which stand out much better on both dark and light terminal themes:
POWERLEVEL9K_BACKGROUND_JOBS_FOREGROUND='black'
POWERLEVEL9K_BACKGROUND_JOBS_BACKGROUND='yellow'

If you agree I can create a PR.

Hi @lucatrv !
Sorry for the late response. That depends very much on the used color scheme. The background_jobs segment is cyan on black/white (depends on $POWERLEVEL9K_COLOR_SCHEME)..
Could you post a screenshot with a default color scheme so we can see the segment?

I attach the screenshots with Powerlevel9k default color scheme, on Gnome Terminal with both dark and light themes.
Default on Gnome Terminal dark:

Default on Gnome Terminal light:

Proposed on Gnome Terminal dark:

Proposed on Gnome Terminal light:

I actually think is a good idea. Sorry it took so long to get a response, @lucatrv.
Please feel free to submit a PR against the next branch. Note that the codebase on next is very different from what's currently on master, so you'll need to make the change on that code and file the PR =)

@bhilburn while working on this PR, I found out that to get the following colors:
POWERLEVEL9K_BACKGROUND_JOBS_FOREGROUND='black'
POWERLEVEL9K_BACKGROUND_JOBS_BACKGROUND='yellow'

I need to edit the file segments/background_jobs.p9k as follows
# Register segment
# Parameters:
#   segment_name  context  foreground  background  Generic  Flat/Awesome-Patched  Awesome-FontConfig  Awesome-Mapped-FontConfig  NerdFont
#                                                            ⚙                                                               
p9k::register_segment 'BACKGROUND_JOBS' '' "yellow" "black" $'\u2699'  $'\uE82F '  $'\uF013 '  '\u'$CODEPOINT_OF_AWESOME_COG' '  $'\uF013 '

while I would have expected:
# Register segment
# Parameters:
#   segment_name  context  foreground  background  Generic  Flat/Awesome-Patched  Awesome-FontConfig  Awesome-Mapped-FontConfig  NerdFont
#                                                            ⚙                                                               
p9k::register_segment 'BACKGROUND_JOBS' '' "black" "yellow" $'\u2699'  $'\uE82F '  $'\uF013 '  '\u'$CODEPOINT_OF_AWESOME_COG' '  $'\uF013 '

(foreground and background colors seem to be swapped).
Can you please advise?

Hm, really? @onaforeignshore - Can you comment, here?
@dritter - You haven't seen any color reversals have you?

Note: I'm on Debian Stable, zsh v5.3.1

Hmm. Changing the fore and background color works for me. The difference to v0.6.6 is that you need to start a new shell to see your changes. It is not possible to change the colors on the fly any more.

This is really weird... I now installed zsh v5.6.2 from Debian Testing, and restarted Gnome Terminal, and yet in order to get the desired colors:

I need to edit segments/background_jobs.p9k as follows:
# Register segment
# Parameters:
#   segment_name  context  foreground  background  Generic  Flat/Awesome-Patched  Awesome-FontConfig  Awesome-Mapped-FontConfig  NerdFont
#                                                            ⚙                                                               
p9k::register_segment 'BACKGROUND_JOBS' '' "yellow" "black" $'\u2699'  $'\uE82F '  $'\uF013 '  '\u'$CODEPOINT_OF_AWESOME_COG' '  $'\uF013 '

(foreground and background colors are swapped).
Not sure what I'm doing wrong...

Indeed, that comment is wrong, if you look at the definition of p9k::register_segment, you'll see the following comment:
# @args
#   $1 string Segment name
#   $2 string State name or ""
#   $3 misc Default background color
#   $4 misc Default foreground color
#   $5 string Generic icon
#   $6 string Flat / Awesome Patched icon
#   $7 string Awesome FontConfig icon
#   $8 string Awesome Mapped FontConfig icon
#   $9 string NerdFont Complete / FontConfig icon

So the third parameter is the background color and fourth is foreground color..

I see. Should I open an issue about this, or submit a PR, or will you take care yourself?

Or I can add a commit to my PR

I'd prefer a separate PR :)
Good catch, btw.

Fixed by #1014! Thanks so much, @lucatrv! =)


Create Sort an array of 0s, 1s and 2s.CPP

Hello sir ,
I'm Mayank Rastogi , github id - mayxnk
I did the contribution by adding a new program of sort an array 0,1,2  in C++ in the repo by following all the rules.
Kindly consider it , & for this I'll very grateful to you.
Thankyou

add the file in correct folder


leader key

Is leader key possible? I tried to use <SPACE> in nmap but it does not work.

Sadly no. Jupyterlab uses the codemirror editor and it's vim mode does not yet have a leader key. See https://github.com/codemirror/CodeMirror/issues/2841
Also from that issue:

The Vim bindings are without a maintainer at the moment, so don't hold your breath waiting for new features.

Thank you


security/acme-client: does not deal correctly with Subject Alternate Names and nsupdate

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[X] I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
[X] I have searched the existing issues, open and closed, and I'm convinced that mine is new.
[X] The title contains the plugin to which this issue belongs

Describe the bug
If you
specify multiple names to be included in a certificate and
you use the RFC update mechanism for DNS updates and
you use CNAMEs for the _acme-challenges
I don't see any valid way to specify the  option to add the individual  --challenge-alias parameter for every single -d parameter as you would need one per alternative name.
A clear and concise description of what the bug is, including last known working version (if any).
Tip: to validate your setup was working with the previous version, use opnsense-revert (https://docs.opnsense.org/manual/opnsense_tools.html#opnsense-revert)
To Reproduce
Steps to reproduce the behavior:
Try creating a certificate using DNS-01 verification with several "Alt Names" where every single of the alternative names has another CNAME pointed to for providing the DNS-01 challenge that needs to be provided to a --challenge-alias parameter in the acme.sh call. You will be missing input fields for them.
Expected behavior
Having one input field per name if you use challenge-alias

If I understand this correctly, you want to use DNS alias mode:
https://github.com/acmesh-official/acme.sh/wiki/DNS-alias-mode
This is supported:

Services: ACME Client: Certificates
Edit Certificate
scroll to the bottom: DNS Alias Mode

Can you refer to the part of the (ACME plugin) documentation where the necessary handling of input for acme.sh case 4 (see https://github.com/acmesh-official/acme.sh/wiki/DNS-alias-mode#4-specify-different-aliased-domains-for-each-domain) is shown?
In my specific case the CNAMEs for my challenges have the form
_acme-challenge.FQDN. IN CNAME FQDN.acme-z.one.
and the only way to do so is calling acme.sh as --issue  -d  x1.example.com --challenge-alias x1.example.com.acme-z.one -d  x1.example.net --challenge-alias x1.example.net.acme-z.one; no matter what I'm entering in OPNSense, this is not coming out.

If you enable the previously mentioned DNS Alias Mode option...

...then the acme.sh command will contain the required parameters:
/usr/local/sbin/acme.sh --issue ... --domain 'test.example.org' --challenge-alias 'acme-challenge-alias.example.com' ...


sidecli should not read state.bin

I believe what @EduardoRFS means by this issue is that the CLI should rely on a remote interface to the node, not local access to its state file. I.e, the CLI should be a thin wrapper around a GraphQL interface or other RPC.

This is handled already.


allowEmptyOption regression in 0.12 ?

Hi,
In the version before 0.12, allowEmptyOption was working this way : the empty option - aka the placeholder - was inserted in the dropdown as an option of the select.
Now, it is inserted as a placeholder on the input. Seems great, but... if we set a display none property on the input to disable it, we can't see the placeholder anymore... It seems to be a big regression !
Any thoughts on this ?

Yes, a very strange behavior. You set this option to true and placeholder (empty option) simply removed.

Hi,
I've found a fast and dirty hack.
In function registerOption replace
if (!key || this.options.hasOwnProperty(key)) return false;
to
if ((!key || this.options.hasOwnProperty(key)) && !this.settings.allowEmptyOption) return false;
It seems working for me.

:+1:  for the fix

:+1: for the fix

@whather :+1:

Duping #739


Usage Question

hey there, I'm wanting to use this api but im wondering if I need to build this project for it to work or something.
I would like to use it like this: https://fmovies-api.vercel.app/search?query=Stranger+Things
but it doesn't give any information whenever I use the api. I think im doing something wrong but im just wondering how exactly does this work. Do i need to register for something?
Thanks.

firstly, you need to use keyword instead of query and for usage info please go through the readme file.
regarding the response issue:-

there is some scraping issue that needs to fixed due to changes in the domain but this is project is no longer being maintained so if you figure out the issue and want to collaborate just create a pull request and I'll merge it

Is there any place i can message you privately?


cmake: lld: Remove duplicate -fuse-ld=lld

-fuse-ld=lld is currently specified twice through the baremetal property (in cmake/linker/lld/linker_flags.cmake) and TOOLCHAIN_LD_FLAGS (in cmake/linker/lld/target.cmake). This doesn't really harm anything as it isn't duplicated on the link line (and specifying it multiple times wouldn't hurt even if it was), but it also doesn't really help anything.
-fuse-ld isn't baremetal-specific and setting it via TOOLCHAIN_LD_FLAGS will cover this case anyway, so remove this duplicate.

@tejlmand should this be part of 4.0?

@tejlmand should this be part of 4.0?

It's not critical, but nice cleanup.
Feel free to include, but i'm not sure how strict we are with release and minor cleanup like this.


fix: change publish to use http relay client in handlers

Description
This PR changes the use of publish from websocket client to the HTTP relay client to solve the websocket disconnect issue.
Resolves #74
How Has This Been Tested?
Integration test.
Due Diligence

[ ] Breaking change
[ ] Requires a documentation update
[ ] Requires a e2e/integration test update

Don't we need this for the /notify endpoint too?

I think not because we are already using the HTTP relay client when processing publishing jobs.


codellama:7b Unexpected EOF

Issue:
codellama 13b run while codellama 7b fails with following error:
Error: error reading llm response: unexpected EOF
I can codellama 13b with same prompt.
I have 16GB RAM

It looks like ollama crashed. Would it be possible to get the logs from you?
Log location:
~/.ollama/logs/server.log

Sure, but log location you provided doesn't exists

Found it on journalctl.
logs.txt

This was due to Ollama trying to load more layers into VRAM than was possible:
ollama[8017]: CUDA error 2 at /go/src/github.com/jmorganca/ollama/llm/llama.cpp/ggml/ggml-cuda.cu:4856: out of memory
ollama[1821]: [GIN] 2023/10/02 - 03:30:54 | 200 |  3.712295143s |       <IP_ADDRESS> | POST     "/api/generate"
ollama[1821]: 2023/10/02 03:30:54 llama.go:320: llama runner exited with error: exit status 1

There is another open issue for refining how many layers we load into memory, there is also a workaround there in the last comment.
#618
We should be returning better error message in the client, I'll tweak this issue to reflect that.

@ratnadeep007 what kind of GPU and how much VRAM do you have? As @BruceMacD mentioned, calculations are slightly different based on models. It's possible for 13B models, it's not trying to offload all the layers to GPU. Instead, some layers are offloaded to GPU while the remainder is processed by the CPU.

@mxyng I am running on RTX 2060 with 6 GB VRAM

may I suggest that there could be a switch to disable GPU offloading, or at very least, to specify how much V-RAM to use?
I have RTX2060 - 12GB VRAM and I get llama.cpp/ggml/ggml-cuda.cu:4856: out of memory

@jerzydziewierz thanks for the suggestion, you can disable GPU offloading right now by setting PARAM num_gpu 0 in the Modelfile, we will be adding this to the CLI soon also. This also allows you to configure less GPU offloading in general.

The root issue here was resolved in #825, let me know if anyone else sees this.

The root issue here was resolved in #825, let me know if anyone else sees this.

I am experiencing this right now. When I try to run these in terminal:
ollama run mistral
`ollama run orca-mini
Or try to call them from my llama-index code.
They fail with the only message being:
Error: Post "http://<IP_ADDRESS>:11434/api/generate": EOF
There is nothing in output re:
Here is output from journalctl for ollama:
Mar 05 11:00:25 jesse-MS-7C02 ollama[74384]: llm_load_tensors: ggml ctx size =    0.11 MiB Mar 05 11:00:25 jesse-MS-7C02 ollama[74384]: llm_load_tensors: mem required  = 3917.98 MiB Mar 05 11:00:25 jesse-MS-7C02 ollama[74384]: llm_load_tensors: offloading 32 repeating layers to GPU Mar 05 11:00:25 jesse-MS-7C02 ollama[74384]: llm_load_tensors: offloading non-repeating layers to GPU Mar 05 11:00:25 jesse-MS-7C02 ollama[74384]: llm_load_tensors: offloaded 33/33 layers to GPU Mar 05 11:00:25 jesse-MS-7C02 ollama[74384]: llm_load_tensors: VRAM used: 0.00 MiB Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]: ................................................................................................... Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]: llama_new_context_with_model: n_ctx      = 2048 Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]: llama_new_context_with_model: freq_base  = 1000000.0 Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]: llama_new_context_with_model: freq_scale = 1 Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]: CUDA error 999 at /go/src/github.com/jmorganca/ollama/llm/llama.cpp/ggml-cuda.cu:495: unknown error Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]: current device: -1809317920 Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]: Lazy loading /tmp/ollama801692426/cuda/libext_server.so library Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]: GGML_ASSERT: /go/src/github.com/jmorganca/ollama/llm/llama.cpp/ggml-cuda.cu:495: !"CUDA error" Mar 05 11:00:26 jesse-MS-7C02 ollama[74962]: Could not attach to process.  If your uid matches the uid of the target Mar 05 11:00:26 jesse-MS-7C02 ollama[74962]: process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try Mar 05 11:00:26 jesse-MS-7C02 ollama[74962]: again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf Mar 05 11:00:26 jesse-MS-7C02 ollama[74962]: ptrace: Inappropriate ioctl for device. Mar 05 11:00:26 jesse-MS-7C02 ollama[74962]: No stack. Mar 05 11:00:26 jesse-MS-7C02 ollama[74962]: The program is not being run. Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]: SIGABRT: abort Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]: PC=0x7fc01a899a1b m=14 sigcode=18446744073709551610 Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]: signal arrived during cgo execution Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]: goroutine 41 [syscall]: Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]: runtime.cgocall(0x9c3170, 0xc00033a608) Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]:         /usr/local/go/src/runtime/cgocall.go:157 +0x4b fp=0xc00033a5e0 sp=0xc00033a5a8 pc=0x4291cb Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]: github.com/jmorganca/ollama/llm._Cfunc_dynamic_shim_llama_server_init({0x7fbf94001d40, 0x7fbf70dfa410, 0x7fbf70d> Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]:         _cgo_gotypes.go:287 +0x45 fp=0xc00033a608 sp=0xc00033a5e0 pc=0x7cf965 Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]: github.com/jmorganca/ollama/llm.(*shimExtServer).llama_server_init.func1(0x45973b?, 0x80?, 0x80?) Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]:         /go/src/github.com/jmorganca/ollama/llm/shim_ext_server.go:40 +0xec fp=0xc00033a6f8 sp=0xc00033a608 pc=0> Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]: github.com/jmorganca/ollama/llm.(*shimExtServer).llama_server_init(0xc00010a2d0?, 0x0?, 0x43a2e8?) Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]:         /go/src/github.com/jmorganca/ollama/llm/shim_ext_server.go:40 +0x13 fp=0xc00033a720 sp=0xc00033a6f8 pc=0> Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]: github.com/jmorganca/ollama/llm.newExtServer({0x17845038, 0xc0004327e0}, {0xc000190af0, _}, {_, _, _}, {0x0, 0x0> Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]:         /go/src/github.com/jmorganca/ollama/llm/ext_server_common.go:139 +0x70e fp=0xc00033a8e0 sp=0xc00033a720 > Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]: github.com/jmorganca/ollama/llm.newDynamicShimExtServer({0xc0000be000, 0x2a}, {0xc000190af0, _}, {_, _, _}, {0x0> Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]:         /go/src/github.com/jmorganca/ollama/llm/shim_ext_server.go:93 +0x547 fp=0xc00033aaf8 sp=0xc00033a8e0 pc=> Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]: github.com/jmorganca/ollama/llm.newLlmServer({0xc3fc44, 0x4}, {0xc000190af0, _}, {_, _, _}, {0x0, 0x0, 0x0}, ...) Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]:         /go/src/github.com/jmorganca/ollama/llm/llm.go:125 +0x149 fp=0xc00033ac78 sp=0xc00033aaf8 pc=0x7ceac9 Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]: github.com/jmorganca/ollama/llm.New({0xc00048e240?, 0x0?}, {0xc000190af0, _}, {_, _, _}, {0x0, 0x0, 0x0}, ...) Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]:         /go/src/github.com/jmorganca/ollama/llm/llm.go:115 +0x628 fp=0xc00033aef0 sp=0xc00033ac78 pc=0x7ce608 Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]: github.com/jmorganca/ollama/server.load(0xc000002f00?, 0xc000002f00, {{0x0, 0x800, 0x200, 0x1, 0xfffffffffffffff> Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]:         /go/src/github.com/jmorganca/ollama/server/routes.go:84 +0x425 fp=0xc00033b0a0 sp=0xc00033aef0 pc=0x99ef> Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]: github.com/jmorganca/ollama/server.GenerateHandler(0xc000466600) Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]:         /go/src/github.com/jmorganca/ollama/server/routes.go:191 +0x8c8 fp=0xc00033b748 sp=0xc00033b0a0 pc=0x99f> Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]: github.com/gin-gonic/gin.(*Context).Next(...) Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]:         /root/go/pkg/mod/github.com/gin-gonic/gin@v1.9.1/context.go:174 Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]: github.com/jmorganca/ollama/server.(*Server).GenerateRoutes.func1(0xc000466600) Mar 05 11:00:26 jesse-MS-7C02 ollama[74384]:         /go/src/github.com/jmorganca/ollama/server/routes.go:877 +0x68 fp=0xc00033b780 sp=0xc00033b748 pc=0x9a91>
You can see that CUDA error is occuring due to llama.cpp


[ignore] Annotations - change file access pattern

Remove the data proxy object in the context manager and replace it with a heavier weight file access manager (FileAccessProvider) class that encapsulates all the various data proxies.
Update engine code to remove the last traces of the original DataProxy opting instead for always retrieving data proxies from the context.
Add a temporary node_name override hack to get demo to work.  We can clean this up when the functionality is expanded more generally.
Removing some tests that have been commented for a long time.

Hopefully this makes developing flytekit a bit easier.  I'm now able to run stuff like this.
docker run -e PROJECT=flytesnacks -v `pwd`:/root -v /Users/ytong/go/src/github.com/lyft/flytekit/flytekit:/opt/venv/lib/python3.8/site-packages/flytekit -v /tmp/output/flytekit:/tmp/output -it flytecookbook:latest bash

and then within the container
FLYTE_INTERNAL_CONFIGURATION_PATH=/root/sandbox.config FLYTE_PLATFORM_CLOUD_PROVIDER=local pyflyte-execute --task-module recipes.aaa.simple --task-name t1 --inputs file:///tmp/output/t1/inputs.pb --output-prefix file:///tmp/output/t1

@wild-endeavor why do we have to run the 2nd command inside the container? if we have a virtualenv is that not enough?

Thank you for doing this. So I eventually want it to be just local file based


Have webview taking the full available space

currently there is some space on right and left sides
I noticed that the padding is set to 20px https://github.com/Microsoft/vscode/blob/35523f6c51bdc1edae1696a586dadd021fe47096/src/vs/workbench/contrib/webview/electron-browser/webview-pre.js#L420
i think it would be better to 0.
for instance we will have:

instead of truncated top bar:

We provide some reasonable default styles so that content without good stylesheets doesn't look terrible. You can use css in your webview to override these


TODO PouchDB: describe issue that happens with #970

See the details in thaliproject/Thali_CordovaPlugin#970

We've found a problem in pouch:
function tryCatchInChangeListener(self, change) {
  // isolate try/catches to avoid V8 deoptimizations
  try {
    self.emit('change', change);
  } catch (e) {
    guardedConsole('error', 'Error in .on("change", function):', e);
  }
}

This exists in recent pouch in packages/node_modules/pouchdb-core/src/changes.js. This is just an example. There are many similar try-catches in pouch.
We are expecting that our handler's exception will be provided in error event. For example:
pouch.changes(..)
.on('change', function () {
  throw new Error('fit');
})
.on('error', function (error) {
  ...
});

But these try-catches blocks all our exceptions. So we've added a workaround:
  PouchAlt.prototype.on =
  PouchAlt.prototype.addListener = function (type, listener) {
    var self = this;
    // We don't want PouchDB to catch our exception from 'listener'.
    // We want to cancel current PouchDB action and emit 'error' with exception.
    return PouchAlt.super_.prototype.addListener.call(this, type, function () {
      try {
        listener.apply(this, arguments);
      } catch (e) {
        self.emit('error', e);
      }
    });
  }

  // 'Changes' has an 'EventEmitter' too, but it isn't exported.
  // We have to overwrite 'EventEmitter' methods here.
  PouchAlt.prototype.changes = function () {
    var changes = PouchAlt.super_.prototype.changes.apply(this, arguments);
    changes.on  = PouchAlt.prototype.on.bind(changes);
    return changes;
  };

Add reference to #970.


[ISSUE #366] remove custom concept [dcn&&region]

#366

@iNanos DefaultEventMeshClient constructor method has subAgent and pubAgent, these agents generateMethod without any sub/pub group should be change.

Some files still contains dcn concept, please have a check, such as client_manage.sh，session.sh，ClientManageController.java，ShowClientBySystemHandler.java e.g.

Codecov Report

Merging #390 (10402e5) into develop (0ffe74e) will increase coverage by 0.10%.
The diff coverage is 0.93%.

@@             Coverage Diff              @@
##             develop    #390      +/-   ##
============================================
+ Coverage       2.84%   2.94%   +0.10%
  Complexity        89      89
============================================
  Files            225     224       -1
  Lines          11054   10733     -321
  Branches         932     918      -14
============================================
+ Hits             314     316       +2
+ Misses         10695   10372     -323
  Partials          45      45

Impacted Files
Coverage Δ

...in/java/org/apache/eventmesh/common/Constants.java
0.00% <ø> (ø)

...g/apache/eventmesh/common/command/HttpCommand.java
0.00% <ø> (ø)

...e/eventmesh/common/config/CommonConfiguration.java
0.00% <ø> (ø)

...rotocol/http/body/client/HeartbeatRequestBody.java
0.00% <0.00%> (ø)

...rotocol/http/body/client/SubscribeRequestBody.java
0.00% <0.00%> (ø)

...tocol/http/body/client/UnSubscribeRequestBody.java
0.00% <0.00%> (ø)

...col/http/body/message/ReplyMessageRequestBody.java
0.00% <0.00%> (ø)

...http/body/message/SendMessageBatchRequestBody.java
0.00% <0.00%> (ø)

...tp/body/message/SendMessageBatchV2RequestBody.java
0.00% <0.00%> (ø)

...ocol/http/body/message/SendMessageRequestBody.java
0.00% <0.00%> (ø)

... and 56 more

Continue to review full report at Codecov.

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


wheres the source

is the source for this SDK up somewhere or is all we get the zip with the bundle in it

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3d76dde8-c24c-db44-3487-a058759273de
Version Independent ID: d6fcf3de-633b-660b-c55c-9a00dc979e22
Content: Cognitive Services Speech SDK for JavaScript
Content Source: docs-ref-services/speech-service.md
Service: cognitive-services
Product: azure
GitHub Login: @mahilleb-msft
Microsoft Alias: mahilleb

Hi @andersponders,
currently the .ZIP is all there is, but we're working on putting out an NPM package and source (hopefully this year, but it could slip into next).
Best, Mark


Feature suggestion: Select Python interpreter directly from this extension

Thanks for this extension! If there are not already plans to do so, I'd love to be able to change the current Python interpreter (that is, automatically issue the Python: Select Interpreter command) directly from the root of the list of venvs shown by vscode-python-manager.
It would be very slick to be able to accomplish that by way of a right-click context menu, or additional button next to the Open in Terminal button, or whatever interface might make the most sense.

@DonJayamanne This extension is a great idea. I have taken a look a VSCode a few times, but keep going back to PyCharm because its interpreter handling is so good. Being able to both create and select interpreters in this extension would be a huge improvement to VSCode's Python support.

ill be working on this feature soon

This has been completed


Build Documentation

Hey I want to use this, but need to update the kafka-clients to 2.8.0 in the build path.
How can I rebuild the jar using gradle? Or could we get a new release :)

A new release with the latest clients will be available by the end of this weekend, if not sooner. :)

@andrecowie If you're still interested, this issue should have been fixed in https://github.com/joschi/kafka-gitops/releases/tag/0.2.16.


CASMINST-3483: set CMN gateway "correctly"

"Correctly" is in quotes here because the fact that we're special-casing
CAN and CMN gateways here means the code is broken in a more fundamental
way.  The gateways are already set correctly before entering writeOutput()
and then seem to get re-templated incorrectly after that.  More
investigation is needed.  For now, copy what was done for the CAN.
Summary and Scope

Fixes CASMINST-3483

Issue Type

Bugfix Pull Request

Prerequisites

[x] I have included documentation in my PR (or it is not required)
[x] I tested this on internal system (x) (if yes, please include results or a description of the test)

Tested with redbull input data.
Idempotency
N/A
Risks and Mitigations
N/A

Version bump to 1.9.10.

fixed


Detect unknown/undefined prop usage

This is a proposal for enhancing vue-tsc
Example:
<MyComponent
    :propThatDoesNotExist="42"
/>

When running npx vue-tsc --noEmit i want it to detect that propThatDoesNotExist is not presently defined in myComponent.
This could produce a warning or error.
Feature like this currently exists in TS files.
When trying to edit fields that is not defined in some typescript class it will output:
Property 'xxx' does not exist on type 'MyClass'.
This would be very helpful for Vue developers when renaming props or performs refactoring or git rebases as looking through the code manually can be tedious.

This is intentional behavior as this is often used in css selectors.
I'll explore add a option in vueCompilerOptions to change this behavior.

@johnsoncodehk thanks
would be great to have.
Having to opt in through some configuration is fine.

I also think it is great to have this feature.
IMO data-* and aria-* can be ignored even if it is not used.

https://www.typescriptlang.org/docs/handbook/jsx.html#attribute-type-checking
Note: If an attribute name is not a valid JS identifier (like a data-* attribute), it is not considered to be an error if it is not found in the element attributes type.

But it seems that vue always treat attribute data-foo as dataFoo

It may be more appropriate to handle this case by giving a warning rather than an error.
The proposed solution is to add option in vueCompilerOptions so maybe users can select option there for themselves of how severe they want to treat this issue, including the possiblity of disabling the check itself

@johnsoncodehk Do you have any plan for adding that?

In 0.36, custom / unknown attrs types behavior handle responsibility will transfer to developer.

Expand custom attrs example

<template>

</template>

// env.d.ts
declare module '@vue/runtime-dom' {
    interface HTMLAttributes {
        myprop: string
    }
}

export { }

Allow any attrs

// env.d.ts
declare module '@vue/runtime-dom' {
    interface HTMLAttributes {
        [key: string]: any
    }
}

export { }

@johnsoncodehk Thankyou for mentioning that here. Suddenly today my Visual Studio Code started giving 'property does not exist on type' warnings for all the custom attributes starting with 'data-*' like this Test after adding the code in env.d.ts for allow any attrs it solved the issue.
declare module '@vue/runtime-dom' {
interface HTMLAttributes {
[key: string]: any
}
}
export { }

@johnsoncodehk Since this change regarding unknown properties. I am also getting this error on a V-Calendar Components v-model value before this it was fine. I am newbie and don't have any idea how I can omit this warning.

I also think it is great to have this feature. IMO data-* and aria-* can be ignored even if it is not used.
Hello. How to enable ignoring this case?

This change is bonkers! How do volar check where this attribute that I passed on purpose ends up? Does it just "assumes" it is the root element of the template? But even that doesn't work properly. Vue has an attribute fallthrough on purpose and this change makes vue-tsc crash on basically every component where I use attribute fallthrough (which I use A LOT).
This feature should be opt-in and not opt-out.
How can I disable this?

@johnsoncodehk your solution does not work for components. I cant even pass an id attribute to a component

@Fuzzyma His solution has worked for me and now I am able to add any properties and Visual Studio Code dont show up any warnings for them just like earlier.
Add this to your env.d.ts file in your Project Root Folder.
// env.d.ts
declare module '@vue/runtime-dom' {
    interface HTMLAttributes {
        [key: string]: any
    }
}

export { }

@lohchab I can't make it work on components

exactly. it might work for html elements but attribute fallthrough for components doesn't work at all

@lohchab I can't make it work on components
LIke on native components it works fine, but what about component attributes? I have VInput component which is just a wrapper around native input.

I got you. Yes, you are right I can confirm its is not working. Its only working for HTML Elements.
For a temporary workaround till the time there's a no solution to this my recommendation is that you switch your Volar Extension Version to the '0.35.2' and Restart the Visual Studio Code.

Until this is fixed, the proper solution is to revert this feature or hide it behind a flag and release a new version because in the current state it's just plane broken

@lohchab I can't make it work on components
LIke on native elements it works fine, but what about component attributes? I have VInput component which is just a wrapper around native input.

You should use AllowedComponentProps interface, please check updated example code.

// env.d.ts

// for native html elements
declare module '@vue/runtime-dom' {
    interface HTMLAttributes {
        [key: string]: any
    }
}

// for vue components
declare module '@vue/runtime-core' {
    interface AllowedComponentProps {
        [key: string]: any
    }
}

export { }

Thankyou @johnsoncodehk  I can confirm adding this code has solved the unknown property problems for both HTML and Vue Component Elements. Keep up the good work. We all appreciate what you are doing on Volar!

I agree that this type of strict linting should be opt-in, fallthrough attributes are a common use case with Vue and the default configuration of Volar should just work with the examples from the Vue docs.

This isn't just about fallthrough either, as shown in https://github.com/johnsoncodehk/volar/issues/1383 this is causing errors for many completely standard HTML attributes directly on the elements. It seems unreasonable requiring people to add custom declaration files to avoid that

Is it possible to make an option like mode="strict" to change default behavior? I mean, props existence check looks like an edge case than something default. Because everything that not described in props are custom attributes, that's vue default behavior

So i can't even make pure component wrapper to my button without adding env.d.ts 😄 Because this component don't have props at all

@johnsoncodehk Is it possible specify allowed attributes for specific component? Or only globally for all?

These changes may make some sense, however. Let's my IDE shows a warning if I use an attribute on a tag that doesn't have one. However, this is only a warning and it does not block the CI/CD.
Volar could introduce a similar, gentle check but only for vue components. However, it is also necessary to be able to describe individually for each component, which STML attributes are valid for it
<template>

		<button v-bind="$attrs"><slot/></button>

</template>

Imo this feature would be only useful if volar could analyze which element receives the attributes in the end. And only then, it can perform a check if that attribute is valid on that element. However, this is almost impossible to analyze statically because you can change where your attrs end up as you want.
It doesn't make sense to me to restrict passing attributes to a component because that basically takes away a lot free customizability (look at all attributes you can give to inputs for validation reasons. You don't want that as a prop).

FWIW, the fix outlined in the comment above related to updating the env.d.ts file is not working in my team's project. Unsure of the exact reasons, but one potential difference is our team is still using Vue 2 /w the composition API, so declaring types on @vue/runtime-core (and potentially even @vue/runtime-dom may not be working as expected.
Still trying to troubleshoot and find a more concrete reason why it's not working for us, but figured I'd share that in case other Vue 2 users are finding the fix is not working for them too.

In 0.36, custom / unknown attrs types behavior handle responsibility will transfer to developer.

Expand custom attrs example

<template>

</template>

// env.d.ts
declare module '@vue/runtime-dom' {
    interface HTMLAttributes {
        myprop: string
    }
}

export { }

Allow any attrs

// env.d.ts

// for native html elements
declare module '@vue/runtime-dom' {
    interface HTMLAttributes {
        [key: string]: any
    }
}

// for vue components
declare module '@vue/runtime-core' {
    interface AllowedComponentProps {
        [key: string]: any
    }
}

export { }

Not so great...

In 0.36, custom / unknown attrs types behavior handle responsibility will transfer to developer.

Expand custom attrs example

<template>

</template>

// env.d.ts
declare module '@vue/runtime-dom' {
    interface HTMLAttributes {
        myprop: string
    }
}

export { }

Allow any attrs

// env.d.ts

// for native html elements
declare module '@vue/runtime-dom' {
    interface HTMLAttributes {
        [key: string]: any
    }
}

// for vue components
declare module '@vue/runtime-core' {
    interface AllowedComponentProps {
        [key: string]: any
    }
}

export { }

It didn't work unfortunately as the project that I'm working on at the moment is using pure JavaScript without TypeScript, and the errors always appear.

Thanks to this feature, I noticed that the Vuetify property names had been updated and was able to correct them. :)
However, it took some work to resolve the issue. FYI:

I had to explicitly add @vue/runtime-core and @vue/runtime-dom to dependencies (probably because I am using pnpm)
The .d.ts file needs to be separate from the file defining vite's ImportMetaEnv (if exists)

For now, I use the following definition in env2.d.ts.
import '@vue/runtime-core';
import '@vue/runtime-dom';

// for vue components
declare module '@vue/runtime-core' {
  export interface AllowedComponentProps {
    [key: string]: any;
  }
}

// for native html elements
declare module '@vue/runtime-dom' {
  export interface HTMLAttributes {
    // allow any data-* attrs
    [key: `data${string}`]: string;
  }
}

export {};

Complex libraries such as Vuetify do not always have all properties defined (especially if they are passed through), and users will end up having to disable the feature completely.
The ideal solution would be for the type definitions of Vuetify components to be updated, but this is not always done quickly.
It seems difficult to use without at least a way to define additional attributes for individual components.

In v0.36.1 this behavior is control by vueCompilerOptions.experimentalSuppressUnknownJsxPropertyErrors and default enabled, if you want report unknown props you need config:
// tsconfig.json
{
  "vueCompilerOptions": {
    "experimentalSuppressUnknownJsxPropertyErrors": false
  }
}

If you see how volar hacking JSX types to ignore unknown prop errors you may want to disable it. (This shouldn't be part of volar's control)
https://github.com/johnsoncodehk/volar/blob/104af79387fec40ec3c9e82299f1258f1947673e/packages/vue-typescript/src/typescriptRuntime.ts#L282-L290

Can you make this disabled by default instead?
I still don't understand what the real point is, as this change breaks totally valid code all over the place for known attributes like all aria attributes.
I'm sure there's good intentions here, but people (especially new users) will have no idea what is going on when their data- attributes are throwing errors suddenly.

@TheDutchCoder Maybe there are some misunderstood, "SuppressUnknownJsxPropertyErrors" mean ignore unknown prop errors, I think you don't want disabled it by default.

Okay I'll give it a spin later.
Just to clarify: data- and aria- attributes are not unknown jsx attributes/properties.
So regardless of the setting, these should never throw errors, which was the original issue.

I can confirm that the update fixes all issues.  It is now opt-in as described above

As @TheDutchCoder said, data-* and aria-* are not unknown attributes, specially on "plain" html elements. They are standard W3C recommendations. The following piece of code is valid html and it should not throw an error regardless of the setting:
<template>
    <input aria-describedby="emailHelp">

aria help...

</template>

As @TheDutchCoder said, data-* and aria-* are not unknown attributes, specially on "plain" html elements. They are standard W3C recommendations. The following piece of code is valid html and it should not throw an error regardless of the setting:
<template>
    <input aria-describedby="emailHelp">

aria help...

</template>

Fix by ba2835fdcf233cad92bdd39519c0d723b7dee42e.

@johnsoncodehk
I still can't get this to work properly.
If I disable experimentalSuppressUnknownJsxPropertyErrors I still get errors thrown for data- and aria- attributes.
If I enable it, invalid attributes don't throw errors at all.
Example:
The data-test-id attribute should not throw an error, but the thisisnotvalid attribute should:

@TheDutchCoder if you don't have the option set, it's on by default. Which means volar behaves as if this feature wasn't enabled at all (its a feature flag). Nothing else was changed afaik.

This still doesn't solve anything.
Setting this to true means that unknown attributes (e.g. foo="bar") will go unchecked.
Setting this to false means that known attributes throw errors (e.g data-foo or aria-disabled).

I am unable to get this to work with the latest version.
vue-tsc 0.38.3 will report errors of unknown props like expected.
later versions reports no errors, even when it should.
I have tested 0.38.4, 0.38.5, 0.39.4
Can anyone confirm that this feature still works as expected?
if not then i suspect it broke in 0.38.4

@IceBlizz6 You should use vueCompilerOptions.strictTemplates, see https://github.com/johnsoncodehk/volar/blob/master/CHANGELOG.md#0384-2022711.


The parameter "xxx" must be defined.

symfony 3.2.2
last thormeier/breadcrumb-bundle
controller :
public function entrepriseViewAction(Entreprise $article, $slug) {

          $breadcrumbProvider = $this->get('thormeier.breadcrumb.breadcrumb_provider');
          $crumb = $breadcrumbProvider->getBreadcrumbByRoute('site_entreprise_view');
          $crumb->setRouteParams([ 'slug' => $article->getSlug(), ]);
          $crumb->setLabelParams([ 'name' => $article->getNom(), ]);
        return $this->render('SiteBundle:Default:entreprise-view.html.twig', array('article' => $article));
    }

route :
site_entreprise_view:
    path:     /entreprise-a-reprendre/{slug}
    defaults: { _controller: SiteBundle:Default:entrepriseView}
    options:
        breadcrumb:
            label: "Entreprise : %name% "
            parent_route: site_reprise

when i go on the page :
The parameter "name" must be defined.
i had forgot anything ?

Hi @NodokaMurmevent. I'm afraid that is an error in the docs. Since the default Twig template is using Twig's trans filter for replacing the label parameters, those need to be wrapped in % as well, like so:
$crumb->setLabelParams([ '%name%' => $article->getNom(), ]);

I'm actually not quite sure if we should keep it like this (i.e. just fix it in the docs) or add some kind of functionality to prepend and append % to the key, if not present already. What do you think?
Could you please also verify, that it works with '%name%' as array key?

i have try with %name% but it's change nothing for avoid this error i need to add  in parameter.yml name: test
but when i do this i have this error :
You have requested a non-existent service "thormeier.breadcrumb.breadcrumb_provider". Did you mean one of these: "thormeier.breadcrumb.breadcrumb_extension", "thormeier_breadcrumb.breadcrumb_provider.default"?

Ok, semms not like an issue with the translator then... Which version of the breadcrumb bundle are you using?

"thormeier/breadcrumb-bundle": "^2.1"

I've had a quick look and it indeed looks like the doc is outdated.
You should be using $this->get('thormeier_breadcrumb.breadcrumb_provider') instead of $this->get('thormeier.breadcrumb.breadcrumb_provider') since this service got renamed in 2.0.0 but unfortunately the doc wasn't updated. Does it work with the correct service ID?
Will fix README to contain the new DI naming.

ok now it's better, i also need to use  setRouteParameters and setLabelParameters and no setRouteParam or setLabelParam
          $crumb->setRouteParameters([ 'slug' => $article->getSlug(), ]);
          $crumb->setLabelParameters([ '%name%' => $article->getNom(), ]);

BUT i have always the same problem i need to add the parameter name in my parameter.yml, if i don't do this all my site have the error :
 The parameter "name" must be defined.

and my controller don't override the parameter for use the correct name with :
$crumb->setLabelParameters([ '%name%' => $article->getNom(), ]);
=> % <= it's change nothing.

The error message is coming from the Symfony container itself, therefore parameters.yml needs to contain this. I think we misunderstood that to begin with. Do you have the stack trace of the error message? Maybe we can figure out which part of the application is needing the parameter.

ok prepare for long text :D
Stack Trace
    in var/cache/dev/appDevDebugProjectContainer.php at line 6673  -
                $name = strtolower($name);
                if (!(isset($this->parameters[$name]) || array_key_exists($name, $this->parameters) || isset($this->loadedDynamicParameters[$name]))) {
                    throw new InvalidArgumentException(sprintf('The parameter "%s" must be defined.', $name));
                }
                if (isset($this->loadedDynamicParameters[$name])) {
                    return $this->loadedDynamicParameters[$name] ? $this->dynamicParameters[$name] : $this->getDynamicParameter($name);
    at appDevDebugProjectContainer ->getParameter ('name')
    in vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Routing/Router.php at line 153  +
    at Router ->Symfony\Bundle\FrameworkBundle\Routing\{closure} (array('%name%', 'name'))
    at preg_replace_callback ('/%%|%([^%\\s]++)%/', object(Closure), 'Entreprise : %name% ')
    in vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Routing/Router.php at line 167  +
    at Router ->resolve ('Entreprise : %name% ')
    in vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Routing/Router.php at line 131  +
    at Router ->resolve (array('route' => 'site_entreprise_view', 'label' => 'Entreprise : %name% '))
    in vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Routing/Router.php at line 131  +
    at Router ->resolve (array(array('route' => 'site_homepage', 'label' => 'Accueil'), array('route' => 'site_reprise', 'label' => 'Entreprise à reprendre'), array('route' => 'site_entreprise_view', 'label' => 'Entreprise : %name% ')))
    in vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Routing/Router.php at line 91  +
    at Router ->resolveParameters (object(RouteCollection))
    in vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Routing/Router.php at line 55  +
    at Router ->getRouteCollection ()
    in vendor/symfony/symfony/src/Symfony/Component/Routing/Router.php at line 371  +
    at Router ->getMatcherDumperInstance ()
    in vendor/symfony/symfony/src/Symfony/Component/Routing/Router.php at line 293  +
    at Router ->Symfony\Component\Routing\{closure} (object(ResourceCheckerConfigCache))
    at call_user_func (object(Closure), object(ResourceCheckerConfigCache))
    in vendor/symfony/symfony/src/Symfony/Component/Config/ResourceCheckerConfigCacheFactory.php at line 46  +
    at ResourceCheckerConfigCacheFactory ->cache ('/home/relancec/v2/relance/var/cache/dev/appDevDebugProjectContainerUrlMatcher.php', object(Closure))
    in vendor/symfony/symfony/src/Symfony/Component/Routing/Router.php at line 307  +
    at Router ->getMatcher ()
    in vendor/symfony/symfony/src/Symfony/Component/Routing/Router.php at line 260  +
    at Router ->matchRequest (object(Request))
    in vendor/symfony/symfony/src/Symfony/Component/HttpKernel/EventListener/RouterListener.php at line 101  +
    at RouterListener ->onKernelRequest (object(GetResponseEvent), 'kernel.request', object(TraceableEventDispatcher))
    at call_user_func (array(object(RouterListener), 'onKernelRequest'), object(GetResponseEvent), 'kernel.request', object(TraceableEventDispatcher))
    in vendor/symfony/symfony/src/Symfony/Component/EventDispatcher/Debug/WrappedListener.php at line 106  +
    at WrappedListener ->__invoke (object(GetResponseEvent), 'kernel.request', object(ContainerAwareEventDispatcher))
    at call_user_func (object(WrappedListener), object(GetResponseEvent), 'kernel.request', object(ContainerAwareEventDispatcher))
    in vendor/symfony/symfony/src/Symfony/Component/EventDispatcher/EventDispatcher.php at line 174  +
    at EventDispatcher ->doDispatch (array(object(WrappedListener), object(WrappedListener), object(WrappedListener), object(WrappedListener), object(WrappedListener), object(WrappedListener), object(WrappedListener), object(WrappedListener), object(WrappedListener), object(WrappedListener)), 'kernel.request', object(GetResponseEvent))
    in vendor/symfony/symfony/src/Symfony/Component/EventDispatcher/EventDispatcher.php at line 43  +
    at EventDispatcher ->dispatch ('kernel.request', object(GetResponseEvent))
    in vendor/symfony/symfony/src/Symfony/Component/EventDispatcher/Debug/TraceableEventDispatcher.php at line 136  +
    at TraceableEventDispatcher ->dispatch ('kernel.request', object(GetResponseEvent))
    in vendor/symfony/symfony/src/Symfony/Component/HttpKernel/HttpKernel.php at line 129  +
    at HttpKernel ->handleRaw (object(Request), 1)
    in vendor/symfony/symfony/src/Symfony/Component/HttpKernel/HttpKernel.php at line 68  +
    at HttpKernel ->handle (object(Request), 1, true)
    in vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php at line 168  +
    at Kernel ->handle (object(Request))
    in web/app_dev.php at line 30  +

**Logs  **
    INFO - User Deprecated: Duplicate key "twig" detected on line 202 whilst parsing YAML. Silent handling of duplicate mapping keys in YAML is deprecated since version 3.2 and will throw \Symfony\Component\Yaml\Exception\ParseException in 4.0.
    INFO - User Deprecated: Duplicate key "edit" detected on line 15 whilst parsing YAML. Silent handling of duplicate mapping keys in YAML is deprecated since version 3.2 and will throw \Symfony\Component\Yaml\Exception\ParseException in 4.0.
    INFO - User Deprecated: Duplicate key "new" detected on line 20 whilst parsing YAML. Silent handling of duplicate mapping keys in YAML is deprecated since version 3.2 and will throw \Symfony\Component\Yaml\Exception\ParseException in 4.0.
    INFO - User Deprecated: Not quoting the scalar "%glifery.entity_hidden_type.entity_form_type.class%" starting with the "%" indicator character is deprecated since Symfony 3.1 and will throw a ParseException in 4.0.
    INFO - User Deprecated: The Twig_Filter_Method class is deprecated since version 1.12 and will be removed in 2.0. Use Twig_SimpleFilter instead.
    INFO - User Deprecated: The Twig_Filter class is deprecated since version 1.12 and will be removed in 2.0. Use Twig_SimpleFilter instead.
    INFO - User Deprecated: Using an instance of "Twig_Filter_Method" for filter "slugify" is deprecated since version 1.21. Use Twig_SimpleFilter instead.
    INFO - User Deprecated: The Twig_Function_Method class is deprecated since version 1.12 and will be removed in 2.0. Use Twig_SimpleFunction instead.
    INFO - User Deprecated: The Twig_Function class is deprecated since version 1.12 and will be removed in 2.0. Use Twig_SimpleFunction instead.
    INFO - User Deprecated: Using an instance of "Twig_Function_Method" for function "slugify" is deprecated since version 1.21. Use Twig_SimpleFunction instead.
    INFO - User Deprecated: Using an instance of "Twig_Function_Method" for function "asset_exists" is deprecated since version 1.21. Use Twig_SimpleFunction instead.
    INFO - User Deprecated: Using an instance of "Twig_Filter_Method" for filter "ladybug_dump" is deprecated since version 1.21. Use Twig_SimpleFilter instead.
    INFO - User Deprecated: Using an instance of "Twig_Filter_Method" for filter "ld" is deprecated since version 1.21. Use Twig_SimpleFilter instead.
    INFO - User Deprecated: Using an instance of "Twig_Function_Method" for function "ladybug_dump" is deprecated since version 1.21. Use Twig_SimpleFunction instead.
    INFO - User Deprecated: Using an instance of "Twig_Function_Method" for function "ld" is deprecated since version 1.21. Use Twig_SimpleFunction instead.
    INFO - User Deprecated: Defining the initRuntime() method in the "Slugify_Twig_Extension" extension is deprecated since version 1.23. Use the `needs_environment` option to get the Twig_Environment instance in filters, functions, or tests; or explicitly implement Twig_Extension_InitRuntimeInterface if needed (not recommended).
    INFO - User Deprecated: The value "France" for SLLH\IsoCodesValidator\Constraints\ZipCode::country options is deprecated since version 1.1 and will be removed in 2.0. Use FR instead.
    INFO - User Deprecated: The value "France" for SLLH\IsoCodesValidator\Constraints\ZipCode::country options is deprecated since version 1.1 and will be removed in 2.0. Use FR instead.
    INFO - User Deprecated: The value "France" for SLLH\IsoCodesValidator\Constraints\ZipCode::country options is deprecated since version 1.1 and will be removed in 2.0. Use FR instead.
    INFO - User Deprecated: The value "France" for SLLH\IsoCodesValidator\Constraints\ZipCode::country options is deprecated since version 1.1 and will be removed in 2.0. Use FR instead.
    INFO - User Deprecated: The value "France" for SLLH\IsoCodesValidator\Constraints\ZipCode::country options is deprecated since version 1.1 and will be removed in 2.0. Use FR instead.
    CRITICAL - Uncaught PHP Exception Symfony\Component\DependencyInjection\Exception\InvalidArgumentException: "The parameter "name" must be defined." at /home/relancec/v2/relance/var/cache/dev/appDevDebugProjectContainer.php line 6673

Stack Trace (Plain Text)
[1] Symfony\Component\DependencyInjection\Exception\InvalidArgumentException: The parameter "name" must be defined.
    at n/a
        in /home/relancec/v2/relance/var/cache/dev/appDevDebugProjectContainer.php line 6673

    at appDevDebugProjectContainer->getParameter('name')
        in /home/relancec/v2/relance/vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Routing/Router.php line 153

    at Symfony\Bundle\FrameworkBundle\Routing\Router->Symfony\Bundle\FrameworkBundle\Routing\{closure}(array('%name%', 'name'))
        in  line

    at preg_replace_callback('/%%|%([^%\\s]++)%/', object(Closure), 'Entreprise : %name% ')
        in /home/relancec/v2/relance/vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Routing/Router.php line 167

    at Symfony\Bundle\FrameworkBundle\Routing\Router->resolve('Entreprise : %name% ')
        in /home/relancec/v2/relance/vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Routing/Router.php line 131

    at Symfony\Bundle\FrameworkBundle\Routing\Router->resolve(array('route' => 'site_entreprise_view', 'label' => 'Entreprise : %name% '))
        in /home/relancec/v2/relance/vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Routing/Router.php line 131

    at Symfony\Bundle\FrameworkBundle\Routing\Router->resolve(array(array('route' => 'site_homepage', 'label' => 'Accueil'), array('route' => 'site_reprise', 'label' => 'Entreprise à reprendre'), array('route' => 'site_entreprise_view', 'label' => 'Entreprise : %name% ')))
        in /home/relancec/v2/relance/vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Routing/Router.php line 91

    at Symfony\Bundle\FrameworkBundle\Routing\Router->resolveParameters(object(RouteCollection))
        in /home/relancec/v2/relance/vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Routing/Router.php line 55

    at Symfony\Bundle\FrameworkBundle\Routing\Router->getRouteCollection()
        in /home/relancec/v2/relance/vendor/symfony/symfony/src/Symfony/Component/Routing/Router.php line 371

    at Symfony\Component\Routing\Router->getMatcherDumperInstance()
        in /home/relancec/v2/relance/vendor/symfony/symfony/src/Symfony/Component/Routing/Router.php line 293

    at Symfony\Component\Routing\Router->Symfony\Component\Routing\{closure}(object(ResourceCheckerConfigCache))
        in  line

    at call_user_func(object(Closure), object(ResourceCheckerConfigCache))
        in /home/relancec/v2/relance/vendor/symfony/symfony/src/Symfony/Component/Config/ResourceCheckerConfigCacheFactory.php line 46

    at Symfony\Component\Config\ResourceCheckerConfigCacheFactory->cache('/home/relancec/v2/relance/var/cache/dev/appDevDebugProjectContainerUrlMatcher.php', object(Closure))
        in /home/relancec/v2/relance/vendor/symfony/symfony/src/Symfony/Component/Routing/Router.php line 307

    at Symfony\Component\Routing\Router->getMatcher()
        in /home/relancec/v2/relance/vendor/symfony/symfony/src/Symfony/Component/Routing/Router.php line 260

    at Symfony\Component\Routing\Router->matchRequest(object(Request))
        in /home/relancec/v2/relance/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/EventListener/RouterListener.php line 101

    at Symfony\Component\HttpKernel\EventListener\RouterListener->onKernelRequest(object(GetResponseEvent), 'kernel.request', object(TraceableEventDispatcher))
        in  line

    at call_user_func(array(object(RouterListener), 'onKernelRequest'), object(GetResponseEvent), 'kernel.request', object(TraceableEventDispatcher))
        in /home/relancec/v2/relance/vendor/symfony/symfony/src/Symfony/Component/EventDispatcher/Debug/WrappedListener.php line 106

    at Symfony\Component\EventDispatcher\Debug\WrappedListener->__invoke(object(GetResponseEvent), 'kernel.request', object(ContainerAwareEventDispatcher))
        in  line

    at call_user_func(object(WrappedListener), object(GetResponseEvent), 'kernel.request', object(ContainerAwareEventDispatcher))
        in /home/relancec/v2/relance/vendor/symfony/symfony/src/Symfony/Component/EventDispatcher/EventDispatcher.php line 174

    at Symfony\Component\EventDispatcher\EventDispatcher->doDispatch(array(object(WrappedListener), object(WrappedListener), object(WrappedListener), object(WrappedListener), object(WrappedListener), object(WrappedListener), object(WrappedListener), object(WrappedListener), object(WrappedListener), object(WrappedListener)), 'kernel.request', object(GetResponseEvent))
        in /home/relancec/v2/relance/vendor/symfony/symfony/src/Symfony/Component/EventDispatcher/EventDispatcher.php line 43

    at Symfony\Component\EventDispatcher\EventDispatcher->dispatch('kernel.request', object(GetResponseEvent))
        in /home/relancec/v2/relance/vendor/symfony/symfony/src/Symfony/Component/EventDispatcher/Debug/TraceableEventDispatcher.php line 136

    at Symfony\Component\EventDispatcher\Debug\TraceableEventDispatcher->dispatch('kernel.request', object(GetResponseEvent))
        in /home/relancec/v2/relance/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/HttpKernel.php line 129

    at Symfony\Component\HttpKernel\HttpKernel->handleRaw(object(Request), 1)
        in /home/relancec/v2/relance/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/HttpKernel.php line 68

    at Symfony\Component\HttpKernel\HttpKernel->handle(object(Request), 1, true)
        in /home/relancec/v2/relance/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php line 168

    at Symfony\Component\HttpKernel\Kernel->handle(object(Request))
        in /home/relancec/v2/relance/web/app_dev.php line 30

After some debuging, I guess I found the issue... The BreadcrumbAttachLoader takes the crumb information from the options: key and puts them in the Routes defaults to get Symfony to cache them, so they don't need to be parsed out on every request. (Symfony doesn't cache options: afaik, but only defaults:, so this workaround was necessary)
Those defaults are then, in turn, sent through a resolve method, that tries to find parameters (strings with % surrounding them) and tries to fetch those from the container directly, which is not the behaviour we want here.
As a quick workaround I suggest you replace the label with a translation key and put the label in your messages.[insert language code here].yml file, so the router doesn't think there's a parameter at all in there anymore.
In the meantime I'm working on a solution for this issue.

@NodokaMurmevent Thank you very much for reporting this issue.
I had a talk with @tobion about this and he suggested that one could replace %name% with %%name%%, because the Syamfony container, which parses all the routing files as well, actually sees %name% as a container parameter and tries to replace it. %% therefore escapes the %. I've added a fix to the standard template to handle %% by replacing them with % to get past the container behaviour and still have the advantages of Twig translations.
c763702 contains the fix. Could you please test if this commit fixes the bug by replacing % with %% in your route label?

It's work ! I have add your commit in my local vendor and with
my route :
site_entreprise_view:
    path:     /entreprise-a-reprendre/{slug}
    defaults: { _controller: SiteBundle:Default:entrepriseView}
    options:
        breadcrumb:
            label: "Entreprise : %%name%%"
            parent_route: site_reprise

and my controller :
    public function entrepriseViewAction(Entreprise $article, $slug) {

          $breadcrumbProvider = $this->get('thormeier_breadcrumb.breadcrumb_provider');
          $crumb = $breadcrumbProvider->getBreadcrumbByRoute('site_entreprise_view');
          $crumb->setRouteParameters([ 'slug' => $article->getSlug(), ]);
          $crumb->setLabelParameters([ '%name%' => $article->getNom(), ]);
        return $this->render('SiteBundle:Default:entreprise-view.html.twig', array('article' => $article));
    }

no more problem or error 👍

Wonderful! I'll update the missing doc and tag a minor release then, thank you very much :) Will close the issue once the release is tagged.

@NodokaMurmevent Tagged release 2.1.4, feel free to install. Will close this issue now, thanks for helping out!

Sorry for opening this again, but the fix with the double "%" doesn't seem to work when using annotation:
/**
@Route("/my-route/{id}", name="my_route_name",options={"breadcrumb" = {
	 *            "label" = "%%name%%",
	 *            "parent_route" = "parent_route"
	 *        }})
	 */
	public function editAction( Request $request, MyObj $obj ) {
		$this->breadcrumbProvider
			->getBreadcrumbByRoute( 'parent_route' )
			->setRouteParameters( array(
				'id' => $strutturaFormativa->getId(),
			) )
			->setLabelParameters( array(
				"%name%" => $obj->getName(), // doesn't work
				"name"   => $obj->getName(), // doesn't work too
			) );

Any suggestion? i don't really want to start using routing.yml now, i love annotations


Feature/simplified build

Simplify build, so it is hardly dependent on developer actions or OS. THis was mostly achieved by commiting to the npm scripts as core build engine. What remains is the manual (outside npm scripts) step to install the libUV dependency (e.g. by miniforge3).
Then, introduce github action to actually build releases.

closing in favor of https://github.com/TNG/AI-Playground/pull/2 : adjusted target and rebased.


No summary text in evidence responses

Here is evidence 54e7712b38da0d6e9a000004 for example:
HTTP/1.1 200 OK
Connection: keep-alive
Content-Encoding: gzip
Content-Type: application/hal+json
Date: Fri, 20 Feb 2015 19:03:45 GMT
Keep-Alive: timeout=20
Server: nginx/1.4.6 (Ubuntu)
Transfer-Encoding: chunked
Vary: Accept-Encoding

{
    "evidence": [
        {
            "_links": {
                "collection": {
                    "href": "http://next.belframework.org/api/evidence",
                    "type": "evidence-collection"
                },
                "self": {
                    "href": "http://next.belframework.org/api/evidence/54e7712b38da0d6e9a000004",
                    "type": "evidence"
                }
            },
            "bel_statement": "p(evidence) increases p(canBeCreated)",
            "biological_context": [
                {
                    "name": "Species",
                    "value": [
                        9606,
                        10090
                    ]
                },
                {
                    "name": "Cell",
                    "value": [
                        "fibroblast",
                        "leukocyte"
                    ]
                }
            ],
            "citation": {
                "id": "10022765",
                "name": "None",
                "type": "PubMed"
            },
            "metadata": {
                "status": "draft"
            }
        }
    ]
}

Confirmed fixed and :+1: on the 7 minute response time. Have a :beer: on me.
We (Selventa/OpenBEL) need to start a contest for quickest turn-around from issue creation to fixed in production, because we're that good.

What :bug:? You didn't see anything (waves hands).


[Storage] Remove playback only annotation on STG 74 features that have not fully rolled out

Hi @seanmcc-msft, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.


remove unnecessary YAML files from the repo

These YAML files were generated a long-time ago and are not part of the
codegen.

Here is what I did:
rm -rf config
make generate
# commit and push this PR

There are a lot of  YAMLs currently in the config that make little sense and add to confusion.

Thanks!
/lgtm
/assign @bowei

/approve


Render Tooltip via React Portal

What:

In this PR we're adding a new prop container to the Tooltip component where the tooltip should be rendered into.

Why:

This PR closes #349.
Tooltips that are rendered in Modal dialogs can cause scrollbars to appear. It was not like that in previous version of wave (1.15.1).
How:

Introduce new (optional) prop container to Tooltip component where the tooltip body should be rendered into
Render the tooltip body into container via react portal
See internal discussion
Implementation according to popper library documentation

Media:

Before:

After:

Checklist:

[ ] Ready to be merged

What do you think if we create a portal by default and attach it to the document.body?
Our users won't even face the issue anymore in that case, the whole issue disappear. I don't see any negative sides on this solution

Good idea. We would need to put a big enough z-index on the tooltip then so that it gets rendered on top of modals. With my changes the responsibility for that is delegated to the user of the library which is not very convenient. I agree that it would be better if the library makes sure that it "just works".

create a portal by default
Do you mean using document.body as portal to render tooltips in any case instead of doing it conditionally? In that case we could remove the container prop.

Do you mean using document.body as portal to render tooltips in any case instead of doing it conditionally? In that case we could remove the container prop.

Yes, I'd do that. In that case the z-index won't gonna be necessary because the tooltip will be sitting on top of the tree and in a separate stacking context

The issue is that Modals come with z-index: 1100 which makes them appear on top of elements that are rendered in a separate stacking context (see example).

The issue is that Modals come with z-index: 1100 which makes them appear on top of elements that are rendered in a separate stacking context (see example).

I've removed the container prop in 94b053c. Tooltips are rendered via React Portal into document.body now.


Customize the menu

Hi,
I am wondering how to customize the menu such as the dropdown menu?

@raheems That's not currently customizable but I'll fix that.

@raheems Okay, I've updated it to allow for a customizable navbar. You can see how here.

The navbar-clone needs to reflect the changes as well 👍

Feel free to submit a pull request


Revised request API

Revised request(many) API based on #75
Also added start-up timer as per ADR-40. It's the max time to wait for the first message.

Are we happy with the public interface i.e. NatsSub and Request*Async?

I had doubts about the options being passed to Request but I can see the value of not littering the API with too many types.

RequestMany returning async enumerator forces the developer to use await foreach. Returning a type with a channel e.g. NatsSub may be a better option.

For the Request options - we need a way to pass Queue Group, Headers, and a Serializer when using Model types.  So the only thing missing from PubOpts is the ReplySubject which is defaulted.
For the Reply options of the RequestAsync methods we could cut those down, as many of the timeouts do not apply when waiting for a single reply.  Or we could document that they have no effect when waiting for a single reply.
For the Reply options of RequestManyAsync - this pretty much does need to be the full set of NatsSubOpts
I think that returning NatsSub is fine for the RequestManyAsync methods

For the Request options - we need a way to pass Queue Group and Headers when not using Model types. So the only thing missing from NatsPubOpts is the ReplySubject which is defaulted.

see comment above

For the Reply options of the RequestAsync methods we could cut those down, as many of the timeouts do not apply when waiting for a single reply. Or we could document that they have no effect when waiting for a single reply.

I'm happy with documenting it. Changed my mind a little. Maybe it's better to keep Type footprint to a minimum. Also, in my opinion at this level of the API it's better to give clues that under the bonnet it is still a pub/sub powering the request reply pattern. We can certainly wrap this later with a much more opinionated/easy/lite API for less demanding applications.

For the Reply options of RequestManyAsync - this pretty much does need to be the full set of NatsSubOpts

Agreed.

I think that returning NatsSub is fine for the RequestManyAsync methods

I was thinking to wrap this PR up as a smaller step and discuss this on a some kind of 'internal redesign' PR. Happy to carry on here though if you like.

I was thinking to wrap this PR up as a smaller step and discuss this on a some kind of 'internal redesign' PR

That sounds good!


Cache settings?

Hi, what are the recommended cache settings for this add-on? When 'cache all' is set on the C5 system, the pop-up notification keeps re-appearing on the same page even after clicking the button.

The block should not be used with full-page caches, since its output depends on every specific visit.


when where you release the code?

Thank you for your interest in this method. Our paper has just been submitted, and it may be a while before the code is released.


Add page number functionality

Stumbled upon this today and it is just what I needed! Thank you for this!
I was wondering if page number buttons can be added next to the "First Commit" button (or the "First Commit" button can be replaced by a button for the last page number), something like the numbers at the footer of Google search results. This would make scrolling through the commits a bit faster. An input box can even be added where users can enter the desired page number. I would be happy to create a pull request for this!
As an aside, I thought the three buttons "Previous", "First Commit", and "Next" could be centered a bit better; they look to be leaning a bit to the right as it stands. I could add this to a pull request as well.

Yo! Happy to hear you found this useful!
Yeah why not, adding page numbers might be a nice enhancement. I don't usually have the need to jump between pages like that, the goal was mostly to just find the first commit to see how old the code base is. But I'm open to this!
Absolutely, any PR is welcome, especially for fixing layout and making the buttons nicer! I wouldn't have guessed it would be off center since I'm just adding a new button between them in the DOM but maybe I'm doing something weird. Feel free to fix it!

Great! I'll get started on it soon~


Drive collection via WMI doesn't include mount points

Drive collection via SQL includes mount points if a SQL file exists on the mount point.  Collection via WMI doesn't include mount points.  The Win32_Volume class used can return this data but it's filtered to show only drives with a drive letter.

Fix is now in the latest release


Desync animations

Hello, I’ve just ported your mod (the 1.12 version) to be compatible with Minecraft 1.8.9, but I’m encountering an issue when my custom mob ticks.
Occasionally, the animations glitch and desynchronize, which results in the mob behaving erratically.
Btw I'm in survival, and not using the server sync method.
My Entity class : https://i.courat.eu/gsNQQxXFla.png
Here’s some proof of the duplicated model issue: https://i.courat.eu/7g3qqGFGwK.mp4, https://i.courat.eu/Hj9OmM36f8.mp4

Sounds unrelated to us
If you've ported your own version, you're responsible for your own bugs


KinematicBody get_floor_velocity() inconsistent result

Godot version
3.4 Beta 3
System information
Windows 10, NVIDIA GTX 750TI, GLES3
Issue description
when doing moving and rotating platform by adding get_floor_velocity to velocity, returned values difference breaks either moving or rotating platform depend if times with delta or not. It works correctly in 3.3.3
in Godot 3.4 Beta 3
moving platform : velocity + get_floor_velocity() * delta
rotating platform : velocity + get_floor_velocity()
in Godot 3.3.3 both platforms works with
velocity + get_floor_velocity() * delta
Steps to reproduce
Create 2 platform, for moving and rotating platform. Animate them using animation player
Make kinematicbody with script
put both kinematic body on top of platform
`extends KinematicBody
var velocity = Vector3()
Called when the node enters the scene tree for the first time.
func _ready():
pass # Replace with function body.
func _physics_process(delta):
if is_on_floor():
	velocity = (Vector3.DOWN * 0.1) + (get_floor_velocity() * delta)
	#TO MAkE ROTATING PLATFORM WORK, REPLACE WITH
	#velocity = (Vector3.DOWN * 0.1) + (get_floor_velocity())
	#BUT THEN MOVING PLATFORM WILL BREAK
else:
	velocity = Vector3.DOWN

var _vel = move_and_slide(velocity, Vector3.UP)`

Minimal reproduction project
br_get_floor_velocity.zip
In 3.4 Beta 3 kinematic body failed to follow rotating platform
In 3.3.3 it works fine

cc @pouleyKetchoupp

Closing as duplicate of #51047, this is fixed in 3.4 Beta 4.
Also for info:

You don't need to apply any floor velocity in your script, it's already done automatically in move_and_slide.
So in the floor case, you can just apply velocity = Vector3.DOWN * 0.1.
In order to improve the results for the moving platform, you can also set your AnimationPlayer playback mode to Physics instead of Idle. It will help getting things well synchronized.
In 3.4 you can also enable motion/sync_to_physics for the platforms. It can help keeping the platform in sync when the direction changes.


vision 0.32.0 again overwrites 'module' for shared proto message types

See https://github.com/GoogleCloudPlatform/google-cloud-python/pull/5467#pullrequestreview-127747194

I'm going to close this for now, once the generator issue is addressed we'll regenerate everything.


embed visualizer in pyqt widget

Primary issue to sort out was that pyqtgraph uses QtCore.QTimer as does PyQt6. A big of a dangerous naming convention, but it seems to be sorted out now...

A quick update that will hopefully pave the way to more careful inspection of triangulated data.


v1.9 backports 2020-10-19

#13613 -- bpf: simplify local redirect a bit for sock lb (@borkmann)
#13244 -- lbmap: Correct issue that port info display error (@Jianlin-lv)
#13664 -- smoketest: Add image tag as latest for cilium agent and operator (@sayboras)

Once this PR is merged, you can update the PR labels via:
$ for pr in 13613 13244 13664; do contrib/backporting/set-labels.py $pr done 1.9; done

test-backport-1.9

test-backport-1.9


The application Keybase has closed unexpectedly

Every time I open the keybase app I am prompted with this message, perhaps it isn't quitting gracefully on shutdown or reboot?
The details state:

Keybase crashed with signal 5

Ubuntu 19.10
Keybase 4.8.0-20191021160049+e5fcade9ba

Sorry about that. This is a known issue with Electron 6: https://github.com/electron/electron/issues/20509. You could add your debug logs to that issue.

I see, thanks @heronhaye I'll close this as a duplicate in the meantime then.


Add Zooming Capability in Timelines

To mimic the functionality had in Highcharts, it would be nice to implement zooming in timelines (line charts) in Chartist.js.
This will likely be an upstream patch to the original project.

I could also use dygraphs specifically for the time series data. That allows zooming, but it would be difficult to make the look consistent.

With gophish going completely free (for good) I'm going to move back to highcharts. That move will resolve this issue, so I'm going to close this for now.


Blinded Messages naming consitancy

In some places they are called outputs. Should be consistent within the project

Part of #51


cplex: download url for source package is outdated, package not compatible with newer versions

Steps To Reproduce
Steps to reproduce the behavior:

Install pkgs.cplex.
Read error message.
Try to download https://developer.ibm.com/docloud/blog/2017/12/20/cplex-optimization-studio-12-8-now-available/
not reachable
Find different cplex version on IBM page, 22.1.0.
Try to build package with that cplex version

Build log
building '/nix/store/918fqvjh5kx6bnq4wm5f2hd3m76q2wnr-cplex-128.drv'...
unpacking sources
patching sources
configuring
no configure script, doing nothing
building
JRE libraries are missing or not compatible....
Exiting....
glibPreInstallPhase
installing
dropIconThemeCache
glibPreFixupPhase
post-installation fixup
patchelf: getting info about '/nix/store/ax58hfnrw0wh11knmxbx4mgsfv3hdpxp-cplex-128/opl/bin/x86-64_linux/oplrun': No such file or directory
builder for '/nix/store/918fqvjh5kx6bnq4wm5f2hd3m76q2wnr-cplex-128.drv' failed with exit code 1

Notify maintainers

Dear @bfortz I notice this package hasn’t been touched in a while, maybe you have moved on. But any hints how you would approach getting a working cplex, no matter the version, would be greatly appreciated.
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
system: "x86_64-linux"
host os: Linux 5.10.126, NixOS, 21.11 (Porcupine)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.16
channels(root): "nixos-21.11.337967.573603b7fdb, unstable-22.05pre379159.dfd82985c27"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Last version I checked was 12.10 and it was still working. I will look into it when I find some time.

Thanks for the reply.
For our specific situation we settled on a docker based solution, which works better for the usecase anyway, so there is no hurry.

I am currently experiencing the same error. When using the latest version of CPLEX (which is, to my knowledge, 22.11), I get the following error:
~ nix-shell -p cplex
this derivation will be built:
  /nix/store/mxf2wi28qvv61pr6b0ipssr884mzz6gc-cplex-128.drv
building '/nix/store/mxf2wi28qvv61pr6b0ipssr884mzz6gc-cplex-128.drv'...
Running phase: unpackPhase
Running phase: patchPhase
Running phase: updateAutotoolsGnuConfigScriptsPhase
Running phase: configurePhase
no configure script, doing nothing
Running phase: buildPhase
Error: Could not find or load main class com.zerog.lax.LAX
Caused by: java.lang.ClassNotFoundException: com.zerog.lax.LAX
error: builder for '/nix/store/mxf2wi28qvv61pr6b0ipssr884mzz6gc-cplex-128.drv' failed with exit code 1;
       last 8 log lines:
       > Running phase: unpackPhase
       > Running phase: patchPhase
       > Running phase: updateAutotoolsGnuConfigScriptsPhase
       > Running phase: configurePhase
       > no configure script, doing nothing
       > Running phase: buildPhase
       > Error: Could not find or load main class com.zerog.lax.LAX
       > Caused by: java.lang.ClassNotFoundException: com.zerog.lax.LAX
       For full logs, run 'nix log /nix/store/mxf2wi28qvv61pr6b0ipssr884mzz6gc-cplex-128.drv'.

It was working with CPLEX Version 20.10 on NixOS 23.11, but with the update to NixOS 24.05 I now get the below error. I guess this is due to an updated java dependency, which is incompatible with the CPLEX Version.
~ nix-shell -p cplex
this derivation will be built:
  /nix/store/74rblwrqb245kkm4p525rahnzapfj6pl-cplex-128.drv
building '/nix/store/74rblwrqb245kkm4p525rahnzapfj6pl-cplex-128.drv'...
Running phase: unpackPhase
Running phase: patchPhase
Running phase: updateAutotoolsGnuConfigScriptsPhase
Running phase: configurePhase
no configure script, doing nothing
Running phase: buildPhase
JRE libraries are missing or not compatible....
Exiting....
Running phase: glibPreInstallPhase
Running phase: installPhase
Running phase: dropIconThemeCache
Running phase: glibPreFixupPhase
Running phase: fixupPhase
patchelf: getting info about '/nix/store/ipr15pyg66wngwc88rrvlysq3w2mznm9-cplex-128/opl/bin/x86-64_linux/oplrun': No such file or directory
error: builder for '/nix/store/74rblwrqb245kkm4p525rahnzapfj6pl-cplex-128.drv' failed with exit code 1;
       last 10 log lines:
       > no configure script, doing nothing
       > Running phase: buildPhase
       > JRE libraries are missing or not compatible....
       > Exiting....
       > Running phase: glibPreInstallPhase
       > Running phase: installPhase
       > Running phase: dropIconThemeCache
       > Running phase: glibPreFixupPhase
       > Running phase: fixupPhase
       > patchelf: getting info about '/nix/store/ipr15pyg66wngwc88rrvlysq3w2mznm9-cplex-128/opl/bin/x86-64_linux/oplrun': No such file or directory
       For full logs, run 'nix log /nix/store/74rblwrqb245kkm4p525rahnzapfj6pl-cplex-128.drv'.


Upgrade OpenCSV and Commons Lang / Text

Major upgrade: from opencsv 4.3 to 5.1 4.6
May also allow to upgrade apache commons-text from 1.3 to 1.8 and commons-lang3 from 3.8 to 3.9

[x] CQ21761 OpenCSV 5.1
[x] CQ20736 OpenCSV 4.6 (no requirement to file PB's anymore)
[x] CQ21762 Apache Commons Lang 3.9
[x] CQ21867 Apache Commons Text 1.8

Can't upgrade to 5.1 yet, because 5.x changes the number of arguments of the com.opencsv.bean.BeanField interface, and this is used in a (be it deprecated) public method in
org.eclipse.rdf4j.query.resultio.text.SPARQLResultsXSVMappingStrategy
So aim for 4.6 instead.


Proposal for allowing nowatchdirs

(Just for reference, this fixes #6.)

Going the fix in #11 instead due to the concerns raised by @aldanor in b4135b7bacb062e4d44d038c6a9cf7a5d93b3c07. Feel free to jump into the discussion if you want. We'll probably be figuring out how to improve --ignore / --norecursedirs in a new issue.
Thank you, @poulter7!


Rewrite lexer to use memory arena instead of fixed-size char buffer.

See #1 for information. There is actual usage of memory arena (StringArena global) which has to be used in lexer.

Done  9e06fe0


Is there a way to obtain current playback level?

I want to know current level, but playback.currentLevel is always -1 when set to "auto"
I can take the info from PLAYBACK_BITRATE event, but it seems to be not always accurate when playback.currentLevel is set manually. And I'd like to know that without waiting for the quality to change.
Is there a way to obtain actual playback level at every moment?

@sapolio the only way to have the current playback level is to use the PLAYBACK_BITRATE event.
Since you're having issues with it not being accurate when the playback.currentLevel is set manually, I recommend using a mixed approach: use playback.currentLevel and if it's set to -1, use the one from the PLAYBACK_BITRATE event.

-1 is equal to auto


ovnkube-trace can't be run on image version 4.13 and above

Using latest or 4.13 image quay.io/openshift/origin-network-tools, ovnkube-trace doesn't work failing with:
sh-4.4# ovnkube-trace -help
ovnkube-trace: /lib64/libc.so.6: version GLIBC_2.32' not found (required by ovnkube-trace) ovnkube-trace: /lib64/libc.so.6: version GLIBC_2.34' not found (required by ovnkube-trac

Would it be possible for us to fix this? Special for 4.14 image I think it is very important for us to fix this so customers can have a working image to use ovnkube-trace.


ModuleNotFoundError: No module named 'tensorflow.contrib'

Hi All,
When I run the chat_console_best_weights_training.bat, the program gives error like below.
ModuleNotFoundError: No module named 'tensorflow.contrib'
I researched it, and I gave a decision for it, I kindly suggest that you wrote pip upgrade tensorflow,
but after 2.0 version of tensorflow, 'contrib' version is removed from lib.
Could you help me for this issue?
Best Reggards.

Hi @halilural - Thanks for pointing this out. The project only works with TF 1.x line for now. I will update the readme accordingly.


[do-not-merge] Verify Webpack Config Changes

Summary
This PR verifies webpack configuration changes.

Closing, testing no longer needed.


Update Transactions list layout

Changes:

Add asset coin icon

Make amount in white color and place near assets icon

Remove Text "Send" and "'Receive. Leave only colored status+icon

Make USD/BTC amount 80% white color.

DAPPS/Contracts transactions.

If there are only 2 assets - display BEAM (as default coin) and "+1" (as second example on screenshot)
If there 3+ assets - display BEAM (as default coin) and "+2" (as first example on screenshot). If there is no BEAM - display biggest amount first.

Transaction details https://zpl.io/2GjDGKm

Updated statuses for MULTIPLY ASSETS https://zpl.io/b6xJ58q

Current design:

Updated design:

Checked.


Create an API for consume new messages

https://github.com/csarcom/python-pubsub/commit/7c3db5747bd22e91fae76e88643ee26f544c5b34


FR: support faster-whisper

https://github.com/guillaumekln/faster-whisper this is way faster than the original implementation. It's already done the job addressed by https://github.com/mli/autocut/issues/22#issuecomment-1333486727. Also #63 and #73 are somewhat useless solved with this one done @yihong0618 @zcf0508

I will take this issue.
Here is my faster-whisper colab for test: https://github.com/lewangdev/faster-whisper-youtube

whisper 和 faster-whisper 接口和依赖不同，我的实现做了以下修改，感觉不适合发 PR 了

cpu 模式下，去掉了并发
cuda 模式下，需要安装 cuBLAS 11.x 和 cuDNN 8.x
改写完之后目前 unit test 有一个失败

faster-whisper 的版本：
https://github.com/lewangdev/autocut

https://github.com/mli/autocut/pull/94


netcoreapp3.0  console app doesn't recognize files/references correctly

Issue Description
A simple 'dotnet new console' app targeting 'netcoreapp3.0' doesn't reference files correctly. If I switch back to 'netcoreapp2.2' it works as expected. 'dotnet restore' doesn't help.

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>netcoreapp3.0</TargetFramework>
  </PropertyGroup>
</Project>

I have tried setting omnisharp.useglobalmono to never - but it doesn't make any difference.
The OmniSharp log says this at the end after restore:
[warn]: OmniSharp.MSBuild.PackageDependencyChecker
TestNetCoreIssue: Did not find 'Microsoft.NETCore.App' in lock file.
Logs
OmniSharp log

[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for 'c:\Dev\eco\TestNetCoreIssue\TestNetCoreIssue.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for 'c:\Dev\eco\TestNetCoreIssue\TestNetCoreIssue.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: c:\Dev\eco\TestNetCoreIssue\TestNetCoreIssue.csproj
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file 'c:\Dev\eco\TestNetCoreIssue\TestNetCoreIssue.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: TestNetCoreIssue
[warn]: OmniSharp.MSBuild.PackageDependencyChecker
        TestNetCoreIssue: Did not find 'Microsoft.NETCore.App' in lock file.

Environment information
VSCode version: 1.33.1
C# Extension: 1.19.1
Dotnet Information
.NET Core SDK (reflecting any global.json):
 Version:   3.0.100-preview4-011223
 Commit:    118dd862c8
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.17763
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\3.0.100-preview4-011223\
Host (useful for support):
Version: 3.0.0-preview4-27615-11
Commit:  ee54d4cbd2
.NET Core SDKs installed:
2.1.2 [C:\Program Files\dotnet\sdk]
2.1.4 [C:\Program Files\dotnet\sdk]
2.1.104 [C:\Program Files\dotnet\sdk]
2.1.200 [C:\Program Files\dotnet\sdk]
2.1.201 [C:\Program Files\dotnet\sdk]
2.1.202 [C:\Program Files\dotnet\sdk]
2.1.400 [C:\Program Files\dotnet\sdk]
2.1.402 [C:\Program Files\dotnet\sdk]
2.1.403 [C:\Program Files\dotnet\sdk]
2.1.502 [C:\Program Files\dotnet\sdk]
2.2.104 [C:\Program Files\dotnet\sdk]
3.0.100-preview4-011223 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.0.0-preview4-19216-03 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.0.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.0.0-preview4-27615-11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.0.0-preview4-27613-28 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download

Visual Studio Code Extensions

Extension
Author
Version

csharp
ms-vscode
1.19.1

debugger-for-chrome
msjsdiag
4.11.3

es7-react-js-snippets
dsznajder
2.2.2

hex-fmt
keroc
1.0.0

python
ms-python
2019.4.12954

sftp
liximomo
1.12.4

team
ms-vsts
1.149.2

vscode-deploy-reloaded
mkloubert
0.87.2

vscode-docker
PeterJausovec
0.6.2

vscode-hexdump
slevesque
1.7.2

vscode-nuget-package-manager
jmrog
1.1.6

TestNetCoreIssue: Did not find 'Microsoft.NETCore.App' in lock file.

this is a "false positive".
The real issue is likely that OmniSharp selects msbuild from Visual Studio 2017 instead of the new msbuild 16 that ships with OmniSharp or with VS 2019.
The workaround would be to either install latest VS 2019 on that machine, that will allow Omnisharp to use its msbuild. This is the "better" workaround.
The "worse" workaround would be that you could... uninstall VS 2017 - this way OmniSharp would be forced to use its own msbuild 16.

Thank you very much @filipw ! Installing VS 2019 fixed it!


Atmospheric pressure in convection calculation

Since not all people live at sea-level, it would be useful to include air-pressure (or air-density) correction factor to convective heat transfer calculation. It also affects evaporation but influence there is very very small.
The usual correction in literature is:
hc = hc_seaLevel * k
k being (pressureAtSite / pressureAtSeaLevel)**n
n ranges from
0.50 in Tikuisis 2004, https://www.researchgate.net/publication/235037111_Prediction_of_Times_of_Facial_and_Finger_Freezing_During_Cold_Air_Exposure
to
0.55 in Gagge 1977, https://www.researchgate.net/publication/229601121_Heat_Exchange_Between_Human_Skin_Surface_and_Thermal_Environment
to
~1.00 in MENEX-2005

It also affects evaporation but influence there is very very small.

I was to fast in writing that sentence - it seems it is not clear yet how big influence of air pressure on evaporative heat loss is.
Some sources say he = he_seaLevel * k
k being (pressureAtSeaLevel / pressureAtSite)**0.45
Other sources say influence is smaller.

Thank you for your suggestion.
I added the codes to correct hc and he values.
https://github.com/TanabeLab/JOS-3/tree/feature%2314