Add Kueue Docsite

What type of PR is this?
/kind documentation

What this PR does / why we need it:
This PR adds the hugo docsite for Kueue
Which issue(s) this PR fixes:

Partially Fixes 377. We still need to get the subdomain kueue.sigs.k8s.io before we can close.
Special notes for your reviewer:

/ok-to-test

Can you fix the tests?

/retest

Flaky test #511


Help integrating - Etekcity EFS-A591S-KUS HR Smart Fitness Scale

Hi,
I have the EFS-A591S-KUS scale which I assumed would work with this integration. It is bluetooth + Wifi (ie, scale -> cloud -> cloud account - app) and works with ve sync app.
Your integration successfully created the device* but both sensors are permanently "Unknown".
I thought that this might just be a matter of sniffing the BLE traffic and figuring out in which format the data is being sent and doing a PR, but now that I'm looking at the logs, I see No Bluetooth adapters found, so maybe I'm actually doing something wrong with the bluetooth proxy setup?
2024-11-24 10:45:45.986 INFO (MainThread) [homeassistant.components.sensor] Setting up etekcity_fitness_scale_ble.sensor
2024-11-24 10:45:45.986 DEBUG (MainThread) [custom_components.etekcity_fitness_scale_ble.sensor] Setting up scale sensors for entry: 01JDE4XT2BGRAXQQNBETMZV95P
2024-11-24 10:45:45.986 DEBUG (MainThread) [custom_components.etekcity_fitness_scale_ble.coordinator] Setting display unit to: LB
2024-11-24 10:45:45.986 DEBUG (MainThread) [custom_components.etekcity_fitness_scale_ble.sensor] Adding sensor to Home Assistant: sensor.etekcity_apex_48_e7_29_33_21_be_weight
2024-11-24 10:45:45.987 DEBUG (MainThread) [custom_components.etekcity_fitness_scale_ble.sensor] Restoring previous state for sensor: sensor.etekcity_apex_48_e7_29_33_21_be_weight
2024-11-24 10:45:45.987 INFO (MainThread) [custom_components.etekcity_fitness_scale_ble.sensor] Sensor added to Home Assistant: sensor.etekcity_apex_48_e7_29_33_21_be_weight
2024-11-24 10:45:45.987 DEBUG (MainThread) [custom_components.etekcity_fitness_scale_ble.sensor] Adding sensor to Home Assistant: sensor.etekcity_apex_48_e7_29_33_21_be_impedance
2024-11-24 10:45:45.987 DEBUG (MainThread) [custom_components.etekcity_fitness_scale_ble.sensor] Restoring previous state for sensor: sensor.etekcity_apex_48_e7_29_33_21_be_impedance
2024-11-24 10:45:45.987 INFO (MainThread) [custom_components.etekcity_fitness_scale_ble.sensor] Sensor added to Home Assistant: sensor.etekcity_apex_48_e7_29_33_21_be_impedance
2024-11-24 10:45:46.083 DEBUG (MainThread) [custom_components.etekcity_fitness_scale_ble.coordinator] Starting ScaleDataUpdateCoordinator for address: 48:E7:29:33:21:BE
2024-11-24 10:45:46.083 DEBUG (MainThread) [custom_components.etekcity_fitness_scale_ble.coordinator] Initializing new EtekcitySmartFitnessScale client
2024-11-24 10:45:46.083 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up etekcity_fitness_scale_ble platform for sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 365, in _async_setup_platform
    await asyncio.shield(awaitable)
  File "/config/custom_components/etekcity_fitness_scale_ble/sensor.py", line 168, in async_setup_entry
    await coordinator.async_start()
  File "/config/custom_components/etekcity_fitness_scale_ble/coordinator.py", line 89, in async_start
    await self._async_start()
  File "/config/custom_components/etekcity_fitness_scale_ble/coordinator.py", line 75, in _async_start
    await self._client.async_start()
  File "/usr/local/lib/python3.12/site-packages/etekcity_esf551_ble/parser.py", line 118, in async_start
    await self._scanner.start()
  File "/usr/local/lib/python3.12/site-packages/etekcity_esf551_ble/bluetooth.py", line 81, in start
    await self._backend.start()
  File "/usr/local/lib/python3.12/site-packages/bleak/backends/bluezdbus/scanner.py", line 173, in start
    adapter_path = manager.get_default_adapter()
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/bleak/backends/bluezdbus/manager.py", line 353, in get_default_adapter
    raise BleakError("No Bluetooth adapters found.")
bleak.exc.BleakError: No Bluetooth adapters found.

* I'm using an esp32 bluetooth proxy and the initial setup flow showed all possible BLE MAC addresses. When I initially set up with the incorrect device I got "Unknown error occurred", so I assumed that this was due to trying to read attributes from a device that didn't support them. Then "turned the scale on" and chose the correct MAC address and it worked. However, further testing shows that the "Unknown error occurred" was due to selecting "Calculate body composition metrics" and occurred even with the Etekcity scale, and that I'm able to set a scale device with any BLE device.

In other words, the fact that this initialized correctly doesn't mean the scale is somehow supported.
Though maybe "Calculate body composition metrics" helps to enforce that it's a supported scale, and the error here is more telling.
FWIW, a filter on the MAC address would make things easier. My proxy was picking up a few dozen devices. Presumably all etekcity scales start with the same octets? FWIW, mine is 48:E7:29:33:21:BE.

This is my first attempt at using the esphome bluetooth proxy, but I believe I'm doing everything correct. Other integrations seem to be detecting bluetooth devices (for example, ibeacon popped up as an integration, and etekcity successfully sees the various MAC addresses).
However, I continue to get the "no adapters found" error from etekcity integration.
I note in the stack trace that bleak is called by this integration directly (as opposed to via a HA API). I suspect that the HA Bluetooth API, which also appears to use Bleak, maybe does some extra abstraction to support proxies?
Maybe the etekcity_esf551_ble package should be using the HA APIs instead? Which brings up an interesting point because, AFAIK, HA wants integrations to be a thin layer on top of a "generic" package (which is exactly what etekcity_fitness_scale_ble + etekcity_esf551_ble is). However, requiring the use of HA's implementation of Bleak would make the underlying package non-generic.

Hi @jamesshannon,
I'm not really familiar with the bluetooth proxy feature, so I don't know if it would work with my integration. Is it just straightforward plain proxying of BT traffic from devices to ESPHome to Home Assistant over BT as is? I mean, is HA just oblivious to it being a proxy, seeing it just as if it's the actual device? Otherwise I don't think it would work with the integration, as it wasn't designed for that but for direct BT connection to the scale.
Did you try it without the proxy?
If you sniff and capture the relevant BT traffic between the scale and the VeSync app on your phone, then I can give it a look and see if the protocol your model uses is similar to the one used by the ESF-551. If it is then we can rule that out and if not then I can try to see if and how I can maybe add support for it too.

Regarding the HA APIs - I don't really like that solution because just like you said it would make the underlying package non-generic and I don't want it to be tied to HA specifically. It's just a client for communicating and working with the scale. This integration uses it for HA, but the way I see it there's no reason for it to not be used for other platforms or projects or whatever anyone might want to use it for.

Hi.

the way I see it there's no reason for it to not be used for other platforms or projects or whatever anyone might want to use it for.

Yeah. It totally appreciate that perspective. That's the way I'd do it, and I believe it's a HA requirement for integrations (though wouldn't apply to yours as it's via HACS).
Which is why the need to use their bleak BT wrapper is so interesting. Because if you use it, then you're not making a generic package. (I say need because I assume at this point that it's required, and the source of the problem.)
Though I guess you could  create etekcity_esf551_ble to do dependency injection? (Ie, when you instantiate the client you first get the HA BT wrapper and then pass that in instantiation; if it's not passed then the connection is established normally.
As for the other questions -- my HA instance is virtualized on a NAS, which doesn't have onboard BT. I could plug in a bluetooth dongle to the single USB port (after getting a hub), but the server is in the basement. The bluetooth proxy is just a proxy via ESPHome. I think that at most layers, HA is oblivious, though I'm sure there is some code at the lower levels that specifically interacts with ESPHome proxies -- proxy support is built-in to HA and I assume it presents most of the BT API stack with a combined view of BT traffic. THat's probably some of the reasoning for the wrapper.
Considering the error, I'm don't think decoding the scale traffic adds anything at this point. I need to solve the error first. I'll try tweaking with the code and see if it suddenly works... or at least gets beyond the error.

Though I guess you could create etekcity_esf551_ble to do dependency injection? (Ie, when you instantiate the client you first get the HA BT wrapper and then pass that in instantiation; if it's not passed then the connection is established normally.

I think it's not just the issue of the library not being generic. IIRC I couldn't actually use HA's BT scanner singleton even before I extracted the non-HA logic to the separate library. I started with a little POC discovering and connecting to the scale and just printing the data to the log, and at that point I was trying to make use of the HA wrapper but had a hard time getting it to work properly with the scale. I don't remember the precise details as it's been a few months now, but I think it was due to the BleakScanner (which I think is used by the HA wrapper) relying on the presence of some field of the BT advertisement that arrives empty in the case of the scale (at least for the ESF-551 model), which caused HA not to reconnect to the scale when it's stepped on and wakes up. I actually couldn't even use BleakScanner itself, even directly and not through HA's wrapper, and had to write my own slightly modified alternative. I need to take another look to be sure, but I think that was the reason behind the AdvertisementReceiver class I have in the library.
Anyway, did you have any luck trying to solve the error?
I think I might have some ESP32s lying around somewhere, so maybe over the weekend f I can find it then I can try looking into the ESPHome BT proxy thing and see if I can figure it out and maybe get it to work.


Export To Systemd

When I have a .env file, foreman is ending up with ExecStart on the Environment line, like this:
Environment="PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games" "RAILS_ENV=uat" "RACK_ENV=uat" ExecStart=/bin/bash -lc 'bash -lic 'bin/sidekiq''
This breaks restarting it.  It should be:
Environment="PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games" "RAILS_ENV=uat" "RACK_ENV=uat" ExecStart=/bin/bash -lc 'bash -lic 'bin/sidekiq''

@jasonivers I think you've mistyped the "it should be" part.
It should be something like the following instead:
Environment=PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
Environment=RAILS_ENV=uat
Environment=RACK_ENV=uat
ExecStart=/bin/bash -lc 'bash -lic bin/sidekiq'

I see exactly the same issue for the few recent days.

I guess this commit introduced regression: https://github.com/ddollar/foreman/commit/c7edf6490b6ccf02df2de9e03d76b1fb1a8df63b
No idea if this one contributed to that too: https://github.com/ddollar/foreman/pull/652

Anyone up for writing a patch and a test case so this doesn't regress again?

I can take a look. Any idea how to write a test for this?
24 янв 2017 г. 6:19 PM пользователь "David Dollar"<EMAIL_ADDRESS>написал:

Anyone up for writing a patch and a test case so this doesn't regress
again?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ddollar/foreman/issues/664#issuecomment-274833645,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAM0GVdz0Fk6Y-QUAJtxb8W1mCW6omEuks5rVhabgaJpZM4Lpw7E
.

Thanks guys for the great work, you might want to remove the gem 0.83 since you removed the release from git

When can we expect this to be released?

Thank you for coding the fix... will it be released any time soon?

thank you so much 👍


How to reset EndDate programatically?

I have page with dropdown of values and start date and end date field. When the user first view the page, start date/end date is default to today's date and user can only select first date of last month, and today's date as end date. Now when user selects certain values from dropdown, i want to allow user to select future date in end date instead of just today's date that i set initially. I tried using 'setEndDate', tried destroying and setting end date but it still doesn't allow user to choose future date.
Any idea how i can set end date pragmatically?
Datepicker version used
1.6.4

I had a similar issue and this solution worked for me: https://github.com/uxsolutions/bootstrap-datepicker/issues/1818#issuecomment-200030641

@yugenekr somewhat similar but not same. my scenario is by default it restricts end date to be today's date. When user select some specific value in dropdown, the end date should allow user to select future date.
i tried something like $("#endDate).datepicker("setEndDate", null); but it doesn't seem to work. :(

I'd test first any particular date is set using the command you sent (making sure it works in your layout at all). And then would probably try set end date to Infinity, as this is the value set by default. Though, according to the code, passing null should also resolve to Infinity internally, so I'd expect your code to work now, if it matches your layout.


I can`t find anything to do when i forget my password

Read the FAQ
#1634


eglMakeCurrent with EGL_NO_SURFACE does not work

for off-screen rendering I use eglMakeCurrent(display, EGL_NO_SURFACE, EGL_NO_SURFACE, context); which throws a nullpointer exception. This should be allowed (and works when copy/pasting eglMakeCurrent and removing checks for draw and read). Is it possible to fix this? (Class is org.lwjgl.egl.EGL10)

This will be fixed in the first 3.1.4 snapshot. Thanks!


udpate of testnet

Purpose

For reviewers

Related Github issues

Changes

Tests

Deployment Considerations
Version Notes
{ major | minor | patch }

NOTE: Include the version notes in the squash commit message

prnet cleaned-up successfully


Only Info toast type are shown

For me toaster only show the info message types irrespective of type.
I have tried calling it by
toaster.pop('warning', "Cancelled", "Grouping operation cancelled.");
toaster.pop({type:'error', title: "Error", body:"Oops...something broke. Please try again"});
Always show the green toast with the info icon.
Any idea why??
I have add all the dependices and module in my application but still nothing chnaged. Everytime i do a toaster.pop() it does display toast with the correct title and message but the same info one.

is this changes implemented in the toaster js??

Hi,
Thank you all for your investigation. The fix is done in the latest release.
Jiri.

This appears to still be a a problem for me.  I have the tried the following two ways:
toaster.error('Title', 'This is a message');
toaster.pop({type: 'error', title: 'error title', body: 'This is an error.'})
And both ways show me an info toast.
I'm using v0.4.16,
with the Angle-Template (latest version).
Thanks!
Brian

@briangullo Do you have two instances of <toaster-container></toaster-container> without unique IDs?  That can cause the type of issue you are having.
If you could please create a plnkr or a jsfiddle that demonstrates the issue, I'd be happy to look at it.

Hi @Stabzs , thanks for responding so quickly. I put together a plunker.  I'm not sure how helpful it will be, because it is only a piece of a much larger application.  http://plnkr.co/edit/V4vuj5mBy4duyerlk23d?p=preview
Maybe you could give it a quick glance and see if there is anything obvious.
Also, I'm getting this error: [$sce:itype] Attempted to trust a non-string value in a content requiring a string: Context: html
TIA,
Brian

No problem, happy to take a look.
The plnkr you linked works just fine after I added an ng-controller reference to it: http://plnkr.co/edit/desZfldVJnTwvmWgEw1O?p=preview
I would check your application first to make sure that you are reusing the same toast container instances.  I would also make sure that you are always firing toast calls from within an Angular context, not from native DOM events or jQuery calls.
Lastly, if you are getting an $sce error, make sure that you are using a bodyOutputType of "trustedHtml".
If none of that helps, try to create a full example of the issue you are seeing in a plnkr and I can point you in the right direction.

@Stabzs , Ok, thanks for the info, I will check it out and let you know what i find.

@Stabzs , just wanted to let you know, it was an issue with my routing.  The way I was combining the asp.net views and the angle routes was calling the same page twice.  Thanks!

@briangullo Thanks for confirming! Glad to hear you were able to work it out.

There isn't a better solution to this Issue? I got the error "Error: [$sce:itype] Attempted to trust a non-string value in a content requiring a string: Context: html", because I have twice instance of toaster. How can I fix it? (other solution than name different toaster)

@ignacio-chiazzo In either case, there isn't a bug.  It's a matter of using the correct APIs.
First off, if you are getting the error you reported, it is because you are attempting to inject an html template without using a bodyOutputType of "trustedHtml".  You can configure this as a global option per toast container or on a per toast basis, per the Body Output Type section of the README.
As for using more than one container, you absolutely can use more than one container.  However, if you do not use unique toasterids per container and you do not target those ids, your toasts will naturally be broadcasted to all available toast containers since you haven't specified which container to target.

@Stabzs  Thanks for responding so quickly! Can you give an example how to work with two ids, ?

@ignacio-chiazzo  my pleasure.
I created an example plnkr here: http://plnkr.co/edit/4ICtcrpTSoAB9Vo5bRvN?p=preview
for this closed issue: https://github.com/jirikavi/AngularJS-Toaster/issues/181.
It should give you exactly what you need for working with two unique container ids.

This should be in the documentation.

@matthieu-D Which part are you referring to?  IDs for toaster containers?  Thanks

Yes ids.

@matthieu-D documentation has been added.  Please review it and let me know if anything is unclear.

Perfect.

Hi, i implemented the version 3.0.0 and, in my case, this error continues.
there are two identicals newToastEventSubscribers when finished this command
$rootScope.$on(
'toaster-newToast', function (event, toasterId, toastId) {
for (var i = 0, len = newToastEventSubscribers.length; i < len; i++)
{
newToastEventSubscribers[i](event, toasterId, toastId);
}
});
then function addToast(toast, toastId) is call twice.
toast.type = mergedConfig['icon-classes'][toast.type];
if (!toast.type) {
toast.type = mergedConfig['icon-class'];
}
In the firt call the lines recovery the type toast-success from dictionary mergedConfig, but in the second call the type is already toast-success and the map fail.
From result i have a toast-info.


Add signing template task prefix

Two examples, first one with a display name of Sign our binaries and the second one with no display name so it uses the default of ESRP Signing

@TravisEz13 There seems to be binary file called .DS_Store in the PR. Please remove.

@adityapatwardhan  fixed and added ignore


How to run phantomjs on app in test environment?

Is there a way to configure teaspoon to use the rails environment "test", but only when running via phantomjs? This would be similar to booting rails with -e test? By default, teaspoon appears to be using the "development" environment.

Yea, I need this as well since rack-mini-profiler doesn't work nicely with my javascript tests. Also I assumed running rake teaspoon would already be run in the test env.


Avoid overflow of sigmoid

In practice, sigmoid is easy to overflow. Maybe we can add an upper bound parameter for sigmoid? like Activaction(x, act_type = 'sigmoid', upper_bound = MAX_X)?

This issue is closed due to lack of activity in the last 90 days. Feel free to reopen if this is still an active issue. Thanks!


[WIP]settings: Sort various table-based widgets.

This is a WIP PR created to get some feedback and doubts resolved, this will soon be corrected and updated.

Posted a few quick comments; the code looks like it's going in a great direction (I didn't test)

looks like Thomas has opened new PR for this!!


srcOnly does not work with stdenvAdapters which set env.NIX_CFLAGS_COMPILE

Describe the bug
When the adapter sets env.NIX_CFLAGS_COMPILE in both the srcOnly stdenv and in the package then there will be overlapping attrs.
https://github.com/NixOS/nixpkgs/blob/master/pkgs/build-support/src-only/default.nix
Steps To Reproduce
Steps to reproduce the behavior:

open repl
p = import ./. { overlays = [(self: super: {stdenv = super.withCFlags [ "-O3" "-march=znver2" "-mtune=znver2" "-flto" ] super.stdenv;  })]; }
p.srcOnly p.bash
get error: The ‘env’ attribute set cannot contain any attributes passed to derivation. The following attributes are overlapping: NIX_CFLAGS_COMPILE.

Expected behavior
No eval failure
Additional context
We should be able to fix this by using overrideAttrs in srcOnly
CC @sternenseemann @mdarocha
Priorities
Add a :+1: reaction to issues you find important.

i feel this is unsolvable... srcOnly uses drvAttrs which has env flatten into the toplevel attrset (not sure where in nixpkgs this step is done). and once they are there it's kind of hard to filter them out? Unless srcOnly filters everything and only keeps src, which I don't know is doable or not :thinking:
the other option is to have the adapters check if NIX_CFLAGS_COMPILE is already set on the top level.


Sending a ping every 2s actually keeps the connection alive so it works.

This is inspite of the bug filed for lila.

Please revert this. It's no longer necessary, I fixed the issue at lichess level.


FEDX-1400 Release gha-dart-oss v0.1.2

Pull Requests included in release:

Patch changes:

FEDX-1458: Fixed publish permissions

Requested by: @matthewnitschke-wk
Diff Between Last Tag and Proposed Release: https://github.com/Workiva/gha-dart-oss/compare/v0.1.1...Workiva:release_gha-dart-oss_v0.1.2
Diff Between Last Tag and New Tag: https://github.com/Workiva/gha-dart-oss/compare/v0.1.1...v0.1.2
The logs for the request that created this PR can be found here
This pull request can be recreated by clicking here

Security Insights
No security relevant content was detected by automated scans.
Action Items

Review PR for security impact; comment "security review required" if needed or unsure
Verify aviary.yaml coverage of security relevant code

Questions or Comments? Reach out on Slack: #support-infosec.


Figure out how to access Exif and GPS IFDs

The Exif 2.2 specification states that at the end of the 0th IFD, there are 2 private-tag-offset attributes, one of which specifies an offset to the Exif IFD, and the other specifies the offset to the GPS IFD.
Both offsets, as usual, are relative to the start of the TIFF header.

Okay, so, apparently the private-tag-offset attributes are included in the total number of attributes that an IFD contains.

I figured this out as part of https://github.com/Gigabyte-Giant/JPEG-Meta-Extractor/commit/2ec820c4135018b2280790342bba17f2fe598784.


examples: add an MPTCP using Socket2

Show how one can easily create an MPTCP capable webserver using Socket2.

MPTCP is a new protocol added in the Linux Kernel since 5.6. The goal of MPTCP is to support multiple path (cf: ADSL & LTE).
This allow for aggregation of links's bandwidth and for resiliency if any of the link fails.
Even if MPTCP is added in the Linux Kernel since 5.6, you may still need to enable it manually using:
sysctl net.mptcp.enabled=1

Signed-off-by: Martin Andre<EMAIL_ADDRESS>

note: this PR will fail until socket2 make a new release with the new Protocol::MPTCP, but the content can still be reviewed
(see https://github.com/rust-lang/socket2/commit/4c436818cddec880c26c4e79aca7106ba88827ff)

Thanks for the PR!
I'm a little hesitant to add a server example using a slightly different IO type. Especially needing to have another dev dependency and check it in CI. If it's already clear you can pass any IO type, is there a benefit to having this example on its own?
Do we just need to make the docs clearer you can pass any async IO?

I understand your totally valid point :)
I just think it would be great to have an explicit example of how to create a MPTCP server using Hyper as it may not be clear to everyone how to do so. I'm not sure about the dependencies, Socket2 was already present and this is why I thaught it wouldn't be too much of an issue (but Socket2 isn't used anywhere so maybe it's just a leftover that need to be cleaned).
It's totally up to you to accept this PR or not.


xds-server part2: add test section

add test section from https://gerrit.automotivelinux.org/gerrit/src/xds/xds-docs
description of architecture and how to launch tests
Change-Id: I872d41304642f0dae9c5893625916ff1b1273cc6
Signed-off-by: Clément Bénier<EMAIL_ADDRESS>

Looks good to me


Can we restrict notifications for the workitem we followed

When we follow a TFS workitem, we get notifications whenever there is any change made in workitem. Can we have a way by which we can get notifications for followed workitems only when there is a change in workitem state.

@imdkanikamahajan Thanks for your question. It looks like you're working through an issue with your scenario or implementation, rather than an issue with the documentation. Here are a few options where you might consider asking your question:

Azure DevOps on Stack Overflow
Azure DevOps Support Bot


Add the python-server api plugin to pypi

Would be really nice to have the great python plugin versioned on pypi.
If you need help with this, contact me.

TBH I'm not sure about this one. In my opinion it would be better to include the python plugin code into the plugin itself and use it as a package there (it's just a very small layer with a neglectable amount of files).

For the scope of ac client plugins I totally agree with you. But for every other python application it makes sense to have this api in a central repository (since ad hoc reuse is almost always a bad idea).
Think of server side applications or other desktop apps using the server api.

I don't get the point why this way of packaging should be a bad idea:
[QUOTE]
<my_server_plugin_root>

acplugins4python/ <stuff from this project goes here, could be shared e.g., by svn external>
main.py
[/QUOTE]

and in main.py you use it like this
[QUOTE]
from acpugins4python import ac_server_plugin
[/QUOTE]
I agree it's a good idea to have the plugin itself shared via pypi, but from my point of view, the plugin really wants to control the API version it is using.

Yes, as I mentioned: For the ac client plugin scope it is all fine. No contradiction with your argument.
But I was talking about standalone python applications (not plugins) interfacing with the server.
btw: A python application can still require a specific version of a PyPi package (and therefore api version). So there shouldn't be any loss of control.

I was also talking about standalone, server-side python applications, not about the client. I just don't see the advantage of having the plugin distributed over PyPi instead of just including the three python modules inside of the application (yet?).

 If now this bunch gets obsolete with a new AC Server version (1.2.x, 1.3, ..) you have to manually check all of the git(hub) repos for updates, and copy them all over again. If they were published in the central PyPi repo a simple
pip install -U module1, module2
would do this for you (without forcing you to manually check, if a new version is available in the github repos).
Sure, they are just three simple python files, but it's about the process. I understand that this might look like overkill at first sight but it definitely comes with some considerable advantages.

OK, I don't want to block this :) If you'd be willing to take care of the deployment, I'd be fine with that. Not sure how much effort this is? Would be cool, if the deployment could be done with a script.
I think we should at least add some version information to the plugin then (this is a good idea anyways).

The whole publish process is well defined and supported by pip. A typical publish to PyPi is done with a single command:
python setup.py register sdist upload

This command

Updates the version number, description and any other meta data to PyPi
builds a distribution zip containing the python package
uploads the zip to pypi

To upload to PyPi you need to be registered (it is free):
https://pypi.python.org/pypi?%3Aaction=register_form
I can upload it for you but I guess you want to keep control of the package.
Alternativley I can provide you the setup.py and all initially needed files to get it going so you can publish it easily.
Versioning is included in the PyPi conventions - see this example setup.py which should be sufficient to publish to PyPi:
from setuptools import setup

setup(name='ac-server-api',
      version='0.1',
      description='Python api layer for Assetto Corsa\'s UDP server API. Developed and tested with ACServer 1.2',
      url='https://github.com/minolin/acplugins',
      author='Minolin',
<EMAIL_ADDRESS>      license='MIT',
      packages=['acserver'], # put the three files (plus an empty __init__.py) into a folder "acserver"
      zip_safe=False)

You can optionally include a README.rst which is then rendered at PyPi.
See my package: https://pypi.python.org/pypi/speedwise-node
If you download and unzip it, you can check the setup.py and everything - but the example above should enable you to publish to PyPi right away. It is really not that much effort needed to get going.
Another short and good example of the PyPi/pip mechanics can be found here: http://www.scotttorborg.com/python-packaging/minimal.html

OK, uploaded version 0.1 to pypi (acplugins4python). Would you please have a look and tell me if that's OK from your side?

Just tested it. Works fine, thank you!
Off-topic: A little hint in README.md on how to enable the acServer's UDP ports in the server.cfg might be helpful.

Thanks for testing. Regarding README: when I have some spare time... Things are a bit busy right now. I think I can close this now... (just uploaded 0.3 to pypi with new API version)


AuthApiError: invalid claim: missing sub claim

Bug report
Describe the bug
Credentials are malformed are not being stored properly and therefore the client is not able to lately resolve the session

After calling  supabase.auth.signInWithPassword({email, password}) this strangely formatted token is generated
'["eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJhdXRoZW50aWNhdGVkIiwiZXhwIjoxNjY4NjAyNTM1LCJzdWIiOiJlYThiMjkxYS0wZTVkLTQ0YmEtYmViYi0zOGViYTQ1Y2UyOTgiLCJlbWFpbCI6ImFsZXh2Y2FzaWxsYXNAZ21haWwuY29tIiwicGhvbmUiOiIiLCJhcHBfbWV0YWRhdGEiOnsicHJvdmlkZXIiOiJlbWFpbCIsInByb3ZpZGVycyI6WyJlbWFpbCJdfSwidXNlcl9tZXRhZGF0YSI6e30sInJvbGUiOiJhdXRoZW50aWNhdGVkIiwic2Vzc2lvbl9pZCI6ImFkN2FmYzRiLTZmYzQtNGQxOC04OWJiLTRiYmM1YmNmMzUxMyJ9.LK3i6Dyh-dZX-yk4NvgEdxYwmxsoOnAk1vfK-0Nmoe4","ktuUPxuJF-PHPhRpWfvUfQ",null,null]'

And later on, doing   await supabase.auth.setSession(token); throws the following error:
{
  error: AuthApiError: invalid claim: missing sub claim
      at /home/alexvcasillas/otpfy/otpfy-v2/node_modules/@supabase/gotrue-js/dist/main/lib/fetch.js:41:20
      at processTicksAndRejections (node:internal/process/task_queues:96:5) {
    __isAuthError: true,
    status: 401
  }
}

This is the versions that I'm currently using:
"@supabase/auth-helpers-nextjs": "^0.5.2",
"@supabase/auth-helpers-react": "^0.3.1",
"@supabase/supabase-js": "^2.1.0",

This worked before with versions:
 "@supabase/auth-helpers-nextjs": "^0.4.0-next.4",
"@supabase/auth-helpers-react": "^0.3.0-next.4",
"@supabase/supabase-js": "^2.0.0",

And I have my product live without issues https://otpfy.com, but after upgrading everything to latest, it stopped working as expected 🤔
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
I'm using next for everything related
Sign in a user server-side
import { createServerSupabaseClient } from "@supabase/auth-helpers-nextjs";
import { NextApiRequest, NextApiResponse } from "next";
import { Database } from "../../types/database";

export default async function handler(
  req: NextApiRequest,
  res: NextApiResponse
) {
  const { email, password } = req.body;

  if (!email || !password) {
    res.status(400).send({ data: null });
    return;
  }

  const supabaseServerClient = createServerSupabaseClient<Database>({
    req,
    res,
  });

  const { data, error } = await supabaseServerClient.auth.signInWithPassword({
    email,
    password,
  });

  if (error) {
    res.status(500).send({ data: null, error: error.message });
    return;
  }

  res.status(200).send({ data: data });
}

Try to see if the user is authenticated after server-side:
import { createServerSupabaseClient } from "@supabase/auth-helpers-nextjs";
import { NextApiRequest, NextApiResponse } from "next";
import { fetchUser } from "../../services/user";
import { Database } from "../../types/database";

export default async function handler(
  req: NextApiRequest,
  res: NextApiResponse
) {
  const supabaseServerClient = createServerSupabaseClient<Database>({
    req,
    res,
  });

  const supabaseAuthToken = req.headers["supabase-auth-token"];

  if (supabaseAuthToken === "undefined") {
    res.status(401).send({ data: null });
    return;
  }

  const token = JSON.parse(supabaseAuthToken as string) as SupabaseAuthToken;

  await supabaseServerClient.auth.setSession(token);

  const {
    data: { user },
    error,
  } = await supabaseServerClient.auth.getUser(token.access_token);

  if (error) {
    res.status(401).send({ data: null });
    return;
  }

  if (user) {
    const userData = await fetchUser(user.id, supabaseServerClient);

    res.status(200).send({ data: userData ?? null });
    return;
  }

  res.status(500).send({ data: null });
}

Expected behavior
I should be able to sign up a user and work fine as expected
System information

OS: Windows
Browser (if applies): Chrome 107.0.5304.107
Version of supabase-js: 2.1.0
Version of Node.js: 16.15.0 on the local environment. 16.x on Vercel

I can't reproduce the malformed credential. But as for setSession(), we're now required to pass in a "session". But not a whole session, just the access_token and refresh_token. The docs have not been fully updated to reflect this, but the Parameters section is correct.
const { data, error } = await client.auth.setSession({ access_token: 'value', refresh_token: 'value' })

After following this example from the auth-helpers repository I managed to have all these features fully working and working like I charm I have to say.
Having upgraded to Next 13 seemed to be the root cause of this issue as now I can see that the supabase-auth-token is looking the same way as the one that I pointed out to be "malformed" because it didn't look like in the previous version.
I think it's safe to close this bug report as it relates to using supabase-js the same way as we did for next<13, which now is different and I've figured it out thanks to the given example. Hope others can find this example helpful too :)

I am having the same issue. But I am not in NextJS-land.
I am working on a server-side Solid Start solution, using cookies. Having said that the reproducing sample is just about identical.
The only difference is that I am getting the access_token and refresh_token from a cookie.
The weird thing is that the setSession call completes fine (I am passing an object with the access and header tokens). It even returns the session-data and the error property is indeed null.
The error comes from the getUser() call. And it is exactly the same as described in this issue.
A few days ago when I started working on the code, it was working too (AFAICT). I first then started to see this a few times and now it is there every time.
Is it necessary to even call getUser? The samples all show the setSession call without using the returned data, which includes the user. Cn't I just use the user returned?
In this app I am not exposing the supabase-client at all in the browser. All the code is run server-side. I am creating a secure cookie that contains the access and refresh tokens (encrypted). So, every request from the client to the server will pass that cookie and I will then be able to authenticate the user (via setSession).
Should I then update the refresh-token in my cookie after the call, if it has changed? As I believe that it may have been rotated - and I guess it should not be reused.

Although, I haven't tried to actually do anything after the setSession call yet. That might fail just as badly as the getUser call of course... I have just been passing the user-data back to tell the browser-client that the user is logged in. Got to go now, but I guess that is something that I will need to test...

Not sure if this is a perfect solution, but I made some option-changes to the call to createClient, which seems to have fixed the issue for me.
const supabase = createClient(supabaseUrl, supabaseKey, {
  auth: {
    autoRefreshToken: false, // All my Supabase access is from server, so no need to refresh the token
    detectSessionInUrl: false, // We are not using OAuth, so we don't need this. Also, we are manually "detecting" the session in the server-side code
    persistSession: false, // All our access is from server, so no need to persist the session to browser's local storage
  },

It seems that after I added persistSession: false the getUser call no longer resulted in an error.

Not sure if this is a perfect solution, but I made some option-changes to the call to createClient, which seems to have fixed the issue for me.
const supabase = createClient(supabaseUrl, supabaseKey, {
  auth: {
    autoRefreshToken: false, // All my Supabase access is from server, so no need to refresh the token
    detectSessionInUrl: false, // We are not using OAuth, so we don't need this. Also, we are manually "detecting" the session in the server-side code
    persistSession: false, // All our access is from server, so no need to persist the session to browser's local storage
  },

It seems that after I added persistSession: false the getUser call no longer resulted in an error.

Yeah, there's no good docs on this. For getUser() to work server-side, persistSession needs to be false.

@Spiralis @j4w8n thanks for bringing this up folks, I'm passing this as a feedback to the Auth team :)

No problem @soedirgo. What I said is only true if you don't pass an access token into getUser. Because in that case, it calls getSession; which is where things really breakdown.
Gary opened an issue about it https://github.com/supabase/gotrue-js/issues/539

I have also added passing the access_code (since I have it from setSession), as I understand that this reduces the work that getUser need to do.

Yep, that's a good way to do it on the server side.

I was getting this error because I have an Express backend and want to attach the user object in Express middleware. I am passing the accessToken / refreshToken via the serverSideRendering docs.
In the middlware, I was calling
const supabase = createClient<Database>(
      SUPABASE_URL ?? "",
      SUPABASE_ANON_KEY ?? "",
    );
supabase.auth.setSession(/*tokens*/)
// ...
supabse.auth.getUser() // returned the invalid claim error

Adding this flag (as referenced above) seems to have fixed it:
      // Without this flag, we get "invalid subclaim" error on supabase.auth.getUser
const supabase = createClient<Database>(
      SUPABASE_URL ?? "",
      SUPABASE_ANON_KEY ?? "",
      {
        auth: {
          persistSession: false,
        },
      }
    );

I am experiecing this issue too.
I have an nx.dev monorepo with an SPA in React app sporting Vite and an express app for backend stuff (both will go inside Tauri app).
Before I landed on the invalid claim: missing sub claim problem I have been debugging a different issue also related to how I was using Supabase. I was getting util.inherits is not a function, because I was trying to use one client for both express and react app (it is a monorepo, why duplicate configs). Anyway, one guy was having an issue with the util.inherits and the underlaying problem was that he was using jsonwebtoken that doesn't want to work with Vite because some nodejs APIs are not polyfilled. I split my code into two separate clients, which solved the util.inherits is not a function bug, but it gave me the invalid claim: missing sub claim one.
Could it be that the underlying issue is in Supabasejs not communicating properly with server-based build frameworks? This library is using jsonwebtoken. The "bug progression" on my end could indicate that jsonwebtoken is missing context, since it is not polyfilled anywhere. This problem also exists for browser's storage APIs and I bet jsonwebtoken is used here to en/decode data.
Since Supabasejs is isomorphic the solution could be in polyfilling jsonwebtoken's missing node APIs or replacing jwt with eg. jose that seems to be supported across environemnts.
I have no idea if any of this applies to invalid claim: missing sub claim, but I am going to debug it some more to narrow down the problem.

I ran into this issue tonight, getting invalid claim: missing sub claim, and ended up on this issue so I'll add my solution here for intrepid explorers 😄
I'm doing something similar to what was mentioned above with a client that logs in via Supabase, then sends the access/refresh tokens to a separate server.
The problem for me was that client.auth.setSession returns a Promise! I was just missing an await...
const supabaseUserClient = createClient(supabaseUrl, supabasePublicKey, {
  auth: {
    autoRefreshToken: false,
    persistSession: false,
  },
});

// you have to `await` this promise for the session to actually be set!
await supabaseUserClient.auth.setSession({
  access_token: accessToken,
  refresh_token: refreshToken,
});

return supabaseUserClient;

I'm having that issue using supabase with expo.
When I set persistSession: false authentication works but I definitely want to persist my session.
Any idea if there is another way to fix?

I'm having that issue using supabase with expo. When I set persistSession: false authentication works but I definitely want to persist my session. Any idea if there is another way to fix?

I'd recommend opening your own issue. This one is pretty stale. You can also ask on the Discord server.

I also encounter this problem, set persistSession to false not works for me, and also this answer link is dead, so this problem is not resolved for me. Is this isssue answered somewhere or is it not fix yet?

I also encounter this problem, set persistSession to false not works for me, and also this answer link is dead, so this problem is not resolved for me. Is this isssue answered somewhere or is it not fix yet?

I'm not 100% sure I understand your problem but have you tried the solution from my comment in another issue:
https://github.com/supabase/supabase-js/issues/786#issuecomment-1792692206

Too bad to see that this error still exists.
Especially when making a POST request inside a Next js /app dir.
How do we get around this? 🤔

Any workarounds? Using supabase on both server and client log-outs users from time to time, really annoying

Same issue here on Safari, working fine on Chrome.

@awalias why is this closed please? This is a persistent issue.

I think worth opening a new issue and linking to it from here so other folks coming from Google find their way

Same issue here on Safari, working fine on Chrome.

The same just happened to me with a Next.js app running in Safari for days in the background. For some reason that I haven't figured out yet, there was an infinite loop that kept calling /auth/v1/user again and again, receiving missing sub claim every time, until my Supabase egress quota limit was reached and I actually took notice of the issue.
According to my Auth logs, those calls stopped once I closed Safari. The network tab in Safari didn't list any of these calls though. So I suspect that there was something going back and forth between the client and my server which issued the calls to the Supabase API.


Separate debug/release dependency directories

While there are requests (#1359, #1596) to allow for the optimization of  dependencies, a suggestion to curb dev times would be to cache the results of dependency builds for debug/release separately, so that switching between cargo build and cargo build --release does not require a full rebuild of all dependencies, only the changed rs source files in question.

This should currently be the case (target/debug and target/release), but is that not working for you?

I'm sorry, I've been avoiding switching between them like the plague since I started using rust for this reason; it seems that it has indeed been resolved some time ago and I never dared to try it and find out :)


tests: adds ansible2.3 as a test environment

Signed-off-by: Andrew Schoen<EMAIL_ADDRESS>

The commit https://github.com/ceph/ceph-build/commit/08f82f9544993467cda9f6189480387d6499db26 changes the scenario being tested to ansible2.3, but that scenario didn't exist so the nightly tests have been failing.


set_physics_override

Your code is clean and well structured, but it has one major problem. When you use set_physics_override, you specify fixed values. This can cause problems if a player already benefits from a speed effect, for example via a potion or thanks to the 3d_armor mod.
Let me explain: if a player under the effect of a speed bonus uses this sprint mod, at the end of their race, their speed will be reset to 1.0, thus canceling the initial speed effect. To fix this, you need to get the player's current speed from before the sprint and add the sprint value to that speed on top, and replace the 1.0 with the player's initial speed found before the sprint

Hi,
Thank you for your feedback. I'm well aware of this issue and intend to fix it soon! This mod was made as a quick fix for the lack of faster movement in the Minetest Game. Originally, it was made for my current project I'm working on and thought, and I thought other people either playing or modding MTG would find it useful.

Okay, I took a look into this issue, and I'm afraid I won't be able to solve this (at least for now). From what I've seen in other mods such as Stamina, Magic Potions and Player Effect Potions they all rely on set_physics_override. This means that they are not only incompatible with my mod because it resets the speed value upon releasing the aux1 button, but they are also incompatible with each other. A speed potion from PEP won't stack with other speed effects from Magic Potions because they will override each other.
I also took a look at the source code of Voxelibre (Mineclone 2) and from what I understood is that they don't have this problem since the potions are made in mind with the default speed variable. Meaning they have a variable representing the original speed and upon consuming speed potion it won't override until the potions counter will expire.
I'm still fairly a begginer programmer and don't have the full grasp of the Minetest API. If you find a solution to this issue, feel free to create a pull request.

local function set_speed(player)
local controls = player:get_player_control()
local current_physics = player:get_physics_override()
local current_speed = current_physics.speed or 1.0
if controls.aux1 then
    player:set_physics_override({speed = current_speed + 0.8})
else
    player:set_physics_override({speed = current_speed})
end

end
minetest.register_globalstep(function(dtime)
for _, player in ipairs(minetest.get_connected_players()) do
set_speed(player)
end
end)


tomcat7 7.0.69

Upstream release 7.0.79: https://tomcat.apache.org/tomcat-7.0-doc/changelog.html
Tested and working on Mac OS X 10.11.5 beta.

Merged in https://github.com/Homebrew/homebrew-versions/commit/48dbb63efa87f38b8ba64f489493db33bd8b56cc. Thank you for your contribution to Homebrew @alanorth; we appreciate it! :smiley_cat:


python3Packages.pikepdf: 4.3.1 -> 4.4.0

Motivation for this change
https://github.com/pikepdf/pikepdf/blob/v4.4.0/docs/release_notes.rst
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

8 packages built:

img2pdf (python39Packages.img2pdf)
ocrmypdf (python39Packages.ocrmypdf)
paperless-ng
pdfarranger
python310Packages.img2pdf
python310Packages.ocrmypdf
python310Packages.pikepdf
python39Packages.pikepdf


feat(HMS-761): add instances description table after launch

https://user-images.githubusercontent.com/11807069/225382117-62798207-baac-4f40-87df-02e0fc352ffb.mov

Adding client side pagination:

The table is shown only in supported providers (aws atm)

Backend was merged FYI.

Looking in pr_check faiure

/retest

Rebased this to include https://github.com/RHEnVision/provisioning-frontend/pull/225

@amirfefer this is now broken (see chat), probably due to the backend change, mind taking a look? :)


Avoid using get plugins manager

Provide plugin manager as a parameter where it's possible.

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: SALEOR-1976 Optimize getting plugin menager


challenges on herox

have you considered this site?
https://www.herox.com/crowdsourcing-projects

@hengck23  Thanks a lot!
Herox.com definitely is very suitable for us ! 😄
However I see that maybe only challenges with "Data Science" tag can be considered.
Do you have any more advices? 🙇


Global variables bug

Bug Description
make backend does not update the .env when we change its values.
Reproduction
The bug is might on the database. Some database updates made the old env variables useless.
Expected behavior
The expected behavior when you update values in the .env file and run make backend should be as follows:
Loading Environment Variables: The updated values in the .env file should be correctly loaded into the environment when the backend service starts.
Database Configuration: The backend should use these updated environment variables to configure the database connection and any other settings that rely on environment variables.
Service Restart: The backend service should restart or reload with the new environment variables, ensuring that the changes are applied.
Who can help?
@ogabrielluiz
Operating System
Ubuntu Linux 22.04
Langflow Version
1.0.9
Python Version

[ ] 3.12
[ ] 3.11
[X] 3.10

🥇 Ran into this one.

I think I have similar issue. When I upgrade and redeploy my langflow app (for example to the newer version 1.0.12), all the global variables are gone, I have to delete and set them up again.

With new version of langflow I have issue editing fields. i have no idea how to edit those fields using UI. its like there is no edit button nor nothing like clicking it twice works...

@severfire Usually we do not allow editing secret variables items.

Will be fixed by #2971


Autoload directories

There are times in a developer's life where we need to load a bunch of arbitrary files, either when we're working with third-party code or when we want to extend out our application past the basic set of libraries and helpers. For example, presenters (see the blog post) would really benefit from being able to be automatically loaded.
This can also be useful when wanting to load all the files in a directory that might change regularly -- so maintaining an array to load everything would be tiresome.
I've alleviated this problem by adding a $this->load->directory() method to the Loader, as well as adding an $autoload['directories'] type to the autoload.php file. I'm using glob() to do the searching, so devs can use rather complex patterns to get nice and specific.

:+1:

Somewhat related to this (and Jamie's post on view presenters) - what are your thoughts on using "require_once()" versus adding another method to the Loader class that basically does the same thing? Has anyone noticed a preference, or complaints about one or the other?
I personally would think that replacing a require_once() near the top of my file with something along the lines of $this->load->class('product'); would better suit the CodeIgniter coding style.
I like the idea of this pull request :+1:, but I can see myself and most likely others not wanting to load unnecessary files, nor separate classes into directories in order to only load one file, even though it may be related to others.


DART

Thank you very much for your contribution!
I resolved the conflict in the documentation due to the parallel Pull Request by DTU Vermilion.


Runtime compilation should fall back to PTX rather than CUBIN

Currently, if the current device is newer than the device supported in that version of CuPy/CUDA, we are falling back to the latest CC supported by NVRTC:
For build-time compilation (CUB/Thrust compiled via nvcc), we are adding PTX for the latest compute capability (assuming CCs are monotonic): https://github.com/cupy/cupy/blob/f2a9d4bf498f80a46b4f2ebbca6734d741c4716a/install/cupy_builder/_compiler.py#L78
For runtime-compilation (kernels compiled via NVRTC), we are using maximum compute capability supported by the NVRTC: https://github.com/cupy/cupy/blob/f2a9d4bf498f80a46b4f2ebbca6734d741c4716a/cupy/cuda/compiler.py#L156
This was intended to use PTX's forward-compatibility feature:
https://docs.nvidia.com/cuda/ampere-compatibility-guide/

For example, PTX code generated for compute capability 7.x is supported to run on compute capability 7.x or any higher revision (major or minor), including compute capability 8.x.

However, after #5097 CuPy generates CUBIN instead of PTX at runtime, so this fallback stopped working as expected. Runtime compilation should be done in PTX when fallback is needed.
This was reported on the forum: https://groups.google.com/g/cupy/c/wJdMOJa8Bxo

User driver needs to be new enough to JIT the PTX, we'll also need to check for that.

Thanks for the comment Leo. To check that, do we have to maintain a list of CCs for each CUDA driver version?

That sounds expansive to me. I am thinking something simpler 😄 For the case of Ada/Hopper, for example, perhaps it's sufficient to just check if cudaDriverGetVersion() returns 11080 or above.

xref: https://github.com/pypackaging-native/pypackaging-native/pull/36#discussion_r1204534722

xref: https://docs.nvidia.com/cuda/cuda-c-best-practices-guide/index.html#using-ptx

As PTX is compiled by the CUDA driver, new toolchains will generate PTX that is not compatible with the older CUDA driver. This is not a problem when PTX is used for future device compatibility (the most common case), but can lead to issues when used for runtime compilation.

So we do need to check the driver version before taking the fallback path. New PTX cannot run on old driver, but old PTX can run on new driver.

xref: https://github.com/cupy/cupy/pull/7954#discussion_r1368081996


feat: Sending structs from Rust to TS

Closes #52
I created a new struct in the Rust backend called Outputs. Outputs are returned to the React frontend when running run_program or prove_program. Outputs include
#[wasm_bindgen(getter_with_clone)]
pub struct Outputs {
    pub stack_output: Vec<u64>,
    pub trace_length: usize,
    pub overflow_addrs: Option<Vec<u64>>,
    pub proof: Option<Vec<u8>>,
}

The proof is stored in the browser for later use
        // Store the proof in the session storage
        if (proof) {
          sessionStorage.setItem("proof", proof.toString())
          }

I think we should update the Outputs struct in the PR comment, since now it also stores program_info. But still looks good to me!


Preserve folding when sub-scene is changed

Fixes #29975
Turns out I was right in https://github.com/godotengine/godot/issues/29975#issuecomment-529269149. The folding is cleared in the constructors, because the scene is ninja-reloaded when the sub-scene is updated, bypassing any standard loading mechanisms. Trying to find this out was terrible process ;_;

Does this problem have anything to do with this hack?
https://github.com/godotengine/godot/blob/24e1039eb6fe32115e8d1a62a84965e9be19a2ed/editor/editor_node.cpp#L1219-L1226

No, the problem was that the scene was silently reloaded, but it didn't load the folding data.

Thanks!

@KoBeWi my sincere gratitude for fixing this, you saved my sanity! 🙂


[chttp2] Tune initial window size/max frame size setting

Only choose frame sizes and initial window sizes that are powers of two - as a more predictable function to avoid flapping.
If window size drops below 1kb then snap to 0 to avoid frantically changing a value that needn't be
Allow the initial window size to drop to zero (we have fuzzing in place that says this is safe)

I've updated this to flag protect it so that we can trial it internally with some customers. @Vignesh2208 @yashykt ptal


Impossible to install on debian, even with pip

Description
It is not possible to install aws-sam-cli on Debian stable.
Steps to reproduce
$ pip3 install aws-sam-cli --user
Collecting aws-sam-cli
  Using cached https://files.pythonhosted.org/packages/c3/7c/79463add5772a98f044fab3024c27db61550bb1d9bbd06a715e3c3dc6b2a/aws_sam_cli-0.10.0-py3-none-any.whl
Collecting PyYAML~=3.12 (from aws-sam-cli)
  Downloading https://files.pythonhosted.org/packages/9e/a3/1d13970c3f36777c583f136c136f804d70f500168edc1edea6daa7200769/PyYAML-3.13.tar.gz (270kB)
    100% |████████████████████████████████| 276kB 2.7MB/s
Collecting serverlessrepo==0.1.5 (from aws-sam-cli)
  Could not find a version that satisfies the requirement serverlessrepo==0.1.5 (from aws-sam-cli) (from versions: 0.1.6, 0.1.7, 0.1.8)
No matching distribution found for serverlessrepo==0.1.5 (from aws-sam-cli)

Observed result
The above error message.
It turns out that aws-sam-cli dropped support for Python 3.5 in 0.11. So on Debian stable pip install aws-sam-cli will silently revert to trying to install 0.10, which for some reason isn't  installable at all anymore.
This results in both a very obscure failure and the inability to use aws-sam-cli on a very common platform.
Expected result
Since Debian stable  is a very common OS in general and a very common base OS for Docker images in particular I expected to be able to install aws-sam-cli.
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)

Okay it's a bit stranger. Support for 3.6+ was added here: https://github.com/awslabs/aws-sam-cli/pull/483
Before that all Python 3.x was supposed to be unsupported, so I don't quite understand why pip tries to install version 0.10.
It seems there was never a clear motivation for why only 3.6+ is supported.

These are the steps which I think would be required:

[ ] Update the version requirement in setup.py
[ ] Update the list of Python versions in tox.ini
[ ] Update the list of Python versions in DEVELOPMENT_GUIDE.md
[ ] Run tests according to the instructions in DEVELOPMENT_GUIDE.md

I'm not  sure if this is desired or not though.

@rvolgers Thanks for the issue but Python3.5 has never been supported. The CLI has been installable in other versions but that was due to an issue in our setup.py (info can be found #966).
When we went to support Python3, we made the explicit decision to only support the newest Python3 version (3.6 at the time). In the ideal case, we will only need to support a single version of Python and customers never have to care what version (or even that it is written in Python). We are getting closer to this ideal world with our installers. For example, the MSI for windows we provide has Python packaged with it. This means windows users, can just install without needing to go download python or make sure they have the right version. For linux, we support Linux Brew and shortly will have a snap (not sure if we have it published yet but we did accept a contribution recently for snap support).
Installing with pip (even though it is not recommended), requires you to make sure you are installing in a supported version. Since this isn't the case, you should either install the CLI into a supported Python version with pip or use one of our installers.
Closing as Python3.5 is not supported.

Thanks for explaining your decision. For what it's worth I'm not a fan of this approach.
The aws-sam-cli tool is highly privileged when used for deployments and depending on things like brew or snap or shipping huge binary dependencies that were built in unknown circumstances from uncertain sources means we now have to trust many more people and systems.
I realize it's in beta and moving fast, but I was hoping to benefit from some of the ergonomic improvements around lambdas for some boring old software. Seems that won't be in  the cards anytime soon though.

@rvolgers You can still use pip just with supported versions, but problems that come about are then left to you (old setuptools, wheels, libraries conflicting with other projects you have installed, etc). Our goal with installers, are to make installations more reproducible and put the burden off customers.

The aws-sam-cli tool is extremely highly privileged when used for deployments and depending on things like brew or snap or shipping huge binary dependencies that were built in unknown circumstances from uncertain sources means we now have to trust many more people and systems.

Can you explain this further? Our brew and snap formulas are all open sourced, brew currently builds from source into a venv. Not sure what about our current approach makes you uneasy.

Simple installation on Linux is extremely important, without tools like brew - I'm trying to run SAM on Travis and this is really hard. I feel that this is the wrong approach :/

For what it's worth, I will no longer be following this issue since with the release of Debian Buster there is now a viable path forward for us that doesn't involve taking a dependency on another distribution channel like snap or brew.
I never answered the question why relying on more distribution channels makes me uneasy, because I feel like it is obvious and don't quite know where to begin explaining it. But here goes:

I don't know anything about how they deal with transfers of control / maintainership
I don't know anything about their social controls / vetting
I don't know anything about their testing approach
I don't know anything about their stability guarantees
I don't know anything about who provides their bulk data hosting, and whether the packaging tools require them to be trusted
I don't know anything about their packaging format and how signatures and hashes are validated
I don't know anything about who provides, funds, and maintains their core infrastructure
I don't know anything about their usage numbers and use cases. For example, they may get millions of downloads for e.g. OSX but only a few for Linux, which would put us into a much smaller niche of users than we are comfortable with.

Especially in small teams you are asking someone to make a judgement call that all of this will be fine and will remain so for however long the dependency persists, even after the person who originally added it has moved on. It simply doesn't scale.


🐛: Footer should always be at the bottom of the page which is not the case here

Footer should always be at the bottom of the page which is not the case here

:white_check_mark: To be Mentioned while taking the issue :

Full name : Tarun Kumar
What is your participant role? GSSOC 2024 ext

Assign this to me under gssoc 2024 ext and hacktoberfest i will work on this issue.

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

@Avdhesh-Varshney What to add in the env it is not working locally you haven't added anything related to that in the readme also it is not working locally what to do. please reply asp.


Track code stats

The objective is to be able to easily check current but also historical stats (such as code quality and complexity metrics) on the state of repositories.
Let's look for existing tools for this first. But if we needed to hack a minimal one for ourselves, here are some ideas:

CI updates a hidden "tracks" file (json, yaml, csv,...) with the new stats on every CI run (maybe only successful ones)
Alternative: Uses an API to tell a service to dump the stats in an actual DB. Probably Elastic, since has Kibana to view graphs etc. Easier to directly do analysis if we don't have to fetch files from each of the repos?

I've written a few things in umpyre, so you can accumulate/aggregate further stuff there.
But if possible, let's use others' packages instead of writing our own: Still, we can develop our own functional interface to these tools in umpyre.
What, and with what to track?
This should, of course, be parametrizable, because we will no doubt want to add and remove trackers.
Implementation-wise, this points to an architecture where we can specify the what in a config file that is separate from the code that uses the config file.
Proposals for tools to use are welcome!
Here are a few ideas:

radon computes Halstead and "Maintainability index" (and two others).
coverage

Tools Ziyan’s looked into:

[wily](https://wily.readthedocs.io/en/latest/) (Recommended)

examines the current complexity of the project or of any of the individual Python files
can be used in a CI/CD workflow to compare the complexity of the current files against a particular commit
can be used with pre-commit hooks
visualize change of complexity over time with table and graph
some commands:

wily build: iterate through the Git history and analyze the metrics for each file
wily report: see the historical trend in metrics for a given file or folder
wily graph: graph a set of metrics in an HTML file
wily diff: compares the last indexed data with the current working copy of a file

will detect and scan all Python code in .ipynb files automatically
uses radon to calculate metrics

[coverage](https://coverage.readthedocs.io/en/6.5.0/) (Recommended used together with wily)

finds the lines of code that are missing tests
can easily run on top of pytest

[radon](https://radon.readthedocs.io/en/latest/)

computes:

cc: compute Cyclomatic Complexity
mi: compute Maintainability Index
hal: compute Halstead complexity metrics
raw: compute raw metrics

LOC: the total number of lines of code
LLOC: the number of logical lines of code
SLOC: the number of source lines of code - not necessarily corresponding to the LLOC [[Wikipedia]](https://radon.readthedocs.io/en/latest/commandline.html#wikipedia)
comments: the number of Python comment lines (i.e. only single-line comments #)
multi: the number of lines representing multi-line strings
blank: the number of blank lines (or whitespace-only ones)

works with Jupyter Notebook

[mccabe](https://pypi.org/project/mccabe/) - checks for McCabe code complexity (The number of independent code paths present. Want score ≤ 10

1–10: low risk, simple program;
11–20: moderate risk, more difficult program;
21–50: high risk, very difficult program;
> 50: very high risk, untestable program.
flake8 wraps around

[complexity](https://github.com/thoughtbot/complexity) - a command line tool calculates an approximation of code complexity per file in a language-agnostic way

not very intuitive interpretation of the values of the metrics

Seems like wily+coverage is the way to go. @valentin-feron what do you think?

Yes I agree. I would even say pylint+wily+coverage (code stylying + complexity tracking + test coverage)


Add some missing Unicode 15 emoji

Hey all - I'm Stephen from Discord. We've used Twemoji for a long time and we really care about the project. We would love to help support the library moving forward. One of our in-house artists Kevin VQ Dam has prepared SVG options for the following emoji in Unicode 15.

Shaking face
Moose
Donkey
Wing
Goose
Jellyfish
Hyacinth
Ginger Root
Pea Pod
Folded hand fan
Wireless symbol
Leftwards pushing hand
Rightwards pushing hand

We've included the SVGs and the 72x72 PNGs (produced by rsvg-convert and pngcrush -rem alla -nofilecheck -reduce -m 7) to the assets folder. This partially responds to #8, excluding those already prepared by @sofodesign, @Gabe-Mitnick and @jyo0329.
Hope these help and looking forward to helping support Twemoji more in the future!

Thanks again to all the folks at Discord who worked with us on these! You've been a massive help for Sofo's and my limited time in recent months and we really do appreciate it.

Great to see Discord stepping up here folks - is there an expected timeframe for these emojis to be implemented within the Discord site and apps?


02-load-data-with-power-query-in-power-bi-desktop.md

English:
Click Save.
Current Translation:
按一下 [檔案] 。
Suggested Translation:
按一下 [儲存] 。
Description:
Mistranslation. Global check this issue.

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

Run bugfix tool and waiting for result.


Replace Ginkgo

This PR replaces the Ginkgo integration tests with native Go tests using the testing package. The restore part of the existing test in master is incomplete in terms of steps and verification. The missing parts are added.
This is still a bit of a WIP but it would be good to go ahead and get eyes on it.

I think I will be able to reproduce the failures we are seeing in https://github.com/k8ssandra/k8ssandra/pull/811. In restore_controller_test.go when I do the force upgrade racks, I need to also set the CassandraDatacenter updating condition to true. The timestamp for it will (or could be) before the restore start time.


Cannot convert value of type '(MoyaTest) -> Endpoint' to expected argument type '() -> Endpoint<>'

with the latest version 10.0.0

@rainedAllNight it's hard to tell exactly what's wrong, but can you add a type annotation to the line where you declare endpointClosure? So something like
let endpointClosure: Moya.EndpointClosure<MoyaTest> = ...

that might lead to swift giving a more helpful error message


Issues with vertexAttribPointer() - none of the pointcloud examples are working

Whenever I try to run any of the point cloud examples in the library, I get the following error:
The function "vertexAttribPointer()" expects parameters like: "vertexAttribPointer(int, int, int, boolean, int, int)"
Related to these lines of code:
  pgl.vertexAttribPointer(vertLoc, 3, PGL.FLOAT, false, 0, pointCloudBuffer);
  pgl.vertexAttribPointer(colorLoc, 3, PGL.FLOAT, false, 0, colorBuffer);

I've tried looking through the KinectPV2 Reference, but cannot find the functions involved, and am at a bit of a loss as to what to do.

The issue seems to be with pointCloudBuffer and colorBuffer, neither of which are 'int' values.
I tried appending '.arrayOffset()' to the end of each, which should return an int, and (I thought) provide the 'offset' value vertexAttribPointer is looking for. However, while this allowed the program to compile, I got a runtime error:
unsuportedOperationException

are you still having problems with the openGL examples?

Since I updated from 0.7.5 to 0.7.7, the OpenGL point cloud examples both work fine!


Highlight calls plugin broken

Ida 7.5 + python3
[PluginLoader] Loading plugins from system-wide and user-specific lists:
[PluginLoader]   System-wide List:      C:\Program Files\IDA Pro 7.5\cfg\plugins.list
[PluginLoader]   User-specific List:    C:\Users\stephen.eckels\AppData\Roaming\Hex-Rays\IDA Pro\plugins.list
[PluginLoader]   Project-specific List: C:\Users\stephen.eckels\Desktop\labs\plugins.list
[PluginLoader] Failed creating system plugin list at C:\Program Files\IDA Pro 7.5\cfg\plugins.list
C:\Users\stephen.eckels\source\repos\Sark\plugins\highlight_calls.py: string argument without an encoding
Traceback (most recent call last):
  File "C:\Program Files\IDA Pro 7.5\python\3\ida_idaapi.py", line 604, in IDAPython_ExecScript
    exec(code, g)
  File "C:/Users/stephen.eckels/source/repos/Sark/plugins/highlight_calls.py", line 4, in <module>
    from ida_settings import IDASettings
  File "C:\Users\stephen.eckels\AppData\Local\Programs\Python\Python37\lib\site-packages\ida_settings\__init__.py", line 1, in <module>
    from .ida_settings import IDASettings, PermissionError
  File "C:\Users\stephen.eckels\AppData\Local\Programs\Python\Python37\lib\site-packages\ida_settings\ida_settings.py", line 859, in <module>
    VALUE_1 = bytes("hello")
TypeError: string argument without an encoding

I see this is related to ida_settings not being up to date on pypi, i've installed locally instead. The script now loads successfully, however when executing it nothing is highlighted (and no errors are reported), any ideas?

User error, had to toggle in view menu. I've messaged Willi about publishing new version of ida_settings


When changing focus to Chrome window A, focus is immediately redirected to Chrome window B

Describe the bug
When changing focus to a Google Chrome window, either via workspace or focus-monitor, I am finding that Chrome (or something else) then immediately redirects focus to a different Chrome window. I can more clearly see this focus change thanks to on-focus-changed = ['move-mouse window-lazy-center'].
I will attempt to reproduce on my personal machine and post a video. I am on a multi-monitor setup with macOS Sequoia 15.1 and AeroSpace v0.15.2-Beta b6cf82771f245ab7349a93baf8709e171537ff58.
Related issues you could find
n/a

I think you'd need to set Displays have separate Spaces under system settings → Desktop & Dock to off.

Interesting, I'll give this a shot

To get this working with the prior setting set to on, I think one needs to use additional private APIs:

Not sure I follow... what's the reasoning here?


change markdown spacing in scriv template

Currently 3 spaces, should make it 1 to be consistent with standard expected by Markdown tooling and CODACY

requested changes checked in PR issue1304-scriv


Add a variable for ALB security polices

The following ELB security policies are available:
https://docs.aws.amazon.com/elasticloadbalancing/latest/application/create-https-listener.html#describe-ssl-policies
This pull request allows the user to select a policy.

Thank you!


Invisible white text in light mode

As you can see in the image below, it's very hard to see the texts in light mode. I would like the texts to be blended in the system color. In dark mode, the text is already white so there is no trouble there.

Same as #34


Support datetime_add and date_add

For @elixir-lang/ecto-adapters,

[x] PG
[x] MySQL
[x] SQLite3
[x] MSSQL

We have added datetime_add and date_add with intervals to Ecto. Here is the commit: https://github.com/elixir-lang/ecto/commit/df37f43a55006ff1e780b87d717901894613dec6
Your adapter should require the new test file and implement the two functions in case date/time interval operations are supported. Otherwise, it should just raise.

@josevalim I noticed that the MySQL changes allow microsecond precision in intervals and that the MySQL adapter excludes :uses_usec tests.  Is that a mistake?  Should the :uses_usec exclusion be removed from integration_test/mysql/test_helper.exs, or should two different tags be used for the tests in integration_test/cases/interval.exs and integration_test/cases/repo.exs?

SQLite: https://github.com/jazzyb/sqlite_ecto/commit/03623a39a1abf3ad2f16099acf3794a0fe0f7057

Had a little restructuring on my connection. Now the intervals are working.
MSSQL:  livehelpnow/tds_ecto@ 9033bc2931cf4ef8388a5deaa7db217ce9657094

:heart: :green_heart: :blue_heart: :yellow_heart: :purple_heart:

The documented code seems not to work on postgres
assert TestRepo.all(from p in Post, where: p.inserted_at >
                             datetime_add(^Ecto.DateTime.utc, -1, "month"))

Gives me an argument error
** (ArgumentError) argument error
    :erlang.apply(0, :type, [])
    (ecto) lib/ecto/type.ex:230: Ecto.Type.match?/2
    (ecto) lib/ecto/query/builder.ex:259: Ecto.Query.Builder.assert_type!/3
    (ecto) lib/ecto/query/builder.ex:90: Ecto.Query.Builder.escape/5
    (ecto) lib/ecto/query/builder.ex:142: Ecto.Query.Builder.escape/5
    (ecto) lib/ecto/query/builder/filter.ex:16: Ecto.Query.Builder.Filter.build/5
    (ecto) expanding macro: Ecto.Query.where/3
    integration_test/cases/interval.exs:223: Ecto.Integration.IntervalTest."test datetime_add with dynamic"/1

Looks like this was reported in #833


Decouple MMIO from CPU emulation in API

Right now the emulator loop calls clemens_emulate() to emulate both CPU and IO.    To support machines other than the IIgs, or more importantly to properly write tests for CPU and I/O units, it would be good to decouple the IO and CPU emulation calls to an API like
clemens_emulate_cpu(&machine);
clemens_emulate_mmio(&machine);

This way instruction tests could just call clemens_emulate_cpu().    Some similar benefits for testing just the FPI and MEGA2 units could be gained - though unit tests would likely focus on the individual subsystems (vgc, rtc, adb) and bypass the memory mapped I/O unit.
LIkewise such an API could be further split up to write a competent disassembler API for the 65816 and skip the CPU state handling that would otherwise be still implemented in clemens_emulate_cpu.

Fixed in https://github.com/samkusin/clemens_iigs/pull/25


Playlists only populate when Home Assistant starts

Playlists for the device populate when Home Assistant starts. If user or device playlists change while Home Assistant is running they will not update. We should not have to restart Home Assistant to see new playlists.
Additionally, because the playlists are populated with both device and user playlists, some playlists can be in the list which are not synced to the device yet. This leads to the issues in #5.
If we only populate with device playlists, polled from the local device during the update loop, playlist management can be off-loaded to the Meural app and web interface.

Resolved in:
https://github.com/GuySie/ha-meural/commit/766da1137717891935e54b65a5b7e3ecfd5f780e


brownie compile doesn't procude any artifacts for token template

Environment information

brownie Version: v1.8.1
ganache-cli Version: v6.9.1
solc -- There is nothing in installation info about solc dependecy. I've installed it like brew install solidity, solc --version = 0.6.6
Python Version: 3.8.1
OS: osx 10.15.4

What was wrong?
brownie compile doesn't procude any artifacts. Here are console logs how I did it:
max@mbp ~ $ pipx install eth-brownie
  installed package eth-brownie 1.8.1, Python 3.8.1
  These apps are now globally available
    - brownie
done! ✨ 🌟 ✨

max@mbp _tmp $ brownie bake token
Brownie v1.8.1 - Python development framework for Ethereum

Downloading from https://github.com/brownie-mix/token-mix/archive/master.zip...
4.45kiB [00:00, 1.71MiB/s]
SUCCESS: Brownie mix 'token' has been initiated at /Users/max/p/_tmp/token

max@mbp _tmp $ cd token/
max@mbp token $ brownie compile
Brownie v1.8.1 - Python development framework for Ethereum

Project has been compiled. Build artifacts saved at /Users/max/p/_tmp/token/build/contracts

max@mbp token $ tree .
.
├── LICENSE
├── README.md
├── build
│   ├── contracts
│   ├── deployments
│   └── interfaces
├── contracts
│   ├── SafeMath.sol
│   └── Token.sol
├── interfaces
├── reports
├── scripts
│   └── token.py
└── tests
    ├── conftest.py
    ├── test_approve_transferFrom.py
    └── test_transfer.py

9 directories, 8 files

Thanks for opening an issue!
The problem is a bug related to _tmp in the install path.  If you move the project to another location so that none of the directory names in the path have a leading underscore, the issue should be fixed.
I'll fix that right away and have a patch release out later today.


Lzip bool

Included int his change set:

All tests compile and pass
Travis is not complaining anymore (can be compiled down to 4.04.0)
All of parameters in HigherOrder.ml Supperposition.ml are converted to flex state
Parameters to unification are flex state and look beautiful
Merged with master

Tests are running on TPTP.

I'm going to review that but it'll take a bit of time. I'll also do the conflict resolution, I think. Thanks @petarvukmirovic :)


Translation and contribution

I left the most title in English because if you translate it to my language the meaning becomes different.

Thanks.


test: set hubble-relay image in helm defaults if available

Hubble-relay image must be set in helm defaults for it to take effect.
Signed-off-by: Jarno Rajahalme<EMAIL_ADDRESS>

test-me-please

Coverage increased (+0.001%) to 36.918% when pulling c551aaf68990625f47f4de160bb52f8c2834e629 on pr/jrajahalme/test-set-hubble-relay-image into f5a7682bdefe98072175e2fd2571f986ac4815f5 on master.


Phase 0 to 1 upgradability: fork/version boundary deserialization issue

Thanks to @dankrad for giving input of the proposed solution.
tldr: (i) The SSZ object versioning is based on protocol versions, and (ii) heterogeneous list/vector is not allowed in SSZ. So with the current phase 1 spec (https://github.com/ethereum/eth2.0-specs/pull/1427), when we cross the version boundary, we are not able to process the previous operations with the new scheme.
Issue
Versioning in the networking layer

For the individual operation gossip topics messages (e.g., attestation, voluntary_exit) are versioned by protocol IDs. So it's fine to receive messages of different versions at the single-operation level.
The Protocol ID would map to the specific schema version of the SSZ object definition, so that we can deserialize it with the corresponding schema. So 👍

Fork/version boundary operations

However, when crossing the version boundary, the current BeaconBlockBody.[operations]: List[Operation, N] only hold for one version of the given Operation.
The block proposer cannot include both the previous version and current version objects in the same SSZ List. For example:

Example 1: Attestation inclusion

In the phase 1 protocol changes, we can forecast that at least AttestationData fields will be changed.
For the attesters of the last slot of the previous version, if they create attestation with the old schema, their attestation will not be able to be included in the block of the first slot of the current version.
If the attesters create attestation with the new schema, it's possible to be included in the next block. But, should they?
Moreover, how about the late attestations?

Example 2: Slashing operations

AttesterSlashing contains attestation_1: IndexedAttestation and attestation_2: IndexedAttestation, so similar to Attestation, the new version block can't include heterogeneous AttesterSlashing formats. So we can't slash the malicious attesters at the previous version epoch.
ProposerSlashing contains header_1: BeaconBlockHeader and header_2: BeaconBlockHeader, which are the conflicting beacon block headers of the slot of the proposer to slash. If we change BeaconBlockHeader format in the future version, we can't slash the malicious proposer that double-proposed at the previous version epoch.

Example 3: BeaconState.previous_epoch_attestations: List[PendingAttestation, MAX_ATTESTATIONS * SLOTS_PER_EPOCH].

At the first epoch of the new version, this field should be able to hold the previous version of PendingAttestation.

Proposed solution

Use SSZ Union type to make Phase1 Lists compatable with both previous & current version of objects. e.g., Phase1BeaconBlockBody.attestations: List[Union[Phase0Attestation, Phase1Attestation], N].
Pros:

The proposers can now include both versions of SSZ objects.

Cons:

Compare to rejecting all incompatible operations, it's more complex to handle both versions.

My instinct is to just disallow phase 0 objects to be included in phase 1 and vice versa. There are a few validators that would lose a tiny amount of rewards, but the losses are tiny. Also, from the protocol point of view, finality will happen in phase 1 just fine. The main risk is that fraud proofs from the end of phase 0 would not carry over into phase 1 so validators could get away with some mischief in the last few slots of phase 0, but especially between phase 0 and phase 1 I don't see even that risk as being anywhere close to high enough to justify the complexity of working around it; relying on honest majority is fine.

Base on the weekly call (as Vitalik's response above), closing the issue now. We might think more about the details once the upgrade is coming. :)


filter option to handle filtering in the app rather than in the library

I have a use case where I need to exclude some files from loading into the context. (It's a file that has to exist in the Google stack who has a function that mirrors a utility on the node side. If it's defined in the context (so that it exists on Google) that mirror function does not get executed.)
This way the programmer can just do:
let path = require('path');
let ctx = gas.require('./src', {}, {filter: function(f) {
    var ext = path.extname(f),
        base = path.basename(f);
    return ext == '.js' && basename != 'exclude';
});

And that way the calling application has more control over how it operates. Other options might in the future be used as well.

@brainysmurf , very useful idea with filter and option 👍 Thanks!


Add the facility to exclude namespaces from generated code

Is your feature request related to a problem? Please describe.
Generated code or AspNetCore projects that have global using means that the addition of some using namespaces is not required
Describe the solution you'd like
Add a configuration to exclude certain 'usings' from generated code, similar to the "additionalNamespaces"  configuration.
Additionally, this feature could support wildcard matching such as:
  "excludeNamespaces": [ // Optional
    "System.*"
  ],

over
  "excludeNamespaces": [ // Optional
    "System.Collections.Generic*",
    "System.Text.Json.Serialization",
    "System.Threading",
    "System.Threading.Tasks",
  ],

Describe alternatives you've considered
Refitter to read and parse the project config file to automatically exclude any global 'usings' included in the file, and the defaults
Additional context
n/a

That's a good idea!
Thanks for suggesting this @dammitjanet

There will be a PR for this either later today or tomorrow morning, just need to add new Tests and update the docs

Thanks for the contribution @dammitjanet


Not able to remove/update existing document (or able to view a deleted document)

my environment running ArangoDB
I'm using the latest ArangoDB of the respective release series:

[ ] 3.1

On this operating system:

[ ] Linux

[ ] Ubuntu .deb

I am using ArangoDB in cluster mode.
Hi guys, I am facing an issue. I am not very sure it's related to cluster only.
I have a coauthors (edge) collections  in which I have a document with _key value 205299267. I am facing some weird issues with this document. This is the behavior of this document under various queries (all issued from web interface).

FOR coauthor IN coauthors FILTER coauthor._id == "205299267" RETURN coauthor
returns me the document
RETURN DOCUMENT("coauthors/205299267")
returns [null]
REMOVE "205299267" IN coauthors
Query fails to execute with error Query: Error message received from shard 's3542516' on cluster node 'PRMR-2a633716-3540-4a30-8ec3-2f00b99f3a46': document not found (while executing)
REMOVE {"_key": "205299267"} IN coauthors
Query fails to execute with error Query: Error message received from shard 's3542516' on cluster node 'PRMR-2a633716-3540-4a30-8ec3-2f00b99f3a46': document not found (while executing)
I can open open this document in my collections i.e. from it's web page on _admin/aardvark/index.html#collection/coauthors/205299267
When I delete or save this document from it's web page I am thrown no error but it doesn't get deleted or updated.

Hi,
Sorry for the late reply; This is actually a duplicate of a bug fixed a while back; Coordinators wouldn't propperly distribute the documents to the propper DB-Servers. Subsequent queries would then fail to find the document in most cases except for full collection scans.
ArangoDB 3.3.19 is available for download with this bug fixed.
Please note the ArangoDB 3.4 Milestone 3 release including the brand new ArangoSearch.
Closing.


[SD-JWT] iat is now disclosable

here https://github.com/italia/eudi-wallet-it-docs/blob/versione-corrente/docs/en/pid-eaa-data-model.rst#L78
we have to align to this https://github.com/oauth-wg/oauth-sd-jwt-vc/pull/202

This is a good catch as in some scenarios the iat attribute can reveal something about a user's data. So having it selective-disclosable is good. Nevertheless, benefits are almost nullified because of the exp attribute, which is exposed to the same or worse issues - and we cannot hide its value because is a mandatory field for JWT.
Anyway, I agree it's worth being included in our implementation.

About the methodology: I'm not happy about us following other's pull requests and issues. I know the reference it's still a draft and I see the value of keeping up with the changes.
I think a better approach would be to open the issue once a new version is released. I foresee these possible benefits:

We rely upon a complete specification; cherry-picking changes may lead to a partial implementation, which could be unstable and insecure
Readers would know exactly which version of the draft we are referencing, making it easier to audit our specifications for bugs or missing stuff
It helps the team by cadencing the work into focused actions.
We prevent rework, as references' unreleased content may still change (although this is always true for drafts).

What do you guys think? Should we try for the next iterations?

our milestone brings as many changes we can to tag our release for our version, the stable release is the one we tag


Update services.inc  for  warning: array_combine(): dyn_dns_status.widget.php on line 151

Corrects the error in the dynamic DNS widget
warning: array_combine(): both parameters should have an equal number of elements in /usr/local/www/widgets/widgets/dyn_dns_status.widget.php on line 151

[ ] Redmine Issue: https://redmine.pfsense.org/issues/NNNN
[ ] Ready for review

To effectively track changes and bug/feature requests, we require an entry on the pfSense Redmine issue tracker associated with every pull request, and likewise the Redmine entry should also have a link back to the pull request.
Please associate this PR to a Redmine issue either by locating an existing issue at https://redmine.pfsense.org or by creating a new issue. Add a link to the Redmine issue that points to this PR, and also add a link on the PR to the Redmine issue.
For more information, see https://docs.netgate.com/pfsense/en/latest/development/pull-request.html
Thanks!

It's a regression introduced by PR #4500 and can be tracked at https://redmine.pfsense.org/issues/11420


Liveness Check for GRPC Server

I now noticed the following behaviour multiple times: The GRPC server fails to process requests when there are some problems with ceph.
Then, the calls are not successful (nothing changed in the database), and the log contains entries like :
	status = StatusCode.UNKNOWN
	details = "Exception calling application: [Errno 107] Socket not connected: '/mnt/ceph/tira/data/runs/touche-23-task-2-validation-re-rank-default-text-20221122-training/touche23-test-maik/2022-11-22-16-42-25/run.prototext'"
	debug_error_string = "{"created":"@1669131967.948182350","description":"Error received from peer ipv4:<IP_ADDRESS>:31553","file":"src/core/lib/surface/call.cc","file_line":1067,"grpc_message":"Exception calling application: [Errno 107] Socket not connected: '/mnt/ceph/tira/data/runs/touche-23-task-2-validation-re-rank-default-text-20221122-training/touche23-test-maik/2022-11-22-16-42-25/run.prototext'","grpc_status":2}"

When I manually restart the GRPC Server, everything works fine again.
We should probably add a liveness probe in this container that checks that the cephfs is properly mounted so that the pods automatically restart in cases as above.

I now checked this in a failed pod: running ls /mnt/ceph/tira already failed. So I added a liveness probe:
        livenessProbe:
          exec:
            command:
            - ls
            - /mnt/ceph/tira
          initialDelaySeconds: 5
          periodSeconds: 5

and ensured that two GRPC servers run in parallel (  replicas: 2).

I deployed this, and with this it is again working (as if I would have restarted the pod).
We need to observe this for some time to see if the liveness probe actually helps.

The liveness check itself works.
However, the underlying problem persists, but is probably easier to solve now.
E.g., few minutes ago, this job failed because the GRPC Server failed with this exception:

At the same time, the liveness probe kicked in (for both pods at exactly the same time):
  Warning  Unhealthy  4m18s (x59 over 22h)  kubelet  Liveness probe failed: command "ls /mnt/ceph/tira" timed out
  Normal   Killing    4m18s (x5 over 162m)  kubelet  Container tira-application-grpc failed liveness probe, will be restarted
  Normal   Pulled     3m45s                 kubelet  Successfully pulled image "registry.webis.de/code-lib/public-images/tira-application-grpc:0.0.14" in 2.359721687s

So the pod is now automatically restarted.
This means, I think we can get it robust by wrapping the job into some failsave mechanism (i.e., try it multiple times with backoff or similar).

The liveness check itself works.
However, the underlying problem persists, but as the liveness probe is correct, I can close this issue.
Work will continue in this ticket: https://github.com/tira-io/tira/issues/307


Error when I try to compile

-- Could NOT find PCRECPP (missing: PCRECPP_LIBRARY PCRE_LIBRARY)
CMake Error at cmake/FindPCRECPP.cmake:28 (message):
  Cannot find pcrecpp libraries.  Terminating.
Call Stack (most recent call first):
  CMakeLists.txt:11 (include)

-- Configuring incomplete, errors occurred!

Archlinux, latest.

Oops, it was FindPCRECPP.cmake file, that contains links to pcrecpp.a while my system has .so libraries.


Integration Test - Release - 2019/02/26 03:36:16

Auto create for integration test. AnotherAuthorUpdatedArticleFlow

@PRMergerTest3 : Thanks for your contribution! The author, @v-caxian, has been notified to review your proposed change.


Updated to GitHubSDK 0.4.1, now using retrofit responses.

Note: Just a quick port, no error handling yet implemented.

This pr opens the possibility to check response.isSuccessful() and do error handling in the callback, right?
On the other hand, I'm curious that what's the current way to handle http error or failed response.

The current way is onError(...) is called on response failure. Discussion on this can be found at Meisolsson/GitHubSdk#8.

@veyndan thanks, the linked discussion content is very useful.


Raises an error on an empty document

RDF::Turtle::Reader.new('', validate: true).statements fails with RDF::ReaderError: Errors found during processing.
I believe a zero character string is a valid turtle document, and that this should parse to an empty set of statements. Is this correct?

I'm having trouble repeating this in an isolated environment. It's probable that this is a dependency issue.

Can't repeat in a base rdf or linkeddata environment. I'll reopen if I can figure out what dependency combination caused this behavior for me.

You should see more detailed messages on street, or whatever the log device is. No reason I can think of that an empty graph would be a problem.


Line editor context menu broken

Can't select properties of tiles anymore (start tile, ramp direction etc.)

Bah.... Some css from somewhere is hiding the checkboxes and radioboxes. I will either change it or make it more stylish using the same markup / classes as in line judge.
Thanks for pointing this out!
You should still be able to use it just by  pressing the words, like pressing "Is start" it will be selected, but you get no visual feedback about it, right?

The "Finish for run" checkbox is affected by this issue as well:

And same for the maze editor! Open new issue?

Solved with newest commits.


[BUG]

Describe the bug
No support for 2 arg /team title commands but page is accepting them anyway
command run: /team title Hi
Caused by: java.lang.NullPointerException
at com.booksaw.betterTeams.Team.getTeamPlayer(Team.java:911) ~[?:?]
at com.booksaw.betterTeams.commands.team.TitleCommand.onCommand(TitleCommand.java:34) ~[?:?]
at com.booksaw.betterTeams.commands.presets.TeamSubCommand.onCommand(TeamSubCommand.java:29) ~[?:?]
at com.booksaw.betterTeams.commands.ParentCommand.onCommand(ParentCommand.java:116) ~[?:?]
at com.booksaw.betterTeams.BooksawCommand.execute(BooksawCommand.java:54) ~[?:?]
... 18 more

This has been fixed and will be included in the next update