IIS 7.5 to many redirects

After updating the aplication the web site does not open anymore.
I've checked the Permissions, Authentications and etc.
The only clue that I've got was on the conversion to Application that if i click the Test button I receive a message of "Invalid Application Path"
I am using Windows Server 2008 R2 with IIS7.5

"conversion to Application that if i click the Test button" - I don't think I understand that bit - can you expand?  What version were you running before?
Make sure you've got .NET 4.6 on your server.

I am using .NET 4.6
when on the GUI if I click with the right button on the mouse to Convert to Application, it opens a window and there we have a button called "Test Settings", If I click it i receive the message bellow

Have a look at this:  http://stackoverflow.com/questions/5794063/invalid-application-path
There are about 100 million ways for IIS to be configured so it won't run a web application, and I'm afraid it's beyond the very limited resources of the Bonobo team to work through them all with everyone, sorry.

How can I get the prior version of 6.0? That used to work

There are some old versions here:
https://github.com/jakubgarfield/Bonobo-Git-Server-Web/tree/master/content/resources/releases


chore: added caching of genesis block, since it doesn't change at all.

As part of optimization. The Genesis block doesn't change, so we should cache it.

This halved the response time for e.g. /network/status from 1.3 seconds to 0.6s


SyntaxError: '=' expected

Description
I saw the recent v4 release and I wanted to upgrade to it in my solidity-template, but there is no CHANGELOG explaining what changed since v2 or v3.
Simply installing<EMAIL_ADDRESS>and<EMAIL_ADDRESS>gets me this error:
SyntaxError: '=' expected. (8:15)
   6 |   import { Contract, ContractFactory, Overrides } from "@ethersproject/contracts";
   7 |
>  8 |   import type { Greeter } from "./Greeter";
     |               ^
   9 |
  10 |   export class GreeterFactory extends ContractFactory {

See the full stack trace here.
How to Reproduce

Clone paulrberg/solidity-template
Switch to the typechain-v4 branch
Install dependencies with yarn
Run yarn typechain

@PaulRBerg do the typechain package release notes include the necessary info?
@krzkaczor we should add release notes for target packages too

Do the typechain package release notes include the necessary info?

Not really. It's not clear from either the following statement:

Do not camel case contract names

Or #293 what exactly I should do to make the upgrade to TypeChain v4.

It's was actually a previous release: https://github.com/ethereum-ts/TypeChain/releases/tag/typechain%403.0.0
You are running an old TS version (i think before 3.7) that doesn't support type imports (export type syntax). Upgrading typescript should fix this problem.
Please reopen if it still doesn't work.

Thanks @krzkaczor! I think it'd be worth it to mention that TypeChain v4 only works with TypeScript v4. Lots of people are still using TypeScript v3.

@PaulRBerg which TS version did you try before? I think it only requires TS3.7. There is a peer dependency for typechain: ^4.0.0, I was also confused by that at first :smile:
Anyway, we'll add a peer dependency on typescript too so you'll get warned if your version is too old.

v3.9.7: https://github.com/PaulRBerg/solidity-template/blob/4e7d7b3907082f34d951a51600e57e735af8beef/package.json#L45

Fixed in: 0f661c6 (#300)
Btw. bonus q: is it possible in semver to say that everything above 3.8 including next major is fine?

Btw. bonus q: is it possible in semver to say that everything above 3.8 including next major is fine?

I think that ^3.8.x should do the trick:
https://jubianchi.github.io/semver-check/#/constraint/^3.8.x

^3.8.x alows 3.9 -- I think @krzkaczor wanted to allow 4.0 too. I don't think that's possible with a single operator if you still want to not allow 5.0.

Oh, yes. That doesn't look like it's possible:
https://github.com/semver/semver/issues/395

Just to clarify - I want to match 3.8, 3.9, 4.x even future 5.x and 21.x releases.
I think it's simply not possible because this is not how semver works :/ Obviously, TS doesn't comfort to semver spec so it is what it is.

@krzkaczor can't you just specify >=3.8.0 then?

Oh, actually it seems that it works (at least according to: https://jubianchi.github.io/semver-check/#/>%3D3.8.0/5 ) KISS! :D


Update dfont.c

move the node to the end of the list, so can't be searched.

The list is the circular linked list, so there is no difference.
release_space use the version to decide remove the node or not.
Use list_move_tail would be better, thanks.


script tag, not generating a closing tag if used without inline script

Hello, when using script tag, without any inline script, e.g.:
script( src := "/addr.js" )

the tag that gets generated is <script src = "/addr.js"/>
and not <script src = "/addr.js"></script>
as one would want. What could I be doing wrong? Thanks

We have a test that verifies that this doesn't happen
https://github.com/lihaoyi/scalatags/blob/master/scalatags/shared/src/test/scala/scalatags/generic/ExampleTests.scala#L13-L42
My money is that someone else, somewhere else in your code is doing this

e.g. see https://github.com/lihaoyi/scalatags/issues/48


Need an icon in the tabs for flipping files to other pane on Brackets 1.6

But of course!

it's done v5.1.0 :smirk_cat:

Cool! :)


Topic needed: Contributing - Guide

A guide for contributors who wish to write a guide

When to write a guide
Before you start
Outline
Supporting materials
Style

Tweaks needed, but min-complete via #74


Pin to upstream Tree-sitter revision

This resolves a handful of buffer overflows related to Tree-sitter that were resolved in the upstream version of this repo, namely within https://github.com/tree-sitter/tree-sitter/pull/2408.
Additionally, this latest version has patches for a number of bug fixes, including seg faults and out-of-bounds accesses.
Compare: https://github.com/simonbs/tree-sitter/compare/v0.20.9-beta-1...tree-sitter:tree-sitter:3b0159d25559b603af566ade3c83d930bf466db1

After Tree-sitter added a Package.swift file to their repository, Runestone was shortly pinning to a specific commit in the Tree-sitter repository. This was added in #296.
However, it turns out that Swift Package Manager regards packages that use commit-based dependency requirements as unstable and these packages cannot be depended on by packages that use version-based dependency requirements. This is detailed in the following snippet from swift-package-manager's documentation for the Package class.
/// Returns a requirement for a source control revision such as the hash of a commit.
///
/// Note that packages that use commit-based dependency requirements
/// can't be depended upon by packages that use version-based dependency
/// requirements; you should remove commit-based dependency requirements
/// before publishing a version of your package.
///
/// The following example defines a version requirement for a specific commit hash.
///
///   .revision("e74b07278b926c9ec6f9643455ea00d1ce04a021")
///
/// - Parameters:
///     - ref: The Git revision, usually a commit hash.
static func revision(_ ref: String) -> Package.Dependency.Requirement

Therefore I forked Tree-sitter and added the 0.20.9-beta-1 version so Runestone can continue to use version-based dependency requirements while depending on Tree-sitter through Swift Package Manager. This change was made in #306.
Introducing commit-based dependency requirements will make it difficult for developers to depend on Runestone. Therefore I'd like for us to stick with version-based dependency requirements.
@eliperkins Would it be an acceptable option for you if I update my fork of Tree-sitter and add a new version called 0.20.9-beta-2? That version will contain all the changes from Tree-sitter's main branch and will allow us to keep using version-based dependency requirements.

TIL! Thanks for calling this out, I had no idea about the implications. I learned something today!

Would it be an acceptable option for you if I update my fork of Tree-sitter and add a new version called 0.20.9-beta-2? That version will contain all the changes from Tree-sitter's main branch and will allow us to keep using version-based dependency requirements.

Yeah that sounds like a great solution. I'll chat with folks who work with Tree-sitter to figure out what it'd take to cut a new version of upstream too, since that would theoretically remove the need for a fork too, I think.
Thanks @simonbs!

TIL! Thanks for calling this out, I had no idea about the implications. I learned something today!

Would it be an acceptable option for you if I update my fork of Tree-sitter and add a new version called 0.20.9-beta-2? That version will contain all the changes from Tree-sitter's main branch and will allow us to keep using version-based dependency requirements.

Yeah that sounds like a great solution. I'll chat with folks who work with Tree-sitter to figure out what it'd take to cut a new version of upstream too, since that would theoretically remove the need for a fork too, I think.
Thanks @simonbs!

Oops. I didn't mean to close the issue.
I have published 0.3.3 which depends on<EMAIL_ADDRESS>This release contains a snapshot of tree-sitter's master branch taken on November 29th, 2023.
This should address your challenge for now, @eliperkins.

I'll chat with folks who work with Tree-sitter to figure out what it'd take to cut a new version of upstream too, since that would theoretically remove the need for a fork too, I think.

@eliperkins Thanks! It would be great if we'll get a new official version soon 🤞

Closing this out for now, since the latest Runestone version brings in the latest version of Tree-sitter through a fork! 👍


Test failing on Linux

I did the procedure of running
]add GLMakie
and
test GLMakie.
However, tests run fine on my windows machines but I tried the tests on 3 Linux machines with Julia 1.5.3, 1.5.4, 1.6.0 and 1.6.1 and tests fail with the message
  Expression: idx == N - 1
   Evaluated: 0 == 99999
Stacktrace:
 [1] macro expansion
   @ .../packages/GLMakie/5uIRQ/test/unit_tests.jl:36 [inlined]
 [2] macro expansion
   @ .../julia/stdlib/v1.6/Test/src/Test.jl:1151 [inlined]
 [3] macro expansion
   @ .../packages/GLMakie/5uIRQ/test/unit_tests.jl:28 [inlined]
 [4] macro expansion
   @ .../julia/stdlib/v1.6/Test/src/Test.jl:1151 [inlined]
 [5] top-level scope
   @ .../packages/GLMakie/5uIRQ/test/unit_tests.jl:10
Test Summary:                                             | Pass  Fail  Total
unit tests                                                |    8     1      9
  Window handling                                         |    6            6
  Pick a plot element or plot elements inside a rectangle |    2     1      3
ERROR: LoadError: LoadError: Some tests did not pass: 8 passed, 1 failed, 0 errored, 0 broken.
in expression starting at /.../packages/GLMakie/5uIRQ/test/unit_tests.jl:9
in expression starting at .../packages/GLMakie/5uIRQ/test/runtests.jl:14
ERROR: Package GLMakie errored during testing

The funny thing is that GLMakie can indeed produce plots, however I am unsure if it is safe to use and fully commit on, if the tests fail.

This happens for me too, no idea why. The linux ci is fine and I think I checked that test manually when it first happened to me. Maybe it's a timing thing and the point picking runs before the plot has updated?

I currently don't have a PC with linux to check this, so hard to debug... If anyone can try to make an mwe out of the test code that fails, we can try to pin it down...

So for me as well:
Test Summary:                                             | Pass  Fail  Total
unit tests                                                |    8     1      9
  Window handling                                         |    6            6
  Pick a plot element or plot elements inside a rectangle |    2     1      3
ERROR: LoadError: LoadError: Some tests did not pass: 8 passed, 1 failed, 0 errored, 0 broken.

Copying the offending @testset begin ... end into a julia instance (with the relevant surround code exectued) fails. Copying the content succeeds.

So indeed evidence for a timing problem...

Maybe this fixes it? https://github.com/JuliaPlots/GLMakie.jl/pull/187

That fixed it for me.


[Sema] Require any for SE-0309 existential types.

This diagnostic for requiring any on existential types with Self or associated type requirements has already been staged in as a warning. Upgrade the warning to an error, per the SE-0335 proposal.
Resolves: rdar://92122082

@swift-ci please smoke test

@swift-ci please test Windows


Documentation for ODrive API

It would be great to have a documentation to the package available at https://pypi.org/project/odrive/. There are some examples throughout the https://docs.odriverobotics.com/ but actually having a list of all packages, functions and classes with one sentence describing each, would be best.

I assume you're referring not to the function/classes of the python package but specifically to the functions and properties exported by the ODrive itself, such as odrv0.axis0.requested_state?
If that's the case then that's definitely desirable and on the radar.

An initial version of a HTML API reference was merged to devel with #424 and will go live on https://docs.odriverobotics.com when firmware v0.5.1 is released.
The source of the documentation is odrive-interface.yaml. Feel free to enhance the documentation in that file.
Here's a preview of what it looks like when compiled to HTML:


Canvas Zoom

I've seen that on issue #5 was asked to add zoom feature of the canvas.
Was it added? I can't find references to it.

No the zoom feature is not added to the package (yet).

I've seen that the issue was opened over an year ago. will it be added soon?

I hope you are happy :P

Thank you very much, you are amazing

I've seen that arrow black dots are not resized as expected

Also, a callback for onScaleUpdate would be useful to manage zoom gesture

Thank you very much, you are amazing

You are welcome :)


Drop Invalid Header - Load balancer attribute

Hi,
Enabled the below annotation for the aws-alb-ingress controller
alb.ingress.kubernetes.io/load-balancer-attributes: routing.http.drop_invalid_header_fields.enabled=false
Getting the error as shown below in the aws-alb-ingress controller logs,
E0227 00:14:44.209725       1 :0] kubebuilder/controller "msg"="Reconciler error" "error"="failed to reconcile attributes of arn:aws:elasticloadbalancing:us-east-1:XXXXXX:loadbalancer/app/XXXXXXXXX/XXXXXXX due to failed parsing attributes; the load balancer attribute routing.http.drop_invalid_header_fields.enabled is not valid"  "controller"="alb-ingress-controller" "request"={"Namespace":"xxx-api","Name":"xxx-ingress"}

Can you please provide details as to how we can use this new annotation to set the load-balancer attribute?
Thanks

What's your ALB Ingress controller image version? If you have built from master then this should work. Otherwise this will not work as the changes for this is not yet released.
This was added as part of https://github.com/kubernetes-sigs/aws-alb-ingress-controller/commit/f83567dfde2694707ebf5b2d09e0c3ef3f2d4fec
But our latest tag 1.1.5 https://github.com/kubernetes-sigs/aws-alb-ingress-controller/pull/1130 was released few days before that commit.

@SaranBalaji90 I used the alb-ingress-controller chart to install/manage the controller.
The chart version is aws-alb-ingress-controller-0.1.10 and APP version is v1.1.2
Do you know how I could get the change from master ? Could I do it via the chart?
https://github.com/helm/charts/tree/master/incubator/aws-alb-ingress-controller

We haven't cut the release yet, so if you want to use this feature then you might have to check out the code, build docker image and push the image to your ecr repo. Will check if its possible through helm charts.

@SaranBalaji90 Thanks for your response. Were you able to check if its possible through helm charts?
Thanks


updated & added missing strings in FR locale

here's a rundown of what i did

filled in every missing instance of msgstr while respecting #2425 wherever possible

i'm not fully aware of modifications made to keep french neutral/inclusive, so i haven't applied to verbs conjugated in passé composé

replaced instances of "Pack de Démarrage" with "Kit de Démarrage", as the use of both of these terms simultaneously might cause confusion
replaced instances of "Like" with "J'aime" or "Mention « J'aime »"

my reasoning is that the government of Québec is infamously strict about its french language charter, and bluesky using "Like" instead of a french equivalent may get bluesky in trouble. i also think that this sounds better in french than "Liké"
i thought of using "cœur", but "user a aimé votre post" is shorter than "user a mis un cœur sur votre post"

replaced instances of "Fil d'actu « Following »" with "Fil des abonnements". i thought referring to it in english wasn't really necessary, and i think "fil des abonnements" makes more sense.

it's possible that some of my translations may be more inclined towards canadian french, as this is the french variant i'm more familiar with.

non-breaking spaces being reverted was a mishap on my end, my workflow was admittedly less than optimal for this and i think copy-pasting the contents straight from my text editor rather than sending the file itself overwrote all of the spaces

Awesome! Thank you for your quick responses. There is just an extraneous dot (.) as the very first character of the file, but beside that, it looks good to me. Thanks again!

LGTM: dear Bluesky team members, please consider this PR reviewed ✅

We can’t add suggestions for non-diff strings, so here are my suggestions for the leftover usage of like spotted by @surfdude29:
 #: src/view/com/post-thread/PostThreadItem.tsx:442
 msgid "{0, plural, one {like} other {likes}}"
-msgstr "{0, plural, one {like} other {likes}}"
+msgstr "{0, plural, one {a aimé} other {ont aimé}}"

Here, we can be more precise:
 #: src/view/screens/Profile.tsx:231
 msgid "Likes"
-msgstr "Likes"
+msgstr "Posts aimés"

And this one is a label, so we can expand it properly:
 #: src/view/com/post-thread/PostThreadItem.tsx:212
 msgid "Likes on this post"
-msgstr "Likes sur ce post"
+msgstr "Mentions « J’aime » sur ce post"

Those suggestions from @Signez all look great to me 👌

Thanks for accepting all the suggestions @CerryTsuki, as far as I'm concerned this LGTM and is ready to merge 🚀

thank you both @Signez and @surfdude29 for feedback and helping me with this! i've only had experience translating games prior, it's interesting to find out how different the process of translating for user experience is from translating a story or dialogue


replace all the imports from tigera/libcalico-go to projectcalico/libcalico-go

[ ] replace all the imports
[ ] replace any dependency in glide files
[ ] replace references in docs

github.com/gunjan5/libcalico-go has moved to github.com/projectcalico/libcalico-go

Not that this is not strictly required since github redirects all the requests to old URL to the new one forever AFAIK

Fixed by #165


Not able to remove or turn off extensions and flagged not from Thorium webstore

System Details

OS: Windows 11 Home
Thorium Version[M117.0.5938.157 - 34th Release]

Problem
Extensions "Chromium PDF Viewer", "Google Hangouts", and Chrome App: "Web Store" are comes Thorium when I installed it and and I cannot remove or turn off any of those extensions. The turn off sliders for these three are greyed out and not clickable.  And clicking remove doesn't do anything. And all three of them have an orange symbol over them, which when I hover says "Not from Thorium Web Store."
Screenshots

Additional Notes
They are turned on by default in incognito, but I can turn that part off. Also, this app's exe file and batch file are blocked from running  in by window's defender, I had to turn it on the install the app.

These are extensions that come with Chromium, Thorium just makes them visible to the outside world.
@ebintobin

These are extensions that come with Chromium, Thorium just makes them visible to the outside world.
@ebintobin

really? I did not know that. But why Google Hangouts though, didn't Google shutdown Hangouts ?

Not all built-in extensions can be turned off.
You can view the discussion about this issue in thorium's repo. You can find it yourself in the issue area.
@ebintobin

Both "Chromium PDF Viewer" and "Google Hangouts" are "Allowed in Ingonito". All are enabled by default and can't disable.

I dont have pdf file. Is like thorium sending our data to someone
I really love this browser and want to give him a chance, but this extenctions quit scary


WIP: Fix Provider produced inconsistent final plan

PR o'clock
Description
compute length of initial lifecycle hooks in dynamic blocks.
Resolves #481
Checklist

[x] terraform fmt and terraform validate both work from the root and examples/* directories
[x] CI tests are passing
[ ] I've added my change to CHANGELOG.md and highlighted any breaking changes
[ ] README.md has been updated after any changes to variables and outputs. See https://github.com/terraform-aws-modules/terraform-aws-eks/#doc-generation

@vranystepan Does this PR resolve your issue ?

@barryib give a me a few minutes, I will verify. Thanks!

Unfortunately I'm getting exactly the same error. But please let me double-check that :)

@vranystepan any news ?

I was experiencing the exact same problem AFAICT. I applied this patch, and it seems to have resolved the issue.

Let's wait for @vranystepan to also confirm.
In the mean time, @barryib would you kindly update the changelog 🙂

@max-rocket-internet This is not working every time as expected. Closing this PR in favor of https://github.com/terraform-aws-modules/terraform-aws-eks/pull/489


[0.12.2 regression]: vars are not supplied in generate_schema_name macro

Issue
Issue description
A PR in 0.12.2 changed the context for the generate_schema_name macro. Whereas previously this macro ran in the context of the model that was being parsed, dbt now supplies a phony context instead.
This PR was intended to ensure that schema generation is handled through the same generate_schema_name macro for all models. Previously, different models (ie. those in packages) would use different macros, leading to confusing and possibly incorrect custom schema names.
As a result of that PR, vars are no longer supplied in the generate_schema_name context. While I think this behavior may be desirable long-term, it is certainly an unintended regression in 0.12.2.
Reproducing
The following macro will fail at parse-time, even if my_var var is configured correctly:
{% macro generate_schema_name(schema_name=none) -%}
  {{ var('my_var') }}
{%- endmacro %}

-- models/my_model.sql

select 1 as id

dbt run

I'll follow up with some further thoughts after poking around some more

I applied both bug and wontfix labels here. This is indeed an unintended breaking change, though I'm unsure how we can support the existing functionality while also making generate_schema_name work in a sane way.
The action item here is to update the documentation for 0.13.0 about the compilation context in generate_schema_name.

I updated the documentation here: https://docs.getdbt.com/v0.13/docs/using-custom-schemas#section-generate_schema_name-compilation-context
Closing this


scrollToTime doesn't work on initial load

Do you want to request a feature or report a bug?
bug
What's the current behavior?
The scrollToTime feature doesn't work when the calendar loads the first time.
In a week view for instance, the time shows 00:00:00 instead of 09:00:00 that was set. However, if the user navigates to the next week, it works as expected.
The applyScroll method below in the TimeGrid.js class is being called to perform the scroll.
applyScroll() {
if (this._scrollRatio) {
const { content } = this.refs
content.scrollTop = content.scrollHeight * this._scrollRatio
// Only do this once
this._scrollRatio = null
}
}
It works fine when called from the componentDidUpdate method but doesn't work when called from componentDidMount.
On debugging the method after it was called from componentDidMount, I noticed that content.scrollTop still retains a value of 0 event after being set.
When I set a timeout as seen below, it works for both cases

What's the expected behavior?
Calendar should scroll to the set time defined with the scrollToTime property

Please re-consider on opening this as a feature.


Add Rating Component

Add Rating Component

Ran Beautify on Other components

@zoef-yt
I have made addressed the comment name mentioned the following closed PR: https://github.com/varun13169/delta-ui/pull/27


refactor(client): credentials observable

Current dependencies on/for this PR:

main

PR #2812   👈

This comment was auto-generated by Graphite.


Remove injest section

Take out the “Ingest” section in “API”. We have global ingest now, so this information is outdated and confusing.

complete with #119


Auditbeat fails to start

Exiting: 1 error: 1 error: failed to create audit client: failed to create audit client: protocol not supported

This error happens when the host kernel has not been compiled with Audit.

https://discuss.elastic.co/t/auditbeat-failed-to-create-audit-client-protocol-not-supported/138601


update docker version to 19.03.2

successfully tested the new docker version on my Jenkins Master/Slave network
first tests show that the argument --gpus is working (nvidia-docker needs to be installed on the node)
I suppose it is enough to install nvidia-docker on the node

Here the error I got with the previous version
java.io.IOException: Failed to run image '<my_image>'. Error: unknown flag: --gpus

See 'docker run --help'.

That would fix #9

Thank you for the contribution!
Approved
Will release it soon.


Chrome support

The Chrome problem

As of version something, Chrome doesn't let frontend extension code make CORS requests (such as the ones needed to get Steam data)
A background script, may be able to make the request, so I could move the request to background and call the background from the front
However, chrome no longer allows new extensions with manifest V2 on their store
Chrome Manifest V3 replaces background scripts with service workers
Firefox Manifest V3 doesn't (at least yet)

So I would need two separate manifests for the browsers, I'll get to it if I get to it someday.

Requires #12


Cancel pending lbryum calls on shutdown

          1 Error

:no_entry_sign:
Please include a CHANGELOG entry.

          1 Message

:book:
See http://keepachangelog.com/en/0.3.0/ for details on good changelog guidelines

  Generated by :no_entry_sign: Danger

lgtm

jack says this is not necessary anymore


xarray.concat gives error with master branch

MCVE Code Sample

import subprocess
import sys
import wget
import glob

def install(package):
    subprocess.check_call([sys.executable, "-m", "pip", "install", package])
try:
    from xclim import ensembles
except:
    install('xclim')
    from xclim import ensembles

outdir = 'tmp'
url = []
url.append('https://github.com/Ouranosinc/xclim/raw/master/tests/testdata/EnsembleStats/BCCAQv2+ANUSPLIN300_ACCESS1-0_historical+rcp45_r1i1p1_1950-2100_tg_mean_YS.nc')
url.append('https://github.com/Ouranosinc/xclim/raw/master/tests/testdata/EnsembleStats/BCCAQv2+ANUSPLIN300_BNU-ESM_historical+rcp45_r1i1p1_1950-2100_tg_mean_YS.nc')
url.append('https://github.com/Ouranosinc/xclim/raw/master/tests/testdata/EnsembleStats/BCCAQv2+ANUSPLIN300_CCSM4_historical+rcp45_r1i1p1_1950-2100_tg_mean_YS.nc')
url.append('https://github.com/Ouranosinc/xclim/raw/master/tests/testdata/EnsembleStats/BCCAQv2+ANUSPLIN300_CCSM4_historical+rcp45_r2i1p1_1950-2100_tg_mean_YS.nc')
for u in url:
    wget.download(u,out=outdir)
datasets = glob.glob(f'{outdir}/*1950*.nc')
ens1 = ensembles.create_ensemble(datasets)
print(ens1)

Expected Output
Following advice of @dcherian (https://github.com/Ouranosinc/xclim/issues/281#issue-508073942) we have started testing builds of xclim against the master branch as well as the current release:
Using xarray 0.14.1 via pip the above code generates a concatenated dataset with new added dimension 'realization'
Problem Description
using xarray@master the xclim.ensembles.create_ensemble call gives the following error:
Traceback (most recent call last):
  File "/home/travis/.PyCharmCE2019.3/config/scratches/scratch_26.py", line 23, in <module>
    ens1 = ensembles.create_ensemble(datasets)
  File "/home/travis/github_xclim/xclim/xclim/ensembles.py", line 83, in create_ensemble
    data = xr.concat(list1, dim=dim)
  File "/home/travis/.conda/envs/xclim_dev/lib/python3.7/site-packages/xarray/core/concat.py", line 135, in concat
    return f(objs, dim, data_vars, coords, compat, positions, fill_value, join)
  File "/home/travis/.conda/envs/xclim_dev/lib/python3.7/site-packages/xarray/core/concat.py", line 439, in _dataarray_concat
    join=join,
  File "/home/travis/.conda/envs/xclim_dev/lib/python3.7/site-packages/xarray/core/concat.py", line 303, in _dataset_concat
    *datasets, join=join, copy=False, exclude=[dim], fill_value=fill_value
  File "/home/travis/.conda/envs/xclim_dev/lib/python3.7/site-packages/xarray/core/alignment.py", line 298, in align
    index = joiner(matching_indexes)
  File "/home/travis/.conda/envs/xclim_dev/lib/python3.7/site-packages/pandas/core/indexes/base.py", line 2385, in __or__
    return self.union(other)
  File "/home/travis/.conda/envs/xclim_dev/lib/python3.7/site-packages/pandas/core/indexes/base.py", line 2517, in union
    return self._union_incompatible_dtypes(other, sort=sort)
  File "/home/travis/.conda/envs/xclim_dev/lib/python3.7/site-packages/pandas/core/indexes/base.py", line 2436, in _union_incompatible_dtypes
    return Index.union(this, other, sort=sort).astype(object, copy=False)
  File "/home/travis/.conda/envs/xclim_dev/lib/python3.7/site-packages/pandas/core/indexes/base.py", line 2517, in union
    return self._union_incompatible_dtypes(other, sort=sort)
....
  File "/home/travis/.conda/envs/xclim_dev/lib/python3.7/site-packages/pandas/core/indexes/base.py", line 498, in __new__
    return DatetimeIndex(subarr, copy=copy, name=name, **kwargs)
  File "/home/travis/.conda/envs/xclim_dev/lib/python3.7/site-packages/pandas/core/indexes/datetimes.py", line 334, in __new__
    int_as_wall_time=True,
  File "/home/travis/.conda/envs/xclim_dev/lib/python3.7/site-packages/pandas/core/arrays/datetimes.py", line 446, in _from_sequence
    int_as_wall_time=int_as_wall_time,
  File "/home/travis/.conda/envs/xclim_dev/lib/python3.7/site-packages/pandas/core/arrays/datetimes.py", line 1854, in sequence_to_dt64ns
    data, copy = maybe_convert_dtype(data, copy)
  File "/home/travis/.conda/envs/xclim_dev/lib/python3.7/site-packages/pandas/core/arrays/datetimes.py", line 2060, in maybe_convert_dtype
    elif is_extension_type(data) and not is_datetime64tz_dtype(data):
  File "/home/travis/.conda/envs/xclim_dev/lib/python3.7/site-packages/pandas/core/dtypes/common.py", line 1734, in is_extension_type
    if is_categorical(arr):
  File "/home/travis/.conda/envs/xclim_dev/lib/python3.7/site-packages/pandas/core/dtypes/common.py", line 387, in is_categorical
    return isinstance(arr, ABCCategorical) or is_categorical_dtype(arr)
  File "/home/travis/.conda/envs/xclim_dev/lib/python3.7/site-packages/pandas/core/dtypes/common.py", line 708, in is_categorical_dtype
    return CategoricalDtype.is_dtype(arr_or_dtype)
  File "/home/travis/.conda/envs/xclim_dev/lib/python3.7/site-packages/pandas/core/dtypes/base.py", line 256, in is_dtype
    if isinstance(dtype, (ABCSeries, ABCIndexClass, ABCDataFrame, np.dtype)):
  File "/home/travis/.conda/envs/xclim_dev/lib/python3.7/site-packages/pandas/core/dtypes/generic.py", line 9, in _check
    return getattr(inst, attr, "_typ") in comp
RecursionError: maximum recursion depth exceeded while calling a Python object

Output of xr.show_versions()

INSTALLED VERSIONS
commit: None
python: 3.7.5 (default, Oct 25 2019, 15:51:11)
[GCC 7.3.0]
python-bits: 64
OS: Linux
OS-release: 4.15.0-74-generic
machine: x86_64
processor: x86_64
byteorder: little
LC_ALL: None
LANG: en_CA.UTF-8
LOCALE: en_CA.UTF-8
libhdf5: 1.10.4
libnetcdf: 4.6.3
xarray: 0.14.1+37.gdb36c5c0
pandas: 0.25.3
numpy: 1.17.4
scipy: 1.3.1
netCDF4: 1.5.3
pydap: None
h5netcdf: 0.7.4
h5py: 2.9.0
Nio: None
zarr: None
cftime: <IP_ADDRESS>
nc_time_axis: None
PseudoNetCDF: None
rasterio: 1.1.1
cfgrib: None
iris: None
bottleneck: 1.3.1
dask: 2.6.0
distributed: 2.6.0
matplotlib: 3.1.1
cartopy: None
seaborn: None
numbagg: None
setuptools: 41.6.0.post20191030
pip: 19.3.1
conda: None
pytest: 5.2.2
IPython: None
sphinx: None

Thanks @tlogan2000.
Can you reduce this example to just a xarray.concat call?

I can reproduce this error with your files:
In [18]: files = glob.glob("*.nc")
    ...: datasets = [xr.open_dataset(file) for file in files]
    ...: xr.concat(datasets, dim="new_dim")
RecursionError

but sorting the files before concatenating results in a different error:
In [19]: files = glob.glob("*.nc")
    ...: datasets = [xr.open_dataset(file) for file in sorted(files)]
    ...: xr.concat(datasets, dim="new_dim")
TypeError: cannot compare cftime.DatetimeNoLeap(1950-01-01 00:00:00) and Timestamp('1950-01-01 00:00:00') (different calendars)

which might mean that there is a problem with the data.
Regardless, we might want to make sure the recursion does not happen.

Ok thanks,
Basically the xclim ensembles code should overwrite a common calendar pd.datetime format to these monthly datasets (various calendar type) before concatenation (as mixing calendars is not possible).   I will try to write it as an xarray only example

I'm guessing decode_times=False will fix that bit.

it does. Also, no errors in either case, so the problem is with DatetimeIndex, CFTimeIndex or the way the data is converted.

This is more or less what I was doing but I think the problem may be that I am trying to overwrite the cfdatetime with the pd.datetime in a loop see code below:
import glob
import xarray as xr
import pandas as pd
# def install(package):
#     subprocess.check_call([sys.executable, "-m", "pip", "install", package])
# try:
#     from xclim import ensembles
# except:
#     install('xclim')
#     from xclim import ensembles

outdir = '/home/travis/Downloads'
url = []
url.append('https://github.com/Ouranosinc/xclim/raw/master/tests/testdata/EnsembleStats/BCCAQv2+ANUSPLIN300_ACCESS1-0_historical+rcp45_r1i1p1_1950-2100_tg_mean_YS.nc')
url.append('https://github.com/Ouranosinc/xclim/raw/master/tests/testdata/EnsembleStats/BCCAQv2+ANUSPLIN300_BNU-ESM_historical+rcp45_r1i1p1_1950-2100_tg_mean_YS.nc')
url.append('https://github.com/Ouranosinc/xclim/raw/master/tests/testdata/EnsembleStats/BCCAQv2+ANUSPLIN300_CCSM4_historical+rcp45_r1i1p1_1950-2100_tg_mean_YS.nc')
url.append('https://github.com/Ouranosinc/xclim/raw/master/tests/testdata/EnsembleStats/BCCAQv2+ANUSPLIN300_CCSM4_historical+rcp45_r2i1p1_1950-2100_tg_mean_YS.nc')
for u in url:
    wget.download(u,out=outdir)
datasets = glob.glob(f'{outdir}/*1950*.nc')

dslist =[]
for d in datasets:
    ds = xr.open_dataset(d, chunks=dict(time=10), decode_times=False)
    ds['time'] = xr.decode_cf(ds).time
    ds["time"].values = pd.to_datetime(
        {
            "year": ds.time.dt.year,
            "month": ds.time.dt.month,
            "day": ds.time.dt.day,
        }
    )
    dslist.append(ds)

ens1 = xr.concat(dslist,dim='realization')

I think I need to leave the ds.time as undecoded and create a calendar variable each time then overwrite the ds values:
import glob
import xarray as xr
import pandas as pd
# def install(package):
#     subprocess.check_call([sys.executable, "-m", "pip", "install", package])
# try:
#     from xclim import ensembles
# except:
#     install('xclim')
#     from xclim import ensembles

outdir = '/home/travis/Downloads'
url = []
url.append('https://github.com/Ouranosinc/xclim/raw/master/tests/testdata/EnsembleStats/BCCAQv2+ANUSPLIN300_ACCESS1-0_historical+rcp45_r1i1p1_1950-2100_tg_mean_YS.nc')
url.append('https://github.com/Ouranosinc/xclim/raw/master/tests/testdata/EnsembleStats/BCCAQv2+ANUSPLIN300_BNU-ESM_historical+rcp45_r1i1p1_1950-2100_tg_mean_YS.nc')
url.append('https://github.com/Ouranosinc/xclim/raw/master/tests/testdata/EnsembleStats/BCCAQv2+ANUSPLIN300_CCSM4_historical+rcp45_r1i1p1_1950-2100_tg_mean_YS.nc')
url.append('https://github.com/Ouranosinc/xclim/raw/master/tests/testdata/EnsembleStats/BCCAQv2+ANUSPLIN300_CCSM4_historical+rcp45_r2i1p1_1950-2100_tg_mean_YS.nc')
for u in url:
    wget.download(u,out=outdir)
datasets = glob.glob(f'{outdir}/*1950*.nc')

dslist =[]
for d in datasets:
    ds = xr.open_dataset(d, chunks=dict(time=10), decode_times=False)
    cal1 = xr.decode_cf(ds).time
    ds["time"].values = pd.to_datetime(
        {
            "year": cal1.time.dt.year,
            "month": cal1.time.dt.month,
            "day": cal1.time.dt.day,
        }
    )
    dslist.append(ds)

ens1 = xr.concat(dslist,dim='realization')

#ens1 = ensembles.create_ensemble(datasets)
print(ens1)

FYI - @dcherian @keewis ... thanks for the suggestions and help  This final small change (dropping time values before replacing with the common calendar) has gotten all cases in the xclim code test suite  running against the<EMAIL_ADDRESS>  Feel free to close
for d in datasets:
    ds = xr.open_dataset(d, chunks=dict(time=10), decode_times=False)
    cal1 = xr.decode_cf(ds).time
    ds = ds.drop_vars('time')
    ds["time"] = pd.to_datetime(
        {
            "year": cal1.time.dt.year,
            "month": cal1.time.dt.month,
            "day": cal1.time.dt.day,
        }
    ).values
    dslist.append(ds)

ens1 = xr.concat(dslist,dim='realization')

#ens1 = ensembles.create_ensemble(datasets)
print(ens1)

@tlogan specifying use_cftime as True or False in the open_dataset call might be useful.
This suggests that the RecursionError in @keews' example is a result of trying to concatenate datasets with mixed DatetimeIndex  & CFTimeIndex indexes.
In [18]: files = glob.glob("*.nc")
    ...: datasets = [xr.open_dataset(file) for file in files]
    ...: xr.concat(datasets, dim="new_dim")
RecursionError


🐛 C3: pages:build script with pnpm scaffolding for Next does not work

Which Cloudflare product(s) does this pertain to?
C3 v.2.0.14
Describe the Bug
I've created a next application via
pnpm create cloudflare

And the resulting package.json does use pnpm for its scripts:

But the pages:build script does not work:

The command should be
pnpm exec next-on-pages

(same for pages:watch)

This is the relevant piece of code that needs updating:
https://github.com/cloudflare/workers-sdk/blob/99baf58b7c35e85c90e1f6df4cea841f31c0a709/packages/create-cloudflare/src/frameworks/next/index.ts#L90-L93

I'm opening this issue for pnpm but yarn (with its different versions) also needs to be tested to make sure that the script works properly with it

(PS: I've been working on this small utility library: package-manager-manager, if we'd like to give it a shot I think it should really help here)

I just explored the above with all possible pms (except yarn berry)

results (showing how things need to change)
npm
Current version
    "pages:build": "npx @cloudflare/next-on-pages@1",
    "pages:deploy": "npm run pages:build && wrangler pages deploy .vercel/output/static",
    "pages:watch": "npx @cloudflare/next-on-pages@1 --watch",
    "pages:dev": "npx wrangler pages dev .vercel/output/static --compatibility-flag=nodejs_compat"

Correct version
    "pages:build": "npx @cloudflare/next-on-pages",
    "pages:deploy": "npm run pages:build && wrangler pages deploy .vercel/output/static",
    "pages:watch": "npx @cloudflare/next-on-pages --watch",
    "pages:dev": "npx wrangler pages dev .vercel/output/static --compatibility-flag=nodejs_compat"

Notes

with @1, npx asks you to install next-on-pages

pnpm
Current version
    "pages:build": "pnpm dlx @cloudflare/next-on-pages@1",
    "pages:deploy": "pnpm run pages:build && wrangler pages deploy .vercel/output/static",
    "pages:watch": "pnpm @cloudflare/next-on-pages@1 --watch",
    "pages:dev": "pnpm wrangler pages dev .vercel/output/static --compatibility-flag=nodejs_compat"

Correct version
    "pages:build": "pnpm next-on-pages",
    "pages:deploy": "pnpm pages:build && wrangler pages deploy .vercel/output/static",
    "pages:watch": "pnpm next-on-pages --watch",
    "pages:dev": "pnpm wrangler pages dev .vercel/output/static --compatibility-flag=nodejs_compat"

Notes

pnpm @cloudflare/next-on-pages does not work, pnpm wants you to remove the @cloudflare/ scope
also @1 needs to be removed
minor: in pnpm run pages:build, run is unnecessary
opposite what I thought, in regards to -- the scripts here are the same as npm, so there isn't anything to change regarding that

yarn
Current version
    "pages:build": "yarn @cloudflare/next-on-pages@1",
    "pages:deploy": "yarn run pages:build && wrangler pages deploy .vercel/output/static",
    "pages:watch": "yarn @cloudflare/next-on-pages@1 --watch",
    "pages:dev": "yarn wrangler pages dev .vercel/output/static --compatibility-flag=nodejs_compat"

Correct version
    "pages:build": "yarn next-on-pages",
    "pages:deploy": "yarn pages:build && wrangler pages deploy .vercel/output/static",
    "pages:watch": "yarn @cloudflare/next-on-pages@1 --watch",
    "pages:dev": "yarn wrangler pages dev .vercel/output/static --compatibility-flag=nodejs_compat"

Notes

yarn is basically identical to pnpm (but with yarn instead of pnpm)
just tested on yarn classic

bun
Current version
    "pages:build": "bunx @cloudflare/next-on-pages",
    "pages:deploy": "bun run pages:build && wrangler pages deploy .vercel/output/static",
    "pages:watch": "bunx @cloudflare/next-on-pages@1 --watch",
    "pages:dev": "bunx wrangler pages dev .vercel/output/static --compatibility-flag=nodejs_compat"

Correct version
    "pages:build": "bunx @cloudflare/next-on-pages",
    "pages:deploy": "bun pages:build && wrangler pages deploy .vercel/output/static",
    "pages:watch": "bunx @cloudflare/next-on-pages --watch",
    "pages:dev": "bunx wrangler pages dev .vercel/output/static --compatibility-flag=nodejs_compat"

Notes

basically identical to npm (except that npm and npx become respectively bun and bunx), with the exception that run is optional (but it's not mandatory to omit)

it looks like what's needed is to have different set of scripts based on 2 conditions:

if pm is npm or bun: npm/bun version (which are the same, except for run which we might leave in)
if pm is yarn or pnpm: yarn/pnpm version (which are the same)

(PS: for this use case using package-manager-manager doesn't seem strictly necessary, it's probably better to just fix this now and consider later if pmm can bring something to the table)


Error in arch container build

Hi, today when run the github action I get the following error:
Step 3/7 : RUN pacman -S --noconfirm --needed --overwrite '*'       openssh sudo       git fakeroot binutils gcc awk binutils xz       libarchive bzip2 coreutils file findutils       gettext grep gzip sed ncurses util-linux
   ---> Running in e7f53f4dd7e9
  error: failed to initialize alpm library
  (could not find or read directory: /var/lib/pacman/)
  The command '/bin/sh -c pacman -S --noconfirm --needed --overwrite '*'       openssh sudo       git fakeroot binutils gcc awk binutils xz       libarchive bzip2 coreutils file findutils       gettext grep gzip sed ncurses util-linux' returned a non-zero code: 255

I found this https://www.reddit.com/r/archlinux/comments/lek2ba/arch_linux_on_docker_ci_could_not_find_or_read/gmg4foj?utm_source=share&utm_medium=web2x&context=3 maybe help.

That reddit account (kredditacc96) is mine.

Can you try KSXGitHub/github-actions-deploy-aur@2b89cb6b44dbf7bd06916a1a2fe411357dfff236 and tell me the result?

Hi,
Having the same issue and tested your new image, now having:
Generating PKGBUILD and .SRCINFO
  Copying PKGBUILD...
  '/PKGBUILD' -> './PKGBUILD'
  Updating .SRCINFO
  ==> ERROR: /etc/makepkg.conf not found.
      Aborting...

Any idea?
Thanks

@deimosfr Can you try 72b5fe2a413d8f824fc12a2c5e4abba7229cd469?

Not better :(
Run KSXGitHub/github-actions-deploy-aur@72b5fe2a413d8f824fc12a2c5e4abba7229cd469
...
Generating PKGBUILD and .SRCINFO
  Copying PKGBUILD...
  '/PKGBUILD' -> './PKGBUILD'
  Updating .SRCINFO
  ==> ERROR: /etc/makepkg.conf not found.
      Aborting...

Then I have no idea why it happens. If /etc/makepkg.conf does not exist, then the error should occur at chmod commands in /entrypoint.sh, not in /build.sh.
I will probably try invoking docker command directly at a later time.

@KSXGitHub I've added a comment to your PR that might resolve the issue. I'm also experiencing the same currently with your GitHub Action.

I have patched glic-2.33 according to suggestion from this reddit comment. Can you try ef5cc6ec3fbd557ee95def420b2b422baeccbe6a?

Still the same error:
Run KSXGitHub/github-actions-deploy-aur@ef5cc6ec3fbd557ee95def420b2b422baeccbe6a
...
Creating builder user
Initializing ssh directory
Copying PKGBUILD
Making sure that makepkg.conf is readable
Adding aur.archlinux.org to known hosts
Importing private key
Checksums of SSH keys
Configuring git
Cloning AUR package into /tmp/local-repo
Generating PKGBUILD and .SRCINFO
  Copying PKGBUILD...
  '/PKGBUILD' -> './PKGBUILD'
  Updating .SRCINFO
  ==> ERROR: /etc/makepkg.conf not found.
      Aborting...

I have forked the content of this repository, and rebuilt it using alpine instead of archlinux. In case you're interested in the information, please see jbouter/aur-releaser. It's a drop-in replacement for the current Workflow in case you wish to use it.
@KSXGitHub Feel free to use my work inside this repository. I have however released my custom additions under the GPL, rather than MIT license.

We're also seeing the same issue on superfly/flyctl:
using 2.2.3
using ef5cc6ec3fbd557ee95def420b2b422baeccbe6a
Let me know if I can help debug this.

It seems GitHub has fixed Arch Linux related problems for us. Can you guys try again (with the latest tag this time)?

Hi,
I confirm with tag v2.2.3 it works \o/
Thanks for your time

If others confirm it as well I will close this issue.

I also confirmed! Thanks


handle upload dup error

@icattlecoder Can you explain this more? I'm interested, but I'm not familiar with the problem it addresses, so I'd like to better understand the motivation.
Thanks,
Mike


converter: firmware: check volume type

At the moment, for ACPI Slic table, we have defined that only Secrets should be used. Add a check to validate it.
What this PR does
Before this PR:
We would not properly error if User tried a unsupported Volume type with SLIC table API
After this PR:
We only allow Secrets to be used, failing early.

Related to: CNV-44417
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

Better handle unsupported volume type with Slic table

@victortoso wondering if we should add a check in the admission webhook to validate this earlier. In any case, I would also leave this check here.

Can we also add validation at API level as this is too late for user.

@xpivarc & @alicefr, I've included the webhook validation plus tests. Thanks for the quick review earlier!

/test pull-kubevirt-build
/test pull-kubevirt-fuzz

Rebased. I've addressed @xpivarc review and also added Context's Architecture field in converter_test.go.
Cheers,


name change?

Firing up my old scripts for a new season -- did this used to be called ff_espn_api?

Yes it was updated over the offseason! New import syntax and pip package

Nice! I was stumped at why my old version wouldn't update. Glad the ESPN didn't break private leagues! I've already used this to do some graphical draft recaps.

I'm glad everything is working for you!


Validate 50 projects manually

I'd like to have more confidence that we're generating accurate results. To do this, I'd like to manually verify 50 randomly sampled projects to ensure that we agree with the tool output -- meaning, that we think it'd be reasonable to go with the top option as the first choice.
If anyone would like to work on this, please just comment below with the package that you've checked and whether or not it was correct. If it wasn't correct, please open an issue so we can improve the tool.

Package URL
Status

pkg:github/ossf/alpha-omega
Bug #14, fixed

Ecosystem
Name
URL
Correct Detection?

github
ckeditor4
https://github.com/ckeditor/ckeditor4
Yes

rubygems
rack
https://rubygems.org/gems/rack
Yes

npm
babel-helper-regex
https://www.npmjs.com/package/babel-helper-regex
Yes

github
pytest-mock
https://github.com/pytest-dev/pytest-mock
Yes

debian
libtie-ixhash-perl
https://packages.debian.org/search?keywords=libtie-ixhash-perl

npm
path-browserify

Yes

github
sqlx
https://github.com/launchbadge/sqlx
Yes

github
abp
https://github.com/abpframework/abp
Yes

github

https://github.com/matthiaskramm/swftools

github
rails_event_store
https://github.com/RailsEventStore/rails_event_store
Yes

npm
underscore

Yes

github
ros
https://github.com/ros/ros

npm
node-forge

Yes

npm
faker

Yes

npm
mime-db

Yes

github
rubygems.org
https://github.com/rubygems/rubygems.org

github
core-foundation-rs
https://github.com/servo/core-foundation-rs

github
auto
https://github.com/google/auto
Yes

github
learnxinyminutes-docs
https://github.com/adambard/learnxinyminutes-docs

debian
libgnutls30
https://packages.debian.org/search?keywords=libgnutls30

github
ecto
https://github.com/elixir-ecto/ecto
Yes

github
pry
https://github.com/pry/pry
Yes

debian
libsoup-gnome2.4-1
https://packages.debian.org/search?keywords=libsoup-gnome2.4-1
Yes

github
Embed
https://github.com/oscarotero/Embed
Yes

debian
libdatrie1
https://packages.debian.org/search?keywords=libdatrie1
Yes

go
github.com/grpc-ecosystem/go-grpc-middleware

github
crate
https://github.com/crate/crate
Yes

github
twine
https://github.com/pypa/twine

github
routing
https://github.com/symfony/routing
Yes

maven
commons-cli:commons-cli

github
android
https://github.com/nextcloud/android

github
ansible
https://github.com/ansible/ansible
Yes

github
rack-cors
https://github.com/cyu/rack-cors
Yes

github
minimist
http://github.com/substack/minimist

nuget
system.valuetuple

nuget
microsoft.netcore.targets.dnxcore

github
cpputest
https://github.com/cpputest/cpputest

npm
cors

Yes

github
joblib
https://github.com/joblib/joblib

github
graphql-java
https://github.com/graphql-java/graphql-java

github
immer
https://github.com/immerjs/immer

debian
libglu1-mesa
https://packages.debian.org/search?keywords=libglu1-mesa

github
image
https://github.com/containers/image
Yes

github
pyright
https://github.com/microsoft/pyright

npm
commondir

Yes

debian
libopencore-amrnb0
https://packages.debian.org/search?keywords=libopencore-amrnb0
Yes

github
make
https://github.com/mirror/make
Yes

github
validator
https://github.com/symfony/validator

github
auspice
https://github.com/nextstrain/auspice

npm
postcss-value-parser

Yes

Fix github/ros/ros via 9aad226f


vm/dart_2/invisible_function_pragma_test fails on Windows precomp product

The windows precompiled product bot was baselined from the windows precompiled release bot (CL changing the bots).
cc @rmacnak-google
exit code:
255

stdout:
RegExps for expected stack:
"^#0      main.<anonymous closure>"
"^#1      main"
"#@ IGNORE_REMAINING_STACK #@"

Actual stack:
#0      main.<anonymous closure> (file:///C:/b/s/w/ir/runtime/tests/vm/dart_2/invisible_function_pragma_test.dart:27)
#1      visible (file:///C:/b/s/w/ir/runtime/tests/vm/dart_2/invisible_function_pragma_test.dart:71)
#2      main (file:///C:/b/s/w/ir/runtime/tests/vm/dart_2/invisible_function_pragma_test.dart:35)
<asynchronous suspension>

Expected line 2 to be `^#1      main` but was `#1      visible (file:///C:/b/s/w/ir/runtime/tests/vm/dart_2/invisible_function_pragma_test.dart:71)`

stderr:
Unhandled exception:
Expect.isTrue(false) fails.
#0      Expect._fail (package:expect/expect.dart:742)
#1      Expect.isTrue (package:expect/expect.dart:141)
#2      assertStack (file:///C:/b/s/w/ir/runtime/tests/vm/dart_2/causal_stacks/utils.dart:249)
<asynchronous suspension>
#3      main (file:///C:/b/s/w/ir/runtime/tests/vm/dart_2/invisible_function_pragma_test.dart:36)
<asynchronous suspension>

--- Re-run this test:
python3 tools/test.py -n dartkp-win-product-x64 vm/dart_2/invisible_function_pragma_test

full log
The test is currently failing on:

Closing in favor of https://github.com/dart-lang/sdk/issues/51468


React UI: Implement missing TSDB head stats section

This PR implements the missing TSDB head stats section in the React UI.
It exposes the following fields in the /api/v1/status/tsdb to make them available in the UI:

numSeries
chunkCount
minTime
maxTime

It provides functionality comparable to that of  #7544 (the string formatting is slightly different).

Closes #7546

Hey @juliusv I'd appreciate a review whenever you get a chance. Thanks!

Awesome! Thanks for the review! I will address these things in the next couple of days.

@juliusv I think I was able to address all of your comments. Please let me know if there's anything else I should update. Thanks!

:+1: Looks good now, thanks again :)

Great! Thanks for the thorough review!


Remove CallerIDPolicy from TOC

OPS Build status updates of commit 65c408b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/skype.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


chore: Upgrade to Relay 13

The type of this PR is: chore

Description
Upgrade to Relay 13.
PR Checklist (tick all before merging)

[ ] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[ ] I have tested my changes on iOS and Android.
[ ] I have added tests/stories for my changes, or my changes don't require testing/stories, or I have included a link to a separate Jira ticket covering the tests.
[ ] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[ ] I have documented any follow-up work that this PR will require, or it does not require any.
[ ] I have added an app state migration, or my changes do not require one. (What are migrations?)
[ ] I have added a changelog entry below or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Warnings

:warning:

❌ An error occurred while validating your changelog, please make sure you provided a valid changelog.

  Generated by :no_entry_sign: dangerJS against cbc66da83dee516b6420e37d99acca985e91879c

im guessing we will close this and recreate it after https://github.com/artsy/eigen/pull/6254?

Closing PR for inactivity - please feel free to reopen it if needed 👌

Exciting!!!


Tags in modals. Dropdown problem

I'm submitting a ...  (check one with "x")
[ ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[x ] support request/question

Current behavior

I set [showDropdownIfEmpty] to true. I focus the tag component, autocomplete dropdown appears. I click somewhere else, the dropdown is still displayed. Even i close the modal (hide it), the dropdown is still there.
How would i go about hiding this dropdown ?
I have figured out a way to tell if the user clicked anywhere else except the component itself, but i can't seem to be able to find a way to hide the dropdown through an event or something. ( i was able to hide it by setting "display" to "none", but that's not a solution since after i focus the component the next time, it considers as it was already open and closes it,  resulting in nothing happening for the user )

I see the issue. Can you try setting [appendToBody]=false? Check out the doc

Thank, this solved the issue.

@Gbuomprisco
Do you have property load-on-down-arrow like ng tag input to show the drop down on hitting down arrow?

Hi @omprakash9,
no there is not (it would be in the readme for sure if it were :)

Hi @Gbuomprisco
Can you try to implement that property in ng2-tag-input under V1.0.0,
If yes can you please provide me workaround on it?

@omprakash9 if you maually register an event on the input and then call the dropdown API by referencing a variable (say #tagInput), you may achieve what you need.

okay thanks @Gbuomprisco


WinUI 3 Preview 4 ContentDialog exception.

Describe the bug
The following code works in UWP, but generates an exception in WinUI 3 Preview 4:
                    var dialog = new ContentDialog
                    {
                        Title = "Notice",
                        Content = "Navigate to a page before selecting settings.",
                        CloseButtonText = "Ok",
                    };

                    // MP! why: System.ArgumentException : Value does not fall within the expected range."
                    ContentDialogResult result = await dialog.ShowAsync();

Steps to reproduce the bug
Steps to reproduce the behavior:

Create a solution with the above snippet of code.

Expected behavior
The code should work (not generate a System.ArgumentException)
Screenshots
n/a
Version Info
NuGet package version:
[Microsoft.WinUI 3.0.0-preview4.210210.4]

Windows app type:

UWP
Win32

No
Yes

Windows 10 version
Saw the problem?

October 2020 Update (19042)
Yes

Device form factor
Saw the problem?

Desktop
Yes

Additional context
n/a

Digging through the docs, I noticed that for WinUI's ContentDialog, you have to set the XamlRoot property before displaying the dialog.  This constitutes a breaking change compared to UWP's ContentDialog as it has no such requirement when instantiated through code.
This requirement complicates MVVM usage and will make porting certain UWP code more tedious.
If I'm hoisting up a Dialog from an MVVM ViewModel, how do I make sure it's attached to a right window in the right state?  A critical system message dialog may need to be app modal and topmost so I can be sure the user sees it.  It can't depend on a window that might have gone away or may be minimized.

ContentDialog will get the xaml root set automatically if you parent it to a page, like would be the case if you include it in your xaml file. So the simplest solution would be to put the content dialog in the same xaml file as the stuff you want it to display over. This is only an issue for content dialogs you make from code. It isn't an issue for UWP apps because there can only be one xaml root for UWP apps, but fore desktop apps you can have multiple.
Duplicate of: https://github.com/microsoft/microsoft-ui-xaml/issues/4251

@StephenLPeters , agreed, except that parenting isn't necessary in UWP.  I'm not sure how UWP handles this, presumably through the AppModel's core window?
The behavior should be the same in both UWP and WinUI.  It would be unfortunate to require lots of compile time checks to select different code paths.  The goal should be to minimize friction from UWP to WinUI.  Some things are looking very good that way.  Would be nice to have a mostly seamless transition.  Little details add up.

I disagree with the closure of this issue, since this is a breaking change that complicates porting UWP code to WinUI.

In UWP there is alway only one xaml root, so the system is able to infer that the singleton is the one it should use.  You can set the XamlRoot in UWP it wont hurt, so you don't need a compile time check, you could just always set it.
I closed this issue because it is a dupe of #4251 and we like to have only one open issue per actual issue.

As this sample demonstrates: https://github.com/Noemata/SimpleMVVM
It's quite easy to "port" a UWP app over to WinUI.  It's also relatively easy to have common code between the two.  Unfortunately, the little differences will add up.  Why add to the friction?
@StephenLPeters , using your logic, I could make an equally valid argument for the WinUI framework setting XamlRoot so that it defaults to the handle of the launching window.
So my real point is about eliminating the friction between UWP and WinUI.
If there were a compile time switch for namspaces so I could do something similar to "using x=y" but without changing code, I could then easily move lots of code over to WinUI.  Yes, it is fairly easy to have common code.  Why not make it even easier?

In winui desktop a single launching window can have as many xaml roots as you want. So in Winui desktop we can't divine the proper xaml root from the launching window.
I don't really understand the compile time switch recommendation. the types being used in UWP and Desktop are the same, there are just slightly different behaviors because of fundamental app model differences.

@StephenLPeters , I surrender.  You guys win as per usual, though the losers will also be the corporate customers I support when I tell them porting their large UWP projects won't be so easy.
Here's what I want to avoid, among the many other details:
#if WINDOWS_UWP
using Windows.UI.Xaml;
using Windows.UI.Xaml.Data;
using Windows.UI.Xaml.Controls;
#else
using Microsoft.UI.Xaml;
using Microsoft.UI.Xaml.Data;
using Microsoft.UI.Xaml.Controls;
#endif

I suggest you try and seamlessly port this: https://github.com/Alvaromah/eShopOnUWP to WinUI, and see how that works out for you.  It's Microsoft's own creation, and it's full of bits that require lots of tweaking.

It seems like my answers to your questions are frustrating you.  I'm sorry if my tone has come across as dismissive, that was not my intention.  The differences between the desktop and uwp application models are complicated and lead to complicated issues, this being one of them.  We do strive for the experience of upgrading or porting an app to Winui 3 to be as seamless as possible, feedback about the pain points in this space is extremely valuable and we really do appreciate your help identifying the issues we have with the product. My responses are simply trying to explain why things are the way they are today, I was not trying to justify them as good or correct. Recognize that winui3 is still very much in a preview state, we have a number of issues like this and definitely need to figure out the best way to resolve them.  One idea for this particular scenario would be that if they system detect that there is only one xaml root in your app, to default the xaml root property of all elements to that.  I don't think that is something that has been considered.

@StephenLPeters , your suggestion "if the system detects that there is only one xaml root in your app, to default the xaml root property of all elements to that", is the sort of compromise that would work in many cases.
I do appreciate that it's not possible to have a one size fits all approach with WinUI.  I'm just looking to minimize the grief involved in transitioning from UWP to WinUI, since this will be the path of least resistance toward WinUI adoption.
I do recommend that you try to port this code over to WinUI to get a feel for what's involved: https://github.com/dotnet-architecture/eShopOnUWP
I picked this particular example since it is representative of typical corporate apps, warts and all.  It took me 4 days to get it working with WinUI (trying to work as quickly as possible).  The XamlRoot issue was minor.  My approach there would normally be to adjust the original source as you had suggested.  That said, the pain points accumulate.  This one seemed to have a reasonable "default" solution as you've suggested.
The namespace change makes maintaining two sets of mostly similar code a drag and error prone.  Getting rid of this one pain point would go a long way toward easing the transition to WinUI.  Given WinUI is so very close to UWP and quite accessible to anyone familiar with UWP, shortening the gap will only accelerate adoption of WinUI.
One other key point I'd like to make ... I'm baffled that WinUI on UWP isn't getting more priority.  I would have gotten that over the finish line first since it would accelerate the prospect of getting a large number of UWP apps onto WinUI because the first part of the transition work could be done with less friction.  UWP devs could keep there WinUI store app as is, and look forward to extending capabilities for a desktop deployment.  Microsoft would gain valuable input on the initial migration process while ensuring the creation of a healthy eco system of apps for WinUI desktop when it was finished.
The current desktop centric approach for WinUI will tend alienate both UWP devs and WPF devs, the two most likely early adopters.  My two cents worth.
As for first impressions; Preview 4 did surprise me.  Most things just work!  Much better than Preview 3.  With some strategic choices made to facilitate ease of transition from UWP and the addition of missing LOB capabilities, WinUI could start to get some serious attention.

One cool way to sort out the namespace problem would be to add a mechanism that is available at the project level.  So within my WinUI version of the project, I draw from the same sources, thus at the source code level there are zero changes, but within the build parameters of the project, I set a namespace mapping that acts as an override for what is in the source code.  This facility would be useful beyond just supporting WinUI migration for C# work.  Something along the lines of:
...
    <ApplicationManifest>app.manifest</ApplicationManifest>
    <Platforms>x86;x64;arm64</Platforms>
    <RuntimeIdentifiers>win10-x86;win10-x64;win10-arm64</RuntimeIdentifiers>
...
    <NameSpaceOverrides>
	Windows.UI.Composition = Microsoft.UI.Composition
	Windows.UI.Xaml.Navigation = Microsoft.UI.Xaml.Navigation
    </NameSpaceOverrides>


FitToWidth does not take focus in Excel Page Setup dialog box when used

Description

Not sure if this is a bug, but would love to have the 'Fit to:' scaling option fall into focus when specifying Fit To Scaling options.  The documentation seems to suggest it should be.
See: https://github.com/qax-os/excelize/blob/master/xmlWorksheet.go#L999-L1006
Steps to reproduce the issue:

Use code similar to that shown below
Write Excel file
Open the file with Excel
Navigate to Page Layout -> Page Setup -> Page
'Adjust to:' radion button is the selected choice, was hoping to see 'Fit to:' as the active selection

f := excelize.NewFile()
var (
    size                 = 1
    orientation          = "landscape"
    firstPageNumber uint = 1
    fitToHeight          = 2
    fitToWidth           = 2
    blackAndWhite        = false
)
if err := f.SetPageLayout("Sheet1", &excelize.PageLayoutOptions{
    Size:            &size,
    Orientation:     &orientation,
    FirstPageNumber: &firstPageNumber,
    FitToHeight:     &fitToHeight,
    FitToWidth:      &fitToWidth,
    BlackAndWhite:   &blackAndWhite,
}); err != nil {
    fmt.Println(err)
}

Describe the results you received:

Describe the results you expected:
Was hoping to see the 'Fit to:' radio button selected.
Output of go version:
go version go1.20.7 linux/amd64

Excelize version or commit ID:
	github.com/xuri/excelize/v2 v2.7.1

Environment details (OS, Microsoft Excel™ version, physical, etc.):
WSL2 under Windows, Ubuntu 22.04

Thanks for your issue. Please also set the sheet property to enable fit-to-page settings:
f := excelize.NewFile()
var (
    size                 = 1
    orientation          = "landscape"
    firstPageNumber uint = 1
    fitToHeight          = 2
    fitToWidth           = 2
    blackAndWhite        = false
+   enable               = true
)
+if err := f.SetSheetProps("Sheet1", &excelize.SheetPropsOptions{
+    FitToPage: &enable,
+ }); err != nil {
+   fmt.Println(err)
+   return
+}
if err := f.SetPageLayout("Sheet1", &excelize.PageLayoutOptions{
    Size:            &size,
    Orientation:     &orientation,
    FirstPageNumber: &firstPageNumber,
    FitToHeight:     &fitToHeight,
    FitToWidth:      &fitToWidth,
    BlackAndWhite:   &blackAndWhite,
}); err != nil {
    fmt.Println(err)
}

I've closed this, if you have any question, please let me know, and reopen this anytime.


Web - Login - No light green logo

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Issue found when executing PR https://github.com/Expensify/App/pull/16932
Action Performed:

Go to URL https://staging.new.expensify.com/
Verify that the light green logo present

Expected Result:
The light green logo present
Actual Result:
No light green logo
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] Web / Chrome
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/231863926-dc46f0aa-6e67-4af4-a981-72c1e8829899.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

Triggered auto assignment to @alexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

I ran out of time, I'll review on Monday.

Not overdue

Yep this is intended, from the PR:

Web

Open the App
Verify that the splash screen had a dark green background, light green logo, and fades away.

@kbecciv do you have any testrail for the bootsplash?

@mountiny No TestRail for this issue


update more info link

Updated the "more information" link from ".../getting-started/scopes/" (redirected to different page) to the most recent URI, appending anchor so page opens at section. Done to save anyone pasting the link from the stdout into the browser time.

I put a task on my to-do list to update all of the rest of the documentation links.

I also have a fix for the failing git build action that I'll check-in with my next PR.


Now able to build curl with openssl for UWP

With this change we are once again able to build curl with OpenSSL support for UWP.

/azp run

@johanlindfors Sorry, I mean modify this file instead of modify curl's CONTROL file.

Well, I found this issue has been fixed in another PR.

Fixed in other PR


[Feature] Selection Algorithm for Merge Operation

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
dependent #11472
This issue proposes an algorithm for selecting eligible parts for the tiered merge operation. The algorithm is based on sorting parts by their minimum timestamp and size, and it focuses on merging only adjacent parts to optimize the merging process and minimize I/O operations.
The algorithm does not consider data deletion as a factor in the selection process, as Time-To-Live (TTL) is assumed to handle data expiry and deletion effectively.

Timestamp-Based Sorting: The algorithm should sort the parts based on their minimum timestamp, ensuring chronological order.
Size-Based Sorting: Along with the timestamp, the size of the parts should also be a factor in sorting and selection. Smaller parts will be prioritized for merging to larger ones.
Adjacent Merging: The algorithm will merge only adjacent parts, maintaining the order and minimizing unnecessary I/O operations.

Use case
No response
Related issues
No response
Are you willing to submit a pull request to implement this on your own?

[ ] Yes I am willing to submit a pull request on my own!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Plaese assign to me.

Fixed by https://github.com/apache/skywalking-banyandb/pull/371


Update TCPListener example code to one that compiles.

It fell behind the actual working code. It would be nice if we could
figure out a way to be able to extract and compile examples from
documentation during CI so we could catch these things.

Thanks to @autodidaddict for finding this.

d'oh. i should have [skip ci]'d that

It might be taboo to mention it here, but one of my favorite features of Rust is the fact that the test runner will scan your code docs and execute them. This can guarantee that the docs never fall behind the code.

@autodidaddict - It's definitely not taboo to mention here. We have a lot of respect for the accomplishments of the Rust community, and have a very genial attitude toward them.
With regard to that particular feature, it's definitely one I'd love to explore, though it would probably be easier implemented after having the pony-in-pony compiler far enough along for a tool to use the API it exposes to extract the examples from the docstrings and compile them.

Totally in favor of that.


Ability to do CSS optimization without minification

I'm looking to use clean-css to clean up some nasty CSS files, but I don't wish to minify the output. I just want to use it to scrub messy CSS into clean, human-readable CSS for some code I'm working on.
I saw that you introduced O0, but if I understand, it only bundles together the existing CSS. If you provided a way to output human readable CSS in addition to minification, it would open clean-css up to a wide new use case. Would it be difficult to do this?

You should be able to do it using { format: 'keep-breaks', level: 0 } options or alternatively use beautify format option.
I noticed we missed that info in docs so I've added it: https://github.com/jakubpawlowicz/clean-css#formatting-options

That's perfect, exactly what I was looking for. Thank you!

Cheers 👍


Export full image or PDF

I want export full image or PDF without scaling it.

Other than this, other exporting options aren't available
https://github.com/bumbeishvili/org-chart/tree/dev


PolyChord live point reading

Description
Anesthetic now reads PolyChord live points, and discards any duplicates if the run is finished.
Checklist:

[x] I have performed a self-review of my own code
[x] My code is PEP8 compliant (flake8 anesthetic tests)
[x] My code contains compliant docstrings (pydocstyle --convention=numpy anesthetic)
[x] New and existing unit tests pass locally with my changes (python -m pytest)
[x] I have added tests that prove my fix is effective or that my feature works

Many thanks @Pablo-Lemos


DistributedDataParallel device_ids and output_device arguments only work with single-device CUDA modules

Hi, I encountered a problem with your code:
AssertionError: DistributedDataParallel device_ids and output_device arguments only work
with single-device CUDA modules, but got device_ids [0], output_device 0, and
module parameters {device(type='cuda', index=0), device(type='cpu')}.

But if I commented
if self.config['trainer']['sync_batch_norm']:
    self.model = torch.nn.SyncBatchNorm.convert_sync_batchnorm(self.model)

of your trainer.py, the code runs without errors. I used the recommended settings.
May I ask why?

SyncBatchNorm is only working under the condition of one GPU per-process mode according to requirements of official Pytorch. In other words, the nproc_per_node and local_world_size  args must be the same in train command args.
So the reasons for the error are that you turn on sync_batch_norm arg as true in config.json but the nproc_per_node and local_world_size  args is different when you run commends. Please check again.

Hi @wenwenyu , thanks a lot for your kind reply. I did set the number of nproc_per_node and local_world_size  to be the same. However, I found no usage of nproc_per_node from python files. May I ask where does the code use nproc_per_node please?

Try to set the number of CUDA_VISIBLE_DEVICES  as same as nproc_per_node.

I am going to close this issue. Please feel free to reopen or create a new one if you have more questions.


M4 launch wrap update

This issue serves as placeholder and discussion point for general wrap for the M4 milestone. It should be the last ticket closed for the milestone, and have attached in comment the final build. Any specific problems found in the build should be taken up in the feature request issue it pertains to, otherwise general comments can be made here. The milestone is only complete when @Slimmy82 closes this issue.

There are so many things stuffed into this last milestone that directly effect user interface and experience that I'm releasing it early so we can ensure everything gets TESTED. Lots and lots of testing is needed for this release. I've already had my kids give it a go and they've found some bugs. Specific to this release 0.9.0 > PancakeCreator_m4_0.9.0MAC | PancakeCreator_m4_0.9.0WIN:

#14, #15 for file input/output and current file management with edit detection and warning dialogs on new, close, open, etc.
#16 for image import! This is giant but is meant to feel like a "silent" addition. The transparency amount is likely up for debate, but everything else works pretty well as expected.
#13 & #25 are still open and need to be managed in 0.9.1 or later before 1.0 release. Shims have been put in, but real discussion is needed before this is finalized and has been tested with a real PancakeBot.

This early release is really about UI testing and verification. Everything in it should work (apart from the color separation work), so if anything at all acts funky, now is the time to call it out.

Great, I will download and play around with it. I will also get a few people to test and play with it.

OK, after a few more weeks of work, I've implemented the very first required parts for fill creation and rendering.  Specific to this release 0.9.5 >  PancakeCreator_0.9.0MAC | PancakeCreator_0.9.5WIN:

#28 - Horizontal mirroring of GCODE by default, with an additional menu item for non-mirrored output
#31 - Full design implemented
#29 & #30 - Paint bucket style fill and GCODE rendering of filled areas. This is huge and likely because of complexity will have some bugs. Needs to be tested, tested, tested!

I've done some general tweaks to fill for #33, fixed a GCODE render issue with very small line lengths (Which may or may not help as we're turning the pump on and off fairly quickly), at least every path should turn the pump off afterwards.
PancakeCreator_0.9.6MAC

All previous version have been invalidated/removed, this is now the final Release Candidate. Once this gets proofed & tested, I'll initiate it as a full release on the main page. PancakePainterMAC-v1.0.0-RC1
Public change list (from original email):

Griddle dimensions now perfectly match the bot understood GCODE units (half mms), and preview perfectly matches the presto griddle.
Name Changed, Logo Changed & Icon Changed.
Settings window: Lists all the tweakable settings for gcode rendering. Saves immediately, resettable.
Fill output improved, added wait cursor for long fills, fixed "can't fill this thing" problem, and added an error catch to it. This was also killing some saved files from being re-opened, so double win.
Drawing is now left mouse only, allows for right mouse click end polygonal path. Double click is somewhat broken as the first click goes to the red dotted, then the second click goes to the new path. Double clicking on the path you just made will end it though.
All file warning dialogs are now native, with explanatory button text
Export for print has a nice "please wait" window now, for complicated exports
Logo now fits on the screen under a certain width
Added version number next to the logo, and GCODE notes when it was made by what version, and with what settings (good for tech support)

All previous version have been invalidated/removed, this is now the final Release Candidate. Once this gets proofed, I'll initiate it as a full release on the main page. PancakePainterMAC-v1.0.0-RC2
Change list:

96405ac: Only add a new path segment node if the path is already selected
New App Icon from designer (looks good!)
#35: Fix all bad paths effected by paperjs issue 801 on fill click
#34: Update build to Electron latest 0.34.0 released 3 days ago.
#38 & #36: Redo end of path handling code to be more inclusive, and ignore extra work on very short paths.
5e494259: Catch and remove stackblur alert boxes that would occasionally kill app at startup with silly messages.

The RC2 release above has been officially released as 1.0.0-Beta1, so M4 extended Is complete.


fix and enable systemd system tests

The systemd unit test never ran in CI and was broken for various
reasons.  Fix the test to execute Podman in systemd units and to also
run generated units files.
Note: more tests will be added in the future.  The simple check for now
will prevent regressions.
Signed-off-by: Valentin Rothberg<EMAIL_ADDRESS>

LGTM

@baude @giuseppe @mheon @TomSweeneyRedHat PTAL and Merge

/lgtm

Would really like a signoff from @edsantiago before merge

Already looked this morning, but it's Friday so I didn't want to admit to working. LGTM and a welcome addition.


:recycle: Deleted non-functional code

Made required changes in the parser file
Changes

Removed unwanted variables (images, height, width)
Removed functions associated with these variables
Added a new required variable (template)

Did the requested changes. Please have a look! @ruddha2001

@saa27 Looks good to me!


OBS Plugin Volume bug

the volume scale on the obs plugin is wrong i can only move between -3dB and 7dB whereas obs scale is from 0dB to -100dB

also if its at -100dB i can go up to 0dB but can't go back down i get stuck at -3dB.

Can you please describe the problem more accurate? If I test it, it works exactly as expected.
Are you using the increase/decrease volume actions or the set volume action?
When I use the decrease volume action and configure it to decrease by -5dB, it decreases by -5dB every time I press the button, until it's on -100 (-inf)dB. And on the other way, with the increase volume action, it increases by 5dB until the volume is at 0.0dB (it goes a bit above which is a bug of OBS, I might can fix it in my plugin)
A short video that shows your issue would be helpful.

oh i see having it to change by 1dB does not work ty


Linux Deb/ App Image support[Feature Request]

🚀 Feature Request

There are many early users like myself who have been supporting OL Community and use Linux as our primary OS..
I'm willing to contribute in any way possible.

+1, me and my friend are using Linux on both our computers and we need to get a Windows VM to use Carpe. Would love to see a Linux support for Carpe ! Of course it means to (maybe) remove Edge WebView requirements.


CTRL+V tool skews new line placement

Copying a line with CTRL+C and then immediately pasting without moving the cursor places the copy on the map, but skewed:

Perhaps this is intentional (so one can clearly see the copied line), but makes it impossible to e.g., make a ridgeline trail the basis for a county boundary.
If we didn't move the cursor then it should drop the new copy exactly on the same spot.
We can still move the new copy with our mouse, or click to drop it right there.

Same I suppose for points, areas.

Apparently iD is somehow using the center of the line, assuming the user wants to grab that.
Anyway, using one's best efforts to place it back where it was, one gets:

So moving it around by hand is bound to fail, as one cannot just make the whole new line snap to the underlying line.

@jidanni Yes, this is intended. The pasted feature is centered on the mouse cursor, wherever that may be, so the user can then click to place the feature. There isn't a "duplicate in place" operation since most features don't overlap exactly in the real world, and even if they do it makes them difficult to manage if they're mapped that way. I recommend one of these alternatives:

Place the pasted feature approximately in the same place. OSM data doesn't need to be super precise
Use a relation to represent the boundary using the existing trail as a member
Use an editor like JOSM for advanced stuff like this

most features don't overlap exactly in the real world,

Indeed.

and even if they do it makes them difficult to manage if they're mapped that way.

Indeed. If ever needing to detach them it might require node by node work (I don't know.)

Place the pasted feature approximately in the same place. OSM data doesn't need to be super precise

(100 years from now: regret.)

Use a relation to represent the boundary using the existing trail as a member

Very good idea (except when the trail is not the legal boundary definition).

Use an editor like JOSM for advanced stuff like this

Can't! Its hardwired reverse mouse mappings mess up my muscle memory for a month.
OK, I just ended up using a loose approximation (one node instead for each five).


Implement monadic error handling, get rid of JavaScript exceptions

Add PGError type to model different errors that can happen when querying PostgreSQL. The mapping from SQLSTATE to error was inspired by psycopg2.

Run all actions in a new PG monad, which is just Aff stacked with ExceptT PGError to provide monadic error handling. Any errors caused by database access are not thrown as JavaScript exceptions anymore.

While at it, remove some duplication between query and command by reusing ffiUnsafeQuery in both cases.

Fixes #25

Thanks again @akheron!
Some notes (quotes from chat) for myself so I know what I should do before release:

Update docs

Test paulyoung/literate-purescript before updating README docs

I think those docstrings should be revisited at some point, because some things might not be correct anymore

Also, explaining runExceptT and pointing to its documentation should be done somewhere. Probably in README and near type PG a = ExceptT PGError Aff a

F***! The whole review is broken as I've commented above lines which I was interested in and in this form this review is completely unreadable. Probably I have to rewrite it tomorrow ;-)

@akheron Could you read my comments using Files changed tab. All my comments are above the code line of interest ;-)

Thanks a lot @akheron! I'm going to try to compile/test examples from README and finally make a release ;-)

@akheron , @Kamirus
I've migrated Thimoteus/literate-purescript and related libs and I'm waiting for its release (possibly also npm "executable" release), so I can update docs, package.json etc. and make proper release. I hope it is going in the next few days. If not I'm going to make release anyway.


False positive with no-unused-state

I'm getting a false positive:
[eslint] Unused state field(react/no-unused-state)
when using the following:

Is there a way to bypass this warning? (I'm using the latest version).
The following will bypass it:

Thanks

For one, using .map but not using the return array makes no sense; use .forEach
Second, don’t dynamically access props or state - explicitly destructure each one, and the warning won’t appear.
If you insist on keeping your current approach, use an eslint override comment.


Day323

Resolves #656.

Pull Request Test Coverage Report for Build 1241

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 1239:
0.0%

Covered Lines:
5

Relevant Lines:
5

💛  - Coveralls


Create an If operation

The operation would be an input/output operation and have 4 main fields:
'condition': boolean
'then': Operation
'otherwise': Operation
'input': Object
We should also allow a 'predicate' field to be set instead of the 'condition'. The logic would then look something like:
boolean computedCondition;
if(null == condition) {
    computedCondition = null != predicate && predicate.test(input);
} else {
    computedCondition = condition;
}

if(computedCondition) {
    if(null == then) {
        return input;
    }
    // set the input on the 'then' operation
    // see OperationChainHandler.updateOperationInput
    return store.execute(then, context);
}

if(null == otherwise) {
    return input;
}
// set the input on the 'else' operation
// see OperationChainHandler.updateOperationInput
return store.execute(otherwise, context);

This operation should implement Operations and the AddOperationsToChain graph hook should be tested with this operation.

Merged into develop.


(iOS) Support for DemiBold alias of SemiBold (font-weight 600)

For more information on font weight naming see this post.
DemiBold is fairly common in font naming. For example, iOS React Native lacks support of "AvNext-DemiBold".
Also removed warning about NSUInteger <=> NSInteger comparison, by making i an NSUInteger
Before and after screenshots:
Before fix

After

Test Plan
Add any DemiBold font to an iOS react native project.  Set fontWeight to '600' on a <Text /> component. The font weight should be applied appropriately.

From what I can tell, these are valid aliases. Have you looked into the Android side as well?

@ide - from what I have read, using numeric font weights ('500', '600', '700'...etc) doesn't work in android. Is this not the case?  In Android, I just explicitly specify fontFamily for each weight

@ide - here's a post that outlines the discrepancy between iOS and android when it comes to font weights.  Because there is no font-weight-matching logic on android from a numeric value to a font name, this problem doesn't (yet) apply.  On Android you have to be discrete about each font name, which means demibold will already work (it does for me testing both).


Minor cleanups in script downloadinputs.sh

avoid repetitions in the code (DRY principle)
use wget instead of curl to give more feedback to the user.
avoid a few bash warnings reported by shellcheck.
avoid changing directory within the script, this is error prone.

The loop seems like a nice idea in theory, but in practice I am not sure it's good since wiktionary often does things very inconsistently and it's not sure the same logic will continue to work for all language variants.
This applies even more so if one wanted a script version that does not always download the latest but a specific "stable" version.
Apart from that I'd suggest to specify the language list directly in the "for" loop, to avoid an unnecessary bash-ism (the use of an array).

@rdoeffinger Thanks for checking and sorry for disappearing.
I put the language list directly in the for loop as you suggested.
Regarding the use of the "for" loop:
if a dictionary's language format change, it would require to update this file.
But even in this case, with the loop, it would reduce code duplication.
Unless all languages are different, but does it happen?
Let me know, and thanks again for the app and updates, I use it every day!

No worries, I won't ever blame anyone for contributing at their own pace.
I'll accept it with the loop, at least for the moment it's an improvement.
Though I wouldn't agree that it's as simple as "does it reduce code duplication".
In exchange for reducing code duplication a loop does increase complexity, so some repetition can be better, especially when like here there's no risk of hidden bugs really.
All the languages being different would happen if we'd have individual "stable" versions, but it doesn't make sense to consider that now.
There is a little bit of a point that this piece of code might be used by non-programmers in order to generate dictionaries, and without a loop it would be more understandable for them.
But as said overall I concluded I in the end agree with you that the loop is better to have.


Implement header as a RetroTinkReadOnlySetting

Previously, clients of the library could set the value of header, just like any other setting. What this means is that they could, in practice, create an invalid profile that would not load on a RT4k device.
This fact, along with some insights from reverse engineering the audio input override setting, point to the need for a concept of Read Only settings.
These settings should not be directly set on a profile. For the same reasons, we should remove them from the RetroTinkSettingsSchema, as an extra bit of compile-time protection.
If a client attempts to set them on a profile, we will throw a SettingNotWritableError exception.

This PR will require a major revision bump as it would represent a breaking change in the API


JS and CSS static files not found on docker-compose up

Hi there!
after last repo pull and running docker-compose up my admin tool lost the JS and CSS styles :/

any advise to fix it?
thanks in advance

as @JohnSzingerCR advised me,
I could locally fix it using
python3 manage.py collectstatic
in my docker-entrypoint.sh file
now i get CSS and JS properly!

Perfect.
On Thu, Sep 5, 2024 at 12:45 PM Juan A. Ruz @.***>
wrote:

as @JohnSzingerCR https://github.com/JohnSzingerCR advised me,
I could locally fix it using
python3 manage.py collectstatic
in my docker-entrypoint.sh file
now i get CSS and JS properly!
—
Reply to this email directly, view it on GitHub
https://github.com/consumer-reports-innovation-lab/osiraa/issues/30#issuecomment-2332199476,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AX5L4MIDGCRZCVRZDLRQ453ZVCDB5AVCNFSM6AAAAABNRSEJN2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZSGE4TSNBXGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

--

This e-mail message is intended only for the designated recipient(s)
named above. The information contained in this e-mail and any attachments
may be confidential or legally privileged. If you are not the intended
recipient, you may not review, retain, copy, redistribute or use this
e-mail or any attachment for any purpose, or disclose all or any part of
its contents. If you have received this e-mail in error, please immediately
notify the sender by reply e-mail and permanently delete this e-mail and
any attachments from your computer system.


add a paramter(-j/--jpg) to get jpg files.

Because I would like to have both pdf and jpg files, I add a parameter to get jpg files.
'magick' command detection is added, because, in Windows,  convert.exe is sometimes "not ImageMagick".
see https://savage.net.au/ImageMagick/html/install-convert.html
'--use_convert' parameter is also added, because, in some environment, convert.exe is correct one.

Great additions! I'll update the readme to include description of the new features and some creds.


Hosted service LanguagesInUkraineByOblastTiles/MapServer does not have a service definition item

The hosted service "Languages in Ukraine by Oblast (Tile Service)" item exists 348c793923c94499a9a9d4cce4d4224d but does not have an associated service definition portal item. Without the service definition item the service won't be published to any user conference machines.
NOTE: Only hosted services published from ArcGIS Desktop or ArcGIS Pro, which upload a service definition item to portal, will be published to the UC servers.
Owned by Craig C. Either he doesn't have a GitHub account or his account does not have access to the Esri org.

@CraigCleveland

@elinz @jrweakland The ability to publish hosted tile services from ArcGIS Desktop was not possible during the publishing process.  Both myself and Avi could not remedy the issue when we were looking into it.  To that end I published the hosted feature services and generated the tiles from there.  I'll re-work the web maps to just consume the feature services and deal with the performance issues...

@CraigCleveland FYI: Re-ran report and the Hosted\LanguagesInUkraineByOblastTiles/MapServer item still exists. Without service definition portal item, the service won't be published during stand-up of Ops Server. Options are to republish the hosted service so service definition item is uploaded to portal or delete this hosted service. Thanks.

@elinz given that the performance of the feature services in and of themselves (i.e. without tile services) was not that bad, I plan to leave the map and apps the way they are.  Just not worth the additional busy work.  If I unshare the tile services that were generated from the feature services is that enough for you?  Or do you need me to delete them outright?

@CraigCleveland Please delete the un-needed hosted LanguagesInUkraineByOblastTiles map service. Thanks.

@elinz - deleted.

@CraigCleveland The hosted service LanguagesInUkraineByOblastTiles.MapServer still exists (portal item doesn't exist). I can delete this for you, just let me know.

@elinz - deleted.  Not sure how it got orphaned, but either way it's taken care of now.

Confirmed it was deleted.


Updated command-line arguments by switching from sys.argv to argparse.

Previously, i was using sys.srgv to process command-line arguments.
But in this latest update i have changed to using argparse; a recommended option to working with command-line arguments.

Made some updates.
Creating new pull request.