Nixos containers fail to start

I created a nixos container declaratively:
{ lib, pkgs, config, ... }:

let
  pypkgs = pkgs.python27Packages;
in
{
  containers.prime1 = {
    privateNetwork = true;
    hostAddress = "<IP_ADDRESS>";
    localAddress = "<IP_ADDRESS>";

    config = { config, pkgs, ... }:
      {
        systemd.services.prime = {
          wantedBy = [ "multi-user.target" ];

          serviceConfig = {
            ExecStart = "${pypkgs.python} -m SimpleHTTPServer";
          };
        };
      };
  };
}

Did a nixos-rebuild and then from journalctl:
Feb 18 11:20:37 nixos systemd[1]: Starting Container 'prime1'...
Feb 18 11:20:37 nixos container prime1[7701]: /nix/store/1klvgi1v9ycfbsrndimq3h19wr4z4akb-unit-script/bin/container@-start: line 24: /nix/var/nix/profiles/per-container/prime1/system/system: No such file or directory
Feb 18 11:20:37 nixos container prime1[7701]: Spawning container prime1 on /var/lib/containers/prime1.
Feb 18 11:20:37 nixos container prime1[7701]: Press ^] three times within 1s to kill container.
Feb 18 11:20:37 nixos systemd-machined[7632]: New machine prime1.
Feb 18 11:20:37 nixos container prime1[7701]: /etc/localtime does not point into /usr/share/zoneinfo/, not updating container timezone.
Feb 18 11:20:37 nixos container prime1[7701]: /nix/store/4akd4ll5v5mwx2aidzj06a848bbl3rrm-container-init: line 19: /nix/var/nix/profiles/system/init: No such file or directory
Feb 18 11:20:37 nixos systemd-machined[7632]: Machine prime1 terminated.
Feb 18 11:20:37 nixos container prime1[7701]: Container prime1 failed with error code 1.
Feb 18 11:20:37 nixos systemd[1]<EMAIL_ADDRESS>main process exited, code=exited, status=1/FAILURE
Feb 18 11:20:37 nixos container prime1[7710]: Could not kill machine: No machine 'prime1' known
Feb 18 11:20:37 nixos systemd[1]: Failed to start Container 'prime1'.
Feb 18 11:20:37 nixos systemd[1]: Unit<EMAIL_ADDRESS>entered failed state.
Feb 18 11:20:37 nixos systemd[1]<EMAIL_ADDRESS>failed.

cc @edolstra

The directory /nix/var/nix/profiles/per-container/prime1 is empty.

Ah ok. So I only did nixos-rebuild build not switch, sorry.


What if keyd used libinput?

Hot off the heels of #66... :)
I'm curious if you've considered using libinput rather than interfacing directly with evdev? I know this would imply a large rewrite of some key parts of the code, but for the sake of imagining possibilities, perhaps we could consider it just for a moment?
(This is also related to linuxtouchpad discussion -- the last question in particular, "should key remappers be implemented at the same level as touchpad remappers (like Touchégg and Gebaar)?")

I learned recently about how gesture remappers like gebaar and Touchegg are similar to key remappers. I've diagrammed the "overview" from the perspective of a touchpad here (the idea is exactly the same for keyboards). In essence, instead of opening evdev file descriptors directly, gesture remappers have to rely on libinput to detect the gestures before they can be remapped. Then, the next layer in the stack opens their "virtual device" and uses that input instead of the "real" device.
libinput handles keyboard events, mouse events, touchpad events, touch screen events, and tablet events. These events are all at a fairly "low level" in the sense that there is some normalization going on, but not a lot of interpretation. And yet, it seems like input devices generally are often related--sometimes multiple kernel devices are the same physical device, and sometimes two or more devices interact. In fact, #42 and #66 are sort of proof of how they are related in sometimes surprising ways.
libinput is now used almost universally in X.Org (Xserver) and Wayland compositors (Weston, mutter, KWin). The one place it may not be universal is in text terminals.

So there are clearly some benefits to using libinput as a source of events, at least at the boundary around something like keyd:

You get some normalization for free (for example if combining a keyboard with a mouse--libinput has a hardware database that provides accel curves and other benefits to make mice behave)
You get beneficial device interactions for free (e.g. touchpad "disable while typing")
You get support for both major graphical desktop systems (granted, this is true of evdev too)
You can start to piece together advanced remapping scenarios where gestures and keys combine to make other possibilities (imagine "Ctrl + 3-finger-swipe right" for instance).

So I guess I'm just spitballing a bit here, but am I missing anything important? Let's say keyd 3.0 uses libinput and we're all done. Is it a net improvement?

Hot off the heels of #66... :)

I'm curious if you've considered using libinput rather than interfacing directly with evdev?

I rejected this at the outset for various reasons. keyd is intended to be a low level remapping tool that is invisible to things which are higher up on the input stack. Furthermore, libinput is just a library used by numerous compositors (and an X driver) and isn't exposed outside of them (wayland regards this as a security risk). Even if it could be implemented on top of libinput it would cease to work on anything which doesn't use it (e.g VTs).

I learned recently about how gesture remappers like gebaar and Touchegg are similar to key remappers. I've diagrammed the "overview" from the perspective of a touchpad here (the idea is exactly the same for keyboards). In essence, instead of opening evdev file descriptors directly, gesture remappers have to rely on libinput to detect the gestures before they can be remapped. Then, the next layer in the stack opens their "virtual device" and uses that input instead of the "real" device.

This may make more sense for touchpads which have more complicated semantics and are used exclusively in the graphical environments, but I'm not sure it makes sense in this case.

And yet, it seems like input devices generally are often related
..#42..proof of how they are related in sometimes surprising ways.

Aside from palm rejection, there aren't too many cases in which the pointer should care about the keyboard. To the extent that it does, I agree that this should be handled higher up the input stack. The solution to this is to ensure libinput associates keyd's virtual device with the appropriate touchpad, not to rewrite the entire project on top of a higher layer of the input stack (which is less portable).

libinput is now used almost universally in X.Org (Xserver) and Wayland compositors (Weston, mutter, KWin). The one place it may not be universal is in text terminals.

Yes, this matters. There may also be instances of people using old X drivers.

So there are clearly some benefits to using libinput as a source of events, at least at the boundary around something like keyd:

I don't think this has been clearly demonstrated.

You get some normalization for free (for example if combining a keyboard with a mouse--libinput has a hardware database that provides accel curves and other benefits to make mice behave)

This is why keyd tried to avoid managing your mouse.

You get beneficial device interactions for free (e.g. touchpad "disable while typing")

Can you name another one? This can and should be fixed by treating the keyd virtual keyboard as just another input device and configuring libinput accordingly.

You get support for both major graphical desktop systems (granted, this is true of evdev too)

Yes. evdev was chosen by design. It was originally intended to emulate open source keyboard firmware (which are desirable because they work everywhere).

You can start to piece together advanced remapping scenarios where gestures and keys combine to make other possibilities (imagine "Ctrl + 3-finger-swipe right" for instance).

This should  be (and has already been?) done higher up the input stack. It is orthogonal to keyd's goals.

Apologies, I should have scrutinized the references you listed before responding. It looks like such libinput remappers are indeed possible, though the rest of my points remain.

Hot off the heels of #66... :)

I'm curious if you've considered using libinput rather than interfacing directly with evdev?

I rejected this at the outset for various reasons. keyd is intended to be a low level remapping tool that is invisible to things which are higher up on the input stack. Furthermore, libinput is just a library used by numerous compositors (and an X driver) and isn't exposed outside of them (wayland regards this as a security risk). Even if it could be implemented on top of libinput it would cease to work on anything which doesn't use it (e.g VTs).

I learned recently about how gesture remappers like gebaar and Touchegg are similar to key remappers. I've diagrammed the "overview" from the perspective of a touchpad here (the idea is exactly the same for keyboards). In essence, instead of opening evdev file descriptors directly, gesture remappers have to rely on libinput to detect the gestures before they can be remapped. Then, the next layer in the stack opens their "virtual device" and uses that input instead of the "real" device.

This may make more sense for touchpads which have more complicated semantics and are used exclusively in the graphical environments, but I'm not sure it makes sense in this case.

And yet, it seems like input devices generally are often related
..#42..proof of how they are related in sometimes surprising ways.

Aside from palm rejection, there aren't too many cases in which the pointer should care about the keyboard. To the extent that it does, I agree that this should be handled higher up the input stack. The solution to this is to ensure libinput associates keyd's virtual device with the appropriate touchpad, not to rewrite the entire project on top of a higher layer of the input stack (which is less portable).

libinput is now used almost universally in X.Org (Xserver) and Wayland compositors (Weston, mutter, KWin). The one place it may not be universal is in text terminals.

Yes, this matters. There may also be instances of people using old X drivers.

So there are clearly some benefits to using libinput as a source of events, at least at the boundary around something like keyd:

I don't think this has been clearly demonstrated.

You get some normalization for free (for example if combining a keyboard with a mouse--libinput has a hardware database that provides accel curves and other benefits to make mice behave)

This is why keyd tries to avoid managing your mouse.

You get beneficial device interactions for free (e.g. touchpad "disable while typing")

Can you name another one? This can and should be fixed by treating the keyd virtual keyboard as just another input device and configuring libinput accordingly.

You get support for both major graphical desktop systems (granted, this is true of evdev too)

Yes. evdev was chosen by design. It was originally intended to emulate open source keyboard firmware (which are desirable because they work everywhere).

You can start to piece together advanced remapping scenarios where gestures and keys combine to make other possibilities (imagine "Ctrl + 3-finger-swipe right" for instance).

This should  be (and has already been?) done higher up the input stack. It is orthogonal to keyd's goals.
Edit:
Apologies, I should have scrutinized the references you listed more carefully before responding. It looks like such libinput remappers are indeed possible, though the rest of my points remain.

Continued offline.


Stop print the step up log

I want  to know how to stop the output log as below?
Using optional features:
    GL_ARB_vertex_array_object
    GL_ARB_ES2_compatibility
    GL_ARB_separate_shader_objects
    GL_ARB_robustness
    GL_ARB_texture_storage
    GL_ARB_invalidate_subdata
    GL_ARB_texture_storage_multisample
    GL_ARB_multi_bind
    GL_ARB_direct_state_access
    GL_ARB_get_texture_sub_image
    GL_ARB_texture_filter_anisotropic
    GL_KHR_debug
    GL_KHR_parallel_shader_compile
Using driver workarounds:
    no-forward-compatible-core-context
    nv-egl-incorrect-gl11-function-pointers
    no-layout-qualifiers-on-old-glsl
    nv-zero-context-profile-mask
    nv-implementation-color-read-format-dsa-broken
    nv-cubemap-inconsistent-compressed-image-size
    nv-cubemap-broken-full-compressed-image-query
    nv-compressed-block-size-in-bits

I find some tips is to add os.environ['HABITAT_SIM_LOG'] = "quiet" into the code, it actually work to ignore some log, but not completely.
I want to know all the setting about the logging about habitat.

Those look like Magnum logging statements. As described here, you may also try export MAGNUM_LOG=quiet.

That is a great method, all logging  kept slient!


Frame value not evaluated if used in array filter

Expression:
(
  $arr := [{'x':1}, {'x':2}];
  $arr[x=$number(variable.field)]
)

Data:
{ "variable": { "field": "1" } }

Expected:
{x: 1}

Actual:
null

The filter operator changes the $ context. The variable must be accessed via $$.
Works as designed


Update reserved usernames list

Adding additional usernames which are already routes, it's safe to add them as any existing users should already have been "broken"(shouldn't be able to access profile etc.)

It's better to use the char ~ for all new paths in future, then we do not need to reserve anything more.

Why serviceworker.js is reserved, it's under /assets/

Why serviceworker.js was reserved, it's under /assets/

Was introduced in #15834 https://github.com/go-gitea/gitea/pull/15834#issuecomment-838938088

Why serviceworker.js was reserved, it's under /assets/

Was introduced in #15834 #15834 (comment)

I can not get the point why should we keep it in the latest code base, maybe it's time to remove it?
And "less" (maybe more) could also be removed.

I can not get the point why should we keep it in the latest code base, maybe it's time to remove it?

🤷🏽♀ I'm not sure, better to leave it in then or silverwind gives the green light.

help and plugins should be kept for future usage.

help and plugins should be kept for future usage.

What about using the char ~ for all new paths in future, then we do not need to reserve anything more.
For example: /~plugins/, no conflict anymore, no one would be hurt.

Or /-/ :)

Yep, /-/ is also widely used in many systems.

So the removal of those "futured reserved names" is good?

So the removal of those "futured reserved names" is good?

After we have an agreement of /-/.

From my experience, if we say about "agreement", most people just keep silence, a few people just disagree for no reason explained, then many useful ideas cannot be made to an agreement.

From my experience, if we say about "agreement", most people just keep silence, a few people just disagree for no reason explained, then many useful ideas cannot be made to an agreement.

Well, what about documenting a similar idea/process as Go has? https://github.com/golang/proposal#the-proposal-process whereby it's a "simple" agreed if nobody has a objection to it.  Such that certain changes can be discussed and actually being worked on instead of being stalled because nobody wants to speak up.

Most communities have similar processes. besides Golang, there are Python PEP https://www.python.org/dev/peps/#meta-peps-peps-about-peps-or-processes , PHP RFC https://wiki.php.net/rfc , etc.
If Gitea can have such documents, it would help, however, such documents need an agreement again. I hope we can get right things done and move on.

Well, some comments are a liitle off-topic. Let back to this PR.
I think @lunny @Gusted and I all agree we can use /-/ in future and do not reserve any name, and remove the unused reserved names. Am I right?
And @go-gitea/maintainers , does any one have objection and new suggestions?

For the Docker/Open Container api I will need /v2/ (https://docs.docker.com/registry/spec/api/) and you can't change that to something else (like /<user>/v2).

not even /api/v2?

The last time I checked this I did not find a way. Here is the Gitlab change for example: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/10422 But I will test it again tomorrow.

Tested it again. The official Docker server has support for a different endpoint but the Docker CLI does not support it.
The spec does not allow a prefix too: https://github.com/opencontainers/distribution-spec/blob/v1.0.0/spec.md#api
Compose file:
version: '3'

services:
  docker-registry:
    image: registry:2
    environment:
      - REGISTRY_HTTP_PREFIX=/test/sub/

Opening <domain>/test/sub/v2 in a browser yields the expected JSON response.
docker tag ubuntu:latest <domain>/test/sub/ubuntu:latest
docker push <domain>/test/sub/ubuntu:latest

results in
"GET /v2/ HTTP/1.1" 404 19 "" "docker/20.10.12 go/go1.16.12 git-commit/459d0df kernel/<IP_ADDRESS>-microsoft-standard-WSL2 os/linux arch/amd64 UpstreamClient(Docker-Client/20.10.12 \\(windows\\))"
"HEAD /v2/test/sub/ubuntu/blobs/sha256:f3ef4ff62e0da0ef761ec1c8a578f3035bef51043e53ae1b13a20b3e03726d17 HTTP/1.1" 404 19 "" "docker/20.10.12 go/go1.16.12 git-commit/459d0df kernel/<IP_ADDRESS>-microsoft-standard-WSL2 os/linux arch/amd64 UpstreamClient(Docker-Client/20.10.12 \\(windows\\))"
"POST /v2/test/sub/ubuntu/blobs/uploads/ HTTP/1.1" 404 19 "" "docker/20.10.12 go/go1.16.12 git-commit/459d0df kernel/<IP_ADDRESS>-microsoft-standard-WSL2 os/linux arch/amd64 UpstreamClient(Docker-Client/20.10.12 \\(windows\\))"

The CLI does not know about the prefix and prepends the v2.
References:
https://github.com/kubernetes/ingress-nginx/issues/4027
https://stackoverflow.com/questions/65888391/docker-registry-with-prefix-has-problem-with-docker-login
https://github.com/docker/cli/issues/3255

Tested it again. The official Docker server has support for a different endpoint but the Docker CLI does not support it. The spec does not allow a prefix too: https://github.com/opencontainers/distribution-spec/blob/v1.0.0/spec.md#api
Compose file:
version: '3'

services:
  docker-registry:
    image: registry:2
    environment:
      - REGISTRY_HTTP_PREFIX=/test/sub/

Opening <domain>/test/sub/v2 in a browser yields the expected JSON response.
docker tag ubuntu:latest <domain>/test/sub/ubuntu:latest
docker push <domain>/test/sub/ubuntu:latest

results in
"GET /v2/ HTTP/1.1" 404 19 "" "docker/20.10.12 go/go1.16.12 git-commit/459d0df kernel/<IP_ADDRESS>-microsoft-standard-WSL2 os/linux arch/amd64 UpstreamClient(Docker-Client/20.10.12 \\(windows\\))"
"HEAD /v2/test/sub/ubuntu/blobs/sha256:f3ef4ff62e0da0ef761ec1c8a578f3035bef51043e53ae1b13a20b3e03726d17 HTTP/1.1" 404 19 "" "docker/20.10.12 go/go1.16.12 git-commit/459d0df kernel/<IP_ADDRESS>-microsoft-standard-WSL2 os/linux arch/amd64 UpstreamClient(Docker-Client/20.10.12 \\(windows\\))"
"POST /v2/test/sub/ubuntu/blobs/uploads/ HTTP/1.1" 404 19 "" "docker/20.10.12 go/go1.16.12 git-commit/459d0df kernel/<IP_ADDRESS>-microsoft-standard-WSL2 os/linux arch/amd64 UpstreamClient(Docker-Client/20.10.12 \\(windows\\))"

The CLI does not know about the prefix and prepends the v2.
References: kubernetes/ingress-nginx#4027 https://stackoverflow.com/questions/65888391/docker-registry-with-prefix-has-problem-with-docker-login docker/cli#3255

So we need to add v2 as reserved name.

So we need to add v2 as reserved name.

I've added v2 to the reserved usernames list.

Regarding "-", I think it's fine for all technical routes (like assets, avatars etc), but for everything visible to the end user, I personally prefer fancy URLs (/user, /settings, /admin etc). They are more intuitive to type and share (I often type URLs myself, and would probably forget about the dash easily).

Regarding "-", I think it's fine for all technical routes (like assets, avatars etc), but for everything visible to the end user, I personally prefer fancy URLs (/user, /settings, /admin etc). They are more intuitive to type and share (I often type URLs myself, and would probably forget about the dash easily).

The - would probably only be used for new routes(which currently is none in the planning IIRC)

OK. Some instances may want to customize their reserved names list. So we may could also add a new list in ini configuration.

OK. Some instances may want to customize their reserved names list. So we may could also add a new list in ini configuration.

Should that be added within this PR? Seems like a good idea.

OK. Some instances may want to customize their reserved names list. So we may could also add a new list in ini configuration.

Should that be added within this PR? Seems like a good idea.

A standalone PR maybe reviewed faster.


Default Image class support

Such as alignright aligncenter, etc.. it was reported in https://wordpress.org/support/topic/image-question-5/#post-8411985

Done and Tested by @ahmedkaludi


v11 Compatibility?

The module seems mostly non-functional in v11. I'm not getting any warnings or errors, and the sub-token icons are there, but they're non-interactable. foundry 11.302, pf2e 5.0.2.

Change in foundry's style.css broke the events. It is fixed now and I bumped the module compatibility to v11.

Quick initial testing shows it working. Thanks for the very quick turnaround!


Feat theme generator

🤔 这个 PR 的性质是？

新特性提交 主题生成器

🔗 相关 Issue

💡 需求背景和解决方案

📝 更新日志

fix(组件名称): 处理问题或特性描述 ...

[ ] 本条 PR 不需要纳入 Changelog

☑ 请求合并前的自查清单
⚠ 请自检并全部勾选全部选项。⚠

[ ] 文档已补充或无须补充
[ ] 代码演示已提供或无须提供
[ ] TypeScript 定义已补充或无须补充
[ ] Changelog 已提供或无须提供

Codecov Report

Merging #655 (31e076c) into develop (769dcd1) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 31e076c differs from pull request most recent head 262f766. Consider uploading reports for the commit 262f766 to get more accurate results

@@           Coverage Diff            @@
##           develop     #655   +/-   ##
========================================
  Coverage    64.33%   64.33%
========================================
  Files          725      725
  Lines        12647    12647
  Branches      3025     3025
========================================
  Hits          8136     8136
  Misses        4511     4511

Impacted Files
Coverage Δ

src/upload/upload.tsx
29.09% <0.00%> (ø)

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 524ecac...262f766. Read the comment docs.


can not launch multiagent mission--MultiMaze.py error

I tried the Python_Examples MultiMaze in Ubuntu, but failed to get into multi agent mission.
my command is as below.
python MultiMaze.py
in another terminals, I run
python MultiMaze.py --role 1
the first one keeps outputing
Waiting for the mission to start............................................................
the second one just outputs that
Will run as role 1
Mission 0 --- starting at 0, 200, 0
DEBUG: Sending MissionInit to <IP_ADDRESS> : 10001
DEBUG: Sending MissionInit to <IP_ADDRESS> : 10000
DEBUG: Looking for server, received reply from <IP_ADDRESS>: MALMOS<IP_ADDRESS>:41812
DEBUG: Sending MissionInit to <IP_ADDRESS> : 10001
DEBUG: Sending MissionInit to <IP_ADDRESS> : 10000
DEBUG: Looking for client, received reply from <IP_ADDRESS>: MALMOBUSY
I want to test multi agent mission in my project, should I set something like the client pool so that to launch multi agents mission?

@WXFMAV Multi-agent missions require you to launch two instances of the Minecraft client - did you do that?
By default they will take ports 10000 and 10001, so MultiMaze.py should then work.

@timhutton I have tried to launch two intance of the Minecraft client, but now the second command
<python MultiMaze.py --role 1>
always return Mission ended abnormally:Unable to connect to Minecraft server in multi-agent mission.
and the seconde Minecraft window show something like:
Failt to log in(Try restart your game
I wonder if it was because I launch both of the two client in my local computer?
show I run the two client in two different computer？
thanks.

You can run them both on the local computer, that should be fine. It sounds like the second agent couldn't authenticate - at the moment, you need an authenticated Minecraft login for each agent you want running in a multi-agent mission. In other words, to run two agents in a mission together you will need to have purchased two Minecraft accounts. Once you've done that, within the Minecraft client you can use the malmo mod options->logins -> add user to enter your usernames and passwords, and Malmo will use that to log the agents in. (You might need to restart the Minecraft clients for it to take effect.) (Note that the login details are written in plain text into a file in your Malmo folder, so don't use the same password you use for all your internet banking... also, make sure you only have one client running when you enter the details, or the other client might stomp on the config file and you'll have to enter them all again...)

@DaveyBiggers  It seems that I haven't found any logins in options. do you mean the options button in the Minecraft Main window?

@WXFMAV from the main menu screen, click on the "Mods" button, then choose "Microsoft Malmo Platform" from the list on the left, and select "Config".
Alternatively, from the in-game menu, select "Mod Options...".

OK! thanks.

Hi, I run into the same problem. But I could not find the "Microsoft Malmo Platform" in the "Mods" button. The picture shows all I have. Any idea? Thanks


OSError: [E050] Can't find model 'None'. It doesn't seem to be a shortcut link, a Python package or a valid path to a data directory.

Rasa version:0.1.1
Python version: 3.7
Operating system (windows, osx, ...):MacOS
Issue:
Traceback (most recent call last):
File "nlu_model.py", line 18, in
run_nlu()
File "nlu_model.py", line 13, in run_nlu
interpreter = Interpreter.load('./models/nlu/default/clgnlu')
File "/usr/local/lib/python3.7/site-packages/rasa_nlu/model.py", line 293, in load
skip_validation)
File "/usr/local/lib/python3.7/site-packages/rasa_nlu/model.py", line 320, in create
model_metadata, **context)
File "/usr/local/lib/python3.7/site-packages/rasa_nlu/components.py", line 419, in load_component
cached_component, **context)
File "/usr/local/lib/python3.7/site-packages/rasa_nlu/registry.py", line 133, in load_component_by_name
return component_clz.load(model_dir, metadata, cached_component, **kwargs)
File "/usr/local/lib/python3.7/site-packages/rasa_nlu/utils/spacy_utils.py", line 126, in load
nlp = spacy.load(model_name, parser=False)
File "/usr/local/lib/python3.7/site-packages/spacy/init.py", line 21, in load
return util.load_model(name, **overrides)
File "/usr/local/lib/python3.7/site-packages/spacy/util.py", line 119, in load_model
raise IOError(Errors.E050.format(name=name))
OSError: [E050] Can't find model 'None'. It doesn't seem to be a shortcut link, a Python package or a valid path to a data directory.
Content of configuration file (config.yml):
haven't created any yet! As I am just aiming for NLU

Content of domain file (domain.yml) (if used & relevant):
slots:
  gender:
    type: text
  course:
    type: text

intents:
 - greet
 - goodbye
 - admission
 - hostel

entities:
 - gender
 - course

templates:
  utter_greet:
    - 'Hello! How can I help?'
  utter_goodbye:
    - 'Talk to you later.'
    - 'Bye bye :('
  utter_ask_course:
    - 'In which course?'
  utter_ask_gender:
    - 'Are you a boy or a girl?'

actions:
 - utter_greet
 - utter_goodbye
 - utter_ask_course
 - utter_ask_gender
 - action_admissioninfo
 - action_hostelinfo

Hi there, it's totally okay to not have any policies configured if you're only using NLU, but do you have an NLU pipeline configured? Also, rasa does not yet support python 3.7, you'll have to create a virtualenv with python 3.6.

{
"pipeline":"spacy_sklearn",
"path":"./models/nlu",
"data":"./data/data.json"
}
Sure, python does show some warning but no errors on that part. But will try with virtualenv with python 3.6 as well

Hmm, can you check in your directories where your trained NLU model is being stored? To me it looks like you're persisting the model to "./models/nlu" and then trying to load it from './models/nlu/default/clgnlu'.

Ahaa! That was so silly of me! Thanks, that helped!

No worries. Glad you got it fixed 😄

I am facing the Same problem and the solution here is not working

@ghostrider303 please create a new issue and fill out the issue template with your information


Improve the implementation of RDD TakeOrdered and Top operations

Current implementation for RDD TakeOrdered and Top operations is based on in-memory sort, which can't handle the scenario that partition data is too large to fit into memory.
This PR tries to solve this problem by

Using a bounded priority queue to find out the top K elements for each partition, priority queue only holds K elements in memory and don't need to sort all data first
Add an extra Reduce operation to aggregate the result data for each partition.

Current coverage is 82.68% (diff: 82.45%)

Merging #528 into master will increase coverage by 0.19%

@@             master       #528   diff @@
==========================================
  Files            64         65     +1
  Lines          7117       7221   +104
  Methods        1149       1155     +6
  Messages          0          0
  Branches        914        932    +18
==========================================
+ Hits           5871       5971   +100
  Misses          915        915
- Partials        331        335     +4

Powered by Codecov. Last update da03e58...a0c72f5

LGTM


Add support for lunar eclipses

So far, only the Moon would cast shadows onto the Earth. Now, the Earth also casts shadows onto the Moon.

This Pull Request does not fix the lunar eclipses. However, the two parameters to change are in lines 1071 and 1075. I do not have edit rights to this repo, you can change that.
To test, just run the app in the default settings. Initially, the Moon is in a position casting shadow on the Earth, which is stationary (speed=0). A few seconds later, the Moon has completed half its orbit around the Earth, and the Earth should be casting shadow on the Moon.
There is a lot of dead code in this app. The functions updateEarth and updateMoon (that you changed) are only called from a menu that is disabled (the circleVarious div, which is hidden).

@danielramosg You should have write access now. Please push your fixes to this branch. I am not able to test this any further due to current workload caused by other projects. Thanks.

@DoroteaDudas, in case you happen to see this, is there any reason why lunar eclipses were disabled from the app?
I would like to use this app for a workshop for the International Day of Mathematics, March 14th, 2025, which coincides with a lunar eclipse.

These changes are now in master and devel, but I needed to force-push devel because it was messed up by a previous commit. Therefore, there is no need to merge this PR and I'll just close it.


Filtering and smoothing without estimating

Hi Junior,
I am trying to filter and smooth my model before estimation, but I'm getting the error messages below (replication files are attached). Thanks a lot if you find any time to look into!
1) When filtering

myFiltSmooth = filter(mdlVector(iMdl),'data',data,'kf_tol',0);
Operands to the || and && operators must be convertible to logical scalar values.

Error in fix_point_iterator
Error in doubling_solve
Error in lyapunov_equation
Error in lyapunov_equation
Error in dsge/filter_initialization
Error in dsge/filter_initialization
Error in dsge/filter
2) When smoothing
myFiltSmooth = smooth(mdlVector(iMdl),'data',data);
Error using NaN
Input following 'like' is not a single or double array.
Error in smooth (line 163)
c = NaN(size(y),'like',y);
Best,
Eduardo

Hi Eduardo,
RISE does not have a function called smooth. You are probably using Matlab's econometric toolbox ...
If that's the case, look for help within Matlab or contact the Mathworks directly.
Cheers,
J.

Hi Junior, thanks for the reply!
But, what about the error in the filter function? By the error message that I received it tells me that it is a Rise function.

The exact filter function that you use depends on the inputs that are passed to the function. I cannot say more without seeing the codes. I presume mdlVector(iMdl) is a dsge object?

Exactly, mdlVector is a vector of DSGE objects. For whenever you have time, the code is attached.
Best
errorReplication.zip

I am using a different version of RISE. Can you post the full log of error you get?

Do you mean the message in the command window? This is what is displayed on it:

Operands to the || and && operators must be convertible to logical scalar values.
Error in fix_point_iterator
Error in doubling_solve
Error in lyapunov_equation
Error in lyapunov_equation
Error in dsge/filter_initialization
Error in dsge/filter_initialization
Error in dsge/filter
Error in errorReplication (line 11)
myFiltSmooth = filter(mdlVector(1),'data',data);

Hi Junior!
I have a doubt about filtering and smoothing without estimating.
After running the MCMC, will the filtered variables change? Do they not depend on the parameters? How can I learn about this? I am lost in this matter. If I don't run the MCMC, I won't have the posterior ones.

Do you mean the message in the command window? This is what is displayed on it:
Operands to the || and && operators must be convertible to logical scalar values.
Error in fix_point_iterator
Error in doubling_solve
Error in lyapunov_equation
Error in lyapunov_equation
Error in dsge/filter_initialization
Error in dsge/filter_initialization
Error in dsge/filter
Error in errorReplication (line 11)
myFiltSmooth = filter(mdlVector(1),'data',data);

If possible, please, post the replication files for me to look into.
cheers,
J.

Hi Junior, I have already sent them, but I can send them again (attached).
Em qui., 30 de jul. de 2020 às 19:21, Junior Maih<EMAIL_ADDRESS>escreveu:

Do you mean the message in the command window? This is what is displayed
on it:
Operands to the || and && operators must be convertible to logical scalar
values.
Error in fix_point_iterator
Error in doubling_solve
Error in lyapunov_equation
Error in lyapunov_equation
Error in dsge/filter_initialization
Error in dsge/filter_initialization
Error in dsge/filter
Error in errorReplication (line 11)
myFiltSmooth = filter(mdlVector(1),'data',data);
If possible, please, post the replication files for me to look into.
cheers,
J.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jmaih/RISE_toolbox/issues/138#issuecomment-666741247,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG2QCHAU5B5B4Z6W2PLQ3QLR6HW7HANCNFSM4OXOMD2A
.

I can't see anything attached to this message.
J.
On Fri, Jul 31, 2020 at 2:06 AM edugca<EMAIL_ADDRESS>wrote:

Hi Junior, I have already sent them, but I can send them again (attached).
Em qui., 30 de jul. de 2020 às 19:21, Junior Maih <
<EMAIL_ADDRESS>escreveu:

Do you mean the message in the command window? This is what is displayed
on it:
Operands to the || and && operators must be convertible to logical scalar
values.
Error in fix_point_iterator
Error in doubling_solve
Error in lyapunov_equation
Error in lyapunov_equation
Error in dsge/filter_initialization
Error in dsge/filter_initialization
Error in dsge/filter
Error in errorReplication (line 11)
myFiltSmooth = filter(mdlVector(1),'data',data);
If possible, please, post the replication files for me to look into.
cheers,
J.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/jmaih/RISE_toolbox/issues/138#issuecomment-666741247
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AG2QCHAU5B5B4Z6W2PLQ3QLR6HW7HANCNFSM4OXOMD2A
.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/jmaih/RISE_toolbox/issues/138#issuecomment-666804980,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AATKBTYNV3XVM6BMMPCV73DR6IDG7ANCNFSM4OXOMD2A
.

Hi Eduardo,
I have just looked at your files and tried to run them but there is a file missing "MultiPolRegress.m". But it is not necessary to send me the file.
What I hope you can send me is (1) a model file, (2) the parameter values, (3) the data (4) possibly any function that is written in the model file and that is unknown to matlab.  Nothing else. With this I should be able to replicate the problem.
Do you think this is something you can do?
Cheers,
J.


[Production] 502 Error when filtering tags

[Firefox] [Chrome] [Safari]
Steps

Go to osf.io and log in
Click on the search bar at the top
Paste one of the searches in the google doc.

Because of how long the searches are, I created a google doc so that I don't fill up this issue page. These are searches that I copied directly from the search bar on production after the error occurred.
These problems could occur on staging, but it could be that we don't have enough tags on staging in order to test it.
Here's the link to the Google doc:
https://docs.google.com/document/d/1G6PFRI2bNKOQMRNJKtG2Ke_vLNd4VLvsrujGTnbuzgk/edit?usp=sharing
Below each search input I have a screenshot of what occurs, though I'll also put one here:

Verify with @NatashaRichter , this is no longer an issue.


Launching Any Modpack

Hello, for the last few months whenever I launch a mudpack on both of my two computers the launcher stops disappears and then comes right back it has kept happening and though eventually it was a common issue that a patch would be sent out and fix. Sadly nothing I have found anywhere has helped and I was hoping someone would be able to help me find a solution. Thank You for anything you can find or help me do to fix this problem.
This is what pops up : [
B#339]  Error occurred during initialization of VM
[B#339]  Could not reserve enough space for object heap
[B#339] Analytics Response [runModpack]: 200
[B#339] Starting download of http://cdn.technicpack.net/platform2/pack-icons/2607.png?1436527764, with 3 tries remaining

Unless this is an issue with a solder pack, then this is a launcher issue and your in the incorrect repository.

What does that mean?

This is for Solder, not the launcher. For the launcher go to http://www.technicpack.net/help


feat(rust): add bls signature stub

@mrinalwadhwa @jared-s we should investigate bls signatures in term of public key self signature, and either add proper self signature for those keys, or disable self-sign for them

@SanjoDeundiak did you intend for the target branch of this PR to be sanjo/from_external instead of develop?

Commits are on develop


Feature/cipher suites for wss connection

Added possibility to set cipher suites on WSS connection.

I will close this pull request because there already is a pull request for this feature (https://github.com/daltoniam/Starscream/pull/110). We will correct the code according to the comments in the other pull request and make a new pull request. Sorry for the inconvenience.


zstandard compression for parameters and results

why
mitigate (as much as possible) 'document too large' mongo exceptions.  16 mb is the limit for mongodb document size.
done

zstandard compression for parameter and results
remove embedded liveaction doc in executions db and replace with liveaction id string. This change will  potentially save 1/2 the time to write the liveaction to the database as the liveaction won't be written 2 times.
added traceback info to exception handling for action execution engine and workflow engine.  This should make it easier to debug for someone when the workflow fails for some reason.  invalid orjson or unterminated yaql strings cause these exceptions in my experience.
This will require a data migration for the executionDB model for the liveaction paramter as it is now a string as opposed to an embedded document
I added a config option to turn off zstandard compression for parameters and results in the execution db and the liveaction db

Benchmark results
TLDR.
zstandard is many times faster for single field large json
zstandard is slightly slower for 8mb json
The cost here is minimal from a speed perspective
$ /st2/st2common/benchmarks/micro$ pytest test_mongo_field_types.py --benchmark-columns=mean,rounds

--------------------------------- benchmark 'live_action_read': 12 tests --------------------------------
Name (time in ms)                                                                  Mean            Rounds
---------------------------------------------------------------------------------------------------------
test_read_large_execution[old_json_dict_field-tiny_1]                            2.3494 (1.0)         387
test_read_large_execution[json_dict_field-tiny_1]                                2.3697 (1.01)        391
test_read_large_execution[old_json_dict_field-json_61kb]                         3.2883 (1.40)        254
test_read_large_execution[json_dict_field-json_61kb]                             3.3988 (1.45)        269
test_read_large_execution[json_dict_field-json_4mb_single_large_field]          12.3281 (5.25)         78
test_read_large_execution[old_json_dict_field-json_647kb]                       13.6826 (5.82)         66
test_read_large_execution[json_dict_field-json_647kb]                           15.9034 (6.77)         67
test_read_large_execution[old_json_dict_field-json_4mb_single_large_field]      17.2653 (7.35)         56
test_read_large_execution[old_json_dict_field-json_4mb]                        114.0750 (48.55)        11
test_read_large_execution[json_dict_field-json_4mb]                            115.1644 (49.02)        11
test_read_large_execution[json_dict_field-json_8mb]                            248.3191 (105.69)        5
test_read_large_execution[old_json_dict_field-json_8mb]                        246.7735 (105.03)        5
---------------------------------------------------------------------------------------------------------

--------------------------------- benchmark 'live_action_save': 12 tests --------------------------------
Name (time in ms)                                                                  Mean            Rounds
---------------------------------------------------------------------------------------------------------
test_save_large_execution[old_json_dict_field-tiny_1]                            6.5457 (1.0)          25
test_save_large_execution[json_dict_field-tiny_1]                                6.7954 (1.04)        134
test_save_large_execution[old_json_dict_field-json_61kb]                        11.6969 (1.79)         78
test_save_large_execution[json_dict_field-json_61kb]                            13.1218 (2.00)         75
test_save_large_execution[json_dict_field-json_4mb_single_large_field]          18.3983 (2.81)         54
test_save_large_execution[old_json_dict_field-json_4mb_single_large_field]      30.7534 (4.70)         28
test_save_large_execution[old_json_dict_field-json_647kb]                       73.0526 (11.16)        14
test_save_large_execution[json_dict_field-json_647kb]                           81.4653 (12.45)        13
test_save_large_execution[old_json_dict_field-json_4mb]                        381.4303 (58.27)         5
test_save_large_execution[json_dict_field-json_4mb]                            385.8807 (58.95)         5
test_save_large_execution[old_json_dict_field-json_8mb]                        737.6227 (112.69)        5
test_save_large_execution[json_dict_field-json_8mb]                            756.7961 (115.62)        5
---------------------------------------------------------------------------------------------------------

-------------------------- benchmark 'live_action_save_multiple_fields': 10 tests -------------------------
Name (time in ms)                                                                    Mean            Rounds
-----------------------------------------------------------------------------------------------------------
test_save_multiple_fields[old_json_dict_field-tiny_1]                              6.6645 (1.0)         113
test_save_multiple_fields[json_dict_field-tiny_1]                                  6.7131 (1.01)        123
test_save_multiple_fields[old_json_dict_field-json_61kb]                          22.1928 (3.33)         47
test_save_multiple_fields[json_dict_field-json_61kb]                              24.7535 (3.71)         41
test_save_multiple_fields[json_dict_field-json_4mb_single_large_field]            37.2357 (5.59)         25
test_save_multiple_fields[old_json_dict_field-json_4mb_single_large_field]       119.9479 (18.00)        10
test_save_multiple_fields[old_json_dict_field-json_647kb]                        198.9707 (29.86)         5
test_save_multiple_fields[json_dict_field-json_647kb]                            228.3664 (34.27)         5
test_save_multiple_fields[old_json_dict_field-json_4mb]                        1,144.1683 (171.68)        5
test_save_multiple_fields[json_dict_field-json_4mb]                            1,139.4643 (170.98)        5
-----------------------------------------------------------------------------------------------------------

This will require a data migration for the executionDB model for the liveaction paramter as it is now a string as opposed to an embedded document

data migration tested
$ ./st2-migrate-liveaction-executiondb  --config-file ../../../../conf/st2.dev.conf
StackStorm v3.5 database field data migration script

Will migrate objects with creation date between 2023-06-06 13:01:20 UTC and 2023-07-06 13:01:20 UTC.

You are strongly recommended to create database backup before proceeding.

Depending on the number of the objects in the database, migration may take multiple hours or more. You are recommended to start the script in a screen session, tmux or similar.

To proceed with the migration, press enter and to cancel it, press CTRL+C.

Migrating affected database objects between 2023-06-06 13:01:20 and 2023-07-06 13:01:20

Migrating execution objects
Will migrate 10 ActionExecutionDB objects

[1/10] Migrating ActionExecutionDB with id 64a6ba4fdce54d96db28f4ae
ActionExecutionDB with id 64a6ba4fdce54d96db28f4ae has been migrated
[2/10] Migrating ActionExecutionDB with id 64a6ba40dce54d96db28f4a2
ActionExecutionDB with id 64a6ba40dce54d96db28f4a2 has been migrated
[3/10] Migrating ActionExecutionDB with id 64a6ba3ddce54d96db28f49c
ActionExecutionDB with id 64a6ba3ddce54d96db28f49c has been migrated
[4/10] Migrating ActionExecutionDB with id 64a6ba4edce54d96db28f4ab
ActionExecutionDB with id 64a6ba4edce54d96db28f4ab has been migrated
[5/10] Migrating ActionExecutionDB with id 64a6ba50dce54d96db28f4b7
ActionExecutionDB with id 64a6ba50dce54d96db28f4b7 has been migrated
[6/10] Migrating ActionExecutionDB with id 64a6ba3fdce54d96db28f49f
ActionExecutionDB with id 64a6ba3fdce54d96db28f49f has been migrated
[7/10] Migrating ActionExecutionDB with id 64a6ba4fdce54d96db28f4b1
ActionExecutionDB with id 64a6ba4fdce54d96db28f4b1 has been migrated
[8/10] Migrating ActionExecutionDB with id 64a6ba4edce54d96db28f4a8
ActionExecutionDB with id 64a6ba4edce54d96db28f4a8 has been migrated
[9/10] Migrating ActionExecutionDB with id 64a6ba41dce54d96db28f4a5
ActionExecutionDB with id 64a6ba41dce54d96db28f4a5 has been migrated
[10/10] Migrating ActionExecutionDB with id 64a6ba50dce54d96db28f4b4
ActionExecutionDB with id 64a6ba50dce54d96db28f4b4 has been migrated
SUCCESS: All database objects migrated successfully (duration: 0 seconds).

add a field for compression of parameters somewhere.

I changed to liveaction_id.

Since liveaction field of the ActionExecutionDB was required before I made liveaction_id also required.  This should help ensure the liveaction actually exists.

also, what is up with the circle-ci failures?  is there anything we can do to fix that?

@cognifloyd The circle ci is fixed.  rabbitmq needs priv=true and redis needed to be pinned. pr. can you merge?

I think zstandard compression is a good change in case numbers across various types of datasets confirm it's indeed worth it / good trade off of CPU cycles used for compressing / decompressing those field values.
We decided to not enable compression by default as part of #4846 to keep things simple and reduce the scope of those changes. I'm fine with enabling the compression by default now, in case it numbers still back this up.
As far as this change goes:

remove embedded liveaction doc in executions db and replace with liveaction id string. This change will potentially save 1/2 the time to write the liveaction to the database as the liveaction won't be written 2 times.

This one I'm not too sure about it yet and I need to dig in and think about it some more.
I think it would be good if we split this PR into two - one for field compression changes and one for field value / foreign key change.
In the end, both changes are somewhat related, but they have vastly different implications - one was already benchmarked in the past, it's backward / forward compatible and the other one is not, it could have large implications and also requires a potentially expensive and breaking migration (which is not backward compatible).

FWIW we have forked over to this branch  along with removing the deep copies in orquesta .   We are seeing huge speed improvements.  Also, no more Mongo document too large.

I rebased the changes.  Now that we completed the mongo, python3.9, 3.10 migration code can we look at this again?


software does not open

Windows 10x64 system
When I click on SQLiteDiskExplorer.exe, cmd seems to open, then it closes.

@dursun0007
Can you confirm that you have extracted all the files into a directory ? Also, is there any message displayed on the console ? Perhaps you can run it through Visual Studio ?
Windows 11 x64:

[image: image.png]
Gui @.***>, 20 Eki 2023 Cum, 16:37 tarihinde şunu yazdı:

@dursun0007 https://github.com/dursun0007
Can you confirm that you have extracted all the files into a directory ?
Also, is there any message displayed on the console ? Perhaps you can run
it through Visual Studio ?
Windows 11 x64:
[image: image]
https://user-images.githubusercontent.com/6315083/276947220-7361a6b5-a566-4d9a-b986-0c09cc86cd15.png
—
Reply to this email directly, view it on GitHub
https://github.com/guillaC/SQLiteDiskExplorer/issues/2#issuecomment-1772756770,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABTDLMIWZT6JGYFYIMEFQ2TYAJ5CZAVCNFSM6AAAAAA6I6DFV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZSG42TMNZXGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

[image: image.png] Gui @.>, 20 Eki 2023 Cum, 16:37 tarihinde şunu yazdı:
…
@dursun0007 https://github.com/dursun0007 Can you confirm that you have extracted all the files into a directory ? Also, is there any message displayed on the console ? Perhaps you can run it through Visual Studio ? Windows 11 x64: [image: image] https://user-images.githubusercontent.com/6315083/276947220-7361a6b5-a566-4d9a-b986-0c09cc86cd15.png — Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABTDLMIWZT6JGYFYIMEFQ2TYAJ5CZAVCNFSM6AAAAAA6I6DFV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZSG42TMNZXGA . You are receiving this because you were mentioned.Message ID: @.>

Hello, your image doesn't appear to be visible. You can use the GitHub web interface to respond to the thread.


Updating Evictor Project link

Change Evictor link to point to Github Project instead of Github user

Merged with https://github.com/spring-cloud/spring-cloud-commons/commit/d95a4d8c44b7c2ffc968fd4976e5969205835474.


[POC][IR] Initial stab at std::string->String upgrade

This PR is an example of String Update with backward compact(see json_compact.py)

cc @jroesch @icemelon9

@jroesch @zhiics
wrt to the String serialization. Right now String is serialized as an normal object. So if the content of String is printable, it will show up as
{type_key: "runtime.String", repr_str: "mystring"}

If the content of the string is not printable, then it will show up as
{type_key: "runtime.String", repr_b64: "base64encoding"}

So the new IR entry will look like (note that the name field actually stores the index to the node table
[
  {"type_key": "TypeVar", "attrs" : { "name": "2" }},
  {type_key: "runtime.String", repr_str: "myname"}
]

This mechanism is baked into json serialization so it is a bit hard to move out. Of course we could also say that String should mostly be printable, and use a special serialization(e.g. just print as str when it is an old  str attribute) Thet is a special case though and makes the json serialization harder to work with when directly serialize a String object itself.

@tqchen ahh, I see. I was thinking if it is necessary to have similar stuff like Load/Save for tvm::String, so that we don't need to put them under serialization.cc. Looks it is not really needed. Thanks.


Add isEven and isOdd to Basics

isEven is referenced on Basics docs, although the function is undefined. Both functions are used quite often, and they are tiny, so there's no trouble in adding them to Basics. Yes, the user can write (\x -> x%2==0), but isEven has little chance of name collision, used often and wouldn't require the user to write yet another small helper function.

This is the policy on adding new stuff to core. I don't really believe the assertion that "Both functions are used quite often". To push this a bit further, can you come up with a list of languages and whether they have this? Like, for Python, Java, JavaScript, Ruby, OCaml, SML, Clojure, Scala, etc. do they have this imported by default? Or something else? If so, what is it?

FWIW, Clojure, Racket, Common Lisp and Emacs Lisp do import this or similar functions by default. I created this thread, because from meta-issue on API changes I understood I should create a new issue for any proposal for core that is somewhat viable. Other than that, I'm pretty happy to use *-extra packages.

What about the other languages I asked about? So far sounds like a lisp thing.

FWIW, I'm writing a little Arithmetic library with things like this in it, based loosely on Haskell's prelude + arithmoi. That sounds like a better place for things like this. (Is Arithmetic a good name, though?)

Yeah, that's the right way to go for now. Arithmetic sounds like a nice name to me :)

:+1 for having isEven and isOdd in Arithmetic. Also, there is a package math in Racket, which is very advanced and has all kinds of functions. If Arithmetic aspires to be anything like a general math-related library, it should be called math, I think.

To me, Math sounds like sin, cos, exp, ln... and Arithmetic sounds like isEven, isOdd, primes, gcd, lcm, Euclidean division... i.e., analysis vs. number theory. For some reason I feel like grouping them together would be messy, but maybe there's no reason not to?
(Also, some stuff got in the way, but I will continue work on the package soon. I'm basically translating arithmoi functions from Haskell to Elm to the best of my ability, which means it's quite involved, especially the prime stuff, but everything should be pretty fast!)

Just like there's Html, Html.Events, Html.Attributes, maybe there should be Math.Arithmetic, Math.Number (for number theory), Math.Trigonometry? Anyway, thanks for working on that :)

I wrote elm-arithmetic, which includes isEven and isOdd, among a bunch of other useful functions.


Add a mailmap to cleanup our git stats a bit

In response to https://academysoftwarefdn.slack.com/archives/C06A14QSWJW/p1702510546377459, I'm adding a mailmap to let us better see how many contributors we've had.
Please have a look and let me us if there is any mistake. I had to make some choices in some situations, so there is probably errors in there.

I will merge this as is. If someone in the mailmap wants to have a different name or email, please feel free to open a new PR.


chore: add lint rule to prevent unnecessary public modifiers

Following the TS style guide: https://google.github.io/styleguide/tsguide.html#visibility

@sbruens , I'm going to merge the PR, so the style changes can be incorporated into my PR.


Blocked a wider range of ads, tracking scripts, and unwanted content from various domains.

I have used this site to test whether the changes I have made have improved the overall efficiency of the ad-blocking. Initially without using BlockHub the efficient of my chrome browser was 32%

After using BlockHub with the current domain restrictions it is 42%

After the additions I have made it is 84%

The code has been refactored to allow for easy addition of domains. If the previous configuration is preferred for this project kindly let me know.


Add appveyor testing

This adds CI testing on Windows via appveyor. I tried it out on my fork, and all tests pass for julia 0.3. There are errors and problems with the nightlies, but those are probably just things that actually need to be fixed.
One problem is that build errors (Pkg.build("PyCall")) do not seem to trigger a test failure. Probably a more generic problem, but something that hits here. I'll continue to figure out what do do about that.
Once this is merged @stevengj needs to go to www.appveyor.com, create an account if he doesn't have one and add this project. At that point he can also add a badge to the readme.

Thanks!


Elvis is broken (401 error) - likely expired token

Elvis shows "No matching results."
The dev console in the browser shows
Error sending the query 'allResults' ServerError: Response not successful: Received status code 401

The graphql network request shows this error message:

This endpoint requires you to be authenticated.

Need to cycle a new token.
See https://github.com/silverstripe/github-issue-search-client/issues/146 for last time this happened
Acceptance criteria

[x] A new token is added to Elvis (assuming that's the problem).
[ ] If the token has an expiry, some sort of automated reminder is created so that we don't find out by elvis breaking next time around.

Recycled. Gave it a no-expiry token since it's got no permissions attached to it anyway.


Database: code support for proper test_db

Currently integration test is using the same database as production database.
Good practice would be to have separate ENVS:

test_db (yes another db instance for testing)
test_user
test_password

And make another for testing database class that inherits normal class and adds some extra testing related queries, like searching for relationship names that are used to connect nodes.

Probably not really feasible with neo4j-community edition.

with time restrictions, not going to be implemented in this project


Avoid closing cursor when consumers are disconnected

Motivation
While investigating the failures of SequenceIdWithErrorTest which are also related to #2148, I've identified these 2 issues:

Getting a "fenced" error during a consumer subscribe operation doesn't trigger the closing of the topic, thus the recovery might not be triggered if there are not producers
When closing a topic, we usually "ignore" managed ledger failures (in the sense that we rely on recovery later on). The only place where we don't ignore the errors on is on the Subscription.close() method. This method should only deal with disconnecting existing consumers and it should not close the ManagedLedger cursor. The cursor is closed when the managed ledger is closed with the topic.

Modifications

Do not close cursor when the subscription is closed, cursor will be close when managed ledger is closed
When we do get a "fenced" error during a subscribe operation, we should close the topic, in same way as we do for add entry operations failed.
Re-enabled SequenceIdWithErrorTest

retest this please


[BUG] Welcome screen asks to agree to T&Cs for using Rancher not Harvester

Describe the bug
The Harvester welcome screen post-install has a checkbox to agree to the T&Cs for using Rancher - shouldn't this be for using Harvester?
To Reproduce
Steps to reproduce the behavior:

Install Harvester
Go to management page and see last line (before Continue button)

Expected behavior
Whilst Rancher (software) is obviously being used for Harvester admin interface I expected to agree to T&Cs for using Harvester (not Rancher).
Support bundle
N/A
Environment:

Harvester ISO version: 0.3.0
Underlying Infrastructure: Baremetal with Intel NUC8i5BEH

Additional context
Screenshot

It's possible the Rancher reference could refer to company but if so I'd expect that to be Rancher Labs, SUSE, or SUSE Rancher not plain Rancher.

Tested in master-655c251a-head went to https://rancher.com/eula although that redirects to https://www.suse.com/licensing/eula/ . Is that acceptable?

I see in the PR language now states "for using {vendor}". What does {vendor} get substituted with? Also the grammar isn't correct, you don't use a company, you use the product/software. Why not say "for using a Rancher Product"?

I see in the PR language now states "for using {vendor}". What does {vendor} get substituted with? Also the grammar isn't correct, you don't use a company, you use the product/software. Why not say "for using a Rancher Product"?

@wjimenez5271 What page are you referring to? I don't see that in the eula page. Also Is it acceptable for the link to go to https://rancher.com/eula and redirect to https://www.suse.com/licensing/eula/, or should it go somewhere else?

@WuJun2016 we should display either Harvester or Rancher upon the single or multi-cluster UI, should not use vendor here, thanks.

I based on the default value in the ui-pl to determine whether it is harvester or rancher, if the default value is Harvester will be displayed as Harvester, other cases are displayed as Rancher.
@guangbochen  @wjimenez5271 @noahgildersleeve   Do you think this is okay ?

Tested in master-655c251a-head. Verified that the text is changed and that the URL is linking to the SUSE EULA page

.


Command "python setup.py egg_info" failed with error code 1 in AppData\Local\Temp\pip-build-4vog3hcr\unicodecsv\

output I get from installer
Collecting unicodecsv==0.9.0 (from -r .\requirements.txt (line 1))
Using cached unicodecsv-0.9.0.tar.gz
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
File "", line 1, in
File "C:\Users\Bryan\AppData\Local\Temp\pip-build-4vog3hcr\unicodecsv\setup.py", line 5, in
version = import('unicodecsv').version
File "c:\users\bryan\appdata\local\temp\pip-build-4vog3hcr\unicodecsv\unicodecsv__init__.py", line 48
except TypeError, e:
^
SyntaxError: invalid syntax
----------------------------------------

Means you're using some obsolete library in python.  This is because of invalid syntax "TypeError, e:" which doesn't support in python(3.x), can be rectified manually by replacing it by "TypeError as e".

Quick Resolution for python 3.x: Go to requirements.txt and replace the code with 'unicodecsv' or either just install it from pip.

requirements.txt only has 1 line in it.  What am I replacing exactly?


feat(keyboard): allow to configure keyevent type

when configuring the plugin one can pass the keyEvent as a setting, which accepts 'keyup' and 'keydown'.
Ported for v1

this is a backport for v1, see the other v2 implementation here https://github.com/aurelia/dialog/pull/363


AspectRatio  does not work in <IP_ADDRESS>

it is usefull in 2.1.1,but does not work in 3.0.0
Or is there another way to make it  full screen?
`
vlc1.SourceProvider.MediaPlayer.SetMedia(url1.ToString());
vlc1.SourceProvider.MediaPlayer.Play();
vlc1.SourceProvider.MediaPlayer.Video.AspectRatio = vlc1.ActualWidth + ":" + vlc1.ActualHeight;
`

I confirm that in 3.0.0 Vlc.DotNet version Video.AspectRatio property doesn't take any effect
It doesn't work for VLCLib 2.2.8 neither VLCLib 3.0.0

Fullscreen support is covered by #44, but I need to have a look at this and see what is broken. As usual, help is welcome :)

when i was mucking around in someone else's fork i had this issue. I actually had to go into one of the player cs files to modify the height and width directly before playback started. When I figure out what file and line it was i will edit this post.

Hi all,
I just read the post again and realised you were using WPF, which I didn't understand at first (this is why I made an issue template...)
Indeed, AspectRatio has no effect anymore on the WPF control, because it has been rewritten and uses VideoFormatCallback, as 9Arca9 points out. We could multiply the height by the ratio to get the width, but there is another solution, which is not yet documented.
The new WPF control is implemented using an ImageSource, which means you can do whatever fancy stuff you want with it in WPF, at the cost of a little performance loss.
Here is how to do:
MainWindow.xaml :
    <Grid>
        <Image x:Name="Image" Stretch="Fill" />
    </Grid>

MainWindow.xaml.cs:
        private VlcVideoSourceProvider sourceProvider;

        public MainWindow()
        {
            InitializeComponent();
            var currentAssembly = Assembly.GetEntryAssembly();
            var currentDirectory = new FileInfo(currentAssembly.Location).DirectoryName;
            DirectoryInfo libDirectory;
            if (IntPtr.Size == 4)
                libDirectory = new DirectoryInfo(Path.Combine(currentDirectory, @"..\..\..\..\..\lib\x86\"));
            else
                libDirectory = new DirectoryInfo(Path.Combine(currentDirectory, @"..\..\..\..\..\lib\x64\"));

            this.sourceProvider = new VlcVideoSourceProvider(this.Dispatcher);

            sourceProvider.CreatePlayer(libDirectory);
            sourceProvider.MediaPlayer.Play(new Uri("http://download.blender.org/peach/bigbuckbunny_movies/big_buck_bunny_480p_surround-fix.avi"));
            this.Image.SetBinding(System.Windows.Controls.Image.SourceProperty, new Binding(nameof(VlcVideoSourceProvider.VideoSource)) { Source = sourceProvider });

Another "workaround", is to move back to a WinForms control, like it was the case in the previous Vlc.DotNet releases. See Samples.Wpf.Minimal.UsingWinForms in code.
By the way, .AspectRatio returns null by default, because this is what vlc does:
https://www.videolan.org/developers/vlc/doc/doxygen/html/group__libvlc__video.html#ga058fe83cdecb2c66d075372416f233f8

Returns the video aspect ratio or NULL if unspecified

You can see an example of using Image here : https://github.com/ZeBobo5/Vlc.DotNet/tree/develop/src/Samples/Samples.Wpf.Image

Any chance of giving the .MediaSource a call to manipulate the VideoFormatCallback internally?
Something along the lines of .MediaSource.AspectRatio = AspectRatio.XXXX, just to simplify changing the aspect ratio.
Also, thanks for the information, I will be using this!

9Arca9 : That could definitely be done, but I have very few time to spend on implementation, and I need to make choices.
Given that there is this workaround and an example of Image usage, I'm not sure there is a lot of use cases in implementing a WPF-specific thing like this AspectRatio. It makes a second entry point for specifying aspect ratio (the one that doesn't work, and that magic WPF-only thing), which is not very obvious for newcomers.
Once you understand that this is just an ImageSource, and that you can stretch your Image the way you want, it's "easy" to size the control to the dimension/ aspect ratio you want.
Still, I am wondering if there is a performance impact of doing one or the other.
Do you think it make sense to have this feature? Would you like to implement it?

Thanks for the reply,
Yes it would actually be very nice to implement. The main downside to using the image dourve is the requirement that the frames need to be effectively rendered twice. Scaling up in video resolution this will start causing more and more CPU usage, and on lower end hardware could introduce an issue with frame drops and other things related to near 100% CPU usage.
I understand where you are coming from, but I feel this would be a more efficient method (though proprietary to wpf, like you said) than binding the source to an image display.
Also, something I should bring up in it's own thread but, when would be the best time to fetch the video height and width? In the on play event the video isn't being rendered, so the values haven't been bound. I am currently using the logging line 'auto hide mouse cursor' which works most of the time.
Thanks for your time!

Using Wpf, I think there will always be scaling when using Image. I don't know if there is some optimisation in the very unlikely event where the Image has the same size as the ImageSource.
The WPF ImageSource is inefficient by-design, because it implies memory copies. I took the decision of implementing it because it open more options to users :
you can choose between perfs with winforms and customizations with wpf...
I don't know of a way of having both at the same time
Regarding your question, we can discuss on gitter. VideoFormatCallback is one way to do. Is there a "parsed" event after which you could get the source dimension in "Media"?

Now that #526 has been merged, I think that it can be quite-easily doable to integrate an aspect ratio in the callback. PR welcome.


Update README.md

This small and useless PR adds a button to get your app on F-Droid and change the link to Google Play Store into a button :)
Thanks for this app

Thanks for the PR!


InputHandler.py error

Hi,
When I run the program in the Linux system with Anaconda python 2.7. I got an error,
"./subprocess.py", line 1335, in _execute_child raise child_exception
OSError: [Errno 2] No such file or directory.
This error is coming from line 10 of InputHandler.py file.
Do you have any ideas about this?
Thanks a lot,
Zesheng

Hey, I think this was caused because you downloaded the .zip file of the source code instead of 'git clone'ing it to your local computer. I've added a fix that should make it work for you. Please re-open if the problem persists.
Thanks for posting the issue!
Pete


Add histogram of all sequences under location-date plot

This should help with identifying any bias caused by a lack of sequencing. Also fix the y-axis labels for percentage mode

Fleshing this out a bit more
Add a subplot below the current location-date plot, with the same functionality as the histogram below the main GroupStack plot. This should aggregate counts across all locations, for a quick view on potential biases from sequencing effort over time. This histogram should, like the GroupStack lower histogram, be scrubbable by date

Code can be adapted from the existing GroupStack plot or from this Vega example: https://vega.github.io/vega/examples/overview-plus-detail/


Psych/Syck YAML issues on 1.9.3

I'm seeing these errors with DJ on Gemcutter. Using the latest DJ prerelease, on 1.9.3, RG 1.8.11. Any ideas? Attempted to set the yamler to Syck, and it didn't work either. Very tempted to switch to resque but would rather stay with DJ right now if we can figure this out.
https://gist.github.com/1394725

Which version of psych? Thought I saw 1.2.2 in your gist from yesterday.

Yep. There's a lot of noise here, but yes:
-bash-3.2$ ./script/rails  console staging
/var/www/rubycentral/staging.gemcutter.org/shared/bundle/ruby/1.9.1/gems/psych-1.2.2/lib/psych.rb:93: warning: already initialized constant VERSION
/var/www/rubycentral/staging.gemcutter.org/shared/bundle/ruby/1.9.1/gems/psych-1.2.2/lib/psych.rb:96: warning: already initialized constant LIBYAML_VERSION
** [NewRelic][11/26/11 00:21:38 +0000 gemcutter-staging (11266)] INFO : Dispatcher: sinatra
** [NewRelic][11/26/11 00:21:38 +0000 gemcutter-staging (11266)] INFO : Application: Gemcutter (Staging)
** [NewRelic][11/26/11 00:21:38 +0000 gemcutter-staging (11266)] INFO : New Relic Ruby Agent 3.3.0 Initialized: pid = 11266
** [NewRelic][11/26/11 00:21:38 +0000 gemcutter-staging (11266)] INFO : Agent Log at /var/www/rubycentral/staging.gemcutter.org/releases/20111126000346/log/newrelic_agent.log
** [NewRelic][11/26/11 00:21:39 +0000 gemcutter-staging (11266)] INFO : NewRelic::Agent::Samplers::DelayedJobLockSampler sampler not available: No DJ worker present
Loading staging environment (Rails 3.0.11)
Using /usr/local/rvm/gems/ruby-1.9.3-p0
ruby-1.9.3-p0 :001 > Psych::VERS** [NewRelic][11/26/11 00:21:48 +0000 gemcutter-staging (11266)] INFO : Resolved collector.newrelic.com to <IP_ADDRESS>
IO** [NewRelic][11/26/11 00:21:48 +0000 gemcutter-staging (11266)] INFO : Resolved collector-8.newrelic.com to <IP_ADDRESS>
N** [NewRelic][11/26/11 00:21:48 +0000 gemcutter-staging (11266)] INFO : Reporting performance data every 60 seconds.

 => "1.2.2"
Using /usr/local/rvm/gems/ruby-1.9.3-p0
ruby-1.9.3-p0 :002 > Psych::VERSION
 => "1.2.2"
Using /usr/local/rvm/gems/ruby-1.9.3-p0
ruby-1.9.3-p0 :003 > $:.grep /psych/
 => ["/var/www/rubycentral/staging.gemcutter.org/shared/bundle/ruby/1.9.1/gems/psych-1.2.2/lib"]
Using /usr/local/rvm/gems/ruby-1.9.3-p0
ruby-1.9.3-p0 :004 > YAML::ENGINE.yamler
 => "syck"
Using /usr/local/rvm/gems/ruby-1.9.3-p0
ruby-1.9.3-p0 :005 > YAML::ENGINE.yamler = "psych"
 => "psych"
Using /usr/local/rvm/gems/ruby-1.9.3-p0
ruby-1.9.3-p0 :006 > Delayed::Job.enqueue Indexer.new
NoMethodError: undefined method `yaml' for #<Psych::Nodes::Stream:0x00000003faf610>
	from /var/www/rubycentral/staging.gemcutter.org/shared/bundle/ruby/1.9.1/gems/psych-1.2.2/lib/psych.rb:193:in `dump'
	from /usr/local/rvm/rubies/ruby-1.9.3-p0/lib/ruby/1.9.1/psych/core_ext.rb:14:in `psych_to_yaml'
	from /var/www/rubycentral/staging.gemcutter.org/shared/bundle/ruby/1.9.1/gems/delayed_job-3.0.0.pre/lib/delayed/backend/base.rb:80:in `payload_object='
	from /var/www/rubycentral/staging.gemcutter.org/shared/bundle/ruby/1.9.1/gems/activerecord-3.0.11/lib/active_record/base.rb:1565:in `block in attributes='
	from /var/www/rubycentral/staging.gemcutter.org/shared/bundle/ruby/1.9.1/gems/activerecord-3.0.11/lib/active_record/base.rb:1561:in `each'
	from /var/www/rubycentral/staging.gemcutter.org/shared/bundle/ruby/1.9.1/gems/activerecord-3.0.11/lib/active_record/base.rb:1561:in `attributes='
	from /var/www/rubycentral/staging.gemcutter.org/shared/bundle/ruby/1.9.1/gems/activerecord-3.0.11/lib/active_record/base.rb:1412:in `initialize'
	from /var/www/rubycentral/staging.gemcutter.org/shared/bundle/ruby/1.9.1/gems/delayed_job-3.0.0.pre/lib/delayed/backend/base.rb:28:in `new'
	from /var/www/rubycentral/staging.gemcutter.org/shared/bundle/ruby/1.9.1/gems/delayed_job-3.0.0.pre/lib/delayed/backend/base.rb:28:in `enqueue'
	from (irb):6
	from /var/www/rubycentral/staging.gemcutter.org/shared/bundle/ruby/1.9.1/gems/railties-3.0.11/lib/rails/commands/console.rb:44:in `start'
	from /var/www/rubycentral/staging.gemcutter.org/shared/bundle/ruby/1.9.1/gems/railties-3.0.11/lib/rails/commands/console.rb:8:in `start'
	from /var/www/rubycentral/staging.gemcutter.org/shared/bundle/ruby/1.9.1/gems/railties-3.0.11/lib/rails/commands.rb:23:in `<top (required)>'
	from ./script/rails:6:in `require'
	from ./script/rails:6:in `<main>'
Using /usr/local/rvm/gems/ruby-1.9.3-p0

Any idea with this? This is blocking our deploys on gemcutter :(
/cc @tenderlove @sferik @cldwalker @cmeiklejohn

Is this issue specific to 1.9.3? I'd vote for just using 1.9.2-p290 for now, if that solves it.

If we're using 1.9.3 do we need to bundle the psych gem manually anymore? Isn't psych the default yamler in Ruby version >= 1.9.2?
I tried removing it in 1a7d490a231dd70488bd0b564a2f12eebcabfe21 and deployed those changes to staging.

Back from all the family shenanigans so I can finally take a good look at this tonight. Sorry, should have mentioned that the other day.

@sferik this definitely isn't fixed, and now the app isn't booting at all on my box without the psych gem.
It's only happening on staging, when I try pushing a gem.

Ok scratch that, it worked!
Solution: Uninstall psych gem from everywhere. Including staging's shared/bundle directory, and my local machine. So @sferik's patch did work, but having the psych gem installed made it very unhappy. /cc @tenderlove
Closing this out, sorry about the e-drama here.

Yay!
We just had a conversation about how we should rip out YAML for the next version.


can Whisper run on the gaps between each speech section？

Could you add an option? Sometimes using vad will miss dialogue，and --vad_threshold VALUE (float) is useless.
Like this：

silero-vad

Use Silero VAD to detect sections that contain speech, and run Whisper on independently on each section. Whisper is also run on the gaps between each speech section, by either expanding the section up to the max merge size, or running Whisper independently on the non-speech section.

silero-vad-expand-into-gaps

Use Silero VAD to detect sections that contain speech, and run Whisper on independently on each section. Each spech section will be expanded such that they cover any adjacent non-speech sections. For instance, if an audio file of one minute contains the speech sections 00:00 - 00:10 (A) and 00:30 - 00:40 (B), the first section (A) will be expanded to 00:00 - 00:30, and (B) will be expanded to 00:30 - 00:60.

This is already done. If you're missing any VAD option please open a new ticket.


Fix/adjust invoice payable at field

As I was trying to validate my API implementation via the validator, I was constantly failing the test to create simple shipping-instructions since the freightPayableAt field was not yet replaced by the invoicePayableAt field.
As far as I understand the code, this should be now done.

Merged as a part of https://github.com/dcsaorg/DCSA-API-Validator/pull/68 - Thanks for your contribution DCSA's API-Validator :)


Document Needs to be updated

[Enter feedback here]

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

ID: 806c0eb1-6e39-d04f-f870-9bab02bd168d
Version Independent ID: 6b936c21-52c3-92b5-1410-70c73a7157e2
Content: Integrate Azure DNS with your Azure resources - Azure DNS
Content Source: articles/dns/dns-custom-domain.md
Service: dns
GitHub Login: @rohinkoul
Microsoft Alias: rohink

@khushi978 , Could you please elaborate where it needs improvement so that we will have a look in to it?

@khushi978 , I was wondering if you have had a chance to look over our previous reply yet? Let us know if you have any query or input for us or if we good to close this issue.

@khushi978 , Since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly reopen the issue and continue the discussion.


problem with checkboxes in Safari 10.0.1

Visit the fiddle link here
https://jsfiddle.net/kyoukhana/bssznj2b/3/
In Safari 10.1.1 desktop check on checkbox a few times.  Value of checkbox isn't being displayed properly.

Well, that's weird. It was working before. Right now I'm not working on MDL, but I'm open to contributions to fix it (mdl branch)


Active editor not found

Description
The results of beautification are not what I expect.
Expected Results
The beautified code should have looked like:
<INSERT CODE HERE>

Steps to Reproduce

Add code to Atom editor
Run command Atom Beautify: Beautify Editor
This beautified code does not look right!

Debug
Here is a link to the debug.md Gist: https://gist.github.com/...
How to create debug.md Gist
Note that this will include a copy of your code.
If your code is private, please create a different sample of code that reproduces the problem.

In the Atom command-palette,
search for and run the command Atom Beautify: Help Debug Editor.
The debugging results will be copied to your clipboard.
Create a new Gist at https://gist.github.com/
Create a file in your new Gist called debug.md.
Paste your debugging results from Atom beautify into debug.md file in your Gist.
Add a link to your Gist in your new Issue.

Checklist

[ ] I have tried uninstalling and reinstalling Atom Beautify to ensure it installed properly
[ ] I have reloaded (or restarted) Atom to ensure it is not a caching issue
[ ] Searched for existing Atom Beautify Issues at https://github.com/Glavin001/atom-beautify/issues
so I know this is not a duplicate issue
[ ] Generated debugging information and added link for debug.md Gist to this issue

Please provide more information describing your issue, then this Issue can be reopened. Thank you.
More specifically, adding a link to the required debug.md Gist which includes debugging information that answers our most commonly asked questions: https://github.com/Glavin001/atom-beautify/blob/master/ISSUE_TEMPLATE.md#how-to-create-debugmd-gist

Having the same issue,
Active Editor not found.
Active Editor not found.
Hide Stack Trace
Error: Active Editor not found.
at /Users/Sloan/.atom/packages/atom-beautify/src/beautify.coffee:152:29
at Promise._execute (/Users/Sloan/.atom/packages/atom-beautify/node_modules/bluebird/js/release/debuggability.js:300:9)
at Promise._resolveFromExecutor (/Users/Sloan/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:483:18)
at new Promise (/Users/Sloan/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:79:10)
at atom-workspace.beautify (/Users/Sloan/.atom/packages/atom-beautify/src/beautify.coffee:77:14)
at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/private/var/folders/9n/dtdf625d7c956z6vdm0d5jm40000gn/T/AppTranslocation/202D7DA2-9F15-42AD-907B-0CCF82618F17/d/Atom.app/Contents/Resources/app/src/command-registry.js:265:35)
at CommandRegistry.handleCommandEvent (/private/var/folders/9n/dtdf625d7c956z6vdm0d5jm40000gn/T/AppTranslocation/202D7DA2-9F15-42AD-907B-0CCF82618F17/d/Atom.app/Contents/Resources/app/src/command-registry.js:3:65)
at CommandRegistry.module.exports.CommandRegistry.dispatch (/private/var/folders/9n/dtdf625d7c956z6vdm0d5jm40000gn/T/AppTranslocation/202D7DA2-9F15-42AD-907B-0CCF82618F17/d/Atom.app/Contents/Resources/app/src/command-registry.js:166:25)
at AtomEnvironment.module.exports.AtomEnvironment.dispatchApplicationMenuCommand (/private/var/folders/9n/dtdf625d7c956z6vdm0d5jm40000gn/T/AppTranslocation/202D7DA2-9F15-42AD-907B-0CCF82618F17/d/Atom.app/Contents/Resources/app/src/atom-environment.js:1314:34)
at EventEmitter.outerCallback (/private/var/folders/9n/dtdf625d7c956z6vdm0d5jm40000gn/T/AppTranslocation/202D7DA2-9F15-42AD-907B-0CCF82618F17/d/Atom.app/Contents/Resources/app/src/application-delegate.js:334:31)
at emitThree (events.js:116:13)
at EventEmitter.emit (events.js:194:7)

@fintroductions,
Please follow the issue template provided. More specifically, adding a link to the required debug.md Gist which includes debugging information that answers our most commonly asked questions.
Thank you.


Add support for slice inputs to custom sequence return types

This commit adds support for dealing with slice inputs to custom
sequence return types such as NodeIndices. Previously, if a slice
was requested from a custom return type it would have raised a
TypeError. With this commit now it will return a new container object
with a copy of the data from the requested slice.
Fixes #590

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

23 of 23 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.003%) to 98.1%

Totals

Change from base Build<PHONE_NUMBER>:
0.003%

Covered Lines:
10944

Relevant Lines:
11156

💛  - Coveralls


How to enable metrics via env vars

What happened?
I am wondering how to enable the metrics endpoint via environment variables. I tried this:
AdguardHome-Sync Version
v0.6.13
AdguardHome Version
v0.107.54
Configuration
- name: LOG_LEVEL
              value: "info"
            - name: CRON
              value: "0 */2 * * *"
            - name: RUN_ON_START
              value: "true"
            - name: API_PORT
              value: '8080'
            - name: METRICS_ENABLED
              value: 'true'
            - name: METRICS_SCRAPE_INTERVAL
              value: '30s'
            - name: METRICS_QUERY_LOG_LIMIT
              value: '10000'

Relevant log output
│                               Autoscroll:On      FullScreen:Off     Timestamps:Off     Wrap:On                                 │
│ adguardhome-sync-d68bd89fc-hs9x7 2024-12-14T21:10:51.453Z    INFO    sync    sync/sync.go:38    AdGuardHome sync    {"version" │
│ : "v0.6.13", "build": "2024-09-28T07:07:12Z", "os": "linux", "arch": "amd64"}                                                  │
│ adguardhome-sync-d68bd89fc-hs9x7 2024-12-14T21:10:51.454Z    INFO    sync    sync/sync.go:65    Setup cronjob    {"cron": "0 * │
│ /2 * * *", "next-execution": "2024-12-14T22:00:00.000Z"}                                                                       │
│ adguardhome-sync-d68bd89fc-hs9x7 2024-12-14T21:10:51.454Z    INFO    sync    sync/http.go:68    Starting API server    {"port" │
│ : 8080}                                                                                │
│ adguardhome-sync-d68bd89fc-hs9x7 2024-12-14T21:10:51.454Z    INFO    sync    sync/sync.go:75    Running sync on startup        │
│ adguardhome-sync-d68bd89fc-hs9x7 2024-12-14T21:10:51.634Z    INFO    sync    sync/sync.go:174    Connected to origin    {"from │
│ ": "<IP_ADDRESS>", "version": "v0.107.54"}                                                                                │
│ adguardhome-sync-d68bd89fc-hs9x7 2024-12-14T21:10:53.362Z    INFO    sync    sync/sync.go:267    Start sync    {"from": "10.72 │
│ .72.72", "to": "<IP_ADDRESS>"}                                                                                │
│ adguardhome-sync-d68bd89fc-hs9x7 2024-12-14T21:10:53.561Z    INFO    sync    sync/sync.go:275    Connected to replica    {"fro │
│ m": "<IP_ADDRESS>", "to": "<IP_ADDRESS>", "version": "v0.107.54"}                                                                │
│ adguardhome-sync-d68bd89fc-hs9x7 2024-12-14T21:10:55.270Z    INFO    sync    sync/sync.go:303    Sync done    {"from": "10.72. │
│ 72.72", "to": "<IP_ADDRESS>"}                                                                                │
│ adguardhome-sync-d68bd89fc-hs9x7 2024-12-14T21:12:04.361Z    INFO    sync    sync/http.go:31    Starting sync from API    {"re │
│ mote-addr": "<IP_ADDRESS>:50780"}                                                                                │
│ adguardhome-sync-d68bd89fc-hs9x7 2024-12-14T21:12:04.486Z    INFO    sync    sync/sync.go:174    Connected to origin    {"from │
│ ": "<IP_ADDRESS>", "version": "v0.107.54"}                                                                                │
│ adguardhome-sync-d68bd89fc-hs9x7 2024-12-14T21:12:05.132Z    INFO    sync    sync/http.go:31    Starting sync from API    {"re │
│ mote-addr": "<IP_ADDRESS>:48132"}                                                                                │
│ adguardhome-sync-d68bd89fc-hs9x7 2024-12-14T21:12:05.132Z    INFO    sync    sync/sync.go:148    Sync already running          │
│ adguardhome-sync-d68bd89fc-hs9x7 2024-12-14T21:12:05.796Z    INFO    sync    sync/http.go:31    Starting sync from API    {"re │
│ mote-addr": "<IP_ADDRESS>:48146"}                                                                                │
│ adguardhome-sync-d68bd89fc-hs9x7 2024-12-14T21:12:05.796Z    INFO    sync    sync/sync.go:148    Sync already running          │
│ adguardhome-sync-d68bd89fc-hs9x7 2024-12-14T21:12:06.601Z    INFO    sync    sync/sync.go:267    Start sync    {"from": "10.72 │
│ .72.72", "to": "<IP_ADDRESS>"}                                                                                │
│ adguardhome-sync-d68bd89fc-hs9x7 2024-12-14T21:12:06.796Z    INFO    sync    sync/sync.go:275    Connected to replica    {"fro │
│ m": "<IP_ADDRESS>", "to": "<IP_ADDRESS>", "version": "v0.107.54"}                                                                │
│ adguardhome-sync-d68bd89fc-hs9x7 2024-12-14T21:12:08.499Z    INFO    sync    sync/sync.go:303    Sync done    {"from": "10.72. │
│ 72.72", "to": "<IP_ADDRESS>"}                                                                                │
│                                                                                │
│                                                                                │
│

Anything else?
No response

API_METRICS_ENABLED: 'true'

Working, awesome!


fMRI QC on multi-echo data

Hello,
I have applied fMRI QC to each of 3 echoes from a multi-band multi-echo acquisition with 1 second TR. I find the estimated motion (DVARS, FD, 6 movement parameters) time-series looks different for each echo! I would have guessed these ought to be the identical but perhaps sub-TR differences between echoes are responsible for this.
Is this surprising to you or something you would have expected? I'm just wondering if this could be a bug rather than a feature of the data.
Thanks!

Unfortunately, MRIQC is totally unaware of multiecho data. We should definitely update it for ME.

Thanks! As far as I can tell, there should be no reason for mriqc to do
anything wrong in analyzing multiple echoes. It worked perfectly from a
user standpoint. But I wanted to double check if you had any thoughts if
this inconsistency could be a bug.
Maybe this is a question for neurostars as well. Will post later.
On Fri, Feb 15, 2019, 12:01 Oscar Esteban<EMAIL_ADDRESS>wrote:

Unfortunately, MRIQC is totally unaware of multiecho data. We should
definitely update it for ME.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/poldracklab/mriqc/issues/773#issuecomment-464180891,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAov9_qZxmLSPh9E0aSlAonjyg2d5ViBks5vNxIogaJpZM4a97La
.

Sorry for the noise - this was opened when I removed the stale bot. Please dismiss notifications.


REDO: Do not automatically load Astropy extension

This is a redo of #393, which has already been approved. It was reverted since the changes should not have been merged until the corresponding PR in astropy is accepted (https://github.com/astropy/astropy/pull/6883). It can be merged once the changes in astropy are merged.

Coverage decreased (-0.004%) to 95.127% when pulling 530577f22656c33d16e4689304a233b53dfc0037 on revert-394-revert-393-no-astropy-extension into 5a394ccea33ed8217845850becc1e321d3a096c6 on master.

Coverage decreased (-0.004%) to 95.127% when pulling 43b519ed901cb8c7fe6a59510757ec74dcf85b5b on revert-394-revert-393-no-astropy-extension into 5a394ccea33ed8217845850becc1e321d3a096c6 on master.


vaultwarden.webvault: 2024.3.0 -> 2024.3.1

Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

The NixOS test fails for me with
server # [   43.696682] vaultwarden[811]: [2024-04-08 19:37:20.956][request][INFO] GET /api/config
server # [   43.699462] vaultwarden[811]: [2024-04-08 19:37:20.956][response][INFO] (config) GET /api/config => 200 OK
server # [   53.816437] test-runner[927]: Traceback (most recent call last):
server # [   53.822889] test-runner[927]:   File "/run/current-system/sw/bin/test-runner", line 18, in <module>
server # [   53.832460] test-runner[927]:     wait.until(EC.title_contains("Create account"))
server # [   53.840907] test-runner[927]:   File "/nix/store/bk2kan47zhbf6zzka099wc0s2dp66car-python3-3.11.8-env/lib/python3.11/site-packages/selenium/webdriver/support/wait.py", line 105, in until
server # [   53.850198] test-runner[927]:     raise TimeoutException(message, screen, stacktrace)
server # [   53.852376] test-runner[927]: selenium.common.exceptions.TimeoutException: Message:

When directly visiting the registration page, the page title is not updated anymore. I am not to much bothered with that and just changed the test.

@ofborg test vaultwarden


EyouCMS v1.5.8 has a vulnerability, stored cross-site scripting (XSS)

version：V1.5.8-UTF8-SP1

1、So you log in to the front desk member, click "I want to contribute", insert payload in the title of the article.
payload:

2、Check the parameter and find title

3、Successful submission

4、Log in to the background and view the content submitted by users

5、Check the submitted content, successfully trigger XSS attack code, pop-up cookie sensitive information

已修复，v1.6.2版本发布