Download as pdf with attached csv

Modeling the behavior we want from data publishers 😊

+1. Wow! From a lunch-line conversation at a data journalism conference to
github issue in no time!
:)
On Friday, May 15, 2015, Jeremy B. Merrill<EMAIL_ADDRESS>wrote:

Modeling the behavior we want from data publishers 😊
—
Reply to this email directly or view it on GitHub
https://github.com/tabulapdf/tabula/issues/329.

--
Sent from a smartphone

On the day of Tabula's 1.0 release, wrote a blogpost on the topic
http://blog.civicdashboards.com/2015/08/opendata-proposal-pdf-data-pddf/
It could just translate to another export type - PDDF :)
And since Tabula knows the location of a table, you would think it can also a the Get the Data button in an available whitespace below each table.


Windows ANGLE/DirectX Support

Proposed Features
Raylib just added a project that allows a windows game to run under ANGLE. We can try to support this.
There is nothing further to say at this time

If it is merged, this will be covered in #15


Docs: Fixes on COVERALLS_FLAG_NAME and COVERALLS_REPO_TOKEN for GitHub Actions

Addresses https://github.com/coveralls-clients/coveralls-python/issues/243

Merging as this is a net improvement, but would love if you (@andy-maier ) had more info to add on the "piling up jobs" thing!

Merging as this is a net improvement, but would love if you (@andy-maier ) had more info to add on the "piling up jobs" thing!


IAM Role needed for viewing Compute Savings Plans in Azure

"Department admins and account owners can't view savings plans unless they're explicitly added to them using Access control (IAM). "
Can you please share what Role is required here from an Azure perspective? My understanding is its User access admin or Owner at MG level or Subscription level (can also be RG). Billing Admin is not a role that can be added from IAM so would like some clarity there. I have a customer that has Account Owner access but all the subscriptions show as ineligible for savings plans.
Thanks in advance.

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

ID: dfbc1d67-0ce5-39a4-3ee1-eadaee8b2789
Version Independent ID: 5c4e332a-3c56-1d11-adc9-2faee3cf5b05
Content: Permissions to view and manage Azure savings plans - Microsoft Cost Management
Content Source: articles/cost-management-billing/savings-plan/permission-view-manage.md
Service: cost-management-billing
Sub-service: savings-plan
GitHub Login: @bandersmsft
Microsoft Alias: banders

@moneyclouds
Thanks for your feedback! We will investigate and update as appropriate.

@moneyclouds Take a look at https://learn.microsoft.com/azure/cost-management-billing/savings-plan/permission-view-manage#grant-access-to-individual-savings-plans. There's additional info there about granting access to a saving plan

@MonikaReddy-MSFT  apologies - I am looking for clarity on ability to create a savings plan. I see that Subscription Owners and Enterprise Admins for EA Customers. Can Account Owners or Billing Admins not be able to purchase?


Support for 1734.285?

Installed on 10.0.1734.285. It does wor, but is says
[*] Terminal Services version: 10.0.17134.1
[-] This version of Terminal Services is not supported.
update.bat/RDPWinst -w both tell me
[] Checking for updates...
[] Current update date: 2018.10.10
[] Latest update date:  2018.10.10
[] Everything is up to date.
Attached is my termsrv.dll
termsrv.zip

10.0.17134.1 is already added to support.


Spaces Should be trimmed or not Allowed in Usernames

Describe the bug
When a User Modifies their Username they can accidentally add a Space to the end of it (Mobile Keyboards often do this Automatically). This Causes the User to be Unable to Login Since they don't know that they have a tailing Space that they need to add to Their Username.
To Reproduce
Steps to reproduce the behavior:

Go to Profile
Click on 'modify'
Add a Space to the End of the Username (happens automatically on Mobile)
Try to Login without the Space.

Expected behavior
Spaces Should trimmed or not be Allowed in Usernames.

#4150

@fforootd @livio-a what's the status on this? Who will be implementing the fix?

I am not sure, since I was not in the planing yesterday

will start with it this morning


[BUG] I would like to create form validation for "Leave a comment" in Blog Details page

Description
I would like to work on implementing form validation for the "Leave a Comment" form. Here’s my approach:
Field Validation:

Ensure the "Name" and "Comment" fields are not left empty before submission.
Validate the "Email" field to ensure the input follows a proper email format (e.g., name@example.com).
Set a character limit for the "Comment" field to avoid excessively long comments (e.g., 500 characters).

Error Messages:

Provide clear error messages below the fields if validation fails (e.g., "Please enter your name" or "Invalid email address").
Highlight fields with errors by using red borders or labels to make it easy for users to identify the problem.

Submit button :
Submit button will only work when all the required fields are filled and follows validation.
Screenshots

Any additional information?
The form is submitted eventhough the mandatory fields are not filled.
The email id is not checked properly it just shows @ and anyother character after that. It doesn't properly checks the email id.
What browser are you seeing the problem on?
Chrome
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I'm a GSSoC'24-Extd contributor
[X] I'm a Hacktoberfest'24 contributor
[X] I am willing to work on this issue (optional)

@mdazfar2 I would like to work on this issue. Please assign me this issue.

@clownfish1805 assigned

@mdazfar2
I have raised PR for this issue. Please check.


why when bind function f(int, std::tuple<int, int>) doesn't work?

code compiled with lua 5.4 and sol 3.3.0
int main()
{
    sol::state lua;
    lua.open_libraries();

    lua.set_function("func1", [](std::tuple<int, int> t)
    {
        std::cout << std::get<0>(t) << ","
                  << std::get<1>(t) << ","

                  << std::endl;
    });

    lua.set_function("func2", [](std::tuple<int, int> t, int k)
    {
        std::cout << std::get<0>(t) << ","
                  << std::get<1>(t) << ","
                  << k              << ","

                  << std::endl;
    });

    lua.set_function("func3", [](int i, std::tuple<int, int> t)
    {
        std::cout << i              << ","
                  << std::get<0>(t) << ","
                  << std::get<1>(t) << ","

                  << std::endl;
    });

    lua.script(R"#(
        func1(   1, 2   )
        func2(   1, 2, 3)
        func3(0, 1, 2   )
    )#");

    return 0;
}

run result:
1,2,
1,2,3,
[sol3] An error occurred and has been passed to an error handler: sol: runtime error: stack index 4, expected number, received no value: not a numeric type that fits exactly an integer (number maybe has significant decimals) (bad argument into 'void(int, std::tuple<int, int>)')
stack traceback:
        [C]: in function 'func3'
        [string "..."]:4: in main chunk

as you can see, func1 and func2 works while func3 not.
Looks param location matters, is this expected?
 Whenever the tuple is encountered the sol::stack::multi_check is called with the tracking and index that both already account for the processed stack items. Works fine when the tuple is a first item because when it's encountered both values are 0.
If only to know the original author's idea it could be an easy fix. Unfortunately a seemingly simple fix may actually break a lot of unrelated stuff.


Template is invalid; Dark mode fails to be recognized

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

First of all, there is no "Report Issue" menu item in the Help menu, if you search for "Report Issue". But the menu item exists, so this is incorrect behavior

Second of all, there is no "code" command installed.
QuinnHex:~ mike$ code
-bash: code: command not found

The issue I am having is that your program fails to recognize I have disabled dark mode.

The version is: Version: 1.87.1 (Universal) running on Mac OS 13.6.4. This is apparently the latest version of VS Code, and I am on a supported Mac version.

Issue 1

First of all, there is no "Report Issue" menu item in the Help menu, if you search for "Report Issue". But the menu item exists, so this is incorrect behavior

This doesn't seem to be the expected behavior of macOS? For example, I just searched for "safari help" in this menu:

And it doesn't give me the "Safari Help" item:

Do you know where it is expected that that item should show up?
Issue 2

Second of all, there is no "code" command installed.

You can install it by running this command:

Open Command Palette (cmd+shift+p)
Type in 'install code'
hit Return

This is documented here in the setup for macOS:
https://code.visualstudio.com/docs/setup/mac#_launching-from-the-command-line
Issue 3

The issue I am having is that your program fails to recognize I have disabled dark mode

By default, VS Code is in Dark mode and doesn't follow along with the OS. It never has and to do that out of the blue would be jarring for user who want dark VS Code but light macOS. That said, it's very easy to:

switch to a light theme: https://code.visualstudio.com/docs/getstarted/themes#_selecting-the-color-theme
have VS Code honor the OS: https://code.visualstudio.com/docs/getstarted/themes#_auto-switch-based-on-os-color-scheme

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Fix some races/multi-thread access in the reboot test.

@ixdy @mbforbes @quinton-hoole
I think that this should fix the problems that are causing this test to perma-fail on GKE.
I'm going to self-merge this on green, because I want e2e to run green over the weekend.

LGTM
(damn go for loops and closures tripping over each other) :-)

This doesn't seem to have fixed the reboot test, which is still failing on GKE.
/cc @mbforbes

I'll open a separate issue to track fixing this.

Whoops!


Update Destination Card to Reflect Correct Shipping Label Status for Orders Moved to In-Progress Page

Current behavior
Currently, when an order is moved from the open page to the in-progress page, the app initiates the process of obtaining the shipping label in the background. However, even when the shipping label is successfully generated, the destination card erroneously displays "missing shipping label." This discrepancy leads to confusion and inefficiencies in order processing. To ensure accurate representation of shipping label status for orders moved to the in-progress page, it is necessary to update the destination card functionality accordingly.
Expected behavior
Adjust the logic within the destination card component to correctly reflect the presence of a generated shipping label for orders in the in-progress stage.
Steps to reproduce the issue

Can you handle fixing this bug by yourself?

[ ] YES
[ ] NO

Environment details

Browser:
OS:
Code Version:

Additional information
Missing shipping label on the In Progress page
Missing shipping label on the Completed page

Issue verified in 2.0.1 and found that issue is still replicating.
https://jam.dev/c/54bd0d27-979a-4a41-b75c-900bc0d9198a
@ravilodhi Please connect with me wherever needed.
Also if shipping label is generated successfully, shipping label code is not visible in details page(In Progress).
https://jam.dev/c/d37e2047-f8e2-48d4-8655-6728040c2b34

The mentioned issue has been fixed in the following PR - https://github.com/hotwax/fulfillment-pwa/pull/445


[6.2.0] initialize(currentFormData) clears warnings and errors until the next onChange

Ok, so I've tracked this bug all the way down to the cause, I just don't have a solution. I'd be happy to submit a PR if we can figure out a solution.
A little background:
in src/reduxForm.js, warnIfNeeded() will always fire updateSyncWarningsIfNeeded() on initialRender (nextProps === undefined), but on subsequent renders, it will only fire the updates if !deepEqual(values, nextProps.values)
see the following copy of warnIfNeeded
warnIfNeeded(nextProps) {
  const { warn, values } = this.props
  if (warn) {
    if (nextProps) {
      // not initial render
      if (!deepEqual(values, nextProps.values)) {
        const { _warning, ...nextSyncWarnings } = warn(nextProps.values, nextProps)
        this.updateSyncWarningsIfNeeded(nextSyncWarnings, _warning)
      }
    } else {
      // initial render
      const { _warning, ...nextSyncWarnings } = warn(values, this.props)
      this.updateSyncWarningsIfNeeded(nextSyncWarnings, _warning)
    }
  }
}

this makes sense for most cases, but what if you initialize the form using the current values of the form (in order to get a pristine state)?
const warn = (values) => {
  let warnings = {};
  if (!values.message || !values.subject) {
    warnings._warning = "missing required fields";
  }
  return warnings;
}

class MyFormComponent extends Component {
  handleSave = (data) => {
    this.props.saveData(data);
    this.props.initialize(data);
  }

  handleSend = (data) => {
    this.props.sendData(data);
  }

  render() {
    const {pristine, warning, handleSubmit} = this.props;
    return (
      <div>
        <Field name='subject' component='text' />
        <Field name='message' component='text' />
        <button type='button'
                disabled={pristine}
                onClick={handleSubmit(this.handleSave)}>
          Save Draft
        </button>
        <button type='button'
                disabled={!!warning}
                onClick={handleSubmit(this.handleSend})>
          Send
        </button>
      </div>
    );
  }
}

const MyForm = reduxForm({
  form: 'myForm',
  warn
})(MyFormComponent);

Since the action handler for the initialize action starts from an empty state, warnings get cleared from the state. and since it's not initialRender, and the values of the form haven't changed, it won't re-calculate warnings.
We need a way to the form to recalculate warnings even if the form has been initialized to it's current values in order to achieve a pristine state.
Technically there is a similar issue with sync errors and the validateIfNeeded() function, but you can't fire a submit on a form with errors anyway (hence why I'm using warnings).
I'd love to get some discussion going around a solution, and like I said, I'd be happy to submit a PR with the final fix.

Dropping the if (!deepEqual(values, nextProps.values)) would do it, right? I wonder how much efficiency that's really providing... It would only be important if the warn() function was cpu-heavy.

after messing around with this for the later half of the day, removing that !deepEqual check doesn't solve it, that's just the first barrier.
The second barrier exists inside updateSyncWarningsIfNeeded where it checks to see if the warning is different from the previous warning. It won't pass that condition since it's comparing this.props.warning to the recalculated nextWarning, which are the same. So it will end up failing that and not firing updateSyncWarnings().
The only solution I've come up with is to modify the way the INITIALIZE action handler works.
currently it starts with a blank slate. I propose we follow that line with the following:
...
    var result = empty; // clean all field state
    // keep old warnings, they will get recalculated if the form values are different from current values
    const warning = getIn(state, 'warning')
    if (warning) {
      result = setIn(result, 'warning', warning)
    }
    const syncWarnings = getIn(state, 'syncWarnings')
    if (syncWarnings) {
      result = setIn(result, 'syncWarnings', syncWarnings)
    }
...

This will persist the old warnings through the INITIALIZE action, which solves my test case where you are reinitializing the form with its current values. It will also not break the current functionality when you reinitialize with values that are different than the current form values, since that passes the first barrier, and will go and re-calculate warnings.
I've tested it locally with both cases and it seems to work fine, and it passes all current tests. Thoughts? I can whip up a PR if you approve.

Fix published in v6.2.1.

Just added PR #2228 which solves the other part of this issue (errors not being persisted across initializations)

@dfalt The reason I didn't add that in as well is because it to initialize() a form with the same values if it has errors, since the form can't be submitted if it has errors (handleSubmit() won't fire if the form has errors).
The only case where this would be possible is if you happen to fire initialize() outside of handleSubmit() that just happens to have the same values.

@bmv437 You're right, after some more digging this is not a re-initialization issue. It actually appears to be an issue with the form's first initialization. I should probably open up a separate issue, but I'll clarify what I'm seeing here anyways.
This issue is manifesting for a form which loads its initialValues asynchronously and sets them after the redux-form component has been mounted.

During redux-form's componentWillMount call, validateIfNeeded is called
Since this is the initial render, the redux-form determines that we should call the form's validate method, which returns errors and ultimately sets these errors through the UPDATE_SYNC_ERRORS action
A bit later, initialValues are passed in as properties causing componentWillReceiveProps to be called
Since the form has yet to be initialized, the INITIALIZE action is fired, setting the form's state to include initial and values (and thereby removing the syncErrors that it had found originally, which is okay until...)
redux-form updates the component's values prop which triggers componentWillReceiveProps and thereby validateIfNeeded to be called
since the component's values have changed, we re-validate and find that there are errors which we pass into updateSyncErrorsIfNeeded
here we determine that the sync errors we found are the same that are stored in our component's syncErrors props, so we do not call the updateSyncErrorsaction creator

The problem lies in step 7 here. Our component is still aware of the original sync errors that we found in step 2, while our redux form state thinks there are no errors.
After writing all this out it's pretty clear that my PR is just a workaround and probably not the "correct" solution. I'm not exactly sure where the correct spot to reconcile the component's syncErrors prop and the redux form state's syncErrors is, but perhaps someone else does.
Either way, I'll look into this a bit more tonight/tomorrow as it seems like an issue. Granted it is one that can be worked around with some slight modifications to how the values are loaded and when they are passed to redux-form, but this feels like something that should be supported.

For what it's worth I wrote a test case that demonstrates the issue I am describing above.
it('recognizes sync errors on initialization after mounting', () => {

  const store = makeStore({})
  const inputRender = createSpy(props => <input {...props.input}/>).andCallThrough()

  class Form extends Component {
    render() {
      const { handleSubmit } = this.props
      return (
        <form onSubmit={handleSubmit}>
          <Field name="foo" component={inputRender}/>
        </form>
      )
    }
  }

  const Decorated = reduxForm({
    form: 'testForm',
    validate: values => {
      const errors = {}
      if (!values.foo) {
        errors.foo = 'This field is required'
      }
      return errors
    }
  })(Form)

  TestUtils.renderIntoDocument(
    <Provider store={store}>
      <Decorated/>
    </Provider>
  )

  const initialState = {
    form: {
      testForm: {
        syncErrors: {
          foo: 'This field is required'
        },
        registeredFields: [
          {
            name: 'foo',
            type: 'Field'
          }
        ]
      }
    }
  }

  expect(store.getState()).toEqualMap(initialState)

  store.dispatch(initialize('testForm', { foo: '' }))

  const expectedState = { ...initialState }
  expectedState.form.testForm.initial = { foo: '' }
  expectedState.form.testForm.values = { foo: '' }

  expect(store.getState()).toEqualMap(expectedState)

})

any progress on this? i've the same prob as dfalt explained, sync errors if they're same they don't pass through initialization ;/

@mvirbicianskas this particular fix has been released in v6.3.2, however, I'm not sure I'm following what's going on in your example. I'd suggest upgrading to v6.3.2 to see if that does resolve your issue and if not perhaps provide some more information about your setup.
How is it that you are reinitializing your form? Are you reinitializing with the same form values as it was initialized with or new form values?


[Gekidou] Unique servers

Summary
Following https://github.com/mattermost/mattermost-mobile/pull/5663 now we check if the server is already being used by checking the server identifier, this way we prevent adding the same server twice, even if the user enters a different url for the same server.
In a similar way we also check if the display name to inform the user in case they already have another server registered with the same name.
Also added a default setting in the config.json that allows to set a default server name as well as we are including an EMM managed configuration to set a default server name.
Ticket Link
https://mattermost.atlassian.net/browse/MM-39735
Not related to this ticket: I've added a small fix for Android push notifications.
Release Note
NONE

Well I gave a fair explanation on everything to provide some context and hopefully this helps you to get a bit more info about mobile


Porting rqt_gui_cpp Cmake

This pr ports rqt_gui_cpp to be built with Colcon
I intentionally separated this from porting the plugin providers so that we can get a jump start on the review process. Also, seeing as this is my first cpp port, I wanted to get a second pair of eyes on just the cmake changes

All feedback addressed. Merging


Removes line break from multiline subtitle

All subtitle entries with multiple lines becomes just one line after the translation.
00:01:34,736 --> 00:01:37,719
- Alt i orden?
- Ja, jeg ville bare høre fra dig.

Becomes ------>
00:01:34,736 --> 00:01:37,719
- Everything okay? - Yes, I just wanted to hear
from you.

I've been trying to find the source of this and it seems to be
sub.content = sub.content.strip().replace("\n", " ")
in srt_file.py

Yeah, it is intentional, cause when a sentence is break into two or more, the translation isn't too good.
Also, number of character doesn't stay the the same, that's why there is a "wrap line" mechanism.
Tho, I see why would you could like to be two lines if dialog starts with "-".


bevy_quill_obsidian will crash if you use StateScoped to remove UI when state changes

I was trying to use StateScoped to despawn my UI when the state change but this results in a crash because bevy_quill_obsidian tries to access the entity for a hover check after it has respawned, what is the correct why to remove UI? I don't think the application should crash if I despawn part of the UI

So the current solution for despawning UI roots is less than ideal, as it requires calling .raze() on the view root.
The eventual goal is to use relations to track ownership, along with component hooks, so that whenever you delete a view root entity all of the things that it owns also despawn automatically. But this is of course waiting on relations...although it may be possible to do something with just component hooks alone. It's a bit complex because hooks only get a deferred world, which means that any actual despawning has to be handled in the command queue. Researching this is one of the things on my TODO list.

how exactly do I call raze on a view root? I have been trying to work it out but cant work out how to get access to a pubic call to raze, the only one I found doesn't relate back to my root node in any way, I am probably missing something obvious.
p.s. would it be possible to add an example of how to cleanup or remove UI

OK, I added some public APIs for despawning a view root, and an example that illustrates how it works: https://github.com/viridia/quill/commit/b169936b5e5f0ad17eb3d1bfc92a5afebc596f55
The code isn't pretty, but as I mentioned earlier, hopefully this will get better.

I've worked on this more. You should now be able to despawn view roots normally with despawn(). In order to make this work, I had to change the raze() method to take a DeferredWorld instead of a World, which meant changes to every view impl. However this is generally good that razing no longer requires world access.

Ah, I thought I was going crazy. So this lib is the reason my StateScoped menus are crashing when switching to a new SubState. This lib is great so far! I just really wish that StateScoped UI would work as well :/

A little helper function I'm using for now. But long term: I would love to be able to use StateScoped again!
pub fn despawn_ui_with_marker<C: Component>(mut commands: Commands, query: Query<Entity, With<C>>) {
    commands.entity(query.single()).despawn();
}


Pubmed Tool SSL Cert Error when running code https://github.com/langchain-ai/langchain/blob/master/docs/docs/integrations/tools/pubmed.ipynb getting 'PubMed exception: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1006)>'

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
%pip install -U xmltodict
from langchain_community.tools.pubmed.tool import PubmedQueryRun
tool = PubmedQueryRun()
tool.invoke("What causes lung cancer?")
Error Message and Stack Trace (if applicable)
'PubMed exception: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1006)>'
Description
I'm running your notebook and getting a certificate failure when hitting pubmed. https://github.com/langchain-ai/langchain/blob/master/docs/docs/integrations/tools/pubmed.ipynb
System Info
platform mac
Python 3.11.7
Langchain Version: 0.1.14

Same error is happening when I run the retriever and document loader notebooks

I am also getting the same errors
I am using Mac M2
python 3.10
certifi                       2023.7.22
langchain                     0.1.8

Let me see.


Proposal: Editional aliases S for latest stable edition & U for the latest stable & or unstable edition

This way you can pass -eS to mean -e2021 (at the time of writing) and -eU to mean -e2024 (at the time of writing).

This is for the CLI only obviously, not for the compiletest directives. We can simply parametrize the edition parsing procedure to take a strictness parameter.

We could also support D for the default edition, namely Rust 2015.


Applying Delta to Empty Quill Instances

User posts contents to server
Server receives content, validates and stores in DB
Server sets new Y.Richtext in map
Client observes map change, creates Quill Instance and binds the two
Server applies delta to new Y.Richtext instance, inserting validated contents
Client observes appliedDelta and inserts it to Quill instance

Quill instance content:

Contents

Expected content:

Contents

I previously worked around this my modifying Y.Richtext to look like this: https://www.diffchecker.com/z0J0Wexr
Passing true if a change is occurring to a previously existing quill instance and false if it was just created (as in the above example). However 18 months later I realise it actually causes a desync in some cases.
I had asked in the past if it was possible to create a Y.Richtext instance, apply the delta, then apply it to the map, but it's not possible.
Any advice on this situation would be greatly appreciated, or if it's better to wait for v13 to drop, I shall.

Spent a few hours researching this, which is pretty much a waste of time considering all of this has been rewritten... But anyway I think maybe observing an applyDelta is a bit broken when it comes to adding new lines, around Line 593.
If I apply these operations and have them observed by a Quill instance, meaning they'll go through yCallback, there will be a break in the code block after each insertion.
[ { insert: 'https://github.com/y-js/y-richtext.git' },
  { attributes: { 'code-block': true }, insert: '\n\n' },
  { insert: 'curl -sL https://deb.nodesource.com/setup_6.x -o nodesource_setup.sh' },
  { attributes: { 'code-block': true }, insert: '\n\n' },
  { insert: 'sudo bash nodesource_setup.sh' },
  { attributes: { 'code-block': true }, insert: '\n\n' },
  { insert: 'sudo apt-get install nodejs' },
  { attributes: { 'code-block': true }, insert: '\n\n' },
  { insert: 'sudo apt-get install build-essential' },
  { attributes: { 'code-block': true }, insert: '\n\n' },
  { insert: 'sudo npm install -g pm2' },
  { attributes: { 'code-block': true }, insert: '\n' },
  { insert: '\n' } ]

Whereas if they're already in the map when the Quill instance is applied, it's all good.
Observing applyDelta

Delta already applied

These additional line breaks may or may not have something to do with the empty line that exists in this newly created Quill Instance.
Update:
Actually I created an interval applying the delta over and over and getting the same results as delta already applied. So my theory is incorrect. There's definitely something wrong but I don't know what it is.

Okay this post is just rambling theories now. But it could be that there's a clash between observing changes whilst bindQuill is being carried out. Seems like it's observing itself and each operation is being carried out twice.
My temporary solution is now to wait for all initial observations to be carried out before binding, which is pretty similar to applying operations before binding to the map.

Okay this post is just rambling theories now. But it could be that there's a clash between observing changes whilst bindQuill is being carried out. Seems like it's observing itself and each operation is being carried out twice.
My temporary solution is now to wait for all initial observations to be carried out before binding, which is pretty similar to applying operations before binding to the map.

Okay I've found the exact issue. Finally. I first came across this issue on Nov 3rd 2016.
Server creates a y-richtext instance and applies delta, which sends two events rather than one
y.share.map.set(itemID, Y.Richtext).applyDelta(value);

First Event: Client receives type="add" message from server and binds to quill instance.
y.share.map.observe(function(event){
	if(event.type == 'add') {
	    event.value.bind(localQuill);
	}
}

On bind, the localQuill has it's contents wiped and replaced with:

Second Event: It then receives the applyDelta update from the server, resulting in:

Server Set Value

So my proposed fix is, if possible, to allow us to create a richtext instance with content pre-applied.
However my workaround has no downsides, in which I bind on the second event rather than the first as the server will not send any more update messages.


[aki] Doesn't work on Redbot 3.5.1

May 07 13:45:14 ubuntu python[273087]: [2023-05-07 13:45:14] [ERROR] red: Package loading failed
May 07 13:45:14 ubuntu python[273087]: Traceback (most recent call last):
May 07 13:45:14 ubuntu python[273087]:   File "/home/ubuntu/redenv/lib/python3.11/site-packages/redbot/core/core_commands.py", line 188, in _load
May 07 13:45:14 ubuntu python[273087]:     await bot.load_extension(spec)
May 07 13:45:14 ubuntu python[273087]:   File "/home/ubuntu/redenv/lib/python3.11/site-packages/redbot/core/bot.py", line 1680, in load_extension
May 07 13:45:14 ubuntu python[273087]:     lib = spec.loader.load_module()
May 07 13:45:14 ubuntu python[273087]:           ^^^^^^^^^^^^^^^^^^^^^^^^^
May 07 13:45:14 ubuntu python[273087]:   File "", line 605, in _check_name_wrapper
May 07 13:45:14 ubuntu python[273087]:   File "", line 1120, in load_module
May 07 13:45:14 ubuntu python[273087]:   File "", line 945, in load_module
May 07 13:45:14 ubuntu python[273087]:   File "", line 290, in _load_module_shim
May 07 13:45:14 ubuntu python[273087]:   File "", line 721, in _load
May 07 13:45:14 ubuntu python[273087]:   File "", line 690, in _load_unlocked
May 07 13:45:14 ubuntu python[273087]:   File "", line 940, in exec_module
May 07 13:45:14 ubuntu python[273087]:   File "", line 241, in _call_with_frames_removed
May 07 13:45:14 ubuntu python[273087]:   File "/home/ubuntu/.local/share/Red-DiscordBot/data/Davidb/cogs/CogManager/cogs/aki/init.py", line 30, in
May 07 13:45:14 ubuntu python[273087]:     from .aki import Aki
May 07 13:45:14 ubuntu python[273087]:   File "/home/ubuntu/.local/share/Red-DiscordBot/data/Davidb/cogs/CogManager/cogs/aki/aki.py", line 28, in
May 07 13:45:14 ubuntu python[273087]:     import akinator
May 07 13:45:14 ubuntu python[273087]: ModuleNotFoundError: No module named 'akinator'
May 07 13:45:25 ubuntu python[273087]: [2023-05-07 13:45:25] [INFO] discord.gateway: Shard ID 0 has successfully RESUMED session b430b5ea3bd205e37244bc86ae8654c4.

This log is from dpy2 branch

Try reinstalling or do [p]pipinstall akinator[fast_async]==1.0.3

traceback for that?

May 07 14:15:29 ubuntu python[273087]: [2023-05-07 14:15:29] [ERROR] red.downloader: error: subprocess-exited-with-error
May 07 14:15:29 ubuntu python[273087]:
May 07 14:15:29 ubuntu python[273087]:   × python setup.py bdist_wheel did not run successfully.
May 07 14:15:29 ubuntu python[273087]:   │ exit code: 1
May 07 14:15:29 ubuntu python[273087]:   ╰─> [23 lines of output]
May 07 14:15:29 ubuntu python[273087]:       running bdist_wheel
May 07 14:15:29 ubuntu python[273087]:       running build
May 07 14:15:29 ubuntu python[273087]:       running build_py
May 07 14:15:29 ubuntu python[273087]:       creating build
May 07 14:15:29 ubuntu python[273087]:       creating build/lib.linux-aarch64-cpython-311
May 07 14:15:29 ubuntu python[273087]:       creating build/lib.linux-aarch64-cpython-311/cchardet
May 07 14:15:29 ubuntu python[273087]:       copying src/cchardet/version.py -> build/lib.linux-aarch64-cpython-311/cchardet
May 07 14:15:29 ubuntu python[273087]:       copying src/cchardet/init.py -> build/lib.linux-aarch64-cpython-311/cchardet
May 07 14:15:29 ubuntu python[273087]:       running build_ext
May 07 14:15:29 ubuntu python[273087]:       building 'cchardet._cchardet' extension
May 07 14:15:29 ubuntu python[273087]:       creating build/temp.linux-aarch64-cpython-311
May 07 14:15:29 ubuntu python[273087]:       creating build/temp.linux-aarch64-cpython-311/src
May 07 14:15:29 ubuntu python[273087]:       creating build/temp.linux-aarch64-cpython-311/src/cchardet
May 07 14:15:29 ubuntu python[273087]:       creating build/temp.linux-aarch64-cpython-311/src/ext
May 07 14:15:29 ubuntu python[273087]:       creating build/temp.linux-aarch64-cpython-311/src/ext/uchardet
May 07 14:15:29 ubuntu python[273087]:       creating build/temp.linux-aarch64-cpython-311/src/ext/uchardet/src
May 07 14:15:29 ubuntu python[273087]:       creating build/temp.linux-aarch64-cpython-311/src/ext/uchardet/src/LangModels
May 07 14:15:29 ubuntu python[273087]:       aarch64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -fPIC -Isrc/ext/uchardet/src -I/home/ubuntu/redenv/include -I/usr/include/python3.11 -c src/cchardet/_cchardet.cpp -o build/temp.linux-aarch64-cpython-311/src/cchardet/_cchardet.o
May 07 14:15:29 ubuntu python[273087]:       src/cchardet/_cchardet.cpp:196:12: fatal error: longintrepr.h: No such file or directory
May 07 14:15:29 ubuntu python[273087]:         196 |   #include "longintrepr.h"
May 07 14:15:29 ubuntu python[273087]:             |            ^~~~~~~~~~~~~~~
May 07 14:15:29 ubuntu python[273087]:       compilation terminated.
May 07 14:15:29 ubuntu python[273087]:       error: command '/usr/bin/aarch64-linux-gnu-gcc' failed with exit code 1
May 07 14:15:29 ubuntu python[273087]:       [end of output]
May 07 14:15:29 ubuntu python[273087]:
May 07 14:15:29 ubuntu python[273087]:   note: This error originates from a subprocess, and is likely not a problem with pip.
May 07 14:15:29 ubuntu python[273087]:   ERROR: Failed building wheel for cchardet
May 07 14:15:29 ubuntu python[273087]: ERROR: Could not build wheels for cchardet, which is required to install pyproject.toml-based projects
May 07 14:15:29 ubuntu python[273087]: [2023-05-07 14:15:29] [ERROR] red.downloader: Something went wrong when installing the following requirements: akinator[fast_async]==1.0.3

It seems like that error is a bug in python3.11

Try doing [p]pipinstall cchardet first and then use [p]pipinstall akinator[fast_async]==1.0.3

i have tried almost anything, but it seems that there is just problem in TA-lib with python 3.11

You could come to phen's support channel in red cog support server so i can support you more easily

pip install cython fixed the issue, thanks for help


Unnecessary slice calculation?

All this calculation where you figure out what to slice:
https://github.com/bitinn/node-fetch/blob/09ef40e8a883344a38f8ebddc58ff0ac129a415c/src/blob.js#L51-L76
Isn't that what Buffer.slice(start, end) also does for for you?
can't you just do:
slice(...args) {
   // ...
   const slicedBuffer = buffer.slice(...args);
   // ...
}

Possibly, but the File API spec specified this, which we reproduce faithfully.


Fix typos in the documentation

🚀 Feature Request
Is your feature request related to a problem? Please describe.

There are definitely typos in the documentation, we should fix them.

Describe the solution you'd like

Go to the files in docs/ and find and fix the typos! Look at the readthedoc auto build to check your work.

PR https://github.com/astrophpeter/blast/pull/195 includes many spelling and grammar corrections.
@djones1040 I recommend closing this issue.


Poll versions on (re-)connection

It would be nice to get the versions of firmwares of the system as sensors in Homassistant.
The updates on my system are done by foxess or my electrician. So I do not know if a new firmware arrives. With the sensor it is possible to show and alert on change.
Originally posted by @abuesen in https://github.com/nathanmarlor/foxess_modbus/discussions/504

Thank you, inatelled beta: Looks all right, nice mdi!
I'm exited to see the first update.

Hello... KH10.5 user here. Running integration version 1.10.1 and I just noticed the three entities to display inverter firmware versions (like sensor.foxess_manager_version). I added these to a dashboard and they are there and say have been updated between 5 and 10 minutes ago, but the version numbers displayed do not match my inverter's real version numbers. For example, I'm running 1.19 of Manager but integration says I'm running 2.81. Not sure if I missed a memo or if that means it's not working on KH. Not a top priority! Thanks.

@lamixer Thanks. Can you post your actual manager/master/slave versions, and the ones reported by this integration?

Sure...
Actual:
Master 1.27 / Slave 1.01 / Manager 1.19
Integration:
Master: 2.95 / Slave 2.57 / Manager 2.81

I'm sorry I didn't remember the foxess-cloud at all since I use the great foxess-modbus integration. So my reported versions in other discussions are wrong.
foxess-cloud says: Master : 1.83 Slave : 1.03 Manager : 1.66
foxess-modbus syas: Master : 1.83 Slave : 1.03 Manager : 3.85
Hardware: Master : 1.83 Slave : 1.03 Manager : 1.66


Merge My Profile Page and Passwordless Sign-in

Resolve Issues #3 #9 #10

Users can now sign into their account with no password by clicking on the "Passwordless Sign-in" button on Sing-in Page that will send a sign-in link to their email.
Users can change their display name on their Profile Page.
Users can reset their password on Profile Page
Users can permanently delete their accounts on Profile Page.
Users can sign-out on Profile Page


Don't use :: as a module separator

That's pretty annoying, but Android tag names are not supposed to include columns apparently.
With adb logcat, we can not filter by module if the module include a column.
For foo::bar, we can't do adb logcat foo::bar because adb will interpret that as "tag foo, log level bar".
I'm not sure what should be done here. Maybe replace :: with ;;, then we could do: adb logcat foo;;bar.

Or use a generic tag (Rust) and add the module name to the log.

Rust name seems reasonable. Tags also have a character limit, and that would be another reason to avoid module names in tags.

Would you recommend to just use Rust as a tag and the log message, or Rust as a tag and the module name + the log message?
For our use case (Servo), we don't need to module name.

It would be nice to have module name in the message. But I am currently not using this library (android project got delayed), so it would be better for you to decide.


Rename initialize(with:count:) to initialize(to:count:).

As proposed in SE-0107: UnsafeRawPointer.
"with" is considered a vacuous preposition. "to" implies direction.
Do not merge without the corresponding corelibs-foundation PR.

@swift-ci Please smoke test.


floatingActionmenucolor cannot be changed?

i tried to change the floatingmenucolor by using the following method.
** fab:fab_colorNormal="#2DBE62"
final FloatingActionMenu fabMenu = (FloatingActionMenu)findViewById(R.id.menu1);
fabMenu.setMenuButtonColorNormal(R.color.green);**
but its not working.if  u have any other option to change the color?

sorry for my issue
i made the change by using the following code
//   fab:menu_colorNormal="#2DBE62"


New gateway events mapped

Related to https://github.com/SrGaabriel/deck/issues/7

This pull request contributes to #7


"This application can't be launch directly."

When i start the application on my android, it close instantly and say :
"This application can't be launch directly."

That's because it can't be launched directly. It's intended to be the interface between web apps like MyEtherWallet and your Ledger device.

And how can you connect the Ledger Nano S and NEW then?

Launch MEW in Chrome, tap "Send Ether & Tokens," tap "Ledger Nano S," and finally tap "Connect to Ledger Nano S." The app will launch, and your device will function as it normally does on a PC.

Has been answered, so closing.


Fix install dependencies

remove dependency on sphinx that causes troubles when installing as a library since sphinx is not necessarily installed

Pull Request Test Coverage Report for Build 482

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.006%) to 68.432%

Files with Coverage Reduction
New Missed Lines
%

goodman_pipeline/core/check_version.py
1
95.45%

Totals

Change from base Build 480:
-0.006%

Covered Lines:
3037

Relevant Lines:
4133

💛  - Coveralls

Pull Request Test Coverage Report for Build 482

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.006%) to 68.432%

Files with Coverage Reduction
New Missed Lines
%

goodman_pipeline/core/check_version.py
1
95.45%

Totals

Change from base Build 480:
-0.006%

Covered Lines:
3037

Relevant Lines:
4133

💛  - Coveralls


Create Rule for Traefik

Hello,
I would like to create an HPA with a metrics from traefik :
traefik_backend_requests_total{backend="traefik.guilan.fr",code="200",method="GET",protocol="http"}

which return me this in the prometheus/graph url :
{backend="traefik.guilan.fr",code="200",instance="traefik-web-ui.traefik.svc.cluster.local:80",job="traefik",method="GET",protocol="http"}

but in fact i don't know how to create the rule ..
i've create this but it doesn't work :
    - seriesQuery: 'traefik_backend_requests_total{backend="traefik.guilan.fr",code="200",method="GET",protocol="http"}'
      resources:
        overrides:
          backend: {resource: "namespace"}
      name:
        matches: "^(.*)_total"
        as: "${1}_per_second"
      metricsQuery: 'rate(traefik_backend_requests_total{backend="traefik.guilan.fr",code="200",method="GET",protocol="http"}[2m]) by'

I think the real problem is that i don't understand well how to create a rule .. :/
Could you please help me with this ?
BR,

what response do you get kubectl get --raw /apis/custom.metrics.k8s.io/v1beta1/

you look like you have a malformed query in your metricsQuery field (you're missing part of the by clause).  Furthermore, just to confirm, does the backend label actually correspond to namespace name?  Do you have a namespace named traefik.guilan.fr?


Running GUI as Windows Service

thanks for this awesome app!
We need to use the GUI version because we use SMTP. But the authentication shouldn´t come up again if my understanding is correct.
So would it be safe to run the no-gui version as a service?

I'm not sure why SMTP in particular requires the GUI in your case (and why the no-GUI auth options aren't suitable), but either way, it is not needed again until your provider requires re-authentication. Whether (and when) this happens is down to the service you are using – for example, with O365 there are all sorts of options for admins to configure this. I'd go ahead and try running it as a service – it is typical on the order of months before re-authentication is needed.

Hey, can someone explain me how I can register the proxy as a service at Windows?
Do I have to convert my proxy autostart bat to exe and register it with sc.exe?

i ended up using either  winsw or NSSM.

Im also trying to get it running with NSSM right now but the service is always unexpected closing. Can you provide me an example of your solution please?

This is my attempt thats not working.
nssm install YourServiceName C:\Path\to\python.exe
nssm set YourServiceName AppDirectory "C:\email-oauth2-proxy-main"
nssm set YourServiceName AppParameters "C:\email-oauth2-proxy-main\emailproxy.py --local-server-auth --debug"
nssm start YourServiceName

Sorry i do not have access to my solution anymore. From what i can remember i enabled logging in nssm and figured it out based on the logs. Hope it helps!


WIP: Add pytest-split-tests to speed up tests on CI.

See if pytest-split-tests can help CI times.

Finding here is that github actions give you CPU seconds.
If we want the tests to run faster on CI we need to ask for a bigger plan.


Address only objects to buildings

Addresses #98 and #97.  Other improvements are being found in the process. :+1:

Initial testing shows this adds new building records in the DC sub-region such as this:  https://www.openstreetmap.org/way/66346595
Seems to be a good addition.  For this particular building it appears potentially office=* needs to be considered a building by default too.
Idea of # of records affected:
SELECT COUNT(*),
        COUNT(*) FILTER (WHERE b.osm_type = 'address') AS address_record,
        COUNT(*) FILTER (WHERE b.osm_type != 'address') AS building_tag_exists
    FROM osm.vbuilding_all b
    INNER JOIN osm.tags t ON b.osm_id = t.osm_id AND b.geom_type = t.geom_type
;

count |address_record|building_tag_exists|
------|--------------|-------------------|
178647|         17000|             161647|

Needs more review on what other tags are on the osm_type = 'address' records.  Likely still other overlap that should be removed, and also other improvements (explicit inclusions) that should be considered.
SELECT t.osm_url, t.tags, *
    FROM osm.vbuilding_all b
    INNER JOIN osm.tags t ON b.osm_id = t.osm_id AND b.geom_type = t.geom_type
    WHERE b.osm_type = 'address'
;

Updated counts now including office tags (without building tags).
SELECT geom_type, COUNT(*),
        COUNT(*) FILTER (WHERE b.osm_type = 'address') AS address_count,
        COUNT(*) FILTER (WHERE b.osm_type = 'office') AS office_count,
        COUNT(*) FILTER (WHERE b.osm_type NOT IN ('address', 'office') )
            AS building_count
    FROM osm.vbuilding_all b
    GROUP BY geom_type
;

The counts in the address_count and office_count columns are objects that previously were not included in these tables at all.

geom_type|count |address_count|office_count|building_count|
---------|------|-------------|------------|--------------|
N        | 17600|        16797|         277|           526|
W        |161137|           13|           3|        161121|

Additional level of detail justified adding osm_subtype column throughout the building layer.
SELECT osm_type, osm_subtype, COUNT(*)
    FROM osm.vbuilding_all b
    GROUP BY osm_type, osm_subtype
    ORDER BY osm_type, osm_subtype
;

Trimmed results...
osm_type     |osm_subtype            |count |
-------------|-----------------------|------|
building     |apartments             |   272|
building     |garage                 |   344|
building     |house                  |  2022|
building     |public                 |    19|
building     |residential            |   164|
building     |roof                   |    65|
building     |yes                    |157412|
building_part|column                 |    38|
building_part|elevator               |     3|
building_part|office                 |     2|
building_part|roof                   |     6|
building_part|steps                  |     4|
building_part|yes                    |   373|
office       |accountant             |     7|
office       |ngo                    |    19|
office       |tax_advisor            |     8|
office       |yes                    |    29|


Implements Scroll Into View

@alvaromb @TSMMark Could you please check out if my work is correct?

For the record this is based on conversation in #216

@alvaromb @TSMMark I've fixed the linting issues and the scrollToPosition error.

LGTM

Please give me a moment to pick up a ☕ and I'll release this.
Many thanks!

@TSMMark hi Mark! Want to join as a collaborator to this repo?

Sure thing!

@alvaromb Thanks for the invite! Do we need to have tests written to cover this behavior? Maybe I'm missing it but I did not see any tests in the codebase, as yarn test only runs eslint.

@TSMMark How would you test this PR? Sorry if the question sounds dumb but I don't know how one should test an UI Component.

@alvaromb is there anything you would like me to do here or would you mind releasing today?

Released https://github.com/APSL/react-native-keyboard-aware-scroll-view/releases/tag/v0.5.0 🎉

hey, just want to say I've made a separate library that was inspired by this initial implementation of @sebasgarcep
https://github.com/slorber/react-native-scroll-into-view


Migrating from checkstyle to spotless for formatting

Description
Adding spotless support in this repo in place of checkstyle so that we can get features for checking and applying the formatting using spotless. The rules used here are from the OpenSearch repo. spotlessJavaCheck is now part of the build task making it easier for developers to format their changes.
Issues Resolved
List any issues this PR will resolve, e.g. Closes [...].
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Sorry @VachaShah , it is impossible to review the PRs as large as those: what we did for security & core - migrate per packages, in in chunks of no more than 300 files, it adds up some work but at least is feasible to go through the changes.

Sorry @VachaShah , it is impossible to review the PRs as large as those: what we did for security & core - migrate per packages, in chunks of pull requests of no more than 300 files, it adds up some work but at least is feasible to go through the changes.

Yeah I thought about this after opening the PR 🙈 Let me break this down in multiple PRs without breaking the builds.

I wouldn't mind one massive PR as long as it's clear that the whole change is a couple of files and a separate "ran ./gradlew spotless:apply" kind of thing and all tests pass.

Thank you @dblock! I started dividing this, first PR is #648 which includes support for spotless and enabling spotless for some modules. The subsequent PRs will enable for other folders.


All the bound cloud applications are re-pushed if deleting one bound pro...

...ject
Phenomenon of the Bug:

During the process of deleting a bound project in Package Explorer, it will trigger all the other bound cloud applications to be re-pushed. The user can't do nothing except waiting all the re-pushing are finished.

Effect of the Modifications:

The re-pushing still exists during the process of deleting bound project, but a confirmation dialog, which asks the user to determine whether to re-push or not, will be presented for each bound cloud application.
By this way, the re-pushing can be interrupted and canceled by the dialog rather than be unbreakable.

Hi there!
We use Pivotal Tracker to provide visibility into what our team is working on. A story for this issue has been automatically created.
The current status is as follows:

[ ] #99824272 All the bound cloud applications are re-pushed if deleting one bound pro...

This comment, as well as the labels on the issue, will be automatically updated as the status in Tracker changes.


fix: img2img was broken for all samplers except ddim,plms

img2img was broken for all samplers except plms and ddim when init image strength was >~0.25.  Been this way for a while. whoops

Addresses #273


Request to add Iconify news feed

Summary
I'd like love to subscribe to Iconify updates. For other repositories, I tend to use https://github.com/:owner/:repo/releases.atom to subscribe to releases, but I see that Iconify doesn't do GitHub releases. I'm aware of the news page on Iconify, but I don't see an RSS/Atom feed for it. I prefer release feeds, but a feed of the current news page would also work.

Problem is, this monorepo has many packages, each package uses its own version numbers. Release requires one version number.

Yes, that might be possible. Need to think about how to automate updates, also it probably can use filters, so you can select which packages you want to see feed for.

While idea sounded good at first, it is a rare use case, but it requires a lot of development time.
This can already be achieved by watching NPM for updates. There are third party tools for that. Not sure if they can do RRS/Atom, but if not, that's an idea for a different project. Either way, it is out of scope for this project.

yes, that's a very good idea!

To help you understand how news works on new website. All news are stored in news/{year}/{file}, where {year} is year, {file} is a separate file for each news item.
Filename for news ends with either .md or .html and name means one of:

16.05 -> {day}.{month}
1642688466 (10 digits) -> UTC time stamp in seconds (as generated by PHP, since old website was using PHP)
1642688466000 (13 digits) -> UTC time stamp in milliseconds (as generated by Date.now() in JavaScript)

Each news file includes metadata, which includes title and link. See scripts/news.mjs for function parseNewsArticle() that parses all possible formats and returns simple to use object, which contains title, link, time (as Date object), content.

Awesome! Great information to have on the file names, by the way. Really appreciate that. I'll get started on this, and will reach out to you once it's done, or if I need another tip on the code base like the one above.
Also, not sure if you like moving issues, but this could possibly be moved to iconify/website now as well.


chore: adding VMware Tanzu to the adopters list

Problem Statement
ESO is used inside VMware Tanzu, so adding the product to the adopters list.
Checklist

[x] I have read the contribution guidelines
[x] All commits are signed with git commit --signoff
[x] My changes have reasonable test coverage
[ ] All tests pass with make test
[x] I ensured my PR is ready for review with make reviewable

Hi @garethjevans !! Thanks!!


Fix ordering of interpolated parameters in TIFF decode error string

Currently, the ordering of the parameters in the error string mean you get a result like this:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: UnsupportedError("[8] with RGBPalette bits per sample is unsupported")', libcore/result.rs:945:5

When really, it should look like this:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: UnsupportedError("RGBPalette with [8] bits per sample is unsupported")', libcore/result.rs:945:5

(Technically, the 'fixed' error message is still wrong, as that was actually a CIELab image with [8, 8, 8] encoding. However, since that's not supported yet, getting the error response to be less confusing is a step forward.)

Thanks!


Height mismatch in input-group (button + textarea)

While using a simple button+textarea input-group I noticed that there is a height mismatch between the two elements, which only exists when using the default size. Using input-group-sm or input-group-lg works properly. Sample: https://jsfiddle.net/iliasch/rb71ng1p/
Looking into bootstrap.css I noticed that height and line-height are specifically defined for input-group-sm and input-group-lg, but not for input-group (default), so the inherited 'auto' height is probably the cause of the problem. Is there a reason why you don't set a specific height for the default size?

Hi @iliasch!
You appear to have posted a live example (https://fiddle.jshell.net/iliasch/rb71ng1p/show/light/), which is always a good first step. However, according to the HTML5 validator, your example has some validation errors, which might potentially be causing your issue:

line 41, column 3 thru column 67: Duplicate ID sample-button.
line 43, column 2 thru column 53: Duplicate ID sample-textarea.
line 48, column 3 thru column 67: Duplicate ID sample-button.
line 50, column 2 thru column 53: Duplicate ID sample-textarea.

You'll need to fix these errors and post a revised example before we can proceed further.
Thanks!
(Please note that this is a fully automated comment.)

Removed unnecessary ids which were causing the validation errors.
https://jsfiddle.net/iliasch/rb71ng1p/

Hi @iliasch!
You appear to have posted a live example (https://fiddle.jshell.net/iliasch/rb71ng1p/show/light/), which is always a good first step. However, according to the HTML5 validator, your example has some validation errors, which might potentially be causing your issue:

line 41, column 3 thru column 67: Duplicate ID sample-button.
line 43, column 2 thru column 53: Duplicate ID sample-textarea.
line 48, column 3 thru column 67: Duplicate ID sample-button.
line 50, column 2 thru column 53: Duplicate ID sample-textarea.

You'll need to fix these errors and post a revised example before we can proceed further.
Thanks!
(Please note that this is a fully automated comment.)

http://jsfiddle.net/iliasch/rb71ng1p/1/

Hi @iliasch!
You appear to have posted a live example (http://fiddle.jshell.net/iliasch/rb71ng1p/1/show/light/), which is always a good first step. However, according to Bootlint, your example has some Bootstrap usage errors, which might potentially be causing your issue:

line 36, column 2: E006: .input-group contains a <textarea>; only text-based <input>s are permitted in an .input-group
line 43, column 2: E006: .input-group contains a <textarea>; only text-based <input>s are permitted in an .input-group
line 50, column 2: E006: .input-group contains a <textarea>; only text-based <input>s are permitted in an .input-group

You'll need to fix these errors and post a revised example before we can proceed further.
Thanks!
(Please note that this is a fully automated comment.)


Bug In Properties assignment in FIR filter

In the StationXML it says:
2000.0
But when I read the filter the sps is 200.0
This took a bit of debugging but what is happening is that inside the data-acquistion box they are applying the following scheme:
Native data is sampled at 32000Hz
This is downsampled to 2000Hz by fir "AD32M"
This is downsampled to 400Hz by fir "fs2ds"
This is downsampled to 200Hz by fir "F96C"
This is downsampled to 40Hz by fir "fs2ds"
Note that the filter "fs2ds" occurs twice in the sequence, so the 2000Hz one is being overwritten by the 200Hz one later on ... sigh ... OK, so how do we get around this?
First thought is that if the filter has "decimation_active" True then we name as the usualname_inputsamplerate.
This will make the decimaton filter names unique.
Alternatively we could track how many times a given AAF is applied and product them, but the first approach seems better.

I made the fix, so that the 5x decimation filters {2000-->400Hz & 200-->40Hz} are labelled differently.
However, something is wrong.
The 2000-->400Hz filter has a 3dB cutoff frequency of nominally 14Hz (which is appropriate for 40Hz data with 20Hz Nyquist) ...
BUT the 200-->40Hz filter has a 3dB cutoff frequency of nominally 2.8Hz.  This cannot be correct.
Ah, it is because of angular_frequency needs to be passed to scipy.signal.freqz() for fs.

I updated the decimation_active method to identify when a decimation filter is being applied.
If decimation_active is True, the filter_name assignment is the concatenation of the existing filter name plus the input sampling rate.  This has solved the bug.


Pick correct config object when passing env argument

When you start your project with npx wrangler@beta dev src/index.ts --env staging it would fail with this error:
/Users/luzanne/Projects/my-worker/node_modules/wrangler/wrangler-dist/cli.js:27069
            throw ex;
            ^

TypeError: Cannot read properties of undefined (reading 'jsxFactory')

After debugging some stuff I found out that the envRootObj was not set correctly.config['env.staging'] does not work, accessing properties goes only 1 deep.
This PR will fix that issue and use the correct config provided by the env variable.
Might be better to also add an extra check here. When an env variable is provided in the arguments, it must be available in the config as well? Thats up to you :)
Config object:
{
  _: [ 'dev' ],
  env: 'staging',
  local: false,
  ip: '<IP_ADDRESS>',
  port: 8787,
  'local-protocol': 'http',
  localProtocol: 'http',
  'upstream-protocol': 'https',
  upstreamProtocol: 'https',
  '$0': 'wrangler',
  filename: 'src/index.ts',
  config: {
    name: 'my-worker',
    type: 'javascript',
    zone_id: 'xxx',
    account_id: 'xxx',
    workers_dev: true,
    env: { staging: [Object], production: [Object] },
    build: { command: 'npm i && npm run build', upload: [Object] },
    __path__: '/Users/luzanne/Projects/my-worker/wrangler.toml'
  }
}

Nice catch, thanks! It shouldn't default to the config tho, probably to an empty object (which gets written with the config values that get inherited. I'll edit your PR directly and land this. Thank you so much for identifying the problem with a potential solution!

I'll test this out locally before merging.

Found some other bugs with reading config from envs and added it to this PR. Thanks again for catching this!

You can test this with wrangler@alpha, I'll cut a beta release later this week.


Dev branch publish recommendations

As discussed earlier, here are my recommendations for handling the dev branch of verb:

Merge the dev branch into master
Semver major bump (I like npm version major -m 'Release: %s')
Publish to npm with a custom tag (probably next) using npm publish --tag next - More information at https://docs.npmjs.com/getting-started/using-tags#publishing-with-tags
Install into packages or globally with npm install verb@next

This should allow you to start shipping the dev branch in your projects without messing with others' workflow.

awesome, we'll do this asap. thanks!

Any plans to get this done in the near future?


Use timezone.now instead of datetime.utcnow

Makes the time objects timezone aware

which timezone does this use? the timezone of the django user who kicked off the build? the timezone of the build worker task process?

It's timezone aware, so under the hood it's always UTC and can be adapted to other timezones as needed based on browser location.

timezone.now is used elsewhere in the code so this is really just bringing these stragglers in line.

ah, timezone aware - cool!


add styles to d3-cloud to fit container height and width and fix problem with ignored list

I tried to use this library with angular material. I tried to render word cloud to md-grid-tile but size of d3-cloud was 0x0. So I updated styles. And I add waiting for document when it is ready, because without that svg had size 0x0. When you were checking ignored objects you tried to find indexOf object name in array of objects and it could work. So I created method for checking that. But I forget to remove comparing color. So in next pull request I'll add optional color of word.

Thanks for the PR, nice to see others being interested in this little project.
A few thoughts based on a first quick look:

you can leave out the dist changes, I'll build on release..
I am a little surprised it is necessary to wait for document ready, as angular itself is normally not initialized before document onready. This SO answer seems to confirm that: https://stackoverflow.com/a/29887821/918496
I see you are trying to ignore words by properties other than just the name. I'm thinking that could be generalized. The directive could take an optional function to filter the words. A hard-coded default function that only looks at name could easily be applied.
Or maybe even better: that (optional) filter function could replace ignoreList entirely. Use filter function if provided, otherwise use ignoreList with its current support.
I like the idea of being able to pass in color along with each word, but it should be optional. You could potentially do things like: (ignoredObject.color ? ignoredObject.color === newValue.color : true)
 + 0 has dropped off twice around var cloudHeight = $element[0].clientWidth. I forgot its true purpose, but it probably had meaning.

Note: you can push more commits to your local 'commity' branch to update this PR..

OK I'll add optional colors and then I'll send another PR.

No need for a new PR, just pile up commits in here..

What do you think about filter function? Should it be something like filterFunction(value, ignore)? Both parameters are objects. Controller will send all combinations of values and ignores. Controller will get filter function from directive attribute. Is it OK?

I was thinking it only needs the value argument. You can provide ignore lists or whatever else is needed directly to the function before passing it into the directive..

I added optional color and custom filter function. Are they ok?

I repaired filters are they ok? Setting width and height in styles and waiting for document ready is used due to angular material.

I removed anguler.element(document).ready. Should I edit something else?

Awesome, looks pretty good.  It still mentions a words array. How about:
Optional. A function that filters words. Invoked for each word, should return true to retain the word, false to skip. Defaults to comparing against ignoreList for legacy purposes.

Regarding document.ready, I think I understand now, but I would think document.ready would not help here. It would sound more logical to me to wait for $element to be 'ready'. Now, I'm not sure you can use $element.ready(), but this answer seems to indicate a zero sec $timeout might do the trick: https://stackoverflow.com/a/32074491/918496. Maybe worth a look..

Documentation updated. Problem with rendering to md-grid-tile was solved with custom directive which broadcasts event on md-grid-list size count and then I show d3-cloud-ng.

Better?

I was about to suggest opening a separate ticket for the ready stuff, and you could still do so if you like.
Thanks for the doc update. I'll merge and tidy tomorrow if you don't mind, when I'm back behind the keyboard. I'll cut a new release so you can use your own work.. 😊

I don't mind. :smile: Thank you very much! :smile:

I think it is useful to follow up on the document.ready stuff, but no need to have this PR wait for that. I created ticket #19 as a reminder to look into it at some point in future..

0.9.8 is released..

Thank you! :smiley:


Error: Unexpected property  found in previous state received by the reducer

Hi Guys,
I use the async reducers to build my project. But I have encountered an error says :

Now my workaround is :
export default function createReducer(asyncReducers) {
  return combineReducers({
    routing,
    home: (state = Map({})) => state,          // Add the initial reducer
    userInfo: (state = Map({})) => state,      // Add the initial reducer
    ...asyncReducers,
  });
}

Does anyone has great idea for it?

combineReducers expects the object keys to be the same every time it processes a dispatch. So, if you have something that is producing keys for the object dynamically, then you need to provide that default initial set of keys for stuff that will load later. This is just a function of how combineReducers works. That workaround is essentially how you should be doing it.


Filter by Project in WI Search Services

Add filtering by project fields (id, name)  in work items list call and search service.

We are already able to fetch the work items by space, moreover we have 7 different filters to fetch work items.


add sample NewsArticle

@juliantoledo @kul3r4 PTAL

PTAL

Just 2 comments, otherwise LGTM.

Fixed two issues. Also restyled and simplified the header.
PTAL

Sample: https://amp-by-example-staging.appspot.com/sample_amps/news_article/preview/

LGTM.

Thanks for review Chiara!


Tests for the Game class

Step 1 - Creating tests

I added rigorous tests of all methods in the Game class
I tried to cover every possible way of using the methods wrongly

Step 2 - Updating Game class

When running the new tests on the Game class it failed some of them
I updated the Game class to pass all tests

I approve of this merge request.


Rna transcription fix

The failure cases defined in canonical-data.json were not included in the original test code.
As a result, the one complex error case failed ("ACGTXXXCTTAA") when the original code returned a truncated version of the transcription, ignoring the "XXX" middle.
I've added the tests and fixed the code. It now returns nil as per the spec.

I don't think we need a nullable String here. The way that I've seen null handled for Array is an empty array []; the same goes for String ( which in Swift also a collection ) is an empty String "".  I've be fine with this being a throwing function though.

OK that's a good point -- I remember reading that somewhere in the Swift 4 Language Book. I'm still getting used to Swift being almost as throw-happy as Java, since I'm coming from pure Objective-C development.
I'll make the mods to throw and push.

OK I've pushed my changes.
@masters3d Could you take a look at the test function testInvalidRnaComplementOfUracil() ? I've made an attempt to call XCTAssertThrowsError() with a follow-up to XCTAssertEquals() to attempt to verify that the correct error was being returned, but couldn't figure out how to get the code to work.
Thanks!

Swift errrors are untyped.

OK -- so you want me to make the errors untyped? Not a problem.

Since there is only one case, I think untyped here is good.

OK it looks like it's all done. LMK if there's something else you need from me here on this exercise.


Set-PnPWebTheme on subsites

I have this issue:
The root site https://tenant.sharepoint.com/sites/sitecollection/ is set with its own modern (  or classic ) theme.
I am using
Set-PnPWebTheme -Theme "customTheme" -WebUrl "https://tenant.sharepoint.com/sites/sitecollection/subsite"
to apply a modern theme to a subsite , successfully .
The command initially succeeds and my subsite modern theme is applied. However as soon as I visit ( just navigate in the browser )  to another site such as the root site collection site which one is set to its own modern theme, then my subsite's modern theme is reverted back to the theme of the root site collection site... ?!?
Not sure if browsing the site reverts the theme, but it gets reverted soon after it is applied to a subsite.

@VesaJuvonen Hi Vesa, would you have heard of such issue , or is it a new thing ?

@webk1 Thank you for your feedback
We want to make sure your PnP issue is handled appropriately.
We have a separate repo for the PnP PowerShell issues. We want your issue to get the proper attention it deserves.
Please open your issue in this repo: https://github.com/SharePoint/PnP-PowerShell
I am going to close this issue so that we can track to correct one in the PnP PowerShell repo.


Document how packages can be tested using rez-test

Maybe this can serve as a base? https://github.com/nerdvegas/rez/compare/master...ColinKennedy:issues/996-add_rez_test_example_package?expand=1 Specifically wiki/pages/Testing-Packages.md and the accompanying files.

For easier access, adding an exact link to @ColinKennedy's work on an old wiki doc page:
https://github.com/ColinKennedy/rez/blob/issues/996-add_rez_test_example_package/wiki/pages/Testing-Packages.md
We should port this page to the new Sphinx documentation.


Remove URL validation feature

We are going to icebox this because it's hard to design a good
experience for this feature. Instead, the Custom team are building an
app that handles this sort of thing. We'll use that API when it's
available.

:+1:


Github pages update for 2024.1

Description
Github pages for 2024.1 release.
Changes proposed in this pull request:

@napetrov @maria-Petrova I do not have the ability to add Reviewers. Can you add reviewers for me?


fix: remove server locking on agents

Please describe the purpose of this pull request.
Locks on the server class are causing strange issues, so removing it for now. Locks should eventually be moved into the Agent class (or we should use queues instead).
How to test
pytest -s tests/test_concurrent_connections.py
Have you tested this PR?
Yes
Related issues or PRs
#1438

Hi! unfortunately I still have the same issue
The problem seems to reside inside memgpt/server/agents/message.py @router.post("/agents/{agent_id}/messages
since it's an async function it cannot accept multiple posts to that endpoint.
The branch streaming-memgpt-api seems to work, what is missing for the merge?
Thank you!

Hi! unfortunately I still have the same issue
The problem seems to reside inside memgpt/server/agents/message.py @router.post("/agents/{agent_id}/messages since it's an async function it cannot accept multiple posts to that endpoint.
The branch streaming-memgpt-api seems to work, what is missing for the merge?
To reproduce it just launch the server with "memgpt server" and send concurrently 2 post requests (with different user and different agent) If you put a log before: if request.role == "user" or request.role is None: You will see that the log is printed once the previous message is processed
Thank you!

Are you using the latest server on main (i.e. rebuilding the docker container before running compose, or running memgpt server)? I had the same issue previous to this fix but after this PR the test tests/test_concurrent_connections.py makes sure different user/agent requests can be concurrently processed.

Hi! unfortunately I still have the same issue
The problem seems to reside inside memgpt/server/agents/message.py @router.post("/agents/{agent_id}/messages since it's an async function it cannot accept multiple posts to that endpoint.
The branch streaming-memgpt-api seems to work, what is missing for the merge?
To reproduce it just launch the server with "memgpt server" and send concurrently 2 post requests (with different user and different agent) If you put a log before: if request.role == "user" or request.role is None: You will see that the log is printed once the previous message is processed
Thank you!

Are you using the latest server on main (i.e. rebuilding the docker container before running compose, or running memgpt server)? I had the same issue previous to this fix but after this PR the test tests/test_concurrent_connections.py makes sure different user/agent requests can be concurrently processed.

Hi! Thank you for your reply, I wrote you on Discord :)

Hi! unfortunately I still have the same issue
The problem seems to reside inside memgpt/server/agents/message.py @router.post("/agents/{agent_id}/messages since it's an async function it cannot accept multiple posts to that endpoint.
The branch streaming-memgpt-api seems to work, what is missing for the merge?
To reproduce it just launch the server with "memgpt server" and send concurrently 2 post requests (with different user and different agent) If you put a log before: if request.role == "user" or request.role is None: You will see that the log is printed once the previous message is processed
Thank you!

Are you using the latest server on main (i.e. rebuilding the docker container before running compose, or running memgpt server)? I had the same issue previous to this fix but after this PR the test tests/test_concurrent_connections.py makes sure different user/agent requests can be concurrently processed.

Hi! Thank you for your reply, I wrote you on Discord :)


[BUG] missing a default timeout parameter and timeout error mismatch when deploying on yarn

Describe the bug
missing a default timeout parameter and timeout error mismatch when deploying on yarn
To Reproduce
To help us reproducing this bug, please provide information below:

Your Python version: 3.7.9
The version of Mars you use: pymars[distributed]==0.6.0
Versions of crucial packages, such as numpy, scipy and protobuf: numpy==1.19.4, scipy==1.5.4, protobuf==3.14.0, pyarrow==2.0.0
Full stack of the error.

Traceback (most recent call last):
  File "test_yarn.py", line 10, in <module>
    cluster = new_cluster(environment='python:///opt/anaconda3/envs/pymodel/bin/python', scheduler_num=1, web_num=1,worker_num=4, worker_cpu=8, worker_mem='28g',min_worker_num=2)
  File "/opt/anaconda3/envs/pymodel/lib/python3.7/site-packages/mars/deploy/yarn/client.py", line 148, in new_cluster
    timeout=timeout - (time.time() - check_start_time))
TypeError: unsupported operand type(s) for -: 'NoneType' and 'float'

By adding a timeout parameter, the error disappear. But sometimes timeout error occurs as follows:
Traceback (most recent call last):
  File "test_yarn.py", line 10, in <module>
    cluster = new_cluster(environment='python:///opt/anaconda3/envs/pymodel/bin/python', scheduler_num=1, web_num=1,worker_num=4, worker_cpu=8, worker_mem='28g',min_worker_num=2, timeout=1)
  File "/opt/anaconda3/envs/pymodel/lib/python3.7/site-packages/mars/deploy/yarn/client.py", line 148, in new_cluster
    timeout=timeout - (time.time() - check_start_time))
  File "/opt/anaconda3/envs/pymodel/lib/python3.7/site-packages/mars/deploy/utils.py", line 31, in wait_services_ready
    raise TimeoutError('Wait kubernetes cluster start timeout')
TimeoutError: Wait kubernetes cluster start timeout

Minimized code to reproduce the error.

import os
from mars.deploy.yarn import new_cluster
from mars.session import Session
import mars.tensor as mt
import mars.dataframe as md

os.environ['JAVA_HOME'] = '/usr/java/jdk1.8.0_191-amd64'
os.environ['HADOOP_HOME'] = "/usr/bin/hadoop"
cluster = new_cluster(environment='python:///opt/anaconda3/envs/pymodel/bin/python', scheduler_num=1, web_num=1,worker_num=4, worker_cpu=8, timeout=1)
print(Session.default_or_local().endpoint)
a = mt.random.rand(10, 10)
print(a.dot(a.T).execute())

Expected behavior

give timeout a default value, such as 60.
when timeout error occurs, print the correct info, E.g. "Wait yarn cluster start timeout"

When timeout is not specified, it might be better to wait infinitely till KeyboardInterrupt is raised.

@wjsi  waitting infinitely till KeyboardInterrupt is better. By the way, TimeoutError raised by the func wait_services_ready, how do you like adding a parameter naming platform to raise the corresponding cluster timout such as k8s or yarn.

@wjsi waitting infinitely till KeyboardInterrupt is better. By the way, TimeoutError raised by the func wait_services_ready, how do you like adding a parameter naming platform to raise the corresponding cluster timeout such as k8s or yarn.

It is cleaner to raise a general error inside wait_services_ready. Different clients for different platforms can catch this error and raise their own using raise ... from None.

Could you please submit a PR to address this issue please? @smartguo

Could you please submit a PR to address this issue? @smartguo

My pleasure, I will try my best.


"X ago" should be updated continuously

On page load, the "0m ago" is updated and all is good. But when time goes on and user doesn't refresh the page, the counter doesn't count and it still says "0m ago" even if the data shown is actually older.
We have decided not to automatically refresh the page for now, but the updated time should be updated. And actually it should show "35 s ago", "36 s ago", "37 s ago" and after 1 minute has passed, it should be "1 min 1 s ago". Just like the mobile apps do.
We can add auto cloud refresh later if decided so, but let's fix this one first. We'll need this same thing on the web dashboard once its layout outlook has been designed first.

QA passed, no auto refresh yet


TimeInterval class

@giacomov, should we integrate your TimeInterval class throughout the code?

Looks like you did already. Shall we close this?

#151 fixes


Vary signature for mainnet

This PR modifies the signature scheme so that signatures on testnets bear no relation to signatures on mainnet.

!approved-for-mainnet


local-up-cluster.sh should start the proxy as root

It seems that since ip per service, the proxy require root in order to call iptable, so starting local-up-cluster with a non-root user currently fails, with the following error:
E1120 01:09:26.606120    5279 proxier.go:319] Failed to initialize iptables: error creating chain "KUBE-PROXY": exit status 3: iptables v<IP_ADDRESS>: can't initialize iptables table `nat': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

@proppy @smarterclayton Is this still an issue?

local-up-cluster.sh runs everything with sudo these days.

Thanks @markturansky! Marking this as fixed.


Update 'item' model to change 'edit item stock' verbiage

Changes "Correction" to "Adjustment" on "Edit Item Stock" page seen here:
http://localhost:3000/inventory/73/edit_stock

Looks Legit


update SageComponent rendering and ProgressBar properties to support Turbo Stream rendering

Description
fix(sage component): explicit force html format when rendering Sage components
When attempting to render a component from a Turbo Stream response
format an `ActionView::MissingTemplate` error is raised, e.g.

Given (in e.g. `/.../show.turbo_stream.erb`):
```html
<turbo-stream action="update" target="progress-bar">
  <template>
    <%= sage_component SageProgressBar, {
      percent: @view.progress_percent,
      label: "Progress",
    } %>
  </template>
</turbo-stream>
```

Raises:
```
ActionView::MissingTemplate - Missing partial
sage_components/_sage_progress_bar with
{
  :locale=>[:en],
  :formats=>[:turbo_stream],
  :variants=>[],
  :handlers=>[:raw, :erb, :html, :builder, :ruby, :jbuilder]
}. Searched in:
  * "/Users/kellyredding/projects/kajabi/kajabi-products/app/views"
  * "/Users/kellyredding/.rubies/2.7.7/lib/ruby/gems/bundler/
     gems/sage-lib-1a13d8b0a7ca/docs/lib/sage_rails/app/views"
  * ...
```

This switches to forcing the `formats:` directive on the render
call when rendering Sage components (since all of the component
templates are html). I got this from the Rails docs here:
https://guides.rubyonrails.org/layouts_and_rendering.html#the-formats-option

feat(progress bar): add animate property to ProgressBar to turn animation on/off
When rendering progress bar updates using Turbo Streams, we are
doing server side rendering. This means we re-render the progress
bar component with a new percentage each time. This works fine
except that the animation (that was previously always on) would
run and slide the bar from zero to percentage each time it was
re-rendered. This made for jarring progress bar updates b/c it
looked like each update had to restart the progress from zero.

I reached out to #sage-support and ended up pairing with Julian
on adding a new `animate` boolean property to ProgressBar. This
property (`nil` but "on" by default for backwards compatibility)
controls whether the animation CSS is applied. If created with
`animate: false`, the animation will be disabled and any render
or re-render will just show the progress bar and the given percent
without animation.

This covers the both the Rails and React component adjustments to
support the new property. This also updates the docs site to show
the new property. Finally, I tested the property in both the Rails
docs site page and the React storybook.

Screenshots
Default animate "on" behavior still exists (backwards compatible change):

Animate false updating via Turbo Streams (via my spike):

Animate on/off in React storybook:

Testing in sage-lib

Do the yarn setup/start stuff to run all the processes locally.
Fire up http://localhost:4000/pages/component/progress_bar?tab=preview and verify animate is still on by default (you should see the progress bars animate to the percentage
Fire up http://localhost:4100/?path=/story/sage-progressbar--default&args=percent:89;animate:true and toggle the animate switch from true to false and see the animation turn on/off on change.

Testing in kajabi-products
Impact level: LOW
I was spiking a test to make sure we could update progress bar percents from Turbo Stream renders and I noticed these issues. There is no place in kajabi-products where this is used (yet) - I was just spiking a new usage. I've attached a gif above from my spike showing it working. The change is backwards compatible so it shouldn't affect any previous usage of progress bars. Let me know if you need more for this section.
Related
N/A - I don't have a usage PR yet as I was just spiking for now.

@ju-Skinner what else is needed on this to merge it? Are we good to go?

@ju-Skinner what else is needed on this to merge it? Are we good to go?

I believe we are waiting on one more review from the team. Since I helped contribute, my review didn't count 😉


Tables in Markdown previewer

I've been testing file previewers v1.4 in our Dataverse test environment (v6.2). When opening a Markdown file (.md) in the Markdown previewer, tables are not displayed as tables but as plain text. The tables look fine in Markdown editors, e.g., https://stackedit.io/app#. Maybe there is a bug in the previewer? Thanks for considering this input!

Hmm, tables are non-standard in Markdown so I'm not super surprised they don't "just work".
@philippconzett which table syntax are you using?
@ErykKul added the Markdown previewer in #23 and might know offhand if tables are supported.

Ah, thanks, @pdurbin, I didn't know. If I remember correctly, I the file I previewed had a table like this:

Row1
Row2
Row3
Row4
Row4

Cell1
Cell2
Cell3
Cell4
Cell5

Cell6
Cell7
Cell8
Cell9
Cell10

Markdown is a markup language of fairly limited design (intended by creator Daring Fireball's Gruber). We're used to using markdowns, extended versions such as Github's flavor, which have implemented quite a few functions. The dataverse previewer seems to use a standard implementation.

I made a PR to add support for tables. They do not look very good, but it works (tested on our pilot env with a README.md from GitHub):

After merging to master all previewers using v1.4 are auto-updated.

@ErykKul seems like a good fix to me! @philippconzett @gwendoux what do yo think?

Looks good to me. Thanks for fixing this!

It's good enough👍. A simple tweak on the css part could fix the "looks good" later ;)

@ErykKul Here is a good source for replicating GitHub Markdown style https://github.com/sindresorhus/github-markdown-css


include ecr native gate for pulse scaling

Summary
The addition of IBM Quantum backends without native cx gates (i.e., ibm_sherbrooke where the native entangling gate is ecr, echoed cross resonance) is not compatible with the pulse scaling done by RZXCalibrationBuilder and RZXCalibrationBuilderNoEcho. This PR addresses this problem by treating the cx and ecr gate on equal footing in those classes.
Details and comments
The logic that handles extracting information from the entangling gates has been moved to _check_calibration_type and the corresponding gate is checked for in backend.defaults().instruction_schedule_map before assigning the correct schedule and corresponding CRCalType (either by definition as it is only assigned in one direction for ecr or an inspection of which qubit the on-resonance compensation tones are applied to).
The unit test TestCalibrationBuilder is also updated for compatibility with the same logic, however the FakeSherbrooke backend from qiskit.providers.fake_provider currently does not have a backend.defaults() method to obtain the instruction schedule map from.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

24 of 32 (75.0%)  changed or added relevant lines in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.03%) to 84.923%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit/transpiler/passes/calibration/rzx_builder.py
24
32
75.0%

Files with Coverage Reduction
New Missed Lines
%

src/sabre_swap/layer.rs
2
98.95%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
66661

Relevant Lines:
78496

💛  - Coveralls

fix #9308

While we are at it, should we add GaussianSquareDrag to this list: https://github.com/Qiskit/qiskit-terra/blob/925f9f3abfdee4faeae67503082d7877f080c2ed/qiskit/transpiler/passes/calibration/rzx_builder.py#L330 ?

Please also update EchoRZXWeylDecomposition to include the ECR.

Modified EchoRZXWeylDecomposition to use the same logic as rzx_builder.py.

While we are at it, should we add GaussianSquareDrag to this list:
https://github.com/Qiskit/qiskit-terra/blob/925f9f3abfdee4faeae67503082d7877f080c2ed/qiskit/transpiler/passes/calibration/rzx_builder.py#L330
?

It is my understanding that the GaussianSquareDrag were only used as compensation tones for DirectCX. Additionally, the DirectCX includes extra pulses that should not scale with the CR angle, so including them will take extra consideration that I believe is outside the scope of this PR.

If I understand correctly GaussianSquareDrag just adds DRAG component to the risefall and can be applied to ECR to deal with noisy spectrum. So I think adding drag version to validation makes sense, though I'm not sure how we can scale this pulse at shorter regime where we need to renormalize amplitude.

It is my understanding that the GaussianSquareDrag were only used as compensation tones for DirectCX.
I think DirectCX uses GaussianSquareEcho in this PR.

Replying to https://github.com/Qiskit/qiskit-terra/pull/9397#issuecomment-1405928034 if you remove the flat-top part you have a normal Gaussian, you can still scale the amplitude but you might have some miscalibrations you need to compensate for. This is anyhow the case for Gaussian square without the drag.

Yes. The question is how we scale the drag component in general. Since this is proportional to the derivative of amplitude, the drag coefficient must be changed with the amplitude. AFAIK there is no established method for this.


Clarify statement about packages

Since there are still a number of dependencies in the gemspec, this seemed a little misleading.

CI is failing due to https://github.com/Shopify/shopify-api-ruby/issues/1058 but since this only impacts the docs it's safe to override.


Landing page design for each of main category pages in the top menu

XD Prototype: https://xd.adobe.com/view/f8181f50-f288-4e59-99c5-b786dbfc5d66-ad4b/

[ ] determine content for each page
[ ] create designs/layouts for each page
[ ] share designs with team/get feedback
[ ] revise and finalize


Removing the focus border from the select box when clicking....

Hello, I am aware that this might not be the place to ask, but not yet having found a solution, asking here.
Essentially, I am trying to remove the ugly black focus border that surrounds my select listbox when clicking or putting focus on it :

This jsfiddle shows my issue, with my version jQuery / Bootstrap*
https://jsfiddle.net/toheyr8c/
Ive tried placing the outline:0 or none, etc on either .selectpicker and .customSelect selectors, but nothing will remove that black focus border!
Thanks for any inputs. Much appreciated.
Pat

Any updates on removing the outline in the new version?


feat(model): Allow from_pretrained to accept PeftConfig class

Signed-off-by: Aaron<EMAIL_ADDRESS>

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

I have updated according and added test cases for this. PTAL when you have time. Thanks

make sense to raise the error. Great recommendation!

Hi @pacman100, an example use case would be:
When you configure the config class beforehand, I think it saves one cycle of constructing and dictionary lookup within PeftModel.from_pretrained.
Also let say we have a LLM class representing a model that contains multiple config kwargs
class LLM:
	peft_config_map = {"lora": {**lora_kwargs}, "prompt_tuning": {**prompt_tuning_kwargs}}

And LLM construct each of the peft config before hand, and only converts the model to PeftModel on the model server (since it is light to construct the config, whereas the model is heavy).


Improve HF integration

Hi @GuozhenZhang1999 and team,
Thanks for this nice work! I see the checkpoints are already available on the hub which is nice to see. This PR aims to improve the HF integration, as we usually recommend to store each checkpoint in a separate, dedicated model repo. This way, downloads also work for your models.
I wrote a quick PoC to showcase that you can easily have integration with the 🤗 hub so that you can

automatically load the model using from_pretrained (and push it using push_to_hub)
track download numbers for your models (similar to models in the Transformers library)
have nice model cards on a per-model basis along with tags (so that people find them when filtering https://hf.co/models) => we could collaborate on adding a dedicated "video-frame-interpolation" tag
perhaps most importantly, leverage safetensors for the weights in favor of pickle.

It leverages the PyTorchModelHubMixin class which allows to inherits these methods.
Usage is as follows:
from model.flow_estimation import MultiScaleFlow

# instantiate model
model = MultiScaleFlow(...)

# equip model with weights
model.load_state_dict(...)

# push to hub
model.push_to_hub("MCG-NJU/vfi-mamba")

# reload
model = MultiScaleFlow.from_pretrained("MCG-NJU/vfi-mamba")

This means people don't need to manually download a checkpoint first in their local environment, it just loads automatically from the hub. Checkpoints could be pushed to https://huggingface.co/MCG-NJU.
Would you be interested in this integration?
Kind regards,
Niels
Note
Please don't merge this PR before pushing the model to the hub :)

Hi @NielsRogge! Thank you very much for your suggestions for our work! But one of our model's components, namely MambaFeature, is passed to MultiScaleFlow as an initialization parameter:
class MultiScaleFlow(nn.Module, PyTorchModelHubMixin):
    def __init__(self, backbone, **kargs):
        super(MultiScaleFlow, self).__init__()
        self.feature_bone = backbone

Because of this, MultiScaleFlow.from_pretrained("MCG-NJU/vfi-mamba") seems unable to correctly initialize self.feature_bone and load its weights. I’m not sure how to integrate your pull request while preserving our current implementation structure. Any ideas?

Thanks for the context @lcxrocks.
Yes if models take nn.Module's in their init, then they can't be JSON serialized into a config.json (cc @wauplin).
So some suggestions here:

either one can define the MambaFeature class within the MultiScaleFlow class, taking JSON serializable arguments as input:

class MultiScaleFlow(nn.Module, PyTorchModelHubMixin):
    def __init__(self, **kwargs):
        super(MultiScaleFlow, self).__init__()
        backbone_kwargs = kwargs.pop("backbone_kwargs")
        self.feature_bone = MambaFeature(**backbone_kwargs)

where you store each of the parameters regarding the backbone in a dedicated backbone_kwargs field in the config.json.

if you prefer to keep the same structure as-is, then we can remove the PyTorchModelHubMixin class and instead define a from_pretrained method ourselves, which uses the hf_hub_download method behind the scenes. See here for an example.

Hey there :wave: Agree with @NielsRogge suggestions above :) I would lean toward the first option (using some backbone_kwargs) if that's possible. Otherwise, another solution would be to add a type annotation to backbone argument and then let the model know how to encode/decode this specific attribute. See the VoiceCraft example in this guide. This would look like this:
def backbone_to_dict(backbone: BackboneClass) -> Dict:
    return ... # return a jsonable dictionary with backbone config

def dict_to_backbone(config) -> BackboneClass:
    return BackboneClass(config) # instantiate backbone based on config

class MultiScaleFlow(nn.Module, PyTorchModelHubMixin,
   coders={
      BackboneClass : (
         backbone_to_dict,  # Encoder: how to convert a `BackboneClass` to a valid jsonable value?
         dict_to_backbone,  # Decoder: how to reconstruct a `BackboneClass` from a dictionary?
      )
   }
):
    def __init__(self, backbone: BackboneClass, **kwargs):
        super(MultiScaleFlow, self).__init__()
        self.feature_bone = backbone

With this solution, the backbone configuration would be saved in the same config.json file with the other kwargs parameter. You should be able to define any logic you want (even downloading files from the Hub), as long as the config is json-serializable.

@NielsRogge @Wauplin Thank you both so much for your valuable suggestions and support! To ensure we maintain the current code readability, we’ve decided to prioritize the second approach suggested by @NielsRogge (#2). However, we truly appreciate the other suggestions and will revisit and consider them in the future.

Makes perfect sense! Thanks for the feedback. Let us know if you have any question building the integration. This guide should be helpful to do it :) https://huggingface.co/docs/huggingface_hub/guides/integrations#a-flexible-approach-helpers