text:
Display issue - conflicting with Architect Plugin?

Description
Getting some funky characters in my side bar whenever I turn this plugin on whilst having Architect enabled (v.2.2.8)

Also tried removing the custom svg icons from the new entries in the sidenav to see if it was those messing it up, and makes no difference either.
Steps to reproduce

Install CP Nav
Turn CP Nav on
Install Architect
Turn Architect on

Additional info

CP Nav Plugin version: 2.0.4
Craft version: 3.0.2

That bug is happening with other plugins that have an option on the sidebar. I have SEOmatic and Sprout Forms, but not Architect and it's happening to me.

Same with SEOmatic.

It actually only looks to be happening on my staging and local environements now, which is odd as it was doing it on all 3 at one point. Here are the environment details (all the same across each one)

PHP version 7.1.17
MySQL 5.5.60
Imagick 3.4.3 (ImageMagick 6.8.9-9)
Craft Pro 3.0.5
Yii 2.0.15.1
Twig 2.4.8
Guzzle 6.3.3
Imagine 0.7-dev

Plugins:

Browser is Firefox Quantum 59.0.2 (64-bit), also occuring on Safari Version 11.0.1 (12604.3.5.1.1) & Chrome Version 66.0.3359.139
Running MacOS Sierra 10.12.6 (16G29)
Issues occur instantly after other plugins, but only seems to affect those items in the sidebar that are below a custom one added via your plugin. If you disable your plugin, the issue goes.
No errors in the console log either :/

Fixed in 2.0.6.

authors: chillibe engram-design ljclark mikestecker

repo: verbb/cp-nav


text:
Adding react-native spanish translation

Updating existing pages ✍

-Update react-native for spanish lenguage
Description
I have added the spanish version of react-native.

[ ] Adding new page
[x] Updating existing documentation
[ ] Other updates

@shuding @huozhi Could you see and review this?Thanks.

source: gharchive/pull-request

repo: vercel/swr-site

license_type: permissive

license_source: github-api


text:
Trigger typing breaks typescript inference because of missing export

Bug report
Description / Observed Behavior
Since Version 2.2.0 the new typing of the trigger function of useSwrMutation breaks type inference if its used in an own NPM module.
Exported variable 'useMutateApi' has or is using name 'TriggerWithArgs' from external module "C:/projekte/Intern/Libraries/nfq-typed-next-api/node_modules/.pnpm/swr@2.2.1_react@18.2.0/node_modules/swr/mutation/dist/index" but cannot be named.ts(4023)
Exported variable 'useMutateApi' has or is using name 'TriggerWithOptionsArgs' from external module "C:/projekte/Intern/Libraries/nfq-typed-next-api/node_modules/.pnpm/swr@2.2.1_react@18.2.0/node_modules/swr/mutation/dist/index" but cannot be named.ts(4023)
Exported variable 'useMutateApi' has or is using name 'TriggerWithoutArgs' from external module "C:/projekte/Intern/Libraries/nfq-typed-next-api/node_modules/.pnpm/swr@2.2.1_react@18.2.0/node_modules/swr/mutation/dist/index" but cannot be named.ts(4023)
Expected Behavior
It would help to at least export these types so typescript can use them on compile time to include them in its own generated *.d.ts file.
Repro Steps / Code Example
/**
 * Get request hook.
 *
 * @param url        API URL.
 * @param swrOptions SWR options.
 * @returns SWR response.
 */
export const useMutateApi = <T extends ApiMethod>(
    url: string | null,
    swrOptions?: SWRMutationConfiguration<Jsonify<ApiResponse<T>['data']>, any> | undefined
) => {
    const {
        data,
        error,
        isMutating,
        reset,
        trigger
    } = useSwrMutation<Jsonify<ApiResponse<T>['data']>, RequestError<T>, Key, MutationRequestOptions<T>>(
        url ? `${basePath}${url}` : null,
        mutationFetcher,
        swrOptions
    );

    return {
        data,
        error,
        isMutating,
        reset,
        trigger
    };
};

Additional Context
SWR version.
Since Version 2.2.0

when will this fix be live?

source: gharchive/issue

authors: ckruppe der-daniel monolithed

repo: vercel/swr

license: MIT


text:
Watch task outputs to avoid cache restorations

Start a daemon, notify it of output globs when a task completes, watch those outputs, check if we can skip cache restores on subsequent runs.
Uses grpc and protobuf for communication.
Before shipping:

[ ] Wire up --no-daemon flag to run
[ ] Add command for daemon status
[ ] Add command for daemon stop
[ ] Add command for daemon start
[ ] Add command for daemon restart
[ ] Proper daemon logfile management
[x] Ensure that the client tries to start the server after maybe killing a previous incarnation
[x] Investigate golang internal lockfile
[ ] Verify ordering guarantees on file-watching
[ ] Sort out proper syntax for protos in Makefile

On the topic of ensuring that we aren't racing with the filesystem event notifications, watchman uses cookies. We briefly discussed this idea as "writing to a well known file after an operation completes, then waiting for that event". They also have some caveats re: FSEvents on macOS. We are not currently using FSEvents, as that requires CGO. https://facebook.github.io/watchman/docs/cookies.html
More investigation is still required here.

After the first pass review, and looking over the use of the unix domain socket and pid files, I'm going to make some changes to how we implement the checks for the server being alive. I think the best path forward is to synchronize on the pid file. Whoever owns the pid file is allowed to do whatever they want with the socket file. The server will attempt to lock the pid file, and on success delete any existing socket file and create their own.
The client will try to find a live process matching the pid file. If the pid file does not exist, try starting a server. If it exists but the server is not responding, try killing it. If the pid file exists but has no matching process, delete it and try starting a server, or report an error to have the user delete the pid file. At no point will the client manipulate the socket file.
It is possible for two clients to race trying to delete a pid file and start a new server, so it may be better to just report an error, or allow for this behavior to be controlled via flag (--force-daemon or something).

Investigated golang internal lockfile. I think it's overkill for what we need, especially given that we'd have to do some work to use it, but if someone publishes a nice library around it, we could potentially drop it in.

@nathanhammond I'm removing the WIP label as I think this is ready for review to merge to main for a "dark launch". Daemon usage is behind a hidden, opt-in flag.

@nathanhammond I decided to go back and remove context instances from a few structs, and I think it's resulted in a little bit of a better design, particularly on client side and in run.go.

Whew, ok, I've managed to get CI to pass w/o the checked-in generated code from protobufs. Our Makefile is not really cross-platform, which makes it a challenge to do. We ought to address that.
@nathanhammond I think it's back over to you at this point.

@nathanhammond I think I've addressed everything, but rather than extract pidLock, I nuked it and [hopefully] simplified the code there after reading a bit more about signaling, as well as running some experiments. I'll let you hit the button if you're still on board, otherwise we can go over it.
Quick summary is that the defer from runTurboServer should always run, as long as we don't get SIGKILL, which we don't catch anyways.

repo: vercel/turborepo


text:
TEST PR

Description

Testing Instructions

Great work, @anthonyshew, but we don't want your silly test PRs in our repo.


text:
Added Agility CMS support.

Adds support for Agility CMS.

This has been replaced by #19 😄

authors: joelvarty leerob

repo: vercel/virtual-event-starter-kit


text:
Feature73 - Get number of active DIDs

Contract updated
Test code updated

@ITStar10 I see you are managing a counter for this which is fine, however I had expected you could do something like _isRegistered.length. Is that possible?
Also, is there any way to iterate through every registered DID?

Update VDA-DID-Registry contract.
Now we can iterate through every active DIDs.
Do we need a function to get all active DIDs?

repo: verida/blockchain-contracts


text:
Unable to set capabilities报错

重装过libcap-bin也不行，日志如下
2021-03-11 10:07:31 Error: Get General 'redir-port' Option Error, OpenClash Can Not Start With Raw Config File
2021-03-11 10:07:31 Error: Get DNS 'enhanced-mode' Option Error, OpenClash Can Not Start With Raw Config File
2021-03-11 10:07:31 Error: Get DNS 'listen' Option Error, OpenClash Can Not Start With Raw Config File
2021-03-11 10:07:31 Error: OpenClash Can Not Start, Try Use Raw Config Restart Again
Unable to set capabilities [--caps=cap_sys_resource,cap_dac_override,cap_net_raw,cap_net_bind_service,cap_net_admin+eip]
2021-03-11 10:07:31 Error: OpenClash Can Not Start, Try Use Backup Rules Start Again
Unable to set capabilities [--caps=cap_sys_resource,cap_dac_override,cap_net_raw,cap_net_bind_service,cap_net_admin+eip]
2021-03-11 10:07:31 Warning: Because of The Different Porxy-Group's Name, Stop Setting The Other Rules!

解决了，原因是没给sys_resource的权限

解决了，原因是没给sys_resource的权限

咋改的啊

repo: vernesong/OpenClash


text:
疑似bug 看门狗进程不会自动退出

重启/重载几次openclash就有几个看门狗进程，懒得捉虫了，应该是重启或者重载的时候没有加kill watchdog导致

可能你需要测试一下kill -9是否正常。
watchdog_pids=$(ps |grep openclash_watchdog.sh |grep -v grep |awk '{print $1}' 2>/dev/null)
    for watchdog_pid in $watchdog_pids; do
        kill -9 "$watchdog_pid" >/dev/null 2>&1
    done

之后看了看脚本没发现啥问题，也不知道咋搞出来的。等我啥时候再复现再来提交详细过程吧，目前是直接把看门狗启动的部分都注释掉了

authors: Mosney vernesong


text:
有没有可能加个选项让 OpenClash 完全不管 dnsmasq

我现在的方案是自己做套dns解析，chinadns+smartdns还是功能更强一些。
而现在有个问题是OpenClash重启时总是会把 dnsmasq 里 Ignore resolve file 这一项改回来😂

自己去启动脚本注释一下命令就行了啊

自己去启动脚本注释一下命令就行了啊

我现在就是这么做的。
只是提个建议。
fake-ip tun模式出来后大部分流量其实可以使用real ip了。
我现在的方案：
chinadns -- smartdns cn group -- carrier dns
\  smartdns global group -- dns-https-proxy -- clash socks5 port -- 8.8.8.8 1.1.1.1
smartdns 设规则，像zoom.us这种返回 anycast ip 的查 clash 内置 dns 走 fake-ip
clash 只激活geoip规则，和少数域名规则。如此可兼具兼容性和分流的准确性。
唯一的问题是clash tun模式性能还是差了点。

authors: LitingLin vernesong


text:
ERROR: replication slot "debezium" already exists

flink 1.11.2
postgresql 12
ES 6.8.2
我在使用cdc 同步postgresql里的数据到ES6中，报如下错误：
Caused by: io.debezium.DebeziumException: Creation of replication slot failed; when setting up multiple connectors for the same database host, please make sure to use a distinct replication slot name for each
Caused by: org.postgresql.util.PSQLException: ERROR: replication slot "debezium" already exists
请问是否有解决这个问题的方法或者什么原因导致的错误

Note: debezium.slot.name is recommended to set for different tables to avoid the potential PSQLException: ERROR: replication slot "debezium" is active for PID 974

repo: ververica/flink-cdc-connectors


text:
Helm deployed Studio release-3.8 suffers from config file etc/studio-api.yaml, field File.SqliteDbFilePath is not set

Studio版本：release-3.8
复现步骤：

git clone https://github.com/vesoft-inc/nebula-studio.git
cd nebula-studio
helm upgrade --install my-studio --set service.type=NodePort --set service.port={30070} deployment/helm

现象：
pod将会报错，日志为：config file etc/studio-api.yaml, field File.SqliteDbFilePath is not set
对应的configmap为：

Pod 将会报错，日志为：config file etc/studio-api.yaml, field File.SqliteDbFilePath is not set

values.yaml 里面的镜像版本改过吗？3.8 的话应该没有这个错误了才对
image:
  pullPolicy: IfNotPresent
  nebulaStudio:
    name: vesoft/nebula-graph-studio
    version: v3.8.0

3.7 确实是会有这样的问题：
https://github.com/vesoft-inc/nebula-studio/blob/b0e4f2474870feae96d5b8ada427afa78c22426d/server/api/studio/internal/config/config.go#L23-L28
另外图里面还在用 Type: "mysql"，如果是测试用的部署的话，应该得切换到 sqlite3 才能让它正常运作

@qiuchen001 重新拉一下 git 仓库的更新，修改一下
https://github.com/vesoft-inc/nebula-studio/blob/70a52ac9efa993e2e528f20a8cba4eda8ea085f5/deployment/helm/templates/configmap.yaml#L31-L32
的 Type 到 sqlite3
然后重新原地执行
helm install nebula-studio --namespace nebula .

应该就能用了。
记得部署之后的 Service 也检查一下，如果需要 NodePort 类型的 Service 需要直接访问的话可以用
kubectl expose <deployment> --name=<name> --type=NodePort

暴露一下。
cc @huaxiabuluo @wey-gu 应该可以关掉 Issue 了

太强了，感谢 @nekomeowww !!!

authors: nekomeowww qiuchen001 wey-gu

repo: vesoft-inc/nebula-studio


text:
Lock main dependencies in CI

Ref #820.
We should update our CI-pipeline, which are run with [dev] so that we have locked version of main dependencies, to make sure our tests are run with the exact same versions as the dependencies. This will make sure tests fail on similar issues in the future.

closed by #907

repo: vespa-engine/pyvespa


text:
Failed to set up a config server cluster

hi all,
according to the document of vespa,i set VESPA_CONFIGSERVERS,VESPA_CONFIGSERVER_ZOOKEEPER_QUORUM_PORT,VESPA_CONFIGSERVER_ZOOKEEPER_ELECTION_PORT in $VESPA_HOME/conf/vespa/default-env.txt on all nodes,but there seems a failure to setting up a Multi-node config servers.
Have I miss any configuration? and what is the correct way？
Thanks

It's enough to set VESPAS_CONFIGSERVERS unless you have conflicts with ports used for something else. How does it fail?

Sorry for the time difference, I'm sorry
After I configure VESPAS_CONFIGSERVERS, I will be prompted to No value found for 'services.addr_configserver' or 'vespa_base.addr_configserver' when I start the config server cluster, although the last show config server starts. Then when I use "lsof" to see listenning ports of the config server process, I can only see 19070, 19071 and 2181, and can not find the election port and communication port of zk. Do not I need to set the myid file for zookeeper?
There is also a question, what is the role of configservers configuration options in service.xml.In my opinion,before the service.xml takes effect, configserver has been determined.

ZooKeeper ports:
I'm sorry, the documentation on setting ZooKeeper ports is wrong. The right names for those are cloudconfig_server__zookeeper_electionPort and cloudconfig_server__zookeeper_quoromPort.
I'll have the doc updated. However, how did you even get into this? :-) You don't need to set these.
Do not I need to set the myid file for zookeeper?
No.
What is the role of configservers configuration options in service.xml
It is a place to add non-bootstrap configuration on configservers. You are right that strictly the listing of the configserver hosts in there is redundant as it has to be the same as the bootstrap environment setting.
Setting up a multinode system:
I'm not sure if you have a working system or not? Just to be sure, here's how to make a multinode system work:

Your /opt/vespa/conf/vespa/default-env.txt should contain
override VESPA_CONFIGSERVERS full-hostname1,full-hostname2,full-hostname-3
You don't need to put anything else there (unless you want to change ports of config services for some reason).
Your services.xml and hosts.xml must configure those same hosts as configservers.
You need to run vespa-start-configserver on all the designated config servers and vespa-start-services on all the other nodes.
At this point you have a system running which does nothing and you can run vespa-deploy prepare [app-package] && vespa-deploy activate on any of the config servers to run an application.
vespa-logfmt -l warning,error (on an admin server) should show no problems, and vespa-logfmt should show that various services starts listening on various ports.

If you don't see this, please update the ticket with exactly what you see when doing which step.

To @FrankYu0502: You guys are probing deep ...  :-)
If the ZK services on 2 and 3 is unreachable you should see that in the log: vespa-logfmt -l warning,error - do you?
Are you sure you looked at the right session?
You need to check the session which is the active one - that session number is the sole content in a file somewhere below /config/v2/tenants/default/ - I don't remember the exact name.
Note that not all files in the application package are distributed in ZooKeeper - only a whitelisted set. (ZooKeeper is not suitable for large files).
Let me know if any of this information helps.

Thanks.
As far as I know, a zk cluster needs to have election ports and communication ports, which means that when the config server cluster starts successfully, I should see that the config server will listen on both ports. I configured it according to the steps mentioned above, but I don't seem to be able to see that the two ports are being monitored. In my opinion,It is irrelevant whether the config server cluster is successful and has no application deployed. Before deploying the application, config servers It should have been a cluster, I understand right?

The defaults for those ZK ports are 2182 and 2183.
I don't remember exactly when and how they are listened to. Do you have a problem with this, or are you curious? If it's just the latter I think you need to look at the ZK source.

@bratseth Here is the warning I got after deploy prepare & activate
[2018-03-26 20:58:27.585] WARNING : configserver     stderr	SLF4J: The following loggers will not work because they were created
[2018-03-26 20:58:27.585] WARNING : configserver     stderr	SLF4J: during the default configuration phase of the underlying logging system.
[2018-03-26 20:58:27.585] WARNING : configserver     stderr	SLF4J: See also http://www.slf4j.org/codes.html#substituteLogger
[2018-03-26 20:58:27.585] WARNING : configserver     stderr	SLF4J: org.apache.zookeeper.server.quorum.QuorumPeerMain
[2018-03-26 21:01:29.223] WARNING : configproxy      configproxy.com.yahoo.config.subscription.impl.JRTConfigRequester	Request callback failed: APPLICATION_NOT_LOADED. Connection spec: tcp/tj-s-staging-rec09.kscn:19070, error message: Failed request (No application exists) from Connection { Socket[addr=/10.38.10.6,port=25018,localport=19070] }
[2018-03-26 21:01:44.992] WARNING : configproxy      configproxy.com.yahoo.vespa.config.proxy.DelayedResponseHandler	Timed out (timeout 15000) getting config name=sentinel,namespace=cloud.config,configId=hosts/tj-s-staging-rec09.kscn, will retry
[2018-03-26 21:06:40.188] WARNING : config-sentinel  config-sentinel.config.frt.frtconnection	Connection to tcp/localhost:19090 failed or timed out
[2018-03-26 21:06:40.188] WARNING : config-sentinel  config-sentinel.config.frt.frtconnection	FRT Connection tcp/localhost:19090 suspended until 2018-03-26 13:07:20 GMT
[2018-03-26 21:07:01.834] WARNING : configproxy      configproxy.com.yahoo.config.subscription.impl.JRTConfigRequester	Request callback failed: APPLICATION_NOT_LOADED. Connection spec: tcp/tj-s-staging-rec11.kscn:19070, error message: Failed request (No application exists) from Connection { Socket[addr=/10.38.10.6,port=26189,localport=19070] }
[2018-03-26 21:07:02.992] WARNING : configproxy      configproxy.com.yahoo.vespa.config.proxy.DelayedResponseHandler	Timed out (timeout 25000) getting config name=sentinel,namespace=cloud.config,configId=hosts/tj-s-staging-rec09.kscn, will retry

@bratseth In host2 and host3, there is even no sessionId (ls /config/v2/tenants/default/sessions is empty).
However, in host1, there has everything (there are hosts.xml, searchdefinitions, services.xml, deployment.xml under /config/v2/tenants/default/sessions/2/userapp/)

OK,thanks.

@bratseth
Vespa running with a single configserver works perfectly. However, in order to ensure HA, I set up 3 configserver(host1, host2, host3) in default-env.txt, services.xml and hosts.xml configure same as configservers and start-configserver, start-services, deploy prepare & activate a sample application. It works well at this time. Then I just vespa-stop-configserver in host1. I get following log on all hosts:
1522120222.160	tj-s-staging-rec09.kscn	43121/32	configproxy	configproxy.com.yahoo.config.subscription.impl.JRTConfigRequester	info	Failure of config subscription, clients will keep existing config until resolved: name=jdisc-bindings,namespace=container.jdisc,configId=docproc/cluster.blog_post.indexing/component/com.yahoo.container.usability.BindingsOverviewHandler, Current generation: 2, Generation changed: false, Config changed: false
1522120264.318	tj-s-staging-rec10.kscn	180801/31	configproxy	configproxy.com.yahoo.config.subscription.impl.JRTConfigRequester	info	Failure of config subscription, clients will keep existing config until resolved: name=lowercasing,namespace=search.querytransform,configId=default/searchchains/chain/blog_post/component/com.yahoo.search.querytransform.VespaLowercasingSearcher, Current generation: 2, Generation changed: false, Config changed: false
This means the proxy could not subsribe any configserver to get config info right? It looks like I'm failed to set up a config server cluster. One config server 'down', configproxys on all nodes are ‘blind’.

@FrankYu0502 Looks to me like the configservers on host2 and host3 does not know about the application you deployed (but they are up and running and answer as they should).
One possible reason for this is that there is something wrong with the zookeeper setup/communication.
When you restart the configserver - what does it say about the Zookeeper quorum?

Hi,
I dumped the heap of the config server java process, but I found that the size of the InnerNodeVector in the ZooKeeperServerConfig variable of the ZooKeeperServer class instance is only 1, although I have set up three configServers. Because of dependency injection, I find it difficult to find the code segment that constructs the ZookeeperServerConfig class instance according to my setting, can you tell me the location of the source code?

@smorgrav
After restarting the configserver on host1, host1, host2, host3 configproxy could communicate with configserver on host1. Nothing has been changed on Zookeeper.
I paste all relevant files here:
hosts.xml:

node1

node2

node3

node4

services.xml:

2

1.0

1

default-env.txt
Copyright 2017 Yahoo Holdings. Licensed under the terms of the Apache 2.0 license. See LICENSE in the project root.
fallback VESPA_HOME /home/work/vespa
override VESPA_USER vespa
override VESPA_CONFIGSERVERS tj-s-staging-rec09.kscn,tj-s-staging-rec10.kscn,tj-s-staging-rec11.kscn

@bratseth
How to set "addr-configserver" on the config servers? (set it on VESPA_HOME/conf/vespa/default-env.txt in all hosts?)

Sorry, I didn't pay attention recently. I also found that I needed to do this setup by reading the code. I set up "services.addr_configserver" and the cluster was successful.
But there is a problem, config server seems to deploy only one application. When I create two tenants, each one in turn deploy an application, I will be prompted config server has been assigned to the first deployed application, does this mean a config server cluster can only deploy one application?

Thanks for reporting back. The addrs_configserver thing is actually unnecessarily confusing - well clean this up!
Regarding multiple applications: That is supported but it is only really needed if you create a multi-tenant hosted system. There's a lot to that which we don't document currently Is it really something you need to do?

Thanks.
We do need deploy multiple applications, because we want to use vespa as a platform to support the recommendation of many businesses(about ten+).If one config server for one application, the operation and maintenance will be very troublesome.

@FrankYu0502 to be clear, either add the line
override services.addr_configserver configserver1FQDN,configserver2FQDN,configserver3FQDN
to your VESPA_HOME/conf/vespa/default-env.txt
or set this as an environment variable on all the config server hosts.

@knowmara ok, it's possible to do that - I know some external customers are doing it (and of course we do it on a massive scale). All the steps you'll need are not documented though, and some will require digging deeper into how things work.
Are your recommendation services are managed by different dev teams with different release cycles etc.? Otherwise, you can have one app with 10 content clusters if they need to scale separately (or otherwise just 10 document types in the same cluster.)

Thank you very much.
Now it is configured like this. I have also created several tenants,  but I will be prompted config server has been assigned to the first deployed application  when deploying one more application.

Yes, our recommendation services are managed by different dev teams.That's the problem.

Ok. Any interest in deploying those applications to our hosted platform on AWS instead of rolling your own? We'll open that up to some select users soon.
Otherwise I'll try to give some pointers when you run into problems, but you'll probably need to figure out a number of things on your own. For the problem you mention: You need to set up the config servers independently of any of the hosted applications. The config servers is a "standalone container application", i.e a container configured from an application package directly with no config server attached. The application package you currently use for the config server cluster itself is under conf/configserver-app/. The applications must use  in services, which does not allow setting the config server nodes.

Thanks.
While our upstream backends are deployed on a private cloud, using a public cloud is inconvenient,so we tend to roll our own.

You need to run vespa-start-configserver on all the designated config servers and vespa-start-services on all the other nodes.

@bratseth I've been reading through the docs for a few hours now trying to work out why my multi-node cluster isn't starting and I didn't come across anything about vespa-start-configserver or vespa-start-services. Is there a reason these things aren't in the docs when they are a necessary step in getting a multi-node cluster working?
For the record, the error I'm seeing is as below, and may actually be unrelated to vespa-start-configserver or vespa-start-services:
Invalid application package: default.default: Error loading model: Multiple services/instances of the id '0' under the service/instance StorageCluster 'storage'. (This is
commonly caused by service/node index collisions in the config.).
Existing instance: storagenode on host 'vespa-1'
Attempted to add:  storagenode0 on no host

I'm not sure where this is coming from because I cannot see any obvious source of collision in services.xml. I've pretty much copied the content part from your examples. If this is unrelated I'll be happy to make another issue.
<?xml version="1.0" encoding="utf-8" ?>
<services version="1.0">

  <admin version="2.0">
    <adminserver hostalias="vespa-1"/>
    <configservers>
      <configserver hostalias="vespa-1"/>
    </configservers>
  </admin>

  <container id="container" version="1.0">
    <document-api/>
    <search/>
    <nodes jvmargs="-Xms512m -Xmx512m">
      <node hostalias="vespa-1"/>
      <node hostalias="vespa-2"/>
      <node hostalias="vespa-3"/>
    </nodes>
  </container>

  <content id="music" version="1.0">
    <search>
      <visibility-delay>1.0</visibility-delay>
    </search>
    <redundancy>2</redundancy>
    <documents>
      <document type="music" mode="index"/>
      <document-processing cluster="container"/>
    </documents>
    <nodes>
      <node hostalias="vespa-1" distribution-key="0"/>
      <node hostalias="vespa-2" distribution-key="1"/>
      <node hostalias="vespa-3" distribution-key="2"/>
    </nodes>
  </content>

</services>

Update: apparently the below line (which I copied from an example) was causing that last error. Then I didn't get the previous error about storage. I guess you cannot use the same node for config and for content or something.
<document-processing cluster="container"/>

I didn't come across anything about vespa-start-configserver or vespa-start-services

They are described in http://docs.vespa.ai/documentation/reference/files-processes-and-ports.html
but not in the quick-starts because the docker image autostarts both. This is a tradeoff between simplifying quickstarts and providing enough understanding to progress later. I think we are too far towards the ease of getting started end currently. I created https://github.com/vespa-engine/vespa/issues/5586 to follow up on that.
I'll add more responses.

Improved error message: https://github.com/vespa-engine/vespa/pull/5588

The first error message I'm unable to reproduce with the services.xml you quote. Please provide the hosts.xml file as well if you are interested in getting to the bottom of that one.

Please let me know if you found an example which does not do this.
I got it from here but it seems I missed that extra tag. My mistake: https://github.com/vespa-engine/sample-apps/blob/master/basic-search-on-docker-swarm/src/main/application/services.xml

The first error message I'm unable to reproduce with the services.xml you quote. Please provide the hosts.xml file as well if you are interested in getting to the bottom of that one.

<?xml version="1.0" encoding="utf-8" ?>
<hosts>
  <host name="vespa-1">
    <alias>vespa-1</alias>
  </host>
  <host name="vespa-2">
    <alias>vespa-2</alias>
  </host>
  <host name="vespa-3">
    <alias>vespa-3</alias>
  </host>
</hosts>

env config:
fallback VESPA_HOME /opt/vespa
override VESPA_USER vespa
override VESPA_UNPRIVILEGED no
override VESPA_CONFIGSERVERS vespa-1

That error went away when I added a new node vespa-config and used that as the admin/config node. This makes me assume that error meant you cannot use the same node as admin/config as well as container/content.

I tried it to keep things simple at first. Also, I have no idea how much RAM that service wants and I figured since the container/content nodes want over 1GB of RAM I may as well save the space by using one of them as the config/admin node. I still have no idea how much RAM the admin node requires but it's running at a lower value than the others now so it's all good.

authors: FrankYu0502 bratseth jazoom knowmara smorgrav

repo: vespa-engine/vespa


text:
Add config setting for throwing if active session cannot be loaded

THe feature flag that controlled this earlier has been removed, there might
still be exceptional cases where one might need to do this to get a config
server to start. Zookeeper server will not start if an exception is thrown,
so it is not possible to fix anything if the state somehow has become bad
See https://github.com/vespa-engine/vespa/pull/10241 for the PR that removed the feature flag.

Good idea.

authors: hmusum jonmv


text:
Require 'file' and make 'profile' optional for shared-credentials

The default profile is 'default'

TelegrafTest fails

authors: gjoranv olaaun


text:
Validate that endpoint points to an existing container cluster

@hmusum
FYI @andreer

Could this lead to a deployment failing for an already existing application?

@hmusum That would mean the application has declared an endpoint that always returns 404. I can try verifying prod applications tomorrow.

Verified that no currently deployed applications violate this validation.

authors: hmusum mpolden


text:
Upgrade questdb from 5.0.3 to 5.0.6

@bratseth PR

It failed a unit test locally, so need to wait for green build at least.

4:28:11 [ERROR] Failures:
14:28:11 [ERROR]   QuestMetricsDbTest.testGc:176 expected:<75> but was:<240>

I'll take a look at this

authors: baldersheim bratseth


text:
Disable creation of '._' files in tarball on mac os

See:
https://superuser.com/questions/61185/why-do-i-get-files-like-foo-in-my-tarball-on-os-x
I got the problem with dot-underscore files in the unpacked application packages again after wiping the mac. This time, the 'com.apple.quarantine' xattr was not set, but instead 'com.apple.provenance'. The latter seems impossible to remove. Hence, this solution.

Unfortunately, this seems to fail on Linux:

[ERROR]   CompressedApplicationInputStreamTest.require_that_gnu_tared_file_can_be_unpacked:95->assertTestApp:67 expected:<3> but was:<0>
[ERROR]   CompressedApplicationInputStreamTest.require_that_nested_app_can_be_unpacked:107 expected:<5> but was:<0>

I tried checking out the 'vespa' git repo from scratch, but the same thing happened. I wonder if it could be because I use https (with git-credentials-manager) instead of SSH.


text:
Jdisc garbage collection metrics

Adds jdisc.gc.count and jdisc.gc.ms counters over the last 1 minute measurement interval with a sliding window.

Thanks, now I can understand much more from just an overview of the code and test.

authors: gjoranv ollivir


text:
Backtracing Async functions (+Task return type)

Was using the Backtracer (Works very well!), But entountered a problem, when trying to trace an async function, the backtrace result is always the same, all functions originate from MoveNext function (Due to the Statemachine), example:
0x06301eb8+0x000 TBetterBinaryProtocol::WriteBinaryAsync 0x062ccf98+0x094 Thrift.Protocol.TProtocol.<WriteStringAsync>d__39::MoveNext
Any other idea to backtrace such functions?

it's good idea to share your code. I guess you need backtrace the WriteStringAsync function, or use tracer on target class(es)

Any other idea to backtrace such functions?

No clue!


text:
Yandex causing error

Hi, I had hard time compiling and running, eventually figured out to change Mounter's Program.cs by adding
} catch (ReflectionTypeLoadException ex) {
               Console.Error.WriteLine($"{ex.GetType().Name}: {ex.Message}");
               foreach(Exception ex2 in ex.LoaderExceptions)
               {
                   Console.Error.WriteLine($"{ex2.GetType().Name}: {ex2.Message}");
               }
               return -1;
           }

Above:
catch (Exception ex) {
                Console.Error.WriteLine($"{ex.GetType().Name}: {ex.Message}");
                return -1;

And figured out error from
ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
To:
ken=1f35af1d8b0c0a75' or one of its dependencies. The system cannot find the file specified.
FileNotFoundException: Could not load file or assembly 'YandexDisk.Client, Version=1.0.8.0, Culture=neutral, PublicKeyToken=1f35af1d8b0c0a75' or one of its dependencies. The system cannot find the file specified.

Hi @acosonic,
thanks for reporting this - I'll look into it.

authors: acosonic viciousviper

repo: viciousviper/DokanCloudFS

license: mit

license_source: bigquery


text:
npm package

Hi,
I have installed with npm, but install version 1.8.2, don't update to 1.10.0.
Please, publish to npm. 😃
Thanks
(sorry my english)

Bump ☝ the npm publish is behind

I noticed this as well, I had to point my dependency directly to github to get the latest version.  I wasn't aware that the developer really had to do much, the package.json file says the latest version is 1.10.0 so I don't quite understand what's going wrong there.

Leaving it here just for if you want to use the latest and greatest and until the maintainer can find the time to publish the release to NPM.
You can add the following line to your dependencies to get 1.10.0 now:
"bootstrap-iconpicker": "git+https://github.com/victor-valencia/bootstrap-iconpicker.git#v1.10.0",

authors: crobinson42 jrmessias radiok stayallive

repo: victor-valencia/bootstrap-iconpicker


text:
Legal Footer on Front Pgae

Is your feature request related to a problem? Please describe.
According to German law I need an imprint and a privacy statement that are easy to reach from the front page. I don't wan't this to take up a lot of space since it is just legal fineprint. The usual solution to this is a tiny footer that appears on all pages. The footer via site.Params.footerText works fine for all pages except for the front page.
Describe the solution you'd like
Add a parameter site.Params.frontPageFooterText to define a footer on the front page.
Describe alternatives you've considered

Include the footer on all pages including the front page. This would save redudant configuration (in my case at least), but break the template's current behaviour for everyone already using the footer.
Make my own template inheriting from Call me Sam. and override the index.html template. I'd prefer to improve the template instead (if the change fits your vision for this template).

Additional context
I'm happy to help with a pull request 🙂
This is how the front page would look like with same footer as other pages:

No objections here!

authors: bitzl victoriadrake

repo: victoriadrake/hugo-theme-sam


text:
The best way to fake uuid.v4

In SUT is v4 method  uuid  used:
uuid = require('uuid')
uuid.v4()
'b14b1abb-180e-4d34-a59c-940bc2e77ac7'

What is the best way fake their returning value in Arrange phase?
// How should we replace 'b14b1abb-180e-4d34-a59c-940bc2e77ac7'
// Can I simply use chance.guid?
uuid = {v4: sandbox.stub().named('uuid.v4').returns(...)}

Why would you stub a method that generates a UUIDv4 with a method that generates a UUIDv4 when you could just use the method itself?

OK, in which cases I SHOULD do it?
I should test if - char has been removed from random uuid:
// Code in SUT
uuid.v4().replace(/-/g, '')

As I mentioned I should stub uuid.v4()  with string constant only?
Usage of  chance.guid is in this case unnecessary.

I'm sorry, but I don't think I understand the question :( Maybe someone else can help.

is chance.guid() guaranteed to produce unique result? Even if called in sequence in for loop? We have a case when it seemingly produces duplicates. It's intermittent, so we cannot reliably reproduce.

is chance.guid() guaranteed to produce unique result?

No. This is a library for fake data.

authors: hellboy81 jayarjo oliversalzburg

repo: victorquinn/chancejs


text:
HTML-type labels get knocked out by notugly.xsl

I'm using notugly.xsl on a dot source file you can find at
https://github.com/dankamongmen/openscad-models/blob/master/schwarz.dot
everything was working alright until I started using some HTML labels. At that point, the content of the HTML labels is blanked in notugly.xsl output.
before:

after:

it also seems to have stripped the color from that doubleoctagon

Hi, thanks for this. Looking at it, I'm guessing the text is there but has ended up white on white background. Likely a relatively easy fix - I'll have a look as soon as I get a chance.

awesome, i wasn't sure if you were still maintaining this useful tool (i've been using it for over a decade!). please take your time. i'll be able to test your fix for you.

Finally had a chance to start looking at it. I've spotted a few more issues, so I think as a first step I'm going to try to untangle a few test cases from your example.

authors: dankamongmen vidarh

repo: vidarh/diagram-tools


text:
Noobie Video Dash Question

Also, I understand that you just created this 5 hours ago. I am guessing your not finished porting over the plugin?
https://github.com/heff/videojs-dashjs
https://github.com/Dash-Industry-Forum/dash.js/tree/development/contrib/videojs
https://github.com/videojs/video.js/wiki/Plugins
Is this going to replace your other thing?

Yeah, this is being worked on and will eventually update the one in the dash.js contrib folder. heff/videojs-dashjs is old and should be deprecated.

authors: chemoish heff

repo: videojs/videojs-contrib-dash


text:
TypeError: Cannot read properties of undefined (reading 'src')  at Array.map () digest: "3294976925" when add source tag in MediaProvider

Current Behavior:
When use source tag in MediaProvider:
TypeError: Cannot read properties of undefined (reading 'src')
at Array.map ()
digest: "3294976925"
Source code:
"use client";

import "@vidstack/react/player/styles/default/theme.css";
import "@vidstack/react/player/styles/default/layouts/video.css";

import { MediaPlayer, MediaProvider } from "@vidstack/react";
import {
  defaultLayoutIcons,
  DefaultVideoLayout,
} from "@vidstack/react/player/layouts/default";

const VideoPlayer = ({ src, title }: { src: string; title: string }) => {
  return (
    <MediaPlayer autoPlay title={title} className="max-h-[80vh]">
      <MediaProvider>
        <source src={src} type="video/mp4" />
      </MediaProvider>
      <DefaultVideoLayout
        icons={defaultLayoutIcons}
      />
    </MediaPlayer>
  );
};
export default VideoPlayer;

Reproduction Link: How to create a repro?
Environment:

Framework: React
Meta Framework: Next.js
Node: 20
OS: Windows 11
Browser: Chrome@125

For React, pass the source object like so:
<MediaPlayer
  src={{ src, type: 'video/mp4', }}
>

repo: vidstack/player


text:
Recurrent PersistenceExceptions thrown in factories due to Primary Key collisions

Hello, this is the issue I've been talking about in the CakePHP #support Slack recently. I'm going to do my best to type it up here and explain all my debugging methods I've attempted thus far, but I'm pretty much stumped.
Please let me know if any additional information is required.
The Problem
I get errors like these from 17 different tests:
CakephpFixtureFactories\Error\PersistenceException : Error in Factory App\Test\Factory\AccessTokenFactory.
 Message: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'yfwOHj3X2SGe4914XD721lrG90dGr0eBzWJRGPMH' for key 'PRIMARY'

The Setup
AccessTokenFactory looks like this:
    protected function setDefaultTemplate(): void
    {
        $this->setDefaultData(function (Generator $faker) {
            /* for clarity, let's call this the "default data array" */
            return [
                'oauth_token' => $faker->regexify('[a-zA-Z0-9]{40}'),        // <-- this is the primary key
                'client_id' => $faker->regexify('[a-zA-Z0-9]{32}'),
//                'user_id' => $faker->uuid,
                'expires' => $faker->unixTime,
            ];
        });
    }

Notes:

The FK column is commented out in the sample above. I've tried it both with and without, but have noticed that WITH sometimes the FKs get messed up for associated entities but WITHOUT sometimes I get user_id does not have a default value. I feel like that might be a separate issue, though.
At this exact moment, the only field that is colliding is the oauth_token field listed above. BUT, it has been other fields in the past, such as IDs and FKs. Once I switched to using combination fixtures+factories, the ID collisions went away (more on this in a minute)

An example test:
    public function testAuthenticateReusesExistingAccessTokenIfPresent()
    {
//        $client = ClientFactory::make()->with('Users.Roles')->persist();
        $client = $this->Clients->find()->contain(['Users'])->first();
        $creds = base64_encode(sprintf('%s:%s', $client->client_id, $client->client_secret));

        $time = FrozenTime::now()->addHour(3);
        $testToken = AccessTokenFactory::make([
            'oauth_token' => '4308be68821e7a952691de06395ea401ce368424',
            'client_id' => $client->client_id,
            'expires' => $time->format('U'),
        ])->withUsers($client->user)->persist();

       // ...

        $this->post('/users/authenticate');

       // ...
    }

Notes:

I have tried making entities for tests two ways: directly in the test with AccessTokenFactory::make() and also in combination with CakePHP fixtures (demonstrated below).
When only using direct factory calls, I was using the TruncateDirtyTables trait. At this exact moment I am using the TransactionStrategy instead.

Example fixture:
class AccessTokensFixture extends TestFixture
{
    public $connection = 'my_test_connection';            // Important: all my tables are located on a non-standard connection

    /**
     * Init method
     *
     * @return void
     */
    public function init(): void
    {
        AccessTokenFactory::make(50)->with('Users.Roles')->persist();
        AccessTokenFactory::make(['expires' => FrozenTime::now()->addDay()->format('U')], 50)->with('Users.Roles')->persist();

        parent::init();
    }
}

Notes:

I know this is not the way either Cake fixtures or the Fixture Factories are technically supposed to be used, but this is a last-ditch effort I was trying yesterday to see if it helped.
Once I switched all my tests over to the fixtures I switched to the TransactionsStrategy and commented out the TruncateDirtyTables trait because I can't have two fixture strategies in play at once.

Other Notes

When I run these tests individually, they pass. When I run the entire test suite, 12 fail with the error mentioned above, and the remaining 5 fail with errors that I believe are downstream of this error (related entity save failures)
The key collisions are not happening in my CI/CD pipeline, which is using GitLab Pipelines with an attached MySQL 5.7 service container. My local is using a MariaDB-10.6 container.

Expected Behavior
My entities are generated with unique primary keys every time, and all entities are dropped in between test runs (*caveat: I know some strategies clean up tables before or after, please take my meaning to be the correct one regardless of what I said)

TODO:

[ ] use the test suite light
[ ] use only factories created in a per tests: Test should be Arrange, Assert, Act.
[ ] Create a debug testsuite with all your tests
[ ] Narrow down the number of tests while still having the tests fail

What has changed
I have dwindled down the debug test suite to the ~three~ two tests that, when run together, cause EITHER an integrity constraint violation in the primary key column OR an entity save failure:
Both of these test classes have been modified to use the TruncateDirtyTables trait as well as generate/persist their entities with the fixture factories (no more transactions, no more static fixtures). I've also updated to the latest minor version of the fixture factories plugin.
Here is the default data for the factory that is having the problem:
protected function setDefaultTemplate(): void
{
    $this->setDefaultData(function (Generator $faker) {
        $faker->seed(md5(microtime()));    // note: now seeding faker with microtime
        $token = $faker->regexify('[a-zA-Z0-9]{40}');
        echo sprintf("    - Generated token: \"%s\"\n", $token);

        return [
            'oauth_token' => $token,
            'client_id' => $faker->regexify('[a-zA-Z0-9]{32}'),
              'user_id' => $faker->uuid,
            'expires' => $faker->unixTime,
        ];
    });
}

Current error(s)
Two different exceptions get thrown by the broken test suite, in different quantities per test run.
I used this command to run the broken test suite three times:
vendor/bin/phpunit --testdox --testsuite debug --repeat 10

Then applied some grep magic to the output to sort and count exceptions thrown, output was:
## InternalErrorException = my app, entity save failure; PersistenceException = this plugin, constraint violation
# 1st run
  34    │ Cake\Http\Exception\InternalErrorException
 106    │ CakephpFixtureFactories\Error\PersistenceException

# 2nd run
  30    │ Cake\Http\Exception\InternalErrorException
 110    │ CakephpFixtureFactories\Error\PersistenceException

# 3rd run
  26    │ Cake\Http\Exception\InternalErrorException
 114    │ CakephpFixtureFactories\Error\PersistenceException

# 4th run
  34    │ Cake\Http\Exception\InternalErrorException
 104    │ CakephpFixtureFactories\Error\PersistenceException
# (note: this run doesn't even add up to 140 total errors, like all the others)

Question/Comments
So, where I'm confused at the moment is why the exceptions would be happening in different quantities each for each run of the test suite when nothing at all is changing about the test suite in between the runs. It would make sense to me for the numbers to never change and be the same between runs.

Another lens into the problem (or at least, a related one) which shows that "when" the user saves can cause errors to occur in different tests over different runs:
Scenario: 4 different tests ~

1 - make token with user, role, and client - persist
2 - make token with user and role - persist
3 - make client with user and role - persist
4 - make client with user (no role) - persist

Over 10 repeats of the test suite saw errors thrown in tests 1 and 3 sometimes, 2 and 3 sometimes, 3 only sometimes, and sometimes not at all. With zero change to the tests code in between.
The exact error is an InternalErrorException generated when the application is unable to create a particular entity (NOT a factory entity, a real one) because it has a dependency on a User entity (factory-made) that is supposed to be persisted at that time but is not:
// these are validation errors for an application-generated entity, not from a factory
// in this case it depends on a factory-generated User entity, which is supposed to be persisted by now
{
    "user_id": {
        "_existsIn": "The specified user ID does not exist in the Users table"
    }
}

So it seems like the tests can sometimes get ahead of ->persist(), or at least that is my takeaway.

It would also appear that seeding the generator in this manner:
$faker->seed(md5(microtime()));
// or

is insufficient

On a recommendation from someone I created a new homebrew random string generator function and my factory now calls this method instead of $faker->regexify(...).
This appears to resolve the integrity constraint violations at first glance, but I need to finish repairing my test suite fully (from all the changes trying to diagnose this issue) to say for certain.
I will update this comment with a final conclusion when it becomes available, but it appears as if the problem may actually lie with the FakerPHP library not being able to generate enough randomness for regexify(), even when seeded.

Closing as it appears there is a strong possibility the defect is in the Faker generator (though what it could be I have been unable to tell, as the results of test runs are so random and irreproducible). The fix, in this case, was to homebrew a random string generator and use that instead of $faker->regexify(). Thanks, all.

repo: vierge-noire/cakephp-fixture-factories


text:
A manpage should be built

If/when this is packaged, it should have a manpage. You can do this trivially by stealing the logic in mrcal/mrbuild. This produces manpages and html docs from the docstring in a TOOL and TOOL --help.
The chunk in the Makefile:
https://github.com/dkogan/mrcal/blob/445995222aaab173559fbf9ebd0e0c3b34c3177f/Makefile.doc#L68
Each TOOL (you have just one here) should have a descriptive docstring on top, and argparse should use it:
https://github.com/dkogan/mrcal/blob/445995222aaab173559fbf9ebd0e0c3b34c3177f/mrcal-show-projection-uncertainty#L56
But let's get this packaged first.

Relatedly, a big docstring in your tool will make pydoc3 work.

repo: vietjtnguyen/fprime-data-tool


text:
Add subscribe method to action to abbreviate addons

This PR adds a new subscribe method for quickly adding a bunch of action callbacks. Long term, this moves actions closer to the Observable interface, but it also cleans up the action form and button pretty nicely.
I also added some tests to gain some missing coverage.

Codecov Report

:exclamation: No coverage uploaded for pull request base (scheduled-model@700734c). Click here to learn what that means.
The diff coverage is 91.66%.

@@                Coverage Diff                 @@
##             scheduled-model     #408   +/-   ##
==================================================
  Coverage                   ?   84.78%
==================================================
  Files                      ?       45
  Lines                      ?     1288
  Branches                   ?      239
==================================================
  Hits                       ?     1092
  Misses                     ?      163
  Partials                   ?       33

Impacted Files
Coverage Δ

packages/microcosm/src/addons/action-button.js
0% <0%> (ø)

packages/microcosm/src/env.js
100% <100%> (ø)

packages/microcosm-preact/src/presenter.js
100% <100%> (ø)

packages/microcosm/src/addons/model.js
100% <100%> (ø)

packages/microcosm/src/addons/action-form.js
100% <100%> (ø)

packages/microcosm/src/history.js
100% <100%> (ø)

packages/microcosm-preact/src/action-form.js
100% <100%> (ø)

packages/microcosm-preact/src/action-button.js
100% <100%> (ø)

packages/microcosm/src/addons/presenter.js
100% <100%> (ø)

packages/microcosm/src/action.js
100% <100%> (ø)

... and 1 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #408 into scheduled-model will decrease coverage by 1.23%.
The diff coverage is 100%.

@@                 Coverage Diff                 @@
##           scheduled-model     #408      +/-   ##
===================================================
- Coverage            87.32%   86.08%   -1.24%
===================================================
  Files                   45       45
  Lines                 1270     1301      +31
  Branches               232      244      +12
===================================================
+ Hits                  1109     1120      +11
- Misses                 135      147      +12
- Partials                26       34       +8

Impacted Files
Coverage Δ

packages/microcosm-preact/src/action-form.js
100% <100%> (ø)
:arrow_up:

packages/microcosm/src/addons/action-button.js
77.77% <100%> (-22.23%)
:arrow_down:

packages/microcosm/src/addons/action-form.js
78.04% <100%> (-21.96%)
:arrow_down:

packages/microcosm/src/action.js
100% <100%> (ø)
:arrow_up:

packages/microcosm-preact/src/action-button.js
100% <100%> (ø)
:arrow_up:

packages/microcosm/src/addons/indexing.js
92.68% <0%> (-7.32%)
:arrow_down:

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 700734c...6fdf63f. Read the comment docs.

authors: codecov-io nhunzaker

repo: vigetlabs/microcosm


text:
Created some C programs

This contain linked list and sorting algorithms along with one matrix operation.

Please accept it

Congratulations for your Open source contribution. Don't forget to add a star on this repo.. Happy hacking

Already starred it, thanks for your time

@vijaygupta18 sir please label it hacktoberfest-accepted

@vijaygupta18 sir please label it hacktoberfest-accepted

repo is already labelled as Hactoberfest accepted don't worry about it.


text:
Disable HTML streaming

hi! I wanted to disable HTML streaming while using vike-react-query, since I would like to keep partial availability of the website for users with JS disabled. but unfortunately, after passing stream: false to the +config.ts, I got the following error:
[vike][request(1)] Following error was thrown by the onRenderHtml() hook defined at /node_modules/vike-react/dist/renderer/onRenderHtml.js
Error: [react-streaming@0.3.26][Wrong Usage] HTML Streaming is disabled: set the option https://vike.dev/stream to true

if I remove stream: false from the config, and then set my user-agent to Google's bot, it automatically disables the HTML streaming, and in that case there's no error.
Tested on the vike-react-query example from the repo

This indeed seems contradictory, let me have a look.

authors: Dubzer brillout

repo: vikejs/vike-react


text:
Added The Doc Slug

I have added the Doc Slug and checked.

resolved the conflict


text:
Instances not bootstrapping after Cloudformation completion

Hi,
Just tried out the latest version of this by running turbine-cluster.template so I could install in an existing VPC.
The instances aren't getting bootstrapped. I tried to figure out where the problem lied by SSH'ing into an instance (webserver in this case) and running /opt/turbine/webserver.setup.sh, which then triggers an error when calling /opt/turbine/commons.setup.sh with the following (less than helpful) message:
[ec2-user@redacted turbine]$ ./commons.setup.sh
: invalid option

Got stuck debugging it here. Any ideas what the problem could be?
Thanks!

Nevermind, had to do with my silly Windows computer adding carriage returns to the bash files :/

repo: villasv/aws-airflow-stack


text:
🛑 Booking is down

In be6513b, Booking ($SITE_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Booking is back up in 2ba2c18.

repo: villekulla-nma/monitor-booking


text:
Don`t show airline

environment

vim: version 7.4.8056
vim-airline: current master
OS: macOS Sierra 10.12.4
What is your airline configuration:
Plug 'bling/vim-airline'
if you are using terminal:
terminal: macVim
color configuration (:set t_Co?): set t_Co=256

actual behavior

With NERDTree

expected behavior
Show vim-airline always

https://github.com/vim-airline/vim-airline/wiki/FAQ#vim-airline-doesnt-appear-until-i-create-a-new-split

authors: chrisbra gHashTag

repo: vim-airline/vim-airline


text:
Everything looks good, but I have seen a "?" on right side (image attached)

environment
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Apr 30 2017 06:21:54)
MacOS X (unix) version
Included patches: 1-589
powerline config:
let g:airline#extensions#tabline#enabled = 1
let g:airline#extensions#tabline#buffer_idx_mode = 1
let g:airline_powerline_fonts = 1
let g:airline_theme = 'badwolf'
let g:airline_detect_paste = 1
let g:airline#extensions#tabline#fnamemod = ':t'

looks like your terminal cannot display certain glyphs. What terminal is this?

iTerm2

Me too, But I happen when add power line fonts
MacOS: 10.12.4
iTerm2: 3.0.15

you probably want to customize the separators. It looks like your terminal cannot display them correctly. @rmichnik what is the output of :echo airline#statusline(1)?

It looks like you are using ryanoasis/vim-devicons, if that is the case please see the FAQ & Troubleshooting

Thank you @ryanoasis!
let g:WebDevIconsUnicodeDecorateFileNodesDefaultSymbol='x'
Fix the problem.

authors: chrisbra kamontat rmichnik ryanoasis


text:
Make BackgroundSocketCreator async using asyncio

When the background_listener option is used, listening for connections is done in a separate thread. This is done with a 5 second timeout on the socket, and checking if it should exit inbetween, meaning there is up to a 5 second delay between calling debugger.close() and the debugger actually closing.
However, since vdebug requires python 3, and the oldest supported version of python is 3.5, we should be able to use async/await.
This PR runs an asyncio event loop in the background thread, which can be exited almost instantly, without waiting for a socket timeout.
This has been tested with vim 8.1 and neovim 0.4.3, as well as python 3.5.9 and python 3.8.2.
As an aside: this also partially addresses #426 and #453, since no superfluous "Exception caught" message is printed on every exit.
Other print calls in the background thread will still fail on neovim.

Seems to work without any problem on neovim 0.5 and python 3.8.2.

Any updates for this?

Thanks, this is a nice improvement

authors: BlackIkeEagle Mte90 meldafert przepompownia

repo: vim-vdebug/vdebug


text:
Vers 9.0.1968 - write any file now  => E1509: Error occured when reading or writing extended attribute

Steps to reproduce
On  system with SMACK64 in kernel (Arch linux).
Writing any file leads to this error
E1509: Error occured when reading or writing extended attribute
It may be coming from copy ingthe xattr from edited file to backup file and attempting to setxattr.
Possibly around line 1513 of this commit:
https://github.com/vim/vim/pull/13203/commits/23fff2bc6a8a379faf742998e9042269d6b6bb89

and likely because non-priv user cannot write system xattr.
On my system
getfattr -m '' foo shows:
security.SMACK64

and lowly user cannot set security.SMACK64 - which could be the problem.
As of now every file that is written generates this error.
Downstream bug: https://bugs.archlinux.org/task/79830
Expected behaviour
Be able to write files without errors
Version of Vim
9.0.1968
Environment
Arch linux
Logs and stack traces
No response

I find it surprising, that you are able to edit a file, but not able to update the SMACK64 security attributes. But just to clarify, the file is written successfully (without those attributes) even though it causes those error messages?
I am also wondering, does the attributes get written correctly, are you also using a Vim build which has SMACK feature enabled? Does those copy the SMACK attributes correctly or not? For the time being, you may want to configure with with --disable-xattr. I need some time to reproduce this issue.

I'm actually not terribly familiar with SMACK but my loose understanding is that there are multiple namespaces for attributes - and while unprivileged user can add/remove the ones in user namespace - they cannot for any attribute in a system namespace.  The system namespaces may include trusted, security and system.
The case for every file here is an attribute in the security namespace - non-priv user cannot change these.
vim should only attempt to setxattr() on attributes for which the current user has permission - for non root it can set those such as "user.comment" but it is forbidden from setting "security.SMACK64". I suspect vim code needs to check if it has permission before attempting to set xattrs or at the very least catch the exceptions and not create errors.
So in this case the attributes enforced by the kernel is in the security namespace and
Only root can edit/change security.SMACK64.
security.SMACK64 is enforced by the kernel on every file (unless it is explicitly removed by root).
So with or without vim attempting to setsecurity.SMACK64 it will be set by the kernel. So if I edit any file with any editor including the previous version of vim all files retain their security.SMACK64 attribute.
e.g. perhaps this helps illustrate
   $ touch foo
   getfattr -m '' foo
   # file: foo
   security.SMACK64

Do what vim does and make a copy - the security namesapce attributes are enforced by kernel:
   $ cp foo goo
   getfattr -m '' goo
   # file: goo
    security.SMACK64

Try to set remove the attribute:
    setfattr -x security.SMACK64 foo
    setfattr: foo: Operation not permitted

Now if we deal with user namespace and try Set attt it will work fine :
   setfattr -n user.comment goo

   getfattr -m ''  goo
  # file: goo
  security.SMACK64
  user.comment

In line 3147 in os_unix.c the return of setxattr() is ignored and errno is checked. setxattr() returns -1 on error
and sets errno to the list you have coded plus those set by stat().
The man page for setxaatr() is slightly unclear to me what error happens when user has no permission to set an attribute.
Likely its EACCESS.  In the case here of simply attempting to copy attributes it is safe to not treat such thing as an error - system and security attributes are enforced by the kernel.
So here's my non-expert suggestions:

ONLY report these errno errors when vim is verbose mode.
This routine is merely attempting to "copy" attributes.

NEVER report errors on EACCESS, ENOTSUP, EPERM and
Again,  as you're simply copying attributes,  - the system saying "no" is not really an error - certainly not for the security or system namespace ones.

regards
gene

This patch fixes my problem. I can't say if this is a complete solution, in particular I did not touch line 3061 which may need something similar.
Maybe this helps:
xattr.patch.txt

how about this patch instead:
Note: I am not sure EACCESS can actually happen. It's not defined in my manpage.
diff --git a/src/errors.h b/src/errors.h
index bb807e7d5..7bce6a26b 100644
--- a/src/errors.h
+++ b/src/errors.h
@@ -3554,8 +3554,6 @@ EXTERN char e_invalid_format_specifier_str[]
        INIT(= N_("E1505: Invalid format specifier: %s"));
 EXTERN char e_xattr_erange[]
        INIT(= N_("E1506: Buffer too small to copy xattr value or key"));
-EXTERN char e_xattr_enotsup[]
-       INIT(= N_("E1507: Extended attributes are not supported by the filesystem"));
 EXTERN char e_xattr_e2big[]
        INIT(= N_("E1508: Size of the extended attribute value is larger than the maximum size allowed"));
 EXTERN char e_xattr_other[]
diff --git a/src/os_unix.c b/src/os_unix.c
index 9356db0b7..b1aff66b0 100644
--- a/src/os_unix.c
+++ b/src/os_unix.c
@@ -3140,6 +3140,10 @@ mch_copy_xattr(char_u *from_file, char_u *to_file)

        while (size > 0)
        {
+           // add one for terminating null
+           keylen = STRLEN(key) + 1;
+           size -= keylen;
+
            vallen = getxattr((char *)from_file, key,
                    val, round ? max_vallen : 0);
            // only set the attribute in the second round
@@ -3154,8 +3158,12 @@ mch_copy_xattr(char_u *from_file, char_u *to_file)
                        errmsg = e_xattr_e2big;
                        goto error_exit;
                    case ENOTSUP:
-                       errmsg = e_xattr_enotsup;
-                       goto error_exit;
+                   case EACCES:
+                   case EPERM:
+                       // silently ignore attributes that cannot be set
+                       // e.g. permission errors for SMACK attributes
+                       key += keylen;
+                       continue;
                    case ERANGE:
                        errmsg = e_xattr_erange;
                        goto error_exit;
@@ -3168,9 +3176,6 @@ mch_copy_xattr(char_u *from_file, char_u *to_file)
            if (round == 0 && vallen > max_vallen)
                max_vallen = vallen;

-           // add one for terminating null
-           keylen = STRLEN(key) + 1;
-           size -= keylen;
            key += keylen;
        }
        if (round)

Hi - EACCES is actually documented though indirectly via stat - in man page says:
       In addition, the errors documented in stat(2) can also occur.

And man 2 stat of course has EACCES :)
I suspect EACCES may be the most likely errno for the situation at hand.
Also quick eyeball on your patch - you need "break;" not "continue;" to break out of switch statement don't you?

ah thanks, then your patch should be (mostly) fine. Let me include it

Thank you :)

I'm still getting this error on nvim v0.10.0-dev-7ca2d64, which should have this fix included if I'm not mistaken (?)
Version v0.9.4 does not have this error.

Neovim is that way: neovim

I'm guessing these is another latent bug in the code, and this is just a side effect bug.  The merged fix is really a workaround for the real problem.  Read on for details.
Since I can't comment on the neovim issue, I'm commenting here, but vim code can benefit as well.   This is still happening with neovim nightly as of this time.  I oddly found that if this fixes it for any given file:
chmod o-rwx file.txt

This is really odd, and I can't explain why this fixed it.  I just compared a bad file with a good file.  The selinux xattrs were the same, and this was the only other difference.

Workaround fix Neovim for Linux.
I just started having this problem because I just installed a Fedora Linux, but on my prior setup, I configured it so files were written without those bits set.
So, a permanent fix was to add this to  /etc/profile (and /etc/zprofile):
umask 027

And run this:
chmod o-rwx -R ~

authors: Hubro chrisbra gene-git mikeslattery

repo: vim/vim

license: Vim


text:
Question - Does syn match respect \zs \ze ?

Hello Reader,
I'm trying to create a custom syntax file.
The lines I'm matching are structured like this ...
<filepath>:<linenumber>:<columnnumber>: <classification>: <message> [<affected entitiy>] (<violated rule>)
example ...
work/path/to/file.c:135:44: advisory: Pointer arithmetic not allowed [-] (Rule 18.4)
all good with that, no issues with the regex, they all work on their own and the correct parts get highlighted as expected.
my strategy is to describe the whole line and use \zs and \ze to mark the start and end of the parts to be highlighted.
here the important lines ...
hi AXV_FILE    guifg=#458588
hi AXV_LINE    guifg=#B8BB26
hi AXV_COL     guifg=#FABD2F
hi AXV_CLASS   guifg=#D79921
hi AXV_MESSAGE guifg=#EBDBB2
hi AXV_ENTITY  guifg=#FB4934
hi AXV_RULE    guifg=#B16286

sy match AXV_FILE    /^\zs[^:]\+\ze:\d\+:\d\+: \w\+: .\+ \[.\+\] (.\+)$/
sy match AXV_LINE    /^[^:]\+:\zs\d\+\ze:\d\+: \w\+: .\+ \[.\+\] (.\+)$/
sy match AXV_COL     /^[^:]\+:\d\+:\zs\d\+\ze: \w\+: .\+ \[.\+\] (.\+)$/
sy match AXV_CLASS   /^[^:]\+:\d\+:\d\+: \zs\w\+\ze: .\+ \[.\+\] (.\+)$/
sy match AXV_MESSAGE /^[^:]\+:\d\+:\d\+: \w\+: \zs.\+\ze \[.\+\] (.\+)$/
sy match AXV_ENTITY  /^[^:]\+:\d\+:\d\+: \w\+: .\+ \[\zs.\+\ze\] (.\+)$/
sy match AXV_RULE    /^[^:]\+:\d\+:\d\+: \w\+: .\+ \[.\+\] (\zs.\+\ze)$/

But when I execute all sy lines, then only the first one works in the sense that only the filename/path gets highlighted.
So I did some investigations and I read :h :syn-priority and I have the feeling that's the part of the documenation that explains why the sy regexs work on their own but not when all have been executed.
The manual does not state if \zs and \ze are considered or not. Or in other words - are these regex pattern starting at the same column or not? From the highlighting I can tell they are definitely considered, but I dont know if these columns are also used for the priority check.
In my opinion Vim should recognize that they are covering different parts of a matching line and should respect \zs and \ze, and therefore there is no overlapping of "regions".

Do you know how this has been implemented at the moment?
Am I missing something like an option that solves my problem?

I also tried playing with contains/contained but has the regions are not actually overlapping, no nesting, if \zs and \ze would be considered

Can Vim in the future consider \zs and \ze to mark the start and end of a matching pattern correctly?

Thanks for your support
marco

Instead of examining whole lines with every :syn-match, try
claiming the line once, and then looking for submatches in
it for decoration, e.g.:
" <filepath>:<line_number>:<column_number>: <classification>: <message> [<affected entity>] (<violated rule>)
sy match AXV_SPAN transparent contains=CONTAINED
	\ /^.\{-1,}:\d\+:\d\+: \w\+: .\+ \[.\{-1,}\] (.\{-1,})$/
sy match AXV_FILE	contained /^\zs.\{-1,}\ze:/
sy match AXV_LINE	contained /:\zs\d\+\ze:\d\+:/
sy match AXV_COL	contained /:\zs\d\+\ze: \w\+:/
" Define a more general match pattern for <message> before...
sy match AXV_MESSAGE	contained /: \zs.\+\ze \[.\{-1,}\] (.\{-1,})$/
" ...a less general match pattern for <classification>.
sy match AXV_CLASS	contained /: \zs\w\+\ze: .\+ \[.\{-1,}\] (.\{-1,})$/
sy match AXV_ENTITY	contained /\[\zs.\{-1,}\ze\] (.\{-1,})$/
sy match AXV_RULE	contained /(\zs.\{-1,}\ze)$/

hi def link AXV_FILE	PreProc
hi def link AXV_LINE	Comment
hi def link AXV_COL	Identifier
hi def link AXV_CLASS	Type
hi def link AXV_MESSAGE	Constant
hi def link AXV_ENTITY	Todo
hi def link AXV_RULE	Error

thank you @zzzyxwvut
I was able to make it work

note, there is also :h syn-nextgroup

authors: chrisbra marcotrosi zzzyxwvut


text:
Active terminal causes :wall to fail with E676: No matching autocommands for acwrite buffer

Steps to reproduce:

vim -u NONE
:term
<C-W>:wall<CR>

What happens:

E676: No matching autocommands for acwrite buffer flashes briefly

What I expect

no confusing error message

Note that if the terminal is no longer active (e.g you exit the shell), :wall doesn't complain.

On 13:18 Thu 05 Oct     , Marius Gedminas wrote:

Steps to reproduce:

vim -u NONE
:term
<C-W>:wall<CR>

What happens:

E676: No matching autocommands for acwrite buffer flashes briefly

What I expect

no confusing error message

Note that if the terminal is no longer active (e.g you exit the shell), :wall doesn't complain.

I see this regularly, when using vim-fugitive :Gcommit command.
Regards,
Marcin

This also happens to me all the time when I have a terminal open and try to use fzf for opening a buffer.
I think this should be fixed in vim itself although I am uncertain of the implementation details, but in the meantime I use the following workaround in my vimrc:
fun! s:workaroundIssue2190()
    " see https://github.com/vim/vim/issues/2190
    if &buftype=='terminal' && !exists('b:workaround_issue_2190')
        autocmd BufWriteCmd <buffer> echo 'workaround 2190'
        let b:workaround_issue_2190=1
    endif
endfun
aug workaroundIssue2190
    autocmd! BufWinEnter * call s:workaroundIssue2190()
aug END

Or add ignoring for write if buftype is nowrite or terminal.
diff --git a/src/ex_cmds.c b/src/ex_cmds.c
index b4351b23d..79dc01314 100644
--- a/src/ex_cmds.c
+++ b/src/ex_cmds.c
@@ -3414,6 +3414,12 @@ do_wqall(exarg_T *eap)
 		++error;
 		break;
 	    }
+
+	    if (bt_dontwrite(buf))
+	    {
+		continue;
+	    }
+
 #ifdef FEAT_BROWSE
 	    /* ":browse wall": ask for file name if there isn't one */
 	    if (buf->b_ffname == NULL && cmdmod.browse)

+1 for the patch  ignoring not-writable buffers.

authors: chrisbra gbarta mattn mgedmin vim-ml


text:
vim9: echo garbles output

Steps to reproduce
I guess the echo implementation makes this a nested echo
run the following
vim9script
def X(): string
    echo 'foo'
    return 'baz'
enddef

echo 'bar' X()

observe output
bar
foo baz

Expected behaviour
expect output
foo
bar baz

which can be obtained with a tmp
var t = X()
echo 'bar' t

Version of Vim
8.2.4589
Environment
ubuntu; gvim; vim-gtk3
Logs and stack traces
No response

This works as intended.  ":echo" evaluates and prints each argument in sequence.
If you want to first evaluate the arguments before printing anything, use string concatenation: "echo 'bar ' .. X()".

authors: brammool errael


text:
Fix for #1255: add STATIC_WINPTHREAD to allow static winpthread.

This is a potential fix for #1255. It adds a STATIC_WINPTHREAD build variable which when set to 'yes' will allow linking the winpthread library statically.
To maintain existing build by default, I'm initializing the value to 'no' if not set. I'm not certain though whether this is a widespread problem. If it is, perhaps the default should be 'yes'.
I'd welcome any ideas or suggestions on how to test more widely outside of my system.

To maintain existing build by default, I'm initializing the value to 'no' if not set. I'm not certain though whether this is a widespread problem. If it is, perhaps the default should be 'yes'.

How about following the setting of STATIC_STDCPLUS?
ifndef STATIC_WINPTHREAD
STATIC_WINPTHREAD=$(STATIC_STDCPLUS)
endif

That makes sense to me. Will make the change. Fewer options to pass in most cases probably.
Thanks for looking it over!

authors: jmmerz k-takata


text:
Read and write eml files with DOS line endings

These are "raw" dumps of emails, and pretty much everyone uses and
expects DOS line endings, as specified in RFC5322.

On Thu, Jul 22, 2021 at 7:11 AM Martin Tournoij
@.***> wrote:

These are "raw" dumps of emails, and pretty much everyone uses and
expects DOS line endings, as specified in RFC5322.

Warning: 'fileformats' (plural) is a global (only) setting. This means
that changing it, even with :setlocal, will change the global value
and therefore affect all files from then on. In particular, all files
(of any filetype) read thereafter will be written (if and when they
are) with DOS ends-of-lines, even if when read they had only Unix
ends-of-lines, since reading a unix-type file with 'fileformats' set
to "dos" (only) will recognize it as a DOS file. (In a DOS file,
either CR+LF or LF alone are accepted as an end-of-line when reading,
and all ends-of-lines, usually including the end of the last line, are
written as CR+LF when writing.)
Best regards,
Tony.

Ah, that is surprising! This setting should probably be global-local, but that's a different issue. I removed that for now, setting just fileformat=dos.

Setting 'fileformat' after loading a file doesn't have an effect.  You would need to reload the file.  And only do that if the 'fileformat' actually changed.
'fileformats' must be global, because it is used when reading a file, for which most likely no buffer exists yet.

Maybe a BufReadPre,BufNewFile autocommand could be created for *.eml, setting 'fileformat' (locally) to dos. This would read unix files without error, and write .eml files with CR+LF ends-of-lines, which is the correct format for email. But where to set up that autocommand? I suppose filetype.vim might be the right place, it sets up a lot of autocommands.
Just throwing an idea on the wall to see if it sticks. What do you people think of it?
Best regards,
Tony.

Setting 'fileformat' after loading a file doesn't have an effect. You would need to reload the file. And only do that if the 'fileformat' actually changed.

In this case, that's actually just fine: loading a file with either \n and \r\n line-endings works, and saving them is always as \r\n with this change.
The reverse would be a bit more problematic, since loading a file with \r\n line-endings you need to tell Vim to interpret those \r's as line endings.
I've seen a lot of .eml files over the years from different systems on account of working a lot with email code, and I don't think I've ever seen one that wasn't with \r\n line endings.
The only issue is when people have "set fileformats=unix" in their vimrc, but that it arguably already not a great setting to add.

authors: arp242 brammool tonymec vim-ml


text:
Test suite QuickCheck failure

    generate-param-odd:      FAIL
      *** Failed! Falsifiable (after 56 tests):
      TestDRG (14634184162,172342014,14634914744,16093274693,6665281464)
      Int0_2901 0
      Use --quickcheck-replay '55 TFGenR 000000005F255FBD000000000007A120000000000000DFA500000001B378B680 0 1152921504606846960 60 0' to reproduce.

Occurred with version 0.6.

has been fixed in the repository for a while. need to release a new version though.

Ah, sorry for not searching first. Is there a single particular commit that I could apply to the Debian package?

@nomeata it's 169570c9632a29c95432468016f294853bcd1ba2

Thanks! Applied it to the Debian package, together with the other patches I suggested today. Let’s see how well that goes.

Looks like I still get this:
    generate-param:          FAIL
      *** Failed! Falsifiable (after 82 tests):
      TestDRG (437993943873007,1050657333325426,1824512674053348,1546774482379053,23414001285279)
      Int0_2901 0
      Use --quickcheck-replay '81 TFGenR 7D1E6987D152076F136A688E2627DEF80114C16CF0ADB8AE20DF36049CF5B9E5 0 1048575 20 0' to reproduce.

Maybe the generate-param tests (and the others) need a similar guard as in 169570c, or alternatively, a different newtype could be used (Int1_2901?)

has been fixed in cryptonite 0.7

authors: nomeata snoyberg vincenthz

repo: vincenthz/cryptonite


text:
MyApp is not defined     at Module../pages/_app.js

i am trying to translate my website into nn_ locality, but after introducing package to my project. this error is coming...
ReferenceError: MyApp is not defined
at Module../pages/_app.js (D:\Files and Softwares\ass\React apps\Hello-Next\nextjs\.next\server\pages\_app.js:3640:1)
at __webpack_require__ (D:\Files and Softwares\ass\React apps\Hello-Next\nextjs\.next\server\pages\_app.js:29:31)
at Object.0 (D:\Files and Softwares\ass\React apps\Hello-Next\nextjs\.next\server\pages\_app.js:5009:18)
at __webpack_require__ (D:\Files and Softwares\ass\React apps\Hello-Next\nextjs\.next\server\pages\_app.js:29:31)
at D:\Files and Softwares\ass\React apps\Hello-Next\nextjs\.next\server\pages\_app.js:124:18
at Object.<anonymous> (D:\Files and Softwares\ass\React apps\Hello-Next\nextjs\.next\server\pages\_app.js:127:10)
at Module._compile (internal/modules/cjs/loader.js:1063:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
at Module.load (internal/modules/cjs/loader.js:928:32)
at Function.Module._load (internal/modules/cjs/loader.js:769:14)

my website is working fine before using next-translate. By just removing next.config.js, everything works properly.
i18n.json..
`{
    "locales": ["nn_"],
    "defaultLocale": "nn_",
    "pages": {
      "*": ["common"],
      "/": ["index"],
      "/quote": ["quote"],
      "/aboutus": ["aboutus"]
    }
  }`

next.config.json
`const nextTranslate = require('next-translate');

module.exports = nextTranslate();
`

just solved this issue by moving export from export  function MyApp to  export default MyApp;

just solved this issue by moving export from export  function MyApp to  export default MyApp;

repo: vinissimus/next-translate


text:
又登录不了了啊啊啊啊

最新得 2084版本啊；
登录就是验证码错误啊。。。。。。
大牛牛们
出手吧。。。。。。。。。。

最新得 2084版本啊；
登录就是验证码错误啊。。。。。。
大牛牛们
出手吧。。。。。。。。。。

那估计是水木系统问题 iphone其他 app也一样 我今天有点忙 空闲时看看
Regards，
Vinney

发件人: skyformat99 @.>
发送时间: Thursday, September 26, 2024 2:10:52 PM
收件人: vinneyg/ZSMTH-VINNEY @.>
抄送: Subscribed @.***>
主题: [vinneyg/ZSMTH-VINNEY] 又登录不了了啊啊啊啊 (Issue #8)
最新得 2084版本啊；
登录就是验证码错误啊。。。。。。
大牛牛们
出手吧。。。。。。。。。。
―
Reply to this email directly, view it on GitHubhttps://github.com/vinneyg/ZSMTH-VINNEY/issues/8, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMMSS3MDOF6EGAXVY423BFLZYOQOZAVCNFSM6AAAAABO4HPEIOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU2DSNRQHA2DCOI.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

系统恢复了 你再试试
Regards，
Vinney

发件人: skyformat99 @.>
发送时间: Thursday, September 26, 2024 2:21:42 PM
收件人: vinneyg/ZSMTH-VINNEY @.>
抄送: vinneyg @.>; Comment @.>
主题: Re: [vinneyg/ZSMTH-VINNEY] 又登录不了了啊啊啊啊 (Issue #8)
最新得 2084版本啊；
登录就是验证码错误啊。。。。。。
大牛牛们
出手吧。。。。。。。。。。
―
Reply to this email directly, view it on GitHubhttps://github.com/vinneyg/ZSMTH-VINNEY/issues/8#issuecomment-2376034276, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMMSS3LWM3FRWRHWSITJQBTZYORXNAVCNFSM6AAAAABO4HPEIOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZWGAZTIMRXGY.
You are receiving this because you commented.Message ID: @.***>

可以了好像；
大牛牛，再改个最新得吧；

好 有空整..
Regards，
Vinney

发件人: skyformat99 @.>
发送时间: Thursday, September 26, 2024 3:56:31 PM
收件人: vinneyg/ZSMTH-VINNEY @.>
抄送: vinneyg @.>; Comment @.>
主题: Re: [vinneyg/ZSMTH-VINNEY] 又登录不了了啊啊啊啊 (Issue #8)
可以了好像；
大牛牛，再改个最新得吧；
―
Reply to this email directly, view it on GitHubhttps://github.com/vinneyg/ZSMTH-VINNEY/issues/8#issuecomment-2376201703, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMMSS3M23CSCFWQIUBEEKC3ZYO427AVCNFSM6AAAAABO4HPEIOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZWGIYDCNZQGM.
You are receiving this because you commented.Message ID: @.***>

好 有空整.. Regards， Vinney
…
________________________________ 发件人: skyformat99 @.> 发送时间: Thursday, September 26, 2024 3:56:31 PM 收件人: vinneyg/ZSMTH-VINNEY @.> 抄送: vinneyg @.>; Comment @.> 主题: Re: [vinneyg/ZSMTH-VINNEY] 又登录不了了啊啊啊啊 (Issue #8) 可以了好像； 大牛牛，再改个最新得吧； ― Reply to this email directly, view it on GitHub<#8 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMMSS3M23CSCFWQIUBEEKC3ZYO427AVCNFSM6AAAAABO4HPEIOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZWGIYDCNZQGM. You are receiving this because you commented.Message ID: @.***>

择日不如撞日，就今天整一个
哈哈哈

择日不如撞日，就今天整一个
哈哈哈

择日不如撞日，就今天整一个
哈哈哈

就今天整一个
哈哈哈

多谢啊。
最近忙着换工作~~
等我空了再弄吧。
Vinney

发件人: skyformat99 @.>
发送时间: 2024年10月14日 3:42
收件人: vinneyg/ZSMTH-VINNEY @.>
抄送: vinneyg @.>; Comment @.>
主题: Re: [vinneyg/ZSMTH-VINNEY] 又登录不了了啊啊啊啊 (Issue #8)
就今天整一个
哈哈哈
―
Reply to this email directly, view it on GitHubhttps://github.com/vinneyg/ZSMTH-VINNEY/issues/8#issuecomment-2409884439, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMMSS3KRL3TOCE7KYVMUNRLZ3M4UDAVCNFSM6AAAAABO4HPEIOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBZHA4DINBTHE.
You are receiving this because you commented.Message ID: @.***>

多谢啊。 最近忙着换工作~~ 等我空了再弄吧。 Vinney
…
________________________________ 发件人: skyformat99 @.> 发送时间: 2024年10月14日 3:42 收件人: vinneyg/ZSMTH-VINNEY @.> 抄送: vinneyg @.>; Comment @.> 主题: Re: [vinneyg/ZSMTH-VINNEY] 又登录不了了啊啊啊啊 (Issue #8) 就今天整一个 哈哈哈 ― Reply to this email directly, view it on GitHub<#8 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMMSS3KRL3TOCE7KYVMUNRLZ3M4UDAVCNFSM6AAAAABO4HPEIOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBZHA4DINBTHE. You are receiving this because you commented.Message ID: @.***>

666

repo: vinneyg/ZSMTH-VINNEY


text:
Add support for Django 3.2

Description: Add support for Django 3.2
Dependencies: None
Merge deadline: None
Installation instructions: None
Testing instructions: None

Open page A
Do thing B
Expect C to happen
If D happend instead - check failed.

Reviewers:

[ ] tag reviewer
[ ] tag reviewer

Merge checklist:

[ ] All reviewers approved
[ ] CI build is green
[ ] Version bumped
[ ] Changelog record added
[ ] Documentation updated (not only docstrings)
[ ] Commits are squashed
[ ] PR author is listed in AUTHORS

Post merge:

[ ] Create a tag
[ ] Check new version is pushed to PyPi after tag-triggered build is
finished.
[ ] Delete working branch (if not needed anymore)

Author concerns: None

Thanks, already solved by other PR.

authors: fjsj hebertjulio

repo: vintasoftware/drf-rw-serializers


text:
feat(agent/grpc): add gRPC server

What am I looking at ???
Add a gRPC server that will run and stream the lifecycle of the agent to a caller. For now, it only streams the data once it's done.
What still needs to be done

[ ] Stream the data continuously during the build and the run
[ ] Better error handling and logs
[ ] Graceful shutdown of the running workload

(In another PR.)
How can I run it ?
git git@github.com:mmoreiradj/cloudlet.git
cd cloudlet
git checkout feat/agent_grpc_server

Then the key build.code-path at src/agent/examples/config.toml to put the right path to the code.
cargo run --bin agent -- --config=./src/agent/examples/config.toml

[!TIP]
To use the debug agent you can use the feature flag debug-agent like this:
cargo run --bin agent -F debug-agent -- --config=./src/agent/examples/config.toml

Merged so the VMM team can work on communication with the agent.

repo: virt-do/cloudlet


text:
Use Bit-based Reader/Writer to avoid using whole bytes for nothing

Bit-based Reader/Writer
Weaver: Sort fields by type in order to serialize all bools together (Thanks @paulpach )
New Write/Read methods
Added new tests

Depends on PR #1

Depends on #4

Codecov Report

Merging #3 into features will increase coverage by 1.9%.
The diff coverage is 80%.

@@            Coverage Diff            @@
##           features     #3     +/-   ##
=========================================
+ Coverage      3.59%   5.5%   +1.9%
=========================================
  Files            30     32      +2
  Lines          7118   7301    +183
  Branches       1192   1196      +4
=========================================
+ Hits            256    402    +146
- Misses         6857   6894     +37
  Partials          5      5

Impacted Files
Coverage Δ

...y-Technologies-networking/Runtime/NetworkReader.cs
39.57% <10%> (-1.58%)
:arrow_down:

...y-Technologies-networking/Runtime/NetworkWriter.cs
50.35% <20%> (-0.74%)
:arrow_down:

Unity-Technologies-networking/Runtime/BitReader.cs
85% <85%> (ø)

Unity-Technologies-networking/Runtime/BitWriter.cs
86.66% <86.66%> (ø)

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 f1ef6c3...2bec1f8. Read the comment docs.

Please submit to branch 'mirror-features'

authors: Lymdun codecov-io paulpach vis2k


text:
Package Json wrong

I wont to include your npm modules directly as esm but your package json is wrong.
the export: "module" points to "dist/index.js"
wich has this code:
  export * from './esm-es5/index.js';

but the index.js in esm-es5 is empty

any news to this?
I try to use your components in my designer: https://node-projects.github.io/web-component-designer-demo/index.html
But for this the exports need to be correct.

Thanks for sharing this with us. I'm one of the maintainers of the project.
Could you please provide me with a simple reproduction where you run into this issue?

As I explained, I create a Designer wich directly can load npm packages from unpkg (or other providers). It then parses the package.json, loads dependecies and at last loads the exports from the package.json
If you look at your package.json here: https://www.npmjs.com/package/@visa/charts?activeTab=explore
you see, your "main" export is "dist/index.cjs.js" but if you use es6 modules, you normaly look for the "modules" exoport in the package.json, wich leads to "dist/index.js" wich then leads to the empty import.
The cjs export cannot directly be used by the browser. Also the package.json normaly shoul export the es6 code via "export" definition. But at first your "modules" export should work

also when you look at your other export "dist/esm/index.js", it is also empty

https://watch.screencastify.com/v/0cBoi7zxDj5LMQ94nxiM

Thank you for the explanation, we are investigating the issue. I'll get back as soon as I have some sort of a recommendation/resolution to the issue.

Just an extra thought: Would there be a way for you to overwrite the default import behavior on your side?

i wrote the import behavior, as it i defined in node.
why do you deliver empy javascript files?
ad I cannot load cjs from the browser.
from where should I know wich files to load in your library?

Thank you for the inputs. We are further investigating the problem. As soon as I have some details on this, I'll get back.

repo: visa/visa-chart-components


text:
💥FIX : Name validation added

Title of the Pull Request

[x] Have you renamed the PR Title in a meaningful way?

Related Issue

Closes: #1255
Description
Validation is added on the name field.Now it only accepts alphabetical letters (a-z, A-Z).
How Has This Been Tested? ⚙
Type symbols and numbers into the name field and try to submit.
Screenshots 📷

Type of change
What sort of changes have you made:

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Checklist

[x] My code follows the code style of this project.
[x] I have followed the contribution guidelines
[x] I have performed a self-review of my own code.
[x] I have ensured my changes don't generate any new warnings or errors.
[x] I have updated the documentation (if necessary).
[x] I have resolved all merge conflicts.

@vishanurag  please review and merge the PR.

repo: vishanurag/Canvas-Editor


text:
Expose superagent to perform it's configuration

I would like to do something like this:
var agent = request.agent(app);
agent.superagent.parse['application/problem+json'] = agent.superagent.parse['application/json'];

It's not possible right now and I cannot use supertest for testing. I'll have to use superagent directly :(.

https://github.com/yury-sannikov/supertest/commit/3e79c452f1bd2730a51ba9589a52cf934960a508 implements this, but no pull request was created yet.

+1 please.

Since this issue was closed, does that mean this was implemented? As far as I can tell, there's no way to pass in an instance of superagent, and the instance used by supertest is not exported. Am I missing how this can be done?
https://github.com/visionmedia/supertest/blob/910a11133b94d44f8ac380a8a46bfdab2bce9f19/lib/test.js#L7

FYI, this is possible using require.resolve:
const path = require('path');
const supertestPath = path.dirname(require.resolve('supertest'));
const superagentPath = require.resolve('superagent', {
    paths: [supertestPath]
});
const superagent = require(superagentPath);

It still would be nice for supertest to export this directly though. Especially since it already exports superagent's Agent:  https://github.com/visionmedia/supertest/pull/54

authors: HolySamosa gabegorelick inovakov janfabry

repo: visionmedia/supertest


text:
Visit crashes after choose-center when hidden subset plot is the currently selected/active plot

Reported by Gary Friedman. Could be related to #17. Put up PC plot of ucd mesh of 'spheres'Put up Subset plot. Now hide it but leave it selected.Now try to choose-center.VisIt crashes. Same on 2.6.1 I am getting test dataset from Gary as I was unable to find a dataset with correct set of ingredients to trigger this bug.
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 1346
Status: Pending
Project: VisIt
Tracker: Bug
Priority: Normal
Subject: Visit crashes after choose-center when hidden subset plot is the currently selected/active plot
Assigned to: -
Category: -
Target version: -
Author: Mark Miller
Start: 02/20/2013
Due date:
% Done: 0%
Estimated time:
Created: 02/20/2013 08:45 pm
Updated: 03/06/2013 07:55 pm
Likelihood: 3 - Occasional
Severity: 4 - Crash / Wrong Results
Found in version: 2.5.2
Impact:
Expected Use:
OS: All
Support Group: Any
Description:
Reported by Gary Friedman. Could be related to #17. Put up PC plot of ucd mesh of 'spheres'Put up Subset plot. Now hide it but leave it selected.Now try to choose-center.VisIt crashes. Same on 2.6.1 I am getting test dataset from Gary as I was unable to find a dataset with correct set of ingredients to trigger this bug.
Comments:

@markcmiller86 were you able to get a dataset to reproduce this issue?

repo: visit-dav/visit


text:
Update doc for DBPutQuadmesh for surfaces/paths embedded in higher dim spaces

Likewise, if 2 of the dimensions are 1, it means the mesh is representing line elements. So, heres the rub thoughHow does one represent in Silo a structured collection of quads in 3 space (e.g. a surface of quads in 3 space). Silos DBPutQuadmesh call expects that number of dimensions specifies both the topological arrangement of nodes/zones and the geometric interpretation in terms of number of coordinate components. Thats limiting! Those two ideas should be de-coupled. So, to get around this issue, a caller would specify ndims=3 (achieving the desired 3-component coordinate) but then specify one of the dimension sizes as 1 ensuring they are treated as surface elements instead. This is a hackish way to model a structured surface of quads embedded in 3 space. But, it kinda sorta does work. Silos API is over 20 years old at this point
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 3040
Status: New
Project: VisIt
Tracker: Docs
Priority: Normal
Subject: Update doc for DBPutQuadmesh for surfaces/paths embedded in higher dim spaces
Assigned to: -
Category: -
Target version: -
Author: Mark Miller
Start: 03/09/2018
Due date:
% Done: 0%
Estimated time:
Created: 03/09/2018 03:05 pm
Updated:
Likelihood: 3 - Occasional
Severity: 2 - Minor Irritation
Found in version:
Impact:
Expected Use:
OS:
Support Group: Any
Description:
Likewise, if 2 of the dimensions are 1, it means the mesh is representing line elements. So, heres the rub thoughHow does one represent in Silo a structured collection of quads in 3 space (e.g. a surface of quads in 3 space). Silos DBPutQuadmesh call expects that number of dimensions specifies both the topological arrangement of nodes/zones and the geometric interpretation in terms of number of coordinate components. Thats limiting! Those two ideas should be de-coupled. So, to get around this issue, a caller would specify ndims=3 (achieving the desired 3-component coordinate) but then specify one of the dimension sizes as 1 ensuring they are treated as surface elements instead. This is a hackish way to model a structured surface of quads embedded in 3 space. But, it kinda sorta does work. Silos API is over 20 years old at this point
Comments:

@markcmiller86 we think this is a silo ticket