Error exception "Expected keys to be an array of string" on Vercel deployment

Expected Behavior
No error when calling getAll().
Current Behavior
Working fine on dev environment, throws "Expected keys to be an array of string" exception on Vercel deployment.
Possible Solution
https://github.com/vercel/edge-config/blob/9689e9a0e21bba231e802074096a5a338f83c64f/src/index.ts#L257 should be conditioned like on line 265.

Was just arriving to call out the same issue. The assertion appears at odds with the functionality! 🥷🤺
https://github.com/vercel/edge-config/blob/main/src/index.ts#L34-L40
https://github.com/vercel/edge-config/blob/main/src/index.ts#L256-L262
Quick suggestion:
        if (localEdgeConfig) {
          if (keys !== undefined) {
            assertIsKeys(keys);
          }

          return Array.isArray(keys)
            ? Promise.resolve(clone(pick(localEdgeConfig.items, keys)) as T)
            : Promise.resolve(clone(localEdgeConfig.items) as T);
        }

Perhaps more accurately:
        if (localEdgeConfig) {
          if (keys === undefined) {
            Promise.resolve(clone(localEdgeConfig.items) as T);
          }

          assertIsKeys(keys);
          return Promise.resolve(clone(pick(localEdgeConfig.items, keys)) as T)
        }

Closing this as it shipped in #61


RadioButtons: Fix SelectionChanged event issues

Description
This PR fixes two issues with the RadioButtons control's SelectionChanged event:

The event is no longer raised two times instead of one time when selecting a radio button by clicking while another radio button is currently selected (selecting via API or keyboard already works correctly). The raised event now contains both the deselected item and the newly selected item (if any).
No longer are 'null' items included in the SelectionChanged.AddedItems and SelectionChanged.RemovedItems collection. If. for example, selection is cleared, SelectionChanged.AddedItems no longer contains any item (currently, it would contain a single 'null' item in this case).

The root cause for the raised duplicated SelectionChanged events is that the RadioButton control has in-built logic which automatically maintains single-selection for grouped RadioButtons. Two RadioButton controls belong to the same group if they share the same parent. With the current implementation of the RadioButtons control this is indeed the case: Each RadioButton has the same parent (the ItemsRepeater). As such, selecting a new RadioButton automatically raises the Unchecked event for the currently selected RadioButton, in turn raising the SelectionChanged event. Following this, the Checked event of the newly selected RadioButton is raised, again raising the SelectionChanged event.
This PR solves this issue by wrapping each RadioButton of the RadioButtons control in a unqiue parent grid, this ensuring that each RadioButton has a different parent. As such, selecting a RadioButton no longer automatically deselects the currently selected RadioButton. Instead, selection and deselection is now handled entirely by the RadioButtons control and thus we have full control when and how often to raise the SelectionChanged event.
Note: Listening to the RadioButton::Click event instead of the Checked and Unchecked events is not an option here as that event does not handle all possible selection cases. For example, programmatic selection of a RadioButton would be no longer recognized then, thus breaking the RadioButtons control.
The added interaction test to to verify if the SelectionChanged event is raised only once per selection logs each raised SelectionChangd event and then counts the number of these created logs per selection. If there is a mismatch (so SelectionChanged event has been raised anything else than exactly one time), verification fails.
The behavior of not passing 'null' elements to the SelectionChanged.*Items collections is covered by the added API test. Since there was no existing RadioButtons' APITests project, this PR is creating one.
Motivation and Context
Fixes #3128 and fixes https://github.com/microsoft/microsoft-ui-xaml/issues/3268.
How Has This Been Tested?
Added API and interaction tests.

@Felix-Dev can you merge master to pick up the CI build fix that just went in?

/azp run

@Felix-Dev The pipeline fix just went in, could you please merge master into this PR?

@StephenLPeters Since this PR is currently is waiting on PR #3194 I would like to wait for that PR to to be merged with master before merging with master here (this PR in its current form doesn't need to be run in the test pipeline anyway as its far from complete). Does that work for you?

yup makes sense

@StephenLPeters Merged with masters, added grid wrapping logic, improved tests.

In general I think it is good to cast your object to they widest type that fulfills your needs, for instance cast to toggle button instead of RadioButton when you are calling Check().  Or casting to Control instead of RadioButton when you want to call focus.   In general I think this strategy tends to enable more retemplating scenarios.  What if a consumer want to use RadioButtons with their CustomSuperCoolRadioButton which derives from toggle button.

What if a consumer want to use RadioButtons with their CustomSuperCoolRadioButton which derives from toggle button.

Given the current implementation, we would wrap that toggle button, which is not a RadioButton, in a RadioButton then: https://github.com/microsoft/microsoft-ui-xaml/blob/dc08d9b429755dd73e581d45764d61a4205f94d4/dev/RadioButtons/RadioButtonsElementFactory.cpp#L39
So when our RepeaterElementFactory instance is used here, we know that every item is actually a RadioButton here (ignoring its wrapping Grid element for now).
A developer could, however, pass a custom ItemTeplate to the ItemsRepeater used by a RadioButtons control which would instead use ToggleButtons instead of RadioButtons. Given that, we should probably allow the widest type possible here (which still makes sense) which would be a ToogleButton control.

Yeah, I think it would likely be fine to leave as is for radio buttons, but I don't think I see a downside of changing this and do see a minor upside.

@StephenLPeters

In general I think it is good to cast your object to they widest type that fulfills your needs, for instance cast to toggle button instead of RadioButton when you are calling Check(). Or casting to Control instead of RadioButton when you want to call focus.

See this case:
if (auto const radioButton = TryGetRadioButtonFromRepeaterElementIndex(focusedIndex, repeater))
{
    if (radioButton.Focus(winrt::FocusState::Programmatic))
    {
        return true;
    }
}

but there is also
if (auto const radioButton = TryGetRadioButtonFromRepeaterElementIndex(index, repeater))
{
    radioButton.IsChecked(containerIsChecked);
}

I guess I could change the return value TryGetRadioButtonFromRepeaterElementIndex() from type ToggleButton to, say, UIElement and then cast it in the above cases to either a Control or a ToggleButton but then I perhaps should change the method name (since it wouldn't return a "RadioButton" any longer but an "UIElement"). And I kinda prefer it named this way because it helps making it clear that we are actually working with RadioButtons here (wrapped inside a Grid). What do you think?

Maybe TryGetRadioButtonAsUIElement,  You probably don't need the FromRepeaterElementIndex part because its implied by the function parameters?

That could work, yeah.

@StephenLPeters I updated the implementation to make use of the widest types as possible (it now resembles the implementation before this PR). Please take a look.

/azp run

@Felix-Dev  looks like a real test failure.

@StephenLPeters Failing tests all run fine for me:

Looking at the Test pipeline output, for all failing tests this the same:
[Error]: System.Runtime.InteropServices.COMException (0x80040201): An event was unable to invoke any of the subscribers (Exception from HRESULT: 0x80040201)    at UIAutomationClient.IUIAutomationTreeWalker.GetFirstChildElementBuildCache(IUIAutomationElement element, IUIAutomationCacheRequest cacheRequest)

I fired up Narrator just to see if I notice anything but all seems fine to me. Any thoughts here?

/azp run

@Felix-Dev Looks like there are some merge conflicts.

@chingucoding If I merge with master now, I won't be able to run interaction tests in my local branch for this PR any longer since PR https://github.com/microsoft/microsoft-ui-xaml/pull/3359 hasn't yet been merged. I would like to wait until that PR has been merged so that in the meantime, if required, I can look into the failing interaction tests (in the test pipeline) again and won't be blocked here.
Thanks for the ping though.

Merged with master.

/azp run

/azp run

Thank you for submitting this PR, the current focus of the team is to assist our users in moving from WinUI 2 to WinUI 3. We are closing this PR as it does not address resolving a critical issue for WinUI 2 or WinUI 3.


Network resource \wsl$\ is invalid according to .NET's System.Uri

I'm on Windows 10 version 1909 [build 10.0.18363.476] and have Ubuntu 18.04 running in WSL.
I've noticed that some Windows apps have issues when accessing Linux paths as network resource in the form of \\wsl$\Ubuntu-18.04\some\dir.
In my case, these apps are using the .NET API System.Uri to validate uniform resource identifiers (URI).
I made some tests and concluded the problem is very likely that \\wsl$\ is an invalid machine name:

On one hand, \\wsl$\Ubuntu-18.04\some\dir is accessible as any normal directory, e.g. from the Windows Explorer.
On the other hand, validation of \\wsl$\Ubuntu-18.04\some\dir with methods like System.Uri.TryCreate fails.
Formally, this result seems to be correct to me, since \\wsl$\ is effectively an invalid name for network resources.

Here's a minimal example for reproduction with .NET Core 3.0:
using System;

namespace NetCoreApp
{
    class Program
    {
        static void Main()
        {
            string[] dirs = { "\\\\wsl$\\Ubuntu-18.04\\some\\dir", // WSL network resource (escaped)
                              "\\\\wsl\\Ubuntu-18.04\\some\\dir"}; // removed the dollar sign
            foreach (string dir in dirs)
            {
                Uri.TryCreate(dir, UriKind.RelativeOrAbsolute, out Uri uriCreated);
                if (uriCreated != null)
                    Console.WriteLine("Created URI: " + uriCreated + " from string " + dir);
                else
                    Console.WriteLine("Could not create an URI from string " + dir);
            }
        }
    }
}

The output is:
Could not create an URI from string \\wsl$\Ubuntu-18.04\some\dir
Created URI: file://wsl/Ubuntu-18.04/some/dir from string \\wsl\Ubuntu-18.04\some\dir

I am aware of https://github.com/microsoft/WSL/issues/4308, which I think is describing the same issue.
However, the problem is not limited to Visual Studio, but probably affecting any .NET app using URIs.

This seems like a .NET issue, not a WSL issue.

As far as I know, a valid hostname may only contain letters a-z, numbers 0-9 and minus -. That's what .NET is checking for and I think it actually does the right thing, because it sticks to the relevant RFCs.
It's a WSL design decision to deliberately use an invalid hostname wsl$. Or at least that's what I understand from this blog post (in particular the Q&A at the end of the post) written by @craigloewen-msft.
In other words: WSL has opted for a non-standard hostname. This can create problems with any software working with hostnames and expecting strict standard conformity. This includes, but is not limited to, the .NET Framework itself as well as apps built on top of it.

https://github.com/dotnet/runtime/issues/36595#issuecomment-637788627 seems they are planning to change the hostname to something else which doesn't violates the spec.

According to the release notes, this has been fixed in build 20175:
- Change \\wsl$ prefix to \\wsl to support URI parsing. The old \\wsl$ path is still supported.


[feature]: move cursor 10 lines down and up by pressing ctrl+ d and ctrl+y respectively

Is your feature already implemented in the latest master?
No
Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
Some editors like nvim and vim allows you to move the cursor 10 lines down by pressing ctrl+d and up by ctrl+y.
It would be cool to have this feature to move quickly throughout the list, playlist or search results.

It should already possible with PageSelectPreviousOrScrollUp and PageSelectNextOrScrollDown. You can configure the page size with page_size_in_rows config option.

It should already be possible with PageSelectPreviousOrScrollUp and PageSelectNextOrScrollDown. You can configure the page size with page_size_in_rows config option.

I mean, for vim/nvim users it would be great to do it using the ctrl + d and ctrl + u keybinding too.
Those two ways could live together. There are also other terminal applications that use the same keybindings to move around up and down. I'd be very nice to have it here too.

You can add bindings to ctrl+u and ctrl+d right?

You can add bindings to ctrl+u and ctrl+d right?

idk, it is possible? how?

Great, I didn't know about this. Anyway I think it would be great to have these keymaps built-in the app.


Adding a new  resource dir to sourceSets.commonMain is not affecting Res.drawable

Scenario
I'm implementing the android flavor strategy to my project. To do that I've added new source and resource dirs. Let's focus in the commomMain:
sourceSets {
    commonMain {
        kotlin.srcDir("src/commonFlavor1/kotlin")
        resources.srcDir("src/commonFlavor1/composeResources")
    }
}

In fact, I added new sources to each flavors (flavor1 and falvor2) and variantes(flavor1Debug, flavor1Release, flavor2Debug, flavor2Release)
sourceSets {
    commonMain {
        kotlin.srcDir("src/common${variant.flavor.flavorName.capitalized()}/kotlin")
        resources.srcDir("src/common${variant.flavor.flavorName.capitalized()}/composeResources")

        kotlin.srcDir("src/common${variant.variantName.capitalized()}/kotlin")
        resources.srcDir("src/common${variant.variantName.capitalized()}/composeResources")
    }
}

The object variant above is gotten according to gradle command been runned.
Problem
All the rouserces added in src/commonFlavor1/composeResources/drawable are not being processed and added to Res.drawable.
Workarrouund
As a way to "solve" this I've create a task to copy the necessary resources to build/generated/compose/resourceGenerator/preparedResources/commonMain/composeResources/.
Unfortunatelly It doesn't work right after a ./gradlew clean I don't know why
fun recursiveCopy(from: File, to: File) {
    if (!from.exists()) return
    from.listFiles()?.forEach { file ->
        if (file.name != ".DS_Store") {
            if (file.isDirectory) {
                val newDir = File(to, file.name)
                newDir.mkdir()
                recursiveCopy(file, newDir)
            } else {
                val destinationFile = File(to, file.name)
                if (destinationFile.exists()) {
                    println("Overwriting $destinationFile")
                    destinationFile.delete()
                }
                if (!destinationFile.parentFile.exists()) {
                    destinationFile.parentFile.mkdirs()
                }
                println("Copying $file to $to")
                file.copyTo(destinationFile)
            }
        }
    }
}

tasks.register("copyKmpResources") {
    doLast {
        println("\n\n--> Copying Flavored KMP Resources")
        val variant = BuildSrcConfig.Variant.getVariant(project = project, gradle = gradle)
        val projectDir = project.projectDir.absolutePath

        val fromFlavor = File(
            projectDir,
            "src/common${variant.flavor.flavorName.capitalized()}/composeResources/"
        )
        val fromVariant = File(
            projectDir,
            "src/common${variant.flavor.flavorName.capitalized()}/composeResources/"
        )

        val destination = "build/generated/compose/resourceGenerator/preparedResources/commonMain/composeResources/"

        println("destination:\n  $destination")
        val destinationFile = File(projectDir, destination)
        println(" - copying \"$fromFlavor\" to \"$destinationFile\"")
        recursiveCopy(fromFlavor, destinationFile)
        println(" - copying \"$fromFlavor\" to \"$destinationFile\"")
        recursiveCopy(fromVariant, destinationFile)
    }
}

tasks.named("prepareComposeResourcesTaskForCommonMain").configure {
    dependsOn("copyKmpResources")
}

Affected platforms

Desktop (Windows, Linux, macOS)
iOS
Web (K/Wasm) - Canvas based API
Android

Versions

Libraries:

org.jetbrains.compose: 1.6.10

Kotlin version: 2.0.0
OS version: MAC OS 14.5
OS architecture: arm64

To Reproduce
Steps to reproduce the behavior:

Add a new composableResource to commomMain

sourceSets {
    commonMain {
        resources.srcDir("src/commonFlavor1/composeResources")
    }
}

Add a new file in the drawable folder in this new source.

e.g.: src/commonFlavor1/composeResources/drawable/icon.xml

Rebuild the project
Check Res.drawable availble items, "icon" will not be an option

Expected behavior
As I've added a new source dir to sourceSets -> commomMain -> resources, I expected that the new resources can be used normally.
Additional context
Adding a new source dir to .kt files has worked as expected, only the composeResources doesn't.
I hope I'm not duplicating a bug, I search for similar issues but I wasn't  able to find
Tks.

I'm implementing the android flavor strategy to my project. To do that I've added new source and resource dirs.

Please don't! The projects source sets are not for the flavoring. The flavoring as you described is the android specific thing. If you need to have different logic/resources then use gradle modules

Anyway, for resourc directory customization there was implemented a feature:
https://github.com/JetBrains/compose-multiplatform/pull/5016

Additional info:
There is no resources in Kotlin Multiplatform!
sourceSets {
commonMain {
kotlin.srcDir("...") // <- adds new source directory to the kotlin source set
resources.srcDir("...") // <- meaningless for the kotlin multiplatform
}
}

The task in the kotlin tracker: https://youtrack.jetbrains.com/issue/KT-33432/MPP-build-variant-feature

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


from django.forms.widgets import get_default_renderer

Hi, i am using django-ckeditor in my application, and find the following alert when i am trying to start app
File "/Users/cnbraid/PycharmProjects/blogadmin/blog/models.py", line 5, in <module>     from ckeditor.fields import RichTextField   File "/Users/cnbraid/.virtualenvs/django1.10.6/lib/python2.7/site-packages/ckeditor/fields.py", line 6, in <module>     from .widgets import CKEditorWidget   File "/Users/cnbraid/.virtualenvs/django1.10.6/lib/python2.7/site-packages/ckeditor/widgets.py", line 12, in <module>     from django.forms.widgets import get_default_renderer

widgets rendering was changed in Django 1.11 and get_default_renderer was introduced.
It's not an error with the project you are using unsupported version of Django.
Consider updating Django or use older version of django-ckeditor.
According to this you might be looking for versions prior to 5.6.0 but I don't know for sure.

Get!
finally , i tried md-editor for my blog.
Thank you very much.


Make a new release of the library

The library still fails to install with the arduino-cli and with IDE2.x
$ arduino-cli lib install "OpenMV Arduino RPC"
Error installing OpenMV Arduino RPC: No valid dependencies solution found: dependency 'SoftwareSerial' is not available

The problem seems to have been fixed in https://github.com/openmv/openmv-arduino-rpc/pull/9 and already merged, but not yet part of a release: https://github.com/openmv/openmv-arduino-rpc/blob/v1.0.7/library.properties#L10

Done: https://github.com/openmv/openmv-arduino-rpc/releases/tag/v1.0.8


"-0" should be parsed as -0 instead of 0

assert_eq!(parse("-0").unwrap(), -0f64);
assert_eq!(parse("-0").unwrap(), JsonValue::Number(-0f64));

Both pass fine for me.

You are right, I can't reproduce it either. I may have been confused by https://github.com/maciejhirsz/json-rust/issues/42#issuecomment-229131194: -0f64 gets printed as 0e0 but parsing seems right.
Side note - that is actually not the right assert because -0f64 and 0f64 are equal:
assert_eq!(-0f64, 0f64);

The correct one is:
assert!(!json::parse("-0").unwrap().as_f64().unwrap().is_sign_positive())


Add release version to oapi file

Here
https://github.com/ethereum/builder-specs/blob/b66471c67f24b6c29a3e5461720c8620310815c6/builder-oapi.yaml#L22
Either at release time or in master should indicate the release version

Thank you for bringing this to my attention. I will make sure to add the release version to the oapi file in the specified location. This will help provide clarity and ensure that users can easily identify the release version.


The sns:ListTagsForResource API call 408 timeout errors should be handled as retryable

Describe the bug
SNS can throw an error:
ERROR: rpc error: code = Unknown desc = operation error SNS: ListTagsForResource, https response error StatusCode: 408, RequestID: , api error UnknownError: UnknownError (SQLSTATE HV0000
This error doesn't seem to be marked as retryable though by AWS, but should be if it's truly a 408 (timeout) error
Steampipe version (steampipe -v)
v0.19.0-rc.2
Plugin version (steampipe plugin list)
v0.93.0
To reproduce
Create 10,000+ SNS topics, and run select * from aws_sns_topic
Expected behavior
The request for listing tags is retried until it hits the maximum number of attempts
Additional context
Related issue in SPC: https://github.com/turbotio/steampipe-cloud/issues/1762

Attempted to look at this as part of something else by adding a DefaultRetryConfig to the table:
func snsRetryConfig() *plugin.RetryConfig {
	return &plugin.RetryConfig{
		MaxAttempts:          20,
		BackoffAlgorithm:     "Exponential",
		RetryInterval:        1000,
		CappedDuration:       240000,
		ShouldRetryErrorFunc: snsRetryError,
	}
}

func snsRetryError(ctx context.Context, d *plugin.QueryData, h *plugin.HydrateData, err error) bool {
	if strings.Contains(err.Error(), "StatusCode: 408") {
		plugin.Logger(ctx).Debug("snsRetryError", "retrying 408", err.Error())
		return true
	}
	if strings.Contains(err.Error(), "no such host") {
		plugin.Logger(ctx).Debug("snsRetryError", "no such host", err.Error())
		return true
	}
	return false
}

This then retries these errors (& those matching the no such host issue) until it eventually failed with:
Error: table 'aws_sns_topic' column 'tags_src' requires hydrate data from listTagsForSnsTopic, which failed with error operation error SNS: ListTagsForResource, exceeded maximum number of attempts, 9, https response error StatusCode: 0, RequestID: , request send failed, Post "https://sns.eu-west-1.amazonaws.com/": dial tcp <IP_ADDRESS>:443: connect: can't assign requested address.
(SQLSTATE HV000)

More info on internal slack


The LyCORIS button is not displayed

I use SD 1.6.0 no button is displayed on web ui

Your model should be displayed in lora tab
you can check the readme or other issue

I tried to use a LyCORIS model I moved the file to the Lora folder I integrate it as soon as possible it writes lora:avaryana:1 instead of lyco

yes
it should be lora:

okay thx ^^


Non complete results

When i use Tweepy to search Tweets it get for me some number much smaller than real results can be seen in search of Twitter itself. I use cursors but it get me for example 122 tweets while there are a lot of tweets in reality. What is the problem?

If you're using the standard search, note, from Twitter's API documentation:

The Twitter Search API searches against a sampling of recent Tweets published in the past 7 days.
Before digging in, it’s important to know that the standard search API is focused on relevance and not completeness. This means that some Tweets and users may be missing from search results. If you want to match for completeness you should consider the premium or enterprise search APIs.

https://developer.twitter.com/en/docs/tweets/search/overview/standard

Please note that Twitter's search service and, by extension, the Search API is not meant to be an exhaustive source of Tweets. Not all Tweets will be indexed or made available via the search interface.

Keep in mind that the search index has a 7-day limit. In other words, no tweets will be found for a date older than one week.

https://developer.twitter.com/en/docs/tweets/search/api-reference/get-search-tweets.html

The Search API is not complete index of all Tweets, but instead an index of recent Tweets. The index includes between 6-9 days of Tweets.

https://developer.twitter.com/en/docs/tweets/search/guides/standard-operators


CC69815: Adding final quotes to SQL command

Hello, @mairaw ,
This proposed file change comes from https://github.com/dotnet/docs.ru-ru/pull/124.
Could you review this contribution and help to merge if agreed?
Many thanks in advance.

Thanks @douglaslMS


Add step to create database user if it doesn't exist

Setting up a new computer helps find these things 😀

Coverage remained the same at 81.625% when pulling c42479c0b0605b63f2dc358f363a5b648c3b1906 on fix-setup-instructions into 29499bca417e575884782d8e0ea088150076b0a4 on master.


20210922 minor revisions

PR progress checklist (to be filled in by reviewers)

[ ] Changes to documentation are appropriate (or tick if not required)
[ ] Changes to tests are appropriate (or tick if not required)
[ ] Reviews completed

What type of PR is this?

Primary type

[ ] [build]    Changes related to the build system
[ ] [chore]    Changes to the build process or auxiliary tools and libraries such as documentation generation
[ ] [ci]       Changes to the continuous integration configuration
[ ] [feat]     A new feature
[x] [fix]      A bug fix
[ ] [perf]     A code change that improves performance
[ ] [refactor] A code change that neither fixes a bug nor adds a feature
[ ] [revert]   A change used to revert a previous commit
[ ] [style]    Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)

Secondary type

[x] [docs]     Documentation changes
[ ] [test]     Adding missing or correcting existing tests

Does this PR introduce a BREAKING CHANGE?

No.
Related issues and/or pull requests

Describe the changes you're proposing

Removing file references in osfamilymap.sls, as param.sls acts on config.location as a directory.
Pillar / config required to test the proposed changes

Debug log showing how the proposed changes work

Documentation checklist

[ ] Updated the README (e.g. Available states).
[ ] Updated pillar.example.

Testing checklist

[ ] Included in Kitchen (i.e. under state_top).
[ ] Covered by new/existing tests (e.g. InSpec, Serverspec, etc.).
[ ] Updated the relevant test pillar.

Additional context

Thanks, @bbilyeu !

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


⚠ GitLab Server has degraded performance

In 5c5019d, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 6826 ms

Resolved: GitLab Server performance has improved in b3c222c.


JIT accessors are correctly updated when plugins block is edited in IDEA

Relates to #338.

Classpath is being recomputed correctly after editing the plugins block but it seems IntelliJ is failing to re-index the generated jars:

Reported as https://youtrack.jetbrains.com/issue/KT-17770


Pass type in path instead of query. Change full to diff

@dschowta is this ready to merge?
The spec has been updated:

https://github.com/w3c/wot-discovery/pull/196
https://github.com/w3c/wot-discovery/pull/198

yes it is ready to be merged


Fix #1107 -- validate GitHub usernames

Fixes #1107.

Please hold on with merging until we figure out in issue #1107 what to do about invalid GitHub usernames.

Suggestion. You may want to use PyGitHub's get_user method to verify is the user exists.

Suggestion. You may want to use PyGitHub's get_user method to verify is the user exists.

Let's do this in another issue: #1139

Any particular reason to define a field in itself, rather than adding a RegexValidator to the existing fields?

No particular reason except that in the future it'll be easier to add a new behavior (i.e. adding new validation rule, like verifying if the user exists) to all GitHub fields.

So what is actually blocking us here?

It's blocked by corresponding issue, that is #1107. This issue needs feedback from @maneesha regarding what to do with existing records with invalid GitHub usernames.

Superseded by #1281.


Muon defaults to ~/.config/brave

Muon version: 5.0.2
Operating system: Linux, Debian

When I run Muon, it defaults to create the LocalStorage, Cookies & Cache to:
 ~/.config/brave

The expected behavior is that creates a new directory (electron does this):
 ~/.config/name

The name parameter is the one specified in package.json
I assume this will also create an issue for the brave browser if application developers start throwing a wrench in the brave folder.

Work around:
We can reset the userData path, to a custom one. (Do this really early, before the app emits the "ready" event)
app.setPath("userData", util.getCustomUserPath());

along with:
function getCustomUserPath() {
    // small hack, userData points to  ~/.config/brave/
    // instead of ~/.config/particl-desktop
    return path.join(path.dirname(app.getPath('userData')), 'particl-desktop');
}

This workaround is not a complete fix, the 'brave' folder is still being generated, however the local storage, cookies and cache seem to have moved. The files are still shared:
user@host:~/.config/brave$ ls
CrashPad  Extensions  Local State  ShaderCache

maybe related to https://github.com/electron/electron/issues/11858

The Tor data dir also resides within the user data directory - I hope that the setPath() fix also makes sure the Tor data dir isn't shared between Muon & other applications.


iox-#234 Only run DDS tests when DDS Gateway is built.

Signed-off-by: Ithier Jeff (CC-AD/EYF1<EMAIL_ADDRESS>

This fixed #234


Create a website for displaying registry

This is not in scope for this extension, but this issue has to go somewhere, so I'm posting it here.

We have registered the iso24229.org domain for publishing the ISO 24229 registry.


New Component: Switch Chain Modal

Many dApps require a functionality for user to be able to switch chains. Even though this component wouldn't use Moralis it could still be a nice useful component for the web3uikit.

@0xTijan can you outline how this would work?

Hey Bill 👋
This would be a dropdown or modal (not sure yet) like in the 1inch or gnosis safe apps for example. When user selects a chain they want to switch to, Metamask pops up for user to approve that. The component would need to have at least 2 props:

currentChain
and chainList - array of wanted chains (EVM) to be in the dropdown or modal

But after looking at a dropdown component this new switch chain component maybe isn't needed at all? 😅
1inch example

Gnosis Safe example

It would have been a nice addition but since moralis servers are going to be deprecated soon i don't think adding this to web3 package is worth it sorry 😅
but we can add it to the new package once we have it ready in future what do you think?

Yeah, makes sense 😃

yeah i'm pretty close to adding the new web3 section @0xTijan , just some final things to workout about how to use NextJS pages with server side rendering in Storybook and make it useful to export to the end dev. Then this will be very nice. I do not think we need more UI for it, maybe just an array of chains would be passed and we would render the @AbhinavMV Select Component with the correct text and logos, then on change it could return the chain ID

i marked this blocked for now until i have the new slice ready, but you could actually add it to the Form section for now if you want @0xTijan

FYI @0xTijan i have added this to web3
I am using this tag to collect idea for the next iteration of the web3 section of the kit and i think this is a great idea! 🤩


Usage of Macros Effectively for CP

Description
I would like to add a documentation on how to use macros while doing CP
Domain
Competitive Programming
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign


[RiskIQ - EASM - Defender EASM] API Review

New API Review meeting has been requested.
Service Name: RiskIQ - EASM - Defender EASM
Review Created By: Philip Wood @mspwood
Review Date: 07/18/2023 01:00 PM PT
Onboarding Record: https://dev.azure.com/azure-sdk/Release/_workitems/edit/14798
PR: https://github.com/Azure/azure-rest-api-specs/pull/24465
Hero Scenarios Link: here
Core Concepts Doc Link: here
Description: - Add a new Microsoft.Easm Dataplane Version 2023-05-01-preview.

Support exporting assets for a provided filter.
Support a unified observations endpoint for paginated retrieval of observations related to an asset.

Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here

Meeting updated by Philip Wood
Service Name: RiskIQ - EASM - Defender EASM
Review Created By: Philip Wood
Review Date: 07/18/2023 01:00 PM PT
Onboarding Record: https://dev.azure.com/azure-sdk/Release/_workitems/edit/14798
PR: https://github.com/Azure/azure-rest-api-specs/pull/24465
Hero Scenarios Link: here
Core Concepts Doc Link: here
Description: - Add a new Microsoft.Easm Dataplane Version 2023-05-01-preview.

Support exporting assets for a provided filter.
Support a unified observations endpoint for paginated retrieval of observations related to an asset.

Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here

Meeting updated by Philip Wood
Service Name: RiskIQ - EASM - Defender EASM
Review Created By: Philip Wood
Review Date: 07/18/2023 01:00 PM PT
Onboarding Record: https://dev.azure.com/azure-sdk/Release/_workitems/edit/14798
PR: https://github.com/Azure/azure-rest-api-specs/pull/24465
Hero Scenarios Link: here
Core Concepts Doc Link: here
Description: - Add a new Microsoft.Easm Dataplane Version 2023-05-01-preview.

Support exporting assets for a provided filter.
Support a unified observations endpoint for paginated retrieval of observations related to an asset.

Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here

We have two open API Review issues for "RiskIQ - EASM - Defender EASM" -- this one and #24887. Can we consolidate to just one of these or are they tracking different updates?

Closing this issue -- we'll use #24887 to track this work.


Option to disable calling home to musikcube.com at startup

I notice that musikcube connects to musikcube.com at startup. Can this be made optional? I'm running version 0.21.1 on macOS.

Yep, we should do this.

This will be in subsequent releases.
https://github.com/clangen/musikcube/commit/d4a88e2085e844b9f9c06beeb16ddcf77ed5d430
Resolving.


Installation errors

I tried various methods on both Windows and Linux, using both Conda and regular Python, but I still encountered errors. See below:
pip install segment-geospatial

Collecting git+https://github.com/opengeos/segment-geospatial
Cloning https://github.com/opengeos/segment-geospatial to [c:\users\trant\appdata\local\temp\pip-req-build-4o96yej_](file:///C:/users/trant/appdata/local/temp/pip-req-build-4o96yej_)
Resolved https://github.com/opengeos/segment-geospatial to commit 1157a6c8df545f70e7859aaa48f4c810fa15f4fe
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'done'
Preparing metadata (pyproject.toml): started
Preparing metadata (pyproject.toml): finished with status 'done'
Collecting fiona (from segment-geospatial==0.12.3)
Using cached fiona-1.10.1-cp313-cp313-win_amd64.whl.metadata (58 kB)
Collecting gdown (from segment-geospatial==0.12.3)
Using cached gdown-5.2.0-py3-none-any.whl.metadata (5.8 kB)
Collecting geopandas (from segment-geospatial==0.12.3)
Using cached geopandas-1.0.1-py3-none-any.whl.metadata (2.2 kB)
Collecting huggingface_hub (from segment-geospatial==0.12.3)
Using cached huggingface_hub-0.26.2-py3-none-any.whl.metadata (13 kB)
Collecting ipympl (from segment-geospatial==0.12.3)
Using cached ipympl-0.9.4-py3-none-any.whl.metadata (8.7 kB)
Collecting leafmap (from segment-geospatial==0.12.3)
Using cached leafmap-0.41.1-py2.py3-none-any.whl.metadata (16 kB)
Collecting localtileserver (from segment-geospatial==0.12.3)
Using cached localtileserver-0.10.5-py3-none-any.whl.metadata (5.2 kB)
Collecting matplotlib (from segment-geospatial==0.12.3)
Using cached matplotlib-3.9.2-cp313-cp313-win_amd64.whl.metadata (11 kB)
Collecting opencv-python-headless (from segment-geospatial==0.12.3)
Using cached opencv_python_headless-<IP_ADDRESS>-cp37-abi3-win_amd64.whl.metadata (20 kB)
Collecting patool (from segment-geospatial==0.12.3)
Using cached patool-3.1.0-py2.py3-none-any.whl.metadata (4.3 kB)
Collecting pycocotools (from segment-geospatial==0.12.3)
Using cached pycocotools-2.0.8.tar.gz (24 kB)
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'done'
Preparing metadata (pyproject.toml): started
Preparing metadata (pyproject.toml): finished with status 'done'
Collecting pyproj (from segment-geospatial==0.12.3)
Using cached pyproj-3.7.0-cp313-cp313-win_amd64.whl.metadata (31 kB)
Collecting rasterio (from segment-geospatial==0.12.3)
Using cached rasterio-1.4.2-cp313-cp313-win_amd64.whl.metadata (9.4 kB)
Collecting rioxarray (from segment-geospatial==0.12.3)
Using cached rioxarray-0.18.1-py3-none-any.whl.metadata (5.4 kB)
Collecting sam2 (from segment-geospatial==0.12.3)
Using cached sam2-0.4.1.tar.gz (75 kB)
Installing build dependencies: started
Installing build dependencies: finished with status 'error'
Running command git clone --filter=blob:none --quiet https://github.com/opengeos/segment-geospatial 'C:\Users\trant\AppData\Local\Temp\pip-req-build-4o96yej_'
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> [4 lines of output]
Collecting setuptools>=61.0
Using cached setuptools-75.6.0-py3-none-any.whl.metadata (6.7 kB)
ERROR: Could not find a version that satisfies the requirement torch>=2.3.1 (from versions: none)
ERROR: No matching distribution found for torch>=2.3.1
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.

Please use conda to install packages on Windows. You will have a hard time trying to install torch related packages on Windows using pip.
See https://samgeo.gishub.org/installation/#install-from-conda-forge


Should "preconnect" point to fonts.googleapis.com?

I had my automatic font optimization go out on my projects (as detailed in https://dev.to/ekafyi/first-impressions-on-next-js-automatic-font-optimization-32a1 ), which I'm in the process of fixing tonight.

Huh???
So anyway I was looking at my configuration, and I noticed something.
https://github.com/timlrx/tailwind-nextjs-starter-blog/blob/89d21c3a597608773c30655e2b150d34a791ffa0/pages/_document.js#L25
Shouldn't this preconnect match the domain currently used?
https://github.com/timlrx/tailwind-nextjs-starter-blog/blob/89d21c3a597608773c30655e2b150d34a791ffa0/pages/_document.js#L27

i.e.
<link rel="preconnect" href="https://fonts.googleapis.com" crossOrigin="anonymous" />

Mmm apparently not according to e.g. https://github.com/ekafyi/example-nextjs-webfont-optimization/blob/with-custom-document/pages/_document.tsx#L26-L29
It looks like preconnect will be handled in an upcoming Next release too https://github.com/vercel/next.js/discussions/24645
I'm gonna close the issue 😁


Using deepGPy choleskies?

In coldeep.py there is a line:
from GPy.util.choleskies import indexes_to_fix_for_low_rank
But within the package there is a choleskies.py file containing the same function.  Do you mean to use the GPy version?

Hi Dan,
Yeah, there's some functionality that was written for DeepGPy that I later
moved (copied) into GPy because it was more generally useful, so sometimes
there will be a clash.
Cleaning up DeepGPy is on the agenda!
James.
On 22 September 2015 at 19:23, Dan Marthaler<EMAIL_ADDRESS>wrote:

In coldeep.py there is a line:
from GPy.util.choleskies import indexes_to_fix_for_low_rank
But within the package there is a choleskies.py file containing the same
function. Do you mean to use the GPy version?
—
Reply to this email directly or view it on GitHub
https://github.com/SheffieldML/deepGPy/issues/4.

Sounds good James.  Does this still imply that the devel branch of GPy is the one to link to?  Or will you be linking to the master branch after the cleanup?
And I think we can close this issue.
Dan

Hi Dan,
I think everything should work with GPy 0.8 now.
James.
On 23 September 2015 at 16:02, Dan Marthaler<EMAIL_ADDRESS>wrote:

Sounds good James. Does this still imply that the devel branch of GPy is
the one to link to? Or will you be linking to the master branch after the
cleanup?
And I think we can close this issue.
Dan
—
Reply to this email directly or view it on GitHub
https://github.com/SheffieldML/deepGPy/issues/4#issuecomment-142630080.


Feat/fam integration cleanup

#311 - Continue from FAM Integration to clean up unused code (Keycloak and Siteminder).

Thanks for the PR!
Any successful deployments (not always required) will be available below.

api
admin
public

Once merged, code will be promoted and handed off to following workflow run.

Main Merge Workflow

Close this PR as it is merged into #287 and merged to main.


Will the messages of the inner event hubs which created by kafka connect  automimatically will expire after  "Message Retention"?

[Enter feedback here]
Will the messages of the inner event hubs which created by kafka connect  automatically will expire after  "Message Retention"?

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

ID: 1800bc69-1c54-7bb5-d127-0b5a94d3762d
Version Independent ID: 7d829763-6a0f-fb98-8df7-28f3684a1690
Content: Integrate Apache Kafka Connect on Azure Event Hubs with Debezium for Change Data Capture - Azure Event Hubs
Content Source: articles/event-hubs/event-hubs-kafka-connect-debezium.md
Service: event-hubs
GitHub Login: @abhirockzz
Microsoft Alias: abhishgu

@HuaqiongWu , thank you for your query. We'll review this and get back to you shortly!

@spelluru Could you please share inputs on the above ask?

@abhirockzz - could you please answer when you get a chance? Thanks!

@HuaqiongWu - I have confirmed with the product team that the message retentions policies apply to these inner event hubs as well. Thanks.
#please-close


make random-beans-validation more random (fixes #237)

Just an idea, not yet ready for merge.
Needs more though and I'm pretty tired at the moment.

Coverage decreased (-0.5%) to 90.523% when pulling 66e396a2941d2e6acacfd229b6e290d0938559e8 on PascalSchumacher:#237 into d4a47dd6e62fe589f2fcaa8d1668cc8b0c168ee4 on benas:master.

Coverage decreased (-0.5%) to 90.523% when pulling a230c1662f6651a0accec94ea4be08b59d63e5ed on PascalSchumacher:#237 into d4a47dd6e62fe589f2fcaa8d1668cc8b0c168ee4 on benas:master.

@benas What do you think?

Coverage decreased (-0.5%) to 90.523% when pulling bb16b8a1c2736fa12f20af37385317dac3f56d58 on PascalSchumacher:#237 into d4a47dd6e62fe589f2fcaa8d1668cc8b0c168ee4 on benas:master.

perfect. This is what I also had in mind to fix this.


chore(proto): allow same type for rpc response

What's changed and what's your intention?
Remove ExecuteResponse as it is the same as GetDataResponse.
We add two configurations into buf.yaml to enable so.

We can also use CreateTaskRequest to replace ExecuteRequest, @liurenjie1024


Tensorflow Docs not working?

hey ,i want to train a object detector and want to do it in tensorflow..rather than MxNet...heres what i m doing following the docs provided on djl website :
MY SETUP
!curl -O https://raw.githubusercontent.com/aws-samples/d2l-java/master/tools/colab_build.sh && bash colab_build.sh !sudo rm /usr/local/cuda !ln -s /usr/local/cuda-10.1 /usr/local/cuda !ln -s /usr/local/cuda/lib64/libcudart.so /usr/lib64-nvidia !nvcc --version !python3 install.py --sys-prefix !pip install pyngrok --quiet
DEPENDENCY PART
%maven org.slf4j:slf4j-api:1.7.26 %maven org.slf4j:slf4j-simple:1.7.26 %maven net.java.dev.jna:jna:5.3.0 %maven ai.djl:basicdataset:0.10.0 %maven ai.djl:api:0.10.0 %maven ai.djl:model-zoo:0.10.0 %maven ai.djl.tensorflow:tensorflow-native-auto:2.3.1 %maven ai.djl.tensorflow:tensorflow-engine:0.10.0 %maven ai.djl.tensorflow:tensorflow-model-zoo:0.10.0 %maven ai.djl.tensorflow:tensorflow-api:0.10.0
My imports:
import ai.djl.Application; import ai.djl.Model; import ai.djl.ModelException; import ai.djl.engine.Engine; import ai.djl.inference.Predictor; import ai.djl.modality.cv.Image; import ai.djl.modality.cv.ImageFactory; import ai.djl.modality.cv.output.BoundingBox; import ai.djl.modality.cv.output.DetectedObjects; import ai.djl.modality.cv.output.Rectangle; import ai.djl.modality.cv.util.NDImageUtils; import ai.djl.ndarray.NDArray; import ai.djl.ndarray.NDList; import ai.djl.ndarray.NDManager; import ai.djl.ndarray.types.DataType; import ai.djl.repository.zoo.Criteria; import ai.djl.repository.zoo.ModelZoo; import ai.djl.repository.zoo.ZooModel; import ai.djl.training.util.ProgressBar; import ai.djl.translate.Batchifier; import ai.djl.translate.TranslateException; import ai.djl.translate.Translator; import ai.djl.translate.TranslatorContext; import ai.djl.util.JsonUtils; import com.google.gson.annotations.SerializedName; import java.io.IOException; import java.io.InputStream; import java.net.URL; import java.nio.charset.StandardCharsets; import java.nio.file.Files; import java.nio.file.Path; import java.nio.file.Paths; import java.util.ArrayList; import java.util.List; import java.util.Map; import java.util.Objects; import java.util.Scanner; import java.util.concurrent.ConcurrentHashMap; import org.slf4j.Logger; import org.slf4j.LoggerFactory;
testing:
var engine=Engine.getInstance().getEngineName(); engine
ERROR  I M GETTING
ai.djl.engine.EngineException: No deep learning engine found. Please refer to https://github.com/awslabs/djl/blob/master/docs/development/troubleshooting.md for more details. 	at ai.djl.engine.Engine.getInstance(Engine.java:120) 	at .do_it$Aux(#99:1) 	at .(#99:1)
WHAT I M DOING WRONG
when hitting this code on python enviornment
import tensorflow as tf print(tf.__version__)
out:2.4.1
..tensorflow 2.4 is there ..how to make it work in djl ...guide me pleaase

@nikkisingh111333 we don't support TensorFlow training. Currently only MXNet engine is fully supported for training capability. PyTorch is still working in progress and has not yet well-tested.

okk so it means i cannot import tensorflow model which i hve trained on
teachable machine into djl...please i want to ask few things:
1.how can i train ssd model oer any other object detector in djl..i mean
fine tune it..all example i m seeing are just using pre trained model
instead of training them on out own dataset
2.when will be TF for djl
please i want to create some awesome projects which i m unable to do since
i cannot find right AI environment in java ..i m Counting on DJL..
On Mon, 12 Apr 2021 at 19:59, Jake Lee @.***> wrote:

@nikkisingh111333 https://github.com/nikkisingh111333 we don't support
TensorFlow training. Currently only MXNet engine is fully supported for
training capability. PyTorch is still working in progress and has not yet
well-tested.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/awslabs/djl/issues/846#issuecomment-817860594, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AL3BT7ESTSWBUSVTAEOKYQTTIL7URANCNFSM42ZJNP5A
.

You can find examples of training in https://github.com/awslabs/djl/tree/master/examples/src/main/java/ai/djl/examples/training


Camera disconnected

Margo stopped experiment with 3:03:01 left in a 24h long experiment (computer 3). The camera was connected...I restarted margo and played with the camera settings, we'll see if it errors out again.

This is a hardware issue. MARGO should throw up an error if the camera suddenly disconnects.


Use crawl_model.status to signal "stop" to rq workers

... instead of a sentinel file.

Reverted to a simple crawl runner instead of job queues.


[BEAM-7856] Re Raise exception for code other than 409

Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @chamikaramj

LGTM. Thanks.


Gson support

Is your enhancement request related to a problem? Please describe.
In our projects we are using Gson not Jackson for Json serialization/deserialization. On top of that we make use of immutables (immutables.org) to define our data objects. Getters and setters are of the form field(), field(type data) not getField(), setField(...). When passing these data classes to JSONSchema.of() the fields are not recognized and we end up with null data in the topic when sending messages using a producer.
Another problem is that in some cases we use json adapters to create a json representation that is different from how the fields are represented in the data class.
At this point it is not possible to set your own JSON schema and pass the JSON string representation instead of the data object.
The SchemaBuilder does not seem to support schema's of type "JSON" .
I tried passing a schema that was created by the JSONSchema class using
String json = JSONSchema.of(Data.class).getSchemaInfo().toString() and then passing the resulting string to
SchemaDefinition.builder().withJsonDef(json).build()
This produces org.apache.avro.SchemaParseException: Type not supported: JSON)
Describe the solution you'd like
Support of JSON schema's in the SchemaDefinition builder. Some documentation on JSON schema's would also be nice.
Support for passing the json representation (string) instead of a POJO.
Direct support for Gson and immutables would be nice.
It would also be nice to be able to specify a limited set of fields to be stored. The json representation of the data object should then be stored as a separate string field.
Describe alternatives you've considered
Switching to Jackson is not an option. Our whole code base is based on Gson for Json related stuff.
Creating mirror classes to convert our immutables to plain and simple POJO's but that's way too much work and a maintenance nightmare.
Additional context
Using version 2.7.1

I don't think this issue is so much about Gson support as it is about making it easy to generate schemas via other means, using other libraries. We've had similar challenges with pulsar4s and generating JSON schemas to support various Scala JSON libraries.
In my opinion the JSON schema support should be entirely pluggable. The core Schema interface should exist in the pulsar client library, and there should be separate libraries that implement it for Jackson, Gson, json4s, etc.

I completely agree. Another problem is the current reliance on getter/setter method to determine the properties of the POJO. Immutables (immutables.org) work with builders instead of setter methods and by default the getter methods for properties are not prefixed with 'get'.

The issue had no activity for 30 days, mark with Stale label.


eslint-plugin-graphql is deprecated

Overview
This is just a heads up that eslint-plugin-graphql  is deprecated and they're recommending switching to graphql-eslint.
Motivation

What inspired this enhancement? What makes you think this should be included?

I found it out about it while tracing dependencies for a dependabot security alert (CVE-2022-0235).
Labels

[ ] Add the Type: Enhancement label to this issue.

Area

[ ] Add any relevant Area: <area> labels to this issue

Scope

Is this issue related to a specific package?

[ ] Tag it with the Package: <package_name> label.

Checklist

[ ] Please delete the labels section before submitting your issue
[ ] I have described this issue in a way that is actionable (if possible)

👍 I was considering working on this during HackDays but I’ll probably be working on something else instead.
What first got me to look into this a few weeks ago was that I found out the rule that enforces fetching ids when available is not working right now, at least not on Shopify/web. It can cause a lot of issues and I think it’s another good reason to switch over to graphql-eslint and their require-id-when-available rule.

👍 I was considering working on this during HackDays but I’ll probably be working on something else instead.
What first got me to look into this a few weeks ago was that I found out the rule that enforces fetching ids when available is not working right now, at least not on Shopify/web. It can cause a lot of issues and I think it’s another good reason to switch over to graphql-eslint and their require-id-when-available rule.


Validator substate fetching problem

Problem
A user may provide an unspecified number of inputs. It becomes the validators responsibility to fetch these from remote nodes (which it technically has to connect to anyway). This could cause a massive burden on system resources and lots of queuing.
Possible solutions:
a. A user transaction must submit all substates for execution.
This would typically happen through the indexer.
If the user provides incorrect substates, this will be caught in the consensus as a foreign shard will vote to ABORT.
Pros:

Simple

Cons:

new transaction message sizes may be big (what is the upper bound?)
user data may become out of date quickly
potential for abuse

b. Foreign shards send their local substates along with the transaction to other remote shards.
Execution occurs once all substates are received. To reduce the validator burden, we could also require the user to submit the transaction to at least one replica in all shards involved.
Pros:

transactions with  erroneous inputs are never executed/are ABORTed without executing
vns that are not involved can simply discard the transaction (we assume that only input shard vns can submit to output shard vns)

Cons:

transactions may include inputs shards that arent actually used by the transaction to waste vn resources (fees should account for this assuming we are able to cheaply validate the validity of fee_instructions)

c. Execute once substates are exchanged in consensus
Add another initial stage where substates are received and execution takes place once consensus has begun. Transactions start with transactions in the <New, is_ready=true> -> <Proposed, is_ready=false> state, and once all substates are received <Proposed, is_ready = true>
Pros:

transactions with  erroneous inputs are never executed/are ABORTed without executing

Cons:

extra round of consensus
cannot tell what the output shards are until later

I like option A


Decide where and how to parse bibtex to structured data

We have different options to what data the API of JabRef online takes as input.
Option A: Similar to bibtex, the value of each field as a simple string. For example, journal = 'Journal of Mathematical Physics' or authors='Tobias Diez and Gerd Rudolph'. Latex code is left untouched and pushed to the server as is.

Advantages:

1:1 conversion with bibtex
Sync via JabRef online gives exactly the same bib file

Disadvantages:

Need to reimplement parsing of certain field values. For example, the author parser.
Makes it harder to match metadata to other structured data. For example, authors need first be parsed before they can be matched with a database of known authors to get e.g. their orcid.
Need additional data that might depend on the user configuration, e.g. the keyword separator.

Option B: A structured representation of the metadata, where each field has a predefined valid format. For example, the bibtex journal and journaltitle are mapped to
 journal:
    name: Journal of Mathematical Physics

and authors are represented by
authors:
   person:
      first-name: Tobias
      last-name: Diez
   person:
      ....

before they are send to JabRef online (yaml only used to visualize the idea, not meant as the actual data format). Latex code in some fields (except say abstract and comment, maybe also except title) are converted to unicode before sending it to the server.

Advantages:

Can reuse existing parsing of JabRef
Makes it easier to match metadata with other structured data

Disadvantages:

More complicated conversion with bibtex. In the best case, one can however still have canonical transformations to and from bibtex that do not loose any data
Sync via JabRef online gives not exactly the same bib file, but in the best case a "normalized" version of the original file (e.g. similar to applying the "convert to biblatex" cleanup); in the worst case, we destroy the user data if our parser is not good enough (for example, if First Lastname is parsed as name: { first = 'Lastname', last = 'First' } and then serialized again one would obtain Lastname First, which bibtex would understand wrongly). However, if the parser is well-designed one could at least prevent data loss.

Option C: Store and accept only parsed and matched data. For example, instead of saving the journal name we only keep the issn; and for each author only the orcid. Then the string values can be recovered from some general database of journals and authors

Advantages:

Makes it easier to match and enrich metadata with other structured data
Less storage required

Disadvantages:

Might not be possible to store all information in that way; for example, not every author has an orcid
Mapping to and from identifiers is not unique; and not constant in time. For example, there are different authors with the same name.

Of course, one can also use these options in parallel; e.g. transfer and save data in format A + B, where A would only be used for sync purposes, but B for everything else. This is however a lot of overhead (development, maintenance and server storage) and lead to additional problems when the user edits a document in JabRef online.
Discussion: Option A would be perfect if our goal with JabRef online were to only provide an online interface for JabRef. However, for some of our aims, especially the construction of a global user-maintained database of high-quality citation metadata, Option C is the closest: ideally, one would only say that a document was authored by x, y, z and define the name of x, y and z independently of the document. Option B seems to be a sensible middle-ground which at least allows to abstract from the bibtex-specific implementation.
Decision: Option B

This is now completely implemented for journal articles, other types are still missing and this is tracked at #332.


Add all open files to Copilot Edit

Files can be dragged/dropped into the Copilot Edit dialog. I would like to be able to add "All Open Files" or drag a folder from the solution explorer to add multiple files.

This already exists in the current VS Code stable:

You can click Add Files and pick Open Editors which is the first entry.
If you have multiple tab groups open, the active editor from each group appears in your working set.


Transform with payload

Which issue does this PR close?
Part of #8663.
Rationale for this change
Curretnly there are many special TreeNode trees in DataFusion so as to carry additional information during tree transformations. These special trees are a bit cumbersome as they need to implement TreeNode functions (apply_children(), map_children()).
This PR proposes to add TreeNode.transform_with_payload(), TreeNode.transform_down_with_payload() and, TreeNode.transform_up_with_payload() methods so as to be able to help with these cases.
This PR implements idea 4. from https://github.com/apache/arrow-datafusion/pull/7942.
What changes are included in this PR?
This PR:

Adds TreeNode.transform_with_payload(), TreeNode.transform_down_with_payload() and TreeNode.transform_up_with_payload(),
Refactors SortPushDown and PlanWithRequitements using TreeNode.transform_down_with_payload(),
Refactors ExprOrdering using TreeNode.transform_up_with_payload()

I will refactor other special TreeNode trees in a follow-up PRs if this PR gets accepted.
Are these changes tested?
Using exinsting tests.
Are there any user-facing changes?
No.

Thank you @peter-toth -- this seems like an improvement to me. Perhaps @viirya and @berkaysynnada can take a look too prior to merging this

Thanks @alamb for the review. Just a note that in this discussion: https://github.com/apache/arrow-datafusion/pull/8672#discussion_r1438363204 some concerns came up regarding the new transform_with_payload() methods might not be able to cover all usecases and so can't replace all derived trees. cc @ozankabak
I might need a few days to check that with a more complex derived tree like OrderPreservationContext and extend this PR or open a follow-up PR if refactor is possible.
But, I think even if it turns out that not all derived trees can be refactored, IMO the new methods are still useful as the usecase of SortPushDown, PlanWithRequitements and ExprOrdering proved.

Yes, I have some concerns about this PR (and getting rid of derived trees in general), so let's not merge this for now.
I gave a brief explanation before, but @berkaysynnada and I will give more details on our reasoning after the holiday (next week).

@ozankabak, @berkaysynnada, I've refactored OrderPreservationContext using TreeNode.transform_with_payload() in https://github.com/apache/arrow-datafusion/pull/8664/commits/269d8ba9695085a0e4c65ec713cd49094fc3a0cf commit of this PR.
IMO the new algorighm not just removes OrderPreservationContext, but also makes the algorighm simpler and more effective.
I was able to eliminate the inner top-down transformation of get_updated_plan() that was kicked off at SortExec nodes during the bottom-up transformation of transform_up(). The new algorighm, that uses TreeNode.transform_with_payload(), does only one traversal. Please find the details here: https://github.com/apache/arrow-datafusion/pull/8664/commits/269d8ba9695085a0e4c65ec713cd49094fc3a0cf#diff-7894863f285ed3ad976c94603d639b99955d4a581e5eaee5f5946960fcbc21e1R52-R67
Please let me know if you still have concerns.

@peter-toth thank you for working on this. We were a little busy but we will work on this and reply in a couple days

Two pieces of news from our side:

I think I figured out a possible way to simplify the overall TreeNode-related code and reduce code duplication significantly. I plan to post a PR on Monday.
I think the integrated up/down idea may indeed be useful. I will try to figure out the trade-off between using the existing Visitor/pre_visit/post_visit mechanism and having a new kind of transform function.

In any case, 2 (which is the main concern of this PR) will benefit from 1 so I will go step by step finish off 1 first.

Thanks for the update @ozankabak.
As regards to 1. https://github.com/apache/arrow-datafusion/pull/7942 and our discussion with @berkaysynnada at https://github.com/apache/arrow-datafusion/issues/8663#issuecomment-1871218567 might be relevant. Although that PR didn't try to eliminate code duplication, it might be useful to design better tree visit/transform functions in terms of effectiveness (self mutation of nodes where possible) and API usability (common TreeNodeRecursion enum results to control recursions).
I think 2. is somewhat orthogonal to 1., the new transformWithPayload functions of this PR depend on map_children only. I beleive whatever will be the alternative of map_children after you simplification the code of this PR can be adjusted easily. (Actually, the original version in https://github.com/apache/arrow-datafusion/pull/7942 did use mutable references to nodes but this separate PR alligns with the current consume and produce way of other TreeNode APIs.)
You might have seen that yesterday I pushed another commit to this PR: https://github.com/apache/arrow-datafusion/pull/8664/commits/88a43c10ec65ea04ea56514af546b9cbf20d77d4 to refactor and remove PlanWithCorrespondingCoalescePartitions using transform_with_payload(). The change is very similar to the previous OrderPreservationContext related one. The new algorightm not just removes the derived tree, but also offers a more effective one pass transformation.
If you have some time after your simplification a review of this PR would be greatly appreciated as I would like to continue working on refactoring the remaining derived trees (either in this PR or follow-up ones).

If you have some time after your simplification a review of this PR would be greatly appreciated as I would like to continue working on refactoring the remaining derived trees (either in this PR or follow-up ones).

Certainly, I will do a deep dive on this after I finish the simplification PR. Thank you for the awesome collaboration

FYI, the draft PR is #8817. I will focus on this once we are done with it 🚀

I will update this PR once https://github.com/apache/arrow-datafusion/pull/8817 gets merged.

Marking as draft as we work on https://github.com/apache/arrow-datafusion/pull/8817 -- I am trying to clean up the list of PRs that need review

Marking as draft as we work on https://github.com/apache/arrow-datafusion/pull/8817 -- I am trying to clean up the list of PRs that need review

Thanks @alamb, I will rebase this once that one gets merged.

@alamb, @ozankabak, @berkaysynnada I rebased this PR and updated the PR description after https://github.com/apache/arrow-datafusion/pull/8817 got merged. Please share your thoughts.

@peter-toth what do you think about first focusing on #8891 and then on this PR? I believe it holds higher importance and could contribute more to the simplification process. It would be easier if we concentrate these 2 PR's one by one, rather than proceeding with both at the same time.

The 2 PRs are not connected but I'm fine with any order. This is a small PR so I think we can probably conclude on something easily. And actually there will be a few more API fixing PRs in https://github.com/apache/arrow-datafusion/issues/8913.

I wonder what the current state / plan for this PR is? (I am going through the PR review backlog)

I wonder what the current state / plan for this PR is? (I am going through the PR review backlog)

Thanks @alamb fot the question! I plan to rebase this PR in a few days, maybe a week. Let me move this to draft till then.


Fuse.Share: Fixed iPad crash bug

iOS design guidelines requires a point of reference for use as the popover spawn origin. Added an optional argument to the share api for passing a UX element for use as the spawn origin. If the user does not provide this, emit a UserError and the popover will spawn in a default location
Not to happy about this fix. Makes the share API clunky. I think the Share API should be UX based instead of JS
This PR contains:

[x] Changelog
[x] Documentation
[ ] Tests

We should have a broader discussion about which APIs should be UX or JS at some point, especially now that expressions are coming to the forefront


Compatibility with route caching

Hi there,
I use extensively your excellent plugin. Now I would like to to do route caching https://laravel.com/docs/5.1/controllers#route-caching but after doing so, it seems that the route cache completely ignores the Entrust rules set-up in the routes file.
Is there a way to make Entrust compatible with route caching?
Thanks.

No answer? :-(

https://github.com/Zizaco/entrust/blob/master/src/Entrust/Entrust.php#L92 That functionality is uses Route::filter() and Route::when() which rely on router events not triggered with caching enabled.
Keep in mind those two functions were deprecated in Laravel 5.2 https://laravel.com/docs/5.2/upgrade#upgrade-5.2.0 so you should think about instead implementing your ACL using middleware where $request->route() has the metadata required to assert whether a user has access.

Many thanks for your answer. I am not sure to understand: if I update my website to 5.2 then what will be the syntax I should use in order to have Entrust compatible with Laravel route caching.

I have no experience using this package, but give this a go: http://lmgtfy.com/?q=laravel+5.2+entrust+middleware.

Hi @derekmd you did not answer my previous question. If I update my website to 5.2 then what will be the syntax I should use in order to have Entrust compatible with Laravel route caching?
Many thanks.

🤦♂


0.12.0 errors with sshfs mounts inside a backup path

Output of restic version
restic 0.12.0 compiled with go1.15.8 on linux/amd64
How did you run restic exactly?
via systemd service: /usr/bin/restic backup --verbose --one-file-system --tag systemd.timer $BACKUP_EXCLUDES $BACKUP_PATHS

BACKUP_EXCLUDES="--exclude-if-present .nobackup"
BACKUP_PATHS="/home /etc/ansible /data/mediaserver /data/shared /data/web /data/weewx"

What backend/server/service did you use to store the repository?
local ext4 filesystem and backblaze b2
Expected behavior
Skip sshfs filesystem mounted at /home/bcotton/ff-web/dav
(don't let the directory name distract you, I no longer dav mount it, I'm just too lazy to mv the mountpoint :smile: )
Actual behavior
backup gives error. It appears to successfully create the backup, but the return code makes systemd think it failed.
repository 2a5d1306 opened successfully, password is correct
found 1 old cache directories in /root/.cache/restic, run `restic cache --cleanup` to remove them
lock repository
load index files
using parent snapshot 4ee93653
start scan on [/home /etc/ansible /data/mediaserver /data/shared /data/web /data/weewx]
start backup on [/home /etc/ansible /data/mediaserver /data/shared /data/web /data/weewx]
scan: lstat /home/bcotton/ff-web/dav: permission denied
scan finished in 28.952s: 338151 files, 527.566 GiB
error: lstat /home/bcotton/ff-web/dav: permission denied

Steps to reproduce the behavior
Upgrade from restic 0.9.6 compiled with go1.14 on linux/amd64 (most recent version in Fedora 33 repos) which behaved as expected.
Do you have any idea what may have caused this?
It may be the same issue as #2659, but it seemed different enough that I thought I should file a new issue.
Do you have an idea how to solve the issue?
No, but explicitly excluding the sshfs mountpoint yields the expected behavior. I don't have other sshfs mounts generally, so it's not a huge concern for me, especially with the workaround.
Did restic help you today? Did it make you happy in any way?
I love how easy it was for me to configure restic backups to a local disk and a remote repository. Thankfully, I've only needed the backups once, but I'm glad I have it. Thanks!

Starting with restic v0.10.0 (PR #2546), error handling is now improved and outputs a different exit code when a backup does not complete successful (e.g. lack of permissions for files).

The proper solution is to also explicitly exclude the sshfs mount from the backup. Then restic won't complain.


Print timestamps with timezone

Codecov Report

Merging #115 into master will increase coverage by 0.04%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #115      +/-   ##
==========================================
+ Coverage   96.92%   96.96%   +0.04%
==========================================
  Files           2        2
  Lines         293      297       +4
==========================================
+ Hits          284      288       +4
  Misses          9        9

Impacted Files
Coverage Δ

loggo/loggo.py
96.94% <100%> (+0.04%)
:arrow_up:

Continue to review full report at Codecov.

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


Question: Is it possible to add in this repository new ruleset?

Hi there. I have a question about this repository. I'm working on some plugins for WordPress and really love WordPress and their standards but sometimes I feel lost while writing code.
I think this idea is not common issue for WordPress and very new for community and I really want that you won't hate it.
After a lot of thinking I realized that only one thing stopping me from being happy: snack_case instead of CamelCase.
Why I think that CamelCase is more pretty:

More clear folders and files structure. For example:
Admin
Options
- TokenOption.php
- LastUpdateDateOption.php
API
- API.php
- Actions
-- SomeAction.php
-- AnotherAction.php

For bad file-folder organization checkout WooComerce or Seo by Yoast — they have hundreds of PHP files and for the first glance it's hard to know where something happens or located (thank you IDE for click by function name to open the function).

Composer autoloader (PSR-4). And no more tons of require in millions of files which makes code more complicated and hard to understand.

We can name files more friendly. For example, comments.php — what is it? Class or just plain functions inside? Maybe this class extended from some other class or implements interface?
But if we add one more word then it makes more sense. CommentsModule.php — it's a module in Jetpack!

This CS is used in Symfony. We can learn and get a lot of fresh ideas from Symfony.

WordPress itself typed in CamelCase :)

I understand that I can create my own rules in separated repository but I want to discuss this with WordPress community :) What you think?

While I appreciate that you want to start this discussion, this is not the right place IMHO.
The people here don't make up the rules. This repository and the sniffs contained therein follow the coding standards as set out by WP Core, WP VIP and common WP and PHP best practices.
Regarding the naming conventions, the WP core handbook is quite clear about these:
https://make.wordpress.org/core/handbook/best-practices/coding-standards/php/#naming-conventions
I'd suggest you ask in the WP Slack what would be a better place for this discussion.


[FLINK-12720][python] Add the Python Table API Sphinx docs

What is the purpose of the change
As the Python Table API is added, we should add the Python Table API Sphinx docs. This includes the following work:
Add scripts to build the Sphinx docs
Note: This PR is based on #8732 (Thanks a lot for @HuangXingBo 's great work!)
Brief change log

Support Sphinx to create Flink Python Docs
Correct doc code style of Python code
Improve some documentation of the Python Table API

Verifying this change
This change is a documentation work without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

@sunjincheng121 Thanks a lot for the review. Have updated the PR accordingly. Regarding to the improvement of the Python docs by adding more examples, that makes much sense to me and I have created a JIRA https://issues.apache.org/jira/browse/FLINK-12897 to tract that.

Thanks for the quick updated @dianfu
+1 to merged.

@flinkbot approve all


koordetector: make koordetector run and compatible with different kernels

Ⅰ. Describe what this PR does
This PR completes codes for koordetector to run with Dockerfile. The functionality of CPU schedule latency eBPF program is now available by this commit.
An eBPF CO-RE way is used to develop CSL collector. For developers' intention, you can follow belowing process to develop a eBPF program under koordetector's architecture:

First, code your eBPF kernel program with a .c file. (e.g. pkg/koordetector/util/ebpf/cpu_schedule_latency/csl.bpf.c)
Second, encapsulate this eBPF program with "github.com/cilium/ebpf" package and provide a go util(e.g. pkg/koordetector/util/cpu_schedule_latency/cpu_schedule_latency.go).
Third, use go generate to compile and generate .o file for your eBPF program. Files in pkg/koordetector/util/ebpf/headers can be used for that.
When koordetector runs, it finds vmlinux (by default in /sys/kernel/btf/vmlinux) file to re-location kernel information such as task_struct structure. If this fails (e.g. kernel < 5.2 does not has vmlinux in /sys/kernel/btf/vmlinux), the CSL collector will use vmlinux files in pkg/koordetector/util/ebpf/core.

For now, I added supporting vmlinux file of kernel vmlinux-4.19.91-27.4.al7.x86_64 in this PR. Vmlinux files for other kernels can be find in BTFhub, Anolis coolbpf or generate by pahole.

Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist

[ ] I have written necessary docs and comments
[ ] I have added necessary unit tests and integration tests
[ ] All checks passed in make test

PTAL @zxustc @xueche


0.3.0 Release

new in 0.3.0

new bind method replaces old keys, can now use event and hotkeys quite easily with this method.
simplified on.
multi-client remote procedure ComponentModifier sessions. (rpc!, open_rpc!, join_rpc!, disconnect_rpc!, close_rpc!, is_host, is_client, is_dead)
new script! and script interface for creating client functions and observable functions in a consistent way.
Additional abstraction to Modifiers.
Client Modifiers
Modifier Abstract type moved to toolips
next! method to set next animations and changes.
observe! has become script in accordance with new syntax.
insert_child! allows the inserting of children.
append_first! allows us to append a child to the top of the children.
push! ComponentModifier bindings to put scripts into documents.
update! allows any Julia type to be written to the "text/html" MIME. Eventually, this function will include an auto-mime algorithm similar to the one seen in Olive.jl here (towards the bottom of the file).

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/76646
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.0 -m "<description of version>" bad9d933a6882f783f2cc69dc491a9ebc523ae6d
git push origin v0.3.0

@JuliaRegistrator register

Registration pull request updated: JuliaRegistries/General/76646
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.0 -m "<description of version>" 7d8fdf4630ead740582fbcbf194b8c004a93d97a
git push origin v0.3.0


Drop all references to ppc64le from build system

What this PR does / why we need it:
For a long time now, COPR hasn't been able to produce ppc64le packages due to hardware issues. Since we rely on COPR for QEMU and libvirt builds, that has affected our ability to roll out virtualization updates consistently across architectures.
Initially we just allowed ppc64le to use older packages, but eventually we were forced to admit defeat and stop building the virt-launcher container on the architecture.
Despite this, the build system is still littered with references to ppc64le packages and this, in addition to bloating the repository, also results in unnecessary churn every time a developer runs 'make rpm-deps' to pick up the latest updates.
This commit drops all of those references. Note that only the build system is modified: all ppc64le-specific logic in KubeVirt
is retained, so once packages are once again available it should be fairly easy to reinstate support.
Release note:
NONE

/retest
/lgtm
/approve
@murilofv FYI happy if at some point we can revive this.

I can't reproduce the test failure locally, and the error message is not very helpful - to me at least ;)
@rmohr do you think it's some temporary problem on the CI side?


drivers: pwm: Restore default on re-initialization

Jira:NCSDK-11329
Signed-off-by: Pawel Dunaj<EMAIL_ADDRESS>

The PWM is not able to properly driver pins after wakeup as it looses some of the configuration during deinit.
The patch restores default configuration.

Rebase, please.

ah... is this nonsensical political correctness. I rebased on master but apparently somebody got changed the well established name for no good reason. Will rebase.

Please remove references to Jira:NCSDK-11329
Add links to GH issues instead.

removed link; GH issue is not created in this case

Zephyr in its entirety. 2 months of being ready for review...

@pdunaj  can you please rebase and push again to get a fresh CI verdict, it has been a while since this was last checked.

@pdunaj can you please rebase and push again to get a fresh CI verdict, it has been a while since this was last checked.

Sorry! I had this pr open in a tab and your comment did not show before I merged


Removed dependency on persistence-api

I removed dependency on javax.persistence.persistence-api in this commit. FREME packages can no longer start with this jar file on the class path.
@ArneBinder you added this dependency. Please check if you need it.

@jnehring I'm really sorry for this, it was an error of my IDE. It could not resolve this dependeny. I deleted my whole local repository, now it works.

no problem ;)


make: *** [migrate] Error 1

I did a pull this morning and got the following error.  Now InvenTree will not start.
django.template.library.InvalidTemplateLibrary: Invalid template library specified. ImportError raised when trying to load 'django.contrib.admin.templatetags.admin_static': cannot import name 'RemovedInDjango30Warning'
Makefile:14: recipe for target 'migrate' failed
make: *** [migrate] Error 1

Hi @lookme2 did you run make update or make migrate? Are you running in a virtual environment and all the required PIP packages are up to date?
I have not seen this error on my setup, it feels like it may be caused by a package incompatibility...

Also can you provide the full error output?

Also can you provide the full error output?

@SchrodingersGat I am running it in a VM with Ubuntu 18.04.  I did to a make update and a make migrate both.  I messed around with it yesterday afternoon and managed to get it running.  To be honest I'm not sure how I fixed it.
If there is some log file you would like to see let me know.  I'll be more than happy to supply that for you.

That is weird. Perhaps there was a step you missed the first time around? Thanks for letting my know you got it fixed.


Remove unneeded using statements in coefficient.hpp

Resolves #3390. Verified that there are no warnings with nvcc.

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.


Configure I18n in cofig.rb

Hiya
I want to use the load.path of I18n to pull in locales files from re-usable submodules.
I have seen something like the below - but does not seem to work correctly.
# I18n
# @see http://www.rubydoc.info/github/svenfuchs/i18n/I18n
Time.zone                      = "Europe/London"
I18n.load_path                 = Dir[Middleman::Application.root_path.join('locales', '**', '*.{yml}')]
activate :i18n, langs: [ :en ], mount_at_root: :en

Any help appreciated.

What is not working exactly?

Hiya,
Under domain.com/__middleman
The load.path configuration is not showing up at all, and not pulling in my other locale .yml files.
Thanks

i18n will automatically setup the load paths, don't override it.
langs is hard coding the list to only en, you should remove that to be able to use multiple langs

@tdreyno Hiya - yeah I have i18n all setup - its just I want module specific language files so if I reuse a module I do not have to make sure that the language elements are copied over to the project specific language files
I think I saw this as a wishlist from another dev also in the v4 locales - will search that out
nb/ at the moment I only have english in this project.
hope that makes sense.

Sorry, can you try to explain " I want module specific language files so if I reuse a module I do not have to make sure that the language elements are copied over to the project specific language files". Not following.


dendrite: 0.8.8 -> 0.8.9

Description of changes
Changelog: https://github.com/matrix-org/dendrite/releases/tag/v0.8.9
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Important bugfix for E2EE


Remove next-compose-plugins?

The next-compose-plugins rewrites the next.config.js-config with invalid data, and the latest version of next.js warns about every configuration error.
A possible solution: https://github.com/cyrilwanner/next-compose-plugins/issues/59#issuecomment-1192523231

Fixed in https://github.com/Frojd/Wagtail-Pipit/commit/9ce5d0dbbe601f28fd10d464c89ee6666d2d89a6


Debug Console Flickering

After the September 2020 update, the debug console is flickering.

I encounter this very annoying issue, even with version 1.50.1.
Whenever there is something output to the debug console, it auto scrolls to somewhere exceeds the bottom. The position is not constant. So it is flickering with random blank area.
I'm debugging Golang codes. Not tested against other languages yet.

This happens with Java as well

Duplicate of https://github.com/microsoft/vscode/issues/107704
If you have exact reproducable steps without Dart, just pure JS or Python would be great so I repro on my machine. Thank you


⚠ Bofrost.lu has degraded performance

In df73cef, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 983 ms

Resolved: Bofrost.lu performance has improved in 497b69a after 6 minutes.


Initial implementation of comms watchdog

Added watchdog timeout property to Axis::Config_t:
axis.config.watchdog_timeout

Added axis protocol function to feed watchdog timer:
axis.watchdog_feed()

Axis::run_control_loop now checks for watchdog expiration.

Ascii protocol: add support for watchdog

The following ASCII commands now automatically update the watchdog:
p, v, t, c, q

Added a 'u' command to update the watchdog of a motor without
modifying setpoints.

Updated ascii protocol documentation to reflect new commands and
effects.

Updated getting started guide to mention watchdog settings and
functions in protocol.

Please note: due to unavailability of hardware at this time, I have been
unable to test this code on an Odrive.

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

Thanks for making this, after adding a fix it works great!


Routine Airline-Flights-118x to 120x have incorrect wait instructions at destination location

Flights indicate they are waiting for negotiations to complete. But they should indicate waiting for passenger exchange to complete.
Cosmetic issue only, No impact to mission completions. Change will be merged into main and published with next release

fixed by v1.0.3

fixed by v1.0.3


Request to Add Video & Audio Switching Action

Description: Currently, there are separate switching actions for Video and Audio. We would like to request the addition of an action that switches both Video and Audio simultaneously.
Command:
@SSW,0,0,1,{inputChannel},{outputChannel}

Done in https://github.com/bitfocus/companion-module-idk-ninjar/commit/3e4b869caae689fa8bda440e1461b467efab97b5


re-ordering my options

Selectize is reordering my provided options, which is undesirable behaviour.
I am providing:
<select name="fields[places]" placeholder="How many places do you require?" id="places" class=" places">
    <option value=""></option>
    <option value="all">All</option>
    <option value="1">1</option>
    <option value="2">2</option>
</select>

The output is ordering by number then alpha, so 1, 2, all.

What's your configuration look like?

Does this not work in your browser?
http://jsfiddle.net/97gvoywx/


Release opentelemetry-collector Helm chart for latest app version (0.42.0)

As of writing, the latest opentelemetry-collector (0.8.1) chart supports appVersion 0.37.1. Attempts to use this Helm chart version with an the image for the app version 0.42.0 produces this error in the pod:
Error: failed to start container "opentelemetry-collector": Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "/otelcontribcol": stat /otelcontribcol: no such file or directory: unknown

Looking into this further, the issue with pod startup seems to be that there is a discrepancy between the Dockerfile in code (https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/v0.42.0/cmd/otelcontribcol/Dockerfile#L14) and the Dockerfile tied to the image in Dockerhub (https://hub.docker.com/layers/otel/opentelemetry-collector-contrib/0.42.0/images/sha256-ec8c214a835edfec73d43340d9099f064973f5273fd5e45b328eaa2beca39115?context=explore) - note the slight difference in entrypoints.

Yes,I got the same prolbem。Using helm,
Warning  Failed     12s (x2 over 14s)  kubelet            Error: failed to start container "opentelemetry-collector": Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "/otelcontribcol": stat /otelcontribcol: no such file or directory: unknown
the image version 0.42.0(otel/opentelemetry-collector-contrib:0.42.0)

It’s because the entrypoint in the container has been changed from /otelcontribcol to /otelcol-contrib. Additionally, --metrics-addr is no longer a valid argument.
We can override the entrypoint by changing command.name in values.yaml but the metrics-addr arg is hardcoded.


Updated html_path

[X] ❗ I have followed the Contributing to DVCLive guide.

[X] 📖 If this PR requires documentation updates, I have created a separate PR (or issue, at least) in dvc.org and linked it here.

dvc.org PR: https://github.com/iterative/dvc.org/pull/2783
Close #148

Codecov Report

Merging #153 (e612dd0) into master (fe95917) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #153   +/-   ##
=======================================
  Coverage   91.66%   91.66%
=======================================
  Files          15       15
  Lines         360      360
=======================================
  Hits          330      330
  Misses         30       30

Impacted Files
Coverage Δ

dvclive/metrics.py
97.14% <100.00%> (ø)

Continue to review full report at Codecov.

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


Inject metadata into the llvm-cov JSON output

As discussed in #285, this injects some metadata into the JSON output of llvm-cov. This can be helpful for tools that rely on the output of it and cargo-llvm-cov as well.
It adds in the following fields under a new cargo_llvm_cov field in the root JSON structure:

version is the cargo-llvm-cov version that was invoked. Helpful for tools to verify that cargo-llvm-cov is of a certain version and has some expected behavior.
manifest_path is the location of the Cargo.toml as resolved by cargo-llvm-cov. This is two-fold:

It can reduce repetition, as otherwise a custom manifest path would need to specified for both cargo-llvm-cov and the other tool.
There might be minor differences in how the mainfest path was resolved, so this ensures the other tool gets exactly the same manifest path as cargo-llvm-cov.

Fixes #285

LGTM. Could you resolve the merge conflict?

Done. Just ping me in case any conflict comes up again :bowing_man:

Thanks! Published in 0.5.23.


运行ios报错library not found for -lcrypto

环境:mac
xcode:11.1
react-native:0.61.2
react-native-baidu-map:1.0.10

怎么解决的


Update ARCore to 1.12.0 to prevent Filament Panic on API 29

When building toolkit and running on devices running Android Q (API 29), a native panic exception is thrown:
2019-10-29 15:50:12.090 8238-8238/com.esri.arcgisruntime.sample.exploresceneinflyoverar E/Filament: Panic
    in void *filament::CircularBuffer::alloc(size_t):124
    reason: couldn't allocate 6144 KiB of memory for the command buffer

https://github.com/google/filament/issues/1345
Updating ARCore to 1.12.0 fixes this.
Regression testing will be required.

Hello, how did you upgrade to 1.12.0? I threw a new error after trying to upgrade:
Caused by: java.lang.NoSuchMethodError: No static method getInstance()Lcom/google/ar/sceneform/animation/AnimationEngine; in class Lcom/google/ar/sceneform/animation/AnimationEngine; or its super classes (declaration of 'com.google.ar.sceneform.animation.AnimationEngine' appears in /data/app/com.esri.arcgisruntime.sample.navigateinar-M99l1YRcJCdGOuCpQ4Q8qw==/base.apk)

This is how I replace arcore's dependency. I don't know whether it is right or not

Looking forward to your reply, thank you very much!


breaking change in starlette

new starlette release has a change that breaks fastapi:
https://github.com/tiangolo/fastapi/issues/2342
we need to pin the starlette version to <0.14.1

fixed upstream and in PR #278

fixed upstream and in PR #278


Add EMA for confirmed

Fine tuned version of #8.
@ladamski, @stasm - this is what I came up with based on Lucas' PR.
Do you think it addresses #8 and #11?
Or is that not a good representation of what you wanted to show?

I made the calculation use the previous ema. Does it look better?

I made the calculation use the previous ema. Does it look better?

Yup that looks great!


HIVE-23763: Query based minor compaction produces wrong files when ro…

…ws with different buckets Ids are processed by the same FileSinkOperator
NOTICE
Please create an issue in ASF JIRA before opening a pull request,
and you need to set the title of the pull request which starts with
the corresponding JIRA issue number. (e.g. HIVE-XXXXX: Fix a typo in YYY)
For more details, please see https://cwiki.apache.org/confluence/display/Hive/HowToContribute

Maybe a bit of logging might help in the future so we can find issues if needed.
Otherwise LGTM


fix: let simp arguments elaborate without disabling error recovery

Modifies simp to elaborate all simp arguments, and then failing if any had any elaboration issues, rather than failing on the first simp argument.
This enables better term info and features like tab completion when there are elaboration errors.
Also included is a fix to the all_goals and <;> tactic combinators. Recall that try/catch for the Tactic monad restores the state on failure. This meant that all messages were being cleared on tactic failure. The fix is to use Tactic.tryCatch instead, which doesn't restore state.
Part of addressing #3831
Closes #4888

Recall that try/catch for the Tactic monad restores the state on failure. This meant that all messages were being cleared on tactic failure. The fix is to use Tactic.tryCatch instead, which doesn't restore state.

That's quite a foot gun, it seems. Should we remove the try-catch instance for TacticM and force every user to think about which one they want where? Or is that too tedious? Or is the other one the better default?

@nomeata I've shot both of my feet with this one, and it's why I added this Tactic.tryCatch escape hatch recently. I really want try/catch to be non-backtracking, but it's going to be a lot of work to evaluate every tactic...


recipes are likely to be missing when multiple mods try to modify return value of ReloadableServerResources.listeners

e.g. Fluidized-Tanks mod when installed along with apotheosis (and placebo) will results in the missing of hellshelf recipes and others (due to setReturnValue cancels others?)
https://github.com/Rongmario/Fluidized-Tanks/blob/master/src/main/java/zone/rong/fluidizedtanks/mixin/ReloadableServerResourcesMixin.java#L19-L23
For a proof and temp fix for a modpack if I add the RecipeManager to listeners for placebo in fluidized-tanks mixin class the recipes will be back.
I understand this is not a bug strictly, just want to let you know this will happens. Is there any possibility to use other api to register recipes instead of using mixin to improve robustness.