feat: conan 2.x recipe

This cannot be used to create a pr on conan-center until after the next release (10.0.34) as it relies on this release's tarball to function, which is not yet in place.
Code change checklist

[x] I have ensured that all methods and functions are fully documented using doxygen style comments.
[x] My code follows the coding style guide.
[ ] I tested that my change works before raising the PR.
[x] I have ensured that I did not break any existing API calls.
[x] I have not built my pull request using AI, a static analysis tool or similar without any human oversight.

@MikeRavenelle i would appreciate some feedback on this one if you have time please!

Looking good, just a few possible ideas for improvements or simplifications.

Thanks, I've made these changes!
When it comes to preparing this for a PR on conan center, how do i go about this? Is there a page on the docs saying how to submit a new package to conan center as i must have missed it.

The main docs are in https://github.com/conan-io/conan-center-index/blob/master/docs/adding_packages/README.md
We are just in the process to moving to a Conan 2-only pipeline, a matter of a couple of weeks. Probably you might want to wait until this happens before submitting it.
I'd say that the recipe is quite good, it shouldn't be very difficult to add it, just some minor things ,like using a conandata.yml with the data, probably removing the export capture of the scm commit.

Also after completing a build of D++ through conan i get the following deprecation warnings about several of the dependencies, is this something to be concerned about, if the dependencies never updated to Conan 2.x and you're deprecating Conan 1.x soon won't this break all D++'s dependencies via Conan?
dpp/10.0.33: Package '70ff0fab11b405566a3aa83746595e4f42384a03' created
dpp/10.0.33: Full package reference: dpp/10.0.33#ceb89c69974c5d471818a4f592cfe2c5:70ff0fab11b405566a3aa83746595e4f42384a03#13a094550d605b980d4c81686fa3496e
dpp/10.0.33: Package folder /home/brain/.conan2/p/b/dpp1c4bd0de58a7b/p
WARN: deprecated: Usage of deprecated Conan 1.X features that will be removed in Conan 2.X:
WARN: deprecated:     'cpp_info.names' used in: opus/1.4, openssl/3.1.2, zlib/1.3
WARN: deprecated:     'cpp_info.build_modules' used in: openssl/3.1.2
WARN: deprecated:     'env_info' used in: openssl/3.1.2

Also after completing a build of D++ through conan i get the following deprecation warnings about several of the dependencies, is this something to be concerned about, if the dependencies never updated to Conan 2.x and you're deprecating Conan 1.x soon won't this break all D++'s dependencies via Conan?

Don't worry too much. We will make sure to remove the legacy parts in ConanCenter recipes before completely deprecating them in the Conan client (that would raise an error). Hopefully this happens relatively fast after we move to the Conan 2-only pipeline, but it is true that there is also no intent to be aggressive about this, because the backlog there is very large, no need to overwhelm the system and reviewers with "stylistic/deprecation" only changes.

@memsharded having difficulty getting this to work on Conan center. everything I've done seems to conflict with what they are saying there e.g. must still support Conan 1.x? and ancient cmake from before 2019 seems to be a thing on their ci!
https://github.com/conan-io/conan-center-index/pull/25745
I would appreciate some input if you have time please
also is Conan center different from Conan itself with different policies???

@memsharded having difficulty getting this to work on Conan center. everything I've done seems to conflict with what they are saying there e.g. must still support Conan 1.x? and ancient cmake from before 2019 seems to be a thing on their ci!

Regarding the CMake version - when Conan 2 was designed, it was done in consultation with industry experts - and Conan 2 itself aims to be compatible (where possible, for the broadest compatibility) with CMake 3.15
https://github.com/conan-io/tribe/blob/main/design/004-tools-cmake.md
Please bear in mind that Conan Center has thousands of users, and what is "an ancient CMake from 2019" for some users, may actually be the version of CMake that users in enterprise environments are actually using - and we aim to support those as well. That's why the default in Conan Center CI is 3.15 in at least one of the platforms, so that we can also ensure broad compatibility with the recipes. It does not mean that all recipes need to be compatible with 3.15 - the recipes can express a requirement on a higher CMake version for this, as @memsharded  mentions above.

@memsharded having difficulty getting this to work on Conan center. everything I've done seems to conflict with what they are saying there e.g. must still support Conan 1.x? and ancient cmake from before 2019 seems to be a thing on their ci!

Regarding the CMake version - when Conan 2 was designed, it was done in consultation with industry experts - and Conan 2 itself aims to be compatible (where possible, for the broadest compatibility) with CMake 3.15<EMAIL_ADDRESS>Please bear in mind that Conan Center has thousands of users, and what is "an ancient CMake from 2019" for some users, may actually be the version of CMake that users in enterprise environments are actually using - and we aim to support those as well. That's why the default in Conan Center CI is 3.15 in at least one of the platforms, so that we can also ensure broad compatibility with the recipes. It does not mean that all recipes need to be compatible with 3.15 - the recipes can express a requirement on a higher CMake version for this, as @memsharded mentions above.

we simply cannot support 3.15 in dpp. we make extensive use of 3.16 features in our makefiles, and do not support any compilers/toolchains with a cmake this old. Our oldest supported compiler is gcc 8 and msvc 2019, msvc 2019 comes with cmake 3.36 (iirc).
If supporting 3.15 is a requirement, we would simply not list on conan until this version is incremented, this library is not intended to run on systems that old.

we simply cannot support 3.15 in dpp. we make extensive use of 3.16 features in our makefiles, and do not support any compilers/toolchains with a cmake this old. Our oldest supported compiler is gcc 8 and msvc 2019, msvc 2019 comes with cmake 3.36 (iirc).

No, but you don't have to! That is a requirement by Conan client, and a default base version for ConanCenter, but not mandatory at all.
You can very easily request and use any CMake version in ConanCenter, and you can do it with a simple tool_requires = "cmake/[>=3.27 <4]" in your recipe (or the minimum version you need). You don't even need to stick to 3.16, you can request any higher version and use in your CMakeLists.txt the newer CMake features you want.
So please, just add to your conanfile.py that tool_requires = "cmake/.... Thanks for the feedback!


Cassava model does not run when simulation and planting dates are from different years

Cassava model does not run with start of simulation and planting dates are from different years and there is a file T. If the file T is removed, the model runs without any issues.  Reported by Diego Magalhães<EMAIL_ADDRESS>

Solved here 3e82436
@chporter I have not tested for the other CROPSIM models but it is possible they can have the same issue (at least CSCAS).


[GOBBLIN-763] Support fields removal for compaction dedup key schema

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Gobblin JIRA issues and references them in the PR title.

https://issues.apache.org/jira/browse/GOBBLIN-763

Description

[x] Here are some details about my PR:
Remove fields, specified by configuration compaction.job.key.fieldBlacklist, while computing compaction dedup key schema
Fix incorrect AvroUtils.removeUncomparableFields implementation, which only keeps the first field of any schema, dropping all other fields which have the same schema.

Tests

[x] My PR adds the following unit tests:
CompactionJobConfiguratorTest.testKeyFieldBlacklist

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

@yukuai518 @autumnust  Please review.

+1 LGTM


Cannot specify JoinGroupRequest protocol priority

Versions
Present on every version that supports JoinGroupRequest
Problem Description
The kafka protocol for JoinGroupRequest allows you to specify priority on group protocols for seamless rollout of new protocols while a consumer group is running. This is done by changing the ordering on the wire for the GroupProtocols. See here for more details
Sarama exposes this field as a map, making it impossible to specify an ordering.

Note that the join group request allows for multiple protocol/metadata pairs. This enables rolling upgrades without downtime. The coordinator chooses a single protocol which all members support.

This is what is in the wiki; I don't read that as implying that order is important. The coordinator should only choose a protocol once all of the group members support it, regardless of order?

Later in the wiki:

Once all members have upgraded, the coordinator will choose whichever protocol is listed first in the GroupProtocols array.

If you're switching from "protov1" to "protov2", you want to deploy your binaries such that they can handle both in the switchover, but once every consumer has been updated, you want to ensure that "protov2" is chosen. The protocol ordering allows for doing this.

Oh yes you're right I'm sorry I must have missed that the first read through.
Fixing this without breaking API compatibility will be a bit awkward but should be possible.


Make the golden tests consistent

I know we said we should pause, but I think it's worth to merge this before you start on the update.
This makes the golden tests produce consistent output. I tested it by running the update goldens workflow three times in a row.
The main change is using clock everywhere and setting the clock during the tests to binding.clock, which is a consistent clock. I was surprised to see that the flutter test framework doesn't do this by default.

This is awesome! We could even set tolerance to 0.0, but let's keep it to allow local runs on different systems, and allow small differences in goldens between patches.


eosio.token: OR params?

Let's say I want to track all transfers TO contract1 and all transfers FROM contract2.
How do we capture this with our params schema @DenisCarriere ?

@YaroShkvorets we can't at the moment
We would need to rethink how we handle params for eosio.token substreams
I'm thinking we need to be able to support ExtendedAsset and ExtendedSymbol
"?from=1.0000<EMAIL_ADDRESS>USDT@tethertether"
We might come up with another solution for params


Update RunnableWithMessageHistory

This PR updates RunnableWithMessage history to support user specific configuration for the factory.
It extends support to passing multiple named arguments into the factory if the
factory takes more than a single argument.

Linter +10 Eugene +1


Provide a separate NuGet package for REST APIs

Right now it is not trivia to call REST APIs of SignalR Service.
It might worth providing a separate NuGet package to make it easier.

We now have Management API


Send a history of NAT type changes to the proxy

Currently, we send only the initially detected NAT type and log all the NAT type changes on the client side only. For this we store NatInfo struct (containing both TCP and UDP NAT types) on the client side and compare it against the NatInfo that comes from p2p. The comparison involves a custom implementation of PartialEq that does not account for the extra info (such as EDM-Random port numbers). If the stored NatInfo is different from the one that we get from p2p, we print out the 'changed NAT type' log.
Once the NAT type change happens, instead of just logging it, also send an RPC to the proxy that should indicate the new detected NAT type (for both TCP and UDP).
On the proxy side log the NAT type changes for each client as (peer_id, udp_nat_type, tcp_nat_type)

Tested & implemented successfully


A cross-platform future?

Thank you very much in this project.
It is promising and fulfills several of my wishes (elegant, modern, header-only,...). Unfortunately an essential requirement for me is that it should be cross-platform (Unix/Linux, Microsoft Windows, macOS,...) Do you consider introducing such a feature in the future  (if it is feasible to do so)?
Again, thank you very much for this contribution! :-)
DJuego

Thanks for the feedback! I do have Windows support planned as a possibility and should be able to add that and test it locally in the near future. I don't have the means to develop/test on macOS, though I'd expect the code to generally build and run there.

Initial Windows support has now been added. I still need to setup Travis-CI, which may enable me to build/test for macOS.

Closing this for now as I've now tested the Windows support locally against Linux and have verified that the code builds and unit tests pass on macOS. Github actions now do Windows and macOS builds.


Remove arrows from trigger text

Arrows in trigger text become "then" (e.g. stack => out) when converted to tts.  Therefore, you shouldn't use arrows in trigger text for things like "tankbuster => target", because it will become "tankbuster then target" in tts.
@MaikoTan mentions a few things here for sleep/stun/interrupt and a few extra Korean lines: https://github.com/quisquous/cactbot/pull/1745#issuecomment-685186522
It looks like there needs to be French, Japanese, and Korean fixes.  Can I ping @VanSlanzar , @MaikoTan, and @Jaehyuk-Lee for this? Feel free to comment here about what the lines should be and I can put together a pull request (or send a pull request yourself, if that's easier).

Yes. I think in Japanese lines, they should be...
// sleep
ja: source + ' にスリプル',
// stun
ja: source + ' にスタン',
// interrupt
ja: source + ' に沈黙',

I think making new PR is better, but I'm busy this week with raid static. So... maybe next week? Or someone else can fix it.

There is one more similar problem that someone suggested to me.
https://github.com/quisquous/cactbot/blob/37ae15b684cb98d17013cf980cd4586653f82dca/ui/raidboss/data/03-hw/raid/a8s.js#L73-L77
https://github.com/quisquous/cactbot/blob/37ae15b684cb98d17013cf980cd4586653f82dca/ui/raidboss/data/03-hw/raid/a8s.js#L89-L93


CSS issue: skeleton-shine unsupported background-position property on PageSpeed

The problem occurs when we test the page speed on https://pagespeed.web.dev/
I think it causes a bug because of the conflict between using background-position in animation.

Fix with https://github.com/viivue/atomic-css/releases/tag/v1.1.8


Newbie questions on using pREST

pREST version (or commit ref): 4.0
pREST endpoint:
PostgreSQL version: 9.6.6
Operating system: Windows 10 (client machine where I have pREST binary)
Go version: none
Log gist:

Description
I posted this same question on Postman forum but maybe I should have posted it here instead ...
If I’m understanding it correctly, pREST would allow me to work-around Postman’s limitation of not being to directly query a database.
(1) Is my assumption correct that I can install pRest on a Windows client machine and configure it to connect to our PostgreSQL server?
(2) If (1) is correct, is my idea correct that I just need to have 2 files on my working directory - prest-windows-4.0-amd64.exe and prest.toml with my toml file containing the following:
[pg]
host = “<IP_ADDRESS>” => replace with PostgresSQL server hostname
user = “postgres” => we’re using this so retain this
pass = “mypass” => replace with postgres password
port = 5432 => retain this
database = “prest” => replace with the database that I’m trying to connect to???
Thanks in advance!!!
PS. I was supposed to post this question on the gitter link provided but I got a 404.

@annedemata correct, pREST opens an interface of your PostgreSQL bank as REST API, yes it runs on Microsoft Windows.

yeap

Thank you so much for the confirmation, @avelino!
So I updated my prest.toml accordingly and I also added PREST_DEBUG=true at the top of the file to disable JWT but I'm getting a 401 Unauthorized. I just tried running http://<IP_ADDRESS>:6000/databases and http://<IP_ADDRESS>:6000/tables.
The details under [pg] section on prest.toml are the same ones that I'm using successfully on pgAdmin so I'm sure that my connection details are correct. Anything else that I can check?
If I should create a new thread or if I should post my questions somewhere else, feel free to let me know.
Thanks again!

Hi @annedemata
sorry the docs is a bit outdated.
please add  jwt dafault to false
[jwt]
 default = false

Let me know if you have more doubts.

Yeeeeeeeeeeyyyyyy, that works!
Thank you, thank you @felipeweb!
If I can contribute to updating any of the documentations, just let me know (I tried clicking "Edit this page on https://postgres.rest/configurations/ but I got a 404). I'm a tester, though and not a developer so my perspective will be more of a regular user : ).


Unable to install URO

I used pip command but not installed.
It shows :
Requirement already satisfied: uro in ./.local/lib/python3.11/site-packages (1.0.0)

cd  ./.local/lib/python3.11/site-packages
Delete two related files or folders uro
now start install again by pip : (dont install by pip3 )
pip install uro --user
now work (👍 :
uro -h


Crashes when no log

Exception thrown: 'System.IO.DirectoryNotFoundException' in System.Private.CoreLib.dll
Line 48: File.AppendAllText($"Logs/{DateTime.Now.ToShortDateString().Replace("/", "-")}.log", finalMessage + "\n");
Exception has occurred: CLR/System.IO.DirectoryNotFoundException
An exception of type 'System.IO.DirectoryNotFoundException' occurred in System.Private.CoreLib.dll but was not handled in user code: 'Could not find a part of the path '/home/xproot/WinBot/WorkingDirectory/Logs/2-2-2022.log'.'
   at Interop.ThrowExceptionForIoErrno(ErrorInfo errorInfo, String path, Boolean isDirectory, Func`2 errorRewriter)
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String path, OpenFlags flags, Int32 mode)
   at System.IO.FileStream.OpenHandle(FileMode mode, FileShare share, FileOptions options)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
   at System.IO.StreamWriter.ValidateArgsAndOpenPath(String path, Boolean append, Encoding encoding, Int32 bufferSize)
   at System.IO.StreamWriter..ctor(String path, Boolean append)
   at System.IO.File.AppendAllText(String path, String contents)
   at WinBot.Util.DiscordSink.Emit(LogEvent logEvent) in [/home/xproot/WinBot/Source/Util/DiscordSink.cs]():line 48
   at Serilog.Core.Sinks.SafeAggregateSink.Emit(LogEvent logEvent)

idk im just guessing

"System.IO.DirectoryNotFoundException"
Did you delete the logs folder?

h closing because h


Subscription operationName not sent

When having multiple named subscriptions and sending one of them, the operationName is not sent with the query string.

The error message is not shown correctly (see #604). Looking at the console, the operationName is not sent via websocket connection:

Therefore, the subscription errors with "Must provide operation name if query contains multiple operations."

Is there any update on this?

@andrew-w-ross new maintainer team here! thanks for the solid bug report. I will get set up to work on this.

@acao Did you have any luck looking at this?

@benjie i was able to reproduce this i thought? i feel like maybe we fixed it and this was a dupe. let me check

resolved by #664

resolved by #664


Dependency injection does not work with es2015 target

Bug, feature request, or proposal:
Bug
What is the expected behavior?
mat-sidenav should Initialize without error
What is the current behavior?
Using target: es5 everything works normal (using --prod --aot --build-optimizer and in dev mode)
When target is set to es2015 error is thrown:
Cannot read property 'create' of undefined
    at MatSidenav.ngAfterContentInit (sidenav.js:268)
    at callProviderLifecycles (core.js:10333)
    at callElementProvidersLifecycles (core.js:10310)
    at callLifecycleHooksChildrenFirst (core.js:10294)
    at checkAndUpdateView (core.js:11422)
    at callViewAction (core.js:11769)
    at execComponentViewsAction (core.js:11701)
    at checkAndUpdateView (core.js:11425)
    at callWithDebugContext (core.js:12592)
    at Object.debugCheckAndUpdateView [as checkAndUpdateView] (core.js:12182)

What are the steps to reproduce?
<mat-sidenav-container class="view"  fxLayout="column" >
        <mat-sidenav  #leftsidenav (opened)="onLeftOpened($event)"
           (closed)="onLeftClosed($event)" class="left"  position="start"  mode="over">
             <ui-view name="left"></ui-view>
        </mat-sidenav>
</mat-sidenav-container>

What is the use-case or motivation for changing an existing behavior?
To work using target: es2015
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular CLI: 1.5.0
Node: 8.7.0
OS: linux x64
Angular: 5.0.0
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cdk: 5.0.0-rc0
@angular/cli: 1.5.0
@angular/flex-layout: 2.0.0-beta.10-4905443
@angular/material: 5.0.0-rc0
@angular-devkit/build-optimizer: 0.0.32
@angular-devkit/core: 0.0.20
@angular-devkit/schematics: 0.0.35
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.8.0
@schematics/angular: 0.1.1
typescript: 2.4.2
webpack-bundle-analyzer: 2.9.0
webpack: 3.8.1

Is there anything else we should know?
no

@kdomagoj - Did this work at one point or is this a regression? I'd generally advise against using ES2015 compiler target until full browser support has landed and those versions have been adopted widely.
@mmalerba - Looks like the focusTrapFactory isn't getting initialized. https://github.com/angular/material2/blob/master/src/lib/sidenav/drawer.ts#L288

@amcdnl
I intend to use es2015 build for cordova(android) app which support es2015 and for desktops I will build with es5 target.
I was waiting for that feature to be available , and since 1.5 CLI it is.
So  after angular 5.0.0 + 1.5 cli upgrade I gave  a try with es2015 target.
Everything works fine when builded with target es5.
This is first time I experience this issue.
Thanks.

It looks like everything that gets injected via DI is undefined, sidenav was just the first thing to throw an error because of it. Will update issue title to reflect the real issue

My initial hunch would be that this is something in ngc

Same error with es2015 and es2016

I tried to reproduce that issue with the latest Angular CLI version, but unfortunately I wasn't able to serve the app with the build-optimizer at all.

https://github.com/angular/angular-cli/issues/8505

There seem to be a lot of issues related to the build-optimizer and the ES2015 target right now. My initial guess was that the build-optimizer removes some important metadata from the ES2015 files, which then causes the Dependency Injection failures.
I will try to manually work-around  https://github.com/angular/angular-cli/issues/8505 to be able to reproduce the issue. In meanwhile it would be helpful if someone runs the CLI with --build-optimizer=false.

The issue of the Angular CLI has been resolved with<EMAIL_ADDRESS>I manually installed<EMAIL_ADDRESS>and everything works fine with the ES2015 TypeScript target now.

I'm closing this issue because it looks like the issue has been resolved with the latest UglifyJS version.
Please let us know if you still that issue with the latest UglifyJS version.

Can confirm issue is resolved!
Thanks @DevVersion
15% smaller main.bundle
10% shorter app load time (to first app state)
with es2015 on Cordova Crosswalk 23 Android

This does not appear to fully resolved yet. Using an empty material table:
    at new CdkTable (table.js:438)
    at new MatTable (table.js:26)
    at createClass (core.js:10379)
    at createDirectiveInstance (core.js:10226)
    at createViewNodes (core.js:11686)
    at callViewAction (core.js:12120)
    at execComponentViewsAction (core.js:12029)
    at createViewNodes (core.js:11714)
    at createRootView (core.js:11575)
    at callWithDebugContext (core.js:12941)```

with angular cli 1.6.1, target es2015<EMAIL_ADDRESS>

Still having this issue with MatSidenav
Angular CLI 1.6.2<EMAIL_ADDRESS>Changing target ES actually does not matter at all. Tried all between ES2015, ES2016, ES2017, ESNext
ERROR TypeError: Cannot read property 'isBrowser' of undefined     at MatSidenav.ngAfterContentChecked (sidenav.js:315)     at callProviderLifecycles (core.js:10646)     at callElementProvidersLifecycles (core.js:10617)     at callLifecycleHooksChildrenFirst (core.js:10600)     at checkAndUpdateView (core.js:11750)     at callViewAction (core.js:12097)     at execComponentViewsAction (core.js:12029)     at checkAndUpdateView (core.js:11752)     at callViewAction (core.js:12097)     at execComponentViewsAction (core.js:12029)

Same.
@DevVersion Please reopen this issue, or help point us in the right direction. ❤
Angular 5.1.2, Angular CLI 1.6.2, Angular Material 5.0.2, Karma 2.0.0, uglify-es 3.3.2.
Works
"target": "es5" // tsconfig.json

Fails
"target": "es2015" // tsconfig.json

import { TestBed, async } from '@angular/core/testing';
import { MatSidenavModule } from '@angular/material';

import { AppComponent } from './app.component';

describe('AppComponent', () => {
  beforeEach(async(() => {
    TestBed.configureTestingModule({
      declarations: [
        AppComponent
      ],
      imports: [ MatSidenavModule ]
    }).compileComponents();
  }));

  it('should render title in a h1 tag', async(() => {
    const fixture = TestBed.createComponent(AppComponent);
    fixture.detectChanges();
    const compiled = fixture.debugElement.nativeElement;
    expect(compiled.querySelector('h1').textContent).toContain('Welcome to app!');
  }));
});

% ng test

[karma]: Karma v2.0.0 server started at http://<IP_ADDRESS>:9876/

Chrome 63.0.3239 (Mac OS X 10.12.6): Executed 1 of 1 (1 FAILED) (1.521 secs / 1.303 secs)
TOTAL: 1 FAILED

1) should render title in a link tag
     AppComponent
     Failed: Cannot read property 'create' of undefined
TypeError: Cannot read property 'create' of undefined
    at MatSidenav.ngAfterContentInit Users/bdover/code/workshop/rethink-reading/node_modules/@angular/material/esm2015/sidenav.js:304:1)
    at callProviderLifecycles Users/bdover/code/workshop/rethink-reading/node_modules/@angular/core/esm2015/core.js:10643:1)
    at callElementProvidersLifecycles Users/bdover/code/workshop/rethink-reading/node_modules/@angular/core/esm2015/core.js:10617:1)
    at callLifecycleHooksChildrenFirst Users/bdover/code/workshop/rethink-reading/node_modules/@angular/core/esm2015/core.js:10600:1)
    at checkAndUpdateView Users/bdover/code/workshop/rethink-reading/node_modules/@angular/core/esm2015/core.js:11750:1)
    at callViewAction Users/bdover/code/workshop/rethink-reading/node_modules/@angular/core/esm2015/core.js:12097:1)
    at execComponentViewsAction Users/bdover/code/workshop/rethink-reading/node_modules/@angular/core/esm2015/core.js:12029:1)
    at checkAndUpdateView Users/bdover/code/workshop/rethink-reading/node_modules/@angular/core/esm2015/core.js:11752:1)
    at callWithDebugContext Users/bdover/code/workshop/rethink-reading/node_modules/@angular/core/esm2015/core.js:12941:28)
    at Object.debugCheckAndUpdateView [as checkAndUpdateView] Users/bdover/code/workshop/rethink-reading/node_modules/@angular/core/esm2015/core.js:12531:1)

I just looked into this issue again.
As I mentioned previously, the issue with the ES2015 mode when serving the application in combination with the build-optimizer in AOT mode has been fixed by the UglifyJS update.
For unit tests, the AOT mode is not supported, and the metadata files won't be read. This means that Angular runs in JIT mode and needs to figure out the ctorParameters and the inheritance itself. Unfortunately this is not supported and therefore the tests won't run in JIT ES2015 mode.
To summarize:

ES2015 with AOT : works
ES2015 with JIT : doesn't work (see https://github.com/angular/angular/issues/15127 and https://github.com/angular/angular-cli/issues/7797)

Closing this issue (again), because everything works as intended on our side.

@DevVersion I understand that tests do not run in JIT ES2015 mode. However, is it expected that ES2015 with JIT doesn't work at all, when serving or building the actual application?


fix: FluentTab not render automatically

🐛 Bug Report
When I updated to 4.3.0 from 4.2.1, my FluentTabs not render the new dynamic Tab automatically.
Version 4.2.1

Version 4.3.0

Version 4.3.0, only work for the first item of FluentSelect, it's very strange:

💻 Repro or Code Sample
<FluentTabs @bind-ActiveTabId="@SelectedTabId" Style="width:100%" Size="TabSize.Medium" @ref="fluentTabs">
    <CascadingValue Value="this" Name="KimiModeling">
        <FluentTab Label="Home" Icon="@(new Icons.Regular.Size24.Home())" Id="@homeTabId">
            <TablesGrid @ref="@tablesGrid" Tables="Tables" TableRecordCrudEvent="TableRecordCrudEvent" ReadOnly="@ReadOnly">
            </TablesGrid>
        </FluentTab>
        <FluentTab Label="TTT" Id="TTID">
            Empty
        </FluentTab>

        @if (TabItems?.Any() == true)
        {
            foreach (var item in TabItems)
            {
                var crudpage = item.GetCrudPageType();
                Dictionary<string, object?> parameters = new() { { nameof(BaseCrud<object>.AsDetailPage), ReadOnly } };
                <FluentTab<EMAIL_ADDRESS><EMAIL_ADDRESS>Data="@item" <EMAIL_ADDRESS>                    @if (crudpage != null)
                    {
                        <DynamicComponent Type="crudpage" Parameters="@item.GetCrudPageParameter(parameters)">
                        </DynamicComponent>
                    }
                </FluentTab>
            }
        }
    </CascadingValue>
</FluentTabs>

Inside FluentTabs host page to directly update the TabItems, it works fine. But if I try to use @ref to ref the FluentTabs host page, and call its same function, it won't work for not first item of FluentSelect (but after manul click the Tab title, it will works for the second call).
    public void AddAndSelect(KimiModdlingTabItem tabItem)
    {
        TabItems.Add(tabItem);
        SelectedTabId = tabItem.TabId;
        StateHasChanged();
    }

Try to force re-render, not work:
    public async Task ReFresh()
    {
        StateHasChanged();
        MethodInfo? method = fluentTabs?.GetType()?.GetMethod("StateHasChanged", BindingFlags.Instance | BindingFlags.NonPublic);
        method?.Invoke(fluentTabs, null);
    }

Why?

To use callback event to close the Tab, different behavior, it's very strange, the Tabs sometimes auto render, sometimes not, when I click "Close" button, to remove tab from tabs list, after any interaction on the page, it will not work for new version:

Hi,
Please stop creating issues without code we can run and steps that describe how to reproduces the effect you are seeing. We can't copy and run any of the code you are posting. We are not here to debug your software project.
The images you include may be clear to you but do not say anything to me and do not convey the issue at all.
Closing this (again) as we can not reproduce.
BTW, that ReFresh method is looking really weird. Not clear what you are trying to achieve there.

I noticed that after update to version 4.3.0, sometime not detect the component property value changed. And, my code version 4.2.1, the SetParametersAsync() always triggered when my FluentSelect selectedoption changed even there's no parameter change, but after version 4.3.0, the SetParametersAsync() not trigger again when selectedoption  changed.

A fix has been implemented in ListComponentBase in commit b7ad573e:
Commit b7ad573e5437c7a0384d12f08411286167229ce9
Author: La Minh Phuc<EMAIL_ADDRESS>Date: maandag 18 december 2023 10:27
Parent: 940efee1
ListComponentBase, maintain consistency between SelectedOption and Value when Multiple is false (#1149)
This commit ensures that SelectedOption and Value consistently reflect each other. When SelectedOption is updated, Value is adjusted to maintain coherence, and conversely, changes to Value are reflected in the corresponding adjustment of SelectedOption.
This fixes #983
Co-authored-by: La Minh Phuc<EMAIL_ADDRESS>Co-authored-by: Vincent Baaij<EMAIL_ADDRESS>You probably need to adjust your code to work with this.

Actually, we have observed the same (or at least similar) behavior since updating to version 4.3.0. Our code example is quite complex, I'm still trying to reduce it to something less complicated, but something definitely has changed in the way FluentTabs rerender.

Changes we made to FluentTab and FluentTabs from v4.2.1 to v4.3:

We added Visible property to FluentTab
We fixed #1194 for FluentTabs by determining if the components needs to re-renderor not <- Im guessing you are seeing a change because of this.

Because of what that last bullet fixes, I'm not expecting we are going to change anything back to the previous situation. This fix was, and is, needed.


Doesn't build on windows

Sorry for the lack of detail...  It looks like it's related to the definition of min and max.  It shows up several times but here's one them:
..........\src\spatialite\deps\geos\geos\src\geom\LineSegment.cpp(171): error C3861: 'max': identifier not found [D:\Projects\Android\SSEDock\node_modules\spatialite\build\src\spatialite\deps\geos\geos.vcxproj]
..........\src\spatialite\deps\geos\geos\src\geom\LineSegment.cpp(174): error C3861: 'max': identifier not found [D:\Projects\Android\SSEDock\node_modules\spatialite\build\src\spatialite\deps\geos\geos.vcxproj]
Someone actually has a branch that looks like it addresses these here: https://github.com/cartant/node-spatialite/commit/da190997294ab400a0817278b80c3e067639a087
but that one also does not build for different reasons related to gyp:
gyp: src\spatialite\deps\lwgeom\binding.gyp not found (cwd: ...\node_modules\spatialite) while loading dependencies of binding.gyp while trying to load binding.gyp

I am experiencing this same issue. I am using Windows 8.1, with VS 12 installed. My errors look like this:
..........\src\spatialite\deps\geos\geos\src\algorithm\LineIntersector.cpp(
80): error C3861: 'max': identifier not found [\node_modules\spatialite\build\src\spatialite\deps\geos\geos.vcxproj]

I managed to fix the build issues on Windows. You can find my fork here;
https://github.com/TesseractG/node-spatialite.git
Note that you also have to run git submodule update -i -r on the checked out repository, or you will be missing lwgeom, as mentioned in the last error by insominx.
node-gyp rebuild works on this repos (for me), but I still cannot get the package to run. If I build it locally, run npm install on it for the dependencies and drop it into my global node_modules, npm list shows it as "invalid" without any further information.
If I try to install it using npm install https://github.com/TesseractG/node-spatialite.git, it does NOT auto-download the lwgeom package and dies on that.
I am still trying to figure it out, but at least it is building...

What version of Windows + VS are you using? I would be interested to accept a PR that fixes Windows, but I don't use Windows and haven't had time to debug it. It's been long enough now that it's also probably time to upgrade all the dependencies.

I am on Windows 10 using Visual Studio 2015 - so latest versions of both.
The problem with issuing a PR is that I cannot guarantee these changes do not break builds on any other platforms...

I have all of it working now on Windows with VS 2015. I had to make some changes to lwgeom as well and I am pretty sure those changes will break compatibility with earlier versions of VS, since they concern fixing mistakes previously present in VS (like not defining NAN and INFINITE).
I can issue merge requests for both. lwgeom will continue to build on all *nix environments and will only build on Windows with VS2015. node-spatialite may or may not build on other environments; I do not know.
Please let me know how you would like to proceed.

I would say please submit a PR! I can test it on Mac and Linux. As far as I know, Windows doesn't work at all at the moment, so I don't think it could work any less ;)

Also, do you need lwgeom? I'm considering removing it to simplify the build process because it makes things significantly more complicated to build...

I am not sure if I need lwgeom, all I know is that the package does not compile/install without it. I am using it in a software package that was developed by someone else (who runs it on a Mac without any issues), so I am not sure if it is needed...
I will issue the merge requests on both projects now.

@TesseractG with your latest fork/PR does npm install https://github.com/TesseractG/node-spatialite.git auto download lwgeom for you? Or are you cloning, running git submodule update -i -r and then building to get it to work on windows?

I'm very close but Its not quite finishing the build. Here is the error
C:\Program Files (x86)\Windows Kits\10\Include\10.0.10150.0\ucrt\stdio.h(1927): fatal error C1189: #error:  Macro defin
ition of snprintf conflicts with Standard Library function declaration (compiling source file ..\..\..\..\..\src\spatia
lite\deps\lwgeom\lwgeom\lwgeom_geos_split.c) [C:\Users\zrussell1\Documents\Pinpoint\libs\node-spatialite\build\src\spat
ialite\deps\lwgeom\lwgeom.vcxproj]

I have this same error across most of the files in lwgeom

I get lwgeom using git submodule update - I am not sure if there is a way to do this automatically. Your NPM package (the one that downloads using npm install) has lwgeom in there, though. I assume you need to special build a release package including all external libraries?
As for the snprintf errors; those are the errors I fixed... If you ook at the changes I made to the config files for win32 and win64 in the commit, then you can see that I removed the superfluous define of snprintf. This error occurred for me too at first, but no longer...
I just did a search for snprintf on all source files I have of lwgeom and the macro no longer appears anywhere. Are you sure you are using my version?

Here is the exact process I'm going through:
git clone https://github.com/TesseractG/node-spatialite.git
...
cd node-spatialite
git submodule update -i -r
...
node-gyp configure build

I thought I found the issue. So I replaced the submodule to download your lwgeom fork however still the same snprintf errors.

I published 0.0.6, could you try that?
npm install<EMAIL_ADDRESS>

That worked great for me. Built with no issues on Windows 7 with VS 2015

Worked fine for me too! Windows 10 with VS 2015.
Whatever the issue with the lwgeom module was, it does not seem to affect me... I think this is good for building on Windows. Thanks for merging!

Great! Thanks for the PR @TesseractG and for testing it out!


Rewind IO cursor after failed image dimension extraction by FastImage

I made this PR in bit of haste so please review accordingly.
FastImage gem does not rewind IO cursor if the dimension extraction fails eg. due to providing a non-image file. Non rewinded IO causes S3 upload to fail with Aws::S3::Errors::BadDigest before file can be validated.

I just noticed the bit about image bombs in the readme. I don't really understand how FastImage protects from those so I guess swallowing all FastImageExceptions could break that protection. Perhaps we should only rescue UnknownImageType exceptions?

Thank you very much for the PR. Actually, rescuing all FastImageException is exactly what we want, because we don't want to react on any errors, since the type/extension validations are checking if the file is an image. As for image bombs, I think that Fastimage doesn't abort but still manages to extract dimensions in this case.
I think this is an important fix, but I think it would be much better if this was fixed in Fastimage itself, so I sent a PR there: https://github.com/sdsykes/fastimage/pull/66.

Yeah, I was also thinking that a more fitting place for the fix would be FastImage itself, but did not have time to dive into the source. Lets hope they'll accept the change! :)
PS. I most likely still need to resort to monkey patching since I've had to lock FastImage to v1.8.1 as my project has a dependency conflict (with Addressable gem) starting from FastImage v1.9.

Hmm, that's unfortunate. Sam Saffron opened a pull request for removing the Addressable dependency, but it's still waiting. Apparently the only reason why Addressable is used over the URI standard library is because there was some bug concerning underscores in URLs, which was fixed in Ruby 2.2. But that can surely be fixed somehow inside Fastimage, I mean, everyone uses URI standard library for parsing all the time.
But I don't want only people who update Fastimage to get this fixed in Shrine (when/if the PR eventually gets merged), so it's better to merge your fix.


how to use with sudo?

$ pip -V
pip 18.1 from /home/user/.asdf/installs/python/3.6.10/lib/python3.6/site-packages/pip (python 3.6)

$ pip install ps_mem
Collecting ps_mem
  Downloading https://files.pythonhosted.org/packages/46/81/ff8429735e2eb13be225dcfabef16d90bfa96b559e3f2643935d33b67697/ps_mem-3.12.tar.gz
Installing collected packages: ps-mem
  Running setup.py install for ps-mem ... done
Successfully installed ps-mem-3.12
You are using pip version 18.1, however version 20.2b1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.

$ ps_mem
-bash: ps_mem: command not found
$ asdf reshim

$ ps_mem
Sorry, root permission required, or specify pids with -p
$ sudo ps_mem
unknown command: ps_mem. Perhaps you have to reshim?
$ asdf exec ps_mem
Sorry, root permission required, or specify pids with -p
$ sudo asdf exec ps_mem
unknown command: ps_mem. Perhaps you have to reshim?

I don't think there is an easy way around this. You would need to install asdf as root, and install whatever command you want to use as root from within this asdf.


Failed to generate project model definition files for the project file

Im using Rider with one project in Unreal Engine 5 and i got two error you can see in the picture

Pressing show logs:
20:11:51.630: C:\Program Files\Epic Games\UE_5.4\Engine\Binaries\ThirdParty\DotNet\6.0.302\windows\dotnet.exe "C:\Program Files\Epic Games\UE_5.4\Engine\Binaries\DotNET\UnrealBuildTool\UnrealBuildTool.dll" -ProjectFiles -Rider -Automated -Minimize -Platforms=Win64 -TargetTypes=Editor -TargetConfigurations=Development "C:\Users\ruben\OneDrive\Documentos\Unreal Projects\ToonTanks\ToonTanks.uproject"
20:11:51.892: Log file: C:\Users\ruben\AppData\Local\UnrealBuildTool\Log_GPF.txt
20:11:52.018: Generating Rider project files:
20:11:52.211: Available x64 toolchains (1):
20:11:52.211:  * C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120
20:11:52.211:     (Family=14.41.34120, FamilyRank=5, Version=14.41.34123, Is64Bit=True, ReleaseChannel=Latest, Architecture=x64)
20:11:52.211: Visual Studio 2022 compiler version 14.41.34123 is not a preferred version. Please use the latest preferred version 14.38.33130
20:11:52.217: Available x64 toolchains (1):
20:11:52.217:  * C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120
20:11:52.217:     (Family=14.41.34120, FamilyRank=5, Version=14.41.34123, Is64Bit=True, ReleaseChannel=Latest, Architecture=x64)
20:11:52.217: Visual Studio 2022 compiler version 14.41.34123 is not a preferred version. Please use the latest preferred version 14.38.33130
20:11:52.219: Available x64 toolchains (1):
20:11:52.219:  * C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120
20:11:52.219:     (Family=14.41.34120, FamilyRank=5, Version=14.41.34123, Is64Bit=True, ReleaseChannel=Latest, Architecture=x64)
20:11:52.219: Visual Studio 2022 compiler version 14.41.34123 is not a preferred version. Please use the latest preferred version 14.38.33130
20:11:52.220: Available x64 toolchains (1):
20:11:52.220:  * C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120
20:11:52.220:     (Family=14.41.34120, FamilyRank=5, Version=14.41.34123, Is64Bit=True, ReleaseChannel=Latest, Architecture=x64)
20:11:52.220: Visual Studio 2022 compiler version 14.41.34123 is not a preferred version. Please use the latest preferred version 14.38.33130
20:11:52.227: Available x64 toolchains (1):
20:11:52.227:  * C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120
20:11:52.227:     (Family=14.41.34120, FamilyRank=5, Version=14.41.34123, Is64Bit=True, ReleaseChannel=Latest, Architecture=x64)
20:11:52.227: Visual Studio 2022 compiler version 14.41.34123 is not a preferred version. Please use the latest preferred version 14.38.33130
20:11:52.230: Available x64 toolchains (1):
20:11:52.230:  * C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120
20:11:52.230:     (Family=14.41.34120, FamilyRank=5, Version=14.41.34123, Is64Bit=True, ReleaseChannel=Latest, Architecture=x64)
20:11:52.230: Visual Studio 2022 compiler version 14.41.34123 is not a preferred version. Please use the latest preferred version 14.38.33130
20:11:52.248: Writing project files...
20:11:52.248: Available x64 toolchains (1):
20:11:52.248:  * C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120
20:11:52.248:     (Family=14.41.34120, FamilyRank=5, Version=14.41.34123, Is64Bit=True, ReleaseChannel=Latest, Architecture=x64)
20:11:52.248: Visual Studio 2022 compiler version 14.41.34123 is not a preferred version. Please use the latest preferred version 14.38.33130
20:11:52.251: Available x64 toolchains (1):
20:11:52.251:  * C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120
20:11:52.251:     (Family=14.41.34120, FamilyRank=5, Version=14.41.34123, Is64Bit=True, ReleaseChannel=Latest, Architecture=x64)
20:11:52.251: Visual Studio 2022 compiler version 14.41.34123 is not a preferred version. Please use the latest preferred version 14.38.33130
20:11:52.615: Exception while generating include data for Target:UnrealEditor, Platform: Win64, Configuration: Development
20:11:52.624: System.ArgumentNullException: Value cannot be null. (Parameter 'element')
20:11:52.624:    at System.Attribute.GetCustomAttributes(MemberInfo element, Type attributeType, Boolean inherit)
20:11:52.624:    at System.Reflection.CustomAttributeExtensions.GetCustomAttributes[T](MemberInfo element)
20:11:52.624:    at UnrealBuildTool.ModuleRules.IsValidForTarget(Type moduleType, ReadOnlyTargetRules targetRules, String& invalidReason) in D:\build++UE5\Sync\Engine\Saved\CsTools\Engine\Source\Programs\UnrealBuildTool\Configuration\ModuleRules.cs:line 1636
20:11:52.624:    at UnrealBuildTool.UEBuildTarget.AddAllValidModulesToTarget(ILogger Logger) in D:\build++UE5\Sync\Engine\Saved\CsTools\Engine\Source\Programs\UnrealBuildTool\Configuration\UEBuildTarget.cs:line 3938
20:11:52.624:    at UnrealBuildTool.UEBuildTarget.PreBuildSetup(ILogger Logger) in D:\build++UE5\Sync\Engine\Saved\CsTools\Engine\Source\Programs\UnrealBuildTool\Configuration\UEBuildTarget.cs:line 3403
20:11:52.625:    at UnrealBuildTool.UEBuildTarget.Create(TargetDescriptor Descriptor, Boolean bSkipRulesCompile, Boolean bForceRulesCompile, Boolean bUsePrecompiled, UnrealIntermediateEnvironment IntermediateEnvironment, ILogger Logger) in D:\build++UE5\Sync\Engine\Saved\CsTools\Engine\Source\Programs\UnrealBuildTool\Configuration\UEBuildTarget.cs:line 1392
20:11:52.625:    at UnrealBuildTool.RiderProjectFile.WriteProjectFile(List1 InPlatforms, List1 InConfigurations, PlatformProjectGeneratorCollection PlatformProjectGenerators, JsonWriterStyle Minimize, ILogger Logger) in D:\build++UE5\Sync\Engine\Saved\CsTools\Engine\Source\Programs\UnrealBuildTool\ProjectFiles\Rider\RiderProjectFile.cs:line 119
20:11:52.625: Available x64 toolchains (1):
20:11:52.625:  * C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120
20:11:52.625:     (Family=14.41.34120, FamilyRank=5, Version=14.41.34123, Is64Bit=True, ReleaseChannel=Latest, Architecture=x64)
20:11:52.625: Visual Studio 2022 compiler version 14.41.34123 is not a preferred version. Please use the latest preferred version 14.38.33130
20:11:52.626: Available x64 toolchains (1):
20:11:52.626:  * C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120
20:11:52.626:     (Family=14.41.34120, FamilyRank=5, Version=14.41.34123, Is64Bit=True, ReleaseChannel=Latest, Architecture=x64)
20:11:52.626: Visual Studio 2022 compiler version 14.41.34123 is not a preferred version. Please use the latest preferred version 14.38.33130
20:11:54.125: Writing project files... 100%
20:11:54.158: Total execution time: 2.48 seconds
I have tried lots of things without lucky

I received this nottification too


docs: Fix upgrade.mode references

I guess upgrade.from is what is meant.

@hasegeli Could you fix the conflicts? I'd like to merge this PR :)

@hasegeli Could you rebase it again? It seems our Jenkins was on vacation :(

@hasegeli Thanks for contribution!


Links-only relations not handled correctly

Detailed description
If you retrieve an item that has links-only relations, modify it and then save it - the JSON sent to the remote server includes the relations with an empty data member - even though the client doesn't know what the data content of that relationship is.
Here's an example to illustrate this. Given this code:
$repo = app(\App\Repositories\PostRepository::class);
$post = $repo->find(1)->getData();
$json = $post->toJsonApiArray();

Say the server replied to the find request with this:
{
  "data": {
    "type": "posts",
    "id": "1",
    "attributes": {
      "content": "This is my first blog.",
      "title": "Hello World!"
    },
    "relationships": {
      "comments": {
        "links": {
          "self": "http://localhost/api/v1/posts/1/relationships/comments",
          "related": "http://localhost/api/v1/posts/1/comments"
        }
      }
    },
    "links": {
      "self": "http://localhost/api/v1/posts/1"
    }
  }
}

I.e. the comments relationship has no data member.
When toJsonApiArray() is called, it will serialize this:
[
    'type' => 'posts',
    'id' => '1',
    'attributes' => [
        'content' => 'This is my first blog.',
        'title' => 'Hello World!'
    ],
    'relationships' => [
        'comments' => [
            'data' => [],
        ],
    ],
    'links' => [
        'self' => 'http://localhost/api/v1/posts/1'
    ],
]

I.e. the comments relationship now has an empty data member. This is incorrect because the data member was never retrieved from the remote server, so the client has no way of knowing what the value for the relationship is.
Presumably the same bug will occur if the server replied with a relationship that only had a meta member.
Context
The JSON API spec says that a relationship must have at least one of data, links, meta - so the client should handle relationships that do not have the data member. It should not assume the relationship has an empty data member for a relationship for which it has not been provided a data member.
In my scenario, changing an attribute on the post and saving it back to the server causes the request to be rejected, as the server does not accept a data member for the comments relationship.
Possible implementation
When serializing relationships, particularly when saving the resource, any relationships that do not have a data member should be skipped, rather than the relationship being assumed to be empty.
Your environment
Laravel 7.22, PHP 7.2, latest version of this package.

@lindyhopchris, can you verify this is fixed on master?

@JaZo Hi! thanks for looking at this so quickly.
This does now work - it doesn't assume that a links-only relation is empty.
However, it throws up a new issue when saving the resource. Relations with no data member should not be present in the payload that's sent to the remote server. This is specified in the spec for creating:

If a relationship is provided in the relationships member of the resource object, its value MUST be a relationship object with a data member. The value of this key represents the linkage the new resource is to have. https://jsonapi.org/format/#crud-creating

And for updating...

If a relationship is provided in the relationships member of a resource object in a PATCH request, its value MUST be a relationship object with a data member. The relationship’s value will be replaced with the value specified in this member. https://jsonapi.org/format/#crud-updating

In other words, the serialization for an outbound request from the client to the remote server is a bit different - it needs to strip out relations that do not have a data member.

You are absolutely right, missed that! I've changed the serialization to strip out relations without a data member. Thanks for testing!

Fix released in 1.1.1.


About link on Chapters Page is not working

Description
When the user goes to the chapters and then goes to about. The link doesn't take the user anywhere. Therefore, the user cannot access the about page from there.
Expected Behavior
When user is on chapters page, and then decides to go to About. He/She should be able to go to About.
Screenshots

Enviroment:

OS: Windows
Browser: Chrome
Version:
Device: Desktop

@akshathar-navada Please assign me this issue.

hey @ishita80 , the link of about in the navbar is working fine. The link in footer 'About Us' has to redirect to the home page about  section ,pls resolve this!

Okay, I will do that.
But the issue is talked about occurs only when we are on the Chapters Page. Please go to Chapters and then click about.

The about in chapter page is directing me to the home page about section itself. Kindly check!

Ok


fix(clientLibs): update client lib versions

removes explicit ruby version
update java version

[ ] CHANGELOG.md updated with a link to the PR (not the Issue)
[ ] Well-formatted commit messages
[ ] Rebased/mergeable
[ ] Tests pass
[ ] http/swagger.yml updated (if modified Go structs or API)
[ ] Documentation updated or issue created (provide link to issue/pr)
[ ] Signed CLA (if not already signed)

LGTM

this is out of date.


Update dependency ghcr.io/appuio/appuio-cloud-agent to v0.7.1

This PR contains the following updates:

Package
Update
Change

ghcr.io/appuio/appuio-cloud-agent
minor
v0.6.1 -> v0.7.1

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

This is again handled as part of #129

Renovate Ignore Notification
As this PR has been closed unmerged, Renovate will now ignore this update (v0.7.1). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.
If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.


option to trigger bell on errors for console type

console.log('\u0007');

PR: #3

@orthagonal lets default to having it disabled for now

@jgallen23
ding should be disabled by default already. to activate you must define which tags trigger a ding, via the consoleBell option


Removes redundant label extractor from auto-configuration

Why is it redundant now? What has changed?

It's already being declared in https://github.com/spring-cloud/spring-cloud-gcp/blob/master/spring-cloud-gcp-autoconfigure/src/main/java/org/springframework/cloud/gcp/autoconfigure/trace/StackdriverTraceAutoConfiguration.java#L132

Good. So, I insist to include such an information into the commit message.
(I can reject my request if there are some strong arguments against)
Thanks


Cut 0.31.0 Release

Scheduled to happen: ~2022-01-31
All targeted pull requests have been merged; waiting for build and tests for release 0.31.0.
Release Steps
Process is described in this document.
Release Blocking PRs

[x] https://github.com/falcosecurity/libs/pull/185
[x] https://github.com/falcosecurity/falco/pull/1863
[x] https://github.com/falcosecurity/falco/pull/1864

Action Items

[x] Pre-Release: Pick a final driver version in Falco: 319368f1ad778691164d33d59945e00c5752cd27
[ ] Pre-release: Prebuilt drivers publish
[ ] Pre-release: Milestones
[ ] Pre-release: Changelog
[ ] Release: Tag
[ ] Release: GH Release
[ ] Docs: Meeting Notes
[ ] Website snapshot
[ ] Website: bump Falco version to 0.30.0
[ ] Website: Updates

https://github.com/falcosecurity/falco-website/pull/493
https://github.com/falcosecurity/falco-website/pull/515
Add plugin documentation for newest features (get_init_schema and list_open_params), and best practices

[ ] Announcements: Blog
[ ] Announcements: Send email
[ ] Announcements: Falco Slack channel

Open Questions
/milestone 0.31.0
/assign @jasondellaluce @terylt @Issif
/kind documentation

@jasondellaluce: GitHub didn't allow me to assign the following users: terylt.
Note that only falcosecurity members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

Scheduled to happen: ~2022-01-31
All targeted pull requests have been merged; waiting for build and tests for release 0.31.0.
Release Steps
Process is described in this document.
Release Blocking PRs
TODO
Action Items

[ ] Pre-Release: Pick a final driver version in Falco
[ ] Pre-release: Prebuilt drivers publish
[ ] Pre-release: Milestones
[ ] Pre-release: Changelog
[ ] Release: Tag
[ ] Release: GH Release
[ ] Docs: Meeting Notes
[ ] Website snapshot
[ ] Website: bump Falco version to 0.30.0
[ ] Website: Updates

https://github.com/falcosecurity/falco-website/pull/493
https://github.com/falcosecurity/falco-website/pull/515
Add plugin documentation for newest features (get_init_schema and list_open_params)

[ ] Announcements: Blog
[ ] Announcements: Send email
[ ] Announcements: Falco Slack channel

Open Questions
/milestone 0.31.0
/assign @jasondellaluce @terylt @Issif
/kind documentation

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Waiting for https://github.com/falcosecurity/libs/pull/185

In the milestone https://github.com/falcosecurity/falco/milestone/21 there are still some open PRs. Those are not blocking, but since the release date is approaching I think we should wait until the end of this week to see if some of them get merged.
Starting from Mon 24th, I would propose to stop merging PRs and start testing what we have for the rest of the week until the release.

Starting from Mon 24th, I would propose to stop merging PRs and start testing what we have for the rest of the week until the release.

Totally agree. :+1:
I would also pick the driver version within this week.

quick update:
I, @jasondellaluce and @FedeDP  noticed some minor issues (with rule checks on loading) that we're trying to fix.

quick update: I, @jasondellaluce and @FedeDP noticed some minor issues (with rule checks on loading) that we're trying to fix.
Rule loader checks fixed here :point_right: https://github.com/falcosecurity/falco/pull/1864 (plus other small fixes).

We also need to update the cloudtrail plugin (a fix was merged recently) :point_right: https://github.com/falcosecurity/falco/pull/1865
Finally, as nice-to-have: https://github.com/falcosecurity/falco/pull/1863

Dev package can be download from here :point_down:
https://app.circleci.com/pipelines/github/falcosecurity/falco/2007/workflows/cee05a2c-4d58-44f2-b6e3-8c7013cc3fda/jobs/18259/artifacts
I believe it's time to test :angel:

Nice-to-have: https://github.com/falcosecurity/falco/pull/1810

This https://github.com/falcosecurity/falco/blob/master/rules/aws_cloudtrail_rules.yaml#L23 is out-to-date.
The cloudtrail plugin version must be bumped to 0.3.0, but also the json plugin is required (we have to add it too).

On top of this, we also need to include the newly-mergedexecveat syscall in the Falco ruleset. Apparentely, it execve is used at this line, so I think it would make sense to check for execveat there too 👉🏼 https://github.com/falcosecurity/falco/blob/2f82a9baa193825337049e4ac69793f3074d6110/rules/falco_rules.yaml#L66

@leogr  done in https://github.com/falcosecurity/falco/pull/1867!

Update:
pre-built drivers in the making :point_down:
https://github.com/falcosecurity/test-infra/pull/613

@jasondellaluce done in #1868 :tada: !

There seem to be an issue with the musl optimized build. The ambiguity is that the MUSL_OPTIMIZED_BUILD is the name of the CMake option that triggers the musl build, whereas MUSL_OPTIMIZED is the name of the definition expected by libs. Falco passes the definition to libs in CMake here 👇🏼
https://github.com/falcosecurity/falco/blob/7750b6f209fdef7b709e22ee4325797dd01949ba/cmake/modules/falcosecurity-libs.cmake#L46
Falco spreadly uses MUSL_OPTIMIZED_BUILD as a code definition to exclude certain features, such as here 👇🏼 https://github.com/falcosecurity/falco/blob/7750b6f209fdef7b709e22ee4325797dd01949ba/userspace/falco/falco.cpp#L140
However, neither MUSL_OPTIMIZED_BUILD nor MUSL_OPTIMIZED is defined in Falco sources through CMake, which ends up not excluding any feature in musl builds.

There seem to be an issue with the musl optimized build. The ambiguity is that the MUSL_OPTIMIZED_BUILD is the name of the CMake option that triggers the musl build, whereas MUSL_OPTIMIZED is the name of the definition expected by libs. Falco passes the definition to libs in CMake here 👇🏼
https://github.com/falcosecurity/falco/blob/7750b6f209fdef7b709e22ee4325797dd01949ba/cmake/modules/falcosecurity-libs.cmake#L46
Falco spreadly uses MUSL_OPTIMIZED_BUILD as a code definition to exclude certain features, such as here 👇🏼
https://github.com/falcosecurity/falco/blob/7750b6f209fdef7b709e22ee4325797dd01949ba/userspace/falco/falco.cpp#L140
However, neither MUSL_OPTIMIZED_BUILD nor MUSL_OPTIMIZED is defined in Falco sources through CMake, which ends up not excluding any feature in musl builds.

https://github.com/falcosecurity/falco/pull/1871 is trying to fix the issue described above.
Moreover, while discovering the issue, we also realized that after https://github.com/falcosecurity/falco/pull/1853 got merged, the static build is not being published anymore. Since we believe it's still valuable we have decided to publish both the dynamic and the static flavor of the bin package (we will just use different file names), here the PR https://github.com/falcosecurity/falco/pull/1873 Thanks to @LucaGuerra for this last-minute effort :pray:

Another minor issue found:
Lua files are now embedded into the Falco executable, but we have noticed a leftover: the --alternate-lua-dir flag (that cannot work and is not useful anymore). Here the fix https://github.com/falcosecurity/falco/pull/1872 Thanks to @FedeDP

I tested the last master image. I was able to test monitoring of syscalls and audit logs. I also tested the integration with Falcosidekick and its outputs.
Everything worked as expected :+1:

I've been testing with the falco libs.  Compiled a version of the sfcollector with it.. and it's passing unit tests, and we are running it through our battery of tests.  Will update if I run into any issues.

/assign @terylt

quick update:
currently, test-infra is building drivers for the new version and has no more capacity.
for this reason, some PRs already approved are pending (tide is temporarily not working).
The issue should be solved once the driver building completes.

any chance for arm64 in this release?

Hey @juris , unfortunately arm64 support will not be shipped with this release. However I think this is one of the next goals for the near future.

Quick update. We seem to have spotted a bug related to the filterchek system related to these issues:

https://github.com/falcosecurity/plugins/issues/56
https://github.com/falcosecurity/plugins/issues/57
We ara investigating a fix and will hopefully open some PRs soon.

Updates: We have fixed all the code issues found in the past few days!
Now, there seems to be a CircleCI problem that causes the publish/packages-deb-dev job to fail 👉🏼 https://app.circleci.com/pipelines/github/falcosecurity/falco/2033/workflows/d553bc07-6f2d-4563-b511-9024ce79193c/jobs/18624
However, we didn't introduce any change in that part, so it's unclear why this happens. We are currently investigating.

CircleCI functionality restored. We also cleaned up the deprecated centos::8 build.
All clear now.
We are ready to release once the changelog PR https://github.com/falcosecurity/falco/pull/1880 gets merged. :star_struck:

All the post-release work is finished! Thanks to everybody for the help! 🥳 🦅


Pandora won't play when instructed via android

check version

I am running mycroft-core version 19 oh 2, release 7
Opensuse 15
AMD 8 core Processor
16 GIG RAM
android verson 1.01 snapshot
code 10001

Mycroft core says it doesn't know how to play pandora when instructed via android
It will play one out of two play lists on pandora when instructed via android
This file contains all 5 logs from /var/log/mycroft
mycroft.tar.gz

Hey, I don't run the Android client myself so won't be able to debug this, but wanted to see if you had used the Pandora Skill's special debug mode. This should help get extra information of what's happening when it crashes, this apparently can be activated vocally with "Pandora debug on".
If it wasn't on when the logs linked above were generated, can you remove the existing logs from /var/log/mycroft/*.log turn on Pandora debug mode, then replicate the issue?
This will give the most detailed info in the shortest space, which really helps to pinpoint the issue.


Add pt language support

Adding files for PT translation on Android

Any feedback on changes vs #173?


Add Organisation Monitoring

We should add organisations and allow them to monitor roads (and thus also vehicles). They should be able to do the following:

Monitor roads using sensors
Communicate their observations to other organisations, and vice versa.

First part is done in #7, Next part will be done trough #33

Done!


Delete Markdown files from the repo

Since the styleguide has been deleted, the repository contains a lot of redundant .md files. Being incorrect, outdated and misleading, they must be deleted.

I'd like to take this up

@jshreyans go ahead, this shouldn't take long.

@dhruvkb If this is taking time, I would like to give it a try.
Thank you

@techievivek we generally have a one week of inactivity rule before the issue is unassigned. It would be a good idea to find another issue in the meantime.

@dhruvkb Ok sure. Thank you.

@dhruvkb Sorry for the delay. Will send a PR today. Just to clarify, by the redundant md files, we mean the files that accompany each component in their respective folders right?


Caching limit and strategy

Hey, just wanted to say nice work on the performance improvements! It's great to see there's no upper limit in how fast a JSON validator for node can go. Caching the validator code internally is great and I guess does the trick for the benchmarks out there.
I was wondering, do you plan on introducing some caching configuration? A limit on the size/number of cached validator code, maybe together with some policy for purging stale validators (e.g. least recently used)? That would help a great deal in large-scale projects with lots of schemas, or when schemas are dynamically generated and can change a lot.
Keep up the good work!

Thank you :) Your jsen was great help too - I've spend quite some time analysing and comparing the code generated by it and imjv.
You are right, there is still some potential for speeding it up, maybe +25-50% I guess. But each step gives less return and more risky. I think you know it first hand. I've found using regexp replaces with generated code for some last step optimisations quite efficient and easier than introducing more conditions in code generation.
Benchmarks are not affected by caching actually, they are using precompiled functions anyway.
I wasn't thinking about the setup with multiple dynamic schemas, I haven't encountered such a use case. Can be added as an option with some LRU eviction I think (or even using set-associative cache I did recently - https://github.com/epoberezkin/sacjs) :) Or at least as an api to purge a schema from the cache - if they are used in other schemas they are referenced internally anyway, so there is no risk removing it.
I was more concerned about correct handling of referenced schemas, resolution scope changes, inline resolutions - that was what prompted me to create ajv in the first place (before I got hooked into benchmarks :). I couldn't find the one that was correctly handling all the cases when I started working on this - https://github.com/JSONScript/jsonscript . Actually I still have two ref resolution issues to resolve - #1 and #2.

Yeah, dereferencing and scope resolution is a pain. I guess there are several reasons this problem is not addressed in a good way in any of the high-profile JSON validators today:

The spec is vague, lacks detailed explanations and better use cases.
It kinda seem unintuitive to the average programmer who deals with schemas and JSON validation.
It's tightly coupled with remote reference fetching, a problem the bulk of JSON validators have put out of scope, as it deals with making HTTP requests.
I still haven't seen a viable real-world use case for scope dereferencing to date.

Actually, your current work seems to go as far as any JSON validator has gone in terms of proper scope resolution.

Thanks :)
You are right - I also think that the resolution scope change is not really necessary - the spec could've been simpler by saying there is one id per file, all internal references should be JSON pointers. Spec has actually got decent examples of scope change and inline resolution, but it doesn't make it any simpler to implement, particularly for generated code.
On the other hand any complex and recursively defined data-structure (tree/graph) will lead to many interlinked schemas in multiple files. So maybe for these complex structures these features make it a bit easier.
By the way, I'd love to hear what you think about JSONScript when you have a moment.

I think any specific caching strategy is out of scope, so I've implemented an option to pass an instance of any cache (see readme) and also removeSchema method.


For-Remove statement allows to remove current element from underlying…

… iterator collection in for-loops

Just noticed the pull-request, sorry. It seems it conflates everything (this, remove, regex, in...).
Would be easier to review if these were separate requests.


Checking to see if the network is online

This is broken.. It doesn't work behind proxy. Need option to disable this, else timing out for ages ~ around 7 minutes during each boot.

@epnixsite please take a look at a recent issue that overcame the same problem:

https://github.com/rancher/k3os/issues/203#issuecomment-539147240
https://github.com/rancher/k3os/issues/203#issuecomment-539170875

If rebuilding the ISO isn't an option for you then this wont do you much good when booting from the ISO but the advice above will completely sidestep the long waits when booting installed v0.3.0 systems.
All that said, I will readily admit that we do need a better experience for fresh air-gapped / firewalled installs.

I understand this and inspected scripts on githhub.. But these checks doesn't make any sense..
If you spinning k3os behind proxy - at least it should use /etc/environments to use HTT{P,PS}_PROXY vars and etc.. In previous versions it was working fine, why this has been added? Also ping in most corp environments would be disabled - so is invalid test too..

Fixed via #249


Stored checkpoints are not restored correctly

If I store a checkpoint after training for a long time with either Tensorflow/Python or TensorFlow.NET and then restore it in TensorFlow.NET then it doesn't give the correct results.
I've trained (in TensorFlow.NET) to e.g. a loss value of ~1.3 and if I then save a checkpoint and restore it in my TensorFlow.NET implementation I get a loss value of around 2.0. If I then take the same checkpoint from TensorFlow.NET and load in a Python implementation I get the expected 1.3 loss.
Did anyone else see something like that? It is this image processing problem I'm working on: https://github.com/meesoft/DnCNN-tensorflow
It is basically a lot of convolution layers with batch normalization. I can't completely rule out that there is a bug in my C# code but then it is just strange that everything behaves as expected until I save and restore.

Hi.. @meesoft  can you please tell me how did you load the ckpt file in c# that is stored using python. Thank you.


Create 8puzzleproblem.py

this is solution to 8 puzzle problem with a sar algorithm
Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

Hey
Thank you for opening this pull request.
This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding.


[issue] There is no typesafe relative to queryKeyFactory in setupServerActionHooks.useServerActionMutation.

I am using zsa-react-query on the client and while working with the library I needed to mutate the data, when I started inserting queryKey I noticed that the key types with createServerActionsKeyFactory are not supported. I looked in the source code and didn't see a type reference:
https://github.com/IdoPesok/zsa/blob/d3a9a153c33df76be4b6bd8e9c8a9eadebb11162/packages/zsa-react-query/src/index.ts#L47-L49
https://github.com/IdoPesok/zsa/blob/d3a9a153c33df76be4b6bd8e9c8a9eadebb11162/packages/zsa-react-query/src/index.ts#L166-L175
I think this would be useful, since mutation involves modifying and invalidating the react-query cache.
https://tanstack.com/query/v4/docs/framework/react/reference/useMutation
versions
"zsa": "0.5.0",
"zsa-react": "0.2.2",
"zsa-react-query": "0.2.0",

Hi, thank you for calling this out! Please try upgrading to<EMAIL_ADDRESS>where you should be able to pass in a mutationKeyFactory for the mutation hooks.


Support for elevenlabs.io

Omnivore was acquired by Elevenlabs, and they provide an upgrade path.
It is possible to create an API key on elevenlabs.io:

Will this plugin support syncing from elevenlabs.io?

Yeah came here to say the same thing. I love using Omnivore in Obsidian. It's the only reason I even use Omnivore. I'd love for this plugin to transition!

An alternative approach is to (on iOS) to use the ToMarkdown Safari extension that turns a page into Markdown, which you can Share to Obsidian app directly.
That way, though, no highlights, no template etc, and you have to type in the file name.
But also you don’t have to wait for the Obsidian extension to sync when you start it (I know there’s an option to turn this off).
I apologise for the offtopic.


add LICENSE to qat-initcontainer

fixes #1604

I added only to qat-initcontainer.
But if it is better to divide the "default_licences.docker" into two different pieces, or change one of the other "libraries", let me know. I did not see any reason to do so.

I did some grepping. Seems like intel-dlb-initcontainer, intel-idxd-config-initcontainer and intel-qat-initcontainer don't copy our LICENSE file. Could you update those as well?

I did some grepping. Seems like intel-dlb-initcontainer, intel-idxd-config-initcontainer and intel-qat-initcontainer don't copy our LICENSE file. Could you update those as well?

Hi, Tuomas! Mentioning intel-qat-initcontainer again means that we need to copy something else than the current change?
Isn't "our" LICENSE the file in the root directory of the repo?

Sure, I can add them to this pr.

:+1:

But, I am a bit confused about why you mention intel-qat-initcontainer again. Do you mean that we need to copy something else than the current change?

AFAIK, current change is fine for qat initcontainer. I was just grepping the project without your change.

Isn't "our" LICENSE the file in the root directory of the repo?

Yes, but we should have it also in the container images.


Eggplant only drops 1 either with fortune

Title. Even if this was intentional it seems odd. Maybe it and corn should drop 1-3?

This is now my third time telling you that this version of the mod has been discontinued.
Please stop leaving issues here.

uh okay? where is the new one. This is the page that the issue tab of your mod brings me to


Bump to SBT 1.8, bump libraries, remove deprecations.

bump to 0.12.0-SNAPSHOT
migrate SBT to 1.8.3, drop support for SBT 0.13 / 1.0.0
bump JUnit / JUnit 4 / Hamcrest / Mockito
bump Scala to 2.12.18, remove cross scala compiling
set minimum JDK version to 8, thus source / target to 1.8
add encoding / xlint settings

Compilation was tested with JDK 8, JDK 11, JDK 17.
I didn't test whether the release plugin / sonatype plugin still works, as I'm not familiar with it.

You could use sbt 1.9.0 already.

@mkurz Jesus, that was fast. :) Yes, bumped to SBT 1.9.

:wink: Title of the PR still says sbt 1.8...

@maichler do you need help maintaining this library? I have lots of experience with sbt-plugins, maintaining dozens of them within the sbt organization. Would you mind add me as maintainer so I can take a look at pull requests and merge them?
What do you think?

@maichler do you need help maintaining this library?

Hi @mkurz :wave:
I haven't been able to find the time for this project for a while now :( So yeah, I guess I could really use some help there.

I have lots of experience with sbt-plugins, maintaining dozens of them within the sbt organization. Would you mind add me as maintainer so I can take a look at pull requests and merge them? What do you think?

I think you're just the person this project needs right now, thanks a lot for the offer!
Let's give it a shot.

@maichler Also, if you want to keep the groupId net.aichler, we still could set up release by tag via https://github.com/sbt/sbt-ci-release. You would need to add some secrets yourself though: https://github.com/sbt/sbt-ci-release?tab=readme-ov-file#secrets
If you decide to change the groupId, you could make me admin of this repo and I can add credentials.

@maichler Perfect, thanks! Also what do you think about changing the groupId from net.aichler to com.github.sbt?

I don't mind changing the groupId, the only reason I kept it was to not break bc.

Because this repos already lives under the GitHub sbt organization, and not just that, we could set up an automatic release process via GitHub actions so with just pushing a tag a release gets published to maven central automatically. I did set up such workflows in many sbt projects already with that groupId.

That would simplify the process a lot, I like it :+1:

Great, thanks! I will come back to set up things this week.

@maichler Just to let you know, I renamed the master branch to main, because this is more common now and all repos I work with a named that way (also actually the reusable workflows I will introduce expecte the default branch to be named ´main`).

Hallo @mkurz, any info regarding merging this PR? Thanks

@sleski I plan to work on this in July/August and to integrate it into Play Framework.

👋🏼 I wanted the PR to split the library bump and sbt bump so I sent https://github.com/sbt/sbt-jupiter-interface/pull/75 for the sbt + GitHub Actions bumps.

Scala Steward took care of the JUnit 5 bump, and I've cherry picked the hamcrest bump to https://github.com/sbt/sbt-jupiter-interface/pull/83 + CI checking on Zulu JDK 8 and Temurin JDK 17.


Visual Studio 15: building project with TypeScript results in "The VsTsc task failed unexpectedly"

We are unable to build a project with Typescript in it because of an error during compilation on the Microsoft.TypeScript.targets file. We have been able to reproduce this on two machines.
Error    MSB4018 The "VsTsc" task failed unexpectedly.
System.UriFormatException: Invalid URI: The format of the URI could not be determined.
   at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
   at System.Uri..ctor(String uriString)
   at TypeScript.Tasks.VsTsc.MakeProjectRelative(String path)
   at TypeScript.Tasks.VsTsc.LogEventsFromTextOutput(String singleLine, MessageImportance messageImportance)
   at Microsoft.Build.Utilities.ToolTask.LogMessagesFromStandardErrorOrOutput(Queue dataQueue, ManualResetEvent dataAvailableSignal, MessageImportance messageImportance, StandardOutputOrErrorQueueType queueType)
   at Microsoft.Build.Utilities.ToolTask.HandleToolNotifications(Process proc)
   at Microsoft.Build.Utilities.ToolTask.ExecuteTool(String pathToTool, String responseFileCommands, String commandLineCommands)
   at TypeScript.Tasks.VsTsc.ExecuteTool(String pathToTool, String responseFileCommands, String commandLineCommands)
   at Microsoft.Build.Utilities.ToolTask.Execute()
   at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
   at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext() C:\Users\me\Documents\GitHub\app\src\app\app.xproj  C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\TypeScript\Microsoft.TypeScript.targets Line    223

TypeScript Version:  2.0.0-beta
Visual Studio Version: VS 2015 14.0.25424.00 Update 3
Node.js version: v6.3.0
tsconfig.json
{
  "compileOnSave": false,
  "compilerOptions": {
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "module": "commonjs",
    "moduleResolution": "node",
    "noEmitOnError": true,
    "noImplicitAny": false,
    "removeComments": false,
    "sourceMap": false,
    "target": "es5",
    "outDir": "/wwwroot/angular/bin"
  },
  "exclude": [
    "wwwroot"
  ]
}

Expected behavior:
Visual Studio permits project to compile.
Actual behavior:
Visual Studio emits compilation error.

Can you share a diagnostic build log?

Made this more resilient for 2.0 RC, if it still repros please attach a diagnostic build log

HI, I am stuck at the following error in Visual Studio 2017 RC.
The language service is disabled for project 'D:\app(3)\app\app\app.jsproj' because it included a large number of .js files. Consider excluding files using the 'exclude' section of a 'tsconfig.json' file.
The operation has timed out	appname
MSB4018	The "VsTac" task failed unexpectedly.
System.ArgumentNullException: Value cannot be null.
Parameter name: requestUriString
at System.Net.WebRequest.Create(String requestUriString)
at Microsoft.VisualStudio.MultiDeviceHybridApps.MdaBuildTasks.RemoteBuild.CreateWebRequest(String url)
at Microsoft.VisualStudio.MultiDeviceHybridApps.MdaBuildTasks.RemoteBuild.PollForBuildComplete(String buildingUrl, Int32 interval, Int32 attempts)
at Microsoft.VisualStudio.MultiDeviceHybridApps.MdaBuildTasks.RemoteBuild.Build()
at Microsoft.VisualStudio.MultiDeviceHybridApps.MdaBuildTasks.VsTac.BuildPlatform()
at Microsoft.VisualStudio.MultiDeviceHybridApps.MdaBuildTasks.VsTac.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.d__26.MoveNext()	EKGEO2015	C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Microsoft\VisualStudio\v15.0\ApacheCordovaTools\vs-mda-targets\Microsoft.MDA.FileMirroring.targets	256
can somebody help me here, I have not been able to build the soln in 2015 and 2017 VS since last 1 month.
Life has been hell....
quick help to resolve this very much appreciated....

@ekambarrao looking at the stack, that crash doesn't seem related to TypeScript. I think you'll get more traction on the VS developer community.

@paulvanbrenk thx for response. I am not using any type script. I am able to build the same solution from different machine but can not from one machine.
the above was where I was held up and now this one.
1>MSBUILD : cordova-build error : An error occurred uploading to the build server https://<IP_ADDRESS>:3000/cordova/build/tasks?command=build&vcordova=7.0.1&cfg=debug&options=--device: The operation has timed out
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Microsoft\VisualStudio\v15.0\ApacheCordovaTools\vs-mda-targets\Microsoft.MDA.FileMirroring.targets(256,5): error MSB4018: The "VsTac" task failed unexpectedly.
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Microsoft\VisualStudio\v15.0\ApacheCordovaTools\vs-mda-targets\Microsoft.MDA.FileMirroring.targets(256,5): error MSB4018: System.ArgumentNullException: Value cannot be null.
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Microsoft\VisualStudio\v15.0\ApacheCordovaTools\vs-mda-targets\Microsoft.MDA.FileMirroring.targets(256,5): error MSB4018: Parameter name: requestUriString
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Microsoft\VisualStudio\v15.0\ApacheCordovaTools\vs-mda-targets\Microsoft.MDA.FileMirroring.targets(256,5): error MSB4018:    at System.Net.WebRequest.Create(String requestUriString)
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Microsoft\VisualStudio\v15.0\ApacheCordovaTools\vs-mda-targets\Microsoft.MDA.FileMirroring.targets(256,5): error MSB4018:    at Microsoft.VisualStudio.MultiDeviceHybridApps.MdaBuildTasks.RemoteBuild.CreateWebRequest(String url)
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Microsoft\VisualStudio\v15.0\ApacheCordovaTools\vs-mda-targets\Microsoft.MDA.FileMirroring.targets(256,5): error MSB4018:    at Microsoft.VisualStudio.MultiDeviceHybridApps.MdaBuildTasks.RemoteBuild.PollForBuildComplete(String buildingUrl, Int32 interval, Int32 attempts)
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Microsoft\VisualStudio\v15.0\ApacheCordovaTools\vs-mda-targets\Microsoft.MDA.FileMirroring.targets(256,5): error MSB4018:    at Microsoft.VisualStudio.MultiDeviceHybridApps.MdaBuildTasks.RemoteBuild.Build()
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Microsoft\VisualStudio\v15.0\ApacheCordovaTools\vs-mda-targets\Microsoft.MDA.FileMirroring.targets(256,5): error MSB4018:    at Microsoft.VisualStudio.MultiDeviceHybridApps.MdaBuildTasks.VsTac.BuildPlatform()
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Microsoft\VisualStudio\v15.0\ApacheCordovaTools\vs-mda-targets\Microsoft.MDA.FileMirroring.targets(256,5): error MSB4018:    at Microsoft.VisualStudio.MultiDeviceHybridApps.MdaBuildTasks.VsTac.Execute()
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Microsoft\VisualStudio\v15.0\ApacheCordovaTools\vs-mda-targets\Microsoft.MDA.FileMirroring.targets(256,5): error MSB4018:    at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Microsoft\VisualStudio\v15.0\ApacheCordovaTools\vs-mda-targets\Microsoft.MDA.FileMirroring.targets(256,5): error MSB4018:    at Microsoft.Build.BackEnd.TaskBuilder.d__26.MoveNext()
1>Done building project "app.jsproj" -- FAILED.
MSB4018	The "VsTac" task failed unexpectedly.
System.ArgumentNullException: Value cannot be null.
Parameter name: requestUriString
at System.Net.WebRequest.Create(String requestUriString)
at Microsoft.VisualStudio.MultiDeviceHybridApps.MdaBuildTasks.RemoteBuild.CreateWebRequest(String url)
at Microsoft.VisualStudio.MultiDeviceHybridApps.MdaBuildTasks.RemoteBuild.PollForBuildComplete(String buildingUrl, Int32 interval, Int32 attempts)
at Microsoft.VisualStudio.MultiDeviceHybridApps.MdaBuildTasks.RemoteBuild.Build()
at Microsoft.VisualStudio.MultiDeviceHybridApps.MdaBuildTasks.VsTac.BuildPlatform()
at Microsoft.VisualStudio.MultiDeviceHybridApps.MdaBuildTasks.VsTac.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.d__26.MoveNext()	EKGEO2015	C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Microsoft\VisualStudio\v15.0\ApacheCordovaTools\vs-mda-targets\Microsoft.MDA.FileMirroring.targets	256

@ekambarrao considering you're not using any typescript.. pleae open an issue on the VS developer community. The people there are much better at finding you the right person/team to talk to. This is the TypeScript  repo, and I honestly have no idea where to direct you.

@paulvanbrenk thx for response. What I figured out is, size of the solution is the culprit that is resulting to break due to timeout.
Is there any max limit or time limit or some thing which I should mention somewhere to handle this "time out error"?

@ekambarrao not that I'm aware off... I've not heard of this.

I some how found that my problem of VSTAC was due to timeout. It is now resolved. However I am held up in a confused situation now. What version of Cordova should one use?
Cordova 6.5.0 do not work with xcode 8.3.1 and ios 10.2
cordova 7.0.1 do not work with lower version but works only with xcode 8.3.1 and ios 10.2.
My app working well in simulators but failing in device.
How to handle this forward compatibility of cordova issue?
or my understanding is wrong?

Hi, my application is running well in simulator for ios but not working in devices.
I am unable to make out the reasons as
I am not able to debug the app in device as the deployment to device for local debug is failing.
It is giving network error xmlhttprequest 101 error.
When I click on ios button, it is dumping some error which containts " exitapp ", though my app don't have exitapp plugin and statement.
I am unable to figure out the reasons why it is not working.
I built using cordova 6.5.0 and I tried using it in ipod with 9.3.1 and iPhone 5s with 10.2.1.
can somebody help to resolve this!! I am completely held up clueless to which direction should I go from here?

@ekambarrao You should really open an issue in the VS Developer community, or Stack Overflow. You'll get much more useful responses there.

@paulvanbrenk, I opened not only in those two places, I wrote to MacinCloud support and also in social msdn. but no responses.

having the same problem with the timeout after 90 seconds, opened an issue at remotebuild: https://github.com/Microsoft/remotebuild/issues/43


BIGTOP-2764: deployment failure when roles include spark::common and spark::yarn*

We need to ensure the spark-datanucleus package is only defined once.  There's a hack in place so it is always defined in spark::common (see BIGTOP-2268):
https://github.com/apache/bigtop/blob/master/bigtop-deploy/puppet/modules/spark/manifests/init.pp#L154
This PR comments out the other definition, which should be reinstated if/when 2268 is fixed.

I've updated the original workaround to include spark::datanucleus instead of redefining the package.  This is much cleaner than including multiple comment blocks to explain the 2268 hack.

spark-39 contains this fix, and is green across clouds for hadoop + spark in yarn mode:
http://bigtop.charm.qa/cwr_bundle_hadoop_spark/33/report.html

LGTM +1

Thanks for the review @ktsakalozos.
+1 as well.

Closed by https://github.com/apache/bigtop/commit/73864a30b29ee89655772ce82b4041c2564d0711


Add FluxCD v0.32 / v0.33 / v0.34 / v0.35

Do we want to deprecate / remove some of the older versions here now?

I don't have a preference, I did an attempt once by looking for upstream supported versions, but smallish projects often do not have a definition for that. Feel free to remove some, if someone is missing any it will be easy to bring it back. Automation FTW.

I've trimmed the versions <0.30 (which is from May), see how that goes I guess?

Seems like there's a jsonnet error now

Oops 😬
Force pushed a typo fix


[ZEPPELIN-5530] Support scala-2.13 for spark interpreter

What is this PR for?
Spark 3.2 starts to support scala-2.13, this PR is to support scala-2.13 on the zeppelin side. A new module scala-2.13 is introduced in this PR. SparkILoop is copied from the spark project with minor modification.
What type of PR is it?
[Feature]
Todos

[ ] - Task

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-5530

How should this be tested?

CI pass

Screenshots (if appropriate)
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

CI is passed, will merge if no more comment


fix: use / for directory separator in pathname

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


remove suggestion of : immobiliare/sentry-php

Hello,
so basically, if we managed to install via composer require, means we have PHP >= 5.3
then we don't need to suggest installing this?
Or am I missing something obvious

It's correct to assume that Composer does not work on PHP < 5.3, so I'm 👍 to remove the suggestion. Maybe we can put it in a section of the docs, but imho it makes no sense as PHP 5.2 is old, not supported and I don't think that there are a lot of people that uses it so the effort would not be justified


Add trigger dag option to deployment workflow

Why
Most of the time, I use the deploy-integration-tests-to-astro-cloud for testing certain DAGs. Thus, if we can add an option to let the workflow which DAGs should be triggered after the deployment, it would facilitate our testing process
Changes

github-actions

add dags_to_trigger_after_deployment input to deployment workflow

dev/providers_rc_test_scripts

change trigger_master_dag into trigger_dag which can take argument dag_ids to trigger multiple different dags

Example run
https://github.com/astronomer/astronomer-providers/actions/runs/5068141893


Gradle build is failing when carbon-components is used as dependency.

Detailed description
Failed to create MD5 hash for file '/home/jenkins/workspace/wdp-classifiers-ui_master-Y2UXLB4VWZBJ3NYAGQYCXWPG27AL752NDKFBJCVDXGUGJLT2XRFQ/node_modules/carbon-components/html/content-switcher/content-switcher???with-icon.html'

Is this issue related to a specific component?
The file, content-switcher--with-icon.html, is seen at couple of places. Everytime Jenkins is failing
carbon-components/src/components/content-switcher/content-switcher???with-icon.html'
BTW, this was working earlier, not sure what else is changed.

What did you expect to happen? What happened instead? What would you like to see changed?
Can we change this file's name?

What version of the Carbon Design System are you using?
I tried both 8.14.2 and 8.15.2

Thanks in advance,
Sreekanth

@asudoh It is not clear if you've changed the file name from content-switcher--with-icon.html to content-switcher-with-icon.html Please confirm.

The reported issue is solved now with "carbon-components": "^8.15.3", you can close this github issue.
Thanks


Add mocks to Coinbase Commerce

@lucasrmp-cb can you add more context about why we need this?

The idea here is mock this requests so we don't break calls like this one because the OS contributor won't have credentials for coinbase commerce. That's also true for capitol canary calls

We'll work with synthetic tests for those cases, it makes this request unnecessary


Introduce eslint-plugin-no-jquery/no-event-shorthand

https://github.com/go-gitea/gitea/pull/24098#issuecomment-1514010690

No problem. I think I will explore enabling more rules from that plugin.


Fix focus issues

Fixes #74
node.setSelectionRange caused focus jump in Safari and mobile browsers. The solution is to set selection only if the input is in the active (focused) state to not interfere with other inputs.

@jsillitoe Any chance this could be merged in this week?

Any news on it? :) It will help me to solve a bug on IE11

Merged.

@jsillitoe Please, could you publish this fix to NPM?

@jsillitoe Please, could you publish this fix to NPM?

Yes, that would be much appreciated @jsillitoe !

Is this published to NPM yet?

Still experiencing this as an issue in IE11, so I think it's still not published to NPM

Lots of people have un-done this change in forks...


feat(fix): fix starknet.py version requirement

What I did
Fixes the ape importing error from the new version of starknet.py
fixes: #7
How I did it
How to verify it
Install ape-cairo from this pr and check that there is no error when we use the ape cli
Checklist

[ ] Passes all linting checks (pre-commit and CI jobs)
[ ] New test cases have been added and are passing
[ ] Documentation has been updated
[ ] PR title follows Conventional Commit standard (will be automatically included in the changelog)

Please also note that this fix is temporary and using the newest version of starknet py would be better