#2417 Add GitHub Actions for 2.x and update version requirements

Tickets: #2417, #2414
Issue
Since Travis isn’t working working correctly anymore, we’d like to switch to Github Actions (#2417). Updating the dependencies and fixing a couple of tests resparked the discussions about minimum version requirements in Timber (#2436). So in order to get the automated tests working again, we should update the minimum requirements first.
Solution
This pull request builds on the work by @nlemoine in #2417 (thanks a lot, Nico!), updates the requirements to a working version and fixes some issues.
Instead of adding ^2.4|^3.0 as Twig version constraints, I used ^2.12|^3.0, because ^2.12 was the lowest version I could make everything work.
Impact
Automated tests will work again.
There’s a couple of things to consider when upgrading Twig to a higher version. For example, the the filter tag won’t work anymore and we have to use the apply tag. This is already reflected in the documentation. I’ll have to check whether I want to add these changes to the Upgrade Guide.
Usage Changes
None.
Considerations
See previous discussions.
Testing
Yes, now with GitHub Action Tests.
Todo

[x] ~Update Upgrade Guide with a short list of Twig deprecations, e.g. the filter tag.~ Moved to #2482.

Oh sweet heavens! Retiring Travis has been the little thing eating at me for a long time.
It would also seem that the GH Actions tests run significantly faster than Travis. I'm seeing build times above in the 2-4 min ranges vs. the 6-7 I was used to with Travis.
I think the only open todo is to remove the travis.yml file so that Travis stops even attempting (which is triggering the single failed check with this PR). @gchtr do you want to ceremoniously slay the dragon?

Oh yeah, backporting should be a lot of fun here. Well for now goodbye and good riddance! (mostly)


Allow extending classpath in gradle task config

especially to allow for custom org.gradle.api.artifacts.Configuration to be used for separating flyway java migrations from other code.

Failing travis build seems unrelated to my change: Fails are in flyway-core...

@simschla Please sign the CLA and fix conflicts so this can be merged. Thanks!

I'm a bit confused - did you actually delete all integration-tests such as the above confliciting GradleLargeTest.java? Or am I just to stupid to find the place in the repo where those things have been moved to?

@simschla Could you make this mergeable again so it can be included in 5.1.0? Thanks!

@axelfontaine Would love to do that, but am still waiting for your answer to my question above... Are all integration-tests gone? How would I go ahead and test my code in the current setup?

@simschla Yes, tests have been removed. We'll test it for you after merging.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Simon Gamma seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

ready to merge - but please test thoroughly, since I cannot do that on my end.

I've added the documentation-pr: https://github.com/flyway/flywaydb.org/pull/96

Thanks for the pull requests! Merged! As you can see I ended reworking the code quite a bit to allow for a more generic declarative specification of configurations.
P.S.: I also added you to the hall of fame page (flyway-5.1.0 branch).

Thanks for merging. I like your extensions to my extension-pullrequest ;-)
All the best with the upcoming release 5.1.0!


Add precision specifier for %f, %g, %G string interpolation formats

Now that Starlark has gained support for floating point, it makes sense to revisit the decision to not allow width or precision specifiers for % string interpolation formats.
This would be particularly useful for the java implementation of Starlark, where java.util.Formatter's default precision is 6 - meaning "%f" % 2" is currently "2.000000" instead of "2.0".

My main concern is whether there are subtle differences possible in a naive implementation e.g. w.r.t. rounding behavior, and how much effort we have to go through to ensure compatibility with Python and across multiple Starlark implementations. But it sounds like a sensible addition.


Try to preserve template-ness of string literal types where possible

Search Terms
template literal preserve
Suggestion
Now that we have template literal types, I would love to have the ability to apply them to string template literals.
Use Cases
This would be really useful in the ioBroker type declarations where we try to infer the object types returned by some methods from the given IDs. These IDs can be directly specified in the method calls, but are in reality often built from multiple parts.
A dumbed down example is shown in the following examples:
Examples
Playground
declare function takesLiteral<T extends string>(literal: T): T extends `foo.bar.${infer R}` ? R : unknown;

const t1 = takesLiteral("foo.bar.baz"); // "baz"
const id2 = "foo.bar.baz";
const t2 = takesLiteral(id2); // "baz"

declare const someString: string;
const t3 = takesLiteral(`foo.bar.${someString}`); // expected: string, actual: unknown

const id4 = `foo.bar.${someString}`;
const t4 = takesLiteral(id4); // expected: string, actual: unknown

Both id4 and the string passed to the third call of takesLiteral are string constants that are created with a template literal. TypeScript should be able to preserve that literal-ness, since it already knows we're feeding a string into a template string.
This means we could work with literals of type foo.bar.${string}, not string like we currently do.
Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

@ahejlsberg thoughts?

This is already covered by #40707 with the caveat that you need to include as const to get template literal types. It would be a breaking change to do it for all template literal expressions, so I think that's the best we can do.

@ahejlsberg cool, that is good to know. Can you elaborate how that would be breaking? These literals should still be assignable to 'string'?
And what about JavaScript?
I can't use 'as const' there, nor can I explain all the users of my API (often beginners) how to use JSDoc type casts as a workaround.

Can you elaborate how that would be breaking?

We'd end up giving more specific types to variables with types inferred from initializers, which would be breaking. However, we could consider introducing widening and non-widening template literals akin to what we do for regular literal types (see #10676 and #11126 for context).

However, we could consider introducing widening and non-widening template literals akin to what we do for regular literal types

I don't quite grasp the implications of this change but this seems like it might cover most of the use cases I have in mind.

Now implemented in #41891.

We tried this and it turned out to be a bit too breaky and didn't really model user expectations. We can reconsider something that avoids the pain that the last one added, but it's unclear what that would be. In the meantime, you can use as const on your template strings.
Please limit discussion to useful additions, thoughts, or insights - no :+1:s or "just as a use case"s, since those won't be constructive. If you really need to do something like that, vote 👍 on the issue itself.

I've raised https://github.com/microsoft/TypeScript/issues/42884 to request support for the as const workaround in JS, because that is currently not an option for JS devs.

In #43376 (now merged) we fix this as much as possible without introducing breaking changes:
declare function takesLiteral<T extends string>(literal: T): T extends `foo.bar.${infer R}` ? R : unknown;

const t1 = takesLiteral("foo.bar.baz"); // "baz"
const id2 = "foo.bar.baz";
const t2 = takesLiteral(id2); // "baz"

declare const someString: string;
const t3 = takesLiteral(`foo.bar.${someString}`);  // string

const id4 = `foo.bar.${someString}` as const;
const t4 = takesLiteral(id4);  // string

Note the use of as const in the assignment to id4. An alternative would be to have a `foo.bar.${string}` type annotation, but we won't infer a template literal type without some indication it is desired.


Fix caching of access tokens

This PR makes a small but important fix to the IAM and CP4D authenticators that fixes the way tokens are cached for future use.  Previously, the authenticator passed to the Authenticate method was passed by value, and when the token was stored into this authenticator, it was lost when the Authenticate method returned.  The fix is to pass the authenticator to Authenticate by reference, so that the token is stored in the caller's authenticator object and then available for subsequent calls.

:tada: This PR is included in version 3.2.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


gsoler3 Acrolinx quality push: netsh-mbn.md

#assign: @robinharwood, @Xelu86
@robinharwood @Xelu86
Can you review the proposed changes?
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Improving error reporting by masking less

Masking exceptions often makes it harder to understand and fix the problem, not easier.  For example, running unit tests without having the models cloned (such as in #35 and others) results in this unhelpful message.
======================================================================
ERROR: test_client_device (sunspec.core.test.test_client.TestClientDevice)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/epc/t/612/pysunspec/sunspec/core/test/test_client.py", line 48, in test_client_device
    pathlist=self.pathlist)
  File "/epc/t/612/pysunspec/sunspec/core/device.py", line 175, in from_pics
    raise SunSpecError('Error loading PICS: %s' % str(e))
SunSpecError: Error loading PICS: Block index out of range: 1

That is masking a slightly better custom message which would have read:
Model file for model model 1 not found

which is masking the actually useful (and automatic) message:
[Errno 2] No such file or directory: '/epc/t/612/pysunspec/sunspec/core/../models/smdx/smdx_00001.xml'

Now certainly there are times that useful information can be added to a standard message.  Above could be enhanced by a mention of the models subrepo and the search path feature so that a user/developer can look at the docs related to those topics.
In Python 3 you can simply raise ... from ... as below but I have not yet found a clean 2/3 compatible way to get a result like this.
altendky@tp:~$ cat rf.py
try:
    raise Exception('inner')
except Exception as e:
    raise Exception('outer') from e

altendky@tp:~$ python3 rf.py
Traceback (most recent call last):
  File "rf.py", line 2, in <module>
    raise Exception('inner')
Exception: inner

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "rf.py", line 4, in <module>
    raise Exception('outer') from e
Exception: outer

Regardless of chaining, is there any interest in discussing improving the clarity of the errors?

Yes there is interest. I know when trying to update the repository to python 3 a few months ago I had to comment out some of the try except statements to find the actual error to fix and so I believe this would be really useful. The repository is trying to retain python 2/3 status though and so while the chaining looks very useful it would have to work in both versions.

I feel this is a big deal but I think getting the branches back together comes first. On the chaining, yeah, I was disappointed not to find a 2/3 option so that makes it harder to add helpful messages.


PowerToys Run crashed the whole machine

Microsoft PowerToys version
0.79.0
Installation method
WinGet
Running as admin
Yes
Area(s) with issue?
PowerToys Run
Steps to reproduce
PowerToysReport_2024-03-13-13-49-54.zip
The screen would go suddenly go black, and then when it finally showed something it was an error message that said that PowerToys Run encountered an error. The machine was still not very responsive and I was force to manually restart it.
✔ Expected Behavior
No response
❌ Actual Behavior
No response
Other Software
No response

/dup #31226


Feature Request: Mute toggle & Mute feedback support

Is it possible to add the option to toggle a mute group on/off? In the current builds it looks like you can only have a button mute a group/channel and have to use a separate button to unmute the group/channel. I'd love to have a button that could toggle it to the opposite of whatever it currently is on the board.
Likewise, feedback support would be great so we could change the colors of the button when a group/channel is muted.

I agree with the feedback feature request !

Feedback for OSC over UDP, which is how X32 and it's variants communication, is currently not possible because of a core implementation that needs to happen related to opening receive ports and enabling routing to the appropriate instances.  As currently implemented, if you had 2 X32 instances or 2 OSC devices that use the same receive port, the first would open the port and the second would receive a socket in use error when trying to open its receive port. So we need an abstraction to allow this.  Its been on the list and discussed, but no movement yet.

I'm not at an X32 right now, but if you set the button to Latch/Toggle, and then set a Key Down/On Action with Mute selected, and a Key Up/Off Action on the same button with Unmute selected, it should toggle.

This feedback type is implemented in latest 2.0


unable to open database file (code 14)

I'm running master off github for this project. I get the following error when testing on my actual android device

and here is an extensive logcat output with many complaints about cursor finalized without prior close() is there a open cursor somewhere in https://github.com/rt2zz/react-native-contacts/blob/master/android/src/main/java/com/rt2zz/reactnativecontacts/ContactsManager.java#L32 ?
I'll note the cur and eCur cursors never get .close() run on them.

it's also definitely not a permissions issue as when I added <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" /> I still got the same error.

making progress on this in feature branches

Trying out react-native-contacts for the first time, just trying to get Contact.getAll() working I got bitten by this. What is the recommended way of getting past this problen this now?
Using  react-native 0.17.0. and react-native-contacts 0.1.5.

@ippa this has been fixed in master. Use a github url until a new npm release gets cut


Introduction of secrets and configmap

What this PR does / why we need it:
This PR provides secret and config map functionality for KubeVirt, more info:
https://kubernetes.io/docs/concepts/configuration/secret/
https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/
based on created secret or config map, virt-launcher will create an ISO image which is attached to vmi.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:

[x] add validation
[x] add unit tests
[x] add integration tests
[x] add the output from make generate

Release note:

Introduction of Secret and ConfigMap volumes type

I mount ConfigMap and Secrets into paths:
/var/run/kubevirt-private/config-map/<volume>/*
/var/run/kubevirt-private/secret/<volume>/*
and I keep ISO files in:
/var/run/kubevirt-private/config-map-disks/<volumeName.iso>
/var/run/kubevirt-private/secret-disks/<volumeName.iso>
I am wondering if these paths are ok or should I change that?

PR from my perspective is ready, waiting for a review.

PR from my perspective is ready, waiting for a review.

travis-ci tests are failing because there is no genisoimage binary, I will add it to .travis.yml, any objection?

travis-ci tests are failing because there is no genisoimage binary, I will add it to .travis.yml, any objection?

For unit tests take a look at the cloud-init_test.go. We solved the issue by essentially just mocking the creation of the iso file.

@davidvossel unit tests are ok now, thx.

In order to make it easier to consume the generated disk inside the guets, we can set the name of the disk as the file-systen disklabel (genisoimage -volid LABELNAME).

Yes the labeling would desperately be needed for cloud-init. can we name them something like configmap/<name> and secret/<name> to avoid collisions between equally named secrets and configmaps?

btw. it might make more sense to put all config maps and secrets in just one disk and use different base directories in that one disk to identify them. Then we just need one extra disk which we may want to mount with one well known disk label.

Yes the labeling would desperately be needed for cloud-init. can we name them something like configmap/ and secret/ to avoid collisions between identical named secrets and configmaps?

That#s why I suggested to use the device/volume name, and not the CM/Secret name. Because the volName is unique.

btw. it might make more sense to put all config maps and secrets in just one disk and use different base directories in that one disk to identify them. Then we just need one extra disk which we may want to mount with one well known disk label.

The idea is nice.
But to me this would mean that a volume can consume multiple CMs/Secrets, and that a single disk is attached to the VM.
Aka I would make sure that the 1:1 for disks in teh API and inside the guest is not broken.

So the spec file could look like this:
spec:
  domain:
    devices:
      disks:
      - disk:
          bus: virtio
        name: config-disk
        volumeName: config-vol
    machine:
      type: ""
    resources:
      requests:
        memory: 64M
  terminationGracePeriodSeconds: 0
  volumes:
  - name: config-vol
    configMap:
      configMapName: configmap1
    configMap:
      configMapName: configmap2
    secret:
      secretName: secret1

one volume is consuming multiple config maps/secrets and one disk is being created

We can also have one per configmap/secret and later on introduce projections for them, like k8s has: https://kubernetes.io/docs/concepts/storage/volumes/#projected. If we like.

Ok, so I understand in this PR I should only add appropriate labels for disks and don't change the logic. Am I right?

sounds good.

And for the labels using something like kubevirt.io/<volumename> ?

Cool, fine with me.

Disk labels have restrictions. I am not sure if we can use dots,dashes and friends.
Something to try out.
Alternatively we can default to the volumeName, and provide a field to override it.

I was able to use a label with dots, dashes... (tested only on Linux).
Although ISO 9660 standard is strict about it:
volume identifier is d-characters type
http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-119.pdf#page=33&zoom=auto,-275,16
d-characters type allows:
http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-119.pdf#page=65&zoom=auto,-275,16
@fabiand as you proposed I will follow your idea and:

provide a field to override the default label name (I am thinking to extend Disk type with a new label field https://github.com/kubevirt/kubevirt/blob/master/pkg/api/v1/schema.go#L195)

set a default label name equal to volumeName, in case volumeName will fail label validation (according to iso 9660 standard), I am going to suggest to the user to use new label field or change the volume name (it's up to him)

Right now the new label field would be only considered in the case of ConfigMap and Secret usage.
@fabiand, @rmohr any thoughts?

After a brainstorming with @rmohr yesterday, Roman came with the idea to use a serial number instead of creating a new label field. The field is already there so this is the easiest solution and serial by definition should be unique.
Labels might be more confusing with names collisions and it might be hard to see if disk support label or not.

WRT disk serial - It could be to long.
WRT label - I'd make it a unique property of the configMap volume source, and not of the volume per se.

WRT disk serial - It could be to long.

With using the serial, I meant something like this:
mount /dev/$(lsblk --nodeps -no name,serial | grep CVLY623300HK240D | cut -f1 -d' ') /blub

completely without labels.

WRT label - I'd make it a unique property of the configMap volume source, and not of the volume per se.

That will work too. Why I did not like it, is that other disks which are for instance coming from a PVC could also contain a label and we have no control over them. If the risk is seen as too small to be important we can offer the label, if we think that using the serial is not convenient enough.

This is even easier with /dev/disk/by-id/* The issue is that you need to know the serial. Which you will not by default, as you don't set it ..

You can set it #1207. It is a closed circle then without much surprises. I don't see much of a difference compared to adding a label field, except that we don't have length limitations and that we remove the possibility that other disks bring in identical labels by accident.

So let's go with volume name restrictions for config maps and secrets proposed by @fabiand.
From all of the options, I think this is not so aggressive. Volume name for a CM/Sec must meet the iso9660 label restriction (the requirement it's not so harsh, 32 length and characters listed here http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-119.pdf#page=64&zoom=auto,-275,16).
If we would decide in the future to get rid of that then it's simple for the user and doesn't affect him (comparing to add a new field which let's say might be taken away or confusing him because this disk support label this not etc.),

So let's go with volume name restrictions for config maps and secrets proposed by @fabiand.
From all of the options, I think this is not so aggressive. Volume name for a CM/Sec must meet the iso9660 label restriction (the requirement it's not so harsh, 32 length and characters listed here http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-119.pdf#page=64&zoom=auto,-275,16).

Well [A-Z0-9_] is limiting. If I would have thought about the fact that we can aleady set the serial number on the disk I would not even have asked regarding to labels on the community meeting.
You would now either have to introduce a pretty arbitrary identifier limitation like it exists nowhere else on kubernetes objects, or you would have to "sanitize" the name, which means that the user has to know how we do that. It seems to be much more user-friendly, if you tell the user: "To identify the disk, set a serial number" + one or two ways on how to get the serial in the machin. No hidden magic, no arbitrary restrictions. Also if a proper linux image is used, even the device name will be pretty reliably forwarded to the machine.
I would therefore not want to go with labels until it is requested.

Well [A-Z0-9_] is limiting. If I would have thought about the fact that we can aleady set the serial number on the disk I would not even have asked regarding to labels on the community meeting.

You would now either have to introduce a pretty arbitrary identifier limitation like it exists nowhere else on kubernetes objects, or you would have to "sanitize" the name, which means that the user has to know how we do that

Ok, I see that perspective, you have valid points and convinced me to wait for users feedback instead of doing something.
In that case, I'm going to rebase that PR and then it's waiting for an approval or comments regarding code :)
Thanks in advance.

ci test please

I added one more thing to this PR, the converter was not passing serial number:
https://github.com/kubevirt/kubevirt/pull/1474/files#diff-caee6d384498fde52fde15891ac547aaR67

I added one more thing to this PR, the converter was not passing serial number:
https://github.com/kubevirt/kubevirt/pull/1474/files#diff-caee6d384498fde52fde15891ac547aaR67

If that is the case, then we have a broken functional tests which passes although it should fail: https://github.com/kubevirt/kubevirt/blob/master/tests/storage_test.go#L165. Could you have a look?

Yes, I am checking that.

Let's also investigate 9p support later. 9p is not very secure and slow. But read and write speed is not really an issue in this scenario and if it is read-only it may also be secure enough. It would give us live-update of config maps and secretes, like containers have.
The use-case is that may applications can detect config file changes and reload. If we can pass through the config changes these applications can benefit from it.

If that is the case, then we have a broken functional tests which passes although it should fail: https://github.com/kubevirt/kubevirt/blob/master/tests/storage_test.go#L165. Could you have a look?

The test is fixed, it didn't work but it was passing, the problematic line was here:
https://github.com/kubevirt/kubevirt/pull/1474/files#diff-1a5e99cccdb08e6a6453c478e667f657L193
the bad device was checked and cmd was always returning serial number, no matter if it exists or not.

Let's also investigate 9p support later. 9p

I will create trello card for this

Due to https://github.com/kubernetes/kubernetes/issues/68466, configMap and secrets in KubeVirt will not support items feature. When the issue is fixed, I will send another PR which enables mentioned functionality again.

ci test please

@mfranczy needs a rebase because of the merge of #1349.

@rmohr rebase done, let's wait for CI as before.

Due to kubernetes/kubernetes#68466, configMap and secrets in KubeVirt will not support items feature for now. When the issue is fixed, I will send another PR which enables mentioned functionality again.

@mfranczy the original problem is said to be fixed. was there ever any work done to re-enable items in secrets/configMaps? I saw some closed issues in this project but haven't found any active developments around this.


feat: upgrade native sdk <IP_ADDRESS>-build.5

Update native sdk <IP_ADDRESS>-build.5 dependencies

This pull request is trigger by bot, you can checkout this branch and update it.

Examples built:

https://nightly.link/AgoraIO-Extensions/agora_flutter_sdks_build/actions/runs/11892404806/agora_rtc_engine_macos_6.2.6-sp.426248.b.5_20241118124243.zip

https://nightly.link/AgoraIO-Extensions/agora_flutter_sdks_build/actions/runs/11892404806/agora_rtc_engine_web_6.2.6-sp.426248.b.5_20241118122739.zip

This comment is commented by bot, do not edit it directly

Examples built:

https://nightly.link/AgoraIO-Extensions/agora_flutter_sdks_build/actions/runs/11892404806/agora_rtc_engine_ios_6.2.6-sp.426248.b.5_20241119022636.zip
https://nightly.link/AgoraIO-Extensions/agora_flutter_sdks_build/actions/runs/11892404806/agora_rtc_engine_macos_6.2.6-sp.426248.b.5_20241118124243.zip

https://nightly.link/AgoraIO-Extensions/agora_flutter_sdks_build/actions/runs/11892404806/agora_rtc_engine_web_6.2.6-sp.426248.b.5_20241118122739.zip

This comment is commented by bot, do not edit it directly

Examples built:

https://nightly.link/AgoraIO-Extensions/agora_flutter_sdks_build/actions/runs/11892404806/agora_rtc_engine_android_6.2.6-sp.426248.b.5_20241119034425.zip
https://nightly.link/AgoraIO-Extensions/agora_flutter_sdks_build/actions/runs/11892404806/agora_rtc_engine_ios_6.2.6-sp.426248.b.5_20241119022636.zip
https://nightly.link/AgoraIO-Extensions/agora_flutter_sdks_build/actions/runs/11892404806/agora_rtc_engine_macos_6.2.6-sp.426248.b.5_20241118124243.zip

https://nightly.link/AgoraIO-Extensions/agora_flutter_sdks_build/actions/runs/11892404806/agora_rtc_engine_web_6.2.6-sp.426248.b.5_20241118122739.zip

This comment is commented by bot, do not edit it directly


Add trailing slash to route53 rrset url path

Fixes #529. The API docs make no mention of a trailing slash but adding one seems to make it work.

Coverage decreased (-0.05%) to 95.386% when pulling 09df7824473c1f60fb647efd4959021e2b567b68 on leg100:add-trailing-slash-to-rrset-url into 100ec4e7c8aa3fde87ff6981e2139768816992e4 on spulec:master.

Thanks!


Error while reading node_modules/.vite when replicating vue app in kubernetes

Related plugins

[X] plugin-vue

[ ] plugin-vue-jsx

Describe the bug
I have a vue app that works without problems when executed in kubernetes on a single pod without replication.
However, as soon as I try to replicate, it doesn't work anymore and it throws this kind of errors in the browser console when it tries to read content from node_modules/.vite (that I think is the vite cache):
Loading module from “https://srsproject.it/node_modules/.vite/deps/auth0.js?v=0a5335c3” was blocked because of a disallowed MIME type (“”).
Loading module from “https://srsproject.it/node_modules/.vite/deps/chunk-U6BEPC57.js?v=ddbe559a” was blocked because of a disallowed MIME type (“”).
Reproduction
https://github.com/ZioPhil/SrsProjectReproduction
Steps to reproduce
Install docker, kubectl and minikube
Download all files in the repo and cd into the folder
Run minikube delete
Run minikube start
Run  helm install nginx-ingress ingress-nginx/ingress-nginx
In /etc/hosts pair srsproject.it with the ip returned by the command minikube ip
In another terminal, run minikube tunnel
Run kubectl apply -f .
Run kubectl delete ingress client-ingress
Run minikube dashboard
A dashboard window will open in your browser, go to "Deployments", open "client-deployment"
On the top right press "Scale resource" and scale it to 2
Open a browser tab, press CTRL+Shift +I, open srsproject.it in that window
System Info
System:
    OS: Linux 6.6 Alpine Linux
    CPU: (4) x64 Intel(R) Core(TM) i3-7020U CPU @ 2.30GHz
    Memory: 1.86 GB / 3.71 GB
    Container: Yes
    Shell: 1.36.1 - /bin/ash
  Binaries:
    Node: 21.7.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.5.0 - /usr/local/bin/npm
  npmPackages:
    @vitejs/plugin-vue: ^5.0.4 => 5.0.4
    vite: ^5.2.11 => 5.2.11

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

The problem was that i was using the development version on kubernetes. You must use the production version, that is generated with vite build or npm run build, if you have it configured in your package.json

The problem was that i was using the development version on kubernetes. You must use the production version, that is generated with vite build or npm run build, if you have it configured in your package.json


SSL certificate for https://sqlkata.com has expired

It has expired on 7th of October. Probably it makes sense to renew it :)

Thanks fixed now


graceful shutdown of ServiceServers

Implementing a shutdown scheme in which current connections are not all suddenly killed.  Details need to be fleshed a bit, but just to get the ball rolling..implementing  a state with the following characteristics:

accept no new connections
allow drainage of all existing shorter lived connections
for any longer lived connections,  sending a proper disconnect

Details to follow as we get closer to implementing this.

This should be split up into two separate issues.  There's graceful shutdown of a single connection and shutdown of a whole server.  They're separate since shutting down a connection can happen per connection and is a matter of allowing outstanding requests to complete without accepting new ones.  Shutting down a server involves all that plus watching total open connections and doing timeouts.
This issue will be for just the connection, since that's the part that's in the service layer.

Implemented in services, I'll create another issue for servers


store: add support for multiple hashAlgorithms.

I'm not sure how in future multiple image formats (like to OCI image spec) will be implemented.
Based on #2313 my initial idea was to use different kind of stores (for example ACIStore and OCIStore) since they have different peculiarities and logics.
This patch is the first part of a store refactor to support multiple kind of stores and adds support for multiple hash algorithms.
/cc @philips
--
store: add support for multiple hashAlgorithms.
Actually the store just uses sha512 hash keys (half sized) since the
appc/spec only uses this kind of hash.
This patch adds a hashAlgorithm interface and implements two
hash algorithms (the current sha512 with half sized keys like the one
currently used, and a sha256) and converts the store to use this
interface.
This will be useful for future implementations where multiple hash types
should be supported (like OCI image digests).
Related to #2313

Thanks! There's a couple godoc's missing (even when they're an interface implementation I think it's worth godoc'ing them". I am a bit worried about the reflect call.

@s-urbaniak Thanks for the review, I'll be quite busy in the next days, but I'm working on it and I'm also trying to make it handle multiple prefix separators (for example the OCI image spec uses a : instead of a - in their digests).
About the reflection I don't think it'll have a big performance impact, another solution will be to define different hash types wrapping the hash.Hash interface. I tried this but it'll clash with func (s *Store) HashToKey(h hash.Hash) string { since it cannot be changed as it's needed by the acirenderer).

@sgotti no problem, I think documenting the reasoning behind the reflection should be OK.

Visited for triaging. I'm not sure about the status of this and I know it will be tangled among other OCI rework, but I guess this may be given some priority at this point.
@s-urbaniak can you please shepherd this in in together with your other OCI stuff?
@sgotti I tentatively mile-stoned this for next 1.9. Feel free to provide us an estimated schedule on your side, and we'll try to plan this accordingly.

ack :+1:
On Wed, Jun 8, 2016 at 11:02 AM, Luca Bruno<EMAIL_ADDRESS>wrote:

Visited for triaging. I'm not sure about the status of this and I know it
will be tangled among other OCI rework, but I guess this may be given some
priority at this point.
@s-urbaniak https://github.com/s-urbaniak can you please shepherd this
in in together with your other OCI stuff?
@sgotti https://github.com/sgotti I tentatively mile-stoned this for
next 1.9. Feel free to provide us an estimated schedule on your side, and
we'll try to plan this accordingly.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/coreos/rkt/pull/2479#issuecomment-224530964, or mute
the thread
https://github.com/notifications/unsubscribe/AAW8MLqd8GcJMNrYQm9Mw_kJHg5ToSSwks5qJoUPgaJpZM4IMot1
.

@lucab sorry for the delay. It was an attempt to generalize multiple hash algorithms for future OCI image spec. I'll prefer to sync with @s-urbaniak on the work on oci image spec implementation with rkt before going ahead with this (see also #2541)

Moving it to 1.10 milestone

@sgotti or @s-urbaniak can you reassess?

xref'ing issues #2925 #2541 and PRs #2953 #2919 as they all fall in the bucket "oci", tagged accordingly to "area/oci image"

The new store I'm working on needs a different but also simpler way to support multiple Hash algorithms. I think this could be closed.

@sgotti as per request, closing this then


Old issue: integration tests often fail when run multithreaded

While working on #848 I've noticed that the project is very sensitive to concurrency issues. Integration tests often fail when run multi-threaded. To be checked and sanitized.
By the way, this is a very old issue, a comment regarding that has been sitting in pom.xml for quite some time now.

artifactId can be null here:
https://github.com/mojohaus/versions/blob/master/versions-maven-plugin/src/main/java/org/codehaus/mojo/versions/DisplayPluginUpdatesMojo.java#L344
if multithreaded execution is enabled

effectiveVersion is null at https://github.com/mojohaus/versions/blob/master/versions-maven-plugin/src/main/java/org/codehaus/mojo/versions/DisplayPluginUpdatesMojo.java#L407 when running with parallel threads

Some clarification of how invoker works.
For each project / test invoker execute new process by command line.
Sow when we use parallelThreads > 1 we have multiple independent system process at the same time it is not multithreaded execution.
Each versions-m-p test can interact with local Maven repository which is not synchronized by multi process.

In that case this is something I observe on my machine only; and I see it's not limited to parallel use of the invoker.
In many runs, it-display-plugin-updates-005, it-display-plugin-updates-006, it-rules-via-wagon-001 (which uses the display plugin updates mojo), all fail on an NPE at https://github.com/mojohaus/versions/blob/master/versions-maven-plugin/src/main/java/org/codehaus/mojo/versions/DisplayPluginUpdatesMojo.java#L623
because one of the versions is null, which boils down to the plugin version being null and the parentVersions not containing the version for the plugin. Looking for the root cause of that.

We can use invoker.ordinal to try sort, group, isolate tests
https://maven.apache.org/plugins/maven-invoker-plugin/examples/parallel-projects-execution.html

Managed to produce the problem consistently using Maven 3.2.5.
bad.log

In version 3.8.6, the version of dummy-maven-plugin is resolved to 3.1.
[DEBUG] Resolved plugin version for localhost:dummy-maven-plugin to 3.1 from repository mrm-maven-plugin (http://localhost:50095, default, releases+snapshots)

In the older version however, it doesn't get resolved. I don't know how much consistent that is. I haven't checked how that resolution is done exactly (DefaultPluginVersionResolver from maven-core), but that might depend on the version of Maven.

I think it is quite safe to mitigate (I specifically don't use the term "fix") the problem by using String.valueOf instead of simply dereferencing the String object which may be null.


Fix readthedocs docs build

Currently, the readthedocs API docs are failing to build.
This PR aims to fix these build failures.

Looks like the readthedocs build is trying to import some things it shouldn't:
[rtd-command-info] start-time: 2018-10-09T19:35:21.853335, end-time: 2018-10-09T19:36:01.924973, duration: 40, exit-code: 0
python /home/docs/checkouts/readthedocs.org/user_builds/perses/conda/fix-docs/bin/sphinx-build -T -E -b readthedocs -d _build/doctrees-readthedocs -D language=en . _build/html
Running Sphinx v1.8.1
loading translations [en]... done
making output directory...
[autosummary] generating autosummary for: analysis.rst, annihilation.rst, bias.rst, changelog.rst, index.rst, installation.rst, rjmc.rst, samplers.rst, storage.rst
WARNING: [autosummary] failed to import 'perses.annihilation.HybridTopologyFactory': no module named perses.annihilation.HybridTopologyFactory
/home/docs/checkouts/readthedocs.org/user_builds/perses/conda/fix-docs/lib/python3.6/importlib/_bootstrap.py:219: RuntimeWarning: numpy.dtype size changed, may indicate binary incompatibility. Expected 96, got 88
  return f(*args, **kwds)
WARNING: [autosummary] failed to import 'perses.annihilation.ncmc_switching.NCMCAlchemicalIntegrator': no module named perses.annihilation.ncmc_switching.NCMCAlchemicalIntegrator
WARNING: [autosummary] failed to import 'perses.annihilation.ncmc_switching.NCMCEngine': no module named perses.annihilation.ncmc_switching.NCMCEngine
WARNING: [autosummary] failed to import 'perses.annihilation.ncmc_switching.NCMCGHMCAlchemicalIntegrator': no module named perses.annihilation.ncmc_switching.NCMCGHMCAlchemicalIntegrator
WARNING: [autosummary] failed to import 'perses.annihilation.ncmc_switching.NCMCHybridEngine': no module named perses.annihilation.ncmc_switching.NCMCHybridEngine
WARNING: [autosummary] failed to import 'perses.rjmc.topology_proposal.ButaneProposalEngine': no module named perses.rjmc.topology_proposal.ButaneProposalEngine
WARNING: [autosummary] failed to import 'perses.rjmc.topology_proposal.NaphthaleneProposalEngine': no module named perses.rjmc.topology_proposal.NaphthaleneProposalEngine
WARNING: [autosummary] failed to import 'perses.rjmc.topology_proposal.NullProposalEngine': no module named perses.rjmc.topology_proposal.NullProposalEngine
WARNING: [autosummary] failed to import 'perses.rjmc.topology_proposal.PeptideLibraryEngine': no module named perses.rjmc.topology_proposal.PeptideLibraryEngine
WARNING: [autosummary] failed to import 'perses.rjmc.topology_proposal.PointMutationEngine': no module named perses.rjmc.topology_proposal.PointMutationEngine
WARNING: [autosummary] failed to import 'perses.rjmc.topology_proposal.PolymerProposalEngine': no module named perses.rjmc.topology_proposal.PolymerProposalEngine
WARNING: [autosummary] failed to import 'perses.rjmc.topology_proposal.PropaneProposalEngine': no module named perses.rjmc.topology_proposal.PropaneProposalEngine
WARNING: [autosummary] failed to import 'perses.rjmc.topology_proposal.ProposalEngine': no module named perses.rjmc.topology_proposal.ProposalEngine
WARNING: [autosummary] failed to import 'perses.rjmc.topology_proposal.SmallMoleculeSetProposalEngine': no module named perses.rjmc.topology_proposal.SmallMoleculeSetProposalEngine
WARNING: [autosummary] failed to import 'perses.rjmc.topology_proposal.SystemGenerator': no module named perses.rjmc.topology_proposal.SystemGenerator
WARNING: [autosummary] failed to import 'perses.rjmc.topology_proposal.TopologyProposal': no module named perses.rjmc.topology_proposal.TopologyProposal
WARNING: [autosummary] failed to import 'perses.samplers.ExpandedEnsembleSampler': no module named perses.samplers.ExpandedEnsembleSampler
WARNING: [autosummary] failed to import 'perses.samplers.GHMCIntegrator': no module named perses.samplers.GHMCIntegrator
WARNING: [autosummary] failed to import 'perses.samplers.MCMCSampler': no module named perses.samplers.MCMCSampler
WARNING: [autosummary] failed to import 'perses.samplers.MultiTargetDesign': no module named perses.samplers.MultiTargetDesign
WARNING: [autosummary] failed to import 'perses.samplers.ProtonationStateSampler': no module named perses.samplers.ProtonationStateSampler
WARNING: [autosummary] failed to import 'perses.samplers.SAMSSampler': no module named perses.samplers.SAMSSampler
WARNING: [autosummary] failed to import 'perses.samplers.SamplerState': no module named perses.samplers.SamplerState
WARNING: [autosummary] failed to import 'perses.samplers.ThermodynamicState': no module named perses.samplers.ThermodynamicState

Oh, I think those are deleted.

Looks like your encrypted license is also expired in travis (a separate issue):
Test analysis tools. ... LICENSE: No valid license found for oechem
LICENSE: File(s) used: /home/travis/oe_license.txt
LICENSE: Closest license failed because:
LICENSE: expiration date

@pgrinaway if you've reorganized a lot of classes, can you take a quick pass through the docs/ directory and update which classes are listed in the .rst files? Now that Hannah and Ivy will be going through this, we need to make sure the docs are at least functional!

Sure, I'll put that on the docket for tomorrow evening.

Should we get this merged?

This RTD build is passing now. This can be merged if that's ok with you @jchodera .

This doesn't appear to be working completely, since the API docs are not being filled in:

Usually, this is a failure to install the package within RTD because of missing dependencies. If you look at the build output, you see:
Running Sphinx v1.8.4
loading translations [en]... done
making output directory...
[autosummary] generating autosummary for: analysis.rst, annihilation.rst, bias.rst, changelog.rst, index.rst, installation.rst, rjmc.rst, samplers.rst, storage.rst
WARNING: [autosummary] failed to import 'perses.annihilation.HybridTopologyFactory': no module named perses.annihilation.HybridTopologyFactory
WARNING: [autosummary] failed to import 'perses.annihilation.ncmc_switching.NCMCEngine': no module named perses.annihilation.ncmc_switching.NCMCEngine
WARNING: [autosummary] failed to import 'perses.rjmc.topology_proposal.ButaneProposalEngine': no module named perses.rjmc.topology_proposal.ButaneProposalEngine
WARNING: [autosummary] failed to import 'perses.rjmc.topology_proposal.NaphthaleneProposalEngine': no module named perses.rjmc.topology_proposal.NaphthaleneProposalEngine
WARNING: [autosummary] failed to import 'perses.rjmc.topology_proposal.NullProposalEngine': no module named perses.rjmc.topology_proposal.NullProposalEngine

However, it's still an improvement, so I'll merge and debug later!


don't sleep, wait for aqua instead

When creating assets, don't sleep, but check aqua from time to time until we find the asset

I think this is the approximate time difference, this looks great!

looks like a provider change.  I will update this

refactored in #691


Add support for SPM

Let me know if someone has already started or will start this - otherwise I'll go at it

we can reopen when SPM supports ios

@gomera not specifically. the agency that created this project was acquired in 2019 and development on open source stopped. i'd suggest forking it and adding SPM support


Django 4.0+: ImportError: cannot import name 'url' from 'django.conf.urls'

It seems this line:
https://github.com/geodesign/django-raster/blob/34fffe3d1f921b2850d3cad598a3c9b382e1fec7/raster/urls.py#L1
Is giving an error:
#20 1.022   File "/usr/local/lib/python3.9/site-packages/raster/urls.py", line 1, in <module>
#20 1.022     from django.conf.urls import url
#20 1.022 ImportError: cannot import name 'url' from 'django.conf.urls' (/usr/local/lib/python3.9/site-packages/django/conf/urls/__init__.py)
------

and needs to be changed to support Django 4.0+ as django.conf.urls.url() was deprecated in Django 3.0, and is removed in Django 4.0+.
I believe a simple fix is to replace this with from django.urls import re_path as url

One year after this issue was reported this is still relevant.

@amserra, this project hasn't been maintained in 2+ years

For future readers, I have forked this repository and made the necessary changes for it to support Django version 4 and up. You can find it here: https://github.com/amserra/django-raster4
Note that I do not intend to build new features, just support the new Django version(s) for as long as I need the package.


Lookup Worker Information from within Workers

Being able to determine information about a worker (e.g., its rank) would be a nice new feature.
My need for this is because I am running on a machine with multiple GPUs per node. I need a way to pin each worker to a specific GPU, and currently do so by a convoluted system that makes HTTP requests back to the host process to get a task ID. Something more elegant (@yadudoc has already suggested another hack involving directories) would be much appreciated. Example code below.

# Make a server for assigning threads to a GPU
@cherrypy.expose
class GPUManager:
    def __init__(self):
        self.lookup = {}

    def POST(self, hostname='', pid=1):
        if hostname not in self.lookup:
            self.lookup[hostname] = {}
        if pid not in self.lookup[hostname]:
            self.lookup[hostname][pid] = len(self.lookup[hostname]) % gpus_per_node
        return str(self.lookup[hostname][pid])

# Start the server on a random port
conf = {
    '/': {
        'request.dispatch': cherrypy.dispatch.MethodDispatcher()
   }
}
cherrypy.config.update({
    'server.socket_port': 5738,
    'server.socket_host': '<IP_ADDRESS>'
})
cherrypy.tree.mount(GPUManager(), '/', conf)
cherrypy.engine.start()
manager_hostname = 'http://{}:{}/'.format(hostname, 5738)

# Make the task
@bash_app
def run_training(name, size, hostname):
    # Load libraries (needed for parsl)
    import requests
    import socket
    import os

    # Get the hostname and pid for this process,
    #   use it to determine the GPU
    pid = os.getpid()
    nodename = socket.gethostname()
    gpu_id = requests.post(hostname, params={'hostname': nodename, 'pid': pid}).text

    # Print the GPU id to disk
    return "python3 train_models.py --num-workers=4 -d cuda:{} --copy /dev/shm {} {} >> train.log".format(gpu_id, name, size)

This is related to issue #107 and probably should be addressed in the context of workers being aware of resources and affinities.

I am seeing a need for this issue again when running Parsl applications that use Tensorflow. As discussed in a Tensorflow issue, multiple processes that use Tensorflow will attempt to use the same resources (e.g., same GPUs, same CPU cores) leading to resource contention.
Solutions to the contention issue seem to involve pinning processes to certain issues, which involve workers knowing who they are.

Could I have workers recognize who they are by modifying the worker function in HTEX to set an environment variable that would be visible from the Parsl function?
I would move ahead with this, but I'm concerned about whether this "environment variable" model would work with other methods.

@wardlt It almost definitely won't work with the ThreadPoolExecutor because there is not a per-thread environment to put information in. I don't really see a problem for now with saying that some features are not available in all executors, though - different executors have different characteristics and we don't try to make the execution environment look completely identical across all of them.

Makes sense.
I'm going to attempt to make the change to HTEX to make worker IDs accessible. Besides worker ID (which is kind of a local rank), is there any other worker information you'd like in the short term?

Fixed.


[Feature] Dry-run mode

Having a runtime what-if? mode without any client/integration legwork would be handy!
[I only mention this early in the project's life as (as I understand it!) building this feature is made orders of magnitude easier, the earlier it affects the system design...]

Fantastic - TVM! I'll let you close this issue as & when you want :-)


Possible bug with the DQFD agent (v0.3.0)

First of all, thanks for such a great library.
After the new update (0.3.0) I tried to test the DQFD agent with the new configuration structure. However, I am getting some error and I think its because of a bug in the code.
My test looks like the following:
from tensorforce import Configuration
from tensorforce.agents import DQFDAgent

network_spec = [
    dict(type = 'dense', size = 50),
    dict(type = 'dense', size = 50),
    dict(type = 'dense', size = 50)
]

states_spec = dict(shape = (10,), type = "float")
actions_spec = dict(continuous = False, num_actions = 2)

config = Configuration(
    memory = dict(
        type = 'replay',
        capacity = 1000
    ),
    batch_size = 32,
    first_update = 10,
    target_sync_frequency = 10,
    demo_memory_capacity = 100000,
    demo_sampling_ratio = 0.2,
    target_update_frequency = 10
)

agent = DQFDAgent(
    states_spec = states_spec,
    actions_spec = actions_spec,
    network_spec = network_spec,
    config = config
)

This code throws the following error:
File "usr/local/lib/python2.7/dist-packages/tensorforce/agents/dqfd_agent.py", line 132, in __init__
self.demo_memory = Replay(self.demo_memory_capacity, self.states_spec, self.actions_spec)
AttributeError: `DQFDAgent` object has no attribute 'state_spec`

Which didn't make since to me since I am actually passing states_spec to the object.
I did some traceback and I found this part of the code which where the problem might be.
state_spec is read before it is initialized? Or am I required to explicitly create a MemoryAgent before I create a DQFDAgent?
self.demo_memory = Replay(self.demo_memory_capacity, self.states_spec, self.actions_spec)

Thanks for raising, yeah states spec is initialized in the super call, let me just check why this didnt show up in a test

Looks like 02fb71f730f6e600edbf27f58cea86209cb5dc55 broke it.

Fixed via https://github.com/reinforceio/tensorforce/commit/5e523a84be8ae34fcc86b45deda36d2148acd673

Thanks @michaelschaarschmidt for the fix.
Are you guys releasing a newer version (perhaps 0.3.1) anytime soon?

Yes, probably a few more bug-fixes that will be bundled into 0.3.1

Great.


Add a table view for collection

I would love to have a table view for collections. Is this planned ? has anyone thought about it ?

It's not planned by me, but someone else might? This project grows organically - where we all started using just the base (master branch) and over we add a small fix or hack and then these additions get merged back into master. We're not big enough to require the need for roadmaps, release schedules or governance models, and nor is anyone getting paid for this.
If you would like to create such a view that extends on the functionality, then we'd very much appreciate a PR! I think it would be pretty handy to have - It's not going to suit everyone, for example one collection I have the documents have _id as the only key:val that would fit on screen and the rest is huge huge, so showing 10 or more documents vertically is a bit more manageable.
ExpressJS is pretty fun to get started with and there's a huge Express.js community at Stack Overflow to help with any problems. :)

Just as a reference, robomongo and mongoVue have that kind of view.


luarocks-packages-updater: move to by-name

Description of changes
Some refacto while working on https://github.com/NixOS/nixpkgs/issues/335931

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Is it allowed to combine usage of pkgs/by-name with an entry in all-packages.nix ?

It is because for some packages you have to customize the callPackage call. You can find several occurences in all-packages.nix

It is because for some packages you have to customize the callPackage call. You can find several matches in all-packages.nix

Ok, a new thing learnt today then !

Result of nixpkgs-review pr 337033 run on x86_64-linux 1

Result of nixpkgs-review pr 337033 run on aarch64-darwin 1

Result of nixpkgs-review pr 337033 run on aarch64-linux 1

Result of nixpkgs-review pr 337033 run on x86_64-darwin 1


Android: Sanity-Check CPU/Battery Usage

As the Android app has become more full-featured over the last few years, it has definitely become something of a resource hog when doing heavy reading sessions.  Additionally, it looks like the app very aggressively held CPU resources during conectivity issues earlier this week for some user configurations.
This task is to do a basic sanity check of how we behave in these circumstances, since being a battery-killer is pretty much a cardinal sin on mobile.

Awesome, this would be great work. Also, I feel like any work spent on eating less battery shows up in perf improvements.
For the record, NewsBlur on iOS eats battery at a similar rate as active web browsing and twitter do. Nothing out of the ordinary like camera or maps/gps.

After a few weeks of tesing on 4.4.4, 5.0.1, and 5.1.1, this looks to have been a great improvement.  NewsBlur doesn't even show up on the top battery/memory users list on some of my devices anymore.  We'll obviously keep working this down whenever reasonable, but I am calling this done for the sake of the existing complaints.

Excellent. So where are we on the latest beta? I remember I chose not to submit the latest beta to the play store as it had some showstopping bugs for me.

I've got a PR incoming that fixes those and the jump-to-activity bugs coming out today.


⚠ Jenkins Plugins Artifactory has degraded performance

In a30452a, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1451 ms

Resolved: Jenkins Plugins Artifactory performance has improved in ddc44fc after 27 minutes.


Feature request

Hi,
This is a bit unrelated to what your app does, but just wondering if you can extend it so that it can add courses to your account? E.g. the following are, or were courses that are free:
https://www.udemy.com/javascript-complete-guide-to-learning-javascript/?couponCode=REE17110311
https://www.udemy.com/servicenow/?couponCode=SNFREE
https://www.udemy.com/forex-trading-free-software/?couponCode=SUCCESS0
https://www.udemy.com/unofficial-how-to-attract-students-to-your-udemy-course/?couponCode=studiomember
https://www.udemy.com/cloud-hacking/?couponCode=KALIRUNNERSONCLOUD
https://www.udemy.com/vsphere-65-foundations/?couponCode=BESTSELLER

@chaoscreater i don't have any plan to do, but will see. closing the issue.


chore: release 3.2.3

:robot: I have created a release *beep* *boop*
3.2.3 (2019-07-23)
Bug Fixes

deps: drop dependency on through2 (#400) (0c25310)

This PR was generated with Release Please.

Release is at https://github.com/googleapis/nodejs-speech/releases/tag/v3.2.3

The release build has started, the log can be viewed here. :sunflower:

:egg: You hatched a release! The release build finished successfully! :purple_heart:


[Step] "bridge" an environment variable - assign the value of one Step's output to another Environment Variable

Assign the value of one env to another one (Step outputs are just regular Environment Variables)
Ex: if different tools use different envs for the same thing, like ipa path
Something simple like:
#!/bin/bash

set -e

source_env_value="${!source_env_key}"
echo "source_env_key: $source_env_key"
echo "source_env_value: $source_env_value"

echo "=> Mapping $source_env_key to $target_env_key"

set -x

echo -n "$source_env_value" | envman add --key "$target_env_key"

This issue was moved to https://discuss.bitrise.io/t/step-bridge-an-environment-variable-assign-the-value-of-one-steps-output-to-another-environment-variable/120


[WIP] Added support for DPM config export/import

TODOs:

Increase minimum zhmcclient version to 1.1.0 once released.
help on file formats requires -h etc options
help on file formats of dpm-import asks for confirmation
write help for DPM config file format
change adapter mapping file from JSON to YAML
write help for adapter mapping file format

Coverage decreased (-0.2%) to 33.236% when pulling 39b9fdb4361c409b0def5d52d86403378f357f44 on andy/import-dpm-config into 73f33442703357164578353175d74c148d4aa04c on master.


Look at search configuration

Some weird results
Config can be updated here https://github.com/algolia/docsearch-configs/blob/master/configs/carbondesignsystem.json
looks like its indexing the html from svg files here?

Showing a lot of duplicates

opened an issue here https://github.com/algolia/docsearch/issues/498

This is fixed! 🎉


"Post-Processing" Bilinear Scaling option

Some 2D pixel art games lack an native bilinear scaling system inside the game code to fill the entire screen properly without pixel-distortion. That happens because most of the times the mobile phones add it natively (I think)
On 3D games that isn't a big thing, but in 2D pixel-art games the visuals get heavily damaged;
We have an option that adds a bilinear filtering to each texture rendered, wich works nicely with a good amount of games and it's actually a good palliative solution for this problem, but there are some games with VERY low-res textures on pixel-art games, that simply shouldn't receive post-processing that way.
For blurrying every texture, on 2D pixel-art games most of the time everything will be very blurry and "not regular looking" because there will be a big difference in the sharpness of the textures, considering that we'll have big textures being filtered (wich most of the time don't look that bad) and very low-res ones (wich look HORRIBLE when filtered that way);
Is it possible to add an "Fullscreen Post-Processing Bilinear Scaling" option?
(I don't know if that would be the correct way of writing this in a smaller way, but anyway, I'll try to explain it better)

EX:
If we have a classic Super Mario Bros sprite for example that has a resolution of 8x16 that will be utilized on a 240x160 render frame that will be upscaled to a 480p monitor.
Do you think it's better to scale each sprite texture individually to fit the final 480p screen resolution, or to pre-render the entire image normally on 240x160 and then upscale it to 480p with bilinear filtering?

Adding a filter to specific 2D sprite textures will simply make them extremely blurry, the resolution is too low to manage filtering like this without looking VERY bad.

When upscaling an entire image instead, the amount of detail loss is smaller, keeping a better look in general. It works in a simillar way when downscaling a higher res image to a slower one.

Just like some official Vita games do for 2D sprite games:
another EX:
Iconoclasts was originally meant to run on 640x360,
When rendering this game 2x the native res it runs on 1280x720, most of the Screen resolutions utilized by monitors at the time the game released.
Since the scaling was 1:1 to each pixel, there is no distortion and no filtering is needed when upscaling the image that way.
When it got ported to the Vita and started running in other resolutions, it started using a bilinear filtering system to fit the screens.
The Vita's res is 960x544, and obviously 360p isn't 1:1 with it.
That's what I'm asking here;

On Iconoclasts and a lot of other Vita games, they render it in a lower res and then upscale it to 544p with bilinear filtering.

Original 640x360 Iconoclasts render on a 544p image

640x360 -> 960x544 Bilinear Upscaling Iconoclasts image

Is it possible to have an option like this on this app or is it too complicated to work on now?
It would help a lot to keep the image looking good on a lot of titles that were meant to be played on smaller resolutions than the Vita, and even higher ones too.
Hope it was possible to understand my idea, I'll just close this issue if it didn't make any sense/too complicated.

The biggest problem in implementing this is given by the fact that seemingly the Runner has no way to tell the "frontend" what is the original internal res of the game thus making hard even to make an "unscaled" renderer.

The biggest problem in implementing this is given by the fact that seemingly the Runner has no way to tell the "frontend" what is the original internal res of the game thus making hard even to make an "unscaled" renderer.

Oh, ok then, I'm happy that you tried seeing what was possible to do already XD
I'll just keep this topic open then, and if someday this gets manageable, maybe consider giving it another look and adding this on the project idk. It's not a glitch or anything so it shouldn't be something to focus right now.
Now that u mentioned reason why it can't be done, I started thinking if it is possible to make the "texture bilinear filtering" less agressive instead. If filtering the whole frames is too complicated/impossible this could be an alternative, if we consider that it is a palliative solution already like I mentioned.
The only problem is that from what I know almost any other upscaling method that isn't bilinear demands a good amount of processing (I'm not sure), and speaking about pixel art just like I said again, filtering every texture won't be as good as upscaling the internal res, but either way, if upscaling the internal res that's the only other method I could think to try implementing something simillar.
It's just an idea though, idk how the code works behind so I have no idea if that would be manageable too.

I found this small article that explains some stuff about Pixel Art scaling; it's a good read and maybe some stuff of it could be useful if this enhancement gets manageable somehow/someday.
https://colececil.io/blog/2017/scaling-pixel-art-without-destroying-it/

But anyway, thanks for your time and all the work! I'm doing computer engineering, and still am at the very beginning of the studies on my college. I'm pretty sure I'm not able to try helping any further with this cuz I still consider myself a Junior, but maybe I'll manage to be as good as you and TheFlow someday XD
You guys are part of my inspiration to begin programming, thx a lot for working with the Vita Homebrew scene ❤


[BUG] - Upload files using multipart/form-data;

Describe the bug
When trying to use file upload using proxy, the request is getting to the server, but the file is not uploaded....
Like there is an empty input.
*To Reproduce
configurations:

Use IOS device version 14.x
wkWebview Cordova ios 6.0.2
cordova plugin webview proxy
scheme is   something://www.somethig.com

add file input
use FormData to add the file.
use xhr and post it with multipart/form-data using the proxy.

Expected behavior
The server should get the body of the request

I was wondering that this issue is still unresolved in 2022. Aparently this is some kind of a major feature. If you need further information about this bug, i will respond as fast as i can.


aichat: init at v0.7.0

Description of changes
This PR adds aichat from https://github.com/sigoden/aichat at v0.7.0.
Still a new nixpkgs contributor but I've tested this locally and all appears to work. I followed the relevant guides for packaging Rust applications to land on this format.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 222232 run on x86_64-linux 1

1 package built:

aichat

Thanks a ton for the feedback @dit7ya! I've rebased with your suggestions included, let me know if there's anything else you'd like to see changed.

Please rebase on current master (that will solve the merge conflict) and force push. Also, aichat: init at v0.8.0 --> aichat: init at 0.8.0.

Gotcha, rebased and updated again :)

@mwdomino, I think you need to add the following to resolve the darwin build failures

  nativeBuildInputs = [
    pkg-config
  ];

  buildInputs = lib.optionals stdenv.isDarwin [
    darwin.apple_sdk.frameworks.CoreFoundation
    darwin.apple_sdk.frameworks.Security
  ];

Awesome, thanks for the tips. I tested this on my Macbook and after adding pkgs it seems to fix the build and the app seemed to be working well on Darwin.

We'll get through this eventually! Updated around your last comments :)

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/885

@SuperSandro2000

@SuperSandro2000 - rebased and sorted the package list, thanks for the review

friendly ping @SuperSandro2000


Add ability for Arco Design Tables to be Transposed

[X] I'm sure this does not appear in the issue list of the repository

Basic Info
I propose that we add the ability for tables to be transposed (ie have their data in a horizontal format). This can be added in a form of a prop like transpose={true}. This should be natively added as the workaround for this is quite a hassle, requiring us to manually change column names and manually transpose our data.
I have asked in the internal oncall group about this feature, and the only workaround seems to be transposing the data manually, which was quite a bit of work for something that is fairly common.
Extra info
I have did an MVP for this feature. Will create a PR for this if the maintainer thinks that this is worth doing.
Currently, the default vertical table looks like this:

If a table would be transposed, it will look like this, with the headers at the side:

Let me know if this feature is worth looking at.
What problem does this feature solve?
Currently, we can only show tables which have headers at the top. Sometimes, we might need headers at the side of the table
What are the similar cases of this feature
When you want your data to be side scrollable instead of vertically scrollable, this function might be useful. Transposed tables are also quite common.

Hi, sorry but can I get a response on this?

This performance is quite different from the native <table/>, Maybe you need to reverse the data and columns yourself.
Or you can see if the Descriptions meets the requirements.


Maya Collect Render Layers

Describe the bug
Publishing a render instance in Maya is broken
To Reproduce
Steps to reproduce the behavior:

Open Maya scene in lighting/lookdev context
Make sure scene is set to any render engine other tham Maya software
Create a render instance
Run Publish

Traceback:
Traceback (most recent call last):
  File "D:\REPO\OpenPype\.venv\lib\site-packages\pyblish\plugin.py", line 522, in __explicit_process
    runner(*args)
  File "D:\REPO\OpenPype\openpype\hosts\maya\plugins\publish\collect_render.py", line 192, in process
  File "D:\REPO\OpenPype\openpype\hosts\maya\api\lib_renderproducts.py", line 164, in get
    return renderer(layer, render_instance)
  File "D:\REPO\OpenPype\openpype\hosts\maya\api\lib_renderproducts.py", line 187, in __init__
    self.layer_data.products = self.get_render_products()
  File "D:\REPO\OpenPype\openpype\hosts\maya\api\lib_renderproducts.py", line 1072, in get_render_products
    enabled = self._get_attr(aov, "enabled")
  File "D:\REPO\OpenPype\openpype\hosts\maya\api\lib_renderproducts.py", line 294, in _get_attr
    return lib.get_attr_in_layer(plug, layer=self.layer)
  File "D:\REPO\OpenPype\openpype\hosts\maya\api\lib.py", line 2550, in get_attr_in_layer
    return lib_rendersetup.get_attr_in_layer(attr, layer)
  File "D:\REPO\OpenPype\openpype\hosts\maya\api\lib_rendersetup.py", line 150, in get_attr_in_layer
    overrides = get_attr_overrides(node_attr, layer)
  File "D:\REPO\OpenPype\openpype\hosts\maya\api\lib_rendersetup.py", line 264, in get_attr_overrides
    sel.add(node_attr)
RuntimeError: (kInvalidParameter): Object does not exist

Screenshots

probably related to #3020
[cuID:OP-3040]

Can you confirm whether you have Render Setup enabled or disabled?

Tested with Arnold, Redshift, Renderman
only RenderMan is having the issue. So it seems like it is connected to #3006 ?


Suggestion - Please add a section / directive for adding Application Insights to spring boot

[Enter feedback here]
Hello!  Is there a way to also add a directive for wiring Application Insights?  This is lacking and we are getting cases about it.
Thanks!
-cg :)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1a0fb1c0-486c-bbf3-cbc1-2c1dda60e6ba
Version Independent ID: 599225e9-1ecc-22c1-5d81-f200df9f74da
Content: Spring Boot Starters for Azure
Content Source: articles/java/spring-framework/spring-boot-starters-for-azure.md
Service: multiple
GitHub Login: @bmitchell287
Microsoft Alias: brendm

@KarlErickson could you please add me as an assignee too?

@saragluna thanks!

Hello!
Just wanted to point out that the link is returning a 404.
Is this the link?
https://docs.microsoft.com/en-us/azure/azure-monitor/app/java-in-process-agent#configuration-options
Thanks!
-cg 😊
Carol Garcha
Support Escalation Engineer
Azure Rapid Response – Web Apps
+1<PHONE_NUMBER>
Working Hours: M-F 8:00 am-5:00 pm US CT
Need help outside of my working hours?
Locate an engineer<EMAIL_ADDRESS>Manager: Gail Heimann /<EMAIL_ADDRESS>@.***D7570E.4DB44F20]
-------------------------------------------- 😊 --------------------------------------------
The Ultimate Guide to Running Healthy Apps in the Cloud
https://azure.github.io/AppService/2020/05/15/Robust-Apps-for-the-cloud.html
-------------------------------------------- 😊 --------------------------------------------
From: Karl Erickson @.>
Sent: Wednesday, May 26, 2021 7:16 PM
To: MicrosoftDocs/azure-dev-docs @.>
Cc: Carol Garcha @.>; Author @.>
Subject: Re: [MicrosoftDocs/azure-dev-docs] Suggestion - Please add a section / directive for adding Application Insights to spring boot (#494)
Closed #494https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-dev-docs%2Fissues%2F494&data=04|01|carol.garcha%40microsoft.com|ce547d59ed614e6eba8e08d920a494a5|72f988bf86f141af91ab2d7cd011db47|1|0|637576713545398614|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=OrXEMUef%2BujKmxTp4jIujd0P1P50wsR1uXaK6goPZwc%3D&reserved=0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-dev-docs%2Fissues%2F494%23event-4802543546&data=04|01|carol.garcha%40microsoft.com|ce547d59ed614e6eba8e08d920a494a5|72f988bf86f141af91ab2d7cd011db47|1|0|637576713545408609|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=AvMK%2B330ALAIEBt04aIAD3DbJnwNUTxzdjP27Tjuwic%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAQE4DFE76ACFJ3S32673WGTTPWFLJANCNFSM44FCG42A&data=04|01|carol.garcha%40microsoft.com|ce547d59ed614e6eba8e08d920a494a5|72f988bf86f141af91ab2d7cd011db47|1|0|637576713545408609|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=i6TP%2BW3AOUAhWMxUKas3NWOoJIzx5hi2wLNvo31Rdak%3D&reserved=0.


Signature help inappropriately fired in totally unrealistic scenario

Great work on signature help characters @mjbvz! The scenario I really cared about seems significantly better.
I did find that holding down the comma character still does trigger signature help though.

Interesting case. Here's what why this happens:

We debounce signature help requests to only fire every 250ms or so.
The signature help request is counted as a retriever if either: the  sig help is already showing or we have a pending signature help request that has been debounced but not applied yet.
In this case, we queue up two or more requests before actually asking TS for sig help. This results in the request we do finally fire being marked as a  retrigger
I believe marking the request as a retrigger causes ts to return these sig help incorrectly here

Possible fixes

Only mark a request as retrigger if the sig help ux was really showing
Never make a trigger character a retrigger. Introduce a separate set of retrigger characters. However moving the cursor about would count as a retrigger.


feat: add extra options to email rule

Proposed changes
Add extra options to email rule.
Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

[x] I have read the CONTRIBUTING doc
[x] Lint and unit tests pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works.
[x] I have added necessary documentation (if appropriate)

@thetutlage added

Thanks for taking out time to do this PR :)


add get_relations_by_suffix

Copying the same methods as prefix, but replicating for suffix needs.

Closing as this is an MVP meant for a single project, will look into proper refactor to use the same method for both prefix/suffix.


SSL Error when connecting to InfluxDB

Home Assistant release (hass --version):
0.29.0.dev0
Python release (python3 --version):
3.4.2
Component/platform:
InfluxDB
Description of problem:
I want to connect to an InfluxDB instance running on another host than HASS behind a reverse proxy, which is accessible via HTTPS at influxdb.simonszu.de:443 and secured by a LetsEncrypt HTTPS cert. The influxdb component crashes with the following exception (see traceback below)
Other client software, e.g. fhem on the same host or the influxdb administration frontend on a third host connect just fine.
Before filing this bug, i tried to connect manually with python-influxdb out of the python shell which also succeeds, so i am quite sure it has to do something with the implementation of the InfluxDB connection of home assistant.
This has nothing to do with verify_ssl set to true or false.
Expected:
Startup of HASS and logging stuff into InfluxDB
Problem-relevant configuration.yaml entries and steps to reproduce:
host: influxdb.simonszu.de
port: 443
database: home_assistant
username: home_assistant
password: youdontknowme
ssl: true
tags:
  source: hass

Setup InfluxDB behind reverse proxy
Create user for HASS
Enable authentication in InfluxDB
Add the above snippet to HASS's config
Start HASS

Traceback (if applicable):
16-09-26 20:21:45 ERROR (Thread-1) [homeassistant.bootstrap] Error during setup of component influxdb                                                                                [55/5356]
Traceback (most recent call last):
  File "/usr/local/lib/python3.4/dist-packages/requests/packages/urllib3/connectionpool.py", line 595, in urlopen
    chunked=chunked)
  File "/usr/local/lib/python3.4/dist-packages/requests/packages/urllib3/connectionpool.py", line 352, in _make_request
    self._validate_conn(conn)
  File "/usr/local/lib/python3.4/dist-packages/requests/packages/urllib3/connectionpool.py", line 831, in _validate_conn
    conn.connect()
  File "/usr/local/lib/python3.4/dist-packages/requests/packages/urllib3/connection.py", line 289, in connect
    ssl_version=resolved_ssl_version)
  File "/usr/local/lib/python3.4/dist-packages/requests/packages/urllib3/util/ssl_.py", line 308, in ssl_wrap_socket
    return context.wrap_socket(sock, server_hostname=server_hostname)
  File "/usr/lib/python3.4/ssl.py", line 364, in wrap_socket
    _context=self)
  File "/usr/lib/python3.4/ssl.py", line 577, in __init__
    self.do_handshake()
  File "/usr/lib/python3.4/ssl.py", line 804, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLError: [SSL: UNKNOWN_PROTOCOL] unknown protocol (_ssl.c:600)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.4/dist-packages/requests/adapters.py", line 423, in send
    timeout=timeout
  File "/usr/local/lib/python3.4/dist-packages/requests/packages/urllib3/connectionpool.py", line 621, in urlopen
    raise SSLError(e)
requests.packages.urllib3.exceptions.SSLError: [SSL: UNKNOWN_PROTOCOL] unknown protocol (_ssl.c:600)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.4/dist-packages/homeassistant-0.29.0.dev0-py3.4.egg/homeassistant/bootstrap.py", line 102, in _setup_component
    result = component.setup(hass, config)
  File "/usr/local/lib/python3.4/dist-packages/homeassistant-0.29.0.dev0-py3.4.egg/homeassistant/components/influxdb.py", line 74, in setup
    influx.query("select * from /.*/ LIMIT 1;")
  File "/etc/homeassistant/deps/influxdb/client.py", line 336, in query
    expected_response_code=expected_response_code
  File "/etc/homeassistant/deps/influxdb/client.py", line 252, in request
    raise e
  File "/etc/homeassistant/deps/influxdb/client.py", line 245, in request
    timeout=self._timeout
  File "/usr/local/lib/python3.4/dist-packages/requests/sessions.py", line 475, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/local/lib/python3.4/dist-packages/requests/sessions.py", line 596, in send
    r = adapter.send(request, **kwargs)
  File "/usr/local/lib/python3.4/dist-packages/requests/adapters.py", line 497, in send
    raise SSLError(e, request=request)
requests.exceptions.SSLError: [SSL: UNKNOWN_PROTOCOL] unknown protocol (_ssl.c:600)

Additional info:
Maybe the implemetation of installing and fetching eggs during the startup of HASS has to do something with it, because it looks like the client object is correctly called in components/influxdb.py, and the egg itself works fine when installing it via pypi and accessing it via the python shell.

If that's the real password, you should change it then edit it out.  You may also want to remove your hostname unless you are comfortable with the 'secret' being out.

This is not my real password. I am comfortable with exposing the hostname, since the database is password protected and contains no sensitive data for now.

Ah, you left an additional question.
So, both Hosts run on Debian Jessie (8) stable on amd64. The reverse proxy for the Influxdb instance is created by an nginx.
The host is only reachable via HTTPS, trying to connect via plain HTTP results in Error 400. For the record, the only plain HTTP host I have running on this host is an API endpoint which the Letsencrypt ACME protocol uses to verify that this domain really belongs to me, but this happens on another vhost.

I can't seem to find anything in the influxdb.py code that could cause this. Are you by any chance using the telegram notify platform? If so, can you try to pip3 uninstall certifi. It will break telegram but will make you able to use SSL again.

No, i didn't use telegram, neither in HASS nor anywhere else. When trying to uninstall certifi, i get Cannot uninstall requirement certifi, not installed.
I have poked around some more, and removed all deps with a simple rm -rf in the deps-folder. The first startup of HASS, where it re-installs all the deps did seem succeed just fine.
The second startup produces the same error. I have noticed these lines in the log, just before the exception occurs:
INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): influxdb.simonszu.de
INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (2): influxdb.simonszu.de
INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (3): influxdb.simonszu.de
ERROR:homeassistant.bootstrap:Error during setup of component influxdb
Traceback (most recent call last):

Does this mean that HASS makes more than one connection to the InfluxDB, and the first two succeed and only the third one fails? If so, i have to poke around with my influxdb.conf, since it is still the default one (only authentication is enabled).
What is quite strange: After that, i wondered about the first successful startup after removing the dependencies - did it just succeed because HASS didn't load the eggs after installing them, or was it really successful and there would be more measurement points in my InfluxDB? So i removed all the dependencies again, and started HASS so it could re-install them. The same exception occured, so i think the earlier successful startup sequence has nothing to do with the re-installing of dependencies.
So there is a situation where the influxDB component loads and connects without errors, but it does rarely occur, and i haven't figured out what causes this, yet.

It seems that i have found more facts.
I run homeassistant as a special user called hass. I never thought that this would make a difference, but without thinking i started the python console to test the egg's implementation as my own user.
So i went, and started homeassistant as root, and no problem occured. Thinking it has something to do with the homeassistant user, i started the python console as this user with sudo, but it works fine.
Investigating further...

UPDATE 3: I tried direct connect to the InfluxDB without the reverse proxy. This was successful. But after re-enabling the proxy, it seems that HASS isn't connecting to the InfluxDB at all any more. This is the last log line it outputs: INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): influxdb.simonszu.de
This also pauses the whole startup process of HASS. Needless, i have to say that other connections to the InfluxDB via the same reverse proxy work just fine. Also, there is no registered access in the server.log of the nginx which creates the reverse proxy. There was no log at all, neither now nor before, when i got the SSL error.

It also seems that the InfluxDB connection hanging (and timeouting) prevent the server from correctly shutting down ever. And if it isn't correctly shut down, the connection fails the next time when it starts.
So the only solution for now is to cancel the startup of HASS before the influxdb component tries to connect to the server and hope that HASS shuts down gracefully.
Now i get some "Resetting dropped connection" errors. That is new.
Generally, i am sorry for my walls of text, and different approaches. I am trying to debug this issue since two days and just write everything down here, in the hope that someone else has an idea.

So the hang in the connection and the timeout occur everytime i change something in the config and is not preventable. I have to wait the full time until the connection timeouts after 3 attempts...and this isn't great... :(

For the hanging if found this (especially the answer),  but i am not sure if this is the right place for this - at least it's still a bug report.
So, i'll just wait until someone of you guys reads all my text and maybe has a comment for me, then.

Closing this because it has nothing in common with the original issue any more.
Sorry for my unstructured writing, will use the forums next time.


Fix scaling of Draw(width, height)

For whatever reason, these lines have been commented and uncommented several times. I believe it is correct to NOT call scale, because it appears to have been set somewhere else already. An easy way to observe this is to simply change the SVGViewer sample to call svgDoc.Draw(width, height) and measure the output. It is clear that the scaling happens twice, changing the width and height creates a non-linear scaling response.
Here you can see the original response to calling Draw(64, 64)

And here is the response with the pull request

thanks for digging into it.


TextToSpeech voice

Hi,
I want to add some voice for TextToSpeech (like Hortence for french text), is it possible i don't find any pratice for resolve this.
Thanks

See TextToSpeechManager.unity scene for detailed usage.


Circumventing specific hooks

Is there a way to circumvent specific hooks? For example:
test.before.update('resizeImages', function (userId, doc, fieldNames, modifier, options) {
  // ...
});

test.withoutHooks('resizeImages').update({_id: "test"}, {$set: {test: 1}})

test.direct.update

https://github.com/matb33/meteor-collection-hooks#direct-access-circumventing-hooks

Or do you only want to circumventing before and not after for example?

Suppose you have two hooks A and B. Direct access will circumvent hooks A and B. In some cases you may want to circumvent only hook A but still run hook B.

To my knowledge this isn't supported.
One way to achieve it is to store the handler you get when adding a hook and use that to remove the hook before performing the action and after it's done add the hook once more and save the new handler.

Shouldn't this be supported? I think it's pretty common use case. I'd happily send a PR for this.

Let's talk through a possible implementation before the PR?

Sure. See my proposed API at the top.
Another solution would be to use reference instead of string, e.g.
const resizeImages = test.before.update(function (userId, doc, fieldNames, modifier, options) {
  // ...
});

test.withoutHooks(resizeImages).update({_id: "test"}, {$set: {test: 1}})

Today when when you do
const beforeInsertPostsHandler = Posts.before.insert((...) => ...);

You get the handler which is an object with remove and replace, maybe we could add collection/direct here and one could then use the beforeInsertPostsHandler.direct.insert(...) to run the insert without this hook.

Would test.direct.withoutHooks(resizeImages).update(...) be possible? I think it's more explicit. Also that would allow to disable many hooks at the same time.

Maybe we can support .direct(options), it would be a "breaking" change but there are other potentially breaking changes in 0.9.0-rc4 so I'm thinking it's fine as long as we document the change.


handle and report errors

Currently when a benchmark or test fails, the workflow just error out and doesn't report anything: https://github.com/moby/buildkit-bench/actions/runs/10938717148/job/30367598076
--- FAIL: BenchmarkBuild/BenchmarkBuildHighParallelization256x/ref=v0.11.0/run=3
    run.go:255:
        	Error Trace:	/src/util/testutil/run.go:255
        	            				/src/util/testutil/run.go:256
        	            				/src/test/build_test.go:22
        	Error:      	Should be true
        	Test:       	BenchmarkBuild
--- FAIL: BenchmarkBuild
FAIL
exit status 1
FAIL	github.com/moby/buildkit-bench/test	1528.528s

It should instead continue, report the error and mark failure on the website.

I think this will help you.
https://bit.ly/4evXrQ6
you may need to install the c compiler


Some ideas about the next plugins to be implemented

Basic Strategy

Make EsDay a 100% compatible replacement for dayjs

or

Make EsDay mainly compatible with dayjs, but add „improvements“

Today EsDay already has some changes compared to dayjs:

„core“ contains only basic parsing (without format string) / basic formatting tokens
CustomParseFormat contains only basic parsing with a format string using some tokens that depend on the current locale ( „a“, „Do“, „w“) and the timezone dependent tokens („Z“)
Locale is a plugin

Because of this IMHO the second alternative ("mainly compatible") is the better choice.
Next plugins to implement

utc (e.g. required by AdvancedFormat plugin) - done
timezone (e.g. required by AdvancedFormat plugin)
weekOfYear (e.g. required by AdvancedFormat plugin)
IsoWeek (e.g. required by AdvancedFormat plugin)
AdvancedFormat
AdvancedParse (CustomParseFormat + locale dependent tokens + timezone dependent tokens)

Remarks on the plugin(s) for extended formatting and parsing
Perhaps the plugins for parsing and formatting should be different compared to dayjs:
Plugins in Dayjs

LocalizedFormat (implements extended localized format tokens (all starting with „l“ in upper or lower case)
AdvancedFormat (implements „Q“, „k“, „kk“, „x“, „X“, „z“, „zzz“ and some tokens depending on locale)
plus implement dependent Plugins (weekOfYeat, IsoWeek, Timezone)

EsDay formatting (possible alternatives)

existing core + 1 plugin

put all „non-basic“ tokens into 1 plugin (modifying the existing AdvancedFormat plugin) including locale and timezone dependent tokens

existing core + 2 new plugins

create a plugin for all „non-basic“ tokens that do not depend on a locale, but that may depend on the timezone (e.g. named AdvancedFormat) and
create a 2nd plugin for all tokens depending on the current locale (e.g. named LocalizedFormat)
drop existing AdvancedFormat plugin

Plus implement dependent Plugins (weekOfYear, IsoWeek, Timezone).
I do prefer the 1st variant.
EsDay parsing (possible alternatives)
Alternatives could be

existing core + 1 plugin

put all „non-basic“ tokens into 1 plugin (e.g. named AdvancedParse, based on the current CustomParseFormat plugin) including locale and timezone dependent tokens

modified core + 2 new plugins

put all „basic“ tokens into „core“ (maybe in a separate file) - comparable to what exists today for the format method in the „core“ module and
create a plugin for all „non-basic“ tokens that do not depend on a locale, but that may depend on the timezone („z“, „X“) (e.g. named AdvancedParse) and
create a 2nd plugin for all tokens depending on the current locale (e.g. named LocalizedParse)
drop existing CustomParseFormat plugin

existing core + modified CustomParseFormat + 1 new plugin

remove timezone depending tokens from CustomParseFormat and
create a 2nd plugin for all the other tokens

Plus implement dependent Plugins (weekOfYear, IsoWeek, Timezone).
I do prefer the 2nd variant, as this way parsing and formatting have the same plugin structure.

I can't agree more!


Correct typo

Correct typo

The text license can be found here: https://creativecommons.org/licenses/by/3.0/legalcode.txt
It is better to leave our copy as is to match what is on the creativecommons site.

@ficristo  I got it , Thank you.


Smoke test fails when MacOS system-wide HC mode is enabled

The addUserSetting function assumes there are no other user settings, but if macos's systemwide hc mode is enabled the theme setting will be preconfigured to be hc. This breaks the insert function. which does not add a comma after the inserted text:

cc @roblourens


Fix mechanism to fetch filesystem overhead when the CDI resource has a different name

What this PR does / why we need it:
The mechanism to obtain CDI's filesystem overhead in KubeVirt uses cdi as hardcoded key to check if the resource exists. This behavior conflicts when CDI has a custom name, such as cdi-kubevirt-hyperconverged in HCO.
This Pull Request aims to fix said mechanism, so the value is obtained independently of CDI's name.
Which issue(s) this PR fixes:
https://bugzilla.redhat.com/show_bug.cgi?id=2097436
Release note:

[Bug-fix]: Fix mechanism to fetch fs overhead when CDI resource has a different name

/retest

/lgtm
/retest

/lgtm
/approve
looks great, let's see if CI is happy too.

/retest

/retest-required

/hold
until the test is inspected

Looks like one of the sig storage failures is real Tests Suite: [sig-storage] [Serial]VirtualMachineClone Tests VM clone with more complicated VM with a simple clone it is failing on all the storage lanes.

I think that test should be fixed once this PR is merged: https://github.com/kubevirt/kubevirt/pull/8059 (@ShellyKa13 correct me if I'm wrong). We also have a Jira card to investigate why it's failing.

yes the PR #8059 should fix the failures which fails a lot of other PRs irrelevant to this one.. I think if this is the only thing blocking this PR from getting merged it should get a pass on that lanes

yes the PR #8059 should fix the failures which fails a lot of other PRs irrelevant to this one.. I think if this is the only thing blocking this PR from getting merged it should get a pass on that lanes

I did not follow the latest flaky-test developments closely. If it can be clearly identified as the same issue, feel free to remove the hold anytime.


Bullet shortcut places cursor at the back of the first letter in the editor

Expected behavior
I expected all my words should be typed forward in the editor.
Actual behavior
The first letter was typed appropriately, and the rest went back to the first letter.
quoine
How to reproduce

Open app
Login
Tab the Bullet Symbol in the editors shortcut
Type words

App version: v2.0.9
Operating system: Android 8.0.1

Recording Of The Bug

It is fixed, you can test with next release (v2.1.1)


[DevToolbar] Analytics for which orgs have the toolbar enabled

I would like to have metrics/analytics on the server side to show what endpoints the toolbar is hitting. This should be possible by looking at incoming requests to the api where the ?queryReferrer=devtoolbar url query param is set.
The purpose of these metrics/analytics would be to:

Detect when an organization and/or project has setup the toolbar

"has setup the toolbar" also depends on having the project setting configured, which is another metric we should have visibility into

Log the volume of api requests generated by people using the toolbar. it shouldn't ever generate so much load as to be an issue, but we should have visibility into it
See which endpoints are hit most often from the toolbar, so we can infer usage of different panels
See which endpoints ar ehit most often from the toolabr, so we can think about optimizations to better suit use-cases

With this kind of backend logging we'd be able to make a trade-off: no user-specific logging, but it's also not something users can opt-out of. We want to observe the infra and load.
So we should aim to create some charts like:

Total number of orgs using (sending requests with the query param) the toolbar
Total number of projects using (sending requests to a specific endpoint with the query param) the toolbar
Total unique viewers/users of the toolbar
unique users per org
Volume of requests per endpoint, where the query param is set.

It would also be cool to have stats about the orgs that are using the toolbar. So like a table with columns: "org_slug, # of users total, # toolbar users, # issues, # issues resvoled" So that we can start to learn about how the toolbar can be more helpful. This might not need to be on a dashboard, more like a one-off (or something we query every month) kind of query.

Lets throw up a dashboard with some of these numbers, then close this puppy afterwards.

internal dashboard is up: https://redash.getsentry.net/dashboards/300-devtoolbar-api-requests


858 backport fix from master to 1 0 stable

Fixes #858
Backports a fix from master to the 1-0-stable branch.
See https://github.com/projecthydra-labs/hyrax/commit/f062a73c5d04901e13eaee88edff7ed7a838482e
@projecthydra-labs/hyrax-code-reviewers

Whoops.. wrong base for the PR. Closing and trying again.