Parsing gradients with regex

Will give incomplete data if user supplied regex does not correctly grab all atoms.
Needs a safeguard by checking that the gradient has the same number of rows as the number of atoms or something.

Also, if dummy atoms are in use, codes will likely not print these in the gradient, so checking for the number of atoms might be problematic.


test: fix test for missing regex translations

The NetRegexes flag needs to be set prior to import when it is
used for evaluation.  This was broken due to a final change to #4433
without being properly retested.
Also, some small cleanups while here.
This is working towards #1306 as well.

Landing this promptly so that no errors creep in here.


[15.0.x] ISPN-16103 CrossSite: Wait for prepare command in case of local failure

https://issues.redhat.com/browse/ISPN-16103

Thanks @pruivo


Malformed response from Lens transactions

Hello,
While porting the Quidli frame for FC into Lens, I've found that once a transaction is performed properly, I don't receive a TxHash in the response. Actually, the response seems to be malformed in some way and the target frame of the post action can't load at all.
https://github.com/Quidli/debug-frames-lens/pull/1
@defispartan made a fix in this demo code that works fine when the frame is anonymous. In that case, the response looks good and I find a TxHash in it, but setting Lens as the client automatically makes it fail.
As he suggested, there might be some issue in the framesjs debugger. I can't be more specific as I have no idea where the issue could be, but would be nice to have some information and eventually a fix.
Thanks

@lusorio I don't see also open frames support for lens here https://github.com/Quidli/debug-frames-lens/blob/366ca0043f2167545257023183f90359ebb08638/app/frames/frames.ts#L16-L32 have you tried setting up the middleware to handle Lens? See https://framesjs.org/guides/lens#create-your-frames-app

Another issue I found is in Lens support @defispartan implemented. I don't see any mention of transactionId there so that could probably be the culprit.
Here transactionId is missing https://github.com/framesjs/frames.js/blob/4df7a3ab065c9ae67bb167b052bdc298af7e4eab/packages/frames.js/src/lens/index.ts#L74-L85
Also it is not specified in the type definition https://github.com/framesjs/frames.js/blob/4df7a3ab065c9ae67bb167b052bdc298af7e4eab/packages/frames.js/src/lens/index.ts#L10-L28
I thought that maybe it is just a matter of adding few lines, but then I noticed that @lens-protocol/client doesn't have transactionId specified in FrameEip712Request type. See the screenshot

I tried to upgrade the @lens-protocol/client to 2.3.1 but with no help.
@defispartan:

is transactionId a part of the message?
Is there any type definition in @lens-protocol/client that can be imported instead of LensFrameRequest so we can be sure it comes from source of truth? For example XMTP is exporting the type from validator, see https://github.com/framesjs/frames.js/blob/4df7a3ab065c9ae67bb167b052bdc298af7e4eab/packages/frames.js/src/xmtp/index.ts#L2

There is no mention of transactionId in Lens spec https://lensframes.xyz/#frame-requests but see Open Frames.
Normally it would be just a matter of adding transactionId and use that in the middleware, but @lens-protocol/client doesn't have transactionId property support in createTypedData().

Hey @michalkvasnicak
Yes, you're right. The link I provided is the code @defispartan proposed to showcase the fix. Actually, when using an anonymous client I can fetch the tx hash (but then I'm missing the user's profileId). In the original code, I was using lens:1.0.0 or lens:vNext as a client as you can see here (with opposite result: profileId, but no tx hash)
https://github.com/Quidli/debug-frames-lens/commit/fcb6b158f7a14fd0a9250746d96d5639e6edca76#diff-b85d4cfafcd6e8f7267c4cfe49d28d8667f5965cf337f7d8d867c0404ad6fc25

@lusorio It is unfortunate but the issue is caused by lens not being 100% compatible with Open Frames spec. The difference is in tx button flow, when it is explicitly mentioned that transactionId should be the part of the message payload, but Lens uses actionResponse instead.

This was done with the intention that actionResponse could be a more general field that supports transaction, signature, or relayer (Lens API) responses, but based on this thread, Open Frames plans to use transactionId for signature responses as well, so we're going to update the Lens Frames spec to deprecate actionResponse and exclusively use transactionId.
After this change is made to the Lens spec and API/SDK, I can open a PR here to fix this.

Thank you both, I'll be waiting for it.


[FLINK-30979] Support shuffling data by partition

Currently sink operator in flink will shuffle data by bucket id, which cause data skew when there is only 1 bucket with multiple partitions in the table. This PR aims to support shuffling data by bucket id and partition when sink.shuffle-by-partition.enable is set.
The main changes are

Added config sink.shuffle-by-partition.enable to support shuffling data by partition
Added PartitionComputer to get partition from row data
Added shuffling data by partition in BucketStreamPartitioner

The main tests are

Added FileStoreShuffleBucketTest to shuffle data by bucket and partition

@JingsongLi  DONE

The failed test case is a known problem and I have created an issue https://issues.apache.org/jira/browse/FLINK-31039


https/http Mixed Content Error from Spinnaker UI

When trying to create a new application from the Spinnaker UI, getting the following error in the dev tools console in chrome:
vendor.bundle.js:31822 Mixed Content: The page at 'https://spinnakereruiaddressfromcloudshellpreview' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://localhost:8081/gate/applications'. This request has been blocked; the content must be served over HTTPS.

Fixed with #18


Failing at generate

Environment

Operating System: Darwin
Node Version:     v14.20.1
Nuxt Version:     3.6.5
Nitro Version:    2.5.2
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      devtools, ssr, typescript, css, plugins, modules, pinia, target, build
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
Basic. Project in Nuxt 3, with font awesome, Pinia, Sass, and Vuetify. Attempt to run generate
Describe the bug
Repeatedly getting this error:
[commonjs--resolver] Missing "./dist/pages/runtime" specifier in "nuxt" package
I have cleared npm cache and installed node modules several times, and have the same result after switching from node versions 14, 16, and 18.
Additional context
No response
Logs
No response

Could you kindly provide a reproduction? 🙏

Could you kindly provide a reproduction? 🙏

Yes. Here: https://stackblitz.com/edit/github-vbpafd?file=pages%2Findex.vue

You have a module, Nuxt Axios, which depends on Nuxt 2.


Remove unused Saved_moments directory

Resolves#370
This PR removes references to the Saved_moments directory that was being created but never used.
I'm not sure if there are cases in which this will break the graph scripts – it is reading in data and dumping it into the global namespace and I don't think there is a good way to track down all the side-effects that would have had 🤔
@jdebacker @rickecon

@asmockler Thank you for this PR.  That SS_graphs.py script is a mess.  I think we need to do some improvements on how to handle the plotting of output in general (see issue #92).  But I think this will be best addressed after we make some updates work with the PB API (see PR #354).
Merging.


Why do we use Oauth library?

This is not a bug, its actually a doubt of mine. Why do we use the erlang library oauth  when the ueberauth repo doesn't ask us to add the erlang library in its documentation.

From that repo

This implementation should be compatible with the signature algorithms presented in RFC5849 - The OAuth 1.0 Protocol, and OAuth Core 1.0 Revision A. It is not intended to cover OAuth 2.0.

That means that only Twitter provider will probably use this package.
Also, OAuth should be hidden from you unless you are creating a new provider.

@shijithkjayan maybe because of Twitter strategy 🤔
In any case, please use the Slack channel or Elixir forum for this, you will probably get faster and better responses.


Allow separator to be in the namespace

The following change allows a user to specify a namespace which contains the separator.
Example: namespace: "foo.bar"; separator: "."
What this fixes:

locker.all() now reports the keys in the above use case
locker.clean() removes all the keys

What was changed:

locker.all() now uses indexOf and substring to determine the presence of the namespace

Thanks!


Fix timed method in Delta implementation for axis::Key

Aaaand again. Now the problem has been spotted in gltf example.

Now also includes fix for mouse wheel


Reduce deletion time of task and projects

Before:

After:

Motivation and context

How has this been tested?

Checklist

[x] I submit my changes into the develop branch
[ ] I have added a description of my changes into the CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (see GitHub docs)
- [ ] I have increased versions of npm packages if it is necessary
(cvat-canvas,
cvat-core,
cvat-data and
cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

@azhavoro , could you please look at helm tests?


Adding Container Metrics for gobblin-yarn

YARN containers were not reporting any Task Level Metrics (e.g. records extracted, records written, bytes written, etc.) because Metrics Reporting was not enabled in the containers
Added ContainerMetrics.java to handle metrics reporting for each YARN container
The metrics hierarchy is as follows ContainerMetrics -> JobMetrics -> TaskMetrics
A JobMetrics instance is obtained in each GobblinHelixTask
Unlike MRJobLauncher where the JobMetrics instance is manually removed from the GobblinMetricsRegistry, GobblinHelixTask does not remove the JobMetrics instance at the end of each task because there may be more tasks in the container that need the JobMetrics instance
Reporting is done on the ContainerMetrics instance
Testing is still in progress

@liyinan926 and @ibuenros can you review?

Mostly formatting comments, otherwise LGTM.

Seems the build was hanging.

Yes, it hangs locally too. Looking into it still.

I'm still addressing the comments and fixing the build. However, I tested this on Nertz and it does not seem to be working. No metrics are being emitted and I am not sure why. It only works if I invoke jobMetrics.startMetricsReporting, but not when I do containerMetrics.startMetricsReporting.
@liyinan926, @ibuenros do either of you see anything wrong with this implementation?
My understanding is that since ContainerMetrics is the parent of JobMetrics and, JobMetrics is the parent of TaskMetrics, that if I invoke containerMetrics.startMetricsReporting everything should be reported properly.

@liyinan926 and @ibuenros I found the issue.
It seems that in Typesafe's Config library the .conf files actually allow you to express the config in JSON format (according to the documentation on their Github page it actually uses a JSON superset called HOCON https://github.com/typesafehub/config#using-hocon-the-json-superset).
HOCON provides multiple ways of writing valid JSON (check the documentation link for examples). One such way is using the dot-notation. So a config such as my.test.config=30 will actually be converted to
{
  "my" : {
    "test" : {
      "config" : "30"
    }
  }
}

The reason that this is problematic is that if you have the following two lines in your config file:
metrics.reporting.kafka.topic=MetricReport
metrics.reporting.kafka.topic.events=GobblinTrackingEvent

Then the resulting config is:
{
  "metrics": {
    "reporting": {
      "kafka": {
        "topic": {
          "events": "GobblinTrackingEvent"
        }
      }
    }
  }
}

My understanding is that you the first config sets a node in the JSON tree to MetricReport, but then the second config over-writes that node to {"events" : "GobblinTrackingEvent"}.
This is exactly the bug that I was hitting when testing this on Nertz. No metrics were being reported because the code could not find the name of the Kafka topic to report to. What happens is that GobblinMetrics.startMetricsReporting takes in a Properties object. So we have to use YarnHelixUtils.configToProperties to convert a Config object to a Properties object. The method uses Config.entrySet to get all the configs in the Config object. It seems as though entrySet will only return the leaf values of the JSON tree, so the resulting Properties object has nothing set for metrics.reporting.kafka.topic.
Is this behavior expected? Do we know of a way around this? This seems very different from how gobblin.configuration.State works, so it seems we could easily hit this issue with other config keys?
For now I can unblock this PR, because it seems the gobblin-metrics uses 3 config keys for reporting data to Kafka metrics.reporting.kafka.topic.metrics, metrics.reporting.kafka.topic.events, and metrics.reporting.kafka.topic. The last value is used as the default if either of the other two are not set. So we can still get things to work, but I still think we should discuss this on Monday.

The issue above has been discussed offline.
PR updated to address all comments. Confirmed this is working as expected after testing on Nertz.
@liyinan926, @ibuenros any more comments?

LGTM.


Delete a SPACE line for observing tide's log

Delete a SPACE line for observing tide's log about merge type

/approve

/lgtm


Submit Workflow: Window Navigator

Preflight

[X] The Alfred team has invited me to submit this workflow.

The submitted workflow:

[X] Was authored by me. ⓘ
[X] Uses Workflow Configuration or has no user-facing settings. ⓘ
[X] Does not have an auto-updater. ⓘ
[X] Does not contain unsigned and non-notarised binaries. ⓘ
[X] Does not download extra software. ⓘ
[X] Uses keywords with more than one character. ⓘ
[X] Has a descriptive About section. ⓘ
[X] Has an icon of at least 256x256 px. ⓘ

Homepage
https://github.com/zeitlings/alfred-workflows#120-window-navigator
Alfred Forum page
https://www.alfredforum.com/topic/21898-window-navigator/
Gallery page content
Setup
Optionally, configure the Hotkeys for quick access.
Usage

Search the windows of the active app globally via the Navigator keyword ww
Search app windows in the current desktop space via the Switcher keyword ws
Search all visible windows of all apps globally via the Global keyword wa

↩ Navigate to the selected window.
⌘↩ Close the selected window.
⌥↩ Quit the owning application.

1. Navigator

2. Switcher

3. Global

Tags
window-management
Test data
No response
Homebrew dependencies
No response
Bundled libraries
No response

Thank you. Live at https://alfred.app/workflows/zeitlings/window-navigator/.


SP5 Controls: right-click "Save As" should launch options dialog

Bug Report
Issue: SVG export produces blocky output for SignalPlot over a certain data density.

Reproducing: See code below. Amount of data needed to cause problem is probably proportional to size of the plot.
private double[] RandData(int count) {
    double[] d = new double[count];
    Random r = new Random();
    for (int i = 0; i < count; i++) d[i] = r.NextDouble()*100;
    return d;
}

private void Form1_Load(object sender, EventArgs e) {

    double[] data2 = RandData(800);

    Signal s2 = formsPlot1.Plot.Add.Signal(data2);
    s2.LineStyle.Color = Colors.Blue;
    s2.LineStyle.Width = 1;
    s2.Data.YOffset = 100;
    s2.Marker = MarkerStyle.None;
    s2.Data.YOffset = 150;

}

System Details

ScottPlot Version: 5.0.11-beta
Operating System: Windows 10
Application Type: WinForms
.NET Version: .NET 8.0

Hi @raburton, thanks for reporting this!
Signal plots are fast because they do a trick: they draw a vertical line for each pixel column containing data.

In the case of the SVG output it doesn't look good because it's zoomed in so far. I think the solution here is to export the SVG at high resolution (e.g., 2000x1000) ... but I recognize there's no good way to do that from a FormsPlot via the right-click dialog, so I'll modify this issue to add a feature where users are prompted for the size of the SVG to export. This should fix the issue!

... it should also let the user decide whether or not to have a transparent or solid background color

Hi @raburton, thanks for reporting this!
Signal plots are fast because they do a trick: they draw a vertical line for each pixel column containing data.

I assume this is only the case for dense data? With less data points (600 or lower worked for me with the above example code) I don't get the simplified SVG, all the lines are as you'd expect and I can zoom right in as far as I want on the SVG and they still look good.

In the case of the SVG output it doesn't look good because it's zoomed in so far. I think the solution here is to export the SVG at high resolution (e.g., 2000x1000) ... but I recognize there's no good way to do that from a FormsPlot via the right-click dialog, so I'll modify this issue to add a feature where users are prompted for the size of the SVG to export. This should fix the issue!

I don't think in pixels for vectors graphics, so are you referring to an internal representation of the chart at the size (thus making the data less dense) so it draws properly? If so, whatever size you pick, this problem will still occur for denser data than that size allows for. Perhaps better to just draw the full data to the SVG, instead of using the simplified method for denser data.

Hi @raburton I'm still working on this but one brief note (writing from my phone)
If a signal plot has 1 billion points, a SVG with 1 billion lines will probably crash (and be a massive file size) so some data reduction must be done. Using a rule like "at most one line per pixel" is a reasonable compromise.
Note that scatter plots don't have this issue. If you save your data as a scatter plot the SVG will look good.
Signal plots work by taking "pixel column" shortcuts, so exporting SVGs will always involve some type of data reduction


Can't use stack allocation in an amdgpu_kernel

Whenever an amdgpu_kernel (developed in LLVM IR) makes use of stack allocation, its execution fails with:
:0:rocdevice.cpp            :2303:<PHONE_NUMBER> us: Device::callbackQueue aborting with status: 0x29
A simple kernel that copies an input array of floats to an output array fails whenever it does so storing the float first onto the stack. This stack problem occurs in our application and I was able to boil it down to said simple kernel. I uploaded the minimal exploit onto pastebin (see below).
The workflow is a follows:

module.ll gets compiled to module.o using LLVM clang that comes with ROCm 4.0
module.o gets relinked to a shared object (module.so) using LLD (that also comes with ROCm)
read_launch reads module.so, allocates and initializes arrays of floats.
read_launch launches the kernel when the error occurs on the subsequent memory copy DtoH.

I attach a complete exploit via several pastebins. The GCN architecture is set to 'gfx1010' which you might have to adjust to your setup.
To replicate the issue issue:
make read_launch
make module.o
make module.so
./read_launch
On my system this fails with the above error. The system this was tested on is Ubuntu 20.04 with a Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] on Linux 5.4.0-42-generic
module.ll
Makefile
read_launch.cc
To prove that the whole setup works and the issue is indeed related to the stack allocation in the kernel I attach the simple kernel without any stack usage. Renaming this kernel (module_copy.ll) to module.ll and making the shared object (module.so) lets the program run without errors.
module_copy.ll

Hi @fwinter,
Thank you for bringing the problem to our notice. I would request you to kindly provide the output of following commands in order to understand your system better.

/opt/rocm/bin/rocminfo
/opt/rocm/bin/rocm-bandwidth-test -t

Hi @fwinter,
Thank you for bringing the problem to our notice. I would request you to kindly provide the output of following commands in order to understand your system better.

/opt/rocm/bin/rocminfo
/opt/rocm/bin/rocm-bandwidth-test -t

Thanks for looking into this. I was able to run rocminfo - output is attached below, but rocm-bandwith-test I could not find in my ROCm 4.0 installation on Ubuntu.
I was able to reproduce the same error on a different machine with a gfx908 card. It though seems not to be an issue with my particular gfx1010 system. It seems likely this error can be reproduced with the above details on many gfx cards.
$ rocminfo
ROCk module is loaded
Able to open /dev/kfd read-write
HSA System Attributes
Runtime Version:         1.1
System Timestamp Freq.:  1000.000000MHz
Sig. Max Wait Duration:<PHONE_NUMBER>3709551615 (0xFFFFFFFFFFFFFFFF) (timestamp count)
Machine Model:           LARGE
System Endianness:       LITTLE
==========
HSA Agents

Agent 1

Name:                    Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
Uuid:                    CPU-XX
Marketing Name:          Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
Vendor Name:             CPU
Feature:                 None specified
Profile:                 FULL_PROFILE
Float Round Mode:        NEAR
Max Queue Number:        0(0x0)
Queue Min Size:          0(0x0)
Queue Max Size:          0(0x0)
Queue Type:              MULTI
Node:                    0
Device Type:             CPU
Cache Info:
L1:                      32768(0x8000) KB
Chip ID:                 0(0x0)
Cacheline Size:          64(0x40)
Max Clock Freq. (MHz):   4600
BDFID:                   0
Internal Node ID:        0
Compute Unit:            12
SIMDs per CU:            0
Shader Engines:          0
Shader Arrs. per Eng.:   0
WatchPts on Addr. Ranges:1
Features:                None
Pool Info:
Pool 1
Segment:                 GLOBAL; FLAGS: KERNARG, FINE GRAINED
Size:                    16259348(0xf81914) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       TRUE
Pool 2
Segment:                 GLOBAL; FLAGS: COARSE GRAINED
Size:                    16259348(0xf81914) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       TRUE
ISA Info:
N/A

Agent 2

Name:                    gfx1010
Uuid:                    GPU-XX
Marketing Name:          Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
Vendor Name:             AMD
Feature:                 KERNEL_DISPATCH
Profile:                 BASE_PROFILE
Float Round Mode:        NEAR
Max Queue Number:        128(0x80)
Queue Min Size:          4096(0x1000)
Queue Max Size:          131072(0x20000)
Queue Type:              MULTI
Node:                    1
Device Type:             GPU
Cache Info:
L1:                      16(0x10) KB
Chip ID:                 29471(0x731f)
Cacheline Size:          64(0x40)
Max Clock Freq. (MHz):   2100
BDFID:                   768
Internal Node ID:        1
Compute Unit:            40
SIMDs per CU:            4
Shader Engines:          4
Shader Arrs. per Eng.:   2
WatchPts on Addr. Ranges:4
Features:                KERNEL_DISPATCH
Fast F16 Operation:      FALSE
Wavefront Size:          32(0x20)
Workgroup Max Size:      1024(0x400)
Workgroup Max Size per Dimension:
x                        1024(0x400)
y                        1024(0x400)
z                        1024(0x400)
Max Waves Per CU:        80(0x50)
Max Work-item Per CU:    2560(0xa00)
Grid Max Size:<PHONE_NUMBER>(0xffffffff)
Grid Max Size per Dimension:
x<PHONE_NUMBER>(0xffffffff)
y<PHONE_NUMBER>(0xffffffff)
z<PHONE_NUMBER>(0xffffffff)
Max fbarriers/Workgrp:   32
Pool Info:
Pool 1
Segment:                 GLOBAL; FLAGS: COARSE GRAINED
Size:                    8372224(0x7fc000) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       FALSE
Pool 2
Segment:                 GROUP
Size:                    64(0x40) KB
Allocatable:             FALSE
Alloc Granule:           0KB
Alloc Alignment:         0KB
Accessible by all:       FALSE
ISA Info:
ISA 1
Name:                    amdgcn-amd-amdhsa--gfx1010
Machine Models:          HSA_MACHINE_MODEL_LARGE
Profiles:                HSA_PROFILE_BASE
Default Rounding Mode:   NEAR
Default Rounding Mode:   NEAR
Fast f16:                TRUE
Workgroup Max Size:      1024(0x400)
Workgroup Max Size per Dimension:
x                        1024(0x400)
y                        1024(0x400)
z                        1024(0x400)
Grid Max Size:<PHONE_NUMBER>(0xffffffff)
Grid Max Size per Dimension:
x<PHONE_NUMBER>(0xffffffff)
y<PHONE_NUMBER>(0xffffffff)
z<PHONE_NUMBER>(0xffffffff)
FBarrier Max Size:       32
*** Done ***

Thanks for looking into this. I was able to run rocminfo - output is attached below, but rocm-bandwith-test I could not find in my ROCm 4.0 installation on Ubuntu.
I was able to reproduce the same error on a different machine with a gfx908 card. It though seems not to be an issue with my particular gfx1010 system. It seems likely this error can be reproduced with the above details on many gfx cards.
$ rocminfo
ROCk module is loaded
Able to open /dev/kfd read-write
HSA System Attributes
Runtime Version:         1.1
System Timestamp Freq.:  1000.000000MHz
Sig. Max Wait Duration:<PHONE_NUMBER>3709551615 (0xFFFFFFFFFFFFFFFF) (timestamp count)
Machine Model:           LARGE
System Endianness:       LITTLE
==========
HSA Agents

Agent 1

Name:                    Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
Uuid:                    CPU-XX
Marketing Name:          Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
Vendor Name:             CPU
Feature:                 None specified
Profile:                 FULL_PROFILE
Float Round Mode:        NEAR
Max Queue Number:        0(0x0)
Queue Min Size:          0(0x0)
Queue Max Size:          0(0x0)
Queue Type:              MULTI
Node:                    0
Device Type:             CPU
Cache Info:
L1:                      32768(0x8000) KB
Chip ID:                 0(0x0)
Cacheline Size:          64(0x40)
Max Clock Freq. (MHz):   4600
BDFID:                   0
Internal Node ID:        0
Compute Unit:            12
SIMDs per CU:            0
Shader Engines:          0
Shader Arrs. per Eng.:   0
WatchPts on Addr. Ranges:1
Features:                None
Pool Info:
Pool 1
Segment:                 GLOBAL; FLAGS: KERNARG, FINE GRAINED
Size:                    16259348(0xf81914) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       TRUE
Pool 2
Segment:                 GLOBAL; FLAGS: COARSE GRAINED
Size:                    16259348(0xf81914) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       TRUE
ISA Info:
N/A

Agent 2

Name:                    gfx1010
Uuid:                    GPU-XX
Marketing Name:          Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
Vendor Name:             AMD
Feature:                 KERNEL_DISPATCH
Profile:                 BASE_PROFILE
Float Round Mode:        NEAR
Max Queue Number:        128(0x80)
Queue Min Size:          4096(0x1000)
Queue Max Size:          131072(0x20000)
Queue Type:              MULTI
Node:                    1
Device Type:             GPU
Cache Info:
L1:                      16(0x10) KB
Chip ID:                 29471(0x731f)
Cacheline Size:          64(0x40)
Max Clock Freq. (MHz):   2100
BDFID:                   768
Internal Node ID:        1
Compute Unit:            40
SIMDs per CU:            4
Shader Engines:          4
Shader Arrs. per Eng.:   2
WatchPts on Addr. Ranges:4
Features:                KERNEL_DISPATCH
Fast F16 Operation:      FALSE
Wavefront Size:          32(0x20)
Workgroup Max Size:      1024(0x400)
Workgroup Max Size per Dimension:
x                        1024(0x400)
y                        1024(0x400)
z                        1024(0x400)
Max Waves Per CU:        80(0x50)
Max Work-item Per CU:    2560(0xa00)
Grid Max Size:<PHONE_NUMBER>(0xffffffff)
Grid Max Size per Dimension:
x<PHONE_NUMBER>(0xffffffff)
y<PHONE_NUMBER>(0xffffffff)
z<PHONE_NUMBER>(0xffffffff)
Max fbarriers/Workgrp:   32
Pool Info:
Pool 1
Segment:                 GLOBAL; FLAGS: COARSE GRAINED
Size:                    8372224(0x7fc000) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       FALSE
Pool 2
Segment:                 GROUP
Size:                    64(0x40) KB
Allocatable:             FALSE
Alloc Granule:           0KB
Alloc Alignment:         0KB
Accessible by all:       FALSE
ISA Info:
ISA 1
Name:                    amdgcn-amd-amdhsa--gfx1010
Machine Models:          HSA_MACHINE_MODEL_LARGE
Profiles:                HSA_PROFILE_BASE
Default Rounding Mode:   NEAR
Default Rounding Mode:   NEAR
Fast f16:                TRUE
Workgroup Max Size:      1024(0x400)
Workgroup Max Size per Dimension:
x                        1024(0x400)
y                        1024(0x400)
z                        1024(0x400)
Grid Max Size:<PHONE_NUMBER>(0xffffffff)
Grid Max Size per Dimension:
x<PHONE_NUMBER>(0xffffffff)
y<PHONE_NUMBER>(0xffffffff)
z<PHONE_NUMBER>(0xffffffff)
FBarrier Max Size:       32
*** Done ***

@fwinter , Thank you for the output.
you can always install rocm-bandwidth-test  using : sudo apt-get install rocm-bandwidth-test
As you must be aware currently we are not supporting gfx1010.
Since you check, gfx908 card as well, I would request you to kindly furnish the "rocminfo" & "rocm-bandwidth-test" output on your gfx908 system.

@fwinter , Thank you for the output.
you can always install rocm-bandwidth-test  using : sudo apt-get install rocm-bandwidth-test
As you must be aware currently we are not supporting gfx1010.
Since you check, gfx908 card as well, I would request you to kindly furnish the "rocminfo" & "rocm-bandwidth-test" output on your gfx908 system.

Thanks for letting me know gfx1010 is not supported. I'm happy to switch over to the gfx908 system. Here's the requested output on the gfx908 compute node. First that of 'rocminfo' followed by the output of 'rocm-bandwidth-test -t'.
$ rocminfo
ROCk module is loaded
Able to open /dev/kfd read-write
HSA System Attributes
Runtime Version:         1.1
System Timestamp Freq.:  1000.000000MHz
Sig. Max Wait Duration:<PHONE_NUMBER>3709551615 (0xFFFFFFFFFFFFFFFF) (timestamp count)
Machine Model:           LARGE
System Endianness:       LITTLE
==========
HSA Agents

Agent 1

Name:                    AMD EPYC 7742 64-Core Processor
Uuid:                    CPU-XX
Marketing Name:          AMD EPYC 7742 64-Core Processor
Vendor Name:             CPU
Feature:                 None specified
Profile:                 FULL_PROFILE
Float Round Mode:        NEAR
Max Queue Number:        0(0x0)
Queue Min Size:          0(0x0)
Queue Max Size:          0(0x0)
Queue Type:              MULTI
Node:                    0
Device Type:             CPU
Cache Info:
L1:                      32768(0x8000) KB
Chip ID:                 0(0x0)
Cacheline Size:          64(0x40)
Max Clock Freq. (MHz):   2250
BDFID:                   0
Internal Node ID:        0
Compute Unit:            128
SIMDs per CU:            0
Shader Engines:          0
Shader Arrs. per Eng.:   0
WatchPts on Addr. Ranges:1
Features:                None
Pool Info:
Pool 1
Segment:                 GLOBAL; FLAGS: KERNARG, FINE GRAINED
Size:                    131062320(0x7cfda30) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       TRUE
Pool 2
Segment:                 GLOBAL; FLAGS: COARSE GRAINED
Size:                    131062320(0x7cfda30) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       TRUE
ISA Info:
N/A

Agent 2

Name:                    AMD EPYC 7742 64-Core Processor
Uuid:                    CPU-XX
Marketing Name:          AMD EPYC 7742 64-Core Processor
Vendor Name:             CPU
Feature:                 None specified
Profile:                 FULL_PROFILE
Float Round Mode:        NEAR
Max Queue Number:        0(0x0)
Queue Min Size:          0(0x0)
Queue Max Size:          0(0x0)
Queue Type:              MULTI
Node:                    1
Device Type:             CPU
Cache Info:
L1:                      32768(0x8000) KB
Chip ID:                 0(0x0)
Cacheline Size:          64(0x40)
Max Clock Freq. (MHz):   2250
BDFID:                   0
Internal Node ID:        1
Compute Unit:            128
SIMDs per CU:            0
Shader Engines:          0
Shader Arrs. per Eng.:   0
WatchPts on Addr. Ranges:1
Features:                None
Pool Info:
Pool 1
Segment:                 GLOBAL; FLAGS: KERNARG, FINE GRAINED
Size:                    132086292(0x7df7a14) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       TRUE
Pool 2
Segment:                 GLOBAL; FLAGS: COARSE GRAINED
Size:                    132086292(0x7df7a14) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       TRUE
ISA Info:
N/A

Agent 3

Name:                    gfx908
Uuid:                    GPU-XX
Marketing Name:          Device 738c
Vendor Name:             AMD
Feature:                 KERNEL_DISPATCH
Profile:                 BASE_PROFILE
Float Round Mode:        NEAR
Max Queue Number:        128(0x80)
Queue Min Size:          4096(0x1000)
Queue Max Size:          131072(0x20000)
Queue Type:              MULTI
Node:                    2
Device Type:             GPU
Cache Info:
L1:                      16(0x10) KB
Chip ID:                 29580(0x738c)
Cacheline Size:          64(0x40)
Max Clock Freq. (MHz):   1502
BDFID:                   49920
Internal Node ID:        2
Compute Unit:            120
SIMDs per CU:            4
Shader Engines:          8
Shader Arrs. per Eng.:   1
WatchPts on Addr. Ranges:4
Features:                KERNEL_DISPATCH
Fast F16 Operation:      FALSE
Wavefront Size:          64(0x40)
Workgroup Max Size:      1024(0x400)
Workgroup Max Size per Dimension:
x                        1024(0x400)
y                        1024(0x400)
z                        1024(0x400)
Max Waves Per CU:        40(0x28)
Max Work-item Per CU:    2560(0xa00)
Grid Max Size:<PHONE_NUMBER>(0xffffffff)
Grid Max Size per Dimension:
x<PHONE_NUMBER>(0xffffffff)
y<PHONE_NUMBER>(0xffffffff)
z<PHONE_NUMBER>(0xffffffff)
Max fbarriers/Workgrp:   32
Pool Info:
Pool 1
Segment:                 GLOBAL; FLAGS: COARSE GRAINED
Size:                    33538048(0x1ffc000) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       FALSE
Pool 2
Segment:                 GLOBAL; FLAGS: FINE GRAINED
Size:                    33538048(0x1ffc000) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       FALSE
Pool 3
Segment:                 GROUP
Size:                    64(0x40) KB
Allocatable:             FALSE
Alloc Granule:           0KB
Alloc Alignment:         0KB
Accessible by all:       FALSE
ISA Info:
ISA 1
Name:                    amdgcn-amd-amdhsa--gfx908
Machine Models:          HSA_MACHINE_MODEL_LARGE
Profiles:                HSA_PROFILE_BASE
Default Rounding Mode:   NEAR
Default Rounding Mode:   NEAR
Fast f16:                TRUE
Workgroup Max Size:      1024(0x400)
Workgroup Max Size per Dimension:
x                        1024(0x400)
y                        1024(0x400)
z                        1024(0x400)
Grid Max Size:<PHONE_NUMBER>(0xffffffff)
Grid Max Size per Dimension:
x<PHONE_NUMBER>(0xffffffff)
y<PHONE_NUMBER>(0xffffffff)
z<PHONE_NUMBER>(0xffffffff)
FBarrier Max Size:       32

Agent 4

Name:                    gfx908
Uuid:                    GPU-XX
Marketing Name:          Device 738c
Vendor Name:             AMD
Feature:                 KERNEL_DISPATCH
Profile:                 BASE_PROFILE
Float Round Mode:        NEAR
Max Queue Number:        128(0x80)
Queue Min Size:          4096(0x1000)
Queue Max Size:          131072(0x20000)
Queue Type:              MULTI
Node:                    3
Device Type:             GPU
Cache Info:
L1:                      16(0x10) KB
Chip ID:                 29580(0x738c)
Cacheline Size:          64(0x40)
Max Clock Freq. (MHz):   1502
BDFID:                   50688
Internal Node ID:        3
Compute Unit:            120
SIMDs per CU:            4
Shader Engines:          8
Shader Arrs. per Eng.:   1
WatchPts on Addr. Ranges:4
Features:                KERNEL_DISPATCH
Fast F16 Operation:      FALSE
Wavefront Size:          64(0x40)
Workgroup Max Size:      1024(0x400)
Workgroup Max Size per Dimension:
x                        1024(0x400)
y                        1024(0x400)
z                        1024(0x400)
Max Waves Per CU:        40(0x28)
Max Work-item Per CU:    2560(0xa00)
Grid Max Size:<PHONE_NUMBER>(0xffffffff)
Grid Max Size per Dimension:
x<PHONE_NUMBER>(0xffffffff)
y<PHONE_NUMBER>(0xffffffff)
z<PHONE_NUMBER>(0xffffffff)
Max fbarriers/Workgrp:   32
Pool Info:
Pool 1
Segment:                 GLOBAL; FLAGS: COARSE GRAINED
Size:                    33538048(0x1ffc000) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       FALSE
Pool 2
Segment:                 GLOBAL; FLAGS: FINE GRAINED
Size:                    33538048(0x1ffc000) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       FALSE
Pool 3
Segment:                 GROUP
Size:                    64(0x40) KB
Allocatable:             FALSE
Alloc Granule:           0KB
Alloc Alignment:         0KB
Accessible by all:       FALSE
ISA Info:
ISA 1
Name:                    amdgcn-amd-amdhsa--gfx908
Machine Models:          HSA_MACHINE_MODEL_LARGE
Profiles:                HSA_PROFILE_BASE
Default Rounding Mode:   NEAR
Default Rounding Mode:   NEAR
Fast f16:                TRUE
Workgroup Max Size:      1024(0x400)
Workgroup Max Size per Dimension:
x                        1024(0x400)
y                        1024(0x400)
z                        1024(0x400)
Grid Max Size:<PHONE_NUMBER>(0xffffffff)
Grid Max Size per Dimension:
x<PHONE_NUMBER>(0xffffffff)
y<PHONE_NUMBER>(0xffffffff)
z<PHONE_NUMBER>(0xffffffff)
FBarrier Max Size:       32

Agent 5

Name:                    gfx908
Uuid:                    GPU-XX
Marketing Name:          Device 738c
Vendor Name:             AMD
Feature:                 KERNEL_DISPATCH
Profile:                 BASE_PROFILE
Float Round Mode:        NEAR
Max Queue Number:        128(0x80)
Queue Min Size:          4096(0x1000)
Queue Max Size:          131072(0x20000)
Queue Type:              MULTI
Node:                    4
Device Type:             GPU
Cache Info:
L1:                      16(0x10) KB
Chip ID:                 29580(0x738c)
Cacheline Size:          64(0x40)
Max Clock Freq. (MHz):   1502
BDFID:                   41728
Internal Node ID:        4
Compute Unit:            120
SIMDs per CU:            4
Shader Engines:          8
Shader Arrs. per Eng.:   1
WatchPts on Addr. Ranges:4
Features:                KERNEL_DISPATCH
Fast F16 Operation:      FALSE
Wavefront Size:          64(0x40)
Workgroup Max Size:      1024(0x400)
Workgroup Max Size per Dimension:
x                        1024(0x400)
y                        1024(0x400)
z                        1024(0x400)
Max Waves Per CU:        40(0x28)
Max Work-item Per CU:    2560(0xa00)
Grid Max Size:<PHONE_NUMBER>(0xffffffff)
Grid Max Size per Dimension:
x<PHONE_NUMBER>(0xffffffff)
y<PHONE_NUMBER>(0xffffffff)
z<PHONE_NUMBER>(0xffffffff)
Max fbarriers/Workgrp:   32
Pool Info:
Pool 1
Segment:                 GLOBAL; FLAGS: COARSE GRAINED
Size:                    33538048(0x1ffc000) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       FALSE
Pool 2
Segment:                 GLOBAL; FLAGS: FINE GRAINED
Size:                    33538048(0x1ffc000) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       FALSE
Pool 3
Segment:                 GROUP
Size:                    64(0x40) KB
Allocatable:             FALSE
Alloc Granule:           0KB
Alloc Alignment:         0KB
Accessible by all:       FALSE
ISA Info:
ISA 1
Name:                    amdgcn-amd-amdhsa--gfx908
Machine Models:          HSA_MACHINE_MODEL_LARGE
Profiles:                HSA_PROFILE_BASE
Default Rounding Mode:   NEAR
Default Rounding Mode:   NEAR
Fast f16:                TRUE
Workgroup Max Size:      1024(0x400)
Workgroup Max Size per Dimension:
x                        1024(0x400)
y                        1024(0x400)
z                        1024(0x400)
Grid Max Size:<PHONE_NUMBER>(0xffffffff)
Grid Max Size per Dimension:
x<PHONE_NUMBER>(0xffffffff)
y<PHONE_NUMBER>(0xffffffff)
z<PHONE_NUMBER>(0xffffffff)
FBarrier Max Size:       32

Agent 6

Name:                    gfx908
Uuid:                    GPU-XX
Marketing Name:          Device 738c
Vendor Name:             AMD
Feature:                 KERNEL_DISPATCH
Profile:                 BASE_PROFILE
Float Round Mode:        NEAR
Max Queue Number:        128(0x80)
Queue Min Size:          4096(0x1000)
Queue Max Size:          131072(0x20000)
Queue Type:              MULTI
Node:                    5
Device Type:             GPU
Cache Info:
L1:                      16(0x10) KB
Chip ID:                 29580(0x738c)
Cacheline Size:          64(0x40)
Max Clock Freq. (MHz):   1502
BDFID:                   33536
Internal Node ID:        5
Compute Unit:            120
SIMDs per CU:            4
Shader Engines:          8
Shader Arrs. per Eng.:   1
WatchPts on Addr.  I'm happy to switch over to the gfx908 system. Here's the requested output on the gfx908 compute node. First that of 'rocminfo' followed by the output of 'rocm-bandwidth-test -t'.
$ rocminfo
ROCk module is loaded
Able to open /dev/kfd read-write
HSA System Attributes
Runtime Version:         1.1
System Timestamp Freq.:  1000.000000MHz
Sig. Max Wait Duration:<PHONE_NUMBER>3709551615 (0xFFFFFFFFFFFFFFFF) (timestamp count)
Machine Model:           LARGE
System Endianness:       LITTLE
==========
HSA Agents

Agent 1

Name:                    AMD EPYC 7742 64-Core Processor
Uuid:                    CPU-XX
Marketing Name:          AMD EPYC 7742 64-Core Processor
Vendor Name:             CPU
Feature:                 None specified
Profile:                 FULL_PROFILE
Float Round Mode:        NEAR
Max Queue Number:        0(0x0)
Queue Min Size:          0(0x0)
Queue Max Size:          0(0x0)
Queue Type:              MULTI
Node:                    0
Device Type:             CPU
Cache Info:
L1:                      32768(0x8000) KB
Chip ID:                 0(0x0)
Cacheline Size:          64(0x40)
Max Clock Freq. (MHz):   2250
BDFID:                   0
Internal Node ID:        0
Compute Unit:            128
SIMDs per CU:            0
Shader Engines:          0
Shader Arrs. per Eng.:   0
WatchPts on Addr. Ranges:1
Features:                None
Pool Info:
Pool 1
Segment:                 GLOBAL; FLAGS: KERNARG, FINE GRAINED
Size:                    131062320(0x7cfda30) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       TRUE
Pool 2
Segment:                 GLOBAL; FLAGS: COARSE GRAINED
Size:                    131062320(0x7cfda30) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       TRUE
ISA Info:
N/A

Agent 2

Name:                    AMD EPYC 7742 64-Core Processor
Uuid:                    CPU-XX
Marketing Name:          AMD EPYC 7742 64-Core Processor
Vendor Name:             CPU
Feature:                 None specified
Profile:                 FULL_PROFILE
Float Round Mode:        NEAR
Max Queue Number:        0(0x0)
Queue Min Size:          0(0x0)
Queue Max Size:          0(0x0)
Queue Type:              MULTI
Node:                    1
Device Type:             CPU
Cache Info:
L1:                      32768(0x8000) KB
Chip ID:                 0(0x0)
Cacheline Size:          64(0x40)
Max Clock Freq. (MHz):   2250
BDFID:                   0
Internal Node ID:        1
Compute Unit:            128
SIMDs per CU:            0
Shader Engines:          0
Shader Arrs. per Eng.:   0
WatchPts on Addr. Ranges:1
Features:                None
Pool Info:
Pool 1
Segment:                 GLOBAL; FLAGS: KERNARG, FINE GRAINED
Size:                    132086292(0x7df7a14) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       TRUE
Pool 2
Segment:                 GLOBAL; FLAGS: COARSE GRAINED
Size:                    132086292(0x7df7a14) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       TRUE
ISA Info:
N/A

Agent 3

Name:                    gfx908
Uuid:                    GPU-XX
Marketing Name:          Device 738c
Vendor Name:             AMD
Feature:                 KERNEL_DISPATCH
Profile:                 BASE_PROFILE
Float Round Mode:        NEAR
Max Queue Number:        128(0x80)
Queue Min Size:          4096(0x1000)
Queue Max Size:          131072(0x20000)
Queue Type:              MULTI
Node:                    2
Device Type:             GPU
Cache Info:
L1:                      16(0x10) KB
Chip ID:                 29580(0x738c)
Cacheline Size:          64(0x40)
Max Clock Freq. (MHz):   1502
BDFID:                   49920
Internal Node ID:        2
Compute Unit:            120
SIMDs per CU:            4
Shader Engines:          8
Shader Arrs. per Eng.:   1
WatchPts on Addr. Ranges:4
Features:                KERNEL_DISPATCH
Fast F16 Operation:      FALSE
Wavefront Size:          64(0x40)
Workgroup Max Size:      1024(0x400)
Workgroup Max Size per Dimension:
x                        1024(0x400)
y                        1024(0x400)
z                        1024(0x400)
Max Waves Per CU:        40(0x28)
Max Work-item Per CU:    2560(0xa00)
Grid Max Size:<PHONE_NUMBER>(0xffffffff)
Grid Max Size per Dimension:
x<PHONE_NUMBER>(0xffffffff)
y<PHONE_NUMBER>(0xffffffff)
z<PHONE_NUMBER>(0xffffffff)
Max fbarriers/Workgrp:   32
Pool Info:
Pool 1
Segment:                 GLOBAL; FLAGS: COARSE GRAINED
Size:                    33538048(0x1ffc000) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       FALSE
Pool 2
Segment:                 GLOBAL; FLAGS: FINE GRAINED
Size:                    33538048(0x1ffc000) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       FALSE
Pool 3
Segment:                 GROUP
Size:                    64(0x40) KB
Allocatable:             FALSE
Alloc Granule:           0KB
Alloc Alignment:         0KB
Accessible by all:       FALSE
ISA Info:
ISA 1
Name:                    amdgcn-amd-amdhsa--gfx908
Machine Models:          HSA_MACHINE_MODEL_LARGE
Profiles:                HSA_PROFILE_BASE
Default Rounding Mode:   NEAR
Default Rounding Mode:   NEAR
Fast f16:                TRUE
Workgroup Max Size:      1024(0x400)
Workgroup Max Size per Dimension:
x                        1024(0x400)
y                        1024(0x400)
z                        1024(0x400)
Grid Max Size:<PHONE_NUMBER>(0xffffffff)
Grid Max Size per Dimension:
x<PHONE_NUMBER>(0xffffffff)
y<PHONE_NUMBER>(0xffffffff)
z<PHONE_NUMBER>(0xffffffff)
FBarrier Max Size:       32

Agent 4

Name:                    gfx908
Uuid:                    GPU-XX
Marketing Name:          Device 738c
Vendor Name:             AMD
Feature:                 KERNEL_DISPATCH
Profile:                 BASE_PROFILE
Float Round Mode:        NEAR
Max Queue Number:        128(0x80)
Queue Min Size:          4096(0x1000)
Queue Max Size:          131072(0x20000)
Queue Type:              MULTI
Node:                    3
Device Type:             GPU
Cache Info:
L1:                      16(0x10) KB
Chip ID:                 29580(0x738c)
Cacheline Size:          64(0x40)
Max Clock Freq. (MHz):   1502
BDFID:                   50688
Internal Node ID:        3
Compute Unit:            120
SIMDs per CU:            4
Shader Engines:          8
Shader Arrs. per Eng.:   1
WatchPts on Addr. Ranges:4
Features:                KERNEL_DISPATCH
Fast F16 Operation:      FALSE
Wavefront Size:          64(0x40)
Workgroup Max Size:      1024(0x400)
Workgroup Max Size per Dimension:
x                        1024(0x400)
y                        1024(0x400)
z                        1024(0x400)
Max Waves Per CU:        40(0x28)
Max Work-item Per CU:    2560(0xa00)
Grid Max Size:<PHONE_NUMBER>(0xffffffff)
Grid Max Size per Dimension:
x<PHONE_NUMBER>(0xffffffff)
y<PHONE_NUMBER>(0xffffffff)
z<PHONE_NUMBER>(0xffffffff)
Max fbarriers/Workgrp:   32
Pool Info:
Pool 1
Segment:                 GLOBAL; FLAGS: COARSE GRAINED
Size:                    33538048(0x1ffc000) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       FALSE
Pool 2
Segment:                 GLOBAL; FLAGS: FINE GRAINED
Size:                    33538048(0x1ffc000) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       FALSE
Pool 3
Segment:                 GROUP
Size:                    64(0x40) KB
Allocatable:             FALSE
Alloc Granule:           0KB
Alloc Alignment:         0KB
Accessible by all:       FALSE
ISA Info:
ISA 1
Name:                    amdgcn-amd-amdhsa--gfx908
Machine Models:          HSA_MACHINE_MODEL_LARGE
Profiles:                HSA_PROFILE_BASE
Default Rounding Mode:   NEAR
Default Rounding Mode:   NEAR
Fast f16:                TRUE
Workgroup Max Size:      1024(0x400)
Workgroup Max Size per Dimension:
x                        1024(0x400)
y                        1024(0x400)
z                        1024(0x400)
Grid Max Size:<PHONE_NUMBER>(0xffffffff)
Grid Max Size per Dimension:
x<PHONE_NUMBER>(0xffffffff)
y<PHONE_NUMBER>(0xffffffff)
z<PHONE_NUMBER>(0xffffffff)
FBarrier Max Size:       32

Agent 5

Name:                    gfx908
Uuid:                    GPU-XX
Marketing Name:          Device 738c
Vendor Name:             AMD
Feature:                 KERNEL_DISPATCH
Profile:                 BASE_PROFILE
Float Round Mode:        NEAR
Max Queue Number:        128(0x80)
Queue Min Size:          4096(0x1000)
Queue Max Size:          131072(0x20000)
Queue Type:              MULTI
Node:                    4
Device Type:             GPU
Cache Info:
L1:                      16(0x10) KB
Chip ID:                 29580(0x738c)
Cacheline Size:          64(0x40)
Max Clock Freq. (MHz):   1502
BDFID:                   41728
Internal Node ID:        4
Compute Unit:            120
SIMDs per CU:            4
Shader Engines:          8
Shader Arrs. per Eng.:   1
WatchPts on Addr. Ranges:4
Features:                KERNEL_DISPATCH
Fast F16 Operation:      FALSE
Wavefront Size:          64(0x40)
Workgroup Max Size:      1024(0x400)
Workgroup Max Size per Dimension:
x                        1024(0x400)
y                        1024(0x400)
z                        1024(0x400)
Max Waves Per CU:        40(0x28)
Max Work-item Per CU:    2560(0xa00)
Grid Max Size:<PHONE_NUMBER>(0xffffffff)
Grid Max Size per Dimension:
x<PHONE_NUMBER>(0xffffffff)
y<PHONE_NUMBER>(0xffffffff)
z<PHONE_NUMBER>(0xffffffff)
Max fbarriers/Workgrp:   32
Pool Info:
Pool 1
Segment:                 GLOBAL; FLAGS: COARSE GRAINED
Size:                    33538048(0x1ffc000) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       FALSE
Pool 2
Segment:                 GLOBAL; FLAGS: FINE GRAINED
Size:                    33538048(0x1ffc000) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       FALSE
Pool 3
Segment:                 GROUP
Size:                    64(0x40) KB
Allocatable:             FALSE
Alloc Granule:           0KB
Alloc Alignment:         0KB
Accessible by all:       FALSE
ISA Info:
ISA 1
Name:                    amdgcn-amd-amdhsa--gfx908
Machine Models:          HSA_MACHINE_MODEL_LARGE
Profiles:                HSA_PROFILE_BASE
Default Rounding Mode:   NEAR
Default Rounding Mode:   NEAR
Fast f16:                TRUE
Workgroup Max Size:      1024(0x400)
Workgroup Max Size per Dimension:
x                        1024(0x400)
y                        1024(0x400)
z                        1024(0x400)
Grid Max Size:<PHONE_NUMBER>(0xffffffff)
Grid Max Size per Dimension:
x<PHONE_NUMBER>(0xffffffff)
y<PHONE_NUMBER>(0xffffffff)
z<PHONE_NUMBER>(0xffffffff)
FBarrier Max Size:       32

Agent 6

Name:                    gfx908
Uuid:                    GPU-XX
Marketing Name:          Device 738c
Vendor Name:             AMD
Feature:                 KERNEL_DISPATCH
Profile:                 BASE_PROFILE
Float Round Mode:        NEAR
Max Queue Number:        128(0x80)
Queue Min Size:          4096(0x1000)
Queue Max Size:          131072(0x20000)
Queue Type:              MULTI
Node:                    5
Device Type:             GPU
Cache Info:
L1:                      16(0x10) KB
Chip ID:                 29580(0x738c)
Cacheline Size:          64(0x40)
Max Clock Freq. (MHz):   1502
BDFID:                   33536
Internal Node ID:        5
Compute Unit:            120
SIMDs per CU:            4
Shader Engines:          8
Shader Arrs. per Eng.:   1
WatchPts on Addr.   The other day, I tried to reproduce your problem on gfx900 ( I had to modify your makefile a bit to take the auto configuration of your card ) but, it did not compile & always gave error : clang-12: note: diagnostic msg: Error generating preprocessed source(s) - no preprocessable inputs.   I am not sure why this problem is coming.
Here are the complete logs :
Fourom1366.txt

Hi @fwinter ,
Since you closed this, We presume that for gfx908 this is working as per the expectations.  The other day, I tried to reproduce your problem on gfx900 ( I had to modify your makefile a bit to take the auto configuration of your card ) but, it did not compile & always gave error : clang-12: note: diagnostic msg: Error generating preprocessed source(s) - no preprocessable inputs.   I am not sure why this problem is coming.
Here are the complete logs :
Fourom1366.txt

Yes, the problem was the alloca instruction not using the correct address space.
Your compiler output tells it:
Allocation instruction pointer not in the stack address space!
%4 = alloca float, align 4
So, all good. No bug. Issue closed.
Thanks!

Yes, the problem was the alloca instruction not using the correct address space.
Your compiler output tells it:
Allocation instruction pointer not in the stack address space!
%4 = alloca float, align 4
So, all good. No bug. Issue closed.
Thanks!


Docs: Build with Sphinx --pre release

If a Requirement specifier includes a pre-release or development
version (e.g. >=0.0.dev0) then pip will allow pre-release and development
versions for that requirement. This does not include the != flag.

From https://pip.pypa.io/en/latest/cli/pip_install/#pre-release-versions

Do not merge this PR, it's just a test to build the theme with Sphinx --pre release

Edit: I did this as an example for https://github.com/sphinx-doc/sphinx/issues/9088#issuecomment-819375712

I guess this should be used with https://github.com/readthedocs/sphinx_rtd_theme/pull/1123?

@Blendify I added this as an example of https://github.com/sphinx-doc/sphinx/issues/9088#issuecomment-819375712
I don't think we want to add this to master for building our docs. However, it may be a good idea to add it to the Sphinx versions that are used to test our theme so we can find issues on our theme before the release is done.

@ericholscher One failure that I found is that this page breaks: https://sphinx-rtd-theme--1130.org.readthedocs.build/en/1130/demo/demo.html. The table of content does not render properly.
See the original: https://sphinx-rtd-theme.readthedocs.io/en/stable/demo/demo.html
It seems the CSS selector is too specific based on .section class that it was replaced by a <section> html tag in docutils==0.17

Can this be closed now?

Yes. Let's close it. It was a test for the pre-release of Sphinx.
However, we should probably create an automated way of building our theme with the latest pre-release of Sphinx to detect breaking changes earlier.


Restore (and possibly other) operations are not handling errors correctly

A customer reported an issue through CSS about restore operations not always failing correctly. No error HTTP status was reported, but a status monitor still returned an error. According to guidelines, this is expected.
The crux of the issue is here:
https://github.com/Azure/azure-sdk-for-net/blob/5f860d9662b99e60f1bfb500f6a6d19910d4ae58/sdk/keyvault/Azure.Security.KeyVault.Administration/src/RestoreOperationInternal.cs#L218-L222
We likely did not populate Error.Code or maybe not even Error, so we didn't create and/or throw a proper RequestFailedException.

Note that guidelines say we should throw a RequestFailedException: https://azure.github.io/azure-sdk/dotnet_implementation.html#dotnet-lro-return


Add a Unix socket version of the default (UDP) client.

howdy! I've reopened https://github.com/jsocol/pystatsd/issues/127 and included this PR as a reference implementation.
Turns out, while the unix socket stream client is great if your statsd server is listening on TCP, but unfortunately it doesn't work for the AF_UNIX + UDP use case.
This PR just adds an additional client to the statsd.client.udp namespace that satisfies the missing use case. I borrowed the same name as the stream client, but I could see that being confusing. Open to suggestion!
edit; I also haven't written tests yet, as I think the naming of the class should probably be nailed down first. If you think this change is good, I'll add test cases for the new client

Honestly, I wasn't even aware this was possible. Do any statsd servers actually support Unix socket + UDP?

@jsocol we run one internally at $dayjob that is based on python's socketserver.UnixDatagramServer, it works really well!

Interesting! Is it an open source server?
Given that it's a fairly esoteric configuration that I couldn't find in the existing ecosystem, my gut reaction is that it should probably not live in this library, since it's too far outside the common use cases. Extending the base classes here isn't super supported, as in they're not a committed public API, but I don't really expect them to evolve much at this point, either.

Haven't heard back so closing this one out. Happy to re-open if we see Unix+Datagram implementations in OSS servers—or to leave as a reference for anyone who's running this configuration locally.


Proper display name and other tweaks and fixes.json

Changed display name, made letter casing more consistent with the English version, fixed spelling and tweaked words and expressions

Thank you! Can you add your name to CREDITS.txt before I merge?


Changes to scroll menu items.

Use nanoScroller jQuery addon to allow for menu items to scroll. A few
minor word changes in index.html.

@rgrp - since you are a better coder than me, can you have a look at it please?

It only works in mainpage, are you considering to do it in every locale index.html?


PLATUI-855: Removed login redirect for all endpoints

looks good to me, and just to say it out loud in my own words to make sure i have understood it because I'm new to the change. This removes some restrictions on certain routes, keeps all existing endpoints but consolidates the code for them, won't break any use cases and if eventually people migrate completely to the canonical endpoint then we might remove the deprecated ones

@oscarduignan Yes exactly, basically the idea is to 1) remove the login requirement for any standalone pages, 2) retrieve enrolments for all contact requests, and 3) keep the existing endpoints until we can migrate everyone on the Platform off them.

@oscarduignan Ah yes sorry, I squashed rather enthusiastically. Change to remove the comment, and to remove the use of the binding of two different URLs to the form POST for ProblemsReports partial, as the two endpoints went to the same inner method anyway (the route itself has not been deleted).


[regression] NullReferenceException in Bluetooth.ScanForDevicesAsync() when no RequestDeviceOptions passed

Created a new project (.NET Framework 4.8, VB.NET)
Added InTHeHand.BluetoothLE NuGet (latest version, 4.0.24)
Called Device.ScanForDevicesAsync() from async button click event.
Crashes with a NullReferenceException.
If I call the same procedure, but pass in a new RequestDeviceOptions class, it works fine. It's only the overload for ScanForDevicesAsync() with no RequestDeviceOptions that crashes.
This is a regression, as it worked in 4.0.23.
Code:
Imports InTheHand.Bluetooth

Public Class Form1
    Private Async Sub butScan_Click(sender As Object, e As EventArgs) Handles butScan.Click
        Await Bluetooth.ScanForDevicesAsync()
    End Sub
End Class

Exception:
System.NullReferenceException: 'Object reference not set to an instance of an object.'

Call stack:
    InTheHand.Bluetooth.Bluetooth.PlatformScanForDevices(InTheHand.Bluetooth.RequestDeviceOptions)
    System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task)
    System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
    System.Runtime.CompilerServices.TaskAwaiter<TResult>.GetResult()
    BeaconConfig.Form1.butScan_Click(Object, System.EventArgs) in Form1.vb

I can see where this was introduced in the windows code. Will get it fixed for the next release

I got the same problem.

Resolved in 4.0.25

Got it！


Activating Open Collective

Hi, I'm making updates for Open Collective. Either you or a supporter signed this repo up for Open Collective. This pull request adds backers and sponsors from your Open Collective https://opencollective.com/ponyc ❤
It adds two badges at the top to show the latest number of backers and sponsors. It also adds placeholders so that the avatar/logo of new backers/sponsors can automatically be shown without having to update your README.md. [more info]. See how it looks on this repo.
You can also add a "Donate" button to your website and automatically show your backers and sponsors there with our widgets. Have a look here: https://opencollective.com/widgets
P.S: As with any pull request, feel free to comment or suggest changes. The only thing "required" are the placeholders on the README because we believe it's important to acknowledge the people in your community that are contributing (financially or with code!).
Thank you for your great contribution to the open source community. You are awesome! 🙌
And welcome to the open collective community! 😊
Come chat with us in the #opensource channel on https://slack.opencollective.com - great place to ask questions and share best practices with other open source sustainers!

@SeanTAllen - since we discussed this in a previous sync call, should we move forward with this merging this PR?

Give me a chance to review.

thanks @monkeywithacupcake !


Need to get the underlyingQueue. Make OperationQueue public?

Just to know, why would you like to access OperationQueue?

I have a BackgroundHelper which fetches remote data using Alamofire in such way:
let operation = ConcurrentOperation {
            let semaphore = Semaphore()
            DispatchQueue.main.async {  // This is needed because Alamofire uses DispatchQueue.main and Realm must be init on the same thread
                let realmManager = RealmManager.persistentRealm()
                manager = UsersManager(realmManager: realmManager)
                manager?.apiGetAccount { _ in
                    defer { semaphore.continue() }
                }
            }
            semaphore.wait()
        }

The thing is that Alamofire's completion block runs on DispatchQueue.main unless I give it a custom thread.
Normally, if I don't mistaken, I can get the current thread of an OperationQueue using "underlyingQueue" variable.
Maybe you have another way of doing so?

I have pushed your desired change in the develop branch.
Remeber to set the underlyingQueue to DispatchQueue.main before adding it to the OperationQueue, as wrote here 😉
Test it and when you will say that everything is ok I will push a new version 👍

I have released Queuer 1.3.1 with your fix inside!
Let me know if is everything ok


Associating wrong volume to non-admin service when service deploys to different node

Bug description
A non-admin creates a volume on node3 and deploys a service mounting this volume, this service is deployed by docker on node 1 so it auto-creates the required volume here and it is defaulting to administrator ownership
Expected behavior
The volume created by docker should be owned by the user that created the service mounting it.
Steps to reproduce the issue:

As non-admin user create volume on node3
As non-admin user deploy service mounting this (that docker deploys on node1)
As admin see there are now 2 volumes with the same name; 1 owned by administrators on node1 and 1 owned by the non-admin on node3
As non-admin see you can only see the volume on node3 and you can delete it (this succeeds as it is un-used by the service)
As non-admin view the service and it will now show a blank volume dropdown (as we are incorrectly showing the un-used volume which is now deleted)

Technical details:

Portainer version: CE-2.0
Docker version (managed by Portainer): 20.10
Platform (windows/linux): Linux
Command used to start Portainer (docker run -p 9000:9000 portainer/portainer): docker stack deploy
Browser: Chrome

Could be related to https://github.com/portainer/portainer/issues/4236


pulp_sync requires scheme part of docker registry URI

Pulp requires the scheme part of the docker registry URI, and so pulp_sync needs to be configured with it.
Don't strip out the scheme part when creating build parameters.
Strip out the scheme part for the source registry URI.
Strip out the scheme part for tag_and_push configuration.
Strip out the scheme part for spec.output.to.name.

LGTM

Oops ... I overlooked that we need to parse the source registry as well. I like the commit but would prefer if we used the same code to handle both source and target registries.
The last commit tries to do that - feel free to modify/drop it.

Updated to allow no source registry & addressed landscape issues.

Related: https://github.com/projectatomic/osbs-client/issues/308#issuecomment-156176676

Ready to merge?

Yes.


Enabling PublishBuildArtifact task in RM file share scenerio

Enabling PublishBuildArtifact task in RM file share scenerio

@SunnyKumarR,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


question: how does this compares to nvim.cmp?

e.g., can it handle completing from buffer, files and AI coding assistants?
Thanks

It's just a small experimental plugin. It doesn't have any other features. Don't pay too much attention to it :)


just check in init.go?

This is maybe more of a question rather than an issue:
Why not just check in init.go, and remove the importer.sh/go stuff entirely? Either way the end user has to modify a list of things, the only difference i see is the requirement of including the "_" prefix. Since the end user is probably just copy/pasting your examples, it might be nice to save them the go generate round-trip.
Just a thought.
Thanks for a great framework!

Hey, thanks for your question.
The idea was that if I forced users to update init.go, when you wanted to update to the latest version of the framework, update would complain of a dirty working tree. But I ended up including the shell script anyway in the repo... that was a mistake. The idea was that people would make their own (open source?) robots outside the slackbot/robots directory with bots that implement the bot interface because bots don't necessarily have to be in the robots directory. Then, by only changing the shell script to point to the various robots, you could generate the importer for your setup. I should probably take out the shell script and move it to the readme so we can properly update the framework using go get -u.

Yeah I think adding something to the README that says "Hey, put an init.go file in this location with these contents" is probably fine. If you leave it in .gitignore you still solve the dirty tree problem.
FWIW, we're using it for four different bots, each answering different slash commands, from the same runtime, and it's great. thanks again!

In lieu of this, I submitted a PR that makes it possible to use slackbot without using slackbot's main function: https://github.com/trinchan/slackbot/pull/19. This lets folks use their own main function easily, and obviates the need for init.go (which I left alone, and which still works fine)

#19 addresses my use-case; I still think checking in init.go and documenting necessary changes is probably the right way to go, since importer.sh makes the tree dirty anyway, but use of slackbot as a library covers our needs. Thanks!


Revamped build artifacts and versioning

I wanted to outline a proposal around the build output is for our two different types of projects, get consensus, and then implement the changes.
There are a few other issues out there (#470, #487, #444, #361 to some extent) related to the build output, and they would follow once these details are nailed down.
CommonJS & node CLI Projects
This includes sw-cli, sw-build, and sw-build-webpack-plugin.
Proposed build/ output
No substantial changes—we currently copy over the (unbundled) source to the the build/ directory as-is, without a distinction between dev and prod.
Proposed package.json metadata

"version": version string from lerna
"files": ["build"]
We currently include "src" as well, but that's not needed and can be removed.
"main": "build/index.js"

Service Worker "Runtime" Projects
This includes code that's executed at runtime within the context of a service worker, most notably sw-lib, but also the other smaller projects like sw-runtime-caching or sw-background-sync-queue.
Proposed build/ output
build/
  importScripts/
    <pkg.name>.dev.js
    <pkg.name>.prod.v<pkg.version>.js
  modules/
    <pkg.name>.dev.mjs
    <pkg.name>.prod.v<pkg.version>.mjs

The build/importScripts/ naming emphasizes that the files in that directory are meant to be consumed by the service worker via importScripts().
The build/modules/ naming, and the .mjs extension, emphasizes that the files there are meant to be consumed as ES2015 modules. I don't know if it's currently important to include the versioning info inside of those filenames, but including it is forward-looking for the time in the future in which a service worker could natively import the modules instead of using importScripts().
Getting the correct version number included in the filenames might pose a challenge, as it could involve hooking into the lerna build and doing a renaming after Rollup bundling is complete but before lerna pushes things out to npm. I need to explore that more.
Assume that sourcemaps are published alongside each JavaScript bundle.
Proposed package.json metadata

"version": version string from lerna
"files": ["build"]
We currently include "src" as well, but that's probably not needed and can be removed.
"main": "build/importScripts/<pkg.name>.prod.v<pkg.version>.js"
Point to the prod iife bundle here, primarily because some JS CDNs use that info to determine what gets served by default.
"module": "build/modules/<pkg.name>.prod.v<pkg.version>.mjs"
It looks like the current ES2015 module bundlers have standardized on using module for this purpose. We can remove jsnext:main which we were previously using.

(I've edited my initial proposal to add in a main:dev field in package.json.)

My only concern with not including the version in the dev build is that it adds friction to switching to the production build.
In my head I was thinking developers could change environment by simply replacing 'dev' and 'prod' in the file name, now it's 'dev' and  'prod.' which I think would actually cause more pain than it solves.
For testing we could create a helper endpoint that would take /__test/find-build/packages/sw-lib/build/sw-lib.dev.js and that return file for /packages/sw-lib/build/sw-lib.dev.v0.0.0.js

Agreed that we can handle the automated testing use case via redirects in our test server. Getting the demos happy with URLs that change with every release is a bit trickier.
In any case, it does make more sense to optimize for developer best practices rather than making first-party demos easier to publish, so I can go back to including version info in dev.
Maybe the solution is to use template variables in the demos to automatically insert the proper URLs inside of importScripts() instead of hardcoding them.

Maybe the solution is to use template variables in the demos to automatically insert the proper URLs inside of importScripts() instead of hardcoding them.

That sounds like it should address the concerns around versioning for dev.

This was fixed by a combination of #505 and #510


Fix test_enum unexpected success on Windows

It might be best just to skip it, my guess is that it's non-deterministic based on hashmap state or something.

I believe it previously failed due to the presence/absence of the \r character.


Chef Manage does not go through Chef Guard

After upgrading to Chef 12, I was able to get Chef Guard working. I then installed opscode-manage and made a few changes through the WebUI. I noticed that these changes were not logged to the config repo by Chef Guard.
Initial I configured the chef server like the Chef Guard instructions recommend. This works for the knife commands but not the WebUI.
lb['upstream'] = {
    "opscode-erchef"=>["<IP_ADDRESS>"],
}

Assuming opscode-manage was ignoring the opscode-erchef setting and talking directly to <IP_ADDRESS>, I moved opscode_erchef to <IP_ADDRESS> and had Ghef Guard listen on <IP_ADDRESS>.
# /etc/opscode/chef-server.rb
opscode_erchef['listen'] = "<IP_ADDRESS>"

# /opt/chef-guard/chef-guard.conf
[default]
  listen = <IP_ADDRESS>
[chef]
  erchefip = <IP_ADDRESS>

This had the same result as before, knife goes through Chef Guard but the WebUI does not.
I looked into the configuration of opscode-manage, but did not see where to tell it to look for erchef. https://docs.chef.io/config_rb_manage.html

@Tech356 very nice, but your looking in the wrong direction... Your initial erchef setting are correct, so it's not in there.
I think this is due to the fact the urls have changed for Chef 12 so they are inline with the urls Enterprise Chef uses.
So what does the url to your nodes info webpage look like? I guess something like https://your.chef.server/organizations/name/nodes?
If so I think you have to configure Chef-Guard to for enterprise chef to make it work.
I'll make this done automatically in the next release comming up shortly...

@svanharmelen That was it. When I configured Chef-Guard for enterprise chef it started working.
There is an outstanding issue related to the default_orgname chef sets up when upgrading. When I don't specify the organization in my knife.rb, the command succeeds using the default_orgname and does not get logged by Chef-Guard. Removing the default_orgname setting from chef-server.rb removes this unlogged path. If Chef-Guard can log those changes that would be good. If not, then a note should be added to the documentation to tell users to remove default_orgname so there isn't an unlogged path.

As you may have noticed I'm working my way through the open issues right now, and I wonder if you could provide me with a little more details about this one? For example do you have an example of the URL's your referring to?
I'll be on IRC today, so maybe hook up there to get this one clear (and fixed)...

When upgrading from Chef 11 OSS, the upgrade adds default_orgname <org_name> configuration setting. This allows the existing clients to continue talking the server using the Chef 11 OSS style urls. Chef will miss the Chef 11 OSS style calls when set to type = enterprise.
From https://docs.chef.io/config_rb_server_optional_settings.html
The Chef server API used by the Open Source Chef server does not
have an /organizations/ORG_NAME endpoint. Use this setting to
ensure that migrated Open Source Chef servers are able to
connect to the Chef server API. This value should be the same
as the name of the organization that was created during the
upgrade from Open Source Chef version 11 to Chef server version
12, which means it will be identical to the ORG_NAME part of
the /organizations endpoint in Chef server version 12. Default
value: the name of the organization specified during the upgrade
process from Open Source Chef 11 to Chef server 12.

A workaround is to delete the default_orgname <org_name> setting so that only Chef 12 style urls are allowed. Although this means every node needs to have it's chef_server_url setting updated to the new Chef 12 style url.

@Tech356 thanks for the detailed info! I actually looked at this one earlier today and think I have a solution. But it will need some more testing so will cycle back when I confirmed the fix/change works.

Hi @Tech356! I'm going to close this issue as its very, very old. And even though it's still true, I don't think it's causing issues anywhere anymore. Thanks!


Setup the testing environment

So far this project doesn't seem to have proper testing coverage.
In my opinion, a proper testing environment can improve the health and consistency of this current project.
With that said I suggest these improvements:

[ ] Replace Minitest by RSpec
[ ] Add shoulda-matchers
[ ] Add simplecov
[ ] Add FactoryBot
[ ] Write specs for all use cases

All gems above are from personal preference, however, they're pretty common in many projects.

[ ] Replace Minitest by RSpec

Can you help us with some of these tasks?


Train without header

Is it possible to train without having a header row, but rather specify column number somehow?

Hi @Larsk97 at the moment a header is required. Can you just add a header with numbers in it? For example, if you have 4 columns, add the line "1,2,3,4" to the top of your CSV.

@nitsky That is what I did for now :+1: Thanks for reply!


Grammar

This appears to duplicate changes requested in another PR  https://github.com/aspnet/AspNetCore/pull/6065.


Update README.md

Fix typo

Thanks @DenimTornado - this isn't actually a typo however - semver means semantic versioning, a small lib we use to make logic switches based on the current Ember version!


Long KEVM proof

This is a simple Solidity program:
// SPDX-License-Identifier: UNLICENSED
pragma solidity =0.8.13;

import "forge-std/Test.sol";

contract Token{

}

contract DealTest is Test {

    function testDeal(uint256 value) public {
        Token alice = new Token();
        vm.deal(address(alice), value);
        assertEq(address(alice).balance, value);
    }
}

I am generating a KEVM proof from it, and running said proof. It takes too long (8m52s s on my machine). I want it to take 20s.
Attached is the bug report.
foundry.tar.gz

Do we have a standard testing harness that can run these bug reports through the profiler? If not, what are the default first profiling steps we should do with these bug reports? Let's write the instructions down, and then we can figure out a way to automatically collect that profiling information and attach it to the issue here.
@ana-pantilie @jberthold and @goodlyrottenapple , when you get a "profile this and make it faster" request, what are the first things that should be attempted?

Do we have a standard testing harness that can run these bug reports through the profiler?
Not really, you just need to configure cabal to build the backend with profiling, and then run the test with some RTS options which will output profiling info. For time profiling, the steps are described here: https://github.com/runtimeverification/haskell-backend/wiki/Profiling#haskell-profiling.

I usually do eventlog profiling, as described in the link above. One thing to mention here, is that you need to tweak the timeout, since Speedscope can't handle eventlog files which are too large. I've noticed that between 3 min and 5 min I usually get good results.

we can figure out a way to automatically collect that profiling information and attach it to the issue here
When opening an issue, if you could also attach one of these Speedscope profiles that would be useful. We could quickly look at the profile and assess if it is a known problem or not.

There's also https://github.com/runtimeverification/haskell-backend/blob/master/docs/profiling.md which was recently added by @goodlyrottenapple . That also documents memory profiling options. That kind of profiling is useful when the test ends with the warning regarding productivity, or if you notice your test is using up more and more memory over time. I'm not sure how useful automating this would be, though, I haven't done memory profiling in a while and I haven't tried the newer options on the GHC 9 build, so maybe @goodlyrottenapple or @jberthold have a more up-to-date perspective on this.

Issue made: https://github.com/runtimeverification/haskell-backend/issues/3221

Thanks @ehildenb !

We should just profile and report what we find.

Yes, this can be used as an exercise to inform the steps we want to use for #3221 .

Running new profiles should be very simple, ideally the build system would have a direct way to consume the tarball and produce the profiles.

@ana-pantilie any progress on this? Did we run the profile manually yet?

@ehildenb https://github.com/runtimeverification/haskell-backend/issues/3221 should be done soon. When it is, I'll re-open this issue using the template from https://github.com/runtimeverification/haskell-backend/pull/3265. The team will meet and we'll look over the data together.
I did take a look at one of the profiles by myself, and I believe that we already have WIP or planned work to improve the hotspots present in the profile. If we find anything new we'll open new issues and link this one to them.

I am triggering a new test run by writing text that contains the sequence .tar.gz

The profiling run above (using latest master with new ceil simplifier) produced no immediate new clues. The (non-profiled) run was cut short after 4 minutes, profiling shows hashWithSalt and liftSimplifier (as well as ravel from the generic lenses) to be big consumers.
On my machine (12th gen. i9 with 16 + 8 cores) the proof finishes after 3 minutes now, though.


Symfony 6 support

./composer.json has been updated
Running composer update deployer/deployer
Loading composer repositories with package information
Restricting packages listed in "symfony/symfony" to "6.0.*"
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires deployer/deployer v7.0.0-rc.3 -> satisfiable by deployer/deployer[v7.0.0-rc.3].
    - deployer/deployer v7.0.0-rc.3 requires symfony/console ^5 -> found symfony/console[v5.0.0, ..., v5.4.0] but it conflicts with your root composer.json require (6.0.*).

Use deployer/dist.

deployer/dist => https://github.com/deployphp/distribution

@cdupoiron Thank you for clarification. I have never heard about this package before even though I use deployer for years and upgrade regularly.


Problem with URLSearchParams

Is this API going to be supported in edge anytime soon? getAll seems to only return one occurrence.
https://developer.mozilla.org/en-US/docs/Web/API/URLSearchParams/getAll

hey @kasper3 , thanks for reporting the issue. This is a web API which is out of scope of the JS engine. Please open an issue on the Edge issue tracker https://github.com/Microsoft/ChakraCore/wiki/External-Issues#edge-issues.


[ctl-commands] Restart haproxy on upgrade in chef-backend mode

When configured to use Chef Backend, all postgresql requests are
routed through HAProxy. Thus, in order to ensure that we can access
postgresql during upgrades, we need to start haproxy rather than
postgresql.
NB: This assumes that the existing 15 second sleep is enough time to
allow haproxy to stabilize (i.e. mark non-leader nodes as DOWN). In
the reconfigure cookbook we do an active check that looks for the
steady-state rather than a sleep.
Signed-off-by: Steven Danna<EMAIL_ADDRESS>

@chef/chef-server-maintainers OK, this is ready for review.  I've decided if we want to put the more-robust haproxy status checking code in here as well, we should just finally do it the "possibly more correct" way and create a shared library that we can access from all of these minor ruby projects: https://github.com/chef/chef-server/pull/1336


[DOC-9553] Correct the note about updating the CA certificate, document how to roll out a CA certificate update gradually

[DOC-9553] Correct the note about updating the CA certificate, document how to roll out a CA certificate update gradually

@cjireland approved the current state of the PR out of band.


alert validation failed after change datasource name in dashboard

Steps to reproduce

create a datasource
create a a panel and alert with the datasource
find a typo in the datasource name, correct the name (dbUrl still the same)
in the panel, point to correct datasource name, delete the alert associated w/ the datasource
save the change will give the following pop up:

Validation Failed
Alert validation error: Data source used by alert url not found, alertName+....., databsource=<OLD data source>

The latest grafana version handle this error more accurate:


arrow module

Hello, when I try to run it, it tells me that the arrow module is missing. I have tried to run it with the phyton idle itself and with pycharm, but the result is the same.

Sorry, I was just adding it

You'll want to pip install -r requirements.txt - all package requirements are included here.


[Feat Request] Inclusion of Skills such as Intrepid Heart for Abnormality Widget/Player Widget

It would be nice to be able to track certain armor skills which are currently not included in the HUD.
For Intrepid Heart:
Option 1) Add independent bar for Intrepid Heart Progress
Option 2) Add a Buff selectable in the Abnormality Widget
For Dragonheart:
Option 1) Add selectable indicator to show thresh hold for Player Hud Widget
Option 2) Add a buff or debuff selectable in Abnormality Widget to track activation
As is right now, I could not tell whether Intrepid Heart would be active, or if Dragonheart's buffs became active when solely relying on the Player HUD Widget combined with a set up Abnormality Widget for buffs and debuffs.

Added Interpid Heart(Buildup) and Dragonheart active state to Abnormality Widget in v2.7.0.
You can update to beta version, If you are patreon.

Thanks for the quick response. I will look forward to v2.7.0!


Build 240223 (>230921) works well but with workaround to solve the cloud auth issue for TP-Link Tapo C220

Description
Hello it works finally for Tapo C220 camera with HA Core 2024.6.2 Frontend 20240610.0
But I have the issue with Cloud Auth today 12.06.24.
After reading forums on Github also I have tried to solve the authentication issue.
My Firmware Build version is 240223 and it is higher than the version in the warning "does not work temporarily on firmware build 230921 and higher" https://github.com/JurajNyiri/HomeAssistant-Tapo-Control?tab=readme-ov-file
Hardware: by TP-Link
Firmware: 1.1.9 Build 240223 Rel.56143n
Hardware: 1.0
Follow the rules: only ascii lowercase letters and numbers.

Created a useless account on https://tplinkcloud.com/
In my case I can use google email without a "dot" and it works.
Change account settings in the mobile app (in my case it is Android)
In this case, the password contains special symbols and upper cases but username follows the rule.

It was added to HA successfully, managed by "buttons" to the available functions in C220.
Streaming SD and HD video.
Thank you for the nice work.
BR, Alex
Reproduction Steps

Install Docker on win10 WSL
Install stable HA
Install HomeAssistant-Tapo-Control
Add device with IP
Auth to camera account
Auth to TP-Link Cloud

Expected behavior
Cloud auth accepts any combination of letters, numbers and special characters in password, email or account.
If applicable, add error logs.
No response
Device Firmware
1.1.9 Build 240223 Rel.56143n
Integration Version
HA  Core 2024.6.2 Frontend 20240610.0
Using stream component
Yes
Does camera work via official integrations?
N/A
Camera has all attributes filled out in developer tools
Yes
HASS Environment
Docker on Win10 WSL from homeassistant/home-assistant:stable image
Search for similar issues
Yes
Additional information
No response

BTW, it is a bug, a working state report and a workaround simultaneously. I have no idea how to post it correctly. Any recommendations how to do it are welcome.
Thanks in advance for your tolerance.

Sorry to dissapoint, but it gets rolled out to accounts in green blue, it was not rolled out to this new account  yet, this is not a long term solution.
If you have it working now, block internet access so it does not receive the update.

Link: https://github.com/JurajNyiri/HomeAssistant-Tapo-Control/issues/551


history Explanation of Blocktime

Hello all,
I am actually writing a script to get better results to put it forward to import for https://app.cryptotax.io/import-manual for Tax reasons. Actually I am stuck with the blocktime. What is the algorithm to translate it to the following format needed due to the cryptotax page:
trade_date: date in dd.mm.yyyy hh:mm:ss format and in the UTC time zone
Thanks in advance

Forgot to mention, I am talking about the results of the following command
example:
listaccounthistory mine {"maxBlockHeight":560002,"depth":0}

Forgot to mention, I am talking about the results of the following command
example:
listaccounthistory mine {"maxBlockHeight":560002,"depth":0}

Blocktime is the standard unix time seconds counted from 1.1.1970 1:00:00
I calculated it using the block explorer in the internet.

Blocktime is the standard unix time seconds counted from 1.1.1970 1:00:00
I calculated it using the block explorer in the internet.


ClassInitialize should have timeout independant from test methods

Method that's designed as a ClassInitialize method should be able to have a Timeout attribute that's independant of the first test being run.
I have a class with lots of tests that required a service running. When running locally, the service is typically not already running, so the class initialize set it up. This can lead to timeout. The current behavior is that the first test to run (which I don't have a way to control), will timeout. Instead I'd like to be able to give ClassInitialize extra time, and then have timeout for other test be short since none of the tests take much time once the service is up and running.

Tagging @pvlakshm @cltshivash to look into the ask.

I believe this is not an issue that's limited to MSTest V1 from an offline thread. MSTestV2 does not include Init/Teardown as part of a tests duration. We might want to add this into the delta doc in testfx-docs.

Made the change in the docs: https://github.com/Microsoft/testfx-docs/pull/60
While its nice to have this new behavior it looks like we might want to add in a way of constraining timeout on setup/teardown methods. Do we have internal extensions perhaps that already do this that we can share out broadly or maybe we might want to just stick in individual timeout attributes on them?

I believe this is fixed by #2085


Run large scale diffs of eyecite output on every PR

A proposal: I think it would help a lot if we had a Github Action that showed the effects of a pull request on a large corpus of random cases. I would script it something like this:

benchmark.py corpus.zip ref1 ref2 compares the eyecite codebase at ref1 and ref2 when run against the zipped folder of text files in corpus.zip.

By default ref1 is main and ref2 is HEAD, so it compares upstream with the current code.

We could have a few standard corpus_10MB.zip, corpus_100MB.zip type files stored as github releases, sampled evenly from documents we care about. I might have a size that takes about 30 seconds to process for local iteration, and a size that takes about 5 minutes to process for CI?
for each of ref1 and ref2, the script clones the repo into a temp dir; makes a temp python venv and installs dependencies; extracts citations from benchmark_cases.zip; and writes the resulting citations to a json file
finally the script stores a diff of the two files and reports the size of the diff and how long each extraction took

This could be very useful locally, and also could be wired up into a Github Action that ran benchmark.py corpus_100MB.zip and saved the results as artifacts of the run, and reported the runtime and diff size as a PR comment.
I'd anticipate two benefits of this:

For bigger PRs like partial cite extraction where we don't know how courts actually cite things, it would be easier to see whether our guess was right.
For smaller PRs where we think we aren't changing much, it would stand out if we were actually adding a bunch of false positives or negatives or slowing down performance.

Basically for a project that depends heavily on heuristics, I think it would be great to have more of a sense of whether a heuristic tweak is helping or hurting on average.

Yeah, this is a really good idea. I'd be pretty excited if somebody wanted to run with this. It'd remove some of the uncertainty we have around the little tweaks we make here and there.
I've seen some other tools that seem to keep track of regressions in things like coverage, I think. Might be nice to be able to say, "Speed is down by 10% and 20% more citations were found." I assume that requires some sort of DB that isn't built into Github, but I've never looked to see if there are simpler solutions for this.
Anyhow, yeah, this feels like a good idea to me.

I assume that requires some sort of DB that isn't built into Github, but I've never looked to see if there are simpler solutions for this.

What might work is to download an artifact from the last successful run on the main branch using this action, and compare it to the same artifact generated in the current run.
Seems like one could start just with a local benchmark script to dump citations and timing information to json from a zip file, and iterate on CI integration from there.

This has been implemented @jcushman.
Although it could certainly and will certainly improve over time, any PR in reporters-db or eyecite will trigger a comparison of the PRs against the current eyecite/reporters and give a sample of improvements or degradations.
We have some trickiness with the token, currently its using one of mine, so I am going to leave this open until we update the token to the freelawbot_token

This is awesome -- thanks, Bill!


Data page search doesn't work on mobile

No results returned:

@yudilevi I imagine this is no longer the case?

Still the case.

it was not a bug on mobile, it was general bug with case sensitivity. Eth or ETH will lead to zero results on desktop as well. fixed


Problems with deployment

Describe the bug
When I press deploy Bolt starts but then suddendly gets an error: I've initiated the deployment process for your Recipe Generator application to Netlify. The build command npm run build will be used to create a production-ready version of your Next.js application, and the output directory .next will be deployed.
Now, let's wait for the deployment to complete and retrieve the deployment status.
An error occured while streaming this message.
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-xruqqm
Steps to reproduce
just deploy any app, it doesnt work
Expected behavior
to deploy the app
Screen Recording / Screenshot
no
Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 129
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 117291273,
  "usedJSHeapSize": 109579845,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = andresroi
Chat ID = b970b34eda8d

Additional context
Error:
An error occured while streaming this message.

Thanks for the report and patience during this beta period! Tracking all deployment related bug fixes in issue #499


Enemy TerminalNode displays incorrectly

This is just a heads up because I was looking at your code for handling enemy logs in the terminal, you have to set the TerminalNode's buyItemIndex, buyRerouteToMoon, and shipUnlockableID to -1 or Terminal.OnSubmit will treat it like your rerouting to a node instead of getting an enemy log.

Is this still an issue that exists?


[DOCFIX] Remove bootstrap related doc

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15815/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15818/
Test PASSed.

@gpang PTAL

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15823/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15825/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15829/
Test PASSed.

Merged build finished. Test PASSed.

@gpang @calvinjia  PTAL

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15837/
Test PASSed.