Copilot Chat Extension SyntaxError :  [ModelMetadataFetcher] Failed to fetch models, SyntaxError: Unexpected token '<', "

Copilot Chat Extension Version: v0.17.1
VS Code Version: 1.19.1 (user setup)
OS Version:
Logs:
2024-07-30 07:42:29.213 [info] [auth] Logged in as user1

2024-07-30 07:42:29.229 [info] [chat] copilot token chat_enabled: true
2024-07-30 07:42:29.229 [info] [auth] Got Copilot token for user1
2024-07-30 07:42:29.659 [info] [ModelMetadataFetcher] Failed to fetch models, SyntaxError: Unexpected token '<', "
<h"... is not valid JSON
at JSON.parse (<anonymous>)

at t.json (c:\Users\XXXXXXX\.vscode\extensions\github.copilot-chat-0.17.1\dist\extension.js:88:17938)

at processTicksAndRejections (node:internal/process/task_queues:95:5)

at UA._fetchModels (c:\Users\XXXXXXX\.vscode\extensions\github.copilot-chat-0.17.1\dist\extension.js:1291:3447)

at UA.getAllChatModels (c:\Users\XXXXXXX\.vscode\extensions\github.copilot-chat-0.17.1\dist\extension.js:1291:2201)

at ZT.getAllChatEndpoints (c:\Users\XXXXXXX\.vscode\extensions\github.copilot-chat-0.17.1\dist\extension.js:1291:6404)

at p (c:\Users\XXXXXXX\.vscode\extensions\github.copilot-chat-0.17.1\dist\extension.js:1115:593)

at sRe (c:\Users\XXXXXXX\.vscode\extensions\github.copilot-chat-0.17.1\dist\extension.js:1115:1332)

at Yct (c:\Users\XXXXXXX\.vscode\extensions\github.copilot-chat-0.17.1\dist\extension.js:1317:883)

at c.n (c:\Users\XXXXXXX\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:144:6384)

at c.m (c:\Users\XXXXXXX\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:144:6347)

at c.l (c:\Users\XXXXXXX\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:144:5804)

2024-07-30 07:42:29.737 [info] [ModelMetadataFetcher] Failed to fetch models, SyntaxError: Unexpected token '<', "
<h"... is not valid JSON
at JSON.parse (<anonymous>)

at t.json (c:\Users\XXXXXXX\.vscode\extensions\github.copilot-chat-0.17.1\dist\extension.js:88:17938)

at processTicksAndRejections (node:internal/process/task_queues:95:5)

at UA._fetchModels (c:\Users\XXXXXXX\.vscode\extensions\github.copilot-chat-0.17.1\dist\extension.js:1291:3447)

at UA.getEmbeddingsModel (c:\Users\XXXXXXX\.vscode\extensions\github.copilot-chat-0.17.1\dist\extension.js:1291:2707)

at ZT.getEmbeddingsEndpoint (c:\Users\XXXXXXX\.vscode\extensions\github.copilot-chat-0.17.1\dist\extension.js:1291:6213)

at sRe (c:\Users\XXXXXXX\.vscode\extensions\github.copilot-chat-0.17.1\dist\extension.js:1115:1436)

at Yct (c:\Users\XXXXXXX\.vscode\extensions\github.copilot-chat-0.17.1\dist\extension.js:1317:883)

at c.n (c:\Users\XXXXXXX\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:144:6384)

at c.m (c:\Users\XXXXXXX\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:144:6347)

at c.l (c:\Users\XXXXXXX\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:144:5804)

Steps to Reproduce:

Open VS Code
Try installing GitHub Copilot Chat throws this exception

getting a similar error with:
[ModelMetadataFetcher] Failed to fetch models, SyntaxError: Unexpected token '<', "<!--# qJfn"... is not valid JSON

Are you behind a corporate firewall of some sorts?
Please also try the latest 0.18 that was just released


Respect custom API URL for all endpoints

https://github.com/muety/wakapi/issues/153 brought up an issue related to the fact that many endpoints inside the CLI are hard-coded. It would be nice to be able to configure the base URL via wakatime.cfg instead, just like it's already possible for the heartbeats endpoint.
For instance, here: https://github.com/wakatime/wakatime/blob/e8deb156f1c2d26e5cf874da97f7b4354b3f5d20/wakatime/api.py#L173

We'll do this in our new Go language version of wakatime-cli being released soon.

Would you accept a PR for this, even though the new CLI is on its way? If so, I'll have a look.


Added Footer dark 8

for issue #839

@Rajdip019 Why have you not merged Footer 6, 7, 8 (white, blue, dark)?
Were they not required ?


Pad control revision 4 GUI

GUI for padctrlr4, should be focused on user friendliness, ease of use, and speed. Space for logging should be incorporated.

See PR #31


OctahedralGaussianGrid not defined

Installed SpeedyWeather.jl on Julia 1.6.4 for Windows. After executing, as in the example,  run_speedy(n_days=30, trunc=63, Grid=OctahedralGaussianGrid, model=:shallowwater, output=true) I get:
ERROR: UndefVarError: OctahedralGaussianGrid not defined
Stacktrace:
 [1] top-level scope
   @ REPL[3]:1

Which version is installed? We have restricted to julia ^1.7 at some point I think, so you probably don’t have v0.4. Please use a newer version of Julia

On 25 Oct 2022, at 14:04, Matteo De Felice @.***> wrote:

Installed SpeedyWeather.jl on Julia 1.6.4 for Windows. After executing, as in the example, run_speedy(n_days=30, trunc=63, Grid=OctahedralGaussianGrid, model=:shallowwater, output=true) I get:
ERROR: UndefVarError: OctahedralGaussianGrid not defined
Stacktrace:
[1] top-level scope
@ REPL[3]:1
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

I have uninstalled my Julia 1.6.4 and installed the 1.8.2 but still I get the version 0.3, getting the same error.

Yes, grids are only implemented with v0.4, check Julia’s package manager to see how you can identify which package is limiting the update or how you can force upgrade to v0.4

On 25 Oct 2022, at 16:09, Matteo De Felice @.***> wrote:

I have uninstalled my Julia 1.6.4 and installed the 1.8.2 but still I get the version 0.3, getting the same error.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.

Closing this as in v0.4 OctahedralGaussianGrid is defined
julia> using SpeedyWeather

julia> OctahedralGaussianGrid
OctahedralGaussianGrid

feel free to raise a new issue for other questions.


Annoying "Assertion failed" logs even when error is handled

Steps to reproduce
Tell us about your environment:

Puppeteer version: 1.3.0
Node.js version: 10.0.0

What steps will reproduce the problem?
Please include code that reproduces the issue.

Have a test that runs page.click('.selector-that-does-not-exist')

What is the expected result?
It should throw an Error that can be caught and not log anything to console
What happens instead?
Assertion failed: No node found for selector: is logged.
This is due to the use of console.assert() in the code: https://github.com/GoogleChrome/puppeteer/blob/3b03ff65c7b369debfcaa67a8673fba105a2d20d/lib/FrameManager.js#L594
In my case, I have to click a button that may or may not be there, so I would like to wrap the call to click() in a try/catch and ignore the No node found error. But even though the error is caught, this line is still logged. The logline doesn't expose any more information than the error. But it spams the test log with red herrings for tests that are passing:
      file tree
Assertion failed: No node found for selector: .toast__close-button
        ✓ does navigation on file click
Assertion failed: No node found for selector: .toast__close-button
        ✓ expands directory on row click (no navigation)
Assertion failed: No node found for selector: .toast__close-button
        ✓ does navigation on directory row click
Assertion failed: No node found for selector: .toast__close-button

Error handling should be in control of the caller of click(), which may chose to log the error (which any test framework would do for you if it is not caught).

That's a good point. Also, Node 10 stopped thowing AssertionError when console.assert fails, so we should migrate to throwing errors explicitly (both in pptr and in our testrunner).


Sec-CH-UA

Chrome now sends Sec-CH-UA: "HeadlessChrome";v="129", "Not=A?Brand";v="8", "Chromium";v="129" headers, despite any overrides. Apparently, there used to be a flag to disable this, but that flag has since been removed.
Can be overriden with extra_http_headers

Since userAgentData is only available in secure contexts, it would likely make sense to construct our own based on the UA rather than try to query userAgentData directly.


kube-router: ipset will only contain one IP if port name is used.

The line causing the issue is at https://github.com/cloudnativelabs/kube-router/blob/cced939a8ba10642afc171c484c0e885a7beb11f/pkg/controllers/netpol/policy.go#L862
Example: https://github.com/BoleynSu-Org/monorepo/blob/badcd3b721a4941724f19fd300de4e072813c1d2/deploy/oj/k3s-cuhk/common/network-policy.yaml#L21
Seems like k3s is using its own fork of kube-router?

It's a fork, but just so that we can embed it in the main process. Have you reported this issue upstream?

cc @manuelbuil @rbrtbnfgl

You linked to a line of code in the upstream project, not in our fork. Can you point to where in our fork it might be, if you think it only exists there?
Our fork is at https://github.com/k3s-io/kube-router/tree/v2.0.0+k3sr3, and has only a few commits that differ from the kube-router 2.0.0 release candidate tag that it was forked at.

As Brad mentioned our fork has minimal changes and the linked code is actually existing upstream. I understand that bugs exist and that they can be quite frustrating, but going out of one's way to specifically call something "buggy" doesn't seem necessary to me in this case.

I think this might be a duplicate of https://github.com/k3s-io/k3s/issues/7391

Yes, it's a tag, not a branch. You can find the upstream tag at https://github.com/cloudnativelabs/kube-router/tree/v2.0.0-rc3 but you will notice it too does not yet belong to a branch that they have pushed. This is just how they have chosen to develop the 2.0 release candidates.

What the meaning of containing only one IP?
What type of traffic do you want to block an how are you trying to test the network policy?
Consider that the node traffic to the pods that are executed on that node is always allowed.

No my questions were related to your deployment. How are you testing that the policy actually works?

Should it be translated to 80 instead of 8080?

could you please give us the steps that you are doing to reproduce the issue? Maybe you are right that the bug could be related to that line of the code but I don't have enough info.

If you try to check the iptables rule on the node for that specific policy what do you get?
sudo iptables-save | grep oj-server-network-policy

I don't know if it strictly related to that line of code but the line that you mentioned it's also upstream
https://github.com/cloudnativelabs/kube-router/blob/prep-v2.0/pkg/controllers/netpol/policy.go#L862
it's related to v2 that supports dualstack we can't use the master branch because it's not supporting it.
In case we found a fix it will be better to fix it upstream and then on our fork.

yes that's the same that I have done to fix it.

I'll update the fix on our fork to have it solved for the next release.

Validated on  branch with commit  / version
Environment Details

Validated on Master Branch 1.27 10fb39ae60abfc60592497903ba734c7e9a17bdf
k3s version v1.27.1+k3s-10fb39ae (10fb39ae)
go version go1.20.3

Infrastructure

[X ] Cloud
[ ] Hosted

Node(s) CPU architecture, OS, and Version:

Linux ip-172-31-33-29 5.15.0-1033-aws #37~20.04.1-Ubuntu SMP Fri Mar 17 11:39:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
NAME="Ubuntu"
VERSION="20.04.6 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.6 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

Cluster Configuration:

1 server

Config.yaml:

Additional files

Testing Steps

Copy config.yaml

$ sudo mkdir -p /etc/rancher/k3s && sudo cp config.yaml /etc/rancher/k3s

Install k3s

Replication Results:

k3s version used for replication:

Run the script:

#!/bin/bash
set -euo pipefail

kubectl delete sts/wordpress || true
kubectl delete deployment/busybox || true
kubectl delete service/wordpress-service || true
kubectl delete networkpolicy/wordpress-network-policy || true

kubectl apply -f - <<EOF
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: wordpress
spec:
  serviceName: wordpress-service
  replicas: 2
  selector:
    matchLabels:
      app: wordpress
  template:
    metadata:
      labels:
        app: wordpress
    spec:
      containers:
      - name: wordpress
        image: wordpress
        ports:
        - name: http
          containerPort: 80
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: busybox
spec:
  selector:
    matchLabels:
      app: busybox
  template:
    metadata:
      labels:
        app: busybox
    spec:
      containers:
      - name: busybox
        image: busybox
        command:
        - sleep
        - infinity
---
apiVersion: v1
kind: Service
metadata:
  name: wordpress-service
spec:
  ports:
    - name: http
      port: 80
      targetPort: http
  clusterIP: None
  selector:
    app: wordpress
EOF

kubectl rollout status sts/wordpress
kubectl rollout status deployment/busybox
! (
    kubectl exec -it deployment/busybox -- wget -O - wordpress-0.wordpress-service.default.svc.cluster.local >/dev/null || echo "failed"
    kubectl exec -it deployment/busybox -- wget -O - wordpress-1.wordpress-service.default.svc.cluster.local >/dev/null || echo "failed"
) | grep failed

kubectl apply -f - <<EOF
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: wordpress-network-policy
spec:
  podSelector:
    matchLabels:
      app: wordpress
  policyTypes:
  - Ingress
  ingress:
  - from:
    - podSelector:
        matchLabels:
          app: busybox
    ports:
    - port: http
EOF

sleep 30
! (
    kubectl exec -it deployment/busybox -- wget -O - wordpress-0.wordpress-service.default.svc.cluster.local >/dev/null || echo "failed"
    kubectl exec -it deployment/busybox -- wget -O - wordpress-1.wordpress-service.default.svc.cluster.local >/dev/null || echo "failed"
) | grep failed

Validation Results:

k3s version used for validation:

![image](https://github.com/k3s-io/k3s/assets/106194120/96c3652f-6076-413c-9307-4923c323a7a0)

NAMESPACE     NAME                                     READY   STATUS      RESTARTS   AGE
kube-system   local-path-provisioner-957fdf8bc-dhx5f   1/1     Running     0          7m40s
kube-system   coredns-77ccd57875-q2q2j                 1/1     Running     0          7m40s
kube-system   helm-install-traefik-crd-fbc7g           0/1     Completed   0          7m41s
kube-system   helm-install-traefik-pdqv7               0/1     Completed   1          7m41s
kube-system   svclb-traefik-53b1fa17-5dlqt             2/2     Running     0          7m27s
kube-system   traefik-64f55bb67d-ktncm                 1/1     Running     0          7m28s
kube-system   metrics-server-54dc485875-f9k8z          1/1     Running     0          7m40s
default       busybox-f7db5bc95-tc5ws                  1/1     Running     0          119s
default       wordpress-0                              1/1     Running     0          119s
default       wordpress-1                              1/1     Running     0          108s

Additional context / logs:


Unable to play Audio on iPhone and iPad device

Hello,
I am facing the problem with the audio play on iPhone devices.It works fine for desktop & Android device.
Please find attached link below:
https://www.balancedview.org/index.php?lang=en&option=com_hwdmediashare&view=mediaitem&layout=popup&id=9400&tmpl=component.
When I trace the issue I get to know that "loadedmetadata" event was unable to trigger for iPhone devices.
We got a reply that "I checked the main website on iOS and works fine. I'm tempted to say it's an encoding issue with your file. Check the Resources page and see if anything of that can help you."
Did you check on iPad or iPhone devices?
Can you please share snapshot for the same with us?
As we tried with different media but was not able to play any of audio file.
Can you please let us know what kind of encoding issue it might be?
Thanks

@sonalitailored Yes, I tried with my iPhone 5S and it worked. Handbrake can help you to optimize your media sources for Web. The loadedmetadata cannot be triggered on iOS; that's a constrain for those devices, so using this tool might be a good start to fix the issues on your media. Only thing I really noticed is that even in desktop, takes some time to play, meaning that either the file is really heavy, or the download index is at a very different position (and not at the beginning) and takes a long time to start the media. Also, this tool (http://renaun.com/blog/code/qtindexswapper/) is worth trying to solve that issue.

Since this issue is not related to the plugin itself, I'm closing this issue. Thanks.

If you have any more questions, please let me know in this ticket


Change 'E to 'E'

Fixes dotnet/docs#28229
The expression is e, but the type of the expression is E. This use refers to the expression, not its type.

Ooh, could you check the Word generator as well? It generates this table too.

(Let me know if you'd like me to - I'm happy to, but can't right now.)

@jskeet The original poster on the issue also commented that this pattern is repeated elsewhere in this clause. Before I check the word converter, and merge this, I'll look for those additional instances.

SGTM, thanks!

@RexJaeschke @jskeet I found the other instances, and I fixes those as well. Do you want to give it a quick look?

Ooh, could you check the Word generator as well? It generates this table too.

@jskeet I did check the word converter output, and the table text matches the markdown casing.


test-branch/execute-job/quoted-authorization/d1ba14bf-d2c6-46b4-85f5-fb83de5a5c0a

PR for testing 62b9762489cadc3148e8481442df349af161e7d6

/canonical/self-hosted-runners/run-workflows 62b9762489cadc3148e8481442df349af161e7d6


Update the java version

Java 17 is no longer supported. The latest mod require Java 21, otherwise this error will occur in the Tracker Status:
Connection Error ('boolean sun.net.www.http.HttpClient.parseHTTP(sun.net.www.MessageHeader, sun.net.www.protocol.http.HttpURLConnection)')

Where do you see those error? Is that in a log file or in the GUI?
Can you post a screenshot?

In the GUI, it's a message in the Tracker Status column. Unfortunately, I can't make a screenshot now, because I made a "dirty" fix in my fork. It works fine with Java 21.

I was going to revert to <IP_ADDRESS> b/c ubuntu doesn't support Java 21 in their repository, but saw the official java repo and I will kindly rip off your solution for installing Java 21. More to follow, thanks!

Thanks for tracking this, I added you to the contributors list!


Upgrade DWD to 1.3.0

How to categorize this PR?

/area control-plane
/kind enhancement
What this PR does / why we need it:
Upgrades the DWD version to 1.3.0. This PR also modifies the clusterRole for DWD to allow access to machine objects in the control plane of shoots.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

The `gardener/dependency-watchdog` image has been updated to `v1.3.0`. [Release Notes](https://redirect.github.com/gardener/dependency-watchdog/releases/tag/v1.3.0)

/cherry-pick release-v1.109

/cherry-pick release-v1.109


Update to pcap2 library

Hi,
It looks like the pcap node does not install in newer versions of nodejs (6.x), and is not updated in a while. Changing to pcap2 seems to work, and seems to have a compatible api (it is a fork of the former). What about using the newer one?
P.S.: Still need to bump the package's version number

Hi,
Sorry @gfcittolin, this is the second PR I have completely missed because 'Watch' was turned off for (my own!) repo.
Looks like a very simple change, so I will merge it now and test later this evening.
Thanks!
nick.

Well, I've already missed issues for the same reason.. shame on us! :)
Thanks anyway, let me know if you need me to test/change something

Hm, just got a crash on my MacBook, which I should probably try and crash:
17 Aug 23:47:35 - [red] Uncaught Exception:
17 Aug 23:47:35 - Error: Don't know how to process TCP option 34

The 'pcap' module was last published 3 years ago.
And 'pcap2' module was last published 2 years ago.
The pcap2 README doesn't really explain why he forked it:
https://github.com/andygreenegrass/node-pcap
He has also disabled the Issue tracker, which is slightly alarming.
Not feeling very comfortable about this...

Oh. Now I'm also not sure what to do. If this broke something then maybe we should revert it.
Also just took a look at the Git repos, and it looks like 'pcap' is being refactored and therefore is "more active" than 'pcap2'. Should we just stick to 'pcap' and wait till a new version is released?

Yeah, the whole thing is very puzzling.
I think andygreengrass just took a snapshot from node-pcap/node_pcap and published it as pcap2 but isn't actively developing it.
Who knows if/when a new 'pcap' will be published.
I am no wondering if node-shark is better/more stable.

I decided to switch back to node_pcap and allow any 2.x.x version.
Loosening the version restriction should allow the current GitHub version to be used, if desired.


docs: Fixed typos

Fixed typos in  README.md

Before you merge just make sure to run yarn docs so the readme is reflected in the documentation page as well.


[Bug][DynamicPartition]Fix bug that Modify a dynamic partition property in a non-dynamic partition table will throw a Exception

Ref #4126

Could you add a UT for this?

@morningman OK, done~

Hi, @morningman , I think the PR should included in 0.13-branch, can you review it? thx~~

Hi, @morningman , I think the PR should included in 0.13-branch, can you review it? thx~~

OK


Unexpected multi-deposit incentive

See context from the 3rd AMA here. The problem is that if someone deposits 32 ETH and early on their balance goes down (even just a bit) then they will have to wait until their balance goes back up to 32.5 ETH (because of hysteresis) for the effective balance to become 32 ETH. This could incentivise some validators to make a second deposit which is not ideal.

The main solutions I see are:

Change the increment/decrement thresholds to x-0.25 and x+0.75
Allow deposits up to 32.5 ETH instead of 32.

Allow deposits up to 32.5 ETH instead of 32.

Deposits above 32 ETH are allowed. Any size above 1 ETH is allowed.

Deposits above 32 ETH are allowed. Any size above 1 ETH is allowed.

1 ETH seems too high, if someone runs 32 validators and 1 ETH is the minimum, this would be an additional validator.

There are two cases:

you deposit and don't get any early punishments (=don't need additional ETH)
you get punished early, and then you will need to deposit >1ETH
not the best UX

Secondary deposits have rather limited use cases, due to the minimum deposit being 1 Ether.
They come in to play if your balance is in the range (x+0.5Ξ,x+1Ξ) for some integer value of x between 16 and 30, as you can carry out a top-up to get yourself above the latch point for the next effective balance increment.  For example, if you had a balance of 29.9Ξ (and hence effective balance of 29Ξ) then a top-up deposit of 1.61Ξ would result in a balance of 31.51Ξ (and hence effective balance of 31Ξ).  For any other situation I believe that the effective balance won't increase further than the the increase in balance.
In general, though, a staker that finds themself in this position (i.e. with a balance less than 31Ξ)is unlikely to be sophisticated enough to carry out this operation (unless there have been some serious finality issues).

My biggest concern is that if I'm not online in my activation epoch, then I'm going to lose rewards for a long period of time. Given this concern, what about some additional logic that the effective balance cannot change within X epochs? I.e. if I was activated at epoch N, my effective balance cannot drop until epoch N+X? If I had any initial liveness issue and I resolved it in X/2  time, then I would be OK.
That would allow some tolerance for first time activations without much change to the rest of the hysteresis effective balance algorithm.

Given that there is a minimum of 8 hours between someone creating a deposit and the validator becoming active, would another few epochs make a difference in terms of the user bringing the validator online?
If it really is a problem then adding a small safety margin to the initial deposit (e.g. an additional 0.01Ξ) should be enough to cover a number of epochs of not attesting without the balance dropping below 32Ξ.

Given that there is a minimum of 8 hours between someone creating a deposit and the validator becoming active, would another few epochs make a difference in terms of the user bringing the validator online?

I don't see an issue with this. If someone were to use an attack that involved activating a validator and never participating, they would be penalized more quickly during that N+X period given an inflated effective balance for a short period of time.
Likewise for the honest participant, if there is a liveness issue in that period, they will have a higher penalty. I think the trade off is worth it to mitigate the scenario outlined in the original comment.
Interested to hear feedback on this idea.

Given that there is a minimum of 8 hours between someone creating a deposit and the validator becoming active, would another few epochs make a difference in terms of the user bringing the validator online?

I read @mcdee's comment not as a suggestion to implement the + x but instead noting that you have 8+ hours to get online what does an additional x epochs buy you? (other than some added consensus complexity)
I'm in favor of what @vbuterin suggested -- Change the increment/decrement thresholds in the to x-0.25 and x+0.75. This is a simple change and provides a "get online" safety marge of 0.25 ETH before the effective change.

I read @mcdee's comment not as a suggestion to implement the + x but instead noting that you have 8+ hours to get online what does an additional x epochs buy you? (other than some added consensus complexity)

An additional X epochs gives you some time to build up a bit of earnings as a safe margin.

There was a discussion about this on Discord.  @djrtwo if there is a true hysteresis on the downside then effective balance can be greater than balance.  I haven't thought it through, but could that cause problems?
An alternative was to go leave the existing system as is except to much reduce the hysteresis from requiring an additional 0.5 Ether before ticking up to requiring an additional 0.05 Ether.  This would maintain the current state where effective balance <= balance at all times, but much reduce the long-term penalty for dropping below an integer Ether boundary.

I haven't thought it through, but could that cause problems?

It takes a bit longer for an inactivity leak to step down and affect finality, but in a true inactivity leak (>1/3 of the network offline or a major partition), this won't affect timing much at all

requiring an additional 0.5 Ether before ticking up to requiring an additional 0.05 Ether

I think the x-0.25 and x+0.75 is sufficient and a bit cleaner. I'm going to code it up now and get a PR for review.

addressed in v0.11.0 release


Add PosgreSQL Studio application to terraref.ndslabs.org

It would be great to have access to BETYdb using PostgreSQL Studio with either a) read-only access to bety6 or b) a local 'sandbox' copy.
For a read only connection, this is how we have provided support for GIS users (as described in documentation).
Users can request ssh login access. But it would be ideal if we could provide a generic existing tunnel.
ssh -nF -L 5432:localhost:5432<EMAIL_ADDRESS>
Then the postgres server is mounted (?) in a way that I can treat it as a local database.
Completion Criteria

[x] instance of PostgreSQL studio on terraref.ncsa.illinois.edu
[ ] ssh tunnel to bety6 (the terraref trait database), ability to connect to bety6 (with viewer account) via ssh tunnel for users with permission

I've added PG studio to the catalog. Given the discussion today, it sounds like the second requirement will require me to come up with a strategy to sync the BETY data to a local instance on the Workbench server.

Strategy for syncing BETYdb: @robkooper is the architect of the system, but there should be two steps

On bety6.ncsa.illinois.edu, set cron job to dump all contents of bety6
on a local postgres server run load.bety.sh -c -r 6
Once this is worked out, document steps required to clone & keep current the terraref trait database (bety6)

A draft workflow that will likely require feedback from @robkooper
Dump
Currently there are cron jobs to dump records from bety6, but neither is sufficient.

dump.bety.sh only dumps records with ids between 6 and 7 billion because the database id is 6

/home/bety/dump.bety.sh -q -l 2 -u YES -m 6 -o /home/bety/bety/public/dump
crontab -l -u bety

pg_dumpall dumps the entire database but does not anonymize users.

crontab -l -u postgres
/usr/bin/pg_dumpall | gzip --rsyncable > /home/backup/postgresql/dumpall.sql.gz

Import
To import data from bety6 using load.bety.sh
load.bety.sh -c -r 6 # to create the database
load.bety.sh -r 6     # to update the database in a cron job

should work, but don't. One reason is that it is missing records from remote sites 0 and 8. We do not want to run load.bety.sh -r 0 because we don't want to bloat bety6 with all of the public data and metadata from that system. The subset of records that I have copied from bety0 to bety6 (e.g. variables, pfts, priors) should be kept.
to import dump
cd /tmp
rsync bety6.ncsa.illinois.edu:/home/backup/postgresql/dumpall.sql.gz
tar -xvf dumpall.sql.gz
psql -d bety < dumpall.sql.gz

The pg_dumpall script could be modified to also provide a dump with anonymized users largely reusing code from line 194 of dump.bety.sh https://github.com/PecanProject/pecan/blob/master/scripts/dump.bety.sh#L194
Related
https://github.com/terraref/reference-data/issues/111
https://github.com/PecanProject/pecan/issues/1355

@robkooper  Looking again at how best to do this.  David mentioned that he's remove viewer access from the users table (https://github.com/terraref/computing-pipeline/issues/262) , so direct connection may be an option again. As discussed last week, we have a few options:

Workbench users can connect directly to TERRA bety instance via internal network to 5432
Periodically copy either dumpall.sql.gz or dump.bety.sh output to Workbench server and import. Both have problems -- dumpall includes non-anonymized data and dump.bety.sh doesn't provide all of the necessary data.  Dump.bety output is easily accessible, dumpall output requires either access to ROGER or bety6 to rsync.

If we can't get access to 5432 directly from workbench via internal network, my inclination is to scp or rsync the dumpall output.  I guess I could setup authorized keys between Workbench and ROGER (or bety6). In this case, I know we'd need to anonymize after import.
Thoughts?

You can use the updated load.bety.sh script from https://raw.githubusercontent.com/PecanProject/pecan/357b70e21592375827e9c55bc5e1ce8e3426bd78/scripts/load.bety.sh
This allows you to specify the URL to get the data from:
load.bety.sh -c -u -m 99 -r 0 -w https://terraref.ncsa.illinois.edu/bety/dump/bety0/bety.tar.gz
load.bety.sh -m 99 -r 6 -w https://terraref.ncsa.illinois.edu/bety/dump/bety6/bety.tar.gz
This will reset the database (-c) and create some default users (-u).

Thanks, Rob. I have an almost working postgis container that uses the above load process. Just doing some sanity checking, I noticed the traits table has no rows?

@robkooper did you set up a cron job to dump and load the data? If so could you paste it here so it will be added to the documentation? https://github.com/terraref/documentation/issues/153

@robkooper PS thanks for such a quick turnaround!

@robkooper regarding the traits table not having any rows ... did you use -l 2 in the dump.bety.sh script to dump data with access_level = 2?

The following runs every hour on the hour:
#!/bin/bash

wget -q -O /home/bety/dump.bety.sh https://raw.githubusercontent.com/PecanProject/pecan/master/scripts/dump.bety.sh
chmod 755 /home/bety/dump.bety.sh

/home/bety/dump.bety.sh -q -l 2 -u YES -m 0 -o /home/bety/bety/public/dump/bety0
/home/bety/dump.bety.sh -q -l 2 -u YES -m 6 -o /home/bety/bety/public/dump/bety6

@craig-willis can you check on the import and see if there is any errors. Looking at the dump there should be traits data:
-rw-r--r-- bety/users 159266947 2017-05-19 09:34 ./traits.csv

Thanks, @robkooper . My mistake, it looks like I was querying the table before the traits data had completed loading.

@dlebauer @robkooper
I have a first-pass at this running on terraref.ndslabs.org. The Dockerfile is on github:
https://github.com/terraref/toolserver-dockerfiles/tree/kitchensink/bety
You can connect to the DB via the Postgres Studio
IP: <IP_ADDRESS>
Database: bety
User:  bety
Password: bety
This is only accessible from within workbench. You should also be able to connect via any postgres client.
Feedback welcome.  In the end, I'll provide a name instead of IP, but for today you just have the IP.

@craig-willis thanks! could you run commands to restrict read access to tables from the bety user? I think it helps to clear the clutter  https://gist.github.com/dlebauer/4aae063ac38d1dba9859da1ddfb5d2c5#file-revoke_select_from_bety_user-sql
Also, when I load the SQL Worksheet and try to run
select (*) from traits;

I get the error message as popup

Server returned TRANSPORT_ERROR with no error message

Actually, that only happens if I hit enter in the window and then try to run it. Somehow hitting enter causes it to log out because when I reload the page I am redirected to login. If I just click the green 'play' button it returns the expected result. Perhaps a bug in the interface, not a big deal.

I've run your SQL statements and will add to the container.

@dlebauer I still need to implement the cronjob on this, but is it otherwise working as hoped?

Yep it is awesome. Thanks!
On Thu, May 25, 2017 at 9:09 AM Craig Willis<EMAIL_ADDRESS>wrote:

@dlebauer https://github.com/dlebauer I still need to implement the
cronjob on this, but is it otherwise working as hoped?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/terraref/computing-pipeline/issues/302#issuecomment-304019260,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAcX5yDa1wOx9A2-5f2TGXBd5xoJ6vImks5r9YucgaJpZM4NGliu
.


Moving spacing as coords attribute + some update

spacing information is currently added as a new coordinate into dft output. I believe it is a strange behaviour.
In this PR, I move frequency spacing information as an attribute of the coordinate itself.
It allows to recall spacing information with:
S = xrft.dft(..., dim='x')
print(S.freq_x.spacing)
Stored as a coordinate attribute, spacing information is kept while doing some operation on xarray S. Moreover, there is now a unique name "spacing".
There was also a bug in _new_dims_and_coords() when called on xarrays with dimensions without coordinates. I propose a simpler version of _new_dims_and_coords() without this bug.

@roxyboy , @rabernat . If you are ok with that, I can start updating the tests who check spacing variable

@lanougue if you want to check if the tests work locally, you can also always run pytest xrft -v in the top directory of xrft.

@lanougue if you want to check if the tests work locally, you can also always run pytest xrft -v in the top directory of xrft.

Thanks ! I did not know about that ;)

To summerize:

spacing (currently assign as a new coordinate) are now defined as an attribute  of the corresponding coordinate. The spacing of all transformed dimensions are all named "spacing" but they can be rercovered through their respective coordinate : output.freq_x.spacing is the spacing of freq_x

No more bug when calling transform on dimension without coordinate. (Strange because I have seen a test somewhere to check that). It rresolve bug1 of #127

_new_dims_and_coords() function simplified

This last commit solves bug2 of #127. No more problem when calling the real transform whose dim is not listed as last argument of dim list.
I added simplifications of transpose operation without defining again the new name of transformed coordinates. It is now automatic.
Sorry for adding modifications in this PR which are not related to "moving spacing attribues"...

Hi @rabernat, What do you think about these changes ?

Fantastic, thank you!


[SSR] Stop resolving externalized dependencies

Describe the bug
AFAICT, Vite should completely ignore externalize SSR dependencies, including:

Not trying to resolve the dependency's module locations
~Not read the dependency's code at all~ (edit: this seems to be the case ✅ )

E.g. https://github.com/vuetifyjs/vuetify/issues/13936; I don't see a reason why Vite should try to resolve the module vuetify/lib/components.
Proposal: Vite should completely ignore externalized deps.
cc @GrygrFlzr
@aleclarson Do you know why Vite touches externalized deps?
@patak-js I'm thinking maybe we should cue in Evan about this at some point.
Reproduction
Vuetify repro: https://github.com/brillout/vuetify3-ssr

Reproduction is here: https://github.com/stephensamra/vite-ssr-pdf-issue

After some digging the root cause of the react-pdf-highlighter error is on react-pdf-highlighter's side.
At least Vite doesn't do dep transpilation here, but it still does dep resolving. (I.e. Vite uses it's owner node resolver instead of using Node.js' built-in require/require.resolve.)
Vite doing dep resolving is the root cause of the Vuetify error.

I'm not getting the same error when running your reproduction at https://github.com/vuetifyjs/vuetify/issues/13936:
Circular dependency: /Users/alec/dev/sandbox/vuetify3-ssr/node_modules/vite-plugin-ssr/dist/esm/page-files/pageFiles.node.js -> /pages/_default/_default.page.server.js -> /pages/_default/app.js -> /pages/_default/vuetify.js -> /node_modules/vuetify/lib/components/index.mjs -> /node_modules/vuetify/lib/components/VCode/index.mjs -> /node_modules/vuetify/lib/util/index.mjs -> /node_modules/vuetify/lib/util/createSimpleFunctional.mjs -> /node_modules/vuetify/lib/util/index.mjs
Circular dependency: /Users/alec/dev/sandbox/vuetify3-ssr/node_modules/vite-plugin-ssr/dist/esm/page-files/pageFiles.node.js -> /pages/_default/_default.page.server.js -> /pages/_default/app.js -> /pages/_default/vuetify.js -> /node_modules/vuetify/lib/components/index.mjs -> /node_modules/vuetify/lib/components/VTimeline/index.mjs -> /node_modules/vuetify/lib/components/VTimeline/VTimelineItem.mjs -> /node_modules/vuetify/lib/components/VTimeline/VTimelineDivider.mjs -> /node_modules/vuetify/lib/components/index.mjs
3:56:56 PM [vite] Error when evaluating SSR module /node_modules/vuetify/lib/components/VBanner/VBannerActions.mjs:
TypeError: Cannot read property 'defineComponent' of null
    at Module.createSimpleFunctional (../../src/util/createSimpleFunctional.ts:9:24)
    at ../../../src/components/VBanner/VBannerActions.ts:3:37
    at instantiateModule (/Users/alec/dev/sandbox/vuetify3-ssr/node_modules/vite/dist/node/chunks/dep-11db14da.js:73323:166)

So it seems like vuetify/lib/components is resolved just fine.

Do you know why Vite touches externalized deps?

I don't think it does? But not clear on your definition of "touches" here.

@aleclarson Yes that's because of this commit https://github.com/brillout/vuetify3-ssr/commit/9ed87bb693ed1b083bb59755aede83da165bc4f5 as it helps Vite's custom resolver.

I don't think it does? But not clear on your definition of "touches" here.

I wasn't sure but actually Vite doesn't seem to transpiled externalized deps (correctly as expected).
But it does, however, try to resolve which sometimes fails, e.g. Vuetify. I reverted the commit at https://github.com/brillout/vuetify3 to reproduce:
10:29:09 PM [vite] Error when evaluating SSR module /pages/_default/vuetify.js:
Error: Cannot find module 'vuetify/lib/components' from '/home/romuuu/tmp/vite-plugin-ssr-vuetify/pages/_default'
    at Function.resolveSync [as sync] (/home/romuuu/tmp/vite-plugin-ssr-vuetify/node_modules/resolve/lib/sync.js:102:15)
    at resolveFrom$3 (/home/romuuu/tmp/vite-plugin-ssr-vuetify/node_modules/vite/dist/node/chunks/dep-11db14da.js:4076:29)
    at resolve (/home/romuuu/tmp/vite-plugin-ssr-vuetify/node_modules/vite/dist/node/chunks/dep-11db14da.js:73358:22)
    at nodeRequire (/home/romuuu/tmp/vite-plugin-ssr-vuetify/node_modules/vite/dist/node/chunks/dep-11db14da.js:73337:25)
    at ssrImport (/home/romuuu/tmp/vite-plugin-ssr-vuetify/node_modules/vite/dist/node/chunks/dep-11db14da.js:73290:20)
    at eval (/pages/_default/vuetify.js:9:31)
    at instantiateModule (/home/romuuu/tmp/vite-plugin-ssr-vuetify/node_modules/vite/dist/node/chunks/dep-11db14da.js:73323:166) (x2)

But it does, however, try to resolve which sometimes fails

That seems like a reason to fix the resolution algorithm, rather than treat externalized deps differently when resolving them.
Have you seen if #3951 fixes it?

My points here are:

Why don't we use Node.js' built-in require.resolve() instead of using our own? In a Node.js context, I don't see a reason why we would want to use something else.
Why does Vite try to resolve an externalized dependency in the first place?

Why don't we use Node.js' built-in require.resolve() instead of using our own? In a Node.js context, I don't see a reason why we would want to use something else.

Once #3951 is merged, modules loaded with ssrLoadModule will use their own require. See here.
const loadModule = Module.createRequire(importer || resolveOptions.root + '/')

Why does Vite try to resolve an externalized dependency in the first place?

No reason currently. Vite could just use require for externals. But when #3951 is merged, custom resolution allows for resolve.dedupe and mode configuration to be respected by all dependencies (compiled or not).

No reason currently, I think. Vite could just use require for externals.

I'd argue that Vite should not try to resolve externalized dependencies then. This is what I expect as a user, and also what the ecocystem at large expects.

Once #3951 is merged, modules loaded with ssrLoadModule will use their own require. See here.

:+1: Neat. Although I'm still wondering; why doesn't Vite use Node.js's built-in require.resolve instead of implementing a customer resolver? (For SSR.)

One thing I'll mention that is somewhat SvelteKit-specific is that we need to bundle all third-party Svelte components because they are distributed as source and need to be run through the Svelte compiler. By far the biggest issue we have is that Svelte components typically get distributed as ESM, but if you encounter one with a CJS dependency it will fail. If we can stop doing new Function and include node_modules in a more standard way with require / import this would help tremendously

@benmccann Your comment seems out of place here, since this thread is about module resolution, not module loading. Nonetheless, have you tried using esm to compile ESM with CJS dependencies on-demand? I might be wrong, but I don't think Node supports ESM with CJS dependency anyway.

I'd argue that Vite should not try to resolve externalized dependencies then. This is what I expect as a user, and also what the ecocystem at large expects.

It's not really an issue if Vite handles it properly. Besides, that would prevent resolve.dedupe and mode from affecting module resolution in SSR, which isn't preferable.

Nonetheless, have you tried using esm to compile ESM with CJS dependencies on-demand?

Like patching Vite to do that? What would get compiled? The ESM to CJS? I think getting that heavy into Vite's internals is far beyond my knowledge of Vite. But why would that be required? I think that if we use Node for the resolving logic we should consider using Node for the loading logic as well because Node has built-in logic to handle it already, so why recreate it?

Your comment seems out of place here, since this thread is about module resolution, not module loading

I'm not incredibly familiar with Vite's internals, but in my mind, the two are highly tied together because the reason you need to do module resolution is for module loading. E.g. Vite can't load ESM modules today because it always tries to require them. However, if it detected that a module was ESM you could import it instead. (I wonder if there might be a way around this by distributing Vite as type: "module" so that you can always do import)

I might be wrong, but I don't think Node supports ESM with CJS dependency anyway.

I'm relatively sure that it does: https://nodejs.org/api/esm.html#esm_interoperability_with_commonjs. It's the #1 thing that users report as far as SSR issues go, so I have to imagine Node supports it based on how many reports of it I've seen. E.g. I just saw that the other day with the unified library: https://github.com/vitejs/vite/issues/4113#issuecomment-883557135

ESM Plan
The fact that Node.js forces a user to migrate her code from CJS to ESM when she adds even only a single ESM-only dependency is quite brutal. I don't think it's a Node.js design flaw, quite the contrary actually. For example, it's been a month that unified is an ESM-only package and since unified is such a widely used pacakge, it will become a tremendous force for ESM adoption.
I was actualy skeptical that ESM will ever get to mass adoption for Node.js user-code, but I'm now confident ESM will spread everywhere even for Node.js user-code. We only need a couple of widely used packages to become ESM-only, and ESM will soon become the de-facto standard.
Let's imagine I've got a Node.js app written with CJS using unified@9, and I'm not using Vite. I now want to upgrade to unified@10. Because unified@10 is a ESM-only pacakge, I'm forced to:

Add type: module in my package.json.
Migrate my whole code from CJS to ESM.

That's a good thing and that's the whole plan here: ESM is spreading.
Vite should respect that clever plan.
So, the only thing Vite should do here is to check whether the user-code's package.json has type: module and if it's the case then Vite doesn't transpile the user-code's import statements to require. That's it.
If a Vite user wants to use unified@10 she has to add type: module to her package.json. And that's a good thing as it respects the ESM-spreading plan. The good news for Vite users is that step 2 can be skipped since Vite user-code is usually already written in ESM.
Bottom line: Vite doesn't need to resolve externalized SSR dependencies, even for ESM.
Not resolving externalized SSR dependencies will work
But, most importantly: why am I confident that Vite shouldn't resolve externalized SSR dependencies?
Today, the vast majority of SSR users are using Node.js servers without a server-side bundler. This means that Node.js is the de-facto standard server-side environment. That's why if Vite stays out of the way and simply lets Node.js do its job, then things will just work.
We can safely make Vite only touch user-code and not dig into node_modules/. (For dev and for externalized SSR dependencies.)

The fact that Node.js forces a user to migrate her code from CJS to ESM when she adds even only a single ESM-only dependency is quite brutal

It doesn't quite require it. CJS can do dynamic imports of ESM. It just can't do static imports of ESM

Today, the vast majority of SSR users are using Node.js servers without a server-side bundler.

Just FYI, SvelteKit has adapters for different environments. The Node adapter runs its code through ESBuild after doing the Vite build. People have also build adapters for other platforms like Cloudflare Workers and Deno. Does Vue by default do only client-side rendering? I had the sense the SvelteKit might be one of the primary ways people use SSR, but I don't know whether that's true. I don't quite understand how whether a server-side bundler is being used would affect this decision though, so none of that contradicts the idea that we might not need to resolve external dependencies.

If a Vite user wants to use unified@10 she has to add type: module to her package.json

SvelteKit projects all have type: "module" by default, but users still can't use unified. If I force unified to be external I get the message Must use import to load ES Module because Vite changed my import statement to require. I know that's a loading issue and this thread is about resolving, but I guess the point I'm trying to make is that it's possible that if we change resolving without fixing loading first it's possible that we're going to be hitting these loading issues way more often making SSR even more difficult to use. Not trying to be a cold blanket here because I support your plan. Just trying to keep the larger picture in mind and order things appropriately

@benmccann

velteKit projects all have type: "module" by default, but users still can't use unified. If I force unified to be external I get the message Must use import to load ES Module because Vite changed my import statement to require.

If the user has type: "module", then Vite should certainly not transpile import statements to require. That's part of the ESM plan I described above.
This means that SveleKit users will be able to use unified (since the user's code does import statements even after transpilation).
The neat thing here is: Vite doesn't need to resolve externalized SSR dependencies. Vite just looks at the user's package.json and if there is a type: "module" then it keeps import statements and otherwise transforms them into require statements. That's it.
To sum up:

Main propsal: Vite doesn't need to resolve externalized SSR dependencies.
ESM proposal: Vite shouldn't transform import statements to require statements if the user has type: "module".
Remove custom resolver propsal #4447: for bundling the entire server-side code with all dependencies, Vite needs to resolve all dependencies. But maybe we can use Node.js's resolver and remove Vite's custom resolver (for SSR at least; we may still need it for the browser-side).

I believe these three proposals will solve many (if not most...) SSR problems mentioned in https://github.com/vitejs/vite/discussions/4230.
Let me know if there are doubts/questions, I'm happy to elaborate further.


Why use custom wizard for creating offers instead of SessionWizardView?

Hi,
Current implementation has a bit hacky way of dealing with ForeignKey's and doesn't support FileField at all. So I wonder is there a design decision behind the implementation or it's just pre Django 1.3?
May be it is a good idea of rewriting it using SessionWizardView?

Closing since the issue is quite outdated and I couldn't find any references of SessionWizardView.


Could not repeat a CpG extraction with the same reference file and its index

Hello,
I was using MethylDackel via Conda to extract CpG from a BAM file created by bwa-meth. After my first attempt of extraction CpG which was successful, my second attempt, aiming at repeating the previous extraction, was not.
I received an error message telling that the program could neither load an index file of a reference genome (hg38 with no alternative chromosomes) nor build one for it. It also suggested that the reference genome file could be corrupted. However, the index file from the previous run was in the same directory as the reference genome.
Could you please let me know what's a solution to this problem.
Thank you very much,
Siripong
P.S. Please see a list of programs and their versions installed in my conda environment below.
Name                    Version                   Build  Channel
_libgcc_mutex             0.1                        main
_openmp_mutex             5.1                       1_gnu
bzip2                     1.0.8                h7b6447c_0
c-ares                    1.19.0               h5eee18b_0
ca-certificates           2023.05.30           h06a4308_0
htslib                    1.12                 h9093b5e_1    bioconda
krb5                      1.19.4               h568e23c_0
libcurl                   7.88.1               h91b91d3_0
libdeflate                1.17                 h5eee18b_0
libedit                   3.1.20221030         h5eee18b_0
libev                     4.33                 h7f8727e_1
libgcc-ng                 11.2.0               h1234567_1
libgomp                   11.2.0               h1234567_1
libnghttp2                1.52.0               ha637b67_1
libssh2                   1.10.0               h37d81fd_2
libstdcxx-ng              11.2.0               h1234567_1
methyldackel              0.6.1                h22771d5_0    bioconda
ncurses                   6.4                  h6a678d5_0
openssl                   1.1.1u               h7f8727e_0
xz                        5.2.10               h5eee18b_1
zlib                      1.2.13               h5eee18b_0

I am also facting the same issue. When the program was run separately for each file it was working but not using bash script

One "fun" issue is that if there is no index for the genome (a .fai file) then running this or any similar tool in parallel will result in each process recreating that file at the same time and overwriting each-others results. My guess is that something like that happened in both of these cases. There's really nothing that can be done within MethylDackel itself to guard against that, "just" ensure that the fasta file is indexed with samtools faidx before running.


Fixes for end of cycle banner

Context
We have EoC banners that let users know about upcoming deadlines (Apply 1 deadline for Apply 1 candidates, Apply 2 deadline for Apply 2 candidates).
These appear at the top of the user's task list when they're applying and their deadline is approaching.
We need to make some fixes and edits so they work as intended.
Changes proposed in this pull request

Banner appearing upon login and not be hidden by the green success message
The banner, with the Apply again deadline, now appears on the post-submission dashboard an application has ended without success and there's still time to Apply again (e.g. before the Apply again deadline)
Added times (i.e. 6pm) and years to the banners, and academic year ranges
Banner will now also appear on the candidate's 'review' page when they're reviewing their application before submission
Using the 'important' banner styling

Guidance to review

Link to Trello card
https://trello.com/c/u06xBaNK
Things to check

[ ] This code does not rely on migrations in the same Pull Request
[ ] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[ ] API release notes have been updated if necessary
[ ] Required environment variables have been updated added to the Azure KeyVault

Thanks @JR-G. Could we add 'starting' to the heading, e.g.: The deadline for applying to courses starting in the....
On a separate note - how come it says 2020 to 2021 academic year rather than 2021 to 2022 academic year?

Thanks @JR-G. Could we add 'starting' to the heading, e.g.: The deadline for applying to courses starting in the....
On a separate note - how come it says 2020 to 2021 academic year rather than 2021 to 2022 academic year?

Ah, in the screenshot? That's just because I grabbed it from an apply 1 application that is still within the apply 2 deadline

Ah, in the screenshot? That's just because I grabbed it from an apply 1 application that is still within the apply 2 deadline

Should still say 2021 to 2022?

I hadn't previously thought of this scenario - when someone has an offer confirmed, perhaps they don't need to see the deadline banner. So they would only then see it again if they withdrew.
Would that be tricky to do @JR-G? I don't think it's a big problem if we can't do it.

I hadn't previously thought of this scenario - when someone has an offer confirmed, perhaps they don't need to see the deadline banner. So they would only then see the banner again if they withdrew their confirmed offer. After which the banner would show the Apply 2 deadline, not the Apply 1 deadline.
Would that be tricky to do @JR-G?

@EmmaFrith Is this using the Display deadline banners cycle switcher? I've just tested this locally using the apply deadline switchers and it appears as if the correct behaviour i.e. no banner appears with a confirmed offer, but will it they withdraw it:

I hadn't previously thought of this scenario - when someone has an offer confirmed, perhaps they don't need to see the deadline banner. So they would only then see the banner again if they withdrew their confirmed offer. After which the banner would show the Apply 2 deadline, not the Apply 1 deadline.
Would that be tricky to do @JR-G?

@EmmaFrith Is this using the Display deadline banners cycle switcher? I've just tested this locally using the apply deadline switchers and it appears as if the correct behaviour i.e. no banner appears with a confirmed offer, but will it they withdraw it:
Confirmed:

Withdrawn:

Yea @JR-G I'm on the display deadline banners setting and it still looks like this:

Same issue in the 'offer accepted' state @JR-G

Just spotted this too - the deadline banner should show here:


Review upgrade-responder telemetry and add it to the agent

Check that it is working with new builds as numbers have fallen off significantly.
Upgrade responder also needs to be able to track agent installs, and stats should be separated across agent and cluster installs.

Have added pull request to fix the code issues.  Once the data is coming in will need to work with EIO to get some additional continuous queries added to our influxdb instance so we can partition the data accordingly.


Fix readme errors flagged by checks

Description
This PR fixes up the readme errors flagged during the merge of our readme script checker: it works! :D https://github.com/Esri/arcgis-runtime-samples-java/runs/1856428169
Just a few things here like fixing up trailing spaces, list order, and tags order. @jenmerritt could you take a look please?

Checklist:

[x] Set target branch to master (current release) or dev (next release)
[x] Request a reviewer
[x] Assign a reviewer
[x] Tag reviewer in comment

@Rachael-E couple more fixes have come up in the re-run of the checks - this might happen where the checks have been able to continue due to your previous fixes, and in continuing they've found further corrections.

Looks good @Rachael-E with the failure due to the bug in the script. Nice that some things have been picked up, but hopefully we can get to the bottom of this bug for future PRs.


Clear LC_ALL for tr call

This resolves additional issues when tr is called in a shell that has set LC_ALL to a specific encoding. In that case, the tr may fail to ignore binary files, expecting that they are in some encoding.
See https://github.com/rbenv/ruby-build/issues/2279

@eregon @mislav I took a stab at this based on the discussion. It should clear LC_ALL in the tr call, which I believe resolves the encoding error on environments with an existing LC_ALL env.
Please check my work.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-k8s-25-main" workflow

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

Questions ?
Please refer to the Backport tool documentation


Make e2e tests work with real or mock backend

Had a discussion with @nicksellen yesterday. There are two difficulties regarding the e2e setup:

how to serve the frontend to the test client
how to handle API requests

The simplest solution for (1) seems to be to run a Express server with the built files (output of yarn build).
For (2), an approach with low initial overhead is to respond to API requests in the Express server. Later on, the API requests should get proxied to a real backend, running inside docker-compose or so.


Tokenizers don't work with OpenSSL 3.0???

THANK YOU to everyone who has worked hard to bring ML to Elixir!!!! Very exciting!!!!
This bug report may reflect user error, rather than an actual bug, because I'm an Elixir ML n00b still trying to understand all the cool stuff you all have built.
I think the error message I'm seeing is because I'm running Ubuntu 22.04.1, which uses OpenSSL 3.0.2 (I see: openssl/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.7 amd64 [installed,automatic]), while tokenizers seems to assume the use of an earlier OpenSSL version (see similar bug reports at https://stackoverflow.com/questions/72133316/ubuntu-22-04-libssl-so-1-1-cannot-open-shared-object-file-no-such-file-or-di). In case this is relevant, I installed Erlang, Elixir, and Rust via asdf.
...
Generated rustler_precompiled app
==> tokenizers
Compiling 6 files (.ex)

16:40:13.320 [debug] Copying NIF from cache and extracting to /home/marlus/.cache/mix/installs/elixir-1.14.2-erts-13.1.2/90822cf8006a0b87e3694ec427cef054/_build/prod/lib/tokenizers/priv/native/libex_tokenizers-v0.1.2-nif-2.16-x86_64-unknown-linux-gnu.so

16:40:13.337 [warn] The on_load function for module Elixir.Tokenizers.Native returned:
{:error,
 {:load_failed,
  'Failed to load NIF library /home/marlus/.cache/mix/installs/elixir-1.14.2-erts-13.1.2/90822cf8006a0b87e3694ec427cef054/_build/prod/lib/tokenizers/priv/native/libex_tokenizers-v0.1.2-nif-2.16-x86_64-unknown-linux-gnu: \'libssl.so.1.1: cannot open shared object file: No such file or directory\''}}

Generated tokenizers app

Again, thank you for building all this cool stuff.
Cheers,
James

FWIW, I tried the exact same thing on my MBP and it ran without an error, consistent with the theory the problem is Ubuntu's use of OpenSSL 3.0, which tokenizers isn't expecting.

Hey! Thanks for the kind note. I'm seeing the same behaviour. I'll look into this and let you know what I find. @josevalim I seem to recall you brought this up when we were having problems with vendoring openssl? @philss is this by any chance to do with static_openssl?

@cigrainger I think the problem is that we don't use vendored SSL for this target - x86_64-unknown-linux-gnu - we only use for MUSL targets. And the compilation is made against the older version of SSL. Thus the user may need to install an older version of libssl by hand.
I'm going to investigate more, in order to confirm my idea.

Thank you, @cigrainger and @philss, for replying so quickly!!! Installing an older version of libssl sounds like the workaround suggested in one of the Ubuntu threads for other libraries that don't yet support OpenSSL 3.0. I'm currently instead playing with Tokenizers on my MBP but will try this if I must run this on Ubuntu. Hopefully Tokenizers will eventually support OpenSSL 3.0, but you're all super busy, so please feel free to close this ticket if you don't have bandwidth for it.
I was browsing through the code you've written for Axon and all your other amazing libraries and don't know how you've managed to accomplish so much so quickly. It's astonishing. Credit to Elixir's brilliant extensibility, your passion/effort to bring ML to Elixir, and the hard work of those who invented these powerful ML algorithms/tools!

I had a go at installing old SSL but -- at least for arm64 (I was running on a Graviton2 instance) -- I was unable to get an OpenSSL 1.0 binary working with it. I actually reverted to just compiling (which worked no problem).

Wow! Tokenizers now compiles without error on my Ubuntu machine!!! Thank you, @philss!!! I'll be pulling for Brazil against Croatia as thanks for this helpful (and clever... instead of fixing the OpenSSL 3.0 incompatibility, you entirely removed the need for OpenSSL!) solution!!! O Campeão voltou!!!

@JamesLavin hahaha, thank you! :D
Vamo ser hexa, Brasil!!

I like your chances, @philss! But still some strong teams left. I didn't see Morocco knocking off Spain, and many (including the refs???) will be pulling for Messi, so some exciting battles ahead. Regardless of the eventual outcome, I suspect Richarlison's insane goal will be the image burned into my mind from this World Cup.

@philss I've attended only three World Cup matches, all in 1994 at Stanford Stadium while I was in grad school there. One of the matches I attended was a 2-0 Brasil victory over Russia. As great as that was, Santana performed before the match!!! I still remember being surrounded by insanely happy Brasilians partying before and after the match. Joyous!  https://www.paloaltoonline.com/weekly/morgue/sports/1994_Jun_17.CEREMONY.html


Uncomment PL-42471

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65b85b1ba6081c7ec7dc3ce6--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65b85bfc5ced5080d778830f--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65b8668160667984effbaf7a--harness-developer.netlify.app


Updated Windows Support Escalation Protocol

Draft is available via the internal SUSE Confluence - https://confluence.suse.com/x/nQIBLw


Add scripts and/or notes for using GPG

I certainly don't ever remember how to do anything and am constantly googling, would be cool to record note and scripts here which are hardcoded with our key.

I personally point people to this page: http://futureboy.us/pgp.html

I would like to say hello and thank you for these lessons.
$ chgrp-R www-data /srv/native


Add liveness/readiness to security faq

Jenkins job istio.github.io/presubmit passed

Jenkins job istio.github.io/presubmit passed

Jenkins job istio.github.io/presubmit passed

Jenkins job istio.github.io/presubmit passed

Jenkins job istio.github.io/presubmit passed

Jenkins job istio.github.io/presubmit passed


Fix spelling errors

Before publishing 0.5 #105 I think these spelling errors should be cleaned up.

Thanks a lot @euphoria

generated and pushed docs with the fixes


Upgrade io.swagger.core.v3:swagger-annotations 2.2.8 -> 2.2.9

This PR contains the following updates:

Package
Type
Update
Change

io.swagger.core.v3:swagger-annotations
compile
patch
2.2.8 -> 2.2.9

Release Notes

swagger-api/swagger-core
v2.2.9: Swagger-core 2.2.9 released!
Compare Source

fix v1 PR Action (#4378)
update readme with minimum JDK 11+ (#4377)
Update 1.5 GH actions (#4374)
added support for generic type bean validation annotations (#4373)
fix #4036 - bundle oneOf/anyOf/allOf as  with  explict prefix (#4371)
update plugin dependencies (#4370)
update dependencies (#4369)
testng update and JDK 11+ build (#4368)
Fix for #4362 - Resolving Schema for system enums fails if enumsAsRef is enabled (#4364)
Fix : Add missing mutualTLS (#4351)
Support of CompletionStage (JaxRS 2.1) (#4342)
Fix #4239: @JsonView ignored for subclasses (#4282)

[ ] If you want to rebase/retry this PR, check this box

Suggested commit message:
Upgrade swagger-annotations 2.2.8 -> 2.2.9


85| Maximal Rectangle | C++

Title -
What will change -
Type of Issue -
Please add/delete options that are not relevant.

[x] Adding New Code
[ ] Improving Code
[ ] Improving Documentation
[ ] Bug Fix

Programming Language
Please add/delete options that are not relevant.

[ ] Python
[x] C++
[ ] Java
[ ] SQL

Self Check

Ask for issue assignment and wait to get assigned to it before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Discord server ✉ - https://discord.gg/CXksGdn
Happy Coding,

I want to work on this issue

can you assign me ?


Request: Expose index filters to node wrapper

I'm building a web UI using Pagefind and it's going great. I'm using the node wrapper API's addHTMLFile function to populate the index.
I'm currently displaying the entire list of Pagefind filters to the user on page load by awaiting pagefind.filters(). This leads to the filters visually popping in once the promise resolves.
What I'd prefer to do is ask the the node index to report the aggregated filters at compile time, which I could then bake into my HTML to prevent content popping.

#371 proposes a solution, but in the meantime here's my workaround. I just parse the HTML myself! 😄
import { parse } from "node-html-parser"; // JSDOC was running out of memory for me, and slower.

/**
 * Parses data-pagefind-filter attributes to exctract all Pagefind filters.
 *
 * Pagefind's node wrapper lib doesn't say which filters it discovered, forcing
 * filter lookup in the client lib, slowing time to first render of filters.
 * This functions gets around that by parsing the HTML again ourselves looking
 * for the same pagefind HTML element attributes which pagefind itself does to
 * reconstruct the same data that [pagefind.filters()] would return.
 *
 * This is an upcomming feature of Pagefind, so this approach will soon be
 * obsolete. See reference issues. This implementation is a best guess effort
 * following the Pagefind docs, it may not perfectly match edge cases in filter
 * names or values.
 *
 * # Reference
 * - https://pagefind.app/docs/filtering/
 * - https://github.com/CloudCannon/pagefind/issues/715
 * - https://github.com/CloudCannon/pagefind/issues/371
 *
 * # Example
 * ```js
 * import assert from "assert";
 * assert.deepEqual(extractPagefindFilters(`
 *   <span data-pagefind-filter="singleName:inlineContent"></span>
 *   <span data-pagefind-filter="singleName">valueContent</span>
 *   <span data-pagefind-filter="name1, name2:inlineContent">valueContent</span>
 *   <span data-pagefind-filter="name1, name2[data-name], name3:inlineContent" data-name="attrValue">valueContent</span>
 * `), {
 *   singleName: { inlineContent: 1, valueContent: 1 },
 *   name1: { valueContent: 2 },
 *   name2: { inlineContent: 1, attrValue: 1 },
 *   name3: { inlineContent: 1 }
 * }
 * ```
 *
 * @param {string} html
 * @returns {object} For brevity "object" is substituted for a proper PagefindFilters type.
 */
export function extractPagefindFilters(html) {
  const pagefindFilters = {};

  parse(html).querySelectorAll("[data-pagefind-filter]").forEach(element => {
    let signature = element.getAttribute("data-pagefind-filter");
    if (!signature) return;

    let filters = [];

    let chars = signature.split("");
    let name = "";
    let mod = ""; // the "[attr-name]" or ":inline content" after the filter name, I'm calling a modifier

    chars.forEach(char => {
      switch (char) {
        case ',':
          if (mod[0] === ":") mod += char;
          else {
            filters.push([name, mod]);
            name = ""; mod = "";
          }
          break;
        case '[':
        case ':':
          mod += char;
          break;
        case ']':
        default:
          if (mod) mod += char;
          else name += char;
      }
    });

    if (name || mod) filters.push([name, mod]);

    filters = filters.map(([name, mod]) => {
      name = name.trim();
      mod = mod.trim();
      if (mod[0] === ":") {
        return [name, mod.substring(1).trim()];
      } else if (mod[0] === "[") {
        return [name, element.getAttribute(mod.substring(1, mod.length - 1))?.trim() || ""];
      } else {
        return [name, element.textContent?.trim() || ""];
      }
    });

    filters.forEach(([name, value]) => {
      if (!pagefindFilters.hasOwnProperty(name)) pagefindFilters[name] = {};
      if (!pagefindFilters[name].hasOwnProperty(value))
        pagefindFilters[name][value] = 1;
      else pagefindFilters[name][value]++;
    });
  });

  return pagefindFilters;
}


Handle other shelves with read correctly and fix shelve reference

This PR removes a false positive detection of the read shelve when the word read exists in any other shelve. E.g. export-read.
Also the reference to this.shelves is not initialized yet, so it returned undefined. We use shelves directly now instead.
Btw. very cool plugin! I am setting it up for myself right now. I hope to contribute some useful features as ideas pop up.

Looks good, thanks for the PR!


Help me to find a Paper+Code+Dataset

Hello . This is my first time in Github.
----->My professor asked me to find a Paper(essay,journal or just explanation of that code+dataset)
and ofcour the Code and Dataset that I need to run it and then learn in by using that paper and explain it!
-----> the subject is a project using Deep learning and working on some images( Like : Smile recognasation using deep learning
with Python) and written with python and the dataset must be images(pictures)
----> I have tried at least 20 Project(Codes) of Guthub(about tumor,traffic,face and .. recognize) but Couldnt run any one of
them!
----> Im working With Google Colab.
--------------> Now if u cant pls help me to find a Simple(few .py codes!) Python Code About Deep Learning + Dataset of images
And of course A Paper that Explains the Code and Method(How it works)
---------------------------------------------------- Thank You Brothers. ------------------------------------------------------------------
<EMAIL_ADDRESS>

This is completely unrelated to DROW.
There are tons of resources out there about deep learning with Python on images.
I'm closing this.

This is completely unrelated to DROW.
There are tons of resources out there about deep learning with Python on images.
I'm closing this.


IOS Status bar font color

How can I change the status bar font color in IOS, without an Appbar?
I've tried AnnotatedRegion<SystemUiOverlayStyle> and SystemChrome.setSystemUIOverlayStyle(..), none of them works.

Using AnnotatedRegion<SystemUiOverlayStyle> is the only way to set the font color of the status bar. The status bar will use white or grey depending on the value of SystemUiOverlayStyle. There is no other way to change the color, nor does it support colors other than white and grey, as these are defined by the system.

Hi @davidp918 ,
This issue doesn't seem to describe a bug or a feature request. Please see https://flutter.dev/community for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you"

Hi @davidp918,
There is already an open issue describing this case https://github.com/flutter/flutter/issues/88431, you may follow up there for further updates closing this issue as a duplicate if you disagree feel free to comment and I will reopen it.
Thank you

The issue mentioned is unrelated as a result reopened the issue, haven't tested yet tho

@davidp918, Please share the output of flutter doctor -v and a minimal and complete reproducible code to better address the issue.


Return 404 on unmatched routes

This commit makes headscale return
HTTP status code 404 (not found) for any
requests it doesn't know how to handle.

[x] read the CONTRIBUTING guidelines
[x] raised a GitHub issue or discussed it on the projects chat beforehand
[ ] added unit tests
[ ] added integration tests
[ ] updated documentation if needed
[ ] updated CHANGELOG.md

@dnaq would you deem this ready for review?

Yeah, it’s just a tiny change. I had just held off on marking it for review to allow for discussions first.

@dnaq great, could you have a look at the lint error? and adding a changelog entry?
otherwise looks reasonable

@kradalby the lint warnings seem to be about the ci environment, not the code (unless I misread them). I’ll add a change log entry


etcd should not produce grpc.ErrClientConnTimeout errors

https://github.com/grpc/grpc-go/blob/4bbe223b12805ab25acbb9d2cadfab2ec9d04bb6/clientconn.go#L46-L49
gRPC has not used this error in a year.  I would like to remove it, since it is dead within our project.
However, it seems etcd is generating and returning this error.  Please find a more appropriate error to return; we will be removing it soon.  (Note: the original PR that deprecated it said it would be removed in 2017Q1.)  Thanks!

@dfawley Thanks for heads-up! We've just deprecated grpc.ErrClientConnTimeout in https://github.com/coreos/etcd/pull/8505.

Thanks for the super quick turnaround!  :+1:


fix query can automatically treat null clause depends on value

Isn't it better that Iciql can automatically treat query condition of value NULL.
When use NULL value with interface like below
Db.open('con').from(r).where(r.column).is(value)...

this create raw sql like below
select columns from r where column = null...;

this where clause doesn't affect anything.
actually this should be
select columns from r where column is NULL...;

Thanks!


WIP: Develop

Pull Request Test Coverage Report for Build 1393

8 of 13 (61.54%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.002%) to 75.87%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/controllers/webhook.controller.ts
0
1
0.0%

src/controllers/register.controller.ts
0
2
0.0%

src/utils/utils.ts
6
8
75.0%

Totals

Change from base Build 1386:
-0.002%

Covered Lines:
2072

Relevant Lines:
2611

💛  - Coveralls

@EmmanuelDemey can you please review this awesome PR ? 💪  🎆


INVESTIGATE: Make Output Ports not always terminate the pipe

This would allow a presenter to "handle" a failure in a way that makes it safe to continue the pipeline.
An example of where this could be useful is for aggregation of failures from multiple pipeline services, such as input port validation and business rule validation. This would require a 3rd pipe to effectively "check" the presenter to see if it has a failure.

This shouldn't be handled in the default pipes and output ports, as it's very specific behaviour that's likely not useful to the majority of consumers.
If people have a need for this behaviour, they can code it themselves - it's not particularly difficult to copy the existing pipe and output port and modify the output port to return a Task and have the pipe use that bool as part of it's logic to see if it should continue.


update image and instructions for Data Science Experience 'create notebook'

Unfortunately, the UI for DSX has changed, and the process for creating the notebook looks different.
Please update the image and instructions.
This is no longer valid:
Use the menu on the left to select My Projects and then Default Project. Click on Add notebooks (upper right) to create a notebook.
See https://github.com/IBM/pixiedust-traffic-analysis#2-create-the-notebook
for an example of the new method.

I dont see any change in the DSX UI. We have provided instruction to use the "Default Project". The other journey has an additional instruction to create a new project.

A new user will see the following:

I think there used to be a menu on the left, as your instructions indicate. I don't see one now.
The menu bar is now on top, at least in my browser. It is called "Projects" now, although previously it may have been on the left and labeled "My projects".

Updated the instructions to say 'Projects'. Please see if this suffices.


bug(update): ng update is not migrating mat-font-size

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
ng update is not migrating mat-font-size
Reproduction
Steps to reproduce:

Have a style file which is using mat-font-size mixin
Run ng update @angular/core@13 @angular/cli@13 @angular/cdk@13 @angular/material@13
Check if mat-font-size is migrating to mat.font-size

Expected Behavior
ng update should migrate mat-font-size
Actual Behavior
ng update is not migrating mat-font-size
Environment

Angular: 13.3.11
CDK/Material: 13.3.8
Browser(s): NA
Operating System (e.g. Windows, macOS, Ubuntu): Windows

Can you post what the unmigrated code looks like? The old mat-font-size is a Sass function, not a mixin.

Can you post what the unmigrated code looks like? The old mat-font-size is a Sass function, not a mixin.

@import "@angular/material/theming";

$config: (
    display-3: (
        font-size: 56px,
        font-weight: 400,
        line-height: 56px,
    ),
);

.custom-class {
    @debug mat-font-size($config, display-3);
    font-size: mat-font-size($config, display-3);
}


Redirect to https

Hi! I'm running my express server inside a docker container, but I don't get to redirect http requests to https protocol.
I've tried with a few options, as for example, adding a 'express-http-to-https' to server.ts or enabling trust proxy but I get nothing.

Thanks

Something like this would work:
force-https.js:
function requireHTTPS(req, res, next) {
  if (req.get('X-Forwarded-Proto').indexOf("https") === -1) {
    return res.redirect('https://' + req.headers.host + req.url);
  }
  next();
}
module.exports = requireHTTPS;

In your server file:
const express = require("express");
const app = express();
const secure = require("./force-https");
app.use(secure);
// ...

You can have a middleware (which is probably the easiest).
But you can also run your application on port 443 and then run a separate 'app' on port 80 with the sole purpose of upgrading requests to https. I like to do the latter... I call it a 'gatekeeper':
const express = require("express")

const gatekeeper = express()
.use(function(req, res) {
    res.status(301).redirect(upgrade_url(req)) // <------- THIS MIDDLEWARE is actually all you need!
})
.listen(SERVER_PORT, SERVER_HOST, function() { // run separate router to migrate requests from HTTP to HTTPS
    console.log(`Application SSL-Gateway with PID ${process.pid} is running and is listening on port ${SERVER_PORT}.`)
})

Here's how I'd then run the actual application:
const app = express()
app.use(require("./controller.js"))

const appserver = require("https")
.createServer(TLS_CREDENTIALS, app)
.listen(SERVER_PORT_TLS, SERVER_HOST, function() {
    console.log(`Application with PID ${process.pid} is available on ports ${SERVER_PORT} and ${SERVER_PORT_TLS}. Visit https://localhost:${SERVER_PORT_TLS}`)
})
.setTimeout(SERVER_TIMEOUT)

Both the above are excellent answers 👍
I'm going to close this since no response from OP, so assume their question was answered by the above :)


dtcgen style --tool figma is not working

The figma API endopint seems to be changed.
https://www.figma.com/developers/api#get-team-styles-endpoint

The figma API endopint seems to be changed. https://www.figma.com/developers/api#get-team-styles-endpoint

it's totally missing the point.
Current conversion procedure is roughly like this:

extract styles with get-team-styles-endpoint endpoint
extract nodes with get-file-nodes-endpoint endpoint where styles of step1 are originally defined
filter out nodes of step2 with rules:

name matches the keyword defined in dtc.config.json
type is RECTANGLE

translate nodes of step3 to style objects that the step5 can handle
Convert style objects into asset files that iOS can handle

I could confirm that step1,2 is working but step3 doesn't output anything.
To fix that, just change the keyword defined in dtc.config.json . But the filtering logic looks TOO STRICT.
Then, the name of each asset is taken from node not by style object. It should be the name of style.
So, my proposal is...

to take over style object to step4 somehow
to use name and style_type of style object to distinct Color style

let's try later on.


Room.venue_address raises when address is None

The property "venue_address" on models.Room incorrectly assumes that venue will have an address.  If it does not, an exception is raised.
This seems to be demonstrated already in a failing unit test. I'm not sure how this came to be checked in while failing.
======================================================================
ERROR: test_view (pr_services.pr_tests.TestSessionManager)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/mhrivnak/git/openassign-server/pr_services/pr_tests.py", line 1313, in test_view
    ret = self.session_manager.detailed_surr_view()
  File "/home/mhrivnak/git/openassign-server/pr_services/testlib/__init__.py", line 75, in _wrapper
    return method(token, *args, **kwargs)
  File "/home/mhrivnak/git/openassign-server/pr_services/event_system/session_manager.py", line 341, in detailed_surr_view
    ret = Utils.merge_queries(ret, facade.managers.RoomManager(), auth_token, ['name', 'venue_name', 'venue_address'], 'room')
  File "/home/mhrivnak/git/openassign-server/pr_services/utils/__init__.py", line 90, in merge_queries
    {'member' : {'id' : q2_ids}}, q2_requested_fields)
  File "/home/mhrivnak/git/openassign-server/pr_services/object_manager.py", line 187, in get_filtered
    result = self.Filter(self)._filter_common(auth_token, filters, field_names)
  File "/home/mhrivnak/git/openassign-server/pr_services/object_manager.py", line 277, in _filter_common
    return facade.subsystems.Getter(auth_token, self.my_manager, query_set, field_names).results
  File "/home/mhrivnak/git/openassign-server/pr_services/gettersetter.py", line 70, in __init__
    self.process(auth_token, requested_fields)
  File "/home/mhrivnak/git/openassign-server/pr_services/gettersetter.py", line 78, in process
    ret[f] = self.getters[f](item, f)
  File "/home/mhrivnak/git/openassign-server/pr_services/gettersetter.py", line 87, in get_general
    return getattr(result_object, field_name)
  File "/home/mhrivnak/git/openassign-server/pr_services/pr_models.py", line 1937, in venue_address
    return self.venue.address.address_dict
  File "/home/mhrivnak/pythons/openassign/lib/python2.6/site-packages/django/db/models/fields/related.py", line 315, in __get__
    rel_obj = QuerySet(self.field.rel.to).using(db).get(**params)
  File "/home/mhrivnak/pythons/openassign/lib/python2.6/site-packages/django/db/models/query.py", line 349, in get
    % self.model._meta.object_name)
DoesNotExist: Address matching query does not exist.

This may be a fixture problem.  The fixture "legacy_objects.json" shows this venue with an address FK of "1", but I don't see in any fixture that an address entry is created to match it.

Interesting. I wouldnt have checked in with a failing test. For some reason that test isn't failing for me. I think you're right about the issue and I'll fix the fixture.

I'm guessing venue_address should just be None when there is no address.

Checkout the issue/83 branch and let me know if the test is still failing.

Interestingly, it is currently passing for me on both the dev and issue/83 branches.


Symlinking on deploys & Rollback functionality

My IDE also removes tailing spaces, which ansible-lint also classifies as an invalid thing
Anyway.
Changes:

Adds 3 states of the web: new, current (symlinked to new), old
Reduces downtime by moving service stop to last possible moment, right before the symlink
Adds Rollback functionality & new playbook to do so

Tests:
Ideally, this would be tested on a real server, but I don't think that's possible?
Issues fixed:
https://github.com/Glimesh/ops/issues/7
https://github.com/Glimesh/ops/issues/3

Sorry for the delay in review this, we've actually been using it in production for a bit :)
It's a great change, thank you for working on it! The one problem I noticed is old deploys are not being cleaned up like they should be. Let me know if you need help debugging!


Crashes on launch, exception thrown in rope

When I launch Spyder, rope throws an exception (attached screenshot).  Some details on my install:
Windows 7 Professional 64bit
Python 3.4 amd64
I've installed the relevant PySide and PyQt4 libraries.
Any help hugely appreciated!

You're using the wrong version of rope for your Python version. Please run
pip uninstall rope
pip install rope_py3k

Thanks Carlos, much appreciated. I'll give that a go.
All the best,
Stuart.
Stuart Baylis
+44 7969 623438

On 23 Oct 2015, at 20:42, "Carlos Cordoba"<EMAIL_ADDRESS>wrote:
You're using the wrong version of rope for your Python version. Please run
pip uninstall rope
pip install rope_py3k
—
Reply to this email directly or view it on GitHub.

Hi Carlos.  That didn't work I'm afraid.  When I try to uninstall rope, I get the error below.
When I install rope_py3k, I still get the same error when launching Spyder.

Well, I don't know how you installed rope. You need to look in your site-packages directory and remove rope manually.

I had the same problem. I solved it by deleting the following directory:
Python34\Lib\site-packages\spyderlib\utils\external\rope
Now spyder opens up okay, but shows that jedi and rope are not installed. Have not yet looked into that,

Quite right, that's sorted it.  It looks like the Pyhton3 AMD64 version of Spyder that I installed came bundled with an incorrect version of rope.
Got Spyder working now - great development environment!

@vishniakou, thanks for finding the cause of this problem. We'll fix it for Spyder 3.0.

@ccordoba12 Is this not tested by travis/appveyor ? I didn't look precisely but I thought external dependencies were tested.

I think this problem is caused by our Windows exe installers (which are untested) because they install a copy of rope in utils/external.
I hope this would be fixed when we stop to distribute those installers and only use wheels.

This is fixed now in pull request #2831 and it's going to be part of Spyder 3.0

Spyder 3.2.6 is not recognizing the jedi version 0.11.
I recomend you to install the jedi version 0.10.0
pip uninstall jedi
pip install jedi==0.10.0

Now it's ok

@eduamf We appreciate you trying to help. However, are you aware the issue you are responding to was closed almost two and a half years ago, likely has nothing to do with what you posted, and any issue is not, in fact "Spyder not recognizing jedi version 0.11" but rather incompatibility between certain third-party, non-Spyder packages? Furthermore, the commands given would likely break most users' installs who use the recommended Anaconda distribution, both due to installing via pip and because jedi 0.10 is not compatible with the current version of parso, 0.11, which breaks Spyder's completion, introspection and help and causes continuous error messages when trying to use them.

?Thank you!

De: C.A.M. Gerlach<EMAIL_ADDRESS>Enviado: domingo, 18 de março de 2018 22:46
Para: spyder-ide/spyder
Cc: Eduardo Antonio Mello Freitas; Mention
Assunto: Re: [spyder-ide/spyder] Bundled rope version is causing Spyder to crash (#2779)
@eduamfhttps://github.com/eduamf We appreciate you trying to help. However, are you aware the issue you are responding to was closed almost two and a half years ago, likely has nothing to do with what you posted, and any issue is not, in fact "Spyder not recognizing jedi version 0.11" but rather incompatibility between certain third-party, non-Spyder packages? Furthermore, the commands given would likely break most users' installs who use the recommended Anaconda distribution, both due to installing via pip and because jedi 0.10 is not compatible with the current version of parso, 0.11, which breaks Spyder's completion, introspection and help and causes continuous error messages when trying to use them.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/spyder-ide/spyder/issues/2779#issuecomment-374078445, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AWYcLwY9aTnjtDXTFVgIl7YKESc74cTbks5tfw4EgaJpZM4GUp5b.