Executing nerdctl run in k8 environment is stuck

Description
Executing nerdctl run in the k8 environment is stuck, but k8s can create pods normally
Steps to reproduce the issue
1.[root@m1 ~]# nerdctl ps
CONTAINER ID    IMAGE                                                                                COMMAND                   CREATED           STATUS    PORTS    NAMES
f0571a9094ce    quay.io/cilium/hubble-ui-backend@sha256:0e0eed917653441fded4e7cdb096b7be6a3bddded5a2dd10812a27b1fc6ed95b    "/usr/bin/backend"        6 minutes ago     Up                 k8s://kube-cilium/hubble-ui-77555d5dcf-pj77v/backend
046ba04231f7    docker.io/wangyanglinux/myapp:v1                                                                            "nginx -g daemon off;"    6 minutes ago     Up                 k8s://default/test-z2gms/test
5c6c52541c37    docker.io/wzxmtlw/metrics-server:v0.6.3                                                                     "/metrics-server --c…"    6 minutes ago     Up                 k8s://kube-system/metrics-server-5c7b6df7d8-md58r/metrics-server
fcb24a33d77a    quay.io/cilium/hubble-relay@sha256:d352d3860707e8d734a0b185ff69e30b3ffd630a7ec06ba6a4402bed64b4456c         "hubble-relay serve"      7 minutes ago     Up                 k8s://kube-cilium/hubble-relay-7bc7544857-95dqm/hubble-relay
....
2.[root@m1 ~]# nerdctl run --name test --rm -it busybox:1.28 /bin/sh
Executing the above command gets stuck
3.Can nerdctl run be executed outside the k8s environment
Describe the results you received and expected
null
What version of nerdctl are you using?
[root@m1 ~]# nerdctl version
Client:
Version:	v2.0.2
OS/Arch:	linux/amd64
Git commit:	1220ce7ec2701d485a9b1beeea63dae3da134fb5
buildctl:
Version:	v0.17.1
GitCommit:	8b1b83ef4947c03062cdcdb40c69989d8fe3fd04
Server:
containerd:
Version:	v2.0.1
GitCommit:	88aa2f531d6c2922003cc7929e51daf1c14caa0a
runc:
Version:	1.2.2
GitCommit:	v1.2.2-0-g7cb36325
Are you using a variant of nerdctl? (e.g., Rancher Desktop)
None
Host information
[root@m1 ~]# nerdctl info
Client:
Namespace:	k8s.io
Debug Mode:	false
Server:
Server Version: v2.0.1
Storage Driver: overlayfs
Logging Driver: json-file
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
Log:     fluentd journald json-file none syslog
Storage: native overlayfs
Security Options:
seccomp
Profile: builtin
cgroupns
Kernel Version:   5.14.0-427.13.1.el9_4.x86_64
Operating System: Rocky Linux 9.4 (Blue Onyx)
OSType:           linux
Architecture:     x86_64
CPUs:             4
Total Memory:     3.793GiB
Name:             m1
ID:               b26f2865-ca8a-49fa-a3a2-ec66adae9813

[root@m1 ~]# kubectl version
Client Version: v1.31.4
Kustomize Version: v5.4.2
Server Version: v1.31.4

@wzxmt I am not sure how to reproduce your problem.
Against a kind cluster, things are working just fine / as expected.
I need more details about your specific deployment.

How can I reproduce it from scratch?
How did you create your kube cluster exactly?
What else is involved here?
What are your containerd details?
output of nerdctl info?
re-run the failing/stuck nerdctl command with --debug-full

@wzxmt I am not sure how to reproduce your problem.
Against a kind cluster, things are working just fine / as expected.
I need more details about your specific deployment.

How can I reproduce it from scratch?
How did you create your kube cluster exactly?
What else is involved here?
What are your containerd details?
re-run the failing/stuck nerdctl command with --debug-full

My K8s deployment method uses binary deployment, and I tried again. Running "nerdctl run --name test --rm -it busybox:1.28 /bin/sh" in Flannel mode works without any stutter, but it stutters in Cilium mode. Here are the deployment modes:
linux-amd64/helm template cilium cilium/cilium --version 1.15.11
--namespace kube-cilium
--set operator.replicas=1
--set k8sServiceHost=apiserver.cluster.local
--set k8sServicePort=8443
--set ipv4NativeRoutingCIDR=<IP_ADDRESS>/16
--set ipam.operator.clusterPoolIPv4PodCIDRList=<IP_ADDRESS>/16
--set hubble.relay.enabled=true
--set hubble.ui.enabled=true
--set hubble.ui.service.type=NodePort
--set hubble.ui.service.nodePort=31235
--set routing-mode=native
--set kubeProxyReplacement=strict
--set bpf.masquerade=true
--set bandwidthManager.enabled=true >>${HOST_PATH}/roles/components/templates/cilium.yaml
[root@m1 ~]# containerd -v
containerd github.com/containerd/containerd/v2 v2.0.1 88aa2f531d6c2922003cc7929e51daf1c14caa0a
[root@m1 ~]# nerdctl info
Client:
Namespace:	k8s.io
Debug Mode:	false
Server:
Server Version: v2.0.1
Storage Driver: overlayfs
Logging Driver: json-file
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
Log:     fluentd journald json-file none syslog
Storage: native overlayfs
Security Options:
seccomp
Profile: builtin
cgroupns
Kernel Version:   5.14.0-427.13.1.el9_4.x86_64
Operating System: Rocky Linux 9.4 (Blue Onyx)
OSType:           linux
Architecture:     x86_64
CPUs:             6
Total Memory:     5.755GiB
Name:             m1
ID:               97bb3274-41ea-4a43-a74b-7dc0b86e3fa9
[root@m1 ~]# nerdctl run --name test --rm -it --debug-full busybox:1.28 /bin/sh
DEBU[0000] verifying process skipped
DEBU[0000] generated log driver: binary:///apps/containerd/bin/nerdctl?_NERDCTL_INTERNAL_LOGGING=%2Fvar%2Flib%2Fnerdctl%2F1935db59

Thanks @wzxmt
What happens with nerdctl network ls, or when starting your container with different container options? (eg: --net host)
@AkihiroSuda anyone around familiar with Kube + eBPF/Cillium who could help debug this?

nerdctl network ls

I later tried the Calico mode and it worked fine. Running "nerdctl network ls" in Cilium mode still stutters, but other modes can be executed normally.
flannel
[root@m2 ~]# nerdctl network ls
NETWORK ID      NAME      FILE
cbr0      /etc/cni/net.d/10-flannel.conflist
17f29b073143    bridge    /etc/cni/net.d/nerdctl-bridge.conflist
host
none
calico
[root@m3 ~]# nerdctl network ls
NETWORK ID      NAME               FILE
k8s-pod-network    /etc/cni/net.d/10-calico.conflist
17f29b073143    bridge             /etc/cni/net.d/nerdctl-bridge.conflist
host
none
Cilium stutters
[root@m1 ~]# nerdctl network ls

nerdctl network ls

I later tried the Calico mode and it worked fine. Running "nerdctl network ls" in Cilium mode still stutters, but other modes can be executed normally.

Interesting.
Staying stuck is rather unusual.
What I am thinking is locking on the same directory.
Been browsing Cilium source code, and indeed they do use filesystem locking, possibly on the same directory as us.
@wzxmt if you feel like it, the most helpful thing you could do is:
# clone nerdctl source code
git clone git@github.com:containerd/nerdctl.git
cd nerdctl

# Edit https://github.com/containerd/nerdctl/blob/main/pkg/netutil/netutil.go#L224
# Line 224, find this:
#	err = lockutil.WithDirLock(e.NetconfPath, fn)
# Replace it with:
#      fn()

# Compile a new nerdctl binary
make binaries

# The updated binary is under `_output`

# Now, try again
_output/nerdctl network ls

If it still does not help, you could pepper fmt.Println("debug message something") in this function (and the caller) to figure out where it is getting stuck.
I wish I could test Cilium but I am short on time right now.
Thanks @wzxmt

nerdctl network ls

I later tried the Calico mode and it worked fine. Running "nerdctl network ls" in Cilium mode still stutters, but other modes can be executed normally.

Interesting.
Staying stuck is rather unusual. What I am thinking is locking on the same directory. Been browsing Cilium source code, and indeed they do use filesystem locking, possibly on the same directory as us.
@wzxmt if you feel like it, the most helpful thing you could do is:
clone nerdctl source code
git clone git@github.com:containerd/nerdctl.git
cd nerdctl
Edit https://github.com/containerd/nerdctl/blob/main/pkg/netutil/netutil.go#L224
Line 224, find this:
err = lockutil.WithDirLock(e.NetconfPath, fn)
Replace it with:
fn()
Compile a new nerdctl binary
make binaries
The updated binary is under _output
Now, try again
_output/nerdctl network ls
If it still does not help, you could pepper fmt.Println("debug message something") in this function (and the caller) to figure out where it is getting stuck.
I wish I could test Cilium but I am short on time right now.
Thanks @wzxmt

Edit https://github.com/containerd/nerdctl/blob/main/pkg/netutil/netutil.go#L224，make binaries
You can execute nerdctl network ls, and execute nerdctl run --name test --rm -it --debug-full busybox:1.28 /bin/sh but there is still a problem

Thanks a lot @wzxmt
I think this confirms what the issue is: cilium is very likely trying to lock the same directory as nerdctl (likely the cni configuration directory).
The problem here will not be trivial to solve.
We need to flock when accessing the cni conf - this is the only way to prevent racy/concurrent modifications.
What we could do is move the lock to a different location though (purely nerdctl).
cc @AkihiroSuda


Add support to use Mavericks with JUnit 5

This PR adds support to use Mavericks in JUnit 5 Unit Tests by adding a MvRxExtension that is compatible with the JUnit 5 extension system, similar to JUnit 4 rules. To avoid code duplication, a new MvRxTestLifecycleCallbacks class is added, which wraps common before & after test code that is shared among the JUnit 5 Extension & JUnit 4 Rule, but can be removed if wanted. If any naming conventions are violated, please let me know.
Why?
I want to run my plain Android Unit Tests with JUnit 5, since JUnit 4 is mostly only needed if running integration tests. Since you cannot use the existing MvRxTestRule in JUnit 5, I tried to copy the source in my own app and migrate it myself. I got it working pretty fast and the migration is straight forward.
Usage
import com.airbnb.mvrx.test.MvRxTestExtension
import com.airbnb.mvrx.withState
import org.junit.Assert.assertEquals
import org.junit.jupiter.api.Test
import org.junit.jupiter.api.extension.RegisterExtension

class CounterViewModelTest {

    @Test
    fun testIncrementCount() {
        val viewModel = CounterViewModel(CounterState())
        viewModel.incrementCount()
        withState(viewModel) { state ->
            assertEquals(1, state.count)
        }
    }

    companion object {
        @JvmField
        @RegisterExtension
        val mvrxTestExtension = MvRxTestExtension()
    }
}

Additional information
To run the Jupiter test one has to add support for it inside the build.gradle of the module. Since the other tests run the tests using JUnit 4, the Counter sample is modified to use the Test Extension. This way, both versions are tested.

cc @gpeal @elihart

any reason for ignoring this? its kinda disrespectful if someone puts in hours of their free time trying to contribute and you don't even get feedback. @gpeal @elihart

sorry for the delay. this will be a great thing to have, we're just busy and will get to it when we can, hopefully before long.

Thanks, Detekt is failing but I'll just merge this and fix the issues myself in a followup for simplicity.


0.27.0 DB Migration Issues

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
After upgrading to 0.27.0, at least one of the subgraphs I was indexing had a store error.
{"graphQLResponse":"{\"errors\":[{\"message\":\"Store error: store error: Unrecognized enum variant: '\\u0000\\u0000\\u0000\\u0000'\"}]}"}
I tried rewinding to fix the issue, but got the following response:
Pausing deployments
error: store error: Unrecognized enum variant: ' '

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
Upgrade from 0.25.2 to 0.27.0 while indexing QmRRCsJpnPzWo8CZroC619MLJ7an2XKML63Qxik2VxgGQ9. It's a small/quick subgraph if you'd like to test upgrading while indexing. Otherwise, let me know what data you'd like from my machine to help debug.
What is the expected behavior?
Migrations run successfully and subgraph continues indexing.

Thanks @datanexus-vincent - I wonder if there was also something in the 0.25.2 -> 0.26.0 changes which might be playing a part here.. was there a reason you hadn't upgraded to 0.26.0 previously? cc @evaporei

hi - following up on this one @datanexus-vincent as we are looking to promote the release soon - were you able to reproduce this, and do you have any indication if it's an issue with 0.26.0?

Sorry, missed the reply last week. I only upgraded from 0.25.2 because I had forgotten to upgrade my testnet setup to 0.26.0 last month. I just went through and rebuilt my testnet setup on 0.26.0, re-synced the subgraph I had issues upgrading with, and upgraded to 0.27.0 with no issues. I believe it was an issue exclusively for upgrading from 0.25.2 -> 0.27.0.

Hello @datanexus-vincent sorry for the delay, how did you get the error {"graphQLResponse":"{\"errors\":[{\"message\":\"Store error: store error: Unrecognized enum variant: '\\u0000\\u0000\\u0000\\u0000'\"}]}"} exactly?
I tried indexing this subgraph QmRRCsJpnPzWo8CZroC619MLJ7an2XKML63Qxik2VxgGQ9 for a bit in 0.25.2 and then did the upgrade to 0.27.0 with no issues whatsoever.
I also did a simple query to the local node and it worked fine { tokens { id } } (result: { "data": { "tokens": [ { "id": "1" }, ... ] } }).

This can happen if you have a old graph node running against a DB that has been migrated to 0.27, for example if you have multiple nodes running against the same DB but only one was updated.

Hey @evaporei. That error occurred for every query on that subgraph after upgrading. Unfortunately though, I'm not sure I'll be able to help much more with this issue. I wasn't keeping my testnet setup in the best condition when I upgraded, I've since deleted the corrupted database / rebuilt my testnet setup, and I'm unable to replicate my issue again by syncing on 0.25.2 then upgrading to 0.27.0. Hopefully that means my original issue was a very unlikely bug that only occurred for my specific upgrade path going back multiple upgrades. I'll be more prepared to test, troubleshoot, and report bugs for future updates once I am working with our more permanent server deployment, which should be very soon.

This can happen if you have a old graph node running against a DB that has been migrated to 0.27, for example if you have multiple nodes running against the same DB but only one was updated.

Hmm, this could be the culprit, but I'm not entirely sure. I'm pretty certain I upgraded my query node at the same time, but there's a chance I could've forgotten to restart the query node resulting in this error. Like I just mentioned our testnet procedures will be seeing an overhaul soon, so I'll be more prepared to give you all better feedback for the next release.


[HOLD for payment 2023-11-21] [$125] [Form Provider Refactor] MoneyRequestMerchantPage

Coming from https://github.com/Expensify/App/issues/25397#issuecomment-1743272245, we created a new Form provider that works with functional components and we need to refactor all usages of the old Form component.
This issue is specific to refactoring src/pages/iou/MoneyRequestMerchantPage.js
cc @kowczarz @cdOut
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01502cdf518c242b82
Upwork Job ID:<PHONE_NUMBER>462670848
Last Price Increase: 2023-10-25

Hello, I'm Tymoteusz Kałuzieński from Software Mansion, the expert agency, and I would like to work on this task.

Proposal
Please re-state the problem that we are trying to solve in this issue.
We need to refactor Form inputs based on the new FORMS.md specification.
What is the root cause of that problem?
The current component is outdated and needs to be refactored.
What changes do you think we should make in order to solve the problem?
(From FORMS.md): All form inputs need to be wrapped in InputWrapper and passed as InputComponent property additionally it's necessary po pass an unique inputID. All other props of the input can be passed as InputWrapper props.
<InputWrapper
    // `InputWrapper` required props
    InputComponent={TextInput}
    inputID="uniqueTextInputID"
    // `TextInput` specific props
    placeholder="Text input placeholder"
    label="Text input label"
    shouldSaveDraft
/>

@Samueljh1 thanks for the proposal. We already have @cdOut working on it though

Summary of payments:

Reviewer: @Santhosh-Sellavel $125

Changing to weekly while we wait for payment

$125 payment approved for @Santhosh-Sellavel based on comment above.


Build(deps-dev): Bump husky from 8.0.1 to 8.0.2 (#4333)

Pull request opened by the merge tool on behalf of #4333

Merged in 7e5fe387ceeeb210c437c82a42ac3216fd7baa0d


Fix typo.

Sorry, hurts my soul :smile:.

Obsessive–compulsive disorder (OCD) is a mental disorder where people feel the need to check things repeatedly, to perform certain routines repeatedly, or have certain thoughts repeatedly.

@skoric it seems like you missed something there while renaming

@vanniktech yup, in /release directory, AS didn't pick up on it when renaming. Thanks :+1:

Looks good to me :+1:

Haha :)

@skoric thanks for PR!
@vanniktech thanks for review!


Fix coredns image version mismatch

What type of PR is this?

What this PR does / why we need it:
The coredns image generated by the airgap_patch image does not match the actual installed version.
{
  "attempts": 1,
  "changed": true,
  "cmd":
    [
      "/usr/local/bin/nerdctl",
      "-n",
      "k8s.io",
      "pull",
      "--quiet",
      "--insecure-registry",
      "<IP_ADDRESS>:30080/registry.k8s.io/coredns/coredns:v1.9.3",
    ],
  "delta": "0:00:00.047678",
  "end": "2024-01-10 22:34:41.775262",
  "msg": "non-zero return code",
  "rc": 1,
  "start": "2024-01-10 22:34:41.727584",
  "stderr": "time=\"2024-01-10T22:34:41-05:00\" level=warning msg=\"skipping verifying HTTPS certs for \\\"<IP_ADDRESS>:30080\\\"\"\ntime=\"2024-01-10T22:34:41-05:00\" level=info msg=\"trying next host\" error=\"failed to do request: Head \\\"https://<IP_ADDRESS>:30080/v2/registry.k8s.io/coredns/coredns/manifests/v1.9.3\\\": http: server gave HTTP response to HTTPS client\" host=\"<IP_ADDRESS>:30080\"\ntime=\"2024-01-10T22:34:41-05:00\" level=warning msg=\"server \\\"<IP_ADDRESS>:30080\\\" does not seem to support HTTPS, falling back to plain HTTP\" error=\"failed to resolve reference \\\"<IP_ADDRESS>:30080/registry.k8s.io/coredns/coredns:v1.9.3\\\": failed to do request: Head \\\"https://<IP_ADDRESS>:30080/v2/registry.k8s.io/coredns/coredns/manifests/v1.9.3\\\": http: server gave HTTP response to HTTPS client\"\ntime=\"2024-01-10T22:34:41-05:00\" level=info msg=\"trying next host - response was http.StatusNotFound\" host=\"<IP_ADDRESS>:30080\"\ntime=\"2024-01-10T22:34:41-05:00\" level=fatal msg=\"failed to resolve reference \\\"<IP_ADDRESS>:30080/registry.k8s.io/coredns/coredns:v1.9.3\\\": <IP_ADDRESS>:30080/registry.k8s.io/coredns/coredns:v1.9.3: not found\"",
  "stderr_lines":
    [
      "time=\"2024-01-10T22:34:41-05:00\" level=warning msg=\"skipping verifying HTTPS certs for \\\"<IP_ADDRESS>:30080\\\"\"",
      "time=\"2024-01-10T22:34:41-05:00\" level=info msg=\"trying next host\" error=\"failed to do request: Head \\\"https://<IP_ADDRESS>:30080/v2/registry.k8s.io/coredns/coredns/manifests/v1.9.3\\\": http: server gave HTTP response to HTTPS client\" host=\"<IP_ADDRESS>:30080\"",
      "time=\"2024-01-10T22:34:41-05:00\" level=warning msg=\"server \\\"<IP_ADDRESS>:30080\\\" does not seem to support HTTPS, falling back to plain HTTP\" error=\"failed to resolve reference \\\"<IP_ADDRESS>:30080/registry.k8s.io/coredns/coredns:v1.9.3\\\": failed to do request: Head \\\"https://<IP_ADDRESS>:30080/v2/registry.k8s.io/coredns/coredns/manifests/v1.9.3\\\": http: server gave HTTP response to HTTPS client\"",
      'time="2024-01-10T22:34:41-05:00" level=info msg="trying next host - response was http.StatusNotFound" host="<IP_ADDRESS>:30080"',
      "time=\"2024-01-10T22:34:41-05:00\" level=fatal msg=\"failed to resolve reference \\\"<IP_ADDRESS>:30080/registry.k8s.io/coredns/coredns:v1.9.3\\\": <IP_ADDRESS>:30080/registry.k8s.io/coredns/coredns:v1.9.3: not found\"",
    ],
  "stdout": "",
  "stdout_lines": [],
}

Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

/lgtm

/lgtm


[BUG][UT] Fix DateUtilsTest failed due to timezone inconsistent

Purpose of the pull request
The UT in DateUtilsTest may fail in some case.
This is caused by the timezone cache in ThreadLocalContext
see https://github.com/apache/dolphinscheduler/runs/5500361419?check_suite_focus=true
Error:  Failures:
Error:    DateUtilsTest.getEndOfDay:130 expected:<2019-0[2-01 07]:59:59> but was:<2019-0[1-31 23]:59:59>
Error:    DateUtilsTest.testTransformToTimezone:204 expected:<2022-03-11 [02]:06:24> but was:<2022-03-11 [10]:06:24>
Error:    DateUtilsTest.testWeek:56 expected:<Mon Jan 28 16:00:00 UTC 2019> but was:<Sun Jan 27 16:00:00 UTC 2019>

Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

Codecov Report

Merging #8848 (230ba84) into dev (2335453) will increase coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##                dev    #8848   +/-   ##
=========================================
  Coverage     45.29%   45.30%
  Complexity     4075     4075
=========================================
  Files           702      702
  Lines         27111    27115    +4
  Branches       2897     2897
=========================================
+ Hits          12281    12284    +3
- Misses        13676    13677    +1
  Partials       1154     1154

Impacted Files
Coverage Δ

...pache/dolphinscheduler/common/utils/DateUtils.java
79.02% <ø> (ø)

...eduler/api/service/impl/AlertGroupServiceImpl.java
90.80% <0.00%> (-0.87%)
:arrow_down:

...i/service/impl/AlertPluginInstanceServiceImpl.java
65.95% <0.00%> (+0.36%)
:arrow_up:

Continue to review full report at Codecov.

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


chore: allow dev version for ansys-tools-filetransfer

Closes #2715
Duplicate of #2716 to fix failing stages for commit style and branch naming conventions

Looks like the issue is not related to my change though...


Fix bug: Allow value === false to be passed

This is necessary to make a checkbox input work.  Without this change,
value would be set to '' in this case.  Add a test.

This fixes #47.

I decided to use: 'value' in this.props as you really should allow any value. But great contribution and thanks for the tests :-)


Rank testing

Rebuild the tooling for rank testing to make it easier to iterate on search relevance

Link to feature: https://wellcomecollection.productboard.com/feature-board/planning/features/19421778

Closing as no longer valid.


Automatically resize buffer selection window

Buffer names are usually comparatively short and don't require a preview.
I have implemented it via fzf.vim ages ago:
function! FZFBufFloat() abort
    let l:blengths = []
    for l:buffer in getbufinfo({'buflisted': 1})
        if empty(l:buffer.name)
            continue
        endif
        let l:buffer = substitute(shellescape(l:buffer.name),
              \ getcwd()."/", "", "")
        let l:buffer = substitute(l:buffer, $HOME, "~", "")
        call add(l:blengths, strchars(l:buffer))
    endfor
    return { 'width': max(l:blengths)+17, 'height':
          \ len(l:blengths)+6, 'yoffset': 0.5, 'border': 'rounded' }
endfunction

command! -bang -nargs=? -complete=dir Buffers call
      \ fzf#vim#buffers(<q-args>, {'options': '--padding=1',
      \ 'window': FZFBufFloat()}, <bang>0)

Would it be possible to have something like this in fzfx.nvim in Lua?

hi @savchenko ,
The code looks like doing below things:

add --padding=1 option to fzf binary.
adjust width, height, border, rounded options for --preview-window option.

If all the code is going to setting the options directly pass to fzf binary, then it could be done via the fzf_opts option (the only difference is written by lua), please see:

FzfxBuffers command default fzf_opts option: https://github.com/linrongbin16/fzfx.nvim/blob/be08a3006551843cf273184c89233e5114d8a21b/lua/fzfx/cfg/buffers.lua#L158-L165

because 'win_opts' doesn't support function.

After further investigation, this works:
buffers = {
  fzf_opts = {
    "--info=hidden --header= --preview-window=hidden --padding=1"
  },
  win_opts = {
        relative = 'win',
        height = 10,
        width = 40,
        border = "rounded",
        zindex = 51,
    }
}

However, this does not:
buffers = {
  fzf_opts = {
    "--info=hidden --header= --preview-window=hidden --padding=1"
  },
  win_opts = function()
    local blengths = {}
    local max_length = 0
    for _, buffer_number in ipairs(vim.api.nvim_list_bufs()) do
      local buffer_object = vim.api.nvim_buf_get_name(buffer_number)
      local buffer_name = vim.fn.expand(buffer_object)
      buffer_name = vim.fn.substitute(buffer_name, vim.fn.getcwd(), "", "g")
      buffer_name = vim.fn.substitute(buffer_name, vim.fn.expand("$HOME"), "~", "g")
      blengths[#blengths + 1] = vim.fn.strwidth(buffer_name)
    end
    for _, length in ipairs(blengths) do
      max_length = math.max(max_length, length)
    end
    return {
      border = "rounded",
      height = #blengths + 4,
      width = max_length + 4,
      relative = 'win',
      zindex = 51,
    }
  end
}

Any idea why? The function returns correctly.

After carefully read your win_opts function, I think it's trying to calculate current buffer list size (for example 8), and then returns the 8 as the fzfx popup window's height.
Is that correct?

hi @savchenko, current engine doesn't support real-time refresh the 'win_opts'.
for example, when 1st run FzfxBuffers, the height is 8, max buffer name length is 36. (we have 8 buffers, and max buffer name length is 36).
in the 1st fzfx popup, if you press some 'ctrl-d' keys and delete some buffers, the 'win_opts' will not be calculate again and refresh the 1st fzfx popup.
but after you press esc key and quit 1st popup, then run the 2nd FzfxBuffers, now the height and width will be calculate by the current buffers status.
I will submit PR to support the 'win_opts' to be a function, but it still cannot support the real-time scenario when you press 'ctrl-d' key.

hi @savchenko , this feature is added in #517 , please pull latest main branch and have a try.


Add support for IBM Cloud Billing Converter

Support for using the converter to map IBM Cloud Billing Report CSV to the FOCUS specification.

An anonymized billing sample has been added for testing purposes

Unit test added for the billing csv

The data_loader was modified to support IBM Cloud's non-standard csv format which contains a header at the top of the CSV. This metadata is duplicated and concatenated to the billing line items.

progress and conversion rules export reports have been added

@chrisw-ibm thank you this is great. I approved run, it's builing as soon as done I can merge it back.

@varunmittal91 I pushed the fix for the linting error on the import order. Can you approve the run again :)

@chrisw-ibm sorry for the back and forth
here's the patch on the formatting error
formatting.patch

Thanks for the patch. All checks pass now!

Thanks for the patch. All checks pass now!

Thank you so much @chrisw-ibm, this is awesome.

Thanks for the patch. All checks pass now!

Thank you so much @chrisw-ibm, this is awesome.

Hey also realized we need to add IBM to supported list of cloud vendors on the README and add the piechart. I would love to connect and discuss more on this.


[v1.18]: Add CaaSP kube-apiserver container image

It will be squashed in https://github.com/SUSE/caasp-container-images/pull/66


Current situation with main CCXT?

Hi
As original ccxt added support for C#, I had 2 questions?
Is there any relation with this project & original ccxt (C# version)?
Will this project develop anymore?

The original ccxt and ccxt.net are not related. We also plan to continue developing ccxt.net separately regardless of ccxt. Thank you.


color

I was wondering what your thoughts are on exposing color information. Right not it seems it is discarded which seems like a loss of information.

Currently ignored but should probably change. Localisation will of course be an issue.

Here's a "wonderful" example from real life:

Note the text referencing the parts of a specific color. (The again, this is a rather extreme example failing WCAG in all sorts of ways.)


Unify JSON-RPC request & response API

Right now, there are multiple types in the project that represent the same schema of a JSON-RPC request or response (WCRequest, JSONRPCRequest, ChatRequest, etc). They are basically duplicates that offer the same functionality, but increase the complexity of the codebase and the effort for maintaining them.
The goal is to provide a unified JSON-RPC request/response pattern API, that:

Is agnostic of any WalletConnect domain rules;
Is as compliant as possible with the JSON-RPC 2.0 specs;
Can replace the current JSON-RPC types scattered around the project.

This aims to reduce the complexity of the codebase and increase the scalability of the project.
The solution can be provided in its own swift package (import JSONRPC) and tested in isolation.

merge-these-changes
Sent with GitHawk


www.e-junkie.com

Energized Protection - block ⚡

Let's make an annoyance free, better open internet, altogether!

Issue Submit Form

  Provide the following infos properly, which will help us to resolve your issue quickly.

Issue(s):
Type x in between [ ] and make sure there isn't any space between brackets. Example; for Your Selected Issue(s), type like this - [x]
You can select more than one category of issues if you need to!

[x] Whitelist
[ ] Blacklist
[ ] App Broken
[ ] Website Broken
[ ] Request
[ ] Other Issue

Pack(s):
Write the name of the pack(s) you are using.

Pack(s) Name:  Ultimate

Extension(s):
Also name the extension(s) if you are using any. If you don't then leave it blank.

Extension(s) Name:

Domain(s):
If you are submitting this issue for whitelist/blacklist issue, send us the domain(s) for whitelisting/blacklisting here. Kindly use the Code Tag to prevent tracking.

Domain(s):

www.e-junkie.com

Your Config:
Just to ensure there is no issues or conflicts with other app/software/magisk module/extension/source list.
Make sure you are running Energized Protection Service only.

Client: PiHole

Version: 5.0

Details:
Write us a lil bit more about your issue or query. You can attach any screen shot or log of the issue or advert, this will help to highlight it.

Your Issue Detail:
This site sells digital downloads
but, the CDN uses *-wpengine.netdna-ssl.com and wpengine.netdna-cdn.com

Thank you for making Energized Protection great, with your kind help!
A project by Ador with ❤

* but, the CDN uses *-wpengine.netdna-ssl.com and wpengine.netdna-cdn.com

this seems solved according to https://github.com/EnergizedProtection/block/issues/459 but

www.e-junkie.com

itself is on the Ultimate set. The source would appear to be Airelle's https://block.energized.pro/assets/sources/filter/airelle-pub.txt, yet another potential mishap on their part.

Yea, still seeing the domain on Ultimate list
I've reported it to Airelle. But I've reported tons of domains to Airelle and they never fix it.

Airelle updated today and removed the entry, thus should be sorted.

Thanks!


"Enable PSM patching" re-enables itself on reboot

[x] I have searched open and closed issues for duplicates
[x] I am submitting a bug report for existing functionality that does not work as intended
[x] I have read https://vigem.org/Community-Support/
[x] This isn't a feature request or a discussion topic

Bug description
After having disabled the PSM patching, by unticking the checkbox for it, and restarting the computer, the checkbox has automatically ticked itself again. It doesn't seem like the setting is stored anywhere. I think it's supposed to be stored in the registry on a value called "IsPSMPatchEnabled", but this doesn't seem to get written anywhere.
I've uninstalled and reinstalled the utility, but the problem remains.
Note that disabling the filter does work as intended while keeping the computer running. It's just that it re-enables itself on reboot.
Steps to reproduce

Install BthPS3.
Start the utility.
Click yes in the elevation prompt.
Go to tab "Filter Driver Settings".
Untick "Enable PSM patching.
Close the utility and restart the computer.
Open the utility again.

Actual result: The checkbox is ticked again. And the filter is active.
Expected result: The checkbox should remain unticked and the filter should remain inactive.
Screenshots
Machine info
CPU-Architecture: x64
Windows version: Windows 10 Enterprise 22H2
Software/driver version(s): v2.6.174
Any other helpful information
Here is a discussion of the problem in Discord:
https://discord.com/channels/346756263763378176/1025174973498789918/1099328923738837013

I could try to manually add it to the registry and see if it at least reads it like it’s supposed to. 🙃
Could you confirm where it’s supposed to be? I couldn’t figure that part out for sure.

It is supposed to be here HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_0A12&PID_0001\a&c9c4e92&0&4\Device Parameters as value BthPS3PSMPatchEnabled, example:

Your key may slightly differ as it depends on the hardware ID of the dongle and the USB port.

Okay, so I found the value here:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\USB\VID_8087&PID_0029\6&28cf390b&1&13\Device Parameters

It was set to 1.
So I opened the utility and unticked it and closed the utility again.
(Now the filter is off until I restart).
Refreshed in Registry Editor, but the value was still 1. Not a good sign.
So I manually changed it to 0.
Restart.
In the utility, the checkbox is ticked again.
In the registry, the value is still on 0.

So the value was created there at some point. Found no other references to BthPS3PSMPatchEnabled. But it's not getting written to and it's not being read from either.
I'm wondering if there is some sort of device mismatch or something. Perhaps the program is expecting this to be at some other location in the registry? There's nothing more to it than just using the included uninstaller, right? Do I manually need to remove some devices or something to fully uninstall it?

Hey  @nefarius any luck with this so far? No rush ofc, just curious what it could be. :) Ready to test whenever.

No. If so, the commit history would reflect changes.

devel branch has all the changes I wanna throw into a new Beta release, almost done so stay tuned.

New pre-release is out, please test!

I downloaded and installed v2.7.296 and restarted when it prompted me. (I didn't have the previous version installed.)
When trying to start the utility (admin mode), I'm getting this error message.

So I uninstalled, rebooted, installed v2.6.174 again, and rebooted. This version is able to start the utility.

I downloaded and installed v2.7.296 and restarted when it prompted me. (I didn't have the previous version installed.)
When trying to start the utility (admin mode), I'm getting this error message.

So I uninstalled, rebooted, installed v2.6.174 again, and rebooted. This version is able to start the utility.

Works perfectly over here, first try:

Previous post was Windows 11, here on Windows 10:

And as a special guest; Windows 10 version 1507!

I'm running this version:

Is there a way to check if the BthPS3 filter driver actually does get installed, or if it's an access problem I'm having?

Well, yeah, see my Screenshots, share what's happening on your end or all we can do is guess and get nowhere.

Ah I didn't realize! 😆
On v2.7.296 I get no such device showing up. So it doesn't get installed for some reason then.

When installing the lower version v2.6.174 I do say yes to this prompt btw.

... and on v2.6.174 I'm getting the device. And it's the new version? Now I'm confused...

So am I, last screenshot looks correct, first one is definitely faulty, no idea what has happened there, also the replace file dialog has never happened to me before so IDK what's going on there either.

Welp, in regards to the original issue of this, uh, issue. Look in the System event log for messages originating from BthPS3 components, pretty much everything gets logged now, so I can close this topic for good.

Might be relevant, might not be. On v2.6.174, when I do get the Bluetooth device, the driver details is mentioning two files. This is as it should be?

Welp, in regards to the original issue of this, uh, issue. Look in the System event log for messages originating from BthPS3 components, pretty much everything gets logged now, so I can close this topic for good.

Yeah, I wish I could, but if I can't start the utility on v2.7.296, I can't disable the PSM patching. :/

That is how it should be and was for years now.

Welp, in regards to the original issue of this, uh, issue. Look in the System event log for messages originating from BthPS3 components, pretty much everything gets logged now, so I can close this topic for good.

Yeah, I wish I could, but if I can't start the utility on v2.7.296, I can't disable the PSM patching. :/

Well, from the info you provided I can't see what's wrong.

Might be relevant, might not be. On v2.6.174, when I do get the Bluetooth device, the driver details is mentioning two files. This is as it should be?

That is how it should be and was for years now.

So the BthPS3PSM.sys file I had is an even lower version, <IP_ADDRESS> as seen above. This file was left in place when uninstalling.
What I did now was move that file out of there and installed v2.7.296.
... and what do you know, now I get the device and can start the utility. ;)

I'll see what I can find regarding the original issue now. 👍

Okay, so I'm not that familiar with Event Viewer, but I used "Find..." and searched for "BthPS3" and found that the source "Nefarius BthPS3 Profile Driver" seemed relevant, so I filtered on that.
The four events highlighted ought to be me starting v2.7.296 and unticking "Enable PSM patching". Then after a reboot I went in there again to see that it's reenabled (as expected).

Below are the details of those for entries. Not that much info to be found though. Should I look for something else in there?

Save the .evtx file somewhere, compress it as zip and attach it here. Don't leave any events out, I need all of them for the full picture, especially the errors.

@nefarius can you maybe trigger uninstaller to remove drivers residue from system as well as registry entries for the program? I had similar problem with the driver + no DS3 was connecting via bluetooth. Only removal of all previous devices + clearing out drivers with driverstorage explorer + removing reg entries allow me to have fully working installation.

Sure! Here are all the events. Had to split it up.

532-events.zip
(I think the recent error are from when it was not finding the device btw.)

@nefarius can you maybe modify uninstaller to remove drivers residue from system as well as registry entries for the program? I had similar problem with the driver + no DS3 was connecting via bluetooth. Only removal of all previous devices + clearing out drivers with driverstorage explorer + removing reg entries allow me to have fully working installation.

See #79

Sure! Here are all the events. Had to split it up.

532-events.zip
(I think the recent error are from when it was not finding the device btw.)

Dang, that didn't work. The setup doesn't install the filter manifest for some reason. In the meantime do as follows:

Close Event Viewer
Download [this file](https://raw.githubusercontent.com/ViGEm/BthPS3/devel/BthPS3PSM/BthPS3PSM.man to e.g. C:\temp\BthPS3PSM.man
Open a PowerShell as Administrator
Run wevtutil im "C:\temp\BthPS3PSM.man"

If nothing is printed in return, it succeeded

Restart the machine
Now redo your tests but we need this event source instead:

You should now get way less events and be able to save them to one file

Here is a working sequence from my machine:

Stored patch status 1 on device instance USB\VID_0A12&PID_0001\a&c9c4e92&0&4
Retrieved patch status 1 for device instance USB\VID_0A12&PID_0001\a&c9c4e92&0&4
Stored patch status 0 on device instance USB\VID_0A12&PID_0001\a&c9c4e92&0&4
Retrieved patch status 0 for device instance USB\VID_0A12&PID_0001\a&c9c4e92&0&4

Alright, the command worked.
I restarted, then went into the utility, disabled the PSM patching, restarted again, went in an looked, still enabled. :/ It only mentions patch status 1.
4-events.zip

Alright, the command worked.
I restarted, then went into the utility, disabled the PSM patching, restarted again, went in an looked, still enabled. :/ It only mentions patch status 1.
No "stored" events.
4-events.zip

How exactly do you test, what are you doing? The filter is supposed to store its last setting on unload/shutdown, is that what you're doing?

I open the utility, elevation prompt, click the 2nd tab, untick the checkbox, close the utility, restart.
Then go in and check.

Aha! I was just able to reproduce it on one of my machines, and I think I know what's happening, will test a potential fix - tomorrow 😉

Alright, new release in the making.

Alright, tested latest build, now all looks good. Preparing new release. For future testing, make sure to turn off both of these or it will not work as expected:

Alright @InterClaw please test this one, works on my end now as desired: http://sharex.nefarius.at/u/BthPS3Setup_x64.msi

It works! 🎉
I first uninstalled v2.7.296, rebooted, and then installed this new version (v2.8.313?). But then I got the problem where it didn't install the bluetooth device for me. Despite BthPS3PSM.sys being version "2.8.313.0".
So then I uninstalled v2.8.313, rebooted, manually deleted BthPS3PSM.sys, and then installed again. And then I got the bluetooth device so I could start the UI.
I disabled the two options as instructed and rebooted again.
The settings remained off! And my controller could connect on the first attempt, as expected now.
I noticed the bluetooth device "Nefarius Bluetooth PS Enumerator" is still there, even when the filter is disabled, but I guess it's not really doing anything right now. 👍

I noticed the bluetooth device "Nefarius Bluetooth PS Enumerator" is still there, even when the filter is disabled, but I guess it's not really doing anything right now. 👍

That is expected behaviour and xorr


Frankdoc.json is missing mandatory information

Regarding the issue https://github.com/ibissource/iaf/issues/3071 in the framework board. I think it is useful to include mandatory information in the json.

The JSON adds a field "mandatory" to mandatory config children. This field is not added for attributes yet.


add link to resized gifs

Description
Add a resized gif for X.U.Hacks
For https://github.com/xmonad/xmonad-contrib/issues/488
Checklist

[X] I've read CONTRIBUTING.md

[ ] I tested my changes with xmonad-testing

[ ] I updated the CHANGES.md file

[ ] I updated the XMonad.Doc.Extending file (if appropriate)

I think they look fine now, thanks!
Now it's fair to say that your first issue is far well behind you tada, so leave that label for new potential contributors! Good job on your contributions clap

I think I grow from a newbie to a more advanced newbie. Haha. Thanks a lot.


Add faraday dependency (>= 1.0.0)

refs #50

Codecov Report

Merging #52 (835763d) into master (817a198) will decrease coverage by 0.08%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##            master      #52      +/-   ##
===========================================
- Coverage   100.00%   99.91%   -0.09%
===========================================
  Files           42       42
  Lines         2420     2420
===========================================
- Hits          2420     2418       -2
- Misses           0        2       +2

Impacted Files
Coverage Δ

lib/calendly/client.rb
99.17% <0.00%> (-0.83%)
:arrow_down:

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

I'll fix CI tests.

I'll take over this PR to #54.


class MLPClassifier not found

MLPClassifier not in Phpml/Classification/

If you browse through the source-code, you can see MLPClassifier is under the Phpml\Classification namespace/folder. So if the autoloader is adjusted properly, it must be able to find it.

Check if you include autoloader in your script:
require 'vendor/autoload.php';

Yes , I create a run.php file , and require vendor/autoload.php
I install it with composer
composer require php-ai/php-ml
and use this example
http://php-ml.readthedocs.io/en/latest/machine-learning/neural-network/multilayer-perceptron-classifier/
but I can not include the class of MLPClassifier
I browse the source-code , can not found class MLPClassifier  in src/Phpml/Classification/
I don't know what to do , sorry
this is my code
`require_once 'vendor/autoload.php';
use Phpml\Classification\MLPClassifier;
$mlp = new MLPClassifier(4, [2], ['a', 'b', 'c']);`

and  this is Exception
Fatal error: Uncaught Error: Class 'Phpml\Classification\MLPClassifier' not found in D:\projects\phpml\run.php:11
Stack trace:
#0 {main}
thrown in D:\projects\phpml\run.php on line 11

I know , on github , the source-code MLPClassifier is under the Phpml\Classification namespace/folder, But
when I install it with composer ,  were not  , sorry , my English is terrible  ^ ^

Sorry, I forgot that MLPClassifier is not released yet (latest 0.4.1 don't have this class). If you want to use it you must install dev-master version:
composer require php-ai/php-ml dev-master

Okey , Thank you


DomainNet dataset.

Hey Longhui,
I am happy to see you release the code of CIFAR10 and CIFAR100 datasets, but there is still a little pity that I cannot see the implementation in DomainNet dataset, which is mentioned in your paper. Could you release the code of DomainNet dataset soon? Or could you tell me how to implement it based on the existing code.
Best.
Yongyi

Thank you very much for your interest. However, regrettably, I do not plan to open source the code of DomainNet, primarily due to considerations of my own research plan. I hope you can understand. But you can treat each domain of DomainNet as a type of corruption like CIFAR10/100-C and implement it by yourself.


Integration with DefiBox

Feature
Allow direct swapping of EFX and NFX on the dashboard using the Defibox liquidity pool.
Description
To get vote power in EffectDAO both NFX and EFX are required. The best way to exchange these is using the Defibox liquidity pool. It would be powerful if users could just stake EFX and have the interface automatically swap the right proportion to NFX and stake that as well, in 1 transaction.
Steps

We should first figure out if Defibox support custom user interfaces (there smart contracts don't appear to be open source).
If this is not the case, this feature can still be achieved by triggering the right actions on their smart contract.
Security concerns should also be covered, like guarding against smart contract updates on Defibox, detecting exceptional exchange rates, and warning for high slippage

A DefiBox link is now added to the stake page which helps, but this feature would still be great to have


snapbox: cfg out platform dependent deps

This prevents build of useless deps -> faster build

Rebased and renamed.


Add an option to disable the periodic suspicious outgoing network activity

I work in an environment in which no outgoing internet traffic is allowed. However, when I was running the vscode (version 1.68.1, with no extension and all the online service settings off) doing simple text editing, I repeatedly got alerts from IT that suspicious outgoing network activity was found from my machine.
I tested the behavior today on my home PC in a VM with a fresh installed Fedora 36 (verified with not any outgoing traffic) and the same online service settings being turned off with the settings json shown in below.
{     "workbench.enableExperiments": false,     "workbench.settings.enableNaturalLanguageSearch": false,     "update.mode": "none",     "update.showReleaseNotes": false,     "json.schemaDownload.enable": false,     "extensions.autoCheckUpdates": false,     "extensions.autoUpdate": false,     "settingsSync.keybindingsPerPlatform": false,     "telemetry.telemetryLevel": "off",     "npm.fetchOnlinePackageInfo": false,     "typescript.disableAutomaticTypeAcquisition": true,     "workbench.startupEditor": "none",     "security.workspace.trust.banner": "never",     "security.workspace.trust.emptyWindow": false,     "security.workspace.trust.enabled": false,     "security.workspace.trust.startupPrompt": "never",     "extensions.ignoreRecommendations": true,     "workbench.preferredLightColorTheme": "Default Dark+", }
And monitored the outgoing traffic with tcpdump. From what I captured, vscode periodically generates an suspicious outgoing network connection to the ip address <IP_ADDRESS>. A part of the tcpdump logs are shown in below.
22:47:19.142214 IP localhost.51548 > <IP_ADDRESS>.https: Flags [S], seq<PHONE_NUMBER>, win 64240, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr 0,nop,wscale 7], length 0 22:47:19.169397 IP <IP_ADDRESS>.https > localhost.51548: Flags [S.], seq<PHONE_NUMBER>, ack<PHONE_NUMBER>, win 65535, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>,nop,wscale 9], length 0 22:47:19.169449 IP localhost.51548 > <IP_ADDRESS>.https: Flags [.], ack 1, win 502, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 0 22:47:19.169719 IP localhost.51548 > <IP_ADDRESS>.https: Flags [P.], seq 1:518, ack 1, win 502, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 517 22:47:19.187331 IP <IP_ADDRESS>.https > localhost.51548: Flags [.], ack 518, win 131, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 0 22:47:19.188511 IP <IP_ADDRESS>.https > localhost.51548: Flags [P.], seq 1:100, ack 518, win 131, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 99 22:47:19.188523 IP localhost.51548 > <IP_ADDRESS>.https: Flags [.], ack 100, win 502, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 0
I did not find any information or document related to this suspicious behavior during a brief web search. There is not any known method to turn the behavior off, as the periodic connection persists even when every internet related setting has already been set to false. Generating such suspicious connection and uncontrollable network traffic without user consent is annoying when working in a limited environment, and can even lead to unexpected costs when working under a metered connection. It is also considered as a harm to user privacy and a potential safety issue.
Thus I would like to submit a feature request here, that a setting should be provided to turn off this suspicious connection and free the users from the unexpected periodic network activity. The software should be able to stay silent in an "offline mode" while all the stuff which generates traffic thru internet should be controllable by the user and require user consent.
Thanks for your time.
Loc

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


pubspec.yaml version change not ending up in git release but present on file system

I'm using GitHub Actions and semantic-release and stumbled upon this module, thought I'd give it a try. Pretty simple.
One problem: using @semantic-release/git to create a git release tag. This package logs it is updating the pubspec.yaml file's version, and indeed it seems so, judging by the cat pubspec.yaml command output I stuck in the semantic-release step in my workflow file. The problem is that the change does not get added to git, the CHANGELOG.md file does for instance, but not the pubspec.yaml.
I initially thought it might have to do with my semantic-release plugin order, in which semantic-release-dart was at the end. However, moving it before @semantic-release/git did not seem to fix the problem.
Very weird. Maybe you could have a look. Also, maybe this is a problem with semantic-release in itself? If so please let me know.
Thanks!
.releaserc.yaml:
branches:
  - master
# TODO: Change later!
repositoryUrl: https://github.com/emme1444/analyst-test.git
plugins:
  - "@semantic-release/commit-analyzer"
  - "@semantic-release/release-notes-generator"
  - "semantic-release-dart"
  - "@semantic-release/changelog"
  - "@semantic-release/git"
dryRun: false
debug: true

semantic-release command output, note the last couple lines which was the output of cat pubspec.yaml after semantic-release during the same step in the workflow:
[10:01:58 PM] [semantic-release] › ℹ  Running semantic-release version 17.3.4
[10:01:58 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/changelog"
[10:01:58 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/git"
[10:01:58 PM] [semantic-release] › ✔  Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer"
[10:01:58 PM] [semantic-release] › ✔  Loaded plugin "generateNotes" from "@semantic-release/release-notes-generator"
[10:01:58 PM] [semantic-release] › ✔  Loaded plugin "prepare" from "semantic-release-dart"
[10:01:58 PM] [semantic-release] › ✔  Loaded plugin "prepare" from "@semantic-release/changelog"
[10:01:58 PM] [semantic-release] › ✔  Loaded plugin "prepare" from "@semantic-release/git"
[10:02:03 PM] [semantic-release] › ✔  Run automated release from branch master on repository https://github.com/emme1444/analyst-test.git
[10:02:04 PM] [semantic-release] › ✔  Allowed to push to the Git repository
[10:02:04 PM] [semantic-release] › ℹ  Start step "verifyConditions" of plugin "@semantic-release/changelog"
[10:02:04 PM] [semantic-release] › ✔  Completed step "verifyConditions" of plugin "@semantic-release/changelog"
[10:02:04 PM] [semantic-release] › ℹ  Start step "verifyConditions" of plugin "@semantic-release/git"
[10:02:04 PM] [semantic-release] › ✔  Completed step "verifyConditions" of plugin "@semantic-release/git"
[10:02:04 PM] [semantic-release] › ℹ  Found git tag v1.0.2 associated with version 1.0.2 on branch master
[10:02:04 PM] [semantic-release] › ℹ  Found 2 commits since last release
[10:02:04 PM] [semantic-release] › ℹ  Start step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[10:02:04 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: Merge branch 'master' of https://github.com/emme1444/analyst-test
[10:02:04 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[10:02:04 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: fix(ci): add cat of pubspec.yaml in workflow
[10:02:04 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The release type for the commit is patch
[10:02:04 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analysis of 2 commits complete: patch release
[10:02:04 PM] [semantic-release] › ✔  Completed step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[10:02:04 PM] [semantic-release] › ℹ  The next release version is 1.0.3
[10:02:04 PM] [semantic-release] › ℹ  Start step "generateNotes" of plugin "@semantic-release/release-notes-generator"
[10:02:04 PM] [semantic-release] › ✔  Completed step "generateNotes" of plugin "@semantic-release/release-notes-generator"
[10:02:04 PM] [semantic-release] › ℹ  Start step "prepare" of plugin "semantic-release-dart"
[10:02:04 PM] [semantic-release] [semantic-release-dart] › ℹ  Write version 1.0.3 to pubspec.yaml in /home/runner/work/analyst-test/analyst-test
[10:02:04 PM] [semantic-release] › ✔  Completed step "prepare" of plugin "semantic-release-dart"
[10:02:04 PM] [semantic-release] › ℹ  Start step "prepare" of plugin "@semantic-release/changelog"
[10:02:04 PM] [semantic-release] [@semantic-release/changelog] › ℹ  Update /home/runner/work/analyst-test/analyst-test/CHANGELOG.md
[10:02:04 PM] [semantic-release] › ✔  Completed step "prepare" of plugin "@semantic-release/changelog"
[10:02:04 PM] [semantic-release] › ℹ  Start step "prepare" of plugin "@semantic-release/git"
[10:02:04 PM] [semantic-release] [@semantic-release/git] › ℹ  Found 1 file(s) to commit
[10:02:08 PM] [semantic-release] [@semantic-release/git] › ℹ  Prepared Git release: v1.0.3
[10:02:08 PM] [semantic-release] › ✔  Completed step "prepare" of plugin "@semantic-release/git"
[10:02:08 PM] [semantic-release] › ℹ  Start step "generateNotes" of plugin "@semantic-release/release-notes-generator"
[10:02:08 PM] [semantic-release] › ✔  Completed step "generateNotes" of plugin "@semantic-release/release-notes-generator"
[10:02:16 PM] [semantic-release] › ✔  Created tag v1.0.3
[10:02:16 PM] [semantic-release] › ✔  Published release 1.0.3 on default channel
$ ls -lah
total 60K
drwxr-xr-x 6 runner docker 4.0K Jan 19 22:00 .
drwxr-xr-x 3 runner docker 4.0K Jan 19 22:00 ..
drwxr-xr-x 8 runner docker 4.0K Jan 19 22:02 .git
drwxr-xr-x 3 runner docker 4.0K Jan 19 22:00 .github
-rw-r--r-- 1 runner docker  281 Jan 19 22:00 .gitignore
-rw-r--r-- 1 runner docker  360 Jan 19 22:00 .releaserc.yaml
-rw-r--r-- 1 runner docker 3.2K Jan 19 22:02 CHANGELOG.md
-rw-r--r-- 1 runner docker  12K Jan 19 22:00 LICENSE
-rw-r--r-- 1 runner docker  478 Jan 19 22:00 README.md
-rw-r--r-- 1 runner docker   35 Jan 19 22:00 analysis_options.yaml
drwxr-xr-x 2 runner docker 4.0K Jan 19 22:00 example
drwxr-xr-x 2 runner docker 4.0K Jan 19 22:00 lib
-rw-r--r-- 1 runner docker  253 Jan 19 22:02 pubspec.yaml
$ git status
On branch master
Your branch is ahead of 'origin/master' by 1 commit.
  (use "git push" to publish your local commits)

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   pubspec.yaml

no changes added to commit (use "git add" and/or "git commit -a")
$ cat pubspec.yaml
name: analyst
description: A strict, opinionated linter and analysis configuration for any dart project.
version: 1.0.3

homepage: https://github.com/emme1444/analyst
repository: https://github.com/emme1444/analyst

environment:
  sdk: ">=2.7.0 <3.0.0"

workflow yaml file:
name: cicd

on:
  push:
    branches:
      - master

jobs:
  release:
    name: Release
    runs-on: ubuntu-20.04
    steps:
      - name: Checkout code
        uses: actions/checkout@v2

      - uses: cedx/setup-dart@v2
      - uses: actions/setup-node@v2
        with:
          node-version: 14

      - run: npm install -g "@semantic-release/changelog"
      - run: npm install -g "@semantic-release/git"
      - run: npm install -g "semantic-release-dart"

      - name: Bump version
        run: |
          export NODE_PATH="$(npm root -g)"
          npx semantic-release@17
          ls -lah
          git status
          cat pubspec.yaml
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
      - name: Publish to pub
        run: dart pub publish --dry-run

Did you find a fix for this?

I had the same problem.


Add team search button to nav

fixes #15 by adding a button "Teams" to the top navigation bar at liga.99damage.de
it also removes obsolete code that is no longer needed from the main page (csgo.99damage.de). the function insertDataTablesCss() is still in the code, it can be found in scripts\util\content\util.js, which is used by all other scripts anway. it's not needed for adding the teams button, hence removed from that file.

adjusted the query selection as suggested. rebased. squashed commits and capitalized message. pls review :-)


Game Sprites

We need a way to visualize the game 2d game board with sprites
we need the following transparent images / sprits:

player
box
empty cell
zombie
rock (or could be a card, rubbish, something impassible)

Ready to go! @webdevcody

Player and Zombie @webdevcody


V2

Needs https://github.com/alicemaz/rust-base64/issues/10 to be fixed

See https://lapo.it/asn1js/#30820122300D06092A864886F70D01010105000382010F003082010A0282010100C9113AAC7B8D47441B1CEDC7DCAB76A4E28656142A1995C89CE76E40DC57CEE2A5BD04CB513BF8978B20821E7F098622FDCBC8F925D54FD90F592297C495C15DDFF82E4BDC3EE51A901A0091F87E7A2155321D95AD4C96CA3DCC165D074D517D2B04572C07309111224B79E94E11D1C88C6ECB464C7997F154BE5AACC870D524442C1F07A067C6FC0B47F3D04813D8C304767D74B7A52BD6B5F38CC07FC2F0A0F2F1BC96F7225E679DCA8F7127CA0C3A1D30504831CE254330CA2F982F9A25CB5C1D4018B9BC2818DF13CB372F9C6A8BEC94A1DFA3F0CB6F223F35D9D912E1032245537F6F2DA1DD963C2D8546AEA6576537209F6BA39FCB8A8D72D9543E53750203010001
That public key is inside a SubjectPublicKeyInfo wrapper, but ring expects a SubjectPublicKey, which is inside the SubjectPublicKeyInfo. Try the key as 3082010a0282010100c9113aac7b8d47441b1cedc7dcab76a4e28656142a1995c89ce76e40dc57cee2a5bd04cb513bf8978b20821e7f098622fdcbc8f925d54fd90f592297c495c15ddff82e4bdc3ee51a901a0091f87e7a2155321d95ad4c96ca3dcc165d074d517d2b04572c07309111224b79e94e11d1c88c6ecb464c7997f154be5aacc870d524442c1f07a067c6fc0b47f3d04813d8c304767d74b7a52bd6b5f38cc07fc2f0a0f2f1bc96f7225e679dca8f7127ca0c3a1d30504831ce254330ca2f982f9a25cb5c1d4018b9bc2818df13cb372f9c6a8bec94a1dfa3f0cb6f223f35d9d912e1032245537f6f2da1dd963c2d8546aea6576537209f6ba39fcb8a8d72d9543e53750203010001.

Note also that there is a PR for ring pending which allows it to parse the SubjectPublicKeyInfo structure to extract the SubjectPublicKey inside it. As soon as I have time, I'll work on getting it merged.

I see thanks, I guess I'll wait for that PR then.

@mike-engel I'll take a code/doc review if you have time too!

@Keats That was a quick doc review, I'll try and look through the code for v2 tomorrow or this weekend and see if I find anything 😄

Thanks!
For sign/verify, it's only doing the crypto operation, they are only exposed because they might be needed by other libraries (https://github.com/Keats/rust-jwt/pull/12).
encode/decode is the preferred nomenclature but I should maybe change the export a bit. They also shouldn't be in the crypto module, I pulled them in lib.rs.

:+1:. Just another random user waiting for the serde part.

@lucab If you have any feedback on v2, let me know!

@Keats it looks good overall. I've just left a couple of minor wishlist items. I guess you'll get a bit more feedback on API ergonomicity once this lands in master or in some alpha-level crates.io release.

Beta available from crates.io: https://crates.io/crates/jsonwebtoken/2.0.0-beta-1


PLACEMENT ROADMAP OF ENGINEERING

HOPE IT MAY HELP STUDENTS FOR A CLEAR VISION

Sure. You can work on it

Thank you for your response .will surely work on it
On Tue, 11 Oct 2022, 23:46 Aaryan Arora, @.***> wrote:

Assigned #4 https://github.com/aaryan2134/Engineering-Resources/issues/4
to @Swastik200 https://github.com/Swastik200.
—
Reply to this email directly, view it on GitHub
https://github.com/aaryan2134/Engineering-Resources/issues/4#event-7565302550,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXNS7FQA3NKTVWWEY3VC7JDWCWVGXANCNFSM6AAAAAARCRKAIE
.
You are receiving this because you were assigned.Message ID:
@.***
com>


Relationships Do Not Work Correctly

Laravel-mongodb Version: 3.9.2
PHP Version: 8.1.5
Database Driver & Version: MongoDB 5.0.9 Community

Description:
Related models that BelongsTo a parent which are saved by entering the ID number of the parent object do not work when queried through the normal model methods.
Steps to reproduce

Create a parent model and save it's ID number to memory
Create a related model and save the model using the ID number directly. e.g: $child->save()
Attempt to query the related models from the parent using the normal relationship function.

Expected behaviour
The related model(s) should be loaded as per normal Laravel behaviour.
Actual behaviour
No models are loaded. You MUST save a model using $parent->Related()->save($child) which in certain sections of an application can sometimes be "wasteful" as the parent need not be loaded into memory.

Please ignore. Discovered a scoping issue which caused this behaviour!


Microformats hex sticker

Text should not be slanted. This was a problem with the previous stickers where people oriented the sticker to make the text flat, making the logo mis-aligned.
The "M" should be lowercase according to the microformats brand guidelines (citation needed)

The black background with the three shades of green (also gradient) don't match the other hex-stickers. It feels unbalanced.

@aaronpk closest we have to "brand" guidelines on microformats.org AFAIK: http://microformats.org/wiki/logo logo-text shows clearly lowercase

Also, consider "microformats.org" instead of just "microformats" as the text underneath the sticker. URLs work - says all the billboards, tv shows, etc.


allow changing opts on project settings file (*.sublime-project)

Allow changing opts (as ctags.opts) on project settings.
Use case: I am adding this as I have a particular project with many files, I want to ignore some of them when generating ctags to speed up things, so I have added the following to the project settings file (ex: myproject.sublime-project):
{
  "settings": {
    "ctags.opts"<EMAIL_ADDRESS>  }
}

then I created the file .ctags_ignore containing the folders I want the ctags command to ignore:
node_modules
public/packs

I can't simply add opts to Sublime Text/Packages/User/CTags.sublime-settings as I would need to create a .ctags_ignore file for each project, which I don't want to.
References:

https://forum.sublimetext.com/t/st3-possible-to-change-plugin-settings-in-sublime-project/22264/4
https://newbedev.com/how-to-exclude-multiple-directories-with-exuberant-ctags

Thanks! I'll try get this in a release before the end of the weekend

Did you have time to release it @stephenfin?
Changing of topic.. What do you think about passing by default the flag<EMAIL_ADDRESS>to the ctags command if a file .ctags_ignore exists at the project root folder?

Would you cut a release please @stephenfin? What do you think about passing by default the flag<EMAIL_ADDRESS>to the ctags command if a file .ctags_ignore exists at the project root folder?

Would you cut a release please @stephenfin?

Sorry for the delay: I was on holiday. This is done now.

What do you think about passing by default the flag<EMAIL_ADDRESS>to the ctags command if a file .ctags_ignore exists at the project root folder?

If you can draft a PR includes docs explaining the impact this would have, I'll be happy to review this. TBH though, I haven't used this extension in years so I'm reluctant to make any significant changes here before keeping things working since I have no way to test them myself.


Generated operations are not including the principal, causing compilation errors

Problem statement
When I am working in my project github.com/sul-dlss-labs/permissions_service and I have created a principal permissions_service.Agent which is in agent.go and I generate the server by doing:
swagger generate server -t generated --exclude-main --principal permissions_service.Agent

Then the operations are generated without importing github.com/sul-dlss-labs/permissions_service which causes a compile error.
For example:
// Code generated by go-swagger; DO NOT EDIT.

package operations

// This file was generated by the swagger tool.
// Editing this file might prove futile when you re-run the generate command

import (
	"net/http"

	middleware "github.com/go-openapi/runtime/middleware"
)

// QueryActionHandlerFunc turns a function with the right signature into a query action handler
type QueryActionHandlerFunc func(QueryActionParams, *permissions_service.Agent) middleware.Responder

...

Swagger specification
2.0
Environment
swagger version: 2.0
go version: 1.9
OS:   MacOS 10.13

Curiously, if I change it to --principal models.Agent it does generate the import:
	"github.com/sul-dlss-labs/arepa/generated/models"

Yes. Principals are assumed to be part of the model package. So you may redefine your principal there.
There must be some assumptions anyway. How would the generator know that your struct is defined in this or that package?

@fredbi  when change the package to permissions and I do swagger generate server -t generated --exclude-main --principal permissions.Agent it generates:
permissions "github.com/sul-dlss-labs/permissions-service"

I'm pretty new to go.  This behavior doesn't make sense to me. There seem to be some package names that are acceptable to it and some that are not.  It would be helpful to me if these assumptions are clearly expressed in documentation or in warnings when running the generator.

Sure documentation would be helpful, but there is nobody around to help... :)
I believe this behavior comes from the name mangling.

is the Agent type mentioned in the spec ? if it isn't, then the x-go-type annotation might solve this issue for you. https://github.com/go-swagger/go-swagger/blob/master/fixtures/codegen/existing-model.yml#L84-L88

in many go tools, packages are assumed to only exist out 1 word so they want the package to be github.com/sul-dslss-labs/permissions/service


Syntax highlight error for comments

Hello guys, thank you for this amazing plugin!
I found a problem with comments and highlights for them. See a screenshot below.

Source:
<!--<Meta
  title="Button"
  component={Button}
  argTypes={{
    disabled: {
      name: 'disabled',
      description: 'Disabled state of button',
      defaultValue: false,
      type: 'boolean',
      control: 'boolean',
    },
  }}
/>

<!-- https://github.com/storybookjs/storybook/issues/11542 -->
<!-- https://github.com/storybookjs/storybook/issues/11813 -->

<!-- export const Template = (args) => <Button {...args} style={{ marginRight: 'var(--fr-size-xs)' }} />; -->

<!-- How to write styles
<style>{`
  .subheading {
    --mediumdark: '#999999';
    font-weight: 900;
    font-size: 13px;
  }
`}</style>
-->

I found that this syntax <!--I'm a comment--> will be removed in favor of {/*I'm a comment*/}, but I think it's good to support both.
https://github.com/mdx-js/mdx/pull/1039

fixed the MDX part (so no any errors now). Unfortunately "proper" comments-like highlighting should be implemented on the markdown plugin side.
The fix is available only for the upcoming 2020.3. If it is a big issue for you, please let me know. I will try to backport the fix to 2020.2.


Hugo v0.123.1 breaks sites

Preliminary Checks

[X] This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/HugoBlox/hugo-blox-builder/issues?q=is%3Aissue
[X] This issue is not a question, feature request, or anything other than a bug report directly related to Hugo Blox Builder. Please post those things on Discord: https://discord.gg/z8wNYzb

Description
Recently upgraded my Hugo to 0.123.1. I have a website the theme-academic-cv theme. I get the following error when running Hugo locally:
ERROR render of "section" failed: "/home/pascal/.cache/hugo_cache/modules/filecache/modules/pkg/mod/github.com/!hugo!blox/hugo-blox-builder/modules/blox-bootstrap/v5@v5.9.6/layouts/_default/baseof.html:11:403": execute of template failed: template: section/publication.html:11:403: executing "section/publication.html" at <.File.UniqueID>: can't evaluate field File in type *source.File
ERROR render of "page" failed: "/home/pascal/.cache/hugo_cache/modules/filecache/modules/pkg/mod/github.com/!hugo!blox/hugo-blox-builder/modules/blox-bootstrap/v5@v5.9.6/layouts/_default/baseof.html:11:403": execute of template failed: template: project/single.html:11:403: executing "project/single.html" at <.File.UniqueID>: can't evaluate field File in type *source.File
ERROR render of "home" failed: "/home/pascal/.cache/hugo_cache/modules/filecache/modules/pkg/mod/github.com/!hugo!blox/hugo-blox-builder/modules/blox-bootstrap/v5@v5.9.6/layouts/_default/baseof.html:11:403": execute of template failed: template: index.html:11:403: executing "index.html" at <.File.UniqueID>: can't evaluate field File in type *source.File
ERROR render of "page" failed: "/home/pascal/.cache/hugo_cache/modules/filecache/modules/pkg/mod/github.com/!hugo!blox/hugo-blox-builder/modules/blox-bootstrap/v5@v5.9.6/layouts/_default/baseof.html:11:403": execute of template failed: template: publication/single.html:11:403: executing "publication/single.html" at <.File.UniqueID>: can't evaluate field File in type *source.File
Total in 242 ms
Error: error building site: render: failed to render pages: render of "page" failed: "/home/pascal/.cache/hugo_cache/modules/filecache/modules/pkg/mod/github.com/!hugo!blox/hugo-blox-builder/modules/blox-bootstrap/v5@v5.9.6/layouts/_default/baseof.html:11:403": execute of template failed: template: publication/single.html:11:403: executing "publication/single.html" at <.File.UniqueID>: can't evaluate field File in type *source.File

According to filenames, I don't think it's specific to the theme I use.
The error disappears when I downgrade Hugo to 0.122.0.
Reproduction Link
N/A
Steps to Reproduce

Create a Hugo website with theme-academic-cv theme.
Run Hugo locally with 0.123.1 version

Expected Result
Default website should compile.
Actual Result
Cannot render defaut website (see description above).
What Hugo Module versions does your site use?
module my_website
go 1.15
require (
github.com/HugoBlox/hugo-blox-builder/modules/blox-bootstrap/v5 v5.9.6
github.com/HugoBlox/hugo-blox-builder/modules/blox-plugin-netlify v1.1.2-0.20231108141515-0478cf6921f9
github.com/HugoBlox/hugo-blox-builder/modules/blox-plugin-reveal v1.1.2
)
What operating system(s) are you seeing the problem on?
Linux
What browser(s) are you seeing the problem on?
Firefox
Which Hugo Blox template are you using?
Academic CV
What version of Hugo are you using?
Hugo Extended 0.123.1

I've had this same problem and it seems to be affecting my old Wowchemy site also which previously would be build fine and now with no code changes is broken.

The compatible version of Hugo for your site can be found in your netlify.toml file or your GitHub Workflow file in the .github folder.
Other versions of Hugo are incompatible so it's not recommended to install buggy new versions of Hugo unless you are helping to test and contribute compatibly for new versions.
The Hugo devs do not use standard semantic versioning, so the Hugo devs make breaking changes in minor/patch versions rather than incrementing the major version. In fact the major version of Hugo is still v0 even after approximately hundreds of updates with breaking changes.
The Hugo devs state that the latest version of Hugo, Hugo v0.123, is a complete redesign of Hugo with many breaking changes. As per Hugo GitHub Issues, there are also several major bugs which are causing sites to fail. It's never recommended to update to the latest version of Hugo as there are almost always major bugs or breaking changes.
If you wish to help file a Hugo bug report for the issues or submit a PR to add compatibly for v0.123 (assuming the reason your site fails is a feature of v0.123 and not a bug), you're welcome :)

Initial compatibility has been added in the new blox-bootstrap v5.9.7 - See 623ca31a5fa3ec05a4fea2f766c145fd557aa1ab
The Academic CV template runs fine on Hugo v0.123 with this compatibility release of blox-bootstrap v5.9.7.
There may still be other breaking changes and Hugo bugs impacting sites attempting to use Hugo v0.123 since it's a major rewrite of Hugo.


Better composable XMLs support

I'd like to compose XMLs with functions. That works but solution is a bit noisy:
use format_xml::xml;

fn f(x: u8, y: u8) -> String {
    let result = xml! {
        {x}
        {y}
    }
    .to_string();
    result
}

fn main() {
    let x = xml! {
        <C>
            {f(1, 2)}
        </C>
        <C>
            {f(2, 1)}
        </C>
    }
    .to_string();
    println!("{}", x);
}

Removing intermediate result variable
fn f(x: u8, y: u8) -> String {
    xml! {
        {x}
        {y}
    }
    .to_string()
}

causes unobvious compiler error:
error: expected expression, found `.`
 --> src/main.rs:8:5
  |
8 |     .to_string()
  |     ^ expected expression

error[E0308]: mismatched types
 --> src/main.rs:4:5
  |
4 | /     xml! {
5 | |         {x}
6 | |         {y}
7 | |     }
  | |     ^
  | |     |
  | |_____expected `()`, found struct `std::fmt::Arguments`
  |       help: consider using a semicolon here
  |
  = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

Which can be fixed by wrapping xml! macros usage with () or {}:
fn f(x: u8, y: u8) -> String {
    (xml! {
        {x}
        {y}
    })
    .to_string()
}

Returning std::fmt::Arguments without constructing intermediate String would be even better, but I didn't find a way to satisfy borrow checker.

Thanks for opening this issue!
The unobvious compile error is mysterious. The macro expands to
format_args !
          (concat!(concat!(concat!(concat!(concat!(concat!(concat!(concat!(concat!(concat!(concat!(concat!(concat!(concat!("", "<"), stringify ! (A)), ">"), "{}"),
                  "</"),
                  stringify ! (A)),
                  ">"),
                  "<"),
                  stringify ! (B)),
                  ">"),
                  "{}"),
                  "</"),
                  stringify ! (B)),
                  ">"),
           x, y)

When I manually replace the xml! invocation with that monstrosity then everything works as expected! I suspect a bug in Rust's parser interaction with macro output but I will need to do a deeper investigation,
In any case there's a better way to implement this. As you've noticed you cannot return std::fmt::Arguments by value as they capture their arguments by reference. These are references to local variables in your function and won't be valid when your function returns.
For the specific purpose of composability I added the following syntax:
// Can also accept &mut std::fmt::Formatter directly
fn f(f: &mut dyn std::fmt::Write, x: u8, y: u8) -> std::fmt::Result {
    f.write_fmt(xml! {
        {x}
        {y}
    })
}

fn main() {
    xml::println! {
        <C>
            |f| {f2(f, 1, 2)}
        </C>
        <C>
            |f| {f2(f, 1, 2)}
        </C>
    };
}

The idea is that you can pass the underlying formatter through just like if you would write an fmt trait implementation. This should be sufficient for composability. So instead of returning an Arguments structure, accept a formatter and write directly into it.
That said when I run this code I get error[E0658]: attributes on expressions are experimental because I try to wrap the resulting println's in a #[inline(never)] annotation to keep all the code generated for the formatting contained. No idea why I didn't catch this earlier. Using the xml! { .. }.to_string() does not have this problem.

Thanks! This write_fmt-based solution would be great to see in readme as well.

Ok after some investigation the weird error you're getting for xml!{}.to_string() is apparently by design. The RFC which specifies this behavior can be found here.
What is happening is that a macro invoked with {} always expands to a statement. In Rust statements are expressions typed (). When applied to the example xml!{}.to_string() the parser takes xml!{} and turns it into a statement expecting a () type, but instead gets the std::fmt::Arguments type. Following a statement with . is also an error.
It's trivial to induce the same error with standard library macros: concat!{""}.to_string() gives the same error.
The compiler then attempts to provide suggestions which are unhelpful. It thinks to make your statement work that adding an explicit ; will throw away the value properly resulting in (). Instead it should print a suggestion to use brackets or parentheses instead.

Thanks for the investigation! From the same thread:

macros invoked with {} can be used as statements, where as macros invoked with [] or () are always expressions

This seems to be true, because this compiles as well:
fn f(x: u8, y: u8) -> String {
    xml!(
        {x}
        {y}
    )
    .to_string()
}

Maybe it's better to use xml!(...) (or xml![...]) instead of xml! {...} everywhere in the readme to make it hard to run into the weird error?

Yeah I'm considering it. I really like the {} for multiline expressions but this potential confusion is problematic. I'm also considering using full statements in the examples instead of what I have now.
But this is for later. In the meantime I rewrote a bunch of code again (see fresh branch) related to utilities to format comma and space-delimited items.


mysql2 chef gem failing to install

Cookbook version
[0.6.14] - actually, latest master branch
Chef-client version
[14.2]
Platform Details
[CentOS 7]
Scenario:
[Install mysql2 Chef Gem]
Steps to Reproduce:
[If you are filing an issue what are the things we need to do in order to repro your problem? How are you using this cookbook or any resources it includes?]

Including 'percona::server' in run list:

include_recipe 'percona::server'
mysql2_chef_gem 'default' do
  provider Chef::Provider::Mysql2ChefGem::Percona
  action :install
end

In 'metadata.rb' I have:

depends     'percona'
depends     'mysql2_chef_gem'

In 'Berksfile' I have:

source 'https://supermarket.chef.io'
metadata
cookbook 'percona', git: 'https://github.com/sous-chefs/percona.git'

Expected Result:
[What are you expecting to happen as the consequence of above reproduction steps?]
To have Percona Server and mysql2 gem installed
Actual Result:
[What actually happens after the reproduction steps? Include the error output or a link to a gist if possible.]
mysql2 gem failing to install due to missing development libraries.
[2018-07-19T11:13:34+00:00] FATAL: Mixlib::ShellOut::ShellCommandFailed: mysql2_chef_gem_mysql2_chef_gem_mysql[default] (tkis_percona::default line 18) had an error: Mixlib::ShellOut::ShellCommandFailed: chef_gem[mysql2] (/tmp/kitchen/cache/cookbooks/percona/libraries/provider_mysql2_chef_gem.rb line 19) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
       ---- Begin output of /opt/chef/embedded/bin/gem install mysql2 -q --no-rdoc --no-ri -v "0.5.2" --source=https://www.rubygems.org ----
       STDOUT: Building native extensions. This could take a while...
       STDERR: ERROR:  Error installing mysql2:
       	ERROR: Failed to build gem native extension.

           current directory: /opt/chef/embedded/lib/ruby/gems/2.5.0/gems/mysql2-0.5.2/ext/mysql2
       /opt/chef/embedded/bin/ruby -r ./siteconf20180719-15481-d9i0j2.rb extconf.rb
       checking for rb_absint_size()... yes
       checking for rb_absint_singlebit_p()... yes
       checking for rb_wait_for_single_fd()... yes
       checking for -lmysqlclient... no
       -----
       mysql client is missing. You may need to 'apt-get install libmysqlclient-dev' or 'yum install mysql-devel', and try again.

Adding
package "Percona-Server-devel-#{node['percona']['version'].tr('.', '')}"
to the recipe before calling 'mysql2_chef_gem' is solving the issue.

Hi @vgirnet
We have released numerous fixes for this cookbook since this issue was raised, could you check if this is still an issue please?
Thanks !

Hello,
I have checked with latest version, mysql2 gem was installed correctly from the first run.
I've got other issues, not related to this one:
There are 2 singing keys for Percona RPMS. The second one worked for newer packages.
https://www.percona.com/downloads/RPM-GPG-KEY-percona - For Percona RPM packages signed on or before December 20th, 2018
https://repo.percona.com/yum/PERCONA-PACKAGING-KEY- For Percona RPM packages signed on or after December 20th, 2018
https://www.percona.com/downloads/
Looks like you need to adjust repositories configuration as well.

could you open new issues for those ones if not already open please and close this one off if completed @vgirnet ?
Thanks


inference error

When i use transformer decoder to inference, i meet some troubles:1.infer_greedy mode returns two str('sample_id' and 'log_prob'). 2.beam search may get a seq that length much longer than max_decoding_length.
I'm so upset :((((, and i check my code, it follows your 'transformer_decoder_test.py'. So,some bugs exist in this repository？

 Does (test_decode_infer_greedy)[https://github.com/asyml/texar/blob/master/texar/modules/decoders/transformer_decoders_test.py#L104] work as you expected?

I uninstall this ,and use other repository now...

I guess that probably you installed an older version of Texar, while the document you read was updated to the latest version. You may reinstall the latest Texar if you'd like to try again.


User Guide Documentation

Flesh out the User Guide, complete with png/gif shots for ease of use.

The docs look fine for now, but what I am probably going to do is merge this pull request and then just update the readme directly from Master because it's fast and it doesn't affect other parts of the source code.

Ok, Thanks.


Create student-gymp.txt

Official Website: https://gymnasium-puchheim.de/
https://www.gymnasium-puchheim.de/informatik/
student-gymp.de is used for student e-mail-addresses and web projects only.

@FDHoho007 Please provide us with a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students. A copy of official instruction given at the enrollment time or sent to you by email is OK.

@FDHoho007 I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the aforementioned issue. Thank you for the understanding!


More readable changelogs

While many open source projects impose guidelines to maintain good log messages, the mediapipe commit history contains no commit messages at all.
Maybe use http://www.catb.org/esr/reposurgeon/ for git import?

@abitrolly This is due to the project use of internal Google tools to do code transformation. Thanks for your suggestion and we will take it into consideration in the future @jiuqiant

@mgyong so what tools do you use except https://github.com/google/copybara ?

@mgyong so did you consider adding change logs here?

I'd like to know if it's worth the hassle to upgrade from 0.8.8 to <IP_ADDRESS> and what could go wrong if I go straight to <IP_ADDRESS>

Found that releases at https://github.com/google/mediapipe/releases contain tiny tag on the left with actual version that I haven't spotted before. No <IP_ADDRESS> or <IP_ADDRESS> info, but already useful.


update_fastlane and check_version_conflict

Hi,
I'm running fastlane ios release with update_fastlane option then getting this stack trace:
(EDIT: even without update_fastlane option I still getting this error)
fastlane ios release
-----------------------------
--- Step: update_fastlane ---
-----------------------------
Updating produce from 0.3.4 to 0.3.5 ... 🚀
Finished updating produce
fastlane.tools succesfully updated! I will now restart myself... 😴
/Users/zakhej/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rubygems/specification.rb:2100:in `check_version_conflict': can't activate mime-types-2.6.1, already activated mime-types-1.25.1 (Gem::LoadError)
from /Users/zakhej/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rubygems/specification.rb:1276:in `activate'
	from /Users/zakhej/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rubygems.rb:216:in `block in finish_resolve'
	from /Users/zakhej/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rubygems.rb:215:in `each'
	from /Users/zakhej/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rubygems.rb:215:in `finish_resolve'
	from /Users/zakhej/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rubygems/rdoc.rb:14:in `<top (required)>'
	from /Users/zakhej/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:121:in `require'
	from /Users/zakhej/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:121:in `require'
	from /Users/zakhej/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rubygems/commands/update_command.rb:9:in `<top (required)>'
	from /Users/zakhej/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:121:in `require'
	from /Users/zakhej/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:121:in `require'
	from /Users/zakhej/.rvm/gems/ruby-2.2.0@global/gems/fastlane-1.6.0/lib/fastlane/actions/update_fastlane.rb:2:in `<top (required)>'
	from /Users/zakhej/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:121:in `require'
	from /Users/zakhej/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:121:in `require'
	from /Users/zakhej/.rvm/gems/ruby-2.2.0@global/gems/fastlane-1.6.0/lib/fastlane/actions/actions_helper.rb:129:in `block in load_default_actions'
	from /Users/zakhej/.rvm/gems/ruby-2.2.0@global/gems/fastlane-1.6.0/lib/fastlane/actions/actions_helper.rb:128:in `each'
	from /Users/zakhej/.rvm/gems/ruby-2.2.0@global/gems/fastlane-1.6.0/lib/fastlane/actions/actions_helper.rb:128:in `load_default_actions'
	from /Users/zakhej/.rvm/gems/ruby-2.2.0@global/gems/fastlane-1.6.0/lib/fastlane.rb:21:in `<module:Fastlane>'
	from /Users/zakhej/.rvm/gems/ruby-2.2.0@global/gems/fastlane-1.6.0/lib/fastlane.rb:18:in `<top (required)>'
	from /Users/zakhej/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:69:in `require'
	from /Users/zakhej/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:69:in `require'
	from /Users/zakhej/.rvm/gems/ruby-2.2.0@global/gems/fastlane-1.6.0/bin/fastlane:5:in `<top (required)>'
	from /Users/zakhej/.rvm/rubies/ruby-2.2.0/bin/fastlane:23:in `load'
	from /Users/zakhej/.rvm/rubies/ruby-2.2.0/bin/fastlane:23:in `<main>'
	from /Users/zakhej/.rvm/gems/ruby-2.2.0/bin/ruby_executable_hooks:15:in `eval'
	from /Users/zakhej/.rvm/gems/ruby-2.2.0/bin/ruby_executable_hooks:15:in `<main>'

I do not know what is mime-types and why I got two versions on my system, but after uninstalling mime-types-2.6.1 fastlane command goes well.
Does anyone know how to fix this and explain such situation?

I'm encountering similar issues.. I have tried to uninstall and i'm getting nowhere.
MobileGoo:~ jamiesciban$ fastlane --v
/Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems/specification.rb:2100:in check_version_conflict': can't activate mime-types-2.6.1, already activated mime-types-1.25.1 (Gem::LoadError) 	from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems/specification.rb:1276:in activate'
from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems.rb:216:in block in finish_resolve' 	from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems.rb:215:in each'
from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems.rb:215:in finish_resolve' 	from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems/rdoc.rb:14:in <top (required)>'
from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:121:in require' 	from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:121:in require'
from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems/commands/update_command.rb:9:in <top (required)>' 	from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:121:in require'
from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:121:in require' 	from /Users/jamiesciban/.rvm/gems/ruby-2.2.1/gems/fastlane-1.6.0/lib/fastlane/actions/update_fastlane.rb:2:in <top (required)>'
from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:121:in require' 	from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:121:in require'
from /Users/jamiesciban/.rvm/gems/ruby-2.2.1/gems/fastlane-1.6.0/lib/fastlane/actions/actions_helper.rb:129:in block in load_default_actions' 	from /Users/jamiesciban/.rvm/gems/ruby-2.2.1/gems/fastlane-1.6.0/lib/fastlane/actions/actions_helper.rb:128:in each'
from /Users/jamiesciban/.rvm/gems/ruby-2.2.1/gems/fastlane-1.6.0/lib/fastlane/actions/actions_helper.rb:128:in load_default_actions' 	from /Users/jamiesciban/.rvm/gems/ruby-2.2.1/gems/fastlane-1.6.0/lib/fastlane.rb:21:in module:Fastlane'
from /Users/jamiesciban/.rvm/gems/ruby-2.2.1/gems/fastlane-1.6.0/lib/fastlane.rb:18:in <top (required)>' 	from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:69:in require'
from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:69:in require' 	from /Users/jamiesciban/.rvm/gems/ruby-2.2.1/gems/fastlane-1.6.0/bin/fastlane:5:in <top (required)>'
from /Users/jamiesciban/.rvm/gems/ruby-2.2.1/bin/fastlane:23:in load' 	from /Users/jamiesciban/.rvm/gems/ruby-2.2.1/bin/fastlane:23:in '
from /Users/jamiesciban/.rvm/gems/ruby-2.2.1/bin/ruby_executable_hooks:15:in eval' 	from /Users/jamiesciban/.rvm/gems/ruby-2.2.1/bin/ruby_executable_hooks:15:in '
MobileGoo:~ jamiesciban$ sudo gem uninstall fastlane
Password:
MobileGoo:~ jamiesciban$ fastlane --v
/Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems/specification.rb:2100:in check_version_conflict': can't activate mime-types-2.6.1, already activated mime-types-1.25.1 (Gem::LoadError) 	from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems/specification.rb:1276:in activate'
from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems.rb:216:in block in finish_resolve' 	from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems.rb:215:in each'
from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems.rb:215:in finish_resolve' 	from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems/rdoc.rb:14:in <top (required)>'
from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:121:in require' 	from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:121:in require'
from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems/commands/update_command.rb:9:in <top (required)>' 	from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:121:in require'
from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:121:in require' 	from /Users/jamiesciban/.rvm/gems/ruby-2.2.1/gems/fastlane-1.6.0/lib/fastlane/actions/update_fastlane.rb:2:in <top (required)>'
from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:121:in require' 	from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:121:in require'
from /Users/jamiesciban/.rvm/gems/ruby-2.2.1/gems/fastlane-1.6.0/lib/fastlane/actions/actions_helper.rb:129:in block in load_default_actions' 	from /Users/jamiesciban/.rvm/gems/ruby-2.2.1/gems/fastlane-1.6.0/lib/fastlane/actions/actions_helper.rb:128:in each'
from /Users/jamiesciban/.rvm/gems/ruby-2.2.1/gems/fastlane-1.6.0/lib/fastlane/actions/actions_helper.rb:128:in load_default_actions' 	from /Users/jamiesciban/.rvm/gems/ruby-2.2.1/gems/fastlane-1.6.0/lib/fastlane.rb:21:in module:Fastlane'
from /Users/jamiesciban/.rvm/gems/ruby-2.2.1/gems/fastlane-1.6.0/lib/fastlane.rb:18:in <top (required)>' 	from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:69:in require'
from /Users/jamiesciban/.rvm/rubies/ruby-2.2.1/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:69:in require' 	from /Users/jamiesciban/.rvm/gems/ruby-2.2.1/gems/fastlane-1.6.0/bin/fastlane:5:in <top (required)>'
from /Users/jamiesciban/.rvm/gems/ruby-2.2.1/bin/fastlane:23:in load' 	from /Users/jamiesciban/.rvm/gems/ruby-2.2.1/bin/fastlane:23:in '
from /Users/jamiesciban/.rvm/gems/ruby-2.2.1/bin/ruby_executable_hooks:15:in eval' 	from /Users/jamiesciban/.rvm/gems/ruby-2.2.1/bin/ruby_executable_hooks:15:in '

Can you try running sudo gem cleanup?

The cleanup doesn't seem to work for me.
Cleaning up installed gems...
Clean Up Complete

Still same error.

Maybe @milch can help? :smiley:

Hmm, interesting. I've now also encountered this error when running on a CI, even without update_fastlane. I'll look into it.

It seems to work if we put an explicit dependency on mime-types 1.25 in the gem specification. I sent a pull request over at #392.
As far as I can tell, this is a bug in the rubygems dependency resolver. The crash occurs when we try to load the rubygems package, which is when rubygems tries to resolve all unmet dependencies. For some reason, it thinks that mime-types isn't loaded yet and then crashes with that error message, because mime-types IS loaded with a different version (that already satisfies the requirements).

I got it working by deleting everything and reinstalling. However after 1-2 days it start giving that error again without us touching the config.


method

may I ask you if your method is a part of distant supervise, thank you

Yes, it is. See Section 3. in the paper: http://aclweb.org/anthology/D17-1188

Hi, the model was learned completely distantly supervised. Does it answer your question?

You have solved my question. Thank you very much.


Move to semantic versioning ... soon

Once this library is a bit more mature I'd like to move to semantic versioning via semantic release

Done 🥳