Some specific native attributes not applied in Shadow DOM

I came up with this issue when I found a bug in a skatejs component that tried to set a string attribute named value inside the shadow DOM of another skatejs component
It works fine in Chrome but not in the rest of the browsers. The attribute seems to not have the value assigned but it is as an property.
I'm not sure why it is not working with this specific name, but I assume there is a reason and there should be more names that will have the same issues. The result, as you can see in the example, is an empty string.
It's not the same case if you slot the component with the value attribute. That case it will work.
Open this example here in FF/Safari/ie
Skate version of the example is the latest.
Quick snippet to show the problem:
// javascript
define('x-bar', {
  props: {
    value: prop.string({ attribute: true }),
  }
});
define('x-foo', {
  render() {
    return (
      vdom.element('div', () => {
        vdom.element('x-bar', { value: 'b'})   // this won't work
        vdom.element('slot')
      })
    );
  },
});

// html
<x-foo>
  <x-bar value="1"/>    // this will work
</x-foo>

You end up having something like this in FF:

@mcorbanini can you retest with 4.0.1? I think this was fixed in #876.

No, it was not fixed. Same issue happening here if you open it in FF.

Since this is not a critical bug and we are not sure if it's related with skate or not I'm closing this issue.
It's only happening in FF but not in other browsers without native support like ie
It can easily be solved by changing the attribute to a different name for now.


Add epsilon library port

EPSILON is an Open Source wavelet image compressor, that is aimed on parallel and robust image processing.
Signed-off-by: Hiroshi Miura<EMAIL_ADDRESS>

Looks good, thanks!


Define artstyle

Lets have a look at cell shading

We will implement cell shading as its own issue later


Allow custom hovers to be disabled

Steps to Reproduce:

User native titlebar
Notice that some "hover" use the native OS hover.
Notice that other hovers use their own Frankenstein hovers that show up inconsistently

Please, provide a way for users to disable these hovers.

@misolori not sure if we have a tracking item for the UX of mixed hover types

@Tyriar since we have other settings that enable certain features this feels like one we should consider and default to the native hover.

I would like to have a lot of the hovers disabled, because some of those are extremely annoying and disruptive, because they show up really fast.
One of the worst ones is the extension's hove, because it does not allow me to rest my mouse cursor without changing something at the screen. This is extremally annoying to me personally and makes reading some things much more diffcult because I then have to focus on where the mouse cursor is at the time when I just want to scan the screen for information (i.e. read).
Personally to me, vscode feels like each day it is getting more frustrating and distracting, and that I waste more time trying to fight it than I spend being actually productive with the product. That is really bad for me, some of these msft products feel like they are being intentionally designed to be addictive instead of being useful.


Remove manual install of python-etcd and posix-spawn from docs.

These are now available as RPM dependencies.

@matthewdupre please can you review?  These instructions should be correct as of #878


Add support to Disqus

This PR enables the user to show, optionally, Disqus comments below each post.
In order to get this working the user only needs to add the following to _config.yml:
disqus:
  shortname: my_disqus_shortname

You can find out more about Disqus' shortnames here.
The current behavior remains the same if no disqus property is supplied.

In order to avoid unnecessary requests in development mode, comments could only be displayed in production mode ( {% if jekyll.environment == "production" %}…)

I made all the suggested changes. Let me know if it looks good or if I should update anything else :)

@nicholaspufal this is looking good! Mind adding some documentation to the README on how to add comment support to my site?

@benbalter I just added a couple of lines to the README file explaining how to use it. Let me know if I missed anything or we are good to go 👍

Question: should the theme add comments to pages by default? E.g., about?

@benbalter Good point. We should add comments only on pages with post layout by default.

We could add comments only on pages with post layout by default?

We could, but that's a really complicated out-of-the-box experience for what I suspect, is the default/most common desired behavior. I guess put it another way:

Do we want pages to have comments by default? Do we think most users want this? if not, do we want to force the user to manually disable it?

Do we want posts to have comments by default? Do we think most users want this? If so, do we want to force users to manually enable it?

I suspect that the majority of users, if they enabled discuss, would want comments on posts (e.g., a blog post), but not Pages (e.g., an about page, their index page), or any other category (which I think is the current behavior, since the include is only included on posts).

I agree with all points listed here. As @benbalter already mentioned, the current behavior already is this:
IF the user enabled disqus (meaning they added a new property to their _config.yml file) and IF it's a post (that _disqus_comments.html partial is only being included as part of the post.html layout) then it will show comments by default.
If they haven't added disqus then no comments would be displayed as the partial won't be loaded at all.
If it's not a post then it will not load that partial as well, meaning no comments will be displayed.
In my mind the current behavior is already what you guys mentioned, am I correct?

LGTM

LGTM.

@jekyllbot: merge +major

Thanks @nicholaspufal!


Difference between $Enum and $Keys

On the face of it they seem to be very similar. Is there some underlying implementation which would lead me to use one over the other?
$Keys<typeof obj> === $Enum<typeof obj> it seems

Also would be great to have a comment on https://github.com/facebook/flow/issues/627 around how we could extract names & values in the context of named/keyed enums.

IIRC they just aliases for the same thing

Yeah, see https://github.com/facebook/flow/blob/master/src/typing/type_annotation.ml#L275

Merging with #627

Cheers! :)


Documentation - Review responsive layouts content

Review the current explanation of responsive layouts and breakpoints that can be found here:
https://www.figma.com/file/nUj2wIDomm5jk9CBAH0iN9/Utility-framework-documentation?type=design&node-id=27-1006&mode=design&t=bLHe9JspU6CeN2Ks-0
It was a first draft and will potentially need a little bit more work.
Note: Add a sidebar category for "responsive layouts" and "states" links.

Draft of guidance:
https://docs.google.com/document/d/11LWVaKGPyA71aCAPpg45J7d8qBNoJlDBnbsqRrxhEYA/


chore: Adding support for arrag_agg on column type tstzrange

SUMMARY

related to https://github.com/apache/superset/issues/28248
Fixed Issue https://github.com/apache/superset/issues/28200
This is Actually a bug fix. The fix is specific to Postgres database.
Location where the code changes need to be made are not ideal.
This Data conversion should be ideally happening at this place
https://github.com/apache/superset/blob/44690fb299ab3b7adc24e84eeec73bccdde14420/superset/db_engine_specs/postgres.py#L179
Added additional conditional check, converted data if needed. as impacts would be low on this change.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

After
Data

Query

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[x] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

@nytai, I have tried Adding column mutators - for converting Postgres adoptor DateTimeTZArray to a simpler one line (datetime,datetime) but it looks like a much more bigger change than expected.
I just added some additional code for debuging - it's apparent that SQLAlchamy Postgres dialect doesn't support All column types which Postgres Adopter supports.
            description = cursor.description or []
            # Create a mapping between column name and a mutator function to normalize
            # values with. The first two items in the description row are
            # the column name and type.
            logger.info(f'Description: {description}')
            logger.info(f'column_type_mutators: {cls.column_type_mutators}')

            for row in description:
                logger.info(f'row: {row}')
                logger.info(f'get_datatype: {cls.get_datatype(row[1])}')
                logger.info(f'get_sqla_column_type: {cls.get_sqla_column_type(cls.get_datatype(row[1]))}')

            column_mutators = {
                row[0]: func
                for row in description
                if (
                    func := cls.column_type_mutators.get(
                        type(cls.get_sqla_column_type(cls.get_datatype(row[1])))
                    )
                )
            }

Above code snippet is near https://github.com/apache/superset/blob/f5843fe588112c5c303215945a36fda0845c9e99/superset/db_engine_specs/base.py#L953
Dubug infromation was:
uperset_app           | 2024-05-04 02:11:20,685:INFO:root:Description: (Column(name='array_agg', type_code=3911), Column(name='event_name', type_code=25))
superset_app           | 2024-05-04 02:11:20,685:INFO:root:column_type_mutators: {<class 'psycopg2._range.DateTimeTZRange'>: <function PostgresEngineSpec.<lambda> at 0xffff6c5a35b0>, <class 'sqlalchemy.dialects.postgresql.ranges.TSTZRANGE'>: <function PostgresEngineSpec.<lambda> at 0xffff6c5a3640>}
superset_app           | 2024-05-04 02:11:20,685:INFO:root:row: Column(name='array_agg', type_code=3911)
superset_app           | 2024-05-04 02:11:20,685:INFO:root:get_datatype: tstzrangeARRAY
superset_app           | 2024-05-04 02:11:20,685:INFO:root:get_sqla_column_type: None

its none since tstzrangeARRAY doesn't exits. Any idea or suggestion?


Social media url becomes mandatory upon input field focus

If user clicks social media url field but decides to abort, they could not submit the form; also should allow them to remove the link if filled.

Problem solved


dropdown doesnt automatically close

The dropdown does not close when an item such as a link has been clicked within the dropdown-menu
Setting vsTriggerClick to true
the dropdown will only close if there is click event outside of the dropdown DOM area.
How can you get it to close without impacting some of the other grouping features?

We are facing similar issue. An update would be greatly appreciated.

same, do u even care?


Provide a setting to automatically exclude all gems

I have checked that this feature is not already implemented

[x] This feature does not exist

Use case
The performance of the global go to symbol in ruby-lsp is noticeably worse when not excluding any gems than when excluding every gem.
Here are some short videos showing the difference:
https://github.com/user-attachments/assets/c5d5d922-df3b-46c7-b9f7-6dd65c9359cc
https://github.com/user-attachments/assets/ece1805e-0cba-4592-a51c-cf57f9c66a6e
Currently, if I want to exclude every gem, I'm forced to list them all in my editor's config file: https://github.com/gmcabrita/dotfiles/blob/f7b8d85449b4f6da3acbc7428548ceb4ca29f999/.config/zed/settings.json#L137-L585.
I also have to update that list as time goes on and new gems are added to an existing project, or I jump to a new project that has gems I am not currently ignoring.
Providing a setting to exclude all gems without having to list them would be a nice improvement.
Description
Possibly support one of these in the editor settings, ensuring that no gems are ever processed/indexed:
{
  "excludedGemPatterns": ["*"]
}

or
{
  "excludeAllGems": true
}

Implementation
No response

If I understand it correctly, global go to symbol is equivalent to workspace symbols in VS Code.

Yes, this is for the workspace/symbol method.

If that's the case, we already started excluding dependencies from the request with/without indexing them (https://github.com/Shopify/ruby-lsp/pull/2131). Can you please upgrade to the latest ruby-lsp to confirm it?

I checked with v0.20.0 and the performance difference is still pretty much the same.

Also, excluding all gems from indexing will seriously degrade the functionality of other features like go-to-definition, autocompletion...etc. so it's not something we'll encourage users to do and it's rarely the right solution to the issue.

I understand that this degrades the go-to definition and autocomplete functionality for external gems. Personally, the performance hit of including all these gems is so annoying that I don't care if I have autocomplete on them or not. I suspect other developers are affected as well, they probably just don't care about editor latency as much as I do or they would have excluded all the gems like I did.
I understand if this is not a setting that ruby-lsp wants to support. Performance for workspace/symbol should still be worked on even if this setting is supported, since it's just a band-aid.

I agree that we can possibly improve the performance of the workspace/symbol request so it has less delay. Therefore, I'll change the title of this issue to be explicit about this end goal.
But I also need to be honest that given our team's current backlog, this will be low on our list for at least a while. That said, if you want to investigate what's causing the slowdown, PRs are welcome 🙂


Added changes to work against AzureStack Environment

These changes allow Storage extension to work with Azure Stack Environments

Hi @yatna, thanks for submitting.
Have those comments made in your fork been addressed yet? If not, could you take a look at those? Also, I see a lot of use of the any type. I assume this was at least partly to avoid making changes to the vscode-azureextensionui package. But it would be preferable to use proper typing and update that package accordingly. If you have any questions about that process, please feel free to reach out.

Just want to say we will be switching over to the new azure-sdk-for-js soon (could be in master as soon as this month, but will need a bit of time before actually releasing). The code being touched by this PR seems very related, so might be best to wait until that's done
Tracking issue: https://github.com/microsoft/vscode-azuretools/issues/510

Hey guys - maybe I wasn't clear enough in my above comment. We're changing to the new "azure-sdk-for-js" within the next couple of weeks and we don't plan to release an update to this extension until after that happens. @yatna I appreciate the effort you've already put in to this PR, but I don't want us to spend more time on throwaway code. If you're trying to get Azure Stack support in for some deadline - let us know and we can discuss options. Otherwise, you're welcome to follow  this issue and file a new PR after that work is done.


Couldn't create Engine

java.lang.IllegalStateException: Couldn't create Engine
at com.google.android.filament.Engine.create(Engine.java:37)
at com.google.ar.sceneform.plugin.viewer.Filamentor$3.run(Filamentor.java:102)

Closing as this issue is missing key information to help us reproduce it.

Android Studio version
Sceneform version
Device manufacturer, model, and O/S
ARCore APK installed version:
On Windows, use: adb shell pm dump com.google.ar.core | findstr /i "packages: versionName"
On macOS, use: adb shell pm dump com.google.ar.core | egrep -i versionName\|packages:
Output of adb shell pm path com.google.ar.core
Output of adb shell getprop ro.build.fingerprint
Specific error message or problem encountered

It looks like the crash you're reporting is in the Android Studio plugin.  It would be helpful to share the Android Studio version, the platform you're running (OS, version), and what the repro is (my assumption is it gives you this error message on startup).
It would also be helpful to share some logs from the issue.  After restarting Android Studio with the plugin enabled and triggering the crash/error, go to Help > Collect and show logs in Finder (or explorer if Windows), and share at least the most recent idea.log file.  Feel free to send them via email if you'd prefer to share them that way.

thank for your concernhere some screenshoot attachedtool : Android Studio 3.3.2disable & Restarting the plugin cast solve the problem (sceneform 1.7.0 & 1.8.0)3d model cant be viewed in sceneform viewer
On Friday, March 29, 2019, 1:17:38 AM GMT+7, tpsiaki<EMAIL_ADDRESS>wrote:

It looks like the crash you're reporting is in the Android Studio plugin. It would be helpful to share the Android Studio version, the platform you're running (OS, version), and what the repro is (my assumption is it gives you this error message on startup).
It would also be helpful to share some logs from the issue. After restarting Android Studio with the plugin enabled and triggering the crash/error, go to Help > Collect and show logs in Finder (or explorer if Windows), and share at least the most recent idea.log file. Feel free to send them via email if you'd prefer to share them that way.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Make github changesets entries not thank core maintainers

Iunno, maybe this is just be being weird, but having "Thanks @noviny" in a bunch of changelog stuff for the thing it's my responsibility to maintain/look after is weird to me.
@mitchellhamilton do you have any thought opinions about this?

Yeah, I do think it's a bit weird but also, I don't feel that strongly about it either way. I guess the question is, what are the alternatives? Remove the thanks? Have a list of who is a core maintainer?

I'd like a core maintainer list to use to strip the thanks for those people.
Going to close this as an issue though just because it's so far down the priority line.
May reopen later/change this if it really bothers me.

Did anyone take the extra mile here and set up a custom formatter like that?


Clicking on Encrypt backups radio option in Backups cause all radio options to hang

Steps:

Install Rancher Backups from Apps & Marketplace
Click on Create backup
Click on Encrypt Backups  in the Encryption section

Results:  I can no longer click on any radio options.  Error in console.

Verified fixed


feat: allow multiallelic SNPs in transform

I'm making this PR for @XimeiWulilyy , who asked recently about whether the transform command could accept multiallelic SNPs. Previously, there was a check in place to restrict it to only biallelic SNPs, since the data.GenotypesVCF class could handle only biallelic SNPs. But in #195, multiallelic support was added to the data.GenotypesVCF class.
This PR removes the biallelic check in transform, adds some tests, and makes some changes to Haplotype.transform and Haplotypes.transform to allow them to handle Genotypes classes with multiallelic SNPs in them.

@mlamkin7 , can you review this? and just double check that the tests are sufficient?
also, can you recall any other reason we hadn't enabled support for biallelic variants in transform, yet? Is there anything I'm not thinking of?


Fix parsing of strict arrays

While ECMA arrays contain script data objects (name-value pairs), strict
arrays contain only a fixed number of values. The spec is misleading
about this, but both ffmpeg and GStreamer handle it like that and so do
files in the wild, e.g. http://streams.videolan.org/samples/FLV/undetectable1.flv

Coverage remained the same at 76.415% when pulling 337c7e5f0bdb013fc46d4c7619dfe71fa83f498e on sdroege:master into 3dc593f1dba0fcae945de71f4f621139a9ed4a31 on Geal:master.

Coverage remained the same at 76.415% when pulling 337c7e5f0bdb013fc46d4c7619dfe71fa83f498e on sdroege:master into 3dc593f1dba0fcae945de71f4f621139a9ed4a31 on Geal:master.

Thanks! This parser is a ot better thanks to all your fixes :)


TFConfig should be demonstrated more specifically.

When I glanced at tf-operator example, I wondered how tf-operator map tensorflow-native code to tf-operator, especially the args of worker-num, ps-num, worker-hosts, ps-hosts, etc.
Is it done by hard coding or is there some magic? Should I keep my input args as the same as tf_cnn_benchmarks.py ?
I couldn't find any clue online, so I had to dig into the source code. Finally, I found that TFConfig structure is the connector. Tf-operator set everything it need into the TFConfig struct and set  it to environment variable.
Does it mean in order to use tf-operator. I have to read config from the  environment variable?(correct me if i am wrong?)If it is so, I think there should some doc specifying this.

TF Estimator will read the TF_CONFIG automatically.

A good write-up on how tf-operator/TfJob helps is available at
https://github.com/Azure/kubeflow-labs/tree/master/7-distributed-tensorflow
The exact examples are still using ksonnet, but the explanation of how TfJob helps is very simple to understand. Hope this helps.

A good write-up on how tf-operator/TfJob helps is available at
https://github.com/Azure/kubeflow-labs/tree/master/7-distributed-tensorflow
The exact examples are still using ksonnet, but the explanation of how TfJob helps is very simple to understand. Hope this helps.

Thx a lot! the example is great!


FooterView doesn't work with footer

Can I have more details about what you're trying to achieve ?
On Tue, Jan 27, 2015, 06:48 Chang-han<EMAIL_ADDRESS>wrote:

—
Reply to this email directly or view it on GitHub
https://github.com/traex/ExpandableLayout/issues/7.

I attached a footer on the listview.
I was using an OnClickListener of Footer(its own listener)
And this is not working with this library, so I handle click with listItemClickListener.
But this way is little confusing to me, so I want to use own OnClickListener of footer.


Date Picker behaving wierd. Not able to chose the complete date at one go.

Describe the bug
Date Picker behaving wierd. Not able to chose the complete date at one go.
To Reproduce
added Date field on the page from library -> halstack-react
Clicked the date picker to launch the calendar, want to select date 06/25/1975, the moment I select 25 then the calendar gets closed. Then I have to open date picker again, and it shows the current date - the moment I click the year and select a year the popup gets closed, It doenst allow me to chose a month, date, and year at one go. Only by adding manual the date I am successful in entering date.

Thanks Praveen,
You are right. This looks like a bug in the date component.
We will have look at it ASAP.
Regards.

Can you please suggest, how to get this fix? what version of halstack-react we need to add?

Hello @ppurumala
We have just released 1.1.1, which contains the fix for this issue.
Regards.

The date picker is still very buggy. When I am selecting an year and then proceed to select a date, the year gets reset.
And always on the date picker the current date shows even I am selecting some other date.
Its very confusing to select a date-month-year from the date picker.

It works fine in the example provided in the documentation site.
https://developer.dxc.com/tools/react/1/#/components/date
Remember there are two types of date components (controlled and uncontrolled). Please make sure you are using them correctly. If the problem persist, please create another issue providing an isolated example.


Get /build/md5.js 404

I use bower and injector adds a scrpt tag to md5.js, but i get 404.

Sorry about that. Forgot to remove reference to md5.js in latest release (0.3.0). Should be fixed now in 0.3.1. Thanks for reporting!


Improve support of MATLAB structure variables

Reported by beutlich on 11 Nov 2016 07:16 UTC
#1840 added the feature to read variables from MATLAB structure variables to MSL 3.2.2. However the feature currently is limitated to 1x1 structures. It would be easy to generalize the feature for arbitrary two-dimensional structures by giving giving the structure element, e.g., a.b could be generalized to a(1,1).b where a is a structure and b is a real array. Then a(2,3).b(4,5).c could also be valid inputs.
If this feature is not considered, then at least the current error message for mxn structures should be improved to point to the dimensional problem and not to the type problem.

Migrated-From: https://trac.modelica.org/Modelica/ticket/2105

@Claytex Thanks for the nice blog at http://www.claytex.com/blog/reading-structures-from-mat-files. Do you have any feature requests?

@HansOlsson @sjoelund I kindly ask for your input since I have no idea who else cares and whom I could ask. Thanks for your feedback. I appreciate it.
Options are:

Do not add support for multidimensional structs, but improve error message.
Add support for multidimensional structs and use MATLAB syntax for array subscription
Add support for multidimensional structs and use Modelica syntax for array subscription
Use both MATLAB and Modelica syntax

Which one do you prefer?

@Claytex @HansOlsson @MartinOtter Any feedback? Otherwise I will simply close as wontfix.

I have no specific opinion at this time

OK, no need to work on it (now), if there is no public interest.


Extending PDFBuilder

What is the way of extending the PDFBuilder and customize it ? I was able to extend the formBuilder but not able to do the same with PDFBuilder. I am guessing it is not exposed as a module. Please let me know what should the appropriate way to do that when using it in an angular based front end project.

Have you checked https://github.com/formio/angular-formio/issues/473 ?

Yes. The thing I am looking for is to customize the default behavior of PDFbuilder when using it through angular-formio library. The #473 is about making custom components when using PDF builder. Thus, I think #473 is different than #480.

Then maybe @travist can help

I am looking at the core code now, and it looks like we are not exporting the Builders construct @ https://github.com/formio/formio.js/blob/master/src/FormBuilder.js#L2.  We need to make a change to export this.  Then you would be able to do the following.
import { Formio } from 'angular-formio';
const PDFBuilder = Formio.Builders.getBuilder('pdf');

class MyPDFBuilder extends PDFBuilder {

}

Formio.Builders.addBuilder('pdf', MyPDFBuilder);

We will add a task for us to export this so this can be done, but right now, we cannot extend the PDF builder from an application.

When can I expect this change to be published?

I just looked and it does seem like the Builders construct is exported. Give the above a try and let me know if it works for you.

Hi @travist. We updated to the latest version (4.6.1) of angular-formio, and tried the snippet that you shared. But looks like "Builders" is still not exposed under Formio:

This is probably that they are not exposed with the type definitions. What happens when you do the following?
(Formio as any).Builders.addBuilder('pdf', MyPDFBuilder);

Tried the same as mentioned above. Still not able to access the builders.The screenshot of error stack is given below -

The code snippet is also given below -

We will add this to our backlog to to get added to the exports.

Has there been any updates on this recently?

Hello @max-in-to can you try using the latest version of angular-formio and see if the issue has been resolved? The newest stable version of Angular-formio is 4.11.0.

We're currently addressing a backlog of GitHub issues, and as part of this effort, some inactive issues may be marked as closed. This isn't a dismissal, but a step toward more efficient tracking.
If you feel the issue is still relevant, please re-open and we'll ensure it gets the attention it deserves. Your understanding is appreciated as we work to enhance our open-source responsiveness.


Add checkstyle plugin and fix code format

I fixed code format with embulk standard style.
Upgrade gradle version
At first, I upgraded gradle because checkstyle plugin doesn't work with gradle 2.6. 2.7+ is required.
Allowing gradle to use checkstyle 6.8+ by ethankhall · Pull Request #491 · gradle/gradle
Install checkstyle plugin
This plugin is bundled with current embulk templates.
Plugin dependencies at build.gradle and configuration XML are generated when we executes embulk new command.
$ embulk new java-output elasticsearch
...
Creating embulk-output-elasticsearch/config/checkstyle/checkstyle.xml
Creating embulk-output-elasticsearch/config/checkstyle/default.xml
Creating embulk-output-elasticsearch/build.gradle
...

Fix code format
I changed following points that were warned by ./gradlew checkstyle commad.

code format
order of import statement
some variable's definition type

👍


Logo

We need a logo for the Chrome Store and for the extensions page thing.

@nywillb

@thatoddmailbox IDK


Phase 2 - Text & Filters

Externs for Text classes
https://github.com/GoodBoyDigital/pixi.js/tree/dev-rewrite/src/text
Also move filters to the new package
https://github.com/GoodBoyDigital/pixi.js/tree/dev-rewrite/src/filters

Text done. Filters later.


Make the Indexing Process Transactional

The goal is to ensure that the indexing process is transactional to maintain data consistency and integrity. This involves wrapping the indexing operations in a transaction so that either all operations succeed or none do.

Hi, I can take this up. Could you please assign this to me?


Update index.md

Addition of detailed instructions for how to install WSL as a prerequisite to toolchain configuration and other edits for clarity.

@microsoft-github-policy-service agree company="Microsoft"

Made above changes to text to point to images in repo under azhop/docs/images as requested


[bug] aiconfig generated from workbooks adds "system_prompt": null

Created prompts in a workbook (not using system prompt but changed temperature). Downloaded the aiconfig from the workbook and this is what the aiconfig had in model metadata. It gives me an error and only is fixed when I removed the system_prompt setting. Assuming cuz its set to null.
{
  "name": "OpenAI Prompt Engineering Guide",
  "schema_version": "latest",
  "metadata": {
    "models": {
      "gpt-4": {
        "model": "gpt-4",
        "top_p": 1,
        "temperature": 0,
        "system_prompt": null,
        "presence_penalty": 0,
        "frequency_penalty": 0
      }
    },
    "parameters": {
      "original_prompt": "testing"
    }
  },

This is fixed, right @Ankush-lastmile @rossdanlm ?

Yea we can close this from https://github.com/lastmile-ai/aiconfig/pull/542. I added more generalized task in https://github.com/lastmile-ai/aiconfig/issues/543


Vuepress: Add features to homepage

Content not finished, but editable in index.md. Closes #62.

Looking good, with just a few minor tweeks think it's good to go.

I would add a heading and subheading to this section, something like Why LDK? and Leading Bitcoin open source projects love LDK. The copy will likely change.
Remove the anchor links from the headings for each feature as it will link out to parts of the from the Documentation -> link
Add the Documentation -> link for the other two sections.

@ConorOkus Updated. The Netlify preview is also back -- I still had configured the vuepress branch as the base, which got deleted. Now every PR targeting develop gets a preview build.

I will open a separate PR to update the copy.


Server crash because of [hudbar] mod

Server crashed at 19h31 14/07/2015
Logs :
19:31:58: ERROR[ServerThread]: ServerEnv: Trying to store id=33691 statically but block (1298,6,48) already contains 49 objects. Forcing delete.
19:31:58: ERROR[ServerThread]: ServerEnv: Trying to store id=33790 statically but block (1298,6,48) already contains 49 objects. Forcing delete.
19:31:58: ERROR[ServerThread]: ServerEnv: Trying to store id=33795 statically but block (1298,7,48) already contains 49 objects. Forcing delete.
19:31:58: ERROR[ServerThread]: ServerEnv: Trying to store id=33809 statically but block (1298,6,48) already contains 49 objects. Forcing delete.
19:31:58: ERROR[ServerThread]: ServerEnv: Trying to store id=33853 statically but block (1298,6,48) already contains 49 objects. Forcing delete.
19:31:58: ERROR[ServerThread]: ServerEnv: Trying to store id=33864 statically but block (1298,7,48) already contains 49 objects. Forcing delete.
19:31:58: ERROR[ServerThread]: ServerEnv: Trying to store id=33869 statically but block (1298,7,48) already contains 49 objects. Forcing delete.
19:31:58: ERROR[ServerThread]: ServerEnv: Trying to store id=33873 statically but block (1298,6,48) already contains 49 objects. Forcing delete.
19:31:58: ACTION[main]: IRC: Disconnected.
19:31:58: ACTION[main]: [interact] Blacklist saved
19:31:58: ACTION[main]: [mana] Server shuts down. Rescuing data into mana.mt
19:31:58: ACTION[main]: [mana] Wrote mana data into /home/quentinbd/minetest/worlds/minetestforfun//mana.mt.
19:31:58: ACTION[main]: compassgps writing settings
19:31:58: ACTION[main]: [tsm_pyramids] Chests saved
19:31:59: ERROR[main]: ERROR: An unhandled exception occurred: ...home/quentinbd/minetest/bin/../mods/hudbars/init.lua:254: attempt to index field '?' (a nil value)
19:31:59: ERROR[main]: stack traceback:
19:31:59: ERROR[main]: 	...home/quentinbd/minetest/bin/../mods/hudbars/init.lua:254: in function 'unhide_hudbar'
19:31:59: ERROR[main]: 	...home/quentinbd/minetest/bin/../mods/hudbars/init.lua:324: in function 'update_hud'
19:31:59: ERROR[main]: 	...home/quentinbd/minetest/bin/../mods/hudbars/init.lua:354: in function '?'
19:31:59: ERROR[main]: 	.../quentinbd/minetest/bin/../builtin/game/register.lua:341: in function <.../quentinbd/minetest/bin/../builtin/game/register.lua:329>

In thread 7f87a6dc3740:
/home/quentinbd/minetest/src/main.cpp:882: int main(int, char**): Assertion '0' failed.
Debug stacks:
DEBUG STACK FOR THREAD 7f879f027700:
#0  virtual void* CurlFetchThread::Thread()
DEBUG STACK FOR THREAD 7f87a6dc3740:
#0  int main(int, char**)
(Leftover data: #1  Dedicated server branch)
(Leftover data: #2  virtual void ServerMap::save(ModifiedState))
(Leftover data: #3  void ItemStack::serialize(std::ostream&) const)
./start02.sh : ligne 26 : 25059 Abandon                 /home/quentinbd/minetest/bin/minetestserver --world /home/quentinbd/minetest/worlds/minetestforfun/ --config /home/quentinbd/minetest/minetest.conf --gameid minetestforfun_game --port 30001
----------------------
Server restarted at mardi 14 juillet 2015, 19:32:29 (UTC+0200)
----------------------
WARNING: system-wide share not found at "/usr/share/minetest"

Important lines
Crashed because of the  hudbar mod line 264
*19:31:59: ERROR[main]: ERROR: An unhandled exception occurred: ...home/quentinbd/minetest/bin/../mods/hudbars/init.lua:254: attempt to index field '?' (a nil value)
19:31:59: ERROR[main]: stack traceback:
19:31:59: ERROR[main]: 	...home/quentinbd/minetest/bin/../mods/hudbars/init.lua:254: in function 'unhide_hudbar'
19:31:59: ERROR[main]: 	...home/quentinbd/minetest/bin/../mods/hudbars/init.lua:324: in function 'update_hud'
19:31:59: ERROR[main]: 	...home/quentinbd/minetest/bin/../mods/hudbars/init.lua:354: in function '?'
19:31:59: ERROR[main]: 	.../quentinbd/minetest/bin/../builtin/game/register.lua:341: in function <.../quentinbd/minetest/bin/../builtin/game/register.lua:329>
In thread 7f87a6dc3740:
/home/quentinbd/minetest/src/main.cpp:882: int main(int, char**): Assertion '0' failed.
Debug stacks:
DEBUG STACK FOR THREAD 7f879f027700:
#0  virtual void* CurlFetchThread::Thread()
DEBUG STACK FOR THREAD 7f87a6dc3740:
#0  int main(int, char**)*

https://github.com/Ombridride/minetest-minetestforfun-server/commit/e6168f84bad3ea8a51ac5a97c82970211ed665a0

Fixed


🔹[EPIC] Migrate documentation and examples to RS SDK 5.0.0

Description
NEAR SDK RS 5.0.0 has been released, we now need to update all docs and docs
### Related Issues
- [ ] https://github.com/near/docs/issues/1745
- [ ] https://github.com/near/docs/issues/1746
- [x] https://github.com/near/docs/issues/1747
- [x] https://github.com/near/docs/issues/1756
- [x] https://github.com/near/docs/issues/1755
- [x] https://github.com/near/docs/issues/1754
- [x] https://github.com/near/docs/issues/1753
- [x] https://github.com/near/docs/issues/1752
- [x] https://github.com/near/docs/issues/1751
- [x] https://github.com/near/docs/issues/1750
- [x] https://github.com/near/docs/issues/1749
- [x] https://github.com/near/docs/issues/1748

For integrations tests on the examples  do you think we should be going with javascript/ava or follow the cargo near structure ant test with near_workspaces?

@flmel sorry for never answering. I guess a good compromise is: workspaces-js for JS projects, workspaces-rs for RS projects

Looks like there are some nice changes to reflect. I love how they have the scrolling "before" and "after" here:
https://github.com/near/near-sdk-rs/releases/tag/near-sdk-v5.1.0
Here's an example showing how to use the #[near] macro:
https://github.com/NEAR-DevHub/neardevhub-contract/pull/103/files#diff-0138e1668433cf4b746a3d18b143e0a7bd1465d8f67989f7956f52076298b259R14
Think we can simplify stuff like this (and elsewhere)

https://docs.near.org/sdk/rust/contract-structure/near-bindgen

Thanks @mikedotexe addressing it!


Not able to create service key in the BTP Cockpit.

Hi,
I've followed the steps to mentioned in the https://github.com/SAP-samples/teched2020-DEV165/blob/main/exercises/create-service-instance-key.md.
I'm not able proceed further from step 10. I've input the same json body but I got an error message as screenshot in the below. The "Create" button is greyed out. Can you please help me? Thanks.

Regards,
Sean

Hi @simplykapoor,
Can you please help me? Hope to hear from you. Thanks.
Regards,
Sean

Hi @Sean3350,
The flow is changed little bit, you do not need to enter any parameter while creating the service key, it inherits from the service instance.
So you just need to enter the Service Key name and create.
Please check the official help documentation for more details:
Help Documentation


Using the helm chart with internal services

External Contributor Checklist

🚨 Please review the guidelines for contributing to this repository.

[x] Make sure that all commits follow the conventional commit specification for the Mender project.

The majority of our contributions are fixes, which means your commit should have
the form below:
fix: simplifying the documentation for the new v5.0.0 helm chart

The new Helm chart v5.0.0 is delivering MongoDB and NATS as sub charts, so installing them manually is no longer required.

Changelog: simplifying the documentation for the new v5.0.0 helm chart
Ticket: MC-6807

[x] Make sure that all commits are signed with git --signoff. Also note that the signoff author must match the author of the commit.

Description
The new Helm chart v5.0.0 is delivering MongoDB and NATS as sub charts, so installing them manually is no longer required.

@mender-test-bot cherry-pick to:

3.3.x
3.4.x


Bulk exporting SharePoint online file metadata (specifically DriveItem unique id, path, filename)

Category

[x] Question
[ ] Documentation issue
[ ] Bug

Question
We have existing files in a SharePoint online site that we need to integrate with the Graph API (1.0) however the calls require the DriveItem item-id value
GET /drives/{drive-id}/items/{item-id}
Using the OneDrive file picker ( https://docs.microsoft.com/en-us/onedrive/developer/controls/file-pickers/js-v72/?view=odsp-graph-online) it's possible to extract this id manually when selecting files.
{       "webUrl": null,       "value": [{            "id": "01NJDWP4LK732UVFCO2ZCYLZF3QDARTUYT",            "parentReference": {                  "driveId": ""            },
However we need to be able to bulk export the item-id (and file name and path) for all files in a SharePoint online site to be able to integrate the data with an existing Graph API solution (which depends on the id value).
Looking to find out how to achieve this either from a functionality within the SharePoint online site or PowerShell script.
Thank you.
[ ]: http://aka.ms/onedrive-api-issues
[x]: http://aka.ms/onedrive-api-issues

As part of a repository clean up effort we are closing older issues. If this issue remains, please: open a new issue, reference this issue, and provide any additional details that may help in resolution. Thank you for your understanding as we work to improve our responsiveness.


Update Sysmon parsing to correct syntax and projection errors

When attempting to utilize the sysmon parsers we ran into many errors that should not typically exist.  These were duplicated in many different log analytics workspaces, empty and with sysmon data.  Depending on the type of data that existed in the workspace we would encounter different errors.
Proposed Changes

Renames incorrectly named data function SysmonEvent13__RegistrySetValue to SysmonEvent13_RegistrySetValue
Remove extraneous actions on Hashes when then column was not available
Use scalar types rather than dynamic when possible to avoid outer unions adding the hungarian notation _type suffix to column names
Formatting for readability and easier maintenance
Add many column_ifexists due to use of project on columns that are not always available

The use of the project following the union, only for intellisense, seems to add undue complexity to these parsers.  Removing the trailing project would be ideal but we have gone ahead and worked around the failures that it causes by adding column_ifexists when an error was produced.

internal reference: XDR-370

Hello @arledesma ! Would it be possible to go over some these comments here and compare to what you are suggesting. There a few recommendations that were similar (some of them) and that were already discussed in a previous PR (open still). I was able to updated the document in the OSSEM project which is where a python script was built to create the parser automatically:
Open PR: https://github.com/Azure/Azure-Sentinel/pull/1754
Current OSSEM Parser:  https://github.com/OTRF/OSSEM/blob/790f672c50df6da28f7c9f7e9a0118fca5a9c0bd/resources/parsers/SysmonKQLParserV13.01.txt
Once PR 1754 is approved then we can move that parser to the Azure-Sentinel repo. It was and is a community contribution from the OSSEM project.
A few things that I can add and also skip in the meantime:

scalar data types conversions for all fields
This registry function rename does not exist in the proposed config from PR 1754

reference: https://github.com/OTRF/OSSEM/blob/790f672c50df6da28f7c9f7e9a0118fca5a9c0bd/resources/parsers/SysmonKQLParserV13.01.txt#L266-L278

let SYSMON_REG_SETVALUE_13=() {
let processEvents = EventData
| where EventID == 13
| extend RuleName = EventDetail.[0].["#text"],
EventType = EventDetail.[1].["#text"],
UtcTime = EventDetail.[2].["#text"],
ProcessGuid = EventDetail.[3].["#text"],
ProcessId = EventDetail.[4].["#text"],
Image = EventDetail.[5].["#text"],
TargetObject = EventDetail.[6].["#text"],
Details = EventDetail.[7].["#text"]
| project-away EventDetail
;

I have also taken care of the hashes values on events where it does not apply.

Would you mind checking if there is anything specific that I am missing based on the previous open PR?
@shainw , regarding https://github.com/Azure/Azure-Sentinel/pull/1754 , we need to get feedback from user to maybe approve it and then work on anything left suggested in this one?
Thank you all for your patience and feedback!

Testing your changes in my tenant I noticed that EventID 1 was not showing up due to a hash parsing error (see screenshot)

Propose changing
| extend Hashes = extract_all(@"(?P<key>\w+)=(?P<value>[a-zA-Z0-9]+)", dynamic(["key", "value"]), Hashes)

to
| extend Hashes = extract_all(@"(?P<key>\w+)=(?P<value>[a-zA-Z0-9]+)", dynamic(["key", "value"]), tostring(Hashes))

After change

Testing your changes in my tenant I noticed that EventID 1 was not showing up due to a hash parsing error (see screenshot)

Propose changing
| extend Hashes = extract_all(@"(?P<key>\w+)=(?P<value>[a-zA-Z0-9]+)", dynamic(["key", "value"]), Hashes)

to
| extend Hashes = extract_all(@"(?P<key>\w+)=(?P<value>[a-zA-Z0-9]+)", dynamic(["key", "value"]), tostring(Hashes))

After change

Was this for all instances of extend Hashes for all of the Sysmon parsers?  I can probably generate some events that match but it would help if the original event(s) were available for me to write tests around.

@Cyb3rWard0g and @ashwin-patil to review and join together existing PR improvements for Sysmon Parser.

Sysmon will be supported by ASIM in the near future to align on the ease of parsing by a singular method via normalization


Can a small working demo project be in the repo for newbie users to see exactly what is going where?

I'm attempting to get the chart running in Chrome Version 68.0.3440.84 with not much luck at all.
I'm getting 'Unexpected Identifier' in Chrome Version 68 for imports/exports and transpiler wont fix it, using script type="module" only causes further issues such as 'Failed to resolve module specifier "vue". Relative references must start with either "/", "./", or "../".', however I feel that this may be due to me misinterpreting the setup.
A small demo project in the repo that users can download with only the minimal required html/js needed to produce the graph locally/on my server would be of great assistance. I know I must be missing something painstakingly obvious to get this running, so seeing a working setup would be great

A dead simple demo
<div id="app">
	<la-cartesian :width="300" :height="150" :data="values">
    <la-line prop="pv"></la-line>
    <la-y-axis></la-y-axis>
    <la-x-axis prop="name"></la-x-axis>
    <la-tooltip></la-tooltip>
  </la-cartesian>
</div>

<script src="//unpkg.com/vue"></script>
<script src="//unpkg.com/laue"></script>
<script>
	new Vue({
		el: '#app',
		data: () => ({
	    values: [
	      { name: 'Page A', pv: 2000 },
	      { name: 'Page B', pv: 3000 },
	      { name: 'Page C', pv: 1200 }
	    ]
	  })
	})
</script>

That did it, thanks. Looking forward to expanding from vue-trends to these full charts


Attribute Errors

Entry-level python programmer attempting to use minecart as shown in examples..
Installed minecart, pdfminer.six
Getting all sorts of attribute errors, slowly working through the documentation to remove errors
ex:
doc = minecart.Document(fp)

result -
AttributeError: module 'pdfminer.pdfparser' has no attribute 'PDFDocument'

then changed "miner.py", line 330 to:
self.doc = pdfminer.pdfdocument.PDFDocument(self.parser, caching=True)

this fixed the problem, and these two lines run properly...

doc = minecart.Document(fp)
doc2 = doc.iter_pages()

but now.....

page = doc.get_page(0)

result -
File "pdf_reader.py", line 28, in
page = doc.get_page(0)
File ".../minecart/miner.py", line 350, in get_page
for i, page in enumerate(self.doc.get_pages()):
AttributeError: 'PDFDocument' object has no attribute 'get_pages'

Is there a problem in the way the environment has been configured, or the versions of the packages that I'm using? I would greatly appreciate any help as I really want to use minecart !

You need to use pdfminer3k, not pdfminer.six.

Thanks for the timely response!
I have installed pdfminer3k as well. Is there a way I can make sure it is being used properly?

Make sure to uninstall pdfminer.six, something like pip uninstall pdfminer.six minecart should work out of the box in that setup. You may have to reinstall it if you've modified any files

OK, great! minecart is up an running. One more question: when opening a pdf file that requires decryption, how should I include the password?

Not sure. You're probably better off removing the password protection using something like pdftk first. I'm not sure if pdfminer supports password protected pdfs

Still having problems with this, even after removing pdfminer3k, pdfminer.six and minecart.

Did you got any solution @bjornasm  @cyberbruno

I had the same issue. I uninstalled pdfminer3k, pdfminer.six, pdfminer, pypdf2, and minecart. Then, I reinstalled minecart. Still had no luck.
I fixed it by uninstalling the poppler package (conda uninstall poppler) and then reinstalling minecart.

I too face "{AttributeError}module 'pdfminer.pdfparser' has no attribute 'PDFDocument'". I have reinstalled PDFminer3k 3 times now. Have reinstalled minecart 3 times aswell. I have uninstalled PDFMiner.six and I still get this.
I can't get access to miner.py to chnge the file becuase of permissions set my pip. I'm on Win 10. Whats even more anoying I can get to the directory where miner.py exists becuase Win 10 is telling me the directory don't exist.


Kick-off meeting

Kick-off Meeting Agenda
1. Welcome and Introduction

Brief opening to set the tone for the meeting.
Share the goals and expected outcomes of the session.

2. Project Overview

Discuss the project’s purpose and objectives.
Align on key milestones and deadlines.

3. Group Name and Repository Description

Brainstorm ideas for the group name.
Agree on a description and structure for the repository.

4. Task Distribution

List all key tasks for the project.
Collaboratively decide who will take on each task.

5. Planning and Organization

Outline the initial plan of action together.
Decide on tools, communication methods, and workflows.

6. Questions and Alignment

Clarify any uncertainties or open questions.
Ensure everyone has a shared understanding of the starting point and goals.

7. Next Steps

Summarize agreed-upon actions.
Set a timeline for follow-up discussions or progress updates.

Kick-Off Meeting Summary
Project: Calculator
Date: December 23, 2024

1. Project Overview
Group Name: Calculator (Subject to discussion)
Project Deadline: January 6, 2025 (All deliverables should be completed by this date)
Group Theme: Calculator
The project will focus on developing various functions as part of a calculator. Below is the list of possible functions. If you have additional ideas for functions, feel free to add them.
List of Possible Functions:

add: Adds two numbers and returns the result.
subtract: Subtracts the second number from the first and returns the result.
multiply: Multiplies two numbers and returns the result.
divide: Divides the first number by the second and handles division by zero.
modulus: Calculates the remainder of dividing two numbers.
power: Calculates the first number raised to the power of the second.
square: Calculates the square of a number.
square_root: Calculates the square root of a number.
factorial: Calculates the factorial of a number.
absolute_value: Returns the absolute value of a number.
calculate_average: Calculates the average of two numbers.
calculate_percentage: Calculates what percentage the first number is of the second.
find_max: Returns the larger of two numbers.
find_min: Returns the smaller of two numbers.
round_number: Rounds a number to the nearest integer or to a specified number of decimal places.
logarithm: Calculates the logarithm of a number to a specified base (default is base 10).
gcd: Finds the greatest common divisor (GCD) of two numbers.
lcm: Finds the least common multiple (LCM) of two numbers.
negate: Changes the sign of a number (positive to negative or vice versa).
convert_to_binary: Converts a number to its binary representation.
median: Finds the median of a list of numbers.
mode: Determines the mode (most frequent value) of a set of numbers.
exponentiation: A more general exponentiation function to raise any number to any power.

2. How We Work
Collaboration Model

Asynchronous Work: We will work asynchronously with follow-up calls every Monday afternoon (on December 30 and January 6).
Communication Tools:

GitHub: Use GitHub to track progress via the project board.
Slack: For daily collaboration and quick discussions.
GitHub Discussions: For technical topics, including .md files and functions. Create a new discussion if one does not exist.

3. Tasks for This Week

Files in Slack:
Two files are available in Slack. Each member should contribute to these files by the end of this week (Deadline: December 29). These files will help us align on group norms and will later be added to the .md file.

Personal Deliverables:
Begin working on your individual functions. The process for personal deliverables is the same as for team tasks. Ensure you check the work steps before contributing.

Group Files on GitHub:
There are 5 group files on GitHub. Collaboration from all members is needed. You can start working on them, and others will follow or contribute later.

4. Team Workflow and Collaboration Guidelines
Process for Starting Tasks

Create an Issue: If you want to start a task (whether personal or part of a team .md file), create an issue in GitHub.
Tracking: Add the issue to the project board and move it through the process.
Discussions: For team deliverables, create a discussion in GitHub for input and reminders.

1. Starting Team Tasks
Any team member can create an issue if they identify a task that needs to be done.
2. Personal Deliverables

Create an Issue: Ensure you create an issue first and add it to the project board so that everyone is aware of your progress.
Code Review:

Code reviews will be done by the person who marks the task as "Ready to Review" on the project board.
Ensure code quality before merging it into the main branch.

3. Contribution Requirements
Each member should complete at least 2 personal tasks and perform 2 code reviews.

5. Final Notes
Communication:
If you need help, don’t wait until Monday. We can arrange 1-on-1 sessions, text chats, or anything that works best for you.
Collaboration:
Let’s communicate openly and track progress via GitHub to stay on the same page.

6. Additional Guidelines

Branching:
All development should occur in a separate branch. The branch name should reflect the task it covers. Merges to the main branch will only be possible after a review.

You all are wonderful people to work with. I appreciate your passion and commitment; it is driving me to get my hands dirty with work and not minding my skill level.

Thank you all for your contributions and I am confident we will make great progress together. Cheers!

Thanks for the efforts in outlining the scope and the procedure to complete the tasks requied. Now that things are clear, lets get down to business.


vision: remove camera cap check and unused speak capability

Summary

Removes redundant camera cap check in vision
Proposed changes

As the camera cover/cap check has been implemented in the camera driver with proper diagnostics, this check in the vision became redundant.
This PR removes the vision check and the speak capability, as it has no use anymore.
Related issues

Closes #462
#455
Checklist

[ ] Run colcon build
[ ] Write documentation
[ ] Test on your machine
[ ] Test on the robot
[ ] Create issues for future work
[X] Triage this PR and label it

I still think that the audio warning is nice. Even if the functionality is now located in the basler driver. We should debug either way why the audio is not played during startup.

If I remember correctly, we now have a simpler function in misc to speak. We should use that one instead. And I agree, we should speak this warning. However, I don't think it should be located in this vision anymore.

function in misc

I don't know what you mean. There is a simple factory for the speak messages, but it is barely needed and only python (the basler driver is cpp).

Yes, that's the one I meant. And yes, its only for python nodes...
My preference for which node should say the warning:

Gameready-script
Something in Misc
Vision
Basler driver

I think integrating it into the basler would be fitting as we have a check there either way. But I just had the following idea:
Diagnostic state to tts! We just say (some) if the arbitrary diagnostic states. Therefore the robot tells us if the camera is overheating, the cap is on there or if the motors are stale/overloaded.


[libpq] Fix build failure when vcpkg path contains spaces

This fixes libpq not building when vcpkg is installed in a path with spaces (due to unquoted paths).
Not sure a port version bump is necessary since this doesn't change the output.

@JackBoosY Done

/azp run


Optionally provide path/link to file with transpilation error

I see this in my terminal:

I have two feature requests:

for us hard of seeing people, it's really hard to read the cyan and yellow color in a light terminal.
Is there some way to turn on darker colors - by passing a dark/light option to pretty?

It would be awesome if the transpiler could include the path to the file in the terminal. My editor is cool and if I click the file path in the terminal it will open the file.

My tsconfig.json is:

    {
      "compilerOptions": {
        "outDir": "dist",
        "allowJs": false,
        "pretty": true,   // << makes it pretty, but I can't read in a light-colored terminal
        "resolveJsonModule": true,
        "sourceMap": false,
        "skipLibCheck": true,
        "rootDir": "src",
        "declaration": false,
        "baseUrl": ".",
        "target": "es2018",
        "module": "commonjs",
        "noImplicitAny": true,
        "removeComments": true,
        "allowUnreachableCode": true,
        "lib": [
          "es2017",
          "es2018"
        ]
      },
      "compileOnSave": false,
      "include": [
        "src"
      ]
    }

The path is right there in the error message?

yeah, maybe webstorm/intellij can only work with an absolute path. but the color thing I suppose is more important, I assume jetbrains products could be made to interpret the relative path.


(BKR-650) removes lines that modify self.hosts  Fixes confine :to logic

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1965/
Test FAILed.

I need to consider the case where a call is made to confine with out a hosts argument ( and where hosts are iterated over in the block that is passed in.  Nate says I broke this.


[Bug Report] Expected to use , rather than <Menu.name /> for JSX statements

Element UI version
2.12.0
OS/Browsers version
Any
Vue version
2.6.10
Reproduction Link
https://codepen.io/snyang/pen/vYYdNxp
Steps to reproduce
Expected to use , rather than <Menu.name /> for JSX statements.
What is Expected?
import { Menu } from 'element-ui';
...
// expected
render(h: any): JSX.Element {
	return (<Menu router={true}>
		{this.renderSubMenu(h)}
	</Menu>
	);
}

What is actually happening?
import { Menu } from 'element-ui';
...
// actual
render(h: any): JSX.Element {
	return (<Menu.name router={true}>
		{this.renderSubMenu(h)}
	</Menu.name>
	);
}

Please close it, it seems that it is Vue underlying logical.


Don't retry if the command is not possible for non-communication related reasons

For example if the car is not charging, charging cannot be stopped:
2024/06/27 01:00:52 INFO received command command=charge_stop VIN=xxx body=map[]
2024/06/27 01:00:53 INFO handle command command=charge_stop VIN=xxx
2024/06/27 01:00:56 WARN failed to stop charge: car could not execute command: not_charging
2024/06/27 01:00:56 INFO retrying in 3 seconds
2024/06/27 01:01:02 WARN failed to stop charge: car could not execute command: not_charging
2024/06/27 01:01:02 INFO retrying in 6 seconds
2024/06/27 01:01:11 WARN failed to stop charge: car could not execute command: not_charging
2024/06/27 01:01:11 INFO retrying in 12 seconds
2024/06/27 01:01:27 WARN failed to stop charge: car could not execute command: not_charging
2024/06/27 01:01:27 INFO retrying in 24 seconds
2024/06/27 01:01:54 WARN failed to stop charge: car could not execute command: not_charging
2024/06/27 01:01:54 INFO retrying in 48 seconds
2024/06/27 01:02:46 ERRO stop retrying after 6 attempts
2024/06/27 01:02:46 ERRO The command was canceled. command=charge_stop err="failed to stop charge: car could not execute command: not_charging"
The same goes for starting charging when the car is already charging. That fault would be is_charging.
IMHO retrying doesn't make sense in these cases. The retry then clogs the command queue while other requests that make more sense could be executed.

Thank you! I have made an update so these command. So we don't retry if the vehicle is already charging respectively has stopped charging.


Add (Cluster)OpenIDConnectPreset resources

What this PR does / why we need it:
This PR adds the following:

new settings.gardener.cloud API group
OpenIDConnectPreset and ClusterOpenIDConnectPreset
New fields in the Shoot specification allowing for generation of kubeconfigs with OpenIDConnect settings in them
OpenIDConnectPreset and ClusterOpenIDConnectPreset mutation admission controllers which apply those Presets to Shoot objects on CREATE requests.

Which issue(s) this PR fixes:
Fixes #1161
Special notes for your reviewer:
Release note:

The new `ClusterOpenIDConnectPreset` resource allows for specifying OpenID Connect configurations which are applied to `Projects` and `Shoot` cluster-wide.

Two new mutation admission controllers are introduced - `ClusterOpenIDConnectPreset`  and `OpenIDConnectPreset`. Those controllers can are enabled by default and can be disabled with `--disable-admission-plugins` flag on gardener-apiserver.

The new `OpenIDConnectPreset` resource allows for specifying OpenID Connect configurations which are applied to `Shoot` namespace-wide.

A new optional field in `Shoot` specification has been added `spec.kubernetes.kubeAPIServer.oidcConfig.clientAuthentication`. It can specify OpenID Connect settings used for `kubeconfig` generation.

`./hack/dev-setup-register-gardener` must be ran to register the new `settings.gardener.cloud` API group.

/cc @vasu1124

According to my understanding ClusterOpenIDConnectPreset resources should only be set by operators/administrators, but not by end-users. End-users shall only use OpenIDConnectPreset resources in their project namespace(s). --> Please add the required RBAC roles to the https://github.com/gardener/gardener/blob/master/charts/gardener/charts/application/templates/rbac-user.yaml file.

Fixed in be33f37

I don't see that the clientConnection field in the OIDC config structure is used anywhere. Do I miss something?

I'll add openid connect kubeconfig generation later on

Please add a release note that developers have to run ./hack/dev-setup-register-gardener to register the new settings.gardener.cloud API group.

Done.
@ialidzhikov
I'll add the specification field

I'll add openid connect kubeconfig generation later on

ok, can you please create an issue and assign yourself?

@ialidzhikov Cluster/OpenIDConnectProviderPreset now have a specification. 8e8440e
@rfranzke I've create a #1433 issue for this.

Why did you rename the API group? I actually liked settings.gardener.cloud. @mandelsoft asked, once you have completed the first implementation of this API group, to introduce a DNSProvider resource in settings.gardener.cloud where end-users/project-owners may define standard DNS settings (similar to the standard OIDC settings you implemented). Now, with authentication.gardener.cloud this doesn't fit anymore and the concept cannot be extended without tremendous effort (of introducing a new API group again).

I'll revert the change group commit.

Okay everything is back to settings.gardener.cloud

@ialidzhikov can you please take a second look so that we can get this merged?

@ialidzhikov can you please take a second look so that we can get this merged?

I am on it. Sorry for the delay.


Suggestion for better release properties

include description for jobs (example: https://github.com/concourse/concourse/blob/master/jobs/atc/spec#L4)
rename docker_registry.storage.name to docker_registry.storage.provider
rename docker_registry.storage.s3.accesskey to docker_registry.storage.s3.access_key
rename docker_registry.storage.s3.secretkey to docker_registry.storage.s3.secret_key
make docker's port configurable and default to 4243 (https://github.com/cloudfoundry-incubator/diego-docker-cache-release/blob/d9194460276e00c78ee076f1ff45ed0127136d32/jobs/docker/templates/ctl.sh#L28)

Thanks, @cppforlife! Gitbot isn't tracking this repo yet, so made https://www.pivotaltracker.com/story/show/100861820 in the Diego tracker for this.


Add a test ensuring streamed response will error if EOF is received early

Motivation and Context

#1801
Description

The SDK depends on our HTTP client (hyper) to return an error in the event that a connection is closed early and only a portion of the response body is received. This PR adds a test that exercises that error.
Testing

The PR adds a test.
Checklist

[x] I have updated CHANGELOG.next.toml if I made changes to the AWS SDK, generated SDK code, or SDK runtime crates

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

If the test is run with logging, the logs look like this:
2022-10-25T18:22:49.387881Z DEBUG hyper_rustls::config: with_native_roots processed 160 valid and 0 invalid certs
2022-10-25T18:22:49.389304Z DEBUG aws_endpoint: resolved endpoint endpoint=Endpoint { url: "http://localhost:3000/", headers: {}, properties: {"authSchemes": Array([Object({"name": String("sigv4")})])} } base_region=None
2022-10-25T18:22:49.390822Z DEBUG hyper::client::connect::dns: resolving host="localhost"
2022-10-25T18:22:49.392746Z DEBUG send_operation{operation="GetObject" service="s3"}: hyper::client::connect::http: connecting to <IP_ADDRESS>:3000
2022-10-25T18:22:49.393251Z DEBUG send_operation{operation="GetObject" service="s3"}: hyper::client::connect::http: connected to <IP_ADDRESS>:3000
2022-10-25T18:22:49.393254Z DEBUG streaming_response: server received new connection from <IP_ADDRESS>:53605
2022-10-25T18:22:49.393311Z DEBUG streaming_response: would block, looping again after small 1ms nap
2022-10-25T18:22:49.393947Z DEBUG hyper::proto::h1::io: flushed 639 bytes
2022-10-25T18:22:49.395154Z DEBUG streaming_response: read 64 bytes from the socket reader
2022-10-25T18:22:49.395168Z DEBUG streaming_response: buf currently looks like:
"GET /some-test-bucket/test.txt?x-id=GetObject HTTP/1.1\r\nuser-age"
2022-10-25T18:22:49.395181Z DEBUG streaming_response: read 64 bytes from the socket reader
2022-10-25T18:22:49.395188Z DEBUG streaming_response: buf currently looks like:
"GET /some-test-bucket/test.txt?x-id=GetObject HTTP/1.1\r\nuser-agent: aws-sdk-rust/0.51.0 os/macos lang/rust/1.62.0\r\nx-amz-user-ag"
2022-10-25T18:22:49.395198Z DEBUG streaming_response: read 128 bytes from the socket reader
2022-10-25T18:22:49.395204Z DEBUG streaming_response: buf currently looks like:
"GET /some-test-bucket/test.txt?x-id=GetObject HTTP/1.1\r\nuser-agent: aws-sdk-rust/0.51.0 os/macos lang/rust/1.62.0\r\nx-amz-user-agent: aws-sdk-rust/0.51.0 api/s3/0.0.0-local os/macos lang/rust/1.62.0\r\nx-amz-date: 20221025T182249Z\r\nauthorization: AWS4-HMAC-SH"
2022-10-25T18:22:49.395217Z DEBUG streaming_response: read 256 bytes from the socket reader
2022-10-25T18:22:49.395223Z DEBUG streaming_response: buf currently looks like:
"GET /some-test-bucket/test.txt?x-id=GetObject HTTP/1.1\r\nuser-agent: aws-sdk-rust/0.51.0 os/macos lang/rust/1.62.0\r\nx-amz-user-agent: aws-sdk-rust/0.51.0 api/s3/0.0.0-local os/macos lang/rust/1.62.0\r\nx-amz-date: 20221025T182249Z\r\nauthorization: AWS4-HMAC-SHA256 Credential=ANOTREAL/20221025/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date;x-amz-security-token;x-amz-user-agent, Signature=d6c2c8561462b5ae2a7241e04a44e115a80396e5b1c1d36a754388eb0ad02aef\r\nx-amz-content-sha256: e3b0c44"
2022-10-25T18:22:49.395579Z DEBUG streaming_response: read 127 bytes from the socket reader
2022-10-25T18:22:49.395586Z DEBUG streaming_response: buf currently looks like:
"GET /some-test-bucket/test.txt?x-id=GetObject HTTP/1.1\r\nuser-agent: aws-sdk-rust/0.51.0 os/macos lang/rust/1.62.0\r\nx-amz-user-agent: aws-sdk-rust/0.51.0 api/s3/0.0.0-local os/macos lang/rust/1.62.0\r\nx-amz-date: 20221025T182249Z\r\nauthorization: AWS4-HMAC-SHA256 Credential=ANOTREAL/20221025/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date;x-amz-security-token;x-amz-user-agent, Signature=d6c2c8561462b5ae2a7241e04a44e115a80396e5b1c1d36a754388eb0ad02aef\r\nx-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855\r\nx-amz-security-token: notarealsessiontoken\r\nhost: localhost:3000\r\n\r\n"
2022-10-25T18:22:49.396108Z DEBUG streaming_response: faulty server has written partial response, now closing connection
2022-10-25T18:22:49.396127Z DEBUG streaming_response: connection to <IP_ADDRESS>:53605 closed after 2.83ms
2022-10-25T18:22:49.396311Z DEBUG hyper::proto::h1::io: parsed 10 headers
2022-10-25T18:22:49.396319Z DEBUG hyper::proto::h1::conn: incoming body is content-length (12 bytes)
2022-10-25T18:22:49.396678Z DEBUG hyper::proto::h1::conn: incoming body decode error: end of file before message length reached


doc: Add CNI chaining documentation for Kube-OVN

Document how to use the generic-veth chaining plugin in combination with Kube-OVN.
Signed-off-by: oilbeater<EMAIL_ADDRESS>Please ensure your pull request adheres to the following guidelines:

[ ] For first time contributors, read Submitting a pull request
[ ] All code is covered by unit and/or runtime tests where feasible.
[ ] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[ ] All commits are signed off. See the section Developer’s Certificate of Origin
[ ] Provide a title or release-note blurb suitable for the release notes.
[ ] Thanks for contributing!

can you please explain what --set enableIdentityMark=false does? I'm not familiar with the option

This option is not documented now, but from the source code here:
https://github.com/cilium/cilium/blob/master/pkg/option/config.go#L308
Without this option, Cilium will add mark to traffic that can be conflict with Kube-OVN mark

Hi, any update on this？

I'll mark this as draft until I see feedback on the latest comment above. Feel free to mark it as "ready for review again" and ping me when there is an update. Thanks!


Confirmation dialog for instance deletion

Confirmation for end-user instance deletion.

If you selecting using check-boxes, then I am putting a confirmation dialog, in case you want to delete it using destroy button one by one, there can be no confirmation. This is for the admin view.


move IMU integration to sensors/vehicle_imu to fix potential accel/gyro sync issues

IMUs now only publish sensor_accel + sensor_gyro (sensor_accel_fifo/sensor_gyro_fifo optional extra)

move accel & gyro integration to sensors/vehicle_imu where we can ensure synchronization between data
delete sensor_accel_integrated/sensor_gyro_integrated
merge sensor_accel_status/sensor_gyro_status into vehicle_imu_status

new uORB::SubscriptionCallback mechanism to throttle callbacks by number of updates

update: 1s, num topics: 68
TOPIC NAME       INST #SUB RATE #LOST #Q SIZE
vehicle_imu         0    3  200   226  1   56
vehicle_imu_status  0    3  200     0  1   56
vehicle_imu         1    3  200   226  1   56
vehicle_imu_status  1    3  200     0  1   56
vehicle_imu         2    3  199   225  1   56
vehicle_imu_status  2    3  199     0  1   56

TODO:

[ ] SITL lockstep issues
[ ] test clipping still works correctly
[x] test bmi088
[ ] test bmi055
[ ] test nxphlite (separate accel + gyro)
[ ] test lsm303d + l3gd20 combo (pixhawk 1 & 2 secondary IMU)

FYI @bkueng @bresch

@dagar I tested that on a BMI088 and the sensor combined data is now free of duplicates!

If the flow of data seems a bit weird with sensors kicking off multiple VehicleIMU WorkItems that it then subscribes to it's because this is intended to accommodate the multi-EKF use case where the simple IMU voter (voted_sensors_update) may not even be needed.
https://github.com/PX4/Firmware/pull/14650

This saves ~2.3 kB of flash on fmu-v2 and ~3.4 kB on fmu-v5.

Can you ensure the vehicle_imu publication ordering? I.e. advertisement on object creation and creation ordering.

Done.

What is your testing and confidence level?

Reasonably confident for something that's never flown. I'm going to manually verify a few things like the propagation of clip counters. I'd also like to review bench log data from the non-synchronized cases we care about (bmi088, bmi055, nxp, original pixhawk, etc) and check for any surprises in the delta_angle_dt/delta_velocity_dt and ekf2 timeslip.
Reviewing an actual flight test with a bmi088 as primary would be great.

I still see a possibility for vehicle_imu reordering: intantiation is based on accel.device_id > 0 && gyro.device_id > 0, so it could be that a later IMU already has its ID published.

In the current PR sensors indexes VehicleIMUs as _vehicle_imu_list[X] = sensor_accelX + sensor_gyroX. One simple idea could be to only build up that list sequentially. The sensors module is rescanning the available accels & gyros up until arming.
Originally I was planning to pursue this post https://github.com/PX4/Firmware/pull/14776 where the ordering will no longer matter. At that point I'd also like to do a pass to have sensors put more effort into the IMU accel + gyro pairing. Things like first pairing up matching device IDs, then remaining accel + gyro on the same bus, and only then pairing up the leftovers.

One simple idea could be to only build up that list sequentially. The sensors module is rescanning the available accels & gyros up until arming.

Yes I would do so as well for now.

I've flown this with the BMI088: https://logs.px4.io/plot_app?log=5e57bfbc-ed5a-46fa-8489-c06a6f4e0253 (vehicle_imu is logged at full rate).
And found one problem:

There are cases with 10 samples instead of the required 5. This happens due to the callback rate limitation, and using
		_sensor_accel_sub.set_required_updates(1);
		_sensor_gyro_sub.set_required_updates(1);

avoids the problem. I didn't check the difference in CPU load.

I've flown this with the BMI088: https://logs.px4.io/plot_app?log=5e57bfbc-ed5a-46fa-8489-c06a6f4e0253 (vehicle_imu is logged at full rate).
And found one problem:

Quick idea in https://github.com/PX4/Firmware/pull/14906/commits/2acb84cab914f3498248b88958a4a4fa6d66ef1b. First integrate all available gyro, then take all accel, but stop once caught up with the last integrated gyro sample.

There are cases with 10 samples instead of the required 5. This happens due to the callback rate limitation, and using
		_sensor_accel_sub.set_required_updates(1);
		_sensor_gyro_sub.set_required_updates(1);

avoids the problem. I didn't check the difference in CPU load.

You can get away with it on stm32f7 with a single IMU, but it's too much in other cases. If the last commit doesn't improve things we can try something in between.

I gave up on the minimum interval time requirement in addition to the number of samples and I believe things are now under control on the BMI088. The publication rate of the BMI088 isn't nearly as regular as the other new drivers using FIFOs and interrupts.
For example the BMI088 vs ICM20602 publication intervals on the Modalai board. Note this also includes the initial period before the actual publication rate is computed and integration is configured to an appropriate number of samples. http://ci.px4.io:8080/blue/organizations/jenkins/PX4_misc%2FFirmware-hardware/detail/pr-sensors_vehicle_imu_integrate/54/pipeline/399#step-790-log-64
BMI088
vehicle_imu: publish interval: 41990 events, 5014.34us avg, min 4036us max 7055us 136.370us rms
vehicle_imu: accel update interval: 169309 events, 1243.74us avg, min 367us max 2551us 87.115us rms
vehicle_imu: gyro update interval: 209988 events, 1002.87us avg, min 224us max 3043us 164.365us rms

ICM20689
vehicle_imu: publish interval: 42162 events, 4990.85us avg, min 4649us max 5352us 37.751us rms
vehicle_imu: accel update interval: 168664 events, 1247.73us avg, min 1222us max 1273us 2.603us rms
vehicle_imu: gyro update interval: 168676 events, 1247.73us avg, min 1222us max 1273us 2.603us rms

Occasionally it's integrating an extra gyro sample. I was experimenting it breaking out of the orb_copy + integration loop once the integrator minimum requirements are satisfied. It's not included at the moment because of concerns with falling behind the raw data.

Occasionally it's integrating an extra gyro sample. I was experimenting with breaking out of the orb_copy + integration loop once the integrator minimum requirements are satisfied. It's not included at the moment because of concerns with falling behind the raw data.

Should be fixed with the last push.

Zooming in you can also get a sense of the (minimal) remaining real-time jitter in the system. The y axis is integration time (4 gyro samples in this case) in microseconds.

Note: mavlink SCALED_IMU, SCALED_IMU2, SCALED_IMU3 are now in the vehicle body frame (including board level adjustments).

The mavlink spec doesn't indicate the frame, but I'd imagine this is what people would expect.


Fix temporary directories used for temporary values files are left over

fix #540
Signed-off-by: xiaomudk<EMAIL_ADDRESS>

what's different between this pr and https://github.com/helmfile/helmfile/pull/563?

@yxxhero I found that pr #563 is also a good solution to this problem. I will close this pr.


Remove CaseEncoder

This should now be done with the CaseTemplateEncoder, and it is confusing to have too many possibilities

done


fix(CreateTearsheet): add custom button

Closes https://github.com/carbon-design-system/ibm-products/issues/4380
Add custom (4th) button to CreateTearsheet
What did you change?

Added an optional prop for custom button text to CreateTearsheet

customButtonText?: string;

Added optional props for custom button to CreateTearsheetStep

customButtonChangeText?: string;
isCustomButtonDisabled?: boolean;
isCustomButtonHide?: boolean;
onCustomButtonClick?: () => void;

Created storybook for custom button
Added unit test

How did you test and verify your work?

Manual tests via storyboard
Added unit test

https://github.com/user-attachments/assets/dbb4b401-1216-4c01-9325-271152498515

I have read the DCO document and I hereby sign the DCO.

thank you for contributing. looks good to me!
i just want to double check with @sstrubberg on this. this was in icebox but didn't have any label for needs design opinion. just want to verify that this is fine on the design side before merging.

Thanks for checking in! @oliviaflory @kingtraceyj @aubrey-oneal Can ya'll weigh-in here from a UX/Visual pov?

thank you for contributing. looks good to me!
i just want to double check with @sstrubberg on this. this was in icebox but didn't have any label for needs design opinion. just want to verify that this is fine on the design side before merging.

Thanks for checking in! @oliviaflory @kingtraceyj @aubrey-oneal Can ya'll weigh-in here from a UX/Visual pov?

It would be great if get a review and approval

@ljcarot can you weigh in?

@davidmenendez @Sreejith-CS I noticed that the Skip button doesn't actually take the user to the next step in the Create flow.
I'm wondering if that is intentional? Is the 4th button just intended for demo purposes and an adopter would have to add the logic to go to the next step? From the original issue I am not 100% sure on the use case and UX intention

@oliviaflory Thanks for the review. Consider the following points.
This change is to create a custom button on the CreateTearsheet. So let's add custom text to the button label. If there is a button labeled Skip, our requirement is to skip all the remaining steps and it will act as the submit button. If the custom button behaves like the next button, there's no use specifying it, because Next and Skip will do the same behaviour.

@oliviaflory Thanks for the review. Consider the following points.
This change is to create a custom button on the CreateTearsheet. So let's add custom text to the button label. If there is a button labeled Skip, our requirement is to skip all the remaining steps and it will act as the submit button. If the custom button behaves like the next button, there's no use specifying it, because Next and Skip will do the same behaviour.

@Sreejith-CS that is fair, I would advise your UX designer to consider whether skipping all remaining steps and submitting is really clear to the user when a button is labeled "Skip", but will not block the addition.
Revised request:

Please remove the story Create tearsheet with custom button. It would be best to mirror the existing 4 button approach that is in the Tearsheet and showcase the 4th button in a control as seen here

actions prop with options to select the buttons:

Three buttons with one ghost
Four buttons with one ghost

The Custom action button should be between the Back and Replace buttons (the same as the tear sheet examples)

@oliviaflory Please consider the following points.

@Sreejith-CS that is fair, I would advise your UX designer to consider whether skipping all remaining steps and submitting is really clear to the user when a button is labeled "Skip", but will not block the addition.

We can add label like `Skip all steps'.

Revised request:

Please remove the story Create tearsheet with custom button. It would be best to mirror the existing 4 button approach that is in the Tearsheet and showcase the 4th button in a control as seen here

actions prop with options to select the buttons:

Three buttons with one ghost
Four buttons with one ghost

We cannot display the custom (4th) button (as a dropdown option) because there are no actions props in the CreateTearsheet. So I think we should keep the story of Create tearsheet with custom button.  So that user can understand each of the props (customButtonText , customButtonChangeText, isCustomButtonDisabled, isCustomButtonHide, onCustomButtonClick). Controls have option customButtonText so we can show custom button.
https://github.com/user-attachments/assets/3582dbca-0239-4575-8b4c-404def1d6ada

The Custom action button should be between the Back and Replace buttons (the same as the tear sheet examples)

This has been implemented.

Hey @Sreejith-CS! Thanks for all your hard work here. But I think we need to re-evaluate the approach taken here as it adds ~5 new props and is not a composable approach that we'd ideally like to see for the CreateTearsheet actions. Our team will add more detailed acceptance criteria to #4380 and move it from the "Icebox" when ready.

@matthewgallo I have updated the code as per discussion and review comments. Please review it

@matthewgallo @elycheea @davidmenendez It would be great if get a review and approval

Thanks for working on these changes @Sreejith-CS! We'll work on reviewing this again 🎉

Thanks @matthewgallo
@davidmenendez @oliviaflory Could you please review

Hey @Sreejith-CS!
@davidmenendez @matthewgallo @oliviaflory and I had some additional discussion on the prop(s) naming and wanted to propose one more change to the naming — instead of experimentalAlternateSubmit we want to suggest experimentalSecondarySubmit.
I know we originally discussed the former as a possible name, but on further review think it could also be interpreted as an alternative to the existing submit rather than additional. We believe the experimentalSecondarySubmit prefix would be a bit clearer than experimentalAlternateSubmit.
Lastly, we would still like to remove the story before we bring this change in. While it’s helpful for us to see and review it, I do think it’s not necessarily a feature we’re currently encouraging, especially as an experimental option.

@davidmenendez @matthewgallo @oliviaflory @elycheea  Thanks for the review. I have updated according to all your review comments. Could you please review again.


Crank the Handle: Update Ansible

Ansible 2.11 and 2.12 are stable.

Pull request 19 contains updated alpine/ansible files.
I've removed the legacy ansible roles and done a test run on my fork. Would like to test it a little harder when I get chance before creating a pull request.


Create BND entries from both sides on SV import

Is your feature request related to a problem? Please describe.
As mentioned in https://github.com/bihealth/varfish-server/issues/32#issuecomment-1103899660, we need BND records for both sides. This should not only be present when building the background database but also when filtering records.
Describe the solution you'd like
During the import of SV variants we should ensure that we have records for both sides of a breakend without introducing duplicate records. Further, we need to properly capture in svs.models.StructuralVariant that the second breakpoint can be on a second chromosome. This will require adjustments in varfish-annotator. This also implies that all SVs must be re-imported.
Describe alternatives you've considered
N/A
Additional context

#32

Resolved in varfish-annotator, v0.23 release: https://github.com/bihealth/varfish-annotator/issues/45


ability to see history from single exercise

As far as I can see v1.0.69 contained this button on the graph page that allowed to see the history for that single exercise
https://github.com/brandonp2412/Flexify/blob/b435e86d28719569f84268259af6417f7317d2da/fastlane/metadata/android/en-US/images/phoneScreenshots/5_en-US.png
After v1.0.69 the button was removed, and looking at the history for a single exercise now would entail searching for the exercise via the search bar on the history page. Was this functionality removed intentionally?
[ Reappearance of #28 ]

Yeah I removed it because I figured nobody would notice since I added the history page, but I can add it back in. Looking at it now i do like how the fab looks with a history icon on it.


A Base64 encoded word cannot be longer than 75 chars (e.g. Subject, To, From etc.)

See http://en.wikipedia.org/wiki/MIME#Encoded-Word for details.

Implemented, it's super effective!


Update calibre to 3.13.0

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Duplicate of https://github.com/caskroom/homebrew-cask/pull/41516
Thanks for the PR nonetheless.


Fix link to documentation

Hi,
Last time I worked on this repo, I noticed the link to the Docs was broken.
Thanks!

Thanks, Dan!


⚠ Avatar API Endpoint has degraded performance

In 352d02b, Avatar API Endpoint (https://avatar.roblox.com/v1/avatar-rules) experienced degraded performance:

HTTP code: 200
Response time: 5706 ms

Resolved: Avatar API Endpoint performance has improved in 13354fd after 16 minutes.


Checkbox Group component shows some unselected values as selected

When a checkbox group has values that include other values, it shows unselected values as selected, state works correctly.
Examle values:
50 100 150
When 50 selected
state: [50]
elements that are showns as active: [50, 150]

I couldn't reproduce this as well together with #596 Probably they are related, so maybe an example will cover both.


Fixed a typo in the #[cfg()] of gettimeofday.

The #[cfg()] was looking for 'arget_os' instead of 'target_os'.

Possibly needs restarting of job: https://travis-ci.org/rust-lang-nursery/libc/jobs/107422617

Oops, thanks! Can you rebase and re-push as well? (just merged another PR)

Oh looks like this picked up a few extra commits, perhaps a rebase is in order?

also feel free to ping the PR whenever you update, unfortunately github doesn't send out notifications for events like that

@alexcrichton Rebased the pull request. Please merge this if you can.

Hm looks like there are still some stray commits here? Perhaps a reset --hard to what's currently on master plus a cherry-pick of the relevant commit?


No files displayed in the browser

Hello
I had an older version of IPFS (0.4.11) with a bunch of files.
The Files Explorer was able to display the files stored into my local storage.

After upgrading to 0.4.16, the Files Explorer is not displaying my files anymore.

Did I miss something during the update process?
Thanks
Said

We've changed the Files panel to display files stored in MFS (take a look at the ipfs files commands). I'm not sure but it looks like that panel used to list all recursive pins (everything listed by ipfs pin ls --type=recursive). If you'd like, you can add those to MFS by running:
ipfs files mkdir /pins/
for p in $(ipfs pin ls -q --type=recursive); do
    ipfs files cp /ipfs/$p /pins/
done

That will add all of your the files/folders you've added to IPFS to the /pins/ directory in MFS.

Hi @Stebalien
It works.
Thanks for your help!

Closing this! Thanks @Stebalien


RF: Reflect function name on nipype workflow

Minor (but breaking) change - I spent way too long looking for morph_grayords_wf in the working directory...

I'm okay with targeting 0.11.1 if you are 😄


Update README.md

In section Roboto Font and Material Design Icons update link to Roboto font.
Now links to https://fonts.google.com/specimen/Roboto.

Thanks!


Updates slack badge on README with users count

Signed-off-by: sachinmukherjee<EMAIL_ADDRESS>
What this PR does / why we need it:
It updates the slack badge with users count. currently, it is broken
Which issue this PR fixes: fixes https://github.com/openebs/openebs/issues/559

@sachinmukherjee there are some conflicts in README.md. can you resolve ?

@do i need to fetch latest changes from upstream and again commit and send PR?

@sachinmukherjee yes, fetch the upstream changes and rebase your branch.
There are alignment issue with slack badge after new changes.

@prateekpandey14 I will do that Please assign this issue to me

@sachinmukherjee  The issue with the slack badge was that a square badge matching other badges was not available. I am closing this PR. It will be great if you can check if the slackin has the fix for a flat-square badge that can give current status.


Missing helper file

Trying to run the rails code but experiencing the following error when running rspec (or the server):
/Users/mnsteen/.rvm/gems/ruby-2.2.3@twiliodeved/gems/actionpack-4.2.0/lib/abstract_controller/helpers.rb:151:in `rescue in block in modules_for_helpers': Missing helper file helpers//users/mnsteen/code/hallometrics/twilio_dev_ed/call_tracking_rails/app/helpers/application_helper.rb_helper.rb (AbstractController::Helpers::MissingHelperError)

Seems to be an issue with ruby 2.2.3, got app working with 2.1.5 (for example), so closing...

@neetso thanks for letting us know.


Purchase flow visual polish

Motivation / Description
I wanted to make some layout improvements and got sidetracked.
Changes introduced

Remove close buttons, instead have an X in the top right corner
Make the success / error icons smaller
Make light buttons have dark text on them

Linear ticket (if any)
Additional comments

          1 Error

:no_entry_sign:
Label the PR using one of the change type labels. If you are not sure which label to use, choose pr:other.

Label
Description

pr:feat
A new feature. Use along with pr:breaking to force a major release.

pr:fix
A bug fix. Use along with pr:force_minor to force a minor release.

pr:other
Other changes. Catch-all for anything that doesn't fit the above categories. Releases that only contain this label will not be released. Use along with pr:force_patch, or pr:force_minor to force a patch or minor release.

pr:RevenueCatUI
Use along any other tag to mark a PR that only contains RevenueCatUI changes

pr:next_release
Preparing a new release

pr:dependencies
Updating a dependency

pr:phc_dependencies
Updating purchases-hybrid-common dependency

  Generated by :no_entry_sign: Danger

Closing this PR, this has all been incorporated into #209

Just to confirm, should this be closed then?

Yep I meant to close this but apparently clicked the wrong button :)


Saml2Profile is not populating roles.

When integrated with SAML provider profile is not loading roles given by the provider.

It should work. The BaseClient has the getUserProfile method which relies on the retrieveUserProfilemethod: https://github.com/pac4j/pac4j/blob/master/pac4j-core/src/main/java/org/pac4j/core/client/BaseClient.java#L234 and computes the roles according to the provided authorization generators. The Saml2Client only implements the retrieveUserProfile method.
Would you mind providing me with further details? Thanks


MODCLUSTER-432 Ignore failing tests on Mac OS X (Maverics)

In case we decide to proceed with the Beta release...

Triggering build using a merge of 3859776a540644c254fb5d236ef1ef057d4e54c4 on branch master:
Private: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/mod_cluster-1.3.x-pull-player-executor/

Build 132 outcome was SUCCESS using a merge of 3859776a540644c254fb5d236ef1ef057d4e54c4 on branch master:
Private: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/mod_cluster-1.3.x-pull-player-executor/132
Public: https://hudson.jboss.org/hudson/job/mod_cluster-1.3.x-pull-player-executor/132