ci(grandpa-ranger): deployment

Summary of changes
Summarize the description of your changes.
If it fixes a bug or creates a feature, link the issue.
Acceptance Checklist
What types of changes does your code introduce?
Put an x in the boxes that apply
Dependencies

[ ] Any dependent changes have been merged and published in downstream modules
[ ] Any teams which manage the dependencies have been notified of the breaking changes

Bug (non-breaking change which fixes an issue):

[ ] Have you written tests to protect against future occurrences of the bug?

Feature (non-breaking change which adds functionality)

[ ] Have you seen it working in a development environment?
[ ] Have you written tests for happy and unhappy paths?
[ ] Have you implemented this feature as per the issue acceptance criteria?

Substrate
If this change involves substrate, have you remembered:

[ ] Storage Migration?
[ ] RPC methods?
[ ] Chainspec, both JSON specs & the module?
[ ] Runtime versioning?
[ ] Benchmarks?

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

[ ] Is the breaking change documented?
[ ] Are your commits fully representative of the change?
[ ] Has any previous functionality been deprecated and versioned?

CI/CD

[ ] If introducing new actions, have you looked at the action code for anything spurious?
[ ] Have you written custom scripts for things that could be actions already on the marketplace?
[ ] If introducing new actions, have you pegged a static version?

Documentation Update

[ ] Have you checked other documentation, such as the docs repository?
[ ] If updating script documentation, have you tested it on both environments?

Further comments
Feel free to explain in further detail your choices if this is a significant change.
Screenshots (Please demonstrate this working in PolkadotJS)

Summary by OpenAI
Release Notes:

New Feature: Added GitHub Actions workflow for building and deploying Docker image of grandpa-ranger package.
Refactor: Minor changes to Kubernetes resource definitions, ESLint configuration, and Helm ignore patterns.
Chore: Added configuration object with connection details for RPC endpoints and signer.

"From Kubernetes resources to Docker builds,
This PR brings new features without any spills.
With minor refactors and chore updates too,
The codebase is now better, through and through."

@openai ignore


actions/checkout@v2 -> actions/checkout@v3

Purpose/implementation Section
What changes are being implemented in this Pull Request?
This should address #604
Everywhere that we are using actions/checkout@v2 I'm now bumping it up to actions/checkout@v3

The last thing not update is the load step’s set-output but that is not something we can control. We’ve gotten rid of the ones we have but the yaml load step appears to have one but doesn’t have an updated version. If push comes to shove we may have to find a different yaml to environment action.


Use more persistent shader type cache dir

Because the OUT_DIR environment variable can change, the shader bindings cache would get invalidated sometimes leading to a recompilation of shader bindings.
Generating the bindings is a slow process and should be avoided.
This PR creates a directory in the crate to use for caching since having a consistent cache directory means shader type re-compilation becomes rare.
To further reduce the cost of these bindings, I changed the shader_types.rs file to only include simd/vector_types.h instead of all of simd/simd.h.
This takes a cargo build -p texture after editing shader_types.h from 16seconds to around 9.7 seconds on my machine (effectively all of that time is spent generating the Rust bindings).
We're really only using one type from that file (vector_float2), but I didn't spend time further investigating how to reduce the amount of simd that we're needlessly compiling (I did investigate rust bindgen whitelists/blacklists but those just control what ends up in the final generating bindings. So no time is saved by white/blacklisting things as far as I can tell).

Because the OUT_DIR environment variable can change, the shader bindings cache would get invalidated sometimes leading to a recompilation of shader bindings.

I'm curious about more details of this scenario. When would OUT_DIR change, and what would you be building in this case that would require recompilation of the shaders?
My limited understanding is that the build script is for the examples only, it's not involved in any dependencies of the library, and thus the only scenario it's used in is when somebody checks out the repo and tries out the examples. Moreover, the extra time it would take to build if OUT_DIR was changed wouldn't be a problem, because we are talking about a developer who is just trying to run the examples.

It looks like OUT_DIR can change when certain metadata about the package changes..
(When finding that link I didn't look into what all the metadata that is considered is)
I also don't know whether or not there are ever times where OUT_DIR gets cleared.
But I do know that even as I was working on this PR I was getting recompiles of the shader types occasionally when I most definitely did not touch them.
What prompted this PR was I came back to the texture build.rs to adapt it to a different project that I'm working on and when I built the project the build script ran even though I hadn't changed anything.

Moreover, the extra time it would take to build if OUT_DIR was changed wouldn't be a problem, because we are talking about a developer who is just trying to run the examples.

In the lens of the example, yeah - which is why I almost didn't even include the caching logic in the original PR.
But then I remembered that, naturally, most developers that are getting started with metal and Rust will look at existing examples and copy from them (the entire point of an example, really).
So if one of the places they'll look first (metal-rs) has an example that encourages the wrong idea that becomes something that starts to trail through other codebases over time.
So yeah if it was just about this example the caching isn't at all useful. I'm just thinking that this example will be copied by >0 people so we should give them the best that we reasonably can.

In short - to me we're trading a small cost (adding a single line to .gitignore), for a (relatively.. emphasis on relatively) large win (bringing the number of times that a build unnecessarily takes an extra 10+ seconds down to 0)

So yeah - that's my thinking. Sorry for not including more of it in the original PR description.
As usual let me know if you think I'm off base and you see it completely differently!

But I do know that even as I was working on this PR I was getting recompiles of the shader types occasionally when I most definitely did not touch them.

If this is unrelated to the OUT_DIR, we'd still need to investigate.

bors retry

If this is unrelated to the OUT_DIR, we'd still need to investigate.

Ah sorry I meant that I was getting that before I stopped using OUT_DIR
This recompilation no longer occurs.

Perhaps you could rebase this to kick off new GH actions round?

Done

bors r+

Looks like bors never merged this

bors retry

actually, CI was all green, IIRC


Dell Avamar synthesis init

Relevant information
Request to add Dell Avamar entity synthesis definition.
Dell Avamar is DellEMC backup solution and entity synthesis required for custom integration, same as for other ext-dell_xxx definitions that are already in
Checklist

[x] I've read the guidelines and understand the acceptance criteria.
[x] The value of the attribute marked as identifier will be unique and valid.
[x] I've confirmed that my entity type wasn't already defined. If it is I'm providing an
explanation above.

Hi @KVilius, it seems like there's a problem with the newly added dashboard definition
error:  /home/runner/work/entity-definitions/entity-definitions/definitions/ext-dell_avamar/dashboard.json: Unexpected string in JSON at position 6864

Hi @KVilius, it seems like there's a problem with the newly added dashboard definition
error:  /home/runner/work/entity-definitions/entity-definitions/definitions/ext-dell_avamar/dashboard.json: Unexpected string in JSON at position 6864

Fixed

Hi @gvassallo, could you check if something else is missing?

Still got this error
../definitions/ext-dell_avamar/dashboard.json invalid
[
  {
    "instancePath": "",
    "schemaPath": "#/additionalProperties",
    "keyword": "additionalProperties",
    "params": {
      "additionalProperty": "variables"
    },
    "message": "must NOT have additional properties"
  }
]

@gvassallo - dashboard file updated, please check again.

Hi @KVilius,
the validation of the dashboard is failing. I think it's due to the trailing comma here: https://github.com/newrelic/entity-definitions/pull/943/files#diff-1faca7e325dbcaaefdb980e73a62aef4358df81a73fd76e46b34477e78fb0bfeR240
Thanks

Hi @KVilius,
it looks like that there are still some validation errors.
You can run this command https://github.com/newrelic/entity-definitions/actions/runs/4356688472/jobs/7628033409#step:5:1 also locally to check validations  (docs)

Hi @KVilius,
Thanks for the fix.
I think the last step that is missing is to run
npm --prefix validator run sanitize-dashboards

and commit the changes.
https://github.com/newrelic/entity-definitions/actions/runs/4382880466/jobs/7672448068#step:6:1


Promise.map synchronously called

What version of bluebird is the issue happening on?

Bluebird v3.3.4

What platform and version? (For example Node.js 0.12 or Google Chrome 32)

Node v5.1.1

Did this issue happen with earlier version of bluebird?

Not after Bluebird v2.9.13 for Bluebird v2.x
When .map is called after a Promise.resolve with a synchronous value, it looks like the mapper function is called synchronously:
// Actual: 1 3 4 5 2
// Expected: 1 2 3 4 5
console.log(1);

Promise.resolve([3, 4, 5]).map((i) => console.log(i));

console.log(2);

It looks like this issue was fixed for a a patch release of v2.x, but it wasn't included in v3.x.

That issue is about .each. It is unrelated to .map which is concurrent and out of order by design. To avoid it being accidentally in-order with immediate values it artificially processes items out of order so that devs realize this fact without having to read documentation.


Create singleton interface for CAL libs

We need to implement a singleton manager for CAL lib which used by another app.

@ntk148v remember to put your progress in this issue's comment, dude.

@ntk148v ping?

@hieulq: i still work on this :( Currently, i try to increase coverage percent, then we can merge my new branch. But, it is still lower than 65.741%. If we finish resource client, we can up to at least 70%. So, can we skip coverage problem, merge and update it later?

@ntk148v ok fine, go ahead and merge it

@ntk148v remember writing doc about the case study of using cal-lib.

@ntk148v ping


Database changes for a failed job are not automatically rolled back

Environment

Python version: 3.8
Nautobot version: 1.1.5-beta.1

Steps to Reproduce

Run a job that makes changes to the database and calls self.log_failure

Expected Behavior
Expected behavior is that the database transaction is rolled back.
The documentation does not state the intended behavior for database changes of failed jobs so the above is my interpretation of expected behavior, failed jobs never change the database in the run method. Even if this is not the intended behavior there can be use cases with an expected failure condition (no program error) that require previous changes to the database to be rolled-back. Rolling back the existing transaction without marking the job as errored and logging a stack trace would be desirable. Using the Nautobot defined AbortTransaction results in a terminated job that remains in status running.

Observed Behavior
The job status is failed but all changes to the database are persisted.

@nautobot/core when adopt #2726 and the changes implemented in #3085 will this go away as the atomic transaction happens within a Job author's handling (and they can capture any error done in transaction.atomic?

#2726 will leave it up to the author on how they would like to handle transactions, letting them wrap calls in transaction.atomic.


MTCVideoPlayer project fails to build

Please Confirm

[X] I have reviewed the MIDIKit Documentation which contains descriptive guides and extensive API reference
[X] I have searched Issues and Discussions to see if the same question has already been asked

macOS Version(s) Used to Build
macOS 14 Sonoma
Xcode Version(s)
Xcode 15
Description
MTCVideoPlayer fails to build.
The first issue deals with resolving the dependencies that can be handled pretty easily ...
But when dependencies are included to the project, You'll see errs in EditableTimecode.swift & AVPlayer.swift files that are probably caused by the changes and deprecations in newer releases of packages.

Thanks for the heads-up. That example project actually shouldn't be there, it's a WIP and was pushed to main by accident.


Can anyone explain how the top_p and top_k parameter affects the output of the model?

Also very interested in this!


Transport timeouts.

This implements a patch to address issue #210.
I've set up a 1 second timeout for the Dial and a 30s timeout for actual requests.
@jbowes @ianlivingstone do you think 30s is good enough for actual requests or should we consider something else?
Note: this depends on #207 to be merged in.
closes #210

@jbowes @ianlivingstone do you think 30s is good enough for actual requests or should we consider something else?

I'd bump it to 60s for safety, as it can take sometime for the Daemon to decrypt and compute results since we're not caching crypto results today.

@ianlivingstone bumped the Client Timeout to 1 minute.

with #207 merged, can you rebase this on master? the actual diff looks good though.


Export Clause and Clause Collection

First of all, thank you for your amazing job!
I tried to extend the Builder but could not because some exports were missing.
At first I tried to move all the clause things from the Query to the Builder class but could not make it work because of how generic is everything. This would have allowed us to use the Builder directly so we could extend it easily but it does not seem to work that way... And could not find on Google how to make chainable things without what you've done...
Anyways, here is a pull request to export the ClauseCollection and the Clause classes.
Have a nice day!

Hi there, thanks for your suggestions. I created a new pull request to implement the changes you suggested as it looks like you had made some other changes in this pull request as well.
Out of curiosity, what kind of extensions were you trying to make to the Builder class?

:tada: This issue has been resolved in version 5.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

Ho, yes thank you, I should have made this pull request from another branch on my fork. Thanks anyways!


Fixes and updates

We want to run the entry setup of the new state, not the previous one :)

Comments for the last commit didn't propagate over when I merged my branches, not sure why... here it is. I hope they're of interest...
"Replaced the low level SPI driver for a more generic RX5808 one.
This should allow for more flexible control of receivers and later addition of new features, including individual control of receivers, setting arbitrary frequencies, and generally improving code structure."

Woah, thanks for this! Sorry for not checking sooner, GitHub didn't give me a notification for some reason. I'll have a bit of a better look shortly. :)

This is awesome, thanks! Let me know when you're ready to merge. This branch is still a WIP for upstream too, so might get a little weird.
Purely cosmetic, but can you aim to match existing conventions? Things like:

Spaces over tabs
camelCase for methods rather than CamelCase
etc.

Happy to go over this myself afterwards either way. Pretty keen on making this is clean and standard as possible so we don't end up in a similar state as the master.

No problem. I've been meaning to do a re-write such as you've done for a while as the upstream has clearly got a bit untidy but it was such a big task that I never really got into it. Now that there's a more sensible base, I'm keen to help with features, testing and tidying etc.
I've just pushed a commit that clears up the spaces/tabs and naming. Let me know if there's anything else you think needs changing. I think I've also cleared up the conflict. I was going to try rebasing off you latest, but tbh, my github skills aren't great.

Only a few months late, but I've now made the requested formatting changes. Because I'm a bit behind, I think there's some conflicts, but they should be pretty simple fixes.


Ensure all sentences start with a capital letter and end with a point

Like the title states, ensure all sentences start with a capital letter and end with a point. Mainly under the subject commands. There are a lot of commands, maybe even all commands, where there are sentences that don't end with a point. Let's try to harmonize our writing style with each command.

E.g. the documentation for m365 adaptivecard send
https://github.com/pnp/cli-microsoft365/blob/9e5586545c531972c44ccc3b3172b9f2378677ea/docs/docs/cmd/adaptivecard/adaptivecard-send.md?plain=1#L3
Here you can append a point to the end of the description sentence.

Sends adaptive card to the specified URL.

https://github.com/pnp/cli-microsoft365/blob/9e5586545c531972c44ccc3b3172b9f2378677ea/docs/docs/cmd/adaptivecard/adaptivecard-send.md?plain=1#L13-L20
Same for all the option descriptions.

-u, --url <url>
: URL where to send the card to.
-t, --title [title]
: Title of the card.
-d, --description [description]
: Contents of the card.

Maybe let's discuss it first to see what other maintainers think.
I think it's a good idea to align it. To be honest I have been using full stops all time time while other command don't. 😀
According to me, it makes sense to always end on a full stop, especially when the description consists of multiple sentences (like: title of the list. specify either title or I'd).
If we do this, we should also update the descriptions of the global options.
But let's see what other people think because it's a drastic change. 🙂

Good point, the global options would also need a bit of fine tuning. @pnp/cli-for-microsoft-365-maintainers any feedback regarding this topic?

Since many descriptions like Title of the card miss the verb, they're not really a sentence, so I'm not so fixed on using a period at the end. I do agree that they should start with an uppercase letter.

@waldekmastykarz would it be interesting to convert those descriptions to a complete sentece? Of course not in this issue but a new one.

Since many descriptions like Title of the card miss the verb, they're not really a sentence, so I'm not so fixed on using a period at the end. I do agree that they should start with an uppercase letter.

Depends, everything can be considered as a sentence 😊
Example:
"What is this?"

"The title of the card."

Each sentence must have a verb. In "What is this" - it's is. In "The title of the card", there's none. So at minimum, we'd need to adjust it to "Defines the title of the card", but then we'd have to add the word defines, specifies, contains, etc. which in my opinion doesn't add any value or makes the text more readable.

It would indeed not add that much value but it would be consistent with descriptions that are relatively bigger. When we have a description with 2 senteces for example, then the statement "The title of the card" would look a bit out of place.

It seems like a significant amount of work with no benefit other than consistency with longer descriptions, which are more of an exception than a rule. I'd suggest that we focus on more valuable features first and close this for now.

The main reason I raised this issue is that our command descriptions are quite diverse. Some are just small statements while others have bigger explanations.

It seems like a significant amount of work with no benefit other than consistency with longer descriptions, which are more of an exception than a rule. I'd suggest that we focus on more valuable features first and close this for now.

Yeah that's true, it will require a lot of work.

And I think that's perfectly fine. We should strive to use as few words as possible to communicate the purpose of each option, because that's easier to understand than prose. In some cases, we can't avoid longer descriptions and adding an extra sentence in the description rather than remarks, makes it easier to grasp. I'd say let's use our judgement and add punctuation where it improves readability rather than making it a rule.

Good for me 👍


Rollback failed: serviceaccount not found

After upgrading the chart from 2.9.4 to 3.2.0, everthing seems to work fine. However, in order to check if a rollback would work, I have tried to rollback from chart 3.2.0 to 2.9.4 and the error I got is:
failed error: pods "pulsar-zookeeper-2" is forbidden: error looking up service account pulsar2/pulsar-zookeeper: serviceaccount "pulsar-zookeeper" not found
I dont understand why it is looking for a service account which in version 2.9.4 should not be present. Indeed from the command 'helm template' with version 2.9.4, there is no reference to this service account. But when I check for the deployed statefulset there it is:
serviceAccountName: pulsar-zookeeper
What is the reason and how can I solve the issue?

There is a chance that rollbacks aren't supported to 2.x of the chart.
The service account creation was made the default as part of #387 changes. Contributions are welcome if there's a need to change things.

Thank you @lhotari for the clarification. Is it written somewhere that it is a breaking change?

Thank you @lhotari for the clarification. Is it written somewhere that it is a breaking change?

I have updated the release notes at https://github.com/apache/pulsar-helm-chart/releases/tag/pulsar-3.2.0

Thank you. Once I've fixed that (I added the service accounts), another issue I found in rolling back is in the bookie logs: java.io.IOException: Error open RocksDB database
In the security context section I have: fsGroupChangePolicy: "OnRootMismatch" I've also tried with 'always' but I got the same error. Can it be fixed in some way?

I don't have good advice to that. The docs contains https://github.com/apache/pulsar-helm-chart?tab=readme-ov-file#upgrading-to-apache-pulsar-2100-and-above-or-helm-chart-version-300-and-above .

Another related Pulsar issue: https://github.com/apache/pulsar/issues/22051


fix(demos): Make all demos mobile-ready

Add meta viewport and any additional demo-only CSS so they can be ran in mobile emualtion and on-devices properly.
Just need one LGTM here from someone. Changes are fairly trivial and demo-specific for manual testing purposes.

LGTM. Just be sure to squash before pulling into master, so we drop the merge commit.

Squash brought both commits in...
Redoing PR fully with one commit and merging in via a second PR.


HCA - Please make dcp30 the default production release.

Please make dcp30 the default production release.
Approvals are in this Slack thread.
dcp30 has 385 datasets total, with 23 updated, 5 new datasets, and 0 re-released.
No datasets were withheld or withdrawn.

Approved:  https://humancellatlas.slack.com/archives/C9XD6L0AD/p1692833263766849?thread_ts=1690900028.334789&cid=C9XD6L0AD


Delete the master branch in the dev repos

One side effect of having the origin repos not be bare repos anymore is that they now have a master branch that propagates down to the developer repos when cloning them. I found that this causes problems in some tests that I'm currently working on where I verify branches in the developer repo. I don't want to complect (mix up two things, thereby making things more complicated) later PRs with this bug and its fix, so here it comes in its own PR.
The master branch is created on line 63 in the origin repo. The origin repo must have the master branch checked out in order to be able to receive pushes of other branches.

Can we add a comment to the function about why the origin repo has a master branch and the developer branch doesn't?

Good idea. Done.


feat(pro): add time filters - resolve #121

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


Invalid range when parsing generated yacc files.

REPRO:
0.  (This was discovered while working on #5482 and may be dependent on that.)

Set a conditional break point in the range constructor with the condition el > 100000000 (end line greater than 100 million).
Debug.

RESULT:
An expression from the generated pars.fs has an ending line of 134 million.  This eventually leads to bad PDBs being generated because a sequence point can't be properly set.
Possibly related to #4476.

@brettfo The ranges were incorrect before #4476.

Fixed in #6383.


Question: Java client "ack" ability after execute

Hello, I know that the TaskClient has the "ack" endpoint setup on it in the Java Client library. One use case that we're looking at is having a "SIMPLE" task, and when we're doing "executing" the task we'd like to then "ack" it. The reason being is that we'd like to add some output data on it and then basically put it in a "WAIT" stage by ack-ing it.
Is there an ability to set some "ack" flag on the TaskResult? If not, what's the recommended way of accomplishing this? Should we construct our Woker with the TaskClient set on the WorkflowTaskCoordinator? And then call it in there?
Thanks, and maybe there's a different strategy all together you could suggest. Basically we want a "SIMPLE" task, but then we want it to go into a WAIT stage.
Thanks.
(I am unable to add the "question" tag, sorry).

One way to achieve this would be to "complete" the simple task with status as IN_PROGRESS and set the callbackAfter to a timeout value after which the task will be rescheduled.  If you do not want the task to be rescheduled, then you can set the callbackAfter value to a large and make a call to complete the task when the task is completed.

Thank you! This should work well enough.


reusing the OTA update facility to update the SPIFFS partition (IDFGH-11309)

In an attempt to reuse the OTA functionality which is currently hard wired to only support ESP_PARTITION_TYPE_APP partitions,
this fix loosens the grip on that and enables the direct specification of the destination update_partition  via config.
the respective plausibility checks are only performed on APP type partitions now.
benefit: encouraging users to develop OTA updates of other parts of the system without bloating the code each time

Few questions:

How would the selection between active/passive custom partition happen? Or that logic is completely application (higher layer) specific?
Is it possible to share your application code which utilizes this PR to handle the custom partition OTA updates?

I am currently using this to update my spiffs image..
the code is not ripe yet, but I can provide the basic building blocks to see what how it is supposed to work
updating the spiffs would be the most probable usecase i suppose, but i cant find a a way to check the first chunk received for some kind of header info, consistancy or the like.
OTA app update bins contain a version header, SPIFFS images dont, but they have some kind of MAGIC numbers scattered across the fsif I could see at least one of them...
Currently looking for this. If you have any suggestions... I'd appreciate it.

Few questions:
* How would the selection between active/passive custom partition happen? Or that logic is completely application (higher layer) specific?

* Is it possible to share your application code which utilizes this PR to handle the custom partition OTA updates?

The steps are baaicaly these:
const esp_partition_t* esp_ota_get_data_partition(esp_partition_subtype_t subtype, const char *label) {     const esp_partition_t * p = esp_partition_find_first(ESP_PARTITION_TYPE_DATA, subtype, label);     return esp_partition_verify(p); }
The OTA Config (advanced example) would look like
esp_https_ota_config_t ota_config = { ... 		.update_partition = esp_ota_get_data_partition(ESP_PARTITION_SUBTYPE_DATA_SPIFFS, WWW_PARTITION),     };
now the OTA Task just does as usual, with some user code, to check if the "to be received OTA" is valid (this is my current working site)
...     esp_app_desc_t app_desc;     err = esp_https_ota_get_img_desc(https_ota_handle, &app_desc);     if (err != ESP_OK) {         ESP_LOGE(TAG, "esp_https_ota_read_img_desc failed");         goto ota_end;     }
    err = validate_fs_image_header(&app_desc);     if (err != ESP_OK) {         ESP_LOGE(TAG, "image header fs verification failed with 0x%x", err);         goto ota_end;     } ...

just comitted 2 more changes so esp_https_ota_get_img_desc and esp_https_ota_perform dont complain about non ESP_PARTITION_TYPE_APP partition type..
I could not figure out how to check the first bytes of spiffs image for plausibility...
If anyone has an idea, please..
the spiffs code is not really helpfull in this regard, the check functions available there are to check the overall file system

This is great feature for data/file_system partition OTA !
I think a more structured way to do it is move components/app_update/esp_ota_ops.c to another file maybe called "partition_update.c" and remove partiton_type and magic_word checking, then include this file into esp_ota_ops.c and add more strict checking

I was able to use this feature to even update bootloader and, just for fun, the partition table (yes just for the fun of it). but this needs some registering of subtypes.
I'd welcome a more generic approach of course. Judging by the now more concrete possibilities of littlefs on the horizon, we will have even more partitions to update.
I currently have a generic approach of updating the partitions with a rest api, without the need of a cloud which is small enough and using hardcoded HTML / scripts.. Nice for maintaining control of the device without internet connection.

@kohait00 for robustness, you may also want to store a var in nvs to record the state of data partition, like app partition state

Just to show another possibility, I can store data in the non-active OTA partition.
When update is performed, I first update app code, reboot to the other partition, then update data partition

Hello @kohait00
Thanks for the PR.
However I think it will be good to have a new component to support OTA for non-app partitions. We have started working on it. I think we should use app_update component only to update the app partitions as the name suggests. I will soon create a PR on https://github.com/espressif/idf-extra-components which will add support for OTA for non app partitions.

Hello @kohait00
I have created a PR for this feature. You can try it from here: https://github.com/espressif/idf-extra-components/pull/328

I am closing this MR. This feature is being developed at https://github.com/espressif/idf-extra-components/pull/328


Daemon messages l10n

Use localize package.

There is very little amount of messages generated on daemon side, except for log messages. I decided to leave log messages only in english for now, because 1) they are mostly technical, it is easier to use english for technical phrases; 2) there are a lot of messages, a lot of work for translators.

Consider this done.


LocaleSwitch documentation

I'm trying to use the LocaleSwitch component.
It renders correctly and updates the new language at this.context.translate, but the component renders with the first select option selected, no matter which option is chosen.
The strings do not update until navigating back to the page or a refresh is forced. I can make this happen by using an onChange handler and calling this.forceUpdate()
Is this the recommended way to handle a locale change?

This component has a property named setLocale (Boolean).
The default value was set to false. I think that users are expecting immediate change. I am going to change the default value to true.

Default value of the property setLocale is true in the latest version 0.0.32. I have added documentation too https://github.com/CherrySoftware/react-translate-maker#locale-switch with small roadmap for this component in short run https://github.com/CherrySoftware/react-translate-maker#roadmap
Let me know if it is working for you

Thanks, I noticed the setLocale option, but it seems like the context change isn't triggering a re-render. I thought it may have something to do with this existing limitation.

Yes you are right. I will fix it tomorrow and I will add a test too.

I have updated components LocaleSwitch and LocaleProvider. More information you can find in the documentation. I rewrote tests too. It is working correctly. You are able to use LocaleSwitch with LocaleProvider in the two modes: controlled and uncontrolled. It is up to you. Let me know what do you think. I am closing it because it is working


Exception in getCompletionDetail(mapping.dart:406)

Thread 0 main threadRangeError: RangeError (end): Invalid value: Not in inclusive range 1..2: -1content_copy
at _StringBase.substring(dart:core)
at getCompletionDetail(mapping.dart:406)
at toCompletionItem(mapping.dart:972)
at CompletionHandler._getServerDartItems.suggestionToCompletionItem(handler_completion.dart:475)
at Iterable.toList(dart:core)
at CompletionHandler._getServerDartItems.<fn>(handler_completion.dart:501)
at OperationPerformanceImpl.run(operation_performance.dart:153)
at CompletionHandler._getServerDartItems(handler_completion.dart:497)
at <asynchronous gap>(async)
at CompletionHandler.handle.<fn>(handler_completion.dart:163)
at <asynchronous gap>(async)
at OperationPerformanceImpl.runAsync(operation_performance.dart:172)
at <asynchronous gap>(async)
at CompletionHandler.handle(handler_completion.dart:201)
at <asynchronous gap>(async)
at ServerStateMessageHandler.handleMessage(handlers.dart:267)
at <asynchronous gap>(async)
at LspAnalysisServer._handleRequestMessage(lsp_analysis_server.dart:986)
at <asynchronous gap>(async)
at LspAnalysisServer.handleMessage.<fn>.<fn>(lsp_analysis_server.dart:454)
at <asynchronous gap>(async)
at OperationPerformanceImpl.runAsync(operation_performance.dart:172)
at <asynchronous gap>(async)
at LspAnalysisServer.handleMessage.<fn>(lsp_analysis_server.dart:437)

@bwilkerson @DanTup

https://dart-review.googlesource.com/c/sdk/+/295542 will fix the crash, though this code is a bit of a hack to try and get the type from a lone setter by extracting it from CompletionSuggestion.parameters. A more complete fix would be to have the setter type available on CompletionSuggestion (or have LSP use a type that's not tied to the protocol that has it).
The reason we're doing this is at all is noted here:
https://github.com/dart-lang/sdk/blob/fa3a72fa7e5818e15118044ddd68a2c2ad2dfcd0/pkg/analysis_server/lib/src/lsp/mapping.dart#L395-L398

I have proposed a refactoring of the code completion engine that would include having a protocol-agnostic representation of suggestions that would include all of the information needed to produce either protocol's representation. I think that's the cleanest solution going forward.

This still happens on 3.1.0-edge.fa3a72fa7e5818e15118044ddd68a2c2ad2dfcd0.
Thread 0 main threadRangeError: RangeError (end): Invalid value: Not in inclusive range 1..2: -1
at _StringBase.substring(dart:core)
at getCompletionDetail(mapping.dart:406)
at toCompletionItem(mapping.dart:972)
at CompletionHandler._getServerDartItems.suggestionToCompletionItem(handler_completion.dart:475)
at Iterable.toList(dart:core)
at CompletionHandler._getServerDartItems.<fn>(handler_completion.dart:501)
at OperationPerformanceImpl.run(operation_performance.dart:153)
at CompletionHandler._getServerDartItems(handler_completion.dart:497)
at <asynchronous gap>(async)
at CompletionHandler.handle.<fn>(handler_completion.dart:163)
at <asynchronous gap>(async)
at OperationPerformanceImpl.runAsync(operation_performance.dart:172)
at <asynchronous gap>(async)
at CompletionHandler.handle(handler_completion.dart:201)
at <asynchronous gap>(async)
at ServerStateMessageHandler.handleMessage(handlers.dart:267)
at <asynchronous gap>(async)
at LspAnalysisServer._handleRequestMessage(lsp_analysis_server.dart:986)
at <asynchronous gap>(async)
at LspAnalysisServer.handleMessage.<fn>.<fn>(lsp_analysis_server.dart:454)
at <asynchronous gap>(async)
at OperationPerformanceImpl.runAsync(operation_performance.dart:172)
at <asynchronous gap>(async)
at LspAnalysisServer.handleMessage.<fn>(lsp_analysis_server.dart:437)

I don't see it anymore in latest builds.


Feature : complex post /entities API

This PR include

complex post /entities PI
handling for 404,504 error cases thrown by vertx router.

Surefire Report.pdf
Newman Summary Report.pdf


Use chipdb*.bin files

Hi, Is there a plan to unify the chipdb binary files between Icestorm and Arachne-pnr?
Now there is a share/icebox directory with the chipdbs*.txt (about ~44Mb) and other share/arachne-pnr directory with the same information chipdb*.bin (about ~12Mb) for the same toolchain.
Do you plan to generate those chipdb*.bin from the icebox tools and read those chipdb*.bin files in the icetime tool?
Thanks!

Do you plan to generate those chipdb*.bin from the icebox tools and read those chipdb*.bin files in the icetime tool?

No. and No.
Creating chipdb*.bin from icebox is almost impossible as icebox is written in python and the chipdb.bin files are created/read using the standard c++ serializer/deserializers (see ChipDB::bread() and ChipDB::bwrite() in arachne-pnr).
For the same same reason it is virtually impossible to read those chipdb*.bin files without copying (and keeping in sync) large amounts of code between icetime and arachne-pnr.


Problem with custom google apps domains?

I can't get this to work at all for my work Google calendar...
Is it possible that using the private Gcal link from a custom domain is the problem?
I've uninstalled then reinstalled the plugin.
The menu icon appears as expected when its first reinstalled, then I updated the settings fie as follows:
{
  "disabled": false,
  "template": "{Start} - {End}: {Title}",
  "templateLine2": "{Description}",
  "accounts": {
    "Google Calendar": [
      "https://calendar.google.com/calendar/ical/my.name%40mydomain.com.au/private-98234e7210f186de0bbfad56a0867273/basic.ics"
    ],
  },
  "timeFormat": 12
}

Once my setting file is created, then the menu icon no longer appears in my Logseq...

If you open the link in an incognito tab, does it download a file called basic.ics?
On 9 Feb 2022, 8:39 AM +0400, Richard Foxworthy @.***>, wrote:

I can't get this to work at all for my work Google calendar...
Is it possible that using the private Gcal link from a custom domain is the problem?
I've uninstalled then reinstalled the plugin.
The menu icon appears as expected when its first reinstalled, then I updated the settings fie as follows:
{
"disabled": false,
"template": "{Start} - {End}: {Title}",
"templateLine2": "{Description}",
"accounts": {
"Google Calendar": [
"https://calendar.google.com/calendar/ical/my.name%40mydomain.com.au/private-98234e7210f186de0bbfad56a0867273/basic.ics"
],
},
"timeFormat": 12
}
Once my setting file is created, then the menu icon no longer appears in my Logseq...
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Hi @sawhney17  Yes it does download the basic.ics file.
I guess this means that something else must be the issue?

@sawhney17 Hey, I am going through a similar problem and found the request sent by the plugin got an 404 error:

But opening the ics url in incognito mode can get the ics file being downloaded correctly.

Can you make sure that you actually have tasks for the day. Are any of the tasks recurring? I haven't implemented logic for that yet.

@sawhney17 Actually I am experiencing something similar. I am using the secret url from google, but I am using google workspace. The error I get is the following:
Here is my full settings json (I created a test-calendar with a test-event, so that you can try it with a real secret url):
{
  "template": "{Start} - {End}: {Title}",
  "useJSON": false,
  "IndentCommonBlock": false,
  "templateLine2": "{Description}",
  "timeFormat": [
    "12 hour time",
    "24 hour time"
  ],
  "calendar1Name": "PersonalCalendar",
  "calendar1URL": "https://calendar.google.com/calendar/ical/c_3a90a6087267d0c4c05cc2cbabd5d51ec4b5784b368d9d3727f43ff56a1b8356%40group.calendar.google.com/private-6a61a5c11efa33d6ca3d8ab6a5a830a9/basic.ics",
  "calendar2Name": "",
  "calendar2URL": "",
  "calendar3Name": "",
  "calendar3URL": "",
  "calendar4Name": "",
  "calendar4URL": "",
  "calendar5Name": "",
  "calendar5URL": "",
  "disabled": false,
  "accountsDetails": {
    "Calendar 1": "https://calendar.google.com/calendar/ical/..."
  }
}

The url allows me to download a ics in incognito. Is it possible that it isn't able to handle the %40 urlescape in the url properly? Or is that handled correctly?


create markdown files for HoTT library

@javra @fpvandoorn These are just for prettier browsing. Feel free to edit them.
The HoTT library is looking really nice!
In init, types like bool and nat are at the top level, but empty, prod, sigma, and sum are in the "types" subfolder. Is there a reason for that? (I am fine with it -- I am just curious.)

Changes Unknown when pulling 984c40dde64f96aecaa5b7d5c720360aaa6c0b8f on avigad:master into ** on leanprover:master**.


Direct Lake Prerequisites Need To Include Data Warehouse

Since Fabric Data Warehouse is eligible for Direct Lake, it should be added to the Prerequisites section instead of only having Lakehouse there.

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

ID: b4140ce1-5f43-81b2-36c4-cf90b2a72682
Version Independent ID: b4140ce1-5f43-81b2-36c4-cf90b2a72682
Content: Learn about Direct Lake in Power BI and Microsoft Fabric - Power BI
Content Source: powerbi-docs/enterprise/directlake-overview.md
Service: powerbi
Sub-service: powerbi-premium
GitHub Login: @Minewiskan
Microsoft Alias: owend

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Not sure what’s happening, but I’m getting this email over and over and over again.
Sincerely,
Jacob Golden | Director of Data & Insights |<PHONE_NUMBER>
[signature_2150300396]
From: Bishal Goswami @.>
Date: Thursday, January 11, 2024 at 8:01 PM
To: MicrosoftDocs/powerbi-docs @.>
Cc: Jacob Golden @.>, Mention @.>
Subject: Re: [MicrosoftDocs/powerbi-docs] Direct Lake Prerequisites Need To Include Data Warehouse (Issue #4919)
Thanks for your comment, @jacobgexigohttps://github.com/jacobgexigo. This issue has been assigned to the doc author for review.
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/powerbi-docs/issues/4919#issuecomment-1888296744, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHDHW5O3NXGYTZ5VLHZTCRLYOCKQRAVCNFSM6AAAAABAVADMBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBYGI4TMNZUGQ.
You are receiving this because you were mentioned.Message ID: @.***>
Caution: This is an external email. Please take care when clicking links or opening attachments. When in doubt, contact your IT Department!

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. This issue has been assigned to the doc author for review.

Thanks for your comment, @jacobgexigo. It's been added.


Better auto colors

When changing themes in terminal vim using autocolors this plugin
currently defaults to using darkgrey and black (for dark
backgrounds) or lightgrey and white (for light backgrounds) for the
indent color. These colors often clash with otherwise harmonious themes.
In complete themes the Normal and CustomCursor background colors are
set which provide theme-appropriate indent colors.

It looks like this got closed without being merged but might still be relevant. There are merge conflicts because some of this has gotten implemented a different way, but I'm going to re-open anyway to review the CursorColumn handling.


Changed cache mode to LOAD_DEFAULT to enable caching

As discussed in https://github.com/PierfrancescoSoffritti/android-youtube-player/issues/869

Thanks!


Vue loosing bindings even using $set method when using keypath props values

I have some strange behavior after upgrading to vue-0.12.9.
I'm not sure what's going on, can't explain really. I've created simplified fiddle to demonstrate it http://jsfiddle.net/plunntic/ydjzhkn8/
Not sure if it's me doing something wrong, but it looks more like vue having problems with bindings?

I've updated the fiddle with some more examples, it looks like vue is loosing the bindings even when using $set method, when using keypath value for a prop, like my-prop="{{ my_model.my_array }}".

You shouldn't be initializing some_model in the created hook. You should be returning it inside the data option, which is specifically for initializing observed properties:
data: function () {
  return {
    some_model: { ... }
  }
}


validator fails on any 3.1 spec

Running the validator against a 3.1 spec immediately results in the error
'float' object has no attribute 'startswith'

Looks like a Python type error. Tried on Python 3.8 and 3.11 and both throw the error. No issues with a 3.0 spec.

Incorrectly raised. The first line was
openapi: 3.1

but it should be
openapi: "3.1.0"


Update some fix comments.

Primary handling changed in #5824.
cargo_as_rustc_wrapper changed in #6759.

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

@bors: r+

:pushpin: Commit 247063c35b40a0827c84f495cc8bdab9020a7438 has been approved by alexcrichton

:hourglass: Testing commit 247063c35b40a0827c84f495cc8bdab9020a7438 with merge 5277137d854f8a8b351b22f5d95aafe8fbe696f4...

:sunny: Test successful - checks-travis, status-appveyor
Approved by: alexcrichton
Pushing 5277137d854f8a8b351b22f5d95aafe8fbe696f4 to master...


USEID-377 monitor eid service

Add counters and timers to the eid service calls. I don't know if there is a better way to annotate inherited methods other than overriding and calling super.

I agree that the controller contains a lot of code and is packed. However, I think the service communication part should be extracted into its own thing to slim down the controller. The success and response counting should happen where we handle the responses, the call counting is done by the timed annotations.


5057 restartpolicy default

Updated two help topics to clarify that the default = always
Updated all the types.go files to include statement of what default is (in descriptions)
Ran "hack/update-swagger-spec.sh" to build output .json files for swagger UI
(note, it looks like the script was not run in a long while and this output includes several other changes that i did not deliver)

Fixes #5057

Great, thanks! Just a few comments:

I noticed that update-swagger-spec.sh was never updated to generate
${SWAGGER_ROOT_DIR}/v1.json
Can you add to that script a line at the end that does
curl ${SWAGGER_API_PATH}api/v1 > ${SWAGGER_ROOT_DIR}/v1.json
and then re-run the script and add the new file it generates (v1.json) to your PR?

Our standard practice on the team is to squash all the commits into one, so please squash your two commits into one

After squashing  (or as part of squashing), please add to the commit message "Fixes #5057" so that merging automatically closes the issue.

Thanks David for all the help on this.
I asked Nikhil because i was concerned and he suggested that I leave the .json output as a separate commit since the build i ran picked up a bunch of other changes that werent mine (ill remember to comment on my intentions next time).
Also to share what i learned (and for future reference), you need the following, in this order, to run to build the new .json files:

Environment setup as defined here (where GO and Etcd are installed and in your PATH and k8s is cloned to your GOPATH)
Run "hack/build-go-sh"
Run "hack/update-swagger-spec.sh"

Hmm, the v1.json file that got generated is empty. That's weird. Maybe just remove your update-swagger-spec.sh changes, and v1.json, from this PR, and then we could fix update-swagger-spec.sh and add v1.json in a followup PR. Sorry for sending you down that road; I'm not sure what the problem is.

LGTM


5.13.0 and <IP_ADDRESS> are the same file

Hey, sorry to bother you again.
I compared my locally generated docset with the one you added to Dash User Contributions.
5.13.0 and <IP_ADDRESS> are the same file.
> shasum versions/5.13.0/Qt_for_Python.tgz; shasum versions/<IP_ADDRESS>/Qt_for_Python.tgz
a31b5eb7696f0225b746ae3423bd8b046a3c2593  versions/5.13.0/Qt_for_Python.tgz
a31b5eb7696f0225b746ae3423bd8b046a3c2593  versions/<IP_ADDRESS>/Qt_for_Python.tgz

I pushed the new packed docset to my fork in case you want to use it. https://github.com/okletzmayr/qt-for-python-to-dash-docset/commit/143ed678f6d6006caa7e0ac953becfc0d63a0579
And thanks for the super fast response to my last pull request, I appreciate it.

I am indeed very sorry that I missed the checksums between docset versions and late response.
I will update Dash User Contributions later.

No worries. At this point we might as well wait for the 5.15 Release, which is scheduled for next week. You could push both 5.15 as an update, and this 5.14.2 version for legacy reasons next week. I'll generate the 5.15 docset for myself anyways; I could open a pull request again.

closed by https://github.com/Kapeli/Dash-User-Contributions/pull/2794


SearchTarget.MatchAny

Like how the array.empty is recommended for things,
add a special const SearchTarget that would be short hand for matching any target.
Ideally, lift this code from the /anyfile flag in the front end.
Note the plan would be static const variable for this.

To the Future

For later


Format changes content in tsx

VSCode Version: 1.7
OS Version: OS X 10.11.6

Before formatting
import * as React from "react";

export interface HelloProps { compiler: string; framework: string; }

export class Hello extends React.Component<HelloProps, {}> {
    render() {
        return
Hello from {this.props.compiler} and {this.props.framework}!
;
    }
}

After Document Format with 2 spaces:
import * as React from "react";

export interface HelloProps { compiler: string; framework: string; }

export class Hello extends React.Component<HelloProps, {}> {
  render() {
    return
Hello from {this.props.compiler}and {this.props.framework}!
;
  }
}

The space between } and is gone after formatting.

This issue was moved to Microsoft/TypeScript#12001


Account template to create account with limits

Corresponds to API: /cloudapi/accounts/create
Note: Docs and tests must be included
part of #64

functionality is verified, but this section in documentation needs fix
https://github.com/Jumpscale/ays9/tree/master/templates/ovc/account#example-for-creating-an-account

This is fixed by #143

software version
master : 47b1b4a


chore[elasticsearch]: support new api

…573)
(cherry picked from commit eca4ffbad9d615b2368dd96278a38520cb888436)

/cherry-pick release-0.9


Error: Dart library 'dart:html' is not available on this platform.

Error:
Error: Dart library 'dart:html' is not available on this platform.
import 'dart:html' show Blob, FormData, UrlSearchParams;
       ^
Info: The unavailable library 'dart:html' is imported through these packages:

    package:supabase_edge_functions_example => package:dart_openai => package:fetch_client => package:fetch_api => dart:html

Any edge function that references packages that nest dart:html should trigger this.
https://github.com/anasfik/openai
uses
https://github.com/Zekfad/fetch_client
uses
https://github.com/Zekfad/fetch_api
Example:
create new edge function
dart pub add fetch_api
import 'package:supabase_functions/supabase_functions.dart';
import 'package:fetch_api/fetch_api.dart' as api;

void main() {
  SupabaseFunctions(fetch: (request) {
    void main() async {
      // Simple cors request
      final response = await fetch(
        Resource('https://api.restful-api.dev/objects/1'),
      );

      print(await response.text());
    }

    return Response("Hello from Supabase Edge Functions!");
  });
}

This all makes sense in that dart_edge has created a custom fetch client, but some packages use custom fetch clients as well. I am attempted to get the dart_openai package to work, which uses conditional importing of the referenced fetch package here:
https://github.com/anasfik/openai/blob/aa42ccee89c0fef5b4102eceee11d28890d0bcdb/lib/src/core/networking/client.dart
if I remove the conditional import so that it only sees the http_client_io, the package will compile as an edge function. If the conditional import is present based on dart.library.io, or even refactoring the imports to look like this
import 'package:dart_openai/src/core/utils/http_client_io.dart'
    if (dart.library.js) 'package:dart_openai/src/core/utils/http_client_web.dart'
    if (dart.library.io) 'package:dart_openai/src/core/utils/http_client_io.dart';

I run into the error referenced above as the import takes the web path. I am not sure if this is directly a dart_edge issue, but thought I would start here as it is likely similar imports / nesting of dart:html will be found across the package ecosystem.

Unfortunately the Zekfad/fetch_api package is assuming the user is running on the web environment, not a JS one. I'll take a look at the openai package but I'm not sure there's much we can do.

Hmm, replacing this:
fetch.FetchClient createClient() =>
    fetch.FetchClient(mode: fetch.RequestMode.cors);

with
import 'package:edge_http_client/edge_http_client.dart';

http.Client createClient() => EdgeHttpClient();

Could do the trick.

The problem is that the code execution follows the JS path for building edge functions, if it followed the normal io path it seems your override would work. If I remove the web dependency from the lib the edge function compiles fine.

After forcing the import path, or modifying the package to use
import 'package:edge_http_client/edge_http_client.dart';

http.Client createClient() => EdgeHttpClient();

as suggested, I now see the same issue as in https://github.com/invertase/dart_edge/issues/34. Will close this to resolve there.


Typo fixes

Fixes #427 and #412.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: mtroiani sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


[Question] Multi sites / apps support

Is it possible with one install to manage multiple apps / sites? Is it possible for each app to have its separate database? Or would his one single db separate on roles/groups?

https://github.com/agentejo/cockpit/issues/673


snapshot isolation is now an opt-in setting

Hi @mjaric, I changed the snapshot isolation like we discussed in #65. Does this work for you?

Note: I used Jose's preferred method as discussed here

that is idea, I will merge it and do small change. Thanks!

in hex  v1.0.16


about 08-asvspoof-activelearn

Dear author,
when I tried to run the bash script in the 08 project, I saw the following error in the training log.
(pytorch-1.7) ming@LAPTOP-EMOK5QV6:/mnt/d/UNI/IFM/project-NN-Pytorch-scripts/project/08-asvspoof-activelearn$ bash 00_demo.sh model-AL-NegE config_AL_train_toyset 01

=======================================================
Step1. Preparation: load environment and get toy data
Conda environment fairseq-pip2 has been installed

=======================================================

=======================================================
Step3. training on toy set
bash 01_train.sh 01 config_AL_train_toyset model-AL-NegE/config_AL_train_toyset/01 16 5 2 0.000001 /mnt/d/UNI/IFM/project-NN-Pytorch-scripts/project/08-asvspoof-activelearn/seed_model/w2v-ft-gf_trained_network.pt
cd model-AL-NegE/config_AL_train_toyset/01
Training starts
Please monitor the log trainig: /mnt/d/UNI/IFM/project-NN-Pytorch-scripts/project/08-asvspoof-activelearn/model-AL-NegE/config_AL_train_toyset/01/log_train

python main.py --model-forward-with-file-name --num-workers 4 --epochs 2 --no-best-epochs 100 --batch-size 16 --lr 0.000001 --seed 01 --module-config config_AL_train_toyset --active-learning-cycle-num 5 --active-learning-new-sample-per-cycle 16 --trained-model /mnt/d/UNI/IFM/project-NN-Pytorch-scripts/project/08-asvspoof-activelearn/seed_model/w2v-ft-gf_trained_network.pt >log_train 2>log_train_err
Training process finished
Trainig log has been written to /mnt/d/UNI/IFM/project-NN-Pytorch-scripts/project/08-asvspoof-activelearn/model-AL-NegE/config_AL_train_toyset/01/log_train

=======================================================
Step4. score the toy data set
ls: cannot access 'model-AL-NegE/config_AL_train_toyset/01/trained_network*.pt': No such file or directory
(pytorch-1.7) ming@LAPTOP-EMOK5QV6:/mnt/d/UNI/IFM/project-NN-Pytorch-scripts/project/08-asvspoof-activelearn$ bash 00_demo.sh model-AL-NegE config_AL_train_toyset 01

=======================================================
Step1. Preparation: load environment and get toy data
Conda environment fairseq-pip2 has been installed

=======================================================

=======================================================
Step3. training on toy set
bash 01_train.sh 01 config_AL_train_toyset model-AL-NegE/config_AL_train_toyset/01 16 5 2 0.000001 /mnt/d/UNI/IFM/project-NN-Pytorch-scripts/project/08-asvspoof-activelearn/seed_model/w2v-ft-gf_trained_network.pt
cd model-AL-NegE/config_AL_train_toyset/01
Training starts
Please monitor the log trainig: /mnt/d/UNI/IFM/project-NN-Pytorch-scripts/project/08-asvspoof-activelearn/model-AL-NegE/config_AL_train_toyset/01/log_train

python main.py --model-forward-with-file-name --num-workers 4 --epochs 2 --no-best-epochs 100 --batch-size 16 --lr 0.000001 --seed 01 --module-config config_AL_train_toyset --active-learning-cycle-num 5 --active-learning-new-sample-per-cycle 16 --trained-model /mnt/d/UNI/IFM/project-NN-Pytorch-scripts/project/08-asvspoof-activelearn/seed_model/w2v-ft-gf_trained_network.pt >log_train 2>log_train_err
Training process finished
Trainig log has been written to /mnt/d/UNI/IFM/project-NN-Pytorch-scripts/project/08-asvspoof-activelearn/model-AL-NegE/config_AL_train_toyset/01/log_train

=======================================================
Step4. score the toy data set
ls: cannot access 'model-AL-NegE/config_AL_train_toyset/01/trained_network*.pt': No such file or directory

in /08-asvspoof-activelearn/model-AL-NegE/config_AL_train_toyset/01/log_train_err
Traceback (most recent call last):
  File "main.py", line 276, in <module>
    main()
  File "main.py", line 162, in main
    model = prj_model.Model(trn_set.get_in_dim(), \
  File "/mnt/d/UNI/IFM/project-NN-Pytorch-scripts/project/08-asvspoof-activelearn/model-AL-NegE/config_AL_train_toyset/01/model.py", line 292, in __init__
    self.m_front_end = FrontEnd(self.v_feat_dim,
  File "/mnt/d/UNI/IFM/project-NN-Pytorch-scripts/project/08-asvspoof-activelearn/model-AL-NegE/config_AL_train_toyset/01/model.py", line 109, in __init__
    self.ssl_model = SSLModel(mpath, ssl_out_dim)
  File "/mnt/d/UNI/IFM/project-NN-Pytorch-scripts/project/08-asvspoof-activelearn/model-AL-NegE/config_AL_train_toyset/01/model.py", line 56, in __init__
    md, _, _ = fq.checkpoint_utils.load_model_ensemble_and_task([mpath])
AttributeError: module 'fairseq' has no attribute 'checkpoint_utils'

I want to know why? And I would like to ask how to use the pre-trained model in the downloaded folder project08-seed-model.tar to evaluate the wild data set?It would be great if you could offer some advice, I look forward to hearing from you. have a beautiful day
Best regards,
Ming

@Tianming40 Sorry for the late reply. It is a busy period for paper submission.

AttributeError: module 'fairseq' has no attribute 'checkpoint_utils'
This looks like an issue with fairseq installation.

Could you check the version of fairseq?
(fairseq-pip2) $: python -c "import fairseq;print(fairseq.__version__)"
1.0.0a0+862efab

I would like to ask how to use the pre-trained model in the downloaded folder project08-seed-model.tar to evaluate the wild data set?

I think you can follow the demo script here to execute the inference.
https://github.com/nii-yamagishilab/project-NN-Pytorch-scripts/blob/e269196d8bf3d3730bedc284b720e481ea7f16ca/project/08-asvspoof-activelearn/00_demo.sh#L104
I don't have clever ideas on how to make pre-trained models work in the wild. It is usually very challenging.
Maybe you can fine-tune the model with some development set data from that domain?


Landing page

Yet another PR that needs @scottkellum's Travis config! This one automatically builds the project and commits everything in the demo folder, including the newly built JavaScript, to the gh-pages branch. This means that the page will be hosted on GitHub Pages (e.g. for my fork). Once this is done we will be able to host the page on js.org, at cjss.js.org.
Eventually we will hopefully be able to produce a full landing page for this project, similar to the README.

From #35:
Use ESLint to maintain consistent coding style.
In order to get this to work with Travis, a repo admin (@scottkellum?) will need to log into Travis with GitHub and authorise the repository. https://docs.travis-ci.com/user/tutorial/
This will mean that commits that do not match the style guide will automatically show up as such in GitHub, and hopefully your editor should support linting.


Initial implementation of stepping back on Windows

This is an initial implementation of saving previous steps when stepping through the process on Windows.
The command is available in the Control -> Step back menu. This feature works similarly to what is implemented in Visual Studio Enterprise. If you stepped through a specific line, you'll be able to step back to it and inspect all locals and call stack (even the objects that were not expanded before, or with different view rules). The snapshots are released once the target enters run state again (continue).
Internally, a new entity kind is created in df and demon that represents a snapshot. Snapshots are children of threads and are created using PssCaptureSnapshot which greatly simplifies the implementation as Windows takes care of doing all of the copy-on-write work that's required to preserve the state. Once a snapshot is activated, we just change the entity we are reading from.
Things to check:

potential bugs/annoyances?

Can't wait for this to be merged.


Uprade swagger-core to 1.5.20 to pickup bug fix

https://github.com/swagger-api/swagger-core/issues/2707

Please fix the now failing tests. See the travis-ci log.

@dantran This PR is causing test failures. These failures must be fixed before the PR can be considered.

sorry about the noise,  i need to decline this PR due to time constraint

The failing tests look like they are related to the issue https://github.com/swagger-api/swagger-parser/issues/772.
@dantran I would love to take on these issues, and finalize the PR, with your OK?


Add toggle for specifying dynamic filtering refresh interval

Previously, dynamic filtering refresh interval was set to
"task.status-refresh-max-wait". However, task status will be
refreshed more frequently since "task.status-refresh-max-wait"
specifies  max wait. Therefore a dedicated refresh toggle is added.
This toggle is marked as experimental as it will eventually be replaced by
delta-based task status update mechanism.

Not sure what is the config parameters deprecation policy. E.g If plan to remove it soon anyway should we maybe already mark it as @deprecated?

I think @experimental fits the toggle more. Note that experimental toggles might still be removed. IMO @deprecated is for long existing toggles which reach end of life.

Also I was not able to understand motivation for the change based on commit message :)

I've improved it slightly


Sprockets::Rails::Helper::AssetFilteredError in RailsAdmin::Main#dashboard

i'm still facing this problem all the day , it tells me
Asset filtered out and will not be served: add Rails.application.config.assets.precompile += %w( rails_admin/aristo/images/bg_fallback.png ) to config/initializers/assets.rb and restart your server
i'm still adding the lines and it still tell me to add other lines (line by line) it's the first time that happend to me with rails_admin

I have faced this issue too.
I have solved it by adding the following line to /config/initializers/assets.rb:
Rails.application.config.assets.precompile += ['rails_admin/**/*', 'fontawesome-webfont.*']

Hope this helps you too!


dioxus-cli build failed

I think you need build it from git repo: cargo install --git https://github.com/DioxusLabs/cli


Can not change input method of fcitix via command 'xkb-switch -s'

OS: Debian GNU/Linux 11
Linux: 5.10.0-8-amd64
xkb-switch version: 1.8.5
I'm using fcitix-rime and have two input methods:

What is the result of xkb-switch -l?
I met the same problem for ibus, which I have us and pinyin, but xkb-switch -l only return us.

I have tested it work for some language, but it cannot for ibus-libpinyin and fcitx-libpinyin.

It should be the bug only of xkb-switch, because @lyokha 's g3kb-switch  can work:

I think xkb-switch cannot work for ibus IME, it only work for xkb keyboard.
$ gsettings get org.gnome.desktop.input-sources sources
[('xkb', 'us'), ('ibus', 'rime')]

If you want to input Chinese characters in vim, I think https://github.com/tonyfettes/coc-rime?tab=readme-ov-file#related-projects should be useful for you.


Don't run formatter if file present in root

The find property is great for noting when to run a task. I see that there is also ignore_pattern for a particular file.  But say I have two formatters, one of which I run conditionally if a file is present, and the other only if that first one is not matched, how can I do this with the current API?  The original issue asking for the conditional with a function would cover both cases, where this is only an "if exists".  Let me know if I'm missing something!

@glepnir something to maybe consider. People want things to run in weird use cases. Turning a variable into a with a few lines is reasonable I think

maybe we can allow communication between multiple configurations.

or maybe provide api for writing unique formatting logics in the fn field

I understand your ask for a function that lets you express both cases. I agree this could lead to cleaner configurations for complex use cases such as yours.
Regarding your ask for how to cover your use case with the current API, wouldn't you be able to successfully achieve this via:
local matched_file = 'some-file';

ft('lang'):fmt({
  -- First formatter
  ...
  find = { matched_file },
}):append({
  -- Second formatter
  ...
  ignore_pattern = { matched_file },
})

The second formatter isn't explicitly triggering because the first one didn't match, however, this is functionally the same because the find/ignore_pattern parameters are set to the opposite of each other. So functionally, the second formatter only runs when the first one doesn't run & vice versa.
Wouldn't this work? Or perhaps I'm missing something?

@pauldiloreto ignore_pattern matches against the file you are formatting and not a root dir file
Got it, my mistake.

With that note, would it be sufficient to support glob patterns so we could pass a negative wildcard? Or perhaps just regex at that point?
Or would it be better to just have a function API like you mentioned earlier in this thread?

I plan to do the api approach since it offers more flexibility (if no one is opposed to that)

I plan to do the api approach since it offers more flexibility (if no one is opposed to that)

Sounds good to me.
I just realized that this would also allow support for the use case of scanning a file (i.e. package.json) for certain keys and only running a formatter if some configuration is present there.

I plan to do the api approach since it offers more flexibility (if no one is opposed to that)

sounds good to me


Add usage instructions with GitHub template

Same as https://github.com/mirego/elixir-boilerplate/pull/56

Since the repo is now a ”template” on GitHub, instructions should take advantage of this.
I also updated the classic instructions since they were outdated.

🦀 Requesting reviewers for this pull request:

@charlesdemers (contributor with 5 commits in the last 90 days and 83 commits overall)


Use e1000 ethernet driver in qemu_x86

Allow user transparently use e1000 ethernet driver in qemu_x86 board.
Usage:
cd samples/net/echo_server
mkdir build && cd build
cmake .. -DBOARD=qemu_x86 -DOVERLAY_CONFIG=overlay-e1000.conf
make run

You must also run net-setup.sh script from net-tools project that will setup host side corretly.
There is some configuration issue either with e1000 or in qemu as the connectivity does not really work as expected. Some initial IPv6 packets are seen in the interface when zephyr boots but after few seconds no packets are received nor sent by zephyr.

Should this be done before or after "make run"?

Before, so that host setup is ok and qemu can be started as a normal user.

So, should this be DNM for now?

There is DNM label set already for this PR.

Codecov Report

Merging #11138 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #11138   +/-   ##
=======================================
  Coverage   53.11%   53.11%
=======================================
  Files         218      218
  Lines       26868    26868
  Branches     5952     5952
=======================================
  Hits        14271    14271
  Misses      10162    10162
  Partials     2435     2435

Continue to review full report at Codecov.

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

There is some configuration issue either with e1000 or in qemu as the connectivity does not really work as expected. Some initial IPv6 packets are seen in the interface when zephyr boots but after few seconds no packets are received nor sent by zephyr.

Ok, so for me the situation remains the same as before (as was reported in https://github.com/zephyrproject-rtos/zephyr/pull/9112): Zephyr can send packets to host. Host receives them. Host sends replies back. But Zephyr never receives anything, and reason for that is quite obvious: e1000 RX interrupt never fires!
Here's for example how net ping <IP_ADDRESS> from Zephyr shell looks in Wireshark:
10	50.580612214	RealtekU_12:34:56	Broadcast	ARP	42		Who has <IP_ADDRESS>? Tell <IP_ADDRESS>
11	50.580622235	IcannIan_00:53:ff	RealtekU_12:34:56	ARP	42		<IP_ADDRESS> is at 00:00:5e:00:53:ff

I.e. Z sends ARP, the host replies, but Z never see that reply:
uart:~$ net stats

Interface 0x00426660 (Ethernet) [0]
===================================
IPv6 recv      0	sent	5	drop	0	forwarded	0
IPv6 ND recv   0	sent	5	drop	0
IPv6 MLD recv  0	sent	0	drop	0
IPv4 recv      0	sent	2	drop	0	forwarded	0
IP vhlerr      0	hblener	0	lblener	0
IP fragerr     0	chkerr	0	protoer	0
ICMP recv      0	sent	2	drop	0
ICMP typeer    0	chkerr	0
UDP recv       0	sent	0	drop	0
UDP chkerr     0
TCP bytes recv 0	sent	0
TCP seg recv   0	sent	0	drop	0
TCP seg resent 0	chkerr	0	ackerr	0
TCP seg rsterr 0	rst	0	re-xmit	0
TCP conn drop  0	connrst	0
Bytes received 0
Bytes sent     344
Processing err 0

Similarly for IPv6:
15<PHONE_NUMBER>20	2001:db8::1	ff02::1:ff00:2	ICMPv6	86		Neighbor Solicitation for 2001:db8::2 from 52:54:00:12:34:56
16<PHONE_NUMBER>35	2001:db8::2	2001:db8::1	ICMPv6	86		Neighbor Advertisement 2001:db8::2 (sol, ovr) is at 00:00:5e:00:53:ff

@jukkar, we have many cases when such investigations were deadlocked because another side was too lazy busy to do the obvious next steps in testing. Let's try to get on the same line now:

Please apply the following patch:

diff --git a/drivers/ethernet/eth_e1000.c b/drivers/ethernet/eth_e1000.c
index 996d4b12d8..d783ff72b7 100644
--- a/drivers/ethernet/eth_e1000.c
+++ b/drivers/ethernet/eth_e1000.c
@@ -130,6 +130,7 @@ out:

 static void e1000_isr(struct device *device)
 {
+printk("e1000_isr\n");
        struct e1000_dev *dev = device->driver_data;
        u32_t icr = ior32(dev, ICR); /* Cleared upon read */

Please show the exact dump from "make run" followed net ping <IP_ADDRESS>, with either "e1000_isr" being printed, or with none of them.

For the output is:
SeaBIOS (version rel-1.11.2-0-gf9626ccb91-prebuilt.qemu-project.org)

iPXE v1.0.0-591-g7aee315
iPXE (http://ipxe.org) 00:02.0 C000 PCI2.10 PnP PMM+007983C0+007583C0 C000

Booting from ROM..

uart:~$ ***** Booting Zephyr OS zephyr-v1.13.0-1622-g8aa65494c8 *****

uart:~$ net ping <IP_ADDRESS>
Sent a ping to <IP_ADDRESS>
Ping timeout
uart:~$ QEMU: Terminated

Oh, and I'm on:
ZEPHYR_SDK_INSTALL_DIR=/home/pfalcon/opt/zephyr-sdk-0.9.5

of course

@pfalcon Please note that this PR is not really about e1000 and if it works or not. The motivation about this PR was to make integration to user workflow seamless, this PR could probably easily used with stellaris driver too.
As I said also in description, the connectivity does not really work for me either. I see some packets sent / received for few seconds but after that the interface becomes a black hole. Of course the e1000 needs to be get working before this PR can be merged, it would be very confusing for end user if this is merged with broken e1000 driver.

@jukkar

@pfalcon Please note that this PR is not really about e1000 and if it works or not.

So, do you suggest that I should resend this request:

Please show the exact dump from "make run" followed net ping <IP_ADDRESS>, with either "e1000_isr" being printed, or with none of them.

to you via private email or some other means, or would you be able to reply here after all?

@jukkar: Oh, that's easy to rectify. Can you please do the following:

Please apply the following patch:

diff --git a/drivers/ethernet/eth_e1000.c b/drivers/ethernet/eth_e1000.c
index 996d4b12d8..d783ff72b7 100644
--- a/drivers/ethernet/eth_e1000.c
+++ b/drivers/ethernet/eth_e1000.c
@@ -130,6 +130,7 @@ out:

 static void e1000_isr(struct device *device)
 {
+printk("e1000_isr\n");
        struct e1000_dev *dev = device->driver_data;
        u32_t icr = ior32(dev, ICR); /* Cleared upon read */

Please show the exact dump from echo_server's "make run" followed net ping <IP_ADDRESS>, with either "e1000_isr" being printed, or with none of them.

1. Please show the exact dump from echo_server's "make run" followed `net ping <IP_ADDRESS>`, with either "e1000_isr" being printed, or with none of them.

I do not see any prints either
SeaBIOS (version rel-1.11.2-0-gf9626ccb91-prebuilt.qemu-project.org)

iPXE v1.0.0-591-g7aee315
iPXE (http://ipxe.org) 00:02.0 C000 PCI2.10 PnP PMM+007983C0+007583C0 C000

Booting from ROM..

uart:~$ ***** Booting Zephyr OS zephyr-v1.13.0-1632-g2f3315601b *****
uart:~$ net ping <IP_ADDRESS>
Sent a ping to <IP_ADDRESS>
Ping timeout
uart:~$

New version where I refactored the SLIP Kconfig file.

I do not see any prints either

Thanks! So after all, we're on the same line here with the behavior we observe.

New version where I refactored the SLIP Kconfig file.

Could you see if it is possible to reduce the code duplication?
Does
depends on (! QEMU_TARGET || NET_QEMU_SLIP)
work, for instance?
If not then perhaps @ulfalizer knows the cleanest way to solve this.

Does
depends on (! QEMU_TARGET || NET_QEMU_SLIP)
work, for instance?

Your suggestion works just fine, thanks for the hint.

Update:

SLIP Kconfig refactoring
NIC model selection made generic so it can be used with any qemu

New version:

fix bad English
simplify qemu command line option, -nic option can be used directly in our qemu version so do that


start of work to refactor submit

Submit now uses the flux operator python sdk (non released version) to create / submit / delete the minicluster, no need for external scripts except for starting minikube. This is likely an improvement and I am going to also test using the sdk for apply.
TODO:

[x] refactor the apply command to also use the sdk
[x] merge the fluxoperator changes https://github.com/flux-framework/flux-operator/pull/99
[x] update aws/google cloud to be tutorials
[x] create flux experiments init command and tutorial to show using it (it's too hard to create atm)
[ ] look into rich for a nicer UI experience for submit / waiting for jobs #29
[ ] ideas that are better than polling? https://github.com/flux-framework/flux-restful-api/issues/49

18th time is the charm! I'm going to do a full run through on google cloud after dinner - if that is good (minus being able to test fully on aws) we should be good to merge and release (and move forward from there).

Note that the operator needs to be deployed with the changes before flux-cloud can use them here.

The test_examples.py should probably be split up!


Check visual ML api

curl commands to

train classification
predict

using Microsoft Costum Vision API you need more than just one http request to train a classification:
1st request: Create a project (if not using an existing project)
2nd request: Create a tag/classification
3rd request: Send images with tag
4th request: Train project

https://southcentralus.dev.cognitive.microsoft.com/docs/services/Custom_Vision_Training_3.0/operations/5c771cdcbf6a2b18a0c3b80f

curl -X POST
'https://{region}.api.cognitive.microsoft.com/customvision/v3.0/training/projects/{project-id}/images?tagIds={tagIds}'
-H 'Content-Type: multipart/form-data'
-H 'Trainig-Key: {subcription-key}'
-H 'Training-key: {subcription-key}'
-H 'cache-control: no-cache'
-H 'content-type: multipart/form-data; boundary=----WebKitFormBoundary7MA4YWxkTrZu0gW'
-F '=@{path1}'
-F '=@{path2}'
... add up to 64 files

1st request: https://southcentralus.dev.cognitive.microsoft.com/docs/services/Custom_Vision_Training_3.0/operations/5c771cdcbf6a2b18a0c3b80f
2nd request: https://southcentralus.dev.cognitive.microsoft.com/docs/services/Custom_Vision_Training_3.0/operations/5c771cdcbf6a2b18a0c3b81f
3rd request: https://southcentralus.dev.cognitive.microsoft.com/docs/services/Custom_Vision_Training_3.0/operations/5c771cdcbf6a2b18a0c3b7ff (see example above)
4th request: https://southcentralus.dev.cognitive.microsoft.com/docs/services/Custom_Vision_Training_3.0/operations/5c771cdcbf6a2b18a0c3b813

It has been decided not to include this issue in the 0.2 release for the hackathon demo in favor to a stable demo and well-prepared presentation, which includes these ideas as a thoughtful outlook with detailed documentation of possible next steps.


Adjust attach() per TeXbook Appendix G 18a

Fixes issue #539.

18a. If the translation of the nucleus is a character box, possibly followed by a kern, set u and v equal to zero; otherwise set u ← h − q and v ← d + r

Some nuances shown below indicate the patch makes Typst more aligned with LaTeX:
LaTeX:
$$ b^2 \sqrt{b^2}, y_1^1 \lg_1^1, (by)_2^2 \neq \left(by\right)_2^2 $$

Typst:
$ b^2 sqrt(b^2), y_1^1 lg_1^1, "("b y")"_2^2 != (b y)_2^2 $

image

LaTeX

Typst with this patch

Typst without this patch

Very nice! I wouldn't have thought that the fix is so simple. :)


implement a raml parser

generaptr should be able to read a valid raml and extract the api schema

maybe we can use https://github.com/raml-org/raml-js-parser-2


Calculation of AMV

Thanks for providing the implementations of AMD and AMV.
I am confused by the code about AMV when taking the average. In the function calc_amd_amv of the file amd_amv_kde_metrics.py, the estimated covariance matrix is averaged over all time steps and all agents. Then, the maximum eigenvalue is computed on the averaged matrix. The calculation is inconsistent with Eq. (4) in the paper. Eq. (4) says the covariance matrix is estimated for each agent at each time step, from which a maximum eigenvalue is computed. The final AMV is obtained by averaging these eigen values. I belive the two quanties, i.e., maximum eigen value of an average matrix and the average of maximum eigen values, are generally not equal.
Could you explain the difference? It will be valuable for me when applying the code to new predictions on other datasets.

Hi Chen,
Thanks for highlighting this. The short answer for the moment, the code is
the ground truth for the AMV. It might be the case that it was miss
represented in the text.
I strongly think the code is the correct one as it aligns with the expected
visualization. When designing the AMV I wanted it to act as ADE/FDE in a
sense.
Abduallah Mohamed
abduallahmohamed.com
On Mon, 18 Dec 2023 at 08:24, Chen Siyuan @.***> wrote:

Thanks for providing the implementations of AMD and AMV.
I am confused by the code about AMV when taking the average. In the
function calc_amd_amv of the file amd_amv_kde_metrics.py, the estimated
covariance matrix is averaged over all time steps and all agents. Then, the
maximum eigenvalue is computed on the averaged matrix. The calculation is
inconsistent with Eq. (4) in the paper. Eq. (4) says the covariance matrix
is estimated for each agent at each time step, from which a maximum
eigenvalue is computed. The final AMV is obtained by averaging these eigen
values. I belive the two quanties, i.e., maximum eigen value of an
average matrix and the average of maximum eigen values, are generally
not equal.
Could you explain the difference? It will be valuable for me when applying
the code to new predictions on other datasets.
—
Reply to this email directly, view it on GitHub
https://github.com/abduallahmohamed/Social-Implicit/issues/14, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AFIVLG6EEOOT5ROV3DWSMS3YKBU5LAVCNFSM6AAAAABAZZIWDOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA2DOMBRG43TMMQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Limitations of the connector

Hi team,
After working with Bloomberg to get the SFTP site set up, it appears that the Bloomberg connector has a daily import limit which is preventing my organisation from being able to archive data into O365. Error messages are as follows:
Error Message: Received more items 1078372 than supported limit (100000), push is throttled and will be delayed.
We get this error every day and no data gets archived into O365. After raising 2 tickets with MS support I have been told that this limitation cannot be changed, which means that this connector is useless. Can you please expand this documentation to cover the limitations of the connector, any alternatives available and how the connector actually works. The daily exports from Bloomberg to the SFTP site generate several att, msg, ib and dscl files. From this documentation, customers don't have much information about which files are targeted for import and in what order they are performed.
Thanks.

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

ID: b000c65c-3d18-7bb2-9379-732f3655add6
Version Independent ID: f8069a1d-8652-9b1b-8d57-1d02949ebc0f
Content: Set up a connector to archive Instant Bloomberg data - Microsoft 365 Compliance
Content Source: microsoft-365/compliance/archive-instant-bloomberg-data.md
Service: o365-seccomp
GitHub Login: @markjjo
Microsoft Alias: markjjo

@musiq787 I've forwarded your issue to engineering team about additional documentation. I'll respond when/if there is more info about this.

@music727 As per what you cited about the cases you opened with MS Support, 100K items per day is the limit, which is a limit in the ingestion pipeline. At this time, there are no alternative workarounds. Here's a list of the type of Instant Bloomberg items/elements that may be ingested to O365. I assume an instance of one of these types would be considered "an item" and there can be one or more of these per chat/conversation. You can probably assume that all of these content types are ingested by the connector.  We'll look into adding this to the documentation.
Attachment: Represents each unique file uploaded to a given conversation or chat room
Conversation:  Represents a given conversation or chat session
History: Represents every time that a user requests to view the historical transcript for a given conversation session or chat room
Invite: Represents an instance when a user initiated a given conversation session as well as all users that were invited to participate
Message: Represents each unique entry within the given conversation session or chat room
ParticipantEntered: Represent a user that just entered the given conversation session or chat room
ParticipantLeft: Represents a user that just left the given conversation session or chat room
SystemMessage:  Represents programmatic content within the given conversation session or chat room

@musiq787 I believe the above reply was meant for you.
Kind regards,
Milda

Thanks guys. This means that companies should not make investments on O365 Compliance products. Features like Advanced eDiscovery & Communications Compliance are rendered useless if customers wish to unify their data from all sources to meet governance standards.. and all this because a connector like Bloomberg's has an import limit. Complete nonsense.

@musiq787 Would suggest you provide this feedback to engineering team at https://office365.uservoice.com/forums/289138-office-365-security-compliance


test(esl-media): e2e testing

Closes: #2709
@ala-n, do we need any other functionality tested or basic check for video/iframe tag is enough?

Nope, checking the existence of an iframe is not enough.
From what I could suggest based on YouTube provider work  we need:

Check that YouTube API is loaded, check that it is loaded once
We need to check the inner iframe is, actually, a YouTube and that it at least contains an ID of the required video
We need to check initial attributes as well (playsinline, autoplay, mute)
Ideally we need as much as possible including the ability to play etc. but unfortunately, YouTube no longer allows playing videos for unauthorized users (autotests including).


More advanced and thorough examples in docs

This PR implements #41 #40 -- adding examples for handling NPZ files and parallelism.

Probably a good idea to include a fully worked example in the docs, eh?  Eg data augmentation on iris via sklearn.

Tagging @justinsalamon

@bmcfee happy to pitch in once im back, if needed.

IIRC, this kind of slicing will (should?) cause memory leaks because the dictionary inherits the identifier of data, despite using the context manager. I believe this demonstrates the behavior.

I'm not sure that's a leak exactly - the reference is still active, so the GC won't (and shouldn't) free it.
However, once the context manager exits AND the last reference to the array is lost, then the GC should collect it.  If it's not, that's a bug in python.
It's worth mentioning that a buffered streamer does force the copy, so that could be an extra sanity check.
(In case it's not obvious, I really don't like doing explicit copies just to avoid apparent GC weirdness.)

I have also thought about making a sample object (I've done this in some of my own work), so that additionally the Sample object could use slots = ['X', 'Y'], and thereby save a lot of memory.

The downside of this is that you'd be stuck with only the two pre-determined variable names. I sometimes have streamers that generate many more variables (eg for multitask learning for different Y's, or cross-modal learning for different X's).
Would it be possible to do something that works like a named tuple (dynamically set, but fixed fields), that you could still use in the way you describe above?

I updated the npz/npy example again to discuss memory mapping issues, and while I was at it, fixed the build on RTD.  @ejhumphrey care to take another pass on this?

looks great 🎉


Support H3 as an additional dataset type

H3 is an embedded High speed, High volume, and High availability object store, backed by a high-performance key-value store (RocksDB, Redis, etc.). H3 also provides a FUSE implementation to allow object access using file semantics. The CSI H3 mount plugin (csi-h3 for short), allows you to use H3 FUSE for implementing persistent volumes in Kubernetes.
In practice, csi-h3 implements a fast and efficient filesystem on top of a key-value store. With csi-h3 deployed, and a Redis server running, you just need to specify the Redis endpoint and the bucket name you want to use, in order to get a mountpoint for your containers. H3 is embedded in csi-h3, so there are no other requirements to install.
H3 could be supported In DLF, with a dataset definition like the following:
apiVersion: com.ie.ibm.hpsys/v1alpha1
kind: Dataset
metadata:
  name: example-dataset
spec:
  local:
    type: "H3"
    storageUri: "redis://redis.default.svc:6379"
    bucket: "b1"

Note that H3 supports many additional key-value stores, but in the distributed environment of Kubernetes, you need a key-value store that can be accessed through a network protocol. For persistent storage, Ardb provides Redis connectivity over a range of key-value implementations, including RocksDB, LevelDB, and others. In that case, the storageUri used will still be in the form redis://..., but the actual service will be provided by Ardb.

Since #92 is merged I will close this issue. @chazapis and @malvag please feel free to re-open this issue in the future if you find it necessary


Minimal change to disable code coverage publishing for PRs.

Can one of the admins verify this patch?


core: fix "template" not allowed as prompt param

Description:  fix "template" not allowed as prompt param

Issue: #26058

Dependencies: none

[ ] Add tests and docs: If you're adding a new integration, please include

a test for the integration, preferably unit tests that do not rely on network access,
an example notebook showing its use. It lives in docs/docs/integrations directory.

[ ] Lint and test: Run make format, make lint and make test from the root of the package(s) you've modified. See contribution guidelines for more: https://python.langchain.com/docs/contributing/

Additional guidelines:

Make sure optional dependencies are imported within a function.
Please do not add dependencies to pyproject.toml files (even optional ones) unless they are required for unit tests.
Most PRs should not touch more than one package.
Changes should be backwards compatible.
If you are adding something to community, do not re-import it in langchain.

If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, ccurme, vbarda, hwchase17.

Could you add a unit test?
I'm open to merging this with additional tests (as long as existing lint/test passes) because I don't think these two functions are used externally. However, parameter changes like this tend to create more breaking changes than they fix because anyone passing template="my template" intentionally would break, and the behavior is easily worked around by using a name other than template


plugins/lsp: filter out null mappings

Adds a check to filter out null mappings in local function mkBinding.
It is only an issue with the LSP module because it doesn't use genMaps to generate the mappings and therefore doesn't filter them out automatically.
Fixes #281

If I understand correctly, passing null to the mkBinding function will still create a binding - but it will be an empty string, and not an actual mapping. We should probably write conditionally. Null should mean don't write, and not write empty string.

I can use filterAttrs on mappings to filter out null mappings.
The issue is that it will generate missing attribute errors when trying to add an action (using mkBinding) to the filtered out mapping option.


pkg/vcs: make backport configs more elaborate

See individual commits.

Added tests for backports.
@ramosian-glider PTAL