Allow registering async components once instead of every instance

A bit like Alpine.data() allows for registering a component for multiple uses.
Currently if you have an accordion component that sits on each accordion item you will need ax-load-src="https://..." for every instance. We could expose an API like:
AsyncAlpine.data('accordion', 'https://...')

and this would allow components named 'accordion' to omit the ax-load-src attribute.

Related, request from 'niznet' on Alpine.js discord:

It would be great if we can have a path alias as an option because I'm not quite fond of using full src of a module on every lazy component. Something like,
AsyncAlpine(Alpine, {
  alias: '/dist/components/'
})

<div
  ax-load
  ax-load-src="carousel" `without .js seems good too`
  x-data="carousel(args)"
></div>

Then it's might lead to possibility to combine the ax-load-src & x-data into one with its arguments like ax-load-src="carousel(args)".

That last example wouldn't work actually as shopify liquid would need to be in .liquid files, not .js.
Needs more thought, I like the alias idea but I wonder if there is way we could simplify the API in a more flexible way, and whether there is a good solution for both the 'alias' implementation and something like Shopify's.

The solution as mentioned by iniznet in #11, using dynamic imports seems like a good alternative option. We would need to offer a html import option still however. Maybe data() vs urlData()?

The 0.4-rebuild adds a new .data() function that allows for dynamic importing of components in addition to the inline syntax. I would like to look at two other options for specifying components in this Issue. As they would be new API additions, we can look at design and implementation of these once 0.4 is released.
.url()
.url() (or similar) would specify the URL for a module to download, and would allow specifying the URL just once instead of having to use ax-load-src on every one. This would actually just be a short alias for the below, but I think is more user-friendly for some users.
// .url()
AsyncAlpine.url('component', 'https://...')
// equivalent
AsyncAlpine.data('component', () => import('https://...'))

.alias()
.alias() (name undecided) would be similar to the suggestion above where you could specify a directory components come from. If an ax-load component hasn't been loaded by .data(), .url() or with an inline URL it could create the by replacing [name] with the component name and fetching the URL.
AsyncAlpine.alias('/components/[name].js')

These were added to version 0.5.0 with the API as above


How to build C libraries

EOS project have add_wast_library macros
https://github.com/EOSIO/eos/blob/master/CMakeModules/wasm.cmake#L95
which can allow build C-library from .c-files
But if try build some simple C-example with eosio.cdt, this will be failed
$ cat CMakeLists.txt
cmake_minimum_required(VERSION 3.5)
project(helloc VERSION 1.0.0)
find_package(eosio.cdt)
add_contract( helloc helloc helloc.c )
target_compile_options( helloc.wasm PUBLIC -R${CMAKE_CURRENT_SOURCE_DIR} -D=HELLOC)
$ cat helloc.h
#ifdef HELLOC
#warning "Need C compile!"
#endif

void foo();
$ cat helloc.c
#include "helloc.h"

void foo() {}
$

like this
...
make[2]: Entering directory '/home/user/workspace/eosio.cdt/cmake-build-release'
[ 13%] Building C object examples/helloc/CMakeFiles/helloc.wasm.dir/helloc.c.o
cd /home/user/workspace/eosio.cdt/cmake-build-release/examples/helloc && /usr/local/eosio.cdt/bin/eosio-cc  -I/usr/local/eosio.cdt/eosio.cdt/include/libcxx -I/usr/local/eosio.cdt/eosio.cdt/include/libc -I/usr/local/eosio.cdt/eosio.cdt/include  -O3  -O3 -DNDEBUG   -abigen -abigen_output=/home/user/workspace/eosio.cdt/cmake-build-release/examples/helloc/helloc.abi -contract helloc -R/home/user/workspace/eosio.cdt/examples/helloc -D=HELLOC -o CMakeFiles/helloc.wasm.dir/helloc.c.o   -c /home/user/workspace/eosio.cdt/examples/helloc/helloc.c
In file included from /home/user/workspace/eosio.cdt/examples/helloc/helloc.c:1:
/home/user/workspace/eosio.cdt/examples/helloc/helloc.h:2:2: warning: "Need C compile!" [-W#warnings]
#warning "Need C compile!"
 ^
1 warning generated.
error: invalid argument '-std=c++17' not allowed with 'C'
[ 13%] Linking CXX executable helloc.wasm
cd /home/user/workspace/eosio.cdt/cmake-build-release/examples/helloc && /usr/bin/cmake -E cmake_link_script CMakeFiles/helloc.wasm.dir/link.txt --verbose=1
/usr/local/eosio.cdt/bin/eosio-ld  CMakeFiles/helloc.wasm.dir/helloc.c.o -o helloc.wasm
/usr/local/eosio.cdt/bin/wasm-ld: error: undefined symbol: apply
examples/helloc/CMakeFiles/helloc.wasm.dir/build.make:94: recipe for target 'examples/helloc/helloc.wasm' failed
make[2]: *** [examples/helloc/helloc.wasm] Error 255
make[2]: Leaving directory '/home/user/workspace/eosio.cdt/cmake-build-release'
CMakeFiles/Makefile2:1151: recipe for target 'examples/helloc/CMakeFiles/helloc.wasm.dir/all' failed
make[1]: *** [examples/helloc/CMakeFiles/helloc.wasm.dir/all] Error 2
make[1]: Leaving directory '/home/user/workspace/eosio.cdt/cmake-build-release'
Makefile:129: recipe for target 'all' failed
make: *** [all] Error 2
...

$ /usr/local/eosio.cdt/bin/eosio-cc -version
eosio-cc version 1.4.0

eosio.cdt need working add_wast_library analogue for build C-libraries

There is an analog, it is CMake's add_library(...).
add_library


Don't pass control to the next middleware function when redirecting

Maybe this will fix #435?

r? @zalun


Support role-id constraints: Validator.

Nist has a constrained set of keys which express different roles in the role-id field (https://pages.nist.gov/OSCAL/documentation/schema/implementation-layer/component/json-schema/#global_responsible-party).
This enforces a constraint where in certain Dict[str, Object] pairs have keys which must be certain strings.
Criteria for success:

A validator that enforces the criteria
generator functionality correctly identifies these scenarios and correctly generates the role-id.

I did this as a more general form of NCName type validation.
The new mode of validation is ncname and the item is roleid.
If other items of type ncname need validation this can be extended.
No need to change the generator because the default string REPLACE_ME conforms to NCName.

Not required with OSCAL 1.0.0


Unexplained az command failures

Describe the bug
I was in process of enabling pod identity in my AKS cluster using the reference https://docs.microsoft.com/en-us/azure/aks/use-azure-ad-pod-identity.
After I executed the "az extension add --name aks-preview" I believe things have started failing.
Prior to it I wanted to configure my cluster to attach to an Azure CR using the below command:
az aks update -n  -g  --attach-acr
The aks update command started failing as seen in the attached file.
Az command failure error.txt
Taking cue from the error I re-attempted doing the following:
az login
az aks get-credentials --name  --resource-group
But now even the aks get-credentials command fails with same error as that in the attached file. I suspect this started happening after installing aks-preview extension.
I am executing these commands from within Windows Powershell.
Windows-10-10.0.19041-SP0
Python 3.6.8
Installer: MSI
azure-cli 2.13.0 *
Extensions:
aks-preview 0.5.31

route to service team

Actually my bad :-( as I had failed to upgrade the CLI to the supported version. After upgrading there are no errors with what I was attempting to do.
This can be closed for now. regret the false alarm


fixed a few minor bugs and support pytorch0.3

convert feed_interpolated_input input x to x.cuda() if cuda is available
added dim parameter for torch.mean() so that the code base can work with pytorch 0.3

great work! :)


Remove kokkos dep from linux wheel.

Before submitting
Please complete the following checklist when submitting a PR:

[x] All new features must include a unit test.
If you've fixed a bug or added code that should be tested, add a test to the
tests directory!

[x] All new functions and code must be clearly commented and documented.
If you do make documentation changes, make sure that the docs build and
render correctly by running make docs.

[x] Ensure that the test suite passes, by running make test.

[x] Add a new entry to the .github/CHANGELOG.md file, summarizing the
change, and including a link back to the PR.

[x] Ensure that code is properly formatted by running make format.

When all the above are checked, delete everything above the dashed
line and fill in the pull request template.

Context:
Kokkos and Kokkos-kernels are large dependencies which are only there to provide one SpMV routine. We can accelerate the build process and lighten the wheels removing the Kokkos and Kokkos-kernels deps by default.
Description of the Change:
Build with ENABLE_KOKKOS=OFF by default.
Benefits:
Accelerate the build process and lightweight wheels.
Possible Drawbacks:
None.
Related GitHub Issues:
#465

Actually, I assume we still test for the Kokkos & non Kokkos builds in the CI, in the same way as before?

Yes, Kokkos tests use Kokkos, but it is removed from the wheels.


Resuming a v2 session with public cloud storage does not work

It seems that when the session resumes we require cloud storage credentials.
We should also check the case when the session is started with cloud storage with credentials and the session is resumed.
See https://swiss-data-science.slack.com/archives/C67N59QL8/p1727166607703479
│   Warning  FailedMount             79s (x29 over 44m)  kubelet
MountVolume.SetUp failed for volume "pvc-b4ec8f21-ebdc-46b3-834f-0a704809d0f5" : rpc error: code = Unk ││ nown
desc = Cannot find the 'secretName' and/or 'secretNamespace' fields in the volume context. If you are not using automated provisioning you have to specify these values manually i ││ n spec.csi.volumeAttributes in your PersistentVolume manifest. If you are using automated provisioning and these values are not found report this as a bug to the developers.           │

One part of this problem is that if there is an old session that has been started prior to the changes we made in https://github.com/SwissDataScienceCenter/csi-rclone/pull/20
Then the PV looks like this:
apiVersion: v1
kind: PersistentVolume
metadata:
  annotations:
    pv.kubernetes.io/provisioned-by: csi-rclone
    volume.kubernetes.io/provisioner-deletion-secret-name: ""
    volume.kubernetes.io/provisioner-deletion-secret-namespace: ""
  creationTimestamp: "2024-08-23T07:44:59Z"
  finalizers:
  - kubernetes.io/pv-protection
  - external-provisioner.volume.kubernetes.io/finalizer
  name: pvc-1bd81ccc-54a1-48fd-ac9f-4bc650f16538
  resourceVersion: "1310777056"
  uid: ca194346-da61-4187-ab95-745040a30330
spec:
  accessModes:
  - ReadOnlyMany
  capacity:
    storage: 10Gi
  claimRef:
    apiVersion: v1
    kind: PersistentVolumeClaim
    name: xxxx
    namespace: renku
    resourceVersion: "1269553012"
    uid: 1bd81ccc-54a1-48fd-ac9f-4bc650f16538
  csi:
    driver: csi-rclone
    volumeAttributes:
      namespace: renku
      remote: some-remote
      remotePath: some-path
      secretName: some-secret
      storage.kubernetes.io/csiProvisionerIdentity:<PHONE_NUMBER>740-8081-csi-rclone
    volumeHandle: pvc-1bd81ccc-54a1-48fd-ac9f-4bc650f16538
  persistentVolumeReclaimPolicy: Delete
  storageClassName: csi-rclone
  volumeMode: Filesystem
status:
  phase: Bound

But the new code looks for the field secretNamespace in the volume attributes and if it is not there it fails.
The failure message in the k8s pod events is the something like this:
MountVolume.SetUp failed for volume "pvc-1bd81ccc-54a1-48fd-ac9f-4bc650f16538" : rpc error: code = Unknown desc = Cannot find the 'secretName' and/or 'secretNamespace' fields in the volume context. If you are not using automated provisioning you have to specify these values manually in spec.csi.volumeAttributes in your PersistentVolume manifest. If you are using automated provisioning and these values are not found report this as a bug to the developers.

I was under the impression that when we use a public bucket then there is no secret used in the mounting of the csi rclone volume at all. But this is not the case. Even when the bucket is public there is a secret associated with it which holds the whole rclone config. So the error that showed up recently for a private bucket is the same as the one originally reported. And with the release of version 0.3.3 of the csi rclone plugin this should not occur anymore at all.
See https://github.com/SwissDataScienceCenter/csi-rclone/pull/32


Serve index.html when user requests folder path in static file hosting

If we are serving static files and the user GETs a folder path URI like /, we should probably automatically serve /index.html.

Worth mentioning this I guess: https://bjornlu.com/blog/trailing-slash-for-frameworks#servers


Find better name for the Panel classes

After discussing the organization of the panel library we decided that the PanelBase class and its subclass are misnamed. This is because we all agreed that the concept of a panel more accurately describes the combination of several components, e.g. a set of widgets with some associated plot.
The class name for the classes that currently inherit from PanelBase should convey the idea that it is a viewable and reactive object that wraps some other object and displays it as part of some larger panel.
Names that we have considered (and so far rejected):

SubPanel

CC: @jbednar @ceball @jlstevens

The class name for the classes that currently inherit from PanelBase should convey the idea that it is a viewable and reactive object that wraps some other object and displays it as part of some larger panel

I agree with all this, except that "displays it as part of some larger panel" is not a defining feature; it's something that can be done, but is in no way required.  Just wrapping up an mpl figure as something that displays itself is already a meaningful action, whether or not the result ends up in a panel. That's why I don't like SubPanel.
How about Pane?

Pane seems to be the best suggestion so far though View and Viewport were also suggested.


(Suggestion/Enhancement) Add Event Injector

Could you make a way to import wondercards via .pgf files like you can in PKHeX?

Good question. I'll check out the PKHeX API and see if there's a simple way to do this. (I expect there is.)

For now, I've added a Mystery Gift database browser / injector.


Add command and shortcut to copy PR link

In the PR page it's possible to copy the link to the PR (something like https://github.com/org/repo/pull/14). But as far as I can see there is no command to do that from the command palette and it's not possible to assign it a shortcut. This would be very useful when writing change logs. Ideally it would also be possible to copy the link in Markdown, for example [#14](https://github.com/orgrepo/pull/14).

I'll add a command, then you can add your own shortcut.


Improve error messaging when role or env is missing, fixes #888

👍

@maosongfu done. I'm echoing back cluster_role_env, from which we can infer parts.

👍


contorller: Don't call c.Assert in goroutine

It results in a data race (see https://ci.flynn.io/builds/20151128100145-5210d2b0)

LGTM


checkup, setup: Wait for VMI to boot

Wait for the VMI condition VirtualMachineInstanceAgentConnected to be true, or timeout.
Manually tested against an OpenShift Virtualization 4.12 cluster.
This PR depends on PR #30.

Change: Increased ginkgo timeout to wait for the job to complete to 15m.

Rebase


Update needed to HAA v0.9.2

Hi! You made a very cool configuration for HHA, thank you!
Do you have any plans to add new accessories further?
@RavenSystem added new accessories, Garage Door and Window Covering.

I've just added the garage accessory https://github.com/glumb/haa-configurator/commit/40a187dcd3938ad56a4dea9031ecf76c4e9f9cf1. Adding the other new features is also planned.

@glumb is there a new link to get to the garage accessory?  I just tried to compile a configuration for a Sonoff SV and can't seem to find the Garage Door Accessory.

There is a bug in the GitHub „build for GitHub pages“ script, resulting in the page not being updated. I’ll seeing I can trigger the update manually.
The other option is to run the configuration  page locally. git clone, npm i, npm run serve

Garage is now available.
For reference: by disabling and enabling ghPages, the page is rebuild.
This is the issue I was referring to: https://github.community/t5/GitHub-Actions/Github-action-not-triggering-gh-pages-upon-push/td-p/26869/highlight/true/page/2

Thanks for the reply, I will try it out later today. I‘m a total newb with coding so It definitely takes me longer to figure things out. You’re tool helps simplify the coding for HAA, I have played around with HomeBridge so I got some of the basics down, but HAA completely messes me up.
Jean-Claude Pirrello
E-Mail<EMAIL_ADDRESS>Cell:<PHONE_NUMBER>

On Dec 30, 2019, at 6:22 AM, Maximilian Beck<EMAIL_ADDRESS>wrote:

Garage is now available.
For reference: by disabling and enabling ghPages, the page is rebuild.
This is the issue I was referring to: https://github.community/t5/GitHub-Actions/Github-action-not-triggering-gh-pages-upon-push/td-p/26869/highlight/true/page/2
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.


Too many active logins - not an accurate error message?

I am not logged in ANYWHERE except Home Assistant, yet I am still getting this error.
This is related to #57 which attempted to clarify the problem, but I think it is being applied too liberally.
Prior to this pull request being merged, the error I actually received was different - something about "reached maximum number of API requests," so this new wrapper error is, I think, too generic.
I've been locked out of seeing my entities in HA now for over 2 hours.
Polling is OFF on the integration, and my automation that polls every X seconds is also disabled. So literally the only thing that's "logged in" is, and has been, Home Assistant.
Not Postman, not my IOS app, not my partner's IOS app, not a web browser. Nothing except HA.
Logger: homeassistant.config_entries
Source: config_entries.py:594
First occurred: 10:43:10 AM (2 occurrences)
Last logged: 12:20:06 PM

Error setting up entry frigidaire for frigidaire
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/frigidaire/__init__.py", line 547, in post_request
    return self.parse_response(response)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/frigidaire/__init__.py", line 492, in parse_response
    raise FrigidaireException(f'Request failed with status {response.status_code}: {response.content}')
frigidaire.FrigidaireException: Request failed with status 429: b'{"error":"cas_3403","message":"You have exceeded the maximum number of active sessions. Please log out of another device or wait until an existing session expires.","detail":"Too many active login context"}'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/config/custom_components/frigidaire/__init__.py", line 22, in setup
    hass.data[DOMAIN][entry.entry_id] = frigidaire.Frigidaire(
                                        ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/frigidaire/__init__.py", line 247, in __init__
    self.authenticate()
  File "/usr/local/lib/python3.12/site-packages/frigidaire/__init__.py", line 380, in authenticate
    frigidaire_auth_response = self.post_request(self.regional_base_url, '/one-account-authorization/api/v1/token',
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/frigidaire/__init__.py", line 549, in post_request
    self.handle_request_exception(e, "POST", f'{url}{path}', headers, json.dumps(data))
  File "/usr/local/lib/python3.12/site-packages/frigidaire/__init__.py", line 517, in handle_request_exception
    raise FrigidaireException(error_str)
frigidaire.FrigidaireException: Error processing request:
POST https://api.us.ocp.electrolux.one/one-account-authorization/api/v1/token
headers={'x-api-key': 'XXXXXXXXXX', 'Authorization': 'Bearer', 'Accept': 'application/json', 'Accept-Charset': 'UTF-8', 'User-Agent': 'Ktor client', 'Content-Type': 'application/json'}
payload={"grantType": "urn:ietf:params:oauth:grant-type:token-exchange", "clientId": "FrigidaireOneApp", "idToken": "XXXXXXXXXX", "scope": ""}

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

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/frigidaire/__init__.py", line 33, in async_setup_entry
    await hass.async_add_executor_job(
  File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/frigidaire/__init__.py", line 30, in setup
    raise data_entry_flow.AbortFlow("You have exceeded Frigidaire's maximum number of active sessions. Please log out of another device or wait until an existing session expires.") from err
homeassistant.data_entry_flow.AbortFlow: Flow aborted: You have exceeded Frigidaire's maximum number of active sessions. Please log out of another device or wait until an existing session expires.

cc @rothn @bm1549

FYI the lockout/timeout period seems to be exactly 2 hours.

Something smells fishy.

Hmm. I think we just create one session in the config flow's validate_input (custom_components/frigidaire/config_flow.py) and one in the module-level init.py (https://github.com/bm1549/home-assistant-frigidaire/blob/main/custom_components/frigidaire/init.py).
So, what could be going wrong?

It's possible your user gets throttled because we make too many API requests and the server-side error is wrong.
It's possible we create more sessions than we realize, i.e. that async_setup_entry in init.py gets called more than once.

I would start by counting the number of frigidaire.Frigidaire() instances we create, perhaps with some sort of debug print. This would show up in the homeassistant logs. Let us know. I don't have the time to write this for you right now, but it shouldn't be too hard if you can code.

Ok, I can play with that later this weekend, thanks for the tips.
More anecdotes:
I chose to only enable 1 of 3 AC unit entities when my lockout was released, and it worked fine. I was able to control it, and since polling was back on, the state updated within 30 seconds just fine. I sent further controls, no problem.
I then went to enable 1 of the 2 remaining disabled AC entities, and got the "Home Assistant will enable this in 30 seconds" message. In 30 seconds, all entities went back down again, totally unavailable. I assume what HA did in the background was just reload the whole integration, which probably ignores the fact that I have disabled some of the entities.
Anyway, here's to another 2 hours of waiting for my ACs to come back online.

@rothn you got any time this weekend? I tried debugging and couldn't get code to output where you suggested.

Sorry-- I'm visiting family and making some repairs on a property last weekend and this next one. One thing I've noticed is that print() doesn't work well. For an example of logging, see custom_components/frigidaire/humidifier.py in this repo:
import logging
...
_LOGGER = logging.getLogger(__name__)
...
_LOGGER.error("Failed to connect to Frigidaire servers")

Does that work for you?

I added this to the __init_.py file and am only getting output 1x when home assistant restarts and/or when i manually reload my frigidaire config entity.
It does not fire off when command actions are made from HA, nor when it polls every 60 seconds. I will update this when it comes back online after 2 hours because every time I reload the integration now it says I have logged in too many times.
However, I did notice this async_setup_entry method is also present inside the climate.py file. I added a different logging output there, but now I have to wait another 2 hours until I can test it out. Do you think they could by "doubling up?"

The entry in climate.py should not be an issue since it doesn't perform a login, but rather re-uses an existing Frigidaire object (in theory). It's possible that there's some serialization logic going on that causes unexpected behavior. Can you add a logging message directly into /usr/local/lib/python3.12/site-packages/frigidaire/init.py in class Frigidaire -> def __init__()?

It might also be useful to capture a Wireshark trace from your homeassistant server

I am putting debugging on hold. I was able to get full functionality back by reverting to this commit: https://github.com/bm1549/home-assistant-frigidaire/tree/d85d58a9222af0fb95814a611126eebdfc669d6f
And including a few Celsius hacks I've written about in other issues. Maybe when you're back we can go back to debugging again, but my family was getting really hot, haha.

My plugins has stopped working. Any chance we can roll back the HACS release to this commit?

@amaisano / @karlg100 can you try using https://github.com/bm1549/home-assistant-frigidaire/tree/57baf069830a6697fe9c3a25b680cc313a0f6e3a instead? I'd like to isolate the problem to either the changes in the frigidaire module or the changes in this repo

Hey folks, I just opened #62 with should help alleviate the problem by reducing the number of times the plugin tries to re-authenticate
Can you try it out for a few days and see if it makes the situation any better?

Fixed via #62


Path /me/calendar/events/delta(): Change tracking is not supported

The path /me/calendar/events/delta() should not be added into metadata, because it doesn't support change tracking.
The Graph API returns the error

Unsupported request: Change tracking is not supported against 'microsoft.graph.event'

I will not report other issues related to delta, it seems to be a generic problem.
Similar for: https://graph.microsoft.com/beta/me/joinedGroups/microsoft.graph.delta()


Update the README

Need to demonstrate how to

Compile the plugin from source
Utilise Forced Feedback
Extend Effects

Document the Joystick Input remapping


DayStore implementation

Please let me know what the appropriate policy is on adding modified third-party code. In this case, I had to modify https://github.com/jbrukh/window to support hourEntry structs instead of float64.
\cc @vishh @mvdan

I am unable to reproduce the same test failure as Travis on my machine. Any clues?

Careful there.

Why are the tests passing now? Are the travis gods aware of license violations? :)

it was a flaky test: https://github.com/kubernetes/heapster/pull/315/files#diff-e4dfa1a125bfbc4332db2c3b31a2b471L150

ping @mvdan @vishh
unless there are any nits, this PR is ready to merge

@afein: Just a few comments. Overall LGTM! Good work!

addressed the two issues on behavior documentation and test readability

LGTM

squashing and self-merging


Request: GRAV CMS Facebook Event Importer

Hallo,
Sorry for disturbing you...
I've installed your Facebook-Plugin for grav-cms and I love it !!!
Now I have a special request and I don't know if you can or would like to help me:
I need to import Facebook-Events to my Grav-Website... And I have no idea how to write a grav-plugin!
But I suppose, based on your facebook-plugin for the feeds, it might be quite easy to change your plugin to work with facebook-events too
Would it be possible to help me (and probably a lot of other grav-users) to create such a plugin for facebook events?
Probably you just would have to adjust the API url, the vars and some of the values...
But I have no idea how to do this !!!
I found an interesting link about importing facebook events to a website but it requires php-include that is not possible on grav:
https://www.codeofaninja.com/2011/07/display-facebook-events-to-your-website.html
Please let me know if you are willing to help,
Thanks a lot,
Oliver

Sorry that it took so long to answer, but I didn't notice that there are any issues (and got no notification about these).
Yes of course I can be help. I can implement this feature into this plugin also.. ?

I investigated a bit and this seems easy to integrate into this plugin.

I would be sooooooo happy if you could integrate that function...
Thanks Thanks Thanks
Oliver
Visit www.Prinla.com <www.prinla.com>
Prinla.com
Oliver Curcuru
Tel: +34 622 197 423
Mail<EMAIL_ADDRESS>On 11.11.2016 17:49, Mika Hänninen wrote:

I investigated a bit and this seems easy to integrate into this plugin.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mikahanninen/grav-plugin-facebook/issues/2#issuecomment-260000720,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQBuzt__dEfMSNZv_T-PFy1FDEhgOsXzks5q9JyjgaJpZM4KpzEV.

This functionality is added in the 1.2.0 version. Have fun :)


[Calyx-FIRRTL] Initialize output ports

This should hopefully be a small PR! It contains changes to firrtl.rs and associated tests so that output ports are initialized to invalid and 0. (I ran into Calyx programs where externalized memories would never get written, causing the FIRRTL-to-Verilog compiler to complain that output ports that wrote to those memories were never initialized)
Please let me know if there's anything I can improve/fix here!

Great, thanks!!


Supports inputs more than 2 dimensions For efficient-KAN

I don't quite understand KAN's code, is it possiable for KanLinear to do as Torch.nn.Linear: only the last dimension is subjected to derivation operations, allowing inputs greater than 2 dimensions?
For example, in multi head attention, our input is similar to [batch, nhead, dim]
However, this is not allowed in the current KAN ("assert x.dim() == 2 and x.size(1) == self.in_features")
Excuse me! I am very interested in exploring the application of KAN in attention

You could get around by flattening everything upto the final dimension, which in your case [batch*nhead, dim]

You could get around by flattening everything upto the final dimension, which in your case [batch*nhead, dim]

If my input size is (B, C, W, H), for example (8,128,64,64), how do I compress my input and how do I set the parameters of the KAN model.I look forward to your reply to my question. Thank you

You could get around by flattening everything upto the final dimension, which in your case [batch*nhead, dim]

Thank you for your answer!
I must admit that I am still not proficient in expanding the dimensions of torch, because I always worry about whether it will still be in its original position after being restored. He should have restored every element to its original position
Thank you very much, I think this is a very helpful answer!
This means that I can directly use view (batch, -1) for qkv point multiplication
And then switch back from view (batch, nhead, -1), right
This operation has the same effect as q.flat (dim=1) and view (batch, nhead, -1)
There isn't any confusion among them, is there
Thank you very much. If that's the case, I think the issue should be closed immediately😳

You could get around by flattening everything upto the final dimension, which in your case [batch*nhead, dim]

If my input size is (B, C, W, H), for example (8,128,64,64), how do I compress my input and how do I set the parameters of the KAN model.I look forward to your reply to my question. Thank you

It‘s correct! I tried in python use code below:
x=torch.arange(0,16,1).reshape([2,4,2])    # you'll get it as  [batch, nhead, dim]
a = x.view(-1,2)
a.view(-1, 4, 2)   # you can see the data reshaped , if eq the original one, then the operation is correct!
so, try with your shape  (B, C, W, H), maybe it can be influnced by your net design idea.

You could get around by flattening everything upto the final dimension, which in your case [batch*nhead, dim]

If my input size is (B, C, W, H), for example (8,128,64,64), how do I compress my input and how do I set the parameters of the KAN model.I look forward to your reply to my question. Thank you

If you data has spatial structure, I would recommend using convolution version of KAN, which I believe there are some already implemented, for example convKAN or LeKAN (you can search for their github).
If you have extracted the features, then flatten the H and W channels and permute them with the C channel, then you should have input of size [B, H*W, C] and then flatten first 2 dim to [B*H*W, C]. But if H and W is 64, I would suggest down sizing them more till like 16 or 8.


Ensure CLI docs stay up to date

Makefile: auto update nexd/nexctl CLI docs
docs: Update nexctl docs to include device update

commit 2454d033acd5fe138da0ffb576c3efa8e2376586
Author: Russell Bryant<EMAIL_ADDRESS>Date:   Mon Nov 6 16:01:08 2023 -0500
docs: Update nexctl docs to include device update

Signed-off-by: Russell Bryant<EMAIL_ADDRESS>
commit d607a95c64cb5674c0c4f26528e7af8271e5827c
Author: Russell Bryant<EMAIL_ADDRESS>Date:   Mon Nov 6 15:58:09 2023 -0500
Makefile: auto update nexd/nexctl CLI docs

Make the build process automatically update the generated CLI docs for
nexd and nexctl. CI will also fail if CLI options are changed but the
docs are not updated. The `make generate` job will see uncommitted
changes and fail.

Signed-off-by: Russell Bryant<EMAIL_ADDRESS>

@mergifyio rebase


Switch to sidekiq queue

Description of change
Switch to sidekiq queue
https://trello.com/c/poF6WWhT/1571-migrate-from-activejob-to-sidekiq-to-process-background-jobs

I just used swagger to create an application and got this in my logs
bops-sidekiq-1     | 2023-04-13T09:22:38.662Z pid=1 tid=dx5 class=ActionMailer::MailDeliveryJob jid=f21d6a724b6c52726cb90b2a ERROR: Error performing ActionMailer::MailDeliveryJob (Job ID: 958cee67-5017-49d4-bdfb-cccc3626344c) from Sidekiq(low_priority) in 108.12ms: ActiveJob::DeserializationError (Error while trying to deserialize arguments: could not connect to server: No such file or directory

ooh ok will check, thanks

I just used swagger to create an application and got this in my logs
bops-sidekiq-1     | 2023-04-13T09:22:38.662Z pid=1 tid=dx5 class=ActionMailer::MailDeliveryJob jid=f21d6a724b6c52726cb90b2a ERROR: Error performing ActionMailer::MailDeliveryJob (Job ID: 958cee67-5017-49d4-bdfb-cccc3626344c) from Sidekiq(low_priority) in 108.12ms: ActiveJob::DeserializationError (Error while trying to deserialize arguments: could not connect to server: No such file or directory

It seems to work if I remove the line config.action_mailer.deliver_later_queue_name = "low_priority" in application.rb

I just used swagger to create an application and got this in my logs
bops-sidekiq-1     | 2023-04-13T09:22:38.662Z pid=1 tid=dx5 class=ActionMailer::MailDeliveryJob jid=f21d6a724b6c52726cb90b2a ERROR: Error performing ActionMailer::MailDeliveryJob (Job ID: 958cee67-5017-49d4-bdfb-cccc3626344c) from Sidekiq(low_priority) in 108.12ms: ActiveJob::DeserializationError (Error while trying to deserialize arguments: could not connect to server: No such file or directory

It seems to work if I remove the line config.action_mailer.deliver_later_queue_name = "low_priority" in application.rb

Re-added this after diagnosing the issue:

The email job is being executed in sidekiq before the web server has committed the transaction to the database. Since the sidekiq process is using a different database connection it doesn't seen the uncommitted planning application when doing find as part of deserializing arguments.


bump jupyterhub chart to 0.11.1

gets kubespawner 0.15, jupyterhub 1.3
adds hub.config passthrough
changes auth config, shouldn't be much else backward-incompatible
@consideRatio any other expected changes I missed that you think might affect binderhub?

No I think we are good to go, for reference here is the changelog.


Package.json dependencies syntax

@martindsouza Before I accept @fuzziebrain PR, I need to ask, do you usually write your dependencies like this: "through2": "^2.0.1"
or like that: "through2": "2.0.x"
Read https://docs.npmjs.com/files/package.json#dependencies for explanation.
I tend to use "2.0.x" simply because it gives more control to the developer, but I'd like to hear your opinion.

@vincentmorneau I'm still fairly new to dependencies. Usually when I add them I have npm automatically add them through the --S parameter.
Overall I like your idea of 2.0.x Since it'll keep the same version but just update to the latest patch set good with me.


Tensorflow Library not loading in macOS (ImportError)

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
No. I've strictly followed the on-site tutorial
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
macOS Sierra
TensorFlow installed from (source or binary):
binary (https://storage.googleapis.com/tensorflow/mac/gpu/tensorflow_gpu-1.1.0-py2-none-any.whl)
TensorFlow version (use command below):
latest (same as that of on-site tutorial version)
Bazel version (if compiling from source):
Not used as it isn't given in tutorial
CUDA/cuDNN version:
CUDA - 8.0
cuDNN - 6.0
GPU model and memory:
GPU: NVIDIA GeForce GTX 775M 2048 MB
Memory: 8 GB 1600 MHz DDR3
Exact command to reproduce:

You can collect some of this information using our environment capture script:
https://github.com/tensorflow/tensorflow/tree/master/tools/tf_env_collect.sh
You can obtain the TensorFlow version with
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
Describe the problem
ImportError: Traceback (most recent call last):
File "/Users/dwdcw/miniconda3/envs/tf27/lib/python2.7/site-packages/tensorflow/python/pywrap_tensorflow.py", line 41, in
from tensorflow.python.pywrap_tensorflow_internal import *
File "/Users/dwdcw/miniconda3/envs/tf27/lib/python2.7/site-packages/tensorflow/python/pywrap_tensorflow_internal.py", line 28, in
_pywrap_tensorflow_internal = swig_import_helper()
File "/Users/dwdcw/miniconda3/envs/tf27/lib/python2.7/site-packages/tensorflow/python/pywrap_tensorflow_internal.py", line 24, in swig_import_helper
_mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description)
ImportError: dlopen(/Users/dwdcw/miniconda3/envs/tf27/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so, 10): Library not loaded: @rpath/libcudnn.5.dylib
Referenced from: /Users/dwdcw/miniconda3/envs/tf27/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so
Reason: image not found
Failed to load the native TensorFlow runtime.

We have dropped support for Mac-GPU setups, starting with 1.2 release.
But your problem is caused by mismatch in cuDNN versions.
All TF binaries are built with cuDNN 5 support.
For use with cuDNN 6, you will need to build from sources.

I had the same problem 'ImportError: dlopen(/Users/dwdcw/miniconda3/envs/tf27/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so, ' .
I solved this by using VirtualEnv to install tensorflow and then success.
I think maybe VirtualEnv can provide more clear enviroment. You can try

I have tried tensorflow-1.10 but got the same problem.
It works on tensorflow-1.9.0

Same problem. tensorflow-1.9.0 works but 1.10 doesn't.


Put a link to "How to use" page in all repositories

Currently only "japan" repository:
https://google.org/personfinder/japan/
has a link to "How to use" page:
http://personfinder.google.org/global/howto.html
using a custom message.
It should be inserted to all repositories by putting it in the HTML template.

Could you point out where these HTML templates are located and the code to Japan as well?

Thanks for the interest! We are currently redesigning the UI (#478), so it may be better to wait until the redesign is settled, then add it to the new UI.

Acknowledged

Is it done yet?

Thanks for the reminder, we do have a mock that includes the how-to link for the new UI on repo homepages, here it is. If you'd like to do this or other work on the new UI (which we're building with React), there's instructions on how to get started here. Let me know if you have any questions of course.
We haven't made a decision on where to put it in the old UI (which we're kinda-sorta converting to the lite mode UI) yet.


Refactor fixer with strategies

The fixer should have multiple fix strategies which can be chosen in accordance with the origin of the trigger (PR comment, issue, etc).

Fixed with #55


match moment's hebrew/israel locale (he-IL) to java's alternate locale code (iw-IL)

When I pass the locale which i get from our back-end java web-service to our client-side app (which uses moment), the locale 'iw-IL' doesn't get mapped to hebrew but chinese instead in moment.js.
So for example when i use something like this:
moment( '25/12/1960', 'DD/MM/YYYY' ).locale( 'iw-IL').format( 'LL' );
I get back chinese formatting, when it should have the same result as hebrew-Israeli formatting:
moment( '25/12/1960', 'DD/MM/YYYY' ).locale( 'he-IL').format( 'LL' );
Can we also support iw (and ji and in) to support java's backwards-compatible locales?
(I can put custom code in my app that passes 'he' instead to my moment formatting calls like above, but thought we could just handle from moment's supported locales).
Applicable info:
https://docs.oracle.com/javase/8/docs/api/java/util/Locale.html
"Locale's constructor has always converted three language codes to their earlier, obsoleted forms: he maps to iw, yi maps to ji, and id maps to in. This continues to be the case, in order to not break backwards compatibility."

I can't reproduce this:
moment( '25/12/1960', 'DD/MM/YYYY' ).locale( 'iw-IL').format( 'LL' );
"December 25, 1960"

"iw-IL" isn't mapped to Hebrew or any other language. Is it possible you just had Chinese set before and had that left over when locale("iw-IL") nooped?
If we have support aliases for locales (@ichernev - we never did that, right?) then we could make iw into an alias for he. In the meantime, we're not going to add whole locales for defunct ISO 639 codes just because Java likes them. I recommend you just check the codes coming back from the server and map them to their modern equivalents.

For locale aliases, I suppose we could just use parentLocale without overriding anything.

@icambron hey i guess it was an older version I am using in app where the chinese showed up (2.10.2):
https://jsfiddle.net/god358j9/

I recommend you just check the codes coming back from the server and map them to their modern equivalents.
Yes, I can do this.

For locale aliases, I suppose we could just use parentLocale without overriding anything.

That's true. Like a little stub that just inherits.


Unable to sign transaction using example

I get
"Unsupported operation: Int64 accessor not supported by dart2js."
When trying to sign an transaction using example at:
https://github.com/Soneso/stellar_flutter_sdk/blob/master/documentation/sdk_examples/send_native_payment.md
Error is in browser_client.dart, row 58 in http lib
completer.complete(StreamedResponse(
Using Flutter 2.5.1
stellar_flutter_sdk: ^1.2.1
Visual Studio Code 1.60.1 on Windows 10.
Flutter extension: 3.26.0
Using Network.TESTNET and StellarSDK.TESTNET;
Fetching account information works but not signing a transaction.
Have created and funded two separate accounts on TESTNET just to test but without luck.
Tested the same transaction with Stellar Laboratory and it works.
Fairly new to flutter but have done a couple of project using the go client for Stellar.

Hello @torkel, unfortunately the sdk is not working with flutter web.

Hello @torkel, unfortunately the sdk is not working with flutter web.

Hello Christian
We need to use flutter web also for our project but these errors don't allow us to use it. Why this SDK is not working for flutter web? There is no chance that we will have it as soon as possible?

@christian-rogobete
Please help me 🙏🌹

Hello @AliKarimiENT, unfortunately I can not help you with this. It is not working with flutter web because the code and libraries used can not be used on flutter web. Maybe some day as flutter web gets more advanced it will work. For now I recommend you to use the js sdk for web.

Hello @AliKarimiENT, unfortunately I can not help you with this. It is not working with flutter web because the code and libraries used can not be used on flutter web. Maybe some day as flutter web gets more advanced it will work. For now I recommend you to use the js sdk for web.

Yes, thanks for your response
Actually I don't know js and I'm a flutter developer.
Now , some parts work correctly but in some parts I face some unknown issues .
Is it a good idea that I use direct APIs instead of using the SDK ? Does this help me to achieve my goal or not?

Depends on what you want to do. If you need to sign transactions you will not be able to do it with API calls. I think that the best idea is to learn and use the js sdk. Especially if you want to sign in the client and not send or store secret keys to/on the server.


Reverse Grayscale theme colors and delete lightest colors from theme …

…and defaults
Addresses issue #117

@rawrmonstar thanks!


Eliminate SeqAnnFeatureCategory

This will quickly grow out of control if many new types of data are added.  Put in a string field instead, or perhaps one tied to an ontology.

Uri Laserson<EMAIL_ADDRESS>writes:

This will quickly grow out of control if many new types of data are added. Put
in a string field instead, or perhaps one tied to an ontology.

I am inclined to agree.  This was an experiment in making the
very common cases easier to program.  We went down the path of
considering specific record types for common cases (Gene,
Transcript, Exon, etc).  The lack of polymorphism in Avro makes
this far more complex that it's worth.
It does seem like a hack, although it was only intended to have
the very common cases, and FEATURE_OTHER requiring looking at
the actually feature definition.

My main hesitation here is that the feature and featureCategory fields may disagree with each other.

That would be bad, although all of this data really needs struck
validation.
I hesitate because it seems like hack.
One thought is to have records that define the orthology terms that can
be uses as comparison.  For instance:
record SOCommonOrthology {
OrthologyTerm GENE  = ...;
OrthologyTerm TRANSCRIPT  = ...;
OrthologyTerm EXON  = ...;
OrthologyTerm INTRON  = ...;
}
GA4GH is in bad need of some defined idioms on how to do things
like this and contained trees vs ids.  I don't actually like the
flattening of records; but have gotten a lot of pushback on it.
Mark
Uri Laserson<EMAIL_ADDRESS>writes:

My main hesitation here is that the feature and featureCategory fields may
disagree with each other.
—
Reply to this email directly or view it on GitHub.*

done.    Never watch a programmer thing out loud.


mopidy: 2.3.1 -> 3.0.1 mopidy-mpd: init at 3.0.0  mopidy-mpris: init at 3.0.1  mopidy-somafm: init at 2.0.0rc1  mopidy-youtube: 2.0.2 -> 3.0a1  pykka: 1.2.0 -> 2.0.2

mopidy-gmusic: 3.0.0 -> 4.0.0
mopidy-mpd: init at 3.0.0
mopidy-mpris: init at 3.0.1
mopidy-somafm: init at 2.0.0rc1
mopidy-youtube: 2.0.2 -> 3.0a1
pykka: 1.2.0 -> 2.0.2

Motivation for this change
This changeset moves mopidy onto the python3 branch (the python2 version is EOL), and updates some plugins. Note that mopidy-mpd was bundled with mopidy previously, but has been extracted into its own plugin in this release.
This PR is slightly WIP as in I cannot figure out how to get mopidy-youtube to build; any help debugging this build error would be appreciated:
these derivations will be built:
  /nix/store/jjjwxll07x0fiin90sh4mbanlhhy36vd-mopidy-youtube-3.0a1.drv
building '/nix/store/jjjwxll07x0fiin90sh4mbanlhhy36vd-mopidy-youtube-3.0a1.drv'...
Sourcing python-catch-conflicts-hook.sh
Sourcing python-remove-bin-bytecode-hook.sh
Sourcing setuptools-build-hook
Using setuptoolsBuildPhase
Using setuptoolsShellHook
Sourcing pip-install-hook
Using pipInstallPhase
Sourcing python-imports-check-hook.sh
Using pythonImportsCheckPhase
unpacking sources
unpacking source archive /nix/store/cnmj7lyj3ch2gskd0fdfhwlddnav2758-Mopidy-YouTube-3.0a1.tar.gz
source root is Mopidy-YouTube-3.0a1
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file Mopidy-YouTube-3.0a1/setup.cfg
patching sources
configuring
no configure script, doing nothing
building
Executing setuptoolsBuildPhase
running bdist_wheel
running build
running build_py
creating build
creating build/lib
creating build/lib/mopidy_youtube
copying mopidy_youtube/youtube.py -> build/lib/mopidy_youtube
copying mopidy_youtube/backend.py -> build/lib/mopidy_youtube
copying mopidy_youtube/__init__.py -> build/lib/mopidy_youtube
creating build/lib/mopidy_youtube/apis
copying mopidy_youtube/apis/youtube_scrapi.py -> build/lib/mopidy_youtube/apis
copying mopidy_youtube/apis/youtube_japi.py -> build/lib/mopidy_youtube/apis
copying mopidy_youtube/apis/youtube_bs4api.py -> build/lib/mopidy_youtube/apis
copying mopidy_youtube/apis/youtube_api.py -> build/lib/mopidy_youtube/apis
copying mopidy_youtube/apis/__init__.py -> build/lib/mopidy_youtube/apis
running egg_info
writing Mopidy_YouTube.egg-info/PKG-INFO
writing dependency_links to Mopidy_YouTube.egg-info/dependency_links.txt
writing entry points to Mopidy_YouTube.egg-info/entry_points.txt
writing requirements to Mopidy_YouTube.egg-info/requires.txt
writing top-level names to Mopidy_YouTube.egg-info/top_level.txt
reading manifest file 'Mopidy_YouTube.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching '.mailmap'
warning: no files found matching '*' under directory '.github'
warning: no files found matching '*' under directory 'tests/data'
writing manifest file 'Mopidy_YouTube.egg-info/SOURCES.txt'
copying mopidy_youtube/ext.conf -> build/lib/mopidy_youtube
installing to build/bdist.linux-x86_64/wheel
running install
running install_lib
creating build/bdist.linux-x86_64
creating build/bdist.linux-x86_64/wheel
creating build/bdist.linux-x86_64/wheel/mopidy_youtube
copying build/lib/mopidy_youtube/ext.conf -> build/bdist.linux-x86_64/wheel/mopidy_youtube
creating build/bdist.linux-x86_64/wheel/mopidy_youtube/apis
copying build/lib/mopidy_youtube/apis/__init__.py -> build/bdist.linux-x86_64/wheel/mopidy_youtube/apis
copying build/lib/mopidy_youtube/apis/youtube_api.py -> build/bdist.linux-x86_64/wheel/mopidy_youtube/apis
copying build/lib/mopidy_youtube/apis/youtube_bs4api.py -> build/bdist.linux-x86_64/wheel/mopidy_youtube/apis
copying build/lib/mopidy_youtube/apis/youtube_japi.py -> build/bdist.linux-x86_64/wheel/mopidy_youtube/apis
copying build/lib/mopidy_youtube/apis/youtube_scrapi.py -> build/bdist.linux-x86_64/wheel/mopidy_youtube/apis
copying build/lib/mopidy_youtube/__init__.py -> build/bdist.linux-x86_64/wheel/mopidy_youtube
copying build/lib/mopidy_youtube/backend.py -> build/bdist.linux-x86_64/wheel/mopidy_youtube
copying build/lib/mopidy_youtube/youtube.py -> build/bdist.linux-x86_64/wheel/mopidy_youtube
running install_egg_info
Copying Mopidy_YouTube.egg-info to build/bdist.linux-x86_64/wheel/Mopidy_YouTube-3.0a1-py3.7.egg-info
running install_scripts
creating build/bdist.linux-x86_64/wheel/Mopidy_YouTube-3.0a1.dist-info/WHEEL
creating 'dist/Mopidy_YouTube-3.0a1-py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it
adding 'mopidy_youtube/__init__.py'
adding 'mopidy_youtube/backend.py'
adding 'mopidy_youtube/ext.conf'
adding 'mopidy_youtube/youtube.py'
adding 'mopidy_youtube/apis/__init__.py'
adding 'mopidy_youtube/apis/youtube_api.py'
adding 'mopidy_youtube/apis/youtube_bs4api.py'
adding 'mopidy_youtube/apis/youtube_japi.py'
adding 'mopidy_youtube/apis/youtube_scrapi.py'
adding 'Mopidy_YouTube-3.0a1.dist-info/LICENSE'
adding 'Mopidy_YouTube-3.0a1.dist-info/METADATA'
adding 'Mopidy_YouTube-3.0a1.dist-info/WHEEL'
adding 'Mopidy_YouTube-3.0a1.dist-info/entry_points.txt'
adding 'Mopidy_YouTube-3.0a1.dist-info/top_level.txt'
adding 'Mopidy_YouTube-3.0a1.dist-info/RECORD'
removing build/bdist.linux-x86_64/wheel
Finished executing setuptoolsBuildPhase
glibPreInstallPhase
installing
Executing pipInstallPhase
/build/Mopidy-YouTube-3.0a1/dist /build/Mopidy-YouTube-3.0a1
Processing ./Mopidy_YouTube-3.0a1-py3-none-any.whl
Requirement already satisfied: Mopidy>=3.0 in /nix/store/v4z1r0cjwnazayf7r8kynj5wg3l76lbj-mopidy-3.0.1/lib/python3.7/site-packages (from Mopidy-YouTube==3.0a1) (3.0.1)
Requirement already satisfied: Pykka>=2.0.1 in /nix/store/hw7p724agdmqlg74zlblvldawz74dw0k-python3.7-pykka-2.0.2/lib/python3.7/site-packages (from Mopidy-YouTube==3.0a1) (2.0.2)
Requirement already satisfied: requests in /nix/store/sz8jskb1qkblwbwdp91mngh9c7m3kvix-python3.7-requests-2.22.0/lib/python3.7/site-packages (from Mopidy-YouTube==3.0a1) (2.22.0)
ERROR: Could not find a version that satisfies the requirement bs4 (from Mopidy-YouTube==3.0a1) (from versions: none)
ERROR: No matching distribution found for bs4 (from Mopidy-YouTube==3.0a1)
builder for '/nix/store/jjjwxll07x0fiin90sh4mbanlhhy36vd-mopidy-youtube-3.0a1.drv' failed with exit code 1
error: build of '/nix/store/jjjwxll07x0fiin90sh4mbanlhhy36vd-mopidy-youtube-3.0a1.drv' failed

(can't figure out why it doesn't find beautifulsoup4 despite being included in propagatedBuildInputs)
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I think you might be misunderstanding me a little - mopidy has migrated to python3, and as such it does not support python2 plugins any more. The plugins which still work have been rewritten/migrated to python3. But many plugins have not been migrated, and I think that we should just remove them

needs a rebase

I think you might be misunderstanding me a little - mopidy has migrated to python3, and as such it does not support python2 plugins any more. The plugins which still work have been rewritten/migrated to python3. But many plugins have not been migrated, and I think that we should just remove them

If there's no plan to migrate the broken plugins, then please remove. Otherwise you can just mark them broken until they are in a usable state. I would just really like for package evaluation reflect the current condition of the package

At least spotify-tunigo can be marked as broken without too much thinking: upstream project is deprecated, and most features are now implemented in the mopidy-spotify plugin.

I can't figure out how to get mopidy gmusic login to work. Does anybody have any idea?

Sorry, I really let this one wither a bit - I updated, rebased, and trimmed off the bits that got merged into other PRs, so I think this ought to be good to merge now

@balsoft I just set up a new instance of mopidy, and did a mopidy gmusic login and it worked fine. Note that there's an unfortunate bug https://github.com/mopidy/mopidy-gmusic/issues/231 which causes no tracks to appear when trying to select an album/artist (e.g. in ncmpcpp, pressing "2", Google Play Music -> Albums -> etc), but playing tracks from the All tracks view still works. It was fixed between the last release and master; you can use the following overlay to use the version currently on master of mopidy-gmusic instead:
self: super:
{
  mopidy-gmusic = super.mopidy-gmusic.overrideAttrs (oldAttrs: rec {
    src = self.fetchFromGitHub {
      owner = "mopidy";
      repo = "mopidy-gmusic";
      rev = "a4a78463b9765af62dd8662d45c2f8d9718f2d63";
      sha256 = "116h7v35vy0pvkab0diwfyrf8lcpbam9can8vx5cyjqxhazigzj7";
    };
  });
}

@GrahamcOfBorg build mopidy-gmusic mopidy-youtube mopidy-mpris mopidy-somafm

@NickHu oh, now it works for me too. I guess I have somehow messed up something last time I tried it ;)

@balsoft @jpotier @jonringer @FRidh Any remaining objections or should I merge this?

Can't wait for it to be merged, one more hacky overlay removed from my config!
Thank you very much for this once again!

Result of nixpkgs-review pr 78361 1

3 packages built:
- mopidy-mpris
- mopidy-somafm
- mopidy-youtube


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 16:09:29 on 2023.07.24
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 0, errors out: 0
Original problem ID: 33005
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=33005

Problem has been resolved in 3m 0s at 16:12:29 on 2023.07.24
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 33005


[new price plan] [dashboard] Update metrics section in homepage

https://github.com/CartoDB/cartodb/issues/15435
https://projects.invisionapp.com/share/REVRCLQ38VT#/screens/402932416

Retest this please


docker networks support

This adds a new environment variable MOTO_DOCKER_NETWORK that is the name of a docker network to bind docker containers ran by moto to. This is for usage of the moto container with docker compose. By creating an overlay network in your docker compose file you can add that network name in this environment variable. This allows you to communicate with other mock services while mocking your application in docker compose.

Codecov Report

Merging #4754 (b2413fe) into master (51bb711) will increase coverage by 0.00%.
The diff coverage is 71.42%.

@@           Coverage Diff           @@
##           master    #4754   +/-   ##
=======================================
  Coverage   95.33%   95.33%
=======================================
  Files         568      570    +2
  Lines       61096    61139   +43
=======================================
+ Hits        58244    58288   +44
+ Misses       2852     2851    -1

Flag
Coverage Δ

servertests
47.43% <28.57%> (-0.01%)
:arrow_down:

test_responses
33.02% <28.57%> (+0.96%)
:arrow_up:

unittests
95.22% <71.42%> (-0.03%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

moto/awslambda/models.py
92.75% <50.00%> (-0.11%)
:arrow_down:

moto/batch/models.py
89.45% <75.00%> (-0.09%)
:arrow_down:

moto/__init__.py
98.71% <100.00%> (ø)

moto/efs/models.py
88.21% <0.00%> (-0.36%)
:arrow_down:

moto/apigateway/models.py
93.64% <0.00%> (ø)

moto/core/responses_custom_registry.py
100.00% <0.00%> (ø)

moto/core/custom_responses_mock.py
93.54% <0.00%> (ø)

moto/core/models.py
97.60% <0.00%> (+0.86%)
:arrow_up:

moto/utilities/distutils_version.py
64.28% <0.00%> (+7.14%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a688c00...b2413fe. Read the comment docs.

This makes a lot of senes, @morsecodist. Adding this variable in AWSLambda is already part of #4658, so let's wait until that one gets merged.
Afterwards we can rebase/repurpose this PR to also add the network name to Docker containers in Batch.

@bblommers makes sense, thanks sorry I missed that other PR. I will get this in batch once that's done but I will close this for now. Let me know if there is any way I can assist. Also maybe we should create some sort of docker wrapper so we don't need to add functionality in two places? It may also be relevant for ECS if it is added.

Also maybe we should create some sort of docker wrapper so we don't need to add functionality in two places?

Agreed, some DRY code would be nice, with all the configuration options that we have now!


ItemBlockGlowPanel doesn't check for a valid metadata before looking up the name

Issue description:
I am using Item Stages to stage the items, and attempting to do it via Wildcard. When doing this, the script errors. There may as well be more that do this, but this is the first item we were doing via wildcard that caused the script to error.
Steps to reproduce:
mods.ItemStages.addItemStage("test", <mekanism:glowpanel:*>);

Version:
Minecraft: 1.12.2
Forge: <IP_ADDRESS>69
Mekanism: 1.12.2-<IP_ADDRESS>0
CraftTweaker: 1.12-4.1.6
MTLib: 3.0.4
Item Stages: 1.0.34
Logs:
https://pastebin.com/xF9nWQVD

Itemstages shouldnt be calling that function with the damage wildcard value

Fixed in 108f4ddbe8d960c9f566af3330fee388c74dd400


Envoy's Python environment degradation when do multiple experiments within the same Federation

When we run multiple experiments (could be TF, then PyTorch, then old TF or PyTorch) within the same Federation, envoy's environment is started to degrade. Probably, the solution could be to create a separate environment for each experiment, or clean up the environment when experiment ended.
On Envoy when the Experiment is finished the gpu memory still allocated.

Closing this as the Interactive API has been deprecated.


P2021: Prisma Dart trying to find the wrong table name

Model Setup
model Game {
  id String @id @default(uuid()) @map("game_id")

  leftTeam  String
  leftScore  Int    @default(0)

  rightTeam String
  rightScore  Int    @default(0)

  @@map("games")
}

Problem
When querying any model, prisma throws a P2021 error.
Stacktrace
Information got from my recoverer
Exception: [{error: KnownError { message: "The table `main.games` does not exist in the current database.", meta: Object {"table": String("main.games")}, error_code: "P2021" }, user_facing_error: {is_panic: false, message: The table `main.games` does not exist in the current database., meta: {table: main.games}, error_code: P2021}}]

Expected

Prisma should be trying to find table games, instead of main.games

Additional Info

Changing the table name to default Game does not work, it still tries to search for main.Game instead of Game
The error happens even if I clean every prisma directory and rerun pnpx/bunx prisma migrate dev again.

Thanks for any help, Sun.

@SunP04 Okay, may I ask which database you are using? So that I can investigate, it would be best to post the query statement.

@medz using sqlite right now.

it would be best to post the query statement.

Any query is causing that issue, so any should work as example.
For future reference, that's my generator/provider setup
generator client {
  provider = "dart run orm"
  output = "../lib/providers/prisma"
}

datasource db {
  provider = "sqlite"
  url      = env("DATABASE_URL")
}

New context and resolutions:
Repo: LiveScore
Path issues:
When using prisma dart, I assumed it also got the path from .env but it didn't, so it created the shown error here (searching for the wrong table).
Aftermath:
Another error showed up when I corrected that problem, the BinaryEngine is never considered to be "ready" and when I call any method or query or just call PrismaClient#$connect.
Stacktrace:

Code: await prisma.$connect();

Unhandled exception:
Exception: Prisma binary query engine not ready
#0      BinaryEngine._serverEndpoint.<anonymous closure> (package:orm/engines/binary.dart:114:13)
#1      RetryOptions.retry (package:retry/retry.dart:131:24)
<asynchronous suspension>
#2      BinaryEngine._serverReady (package:orm/engines/binary.dart:121:18)
<asynchronous suspension>
#3      BinaryEngine._internalStart (package:orm/engines/binary.dart:99:19)
<asynchronous suspension>
#4      BinaryEngine.start (package:orm/engines/binary.dart:60:18)
<asynchronous suspension>
#5      main (file:///C:/Users/pedro/Desktop/Coding/Dart/livescore/bin/server.dart:26:3)
<asynchronous suspension>

@SunP04
import 'dart:io';

import 'env.dart';
import 'package:livescore/providers/prisma/client.dart';
import 'package:path/path.dart' as p;

final class PrismaConfig {
  final PrismaClient client;

  const PrismaConfig({required this.client});

  factory PrismaConfig.connect(EnvConfig env) {
    final fullPath = p.join(Directory.current.path, "prisma", env.dbPath);
    final path = p.normalize(fullPath);

    final client = PrismaClient(datasourceUrl: path);

    return PrismaConfig(client: client);
  }
}

You made a serious mistake, that is, you did not follow the Prisma Connection URL protocol rules. 👉 https://www.prisma.io/docs/orm/overview/databases/sqlite

I think the URL you finally completed on the Window should be in the style of C:\\a/b/c/d.db, but it actually needs to be file:C:\\a/b/c/d.db

According to your code, you only need to change line 16 to:

++ final client = PrismaClient(datasourceUrl: 'file:$path');
-- final client = PrismaClient(datasourceUrl: path);

Then make sure env.dbPath is a path relative to the prisma/ directory.

@SunP04
import 'dart:io' show File;

String resolvePrismaConnectURL(String datasourceUrl) {
  final url = Uri.tryParse(datasourceUrl);
  const ptotocols = ['file', 'mysql', 'mongodb', 'sqlserver'];

  if (url == null || !ptotocols.contains(url.scheme)) {
    throw StateError('Invalid Prisma connection URL');
  } else if (url.scheme == 'file') {
    final sqliteDatabaseFile = File.fromUri(url);
    if (sqliteDatabaseFile.existsSync()) {
      return 'file:${sqliteDatabaseFile.path}';
    }

    throw StateError('SQLite database file not found');
  }

  return url.toString();
}

I'll give you a method I often use to verify the URL, which can ensure that your database URL is correct.

@medz
aaah, didn't know I actually needed to add the scheme on it, I thought it inferred from the provider type
Just pushed those changes to git and they're running now, it was just that error.

I'll give you a method I often use to verify the URL, which can ensure that your database URL is correct.

I added that method in my lib/shared/path/resolve_protocol.dart and there is a reference to you there, since I didn't write the code :d
Thanks for all the help

Since the problem is resolved, I'll just close the issue and I don't know if there is a solved tag or not, but it's solved too.

@SunP04 https://gitlab.com/SunP04/livescore/-/blob/dev/bin/config/prisma.dart?ref_type=heads#L13
I observed that you used the Prisma Datasource URL incorrectly. resolvePrismaFileProtocol function will return the correct Prisma Connection URL, you don't need to deal with it.
import 'package:livescore/shared/path/resolve_protocol.dart';

import 'env.dart';
import 'package:livescore/providers/prisma/client.dart';

final class PrismaConfig {
final PrismaClient client;

const PrismaConfig({required this.client});

factory PrismaConfig.connect(EnvConfig env) {
-- final path = resolvePrismaFileProtocol(env.dbPath);
++ final path = resolvePrismaFileProtocol(env.DATABASE_URL);
-- final client = PrismaClient(datasourceUrl: "file:$path");
++ final client = PrismaClient(datasourceUrl: url);

return PrismaConfig(client: client);
}
}


Cannot perform ng new after upgrade to 1.4.5 - Error: tree.branch is not a function

Bug Report or Feature Request (mark with an x)
- [x] bug report
- [ ] feature request

Versions.
    _                      _                 ____ _     ___
   / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
  / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
 / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
/_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
               |___/
@angular/cli: 1.4.5
node: 8.5.0
os: linux x64

Repro steps.

npm uninstall -g @angular/cli
npm cache verify
npm install -g @angular/cli@latest
ng new my-project

The log given by the failure.

Error: tree.branch is not a function
tree.branch is not a function
Desired functionality.
After updating to v1.4.5 the user should be able to generate a new project.

Closing as restarting my terminal fixed the problem.


FileURLRetrievalError when installing

I'm submitting a ...

[O] bug report
[ ] feature request

What is the current behavior?
I've encountered this error, which is already a closed issue.
gdown.exceptions.FileURLRetrievalError: Failed to retrieve file url:

        Cannot retrieve the public link of the file. You may need to change
        the permission to 'Anyone with the link', or have had many accesses.
        Check FAQ in https://github.com/wkentaro/gdown?tab=readme-ov-file#faq.

You may still be able to access the file from the browser:

        https://drive.google.com/uc?id=1PD_85XrMIq3ZgJF4sK3e0Ot3jR6J7Vkz

but Gdown can't. Please check connections and permissions.
Downloading example trajectories complete

Could you fix it?

Motivation for Change
Please tell us about your environment:

Version:
Browser:
Language:

I think this might be related to Google's request frequency limitation but the link is still valid. I also met this problem. But I manually download the folder and send it to the server through scp. This should fix it but a little bit more time-consuming.

Thank you!


Support decimal label rate

Make label_rate be of type float in Hubert pretraining to support decimal label rate (e.g. 33.3Hz, otherwise verify_label_lengths() will give warnings if the undelying label rate is 33.3Hz)
Before submitting

[ ] Was this discussed/approved via a Github issue? (no need for typos, doc improvements)
[x] Did you read the contributor guideline?
[ ] Did you make sure to update the docs?
[x] Did you write any new necessary tests?

What does this PR do?
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

@dianaml0 Any chances to merge this?

Thanks for your reply. I think my current description is shown as "make label_rate be of type float in Hubert pretraining to support decimal label rate (e.g. 33.3Hz, otherwise verify_label_lengths() will give warnings if the undelying label rate is 33.3Hz)"
What do you want me to change?

Thanks for your reply. I think my current description is shown as "make label_rate be of type float in Hubert pretraining to support decimal label rate (e.g. 33.3Hz, otherwise verify_label_lengths() will give warnings if the undelying label rate is 33.3Hz)"
What do you want me to change?

@freewym no worries, I updated the title and description

@dianaml0 Do we need to run another round of test? I notice that the lint error has been fixed in main.

@dianaml0 Do we need to run another round of test? I notice that the lint error has been fixed in main.

@freewym yes thanks, just updated the branch so tests should rerun

@dianaml0 Failed on python 3.8... Probably just a bad luck and needs a re-run

@freewym just triggered a re-run

@dianaml0  The internal tests failed. Not sure if it's related.

@freewym I'm rerunning the internal tests now as well

@freewym I'm rerunning the internal tests now as well

@dianaml0 how was the tests going?


Fixed typo from my to by

@btford Just noticed a small typo and here is the fixed PR.

Landed as d8e4deea04c7e600fda67382fa89188e989d0abe. Thanks!


Update dashboard settings page to new designs

Use new design system components to update settings page.

All form components should be used from the design system.
Follow figma specs here: https://www.figma.com/file/bMhG3KyrJF8vIAODgmbeqT/Design-System?node-id=467%3A13745

Unable to have multiple logos. When I upload a 2nd logo it replaces the first rather than appear as another logo option
https://share.getcloudapp.com/04uJP64W

@csossi Is this issue new with this specific change, or does it also happen on main / the stories-new site?

@csossi weird! I just tested staging and the branch and they're working as expected. Can you open your console log and show what your API response is when that POST and GET happen?

I just tested it as well and saw that it was adding a new one, but maybe mine is different since I already started with an image loaded in first.

Yeah i'm really curious about this. I went back and reset my entire environment so I started with a blank slate and it's still working. 🤔

@csossi Is this issue new with this specific change, or does it also happen on main / the stories-new site?

just checked Main, @swissspidy  - happening there as well. Cleared cache and checked PC/Chrome and PC/Opera as well as Mac/Chrome - all with the same "replace" result

@csossi Is this issue new with this specific change, or does it also happen on main / the stories-new site?

just checked Main, @swissspidy - happening there as well. Cleared cache and checked PC/Chrome and PC/Opera as well as Mac/Chrome - all with the same "replace" result

thanks for testing. since this happens on main it's clearly not a bug caused by this change here and would warrant its own ticket. it should obviously not block QA on this change. any other findings there?

All good other than that, @swissspidy - setting this to "pass"


Add EBCDIC writer

Hi, would it be possible to add to Cobrix the possibility to write EBCDIC file given the Copybook?
Thanks

Not at the moment. There are plans to add it, but now sure when we start implementing it.
Here is the issue to track: https://github.com/AbsaOSS/cobrix/issues/186


Support LibraryManagedAttributes<TComponent, TAttributes> JSX namespace type

Fixes #23812
Allows, eg:
class Component extends ReactComponent {
    static propTypes = {
        foo: PropTypes.number,
        bar: PropTypes.node,
        baz: PropTypes.string.isRequired,
    };
    static defaultProps = {
        foo: 42,
    }
}

const a = <Component foo={12} bar="yes" baz="yeah" />;
const b = <Component foo={12} />; // Error, missing required prop bar
const c = <Component bar="yes" baz="yeah" />;
const d = <Component bar="yes" baz="yo" bat="ohno" />; // Error, baz not a valid prop
const e = <Component foo={12} bar={null} baz="cool" />; // bar is nullable/undefinable since it's not marked `isRequired`
const f = <Component foo={12} bar="yeah" baz={null} />; // Error, baz is _not_ nullable/undefinable since it's marked `isRequired`

when JSX.LibraryManagedAttributes<TComponent, TAttributes> is appropriately defined. Thanks to conditional types, this method of supporting propTypes and defaultProps allows definition authors a ton of freedom in how the static types need to be transformed before they are checked against what the user wrote. (Allowing customization of, for example: how conflicts between provided props and inferred props are handled, how inferences are mapped, how optionality is handled, and how inferences from differing places should be combined)
As an aside, you can fully implement the functionality of both InstrinsicAttributes and InstrinsicClassAttributes using this new type entrypoint, so in a way it obsoletes them.
Feel free to 🚲 🏠  with the name and give feedback; the actual implementation is relatively simple. @DanielRosenwasser you probably have some opinions here, right? 😄

Could you elaborate in this PR on what LibraryManagedAttributes is intended to do and give some specific implementations examples?

@jaredpalmer The Props type parameter should be the "internal" props (so what you read), while the props returned by the type alias should be the "external" props (the ones you write in a tag). So, instead of
interface Props {
  thing?: string; // still optional
}

class Thing extends React.Component<Props> {
   static defaultProps = {
      thing: 'hello'
   }

  render() {
    console.log(this.props.thing) // inferred because of defaultProps, no ! needed
    // ...
 }
}
// ..
<Thing /> // works

you'd have
interface Props {
  thing: string; // note: not optional within class, but is optional when writing due to the default
}

class Thing extends React.Component<Props> {
   static defaultProps = {
      thing: 'hello'
   }

  render() {
    console.log(this.props.thing) // inferred because of defaultProps, no ! needed
    // ...
 }
}
// ..
<Thing /> // works

or at least that's what makes sense to me - since the Props generic param is the type of the first argument to the factory/class (which includes all defaults).

got it so it will work like Flow. cool!

This is indeed awesome! In the meantime I wrote an article for React consumers struggling with this "deal breaker" ✌ https://medium.com/@martin_hotell/react-typescript-and-defaultprops-dilemma-ca7f81c661c7

@mhegazy I've synchronized this branch with master; can I get this reviewed?

We will need to update https://github.com/Microsoft/TypeScript-Handbook/blob/master/pages/JSX.md

What is the expected behaviour when the props type is a union? Is this expected?
{
    type Props = { shared: string } & (
        | {
              type: 'foo';
              foo: string;
          }
        | {
              type: 'bar';
              bar: string;
          });
    class Component extends ReactComponent<Props> {
        static defaultProps = {
            shared: 'yay',
        };
    }

    <Component type="foo" />; // Expected error, got none
    // Unexpected error
    // Property 'foo' does not exist on type 'Defaultize<Props, { shared: string; }>'.
    <Component type="foo" foo="1" />;
}

@mhegazy Is it an issue worth tracking? If so, I'll open a separate issue.

yes please.

@OliverJAsh it's probably also worth noting that while this code is in typescript, there won't be any changes until the react .d.ts is updated to use the new jsx namespace entrypoint; so until that happens defaultProps still won't do anything.

@mhegazy https://github.com/Microsoft/TypeScript/issues/25503.

For any questions/issues, please file a separate follow-up issue.


Support for pathlib.Path.link_to()

Python 3.8 has added a new method to pathlib library: Path.link_to() for creating hard links (https://docs.python.org/3/library/pathlib.html#pathlib.Path.link_to). I think that it is not supported by pyfakefs yet (v. 4.3.3).
It would be nice to mock this method since it is an easy way to create hard links.
Maybe it would be a good idea to include a FakeFilesystem.create_link() method for creating hard links (similar to FakeFilesystem.create_symlink() for soft links).
Thank you.

Good point, thank you!

@JD-Veiga - shall work in master now. Do you need a released version?

Excellent and quick work! I have installed it from master. Thanks a lot. Happy new year!

Last sensible thing I did this year ;) Happy New Year to you, too!

Hi,
Everything is running fine until I have updated one of the dependencies of my code this morning. The update has installed pathlib2 and, tough I do not use directly it in my project, pyfakefs imports pathlib2 now. As a consequence, Path.link_to() has vanished because of: https://github.com/jmcgeheeiv/pyfakefs/blob/846ec97c0efe2f819f883f26ae90247e4ea55aee/pyfakefs/fake_pathlib.py#L126
I have uninstalled pathlib2 from my virtualenv but it is not a permanent solution for everyone everywhere.
Is there a way of adding link_to() to pathlib but not to pathlib2? Maybe a _FakeAccessor for pathlib and a different one for pathlib2? Maybe raising an exception when pathlib2.link_to() is called?
Thank you again.

Hi,
Everything is running fine until I have updated one of the dependencies of my code this morning. The update has installed pathlib2 and, tough I do not use directly it in my project, pyfakefs imports pathlib2 now. As a consequence, Path.link_to() has vanished because of: https://github.com/jmcgeheeiv/pyfakefs/blob/846ec97c0efe2f819f883f26ae90247e4ea55aee/pyfakefs/fake_pathlib.py#L126
I have uninstalled pathlib2 from my virtualenv but it is not a permanent solution for everyone everywhere.
Is there a way of adding link_to() to pathlib but not to pathlib2? Maybe a _FakeAccessor for pathlib and a different one for pathlib2? Maybe raising an exception when pathlib2.link_to() is called?
Thank you again.

Ok, I had thought pathlib2 is not used anymore (it is definitely not needed in Python 3.8). Making a separate accessor for pathlib2 is probably not worth it. I could just remove the check for pathlib2 and let it fail if you use pathlib2 instead of pathlib.
This is probably the best option, because if you want to use link_to, you cannot use pathlib2, or you would get the same exception.

Ok, I had thought pathlib2 is not used anymore (it is definitely not needed in Python 3.8). Making a separate accessor for pathlib2 is probably not worth it. I could just remove the check for pathlib2 and let it fail if you use pathlib2 instead of pathlib.
This is probably the best option, because if you want to use link_to, you cannot use pathlib2, or you would get the same exception.

I think so now that Python2 is in EOL but... everything comes back... in subtle ways... Thank you once again.

I think so now that Python2 is in EOL but... everything comes back... in subtle ways... Thank you once again.

Ok, done. Yeah, I see Python2 used still quite a bit... seems to be unkillable. Though using pathlib2 with Python 3.8 really doesn't make much sense - pathlib2 has stopped developing a couple of years ago, while pathlib is changing with each Python version.

Ok, done. Yeah, I see Python2 used still quite a bit... seems to be unkillable. Though using pathlib2 with Python 3.8 really doesn't make much sense - pathlib2 has stopped developing a couple of years ago, while pathlib is changing with each Python version.


V11 feature request:  pre-package the compendium packs in folders

Foundry V11 will add compendium folders and therefore allow the module to organize the compendium packs better.
Currently, there are 73 packs, which is a lot of packs.  They take up so much space that scrolling down the list is time-consuming, even though it's necessary sometimes - particularly for non-pf2e compendiums (as the pf2e content is more easily accessed through the compendium browser).  It would be great to collect many of them together, grouped up and divided among folders.
Note that, based on recent V11 development commentary, systems and modules will not be able to include such folders as part of the manifest;  instead, they'll have to add it to some initialization/migration script for now.
The actual division of folders is something that should be given more consideration, but my initial suggestion is to simply divide them by type and subtype.  This means one folder for all Actors, one for all Items, one for all Journal entries, etc.  This can also be a bit less simple, with subtypes - for example, one folder for all Player Characters, one for all NPCs, one for Feats, one for Actions, etc.
An alternative division to suggest would be by source category:  one folder for all "core series" rulebooks, one oflder for all adventure path content, etc.  However, that division may require splitting up some of the packs - e.g. "Feats" which currently has all feats from all sources.

We'll likely just go back to the same organizational scheme we have in Foundry 0.7

Currently not possible in V11

Atro mentioned a one-time script the first time a world is loaded to create and assign compendia to folders. A potential solution


Show complete docstring on hover

What we have:

which only shows a very terse signature. We need the full docstring instead:

as in Juptyer:
https://user-images.githubusercontent.com/5494367/131711331-b0e085f1-1290-4177-b068-44b612aa25e3.mov
Version: 1.59.1
Commit: 3866c3553be8b268c8a7f8c0482c0c0177aa8bfa
Date: 2021-08-19T11:53:52.479Z
Electron: 13.1.7
Chrome: 91.0.4472.124
Node.js: 14.16.0
V8: 9.1.269.36-electron.0
OS: Darwin x64 20.6.0

/extPython
It actually looks like extension issue and it's not providing full information for hovers (or picks that text from some other place).
You can see in gif attached to issue #112373 - hovers support can have a ton of text.


terribly slow: format="json", stream=False, please advise

I appreciate great work achieved with ollama.  I see a lot of potential of use.
However, when I tested.  I found that the generate and chat function takes way too long time to response, when I set format="json" and stream=False.  Speed normal with non-json mode and stream.  Please advise.  many thanks.

Hey, I have the same behaviour, any clue on how you solved it ?


Shoot conditions lastUpdateTime is no longer updated continuously

How to categorize this PR?

/area scalability robustness
/kind enhancement
/priority normal
What this PR does / why we need it:
The shoot's .status.conditions[].lastUpdateTime is no longer continuously updated to prevent spamming etcd with too many unnecessary updates.
Special notes for your reviewer:
If the gardenlet does not renew its lease anymore then the GCM will, after a certain threshold, set the shoot conditions to Unknown to indicate that the displayed information is most likely outdated.
Release note:

The shoot's `.status.conditions[].lastUpdateTime` is no longer continuously updated. Note that if the gardenlet does not renew its lease anymore then the gardener-controller-manager will, after a certain threshold, set the `Shoot`'s conditions to `Unknown` to indicate that the displayed information is most likely outdated.

/assign @amshuman-kr @shreyas-s-rao @vlerenc

Thanks @rfranzke. When we merge it/deploy it to dev, we should check whether it indeed behaves as expected and the no longer updated .status.conditions[].lastUpdateTime will not cause trouble in the components.
WDYT if we no longer update .status.conditions[].lastUpdateTime for shoots:

@grolu for the dashboard
@wyb1 @mliepold for the availability monitoring

/invite @grolu @petersutter @wyb1 @mliepold

we have no logic that depends on .status.conditions[].lastUpdateTime.
This would be the only effect (Last Updated shows nothing), however we have a PR ready to remove this field https://github.com/gardener/dashboard/pull/810

Btw there is already a condition builder which checks if condition really needs to be updated e.g. https://github.com/gardener/gardener/blob/2fb3b07c5c741b432889ce155a89a82cd88532b1/pkg/gardenlet/controller/seed/seed_lease_control.go#L101-L120

Btw there is already a condition builder which checks if condition really needs to be updated e.g.

Yes, I know, actually I started using it, but then I faced that the botanist/health_check.go would be adapted as well, resulting in a larger refactoring. I have a WIP branch for it and will continue separately.


Why tikv require "nodelalloc" for ext4?

The document requires nodelalloc to be configured, but not explained. I'm curious why, someone gives me a pointer?

@ethercflow will answer it

Two reasons:

security
https://lwn.net/Articles/322823/;
performance
The default ext4 mount option is delalloc - delayed on-disk block allocation for writes. This can cause a bottleneck in the system under high write conditions resulting in slow io drain to disk;

I should say your answer causes more confusion than clarification.
For the security part, the bug referenced by the article is fixed ten years ago, and I believe rocksdb would call fsync() at proper time to ensure data security.
For the performance part, as I understand, the option delalloc would cause ext4 to delay block allocation as possible to batch writes, this would improve performance, not the opposite. Also from the article:
"Delayed allocation" means that the filesystem tries to delay the allocation of physical disk blocks for written data for as long as possible. This policy brings some important performance benefits.

So is this nodelalloc requirement decided by test or some deduction? I might need more materials.

I remember that we used delalloc before but met data lost on VM or cloud instance crashed, so we decide to use nodelalloc.

For the security part, although it has been fixed, some users may still use an older kernel version.
For the performance part, you can get more detailed information from: https://access.redhat.com/solutions/472273.

Unfortunately I don't have access to a RedHat subscription but I understand your rationale. Thanks for your patience.

You're welcome, welcome to discuss  :)


Edit: TV5 (Philippines)

Channel ID (required)
TV5.ph
Channel Name
TV5 PH
Alternative Names
5 Channel
Network
TV5 Network, Inc.
Owners
MediaQuest Corporation
Country
PH
Subdivision
PH-MNL
City
Manila
Broadcast Area
Quezon City
Languages
tag;eng
Categories
news; ent
NSFW
None
Launched
No response
Closed
No response
Replaced By
No response
Website
https://tv5.com.ph
Logo
No response
Notes
No response

Duplicate of https://github.com/iptv-org/database/issues/14952


thrimshim: use send_file to serve templates from database

I don't claim to understand why this works, but this makes downloading the thumbnail templates (to preview on the thumbnail management page, or to select the "hole" in the advanced crop settings in the editor) way faster. Something to do with how flask is chunking the memoryview object to serve.
Applying this changed the timings to download "fiddling.png" from 818ms waiting and 6770ms receiving, to 777ms waiting and 14ms receiving.
Resolves #458

It will not spot all Python bugs but running a linter such as Pyflakes before pushing is good practice.

ekim has a better fix (bytes(image) apparently is enough), closing


[SPARK-19265][SQL] make table relation cache general and does not depend on hive

What changes were proposed in this pull request?
We have a table relation plan cache in HiveMetastoreCatalog, which caches a lot of things: file status, resolved data source, inferred schema, etc.
However, it doesn't make sense to limit this cache with hive support, we should move it to SQL core module so that users can use this cache without hive support.
It can also reduce the size of HiveMetastoreCatalog, so that it's easier to remove it eventually.
main changes:

move the table relation cache to SessionCatalog
SessionCatalog.lookupRelation will return SimpleCatalogRelation and the analyzer will convert it to LogicalRelation or MetastoreRelation later, then HiveSessionCatalog doesn't need to override lookupRelation anymore
FindDataSourceTable will read/write the table relation cache.

How was this patch tested?
existing tests.

cc @yhuai @gatorsmile

Test build #71522 has started for PR 16621 at commit a7845cc.

Test build #71522 has finished for PR 16621 at commit a7845cc.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class QualifiedTableName(database: String, name: String)
class FindHiveSerdeTable(session: SparkSession) extends Rule[LogicalPlan]

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71522/
Test FAILed.

Test build #71549 has started for PR 16621 at commit 98a5483.

Start the review. Will remove this comment when the review is finished.

Test build #71549 has finished for PR 16621 at commit 98a5483.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class QualifiedTableName(database: String, name: String)
class FindHiveSerdeTable(session: SparkSession) extends Rule[LogicalPlan]

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71549/
Test FAILed.

Test build #71567 has started for PR 16621 at commit 919aaa2.

Could we rename SimpleCatalogRelation to UnresolvedCatalogRelation? The current name looks very confusing to me.

can we do it later? We are going to merge CatalogRelation implementations and unify the table relation representations soon.

Test build #71567 has finished for PR 16621 at commit 919aaa2.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class QualifiedTableName(database: String, name: String)
class FindHiveSerdeTable(session: SparkSession) extends Rule[LogicalPlan]

Sure. No problem.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71567/
Test FAILed.

Test build #71572 has started for PR 16621 at commit 2883c8b.

Test build #71574 has started for PR 16621 at commit bbccdae.

No more comments. It looks pretty good! Let us see whether all the test cases can pass.

Test build #71576 has started for PR 16621 at commit d636389.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71576/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71574/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71572/
Test FAILed.

Test build #71583 has started for PR 16621 at commit 096fcc8.

Test build #71583 has finished for PR 16621 at commit 096fcc8.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class QualifiedTableName(database: String, name: String)
class FindHiveSerdeTable(session: SparkSession) extends Rule[LogicalPlan]

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71583/
Test PASSed.

LGTM

Thanks! Merging to master.