transform would get supercharged with access to history item

Good stuff @RomRider.  Thanks for putting this together.
I have a use case where I am trying to chart daily usage of my xfinity internet service.  I am trying to create a bar chart of daily usage for a given 'month so far' and an indication if I am on track to stay under my bandwidth cap (1229 GB/mo).    I have sensors that have a daily history of usage as well as an array of 6 prior months total usage.
So, for any given day/datapoint, I need to:

calculate the perday bandwidth amount (bandwidth_cap/days_in_the_month)
determine what day of the current cycle this data represents (data_timestamp is timestamp of when data was recorded)
calculate thresholds of usage based on (number of days * perday)
color a bar or line segment with red, yellow, or green based on say under 70% (green), 70-90% (yellow), and >90% red.
I need to calculate this for every historical point.

The result should be a set of colorized bars that would show each day individually based on the day into the period.  Note that day 1 could be over but day 2 could be under so the bars would be red then green if day 1 was a busy day and day 2 wasn't.
I have the config-template-card which allows me to use scripting over the entire apexcharts-card, however, this is only good for the current (today) instantiation of the entity.
I am looking at the transform option to provide this info, however, there is no access to the actual history item, instead, we get the historical 'x' value which is the state of the item and full access to the hass.states['sensor.xfinity_usage'] object, but this is again the current value, not the actual item that is being pulled from the history.
I think if there were an option to directly access the object structure item being transformed it would allow this capability.
So this line and this one
I think would just need to pass in the current working item to make it available as a named entity as 'x' or 'hass'.
Here is what a sample graph would look like, ideally the green bars would show based on that data points current usage not the usage as of the day it is being displayed.  The following yaml was attempting to draw a line graph overlay that would show the 70% and 90% threshold lines, but it became clear that data isn't available.  Note, this example is setting color based on the current state, not previous state.

using:
type: 'custom:config-template-card'
variables:
  THIS: 'states[''sensor.xfinity_usage'']'
  tthold: |
    (thresh,THIS) => {
      const date = new Date(THIS.attributes.raw.usageMonths[6].endDate);
      console.log(date);
      const daysmon = date.getDate();
      console.log("daysmon="+daysmon)
      console.log(THIS.attributes.data_timestamp);
      const today = new Date(THIS.attributes.data_timestamp * 1000).getDate();
      console.log(">>" + today);
      const daysleft = daysmon - today ;
      const perday = 1229/daysmon;
      console.log("usage= "+THIS.state);
      return today * perday * thresh;
    }
entities:
  - sensor.xfinity_usage
card:
  type: 'custom:apexcharts-card'
  header:
    show: true
    title: 'Xfinity Usage'
    show_states: false
    colorize_states: true
  update_interval: 12h
  experimental:
    hidden_by_default: true
    color_threshold: true
  apex_config:
    xaxis:
      labels:
        format: M/d
    yaxis:
      min: 0
      max: '${tthold(1,THIS)}'
    legend:
      show: false
    hidden_by_default: true
    color_threshold: true
  span:
    start: day
    offset: '-5d'
  graph_span: 7d
  series:
    - entity: sensor.xfinity_usage
      type: column
      name: Current
      extend_to_end: false
      fill_raw: last
      group_by:
        func: last
        duration: 1d
      show:
        legend_value: false
        datalabels: true
      color_threshold:
        - color: Red
          value: '${tthold(0.9,THIS)}'
        - color: Yellow
          value: '${tthold(0.7,THIS)}'
        - color: Green
          value: 0
    - entity: sensor.xfinity_usage
      transform: "
      console.log('this='+Object.keys(this));
      var THIS = hass.states['sensor.xfinity_usage'];
      const thresh = 0.7;
      console.log('entity='+THIS.attributes.data_timestamp);
      const date = new Date(THIS.attributes.raw.usageMonths[6].endDate);
      console.log(date);
      const daysmon = date.getDate();
      console.log('daysmon='+daysmon);
      console.log(THIS.attributes.data_timestamp);
      const today = new Date(THIS.attributes.data_timestamp * 1000).getDate();
      console.log('>>' + today);
      const daysleft = daysmon - today ;
      const perday = 1229/daysmon;
      console.log('perday='+perday);
      console.log('today='+today);
      console.log('thresh='+thresh);
      console.log('x='+x);

      return x * today * perday * thresh;
      "
      type: line
      name: Current
      extend_to_end: false
      fill_raw: last
      group_by:
        func: last
        duration: 1d
      show:
        legend_value: false
        datalabels: true

As a reference, here what the xfinity_usage sensor looks like, there is essentially some data in the outer block like data_timestamp, usage, and total and then there are 6 months of past usage summaries with usageMonths[6] being this month so far and also contains the start/end date of the current period.
{'data_timestamp':<PHONE_NUMBER>,
              'friendly_name': 'Xfinity Usage',
              'raw': {'courtesyAllowed': 1,
                      'courtesyRemaining': 1,
                      'courtesyUsed': 0,
                      'displayUsage': True,
                      'inPaidOverage': False,
                      'usageMonths': [{'additionalBlocksUsed': 0.0,
                                       'additionalCostPerBlock': 10.0,
                                       'additionalIncluded': 0.0,
                                       'additionalPercentUsed': 0.0,
                                       'additionalRemaining': 0.0,
                                       'additionalUnitsPerBlock': 50.0,
                                       'additionalUsed': 0.0,
                                       'allowableUsage': 1229.0,
                                       'billableOverage': 0.0,
                                       'currentCreditAmount': 0,
                                       'devices': [{'id': 'B0:39:56:99:E4:E1',
                                                    'usage': 931.0}],
                                       'displayUsage': True,
                                       'endDate': '08/31/2020',
                                       'homeUsage': 931.0,
                                       'maxCreditAmount': 0,
                                       'overageCharges': 0.0,
                                       'overageUsed': 0.0,
                                       'policy': 'limited',
                                       'policyName': '1.2 Terabyte Data Plan',
                                       'startDate': '08/01/2020',
                                       'totalUsage': 931.0,
                                       'unitOfMeasure': 'GB',
                                       'wifiUsage': 0.0},
                                      {'additionalBlocksUsed': 0.0,
                                       'additionalCostPerBlock': 10.0,
                                       'additionalIncluded': 0.0,
                                       'additionalPercentUsed': 0.0,
                                       'additionalRemaining': 0.0,
                                       'additionalUnitsPerBlock': 50.0,
                                       'additionalUsed': 0.0,
                                       'allowableUsage': 1229.0,
                                       'billableOverage': 0.0,
                                       'currentCreditAmount': 0,
                                       'devices': [{'id': 'B0:39:56:99:E4:E1',
                                                    'usage': 987.0}],
                                       'displayUsage': True,
                                       'endDate': '09/30/2020',
                                       'homeUsage': 987.0,
                                       'maxCreditAmount': 0,
                                       'overageCharges': 0.0,
                                       'overageUsed': 0.0,
                                       'policy': 'limited',
                                       'policyName': '1.2 Terabyte Data Plan',
                                       'startDate': '09/01/2020',
                                       'totalUsage': 987.0,
                                       'unitOfMeasure': 'GB',
                                       'wifiUsage': 0.0},
                                      {'additionalBlocksUsed': 0.0,
                                       'additionalCostPerBlock': 10.0,
                                       'additionalIncluded': 0.0,
                                       'additionalPercentUsed': 0.0,
                                       'additionalRemaining': 0.0,
                                       'additionalUnitsPerBlock': 50.0,
                                       'additionalUsed': 0.0,
                                       'allowableUsage': 1229.0,
                                       'billableOverage': 0.0,
                                       'currentCreditAmount': 0,
                                       'devices': [{'id': 'B0:39:56:99:E4:E1',
                                                    'usage': 730.0}],
                                       'displayUsage': True,
                                       'endDate': '10/31/2020',
                                       'homeUsage': 730.0,
                                       'maxCreditAmount': 0,
                                       'overageCharges': 0.0,
                                       'overageUsed': 0.0,
                                       'policy': 'limited',
                                       'policyName': '1.2 Terabyte Data Plan',
                                       'startDate': '10/01/2020',
                                       'totalUsage': 730.0,
                                       'unitOfMeasure': 'GB',
                                       'wifiUsage': 0.0},
                                      {'additionalBlocksUsed': 0.0,
                                       'additionalCostPerBlock': 10.0,
                                       'additionalIncluded': 0.0,
                                       'additionalPercentUsed': 0.0,
                                       'additionalRemaining': 0.0,
                                       'additionalUnitsPerBlock': 50.0,
                                       'additionalUsed': 0.0,
                                       'allowableUsage': 1229.0,
                                       'billableOverage': 0.0,
                                       'currentCreditAmount': 0,
                                       'devices': [{'id': 'B0:39:56:99:E4:E1',
                                                    'usage': 850.0}],
                                       'displayUsage': True,
                                       'endDate': '11/30/2020',
                                       'homeUsage': 850.0,
                                       'maxCreditAmount': 0,
                                       'overageCharges': 0.0,
                                       'overageUsed': 0.0,
                                       'policy': 'limited',
                                       'policyName': '1.2 Terabyte Data Plan',
                                       'startDate': '11/01/2020',
                                       'totalUsage': 850.0,
                                       'unitOfMeasure': 'GB',
                                       'wifiUsage': 0.0},
                                      {'additionalBlocksUsed': 0.0,
                                       'additionalCostPerBlock': 10.0,
                                       'additionalIncluded': 0.0,
                                       'additionalPercentUsed': 0.0,
                                       'additionalRemaining': 0.0,
                                       'additionalUnitsPerBlock': 50.0,
                                       'additionalUsed': 0.0,
                                       'allowableUsage': 1229.0,
                                       'billableOverage': 0.0,
                                       'currentCreditAmount': 0,
                                       'devices': [{'id': 'B0:39:56:99:E4:E1',
                                                    'usage': 882.0}],
                                       'displayUsage': True,
                                       'endDate': '12/31/2020',
                                       'homeUsage': 882.0,
                                       'maxCreditAmount': 0,
                                       'overageCharges': 0.0,
                                       'overageUsed': 0.0,
                                       'policy': 'limited',
                                       'policyName': '1.2 Terabyte Data Plan',
                                       'startDate': '12/01/2020',
                                       'totalUsage': 882.0,
                                       'unitOfMeasure': 'GB',
                                       'wifiUsage': 0.0},
                                      {'additionalBlocksUsed': 0.0,
                                       'additionalCostPerBlock': 10.0,
                                       'additionalIncluded': 0.0,
                                       'additionalPercentUsed': 0.0,
                                       'additionalRemaining': 0.0,
                                       'additionalUnitsPerBlock': 50.0,
                                       'additionalUsed': 0.0,
                                       'allowableUsage': 1229.0,
                                       'billableOverage': 0.0,
                                       'currentCreditAmount': 0,
                                       'devices': [{'id': 'B0:39:56:99:E4:E1',
                                                    'usage': 1099.0}],
                                       'displayUsage': True,
                                       'endDate': '01/31/2021',
                                       'homeUsage': 1099.0,
                                       'maxCreditAmount': 0,
                                       'overageCharges': 0.0,
                                       'overageUsed': 0.0,
                                       'policy': 'limited',
                                       'policyName': '1.2 Terabyte Data Plan',
                                       'startDate': '01/01/2021',
                                       'totalUsage': 1099.0,
                                       'unitOfMeasure': 'GB',
                                       'wifiUsage': 0.0},
                                      {'additionalBlocksUsed': 0.0,
                                       'additionalCostPerBlock': 10.0,
                                       'additionalIncluded': 0.0,
                                       'additionalPercentUsed': 0.0,
                                       'additionalRemaining': 0.0,
                                       'additionalUnitsPerBlock': 50.0,
                                       'additionalUsed': 0.0,
                                       'allowableUsage': 1229.0,
                                       'billableOverage': 0.0,
                                       'currentCreditAmount': 0,
                                       'devices': [{'id': 'B0:39:56:99:E4:E1',
                                                    'usage': 205.0}],
                                       'displayUsage': True,
                                       'endDate': '02/28/2021',
                                       'homeUsage': 205.0,
                                       'maxCreditAmount': 0,
                                       'overageCharges': 0.0,
                                       'overageUsed': 0.0,
                                       'policy': 'limited',
                                       'policyName': '1.2 Terabyte Data Plan',
                                       'startDate': '02/01/2021',
                                       'totalUsage': 205.0,
                                       'unitOfMeasure': 'GB',
                                       'wifiUsage': 0.0}]},
              'total': 1229.0,
              'unit_of_measurement': 'GB',
              'units': 'GB',
              'used': 205.0
}

Thanks in advance
-Fred

Hey,
I didn't read through all the code nor try to do the maths on your behalf but it seems you have thought it through. 😊
If what you need is access the full state of the current timestamp (with all the attributes etc...) on top of just the state value for each entry, I can make this happen.
Would that work for you?

Yes, absolutely, that would provide some options for how to present the data.   More broadly, maybe a general mechanism similar to the config-template-card might be a way to add more consistent scripting across the entire card, i.e, not reinventing what args get passed into template, data_generator, and no doubt future yet to be named features ;-)   In my example, there is a function called tthold() that is global to the card from config-template-card, would it be useful to allow the transform/data_generator access to that context?  Just thinking out loud ...
Thanks!

Thank you!  This works well.  Here is a graph that can now plot the % usage for each day:

All I had to do was change the data_timestamp reference from the current xfinity_usage object to the entity as it existed the day it was recorded:
transform: >-
        ...
        console.log(entity.attributes.data_timestamp); const today = new
        Date(entity.attributes.data_timestamp * 1000).getDate();

The red and yellow lines represent the 70% and 90% usage levels for that day of the cycle.  Now that we have this field I think much more interesting graphs can be created.
Thanks again for the quick turnaround!
-Fred


Release 0.12.32 has breaking changes

Hi,
Using Renovate, trying to have the following bump will fail our tests:

FAILED .../test_services.py::test_foo - pydantic_core._pydantic_core.ValidationError: 30 validation errors for LimitOffsetPaginatedResponse[FooResponse]
items.0.bar
  Field required [type=missing, input_value=(<foo.Foo...ect at 0x7f56f02c27b0>,), input_type=Row]
    For further information visit https://errors.pydantic.dev/2.10/v/missing
items.0.baz
  Field required [type=missing, input_value=(<foo.Foo...ect at 0x7f56f02c27b0>,), input_type=Row]
    For further information visit https://errors.pydantic.dev/2.10/v/missing
...

Also, this simple function would fail with the new version:
    def get_all_foos(self: Self) -> LimitOffsetResponse[FooResponse]:
        """Get all foos."""
        get_foos_query = self._session.query(Foo)

        result = paginate(
            self._session,
            get_foos_query,
            additional_data={"message": "OK"},
        )
        return result

And the page is

customizers = [
    UseFieldsAliases(
        items="details",  # `details` contains the list of items.
    ),
    UseAdditionalFields(
        message=str,  # `message` is always there.
    ),
    UseIncludeTotal(True),
]

DEFAULT_RESULT_SIZE: Final[int] = 10  #: Default number of items per response.
MAX_RESULT_SIZE: Final[int] = 1000  #: Maximum number of items per response.

T = TypeVar("T")

LimitOffsetResponse = CustomizedPage[
    LimitOffsetPage[T],
    UseName("LimitOffsetPaginatedResponse"),
    UseParamsFields(
        limit=Query(DEFAULT_RESULT_SIZE, ge=1, le=MAX_RESULT_SIZE, description="Page size limit"),
        offset=Query(0, ge=0, description="Page offset"),
    ),
    *customizers,
]

I obviously removed many many lines (and changed some names).
For now, I just wanted to report the bare minimum to showcase what type of failures we get. And if that's not helpful, I'll try coming up with a minimal example in a few days / weeks.

Hi @Mulugruntz,
It's related to #1383, it will be fixed in next release

Hi @Mulugruntz,
New version 0.12.33 has been released, this issue should be fixed now.

@uriyyo Thanks, going to reactivate it and see how it gets picked up!

The tests have passed. Thanks @uriyyo :)


mmcsd: fix a typo

@gneworld - This is an indication you need to build and test your work before submitting it. Please ensure you have configuration that enable and build you changes provide  them in the test section.


loratap is now cover

Loratap is now workign as a cover, not just 3 buttons

Actually this is how I originally implemented it, but the reporter said it is not working.

For my loratap switch, my version works like a charm. Should I create a brand new yaml, like loratap_cover.yaml?

No, the issues reported were not with the device itself, but the HA cover interface.  I made some changes to try to fix it, and maybe the reporter was not testing the updated version when they reported the fixes did not work.


update egui and egui_baseview

updated to use the latest version of egui and egui_baseview

Thanks for the effort!


Loss of PPS input question

In the second figure, under the TIMESTAMP_UPR register description, it appears like the period of the last PPS signal is shorter than the previous two pulses, as evidenced by attributes in the UTC_TIME_LWR (time period of the last increment was shorter, when compared to the previous two cycles.
https://github.com/ajn96/iSensor-SPI-Buffer/blob/master/REGISTER_DEFINITION.md#TIMESTAMP_UPR
Could this be indicative of a signal artifact, which came from the act of removing the PPS clock signal?  In other words, did a glitch cause this to trigger sooner than it would have otherwise or is there another reason for the difference in period?  Thank you!

Hi Mark,
You're correct, the short period on the last PPS input period was likely due to an input glitch when disabling the PPS signal.
The PPS input to the SPI buffer for this image was being generated by an FX3 PWM output (1Hz, 50% duty cycle). When a PWM output is disabled on the FX3, the pin is tri-stated. This caused a low to high transition to be seen by the SPI buffer, which triggered the PPS ISR (DIO_INPUT_CONFIG PPS Polarity bit was set to 0).
Do you think it would be valuable to detect an error like this for the PPS_UNLOCK bit? Currently, this bit is only set when the PPS signal is lost - it would be easy enough to flag an invalid PPS period as well (allowed freq of 1Hz +- 3%).

Thank you, Alex!
This confirmation helps strengthen my understanding of this function, which by the way, is pretty cool!
With respect to detecting an error, based on the time period, I can imagine that being useful.  What would limit the precision of this detection method?

Thank you, Alex!
This confirmation helps strengthen my understanding of this function, which by the way, is pretty cool!
With respect to detecting an error, based on the time period, I can imagine that being useful. What would limit the precision of this detection method?

There are two major limits to the precision of the PPS error detection:

CPU activity can make interrupt latency (to process PPS edge) somewhat variable. The PPS input has a lower interrupt priority than the user SPI, so if the processor is executing the user SPI ISR when the PPS input comes in the "measured" period could be off by ~1us. In addition, the PPS input shares the same interrupt vector as the IMU data ready, so if an IMU data ready comes in just before the PPS that could push the inaccuracy of the period measurement out further.
Accuracy of the crystal used to clock the SPI buffer. 20ppm shouldn't drift much over 1 second, but wouldn't want to pull the margins in too close and start reporting false PPS_UNLOCK failures.

Thinking about the possible error sources more now, I suspect I could very safely assert an error if the PPS period is off by +-10ms (1%).
It might be possible to set up another timer peripheral on the ST processor to operate in input capture mode to monitor the PPS input, which would give much more precise and accurate timing measurements.

Thank you!  Based on what I know so far, +/-1% seems like it would suffice.  Perhaps some applications will value more precise detection, but I am not sure that should be the responsibility of the IMU (which in this context, would include this FIFO/Buffer). I will keep thinking about this, in my research.  Thank you for the education on the capability.

Added +- 1% error detection on release 1.3


Comments no longer have syntax hightlight

Install https://marketplace.visualstudio.com/items?itemName=arcensoth.language-mcfunction


EXSWHTEC-359 - Implement tests for 3D mipmapped texture device functions

tex3DLod
tex3DGrad.

Depends-on: #368

PR has been merged into develop branch via commit<PHONE_NUMBER>047056a869ddfd12758ff26453699e.


introduce backends.common to reduce circular dependencies

The backends module and modules llama_cpp and vllm have circular dependency, which is anti-pattern.
The backends module, along with the llama_cpp and vllm modules, have a circular dependencies, which is considered an anti-pattern."
This PR is intentionally kept small to facilitate an easier code review. The plan is to relocate the relevant code from backends to common in a subsequent PR, eliminating the circular dependency entirely.
Current state:
graph LR;
  backends --> llama_cpp
  llama_cpp --> backends
  backends --> vllm
  vllm --> backends

Desired state:
graph LR;
  backends --> llama_cpp
  llama_cpp -->common
  backends --> common
  backends --> vllm
  vllm --> common

References:

https://en.wikipedia.org/wiki/Circular_dependency
https://en.wikipedia.org/wiki/Acyclic_dependencies_principle

@makelinux could you link the follow-up PR if it's ready? Might be better to merge these 2 in succession.

@makelinux could you link the follow-up PR if it's ready? Might be better to merge these 2 in succession.
@khaledsulayman,

Unfortunately, it's not practical to submit several commits or pull requests simultaneously. Combining multiple changes in a single pull request increases the risk of merge conflicts and may require multiple rebases. Creating a pull request based on another is also challenging, if not impossible. If you have any suggestions or know of a workaround, please let me know.


overflow removed

As mentioned in issue #462 i have dealt with the overflow in x direction that was happening with properties like flex and flex-wrap.
Because there was content being repeated in the head tag of index.html and navbar.html, I have also deleted it
Earlier:

Now:

There have a conflict issue plz check it once. and then recreate a new PR. ok

Sir I've resolved the conflicts. You can check here

I have made a new PR #555


Add a filter to issue-2895

Should skip the test in Node 0.12, which doesn't support const.

O noes, this was almost an all-green PR! 😆

Thanks


Setup large-scale test cluster with GKE credits

Stages:

[x] 256 nodes
[x] 512 nodes
[x] 1024 nodes
[x] 2048 nodes

Done and achieved


Xamarin.Build.Download - Error : Cannot create a file when that file already exists.

Agent Version and Platform
Using "windows-2022" as vmImage for the pool.
The exact issue on some agents is :
[error]C:\Users\VssAdministrator\.nuget\packages\xamarin.build.download\0.11.0\buildTransitive\Xamarin.Build.Download.targets(52,3): Error : Cannot create a file when that file already exists.

Set build variables.
Download all required tasks.
Downloading task: gitversion/setup (0.9.14)
Downloading task: gitversion/execute (0.9.14)
Downloading task: NuGetToolInstaller (1.208.1)
Downloading task: MSBuild (1.211.0)
Downloading task: PublishBuildArtifacts (1.200.0)
Downloading task: PostBuildCleanup (3.1.1)
Checking job knob settings.
   Knob: AgentToolsDirectory = C:\hostedtoolcache\windows Source: ${AGENT_TOOLSDIRECTORY}
   Knob: AgentPerflog = C:\agents\perflog Source: ${VSTS_AGENT_PERFLOG}
Finished checking job knob settings.
Plugin: 'Test Result Parser plugin' is running in background.
Plugin: 'Test File Publisher plugin' is running in background.
Start tracking orphan processes.
Finishing: Initialize job

OS of the machine running the agent? Windows
Azure DevOps Type and Version
What's not working?
All agents named "WIN-XXX" will produce a Xamarin.Build.Download error :
[error]C:\Users\VssAdministrator\.nuget\packages\xamarin.build.download\0.11.0\buildTransitive\Xamarin.Build.Download.targets(52,3): Error : Cannot create a file when that file already exists.
Agent machine name: 'fv-az132-286' IS WORKING  and does NOT produce this error.
Question is : what is different between  fv-az132-286 AND WIN-47H1L50AF85
We tried to specify the agent computer name but it throws. Also this is not a viable fix.
No agent found in pool Azure Pipelines which satisfies the following demand: Agent.ComputerName. All demands: Agent.ComputerName -equals fv-az132-286, Agent.Version -gtVersion 2.163.1
Agent and Worker's Diagnostic Logs
[error]C:\Users\VssAdministrator\.nuget\packages\xamarin.build.download\0.11.0\buildTransitive\Xamarin.Build.Download.targets(52,3): Error : Cannot create a file when that file already exists.

@vincentcastagna thank you for reporting that!
Could you please confirm that the same pipelines fail on one agent but work fine on another, depending on the selected agent?
Is it possible to share a minimal pipeline defenition that has this issue?


Publishing: Gitlab support

Add support for publishing Helm charts in the Gitlab Package Registry.
Closes unbroken-dome/gradle-helm-plugin#132

Great work, thank you!


SwiftDriver: initial work to properly handle android cross-compilation

The intent here is to permit the Windows/macOS style cross-compilation for Android. This involves passing -sdk with the path to the "Swift SDK" which overlays the system's native SDK (NDK). The ANDROID_NDK_ROOT is a well-defined environment variable (setup by the SDK installer as well as a general expectation for Android development) that identifies the root of the installation of the NDK. This allows us to locate the native SDK root (--sysroot) for driving the linker driver amongst other paths.

With this set of changes I am down to:
swiftc -target aarch64-unknown-linux-android28 -sdk "S:\Program Files\Swift\Platforms\Android.platform\Developer\SDKs\Android.sdk" -emit-executable -o hello hello.swift -Xclang-linker "-LS:\Program Files\Swift\Platforms\Android.platform\Developer\SDKs\Android.sdk\usr\lib\swift\android\aarch64" -Xclang-linker -resource-dir -Xclang-linker S:\b\android-ndk-r26b\toolchains\llvm\prebuilt\windows-x86_64\lib\clang\17

The bits that I would like to remove:
-Xclang-linker "-LS:\Program Files\Swift\Platforms\Android.platform\Developer\SDKs\Android.sdk\usr\lib\swift\android\aarch64"

This feels like we are failing to setup the library search path when we have a -sdk parameter for the layout like we do on Windows.
-Xclang-linker -resource-dir -Xclang-linker S:\b\android-ndk-r26b\toolchains\llvm\prebuilt\windows-x86_64\lib\clang\17

This is due to my builds missing clang_rt.builtins-... for Android and so we need to pull some files from the NDK.
Addressing those two issues would give us the following invocation:
swiftc -target aarch64-unknown-linux-android28 -sdk "S:\Program Files\Swift\Platforms\Android.platform\Developer\SDKs\Android.sdk" -emit-executable -o hello hello.swift

and with SDKROOT set to S:\Program Files\Swift\Platforms\Android.platform\Developer\SDKs\Android.sdk and ANDROID_NDK_ROOT set to S:\b\android-ndk-r26b, we should then be able to build code as:
swiftc -target aarch64-unknown-linux-android28 -emit-executable -o reduced reduced.swift

The reason this entire approach doesn't already work is because of a regression in this new Swift Driver, see #1562. We should fix that for all platforms, not paper over it with these Android-specific changes.

I'm not sure I'm following the "papering over" here. The idea here is to default the -sdk parameter for android targets using ANDROID_NDK_ROOT, and subsequently -sysroot as well. You can always explicitly specify the parameters. We do something similar for Windows where SDKROOT will be used to default the parameter for -sdk on Windows, and we query the registry for determining the path to the various system include directories.

There are two aspects to this pull, having this new swift driver read environment variables like SDKROOT/ANDROID_NDK_ROOT and looking in those paths for the right build files.
I don't think we should hard-code such environment variables in this driver, but always "explicitly specify" them, as you say. As for finding build files, the reason that doesn't work already is #1562: take a look at my detailed writeup from a couple weeks ago for why.

I disagree with you on that point. I would like the default value behavior for the targets where possible, much as it works on macOS. Fixing the behavior to work with the parameters however should be done.

@artemcm, as I already said, this should not be merged, as this is largely an Android-specific hack to paper over the real fix for all platforms, swiftlang/swift#72409, which has not been worked on for the last three months.

@swift-ci please test

@swift-ci please test Windows platform

@compnerd, I think you've found a real bug in this repo with locating the Swift SDK overlay modules and headers in an SDK, which his swiftlang/swift#72409 fixes more generally.
Can you try reverting this pull in your local build, applying that frontend patch instead, and see if it fixes most of these issues? If it doesn't, you can pare this down to fix what's left, as that frontend fix will be needed for all platforms and should fix most of your issues here.

@artemcm I kept the 'swiftrt.o' adjustment based on the SDK path in this patch. https://github.com/swiftlang/swift/pull/72409 does not work for Android specifically as I mentioned in that PR, as with that change Swift is unable to find the clang builtin headers next to the toolchain, which are separate from the Android SDK.

@swift-ci please test

@artemcm do you think this needs further changes?

At a high-level, I think that this is the right direction. swiftrt.o is tied to the runtime. If it gets mismatched with the runtime, programs will explode. If the compiler generates extra metadata segments that the runtime doesn't know about, then they'll just be  dead weight and won't get loaded and it should mostly be fine because the runtime won't try to use them. (We do need an availability story there though, but that's not about swiftrt.o). This does mean that the compiler needs to be at least as old as the runtime that it's building for though. (Technically, without any ABI stability story, you can't mix-and-match versions of the compiler and SDK though... And the swiftmodules in the SDK won't work with a mismatched compiler anyway? So maybe that's fine???)
But I would also like to ask for something of a vision document listing out what each of the files in the current Linux toolchain/SDK are tied to so that when they move, it doesn't come as a surprise and there is something we can discuss and point to instead of a smattering of compiler changes. When it comes down to it, the toolchain files should be pretty easy to move. Move the file and update the compiler at the same time, and since they're tied to that specific compiler, if anyone complains about a missing file, it means they were living life on the edge and were getting very lucky regarding ABI. SDK content is maybe a bit weirder, but given that, for now anyway, the Linux SDKs are sort of tied to a specific compiler build through ABI instability and rev-locked swiftmodule files, maybe it's okay?
Apple platforms and Windows both need to support the split builds due to how the SDKs and toolchains are split in Xcode and how libraries work on Windows, which is why they both look remarkably similar in terms of the layout. swiftrt.o(bj) is only relevant to Windows because the dynamic loader on Darwin knows how to unpack the runtime metadata from binaries automatically so it isn't necessary. Linux is the odd one where you can build against the system you're running on, and unfortunately that allowed for a disorganized Linux build. As you noted, @finagolfin, the Linux installs have the compiler running on a different Swift runtime than the one it was built against. We've gotten very lucky that things have played out as well as they have. Untangling it will require moving files to the appropriate locations though.

Honestly, the swiftrt.o change in this pull is superfluous and unnecessary if swiftlang/swift#72409 is applied. Rather, this helps to change where the runtime libraries are placed, ie in arch-dependent directories, and change the meaning of -resource-dir just for this one SDK.
See the discussion on swiftlang/swift#72409 for more info on what they're doing.

I suspect this is causing macOS PR testing failures, not clear yet how.
https://ci.swift.org/job/swift-PR-macos-smoke-test/14409/


master documentation is not building automatically

While the documentation for the develop branch is now building freshly on each merged pull request, the master documentation is out of date. This was evidenced by #1403, which pointed out that the multiclass classification notebook (master) had a bug, whereas everything was working fine as expected in the develop version. (Note that the master docs have been re-started manually to fix this for now.)

Thanks to @vdutor for manually kick-starting the documentation build for master as a one-off - this brings the documentation up to date with the 2.0 release from yesterday. We should automate this in the long run, but has lower priority for now.

my mistake sorry


Fix release chart action

What this PR does / why we need it:
/cc @locustbaby @samhuang-z
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ ] Chart Version bumped
[ ] Variables are documented in the README.md
[ ] Title of the PR starts with chart name (e.g. [mychartname])
[ ] PR only contains changes for one chart

/lgtm

/lgtm


Add Clone implementation for SharedItem and SharedError

This addresses https://github.com/alexcrichton/futures-rs/pull/528#issue-240380014.
This change would benefit users of the gltf crate as they would be able to make cheap immutable copies of the acquired data.

Thanks!


Mecanum drive manager class

New file called MecanumDriveManager.java. Basically my version of the SampleMecanumDrive class the roadrunner quickstart provides.

Closed in #38.


Options for SwaggerUI like OAuthClientId and OAuthAdditionalQueryStringParams

Is there a way to configure swaggerUI options like :
c.OAuthClientId(apiSettings.ClientId);
c.OAuthAdditionalQueryStringParams(new Dictionary<string, string>
{
    { "resource", $"{apiSettings.ClientId}"}
});

Hi, @sadiqkhoja
I've never tried to.
Can you drop me a link to the docs and give an example why do you need them?
Thanks

I would also appreciate if this was possible. I managed to configure your great extension to use our ID server, but UI requires Client ID every time which is annoying. Also, it would be good to be able to set different oauth2RedirectUrl because there is no default static /oauth2-redirect.html file. However, it is easy enough to serve one. It might be a valuable resource in the static resources of this library as well, to keep things aligned.

I would also appreciate if this was possible. I managed to configure your great extension to use our ID server, but UI requires Client ID every time which is annoying. Also, it would be good to be able to set different oauth2RedirectUrl because there is no default static /oauth2-redirect.html file. However, it is easy enough to serve one. It might be a valuable resource in the static resources of this library as well, to keep things aligned.

We are currently exploring to add Swagger for azure functions and this package helped solve our purpose, however would like to have OAuth enabled for user to be able to auth using Azure AD and make requests. any update if this feature is being worked on?

We are currently exploring to add Swagger for azure functions and this package helped solve our purpose, however would like to have OAuth enabled for user to be able to auth using Azure AD and make requests. any update if this feature is being worked on?

Related pull request: https://github.com/vitalybibikov/AzureExtensions.Swashbuckle/pull/61

Related pull request: https://github.com/vitalybibikov/AzureExtensions.Swashbuckle/pull/61

Released in 3.3.2


Fixes configuration constant names used inside .sh file

Constants used inside ./script.sh doesn't match the ones defined inside a sample config.example.tcl, what throws an error while running the script.
This pull request is supposed to fix the problem, so other people doesn't face it using sample configuration file.

Thank you for fixing this. For some strange reason I fixed mine but for completely forgot to fix the template file.


Add a Gitter chat badge to README.md

alehander42/pseudo now has a Chat Room on Gitter
@alehander42 has just created a chat room. You can visit it here: https://gitter.im/alehander42/pseudo.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Current coverage is 85.01%

Merging #1 into master will not affect coverage as of c6e3a66

@@            master      #1   diff @@
======================================
  Files           45      45
  Stmts         1808    1808
  Branches         0       0
  Methods          0       0
======================================
  Hit           1537    1537
  Partial          0       0
  Missed         271     271

Review entire Coverage Diff as of c6e3a66

Powered by Codecov. Updated on successful CI builds.


access control engine and endpoint configuration

PR Checklist

[ ] A description of the changes is added to the description of this PR.
[ ] If there is a related issue, make sure it is linked to this PR.
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added or modified a feature, documentation in docs is updated

Description of changes

@xx-db

lgtm besides a few nits. Do we ever need to worry about having different keys for the same resourceType? like something that got passed in both in pathparam and payload.

I don't entirely envision that, but if it does happen, hopefully they would match and would just pick one.


Fix compile issues

Fixes #211

Thank you @whmountains. It looks good! However, you've accidentally committed a yarn.lock file as well and made changes to tsconfig.json.
#205 fixes this as well. But if we want to do a release using TypeScript 2.0 then I think we should merge this.

Thank you for the PR. But the compiler issues has now been fixed by #205.


feat(server): add new hook render:beforeResponse

Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[x] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

Resolves: #7468
It also allows to overwrite headers set by next renderer.
Checklist:

[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[x] All new and existing tests are passing.

Codecov Report

Merging #7469 into dev will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##              dev    #7469   +/-   ##
=======================================
  Coverage   70.32%   70.32%
=======================================
  Files          88       88
  Lines        3704     3704
  Branches     1010     1010
=======================================
  Hits         2605     2605
  Misses        892      892
  Partials      207      207

Flag
Coverage Δ

#unittests
70.32% <100.00%> (ø)

Impacted Files
Coverage Δ

packages/server/src/middleware/nuxt.js
97.46% <100.00%> (ø)

Continue to review full report at Codecov.

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

Thanks @Dima000 :heart:

Please don't forget to alter the documentation as well.

I'll do a PR to the docs this week.
Thanks for the feedback guys and thanks for mentaining this awesome project


JSON records to Parquet on S3 won't work

Hi
I would like to write parquet directly on S3 my events are only JSON string.
Do you know if what I'm trying to do can work ?
In fact I've already tried with this config

{
"name": "ParquetS3",
"config": {
"name": "ParquetS3",
"connector.class": "com.qubole.streamx.s3.S3SinkConnector",
"format.class": "io.confluent.connect.hdfs.parquet.ParquetFormat",
"partitioner.class": "io.confluent.connect.hdfs.partitioner.HourlyPartitioner",
"locale": "en",
"timezone": "UTC",
"tasks.max": 11,
"topics": "XXX",
"flush.size": 50000,
"s3.url": "s3n://XXXXX",
"hadoop.conf.dir": "/etc/kafka-connect-s3/hadoop-conf"
}
}

it's actually don't work
The only error I can see in the log is

Task ParquetS3-56 threw an uncaught and unrecoverable exception (org.apache.kafka.connect.runtime.WorkerTask:141)
java.lang.NullPointerException
at io.confluent.connect.hdfs.DataWriter.close(DataWriter.java:299)
at io.confluent.connect.hdfs.HdfsSinkTask.close(HdfsSinkTask.java:122)
at org.apache.kafka.connect.runtime.WorkerSinkTask.commitOffsets(WorkerSinkTask.java:317)
at org.apache.kafka.connect.runtime.WorkerSinkTask.closePartitions(WorkerSinkTask.java:480)
at org.apache.kafka.connect.runtime.WorkerSinkTask.execute(WorkerSinkTask.java:152)
at org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:139)
at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:182)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)

Is there any other log output for streamX connector
Thanks

@inneractive-opensrc This doesn't work because the io.confluent.connect.hdfs.parquet.ParquetFormat class expects the source data being read into the formatter to be Avro format. If you check out my fork, I've added the ability to convert CSV sourced data to Parquet before uploading to S3, which is very similar to what you want. You'd just need to write similar functionality that converts the source data from JSON (instead of CSV) to Parquet.


Create directory with configs for our prow and other CI infrastructure.

This directory contains configs for prow, boskos and gunernator.
They were generated by copying over some stuff from kubernetes/test-infra
and knative/test-infra, and modifying them until they worked.

/lgtm


Voronoi Analysis works fine for 128 atoms but fails for 250 atoms and larger

Describe the bug
I calculate:
np.mean(lst), np.max(lst), np.min(lst), np.std(lst)
(17.652945, 17.65295, 17.652939, 2.5246266e-06)  # small cell
(26.47941835024731, 70.12143498554614, 17.3288579518855, 14.405461275280086)   # large cell

To Reproduce
https://github.com/jan-janssen/ovito-vs-pyscal/blob/master/ovito-vs-pyscal-voronoi.ipynb
Expected behavior
The mean, maximum, minimum and standard deviation should not change when changing the simulation cell
Additional context
The melting point calculations seem to be all fine for fcc, bcc and diamond structures just hcp fails:
https://github.com/jan-janssen/pyiron_meltingpoint

Thanks for pointing this out. Now fixed. I will make a release soon.

I can confirm it is fixed with the new release. I now opened a pull request for migrating the melting point protocol to pyscal and the results look very promising https://github.com/pyiron/pyiron_meltingpoint/pull/9#issuecomment-738643029 - maybe you can even use it to compare your melting points.


"Invalid size" error thrown before trimming occurs

The attached image has a lot of transparent padding causing it to be larger than options.width & options.height, and the "Invalid size" error is thrown by PackProcessor.
Trimming any transparent pixels should take effect before minWidth and minHeight are calculated.
To Reproduce
Using this image...
await packAsync(
    [{
        path: 'a.png',
        contents: await readFile('a.png')
    }],
    {
        exporter: 'JsonHash',
        textureFormat: 'png',
        textureName: 'a.png',
        width: 2048,
        height: 2048,
        allowTrim: true
    }
);

This produces an Invalid size error.
Note that if you bypass the error by settingoptions.width = 6000 & options.height = 6000 the atlas is packed and the resulting image size is only 112x32 (well within the 2048x2048 limits).

I am facing the same problem - any update on a fix @odrick ?


Drag and Drop inside VSCode not working with Linux/Wayland

Does this issue occur when all extensions are disabled?: Yes

Version: 1.87.0
Commit: 019f4d1419fbc8219a181fab7892ebccf7ee29a2
Date: 2024-02-27T23:42:16.599Z
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 6.7.8-arch1-1
Steps to Reproduce:

Start VSCode with the flag --ozone-platform=wayland
Drag a file from the file tree to the right side to open an editor
while dragging a the mouse has a drag-handle named with the filename
when dropping, nothing happens.
same happens, wenn i want to sort/rearrange the open editors to move one editor to the right side (when using split panes)

now remove the --ozone-platform=wayland, vscode now runs with X11. Drag/Drop now works as expected.
As i use the --ozone-platform-Setting since many months i'm sure this happend with the latest update (yesterday).

Stop: It looks like it is an interference with my system. After downgrading VSCode the same happens. So it looks like it is a problem with new new Plasma6/KDE and vscode (no other app has the same problem).

duplicate of #156723
closing it here.


There is no items in dropdown menu of Packer Installation

I installed packer-plugin on plugin management page.
I added packer to publisher step but I can do nothing anymore.
No item is not shown in dropdown menu of Packer Installation.
What should I check to run?

Getting the same error. Whats the issue / workaround?


Add abnormal_flag to sender CSV schemas

This PR add abnormal_flag to sender CSV schemas so it can be used in receiver filtering.
Test Steps:

Copy settings from attached file for il into local organizations.yml file
Run ./prime data command with attached test file for organization with csv-upload-covid-19 schema

Changes

adds abnormal_flag to

Checklist
Testing

[ x] Tested locally?
[x ] Ran ./prime test or ./gradlew testSmoke against local Docker ReportStream container?

Process

[ ] Are there licensing issues with any new dependencies introduced?
[X ] Includes a summary of what a code reviewer should test/verify?
[ ] Updated the release notes?
[ ] Database changes are submitted as a separate PR?
[ ] DevOps team has been notified if PR requires ops support?

Linked Issues

Fixes #8269

To Be Done
Create GitHub issues to track the work remaining, if any

#8086
Il-new filter-settings.txt
test.csv

test.csv
Il-new filter-settings.txt

Great job you done, @GilmoreA6.  Reviewed, Tested, and Verified.  Approved.


All SVG tags are focusable in IE11 (Icon component)

Detailed description

Describe in detail the issue you're having.

IE11 does not handle SVG's properly and allows all of them to be focusable. In most cases, SVG's should not be focusable (either because they are not interactive or the button around them should be the part gaining focus).

Is this issue related to a specific component?

Yes, the Icon component, which is used to display SVG's

What would you like to see changed?

If I'm not mistaken, this should be fixable by adding a focusable="false" attribute to the svg tag here: https://github.com/IBM/carbon-components-react/blob/master/src/components/Icon/Icon.js#L135
(Based on this SO article: https://stackoverflow.com/questions/29393144/how-to-prevent-svg-elements-from-gaining-focus-with-tabs-in-ie11)

What browser are you working in?

IE11

What version of the Carbon Design System are you using?

6.32.4

What offering/product do you work on? Any pressing ship or release dates we should be aware of?

Watson Compare & Comply Tooling UI

Given whether an icon should take focus depends on its usage, the attribute should be set by components using <Icon>. Here's an example: https://github.com/IBM/carbon-components-react/blob/v6.38.0/src/components/OverflowMenu/OverflowMenu.js#L523

That would help us for cases in which we control the Icon component, but Icon is also used within the components in this library without focusable: false being set (e.g. https://github.com/IBM/carbon-components-react/blob/master/src/components/ListBox/ListBoxMenuIcon.js#L29). I still think the best option is to set a default value of false to focusable in the Icon component, and let users override it as necessary.

@ColbyJohnIBM I thought of your option, but reluctant to do so esp. given shorter lifecycle IE11 has toward the future. Meanwhile, do you want to enter issues where we have icons (in non-<Icon> components) that shouldn't get focus but gets focus with IE? Thanks!

It would fix our issues if the components here would make sure their uses of Icon all had focusable="false" attributes. I would provide a list of locations of Icon usages that don't have this attribute, but I don't have the repo pulled down locally. I think most IDEs should be able to help with finding all such occurrences and making those changes. (I'm not aware of how to search through all files using the GH webapp. If there's a way to do that, please let me know and I'll use it to find these occurrences.)

Thank you for your thought @ColbyJohnIBM - Probably GH search box? Assuming you are using carbon-components-react, you can use your editor to look for code in node_modules/carbon-components-react/es also.


Use i18n for the whole app

Is your feature request related to a problem?
#711 added support for i18n-translation.
As a first example this headline was translated.
Translations (for i.e. English) will be maintained in this file.
Describe the solution you'd like
All other strings in the app need to be replaced by i18n-placeholders and moved to the en.json.
It should be somewhat possible to guess where a certain string is being used by looking at a structured json-file.
Could be good to look at other projects using the same plugin, i.e.

https://github.com/cstenglein/raspiblitz-web/blob/master/src/i18n/langs/en.json
...happy for further examples

This can be done in multiple steps. If you are interested to give this a try maybe start with a PR for one section first and get feedback first before moving on.
Are you working on this?
No

thanks willing to push translation pr's as soon  as possible

Via Weblate after approving the OSS libre hosting plan:

Don’t forget to mention you use Weblate in the README and the website of your project! You can use the lovely stuff from the Share menu of your Weblate project for it.

Let's support them with mentions.

Hello, I've started working on this here. This just includes the "welcome" pages since I wanted to receive feedback on that before doing more. Thanks!

It should be somewhat possible to guess where a certain string is being used by looking at a structured json-file.

@escapedcat Should we be optimizing for guessing where strings are in the code or guessing where they are in the UI? For example, in en.json in welcome.choose_connector.alby, I could add a key called new_wallet which contains all the strings for the Alby hosted wallet page, because the enclosing folder for the code with those strings is called NewWallet, or I could just name it something like page because it's the corresponding "page" under the choose_connector.alby key in the UI.

Good question. I think most projects I've seen so far are using a mix.
On one hand you have certain "views" (i.e. a special headlien will only show up on one page) an on the other hand we have more general things like "forms" (i.e. a "sats" input mitht show up in different forms).
Does this help?
Also we have the option to enrich the data Weblate shows, i.e. here we added a screenshot of view which can be added to several related strings'

Yes that helps, I'll take a crack at following a pattern that best combines the particular with the general to optimize for clarity.
As far as Weblate goes, is there a way to export/import strings from/to json so that we don't have to do the duplicate work of adding strings in the repo and in weblate? I'm not really seeing how Weblate is directly connected to i18n in the project

As far as Weblate goes, is there a way to export/import strings from/to json so that we don't have to do the duplicate work of adding strings in the repo and in weblate? I'm not really seeing how Weblate is directly connected to i18n in the project

That's already set up and working, no worries ;)

We will move in further translations step by step via future PRs


Wrong heap space data in Observatory

Fixed situation when compacted heap space contains a wrong data (new space instead of an old space)

Thanks!


[Minor Bug] Resetting to AS from a higher rank while training transfers the gains

I set a Long training at Genin rank
Went to reset my character to Akademi-sei
Gained 24 gains instead of 16

Nothing major and likely part of an intentional process: if you set a training before a boost ends, you still receive the boosted gains even when the boost ends during it.

Hmmm. I think we could probably leave this as is - I'd rather be consistent about "gains are calculated at the start" or "gains are calculated at the end"


MacOS Style Table

Use case
In SwiftUI, the table looks very different than anything readily available in Flutter.  This package should probably create a similar table component with this predefined style.
Proposal
Create a MacosTable widget that allows creating a table that looks like the one you can build natively.

Hey Skyler. We already have #262 for this.


ISPN-8921 KeyStream stream operations use entrySet on remote nodes

Now keySet operations use key set on remote nodes
Clean up keySet/entrySet/values wrappers for interceptors

https://issues.jboss.org/browse/ISPN-8921
https://issues.jboss.org/browse/ISPN-8923
https://issues.jboss.org/browse/ISPN-8924
https://issues.jboss.org/browse/ISPN-8880
https://issues.jboss.org/browse/ISPN-8926
The main changes of this class revolve around the variable entryStream which dictate if the stream operation contains entries or not. This is determined by whether the toKeyFunction is not null (entry) or is null (key).
The whole Original type found in code is to help with typing to prevent passing in the wrong types. But this type is normally just CacheEntry or Object depending on if it is a entryStream or keyStream.  Most of these can be pretty much ignored, including all the ForEach classes. Later at some point I hope to enhance the typing on the IntermediateOperations and that would allow typing all the way down.
I also removed the old *IteratorOperation classes as they are no longer used since we use the new reactive streams iterator implementation.

To be honest this JIRA has a lot of noise and very little substantive changes.
The big change is that the DistributedCacheStream now has a toKeyFilter that based on if it is not null will cause the remote node to fire off a key stream or an entry stream.
I also cleaned up some code in EncoderCache/PrefetchInterceptor so they didn't delegate calls to the cache and instead let them push down to the child CacheSet (which should help for local caches). I believe the EntrySet and KeySet Command wrappers can also ignore the cache, but I haven't changed those yet.
I will try to get some perf #'s difference with doing a size method on a DIST cache tomorrow.

A couple test failures could be related: https://ci.infinispan.org/job/Infinispan/job/PR-5824/6/#showFailuresLink
Looking...

Added a couple more bug fixes that were exposed when moving to keySet (ISPN-8880 and ISPN-8926). @gustavonalle the latter was the cause of my problems :)

The 4 test failures https://ci.infinispan.org/job/Infinispan/job/PR-5824/9/#showFailuresLink seem unrelated.

Added comments, rebased and updated PR description to help a little more :)

Excellent work, merged !


chat titles appear on sidebar

Have the chat titles update on the sidebar on their own

Focusing on Slack


[localization] Add better support for Chinese languages

Different mapbox-streets source versions have different levels/types
of support for Chinese languages. To support Chinese languages, it's
better to map android system Locale to MapLocale dynamically according
to the mapbox-streets source version that is being used.
Android system's Chinese Locales also changed in different android
versions. Add support for new Locales like zh_CN_#Hans (with script
part in Locale).

Created a PR #878 to address this issue.


Automated Package Upgrade

:tada: This PR is included in version 2.2.320 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Created parent tag dosen't show up after restart of obsidian.

While parent tags' nodes will be added by the plugin, as resolved in a previous issue #2 (say #cheese/brie, and #cheese/double_gloucester both exist, but if #cheese itself doesn't exist by itself, a #cheese node will be created by the plugin),  after a restart of Obsidian, the created tag will disapear and it will only reapear following a restart of the plugin.

following the latest update you seem to have forgoten to release the actual plugin as a built main.js file


[Mac] feat: Support screen capture for macOS.

Try adding screen sharing for macOS:
TODO: (1/5)

[x] Screen capture
[x] select screen
[x] Window capture
[x] Select window
[x] Get thumbnail for preview

@hiroshihorie your MacOS version didn't have this issue IIRC. Perhaps there are some insights there?

wow nice find, needs to multiple of 32 ?

hey @vickyleu, Thanks for reporting the issue, and are there any steps to reproduce？


fuse WIP + dynamic route

Coverage remained the same at 87.652% when pulling 5f9999690cc96af697c39153a10819f593534775 on import-part into 084cb43d9152eee3ddbb45539babc8610d262604 on master.


hyperparameters

What are the hyperparameters you set in the COCO dataset, such as batch and workers?

This parameter is your final setting in the COCO dataset


Update documentation examples to reflect newest angular-translate version

The current docs at https://angular-translate.github.io/docs/#/guide/05_using-translate-directive do not reflect the translate-attr changes being introduces with 2.12 (respective working 2.12.1) as a 2.10.x is referred from the sourcecode. Needs a patch.

fixed


✔Update Tutorial Video to Latest | Updated Readme Tutorial

Hey @ayush-t02
issue closes #697

I have updated the Old Tutorial video in the How to Play Page of the website
I covered each new feature added to the website from starting the game to declaring the winner of the game.
Additionally I have updated the Before-Start and After-Win Images in the Readme.md file
Also, I have updated the Readme.md file video tutorial to new one

As you can see both here -
https://github.com/user-attachments/assets/63c531ba-f2a2-493a-a087-70728868b655
https://github.com/user-attachments/assets/458eba50-6e17-4441-a83c-2edd6a4bbc4f
Please take a look and review it.
thankyou!

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for review.

Thank you soo much for contributing to our repository 💗

@aslams2020 the video doesn't seem to work in the readme, take a look at it. Also according to one of the contributors video also has issues in the howtoplay page.

Oh ok , i will look into it.
thanks for clarifying!

just one thing to add, all the issues are coming up in real time deployment and not the local setup.


When a tag tab is loaded upon opening the bank interface, the selected tab's background takes 1 tick to become highlighted

idk when this was fixed, but it no longer occurs.


useCellRangeSelection - Working on this hook, Ability to select cell ranges and single select (UI demo)

Multi-cell range selection and single-cell select feature
Hi @tannerlinsley,  Implemented this new hook, Will this be a good addition to the library?
@gargroh helped me to come up with this idea.

Usage:

Multiple cell range selections can be done using Ctrl + range selection (click and drag). First range selection can be done without Ctrl
Cell selections (and unselection) can be done using Ctrl + click

Compatibility:
This feature works well with useColumnOrder. With useGroupBy, it selects all cells within the range (including empty cells when expanded)
Few details on the implementation:

added cell Id's
state.selectedCells Is a map of cell.id = true, Same as selectedRowIds
I have added instance.cellsById,  actions for start, selecting, end on an instance

Few things I have not considered adding (will work on it, if this is required):

Unselecting cell ranges
Ability to represent like layer for overlapping range selections, but I am thinking if this can be done by keeping count
state.selectedCells : {cell.id :  count, ...}

I am new to contributing to open source, Need your thoughts and feedback.
If this looks good, I have some refactoring left and I will create a PR.. Thanks :)

We could definitely use something like this at our company. I'd love to help out building this in whatever way necessary.

Another question: I think the table should scroll whenever mouse (selecting) reaches its viewport

Update: @israelidanny @tannerlinsley - This PR is merged in react-table-plugins  🎉
Check Documentation and codesandbox
Let me know, what do you think and if it's a good addition here, will raise a PR

I would like to see this integrated with v8 (the next branch). Wanna take a whack at it there? You'll need to look at how other plugins have changed to fit the new architecture.

Yeah, I will have a look at the new architecture.

@tannerlinsley If you have time, Can you please look at the implementation and can review the code? So that we are following the right direction:
Code link,
Codesandbox and Docs

This looks awesome. And yes, the architecture looks pretty good. Things might change a little bit with v8, so I'll keep you posted.


Python a Decision Tree Classifier from Scratch

Pull Request Type
What kind of change does this PR introduce?
[√] Solved an issue/task
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:
What is the current behavior?

Issue Number: [888]
What is the new behavior?
Implement a Decision Tree Classifier from scratch using Python. Do not use libraries like scikit-learn that have pre-implemented classifiers; instead, use basic libraries like NumPy for numerical calculations.
Other information

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out my other projects. Just click here to find more. These projects contain real issues that you can help resolve. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!


fix(#921): i18n added to error page (wip)

Description
i18n not working in ErrorBoundary.
discord username: Yogi#0330
closes #921

Error translation file added to root page.
18next's withTranslation hoc method added.

## Things to check before creating a PR

[ ] I have inspected my topic, checked.
[ ] If it is a core feature, executed detailed tests.

Creating PR rules

[ ] PR must be created for an issue with approved tag. Otherwise PR will be rejected.
[ ] Relevant issue number: The issue number related to PR must be attached to head of PR header, after prefix after prefix # must be attached in parenthesis. A header like this could be used "prefix(#issue_number): PR header" .
[ ] A descriptive and understandable title: The PR title should clearly describe the nature and purpose of the changes. The PR title should be the first thing displayed when the PR is opened. And it should follow the semantic commit rules. For example, a title like "docs(#issueId): Add README.md" can be used.
[ ] Related file selection: Only relevant files should be touched and no other files should be affected.
[ ] Format and Lint Suitability : The code should be made in accordance with a certain format standard and examined according to the lint rules.
[ ] Clean commit history: The commits where the changes are made should be clear and organized.
[ ] Opening PR when job is completed: PR should be opened when job is completed and sent for review by other team members.

Changes

[ ] A new feature (a change that adds a new feature, not a breaking change)
[ ] A new refactor (a change that is not a breaking change, that improves the readability or performance of the code)
[ ] A breaking change
[ ] Documentation change

How were these changes tested?
Please describe the tests you did to test the changes you made. Please also specify your test configuration.
Test Configuration:

Firmware version:
Hardware:
Toolchain:
SDK:

Don't merge this mr as it is.

this bug has already been fixed. I am closing this pr. thanks for your effort.


Investigate what is need to support pypi-based T0 support

Impact of the new feature
Investigate what is needed to support pypi based deployment for the T0 package. Not this is a spec that depends not only on the WMCore repository, but the T0 repository as well:
https://github.com/cms-sw/cmsdist/blob/comp_gcc630/t0.spec
Is your feature request related to a problem? Please describe.
Now that we are building and uploading packages to pypi, we might need to do the same for t0.
Describe the solution you'd like
At present t0 is uploading their own package to pypi and we have a conflict of names. We might need to rename and adjust properly in the requirements.txt on of the the repositories.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
In the spec, you can see both WMCore and T0 repositories are fetched and built
https://github.com/cms-sw/cmsdist/blob/comp_gcc630/t0.spec#L12-L13
One of the problems we have right now is conflict names. When you upload the t0 package, the name is t0  and of course, the packages and modules included are different.
https://github.com/gkfthddk/T0/blob/master/setup_dependencies.py#L49-L58
https://github.com/dmwm/WMCore/blob/master/setup_dependencies.py#L238-L265
After talking to the T0 team, it seems their package has been built but is not used for deployment at present. We would need to make sure they have the dependencies they need from us, directly from pypi.

@jhonatanamado FYI


include the Pageflow version in all the cache keys

It's pretty safe to say we want all caches purged after a version change.
When we do it like this, it's all taken care of.

Coverage increased (+0.0003%) to 99.204% when pulling 72674de22296eeb5009d52bd03249388b744d0ff on scrollytelling:pageflow-version-into-model-cache-key into 40cda2b30048e8af271c2257a224210a5c2667d3 on codevise:master.

Coverage increased (+0.0003%) to 99.204% when pulling 1ea36b795ba64de7c72a244b13ab6741602afb58 on scrollytelling:pageflow-version-into-model-cache-key into 40cda2b30048e8af271c2257a224210a5c2667d3 on codevise:master.


Add apply method to iteratee (with some unrelated renaming)

Current coverage is 100.00%

Merging #42 into master will not affect coverage as of d7a2a32

@@            master     #42   diff @@
======================================
  Files           17      17
  Stmts          425     426     +1
  Branches        34      34
  Methods          0       0
======================================
+ Hit            425     426     +1
  Partial          0       0
  Missed           0       0

Review entire Coverage Diff as of d7a2a32

Powered by Codecov. Updated on successful CI builds.


Revert "Add private host option for private networks support in hyperdrive"

Reverts cloudflare/workers-sdk#4932

Just needs its changeset.


Test issue for new repo

[Enter feedback here]

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

ID: a4487fcf-f79e-2506-7595-7aafb8c66c9f
Version Independent ID: 351f7d7a-6bef-b933-fa5a-09a47854cae7
Content: Add, remove, and arrange favorites in Azure portal
Content Source: benchmark/azure/_placeholder.md
Service: security
GitHub Login: @mgblythe
Microsoft Alias: mblythe

@mgblythe
Thank you for your GitHub issue! Since this is a test for your new repo, I'll go ahead and close this out.


Behavior diverge from othe runtimes on empty fd_read

fd_read or fd_write with a 0 length iovec succeeds on host Linux as well as other Wasm runtimes (Wasmer, Wasmtime, WasmEdge, WAMR).  However, uvwasi returns inval.  This is a result of libuv performing null checks at the start of uv_fs_{read,write}.
I want to raise this issue to see if maintainers wish to converge with other runtimes here.  0 length read or write should intuitively be a no-op, and we can address this edge case in uvwasi without changing libuv.

Seems reasonable to me, approved the PR but will give other maintainers a bit of time to review as well.


DEMO: add transfer-pvc subcommand to migrate pvc data

This PR adds a subcommand to transfer a single PVC from one cluster to another.
A sample invocation of this command is as follows:
crane transfer-pvc --pvc-name foo --source-context=source-ctx --destination-context=destination-ctx

In this sample, you need to have the source-context and destination-context pointing to the cluster and namespace of the pvc Foo.

It is assumed that the source namespace will be equal to the destination namespace, this will change in the future.
The subcommand does not clean-up the resources it creates. In order to clean up manually before running use the following command:

$ oc --context=destination-ctx -n pvc-transfer-source delete pod,cm,secret,svc,route -l app=crane2 && oc --context=destination-ctx -n pvc-transfer-source delete pvc foo && oc --context=source-ctx -n pvc-transfer-source delete pod,cm,secret,svc,route -l app=crane2

Currently the tool assumes PVC does not exist at the destination. Eventually we might want to provide configuration options to users on how to handle this case

LGTM, create the issues for follow up and then lets merge


@conda-forge-admin, please add bot automerge

@conda-forge-admin, please add bot automerge¶

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/ptitprince-feedstock#5.


Icon Issue

When trying to use the icon unicode code, e8b6, it doesn't display...

It appears like it is a more serious issue.... When in the inspector, and I try to change a button or something like that, I use the following code:
<button class="mdl-button mdl-js-button mdl-button--fab mdl-js-ripple-effect">
  <i class="material-icons">add</i>
</button>

The button just goes to a straight html button with no styling and a plus sign in the center.... possibly an issue with the forum not importing the actual material design stylesheet?

@PartialDevAdmin Can you give me more details about this?

Your theme does not import the stylesheet from https://getmdl.io, so any custom settings, classes, etc. have to be manually entered in the material.css file...

I will add it later.


.github: Add dependabot config

What type of PR is this?
/kind cleanup
/area dependency security release-eng
What this PR does / why we need it:
...because automated dependency updates are super cool!
/assign @puerco @saschagrunert @cpanato
cc: @kubernetes-sigs/release-engineering
Which issue(s) this PR fixes:

Special notes for your reviewer:
Does this PR introduce a user-facing change?

NONE

looks some go mod issue

looks some go mod issue

Needs https://github.com/kubernetes-sigs/k8s-container-image-promoter/pull/337 now that https://github.com/kubernetes/test-infra/pull/22818 has merged.

Needs re-lgtm.

/retest

This will fail the same way again.
/override pull-cip-auditor-e2e
ref: https://github.com/kubernetes-sigs/k8s-container-image-promoter/pull/337#issuecomment-876218433


Crashes on song title >128 characters

Hello, I've noticed the app sometimes crashing on certain musics. It has happened on some of the Apple Music Music Mix lists so I don't know if it's related to the musics not being in my library (but it doesn't seem to be the case as I'm listening to non library music without the app crashing) but that brings me to the second type of crash: titles. I don't know if it's the special character of the title ( called "¿") or the length of the album title Music to listen to~dance to~blaze to~pray to~feed to~sleep to~talk to~grind to~trip to~breathe to~help to~hurt to~scroll to~roll to~love to~hate to~learn Too~plot to~play to~be to~feel to~breed to~sweat to~dream to~hide to~live to~die to~GO TO but something in this music is definitely breaking the app (or Discord limitations maybe). I don't think it's the author as all the other Bring Me The Horizon songs seem to work fine

I figured out the issue, the state has to be <128 characters. I will fix this as soon as I can :)
pypresence.exceptions.ServerError: Child "activity" fails because child "state" fails because "state" length must be less than or equal to 128 characters long

To be honest that's an edge case XD Nice figuring it out tho !

Hi, absolutely love the work! Any updates on this bug?

@@ -67,10 +67,10 @@ def get_rp(info, statuses):

    formatting_args = {
        "status": "Playing" if info[0] == "PLAYING" else "Paused",
        "state": info[0][:125] + "..." if len(info[0]) > 128 else info[0],
        "song": info[1][:125] + "..." if len(info[1]) > 128 else info[1],
        "artist": info[2][:125] + "..." if len(info[2]) > 128 else info[2],
        "album": info[3][:125] + "..." if len(info[3]) > 128 else info[3],
    }

    # Format arguments

I wonder if this code would help solve your code, and you could push out a new release? I tried to make my own pull and compile it but it was missing a lot of the necessary libraries

Awesome, let me know if that works! Looking forward to the next release because this bug is single-handedly driving me the most crazy lol.


PyPi assumes that a Release Version pertains to a particular Python version

Describe the bug
PyPi assumes that a Release Version pertains to a particular Python version. If I have a release version 0.5.0 and twine upload wheel files, some of them with a different Python version requirement, PyPi assumes that all wheel files uploaded under version 0.5.0 require the same Python version. This causes installation problems.
Expected behavior
PyPi recognizes the Python version requirement for each wheel file under the same release version correctly. Pip install chooses the correct wheel files and installation proceeds normally.
To Reproduce
Consider the following wheel files:
MyLib-0.5.0-cp311-cp311-manylinux_2_27_x86_64.whl
MyLib-0.5.0-cp310-cp310-manylinux_2_34_x86_64.whl
MyLib-0.5.0-cp311-cp311-win_amd64.whl
MyLib-0.5.0-cp310-cp310-manylinux_2_34_x86_64.whl
MyLib-0.5.0-cp36-cp36m-manylinux_2_28_x86_64.whl
MyLib-0.5.0-cp312-cp312-manylinux_2_34_x86_64.whl
Each of these binary distribution wheel files have different Python requirement. However, the release version is 0.5.0.
PyPi assumes Python requirements for all these as 3.10.
If we examine the Jason response (https://pypi.org/pypi/MyLib/0.5.0/json), it is:
        "python_version": "cp311",
        "requires_python": "==3.10.*",

and so on.
This causes problems with pip, as it is not able to find the matching wheel files.
My Platform
My Platforms are variant,
Windows & several variants of Linux with varying Python and glibc installations.
Additional context
Same release with wheel files having different Python requirements.

Please provide a real example other than a sample mylib that doesn't have the issue you're showing to help reproduce the issue.

Sure. I will upload the files again and send you the details.
Thanks and best regards,
-Venkat-
Venkateswaran Kasirajan | +1-303-328-8095 |
Author: Fundamentals of Quantum Computing, Theory and Practice
https://www.springer.com/us/book/9783030636883
I fully realize that no wealth or position can long endure, unless built
upon truth and justice; therefore, I will engage in no transaction which
does not benefit all whom it affects. - Napoleon Hill.
On Fri, May 31, 2024 at 1:51 PM Mike Fiedler @.***>
wrote:

Please provide a real example other than a sample mylib that doesn't have
the issue you're showing to help reproduce the issue.
—
Reply to this email directly, view it on GitHub
https://github.com/pypi/warehouse/issues/16033#issuecomment-2142891554,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BI3Q4LHQY2AXHD3JDMTR2QTZFDIFDAVCNFSM6AAAAABITLSZH6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBSHA4TCNJVGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Please see this problem in the test environment:
https://test.pypi.org/pypi/QuantumRingsLib/0.5.0/json
Thanks and best regards
-Venkat-

Do you have an example from the production PyPI instead? The behaviors of TestPyPI may differ, specifically in the end user behavior, and are not always the same as a real production PyPI project.

Hi Mike,
Thanks for your attention on this problem.
I deleted the 0.5.0 files, since we had to send the link to some of our users. The json link gives the same response, which means the internals of both PyPI and TestPyPI should be the same, for this problem.
I will upload again and let you know.
Thanks for the help.

Closing this as a duplicate of https://github.com/pypi/warehouse/issues/8090, which is the root cause of this issue.


Should the shell command precede the Git?

I was wondering if the shell commands should precede the git stuff requires shell work?

That's a reasonable question, the assumption being 'shouldn't we cover shell commands before doing things in git?'
This learning plan assumes that the new hire has some fluency with the command line, so I don't think it matters which order the lessons are in. I'll add a prerequisites section, though, that describes what we assume the person working through this plan can already do.

Yes, that is a better representation of what I was asking.  Sounds like a good plan.


Added the project list command

The command is ocdev project list

Something is not right. After project is created it should be set as active
▶ ./ocdev project list
ACTIVE   NAME
  *      asdf

▶ ./ocdev project create bbb
New project created and now using project : bbb

▶ ./ocdev project list
ACTIVE   NAME
  *      asdf
         bbb

▶ oc project
Using project "asdf" on server "https://<IP_ADDRESS>:8443".

@kadel Done

Tests are OK, travis is currently having some issues with OSX, but all unit and e2e test already passed.

@containscafeine Done


Searches

My bing searches are taking a very long time between searches, up to 15 minutes in-between searches in some cases. I get you don't want them machine gunned, but this seems excessive.

Each search take 20 seconds max, it is a time that avoid to be ban. Also, bing is very slow to show available points on an account.
I will test with a bit less time, I keep you up to date.

I tested, for slow internet connection and slow computers, these delays are pretty good. I don't think we have to change them.


[Xamarin.Forms] Animation does not render properly on iOS

Please run the attached repro and observe that the animation does not render properly on iOS whereas Android works fine. I'd like to know why this is the case so that we can create a PR to fix it.
LottieTest - updated.zip

Hi ! :D
It seems if i'm not wrong, you forgot to add "AnimationViewRenderer.Init();" in the AppDelegate.cs file to use Lottie on iOS (in the FinishedLaunching() function).
More, check your animation, sometimes, on iPhone, animations may be too large for the iPhone screens, for exemple, yours 1080 x 1080 is kinda big.
If you can, reduce it to ~400, animations are made vectorially, so not worry about the quality.
Tell me if you have fixed it :)
Good luck !

@Near0ne My original project had the Init() call, but the issue was still present. I just updated the repro and added that line. Thanks!
As for the size, I have many 1080 x 1080 animations that play perfectly fine on different iPhone models, so I don't think the issue has to do with size.

@Near0ne I think I'm going to have to stop using LottieXamarin since the differences between iOS and Android are killing me. :) I just tested out https://github.com/LottieFiles/lottie-player and it's working great!!

The differences is because it is 2 different render engines. If you use the web version it is only 1. The swift rewrite they did was supposed to make it better but Xamarin doesn't support it properly.

@martijn00 Thank you, Martijn. That's what I thought. I'm hoping Xamarin can support it better in the future. Thanks for your work on getting this library out there for Xamarin folks. :)


Crossing paths yield unexpected fill patterns - brush tool

Reported by @ericrosenbaum during Paint Editor Internal Playtest 7/6/17:

crossing paths results in a weird fill pattern when drawing a closed shape with the brush tool

Chrome, Mac OS
Example

Dupe of https://github.com/fsih/papergrapher/issues/29


Change – to - in documentation

This allows for copying directly into powershell will work
Closes #76033

@bwhybel : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good; thanks.


new card type available, AskForPermissionsConsent

Per https://developer.amazon.com/blogs/alexa/post/75db99e4-dc77-42d1-89d1-aa8b41301324/build-more-engaging-skills-with-device-address-api-and-gain-insights-with-the-new-metrics-dashboard
Here's the specific documentation:
https://developer.amazon.com/public/solutions/alexa/alexa-skills-kit/docs/device-address-api

Please contribute!

Fixed in #225


Add Grid Underlay to 2D Network

To enable users to refine their node layout, adding grid lines would be extremely helpful. We don't need it to be zoom-scaled, just a simple underlay of a static grid (e.g., graph paper) would suffice.

Resolved by 1ee1693


Cannot delete Starting Faction Influence

Describe the bug
Cannot delete Influence, this is for example important for homebrew changes or Astra Telepathica
To Reproduce

Have a character with his faction influence
Try to delete it

Screenshots

Version Numbers
ImpMal 2.0.4

It is tied to the faction item, this is intended

How should this be done?


Add a Reverse of STATUS_CODES

Hi, love the library, using it in my blog, works like a charm 😃
I got a feature request to make. Currently, there's the STATUS_CODES constant. What I am suggesting is something that is revers of that. So, by typing CODES, then ., we'd get intellisense for all the status code messages. This will help people who don't have the codes memorized. Intellisense will remove Googling/Remembering the exact codes out of the equation entirely.
Where to use:

Here, I can replace 422 with CODES['Unprocessable Entity']. This will remove mental overhead while reading the code too :)

Maybe it's just me being weird, but I find the status texts 10x harder to remember. Plus the human-readable names are opinionated by nature; for example, 404 could justifiably be mapped to any one of: NOT_FOUND, PageNotFound, MissingPage
Leaving open with label for other's input here.


Added hash256_file_hex_string

Hash computation for a given file.
The ifstream has to be opened in binary mode, else the returned hash differs from other hashing tools

Thanks @PhilLab
Now hash256 can process istream_iterator.


Fix date format returned by REST API

Coverage increased (+0.009%) to 88.94% when pulling 8363e13d651a55ff79b10a9973dd1f654a91c11e on mprimi:FIX-genie-date-format-via-api into 92968b5a538c59e63a320b366b4335e01842199e on Netflix:3.3.x.


Next

This pull request supersedes PR #517 (which I inadvertently submitted, not understanding how pull requests work, sorry).
Associated functions were added to ByteStream to allow for uploading chunks of data from files, one augments the from_file function and the other the from_path one.
The from_path_chunk function creates its own internal file handle so that it can be called from separate threads.
This submission includes also two examples of how to perform a partial and a multipart file upload.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hello! thanks for opening this pull request—this is definitely a change worth making.
However, this entire repo actually just holds essentially generated code—we actually need the PR in this file: https://github.com/awslabs/smithy-rs/blob/main/rust-runtime/aws-smithy-http/src/byte_stream.rs
(note that we recently landed an unreleased refactoring that uses a builder instead). Let me know if you need any help / guidance porting the PR there.


Player Knockback

We should have a base Knockback value and multiply or divide it based on what player is getting hit.
Owner - The Owner of the rocket should take Knockback * 1.1 (potentially higher?)


SRV Lookup Timeout

Hello,
thanks for Working on this nice Plugin.
I try to setup it up for Prometheus DNS service discovery.
When I try to query a SRV Record the request just runs into an timeout.
MariaDB [dns]> select * from coredns_records;

id
zone
name
ttl
content
record_type

21
mon.local.
nodeexporter._tcp
30
{"Target":"router01.net.mon.local","Weight":0,"Port":9100,"Priority":10}
SRV

22
mon.local.
router01.net
30
{"ip": "<IP_ADDRESS>"}
A

When I try to query the SRV Record I get an Timeout on every DNS Client I tested. The A Record works without an Problem.
In the Log I just see three Requests:
[INFO] [IPV6_ADDRESS]:52152 - 30764 "SRV IN nodeexporter._tcp.mon.local. udp 68 false 4096" NOERROR qr,aa,rd 136 0.001510555s
[INFO] [IPV6_ADDRESS]:52152 - 30764 "SRV IN nodeexporter._tcp.mon.local. udp 68 false 4096" NOERROR qr,aa,rd 136 0.001565826s
[INFO] [IPV6_ADDRESS]:52152 - 30764 "SRV IN nodeexporter._tcp.mon.local. udp 68 false 4096" NOERROR qr,aa,rd 136 0.002095277s

Corefile:
.:53 {
    forward . <IP_ADDRESS> 2620:fe::fe <IP_ADDRESS> 2a05:fc84::43 <IP_ADDRESS>  2001:678:ed0:f000::
    prometheus [::]:9253
    errors
    log
    debug
}
mon.local.:53 {
mysql {
    dsn coredns:coredns@tcp(<IP_ADDRESS>:3306)/dns
    }
    errors
    log
    debug
}

Could you please look into this Problem?

Can you isolate the config so there is no forward section and CoreDNS is the only server involved. This way you might be able to narrow down the timeout to the right place.


Can't make items with 0 slots

There are items in the base game with 0 slots (such as scrap kettle) but the tool doesn't seem to let you make these.

The tool also automatically converts items with 0 slots to items with 1 normal slot


May-Kah and May-Tah's values are swapped in the "names" list.

I wanted to name my Furby "May-Kah," so I sent "130021000056" using the NRF connect app, but it ended up making it "May-Tah." So I tried "130021000058" and got it to "May-Kah."

I can't reproduce this, for me May-Kah is 0x56 and May-Tah is 0x58. Sometimes the pronounciation is not that clear. Could you try other first syllables to check if maybe you only got confused by Furby's pronounciation of Kah vs Tah?

I tried many times, just to check if I was mishearing, but it's a lot more clear when I have it greet my other Furby. I'll try and grab a video or something.

Okay, I don't know what changed, but the names match up now. Maybe I was hearing it wrong. Whoops.


Cannot build iso without substituters because lwfinger/rtlwifi_new is missing

Describe the bug
If you attempt to build the NixOS iso without any binary caches (i.e. you want to bootstrap NixOS from source), the build will fail with a 404 Not Found on https://github.com/lwfinger/rtlwifi_new/archive/a108e3de87c2ed30b71c3c4595b79ab7a2f9e348.tar.gz
This is because the repo no longer exists.
To Reproduce
Steps to reproduce the behavior:
On a system that does not already have this package installed: pkgs/os-specific/linux/rtlwifi_new/default.nix
nix-build --no-substitute "<nixpkgs/nixos>" \
  --arg configuration "<nixpkgs/nixos/modules/installer/cd-dvd/installation-cd-minimal.nix>" \
  -A config.system.build.isoImage

Eventually, you'll see
  trying https://github.com/lwfinger/rtlwifi_new/archive/a108e3de87c2ed30b71c3c4595b79ab7a2f9e348.tar.gz
    % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                   Dload  Upload   Total   Spent    Left  Speed
    0     0    0     0    0     0      0      0 --:--:--  0:00:05 --:--:--     0
  curl: (22) The requested URL returned error: 404 Not Found
  error: cannot download source from any mirror

Expected behavior
An iso image of NixOS should be built.
Additional context
This is an issue for almost no one, as the build is cached, and the builders for the cache probably have the source cached or something. But some people do like the ability to build their OS from source themselves.
EDIT: Looks like the maintainer expects people to use the driver in the kernel. That repo used to direct people to the now-missing repo.
Notify maintainers
@tvorog

It at least successfully builds if you simply remove this firmware on 20.03. Whether or not that's a good idea, I have no idea.
diff --git a/nixos/modules/hardware/all-firmware.nix b/nixos/modules/hardware/all-firmware.nix
index b07edb0f6ac..832583ade6d 100644
--- a/nixos/modules/hardware/all-firmware.nix
+++ b/nixos/modules/hardware/all-firmware.nix
@@ -48,7 +48,6 @@ in {
         rtl8192su-firmware
         rt5677-firmware
         rtl8723bs-firmware
-        rtlwifi_new-firmware
         zd1211fw
         alsa-firmware
         sof-firmware
diff --git a/pkgs/os-specific/linux/firmware/rtlwifi_new-firmware/default.nix b/pkgs/os-specific/linux/firmware/rtlwifi_new-firmware/default.nix
deleted file mode 100644
index 673ef686e48..00000000000
--- a/pkgs/os-specific/linux/firmware/rtlwifi_new-firmware/default.nix
+++ /dev/null
@@ -1,23 +0,0 @@
-{ stdenv, lib, linuxPackages }:
-
-with lib;
-
-stdenv.mkDerivation rec {
-  name = "rtlwifi_new-firmware-${linuxPackages.rtlwifi_new.version}";
-  inherit (linuxPackages.rtlwifi_new) src;
-
-  dontBuild = true;
-
-  installPhase = ''
-    mkdir -p "$out/lib/firmware"
-    cp -rf firmware/rtlwifi/ "$out/lib/firmware"
-  '';
-
-  meta = {
-    description = "Firmware for the newest Realtek rtlwifi codes";
-    inherit (src.meta) homepage;
-    license = licenses.unfreeRedistributableFirmware;
-    platforms = with platforms; linux;
-    maintainers = with maintainers; [ tvorog ];
-  };
-}
diff --git a/pkgs/os-specific/linux/rtlwifi_new/default.nix b/pkgs/os-specific/linux/rtlwifi_new/default.nix
deleted file mode 100644
index 403f0a40010..00000000000
--- a/pkgs/os-specific/linux/rtlwifi_new/default.nix
+++ /dev/null
@@ -1,40 +0,0 @@
-{ stdenv, lib, fetchFromGitHub, kernel }:
-
-with lib;
-
-let modDestDir = "$out/lib/modules/${kernel.modDirVersion}/kernel/drivers/net/wireless/realtek/rtlwifi";
-
-in stdenv.mkDerivation rec {
-  pname = "rtlwifi_new";
-  version = "2019-08-21";
-
-  src = fetchFromGitHub {
-    owner = "lwfinger";
-    repo = "rtlwifi_new";
-    rev = "a108e3de87c2ed30b71c3c4595b79ab7a2f9e348";
-    sha256 = "15kjs9i9vvmn1cdzccd5cljf3m45r4ssm65klkj2fdkf3kljj38k";
-  };
-
-  hardeningDisable = [ "pic" "format" ];
-
-  nativeBuildInputs = kernel.moduleBuildDependencies;
-
-  makeFlags = [ "KSRC=${kernel.dev}/lib/modules/${kernel.modDirVersion}/build" ];
-
-  enableParallelBuilding = true;
-
-  installPhase = ''
-    mkdir -p ${modDestDir}
-    find . -name '*.ko' -exec cp --parents {} ${modDestDir} \;
-    find ${modDestDir} -name '*.ko' -exec xz -f {} \;
-  '';
-
-  meta = {
-    description = "The newest Realtek rtlwifi codes";
-    inherit (src.meta) homepage;
-    license = stdenv.lib.licenses.gpl2;
-    platforms = with platforms; linux;
-    maintainers = with maintainers; [ tvorog ];
-    priority = -1;
-  };
-}
diff --git a/pkgs/top-level/all-packages.nix b/pkgs/top-level/all-packages.nix
index c29a75868ed..3ce17db523d 100644
--- a/pkgs/top-level/all-packages.nix
+++ b/pkgs/top-level/all-packages.nix
@@ -16693,8 +16693,6 @@ in

     rtl8821ce = callPackage ../os-specific/linux/rtl8821ce { };

-    rtlwifi_new = callPackage ../os-specific/linux/rtlwifi_new { };
-
     openafs = callPackage ../servers/openafs/1.6/module.nix { };
     openafs_1_8 = callPackage ../servers/openafs/1.8/module.nix { };

@@ -17196,8 +17194,6 @@ in

   rtl8723bs-firmware = callPackage ../os-specific/linux/firmware/rtl8723bs-firmware { };

-  rtlwifi_new-firmware = callPackage ../os-specific/linux/firmware/rtlwifi_new-firmware { };
-
   s3ql = callPackage ../tools/backup/s3ql { };

   sass = callPackage ../development/tools/sass { };

BTW, I was getting the source from our binary cache, so most people should be unaffected AFAIK.  (Notable exception: moving /nix/store elsewhere.)