Remove 'new-task' GitHub template

Too many options here was a bit overwhelming for me. I
am not sure what a specific 'Task' label gives us over
just blank issues.

@choldgraf I'm trying to go through and look at processes where I'm overwhelmed with the amount of choices, and trying to change to fit.
I'm also not sure if 'Goal' is helpful anymore, so we should consider removing that too.

I like the idea of having a template that nudges me to describe the problem and think about a possible pathway forward, but I do also find the number of choices overwhelming. I almost always choose "New Task" though because it feels low down on the list of importance and, therefore, less disruptive if I generate a few over the course of a single working day (I view "Tasks" like "To-Dos"). The exception to my thinking here is the "New Hub" template, which is pretty well scoped I feel.

@sgibson91 ya I find the new hub and incident report templates helpful. I use 'blank issue' similar to how you use task. May I suggest we remove everything except new hub and incident report?

I'd quite like some kind of template for these general things just to avoid blank issue bodies and provide that scoping nudge. What do you think of the Turing Way's "General" issue template? https://github.com/alan-turing-institute/the-turing-way/blob/master/.github/ISSUE_TEMPLATE/ISSUE_TEMPLATE.md

@sgibson91 I like that template! I agree that templates are helpful - I mostly just want to reduce the number of them!

I mostly just want to reduce the number of them!

Totally agree with you there!

So, you/we are proposing to have 3 types of issues: New Hub, Incident report, and New Issue (with some templating), and then we use labels for enhancement, task, discussion, etc?

Well, actually looking at https://github.com/2i2c-org/pilot-hubs/issues/595, do we need one for Debriefs?

What if we took the following approach:

Remove the task github issue template
Encourage a team practice of:

If the new issue is sufficiently complex, encode it as an enhancement/deliverable by using the enhancement issue template. This way we can track the issue as part of our development workflow.
If the new issue is not complex, try to find a "tracking deliverable issue" and add it as a task. This way we can track it as part of broader priorities and deliverables to work towards.

Here I think we will have to strike a balance between "having millions of issues" and "having issues that are extremely large and overly-scoped". But in my experience oftentimes small-ish tasks can often be categorized as part of broader efforts, so we should track them as-such rather than creating different issues for them.
This is also related to https://github.com/2i2c-org/team-compass/pull/188

Encourage a team practice of

That the difficult piece :wink:
I like the proposal but I think it would be difficult to play it for real. People usually open issues quickly as a response to something they find, they think, etc. The additional step of looking into other big "home" issues will most likely discourage people to open issues at all (because they will miss time or they think they will do it later and forget) or encourage people to avoid that step that will result in a no practice at all. In that scenario, I would prefer people to open issues as easily as possible and then set up aside some specific time to curate those issues.

@damianavila though in those cases, they could always open up a blank issue, no? I agree that we don't want to discourage the creation of issues in general, though we definitely do want to encourage greater signal to noise.
This could also be something that more time spent in refinement etc could help with. Perhaps any new issue should include a needs-triage label that could be used as a signal that somebody should make sure it's got the proper structure etc?

@damianavila though in those cases, they could always open up a blank issue, no?

Those are back holes 😉  .

though we definitely do want to encourage greater signal to noise.

I totally agree with that.

This could also be something that more time spent in refinement etc could help with

Yes... what I am saying above is trying to do the refinement after the issue is created and not ask for that at the time to create the issue (I see looking for a parent issue as a sort of refinement).

Perhaps any new issue should include a needs-triage label that could be used as a signal that somebody should make sure it's got the proper structure etc?

I would assume every new issue needs-triage (without the need of a label) until we know it is ready to live standalone (and maybe that is the time to assign a label) or as a task in a parent issue.

So, how should we relate that to this PR? I agree with you that blank issues are basically black holes, though the template that this PR is removing is just this markdown:
# Summary

<!-- What is the context needed to understand this task -->

a label

so it feels like that is not a lot of structure anyway, and I'm not sure that we gain much by having a template for this. Does that make sense?

I'm on the same page with @damianavila. Extra decisions to be made at issue creation time add impedence to issue creation, especially since often issues are created in a batch.
We can add a 'needs-triage' label by default to all blank issues?

so it feels like that is not a lot of structure anyway, and I'm not sure that we gain much by having a template for this

I'm actually amazed that this template isn't something like
# Summary

<!-- Description... -->

# Actions to be taken

- [ ]
- [ ]

That's the kind of structure I'd want.

How about we combine a few of the ideas above into the following structure:
Templates we use

New Hub
Incident Report
General Issue

We keep New Hub and Incident Report the same as they are now. We combine our current templates for New Goal, New Task, and Enhancement (AKA deliverable) into the following General Issue template (inspired from the Turing Way):
<!--
Please complete the following sections when you open an issue. You are encouraged to keep this top level comment box updated as we learn more about the issue. If you have write access to the repository please also assign the appropriate label (or labels) to your issue.
-->
### Summary

<!-- Please provide a detailed description of the change or addition you are proposing, or the question you're asking. Please provide as much context as possible and link to related issues and/or pull requests. If this issue is related to a bug, include information about how to reproduce it.
-->

*Lorem ipsum dolor sit amet, consectetur adipiscing.*

### Tasks to complete

<!-- We suggest using bullets (indicated by * or -) and filled checkboxes [x] here -->

- [ ] *Lorem ipsum dolor sit amet, consectetur adipiscing.*
- [ ] *Lorem ipsum dolor sit amet, consectetur adipiscing.*

---

### Updates

<!-- To avoid that others have to read through the full thread of comments, please update the initial issue with important updates (e.g. decisions taken) regularly. You can update the task list and summary above directly (this is encouraged!) or add new information below in this new section.
-->

*Lorem ipsum dolor sit amet, consectetur adipiscing.*

Hey all - I didn't want to lose track of this PR, so I've opened up a new PR to supercede this one. What do folks think? https://github.com/2i2c-org/pilot-hubs/pull/619

Thanks for opening #619, @choldgraf! I'll close this in favor of that.


The same code which is fine on Android 6.0.1, but an error("The model is not a valid Flatbuffer file") is reported on Android 8.0.0

OS Platform and Distribution
Win 10
Android Studio 3.0.1
sdk version 26
TensorFlow installed from
N/A
TensorFlow version
N/A
Bazel version
N/A
CUDA/cuDNN version
N/A
GPU model and memory
N/A
Exact command to reproduce
N/A
Mobile devic
Huawei Honor 8 & Gome K1
Describe the problem
I am using the TFLite demo for Android. Since there are two ways to initialize an Interpreter with a model file:
The Interpreter can be initialized with a model file using the constructor:
public Interpreter(@NotNull File modelFile);
or with a MappedByteBuffer:
public Interpreter(@NotNull MappedByteBuffer mappedByteBuffer);
The official TFLite demo uses the second way(MappedByteBuffer) to initialize an Interpreter. I change it to the first way(using File) and The modified code is as follows(the constructor of ImageClassifier):
//tflite = new Interpreter(loadModelFile(activity));  //official code. The second way to initialize.
File modelFile = new File("/storage/emulated/0/DCIM/" + getModelPath());   //the first way
tflite = new Interpreter(modelFile);            //the first way

When I run it on Gome K1 mobile phone(Android 6.0.1), it works fine. However, when I run it on Huawei Honor 8(Android 8.0.0), an error occurred:
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.example.tflite_pure/com.example.tflite_pure.MainActivity}: java.lang.IllegalArgumentException: Contents of /storage/emulated/0/DCIM/mobilenet_v1_1.0_224.tflite does not encode a valid TensorFlowLite model: Could not open '/storage/emulated/0/DCIM/mobilenet_v1_1.0_224.tflite'.The model is not a valid Flatbuffer file
I am not sure if this problem is caused by different versions of Android(6.0.1 vs 8.0.0). So any help would grateful. Thanks.

Thanks, The problem description has been updated according to the issue template.

Nagging Assignee @aselle: It has been 15 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @aselle: It has been 30 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Did you verify that the file is on the same path on both phones ?

This is likely an issue with storage access and permission changes. I would recommend using the MappedByteBuffer path on Android.


Add missing space in example

:smile:

A pull request for one simple space in an example file? Really? The github is collecting more and more.

@johannesbottcher I honestly appreciate your opinion about this

Thanks, but I don't want this modification! Sorry!


error: ‘imag_out’ is not a member of ‘at’

I have this problem when installing the current on master
/home/adnguyen/Downloads/nestedtensor/nestedtensor/csrc/unary.cpp:86:27: error: ‘imag_out’ is not a member of ‘at’
   add_unary(m, c, "imag", at::imag_out);
                           ^~
/home/adnguyen/Downloads/nestedtensor/nestedtensor/csrc/unary.cpp:96:27: error: ‘real_out’ is not a member of ‘at’
   add_unary(m, c, "real", at::real_out);
                           ^~
error: command 'gcc' failed with exit status 1

My environment:
python: 3.7.7.
pytorch: latest nightly version.

Thank you! Will merge the fix asap.


Update Cadence Upgrade Banner

Add a link to the migration hub and/or migration guide in the various upgrade banners.
Change various banners:

[ ] developer docs
[ ] cadence-lang
[ ] contract browser
[ ] flow cli
[ ] playground

blocked: need guidance from @Aliserag on wording.

Lets send people to the new Migration hub, planning to get that published this week.


Processing is not blocked until redirected to an external URL

Environment

Operating System: Linux
Node Version:     v18.18.0
Nuxt Version:     2.17.3
CLI Version:      3.11.1
Nitro Version:    2.9.6
Package Manager<EMAIL_ADDRESS>Builder:          webpack
User Config:      ssr, bridge, serverHandlers, devServerHandlers, devServer, typescript, nitro, buildModules
Runtime Modules:  -
Build Modules<EMAIL_ADDRESS>

Reproduction
https://stackblitz.com/edit/github-cpfme2
Describe the bug
Processing is not blocked until redirected to an external URL.
Expected logs
redirected

Actual logs
redirected
should not call

Additional context
No response
Logs
No response

Resolved at https://github.com/nuxt/bridge/pull/1197
https://stackblitz.com/edit/github-cpfme2-8k2ziq
If you want to use it early, please use<EMAIL_ADDRESS>


Not able to crawl Javascript-disabled webpages

Hello guys, I am using newspaper3k to crawl text from webpages.
I noticed that the article.parse() function is not able to read the content of webpages which have Javascript disabled.
Following is the code that I am using:
`
url = "https://seekingalpha.com/article/4439299-russell-2000-leading-wall-street-lower-sell-iwm"
article = Article(url)
article.download()
article.parse()
print(article.text)
`
I am getting the following error:
`Javascript is Disabled
Your current browser configuration
is not compatible with this site.`
Does anyone know how to overcome this?

seekingalpha.com requires a login, so you need to pass that information to the website to harvest the article text.  I haven't tried to use newspaper3k for this, but it should work because the package uses Python Requests.


Add Total Downloads

Adds the total number of asset downloads to the page bottom.

btw: :+1: for this project!

Thanks for the patch @PhrozenByte


Installing custom resources before a helm upgrade

Thanks for these charts. I always found the flux bootstrap a bit of magical complex install process and the terraform flux provider unable to handle upgrades.
Is your feature request related to a problem ?
Currently helm3 when doing an upgrade doesn't upgrade custom resources which can lead to deployment failures because custom resources are not upgraded.
Describe the solution you'd like.
I suggest creating in the repo a crds directory and a crds_0.24.0.yaml file with the crds definitions for each chart release.
then it will be possible to just download the file and then do a
helm apply -f  crds_0.24.0.yaml
before doing the helm upgrade
if you think thats a good idea then i can create a PR.
Describe alternatives you've considered.
alternatively you need to download the chart and extract the crds into file(s) and apply them not a big deal i guess but easy to forget.
We could just add docs in the readme of that process to remind folks instead of providing the crds file/
Additional context.
No response

Currently helm3 when doing an upgrade doesn't upgrade custom resources

Have you verified that this applies to the flux2 chart?

Alternatively you could do the followiing:
helm3 apply -f https://github.com/fluxcd-community/helm-charts/blob/flux2-0.6.1/charts/flux2/templates/crd-controller-clusterrole.yaml
flux2-0.6.1 is the tag of the release. So you can download and apply the crds of the corresponding chart release. We could document this process in the readme.

@dwerder how would applying some RBAC help with CRDs upgade?
I don't think what's reported here is true. The flux2 chart doesn't uses the crds dir, so Helm should upgrade all CRDs since they are in templates.

@stefanprodan it was just an example, that it is already possible to apply specific crds file for each release. I just took the first file named crd as example.

I don't think what's reported here is true. The flux2 chart doesn't uses the crds dir, so Helm should upgrade all CRDs since they are in templates. - thanks for that. there is alot of confusion as to updgading crds in helm3.


macOS system interpreter warning showing erroneously

Environment data

VS Code version: 1.23.1
Extension version (available under the Extensions sidebar): 2018.4
OS and version: macOS 10.13.4 (High Sierra)
Python version (& distribution if applicable, e.g. Anaconda): 3.6.5 via pyenv
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A

Actual behavior
When I open a Python project, it appropriately detects the interpreter from my environment (by pyenv's shims), but the "Selected interpreter is macOS system Python which is not recommended. Please select different interpreter" still pops up. There's a few-second delay between the error and the correct interpreter appearing in the status bar, so maybe there's an ordering problem or race condition here?
Expected  behavior
There should not be an error message, since I'm not using the system interpreter, and the extension actually does detect that correctly, but only after giving the error.
Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
##########Linting Output - pylint##########
No config file found, using default configuration

(Note that it is detecting pylint, which is only installed in my pyenv version of Python, not the system; I don't get the complaint about no litners being available.)
Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)
The only Python-related message is:
[Extension Host] Python Extension: Failed to get conda environment list from conda Error: spawn conda ENOENT
    at exports._errnoException (util.js:1050:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
    at onErrorNT (internal/child_process.js:367:16)
    at _combinedTickCallback (internal/process/next_tick.js:80:11)
    at process._tickCallback (internal/process/next_tick.js:104:9)
t.log @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:263

@sjml Please could you install our latest development build from here and let us know whether you are still able to replicate this issue.

I installed the development build and it appears to have fixed the problem -- on my first subsequent launch, I still saw the erroneous notification, but after that it hasn't shown up. (Maybe an old cached file or something?)
which python produces /Users/sjml/.pyenv/shims/python from my terminal, FWIW.

The problem is resolved, but just wanted to point out that there may be a bug in the @no-response bot, as I did actually provide followup.


[SR-7041] Remove duplicate conditional check

There is a duplicate if check in TypeCheckConstraints.cpp, as noted by https://gist.github.com/modocache/00eb437ca3cac84960992cdc23fa0f52#file-swift-6edb5132-tasks-txt-L1249

Resolves SR-7041.

@swift-ci please test

@swift-ci please smoke test

@swift-ci please test and merge


Add AGU Open Science in Action Presentation to list

Adds  Open Science in Action Presentation from AGU Fall 2023 to list.
Zenodo: https://zenodo.org/records/8408028
AGU: https://agu.confex.com/agu/fm23/meetingapp.cgi/Paper/1355329

@ehsteve @Alrobbertz Doesn't allow me to assign reviewers


Fix enums with repr(u64)

Use uint64_t for enums with repr(u64).

The travis build failed with:
/usr/bin/ld: /home/travis/build/thepowersgang/mrustc/output/cargo-build/build_libgit2-sys/lib/libgit2.a(filebuf.c.o): undefined reference to symbol 'deflate'
/usr/lib/x86_64-linux-gnu/libz.so: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status

This seems unrelated to my change.

Ooops... Good spot.


[BUG] Cluster creation fails on macOS and asks for docker login repeatedly

What did you do
Tried to create a cluster with 1 server and 2 agents.

How was the cluster created?
k3d cluster create my-cluster --servers 1 --agents 2 --port 9080:80@loadbalancer --port 9443:443@loadbalancer --api-port 6443 --k3s-arg "--disable=traefik@server:*"

It fails with a docker failed to pull the image 'docker.io/rancher/k3s:v1.25.7-k3s1': Error response from daemon: Please run 'docker login' error, even though I had previously done docker login.
If I run a docker pull 'docker.io/rancher/k3s:v1.25.7-k3s1' before the cluster creation, it works.
Screenshots or terminal output
$ docker login
Authenticating with existing credentials...
Login Succeeded

$ k3d cluster create my-cluster --servers 1 --agents 2 --port 9080:80@loadbalancer --port 9443:443@loadbalancer --api-port 6443 --k3s-arg "--disable=traefik@server:*" --verbose
DEBU[0000] DOCKER_SOCK=/var/run/docker.sock
DEBU[0000] Runtime Info:
&{Name:docker Endpoint:/var/run/docker.sock Version:24.0.5 OSType:linux OS:Docker Desktop Arch:aarch64 CgroupVersion:2 CgroupDriver:cgroupfs Filesystem:extfs InfoName:docker-desktop}
DEBU[0000] Additional CLI Configuration:
cli:
  api-port: "6443"
  env: []
  k3s-node-labels: []
  k3sargs:
  - --disable=traefik@server:*
  ports:
  - 9080:80@loadbalancer
  - 9443:443@loadbalancer
  registries:
    create: ""
  runtime-labels: []
  volumes: []
hostaliases: []
DEBU[0000] Configuration:
agents: 2
image: docker.io/rancher/k3s:v1.25.7-k3s1
network: ""
options:
  k3d:
    disableimagevolume: false
    disableloadbalancer: false
    disablerollback: false
    loadbalancer:
      configoverrides: []
    timeout: 0s
    wait: true
  kubeconfig:
    switchcurrentcontext: true
    updatedefaultkubeconfig: true
  runtime:
    agentsmemory: ""
    gpurequest: ""
    hostpidmode: false
    serversmemory: ""
registries:
  config: ""
  use: []
servers: 1
subnet: ""
token: ""
DEBU[0000] ========== Simple Config ==========
{TypeMeta:{Kind:Simple APIVersion:k3d.io/v1alpha4} ObjectMeta:{Name:} Servers:1 Agents:2 ExposeAPI:{Host: HostIP: HostPort:} Image:docker.io/rancher/k3s:v1.25.7-k3s1 Network: Subnet: ClusterToken: Volumes:[] Ports:[] Options:{K3dOptions:{Wait:true Timeout:0s DisableLoadbalancer:false DisableImageVolume:false NoRollback:false NodeHookActions:[] Loadbalancer:{ConfigOverrides:[]}} K3sOptions:{ExtraArgs:[] NodeLabels:[]} KubeconfigOptions:{UpdateDefaultKubeconfig:true SwitchCurrentContext:true} Runtime:{GPURequest: ServersMemory: AgentsMemory: HostPidMode:false Labels:[]}} Env:[] Registries:{Use:[] Create:<nil> Config:} HostAliases:[]}
==========================
DEBU[0000] ========== Merged Simple Config ==========
{TypeMeta:{Kind:Simple APIVersion:k3d.io/v1alpha4} ObjectMeta:{Name:} Servers:1 Agents:2 ExposeAPI:{Host: HostIP:<IP_ADDRESS> HostPort:6443} Image:docker.io/rancher/k3s:v1.25.7-k3s1 Network: Subnet: ClusterToken: Volumes:[] Ports:[{Port:9080:80 NodeFilters:[loadbalancer]} {Port:9443:443 NodeFilters:[loadbalancer]}] Options:{K3dOptions:{Wait:true Timeout:0s DisableLoadbalancer:false DisableImageVolume:false NoRollback:false NodeHookActions:[] Loadbalancer:{ConfigOverrides:[]}} K3sOptions:{ExtraArgs:[{Arg:--disable=traefik NodeFilters:[server:*]}] NodeLabels:[]} KubeconfigOptions:{UpdateDefaultKubeconfig:true SwitchCurrentContext:true} Runtime:{GPURequest: ServersMemory: AgentsMemory: HostPidMode:false Labels:[]}} Env:[] Registries:{Use:[] Create:<nil> Config:} HostAliases:[]}
==========================
INFO[0000] portmapping '9080:80' targets the loadbalancer: defaulting to [servers:*:proxy agents:*:proxy]
INFO[0000] portmapping '9443:443' targets the loadbalancer: defaulting to [servers:*:proxy agents:*:proxy]
DEBU[0000] generated loadbalancer config:
ports:
  80.tcp:
  - k3d-my-cluster-server-0
  - k3d-my-cluster-agent-0
  - k3d-my-cluster-agent-1
  443.tcp:
  - k3d-my-cluster-server-0
  - k3d-my-cluster-agent-0
  - k3d-my-cluster-agent-1
  6443.tcp:
  - k3d-my-cluster-server-0
settings:
  workerConnections: 1024
DEBU[0000] ===== Merged Cluster Config =====
&{TypeMeta:{Kind: APIVersion:} Cluster:{Name:my-cluster Network:{Name:k3d-my-cluster ID: External:false IPAM:{IPPrefix:zero IPPrefix IPsUsed:[] Managed:false} Members:[]} Token: Nodes:[0x140004751e0 0x14000475380 0x14000475520 0x140004756c0] InitNode:<nil> ExternalDatastore:<nil> KubeAPI:0x14000399680 ServerLoadBalancer:0x140002f2c90 ImageVolume: Volumes:[]} ClusterCreateOpts:{DisableImageVolume:false WaitForServer:true Timeout:0s DisableLoadBalancer:false GPURequest: ServersMemory: AgentsMemory: NodeHooks:[] GlobalLabels:map[app:k3d] GlobalEnv:[] HostAliases:[] Registries:{Create:<nil> Use:[] Config:<nil>}} KubeconfigOpts:{UpdateDefaultKubeconfig:true SwitchCurrentContext:true}}
===== ===== =====
DEBU[0000] '--kubeconfig-update-default set: enabling wait-for-server
INFO[0000] Prep: Network
DEBU[0000] Found network {Name:k3d-my-cluster ID:956af13d8ad8b4381e192932424ab02eb5b3ff54a0fe3a1909c5a042868a23f3 Created:2023-08-08 06:38:48.462306428 +0000 UTC Scope:local Driver:bridge EnableIPv6:false IPAM:{Driver:default Options:map[] Config:[{Subnet:<IP_ADDRESS>/16 IPRange: Gateway:<IP_ADDRESS> AuxAddress:map[]}]} Internal:false Attachable:false Ingress:false ConfigFrom:{Network:} ConfigOnly:false Containers:map[] Options:map[com.docker.network.bridge.enable_ip_masquerade:true] Labels:map[app:k3d] Peers:[] Services:map[]}
INFO[0000] Re-using existing network 'k3d-my-cluster' (956af13d8ad8b4381e192932424ab02eb5b3ff54a0fe3a1909c5a042868a23f3)
INFO[0000] Created image volume k3d-my-cluster-images
INFO[0000] Starting new tools node...
DEBU[0000] DOCKER_SOCK=/var/run/docker.sock
DEBU[0000] DOCKER_SOCK=/var/run/docker.sock
DEBU[0000] DOCKER_SOCK=/var/run/docker.sock
DEBU[0000] [Docker] Local DfD: using 'host.docker.internal'
DEBU[0000] [Docker] wanted to use 'host.docker.internal' as docker host, but it's not resolvable locally: lookup host.docker.internal: no such host
DEBU[0000] DOCKER_SOCK=/var/run/docker.sock
DEBU[0000] Detected CgroupV2, enabling custom entrypoint (disable by setting K3D_FIX_CGROUPV2=false)
DEBU[0000] Created container k3d-my-cluster-tools (ID: 114d7b45cef1f7231e510818ffff93b6c618b4b9c568bf9b0f43a0d0adda2ab3)
DEBU[0000] Node k3d-my-cluster-tools Start Time: 2023-08-08 08:43:30.454212 +0200 CEST m=+0.133891918
INFO[0000] Starting Node 'k3d-my-cluster-tools'
DEBU[0000] Truncated 2023-08-08 06:43:30.616273461 +0000 UTC to 2023-08-08 06:43:30 +0000 UTC
INFO[0001] Creating node 'k3d-my-cluster-server-0'
ERRO[0001] Failed Cluster Creation: failed setup of server/agent node k3d-my-cluster-server-0: failed to create node: runtime failed to create node 'k3d-my-cluster-server-0': failed to create container for node 'k3d-my-cluster-server-0': docker failed to pull image 'docker.io/rancher/k3s:v1.25.7-k3s1': docker failed to pull the image 'docker.io/rancher/k3s:v1.25.7-k3s1': Error response from daemon: Please run 'docker login'
ERRO[0001] Failed to create cluster >>> Rolling Back
INFO[0001] Deleting cluster 'my-cluster'
DEBU[0001] no netlabel present on container /k3d-my-cluster-tools
DEBU[0001] failed to get IP for container /k3d-my-cluster-tools as we couldn't find the cluster network
DEBU[0001] Cluster Details: &{Name:my-cluster Network:{Name:k3d-my-cluster ID:956af13d8ad8b4381e192932424ab02eb5b3ff54a0fe3a1909c5a042868a23f3 External:true IPAM:{IPPrefix:<IP_ADDRESS>/16 IPsUsed:[<IP_ADDRESS>] Managed:false} Members:[]} Token:UXlFIDdKpumFYrwrVMSi Nodes:[0x140004751e0 0x14000475380 0x14000475520 0x140004756c0 0x140000036c0] InitNode:<nil> ExternalDatastore:<nil> KubeAPI:0x14000399680 ServerLoadBalancer:0x140002f2c90 ImageVolume:k3d-my-cluster-images Volumes:[k3d-my-cluster-images]}
DEBU[0001] Deleting node k3d-my-cluster-serverlb ...
ERRO[0001] docker failed to remove the container 'k3d-my-cluster-serverlb': Error response from daemon: No such container: k3d-my-cluster-serverlb
DEBU[0001] Deleting node k3d-my-cluster-server-0 ...
ERRO[0001] docker failed to remove the container 'k3d-my-cluster-server-0': Error response from daemon: No such container: k3d-my-cluster-server-0
DEBU[0001] Deleting node k3d-my-cluster-agent-0 ...
ERRO[0001] docker failed to remove the container 'k3d-my-cluster-agent-0': Error response from daemon: No such container: k3d-my-cluster-agent-0
DEBU[0001] Deleting node k3d-my-cluster-agent-1 ...
ERRO[0001] docker failed to remove the container 'k3d-my-cluster-agent-1': Error response from daemon: No such container: k3d-my-cluster-agent-1
DEBU[0001] Deleting node k3d-my-cluster-tools ...
DEBU[0001] Skip deletion of cluster network 'k3d-my-cluster' because it's managed externally
INFO[0001] Deleting 1 attached volumes...
DEBU[0001] Deleting volume k3d-my-cluster-images...
FATA[0001] Cluster creation FAILED, all changes have been rolled back!

$ docker pull docker.io/rancher/k3s:v1.25.7-k3s1
v1.25.7-k3s1: Pulling from rancher/k3s
8f802876bc40: Pull complete
91fe88c41772: Pull complete
Digest: sha256:aa02a6508ec2b8aeac839443f3b69b24e7789a8d9f0d9cb24f2adc2f26d5a60a
Status: Downloaded newer image for rancher/k3s:v1.25.7-k3s1
docker.io/rancher/k3s:v1.25.7-k3s1

$ k3d cluster create my-cluster --servers 1 --agents 2 --port 9080:80@loadbalancer --port 9443:443@loadbalancer --api-port 6443 --k3s-arg "--disable=traefik@server:*"
INFO[0000] portmapping '9080:80' targets the loadbalancer: defaulting to [servers:*:proxy agents:*:proxy]
INFO[0000] portmapping '9443:443' targets the loadbalancer: defaulting to [servers:*:proxy agents:*:proxy]
INFO[0000] Prep: Network
INFO[0000] Re-using existing network 'k3d-my-cluster' (956af13d8ad8b4381e192932424ab02eb5b3ff54a0fe3a1909c5a042868a23f3)
INFO[0000] Created image volume k3d-my-cluster-images
INFO[0000] Starting new tools node...
INFO[0000] Starting Node 'k3d-my-cluster-tools'
INFO[0001] Creating node 'k3d-my-cluster-server-0'
INFO[0001] Creating node 'k3d-my-cluster-agent-0'
INFO[0001] Creating node 'k3d-my-cluster-agent-1'
INFO[0001] Creating LoadBalancer 'k3d-my-cluster-serverlb'
INFO[0001] Using the k3d-tools node to gather environment information
INFO[0001] Starting new tools node...
INFO[0001] Starting Node 'k3d-my-cluster-tools'
INFO[0002] Starting cluster 'my-cluster'
INFO[0002] Starting servers...
INFO[0002] Starting Node 'k3d-my-cluster-server-0'
INFO[0006] Starting agents...
INFO[0006] Starting Node 'k3d-my-cluster-agent-1'
INFO[0006] Starting Node 'k3d-my-cluster-agent-0'
INFO[0010] Starting helpers...
INFO[0010] Starting Node 'k3d-my-cluster-serverlb'
INFO[0016] Injecting records for hostAliases (incl. host.k3d.internal) and for 5 network members into CoreDNS configmap...
INFO[0018] Cluster 'my-cluster' created successfully!
INFO[0018] You can now use it like this:
kubectl cluster-info

Which OS & Architecture
$ k3d runtime-info
arch: aarch64
cgroupdriver: cgroupfs
cgroupversion: "2"
endpoint: /var/run/docker.sock
filesystem: extfs
infoname: docker-desktop
name: docker
os: Docker Desktop
ostype: linux
version: 24.0.5

macOS Ventura 13.5
Which version of k3d
$ k3d version
k3d version v5.4.9
k3s version v1.25.7-k3s1 (default)

Which version of docker
$ docker version; docker info
Client:
 Cloud integration: v1.0.35-desktop+001
 Version:           24.0.5
 API version:       1.43
 Go version:        go1.20.6
 Git commit:        ced0996
 Built:             Fri Jul 21 20:32:30 2023
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

Server: Docker Desktop 4.22.0 (117440)
 Engine:
  Version:          24.0.5
  API version:      1.43 (minimum version 1.12)
  Go version:       go1.20.6
  Git commit:       a61e2b4
  Built:            Fri Jul 21 20:35:38 2023
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.6.21
  GitCommit:        3dce8eb055cbb6872793272b4f20ed16117344f8
 runc:
  Version:          1.1.7
  GitCommit:        v1.1.7-0-g860f061
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0
Client:
 Version:    24.0.5
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.11.2-desktop.1
    Path:     /Users/spremraj/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.20.2-desktop.1
    Path:     /Users/spremraj/.docker/cli-plugins/docker-compose
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.0
    Path:     /Users/spremraj/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.20
    Path:     /Users/spremraj/.docker/cli-plugins/docker-extension
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v0.1.0-beta.6
    Path:     /Users/spremraj/.docker/cli-plugins/docker-init
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     /Users/spremraj/.docker/cli-plugins/docker-sbom
  scan: Docker Scan (Docker Inc.)
    Version:  v0.26.0
    Path:     /Users/spremraj/.docker/cli-plugins/docker-scan
  scout: Command line tool for Docker Scout (Docker Inc.)
    Version:  0.20.0
    Path:     /Users/spremraj/.docker/cli-plugins/docker-scout

Server:
 Containers: 5
  Running: 5
  Paused: 0
  Stopped: 0
 Images: 5
 Server Version: 24.0.5
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 3dce8eb055cbb6872793272b4f20ed16117344f8
 runc version: v1.1.7-0-g860f061
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
  cgroupns
 Kernel Version: 5.15.49-linuxkit-pr
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 5
 Total Memory: 10.7GiB
 Name: docker-desktop
 ID: c365d28b-7020-42f3-85ed-c833122e8809
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  <IP_ADDRESS>/8
 Live Restore Enabled: false

WARNING: daemon is not using the default seccomp profile

Just encountered this issue as well on MacOS Sonoma

I assume there's something specific to the keychains / credential stores on those hosts.
Unfortunately I cannot reproduce this on any machine or VM I have, so it's fairly difficult to debug.
The fact that the error is coming from the docker Daemon itself is a little concerning.
For everyone that's still experiencing this issue - it may be interesting to know your k3d versions and your docker infos to see if there's an issue between specific versions of k3d and docker.

is there any solution found for this ?

any update?

Can anyone provide any debug information or anything I asked for here?


feat(actors): Default token settings

Basic implementation of default actor token settings suggested in #1652
It's mostly a proof of concept while someone review the suggested defaults and decide where best to put that code.

This looks good. My only thoughts are that non-PC actors should default to hostile, not neutral... and we don't need numbers appended to minion groups.
If you're comfortable making those changes, I'd be happy to accept the PR. If not, I can base a new PR from this draft and make it myself.
Regardless, I appreciate the help and time you're putting in!

That's easy enough, I'll update the PR and remove the Draft status.
Do I leave the prepended adjectives for Rivals ?

I'd rather we put it behind a setting, in case someone doesn't like it. But I changed the settings format after you started, so I can make the change after the PR is merged... or you can merge main into your working code and add it to the actorSettings setting menu.

I'll give it a try, I'll have something ready tomorrow.

Should be good, though I couldn't find how settings where ordered in their respective menus.

@obrenckle looks good. Can you please create a new setting without removing token_configured? This is used to configure the prototype token (but still allow the user to override it if they prefer.)

Actually, I'll just do it. :)

Sorry, I thought you had set the token_configure as an example, I should have checked with grep...


Top 404s as of 2022/03/04

Here are the top 404s:

[ ] /v1alpha1 - @tomkerkhove - what should this redirect to?
[ ] /docs/INSERT-CORRECT-VERSION/deploy/ - @tomkerkhove do you have an idea where this is coming from?
[ ] /docs/2.6deploy - #708
[ ] /scalers/mysql/
[ ] /scalers/redis-lists/
[ ] /%EF%BC%89%E3%80%82
[ ] /scalers/apache-kafka/

@tomkerkhove and @kedacore/keda-maintainers : please see my questions in the opening comment.

@tomkerkhove - another question: is @kedacore/keda-maintainers a private team? If so, could you make it public? Otherwise I can't refer to it. Thanks.

[ ]  /v1alpha1 - @tomkerkhove

Ignore, that shouldn't be used

[ ]  /docs/INSERT-CORRECT-VERSION/deploy/ - @tomkerkhove

Ignore, that shouldn't be used

[ ]  /docs/2.6deploy - Fix deploy 404s #708

Thanks

[ ]  /scalers/mysql/

Send to latest

[ ]  /scalers/redis-lists/

Send to latest

[ ]  /%EF%BC%89%E3%80%82

No idea what this is - I'd say ignore, that shouldn't be used

[ ]  /scalers/apache-kafka/

Send to latest

[ ]   /v1alpha1 - @tomkerkhove

Ignore, that shouldn't be used

Right, it shouldn't be used. But rather than a 404, it might be more helpful to someone visiting that link if it redirected to an explanation that /v1alpha1 is just an API version ID -- possibly referencing https://kubernetes.io/docs/reference/using-api/#api-versioning? WDYT?

That's OK for me, but personally wouldn't spend much time on it given 404 is correct as well.
Otherwise we will have rules for all these scenarios


Tracking issue: remove references to List.nthLe

During the port, List.nthLe has been deprecated in favour of List.get. This issue tracks removing all references of the latter.
Particular subtasks.

Remove uses of nthLe in proofs: these are usually marked with set_option linter.deprecated false in.
(Because of leanprover/lean4#..., there are further references.)
Re-state theorems involving nthLe using get; this often involves fixing proofs.
In step 2, rename theorems using nthLe to get, deprecating the old names.
After enough time, remove unused deprecated theorems.

Some recent PRs working towards this goal:

migrating nthLe -> get: #12171, #12173, #12170, #12219, #12208, #12209, #12220, #12301
removing deprecated theorems: #9607, #12306, #12307; #12362, #12367, #12350
add deprecation dates: #12347, #12337

All references have been removed by now: this issue can be closed.


install_supersonic.sh does not work

Apparently, there is a missing call to "autogen.sh" inside
"install_supersonic.sh" script.

Pushed trivial fix into a separate branch in my clone -
https://code.google.com/r/wojtekzozlak-supersonic/source/detail?r=6587b3edc9dba6
1ad8f4ebb9551f4744e25b5af8&name=installation-fix .

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 25 Jan 2014 at 6:17

I think this ticket should be closed. I don't know why it got migrated with the import. Esp. since there is a comment from one of the authors describing proper usage (as not to run into the issue).

I'm sorry about extremely long delay. After Google Code shutdown I didn't recovered my presence on github till now.


Add discouraged to schema (and with statement demo feature)

This adds discouraged to the schema. The idea here is that consumers would be able to show something like an MDN deprecation banner, saying that a feature is discouraged from use (citing a source) and suggesting an alternative (if one exists).
There are a couple of things missing here:

There is no documentation. I'd like to get some feedback on the overall approach here before writing up how consumers are meant to use this or how feature authors are to decide whether to set discouraged and set useful according_to and alternative values.
This depends on https://github.com/web-platform-dx/web-features/pull/2386 as a valid alternative feature.

Someday, I'd like to have a proper status (with iconography) for this condition that would take the place of Baseline for such features. This is a prerequisite for doing this, but doesn't actually affect the Baseline definition today.
See also: https://github.com/web-platform-dx/web-features/issues/311

To stress test this a bit, I went through the CSS keys that are deprecated and standard track. I'm thinking I'll create the following features:
Clip
alternative: clip-path

"css.properties.clip"
"css.properties.clip.auto"
"css.types.shape"
"css.types.shape.rect"

Media Queries (deprecated)
alternative: media-queries

"css.at-rules.media.device-aspect-ratio"
"css.at-rules.media.device-height"
"css.at-rules.media.device-width"

Writing mode (deprecated)
alternative: writing-mode

"css.properties.writing-mode.lr"
"css.properties.writing-mode.lr-tb"
"css.properties.writing-mode.rl"
"css.properties.writing-mode.rl-tb"
"css.properties.writing-mode.tb"
"css.properties.writing-mode.tb-rl"

color-adjust
alternative: print-color-adjust

"css.properties.color-adjust"

SVG (deprecated)

Existing keys in draft, plus css.properties.glyph-orientation-vertical which was missed.

IME Mode
(no alternative)

"css.properties.ime-mode"

text-decoration-line :blink
alternative: animations-css

"css.properties.text-decoration-line.blink"

word-break: break-word
alternative: Use overflow-wrap: anywhere instead (note we only can link to overflow-wrap)

"css.properties.word-break.break-word"

overflow: overlay
alternative: Use overflow: auto  instead (note we can only link to overflow-shorthand)

"css.types.overflow.overlay"

Overview
Note that the list isn't long (and makes me want to double check my query), but it does surface a question around alternatives-
What should we do when the alternative is just a single key within a larger feature? Can we mention the alternative in the description when possible?

I like this. Just left one comment to help consumers.
My more important general comment is how do we ensure that this isn't used for things we don't agree with. Because this is not data we can really check, there isn't much, beside thorough reviewing, to ensure this isn't used incorrectly.
Not sure what incorrect usage there could be, but I want to avoid, for example, cases where someone marks a feature as discouraged because it's just not implemented in browser X, and browser X vendor opposes that feature.

That is a concern for sure, and it's independent of the wording. Even going with "deprecated", unless that comes out of the standardization process, it's not clear what should happen next. If one vendor considers an API as deprecated, but another one doesn't. Is that feature deprecated? Not hypothetical either, see Battery Status.

Maybe we limit this to cases where it's unambiguous (either from the spec or alignment of vendors) and explicitly exclude cases where there is disagreement for now?

This PR was discussed during today's WebDX CG call (minutes).

I've pushed some guidelines and changes to the README for consumers. I hope it answers most of the remaining questions.

What should we do when the alternative is just a single key within a larger feature? Can we mention the alternative in the description when possible?

Eventually, I think we should have a way to refer to inner/sub-features, but I don't think we have to have it here. I suspect that after we've enumerated the discouraged features we can revisit this more easily.
For now, I think we can satisfy the basic case of "see also: [something else to use instead]" without providing a detailed explanation for what we're referring to, specifically.

Not sure what incorrect usage there could be, but I want to avoid, for example, cases where someone marks a feature as discouraged because it's just not implemented in browser X, and browser X vendor opposes that feature.

Maybe we limit this to cases where it's unambiguous (either from the spec or alignment of vendors) and explicitly exclude cases where there is disagreement for now?

I included some text covering this in the new guidelines. The main thrust of it is: only set discouraged when a feature has consensus for discouragement. In most cases, this will come affirmatively from the specification (text saying don't use it or a transparent decision to drop something from a specification). Less frequently, this could come from the implementers, if all of them did so (e.g., you have a single-browser feature and that vendor starts telling developers to stop using that feature).

FYI: I'm planning to merge this PR after the last BCD and web-features releases of the year, probably the afternoon of Friday, December 20.


Facebook - get timestamp from tahoe if missing.

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x ] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x ] Searched the bugtracker for similar pull requests
[ x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[ ] I am the original author of this code and I am willing to release it under Unlicense
[x ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x ] Bug fix
[ ] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
For post live videos, timestamp was not extracted.
Explanation of your pull request in arbitrary form goes here. Please make sure the description explains the purpose and effect of your pull request and is worded well enough to be understood. Provide as much context and examples as possible.

Hi, I improved PR. What is stopping us from merging this PR?


TMDB table's?

Can anyone explain me how and whatfor these table's are?
they are and stay empty,
There are these scripts: precacheTmdbInfo.php and queryTmdb.php
-> php precacheTmdbInfo.php
Done precaching tmdb information collections  (that's it, table's stay empty)
-> php queryTmdb.php
queryTmdb.php - query tmdb distribution script
You have to give the filename as a parameter which you received first
??
tmdb_cast	Browse Browse	Structure Structure	Search Search	Insert Insert	Empty Empty	Drop Drop	~0	InnoDB	ascii_general_ci	48 KiB	-
tmdb_credits	Browse Browse	Structure Structure	Search Search	Insert Insert	Empty Empty	Drop Drop	~0	InnoDB	ascii_general_ci	32 KiB	-
tmdb_crew	Browse Browse	Structure Structure	Search Search	Insert Insert	Empty Empty	Drop Drop	~0	InnoDB	ascii_general_ci	48 KiB	-
tmdb_images	Browse Browse	Structure Structure	Search Search	Insert Insert	Empty Empty	Drop Drop	~0	InnoDB	ascii_general_ci	32 KiB	-
tmdb_info	Browse Browse	Structure Structure	Search Search	Insert Insert	Empty Empty	Drop Drop	~0	InnoDB	ascii_general_ci	32 KiB	-
tmdb_trailers	Browse Browse	Structure Structure	Search Search	Insert Insert	Empty Empty	Drop Drop	~0	InnoDB	ascii_general_ci	32 KiB

The acronym 'tmdb' seems related to https://www.themoviedb.org/
So I think someone started to implement support for that database, but never finished it? Otherwise I have no clue.

Recent Spotweb releases introduced something called collections (or mastercollections as it is called in the code).
If you run the most recent release, you can see the collection bit on the Spot details page (it automatically recognizes media and adds season/episode/etc selection to the system). If your system does not do this, please enable 'Create collections' on the settings page, and then run 'recreate-collections.php' on the CLI (it will take forever to run).
For the TMDB tables, this is related to those collecitons so it seems. If you run 'exportmc.php' to export the master collections, you then are able to fetch the TheMovieDb data using 'queryTmdb.php'  which seems to export it to some kind of CSV file. You then are able to import this using  'importMc.php'.  My guess as to why this is so convulated is that it can be made to run in parallel or something (exportmc allows to split the export file into multiple chunks).
I do think it is not finished yet (at all!), but it seems rather nice as it can also pre-cache a lot of TMDB information which has a lot of potential to further enrich the UI part of Spotweb.

Yes, i have been playing around this this, but not in a synology ;-)
Anyway..
php exportmc.php
SpotWeb crashed
Export of collections failed:
42000: 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ON (mc.title, mc.year)
mc.id AS mcid,' at line 1 (SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ON (mc.title, mc.year)
mc.id AS mcid,' at line 1)
#0 /home/public_html/spotweb/lib/dbeng/dbeng_pdo.php(146): dbeng_pdo->exec('SELECT DISTINCT...', Array)
#1 /home/public_html/spotweb/exportmc.php(40): dbeng_pdo->arrayQuery('SELECT DISTINCT...')
So yes, indeed it's not finished yet. ;-)

Try on PostgreSQL as the "distinct on" is a PostgreSQL specific bit, or rewrite the query to be compatible with MySQL.


Walkthrough failing for .Net 6

When I tried following this walkthrough using .Net 6, and the sample projects as specified. SimpleMathComponent wouldn't build
Build started...
1>------ Build started: Project: SimpleMathComponent, Configuration: Debug x64 ------
1>64 bit MIDLRT Processing D:\Projects - Tests\C# Projection Test\CsWinRT-master\CsWinRT-master\src\Samples\Net5ProjectionSample\SimpleMathComponent\SimpleMath.idl
1>SimpleMath.idl
1>64 bit MIDLRT Processing C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\winrt\winrtbase.idl
1>winrtbase.idl
1>64 bit MIDLRT Processing C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\winrt\midlbase.idl
1>midlbase.idl
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.ai.machinelearning.machinelearningcontract\<IP_ADDRESS>\windows.ai.machinelearning.machinelearningcontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.ai.machinelearning.preview.machinelearningpreviewcontract\<IP_ADDRESS>\windows.ai.machinelearning.preview.machinelearningpreviewcontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.applicationmodel.calls.background.callsbackgroundcontract\<IP_ADDRESS>\windows.applicationmodel.calls.background.callsbackgroundcontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.applicationmodel.calls.callsphonecontract\<IP_ADDRESS>\windows.applicationmodel.calls.callsphonecontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.applicationmodel.calls.callsvoipcontract\<IP_ADDRESS>\windows.applicationmodel.calls.callsvoipcontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.applicationmodel.communicationblocking.communicationblockingcontract\<IP_ADDRESS>\windows.applicationmodel.communicationblocking.communicationblockingcontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.applicationmodel.socialinfo.socialinfocontract\<IP_ADDRESS>\windows.applicationmodel.socialinfo.socialinfocontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.applicationmodel.startuptaskcontract\<IP_ADDRESS>\windows.applicationmodel.startuptaskcontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.devices.custom.customdevicecontract\<IP_ADDRESS>\windows.devices.custom.customdevicecontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.devices.deviceslowlevelcontract\<IP_ADDRESS>\windows.devices.deviceslowlevelcontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.devices.printers.printerscontract\<IP_ADDRESS>\windows.devices.printers.printerscontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.devices.smartcards.smartcardbackgroundtriggercontract\<IP_ADDRESS>\windows.devices.smartcards.smartcardbackgroundtriggercontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.devices.smartcards.smartcardemulatorcontract\<IP_ADDRESS>\windows.devices.smartcards.smartcardemulatorcontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.foundation.foundationcontract\<IP_ADDRESS>\windows.foundation.foundationcontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.foundation.universalapicontract\<IP_ADDRESS>\windows.foundation.universalapicontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.gaming.xboxlive.storageapicontract\<IP_ADDRESS>\windows.gaming.xboxlive.storageapicontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.graphics.printing3d.printing3dcontract\<IP_ADDRESS>\windows.graphics.printing3d.printing3dcontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.networking.connectivity.wwancontract\<IP_ADDRESS>\windows.networking.connectivity.wwancontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.networking.sockets.controlchanneltriggercontract\<IP_ADDRESS>\windows.networking.sockets.controlchanneltriggercontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.security.isolation.isolatedwindowsenvironmentcontract\<IP_ADDRESS>\windows.security.isolation.isolatedwindowsenvironmentcontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.services.maps.guidancecontract\<IP_ADDRESS>\windows.services.maps.guidancecontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.services.maps.localsearchcontract\<IP_ADDRESS>\windows.services.maps.localsearchcontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.services.store.storecontract\<IP_ADDRESS>\windows.services.store.storecontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.services.targetedcontent.targetedcontentcontract\<IP_ADDRESS>\windows.services.targetedcontent.targetedcontentcontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.storage.provider.cloudfilescontract\<IP_ADDRESS>\windows.storage.provider.cloudfilescontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.system.profile.profilehardwaretokencontract\<IP_ADDRESS>\windows.system.profile.profilehardwaretokencontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.system.profile.profilesharedmodecontract\<IP_ADDRESS>\windows.system.profile.profilesharedmodecontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.system.profile.systemmanufacturers.systemmanufacturerscontract\<IP_ADDRESS>\windows.system.profile.systemmanufacturers.systemmanufacturerscontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.system.systemmanagementcontract\<IP_ADDRESS>\windows.system.systemmanagementcontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.ui.viewmanagement.viewmanagementviewscalingcontract\<IP_ADDRESS>\windows.ui.viewmanagement.viewmanagementviewscalingcontract.winmd
1>Processing WinMD c:\program files (x86)\windows kits\10\references\10.0.19041.0\windows.ui.xaml.core.direct.xamldirectcontract\<IP_ADDRESS>\windows.ui.xaml.core.direct.xamldirectcontract.winmd
1>MDMERGE : error MDM2025: The input directory or file D:\Projects - Tests\C  is not valid.
1>Microsoft(R) Metadata Merge Utility Version 10.0.49.
1>
1>
1>D:\Projects - Tests\C# Projection Test\CsWinRT-master\CsWinRT-master\src\Samples\Net5ProjectionSample\packages\Microsoft.Windows.CppWinRT.2.0.200703.9\build\native\Microsoft.Windows.CppWinRT.targets(468,9): error MSB3073: The command "mdmerge @"D:\Projects - Tests\C# Projection Test\CsWinRT-master\CsWinRT-master\src\Samples\Net5ProjectionSample_build\x64\Debug\SimpleMathComponent\obj\mdmerge.rsp"" exited with code 2.
1>Done building project "SimpleMathComponent.vcxproj" -- FAILED.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
So I renamed the folder 'C# Project Test' to 'CSProjectionTest' but when I reloaded the solution VS is showing a brown bar and red cross above the tabs with the following error message

Current solution contains incorrect configurations mappings

So I've opened the Configuration Manager and everything looks correct to me...
SimpleMathComponent
Debug x64
Release x64
SimpleMathProjection
Debug x64
Release x64
Edit: However, ignoring the error, I built the project again and it succeeded.
Further, trying to build the solution fails with the following errors...

Severity	Code	Description	Project	File	Line	Suppression State
Error		Could not read the Windows SDK's Platform.xml at C:\Program Files (x86)\Windows Kits\10\Platforms\UAP\10.0.22000.0\Platform.xml	SimpleMathProjection	D:\Projects - Tests\CSProjectionTest\CsWinRT-master\CsWinRT-master\src\Samples\Net5ProjectionSample\SimpleMathProjection\EXEC	1

Severity	Code	Description	Project	File	Line	Suppression State
Error	MSB3073	The command ""C:\Users\deads.nuget\packages\microsoft.windows.cswinrt\1.3.5\cswinrt.exe" @"D:\Projects - Tests\CSProjectionTest\CsWinRT-master\CsWinRT-master\src\Samples\Net5ProjectionSample_build\x64\Release\SimpleMathProjection\bin\cswinrt.rsp"" exited with code 1.	SimpleMathProjection	C:\Users\deads.nuget\packages\microsoft.windows.cswinrt\1.3.5\build\Microsoft.Windows.CsWinRT.targets	115

Severity	Code	Description	Project	File	Line	Suppression State
Error	NETSDK1112	The runtime pack for Microsoft.Windows.SDK.NET.Ref was not downloaded. Try running a NuGet restore with the RuntimeIdentifier 'any'.	SimpleMathProjection	C:\Program Files\dotnet\sdk\6.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets	427

Here's my SimpleMathProjection.nuspec file
<?xml version="1.0" encoding="utf-8"?>
<package xmlns="http://schemas.microsoft.com/packaging/2012/06/nuspec.xsd">
  <metadata>
    <id>SimpleMathComponent</id>
    <version>0.1.0-prerelease</version>
    <authors>Contoso Math Inc.</authors>
    <description>A simple component with basic math operations</description>
    <dependencies>
      <group targetFramework="net6.0-windows10.0.22000.0" />
    </dependencies>
  </metadata>
  <files>
    <!--Support .NET Core 3, UAP, .NET Framework 4.6, .NET 5, C++ -->
    <!--Architecture-netural assemblies-->
    <file src="..\..\_build\x64\Debug\SimpleMathProjection\bin\SimpleMathProjection.dll" target="lib\net6.0-windows10.0.22000.0\SimpleMathProjection.dll" />
    <!--Architecture-specific implementation DLLs should be copied into RID-relative folders-->
    <file src="..\..\_build\x64\Debug\SimpleMathComponent\bin\SimpleMathComponent\SimpleMathComponent.dll" target="runtimes\win10-x64\native\SimpleMathComponent.dll" />
  </files>
</package>

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

ID: a40b34b2-1bc9-25ed-b91e-cee68bc9edc1
Version Independent ID: ecfcea0e-cad5-f4c7-6ab2-6970d4e8adcb
Content: Make a C# projection from a C++/WinRT component, distribute as a NuGet for .NET 5+ apps - UWP applications
Content Source: windows-apps-src/csharp-winrt/net-projection-from-cppwinrt-component.md
Product: uwp
Technology: platform
GitHub Login: @stevewhims
Microsoft Alias: stwhi

So coming back to this today, I cleaned the solution, rebuilt the solution

Build started...
========== Build: 0 succeeded, 0 failed, 2 up-to-date, 0 skipped ==========

And error list:

Severity	Code	Description	Project	File	Line	Suppression State
Error		Could not read the Windows SDK's Platform.xml at C:\Program Files (x86)\Windows Kits\10\Platforms\UAP\10.0.22000.0\Platform.xml	SimpleMathProjection	D:\Projects - Tests\CSProjectionTest\CsWinRT-master\CsWinRT-master\src\Samples\Net5ProjectionSample\SimpleMathProjection\EXEC	1

Severity	Code	Description	Project	File	Line	Suppression State
Error	MSB3073	The command ""C:\Users\deads.nuget\packages\microsoft.windows.cswinrt\1.3.5\cswinrt.exe" @"D:\Projects - Tests\CSProjectionTest\CsWinRT-master\CsWinRT-master\src\Samples\Net5ProjectionSample_build\x64\Release\SimpleMathProjection\bin\cswinrt.rsp"" exited with code 1.	SimpleMathProjection	C:\Users\deads.nuget\packages\microsoft.windows.cswinrt\1.3.5\build\Microsoft.Windows.CsWinRT.targets	115

Thanks, @Gavin-Williams, I'm making enquiries about expected support.
-Steve

I just want to point out that I did stray slightly from the walkthrough in two ways - (1) I used .Net 6 instead of 5 and (2) I removed the lines in the nuspec file which coded for dependencies on .net framework / core / uwp.
I'm pretty weak with 'dev ops' or whatever all this manual prep work is called - I've been spoiled by learning to develop with UWP over the past few years, which makes everything so damn easy. Everything just works. So apologies for stumbling over what is probably straight forward for regular C++ dev's.
To me, that first error looks like it's saying that the Windows SDK isn't supporting UWP. I have removed UWP as a target - but I'm wondering if the sample project somehow hard codes support for the 4 platforms that it supports (UWP, Core, Framework, 5). The second error just above, I would interpret that as simply the tool failing because of the previous error.

@Gavin-Williams, using .NET 6 vs .NET 5 should not cause any new issues here. Are both your C++/WinRT and C# projects targeting the 10.0.22000 SDK? It seems from the output above that the C++/WinRT project might be targeting 10.0.19041.0. Is the TargetFramework property in your csproj net6.0-windows10.0.22000.0?
Could you also confirm what version of VS you are using? If there's a repro we can look at, that would make it easier to determine the issue.

@angelazhangmsft I'm using VS2022.
I updated SimpleMathComponent properties:
Target Platform Version -> 10.0.20348.0
Platform Toolset -> Visual Studio 2022 (v143)
I checked SimpleMathProjection.csproj and TargetFramework = net6.0-windows10.0.22000.0
I checked SimpleMathProjection.nuspec and <group targetFramework = "net6.0-windows10.0.22000.0"

@Gavin-Williams, it looks like you don't have the Windows 10.0.22000.0 SDK installed. You can install it here, or alternatively target the 10.0.20348.0 SDK.
For the NU5019 error, it might be because you are build Release and not Debug. You will need to change the nuspec accordingly and check the location of the SimpleMathProjection.dll output.

Where is the DLL (SimpleMathProjection.dll) meant to be? I don't see it. And where is the nuget package that is meant to be generated?

When I'm trying to consume the runtime class, in Program.cs, SimpleMathComponent could not be found. I think this line in the docs for SampleConsoleApp.csproj is wrong.

../../CppWinRTProjectionSample/SimpleMathProjection/nuget

This is the folder path ...

D:\Projects - Tests\CSProjectionTest\CsWinRT-master\src\Samples\Net5ProjectionSample\SimpleMathProjection\nuget

And in that folder I see 1 file - SimpleMathProjection.nuspec - is that right?

awesome trying itnow @angelazhangmsft

So going back to the CppWinRTComponentProjectionSample, I thought it was working, but now when I try to build the solution I get an error...

NU5019	File not found: '...._build\x64\Debug\SimpleMathProjection\bin\SimpleMathProjection.dll'.	SimpleMathProjection	C:\Program Files\dotnet\sdk\6.0.100\Sdks\NuGet.Build.Tasks.Pack\build\NuGet.Build.Tasks.Pack.targets	221

When I look in the bin folder there, I see a ref folder and a cswinrt.rsp file. There is no dll

I checked configuration again - switching around between release and debug. Now I have 2 errors

Path 'D:\Projects - Tests\CSProjectionTest\Net5ProjectionSample_build\x64\Debug\SimpleMathComponent\bin\SimpleMathComponent\SimpleMathComponent.winmd' is not a file or directory	SimpleMathProjection	D:\Projects - Tests\CSProjectionTest\Net5ProjectionSample\SimpleMathProjection\EXEC	1

MSB3073	The command ""C:\Users\deads.nuget\packages\microsoft.windows.cswinrt\1.3.5\cswinrt.exe" @"D:\Projects - Tests\CSProjectionTest\Net5ProjectionSample_build\x64\Debug\SimpleMathProjection\bin\cswinrt.rsp"" exited with code 1.	SimpleMathProjection	C:\Users\deads.nuget\packages\microsoft.windows.cswinrt\1.3.5\build\Microsoft.Windows.CsWinRT.targets	115

But now I have files in _build/x64/Debug/SimpleMathComponent/bin/SimpleMathComponent/
SimpleMathComponent.dll
...

I haven't fixed this project yet - I'll go through the walkthrough one more time. Maybe I missed something.

I went through the steps today, this time using Visual Studio 2022 and .NET 6. Of course, tweaks to the steps are necessary for those bits, but I did manage to complete it successfully. So I then updated the topic to focus primarily Visual Studio 2022 and .NET 6 (since those are now GA), while still supporting VS2019 and .NET 5.
After those changes were published I made sure I hadn't missed anything by going through the steps an additional time.
So if I follow the steps as they are currently, it works for me.
I'll go ahead and close, but please create a new issue if there's anything wrong with the steps as they are now.
Thanks!
Steve


Refresh entire provider for special LPAR UUID

The HMC uses 88888888-8888-8888-8888-888888888888 to indicate an unassigned LPAR UUID. This is an error state, but we've seen it occur in a test environment so I'm adding a special case for it to trigger a full ems refresh.

Awesome @jaywcarman !  Can we get a spec test covering this case?


We don't support the chainId you provided: eip155:31337

Hey there! Using the latest 2.0.0-rc1 - I am getting this error when connected to hardhat
[{\"field\":\"chainId\",\"description\":\"We don't support the chainId you provided: eip155:31337\"}]}", requestBody="{\"method\":\"eth_getBalance\",\"params\":
my config:
const chains = [mainnet, polygon, avalanche, bsc, hardhat];
const {provider} = configureChains(chains, [
  walletConnectProvider({projectId}),
]);
const wagmiClient = createClient({
  autoConnect: true,
  connectors: modalConnectors({appName: "web3Modal", chains}),
  provider,
});

const ethereumClient = new EthereumClient(wagmiClient, chains);

workaround for now its to manually specify jsonRpcProvider
const {provider} = configureChains(chains, [
jsonRpcProvider({
rpc: (chain) => ({
http: http://<IP_ADDRESS>:8545,
}),
}),
],);

Error is coming from our walletConnectProvider which is essentially an rpc, that chain id seems to be refereeing to something called GoChain Testnet which is not supported, hence why you needed custom rpc.


Replace upper belt sliding surface

From #65. The UHMW tape is worn out in some areas, which is causing the belt to make a lot of noise during towing. The wear is probably related to the fact that in some spots the tensioning clamp bracket rubs a little (#69 would probably address this). I am going to get a quote on a thicker continuous UHMW strip for the upper sliding surface. This should last quite a while longer, though we may need to install it with sheet metal screws if we can't get adhesive-backed strips that thick.

cc @wosnik @iangagnon
Here's a closeup of the timing belt housing cross-section. The part that needs to be replaced is a 0.020" thick piece of adhesive-backed UHMW plastic film:

The tape is nominally 1245.5" long 4.75" wide, and the gap is designed to be 0.133" tall. We could probably step up to 0.060" thick strips or so. The width of the housing is 5.160", so we could go up to 5" or so wide on the new UHMW, though it's not necessary that it be wide.
The original pieces (there is a lower strip as well) cost $537.

Could get a quote from these guys: http://www.eplastics.com/slick_strips

Steps to perform the repair:

Remove all outer timing belt housing pieces. In the picture above, these are the aluminum angle sections (one is polycarbonate, as the wavemaker end) in the upper right. Note that it will be easiest to keep these in order, despite being theoretically identical.
Release belt tension. See https://marine.unh.edu/oelab/wiki/doku.php?id=tow_tank:maintenance:procedures#setting_drive_belt_preload
Remove timing belt tensioning clamp ends and move the belt out of the way of the upper sliding surface.
Remove timing belt tensioning bracket from carriage via the four 1/4-20 hex bolts.
Peel off old UHMW film.
Clean surface with mineral spirits or acetone.
Apply new UHMW film. This usually comes with pressure sensitive adhesive so adequate pressure will need to be applied. I used a small plastic roller the first time.
Re-install belt tensioning bracket at the carriage. Care should be taken to ensure the bracket is parallel with the carriage path.
Re-install belt tensioning clamps in the bracket and set preload according to https://marine.unh.edu/oelab/wiki/doku.php?id=tow_tank:maintenance:procedures#setting_drive_belt_preload
Re-install timing belt housing pieces.
Test to ensure the belt resonance is gone.

Another Idea I had a while back was to put small ball bearings on the tensioning clamps or their mounting bracket to keep them from rubbing on the sliding surface as well, which is likely a cause of some, if not all of the wear.
Maybe something like this: http://www.mcmaster.com/#2342k183/=111thav

I'm going to put together a drawing for this with part numbers on it. We will still need a quote for the UHMW though.

I can't seem to find the name of the manufacturer I bought the first rolls from--just the price. I think the ePlastics guys will make custom rolls though.

From @jcahern:

these guys will do 108' long roll, 5" width, 0.022" thick including acrylic adhesive for $436.  sound good?  they do 30 and 60mil but not in a length long enough.  they have it in stock so I can have it here next week.

http://catalog.cshyde.com/category/ategories-tapes-with-adhesive-uhmw-tapes-1

With a 5" wide tape, the new rolling ball bearings will be rolling on the tape--not sure if that's a good or a bad thing! It's probably okay.

@jcahern, Do you want to try to get a quote from eplastics? I have a feeling they can do 4.75" wide, 0.060" thick, and the proper length if we ask.

prob worth avoiding.
On 2/9/2016 4:21 PM, Pete Bachant wrote:

From @jcahern https://github.com/jcahern:
these guys will do 108' long roll, 5" width, 0.022" thick
including acrylic adhesive for $436. sound good? they do 30 and
60mil but not in a length long enough. they have it in stock so I
can have it here next week.

http://catalog.cshyde.com/category/ategories-tapes-with-adhesive-uhmw-tapes-1

With a 5" wide tape, the new rolling ball bearings will be rolling on
the tape--not sure if that's a good or a bad thing! It's probably okay.
—
Reply to this email directly or view it on GitHub
https://github.com/UNH-OE/wave-tow-tank/issues/70#issuecomment-182072621.Web
Bug from
https://github.com/notifications/beacon/AQWqWmeGnm73x0UrVyMhHNZF8gElbxm-ks5pik_sgaJpZM4GMpun.gif

Here's a drawing I whipped up for my proposed modifications:
Belt tensioner mods.PDF

do you think the bearings should be spring loaded so when they do
contact the rail there's some shock absorption?  maybe just some kind of
polymer wheel?
On 2/9/2016 7:58 PM, Pete Bachant wrote:

Here's a drawing I whipped up for my proposed modifications:
Belt tensioner mods.PDF
https://github.com/UNH-OE/wave-tow-tank/files/124050/Belt.tensioner.mods.PDF
—
Reply to this email directly or view it on GitHub
https://github.com/UNH-OE/wave-tow-tank/issues/70#issuecomment-182152105.Web
Bug from
https://github.com/notifications/beacon/AQWqWoD8A-oATfqGEws22InQ1I6jjZ_Rks5pioKbgaJpZM4GMpun.gif

I can't find any wheels small enough to fit in such a tight spot, and the plastic bearings I've seen are pretty low capacity and unsealed. The 6 x 6  beam that the tensioner mounts to actually does act like a spring as it twists, which is why I had to add the tie rod that connects the carriage face to the large I-beam. I actually think going with the bearings but getting the 5" wide tape would be optimal, so the wheels ride on a plastic surface. Let me know what you think.

And here's a snapshot of the rev 0 drawing for the sake of posterity:

cool, sounds good.  I'll keep looking for 0.060" thickness but if I
can't I'll just go with 0.020.  it can just be a maintenance item. but
if the tensioner scuffing problem is fixed 0.020 should last longer
anyway.  thanks for doing all this work, makes my job easy.
On 2/10/2016 8:34 AM, Pete Bachant wrote:

I can't find any wheels small enough to fit in such a tight spot, and
the plastic bearings I've seen are pretty low capacity and unsealed.
The 6 x 6 beam that the tensioner mounts to actually does act like a
spring as it twists, which is why I had to add the tie rod that
connects the carriage face to the large I-beam. I actually think going
with the bearings but getting the 5" wide tape would be optimal, so
the wheels ride on a plastic surface. Let me know what you think.
—
Reply to this email directly or view it on GitHub
https://github.com/UNH-OE/wave-tow-tank/issues/70#issuecomment-182377266.Web
Bug from
https://github.com/notifications/beacon/AQWqWhO1joUs0MyTr6eQtTczffk0DMN1ks5pizPrgaJpZM4GMpun.gif

Yeah, it will probably be fine. I think the tank got used a bit more often and at higher loads in my experiments than it will in the future.
That reminds me: I just migrated over a rough draft of the maintenance schedules we were attempting to establish for the tank. Feel free to edit if you have any ideas: https://github.com/UNH-OE/wave-tow-tank/wiki/Maintenance-schedule

does github have a messaging service?
On 2/10/2016 8:55 AM, Pete Bachant wrote:

Yeah, it will probably be fine. I think the tank got used a bit more
often and at higher loads in my experiments than it will in the future.
That reminds me: I just migrated over a rough draft of the maintenance
schedules we were attempting to establish for the tank. Feel free to
edit if you have any ideas:
https://github.com/UNH-OE/wave-tow-tank/wiki/Maintenance-schedule
—
Reply to this email directly or view it on GitHub
https://github.com/UNH-OE/wave-tow-tank/issues/70#issuecomment-182385822.Web
Bug from
https://github.com/notifications/beacon/AQWqWspGANhivjuEIPaP6IuwTa-b7wPAks5pizjEgaJpZM4GMpun.gif

Only via specific issues in the public issue tracker. We could create a Slack team for the lab for other messaging purposes.

@jcahern how did this go? I haven't been in the lab for a while. Is this issue ready to be closed?

Also a reminder to update the tow system status after this is finished: https://github.com/UNH-OE/wave-tow-tank/wiki

i think so.  covers are still off if you want to take a look.  i don't
see any issues.  it was in use last week but at slow speed. the side of
the flange towards the wave generator bends down and contacts the rail.
but it is covered with uhmw tape so there's not much friction.
On 3/14/2016 9:40 AM, Pete Bachant wrote:

@jcahern https://github.com/jcahern how did this go? I haven't been
in the lab for a while. Is this issue ready to be closed?
—
Reply to this email directly or view it on GitHub
https://github.com/UNH-OE/wave-tow-tank/issues/70#issuecomment-196314376.Web
Bug from
https://github.com/notifications/beacon/AQWqWg5SDhMkPtOB-YVAHAE2mmWIyCEOks5ptWVBgaJpZM4GMpun.gif

After tightening the button head screws for the tensioning clamps, did you give the large tensioning clamp nuts an extra quarter turn or so? That arches the ends of the plate up so they won't contact the sliding surface.
When do you think the timing belt guards will be back on? I will try to stop in before and take a look.

I'll give that a shot.  I wanted to retension after use anyway.
guards can go back on whenever.  prob this week.
On 3/14/2016 10:22 AM, Pete Bachant wrote:

After tightening the button head screws for the tensioning clamps, did
you give the large tensioning clamp nuts an extra quarter turn or so?
That arches the ends of the plate up so they won't contact the sliding
surface.
When do you think the timing belt guards will be back on? I will try
to stop in before and take a look.
—
Reply to this email directly or view it on GitHub
https://github.com/UNH-OE/wave-tow-tank/issues/70#issuecomment-196328677.Web
Bug from
https://github.com/notifications/beacon/AQWqWi3O654IrA7cMas8yUONgW2Q4HeHks5ptW8ZgaJpZM4GMpun.gif

pete,
let me know when you inspect the tank and i'll put the covers back on.
On 3/14/2016 10:22 AM, Pete Bachant wrote:

After tightening the button head screws for the tensioning clamps, did
you give the large tensioning clamp nuts an extra quarter turn or so?
That arches the ends of the plate up so they won't contact the sliding
surface.
When do you think the timing belt guards will be back on? I will try
to stop in before and take a look.
—
Reply to this email directly or view it on GitHub
https://github.com/UNH-OE/wave-tow-tank/issues/70#issuecomment-196328677.Web
Bug from
https://github.com/notifications/beacon/AQWqWi3O654IrA7cMas8yUONgW2Q4HeHks5ptW8ZgaJpZM4GMpun.gif

Sounds good. I probably won't make it over there until Friday afternoon/evening though. Lots of thesis writing!

good luck.  I'll leave it off.
On 3/15/2016 10:41 AM, Pete Bachant wrote:

Sounds good. I probably won't make it over there until Friday
afternoon/evening though. Lots of thesis writing!
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/UNH-OE/wave-tow-tank/issues/70#issuecomment-196849321Web
Bug from
https://github.com/notifications/beacon/AQWqWmiKKNPDBXYadCrQXCSZW_3eDJtoks5ptsUWgaJpZM4GMpun.gif

Qualitative observation: At low speeds (~0.2-0.3 m/s) the belt/carriage runs much quieter that it used to.
From: jcahern<EMAIL_ADDRESS>Sent: Tuesday, March 15, 2016 11:53 AM
To: UNH-OE/wave-tow-tank
Cc: Wosnik, Martin
Subject: Re: [wave-tow-tank] Replace upper belt sliding surface (#70)
good luck. I'll leave it off.
On 3/15/2016 10:41 AM, Pete Bachant wrote:

Sounds good. I probably won't make it over there until Friday
afternoon/evening though. Lots of thesis writing!
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/UNH-OE/wave-tow-tank/issues/70#issuecomment-196849321Web
Bug from
https://github.com/notifications/beacon/AQWqWmiKKNPDBXYadCrQXCSZW_3eDJtoks5ptsUWgaJpZM4GMpun.gif

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/UNH-OE/wave-tow-tank/issues/70#issuecomment-196891962

I just got a chance to check out the repair and it looks like you guys did a great job. I did adjust one thing though. After tightening the button head screws on the tensioning clamps, I tightened the large ~23 mm nuts about an extra half turn so the plate is somewhat concave, so the ends don't touch:

I'd say it's ready to go all back together, then we can close this issue and set the tow system status back to operational!

Perfect. Thanks Pete.
On Mar 18, 2016, at 6:12 PM, "Pete Bachant" <notifications<EMAIL_ADDRESS>wrote:
I just got a chance to check out the repair and it looks like you guys did a great job. I did adjust one thing though. After tightening the button head screws on the tensioning clamps, I tightened the large ~23 mm nuts about an extra half turn so the plate is somewhat concave, so the ends don't touch:
[image]https://cloud.githubusercontent.com/assets/4604869/13893447/ce3e3262-ed34-11e5-80aa-d549429b92bf.png
I'd say it's ready to go all back together, then we can close this issue and set the tow system status back to operational!

You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHubhttps://github.com/UNH-OE/wave-tow-tank/issues/70#issuecomment-198563004

May want to do some more thorough testing, but since the surface is replaced, I'm going to close this issue and update the status.

Also added an item to the table at https://github.com/UNH-OE/wave-tow-tank/wiki/Maintenance,-repairs,-changes.


support default gradle version coming with RN

Project created by react-native init .. won't compile because implementation() is not supported by specified gradle version

This is an invalid merge. implementation should be used everywhere. The react-native init is outdated. but you should update it yourself. No need to revert to compile. Compile is depricated

This library is built to work with react-native, so in my opinion it should follow react-native configuration and not force users to update gradle.
Even though you will be warned that compile is depricated during compilatation if you update your gradle, it will still compile the project, but with older (RN default) version and using implementation it won't.

In my opinion if you build a library you don't want to use outdated versions. React native init istself is outdated as well. Where I work we never use react native init. we build our own template project. This way the template project is never outdated


Update App authentication paragraph

Specified an unclear "them" that refered to an app's credential and fixed an typo (apps' VS app's)

Many thanks!

From: Frikky @.>
Sent: Wednesday, October 26, 2022 2:05:38 PM
To: Shuffle/Shuffle-docs @.>
Cc: Ibrahimous @.>; Author @.>
Subject: Re: [Shuffle/Shuffle-docs] Update App authentication paragraph (PR #146)
I'm not sure whether this makes it more or less clear tbh. I guess there is something to be said with "credentials" vs "configuration" being used anonymously here, which may be wrong.
Either way - thanks! Merging it in :)
—
Reply to this email directly, view it on GitHubhttps://github.com/Shuffle/Shuffle-docs/pull/146#issuecomment-1291931944, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AA2IBTNMZFLMLBHEKPAYWBTWFENBFANCNFSM6AAAAAAROXCVGE.
You are receiving this because you authored the thread.Message ID: @.***>


[Question] Security policy

Hi,
I see that there is no security policy listed currently for this project. Is there any such security policy that exists and is being used for this project development?
For example:
https://www.microsoft.com/en-us/securityengineering/sdl/practices
Thanks!

@milfordjosh
Hi,
Thanks for your question. You can find Esri's overall security policy at https://trust.arcgis.com, and if you have any specific concerns they can be reported at https://trust.arcgis.com/en/security-concern/.
We'll investigate and determine the appropriate content to specifically list for this, and other similar projects.
Thanks

Thank you for the quick answer. I was able to find exactly the information I needed on that page, including this pdf:
https://downloads.esri.com/RESOURCES/ENTERPRISEGIS/Esri_SDLC.pdf
Very much appreciated!


Issue #DP-1188 fix: Select role is displayed as an option in the drop down values

Added changes to other PR


Double Kasra character with Omar Naskh font

Have a problem which is related to nested lookups format 6.3 sometimes certain glyphs get duplicated for no reason.

Fixed by last commit: 4f0f77a2ea9298b339921f7e8b5890a29eaed9c2.


test integration

Was curious if this works when submitting a PR from a fork as opposed to a branch on the upstream repo.