Cannot open multiple {headless: false} browsers on macos arm

Minimal reproducible example:
main.ts:
import { launch } from "jsr:@astral/astral";

function randomIntFromInterval(min: number, max: number): number {
  return Math.floor(Math.random() * (max - min + 1) + min);
}

async function performTask() {
  // Launch the browser
  const browser = await launch({ headless : false });
}

async function runMultipleBrowsers() {
    for (let i = 0; i < 2; i++) {
      await new Promise((resolve) => setTimeout(resolve, randomIntFromInterval(0, 1000)));
      performTask();
    }
}
runMultipleBrowsers();

deno run --allow-net --allow-env --allow-read --allow-write --allow-run main.ts

Macos version: 14.7 (23H124) (Sonoma)
Error:
Process exited with code 0
error: Uncaught (in promise) Error: Your binary refused to boot
    throw new Error("Your binary refused to boot");
          ^
    at runCommand (https://jsr.io/@astral/astral/0.4.8/src/browser.ts:65:11)
    at eventLoopTick (ext:core/01_core.js:175:7)
    at async launch (https://jsr.io/@astral/astral/0.4.8/src/browser.ts:289:33)
    at async performTask (file:///Users/tom/programming/tade/bot/minimalExample.ts:9:19)
Process exited with code 1

It works completely fine when I launch only one browser instance or if I launch with {headless:true}.
The problematic line:
https://github.com/lino-levan/astral/blob/7ce5b21da5bd91b03df2e80c9ab3998cfeb123ed/src/browser.ts#L65

I've found that this issue is not present in the deno.land 0.3.5 version. Hovewer it is present when you switch to the jsr version (since 0.3.6).

I've found more context. This is because the browser is opening within an existing context. That means that the executable will just exit with an exit code 0 more info on that here.
The solution I'm proposing is to always generate a new browserContext.
I've added an example of how that could be done in #111. I'l leave the implementation up to you.
Thanks for your work.

We already open the browser in a unique context each time. Maybe that code is broken but I find it a little unlikely given other tests would test for it. The thing that is particularly weird to me is that this only happens when headless is off.


Add gpt-4-turbo

https://platform.openai.com/docs/models/continuous-model-upgrades

gpt-4-turbo  is available on https://www.chatbotui.com/

It's currently set to the old version.

i opened a MR for that: https://github.com/mckaywrigley/chatbot-ui/pull/1672

Are there any further plans to support GPT-4 Turbo to the self-hosted chatbot-ui version?

Gpt4o has been pushed, so i think this issue can be closed


Attempting to test with Vitest

I decided to take a stab at getting your tests you wrote to work with Vitest since it is the new hotness.
I am getting close but getting this weird error, and since I don't know C++ I don't know what it means heh

yes it might be related with #4 , at some point i need to go back on the C++ side and see how to solve that.
besides that, going CommonsJS or ES6 modules should not cause any major issue.
that would be a cool enhancement.

this is nice ;-) i have a PR to enable it to run on every commit but as you can imagine we're limited by the lack of gpio pins on github runners 😅
anyway, please open a PR to the repo when you feel you get a time so we can offer this to everyone consuming this library.

Hi @khill-fbmc !
This is one issue i could address along the 'testing mode' for the library.
In order to proper cover the library with tests, i will need to simulate gpiopins so it can be transparent for the javascript wrapper if we are in a real hardware of inside a github runner or something.
my findings so far point to use exactly what ligpiod itself uses to test: https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/tree/tests/Makefile.am?h=v1.6.x
but we can also make use of some environment variables to override a few things, the operating system environment for instance.
we could create a set of prefixed environment variables to override our system checks, for example NODE_LIBGPIOD_OS_TYPE ; lib bootstrap would stilll performing the check, but the env var would take precedence and then we use that.
i plan to spare time this weekend to move forward to it, we can discuss good overrides for this situation and others

still blocked by #24

issues cleanup.
our mocha test suite still need improvements, vite would be good, if the gpio-sim gets completely figured out on github actions besides local development.
we can back to the topic in the future, focusing on complete API parity for now, we still lack bulk read/write and callbacks.

No worries! I did drive through in classic ADHD style, do some work that was interesting right then, and now I am miles away 🙃


server

Checklist

[ ] I've searched for similar issues.
[x] I'm using the latest version of HTTPie.

Minimal reproduction code and steps

Current result
…
Expected result
…

Debug output
Please re-run the command with --debug, then copy the entire command & output and paste both below:
$ http --debug <COMPLETE ARGUMENT LIST THAT TRIGGERS THE ERROR>
<COMPLETE OUTPUT>

Additional information, screenshots, or code examples
…

fix isus


SAK-40027 (Assignments) Multi node caché issues

This PR reverts #5745 because we have tested on our multinode servers and Version wasn't been updated when submissions were created so there was still a race condition.
It was only necessary to remove the submissions cache on Assignment Hibernate object.
We were worried about the benchmarks being a lot worse but that's not been the case. I attach two documents for you to see the difference. These documents are in spanish but text is quite simple.
If there are any doubts about this maybe @adrianmticarum  or @juanjmerono can help to clarify them.
Our tester has been @jesusmmp , if you people need anything too
Bulk automatic tests (first column with cache, 2nd column without it):

Manual tests on some sites from 20 to 200 users (instructor and students)
Pruebas caché Assignment - Hoja 1.pdf

@ern I've updated PR. We have tested on our servers and it's still working right.


feat(home): Redesign Home Page & fix(fonts): Fonts not showing the right style

Updated the UI for the Home Page from Figma.
In the previous PR (#181) I made, I forgot to include the new font files (sorry abt
that), which messed with the site's styling. I was told to include it in this PR instead of making a new one.

hi geeth can u change the header to be more bold

The challenge arrows on mobile are messed up. Also, the keynote speaker descriptions don't show the bottom.

@abdullah50053 they are temporary as kelly didn't find the design yet for them.

First FAQ is centered, others are left aligned.

Reduce gap between "meet the team" title and content:

fixed the issues

This is negative mobile accessibility rizz :(( It's hard to see the left/right buttons plus it overlaps with the text.

i'll remove the arrows on mobile

wait but if we remove arrows on mobile then ppl wont know to swipe which means negative UX accessibility rizz

i will make it look like this...

that's W accessibility rizz


Global

replace "en-us" to "zh-cn" in the link.
ex:
LAB_07_Implementing_migration_in_hybrid_scenarios.md
https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2022
to
https://www.microsoft.com/zh-cn/evalcenter/evaluate-windows-server-2022

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

https://github.com/MicrosoftLearning/AZ-801-Configuring-Windows-Server-Hybrid-Advanced-Services.zh-CN/blob/OLPRODLOC/Instructions/Labs/LAB_07_Implementing_migration_in_hybrid_scenarios.md
https://github.com/MicrosoftLearning/AZ-801-Configuring-Windows-Server-Hybrid-Advanced-Services.zh-CN/blob/OLPRODLOC/Instructions/Labs/LAB_AK_07_Implementing_migration_in_hybrid_scenarios.md

fixed

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team


Rendering only one image

Hi, I tried applying the rendering to a body with a png texture but it's rendering the whole canvas and other objects. Any clue what am I doing wrong? my project has setup and draw functions for each object. Thanks

It's hard to tell without seeing your code. Are you sure you applied it to just that particular body? See example below:
const box1 = Bodies.rectangle(x, y, 64, 64, {
    strokeStyle: '#ffffff',
    sprite: {
        texture: './img/box.png'
     }
 }

hey thanks for replying
this is in the setup function of the single body:
var opt = {restitution: 0.95,
friction: 0,
render: {
sprite: {
texture: 'assets/ball.png',
xScale: 0.2,
yScale: 0.2}
}};
ball = Bodies.circle(50, 50, 20,opt);
and this in the general setup:
var render = Render.create({
element: document.body,
engine: engine,
options: {wireframes: false }});
Render.run(render);
if I remove the code above in the general setup, nothing happens, otherwise it creates a second canvas below the original with the image I was trying to render and other objects affected. I'm not sure what I'm doing wrong...

I've just modified the base starter code from the Matter.js site and added a sprite on the ball object. Can you try this code and see if it works for you, and if so maybe try to see any differences in your code. Again, it's quite difficult to know what's going wrong without seeing all your code. Not sure if you can save it in replit, github, etc.?
// module aliases
var Engine = Matter.Engine,
    Render = Matter.Render,
    Runner = Matter.Runner,
    Bodies = Matter.Bodies,
    Composite = Matter.Composite;

// create an engine
var engine = Engine.create();

// create a renderer
var render = Render.create({
    element: document.body,
    engine: engine,
    options: {
        wireframes: false
    }
});

var opt = {
  restitution: 0.95,
  friction: 0,
  render: {
    sprite: {
      texture: 'assets/ball.png'
    }
  }
};

const ball = Bodies.circle(300, 50, 50, opt);

const box = Bodies.rectangle(200, 100, 50, 80);

var ground = Bodies.rectangle(400, 610, 810, 60, { isStatic: true });

// add all of the bodies to the world
Composite.add(engine.world, [ball, box, ground]);

// run the renderer
Render.run(render);

// create runner
var runner = Runner.create();

// run the engine
Runner.run(runner, engine);

In my code I have boxes and balls. I've tried your code but it's still showing me the 2 canvases next each other, where the second is rendered with different colours for the boxes and the texture for the balls. Boxes and balls are in different functions: 2 setups functions and 2 drawing functions each called in the main setup and draw functions. Any clue what's making a copy of the canvas? It just appears when I add
// create a renderer
var render = Render.create({
element: document.body,
engine: engine,
options: {
wireframes: false
}
});
// run the renderer
Render.run(render);

Hi - not entirely sure what you mean by two separate draw functions? Are you able to share more of your code to see exactly what's happening. Or maybe save your project into github, codepen, replit, etc.
It sounds like you might be using the Matter renderer to draw the objects as well as some other graphics engine such as P5.js, the native canvas API, etc. which might be causing the duplication, but can't be sure without seeing more of the code.

Hopefully this one was resolved so closing, thanks all.


docs(subscription): fix duration doc types

Fixes #653

[ ] Tests and linter pass
[x] Code coverage does not decrease (if any source code was changed)
[x] Appropriate docs were updated (if necessary)

/cc @kamalaboulhosn


How to use HiFi-GAN with mel-spectrogram from Tacotron

Hi
Thanks for this great implementation.
I trained Tacotron and used WaveRNN as vocoder and result was good. Now I want to use HiFi-GAN as vocoder so I cloned this project and run it with mel-spectrogram reached from Tacotron. But result was very noisy! You can listen to result here and some prints are as follow:
x = synthesizer.synthesize_spectrograms(texts, embeds)
print(x)
with torch.no_grad():
    x = torch.from_numpy(x).to(device)
    x = x.unsqueeze(0)
    print(x.shape)
    y_g_hat = generator(x)
    audio = y_g_hat.squeeze()
    audio = audio.cpu().numpy()

[[-3.7809916 -3.7548614 -3.810056  ... -3.900182  -3.9460294 -3.812808 ]
[-3.9151711 -3.9173453 -4.018536  ... -3.9720445 -4.00277   -3.8934054]
[-3.8845775 -3.906875  -4.005348  ... -3.9689758 -3.9909463 -3.8506253]
...
[-3.4353547 -3.374465  -3.3435407 ... -3.312714  -3.3319786 -3.4587195]
[-3.4256952 -3.3695805 -3.339043  ... -3.3475647 -3.3527846 -3.4885204]
[-3.49198   -3.4372733 -3.4019573 ... -3.3571553 -3.3713949 -3.488055 ]]

torch.Size([1, 80, 325])

I got wav result of WaveRNN for this mel-spectrogram and run HiFi-GAN with this wav and result was great. Some print are as follow:
x = torch.FloatTensor(wav).to(device)
x = get_mel(x.unsqueeze(0))
print(x)
print(x.shape)
with torch.no_grad():
    y_g_hat = generator(x)
    print(y_g_hat.shape)
    audio = y_g_hat.squeeze()
    audio = audio.cpu().numpy()

tensor([[[-11.5129,  -8.3294,  -6.7415,  ..., -11.5129, -11.5129, -11.5129],
[-11.5129,  -9.4963,  -6.9599,  ..., -11.5129, -11.5129, -11.5129],
[-11.5129,  -9.9807,  -7.2935,  ..., -11.5129, -11.5129, -11.5129],
...,
[-11.5129,  -9.8441,  -8.7276,  ..., -11.5129, -11.5129, -11.5129],
[-11.5129, -10.4379,  -9.1857,  ..., -11.5129, -11.5129, -11.5129],
[-11.5129, -10.4412,  -9.2296,  ..., -11.5129, -11.5129, -11.5129]]],
device='cuda:0')
torch.Size([1, 80, 327])

So HiFi-GAN work well but I think when using mel-spectrogram directly we should change some thing (like hop_size?) but what and how?

I guess that your melspectrogram generated by Tacotron is normalized, if it is true, you should de-normalize by mean and std.


Summer bank holiday test

Fix the SummerBankHolidayTest for England, Wales and Northern Ireland which occasionally failed, because they failed to check for the renaming from August Bank Holiday to Summer Bank Holiday in 1965.
Also, update the tests for these countries to the coding standard introduced in 27c6e8173.

Thanks! Yes, also noticed this myself but hadn't yet time to fix it.


Autocomplete: Group headers are not selectable.

I am trying to make the Material-UI Autocomplete group header selectable. I have used groupBy and renderGroup props to group the list of options and display them.

@akumath14 This is not possible. We are considering it for https://github.com/mui-org/material-ui-x/issues/514


Support declarative pipeline syntax

Support for testing declarative pipeline syntax.
Provides a DeclarativePipelineTest base class that

Does syntactic checking of the declarative pipeline model
Mocks the ModelInterpreter provided by the pipeline-model-definition-plugin and sets props/params/credentials etc. and calls steps on stages, with when predicates and post actions.

Yet there are several caveats with this approach:

It does not verify whether there is any if,else,loop instructions on regular steps blocks,
Mock model interpreters should be easily extensible by users, which is not possible for now. For now the only extension point is the pipeline keyword, which involves rewriting every model interpreter.
DeclarativePipelineTest does not use CPS transformation so it does not verify the pipeline against serialization issues.

@ozangunalp - This is pretty good stuff. When will this Pull-request be merged to master?

@crasp @jdoshi1 thanks for testing this pull request.
I prepared this PR a while ago and as I wrote in the description back then, I would like to find a solution that is extensible.
I honestly fear that the declarative pipeline syntax will evolve and with this solution we won't be able to follow it.
I'll try to look a bit more and eventually release it as experimental for everyone's use.
Thanks again for checking out the PR.

Any chance of an update on this issue? JenkinsPipelineUnit is a great tool, and as the Declarative method becomes more widely used it's going to be critical that Pipelines be tested properly.

When this will be released?

@kmadel @cavdhut as mentioned above it does not work very well together with declarative syntax. There have been evolving some other projects that cover this at this years Jenkins World, like https://github.com/homeaway/jenkins-spock. Maybe you can check this out as well.

@crasp there comes a point where you have to start thinking about marking a repository which sits underneath the Jenkins community umbrella as either deprecated, or looking for new maintainers. It would help give potential users a direction of travel, if nothing else.
As is evidenced by this and other PRs / Issues, there is clearly more than enough interest in a tool like JenkinsPipelineUnit to warrant a bit more love than it currently gets, and I for one would rather use a testing tool attached to an 'official' organisation in GitHub rather than some random repository overseen by an individual. In theory, being attached to an organisation implies ongoing maintainence and support (unless stated otherwise) - whereas you just can't get that level of comfort from a random individuals' repo, no matter how good the content initially.

Hi @benemon,
I totally agree on your point about individuals maintaining (or not) repos sitting under the organization umbrella.
In the past year I did not had time to give the love that this community deserves to JenkinsPipelineUnit project.
In my defense, in the past months we had been talking with the Jenkins team to onboard at least one other maintainer to the project to get things going and keep the project up to date. I do not know why things did not advance, but i will make sure we have updates ASAP.
As for this PR, it was a proof of concept investigating the viability of the declarative pipeline support for JPU. I come to the decision that keeping up to date the declarative DSL syntax – with possible extensions etc. – would not be feasible and i chose to not advance in its development.
I understand very well the need to test a Jenkins pipeline and secure it's execution against regressions, but for the classic imperative DSL pipelines and libraries.
Unless I missed something during the past months declarative pipelines have a standard lifecycle for stage composition and error handling, and it does not have conditional logic or complex configuration. I think it is a great way to write jenkins pipelines and simplify the common tasks with CI/CD pipelines.
Even though I am open for discussion about the subject, I do not see the need to test declarative pipelines in JPU and when I discussed (a year ago) with the Jenkins team we came up with the same conclusion.
That said the Spock specifications provided by the cited project seems like a decent way if someone insists on testing declarative pipelines.
I am again sorry for the frustration that I caused on the maintenance of this project, and promise to get things going in the near future.
Ozan

@ozangunalp
Thanks for the prompt response, it is very much appreciated. Please understand that my comments are in no way a reflection of the time and energy you have clearly spent with this project.
There's a lot of potential here that would be a shame to go to waste, given the clear interest from the community in JPU. With that in mind, its really good to hear that you've been having talks about extending the maintainence team around the repository. I'm not even talking solely about Declarative Pipelines.
I'll raise an issue for it, but it would be great to get a roadmap or at least a tentative understanding of timelines and objectives around this project and how you see it developing in the future.

@benemon thanks for the understanding.
I will get back to you with more info.


Templates Required

Templates for New PR and Issues are required to allow easier and better descriptions of the same.

I have already started working on this issue so can you kindly assign this one to me.


After power off ESXi host, disk cannot be mounted to new node.

Shanghai team reported the issue when testing with mongoDB.
Each node has multiple pods and each pod has their own persistent volume.
After power off one of the ESXi host, the node is restarted on another host.
However the disk cannot be mounted to other node.
Error from vCenter:
File system specific implementation of LookupAndOpen[file] failed
Failed to add disk 'scsi1:3'.
Cannot open the disk '/vmfs/volumes/vsan:5231ae302a9fb63a-fe0fadf567dd24cb/562ba158-d8a2-046f-6ba7-0050569ce285/k8s-test-cluster-1-dynamic-pvc-19e1e6d7-07cd-11e7-a07b-005056b281c6.vmdk' or one of the snapshot disks it depends on.

From kubernetes:
Failed to attach volume "pvc-1a79af4e-07cd-11e7-a07b-005056b281c6" on node "node6" with: Failed to add disk 'scsi1:0'.
Error syncing pod, skipping: timeout expired waiting for volumes to attach/mount for pod "default"/"mongodb-shard-node01-472414307-qvl77". list of unattached/unmounted volumes=[vsphere-storage-mongoc01 vsphere-storage-db-rsp01 vsphere-storage-db-rss04 vsphere-storage-db-rsa0

Divyen tried to reproduce this error with a single wordpress pod and everything looks good.
The same error shows up for a while but disappears after the pod is rescheduled.
The next step we may want to try out the same yaml files to see if the mounting will be successful when there are multiple disks need to be unmounted/mounted.

Just checked Shanghai team's VSAN Cluster, I see default VSAN Policy has Number of failures to tolerate is set to 1.
If they are failing over one host. we should not encounter this issue. but if they are powering off couple of hosts from hardware console, then node VM's primary disk can become inaccessible and so master can never unmount and detach volume from that node.

@divyenpatel
Just verified that only one host is powered off at one time... So this might not be the reason of the error.

@luomiao
even if we power off one host after another with some delays, some nodes may become inaccessible after we power off second host, and can lead to this situation. as only two copies of the nodes disk is present.
For example.
VM node1 is deployed on host1.
VM node2 is deployed on host2.
VM node3 is deployed on host3.
VM master is deployed in host3.
node1's primary disk's copy is available on host1 and host2.
node2's primary disk's copy is available on host1 and host2.
node3's primary disk's copy is available on host3 and host2.
master's primary disk's copy is available on host4 and host3.
VM node1 has the pod and volume disk is attached to node1.
Power off host1. assume node1 VM will be restarted on host3.
and at the same time pod is scheduled to be recreated on node2 which is deployed on host2.
volume disk will be detached from node1 and attached to node2.
now power off host2, which has node2 and the pod.
assume node2 be restarted on host3 and pod is scheduled to be recreated on node3.
node2's primary disk's copies were available only on host1 and host2. and so node2's disk will become inaccessible, but in VC node2 is still powered on VM - with volume disk attached.
even if pod is scheduled to be created on node3, cloud provider will never be able to attach hot volume disk to node3, as volume disk is already attached to powered on vm node2
For two host failover, we should change default VSAN profile and set “Number of failures to tolerate” to “2”. Also policy needs to be re-applied back to node VMs, so that appropriate copies of objects are created. if volumes were created before increasing FTT, policy needs to be re-applied to those volume disks.
Can we ask Shanghai team to increase FTT to two and then perform two host failover?

We were able to reproduce this issue on testbed prepared by Shanghai team.
At the beginning one pod is running on node 4 with 4 volumes attached/mounted.
After we powered off the host ESXi where node 4 is running on, the Pod is reschedule to node 5.
However, only 2 disks are successfully attached/mounted to node 5.
The other 2 disks are still attached to node 4, with mount path empty:
root@node4 [ /var/lib/docker/containers ]# lsblk
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sdc      8:32   0   30G  0 disk
sdd      8:48   0   10G  0 disk
sde      8:64   0 15.6G  0 disk
|-sde1   8:65   0    2M  0 part
`-sde2   8:66   0    8G  0 part /
sr0     11:0    1 1024M  0 rom

The logs have a bunch of messages:
{"log":"W0324 03:48:33.700489     458 mount.go:136] could not determine device for path: \"/var/lib/kubelet/pods/403c8515-07cd-11e7-a07b-005056b281c6/volumes/kubernetes.io~vsphere-volume/pvc-1bd0299d-07cd-11e7-a07b-005056b281c6\"\n","stream":"stderr","time":"2017-03-24T03:48:33.700730434Z"}
{"log":"E0324 03:48:33.701679     458 reconciler.go:433] Could not construct volume information: directory /var/lib/kubelet/pods/403c8515-07cd-11e7-a07b-005056b281c6/volumes/kubernetes.io~vsphere-volume/pvc-1bd0299d-07cd-11e7-a07b-005056b281c6 is not mounted\n","stream":"stderr","time":"2017-03-24T03:48:33.701751806Z"}

and
{"log":"E0324 03:48:34.604697     458 kubelet_volumes.go:110] Orphaned pod \"403c8515-07cd-11e7-a07b-005056b281c6\" found, but error \u003cnil\u003e occured during reading volume dir from disk\n","stream":"stderr","time":"2017-03-24T03:48:34.604854878Z"}
{"log":"E0324 03:48:34.604916     458 kubelet_volumes.go:110] Orphaned pod \"5454a242-0ed2-11e7-a07b-005056b281c6\" found, but error \u003cnil\u003e occured during reading volume dir from disk\n","stream":"stderr","time":"2017-03-24T03:48:34.60548334Z"}
{"log":"E0324 03:48:34.605127     458 kubelet_volumes.go:110] Orphaned pod \"647dbda9-0d8d-11e7-a07b-005056b281c6\" found, but error \u003cnil\u003e occured during reading volume dir from disk\n","stream":"stderr","time":"2017-03-24T03:48:34.605557595Z"}
{"log":"E0324 03:48:34.605270     458 kubelet_volumes.go:110] Orphaned pod \"ec836ab2-0f91-11e7-a07b-005056b281c6\" found, but error \u003cnil\u003e occured during reading volume dir from disk\n","stream":"stderr","time":"2017-03-24T03:48:34.605569314Z"}

@luomiao, tried to reproduce issue with 10 Volume pod, unable to reproduce the issue.
All 10 Volumes got attached to the new node where POD is re-scheduled.
Kubernetes Version I have is : v1.5.7-beta.0.2+50e04da70f6d4a
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.3", GitCommit:"029c3a408176b55c30846f0faedf56aae5992e9b", GitTreeState:"clean", BuildDate:"2017-02-15T06:40:50Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"5+", GitVersion:"v1.5.7-beta.0.2+50e04da70f6d4a", GitCommit:"50e04da70f6d4a61648b41fcb94f3a2a28a28dec", GitTreeState:"clean", BuildDate:"2017-03-29T00:38:51Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}

Created pod with 10 Volumes. pod placed on node1. All volumes attached to node1.
$ kubectl create -f 10-disk-mysqlPod.yaml
service "wordpress-mysql" created
persistentvolumeclaim "mysql-pv-claim1" created
persistentvolumeclaim "mysql-pv-claim2" created
persistentvolumeclaim "mysql-pv-claim3" created
persistentvolumeclaim "mysql-pv-claim4" created
persistentvolumeclaim "mysql-pv-claim5" created
persistentvolumeclaim "mysql-pv-claim6" created
persistentvolumeclaim "mysql-pv-claim7" created
persistentvolumeclaim "mysql-pv-claim8" created
persistentvolumeclaim "mysql-pv-claim9" created
persistentvolumeclaim "mysql-pv-claim10" created
deployment "wordpress-mysql" created

$ kubectl get pvc
NAME               STATUS    VOLUME                                     CAPACITY   ACCESSMODES   AGE
mysql-pv-claim1    Bound     pvc-22c1f749-14ab-11e7-ae77-005056bdb770   2Gi        RWO           5m
mysql-pv-claim10   Bound     pvc-22f1155b-14ab-11e7-ae77-005056bdb770   2Gi        RWO           5m
mysql-pv-claim2    Bound     pvc-22c7b37a-14ab-11e7-ae77-005056bdb770   2Gi        RWO           5m
mysql-pv-claim3    Bound     pvc-22cc8560-14ab-11e7-ae77-005056bdb770   2Gi        RWO           5m
mysql-pv-claim4    Bound     pvc-22d1b151-14ab-11e7-ae77-005056bdb770   2Gi        RWO           5m
mysql-pv-claim5    Bound     pvc-22d6b2eb-14ab-11e7-ae77-005056bdb770   2Gi        RWO           5m
mysql-pv-claim6    Bound     pvc-22dbf7f2-14ab-11e7-ae77-005056bdb770   2Gi        RWO           5m
mysql-pv-claim7    Bound     pvc-22e12ac7-14ab-11e7-ae77-005056bdb770   2Gi        RWO           5m
mysql-pv-claim8    Bound     pvc-22e6dbbc-14ab-11e7-ae77-005056bdb770   2Gi        RWO           5m
mysql-pv-claim9    Bound     pvc-22ec090e-14ab-11e7-ae77-005056bdb770   2Gi        RWO           5m
$

$ kubectl describe pod wordpress-mysql-4011518514-zmfqj
Name:		wordpress-mysql-4011518514-zmfqj
Namespace:	default
Node:		node1/<IP_ADDRESS>
Start Time:	Wed, 29 Mar 2017 11:11:46 -0700
Labels:		app=wordpress
		pod-template-hash=4011518514
		tier=mysql
Status:		Running
IP:		<IP_ADDRESS>
Controllers:	ReplicaSet/wordpress-mysql-4011518514
Containers:
  mysql:
    Container ID:	docker://e6db586f6247ba7fa76a84b0ba460d78df9e009a4072d6051f7b5c71d3b3695f
    Image:		mysql:5.6
    Image ID:		docker://sha256:68399df75c596686ace0c41106d1506965b15d54dd48f8599ad94ef589e0fc3e
    Port:		3306/TCP
    State:		Running
      Started:		Wed, 29 Mar 2017 11:12:33 -0700
    Ready:		True
    Restart Count:	0
    Volume Mounts:
      /var/lib/mysql from mysql-persistent-storage1 (rw)
      /var/lib/mysql10 from mysql-persistent-storage10 (rw)
      /var/lib/mysql2 from mysql-persistent-storage2 (rw)
      /var/lib/mysql3 from mysql-persistent-storage3 (rw)
      /var/lib/mysql4 from mysql-persistent-storage4 (rw)
      /var/lib/mysql5 from mysql-persistent-storage5 (rw)
      /var/lib/mysql6 from mysql-persistent-storage6 (rw)
      /var/lib/mysql7 from mysql-persistent-storage7 (rw)
      /var/lib/mysql8 from mysql-persistent-storage8 (rw)
      /var/lib/mysql9 from mysql-persistent-storage9 (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-6fd49 (ro)
    Environment Variables:
      MYSQL_ROOT_PASSWORD:	mysqlpassword
Conditions:
  Type		Status
  Initialized 	True
  Ready 	True
  PodScheduled 	True
Volumes:
  mysql-persistent-storage1:
    Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:	mysql-pv-claim1
    ReadOnly:	false
  mysql-persistent-storage2:
    Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:	mysql-pv-claim2
    ReadOnly:	false
  mysql-persistent-storage3:
    Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:	mysql-pv-claim3
    ReadOnly:	false
  mysql-persistent-storage4:
    Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:	mysql-pv-claim4
    ReadOnly:	false
  mysql-persistent-storage5:
    Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:	mysql-pv-claim5
    ReadOnly:	false
  mysql-persistent-storage6:
    Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:	mysql-pv-claim6
    ReadOnly:	false
  mysql-persistent-storage7:
    Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:	mysql-pv-claim7
    ReadOnly:	false
  mysql-persistent-storage8:
    Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:	mysql-pv-claim8
    ReadOnly:	false
  mysql-persistent-storage9:
    Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:	mysql-pv-claim9
    ReadOnly:	false
  mysql-persistent-storage10:
    Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:	mysql-pv-claim10
    ReadOnly:	false
  default-token-6fd49:
    Type:	Secret (a volume populated by a Secret)
    SecretName:	default-token-6fd49
QoS Class:	BestEffort
Tolerations:	<none>
Events:
  FirstSeen	LastSeen	Count	From			SubObjectPath		Type		Reason			Message
  ---------	--------	-----	----			-------------		--------	------			-------
  6m		6m		5	{default-scheduler }				Warning		FailedScheduling	[SchedulerPredicates failed due to PersistentVolumeClaim is not bound: "mysql-pv-claim1", which is unexpected., SchedulerPredicates failed due to PersistentVolumeClaim is not bound: "mysql-pv-claim1", which is unexpected., SchedulerPredicates failed due to PersistentVolumeClaim is not bound: "mysql-pv-claim1", which is unexpected., SchedulerPredicates failed due to PersistentVolumeClaim is not bound: "mysql-pv-claim1", which is unexpected.]
  6m		6m		1	{default-scheduler }				Normal		Scheduled		Successfully assigned wordpress-mysql-4011518514-zmfqj to node1
  5m		5m		1	{kubelet node1}		spec.containers{mysql}	Normal		Pulling			pulling image "mysql:5.6"
  5m		5m		1	{kubelet node1}		spec.containers{mysql}	Normal		Pulled			Successfully pulled image "mysql:5.6"
  5m		5m		1	{kubelet node1}		spec.containers{mysql}	Normal		Created			Created container with docker id e6db586f6247; Security:[seccomp=unconfined]
  5m		5m		1	{kubelet node1}		spec.containers{mysql}	Normal		Started			Started container with docker id e6db586f6247

Powered off Node1's Host, and POD is scheduled to start on node3.
$ kubectl get pod
NAME                               READY     STATUS              RESTARTS   AGE
wordpress-mysql-4011518514-7n8dc   0/1       ContainerCreating   0          20s

$ kubectl describe pod wordpress-mysql-4011518514-7n8dc
Name:		wordpress-mysql-4011518514-7n8dc
Namespace:	default
Node:		node3/<IP_ADDRESS>
Start Time:	Wed, 29 Mar 2017 11:22:42 -0700
Labels:		app=wordpress
		pod-template-hash=4011518514
		tier=mysql
Status:		Running
IP:		<IP_ADDRESS>
Controllers:	ReplicaSet/wordpress-mysql-4011518514
Containers:
  mysql:
    Container ID:	docker://47cf7554025f533ecefe3b88e706c714056b2dceec021e1d1262f610f5ed1a02
    Image:		mysql:5.6
    Image ID:		docker://sha256:68399df75c596686ace0c41106d1506965b15d54dd48f8599ad94ef589e0fc3e
    Port:		3306/TCP
    State:		Running
      Started:		Wed, 29 Mar 2017 11:27:56 -0700
    Ready:		True
    Restart Count:	0
    Volume Mounts:
      /var/lib/mysql from mysql-persistent-storage1 (rw)
      /var/lib/mysql10 from mysql-persistent-storage10 (rw)
      /var/lib/mysql2 from mysql-persistent-storage2 (rw)
      /var/lib/mysql3 from mysql-persistent-storage3 (rw)
      /var/lib/mysql4 from mysql-persistent-storage4 (rw)
      /var/lib/mysql5 from mysql-persistent-storage5 (rw)
      /var/lib/mysql6 from mysql-persistent-storage6 (rw)
      /var/lib/mysql7 from mysql-persistent-storage7 (rw)
      /var/lib/mysql8 from mysql-persistent-storage8 (rw)
      /var/lib/mysql9 from mysql-persistent-storage9 (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-6fd49 (ro)
    Environment Variables:
      MYSQL_ROOT_PASSWORD:	mysqlpassword
Conditions:
  Type		Status
  Initialized 	True
  Ready 	True
  PodScheduled 	True
Volumes:
  mysql-persistent-storage1:
    Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:	mysql-pv-claim1
    ReadOnly:	false
  mysql-persistent-storage2:
    Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:	mysql-pv-claim2
    ReadOnly:	false
  mysql-persistent-storage3:
    Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:	mysql-pv-claim3
    ReadOnly:	false
  mysql-persistent-storage4:
    Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:	mysql-pv-claim4
    ReadOnly:	false
  mysql-persistent-storage5:
    Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:	mysql-pv-claim5
    ReadOnly:	false
  mysql-persistent-storage6:
    Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:	mysql-pv-claim6
    ReadOnly:	false
  mysql-persistent-storage7:
    Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:	mysql-pv-claim7
    ReadOnly:	false
  mysql-persistent-storage8:
    Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:	mysql-pv-claim8
    ReadOnly:	false
  mysql-persistent-storage9:
    Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:	mysql-pv-claim9
    ReadOnly:	false
  mysql-persistent-storage10:
    Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:	mysql-pv-claim10
    ReadOnly:	false
  default-token-6fd49:
    Type:	Secret (a volume populated by a Secret)
    SecretName:	default-token-6fd49
QoS Class:	BestEffort
Tolerations:	<none>
Events:
  FirstSeen	LastSeen	Count	From			SubObjectPath		Type		Reason		Message
  ---------	--------	-----	----			-------------		--------	------		-------
  7m		7m		1	{default-scheduler }				Normal		Scheduled	Successfully assigned wordpress-mysql-4011518514-7n8dc to node3
  6m		6m		1	{controller-manager }				Warning		FailedMount	Failed to attach volume "pvc-22cc8560-14ab-11e7-ae77-005056bdb770" on node "node3" with: Failed to add disk 'scsi1:0'.
  6m		6m		1	{controller-manager }				Warning		FailedMount	Failed to attach volume "pvc-22f1155b-14ab-11e7-ae77-005056bdb770" on node "node3" with: Failed to add disk 'scsi1:0'.
  5m		5m		1	{controller-manager }				Warning		FailedMount	Failed to attach volume "pvc-22c7b37a-14ab-11e7-ae77-005056bdb770" on node "node3" with: Failed to add disk 'scsi1:0'.
  5m		5m		1	{controller-manager }				Warning		FailedMount	Failed to attach volume "pvc-22e12ac7-14ab-11e7-ae77-005056bdb770" on node "node3" with: Failed to add disk 'scsi1:0'.
  4m		4m		1	{kubelet node3}					Warning		FailedMount	Unable to mount volumes for pod "wordpress-mysql-4011518514-7n8dc_default(b2c5b116-14ac-11e7-ae77-005056bdb770)": timeout expired waiting for volumes to attach/mount for pod "default"/"wordpress-mysql-4011518514-7n8dc". list of unattached/unmounted volumes=[mysql-persistent-storage1 mysql-persistent-storage2 mysql-persistent-storage3 mysql-persistent-storage4 mysql-persistent-storage5 mysql-persistent-storage6 mysql-persistent-storage7 mysql-persistent-storage8 mysql-persistent-storage9 mysql-persistent-storage10]
  4m		4m		1	{kubelet node3}					Warning		FailedSync	Error syncing pod, skipping: timeout expired waiting for volumes to attach/mount for pod "default"/"wordpress-mysql-4011518514-7n8dc". list of unattached/unmounted volumes=[mysql-persistent-storage1 mysql-persistent-storage2 mysql-persistent-storage3 mysql-persistent-storage4 mysql-persistent-storage5 mysql-persistent-storage6 mysql-persistent-storage7 mysql-persistent-storage8 mysql-persistent-storage9 mysql-persistent-storage10]
  4m		4m		1	{controller-manager }				Warning		FailedMount	Failed to attach volume "pvc-22d1b151-14ab-11e7-ae77-005056bdb770" on node "node3" with: Failed to add disk 'scsi1:0'.
  4m		4m		1	{controller-manager }				Warning		FailedMount	Failed to attach volume "pvc-22d6b2eb-14ab-11e7-ae77-005056bdb770" on node "node3" with: Failed to add disk 'scsi1:0'.
  3m		3m		1	{controller-manager }				Warning		FailedMount	Failed to attach volume "pvc-22dbf7f2-14ab-11e7-ae77-005056bdb770" on node "node3" with: Failed to add disk 'scsi1:0'.
  3m		3m		1	{controller-manager }				Warning		FailedMount	Failed to attach volume "pvc-22ec090e-14ab-11e7-ae77-005056bdb770" on node "node3" with: Failed to add disk 'scsi1:0'.
  3m		3m		1	{controller-manager }				Warning		FailedMount	Failed to attach volume "pvc-22e6dbbc-14ab-11e7-ae77-005056bdb770" on node "node3" with: Failed to add disk 'scsi1:0'.
  2m		2m		1	{controller-manager }				Warning		FailedMount	(events with common reason combined)
  2m		2m		1	{kubelet node3}					Warning		FailedMount	Unable to mount volumes for pod "wordpress-mysql-4011518514-7n8dc_default(b2c5b116-14ac-11e7-ae77-005056bdb770)": timeout expired waiting for volumes to attach/mount for pod "default"/"wordpress-mysql-4011518514-7n8dc". list of unattached/unmounted volumes=[mysql-persistent-storage8 mysql-persistent-storage10]
  2m		2m		1	{kubelet node3}					Warning		FailedSync	Error syncing pod, skipping: timeout expired waiting for volumes to attach/mount for pod "default"/"wordpress-mysql-4011518514-7n8dc". list of unattached/unmounted volumes=[mysql-persistent-storage8 mysql-persistent-storage10]
  1m		1m		1	{kubelet node3}		spec.containers{mysql}	Normal		Pulling		pulling image "mysql:5.6"
  1m		1m		1	{kubelet node3}		spec.containers{mysql}	Normal		Pulled		Successfully pulled image "mysql:5.6"
  1m		1m		1	{kubelet node3}		spec.containers{mysql}	Normal		Created		Created container with docker id 47cf7554025f; Security:[seccomp=unconfined]
  1m		1m		1	{kubelet node3}		spec.containers{mysql}	Normal		Started		Started container with docker id 47cf7554025f

$ kubectl exec -it wordpress-mysql-4011518514-7n8dc bin/sh
# df -h
Filesystem      Size  Used Avail Use% Mounted on
overlay         7.8G  2.3G  5.1G  31% /
tmpfs           3.9G     0  3.9G   0% /dev
tmpfs           3.9G     0  3.9G   0% /sys/fs/cgroup
/dev/root       7.8G  2.3G  5.1G  31% /etc/hosts
/dev/sdg        2.0G  3.0M  1.8G   1% /var/lib/mysql5
/dev/sde        2.0G  3.0M  1.8G   1% /var/lib/mysql7
/dev/sdk        2.0G  119M  1.7G   7% /var/lib/mysql
/dev/sdd        2.0G  3.0M  1.8G   1% /var/lib/mysql2
/dev/sdj        2.0G  3.0M  1.8G   1% /var/lib/mysql8
/dev/sdi        2.0G  3.0M  1.8G   1% /var/lib/mysql9
/dev/sdc        2.0G  3.0M  1.8G   1% /var/lib/mysql10
/dev/sdb        2.0G  3.0M  1.8G   1% /var/lib/mysql3
/dev/sdh        2.0G  3.0M  1.8G   1% /var/lib/mysql6
/dev/sdf        2.0G  3.0M  1.8G   1% /var/lib/mysql4
tmpfs           3.9G   12K  3.9G   1% /run/secrets/kubernetes.io/serviceaccount
shm              64M     0   64M   0% /dev/shm
#

Verified All Volumes are now attached to node3.

@luomiao As we discussed, when I tried with higher capacity volume I am able to reproduce this issue. One of the 30 GB volume was left in the failed over node.
I am continuously seeing message on the failed over node.
kubelet_volumes.go:110] Orphaned pod "60185498-14b4-11e7-ae77-005056bdb770" found, but error <nil> occured during reading volume dir from disk
https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/kubelet_volumes.go#L110
# lsblk
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sdc      8:32   0   30G  0 disk
sdd      8:48   0 15.6G  0 disk
|-sdd1   8:49   0    2M  0 part
`-sdd2   8:50   0    8G  0 part /
sr0     11:0    1 1024M  0 rom

Great that we finally caught this issue!
So a larger volume may need more time to get unmounted/detached.
We need to figure out what's the order when the pods/nodes getting rescheduled.
What's the order of unmounting volumes, killing old pod, scheduling new pod.

Issue is producible on release 1.6 branch also.
Observed this failure on build v1.6.3-beta.0.43+ab61393ee6b119
Created an issue on Kubernetes to get help from Kubernetes SIG storage.
https://github.com/kubernetes/kubernetes/issues/45464

Merged and cherry picked to 1.6


IE raises "Access denied" error in some cases

I'm getting occasional localized errors in my JS logs translating as "Access denied" from IE 11 with stacks like this:
Error: Toegang geweigerd. // Error: Access denied

  at findProperties (app/~/viewport-units-buggyfill/viewport-units-buggyfill.js?:189)
  at func (app/~/viewport-units-buggyfill/viewport-units-buggyfill.js?:164)
  at func (app/~/viewport-units-buggyfill/viewport-units-buggyfill.js?:90)

I don't think the line numbers are very accurate, but from my understand this is caused by accessing document.styleSheets when some stylesheet is loaded from another host.
Shall we try-catch it?

we already have something in place to deal with foreign resources: importCrossOriginLinks. We should try making that work before simply silencing something. Maybe the try-catch then becomes unnecessary?

The problem is document.styleSheets itself throws in some cases (maybe has to do with IE permissions). How do we work around that?

it probably throws when accessing something you shouldn't. the only way I see this would work is by dopping the forEach and going with a for () { try{ … } catch(e){} } loop. do you want to try it out and send a PR?

Submitted as #39.
I have not tested this yet (written in browser).
I also don't like complete error swallowing, shall we at least do console.warn?

I have made this PR which fixed this issue for me. I received this error in IE9 after calling sheet.cssRules on a remote stylesheet from inside an iframe. Since the CSSRuleList should always be an array-like object, it is better to use typeof.

https://github.com/rodneyrehm/viewport-units-buggyfill/pull/64

fixed by merging #64


Send email using nodemailer on successful signup

Also show me the email template before sending

hey can u please assign me this issue iwould love to work on this issue under #jwoc 2k23 i have prior  experience by the way on node js

can u please elaborate  what kind of functionality do u need specifically

Send an email when new user signs up!

??

I am working on it will try to submit by tomorrow


Don't use S390 object code for generating build args

For generating build args from a cilium directory, we get the list of bpf object files in the directory and then use the first one in the list to generate the build program and map labels.  However, Aya Object::parse doesn't currently work for S390 files, so if an S390 file happens to be the first one in the list, it doesn't work.
This is a temporary fix that doesn't use S390 files, and if no other type of file exists, it returns an error.
Fixes: #1200

I'm merging this without a review to hopefully get the upstream bpfman-image-build action working again.


Details for Calculating Months

Details for Calculating Months, Weeks, Days, Hours, Minutes, and Seconds shown.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.

Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding.


PostGIS: Find & test Spatial Functions (for our agreegation methods)

From our tech report:

Geometric center;
Bounding rectangle;
Clustering of points (DBSCAN) [27];
Hexagons;
Aggregation per administrative units.

PostGIS Spatial Functions defined in chapter 8 of their documentation

Geometric center;

PostGIS function name and link to definition: ST_Centroid
Examples:

Bounding rectangle;

PostGIS function name and link to definition: ST_Envelope
Examples:
https://postgis.net/docs/manual-1.4/ST_Envelope.html
https://gis.stackexchange.com/questions/83387/performing-bounding-box-query-in-postgis

Clustering of points (DBSCAN) [27];

PostGIS function name and link to definition: ST_ClusterDBSCAN, there is also: ST_ClusterKMeans and ST_ClusterWithin
Examples:
For KMeans: https://access.crunchydata.com/documentation/postgis/3.1.1/ST_ClusterKMeans.html

Hexagons;

PostGIS function name and link to definition: ST_Hexagon
Examples:

Aggregation per administrative units.

PostGIS function name and link to definition:
Examples:

@mariidpm Mari, nice work! I've already mentioned it once with Inga but didn't discuss it with you. Imho the last method is too complex to implement. I used it in the tech report because back then I thought it might look very interesting for our previous use case. But for now, I think we should change it. What do you think?

@dancingsushii sounds good, I couldn't find anything in postgis for it, so happy to switch for another method which we can use in postgis


fix(build): Fixed build issue

PR related to this trello task --> https://trello.com/c/FyuKZ7Kg

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Hackers nft updates

Removes vault, description, and tier from the NFT and use the IPFS hash for the token ID.
Adds option to permanently stop minting of an NFT or multiple NFTs.
Adds HATHackersNFT to the deployement scripts and deploy to Goerli.
Transfer ownership to Hats governance on deployment.

Hi, so I'm not sure about the comments.

I could add a createAndMint function or something, but I don't think it's in any way unnatural to have the create separated from the minting. The create only happens one, while minting can be called many times. So I think it makes sense to separate them.
To use that "whitelist" to stop minting would mean to delete/ alter the uri of the NFT which is not what we want. And the blacklisting to not be able to ever mint (even though it's only owner) was a requirement Shay asked for.


random crash in rocky while zooming and panning

While running rocky, I'm noticing a random crash while panning around on the Earth (see attached image below on details).
I'm seeing this running the rdemo.exe and rengine.exe apps. It appears to happen at different times during execution but it happens regularly at the same location in the code (vsg).
My environment...
OS:                  Windows 10
IDE:                  Visual Studio 2022
Configuration: RelWithDebInfo
Platform:          x64

Just a follow-up to my previous post,..
I'm noticing that the process memory (in the diagnostic tools) steadily increases as I move around until it reaches 10.1+ Gb. It is at this point that the crash occurs.
It's like memory isn't being released somewhere...

Yes. I have noticed the same thing, and it seems to be a function of the pre-allocation of pools in ResourceHints.
In rengine.cpp we are using those resource hints and there's a big memory leak. In rdemo (the code is actually in Application.cpp line ~564)  however we're limiting the numDescriptorSets to 1, and there problem doesn't exist.
I am not smart enough about the guts of VSG (yet?) to know what's up, so I appreciate the experimentation and sharing of knowledge :)

Thanks for the feedback Glenn.
For the record, the crash still occurs with rdemo.exe  like the other applications.
Looking at my version, it has resourceHints->numDescriptorSets = 64; for line 564.
I will do some further research and investigation on the matter on my end to try and help...

Grab the latest (with numDescriptorSets = 1) and let me know if you still se the problem.

Okay.
I did a pull of the rocky repo.
Do I need to rerun the bootstrap-vcpkg.bat file to update?

Probably not, but I would definitely re-run cmake on your build folder.

I was finally able to run the rsimple.exe application with the aforementioned changes to the numDescriptorSets and the crash has not happened yet.
However, now I'm seeing something different. It appears that paging stalls periodically so that the higher LODs don't page in.
I've attached a picture showing the problem.

Can you give me the viewpoint?
In rdemo, open Camera->Viewpoints and take a screenshot.

Here's a capture around the same area with viewpoint displayed. It might be the source imagery for the tile but I don't see this in osgEarth using ReadyMap...

Glenn,
Not sure if this is related but I'm noticing that rengine.exe won't render the ReadyMap tiles with the latest git pull of rocky. I just see an orange globe.
Do you see this as well?
I debugged into the rengine.cpp and it appears to be loading the imagery and elevation layers okay.
I'm able to run rdemo.exe and rsimple.exe and see the ReadyMap stuff fine so it's not a network problem on my end.
Shayne

On 10/30/2023 2:20 PM MDT Glenn @.***> wrote:
Can you give me the viewpoint?
In rdemo, open Camera->Viewpoints and take a screenshot.
—
Reply to this email directly, view it on GitHub https://github.com/pelicanmapping/rocky/issues/19#issuecomment-1785971682, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATC464PNQKISEPCLAYWUCHLYCADXFAVCNFSM6AAAAAA6RWAB3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBVHE3TCNRYGI.
You are receiving this because you authored the thread.Message ID: @.***>

It's just missing data on the server. (This is osgEarth, Rocky, and ReadyMap console from left to right)

As for rengine, I pushed a quick fix for that -- I would stick to rdemo for the most part since that's the app that gets the most attention. I do not spend as much time keeping the other 2 up to date :)


Properly cast byte[] for BinaryData ctor in TableEntity.GetBinaryData

fixes #29029

API change check
API changes are not detected in this pull request.

Looks like this is also being addressed here - #29030

oops - missed that.


Extend Dataset for Testing Framework

Description
Expand the current dataset for the testing framework by adding six new scenarios. These new scenarios will include three scenarios related to Kyma problems and three scenarios related to Kubernetes problems. Each scenario should have a corresponding validation file for the validator.
Subtasks

Kyma-Related Scenarios:

Develop three new scenarios that focus on issues related to Kyma.
Ensure each scenario covers different aspects of Kyma to provide a broad testing scope.
Write corresponding expectation files for each scenario.
Create corresponding validation files for each scenario to be used by the validator.

Kubernetes-Related Scenarios:

Develop three new scenarios that focus on issues related to Kubernetes.
Ensure each scenario covers different aspects of Kubernetes to provide a broad testing scope.
Write corresponding expectation files for each scenario.
Create corresponding validation files for each scenario to be used by the validator.

Testing:

Deploy new scenarios to gardener cluster
Test the scenarios within the testing framework to confirm they work as expected.

Acceptance Criteria

[ ] Three new scenarios related to Kyma problems are created and integrated into the dataset.
[ ] Three new scenarios related to Kubernetes problems are created and integrated into the dataset.
[ ] Each scenario has a corresponding expectation file.
[ ] Each scenario has a corresponding validation file for use by the validator.
[ ] All new scenarios are deployed and tested within the testing framework to ensure proper functionality.

related: https://github.com/kyma-project/kyma-companion/issues/141

Previous issue: #92

split the PR into two: evaluation cases and validation?


Create Dependabot config

With this config Dependabot will open once a week PRs to update the Android and NPM dependencies.
Please merge after #331 and #332.

What's the purpose of this? Randomly upgrading dependencies is potentially destabilizing. I would rather this be a manual process when we need to update deps.

The main purpose of timely dependency updates is having the latest performance and, most importantly, security updates included. An automated process guarantees that it happens timely, in small, tractable and predictable chunks. The risk of a manual process is having things left out.
For example, Gradle, the Android build system used, will throw depreciation alerts for outdated APIs and functions. This way, updating to the next major version can be prepared in advance.
Unfortunately, Gradle hasn't been updated in over 4 years, lagging now 4 major versions behind. Gradle 5.x knows what will break in Gradle 6.x, but Gradle 2.x has no idea. This makes updating very difficult.
I think a manual process could serve this purpose as well, but is has to be executed timely and consistently. We humans are in general not great at that, so that would be the main argument for automating this process in some way.
Note that Dependabot only opens PRs, you decide when to merge them. And of course in can be configured to run a schedule that fits your workflow.

The main purpose of timely dependency updates is having the latest performance and, most importantly, security updates included. An automated process guarantees that it happens timely, in small, tractable and predictable chunks. The risk of a manual process is having things left out.
For example, Gradle, the Android build system used, will throw depreciation alerts for outdated APIs and functions. This way, updating to the next major version can be prepared in advance.
Unfortunately, Gradle hasn't been updated in over 4 years, lagging now 4 major versions behind. Gradle 5.x knows what will break in Gradle 6.x, but Gradle 2.x has no idea. This makes updating very difficult.
I think a manual process could serve this purpose as well, but is has to be executed timely and consistently. We humans are in general not great at that, so that would be the main argument for automating this process in some way.
Note that Dependabot only opens PRs, you decide when to merge them. And of course in can be configured to run a schedule that fits your workflow.

@EwoutH, we really appreciate all the work you've contributed to the project, and thanks so much for your detailed explanation.
For now we've decided we don't want accept this change to automate dependency updates. While completely understand the argument for ensuring all packages and dependencies are up to date, and the advantages this provides, it also has the inverse impact of possibly destabilizing the project or possibly introducing bugs in newer versions of dependencies. I would much rather we limit the dependencies we take on and keep an eye on when those dependencies make sense to upgrade.
In terms of Gradle, you are absolutely correct that the Gradle wrapper version for the Android library is very out of date. Fortunately, I don't believe this has a concrete impact on consumers as consuming apps will compile the lib using the Gradle version of their root project. (Ex. we are using 6.5 in the example project: https://github.com/teslamotors/react-native-camera-kit/blob/master/example/android/gradle/wrapper/gradle-wrapper.properties)
If you want to create a PR to update Gradle in the Android lib to match the example project, or if there is any other dependency that makes sense to update, we would gladly accept that change!
Thanks again!

@EwoutH, we really appreciate all the work you've contributed to the project, and thanks so much for your detailed explanation.
For now we've decided we don't want accept this change to automate dependency updates. While completely understand the argument for ensuring all packages and dependencies are up to date, and the advantages this provides, it also has the inverse impact of possibly destabilizing the project or possibly introducing bugs in newer versions of dependencies. I would much rather we limit the dependencies we take on and keep an eye on when those dependencies make sense to upgrade.
In terms of Gradle, you are absolutely correct that the Gradle wrapper version for the Android library is very out of date. Fortunately, I don't believe this has a concrete impact on consumers as consuming apps will compile the lib using the Gradle version of their root project. (Ex. we are using 6.5 in the example project: https://github.com/teslamotors/react-native-camera-kit/blob/master/example/android/gradle/wrapper/gradle-wrapper.properties)
If you want to create a PR to update Gradle in the Android lib to match the example project, or if there is any other dependency that makes sense to update, we would gladly accept that change!
Thanks again!


How to override the sidebar item's font size and item's height?

I want to increase the size of sidebar menu text and increase the height of the sidebar menu item. But I don't know How to do that. Can Someone tell me?

@AnZeng00 Use the following CSS to override the font-size and item height.
.bb-sidebar .nav-item {
    line-height: 3rem;
    font-size: 1.5rem;
}

Before:

After:


add passes for vulkan-shader-profiler

Depends on https://github.com/KhronosGroup/SPIRV-Headers/pull/398

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

Also, please note that this PR introduces a dependency of spirv-tools on vulkan-headers

I haven't looked deeply.  Requiring a depdency on vulkan-headers seems unfortunate.

I have removed the dependency on vulkan-headers.
I will keep the passes in another repository, but those changes are still needed for those to work


npm installation failing on FreeBSD because install-message.sh uses /bin/bash instead of /bin/sh

The install-message.sh script is preventing successful installation of npm on FreeBSD, which does not include bash in its default distribution.
This:
#!/bin/bash
Would be more portable as:
#!/bin/sh

Also seeing @ZoomQuiet's issue on FreeBSD 8.2...

@isaacs so sorry,get it, after testing..


Redirect generate wrong access logs

Do you want to request a feature or report a bug?
Reporting a bug
What did you do?
Run traefik with http redirected to https and examine access logs.
What did you expect to see?
A single curl on nginx1 generates 1 line in the access log:
<IP_ADDRESS> - - [13/Dec/2017:19:49:27 +0000] "GET / HTTP/1.1" 200 612 - "curl/7.54.0" 34 "Host-nginx1-test-tld-3" "http://<IP_ADDRESS>:80" 0ms

A single curl on nginx2 generates 1 line in the access log:
<IP_ADDRESS> - - [13/Dec/2017:19:50:41 +0000] "GET / HTTP/1.1" 200 612 - "curl/7.54.0" 42 "Host-nginx2-test-tld-2" "http://<IP_ADDRESS>:80" 0ms

What did you see instead?

Same goes with nginx3:
<IP_ADDRESS> - - [13/Dec/2017:19:52:07 +0000] "GET / HTTP/1.1" - - - "curl/7.54.0" 43 "Host-nginx1-test-tld-3" - 0ms
<IP_ADDRESS> - - [13/Dec/2017:19:52:07 +0000] "GET / HTTP/1.1" 200 612 - "curl/7.54.0" 44 "Host-nginx3-test-tld-1" "http://<IP_ADDRESS>:80" 0ms

I haven't looked at the code yet. I'll see if I can pin down the issue.


fix: reset styling after server brand

Before:
After:
thnx :3

oh thanks, I use Better F3 mod so I never saw this


Authorization system for SAAS

In order to create a SAAS platform, I need to have some means to auth the user and restrict it to access some ressources that does not belongs to him.
We'll base ourselves on 2 way to restrict the request.

Cookie based for end user (he'll log with a Magic Url sent by mail)
API Key for the servers being monitored (generated through the admin platform by the user).
Can be revoked and refreshed at anytime by the user.

[x] - Can create user
[x] - Can login user
[x] - Can auth user (to test)
[x] - Can auth server (to test)
[] - Can register server


fix(icon-button): remove tooltip and add alt text

applying the alt prop to the button's aria-label
updating examples of suggested alt text
removing tooltip from button
consolidating interactive-icon into icon-button

Coverage decreased (-0.1%) to 88.321% when pulling 1eb312687bd2c6cb8c71482343d2f93e163189bb on ciduarte/iconButton into 1c671d0cc86e96e5e61ac0412a50744003998624 on master.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


DD/MM/YYYY regex

Hi, thank you for opening issue.
Please provide some additional comments on issue.


rails 3.2.1, ruby 1.9.3 & memcached

Gemfile: gem 'memcached'
production.rb: config.cache_store = :mem_cache_store, Memcached::Rails.new("localhost:11211")
Results in: "Could not find cache store adapter for mem_cache_store (cannot load such file -- memcache)"
Googling around I also tried placing " require 'memcached'  " in various strategic places, for example suggested here: http://apidock.com/rails/ActionController/Caching/cache_store%3D/class  ... but it doesn't fix the problem.

Looks like a Rails bug...it's assuming that memcache-client.gem is available even though you are using memcached.gem. Ideally it wouldn't autoload a specific client.


To consider: RapidTide

https://github.com/bbfrederick/rapidtide
cc @poldrack

I'd be happy to help with that...

What stage in preprocessing should rapidtide be run on? If we break it down into fMRIPrep's basic stages:

Motion correction
Slice timing correction
Susceptibility distortion correction
Coregistration to T1w
Normalization to standard space

It definitely needs to be done after motion correction and slice timing correction, and ideally after susceptibility distortion correction, since that can interact with motion.
It can be done any time after that, and there are good reasons to do it in various stages, so this is a topic for discussion.
A) For computational efficiency, it would be best to do it in native space, before Coregistration to T1w or Normalization to standard space, since these typically increase the image size, and compute time is directly proportional to the number of voxels in the image.  However, fmriprep doesn't make a motion, slice time, and sdc corrected image (or transform matrices from native to T1 space) available in the normal pathway, so this may be a non-starter.
B) After T1w coregistration, we have a good brain mask, which can be used to limit the processing area more cleanly than using rapidtide's internal mask generation function.  However, this brain mask removes the superior sagittal sinus, which usually provides a large area with a nice robust signal for generating the initial regressor if you are using rapidtide's internal mask.  The T1w dataset has the brain mask applied, so this data is gone.  This is more an issue for people with gross vascular pathology - using the global mean as a starting regressor usually works fine.
C) After freesurfer runs (if it is run), you can generate your initial regressor using an anatomic mask.  Using cerebellar gray matter tends to give a nice clean initial signal, in my experience, even in a lot of people with disturbed circulation.
B and C can both be done in T1w space or MNI space; which may be larger or smaller (T1w or destination MNI152 space) depends on your target resolution.   If you do it in standard space, you don't have to transform the maps to standard when you're done, so it might be the most efficient computationally.

A) For computational efficiency, it would be best to do it in native space, before Coregistration to T1w or Normalization to standard space, since these typically increase the image size, and compute time is directly proportional to the number of voxels in the image.

Resampling to T1w should not upsample. Might slightly increase the FoV to ensure that the original bounding box fits inside the new, rotated one. I'm not sure from B whether the brain mask is used to focus processing or just to retrieve an initial signal and then all voxels are processed... As long as it accepts a brain mask, the number of voxels should be quite close to the original.

However, fmriprep doesn't make a motion, slice time, and sdc corrected image (or transform matrices from native to T1 space) available in the normal pathway, so this may be a non-starter.

I believe we actually do CompCor in the HMC+STC+SDC space, so this might not cost anything. If we don't create the time series in BOLD space, it would be worth testing whether it's cheaper to run RapidTide in the T1w or generate the BOLD space and run RapidTide.

I'm not sure from B whether the brain mask is used to focus processing or just to retrieve an initial signal and then all voxels are processed... As long as it accepts a brain mask, the number of voxels should be quite close to the original.

By default, the same mask is used to retrieve the initial regressor and the mask to focus processing, but they can be specified individually.  In subjects who have had strokes, or other conditions that can cause a large variation in delay time across the brain (10's of seconds), using the same mask for both can generate a bad initial regressor with multiple delay components that can't be separated by refinement, which hinders delay mapping because the probe regressor has autocorrelation sidelobes.  So in those cases it's good to limit the global mean regressor estimation to a region with putatively "normal" circulation.  In healthy young subjects, this is almost never a problem, since the delay histogram is a single peak with a halfwidth of only a couple of seconds.  Older healthy subjects more frequently have wider, more complex delay histograms.
For data denoising this isn't that big a deal - if you can't distinguish the global mean signal from a delayed copy of itself, regressing out either will remove the hemodynamic noise effectively.  It's only if you care what the delay value is in any voxel that this is an issue you have to deal with.

We do accept lesion masks in T1w space to improve normalization, so we could construct the initial regressor mask by intersecting the FreeSurfer (or FAST) gray matter mask with the negated lesion mask.
We could also consider accepting a manual rapidtide mask, to permit researchers with pathological or otherwise unusual cases to create it directly when the automatic generation fails.

If rapidtide can be run post-fMRIPrep (i.e., on standard space data with no denoising and no smoothing), then I think it would make sense to ensure that there is good documentation on rapidtide's side regarding running on fMRIPrepped data. At minimum, I think that means (1) fMRIPrep config recommendations, (2) recommendations for Freesurfer ROIs, (3) fMRIPrep-specific (or BIDS-Derivatives-specific) confounds ingestion functions, and (4) a wrapper to select fMRIPrep preprocessed data and confounds files, e.g., as a BIDS App.
In case it really would be better to run on T1w-space data instead of standard-space data, then the T1w-to-template transform that fMRIPrep outputs can be automatically applied on rapidtide's side.
Perhaps I'm misunderstanding the ROI issue though.

In the "you didn't ask but I'll answer it anyway" section, whether you should do rapidtide before or after AROMA is unclear.

fMRIPrep outputs the raw AROMA regressors, right? So one recommendation could be to run rapidtide on the regular preprocessed data instead of the AROMA aggressively denoised data, and then include the AROMA components in a GLM with the voxel-wise lagged regressors from rapidtide.

Chris - I think both of those ideas are good ones.  The first is certainly easy to implement - masks in rapidtide are specified as the logical and of an include mask and the inverse of an exclude mask.  So simply passing the lesion mask directly to rapidtide as an exclude mask will do this.  The second might be a little tricky, as you probably need the results of the initial fmriprep run before the masks you will want to use exist.
Taylor - yes, I really do need to up the documentation section, and that's a good section to add first (since I've already worked that all out).  Rapidtide is good about taking in bidsified files as input, but I should change the outputs to be bidsified as well.
You are correct, AROMA and rapidtide can be run in parallel and the regressors can be applied after the fact in one go.

To clarify, should rapidtide then be considered more a post-fMRIPrep workflow, or is it crucial to integrate it into fMRIPrep?
I am concerned about feature creep, but on the other hand I feel like leaving rapidtide out of the workflow is an implicit statement about its importance, rather than the preprocessing stage at which it should be performed. Everything I've read indicates to me that dealing with sLFOs is, well, really important. Would it make sense for fMRIPrep to document workflows designed to operate on fMRIPrepped data in the documentation somewhere? That way users would at least be aware of rapidtide and could use it more easily.

Well, I'm obviously biased, but I'd say that if you don't remove the blood flow signal, any claims you make about "neuronal" connectivity should be taken with a grain of salt.  Making rapidtide part of the workflow removes the friction of applying it, and that's probably a good thing.

That's a good point. One issue, though, is the sheer number of parameters that can be set for rapidtide. Would you recommend hardcoding those parameters in the fMRIPrep calls?
The alternative, I think, is to support configuration files. I'm not sure if there are plans for that yet in fMRIPrep, but it wouldn't be the worst idea for some of the third-party tools like rapidtide, AROMA, and tedana.

One of the goals for 2.0 has been to make the defaults much smarter, and to a large extent that has succeeded.  If you run "rapidtide inputfile outputroot --denoise" that will usually do what you want now.  But it would be good to have a mechanism for setting other parameters.

That definitely makes integration easier!

@bbfrederick What rapidtide-generated files would you like to retain in the fMRIPrep outputs?

That depends a little on how you want to do the final filtering.  I would suggest the _filtereddata.nii.gz file (the data with the hemodynamic signal regressed out), although you could also save the "_lagregressors.nii.gz" file, which is the voxel specific delayed hemodynamic regressors, so you could regress everything out in one model.
Other than that, I'd save the final regressor timecourse, and the _lagtimes.nii.gz, _lagstrengths.nii.gz, _lagsigma.nii.gz, and _lagmask.nii.gz files.  These are the 3D maps of the correlation parameters, and can be very useful if you are interested in the hemodynamic delays.  They are small and generally useful.

I think that produces six new files for each functional run.

_lagregressors.nii.gz
final regressor timecourse (txt file I believe)

This could possibly be integrated into the confounds file, if that wouldn't be too confusing to users.

_lagtimes.nii.gz
_lagstrengths.nii.gz
_lagsigma.nii.gz
_lagmask.nii.gz

Given that rapidtide can be run on fMRIPrep outputs, it seems like the best solution is to build a rapidtide postprocessing BIDS App, like fmripost-aroma will do for ICA-AROMA and XCP-D does for a range of old-school resting-state nuisance regression strategies.

Works for me. What do I need to do for that?
Blaise

I agree too - and I'd be very happy to work with @bbfrederick toward this. cc/ @celprov @acionca

I haven't looked at the source code for fmripost-aroma, but if it's fairly mature then you could adapt that and just swap out the AROMA-specific elements with rapidtide ones.
I'm also thinking of developing a similar workflow to run tedana on fMRIPrep outputs (and hopefully other preprocessing BIDS Apps), so having some kind of generic postprocessing template repo would be very useful for multiple projects.

+1 for a generic postprocessing template repo

I haven't looked at the source code for fmripost-aroma, but if it's fairly mature

It's a stub repository at the moment. If this is important to someone, I would be happy to guide development (https://github.com/nipreps/fmripost-aroma/issues is a rough roadmap), but I don't have the time to spend on it right now. I also think rapidtide would be a good first project, and possibly more impactful.
If you want an example app that takes in an fMRIPrep output directory as an input, you could have a look at https://github.com/nipreps/resampler. It's a little rough, but it's also pretty light. The only thing it uses from other nipreps packages is a data file that makes it easy to query nipreps derivatives with pybids.

I've created nipreps/fMRIPost-rapidtide, so I'm going to close this issue now.


Lokoctl reinstalls kube-proxy and much of control-plane on every update

The "Ensuring controlplane component ..." step installs the kube-proxy and some other control plane component every time you run lokoctl component update. For a large enough cluster this is time consuming and very slow. Especially if the lokoctl cluster apply command fails for some reason and user has to run the command again.
"Ensuring" should just ensure instead of doing update every time.

The "Ensuring controlplane component ..." step installs the kube-proxy and some other control plane component every time you run lokoctl component update. For a large enough cluster this is time consuming and very slow. Especially if the lokoctl cluster apply command fails for some reason and user has to run the command again.

This seems odd. The only thing which should be happening is re-installation of last Helm release for kube-proxy, which assuming no changes on the cluster has been made externally, should be very quick.
What kind of slowness and cluster events do you observe when this is happening? Do you use some external software to modify kube-proxy configuration?
As a workaround, you can also use --skip-pre-update-health-check, which will skip running those health checks.

lokoctl component update

Wait, does it run for lokoctl component update? Really? This is clearly a bug then.

Oops I meant, lokoctl cluster apply. Editing the description.

I also have this problem when creating a cluster and the first run has a provisioning failure, and the second run (with --skip-pre-update-health-check) now thinks that because exists is true, it needs to run this:
        // Do controlplane upgrades only if cluster already exists and it is not a managed platform.
        if exists && !c.platform.Meta().Managed {

Knowing whether the cluster "exists" is maybe a bit tricky, but it would at least be good to have a flag to disable this, similar to --skip-pre-update-health-check.

I also have this problem when creating a cluster and the first run has a provisioning failure, and the second run (with --skip-pre-update-health-check) now thinks that because exists is true, it needs to run this:

Yeah. If provisioning fails, the best thing to do right now it to tear everything down and start from scratch.

I think it would be good to have an option to suppress the control plane updates.

Perhaps. Can you open separate issue for it?

Maybe this is not a case now.


Diagnostics with severity Hint and Information have no visual indication in UI

Diagnostics created from an extension with DiagnosticSeverity.Hint or DiagnosticSeverity.Information have no indication in the UI. They show up very gray in the Errors/Warning selector (ctrl+m) and do not show indicators in the status bar and are not underlined in the editor.

That the don't show up in the status line is by design.
Moving to Joh for the Ctrl+M list.

Hint has no indication by design, Information shows in the editor like a warning, the status bar being aligned with Ctrl+M list is also by design - which we may should discuss.
@hoovercj Can you make validate that severity information shows up? Because according to (this)[https://github.com/Microsoft/vscode/blob/master/src/vs/editor/common/services/modelServiceImpl.ts#L135] it must

Regarding hint having no underline indication by design, what is the intended use-case of then?
@jrieken I'll look into that, yes

It would allow you to hint to a code action provider what to propose

Apologies for the late follow-up.
I just verified that:

Information diagnostics now show up in the status bar
Information diagnostics are underlined the same as warnings
Hint and Information diagnostics are shown in the ctrl+m list just fine.


Override cache key per request

This issue is similar or might be related to https://github.com/RasCarlito/axios-cache-adapter/issues/99. I'm not able to override the cache key per request:
const options = {
    cache: {
        debug: true,
        key: (req) => {
            console.log('This method is not called');
        },
    },
};

axiosInstance.get('/resources', options).then((resp) => {
    console.log(resp.request.fromCache);
    return resp.data;
});

It keeps using the default key.
Here is an example where this bug is exposed (thank you @jahead for the example code from other issue ;) )
https://codesandbox.io/s/axios-cache-api-testing-forked-xr64f?file=/src/App.js

Let me have a look. What version of axios are you using?
This might be fixed with the update to axios 20. Just waiting on @RasCarlito for merging #215

https://codesandbox.io/s/axios-cache-api-testing-forked-y146g?file=/src/App.js
This solution works.
const cache2 = setupCache({
  maxAge: 1 * 60 * 1000,
  debug: true,
  key: (req) => {
    console.log("Using custom cache key");
    return "custom-cache-key";
  }
});

const options = {
  adapter: cache2.adapter
};

axiosInstance.get('/resources', options).then((resp) => {
    console.log(resp.request.fromCache);
    return resp.data;
});

Thanks @jahead! I'm assuming your proposed solution is a workaround for now? Initialising a full adapter seems a bit much. I'll have a look at your PR and maybe just use that instead.

Should now be fixed with latest release https://github.com/RasCarlito/axios-cache-adapter/releases/tag/2.6.0

@RasCarlito I just tried the 2.7.0 release. Unfortunately this issue still exists. Setting a key override has no affect.

@boedy I'll have a look ASAP 🙂

Just to let you know, I'm working on a fix for this. The cache key option was not included in the request override. I have an issue to fix on the tests and I will post the PR and probably make a release right after because I have another PR ready to be merged.

Ok now it should really be fixed in latest release https://github.com/RasCarlito/axios-cache-adapter/releases/tag/2.7.1


genmypy: 0.3.0-1 in 'noetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository genmypy to 0.3.0-1:

upstream repository: https://github.com/rospypi/genmypy.git
release repository: https://github.com/rospypi/genmypy-release.git
distro file: noetic/distribution.yaml
bloom version: 0.10.7
previous version for package: null

genmypy
* Rename genpyi to genmypy (#35 <https://github.com/rospypi/genmypy/issues/35>)

This is another PR to address the review in #29376 and #29377.
Could you review this instead?
As I commented in https://github.com/ros/rosdistro/pull/29376#discussion_r625862878, I renamed my package to genmypy, which is less confusing with genpy. Please let me know if there is any problem.

As I commented in #29376 (comment), I renamed my package to genmypy, which is less confusing with genpy. Please let me know if there is any problem.

Naming sounds fine to me :+1:

Thank you for your review!
I have added a doc entry for genmypy.


White screen on IOS version of the Flutter app

Steps to Reproduce

Run flutter create bug.
Update the files as follows: ...
...

Expected results:
Actual results:

Logs

@Schweinsei007
There's no description / details of the issue you are facing. Please provide flutter doctor -v and a minimal complete reproducible code sample that shows the issue.


attributes missing, only provides getter and setter

In this case, the WebIDL looks like
interface Vector2 {
    void Vector2(float x, float y);
    attribute float x;
    attribute float y;
};

and the TS type is like
 class Vector2 {
        constructor(x: number, y: number);
        get_x(): number;
        set_x(x: number): void;
        get_y(): number;
        set_y(y: number): void;
 }

but the actual object has more than just a getter and setter:
Vector2 {ptr: 5248120}
ptr: 5248120
x: 10
y: 20
__proto__: WrapperObject
constructor: ƒ Vector2(x, y)
get_x: ƒ ()
get_y: ƒ ()
set_x: ƒ (arg0)
set_y: ƒ (arg0)
__class__: ƒ Vector2(x, y)
__destroy__: ƒ ()
x: (...)
y: (...)
get x: ƒ ()
set x: ƒ (arg0)
get y: ƒ ()
set y: ƒ (arg0)
__proto__: WrapperObject

And the live object can definitely be used like vec.x = 10 or console.log(vec.x). Shouldn't the TS type contain x and y as number type, no?

I will make a PR for this, I am just curious if there is a reason why it you didn't do it - maybe it is undefined behavior, something like this @giniedp

I am not sure any  more why i left them out. My initial implementation was based on the binding description of ammo.js
https://github.com/kripken/ammo.js/ where it states

Native JavaScript getters and setters could give a slightly nicer API here, however their performance is potentially problematic.

So maybe i just focused on the getters and setters.
Official documentation has no mention about performance.
https://emscripten.org/docs/porting/connecting_cpp_and_javascript/WebIDL-Binder.html#attributes
Regardless of the potential performance penalty i agree with you, the properties should also be part of the generated type.

should be fixed now. Thanks for the report.


Is it possible to access proxy on another local computer

Hi, is it possible to connect proxy from tunneling
proxy usually use server
pc1 --> proxy[server] --> domain
I need to put proxy behind tunneling
pc1 --> tunneling[server] --> proxy[pc2] --> domain
proxy used as middleman to mimick all connection so I can change myip dynamically to private ip

Hi @goldalworming, support is now provided at https://forum.indiebits.io/. You can log in there with your GitHub account.
Thanks,
//anders


update syn to 0.12

a lot of new lines added mostly because of Cargo.lock. serde_derive using syn hasn't been published yet

Coverage remained the same at 87.54% when pulling 7b1c9a76512a11366ee6f1f9c1563dcea399cf96 on update_syn into 39af9dd3604a9278a2f03861b1112373e7fbeb04 on master.


Using react-resize-observer to observe carousel width

Fixes #160. The react-resize-detector makes the window.resize events superfluous.

[X] an issue linked to the PR

@bunysae
Thanks.
I opened https://github.com/brainhubeu/react-carousel/pull/479 instead to build a testing environment there.


Broken deploy

Every time the site deploys the custom domain needs to be reset. This should be debugged and fixed. Might be solveable by using the actions-based deployment.

Fixed by automatically creating the CNAME file.


DASH: Add a link to Dashboard on non-dashboard or user controller views

Using @mebates 's designs as a guide:

If a user is logged in and not on the dashboards controller, we should include a link up in the top right next to the username to head back to the authenticated_root_url.
We can make these changes in app/views/layouts/_navigation_links.html.erb.

And if all three links at the top can now be purple, even better! 💜

@CamLatimer resolved primary issue in #251; changing this to an integration test to confirm behavior.

This is a good chance to take a stab at writing a capybara integration test if you've never done it before! Using the capybara API, you'll use a fake web browser to basically do the following:

Visit the main dashboard
Assert that the Dashboard link isn't there
Visit a patient's edit URL
Assert that the dashboard link is there
Click the Dashboard link
Assert that you're sent to the main dashboard
Assert that the Dashboard link is gone again

Switching the tag to minitest, but keeping the beginner friendly tag.

Resolved in #272 by @ashlynnpai ! Closing.


loss question

Hi @chufengt ,
Thanks for your great job and sharing.
I just have a question about the loss
in your paper:

it is weight for each attribute
In your code:

it is weight when calculate positive label loss
I think they are not equivalent.
Is there some mistake?
Thanks
Meixitu

Yes, I think there is a mismatch.
In the paper, I give the standard style (Li et al. 2015), which weights for both positive and negative.
In the code, I think I have tried both of these styles and find the results are similar.

@chufengt ，
Thank you.

Meixitu


Nested menu goes out of screen on mobile

Bug, feature request, or proposal:
Bug
What is the expected behavior?
Nested menu should stay on screen if possible or main menu should be closed or something
What is the current behavior?
See screenshot below
What are the steps to reproduce?
Create nested menu and open it on mobile
What is the use-case or motivation for changing an existing behavior?
Using nested submenu on mobile devices
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
All
Is there anything else we should know?

In this case it looks like none of the positions would've fit on screen. This is the one that shows the largest area of the element. We're working on some improvements to the connected positioning that should allow for content to be pushed into the viewport.

@crisbeto is there a way to close main menu like it was working before introducing nested menu? That would be better than this

I have the same problem, even if submenu can fit into window. It never overlaps main menu. Looks like bug for me.

This is an issue not only on mobile. I have a desktop menu that has quite a few items in it, the menu will open but cut off the first entries.

Notice the menu is behind the browser bar and notice it shows Cabin 12 as the first entry. Cabin 1-11 are behind the bar. I can make a hack fix by adding a max-height to the mat-menu-panel but that does not seem the best solution.

Can I get an info about the status of this bug please? @kara @crisbeto

This seems to have been fixed as of Angular Material 7
Is anyone still having this issue?

Hello @aeslinger0 ,
Thank you for this information. I suggest filing a new issue report for click behavior between nested menu and top menu. That way it can get more attention and the information may be more clear to library maintainers. If you can reproduce with Menu examples on docs site, that would be really helpful.
Since the reported issue appears to have been fixed, I'll mark this issue as closed.
Best Regards,
Zach


More logging of errors for LTI exceptions

This isn't capturing what's going on with an invalid record at the moment, so add more logging.

selfie


Enable researcher profile and ORCID synchronization on rest demo

Description
Changes to enabled researcher profile and ORCID synchronization on rest-demo. The login with ORCID is enabled and configured in our local configurations.
This PR includes also a merge with the main (see commit https://github.com/DSpace/DSpace/commit/0d73c761a28e17356cdc8fff40b81151d82df502 to see only the configuration changes)
Checklist
This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome). If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

[X] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & integration tests). Exceptions may be made if previously agreed upon.
[X] My PR passes Checkstyle validation based on the Code Style Guide.
[X] My PR includes Javadoc for all new (or modified) public methods and classes. It also includes Javadoc for large or complex private methods.
[X] My PR passes all tests and includes new/updated Unit or Integration Tests based on the Code Testing Guide.
[X] If my PR includes new, third-party dependencies (in any pom.xml), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
[X] If my PR modifies the REST API, I've linked to the REST Contract page (or open PR) related to this change.

thanks @LucaGiamminonni as agreed in the dev meeting 2022-06-23 we are going to enable as much as possible (optional) features on the official demo, so merging now


How to specify the ip of the tunl0 interface in ipip mode when installing calico

Your Environment

Calico version 3.23.3
Orchestrator version (e.g. kubernetes, mesos, rkt): k8s 1.22.5
Operating System and version: ubuntu 22.04
I did not install calico using tigera. How can I assign a specific ip to the tunl0 interface?
I didn't find useful configuration options in the calico yaml file.

I found that the ip of the tunl0 interface is the first ip in the block assigned to the node.

https://github.com/projectcalico/calico/blob/38a92dfcc791717d2506040c8c24e1d11777c396/libcalico-go/lib/ipam/ipam_block_reader_writer.go#L517-L523
There is a function that uses ippool and hostname to generate ip block.


Improve error message for non-x86_64 platforms

Currently if @bytecodealliance/jco and @bytecodealliance/componentize-js are installed this happens locally:
$ jco componentize -w foo.wit -o bar.wasm foo.js
(jco componentize) Error: componentize-js must first be installed separately via "npm install @bytecodealliance/componentize-js".
    at componentize (file:///home/acrichto/node-v19.8.1-linux-arm64/lib/node_modules/@bytecodealliance/jco/cli.mjs:44427:11)
    at async file:///home/acrichto/node-v19.8.1-linux-arm64/lib/node_modules/@bytecodealliance/jco/cli.mjs:45420:9

I believe the reason for this is that I'm on an AArch64 Linux machine which doesn't have precompiled binaries for Wizer, but it'd have been more helpful for me if the error had mentioned that.

The precompliations for Wizer are listed in the optional dependencies here - https://unpkg.com/<EMAIL_ADDRESS>You do just need to separately run npm install @bytecodeallianace/componentie-js in the environment I believe.
Let me know if I can assist further.

Oh sorry, my point is that there is no precompiled binary for my platform. The error message tells me to run npm install @bytecodealliance/componentize-js, which I already did. The error message I think can be improved here to forward wizer's own error message of "platform not supported".

Ah, okay, noted I'll fix the error handling here.
I see you've already got onto this - as soon as the new release goes out it will be in the version range for componentize-js which should resolve the issue without any release of componentize / jco being necessary.


[chart/redis-ha][BUG] - incorrect master IP being returned by sentinel on startup

Describe the bug
Incorrect master IP is returned by sentinel iff current master-pod is killed, and the new pod starts up before the sentinels can elect a new master. This leads to a timeout when attempting to connect to the cluster, and finally results in a forced failover.
To Reproduce
Steps to reproduce the behavior:

Kill current master pod
Exec onto new pending pod -> config-init container
Run redis-cli -h app-redis-redis-ha -p 26379 sentinel get-master-addr-by-name mymaster | grep -E '[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}'
The ip returned will be of the old master pod (attempting to run redis-cli -h "$MASTER" ping will timeout as expected)

Expected behavior
On pod startup, above command should return IP of newly elected master, leading to a correct addition to the cluster (without the forced failover needing to occur -> as this throws errors on most clients)
Additional context
Perhaps add a pause here to ensure that the correct IP is returned?

@thameezb This may be something I am limited in fixing without a fair bit of time. Sorry for the delay in responding, I'll try and jump on this when I can.

@DandyDeveloper  Any news on this issue. We are also facing issue in client side application.

@devsinghnaini @thameezb I am about to merge https://github.com/DandyDeveloper/charts/pull/23 which should give better results in initialization of these pods and has a much better chance at finding the right master.
Although I haven't personally experienced your issues, can you try testing this

I'm going to close this as we haven't had any feedback. Feel free to reopen.


Added marker support

@lincolnfrog I made the suggested changes. Please, review it whenever you can.

Tried to fix as many as I could. My find and replace regex might not have been bulletproof :)


Add Topic To Set the Maneuver

For better performance and because it's not a parameter, it's better to use topic instead of service to modify the robot maneuver.

After some consideration, it's better to still put the configure maneuver but with adding a way to modify the maneuver via topic publication.


Cannot install: write: socket is not connected

I can install other go projects, but for this one I get this error: write: socket is not connected
$ go install github.com/becheran/roumon@latest
go: downloading github.com/becheran/roumon v1.2.0
go: github.com/becheran/roumon@latest: <EMAIL_ADDRESS>verifying module<EMAIL_ADDRESS>Get<EMAIL_ADDRESS>write tcp [fe80::6e7e:67ff:fedc:d035%utun4]:52931->[2607:f8b0:4005:811::2011]:443: write: socket is not connected

Note: installing the bin directly works. I tried to install other tools built in go and it works, but not fo

Does it still not work? I don't see how this relates to the code since it fails already in the verify module step of go.
What go version and operating system do you use?

Since it's working when downloading the bin, I guess we can close this ticket.
If someone sees this convo at some point and finds/knows the solution, let us know!


Error

Uncaught TypeError: Cannot read properties of undefined (reading 'premium')
Process exited with code 1
If you type a prefix and command that is not in the command, the bot ends.

This isn't an error with the code. Its a your-end error. Please refrain from using issues for errors. If you have any issues, let us know on the discord server.