Current: {{ container_name}}	 is not expanded on grafana dash bord.

What did you do?
install  kube-prometheus and prometheus-operator by using helm
What did you expect to see?
Container names are shown in pods dashbord.
What did you see instead? Under which circumstances?
A variable that is container_name is not expanded actual value.
Current: `{{ container_name`}}

Other variables are not expanded too.

Environment

Kubernetes version information:
Client Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.4", GitCommit:"793658f2d7ca7f064d2bdf606519f9fe1229c381", GitTreeState:"clean", BuildDate:"2017-08-17T08:48:23Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"8+", GitVersion:"v1.8.3-rancher1", GitCommit:"beb8311a9f114ba92558d8d771a81b7fb38422ae", GitTreeState:"clean", BuildDate:"2017-11-14T00:54:19Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:
Rancher Kubernetes Engine

Manifests:
Using helm command.
helm install coreos/kube-prometheus --name kube-prometheus --set global.rbacEnable=true --
namespace monitoring
helm install prometheus-operator --name prometheus-operator --namespace=monitoring

NAME                    REVISION        UPDATED                         STATUS          CHART                         NAMESPACE
kube-prometheus         1               Tue Mar 13 16:20:23 2018        DEPLOYED        kube-prometheus- 0.0.29       monitoring
prometheus-operator     1               Tue Mar 13 17:46:05 2018        DEPLOYED        prometheus-operator-0.0.15    monitoring

Prometheus Operator Logs:

insert Prometheus Operator logs relevant to the issue here

This is a know issue,  introduced on #1006. @vglafirov do you have time to work on this issue?

@gianrubio #1081 should fix this issue.

@gianrubi, @vglafirov
Thank you so much. And sorry for my slow reply.

Fixed by #1081


New notifier steals focus

The new brew-autoupdate.app notifier (#43) "steals the focus" when displaying a notification.
For as long as the 🍻 icon is being displayed in the macOS dock (about 3 seconds for me), the focus is removed from the prior window and instead moved to brew-autoupdate. Once the brew-autoupdate app closes (i.e. the dock icon disappears), the focus is returned to the prior window.
(Notably, the notification banner itself outlives the brew-autoupdate app instance by a few seconds, but I doubt that this is of any relevancy here and just due to how macOS handle notifications.)
You can manually return the focus while brew-autoupdate is still running by clicking or Cmd+Tab-ing to where you want to go. However, since the whole stunner just takes about 3 seconds, you usually don't realize what's going on, before everything is back to normal again.
This is quite an annoying bug though, especially if you have a high update frequency. I spend most of my time in VS Code furiously bashing my keyboard, when all of a sudden I get spammed with the system alert sound effect, while all my keystrokes vanish into /dev/null. Instant flow killer. 😄

Whild trying to provide easy reproduction steps, I also found the fix. 😂
This is the command in ~/Library/Application\ Support/com.github.domt4.homebrew-autoupdate/brew_autoupdate that's triggering the notifier:
/usr/bin/open /usr/local/Homebrew/Library/Taps/homebrew/homebrew-autoupdate/notifier/brew-autoupdate.app

https://github.com/Homebrew/homebrew-autoupdate/blob/3143047cc04a512d163ae22c667e5ef026ec57af/lib/autoupdate/notify.rb#L43-L49
You can reproduce the issue by executing that command.
Luckily, the fix is simple. man open reveals two interesting options:

-g: Do not bring the application to the foreground.
-j:  Launches the app hidden.

And indeed, applying either of them resolves the issue. I can't tell any difference between -g and -j though. I would expect -j to prevent the 🍻 icon from showing up in the dock, but it still shows. There are also no other noticeable differences in behavior.


Worked smoothly until testing the app

After successful migration and database update I tried to run the app using /Movies command but I got 404 error. I did not get any error earlier.

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

ID: 6719f08e-3bd7-dc1a-71df-f2ef9fbca9d8
Version Independent ID: 7096fdb3-612e-9e00-bd0b-8ea4886a09ce
Content: Add a model to a Razor Pages app in ASP.NET Core
Content Source: aspnetcore/tutorials/razor-pages/model.md
Product: aspnet-core
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Problem solved. Scaffolding needs to take place in Pages subfolder and not in a folder somewhere in the root of the app.

cc @seancpeters


User to be able to delete all dispatches at once

Description
Right now, a user can only select all dispatches that are in view, and then delete them all. There is a feature request to permit a user to delete all dispatches (incl ones that are not shown on the view)
Eg - Assume there are 100 dispatches. With a page size of 10, a user can only select and delete 10 dispatches at once. The ask is to let them delete all 100 at once.
The current delete implementation is shown in the below screenshot with relevant areas highlighted.

User experience

It might be acceptable for a user to make a 'Delete all' and be notified about it's acceptance ie 'Your request to delete all dispatches is being processed'. This will especially help when there are say 100s of dispatches in the DB and deleting all of them will take a few seconds.
This is a non-critical activity from a user/GUI point of view and hence a background update is not a bad option.
Once all dispatches have been deleted, no notification will be shown to the user. The next time the user refreshes the page, the data will update by itself.

Implementation details

To handle deletion of 100s of dispatches at once, it is proposed for the UI to pass an identifier 'all' directly or indirectly that informs the BE reg the request to delete all dispatches. The BE will respond back with a generic 'acceptance notification' as described above.
One edge case to handle might be if any dispatch is running during the moment of the delete all request. In that case, it is preferred to retain the on-going dispatch and only delete non-running dispatches.

Hey team! Please add your planning poker estimate with ZenHub @ArunPsiog @Prasy12

Hi @santoshkumarradha - Pls vet out these details once. Have requested Soc for designs.

just to add a bit, ideally what we want is kind of "select all" and not just delete all. For instance, once filter is enabled, if a user selects "failed" dispatches and chooses the all tick and clicks select all and then delete it etc..

just to add a bit, ideally what we want is kind of "select all" and not just delete all. For instance, once filter is enabled, if a user selects "failed" dispatches and chooses the all tick and clicks select all and then delete it etc..

@santoshkumarradha Pls note that the 'Select all' will only apply to the current searched/queried dispatch list.
This 'Select all 100 dispatches' will only show the count that is consistent with the current search & filter query. Eg if there are in total 100 dispatches and only 17 starting with 'Expe'. Then when a user searches for 'Expe', a total of 10 records will be displayed in Page 1 with a total of 17 records. The 'Select all' will only apply to the 17 and not 100.

@amalanpsiog


[FLINK-24760][docs] Update user document for batch window tvf

What is the purpose of the change
The pr adds documentation for Window deduplication.
Brief change log

Window-agg.md
Window-join.md
Window-topn.md
Window-tvf.md

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (docs)

@MartijnVisser @infoverload Thanks a lot for review.  I updated pull request to address those typos.

@godfreyhe Thanks for review, I've updated, please have a look again.

@flinkbot run azure

@flinkbot run azure


QUIC: Fixed the signalActivity is not work on QUIC branch

See #3056
The EventIO->syscall can not be initializing by ats_malloc. So it will not be added to epoll's queue。

@maskit
Updated!


Updated to Swift 3

Updated current tutorial and added additional view controller to show more detailed use of XML parser.

Nice job @OhTerryTorres


[Partner submission] [Data Validation] All Subrecipients must have at least one Subaward reported (via UEI/TIN) / All Subawards must have a Subrecipient Reported (check via UEI/TIN)

Submitted Description:
A suggestion for next quarter. Got out of a few meetings reviewing agency submissions and found that, in some cases, agencies would submit a report with a subrecipient filled out but no corresponding subaward.
In the next cycle, can we have an Excel or Render-based validation that looks between the 'Subrecipient' and 'Awards > 50000' tab to confirm consistency between reported subrecipients and reported subawards?
(Optional) Uploaded file - click to download:

Update 2022-08-18

It should be an error to include a subaward with no subrecipieint
it should be a warning to include a subrecipient with no subaward


Show pause indicator when autoplay is paused on focus

When pauseOnFocus is true and the carousel is paused, a visual indicator should be shown on the carousel. Maybe a pause icon or text or something, but I think it would be best if a slot would be used, so the user can add whatever they want.

Hi @weaseldotro,
Nice idea, ok

@weaseldotro could you please send a sketch or smth visual of
how do you want this pause indicator should look like, and
where exactly in the carousel?

Hmm, how about a 2px or 3px progress bar at the top or at the bottom of the image that will start at 100% and then decrease according to the duration? https://css-tricks.com/timer-bars-in-css-with-custom-properties/
When the mouse is hovered on the image, the progress bar should pause.
On mobile, when the user taps the image the progress bar shoud pause, and the on the second tap it should resume.
I think this is the best solution.

Released in<EMAIL_ADDRESS>

Looks great, good job!
I've noticed a little quirk: on my iPhone with Safari, tapping on a carousel with autoplay with pause on focus will restart the current progress from zero. However, there is noticeable delay between the time you tap on the image and the restart of the progress. Not a lot, I'm guessing something like .5 seconds, but still, pretty noticeable.
Also, I think my initial suggestion would work better on mobile than the current implementation: when the user taps the image the progress bar should pause, and then on the second tap it should resume.

Yes, it is initial solution for focusing behaviour, which comes from one of the previous releases. Seems it works differently in Safari. I'll rethink it with two-taps-approach as well.
Thanks.


GEOMESA-2698 SimpleFeatureType config to prioritize time-based indices

Signed-off-by: Emilio Lahr-Vivaz<EMAIL_ADDRESS>

Merged as c11aa3c279e1c7106dbaf8864c5b1dd17a658951


[Theme]: fix color background

fix color background selected items in QComboBox
remove empty spase around mesh interactor toolbar

What we now have

What I propose


Added mapping of experimental Otel telemetry.distro.name and version attributes

Closes #200 .

Once we will have "otel native" storage, those fields would be stored as top-level elements.
We will need to modify the UI to make use of those (for example to show a proper Elastic + Otel label on services where it's used), so if we can also store them as top-level elements that would provide a future-proof mapping in the UI.
This is the strategy that was used to add code.stacktrace in https://github.com/elastic/apm-data/issues/177


Add storybook and Modal component from the design system

Related to #372
I decided to add storybook to make developing components in isolation easier. Please let me know if you can't get npm run storybook working locally. I had to do a bit of hackery to get custom CSS/JS running within storybook to mimic the display on the frontend properly.
Edit: Decided to reduce the scope of this PR to adding storybook and implementing a generic modal component with new design system styling. More work for 372 incoming.

Not sure why the PR build cancelled 🤔


[UForm] How to add validation to custom input

Description
I've created a custom input component (using normal HTML input) and put it inside a UForm -> FormGroup, but it doesn't show any errors when validate. How can i achive this?

@hamonCordova https://github.com/nuxt/ui/issues/1573

Thanks!
On Fri, Jul 26, 2024, 14:32 Spencer Small @.***> wrote:

@hamonCordova https://github.com/hamonCordova #1573
https://github.com/nuxt/ui/issues/1573
—
Reply to this email directly, view it on GitHub
https://github.com/nuxt/ui/issues/1983#issuecomment-2253190472, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AIJZ6KZIVEXXL3KKPGPXUXTZOKB4RAVCNFSM6AAAAABLNGAN7OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJTGE4TANBXGI
.
You are receiving this because you were mentioned.Message ID:
@.***>


Temporal.io integration

Description
Temporal has a python sdk with at least some level of opentelemetry support.
It would be great to be able to instrument it in logfire.
More info here: https://docs.temporal.io/develop/python/observability#tracing
and opentelemetry sample here: https://github.com/temporalio/samples-python/tree/main/open_telemetry

Actually after digging into this, it works pretty well with logfire out of the box:
from temporalio.contrib.opentelemetry import TracingInterceptor
from temporalio.client import Client

temporal_client = await Client.connect(
            "localhost:7233", # temporal host
            interceptors=[TracingInterceptor()],
        )

Feel free to close this feature request if you'd like.

It seems the opentelemetry scope name they use is the module name, so instead of having opentelemetry.instrumentation.temporalio, we have temporalio.contrib.opentelemetry. This displays this in our UI:

I was able to run Temporal IO locally with:
import asyncio
from dataclasses import dataclass
from datetime import timedelta

from temporalio import activity, workflow
from temporalio.client import Client
from temporalio.contrib.opentelemetry import TracingInterceptor
from temporalio.worker import Worker

import logfire

logfire.configure()

@dataclass
class YourParams:
    greeting: str
    name: str

@activity.defn(name='your_activity')
async def your_activity(input: YourParams) -> str:
    return f'{input.greeting}, {input.name}!'

@workflow.defn(name='YourWorkflow', sandboxed=False)
class YourWorkflow:
    @workflow.run
    async def run(self, name: str) -> str:
        return await workflow.execute_activity(
            your_activity,
            YourParams('Hello', name),
            start_to_close_timeout=timedelta(seconds=10),
        )

async def main():
    # Start a separate worker process
    client = await Client.connect('localhost:7233', interceptors=[TracingInterceptor()])

    async with asyncio.TaskGroup() as tg:
        worker = Worker(
            client,
            task_queue='my-task-queue',
            workflows=[YourWorkflow],
            activities=[your_activity],
        )
        tg.create_task(worker.run())
        tg.create_task(
            client.execute_workflow(
                YourWorkflow.run,
                'your name',
                id='your-workflow-id',
                task_queue='your-task-queue',
            )
        )

if __name__ == '__main__':
    asyncio.run(main())

And I had to install the server with brew install temporalio, and run via temporal server start-dev.

This is a matter of documenting, and maybe submitting a PR on their side to replace __name__ by 'temporalio, or opentelemetry.temporalio, or... To be fair, there's nothing wrong with what they do, is just that others follow a non-specified standard (as far as I know it's not specified).


include hex characters into unsigned definition

To close #247
This is one possible way you could correct the problem, perhaps discuss here how it could be improved.
Also, someone please double check what I wrote is correct in the first place. 😁

bors r+


Compute and set Offsets on the the chip registers (User Bank 4), with Raw reading, Notch Filter

Here are the main updates:

Raw reading getRawAGT(): necessary to compute offsets
Data reading getAGT(): use the rawReading, method.
Added some definitions
Added get resolutions
Added compute Offsets: compute the offset to be put in the user bank register, this provide a simple calibration method
Added set offset methods: either setting all Offsets are once, or setting for each axis, gyro and accelerometer
Added an example on how to use the Offset methods.
Notch filter settings, user should input the notch frequencies for each axis, and Bandwidth (untested) added enum for the bandwidth. (testing would require to stream data towards an analyzer and having a code to change the notch filter live)

LGTM


Browse MAS

An extension to browse the Mac App Store. This could probably be achieved using the MAS cli

This sound quite interesting

There is now the Mac App Store Search extension available, so this issue might be able to be closed.


Invalid column decoder encountered when generating large-scale SRAM

Thank you so much for taking a look at my question.
ERROR: file column_decoder.py: line 118: Invalid column decoder?
Traceback (most recent call last):
File "/home/ICer/jl32n22/design/tools/OpenRAM/sram_compiler.py", line 73, in
s = sram()
File "/home/ICer/jl32n22/design/tools/OpenRAM/compiler/sram.py", line 56, in init
self.s.create_netlist()
File "/home/ICer/jl32n22/design/tools/OpenRAM/compiler/modules/sram_1bank.py", line 199, in create_netlist
self.add_modules()
File "/home/ICer/jl32n22/design/tools/OpenRAM/compiler/modules/sram_1bank.py", line 465, in add_modules
self.bank = factory.create("bank", sram_config=self.sram_config, module_name="bank")
File "/home/ICer/jl32n22/design/tools/OpenRAM/compiler/sram_factory.py", line 153, in create
obj = mod(name=module_name, **kwargs)
File "/home/ICer/jl32n22/design/tools/OpenRAM/compiler/modules/bank.py", line 49, in init
self.create_netlist()
File "/home/ICer/jl32n22/design/tools/OpenRAM/compiler/modules/bank.py", line 61, in create_netlist
self.create_instances()
File "/home/ICer/jl32n22/design/tools/OpenRAM/compiler/modules/bank.py", line 165, in create_instances
self.create_column_decoder()
File "/home/ICer/jl32n22/design/tools/OpenRAM/compiler/modules/bank.py", line 535, in create_column_decoder
self.column_decoder = factory.create(module_type="column_decoder",
File "/home/ICer/jl32n22/design/tools/OpenRAM/compiler/sram_factory.py", line 153, in create
obj = mod(name=module_name, **kwargs)
File "/home/ICer/jl32n22/design/tools/OpenRAM/compiler/modules/column_decoder.py", line 32, in init
self.create_netlist()
File "/home/ICer/jl32n22/design/tools/OpenRAM/compiler/modules/column_decoder.py", line 39, in create_netlist
self.add_modules()
File "/home/ICer/jl32n22/design/tools/OpenRAM/compiler/modules/column_decoder.py", line 118, in add_modules
debug.error("Invalid column decoder?", -1)
File "/home/ICer/jl32n22/design/tools/OpenRAM/compiler/debug.py", line 47, in error
assert return_value == 0
AssertionError
make[1]: *** [Makefile:85: scn4m_subm_1w1r_4_small.ok] Error 1
make: *** [Makefile:95: scn4m_subm_1w1r_4_small] Error 2
Other relevant logs are as follows:
Technology: scn4m_subm
Total size: 307200 bits
Word size: 4
Words: 76800
Banks: 1
RW ports: 0
R-only ports: 1
W-only ports: 1
[openram.sram_config/recompute_sizes]: Recomputing with words per row: 4800
[openram.sram_config/recompute_sizes]: Rows: 16 Cols: 19200
[openram.sram_config/recompute_sizes]: Row addr size: 4 Col addr size: 12 Bank addr size: 16
[openram.sram_config/compute_sizes]: Set SRAM Words Per Row=4800
[openram.modules.bitcell_base_array/init]: Creating scn4m_subm_1w1r_4_small_global_bitcell_array 16 x 19200
[openram.modules.bitcell_base_array/init]: Creating scn4m_subm_1w1r_4_small_local_bitcell_array 16 x 16
[openram.modules.bitcell_base_array/init]: Creating scn4m_subm_1w1r_4_small_capped_replica_bitcell_array 16 x 16
[openram.modules.capped_replica_bitcell_array/init]: Creating scn4m_subm_1w1r_4_small_capped_replica_bitcell_array 16 x 16 rbls: [1, 1] left_rbl: [0] right_rbl: []
[openram.modules.bitcell_base_array/init]: Creating scn4m_subm_1w1r_4_small_replica_bitcell_array 16 x 16
[openram.modules.replica_bitcell_array/init]: Creating scn4m_subm_1w1r_4_small_replica_bitcell_array 16 x 16 rbls: [1, 1] left_rbl: [0] right_rbl: []
[openram.modules.bitcell_base_array/init]: Creating scn4m_subm_1w1r_4_small_bitcell_array 16 x 16
[openram.modules.bitcell_array/init]: Creating scn4m_subm_1w1r_4_small_bitcell_array 16 x 16
[openram.modules.bitcell_base_array/init]: Creating scn4m_subm_1w1r_4_small_replica_column 18 x 1
[openram.modules.bitcell_base_array/init]: Creating scn4m_subm_1w1r_4_small_dummy_array 1 x 16
[openram.modules.bitcell_base_array/init]: Creating scn4m_subm_1w1r_4_small_dummy_array_0 1 x 17
[openram.modules.bitcell_base_array/init]: Creating scn4m_subm_1w1r_4_small_dummy_array_1 1 x 17
[openram.modules.bitcell_base_array/init]: Creating scn4m_subm_1w1r_4_small_dummy_array_2 20 x 1
[openram.modules.bitcell_base_array/init]: Creating scn4m_subm_1w1r_4_small_dummy_array_3 20 x 1
[openram.modules.wordline_buffer_array/init]: Creating scn4m_subm_1w1r_4_small_wordline_buffer_array
[openram.modules.bitcell_base_array/init]: Creating scn4m_subm_1w1r_4_small_local_bitcell_array_0 16 x 16
[openram.modules.bitcell_base_array/init]: Creating scn4m_subm_1w1r_4_small_capped_replica_bitcell_array_0 16 x 16
[openram.modules.capped_replica_bitcell_array/init]: Creating scn4m_subm_1w1r_4_small_capped_replica_bitcell_array_0 16 x 16 rbls: [1, 1] left_rbl: [] right_rbl: []
[openram.modules.bitcell_base_array/init]: Creating scn4m_subm_1w1r_4_small_replica_bitcell_array_0 16 x 16
[openram.modules.replica_bitcell_array/init]: Creating scn4m_subm_1w1r_4_small_replica_bitcell_array_0 16 x 16 rbls: [1, 1] left_rbl: [] right_rbl: []
[openram.modules.bitcell_base_array/init]: Creating scn4m_subm_1w1r_4_small_bitcell_array_0 16 x 16
[openram.modules.bitcell_array/init]: Creating scn4m_subm_1w1r_4_small_bitcell_array_0 16 x 16
[openram.modules.bitcell_base_array/init]: Creating scn4m_subm_1w1r_4_small_dummy_array_4 1 x 16
[openram.modules.bitcell_base_array/init]: Creating scn4m_subm_1w1r_4_small_dummy_array_5 1 x 16
[openram.modules.bitcell_base_array/init]: Creating scn4m_subm_1w1r_4_small_dummy_array_6 1 x 16
[openram.modules.bitcell_base_array/init]: Creating scn4m_subm_1w1r_4_small_dummy_array_7 20 x 1
[openram.modules.bitcell_base_array/init]: Creating scn4m_subm_1w1r_4_small_local_bitcell_array_1 16 x 16
[openram.modules.bitcell_base_array/init]: Creating scn4m_subm_1w1r_4_small_capped_replica_bitcell_array_1 16 x 16
[openram.modules.capped_replica_bitcell_array/init]: Creating scn4m_subm_1w1r_4_small_capped_replica_bitcell_array_1 16 x 16 rbls: [1, 1] left_rbl: [] right_rbl: [1]
[openram.modules.bitcell_base_array/init]: Creating scn4m_subm_1w1r_4_small_replica_bitcell_array_1 16 x 16
[openram.modules.replica_bitcell_array/init]: Creating scn4m_subm_1w1r_4_small_replica_bitcell_array_1 16 x 16 rbls: [1, 1] left_rbl: [] right_rbl: [1]
[openram.modules.bitcell_base_array/init]: Creating scn4m_subm_1w1r_4_small_replica_column_0 18 x 1
[openram.modules.and2_dec/init]: Creating and2_dec and2_dec
[openram.modules.and3_dec/init]: Creating and3_dec and3_dec
[openram.modules.and4_dec/init]: Creating and4_dec and4_dec
[openram.modules.wordline_driver_array/init]: Creating scn4m_subm_1w1r_4_small_wordline_driver_array
[openram.modules.wordline_driver/init]: Creating wordline_driver wordline_driver
[openram.modules.pbuf/init]: creating pbuf with size of 1200
[openram.modules.precharge_array/init]: Creating scn4m_subm_1w1r_4_small_precharge_array
[openram.modules.column_mux_array/init]: Creating scn4m_subm_1w1r_4_small_column_mux_array
[openram.modules.write_driver_array/init]: Creating scn4m_subm_1w1r_4_small_write_driver_array
[openram.modules.precharge_array/init]: Creating scn4m_subm_1w1r_4_small_precharge_array_0
[openram.modules.sense_amp_array/init]: Creating scn4m_subm_1w1r_4_small_sense_amp_array
[openram.modules.column_mux_array/init]: Creating scn4m_subm_1w1r_4_small_column_mux_array_0
It seems that there is a problem with the number of columns of my SRAM, how should I configure the parameters to ensure that I get an SRAM with a suitable number of rows and columns? In addition, I would like to ask, what is the maximum number of words supported by the current version of OpenRAM? I often encounter this problem when generating large-scale SRAM.

This is a very big memory with a very small word size. It probably is running intoa  corner case.   Do you have your config file and which version of openram you are using (commit id)?
We really focus on generating smaller blocks that can be used in larger memory designs. We have a virtual banking option which will generate Verilog that can be synthesized to use these multiple banks.
We don't really have a "maximum" per say. There is a limit on the hierarchical decoder since we have at most a nand4 in the pre-decoders and the final decoder. However, a single bank will run into limits long before that due to long bitlines and bitline leakage/noise margins. It is difficult to predict in each technology, so we leave it to the user to do functional simulation. Ultimately, we'd like to automate it better, but there's a reason memory design is hard. :)

word_size = 4
num_words = 307200  # 640*480 words(addresses)
write_size = 4
local_array_size = 16  # number of columns per array
words_per_row = 19200  # number of addresses per line
num_spare_rows = 0
num_spare_cols = 0
num_rw_ports = 0
num_r_ports = 1
num_w_ports = 1
tech_name = "scn4m_subm"
nominal_corner_only = True
route_supplies = "minimal"
check_lvsdrc = True
perimeter_pins = False
output_name = "sram_{0}rw{1}r{2}w_{3}{4}{5}".format(num_rw_ports,
num_r_ports,
num_w_ports,
word_size,
num_words,
tech_name)
output_path = "macro/{}".format(output_name)
Here is my config file, there seems to be something wrong with the setting of local_array_size = 16 and words_per_row?
Also, while inspecting the device, I found out that the output of the write driver is made of two nmos that turn on gnd and bl/br at en din' and en din respectively, which doesn't seem to work if gnd remains grounded bl/br output high level? Will this cause failure to build SRAM?

You are manually specifying a lot of parameters that aren't usually. I suggest not appreciating the words per row if you specify the 16 local arrays. I have never done that so it's likely the issue.


Campaign admin UI with subset selection and test results.

Also adds a button to verify API endpoint.
NB:

Some portals blow up when using multiple subsets (ie. an organisation and a tag subset) -- but that's a CKAN setup thing.
New campaign setup now assumes the user will provide the base api url e.g. "http://data.gov.uk/api" or "http://data.sa.gov.au/data/api"

Addresses #1414, #1419

Coverage increased (+0.3%) to 81.318% when pulling 4c9bdad5a849de9b0167fe95293af75ade78d0b8 on digitalWestie:campaigntestrun into 658ae69892b85940e0910e60ff23abbf6c7476d8 on theodi:staging.

Don't publish test / prefetched campaign certificates.


SFI effort: EF repos: Images: Triage All

Triaging + plan for completion must be complete by end of September, actual fixing can occur after that.
CS effort for repos:
dotnet_EntityFramework_Docs
dotnet_EntityFramework_ApiDocs
Image scans:
10 images in EntityFramework.Docs
0 images in EntityFramework_ApiDocs
Tasks:

Consider first running Genevieve's Clean Repo Tool to identify and get rid of all images that are orphaned.  That alone may help clear a number of these out.
Review and triage all images first.
For images that need to be fixed, set a plan for fixing them and schedule.

For details on how to triage, fix and note completion, see:
SFI info in Teams
Related to parent tracking issue for this repo: https://github.com/dotnet/AspNetCore.Docs/issues/33229
(As soon as we have a label for this to auto connect the appropriate ADO parent set it.)

Associated WorkItem - 295461

Closing as completed successfully.  Updated AzDO related issue.  All images issues triaged.


Improv: Similar to AWS AppSync, server should only return fields from user query (filter out extra fields)

Dependency: Replace dot-object with wild-wild-path in client/utils. Wild-wild-path can then be used to filter out query fields based on paths.

Was just about to open an issue. Would this fix the situation where I have a custom resolver:
type HealthcheckStatus {
  status: String!
  code: Number
}

extend type Query {
  healthcheck: HealthcheckStatus
}

Now, when querying the following, the response will include all fields, not filtering just the requested path:
query {
  healthcheck {
    status
  }

Yes, this is related. Yoga GraphQL returns all the data, regardless of the actual Query. Note that this should only be an issue with the local dev server.

Released in 1.0.0-rc.4.


fluo-env.sh now supports FLUO_JAVA_OPTS set in environment

Appended FLUO_JAVA_OPTS to JAVA_OPTS in fluo-env.sh  . This allows to set FLUO_JAVA_OPTS to set from command line . #954

@srikailash thanks for the contribution.  It seems the email address you used in the commit is not linked to your github account.  If you want you can got to your github account settings and add that email address.  Then when someone looks at the commits your github account will show up.
If you would like to be added to Fluo's people page you can give me the info or submit a PR to the website repo modifying people.md.
Are you ok with @ApacheFluo tweeting about your first contribution?   If so, do you have a twitter user we could mention?

Thanks for the community for helping me setup fluo . Looking forward for more pull requests .
Regarding twitter usage : I don't use it :) . I will make a pull request to webiste repo . Thanks :)


Update logging

[x] Update logging for better visualization.
[x] Add the validator and miner installation guide
[x] Update README

add QuickStart link
add  usable commands

Pretty good work. 👍


php-7.4.2/pecl Notice

mac:~ qidizi$ /usr/local/Cellar/php/7.4.2/bin/pecl search kafka
Retrieving data...0%

Notice: Trying to access array offset on value of type null in Remote.php on line 550

Notice: Trying to access array offset on value of type null in /usr/local/Cellar/php/7.4.2/share/php/pear/PEAR/Command/Remote.php on line 550

Call Stack:
    0.0005     413128   1. {main}() /usr/local/Cellar/php/7.4.2/share/php/pear/peclcmd.php:0
    0.0015     480584   2. require_once('/usr/local/Cellar/php/7.4.2/share/php/pear/pearcmd.php') /usr/local/Cellar/php/7.4.2/share/php/pear/peclcmd.php:32
    0.0257    1950520   3. PEAR_Command_Remote->run() /usr/local/Cellar/php/7.4.2/share/php/pear/pearcmd.php:317
    0.0257    1950520   4. PEAR_Command_Remote->doSearch() /usr/local/Cellar/php/7.4.2/share/php/pear/PEAR/Command/Common.php:270

Notice: Trying to access array offset on value of type null in Remote.php on line 551

Notice: Trying to access array offset on value of type null in /usr/local/Cellar/php/7.4.2/share/php/pear/PEAR/Command/Remote.php on line 551

Call Stack:
    0.0005     413128   1. {main}() /usr/local/Cellar/php/7.4.2/share/php/pear/peclcmd.php:0
    0.0015     480584   2. require_once('/usr/local/Cellar/php/7.4.2/share/php/pear/pearcmd.php') /usr/local/Cellar/php/7.4.2/share/php/pear/peclcmd.php:32
    0.0257    1950520   3. PEAR_Command_Remote->run() /usr/local/Cellar/php/7.4.2/share/php/pear/pearcmd.php:317
    0.0257    1950520   4. PEAR_Command_Remote->doSearch() /usr/local/Cellar/php/7.4.2/share/php/pear/PEAR/Command/Common.php:270

Matched packages, channel pecl.php.net:
=======================================
Package Stable/(Latest) Local
rdkafka 4.0.3 (stable)        Kafka client based on librdkafka
mac:~ qidizi$

but php 7.3 is fine
mac:~ qidizi$<EMAIL_ADDRESS>search kafka
Retrieving data...0%
Matched packages, channel pecl.php.net:
=======================================
Package Stable/(Latest) Local
rdkafka 4.0.3 (stable)        Kafka client based on librdkafka
mac:~ qidizi$

same error for PHP 7.4.3, when using the pecl to search or install anything
pecl search redis

Retrieving data...0%

Notice: Trying to access array offset on value of type null in Remote.php on line 550

Notice: Trying to access array offset on value of type null in /usr/local/Cellar/php/7.4.3/share/php/pear/PEAR/Command/Remote.php on line 550

Notice: Trying to access array offset on value of type null in Remote.php on line 551

Notice: Trying to access array offset on value of type null in /usr/local/Cellar/php/7.4.3/share/php/pear/PEAR/Command/Remote.php on line 551
Matched packages, channel pecl.php.net:
=======================================
Package Stable/(Latest) Local
redis   5.2.0 (stable)        PHP extension for interfacing with Redis

pecl version

PEAR Version: 1.10.10
PHP Version: 7.4.3
Zend Engine Version: 3.4.0
Running on: Darwin xyzMacBook-Pro.local 17.7.0 Darwin Kernel Version 17.7.0: Thu Jan 23 07:05:23 PST 2020; root:xnu-4570.71.69~1/RELEASE_X86_64 x86_64

@MikeMcQuaid may you reopen this issue? I install PHP 7.4 through the homebrew-bottles/bottles/php-7.4.3.high_sierra.bottle.tar.gz package, then got these notices.

@lanlin No because it's in the wrong repository and didn't fill out the issue template. Feel free to open a new issue in Homebrew/homebrew-core (after filling out the whole issue template)


Fix "Error: stream.push() after EOF"

Consider some data, for example, the Ubuntu 15.10 Desktop AMD64 image
from http://releases.ubuntu.com/15.10/ubuntu-15.10-desktop-amd64.iso
The size of this file is<PHONE_NUMBER> bytes. If we create a readable
stream out of this file, my system (rMBP running OS X) will read in
blocks of 65536.
Now let's try dividing the Ubuntu image size by our hypothetical buffer
length:
1178386432 / 65536 = 17980.75

Notice the result is a float number, and thus the image file can't be
read in an integral amount of blocks.
This causes slice-stream to receive one more buffer in
._transform(). Even if you signaled the end of the stream (EOF) by
pushing null, slice-stream will send this last buffer to the slice
function, so the user will try to push it, and therefore get:
Error: stream.push() after EOF
As a workaround, I can set the readable stream's high water mark to a
number that cleanly divides the image size, like 1024, and everything
will work fine, however to have more protection from this module, its a
good idea to check if the stream is readable (e.g: EOF has not been
signaled yet), before attempting to process a new buffer.
I managed to create a test case with a small image (2MB) and setting a
high water mark of 10 (since 2048 is not cleanly divisible by 10).
This issue as originally reported at https://github.com/resin-io/etcher/issues/307
Signed-off-by: Juan Cruz Viotti<EMAIL_ADDRESS>

The tests are failing due to<EMAIL_ADDRESS>not being able to get installed on NodeJS v0.8. That version is no longed supported, so I guess its safe to remove from Travis CI.

I'll be maintaining a fork of this project at https://github.com/jviotti/slice-stream2


DisableTransactions in MongoDB, debugging Cosmos DB for MongoDB

Describe the bug
Not sure if the DisableTransactions option is being taken into consideration when passed, in the code it looks like hardcode to false, and never used:
https://github.com/remult/remult/blob/fc2f5c6d67fb43632fdc8ae1b7242fff32a7fc55/projects/core/remult-mongo.ts#L37
My code:
MongoDataProvider(client.db((process.env as any).MONGODB_DATABASE_NAME), client, { disableTransactions: true });

I wanted to disable transactions because I'm getting the following error:
Error=2, Details='Response status code does not indicate success: BadRequest (400); Substatus: 1101; ActivityId: 4a5f881b-e63d-4756-981e-23b60d6428e4; Reason: (Response status code does not indicate success: BadRequest (400); Substatus: 1101; ActivityId: 4a5f881b-e63d-4756-981e-23b60d6428e4; Reason: (Response status code does not indicate success: BadRequest (400); Substatus: 1101; ActivityId: 4a5f881b-e63d-4756-981e-23b60d6428e4; Reason: (Message: {"Errors":["Transaction is not active"]}

Thanks.
I've fixed it in version 0.22.1 (https://github.com/remult/remult/releases/tag/v0.22.1)
Can you check it and let me know that it's ok?

Yes! { disableTransactions: true } works now!
I still got the following error from Cosmos DB if I set disableTransaction to false.
Reason: (Message: {"Errors":["Transaction is not active"]}

According to Cosmos DB for MongoDB documentation:
Multi-document transactions are supported within an unsharded collection in API version 4.0. Multi-document transactions are not supported across collections or in sharded collections in 4.0. The timeout for transactions is a fixed 5 seconds.
https://learn.microsoft.com/en-us/azure/cosmos-db/mongodb/use-multi-document-transactions
I'm using Cosmos DB 4.2 API, and unsharded collection. However, I simple reading operation from a static backendMethod cause Cosmos DB to trigger the error.
My code:
const user = await remult.repo(User).findFirst({ email: email });

I wonder why remult "transaction" is considered multi-document while I'm only doing a simple read to one collection?
Or it is Cosmos DB that is not accepting transactions at all even when the documentation says so.
Any thoughts?
Thanks

Are you still getting the error?
On Tue, Jul 25, 2023 at 14:26 Elier Delgado @.***>
wrote:

Closed #215 https://github.com/remult/remult/issues/215 as completed.
—
Reply to this email directly, view it on GitHub
https://github.com/remult/remult/issues/215#event-9910488206, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AD65PUZ5MU7ODMKA5NXZN5LXR6UM3ANCNFSM6AAAAAA2WMHCJQ
.
You are receiving this because you commented.Message ID:
@.***>

Perfect - I thought you had another error - I'm happy that you don't.
Cheers
On Tue, Jul 25, 2023 at 3:16 PM Elier Delgado @.***>
wrote:

No, if I set disableTransaction to true, all works fine.
—
Reply to this email directly, view it on GitHub
https://github.com/remult/remult/issues/215#issuecomment-1649727848, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AD65PU3Z7NIPW3BP7JT2B2LXR62KZANCNFSM6AAAAAA2WMHCJQ
.
You are receiving this because you commented.Message ID:
@.***>


Audit tensorflow-related documentation and samples

Following the work discussed on https://groups.google.com/g/iree-discuss/c/cWZUMXlXscE/m/qTlRXY8NFAAJ, let's check that our documentation and samples are still up to date

[ ] https://google.github.io/iree/building-from-source/python-bindings-and-importers/#building-tensorflow-components-with-bazel
[ ] https://github.com/google/iree/tree/main/colab
[ ] https://google.github.io/iree/ml-frameworks/tensorflow/

ideally we should also expand on documentation and samples for other frontends

I've got a lot more work to do. I think we should get someone else to do this. Probably better for someone not-me to trial it anyway: I'm too familiar with it all to spot rough areas.

TF docs seem to still be accurate, and the recently added TFLite docs help too: https://google.github.io/iree/getting-started/tflite/
As JAX and other frontends stabilize we should write new docs for them.


refactor(*) patches to make patches applying without warnings

Summary
Fixes warnings about offsets and fuzzes.

I think travis is failing regardless of the PR.

Does this fix:
https://github.com/Kong/openresty-patches/issues/53
and
https://github.com/Kong/openresty-patches/issues/45
I imagine? Looks like a change in offsets and such.


Support custom domains in API Management

API Management typically exposes APIs consumed by external applications, and need to provide a professional integration experience.
We should support custom domains, from the dedicated Bicep template.

See (this page)[https://docs.microsoft.com/en-us/azure/api-management/configure-custom-domain?tabs=managed] ; a strong limitation still exists (custom domain cannot be mapped on creation, with managed certificates).


Consumer offset for stream with single message not stored

Describe the bug
When I have a stream with only 1 message and create a single active consumer for that stream, calling consumerContext.Consumer.StoreOffset(), when consuming the message, does not store the offset. When I restart the single active consumer, the consumer will start from the beginning as the offset is not stored, thus the first and only message is replayed.
If I have 2 or more messages in the stream, then the offset is stored (for the 2nd message) and the single active consumer will start where it left off (offset + 1). So this works as expected.
I believe this issue is caused by the fact that the first message in the stream has an offset of 0 and ints are initialized with 0. There is some logic in this client to only store the offset when it has increased.
In updateLastStoredOffset() there is this check if consumer.lastStoredOffset < consumer.currentOffset. Here I think lastStoredOffset is by default 0 and currentOffset is 0, so updateLastStoredOffset() returns false and thus internalStoreOffset() does not store the offset on the RabbitMQ server.
Reproduction steps

Create stream
Publish one message to stream
Setup single active consumer, consume the message and store the offset
Restart the consumer, the consumer will start from offset 0 because the offset is not stored
...

Expected behavior
Consumer offset should be able to be stored even after processing only the first message in the stream
Additional context
No response

@Darthmineboy  Thank you for reporting the issue. Will have a look as soon as possible.

@Darthmineboy Can you try #307 ? thank you

@Darthmineboy   FYI https://github.com/rabbitmq/rabbitmq-stream-go-client/releases/tag/v1.4.4

closed via #307


Status bar wrong color

The color of status bar in Black and dark mode is wrong (it shuld be darker like in previous version)

This is only the case in the Settings, right?
I already fixed this in my local build.

@kollerlukas Yes


Delete Group Command

!deletegroup in a group owned by the user will delete the group and alert all of its members.

Moderators can now also delete groups.
Some special groups are protected: 'Meta', 'Memes', 'Recreation', 'Gaming', 'Politics', 'Testing'


Make it compatible with Vue please

Just realized it would not work with vue , but i need it for my next project

There's more than one toast plugin for Vue already.


Prevent unhandled RangeError in CommonDateField

Fixes https://github.com/mikel/mail/issues/1269
The normalize_datetime method causes a RangeError crash when DateTime.parse fails to parse a date too big. This fixes this issue naively by using the original string when a RangeError is raised from the DateTime call.

I run into this as well! @zelivans what do you think of adding also a test for this? This is the one I had added myself before realising there was already a PR for this:
diff --git a/spec/mail/fields/date_field_spec.rb b/spec/mail/fields/date_field_spec.rb
index bdb9e916..720f4c7c 100644
--- a/spec/mail/fields/date_field_spec.rb
+++ b/spec/mail/fields/date_field_spec.rb
@@ -66,5 +66,10 @@ describe Mail::DateField do
       field = Mail::DateField.new("12 Aug 2009 30:00:02 GMT")
       expect(field.date_time).to be_nil
     end
+
+    it "should handle out of integer range errors in date" do
+      field = Mail::DateField.new("12 Aug 2009 12:00:8184237681594 GMT")
+      expect(field.date_time).to be_nil
+    end
   end
 end


Fixes #1575 Rename folder failed to "reparent" folder

Fixes #1575 Rename folder failed to "reparent" folder
Fixes most of the renaming issues.

This is not ready to merge yet - I need to get tests running so I can check them, but right now I'm fighting against implicit assembly references failing to resolve.

I can't get the shared project tests running at all on my local box, I think they're going to need a restructure to avoid the mixed assembly reference issues I'm hitting constantly. Going to set up a test run to validate this instead, and file a new issue to refactor tests.

👍


Type narrowing fails to understand that a variable is always assigned

🕗 Version & Regression Information
on next
⏯ Playground Link
https://tsplay.dev/WGb4Vm
💻 Code
function f(x: { a: '1' } | { a: '2' }): string {
	let foo: string;

	if (x.a === '1') {
		foo = 'one';
	} else if (x.a === '2') {
		foo = 'two';
	}

	return foo;
}

🙁 Actual behavior
return foo errors with Variable 'foo' is used before being assigned.(2454).
🙂 Expected behavior
Given that the type of x is known, and the if/else if covers both branches, if i put else { } i'd expect TS to complain somehow that the else block is unreachable - and since foo is assigned in every possible code branch as far as TS is aware, i would expect no error.
I recognize that the runtime value might not conform to the type, but doesn't TS assume it does, meaning that it shouldn't error here?
Additional information about the issue
No response

Interesting, ok - so in order to silence the error without an override comment, i'd have to add an else that throws or assigns?

Correct

ok, thanks for confirming


Elastic output module

This PR adds a storage module for Elastic along with a default overview dashboard. This module includes the following features:

Attempts to conform to ECS naming standards for fields
Configurable ability to save HTTP response content as ZIP archives
Adds payload processing output (i.e. Yara matches)

Please note, the module dynamically creates field names based off of the HTTP response content and may require adjustments to the index's max field limit, depending on your desired setup. Documents are indexed using the bulk insert API. The number of items submitted per bulk request will coincide with the overall batch processing size, set in the main configuration. Any documents that cause a failure to index will thus fail all items in that bulk request.

:thumbsup: Looks good to me.


Error when I run step3 on my own dataset

Hello, thank you for sharing your code! I got this error when I run 'step3' on my own dataset. I notice the detection results in line_detection.py is all False for some image, and I think it may be the reason. But how can I solve this problem?

Hi, this is probably due because no junction was detected indeed. I have just pushed a simple fix that should solve your issue. Let me know if the problem persists.


Support GLOB patterns

I am not sure if you do support GLOB patterns - but i am having trouble using this binary to grab a specific release asset using GLOB patterns - like i can  using gh cli. I have a project where i would like to embed this binary for easy, and lightweight, grabbing of a specific release asset. The issue is that the release asset to grab is user-configured. As in the user supplies a string to be able to grab the asset - each asset however has a name that changes based on the version  and target.
In the gh cli - this is functional
gh -R lorow/OpenIris release download -p "workspace-v*-esp32Cam*.zip"

This would grab the binary for the specific target board.
How can i achieve the same thing with your project :)

Note: dra untag does not work - i've tried. It just gives me the asset name in full, it doesn't allow any type of pattern usage.

understood, thank you. In order to use your tools I'll have to fix the version discrepancy, and remove the revision number from the name. That way I can grab a release by predictable name and simple untag the version.
Appreciate the quick response, great work. Very nice project. Saved me a lot of time 😅

i am not sure i should create another issue for this (let me know if that is your preferred approach)- but i have one more question related to this topic.
I would like to automate the untagging process so that our users can select the release asset from a dropdown menu in the GUI and in the backend it calls the download command by passing a string to the command. I have the binary embedding and the passing of the command handled.
Is there a way to avoid having to select an asset using the untagging command, or do i just have to keep track of the most recent version (somehow) and then call the download command directly by formatting the string with the version?


Tidying of Block Status Updates

Description
This change only reports changes to block status (tidiness)
Fixes # (2121)
Type of change
Choose which options apply, and delete the ones which do not apply.

Breaking change (fix or feature that would cause existing functionality to not work as expected)

this was implemented in a different way in #2401 so closing


No data is obtained from VW

Hello Mr Steinbach,
My wife drives an ID 3 (taken over May 22) and I drive a Passat GTE (taken over Dec. 20). Unfortunately, I now have the problem that the data update, after the Docker container start, no longer works after only a few days. In my home automation system IP-Symcon, however, a ping request from your service continues to arrive.

When I stop and restart the Docker container, the data is updated immediately. And the data can also be read out via the WeConnect app.
Is it also possible to view a log in the Docker version of your service? I couldn't find anything in Portainer at the last minute.
Best regards
Ralf Gronau

I recently discovered that too. I think this might happen when the connection to the broker is lost. I will investigate further.

Regarding the logging you have to increas loglevel by adding e.g. -vv to the ADDITIONAL_PARAMETERS. This will increse the loglevel

Hello Mr Steinbach,
Yesterday the data retrieval stopped again. But this time I was able to recognise something with a corresponding log entry.  Alternatively, you could perhaps include a parameter that restarts the system at a time to be specified as a parameter!
2023-02-14T19:49:14+0100:WARNING:departure_timers_status:/vehicles/WVWZZZ3CZME051453/domains/departureTimers/departureTimersStatus/timers/2: Unknown attribute targetSOC_pct with value 100,
2023-02-14T19:49:14+0100:WARNING:departure_timers_status:/vehicles/WVWZZZ3CZME051453/domains/departureTimers/departureTimersStatus/timers/3: Unknown attribute targetSOC_pct with value 100,
2023-02-14T19:54:15+0100:INFO:weconnect_mqtt_base:Update data from WeConnect,
2023-02-14T19:54:22+0100:WARNING:departure_timers_status:/vehicles/WVWZZZ3CZME051453/domains/departureTimers/departureTimersStatus/timers/1: Unknown attribute targetSOC_pct with value 100,
2023-02-14T19:54:22+0100:WARNING:departure_timers_status:/vehicles/WVWZZZ3CZME051453/domains/departureTimers/departureTimersStatus/timers/2: Unknown attribute targetSOC_pct with value 100,
2023-02-14T19:54:22+0100:WARNING:departure_timers_status:/vehicles/WVWZZZ3CZME051453/domains/departureTimers/departureTimersStatus/timers/3: Unknown attribute targetSOC_pct with value 100,
2023-02-14T19:59:22+0100:INFO:weconnect_mqtt_base:Update data from WeConnect,
2023-02-14T19:59:22+0100:INFO:openid_session:Token expired,
2023-02-14T19:59:22+0100:INFO:we_connect_session:Refreshing tokens,
2023-02-14T20:00:25+0100:WARNING:departure_timers_status:/vehicles/WVWZZZ3CZME051453/domains/departureTimers/departureTimersStatus/timers/1: Unknown attribute targetSOC_pct with value 100,
2023-02-14T20:00:25+0100:WARNING:departure_timers_status:/vehicles/WVWZZZ3CZME051453/domains/departureTimers/departureTimersStatus/timers/2: Unknown attribute targetSOC_pct with value 100,
2023-02-14T20:00:25+0100:WARNING:departure_timers_status:/vehicles/WVWZZZ3CZME051453/domains/departureTimers/departureTimersStatus/timers/3: Unknown attribute targetSOC_pct with value 100,
2023-02-14T20:05:26+0100:INFO:weconnect_mqtt_base:Update data from WeConnect,
2023-02-14T20:05:28+0100:WARNING:departure_timers_status:/vehicles/WVWZZZ3CZME051453/domains/departureTimers/departureTimersStatus/timers/1: Unknown attribute targetSOC_pct with value 100,
2023-02-14T20:05:28+0100:WARNING:departure_timers_status:/vehicles/WVWZZZ3CZME051453/domains/departureTimers/departureTimersStatus/timers/2: Unknown attribute targetSOC_pct with value 100,
2023-02-14T20:05:28+0100:WARNING:departure_timers_status:/vehicles/WVWZZZ3CZME051453/domains/departureTimers/departureTimersStatus/timers/3: Unknown attribute targetSOC_pct with value 100,
2023-02-14T20:10:29+0100:INFO:weconnect_mqtt_base:Update data from WeConnect,
2023-02-14T20:10:31+0100:WARNING:departure_timers_status:/vehicles/WVWZZZ3CZME051453/domains/departureTimers/departureTimersStatus/timers/1: Unknown attribute targetSOC_pct with value 100,
2023-02-14T20:10:31+0100:WARNING:departure_timers_status:/vehicles/WVWZZZ3CZME051453/domains/departureTimers/departureTimersStatus/timers/2: Unknown attribute targetSOC_pct with value 100,
2023-02-14T20:10:31+0100:WARNING:departure_timers_status:/vehicles/WVWZZZ3CZME051453/domains/departureTimers/departureTimersStatus/timers/3: Unknown attribute targetSOC_pct with value 100,
2023-02-14T20:15:32+0100:INFO:weconnect_mqtt_base:Update data from WeConnect,
2023-02-14T20:15:34+0100:WARNING:departure_timers_status:/vehicles/WVWZZZ3CZME051453/domains/departureTimers/departureTimersStatus/timers/1: Unknown attribute targetSOC_pct with value 100,
2023-02-14T20:15:34+0100:WARNING:departure_timers_status:/vehicles/WVWZZZ3CZME051453/domains/departureTimers/departureTimersStatus/timers/2: Unknown attribute targetSOC_pct with value 100,
2023-02-14T20:15:34+0100:WARNING:departure_timers_status:/vehicles/WVWZZZ3CZME051453/domains/departureTimers/departureTimersStatus/timers/3: Unknown attribute targetSOC_pct with value 100,
2023-02-14T20:20:34+0100:INFO:weconnect_mqtt_base:Update data from WeConnect,
2023-02-14T20:20:37+0100:WARNING:departure_timers_status:/vehicles/WVWZZZ3CZME051453/domains/departureTimers/departureTimersStatus/timers/1: Unknown attribute targetSOC_pct with value 100,
2023-02-14T20:20:37+0100:WARNING:departure_timers_status:/vehicles/WVWZZZ3CZME051453/domains/departureTimers/departureTimersStatus/timers/2: Unknown attribute targetSOC_pct with value 100,
2023-02-14T20:20:37+0100:WARNING:departure_timers_status:/vehicles/WVWZZZ3CZME051453/domains/departureTimers/departureTimersStatus/timers/3: Unknown attribute targetSOC_pct with value 100,
2023-02-14T20:25:38+0100:INFO:weconnect_mqtt_base:Update data from WeConnect,
2023-02-14T20:25:50+0100:WARNING:departure_timers_status:/vehicles/WVWZZZ3CZME051453/domains/departureTimers/departureTimersStatus/timers/1: Unknown attribute targetSOC_pct with value 100,
2023-02-14T20:25:50+0100:WARNING:departure_timers_status:/vehicles/WVWZZZ3CZME051453/domains/departureTimers/departureTimersStatus/timers/2: Unknown attribute targetSOC_pct with value 100,
2023-02-14T20:25:50+0100:WARNING:departure_timers_status:/vehicles/WVWZZZ3CZME051453/domains/departureTimers/departureTimersStatus/timers/3: Unknown attribute targetSOC_pct with value 100,
2023-02-14T20:30:50+0100:INFO:weconnect_mqtt_base:Update data from WeConnect,
2023-02-14T20:30:53+0100:WARNING:departure_timers_status:/vehicles/WVWZZZ3CZME051453/domains/departureTimers/departureTimersStatus/timers/1: Unknown attribute targetSOC_pct with value 100,
2023-02-14T20:30:53+0100:WARNING:departure_timers_status:/vehicles/WVWZZZ3CZME051453/domains/departureTimers/departureTimersStatus/timers/2: Unknown attribute targetSOC_pct with value 100,
2023-02-14T20:30:53+0100:WARNING:departure_timers_status:/vehicles/WVWZZZ3CZME051453/domains/departureTimers/departureTimersStatus/timers/3: Unknown attribute targetSOC_pct with value 100,
2023-02-14T20:35:54+0100:INFO:weconnect_mqtt_base:Update data from WeConnect,
2023-02-14T20:35:55+0100:CRITICAL:weconnect_mqtt_base:There was a problem when authenticating with WeConnect: You have to login at myvolkswagen.de and accept the terms and conditions,
2023-02-14T20:35:55+0100:INFO:weconnect_mqtt_base:Client successfully disconnected,
2023-02-14T20:36:06+0100:INFO:weconnect_mqtt_base:WeConnect-mqtt 0.41.1 (using WeConnect-python 0.50.1),
2023-02-14T20:36:06+0100:INFO:weconnect_mqtt_base:Connect to WeConnect,
2023-02-14T20:36:06+0100:INFO:weconnect_mqtt_base:Connected to MQTT broker,
2023-02-14T20:36:06+0100:INFO:weconnect_mqtt_base:Update data from WeConnect,
2023-02-14T20:36:07+0100:ERROR:client:Caught exception in on_connect: You have to login at myvolkswagen.de and accept the terms and conditions,
Exception in thread Thread-1 (_thread_main):,
Traceback (most recent call last):,
File "/usr/local/lib/python3.11/threading.py", line 1038, in _bootstrap_inner,
self.run(),
File "/usr/local/lib/python3.11/threading.py", line 975, in run,
self._target(*self._args, **self._kwargs),
File "/usr/local/lib/python3.11/site-packages/paho/mqtt/client.py", line 3591, in _thread_main,
self.loop_forever(retry_first_connection=True),
File "/usr/local/lib/python3.11/site-packages/paho/mqtt/client.py", line 1756, in loop_forever,
rc = self._loop(timeout),
^^^^^^^^^^^^^^^^^^^,
File "/usr/local/lib/python3.11/site-packages/paho/mqtt/client.py", line 1164, in _loop,
rc = self.loop_read(),
^^^^^^^^^^^^^^^^,
File "/usr/local/lib/python3.11/site-packages/paho/mqtt/client.py", line 1556, in loop_read,
rc = self._packet_read(),
^^^^^^^^^^^^^^^^^^^,
File "/usr/local/lib/python3.11/site-packages/paho/mqtt/client.py", line 2439, in _packet_read,
rc = self._packet_handle(),
^^^^^^^^^^^^^^^^^^^^^,
File "/usr/local/lib/python3.11/site-packages/paho/mqtt/client.py", line 3039, in _packet_handle,
return self._handle_connack(),
^^^^^^^^^^^^^^^^^^^^^^,
File "/usr/local/lib/python3.11/site-packages/paho/mqtt/client.py", line 3138, in _handle_connack,
on_connect(,
File "/usr/local/lib/python3.11/site-packages/weconnect_mqtt/weconnect_mqtt_base.py", line 585, in on_connect_callback,
self.updateWeConnect(),
File "/usr/local/lib/python3.11/site-packages/weconnect_mqtt/weconnect_mqtt_base.py", line 446, in updateWeConnect,
self.weConnect.update(updateCapabilities=self.updateCapabilities, updatePictures=self.updatePictures, selective=self.selective),
File "/usr/local/lib/python3.11/site-packages/weconnect/weconnect.py", line 191, in update,
self.updateVehicles(updateCapabilities=updateCapabilities, updatePictures=updatePictures, force=force, selective=selective),
File "/usr/local/lib/python3.11/site-packages/weconnect/weconnect.py", line 199, in updateVehicles,
data = self.fetchData(url, force),
^^^^^^^^^^^^^^^^^^^^^^^^^^,
File "/usr/local/lib/python3.11/site-packages/weconnect/weconnect.py", line 364, in fetchData,
statusResponse: requests.Response = self.session.get(url, allow_redirects=False),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^,
File "/usr/local/lib/python3.11/site-packages/requests/sessions.py", line 600, in get,
return self.request("GET", url, **kwargs),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^,
File "/usr/local/lib/python3.11/site-packages/weconnect/auth/we_connect_session.py", line 69, in request,
return super(WeConnectSession, self).request(,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^,
File "/usr/local/lib/python3.11/site-packages/weconnect/auth/openid_session.py", line 192, in request,
url, headers, data = self.addToken(url, body=data, headers=headers, access_type=access_type, token=token),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^,
File "/usr/local/lib/python3.11/site-packages/weconnect/auth/openid_session.py", line 229, in addToken,
self.login(),
File "/usr/local/lib/python3.11/site-packages/weconnect/auth/we_connect_session.py", line 76, in login,
response = self.doWebAuth(authorizationUrl),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^,
File "/usr/local/lib/python3.11/site-packages/weconnect/auth/we_connect_session.py", line 242, in doWebAuth,
raise AuthentificationError('You have to login at myvolkswagen.de and accept the terms and conditions'),
weconnect.errors.AuthentificationError: You have to login at myvolkswagen.de and accept the terms and conditions,
2023-02-14T20:41:06+0100:INFO:weconnect_mqtt_base:Update data from WeConnect,
2023-02-14T20:41:08+0100:CRITICAL:weconnect_mqtt_base:There was a problem when authenticating with WeConnect: You have to login at myvolkswagen.de and accept the terms and conditions,
Best regards
Ralf Gronau

The problem here is that you actively have to login at Volkswagen and accept the new terms and conditions. This is something the software cannot recover from itself.


CMAKE package dependencies

The cmake file could probably use some changes for alternative names for allegro-5.0.pc and allegro_image-5.0.pc. I have these files in a custom location where pkg-config knows where they are. However, they were installed as allegro-5.pc and allegro_image-5.pc, so I got an error at first when using cmake. Was easy enough for me to create symlinks to them, but would be nice if this package detected these names on its own. If it's of any importance, I am using the latest allegro (5.1) available at the time of this writing.

Is there any official Allegro documentation for how package config files are supposed to be named? I'm curious if these will change with each point release, or if allegro-5.pc is a safe assumption until the release of Allegro 6.

I haven't been able to find any documentation about this.

@ElectricSolstice , can you try checking out the cmake_pkg_deps branch and see if that works for you? I changed CMakeLists to check for allegro-5.pc and fall back to allegro-5.0.pc if it's not found.

When I try that branch, I get this error.
cmake .
CMake Error at CMakeLists.txt:27 (pkg_search_modules):
  Unknown CMake command "pkg_search_modules".

-- Configuring incomplete, errors occurred!

Alright, I think I finally got it working. Can you give the cmake_pkg_deps branch another shot?

It's working now on my computer.

Cool, feel free to open comment here if this becomes an issue again.


Problems guessing column type data begin with large blank.

One of my column started with blank for quite large (about 8000 rows), then follow with the text data.
When importing, there are warning that this column was determined to be integer and then importing fails, resulted in all NA for this column.
My only work-aroud is to specify all the col_type.

Duplicate of #131
Temporary solution:
# install.packages("devtools")
devtools::install_github("tklebel/readxl")
read_excel("file.xlsx", n = 10000)

Sorry for the duplicated issue.
Thx for you promptly reply.


Update schema compare extension to support SQL Login

This PR fixes the scenario where SchemaCompare can't reload an scmp where the source or target uses username/password to connect since the password is not persisted.
If the connection profile doesn't yield a connection Uri, the fix actually goes in and checks within the active connections list to get the connection details. If not, connection dialog opens up to get the connection information, upon approval.
This PR fixes #6833

@Benjin Yes, your understanding of null vs undefined is correct. But we just don't use that model in our code base currently - it's all undefineds.


conda-env-activate doesn't work but conda-env-list does

I'm not sure if this is a package problem or a system config problem, so sorry if this is in the wrong place, but I was hoping you may have some experience with this even if it isn't!
conda-env-list works fine, but conda-env-activate generates the error
conda--get-path-prefix: Error: executing command "/home/username/miniconda3/bin/conda ..activate "bash" "/home/username/miniconda3/envs/scratch/"" produced error code 2

My main shell is zsh, but I can conda activate fine from both it and bash on my system. Though conda activate from eshell in emacs also doesn't work.
It seems like the error could be calling conda from the path. While I can call simply conda activate from my shell, doing it from the path as /home/username/miniconda3/bin/conda activate fails with the error
CommandNotFoundError: Your shell has not been properly configured to use 'conda activate'.
...

I have similar behvaiour to the conda.el package though, in that /home/username/miniconda3/bin/conda info -e works fine.
I'm running emacs 27, with doom emacs. Here is the output from doom info
generated  Jul 31, 2022 00:02:35
system     Linux Mint 20.3 Linux 5.4.0-122-generic x86_64
emacs      27.1 ~/.emacs.d/ -> ~/.emacs.d/
doom       3.0.0-dev HEAD -> master, origin/master, origin/HEAD 615848e3a 2022-07-31 00:58:36 +0200 ~/.doom.d/ -> ~/.doom.d/
shell      /usr/bin/zsh
features   XPM JPEG TIFF GIF PNG RSVG CAIRO SOUND GPM DBUS GSETTINGS GLIB NOTIFY INOTIFY ACL LIBSELINUX GNUTLS LIBXML2 FREETYPE HARFBUZZ
	   M17N_FLT LIBOTF ZLIB TOOLKIT_SCROLL_BARS GTK3 X11 XDBE XIM MODULES THREADS XWIDGETS LIBSYSTEMD JSON PDUMPER LCMS2 GMP
traits     batch server-running envvar-file custom-file
modules    :completion company vertico :ui doom doom-dashboard (emoji +unicode) hl-todo modeline ophints (popup +defaults) treemacs
	   vc-gutter vi-tilde-fringe workspaces :editor (evil +everywhere) file-templates fold (format +onsave) parinfer snippets :emacs
	   dired electric undo vc :term eshell :checkers syntax :tools lookup lsp magit :lang emacs-lisp json markdown (org +pretty +jupyter
	   +roam2) (python +lsp +conda +pyright) :config (default +bindings +smartparens)
packages   (evil-tutor) (catppuccin-theme) (org-modern)

Could you please provide the output of conda info?

Here your go!
     active environment : base
    active env location : /home/username/miniconda3
            shell level : 1
       user config file : /home/username/.condarc
 populated config files : /home/username/.condarc
          conda version : 4.13.0
    conda-build version : not installed
         python version : 3.9.5.final.0
       virtual packages : __cuda=11.4=0
                          __linux=5.4.0=0
                          __glibc=2.31=0
                          __unix=0=0
                          __archspec=1=x86_64
       base environment : /home/username/miniconda3  (writable)
      conda av data dir : /home/username/miniconda3/etc/conda
  conda av metadata url : None
           channel URLs : https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
          package cache : /home/username/miniconda3/pkgs
                          /home/username/.conda/pkgs
       envs directories : /home/username/miniconda3/envs
                          /home/username/.conda/envs
               platform : linux-64
             user-agent : conda/4.13.0 requests/2.27.1 CPython/3.9.5 Linux/5.4.0-122-generic linuxmint/20.3 glibc/2.31
                UID:GID : 1000:1000
             netrc file : None
           offline mode : False

I have the same issue.  Downgrading conda to 4.12.0 seems to fix it, so it must have something to do with whatever changed in 4.13.0
Works fine:
conda install -n base conda=4.12.0

Gives error message when calling conda-env-activate:
conda install -n base conda=4.13.0

Hmm, that implies that it's calling the deprecated activator method. Do you happen to know for sure which version (git hash) of conda.el you're using?

I had the same issue with doom and I can confirm it is now fixed after fixing doom emacs issue 6626
The doom's maintainer pinned the conda.el version to current latest commit a65ed0084876366fd1b238bb2b8b36ee75ac98d8

Looks like it was an issue with doom pinning the conda.el version, and the newest conda.el version works fine. This has also been incorporated into doom, and running doom upgrade has now fixed the problem for me so I'm closing this. Thanks for everyone's help!


Temp Files for Score and Metadata Files

Creates a decorator for mapping routines which creates a temporary directory in which score set metadata and score files can be downloaded. The directory path is then passed to the mapping routine so that these temp files can be used by the mapper. Once the wrapped function exits, the temporary directory is purged.

Looks great!


Stop sending metrics to builder name

This is a following up of https://github.com/flutter/flutter/pull/92530.
More than 14 commit data points have been collected, and we are ready to deprecate sending data to old benchmark names. This will not affect existing alerts which are independent of benchmark names.
With this PR, users of Skia Perf are expected to view trending charts based on new benchmark names (the test names). We need to send a PSA before this lands.
Related issue: https://github.com/flutter/flutter/issues/74522, https://github.com/flutter/flutter/issues/92203

A friendly ping /cc @zanderso


#6736, #6738: Improve watcher error reporting

Show both logical and physical coords in the watcher log
Clean up log alignment, stdout formatting
Show what core illegal noc transaction was trying to access
Show reason why illegal noc transaction was flagged
Fix illegal noc transaction always showing memory as L1

Passing CI:
https://github.com/tenstorrent-metal/tt-metal/actions/runs/8546067848
https://github.com/tenstorrent-metal/tt-metal/actions/runs/8546451134

Removed #6738 changes, can we just merge the #6736 changes?

Passing CI: https://github.com/tenstorrent-metal/tt-metal/actions/runs/8572995474
https://github.com/tenstorrent-metal/tt-metal/actions/runs/8573000765


test: add unit test for Notify

Description
Add unit test for Notify.
Related Issue

Motivation and Context

Screenshots (if appropriate)
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation Update (if none of the other choices apply)

Checklist

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.

If you use table driven tests, then you have to test different cases.

Done, thanks for the review!


"Signup/Login" button always takes you to Sign up

Resolved
Commit 5bddc3f
Split Log in/ sign up into two buttons with two separate routes.


bug: add support fo 64k page size

cat /etc/redhat-release
Red Hat Enterprise Linux release 9.4 (Plow)
uname -r
5.14.0-427.13.1.el9_4.aarch64+64k
Needed modules:
kernel-64k-devel.aarch64
kernel-64k-modules.aarch64

@rollandf can you provide more info in commit msg, what is the meaning of support 64k page size
i.e please mention the kernel version as appears in uname -r as well as the kernel packages that need to be installed.

@rollandf can you provide more info in commit msg, what is the meaning of support 64k page size i.e please mention the kernel version as appears in uname -r as well as the kernel packages that need to be installed.
it would help me do a review of this one :)

Sorry, about that. I added more info.

26-Sep-24_12:00:35] NVIDIA driver container exec start
[26-Sep-24_12:00:35] OS is Red Hat
[26-Sep-24_12:00:35] [os-release]: NAME="Red Hat Enterprise Linux" VERSION="9.2 (Plow)" ID="rhel" ID_LIKE="fedora" VERSION_ID="9.2" PLATFORM_ID="platform:el9" PRETTY_NAME="Red Hat Enterprise Linux 9.2 (Plow)" ANSI_COLOR="0;31" LOGO="fedora-logo-icon" CPE_NAME="cpe:/o:redhat:enterprise_linux:9::baseos" HOME_URL="https://www.redhat.com/" DOCUMENTATION_URL="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9" BUG_REPORT_URL="https://bugzilla.redhat.com/" REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 9" REDHAT_BUGZILLA_PRODUCT_VERSION=9.2 REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux" REDHAT_SUPPORT_PRODUCT_VERSION="9.2"
[26-Sep-24_12:00:35] [uname -a]: Linux co-node-38.maas 5.14.0-427.13.1.el9_4.aarch64+64k #1 SMP PREEMPT_DYNAMIC Wed Apr 10 15:34:42 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

....
[26-Sep-24_12:00:35] Function: redhat_fetch_major_ver
[26-Sep-24_12:00:35] Executing command: egrep "^ID=|^VERSION_ID=|^RHEL_VERSION=" /host/etc/os-release
ID="rhel"
VERSION_ID="9.4"
declare -- ID="rhel"
declare -- VERSION_ID="9.4"
[26-Sep-24_12:00:35] RHEL major version: 9
[26-Sep-24_12:00:35] Installing dependencies
[26-Sep-24_12:00:35] 64k page size kernel identified
[26-Sep-24_12:00:35] Executing command: cp /host/etc/yum.repos.d/redhat.repo /etc/yum.repos.d/

[26-Sep-24_12:00:35] Executing command: dnf -q -y install kernel-64k-devel-5.14.0-427.13.1.el9_4.aarch64

Installed:
  bison-3.7.4-5.el9.aarch64
  elfutils-libelf-devel-0.188-3.el9.aarch64
  flex-2.6.4-9.el9.aarch64
  kernel-64k-devel-5.14.0-427.13.1.el9_4.aarch64
  openssl-devel-1:3.0.7-17.el9_2.aarch64
  zlib-devel-1.2.11-39.el9.aarch64
[26-Sep-24_12:01:20] Executing command: dnf -q -y install kernel-64k-modules-5.14.0-427.13.1.el9_4.aarch64

Installed:
  kernel-64k-core-5.14.0-427.13.1.el9_4.aarch64
  kernel-64k-modules-5.14.0-427.13.1.el9_4.aarch64
  kernel-64k-modules-core-5.14.0-427.13.1.el9_4.aarch64
  linux-firmware-20240716-143.2.el9_4.noarch
  linux-firmware-whence-20240716-143.2.el9_4.noarch
[26-Sep-24_12:02:05] Executing command: dnf -q -y --releasever=9.4 install elfutils-libelf-devel kernel-rpm-macros numactl-libs lsof rpm-build patch hostname

Upgraded:
  elfutils-debuginfod-client-0.190-2.el9.aarch64
  elfutils-libelf-0.190-2.el9.aarch64
  elfutils-libelf-devel-0.190-2.el9.aarch64
  elfutils-libs-0.190-2.el9.aarch64
  python3-rpm-<IP_ADDRESS>-29.el9.aarch64
  rpm-<IP_ADDRESS>-29.el9.aarch64
  rpm-build-libs-<IP_ADDRESS>-29.el9.aarch64
  rpm-libs-<IP_ADDRESS>-29.el9.aarch64
  rpm-sign-libs-<IP_ADDRESS>-29.el9.aarch64
Installed:
  bzip2-1.0.8-8.el9.aarch64               debugedit-5.0-5.el9.aarch64
  ed-1.14.2-12.el9.aarch64                elfutils-0.190-2.el9.aarch64
  gdb-minimal-10.2-13.el9.aarch64         info-6.7-15.el9.aarch64
  kernel-rpm-macros-185-13.el9.noarch     libtirpc-1.3.3-8.el9_4.aarch64
  libzstd-devel-1.5.1-2.el9.aarch64       lsof-4.94.0-3.el9.aarch64
  numactl-libs-2.0.16-3.el9.aarch64       patch-2.7.6-16.el9.aarch64
  python-rpm-macros-3.9-53.el9.noarch     python3-packaging-20.9-5.el9.noarch
  python3-rpm-generators-12-9.el9.noarch  python3-rpm-macros-3.9-53.el9.noarch
  rpm-build-<IP_ADDRESS>-29.el9.aarch64       zstd-1.5.1-2.el9.aarch64
Updating Subscription Management repositories.
Unable to read consumer identity
Subscription Manager is operating in container mode.

This system is not registered with an entitlement server. You can use subscription-manager to register.

Red Hat Enterprise Linux 9 for ARM 64 - AppStream (RPMs)                                                          8.3 kB/s | 4.5 kB     00:00
Red Hat Enterprise Linux 9 for ARM 64 - BaseOS (RPMs)                                                             4.8 kB/s | 4.1 kB     00:00
Red Hat Universal Base Image 9 (RPMs) - BaseOS                                                                     62 kB/s | 3.8 kB     00:00
Red Hat Universal Base Image 9 (RPMs) - AppStream                                                                  79 kB/s | 4.2 kB     00:00
Red Hat Universal Base Image 9 (RPMs) - CodeReady Builder                                                          66 kB/s | 3.8 kB     00:00
Metadata cache created.
[26-Sep-24_12:02:24] Function: build_driver_from_src
[26-Sep-24_12:02:24] Starting driver build
[26-Sep-24_12:02:24] Executing command: /run/mellanox/src/MLNX_OFED_SRC-24.07-<IP_ADDRESS>/install.pl --without-depcheck --kernel 5.14.0-427.13.1.el9_4.aarch64+64k --kernel-only --build-only --with-mlnx-tools --without-knem --without-iser --without-isert --without-srp --without-kernel-mft --without-mlnx-rdma-rxe --without-mlnx-nfsrdma --without-mlnx-nvme --disable-kmp
Logs dir: /tmp/OFED.22527.logs
General log file: /tmp/OFED.22527.logs/general.log


fix: await buildDone hook

Types of changes

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

Description

Checklist:

[ ] 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)
[ ] All new and existing tests are passing.

Codecov Report

Merging #4955 into dev will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##              dev    #4955   +/-   ##
=======================================
  Coverage   92.93%   92.93%
=======================================
  Files          73       73
  Lines        2419     2419
  Branches      594      594
=======================================
  Hits         2248     2248
  Misses        156      156
  Partials       15       15

Impacted Files
Coverage Δ

packages/server/src/middleware/nuxt.js
98.52% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Mesh Output view doesn't work when using min16* types in HLSL

When using min16 precision types in HLSL several Mesh Output panes don't work. The only thing that shows up is the index buffer in the VS Input pane.
min16.zip contains a minimal .fx file for repro (adapted from Direct3D11Tutorial\Tutorial07) and a log.
Tested using v0.90.

Thanks for the nice repro case. I've added support for min precision (min16/min10 etc), although it's only really in name, since AFAIK D3D's min precision only affects variables within the shader, anything externally facing just gets promoted to 32-bit. At the least, constant buffer values are still expected to be 32-bit, I guess inter-stage stuff could be optimised to 16-bit if the implementation allows, but the mesh output uses stream-out which promotes things to full float.
It's fixed on v0.x so the next v0.x nightly build should work, let me know if you have any more problems.

Thanks for the fast response! I Just tested by building from source and it works fine.
If if I put in 16-bit values using an input layout like this:
D3D11_INPUT_ELEMENT_DESC layout[] =
{
{ "POSITION", 0, DXGI_FORMAT_R16G16B16A16_FLOAT, 0, 0, D3D11_INPUT_PER_VERTEX_DATA, 0 },
{ "TEXCOORD", 0, DXGI_FORMAT_R16G16_FLOAT, 0, 8, D3D11_INPUT_PER_VERTEX_DATA, 0 },
};
at least the shader disassembly shows up as using min16f types instead of def32/min16f as def32 and renderdoc also shows the format correctly in the Input Assembler view.
I gathered my modifications into Tutorial07Modifications.zip. You can apply it on top of the Direct3D11Tutorials/Tutorial07 folder from https://github.com/walbourn/directx-sdk-samples.
I also have a follow up on this:
When using the pixel shader debugger, values from 16-bit interpolators get set to all zero. In the example I attached it's v1 (TEXCOORD) and v2 (COLOR).

I tried on the latest build but I can't repro that pixel shader debugging issue - for me the pixel debug values come out fine. I tried on both the min16float.rdc you attached originally, and on a newly compiled version from that tutorial + your modifications. Can you send the .rdc you're debugging and a pixel that isn't working for you? Also just to be sure, can you try with the latest v0.x nightly build so we're both using the same source revision.
About the vertex input stuff - I think this would still be only used internally by the driver, it doesn't change what datatypes are valid for the input layout. It's totally valid to pass DXGI_FORMAT_R16G16B16A16_FLOAT input data to a shader that declared a float4 input, and this is quite common for most vertex inputs since it's rare to need full 32-bit precision. The shader will just read the half data and convert it to full floats after reading in the shader - with the min16float hint the compiler can optionally skip that conversion and pipe it into further half computations. Since the shader is compiled independently of the input layout description I think the min16f annotations are just indicating that it's declared to possibly accept 16F data without change.
The {min16f} vs any other type of disassembly annotationse I don't really understand (and it's not documented AFAIK). In the same commit I switched renderdoc's disassembly to just use {min16f} everywhere since the as def32 was just a lot of noise, and it's not clear where it's applied and where it's not.

Sure thing, here's log I captured with the 32bit 2017-08-15 nightly.
Any pixel will do, here's a screenshot of the debugger for pixel 425, 420

Ah, I see, thanks for the clarification. In our experience AMD cards tend to actually take the 16 bit hints seriously (:

Hmm, unfortunately I still get normal shader debugging. I tried on a windows 10 pc (since on my normal win7 pc the min precision stuff won't be active) and with nvidia/amd, but no luck. I tried the 32-bit nightly but it behaved the same.
What hardware/driver version are you on? try updating drivers if there's a newer one available.
My best guess aside from driver wonkiness is that when I run a special fragment shader to gather the interpolator inputs for the shader debugging, there's a signature mismatch because I declare the inputs as float4 instead of min16float4. However I don't get any warnings from the D3D debug layer, and it seems to work fine in every case I can test.
Would you be up for diving into the code if I told you where to look, and breakpoint/add some hacks to test the theory?

A colleague of mine checked on his machine with an Nvidia Titan X and it worked. For me on an R9 Fury it doesn't. I'm leaving for a vacation now, but I'll follow up when I'm back end of August. If it's not the driver, then I can help with checking the code, as you suggest.

Colleague here. We updated the garphics driver for the R9 Fury and the shader debugging is now working correctly. You can close this issue as fixed. Thank you very much for the quick fix! RenderDoc is really an awesome peace of software.

Interesting! I'm glad it's fixed.
Thanks again for the clear & easy repro, and if you run into any other issues then my door is always open :smile:

Great, thanks again for the quick fix!
We'll be sure to do that.


Custom HTTP response header from license response

Our Widevine license proxy service needs to return some values to the client app (Shaka Player).
We decided to use a custom HTTP header in the license response message.
I try to use a response filter in the NetworkingEngine to get the custom header field,
however, Shaka Player does not return the custom header field in the response object.
Does the Shaka Player supports this usage?  Is there an example app for this usage?

This sounds like a CORS issue.  Cross-origin, your license server must explicitly expose the header, as well.  Otherwise, the browser will not allow the JavaScript application to see it.
See: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Expose-Headers
Does this help?

Yes, exactly as you said.
Also, the header name is changed to all lower case.

Glad to hear it!  Since it sounds like everything's resolved, I'll go ahead and close the issue.


Bump versions for Qiskit 0.45.3

Summary
This also includes a minor fixup of the only release note for the version.

Details and comments
... not at all stressed that this might be the most unstable change we've ever applied to a patch release - deliberately poisoning the import.

Yeah, in theory it should only raise an error on an invalid environment.  I really really hope I/we haven't missed any esoteric Python setups people have in the consideration, though!

Let's just admin merge this after CI finishes, it's not worth another round trip through CI for the merge queue.

Yeah, I was already queue-skipping it to the top of the Azure pile, but there's no need to go through another run.  The PR is already up-to-date with stable/0.45.


Feature/release setup

Summary

Removes the error-handler-core from the application app module and the app core will expose it.
error-handler-rest can't be used without the error-handler-core. For this, the rest module will expose it's transitive dependency to error-handler-core.
Add the bintray deployment setup.

How to test

Sync the project
run the publishToMavenLocal gradle task (make sure to run for the whole project or for both lib modules). This will create an artifact in the local maven repository.
Add mavenLocal() below jCenter() in repositories { .. }

repositories {
        ...
        jcenter()
        mavenLocal()
        ...
    }

Change the dependency in the app-core module from api project(':error-handler-rest')
to  implementation "com.halcyonmobile.error-handler:rest:0.1.0"
Sync & Install the app

@tamashalcyon Your issue is caused by this
implementation "com.halcyonmobile.error-handler:rest:0.1.0"
Since this is in the core module and we need also it the app module, implementation needs to be api, the how to test section was incorrect (updated that as well).


Add subscription support

This should add subscription support: the parser, schema, and unifier now knows about that operation type. Fixes #33.
I don't have a good setup to test subscription support, but I assume the responses look just like the responses from queries and mutations. @Gregoirevda, could you maybe verify that this is the case for reason-apollo?

I confirm the pxx work well:
https://github.com/apollographql/reason-apollo/pull/104

@mhallin  planning to release soon?


Consistent naming convention for pix vs. pixel

I'm not sure if there is an agreed upon convention, but I would suggest:

pixel used for arrays
pix used for array iterator


Clarify Gateway Listener Status AttachedRoutes field

What type of PR is this?
/kind cleanup
/kind documentation
What this PR does / why we need it:
Document that the field intends to count purely Gateway<->Route relationships regardless of validity of either resource.
Which issue(s) this PR fixes:
Fixes #1626
Does this PR introduce a user-facing change?:
Clarify that the Gateway Listener status AttachedRoutes field is a count of the number of Routes associated with a Listener regardless of Gateway or Route status.

/approve
Nice work, thanks @sunjayBhatia!


Upgrade the runtime images with rhods runtime,ref:b7e647e

Upgrade the runtime images with rhods runtime,ref:b7e647e
The runtime image are updated with RHODS based image from quay.io/modh.
Commit reference: https://github.com/red-hat-data-services/notebooks/commit/b7e647edd3e637e7d22f4a3ef0200d128c87d296
Tags:

runtime-cuda-tensorflow-ubi9-python-3.9-2023a-20230817-b7e647e
runtime-cuda-tensorflow-ubi8-python-3.8-2023a-20230817-b7e647e
runtime-pytorch-ubi9-python-3.9-2023a-20230817-b7e647e
runtime-pytorch-ubi8-python-3.8-2023a-20230817-b7e647e
runtime-datascience-ubi8-python-3.8-2023a-20230817-b7e647e
runtime-datascience-ubi9-python-3.9-2023a-20230817-b7e647e
runtime-minimal-ubi9-python-3.9-2023a-20230817-b7e647e
runtime-minimal-ubi8-python-3.8-2023a-20230817-b7e647e

Merging this to get the final result image for RHODS-1.32 ready.
Thanks.


added base telemetry types/interfaces

Description
Adds new set of telemetry types and interfaces, identical to ITelemetryProperties (with the addition of null). ITelemetryProperties has been changed to deprecated, as it will be repurposed to support flat arrays and objects in a future release.
Added:

TelemetryBaseEventPropertyType
TaggedBaseTelemetryPropertyType
ITelemetryBaseProperties

This PR is a subset of #12119, as it was suggested that the changes should be staged through multiple releases.
Reviewer Guidance
Questions

Is common/lib/common-definitions/BREAKING.md the correct location to add the "Upcoming" note? Or should this have been added into the Upcoming.md file in the root directory?
Should I specify the version for the "Upcoming" note? If so, is the version I should specify 0.21?

@ssimic2 / @scottn12 - can you answer his questions about where to put the "Upcoming" note?

As I mentioned in Teams, I think we should pause this PR (and the other ones we keep iterating on) and get a plan written down on paper and shared at Office Hours.  I can definitely help.  The layers upon layers of staging and rolling out these type changes is surprising, and you really want to get it right on the first go because iterating is so costly.
When I realized this was the only change to common-definitions in next it gave me pause, realizing all the follow-up PRs you'll have to do to roll this out, and that we probably want to carefully front-load the other additive changes in the same release.
Honestly, the scope of this work has crept a bit, your actual goal is to make an additive change to the interfaces we use internally, meanwhile we're sitting here looking at a PR making a breaking change to an external interface.  Way harder.  So let's get focused on tactically getting your additive changes in, and document other changes we may want in this space so we can discuss as a team and then cost/schedule the work independently from your task.

@ssimic2 / @scottn12 - can you answer his questions about where to put the "Upcoming" note?

This is the correct location! I think not everyone is aware of this file, but that is a separate issue we need to address


Update to xunit 2.3

Other aspnet repos have upgrade xunit to 2.3 while EF remains on 2.2. Upgrading to 2.3 will be a non-trivial task because this upgrade bundles xunit.analyzers which will fail the build.
Possible solutions:

Upgrade to the xunit 2.3 runtime but exclude the analyzer. Currently difficult because of: https://github.com/dotnet/sdk/issues/1212
Fix all of the analyzer errors
Upgrade to 2.3 but add a ruleset to make xunit.analyzer errors  "Info" or "Hidden" instead: see https://github.com/dotnet/roslyn/blob/master/docs/compilers/Rule Set Format.md

FYI - here are the warnings and errors triggered by xunit.analyzers:
Name            Count   Meaning
----            -----   -------
xUnit1000       10      Test classes must be public
xUnit1003       420     Theory methods must have test data
xUnit1004       220     Test methods should not be skipped
xUnit1005       210     Fact methods should not have test data
xUnit1008       24      Test data attribute should only be used on a Theory
xUnit1010       1148    Type mismatch between InlineData and method parameter
xUnit1013       4848    Public method on a test class is not marked as Fact or Theory
xUnit2000       76      A literal or constant value is given as the 'actual' value in a call to Assert.Equal(expected, actual)
xUnit2002       64      Do not use Assert.NotNull() on value type 'bool'.
xUnit2003       108     Do not use Assert.Equal() to check for null value. (Use Assert.NotNull or Assert.Null)
xUnit2004       188     Do not use Assert.Equal() to check for boolean conditions. (Use Assert.True or Assert.False)

By the way, I suspect the total number is actually half as many. The errors/warnings appear once per target framework and tests currently target net46 and netcoreapp2.0

I will tackle some of these (small count ones to fix. May ignore the one with 4848 count.

@smitpatel here's the build log produced from compiling https://github.com/natemcmaster/EntityFramework/commit/fe05abd219b72e2f67b7ec2dca8c8b4a580e2960. It contains the files/line numbers that produced these warnings.
ef.txt

Note: also there are various skipped test warning coming up in test output due to theories having duplicated data. Clean up that part too.


Add testOutputsDirectory to flutter_drive

Declares a top-level getter that returns the outputs directory to which
Flutter Driver tests can write any output files. Timeline data defaults
to this directory.

/cc @yjbanov


ISPN-12124 OracleTableManager is overly conservative with object name…

… max length
https://issues.redhat.com/browse/ISPN-12124

Put on hold until I think about migration side effects.

Looks like the only migration side effect is that there may be an extra index for both segment and timestamp index.

One related failure:
Error
expected [null] but found [1]
Stacktrace
java.lang.AssertionError: expected [null] but found [1]
	at org.infinispan.tools.store.migrator.MigratorConfigurationTest.testDbPropertiesLoaded(MigratorConfigurationTest.java:222)
	at org.infinispan.commons.test.TestNGLongTestsHook.run(TestNGLongTestsHook.java:24)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)
... Removed 23 stack frames

One related failure:
Error
expected [null] but found [1]
Stacktrace
java.lang.AssertionError: expected [null] but found [1]
	at org.infinispan.tools.store.migrator.MigratorConfigurationTest.testDbPropertiesLoaded(MigratorConfigurationTest.java:222)
	at org.infinispan.commons.test.TestNGLongTestsHook.run(TestNGLongTestsHook.java:24)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)
... Removed 23 stack frames

Checking

Test should be updated now to ignore the min/max db properties

Merged, thanks


it is failed when running the example

I ran in a issue when npm install:
npm ERR! code 127
npm ERR! path /Users/yanteng/Projects/FAW/libs/gantt-task-react-main
npm ERR! command failed
npm ERR! command sh -c run-s build
npm ERR! sh: run-s: command not found
npm ERR!      /Users/yanteng/.npm/_logs/2023-03-16T07_51_34_395Z-debug-0.log
could someone know how to fix it?

Did you navigate into the example folder first?

Yes， I fixed it by using this command：
npm install create-react-app

npm install create-react-app

Also ran into this error. Npm installing the root repository first and then the example directory worked for me.


Added a logo proposition : Proposed_Logo.svg

Hi,
The pull request is made in relation to Issue #31
And it is made in the context of Hacktoberfest.
I have made a proposition for your logo which is the file "Propositon_Logo.svg".
Best regards

Hello, I do not understand why there is a failure of ci/bitrise. The error message does not explain the issue so that I am not able to solve it.

Ping @mugbug could you please have a look at my pull request and help me progress by labelling it as "hacktoberfest-accepted" please ?

Thank you !


how to use command with this driver with geoNear query?

mongodb office command lilke below:
db.runCommand( {
geoNear:  ,
near: { type: "Point" , coordinates: [  ] } ,
spherical: true,
...
} )
http://docs.mongodb.org/manual/reference/command/geoNear/
how to do the same with mongodb-erlang driver?

Use this as a selector :
{ '$near' , { '$geometry', { 'type', <<"Point">>, 'coordinates', [Latt, Long] } , '$maxDistance', Max} }

If the "Max" here instead were to be defined by a property in the document (as being discussed for instance here: https://stackoverflow.com/questions/35329898/how-to-use-a-document-property-for-maxdistance-in-a-nearsphere-query). Would there still be a way to make such a query with mongodb-erlang? The "aggregate" function is not exposed, am I right?


Update UG

make it clear for addattribute it does not allow for multiple attributes of the same name but for add person it allows for multiple attribuets of the same name and that it takes the last duplicate attribute.

done