cmd/go/internal/test: go test -list doesn't always display all examples

Go 1.9 adds a new feature described at https://beta.golang.org/doc/go1.9#go-test-list:

The go test command accepts a new -list flag, which takes a regular expression as an argument and prints to stdout the name of any tests, benchmarks, or examples that match it, without running them.

go test -help says:
-list regexp
    List tests, benchmarks, or examples matching the regular expression.
    No tests, benchmarks or examples will be run. This will only
    list top-level tests. No subtest or subbenchmarks will be shown.

It's issue #17209, implemented in CL 41195 (ba8ff87dbeb87813a4604e36adb609b1e8fcb7be). /cc @nemith @mpvl
What version of Go are you using (go version)?
go version go1.9rc1 darwin/amd64
What operating system and processor architecture are you using (go env)?

$ go env
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/Dmitri/Dropbox/Work/2013/GoLanding:/Users/Dmitri/Dropbox/Work/2013/GoLand"
GORACE=""
GOROOT="/usr/local/go"
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/tw/kgz4v2kn4n7d7ryg5k_z3dk40000gn/T/go-build927351599=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"

What did you do?
I ran go test -v and go test -list=Example on a sample package with 3 examples, two of which are runnable (i.e., they have a "Output:" comment at the end), and one is not runnable (no "Output:" comment):
package main_test

import "fmt"

func ExampleLoud() {
	// Dog says:
	fmt.Println("BARK!")

	// Output: BARK!
}

func ExampleQuiet() {
	// Gopher says:
	fmt.Println("")

	// Output:
}

func ExampleNoOutput() {
	// This example has no "Output:" comment at the end,
	// so it doesn't get run, it's just shown in docs and
	// ensured to build without errors.

	_ = fmt.Sprintln("*tree falling sound*")
}

Note, the above is just a minimal reproduce sample. I ran into this issue in a real Go package github.com/shurcooL/issuesapp/httpclient:

httpclient $ go test -v
=== RUN   ExampleNewIssues
--- PASS: ExampleNewIssues (0.00s)
=== RUN   ExampleNewIssues_authenticated
--- PASS: ExampleNewIssues_authenticated (0.00s)
=== RUN   ExampleIssues_List
--- PASS: ExampleIssues_List (0.00s)
=== RUN   ExampleIssues_Count
--- PASS: ExampleIssues_Count (0.00s)
=== RUN   ExampleIssues_ListComments
--- PASS: ExampleIssues_ListComments (0.00s)
PASS
ok  	github.com/shurcooL/issuesapp/httpclient	0.011s
httpclient $ go test -list=Example
ExampleIssues_List
ExampleIssues_Count
ExampleIssues_ListComments
ok  	github.com/shurcooL/issuesapp/httpclient	0.012s
httpclient $

What did you expect to see?
$ go test -v
=== RUN   ExampleLoud
--- PASS: ExampleLoud (0.00s)
=== RUN   ExampleQuiet
--- PASS: ExampleQuiet (0.00s)
PASS
ok  	sample/package	0.006s
$ go test -list=Example
ExampleLoud
ExampleQuiet
ok  	sample/package	0.005s
$

What did you see instead?
$ go test -v
=== RUN   ExampleLoud
--- PASS: ExampleLoud (0.00s)
=== RUN   ExampleQuiet
--- PASS: ExampleQuiet (0.00s)
PASS
ok  	sample/package	0.006s
$ go test -list=Example
ExampleLoud
ok  	sample/package	0.005s
$

ExampleQuiet is not listed in go test -list=Example output, even though it's a valid runnable example [1] that runs as part of go test -v.
[1] https://golang.org/cmd/go/#hdr-Description_of_testing_functions
Cause
The cause is simple and can be seen in the code implementing the feature at https://github.com/golang/go/commit/ba8ff87dbeb87813a4604e36adb609b1e8fcb7be#diff-70e628298261565d825f7199d13042f2R972. testing.listTests function has this loop for printing examples:
for _, example := range examples {
	if ok, _ := matchString(*matchList, example.Name); ok && example.Output != "" {
		fmt.Println(example.Name)
	}
}

Notably, it checks that example.Output != "". I'm assuming it does that to try to find runnable examples. However, some runnable examples (i.e., ones with last comment that starts with "Output:" or "Unordered output:") have empty expected output.
They're still runnable, and should be included in output of go test -list, just like they are in output of go test -v.

Added Go1.9 milestone since this is a bug in a new Go 1.9 feature, feel free to update if needed.

Yes the output check isn't needed.  The check is already done when the testmain.go is generated.
https://github.com/golang/go/blob/master/src/cmd/go/internal/test/test.go#L1491

Yes the output check isn't needed.  The check is already done when the testmain.go is generated.
https://github.com/golang/go/blob/623e2c4603053c8e2ecf4cd7ed5f8242a7a02226/src/cmd/go/internal/test/test.go#L1491

That's very helpful, thanks for pointing that out!


Feature/ohlulu

Add Date Extensions
File rename: Config.swift to MinionsConfig.swift

起床囉～～～～～

🥺


Improve typegen for empty types

After merge of #2122, typegen removes empty types from function input arguments, which corresponds to the runtime behavior of the abi-coder, which ignores empty inputs. This led to unexpected function signatures. Based on the abi below,
abi MyContract {
   fn types_value_then_empty(x: u8, y: ()) -> ();
   fn types_value_then_empty_then_value(x: u8, y: (), z: u8) -> ();
}

these are the generated functions (in usage):
contract.functions.empty_then_value(35).call();
contract.functions.value_then_empty_then_value(35, 35).call();
``

This is odd and unexpected and should be like this:
```ts
contract.functions.empty_then_value(null, 35).call();
contract.functions.value_then_empty_then_value(35, null, 35).call();

To implement this, we need to change both the abi-coder to accept null (or undefined, which I prefer) for empty types as well as the typegen to match this new runtime behavior.

Blocked by the ongoing work around v1 encoding.

This is linked to #2532


Fix support for legacy theme check configuration identifiers

WHY are these changes introduced?
Fixes https://github.com/Shopify/theme-tools/issues/208
The docs for our CLI was stating that for theme check the --config :theme_app_extension would auto load the TAE config, but this was not working. After some digging, I realized we did not support this command, and hence added a backwards compatibility to ensure if :theme_app_extension was run, theme-check:theme-app-extension, was called.
WHAT is this pull request doing?
This pull request is updating our docs for the config value, and is adding backwards compatibility.
How to test your changes?

Simply run pnpm run shopify theme check --dev-preview --config :theme_app_extension and make sure it run's succesfully.
TopHat Screenshot

Measuring impact
How do we know this change was effective? Please choose one:

[x] n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix

Checklist

[ ] I've considered possible cross-platform impacts (Mac, Linux, Windows)
[x] I've considered possible documentation changes
[ ] I've made sure that any changes to dev or deploy have been reflected in the internal flowchart.

top hatted this change in the main branch. everything is working as intended.


Releasing 0.4.1 to hex?

Hello @timbuchwaldt would it be possible to release 0.4.1 to hex? It looks like the latest is 0.4.0 and there are some fixes to the Callback setup in 0.4.1 that would be useful for us.
Thanks for your efforts!

Hi Dylan,
it should have been automatically released, but hex.pm required the confirmation of the new Code of Conduct. I now pushed the update, sorry for the inconvenience.

Greatly appreciated. Thanks!


Incorrect varint length calculation for negative ints

When calculating the size of a varint for signed integers, the number is casted to unsigned. When the number is negative, this causes std::T::MAX + 1 to be added to it. However, a negative varint should have the same length as its absolute value.
The problem can be reproduced like this:
message Foo {
        required sint32 bar = 1;
}

And then,
let mut x = test::Foo::new();
x.set_bar(-1);
println!("BYTES: {:?}",x.write_to_bytes().unwrap());  // Outputs [8, 1] (Size: 2)
println!("COMPUTED SIZE: {:?}", x.compute_size()); // Outputs 11!

The solution is to use the number's absolute value when calculating the varint size, instead of casting it to an unsigned.

Submitted #169 as a possible solution.

I just realized that this only applies to sint* values, not int*. What is really happening is the sint data is being serialized correctly, but the size of the message is calculated as if it was an int (which is less efficient when encoding negative numbers).
That also means my patch is not good, because it breaks ints (as the travis result shows :) I'm looking into a fix for that.

Fixed. Thank you for the bugreport!


CTD on load

Having issues getting this running, dependencies are all up to date. My crash logs are (ctd_helper.log) and Cyberpunk2077.dmp
Any help would be appreciated

Latest update fixes issue, no clue what the issue was though


Add context.Context as an argument to dataloader.BatchFunc?

Currently I pass in a context.Context via closure. I'm curious if anyone has a better way of passing the context to the batch function.
func Attach(ctx context.Context) dataloader.BatchFunc {
  return func(keys []string) []*dataloader.Result {
    // the batch function, now with 100% more context
  }
}

Are there any downsides to changing the signature of BatchFunc to include the context as an argument?
- type BatchFunc func([]string) []*Result
+ type BatchFunc func(context.Context, []string) []*Result

I don't use context in all of my loaders, and where I do, I create a makeBatchFunc(ctx context.Context) dataloader.BatchFunc that makes the context available via a closure.
That said, I'm open to hearing a solid argument on making the change. I'm also hesitant to introduce breaking changes.

That's interesting... I found I am always enclosing a context in my batch functions to provide request deadlines/timeouts, request tracing, etc.
If others have use-cases where a context is not needed, then I agree that it's not worth it to break the interface. I don't have any arguments for making the change other than convenience.

@tonyghita if we were to make this change, how would the batchFunc get access to the context so that it can be called? Would you suggest also adding the context to the load(key string) and loadMany(keys []string) methods as well?

Yes, it would have to break all sorts of interfaces ☹

This has been resolved by v2, thanks @nicksrandall!


bug(material/chip): Mdc Chip Grid empties all options when using Reactive Forms and focusing out

Is this a regression?

[X] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
14.2.6
Description
Having Reactive forms attached to mat-chip-grid which accepts an array of object values, clears them on focus out.
Reproduction
Steps to reproduce:

Create a formgroup with some formControl
Bind it to <mat-chip-grid>
Add some new options (or the same works if the list is already populated) that are arrays of objects.
Focus out of the component

https://stackblitz.com/edit/angular-6g9jz1?file=src%2Fapp%2Fchips-input-example.ts,src%2Fapp%2Fchips-input-example.html
Upon further investigation, figured that the core problem is that on focus out, object values are transformed to strings hence why we don't see the name property. Nevertheless objects were not transformed in v 14.

Note: In the Docs Chip list works as expected because it is not bound to Reactive forms
Expected Behavior
All options remain with previously defined object values
Actual Behavior
All options are transformed to strings thus we have empty text options
Environment

Angular: 15.0.4
CDK/Material: 15.0.3
Browser(s): Chrome 108.0.5359.124
Operating System: macOS Ventura 13.1

Hello,
I'm unable to use the new chips because of this issue.
I can see that the related fix is stuck since the 10 january, is it planned to be fixed soon ?
Are there some workaround ? (Except using the legacy chips)

To clarify - the focus-out event doesn't clear the value, it converts it to an array of strings.
So if we use items as objects like this: [{ id: 1, name: 'orange'}, { id: 2, name: 'apple'}]
then after the focus-out event, the component value becomes ['orange', 'apple].
A very hacky workaround would be to listen to blur event on the  element
<input ... (blur)="onBlur()">
And restore the array of objects by searching the list by the names we got in the component's value...

onBlur(event: FocusEvent) {

     setTimeout(() => this.restoreArrayOfObjects, 0);

}

private restoreArrayOfObjects() {

     // find the objects by their names from formControl.value/ngModel/whatever

     // and update the value to an array of objects by this.formControl.setValue()

}

Agree, this solution is hacky. In fact I made a PR that fixes the issue. There are a couple of solutions how we can do it.
Either by adding a new ’@Input’ that specifies the exact property that needs to be accessed. Or there has to be made a refactor in the edit mode logic. Either way I need input from the code owner since it was 5 months and still no answer.

I'll tell you something, the issue seems much bigger than that, as I have a case where your fix won't help.
In some part of the application I'm using chips that display their name + description
<mat-chip-row
    *ngFor="let item of selectedItems"
    (removed)="remove(item)">
    {{ item.name }}
    {{ item.description }}
    <mat-icon matChipRemove>cancel</mat-icon>
</mat-chip-row>

As I have described previously, the focus out (blur) event causes the selected items array to become an array of strings.
However, the bigger issue is that if I'm displaying name + description, then these two values get combined in the array, so the array (ngModel or control's value) becomes:
['Google Chrome: Fast & Securecom.android.chrome']
Looks like the focus out event takes the innerText of the chip element and uses it as the item's value, which seems like a huge misconception.

@poveu but how does your chips get created? You have only one input to add. So how are you able to define both name and description?

As I said before, in my case, my form control (or ngModel) value (currently selected items) is not an array of strings (with just item names) but it's an array of whole objects - so I can display whatever data I want, not just the name.
Look at my modified example:
https://stackblitz.com/edit/ovb2sn?file=src%2Fapp%2Fchips-autocomplete-example.ts
The thing is, even for this example to work, I had to switch from event.option.viewValue (which was used by Angular team in their basic example and which is just a string) to event.option.value (which is the real value = full object).

Ok, so I ran into the same issue as OP and luckily it looks like I was able to figure it out.
There's a mistake in the template in the attached stackblitz example (the one from the starting post) which causes this issue (see picture below). [value] should be bound to option instead of option.name. This causes re-evaluation of the array on blur which boils down to here - which ultimately causes array of objects to turn into an array of strings.
So, unless I missed something else, looks like there's no bug here, just a little misunderstanding.

Have the exact same issue.... why was this behaviour changed?

I have noticed another issue using formControl, caused by Angular Material's team using viewValue.
When inside <mat-chip-row> there is any HTML element, or even just the delete button is wrapped inside some <ng-container>, then whole chip-row's viewValue contains this element's (button with <mat-icon>cancel</mat-icon> in this case) innerText...
So for example, ["Apple"] becomes ["Apple cancel"].
Look at my simple example:
https://stackblitz.com/edit/ovb2sn-s41kjs?file=src%2Fapp%2Fchips-autocomplete-example.html,src%2Fapp%2Fchips-autocomplete-example.ts
All you have to do to reproduce the issue is to click on the text input and then focus it out. This will run Material's blur/focusOut code and update the form control value with the chips' viewValue which becomes ["Apple cancel"].

Very good point for @AlexanderLeonov !

Ok, so I ran into the same issue as OP and luckily it looks like I was able to figure it out.
There's a mistake in the template in the attached stackblitz example (the one from the starting post - just copying link here for convenience) which causes this issue (see picture below). [value] should be bound to option instead of option.name. Losing focus causes re-evaluation of the array which boils down to here - which ultimately causes array of objects to turn into an array of strings.
So, unless I missed something else, looks like there's no bug here, just a little misunderstanding.

Is it a bug or a feature?
I've checked out the documentation for Chips and mat-chip-row @Input() value: any | The value of the chip. Defaults to the content inside the mat-mdc-chip-action-label element.. It specifies that will take the label content if there are no value. I think it is a big change that it isn't reflected in examples and it pass by unnoticed.

That is very true @AlexanderLeonov & @jonastg !
Setting [value] param for mat-chip-row even fixes the issue I have reported a few posts above.

In my opinion, just defaulting to innerText is not a very good idea, and this thread is a very good example of why, especially the last issue reported by @poveu. I think this is not a bug in the sense that the code behaves as designed and doesn't just break unexpectedly. The issue here is that the design itself is very confusing and unclear. I think the component should kick and scream at you if you don't provide a value the way it expects it to be provided. Silent crippling the data without any explanations doesn't seem acceptable to me.

...the data that makes no sense, like the "cancel" part of the removal button.
I agree 100%.

I think that since [value] appears to be from logical perspective, mandatory for <mat-chip-row>, and since we already have angular 16 in material, we can benefit from required inputs. The solution would be to make @Input({requred: true}) value in MatChip source code. Also would be great if this information was documented. So I guess there are a couple of action points to be done.

I would also like to warn, that by changing [value]="option" from [value]="option.name" when enabling chip edit we get [object Object] in the input, because MatChipEditInput is getting the textContent from the input, which is our case is an object.
I have refactored the original example by removing unnecessary code and making add / edit / delete of a chip working with reactive forms approach and with [value]="option" - https://stackblitz.com/edit/angular-6g9jz1-zkc8ak?file=src%2Fapp%2Fchips-input-example.ts,src%2Fapp%2Fchips-input-example.html

Yeah... That's an issue too albeit a different one. Mat components can't really make any assumptions about the object being bound to the value property, hence they should ask app to provide some info/mappings/whatever it is about those objects, or they should clearly describe what assumptions mat components impose on those objects (like having certain field or something) in order for other functionality - like tag editing - to work correctly. This looks either like a missing functionality or a design flaw.
I suspect you can work around this particular issue by redefining .toString() in the tag objects but it feels more like a hack rather than a solution.


Remove commas from keyword list.

This is the same patch as #937 but with the last change date updated this time.

@brammool, I'm not going to send diff to the mailing list this time because it's very easy to obtain a raw diff from the pull request.
Simply adding .diff or .patch in the browser URL bar on any pull request URL visited at GitHub makes a nice raw diff.

Included


Lock wait timeout exceeded error when running multiple calls that includes distributed transactions

Seemingly, subsequent calls with distributed transactions causes database hang due to too many connections due to some problems in connection management. Due to this client get hanged.
When executing the sample client  against the ballerina files [1], [2] following error occurs in client and the client is hanged
Error at client side
com.mysql.cj.jdbc.exceptions.MySQLTransactionRollbackException: Lock wait timeout exceeded; try restarting transaction

We are not getting this error now. Should have been fixed.


Unexpected label when key type is AssetReference

public SerializableDictionary<string, AssetReference> Images = new SerializableDictionary<string, AssetReference>();

Not sure what went wrong, and maybe we should make a new CustomPropertyDrawer for every class with this issue?

Hey @kice , did you manage to resolve this ?

If nothing has changed, then no.


Links to presentations are not public

Links to the presentations at adobecloud are restricted to CTU accounts. It shall be made public.

https://documentcloud.adobe.com/gsuiteintegration/index.html?state={"ids"%3A["1JxvTRhME_5Ecprk_qcegegYUoU49yGN9"]%2C"action"%3A"open"%2C"userId"%3A"100616406588850202743"%2C"resourceKeys"%3A{}} and https://documentcloud.adobe.com/gsuiteintegration/index.html?state={"ids"%3A["1ZKqIy4CdVWQh6bD5MepahdqttsSB21Bm"]%2C"action"%3A"open"%2C"userId"%3A"100616406588850202743"%2C"resourceKeys"%3A{}} in Janas and Max's Open Mic Sessions

@MichalMed I propose to close this issue. I can't even access the files with my CTU account and it is highly unlikely that Jana is going to fix it. All other OpenMic slides are in a shared Google Drive folder that is accessible to anyone with a link, so I consider this problem resolved.

@MichalMed @blcham Once again, I propose to close this issue.


Colored text and shaded table cells

BIPM rapport 2018-02 includes text in color and shaded table cells. That would have been ignored if the text didn't refer to some color which was used.
In case of the colored text, I used stem syntax for coloring, e.g. stem:[color(red)("some text")], which is some kind of a solution for this part...
However, I didn't manage to find an appropriate markup solution for the shading cells issue.
Example from 2018-02:

We have made a point of ignoring colour shading in tables, as our approach has been to emphasise semantics in Metanorma. We do not support this, and we have good reasons for not supporting this.
I will not be implementing this without an explicit requirement from BIPM, and a clear indication that this kind of formatting will be ongoing.

We will put this on hold for now. I don't think it is necessary.


Go SDK Codes: add level

Add log level to FF Golang SDK codes
Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screenshot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66015825e37e7a008bff3f53--harness-developer.netlify.app


Support custom dependency nodes, such as exports

First of all, I want to thank you for such a great plugin!
In our product we use FSD methology and it is crucial to us to keep track of boundaries violations.
But we discovered that boundaries can be broken not only by import statements. There are several other ways of introducing dependencies between modules:

Re-exports. This problem is addressed in the #213
Dynamic imports: const Module = import('path/to/module');
Module mocks, for example: jest.mock

It would be very useful to allow users define their own dependency nodes.
I came up with the following solution:

Introduce the new setting boundaries/additional-dependency-nodes:

{
    // Format: [{ selector: '{esquery selector}', kind: '{value|type}' }]
    'boundaries/additional-dependency-nodes': [
        // Dynamic imports: import('source')
        { selector: 'ImportExpression > Literal', kind: 'value' },

        // Named exports: export { ModuleA } from 'modules/a'
        // Note ':not' pseudo-class here; it addresses parsers that do not have the exportKind property.
        { selector: 'ExportNamedDeclaration:not([exportKind=type]) > Literal', kind: 'value' },

        // Named type exports: export type { ModuleA } from 'modules/a'
        { selector: 'ExportNamedDeclaration[exportKind=type] > Literal', kind: 'type' },

        // And so on. We were able to describe all the cases we needed with this syntax.
    ]
}

Directly select Literal nodes to extract dependency source. This allows us to get rid of dependencyLocation helper and also simplifies how dependecy nodes are defined: we only need a single selector.

What do you think? Am I missing something?
If the solution is OK, I will finalize it by adding tests, validating the settings and updating the documentation.
closes #213

Hi @gridsane , I think that the solution is brilliant! It would be a great improvement for the plugin, thank you very much.
As you said, it would be needed to add documentation about it, tests, etc. Please let me know if I can help you somehow 😃

Hi, @javierbrea! Could you please review the PR?
Changes:

Added predefined settings for exports and dynamic imports.
Added minimal tests to check the new setting. I used only two rules to check the settings: element-types to assert the functionality and external to verify export specifiers. I think copying settings for other rules would be excessive. What do you think?
Updated the documentation and changelog.
Also, added a guide entry to address incompatible changes (see below).

Questions:

Do we need to change error messages and rule descriptions, to avoid using the term "import"? For example, we could change "Importing unknown elements is not allowed" to "Using unknown elements is not allowed".
Do we need to rename the importKind option to simply kind? Now, it can be used in the context of export statements.

Backward compatibility issue and major version bump
I think it should be the new major version, due to incompatible changes in error position calculation. The issue is how dependencyLocation works with multiline imports:
// Single-line
import { ComponentB } from '../component-b/ComponentB.js'
// ------------------------^(start)---------------------^(end)
// { start: { line: 1, column: 27 }, end: { line: 1, column: 57 }}

// Multiline (here is the issue)
import {
// -------------------------^(start)
    ComponentB
} from '../component-b/ComponentB.js'
// --------------------------------------------------------^(end)
// { start: { line: 1, column: 29 }, end: { line:3, column: 59 }}

Referring to Literal nodes will fix the multiline behavior:
import {
    ComponentB
} from '../component-b/ComponentB.js'
// ----^(start)---------------------^(end)

So, if the eslint-disable-next-line directive was used to ignore a multiline import error, it will break in the next version.

I completely agree that the best way is to carefully update the documentation. I'll leave the rest of the documentation untouched, so you can make proper changes.
I like your idea of making 'export' and 'dynamic-import' the defaults in the major release.
However, I just realized that the setting 'additional-dependency-nodes' doesn't permit changes to default values.
Could we rename it to just "dependency-nodes" and allow users to redefine it?
In this case, it would be possible to maintain backward compatibility by redefining it to ['import']. In this scenario, we could leave constants as they are. Duplicated entries will not affect the performance because the final result is an object with selectors as keys. Duplicates will be eliminated, and ESLint will not traverse the same node twice.

@gridsane, you're right about duplicated entries, I didn't notice that the final result is an object, so there is no a performance problem, I'll resolve that conversation.
It's also a good idea to provide users a way to deactivate default dependency nodes, but I don't like too much that users that may want to define their own dependency nodes would have to redefine again the default ones. What about having two different settings, one allowing to redefine the dependency-nodes, and another one enabling to add additional ones? It would look like:
{
    // Next setting allows to enable/disable built-in default dependency nodes.
    // In the first version, "export" and "dynamic-import" should be supported,
    // but they should be disabled by default for an easier version adoption.
    // In an oncoming major version they will be enabled by default,
    // but users will be able to deactivate them using this setting.
    "boundaries/dependency-nodes": ["import", "export", "dynamic-import"],

   // Next setting allows to add custom dependency-nodes.
   // It does not affect to the default ones, so, users don't have to redefine
   // defaults in case they want all defaults enabled and they only want to add more.
    "boundaries/additional-dependency-nodes": [
        {
           selector: "CallExpression[callee.object.name=jest][callee.property.name=mock] > Literal:first-child",
           kind: "value"
        }
    ]
}

The boundaries/dependency-nodes setting should support only strings, and only those that are defined as built-in dependency nodes in the plugin, and the boundaries/additional-dependency-nodes should support only objects.

I reorganized the settings as you suggested. I'm not sure about the changes in "CHANGELOG.md". Should I delete or modify the "Breaking changes" section and the guide?
If there is anything I can tweak, just let me know.

I reorganized the settings as you suggested. I'm not sure about the changes in "CHANGELOG.md". Should I delete or modify the "Breaking changes" section and the guide?

Don't worry @gridsane , I'll review the docs in the release branch.


[method style syntax] Resurrected 49788a86d8c3d4f9b8f83e796625e086adcc02d6

Resurrected dot call syntax

Next PR will add self and a few other additions (or I might add it to this PR as a separate commit)

Built on #844

Any reason why this does not go towards main? As far as I remember, this is a feature we all want and have agree upon a while ago. @sblackshear

Any reason why this does not go towards main? As far as I remember, this is a feature we all want and have agree upon a while ago. @sblackshear

https://github.com/move-language/move/issues/460

Any reason why this does not go towards main? As far as I remember, this is a feature we all want and have agree upon a while ago. @sblackshear

Just a place to iterate, we will merge back to main when it stabilizes.


[add-resource] New Plugin (embed-fontawesome)

I would like to add a plugin to the Grav Repository.
Here are the project details: https://github.com/n-parsons/grav-plugin-embed-fontawesome
The Embed Font Awesome plugin for Grav automatically embeds icons into generated web pages as inline SVGs.

Added to GPM.


Provide a way to specify where the cache is stored

This is a feature request.
The platform specific cache directory is used to store the cache now. I guess the underlying cache provider implementation decides ultimately where the cache is created. However it would be better to provide the developers with an option to specify the cache storage location so that for example in iOS and Android, the app dir can be used.

It is stored in the cache dir: https://github.com/jamesmontemagno/monkey-cache/blob/master/src/MonkeyCache/Utils.cs#L20

Going to implement this today!


Give yourselves some credit!

At the bottom of your README, consider adding some short sections to acknowledge the hard work you've each put into the project, and maybe a link to your favorite home/profile page. You could also acknowledge and link to any open source software you've leveraged. And perhaps add a CONTRIBUTING.md file if you'd like to make it easier for folks to stand on your shoulders.
Personally, I like this "built-with/by" part of the orcanode repo best:

Looks like y'all added some nice content from Build With on down, so I'll close this issue.


Feature: Support for the OpenAPI variation of JSON Schema

The OpenAPI specification contains a slightly modified subset of JSON Schema. It would be handy for my use case if I could validate documents against it.
I'm interested in implementing this, would that be acceptable to integrate into this project? Any advice on how to approach it?

Hi @DavidMikeSimon—thanks for the interest!
I'd definitely be open to adding OpenAPI support. Right now the supported schemas are implemented here: https://github.com/davishmcclurg/json_schemer/tree/master/lib/json_schemer/schema and are subclasses of JSONSchemer::Schema::Base. So I think adding another version there would be the place to start.


Manage Household Page has Issues with Large Data Volumes and CPU Usage.

A lot of people chiming in here: https://powerofus.force.com/0D58000002BLwVb
I took a stroll through the code and didn't see anything OBVIOUS but that page has a nice mix of remote and VF actions so I didn't get too far down the well.

**lurch: add

Tracking W-008591

Included in beta release version 3.77 (Beta 3) and higher

Included in production release version 3.77


[RESTEASY-1512]

jboss-modules targets just wildfly (no longer AS7) and conforms to
wildfly 10.1.0.Final.

Cool, thanks Ron.


Improve compile handling to reduce incorrect warnings

A few changes:

Remove the incorrect warnings when a <Compile Include=> gets converted to a <Compile Update=>
Improving the messages around why 'Update's are required
Treat resource designers the same as any other so that additional sub-elements and attributes are picked up

Sorry about the file format changes which make the diffs a bit useless. I think it's because I did ctrl+k+d on the file and it applied the editorconfig which presumably hadn't been applied before everywhere.
It could be worth going through all the files and auto-formatting as a one-off to apply the editorconfig settings.


[docs] [WIP] Website - Introduce build modes

\cc @DevExpress/testcafe-docs
Please double-check this.
I've introduced three build modes:

testing - when the website is built for testing
development - when the website is built for local deployment
production - when the website is built for publishing

Use cases:

blog comments - won't be added in testing mode; in development mode, comments from a 'staging' thread are displayed; in production mode, public comment threads are displayed.
Google Analytics is added only in production mode.
...

Did I get it right that tests fail because I can't use spawn(..., { env : { ... } } in Travis - I can only assign environment variables in .travis.yml?

okay, trying it with .travis.yml

lgtm

WIP!

have to make sure the spawned process inherits environment variables and it's actually built in testing mode.

yep, it does

FPR

lgtm, but can you add comment to gulp file about possible build configurations and how they affect site functionality, please?

Meh, I surely can but, most probably, noone will update this comment ever.
The way build configurations affect site functionality is implemented in a different place - in website assets.
Who will remember to update a comment in Gulpfile.js when changing website assets?

@VasilyStrelyaev we've just talked to move website assets to this repo, so it makes sense IMO

lgtm

lgtm


Display subtype feature layer

This is a new sample for display subtype feature layer. The design shows a random renderer being applied to the sublayer, this would have added in a lot of unnecessary code so I've opted for a toggle button to switch between the original renderer and one single new one. @JonLavi could you take a first look please?

Don't think we really need to be able to change the minimum scale in the sample to demonstrate it.
Either way, I'd propose a minor UI change:

thanks @tschie, @JonLavi, I've addressed the comments and updated the UI. Could you take another look please? Thanks!

@tschie @JonLavi thanks, all changes updated. Feel free to merge if you think this looks good, otherwise I'll do it when back in the office.


Add Acknowledgement Shutdown Timeout (#631)

See #631

With this one I think I'm all set code-wise for RC.
After the SqsTemplate is merged I'll add it to the sample.
There are a few more blind spots of test coverage overall than I'd like, but I think it's good enough and I'll work on adding more tests when I have the time.

I've added another commit with an API cleanup for the ContainerOptions. It probably should have been another PR, but I was afraid there would be too many conflicts with this one. The individual commits are preserved though.

@maciejwalkowiak with this I'm done!
Feel free to merge when you'd like, and let me know if you have any questions.
Looking forward to the RC!


Update run.py

Hey this is a new PR

Qovery can create a Preview Environment for this PR.
To trigger its creation, please post a comment with one of the following command.

Command
Blueprint environment

/qovery  preview aa190093-9b25-4c7c-8cbf-2c59eec4929d
blueprint-x

/qovery  preview 3e403dbb-d455-4ae9-81bc-54e54197df03
production

/qovery  preview {all|UUID1,UUID2,...}
To preview multiple environments

This comment has been generated from Qovery AI :robot:.
Below, a word from its wisdom :

Write comments that add new information that doesn’t exist in the code

/qovery preview aa190093-9b25-4c7c-8cbf-2c59eec4929d

A preview environment was automatically created via Qovery.
Click on the link below to follow its deployment and use it.
:point_right: [PR] blueprint-x - Update run.py - 2023-10-23T15:12:42Z
Another comment will be posted when deployments are terminated


Add integration tests for ingress and ingress-per-unit

We should have some basic tests in place that deploy traefik, and have it related on both the ingress, and ingress-per-unit interface.
More advanced tests should follow that switch the subdomain/path mode and test the available routes.

For ingress_per_unit, we should replicate https://github.com/canonical/prometheus-k8s-operator/blob/main/tests/integration/test_ingress_with_traefik_k8s.py here. I am honestly surprised I did not yet :-)


clone repo form refacotred to MVP

PR for jira https://issues.jboss.org/browse/GUVNOR-2218

Over all nice looking MVP code. Good to see the code base getting better.

removed author comments

added licences

renamed set methods to show methods

used BaseModal as base class for view implementation

Great, I think we are getting closer to be able to merge.
I still would prefer to @Inject an instance of RepositoryPreferences rather than use the IOC class in CloneRepositoryPresenter. See my original comment in the PR.
Once this has been changed we will need additional PRs for, drools-wb, livespark, optaplanner-wb and kie-wb-distributions repositories to fix the instantiation of CloneRepositoryForm (now CloneRepositoryPresenter) like you've done in GuvnorWorkbenchEntryPoint.
In the listed repositories, look at the xxx-webapp module and the AdministrationPerspective for example: https://github.com/droolsjbpm/drools-wb/blob/master/drools-wb-webapp/src/main/java/org/drools/workbench/client/perspectives/AdministrationPerspective.java#L121

@manstis please, stay tuned, I am not at work to Monday.

done

added addCloseHandler method to presenter

http://github.com/droolsjbpm/guvnor/commit/b8d352790

Thanks for doing this.. I hope you've learned a lot from the experience :)

http://github.com/droolsjbpm/guvnor/commit/02f6fc2f7


Add search to select dropdown with many items like reviewers and partners

For the become dropdown on the account page we have a search field on top to quickly find a specific user. (A side note, this fields should not have checkboxes since it is not multi select.)
This would be useful on more select dropdown like the reviewer and partner input fields found on the submission detail view.

Related to improve design for assinging reviewers, partners, etc https://github.com/HyphaApp/hypha/issues/2723

Being done in another issue.


Bugfix categories.php action delete_category_confirm

one additional check to prevent whole store removal
Don’t ask me how it happened, but it was passed categories_id=0 and I have removed the whole store only with one click. I would like to propose my patch to prevent such behavior. Please also check whether it can happen in osC 3. Best regards
liondron

Thanks. Although not a reproducible bug, extra checks will be added in v2.3.5 to prevent that from occurring at all.


Stratification Bug while using apex(pullback(...))

While trying to use apex(pullback(...)) or ob(pullback(...)) sname is the only attribute populated
Below is what was ran to reproduce this result. Examples came from both demo notebooks

I was able to get the expected result using:
res = stratify(modelATyped=>[[:strata],[:strata],[:strata],[]], # S I R D
        modelBTyped=>[[:disease], [:disease,:infect]],# Q NQ
        typesP
)

function stratify(petri_net1, petri_net2, type_system)
  return pullback([add_cross_terms(petri_net, type_system) for petri_net in [petri_net1, petri_net2]]) |> apex
end

if you're following the stratification made easy demo, then you are getting expected results.
The pullback you are trying to construct was called naive_stratification in the notebook, and it was an example intended to demonstrate that "directly" stratifying those two models will produce a model that has no transitions. (nt counts the number of transitions and the notebook showsnt(naive_stratification) == 0). The stratify helper function automates how you have to update SIRD and Quarantine the models such that the stratification that we really want is computed via Catlab's pullback.
Let me know if any of the wording in that notebook can be fixed or if this doesn't actually address your problem!


MF-998 - Add Twins service to Makefile and docker-compose.yml

Signed-off-by: Darko Draskovic<EMAIL_ADDRESS>

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1035   +/-   ##
=======================================
  Coverage   79.16%   79.16%
=======================================
  Files          95       95
  Lines        6610     6610
=======================================
  Hits         5233     5233
  Misses       1065     1065
  Partials      312      312

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 1c2c86b...353e448. Read the comment docs.


[enh] FilterCompare validator

related to #4479 #14013
the proposal is to create a validation to be easily used with the Query::andFilterCompare() method.
the proposed syntax is
[
    'date'
    'comparable',
    'allowedOperators' => ['=', '>=',  '<=', ':']
    'validator' => [
       'date',
       'min' => '2016-01-01',
    ], // date equals '>=2017-01-01' passes
],
[
    'name',
    'allowedOperators' => ['=', '~'],
    'validator' => [
        'string',
    ], // '~hello' passes but '>5' fails
    'defaultOperator' => '~', // 'hello' is turned into '~hello' but '=hello' goes unchanged
]

that way they can be validated before being sent to a query
->andFilterCompare('date', $this->date)
->andFilterCompare('name', $this->name)

@klimov-paul what do you think?


Update NFRs and Glossary for Developer Guide

Codecov Report

Merging #43 (55bcd3e) into master (2d807b7) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #43   +/-   ##
=========================================
  Coverage     66.83%   66.83%
  Complexity      488      488
=========================================
  Files            84       84
  Lines          1622     1622
  Branches        198      198
=========================================
  Hits           1084     1084
  Misses          477      477
  Partials         61       61

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 2d807b7...55bcd3e. Read the comment docs.


ESP32-RFID Project with WebServer won't compile

There is a bug regarding this dependency:
me-no-dev/ESP Async<EMAIL_ADDRESS>I replaced that line with https://github.com/me-no-dev/ESPAsyncWebServer.git to get it to compile, but that's not a real solution. You can see the error discussed here:
https://github.com/me-no-dev/ESPAsyncWebServer/issues/1147
Could you help find the right way to fix it?

Hmm interesting... Can you try with this https://github.com/esphome/ESPAsyncWebServer library which is a fork of the original?


Integrate blockstream with ethers

See: #1088

@justinbarry -- can you get the conflict sorted and get this merged first thing after the meeting?

@pgebheim FYI, I dropped the demo code.


Clone of PR #585

CI appears to be in an invalid state; creating a PR with @scolsen's commits to see if I can't get it unstuck.
Fixes #442.

Same issue on this PR:
starting build "59d005a5-76a6-4ce7-ac87-b0aefb08762a"

FETCHSOURCE
Initialized empty Git repository in /workspace/.git/
From https://github.com/google/ground-android
 * branch            1ffc1024a033b04f90a02ac16040aac6f47d4393 -> FETCH_HEAD
HEAD is now at 1ffc102 Merge branch 'master' of https://github.com/google/ground-android into rename-offline-areas
BUILD
Starting Step #0 - "Copying gradle build cache tar from GCS"
Starting Step #2 - "Copy .git directory for versioning"
Step #0 - "Copying gradle build cache tar from GCS": Already have image (with digest): gcr.io/cloud-builders/gsutil
Step #2 - "Copy .git directory for versioning": Already have image (with digest): gcr.io/cloud-builders/git
Step #2 - "Copy .git directory for versioning": Cloning into 'tmp'...
Step #2 - "Copy .git directory for versioning": mv: cannot move 'tmp/.git' to './.git': Directory not empty
Finished Step #2 - "Copy .git directory for versioning"
ERROR
ERROR: build step 2 "gcr.io/cloud-builders/git" failed: step exited with non-zero status: 1


Rare 'reading speed in wrong direction error' on one-way zero distance loop edge.

When running random tests for #1581 the following error came up, see the modified test here:
cf65bb7882315db709dca1ac9e22d7bd710af4be
java.lang.IllegalStateException: Calculating time should not require to read speed from edge in wrong direction. (3 - 3) (49.400074021519885,9.700012051314385), (49.400074021519885,9.700012051314385) 0.0 Reverse:true, fwd:true, bwd:false

	at com.graphhopper.routing.weighting.AbstractWeighting.calcMillis(AbstractWeighting.java:53)
	at com.graphhopper.routing.weighting.FastestWeighting.calcMillis(FastestWeighting.java:83)
	at com.graphhopper.routing.ch.PreparationWeighting.calcMillis(PreparationWeighting.java:57)
	at com.graphhopper.routing.ch.Path4CH.expandEdge(Path4CH.java:53)
	at com.graphhopper.routing.ch.Path4CH.expandSkippedEdges(Path4CH.java:72)
	at com.graphhopper.routing.ch.Path4CH.expandEdge(Path4CH.java:57)
	at com.graphhopper.routing.ch.Path4CH.processEdge(Path4CH.java:47)
	at com.graphhopper.routing.PathBidirRef.extract(PathBidirRef.java:79)
	at com.graphhopper.routing.AbstractBidirAlgo.extractPath(AbstractBidirAlgo.java:297)
	at com.graphhopper.routing.AbstractBidirAlgo.calcPath(AbstractBidirAlgo.java:95)
	at com.graphhopper.routing.RandomCHRoutingTest.issue1574_random(RandomCHRoutingTest.java:98)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.rules.RunRules.evaluate(RunRules.java:20)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
	at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
	at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
	at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
	at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)

The problem is that the speed is set to zero and that this is decoupled from the access bits. See e.g. #367
I have thought this through multiple times and wanted to create a special SpeedAccessEncodedValue object that automatically sets the access bits based on the speed. But this is a bit tricky and would not help when we calculate the speed and access limits on demand. So e.g. the estimated speed could be well over 10km/h and still the truck does not fit through the bridge.

Where is the speed set to zero ? Or do you mean the distance (which is 0 at the point the exception is thrown in my debugger).

I was too hasty as I saw the "0" in the exception, but you are right that the distance==0.
Still this issue appears because speed and access values are not in sync. So everytime you set the speed to 0 (or any other property that will lead to weight==infinity) you have to set the edge inaccessible explicitly.
This is also a conceptual problem that we use "static access properties" instead of "dynamic weighting". See e.g. the EdgeFilter in QueryGraph where it could happen that the weight==infinity for an allowed edge ("access-wise"). See #729

Ok I see, but in this case the speed is not zero:

It's a zero distance (and zero weight, because of fastest weighting) (non-shortcut) loop edge that is read in the wrong direction during path extraction.

Related to: #1525, #1247

I just stumbled also over this still open issue #1234

A possible explanation is that a zero distance loop is usually an error in OSM data and probably almost never tagged with one_way, but if we use a zero distance loop with only one direction we get the above error

But we avoid distance==0 in the OSM import: https://github.com/graphhopper/graphhopper/blob/master/reader-osm/src/main/java/com/graphhopper/reader/osm/OSMReader.java#L740

But we avoid distance==0 in the OSM import:

Yes, and also loops as just came to my mind again: #1531

I still might have a look what is going on here, not sure if we have to rely on the import or if this can be fixed easily.

So it turned out there was in fact a problem (I only realized I had fixed it after I had fixed it :))
When there was a loop at a node we were contracting like at node 0 here:
0-1
o

we introduced a shortcut from 0 to 1 where the first skipped edge was the loop and this could cause the read in the wrong direction error later when unpacking the shortcut. It did not matter whether the distance was 0 or not, but unfortunately GHUtility#buildRandomGraph always uses distance 0 for loop edges.
Fixed in b2ba5bd6a107eb2966135735b2c05186f0624254.


hh: invalid option -- 'P'

Great tool btw. It saves me ton of typing. Thank you for sharing your effort!
when I type mci -P and press Ctrl+R then I get this:
hh: invalid option -- 'P'
Usage: hh [option] [arg1] [arg2]...
Shell history suggest box:

  --favorites              -f ... show favorites view
...

I am not sure if this is a feature or bug but I would expect to browse the history as usual, not the help to be printed out.
hh --version
hh version "1.19"
   build   "Nov 26 2015 21:18:22"

Thank you!
Ad bug: reproducible - command line builder to add options/parameters separator before parameters e.g.
hh -- mci -P

Quickfix: you may easily fix this problem by changing the following line in .bashrc from:
bind '"\C-r": "\C-a hh \C-j"'    # bind hh to Ctrl-r

to
bind '"\C-r": "\C-a hh -- \C-j"'    # bind hh to Ctrl-r

Thank you.


Fix the case-sensitive comparison on the seed name

resolves #429
Description
To reproduce the Bug create a seed file named MySeed.csv  in your seed folder with the following content :
adapter,version
glue,1.8.1

Run 2 times : dbt seed
The first time the table did not exist in glue metastore, so the command pass.
❯ dbt seed
14:37:32  Running with dbt=1.8.6
14:37:33  Registered adapter: glue=1.8.1
14:37:33  Found 1 seed, 879 macros
14:37:33
14:37:34  Concurrency: 1 threads (target='dev-glue')
14:37:34
14:37:34  1 of 1 START seed file dbt.MySeed .............................................. [RUN]
14:37:51  1 of 1 OK loaded seed file dbt.MySeed .......................................... [CREATE 1 in 16.85s]
14:37:51
14:37:51  Finished running 1 seed in 0 hours 0 minutes and 17.59 seconds (17.59s).
14:37:51
14:37:51  Completed successfully
14:37:51
14:37:51  Done. PASS=1 WARN=0 ERROR=0 SKIP=0 TOTAL=1

The second time the command did not pass
❯ dbt seed
14:37:58  Running with dbt=1.8.6
14:37:58  Registered adapter: glue=1.8.1
14:37:58  Found 1 seed, 879 macros
14:37:58
14:37:59  Concurrency: 1 threads (target='dev-glue')
14:37:59
14:37:59  1 of 1 START seed file dbt.MySeed .............................................. [RUN]
14:38:03  Glue adapter: Glue returned `error` for statement None for code

csv = [{"adapter": "glue", "version": "1.8.1"}]
df = spark.createDataFrame(csv)
table_name = 'dbt.MySeed'
if (spark.sql("show tables in dbt").where("tableName == 'MySeed'").count() > 0):
    df.write        .mode("overwrite")        .format("parquet")        .insertInto(table_name, overwrite=True)
else:
    df.write        .option("path", "s3://dbt-glue-test-xxxxxxxxxxxx/simple-test/dbt/MySeed")        .format("parquet")        .saveAsTable(table_name)
SqlWrapper2.execute("""select * from dbt.MySeed limit 1""")
, AnalysisException: Table `dbt`.`MySeed` already exists.
14:38:03  1 of 1 ERROR loading seed file dbt.MySeed ...................................... [ERROR in 3.59s]
14:38:03
14:38:03  Finished running 1 seed in 0 hours 0 minutes and 4.26 seconds (4.26s).
14:38:03
14:38:03  Completed with 1 error and 0 warnings:
14:38:03
14:38:03    Database Error in seed MySeed (seeds/MySeed.csv)
  GlueCreateCsvFailed
14:38:03
14:38:03  Done. PASS=0 WARN=0 ERROR=1 SKIP=0 TOTAL=1

I find in the Athena documentation (sorry not in Glue documentation) Database, table, and column name requirements

Acceptable characters for database names, table names, and column names in AWS Glue must be a UTF-8 string and should be in lower case.

To solve this issue I added lower function in the where statement ("tableName == lower('MySeed')").
dbt seed
14:44:46  Running with dbt=1.8.6
14:44:46  Registered adapter: glue=1.8.1
14:44:47  Found 1 seed, 879 macros
14:44:47
14:44:48  Concurrency: 1 threads (target='dev-glue')
14:44:48
14:44:48  1 of 1 START seed file dbt.MySeed .............................................. [RUN]
14:44:53  1 of 1 OK loaded seed file dbt.MySeed .......................................... [CREATE 1 in 5.74s]
14:44:53
14:44:53  Finished running 1 seed in 0 hours 0 minutes and 6.51 seconds (6.51s).
14:44:53
14:44:53  Completed successfully
14:44:53
14:44:53  Done. PASS=1 WARN=0 ERROR=0 SKIP=0 TOTAL=1
❯ dbt seed
15:02:45  Running with dbt=1.8.6
15:02:45  Registered adapter: glue=1.8.1
15:02:46  Found 1 seed, 879 macros
15:02:46
15:03:04  Concurrency: 1 threads (target='dev-glue')
15:03:04
15:03:04  1 of 1 START seed file dbt.MySeed .............................................. [RUN]
15:04:38  1 of 1 OK loaded seed file dbt.MySeed .......................................... [CREATE 1 in 93.38s]
15:04:38
15:04:38  Finished running 1 seed in 0 hours 1 minutes and 51.96 seconds (111.96s).
15:04:38
15:04:38  Completed successfully
15:04:38
15:04:38  Done. PASS=1 WARN=0 ERROR=0 SKIP=0 TOTAL=1

Checklist

[X] I have signed the CLA
[X] I have run this code in development and it appears to resolve the stated issue
[ ] This PR includes tests, or tests are not required/relevant for this PR
[X] I have updated the CHANGELOG.md and added information about my change to the "dbt-glue next" section.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Nice, working on my side.
@moomindani could you please take a look when you have some time ? thanks!

Conflict on CHANGELOG.md fixed.

Thank you for your contribution :)


feat(ContentWithQuestion):  add ContentWithQuestion

Task Description
增加原有的ContentWithQuestion组件
Upgrade Compatibility

 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.wt01067819 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


logitech: don't show hidden features

Signed-off-by: Filipe Laíns<EMAIL_ADDRESS>

Like a CHECK_BIT macro?

yep, that's what I meant, thanks :)


Alternate signing algorithm support

Right now it looks like identity server only supports one signing algorithm. Is it possible to add others?

Right now we only support RSA with SHA256.
.NET / .NET Core had some problems with supporting other algorithms x-plat without multi-targeting. This might be resolved now with .NET Core 2. We'll have to look into it post IS4 2.0.

That's great to see that you've added this to the milestone. Will PS256 algorithm also be supported?

tbh - I didn't have yet to research yet. If you want to have a look - feel free.

Jose-Jwt (for .Net & .Net Core) supports a lot of alternative algorithms, also PS256. Would including this lib to IdentityServer be an option?

So does the Microsoft JWT handler - which is what we currently use.
That being said - you can use whatever JWT library you want by implementing the ITokenCreationService.

@leastprivilege I'm looking at ITokenCreationService and it's unclear how I can implement it to provide ES256 signatures.
As far as I can tell, the DefaultTokenCreationService can be used as-is, instead we just need to supply an ES256 SecurityKey via the IKeyMaterialService (as it's passed into the System.IdentityModel.Tokens.Jwt.JwtHeader constructor which takes care of the rest... I think?)
...so how do we supply an ES256 key?

Will be fixed in 3.0


reject creating event in onEventCreate

If we want to reject creating an event when the user clicked to add event we couldn't do it.
But now we can return false to reject adding the event to the calendar.
there is deleteFunction in onCreateEvent, but functionality is differnt. deleteFunction works when onCreateEvent finished and event added to the calendar then the user can call it to delete the event.

Thanks @raftx24, that's also a good move!
Now published in version 2.2.0 and updated documentation.


chore: workaround wrangler dev streaming issue

#652  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @hi-ogawa and the rest of your teammates on  Graphite


Das_Geek: Watch riveragroup.com

Das_Geek requests the watch of the watch_keyword riveragroup\.com. See the MS search here and the Stack Exchange search here.

riveragroup\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Machavity in Charcoal HQ


Actions Palooza

Goal: Uplevel fellows to understand workflow automations from 11/3-12/15

Starting: 11/3-11/17
IssueOps/Communications

labels
welcome messages

Post 11/17-12/12
Intermediate:

CI bugs

Advanced: Security workflows

[ ] #130
[ ] Scorecards

Will reopen lateer

https://github.com/github/octoseven-advocats/issues/121


Webmanifest fetching improvements

fixes #1194
fixes #1209

@CedrikNikita I have fixed bugs that I have found before


fix rviz settings

Change the sytle of pointcloud (Points -> Squares).
Fix topic name of checkpoint etc.
Enable visualization of predicted paths of dynamic objects.


Wireguard does not work after upgrade to 3227.2.0

Wireguard interface stopped getting ip address. Showing link status:  link/none.
Minimal WG config to reproduce:

Create file at /etc/wireguard/wg0.conf with the contents:

[Interface]
PrivateKey = GGBq7heupvx84YpvsffxbAJlLYGIwhl5YqJaBbif+UE=
ListenPort = 5555
Address = <IP_ADDRESS>/32

Run wg-quick wg0 up
Run ip a

The output on flatcar v. 3227.2.0:
...
wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000
    link/none
...

The output on flatcar v. 3139.2.3:
...
wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000
    link/none
    inet <IP_ADDRESS>/32 scope global wg0
       valid_lft forever preferred_lft forever
...

Hi @zhanbalam,
Sorry about that - we're currently investigating on some issues related to systemd-networkd, yours might be linked.
Could you please provide the output of:
networkctl list
networkctl status wg0
journalctl --no-pager --boot -u systemd-networkd

$ networkctl list
IDX LINK       TYPE      OPERATIONAL SETUP
  1 lo         loopback  carrier     unmanaged
  2 enp7s0     ether     routable    configured
  3 vlan       vlan      routable    configured
  4 wg-private wireguard carrier     failed
  5 wg-default wireguard carrier     failed
 12 wg0        wireguard carrier     failed

6 links listed.

$ networkctl status wg0
● 12: wg0
                     Link File: /usr/lib/systemd/network/99-default.link
                  Network File: /usr/lib/systemd/network/zz-default.network
                          Type: wireguard
                         State: carrier (failed)
                  Online state: offline
                           MTU: 1420 (max:<PHONE_NUMBER>)
                         QDisc: noqueue
  IPv6 Address Generation Mode: none
          Queue Length (Tx/Rx): 1/1
             Activation Policy: up
           Required For Online: yes

Jul 25 10:54:06 localhost systemd-networkd[1012]: wg0: Failed
Jul 25 10:54:06 localhost systemd-networkd[1012]: wg0: Link UP
Jul 25 10:54:06 localhost systemd-networkd[1012]: wg0: Gained carrier
Jul 25 12:03:11 localhost systemd-networkd[1012]: wg0: Link DOWN
Jul 25 12:03:11 localhost systemd-networkd[1012]: wg0: Lost carrier
Jul 25 12:03:12 localhost systemd-networkd[1012]: wg0: Bumping MTU bytes from 1420 to 1500 because of stacked device. If it is not desired, then please explicitly specify MTUBytes= setting.
Jul 25 12:03:12 localhost systemd-networkd[1012]: wg0: Failed to configure DHCPv4 client: Invalid argument
Jul 25 12:03:12 localhost systemd-networkd[1012]: wg0: Failed
Jul 25 12:03:12 localhost systemd-networkd[1012]: wg0: Link UP
Jul 25 12:03:12 localhost systemd-networkd[1012]: wg0: Gained carrier

$ journalctl --no-pager --boot -u systemd-networkd
Jul 21 16:46:24 localhost systemd[1]: Starting Network Configuration...
Jul 21 16:46:24 localhost systemd-networkd[1012]: lo: Link UP
Jul 21 16:46:24 localhost systemd-networkd[1012]: lo: Gained carrier
Jul 21 16:46:24 localhost systemd-networkd[1012]: Enumeration completed
Jul 21 16:46:24 localhost systemd[1]: Started Network Configuration.
Jul 21 16:46:25 localhost systemd-networkd[1012]: vlan: netdev ready
Jul 21 16:46:25 localhost systemd-networkd[1012]: enp7s0: Link UP
Jul 21 16:46:25 localhost systemd-networkd[1012]: vlan: Link UP
Jul 21 16:46:27 localhost systemd-networkd[1012]: enp7s0: Gained carrier
Jul 21 16:46:27 localhost systemd-networkd[1012]: vlan: Gained carrier
Jul 21 16:46:29 localhost systemd-networkd[1012]: vlan: Gained IPv6LL
Jul 21 16:46:29 localhost systemd-networkd[1012]: wg-default: Link UP
Jul 21 16:46:29 localhost systemd-networkd[1012]: wg-default: Gained carrier
Jul 21 16:46:29 localhost systemd-networkd[1012]: wg-private: Link UP
Jul 21 16:46:29 localhost systemd-networkd[1012]: wg-private: Gained carrier
Jul 21 16:46:29 localhost systemd-networkd[1012]: wg-private: Bumping MTU bytes from 1420 to 1500 because of stacked device. If it is not desired, then please explicitly specify MTUBytes= setting.
Jul 21 16:46:29 localhost systemd-networkd[1012]: wg-private: Failed to configure DHCPv4 client: Invalid argument
Jul 21 16:46:29 localhost systemd-networkd[1012]: wg-private: Failed
Jul 21 16:46:29 localhost systemd-networkd[1012]: wg-default: Bumping MTU bytes from 1420 to 1500 because of stacked device. If it is not desired, then please explicitly specify MTUBytes= setting.
Jul 21 16:46:29 localhost systemd-networkd[1012]: wg-default: Failed to configure DHCPv4 client: Invalid argument
Jul 21 16:46:29 localhost systemd-networkd[1012]: wg-default: Failed
Jul 21 16:46:29 localhost systemd-networkd[1012]: enp7s0: Gained IPv6LL
Jul 21 16:46:31 localhost systemd-networkd[1012]: enp7s0: DHCPv4 address <IP_ADDRESS>/26, gateway <IP_ADDRESS> acquired from <IP_ADDRESS>
Jul 25 09:00:37 localhost systemd-networkd[1012]: wg0: Bumping MTU bytes from 1420 to 1500 because of stacked device. If it is not desired, then please explicitly specify MTUBytes= setting.
Jul 25 09:00:37 localhost systemd-networkd[1012]: wg0: Failed to configure DHCPv4 client: Invalid argument
Jul 25 09:00:37 localhost systemd-networkd[1012]: wg0: Failed
Jul 25 09:00:37 localhost systemd-networkd[1012]: wg0: Link UP
Jul 25 09:00:37 localhost systemd-networkd[1012]: wg0: Gained carrier
Jul 25 09:08:47 localhost systemd-networkd[1012]: wg0: Link DOWN
Jul 25 09:08:47 localhost systemd-networkd[1012]: wg0: Lost carrier
Jul 25 09:08:56 localhost systemd-networkd[1012]: wg0: Link UP
Jul 25 09:08:56 localhost systemd-networkd[1012]: wg0: Gained carrier
Jul 25 09:08:56 localhost systemd-networkd[1012]: wg0: Reconfiguring with /usr/lib/systemd/network/zz-default.network.
Jul 25 09:08:56 localhost systemd-networkd[1012]: wg0: Bumping MTU bytes from 1420 to 1500 because of stacked device. If it is not desired, then please explicitly specify MTUBytes= setting.
Jul 25 09:08:56 localhost systemd-networkd[1012]: wg0: Failed to configure DHCPv4 client: Invalid argument
Jul 25 09:08:56 localhost systemd-networkd[1012]: wg0: Failed
Jul 25 09:12:05 localhost systemd-networkd[1012]: wg0: Link DOWN
Jul 25 09:12:05 localhost systemd-networkd[1012]: wg0: Lost carrier
Jul 25 09:12:09 localhost systemd-networkd[1012]: wg0: Link UP
Jul 25 09:12:09 localhost systemd-networkd[1012]: wg0: Gained carrier
Jul 25 09:12:09 localhost systemd-networkd[1012]: wg0: Reconfiguring with /usr/lib/systemd/network/zz-default.network.
Jul 25 09:12:09 localhost systemd-networkd[1012]: wg0: Bumping MTU bytes from 1420 to 1500 because of stacked device. If it is not desired, then please explicitly specify MTUBytes= setting.
Jul 25 09:12:09 localhost systemd-networkd[1012]: wg0: Failed to configure DHCPv4 client: Invalid argument
Jul 25 09:12:09 localhost systemd-networkd[1012]: wg0: Failed
Jul 25 09:20:12 localhost systemd-networkd[1012]: wg0: Link DOWN
Jul 25 09:20:12 localhost systemd-networkd[1012]: wg0: Lost carrier
Jul 25 09:20:15 localhost systemd-networkd[1012]: wg0: Bumping MTU bytes from 1420 to 1500 because of stacked device. If it is not desired, then please explicitly specify MTUBytes= setting.
Jul 25 09:20:15 localhost systemd-networkd[1012]: wg0: Failed to configure DHCPv4 client: Invalid argument
Jul 25 09:20:15 localhost systemd-networkd[1012]: wg0: Failed
Jul 25 09:20:15 localhost systemd-networkd[1012]: wg0: Link UP
Jul 25 09:20:15 localhost systemd-networkd[1012]: wg0: Gained carrier
Jul 25 09:22:36 localhost systemd-networkd[1012]: wg0: Link DOWN
Jul 25 09:22:36 localhost systemd-networkd[1012]: wg0: Lost carrier
Jul 25 09:22:56 localhost systemd-networkd[1012]: wg0: Bumping MTU bytes from 1420 to 1500 because of stacked device. If it is not desired, then please explicitly specify MTUBytes= setting.
Jul 25 09:22:56 localhost systemd-networkd[1012]: wg0: Failed to configure DHCPv4 client: Invalid argument
Jul 25 09:22:56 localhost systemd-networkd[1012]: wg0: Failed
Jul 25 09:22:56 localhost systemd-networkd[1012]: wg0: Link UP
Jul 25 09:22:56 localhost systemd-networkd[1012]: wg0: Gained carrier
Jul 25 10:54:04 localhost systemd-networkd[1012]: wg0: Link DOWN
Jul 25 10:54:04 localhost systemd-networkd[1012]: wg0: Lost carrier
Jul 25 10:54:06 localhost systemd-networkd[1012]: wg0: Bumping MTU bytes from 1420 to 1500 because of stacked device. If it is not desired, then please explicitly specify MTUBytes= setting.
Jul 25 10:54:06 localhost systemd-networkd[1012]: wg0: Failed to configure DHCPv4 client: Invalid argument
Jul 25 10:54:06 localhost systemd-networkd[1012]: wg0: Failed
Jul 25 10:54:06 localhost systemd-networkd[1012]: wg0: Link UP
Jul 25 10:54:06 localhost systemd-networkd[1012]: wg0: Gained carrier
Jul 25 12:03:11 localhost systemd-networkd[1012]: wg0: Link DOWN
Jul 25 12:03:11 localhost systemd-networkd[1012]: wg0: Lost carrier
Jul 25 12:03:12 localhost systemd-networkd[1012]: wg0: Bumping MTU bytes from 1420 to 1500 because of stacked device. If it is not desired, then please explicitly specify MTUBytes= setting.
Jul 25 12:03:12 localhost systemd-networkd[1012]: wg0: Failed to configure DHCPv4 client: Invalid argument
Jul 25 12:03:12 localhost systemd-networkd[1012]: wg0: Failed
Jul 25 12:03:12 localhost systemd-networkd[1012]: wg0: Link UP
Jul 25 12:03:12 localhost systemd-networkd[1012]: wg0: Gained carrier

Thanks @sms-system for providing the logs. If you have the hand on the instance, could you try to set the KeepConfiguration=yes parameter?
Or directly use this Ignition configuration:
{
  "ignition": {
    "version": "3.3.0"
  },
  "storage": {
    "files": [
      {
        "path": "/etc/systemd/networkd/zz-default.dropins/keep.conf",
        "contents": {
          "source": "data:,%5BNetwork%5D%0AKeepConfiguration%3Dyes%0A"
        }
      }
    ]
  }
}

@tormath1 Nope, it doesn't work
$ cat /etc/systemd/networkd/zz-default.network.d/keep.conf
[Network]
KeepConfiguration=yes

$ sudo reboot

$ journalctl --no-pager --boot -u systemd-networkd
Jul 27 10:54:54 localhost systemd[1]: Starting Network Configuration...
Jul 27 10:54:54 localhost systemd-networkd[992]: lo: Link UP
Jul 27 10:54:54 localhost systemd-networkd[992]: lo: Gained carrier
Jul 27 10:54:54 localhost systemd-networkd[992]: Enumeration completed
Jul 27 10:54:54 localhost systemd[1]: Started Network Configuration.
Jul 27 10:54:55 localhost systemd-networkd[992]: vlan: netdev ready
Jul 27 10:54:55 localhost systemd-networkd[992]: enp7s0: Link UP
Jul 27 10:54:55 localhost systemd-networkd[992]: vlan: Link UP
Jul 27 10:54:57 localhost systemd-networkd[992]: enp7s0: Gained carrier
Jul 27 10:54:58 localhost systemd-networkd[992]: vlan: Gained carrier
Jul 27 10:54:59 localhost systemd-networkd[992]: enp7s0: Gained IPv6LL
Jul 27 10:54:59 localhost systemd-networkd[992]: vlan: Gained IPv6LL
Jul 27 10:54:59 localhost systemd-networkd[992]: wg-default: Link UP
Jul 27 10:54:59 localhost systemd-networkd[992]: wg-default: Gained carrier
Jul 27 10:54:59 localhost systemd-networkd[992]: wg-private: Bumping MTU bytes from 1420 to 1500 because of stacked device. If it is not desired, then please explicitly specify MTUBytes= setting.
Jul 27 10:54:59 localhost systemd-networkd[992]: wg-private: Failed to configure DHCPv4 client: Invalid argument
Jul 27 10:54:59 localhost systemd-networkd[992]: wg-private: Failed
Jul 27 10:54:59 localhost systemd-networkd[992]: wg-default: Bumping MTU bytes from 1420 to 1500 because of stacked device. If it is not desired, then please explicitly specify MTUBytes= setting.
Jul 27 10:54:59 localhost systemd-networkd[992]: wg-default: Failed to configure DHCPv4 client: Invalid argument
Jul 27 10:54:59 localhost systemd-networkd[992]: wg-default: Failed
Jul 27 10:54:59 localhost systemd-networkd[992]: wg-private: Link UP
Jul 27 10:54:59 localhost systemd-networkd[992]: wg-private: Gained carrier
Jul 27 10:55:01 localhost systemd-networkd[992]: enp7s0: DHCPv4 address <IP_ADDRESS>/26, gateway <IP_ADDRESS> acquired from <IP_ADDRESS>

$ networkctl status wg-private
● 4: wg-private
                     Link File: /usr/lib/systemd/network/99-default.link
                  Network File: /usr/lib/systemd/network/zz-default.network
                          Type: wireguard
                         State: carrier (failed)
                  Online state: offline
                           MTU: 1420 (max:<PHONE_NUMBER>)
                         QDisc: noqueue
  IPv6 Address Generation Mode: none
          Queue Length (Tx/Rx): 1/1
             Activation Policy: up
           Required For Online: yes

Jul 27 10:54:59 localhost systemd-networkd[992]: wg-private: Bumping MTU bytes from 1420 to 1500 because of stacked device.>
Jul 27 10:54:59 localhost systemd-networkd[992]: wg-private: Failed to configure DHCPv4 client: Invalid argument
Jul 27 10:54:59 localhost systemd-networkd[992]: wg-private: Failed
Jul 27 10:54:59 localhost systemd-networkd[992]: wg-private: Link UP
Jul 27 10:54:59 localhost systemd-networkd[992]: wg-private: Gained carrier

Sorry, the correct path should be: /etc/systemd/network/zz-default.network.d/keep.conf

Oh, yes. Wireguard works with this drop-in now

according to the documentation^1:

The setting "dhcp" implies "dhcp-on-stop", and "yes" implies "dhcp" and "static".

I think we could default to KeepConfiguration=yes in place of this: https://github.com/flatcar-linux/init/blob/b99ff0626f5983af7aee47e95f34991d42f68e5b/systemd/network/zz-default.network#L3


Pull in apis and conformance tests from knative.dev/serving

This PR only copies the whole history.  Modifications will follow.

/hold

Going to Rebase & Merge


Add location to glFragColor in WebGL preprocessor

To simplify some specific uses of MultiRenderTarget it would be handy to have `layout(location = 0) prepended to the glFragColor output. Without this you cannot declare another output buffer as in OpenGL ES 3 all output locations must be specified.
This change shouldn't have any impact on typical use but makes it easier for custom MRT/Deferred shading situations.

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/13427/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13427/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13427/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/13427/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/13427/merge
https://gui.babylonjs.com/?snapshot=refs/pull/13427/merge
https://nme.babylonjs.com/?snapshot=refs/pull/13427/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/13427/merge#BCU1XR#0


MVP of SingleStore documentation

Proposed changes
Created the first version of the SingleStore documentation.
Merge timing
ASAP once approved
Related issues (optional)
None

Thanks so much for the feedback.  I have accepted all code changes requested and believe this is good to go.  @tcgilbert @forstisabella - Please feel free to merge this PR into the mainline.  Thanks so much.

@forstisabella, you can include this in the next docs deployment.
@ugpeter, since the catalog metadata has been submitted, we’re ready to move the integration to Public Beta once the docs are live. If you’d prefer to wait for a specific date, please let me know. Otherwise, I’ll proceed with making the integration live.


Stream raw bus events

Please advice me how can I use your lib to replay all bus events (CAN frames, ETH frames etc...) in the log file. (with stream or iterator interface)

include events from all channels in chronological order.
provide the timestamp of the event
provide the raw data of the event (without signal parsing)
provide the channel group
support unsorted measurement files
support VLSD channels

update: edited for clarity, and specified the request

I build an example in src/example/java/de/richardliebscher/mdf4/BusEventsExample.java.  The code any works in the main branch, because version 0.2.0 is missing some features, like reading VLSD channels and structures.
Unsorted measurement files are not supported and will not be supported anytime soon, because of it's complexity.
I hope this helps you. If anything is unclear, just ask.


Crop Issues

So i am able to detect a video using
python detect_video.py --weights ./checkpoints/custom-416 --size 416 --model yolov4 --video ./data/video/car1.mp4 --output ./detections/recognition.avi --crop
however the license plate image is not saved in the detect/crop folder.
I would be glad for help

i was able to get the issue fixed. i realized that at the particular frame there was no license plate detected


feat(Analysis/Distribution/SchwartzMap): projection to ZeroAtInfty and corresponding type class

Adds a characterization of ZeroAtInfty in terms of norms and uses one direction to show that every Schwartz function is zero at infinity.
We also add a few lemmas that characterize elements of the cocompact filter in terms of norm estimates.

Part of a project to prove integration by parts for the partial derivatives on Schwartz space.

bors merge


Clientd (REST API)

Initial stup for clientd REST API + cli to interact with it.
the tests are only vanity. will refactor them if everything is setup.

It's a little weird our the Success key is capitalized in the response. Can we lower-case it?
{
  "Success": {
    "coins": [],
    "pending": {
      "transactions": []
    }
  }
}

Besides these comments the PR looks great.

🎉 🎉 🎉


Add more features to chat

Among other things, we are adding the ability to delete and edit messages.

hey! I wasn't able to run this because it doesn't find ViewAction::FingerHoverIn on the makepad-widgets package in the moxin-changes branch. But I'll comment on what i saw from a brief look.

hey! I wasn't able to run this because it doesn't find ViewAction::FingerHoverIn on the makepad-widgets package in the moxin-changes branch. I'll see if i can fix it, but I'll comment on what i saw from a brief look.

Cargo.lock changes should fix this


Monitor and alert on disk (s.m.a.r.t.) health

Details
Describe the solution you'd like:
I want to monitor my Kubernetes OS and ceph disks as well as my NAS disks.
Anything else you would like to add:
It seems pretty hacky to accomplish this, see different ways to possibly solve this below.
Additional Information:
WIth Prometheus:

https://github.com/prometheus/node_exporter#textfile-collector
https://github.com/prometheus-community/node-exporter-textfile-collector-scripts

or

https://github.com/Sheridan/smartctl_exporter (looks rarely maintained)

With node-problem-detector:

Hack together scripts to return error codes on my conditions using smartctl and/or nvme-cli
https://github.com/deliveryhero/helm-charts/blob/master/stable/node-problem-detector/values.yaml

With scrutiny:

https://github.com/AnalogJ/scrutiny (rough edges)

I am happy with this method https://github.com/onedr0p/home-cluster/commit/a593b4c8174a2e9c5a38b62dfc68866fcbdd358a


Changes to README.md

Edits first paragraph  for concision and clarity.
Rearranged the first sentence to make it more concise for readers.
Split the second sentence into two sentences to separate the two features explained. The first new sentence explains the first feature of the old second sentence and emphasizes how Carlo does the communicating to the reader. The second new sentence explains the second feature of the old second sentence.
Fixes #41

I signed it.


When you resize the window vertically until the "textbox" area is just not visible and resize back to normal, it can "reset" the console's text (look at image)

Environment
Microsoft Windows [Version 10.0.18362.175]

Steps to reproduce
What you do is rapidly resize the height of the terminal's window until the textbox bit of the console disappears (basically so the only thing visible is the top window bar)
Expected behavior
Normally what should happen is the text shouldn't change at all and should stay the same before resizing.
Actual behavior
The text keeps "repasting" over and over again. I presume it's to do with the console's text buffer or something. when you resize the window, the text changing at the very top is noticed and the console thinks someone typed something in and because nothing was typed in it's registered as the enter key being clicked. This explains why it repeats D:\>.
Before resizing the height:

After resizing the height quite fast (about 10 times):

#1465


Refactor loadModule

Same refactor as https://github.com/kwonoj/hunspell-asm/pull/67 is required.

closed via https://github.com/kwonoj/cld3-asm/pull/16 .


operator/ingress: Fix godoc re DNS on Azure and GCP

Fix the godoc for EndpointPublishingStrategy to say that wildcard DNS management is supported on Azure and GCP in addition to AWS.

operator/v1/types_ingress.go: Update.
operator/v1/zz_generated.swagger_doc_generated.go: Regenerate.

Alternatively, we could simply say that it is supported on some platforms, and that the ingresscontroller's status field will show whether it is currently managed.
@ironcladlou

/lgtm

/approve

/approve


update type defs for transform

Update type definitions for transform
https://github.com/jeffbski/redux-logic/issues/124

Thanks @saurabhsood91 it landed in v2.0.1


Missing Code

the code for cleaning all the account's live events is missing

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

ID: e3a8e309-8b1d-f6ca-4a17-8fe3d6718f03
Version Independent ID: da172793-27f2-0c92-46e5-a3814c913492
Content: Stream live with Azure Media Services v3
Content Source: articles/media-services/latest/stream-live-tutorial-with-api.md
Service: media-services
GitHub Login: @Juliako
Microsoft Alias: juliako

Hi @bilalawwad Thank you for your feedback! We will review and provide an update as appropriate.

@bilalawwad, Thanks for bringing this to our attention. Your feedback has been shared with the content owner (@Juliako) for further review on the code/doc section.

In the interim, kindly take a look at this sample .

removed the code place holder

#please-close


"Next Video" Command?

Is there a way to move to another video without stopping/restarting the screensaver? E.g. a shortcut?

When the screeen saver is running ? If you are not running Catalina/Big Sur, right Arrow key. On those though, I can no longer intercept key presses for the time being, so in that case, nope.


Dev footer feature flag formatting

Purpose
Better formatting for the feature flags tab in the dev mode footer modal:

Summary of Changes

arrange feature flags in columns
underscore and sort feature flag names
rename home page version B feature flag so it cleanly converts back to snake_case

Side Effects
none
Feature Flags
It lets you toggle all of them!
QA Notes
n/a
Ticket
n/a
Reviewer Checklist

[ ] meets requirements
[ ] easy to understand
[ ] DRY
[ ] testable and includes test(s)
[ ] changes described in CHANGELOG.md

Pull Request Test Coverage Report for Build 2856

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 71.439%

Totals

Change from base Build 2854:
0.0%

Covered Lines:
5997

Relevant Lines:
7539

💛  - Coveralls


Missing documentation for getElement()

In the migration guide, it is mentioned to replace getNode() with getElement() when using shallow(). However, the API is missing any getElement() documentation.

Hey @ljharb, I would love to take it. But before I start a couple of questions:

Should I also add getElements that exist but not mentioned in docs?
Should I remove getNode and getNodes from shallow docs?

Hey @ljharb, I would love to take it. But before I start a couple of questions:

Should I also add getElements that exist but not mentioned in docs?
Should I remove getNode and getNodes from shallow docs?

Anything you see that needs correcting, please do send a PR for :-)

Closed in #1425


On-Screen Keyboard Blocks Page Behind

When the on-screen keyboard is open, it's not possible to interact with any elements on the page (except for the on-screen keyboard).

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

ID: afdf6b9f-3d73-a1f2-4b57-684c07cacdab
Version Independent ID: d9f4a048-6942-e360-933c-e4d11f4b56bb
Content: Release Notes for Raspberry Pi 3B+ - Windows IoT
Content Source: windows-iotcore/release-notes/Insider/RPi3BP.md
Product: windows-iot
GitHub Login: @zeeshanfurqan
Microsoft Alias: zeeshan.furqan

Hi @scout208 - we're still investigating this.

Hi @scout208 - sorry for the delay in my response. The reason for this is that we may need to release another build to fix this issue. There is still discussion internally.

@saraclay No worries. For me, this is the only thing that is keeping from using the 3B+ for all intents and purposes. If we could just get an update on the consensus whenever it is reached internally that would be much appreciated! Thank you 👍

Hi @scout208 - thank you for being patient. The team was wondering if you're getting the latest Insider flights? In particular, the latest insider flight 17733 should have the OSK fix. Please let us know.

@saraclay I'm trying it now. I will update when I have finished testing it. I thought that the latest insider flight 17733 was only for all other boards while there was a specific separate release for Raspberry Pi 3B+. Is this not correct?

This is true, but the OSK issue has been resolved in 17733. The release for the Raspberry Pi 3B+ is a technical preview. At this time, we recommend using the 3B or other devices with supported Intel, Qualcomm, or NXP SoCs. Do let us know if this update works for you, though.

Okay, I think there is some confusion. I'm not having any problems with the OSK on the latest release of IoT Core for Raspberry Pi 3B. The issue I'm having with the OSK is on the technical preview. The reason I submitted this issue was to let you guys know that there is a problem with the OSK on the technical preview for 3B+ so you can know about that before you make the release.

Absolutely. We have definitely noted this - though if you need a fast turnaround, we do recommend the 3B until another 3B+ technical release is on its way. Closing this out for now, but feel free to re-open if anything else comes up.


[FEATURE REQUEST] - Quick plea to get the new /leave functionality in

I'm always frustrated when I have to manually change the character name every time I want to switch characters to get full trade functionality.
Instead of /kick {character_name} we now have /leave, which is much more general implementation.
It would be much nicer to have this as the "party leave" command than the self-kick method.

I think we must consider multiplayer team, so probably keep useing /kick

Won't be fixed since that only works when you want to leave and MT can't possibly know if you joined a team or you did invite someone


Test examples in the documentation

Inoperable example code really undermines adoption, as seen most recently in #520.
In the short term we should go through the docs and fix these one by one, but it might be an idea to write regression tests for them.
Gold plating would be to embed jsbin / jsfiddle live examples that could be demo'd in situ.

Yeah this is in the todo list. Contributions welcome.

I've got a major release in the middle of the week so I'm going to stick to my usual role of whining until the tail end ;)
Thinking deeper about this, a sustainable choice would be to have all the example snippets as distinct JS files. This would make testing easier, and could allow some clever scripting to integrate with the jsFiddle API to ensure all code is perpetuated. This would make it super easy for beginners and old hands to fork examples to suit others' needs etc. One for the backburner.

Closing this and #500 in favor of #526, which is more descriptive of the task at hand


Alpha Slider Inverted?

Hi,
This is super minor, but the Alpha slider is seemingly inverted?
In WeakAuras, when selecting 100 Alpha, the bar is transparent and 0 means it is fully opaque.

You can see this here, if you look at the WeakAura display, the color swatch is transparent, despite 100 Alpha.

upvote. just noticed the same thing. thought I was going crazy... alpha slider is indeed reverted.

Retail or Classic?

Retail is what I have tested it on.

Same here, retail.

This update has corrected it, however, clicking on the colours in the colour palette will automatically set the alpha to zero.

https://github.com/Jaslm/ColorPickerPlus/issues/16#issuecomment-1905499572


What is the difference between source_routing and router firmware?

I understand the difference between coordinator and router, but what is the difference between the source_routing firmware and router firmware?

Source_routing firmware: https://github.com/Koenkk/Z-Stack-firmware/tree/master/coordinator/Z-Stack_Home_1.2/bin/source_routing
Router firmware: https://github.com/Koenkk/Z-Stack-firmware/tree/master/router/CC2531/bin

Aren´t they both router firmware for the same devices? If so why are they in different folders?

The source routing firmware is a coordinator firmware, not a router firmware.
So comparing these makes no sense, instead you can compare the source routing vs the default firmware.
The difference between them is explained here https://github.com/Koenkk/Z-Stack-firmware/tree/master/coordinator#im-a-zigbee2mqtt-user-which-one-should-i-use and the overview above it.

Ok, I have read those instructions like a hundred times and I just got it now, source routing is also a coordinator firmware but design for networks with more devices. It didn't make sense to me before because I was assuming the router firmware had the same limit of 5 direct children as the source routing but now I understand it doesn't make sense that it has this limit of 5 direct children.
Thank you very much, you can close this incident.

@Koenkk  not clear for me, but who is playing the role of collector ? Is that the coordinator as well ?

@pipiche38 what do yo mean with "collector"?

in the reference

Source routing
In contrast to many-to-one routing that establishes routing paths from many devices to one data collector, source routing allows the collector to store and specify routes for many remotes. To use source routing on a network, many-to-one routes must first be established on the network from remote nodes to the central data collector.

Yes it is the coordinator


[5.0] Fix has() on self referencing relationship with table prefix

Fixes #8795
The relation shouldn't add a table prefix, this is taken care of in \Illuminate\Database\Grammar@wrapTable.
Since adding just a few integration test methods that use a connection with table prefix would be needlessly complicated, I decided to add a test class that extends the original integration test and runs the same checks with prefixed tables.

Looks good to me. :)

@lukasgeiter Please could you send a PR for this to 5.1. In it's current form, the tests fail.

Sure, will do.

Thank you. We were having trouble with it. :)

Done. I think the problem was that you added the relationship methods (childPosts and parentPost) to the wrong test model...

Oh, thank you. :)


Log incompatible tasks causing the configuration cache to be discarded

Fixes #20007

@bot-gradle test and merge

OK, I've already triggered a build for you.

Thanks for the feedback, @ljacomet! We don't have the bandwidth to do it right now but we'll get back to that in 2023, promise! 😃
I hope this smaller improvement can still save people some frustration in the near future.

@bot-gradle test and merge

OK, I've already triggered a build for you.


Add business data match Injection

Issue Description
Type:  feature request
Describe  what feature you want
   Chaosblade-exec-jvm already supports coarse-grained explosion radius control, such as Dubbo Group, Version, which is generally sufficient for single-application drills.
    At Qunar.com, we hope to be able to randomly drill all online businesses under this requirement. More precise explosion radius control is needed, for example, all the weakly dependent interfaces involved in a certain interface at the app entrance are drilled. These interfaces may be distributed across hundreds of applications at different levels downstream.
  1. How can we ensure that the injection of faults in hundreds of applications will not affect the business of other calling applications, which is the basis for the drill..
  2. How to do the same as automatic Stress Testing. When injecting faults, we can gradually increase the user impact from the smallest scale to the full scale.
   Based on this, we hope to achieve the above effects by matching fault injection with distributed link tracing or other transmitted business data. It is hoped that this solution does not rely on specific link tracking middleware, such as Hawk-eye and QTRACE (Qunar.com distributed link tracking).
  目前chaosblade-exec-jvm已经支持了粗粒度的爆炸半径控制，比如dubbo，group、version，这在单应用的演练中一般是够用的。
  在去哪网，我们希望可以做到对线上所有的业务可以随机演练，这个要求下。就需要更精准的爆炸半径控制，比如对app入口某个接口下的所有涉及到的弱依赖接口都进行演练。这些接口可能分布在下游不同层级的上百个应用中。
  1.我们怎么保障在为这上百个注入故障的同时，不影响其它调用应用的业务，是演练可以进行的基础。
  2.怎么做到像自动化压测式的自动加压一样。我们在注入故障的时候可以从最小规模的用户影响，逐渐增大到全量。
  基于此我们希望可以借助分布式链路追踪或其它方式传递的业务数据进行故障注入的匹配，来达到以上效果。并且希望此解决方案不依赖于具体的链路追踪中间件，如鹰眼、QTRACE（去哪网分布式链路追踪）。
Describe what you expected to happen?
  1. Obtain the business data passed in trace by Dubbo, HTTP and other RPC calling clients or  get data by implement the  for matching injection.
  通过在dubbo、http 等rpc调用客户端中获取trace中传递的业务数据或者通过spi实现业务数据获取，进行匹配注入。
  2. RPC calls support custom retrieval of business data through jsonPath from HTTP headers or map  returned in getAttachments of Dubbo Invocationd.
   rpc方式支持在dubbo  invocationd的getAttachments中返回的map或http header通过jsonpath定制化获取业务数据。
  3. Spi obtains business data by implementing the following interfaces
   spi 方式通过实现以下接口获取业务数据
public interface BusinessDataGetter {
String get(String key) throws Exception;
}
--b-parms='[{
	"key":"a1.b1.b1",
	"value":"a_value"，
            “mode”:"rpc"
},
{
	"key":"a2.b2.c2",
	"value":"b_value",
             “mode”:"spi"
}]’

http example：
blade create http throwCustomException --uri='https://www.baidu.com'
--b-parms='[{
	"key":"a1.b1.c1",
	"value":"a_value",
             “mode”:"rpc"
},
{
	"key":"a2.b2.c2",
	"value":"b_value",
             “mode”:"rpc"
}]’

Injection  Conditon Expressed By Java Codes:
   JSON.parseObject(header.get("a1")) .getString("b1.c1").equals(a_value)
  &&
  JSON.parseObject(header.get("a2")) .getString("b2.c2").equals(b_value)

dubbo example：
blade create dubbo throwCustomException --consumer --service=com.qunar.api --version=1.0.0  --b-parms='[{
	"key":"a",
	"value":"a_value",
             “mode”:"spi"
},
{
	"key":"b",
	"value":"b_value",
             “mode”:"spi"
}]’

Injection  Conditon Expressed By Java Codes:
   BusinessDataGetter.get("a").equals(a_value)
  &&
   BusinessDataGetter.get("b").equals(b_value)

#207


Will this be released for 10.14.4?

It looks very good! I was hoping to find a solution for my MBP Late 2008, which is still my number one machine currently used.

is this dead?

I'm waiting for update too, It works fine on 14.3 but not on 14.4.

just was. Enjoy

Great! Thanks a lot! By the way: Some parts of the UI are missing the highlighted color, like Messages App. It will just highlight the text but not the background of the selected list item. Don't know if this is fixable. Anyway, great effort! Imagine: Still using my Late 2008 MBP with Mojave as my main machine! How crazy is that! Sustainability becoming reality! Looking forward to 10.5 :)

Yes pretty crazy.  I find the older machines more reliable than the new ones.  Anyway, we're actively working the whole .5b+ and 10.15 compatibility issues.  I will look into an update once .5 becomes more stable.  NOTE: Apple apps are starting to use different UI frameworks so unfortunately these fixes aren't comprehensive, but I'll take another stab at it.