To Do list: list structure

Project requirements

Set up a new project with webpack that is based on the webpack exercise you have already completed.
Create an index.html file and write your HTML markup here. Create an empty To Do List placeholder (<div> or <ul> element). The index.html file must be set as a template using the HTML Webpack Plugin.
Create an index.js file and set an array of some simple to do tasks (array of objects). Each task object should contain three keys:

description [string].
completed [bool].
index: [number].

Write a function to iterate over the tasks array and populate an HTML list item element for each task.
On page load render the dynamically created list of tasks in the dedicated placeholder. The list should appear in order of the index values for each task.
Create a style.css and set rules for the To Do List. CSS must be loaded by Webpack Style/CSS Loader. Your list should be a clone of the part of the minimalist project captured in the video below.

All your source files (index.html, index.js and style.css) must be located in /src directory and your distribution files will be generated by webpack and served by webpack dev server from /dist folder.

webhint linter is not working well, Microverse notified us to submit the project and that issue would be ignored by code reviewers, the rest of the project requirements are finished and working perfectly.


python311Packages.dogpile-cache: 1.1.8 -> 1.2.0

Changelog: https://github.com/sqlalchemy/dogpile.cache/releases/tag/rel_1_2_0
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 231728 run on x86_64-linux 1

42 packages built:

heatclient (python310Packages.python-heatclient)
heatclient.dist (python310Packages.python-heatclient.dist)
ironicclient (python310Packages.python-ironicclient)
ironicclient.dist (python310Packages.python-ironicclient.dist)
manilaclient (python310Packages.python-manilaclient)
manilaclient.dist (python310Packages.python-manilaclient.dist)
nox
nox.dist
openstackclient (python310Packages.python-openstackclient)
openstackclient.dist (python310Packages.python-openstackclient.dist)
python310Packages.bugwarrior
python310Packages.bugwarrior.dist
python310Packages.dogpile-cache
python310Packages.dogpile-cache.dist
python310Packages.openstacksdk
python310Packages.openstacksdk.dist
python310Packages.osc-lib
python310Packages.osc-lib.dist
swiftclient (python310Packages.python-swiftclient)
swiftclient.dist (python310Packages.python-swiftclient.dist)
python310Packages.subliminal
python310Packages.subliminal.dist
python311Packages.bugwarrior
python311Packages.bugwarrior.dist
python311Packages.dogpile-cache
python311Packages.dogpile-cache.dist
python311Packages.openstacksdk
python311Packages.openstacksdk.dist
python311Packages.osc-lib
python311Packages.osc-lib.dist
python311Packages.python-heatclient
python311Packages.python-heatclient.dist
python311Packages.python-ironicclient
python311Packages.python-ironicclient.dist
python311Packages.python-manilaclient
python311Packages.python-manilaclient.dist
python311Packages.python-openstackclient
python311Packages.python-openstackclient.dist
python311Packages.python-swiftclient
python311Packages.python-swiftclient.dist
python311Packages.subliminal
python311Packages.subliminal.dist


Add a CLI

Add a Command Line Interface that allows running Smapy without having to write any python code but the actions and resources.
The CLI will be given a path to a config file and this will contain everything necessary, including the gunicorn options and the resources and routes list.

 test


Vulkano versions of Sascha Willems' Vulkan examples?

Sascha Willems has a repository with many useful Vulkan examples here: https://github.com/SaschaWillems/Vulkan. They are written in C++ and use the bare Vulkan API for the most part. Would it be useful for some (or maybe even all, eventually) of these examples to be ported over to Vulkano?

You should pick one example you fancy; convert it to Rust; and report your results. Details of the experience will help others and hopefully inspire people to convert other (may all) examples.

I might be up to it, but I can only start in a few months though.


use width/height in get_vrt_transform when overzooming a dataset

This PR re-add width and height parameters to the get_vrt_transform (removed in #648) but will only be used when over-zooming a dataset
cc @amarouane-ABDELHAK @j08lue

Thank you for offering a permanent solution to the issue. It was indeed a challenge to identify the cause of the visualization problem. I wonder why we didn't think of integrating these additional lines of code into the existing pull request rather than starting a new one.


Release/v1 to DEV

I'm missing where API_BASE_URL is set, but I assume it defaults to v1 and allows a setting to v0? Or just v1?
There is this src/constants.js file where we set the URLs and also the API version.
Regarding the API version as a setting, the idea was to simply move from v0 to v1 on this next release, since we have the current v0.12 as an option for anyone who wants to access the API v0.
Lmk your thoughts on it. cc @Hackdom

yeah that's good. that matches perfectly with what we've discussed this week


refactor(ngOptions): optimize getWatchables array

We need to prevent storing irrelevant or unnecessary watchers. See discussion in PR #11017:
@petebacondarwin wrote:

I realised that we can actually optimize this by only including things that are being specified. So for instance, if no disable when clause was provided we would not need to watch this expression. The same for the displayFn which computes the label.

closed in 3cea386b2c26abffb0d2acfd9584203126f7579c


[BUG]: HuggingFace dataset materializer problem

Contact Details [Optional]
No response
System Information
zenml v0.30rc0 (applies also to v0.22 and v0.23)
ZenML version: 0.30.0rc0
Install path: /opt/anaconda3/lib/python3.9/site-packages/zenml
Python version: 3.9.7
Platform information: {'os': 'linux', 'linux_distro': 'ubuntu', 'linux_distro_like': 'debian', 'linux_distro_version': '22.10'}
Environment: native
Integrations: ['github', 'huggingface', 'pillow', 'plotly', 'pytorch', 'pytorch_lightning', 'scipy', 'sklearn']
The current user is: 'default'
The active project is: 'default' (global)
The active stack is: 'default' (global)
    Stack Configuration

┏━━━━━━━━━━━━━━━━┯━━━━━━━━━━━━━━━━┓
┃ COMPONENT_TYPE │ COMPONENT_NAME ┃
┠────────────────┼────────────────┨
┃ ARTIFACT_STORE │ default        ┃
┠────────────────┼────────────────┨
┃ ORCHESTRATOR   │ default        ┃
┗━━━━━━━━━━━━━━━━┷━━━━━━━━━━━━━━━━┛
What happened?
While passing a arrow dataset between two steps through HuggingFace dataset materializer, the dataset cannot be used in the second step, because its cache_file folder doesn't exist anymore.
The problem arises from the use of TemporaryDirectory in handle_input , which is destroyed at return, whereas this directory is still referenced in the dataset info. The folder must survive as long as the dataset is in use, so a simple work-around would be to use tempfile.mkdtemp instead of TemporaryDirectory.
But we should find how to clean-up properly after use.
Reproduction steps
No response
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi @ghpu thank you for reporting this issue. Is there any code snippet to help me to replicate this issue?
It would be helpful if you can post the full error traceback here too.
Also, would you please post the output of
python -c "import zenml.environment; print(zenml.environment.get_system_details())"
zenml status
and
zenml stack describe ?

Here is  a minimal example producing the issue:
from zenml.pipelines import pipeline
from zenml.steps import step
from zenml.steps import BaseParameters, Output

import datasets, transformers
from transformers import AutoTokenizer
from transformers import DataCollatorWithPadding
from transformers import AutoModelForSequenceClassification, TrainingArguments, Trainer

class Params(BaseParameters):
    model = "distilbert-base-uncased"
    dataset_name = "imdb"
    num_labels = 2
    label_col = 'label'
    text_col = 'text'
    batch_size = 16
    epochs = 3
    log_steps = 100
    output_max_length = 128
    max_length = 512
    learning_rate = 2e-5
    weight_decay = 0.01

@step
def load_dataset(params: Params) -> datasets.DatasetDict:
    data = datasets.load_dataset(params.dataset_name)
    return data

@step
def load_tokenizer(params: Params) -> transformers.PreTrainedTokenizerBase:
    tokenizer = AutoTokenizer.from_pretrained(params.model,
                                              model_max_length=params.max_length)
    return tokenizer

@step
def tokenize(params: Params,
             tokenizer: transformers.PreTrainedTokenizerBase,
             data: datasets.DatasetDict) -> datasets.DatasetDict:
    data = data.map(
        lambda exs: tokenizer(exs[params.text_col],truncation=True),
        batched=True)
    return data

@step
def train_model(params: Params,
                  tokenized_data: datasets.DatasetDict,
                  tokenizer: transformers.PreTrainedTokenizerBase) -> transformers.PreTrainedModel:
    data_collator = DataCollatorWithPadding(tokenizer=tokenizer)
    model = AutoModelForSequenceClassification.from_pretrained(params.model,
                                                               num_labels=params.num_labels)
    training_args = TrainingArguments(output_dir="./results/",
                                      learning_rate=params.learning_rate,
                                      per_device_train_batch_size=params.batch_size,
                                      per_device_eval_batch_size=params.batch_size,
                                      num_train_epochs=params.epochs,
                                      weight_decay=params.weight_decay)
    trainer = Trainer(model=model,
                      args=training_args,
                      train_dataset=tokenized_data["train"],
                      eval_dataset=tokenized_data["test"],
                      tokenizer=tokenizer,
                      data_collator=data_collator)
    trainer.train()
    return model

@pipeline(enable_cache=False)
def test_pipeline(load_data,
                  load_tokenizer,
                  tokenize_data,
                  train_model):
    data = load_data()
    tokenizer = load_tokenizer()
    tokenized_data = tokenize_data(data=data,tokenizer=tokenizer)
    model = train_model(tokenized_data=tokenized_data,tokenizer=tokenizer)

def main(**kwargs):
    pipeline = test_pipeline(
        load_data=load_dataset(),
        load_tokenizer=load_tokenizer(),
        tokenize_data=tokenize(),
        train_model=train_model()
    )
    pipeline.run(unlisted=True)

if __name__ == "__main__":
    main()

Hi @ghpu, @morganveyret, thank you for reporting this issue and providing the minimal code example. we have now an open PR that will be released by the end of this week. However, if you want to use it before it's out you can create a custom materializer CustomHFDatasetMaterializer with the same code and call it within a step using @step(output_materializers=CustomHFDatasetMaterializer).

This was fixed in 0.30.0


Remove version: jsdelivr.Globalping version 1.1.5

This version is older than what has been set in max-versions-to-keep by the publisher.
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/jsdelivr/globalping-cli/releases/download/v1.1.5/globalping_Windows_i386.zip
OK
(Automated message - build 923)


Can not get the flutter 2.10.2 Release notes

There is only 2.10.1 in https://github.com/flutter/flutter/wiki/Hotfixes-to-the-Stable-Channel

Also, the wiki page references
"We intend to announce hotfixes to the flutter-announce group, and we recommend that you subscribe to that list if you publish an application using Flutter."
Both 2.10.1 and 2.10.2 are not (yet) announced in the flutter-announce group.

@haohongwei
The https://github.com/flutter/flutter/wiki/Hotfixes-to-the-Stable-Channel will soon get updated. Meantime you can check this link for your reference: https://github.com/flutter/flutter/releases/tag/2.10.2
I suggest you to keep an eye on hotfixes wiki for detailed information on the newest hotfix.
Closing from here.

I think it's not really OK to not having a proper changelog when releasing something on your stable channel.
From what I understand the changelog is a combination of:

https://github.com/flutter/engine/commit/a83ed0e5e3b9cd2b5e2f07ef31c72f43c55e93b7
https://github.com/flutter/flutter/releases/tag/2.10.2 (but this only show a commit that is also reverted, so it's empty)

+1 Still not see changelog now :(

Could be due to the fact that there's a long weekend in the US (21 Feb, Monday) and all Flutter team would be not available. Once they are back to work, it'll hopefully be updated, so please have patience.

Sure. Did not realized it is long weekend before.

https://groups.google.com/g/flutter-announce/c/GYHKJscFwOk/m/Gx19IeHKBwAJ 🎉


Consecutive strings has two wrong test cases

Time: 3848msPassed: 207Failed: 2Exit Code: 1
Test Results:
Basic tests
longestConsec(['zone', 'abigail', 'theta', 'form', 'libe', 'zas'], 2)
Expected: 'abigailtheta'
Actual: 'thetaabigail'
Which: is different.
Expected: abigailthe ...
Actual: thetaabiga ...
^
Differ at offset 0
Completed in 59ms
longestConsec(['ejjjjmmtthh', 'zxxuueeg', 'aanlljrrrxx', 'dqqqaaabbb', 'oocccffuucccjjjkkkjyyyeehh'], 1)
longestConsec([], 3)
longestConsec(['itvayloxrp', 'wkppqsztdkmvcuwvereiupccauycnjutlv', 'vweqilsfytihvrzlaodfixoyxvyuyvgpck'], 2)
longestConsec(['wlwsasphmxx', 'owiaxujylentrklctozmymu', 'wpgozvxxiu'], 2)
longestConsec(['zone', 'abigail', 'theta', 'form', 'libe', 'zas'], -2)
longestConsec(['it', 'wkppv', 'ixoyx', '3452', 'zzzzzzzzzzzz'], 3)
Expected: 'ixoyx3452zzzzzzzzzzzz'
Actual: 'wkppvixoyxzzzzzzzzzzzz'
Which: is different.
Expected: ixoyx3452z ...
Actual: wkppvixoyx ...
^
Differ at offset 0
Completed in 4ms
longestConsec(['it', 'wkppv', 'ixoyx', '3452', 'zzzzzzzzzzzz'], 15)
longestConsec(['it', 'wkppv', 'ixoyx', '3452', 'zzzzzzzzzzzz'], 0)
Completed in 73ms
Random tests

Problems with kata and kata tests should be reported in kata discourse. Please post your questions in kata discussion section.
Additionally, please read this paragraph of FAQ and see if you can find anything helpful there: https://docs.codewars.com/training/troubleshooting#kata-bug


[MM-12340] update release process

Overall looks good. Requesting @amyblais to review as she's the best from PM side (for editor review and given she's the release manager).


[WIP] Next version

[x] Multiple destination (vue-skip-to-list)
[x] Basic definition file (TypeScript)
[x] Handling the link event to keep "exact" from the "vue-router"
[x] Update style
[x] Integration tests

@ktquez Happy to merge if you are 🎉

@shwilliam
I think we could launch the new version with what we have now and add other features without haste.
What do you think?

Totally agree! I'm happy with where we're at.
Supporting non-ID query selectors will require comprehensive testing before it makes it into a release.


⚠ Bofrost.be has degraded performance

In fe6d00f, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1028 ms

Resolved: Bofrost.be performance has improved in 6d05474 after 6 minutes.


Errors when resize a Table Component with custom components in columns

Steps to reproduce
1.Render a custom component in columns of the <at-table></at-table>.
2.Resize browser or dev tool in browser.
Which browser?

"vue": "^2.5.2",
"at-ui": "^1.2.0-beta",
"at-ui-style": "^1.5.1",
Chrome  V66.0.3359.139
What is expected?
No error in console
What is actually happening?

Got thousands of errors in console:
[Vue warn]: Error in nextTick: "TypeError: Cannot read property 'querySelectorAll' of undefined"

found in

---> <AtTable>

TypeError: Cannot read property 'querySelectorAll' of undefined
    at VueComponent.eval (at.js?cb07:6771)
    at Array.eval (vue.esm.js?efeb:1837)
    at flushCallbacks (vue.esm.js?efeb:1758)

// line 6771 of at.js
 var $td = _this3.$refs.body.querySelectorAll('tr')[0].querySelectorAll('td');

It seems that not only in Table Component, but many other components also threw this error.
Is there any official developers say sth about this?

I had same issues with this error as well.
Is this some sort of bugs?

same issue

Hola tuve ese mismo error :C
Vé al module y en at.js, busca esta función: handleResize: function handleResize() {....}
Lo que hice fue validar si es null
También cambie los sizes pero eso ya a tu gusto


TeachIn

This pull request introduces 2 alerts when merging 439c4902be48391593410007a92fdf6a1f00e580 into 110fdff09bc4cea89fccbdf7d171c50c00f464cc - view on LGTM.com
new alerts:

2 for Unused variable, import, function or class

Comment posted by LGTM.com


Add built-in support for Delay monad

Currently there is no good way to define potentially-looping functions with agda2hs. We have the loop function in Haskell.Extra.Loop but it still requires a proof of termination if you want to use it on the Agda side. This PR adds support for the Delay monad to agda2hs, in a way that is completely transparent in the resulting Haskell code.

Hm, I just realized this is not sound, since it is possible to distinguish between now and later in Agda. For example, one can write the following function:
bad : Delay a ∞ → Bool
bad (now x) = True
bad (later x) = False

which would get compiled to
bad :: a -> Bool
bad x = True
bad x = False

which is, well, bad.
If we want to have actual support for delay, we should enforce somehow that the result is the same in both cases, or simply forbid pattern matching on Delay altogether.

Perhaps we could allow a single function runDelay defined like this:
runDelay : {@0 x : a} (y : Delay a ∞) → @0 HasResult x y → a
runDelay (now x) now = x
runDelay (later y) (later p) = runDelay (y .force) p

plus possibly a proof that the result of runDelay is indeed equal to x.

@flupe this is ready now, could you do a quick review?

lgtm


Peer Review feedback - Siqi Zhou

Dear all,
Thanks for presenting this fabulous group project to me. I liked reading the reports you created and acquired much from it. I would just add a few points that you could consider to change if you like :)

Documentation: Overall, yes it is great! I noticed there is just no .md file available under /doc folder. To render a .md file might be helpful and more user-friendly when opening it from the GitHub website.

Code: The code is readable, clear, and with appropriate comments inside.

Analysis and reasoning: Yes it is great. I think you've done a great job! Perhaps you could utilize forward selection to reduce the number of features to enhance your model in future work.

Communication: Yes, it's easy to follow and the report communicates the findings effectively. Well done!

Suggestions: Perhaps remove the .ipynb_checkpoints folder under /src? My suggestion is to create a .gitignore file to exclude those files to be pushed to your repo.

BRs,
Siqi Zhou

Hi Siqi,
Thank you so much for your feedback!


SDK2: Replace old SDK in preview feature controller

Which issue this PR addresses:

Fixes https://issues.redhat.com/browse/ARO-4665
What this PR does / why we need it:

This PR replaces old SDK in preview feature controller.
Test plan for issue:

Test preview feature in local dev cluster according to https://learn.microsoft.com/en-us/azure/openshift/howto-enable-nsg-flowlogs.
Is there any documentation that needs to be updated for this PR?

N/A
How do you know this will function as expected in production?

Enable preview feature.

/azp run

/azp run e2e

/azp run e2e

/azp run e2e

Third E2E run had the same failure as the first - cluster installation failed because k8s API server wasn't ready.
There's no way it's related to your changes, but if it happens again on this fourth try, maybe we should start looking at changes that were merged recently (?).

/azp run

/azp run ci

/azp run e2e

/azp run


Added: Accessing the classification metadata

@giladmit : Thanks for your contribution! The author, @giladm, has been notified to review your proposed change.

#sign-off

@giladmit: I'm sorry - only the author of this article, @giladm, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@giladmit - If you are the listed author for an Azure technical article, you need to use the private repository (azure-docs-pr) for all content updates and new articles.
Closing this pull request so that you can make updates in the private repo. Thanks.


types are to challenging to decipher

Types need json examples. At present we point to the schemas which don't include formatting and values such as spec, apiversion etc.

thanks to bob for pointing me to the entries in test, will self assign and add a where to find pointer

See also #665


No unification of build and intellisense diagnostics in VS2017 (was in VS2015)

There are likely multiple issues with the Visual Studio Error list..  I'm splitting out one known repro for a basic one, which is the lack of "Error Unification" between build and intellisense errors.

open any solution, e,g,
devenv tests\projects\misc\TestProjectChanges\TestProjectChanges.sln

2,. add an error, watch intelliense error appear

do a build, wathc duplicate copy of "build" error appear

fix the error - the "intellisense" copy goes away, but the red suiglly stays

do a build - the "build" error goes away

Although logical, it is painful to have the red squiggly stay around even after you've fixed the error.  In practice this means that once you do a build, and there are errors, you have to keep doing builds do clear all your red-squigglies, or else resort to showing Intellisense errors only.
This is a regression (or at least a change) from how F# worked in VS2015 and before, when build and intellisense errors were "unified" and fixing an error made it disappear from the error list - the user just was not particularly aware of the distinction between build and intellisense errors.
Now I'm not sure how deeply this distinction is built into Roslyn - it may not be something we control anymore - advice welcome please @Pilchie  @DustinCampbell
Note that the diagnostic ID is also missing for the build error - this could be the underlying problem since some comments in the F# language service code imply that error de-duplication should be ocurring.  It's possible this is a problem with whichever error parser is being used by default

Here is the output from the build, it contains FS0039
3>C:\GitHub\dsyme\visualfsharp\tests\projects\misc\TestProjectChanges\TestProjectChanges\Program.fs(7,58): error FS0039: The field, constructor or member 'PropertyA' is not defined. Maybe you want one of the following: PropertyAlwaysAvailable
3>Done building project "TestProjectChanges.fsproj" -- FAILED.

(Note, I haven't yet compared to C# roslyn behavior)

@dsyme, I compared C# and F# in VS 2015 and VS 2017, and the results is in a comment a bit down in #2548. I don't understand that much of this, but it looks to me there's pretty much the same issue in VS 2015, but just not that obvious to the user.

@BentTranberg Ah yes, thanks.  Good analysis.  TBH I much prefer the "unified error list" model of F# in VS015 (all errors are just one kind of error), I wonder why C#/roslyn didn't adopt this model.

One of the odd things here is that this recently added code  seems to indicate that we are trying to do error unification.
    // Normalize the error message into the same format that we will receive it from the compiler.
    // This ensures that IntelliSense and Compiler errors in the 'Error List' are de-duplicated.
    // (i.e the same error does not appear twice, where the only difference is the line endings.)

However the displayed error message in the error list above still has newline characters.  Odd, will debug through this

@dsyme we are trying but we aren't reporting build errors through Roslyn, so it doesn't see the build/intellisense errors as identical (as the former don't have error IDs amongst other data). I believe I put more info in my PR: https://github.com/Microsoft/visualfsharp/pull/2839#issuecomment-294573571

@dsyme we are trying but we aren't reporting build errors through Roslyn, so it doesn't see the build/intellisense errors as identical (as the former don't have error IDs amongst other data). I believe I put more info in my PR: #2839 (comment)

Thanks, that's very helpful!  Here's a copy of the relevant comment:

@heejaechang I can answer that. F# build errors are passed to the IDE via the ErrorListProvider, which is wrapped by a Microsoft.VisualStudio.Shell.TaskProvider. See DocumentTask.cs@506 in the F# code.
I think the correct solution for this is to move over to Roslyn's ProjectExternalErrorReporter. We currently don't report any errors through this, but this class implements IVsLanguageServiceBuildErrorReporter2 so we can report build errors through the ReportError2 method. This is what the Roslyn project system does.

More notes. The current F# project system has IDEBuildLogger which is added to MSBuild loggers in DoMSBuildSubmission
                loggerList.Add(buildLogger);

MSBuild then raises events and these get pushed to ErrorHandler and WarningHandler and thus to AddToErrorList.   This creates a DefaultCompilerError (which does contain the error code) and a DocumentTask which doesn't. The task gets registered using taskReporter.AddTask.  As @saul mentions, this last call should be removed and we should probably use ProjectExternalErrorReporter

@Pilchie I'd appreciate some guidance here: does Roslyn come with any mechanism for listening to build output (e.g. from an MSBuild build logger) and creating matching tasks from the Error and Warning items that come from MSBuild?  And matching those to the text being shown in the output window?
The context is that F# intellisense errors (via roslyn) and the F# build errors (via non-roslyn) are not being de-duplicated. This is because of subtle differences in the content of the error/task items being produced by these two paths (slightly different text in multi-line error messages, and a missing ID for the non-Roslyn errors).  Ideally we want to produce all errors via roslyn to better ensure consistency.  But we don't want to reinvent the wheel here.

@saul @Pilchie  I notice we do already create our own ProjectExternalErrorReporter, perhaps we just have to use that
Glancing around the Roslyn code I see GetExternalErrorReporter but also note there is no F# mapping here, which must be why we create our own. It would be helpful to start removing the C#/VB-specific things from Roslyn and just make it a multi-language framework.

@saul @Pilchie
I took a look at what it would take to junk the existing F# code for build task creation and use ProjectExternalErrorReporter.  A draft of what would be needed is here:
https://github.com/Microsoft/visualfsharp/compare/master...dsyme:eld?expand=1
@saul If you get the chance could you take a glance over that draft and see what you think?  The idea is to literally delete the use of TasKReporter and TaskProvider in the ProjectSystem.Base and replace it with a propagated IVsLanguageServiceBuildErrorReporter2 (i.e. a ProjectExternalErrorReporter)

@heejaechang has pretty much done everything related to the Error List since Roslyn started, and I'll admit that I've lost track of it.
HeeJae - can you confirm my understanding is correct?
IIRC, Roslyn has no ability to insert msbuild loggers or anything, but the C# project system looks for error output and creates the "Build" tasks.  Roslyn only reports the "IntelliSense" errors from it's in-memory model.

@saul @heejaechang @Pilchie  I updated the branch above, https://github.com/Microsoft/visualfsharp/compare/master...dsyme:eld?expand=1.
However I get a crash when using it.  I believe the CompilerDiagnosticAnalyzer service has not been implemented for F#.  We do implement DocumentDiagnosticAnalyzer.  I'll try to implement CompilerDiagnosticAnalyzer  tomorrow, I presume it is not too hard.
Here are the details how I got to this conclusion if you're interested... Creating the error manager makes us fall active paths to this FailFast check https://github.com/dotnet/roslyn/blob/175c1605927859bc3cfcd4a84b720b27c4054ba9/src/Features/Core/Portable/Diagnostics/EngineV2/DiagnosticIncrementalAnalyzer.StateManager.cs#L139. This is because this code:
                var compilerAnalyzer = _analyzerManager.GetCompilerDiagnosticAnalyzer(project.Language);

is returning null for F#. This is because:
        return _hostAnalyzerManager.GetCompilerDiagnosticAnalyzer(language);

is returning null. The _hostAnalyzerManager comes from this.  So this is returning null, because _compilerDiagnosticAnalyzerMap.TryGetValue is returning null,

Ouch, ComppilerDiagnosticAnalyzer is internal in Microsoft.CodeAnalysis.dll, and FSharp.Editor doesn't have an IVT attribute to that DLL (it has IVT attributes to many other DLLs).
@Pilchie @cartermp  This is a bit of a show-stopper on fixing this regression from VS2015

@dsyme - Roslyn's ErrorList implementation also doesn't have IVT to Microsoft.CodeAnalysis.dll.  That dll is part of our compiler layer, and none of the VS assemblies have IVT to it.

I expect we actually depend on the CompilerDiagnosticAnalyzer from Microsoft.CodeAnalysis.EditorFeatures.dll, and F# should have IVT to that.

@Pilchie Thanks.  I think it has an IVT (though I don't seem to be able to see DefaultDiagnosticAnalyzerService which is strange).  Though even if I could get one of those I'm not yet sure how would I pass it in and associate it with the F# language name - perhaps it's easy

@Pilchie Poking around I also notice scary not-friendly-to-F# things like this (found that via a code search) which would indicate it's not going to recognize anything as a CompilerDiagosticAnalyzer easily.  That's used here
It's late and I'm kind of lost in this stuff.  If you can see a way to solve the basic problem of reusing Roslyn's implementation of ProjectExternalErrorReporter (which seems to require a CompilerDiagosticAnalyzer) then that would be very helpful.

@saul To recap - I think my prototype branch to use ReportError2 via our ProjectExternalErrorReporter is quite close to working but we've hit this internal Roslyn problem while trying to use the Roslyn ProjectExternalErrorReporter.
Perhaps there is some other path we can take like our own implementation of the VS interface for ReportError2 though there's a significant amount of code involved in that.
I'm a bit concerned that there are a few landmines for F# scattered over the Roslyn codebase (e.g. places where if-C#-if-VB is hardwaired).  If we stick to the well-trodden path that TypeScript has already used we should be OK I suppose, but it's not easy to tell what that path is.

@saul @Pilchie I've added a Roslyn issue here which I think summarizes things: https://github.com/dotnet/roslyn/issues/19547

@dsyme can you try this? https://github.com/dotnet/roslyn/pull/19561 to see whether this fix your issue?

@heejaechang Thanks!  I'll aim to give that a go tomorrow UK time, if not the next day

An update on this: we've made good progress towards unifying the build and intellisense error lists , see discussion on https://github.com/dotnet/roslyn/pull/19561.  This even appears to work for multi-line error messages which I had expected to be problematic
This requires a Roslyn fix, so we have to see when that makes it in - hopefully soon!  We will also require the Roslyn fix to be in place, or Visual Studio will crash when it hits the call to FailFast.

@dsyme Glad to see we're making progress on this. Also the multi-line messages are already identical, I made sure of that in my PR when I attempted to fix it 👍

Also the multi-line messages are already identical, I made sure of that in my PR when I attempted to fix it

Nah :) The ones coming from the build do not have line breaks.  See the two screen shots below, the first showing the Intellisense error, the second the Build error

Hmm then something isn't right... or the build errors are being reported to the IDE in a different way now? There is code that explicitly replaces the fake newline character with the real one before passing it to the platform: https://github.com/Microsoft/visualfsharp/blob/ce473ddab307c1bbbf027207badf086e71a238ff/vsintegration/src/FSharp.Editor/Common/RoslynHelpers.fs#L108-L111

@saul That's right for Intellisense errors.  The question is build errors, which go via the IDEBuildLogger class.
The screenshots above are for my branch when using a fixed Roslyn
When using master, you get this:

In which case, the errors should definitely go through ErrorLogger.NormalizeErrorString |> ErrorLogger.NewlineifyErrorString.
Your last screenshot also doesn't agree with the screenshot I put on the PR, which does have new lines in both cases. Maybe it's something specific to the suggested names? Either way it should have new lines!

In which case, the errors should definitely go through ErrorLogger.NormalizeErrorString |> ErrorLogger.NewlineifyErrorString.

Yes, I was wondering that.  Though don't forget the error text is scraped from the output of fsc.exe  by MSBuild (with --flaterrors).  Does that even have the magic characters needed?

@brettfo The fix is now in roslyn - https://github.com/dotnet/roslyn/pull/19561. Could you update this issue when we have those Roslyn binaries in this repo please?   THanks!

@dsyme We don't install roslyn binaries here.  As there are no API changes involved in the Roslyn change, this should just start working on newer builds of VS with that Roslyn change.

@Pilchie Ah. The problem is that we can't use the functionality until we can be sure we have the fix - if we ended up running against the old binaries we bring down the whole VS process because we end up hitting the FailFast here (I suggested a more gracious error handling technique would have been sensible :) )
https://github.com/dotnet/roslyn/blob/175c1605927859bc3cfcd4a84b720b27c4054ba9/src/Features/Core/Portable/Diagnostics/EngineV2/DiagnosticIncrementalAnalyzer.StateManager.cs#L139

In that case I would recommend either:

Holding the F# change until there is a public build with the fix, which is unforunate.
Conditioning the F# change on the file version of the Roslyn binary being higher than the first Roslyn signed build with this fix (looks like that's 20170524.5) and filing an issue to remove the lightup check once F# depends on a public version with the fix.

Conditioning the F# change on the file version of the Roslyn binary being higher than the first Roslyn signed build with this fix (looks like that's 20170524.5) and filing an issue to remove the lightup check once F# depends on a public version with the fix.

That sounds plausible

Fixed by #3071


Resource temporarily unavailable, ENOMEM on CPU with memory rlimit

System information

Have I written custom code (as opposed to using a stock
example script provided in TensorFlow): yes, trivial example
OS Platform and Distribution (e.g.,
Linux Ubuntu 16.04): Debian buster
TensorFlow installed from (source or
binary): source
TensorFlow version (use command below): 2.1.0
Python version: 3.73
Bazel version (if compiling from source): ?
GCC/Compiler version (if compiling from source): 8.3.0
CUDA/cuDNN version: - GPU model and memory: not relevant

Describe the current behavior
The system has 12 GB total physical memory, with /etc/security/limits.conf set to limt per-process max memory to 10 GB as follows:
* hard rss 10485760
* hard as 10485760

A trivial code example runs out of memory. The last failling syscall obtained with strace is
mmap(NULL, 8392704, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = -1 ENOMEM (Cannot allocate memory)
Looking at mmap invocations from strace confirms that it is indeed allocating close to 10 GB memory before fail. This does not happen when the resource limits are removed. I suspect that it's ignoring the rlimit and trying to allocate all physical memory.
Describe the expected behavior
The library should respect the current max memory rlimit (or better yet, not try to allocate all system memory?) or provide some configuration parameter to limit memory (I found none for the CPU-based version).
Standalone code to reproduce the issue
from __future__ import absolute_import, division, print_function, unicode_literals

import tensorflow as tf
import numpy as np

tf.config.set_visible_devices([], 'GPU')
model = tf.keras.Sequential([ tf.keras.layers.Dense(units=1, input_shape=[1]) ])
model.compile(optimizer='sgd', loss='mean_squared_error')

xs = np.array([-1.0, 0.0, 1.0, 2.0, 3.0, 4.0], dtype=float)
ys = np.array([-3.0, -1.0, 1.0, 3.0, 5.0, 7.0], dtype=float)

model.fit(xs, ys, epochs=1)

Other info / logs
Strace output:
...
write(1, "Train on 6 samples\n", 19Train on 6 samples
)    = 19
ioctl(1, TCGETS, {B38400 opost isig icanon echo ...}) = 0
sched_getaffinity(0, 128, [0, 1, 2, 3, 4, 5, 6, 7]) = 64
sysinfo({uptime=8660, loads=[12896, 10528, 13536], totalram=12518699008, freeram=2526597120, sharedram=950390784, bufferram=1171718144, totalswap=4898942976, freeswap=3857969152, procs=741, totalhigh=0, freehigh=0, mem_unit=1}) = 0
mmap(NULL, 8392704, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = -1 ENOMEM (Cannot allocate memory)
futex(0x7f5ca3c481a0, FUTEX_WAKE_PRIVATE,<PHONE_NUMBER>) = 0
write(2, "terminate called after throwing "..., 48terminate called after throwing an instance of ') = 48
write(2, "std::system_error", 17std::system_error)       = 17
write(2, "'\n", 2'
)                      = 2
write(2, "  what():  ", 11  what():  )             = 11
write(2, "Resource temporarily unavailable", 32Resource temporarily unavailable) = 32
write(2, "\n", 1
)                       = 1

@jploski,
I was able to run the code without any issues and did not observe any memory issues. Please find the gist of it here. Thanks!

@amahendrakar What does "ulimit -m" and "ulimit -v" report in your test environment? Did you set a memory limit in /etc/security/limits.conf (and logged in again to make it effective)? This code sample only crashes for me if there is a configured memory limit, and it works otherwise (sorry if that was not clear from the original bug report).

@jploski,
The output of both ulimit -m and ulimit -v is unlimited. Please check the gist of it here.
Unfortunately, I am unable to set the memory limit in the limits.conf file. Thanks!

@amahendrakar I just checked that I can also use set the rlimit in shell without without changing limits.conf:
ulimit -v 10485760
ulimit -m 10485760
python3 example.py

(The value should be something below the total available memory in kB.)

@jploski,
I've tried running the above commands and reset the runtime. Didn't observe any changes, got the same output as before.

TensorFlow does not detect the amount of memory available via rlimits. Crashing when allocating memory above these limits is working as intended. This happens with most programs:
#include <stdio.h>
#include <stdlib.h>

int main () {
        char *a = malloc(SZ);
        printf("Allocated %u bytes to %p\n", SZ, a);
        *a = '0';
        printf("Set the start of %p to 0\n", a);
        return 0;
}

root@7b8dce9800a9:/work# ulimit -v 4504; ./a.out
Allocated 10000 bytes to 0x55890a43e260
Set the start of 0x55890a43e260 to 0
root@7b8dce9800a9:/work# ulimit -v 4503; ./a.out
Allocated 10000 bytes to (nil)
Segmentation fault (core dumped)

Although there exist calls to detect available memory limits and trim allocation, this would have to happen before every allocation and would still be vulnerable to TOCTOU. Plus, it is not portable, thus not something we would prioritize.
Furthermore, there is a tf.config.experimental.set_memory_growth API point.

Of course, the issue here is not that a crash occurs when you allocate memory above limit. The issue is that you attempt to allocate more memory than is available, which most programs don't do.
Not fixing this issue means that the non-GPU version is unusable in presence of a rlimit. Not sure how it behaves with other kinds of limits (e.g. cgroup limits imposed by Docker containers), but I predict it would fall on its face as well. (A similar issue existed for a time in Java VM and got fixed to make it behave properly.)
If you can't handle it so as to allocate only the amount of memory actually available to the process, I suggest that you at least display some warning if a memory limit is detected.

I'm going to add it to the security list of issues for further prioritization.

Hi There,
This is a stale issue. As you are using an older version of tensorflow, we are checking to see if you still need help on this issue. Please test the issue with the latest TensorFlow (TF2.7 and tf-nightly). If the issue still persists with the newer versions of TF, please feel free to open it in keras-team/keras repository by providing details about the issue and a standalone code to reproduce the issue. Thanks!
Please note that Keras development has moved to a separate Keras-team/keras repository to focus entirely on only Keras. Thanks!


getting an error while using LogoutView.as_view() in main urls.py file

My main urls.py file looks like this...
urlpatterns = [
url(r'^$', views.home, name='home'),  # the route for home
url(r'^signup/$', accounts_views.signup, name='signup'),
url('r^logout/$', auth_views.LogoutView.as_view(), name='logout'),  # this is a Django class-based view
url(r'^boards/(?P\d+)/$', views.board_topics, name='board_topics'),  # listing topics based on
Board
url(r'^boards/(?P\d+)/new/$', views.new_topic, name='new_topic'),
url(r'^admin/', admin.site.urls),
]
The error i am getting is as follows:
url('r^logout/$', auth_views.LogoutView.as_view(), name='logout'),
AttributeError: module 'django.contrib.auth.views' has no attribute 'LogoutView'
How do i fix this?

try changing to : url(r'^logout/$', auth_views.logout, name='logout'),


chores after releases for ASA-2024-007

Description

closes: #XXXX

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against the correct branch (see CONTRIBUTING.md).
[ ] Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/).
[ ] Added relevant godoc comments.
[ ] Provide a conventional commit message to follow the repository standards.
[ ] Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
[ ] Re-reviewed Files changed in the GitHub PR explorer.
[ ] Review SonarCloud Report in the comment section below once CI passes.

Wondering if we need to maintain all the compatibility tests for retracted versions?

I will clean this up in a follow up PR, but I think I am going to add the latest tags of each major version to the compatibility tests of the currently supported versions, even if those major versions are EoL. At the end of the day, even if they are EoL it would still be nice that we don't break compatibility.

Wondering if we need to maintain all the compatibility tests for retracted versions?

I will clean this up in a follow up PR, but I think I am going to add the latest tags of each major version to the compatibility tests of the currently supported versions, even if those major versions are EoL. At the end of the day, even if they are EoL it would still be nice that we don't break compatibility.

i kind of feel like keeping the compatibility tests in might signal something contrary to EoL, though, so maybe that's something to discuss internally. i remember this topic coming up before and i think we decided to not keep the EoL tags in for that reasoning...but maybe worth discussing again.


Make ext-openssl and phpseclib optional dependencies

PR for #88. Please note that this will require a new major version since phpseclib would get removed with an update even if it's used in a project. It has to be explicitly required after this PR.

@kelunik looks good. Shallwe go for a major release so that others can upgrade as they want? I guess a bunch of people would want to rely on having those libraries installed, whereas others wouldnt mind at all :)

If you don't have any other breaking changes pending and think this change satisfies a new major version by itself, go ahead.

thanks man!


Upgrade to Python 3.12

SSIA, we are on aiohttp 3.9.1 on both Supervisor and Core, removing the blockers to move to Python 3.12.
We are very early in the current development cycle, so that should be a good time to move.

Let's wait 1-2 bugfix version of python 3.12 before we ship it to all

That is the point of this PR. The 3.12.1 is expected this week. This bump would give us a full month of testing.
We currently have no blockers left (besides known incompatible integrations that have been notified way before).
../Frenck


Use native enums if the database supports them

Upstream: https://code.djangoproject.com/ticket/24342
Are there any advantages to doing this?

Enums are supported by postgres, mysql, mariadb and oracle. The only Django supported RDBMS that does not support them as native types is SQLite.
They do not offer much advantage over django-enum's implementation using check constraints but one solid reason to support them is to support inspectdb.

MYSQL, Mariadb and Oracle all support enum creation inline with table creation. Postgres requires the Enum type to be created before the table, i.e. CREATE TYPE mood AS ENUM ('sad', 'ok', 'happy');. Its unclear to me how you might generate migrations that do this without monkey patching Django internals.

I would like to support native enum types in the future. Kicking this can down the road to after the 2.0 release.
My current thinking is to add a native toggle as a kwarg to EnumField:
enum_field = EnumField(EnumClass, native=True)

This would resolve to a NativeEnumField type that works on connections other than sqlite and uses the names of the EnumClass as the internal database Enum types. Supporting this on mariadb, mysqldb and oracle seems trivial - postgres is more complicated.


Fails tests on machine that has /usr/lib/nagios/plugins/ directory

As per subject. Sample fail report: http://www.cpantesters.org/cpan/report/098edf76-e3e0-11ec-b10a-61aea8c5ac02

Fixed in version 1.502, I just disabled that test as am not maintaining nagios at present, thanks for the report.


Fixes bot username override issue with incoming webhooks

Summary
In Global thread item list bot (incoming webhook) username override wasn’t implemented which this pr will fix
Ticket Link
Fixes https://mattermost.atlassian.net/browse/MM-38180
Related Pull Requests
NONE
Screenshots

Release Note
* Global thread item username (incoming webhook) username override fix

@AshishDhama I didn't merge since Kyriakos left a suggestion.

still LGTM :)

@koox00 @jgilliam17 please take another look.

/update-branch


Bump version to 4.1.2.

Would it be possible to push the new version to rubygems?

Thanks for this, I've released it, but I had to do some other changes so I didn't merge this one.


Change colorScheme to dropdown on profiles page

Summary of the Pull Request
Make the color scheme profile setting a combobox

References

PR Checklist

[ ] Closes #xxx
[ ] CLA signed. If not, go over here and sign the CLA
[ ] Tests added/passed
[ ] Documentation updated. If checked, please file a pull request on our docs repo and link it here: #xxx
[ ] Schema updated.
[x] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Detailed Description of the Pull Request / Additional comments

Validation Steps Performed

Closing in favor of #8388.


float3/4.Normalize.Zero returns zero

see #461

If I remember correctly intN.Normalize() to return a floatN, instead of a intN approximation, was deliberate. But it is as matter of definition and should be discussed at our next meeting.

imoh intN(1,1,1) should not normalize to intN(0,0,0) due to missing decimals.

I agree, that is why we didn't drop the decimal.


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter awattar for common errors and appropiate suggestions to keep this adapter up to date.
This check is based the current head revisions (master / main  branch) of the adapter repository
Please see the result of the check below.
ioBroker.awattar
   -
ERRORS:

[ ] :heavy_exclamation_mark: [E026] "{'engines': {'node'>='16'}}" is required at package.json, "{'engines':{'node'>='18'}}" is recommended
[ ] :heavy_exclamation_mark: [E033] @iobroker/adapter-core 2.4.0 specified. 3.1.4 is required as minimum, 3.1.6 is recommended. Please update dependencies at package.json
[ ] :heavy_exclamation_mark: [E036] @iobroker/testing 2.3.0 specified. 4.1.3 is required as minimum,  4.1.3 is recommended. Please update devDependencies at package.json
[ ] :heavy_exclamation_mark: [E136] No "common.news" found for actual version 1.0.6 in io-package.json
[ ] :heavy_exclamation_mark: [E157] js-controller 2.0.0 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.
[ ] :heavy_exclamation_mark: [E254] Versions "1.0.2, 1.0.3" listed at common.news at io-package.json do not exist at NPM. Please remove from news section.
[ ] :heavy_exclamation_mark: [E701] No actual year found in LICENSE. Please add "Copyright (c) 2024 SirJojo69<EMAIL_ADDRESS>at the start of LICENSE

WARNINGS:

[ ] :eyes: [W127] Missing suggested translation into uk of "common.titleLang" in io-package.json.
[ ] :eyes: [W134] Missing suggested translation into ru,pt,nl,fr,it,es,pl,uk,zh-cn of "common.desc" in io-package.json.
[ ] :eyes: [W135] "common.tier" is required in io-package.json. Please check https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/objectsschema.md#adapter.
[ ] :eyes: [W154] Missing suggested translation into uk of some "common.news" in io-package.json.
[ ] :eyes: [W168] "common.keywords" should not contain "iobroker, adapter, smart home" io-package.json
[ ] :eyes: [W181] "common.license" in io-package.json is deprecated. Please define object "common.licenseInformation"
[ ] :eyes: [W184] "common.main" is deprecated and ignored. Please remove from io-package.json. Use "main" at package.json instead.
[ ] :eyes: [W184] "common.materialize" is deprecated for admin >= 5 at io-package.json. Please use property "adminUI".
[ ] :eyes: [W184] "common.title" is deprecated and replaced by "common.titleLang". Please remove from io-package.json.
[ ] :eyes: [W513] "gulpfile.js" found in repo! Think about migrating to @iobroker/adapter-dev package
[ ] :eyes: [W953] .npmignore found - consider using package.json object "files" instead.

SUGGESTIONS:

[ ] :pushpin: [S522] Please consider migrating to admin 5 UI (jsonConfig).

Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
Suggestions reported by repository checker should be reviewed. Suggestions can be ignored due to a decision of the developer but they are reported as a hint to use a configuration which might get required in future or at least is used be most adapters. Suggestions are always optional to follow.
You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:
@iobroker-bot recheck
@iobroker-bot recreate
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence
Last update at Fri, 13 Sep 2024 09:51:05 GMT based on commit 8af7d95549fd67ea06fcd36a1eb35584d3b05186
ioBroker.repochecker 3.0.5

This issue has been updated by ioBroker Check and Service Bot
The following issues have been fixed
[W184] "common.main" is deprecated and ignored. Please remove from io-package.json. Use "main" at package.json instead.
:thumbsup:Thanks for fixing the issues.
The following issues are new and have been added
[W184] "common.main" is deprecated and ignored. Please remove from io-package.json. Executable is defined by entry "main" at package.json.


Nima: WebClient Proxy Support

Environment Details

Helidon Version: 4
Helidon Nima

Problem Description
Nima WebClient does not have Proxy support. This issue is spawned off from https://github.com/helidon-io/helidon/issues/5386 to cover the proxy support implementation on Nima client.

Once this is implemented, please make sure that Proxy is added as part of the key (KeepAliveKey) in https://github.com/helidon-io/helidon/blob/main/nima/webclient/webclient/src/main/java/io/helidon/nima/webclient/http1/ClientRequestImpl.java#L330-L331


Updated Downloads Page w/ Link to iOS SDK v1.1.2 Fat Binary

@pavitrabhalla
Changes

I updated the download link for the iOS SDK v1.1.2 Fat binary on the Downloads page and
Updated the information on the jumbotron UI of the main Index to reflect the updated SDKs from today and last week

:+1: Looks good!


colab error

I should have to do this for unsetting espeak
!apt-get install espeak
Also It occured
AttributeError: 'HParams' object has no attribute 'duration_discriminator_type'

configs/vits2_vctk_standard.json
follow that file and change your json to add 'duration_discriminator_type'

configs/vits2_vctk_standard.json follow that file and change your json to add 'duration_discriminator_type'

https://colab.research.google.com/drive/1y_XFXZTcWmV7l0w1anZqfD4zrEdXGwQ5?usp=sharing
other error occured.  how can i solve that?

if you are talking about this error -
torch.cuda.OutOfMemoryError: CUDA out of memory. Tried to allocate 20.00 MiB. GPU 0 has a total capacty of 14.75 GiB of which 5.06 MiB is free. Process 33947 has 14.74 GiB memory in use. Of the allocated memory 14.26 GiB is allocated by PyTorch, and 200.53 MiB is reserved by PyTorch but unallocated. If reserved but unallocated memory is large try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF
it says that your gpu is out of memory, so reduce batch size number and try again. I will advice you to google search the errors to debug on your own first and read a bit more about training models. Thanks.


fix for https://github.com/kubernetes/website/issues/17597

Fix for issue #17597

@lojies @sftim please see if this PR looks good.

/lgtm
/approve


Adding a java ping pong game.

This app is a multiplayer ping pong game with an endless scoring system.
This project would be under GSSOC'22

@J-Harsh  Add the proper discription in discription box then i will assign you issue.

This app is a multiplayer ping pong game with an endless scoring system.
This project would be under GSSOC'22

@J-Harsh go for it, Good Luck 👍


Update batch-add clear exit ug

Updated batch-add, clear and exit in the User Guide
Now batch-add includes clear steps from creating CSV file to running the command

Codecov Report

Merging #225 (5a4220b) into master (095dac5) will decrease coverage by 0.08%.
The diff coverage is 55.55%.

@@             Coverage Diff              @@
##             master     #225      +/-   ##
============================================
- Coverage     56.83%   56.74%   -0.09%
  Complexity      499      499
============================================
  Files            93       93
  Lines          2129     2134       +5
  Branches        254      256       +2
============================================
+ Hits           1210     1211       +1
- Misses          849      851       +2
- Partials         70       72       +2

Impacted Files
Coverage Δ

...in/java/coydir/logic/commands/BatchAddCommand.java
69.84% <55.55%> (-4.30%)
:arrow_down:

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

Fixes #190


Fix typo: revokation -> revocation

https://en.wiktionary.org/wiki/revocation

Fixed (did this one manually as the merge conflicted with the last one), thanks!


feat(apps/prod/jenkins): use the image with pre-install plugins

To solve the issue that jenkins auto install all plugins after each restart. We deployed using pre-installed plugin versions of the image.

@purelind: it is solved by other way, thanks.


The Sims 2: objects use wrong textures in 2.5.2

As of version 2.5.2, some 3D objects in The Sims 2 use textures that don't belong to them:

The same scene with the same game setup in 2.5.1:

Logs from both versions are almost the same:
2.5.2 Sims2EP9RPC_d3d9.log
2.5.1 Sims2EP9RPC_d3d9.log
You can also find similar reports on Reddit:
https://www.reddit.com/r/sims2help/comments/1hn59yx/new_hpintel_laptop_graphic_glitches/
https://www.reddit.com/r/sims2help/comments/1hk9drk/how_to_fix_this_sht/
https://www.reddit.com/r/sims2/comments/1hlnh7e/something_cursed_for_your_amusement_dxvk/
Software information
The Sims 2
high settings
RPC launcher
System information

GPU: NVIDIA GeForce GTX 1660 Ti / Intel(R) UHD Graphics 630
Driver: <IP_ADDRESS>22 / <IP_ADDRESS>9
OS: Windows 11
DXVK version: 2.5.2 (x32, d3d9)

Hi there. This should already be fixed on master. Try this build https://github.com/doitsujin/dxvk/actions/runs/12435734651

@Blisto91 Yeah, this build fixes the issue. Thanks.


rm: fix -vr to match GNU's output, add -R for recursive

This

fixes #1768.
adds a test case for removing directory with --verbose
adds an additional flag -R for --recursive
cleans up prompt_file()

As discussed here https://github.com/uutils/coreutils/issues/1768#issuecomment-796162092 there was a logic bug in handle_dir() that prevented the correct stdout/stderr output if --interactive mode was not set to always.
In an attempt to fix this bug and to fix the stdout/stderr to match GNU's output, I moved the call to remove_dir_all() from handle_dir() to remove_dir(). Also, for simplicity, I replaced the call to fs::remove_dir()withremove_dir_all()'.

I am not a big fan of having a PR (even less commits) doing several things at once.
Would it be possible to split this PR in smaller commits?
thanks

@sylvestre Done.

I just realised that this pull request has two bugs which are related to #1769.
1:  rm_uu -d non_empty_dir deletes the directory instead of stating: cannot remove 'non_empty_dir': Directory not empty
2: rm -rfv non_empty_dir does not list the deleted file(s)
$ mkdir -p non_empty_dir && touch non_empty_dir/file_a
$ rm -d non_empty_dir
removed 'non_empty_dir/file_a'
removed directory 'non_empty_dir'

$ mkdir -p non_empty_dir && touch non_empty_dir/file_a
$ rm_uu -rfv non_empty_dir
removed directory 'non_empty_dir'

I guess I'll split this PR into two separate PRs and fix these bugs there.


Module is still using old puppet types

Use Case
The module is still using the old form of Puppet types.
While this will not cause any outright errors, it does make the module more difficult to pick up and alter in the future as the way in which it is written is no longer standard and will be less familiar to people going forward.
Describe the Solution You Would Like
The existing types should be moved to the current format.

I think I may have confused myself.........
Gonna close this and rethink what I meant

Perhaps you meant parser functions? Though I don't see those here either.


Filler Bot unable to submit transactions

During the process of running the keeper bot (command: yarn start --filler --trigger --config-file example.config.yaml), it always reports the following error and transactions have not been successfully submitted.
————————————————————————————————————————————————————————
[2024-02-21T02:21:19.474Z] info: slotSubscriber slot: 249460315, userMap slot: 249460344
[2024-02-21T02:21:19.475Z] info: including taker AMDsLg6HPmkQRUBwhYMCpVoNc17tJEJmjgNpa3srWc4d-35534 (fillTxId: 678)
[2024-02-21T02:21:19.475Z] info: Filling perp node 1 (fillTxId: 678)
taker on market 11: AMDsLg6HPmkQRUBwhYMCpVoNc17tJEJmjgNpa3srWc4d-35536 short 0/1067 @ 0 (orderType: oracle)
makers:
vAMM
[2024-02-21T02:21:19.475Z] info: slotSubscriber slot: 249460315, userMap slot: 249460344
[2024-02-21T02:21:19.476Z] info: including taker AMDsLg6HPmkQRUBwhYMCpVoNc17tJEJmjgNpa3srWc4d-35536 (fillTxId: 678)
[2024-02-21T02:21:19.476Z] info: sending tx, 26 unique accounts, total ix: 2, calcd tx size: 1024, took 2ms (fillTxId: 678)
Error loading priority fee solana: Unexpected token 'j', "json metho"... is not valid JSON
SyntaxError: Unexpected token 'j', "json metho"... is not valid JSON
at JSON.parse ()
at ClientBrowser._parseResponse (/Users/yong/Desktop/project/keeper-bots-v2/node_modules/jayson/lib/client/browser/index.js:131:21)
at /Users/yong/Desktop/project/keeper-bots-v2/node_modules/jayson/lib/client/browser/index.js:103:10
at ClientBrowser.callServer (/Users/yong/Desktop/project/keeper-bots-v2/node_modules/@solana/web3.js/lib/index.cjs.js:6472:9)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Simulated tx took: 262ms
[2024-02-21T02:21:20.299Z] info: tryBulkFillPerpNodes estimated CUs: 29922 (fillTxId: 678)
[2024-02-21T02:21:20.299Z] error: simError: {"InstructionError":[4,{"Custom":6239}]} (fillTxId: 678)
[2024-02-21T02:21:20.299Z] info: Processing tx log for assoc node 0
taker on market 11: AMDsLg6HPmkQRUBwhYMCpVoNc17tJEJmjgNpa3srWc4d-35534 short 0/1067 @ 0 (orderType: oracle)
makers:
vAMM
[2024-02-21T02:21:20.299Z] error: assoc node (ixIdx: 0): AMDsLg6HPmkQRUBwhYMCpVoNc17tJEJmjgNpa3srWc4d, 35534; does not exist (filled by someone else); Program log: Order does not exist 35534
[2024-02-21T02:21:20.299Z] info: Processing tx log for assoc node 1
taker on market 11: AMDsLg6HPmkQRUBwhYMCpVoNc17tJEJmjgNpa3srWc4d-35536 short 0/1067 @ 0 (orderType: oracle)
makers:
vAMM
[2024-02-21T02:21:20.299Z] error: assoc node (ixIdx: 1): AMDsLg6HPmkQRUBwhYMCpVoNc17tJEJmjgNpa3srWc4d, 35536; does not exist (filled by someone else); Program log: Order does not exist 35536
——————————————————————————————————————————————————
I increased maxPriorityFeeMicroLamports from 10000 to 20000 or even higher, but still couldn't submit transactions. Is it due to my computing speed, network issues, or low fee configuration?

this can happen if the RPC you are using is down or out of credits

this can happen if the RPC you are using is down or out of credits

out of credits? How to check credits?"

you cannot use the RPC in example.config.yaml, will remove it. Need to find your own RPC https://solana.com/rpc


s/ChefVaultItem/ChefVaultCookbook

Replace 'include ChefVaultItem' with 'include ChefVaultCookbook' to reflect
change in chef-vault cookbook 1.3.1
Fixes #1

@oifland Can you try to run the rspec unit tests? They fail for me. We may have to merge anyways and fix the tests in a future PR. :(


Final Project , week 1, Sunday Roll Call

Leave a comment with these two things:

A summary of your last chapter using only emojis
Something you'd like to share, anything goes! (within respect)

emoji cheat sheet

💫

:+1:

👍


thread 'main' panicked at 'attempt to subtract with overflow', src/main.rs:76:15

My Ubuntu rust packages are probably quite old. But I don't think it matters too much.
tilmanb@zuse:~/git/nat$ RUST_BACKTRACE=1 cargo run
    Finished dev [unoptimized + debuginfo] target(s) in 0.07s
     Running `target/debug/nat`
thread 'main' panicked at 'attempt to subtract with overflow', src/main.rs:76:15
stack backtrace:
   0: backtrace::backtrace::libunwind::trace
             at /usr/src/rustc-1.43.0/vendor/backtrace/src/backtrace/libunwind.rs:86
   1: backtrace::backtrace::trace_unsynchronized
             at /usr/src/rustc-1.43.0/vendor/backtrace/src/backtrace/mod.rs:66
   2: std::sys_common::backtrace::_print_fmt
             at src/libstd/sys_common/backtrace.rs:78
   3: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
             at src/libstd/sys_common/backtrace.rs:59
   4: core::fmt::write
             at src/libcore/fmt/mod.rs:1063
   5: std::io::Write::write_fmt
             at src/libstd/io/mod.rs:1426
   6: std::sys_common::backtrace::_print
             at src/libstd/sys_common/backtrace.rs:62
   7: std::sys_common::backtrace::print
             at src/libstd/sys_common/backtrace.rs:49
   8: std::panicking::default_hook::{{closure}}
             at src/libstd/panicking.rs:204
   9: std::panicking::default_hook
             at src/libstd/panicking.rs:224
  10: std::panicking::rust_panic_with_hook
             at src/libstd/panicking.rs:470
  11: rust_begin_unwind
             at src/libstd/panicking.rs:378
  12: core::panicking::panic_fmt
             at src/libcore/panicking.rs:85
  13: core::panicking::panic
             at src/libcore/panicking.rs:52
  14: nat::main
             at src/main.rs:76
  15: std::rt::lang_start::{{closure}}
             at /usr/src/rustc-1.43.0/src/libstd/rt.rs:67
  16: std::rt::lang_start_internal::{{closure}}
             at src/libstd/rt.rs:52
  17: std::panicking::try::do_call
             at src/libstd/panicking.rs:303
  18: __rust_maybe_catch_panic
             at src/libpanic_unwind/lib.rs:86
  19: std::panicking::try
             at src/libstd/panicking.rs:281
  20: std::panic::catch_unwind
             at src/libstd/panic.rs:394
  21: std::rt::lang_start_internal
             at src/libstd/rt.rs:51
  22: std::rt::lang_start
             at /usr/src/rustc-1.43.0/src/libstd/rt.rs:67
  23: main
  24: __libc_start_main
  25: _start
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
permissions   size      last modified       grouptilmanb@zuse:~/git/nat$

tilmanb@zuse:~/git/nat$ git log -n 1
commit 6d34b3c80b77f94e2f076158affcb8e6ba8d9b04 (HEAD -> main, origin/main, origin/HEAD)
Author: Will Lane<EMAIL_ADDRESS>Date:   Fri Oct 23 00:29:00 2020 -0700

    updated colors for users using lighter terminal themes

tilmanb@zuse:~/git/nat$ rustc --version
rustc 1.43.0

My rust foo is very weak and I didn't have tome to dig into it. But perhaps you want to know.
Feel free to just close the ticket.

Having a group length smaller than 8 causes this integer underflow in the following line.
https://github.com/willdoescode/nat/blob/6d34b3c80b77f94e2f076158affcb8e6ba8d9b04/src/main.rs#L76
It crashes the software in debug mode and causes many underlined prints in release mode.

I am adding a fix to this right now

should be fixed now. let me know if you have any issue with the latest release.

on the most recent commit in main i get the following output:
➜ cargo build && cargo run
    Finished dev [unoptimized + debuginfo] target(s) in 0.04s
    Finished dev [unoptimized + debuginfo] target(s) in 0.02s
     Running `target/debug/nat`
thread 'main' panicked at 'attempt to subtract with overflow', src/main.rs:58:25
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.
permissions   size      last modified       group%

this should be fixed in the latest release


Add Taking a Course Project to Publication

Added blog post from a student team successful at taking their course project to the ACM conference.
https://github.com/fusical/emotiw
https://dl.acm.org/doi/10.1145/3382507.3417966
Co-authored-by: Leila Abdelrahman<EMAIL_ADDRESS>Co-authored-by: Tom Jin<EMAIL_ADDRESS>Co-authored-by: Amil Khanzada<EMAIL_ADDRESS>Co-authored-by: Cong Kevin Chen<EMAIL_ADDRESS>

https://practical-wilson-b29edf.netlify.app/choose-project/


IOT : Arduino code to blink LED without using delay() function

Pls assign this once the PR is merged @orvil1026 @csendranshi

The PR #111 has been merged but I forgot to link issue #102 to it. I am closing issue #102 .


Auto-upgrade to <IP_ADDRESS>

Base PullRequest
default branch (https://github.com/http4k/http4k-connect/tree/master)
Command results

Details:

add path
/home/runner/work/_actions/technote-space/create-pr-action/v2/node_modules/npm-check-updates/build/src/bin

./upgrade_http4k.sh <IP_ADDRESS>

Changed files

Changed file:

gradle.properties

:octocat: Repo | :memo: Issues | :department_store: Marketplace

Codecov Report

Merging #180 (e756fe8) into master (4aa5f65) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #180   +/-   ##
=========================================
  Coverage     65.49%   65.49%
  Complexity      808      808
=========================================
  Files           415      415
  Lines          4820     4820
  Branches        426      426
=========================================
  Hits           3157     3157
  Misses         1419     1419
  Partials        244      244

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


[flutter_tools] RPCError: removeBreakpoint: (-32602) invalid breakpoint id

#3 crasher on stable/3.3.0
with command: flutter debug_adapter
RPCError: removeBreakpoint: (-32602) invalid breakpoint id bp/5532#98:0
at new _OutstandingRequest(vm_service.dart:1746)
at VmService._call(vm_service.dart:2262)
at VmService.removeBreakpoint(vm_service.dart:2127)
at IsolateManager._sendBreakpoints.<anonymous closure>(isolate_manager.dart:633)
at Future.forEach.<anonymous closure>(future.dart:646)
at Future.doWhile.<anonymous closure>(future.dart:703)
at _rootRunUnary(zone.dart:1399)
at _CustomZone.runUnary(zone.dart:1300)
at _CustomZone.runUnaryGuarded(zone.dart:1209)
at _CustomZone.bindUnaryCallbackGuarded.<anonymous closure>(zone.dart:1246)
at _rootRunUnary(zone.dart:1399)
at <asynchronous gap>(async)
at _CustomZone.bindUnaryCallbackGuarded.<anonymous closure>(zone.dart:1246)
at <asynchronous gap>(async)

Stable 3.3.0 uses dds version 2.2.5: https://github.com/flutter/flutter/blob/stable/packages/flutter_tools/pubspec.yaml#L13

@christopherfujino hmm, unsure. It looks like the code was written to avoid races and I can't see any obvious path. How often is this occurring? Is it across all platforms? I'll see if I can trigger it. If you see anyone report that they can repro this, I'd be very interested in a log file (captured with the Capture Debugging Logs command).
I enabled SDK DAPs for ~10% of users in the last Dart-Code release. If this is happening lots we can push an update to Dart-Code to revert that until we have a fix.

invalid breakpoint id bp/5532#98:0

Also - do you know if all instances of this have IDs that start bp/. It looks like VM breakpoints starts with "breakpoint" and when using Chrome/DWDS it's bp/, so I wonder if it's web-specific (although I haven't been able to repro there either yet).

I think I've managed to trigger this running in iOS Simulator (so not web), however it doesn't crash it seems to be handled. What I did was add two breakpoints that resolve to the same line (a line of code, and the blank line before it).
The VM returns the same breakpoint ID from the second request to add a breakpoint (although to complicate things, it seems like this only happens if the code has been run previously and compiled - it seems to return a new breakpoint if not), and we blindly keep track of it as a second breakpoint. When we come to remove the breakpoints, we then try to remove it twice (but after the first removal, the ID is not longer valid).
The fix for that is fairly simple, but I can't repro via web (a breakpoint on the blank line is entirely rejected) so I'll continue to see if I can understand how it happened above before fixing.
For reference, my steps to reproduce (which triggers an error if recording logs, but does not crash for me):

Create counter app
Add a blank line above _counter++
Run Capture Debugging Logs to start logging
Run the app on iOS Simulator
Click the button so that the counter increment runs
Add a breakpoint to the blank line
Add a breakpoint to _counter++
Remove the first breakpoint
Remove the second breakpoint
Click Cancel to open the log file

In the log file, find the last instance of removeBreakpoint and there's an error recorded where it failed to remove (because it was already previously removed). This error is silent to the user though (and does not crash the tool).

Based on this code it looks like breakpoint IDs for web are always scriptid/line/col (the example above was bp/5532#98:0). So adding a breakpoint on a different line that happens to resolve to the same location doesn't seem like it will work for web.
Other thoughts:

We somehow had two isolates live when this happened, so we tried to remove the same breakpoint twice (web only has one isolate, but I think during a restart it may exit and a new one be produced, so maybe something happened there)
We had two files open in VS Code that somehow represented the same script ID, so we had the ID reused that way

(None of this explains why it was a crash in that instance, but perhaps when this occurred the original call had a different call stack to my repro, one that doesn't handle errors?)

(@christopherfujino sorry for the noisy notifications 🙃)
I'm still unable to reproduce this, but I am now convinced there are some races and we just need error handling around this:

It's not the issue for web, but removing a breakpoint for an isolate that has gone will fail. This means that whatever we do in the debug adapter, there is always a change that right after we start sending a removeBreakpoint call to the VM, the isolate exited. This means we can never assume it will always pass (and therefore, we need to handle errors when calling removeBreakpoint, exactly like we already do with the subsequent addBreakpoint calls)
When a breakpoint exits, even if we get the event before we try to update any breakpoints, there are awaits in the processing of the exit event (for ex. we need to ensure any initialisation of the isolate completes before we try to clean it up), so there's always an opportunity for another request from the client that modifies breakpoints to try and get in there.

I'm not certain, but I suspect the issue above is triggered by the second. Maybe some timing of a restart (which pretends to terminate and re-create an isolate on web) and breakpoint update overlapped and triggered this.
I'll get a fix into DDS. If this issue is occurring frequently and you think we should roll back the 10% of users on the new DAPs until this fix is shipped, let me know.

(@christopherfujino sorry for the noisy notifications upside_down_face)
I'm still unable to reproduce this, but I am now convinced there are some races and we just need error handling around this:

It's not the issue for web, but removing a breakpoint for an isolate that has gone will fail. This means that whatever we do in the debug adapter, there is always a change that right after we start sending a removeBreakpoint call to the VM, the isolate exited. This means we can never assume it will always pass (and therefore, we need to handle errors when calling removeBreakpoint, exactly like we already do with the subsequent addBreakpoint calls)
When a breakpoint exits, even if we get the event before we try to update any breakpoints, there are awaits in the processing of the exit event (for ex. we need to ensure any initialisation of the isolate completes before we try to clean it up), so there's always an opportunity for another request from the client that modifies breakpoints to try and get in there.

I'm not certain, but I suspect the issue above is triggered by the second. Maybe some timing of a restart (which pretends to terminate and re-create an isolate on web) and breakpoint update overlapped and triggered this.
I'll get a fix into DDS. If this issue is occurring frequently and you think we should roll back the 10% of users on the new DAPs until this fix is shipped, let me know.
Edit: CL at https://dart-review.googlesource.com/c/sdk/+/257962/.

Thanks for the quick fix!

I think this was closed accidentally by the SDK change being pushed to a repo. Re-opening until the DDS change is in Flutter.

I think this was closed accidentally by the SDK change being pushed to a repo. Re-opening until the DDS change is in Flutter.

Thanks

Interesting @DanTup I did not close this manually, I wonder if this was due to the recent roll.

Yeah, it was GitHub. I think you pushed to your sdk fork on GitHub (https://github.com/itsjustkevin/sdk) which included my commit that has the fix in DDS (https://github.com/itsjustkevin/sdk/commit/94a64a01f630e4a96b6b3cf3ec3c9a6b3f5f3445). GitHub saw my commit message (which contains "fixes ") and since you have access to close this issue, assumed a fix had been merged (you can close issues in Repo A from Repo B.. it doesn't seem to matter whether Repo B is just a fork or not).
I don't know why it didn't happen when the SDK is synced up to the official repo (the same commit already existed at https://github.com/dart-lang/sdk/commit/94a64a01f630e4a96b6b3cf3ec3c9a6b3f5f3445), but I should be more careful with my commit messages (I was only thinking about Gerrit when I pushed it 😄).
(I've accidentally closed several of issues this way - and sometimes I've only noticed because people pinged me afterwards 😬)

Interesting @DanTup I did not close this manually, I wonder if this was due to the recent roll.

I think it's because the CL noted "Fixes flutter/flutter#111045", and maybe your fork picked up this commit before copybara to dart-lang/sdk?

cc @ iinozemtsev

Update on this issue:

@DanTup published a new version of dart-code that stops the experiment using flutter debug-adapter, so only users explicitly using it from the command line should be affected. This will be re-enabled once the upstream dds fix is rolled to Flutter stable.
The upstream DDS fix was landed in https://github.com/dart-lang/sdk/commit/94a64a01f630e4a96b6b3cf3ec3c9a6b3f5f3445

This issue can be closed once:

a new version of DDS has been published
this version has been autorolled to the framework.

Regarding publishing a new version of DDS, @bkonyi could you do that?

so only users explicitly using it from the command line should be affected

To be clear, I wouldn't expect any users to be explicitly running this command from the command line - though perhaps you mean users that have configured other (non-VS Code) clients to spawn the debug adapter using the flutter debug_adapter command.

This will be re-enabled once the upstream dds fix is rolled to Flutter stable.

My plan is to re-enable it based on the version of the SDK once it rolls into Flutter, so that master/beta users will have it re-enabled (if they have the updated DDS) sooner than a stable release, just to help get additional testing/validation before then.
@christopherfujino out of interest, has there been a significant reduction in the number of crash reports since the original influx?

@christopherfujino I'll publish a new DDS today once this CL lands.

DDS v2.3.0 has been published.

@DanTup I don't see a single report on the latest 3.3.2 stable!

DDS v2.3.0 has been published.

I will now close this issue as the upstream patch has been rolled to the framework. Thanks all!


Horizontal Scrolling Reversed

On windows, in the bevy 0.9 version of this crate, horizontal scrolling is flipped. This was originally an issue in egui, which we had to fix upstream in winit: https://github.com/emilk/egui/issues/965
I haven't had the time to fully debug this yet, but it appears scrolling works as expected in egui, so something is being flipped in this crate.

https://github.com/mvlabat/bevy_egui/pull/159/files#diff-420f4e08a25299e0e1fb09f4757e1d5d027a2278f37030c09ab9c06786cfa52eL224
This should be already fixed in 0.10. Do you want it backported to 0.9?

Ah, I missed this. I appreciate the offer, but nope, I'll be able to upgrade eventually.
Thanks!


Stress-test HystrixObservableCollapser

Hystrix-pull-requests #263 FAILURE
Looks like there's a problem with this pull request

NetflixOSS » Hystrix » Hystrix-pull-requests #24 SUCCESS
This pull request looks good

Didn't see a problem with test that failed as part of #368


Disable a validation test that is currently failing until we have a

chance to investigate.

@swift-ci Please smoke test

@atrick FYI, disabling this for the moment.

Superseeded by
https://github.com/apple/swift/pull/18058


Check error code rather than custom implement get_string

JFYI: you can check error code if you want a better errors so I made example of get_string

I appretiate your work on this.
It's a good idea to minimize re-implementing stuff that already exists; however I don't think this is a reliable way to handle errors. The problem is that the error codes ERROR_INVALID_FLAGS and ERROR_INVALID_PARAMETER are very generic and they can come from many different winapi functions. I understand that using the current implementation, this is correct, but the clipboard_win::get(clipboard_win::Unicode) function-call gives me no guarantees that this is not going to change in a future release. And if it does change, I get no warnings or errors, the code will just compile without me knowing that it's incorrect.

Ok, this code has no need to change (as it is the only way to get unicode string) but your concern is valid


feat(levm): implement precompile blake2f

Motivation
The goal is to implement the blake2f precompile.
Description
The blake compressing functionality is based on RFC 7693.
There are some related EF tests not passing, I left a commented test that simulate one of those cases. The test cases that do not pass are from stPreCompiledContracts/blake2B.json.

Have you tried using a rust crate like Blake2. Couldn't that get some of the complexity out of the way here?

I feel like some of the errors propagated should actually be internal errors if they are not intended to happen independently of the input received.

Have you tried using a rust crate like Blake2. Couldn't that get some of the complexity out of the way here?

I tried to use related crates, but I couldn't find one that does what we specifically need. The functionality is similar to the functionalities that are related to the Blake2 algorithm, but this one is more configurable than the others, since it receives parameters that the others do not.


incorrect peer dependencies - React 17 Support

Running my e2e tests using cypress I get the following warnings in my CLI. I'm on v1.1.1. Is there any way to fix these? It's really annoying to see a ton of warnings.
warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>|| ^6.0.0".
warning "@react-theming/storybook-addon ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "@react-theming/storybook-addon ><EMAIL_ADDRESS>has incorrect peer dependency "<EMAIL_ADDRESS>warning "@react-theming/storybook-addon ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "@react-theming/storybook-addon ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "@react-theming/storybook-addon ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^15.5.4".
warning "@react-theming/storybook-addon ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^15.5.4".
warning "@react-theming/storybook-addon > @storybook/addon-devkit ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "@react-theming/storybook-addon > @storybook/addon-devkit ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "@react-theming/storybook-addon > @usulpro/react-json-view ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS><17.0.0".
warning "@react-theming/storybook-addon > @storybook/addon-devkit > @reach/rect ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "@react-theming/storybook-addon > @storybook/addon-devkit > @reach/rect ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "@react-theming/storybook-addon > @storybook/addon-devkit > @storybook/addons > @storybook/api > @reach/router ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0".

It would be nice if this could get updated to use latest react

Sure @CWSites I think we can do it safely! Fell free to add a PR for that. It will be really appreciated!

Sure @CWSites I think we can do it safely! Fell free to add a PR for that. It will be really appreciated!

I'll do my best but extremely busy with work.

Hi, same problem here, it would be nice that addon-devkit accept<EMAIL_ADDRESS>

Same issue. Started a project with npx create-next-app npx sb init & npm i @react-theming/storybook-addon and getting the output
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@storybook/react
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!   peer<EMAIL_ADDRESS>|| ^6.0.0" from<EMAIL_ADDRESS>npm ERR!   node_modules/@react-theming/storybook-addon
npm ERR!     @react-theming/storybook-addon@"*" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@react-theming/storybook-addon/node_modules/@storybook/addon-devkit
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@react-theming/storybook-addon
npm ERR!     @react-theming/storybook-addon@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /home/anon/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/anon/.npm/_logs/2021-08-08T17_57_15_060Z-debug.log

@UsulPro discussed with the storybook folks and they mentioned that you should no longer be using the @storybook/addon-devkit as the APIs have moved to storybook itself. See more details here: https://github.com/storybookjs/storybook/issues/16557. What are your thoughts?

@JettScythe, it looks like you're missing other peer dependencies. Can you verify that you have the following installed?

<EMAIL_ADDRESS>

@CWSites I can confirm I have the following:
        "@storybook/addon-essentials": "^6.3.6",
        "@storybook/addon-links": "^6.3.6",
        "@storybook/react": "^6.3.6",

@JettScythe thanks, I had to do the same and wasn't going to revert to an earlier version of @storybook/react. Hopefully it will get fixed soon :)

@CWSites

is there a reason that you forked react-json-view,
I had to fork it at the moment when this package wasn't maintained and the author didn't respond. Now we have an extra feature to show colors. I know the maintainer came back and updated the repo so I did a PR to the original. But it still isn't merged and I'm afraid it's outdated now.

they mentioned that you should no longer be using the @storybook/addon-devkit as the APIs have moved to storybook itself
answered there

Fixing peerDependencies in addon-devkit would be enough to solve this?

@UsulPro I believe so, would it be possible to get around the need to use addon-devkit?

Guys! I believe we can close it finally as I've updated dependencies. Let me know if there are any issues yet?

I believe this still doesn't work with React 17 because of this line. @UsulPro

Still getting the following as of latest today
warning "@react-theming/storybook-addon ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^15.5.4".
warning "@react-theming/storybook-addon ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^15.5.4".
warning "@react-theming/storybook-addon > @usulpro/react-json-view ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS><17.0.0".
warning "@react-theming/storybook-addon > @storybook/addon-devkit ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "@react-theming/storybook-addon > @storybook/addon-devkit ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "@react-theming/storybook-addon > @storybook/addon-devkit > @reach/rect ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "@react-theming/storybook-addon > @storybook/addon-devkit > @reach/rect ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>

@UsulPro see above, still a few issues here.


Bug/tilage investigation

Updated tiling to work properly.

for the midwest: if i select click tiling from somewhat poorly drained it increases to moderately well drained correctly, but if i unselect tiling it goes down two levels to poorly drained instead of back to the original somewhat poorly drained

updated conflicts and lint errors.


Add Support for ICMPv6 filters on raw sockets

Since ICMPv6 has man more message types than ICMPv4 a raw ICMPv6 socket will by default receive all the ICMPv6 messages. While it's possible to filter them all yourself it seems like it might be better to add support for the ICMPv6 filters as referenced here: https://tools.ietf.org/html/rfc2292#section-3.2 I believe windows has a similar facility as well.

Socket2 doesn't implement the RFC itself, it's a wrapper around system calls. So if the OSs provide a way to filter ICMP packets feel free to open a pr to add this.

Socket2 doesn't implement the RFC itself, it's a wrapper around system calls. So if the OSs provide a way to filter ICMP packets feel free to open a pr to add this.

Due to the lack of progress I'm going to close it. Any more discussion or contributions are of course always welcome.


Feature Request: CRD for HumioViews

It would be awesome to be able to manage views in Humio through a custom resource, e.g. HumioView.

@jswoods @SaaldjorMike are you planning on implementing this one anytime soon? Otherwise, we would like to take a stab at it. 👍

@kaspernissen I don't think we are close to starting the work on this soon, at least not for multiple weeks. Most of the focus has been on the HumioCluster resource type.
As for adding support for views, we may need to extend the api package in humio/cli project in case what we need is not available right now to add support for views.

Yes, it looks like it's read-only at the moment with Get and List.
We will have a look at it, it should be fairly simple to add support for it as the graphql already has support creating views, right?

We will have a look at it, it should be fairly simple to add support for it as the graphql already has support creating views, right?

That would be my expectation yes, at least as long as we keep RBAC out of the picture. Right now repositories created by the operator does not allow you to specify what users/groups gets access to the repository, and I suppose we could consider skipping RBAC for views in the first iteration as well. I guess it all depends on the amount of work that is required to make RBAC work.

Hi. I have forked the repository and have begun working on it in collaboration with @kaspernissen.
@SaaldjorMike You are right. The cli needs an update which is where we will start.


OCMock 3.1.3 can't install on projects deploying for less than iOS 8.2

Hi @erikdoe ,
The new podspec configuration: s.ios.deployment_target = '8.2'
Means min version of iOS 8.2. (http://guides.cocoapods.org/syntax/podspec.html#deployment_target)
It can not install for projects supporting iOS 8.0 or 8.1 either.
Is this on purpose?
Thank you,
Amir

Apologies. This was not the intention. There was an issue with publishing the pod (#224), and what you are seeing seems to be a side effect of the fix (#226). Looks like we have to solve it in a different way.
For the next few days I won't have access to a computer, but if anyone has an idea how to solve #224 in a better way please share it so that I can get a new release out quickly. Please DO NOT send a PR against master. That has moved on adding new features that shouldn't be in a small fix release.

I can give it a shot. What is the minimum versions you would like to support?

Okay. I've just pushed OCMock 3.1.4 to the spec repo. There was a bit of guesswork involved because the documentation for CocoaPods wasn't all too clear on how to support multiple platforms (https://guides.cocoapods.org/syntax/podspec.html#platform). It should work, though. Please re-open THIS issue if it doesn't.

So, looking at the published pod this didn't work either. I've now tried the original workaround with a different deployment target, and I've filed an issue with CocoaPods (CocoaPods/CocoaPods#4075).

Thanks. I think this should work(as far as I understood cocoa pods syntax).
I'll give it a try in a few days. I don't have access to my computer.

@erikdoe it works know. Thanx.


Connection to clusters with external kubeconfig files lost after upgrade to 5.0.0

Describe the bug
Ability to connect to clusters through external kubeconfig files broken in 5.0.0
To Reproduce
Steps to reproduce the behavior:

Dialog displayed offering to upgrade to latest version 5.0.0.  No warning that accepting will lose all connectivity to clusters if using external kubeconfig files.
Click to upgrade.
After restart with 5.0.0 previous clusters are shown in "hotbar" but saying "unknown".  Clusters can be added but only with copy-paste content (and with warning that clusters will not be merged into .kubeconfig) and not by accessing existing files.
%AppData%/Roaming/Lens/lens-cluster-store.json still contains cluster setups with correct "kubeConfigPath", and the kubeconfig file still exists and with correct content.

Expected behavior

Support for multiple external kubeconfigs should be supported (I don't want or need cloud sync of single kubeconfig file).
Failing that at the very least a strong warning that connectivity will be lost should be displayed before upgrade when external kubeconfig files are configured.

Environment (please complete the following information):

Lens Version: now 5.0.0
OS: Windows
Installation method (e.g. snap or AppImage in Linux): in-app upgrade from previous version.

Logs:
When you run the application executable from command line you will see some logging output. Please paste them here:
info: ≡ƒôƒ Setting Lens as protocol client for lens://
info: ≡ƒôƒ Protocol client register succeeded Γ£à

Kubeconfig:
Quite often the problems are caused by malformed kubeconfig which the application tries to load. Please share your kubeconfig, remember to remove any secret and sensitive information.
n/a - previous configs worked fine in v4.x, current kubeconfigs are not even processed

Additional context
none, but need access to clusters via lens asap.

Digging further and comparing old (not working) and new entries created by copy-paste in %AppData%/Roaming/Lens/lens-cluster-store.json it seems the difference between the entries is minimal, and only that old entries have:
"kubeConfigPath": "C:\\Users\\{ME}\\.kube-lens\\k8s-pp-blue-sa.config"

New ones have:
"kubeConfigPath": "C:\\Users\\{ME}\\AppData\\Roaming\\Lens\\kubeconfigs\\60909c42-e3f4-4877-8d5d-e0c453d9e425"

So a guid rather than named filename and a different path.  Not sure that would stop it being loaded though, unless new entries have extra supporting records elsewhere?
If so, ofc the relevant entries should be created by migration on install of v5.0.0 imho.

Still no idea why current configs aren't working as they show up in sidebar, but if anyone else reads this, following advice on slack, the solution is to add files (or directories) containing external kubeconfig files as a "Kubeconfig sync" under the "Kubernetes" tab of preferences in v5.x
Fix is apparently slated for v5.0.1


Add filter to FileDialog Lbrary entry

We should demonstrate the usage of filter in the Open File library entry
  text_files = gtk_file_filter_new ();
  gtk_file_filter_set_name (text_files, _("Text Files"));
  gtk_file_filter_add_mime_type (text_files, "text/plain");
  gtk_file_filter_add_mime_type (text_files, "application/x-zerosize");
  gtk_file_chooser_add_filter (GTK_FILE_CHOOSER (native), g_object_ref (text_files));

Hey @sonnyp can you tell me the expected behavior of Open File cause it is showing error when i select open file

and open multiple files just logs the number of file selected .

okay but open file is supposed to open the selected image or file or just log it in console?

@sonnyp

Removed initial_folder and default_folder. https://gist.github.com/Sahil-Shadwal/6d63af8c237bf069e4ed7af7026a5790

So, should i make PR first and get my code reviewed or after ?

hey do i need to add more filters ?


Does every process loads a copy of data?

This issue is to confirm whether each process loads a copy of data into the memory in multiprocessing_train, which may consume too much memory when the dataset is huge , or there are some tricks I missed.
Thanks a lot!

Thats true, although we have a working prototype right now that eliminates this problem. It should be available for everyone soon

Ok, I got it. Thanks for your help!