Call to authenticate fails from .NET

The call to /REST/server/authenticationtokens in MFWSClient.cs has suddenly stopped working. The error we receive is
System.Net.WebException: The SSL connection could not be established, see inner exception.
---> System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.
---> System.Security.Authentication.AuthenticationException: Authentication failed because the remote party sent a TLS alert: 'HandshakeFailure'.
---> System.ComponentModel.Win32Exception (0x80090326): The message received was unexpected or badly formatted.
--- End of inner exception stack trace ---
at System.Net.Security.SslStream.ForceAuthenticationAsync[TIOAdapter](TIOAdapter adapter, Boolean receiveFirst, Byte[] reAuthenticationData, Boolean isApm)
at System.Net.Http.ConnectHelper.EstablishSslConnectionAsync(SslClientAuthenticationOptions sslOptions, HttpRequestMessage request, Boolean async, Stream stream, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
This began happening on 12/21/2023. Anyone else having this issue?

We added this temporary fix in our global.asax file. M-Files must have changed something something in their load balancer or IIS configuration that has caused the negotiate step of TLS to fail. It only is failing on Windows 11/Server 2020. Our Linux containers seem to work.
// force TLS 1.2 because of M-Files. This is a "temporary" fix
System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12;

TLS 1.2 has been a requirement in the M-Files cloud for some time. Where is your vault located? What changed on your server on 21st December; was it an M-Files install?
That said, the core issue is because the default protocols supported by dotnet are defined by dotnet and/or the OS that the code is running on. We could alter the library to perhaps attempt to include 1.2 into the supported protocols, but we'd then have to possibly do the same with other versions in the future... I'm not sure I like that.

If your vault is hosted in M-Files cloud, it uses Azure app services. So this is interesting https://techcommunity.microsoft.com/t5/apps-on-azure-blog/upcoming-tls-1-3-on-azure-app-service-for-web-apps-functions-and/ba-p/3974138


Let's define image icon

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
I setup th card and would like to use th status image as a privacy function. Bit the icon for the static icon is a picture and I would like to change this icon .any idea or do I have to add an icon myself with a button that calls the function to show the static image ?
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

There's no way to do that with the built-in default menu items. Your best bet (as you guessed) would be to do something like this:
elements:
  - type: custom:frigate-card-menu-icon
    icon: mdi:butterfly
    tap_action:
      action: custom:frigate-card-action
      frigate_card_action: image

There are two downsides to this:

With the in-built menu icons, they are styled/emphasized  when that view is active (e.g. click on 'Clips' and notice how the color of the icon will change to show it is selected). That would not happen with the above idea.
Support for custom:frigate-card-action is not in any released build, so you'd need to wait for the next one.

Then I wait  for next build or does Dev version already work with that action?

You'd need to wait for the next beta build.

Going to close this for now, but let me know if it doesn't work for you once released!


The Evaluate roll selection GUI needs work

Only shows 5 at a time, not searchable.. would literally take an hour or more to scroll through this list -- let alone if you are actually thinking on each one and clicking/selecting things. Having to select them and then also click the arrow shouldn't be necessary. (these could just 1 click check boxes)
I'd like to know exactly where these settings are stored so I can open it in notepad and control + F my way to what I want. I scrolled for a couple minutes trying to find Has Abyssal Socket and just gave up in nightmare-GUI frustration.
I think the program isn't respecting system refresh rate or something either. Even at 165hz refresh I get pretty bad smearing/skipping if I try to scroll quickly.

So how do we actually add and remove auto selected mods? The current gui for it is laughably unusable. Just tell us which config it is in since this type of polish is probably low priority.

Where is the actual setting located in a file? Would be so much easier than trying to use this GUI.


Parsing OpenQASM 3 parameter variables

Summary
This pull requests allows for parsing input (i.e. symbolic) parameter variables.
Details
OpenQASM 3 introduces many variable types, such as the angle and float types. Both types can be used to describe the values passed to rotations (the documentation refers to using angle types, though the OpenQASM generator in qiskit seems to use float). When either type is prefixed by the input keyword, this indciates that the circuit is parameterized and that this value should be taken as a parameter at runtime. There doesn't seem to be a consensus on how to do this in practice, though in this pull request I've decided to focus on arrays of angle or float values.
An unconventional design choice in OpenQASM 3 is that angle[n] indicates an n-bit floating-point angle, whereas array[angle,n] indicates an array of n angles with default bit-width. Then the following declarations are now supported by the parser:

input array[angle,n] name;
input array[float,n] name;

Each array cell is associated with a unique symbolic parameter. When a cell is referenced as the parameter to rotation gate, the aforementioned symbolic parameter is used as the argument.
Further Work
Note that when parsing multiple files, the OpenQASM 3 file does not remember the current state of the context. For constant values this is less than optimal (the same constant may be constructed multiple times), though it does not impact correctness. However, if you want to compare two circuits using the same parameters, this becomes impossible. Let's say both circuits declare input array[angle,3] ps; as the only parameter array, and that constant parameters do not appear in the circuits. Then ps[i] will be associated to symbolic parameter i in the first circuit, and parameter 3+i in the second circuit. In a future pull request, I want to add the option to have this data persist across multiple files.
The use-case I have in mind is to generate a json file from a pair of OpenQASM files with the same parameter variables, so that the Quartz verifier can check the parameterized equivalence of these circuits. I guess in some sense, this would be a front-end to the equivalence checker.

Note that when parsing multiple files, the OpenQASM 3 file does not remember the current state of the context. For constant values this is less than optimal (the same constant may be constructed multiple times), though it does not impact correctness. However, if you want to compare two circuits using the same parameters, this becomes impossible. Let's say both circuits declare input array[angle,3] ps; as the only parameter array, and that constant parameters do not appear in the circuits. Then ps[i] will be associated to symbolic parameter i in the first circuit, and parameter 3+i in the second circuit. In a future pull request, I want to add the option to have this data persist across multiple files.

Good point! Does it make sense to use different ParamParser objects whenever two circuits use different parameters with the same array name? For example, if 3 circuits have
input array[angle,3] ps;
rz(ps[0]) q[0];

input array[angle,3] ps;
rx(ps[0]) q[0];

input array[angle,3] ps2;
rx(ps2[0]) q[0];

And if we use the same ParamParser object, then the first two circuits should share the same symbolic parameters, but the third one uses a different set of parameters. If the user wants different symbolic parameters even for the first two circuits, then they should use different ParamParser (or Context) objects to parse them.

@xumingkuan I agree with everything you said. I'll see if I can make that work in my next pr.


not support :kbd:Enter

not support
:kbd:`Enter`

error msg:

other

Can't Toggle Preview, only can preview but can't back to edit with ctrl+shift+r.
Can't click link in preview

The kdb tag is a Sphinx specific tag which is a superset of RST. This extension only supports tags defined in the docutils python module.
As for the other two issues, the first is being worked on but is dependent on the VSCode team opening up some more features of the API, the second I would classify as a nice to have but will look into :smile:

@tht13 an update from Microsoft is that Markdown becomes an individual extension (instead of hooking deeply with VSCode itself), so that opening up the opportunities for the two reStructuredText extensions.

@lextm I have been tracking this issue as it is also functionality I will incorporate into my html preview extension :smile:
I have raised this issue for VSCode as a suggestiong for how this can be done, both for our extensions and their markdown one.


Blank space at the end of page

Environment
"nuxt": "^3.2.0"
Reproduction

Describe the bug
When I redirect to another page using navigateTo(), nuxt generates blank space at the end of page and that space is not even in body or html tag.

Additional context
No response
Logs
No response

let me check @danielroe


Added Route Rule filter

Signed-off-by: SudhanAruna<EMAIL_ADDRESS>For Issue nmstate#935
Added filter function for route rules. Please let me know for improvements

Coverage remained the same at ?% when pulling 5a3bd6154252acc6333ec8ad025370c6df0ab971 on SudhanAruna:Filter_RouteRules into 4d05b7ee88802f65effcd399b4cfdff0d67d6771 on nmstate:master.


refactor spawn API

I would want the spawn and spawn_blocking to return a spawn handle or something equivalent and as substrate uses tokio quite extensively looks reasonable to return tokio::task::JoinHandle instead.
Needed by #13992
No real code changes rather than tests and benchmarks

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2744791

A spawn handle is just:
let (rx, tx) = oneshot::channel();

spawner.spawn(async move { do_something.await(); let _ = tx.send(()); });

rx.await();

yeah, but I didn't to make code so verbose with oneshot's when tokio spawn already has it..
I can add the oneshot stuff and you can complain in my other pr :D

I can add the oneshot stuff and you can complain in my other pr :D

Let's try that for now :P

yeah, but I didn't to make code so verbose with oneshot's when tokio spawn already has it..

If we add the JoinHandle, I would still make it generic. Aka something that wraps a Box<Future>. I know that we are currently using Tokio, but it doesn't leak that much to the internals right now.

Fair enough
We could add some such as impl Future<Result<(), ()>` as return handle but yeah closing this


advance::all_edges

all_edges advance is actually different from other advance load-balancing schedules. As the name suggests, it performs on ALL edges of the graph, therefore, ignoring the input frontier. This needs a slightly different API interface to make sure people understand when they use this advance, it is not necessarily on the input frontier, it is on the entire graph.
We can also consider making it a new operator instead to avoid this confusion.

@bkj this is the concept you're using for pagerank.

https://github.com/gunrock/essentials/commit/3164aa8f89f966be8eefd90f7cdfbc43c933b3a7


gif as background img?

I have a gif that is the background of a div element. Ive tried adding the freezeframe class to the div but it doesnt seem to work. Any ideas?

just updated to v3, previous version had issue with CORS which is fixed now, check out the new version and let me know if you're still having an issue


Update version number and create Attribution.txt

Update version number to 0.7.1 for Delhi dot release and create Attribution.txt
fix #2
Signed-off-by: Cloud Tsai<EMAIL_ADDRESS>

@tonyespy
I've added them into SDK.  Is it fine for this PR?


Support WebGL2 and WebGPU in the same WASM file

What problem does this solve or what need does it fill?
Bevy currently forces you to choose either WebGL2 or WebGPU when building a project. This is one extra thing that developers need to think about when deploying their games, which is already a complicated enough process.
Since the web is a large, incredibly portable platform, we should attempt to make targeting it as painless as possible.
What solution would you like?
In https://github.com/gfx-rs/wgpu/pull/5044, WGPU added support for detecting WebGL2 and WebGPU at runtime. I think integrating this into Bevy would be incredibly useful, and give WebGPU more exposure. This would be achieved through the existing webgl2 and webgpu features.

webgl2 enabled?
webgpu enabled?
Behavior

✅
✅
Detect API at runtime, preferring WebGPU and falling back to WebGL2 if not available

✅
❌
Use WebGL2, panicking if not available at runtime

❌
✅
Use WebGPU, panicking if not available at runtime

❌
❌
Fail to compile for WASM

Questions

What crate(s) will need to implement this functionality? Is there a way we can abstract over both APIs to reduce the amount of logic necessary?
Does WebGPU still need --cfg=web_sys_unstable_apis, and do we handle this already?
How difficult will this change be? Is it something we can plan on finishing by Bevy 0.14?

What alternative(s) have you considered?

Instead of panicking, using the error!(...) macro may be preferred because it will be visible in the Javascript console.

Do we have a panic handler for WASM that logs panics? If not, then error! may be preferred.

Additional context

Discord message that inspired this feature request
https://github.com/bevyengine/bevy/pull/11280#issuecomment-1894914591

cc @Elabajaba, who originally migrated Bevy to the WGPU version that introduced this feature.

Questions

What crate(s) will need to implement this functionality? Is there a way we can abstract over both APIs to reduce the amount of logic necessary?

Only rendering part should be affected

Does WebGPU still need --cfg=web_sys_unstable_apis, and do we handle this already?

No, wgpu now vendors those so they're not needed anymore

How difficult will this change be? Is it something we can plan on finishing by Bevy 0.14?

Biggest difficulty I think is that currently some const change value depending on WebGL2 / WebGPU / Native. Deciding them at runtime means they won't be const anymore.
Also I think WebGPU detection is hard to do perfectly, so we need a way to "force" fallback on WebGL2 even if WebGPU is detected

Biggest difficulty I think is that currently some const change value depending on WebGL2 / WebGPU / Native. Deciding them at runtime means they won't be const anymore.

Ok, that will require a bit of benchmarking then to ensure the performance hit is not too great. This will probably affect all of WASM, even if you don't runtime detection.

Also I think WebGPU detection is hard to do perfectly, so we need a way to "force" fallback on WebGL2 even if WebGPU is detected

You can toggle off the webgpu feature at compile time. If we want to do this at runtime, perhaps there can be a resource that configures it. Quick draft:
// This is a bad name, please ignore it
#[derive(Resource)]
enum WASMBackend {
    WebGPU,
    WebGL2,
    Available, // Prefers WebGPU if possible, could be named `PreferWebGPU`
}

Ideally (parts of) Bevy should also support building without WebGL2 and WebGPU, and support targeting wasi (https://github.com/bevyengine/bevy/issues/4906 & https://github.com/bevyengine/bevy/pull/8520)

Related: #11505

Will this feature double the WASM file size for those who only want to use WebGPU or WebGL2, or just increase the size slightly?

just increase slightly!


Guidance for AAD groups

could you please provide recommendations for creating and managing Azure AD groups.

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

ID: ed24fd26-b126-c171-7edd-9f6713f23ab5
Version Independent ID: 1e240640-ff8c-8183-bd28-ebe3aa4674ff
Content
Content Source
Service: security

@DeanGross
For the implementation of the specific question, it would be better to post on MSDN, so that the community can help answer the question. The link below should take you to AAD specific section
https://social.msdn.microsoft.com/Forums/en-US/home?forum=WindowsAzureAD

I'm confused by the response, i don't understand why this would be considered a dev topic. The page that I added the comment to is all about best practices, i'm just asking for another section to discuss best practices for AAD groups

@DeanGross thanks for the feedback, my advice was to check on forums to get a broader input from users already using the solution, I'll assign the comment to the author to see if they can provide you with additional insights as you wish.

Hi @Adam-Smith-MSFT why this topic was assigned to me? I don't work at the content organization anymore.

@YuriDio You were marked as the author in the metadata, please ignore, I'll assign it to the manager in charge to update the content.

@DeanGross Hi Dean, to address your immediate concern, we have a lot of content in the AAD documentation on managing groups. A good place to start would be Manage access to resources with Azure Active Directory groups.

#in-process
@DeanGross Instead of updating the article you refer to (which is old and needs to be replaced), can you look at our main doc pages for managing groups. That's the best place to find guidance on this subject.

@mtillman , thanks for the suggestion. I'm familiar with the extensive guidance, but what I'm looking for is the recommended best practices for groups. The page states that "For each best practice, we’ll explain:

What the best practice is
Why you want to enable that best practice
What might be the result if you fail to enable the best practice
Possible alternatives to the best practice
How you can learn to enable the best practice".
I'm just asking for this to be done for AAD Groups

@DeanGross I see what you're asking for. I've opened an item on our internal work backlog to address your request. Since it's now on our backlog, we're going to close the issue here. When we update the content, we'll report back on this issue so that you will be notified.
#please-close

@DeanGross
We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Failure [INSTALL_FAILED_CPU_ABI_INCOMPATIBLE]

App launches only in boxed android emulator, x86 Architecture. When i tried to run app in Genymotion or another architecture i got this error "pkg: /data/local/tmp/com.ericsson.research.owr.examples.nativecall
Failure [INSTALL_FAILED_CPU_ABI_INCOMPATIBLE]"
Is there someway to launch on another architecture?
Thanks in advance!

I don't think running in Android emulators is supported yet. @Rugvip?

Related to EricssonResearch/openwebrtc#435


Modify EBI code so that it does not upload empty files

These cause error messages to be thrown from EBI's end

I think this should be Alpha 0.2. It is a time sink for Gail because she has to run demux once, look at the log, manually remove samples with zero sequences from the prep template, and run demux again.

@adamrp Are you able to work on this?

+1
On May 7, 2015, at 10:22 AM, adamrp<EMAIL_ADDRESS>wrote:
I think this should be Alpha 0.2. It is a time sink for Gail because she
has to run demux once, look at the log, manually remove samples with zero
sequences from the prep template, and run demux again.
—
Reply to this email directly or view it on GitHub
https://github.com/biocore/qiita/issues/1070#issuecomment-99943542.

Yes, I think I can do this later today

Thanks! assigning to you so we don't loose track :-)


Faster draw functions (up to 10 times)

Precompute of indices of the buffer array to speed up drawings
Faster draw single pixel (fillMatrixBuffer)
Implementation of virtual AdaFruit GFX methods:
--- drawFastHLine
--- drawFastVLine
--- fillRect
The source has been indented and formatted using tabs, merge could not be handled by Git.

Oops, my 8266 is working at 40MHz with a 64x32 led matrix. Can be set at 20MHz, the optimization is at buffer matrix level, not at SPI.
The main idea is to compute the offset of the first byte of each line (actually the last one, since it is reversed to be streamed to SPI). This works correctly for 32x32 and 64x32 matrices, I didn't test for panel_width>1, but the original slower method is still there and can be used instead. At least since I would grab more than one panel... :)


Add ability to pass in connect_args to sql alchemy.

I need to be able to pass some connection config into sqlalchemy.  I think this is the easiest way to do it.

Ah, here's the doc I see: http://docs.sqlalchemy.org/en/rel_1_0/core/engines.html#custom-dbapi-args
But shouldn't there be any way to set connection_args in the __init__ of the class?

Ooops, forgot to put that in.

That was fast! :D

If you could add a test for this as well. That would be appreciated!

Sure.  I think I might update CopyToTable as well to pass this into the target it creates.

So I'm not exactly sure what the best way to test this is.  It does not appear that sqlite has many options, and I could not find a good way to extract it from the engine object.  I added the connect_args to the SQLATask that is used in several other tests, and it does appear that the tests are passing.

How are you supposed to use the CopyToTable task here? Write a test or at least documentation of how the connection_args are set. It's also not clear to me why the default value sometimes is {} and sometimes None.

Yeah, the inconsistency was not correct, I have fixed that.  I added some info in the documentation about it.  Its difficult to dive into too much detail because the way it works is very database specific.  The tests are setting the field, so it is technically being used.  Unfortunately, sqlite does not really have many connection settings, so I'm not sure how to verify this in a test.

Hmm, it seems like there's a test failure. Will you look at it?

Are the tests in a good state right now?  I'm getting failures when running all the tests on master.  When I run only the sqla tests, they all pass.
PYTHONPATH=. nosetests

Is am running the tests correctly?

No, you should use the tox command. Something like PYTHONPATH='' tox -e py27-nonhdfs test/my_test.py

Looks better now! :)
It seems like there's an actual test using this stuff now. Good job! Should I merge?

lgtm

If you were asking me, then yes I think you should merge. :)


refactor(uibackend): create new uibackend module

Description
https://github.com/openclarity/vmclarity/blob/main/rfc/multiple-go-modules.md

Create new uibackend module
Update licensei to ignore gen.go files and not directories

Type of Change
[ ] Bug Fix
[ ] New Feature
[ ] Breaking Change
[x] Refactor
[ ] Documentation
[ ] Other (please describe)
Checklist

[x] I have read the contributing guidelines
[ ] Existing issues have been referenced (where applicable)
[x] I have verified this change is not present in other open pull requests
[ ] Functionality is documented
[x] All code style checks pass
[ ] New code contribution is covered by automated tests
[x] All new and existing tests pass

Two notes:
uibackend package is used to generate API models only, but is defined on a parent level (above server and client). Is it possible to have uibackend/api/models, uibackend/client, uibackend/server instead of the current mode? It makes it a bit cleaner to separate the package responsibility

This sounds like a good idea. I would probably go even further and rename models to types. e.g. uibackend/types
Same should be followed for api module as well.

* `uibackend/server/pkg` can be moved to `uibackend/server` to keep it clean similar to `uibackend/client`

Disagree. I would keep  uibackend/server/pkg as there is a uibackend/server/cmd package as well. the server is an actual applications while the client is "just" a library.

thanks for reviewing, @ramizpolic and @chrisgacsal ! I will make the changes mentioned and split uibackend into 3 modules: types instead of models, client and server 👍

Please hold on with merging this until the following PR is merged: https://github.com/openclarity/vmclarity/pull/864


[Core] Add translations

{
"id": "word",
"_type": "WORD",
"translations": {"_type":"MAP", "pt_BR": { id:"palavra }}
}

Depends on #127

Another approach is to use an attribute meaning and multiple words from different languages might share the same meaning.
The query would take more time but the database will be smaller


Suggestions for the Search menu

I find the current ("make it like Amazon") filters difficult to understand.
Here is what I would suggest:

the numbers should remain with the full list counts after an update due to filtering.
the "See more" should only list an entity if it has a non-zero count. If there are none, I would leave the "See more" off.
once an item is picked in a category, add a "Clear" in that category on the left side menu.

Happy to discuss these further and what complexities these introduce.

Wondering if we can retire the inactive search URL parameter. Here are my thoughts:

This is not a generic Aries-VCR or credential concept, however the logic is embedded within Aries-VCR and the generic search interface.
We can still query and filter for active/historical entities through the application of entity_status category filters. Especially in light of the changes to filtering we want to make that successively expand the result set as filters are applied.

Thoughts on this?


insertFinalNewline does not insert final newline in certain case

Issue Type: Bug

Set insertFinalNewline to "true" in Settings.

Create a file (ex.: nodemailer.d.ts) with the following content
declare module 'nodemailer.d.ts';

Save the file. Observe that a newline is not added.

Remove everything after declare module. Save. Observe that a newline is added.

VS Code version: Code 1.30.1 (dea8705087adb1b5e5ae1d9123278e178656186a, 2018-12-18T18:07:32.870Z)
OS version: Linux x64 4.9.0-8-amd64

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-5250U CPU @ 1.60GHz (4 x 2635)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: disabled_softwarevideo_decode: unavailable_softwarevideo_encode: unavailable_softwarewebgl: enabledwebgl2: enabled

Load (avg)
0, 0, 0

Memory (System)
15.56GB (0.92GB free)

Process Argv
--unity-launch

Screen Reader
no

VM
0%

Extensions (4)

Extension
Author (truncated)
Version

dart-code
Dar
2.21.1

flutter
Dar
2.21.1

polymer-ide
pol
0.6.0

vscode-bolt-language
smk
0.0.4

I wonder if this issue is being caused by an installed extension. Can you try to run VS Code without extensions? From the command line (NOT the integrated terminal in Code), execute: code --disable-extensions and try your steps again to see if it reproduces. If you see it is an issue with the extension, please file it against the extension repository itself.

Thanks, this is fair. Here's what I just did:

exit VSCode

start VSCode from a terminal in an empty directory
$ code --disable-extensions nodemailer.d.ts

noted that a pop up appears telling me that extensions are disabled.

type declare module 'nodemailer.d.ts';, hit ^S (save). Observe that a newline is still not added.

@dotdoom can you share your settings?

I still cannot reproduce, here is what I see:

Thanks, so this seems to be triggered by a code action. Moving to @mjbvz (also @jrieken fyi)

Caused by https://github.com/Microsoft/TypeScript/issues/29236 upstream
I'll look into making the VS Code side of this more reliable so that other save participates are still run if the code actions fail


docs: update README.md

:tada: This PR is included in version 0.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


HPA can't get metric from metric server

i installed Krustlet in KinD. When i want to test whether HPA works or not. I got the error message like below.  krustlet doesn't support it, or i made some mistake here?
Script.txt
Thanks for any help!

At this time there is no support for HPA workloads.

At this time there is no support for HPA workloads.

@chuiyunjun If you'd like, we can recategorize this as a feature request to support metric endpoints. However, that will likely be low on the maintainers' list until after we hit 1.0. I think we'd be willing to look at any community PRs if someone would like to add it though!

@chuiyunjun If you'd like, we can recategorize this as a feature request to support metric endpoints. However, that will likely be low on the maintainers' list until after we hit 1.0. I think we'd be willing to look at any community PRs if someone would like to add it though!


Support emitting assets via webpack build

The webpack loader currently outputs a file directly to dist, which can then be picked up by the consumer's server render.
It's possible to pass in custom file systems to webpack, such as memory-fs.
This change allows the loader to optionally output assets directly into the Webpack output.
This change is non-breaking, and opted into by passing emitAssets: true.
I believe it may make sense to have emitAssets be the default behaviour, but that could break consumer builds.
Examples
Write to disk
    new ReactLoadablePlugin({
      writeToDisk: true, // or undefined
      filename:  path.resolve(__dirname, 'example', 'dist', 'react-loadable.json'),
    })

Emit to Webpack assets
    new ReactLoadablePlugin({
      writeToDisk: false,
      emitAssets: true,
      filename: 'react-loadable.json',
    })

Example output of emitting assets

Can it just emitAssets all the time?

I think another PR has handled this


Retrieving a lost username

Acceptance criteria:
Given that the email is known in the db
Ensure that the associated nick is emailed to the address

For this and #9, we will need to create a<EMAIL_ADDRESS>email address.
It might be simplest to just set it up as a gmail account, and then use the gmail api to send things.

FWIW, we wouldn't need to. We can send emails without having a real registered email address.
The only reason we would need a real mailbox is if we want to support replies. Which we probably won't.

The support should be limited to IRC, GitHub and maybe the dedicated subreddit. If we can avoid setting up an email address, let's do so.


Feature Request

Quick Select
Being able to use a key combination click (ie. Ctrl + Shift + LMB) to select all nodes connected to a node, recursively.

So for example if you have an IF statement, then the clicking on the IF node with this combo will select the IF node + all nodes connected (ie. Compare node) to it as well as connected to them (ie. left condition + right condition), etc. etc.

I've added this feature which will select all linked nodes a64f87f
Keybind
Hold down Left Alt + Click will select all nodes linked to the node you clicked
Hold down Left Alt + Left Ctrl + Click will select all nodes linked to the node you clicked and also keep the previous nodes you clicked selected

Hey, thanks for adding this.
I have noticed a bug where, if you click select (normal selection) any node part of a node tree, and then CTRL + ALT + Click select a node from a different node tree, it will correctly select all the nodes of the new node tree but also incorrectly select the connected nodes of the node tree that still has the previous selection:
https://github.com/blockout22/OverwatchVisualScripting/assets/63469833/a61b73f9-ee6d-4bc0-bda4-268c1f2d847f

I have now fixed that bug

Found a new bug.
If I select one node in a the first tree, then select another in the second tree, and then Ctrl + Alt + Shift click the already selected node on the second tree, it deselects that second tree's node, and the selects the whole first tree because it still has a selection.
https://github.com/blockout22/OverwatchVisualScripting/assets/63469833/b18325a5-0101-41a4-9ada-db18c2b6ce03
Same with multiple trees, it will default to last selection for the quick select.
https://github.com/blockout22/OverwatchVisualScripting/assets/63469833/aa208063-8e55-4ab3-903c-6f3bda756a45

ah I see what is happening, Shift clicking doesn't cause it as it still happens without it
it's because holding ctrl also lets you deselect the node to
I'll continue looking at it and try to find a fix for it

Makes sense


[Feature Request]: Smart code formatting based on context

Describe the feature
It would be super nice if there was a smart AI code formatting option where the AI looks at your codebase and understands your formatting style and then formats the current file based on the style of the rest of the code base. I do not like to use formatters like prettier since they are too opinionated but if the AI could analyze my style and apply the same formatting that would be so 🔥 😍

Can you give me a prompt example where gpt model would style the code? That's ideally the job of formatting utilities or linters like prettier, eslint etc. On the other hand the extension currently doesn't support embeddings of full projects due to token limitations. Perhaps you could give some examples of current capability of these models where you see it'd be helpful in styling your code

For this use-case it might more efficient to use AI to generate a config that matches the formatting you like to use. I'm a big fan of VSCode's "Format document" action which works flexibly with different formatters with different rules. Your original feature may be possible with the GPT-4 32k model, but will be pricey if you're doing this on a lot of files.


[Bug] Build fails due to "babel-plugin-universal-import/universalImport" MODULE_NOT_FOUND

Issue
I have yarn workspaces project.
During react-static build I get following errors:
ERROR in */workspaces/xxx/artifacts/react-static-templates.js
Module not found: Error: Can't resolve 'babel-plugin-universal-import/universalImport' in '*/workspaces/xxx/artifacts'
 @ */workspaces/xxx/artifacts/react-static-templates.js 2:0-78 4:0-78 6:0-78 8:0-78 10:0-78 12:0-77 26:20-36 46:20-37 66:20-37 86:20-37 106:20-37 126:20-37
 @ ../lib/bootstrapTemplates.js
 @ multi ../lib/bootstrapPlugins.js ../lib/bootstrapTemplates.js ../lib/bootstrapApp.js

                => There were ERRORS during the node build stage! :(
                => Fix them and try again!

...

Trace: {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '*/node_modules/react-static/lib/static/exportRoutes.threaded.js'
  ]
}

...

Error: Cannot find module '*/workspaces/xxx/artifacts/static-app.js'
Require stack:
- */node_modules/react-static/lib/static/exportRoutes.threaded.js

- loader.js:902 Function.Module._resolveFilename

react-static depends on babel-plugin-universal-import and it is resolved to<EMAIL_ADDRESS>Workaround
When I go to workspace containing react-static project and do yarn install babel-plugin-universal-import (resolves to<EMAIL_ADDRESS>- build works fine.
Environment
# npx envinfo --system --npmPackages react* --binaries --npmGlobalPackages react* --browsers
zsh: no matches found: react*        # ran both in root workspace and in `react static` workspace - same reuslt

# npx envinfo --system
System:
  OS: macOS 11.6
  CPU: (8) x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
  Memory: 2.47 GB / 16.00 GB
  Shell: 5.8 - /bin/zsh

# yarn -v
1.19.0

# node -v
v14.18.0

# yarn.lock react-static resolution
<EMAIL_ADDRESS>  version "7.6.2"
  resolved "https://registry.yarnpkg.com/react-static/-/react-static-7.6.2.tgz#f860473d5934736899231a1a65ae80f5e861ad47"
  integrity sha512-JQACM+3GgF1vkUH6E6w1k0Qut6IbcfXjU37shGUWM9tIs3F9e/33saXK4G/uSl1kc8qjI+RekAQs/qyjMlUKlg==
  dependencies:
    "@babel/cli" "^7.5.5"
    "@babel/core" "^7.5.5"
    "@babel/plugin-proposal-class-properties" "^7.5.5"
    "@babel/plugin-proposal-export-default-from" "^7.5.2"
    "@babel/plugin-proposal-optional-chaining" "^7.2.0"
    "@babel/plugin-syntax-dynamic-import" "^7.2.0"
    "@babel/plugin-transform-destructuring" "^7.5.0"
    "@babel/plugin-transform-modules-commonjs" "^7.5.0"
    "@babel/plugin-transform-runtime" "^7.5.5"
    "@babel/preset-env" "^7.5.5"
    "@babel/preset-react" "^7.0.0"
    "@babel/preset-stage-0" "^7.0.0"
    "@babel/register" "^7.5.5"
    "@babel/runtime" "^7.5.5"
    "@reach/router" "^1.3.1"
    autoprefixer "^9.7.4"
    axios "^0.21.1"
    babel-core "7.0.0-bridge.0"
    babel-loader "^8.0.6"
    babel-plugin-macros "^2.6.1"
    babel-plugin-transform-react-remove-prop-types "^0.4.24"
    babel-plugin-universal-import "^4.0.0"
    case-sensitive-paths-webpack-plugin "^2.2.0"
    chalk "^2.4.2"
    chokidar "^3.0.2"
    circular-dependency-plugin "^5.2.0"
    cors "^2.8.5"
    css-loader "^2.1.1"
    download-git-repo "^2.0.0"
    extract-css-chunks-webpack-plugin "^4.6.0"
    file-loader "3.0.1"
    fs-extra "^7.0.1"
    git-promise "^1.0.0"
    glob "^7.1.4"
    gunzip-maybe "^1.4.1"
    html-webpack-plugin "^3.2.0"
    inquirer "^6.5.1"
    inquirer-autocomplete-prompt "^1.0.1"
    intersection-observer "^0.7.0"
    jsesc "^2.5.2"
    match-sorter "^3.1.1"
    minimist "^1.2.0"
    mutation-observer "^1.0.3"
    optimize-css-assets-webpack-plugin "^5.0.3"
    portfinder "^1.0.21"
    postcss-flexbugs-fixes "^4.1.0"
    postcss-loader "^3.0.0"
    pretty-error "^2.1.1"
    progress "^2.0.3"
    prop-types "^15.7.2"
    raf "^3.4.1"
    raw-loader "^3.1.0"
    react-helmet "^6.1.0"
    react-universal-component "^4.0.0"
    resolve-from "^5.0.0"
    serve "^11.1.0"
    shorthash "^0.0.2"
    slash "^2.0.0"
    socket.io "^2.2.0"
    socket.io-client "^2.2.0"
    style-loader "0.23.1"
    swimmer "^1.4.0"
    tar-fs "^2.0.0"
    terser-webpack-plugin "^1.4.1"
    upath "^1.1.2"
    url-loader "^2.1.0"
    webpack "^4.39.2"
    webpack-bundle-analyzer "^3.4.1"
    webpack-dev-server "^3.8.0"
    webpack-flush-chunks "^2.0.3"
    webpack-node-externals "^1.7.2"

Try add it babel-plugin-universal-import in the package, not in the workspace.


Add support link

Add Support link in sidebar, and fix icon for Users

@kldavis4 This is a nice feature and would allow me to deploy this for anyone who wants a new website instead of bloated WordPress. I hope this gets merged. Any idea what's blocking this?


guzzle php mock response content

I want to mock a response to the guzzle request:
 $response = new Response(200, ['X-Foo' => 'Bar']);

 //how do I set content of $response to--> "some mocked content"

 $client = Mockery::mock('GuzzleHttp\Client');
 $client->shouldReceive('get')->once()->andReturn($response);

I noticed I need to add as third parameter the interface:
 GuzzleHttp\Stream\StreamInterface

but there are so many implementations of it, and I want to return a simple string...
Any ideas?

After hours of searching I found a solution: https://laracasts.com/discuss/channels/testing/mocking-the-guzllehttpclient-class-is-not-working


fet(custom-scripts): added custom scripts support (#1425)

run tests

Pull Request Test Coverage Report for Build 1751

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.003%) to 53.53%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/app/shared/services/auth.service.ts
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/app/shared/services/auth.service.ts
1
46.15%

Totals

Change from base Build 1749:
-0.003%

Covered Lines:
9522

Relevant Lines:
15785

💛  - Coveralls

run tests

run tests

run tests

run tests


Add @with_error, remove @generate_error_functions

@generate_error_functions was not a great macro: it required adding new names to a line every time a diagnostic is added, it was dealing with several variables at the same time, and could not be used outside of its scope of definition and/or called twice.
@with_error accomplishes a the same goals as
@generate_error_functions without the problems. The only difference is that now compute functions have to be decorated.

Merging bypassing requirements because the Buildkite error is due to #725


Added cube root Operator

Closes Issue: https://github.com/Redempt/Crunch/issues/1
Added the cube root operator, I wanted to add an Operator that allows you to root by any power, e.g. root(x, 8) but wasnt sure how to do that with the current codebase

Yeah, my ide auto formats stuff, ill change that back

welp, I undid the method references, but looks like my ide automatically fixes the indents and I cba to figure out how to turn that off, so :shrug: fix it yourself if u want, idk

Good enough I guess, thanks for the PR


Today´s Timerange shows the whole week

When using the Grafana Timerange Today the calender shows the whole week. In our usecase its hard to read the entry titels. It would be better if there was a possiblity to show only one day when the timerange Today is selected

Rather than a Day view, I've been thinking about a "feed" view, where all events are laid out vertically. Google Calendar calls this view "Schedule". For time intervals that are less than a day, this would be pretty much equal to a Day view.
I'll add this to the backlog, but I'll probably be prioritizing issues related to the monthly view. If anyone wants to work on this sooner, I'd be happy to help.

The described feed view sounds promising!


Improve client library test performance

Per discussion with @SahilTikale @naved001 @kylehogan , we'd like to refactor tests to be able to operate in parallel.
Right now this includes:

[ ] Client library tests can spawn a different web server for each test, each on its own port. Picking a port could be done either sequentially or randomly, first checking to see if the port is already bound to.
[ ] Maybe keystone (I've heard @zenhack has ideas on this)

I started some work on this on a branch, but it's blocked by the outright failures we're having. The basic notion I had was to split up our tests into a larger matrix, so e.g. the keystone and apache tests run separately from tests/unit, and thus all of that installation doesn't need to happen in unit, and fewer tests need to be run in those cases.

Tests running with postgres are currently unable to run in parallel due to sharing a single DB.
To overcome this (allowing us to run unit tests in parallel with py.test -n auto --boxed), each worker process could have its own DB named after its worker name. Pytest-xdist's docs describe how to do this.

I'm going to submit a PR doing the keystone stuff (and some other componentization); I started working on it while we were fussing with the transient failures, but was blocked on the fix.

So, at this point tests/unit/client.py even on sqlite3 is taking longer than the rest of the tests put together -- including the keystone test and apache, and their setup steps. I'm going to do the keystone breakout anyway, since I think it will pay off once we fix that, but this is just dumb -- there's something deeper going on than "we should start parallelizing," those tests should not be that slow.

The time is being eaten up by populate_server() -- it takes about 40 seconds to run on my laptop.

...which amounts to about  0.67 requests per second. I'm also getting a whole bunch of this:
connectionpool.py          395 DEBUG    "PUT /switch/mock-01/port/gi1/0/3 HTTP/1.1" 200 0
connectionpool.py          248 INFO     Resetting dropped connection: <IP_ADDRESS>
connectionpool.py          395 DEBUG    "POST /switch/mock-01/port/gi1/0/3/connect_nic HTTP/1.1" 200 0
connectionpool.py          248 INFO     Resetting dropped connection: <IP_ADDRESS>
connectionpool.py          395 DEBUG    "PUT /switch/mock-01/port/gi1/0/4 HTTP/1.1" 200 0
connectionpool.py          248 INFO     Resetting dropped connection: <IP_ADDRESS>
connectionpool.py          395 DEBUG    "POST /switch/mock-01/port/gi1/0/4/connect_nic HTTP/1.1" 200 0
connectionpool.py          248 INFO     Resetting dropped connection: <IP_ADDRESS>
connectionpool.py          395 DEBUG    "PUT /switch/mock-01/port/gi1/0/5 HTTP/1.1" 200 0
connectionpool.py          248 INFO     Resetting dropped connection: <IP_ADDRESS>
connectionpool.py          395 DEBUG    "POST /switch/mock-01/port/gi1/0/5/connect_nic HTTP/1.1" 200 0
connectionpool.py          248 INFO     Resetting dropped connection: <IP_ADDRESS>
connectionpool.py          395 DEBUG    "PUT /switch/mock-01/port/gi1/0/6 HTTP/1.1" 200 0
connectionpool.py          248 INFO     Resetting dropped connection: <IP_ADDRESS>
connectionpool.py          395 DEBUG    "POST /switch/mock-01/port/gi1/0/6/connect_nic HTTP/1.1" 200 0
connectionpool.py          248 INFO     Resetting dropped connection: <IP_ADDRESS>
connectionpool.py          395 DEBUG    "PUT /switch/mock-01/port/gi1/0/7 HTTP/1.1" 200 0
connectionpool.py          248 INFO     Resetting dropped connection: <IP_ADDRESS>
connectionpool.py          395 DEBUG    "POST /switch/mock-01/port/gi1/0/7/connect_nic HTTP/1.1" 200 0
connectionpool.py          248 INFO     Resetting dropped connection: <IP_ADDRESS>
connectionpool.py          395 DEBUG    "PUT /switch/mock-01/port/gi1/0/8 HTTP/1.1" 200 0
connectionpool.py          248 INFO     Resetting dropped connection: <IP_ADDRESS>
connectionpool.py          395 DEBUG    "PUT /project/proj-01 HTTP/1.1" 409 68
connectionpool.py          248 INFO     Resetting dropped connection: <IP_ADDRESS>
connectionpool.py          395 DEBUG    "PUT /project/proj-02 HTTP/1.1" 409 68
connectionpool.py          248 INFO     Resetting dropped connection: <IP_ADDRESS>
connectionpool.py          395 DEBUG    "PUT /project/proj-03 HTTP/1.1" 409 68
connectionpool.py          248 INFO     Resetting dropped connection: <IP_ADDRESS>
connectionpool.py          395 DEBUG    "POST /project/proj-01/connect_node HTTP/1.1" 200 0
connectionpool.py          248 INFO     Resetting dropped connection: <IP_ADDRESS>
connectionpool.py          395 DEBUG    "POST /project/proj-02/connect_node HTTP/1.1" 200 0
connectionpool.py          248 INFO     Resetting dropped connection: <IP_ADDRESS>
connectionpool.py          395 DEBUG    "POST /project/proj-02/connect_node HTTP/1.1" 200 0
connectionpool.py          248 INFO     Resetting dropped connection: <IP_ADDRESS>
connectionpool.py          395 DEBUG    "POST /project/proj-03/connect_node HTTP/1.1" 200 0
connectionpool.py          248 INFO     Resetting dropped connection: <IP_ADDRESS>

There is likely something odd going on with the way HTTP requests are being handled.
I will point out that I was against spinning up an actual server for these tests.  I was left out of the discussion -- you guys had it off-line without me, despite me being the person who raised the concern in the first place. I think I was just too exhausted by the whole thing to argue anymore.
I still think we shouldn't be spinning up a full web server -- the functionality that is being tested doesn't need it, and though it shouldn't have this much of an effect it is going to slow things down. In addition to real network activity, it means we can't use an in-memory db, so we're actually hitting the disk for each requests -- probably even doing a sync() on commit.
I don't know that I think debugging a performance problem with a dev server that isn't supposed to be fast in the first place is worthwhile -- if we want benchmarks we should run them against apache.

Re: running a full server, there was a debate (I was on the side of using flask's built-in server), and the vote was to use the dev server. @pjd-nu and @okrieg felt that it was necessary to quickly make a decision, so we did it at one of the HIL meetings.
Given the time I spent debugging/fixing this as part of #774, I'm tempted to to revert the client library tests if we can't stabilize them soon.

+1 for reverting if we can't solve this soon. I'd also like to get the dev server out of there one way or another -- it's adding complexity (and a big performance hit, even in the theoretical case where there's not something funny going on) without much tangible benefit.

FYI - we can treat this PR as a general let's improve client library test performance.
The client library tests caused Travis CI to go from ~15 mins to about an hour

I'd like to re-open the question of whether it's a good idea to actually spin up a web server for the client lib tests. I still maintain it isn't. But given these problems it seems worth discussing again (on the record this time...)
//cc @henn, @okrieg, @pjd-nu

@SahilTikale - Any updates on this?

@henn from the last email I was under an impression that we have frozen making of new PRs since we want to make a shift from haas to hil in our codebase. Therefore I was waiting for that to happen before I could submit PR to improve the efficiency of the tests. Let me know if that is not the case.

The freeze was as of tomorrow. But at this point it's probably a bot late.
Also, for the record, at the HIL meeting today we discussed and agreed that we don't need to spin up a real web server in the client tests.

@zenhack mentioned that we should not have a full fledged web server for these tests.
@henn mentioned moving this tests along with integrations tests.
I have a version of the current tests run faster than these tests, but I will not make the PR until #805 is resolved. Since there are difference of opinions on what approach is best, we should discuss it out here.
@okrieg @pjd-nu

So, to clarify, at the meeting I raised the point that we've had different discussions with different groups of people and settled on different things; we were starting another one and I think it's proven a waste of time to have that conversation without everyone being able to participate, which means doing it here.
At the meeting I called into two weeks ago I thought we'd settled on not needing a web server for these at all. I gathered from the meeting today that at some point folks decided moving these into the integration tests would make sense? Unfortunately I wasn't around for the discussion/rationale behind that. I seem to recall @knikolla pointing out somewhere (probably on the original PR?) that these really weren't integration tests; they are simple unit tests.
@henn, can you fill me in on the reasoning here?

Ok, so here goes my $0.02:
I agree that the improving CI test is prioritized right after the renaming PR. This is the tech debt we have to pay because back in time we just want the client lib to done. We don't want to small fixes that will break other things or some hacking just to ease the pain. What we want is to reduce the CI running time to a reasonable time frame. I estimate it to be a job that will consume quite some time, and of cause afterwards we need some explicit requirements on the CI part.
@zenhack @henn @SahilTikale Do we need to come to some consensus next time?

I was actively against the current design at the time; my opinion re: the web server thing basically hasn't changed. The decision was made at an in-person meeting that was not recorded, and I was just out of steam on that PR; I didn't have the energy to protest anymore. If I wasn't so exhausted, I probably would have made more of a stink about it. When stuff turned out to be outright broken once we merged it, I was pissed. I drafted a number of comments that I had the good sense not to actually send.
I've really been pushing for doing as much as possible on the bug tracker; I think if we can agree that that kind of decision has to be hashed out here, we won't have an issue.
Also, that PR was a really pathological failure of process -- there were many, many dropped balls. Part of the problem is that it was just enormous, and had that we'd allowed it to be worked on for a very long time without real interaction with other developers. by the time I really dug into it, the patch had rather a lot of technical debt.
As far as how we go about fixing this, The lowest-hanging fruit is getting that web server out of there. Instead, we should use mock objects. Concrete benefits of this approach:

Most importantly, I actually did some measurements, and the time is all going in to the server setup and/or network traffic. So cutting all of that out should have a big impact.
Also, killing the web server will allow us to use an in-memory database for the sqlite run, like all of the other tests. This will improve things somewhat, though it won't affect the postgres run.
It will be generally simpler; per my comments above, these are unit tests; they're supposed to focus on a specific chunk of the code.

To make this happen, we'd need a mock object to use as an HTTPClient. This is in large part the motivation for #777.

these are unit tests; they're supposed to focus on a specific chunk of the code.

This might have been said before, but @knikolla once told me about this neat requests-mock library to mock out the HTTP requests. If all we want is unit tests for the client library, then we can use that instead of a web server, right?

Yeah, that might be even better.

So I spent a bit of time poking at requests-mock; it looks like it would be a big chunk of work to move this over to that, since we'd actually have to spec out the responses for each test in detail.
My inclination is to do the thing I outlined before (fix #777, then use a flask based mock object). If you want to put a label on it "functional testing" might be better than unit; this is true for a lot of what we have in the tests/unit/ directory. But the key thing is: this performance issue is really crippling as a developer, and I think this is the easiest way forward. I also that whatever you call these tests, they're mostly sensible, if we can fix the perf issue.

I agree with @zenhack.

#827 fixes this.

#827 didn't parallelize the tests, even though it did reduce the time significantly.
Re-opening for that purpose.


Correcting config_parse_file()

The compiler gave me this error:
src/configfile.c:1232:8: error: 's.size' may be used uninitialized in this function [-Werror=maybe-uninitialized]
if (s.size == 0) /* the file was empty, nothing to parse */

I think this way the generated code will be smaller - it's the stream_open() that should check the stat->size anyway...
Also, we are calling stream_close() even when stream_open() did fail...

Sorry for my english, for my weird coding style and for my stupidness if I'm doing anything wrong here...

Thanks for reporting the read of an uninitialized variable!
I fixed it by making sure no error gets returned for empty files - see def17b2925f5e8db74a7dbd93448726adac41e0c


Tutorial doesn't work on iOS17.

Per Mattermost guidelines, GitHub issues are for bug reports: http://www.mattermost.org/filing-issues/.
For troubleshooting see: http://forum.mattermost.org/.
For feature proposals see: http://www.mattermost.org/feature-requests/
If you've found a bug--something appears unintentional--please follow these steps:

Confirm you’re filing a new issue. Search existing tickets in Jira to ensure that the ticket does not already exist.
Confirm your issue does not involve security. Otherwise, please see our Responsible Disclosure Policy.
File a new issue using the format below. Mattermost will confirm steps to reproduce and file in Jira, or ask for more details if there is trouble reproducing it. If there's already an existing bug in Jira, it will be linked back to the GitHub issue so you can track when it gets fixed.

Summary
Tutorial doesn't work on iOS17.
Environment Information

Device Name: iphone 12 pro
OS Version:  17.0.2
Mattermost App Version: 2.8.0
Mattermost Server Version: 8.1

Steps to reproduce

View a list of members
Tutorials containing the message 'Long-press on an item to view a user's profile' did not render correctly

Expected behavior
Tutorials containing the message 'Long-press on an item to view a user's profile' should render correctly
Observed behavior (that appears unintentional)
Not rendered, does not recognize any touch. The app is dead
But, works fine on Ios16
Possible fixes
Appears to be a rendering issue in Ios17

Opened https://mattermost.atlassian.net/browse/MM-54575.

I'd tried to reproduce this bug on iOS 17.0.2, but the flow is seems like working as expected. Steps I followed:

Navigated to the members list
Tutorial dialog containing long-press on an item to view a user's profile shows up
Clicked on random point on the screen to hide/disable the tutorial dialog
Then long-pressed on few member to view the user's profile info

https://github.com/mattermost/mattermost-mobile/assets/28022451/9d28ee95-a994-4d86-b6d4-85d27185b1b9

@adityasonel Have you tested it on 17.0.3? I updated to 17.0.3 and did a clean install of mattermost and it reproduces.

This should be fixed by #7599


Contributor added!!

Hey, I added myself as a contributor in data/contributors.js

Please remove the contributor.js.swp file and Update the PR also add your data to the end of the list. @AKACHI-4

okay @Rajdip019


Publish public part of signing key to verify downloads

Would be nice to verify the provided GPG signature tf-summarize_SHA256SUMS.sig but I can't seem to find the public key.
$ gpg --verify tf-summarize_SHA256SUMS.sig
gpg: assuming signed data in 'tf-summarize_SHA256SUMS'
gpg: Signature made So 22 Okt 2023 18:52:09 CEST
gpg:                using RSA key 810C11685E2C731839DD114953FF49669670DBD6
gpg: Can't check signature: No public key

Any updates on this?


Node.js bindings: Add JS bindings for SPI

This patch contains the native and highlevel JavaScript bindings for SPI.

@gabrielschulhof @barbieri could you please review this?


use promise.all

Refactor fetch function to use Promise.all

Exist any issue related to this PR's?


Add JSON support

JSON has been implemented in third party repo. Maybe merge this into upstream?

Yes, it's something I talk about with @stevenh last year, he saids he had pinged the owner for a pull request, so if today nothing was done, it means we must probably do it ourselves. If I remember, this repository (eXprojects) is not a fork from a repo but from a tarball archive, so this repo is missing some history, so there is some work to do by hand.
This is something I want to do since many months but I've never found the time to do it, cf. https://github.com/XQF/xqf/issues/12 . :wink:

See #13.


Azure DBaaS Snapshot Backups

Hi Team,
I would like to schedule the daily snapshot backups for the DBaaS MySQL/PostgreSQL databases.
But I do not find this feature yet and highly recommend for it.

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

ID: 28ded65a-1b0a-f610-a3ad-3812589cc005
Version Independent ID: 3fdac72c-6c42-e572-3822-c77ea9002e0e
Content: Use incremental snapshots for backup and recovery of unmanaged Azure Windows VM disks
Content Source: articles/virtual-machines/windows/incremental-snapshots.md
Service: virtual-machines-windows
GitHub Login: @aungoo-msft
Microsoft Alias: aungoo

@atullalwani Backup and restore can be configured for Databases. Please check this link.
Are you looking for an option to take a backup of the backup and store it in a separate place for long term retention?

@jakaruna-MSFT Thanks for the update 👍 . Can we see the full weekly/ differential backups in the portal for a specific DBaaS system. Is there any other way I can create a current manual snapshot of the database system?

Its not possible right now.
Service takes Full backups daily and snapshots every 5 minutes.
There is a feedback here which is asking for Portal access for the backup configuration. Please upvote there.
If you want to take a backup and persist it outside of the service, Then we need to take a mysql dump and store. Please refer to this feedback's comment.  You can add a read replica (not for basic pricing tier) if you have performance issues while running mysql dump.
You can also submit a feedback here  if you need other features.

@atullalwani is there any update

@jakaruna-MSFT : Thank you for the information. We can close this thread. Please do notify me once manual snapshots are made available. I have upvoted in the above link. 👍


Non-unique-files fix for Videogrid WOH

There are several problems with multiple instances of the videogrid operation running at the same time, e.g. causing event B to have the same output video as event A or output videos appearing too short. This PR attempts to fix these problems by improving on the passing and naming of files.

Now passes track objects instead of absolute track paths to the service, so that the service can copy files into its own workspace.
Deletes copied files when done.
Gives output files in service unique names (by adding the current job id to the file name).

To test this pull request:

An example workflow could look like: test-video-grid.zip
The videogrid operation requires a SMIL file. Other than writing one yourself, the (probably) easiest way to generate one is to use the /ingest/addPartialTrack API, which automatically generates one for you. (I.e. create an MP with /ingest/createMediaPackage, add tracks to it with /ingest/AddPartialTrack and then start a workflow on it with /ingest/ingest/test-video-grid)

Your pull request should…

[ ] have a concise title
[ ] close an accompanying issue if one exists
[ ] be against the correct branch (features can only go into develop)
[ ] include migration scripts and documentation, if appropriate
[ ] pass automated testing
[ ] have a clean commit history
[ ] have proper commit messages (title and body) for all commits
[ ] have appropriate tags applied

Do you have an example workflow here we can test with?

Do you have an example workflow here we can test with?

I've updated the first comment with an example workflow.


minimum value of component chi set to 1e-4

For some special cases, the default minimum value of  chi (1e-4)  can be too low, e.g. inflation.
This value is currently set up (hard-coded) in CCZ4/PositiveChiAndAlpha.hpp
It has been proposed that this value could be established in the params files (and therefore, read by GRChomboCore/SimulationParametersBase.hpp).
Note that this may need to update the unit test accordingly.

Fixed in #62. @cjoana can I ask you to review and see if this works for you?


Structural recursion: wrong motive generated

Prerequisites
Please put an X between the brackets as you perform the following steps:

[X] Check that your issue is not already filed:
https://github.com/leanprover/lean4/issues
[X] Reduce the issue to a minimal, self-contained, reproducible test case.
Avoid dependencies to Mathlib or Batteries.
[X] Test your test case against the latest nightly release, for example on
https://live.lean-lang.org/#project=lean-nightly
(You can also use the settings there to switch to “Lean nightly”)

Description
Structural recursion may fail due to a badly formed motive in a brecOn call
Context
I encountered this issue when trying to formalise a theory of signatures for inductive types.
Steps to Reproduce
MWE:
inductive Tyₛ (l : List Unit): Type
| U : Tyₛ l
open Tyₛ

inductive Varₚ (d : Unit): List Unit → Type
| vz : Varₚ d [d']
| vs : Varₚ d l → Varₚ d (Bₛ :: l)

inductive Tmₛ {l : List Unit}: Tyₛ l → Unit → Type 1
| arr   : (T : Type) → Tmₛ A d → Tmₛ A d
| param : Varₚ d l → Tmₛ A d → Tmₛ (@U l) d

def TmₛA {l : List Unit} {d : Unit} {Aₛ : Tyₛ l} (t : Tmₛ Aₛ d): Type :=
match t with
  | .arr dom cd =>
    let cd := TmₛA cd
    dom → cd
  | _ => sorry
termination_by structural t

Expected behavior: The function gets accepted.
Actual behavior: The following error pops up:
failed to infer structural recursion:
Cannot use parameter t:
  application type mismatch
    @Tmₛ.brecOn l fun {d} {Aₛ} t => Type
  argument
    fun {d} {Aₛ} t => Type
  has type
    {d : Unit} → {Aₛ : Tyₛ l} → Tmₛ Aₛ d → Type 1 : Type 2
  but is expected to have type
    (a : Tyₛ l) → (a_1 : Unit) → Tmₛ a a_1 → Type 1 : Type 2

Versions
Lean 4.15.0-nightly-2024-11-08 Target: x86_64-unknown-linux-gnu
Additional Information
The issue seems to be that the motive generated for the recursive call puts arguments in the wrong order. Changing the order of arguments in the signature of Tmₛ fixes things:
def TmₛA {l : List Unit} {Aₛ : Tyₛ l} {d : Unit} (t : Tmₛ Aₛ d): Type :=
match t with
  | .arr dom cd =>
    let cd := TmₛA cd
    dom → cd
  | _ => sorry
termination_by structural t
-- works

Impact
Add :+1: to issues you consider important. If others are impacted by this issue, please ask them to add :+1: to it.

Ok, in general there is code there for this kind of reshuffling of arguments, but it seems to be not tested enough. Maybe the tests only had one level of indices or so. I can have a look next week.

Mostly a straight-forward fix, it sees: https://github.com/leanprover/lean4/pull/6116


messages between fleet adapter and fleet manager

hi,
can i verify why is it that the rmf core integration diagram (https://github.com/osrf/rmf_core/blob/master/docs/rmf_core_integration_diagram.png) specify only 4 messages between fleet adapter and fleet manager? i would thought there are more than these 4 messages because it lacks:

the message to report to traffic schedule database the itineraries of the fleet
the message to report the position of the fleet
as pointed out in the 4 levels of control for fleet, these two messages are necessary.

As was pointed out, there are more msgs in existence between the fleet_adapters and rmf_core (rmf_traffic_msgs). These msgs will mainly handle the negotiation and update of the traffic schedule databases. Also, according to the diagram, fleet_state msg is used to report the fleet position to the fleet_adapter.

That diagram is out of date (we've replaced those message interfaces with an explicit C++ API that's discussed somewhat here), but the basic idea is exactly as @tanyouliang95 described: The fleet adapter API will do most of the heavy lifting for communicating with the rest of RMF, and the individual fleets just need to satisfy a much simpler set of inputs and outputs than what's required for the overall traffic scheduling and negotiation system.

thanks both for the replies. Is there any sample code or materials that could help me understand how to implement a fleet adapter and the interfacing portion of the fleet manager to the fleet adapter? Thanks.

Here's one example of a "Full Control" fleet adapter that uses a ROS2 message API to interface with the rmf_fleet_adapter API. I don't recommend using the ROS2 message API of that fleet adapter because it's been deprecated due to not being expressive enough in various corner cases. But it may serve as a useful example for how to use the fleet adapter API.
There's a fleet adapter in development here that integrates with the MiR100 API using the fleet adapter Python bindings. This fleet adapter is still under review and isn't tested yet, but the general idea behind it may be a good reference.
There aren't any examples that use the traffic light API yet. For the traffic light we're currently working on a mockup traffic light fleet manager for testing purposes, and then we'll begin integrating it with some real-world fleet manager APIs.

Thanks for the reply. It seems that the communication between fleet adapter and fleet manager is carefully managed to keep it simple and generic using the 4 rmf messages. In that case, can i say that fleet adapter is pretty much generic and can be reused by another new fleet vendor with slight modification on the following steps listed out in the https://osrf.github.io/ros2multirobotbook/integration_fleets.html :

step 1 no need because reuse
step 2 if no difference in approach to read runtime param, not required to change.
step 3 loading the specific graph of fleet for the new vendor
step 4 no need because reuse
step 5 adding fleet of the new vendor
step 6 no change required because the messages comms with fleet manager are generic rmf messages
step 7 make changes to add new vendor's fleet
step 8 no change required because the messages comms with fleet manager are generic rmf messages

The basic workflow of developing a fleet adapter is the following:
1.Create an application that links to the rmf_fleet_adapter library.
2.Have the application read in runtime parameters in whatever way is desired (e.g. command line arguments, configuration file, ROS parameters, REST API calls, environment variables, etc).
3.Construct a route graph for each fleet that this application is providing the adapter for (a single adapter application can service any number of fleets), and/or parse the route graph from a YAML file using the rmf_fleet_adapter::agv::parse_graph utility.
4.Instantiate an rmf_fleet_adapter::agv::Adapter using Adapter::make(~) or Adapter::init_and_make(~).
5.Add the fleets that the application will be responsible for adapting, and save the rmf_fleet_adapter::agv::FleetUpdateHandlePtr instances that are passed back.
6.Implement the RobotCommandHandle class for the fleet manager API that is being adapted.
7.Add the robots that the adapter is responsible for controlling. The robots can be added based on the startup configuration, or they can be dynamically added during runtime as they are discovered over the fleet manager API (or both).

When adding a robot, you will need to create a new instance of the custom RobotCommandHandle that you implemented.
You will also need to provide a callback that will be triggered when the adapter is finished registering the robot. This callback will provide you with a new RobotUpdateHandle for your robot. It is imperative to save this update handle so you can use it to update the robot's position over time.
8.As new information arrives from the fleet manager API, use the collection of RobotUpdateHandle classes to keep the adapter up-to-date on the robots' positions.

If you're suggesting copy/pasting the source code of an existing fleet adapter and then transplanting a new fleet's API into it, then sure, that's a perfectly acceptable thing to do, as long as the source code you're copying has a permissive license (everything from OSRC uses Apache-2.0, which is permissive) and you keep a copy of the original license. You can add your own license (including a closed-source license) on top of the permissive license, but legally speaking the permissive license of the code you're copying must remain with the source code, even if the permissive license will be "overpowered" by a closed-source license.

@mxgrey thanks for the reply.
Actually i am coming for the angle of the work involved for a vendor to implement their own version of fleet adapter even if they have a workable version of the fleet adapter provided for them. Because the vendor is using a different fleet and running in a different site, using a different fleet manager.
Also, I am curious to confirm that there should be very minimum or none effort to switch fleet manager since the communication between fleet adapter and fleet manager is in ROS 2 using standard RMF defined messages (4 of them).

i am coming for the angle of the work involved for a vendor to implement their own version of fleet adapter even if they have a workable version of the fleet adapter provided for them.

I'm not sure how this is different from what I described, so I may need you to elaborate on this.

there should be very minimum or none effort to switch fleet manager since the communication between fleet adapter and fleet manager is in ROS 2 using standard RMF defined messages (4 of them).

If you're talking about the messages here in rmf_fleet_msgs, that API is considered deprecated. I would generally discourage using it because it has some known edge cases that cause undesirable behavior. It does mostly work and it is usable for demo purposes, but it may exhibit some intended behavior.
Instead for anything more important than a basic demo, I recommend using the C++ API that's described here. It may involve some more effort, but it will give more reliable results.

Closing as this is not an issue. To continue discussing this topic, please open a discussion.


fix: github api limit rate

fix https://github.com/biomejs/biome-vscode/issues/56

Hey @zoolsher,
Thanks for the PR, but ultimately I decided to go in a slightly different direction to fix this issue, notably I added logging.
Cheers, and thanks again for reporting.


Drop support for Django 3.2

Description

Django 3.2's EOL was passed last month (April 1st); see Django's supported versions.
Related Issue

None
Motivation and Context

Removing support for dependencies for which development has stopped.
How Has This Been Tested?

See the GitHub Actions test build.
Screenshots (if appropriate):
Types of changes

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

Checklist:

[x] I have run the pre-commit run command to format and lint.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] I have added my name and/or github handle to AUTHORS.rst
[x] I have added my change to CHANGES.rst
[x] All new and existing tests passed.

@tim-schilling Are you available to review this? I'm planning on opening a release PR after merging this 🙂

I'll to try to make time tomorrow morning, but no promises. Feel free to merge and release without it though!

Great! No worries if it turns out otherwise :)
I don't have the administrative permissions to merge without a review (assuming that's what you meant), but I can try requesting reviews from some of the other Jazzband members 🙂

If you have time, I'd suggest doing two releases. The first with all of the changes before dropping 3.2. Then another version that drops 3.2. That way anyone using 3.2 still can utilize the latest changes.

Nice thinking, let's do that! I'll open a release PR for 3.6.0 before merging this 🙂
We can do 3.7.0 (or 3.6.1? 4.0.0? The version history's relationship with semantic versioning seems slightly inconsistent 😅) with the changes from this PR - though I'm not sure that I see the usefulness of a release that only drops a dependency version used in our CI code..? 🤔 (..apart from removing the asgiref>=3.6 installation requirement, I guess)

Eh, I think minor version changes are fine for both, so 3.7.


Error 1527 when parsing an array with cluster containing empty cluster and scalar

Reported here.
Here is the reproducer:
Error 1527 JKI JSON.vi

{
    "array": [
        {
            "cluster": {
                "empty_cluster": {}
            },
            "scalar": 0
        }
    ]
}

@nate-moehring would you (or anyone else) be interested in looking into this issue?

Create fork/branch for a Pull Request
Add reproducer as a Caraya test with Issue #51 in VI name
Fix the bug and keep all unit tests passing :)

Sure, I can help with this, but first help me understand what the expected behavior would be.  If you wired this to a Variant to Data node, the type cluster constant would need to have both 'empty_cluster' and 'cluster' elements omitted, otherwise the conversion would fail.  Does SlippinJimmy know that these elements will always be empty?  If not, then this error seems appropriate (though vague).  If it's sometimes populated in jsonText, then the _type_cluster would need to be fully defined.  Is there a way to specify optional (non-critical elements) of a json cluster such that isn't doesn't break the unflatten?  If he does know that 'empty_cluster' is always empty, which therefore implies that 'cluster' will also be empty, then that seems like a pretty tough case to handle.
Workaround:  Using the Path input on Native JSON Unflatten from String nodes to decode select items from the JSON is super easy and powerful.

@nate-moehring - that’s a great question.
I noticed that parsing this, JSON seems to work OK (Meaning: No Error).
        {
            "cluster": {
                "empty_cluster": {}
            },
            "scalar": 0
        }

The error seems to occur in the specific case where this is an element of an array.
I’m having front of my computer for most of today, but I’m thinking we should look at what the variant structure looks like for the similar, “working” cases.
A first/incremental step forward probably looks like “fixing” the inconsistency by getting the error to go away so that the test case outputs a variant with an array with one element that’s equivalent to the data produced from that second example JSON snippet.
Of course, the Devil‘s going to get into the details around how flattened data is handled. LabVIEW Gets a bit with zero element clusters.
Where we may end up with this is: returning a null variant in liu of empty clusters ({}).
I’ll think of a bit more about this once I have a chance to get in front of the computer later this weekend.

@nate-moehring here's an example showing the desired output.  The upper/working code shows how if we remove the outer array, we can successfully convert it to variant and then use the OpenG Variant library to make it an element of a 1D Array.
Example VI: Issue 51 - Array of Cluster with Element of Empty Cluster.vi
Example Screenshot:

I made some progress tonight.  I used your repro to create a test VI (see my branch), and then found that I could fix this particular bug by removing a single node, but this then breaks other tests:

On the left side of the To Variant it has all the type-info, but on the right side it's like the type info gets lost, even though the data is preserved.  (Yes, Show Type is enabled)

This repro shows the problem.
Errored Variant.zip

@nate-moehring Yes, I would call this a LabVIEW bug -- nice work catching it!
Yes, let's report it to NI. Would you be willing to do that and report back here with an NI Bug ID #?
Regarding a short-term work-around, I'd be curious to see which cases now fail. Maybe the extra layer of variant wrapping in Parse Value could be removed and (whatever it was attempting to address could be) done in a different way.
Also, please create a pull request from your own fork/branch, since that'll make it easy for me to check it out and fiddle in there with you, if needed.

@nate-moehring actually, I'll ping LabVIEW R&D abound this, directly, and see if they can get it into the system.

@jimkring Pull request: https://github.com/JKISoftware/JKI-JSON-Serialization/pull/52

Keeping an interested eye on this.
I used to rely on this library because jsonText does not accept deserialization without specifying type, but have since made a jsonText wrapper that supports it.
I'm attaching it here for anyone wanting to reverse engineer it and see how it could fix this Parser.
(VI depends on jsonText and LVOS' Data Manipulation)
JSON text to Variant (Void).zip

Thanks @francois-normandin .  I've poked around with the libraries you provided, man that's a lot of code.  In some ways it's more simple code, which is good, and it seems like it might handle more cases than the JKI library, but I'd have a hard time creating a side-by-side feature comparison list.
It's true that your library parses the problematic json just fine.  It's also true that the array of variants that gets created just prior to being reshaped into a variant array works just fine.  And an element of that array can be flattened and unflattened just fine, unless I force it through a To Variant like what is happening in Parse Value, then I see the same Error 1527.
My conclusion thus far is that I need to remove the To Variant from the JKI Parse Value begin-array case, and then look to the non-array cases of JSON text to Variant (Void) to help address the many resulting unit test errors.

My conclusion thus far is that I need to remove the To Variant from the JKI Parse Value begin-array case, and then ... address the many resulting unit test errors.

I should have some time to work on this next week.


Enable "disabling" of container image version checks

Is your feature request related to a problem? Please describe.
Whilst it's great Portainer now shows if a container if not up to date (red circle) it requires DNS calls out to do so.  If your DNS service is running in a container, or is down, portainer effectively stalls on the "Container" screen until checks time out.
I suspect it's the web UI rather than Portainer, as if I can see a container link and copy it, close the window and open a new window with the direct container link, it will open.

Describe alternatives you've considered
I have CWATCH, WatchTower is available - but when I need to restart containers using portainer in a troubled network, this causes delays :)

This can be disabled on a per-environment basis under either Host | Setup for Docker Standalone environments, or Swarm | Setup for Docker Swarm environments.

Thanks for confirming, I was looking more generally under "main settings" rather than on a per host basis :)


Download Data

Hi all!
The download tab is a key component for our Geoportal. From what I see the download tab uses a list of layers published to ArcGIS Server (independently from Geoportal). Is there a way to manage the Geoportal's "data to download" directly from our Geoportal?
Thank you,
Alex

hi Alex, not easily. as you correctly concluded, the list of layers comes from the clip-zip-ship geoprocessing tool that is published to ArcGIS Server.
what you could do (if you're into writing python tools) is write a new geoprocessing tool that accepts the extent and such as inputs, as well as one or more layers from a remote map service/feature service together with the URL to that service. The GP tool would then send the request to the remote web service, get the subset data and then do some local processing to reproject and such. Not rocket science, but with different service types, not entirely trivial either.


Move expansion of Canvas-Specific control type into INameResolver from IExternalControl

This change is a breaking-internals change, but it allows for safer testing of ongoing analysis improvements. It should have no impact on non-canvas hosts, other than up taking a new member, if they directly implement INameResolver, and IIRC, they should be using ReadOnlySymbolTable instead of directly using INameResolver.

✅ No public API change.

✅ No public API change.


Bump 2.3.n ruby version in CI from 2.3.1 to 2.3.3

ref: https://www.ruby-lang.org/en/news/2016/11/21/ruby-2-3-3-released/

:two: ⚫  :three: ⚫  :three:   🏃


Question: how to force recipe upload

Question: how to force recipe upload
Hello! We use CPT in our CI scripts. During CI we build packages for several types of OS (Win + Linux) and when the CPT tries to upload packages it sometime fails to do this with error "Upload recipe to 'my_remote' failed: Remote recipe is newer than local recipe" . Looks like the problem is in the fact that recipes for distinct platforms are built and uploaded concurrently from distinct machines. I know that there is a parameter --force for conan upload command but I can't find a way to set it in current CPT version. Can you give some advice how this can be fixed? Maybe the intended design is to serialize build process to handle distinct OSes one after another?

Fixed by #548
It should be available on CPT 0.35.1

Can you please tell when 0.35.1 will be available for download?


Adds option for usage of fixed width integer

This fixes #53 with adding an optional option to the Swift template file.

Awesome, nice one @martinknabbe. I'd like to change this around a bit though. It would be good for the property to be defined in options (for a general place and so it can also be changed from the command line) and for non-swift formatters to be unaware of this property.

Inject templateConfig into the CodeFormatter (and the swift subclass)
parse out the useFixedWidthIntegerTypes property from templateConfig.options in the SwiftFormatter initializer and set a property within that class

Just for clarification. To me the options section in the template file looks like options just for stencil files. Is it intended to put all kind of options in there?
With "Inject templateConfig" you mean through initializer, correct? Like:
public init(spec: SwaggerSpec, templateConfig: TemplateConfig) {

Yep, that's pretty much what I meant. Thanks @martinknabbe!

I've renamed the property to fixedWidthIntegers and added it to the default template in master 👍

When is this going to be released?
Is there an upcoming release planned?

A release will be happening soon. This must be released first https://github.com/xcodeswift/xcproj/pull/191


Fix a CupertinoScrollbar NNBD issue

Fixes https://github.com/flutter/flutter/issues/110625
I believe that the issue is an exception in production, I mean there will be assertion errors in debug mode.
I still modified some code because I wanted to be consistent with other places where getScrollbarDirection is used.
In fact, it's hard for test cases to test exactly what I've changed because the debug checking will fail the test first.

BTW - thank you for picking this up so quickly. 💙


publish ebf as otel collector module

Is your feature request related to a problem? Please describe.
I need to setup and run additional processes to enable ebf collection on devices(eg iot). I want to have the features as part and integrated into the otel collector process.
Describe the solution you'd like
Provide the collector and reducer feature set as opentelemetry  collector modules which can be optional integrated  as receiver and /or processor module.
Describe alternatives you've considered
No response
Additional context
No response

What about metrics from https://github.com/open-telemetry/opentelemetry-ebpf/blob/main/docs/kernel-collector.md - are those covered in hostmetrics.
What about embedding reducer https://github.com/open-telemetry/opentelemetry-ebpf/blob/main/docs/reducer.md otel collector receiver for inbound ebpf stream pushed from "ebpf collector's" running on the same edge but on "low" resource devices:
The otel collector would be "the" gate on the edge for all controllers around at the same iot edge , kind of a gateway to the backend collecting epbf requests.

What I meant was to suggest if this software features should be offered under hostmetrics receiver or not. What hostmetrics offer and what this project offers is really about the hostmetrics and it would be nice to have all the configuration in one receiver. But I understand why it might benefit to keep separate too.

I think you are referring to the encapsulation of the eBPF collector as a receiver directly available as part of the receivers of the OpenTelemetry collector.
The collector right now doesn't allow cross-compilation of C components (it builds with CGO=0).
https://github.com/open-telemetry/opentelemetry-collector/blob/main/CONTRIBUTING.md#using-cgo
Now, we could build a separate go receiver that encapsulates the eBPF collector and offer it for folks who want to build their own collector distribution.

"prohibited due to the lack of portability and complexity"
Would it generally work .... The problem on IOT devices mostly is that go is not the first citizen, whereas c its one:
Switching CGO= for a collector with ebf "onboard" ..would make sense a lot, doesn't it?

From the SIG meeting: what problem are we trying to solve? Are we trying to slim down the solution to one binary, which compiles both the eBPF collector and the OpenTelemetry Collector?
Given that you mention that Go is not a first class citizen on iot devices, why not instead deploy the kernel collector on the device and move off the reducer to a central location? Then it might make sense to create a reducer receiver.

Sorry..maybe i made it not clear, the reducer as an otel collector receiver is exactly what i requested, where as the eBpf collector  can run in x instances in the outer rim of that iot/edge device where resources are tight and go is not welcome but still push it to the collector where its gets reduced and forwarded to the cloud


Don't use a StringIO when encoding data.

When data is encoded to BERT, each individual, encoded result piece is stored inside an Array based Buffer. At the end, each piece is sequentially written out to a StringIO object and the underlying String is returned. Unfortunately, this sequential writing to StringIO causes a lot of growth and reallocation of the internal String object. By calling #join on the Buffer's Array, Ruby will allocate a single string that can contain the whole result in a single step.
See benchmarks in https://github.com/github/bert/pull/7#issuecomment-239096180.

This is an easy win in reducing memory usage without any noticeable impact on CPU usage. 🎆

Yeah, this looks like a gain even for smaller payloads.

It looks like this PR causes some encoding-related test failures:
https://travis-ci.org/github/bert/builds/190846984
@arthurschreiber, @carlosmn: Do you mind if I revert this PR? I'm trying to get master CI'd and in a state where it reflects what we're running in production.

@charliesome See the fix over in https://github.com/github/bert/pull/10.