Migration from Node 6 to Node 10 | warning messages

Question, Bug, or Feature?
Type: Question
Enter Task Name: Universal Packages
Environment

Agent - Hosted

Issue Description
We are starting to see this warning message for some tasks:
Task         : Universal packages
Description  : Download or publish Universal Packages
Version      : 0.190.0
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks
##[warning]This task uses Node 6 execution handler, which will be deprecated soon. If you are the developer of the task - please consider the migration guideline to Node 10 handler - https://aka.ms/migrateTaskNode10. If you are the user - feel free to reach out to the owners of this task to proceed on migration.
May I ask when the migration will be done for such kind of tasks from Node6 to Node10? Getting tons of warning messages because of this.

Hi @attila-szabo1-epam the target date for Node 6->Node 10 migration is March 31st 2022 at the moment.

@anatolybolshakov Just curious, I've got 2 questions:
1 - What's the reason for delaying the upgrade? Node 6 is end-of-life (i believe since 2019).
2 - What's the reason for using really old end-of-life versions? Seems like it could be a security issue to use really old unmaintained versions? Why won't you upgrade to current LTS?

MS explains this here:
https://docs.microsoft.com/en-us/azure/devops/release-notes/2020/pipelines/sprint-177-update
Update from what was originally published: Due to an incompatibility with Red Hat Enterprise Linux 6 and Node 14, we've suspended work on Node 14 and will first focus on getting to Node 10.

Hi @attila-szabo1-epam the target date for Node 6->Node 10 migration is March 31st 2022 at the moment.

Doesn't this conflict with the move to remove Node 10 off all Azure DevOps Agents on: 15th November 2021: https://github.com/actions/virtual-environments/issues/4356 ?

@attila-szabo1-epam Thanks for the link. That blog post is over a year old now. IMO i would see that issue as critical as it's not acceptable to use unmaintained non-lts versions.

@attila-szabo1-epam @jackson15j @badsyntax unfortunately it takes some to migrate whole infrastructure to Node 6 - since there is a lot of in-the-box tasks depending on Node 6. There is also a lot of custom tasks depending on Node 6, and it could take some time for maintainers to complete migration.
Node version used for tasks execution is shipped separately with agent - so it does not depend on version installed on a hosted image.

@anatolybolshakov i understand, but it seems like this wasn't planned correctly. (but i'm just a casual observer and not aware of all the details.)

I'm also getting this warning...
##[warning]This task uses Node 6 execution handler, which will be deprecated soon. If you are the developer of the task - please consider the migration guideline to Node 10 handler - https://aka.ms/migrateTaskNode10. If you are the user - feel free to reach out to the owners of this task to proceed on migration.
What do i do to fix this?

Ignore it until they upgrade the task , then the warning msg will be gone.

My NuGet task only consists of this in my YAML CI build...
steps:

task: NuGetCommand@2
inputs:
command: 'restore'
feedsToUse: select
vstsFeed: 'b161411d-e976-445e-a736-8ef0a0397756/be77ebae-d25b-4745-b142-3a1259d4ea93'
includeNuGetOrg: true
restoreSolution: '**/*.sln'

This task has old dependency as well, part of the upgrade is azure lib:
https://github.com/microsoft/azure-pipelines-tasks/blob/master/Tasks/NuGetCommandV2/package.json
"dependencies": {
"azure-pipelines-task-lib": "2.8.0",
If you read this : https://aka.ms/migrateTaskNode10

Upgrade azure-pipelines-task-lib to ^3.1.7 in package.json dependencies.

This does mean all our pipelines are being spammed with warnings we can't do anything about, making it hard to see genuine warnings - it would be great to get these tasks updated sooner rather than later.

I had this warning for NuGetToolInstaller@0, which I've updated to NuGetToolInstaller@1, but I also have this warning for NuGetCommand@2, which doesn't appear to have a newer version.
I use the .NET CLI for all my modern .NET pipelines, but I still have .NET 4.x build pipelines that are in active use.
Hopefully NuGetCommand@2 gets upgraded soon.

Getting this warning on the CopyFiles activity.
==============================================================================
Task         : Copy files
Description  : Copy files from a source folder to a target folder using patterns matching file paths (not folder paths)
Version      : 2.190.1
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/copy-files
==============================================================================
##[warning]This task uses Node 6 execution handler, which will be deprecated soon. If you are the developer of the task - please consider the migration guideline to Node 10 handler - https://aka.ms/migrateTaskNode10. If you are the user - feel free to reach out to the owners of this task to proceed on migration.

There's got to be something that can be done -- or perhaps Azure DevOps can stop spamming the warnings. I realize the deprecation is a big deal but with so many built in tasks using the old handler, all my pipelines are just riddled with warnings. I understand what it's about, but others viewing the results think there's legitimately something wrong with our stuff. Plus the spam just makes it difficult to see anything. Maybe ADO can only warn about non-built in tasks and/or ones that aren't using the latest version. Would sure cut down a ton of mostly meaningless spam.

@seangwright I seem to be getting this warning with NuGetToolInstaller@1 as well as NuGetCommand@2

Agree, it is pretty annoying:

Is there a way to filter out warnings that start with "This task uses Node 6..."?

Because of this change, we suddenly have 80+ pipelines with some of them over 20 of these warnings. It's affecting our quality process to fix real warnings. This is just noise.
Can this be reported on a higher level (aggregated) instead with the causing task and it's vendor?

@seangwright I seem to be getting this warning with NuGetToolInstaller@1 as well as NuGetCommand@2

I am also getting this warning for VSTest@2.
It is very confusing to get this message from the use of Microsoft delivered tasks that have no apparent connection to Node in a project with no connection to Node.

@CZEMacLeod @jshall Yah, I am too - at first I thought the remaining warnings in my pipelines were from other tasks, but there's so much noise now that I missed VSTest@2 is still presenting warnings 🤦♂🤦♂🤦♂.
Thankfully our .NET CLI tasks aren't producing warnings, but we can't just switch to that from the VS tasks for classic ASP.NET applications that we produce builds of on a daily basis 😑.

@seangwright I seem to be getting this warning with NuGetToolInstaller@1 as well as NuGetCommand@2

I am also getting this warning for VSTest@2.
It is very confusing to get this message from the use of Microsoft delivered tasks that have no apparent connection to Node in a project with no connection to Node.

Yes. It feels very strange that Microsoft tasks wasn't fixed before the warning was going to go live, when ppl at Microsoft absolutely should know this change is coming.

Hi @attila-szabo1-epam the target date for Node 6->Node 10 migration is March 31st 2022 at the moment.

Why cant you just state this in the warning message instead of the generic "deprecated soon", we started panicking and searching for alternate TASKS just to have  a backup plan when/if our pipelines start breaking...
Now we at least know we have 4 months to tackle this.
Also as someone else said, now all our pipelines are cluttered with these warnings, we need a way to disable them!

Can someone tell me how to fix this?
I am using React app in azure-pipelines and getting these warnings on copyfiles and npmAuthenticate and I could not find from where this issue is coming from.
Should I change some things in the .yml file? Or do I need to change something in package.json🙄?

Can someone tell me how to fix this?
I am using React app in azure-pipelines and getting these warnings on copyfiles and npmAuthenticate and I could not find from where this issue is coming from. Should I change some things in the .yml file? Or do I need to change something in package.json🙄?
Or if this issue is something else which will resolve automatically after march 2022 then please tell.

You need to upgrade the tasks used in your (yaml) pipeline to a newer version. However, for almost all tasks (as of which most we use are Microsoft standard tasks) there isn't a newer version available that fixes the issue at this point.

Just ran into this warning message as well and was wondering what I was supposed to do. Looks like nothing, we need to wait for MS to upgrade the tasks.

For those looking for a way to remove the warnings, there is a section about that on the migrateNode10 page:
https://github.com/microsoft/azure-pipelines-tasks/blob/master/docs/migrateNode10.md#how-to-disable-warnings-for-node-6-deprecation
To avoid noise in pipeline logs - you can disable Node 6 deprecation warnings by setting up DISABLE_NODE6_DEPRECATION_WARNING agent knob in one of 2 ways:

Set up DISABLE_NODE6_DEPRECATION_WARNING pipeline variable as true
For self-hosted agents - set up environment variable DISABLE_NODE6_DEPRECATION_WARNING as true

"Waiting for response" by whom exactly?

For those looking for a way to remove the warnings, there is a section about that on the migrateNode10 page: https://github.com/microsoft/azure-pipelines-tasks/blob/master/docs/migrateNode10.md#how-to-disable-warnings-for-node-6-deprecation
To avoid noise in pipeline logs - you can disable Node 6 deprecation warnings by setting up DISABLE_NODE6_DEPRECATION_WARNING agent knob in one of 2 ways:

Set up DISABLE_NODE6_DEPRECATION_WARNING pipeline variable as true
For self-hosted agents - set up environment variable DISABLE_NODE6_DEPRECATION_WARNING as true

Maybe I'm doing the wrong thing but I added the following to my azure-pipelines.yml:
variables:
  DISABLE_NODE6_DEPRECATION_WARNING: 'true'

and I'm still getting the warnings...
Does this not work or am I supposed to put this flag somewhere else?
Thanks

@ML-Emyode @ByteDev I added the environment variable DISABLE_NODE6_DEPRECATION_WARNING to my build server with the value of true and still get the warnings.
(I use a docker version of the vs buildtools and agent running on a windows container)
It shows up in the Agent Capabilities screen in Azure DevOps so I would assume that it is detected and working as it should.

Added like the 2nd way to test in my pipeline too , to see it works or not.
In yaml I would add it like this:
variables:

name: DISABLE_NODE6_DEPRECATION_WARNING
value: 'true'

or to here:

@attila-szabo1-epam It it works?

Nope, warnings still appeared, seems changes does not merged yet to ignore these warnings.

Hi everyone, we've merged a fix with an agent knob in PR - to be able to disable warnings - this will be available with the next agent release.

Hi everyone, we've merged a fix with an agent knob in PR - to be able to disable warnings - this will be available with the next agent release.

What is the normal time frame for this?

@anatolybolshakov  - A knob to disable the warnings is not the right solution here.  Its an unreasonable burden to ask us to add it to all of our pipelines (my current org has well over 1aK pipelines) just to cut down on a thing we should not be seeing anyway.
We are all complaining about them showing up for MSFT created tasks. Eventually we expect you to do the needful and update your tasks, but since you are well aware that they need to be updated, and there is nothing that we the users can do but complain about this warning and deal with its noise, it would make more sense for you to not warn us by default for every MSFT created task.

Yes, the core issue is that the currently documented major version and the recommended task for many workloads (such as NuGetCommand@2) is using a deprecated Node runtime.
If customers suppress the warning, what's going to happen is that:

They will not notice when the deprecation is complete
Their pipelines will spontaneously start failing for tasks Microsoft documented and assured that they could use
They will likely move to another CI technology, because if they have to rewrite their pipelines to not use deprecated commands, they might as well choose one that is better-documented and where changes to it are better-communicated.

@attila-szabo1-epam I'm really not sure that closing this issue is the right thing here.
Both @StingyJack and @DHowett 's comments are very valid.
The issue really should be open until all the Microsoft supplied tasks no longer generate a warning.
The use of the suppression setting is a burden to consumers, and will result in them (us) not being aware of third-party or internally built tasks which might also have the issue and not knowing to do something about it.

This issue was raised with a question which was answered.

Can this issue be reopened or a follow on issue linked?  The last comment was unprofessional, hateful and trolling, and agree with @CZEMacLeod and others here.
Comments on the variable fix
The proposed fix is a debugging workaround for the underlying issue that every pipeline in the world using Microsoft-authored tasks, eg. "CopyFiles", "npmAuthenticate" or "Nugetcommand" is getting this warning with no means to fix the underlying issue.
Everyone who wants to ignore it to get a green status pipeline will have to implement the variable workaround, then watch for new versions of extensions to appear, then fix the versions, then remove the variable workaround.  Running a pipeline to test the workaround might not be an option in some cases.  Everyone monitoring their failing/warning tasks is getting this error and alerts around it.
The warning message was great in terms of visibility to surface the underlying fact that NodeJS extensions are deprecated.  That message is now out there.  Changes required to implement this change across pipelines and documentation are so much greater than the value of this message running in every single pipeline run on every single affected task.
This variable fix is a temporary feature flag which should be removed when the upgrade is complete.  So this work would need to be done twice, for every pipeline?
Proposed interim patch
The warning spamming the logs should be turned off immediately with minimal or no user intervention, as we can see from above sentiment.    At least for MS-hosted agent pipelines and extensions.
If the warning can't be turned off, give teams an automated way of opting out.
Provide interim workarounds for each Microsoft-managed extension if there are concerns about older versions of NodeJS in extensions.
Microsoft Docs and sample code need to be updated with the upgraded versions when they are available.
Let users migrate to upgraded versions.
Proposed mitigation ideas

One option for a fix should be that the Azure Devops interface exposes some message and provides ability to quiet the warning across pipelines for the complete project or organization for a certain timeframe.  There is no need to show a warning on each pipeline run for something that cannot be fixed by the end-user and no value to ask the end user to follow up with pipeline extension authors.  The authors of extensions should receive a warning in their respective git repos, perhaps with some regular report about how many consumers are affected.  Devops Administrators and/or Build Administrators should receive the warning and a list of affected pipelines and tasks in the portal.

How about actions to upgrade these tasks in the background?  The end-user shouldn't have to intervene for a Microsoft-managed Devops extension task upgrade.  If there's a problem with the upgrade, there should be some option to pin a different version.  I would expect a warning if there's a problem.  Going forward with security updates should be automatic?

Another option to fix could be a dependabot-style PR option to upgrade the task when it's fixed.  But again that involves a lot of change tickets and noise.  Why not do this security upgrade with minimal intervention?

Call to Action
A warning pipeline is not a green pipeline, and teams should have control of their pipelines to make them green.  A Security Advisor & Alerting tool might be a better method to address security issues like this.  Different teams could be working on the pipelines and security initiatives, making the ability to implement these debugging variables problematic.
Communicate security messages with urgency, clarity, and with possibilities for actionable mitigation plans.

See https://github.com/microsoft/azure-pipelines-tasks/issues/15508 for an open task with WIP info on CopyFiles@2 and PipAuthenticate, and AppCenterDistribute to continue this discussion, as the question above was answered.
It looks pretty straightforward to comment out the warning in the PR which started this, or to automatically enable the debug variable by default.  How about doing that instead of holiday log spam, and then letting us know when it's fixed with a pleasant emoji warning in our pipelines to greet us in the new year?  It's ok to admit when you are wrong for the right reasons... security vs. convenience and all that.
For those that want to opt into canary warnings about internal Microsoft tasks, that might be a good use of the debug feature flag variable.

If this is being viewed as a question, maybe we need a new issue raised to track the issue (i.e. pipeline warnings appearing that we don't have the power to resolve).
Would you like me to open one? I think I'd err on the side of re-opening this one personally, since there's plenty of useful discussion here.

Hi everyone, just as a quick update - due to issues with increased amount of warnings we are working on disabling of Node 6 warning message for in-the-box tasks and leave warnings only for a custom tasks. We are planning to roll out relevant agent update in the next two days - will keep you posted in the issue.
For Node 6 - we are not going to deprecate previous execution handler until all the relevant supported in-the-box tasks will be migrated to the new Node execution handler, please don't worry about it. The main goal of this warning message is to notify custom extensions owners about upcoming agent update - I agreed that this is a fair point not to display them for the pipeline owners.

Hi,
Just making sure, do you know how users who are exclusively on legacy Node6 agents will be affected if we upgrade our extension to Node10 exclusively and the user updates the extension from the marketplace? Our team's extension has a few users who fit into this category; I've got a few questions:

What would happen to users in this scenario: would the jobs break entirely?

If it breaks entirely, would the only path forward for them be to uninstall the VSIX and manually install a new VSIX with autoupdates disabled?

Would Microsoft be able to prevent these customers from updating in the first place?

Stalebot, cut it out. This is not a way to run an opensource community.

@anatolybolshakov Have the internal tasks been migrated to Node10 yet and is there a date for disabling the old handlers?

asdfghjkl;

Not stale = see also #19707


Add an option "--ignore-parameters" to turn off any attempt to parse command-line files as parameter files

See #300
This PR depends on #372 and should be merged after that one.

Coverage increased (+0.01%) to 71.543% when pulling 146e20237897ea4b69f6bfa8e10b2c98fec9aff2 on apdavison:issue300 into d5cc713574dc92c03fff1ddceca776cb4320fa5a on open-research:master.


Make hover and focus not respond when buttons and fields are disabled.

Description
Disabled fields and buttons were responding to hover and focus changes, and they shouldn't.
Tests
I added the following tests:

Hover and focus tests for both outlined and filled text fields for when they are enabled and disabled.
Hover and focus tests for ink well.

Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[X] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[X] I signed the CLA.
[X] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[X] I updated/added relevant documentation (doc comments with ///).
[X] All existing and new tests are passing.
[X] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[X] I am willing to follow-up on review comments in a timely manner.
[X] I am willing to check all the boxes.

Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?

[X] No, this is not a breaking change.

@fkorotkov What's up with all of our Windows bots?  This isn't the only PR that's just DOA.  They go red immediately upon submitting a change.

@gspencergoog  Sorry, just noticed the GitHub notification. It should be working now. Sorry for the inconvenience! Don't hesitate to ping<EMAIL_ADDRESS>next time for quicker response.


strictNullChecks does not work in ===

Bug Report
🔎 Search Terms
strictNullChecks
strictNullChecks equals
strictNullChecks ===
🕗 Version & Regression Information
I had not encountered this before until I found a bug in our framework, which I thought would be caught by TS.
Playground shows this being an issue since 3.3.3333 (as far back as it goes) and also on nightly (4.5.0-dev202110929).
Please keep and fill in the line that best applies:

This is the behavior in every version I tried, and I reviewed the FAQ for entries about strictNullChecks

⏯ Playground Link
https://www.typescriptlang.org/play?#code/PTC0oZwFwJwSwMZQHIFcA26DCALApggNYQCwAUOnlAAQCG1AXNQHaoC2ARnjNQLzUAmcuRDUAKgGUBAZgECANNSg44EahBwB7AO5ro8JGky4CxOjDzU8zWh0oATAHTl6-VpmFlRkmQDYA7IrwAOY4UABmGOgAnupwzAiWrJzcdMz21ByampS0zNQ4tABuSZrUmiUw6LQADi58vPywqHie3lLSAUFwoRFRsRCoCUnsXDx5GfrxwQXFpeWV1XVkro3UAORQeNDr1G3A1ADqOLH2mttKKmrMmjTKMDriHQEA-NRoKePpLFGzJSxlCrcJbUbT4fJTQxRExENSqKw2Ox4Jz1RpuKL7cRXahsHphTKWIq0dBwDJwcJ0UG0NRDeJwKBwYlwABeyMUHFQd3w1DOCD0tFiQ3seHC8WRaQy7nQ5ksCE0zAgpO44ogeBqtBgtC2SmiNW2zhWDX4QpFYvsQA
💻 Code
//--strictNullChecks
let a : number = 2

// Why does this not throw TS2367? Number and null have no overlap when strictNullChecks is enabled.
a === null

// This might be valid if a was uninitialized, but the docs say undefined and null are considered separate types.
a === undefined

🙁 Actual behavior
As per the documentation "When strictNullChecks is true, null and undefined have their own distinct types and you’ll get a type error if you try to use them where a concrete value is expected."
This would mean that a number being compared to null, will throw TS2367 "This condition will always return 'false' since the types 'number' and 'X' have no overlap.". However, both null and undefined in the code above do not raise TS2637.
🙂 Expected behavior
If strictNullChecks is enabled, number === null should raise TS2637 since there is no overlap between the types.

Duplicate of #11920. Used search terms: compare null in:title

Right, sorry missed that one. I'll close this. Thanks for the heads up!


Add script to create the acl files for squid

Created a new script based on create-unbound.sh which creates the acl files for squid

Appears to work.


FWL fails to restart properly after issuing command datareftool/reload_plugins

After issuing the command datareftool/reload_plugins, FlyWithLua's plugin restarts properly, but the Lua interpreter stops with this error reported only on screen (no trace on Log.txt file):
[string "FLYWITHLUA_DEBUG()"]:1 attempt to call global "FLYWITHLUA_DEBUG" (a nil value)
Manually forcing FWL to reload all scripts, solves the problem.
I've tested without any script installed, to be sure not to have any possible interference.
Best.

The problem is with XPLMSpeakString("All Lua Script files loaded."); at line 7940 doesn't have enough time to finish before reloading plugins.
So your option are:

developer_mode = 1 (doesn't work always, as sometimes the reading of preferings is slow and developer_mode gets 0)
delete lines 7938-7941 (keep in mind that if other plugin use XPLMSpeakString() also you will have crash, so wait to finish before pressing reload plugins)
If you prefer to listen the message simply use a waiting command to finish message, before return 0;


Add Logout button

So user can logout and token is deleted from local storage.
Insure that logged in user is informed about being logged in by showing his info (pic and user name).

When the token expiration date is old or user is not logged in -> the login button is visible.
When the token is not expired -> user info is shown and logout button is visible.
After clicking Logout button all local storage is cleared.


GetContentAsync no longer working after update

I have a simple method
public virtual string GetHtml(Page page)
{
    return page.GetContentAsync().Result;
}

Before updating to 1.8 from 1.6 this method worked fine for me. However, it seems to hang whenever it is called now. The reason it is inside a method like this is that I have other overrides that fetch the html differently.
If I simply call the function it just hangs. However, If i call the same method using an await before doing it using .Result it works. The code below will work only if string temp = is used first.
string tmp = await Page.GetContentAsync();
var html = handler.GetHtml(page);

I'll take a look into it.

@danhastings I'm investing and investing time on this guy and I still don't find the why.
I would really appreciate your help here.
This is the diff between 1.8 and 1.6. https://github.com/kblok/puppeteer-sharp/compare/v1.6...v1.8#diff-888ccb9bc7a7d7e9efb006217c35ee93
I really would like to fix it. But on the other side, we can use awaits in most places now and the .Result deathlock is a common topic in many places (I'm talking about Stack Overflow of course).
@Meir017 if you can take a look at that diff and see if you see something, please let me know.

@kblok I downgraded to v1.7 and it is working again. This narrows it down a bit to something specific to v1.8. Ill have a look over the diff and see if i can find anything

This PR is guilty https://github.com/kblok/puppeteer-sharp/pull/647

I dug a lot into it and now joy. It is because that commit but I can't find out what is causing. On v1.7 this code works
await page.GoToAsync("about:blank", new NavigationOptions { });
Console.Write(GetHtml(page));

Whereas if I remove await page.GoToAsync("about:blank", new NavigationOptions { });, GetHtmlhangs.
I would gladly review any fix on this. But I think I won't invest more time in this until we catch Puppeteer.

Closed due to inactivity. Feel free to reopen it if needed.


Load data with at prefix

Addresses #11
Builds on top PR of #9

Coverage remained the same at ?% when pulling 20dec3008dfd2162a9307560fb2c9c3407b86251 on tomdottom:load-data-with-at-prefix into b79b267a75210b8845745fd88498733aa613c745 on andreif:master.

Implementation of #12 invalidates most of this PR. Closing in favour of that implementation.


[BUG] DWCjProgressBar setValue() method has no huge effect.

when I use the setMaximum() of 90 and use the code below, my progressBar grows "almost" as fast as when my setMaximum() is 10.
There difference between having a max of 90 or 10 should be actualy noticeable. However, there is only a very small difference, which I believe, it doesnt work as it suppose to be.
public class DWCjControlProgressBarSample extends App {
 private AppPanel appPanel;
 private ProgressBar firstProgressBar;
 private Button modifyButton;

 @Override
 public void run() throws DwcAppInitializeException {
 appPanel = new AppPanel();

 firstProgressBar = new ProgressBar();
 appPanel.add(firstProgressBar);

 firstProgressBar.setMaximum(90);

modifyButton.onClick(this::onClick);
}

private void onClick(ButtonClickEvent buttonClickEvent){
     value();
}

private void value(){
       boolean flag = false;
       while (!flag){
           firstProgressBar.setValue(firstProgressBar.getValue() + 1);
           if(Objects.equals(firstProgressBar.getValue(), firstProgressBar.getMaximum())){
               flag = true;
           }
      }
}

To me, I believe it's a noticeable enough effect, and may be useful to those who are used to using this method in existing DWC applications

when I use the setMaximum() of 90 and use the code below, my progressBar grows "almost" as fast as when my setMaximum() is 10.

I cannot reproduce such behavior Oskan. Make sure  you are using the latest version of BBj


Measurement value getting removed for 'complex' types

When a sample measurement is set and the value is and 'object', that is any {} type json,  the value is cleared, that is set to {}. For example, a matrix measurement that looks like this (on the input side):
data = {"name":"Lattice",
"attribute":"lattice",
"otype":"matrix",
"unit":"",
"units": [],
"value": {
"dimensions": [3,3],
"otype": "float",
"value": value
},
"is_best_measure":True}
has the value (in the database) set to {}
The problem is with the statement:
schema.prepare(schema.measurement, measurement);
at or about line 195,
materialscommons.org/backend/servers/mcapi/resources/projects/experiments/samples.js
The work around was to preserve the value (of measurement.value) across the call. See comments in code.
Fixing this will require some research!

This is the workaround commit for this issue: https://github.com/materials-commons/materialscommons.org/commit/89622bf9849ba4fe5aa4098867c750f39883c8ce


fix: Reduce warnings in load mode

Description

Modifies number of scopes check to always compare number of scopes and number of recordings loaded from file.
Motivation and Context

Unnecessary warnings.
Types of changes

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

Checklist:

[ ] I have updated the documentation accordingly. If you are changing code related to user secrets you need to really make sure that security documentation is correct.
[x] I have read the CONTRIBUTION_GUIDE document.
[x] I haven't repeated the code. (DRY)
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

I do not understand it. Can you show me recording which will trigger the warning please?

I went through define function in more detail and this won't ever trigger a warning. Every valid recording passed in define gets intercepted, so length of those arrays should always match.
Sorry about this confusion, I should have checked it sooner. I propose to modify this check to warn only if length does not match. It might not be necessary, but we process the recordings, so it might be handy when someone accidentally removes recording in beforeRecordingLoad hook or if define would change its implementation. What do you think?

Thats fine, I just wasn't able to understand what I am not seeing. Si I guess this PR can be closed and we will need to find other way.

I can remove the warning for now, it's not useful anyway.

And would it be possible to print it only off in record mode?

Damn, I was in different context. I would remove it, because there are cases when recording should be empty.


SOL activity not updating in “My SOL” view, but is showing “My Activity” view

Describe the bug
When testing locally, after sending or receiving a SOL txn, the "My Activity" view shows the txn, but the activity section in the "My SOL" view doesn't
To Reproduce
Steps to reproduce the behavior:
When locally testing on Android / iOS

Send SOL
Txn doesn't display in the activity section in "My SOL" view

Expected behavior
activity section in "My SOL" view should udpate
Screenshots

Smartphone (please complete the following information):

OS: Android / iOS
App Version: 2.0.6

Hi @deasydoesit  visit the official Support page to initiate a chat with the support team on the live chat to report your errors for review and for further assistance via Live Support

This should be fixed. @deasydoesit Good to close?

Yessir!


Overflow mechanism for more than maxCount completions

Currently maxCount is a hard limit to the number of shown elements. Additional elements are discarded without any indication to the user.
It would be nice if there was an indication that additional elements are available (maybe show a ... ellipsis?) and even nicer if the user could somehow use those additional elements (maybe by scrolling through the list?) even if still only a limited number of elements is visible at once.

You can do that by overriding max-height of .textcomplete-dropdown and set huge number to maxCount.

Ah, ok that works great, thanks a lot! I guess this issue can be closed then.
(We use jquery-textcomplete in this plugin for the Trac issue tracker and wiki system. It works great! Many thanks for writing it.
We'll use this CSS  as suggested.)


feat: Dynamic template system with editable system prompt fields.

Please describe the purpose of this pull request.
This implements a dynamic template field system for the system message editable at runtime through CLI.  This also implements a customizable core memory without hard coded persona and human block. For use cases such as a customer service bot, dungeon master in a DnD game, where no persona and human is necessary or too unspecific and there is need for specific fields etc.
This all aims to make MemGPT more configurable for use cases outside that of a chatbot with a persona.
How to test
Load a system prompt with template fields and edit one through the cli. Create a customizable core memory preset.
More detail to the template field system for system message:
It adds a simple but effective template system for building the system message of memgpt.
It has predefined template fields that can be used to add parts of the default memgpt_chat system message.
The following shows the memgpt_chat system message in template form:

Each field adds a part of the system message of memgpt_chat, the template system will generate the memgpt system message automatically from it.
The template system get triggered when the system message string in the memgpt preset, ends with '_templated'. Like for example the following memgpt preset:

It then will load the built in template fields, like 'memgpt_introduction' or 'memgpt_realism_authenticity' and tries to load a file with the same name and path as the system message file, but having a file ending of '.yaml' consisting of field names with their respective content. The following is a complete example for instructing memgpt to talk like an old pirate:
memgpt_chat_pirate_templated.txt (in the user folder system_prompts)
{memgpt_introduction}

{memgpt_realism_authenticity}

{memgpt_control_flow}

{memgpt_basic_functions}

{memgpt_memory_editing}

{memgpt_recall_memory}

{memgpt_core_memory}

{memgpt_archival_memory}

{memgpt_introduction_end}

{pirate_instruction}

memgpt_chat_pirate_templated.yaml (in the user folder system_prompts)
pirate_instruction: 'Always reponsond like an old pirate!!!'

memgpt_pirate_preset.yaml (in the user folder presets)
system_prompt: "memgpt_chat_pirate_templated"
functions:
  - "send_message"
  - "pause_heartbeats"
  - "core_memory_append"
  - "core_memory_replace"
  - "conversation_search"
  - "conversation_search_date"
  - "archival_memory_insert"
  - "archival_memory_search"

Here is the resulting chat response of memgpt using the example preset:

The template fields are dynamic and editable through the CLI by using the "/edit_template_field" which prompts the user to input the template field name and its value. This allows to change parts of the system prompt dynamically during the runtime of the application.
Details on the configurable Core Memory
This makes it possible to initiate the core memory with other or more specific sections and information then the default persona and human section. To activate it the user has to specify his preset with a core_memory_type field set to "custom" and provide a custom_memory_file, which is an additional yaml containing sections and values of the initial core memory.
A user agent preset example:
system_prompt: "memgpt_chat"
core_memory_type: "custom"
core_memory_file: "initial_core_memory"
functions:
  - "send_message"
  - "pause_heartbeats"
  - "core_memory_append"
  - "core_memory_replace"
  - "conversation_search"
  - "conversation_search_date"
  - "archival_memory_insert"
  - "archival_memory_search"

The file inital_core_memory.yaml, next to the preset:
persona: 'The following is a blank slate starter persona, I need to expand this to develop my own personality.

My name is MemGPT.
I am kind, thoughtful, and inquisitive.'

human: 'First name: Chad'

This is just an example to create a default memgpt core memory with initial core memory. But you can put any fields and values you want as sections into the core memory yaml file.
Have you tested this PR?
Yes
Is your PR over 500 lines of code?
No

@cpacker @sarahwooders Maybe you both could give me a short feedback the next days on what you think about the system.

@cpacker I have addressed all your comments by templating everything that make sense. I added:
system_message_layout_template
core_memory_section_template
To the agent preset. That will load the corresponding templates from the preset folder. If no template is specified it will fallback on the default way.

This is the default system_message_layout_template
{system}

### Memory [last modified: {memory_edit_timestamp}]
{len_recall_memory} previous messages between you and the user are stored in recall memory (use functions to access them)
{len_archival_memory} total memories you created are stored in archival memory (use functions to access them)

Core memory shown below (limited in size, additional information stored in archival / recall memory):
{core_memory_content}

This is the default core_memory_section_template:
<{memory_key} characters={memory_value_length}/{memory_value_limit}>
{memory_value}
</{memory_key}>

Hey @Maximilian-Winter - this is an awesome PR and we're really sorry about not merging it. We are currently working on generalizing the memory specification (and also will eventually generalize the templating). Given how much the codebase has changed since this PR, I think we'll re-implement some of this stuff in multiple individual PRs (the first of which is here #1479) and make you a co-author on those since I am looking at your implementation to inform the designs.
Again wanted to just let you know that although we didn't manage to merge this, @cpacker and I have looked over this PR very carefully and intent to implement parts of this -- so really appreciate your work.

Closing since this is stale and we've incorporated into #1479 and #1584


Update golangci-lint version to v1.45.2

The additional - uses: actions/setup-go@v2 is needed based on instructions from https://github.com/golangci/golangci-lint-action#compatibility
Signed-off-by: Mike Ng<EMAIL_ADDRESS>

Not sure why the GitHub actions are not triggering. Reopening the PR to see if it toggles.

Maybe it's a GitHub UI bug. When I reopen the issue I can briefly see the GitHub actions running in the back.


Update typings for obs-websocket 4.9.x

Description:
The typings seems to be outdated on npm.
I was able to compile the typings locally and use new events like VirtualCamStopped etc but with the package downloaded from npm, the new events and requests from the v4.9.x are missing.
Versions Used (if applicable):

obs-websocket-js version: 4.0.2
obs-websocket plugin version: 4.9.1
obs-studio version:
node version:

I mentioned this in Discord, with my edited script that was merged recently it should need regenerating and then a new NPM version publishing, but I don't think I have access to do that myself.

Given that there is going to be quite a number of updates necessary to support >5.0.0, I think it would be wise to tag / update npm now. I was able to build locally without issue and use the new typings so unless there are any other issues I think this would be very helpful to get published soon.


Table reference

This PR addresses issue #320 which is in relation to chaise issue #932. There are 3 changes included here:

Table has a get reference function to get a reference to that specific table. Table has a private function for getting the uri representing it used for generating the reference.
Reference exposes it's table object via a public get table function.
When contextualizing a reference, the filter is no longer removed when contextualizing to the create case.

This PR must be merged before this PR in chaise is merged.

@jrchudy Please pull the master so the checks pass, then we can merge.


Can you add code to train custom models?

Hello, I would like to try to train my own model, but I can not find the code for learning it in the repository, as I see the usual convolutional model is used here, could you publish the files for its learning, I want to try to train it on other devices with a small number of examples, I would not want to spend time repeating the structure of this. Thanks!

The training code is proprietary.
If you need to train your own models you have to look for other solutions like Simple Audio Recognition or Mycroft Precise.
I will update the README to make this more clear.


Create updated frontend

@gauravsingh1281 here it is brother? Anything else?

@gauravsingh1281 Have you seen it brother?

Hey, @Aazib-at-hub no changes are visible on the deployment preview please check.

@gauravsingh1281 i think let's leave it it looks good.


Clocks/Delay papercut.

You have the system clock speed in the results of hal::clocks::init_clocks_and_plls. But you can't just pass it to cortex_m::delay::Delay. And it feels like you should be able to.

What's wrong with the current situation?
      let clocks = init_clocks_and_plls( [...] ).ok().unwrap();
      let sys_hz: u32 = clocks.system_clock.freq().integer();
      let mut delay = cortex_m::delay::Delay::new(core.SYST, sys_hz);

Too complicated?

Yes. At worst it should be:
      let clocks = init_clocks_and_plls( [...] ).ok().unwrap();
      let mut delay = cortex_m::delay::Delay::new(core.SYST, clocks.system_clock.into());

Don't forget your example requires I think two traits to be in scope.

Looking at other HALs, one option is to just not use cortex_m::delay::Delay but implement our own Delay, like here:

https://github.com/stm32-rs/stm32f3xx-hal/blob/master/src/delay.rs
https://github.com/atsamd-rs/atsamd/blob/master/hal/src/delay.rs

Interestingly, I found those by searching for Delay::new in the https://github.com/rust-embedded organization, the very one where the cortex_m crate also lives. Perhaps cortex_m::delay::Delay is just too low-level?
Also noteworthy: https://github.com/rust-embedded/embedded-hal/issues/103

@jonathanpallant: Now that Timer implements the delay traits, it shouldn't be necessary to use cortex_m::delay::Delay. Can we close this ticket, or do you think it's still worth improving the usability of cortex_m::delay::Delay?
The usage with Timer is now:
let clocks = init_clocks_and_plls( [...] ).ok().unwrap();
let mut timer = rp2040_hal::Timer::new(pac.TIMER, &mut pac.RESETS, &clocks);
timer.delay_ms(500);

As mentioned above, I think this is solved with the current API. Timer should be the common delay implementation, so the usability of cortex_m::delay::Delay isn't as important as before.
@thejpster, feel free to reopen if you disagree.


Apple Match-O Linker Error

Expected Behaviour
Run app on iOS simulator
Actual Behaviour
Xcode compilation error
Steps to Reproduce
Add the plugin to the project and try to run on a simulator from Xcode
Platform and Version
iOS 10.2

Cordova CLI version and cordova platform version
cordova version: 6.4.0
cordova ios version: 4.3.1

Plugin version
phonegap-plugin-push version: 1.9.2

Logs taken while reproducing problem
ld: library not found for -lPods-*ProjectName*
clang: error: linker command failed with exit code 1 (use -v to see invocation)

@akz92 push notifications are not supported on the simulator so I'm not going to spend any time on this.

@macdonst I'm sorry, I didn't provide all the details. This error also happens when compiling for a device or to archive.

@akz92 well that's totally different then. Make sure you have cocoapods 1.1.1 installed and do pod setup. Also, if you are upgrading from an earlier version of cordova-ios you may want to do:
cordova platform rm ios
cordova platform add ios

@akz92 I have the exact same issue. I have cocoapods-1.1.1 installed and removed my iOS platform en added it again. issue is still there.

Same problem here. cocoa-pods 1.1.1 and re-adding ios platform didn't help

@macdonst I did what you suggested but nothing changed =/

Same problem here

Workaround: Open project in XCode -> Go to "Build Phases" -> "Link Binary with Libraries" -> Remove the Pods entry

try to open the .xcworkspace instead of the .xcodeproj file with xcode

Opening the .xcworkspace solved the issue for me

Yeah, you should be opening the .xcworkspace. Now that cordova-ios has cocoapod support there are 2 projects that are now contained in the work space.

Hii all how to add a  .m file in xcode

Updating the pod helped me to fix this issue.
pop update
Use this code in your iOS directory


Bug in SymmProdDAG?

   @inbounds for i = 1:dag.num1
      AA[i] = A[i]
   end

   # Stage-2: go through the dag and store the intermediate results we need
   @inbounds for i = (dag.num1+1):length(dag)
      n1, n2 = nodes[i]
      AA[i] = AA[n1] * AA[n2]
   end

This appears to simply ignore the first num1 nodes in the graph, however, they are not of the form (i, 0), which suggests that this is a bug.

blech - just misread a test. This is all good.


fix: Set container memory limit to the same as the task to ensure the…

Description of changes:
As part of investigating this memory issue with AWS Fargate it was discovered that .NET has incorrect understanding of the amount of heap space when only setting the task memory size. .NET looks at the containers hard memory limit which is not the same as the task memory.
The change is set our configured memory for both the task and container. We can do that in this tooling because we are only deploying a single container as part of the task definition.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@edwinloubser This change won't affect Lambda because it doesn't handle Lambda deployment. Using the DOTNET_GCHeapHardLimit environment variable in Lambda will help .NET in Lambda have a better understanding of the amount of available memory for the GC.

@normj understood and thank you for confirming.


cant launch 3dsx version

i am running 2ds 11.3 b9s 1.2 luma 8.0 hbl 2.0. when i launch it from homebrew launcher it asks me to select my region, when i do that the message please wait while your files are being imported then crashes with the code C8804470|4000000030700|0

Try using the cia version.

this error code means that you're selecting the wrong region.Try selecting other regions

okay it opened this time and i selected unlock all tracks, characters, vehicles etc, i press start and it exits and i assume it saves? i go on to mk7 and its corrupted so how do i restore the backups?

ok cool i used the new 3dsx version and it worked, though id still like to restore my original save and add on top of that

Steps to restore:-

Open up FBI
Select SD
Scroll Down and open mk7se
Open backup
There must be * only two* SystemX.dat files where X is a number from 0-9
Click on the file, and an "file action" dialog will show up. Select "Copy all contents" from there.
Go back to main menu of FBI and select Titles
Scroll down until you see "MARIO KART 7" and press the A button a "title action" dialog box will show  up
Select Browse Save Data
Select "" by pressing the A button and select Paste


Fix mp4 videos saving on Android Q

Codecov Report

Merging #71 (210871a) into master (175d454) will not change coverage.
The diff coverage is 0.00%.

@@          Coverage Diff           @@
##           master     #71   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files         365     365
  Lines       10081   10098   +17
  Branches      924     928    +4
======================================
- Misses      10081   10098   +17

Impacted Files
Coverage Δ

...pmobilny/ui/modules/embedview/EmbedViewActivity.kt
0.00% <0.00%> (ø)

...opmobilny/ui/modules/photoview/PhotoViewActions.kt
0.00% <0.00%> (ø)

...o/github/wykopmobilny/ui/widgets/WykopEmbedView.kt
0.00% <0.00%> (ø)

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 175d454...210871a. Read the comment docs.


Torch.tensor issue

Thanks for your work, it helps a lot! ❤ My first lora came out 10/10 yesterday, following your guide.
However, today I'm getting these warnings on each training steps:
Steps:   1%|_                                  | 64/5000 [19:45<24:36:41, 17.95s/it, lr=0.0001, step_loss=0.384]Passing `txt_ids` 3d torch.Tensor is deprecated.Please remove the batch dimension and pass it as a 2d torch Tensor
Passing `img_ids` 3d torch.Tensor is deprecated.Please remove the batch dimension and pass it as a 2d torch Tensor

Is there any fix for that? Also, does it affects the training itself?

It does not affect training. It's just a deprecation warning in SimpleTuner that will be patched in the next release. You can ignore it.

Thank you!


(build) fix secure issue in spring.

Codecov Report

Merging #124 (21ec282) into dev (d0aab1c) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##                dev     #124   +/-   ##
=========================================
  Coverage     23.81%   23.81%
  Complexity      194      194
=========================================
  Files            94       94
  Lines          2843     2843
  Branches        190      190
=========================================
  Hits            677      677
  Misses         2141     2141
  Partials         25       25

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 d0aab1c...21ec282. Read the comment docs.


Bumped version number to allow packages to update.

Addresses #5.
This allows people who depend on this package to update their dependency and receive the fix introduced in #4. This will mean a lot to people using Node version 7.x.x as they are currently unable to use this module.

An example of where this change is needed is santinic/how2#70, which throws the deprecation warning on Node 6.x and causes how2 to fail entirely with 7.0.0.


Fix parameter metadata

fix an error on parameter metadata with SQL Server 2008 when calling insertion and parameter name contains braces

Codecov Report

Merging #410 into dev will decrease coverage by 0.06%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##                dev     #410      +/-   ##
============================================
- Coverage     45.01%   44.94%   -0.07%
+ Complexity     2135     2132       -3
============================================
  Files           107      107
  Lines         24669    24670       +1
  Branches       4102     4102
============================================
- Hits          11104    11089      -15
- Misses        11705    11724      +19
+ Partials       1860     1857       -3

Flag
Coverage Δ
Complexity Δ

#JDBC41
44.69% <0%> (-0.05%)
2118 <0> (+3)

#JDBC42
44.82% <0%> (-0.03%)
2129 <0> (-4)

Impacted Files
Coverage Δ
Complexity Δ

...oft/sqlserver/jdbc/SQLServerParameterMetaData.java
23.98% <0%> (+0.16%)
31 <0> (+1)
:arrow_up:

...m/microsoft/sqlserver/jdbc/SQLServerResultSet.java
31.72% <0%> (-0.9%)
242% <0%> (-7%)

...n/java/com/microsoft/sqlserver/jdbc/Parameter.java
58.44% <0%> (-0.22%)
56% <0%> (ø)

...om/microsoft/sqlserver/jdbc/SQLServerBulkCopy.java
49.71% <0%> (-0.15%)
213% <0%> (-1%)

...rc/main/java/com/microsoft/sqlserver/jdbc/dtv.java
59.65% <0%> (-0.14%)
0% <0%> (ø)

...in/java/com/microsoft/sqlserver/jdbc/IOBuffer.java
54.68% <0%> (+0.06%)
0% <0%> (ø)
:arrow_down:

...ncurrentlinkedhashmap/ConcurrentLinkedHashMap.java
42.42% <0%> (+0.21%)
46% <0%> (ø)
:arrow_down:

...m/microsoft/sqlserver/jdbc/SQLServerStatement.java
59.87% <0%> (+0.3%)
139% <0%> (+1%)
:arrow_up:

...c/main/java/com/microsoft/sqlserver/jdbc/Util.java
60.04% <0%> (+0.43%)
91% <0%> (+1%)
:arrow_up:

... and 2 more

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 55e20ed...78d40e0. Read the comment docs.


Update

Dark is there any updates soon.
If there are, which features will be added?

This isn't something that would be for github bug reports.


Fix data sources that include includes in their queries

Coverage increased (+0.07%) to 91.36% when pulling 019216e6c65e6511b2cfc9496b11496612bdb5f4 on fix-data-sources-with-includes into 5e1af7a9e703300c10dd7c617eba2b1ba2eaaa11 on master.


Prototype W3C DQV (Data Quality Vocabulary)-based QA ontology and DCAT (Data Catalogue Vocabulary) generation

This is the result of investigating how we can represent QA results and integrate them into the platform. It's not complete code or RDF but should be enough to plot a path in future stories.
Included here:

RDF in ontologies/ which includes

The background structure which individual results link to (Data Quality Vocabulary Categories, Dimensions and Metrics for our specific case, definitions of the EDAP grading scheme, etc).
Two sample conversions of the two example outputs we got from NPL into triples.

A converter from STAC to DCAT-based triples so that datasets can be represented in RDF. The QA results need to link to these and we need them for searching for annotations based on identifiers. This is invoked only from tests.
Sekeleton framework for an annotations ingester which would receive catalogue change messages from Pulsar, generate DCAT, and ingest pre-generated QA/annotation graphs.

Part of this skeleton is a stub for a candidate method for de-duplicating functionality duplicated across all the harvesters, ingesters and transformer. The STAC-to-DCAT converter fits into this proposed framework but the framework itself is not implemented (hence it being called only from tests). Implementing it would be in EODHP-643, EODHP-644 and EODHP-999.

The Github Actions will fail until PRs 2 and 3 in github-actions are merged. I've tested with the feature branches for those PRs and it succeeded, but they'll be deleted once merged.


[FEATURE] Support for Windows Containers

Describe the solution you'd like
It might be a huge request given the implications, but I would like to have the option to choose to specify how many windows node to deploy (default to 0) so that the cluster can support windows container as well.
Is this something feasible?

Hi @gionapaolini , thanks for opening this issue!
I'm afraid, k3s won't work on Windows directly and honestly, I never worked with Windows containers before, so I have no idea how k3d would work with Docker and Windows Containers :thinking:
Any input welcome though.

Hey @gionapaolini,
There is an open issue on K3S to support windows agents.
https://github.com/k3s-io/k3s/issues/114
As K3D is just a wrapper for launching K3S in Docker I do not see any chance support windows containers or nodes at this point of time.


Add sample token.

Summary
We recently upgraded our reference server to allow users to preconfigure a static bearer token that always work.  Update the config to prefill that for the reference server for ease of use purposes.  Note that this will technically not work until the new reference server is deployed, but since it isn't prefilled now anyhow, this doesn't really hurt things.
See https://github.com/onc-healthit/inferno.healthit.gov/pull/71
New behavior
Bearer token for single patient api tests will be prefilled.

When I try to use a preset while running inferno-community locally I get Unknown module:


Access is denied error in RegisterTaskDefinition method...

I am getting Access is denied error when try to run the example code in front page which is
using (TaskService ts = new TaskService())
{
                    TaskDefinition td = ts.NewTask();
                    td.RegistrationInfo.Description = "Does something";

                    td.Triggers.Add(new DailyTrigger { DaysInterval = 2 });

                    td.Actions.Add(new ExecAction("notepad.exe", "c:\\test.log", null));

                    TaskPrincipal tp = td.Principal;

                    ts.RootFolder.RegisterTaskDefinition(@"Test", td);

                    ts.RootFolder.DeleteTask("Test");
                }

I have running this code with Administration privileges and also I have manually created Test folder in Task Scheduler in Windows. My operation system is Windows 7 with UAC disabled.
So any idea, what I am missing? I had just search other discussions tried all other things but no solution..
Originally posted: 2012-12-26T07:22:47

Permissions at either the system level or checking if UAC is blocking your rights would be my first guess. Nothing else seems to be amiss.
Originally posted: 2013-01-02T08:40:08


[Proposal] Add conda release

With the ability to make github actions on release, add conda releases to github release workflow

Why not using the standard conda-forge channel?
I'm asking this because it seems to me that the existing tooling built around conda-forge is hard to match with any simpler GH Action, which could mean less maintenance in the long run.

Agreed, looking at it more, I think we just need to make a staged recipe for the project with each of the options

I was looking a bit into it, the first problem I encountered is that pygame is not packaged for Conda (but I guess you knew that already) and from what I could read it looks pretty tricky to package, but I'll try to have a look anyway.
Related issues: https://github.com/pygame/pygame/issues/1953, https://github.com/conda-forge/staged-recipes/pull/19665, https://github.com/pygame/pygame/issues/3320.

gym is already in conda-forge, including most of the optional outputs (but stuck on 0.21 due to the addition of the extremely trick pygame dependency with 0.22). please help us get things packaged there rather than do your own thing. Though the good news is that https://github.com/conda-forge/staged-recipes/pull/19665 seems to be nearing completion...

I apologize for interrupting the thread, but I was curious about the progress of the "Official Conda packaging" mentioned in Roadmap #12. Since February is coming to an end, I was wondering if there are any updates you could share with us regarding the status of this feature. Thank you for your time and efforts!

@h-vetinari has been doing an amazing job on conda, and there already exists a conda install for gymnasium.
https://github.com/conda-forge/gymnasium-feedstock

We don't have 0.27 yet as there'll be some new dependencies that'll take some work. Join the discussion in https://github.com/conda-forge/gymnasium-feedstock/issues/1 if you want, and any help is always welcome (I can try to help out, but probably won't be able to lead this effort; the gym->gymnasium transition already took a bunch of time I didn't really have planned for this 🙃).

Gymnasium on conda has been updated to the latest version, thank you to @h-vetinari  and @ChristofKaufmann for all of their hardwork
https://github.com/conda-forge/gymnasium-feedstock

Happy to hear it!
Now that we've caught up in terms of versions, it's would probably be worth mentioning under the installation instructions? We also support windows. :)
conda install -c conda-forge gymnasium  # or "gymnasium-all" for all supported optional extensions

yes, good point, @h-vetinari could you make a pr for this?

yes, good point, @h-vetinari could you make a pr for this?

This seems to have fallen through the cracks, sorry - anyone else up for it?

Is this just a documentation update? Sorry, I have forgotten what we wanted to do


1.2.0 wheel on pypi contains 1.3.1 code!!!

This seems to have happened yesterday, the wheel of 1.2.0 was updated but the content is not right.

Yes

@gbataille Thanks for pointing this out. I will get this sorted out. This was not my intention at all. I created 1.3.0 but forgot to update the version string in the project. Therefore the upload to PyPi of the wheel is incorrect. I will take that down and try to un tag the 1.3.0 release.

thanks.
This drove me crazy. all my builds started to fail all of a sudden (with
fresh venv).
The issue is the PR I submitted. Tom's code to obfuscate passwords actually
does not work with drf test, for a reason that slightly eludes me for the
moment.
The fix works though.
On Fri, Aug 4, 2017 at 9:17 AM, Andrew Velis<EMAIL_ADDRESS>wrote:

@gbataille https://github.com/gbataille Thanks for pointing this out. I
will get this sorted out. This was not my intention at all. I created 1.3.0
but forgot to update the version string in the project. Therefore the
upload to PyPi of the wheel is incorrect. I will take that down and try to
un tag the 1.3.0 release.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aschn/drf-tracking/issues/64#issuecomment-320176372,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABD76XIu50duvX9mNRGup9a0fYhDsJJFks5sUsWZgaJpZM4OtW8y
.

@gbataille I have remove the published wheel but left 1.2.0 that was uploaded on March 8th. This should bring it back to what it was before the upload.

@gbataille I am going to close this issue.


feat: remove oauth interface auth

Signed-off-by: Gaius<EMAIL_ADDRESS>
Description

Remove oauth interface auth.

Related Issue

Motivation and Context

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation Update (if none of the other choices apply)

Checklist:

[x] Code compiles correctly.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

Codecov Report

Merging #857 (a9f7a7d) into main (d063ef2) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #857   +/-   ##
=======================================
  Coverage   41.34%   41.34%
=======================================
  Files         103      103
  Lines        8047     8047
=======================================
  Hits         3327     3327
- Misses       4306     4309    +3
+ Partials      414      411    -3

Flag
Coverage Δ

Object-compatibility-e2etests
?

e2etests
?

unittests
41.34% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

client/daemon/peer/peertask_stream.go
53.82% <0.00%> (-1.23%)
:arrow_down:

client/daemon/peer/peertask_file.go
52.02% <0.00%> (-0.34%)
:arrow_down:

client/daemon/peer/peertask_base.go
46.66% <0.00%> (+0.60%)
:arrow_up:

client/daemon/peer/peertask_stream_callback.go
64.07% <0.00%> (+1.94%)
:arrow_up:


Azure API base instruction wrong?

Hi. I think you have the Azure API base instruction wrong.
I tried https://{your-resource-name}.openai.azure.com/openai/deployments/{deployment-id}/completions?api-version={api-version}
However got errors - error message was the model was ?looking for GPT 4
Instead I used https://{your-resource-name}).openai.azure.com/openai/deployments/{deployment-id}/chat/completions?api-version=2023-12-01-preview, which seems to work.  (i.e. add in '/chat' after deployment ID - which seems to be in some other instructions on general sites around using Azure GPT4V).
Is this correct now, or will this create issues for me?
thanks

Thanks, you are correct. Just update the readme according.


profiler issue when training with 64 or more GPUs

Issues happened at the profiler steps frequently, under the disguise of other problems such as all-reduce timeouts.

We tried inserting a torch.distributed.barrier() right after trace dumping. However, it doesn't seem to resolve the issue. In fact, now the timeout happens at the all-reduce which the barrier itself issues (with 100 seconds timeout).
It is confusing that dumping on all ranks takes less than 25 seconds, and it seems all ranks have joined the barrier, and all ranks seems to have timed out.
Reopen to track this issue.

Investigated offline with @wconstab, it seems not all ranks finished trace dumping and got stuck, thus causing timeout. We wondered if it was caused by unstable mounted storage write. I'll switch to "dumping to local disk during training -> cp to mounted storage after training" and see if it helps.

This is also a case where our tooling for desync debug needs to improve.  It should be very easy/quick to learn that 32/64 ranks did not join the barrier and that's the reason for the timeout, but it still requires some head-scratching today to get to that conclusion.  cc @c-p-i-o

oh - in this case, the users (us) didn't even try using the flight recorder. we just looked at the logs carefully and determined that only 32 ranks printed a log that was right before the barrier call, so then we realized the other 32 were missing from the barrier.  or something like that.
my point is that in general, we want the timeout message to say something nice and helpful like "these specific ranks didn't join", instead of the opaque message we get today which is just that some collective timed out

update: the issue has been figured out -- it's because the profiling dumping step taking too much time than reasonable. It only takes 0.5 seconds for 70B model to dump (~80MB trace per rank) to local disk, but was taking ~1000 seconds for the mounted storage.


Broken links in README.MD

is this project dead  ?

yes: extinct like a dinosaur …
Martin Jonasse
Seemattstrasse 38
CH-6333 Hünenberg See
Fon: 079 832 69 10
<EMAIL_ADDRESS>
On 02 Jan 2020, at 15:30, do-d1<EMAIL_ADDRESS>wrote:
is this project dead ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/mapbox/osm-bright/issues/129?email_source=notifications&email_token=AILY7GZEQYVLK25XEXEHZ73Q3X3BNA5CNFSM4GMGIWT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH6O34I#issuecomment-570224113, or unsubscribe https://github.com/notifications/unsubscribe-auth/AILY7G37XJ72YG6ELUVXXQTQ3X3BNANCNFSM4GMGIWTQ.


Feature Request: Automate Helm Chart Update

Is your feature request related to a problem?
Up to now we used Updatecli to define tailored update scenarios. I am now looking to automatically detected those common scenarios.
One of them is:

Search recursively all Chart.yaml in a specific directory/git repository
Identify all chart dependencies
Generate appropriate Updatecli manifest and then run them right away

name: <chart_name>-<dependency_name>
sources:
    <dependency_name>:
        name: Get latest "<dependency_name>" Helm Chart Version
        kind: helmchart
        spec:
            name: <dependency_name>
            url: <dependency_url>
conditions:
    <dependency_name>:
        name: Ensure dependency "<dependency_name>" is specified
        kind: yaml
        spec:
            file: .chart/<chart_name>/Chart.yaml
            key: dependencies[2].name
            value: <dependency_name>
        disablesourceinput: true
targets:
    <dependency_name>:
        name: Bump chart dependency "<dependency_name>" in Chart "<chart_name>"
        kind: helmchart
        spec:
            file: Chart.yaml
            key: dependencies[2].version
            name: chart/<dependency_name>
            versionincrement: minor
        sourceid: <dependency_name>

Solution you'd like
I would like to be able to run the following command
# Updatecli should be able to identify helm chart
updatecli diff

#Updatecli should be able to apply helm chart update
updatecli apply

The flag --disable-auto would disable the auto-guessing feature
Alternatives you've considered
No response
Anything else?
For a more global discussion https://github.com/updatecli/updatecli/discussions/755
The auto feature would also greatly benefit from https://github.com/updatecli/updatecli/issues/716

Related: https://github.com/updatecli/updatecli/issues/409

Related: #409

Related: #409

I am getting there :)

Now that the autodiscovery is ready, I can have a look to this issue if needed.
Considering that there is no way to clearly identify Helmfile configuration, I am not considering the helmfile crawler to be running by default. Instead we'll need to enable it using a configuration.
So proposed Updatecli manifest
# A scm configuration can be specified so Updatecli browse the git repository content.
scms:
    default:
        kind: github
        spec:
        # ...
pullrequests:
    default:
       kind: github
       spec:
       # ....

autodiscovery:
     # Optional configuration to specified the scm configuration used in generated manifest
     scmid:
     # Optional configuration to specified the pullrequest configuration used in generated manifest
     pullrequestid:

     crawlers:
         helmfile:
            # default false
            enabled: true

            # Optional, mutually exclusive with only
            ignore:
              - path: <specifies path to ignore>

            # Optional, mutually exclusive with ignore
            only:
              - path: <only explore this path>

            # OptionDefault scm directory or local if nothing specified
            rootdir: <override directory to analyze>

The rule would be
If we find a yaml file with the following content
repositories:
    - name: example
      url: https://mychart

releases:
    - chart: example/mychart
      version: 1.0.0

Then we generate the manifest
title: "Bump {{ helmChart Name }} Helm Chart Version"

# if `scmid` is specified in autodisccovery configuration
scms:
  {{ scmid }}:
    kind: github
    spec:
      {{ scmid spec }}

sources:
  {{ chartName }}:
    name: Get latest {{ chartName }} version
    kind: helmchart
    spec:
      url: {{ chartRepositoryUrl }}
      name: {{ chartName }}

conditions:
  # Extra protection in case the target file changed between the detection and apply
  {{ chartName }}:
    name: "Ensure {{ chartName }} chart is specified"
    kind: yaml
    scmid: default
    spec:
      file: {{ filename }}
      key: {{ identified_key }}
      value: {{ repositoryNAme }}/{{ chartName }

targets:
  {{ chartName }}:
    name: "Update {{ chartName }} chart version"
    kind: yaml
    scmid: default
    spec:
      file: {{ filename }}
      key: {{ identified_key }}

# If pullrequestid is specified in autodiscovery configuration`
pullrequests:
  default:
    kind: github
    scmid: {{ scmID }}
    spec:
      labels:
        - dependencies
        - accountapp


Accept proj4 as dict?

Some libraries create proj4 representations as dicts instead of as a string. Probably useful to accept such a proj4 dict. This would be easy since internally we transform the string to dict anyway.
Should this be in a separate method loader.from_proj4_dict, or just allow loader.from_proj4() to accept either string or dict? @djhoese?

just allow loader.from_proj4() to accept either string or dict?

I'd prefer to just allow from_proj4() to accept either.  Within that function it is already converting the proj4 string into a dictionary.  One function that accepts either seem more pythonic to me.  My 2 cents.

Sounds good, that would be my preference too, simpler API and more flexible input. And agree about + key signs.

Added in 8f8857c302aa52cb0969976e61f73f1b0e588634.


NO-JIRA: Show the actual tables from the preconfigured MySQL container (Branch 1.1)

update tutorial to reflect current database content

Hey @JanHendrikDolling, thanks a lot! I'll attribute this to https://issues.redhat.com/browse/DBZ-1845. Note the 1.1 branch is maintained only for critical doc fixes, for smaller fixes like the one here applying to master would be enough.


Make artifact available on Maven

The button in the README points to https://search.maven.org/search?q=a:monix-connect*, however it appears that the artifact is not available on Maven.
Can you please publish versions to Maven?

Hi @scheleaap, thanks for pointing that. There was some problems that made us stop publishing the aggregated jar, but I will look into it or either remove that part of the docs.
I would recommend to just pick up the connector you need, in order to avoid pulling transitive dependencies in between.
See for example aws-s3.

Ah, thanks for pointing out the individual artifacts! I did not notice there is a specialized artifact on the (in my case) MongoDB page.

No problem @scheleaap


Better Approach To Keepalive

In order to conserve battery, both Badger 2040 and Badger 2040 W cut the power immediately after refreshing the display in most examples. This is great for battery life, but not so great for user experience and we haven't really considered what the right balance should be here. It has also led to bugs like #7 where user-interaction causes the power to cut abruptly and unexpectedly.
I propose a major rethink of this pattern with some key goals:

Try to avoid the user having to think about battery and when to power off
Allow the system to remain powered on while the user is interacting- this would make apps like List as snappy as they are on USB power
Allow the system to go to sleep/power off after a period of inactivity, whereupon a new button press turns it on and reloads the last app as normal

It feels like all of the user-facing buttons should be polled somehow in the background (we could attach an interrupt for this perhaps) and any button press should ensure the 3V3_ENABLE pin is turned back on to keep power running.
Rather than having a halt in the main loop, we should probably find some means of checking if the system is busy, and cut power when it has been "idle" for a (configurable?) timeout.
I don't know quite how any of this will work but I think it's worth thinking about.

Exactly this is the reason, I was recently ordering a Badger 2040 (without WiFi) to see, if it gives a better user experience. The "radio" module really consumes a lot and batteries (alkalines...) below 3V total voltage, seem to be a fragile thing. So also ordered LiPos to pimp my 2040 W.
Another question is, why this battery box for the alkalines was added anyways? Shouldn't there be a LiPo-charger onboard, so we wouldn't have to detach even the LiPo battery?
There is much headroom for improvement...


Update scheduler plugin usage in test_scheduler_highlevel_graph_unpack_import

As title
EDIT: https://github.com/dask/distributed/pull/5120 updated scheduler plugins to be tracked in a dictionary instead of a list. This PR update some logic in dask/tests/test_layers.py::test_scheduler_highlevel_graph_unpack_import accordingly

Planning to merge this after CI finishes to unblock other PRs


Enable executing TLSChallengeTest and UpgradesTest on P/Z

This PR intends to enable executing TLSChallengeTest and UpgradesTest on P/Z. Also a workaround has been added in UpgradesTest to make it execute on P/Z.
Changes are verified manually using ./gradlew test --tests=TestName
Part of this PR intends to revert few changes added as part of #4357

/test ocp-4-10-qa-e2e-tests
/test ocp-4-12-qa-e2e-tests

hi @gavin-stackrox kindly check this PR

/test ocp-4-10-qa-e2e-tests
/test ocp-4-12-qa-e2e-tests


Pending legislation: Michigan HB 5619

https://www.legislature.mi.gov/documents/2023-2024/billintroduced/House/htm/2024-HIB-5619.htm

https://www.legislature.mi.gov/Bills/Bill?ObjectName=2024-HB-5619


Swap back to Identity as the default for SQL Server

Also remove all SQL Server-specific ways to change whether a property is considered StoreGneratedPattern.Identity or not. This is a core level concept that should be handled by the core.
Issue #2175.

:shipit:

@ajcvickers This is great! Saved me reams of code on the SQLCE provider


fix should not use light index change for bloom filter index

Proposed changes
Only inverted index support light index change, bitmap and bloomfilter index do not support light index change.
Before this pr, if we add or drop bitmap and bloomfilter index, it only do linked schema change, do not rewrite index data for history data.
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


[Bug]: Add ARM linting rule to flag @get operation override on ArmResourceActionAsync and ArmProviderActionAsync

Describe the bug
Default Action verb is @post, but we do allow verb override to such as @get. Should have linting rule to flag error on anything other than @post.
Reproduction
Playground
Checklist

[x] Follow our Code of Conduct
[x] Check that this issue is about the Azure libraries for typespec. For bug in the typespec language or core libraries file it in the TypeSpec repo
[x] Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
[x] The provided reproduction is a minimal reproducible example of the bug.

talked with Allen offline and the purpose of this issue: a new rule to flag anything other than get and post as error.


Changing both component's sizes causes exception

When you change both component's size you will get $digest already in progress exception.

I fixed this by placing the $apply function within a setTimeout() on line 82


Installing issue, 20.04.2023

As far as I am aware this issue is related to Binary Ninja itself rather than my plugin.
For further information, you can execute the command in cmd to see exactly what is going on "C:\Program Files\Vector35\BinaryNinja\plugins\python\python.exe" -m pip --isolated --disable-pip-version-check install --verbose --target "C:\Users\<user>\AppData\Roaming\Binary Ninja\python310\site-packages" requests bs4.
The plugin might still work even if the pip installation fails depending if required packages have been installed in the past.
To fix this manually, what you can do is install required packages using regular python (if you have it installed on your system) rather the one bundled with Binary Ninja by executing python -m pip --isolated --disable-pip-version-check install --verbose --target "C:\Users\<user>\AppData\Roaming\Binary Ninja\python310\site-packages" requests bs4 in cmd.

I can confirm that I just tried this and it worked! Thank you!


favicon.ico file

Generate favicon.ico file.

I think @mar-bi had a few suggestions when we first started the Slack chat, not sure if they are still available due to the message limitations on slack.
@mar-bi do you still have the grad.then() mockups you did?

yes, sure i have it

However it is quite long for a favicon. Could we use just a cap instead?

I like 1 or 3

I prefer this one :)

First is perfect.

Nice choice, guys! :+1:
Here is the .svg

I will. :-)


When StorageIntegration will be supported in Python

Hi, as we are building our IAC for sources we need to ingest data to Snowflake using Snowpipe, we found that it seems StorageIntegration is not yet supported in pulumi_snowflake as shown in the screenshot

I would like to raise such an issue so keep track on the latest development of such support.
Thanks.

Hi @kongwilson , thanks for opening up this issue. Apologies for the misleading docs – this resource should be fully supported in the pulumi provider. We'll track progress on this issue, but you should be able to use the resource now.
Please let us know if you have any further questions.

Thanks @aq17 , I will give it a go:)

It does exist and works well. Thanks


zotero: 7.0.8 → 7.0.10

Diff: https://github.com/zotero/zotero/compare/7.0.8...7.0.10
This update has also the side effect of "unbreaking" the "Better Bibtex" plugin for Zotero.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 359851

x86_64-linux

:white_check_mark: 1 package built:

zotero

x86_64-darwin

:white_check_mark: 1 package built:

zotero

aarch64-darwin

:white_check_mark: 1 package built:

zotero


Not working in Firefox

Firefox 62 for Mac
It adds the button to the toolbar, and when I go to Preferences, I can't add anything. This is all I see:

It appears that the body of the table is empty:

Hi ,
we are not supporting firefox for now


Support  for WindowGroup

Hi guys
I checked your library and example and I saw StackNavigationViewController and TabNavigationViewController work with
SceneDelegate
like this
`func scene(_ scene: UIScene, willConnectTo session: UISceneSession, options connectionOptions: UIScene.ConnectionOptions) {
guard let windowScene = scene as? UIWindowScene else {
return
}
	// 👉 Choose showcase 👈
	let showcase: Showcase = .advanced

	let window = UIWindow(windowScene: windowScene)
	window.rootViewController = makeRootViewController(
		with: readShowcaseForUITest() ?? showcase
	)
	self.window = window
	window.makeKeyAndVisible()
}`

But with SwiftUI project, we will use WindowGroup instead.
How can I set StackNavigationViewController, TabNavigationViewController for  WindowGroup without create new UIViewControllerRepresentable

Hi @toanbv-fabbi!
The idea of this Swift Package is to build the navigation using UIKit. SceneDelegate/AppDelegate is the preferred approach because you can use the rootViewController of the window. I'm not sure if there is a benefit in using the SwiftUI based setup, but StackNavigationViewController and TabNavigationViewController are just subclasses of UINavigationController and UITabBarController so you can wrap it like any other UIViewController in SwiftUI.

you can read at here
https://www.iosdevie.com/p/swiftui-replace-appdelegate-scenedelegate
https://betterprogramming.pub/say-goodbye-to-scenedelegate-in-swiftui-444173b23015


updates service type to reflect only the necessary properties

I hit a use case in generating a plugin that requires connect-web for transport but doesn't need the generation of services.  In that situation, this was the only blocker I am aware of that forced me to use a service.  Come to find out, then, that the full service isn't actually required.  This PR addresses that by only asking for the required fields.  It's a backwards compatible change because a full service will still structurally match.

Thanks for the initiative, Dimitri!
I'm afraid now is not a good time for this change, because we are working on the next release in the connect-web-next package, and there are a couple of things in flight that might be complicated by this change.
Closing this for - let's revisit after we switched @bufbuild/connect-web to use @bufbuild/connect-core. In the meantime, you can simply pass {typeName: "...", methods: {}} as a valid ServiceType.


create regex-matcher for multi-line support

see cfe-01 with the start-regex matching feature. allow timeout for new lines so messages terminate even if no new ones are coming up, like on cfe-01.
#16 related

Just as a reference:
Logging:
"command": [
    "/usr/bin/bash"
],
"args": [
    "-c",
    "echo 'I am first pod'; echo -e 'This is an example\nmultiline\nlog message'; sleep inf;"
]

Output:
# cat /var/log/pods/default_first-pod_fa1cff2a-0ad8-4039-8d98-8af16a6016ab/first-pod/0.log
{"log":"I am first pod\n","stream":"stdout","time":"2023-05-22T15:18:45.081887403Z"}
{"log":"This is an example\n","stream":"stdout","time":"2023-05-22T15:18:45.08192463Z"}
{"log":"multiline\n","stream":"stdout","time":"2023-05-22T15:18:45.081934895Z"}
{"log":"log message\n","stream":"stdout","time":"2023-05-22T15:18:45.081941044Z"}


Cache storage data in worker

When handling batch algorithm processing, the complete input data (including the data to be processed by the rest of the parallel algorithms) is obtained from storage upon the beginning of every algorithm in the batch.
To enhance performance, cache the last processed data from the storage in the worker, so that it will be obtained once per worker.

TID-630

worker cache Test
File: cache_test.js
describe : "'Test worker cache'"

Test
description

storage get amount
validate that the worker uses cache mechanism and does not read data from storage if its exists in cache


Images Distorted in Firefox on macOS and Windows After Scrolling

I am experiencing an issue in Firefox where images are sometimes displayed distorted after scrolling. This problem occurs on both macOS and Windows platforms. The issue seems to be related to the CSS property content-visibility: auto;.
Steps to Reproduce:

Open Firefox on either macOS or Windows.

Visit a webpage with multiple images. (e.g. about us)

Scroll down to the bottom of the page.

Scroll back up so that the images re-enter the viewport.

Expected Behavior:
Images should display correctly and maintain their original aspect ratio and quality.
Actual Behavior:
Some images appear distorted, stretched, or compressed after they re-enter the viewport following a scroll action.
Workaround: When the following CSS option is commented out in the Layout.astro file, the issue does not occur:
img {
    content-visibility: auto;
}

Screenshots:

Could you please investigate and provide a fix for this issue?
It significantly affects the user experience, and any help would be greatly appreciated. Thank you!

Hi @rekombination
After trying many things, finally to solve it we have eliminated the style that you mentioned:
img {
    content-visibility: auto;
}

Fixed with: https://github.com/onwidget/astrowind/commit/ab746d051378b8b15dd83c544cf7b4be8aced27b
Thanks


Development Will Resume Soon!

Hello all, just wanted to say that I have not forgotten this project! I've been checking in from time to time really surprised and grateful for the growth and feedback!
You may have seen my commit from about two months ago, and I just wanted to echo this in GitHub issues in case someone hasn't seen it in the readme!
I've been busy with university in the past half year, but plan on resuming development to address all the issues at around February. Hopefully, this coincides with Svelte 5's release: it's coming soon, and I would prefer for my updates to be written in the new syntax rather than old syntax if possible!

That's very awesome Braden, looking forward to it! After all, Whispering is by far the best speech recognition on Windows out there.

That's great, this is a really cool project!

great project we are waiting for you to come back to it. thanks for your commitment it is usefull to a lot of us

It's great to hear that, Braden! Thanks a lot for the update :)
Quick question: Would it be possible for you to release a hotfix, so that the Firefox version of Whispering works again? Because the only reason, I'm still using Brave Browser is, that Whispering is broken on Firefox, unfortunately.

Hi Braden,
just wanted to mention that we users are thinking a lot about you and would love to see you resume development of Whispering. For my part, I would like to have two different hotkeys to turn Whispering on and off so that I can control it reliably with Autohotkey and/or keyboard remapping.

Hi Braden, just wanted to mention that we users are thinking a lot about you and would love to see you resume development of Whispering. For my part, I would like to have two different hotkeys to turn Whispering on and off so that I can control it reliably with Autohotkey and/or keyboard remapping.

Having two hot key is a mess for normal user. I have another reccorder that have that and it’s such a problem. You can use Mac whisper if you want that it’s not free but have this messed up multiple key shortcut. Let Whispering with simplicity of use. It’s perfect as it is nothing more needed.

Understand what you mean and agree. The problem that I'm having is that sometimes the status of Whispering is not clear because it might have been inadvertently started, meaning that it can unintentionally be active and record for hours. If you then want to actually dictate something and switch it on via hotkey, it will be switched off instead and you loose your dictation.
Therefore, an option for two different hotkeys (that can but does not have to be used) would be good, alternatively a way to recognize visually and programmatically (also if minimized) whether Whispering is active and listening or not.
[dictated using Whispering]

Thank you Braden! Looking forward to seeing the next version of Whispering, which is already one of the greatest things in existence for dictating anywhere on your PC.
May I ask, when resuming work on Whispering, could you start building from this great fork by @HamzaETTH? https://github.com/braden-w/whispering/issues/69
Thank you!

@braden-w The extension is completely broken now unfortunately, due to the domain for ChatGPT moving from chat.openai.com to chatgpt.com.
Do you think you could kindly provide a hotfix?

Therefore, an option for two different hotkeys (that can but does not have to be used) would be good, alternatively a way to recognize visually and programmatically (particularly when minimized) whether Whispering is active and listening or not.
[dictated using Whispering]

Most definitely.  Alternatively, if we are sticking to the the same-key-toggle, please consider enabling some sort of distinguishing feature in AutomationProperties Class for the respective buttons so as to facilitate better accessibility please.

Greetings everyone.  While awaiting Braden to hopefully resume development of this wonderful, cross-platform app with browser plugin, take a look at my comment below:
https://github.com/braden-w/whispering/issues/51#issuecomment-2119316375
With vanilla AHK (v1 or v2), cURL and phiola, it wouldn't take much to whip up a Whispering desktop app equivalent, with prompting.
Of course, that would be Windows-only, and extra work would involved to make a browser plugin.
But there will be enormous flexibility with the cURL approach on Windows.  The workflow can even be ported to something like VoiceMacro, for both computer control and prose dictation ...


How to set position of and change position frequenlty

I have implemented this speed view in my project, but it started to move automatically from left to right, but I want to change position of indicator between 180 to 360. Can you please tell me how to achieve this.

Tremble is an option to move indicator around current speed #28 .
to stop it use app:sv_withTremble="false" Attribute, or if you want to increase the range use sv_trembleDegree="180" Attribute.
is that what you want ? I'm sorry, but your question is confusing to me!

Hello,
Sorry if my question has confused you, but yes your answer is right, it is
that which i wanted, thank you for your support.
On Wed, May 24, 2017 at 11:33 AM, Anas Altair<EMAIL_ADDRESS>wrote:

Tremble https://github.com/anastr/SpeedView/wiki/0.-Get-Started#tremble
is an option to move indicator around current speed #28
https://github.com/anastr/SpeedView/issues/28 .
to stop it use app:sv_withTremble="false" Attribute, or if you want to increase
the range use sv_trembleDegree="180" Attribute.
is that what you want ? I'm sorry, but your question is confusing to me!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/anastr/SpeedView/issues/29#issuecomment-303626195,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXRd4sXSdj6Y-tO0ylnQlNasG4Hlhq7Qks5r88gfgaJpZM4Nkn8S
.

--
Keyur NimavatSenior Android DeveloperLets Treat Everyone Fairly
M: +91 9586 432121
L :<PHONE_NUMBER>1
A :  KBA SYSTEMS,
312, DEV ARC COMMERCIAL COMPLEX,
BEHIND VIJAY SALES, ISCON CROSS ROAD,
S.G. HIGHWAY,
SATELLITE,
AHMEDABAD-380054
GUJARAT, INDIA
W: www.kbasystems.com  E<EMAIL_ADDRESS>https://www.facebook.com/kbasystemscompany
https://in.linkedin.com/in/kba-systems-081aa7125

Dear ,
Your Friend Carter Adom has invited you to join Rig Lynx.
Rig Lynx Admin
Phone No: +1<PHONE_NUMBER>
Email Id<EMAIL_ADDRESS>Address: Houston,Texas
© 2017 Rig Lynx All Rights Reserved

@KeyurKba !!

Hi ,
Your Friend Harshal Aher has invited you to join Rig Lynx.
Rig Lynx Admin
Phone No: +1<PHONE_NUMBER>
Email Id<EMAIL_ADDRESS>Address: Houston,Texas
© 2017 Rig Lynx All Rights Reserved

Hi ,
Your Friend Frank Grills has invited you to join Rig Lynx.
Rig Lynx Admin
Phone No: +1<PHONE_NUMBER>
Email Id<EMAIL_ADDRESS>Address: Houston,Texas
© 2017 Rig Lynx All Rights Reserved


[67] Add first source compatibility regression fix

Do we know what project in the compat suite triggered this?

Can't seem to figure it out from the tweet or issue(s), unfortunately :(


Add a bridge test for AmountRequired

?
📝 Description
Bridge integration tests didn't include a test of the AmountRequired error, i.e they were not testing that when the transaction amount is 0 or not provided we return an error.
❓ Context

Impacted projects: ledger-live-common
Linked resource(s): -

✅ Checklist

[x] Test coverage
[x] Atomic delivery
[x] No breaking changes

📸 Demo

🚀 Expectations to reach
Integration tests passing for all currencies (but currently broken for many other reasons)

Integration tests run : https://github.com/LedgerHQ/ledger-live/actions/runs/2712583291


[cherry-pick] fix: panic at empty http spec (#1660)

Type of change:

[x] Backport patches

Backport #1660

Codecov Report

:exclamation: No coverage uploaded for pull request base (v1.6.0@db20b67). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head d86906e differs from pull request most recent head 84cccd7. Consider uploading reports for the commit 84cccd7 to get more accurate results

@@            Coverage Diff            @@
##             v1.6.0    #1757   +/-   ##
=========================================
  Coverage          ?   41.52%
=========================================
  Files             ?       87
  Lines             ?     7420
  Branches          ?        0
=========================================
  Hits              ?     3081
  Misses            ?     3987
  Partials          ?      352

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Tests for ISPN-7300 and ISPN-7301 and extending query testsuite

Extending query testsuite and tests for:
https://issues.jboss.org/browse/ISPN-7300
https://issues.jboss.org/browse/ISPN-7301
Tests testFullTextTermDoesntOccur and testFullTextTermRightOperandAnalyzed should be failing because of the above mentioned issues.

I've disabled the failing test2 and integrated it. Thanks @Holmistr !


Add daocloud casestudy

What type of PR is this?
/kind documentation
What this PR does / why we need it:
Add daocloud casestudy based on the recent presentation.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
/cc @RainbowMango @wawa0210

Please solve the conflicts.


Moving templates to separate documents

This had been done for one of the components, but not for all of them. Moving them to separate files makes it easier for me to edit and work with the html, but you might have a reason for keeping these relatively small templates in the components.

Hi @LukeSchlangen thanks for the PR. As an example project I think it's best to show a mix of inline and external templating. Therefore I'm going to close this without merging.
Thanks again :)

Makes sense!