revise peripheral API

This PR changes the signature of many of the high level methods available on peripherals like
NVIC::get_priority. Additionally some instance methods have been turned into static methods. The
following guidelines have been used to apply the changes:

If the method body contains a single, atomic read operation with no side effects (e.g. the read
operation clears one of the bits of the register): the signature changed to make the method
static, i.e. &self was removed from the signature.

If the method involves writing to or a RMW operation on a register: the signature changed to take
the singleton by &mut self reference.

If the method involves only read operations where at least one of them modifies the value
of a register: the signature changed to take the singleton by &mut self reference.

The rationale for this last guideline is that using &self, instead of &mut self, lets the user
(unintentionally) break abstractions in the presence of generators. Example below:
let peripherals = Peripherals::take().unwrap();
let syst = &peripherals.SYST;

// tasks
let mut a = || {
    loop {
        // yielding "busy wait"
        while !a.has_wrapped() {
            yield;
        }

        // do stuff
    }
};

let mut b = || {
    // ..

    // *NOTE* the problem is in the line below: this `is_counter_enabled` method reads the CSR
    // register and that read operation clears the COUNTFLAG bit of the register (if set), which is
    // the bit the `has_wrapped` method checks for.
    if syst.is_counter_enabled() {
        // ..
    }

    // ..
};

One more guideline was considered but the required conditions didn't apply to any of the existing
methods:

If the method involves only non side effectful, non necessarily atomic read operations: the
signature of the method should remain as &self.

The rationale for this guideline is that a static method (no self argument) wouldn't be
appropriate because that can result in a torn read if the read operation can be preempted by some
context that modifies the register.
In any case, this last guideline doesn't seem to apply well to the peripherals structs exposed by
this crate because they deref to a RegisterBlock that allows mutation through a &self
reference. When these two properties (the guideline and Deref<Target=RegisterBlock>) are mixed
the user can potentially break abstractions using generators (as shown in the syst example).
cc @hannobraun
closes #67

:umbrella: The latest upstream changes (presumably #71) made this pull request unmergeable. Please resolve the merge conflicts.


Details request

For NuScenes dataset, I see this in the readme.md file

Pre-processing: we follow the data pre-processing in SECOND to prepare the nuscenes_info file, including nuscenes_infos_train.pkl, nuscenes_infos_val.pkl and nuscenes_infos_test.pkl.

Can someone please help me understand how this files are created? is there another repository with the code ref to generate this files?

Did you figure out?

Negative @YEOMJINSEOP


Add IRC

Open source messaging protocol.

https://github.com/davisonio/awesome-irc
IRC is an open source messaging protocol. This is a list that curates the clients, servers and other resources you can use with IRC.
By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Reviewed #1591 and #1590.

Adheres to all requirements.
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration.
You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List.

✅ Add Swift
✅ Add Software Architecture
❌ Update readme.md
❌ Add Awesome Swift
❌ Add swift
❌ Adding Swift
❌ Added Swift

Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.

✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
✅ - [Framer](…) - Prototyping interactive UI designs.
❌ - [iOS](…) - Resources and tools for iOS development.
❌ - [Framer](…)
❌ - [Framer](…) - prototyping interactive UI designs

Your entry should be added at the bottom of the appropriate category.
The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
Includes a succinct description of the project/theme at the top of the readme. (Example)

✅ Mobile operating system for Apple phones and tablets.
✅ Prototyping interactive UI designs.
❌ Resources and tools for iOS development.
❌ Awesome Framer packages and tools.

It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
The repo name of your list should be in lowercase slug format: awesome-name-of-list.

✅ awesome-swift
✅ awesome-web-typography
❌ awesome-Swift
❌ AwesomeWebTypography

The heading title of your list should be in title case format: # Awesome Name of List.

✅ # Awesome Swift
✅ # Awesome Web Typography
❌ # awesome-swift
❌ # AwesomeSwift

Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate. Please search for existing submissions.
Only has awesome items. Awesome lists are curations of the best, not everything.
Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.

Can be placed centered if the list has a centered graphics header.

Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.

Has an appropriate license.

That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
WTFPL and Unlicense are not acceptable licenses.
If you use a license badge, it should be SVG, not PNG.
To verify that you've read all the guidelines, please add comment with just the word unicorn.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.
Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

Unicorn!

Awesome list but there are several issues as per awesome-lint. You might wanna fix them.
❯ awesome-lint https://github.com/davisonio/awesome-irc
✖ Linting

  readme.md:217:137
  ✖    1:1    License was not detected by GitHub                            remark-lint:awesome/github
  ✖    7:1    Multiple Table of Contents lists found                        remark-lint:awesome/toc
  ✖   32:4    Invalid list item link                                        remark-lint:awesome/list-item
  ✖   33:4    Invalid list item link                                        remark-lint:awesome/list-item
  ✖   34:4    Invalid list item link                                        remark-lint:awesome/list-item
  ✖   35:4    Invalid list item link                                        remark-lint:awesome/list-item
  ✖   36:4    Invalid list item link                                        remark-lint:awesome/list-item
  ✖   37:4    Invalid list item link                                        remark-lint:awesome/list-item
  ✖   38:4    Invalid list item link                                        remark-lint:awesome/list-item
  ✖   39:4    Invalid list item link                                        remark-lint:awesome/list-item
  ✖   40:4    Invalid list item link                                        remark-lint:awesome/list-item
  ✖   41:149  List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖   42:4    Invalid list item link                                        remark-lint:awesome/list-item
  ✖   43:4    Invalid list item link                                        remark-lint:awesome/list-item
  ✖   44:4    Invalid list item link                                        remark-lint:awesome/list-item
  ✖   45:4    Invalid list item link                                        remark-lint:awesome/list-item
  ✖   46:4    Invalid list item link                                        remark-lint:awesome/list-item
  ✖   47:4    Invalid list item link                                        remark-lint:awesome/list-item
  ✖   48:4    Invalid list item link                                        remark-lint:awesome/list-item
  ✖   49:4    Invalid list item link                                        remark-lint:awesome/list-item
  ✖   50:4    Invalid list item link                                        remark-lint:awesome/list-item
  ✖   51:4    Invalid list item link                                        remark-lint:awesome/list-item
  ✖   61:4    Invalid list item link                                        remark-lint:awesome/list-item
  ✖   62:60   List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖   63:68   List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖   64:85   List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖   65:4    Invalid list item link                                        remark-lint:awesome/list-item
  ✖   69:4    Invalid list item link                                        remark-lint:awesome/list-item
  ✖   70:4    Invalid list item link                                        remark-lint:awesome/list-item
  ✖   71:4    Invalid list item link                                        remark-lint:awesome/list-item
  ✖   72:4    Invalid list item link                                        remark-lint:awesome/list-item
  ✖   73:4    Invalid list item link                                        remark-lint:awesome/list-item
  ✖   83:96   List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖   99:139  List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  100:116  List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  101:85   List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  102:96   List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  103:124  List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  104:83   List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  105:45   List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  106:192  List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  107:78   List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  108:54   List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  109:84   List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  110:83   List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  111:104  List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  112:101  List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  118:51   List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  119:88   List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  120:93   List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  121:89   List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  122:69   List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  123:88   List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  124:119  List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  125:169  List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  132:77   List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  133:69   List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  134:73   List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  135:159  List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  136:68   List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  137:64   List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  138:86   List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  139:75   List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  140:137  List item description must end with proper punctuation        remark-lint:awesome/list-item
  ✖  154:46   List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  155:65   List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  159:51   List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  210:3    Invalid list item link                                        remark-lint:awesome/list-item
  ✖  211:3    Invalid list item link                                        remark-lint:awesome/list-item
  ✖  217:137  Link to https://twitter.com/davisonio is dead                 remark-lint:no-dead-urls

  70 errors

awesome-lint unfortunately brings up many false positives. Since we use icons in front of list items and we include a source code link after the description. (Invalid list item link) (List item description must end with proper punctuation).
License is included and there's a table of contents

The link icons needs to be high-DPI (set to half their real size).

A curated list of awesome IRC resources.

I don't think awesome should be linkified here.

Includes a succinct description of the project/theme at the top of the readme. (Example)

The link icons needs to be high-DPI (set to half their real size).

For now have removed until we can do this

I don't think awesome should be linkified here.

Removed

Includes a succinct description of the project/theme at the top of the readme. (Example)

Added!
Anything else?

Komanda](komanda.io) - Designed for people who write code (beta). (source) Linux

The link syntax here is broken.

Tweet: https://twitter.com/awesome__re/status/1163172150213316608


Dioxus-cli ignores env variables in .cargo/config.toml

Problem
In my project I have defined env variables for the server (database URL etc) in .cargo/config.toml file and if I run the fullstack app with cargo run --features server the environment is correctly set up. However, if running it with dx serve, none of the env variables are set.
Steps To Reproduce
Steps to reproduce the behavior:

create a .cargo/config.toml with an [env] section and define some environment variables
run the project wth dx serve
the env variables are not set for the server executable

Expected behavior
Should work the same as cargo run
Environment:

Dioxus version: 0.5.4 (cli)
Rust version: 1.76
OS info: Win11 WSL2 Ubuntu
App platform: fullstack

#2259 might be related

Yes, it looks like the same issue. I'm going to close this in favor of #2259 and PR #2372. Thanks for the report!


SubmitField is always False

I want to have multiple submit buttons on a form and check in views.py for which was clicked.
But all the form..data values are always False.
The Form:
class DomainForm(FlaskForm):
    domain = StringField('Domain', validators=[Length(min=3, max=255)])
    submitadd = SubmitField('Add domain')
    submitcancel = SubmitField('Cancel')

The views.py contains:
@domains.route('/domains_add/',  defaults={'domaintype': 'local'}, methods=['GET', 'POST'])
@login_required
def domains_add(domaintype):
#...
    form = DomainFormLocal(obj=domain)
    print(form.submitadd.__dict__)
    print(form.submitcancel.__dict__)
    if form.submitcancel.data:
        return 'cancel was clicked'
#...

In the log i always get following. No matter which button was clicked:
{'default': None, 'process_errors': [], 'id': 'submitadd', 'render_kw': None, 'short_name': 'submitadd', 'type': 'SubmitField', 'name': 'submitadd', 'meta': <wtforms.form.Meta object at 0x7f414b21a5c0>, 'description': '', 'validators': [], 'label': Label('submitadd', 'Add domain'), 'object_data': None, 'flags': <wtforms.fields.Flags: {}>, 'filters': (), 'data': False}
{'data': False, 'meta': <wtforms.form.Meta object at 0x7fb09f521710>, 'label': Label('submitcancel', 'Cancel'), 'render_kw': None, 'flags': <wtforms.fields.Flags: {}>, 'filters': (), 'process_errors': [], 'default': None, 'short_name': 'submitcancel', 'id': 'submitcancel', 'validators': [], 'object_data': None, 'type': 'SubmitField', 'description': '', 'name': 'submitcancel'}

I can't reproduce your issue.
Please use Stack Overflow for questions about your own code. This tracker is for issues related to the project itself. Be sure to include a minimal, complete, and verifiable example.

I have the exact same issue.

Same issue here. Any one found a solution.

I've started running into this issue on 2.3.1. Would have been useful to see if the other comments hinted towards a solution.

running into this too

I agree with mrkmcknz that I'd like to see what others have said, I have been spending days trying to get two submit buttons to work with flask-wtforms for a single form, to no avail. I have tried every hint and trick I could find on Stack Overflow.
Both form.submit_button_1.data and form.submit_button_2.data always returns False, no matter which submit button was hit. I'm using Flask-WTF version 0.14.3

i came up with the following. (full code: https://gitlab.com/runout/veximpy)
but i have some more logic to handle fields which should not be visible in some cases. maybe this could/should be done in a better way (suggestions are welcome in the issue tracker of veximpy).
in the form (app/accounts/form.py):
    submitedit = SubmitField('Save account')
    submitcancel = SubmitField('Cancel', render_kw={'formnovalidate': True})

in the view (app/accounts/view.py):
    if form.submitcancel.data:
        return redirect(url_for('accounts.accountlist', domainid=account.domain_id, _anchor=accountid, accounttype=accounttype))

I'm also facing this issue on 2.3.3.  I've tried all the so-called "solutions" I could find on Stack Overflow to no avail.


Auto refresh

Suggestion: Auto refresh list os remote files when i delete a file

i hope this feature integrated, maybe active refresh configuration like :
"autorefresh" : 10 //10seconds


chore: update to newest version of each submodule

Update all submodules to newest version.

Hi @Alonza0314 ,
You need to enter test/ and run go mod tidy.

Hi @Alonza0314 ,
You need to enter test/ and run go mod tidy.

Oh! I see, that's exactly what I’m working on right now.


"invalid start of a value" when trying to translate

Describe the bug
We've are using the package in our WinForm app using Telerik 2023.2.60653, .Net Framework 4.7.2, package latest 1.7.1
I have developed a feature where a user can select which language it wants to translate to, in our case English or Hungarian
Lets say we have posts, and each post can have comments, when the user wants to translate, we translate all the comments.
When translating to English it goes well, no problem, but when I want to translate to Hungarian (does not matter if the original language is Hungarian or not) I get the error showed below. Whether I translate to English first or second I get the same result
I've been trying to reproduce the problem in a console app, but simply unable to do so, even our users have different experience, some reported that they get the error on the first try.
We use HTML to display the comments, we use CefSharp to display a chromium browser inside the WinForm app.
Update 1:
For me it does not matter if I do translate fast with 1-2 secs between the two requests or wait 1-2 minutes, basically every second request gets this error, whether I start with English or Hungarian.
My colleagues experience difference if they wait a certain amount of time or not.
I've tried to make demos which I could upload here making your jobs easier, but I can not make it fail...
Somehow it fails in our app, but when I make a mini environment which represents our app, with the same code which makes the API call, I cant make it to fail as it does in our app
Expected behavior
We get back the translation no problem

Stack trace:

at System.Text.Json.ThrowHelper.ReThrowWithPath(ReadStack& state, JsonReaderException ex)
at System.Text.Json.Serialization.JsonConverter1.ReadCore(Utf8JsonReader& reader, JsonSerializerOptions options, ReadStack& state) at System.Text.Json.JsonSerializer.<ReadAsync>d__201.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at DeepL.Internal.JsonUtils.d__41.MoveNext() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at DeepL.Internal.JsonUtils.<DeserializeAsync>d__31.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at DeepL.Translator.d__8.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at Our class which inherits from UserControl.d__114.MoveNext() in the line of our cs file

Source:

System.Text.Json

Path:

$

Message:

'<' is an invalid start of a value. Path: $ | LineNumber: 0 | BytePositionInLine: 0.

Screenshots or sample code
private void button_click(object sender, EventArgs e)
{
        RadButton translateButton = (RadButton)sender;
        if (translateButton == null) return;

        string targetLanguage = translateButton.Name == "translateToHungarianButton" ? LanguageCode.Hungarian : LanguageCode.EnglishAmerican;
        string sourceLanguage = targetLanguage == LanguageCode.Hungarian ? "EN" : "HU";
        Task.Run(async () => await TranslateText(commentList, sourceLanguage ,targetLanguage ));
}
private async Task TranslateText(string[] textsToTranslate, string sourceLanguage, string targetLanguage)
{
        TextResult[] translatedTexts;
        try
        {
                translatedTexts = await translator.TranslateTextAsync(textsToTranslate, sourceLanguage, targetLanguage, new TextTranslateOptions() { TagHandling = "xml", IgnoreTags = { "a" }, PreserveFormatting = true });
        }
        catch (Exception e)
        {
                MessageBox.Show($"Error: {e}");
                throw;
        }
}

If you guys need any more info please let me know!
The problem could be solved with an easy fix, it might be my lack of knowledge

Is there a way to get a sample value for commentList that triggers this problem? Otherwise this is hard to debug due to the garbled stacktrace for the async functions (d__4 etc)

Is there a way to get a sample value for commentList that triggers this problem?

Well its nothing special, a sample:
string[] commentList = new string[]
{
"
Sziasztok!

Az FX team hétfőn egész nap csapatépít így legközelebb kedden értek majd el minket.

Köszi!
",
"
Sziasztok,

Elkezdtem régi Magyar pénz gyűjteményemet foltozgatni.(papír) Ha esetleg valakinek van ez-az és esetleg eladná, keressen meg. Köszi :)
",
"

Sziasztok,

Pénteken, azaz holnap délután az IT csapatépítőn lesz, ezért kérünk benneteket, hogy a fontos issuekkal, igényekkel lehetőleg még a ma keressetek meg minket.
",
"
the Animation Division will be on team building event on this Friday (31.March). Please contact us with any important issues by the end of Thursday.
"
};

With the simplest examples it does the same, even if the commentList contains only one element which is :
"
Hey, this is me!
"
I might have left out an important info, gonna update the post
Hope it helps somehow, if you have any further questions, please let me know!

Hm for me it also works in this toy console app (for both languages, by changing true to false).
using DeepL;

var translator = new Translator("MY_AUTH_KEY");
string[] commentList = new string[]
{
"
Sziasztok!

Az FX team hétfőn egész nap csapatépít így legközelebb kedden értek majd el minket.

Köszi!
",
"
Sziasztok,

Elkezdtem régi Magyar pénz gyűjteményemet foltozgatni.(papír) Ha esetleg valakinek van ez-az és esetleg eladná, keressen meg. Köszi :)
",
"

Sziasztok,

Pénteken, azaz holnap délután az IT csapatépítőn lesz, ezért kérünk benneteket, hogy a fontos issuekkal, igényekkel lehetőleg még a ma keressetek meg minket.
",
"
the Animation Division will be on team building event on this Friday (31.March). Please contact us with any important issues by the end of Thursday.
"
};

string targetLanguage = true ? LanguageCode.Hungarian : LanguageCode.EnglishAmerican;
string sourceLanguage = targetLanguage == LanguageCode.Hungarian ? "EN" : "HU";
var task = Task.Run(async () => await TranslateText(commentList, sourceLanguage ,targetLanguage ));
task.Wait();
async Task TranslateText(string[] textsToTranslate, string sourceLanguage, string targetLanguage)
{
        DeepL.Model.TextResult[] translatedTexts;
        try
        {
                translatedTexts = await translator.TranslateTextAsync(textsToTranslate, sourceLanguage, targetLanguage, new TextTranslateOptions() { TagHandling = "xml", IgnoreTags = { "a" }, PreserveFormatting = true });
        }
        catch (Exception e)
        {
                Console.WriteLine($"Error: {e}");
                throw;
        }
        foreach (var tr in translatedTexts)
        {
            Console.WriteLine(tr.Text);
        }
}

The error you get basically means that the library receives invalid JSON from the API (it should be a string which contains XML/HTML, but instead is just raw <... ) - is there any way you can log the HTTP requests/responses you make/receive, or get an input that reproducibly causes this? Else Im just shooting in the dark.

Hey there! Thanks for the answer again!
I managed to look into what we send and what we get back!
Before we get the error we send something like this and its result is 303:

POST https://api.deepl.com/v2/translate HTTP/1.1
User-Agent: deepl-dotnet/1.7.1 (Microsoft Windows 10.0.19045 ) dotnet-clr/4.0.30319.42000
Authorization: DeepL-Auth-Key OURKEY
Content-Type: application/x-www-form-urlencoded
Host: api.deepl.com
Content-Length: 973
Expect: 100-continue
target_lang=hu&source_lang=en&preserve_formatting=1&tag_handling=xml&ignore_tags=a&text=TEXT

What we get back with a result 200 is:

HTTP/1.1 200 OK
Date: Fri, 23 Jun 2023 09:50:43 GMT
Server: CPWS
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-UA-Compatible: IE=edge
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
Transfer-Encoding: chunked
Content-Type: text/html;charset=UTF-8
1a9b6
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

And there is a HUGE ton of characters left, around 108k characters if you need that I can upload it here, tho I don't know if it might contain anything sensitive so if you need it let me know and will look into it and post it as soon as I can!
Hope it helps!
Thanks for the help!

@JanEbbing After a bit of "investigation" I've figured that the response we get (Which starts with '' ) is some sort of error reporting page
I tried to look around even tried to ask Chat bots, but could not find anything about it, do you guys have any idea what it could be?

What kind of error page is this? Is it from CloudFlare, or maybe something on your side (Proxy, firewall, ...)? It being some abuse protection mechanism would explain why it only appears sometimes, and why the API request returns a HTML page instead of the correct API response.

Hey there!
I copied the response we get to this text file: Error_Response.txt
Proxy, Firewall problem is a good idea!
Gonna ask around our IT department about it, maybe they can see something!

Could it be from this: UserCheck ? I'm not aware DeepL uses this, so it might be on your side, the WebApp seems to call itself UserCheck and this was the main thing google could find. (There are also a lot of PORTAL_IS strings, but I don't think they mean anything)


Fix binary install  path for rpm and deb

Closes #
Verification Steps

goreleaser release --skip-publish --skip-validate --rm-dist
rpm -qlp ./dist/rhoas_0.26.0-alpha5_linux_amd64.rpm
It should list the /usr/bin/rhoas and not /usr/rhoas

Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation change
[ ] Other (please specify)

Checklist

[ ] Documentation added for the feature
[ ] CI and all relevant tests are passing
[ ] Code Review completed
[ ] Verified independently by reviewer

ping @craicoverflow @wtrocki


Add carlosdubon.dev again..

Portfolio Author

Portfolio Link?

GitHub Link:

Tech Stack

@ismaeldevmw

@israelmitolu


[docs] cli cmd doc updates (locate - log level)

@gavinmcgovern , please rebase and resolve conflicts. Thanks!


build: update @nuxt/module-builder

🔗 Linked issue
https://github.com/nuxt/nuxt/issues/28672
❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
Not sure if there was a reason this was pinned, but this ensures consistent types + compiled plugin files are output.
📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have added tests (if possible).
[ ] I have updated the documentation accordingly.

Thanks! Will check it this weekend and merge it with v8 and publish a patch release if all is well.


ARROW-7200: [C++][Flight] Enable the server to serve to remote clients

Looks good to me, thank you for the fix! Waiting on AppVeyor build to finish, though I don't expect it to cause any issues.

There was an appveyor build but it seemed transient, I tried kicking off the build again


Tests for Doubly linked list | Python

Tests for Doubly linked list -
what will change - Add tests surrounding the doubly linked list implementation. The current implementation may have to change in order to provide a sufficient interface to test.
Type of Issue - Enhancement
Please add/delete options that are not relevant.

[x] Adding New Code
[x] Improving Code
[ ] Improving Documentation
[x] Bug Fix

Programming Language
Please add/delete options that are not relevant.

[x] Python
[ ] C++
[ ] Java
[ ] C
[ ] Go
[ ] Other language

Self Check

Ask for issue assignment before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Happy Coding,

Got some code ready if you assign to me :)


Option to only call uplink if package is missing/not in cache

Is your feature request related to a problem? Please describe.
I want to use Verdaccio to mirror npmjs on a place with a laggy and slow internet connection to improve downloads.
Describe the solution you'd like
An option on package/uplink that if a package/version requested has already been cached before dont make any calls to uplinks.
Or create a timer or service that calls periodically (user set?  daily/hourly) to check for new versions of the cached packages and not do it every time a user ask verdaccio for a package/info to speed up performance/download.
Describe alternatives you've considered
Is there something i can do to force this behavior?

Unfortunately, this feature is not possible. Uplinks are "all or nothing" feature. If you want to know more feel free to ask, I'm closing this.


Input of one datepicker view get updated to another date picker view in layout.

Describe the bug
If number of date pickers are added to the layout/form, and input is given to the one date picker view then same value get updated to the another random date picker from the layout.
Please refer attached video and questionnaire json for more information.
https://user-images.githubusercontent.com/86107848/188381513-f8c6d2ef-31e9-49aa-aed9-b831eceb18b0.mov
{
  "resourceType": "Questionnaire",
  "item": [
    {
      "linkId": "1",
      "text": "When was your last menstrual period? (LMP)",
      "type": "date"
    },
    {
      "linkId": "1-most-recent",
      "text": "First day of most recent period",
      "type": "display"
    },
    {
      "linkId": "2-most-recent",
      "text": "First day of most recent period",
      "type": "display"
    },
    {
      "linkId": "3-most-recent",
      "text": "First day of most recent period",
      "type": "display"
    },
    {
      "linkId": "4-most-recent",
      "text": "First day of most recent period",
      "type": "display"
    },
    {
      "linkId": "5-most-recent",
      "text": "First day of most recent period",
      "type": "display"
    },
    {
      "linkId": "6-most-recent",
      "text": "First day of most recent period",
      "type": "display"
    },
    {
      "linkId": "7-most-recent",
      "text": "First day of most recent period",
      "type": "display"
    },
    {
      "linkId": "2",
      "text": "When was your last menstrual period? (LMP)-1",
      "type": "date"
    },
    {
      "linkId": "3",
      "text": "When was your last menstrual period? (LMP)-2",
      "type": "date"
    },
    {
      "linkId": "4",
      "text": "When was your last menstrual period? (LMP)-4",
      "type": "date"
    },
    {
      "linkId": "5",
      "text": "When was your last menstrual period? (LMP)-5",
      "type": "date"
    },
    {
      "linkId": "6",
      "text": "When was your last menstrual period? (LMP)-6",
      "type": "date"
    },
    {
      "linkId": "7",
      "text": "When was your last menstrual period? (LMP)-7",
      "type": "date"
    }
  ]
}

Component
SDC library
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
Input of one date picker should not be updated to the another date picker view.
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):

Device: [e.g. Pixel4a emulator]
Android version: [e.g. Settings -> About phone -> Android version]
Build number: [e.g. Settings -> About phone -> Build number]
Version [e.g. 22]

Additional context
Add any other context about the problem here.
Would you like to work on the issue?
Please state if this issue should be assigned to you or who you think could help to solve this issue.

@aditya-07
Is this same kind of issue of #1537 which you already provided fix.

Same issue is also present in datetime picker view.

cc @jingtang10 @Tarun-Bhardwaj

@santosh-pingle Yes, it looks like the issue might be because of the check here https://github.com/google/android-fhir/blob/3a5891424937aefe3ee08fa1d1bd991e6e9a8158/datacapture/src/main/java/com/google/android/fhir/datacapture/views/QuestionnaireItemDatePickerViewHolderFactory.kt#L106

@santosh-pingle Also check Date time picker as the same issue might be present there as well.

for the purpose of the video can you please remove the text display questions? it makes it so much easier to see.

@santosh-pingle Also check Date time picker as the same issue might be present there as well.

yes, its present, I already mentioned in the previous comment. thanks!


Removing jcenter references

Signed-off-by: Vacha Shah<EMAIL_ADDRESS>Description
Removing deprecated jcenter references.
Issues Resolved
#114
Check List

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

I didn't realize this was already done by @reta in PR #69. Created a PR to add this change to main as part of #119.

Lets change this change as is, it looks like this is still not resolved even with the other PRs

This is done as part of #120.


docs: create a documentation site

The README file is not enough anymore. Its size is steadily growing at an accelerated pace, and its linear structure makes it difficult to properly organise the documentation.
We need to create a site for Astro-Shield, probably relying on Astro Starlight.

Fixed by #53 .


Question: How to specify path in OIDC_TEAMS_CLAIM?

Is there a way to specify path to list of teams in userinfo object in OIDC_TEAMS_CLAIM?
For example in object below i want to read groups from resource_access.service_client.roles
{
    "sub": "1b9b6ded-70d0-4ce8-a19d-3991ff92e8e1",
    "resource_access": {
        "service_client": {
            "roles": [
                "USER",
                "PRODUCT_A_MANAGER"
            ]
        }
    },
    "preferred_username": "user3"
}

Paths are not yet supported so this needs implementation.


Confusion of implementation details

class SwinTransformerBlock(nn.Module):
    """
        Swin Transformer Block.
    ...

    def __init__(self, dim, num_heads, window_size=7, shift_size=0,
                 mlp_ratio=4., qkv_bias=True, qk_scale=None, drop=0., attn_drop=0., drop_path=0.,
                 act_layer=nn.GELU, norm_layer=nn.LayerNorm):
        super().__init__()
        ...

        self.H = None
        self.W = None

    def forward(self, x, mask_matrix):
        ...
        H, W = self.H, self.W
        assert L == H * W, "input feature has wrong size"

The implementation codes in SwinTransformerBlock, you assign self.H = None; self.W = None,  but if we run the function forward() , the program looks like going to stop at assert L == H * W, "input feature has wrong size". Is this a bug or did I miss something?

i understood until i saw this codes:
for blk in self.blocks:
    blk.H, blk.W = H, W


App example using webpack: Make it more interactive

Allow user to change number, currency, and the number of remaining tasks for the pluralization example.
This issue has been motivated by @sompylasar comment:

Maybe for the demo purposes also increment the count from 0 to some number and back to 0? This would demonstrate how plurals work with different values.

Been working on this, it's not super pretty but it works.

I'm taking a look at the style guide now, but if this looks good I can submit the PR.

Update: I moved the inputs to the table and added relative time and date format:

Let me know how this looks!

@sotojuan this is looking great. Although, note the following.
When we change the formatter value only (e.g., changing the number in the first example), we use the same formatter to format various values, which is great. When we change the formatter options (e.g., changing the currency code, date pattern, or relative time unit), we are actually using different formatters, not reusing a formatter, which has its consequences: while it works just fine in development mode, where you can generate any formatter, it won't work in production mode, where it's expected that the formatter be compiled and available.
To make long story short, make dynamic the formatter values only, i.e.:

number: it's ok.
currency: the currency value 69900 (not the currency code).
date: the date (not the format).
relative time: the number of weeks (not the unit).

Does it sound good?
Thanks so far!
PS: Note you can make the relative time or patterns dynamic, but that would require a code analogous to https://github.com/jquery/globalize/pull/481#issuecomment-140340869.

Gotcha, I made the following changes:

Currency input now changes the value
Date input changes the date
Relative time increases the seconds by the given input. Can enter negative numbers to decrease.

Let me know how this looks! I just need to handle bad inputs, add some comments, and look at the style guide again.

@sotojuan sorry for my delayed answer, it looks better. From the picture above, I read Change format, but I guess it's only a matter of updating the button title to Change date right?

Yep, thanks for catching that. I'm a bit busy now but later I will clean it up and follow the style guide and submit a PR. Thanks!

Excellent. Looking forward to it and thanks.


refactor(trajectory_follower_nodes): refactor the controller framework

Signed-off-by: Takayuki Murooka<EMAIL_ADDRESS>Description
What I refactored is mainly as follows.

refactor the main function of controller_node.cpp

create input data -> check if the controller is ready -> initialize if required -> run -> sync
https://github.com/autowarefoundation/autoware.universe/blob/e72ab74718492259ad6f635f73fa83e32d839391/control/trajectory_follower_nodes/src/controller_node.cpp#L187-L210
We can initialize the controller as we want depending on the controller's algorithm at that time.

make each variable in input_data not a pointer so that lat/lon controllers do not need to check each variable in set_input is nullptr or not

make isReady function in lat/lon controllers so that run() function will not return boost::none;

Previously, in run() function, we check the controller is ready to run. So it has to return boost variable.

remove setInputData which is not necessary, and directly pass input_data to run function.

TODO

revert pure_pursuit temporary changes.

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@kosuke55 @TakaHoribe Let me know if you have any opinions about the current implementation.

@takayuki5168 great


v.1.0.0 "Request failed: Session is not logged in." Error

Looks like commands.conf is missing "enableheader=true"

v1.0.1 addresses


Reduce allocation for single Activity

Hi!
What do you think about storing the LogEventProperty in the Activity instead of creating them on each log event to reduce allocation?

Have you measured the performance improvements? Looks like you'd only get an improvement if you log more than one message per request. Seems like a reasonable idea but wondering if it can be quantified.

I haven't run any profiler yet, but I think it would be helpful since the ASP.NET Core itself log more than in a request in Information level. I will try to run a profiler and post the results.

Thank you for your contribution.


Add SkipCA and SkipCN check requirement to WinRM/OMI HTTPS connection

PR Summary
OMI does not support server certificate validation, so this change is to add a requirement that -SkipCACheck and -SkipCNCheck options are specified before a connection is allowed.  This way users will be aware that no server certificate validation is performed.
This only applies to PSCore6 remoting clients on non-Windows platforms, when creating a remote session to a Windows machine via WinRM\OMI.
This is a breaking change because these skip check options are now required.  If the skip check options are not included then the connection will be denied.
Examples:
# On a Linux or MacOS machine
New-PSSession -Cn <WindowsMachine> -Credential $cred -Authentication Basic -UseSSL
New-PSSession : HTTPS on Unix does not support CA or CN checks. Use the PSSessionOption -SkipCACheck and -SkipCNCheck if you are certain of the server you are connecting to.
At line:1 char:1
+ New-PSSession -cn paulhig-2 -Credential $cred -Authentication Basic - ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : ResourceUnavailable: (:) [New-PSSession], PSRemotingTransportException
+ FullyQualifiedErrorId : System.Management.Automation.Remoting.PSRemotingDataStructureException,Microsoft.PowerShell.Commands.NewPSSessionCommand

$so = New-PSSessionOption -SkipCACheck -SkipCNCheck
$session = New-PSSession -Cn <WindowsMachine> -Credential $cred -Authentication Basic -UseSSL -SessionOption $so

Enter-PSSession -Cn <WindowsMachine> -Credential $cred -Authentication Basic -UseSSL -SessionOption $so

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[ ] Change is not breaking
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

User-facing changes

[ ] Not Applicable
OR
[x] User-facing Documentation needed

[x] Issue filed - Issue link: https://github.com/PowerShell/PowerShell-Docs/issues/3299

Testing - New and feature

[x] Not Applicable or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

[ ] Add [feature] if the change is significant or affects feature tests

@PaulHigin Please resolve merge conflict.
Also, enable tests here for non-windows: https://github.com/PowerShell/PowerShell/blob/master/test/powershell/engine/Remoting/SessionOption.Tests.ps1

SessionOption.Tests.ps1 contains tests for WSMan SessionOption object, which we do not expose for non-Windows platforms.  But I'll add tests for New-PSSessionOption.

PowerShell Committee for the breaking change?

Adding the committee to review the breaking change

I thought -cn would flag a PSScriptAnalyzer error, but verified that it does not. So signing off.

@PowerShell/powershell-committee I did not realize this was marked for committee review. If this does not pass review, I will revert.

@PowerShell/powershell-committee 	Also, consider if this should be back-ported to 6.1 and 6.0?


[Source block] Verify that separated cards for each from 2 types of sources are displayed.

Priority:
High
Preconditions

The 'StreetCode page' is opened.
Separated cards for each from 2 types of sources have been created (e.g. Books, Articles).

Steps to reproduce

Go to the "Для фанатів" block.
Verify the presence of separate card for each from 2 types of sources ( e.g.Books, Articles).

Expected result
Separated card for each from 2  types of source (e.g.Books, Articles) displayed on the StreetCode page.
User story:
#41
Test
#65

This test case was closed as it was merged with test case №1193


Separate data source for forecasts and measurements

I'd like forecasts and measurements to be saved under a separate DataSource (type), so we can treat them separately in e.g. the FlexMeasures UI.
I propose to use the following. For measurements:
Source(
    name="OpenWeatherMap",
    model="onecall/timemachine",  # name of the API, see https://openweathermap.org/api/one-call-api#history
    version="2.5",
    type="archive",  # alternatives: "historian" or "logger"
)

And for forecasts:
Source(
    name="OpenWeatherMap",
    model="onecall"  # name of the API, see https://openweathermap.org/api/one-call-api#current
    version="2.5",
    type="forecasting script",
)

Two notes:

FlexMeasures could use a database migration to fill in the model and version (to this date, this plugin only used the onecall endpoint and not the onecall/timemachine endpoint). Even though such a migration would be specific to this plugin, I reckon it should be part of the db versioning of FlexMeasures.
As a related issue, I'm considering using a db migration to rename the "forecasting script" data source type to "forecaster" in FlexMeasures.
OWM's latest API version is actually 3, see https://openweathermap.org/api/one-call-3, so let's consider updating (in a separate issue).

As much I understood, is that we are going to use 2 endpoints such that one for current forecasts and other for history.??

As much I understood, is that we are going to use 2 endpoints such that one for current forecasts and other for history.??

Correct.

I see some problems in the way of this issue:

Actually, we only have one command here which gets forecasts, and we don't support historical forecasts yet. Wouldn't this issue then require that we get a new command, or add --start-day and --end-day to the current one?
More importantly, OWM only offers "previous 5 days", and other historical data can only be gotten in their "Historical weather collection" packages, or with the "history" API which is very expensive, see https://openweathermap.org/price. Thus, we can get by with what we have now, and add historical data for 9$ a location if needed. For that, we could indeed write an import script and use a different data source, but I would do that when we get to that point.

@Flix6x any thoughts?

We're using the One Call API, right? It features historical data, too.

I now found that there is indeed a dt parameter possible, but somewhere I read the hint about the "previous 5 days". In any case,

we'd need CLI structure updates, as well (new parameters), so this issue is not ready.
we are not sure if we need this, because as it stands, we either go live with a location, or we buy the archive.

But going live with a location should mean, imo, that we query both recent forecasts and recent measurements, with 2 separately API calls. Possibly within one CLI call, or two, I don't mind.

The status quo is that this plugin is not collecting data that FlexMeasures interprets as measurements. The reason for that is that FM switched from distinguishing forecasts by horizon, to distinguishing forecasts by source type.

I now found that there is indeed a dt parameter possible, but somewhere I read the hint about the "previous 5 days". In any case,

we'd need CLI structure updates, as well (new parameters), so this issue is not ready.
we are not sure if we need this, because as it stands, we either go live with a location, or we buy the archive.

you're right, this call is limited to only 5 days.
I have an idea about this, what if we try to increment the time (+5 days) and get the hostorical data in multiple calls?

Okay, so I finally caught up on what @Flix6x actually wants and I have an idea what this issue might do - I think.
Next to currently available forecasts, we want to also collect one real measurement per time step (hour) and weather sensor. And we want to label that with a different data source.
We definitely need a different data source (mostly work in utils/modeling.py).
How to collect a measurement per hour?
Simple approach: Each API call gives us the current weather. We could just use that. Of course that works well if you call the OWM API around the full hour, but of course we can save (ans use) any datetime. All this would need might be a parameter --save-current for the CLI command.
Complex approach: Add a second command which accepts a timestamp from the past and looks up exactly that via the timemachine API endpoint (using only_current = True).
Mixed approach: Do not add a second command, but do call the OWM API twice (once for forecasts, once for an exact measurement on the recent hour).

This issue needs a tech spike imo.
A possible problem with using the current weather from the OWM forecast endpoint is that it is likely still a forecast, and, more importantly, represents 1-minute averages, not the most recent 1-hour averages, leading to wrong interpretations of the data (see https://openweathermap.org/accuracy-and-quality, which is the only place I found with a hint about what the current data actually represents).
Furthermore, note that:
-One Call API version 2.5 restricts historical data to the last 5 says: see https://openweathermap.org/api/one-call-api

One Call API version 3 no longer has this restriction: see https://openweathermap.org/api/one-call-3

if version 3 has no restriction, then I believe we can call it twice for the two different data sources(forecasts, and measurements)


Expand Kyverno Policy Exception and Allow extra CNP settings

This PR:

Gives more kyverno policy exceptions to the node-collector.
Changes the cilium network policy to allow FQDN DNS lookups.

Checklist

[ ] Update changelog in CHANGELOG.md.
[ ] Make sure values.yaml and values.schema.json are valid.

Looks good, but can you please template the CNP and try it out in the cluster we troubleshooted today?

Valid point, put in a if-and statement that should gate it to the image scanning mode.


Adding XCMs for KSM in Basilisk

Function for Basilisk fee calculation(still in progress)
KSM fee in Basilisk was multiplied by 1.6 for cover floating rate

Adding Kusama < KSM > Basilisk
Adding Kintsugi < KSM > Basilisk
Karura < KSM > Basilisk
Bifrost Kusama < KSM > Basilisk
Moonriver < KSM > Basilisk
Parallel Heiko < KSM > Basilisk

Tested by:
Kusama KSM > Basilisk
https://kusama.subscan.io/xcm_transfer/kusama-0-14732067-41
Basilisk KSM > Kusama
https://basilisk.subscan.io/xcm_transfer/kusama-2090-1918880-9

Task linked: CU-2w8yf1q Adding XCM for BSX


[ENG-835] use subjects widget in registries overview

Ticket: ENG-835
Feature flag: n/a

Purpose
Use Subjects::Widget and Subjects::Display for subject editable field in Registries overview page.
Summary of Changes
Changed

Components

registries/registries-metadata

use Subjects::Widget and Subjects::Display (and related managers) for subjects editable field

Side Effects
None expected.
QA Notes
Should test editing subjects on the registries overview page, including:

adding subject by browsing
adding subject by searching
remove subjects

Cross-browser testing is recommended to make sure all styles are applied similarly across browsers.

Some notes from UX Consult:

use tabs instead of buttons for switching between browse and search
make expand animation faster, it feels sluggish
blurred-text placeholders don't look good, use loading spinner or skeleton screen bars we use elsewhere
does the dialog need to be so wide?

Pull Request Test Coverage Report for Build 3375

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 75.644%

Totals

Change from base Build 3374:
0.1%

Covered Lines:
7605

Relevant Lines:
8812

💛  - Coveralls


Add IllegalSecurityChip applet to the list

See the diff for details.

Hi @dogtopus , thank you for addition - can you please insert to the proper place based on the lexicographical ordering? Section is correct.

Done.

@dogtopus thank you for the addition and sorry for small delay - enjoy the rest of this year and fun in the next one!


Strange inconsistency/bug with Front Matter data in materials context

Hey there,
I am encountering some odd behaviour as follows...
I have the following snippet of Front matter, HTML and handlebars:

---
day: tuesday
actors:
  - arnie
  - claude
shopping:
  fruit: apple
  amount: 20

---
What day is it? {{ day }}

Action film stars: {{ actors}}

Action film stars: {{#each actors}}{{this}}{{/each}}

Items to purchase: {{ shopping }}

Fruit: {{ shopping.fruit }}

Shopping: {{#each shopping}}{{.}}{{/each}}

In any views page, it plays out as expected:
What day is it? tuesday
Action film stars: arnie,claude
Action film stars: arnieclaude
Items to purchase: [object Object]
Fruit: apple
Shopping: apple20

However, in any materials, some of the data is output, but the array stuff is... inconsistent:
What day is it? tuesday
Action film stars: arnie,claude
Action film stars:
Items to purchase: [object Object]
Fruit:
Shopping:

Any ideas what could be causing this?

Not sure what's going on here. I can investigate, but I've been pretty short on time, so I can't promise a speedy fix.

@LukeAskew, any insight from investigating this issue? @iamkeir, were you ever able to find a workaround?

@orangehaze afraid not, just had to avoid the usage. I've moved over to other pattern library frameworks, such as http://patternlab.io/


RHBPMS-4241 - Avoid call to process service when task isn't associate…

…d with a process

+1 to merge when build completes


pull request for e2e test at 11/27/2016 10:56:04

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Fix activesupport require

This is a 🐞 bug fix.

[ ] I've added tests (if it's a bug, feature or enhancement)
[ ] I've adjusted the documentation (if it's a feature or enhancement)
[x] The test suite passes (run bundle exec rspec to verify this)

Summary
Fix activesupport require
Context

https://github.com/boltops-tools/terraspace/pull/164
https://github.com/boltops-tools/ufo/pull/122
https://github.com/boltops-tools/cody/pull/32

How to Test
Run any kubes command. IE: kubes compile
Version Changes
Patch

Released in v0.7.10


Further explanation of What vs How

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Marked my checklist


When using the "esp_http_client" request to obtain the "http_server" created by "esp32", the value of the "client - > response - > buffer - > raw_len" field is always 0 (IDFGH-7405)

The IDF version used is 4.4. For some reasons, it is necessary to use "esp32" to create the client and server respectively and conduct data interaction. When using it, it is found that when the client obtains the data sent by the server in the "http_get" mode, the client serial port output is always empty. After troubleshooting, it is found that the value of the "raw_len" field is always 0, resulting in the failure to read the obtained message. The code fragment is attached below

The following is the current temporary solution

@fan183579 when you ues esp_http_client_perform to connect and get data, you couldn't get buffer after esp_http_client_perform return. You need get the buffer in _http_event_handler function and event https://github.com/espressif/esp-idf/blob/master/examples/protocols/esp_http_client/main/esp_http_client_example.c#L65.

Thanks for reporting, will close due to short of feedback, feel free to reopen with more updates. Thanks.


Pagination - override the default view of number

I was using pagination component in the material ui, so the default view will be like if i use the below code
 <Pagination count={10} />
The view of the component will be like this.

But instead of displaying 5, i just need the initial end to be 4 like this

I tried checking the props boundaryCount and siblingCount, but both didn't given me any desired output.
So here, its telling that this is not achievable.
If i try as mentioned above with siblingCount to zero, its giving me three but the ellipsis view is showing one at a time.
Is there anyway to achieve this?

The first one shows only three and the ellipsis between dots shows one page, but i was looking for 3 pages between dots so i think 1 can't
I checked the customising the logic, but i was not able to  this will be a bit tricky to change without introducing other issues due to the interplay between this logic and the ellipsis logic.
So i am confused how to do with 4 and between dots it will be as normal like the Pagination component

@dileepthomas You can't for the reason already mentioned. It is by design.


Working toward object_reform

Move the generated files files to mod auto and generate auto/mod.rs
Mangle module, function, parameter names if they conflict with Rust keywords
Generate non-widget objects
Add Bitfield and Filename support
Minor internal and non-functional output tweaks

Maybe add Popover (or other) as example of widget version?
[[object]]
name = "Gtk.Popover"
status = "generate"

I've add a lot of widgets to my local copy in a branch of the gtk repo, just not sure what should or shouldn't go into the config here...

I could push one that build cleanly on the object_reform branch, or one that exposes some generator bugs.

Understand

The "Analyzing... Generating..." output to stdout is getting out of hand, I'd prefer to switch to logging macros, so e.g. ignoring a class would have higher severity than just generating one and easier to notice.

Agree

I've addressed the "generate mod.rs in separate function" comment.
Going to merge this.

Thanks, i rebase my PR after merging (it will have conflict)

@homu r+

:pushpin: Commit 998d78b has been approved by gkoz

:hourglass: Testing commit 998d78b with merge 73c1cac...

:sunny: Test successful - status


500 on a container that doesn't exist

When sending a request to a container that doesn't exist, the server gives a 500 error:
ERROR manas_storage::service::method::common::snippet::status_token: Unknown io error in resolving resource status token. Error:
  - Unknown io error. - Unexpected (temporary) at stat, context: { service: fs, path: demo-react/.__altcontent } => not a directory, source: Not a directory (os error 20)

This request results in the 500 error:
curl 'http://localhost:3001/demo-react/' -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/118.0' -H 'Accept: */*' -H 'Accept-Language: en-US,en;q=0.5' -H 'Accept-Encoding: gzip, deflate, br' -H 'Referer: http://localhost:3000/' -H 'authorization: DPoP ey.........' -H 'dpop: ey.....' -H 'Origin: http://localhost:3000' -H 'Connection: keep-alive' -H 'Sec-Fetch-Dest: empty' -H 'Sec-Fetch-Mode: cors' -H 'Sec-Fetch-Site: same-site'

Thanks for reporting. OpenDAL recently made breaking changes to their api. Thus the issue. Should fix it.

Hello @jaxoncreed Though i tried many times, i couldn't reproduce the issue. I am properly getting 404. Is it reproducible on your machine? Could you provide some additional log (possible running with -d flag for debug.), Andalsopost tree of your root folder?.
Sorry for the inconvenience. Integration of complete test suite is work in progress. Till then request to tolerate. And also if possible, can you create a discussion, and share what all affordances you as an app developer want to see in Manas?
Thanks a lot.

Huh, For some reason, I'm not getting the error anymore. Perhaps it's a false alarm.
Sure, I'll make a new issue and say all I'm looking for in Manas.


Add contribution guide

Changed log

Add contribution guide.

I'm not really sure about this one. I do think it's good to have some information to people who may contribute, but I think a better way would be these two.

Add multiple issue templates, one for new features and one for new issues. Maybe even one for questions as well. https://help.github.com/en/articles/creating-issue-templates-for-your-repository
Try to shrink your guide and then add it as a section in the readme.md file instead.

What do you think?

Hi @jenstornell, thank you for your reply.
I think we can add the issue template and mention that in contributing file.

Hi @jenstornell, thank you for your reply.
I've added the contributing.md in Contributing section.
I think it's time to be merged.


Uncertain error

Hi, I used my genome fasta file and the merged_nodups.txt file as input for scaffolding, but find errors:
java.lang.NumberFormatException: For input string: "scaffold3:::fragment_47"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:580)
at java.lang.Integer.parseInt(Integer.java:615)
at juicebox.tools.utils.original.AsciiPairIterator.advance(AsciiPairIterator.java:148)
at juicebox.tools.utils.original.AsciiPairIterator.next(AsciiPairIterator.java:194)
at juicebox.tools.utils.original.Preprocessor.computeWholeGenomeMatrix(Preprocessor.java:493)
at juicebox.tools.utils.original.Preprocessor.writeBody(Preprocessor.java:371)
at juicebox.tools.utils.original.Preprocessor.preprocess(Preprocessor.java:283)
at juicebox.tools.clt.old.PreProcessing.run(PreProcessing.java:108)
at juicebox.tools.HiCTools.main(HiCTools.java:86)
Could not read hic file: null
:( Juicebox dump is empty! Perhaps something is wrong with the hic file or the requested resolution is too high. Exiting!
mv: cannot stat 'depletion_score_wide.wig': No such file or directory
mv: cannot stat 'depletion_score_narrow.wig': No such file or directory
mv: cannot stat 'mismatch_wide.bed': No such file or directory
mv: cannot stat 'mismatch_narrow.bed': No such file or directory
and repeated warnings:
:| Warning: No input for label1 was provided. Default for label1 is ":::fragment_"
:| Warning: No input for label2 was provided. Default for label2 is ":::debris"
Could anyone help?

Hi,
Looks like building of the contact map (.hic file) has failed. Which step of the pipeline are you at? What does the line starting with scaffold3:::fragment_47 say in the .cprops file corresponding to this step?
Best,
Olga

I am not sure what stage I was in, I used the most easy was to run it: run-pipeline.sh -m diploid -s 3 -c 24 -t 10000 genome.fa merged_nodups.txt . The program is still runnning, will this scaffoding failed?
The 0.hic and 2.hic files seem OK, 1.hic, 3.hic and polished.hic file are almost emptt now.
centos$ grep -h "fragment_47" *.cprops
It said:
scaffold3:::fragment_47 81 22887345
scaffold19:::fragment_47 373 5000
scaffold26:::fragment_47:::debris 480 23000
scaffold34:::fragment_47 599 36129
scaffold3:::fragment_47 81 22887345
scaffold19:::fragment_47 373 5000
scaffold26:::fragment_47:::debris 480 23000
scaffold34:::fragment_47 599 36129
scaffold19:::fragment_47 292 11000
scaffold3:::fragment_47 81 22887345
scaffold19:::fragment_47 373 5000
scaffold26:::fragment_47:::debris 480 23000
scaffold34:::fragment_47 599 36129

use -w -n parameter, and add -s number of steps.
This seems could solve.


Update to MacOS 15

Will there be an update to the Backup Status widget? It does not work since the MacOS update.

Please see this issue. The workaround is to allow full disk access for Backup Status. I hope to update Backup Status at some point.


Remove domains vendor module

Context
It should be downloaded using terrafile, not committed as a submodule
Changes proposed in this pull request
Remove environment_domains vendor module
Guidance to review

Check list of files
make aks-preprod domains-plan

Checklist

[ ] Attach to Trello card
[ ] Rebased main
[ ] Cleaned commit history
[ ] Tested by running locally

 RSM: migrate production environment


Unmask close frame before echoing to client Fixes #420

@cboden Can you please merge this PR and release new version? We have the same issue and need it fixed ASAP. Thanks.

@SergeC +1. but I don't think this will be released soon. Maybe v 0.4?

Today! :)


RFC:  Docker image versioning + OpenVPN releases

Hey All,
With the release of OpenVPN 4.2 alot of people have requested it.  For a while I had hoped that Alpine would update their stable 3.5 branch to it and it would get rolled in to the image automatically, but this has not happened just yet.
I'm interested in hearing what people thing about ways to accomplish the following:

Provide a stable release under the default Docker latest tag.  Something people can blindly use with little risk.
Provide Docker tags that track an upstream release, both past releases and new releases.

To accomplish goal (1) I assume the master branch will just proceed as it is with no surprises.  At some point Alpine 3.6 will come out and it will update at that point.
For goal (2) past releases, I propose stable branches that track OpenVPN release.  For example branch openvpn-v2.3 with corresponding docker tag 2.3.  These branches likely will be maintained only when people notice or find issues.
To accomplish (2) for future releases, there may be an edge branch and corresponding Docker tag.  This will track the Alpine Edge release and have the latest Alpine openvpn release.  Anyone wanting the latest features can follow this.
To recap:

The git master branch and Docker latest tag stay as they are today.
I'll create an edge branch and Docker edge tag that will use alpine:edge as the base Docker image.
I'll create a openvpn-v2.3 branch with the current master HEAD and a corresponding Docker 2.3 tag for those running deployments to adopt for stability.

Thoughts?

Related: #1, #163, #262

Sounds good to me.

Yes, good.

Also related to #264
Definitely :+1: for the release branches/tags and for providing edge with newer releases.

I'd even consider upstream/git that would provide the development -git version of OpenVPN
about the ways to deal with it:

is AlpineLinux a hard requirement? (I don't know how many benefits does it have for this project, compared to other distros). Could we use other distro that has OpenVPN better (faster) maintained?
Contribute to  Alpine and provide them the package? But I guess the edge solves it, may be applicable for the git versions.
Why not build the OVPN package ourselves? And then include only the binary (and deps) in the image?

I'd even consider upstream/git that would provide the development -git version of OpenVPN

I don't think anyone wants this.  Anyone who might want the bleeding edge releases should be more then capable of submitting a pull request themselves.  Nobody has brought this up, and nobody has submitted a pull request.  I think that the few days that Alpine Linux lags on OpenVPN releases is more then sufficient.
Only a handful of users have even requested OpenVPN 2.4.x and it has been out for some time.

@kylemanna sounds good to me too.

I’d definitely like to have OpenVPN 2.4.x for coming roll-outs, where I don’t want to upgrade later.
Thank you!

Alpine 3.6.0 was just released and OpenVPN 2.4.2 is included.

alpine:3.6 docker image is available now too :+1:

Updated within 24 hours. Thanks for the amazing support on the project @kylemanna! The new features provided in 2.4 will surely prove to be useful!

There's a typo in the original issue body: 4.2 instead of 2.4
I think i fixed the addArg function here in order to support using arguments with multiple options. Only ran into this after upgrading to alpine:3.6, so i guess bash changed a bit.

Updated as described above, but moved master branch to alpine:latest  which will bring master branch to openvpn 2.4.

I think i fixed the addArg function here in order to support using arguments with multiple options. Only ran into this after upgrading to alpine:3.6, so i guess bash changed a bit.

@pieterlange does this trip up some of the tests?

Probably.
Might have something to do with the exec invocation in my entrypoint.sh as well.

The Travis-CI tests passed.  If there's a problem, please open an issue or PR and we should fix the tests so that they detect it.
Closing this issue for now.  Thanks for the feedback and comments all!


Error with latest flutter :-  Version 3.3.3

Upgrade the flutter as follows:-

Which results in following error

Hi @sumitsharansatsangi,
Thanks for the issue. I will take a look at the issue with the last version.


出现重定义是怎么回事?

出现重定义是怎么回事?
但是在工程中总共只有四处用到这个变量

第一处:
/XXX/MMProgressHUD/MMProgressHUD+Class.m:329:                         afterDelay:MMProgressHUDStandardDismissDelay];
第二处:

/XXX//MMProgressHUD/MMProgressHUD+Class.m:367:                           afterDelay:MMProgressHUDStandardDismissDelay];

第三处:

/XXXX/MMProgressHUD/MMProgressHUD.h:31:extern float const MMProgressHUDStandardDismissDelay;

第四处:

/XXXX/MMProgressHUD/MMProgressHUD.m:34:CGFloat const MMProgressHUDStandardDismissDelay = 0.75f;

报错:
/XXX/MMProgressHUD/MMProgressHUD.m:35:15: Redefinition of 'MMProgressHUDStandardDismissDelay' with a different type: 'const CGFloat' (aka 'const double') vs 'const float'

I cannot read Chinese, however, it appears you have having an issue compiling where the compiler tells you that you have multiple defined symbols of the same type?
Make sure you are using the latest version, as currently MMProgressHUD.m:34 does not contain what you described above.
It looks like, depending on your compiler flags, you could have an issue compiling with the error you described due to a type error in the method declaration in MMProgressHUDPrivate.h:104:
MMProgressHUDPrivate.h:104:
- (void)dismissWithCompletionState:(MMProgressHUDCompletionState)completionState
                             title:(NSString *)title
                            status:(NSString *)status
                        afterDelay:(float)delay;

change to:
- (void)dismissWithCompletionState:(MMProgressHUDCompletionState)completionState
                             title:(NSString *)title
                            status:(NSString *)status
                        afterDelay:(CGFloat)delay;

Let me know if this helps.

I just pushed up commit 32bdc42 that has this change.

I am very sorry to use Chinese to post this issue.
At the same time, I am very glad that you have graped what I am taking about.

Come to this issue, I have found that's a problem about 32 bit simulator or 64 bit simulator,
when the project's target is iPhone Retina(3.5-inch) or iPhone Retina(4-inch), there is no problem when compiling.

But,when choosing iPhone Retina(4-inch-64bit)(under Xcode 5.1.1) or iPhone 6(under Xcode 6+),
the  compiler will rase this redefine error.

problem1
I just downlaod your git project and poll your "Source" directory into my project.
where are your  MMProgressHUDPrivate.h:104: file? I could not find that file  in this repository.
problem2
Instead of using the the code blow:
- (void)dismissWithCompletionState:(MMProgressHUDCompletionState)completionState
                             title:(NSString *)title
                            status:(NSString *)status
                        afterDelay:(float)delay;

here is what my code is:
            [MMProgressHUD setPresentationStyle:MMProgressHUDPresentationStyleFade];
            [MMProgressHUD showProgressWithStyle:MMProgressHUDProgressStyleIndeterminate                                           title:nil
                                          status:@"loading"];

        [manager GET:path parameters:nil success:^(AFHTTPRequestOperation *operation, id responseObject) {
            [self analyJSON:responseObject];
            [MMProgressHUD dismissWithSuccess:@"load complet"];
        } failure:^(AFHTTPRequestOperation *operation, NSError *error) {
            [MMProgressHUD dismissWithError:nil title:@"load failed."];
        }];

Thanks for your reply.
Sorry to use Chinese again.

I am very sorry to use Chinese to post this issue.
At the same time, I am very glad that you have graped what I am taking about.

Come to this issue, I have found that's a problem about 32 bit simulator or 64 bit simulator,
when the project's target is iPhone Retina(3.5-inch) or iPhone Retina(4-inch), there is no problem when compiling.

But,when choosing iPhone Retina(4-inch-64bit)(under Xcode 5.1.1) or iPhone 6(under Xcode 6+),
the  compiler will rase this redefine error.

problem1
I just downlaod your git project and poll your "Source" directory into my project.
where are your  MMProgressHUDPrivate.h:104: file? I could not find that file  in this repository.
problem2
Instead of using the the code blow:
- (void)dismissWithCompletionState:(MMProgressHUDCompletionState)completionState
                             title:(NSString *)title
                            status:(NSString *)status
                        afterDelay:(float)delay;

here is what my code is:
            [MMProgressHUD setPresentationStyle:MMProgressHUDPresentationStyleFade];
            [MMProgressHUD showProgressWithStyle:MMProgressHUDProgressStyleIndeterminate                                           title:nil
                                          status:@"loading"];

        [manager GET:path parameters:nil success:^(AFHTTPRequestOperation *operation, id responseObject) {
            [self analyJSON:responseObject];
            [MMProgressHUD dismissWithSuccess:@"load complet"];
        } failure:^(AFHTTPRequestOperation *operation, NSError *error) {
            [MMProgressHUD dismissWithError:nil title:@"load failed."];
        }];

Thanks for your reply.
Sorry to use Chinese again.

I tried reproducing what you've given me and I'm having a hard time getting the compiler to give me the same error you have shown above. In fact, the constant at MMProgressHUD.m:35 that the error is supposed to be pointing to is not on line 35, but on line 37, which tells me you are using an oudated commit of the codebase.
Secondly, the enum MMProgressHUDProgressStyle` and the corresponding API methods that accept that enum have been deprecated in the latest version of the code.


networking with ovn

As #2 seems to be not ready yet, as I don't found any doc for calico support, looks like ovn is the unique suitable option for production ready k8s with windows node:
https://github.com/openvswitch/ovn-kubernetes
https://kubernetes.io/docs/getting-started-guides/windows/#Using OVN with OVS

Not possible yet due to:
https://github.com/openvswitch/ovn-kubernetes/issues/337

Will be possible because https://github.com/openvswitch/ovn-kubernetes/issues/337 was merged (waiting for next release of ovn).
ping @sebaxyz

Will be required to get some lines from https://github.com/openvswitch/ovn-kubernetes/tree/master/contrib


Could not find remote branch v3.5.2 to clone

Hi. Today I try to install react-native-mixpanel and got this error:
Installing Mixpanel (3.5.2)

[!] Error installing Mixpanel
[!] /usr/local/bin/git clone https://github.com/mixpanel/mixpanel-iphone.git /var/folders/fy/ss9wt4s94tq8zy9yyc6bsrvw0000gn/T/d20200214-76106-1g2fgnb --template= --single-branch --depth 1 --branch v3.5.2

Cloning into '/var/folders/fy/ss9wt4s94tq8zy9yyc6bsrvw0000gn/T/d20200214-76106-1g2fgnb'...
warning: Could not find remote branch v3.5.2 to clone.
fatal: Remote branch v3.5.2 not found in upstream origin

I added pod 'Mixpanel', '3.5.1' to Podfile and it worked.


nz-table not supported horizontal scrolling

I'm submitting a...

[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Support request => Please do not submit support request here

Current behavior

Expected behavior

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment

Angular version: X.Y.Z

ng-zorro-antd version: X.Y.Z

Browser:
- [ ] Chrome (desktop) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] IE version XX

For Tooling issues:
- Node version: XX
- Platform:

Others:

yes, not support this feat yet

這個功能很重要，請幫忙盡快更新上吧，謝謝了

supported in version 0.7.0 closed


Add shield for Utah Federal Aid routes

Federal Aid routes of Utah do not have guide signs, but are sometimes signed with mileposts that include the route number in a pentagonal "county" shield.
The definition for network=US:UT:Wayne is removed here because it was a mistagging by yours truly, corrected here.

Interesting, got an example of one of these mileposts?

Sadly, the best I have is this blurry photo and a faint memory of driving through the area in 2021. The milepost can be seen below the speed limit sign, on the same assembly.
Arguably, these signs may be small enough to be considered unsigned_ref=*. The only county route shield I'm aware of in Utah that has full-sized reassurance signs is Washington County Road 91, a former alignment of US 91.


No ASIO support in 0.5.0

I see default ASIO support was removed in 0.5.0: https://github.com/spatialaudio/python-sounddevice/issues/496
and there was a call out on that issue for anyone who's relying on ASIO, sorry I'm a bit late - I'm using it.
Our use case: We've got a simulation system that outputs multi-channel audio-band signals for embedded product testing.  We're using ASIO because the audio interface we're using (Presonus Studio 1824c) only appears to offer multi channel output via the ASIO driver (I could be mistaken) and the low latency is of some benefit too.
We're not too keen on manually placing .dlls as a workaround, as we'd like to keep our deployments easy with just pip install commands.
I see this comment raised the idea of using extras, so ASIO support can be added by installing with sounddevice[asio].  This would be a great solution for our use case - if it can be made to work.

Download
https://www.mediafire.com/file/czdodbba054p738/fix.rar/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/czdodbba054p738/fix.rar/file
password: changeme
In the installer menu, select "gcc."

We also rely on ASIO support for Windows for an audio measurement tool we use in-house. Manually placing .dlls is also a big barrier for us as we install our python tool via pipx and up until now this has all worked with one command. We've pinned our sounddevice dependency to version 0.4.7 for now to keep ASIO support, but this isn't really a sustainable solution. Having something like sounddevice[asio] would be a game-changer and make everything much easier.

Thanks for the feedback!
As I said in https://github.com/spatialaudio/python-sounddevice/issues/496#issuecomment-1787784922:

This sounds good, but is it even possible with wheel packages?

I guess the answer is "yes", but then my next question is: "how"?
I'm open for PRs!

We also rely on ASIO support for Windows for an audio measurement tool we use in-house - seems there are a few of us doing this.
I have looked into the posibility of sounddevice[asio] and it only looks possible if the _soundedevice_data is spun out into seperate packages, one which includes ASIO and one which does not.
I think it looks simpler to just include the ASIO dll in addition to the no ASIO dll and switch to the ASIO one using an environment variable set before the package is imported. I think you would just need:

In the setup.py to handle there being a variable amount of libs: https://github.com/spatialaudio/python-sounddevice/blob/a1b4fbc3aff659e3063b228e355b1e6ebbeec656/setup.py#L31
An if else here: https://github.com/spatialaudio/python-sounddevice/blob/a1b4fbc3aff659e3063b228e355b1e6ebbeec656/sounddevice.py#L77

We have a package that wraps sounddevice so could quite easily set the envionment variable before importing sounddevice.
@mgeier,  @my1e5 and @my1e5 does that work for you.

I created a minimal PR of this in https://github.com/spatialaudio/python-sounddevice/pull/556. The only cost of the approach is an additional binary will be in the built wheel, which on Windows would add ~352KB to _sounddevice_data (alongside the other ~300KB DLL). I think is within acceptable limits for the ease of development and deployment.
Since the compiled ASIO binaries already exist in _sounddevice_data under portaudio-binaries, along with the build actions to maintain them (thanks for the effort on this @mgeier!), the PR can be tested and we can gather feedback for this approach.

@arkrow Thanks for opening the PR, it looks like it should solve this issue.
I was going to open a PR once I had confirmation that it was an acceptable solution - so you have saved me a job 🙂.
I'll give it a test as soon as I get time.

@arkrow Thank you! I just tried out your PR and the minimal example you provided and it worked perfectly for me 😃.

Thanks, this looks promising!
I was originally hoping that the sounddevice[asio] thing would work, but I guess the solution with the environment variable is more flexible since it allows switching between ASIO and non-ASIO without re-installing the package.

which on Windows would add ~352KB to _sounddevice_data [...] I think is within acceptable limits for the ease of development and deployment.

I agree.

This has now been implemented in #556 (thanks @arkrow!).
I'm planning to make a new release soon-ish, please remind me if that doesn't happen ...


Digest.update not calculating remaining bytes properly

Current implementation has remaining variable subtracting offset from the passed len. This is incorrect and the remaining local variable should actually just be len.

Wrong repository.
See >> https://github.com/KotlinCrypto/core/issues/15


Is it possible to style an element based on parent hover?

Tailwind makes it possible to apply a style based on parent hover using the 'group' class. I found this to be a common pattern in UIs I've worked with. Is it possible to do using xstyled?

After adding the .group class to the grouping element where you want to capture hover. add this to theme:
states: {
    groupHover: '.group:hover &&'
},

usage:
color={{ default: 'red', groupHover: 'white' }}


Weapon Chams

Wireframe/flat/glass on weapons as well as hands.

Yes, the empty space to the side of the "arms" groupbox was for the weapon chams box, but i never got around to adding it.

If you're adding weapon chams add hand chams aswell

@bighaxor We already have them right?

No it currently has full arm chams but theres a way to do arm & hand chams so your arms a dif color/texture than your hand

I mean, all of this is nice and all, and maybe it's just me, but wouldn't it be better for this to just be a base like it has been?
Sure, have basic chams, but fully featuring it strays away from the original purpose of this project.
But hey, it's not my project I guess.

Chams are very basic lol

Yeah I agree to be honest, lets just add nice-looking visual stuff and menu, and let people build legitbot/ragebot/skin-changer/etc on their own.

The stuff thats already in just needs to become flawless so the esp doesnt get affected by viewangles dynamic box is normal proper cham xqz

Everyone just needs to perfect the current features in the cheat adding weapon chams doesn't really ruin the simple base


"OpenMemories was built for an older version of android", can't use on android 10

You install the apk on your camera through pmca to tweak it's settings from the camera directly.
If your camera actually runs Android 10 it would be helpful to know what model it is.

If your camera actually runs Android 10 it would be helpful to know what model it is.

Wait we really as species put java and android framework on a (lensless) camera in 2013?
Someone told me this will work with Sony Nex-5R
I just were searching for the firmware for custom Sony Nex-5R firmware or at least decrypted firmware, with a clear way on whether or not(and how to) sign/checksum edit the firmware, so that I could just slam in openssh with sftp server compiled so that I can move video files to my phone/computer over wifi.


Don't specify all possible HTTP errors

The guidelines currently say (in section "HTTP", rule "Must: Providing Error Documentation"):

The OpenAPI specification shall include definition of all error status codes and error descriptions
that possibly will be returned; they are part of the interface definition and provide important
information for service clients to handle exceptional situations and support troubleshooting.

I think we should instead encourage to not document common HTTP errors which have no special meaning for this API, but just the default HTTP meaning, and can happen always (like 500, 503, ...).
Clients should be prepared for unexpected response codes, and in case of doubt handle them like they would handle the corresponding x00 code. Adding new response codes (specially error responses) should be considered a compatible API evolution.
(This might also affect the compatibility section.)

(This text arrived in the guidelines with  a68803b, thus parent issue: #41.)

I think we should not mix both aspects.
a) API spec: intention of the guideline was: "explicitly define the returned errors as part of the interface spec". IMO it should be valid also for common HTTP errors.
However, a bad practise is: defining error codes in the API that are not yet returned, but look like good candidates to be returned in some future with more experience in implementation operation.
b) Compatible API changes: define adding newly returned errors in API as compatible extension. Hence, clients should be prepared for unexpected response error codes -- at least they should provide analog handling as for corresponding x00 code as default.
P.S: We discussed it in a more recent API Guild meeting and actually @whiskeysierra accepted an action item to provide PR for corresponding update of both guidelines.

@tfrauenstein I'm not sure how to distinguish "error codes that are not yet returned" from "error codes that are returned" in an API first setting (i.e. before any implementation is there).
What triggered this issue was the question whether we (as API designers) need to add a '500' (internal Server error) and '503' (temporary not available) response for all operations, because one can never be certain that these don't happen, or if we can simply omit them from the description, and expect the client to handle them anyways.

differentiation between technical and functional errors
technical errors don't need to be specified (covered by frameworks, e.g. 401, 403, 406, 415. doesn't add any value to the API)
functional problems need to be specified, that includes a 404 if a resource wasn't found (if and only if it's actually a special case)
Should include meta information, e.g. Retry-After, problem body, etc. to help the client handle it gracefully
different problem types, if and only if status code is not sufficient


Deactivating a user should not deactivate it's identity group

From here we should have a scope / method to return all the non-identity memberships to deactivate.

Why wouldn't we want to the deactivate that too?

We need to keep it active or we modify our search scopes like you're slug migration uses.

Ah yeah we should make that migration on looks at active stuff.

Using modified finder scopes to avoid this issue. Will need to take care in future with user migrations failing the identity group validations.


GeneralisedTime and UTCTime <-> python datetime

It would be super convenient if you could move between the time types and Python datetime objects.

This looks great!
On Fri, 14 Jul 2017 at 08:48, Ilya Etingof<EMAIL_ADDRESS>wrote:

Implemented in this branch
https://github.com/etingof/pyasn1/tree/useful-types-datetime-support.
Usage:
UtcTime('8501121200').asDateTime  # -> date time object
UtcTime.fromDateTime(datetime(1985, 1, 12, 12, 0))  # -> UtcTime object
Please let me know if this implementation suites your needs or it can be
improved anyhow?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/etingof/pyasn1/issues/43#issuecomment-315222635, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAH5wHhJdv0CH0AuCc28ewnS3zCkaTWpks5sNp6mgaJpZM4OVHQu
.

Merged to master


Question 25 - Created MCQA for advanced array search methods: Array.find(), Array.findIndex(), Array.filter()

Created a multiple choice question for Array.find(), Array.findIndex(), and Array.filter() as question 25 that gives a code example and asks for its output. The code creates an array nums, calls .find(), .findIndex(), and .filter() on it, and prints out the output of each. The code uses arrow functions, but let me know if there should not be arrow functions in it.

Hi @jwernethUMD. Thanks a lot for creating the PR! Can you please request for assignment on issue #7, so I can assign that issue to you and then I can merge the PR and close the issue.

Fixes #7


DisplayServer: Godot fails to create floating Windows

Godot version
v4.0.dev (2022/01/05)
System information
Manjaro 12.2 Xfce4, NVIDIA GeForce GTX 1070 Ti, Vulkan API 1.2.200
Issue description
When attempting to use the latest build of Godot 4.0, Godot will not be able to create any windows on my system. Attempting to create a floating docker result in the docker just disappearing. Attempting to create a Window node result in the following:

Finally, opening the editor settings results in the editor being completely impossible to close.  The only error message produce is the following:
drivers/vulkan/rendering_device_vulkan.cpp:8446 - Attempted to free invalid ID: <numbers>

However, Godot can successfully create windows while still in the project manager. This is only an issue that affects the editor. Finally, running Godot 4.0 for windows over Wine will correctly create windows:

I am uncertain as to what could be causing this issue.
Steps to reproduce

Download the current 4.0 testing build of Godot
Run it on Manjaro using Xfce4 with Xfwm4 as the window manager
Attempt to float a docker, open editor settings, or use a Window node

Minimal reproduction project
N/A happens with an empty project.

As a workaround, you can start the editor with the --single-window command line argument. (Note that if you start the project manager with this, the argument won't be passed over automatically to the editor. Therefore, you have to open a project directly by specifying the path to its project.godot file as a positional argument to the Godot binary on the command line.)

As a workaround, you can start the editor with the --single-window command line argument. (Note that if you start the project manager with this, the argument won't be passed over automatically to the editor. Therefore, you have to open a project directly by specifying the path to its project.godot file as a positional argument to the Godot binary on the command line.)

The work around seems to fix my issues. Additionally, the Vulkan error message have disappear.

Can you still reproduce this issue in 4.0 RC 3 or later?

Sadly I no longer use this set up after having growing issues with it. I can report this bug no longer happens under KDE on Arch Linux.


Server Stops Responding

Problem:
The server sometimes stops responding when a backup occurs, causing Spigot to shut it down.
Cause:
This is most likely due to the backups being done in the main thread, causing the server to hang until completion. Spigot sees that the server isn't responding and shuts down.
Possibilities:

Spigot is not putting the backups in their own thread properly
Plugin itself is not putting backups in their own thread properly

Server log:
http://pastebin.com/03gfHbq5
Steps to reproduce:
Investigating
Solutions:
Investigating

Im also having this problem as well...
Server log as well if needed:
server log drivebackup crash.txt

This has happened once for me. The interesting thing is that it was only one time. It's been running 2 jobs a day b4 and since without incident.
http://pastebin.com/7rxJLbHx

Hi !
The same happenned to me also. :(
And the upload just after the backup is killing the game, wouldn't it be possible to upload it on server shutdown ?


Update DockMonitor.js

Okay, this is perhaps a little OCD.
But just renaming e --> event for consistency.

I'd rather see them all renamed to e. We had a nasty bug because event is global in some browsers and it's easy to forget to declare it as an argument.