Wording issue on instructions

Challenge http://www.freecodecamp.com/challenges/waypoint-use-the-bootstrap-grid-to-put-elements-side-by-side has an issue. Please describe how to reproduce it, and include links to screen shots if possible.
Second issue to solve states "Each of your Bootstrap buttons should be wrapped within its own a div element with the class "col-xs-4".  The word "a" should be removed.  It should read "wrapped within its own div"...

Fixed, opened a pull request - https://github.com/FreeCodeCamp/freecodecamp/pull/1114


Peaceful Essence Uncraftable!

Issue description:
Peaceful Essence is just Uncraftable.
Different Mob names...
Steps to reproduce:

Versions:

Minecraft: 1.12.2
Forge: <IP_ADDRESS>27
McJtyLib: mcjtylib-1.12-2.6.5
RFTools: rftools-1.12-7.30
OptiFine: 1.12.2_HD_U_C8
Modpack: FTB Presents Direwolf20 1.12

Your RFTools version is outdated, and a similar bug has been fixed since the version you're on was released. See if updating (and getting new syringes) makes it work.


Can we plot tumor ID in PlotOncogenicPathways

The plot will be better visualized with tumor barcode in the bottom

Hi,
Thank you for using maftools. I have pushed a commit to fix it. You can use arguments showTumorSampleBarcodes and SampleNamefontSize to annotate plots with sample names. You will have to install it from GitHub.
Please let me know if this works for you.

Hi,
Thank you for using maftools. I have pushed a commit to fix it. You can use arguments showTumorSampleBarcodes and SampleNamefontSize to annotate plots with sample names. You will have to install it from GitHub.
Please let me know if this works for you.

Thanks a lot！It works！

Would naming the parameter sampleNameFontSize make the casing consistent with showTumorSampleBarcodes and therefore easier for users to remember without having to refer to documentation? It would also be nice if titv could be TiTv, to make it similar to plotTiTv (science journals also capitalise the Ts).


SwaggerResponseAttribute - Make Type optional

Suggested feature: For some response codes, there is no data to be returned. The SwaggerResponse should be able to be created with just an HttpStatusCode and a description. So instead of:
[SwaggerResponse(HttpStatusCode.NotFound, typeof(object), Description = "Not Found")]
This (or similar):
[SwaggerResponse(HttpStatusCode.NotFound, Description = "Not Found")]
It wasn't clear to me in the beginning that typeof(object) should be used when there is no explicit type.

Use typeof(void) in the case of no response

[ ] Add new ctors without type parameter and set type to typeof(void)

Being on the other side of this now and knowing how to do it, I think it's a minor inconvenience. typeof(void) isn't something that I've had to use frequently, so I suspect for a lot of people, it's not going to come to mind to use it.
I'm trying to think of what the downsides are to automatically setting the type but with as green as I am to all of this, I'd just be guessing. It definitely feels like a sane default though.

Its documented here:
https://github.com/RSuter/NSwag/wiki/WebApiToSwaggerGenerator#specify-the-response-type-of-an-action
And i dont like it to be implicit because it may confuse users as it would replace the actual response type and some people might think that the attribute with just a status code only changes the status code but not the method response type..

I do remember scanning over that now, but I took that more in the context of forcing a 204, but now that I read it again, I see it clearer.
I made a minor edit to the page to show that usage. Feel free to backout if need be.
Thanks for the great project!


What do the versions mean?

Hi,
when I read versions in the format of x.y.z I assume semantic versioning (maybe I shouldn't?). But it seems gopass introduces quite a few breaking changes in new minor version.
So, what do gopass' versions mean?
Background is that we rely heavily on gopass in a team of ~40 people for our infrastructure, system, and application secrets. We maintain our own homebrew repo which provides a specific version of various tools, gopass included. The other day I updated that version from 1.8.6 to 1.9.2 assuming everything would just continue working. But we ran at least into issue https://github.com/gopasspw/gopass/issues/1353 which is kind of a bummer because now we'll have to update a lot of repos and communicate that to a lot of people, or we go back and are stuck with 1.8 for now.

This is a good question. Thanks for asking.
First of all gopass is using semantic versioning because that's what a lot of tools, e.g. goreleaser expect.
We try not adhere to the spirit of semantic versioning, i.e. no behavioral changes in patch releases, no breaking changes in minor releases.
But what's a breaking change? Any change might break someones workflow.
So I'd say a breaking change means changing the previously defined behaviour.
However we never did a clean definition so far. This is something we started to address while working on the 1.10.0 release.
Now you'll find documentation / specification for all supported CLI commands in docs/commands.
We've also started to define our core use cases - however that work isn't finished, yet.
So I'd suggest you look at the existing command documentation and file issues if you notice any discrepancies between what's documented and actual behaviour on the on hand as well as discrepancies between your expectations and the specification on the other hand.
Then we can start to discuss specific details.
One thing we should do to resolve this issue is to document how we define our versioning scheme.

Oh, and btw. what's the problem with #1353 exactly?
Maybe you want to re-open that issue if it's still affecting you or file a new one detailing your conerns.
But keep in mind that a lot ton of issues were fixed in 1.10.0. Did you try that one?

Thanks for responding so quickly! There are a few things to unpack, I hope I manage to address them all.

We try to adhere to the spirit of semantic versioning, i.e. no breaking changes in patch releases, no major architectural changes in minor releases.

When you say "semantic versioning", are you referring to semver.org or a versioning schema that adheres to your own semantics? Either is fine, I'd just like to be on the same page.
The semantics of minor releases you're describing don't make much sense to me. In my understanding of software, architectural changes don't necessarily change or break the API or UI. So, when would those be okay?
And isn't a new secrets format a major architectural change? Especially because you're suggesting in the changelog:

you might want to run gopass config mime false before performing any kind of write operation on the password store. Otherwise mutated secrets will be written using the new native gopass MIME format and might not be readable from other implementations.

That sounds pretty disruptive to me. Because - like in our case - when some people update to 1.10.0 and others are still on 1.8.6 things are bound to break for them. You could argue that people should always keep their tools up-to-date but with a lot of people this is hard to coordinate. For scenarios like this it'd be good to announce such changes via the tool itself, as in, you release a version that keeps the behavior but announces its deprecation. Much like in libraries and frameworks that log deprecation warnings but keep that behavior for a few versions.

However we never did a clean definition so far. This is something we started to address while working on the 1.10.0 release.
We've also started to define our core use cases - however that work isn't finished, yet.

That's a very good thing. It's a bit unfortunate that gopass' versioning started with 1.0.0. According to semver.org it would have been better to start with 0: Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable. But it is what it is now.
So, all that being said, why not go to 2.0.0 instead of 1.10.0?

Oh, and btw. what's the problem with #1353 exactly?
Maybe you want to re-open that issue if it's still affecting you or file a new one detailing your conerns.
But keep in mind that a lot ton of issues were fixed in 1.10.0. Did you try that one?

It's just something that accidentally broke people's setup, ours included. We'll find a way around it but not by updating to 1.10.0 because I'm too afraid it'll break too many things for too many people and too many repos containing scripts using gopass.

I'm referring to semver.org. But we never wanted gopass to be used as a library and didn't hold ourselves accountable to the strict versioning style.
Maybe we should still be on a major version of 0. I'm not sure.
Btw. we started interally with a major version of 0.
The upgrade path for the new secrects format is indeed a bit rough. That wasn't planned very well and I wonder if it's to late to revert the default to not using the new format, yet. We still support all previous formats, but you're right. Users of older versions will get into trouble. That wasn't intentional.
Maybe 1.10.0 should have been a 2.0.0 relase. But I guess that's too late now.
I'd appreciate if you could help us (e.g. by providing feedback) making the next 1.10.x releases one you'd be willing  to upgrade to. I'm sure others would appreciate that, too.

For #1353 the problem actually stem from the fact that autoclip should not have influenced show and it should now have been fixed in #1513
1.10 should actually be easier to migrate to than 1.9.2, I think since we corrected a lot of bugs / misbehaviour that were in 1.9.2 since it wouldn't suffer from #1353 for instance.
If you have a big team using gopass, we would be really super happy to get as much feedback as you can give us :)

Thank you for the insight, @dominikschulz. And thanks for the info and encouragement, @AnomalRoil. Sorry for the late response. I've moved on to another project, so I can't really support my old project with upgrading gopass anymore, I hope when they try that they'll find this thread.
Regarding feedback, I do have a few things (this is for version 1.8.6). I don't know if this thread is the right place, if not I'm happy to repost somewhere else:

Over time, years in our case, the store becomes almost unmanageable big, both in number of secrets (I'll get to some reasons later) and in storage size, gigabytes in our case. Adding new recipients takes half an hour with reencrypting all the secrets (only recently we discovered the concurrency setting). It became a gamble because - I don't know why exactly - we had cases where someone was in the process of adding a new recipient which then failed because another person had updated the store in some way in the meantime. It had something to do with the Git commits, I think.  But that means you lose some of the audit trail, not tragic in our case but also not ideal, I think.
I mentioned the sheer number of secrets. We ended up with quite a few duplicated entries because some secrets, like certificates, were used in multiple places. This is definitely partly a problem on the user side, we should have been more disciplined or strict or should've come up with a policy of how to organize secrets. But maybe there's a way the tool could assist.
Discoverability was another issue, and also a reason why people created duplicates. But simply finding credentials for something was difficult sometimes because the creators chose a name that was intuitive for them but not for others. So, maybe metadata like tags could help here when they are included in the search. The new format might enable this.
Another super helpful feature would be secret deprecation or expiry. There are multiple reasons for this. The obvious one is that credentials should be changed now and then, especially considering that people, like me, leave the team/project or the company altogether (such an event should trigger a complete credentials rotation anyway but that's a whole different story). Another reason is that sometimes credentials simply become obsolete, we've accumulated a lot of zombie credentials in our store over time. And there was not really a way for us to know which ones are still used. At some point I even thought about implementing a wrapper that logs accesses, and let people install and use that instead of gopass directly. Such a feature would also help with the other things I mentioned before.
Something that came up recently was that we couldn't add a secret because one recipient's key had expired. For some reason I didn't have to deal with that in all my time in the project before. But when I had to I became quite confused, and it's probably partly because I don't fully understand the concepts behind gopass, or gpg for that matter. Fortunately we could quickly contact that person, not a tech-savvy one btw., and helped them update their key. But what if that person had been on holiday? After updating the key and syncing it via gpg we tried to update the recipient, or rather add them again (what does update do?). But it said that the recipient existed already. What's the workflow in this case? Eventually we simply removed and re-added them which meant that we had to reencrypt all secrets again. I guess that's how it's supposed to work, is it? It was quite confusing though.

Maybe some of these things have been mentioned by other people in other issues before, I didn't check. It's just the major pain points I can remember from working with it in a bigger team for almost 2.5 years.
All of this being said, I know that gopass solves a difficult problem and I'm aware that good security often comes at the cost of convenience. Some things I mentioned are just rough edges that can be polished. But maybe there's also a deeper issue with Git as the default backend, I don't know, just guessing.

Thank you very much for sharing your experience with us. Actually with 1.11.0 some breaking changes have been rolled back and other issues have been fixed, so upgrading from older versions should have become feasible again.
gopass was never designed for huge teams or huge repo sizes. If most people are only reading from the repo having three digit number of recipients should be OK, but anything more than that is not something we can or want to support. For that you'd need a different system. I have worked with decent web-based credential managers, but of course they come with their own set of risks and no decent open-source ones seem to exist (and commercial ones are not an option for me in this use case).
Expring recipient keys is one of the issues that come with using gpg. I've tried to get rid of that, but too many people need use gpg so we're stuck with that. We'll need to figure out the best option to deal with that.

Thank you very much for sharing your experience with us. Actually with 1.11.0 some breaking changes have been rolled back and other issues have been fixed, so upgrading from older versions should have become feasible again.
gopass was never designed for huge teams or huge repo sizes. If most people are only reading from the repo having three digit number of recipients should be OK, but anything more than that is not something we can or want to support. For that you'd need a different system. I have worked with decent web-based credential managers, but of course they come with their own set of risks and no decent open-source ones seem to exist (and commercial ones are not an option for me in this use case).
Expring recipient keys is one of the issues that come with using gpg. I've tried to get rid of that, but too many people need use gpg so we're stuck with that. We'll need to figure out the best option to deal with that.

@dAnjou Please note that many of these issues should have been addressed meanwhile and we tried to properly document our promises around API stability and what versions mean. Also we have taken a much more cautionous approach wrt. breaking changes will be more careful going forward. The catch is that you'll have to upgrade to 1.11.0 (or better: 1.12.0+) to get there.
Feel free to re-open in case this is still and issue that needs to be discussed.


when i create a file there isn't the fold the first time

I don't know if it's because i use templater
https://github.com/Benature/obsidian-metadata-hider/assets/105045271/077b2b59-eec9-40ed-a1f1-dbc14af0f205

Sorry, I don't get this issue. What do you mean by "the fold"?


package install error

Hey,
I get this error when trying to install the betfairlightweight package from the mac terminal:
ERROR: Could not build wheels for ujson which use PEP 517 and cannot be installed directly
Any ideas?
Cheers!

Can you try the following:
pip install --upgrade pip setuptools wheel


Release v0.11.0

Adjust token expiry window to 40 seconds because of Azure (#170).
Use same logic as Go SDK for DatabricksConfig.isAzure() (#174).

API Changes:

Added attributes, count, excludedAttributes, filter, sortBy, sortOrder, and startIndex fields for com.databricks.sdk.service.iam.GetAccountUserRequest and com.databricks.sdk.service.iam.GetUserRequest.
Added schemas field for com.databricks.sdk.service.iam.Group, com.databricks.sdk.service.iam.ListGroupsResponse, com.databricks.sdk.service.iam.ListServicePrincipalResponse, com.databricks.sdk.service.iam.ListUsersResponse, com.databricks.sdk.service.iam.ServicePrincipal, and com.databricks.sdk.service.iam.User.
Added com.databricks.sdk.service.iam.GetSortOrder, com.databricks.sdk.service.iam.GroupSchema, com.databricks.sdk.service.iam.ListResponseSchema, com.databricks.sdk.service.iam.ServicePrincipalSchema, and com.databricks.sdk.service.iam.UserSchema class.
Added webhookNotifications field for com.databricks.sdk.service.jobs.SubmitTask.
Added workspaceClient.apps() service and related classes.
Added accountClient.networkPolicy() service and related classes.

OpenAPI SHA: 5903bb39137fd76ac384b2044e425f9c56840e00, Date: 2023-10-23
Dependency updates:

Bump org.junit:junit-bom from 5.9.3 to 5.10.0 (#124).
Bump org.slf4j:slf4j-api from 2.0.7 to 2.0.9 (#146).
Bump org.slf4j:slf4j-reload4j from 2.0.7 to 2.0.9 (#147).
Bump org.apache.maven.plugins:maven-javadoc-plugin from 3.5.0 to 3.6.0 (#156).

Integration tests passed, merging.


Push the snapshot artifacts to the Sonatype repo

Sonatype credentials (the same as for their Jira) are required to push the artifacts to the Maven repository.
Please test that this works.
You need Java 7+ SDK, git and Maven 3 installed.
Add the credentials to ~/.m2/settings.xml:
<settings>
  ...
  <servers>
    <server>
      <id>ossrh</id>
      <username>your-jira-id</username>
      <password>your-jira-pwd</password>
    </server>
  </servers>
  ...
</settings>

Then run this:
git clone git@github.com:CurrencyCloud/currencycloud-java.git
cd currencycloud-java
mvn clean deploy

Pushed to Sonatype Nexus:  0.7-SNAPSHOT

https://oss.sonatype.org/#nexus-search;quick~currencycloud-java

<dependency>
  <groupId>com.currencycloud.currencycloud-java</groupId>
  <artifactId>currencycloud-java</artifactId>
  <version>0.7-SNAPSHOT</version>
</dependency>

Great, thanks.


pingAll function

Why the pingAll function takes the urls from the configuration file, instead of calling every other single function?
Right now the pingAll method does not pings on PingOMatic?

Good notice. Thank you. I will fix it in the next release.

Thank you for this package, have a good day!

@angelocala94 i've made changes.. Please update.
Currently I just added pingomatic manually, because it has different logic than other services.
TODO: refactor them in proper way in the future.
Thank you again for your feedback.

Many thanks!


Cache stores the app BEFORE "build" step

That causes we are unable to cache anything we generate in the build action, eg assets.
Expected behaviour: on the initial build, cache the app AFTER build step.
BTW: everything else seem to work very nice and smoothly :+1:

You're right it shouldn't affect public folder. Seems like there's something wrong with yarn cache in our case. Take a look:
1). seems like everything is ok after the 1st build (yarn packages cached, assets cached) :+1:
2). but... at the 2nd build after yarn cache is restored it "builds" something again (this is problably why our assets got recompiled)
[4/4] Building fresh packages...
Done in 13.75s.

3). then when yarn install got executed for the second time (by our assets:precompile's init step)
[1/4] Resolving packages...
success Already up-to-date.
Done in 0.63s.

it looks like it should actually in (2)
The consequence step (2) does something, our assets:precompile reads as "packages got changed" and despite it was restored from the cache it triggers the recompilation task.
cypress.yml https://gist.github.com/mleszcz/16d80ec77e675d0b302861843576ff6e
1st build

2nd build

Thanks A LOT for helping us.

Closing, based on previous comment that the issue is resolved.


SplObjectStorage vs. Array: which is better for storage of connections with frequently updated added properties?

Hi,
I am thinking of adding some additional information to the ConnectionInterface object once a new connection is open, such as last time a message is sent in by that connection/client, and update that added property frequently.
SplObjectStorage uses hash of the entire object as key, change of object itself will result in a new key. Given this, is SplObjectStorage is still the preferred/better way to store connection/client information?
Thanks.

There are some general discussion about SplObjectStorage vs. Array. I will go with array.


[bug] pouch images failed : unknown image config media type application/octet-stream

Ⅰ. Issue Description
we encounter an error when execute pouch images :
#pouch images
Error: failed to get image list: {"message":"unknown image config media type application/octet-stream"}

when use ctr tool to list images, we can get a warn info, but still works:
#ctr --address /var/run/containerd.sock images ls
WARN[0000] encountered unknown type application/octet-stream; children may not be fetched
WARN[0000] encountered unknown type application/octet-stream; children may not be fetched
REF                                                                                TYPE                                                 DIGEST                                                                  SIZE    PLATFORMS   LABELS
reg.docker.alibaba-inc.com/ali/os:5u7                                                application/vnd.oci.image.manifest.v1+json           sha256:81e93aa4f0c8acb2c689a5b7186aac4e1d315922bafb3da36278661f55a56bd4 2.1 GiB linux/amd64 -

Ⅱ. Describe what happened
Ⅲ. Describe what you expected to happen
even encounter an error, we should still can list images
Ⅳ. How to reproduce it (as minimally and precisely as possible)

Ⅴ. Anything else we need to know?
Ⅵ. Environment:

pouch version (use pouch version):
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

Duplicate with #1583


Sample: ERR during playback of out.wav

I used the makefile to build this software with this version of gcc (i think it came with brew):
Seppis-MacBook-Air:EasyVolcaSample seppi$ gcc -v
Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/c++/4.2.1
Apple LLVM version 10.0.1 (clang-1<IP_ADDRESS>)
Target: x86_64-apple-darwin18.7.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin

I then used ffmpeg to convert a small sample of quacking to wav, and then used the EasyVolcaSample binary to create an out.wav file.
When I run the out.wav file connected to my volca sample, I get an ERR until I press function.
Attached is the mp3, the converted wav and the out.wav file that I am attempting to use.
I was able to use the korg factory sample file to reset my device, so I am pretty sure it is not a problem there.
The firmware of the volca shows: 1.30 P0.09 51.00 which makes believe it is firmware version 1.30
I am going to update to 1.42 and try again!
Archive.zip

I have updated my device to 1.42 and still have the same problem.

I notice that the *.c files are the same (if not newer) than the one from korg. I will create a ticket there.


Can't spin up a small machine on Pangeo staging hub

Description
I was working on #655 and wanted to login to the staging hub in order to test if I had successfully granted access to the Pangeo requestor-pays data. From the profile list I selected "small machine", but my server never comes up.
Error logs from the JupyterHub page:

Output of `kubectl describe pod jupyter-sgibson91`
Name:                 jupyter-sgibson91
Namespace:            staging
Priority:             0
Priority Class Name:  staging-default-priority
Node:                 <none>
Labels:               app=jupyterhub
                      chart=jupyterhub-1.1.3
                      component=singleuser-server
                      heritage=jupyterhub
                      hub.jupyter.org/network-access-hub=true
                      hub.jupyter.org/network-access-proxy-http=true
                      hub.jupyter.org/servername=
                      hub.jupyter.org/username=sgibson91
                      release=staging
Annotations:          hub.jupyter.org/username: sgibson91
Status:               Pending
IP:
IPs:                  <none>
Init Containers:
  volume-mount-ownership-fix:
    Image:      busybox
    Port:       <none>
    Host Port:  <none>
    Command:
      sh
      -c
      id && chown 1000:1000 /home/jovyan && ls -lhd /home/jovyan
    Environment:  <none>
    Mounts:
      /home/jovyan from home (rw,path="sgibson91")
      /var/run/secrets/kubernetes.io/serviceaccount from user-sa-token-mxwp5 (ro)
Containers:
  notebook:
    Image:      pangeo/pangeo-notebook:bcfacc5
    Port:       8888/TCP
    Host Port:  0/TCP
    Args:
      jupyterhub-singleuser
      --ip=<IP_ADDRESS>
      --port=8888
      --SingleUserNotebookApp.default_url=/lab
    Limits:
      cpu:     2
      memory:<PHONE_NUMBER>
    Requests:
      cpu:     1
      memory:<PHONE_NUMBER>
    Environment:
      CPU_GUARANTEE:                          1.0
      CPU_LIMIT:                              2.0
      DASK_GATEWAY__ADDRESS:                  http://proxy-public/services/dask-gateway
      DASK_GATEWAY__AUTH__TYPE:               jupyterhub
      DASK_GATEWAY__CLUSTER__OPTIONS__IMAGE:  {JUPYTER_IMAGE_SPEC}
      DASK_GATEWAY__PROXY_ADDRESS:            gateway://traefik-staging-dask-gateway.staging:80
      DASK_GATEWAY__PUBLIC_ADDRESS:           /services/dask-gateway/
      JPY_API_TOKEN:                          2e1b1dd265ce40c0a7cdc598867fee0e
      JUPYTERHUB_ACTIVITY_URL:                http://hub:8081/hub/api/users/sgibson91/activity
      JUPYTERHUB_ADMIN_ACCESS:                1
      JUPYTERHUB_API_TOKEN:                   2e1b1dd265ce40c0a7cdc598867fee0e
      JUPYTERHUB_API_URL:                     http://hub:8081/hub/api
      JUPYTERHUB_BASE_URL:                    /
      JUPYTERHUB_CLIENT_ID:                   jupyterhub-user-sgibson91
      JUPYTERHUB_HOST:
      JUPYTERHUB_OAUTH_CALLBACK_URL:          /user/sgibson91/oauth_callback
      JUPYTERHUB_SERVER_NAME:
      JUPYTERHUB_SERVICE_PREFIX:              /user/sgibson91/
      JUPYTERHUB_USER:                        sgibson91
      JUPYTER_IMAGE:                          pangeo/pangeo-notebook:bcfacc5
      JUPYTER_IMAGE_SPEC:                     pangeo/pangeo-notebook:bcfacc5
      MEM_GUARANTEE:<PHONE_NUMBER>
      MEM_LIMIT:<PHONE_NUMBER>
    Mounts:
      /home/jovyan from home (rw,path="sgibson91")
      /home/jovyan/shared from home (ro,path="_shared")
      /home/jovyan/shared-readwrite from home (rw,path="_shared")
      /usr/local/etc/jupyter/jupyter_notebook_config.json from files (rw,path="jupyter_notebook_config.json")
      /var/run/secrets/kubernetes.io/serviceaccount from user-sa-token-mxwp5 (ro)
Conditions:
  Type           Status
  PodScheduled   False
Volumes:
  home:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  home-nfs
    ReadOnly:   false
  files:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  singleuser
    Optional:    false
  user-sa-token-mxwp5:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  user-sa-token-mxwp5
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  node.kubernetes.io/instance-type=n1-standard-2
Tolerations:     hub.jupyter.org/dedicated=user:NoSchedule
                 hub.jupyter.org_dedicated=user:NoSchedule
                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                 node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason             Age    From                    Message
  ----     ------             ----   ----                    -------
  Warning  FailedScheduling   4m24s  staging-user-scheduler  0/2 nodes are available: 2 node(s) didn't match node selector.
  Warning  FailedScheduling   4m24s  staging-user-scheduler  0/2 nodes are available: 2 node(s) didn't match node selector.
  Normal   NotTriggerScaleUp  4m22s  cluster-autoscaler      pod didn't trigger scale-up: 4 node(s) had taint {k8s.dask.org_dedicated: worker}, that the pod didn't tolerate, 4 node(s) didn't match Pod's node affinity, 1 Insufficient memory

Also, the hub pod is having difficulty with its readiness probe for some reason.
Output of `kubectl describe pod hub-*`
Name:                 hub-766bbc7848-cm469
Namespace:            staging
Priority:             0
Priority Class Name:  staging-default-priority
Node:                 gke-pangeo-hubs-cluster-core-pool-b7fdb3c5-x0hz/<IP_ADDRESS>
Start Time:           Tue, 07 Sep 2021 13:20:05 +0100
Labels:               app=jupyterhub
                      component=hub
                      hub.jupyter.org/network-access-proxy-api=true
                      hub.jupyter.org/network-access-proxy-http=true
                      hub.jupyter.org/network-access-singleuser=true
                      pod-template-hash=766bbc7848
                      release=staging
Annotations:          checksum/config-map: 390369c2af173ec8d3c020b3c4c6718fc041fe7e9e565f65580c0e348c8d92fb
                      checksum/secret: 142644abf7719d61f74984c73a4c755a9a6b714dc2d9d6ae8085bdf6f61f8b5a
                      cni.projectcalico.org/podIP: <IP_ADDRESS>/32
                      cni.projectcalico.org/podIPs: <IP_ADDRESS>/32
Status:               Running
IP:                   <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/hub-766bbc7848
Init Containers:
  templates-clone:
    Container ID:  containerd://11b059c859c075b07394e2966970507e6f6dd9aad95bde31102e2427d20328df
    Image:         alpine/git
    Image ID:      docker.io/alpine/git@sha256:0590372ee83d4d0ff4f08f8d2a98b0ba413d911a2e89c1d3418a1fed9a66337c
    Port:          <none>
    Host Port:     <none>
    Args:
      clone
      --
      https://github.com/2i2c-org/pilot-homepage
      /srv/repo
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Tue, 07 Sep 2021 13:20:23 +0100
      Finished:     Tue, 07 Sep 2021 13:20:24 +0100
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /srv/repo from custom-templates (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from hub-token-vf7lt (ro)
Containers:
  templates-sync:
    Container ID:  containerd://c46ec77698ac7d254fdbb967abf725132486738fb77de0e122a4c15d52d5f628
    Image:         alpine/git
    Image ID:      docker.io/alpine/git@sha256:0590372ee83d4d0ff4f08f8d2a98b0ba413d911a2e89c1d3418a1fed9a66337c
    Port:          <none>
    Host Port:     <none>
    Command:
      /bin/sh
    Args:
      -c
      while true; do git fetch origin;
      if [[ $(git ls-remote --heads origin staging | wc -c) -ne 0 ]]; then
          git reset --hard origin/staging;
      else
          git reset --hard origin/master;
      fi
      sleep 5m; done

    State:          Running
      Started:      Tue, 07 Sep 2021 13:20:25 +0100
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /srv/repo from custom-templates (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from hub-token-vf7lt (ro)
  hub:
    Container ID:  containerd://ccb3598fcc4ce99e7c09812425d4492c3b50803bfd4a20ac6c924dbf6ae8844c
    Image:         quay.io/2i2c/pilot-hub:0.0.1-n1159.h5b045cd
    Image ID:      quay.io/2i2c/pilot-hub@sha256:20c687d90c30c723c17e676ea32d84a093a4179da20d788f8f0184a38107da4d
    Port:          8081/TCP
    Host Port:     0/TCP
    Args:
      jupyterhub
      --config
      /usr/local/etc/jupyterhub/jupyterhub_config.py
      --upgrade-db
    State:          Running
      Started:      Tue, 07 Sep 2021 13:20:25 +0100
    Ready:          True
    Restart Count:  0
    Limits:
      memory:  2Gi
    Requests:
      cpu:      10m
      memory:   128Mi
    Liveness:   http-get http://:http/hub/health delay=300s timeout=3s period=10s #success=1 #failure=30
    Readiness:  http-get http://:http/hub/health delay=0s timeout=1s period=2s #success=1 #failure=1000
    Environment:
      PYTHONUNBUFFERED:        1
      HELM_RELEASE_NAME:       staging
      POD_NAMESPACE:           staging (v1:metadata.namespace)
      CONFIGPROXY_AUTH_TOKEN:  <set to the key 'hub.config.ConfigurableHTTPProxy.auth_token' in secret 'hub'>  Optional: false
    Mounts:
      /srv/jupyterhub from pvc (rw)
      /usr/local/etc/jupyterhub-configurator/00-default.schema.json from files (rw,path="configurator-schema-default")
      /usr/local/etc/jupyterhub/config/ from config (rw)
      /usr/local/etc/jupyterhub/jupyterhub_config.py from config (rw,path="jupyterhub_config.py")
      /usr/local/etc/jupyterhub/secret/ from secret (rw)
      /usr/local/etc/jupyterhub/z2jh.py from config (rw,path="z2jh.py")
      /usr/local/share/jupyterhub/custom_templates from custom-templates (rw,path="templates")
      /usr/local/share/jupyterhub/static/extra-assets from custom-templates (rw,path="extra-assets")
      /var/run/secrets/kubernetes.io/serviceaccount from hub-token-vf7lt (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  config:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      hub
    Optional:  false
  secret:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  hub
    Optional:    false
  files:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  hub
    Optional:    false
  custom-templates:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  pvc:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  hub-db-dir
    ReadOnly:   false
  hub-token-vf7lt:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  hub-token-vf7lt
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  hub.jupyter.org/node-purpose=core
Tolerations:     hub.jupyter.org/dedicated=core:NoSchedule
                 hub.jupyter.org_dedicated=core:NoSchedule
                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                 node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason                  Age                From                                   Message
  ----     ------                  ----               ----                                   -------
  Normal   Scheduled               2m22s              gke.io/optimize-utilization-scheduler  Successfully assigned staging/hub-766bbc7848-cm469 to gke-pangeo-hubs-cluster-core-pool-b7fdb3c5-x0hz
  Normal   SuccessfulAttachVolume  2m11s              attachdetach-controller                AttachVolume.Attach succeeded for volume "pvc-22d5b3ad-6f0a-44ef-b306-0461f0928cb8"
  Normal   Pulling                 2m4s               kubelet                                Pulling image "alpine/git"
  Normal   Pulled                  2m4s               kubelet                                Successfully pulled image "alpine/git" in 127.33456ms
  Normal   Created                 2m4s               kubelet                                Created container templates-clone
  Normal   Started                 2m3s               kubelet                                Started container templates-clone
  Normal   Pulling                 2m3s               kubelet                                Pulling image "alpine/git"
  Normal   Pulled                  2m3s               kubelet                                Successfully pulled image "alpine/git" in 88.104644ms
  Normal   Created                 2m2s               kubelet                                Created container templates-sync
  Normal   Started                 2m2s               kubelet                                Started container templates-sync
  Normal   Pulled                  2m2s               kubelet                                Container image "quay.io/2i2c/pilot-hub:0.0.1-n1159.h5b045cd" already present on machine
  Normal   Created                 2m2s               kubelet                                Created container hub
  Normal   Started                 2m2s               kubelet                                Started container hub
  Warning  Unhealthy               112s (x5 over 2m)  kubelet                                Readiness probe failed: Get "http://<IP_ADDRESS>:8081/hub/health": dial tcp <IP_ADDRESS>:8081: connect: connection refused

Value / benefit
I will immediately benefit from being able to test if I have successfully granted access to requestor pays data.
Users of the hub (incl. production which will borrow from staging's config) will need to be able to spin up any machine in the profile list.
Tasks to complete

[ ] Check other machine sizes spin up ok
[ ] Tweak nodeselector and memory request values to mitigate

Updates

The medium machine spins up fine and I was able to test the requestor pays stuff there

Update

The medium machine spins up fine and I was able to test the requestor pays stuff there

(I don't know why this isn't showing up at the bottom of the top comment btw. It's in the raw markdown 🤷🏻♀)

We match pods to nodepools based on node labels and memory capacity (https://github.com/2i2c-org/pilot-hubs/blob/2f4a68b68fe4277c4a58b2fbd9544568bf48f0d0/config/hubs/pangeo-hubs.cluster.yaml#L78), so only one pod ends up on a node (not helpful in edu contexts, but helpful in research contexts). We probably need to tweak the values for nodeselector and memory request so the autoscaler knows which nodepool to scale up.

Tasks to complete

[ ] Check other machine sizes spin up ok
[ ] Tweak nodeselector and memory request values to mitigate

Thanks for checking this Sarah! I just hit the same issue myself and was glad to see it was already on the radar.
As long as we are looking at the profile list, it would be nice to match the settings of the earlier cluster: https://github.com/pangeo-data/pangeo-cloud-federation/blob/d051d1829aeb303d321dd483450146891f67a93c/deployments/gcp-uscentral1b/config/common.yaml#L76-L105
I am concerned about the possible cost liabilities if we let anyone launch a notebook pod with 128 GB of RAM! Ideally we could differentiate the profile list based on user groups, but afaik this is not possible.

Thanks @rabernat - I will begin working on this today and I was indeed going to check what options where currently available on the old cluster :)

Confirming that changing the cpu/mem specs to match what is currently running on the old pangeo cluster (linked above in Ryan's comment) fixes this issue. I'm going to check everything else spins up ok and add in the ML option too.

@TomAugspurger do you mind giving me a little bit of insight into the nodepool machine types that the different profiles are assigned to when they're requested please? Poking around here it seems to me everything is a n1-highmem-4?

I think the GCP hub is configured to use GKE's "node auto-provisioning": https://cloud.google.com/kubernetes-engine/docs/how-to/node-auto-provisioning. The basic idea is to create a node-pool on the fly based on the resource requests of the pod.
The only thing giving me pause is that the auto-provisioning stuff seems to be commented out in the Makefile (https://github.com/pangeo-data/pangeo-cloud-federation/blob/d051d1829aeb303d321dd483450146891f67a93c/deployments/gcp-uscentral1b/Makefile)


subctl verify shouldn’t randomise test order

What happened:
I ran subctl verify several times; each time, the test order varied, which meant the display of skipped tests changed; e.g.
Will run 40 of 44 specs
•••••S•SS••••••••••••SS•••SS•••••SSSSSSSSSSS

and
Will run 44 of 44 specs
SSSSSSSSSSS•••••S•••••••••••••••••••••S•SS••

What you expected to happen:
The skipped tests to be consistently displayed.
How to reproduce it (as minimally and precisely as possible):
Run subctl verify several times.

It might help mitigate this to show the test name, as tracked in https://github.com/submariner-io/subctl/issues/131.
In CI, I think it's a feature to randomize the test order, to make the tests more robust and maybe catch other issues.
But for a user, yes it seems like it's just confusing, makes it harder to compare the output. But we use subctl verify in CI, so that complicates things. It seems it would need to be a flag. But as @tpantelis points out, maybe having the random order in places that use go test from Shipyard would be enough and the places in CI that use subctl verify would not likely be impacted by having deterministic ordering.

Ginkgo randomizes the order of top-level containers and it doesn't look like this is configurable. We can only control randomization of specs in each top-level container which is off by default.

Can’t we hard-code the seed, when run from subctl?

Can’t we hard-code the seed, when run from subctl?

yeah we can configure that.


Add support for restarting node server when file change using nodemon

Thanks for the feature 👍
If you have more ideias to improve this project you can share it!


[Bug] Failures in Start-Migration due to batch separation

Environmental information

Sorry, that command doesn't return anything for me, but here's some output I can get from running parts separately:
PSVersion 5.1.18362.145
Name    : dbatools
Path    : C:\Program Files\WindowsPowerShell\Modules\dbatools\1.0.66\dbatools.psd1
Version : 1.0.66

SQL Server:

Microsoft SQL Server 2017 (RTM-CU16) (KB4508218) - 14.0.3223.3 (X64)   Jul 12 2019 17:43:08
Copyright (C) 2017 Microsoft Corporation  Developer Edition (64-bit) on Windows 10 Pro 10.0 <X64> (Build 18362: )
(Hypervisor)

us_english

Report

When running Start-Migration, I got this error:
WARNING: [09:51:33][Copy-DbaInstanceTrigger] Issue creating trigger on destination | 'CREATE TRIGGER' must be the first
 statement in a query batch.

It looks like two items fail because of missing batch separators.

Host used

[X ] powershell.exe
[ ] ISE
[ ] VS Code
[ ] Other (please specify)

If anything other than powershell.exe was used, please confirm that you can duplicate the issue with powershell.exe

[ ] Still buggy in powershell.exe

Errors Received

See above.
Steps to Reproduce

Create in master database:
USE master;

CREATE VIEW [dbo].[ThirdPartyView] AS
SELECT *
FROM sys.databases;

Create wherever:
CREATE   TRIGGER [database_name_check] ON ALL SERVER
      FOR CREATE_DATABASE
AS
      BEGIN
            SET NOCOUNT ON;

            DECLARE @event_data XML;
			SET @event_data = EVENTDATA();
			SELECT @event_data
            IF ((SELECT @event_data.value('(/EVENT_INSTANCE/LoginName)[1]', 'NVARCHAR(255)') ) =  'NADABRUTO\edarl'
			     AND (SELECT @event_data.value('(/EVENT_INSTANCE/DatabaseName)[1]', 'NVARCHAR(255)') ) NOT LIKE  '%Stack%')
						BEGIN
							RAISERROR('NO CAN DO, BUCKAROO', 0, 1) WITH NOWAIT;
							ROLLBACK;
						END

      END;

Then try to run something like this: Start-DbaMigration -Source NADABRUTO\SQL2017 -Destination NADABRUTO\SQL2019 -Exclude Databases
Expected Behavior

Should copy objects without error.
Actual Behavior

Did not copy objects.

The trigger I can recreate and is due to the logic here
https://github.com/sqlcollaborative/dbatools/blob/51bc5eaf989c49f6aced69aa0d840c6d9562cdb7/functions/Copy-DbaInstanceTrigger.ps1#L166-L167
                        $sql = $sql -replace "CREATE TRIGGER", "`nGO`nCREATE TRIGGER"
                        $sql = $sql -replace "ENABLE TRIGGER", "`nGO`nENABLE TRIGGER"

because @erikdarlingdata  has more than one space between CREATE and TRIGGER :-)
@wsmelton - happy for me to PR with
$sql = $sql -replace "CREATE ", "nGOnCREATE "
Are there any issues I would be missing there?
@erikdarlingdata  I cant reproduce with the view :-(

Hm. I'll see if there's anything else about the view that makes it special when I get back home. Thanks Rob!

Hi @erikdarlingdata - just provided a pull request for that.

@andreasjordan WOOHOO! Thank you!


Hover effects (mouse-over) or Annotations

Component Description
Hover effects (mouse-over) or Annotations.
Currently we have hover effect (mouse-over) or Annotations built already.  Works well except if the annotations is 1 wide aka between adjacent cells to do a hover how to implement ?
example
const annotations: Annotation[] = [
{
text: 'example',
type: 'CDS',
direction: 'forward',
start: 10,
end: 200,
className:
'dark:text-amber-800 dark:bg-amber-400 bg-amber-600 text-white',
},
{
text: 'example',
type: 'foo',
direction: 'reverse',
start: 300,
end: 20,
className: 'dark:text-rose-800 dark:bg-rose-400 bg-rose-600 text-white',
},
];
works perfectly
const annotations: Annotation[] = [
{
text: 'example',
type: 'CDS',
direction: 'forward',
start: 10,
end: 10,
className:
'dark:text-amber-800 dark:bg-amber-400 bg-amber-600 text-white',
},
{
text: 'example',
type: 'foo',
direction: 'reverse',
start: 11,
end: 11,
className: 'dark:text-rose-800 dark:bg-rose-400 bg-rose-600 text-white',
},
];
This effect of 10 hides 11. Is it possible to implement hover over and show a specialized text like Pos:10 and probably or even the hover effect or mouse over. Any way to show some extra context over each cell would be appreciated.
Special Behavior
Style Variants

[x] Dark Mode
[ ] Light Mode

Time Estimate

I'm out until Jan 6th, but I'll definitely take a look then!

@vijib Don't think I fully understand,

Are you seeing something other than two annotations side by side, where you can hover over each individually?
Or are you asking to be able to override the builtin hover label with something else?

@ninjha01  Is there a way to do hover effects of adjacent cells. If so please share the code with me please ? Thanks

There isn't a way to hover an adjacent cell currently. Could you tell me a little about what it would enable for you?
Here is some example code with your example annotations

The example you have works beautifully. Would be grateful if you please tell me what this means
const annotations: Annotation[] = [
{
text: "example",
type: "CDS",
direction: "forward",
start: 10,
end: 10,
className:
"dark:text-amber-800 dark:bg-amber-400 bg-amber-600 text-white",
},
{
text: "example",
type: "foo",
direction: "reverse",
start: 11,
end: 11,
className: "dark:text-rose-800 dark:bg-rose-400 bg-rose-600 text-white",
},
];
the className
"dark:text-amber-800 dark:bg-amber-400 bg-amber-600 text-white",
and
className: "dark:text-rose-800 dark:bg-rose-400 bg-rose-600 text-white",
what are they achieving? Thanks

That's using tailwind's dark mode to set specific styles when the dark className is set on a parent element. In that case you'll see the text be set to rose-800 and the background set to rose-400 like so:

as opposed to text in white and background in rose-600 like so

Aha, looks good. Thanks @ninjha01  please close this issue. thanks again for your help

sorry one more question. what is forward and reverse here ?

You sometimes want to show whether the CDS (or other annotation) is on the "forward" strand (5' to 3') or the reverse stand of DNA/RNA.

Got it. Thanks @ninjha01  Appreciate your help


Empty generated file for @blueprintjs/icons

I'm trying to generate typings for @blueprintjs/icons (I'm starting with this simple one as a PoC, and then I intend to move on to more complicated modules of course). See https://github.com/joffrey-bion/kotlin-blueprintjs for my existing declarations.
In this @blueprintjs/icons NPM module, the package.json's typings property points to this lib/esm/index.d.ts definition file:
export { IconSvgPaths16, IconSvgPaths20, iconNameToPathsRecordKey } from "./iconSvgPaths";
export { getIconContentString, IconCodepoints } from "./iconCodepoints";
export { IconName, IconNames } from "./iconNames";

But when I generate external from it using Karakum, I only get this empty-ish index.kt file:
@file:JsModule("blueprintjs-icons/index")
@file:Suppress(
    "NON_EXTERNAL_DECLARATION_IN_INAPPROPRIATE_FILE",
)

package blueprintjs.icons

/* export { IconSvgPaths16, IconSvgPaths20, iconNameToPathsRecordKey } from "./iconSvgPaths"; */

/* export { getIconContentString, IconCodepoints } from "./iconCodepoints"; */

/* export { IconName, IconNames } from "./iconNames"; */

Here is my config for the Karakum Gradle plugin (in case it's useful):
{
    "input"<EMAIL_ADDRESS>    "output": "src/jsMain/generated",
    "libraryName": "blueprintjs-icons"
}

So I have a couple questions:

Why is the JsModule called blueprintjs-icons/index? Is this because it's <libraryName>/<originalFileName>? Could this cause a problem when importing these declarations in Kotlin? Or will this work out of the box?

Why is everything commented?

Why is the JsModule called blueprintjs-icons/index? Is this because it's /? Could this cause a problem when importing these declarations in Kotlin? Or will this work out of the box?

By default Karakum tries to preserve original structure of files, it may be good for granular imports (if library contains 100 files, but you need just one of them), but for small libs it maybe not good strategy, so you can override it using moduleNameMapper:
    "moduleNameMapper": {
        ".*": "blueprintjs-icons"
    }

Why is everything commented?

Because there is no analog for re-export in Kotlin syntax :slightly_smiling_face: It is how Karakum works: if it meet something that it does not know how to convert, it just leaves the original code in comments.

But how am I supposed to make things work then? I mean the other files aren't converted as they should. I don't mind that it doesn't re-export, but Karakum should follow the import and convert the corresponding files too, right?

Now I see that my initial advice was incorrect, you should specify @blueprintjs/icons as libraryName in your config file, because it is actually name of NPM package and then use this mapping
    "moduleNameMapper": {
        ".*": "@blueprintjs/icons"
    }

If you want to see @file:JsModule("@blueprintjs/icons") instead of @file:JsModule("@blueprintjs/icons/index") in you generated files.

I thought all files exporting top-level declarations from the blueprintjs-icons JS module should also have a JsModule with the name of the original JS module.

And they do. The thing it that there is no blueprintjs-icons (or to be correct @blueprintjs/icons) JS module in reality, JS module is file with JS code + js extension. @blueprintjs/icons is package, package is a folder that marked by package.json file. So Node module resolution works this way: if there is main or exports field in  package.json, then it forwards import from package name to file that specified main or exports field (e.g. if you have ./lib/esm/index.js in you package.json and your package is @blueprintjs/icons, so import "@blueprintjs/icons" will be resolved to import "@blueprintjs/icons/lib/esm/index.js"). So, actually Karakum tries to write into @JsModule name of JS file, TS declarations were written for.

Here I would expect ./iconSvgPaths.d.ts, ./iconCodepoints.d.ts, and ./iconNames.d.ts to be converted to the corresponding Kotlin externals

It is fair expectation, but what if @blueprintjs/icons depends on third party library (and I believe it does)? Should Karakum convert files in that libraries too? Now the strategy of conversion is more strict: only files, that specified in input field will be converted. If you have multiple files in your library you can use glob expressions or even array of glob expressions.


memorable emoji experiment

In a secure communication system, it is necessary at some point to verify keys.
Usually, this is represented as text key encoded as letters, hex, base32, base58 or maybe base64. Since a hash is a lot to deal with, often the hash is truncated to be easier for humans to process. (it's important not to truncate too much, or security will be lost https://evil32.com/ )
Humans have an approximately fixed capacity to remember things, and so when looking at a finger print, how many bits are they actually remembering? Since it seems the way humans work is they can remember (say) 7 things, but there is not a limit on the size of the set the 7 things are picked from. They could just as easily remember 7 animals as 7 digits.
Thus, to exand the security property of the user interface, if key fingerprints are displayed in a denser format (such as base emoji) then humans ought to be able to remember more bits, and thus have more secure fingerprints.
I want to test this in an experiment - i figure, a web page test subjects visit, and it associates keys with user names - then an attacker is simulated, where the subject must flag invalid keys that partially collide with their known keys.
The question is: does the detection success vary in proportion to encoding, and collision length?
@jbenet would love your ideas on this.
So far I have been unable to find any research on the usability of key fingerprints.

found this: https://github.com/tomrittervg/crypto-usability-study


Add gen task to gapic gem

The top-level rake gen task breaks because this task is missing. We have similar no-op tasks in gapic-common and shared.


Jbaker/arrow keys open bib

Alaska Airlines Pull Request
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes: #78
Summary:
Update all deps.
Add functionality to open the bib when using the arrow keys if there are available options to show.
Type of change:
Please delete options that are not relevant.

[x] New capability
[ ] Revision of an existing capability
[ ] Infrastructure change (automation, etc.)
[ ] Other (please elaborate)

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

:tada: This PR is included in version 1.7.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


GitHub API Compliance Fixes

This fixes a few API-bugs
Fixes!

Label-data are now compliant
Labels can be fetched by Name (as well as ID)
API-Token can be sent via ?access_token=[...]
Issue-Listing can be queried for ?state=all to fetch all issues (for said repo)
Repos can be fetched by ID with /repositories/:id (undocumented feature, but it's used by OctoKit 😒 )

Backwards Compatability Breakage!

label.Color is no longer prefixed with # (since GH doesn't do that)

Related Issue: #64
I'm sure there are more Gogs-issues that I'm closing with this PR, but I'm to lazy ATM to look them up 😆

LGTM

LGTM.

@lunny @tboerger I want a 3rd opinion since I'm actually breaking stuff here as well :trollface:

@bkcsoft would it not be technically a 4th and 5th opinion? 1st being yours, 2nd being @0xbaadf00d and 3rd being me... unless I'm not an opinion ._.

@LefsFlarey I didn't count myself 😆

@bkcsoft oh ok. .-.

Current coverage is 3.02% (diff: 0.00%)

Merging #227 into master will decrease coverage by <.01%

@@            master      #227   diff @@
========================================
  Files           33        33
  Lines         8106      8120    +14
  Methods          0         0
  Messages         0         0
  Branches         0         0
========================================
  Hits           246       246
- Misses        7840      7854    +14
  Partials        20        20

Powered by Codecov. Last update cb16028...b6ff427

@lunny done :)

rebased and fixed conflicts :)

@lunny could you review again? :slightly_smiling_face:

LGTM

But maybe you need to rebase as the drone push failed with matrix builds.

@tboerger noted, I also need to rebase now that a few fixes in this one got fixed in #300 (related to go-sdk vendor update)...

push failed

Now it should be fine :D


Limit usage of malloc.conf options to OpenBSD

Turns out the S option has a different meaning on {Free,Net}BSD and the R option
is not supported.
/cc @DBOTW and @mike-burns for autoconf inspection

Codecov Report

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

@@           Coverage Diff           @@
##           master     #282   +/-   ##
=======================================
  Coverage   90.14%   90.14%
=======================================
  Files           1        1
  Lines         497      497
=======================================
  Hits          448      448
  Misses         49       49

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 1b37a9d...e7ab4ea. Read the comment docs.


can't scroll through content of the dialog if dialog is higher than the page height

this seems to be a common issue with dialog libraries. the way i worked around it for my own implementations is that i disabled scrolling for the content in the background and added a scrollbar for the dialog modal.

Hello.
a11y-dialog does not make any consideration regarding styling. This is entirely up to you (aka the implementor). Scrolling, sizing and positioning is entirely done through the CSS layer, which is not part of the library.


Added step for highlighting subgrid row at position X & support for editable subgrids

Purpose
Added step for highlighting (not opening) subgrid row at position X & added support for editable subgrids
Approach
Added step for highlighting (not opening) subgrid row at position X & support for editable subgrids
TODOs

[x] Automated test coverage for new code
[x] Documentation updated (if required)
[x] Build and tests successful

Thanks, @sahjan. Can I also ask that you create a PR for EasyRepro and add a comment to this extension method with a link to the PR? That'll keep the technical debt on this repository down and help contribute to a wider audience. The bug that required this extension method was actually fixed in https://github.com/microsoft/EasyRepro/pull/1031 so it was a candidate for removal.

Thanks, @sahjan. Can I also ask that you create a PR for EasyRepro and add a comment to this extension method with a link to the PR? That'll keep the technical debt on this repository down and help contribute to a wider audience. The bug that required this extension method was actually fixed in https://github.com/microsoft/EasyRepro/pull/1031 so it was a candidate for removal.


Should not be able to add same member multiple times

Version: Master 2.2 (2/19/19)
What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

Create any of the following: GDNS provider, GDNS entry, MC app
Add a member. Notice you can add the same member several times

Result:
You should ideally not be able to set the same user several times as there is no reason for this as the access types are distinct and unique.
Expected result:
You can only add a member once
Actual result:
You can add the same member as many times as you want and still submit the form (create/upgrade/edit).

Related to this, I have seen that often (not always), selecting a user from the dropdown will add the selected user to the member list twice.

@bmdepesa issue has been filed, and a fix will be in shortly https://github.com/rancher/rancher/issues/18292


Having issue setting up multiple Scenes

Hi, I have an application that involves creating multiple scenes within a loop, but only one scene gets created successfully. Any more than that i start getting all sorts of errors. From width of undefined to segmentation dump error. I setup my own queue using bull so only one video is ever processed at a time.
Here is a screenshot of the error.

Here is my code.
    const image = new FFImage({
      path: imagePath,
      opacity: 1,
      y: this.canvasHeight / 2,
      x: 500,
      scale: 0.9,
    });

    for (let i = 0; i < textArray.length; i++) {
      const textLine = textArray[i];
      const duration = 10;
      const fontSize = this.fontSize;
      const renderText = new FFText({
        text: textLine,
        style: { fontSize },
        x: 900,
        y: this.canvasHeight / 2,
      });
      renderText.setColor('#ffffff');
      renderText.addEffect('fadeIn', 1, 1);
      renderText.addEffect('fadeOut', 3, duration - 3);
      renderText.setFont(path.join(this.assetPath, `fonts/${this.font}`));

      renderText.setAnchor(0, 0.5);
      renderText.setStyle({ verticalAlign: 'middle' });

      const scene = new FFScene();
      scene.setBgColor(this.sceneColor);
      scene.setDuration(duration);
      this.creator.addChild(scene);

      scene.addChild(image);
      scene.addChild(renderText);
    }

The video builds in the end, but Image is not rendered on the scenes. Only text shows up.

I run your code without errors.
Please ensure that the path of the image is correct, and do not addChild image in the for loop

Maybe you can provide more detailed code or upload the project

You mean I shouldn't do scene.addChild(image) within the loop? But I want the image to appear in all the scenes. How do I do that?

You mean I shouldn't do scene.addChild(image) within the loop? But I want the image to appear in all the scenes. How do I do that?

But you created it once

Yes, I did. I thought the optimal thing to do was to create it once and reuse it wherever it was needed. Will try creating it within the loop and see what I get.

Thank you @drawcall, that worked!


When I use this react-native-pager-view in Expo Web it crashes the whole building

Environment
"@gorhom/bottom-sheet": "^4.6.4",     "@react-native-async-storage/async-storage": "1.23.1",     "@react-native-community/netinfo": "11.3.1",     "@react-navigation/native": "^6.1.18",     "@react-navigation/native-stack": "^6.11.0",     "axios": "^1.7.7",     "expo": "~51.0.36",     "expo-auth-session": "~5.5.2",     "expo-clipboard": "~6.0.3",     "expo-crypto": "~13.0.2",     "expo-device": "~6.0.2",     "expo-font": "~12.0.10",     "expo-image": "~1.13.0",     "expo-notifications": "~0.28.18",     "expo-status-bar": "~1.12.1",     "firebase": "^10.13.1",     "lottie-react-native": "6.7.0",     "react": "18.2.0",     "react-dom": "18.2.0",     "react-native": "0.74.5",     "react-native-dotenv": "^3.4.11",     "react-native-gesture-handler": "~2.16.1",     "react-native-modern-datepicker": "^1.0.0-beta.91",     "react-native-pager-view": "6.3.0",     "react-native-reanimated": "~3.10.1",     "react-native-safe-area-context": "4.10.5",     "react-native-screens": "3.31.1",     "react-native-svg": "15.2.0",     "react-native-web": "~0.19.10",     "expo-localization": "~15.0.3",     "expo-system-ui": "~3.0.7",     "@expo/metro-runtime": "~3.2.3"
Description
I was using PagerView in my android app using Expo. But Expo also provides web support and when I started my webapp using expo it was not letting me build and giving me error =>
Unable to resolve "../Utilities/Platform" from "node_modules\react-native\Libraries\ReactPrivate\ReactNativePrivateInterface.js"
Reproducible Demo
You just have to write
import PagerView from 'react-native-pager-view';
in a expo project and run it on web. It will give the following error.
Temp Stackoverflow Solution =>
https://stackoverflow.com/questions/79052387/unable-to-resolve-utilities-platform-from-node-modules-react-native-librar

Hello
The pager does not support the web platform. To ensure consistent behavior across all platforms, please implement a solution that returns an empty component for the web application


NUT-05 changes

Fixes: none
Description
Implement changes proposed in https://github.com/cashubtc/nuts/pull/136
Changes

add state in MeltRepsonse
alter API to parse state and return stable isPaid (backwards compatible)
add state

PR Tasks

[x] Open PR
[ ] run npm run test --> no failing unit tests
[ ] run npm run format

@gandlafbtc I am having problems with the test suite, so I did not run tests yet.
 TypeError: Cannot assign to read only property 'fetch' of object '[object global]'

      3 | import fetch, { Headers, Request, Response } from 'node-fetch';
      4 |
    > 5 | (globalThis as any).fetch = fetch;
        |                          ^
      6 | (globalThis as any).Headers = Headers;
      7 | (globalThis as any).Request = Request;
      8 | (globalThis as any).Response = Response;

      at Object.<anonymous> (test/_replace-native-fetch.ts:5:26)

Superseded by https://github.com/cashubtc/cashu-ts/pull/148 (please reopen if necessary)


Version 2 Improvements and Ideas

Planned version 2 features: (note: features completed have only undergone basic testing)

[x]  zoomrec client (that actually records the meeting) receives its meetings from the zoomrec server via JSON API (no more local meetings.csv)
[x] zoomrec server has all JSON APIs to create/modify/delete meetings which will allow to build better UIs e.g. a graphical telegram UI or app
[x] zoomrec client supports a postprocessing script e.g. to transcribe meetings after recording. I use an ESP8266 that connects to the server to find out if a meetings is about to start and starts a PC with zoomrec client. It also switches the PC off if meetings is beyond its scheduled end - but with postprocessing it is not possible to predict when all is finished. Therefore, a status concept for the meetings is introduced, such that the ESP8266 knows when meeting has ended including postprocessing
[ ] zoomrec server using sqlite instead csv files to manage meetings and users
[x] use Ubuntu 24.04 LTE as base image for zoomrec client
[x] support multiple zoomrec clients to allow recording in parallel (meetings get assigned to clients)
[ ] zoomrec server supports users and meetings are linked to user. User record contains email details and telegram id to update user about meetings recorded/added. Currently user information like telegram id is stored in the meetings (and therefore duplicated and not possible to centrally manage)
[ ] currently the zoomrec clients has a SMB server included to access the recordings remotely but that only works in a LAN. The zoomrec server will have an sftp server and the client transfers the recording to the server, where they can be accessed from the internet (another reason to have a user database to manage the access via sftp)
[ ] build a YAML based configuration framework for the screen control to accommodate Zoom changes in UI behavior and also support other tools like teams. The screen control doesn't work anymore for latest zoom version out of the box, so new screenshots of buttons and labels are required anyway, so this seems to be the right time to do this on conjunction with allowing to work with latest Zoom versions. At the moment I use the oldest supported version to avoid touching the screen control logic (which is a bit of Spaghetti code - but largely works for now)

thanks for the info.
will see what i can do, when I get time again (hopefully soon)


Objects are not valid as a child

Hi, I'm quite new to fluid and trying to setup a simple project with the preact-cli:
npx preact-cli create simple preact-fluid-test
cd preact-fluid-test
npm install preact-fluid --save

Then I replace the default index.js page with the following:
import { Button } from 'preact-fluid';
import './style';

export default function App() {
	return (
		<Button>
			Hello, World!
		</Button>
	);
}

And run npm run dev. However, I can see just an empty page in the browser and the following error in the DevTools:
Uncaught Error: Objects are not valid as a child. Encountered an object with the keys {nodeName,children,attributes,key}.

  in Button
  in App

    at eval (debug.js?8a89:328:1)
    at Array.forEach (<anonymous>)
    at preact__WEBPACK_IMPORTED_MODULE_0__.options.diffed (debug.js?8a89:340:1)
    at preact__WEBPACK_IMPORTED_MODULE_0__.options.diffed (index.js?a1c1:62:1)
    at j (index.js?5962:267:1)
    at w (children.js?36d0:137:1)
    at j (index.js?5962:211:1)
    at w (children.js?36d0:137:1)
    at j (index.js?5962:211:1)
    at P (render.js?e2d9:16:1)

The package.json
{
  "private": true,
  "name": "preact-fluid-test",
  "version": "0.0.0",
  "license": "MIT",
  "scripts": {
    "build": "cross-env NODE_OPTIONS=--openssl-legacy-provider preact build",
    "serve": "sirv build --port 8080 --cors --single",
    "dev": "cross-env NODE_OPTIONS=--openssl-legacy-provider preact watch",
    "lint": "eslint src"
  },
  "eslintConfig": {
    "extends": "preact"
  },
  "eslintIgnore": [
    "build/*"
  ],
  "devDependencies": {
    "cross-env": "^7.0.3",
    "eslint": "^7.17.0",
    "eslint-config-preact": "^1.1.3",
    "jest": "^29.3.1",
    "preact-cli": "^3.0.0",
    "sirv-cli": "^1.0.3"
  },
  "dependencies": {
    "preact": "^10.1.0",
    "preact-fluid": "^0.9.1",
    "preact-render-to-string": "^5.1.2"
  }
}

I'm seeing this too.
Pretty much exactly the same setup - default preact-cli setup, installed preact fluid, tried to show a button in various places and getting the same error:

       Uncaught (in promise) Error: Objects are not valid as a child. Encountered an object with the keys {nodeName,children,attributes,key,__,__b}.


Adapter API: add parsers/serializers

https://github.com/juttle/juttle-s3-adapter/pull/8 requires these out of the Juttle lib, but the cool kids are pulling all their Juttle dependencies off the JuttleAdapterAPI these days.
@demmer @rlgomes

+1 should have thought of this earlier

+1 to the additions, but the API version should be 0.6.0.

Actually as we discussed in person, let's make this 0.5.2. Also can you re-open this PR against the 0.5.x branch since we'll release it as a bugfix since it's needed to enable the S3 adapter to be ported to the new API.

https://github.com/juttle/juttle/pull/478


better support RMarkdown syntax

I love writing RMarkdown with R-Box in ST3, but it seems I can't get proper syntax highlighting and REPL-ing/Build System to work at the same time.
If I select AcademicMarkdown as a syntax, highlighting for italics and even @citations works fine, but no REPL or Build system or R highlighting.
Conversely, If I choose R Markdown, the above works fine, but I loose syntax highlighting for italics and other simple Markdown stuff.
What's up with that? My screw-up, or still a limitation?
Ps.: fantastic work! – It's like magic to have R in your ST3. No more IDEs.

RMarkdown is derived from Markdown Extended and obviously it doesn't support italics and citations.
I will give it a thought. It shouldn't too difficult to add AcademicMarkdown support.

Thanks @randy3k – sorry if I was being dense.
AcademicMarkdown support would be super.
Thanks for the great work, can't get over how great it is to have R in ST3.

I have added AcademicMarkdown support for sending commands. However, the R code high light will not work as it should be handled by AcademicMarkdown syntax.


Object reference not set  in an instance of an object

Hi there not really technical savvy here but i cant seem to be able to export the calendar i face the issue mentioned in  the title everytime i try to run the programme

Did you download and place the correct version of chromedriver in the the same folder?


Add planets/sun

Basic layout for planets and sun. They don't need to orbit yet. Placeholder textures should probably also be used. Maybe have pop up box that would allow for the mass, size( won't affect physics probably), velocity (speed and direction) and distance to be entered with sliders/text.

Oh we should probably allow for the the starting angle to be modified too. Like straight line angle from planet to sun


Changing BlurRadius

Is changing the blur radius no longer possible with MZFormSheet? I know the older version used to allow this but I don't see the option anymore. I know we are using the native blur but I don't see why the option would not be available?

No it is not possible, this was causing some bugs so i have decided to native blur

Alright, thank you for letting me know. What bugs were occurring? I only ever had one that was an easy fix, I was supporting iOS 7 or newer though. I don't know if it would be rejected from the app store but I may just go back to the old version if I need to use it again.


Manifest: Bump to v0.5

https://github.com/endlessm/endless-key-flatpak/releases/tag/v0.5

oops, just saw #1 😂


ENOENT, No such file or directory

Hi, I was using the code, and this error appeared. The files are named correctly, so I don´t know what can it be.

I have exactly the same problem. It drives me nuts! Can someone help?

I am having the same issue and its saying layers/eyeball/ file not found but I don't have a file that name

Same issue

Try to save the documents/code, close the program and open it again. It's fixed when it's saved.

it worked thanks
On Sat, Dec 11, 2021 at 10:38 AM mariadimm @.***> wrote:

Try to save the documents/code, close the program and open it again. It's
fixed when it's saved.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/HashLips/generative-art-node/issues/108#issuecomment-991593034,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWYI4KGCHU6A5KGN4HJKKZDUQMS25ANCNFSM5INI7GFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I just went to "File", "Save All", rerun the command "node index.js" and it perfectly went. Awesome.


Use xterm as default TERM variable.

Issue: https://github.com/aws-controllers-k8s/community/issues/885
Use xterm as default TERM variable to get rid of following error in prow job logs No value for $TERM and no -T specified
➜  test-infra git:(xterm) make kind-test
checking AWS credentials ... ok.
loading the images into the cluster ... ok.
=============================================================================================================================================================================================================================================checking AWS credentials ... ok.
test-helm.sh] Starting Helm Artifacts Test
test-helm.sh] installing the Helm Chart ack-ecr-controller in namespace ack-system-test-helm ... ok.
test-helm.sh] waiting 10 seconds for ecr controller to start ... ok
test-helm.sh] ACK ecr controller pod name is ack-system-test-helm/ack-ecr-controller-84c7fcf88-clmfm
test-helm.sh] Verifying that pod status is in Running state ... ok.
test-helm.sh] Verifying that there are no ERROR in controller logs ... ok.
test-helm.sh] uninstalling the Helm Chart ack-ecr-controller in namespace ack-system-test-helm ... ok.
test-helm.sh] removing ecr crds installed by Helm ... ok.
test-helm.sh] deleting ack-system-test-helm namespace ... ok.
test-helm.sh] Helm Artifacts Test Finished Successfully
=============================================================================================================================================================================================================================================Skipping e2e tests because ENABLE_E2E_TESTS is not true. Current value is : false

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/approve
/lgtm


Gif for different dashboards

2 ways we can get dashboard list:

[ ] By Tag
[ ] By Dashlist

create dir dash_clips
have json representing clips
then run the above command..
4, Generate clip in clips directory..

wizzy clip dashboards by tag tag_name

wizzy clip dashboards by file file_name

wizzy clip dash-list dash-list-name
wizzy clip dashboards-by-tag tag-name


deviceplugin: generalize A && B variants

Extract both variants in a more generic plugin, which is now
configurable with a JSON config file.
The configuration file allows to specify which devices should be created on which hostname, with special value '*' meaning "every host".
Also adds example config file
Signed-off-by: Francesco Romani<EMAIL_ADDRESS>

Docs are most likely lacking. Please suggest what needs to be documented better.

A few suggestions below:

Updating the README to point to the example config and indicate that it would create a setup such as the diagram included.

Update the Dockerfile and/or manifests to include the command line

Minor formatting changes made to the environment variable in the last commit, can we include that?

Minor update to the example config file is needed to match the diagram in the README

/hold

force pushed because of a rebase :
PENDING:

fixing the environment variable name as requested
proper testing against a real cluster

force pushed because of a rebase :
PENDING:
* fixing the environment variable name as requested

* proper testing against a real cluster

env var naming fixed

all fixed and tested, AFAICT seems good. I had to revert some changes, so I decided to squash all the patches.

I tested this PR, I noticed that in a scenario when we request both device type A and type B it creates a single device file /dev/tty10. Previous implementation would create tty10, tty11... corresponding to request for device type A and tty20, tty21 corresponding to request for device type B. A solution of this could be we make device files configurable parameter too but open to alternatives

Looks good, tested it works as expected!

Looks good, works as expected!

I have submitted a PR to your branch suggesting minor changes here. It is based on your branch so it should merge into your code without issues

Rebase you branch on the latest master branch and squash commits

Thanks for this excellent PR!

PR merged and changes rebased + squashed


feat(session replay): introduce standalone version of session replay package

Summary
This PR introduces a standalone version of the session replay SDK, that is also used by the existing plugin. The interface and functionality of the plugin itself has not changed at all, the functionality has been mostly moved to the standalone SDK. This will allow us to support customers who want to use session replay who aren't instrumented through the browser SDK.
To make reviewing this PR a bit easier, I've made the following gists to help compare functional logic movement, view the diffs of the most recent versions to see the file comparisons:

The existing plugin-session-replay-browser/src/session-replay.ts file vs the updated plugin-session-replay-browser/src/session-replay.ts (gist)
The existing plugin-session-replay-browser/src/session-replay.ts file vs the new session-replay-browser/src/session-replay.ts (ie, the old version of the plugin vs the new standalone sdk) (gist)
The existing plugin-session-replay-browser/test/session-replay.test.ts file vs the updated plugin-session-replay-browser/test/session-replay.test.ts (gist)
The existing plugin-session-replay-browser/test/session-replay.test.ts file vs the new session-replay-browser/test/session-replay.test.ts (gist)

Checklist

[x] Does your PR title have the correct title format?
Does your PR have a breaking change?:  no

Just realized based on the build failures that I'll need to break this into 2 PRs, to merge the session replay standalone first. I'll leave this open for now as I'd still love a review that looks at this change end to end


Importing nodes reverse their order

Due to changes in #130 the order of imported nodes is reverted.

Merged.


feat: Secret resource

Changes

add snowflake_secret_with_client_credentials resource
add snowflake_secret_with_authorization_code_grant resource
add snowflake_secret_with_basic_authentication resource
add snowflake_secret_with_generic_string resource
fix parsing oauth_scopes list with comma separated elements

Test Plan

[x] acceptance tests

References

https://docs.snowflake.com/en/sql-reference/sql/create-secret

I forgot to add, but there are missing entries in MIGRATION GUIDE and custom templates in templates/resources/ - please copy one of them and adjust accordingly for each of the resources. We need them to add some custom notes - in this case, we want to note that these resources are v1 release candidates.


New version: finufft_jll v2.0.4+1

Autogenerated JLL package registration

Registering JLL package finufft_jll.jl
Repository: https://github.com/JuliaBinaryWrappers/finufft_jll.jl
Version: v2.0.4+1
Commit: f03c4e77d39415aad5f4d0ecded991aedb07211b
Revision on Yggdrasil: https://github.com/JuliaPackaging/Yggdrasil/commit/6e12d3c77f990acdca357756a86ced4ae25f584b
Created by: @giordano

Wait, something's not right.  Artifacts are not lazy in https://github.com/JuliaBinaryWrappers/finufft_jll.jl/blob/f03c4e77d39415aad5f4d0ecded991aedb07211b/Artifacts.toml


Use PSW API in bazel for CLion

Description of this change
Using PSW API in bazel for CLion

Other than that, looks good to me and seems to be working as expected.

@TomatorCZ could you please update the PR title and description to make it more detailed regarding the scope of the change?


Integrate LCOX

Would be helpful to integrate the levelised cost of the energy carrier into the outouts.

Calculation ins now integrated into the functions module.


[Support] Unable to connect to LAN if WG connected on LAN

In raising this issue, I confirm the following:
{please fill the checkboxes, e.g: [X]}

[x] I have read and understood the contributors guide.
[x] The issue I am reporting can be replicated.
[] The issue I am reporting can be is directly related to the pivpn installer script.
[x] The issue I am reporting isn't a duplicate (see FAQs, closed issues, and open issues).

Issue
I have PiVPN with a WireGuard setup running on a RPi4 in combination with PiHole.
Have forwarded the port to the RPi and all works as intended when I connect from outside my LAN to WG.
Will get a connection and am able to browse internet and connect to internal resources on my LAN.
Problems arise when I'm connected to my LAN (either wifi or cabled) and try to still have that WG connection.
(The idea is that the WG is always on to make sure all traffic routes through home as this will keep PiHole active)
When connected to the LAN and an active WG connection I can still internet but no internal LAN resources are reachable.
When doing a ping I get 1  General failure.
Have you searched for similar issues and solutions?
(yes/no / which issues?)

yes
Console output of      curl -L install.pivpn.io | bash
  Output Here

Console output of      pivpn add or pivpn add nopass
  Output Here

Console output of      pivpn debug

pi@pihole:~ $ pivpn debug
::: Generating Debug Output
::::            PiVPN debug              ::::
=============================================
::::            Latest commit            ::::
commit 5aa0de636f32fd674b77a2b3dd64d97b51680707
Author: 4s3ti<EMAIL_ADDRESS>Date:   Mon May 31 21:01:46 2021 +0200

    IRC From freenode to libera.chat

    Changed info about IRC Chanel,
    Chanel moved from freenode to libera.chat
=============================================
::::        Installation settings        ::::
PLAT=Raspbian
OSCN=buster
USING_UFW=0
IPv4dev=eth0
dhcpReserv=1
IPv4addr=<IP_ADDRESS>/24
IPv4gw=<IP_ADDRESS>
install_user=pi
install_home=/home/pi
VPN=wireguard
pivpnPORT=51820
pivpnDNS1=<IP_ADDRESS>
pivpnDNS2=
pivpnHOST=REDACTED
INPUT_CHAIN_EDITED=0
FORWARD_CHAIN_EDITED=0
pivpnPROTO=udp
pivpnMTU=1400
pivpnDEV=wg0
pivpnNET=<IP_ADDRESS>
subnetClass=24
ALLOWED_IPS="<IP_ADDRESS>/0, ::0/0"
UNATTUPG=1
INSTALLED_PACKAGES=(wireguard-tools qrencode unattended-upgrades)
=============================================
::::  Server configuration shown below   ::::
[Interface]
PrivateKey = server_priv
Address = <IP_ADDRESS>/24
MTU = 1420
ListenPort = 51820
### begin USER1-S20FE ###
[Peer]
PublicKey = USER1-S20FE_pub
PresharedKey = USER1-S20FE_psk
AllowedIPs = <IP_ADDRESS>/32
### end USER1-S20FE ###
### begin USER1-Corp-Laptop ###
[Peer]
PublicKey = USER1-Corp-Laptop_pub
PresharedKey = USER1-Corp-Laptop_psk
AllowedIPs = <IP_ADDRESS>/32
### end USER1-Corp-Laptop ###
### begin USER2 ###
[Peer]
PublicKey = USER2_pub
PresharedKey = USER2_psk
AllowedIPs = <IP_ADDRESS>/32
### end USER2 ###
=============================================
::::  Client configuration shown below   ::::
[Interface]
PrivateKey = USER1-S20FE_priv
Address = <IP_ADDRESS>/24
MTU = 1400
DNS = <IP_ADDRESS>

[Peer]
PublicKey = server_pub
PresharedKey = USER1-S20FE_psk
Endpoint = REDACTED:51820
AllowedIPs = <IP_ADDRESS>/0, ::0/0
=============================================
::::    Recursive list of files in       ::::
::::    /etc/wireguard shown below       ::::
/etc/wireguard:
configs
keys
wg0.conf

/etc/wireguard/configs:
clients.txt
USER1-Corp-Laptop.conf
USER1-Corp-Laptop.conf.save
USER1-S20FE.conf
USER2.conf

/etc/wireguard/keys:
USER1-Corp-Laptop_priv
USER1-Corp-Laptop_psk
USER1-Corp-Laptop_pub
USER1-S20FE_priv
USER1-S20FE_psk
USER1-S20FE_pub
USER2_priv
USER2_psk
USER2_pub
server_priv
server_pub
=============================================
::::            Self check               ::::
:: [OK] IP forwarding is enabled
:: [OK] Iptables MASQUERADE rule set
:: [OK] WireGuard is running
:: [OK] WireGuard is enabled (it will automatically start on reboot)
:: [OK] WireGuard is listening on port 51820/udp
=============================================
:::: Having trouble connecting? Take a look at the FAQ:
:::: https://github.com/pivpn/pivpn/wiki/FAQ
=============================================
:::: WARNING: This script should have automatically masked sensitive       ::::
:::: information, however, still make sure that PrivateKey, PublicKey      ::::
:::: and PresharedKey are masked before reporting an issue. An example key ::::
:::: that you should NOT see in this log looks like this:                  ::::
:::: YIAoJVsdIeyvXfGGDDadHh6AxsMRymZTnnzZoAb9cxRe                          ::::
=============================================
::::            Debug complete           ::::
:::
::: Debug output completed above.
::: Copy saved to /tmp/debug.log

Have you taken any steps towards solving your issue?
While connected to LAN and WG, tracert to internet
tracert -w 100 -d google.com

Tracing route to google.com [<IP_ADDRESS>]
over a maximum of 30 hops:

  1     6 ms     2 ms     1 ms  <IP_ADDRESS>
  2     1 ms     1 ms     1 ms  <IP_ADDRESS>
  3    12 ms     3 ms     2 ms  <IP_ADDRESS>
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     4 ms     4 ms     4 ms  <IP_ADDRESS>
  7     5 ms     5 ms     5 ms  <IP_ADDRESS>
  8     4 ms     3 ms     4 ms  <IP_ADDRESS>

Trace complete.

While connected to LAN and WG, tracert to internal resource
tracert -w 100 -d <IP_ADDRESS>

Tracing route to <IP_ADDRESS> over a maximum of 30 hops

  1  General failure.

Trace complete.

It is likely a routing issue but can't figure out where it breaks down

Hi @Rouzax

It is likely a routing issue but can't figure out where it breaks down

you are entirely right there, and the reason is very simple, that is not how the vpn is intended to be used!
If you have VPN inside your home, you connect from outside into home!
connecting to the VPN when you are already inside your home is pointless and useless.
Read this, hope it helps you: https://blog.4s3ti.net/vpn-where-to.html

Moving this to discussions


Add swifttype  body embedded data attribute tags to improve search

This PR adds some meta tags to registry package pages so that we can improve search experience, to address https://github.com/pulumi/registry/issues/558.
Swiftype docs: https://swiftype.com/documentation/site-search/crawler-configuration/meta-tags?size=n_10_n#embedded
In this PR
With this PR, I added tags to the package title and to the overview description on the package landing page.  This by itself should have 0 impact - no visible changes in the UI, just the updated markup, and no impact on search.
Next steps
Based on all my doc-reading (please correct me if I'm wrong, swifttype is new to me!), I believe that the next steps should be adding weights to the two new tags.  The highest weight we currently have is 3.5 (https://app.swiftype.com/engines/pulumi-docs/document_types/page/custom_queries/65161/edit).  Given that, I propose:

package-overview-description: 4.5.  Optimize the chances that searches for "Azure" or "aiven provider" give the landing page for the package as the top result.
package-title: 4.  This title appears on all of the top-level package pages - installation, how-tos, etc. Optimize the chances these top-level pages are ranked higher than subpages ("how to do a hello-world").

@kimberleyamackenzie I ask because I haven't done this myself: How relevant is it that this content be wrapped in a div tag within the body of the page? I ask because in theory, since this is page-level metadata (it describes this whole page), it'd be slightly better/cleaner to capture it as page-level frontmatter and then use that frontmatter to populate both the page itself and the any Swiftype-specific meta tags. What do you think?

@cnunciato We do use some shortcodes on these pages already, but I for sure understand keeping them to a minimum.  I was looking to not break up the info (right now this content is inserted to the template all together, and at least for me, makes it easier to understand what comes from where and how it manifests on the page), but I can pivot to your suggested approach.  Could you point me to where we define the schema.json to update this?

Caught up with @kimberleyamackenzie over Zoom (thanks!) and we're going to try using the frontmatter-param approach to see if we can get the outcome we want.

Based on @cnunciato's suggestion, I actually took out most of this PR and moved the logic over to hugo - I'll open that PR shortly, but in the meantime, this PR still touches one file, specifically adding the tag to the package title.  Tagging for re-review to look at that singular change.

thanks yall for collaborating together on this!! 💜


Add target 'node' to webpack config for react builds

In my opinion target: 'node' should be set in webpack to avoid any node specific shims that will be included by webpack.
As the react build of cleave.js is no standalone application (for example react and react-dom are excluded from the build) the user of the react build needs to come with his own build chain. Within this build chain process is defined by the node environment and thus does not need to be shimed.
My fix enforces webpack to assume that the consumer of the build runs in a node environment and thus prevents to add any node specific shims. See also diff of the resulting builds.

Makes sense, will merge.


[WW-5362] Removes type attribute out of <s:script/> tag

Closes WW-5362

FYI @sepe81 @gregh3269

Seems now I get
SEVERE: Exception sending context initialized event to listener instance of class [org.apache.struts2.tiles.StrutsTilesListener]
java.lang.NoClassDefFoundError: org/apache/commons/digester3/Rule
Caused by: java.lang.ClassNotFoundException: org.apache.commons.digester3.Rule
Deps want commons-digester-2.1.jar think this is v3?

What app have you used? This change shouldn't affect Digester

My app.

This is related to WW-5347 - and you are using <IP_ADDRESS> version as far I see, changes in this PR are unrelated to your problem.

OK, why would the jars be missing for
.m2/repository/org/apache/struts/struts2-tiles-plugin/6.4.0-SNAPSHOT
.m2/repository/org/apache/struts/struts2-javatemplates-plugin/6.4.0-SNAPSHOT
whilst
.m2/repository/org/apache/struts/struts2-core/6.4.0-SNAPSHOT are present.

@gregh3269 can we discuss this in the dev@ email list?

OK, mailing list.
...although I got it working and it seems good.

Are we good here?


README: Add Contribution section and License info

Suggested for openjournals/joss-reviews#107
You may want to extend the (c) Copyright to include all the contributors (and their institutions)

Good point, thanks!


Create an old school JS 'class' that can build and launch
an image
Fix some of the UX issues that came up:

Show log when build fails
Don't show waiting when we know the build already exists
Clear out the progress bar if we start a new build

Write comment about the state transitions that are valid. Should
enforce it at some point!A
Separate build and runtime parameters slightly better than before!

I need to add support back for file path detection - maybe move that logic to the server side actually (on JupyterHub), rather than the client.

I'm going to do the following:

In the tmpauthenticator derivative, I'll just stash all of the options from query params into user.spawner.user_options
In pre_start, change the spawner options based on the items from user_options

This should be more generalizable than the current solution

Merged!


[FEATURE] Support for Zhipu Model image generations interface

the official endpoint： https://open.bigmodel.cn/api/paas/v4/images/generations

Implemented in https://github.com/langchain4j/langchain4j/pull/1152


F#: #i directive with @-prefixed verbatim string fails with Invalid URI error

Describe the bug
#i directive with @-prefixed verbatim string:
#i @"nuget: C:\code\LocalPackages"

Fails with output:
Restore sources
@ C:\code\LocalPackages
Error: PackageManagement Error 3217 Invalid URI: The URI scheme is not valid.

Triple-quoted string as follows works:
#i """nuget: C:\code\LocalPackages"""

Please complete the following:
Which version of .NET Interactive are you using?
Version: 1.0.240403+56a0e392fba305af06e72ce7dec885b2b6722c00
Build date: 2021-08-07T17:28:18.2479865Z

OS

[x] Windows 10
[ ] macOS
[ ] Linux (Please specify distro)
[ ] iOS
[ ] Android

Browser

[ ] Chrome
[x] Edge
[ ] Firefox
[ ] Safari

Frontend

[ ] Jupyter Notebook
[ ] Jupyter Lab
[ ] nteract
[x] Visual Studio Code
[ ] Visual Studio Code Insiders
[ ] Other (please specify)

The #i ... parser in .NET Interactive is different from the one used in FSI.  In a notebook you don't need to use a verbatim string, just this will suffice: #i "nuget:path\to\folder".


Add hass-gardena-smart-system in the default repositories of HACS

A PR has been opened there : https://github.com/hacs/default/pull/515

The integration is now in the default repositories from HACS !


Deployment of static frontends

Implements the requirement
https://github.com/nuvolaris/nuvolaris-cli/blob/main/README.md#static-frontend
Nuv must scan the folders and create an yaml file the static contents.
Format of the YAML:
namespace: <namespace>
path: <path>
resources:
  <file1>: <body1>
  <file2>: <body2>
  ...

Where the <fileN> is the relative path of under the various web folders.
The <bodyN> file is the base64 encoded of the corresponding file.
Those files will be crd to be deployed to Kubernetes.

Closing this issue as we are moving to deploy an s3 compatible storage


Update library versions for security vulnerabilities.

Dependabot highlighted some issues with dependencies, this pr updates those

Good news! this is blocked on this: https://github.com/microsoft/node-jsonc-parser/pull/78


No Input Validation When finalizing a form

In the Survey App, I can create a blank form. This because, I can go to next without selecting any option, or typing anything.
This is understandable, because you can mark the instance as incomplete. My concern is the fact that you could actualy finalize an empty form (that is no entry was recorded). Is this a bug, or is this how its supposed to work?

There is the required column in form definition that if set to true will require the question be answered before the user can move on. It's up to the form designer to decide if the question is required or not.


Mobile forms: Entering a text field zooms the page on iPhone.

As per below:

Default font-size for text fields in a form is 14px. If this is changed to 16px then the site won't zoom on form element focus.
This could be done by changing:
$rpl-form-text-ruleset: ('xs', 1.3em, 'regular') !default;
$rpl-form-element-text-ruleset: ('xs', 1em, 'regular');

to
$rpl-form-text-ruleset: ('s', 1.3em, 'regular') !default;
$rpl-form-element-text-ruleset: ('s', 1em, 'regular');

Hi @alan-cole - thanks I've raised an internal ticket SDPA-5285. I agree with the change. Just checking with Design if there are any concerns with changing it.


Ordering Columns

How do i specify the order of the columns to appear in the rendered output

+1, I assume the order of columns is getting mixed up because the data is converted to a dict

+1

Thanks for reporting! I just added a new columns property that allows you to specify the order: https://github.com/plotly/dash-table-experiments/commit/790173eed46ea0d28382491a73435d0fce5fa652
Upgrade with pip install dash-table-experiments==0.2.1


vision torch no longer blocks equipping ship tools

What's fixed?

in the title: vision torch no longer blocks equipping ship tools

ie if you're piloting your ship while holding a vision torch, you can use the scout launcher, signalscope, etc, as expected

Made a draft so I can add OnProjectionCompleted event


Resolve unmet peer dependencies

I do not see any specific features (maybe I missed something), but it seems reasonable to go for every react and react-native version if react-navigation does.
resolves #4

Would you mind releasing a version with this patch in it?

Just did -> alpha.10 includes it

Thanks!


Detect if this is Chrome on Mac and set architecture to 64

On version 39 of Chrome and above only 64bit is supported on Mac (see here)
This change, detects this and set os.architecture accordingly.

+1


fix(*): fix possible crash

Possibly Fixes #131
Proposed Changes

Guard against setting a null key or value or null dict

Can one of the admins verify this patch?