text:
Remove relsase info to resolve setup bug

There is this bug that happens when you run  pip install -e . the error report is below.
This is a quick fix that takes care of that
(venv) C:\Users\Manav\Desktop\Rocketry\omnibus>pip install -e .
Defaulting to user installation because normal site-packages is not writeable
Obtaining file:///C:/Users/Manav/Desktop/Rocketry/omnibus
  Installing build dependencies ... done
  Checking if build backend supports build_editable ... done
  Getting requirements to build editable ... error
  error: subprocess-exited-with-error

  × Getting requirements to build editable did not run successfully.
  │ exit code: 1
  ╰─> [27 lines of output]
      Traceback (most recent call last):
        File "C:\Users\Manav\AppData\Roaming\Python\Python312\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py", line 353, in <module>
          main()
        File "C:\Users\Manav\AppData\Roaming\Python\Python312\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "C:\Users\Manav\AppData\Roaming\Python\Python312\site-packages\pip\_vendor\pyproject_hooks\_in_process\_in_process.py", line 132, in get_requires_for_build_editable
          return hook(config_settings)
                 ^^^^^^^^^^^^^^^^^^^^^
        File "C:\Users\Manav\AppData\Local\Temp\pip-build-env-4lozi648\overlay\Lib\site-packages\setuptools\build_meta.py", line 458, in get_requires_for_build_editable
          return self.get_requires_for_build_wheel(config_settings)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "C:\Users\Manav\AppData\Local\Temp\pip-build-env-4lozi648\overlay\Lib\site-packages\setuptools\build_meta.py", line 327, in get_requires_for_build_wheel
          return self._get_build_requires(config_settings, requirements=[])
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "C:\Users\Manav\AppData\Local\Temp\pip-build-env-4lozi648\overlay\Lib\site-packages\setuptools\build_meta.py", line 297, in _get_build_requires
          self.run_setup()
        File "C:\Users\Manav\AppData\Local\Temp\pip-build-env-4lozi648\overlay\Lib\site-packages\setuptools\build_meta.py", line 497, in run_setup
          super().run_setup(setup_script=setup_script)
        File "C:\Users\Manav\AppData\Local\Temp\pip-build-env-4lozi648\overlay\Lib\site-packages\setuptools\build_meta.py", line 313, in run_setup
          exec(code, locals())
        File "<string>", line 5, in <module>
        File "C:\Users\Manav\Desktop\Rocketry\omnibus\omnibus\__init__.py", line 1, in <module>
          from .omnibus import Sender, Receiver, Message
        File "C:\Users\Manav\Desktop\Rocketry\omnibus\omnibus\omnibus.py", line 6, in <module>
          import msgpack
      ModuleNotFoundError: No module named 'msgpack'
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build editable did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

This change is

setup.py line 13 at r1 (raw file):

    name='omnibus',
    version='1.0.0',
    description='A unified data bus',

Everything looks good! Feel free to merge when you can.

authors: BigLiban KavinSatheeskumar

repo: waterloo-rocketry/omnibus


text:
Add support for Swift 3.0

Our understanding is that Swift 3.0 should be in a (relatively) stable preview state by July 27.
"The last day to take planned source-breaking changes for Swift 3 is July 27." -- https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160711/024424.html
That would be a good time to start a swift3 branch and transition the SDK to support Swift 3.0.
We should also examine many of the decisions that we made in the SDK. With so many changes for Swift 3.0, it would also be a good time to change features of the SDK. For example--do we like separate success and failure functions? how do users authenticate? is the RestKit serialization working well for us? are there any dependencies we should drop? do we want to change the API for any of the services?

Any word on when this might happen? Next few weeks? Months? Thanks!

Yeah! Should be in the next few weeks. I think this is a high-priority issue that we should tackle in our next sprint (9/26 - 10/7). I'll be sure to advocate for it in our team's upcoming planning meeting.

Thanks I'll add my comment as well. Xcode 8 recommends by default updating all projects to Swift 3, and with this module not compiled in Swift 3 it is not possible to update the rest of the project to swift 3 (almost worse than the Objective-C to Swift transition because at least that allowed bridging headers). Looking forward to this as it pains me to not update to swift 3 immediately. Thanks.

Thanks for your comment, @kteman. It's always good for us to hear about our users' experiences, and it's really helpful to hear that users are frustrated by the lack of Swift 3.0 support. This is more ammunition for me to try and prioritize Swift 3.0 support in our upcoming sprint. Thanks!

Thanks. It's pretty important to me as this is the only barrier for getting my project to Swift 3. I'm looking forward to making that transition sooner than later (like taking care of house cleaning, want to get it done).

I want to give a quick update for anyone following this issue:
We made a lot of progress migrating the SDK to Swift 3.0. In the swift-3.0 branch we've been able to update the project settings and move all of our services to Swift 3.0 (with the exception of Speech to Text which requires some more work around the interfaces to C libraries).
There's still a lot of work to be done, though, before we feel comfortable publishing a release. In particular, we want to review the SDK and adhere to the Swift 3.0 API Design Guidelines. We expect a lot of changes to the API (mostly around parameter names).
Ideally, we would finish the Swift 3.0 migration by 10/7. But realistically, it will probably take another week or two since there are some important outstanding issues and user questions that we should address.
Be aware that the swift-3.0 branch is still under active development--we expect a lot of changes over the coming week or two. If you want to live on the cutting-edge, you can specify the swift-3.0 branch in your Cartfile (github "watson-developer-cloud/ios-sdk" "swift-3.0"), but expect breaking changes as we push new commits.

The code builds and tests pass. We're reviewing PRs to rename the SDK methods according to the Swift 3.0 API Guidelines. Hope to get it released soon.

sorry... I don't understand "PRs to rename the SDK methods according to the Swift 3.0 API Guidelines".  Pull Requests? I don't see any that rename methods.  Guess I need to google "Swift 3.0 API Guidelines".  Do you think the swift-3.0 branch is good enough to use in development as we don't want to go back to 2.3 when we need to use 3.0 for other libraries.

We have migrated the SDK to Swift 3.0 and removed the Alamofire and Freddy dependencies in the swift-3.0-remove-dependencies branch. We'll be merging that branch to master and publishing a release today or Monday after updating the readme and tackling issue #510 with Visual Recognition.
Thanks for your patience, all. We've been doing our best to tackle issues and deliver, but the team here has been pulled in many different directions, causing some of these issues to take much longer than expected.

Thanks so much for y'all's work on this Glenn!

Just for being secure myself 😏, I can use the swift-3 branch right now? (I can't wait until monday)

I would actually recommend the swift-3-remove-dependencies branch. It's a bit newer. The readme and quickstart guides have also been updated in that branch, in case you find them helpful.

source: gharchive/issue

authors: MatthewWaller glennrfisher horaciogarza kteman troyibm

repo: watson-developer-cloud/ios-sdk

license_type: permissive

license_source: github-api


text:
Directory Structure for repo in terms of package directories

This single repo holds multiple packages.
There should be top level packages directory.
Then under packages a directory per package
Then under each package have actions, annotations and README files
It should be structure differently to illustrate the content better and segregate per package.
packages
├── conversation-v1
│   ├── conversation-v1.json
│   ├── create-counterexample.js
│   ├── create-counterexample.json
│   ├── create-dialog-node.js
│   ├── create-dialog-node.json
│   ├── README.md
...
├── discovery-v1
│   ├── add-document.js
│   ├── add-document.json
│   ├── add-training-data.js
│   ├── add-training-data.json
│   ├── README.md
...
├── language-translator-v2
│   ├── create-model.js
│   ├── create-model.json
│   ├── delete-model.js
│   ├── delete-model.json
│   ├── README.md
....
├── natural-language-classifier-v1
│   ├── classify.js
│   ├── classify.json
│   ├── create-classifier.js
│   ├── create-classifier.json
│   ├── delete-classifier.js
│   ├── delete-classifier.json
│   ├── README.md
....

Will these packages be delivered in other runtimes/languages in the future, or are there only plans for node?
I think for now, this is okay, but we might want to think about how this divides in the future.  For other packages, we do something like:
runtimes
|--nodejs
| . |--conversationv1
| . | . |--coversation-v1.json
| . | . |--create-counterexample.js
|--python
| . |--conversationv1
| . | . |--coversation-v1.json
| . | . |--create-counterexample.js

@csantanapr @anweshan this issue can be closed.

authors: beemarie csantanapr

repo: watson-developer-cloud/openwhisk-sdk


text:
Revert "Feature/project readme"

Reverts watsona22/prework-study-guide#11

Revert request.

source: gharchive/pull-request

license: MIT


text:
useReactFlow: setNodes([]) does nothing

Describe the Bug
Calling setNodes([]) in an effect or event callback does nothing. It's only the setNodes from useReactFlow. The setNodes from useNodesState() works.
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
As described above. This will happen in any application.
Expected behavior
setNodes([]) should remove all nodes.
Screenshots or Videos
No response
Platform

OS: Win10
Browser: na. Electron
Version: "10.0.8

Additional context
This is the implementation for setNodes. In my debugging, hasDefaultNodes was false and onNodesChange was a function, so we take the else if branch.
      const changes = nextNodes.map((node) => ({ item: node, type: 'reset' } as NodeResetChange<NodeData>));
      onNodesChange(changes);

Since my nextNodes is empty, changes will also be empty. Hence, applyChanges find no c.type === 'reset' change.

setEdges has the same bug.

@moklick, @chrtze Is there an interest in fixing this?

Hey @RunDevelopment
I will check your PR now. I think, that we made a mistake by allowing users to use these functions for controlled flows. They were only meant to be used with uncontrolled flows and also not necessary for controlled flows. Not 100% sure if I want to go this road further or remove the functionality completely for controlled flows.

It would be nice if useReactFlow could continue to work for both. It's simply very convenient to have access to all nodes and edges (and their setters) without having to do the context work/props passing yourself.
We currently work around this bug by passing the setNodes and setEdges function around using a context.

Thanks for your help! This was a good fix for the issue and you are right, that it's very convenient to have these helper functions.

released in v10.2.3

Thank you, @moklick!

I am facing the same thing with version 11.7.3 calling setNodes from useReactFlow doesn't update the nodes defined with:
 const [nodes, setNodes, onNodesChange] = useNodesState(props.nodes);

Only calling setNodes from useNodesState seems to update the state. Is this known or is there any workaround? Similar to @RunDevelopment I don't want to prop drill setNodes in the tree.

Can you create a codesandbox for this? I can't repro your issue: https://codesandbox.io/s/summer-pine-vvt7h6?file=/src/NodeResetter.tsx:175-233

@moklick Thanks for taking the time to prepare the sandbox. I found what the problem was:
I was using the useReactFlow from within a sibling component from <ReactFlow />. I moved the sibling component to be a child and rendered it inside a Panel and now the setNodes function works.
What I don't understand is that my structure was:
<ReactFlowProvider>
    <SettingsMenu />
    <ReactFlow />
</ReactFlowProvider>

From the SettingsMenu component I was calling the setNodes function. Shouldn't the SettingsMenu be able to call the setNodes function in this structure?
In any case, I changed the structure to be:
<ReactFlowProvider>
    <ReactFlow>
        <SettingsMenu />
    <ReactFlow />
</ReactFlowProvider>

And it works fine now!

I found the same thing.  Can you explain why the setNodes function was only effective within the ReactFlow component's subtree? @moklick

That's a bit weird indeed and shouldn't be the case. I will take a look.

That's a bit weird indeed and shouldn't be the case. I will take a look.

Sorry, I made a mistake, it actually works, thanks for your reply

authors: RunDevelopment dongtc moklick nathanqueija

repo: wbkd/react-flow


text:
How can I achieve 1-way connection between nodes?

First of all, thank you for this awesome library, I can make my graph the way I want with ease.
However, I was trying to create a graph where every node only provides the 1-way connection: click & hold the mouse button on the "source Handle", drag to the target node (anywhere inside the target node, not only around its "target Handle") and release the mouse button to create the connection.
I figure out my way to achieve this: style the "target Handle" to be as large as its whole node, so that I can release the mouse anywhere inside the node, it will be a release on the "target Handle" to establish the connection.
But there are some problems:

The "target Handle" now overlaying upon the node, so I can't move the node.
The connection line can be started from both source & target Handle.

What I want are:

When dragging the connection line, release it on the node will establish the connection
Disable the drag gesture of the "target Handle", so 1-way connection must start from "source Handle"

Thanks in advance!

Hey @buitrung
thanks for your kind words :)
You need to implement some custom behaviour here but I think it's possible.
I would try this:

Make all target handlers invisible by default
Make them visible by setting a with a flag or class in the onConnectStart handler
Unset the flag or class in the onConnectStop handler with a 1ms timeout (I just saw that onConnectStop gets called before onConnect. I think we should change this. Then you would not need the timeout).

I think you are right. I thought that we would need a function that gets called after onConnect but it makes no difference. You can use onConnectStop.

Here is the order of method called:
onConnectStart
onConnectStop
onConnect
onConnectEnd
If the connection is not established then onConnectEnd will not be called, that's the difference.
In my case, using one over the other makes no difference. However it is still convenient to have these both methods, like when I want to make sure user has successfully dragged the connection line to a node.

Alright! I am glad it worked out for you :)

This looks very interesting. Sorry to try to revive this, but I'm struggling to update the class for the handle on onConnectStart. Any one can help?
I created a custom node and the target handles are now invisible (through classes), I want to make them visible upon onConnectStart but I can't find the best way to do so. Should I just select the element via class? thanks!

@chandantiwari1 you can create a custom node and set isConnectableStart of the source handle to false if there is already a connection.
const isSourceConnected = useStore(s => s.edges.find((edge) => edge.source === id));

Hi can you @buitrung can you share some code example here ?

authors: CarlosSuarezJS20 buitrung kishan-getstarted moklick


text:
Modify node selection from outside

There is a way to listen for selection changes onSelectionChange and to define if elements are selectable.
If I'm not mistaken, there is no way define or change which elements are selected from outside. Also there is no way to ask which elements are currently selected on reactFlowInstance or with  ReactFlowProvider.
If that's correct, it would be neat to add this :)
Update
I guess one could use ReactFlowProvider to listen for selected elements.
https://github.com/wbkd/react-flow/blob/f35ad054364baf605bad30471f0306f211a34055/src/container/EdgeRenderer/index.tsx#L202
This issue is about changing it from outside, though :)

I added an example in the provider example.

Hi how to select multiple node in the new reactflow??

@zyaanbookee in mac, hold command button and click target nodes

For developers who are coming after 2023, you can use useStoreApi provided by reactflow to update node selection from outside.
Example:
update selection from outside when clicked on custom node:
import { useStoreApi } from 'reactflow';

const { addSelectedNodes } = store.getState()

// updating selection when clicked on custom node
const updateActiveNode = () => {
    const temp = nodes.find((node) => node.id === id)
    if (temp) addSelectedNodes([temp.id]) // provide array of node ids
}

For developers who are coming after 2023, you can use useStoreApi provided by reactflow to update node selection from outside.
Example: update selection from outside when clicked on custom node:
import { useStoreApi } from 'reactflow';

const { addSelectedNodes } = store.getState()

// updating selection when clicked on custom node
const updateActiveNode = () => {
    const temp = nodes.find((node) => node.id === id)
    if (temp) addSelectedNodes([temp.id]) // provide array of node ids
}

Does it concatenate the current selection with the provided array, or does it set the selection to the provided array?

authors: MatheusRoichman andys8 imvetri kartikk-k moklick zyaanbookee


text:
Condense origin address entries into a single table.

Fixes #323

Minor comment aside, LGTM.

repo: weaveworks/scope


text:
Revises branch planner pages a bit

Reorganizes and streamlines branch planner pages. More editing to come, but this is a first pass.

We seem to have added the branch-planner.png file twice in this PR in 2 different paths, let's fix if this was not intentional.

authors: LappleApple yiannistri

repo: weaveworks/tf-controller


text:
Kubernetes API cannot reach Kubernetes Dashboard

In my setup I have a master and a node both with a public IP and connected to each other using a VPN. Kubernetes was deployed using Kubeadm and weave was deployed using https://git.io/weave-kube. Kubeadm used the -api-advertise-addresses parameter where only the VPN assigned address for the master was given.
This all works, master and node can see each other on both sides of the VPN. Weave starts and both sides can find each other using the public IPs (eth0). Those are not connected to the same switch.
This gives us the following networking situation:

Master
Node

eth0 (IPv4)
eth0 (IPv4)

tun0 (VPN)
tun0 (VPN)

weave
weave

Next I deployed the Kubernetes Dashboard which got assigned to the node. The dashboard starts and connects to the api deployed on the master.
To access the dashboard I use the following command on the master node:
curl -v -L http://127.0.0.1:8080/ui

After a while it fails with:
Error: 'dial tcp 10.32.0.1:9090: i/o timeout'

After some searching I noticed the weave interace on the master node had no address assigned. I had a chat with @bboreham and doing a manual local expose in the weave pod on the master solved my problem. He told me weave will only assign an address if a pod uses the pod network on the specific host. In my case only pods using the host network were deployed and therefore no address was assigned.
This leads to the problem that the kubernetes api can't use the pod network where the kubernetes dashboard pod is deployed.
The setup is composed of two Ubuntu 16.04 machines with nothing special. Uname -a lists for both:
Linux 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:39:52 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

I hope this report helps.

@bpasson @bboreham  could you share the manual solution on how to expose kubernetes service (api server)? I ran into a similar situation:

3 master kubernete nodes running inside private network (coreos 1185.3.0/stable + hyperkube)
2 worker nodes (cores 1185.3.0/stable + hyperkube) are available via public Internet

The weave-npc containers running on the worker nodes are unable to connect to the kubernetes apiserver service (e.g. 10.13.0.1), which causes all weave network connections (not on host os, only inside POD containers) blocked by the weave-npc container.
kubectl logs -c weave-npc weave-net-xxxx
E1127 03:55:02.816764    1955 reflector.go:214] github.com/weaveworks/weave/vendor/k8s.io/client-go/tools/cache/reflector.go:109: Failed to list *v1.Namespace: Get https://10.16.0.1:443/api/v1/namespaces?resourceVersion=0: dial tcp 10.16.0.1:443: i/o timeout

/home/weave # curl -kv http://localhost:6781/metrics
...
# HELP weavenpc_blocked_connections_total Connection attempts blocked by policy controller.
# TYPE weavenpc_blocked_connections_total counter
weavenpc_blocked_connections_total{dport="53",protocol="udp"} 50190
weavenpc_blocked_connections_total{dport="80",protocol="tcp"} 11

If you log in the machine which has no address assigned to the weave interface use docker ps to locate the weaveworks/weave-kube container. If you found it, open a shell as follows:
$ docker exec -it <container-id> sh

Inside the container you can then run the following to have the interface get an address assigned:
# /home/weave/weave --local expose

Keep in mind that if the machine reboots you need to do this again. In my setup I created a DaemonSet to run a very small http-server that uses the pod network to force weave to do a local expose on every node.

Hi sorry, this was most likely an unintended consequence of #2637, which moved the expose call inside the CNI plugin.  You are getting this symptom because the plugin never runs if there are no pods on the node.
Therefore another workaround is to arrange that there is some pod run on the node each time it boots - it doesn't matter if it then continues running or finishes.  It needs to use the pod network though; all of Kubernetes' own pods on master run in the host network.

authors: bboreham bpasson je2ryw

repo: weaveworks/weave

license_source: bigquery


text:
Set cannot be destroyed: it is in use by a kernel component

What happened?
Getting "ipset v7.2: Set cannot be destroyed: it is in use by a kernel component"
[root@k10dal1terarocketio ~]# kubectl get all --all-namespaces
NAMESPACE     NAME                                              READY   STATUS              RESTARTS   AGE
kube-system   pod/coredns-f9fd979d6-mdnst                       0/1     ContainerCreating   0          117s
kube-system   pod/coredns-f9fd979d6-xxzvl                       0/1     ContainerCreating   0          117s
kube-system   pod/etcd-k10dal1terarocketio                      1/1     Running             0          2m8s
kube-system   pod/kube-apiserver-k10dal1terarocketio            1/1     Running             0          2m8s
kube-system   pod/kube-controller-manager-k10dal1terarocketio   1/1     Running             0          2m8s
kube-system   pod/kube-proxy-m74fl                              1/1     Running             0          117s
kube-system   pod/kube-scheduler-k10dal1terarocketio            1/1     Running             0          2m8s
kube-system   pod/weave-net-sfwg2                               1/2     CrashLoopBackOff    4          117s

NAMESPACE     NAME                 TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)                  AGE
default       service/kubernetes   ClusterIP   10.96.0.1    <none>        443/TCP                  2m15s
kube-system   service/kube-dns     ClusterIP   10.96.0.10   <none>        53/UDP,53/TCP,9153/TCP   2m14s

NAMESPACE     NAME                        DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
kube-system   daemonset.apps/kube-proxy   1         1         1       1            1           kubernetes.io/os=linux   2m14s
kube-system   daemonset.apps/weave-net    1         1         0       1            0           <none>                   2m8s

NAMESPACE     NAME                      READY   UP-TO-DATE   AVAILABLE   AGE
kube-system   deployment.apps/coredns   0/2     2            0           2m14s

NAMESPACE     NAME                                DESIRED   CURRENT   READY   AGE
kube-system   replicaset.apps/coredns-f9fd979d6   2         2         0       117s

How to reproduce it?

CentOS 8
cri-o
Kubernetes 1.19.3
Deploy weave:
kubectl apply -f "https://cloud.weave.works/k8s/net?k8s-version=$(kubectl version | base64 | tr -d '\n')&env.IPTABLES_BACKEND=nft"

Anything else we need to know?
Vultr VM. CentOS 8, 4GiB of RAM
Versions:

[root@server ~]# uname -a
Linux server 4.18.0-193.19.1.el8_2.x86_64 #1 SMP Mon Sep 14 14:37:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
[root@server ~]# kubectl version
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T12:50:19Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T12:41:49Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/amd64"}

Logs:
[root@server ~]# kubectl -n kube-system logs pod/weave-net-sfwg2 weave
ipset v7.2: Set cannot be destroyed: it is in use by a kernel component
[root@server ~]# kubectl -n kube-system logs pod/weave-net-sfwg2 weave-npc
INFO: 2020/10/20 14:16:48.880872 Starting Weaveworks NPC 2.7.0; node name "k10dal1terarocketio"
INFO: 2020/10/20 14:16:48.881322 Serving /metrics on :6781
Tue Oct 20 14:16:48 2020 <5> ulogd.c:408 registering plugin `NFLOG'
Tue Oct 20 14:16:48 2020 <5> ulogd.c:408 registering plugin `BASE'
Tue Oct 20 14:16:48 2020 <5> ulogd.c:408 registering plugin `PCAP'
Tue Oct 20 14:16:48 2020 <5> ulogd.c:981 building new pluginstance stack: 'log1:NFLOG,base1:BASE,pcap1:PCAP'
WARNING: scheduler configuration failed: Function not implemented
DEBU: 2020/10/20 14:16:48.904826 Got list of ipsets: [weave-kube-test]
DEBU: 2020/10/20 14:16:48.904849 Flushing ipset 'weave-kube-test'
DEBU: 2020/10/20 14:16:48.905421 Destroying ipset 'weave-kube-test'
INFO: 2020/10/20 14:16:48.965197 EVENT AddNamespace {"metadata":{"creationTimestamp":"2020-10-20T14:16:20Z","managedFields":[{"apiVersion":"v1","fieldsType":"FieldsV1","fieldsV1":{"f:status":{"f:phase":{}}},"manager":"kube-apiserver","operation":"Update","time":"2020-10-20T14:16:20Z"}],"name":"default","resourceVersion":"162","selfLink":"/api/v1/namespaces/default","uid":"b22b510a-72de-49fd-b8c0-a2ee10bea40b"},"spec":{"finalizers":["kubernetes"]},"status":{"phase":"Active"}}
INFO: 2020/10/20 14:16:48.976327 creating ipset: &npc.selectorSpec{key:"", podSelector:labels.internalSelector{}, namespaceSelector:labels.Selector(nil), policyTypes:[]npc.policyType(nil), ipsetType:"hash:ip", ipsetName:"weave-k?Z;25^M}|1s7P3|H9i;*;MhG", nsName:"default"}
DEBU: 2020/10/20 14:16:48.977034 adding rule for DefaultAllow in namespace: default, chain: WEAVE-NPC-DEFAULT, [-m set --match-set weave-;rGqyMIl1HN^cfDki~Z$3]6!N dst -j ACCEPT -m comment --comment DefaultAllow ingress isolation for namespace: default]
DEBU: 2020/10/20 14:16:48.978996 adding rule for DefaultAllow in namespace: default, chain: WEAVE-NPC-EGRESS-DEFAULT, [-m set --match-set weave-s_+ChJId4Uy_$}G;WdH|~TK)I src -j WEAVE-NPC-EGRESS-ACCEPT -m comment --comment DefaultAllow egress isolation for namespace: default]
DEBU: 2020/10/20 14:16:48.980585 adding rule for DefaultAllow in namespace: default, chain: WEAVE-NPC-EGRESS-DEFAULT, [-m set --match-set weave-s_+ChJId4Uy_$}G;WdH|~TK)I src -j RETURN -m comment --comment DefaultAllow egress isolation for namespace: default]
INFO: 2020/10/20 14:16:48.982342 EVENT AddNamespace {"metadata":{"creationTimestamp":"2020-10-20T14:16:19Z","managedFields":[{"apiVersion":"v1","fieldsType":"FieldsV1","fieldsV1":{"f:status":{"f:phase":{}}},"manager":"kube-apiserver","operation":"Update","time":"2020-10-20T14:16:19Z"}],"name":"kube-system","resourceVersion":"10","selfLink":"/api/v1/namespaces/kube-system","uid":"1d3ff025-501b-4395-a50f-6b25a7650da3"},"spec":{"finalizers":["kubernetes"]},"status":{"phase":"Active"}}
INFO: 2020/10/20 14:16:48.985383 creating ipset: &npc.selectorSpec{key:"", podSelector:labels.internalSelector{}, namespaceSelector:labels.Selector(nil), policyTypes:[]npc.policyType(nil), ipsetType:"hash:ip", ipsetName:"weave-iuZcey(5DeXbzgRFs8Szo]+@p", nsName:"kube-system"}
DEBU: 2020/10/20 14:16:48.985956 adding rule for DefaultAllow in namespace: kube-system, chain: WEAVE-NPC-DEFAULT, [-m set --match-set weave-P.B|!ZhkAr5q=XZ?3}tMBA+0 dst -j ACCEPT -m comment --comment DefaultAllow ingress isolation for namespace: kube-system]
DEBU: 2020/10/20 14:16:48.987540 adding rule for DefaultAllow in namespace: kube-system, chain: WEAVE-NPC-EGRESS-DEFAULT, [-m set --match-set weave-E1ney4o[ojNrLk.6rOHi;7MPE src -j WEAVE-NPC-EGRESS-ACCEPT -m comment --comment DefaultAllow egress isolation for namespace: kube-system]
DEBU: 2020/10/20 14:16:48.989199 adding rule for DefaultAllow in namespace: kube-system, chain: WEAVE-NPC-EGRESS-DEFAULT, [-m set --match-set weave-E1ney4o[ojNrLk.6rOHi;7MPE src -j RETURN -m comment --comment DefaultAllow egress isolation for namespace: kube-system]
DEBU: 2020/10/20 14:16:48.992608 EVENT AddPod

Network:
# ipset list
Name: weave-;rGqyMIl1HN^cfDki~Z$3]6!N
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536 comment
Size in memory: 120
References: 1
Number of entries: 0
Members:

Name: weave-s_+ChJId4Uy_$}G;WdH|~TK)I
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536 comment
Size in memory: 120
References: 2
Number of entries: 0
Members:

Name: weave-k?Z;25^M}|1s7P3|H9i;*;MhG
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536 comment
Size in memory: 120
References: 0
Number of entries: 0
Members:

Name: weave-P.B|!ZhkAr5q=XZ?3}tMBA+0
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536 comment
Size in memory: 120
References: 1
Number of entries: 0
Members:

Name: weave-E1ney4o[ojNrLk.6rOHi;7MPE
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536 comment
Size in memory: 120
References: 2
Number of entries: 0
Members:

Name: weave-iuZcey(5DeXbzgRFs8Szo]+@p
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536 comment
Size in memory: 120
References: 0
Number of entries: 0
Members:

Name: weave-Rzff}h:=]JaaJl/G;(XJpGjZ[
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536 comment
Size in memory: 120
References: 1
Number of entries: 0
Members:

Name: weave-41s)5vQ^o/xWGz6a20N:~?#|E
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536 comment
Size in memory: 120
References: 2
Number of entries: 0
Members:

Name: weave-4vtqMI+kx/2]jD%_c0S%thO%V
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536 comment
Size in memory: 120
References: 0
Number of entries: 0
Members:

Name: weave-]B*(W?)t*z5O17G044[gUo#$l
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536 comment
Size in memory: 120
References: 1
Number of entries: 0
Members:

Name: weave-sui%__gZ}{kX~oZgI_Ttqp=Dp
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536 comment
Size in memory: 120
References: 2
Number of entries: 0
Members:

Name: weave-mF}1zpEo4W6iYroE^=:V3{S6W
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536 comment
Size in memory: 120
References: 0
Number of entries: 0
Members:

Name: weave-kube-test
Type: hash:ip
Revision: 4
Header: family inet hashsize 1024 maxelem 65536
Size in memory: 120
References: 0
Number of entries: 0
Members:

This happens every time weave is deployed.

If I ipset destroy weave-kube-test, it just gets recreated by the weave pod every time it attempts to start.

Seeing folks hacking in a sleep 1 before the ipset destroy call:
https://github.com/replicatedhq/kURL/pull/717/commits/877767c3abf7f498574f9b2e4199e208683a4dca
It's kind of messy, but maybe something that needs added until the race condition can be figured out.

The solution listed above immediately fixed the issue for me

It seems worked for me, thank you @kallisti5. However, in CentOS 8, the issue can reproduced more easily.

It seems worked for me, thank you @kallisti5. However, in CentOS 8, the issue can reproduced more easily.

This also worked for me when using Kubespray to deploy Kubernetes cluster with Weave. After modifying roles/network_plugin/weave/templates/weave-net.yml.j2 according to the patch provided above everything worked like a charm.
Thanks!

authors: fuzhibo kallisti5 matulek


text:
Template for GitHub issues

Should hopefully help triage users and diagnose bugs in more effective ways.

Sample output:

Setup & Logs
Weave Version
$ weave version

Docker Version
$ docker version

Weave Logs
$ docker logs weave
## or, under Kubernetes:
$ kubectl logs -n kube-system <weave-net-pod> weave
## If very long, please consider a Gist.

Docker Daemon Logs
$ journalctl -u docker.service --no-pager
## or equivalent under your OS.
## If very long, please consider a Gist.

Environment
Cloud provider or hardware configuration
OS
$ cat /etc/*release*

Kernel
$ uname -a

Network configuration:
$ ip route
$ ip -4 -o addr
$ iptables-save
## If very long, please consider a Gist.

Install tools
For example: weave script, Kubernetes daemonset YAML, KOPS, etc.
Misc.
What happened?
What you expected to happen?
How to reproduce it? (as minimally and precisely as possible)
Anything else we need to know?

Why wouldn't we package most of the above into a weave ... command?
And why no weave report?

Why wouldn't we package most of the above into a weave ... command?
+1

And why no weave report?

Had it on my list and accidentally forgot it. Adding it now.

Kubernetes version, which I had also forgotten.

A) Any suggestion for the name of the command?

weave bug-report?
weave gh-issue?
weave full-report?
weave full-details?

B) Do we foresee any issue running this command (which would mean meta troubleshooting...) vs. separate commands (which would maybe mean they are more the responsibility of the end-user)?

with sudo or without sudo?
--kubeconfig /etc/kubernetes/admin.conf?
anything else?

Bear in mind that the more things we ask the user to do, the less likely they are actually going to file a bug report. Which would be bad.
Also, not all issues filed by users are bug reports. Some are feature requests, questions, etc, where little/none of all that info is relevant.

Bear in mind that the more things we ask the user to do, the less likely they are actually going to file a bug report. Which would be bad.

Yes, that's exactly what I thought when you mentioned having a single command to run.

Also, not all issues filed by users are bug reports. Some are feature requests, questions, etc, where little/none of all that info is relevant.

That's covered by the comments you see when you click on "New Issue", but which aren't rendered in the above sample output. See actual diff.

@rade, just to clarify my intent behind this PR:

I'd like to help users engage us in the best possible way (e.g. the Is this a REQUEST FOR HELP? section suggests useful resources and points to the help page where we mention Slack)
in case of a bug, I wanted to suggest a template (people do not have to follow it necessarily and can edit at will!) for end-users so they provide as much relevant information as possible up-front, as I've seen a lot of back and forth to get basic information/logs/etc. in the past (e.g. 12 days to know the exact Docker package on this issue: https://github.com/weaveworks/weave/issues/2835#issuecomment-288132014), which in the end is bad for everyone:

end-users don't receive timely help
we miss opportunities to help them be successful with Weave Net, to fix bugs, etc.

also, in quite a few cases we've had replies like "sorry, I've already removed the cluster", while providing guidance up-front could have avoided this.
it is common practice to have such template, e.g.:

https://github.com/kubernetes/kubernetes/issues/new
https://github.com/hashicorp/terraform/issues/new

I'm all for making this less manual with an unique command, and even ultimately fully automate it, but in the meantime, I believe this PR is a small step forward.
Please let me know if you're completely against it, and I'll just close the PR. Thanks!

I am not against this, but feel the list of stuff we ask for is simply too long. Note that the examples you cite ask for considerably less info.
I fear as it stands the first impression to potential bug submitters will be "This is daunting, I don't have time for this."
So until we have packaged things into a command, we should ask for less.

I have rephrased a few things and shortened it a bit for now.
I may come up with a command later, but any issue running it may create even more confusion among users.
As usual, any constructive feedback is welcome! @brb, @bboreham feel free to share your opinion!
Note that text within HTML comment blocks (<!-- -->) does not get rendered by Markdown, but they appear when you click the "New Issue" button.

<!--
Hi, thank you for opening an issue!
Before hitting the button...

** Is this a REQUEST FOR HELP? **
If so, please have a look at:
- our FAQ: https://www.weave.works/docs/net/latest/faq/
- our troubleshooting page: https://www.weave.works/docs/net/latest/troubleshooting/
- our help page, to choose the best channel (Slack, etc.) to reach out: https://www.weave.works/help/

** Is this a FEATURE REQUEST? **
If so, please search existing feature requests, and if you find a similar one, up-vote it and/or add your comments to it instead.
If you did not find a similar one, please describe in details:
- why: your use-case, specific constraints you may have, etc.
- what: the feature/behaviour/change you would like to see in Weave Net
Do not hesitate, when appropriate, to share the exact commands or API you would like, and/or to share a diagram (e.g.: asciiflow.com): "a picture is worth a thousand words".

** Is this a BUG REPORT? **
If so, please search existing bug reports, and if you find a similar one, up-vote it and/or add your comments to it instead.
If you did not find a similar one, please fill in as much of the template below as you can.
If you leave out information, we will not be able to help you as well.

In all cases, be ready for follow-up questions and please respond in a timely manner.
If we cannot reproduce a bug or think a feature already exists, we might close your issue.
If we are wrong, please feel free to reopen it and explain why.

Thank you!
-->

Environment:
Weave:
$ weave report

Docker:
$ docker version
$ docker-runc --version

Kubernetes:
$ kubectl version

Logs:
<!-- Anything interesting or unusual output by the below, potentially relevant, commands? -->
<!-- (If output is long, please consider a Gist.) -->

$ docker logs weave
$ journalctl -u docker.service --no-pager
$ kubectl logs -n kube-system <weave-net-pod> weave
$ kubectl get events

OS:
$ uname -a
$ cat /etc/*release*

Network:
$ ip route
$ ip -4 -o addr

<!-- Anything interesting or unusual output by iptables-save? -->
<!-- (If output is long, please consider a Gist.) -->

What you expected to happen?
What happened?
<!-- Error message, actual behaviour, etc. -->

How to reproduce it?
<!-- Specific steps, as minimally and precisely as possible. -->

Anything else we need to know?
<!-- Cloud provider? Hardware? How did you configure your cluster? Kubernetes YAML, KOPS, etc. -->

FYI, draft of command in full-report branch: https://github.com/weaveworks/weave/commit/1fb5b8c95e55cc6d8569ad697c59192cdc5253d8
I can already see plenty of ways this could go wrong, so not sure I want to continue in this direction.

I think weave report is way too detailed to be included like this.
Also we don't want people adding "I have this issue too" to similar bug reports; mostly they are not the same and it gets very difficult to follow the threads.
I made some edits and uploaded in branch gh-issue-template-bryan
see https://raw.githubusercontent.com/weaveworks/weave/648709b3e76e9f8b2614c88d01f4ce955222ce4c/.github/ISSUE_TEMPLATE.md

@bboreham, I'd be fine having the version with your edits: this would be much better than no template at all!
Feel free to override this PR with it and I'll merge it.

I pushed my version onto this branch

authors: bboreham marccarre rade


text:
Querying previously created Weaviate database, Verba just says "no chunks available"

Description
Querying previously created Weaviate database, Verba just says "no chunks available"
I don't know whether this is a bug or a feature. The system might not be prepared to load a pre-existing Weaviate database.
But it would be really nice to use an existing Weaviate instance, rather than uploading files one by one. But maybe our schema differs from what's required by Verba. Any tipos for this? Would really appreciate!
Is this a bug or a feature?

[ ] Bug
[x ] Feature

Steps to Reproduce
Install Verba, point VERBA_WEAVIATE_URL to a preexisting Weaviate instance.
Try to make questions to documents there, but answering "no chunks available"

Verba currently depends on specific collection configurations, you need to upload your documents via Verba first to apply RAG on it.

authors: manolinux thomashacker

repo: weaviate/Verba


text:
docs: update how to use swc plugin in rspack rule

Summary
update how to use swc plugin in rspack rule. experimental should be used in jsc

Checklist

[ ] Tests updated (or not required).
[x] Documentation updated (or not required).

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

LGTM, thanks👍🏻

authors: CLAassistant SoonIter zhangmingyuan666

repo: web-infra-dev/rspack


text:
perf: enable xxhash64 hash function by default

Summary

Enable xxhash64 hash function by default for performance.
output.hashDigestLength now defaults to 16, as the hash value generated by the xxhash64 algorithm is up to 16 characters. This can also reduce the bundle size.
Rsbuild has been using xxhash64 since v0.1, so this change will not affect Rsbuild.

Benchmark
md4 is slow when building large files, case: https://github.com/hardfist/performance-compare-ng/tree/add-big/apps/10000-big
hyperfine --warmup 1 --runs 3 'HASH_FUNCTION=md4 node --run build:rspack' 'HASH_FUNCTION=xxhash64 node --run build:rspack'
Benchmark 1: HASH_FUNCTION=md4 node --run build:rspack
  Time (mean ± σ):     11.428 s ±  0.758 s    [User: 83.504 s, System: 5.808 s]
  Range (min … max):   10.892 s … 12.295 s    3 runs

Benchmark 2: HASH_FUNCTION=xxhash64 node --run build:rspack
  Time (mean ± σ):      9.697 s ±  0.318 s    [User: 79.664 s, System: 6.127 s]
  Range (min … max):    9.374 s … 10.009 s    3 runs

Summary
  HASH_FUNCTION=xxhash64 node --run build:rspack ran
    1.18 ± 0.09 times faster than HASH_FUNCTION=md4 node --run build:rspack

Related

https://github.com/webpack/webpack/pull/14306
https://github.com/webpack/webpack/pull/14860

Checklist

[ ] Tests updated (or not required).
[ ] Documentation updated (or not required).

!bench

!bench

authors: SoonIter chenjiahan


text:
Mixer-thread fix withdraw

related #40

#40 seems to be related with anon, this PR adds more logs to withdraw functionality


text:
Add logstash CRD /  controller

Add a way to deploy Logstash.
Implement #25

Codecov Report

Merging #42 (e27c129) into main (804d561) will increase coverage by 0.84%.
The diff coverage is 65.59%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main      #42      +/-   ##
==========================================
+ Coverage   60.94%   61.79%   +0.84%
==========================================
  Files         110      133      +23
  Lines       11226    13742    +2516
==========================================
+ Hits         6842     8492    +1650
- Misses       3945     4731     +786
- Partials      439      519      +80

Flag
Coverage Δ

unittests
61.79% <65.59%> (+0.84%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

apis/kibana/v1alpha1/kibana_types.go
100.00% <ø> (ø)

apis/kibana/v1alpha1/zz_generated.deepcopy.go
0.00% <ø> (ø)

apis/logstash/v1alpha1/zz_generated.deepcopy.go
0.00% <0.00%> (ø)

apis/shared/elasticsearch_ref.go
100.00% <ø> (ø)

apis/shared/zz_generated.deepcopy.go
0.00% <0.00%> (ø)

...trollers/elasticsearch/elasticsearch_controller.go
67.29% <0.00%> (-1.03%)
:arrow_down:

.../logstash/builder_secret_ca_elasticsearch_test..go
0.00% <0.00%> (ø)

controllers/kibana/kibana_controller.go
64.03% <33.33%> (-2.81%)
:arrow_down:

controllers/logstash/common.go
35.29% <35.29%> (ø)

controllers/logstash/controller_statefulset.go
37.36% <37.36%> (ø)

... and 28 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

repo: webcenter-fr/elasticsearch-operator


text:
[🐛 Bug]: Can't install on Windows in monrepo

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

WebdriverIO Version
latest (as of 2024-01-23)
Node.js Version
v20.11.0 (Windows 10)
Mode
WDIO Testrunner
Which capabilities are you using?
No response
What happened?
Tried to set up wdio by running npm init wdio@latest .
What is your expected behavior?
To have wdio set up and ready to run.
How to reproduce the bug.

Check out https://github.com/humanwhocodes/fsx
npm install at the top level
cd packages/memory
npm init wdio@latest .

Relevant log output
$ npm init wdio@latest .
Need to install the following packages:
  create-wdio@latest
Ok to proceed? (y) y

                 -:...........................-:.
                 +                              +
              `` +      `...`        `...`      + `
            ./+/ +    .:://:::`    `::///::`  ` + ++/.
           .+oo+ +    /:+ooo+-/    /-+ooo+-/ ./ + +oo+.
           -ooo+ +    /-+ooo+-/    /-+ooo+-/ .: + +ooo.
            -+o+ +    `::///:-`    `::///::`    + +o+-
             ``. /.     `````        `````     .: .``
                  .----------------------------.
           `-::::::::::::::::::::::::::::::::::::::::-`
          .+oooo/:------------------------------:/oooo+.
      `.--/oooo-                                  :oooo/--.`
    .::-``:oooo`                                  .oooo-``-::.
  ./-`    -oooo`--.: :.--                         .oooo-
   `-/.
 -/`    `-/oooo////////////////////////////////////oooo/.`    `/-
`+`   `/+oooooooooooooooooooooooooooooooooooooooooooooooo+:`   .+`
-/    +o/.:oooooooooooooooooooooooooooooooooooooooooooo:-/o/    +.
-/   .o+  -oooosoooososssssooooo------------------:oooo-
`oo`   +.
-/   .o+  -oooodooohyyssosshoooo`                 .oooo-
 oo.   +.
-/   .o+  -oooodooysdooooooyyooo` `.--.``     .:::-oooo-
 oo.   +.
-/   .o+  -oooodoyyodsoooooyyooo.//-..-:/:.`.//.`./oooo-
 oo.   +.
-/   .o+  -oooohsyoooyysssysoooo+-`     `-:::.    .oooo-
 oo.   +.
-/   .o+  -ooooosooooooosooooooo+//////////////////oooo-
 oo.   +.
-/   .o+  -oooooooooooooooooooooooooooooooooooooooooooo-
 oo.   +.
-/   .o+  -oooooooooooooooooooooooooooooooooooooooooooo-
 oo.   +.
-+////o+` -oooo---:///:----://::------------------:oooo-
`oo////+-
+ooooooo/`-oooo``:-```.:`.:.`.+/-    .::::::::::` .oooo-`+ooooooo+
oooooooo+`-oooo`-- `/` .:+  -/-`/`   .::::::::::  .oooo-.+oooooooo
+-/+://-/ -oooo-`:`.o-`:.:-````.:    .///:``````  -oooo-`/-//:+:-+
: :..--:-:.+ooo+/://o+/-.-:////:-....-::::-....--/+ooo+.:.:--.-- /
- /./`-:-` .:///+/ooooo/+///////////////+++ooooo/+///:. .-:.`+./ :
:-:/.           :`ooooo`/`              .:.ooooo :
    ./---
                :`ooooo`/`              .:.ooooo :
                :`ooooo./`              .:-ooooo :
                :`ooooo./`              .:-ooooo :
            `...:-+++++:/.              ./:+++++-:...`
           :-.````````/../              /.-:````````.:-
          -/::::::::://:/+             `+/:+::::::::::+.
          :oooooooooooo++/              +++oooooooooooo-

                           Webdriver.IO
              Next-gen browser and mobile automation
                    test framework for Node.js

Installing @wdio/cli to initialize project...
✔ Success!
node:internal/modules/esm/resolve:214
  const resolvedOption = FSLegacyMainResolve(packageJsonUrlString, packageConfig.main, baseStringified);
                         ^

Error: Cannot find package 'C:\Users\nzaka\projects\humanwhocodes\fsx\packages\web\node_modules\@wdio\utils\node_modules\proxy-agent\package.json' imported from C:\Users\nzaka\projects\humanwhocodes\fsx\packages\web\node_modules\@wdio\utils\node_modules\@puppeteer\browsers\lib\esm\httpUtil.js
    at legacyMainResolve (node:internal/modules/esm/resolve:214:26)
    at packageResolve (node:internal/modules/esm/resolve:840:14)
    at moduleResolve (node:internal/modules/esm/resolve:910:20)
    at defaultResolve (node:internal/modules/esm/resolve:1130:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:396:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:365:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:240:38)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:85:39)
    at link (node:internal/modules/esm/module_job:84:36)
{
  code: 'ERR_MODULE_NOT_FOUND'
}

Node.js v20.11.0

⚠  Ups, something went wrong: Error calling: npx wdio co
nfig!
npm ERR! code 1
npm ERR! path C:\Users\nzaka\projects\humanwhocodes\fsx\packages\web
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c create-wdio "."

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\nzaka\AppData\Local\npm-cache\_logs\2024-01-24T00_21_30_109Z-debug.log

### Code of Conduct

- [X] I agree to follow this project's Code of Conduct

### Is there an existing issue for this?

- [X] I have searched the existing issues

Thanks for reporting @nzakas , the issue has been fixed. Please try again via npm init wdio@latest ..

authors: christian-bromann nzakas

repo: webdriverio/create-wdio


text:
2 - ref family

<template>

      -
      {{ count }}
      +

</template>

第二题

repo: webfansplz/vuejs-challenges


text:
Allow deprecation of input values (arguments and input fields)

I haven't find anything about it in gql specs. Am I missing something?
private static function printInputObject(InputObjectType $type)
    {
        $fields = array_values($type->getFields());
        return self::printDescription($type) .
            "input {$type->name} {\n" .
                implode("\n", array_map(function($f, $i) {
                    return self::printDescription($f, '  ', !$i) . '  ' . self::printInputValue($f);
                }, $fields, array_keys($fields))) . "\n" .
            "}";
    }

doesn't print deprecation reason vs
private static function printObject(ObjectType $type)
    {
        $interfaces = $type->getInterfaces();
        $implementedInterfaces = !empty($interfaces) ?
            ' implements ' . implode(', ', array_map(function($i) {
                return $i->name;
            }, $interfaces)) : '';
        return self::printDescription($type) .
            "type {$type->name}$implementedInterfaces {\n" .
                self::printFields($type) . "\n" .
            "}";
    }

private static function printFields($type)
    {
        $fields = array_values($type->getFields());
        return implode("\n", array_map(function($f, $i) {
                return self::printDescription($f, '  ', !$i) . '  ' .
                    $f->name . self::printArgs($f->args, '  ') . ': ' .
                    (string) $f->getType() . self::printDeprecated($f);
            }, $fields, array_keys($fields)));
    }

Thanks!

While it makes sense for me, but deprecation is not described for input object types in GraphQL specs (or reference implementation). So I guess this question should be first raised in spec repo.
I'll close it for now, but will track specs / reference implementation updates in this regard.

There a PR that was created 9 days ago to handle deprecation of input fields.
Once it will be merged we can make the changes to this repo!
https://github.com/facebook/graphql/issues/197

@vladar I think this should be reopened now: https://github.com/graphql/graphql-spec/pull/525

@vladar I think this should be reopened now: https://github.com/graphql/graphql-spec/pull/525

This should be a great first PR, a relatively straightforward port of https://github.com/graphql/graphql-js/pull/2733. Any takers?

This should be a great first PR, a relatively straightforward port of https://github.com/graphql/graphql-js/pull/2733. Any takers?

Hello, @spawnia
I've created a PR to resolve this issue: #1382

Thank you @TaProhm, released with https://github.com/webonyx/graphql-php/releases/tag/v15.4.0.

authors: TaProhm bginsburg enumag simPod spawnia vladar

repo: webonyx/graphql-php

license: mit


text:
Fix examples/03-standard-server - Notice: Trying to access array offset on value of type null

Removed $rootValue['prefix'] variable from field "echo" resolve function because $rootValue is always null.
"text": "
\nNotice:  Trying to access array offset on value of type null in .../examples/03-standard-server/graphql.php on line 30
\n{\"data\":{\"echo\":\"Hello world\"}}"

To reproduce this notice message run:
curl -d '{"query": "query { echo(message: \"Hello World\") }" }' -H "Content-Type: application/json" http://localhost:8080

I will include the $rootValue in this example.

authors: spawnia urbanc


text:
Add linebreak before postfix

Fix #5

You probably should not check in the npm-debug.log file.

@Andersos, you are right, thanks.

I think you also only want to change the stuff in the index.jsfile and not the changes to the README.md and the package.json file.

Yes, you are right, but I needed the changes, particularly npm package right away. I could not wait till the pull request will be accepted. I can revert index.js and README.md back. Do you have rights to merge this pull request?

Unfortunately I do not. I was looking at this repo and thought I could give some feedback. Looks like the Webpack team is too busy with other stuff.

Merged the other PR.

The other PR is https://github.com/webpack/imports-loader/pull/15

authors: Andersos malykhinvi sokra

repo: webpack/imports-loader


text:
Fix issue: Sub-Navigation disappears when sub-menu entry "Migrate" is clicked

"migrate" added to:
 isActive: url => /^\/(api|concepts|configuration|guides|loaders|migrate|plugins)/.test(url),

Uhmm, not sure why it was never added. Maybe an oversight or by decision?

It doesn't happen in the website, right?

No, this issue is only related to branch rebuild. By decision wouldn't make much sense to me :-), I guess it's a mistake.

The only issue with "Migrate" page is that it has not enough content initially in order to have a scrollbar.
So when you click through the sub-navigation, you will see that the whole page moves left<-->right, when entering/leaving Migrate entry.

Yes, it is normal because of the scrollbar.

Thanks!

authors: Legends montogeek


text:
meta: minor grammatical fix

Minor grammatical fix.

Thanks!


text:
Webpack HMR almost works - but I am using webpack not webpack-dev-server

I am using webpack --hot --watch not webpack-dev-server --hot
I am having this issue:
https://stackoverflow.com/questions/60356923/hot-module-replacement-hmr-is-not-working-in-react-app
it looks like this:
ReactDOM.render(
  <Root store={store} onEnterRedir={onEnterRedir}/>,
  document.getElementById('app')
);

if (module.hot) {
  console.log('the module IS hot');   // works - this gets logged
  module.hot.accept('./root.jsx', () => {
    console.log('the module was reloaded.'); // doesn't work - doesn't get logged
    const NextRootContainer = require('./root.jsx').default;
    ReactDOM.render(<NextRootContainer onEnterRedir={onEnterRedir} store={store}/>, document.getElementById('app'));
  })
}

I think I know what the problem is - the problem is likely that webpack as opposed to webpack-dev-server doesn't have a websocket server that can notify the browser when a module has changed.
Is that most likely the problem? Is there any way to replicate the websocket server of webpack-dev-server with webpack?
I was thinking something like this:
webpack --watch --hot |  notify_client

so I could notify the client manually when there are changes?  but that makes me wonder - what is the --hot flag for then? It seems to enable module.hot on the front-end, but doesn't provide a server to ping the client when files change?

--hot enables the API when using only webpack.
The dev server uses the API to trigger the process, but you also use the API to trigger hot update.
See webpack/hot/... for possible implementations. E.g. add webpack/hot/poll?1000 to your entry point for a polling implementation that doesn't need a websocket

Answer above

authors: ORESoftware evilebottnawi sokra

repo: webpack/webpack


text:
Avoid requireing modules

Imagine this code:
if(... is NOT webpack? ...)
    var mod1 = require(...)
    var mod2 = require(...)
else
    var mod1 = undefined;
    var mod2 = undefined;

My goal is to only include modules when I am not in the browser. How can I do so?

IgnorePlugin?

#derp thats the one i needed.

authors: IngwiePhoenix SimenB


text:
Allow require.context() passing a fixed chunk name

Feature request

What is the expected behavior?
Support a syntax like require.context('./modules', true, /\.js$/, 'lazy', 'myModule') to allow specifying a fixed chunkName.
What is motivation or use case for adding/changing the behavior?
I want to split some code and pack them into a single file about operating dialogs from a enormous module.

require.context() doesn't support specifying a fixed chunkName.
require.ensure() and import() don't support passing expressions as module names.

How should this be implemented in your opinion?
I try to turn webpack\lib\dependencies\RequireContextDependencyParserPlugin.js into a new async-import-plugin. It supports the fifth param which can pass a fixed chunkName. The following is a replaying step.

Clone the repo async-import-plugin, run npm i.
Modify some code about managing chunkName in webpack\lib\ContextModule.js.

Run npm run build, then require.asyncImport('./modules', true, /\.js$/, 'lazy', '$myModule$') in index.js can achieve the target.

Are you willing to work on this yourself?
yes

For maintainers only:

[ ]  webpack-4
[ ]  webpack-5
[ ]  bug
[ ]  critical-bug
[ ]  enhancement
[ ]  documentation
[ ]  performance
[ ]  dependencies
[ ]  question

For maintainers only:

[ ]  webpack-4
[ ]  webpack-5
[ ]  bug
[ ]  critical-bug
[ ]  enhancement
[ ]  documentation
[ ]  performance
[ ]  dependencies
[ ]  question

For maintainers only:

[ ]  webpack-4
[x]  webpack-5
[ ]  bug
[ ]  critical-bug
[x]  enhancement
[ ]  documentation
[ ]  performance
[ ]  dependencies
[ ]  question

Duplicate https://github.com/webpack/webpack/issues/9184


text:
TypeError: Cannot read property '.js' of undefined

Webpack version:
1.13.1
Environment:
OSX 10.11.6
Language:
ES6/7
Current behavior:
Error thrown here: oldHandlers[ext] = (void 0)[ext]; in hookExtensions()
After building, when run I get the same error as explained here:
http://stackoverflow.com/questions/37275183/webpack-bundle-throwing-uncaught-type-error
Webpack Configs

/webpack.config.babel.js (main file)
/webpack (all config files)

The issue occurs when disabling externals: nodeModules() from webpack/config.server.js
and removing the webpack-hot-middleware with all related stuff from the project (which prevent webpack.config.babel.js to be reloaded a second time here)

You are not allowed to use require.extensions in code compiled with webpack.

AFAIK, require.extensions itself is at risk of being removed from node.

authors: Kovensky foxhound87 sokra


text:
CommonsChunkPlugin will not fetch all node_modules

Hey there,
I am on webpack v.2.6.1. I have the problem, that webpack will simply not extract all node_modules as configured but rather put them in the entry point.
I have a function creating common chunks:
function createStaticCommonsChunk(name, includes) {
	return new webpack.optimize.CommonsChunkPlugin({
		async: name,
		children: true,
		minChunks(module) {
			var context = module.context;

			return context && includes.some(str => context.includes(str));
		},
	})
}

My entry point is called react-index.js.
Now, my plugins-config looks like this:
createStaticCommonsChunk('shared.static', [
	'node_modules',
	'vendor'
]),

createStaticCommonsChunk('backbone.static', [
	'node_modules/d3',
	'node_modules/photoswipe',
	'node_modules/bootstrap-slider',
	'node_modules/bootstrap-sass',
	'node_modules/dropzone',
	'node_modules/clndr',
	'node_modules/backbone',
	'node_modules/webcamjs',
	'node_modules/BaremetricsCalendar',
	'node_modules/clipboard',
	'node_modules/big-integer',
	'vendor',

	'node_modules/react',
	'node_modules/redux',
	'node_modules/lodash',
	'node_modules/velocity',
	'node_modules/axios',
	'node_modules/history'
]),

createStaticCommonsChunk('react.static', [
	'node_modules/react',
	'node_modules/redux',
	'node_modules/lodash',
	'node_modules/velocity',
	'node_modules/axios',
	'node_modules/history'
])

Analysis:

Shouldn't all the modules from node_modules not catched by backbone.static and react.static be in the shared.static-chunk? Also, why arent all the backbone-modules in the backbone.static chunk?
If you need more information about the webpack.config.js, I put it up here: https://jsbin.com/nukulaxuqo/edit?js

It looks like you just deleted our lovely crafted issue template. It was there for good reasons. Please help us solving your issue by answering the questions asked in this template. I'm closing this. Please open a new issue with filled issue template. Also make sure your issue is not a question. Questions should be posted on Stack Overflow.

authors: misantronic sokra


text:
fix(lazy-compilation): support lazy compilation in ios9

bugfix: ios9 typeof EventSource === 'object'

Closing due to inactivity. I think we don't want to support ios9, it is very old, anyway feel free to feedback


text:
refactor requireresolveheader dependency to es6

What kind of change does this PR introduce?
refactor
Did you add tests for your changes?
current tests should pass
If relevant, link to documentation update:
N/A
Summary
upgrade RequireResolveHeaderDependency and RequireResolveHeaderDependencyTemplate to es6
Does this PR introduce a breaking change?
No

Thank you!

authors: TheLarkInn timse


text:
remove deprecated stuff

What kind of change does this PR introduce?
deprecation

Did you add tests for your changes?
no

If relevant, link to documentation update:
N/A

Summary
remove deprecated stuff
disallow module.loaders

Does this PR introduce a breaking change?
yes

Other information

https://webpack.js.org/api/loaders/#deprecated-context-properties
Unused

this.value
this.inputValue
this._compiler
 this.resolveSync

Used

this.options: file-loader, worker-loader, ... (Maybe undeprecate ?)
this.minimze: sass-loader, css-loader, html-loader`, ...
this._compilation: extract-text-webpack-plugin
this._module:  file-loader
this.exec: postcss-loader  (Would be good to undeprecate :))
this.debug: script-loader

this._compilation: worker-loader

this._compilation.options.output.publicPath: nested-require-loader

authors: FrogTheFrog TrySound michael-ciniawsky sokra


text:
Can't access to web page

I cannot access webpod.dev because chrome says certificate is invalid.

maybe dns propagation is not completed in Korea?

I still in development of the website) will update next week

This is also more problematic due to the lack of any description in the README. What is this? 😅

Fixed. First version of website is available.

authors: ELLIOTTCABLE antonmedv sh-cho

repo: webpod/webpod


text:
Access-Control-Allow-Origin Problem in Fetching TurnServer

I have copied the apprtc code to host it on my own GAE server (Python). I see the following error on the Javascript console. How do I fix this?
XMLHttpRequest cannot load https://computeengineondemand.appspot.com/turn?username=781166553&key=4080218913. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://.appspot.com' is therefore not allowed access.
I have tried the following in my response handler:
self.response.headers ['Access-Control-Allow-Origin'] = "*"
But I still have a problem. Any suggestion?

You must artr your own TURN server like coturn.
You must not use google server bandwitch so request is blocked from other domains.

Thanks for the response. Is there a list of components that one has to service on their own to support apprtc on their own server? For example,

TURN Server (Could use coturn, does google app engine support it?)
?

Appreciate your help!

You need:

Host the AppRTC web app on a Google App Engine instance
Host a signalling solution, e.g. Collider a websocket based signal server running on Google Compute Engine.
Host a turn server like Coturn or rfc5766-turn-server. E.g. Coturn has instructions on how to install it here, then just find a hosting solution that can host an environment that it supports.

As workaround, in Chrome,  you can use this extension: https://chrome.google.com/webstore/detail/cors-toggle/omcncfnpmcabckcddookmnajignpffnh?hl=en

authors: GaetanoCarlucci KaptenJansson aktywnitu santhosh-kumar

repo: webrtc/apprtc


text:
🛑 Jeff with Susan is down

In eb752e9, Jeff with Susan (https://www.jeffwithsusan.com) was down:

HTTP code: 521
Response time: 106 ms

Resolved: Jeff with Susan is back up in c30ee13 after 8 minutes.

repo: webworldview/uptime


text:
Mini Program's message type became to message_type_unspecified

When you send a message is a mini program, the meesage type is message_type_unspecified, this shoud be a bug.
wechaty                            0.6.13
wechaty-puppet                     0.2.0
wechaty-puppet-hostie              0.4.1

Yes, after check the payload from rocky protocol, there are thumbSize and thumbMd5 field added which will cause an error.  So, we should add an soft init function to make it running well on other protocol. Pr is welcome.

repo: wechaty/python-wechaty


text:
部署和token

请问如何部署和生成自己的token

It's very easy to publish a token by yourself, you need run Wechaty docket image by following https://github.com/wechaty/wechaty/issues/1986
And also you can provide token service for the community which is a great favor for us, learn more from https://github.com/wechaty/puppet-service-providers/issues/1

repo: wechaty/wechaty-puppet-hostie


text:
HF integration

Hi,
Niels here from the open-source team at Hugging Face. Congrats on your work! I discovered your work through the paper page: https://huggingface.co/papers/2408.09085 (feel free to claim the paper so that it appears at your HF account!).
Would you be up for making the checkpoints available on 🤗 , tagging them with "pipeline_tag: mask-generation" in the model card so that people find them when searching https://huggingface.co/models?pipeline_tag=mask-generation&sort=trending? Refer to https://huggingface.co/docs/hub/models-uploading for details.
Do note that with a single line of code, a checkpoint can be downloaded from the hub, using the hf_hub_download method. In case you have a custom PyTorch model for which you want to add from_pretrained and push_to_hub capabilities, we recommend leveraging PyTorchModelHubMixin.
Happy to assist!
Cheers,
Niels
ML Engineer @ HF 🤗

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Hi @NielsRogge ,
Thank you for reaching out and for your interest in our work! We are currently preparing and will release the code and checkpoints in a few days. We will then update the model card and checkpoints on Hugging Face. We will update you on our progress.
Best regards,

Hi @NielsRogge ,
We have updated the model cards and a collection involving all our models at here . Thank you.
Best regards,

That's really great, thanks for doing that!
Would it also be possible to add a link to https://hf.co/papers/2408.09085 within the respective model cards? This way, all models will be visible from https://huggingface.co/papers/2408.09085.
Similarly, you can add a paper into a collection as well if you want :)
Cheers!

Hi @NielsRogge ,
Sorry for the late reply. I have added the paper to the collection and to the model cards. Thank you for your reminder and helpful guidance!
Best regards,


text:
When will the training code be released?

Excellent work. When will the training code be released?

Hi @XiaozhenQiao ,
Thank you for your interest in our work! We plan to release the training code upon acceptance. After acceptance, we will release the MM-SAM's training and testing code based on SAM1 and SAM2.
Best regards,

Looking forward to your code，I wish your article will be received soon.
Best wishes!


text:
Uncaught (in promise) TypeError: Cannot use 'in' operator to search for 'body' in undefined

Getting a type error below. Anything I am missing:
Uncaught (in promise) TypeError: Cannot use 'in' operator to search for 'body' in undefined
    at t.DocumentStore.getFieldLength (elasticlunr.js:10)

mdArr = [{url: '/body', body: 'array of string test'}, {url: '/note', body: 'array of string'}, {url: 'tester', body: 'array of string test test test test'}]
searchString = 'test'

function searchDocs(mdArr, searchString) {
  let result, docIndex = elasticlunr(function () {
    this.addField('url');
    this.addField('body');
  });
  for (var i = 0; i < mdArr.length; i++) {
      docIndex.addDoc(mdArr[i]);
  }
  // All the three docs added

  // Erring out at the following line
  result = docIndex.search(searchString);

  return result;
}

I realise this is an old issue, but I found that I needed a reference field to be defined and in every document. Unfortunately I've been trying to figure out if I can setup the system to auto-ID my documents as I insert them but with no success so far, so you need to add a reference field manually.

Ok sure.

This is the error that happens if your documents don't have an 'id' field. Couldn't find a reference to this being required in the docs.

authors: adamrabung ganeshkbhat valandir


text:
Allow all filters to stay in form but hidden if filters wrapper too long

I'd invite anyone reviewing this to run it locally and test it, I've done my own tests, but this was a peculiar one and could use extra checks on a different screen as that's how we found out about it in the first place.
Who is this for?
All search users
What is it doing for them?
Any filter that is preselected (in the URL query) but not displayed on desktop (because of a smaller screen), won't get submitted on the next form submit when filtering further.

On the widest screen, filter with a language on https://wellcomecollection.org/search/works
Resize your screen so some filters still display but the Language ones disappears
Select a Location
See the language disappear from your search.
This happens only on desktop because of the behaviour of filters only displaying a limited amount based on screen size. The modal box has no issue and neither do the mobile filters.

I've changed the logic to only hide the filters visually when they don't fit instead of not rendering them at all, which allowed us to simplify the code a little bit.
I've also tweaked the styles a little bit as there was a double margin before the "All Filters" button. This might have been on purpose to differentiate it from the others, if so do let me know and I'll bring it back (@AMBacelar , @jtweed, @DominiqueMarshall)!
(Before)

(After)

Closes #9631

I've tested it locally and it seems okay to me, looking at the code now.

authors: alexwlchan rcantin-w


text:
Remove the SQL store from the id_minter

In order that we have predictable, sensible, scalable infrastructure the id_minter should no longer use a SQL database.
There have been issues with the id_minter running out of db connections in the past - RDS is an unnecessary fixed cost and is a scaling bottleneck. It is also an unusual and unexpected architectural choice in the context of the the rest of the pipeline architecture.
This PR will provide parallel storage in DynamoDB (while continuing to retrieve and store in RDS) to ensure continuity of service, testing and a safe and easy rollback migration path in the event of DynamoDB turns out to be a bad choice.
Note:
This is a work in progress, and will require a migration from SQL to DynamoDB of existing identifiers (this PR allows decoupling of that process from deployment of code changes).

😱

Is this ready for detailed review yet, or just here for visibility?

@alexwlchan just here for discussion right now. We should have done this ages ago.

You are definitely right that there's no reason other than historical reasons to have mysql and that it could be switched to dynamo and we would achieve all of the things you say.
I'm not sure about how valuable those things are.
I don't think dynamodb would be that much less expensive, I think it would be in the same cost range.
As for mysql is a bottleneck, I think in practice that doesn't show. A reindex takes 4/5 hours because the transformer takes 4/5 hours , everything seems backed up right at the start of the pipeline. But most importantly, we don't really care, we don't need it to be faster, which is why we aren't speeding up the transformer.
It's true that it would make the service more consistent with the rest, but it's a service that we never change so I'm not sure whether that would make any future development easier.
It's true that it causes issues when scaling up the idminter and those are annoying, but I feel that is the only real tangible advantage we would get.
I'm not sure if that on its own is worth a big refactoring like this one, especially given that it needs to be taken into account how to migrate the data and how potentially to store the ids into two databases while we migrate.
I feel that migrating the idminter adds lots of room for bugs and lots of room for error in an otherwise very stable code.
TLDR: I don't think it's worth the time/effort/risk..

authors: alexwlchan alicefuzier kenoir

repo: wellcometrust/catalogue


text:
Notifier: fails to notify Archivematica, and doesn't have any logs about it

Probably because it can't send callbacks to our Archivematica instance.
See ingest ID d5ff7a8a-4d8b-48cd-80c5-d05ae1d2f8e5

Ah, I did find the logs, there's just no big traceback.

Archivematica is world-readable in wellcometrust/archivematica@03749d2, so the notifier can make callbacks. It seems to be getting a 401 in the callback response:
[WARN] [03/28/2019 14:53:26.750] [main-actor-system-akka.actor.default-dispatcher-1946] [main-actor-system/Pool(shared->https://archivematica-storage-service.wellcomecollection.org:443)] [0 (WaitingForResponseEntitySubscription)] Response entity was not subscribed after 1 second. Make sure to read the response entity body or call `discardBytes()` on it. POST /api/v2/file/0ba7cdd8-e0ce-4f90-a87e-c6aaa3821f0a/wellcome_callback/ Strict(986 bytes) -> 401 Unauthorized Chunked
No newer events found at the moment. Retry.

This works!

repo: wellcometrust/platform


text:
[WIP] First pass at a module for DynamoDB/S3-hybrid asset store

A first attempt at what this might look like.
Who is this change for?
🌵

Closing as superseded.

authors: alexwlchan kenoir


text:
first pass of basic inline links

Fixes/References #2617
Who is this for?
People wanting to see nice looking embedded lists in content
What is it doing for them?
Making the lists look beautiful.
This will help me move onto allowing event series etc to be embedded.

This is more to do with 'lists' than 'links', right?

Sure.

(it is - I think these might be promos, that's why they're simply done as the current promo really didn't work).


text:
Bouncy icon

What is this PR trying to achieve?
Fixes #624
What does it look like?

Wicked!!

if we should use this animation everywhere

Power vs responsibility... we need to start measuring performance before going headfirst into this.

authors: Norvard jamesgorrie


text:
Visit / read / research

#3363

As agreed, let's get this out in small steps, behind a toggle.
Notes on implementation from conversation with @gestchild
Could be less flexible, and not be a list, but a set of three, two property components.
e.g.
{
  onwardItems: {
    researchItem: {},
    readItem: {},
    visitItem: {}
  }
}

Stretches
Headings
I'm assuming we will start having some questions around control of the heading, from the experience we've had so far, allowing there to be a content controlled set of items might be better, and allows a content designer to come up with a consistent approach, so we might land up with:
{
  onwardItems: {
    researchHeading: {},
    researchItem: {},
    readHeading: {},
    readItem: {},
    visitHeading: {},
    visitItem: {}
  }
}

Attaching works
How do we go about this?


text:
menuType含义

hi，大佬，问一下 menuType: C、 M、 F、 A分别代表什么意思?

"M"：目录
"C"：菜单
"F"：按钮
"A"：接口

没有把这些标识写入字典吗？

authors: hatch1994 wangbokun wenjianzhang

repo: wenjianzhang/go-admin


text:
源码 缺 wkeScreenshot 等12个 函数的实现 请补全

源码里缺了一下几个函数的实现：
wkeShutdownForDebug

wkeIsWebviewValid

wkeClearCookie

wkeSetStringWithoutNullTermination

wkeCreateStringWithoutNullTermination

wkeGetStringLen

wkeScreenshot

wkeNetGetRawHttpHead

wkeNetGetRawResponseHead

wkePluginListBuilderAddPlugin

wkePluginListBuilderAddMediaTypeToLastPlugin

wkePluginListBuilderAddFileExtensionToLastMediaType

新功能不再提供源码了

@weolar
wkeClearCookie should be implemented anyway.

这个的实现很简单：
void WKE_CALL_TYPE wkePerformCookieCommand(wkeWebView webView, wkeCookieCommand command)
{
WKE_CHECK_WEBVIEW_AND_THREAD_IS_VALID(webView, (void)0);
CURL* curl = curl_easy_init();
if (!curl)
return;
std::string cookiesPath = webView->getCookieJarPath();
CURLSH* curlsh = webView->getCurlShareHandle();

curl_easy_setopt(curl, CURLOPT_SHARE, curlsh);
curl_easy_setopt(curl, CURLOPT_COOKIEJAR, cookiesPath.c_str());

switch (command) {
case wkeCookieCommandClearAllCookies: {
    curl_easy_setopt(curl, CURLOPT_COOKIELIST, "ALL");
    std::wstring cookiesPathW = base::UTF8ToWide(cookiesPath);
    ::DeleteFileW(cookiesPathW.c_str());
}
    break;
case wkeCookieCommandClearSessionCookies:
    curl_easy_setopt(curl, CURLOPT_COOKIELIST, "SESS");
    break;
case wkeCookieCommandFlushCookiesToFile:
    curl_easy_setopt(curl, CURLOPT_COOKIELIST, "FLUSH");
    break;
case wkeCookieCommandReloadCookiesFromFile:
    curl_easy_setopt(curl, CURLOPT_COOKIELIST, "RELOAD");
    break;
}
curl_easy_cleanup(curl);

}
void wkeClearCookie(wkeWebView webView)
{
wkePerformCookieCommand(webView, wkeCookieCommandClearAllCookies);
}

@weolar
感谢提供代码 学习了


text:
create lp and add settings

概要

Bootstrap を導入しています。
LP ページは暫定的なものです。

イメージ

official

custom

コンフリクト解消した結果
このような見た目になっています。

repo: weseek/growi


text:
Update sbt-dotenv to 2.1.194

Updates au.com.onegeek:sbt-dotenv from 2.1.146 to 2.1.194.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "au.com.onegeek", artifactId = "sbt-dotenv" } ]

labels: sbt-plugin-update, semver-patch

Codecov Report

Merging #140 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #140   +/-   ##
=======================================
  Coverage   12.96%   12.96%
=======================================
  Files          54       54
  Lines        2168     2168
  Branches       28       28
=======================================
  Hits          281      281
  Misses       1887     1887

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 74c1b5d...0f8158c. Read the comment docs.

authors: codecov-commenter scala-steward

repo: weso/rdfshape


text:
Update scalatest to 3.2.2

Updates org.scalatest:scalatest from 3.2.0 to 3.2.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalatest", artifactId = "scalatest" } ]

labels: test-library-update, semver-patch

Codecov Report

Merging #115 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #115   +/-   ##
=======================================
  Coverage   60.02%   60.02%
=======================================
  Files          98       98
  Lines        3892     3892
  Branches      141      141
=======================================
  Hits         2336     2336
  Misses       1556     1556

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 62e1565...61ad620. Read the comment docs.

repo: weso/shex-s


text:
Adds role of dialog to modal

Description
As pointed out by Knowbility and Axe, modals outside of body need to have a landmark for screenreaders to be able to navigate it correctly.
When researching this, it became apparent that even if a modal is in the body element it should have a `role="dialog", as it:
 helps assistive technology identify the dialog's content as being grouped and separated from the rest of the page content
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/dialog_role
Solution
Adds role="dialog" to modal.

Thanks @NicholasLancey , looks good.

authors: NicholasLancey andrewrubin

repo: wethegit/wtc-modal-view


text:
service name now gets added to log entries when a custom logger is set or in saga store

https://github.com/wework/grabbit/issues/200
#200

#206

Coverage increased (+0.1%) to 76.224% when pulling f994d7f5353e0dde7baa6bcaebcfbafe07256ce8 on fix-logging into 784d8f421e676bd7b9ad92cf7140f9243969d783 on v1.x.

authors: coveralls rhinof

repo: wework/grabbit


text:
🛑 Portal is down

In bb490e0, Portal (https://winterco.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Portal is back up in d9cd8e3.

repo: wfjsw/status-winterco-org


text:
task/setup options

Split out transformers, accelerate, and torch requirements into 'complete' extras. To install these dependencies, users will now need to:
pip install phasellm[complete]

Merged into new dev branch by https://github.com/wgryc/phasellm/pull/47

repo: wgryc/phasellm


text:
removed deprecated functions and updated the code to work with the la…

Upgraded to work with the latest version of ember, removed the deprecated api calls and removed unnecessary dependencies.

@waleedq Thank you for your contribution! You have done a great job - PR looks good. But addon's dummy app seems to be broken. In near future I'm going to figure out what's wrong with it and possibly fix it (I think not all npm devDependencies were updated.)

@ajile thank you for reviewing, please let me know how to test the dummy app so i can fix it, as i've deleted some dependencies maybe that caused it.

I've created PR to your fork (waleedq/ember-dialog#1). It fixes dummy application and resolves other deprecations after moving to the latest ember. If the PR is good for you, it can be accepted into your master (those commits will be appended to current PR).
Also I've reviewed your PR - it's great. Although I found few things that should be fixed before I can accept it to master and publish new version (It will be stable version - v3.0.0).

Dummy application is a part of ember addon (see tests/dummy/) that used for debugging and acceptance tests. It's some kind of ember application that already has ember-dialog on aboard. It can be run as a regular application - by command ember s (it appears on 127.0.0.2100).
The ember-dialog uses dummy application to public site - http://wheely.github.io/ember-dialog/. Unfortunately for a moment the most its pages are not translated to english (I planing to translate it sometime), although examples are independent of language and useful for debugging.

@ajile any idea when you can merge and tag new release?

@ivandokov, I planned to do it at the weekends. If I have some spare time I will do it tomorrow.

I've ran into the problem of using ember-dialog with the latest version of ember@v2.10.0. Seems the Ember.Component lost template property and now the dialogs show up without body.
While with previous version of ember@v2.9.1 it works fine. I tried to workaround the problem at the weekends, but did not get any results. If you guys know how to fix it feel free to contribute or leave your comments in the issue #87.
I'll try figure out how to fix it in near future. Until then I won't create new tag to prevent problems of using ember-dialog by projects on the latest version of ember. But I accept this PR into master.
If your project uses ember version between 2.3.2 and 2.9.1 it is able to use ember-dialog directly from the repo by commit hash (as temporary solution).

authors: ajile ivandokov waleedq

repo: wheely/ember-dialog


text:
Allow URL override from config file to use our HAProxy gateway to silverp

Allow URL override from config file to use our HAProxy gateway to silverpop.
Upped version.

Ignore this.  Missed a header needed for HAProxy.  New pull request to come.

repo: where/silverpopper


text:
Remove all hardcoded instances of system clock frequency

revC will run at 48 MHz sysclk (at least in the end, perhaps not initially) so this is a prerequisite for proper revC support.

Done.

repo: whitequark/Glasgow


text:
Fix binance zero fees

Description
Binance has introduce zero fees (maker and taker) for some pairs.
Refs: https://www.binance.com/en/support/announcement/binance-launches-zero-fee-bitcoin-trading-10435147c55d4a40b64fcbf43cb46329 && https://www.binance.com/en/blog/markets/zero-btc-trading-fees-they-do-what-they-say-on-the-tin-6168074889174657450
Fixes # (issue)
This change will check the market and returns 0 if the bot market is one of those.
I've also updated the simulation.
Please make your selection.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] This change requires a new dependency
[ ] Code Maintainability / comments
[ ] Code Refactoring / future-proofing

How Has This Been Tested?
I used the provided script-get_fees.py with different market to check that fees are 0.1% for all pairs and 0% for those.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added pytest unit tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

Hi,
thank you. Looks ok to me, but could you look into the unit tests and why they are failing?

Done. It sas some typos in readme and in a test file. Don't know how they've pass the codespell test before...

Thank you, the code LGTM. I didn't check if it makes sense though. The only issue I could see is the implicit type conversion from float to int when you're setting
takerfee = -1 which was 0.00 before.
So you may want to explicitly typecast it back to float, just for safety.
>>> type(-1)
<class 'int'>
>>> type(0.00)
<class 'float'>
>>> type(float(-1))
<class 'float'>
>>>

Hi @Nicolas469, thanks for the PR. This is a great update. We don't raise PR's directly into the "main" branch. It needs to be go into "beta" first. In addition to this for the last few weeks/months I've been working on a major update. It will replace the "beta" branch and become main. Can you please check out "dev/pycryptobot7", install the deps, and make your change there in a new PR. Please note that there has been a major code update so please confirm to the new "rules". I've explained here: https://trading-data-analysis.pro/pycryptobot-v7-is-almost-here-b68bdb87d33a

Thx @loomsen for the feedback, I've updated the type of "takerfee"3
@whittlem: I've changed to "beta" and I'll check the v7 later :)

Thanks, not "beta"... "dev/pycryptobot7". That is the new major release which will replace "beta". There is a huge code update so you may need to update your code to work on the new version.

Sorry I thought that while waiting for v7 to be live we could merge this update in v6.
But yes I'll check v7 and also make this change there.

authors: Nicolas469 loomsen whittlem

repo: whittlem/pycryptobot


text:
Unable to locate library. (While searching for a .vos file.)

Having same issue as #192 with the same source material.
"Unable to locate library Pset1Signature. (While searching for a .vos file.)"
Here is the output you asked about in the previous ticket:
2022-01-26 02:21:17,870: ('/snap/bin/coqidetop.opt', '-main-channel', 'stdfds', '-async-proofs', 'on', '-async-proofs-command-error-resilience', 'off', '-async-proofs-tactic-error-resilience', 'off', '-topfile', '/home/jon/projects/spring21/pset01_ProgramAnalysis/Pset1Implementation.v', '-R', '/home/jon/projects/spring21/frap/', 'Frap')
I was using 8.12.?? on WSL2 via normal apt install through Ubuntu. Removed it and installed the snap version to get 8.13.2. Both version threw the same error.

I'm going to close this. Its doing the same thing on multiple IDEs.

Sorry you're encountering this issue, but I'm not able to reproduce it on my end and the coqidetop arguments look correct. Are you sure Pset1Signature is compiled, can you see Pset1Signature.vos in the pset01_ProgramAnalysis directory?

Thank you for responding. This is a case of me not knowing what I'm doing. For this set of problems I assumed the instructions for running make to compile the book did so for all problem sets. But it doesn't.
If anyone finds this and has the same issue, you have to run make in each problem set directory.

authors: jvolden whonore

repo: whonore/Coqtail


text:
Tempfile of shuffled dataset should be better in /tmp dir of the host.

Currently, the temporary shuffled dataset is saved in the dir of original dataset (in /user_data/weihr/ for default), which leads to frequently writing the remote mounted dir /home/user_data. This will perhaps make the remote filesystem failed to mount, which happened today in 1080ti-1.

Maybe we should use os.getcwd() at this place. I'll submit a pr.


text:
Add docs for 48001 error

A new inspection was created.

The inspection completed: No new issues

Codecov Report

Merging #206 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #206   +/-   ##
========================================
  Coverage    84.53%   84.53%
========================================
  Files           28       28
  Lines         1106     1106
========================================
  Hits           935      935
  Misses         171      171

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 d6ee932...e0e4af9. Read the comment docs.

A new inspection was created.

The inspection completed: No new issues

authors: codecov-io scrutinizer-notifier whtsky

repo: whtsky/WeRoBot


text:
Linux下需要装哪些依赖呢

Linux下需要装哪些依赖呢，请教一下

我都是失败。。。。。不知道咋回事

repo: whyour/qinglong


text:
🛑 Girasol 🇬🇧 (en) is down

In d703641, Girasol 🇬🇧 (en) (https://holiday-lescala.com/en/h/house-girasol/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Girasol 🇬🇧 (en) is back up in 753a364 after 3 minutes.

repo: whytspace/upptime-holiday-lescala


text:
🛑 Bianya 🇬🇧 (en) is down

In 82bc851, Bianya 🇬🇧 (en) (https://holiday-lescala.com/en/h/house-bianya/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Bianya 🇬🇧 (en) is back up in 282f472 after 29 minutes.


text:
podre

podre

ih garota se manca

faz melhor

authors: JulieClaro wiccanoscarlate

repo: wiccanoscarlate/Portifolio


text:
Using Numpad keys to switch between desktops

Hi,
I'm found this software pretty good for my usage and I appreciated, but one thing I couldn't figure out that how to do that is how to use Alt + Numpad keys to switch between desktops? Is there a way to do that?
And another thing I should mention that the color of the desktop number shown in taskbar is white that is not proper for light themes, is there a way to change the color of the desktop number?
Thank you
Kind regards
Jaziny

@Jaziny Thanks for letting me know about light theme not working! Apparently Microsoft changed the name of the setting in the registry in a recent update and I hadn't noticed it.
Download this new version here. Let me know if it works and I can close this issue.
Yes, numpad is supported, you can use any keys specified here in the config file.
To change this, right click WinJump in the systray and select Open config file:

In your config file, replace d0, d1, d2, etc. with NumPad0, NumPad1, etc. so that you config file looks like this:
{
  "toggle-groups": [],
  "jump-current-goes-to-last": false,
  "change-desktops-with-scroll": true,
  "move-window-to-desktop": {
      "shortcut": "alt+shift"
  },
  "jump-to": [
    {
      "Shortcut": "win+NumPad0",
      "desktop": 10
    },
    {
      "Shortcut": "win+NumPad1",
      "desktop": 1
    },
    {
      "Shortcut": "win+NumPad2",
      "desktop": 2
    },
    {
      "Shortcut": "win+NumPad3",
      "desktop": 3
    },
    {
      "Shortcut": "win+NumPad4",
      "desktop": 4
    },
    {
      "Shortcut": "win+NumPad5",
      "desktop": 5
    },
    {
      "Shortcut": "win+NumPad6",
      "desktop": 6
    },
    {
      "Shortcut": "win+NumPad7",
      "desktop": 7
    },
    {
      "Shortcut": "win+NumPad8",
      "desktop": 8
    },
    {
      "Shortcut": "win+NumPad9",
      "desktop": 9
    }
  ]
}

Note that you will need to have scroll lock on for it to work, otherwise you'll have to create additional mappings for the keys when num lock is off (let me know if you'd like me to show you how to do this).

Thank you for your fast respond, I downloaded new version and the problem solved, also now I can use numpad keys for changing desktops and it is enjoyable, very appreciated.

@Jaziny Great to hear! Enjoy!

authors: Jaziny widavies

repo: widavies/WinJump

license: Unlicense


text:
Refactor server

[x] HostConnection class
[x] Debugger class
[x] Error codes instead of calling quit_debugger()
[x] Communication between debugger and target process via messages
[ ] Remove server CLI

In addition to the Debugger class I also introduced a Target class. I'm leaving the CLI there for the moment.

repo: wiemerc/CWDebug