[BUG] New volume stuck detaching

Describe the bug
Note this is arm64, using master-arm64 image tags.
A newly created volume is detaching and unable to attach to a pod.
Pod events:
  Type     Reason              Age                   From                     Message
  ----     ------              ----                  ----                     -------
  Warning  FailedScheduling    9m36s                 default-scheduler        persistentvolumeclaim "test1" not found
  Warning  FailedScheduling    8m35s                 default-scheduler        persistentvolumeclaim "test1" not found
  Warning  FailedScheduling    8m28s                 default-scheduler        0/5 nodes are available: 5 pod has unbound immediate PersistentVolumeClaims.
  Warning  FailedScheduling    8m28s                 default-scheduler        0/5 nodes are available: 5 pod has unbound immediate PersistentVolumeClaims.
  Normal   Scheduled           8m7s                  default-scheduler        Successfully assigned default/test1-7f6c4d4545-8l4ll to node04
  Warning  FailedAttachVolume  114s (x11 over 8m7s)  attachdetach-controller  AttachVolume.Attach failed for volume "pvc-dc1e714a-be64-4ffc-994a-5a0ccbbad495" : rpc error: code = Aborted desc = The volume pvc-dc1e714a-be64-4ffc-994a-5a0ccbbad495 is detaching
  Warning  FailedMount         96s (x3 over 6m4s)    kubelet                  Unable to attach or mount volumes: unmounted volumes=[data], unattached volumes=[data default-token-wbd5m]: timed out waiting for the condition

PVC events:
  Type     Reason                 Age                From                                                                                Message
  ----     ------                 ----               ----                                                                                -------
  Normal   ExternalProvisioning   12m (x2 over 12m)  persistentvolume-controller                                                               waiting for a volume to be created, either by external provisioner "driver.longhorn.io" or manually created by system administrator
  Normal   Provisioning           12m (x2 over 12m)  driver.longhorn.io_csi-provisioner-686b6fff79-sj2dg_0d4e5093-7b79-4fdf-89e6-af210935fa2f  External provisioner is provisioning volume for claim "default/test1"
  Warning  ProvisioningFailed     12m                driver.longhorn.io_csi-provisioner-686b6fff79-sj2dg_0d4e5093-7b79-4fdf-89e6-af210935fa2f  failed to provision volume with StorageClass "longhorn": rpc error: code = DeadlineExceeded desc = context deadline exceeded
  Normal   ProvisioningSucceeded  12m                driver.longhorn.io_csi-provisioner-686b6fff79-sj2dg_0d4e5093-7b79-4fdf-89e6-af210935fa2f  Successfully provisioned volume pvc-dc1e714a-be64-4ffc-994a-5a0ccbbad495

To Reproduce
Steps to reproduce the behavior:

Download deploy/longhorn.yaml from master.
Replace every instance of longhornio/${image}:{tag} with longhornio/${image}:master-arm64.
Uncomment CSI_ATTACHER_IMAGE and set it to longhornio/csi-attacher:v2.2.1-lh1.
Uncomment CSI_PROVISIONER_IMAGE and set it to longhornio/csi-provisioner:v1.6.0-lh1.
Uncomment CSI_NODE_DRIVER_REGISTRAR_IMAGE and set it to longhornio/csi-node-driver-registrar:v1.2.0-lh1.
Uncomment CSI_RESIZER_IMAGE and set it to longhornio/csi-resizer:v0.5.1-lh1.
Create a PVC with storageClassName: longhorn.
Create a pod to mount the PVC.

Expected behavior
The pod should become Ready.
Log
If applicable, add the Longhorn managers' log when the issue happens.
Environment:

Longhorn version: f91466b
Kubernetes version: v1.19.3+k3s3
Node config

CPU type: arm64
OS: Ubuntu 20.04.1
CPU per node: 4
Memory per node: 4GB
Disk type: SD flash card
Network bandwidth and latency between the nodes: local 1Gbps switch

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): Bare metal

Additional context
Fixed by modifying ClusterRole longhorn-role to add:
            - apiGroups: ["policy"]               resources: ["poddisruptionbudgets"]               verbs: ["get", "watch", "list", "delete", "update", "create"]

Can you share the log of longhorn-manager? As well as longhorn-csi-plugin log inside the longhorn-csi-plugin pod.

The longhorn-manager log had lots of these, until I modified the ClusterRole:
time="2020-11-24T05:13:07Z" level=warning msg="Error syncing Longhorn instance manager longhorn-system/instance-manager-r-b133944b: fail to sync instance manager for longhorn-system/instance-manager-r-b133944b: poddisruptionbudgets.policy is forbidden: User \"system:serviceaccount:longhorn-system:longhorn-service-account\" cannot create resource \"poddisruptionbudgets\" in API group \"policy\" in the namespace \"longhorn-system\""

And the CSI pod had many repetitions of this:
time="2020-11-24T05:09:27Z" level=error msg="GRPC error: rpc error: code = Aborted desc = The volume pvc-dc1e714a-be64-4ffc-994a-5a0ccbbad495 is detaching"
time="2020-11-24T05:09:27Z" level=info msg="GRPC call: /csi.v1.Controller/ControllerPublishVolume"
time="2020-11-24T05:09:27Z" level=info msg="GRPC request: {\"node_id\":\"node04\",\"volume_capability\":{\"AccessType\":{\"Mount\":{\"fs_type\":\"ext4\"}},\"access_mode\":{\"mode\":1}},\"volume_context\":{\"fromBackup\":\"\",\"numberOfReplicas\":\"3\",\"staleReplicaTimeout\":\"2880\",\"storage.kubernetes.io/csiProvisionerIdentity\":\"1606192170543-8081-driver.longhorn.io\"},\"volume_id\":\"pvc-dc1e714a-be64-4ffc-994a-5a0ccbbad495\"}"
time="2020-11-24T05:09:27Z" level=info msg="ControllerServer ControllerPublishVolume req: volume_id:\"pvc-dc1e714a-be64-4ffc-994a-5a0ccbbad495\" node_id:\"node04\" volume_capability:<mount:<fs_type:\"ext4\" > access_mode:<mode:SINGLE_NODE_WRITER > > volume_context:<key:\"fromBackup\" value:\"\" > volume_context:<key:\"numberOfReplicas\" value:\"3\" > volume_context:<key:\"staleReplicaTimeout\" value:\"2880\" > volume_context:<key:\"storage.kubernetes.io/csiProvisionerIdentity\" value:\"1606192170543-8081-driver.longhorn.io\" > "
time="2020-11-24T05:09:27Z" level=error msg="GRPC error: rpc error: code = Aborted desc = The volume pvc-dc1e714a-be64-4ffc-994a-5a0ccbbad495 is detaching"
time="2020-11-24T05:14:27Z" level=info msg="GRPC call: /csi.v1.Controller/ControllerPublishVolume"
time="2020-11-24T05:14:27Z" level=info msg="GRPC request: {\"node_id\":\"node04\",\"volume_capability\":{\"AccessType\":{\"Mount\":{\"fs_type\":\"ext4\"}},\"access_mode\":{\"mode\":1}},\"volume_context\":{\"fromBackup\":\"\",\"numberOfReplicas\":\"3\",\"staleReplicaTimeout\":\"2880\",\"storage.kubernetes.io/csiProvisionerIdentity\":\"1606192170543-8081-driver.longhorn.io\"},\"volume_id\":\"pvc-dc1e714a-be64-4ffc-994a-5a0ccbbad495\"}"
time="2020-11-24T05:14:27Z" level=info msg="ControllerServer ControllerPublishVolume req: volume_id:\"pvc-dc1e714a-be64-4ffc-994a-5a0ccbbad495\" node_id:\"node04\" volume_capability:<mount:<fs_type:\"ext4\" > access_mode:<mode:SINGLE_NODE_WRITER > > volume_context:<key:\"fromBackup\" value:\"\" > volume_context:<key:\"numberOfReplicas\" value:\"3\" > volume_context:<key:\"staleReplicaTimeout\" value:\"2880\" > volume_context:<key:\"storage.kubernetes.io/csiProvisionerIdentity\" value:\"1606192170543-8081-driver.longhorn.io\" > "
time="2020-11-24T05:14:27Z" level=debug msg="ControllerPublishVolume: current nodeID node04"

I see. The deployment method is wrong.
The master for github.com/longhonr/longhorn is still v1.0.2. To deploy the in-dev master, you need to deploy from https://github.com/longhorn/longhorn-manager , See https://github.com/longhorn/longhorn-manager#deployment . You shouldn't need to modify anything to make it work.
You can use the uninstaller to cleanup the broken deployment for now.

Thanks! It worked as you said.

Hi, can we reopen this issue ?
  Using the inClusterConfig.  This might not work.
I1202 22:47:20.149482       1 shared_informer.go:197] Waiting for caches to sync for longhorn datastore
E1202 22:47:20.198735       1 reflector.go:123] k8s.io/client-go/informers/factory.go:134: Failed to list *v1beta1.PodDisruptionBudget: poddisruptionbudgets.policy is forbidden: User "system:serviceaccount:longhorn-system:longhorn-service-account" cannot list resource "poddisruptionbudgets" in API group "policy" at the cluster scope

I fix it with the following command:
kubectl patch clusterroles.rbac.authorization.k8s.io longhorn-role --type='json' -p='[{"op": "add", "path": "/rules/1", "value": {"apiGroups": ["policy"], "resources": ["poddisruptionbudgets"], "verbs": ["get", "watch", "list", "delete", "update", "create"]} }]'

I think CRD is not fixed in the last version :

REPO: https://charts.longhorn.io
CHART: longhorn-1.0.2
APP VERSION: v1.0.2

@MalibuKoKo ARM64 is not supported for Longhorn v1.0.2, and only replace the images won't work. Please install using longhorn-manager repo as I mentioned above if you want to give it a try before the formal release. ARM64 will be released with the upcoming Longhorn v1.1.0 release, with the Helm chart.


[Feature Request]: Adding more Featured Categories

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
To add the more number of featured categories such as skincare, home essentials, smart gadgets etc
Use Case
Adding more featured categories like skincare, home essentials, and smart gadgets can significantly enhance the project by:

Attracting a wider audience with diverse interests.
Increasing user engagement through frequent visits and exploration.
Boosting sales via cross-selling opportunities and increased transactions.
Enhancing user experience with better personalization and convenience.
Providing a competitive edge by differentiating the platform from rivals.
Collecting comprehensive data for targeted marketing and trend analysis.
Enabling strategic vendor partnerships and promotional opportunities.
Improving inventory management to handle a broader product range.
Facilitating targeted marketing strategies for new categories.
Enhancing user satisfaction through a comprehensive product offering.

Benefits
No response
Add ScreenShots

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@nisargaa20 can you tell how will you add new product ? Is there any API ?

@MAVRICK-1  I will add the UI of the categories not the product


"No such file" error

After npm install hiper -g, hiper baidu.com throws this exception:
/usr/bin/env: 'node --no-warnings': No such file or directory
I'm currently running Node 10 with nvm on Manjaro (Arch) Linux.

Hi, May be you should run sudo ln -s /usr/bin/nodejs /usr/bin/node

I think it must be something else. That command returns an error because /usr/bin/node already exists. I currently have node installed with both pacman (because it's a dependency of some locally installed apps like atom) and with nvm, so when I run which node it returns:
/home/sendrecv/.nvm/versions/node/v10.3.0/bin/node

Try which env and type /usr/bin/env. Then run /usr/bin/env node.

Same issue here, node 10. The env is set properly (I think) and both /usr/bin/env and /usr/bin/env node work by themselves, but not when running hiper

Hi, was just gonna report that myself. The problem lies within your shebang.
https://github.com/pod4g/hiper/blob/aa30b1651c31de7643849c81b6134375c73c16a8/src/index.js#L1
Linux (unlike BSD it seems) doesn't support more than one argument to the shebang command. (Details)
Get rid of the --no-warnings argument and it should function properly. node added support for a NODE_NO_WARNINGS environment variable. Maybe use that as a workaround?

@pseudolog has it right, remove the --no-warnings and it will work correctly
and I agree with the NODE_NO_WARNINGS env variable as a work around, I think that would be the best course of action

@pseudolog Well done!!!!

Hi guys.
I change my code  as follow The warning message will still appear
#! /usr/bin/env node
process.env.NODE_NO_WARNINGS = 1
...

Can someone help me?

Maybe add a shell wrapper, instead of excute the index.js directly.

I guess the cleanest solution would be to actually handle those promise rejections. Otherwise there's process.removeAllListeners('warning')

@zhiyan Please give me more details. what should i do？

The problem has been solved, please upgrade hiper to 0.0.15
run below to upgrade:
npm i hiper -g


Operation Journal

This would be useful to activate during a database export. In this way any operation occurred during the export could be re-applied to the database copy.

Seems we don't need this anymore. I just postpone this waiting to understand if the new WAL is enough.

Ok, in case of sharding we'd need this:

Node 1 has the clusters A, B and C
Node 2 has the clusters C and D

In this case the WAL is not enough. We'd need a sort of WAL per cluster...

Guys,
Is this somehow related to thing commonly called "audit log"? Some table(or view) with all operations over specific entities in a system. Can WAL be used for that? It's expected to see the following things in "audit log":

What document was changed
By whom that document was changed
When it was performed
Where (node) and from where (IP address or something)
Type of change: create, update delete
New and old values

I planned this feature for Orienteer (https://github.com/OrienteerDW/Orienteer/issues/156), but if OrientDB has it OOB - that will be cool.

It is implemented several versions ago, journal and wal are conceptually the same things.

We have already discussed this level of operation journal is not enough to provide database consistency, also solution which includes wal for leave backups was proposed. We do not need PoC of this because the same solution has been already implemented in PostgreSQL , so it is living proof of effectiveness of this design.

@laa Have you read my last comment on this?

Yes, but we disscussed operation journal before with Artem, operation journal was in previous version of distributed system and this journal does not allow to keep data consistency in case of split brain syndrom. that is fist point. the second point is that transaction are not performed on cluster level granulrity so cluster level wal will not solve data consistency problems. And last one there are practically proved methods of keeping data consistency in distributed storage like Merkel tree  usage or Paxos, or bunch of other apporaches which were practically tested why we do not use them ?

I'm not talking about the consensus algorithm, but rather the way we can handle sharding by using the OrientDB features = manage cluster level journal. The answer could also be "it's too complex" and we can avoid incremental backup/restore in case of sharding


Moderate code readability improvement

This is an alternative compromise to #4 based on the discussion with @LaansDole

guess on line 32 is very vague, change to repeatedChar
You can change the name of variable of totalFreq -> totalFreq_CharRMI, that saves us 3 lines of comments on line 30, 46, 53
I still think the modulo on line 78 is too overwhelmed to put in a line. There are 3 operations happened at the same time, a separate function nextCharacterFrom(int charHash) should be better and clearer for the context.
matchCount - cumulativeMatchCount is still unclear, I think newMatchCount - cumulative MatchCount is better for context

The rest are fine

Resoved


feat: contract sizing task

Purpose for this PR

Need to know the size of the BondFactory that is exceeding the limit ...adding a task to display the contract sizes.

This added task is not ideal, a custom script should be created to output only the affected contract and ancestry.
Also it should work under npm, not requiring yarn


chore: Latest minor/patch updates and react packages updates

Update all minor/patch updates of packages

Styled components did some minor changes in v5.2.0, that broke 2 of our snapshot tests. Update of snapshots is needed.

Preallocate global style placement to ensure cGS is consistently inserted at the top of the stylesheet; note that this is done in runtime order so, if you have multiple cGS that have overlapping styles, ensure they're defined in code in the sequence you would want them injected (see #3239)

Update react and react-dom packages

Enzyme is not working with react v17 yet. There is a non official adapter that is working for us, until official adapter is released

Update react-spring package

React-spring renamed or removed most of their types. See here https://aleclarson.github.io/react-spring/v9/#Revamped-types . Update the returning type of our own useFlash hook.

Thanks for taking the time to do this @ValGeorgiev 🔥 Additional notes you've made help a massive amount 🚀
It looks like visual regression is working fine so I'm fairly comfortable with these changes. I'd say go ahead and merge it but if you have a short moment to try out basic user interactions (clicking around in cache/events view, triggering a request) in the full E2E (extension/standalone) - that should just ensure that event handlers are working as expected.
I'll pull your build artifact and do the same for the extension 👍


Set test case duration

@irushx Is this tested locally to verify the timing is expected? You can replace %user%/.nuget/yunit/xxx/yunit.testadapter.dll with a local build of the dll to test it in other solutions.

e dll to test it in other solutions.

@irushx Is this tested locally to verify the timing is expected? You can replace %user%/.nuget/yunit/xxx/yunit.testadapter.dll with a local build of the dll to test it in other solutions.

@yufeih yes, I tested locally.


gke: add initial step that checks for failing namespaces that have persisted for certain interval

Thinking about this more, I suggest instead of "let's find all the namespaces that are orphaned," we should make it specific to the build that's being run. Something like:

determine the namespace to be created (probably ==build_id)
schedule a job to delete that namespace after X hours (let's say 48)
create the namespace
run tests
steps after this will not run if tests fail
delete the namespace
remove the scheduled job as it's now unnecessary

To schedule the job, we can use Kubernetes Cron Scheduling.
(AFAICT, there's no kubernetes equivalent of the linux at command [which is designed for executing jobs exactly once], but I believe we can get close enough with cron... or maybe some other solution)

Issue was opened while in development, closing for now while project is in maintenance mode.


Trouble running vi in 'docker exec bash' via Docker Quickstart Terminal

Reporting a problem I hit in case useful. Fundamentally from Windows I am trying to be able to run 'vi' inside Docker container and have it work correctly without screen being scrambled when you scroll around the document.
How I repeat:
I run "Docker Quickstart Terminal" from Start menu, use 'vi' on local files, all is good. Terminal/vi works perfectly. echo $TERM reports "cygwin".
I then run "docker exec -i -t my-container bash". TERM variable is xterm. I use vi, screen gets jumbled up. I try "export TERM=cygwin" and try again, screen still jumbled up, then when I exit I get a panic message. (See below.)
So I tried a simpler test. "docker run -i -t ubuntu", similar thing (but no panic). TERM is by default set to xterm and vi does not work very well. I set to cygwin, still does not work (but exiting vi this time did not cause a panic). Note there is a "cygwin" entry in /lib/terminfo/c/cygwin.
Reporting in case the panic is interesting to you, but more fundamentally trying to work out how on Windows I can run 'vi' in a Linux container and have scrolling up/down of the document working.
oot@52f2ec8258e0:/# panic: runtime error: slice bounds out of range

goroutine 12 [running]:
bufio.(*Reader).fill(0xc08204c6c0)
        /usr/local/go/src/bufio/bufio.go:86 +0x2e2
bufio.(*Reader).WriteTo(0xc08204c6c0, 0x3725b0, 0xc08200ebe0, 0x1c4e, 0x0, 0x0)
        /usr/local/go/src/bufio/bufio.go:449 +0x285
io.Copy(0x3725b0, 0xc08200ebe0, 0x3748a0, 0xc08204c6c0, 0x0, 0x0, 0x0)
        /usr/local/go/src/io/io.go:354 +0xb9
github.com/docker/docker/api/client.func-+022(0x0, 0x0)
        /go/src/github.com/docker/docker/api/client/hijack.go:210 +0x1e0
github.com/docker/docker/pkg/promise.func-+001()
        /go/src/github.com/docker/docker/pkg/promise/promise.go:8 +0x36
created by github.com/docker/docker/pkg/promise.Go
        /go/src/github.com/docker/docker/pkg/promise/promise.go:9 +0x102

goroutine 1 [chan receive]:
github.com/docker/docker/api/client.(*DockerCli).CmdExec(0xc0820983c0, 0xc08204c
140, 0x4, 0x4, 0x0, 0x0)
        /go/src/github.com/docker/docker/api/client/commands.go:2713 +0xabc
reflect.callMethod(0xc0820f1320, 0xc08204fbe8)
        /usr/local/go/src/reflect/value.go:605 +0x180
reflect.methodValueCall(0xc08204c140, 0x4, 0x4, 0x1, 0xc0820f1320, 0xc082098401,
 0xc0821085a0, 0x5, 0xc08200eb01, 0x365da8, ...)
        /usr/local/go/src/reflect/asm_amd64.s:29 +0x3d
github.com/docker/docker/api/client.(*DockerCli).Cmd(0xc0820983c0, 0xc08204c130,
 0x5, 0x5, 0x0, 0x0)
        /go/src/github.com/docker/docker/api/client/cli.go:81 +0x385
main.main()
        /go/src/github.com/docker/docker/docker/docker.go:138 +0xb90

goroutine 5 [syscall]:
os/signal.loop()
        /usr/local/go/src/os/signal/signal_unix.go:21 +0x26
created by os/signal.init-+1
        /usr/local/go/src/os/signal/signal_unix.go:27 +0x3c

goroutine 11 [chan receive]:
github.com/docker/docker/api/client.(*DockerCli).hijack(0xc0820983c0, 0x898b90,
0x4, 0xc08206eb90, 0x4c, 0x1, 0x372580, 0xc08200eb90, 0x3725b0, 0xc08200ebe0, ..
.)
        /go/src/github.com/docker/docker/api/client/hijack.go:237 +0xd38
github.com/docker/docker/api/client.func-+015(0x0, 0x0)
        /go/src/github.com/docker/docker/api/client/commands.go:2689 +0x192
github.com/docker/docker/pkg/promise.func-+001()
        /go/src/github.com/docker/docker/pkg/promise/promise.go:8 +0x36
created by github.com/docker/docker/pkg/promise.Go
        /go/src/github.com/docker/docker/pkg/promise/promise.go:9 +0x102

goroutine 9 [IO wait]:
net.(*pollDesc).Wait(0xc08210a170, 0x72, 0x0, 0x0)
        /usr/local/go/src/net/fd_poll_runtime.go:84 +0x4e
net.(*ioSrv).ExecIO(0xc08204a0f0, 0xc08210a060, 0x89b3f0, 0x7, 0x97d8c0, 0xaf, 0
x0, 0x0)
        /usr/local/go/src/net/fd_windows.go:188 +0x305
net.(*netFD).Read(0xc08210a000, 0xc08205dc00, 0x400, 0x400, 0x0, 0x0, 0x0)
        /usr/local/go/src/net/fd_windows.go:470 +0x180
net.(*conn).Read(0xc08204a020, 0xc08205dc00, 0x400, 0x400, 0x0, 0x0, 0x0)
        /usr/local/go/src/net/net.go:121 +0xe3
crypto/tls.(*block).readFromUntil(0xc0820f08d0, 0x3740f8, 0xc08204a020, 0x5, 0x0
, 0x0)
        /usr/local/go/src/crypto/tls/conn.go:454 +0xed
crypto/tls.(*Conn).readRecord(0xc0820642c0, 0x17, 0x0, 0x0)
        /usr/local/go/src/crypto/tls/conn.go:539 +0x2e1
crypto/tls.(*Conn).Read(0xc0820642c0, 0xc08201b000, 0x1000, 0x1000, 0x0, 0x0, 0x
0)
        /usr/local/go/src/crypto/tls/conn.go:904 +0x16d
net/http.noteEOFReader.Read(0x374660, 0xc0820642c0, 0xc08209e5d8, 0xc08201b000,
0x1000, 0x1000, 0xc08200aa00, 0x0, 0x0)
        /usr/local/go/src/net/http/transport.go:1270 +0x75
net/http.(*noteEOFReader).Read(0xc0820c62a0, 0xc08201b000, 0x1000, 0x1000, 0xc08
201c000, 0x0, 0x0)
        <autogenerated>:125 +0xdb
bufio.(*Reader).fill(0xc0820ec360)
        /usr/local/go/src/bufio/bufio.go:97 +0x1d5
bufio.(*Reader).Peek(0xc0820ec360, 0x1, 0x0, 0x0, 0x0, 0x0, 0x0)
        /usr/local/go/src/bufio/bufio.go:132 +0xf7
net/http.(*persistConn).readLoop(0xc08209e580)
        /usr/local/go/src/net/http/transport.go:842 +0xab
created by net/http.(*Transport).dialConn
        /usr/local/go/src/net/http/transport.go:660 +0xca6

goroutine 10 [select]:
net/http.(*persistConn).writeLoop(0xc08209e580)
        /usr/local/go/src/net/http/transport.go:945 +0x424
created by net/http.(*Transport).dialConn
        /usr/local/go/src/net/http/transport.go:661 +0xcc3

goroutine 13 [runnable, locked to thread]:
syscall.WSASend(0x138, 0xc08210a430, 0x1, 0xc08210a418, 0x0, 0xc08210a3e8, 0x0,
0x0, 0x0)
        /usr/local/go/src/syscall/zsyscall_windows.go:1528 +0xcb
net.func-+026(0xc08210a3e8, 0x0, 0x0)
        /usr/local/go/src/net/fd_windows.go:515 +0x95
net.(*ioSrv).ExecIO(0xc08204a0f8, 0xc08210a3e8, 0x89b410, 0x7, 0x97d8d0, 0x1, 0x
0, 0x0)
        /usr/local/go/src/net/fd_windows.go:166 +0x25d
net.(*netFD).Write(0xc08210a300, 0xc0820b6000, 0x1e, 0x400, 0x0, 0x0, 0x0)
        /usr/local/go/src/net/fd_windows.go:516 +0x183
net.(*conn).Write(0xc08204a110, 0xc0820b6000, 0x1e, 0x400, 0x0, 0x0, 0x0)
        /usr/local/go/src/net/net.go:129 +0xe3
crypto/tls.(*Conn).writeRecord(0xc082064580, 0x17, 0xc082124000, 0x1, 0x8000, 0x
0, 0x0, 0x0)
        /usr/local/go/src/crypto/tls/conn.go:748 +0x4fa
crypto/tls.(*Conn).Write(0xc082064580, 0xc082124000, 0x1, 0x8000, 0x0, 0x0, 0x0)

        /usr/local/go/src/crypto/tls/conn.go:880 +0x418
io.Copy(0x374c20, 0xc0820f2440, 0x374d78, 0xc08200eb90, 0x40, 0x0, 0x0)
        /usr/local/go/src/io/io.go:364 +0x27f
github.com/docker/docker/api/client.func-+023(0x0, 0x0)
        /go/src/github.com/docker/docker/api/client/hijack.go:221 +0xe3
github.com/docker/docker/pkg/promise.func-+001()
        /go/src/github.com/docker/docker/pkg/promise/promise.go:8 +0x36
created by github.com/docker/docker/pkg/promise.Go
        /go/src/github.com/docker/docker/pkg/promise/promise.go:9 +0x102

goroutine 14 [sleep]:
github.com/docker/docker/api/client.func-+025()
        /go/src/github.com/docker/docker/api/client/utils.go:286 +0x69
created by github.com/docker/docker/api/client.(*DockerCli).monitorTtySize
        /go/src/github.com/docker/docker/api/client/utils.go:295 +0x163

akent@L-SJN-20000267 MINGW64 ~/Google Drive/GSD Book/gsd-dev/gsd-sftp
$

I'm running Windows 10 and did the following without any issues:

Open Docker Quickstart Terminal
Ran cd My\ Documents then vi desktop.ini to confirm I could view/edit the file
Ran echo $TERM and confirmed cygwin
Started a new busybox container with sh: docker run -itd busbybox sh
Exec'd into the container: docker exec -it container-id sh
Used vi etc/groups saw all groups no problem
Ran echo $TERM and got xterm

Whatever you're doing in your 'container' seems to be causing an issue. If the above scenario works properly, then it's pointing to issues with how you connect or whatever is in your my-container.

Using 'less' in busybox gives a fatal error and it drops back to Windows terminal emulator window.
$ docker run -it busybox
/ # less /etc/passwd
FATA[0062] The parameter is incorrect.
$

There is no /lib at all in busybox, so no /lib/terminfo etc describing what "xterm" means. Changing TERM to 'xxxx' does the same thing as "xterm". Basically I think busybox is a super cut down version of binaries with the terminal escape sequences hard coded into the binaries (no way to change it). So it is not useful for testing TERM settings. No matter what TERM is set to, it does the same thing.
Try using ubuntu
$ docker run -it ubuntu
root@9055e364b93d:/# vi /etc/passwd

I did some copy/paste to make file longer, then tried ^Y and ^E (display one more line at top or bottom of screen) - messes up the screen.
root@9055e364b93d:/# less /etc/passwd

Did not abort window immediately, but output was only a single page.
root@9055e364b93d:/# cat /etc/passwd /etc/passwd /etc/passwd /etc/passwd | less

Type 'u' and 'd' to scroll up/down half a page - screen gets messed up quickly.
Looking in /lib/terminfo there are terminal definitions. But 'xterm' (and 'cygwin') does not work well.
Also using vi plays up, but it is worth noting in Ubuntu "vi" is "vim", unlike busybox where "vi" is a special cut down binary with a single terminal type built in.
The fact that 'vi' does work in busybox seems to indicate there is a set of escape sequences that the terminal emulator works with well (ignoring 'less' crashing out for some reason!). I just don't know what terminal type to use for a Linux container that supports TERM settings.
Thanks!

Less works perfectly fine for me in busybox - I really think you have something going on in your terminal that's causing the issues/crashing.
Doing:
$ docker run -it busybox
/ # less /etc/passwd

Actually shows the content of the file for me and I can escape out q without any issues at all.
Same thing with the ubuntu image. which actually uses regular vi not vim.
$ docker run -it ubuntu bash
root@1dc5928237d5:/# less /etc/passwd
root@1dc5928237d5:/# vi /etc/passwd

I could then navigate with j (down) k (up) l (right) h (left)
Seems to be a problem with your system - Try on a fresh machine and report back if it still happens

Well I am baffled. I tried on another machine and works perfectly. I will try and reinstall my own laptop. Sorry for the distraction.

@alankent no worries, it's sometimes difficult to tell if the software is at fault or something on the machine is causing it. Thanks for the feedback.


Support Inverted Barcodes?

Does this support inverted barcodes? Specifically, some VIN barcodes have a black background with white barcodes, which is inverted. Will this pick those up?
If not, is there plans to support them?

It seems to actually be working ok for Code39 barcodes that are inverted, but I can't get it to read any Code128 barcodes that are inverted.


popup category filter

top right corner should have a filter button
popup dialog with semi-transparent background
with a few tags (categories)  (there's already a <Tags component)


When you click into a node menu, set selection to that node

Otherwise you can't cut/copy/paste that node

@ArcaTech - apologies for the delayed reply. it looks like it's working fine now so it must've been fixed at some point after i made the ticket. thanks! will close.


add a blog page for the project

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
as of now the blog buttons opens  nothing , would like to add it
please assign under ssoc'24
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@kairveeehh okay go ahead, Css class should be in hierarchical structure


In a block you can now add:
@formField('block_editor', ['name' => 'test'])
And these can be rendered using:
{!! $block->renderBlocks('test') !!}
todo

[x] Check the preview as it seems broken
[x] Why are all the blocks duplicated on save

relates
Should/could make #1245 no longer required as the same can be accomplished with more control.
screenshots

This is now more mature, it does not need an upgrade path. But it does simplify a lot of the internal rendering logic.

[ ] Remove the editor button on the right as it will not be supported
[ ]

.

From the docs:
Nested blocks
Since Twill 3.x it is possible to nest blocks. In theory to infinity.
To make this work you can add one or more block editors to your block.
However, you have to specify their names
resources/views/twill/blocks/nested-block.blade.php
@twillBlockTitle('Nested Block left right')
@twillBlockIcon('text')
@twillBlockGroup('app')

@formField('input', [
    'name' => 'title',
    'label' => 'Title',
    'translated' => true,
])

@formField('block_editor', ['name' => 'left'])
@formField('block_editor', ['name' => 'right'])

With the example above we now have 2 editors. One is named left and the other right.
Now, let's move over to the rendering aspect.
Basic usage
Following the documentation of block editors we know already how to render
a block.
resources/views/site/blocks/nested-block.blade.php
@php
    /** @var \A17\Twill\Services\Blocks\RenderData $renderData */
@endphp

        Left
        {!! $renderData->renderChildren('left') !!}

        Right
        {!! $renderData->renderChildren('right') !!}

$renderData is new in Twill 3.x, it is a nested representation of the data to be rendered.
Manually rendering
By default the solution above will render all the children next to each other. But if you wish to wrap the
children each in their own container you can use the getChildrenFor method on the $renderData
@php
    /** @var \A17\Twill\Services\Blocks\RenderData $renderData */
@endphp

        Left

        @foreach($renderData->getChildrenFor('left') as $leftBlock)

                {!! $leftBlock !!}

        @endforeach

        Right

        @foreach($renderData->getChildrenFor('right') as $leftBlock)

                {!! $leftBlock !!}

        @endforeach

I can merge this after the #1360

This needs to be retested after table and form builder are merged.

All done!


floppy-disk

requested icon
floppy-disk

category suggestion
item
search synonyms
save

[ ] print 用意

released in v2
https://github.com/CyCraft/pepicons/releases/tag/v2.0.0


AppSharedPackageContainer Documentation

Adding PS cmdlet help for
Add- Get- Remove- Reset- AppSharedPackageContainer

Docs Build status updates of commit 755b293:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/appx/Add-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Remove-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Reset-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 0808d2b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/appx/Add-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Remove-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Reset-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 98aa2d6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/appx/Add-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Remove-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Reset-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit e15c6f0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/appx/Add-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Remove-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Reset-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 9d33b17:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/appx/Add-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Remove-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Reset-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit d75bb5f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/appx/Add-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Remove-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Reset-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit d75bb5f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/appx/Add-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Remove-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Reset-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit b11684f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/appx/Add-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Remove-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Reset-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit b11684f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/appx/Add-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Remove-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Reset-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit b8b9809:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/appx/Add-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Remove-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Reset-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 29e8b45:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/appx/Add-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Remove-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Reset-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit ff226d8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/appx/Add-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Remove-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Reset-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

closing/re-opening PR to restart validation checks

Docs Build status updates of commit c9d3b1e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/appx/Add-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-NonRemovableAppsPolicy.md
:white_check_mark:Succeeded

docset/winserver2022-ps/appx/Remove-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Reset-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Set-NonRemovableAppsPolicy.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 6c3e789:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/appx/Add-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Remove-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Reset-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 403dd75:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/appx/Add-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Remove-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Reset-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit c752a3d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/appx/Add-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-NonRemovableAppsPolicy.md
:white_check_mark:Succeeded

docset/winserver2022-ps/appx/Remove-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Remove-AppxPackageAutoUpdateSettings.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Reset-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Set-NonRemovableAppsPolicy.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit dad61c7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/appx/Add-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Remove-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Reset-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 743d970:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/appx/Add-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Remove-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Reset-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit c752a3d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/appx/Add-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-NonRemovableAppsPolicy.md
:white_check_mark:Succeeded

docset/winserver2022-ps/appx/Remove-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Remove-AppxPackageAutoUpdateSettings.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Reset-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Set-NonRemovableAppsPolicy.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 932f277:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/appx/Add-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Remove-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Reset-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 9e81d6d:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://aka.ms/SiteHelp and include the error report for our team to troubleshoot

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 9d33b17:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/appx/Add-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Remove-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Reset-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit db80bb7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/appx/Add-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Remove-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Reset-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 35d2c24:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/appx/Add-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Appx.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-NonRemovableAppsPolicy.md
:white_check_mark:Succeeded

docset/winserver2022-ps/appx/Remove-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Remove-AppxPackageAutoUpdateSettings.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Reset-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Set-NonRemovableAppsPolicy.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 109f586:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/appx/Add-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Remove-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Reset-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 35d2c24:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/appx/Add-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Appx.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-NonRemovableAppsPolicy.md
:white_check_mark:Succeeded

docset/winserver2022-ps/appx/Remove-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Remove-AppxPackageAutoUpdateSettings.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Reset-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Set-NonRemovableAppsPolicy.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 2253978:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/appx/Add-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Get-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Remove-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/appx/Reset-AppSharedPackageContainer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 1432545:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://aka.ms/SiteHelp and include the error report for our team to troubleshoot

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 10b18f5:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://aka.ms/SiteHelp and include the error report for our team to troubleshoot

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 1a54273:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://aka.ms/SiteHelp and include the error report for our team to troubleshoot

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 109f586:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://aka.ms/SiteHelp and include the error report for our team to troubleshoot

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 35d2c24:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://aka.ms/SiteHelp and include the error report for our team to troubleshoot

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


chore(deps): upgrade compiler dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-compiler-dependencies-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2205

Questions ?
Please refer to the Backport tool documentation


Great, but this is not AI

Unlike you mentioned on your dev.to article... this is not at all AI.. basically doing if and else on the input doesn't make it AI.
Please consider changing the README as many people will land up there thinking of AI/ML.

Ya,  exactly tho ai/ml sounds cool and technical the speech recognition is using ml this is not enough to call this thing based on ai

I agree. This is just a bunch of if-else that's all.

@manthanabc The speech recognition is external and not a part of this project anyways.
I'm just not happy with the fact that it is mentioned it is an AI and stuff but ultimately it is a 10 year old kid's if..else project lmao..
I mean writing the dev.to article for if..else work is misleading

@divy-work I was also surprised that this project was trending. Now your issue clears everything.
So the understanding is much more flexible. Maybe you wanna check it out:
https://github.com/Tristi-X/F.R.I.D.A.Y


Make stable

Hi,
Hyper now depends on Electron 1.7.6, so it can handle Touch Bar in vanilla.
I just added your plugin to the config and it started working instantly. The README needs an update.

I've noticed! However I haven't tested it again ever since, haha. I'll update the readme when I get home.

My celebrations were preliminary, the buttons render alright, but I'm getting exceptions after pressing them. Still, I assume this is fixable.
Uncaught Exception:
TypeError: Cannot read property 'write' of undefined
    at Object.click (~/.hyper_plugins/node_modules/hyper-touchbar/index.js:44:37)
    at TouchBarButton.onInteraction (/Applications/Hyper.app/Contents/Resources/electron.asar/browser/api/touch-bar.js:169:16)
    at BrowserWindow.interactionListener (/Applications/Hyper.app/Contents/Resources/electron.asar/browser/api/touch-bar.js:109:14)
    at emitThree (events.js:116:13)
    at BrowserWindow.emit (events.js:197:7)

Hey @viktorsec - I can't seem to reproduce... It works fine for me. Does it work okay for you now by any chance?

I just ran into this error - restarting Hyper was all it took to solve it.


[ci] Resolve issues with MacOS wheel-file smoke test

Follow up from https://github.com/single-cell-data/TileDB-SOMA/pull/2620#issuecomment-2127661222
[sc-48079]

Last few relevant changes to the macOS wheel-build and smoke-tests in python-packaging.yml:

X86
ARM

PR
macOS
wheel build
smoke-test
macOS
wheel build
smoke-test

#1385 (May '23)
11
✅
✅
🚫 → 12
🚫 → ✅
🚫

#2594 (5/20/24)
11 → 12
✅
✅
12
✅
🚫

#2491 (5/21/24)
12 → 14
✅
❌
12
✅
🚫

#2620 (5/23/24)
14 → 12
✅
❌ → 🚫
12 → 14
✅
🚫

(✅/❌ = link to representative GHA run, 🚫 = not implemented)
#2594 was the best state to date:

macos-12 x {x86,arm} wheels built, x86 smoke-test passed

macos-12 EOL is in Q4 (as opposed to macos-11 Q2)

No one has gotten macos-14 smoke-tests to work (for x86 or ARM)

#2640 puts us back on macos-12, where at least the x86 smoke-test works. It also adds smoke-tests for Python 3.10 (in addition to 3.11) and parallelizes and cleans up the GHA, for better DX.
Going forward, we can get macos-14 working, or explore an incremental upgrade to macos-13 in the meantime.

Adding a row to the table above to reflect the current state:

X86
ARM

PR
macOS
wheel build
smoke-test
macOS
wheel build
smoke-test

#1385 (May '23)
11
✅
✅
🚫 → 12
🚫 → ✅
🚫

#2594 (5/20/24)
11 → 12
✅
✅
12
✅
🚫

#2491 (5/21/24)
12 → 14
✅
❌
12
✅
🚫

#2620 (5/23/24)
14 → 12
✅
❌ → 🚫
12 → 14
✅
🚫

#2640/#2641 (5/24/24)
12
✅
🚫 → ✅
14
✅
🚫 → ✅


Change forked-to links to button

Description
Change the forked-to links below the repo name, to a button next to the Fork button.
The design changes depending on the amount of forks:

0 = no extra button.
1 = extra button is link to your fork.
> 1 = extra button opens menu, which contains list of all your forks.

Screenshots
0 forks:

1 fork:

2 forks:

Play nice with hide-watch-and-fork-count feature:

Closes
Discussion https://github.com/sindresorhus/refined-github/pull/2214 & https://github.com/sindresorhus/refined-github/pull/2216
Follows https://github.com/sindresorhus/refined-github/pull/2153 & https://github.com/sindresorhus/refined-github/pull/2216
Supersedes https://github.com/sindresorhus/refined-github/pull/2214

/cc @bfred-it, @karlhorky, @1138-4EB

forks:

I just realized that this is the same exact content that the regular Fork button, minus the change to create more forks. It doesn't make much sense to have two buttons that do the same thing.
Suggestions:

1 fork is fine like you're showing
when there are multiple forks:

add a ▼ to the Fork button (as a visual indicator)
preload the lightbox

always:

listen to the lightbox loading and adjust its DOM to display as a dropdown instead; maybe its content should just change from details-dialog to details-menu

Thoughts?

Not sure I like this better, but here it is:
2 forks button:

2 forks menu:

Not sure I like this better, but here it is:

I definitely think that the first one is better than this. I believe the way to go would be to add the 'Create new fork' item as an 'additional fork item' in https://user-images.githubusercontent.com/55841/61155136-6bd8fe00-a4f0-11e9-941c-e55647a8eadf.png. Hence, in practice, this PR will 'convert the modal into a dropdown menu'.

I definitely like the first custom dropdown menu, but I do agree with @bfred-it that the custom menu and build-in dialog are almost the same.
What if we just replace the build-in fork dialog with the custom dropdown menu. And append (like @1138-4EB said) an menu-item to create a fork (an action that is only done once per user/organization, accepting the one extra click).

Design 3; this replaces the build-in fork dialog with an custom fork dropdown menu. It includes 2 or more fork links, plus a link to create a new fork.
0 forks:

1 fork:

2 forks (https://github.com/sindresorhus/refined-github/pull/2230/commits/e9522f170ab1e3d14ceaab1cdaa057052687f1f8), button:

2 forks (https://github.com/sindresorhus/refined-github/pull/2230/commits/e9522f170ab1e3d14ceaab1cdaa057052687f1f8), menu:

P.s. hiding the build-in dialog should be improved.

This would then slow down the creation of more forks. My suggestion was to reuse the same light box content (all of it, but adjusted with some classes) to look like a dropdown. The dark shadow can also be dropped

@bfred-it commented on Jul 14, 2019, 4:09 AM GMT+2:

This would then slow down the creation of more forks. My suggestion was to reuse the same light box content (all of it, but adjusted with some classes) to look like a dropdown. The dark shadow can also be dropped

Design 2 thus: https://github.com/sindresorhus/refined-github/pull/2230#issuecomment-511146632 (without the dark shadow) ?

Design 3 of course is better-looking but it's best to also include the other links in that lightbox:
# Your forks
% user/repo
% org/repo

# Create fork
% org2
% org3
% org4 (no permission) `disabled`

As for our cache, we only need to store the first fork, for 2 reasons:

a filled cache means we have to validate it, i.e. we'll have to preload the dropdown
we don't actually need the list of forks in the cache because we'll only ever show it after the dropdown is preloaded

Just an heads-up; I'm still working on this. The button is done, and the forks list is created, I just need to read the fork dialog to get the missing organizations. To be continued...

Something to keep in mind: users without organizations don't have a popup:
<form class="btn-with-count" action="/chartjs/Chart.js/fork" accept-charset="UTF-8" method="post">
            <button class="btn btn-sm btn-with-count" data-hydro-click="{"event_type":"repository.click","payload":{"target":"FORK_BUTTON","repository_id":8843683,"client_id":"1512404804.1558770078","originating_request_id":"F8AF:14C9:984A6D:DCBCD6:5D3EC08B","originating_url":"https://github.com/chartjs/Chart.js/tree/6632b8ba8475e020fd0533e2630117376a9cbc73","referrer":null,"user_id":53252526}}" data-hydro-click-hmac="4fc7804f0046d6c8bdca3e655e7d8efee5bf3569d3f8ce0683b5f8515fa86bc8" data-ga-click="Repository, show fork modal, action:files#disambiguate; text:Fork" type="submit" title="Fork your own copy of chartjs/Chart.js to your account" aria-label="Fork your own copy of chartjs/Chart.js to your account">              {SVG icon}
              Fork
</button></form>

This code seems unchanged whether I already have the fork or not

x forks:

% org4 (no permission) disabled

There appears to be no disabled state for select-menu.

Looks good in the screenshot! Is this done?

@fregante This PR is restored to design 1. Feel free to make changes if required.

Thanks! This makes the feature more refined!
I'll keep this as the last comment as a to-do

[ ] await updateForks(forks) should probably be replaced by that code that triggers the lightbox to load, so our existing load handler can check all the forks at once. updateForks and validateFork can then be dropped altogether.


Torch mode in video instead of flash mode

Hi, I just found an issue with the torch mode of the camera when recording video. Currently in your code you're toggling flashMode of the device, which should be replaced with torchMode for the feature to work properly.
Anw, thanks for the library!

Thank you it helps!

@itsmeichigo Closing due to the age of the ticket. If you could open a PR it'd be appreciated.


Support multiple SOTA/POTA in same input file

If I am activating several SOTA summits in a single trip, is it possible to add support for multiple SOTA (or POTA/WWFF etc.) in the same FLE file?
For example:
#Header
mycall MW0PJE/P
mysota GW/NW-001
#Log
2m FM
1000 mw0abc
01 mw0abd
.
.
.
mysota GW/NW-002
1200 mm0abe
01 mm0abf
.
.
.
mysota GW/NW-003
1400 mi0abg
01 mi0abh

In SOTA CSV (maybe also in ADIF) you can have more than one summitin the same output file.
pete

The enhancement request has been mentioned to Bernd (DF3CB), developer of the Windows application.

Christophe, ON6ZQ, confirms that it is supported in the SOTA output.
It needs to be investigated whether this would work for POTA or WWFF.

Feature can be tested with ./FLEcli csv -i test/data/multi-SOTA-summits.txt  --overwrite
The load file should be updated first as it currently fails as expected with:
Processing errors:
Attempt to redefine MySOTA at line 12
Attempt to redefine MySOTA at line 17

The log output, currently:
MyCall    MW0PJE/P
MySOTA    GW/NW-001

Date       Time Band Mode Call         Sent Rcvd Notes
----       ---- ---- ---- ----         ---- ---- ----
2016-04-24 1000 2m   FM   MW0ABC       59   59
2016-04-24 1001 2m   FM   MW0ABD       59   59
2016-04-24 1200 2m   FM   MM0ABE       59   59
2016-04-24 1201 2m   FM   MM0ABF       59   59
2016-04-24 1400 2m   FM   MI0ABG       59   59
2016-04-24 1401 2m   FM   MI0ABH       59   59

The log output should be something like:
MyCall    MW0PJE/P
MySOTA    GW/NW-001

Date       Time Band Mode Call         Sent Rcvd Notes
----       ---- ---- ---- ----         ---- ---- ----
2016-04-24 1000 2m   FM   MW0ABC       59   59
2016-04-24 1001 2m   FM   MW0ABD       59   59

MyCall    MW0PJE/P
MySOTA    GW/NW-001

Date       Time Band Mode Call         Sent Rcvd Notes
----       ---- ---- ---- ----         ---- ---- ----
2016-04-24 1200 2m   FM   MM0ABE       59   59
2016-04-24 1201 2m   FM   MM0ABF       59   59

MyCall    MW0PJE/P
MySOTA    GW/NW-001

Date       Time Band Mode Call         Sent Rcvd Notes
----       ---- ---- ---- ----         ---- ---- ----
2016-04-24 1400 2m   FM   MI0ABG       59   59
2016-04-24 1401 2m   FM   MI0ABH       59   59


DS-R: 1.2.DOC History - History of Data Science #140

Description 📜
Made a document on the topic of the History of data science.
Fixes #140

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] Datascience with R

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.

[x] I have performed a self-review of my own code or work.

[x] My changes generates no new warnings.

[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

@micepram, Kindly evaluate the PR.
Batch - 1
serial number: 12
Name: M. Ashish Reddy

@micepram , Can you kindly merge this PR if everything is ok . So that i can work on other pr's.

@micepram , Can you kindly merge this PR if everything is ok . So that i can work on other pr's.

Hey, the content seems to be plagiarized. You're free to rephrase the sentences but please don't copy.

@harshita2319 , can you please review it mam. I have changed the sentences.

Check Plagiarism
After running your content through, I get 72% plagiarized. Please rephrase content and reference the sources @ashish-reddy-20-08 and bring it down to below 30% at a minimum.

@micepram, @harshita2319  , can you please evaluate , I have made the changes.

@micepram  , @harshita2319 , PLEASE REVIEW THE PR AND MERGE IT IF EVERYTHING IS FINE.


Update build scripts

Updated NuGet to v3.3.0

Appears to give a nice speed boost when installing packages, using AppVeyor as a benchmark, there's a ~2 minute reduction in the time it takes to acquire packages, compared to the current version of nuget the build script uses.

Updated Cake to 0.8.0 and Cake.CMake to 0.0.2
Created a 'publish' directory and copied all files to be published to it

Converted the Build-Installer task & PicoTorrent.wxs installer script to use the 'publish' directory
Converted the Build-Portable-Package task to zip the 'publish' directory, to automatically grab any new translation files

Added newest translation files to PicoTorrent.wxs installer script

Not familiar with the WiX toolset, so not sure if it's possible or recommended to add an entire directory at once, instead of individual files

Great work @zp! Merge whenever :smile:
Regarding WiX - you cannot add a whole directory at once, but you can use Heat to generate a file list. Might be overkill right now, but may be something to consider if we get a lot of languages.


Update aka.ms/azsdk/onboarding/informational with new Onboarding wiki

We will have a new more generic wiki for the Informational meetings. Once it is ready, we need to update this aka.ms link and make sure that it is the one we consume on our scheduling tool and email templates

@maririos - I have 2 Azure SDK Informational Meeting wiki pages.
Azure SDK Information Meeting
AKA links

[ ] Create new AKA for https://aka.ms/azsdk/onboarding/informational, link to wiki page - https://dev.azure.com/azure-sdk/internal/_wiki/wikis/internal.wiki/773/Azure-SDK-Informational-Meeting
[ ] AKA link to the scheduling tool information meeting power app - https://aka.ms/azsdk/scheduleinformational
[ ] AKA link to the agenda wiki page for Azure SDK Information Meeting - data plane follow-up - https://aka.ms/azsdk/onboarding/dpinfomeeting

Conditional triggers for informational meeting agenda for data plane
IF product ADO work item field or dataverse table field "information mtg data followup" state equals incomplete, THEN use the https://aka.ms/azsdk/scheduleinformational ELSE use https://aka.ms/azsdk/onboarding/informational.
TODO:  I will open a GitHub issue for Azure SDK Release Planner Beta V1 for the "information mtg data followup" field.

It turns out I am not an owner of https://aka.ms/azsdk/onboarding/informational, I have requested access to it so I can modify it with the new wiki you created

It turns out I am not an owner of https://aka.ms/azsdk/onboarding/informational, I have requested access to it so I can modify it with the new wiki you created

Great, I could not find the link aka tool so did not know who owned it.  :-)

Link has been updated :)

Conditional triggers for informational meeting agenda for data plane
IF product ADO work item field or dataverse table field "information mtg data followup" state equals incomplete, THEN use the https://aka.ms/azsdk/scheduleinformational ELSE use https://aka.ms/azsdk/onboarding/informational.
TODO: I will open a GitHub issue for Azure SDK Release Planner Beta V1 for the "information mtg data followup" field.

Sounds good!
So looks like this issue is all done, right?

Correct this is done. This issue will have a dependency on the issue I need to open for the "informational mtg data followup".  I will open that tomorrow.

I think that we can trigger to use the appropriate template by using a drop-down box for service partners to identify what type of follow-up meeting.   See this GitHub issue - https://github.com/Azure/azure-sdk-tools/issues/3788.


Add GitHub Action to check Jekyll build of docs on on all PR checkins.

This PR adds a GitHub Action to check the Jekyll build whenever a PR is created or updated.

Forgot to mention ...
The current Travis build appears to be a pretty old setup to build the DocBooks version of the CF conventions docs. The .travis.yml calls generate.sh which runs make on Data/cf-conventions/cf-conventions-1.*/makefile. It is currently failing because there is no makefile in the 1.8 directory.
I will submit another PR removing the Travis, .sh, and make files along with some of the extra stuff left in the various Data subdirectories from old builds.

I'm going to merge this in so we can start testing PRs.
I will look at how to require reviews for this type of PR, probably by members of the info-mgmt team ( @cf-convention/info-mgmt ). And will submit another PR on that.


can not work by 'p' and 'esc' key

Hi, I don't know why the key can't wok, and I cannot label the target to tracking

Confirmed, keyboard does not work at all on Linux, OpenCV 2.4.

I am also facing this issue doesn't work after pressing key 'p'. Please help someone ??

Hi, Even I was facing similar problem, was not able to pause the video by pressing 'p'.
Solution to make it work is given below.
In object-tracker-single.py & object-tracking-multiple.py
Replace line 23 by 2 lines given below
Line23 :  if(cv2.waitKey(10)==ord('p')):
Replace :
key=cv2.waitKey(1) & 0xff
if(key==ord('p'))
In get_points.py
Replace line 52 by command given below
Line 52:  key = cv2.waitKey(30)
Replace :
key=cv2.waitKey(1) & 0xff
By changing the above mentioned lines one will be able to execute the tracker successfully.

@bhatshashank please open a pull request if you think that solved the problem

I have solved the issue. Opened a pull request. Until not accepted, you can use my forked repo.


Invalid token... invalid audience

Was able to upload the sample webapp on GAE but when I try to access, I am getting an Invalid error blah blah blah: Invalid audience. I have used the "github.com/ConradIrwin/xsrftoken" instead of "github.com/adg/xsrftoken". I also have updated the oauth2 library because I am getting an invalid string clientID being moved to audience []string. Now, when I test the webapp in browser, I am just looping around the login screen screen. Then, checking the log in GAE, I am getting an invalid token. Is there anyone who has been able to make this toolkit work?
	var clientID []string
	clientID = append(clientID, fmt.Sprintf("%v", clientIDx))
	aelog.Infof(c,"clientID: %v", clientID)
	token, err := gitkitClient.ValidateToken(c, ts, clientID) <-- this maps to audience []string which errors our when directly pass the clientID as string only. Not sure if this is the one that causes the invalid token issue or the broken xsrf library?

I could deploy favweekday on GAE. login works without problem.
I used "github.com/adg/xsrftoken".

I see... So maybe there is just something wrong with my setup. May I know why the adg/xsrftoken is getting an error like below?
go get github.com/adg/xsrftoken
can't load package: package github.com/adg/xsrftoken: no buildable Go source fil
es in C:\Development\go-path\src\github.com\adg\xsrftoken

When I tested adg/xsrftoken existed, now it gives 404.
If I make it work with https://github.com/ConradIrwin/xsrftoken I'll let
you know.
On Sat, Apr 2, 2016 at 9:33 AM, edwindvinas<EMAIL_ADDRESS>wrote:

I see... So maybe there is just something wrong with my setup. May I know
why the adg/xsrftoken is getting an error like below?
go get github.com/adg/xsrftoken
can't load package: package github.com/adg/xsrftoken: no buildable Go source fil
es in C:\Development\go-path\src\github.com\adg\xsrftoken
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/googlesamples/identity-toolkit-go/issues/12#issuecomment-204666967


Create an option to not remove machines (created through UI bydocker-machine) with purging environment

We implemented removing the machines that were created from the UI/API using docker-machine whenever an environment was purged.
There may be a slim use case that users might want NOT want the machines purged.
If enough users request it, we can add the option in to OPT OUT of removing the machines.

Closing due to inactivity.  This isn't something we will add.


feat: add ARCx Governance Token

Hey, Kerman (https://twitter.com/kermankohli) founder of ARCx (arcx.money) here. We'd like to get the ARCx token added on Sushiswap so that users don't have to type in the address and it shows as an untrusted token.

Any insights as to why this is failing?


🐛Cherrypick Add live-iso option to Image's DiskFormat for v1a5 in release-0.5

This PR will add the live-iso option for v1a5 in release-0.5 branch and changes are done according to main branch #527

/test generate

Closing PR because of the go version mismatch issue.


Duplicate identifier error

Node Version: 6.9.1
Protractor Version: 4.0.11
Angular Version: 2.1.2
Operating System and Version chrome, ubuntu 16 LTS
Your protractor configuration file

exports.config = {
    seleniumAddress: 'http://localhost:4444/wd/hub',
    specs: ['./protractor/**-spec.js'],

    // Capabilities to be passed to the webdriver instance.
    capabilities: {
        'browserName': 'chrome'
    },

    // Options to be passed to Jasmine-node.
    jasmineNodeOpts: {
        showColors: true
    }
};

Shouldn't https://github.com/angular/protractor/blob/master/package.json#L15 be declared as a dev dependency?
Opened up this bug after submitting: https://github.com/DefinitelyTyped/DefinitelyTyped/issues/13064
I've started a new angular2 project and included the following dev dependency:
"@types/mocha": "2.2.33",
It installs correctly however when I run:
webpack --config webpack.config.dev.js --progress --profile --watch
I get:
[at-loader] node_modules/@types/jasmine/index.d.ts:15:18
    Duplicate identifier 'xit'.

[at-loader] node_modules/@types/mocha/index.d.ts:33:13
    Duplicate identifier 'describe'.

[at-loader] node_modules/@types/mocha/index.d.ts:34:13
    Duplicate identifier 'xdescribe'.

[at-loader] node_modules/@types/mocha/index.d.ts:39:13
    Duplicate identifier 'it'.

[at-loader] node_modules/@types/mocha/index.d.ts:40:13
    Duplicate identifier 'xit'.

My webpack config file:
var webpack = require('webpack');

module.exports = {
    devtool: 'cheap-module-eval-source-map',

    output: {
        path: './public/js/app',
        publicPath: "/js/app/",
        filename: 'bundle.js',
        chunkFilename: '[id].chunk.js'
    },
    entry: {
        'app': './assets/app/main.polymer.ts'
    },

    resolve: {
        extensions: ['.js', '.ts']
    },

    module: {
        loaders: [
            {
                test: /\.ts$/,
                loaders: [
                    'awesome-typescript-loader',
                    'angular2-template-loader',
                    'angular2-router-loader'
                ]
            },
            {
                test: /\.html$/,
                loader: 'html'
            },
            {
                test: /\.css$/,
                loader: 'raw'
            }
        ]
    },

    plugins: [
        new webpack.ContextReplacementPlugin(
            // The (\\|\/) piece accounts for path separators in *nix and Windows
            /angular(\\|\/)core(\\|\/)(esm(\\|\/)src|src)(\\|\/)linker/,
            './src' // location of your src
        )
    ]
};

Same thing happens with @types/jasmine:
Just found out that the errors:
[at-loader] node_modules/@types/jasmine/index.d.ts:9:18
    Duplicate identifier 'describe'.

[at-loader] node_modules/@types/jasmine/index.d.ts:11:18
    Duplicate identifier 'xdescribe'.

[at-loader] node_modules/@types/jasmine/index.d.ts:13:18
    Duplicate identifier 'it'.

[at-loader] node_modules/@types/jasmine/index.d.ts:15:18
    Duplicate identifier 'xit'.

Apparently this happens when I write my tests with mocha and use protractor for e2e tests.

Yup, we'll change this. Thanks for reporting it.

@cnishina created pull request https://github.com/angular/protractor/pull/3793

Since this is a potential breaking change to existing jasmine users, I've opened PR #3795 to fix this in the upcoming release for selenium3 in the beta branch. This specific package does not require import {it} from 'jasmine' similarly to how the the mocha typings are written. This is a good idea to move this out.
We still use q types in plugins and I believe that should be included until we eventually remove q. Also, we export some @types/selenium-webdriver under the Protractor typings so that should be maintained.
A work around would be to set your types array in your tsconfig and to not include jasmine type:

{
   "compilerOptions": {
       "types" : ["node", "lodash", "express"]
   }
}

This tsconfig.json file will only include ./node_modules/@types/node, ./node_modules/@types/lodash and ./node_modules/@types/express. Other packages under node_modules/@types/* will not be included.

from https://www.typescriptlang.org/docs/handbook/tsconfig-json.html

closed with https://github.com/angular/protractor/pull/3795


!user command says if a user is "Verified", rather than "Pending"

Previously, the !user command would tell mods if a user is "Pending", which is True before they are verified and False thereafter. I think most of us are interested in whether or not they are "Verified", which is False when they are pending and True otherwise. This PR aligns the message in the embed with the expected semantics.

Coverage remained the same at 56.442% when pulling fc8a1246b281fd0d495955e0b84c6fc75a59ba4d on swfarnsworth/info into 6e440d9c6d0ad2df472290ac0b2ef2a89f9159f9 on master.


Unexpected error when implementing mergesort

I tried proving the correctness of mergesort and got "Unexpected error Failure("Bound term variable not found: sl1")"
I stripped down the code to this piece here:
module MergeSort
open List

assume val split : list int ->  (list int * list int)

assume val merge: l1:list int -> l2:list int ->
           Tot (l:list int { (forall x. (mem x l1 \/ mem x l2 <==> mem x l)) })

val mergesort: l:list int -> (list int)
let rec mergesort l = match l with
  | [] -> []
  | [x] -> [x]
  | _ ->
    let (l1, l2) = split l in
    let sl1 = mergesort l1 in
    let sl2 = mergesort l2 in
    merge sl1 sl2

I first thought that fstar fails while proving termination, but making split and mergesort total or not seems not to make a difference.

Hi Yannick, Seems you weren't the only one who had this problem, Enrico had it too. Hope you managed to somehow work around it for the homework.
Marking this as a duplicate of #170, because that has an even smaller file (saw this too late, sorry).