Sequence-based implementation of combining algorithms in addition to variadic ones

Existing implementations of combineLatest , zip , merge are great when the total number of sequences is known at compile time (2 or 3 without variadic generics). In some scenarios, these sequences have same element types, but the total number of sequences is computed at run time. Existing implementations won't work here, and I think the library would benefit from implementations that take a Sequence (or some other container protocol) of AsyncSequences that have the same element type to cover these use cases.

Thanks for opening this @MaxDesiatov. This is something we can look into after the 1.0 release!

This is my attempt to make combineLatest support variadic parameters.
https://github.com/apple/swift-async-algorithms/pull/322/files


[Beta 2] query keyword is required in all queries

Describe the bug
Previously, you could make a query like so:
const String getUsers = """
  {
    users {
      id
      name
    }
  }
"""

however, now the query keyword is required, even if no variables are being passed.
const String getUsers = """
  query getUsers {
    users {
      id
      name
    }
  }
"""

To Reproduce
Steps to reproduce the behavior:

Attempt to make the first query (any query without query
Failure

Expected behavior
query should not be required.

+1. Query builder should support default behavior of no query keyword.
Moreover, request would fail by unknown operation if there was a parameter list after query keyword without query name.
For example this query doesn't work:
query ($order_by_time: Boolean = true) {
    items(order_by_time: $order_by_time){
        id
        name
    }
}

It has to be:
query GetItemsByOrder ($order_by_time: Boolean = true) {
    items(order_by_time: $order_by_time){
        id
        name
    }
}

When we use query or mutation without Operation name it will add operation name like
_operationName ??= 'UNNAMED/' + document.hashCode.toString();
And my backend hasura graphql server gives error in invalid operation

It's not in just query when I run mutation from bloc (not using mutation widget) throws this error.

@Kyle-MendeHow is this a valid query?
const String getUsers = """
  users {
    id
    name
  }
"""

Even if the query keyword is omitted shouldn't there always be wrapping brackets like so:
const String getUsers = """
  {
    users {
      id
      name
    }
  }
"""

@HofmannZ Oops! I accidentally typed it out wrong :) Good catch!

yeah this looks like a regression - probably need to decouple operationName from the operation identification functionality I added the default for.
I've been a bit busy, but I should be able to get to this later this week

@micimize any progress?

@endigo I haven't had time to work on it - I would update here proactively if I had

closed by #276

:tada: This issue has been resolved in version 1.0.1-beta.8 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Automock only "application/json" requests?

Describe the bug
I want to mock all application/json requests for my app with RegExp but when I use below it mocks every request/response included .css, .js files also.
beforeEach(() => {
  cy.playback('POST', new RegExp('^/*/'), { toBeCalledAtLeast: 0 });
  cy.playback('GET', new RegExp('^/ab/*/'), { toBeCalledAtLeast: 0 });
  cy.playback('GET', new RegExp('^/search/*/'), { toBeCalledAtLeast: 0 });
});

Is there any way to mock only application/json requests/responses?

The library uses Cypress intercept, so instead of using a url, you could specify a more specific route matcher if you only want certain calls to be intercepted and mocked. For example you should be able to specify only requests with application/json headers.
https://github.com/oreillymedia/cypress-playback?tab=readme-ov-file#url-string-glob-regexp

@DigTheDoug  thanks a lot 🙏


*ngIf error after updating project to 2.4.8 from 2.2.1

Ionic version:  (check one with "x")
[ ] 1.x
[ ] 2.x
I'm submitting a ...  (check one with "x")
[ ] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

template parse errors:
Parser Error: Unexpected token : at column 1 in [search] in<EMAIL_ADDRESS>Expected behavior:

*ngIf is should work as it expected
Steps to reproduce:

Related code:
1h
[code]

<ion-title class="header-title" *ngIf!="search">Exam List
<ion-searchbar  *ngIf="search">-->

[/code]
insert any relevant code here

Other information:
This code was working with 2.2.1 but after updating to 2.4.8 it is giving error.
template parse errors:
Parser Error: Unexpected token : at column 1 in [search] in<EMAIL_ADDRESS>Unhandled Promise rejection: Template parse errors:
Parser Error: Unexpected token : at column 1 in [search] in HomePage@5:16 ("

<ion-title [ERROR ->]*ngIf!="search" class="header-title">Class Detail
<ion-searchbar (ionInput)="getItems"): HomePage@5:16
Parser Error: Unexpected token : at column 1 in [search] in HomePage@5:16 ("n>
<ion-title *ngIf!="search" class="header-title">Class Detail
<ion-searchbar ERROR ->="getItems($event)" [hidden]="search">
<ion-buttons end [hidden]="sea"): HomePage@6:19
Parser Error: Unexpected token : at column 1 in [search] in HomePage@5:16 ("rch" class="header-title">Class Detail
<ion-searchbar (ionInput)="getItems($event)" [ERROR ->][hidden]="search">
<ion-buttons end [hidden]="search"><button ion-button clear "): HomePage@6:49
Parser Error: Unexpected token : at column 1 in [search] in HomePage@5:16 ("

<ion-title *ngIf!="search" class="header-title">Class Detail
[ERROR ->]<ion-searchbar (ionInput)="getItems($event)" [hidden]="search">
<ion-buttons en"): HomePage@6:4, Directive Searchbar
Parser Error: Unexpected token : at column 1 in [search] in HomePage@5:16 ("

<ion-title *ngIf!="search" class="header-title">Class Detail
[ERROR ->]<ion-searchbar (ionInput)="getItems($event)" [hidden]="search">
<ion-buttons en"): HomePage@6:4, Directive Searchbar
Parser Error: Unexpected token : at column 1 in [search] in HomePage@5:16 ("

<ion-title *ngIf!="search" class="header-title">Class Detail

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
insert the output from ionic info here

ordova CLI: 6.5.0
Ionic Framework Version: 2.1.0
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.1.4
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 10
Node Version: v7.7.1
Xcode version: Not installed
This same code is working fine in other project having 2.2.1 it is in header bar
.

ngIf!="search. Should it be ngIf="!search"

Thanks it is working now.I would be more careful now on these things.


Added Snyk

See Issue #85

Coverage remained the same at 100.0% when pulling 3cb61a78d87411e1f0ad83a5e21bf81fc91039e2 on feature/snyk into 5e2dd481ef2157507fff7bdb514f88b53aef6de4 on master.


Can't Test with mockObserver navigation in an app with Multiprovider.

This worked when I had just one provider but doesn't when I do setup with Multiprovider.
// Mock class
class MockNavigatorObserver extends Mock implements NavigatorObserver {}

class MockAuthProvider extends Mock implements AuthProvider {}

class MockUserProfileProvider extends Mock implements UserProfileProvider {}

NavigatorObserver mockNavigatorObserver;
MockAuthProvider mockAuthProvider;
MockUserProfileProvider mockUserProfileProvider;

void main() {
 setUp(() {
    mockNavigatorObserver = MockNavigatorObserver();
    mockAuthProvider = MockAuthProvider();
    mockUserProfileProvider = MockUserProfileProvider();
  });

Future<Null> buildWidget({
  WidgetTester tester,
  Widget widgetToBuild,
}) async {
  await tester.pumpWidget(
    MultiProvider(
    providers: [
      ChangeNotifierProvider<AuthProvider>(create: (BuildContext context) {
        return mockAuthProvider;
      }),
      ChangeNotifierProvider<UserProfileProvider>(
          create: (BuildContext context) {
        return mockUserProfileProvider;
      }),
    ],
    child: MaterialApp(
      // the non-config bit next line
      home: widgetToBuild,
      //more config below
      routes: RouteConfig.routes,
      navigatorObservers: [mockNavigatorObserver],
    ),
  ));

  tester.pumpAndSettle();

  verify(mockNavigatorObserver.didPush(any, any));
}

Future<Null> navigateToPageByButtonKey(
    WidgetTester tester, String buttonKey) async {
  Finder buttonFinder = find.byKey(Key(buttonKey));
  expect(buttonFinder, findsOneWidget);

  await tester.tap(buttonFinder);
  await tester.pumpAndSettle();
}

testWidgets('CreateProfile .. NextButton -> CalendarScreen',
      (WidgetTester tester) async {
    await buildWidget(
      widgetToBuild: CreateProfileScreen(),
      tester: tester,
    );

    var userNameField =
        find.byKey(Key(CREATE_PROFILE_SCREEN_USERNAME_FORM_FIELD_KEY));
    await tester.enterText(userNameField, 'testUserName');
    await navigateToPageByButtonKey(
        tester, CREATE_PROFILE_SCREEN_NEXT_BUTTON_KEY);
    // verify(mockNavigatorObserver.didPush(any, any));
    expect(find.byKey(Key(CALENDAR_SCREEN_KEY)), findsOneWidget);
  });
}

run output:
══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
The following assertion was thrown building MultiProvider:
Failed assertion: boolean expression must not be null

Either the assertion indicates an error in the framework itself, or we should provide substantially
more information in this error message to help you determine and fix the underlying cause.
In either case, please report this assertion by filing a bug on GitHub:
  https://github.com/flutter/flutter/issues/new?template=BUG.md

The relevant error-causing widget was:
  MultiProvider
  file:///Users/derga002/Projects/flutter/nanny_share/nanny_share/test/test_helper.dart:33:5

When the exception was thrown, this was the stack:
#0      _ListenableDelegateMixin.debugCheckIsNewlyCreatedListenable (package:provider/src/listenable_provider.dart:140:26)
#1      _BuilderListenableDelegate.startListening (package:provider/src/listenable_provider.dart:128:12)
#2      _ListenableDelegateMixin.initDelegate (package:provider/src/listenable_provider.dart:169:24)
#3      _DelegateWidgetState._initDelegate (package:provider/src/delegate_widget.dart:118:21)
#4      _DelegateWidgetState.initState (package:provider/src/delegate_widget.dart:110:5)
#5      StatefulElement._firstBuild (package:flutter/src/widgets/framework.dart:4355:58)
#6      ComponentElement.mount (package:flutter/src/widgets/framework.dart:4201:5)
#7      Element.inflateWidget (package:flutter/src/widgets/framework.dart:3194:14)
#8      Element.updateChild (package:flutter/src/widgets/framework.dart:2988:12)
#9      ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
#10     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
#11     ComponentElement._firstBuild (package:flutter/src/widgets/framework.dart:4206:5)
#12     ComponentElement.mount (package:flutter/src/widgets/framework.dart:4201:5)
#13     Element.inflateWidget (package:flutter/src/widgets/framework.dart:3194:14)
#14     Element.updateChild (package:flutter/src/widgets/framework.dart:2988:12)
#15     RenderObjectToWidgetElement._rebuild (package:flutter/src/widgets/binding.dart:1028:16)
#16     RenderObjectToWidgetElement.update (package:flutter/src/widgets/binding.dart:1006:5)
#17     RenderObjectToWidgetElement.performRebuild (package:flutter/src/widgets/binding.dart:1020:7)
#18     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
#19     BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:2432:33)
#20     AutomatedTestWidgetsFlutterBinding.drawFrame (package:flutter_test/src/binding.dart:974:18)
#21     RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:283:5)
#22     SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1102:15)
#23     SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1041:9)
#24     AutomatedTestWidgetsFlutterBinding.pump.<anonymous closure> (package:flutter_test/src/binding.dart:872:9)
#27     TestAsyncUtils.guard (package:flutter_test/src/test_async_utils.dart:69:41)
#28     AutomatedTestWidgetsFlutterBinding.pump (package:flutter_test/src/binding.dart:859:27)
#29     WidgetTester.pumpWidget.<anonymous closure> (package:flutter_test/src/widget_tester.dart:323:22)
#32     TestAsyncUtils.guard (package:flutter_test/src/test_async_utils.dart:69:41)
#33     WidgetTester.pumpWidget (package:flutter_test/src/widget_tester.dart:320:27)
#34     buildWidget (file:///Users/derga002/Projects/flutter/nanny_share/nanny_share/test/test_helper.dart:32:16)
#35     main.<anonymous closure> (file:///Users/derga002/Projects/flutter/nanny_share/nanny_share/test/create_profile_screen_test.dart:13:11)
#36     testWidgets.<anonymous closure>.<anonymous closure> (package:flutter_test/src/widget_tester.dart:124:25)
#37     TestWidgetsFlutterBinding._runTestBody (package:flutter_test/src/binding.dart:696:19)
<asynchronous suspension>
#40     TestWidgetsFlutterBinding._runTest (package:flutter_test/src/binding.dart:679:14)
#41     AutomatedTestWidgetsFlutterBinding.runTest.<anonymous closure> (package:flutter_test/src/binding.dart:1050:24)
#47     AutomatedTestWidgetsFlutterBinding.runTest (package:flutter_test/src/binding.dart:1047:15)
#48     testWidgets.<anonymous closure> (package:flutter_test/src/widget_tester.dart:121:22)
#49     Declarer.test.<anonymous closure>.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:171:27)
<asynchronous suspension>
#50     Invoker.waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:242:15)
#55     Invoker.waitForOutstandingCallbacks (package:test_api/src/backend/invoker.dart:239:5)
#56     Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:169:33)
#61     Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:168:13)
#62     Invoker._onRun.<anonymous closure>.<anonymous closure>.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/invoker.dart:392:25)
#76     _Timer._runTimers (dart:isolate-patch/timer_impl.dart:384:19)
#77     _Timer._handleMessage (dart:isolate-patch/timer_impl.dart:418:5)
#78     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:174:12)
(elided 32 frames from class _FakeAsync, package dart:async, package dart:async-patch, and package stack_trace)

════════════════════════════════════════════════════════════════════════════════════════════════════
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following TestFailure object was thrown running a test:
  No matching calls (actually, no calls at all).
(If you called `verify(...).called(0);`, please instead use `verifyNever(...);`.)

When the exception was thrown, this was the stack:
#0      fail (package:test_api/src/frontend/expect.dart:153:30)
#1      _VerifyCall._checkWith (package:mockito/src/mock.dart:648:7)
#2      _makeVerify.<anonymous closure> (package:mockito/src/mock.dart:935:18)
#3      buildWidget (file:///Users/derga002/Projects/flutter/nanny_share/nanny_share/test/test_helper.dart:54:9)
#17     AutomatedTestWidgetsFlutterBinding.runTest.<anonymous closure> (package:flutter_test/src/binding.dart:1066:17)
#19     AutomatedTestWidgetsFlutterBinding.runTest.<anonymous closure> (package:flutter_test/src/binding.dart:1054:35)
(elided 29 frames from class _FakeAsync, package dart:async, package dart:async-patch, and package stack_trace)

The test description was:
  CreateProfile .. NextButton -> CalendarScreen
════════════════════════════════════════════════════════════════════════════════════════════════════
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following message was thrown:
Multiple exceptions (2) were detected during the running of the current test, and at least one was
unexpected.
════════════════════════════════════════════════════════════════════════════════════════════════════
00:02 +0 -1: CreateProfile .. NextButton -> CalendarScreen [E]
  Test failed. See exception logs above.
  The test description was: CreateProfile .. NextButton -> CalendarScreen

00:02 +0 -1: Some tests failed.

flutter doctor output:
~/Projects/flutter/nanny_share/nanny_share [fix_tests] $ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, v1.12.13+hotfix.5, on Mac OS X 10.15.2 19C57, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 11.3)
[✓] Android Studio (version 3.5)
[✓] IntelliJ IDEA Ultimate Edition (version 2019.2.4)
[✓] VS Code
[✓] Connected device (1 available)

• No issues found!

Hi @belaad
provider is without doubt an excellent package,
but it's a 3rd party package nevertheless.
You may want to open an issue in the dedicated github
Closing, as this isn't an issue with Flutter itself,
if you disagree please write in the comments and I will reopen it
Thank you


MAP-1457 JwtAuthInterceptor unused classes test coverage

There some classes not used They should be deleted

There is not usage of this class

This simply file removal increase 1 % the coverage
->

89.5% (136/152) | 84.3% (522/619) | 67.3% (659/979) | 90.1% (3210/3561) | 90.2% (16701/18512)
-- | -- | -- | -- | --


Replace Data Catalog with Azure Purview

At line 132 the comparison is between AWS Glue and Data Catalog. AWS Glue IMO is a ETL tool and Data Catalog is a governance tool. Not sure it its a fair comparison. Also, Data Catalog should be replaced with Azure Purview

@EdPrice-MSFT : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#Sign-Off

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

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.


fix(toml): Add default-features to TomlWorkspaceDependency

In #11329 it was noted that default-features is ignored when used in a dependency that inherits from a workspace i.e.
[workspace]
members = []
[workspace.dependencies]
dep = "0.1"

[package]
name = "bar"
version = "0.2.0"
authors = []
[dependencies]
dep = { workspace = true, default-features = false }

This problem is caused by problems with deserializing a TomlDependency and not emitting an unused manifest key correctly. When discussed in a recent Cargo team meeting we felt the best course of action was to allow default-features = false when inheriting a dependency, but it does not change actually set default-features. It will be used to warn when there is a difference between the definition in [workspace.dependencies] and [dependencies] i.e.
[package]
name = "bar"
version = "0.2.0"
[dependencies]
dep = { workspace = true, default-features = false }

[workspace]
members = []
[workspace.dependencies]
dep = { version = "0.1", default-features = true }

This does not entirely resolve the problem with unused manifest keys. A follow up PR and issue will be created to address those concerns.
close #11329

I'm overall a bit uncertain about the behaviors here, so I'm going to write out what my expectations would be:
workspace: foo = { version="1.0", default-features = false }
member: foo = { workspace = true }
expectation: The foo dependency should have default-features disabled. There should not be any warning, as this was the expected syntax that was decided in the RFC, and is generally the natural way to write it. That is, the user wanted whatever was defined in the workspace.
workspace: foo = { version="1.0", default-features = false }
member: foo = { workspace = true, default-features = true }
expectation: The foo dependency should have default-features enabled. There should not be any warning. This allows different members to decide whether or not they have the default-features enabled. (If this is a warning/error, users could circumvent it with features=["default"] which seems unnecessary.)
workspace: foo = { version="1.0", default-features = false }
member: foo = { workspace = true, default-features = false }
expectation: The foo default-features should be disabled. I think it should be allowed without warning, it is just re-iterating the workspace value.

workspace: foo = { version="1.0", default-features = true } or foo = "1.0"
member: foo = { workspace = true }
expectation: The foo dependency should have default-features enabled. No warning/error.
workspace: foo = { version = "1.0", default-features = true } or foo = "1.0"
member: foo = { workspace = true, default-features = false }
expectation: This should have been an error, but since it was erroneously accepted in the past, it should be a warning that the default-features is ignored, and may be an error in the future.
workspace: foo = { version = "1.0", default-features = true } or foo = "1.0"
member: foo = { workspace = true, default-features = true }
expectation: This should have been an error, but since it was erroneously accepted in the past, I think we should just accept it without a warning/error. It is just re-iterating the default. It is also I think a bit unlikely (I don't see default-features = true done very often).
WDYT?

I personally would agree with @ehuss on expectations, however it's worth noting that the RFC does specify different behavior currently:

For now if a workspace = true dependency is specified then also specifying the default-features value is disallowed. The default-features value for a directive is inherited from the [workspace.dependencies] declaration, which defaults to true if nothing else is specified."

I would very much like to have the ability to use the second case in the posted list however, despite it being against the RFC as currently written.

I agree with what was talked about above. It is the best way forward with minimal changes to the expected behavior. I have implemented tests for the changed behavior. Let me know if you want me to add tests for the unchanged behaviors.

BTW, when you are ready for a review, you can use @rustbot ready, and it will update the PR labels.

@rust-lang/cargo This makes some changes to the way default-features=… is handled with workspace inheritance. Since this is a small change in behavior, and a small deviation from the RFC, I'm going to go ahead and do an FCP to run it by everyone. The table below should summarize the behavior.

Workspace
Member
Old Default
New Default
Reasoning

nothing
df=false
Enabled
Enabled, warning that it is ignored.
Should have been an error in the past since the field is ignored. May change to an error in the future.

df=true
df=false
Enabled
Enabled, warning
^Same

nothing
df=true
Enabled
Enabled
There is no conflict about default being enabled.

df=true
df=true
Enabled
Enabled
^Same

nothing
nothing
Enabled
Enabled
No ambiguity.

df=true
nothing
Enabled
Enabled
^Same

df=false
df=false
Disabled
Disabled
No ambiguity.

df=false
df=true
Disabled
💥Enabled
This allows members to decide whether or not they want default features. The workaround of features=["default"] seems unnecessary.

df=false
nothing
Disabled
Disabled
Natural way to write "give me whatever was written in workspace".

@rfcbot fcp merge

Wanted to make clear some points

The deviation from the RFC is we allow the package to have default-features in the dependency
We are maintaining the additive nature of the package dependency, it can enable default features but it can't disable them

With those, I think this makes sense and I'm fine with it.
As for the warning, at worse, it can be an error in the next edition.  If we feel the impact is minimal, we can change it sooner.

@bors r+

:pushpin: Commit 49d722cfe654a86c7e4f3847742bb13b7702da28 has been approved by weihanglo
It is now in the queue for this repository.

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing 7e2a3c21e0e13388b6e5e82cacb016934187ed13 to master...


Attempt to rename the nuget package tgz to avoid long path issues when releasing the package

Recently, there were some templates added that have a long enough folder/path name that the npm packaging steps of the release pipeline started failing.
It appears that the ADO extract task keeps the full filename and the nested folder's filename, creating a giant path like this:
D:\a\r1\a\npm-publish\_azure_monitor_workbook_templates-1.0.0-build.15583.tgz_\azure_monitor_workbook_templates-1.0.0-build.15583.tar\package\en-us\workbooks...
where the npm package+version number ends up in that path 2x, and then the names of the processed templates.  This PR tries to rename that build output to a shorter name (build.tgz) to try to get back 50-100 characters in the path. (i think it will only affect the first instance of the path, but i'm not sure, and without running the release pipeline on the output from this build, i won't know if it still gets packaged+correctly deployed with the right npm package name.
I've also opened up an issue with CDPX to see if there's some other settings for this i can turn on to avoid having to do this.
I've also notified the team that was affected by the long path.
Once i figure out what the resulting path is, i can add a validation to make sure folder paths don't exceed the limitations here.  (still sad/amazed that a 255 ch path limit is still a thing in 2020, but this is 2020 so it seems very apropos)
after the buddy build passed, i do see that the output is renamed:

but need to verify it on the real master build, and that the real deployment still finds the output and deploys the package to npm correctly.

i'm going to try to complete this, and see if the build AND deployment work. if they don't, i'll revert this


Missing CONTRIBUTING.md File in Repository

The repository currently lacks a CONTRIBUTING.md file, which is an important resource for guiding potential contributors on how to engage with the project effectively. A CONTRIBUTING.md file outlines the contribution guidelines, coding standards, and procedures for submitting pull requests, thus streamlining the contribution process and ensuring consistency across contributions.
Could you please assign this issue to me under GSSOC 24.

In The repository I can add a CONTRIBUTING.md file which will be helpful for all the contributor who visited this project
I would like to work on this issue . so please assign this task to me and Can u please label the issue as GSSoC'24

This issue is already solved.
Try to contribute to different issues.


npm-check fixes

Deliverables

[ ] apply audit fix
[ ] update outdated deps
[ ]  add depcheck config to package.json

Work for this issue will begin begin on branch work-liquid-labs/question-and-answer/69.


1,2,3,4 (list of any type) parsed as error

hi, i was testing few examples and looks like this case is not working. is it valid?

list is defined as [1,2,3,4]

@pragyandas thanks for your response, ive seen other engines and examples are without square brackets, also 9.2.6 doesnt includes intervals grammar as 9.2.8. could you have a sec could yo recheck? thanks.
ref: 9.2.6 simple expressions = simple expression , { "," , simple expression } ;

@gustavomick I cannot find the semantics of simple expressions in the DMN 1.1 specs. Can u please direct me to some resource which explains the usage of simple expressions.

Not sure what you asking for, is this useful?

https://docs.camunda.org/manual/7.6/reference/dmn11/feel/language-elements/

considering those examples i reframe that "1 + 2 / = A" is not a valid expression for an input entry, since is not boolean expression right side , nor an arithmetic expression nor a simple value. hope it helps. thanks.

@gustavomick Thanks for directing me to the right resource. I will add simple expressions and make some tweaks to the grammar to invalidate expressions like "1 + 2 / = A"

y np glad to help. good weekend

@pragyandas wondering if there is any estimated resolution time on this one? thanks!

I am working on this one right now. I should be able to update the status soon.

hi @pragyandas i was considering about using this library, but since we have no updates since last month i'm not sure about continuity. is this still alive? thanks

It is very much active, here is what we are working on:

DRG/ DRD design and initial implementation
Correcting decision table expression
Deeper integration with oecloud model relations (Example: writing expression parent.parent.name for example will fetch parent from parentId twice)

By the way we are also planning to open source bpmn implementation in node.js soon.

Seems a lot going on there, any chance to have this small fix separated from this big push? thanks

@gustavomick I tried adding simple expressions but the grammar for it is parallel to grammar for expression. As the parser used in FEEL is a parser with single allowedStartRules, it is not possible to implement this with the current configuration. However, I will try to generate a parser with multiple allowedStartRules and check if it works. Will update you soon on this.

@gustavomick I have added simple expressions to the grammar. It has been made a different grammar entry point.
As the usage of simple expressions is very specific to input and output entries in a decision table, a parallel grammar implementation is desired.
The following code snippet illustrates the usage of the same :
const FEEL = require('./dist/feel');

const context = '{a : 1, b:2, c:3, d:4}';
const parsedContext = FEEL.parse(context); // parsed with default entry point

const text = 'a,b,c,d'
const parsedText = FEEL.parse(text,{startRule : "SimpleExpressions"}); // parsed with "SimpleExpressions" entry point

parsedContext.build().then(ctx => {
  return parsedText.build(ctx);
}).then((result) => {
    console.log(result);
}).catch(err => {
    console.error(err);
});

Hey, thanks for your feedback, could you expand on what you mean "specific to input and out entries", i'm confused .. is not "input / outputs exps" the main purpose of FEEL existence?
From what i see from dmn standard (ref above) is not a separated grammar, is core to grammar itself , rule number 1) "expression = simple expression"
again thanks for your thoughts on this, may be im misunderstanding something here.

@gustavomick I think you are referring to S-FEEL (the subset of FEEL). In FEEL expression and simple expressions are parallel to each other (DMN 1.1 clause 10). In the previous comment, I talked about input and output entries of a decision table and not I/O expressions.
As input/output entries are not implemented in the current decision table implementation, I can't include an example at this point.

thanks, i haven't found the reference you are mentioning regarding that they are parallel (could be a spec ambiguity) so if you can provide me with page / sections would be super useful,
in mean time few comments that to me worth debating when you have a moment to read:
1 - I think there is a kind of contradiction here. if we say s-feel is a subset, we are implying that is "part of" so included on Feel, and not an alternative grammar.
2 - Conformance Level 3 (FEEL) must be fully compliant with Level 2 (S-FEEL), is not possible to conform L 3 without L 2, so s-feel clauses are a must, from conformance pov.
3- Considering dmn spec FEEL grammar rule is also saying  (ref picture)
simple expression = arithmetic expression | simple value => textual expression = simple expression =>  expression = simple expression . I'm not fully tracing this grammar tree but only this branch makes simple exp a requirement.
4- and they there is a usability factor, we can say not(1,2,3) is valid, but 1,2,3 is not (among other cases) . i can not "sell" that, to me language primarily have to make sense from user pov.
thanks again

As it can be noted from the spec, S-FEEL is primarily for the purpose of implementation in decision table only. But there are other Boxed Expressions and decision table is one of them. According to the FEEL grammar specs, expression is not directly related to simple expressions in any way, neither are simple positive unary tests and unary tests. Considering the complexity of the grammar specification it is necessary to have multiple start rules for the grammar implementation. Simply put, the start rules create some sort of grouping for the parsing of the grammar and can be used for parsing different aspects of the language. Moreover, as FEEL is not a context-free grammar, there is a need for multiple entry points to provide some context for usability.

Ok i have other comments but I think at this point we can agree to disagree. :) I mean I wanted you to recheck this before were too late and need it a major refactor but if you think is the right path is fine by me.
Let me know if you have any second thoughts about this. Thanks for your feedback and have a good day.

@gustavomick Well, sometimes it is very difficult to find sense out the specification in a very straight forward way as it is kinda cryptic at places and there are no clear demarcations for these kinds of things. I figured it out the hard way but PEG.js saved me with the option --allowed-start-rules. But it is a very common practice for languages to have multiple start rules to allow complexity. I will still keep an eye open for the issues that might come in while analyzing this. You too have a great day. Thanks. :)


Is there a support for Web?

Is there a support for Web?

No, unfortunately, this library requires Native SDKs.  Use ReactNative Platform to conditionally switch between maplibre-react-native and maplibre-gl-js in the component.


make bufio.Reader a member of lxi.Device

Hello,
I would suggest to make the bufio.Reader instantiated in the Query method a member of the Device struct.
There are multiple potential problems with the existing code.

The reader may read more data than the line, if possible. This data will be lost.
The reader allocates buffers for buffering data and the reader object. This creates pressure on the GC.

By making the Reader a member of the Device struct, it becomes persistant as well as its buffers and the data it contains. Is it still possible to use the Read methods and even read bytes per bytes, but efficiently.
Change the Device into this:
type Device struct {
	conn net.Conn
	rdr *bufio.Reader
}

The NewDevice function becomes:
func NewDevice(address string) (*Device, error) {
	v, err := NewVisaResource(address)
	if err != nil {
		return nil, err
	}
	tcpAddress := fmt.Sprintf("%s:%d", v.hostAddress, v.port)
	c, err := net.Dial("tcp", tcpAddress)
	if err != nil {
		return nil, err
	}
	return &Device{conn: c, rdr: bufio.NewReader(c)}, nil
}

Note that the convention is to return a nil Device in case of error.
The Read function becomes:
// Read reads from the network connection into the given byte slice.
func (d *Device) Read(p []byte) (n int, err error) {
	return d.rdr.Read(p)
}

The Close function becomes:
// Close closes the underlying network connection.
func (d *Device) Close() error {
	d.rdr = nil
	c := d.conn
	d.conn = nil
	return c.Close()
}

And Query becomes:
func (d *Device) Query(cmd string) (string, error) {
	err := d.Command(cmd)
	if err != nil {
		return "", err
	}
	return d.rdr.ReadString('\n')
}

@chmike — Thanks!


Support for claimTask.allowOverrideAssignment

The GraphQL API supports a parameter allowOverrideAssignment in the claimTask mutation, that is not available in the Java Client yet. Please add it as an optional parameter to the CamundaTaskListClient.claim method

Hi @angelo-v,
I'll try to look into it next week. If you want it earlier, please feel free to open a PR :)

Hi @angelo-v,
This is available in 1.6.2 and you now ave 2 claims method. One with allowOverrideAssignment and the other one without (default value will be false). Hope that helps! Tell me if I can close the ticket after your tests. Thanks :)

Thank you very much for the quick response, this is helpful


Address id collision potential in tabs, anchor tabs, and possibly others

🧹 Tech Debt
The anchor tabs and tabs components use a FAST utility function to generate id values for some elements (if not provided by the client). These are of a simple form, like tab-1 that could conflict with ids of other elements. We should evaluate how to best avoid this.
Refer to comment in PR: https://github.com/ni/nimble/pull/1042#discussion_r1101771988

The linked discussion thread lists several ideas for resolving this. The first step is to reach out to FAST to see if they agree this is a bug.


tsconfig.json completely ignored

Hey guys.
When I run grunt-ts it ignores my tsconfig.json file and nothing is generated.
My tsconfig.json looks like this:
{
    "compilerOptions": {
        "module": "amd",
        "declaration": false,
        "noImplicitAny": false,
        "removeComments": true,
        "isolatedModules": false,
        "jsx": "react",
        "noLib": false,
        "preserveConstEnums": true,
        "outDir": "../build",
        "sourceMap": false,
        "newLine": "LF"
    },
    "filesGlob": [
        "./**/*.ts",
        "./**/*.tsx"
    ],
    "exclude": [
        ".baseDir.ts"
    ],
    "files": [
        "./_all.d.ts",
        "./App.ts",
        "./AppModule.ts",
        "./AppModuleConfig.ts"
    ]
}

And my grunt task is like this:
ts: {
      default: {
        tsconfig: './app/tsconfig.json'
      }
},

Am I missing something?

This works for me:
	ts: {
		options: {
			fast: 'never'
		},
		build: {
			tsconfig: {
				tsconfig: "./src/",
				passThrough: true
			}
		}
	},

No lucky with that configuration.

Hi - sorry for the delay.  I've been very busy with a new job and baby and a few other projects.  I will try to look into this as soon as possible.

@ealves-pt What version of TypeScript and grunt-ts do you have?  Please run this in your command line from the same folder as your gruntfile.js, and see if it runs TypeScript as you expect:
node node_modules\typescript\lib\tsc.js --project app

(if you need to fix this at all to get it working, let me know how)
By the way - please re-read the docs in the grunt-ts readme about how to use the tsconfig option.  The exclude property is ignored if a filesGlob is specified.

@nycdotnet the current versions in user are<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Running that command works as expected.
Regarding the exclude config I already dropped it my config file.

Ah ok.  grunt-ts added support for tsconfig.json in v5.  Update to the latest grunt-ts (5.1.1 as of today) and it should hopefully work OK.

Worked like a charm. Thank you very much for the help. :+1:


WIP: Regexp Unicode support

Part of https://github.com/NVIDIA/spark-rapids/issues/5549
Changes in this PR:

New regexp fuzz tests that generate unicode input data
RegExp will fall back to CPU if LANG is not en_US.UTF-8
An exception will occur if any executors has a different LANG setting to the driver

Driver error when LANG is not UTF-8
      !Expression <RegExpReplace> regexp_replace(name#4, [ae], _, 1) cannot run on GPU because regular expression support is disabled because environment variable 'LANG' is not set to 'en_US.UTF-8' and this would result in incorrect handling of Unicode data
        @Expression <AttributeReference> name#4 could run on GPU

Driver & Executor LANG mismatch
java.lang.RuntimeException: Driver and executor LANG mismatch. Driver LANG is 'en_US.UTF-8' and executor LANG is 'cockney'.
	at com.nvidia.spark.rapids.RapidsExecutorPlugin.init(Plugin.scala:218)

build

build

build

build

build

Closed in favor of https://github.com/NVIDIA/spark-rapids/pull/5776


Is it list_max/2 like in Scryer or max_list/2 like in SWI?

In order to run https://github.com/josd/phy with both Trealla and Scryer we currently do a dirty trick in https://github.com/josd/phy/blob/19b39eac5b4c054048680d3556c994bf4edf92c6/phy.pl#L517
as well as in https://github.com/josd/phy/blob/19b39eac5b4c054048680d3556c994bf4edf92c6/phy.pl#L525
Maybe it is possible to also provide list_max/2 and list_min/2 in https://github.com/trealla-prolog/trealla/blob/main/library/lists.pl ?

Thanks @infradig it is now working fine.


cloud-init stuck at docker-cache.service

Hi @pires
I'm using this project to brought kubernetes up in my local machine, and fleetctl list-machines gives right output, but it failed to do kubectl create, output is
F0307 18:28:04.580672   56532 create.go:81] Post http://<IP_ADDRESS>:8080/api/v1beta1/pods?namespace=default: dial tcp <IP_ADDRESS>:8080: connection refused
I sshed in master, and found it didn't start kubernetes api server, and I only find flanneld setup-network-environment waiter.sh in /opt/bin, also ps -aux says coreos-cloudinit is still running and stat is Ssl. I couldn't find where cloud-init's log exists, so I killed cloud-init and started it manually, it seems it stucks at docker-cache.service.
several line at end of output:
2015/03/07 10:27:56 Calling unit command "start" on "fleet.socket"'
2015/03/07 10:27:56 Result of "start" on "fleet.socket": done
2015/03/07 10:27:56 Calling unit command "start" on "fleet.service"'
2015/03/07 10:27:56 Result of "start" on "fleet.service": done
2015/03/07 10:27:56 Calling unit command "start" on "etcd-waiter.service"'
2015/03/07 10:27:56 Result of "start" on "etcd-waiter.service": done
2015/03/07 10:27:56 Calling unit command "start" on "docker-cache.service"'
I don't know how to fix this.

Docker-cache is a registry docker container that will serve as a cache for
minions to use when pulling images from the Internet. It takes sometime to
download, depending on your Internet speed. Is it slow for you?
On Mar 7, 2015 10:46 AM, "Di Xu"<EMAIL_ADDRESS>wrote:

Hi @pires https://github.com/pires
I'm using this project to brought kubernetes up in my local machine, and fleetctl
list-machines gives right output, but it failed to do kubectl create,
output is
F0307 18:28:04.580672 56532 create.go:81] Post
http://<IP_ADDRESS>:8080/api/v1beta1/pods?namespace=default: dial tcp
<IP_ADDRESS>:8080: connection refused
I sshed in master, and found it didn't start kubernetes api server, and I
only find flanneld setup-network-environment waiter.sh in /opt/bin, also ps
-aux says coreos-cloudinit is still running and stat is Ssl. I couldn't
find where cloud-init's log exists, so I killed cloud-init and started it
manually, it seems it stucks at docker-cache.service.
several line at end of output:
2015/03/07 10:27:56 Calling unit command "start" on "fleet.socket"'
2015/03/07 10:27:56 Result of "start" on "fleet.socket": done
2015/03/07 10:27:56 Calling unit command "start" on "fleet.service"'
2015/03/07 10:27:56 Result of "start" on "fleet.service": done
2015/03/07 10:27:56 Calling unit command "start" on "etcd-waiter.service"'
2015/03/07 10:27:56 Result of "start" on "etcd-waiter.service": done
2015/03/07 10:27:56 Calling unit command "start" on "docker-cache.service"'
I don't know how to fix this.
—
Reply to this email directly or view it on GitHub
https://github.com/pires/kubernetes-vagrant-coreos-cluster/issues/30.

well, around 220Kb/s, kind of slow. how long it will take, and how should I determine if it's finished?

when docker ps show registry
when kubernetes binaries are running

On Sat, Mar 7, 2015 at 10:55 AM, Di Xu<EMAIL_ADDRESS>wrote:

well, around 220Kb/s, kind of slow. how long it will take, and how should
I determine if it's finished?
—
Reply to this email directly or view it on GitHub
https://github.com/pires/kubernetes-vagrant-coreos-cluster/issues/30#issuecomment-77684079
.

--
Pires

ok, finished, thanks a lot


enhancement request: Numbers across the UI to match the browser selection

Is there an existing issue for this?

[X] I have searched the existing issues

Enhancement description
Numbers across the UI to match the browser selection
🧑💻 Implementation
Use Pipe
Anything else?
No response

I'll make it

@astra1 I believe there is a missed numbers pipe on the asset group selector


Implement Array#pack

Remove "skip-test" comment from top of a spec/core/array/pack/*_spec.rb file.
Modify ArrayPacker and/or StringPacker to make the specs pass
Commit! (EASY! :laughing:)

[x] a_spec.rb
[x] at_spec.rb
[x] b_spec.rb
[ ] buffer_spec.rb
[x] comment_spec.rb
[x] c_spec.rb
[x] d_spec.rb
[x] empty_spec.rb
[x] e_spec.rb
[x] f_spec.rb
[x] g_spec.rb
[x] h_spec.rb
[x] i_spec.rb
[x] j_spec.rb
[x] l_spec.rb
[x] m_spec.rb
[ ] n_spec.rb
[ ] percent_spec.rb
[ ] p_spec.rb
[ ] q_spec.rb
[x] s_spec.rb
[x] u_spec.rb
[ ] v_spec.rb
[ ] w_spec.rb
[ ] x_spec.rb
[x] z_spec.rb

@seven1m It seems that directives n+N and p+P  have been implemented in PR #668. We can check them off the list.

🎉


ProcAmp (video settings for Brightness, Contrast, Hue, and Saturation)

support ProcAmp in yami vpp, this should include unittest too

Close this since it's in planning.


Sundowner meta, AKA reflect land

Description

To be short, I have seen while playing on salamander a reocurring build that can be purchased by syndies, loneops and nukies at the cost of 24 TC.
It's composed of the following: Juggernaut suit (12TC), E-sword (8TC), E-dagger (2TC), EMP implant (2TC) at bare minimum.
Why ?
Because this build gives crazy survivability to the person running it, and has BARELY any counter.  What you are looking at is a guy that can, while standing still, reflect any projectile (stuns, bullets, ANY and all of them) thanks to the recent reflect chance change giving for example the E-sword 50% reflect chance while standing still. This stacks with the E-dagger. Then it has 80% resistance to most damage, and short range stun doesn't work due to the EMP implant. And the reflect doesn't stop when they move, it is lower yes but still present and quite high, near 50%
TL:DR a player can buy for 24TC gear that makes him able to deflect all projectiles, is immune to stun and if you do manage to hit them will not take any kind of damage.
Counters ?
I did mention a few counters, they go as follows:
-stinger grenades (works only when they are standing on top of it, or two are hit in quick succession)
-hypospray, with narcs, or poison (need to get in close range and the only person who has it likely won't be fighting, and well, shouldn't be the one dealing with it)
Some may mention truncheons, but truth is you need to land 28 continouus hits to down them with it, since truncheon stun damage is based on the blunt damage dealt.
This is not theory crafting, it's been run before on mander and has proven to be an easy way to get a loneop victory without any effort, strategy, or preparation, just at most a bit of button pressing. See round #55095.
TL:DR
What we are left with is a build that can be ran easily by loneops and nukies, and requires to kill renault for syndies, requires no prep, is flat immune to most takedown manners present in the game nor requires much skill.
The way I see the ISSUE at is in reflect chances, way to fix it would be to hopefully make dual wielding reflecting weapons not stack for crazy reflect chance, or just reducing their max reflect chances individually.
Alternatively, make energy blades affect by EMP, this would ensure it isn't that easy to just get crazy deflect and close range stun immunity.

Just dont come close wtf
le solution
le pipegun + bolas
stamina crit
gg
what the fuck, use your mind for goodies


Performance impact (esp. with subdocuments)

Hi! Today I started investigating slow updates in my app, found https://github.com/aldeed/meteor-simple-schema/issues/347, and built an app to measure performance along a number of axes (is the schema attached?, plus the validate and bypassCollection2 flags, number of DB entries and subdocuments).
I've found that performance degrades rapidly as even a small number (50 - 100) of subdocuments are added, as well as when inserting a relatively small number of DB entries (again, 50 - 100) when the schema is attached and bypassCollection2 is false. This is hinted at in the documentation, but even so, it feels like performance issues should crop up only when the (sub)document count is a few orders of magnitude higher. I realize improvements like this require major effort, my expectations are set accordingly, but maybe even starting a conversation is useful.
The repo to reproduce (just clone and start with meteor): https://github.com/abesto/meteor-simple-schema-347-repro
A screenshot of various measurements:

Hey @abesto I'm also running into performance issues. My bigger worry right now is that this repo is dead (like Simple Schema) and that @aldeed is not maintaining it anymore. I'm about to launch my product and I'm already running into a bunch of performance problems. Simple Schema/Collection2 do not seem to be scalable.
For me the main issue is that clean is killing it, taking several seconds to complete. I'd be curious to hear about your tests or results if you've gone further in your analysis.

@Taakn nope, this is the full extend of my research. I guess one work-around is not using subdocuments. Another is not checking the schema at runtime. Can't think of any others.
For me this was used in a side-project only.

Thanks @abesto MongoDB is offering document validation now so I might move towards that https://docs.mongodb.com/manual/release-notes/3.2/#document-validation

I have an app that has to regularly load 140kb of JSON into a collection while the user is waiting. This was taking 30 seconds! After removing SimpleSchema it took a quarter of a second.
I had to remove the schema until something gets fixed on this. :(

Closing. I'm guessing this was fixed by SimpleSchema 1.2.0 last year. See https://github.com/aldeed/simple-schema-js/issues/206


Task list to display only the active window

is it possible to create a rule to reveal on task list only the active window title?

You want the task list to display only the active window and not inactive windows?
Or do you want to display all open windows on the task list, without the icon?

A picture is worth 1000 words.  Can you illustrate what you want?

You want the task list to display only the active window and not inactive windows?
Or do you want to display all open windows on the task list, without the icon?

Only the active window, and hide all the others, and nothing when there is no active window (or something more custom)


How to create a web service that receives non-form-data?

I am attempting to create a web service that receives a HTTP Post whose message body is XML.   Using the PostableRestfulWebService example I have been able to get a service working that receives Form data.   But I get errors when I try send XML data.  It seems the problem is that com.google.sitebricks.headless.Request expects data to be submitted as Form data.   Is there an alternate to this Request interface that I can specify here to be able to accept alternate data formats?   Or other mechanism for receiving non-form data?

Disregard this post.   I realize that you simply use the HttpServletRequest instead.

Does the request.read() method not work? That has similar semantics to Reply.with().as(Xml.class);Alternatively, you can inject the HttpServletRequest and Xml transport as method arguments and process the servletRequest.getInputStream() directly.Dhanji


LinkAbstractor class fails with PHP 7.3+

The issue originated from https://github.com/sunra/php-simple-html-dom-parser library, seems like it's not maintained anymore.
See https://github.com/sunra/php-simple-html-dom-parser/issues/74
https://github.com/sunra/php-simple-html-dom-parser/issues/84
What about replacing it with a maintained one? There is a replacement suggested by @voku that looks promising.
https://github.com/sunra/php-simple-html-dom-parser/issues/77
https://github.com/voku/simple_html_dom

@HamedDarragi
How did you install concrete5? Our composer.json apply patches for it automatically. See also: https://github.com/concrete5/dependency-patches

@hissy i'm using https://github.com/concrete5/concrete5-core i use also https://github.com/concrete5/dependency-patches but it wasn't applied as the extra property missed the correct allow-subpatches:
"extra": {
    "allow-subpatches": [
      "concrete5/dependency-patches",
      "concrete5/core"
    ]
  }

Anyway, it works for now. but IMO it's time to get rid of some dead dependencies.


consistent pointer use in Create/Update calls

Adds CreateImage, UpdateImage, DeleteImage
Changes UpdateOptions and CreateOptions and similar Options parameters to values instead of pointers, these were never optional and the function never updated any values in the Options structures
Changes InstanceUpdateOptions to use pointers for optional fields Backups and Alerts, adds WatchdogEnabled
Changes InstanceClone's Disks and Configs to ints instead of strings
Adds RescueInstance and RescueInstanceOptions
Updates template.go which can be used as a manual template when adding support for missing endpoints

This closes #37 and addresses most of the concerns in #29

I'm willing to take the coverage hit for now, because with https://github.com/chiefy/linodego/issues/32 we will create Instances and walk all of the config and disk functions in a controlled environment, without magic and the requirement that personal accounts have fixture conditions.


fix the SVG component export

Great, thanks. I've tested this with the basic-svg example and it works fine.
Tested with:

Destructured usage – const { Path } = Svg;
react-native-svg style import – import Svg, { G, Path } from 'react-sketchapp/lib/components/Svg';
Static usage – Svg.Path


I have a concern

Your website is great, but I have a concern.
Can i like reset my controller before it was calibrated?
Thanks

Hi, nope it cannot be done. The website overwrites the factory calibration written in the controller.


[WIP]chore(side-panel): исправил функцию формирования урла сторибука в демках

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.007%

Covered Lines:
6842

Relevant Lines:
7880

💛  - Coveralls


Add content for Baremetal section under Setup section

Add procedure for baremetal setup

@Rupeshiya You can add it under Setup - Installation section -"Installing OpenEBS on Bare Metal"

@Rupeshiya When will you be able to work on this?

No separate documentation is required for running OpenEBS as long as the common prerequisites are met.
(This issue was created earlier, when the K8s install also was being documented as part of the OpenEBS installation.)


use static_assertions to assert invariants about opqaue struct sizes

These are currently debug_assert!() which won't fail until runtime.

Ah, this won't work with generics.


Spike on Form builder architecture

Notes from Mae:

Another note, it knows which kind of Response input to display bc Question has both name and input_type

My Response has fields for each kind of input type to simplify, so, fields are:
string_value
integer_value
file_value
boolean_value
array_value

The Checklist/Tasklist builder was built the same way so as to store the List (Form) separate from the Assignments (Responses).

Hey, I wasn't part of the Spike discussion, so I might be missing some context, but I'm concerned that updating or deleting a question could mess up the historical response data. E.g. if a question is deleted, all associated responses would also be removed. I think keeping historical data is crucial, especially since it may contain important information like adopter contact details, and losing such data could be problematic.
But I think there's a straightforward solution. We can add question_text and input_type fields to the Response model and when creating a response, we should copy this information from the Question. This way, even if the question is later updated or deleted, we'll still have a record of the original question text at the time the response was submitted. It might also be necessary to modify or remove the foreign_key constraint between the Response and the Question models (so we can delete Question, without losing Responses).
I hope this is helpful :) We can also add this later if needed and keep the solution simple for now.

Thanks for raising the valid concern @Ptrboro ! I wonder if @edwinthinks 's idea of soft deleting would be sufficient? If we do that then we wouldn't have to add redundant data elsewhere. We could also use the gem papertrail to keep track of versions of Questions (not sure if this addresses the need around Question deletion though). What do you all think?
For now, it's probably best to make Questions unable to be updated or deleted just for simplicity but I think we'd want to support updates/deletion in the future.

@Thrillberg @edwinthinks soft-deleting will fix the problem for deleted questions but not for updated ones 🤔 It will be common for people to change the text of a question instead of deleting and creating a new one. Non-tech people won't be aware that responses are linked to questions and changing the question text will change how the old submissions look like. Papertrail is worth researching but it's a big framework and may have its own set of challenges.
But I think we all agree to start with a simple and solid foundation and add this logic later :)

I'm in favor of @Ptrboro's suggestion to cache the original question data over soft delete (because of the update scenario).
I've got this in the wild and there, I've been able to train users to make a new question when the fundamental meaning is changed. I also have a text_override field on FormQuestion so if they want it to display differently on one Form, they can do that without changing the question and we have record of what was on that Form.
But @Ptrboro's solution is both cleaner and more performant.


Ubuntu Trusty version referenced in ubuntu-trusty-64.json is deprecated

The version of Ubuntu coded into the json is ubuntu-14.04-server-amd64.iso which has been removed and replaced with http://releases.ubuntu.com/trusty/ubuntu-14.04.2-server-amd64.iso.
wget http://releases.ubuntu.com/trusty/ubuntu-14.04-server-amd64.iso
--2015-03-29 18:57:45--  http://releases.ubuntu.com/trusty/ubuntu-14.04-server-amd64.iso
Resolving releases.ubuntu.com (releases.ubuntu.com)... <IP_ADDRESS>, 2001:7b8:3:37:213:136:29:219
Connecting to releases.ubuntu.com (releases.ubuntu.com)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2015-03-29 18:57:47 ERROR 404: Not Found.
I have updated the .json file and confirmed that I am able to build an image using packer on Ubuntu 14.0.4.  Using the following command:
packer build ubuntu-trusty-64.json
Added it to the vagrant box list:
vagrant box add lattice/ubuntu-trusty-64 ubuntu-trusty-64.box
Downloading box from URL: file:/home/snoble/lattice/ubuntu-trusty-64.box
Extracting box...te: 1074M/s, Estimated time remaining: --:--:--)
Successfully added box 'lattice/ubuntu-trusty-64' with provider 'virtualbox'!
And after modifying the Vagrantfile vagrant up the image:
root@virtualbox:/home/snoble/lattice# vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
[default] Importing base box 'lattice/ubuntu-trusty-64'...
[default] Matching MAC address for NAT networking...
[default] Setting the name of the VM...
[default] Clearing any previously set forwarded ports...

Hi @sonoble,
Thank you much for this Pull Request. A story has been created in our internal tracking system. I have prioritized it for the team, but since there's some extra work in creating a new image, it's not something we can get to immediately. You can follow our progress there, if you like: https://www.pivotaltracker.com/story/show/91363618
--
Marco Nicosia
Product Manager
Pivotal Software, Inc.

Hi @sonoble,
We've released Version 0.2.5 of Lattice, which has switched the base images to Ubuntu Trusty 64 14.04.2. I've been keeping this issue open until that release.
https://github.com/cloudfoundry-incubator/lattice/releases/tag/v0.2.5
Closing this issue, but please feel free to reopen if the release does not sufficiently address this issue.
--
Marco Nicosia
Product Manager
Pivotal Software, Inc.


Maybe a concise short conclusion?

Hi @ericlee0920, I have added a short conclusion in our report here  Thank you.


Update format Lambda to generate GeoHarvester extract command

Purpose and background context
Update format Lambda function to generate GeoHarvester extract command based on source input variable provided in payload to TIMDEX StepFunction.
For more details, see Confluence documentation: TIMDEX StepFunction Updates | Pipeline Lambdas
How can a reviewer manually see the effects of these changes?

Build the Container
Run the default handler for the container
Open a new terminal and post the following to the container:curl -XPOST "http://localhost:9000/2015-03-31/functions/function/invocations" -d '{"next-step": "extract", "run-date": "2022-03-10T16:30:23Z", "run-type": "daily", "source": "gismit", "verbose": "true"}'

Observe the GeoHarvester extract command in the following output:{"run-date": "2022-03-10", "run-type": "daily", "source": "gismit", "verbose": true, "harvester-type": "geo", "next-step": "transform", "extract": {"extract-command": ["--verbose", "harvest", "--harvest-type=incremental", "--from-date=2022-03-09", "--output-file=s3://timdex-bucket-name/gismit/gismit-2022-03-10-daily-extracted-records-to-index.jsonl", "mit"]}}

Notice that (a) --harvest-type=incremental because run-type=daily and the (b) .jsonl file type appended to the output-file parameter.

Includes new or updated dependencies?
NO
Changes expectations for external applications?
NO
What are the relevant tickets?
https://mitlibraries.atlassian.net/browse/GDT-115
Developer

[x] All new ENV is documented in README
[ ] All new ENV has been added to staging and production environments
[x] All related Jira tickets are linked in commit message(s)
[x] Stakeholder approval has been confirmed (or is not needed)

Code Reviewer(s)

[ ] The commit message is clear and follows our guidelines (not just this PR message)
[ ] There are appropriate tests covering any new functionality
[ ] The provided documentation is sufficient for understanding any new functionality introduced
[x] Any manual tests have been performed and verified
[ ] New dependencies are appropriate or there were no changes

@ghukill and @ehanson8 -- Please see the latest updates to this PR!

Looking good. Proposed one more change, define the source list ["gismit", "gisogm"] as a config-level constasnt, and that can be checked against throughout the code, as opposed to checking against the hardcoded list. And apologies again for not proposing that the first time around.
But, marking this PR as "Comment" because with or without that change, otherwise looks good and approved! Please feel free to merge, from my POV, with or without that change.
Logistically, once this is merged, I'd suggest we keep GDT-114 and GDT-115 open until we run the StepFunction through a few test runs now that most things are in place. We can make sure these two stories are aligned with respect to the StepFunction flow.

Looks as though the deployed version to Dev1 is operating as hoped!

StepFunction execution for gismit / daily, uses the GeoHarvester with correct arguments
StepFunction execution for libguides / daily that correctly invokes the OAIHarvester

@jonavellecuerdo - if and when you merge this PR, from my POV, I think it's probably also safe to also mark GDT-115 as done.

@ghukill and @ehanson8 -- Please see the latest commit, addressing your comments. :)


Improved adaparse documentation + minor changes

-In some cases, adaparse could omit the last line, this PR fixes that.
-We call count less often. Note that there are other possible performance optimization possible.
-I ran some benchmarks against trurl, and I include some documentation in the documentation.
-I propose that when piping a list of URLs through the tool, we only print out the invalid URLs by default. If someone wants to get the href, they call add -g href.
-I have added the href getter
-There is a minor issue (unrelated) in apple_arm_events.h that I try very hard to get fixed...
-In some cases, we would omit flushing the last line of output (when benchmarking).
Rebased version of  https://github.com/ada-url/ada/pull/383

@anonrig This actually requires some attention: please read the documentation as things are changed somewhat.

See
https://github.com/lemire/ada/blob/rebased/docs/cli.md
I did not rename the executable. We can do it but it has to be done rarely.

merging


Added doxygen support and automatic doxygen builds using Travis

Also refactored many comments to agree with doxygen format.

@all-contributors please add @jacobaustin123  for code, design, and documentation


Fix misleading error message.

Changed setVideoFilterComplex to setComplexVideoFilter.
The method setVideoFilterComplex does not exists which misleads developer as he cannot find this method.

Awesome. Thanks!

I can't see setComplexVideoFilter as well.


Remove JVM_ARGS conditional for obsolete Java versions

Resurrecting #21215

Context
Gradle has required Java 8 to run since Gradle 5.0.
Contributor Checklist

[x] Review Contribution Guidelines.
[x] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[x] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
[x] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team.
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective.
[ ] Provide unit tests (under <subproject>/src/test) to verify logic.
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes.
[ ] Ensure that tests pass sanity check: ./gradlew sanityCheck.
[ ] Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest.

Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

We pinged the responsible team to get a status on

https://github.com/gradle/gradle/pull/20054

Thanks - I'll wait to rebase until there's a response.

I think this PR is now obsoleted by #28731.


Tooltip unnecessarily breaks into multiple lines when positioned to the right

A tooltip breaks into multiple lines when it is positioned to the right, even though there is enough space for it to move further to the left. This doesn't happen if it is positioned to the left.
See this example. (Uses #13718.)

Split out from https://github.com/twbs/bootstrap/issues/13902#issuecomment-46882090

Punting as a won't fix—v4 includes a new positioning library for our affix, tooltips, and popovers.


prior art

We all know about CITGM, but are you aware of https://www.npmjs.com/package/fugl ?
Not sure what you want to do with this, but at minimum, it may be helpful in design decisions

There are a couple of other tools listed in https://github.com/nodejs/package-maintenance/issues/84 too.


Limit to format and size files upload

Is your feature request related to a problem? Please describe.
Currently a user could upload any file (.sh, .js, ...) of any size, and break your toy.
As already asked, it would be great to limit type and size.
Describe the solution you'd like
Limit formats using a comma list (enum), and size at file-type field edition.
Bonus: a library to downsize images to a max size.
Describe alternatives you've considered
WP plugin, see https://www.abstractapi.com/guides/best-image-resize-api

docs https://wiki.saltcorn.com/view/ShowPage/files-management

Perfect! Thank you @AleksandrSokolov


Fix the issue where runTest ignores arguments

What changes are proposed in this pull request?
Fix the issue that TestRunner related parameters have no effect.
Why are the changes needed?
Fix the issue that TestRunner related parameters have no effect. #17066
Does this PR introduce any user facing changes?
no

@jiacheliu3 PTAL

alluxio-bot, merge this please


Not gettiing user email information on login failures

Library

[ ] "msal": "^1.4.4",

Framework

React

Description
We are using this library in our react app (ms bot webchat channel). Recently, we have got a requirement to log the user login failure event into application insights and as part of this event, we need to add user email as one of the properties. So that we can cross-check when any customer complains about the login issue.
Error Message
We are actually looking for user email information on login failure.
MSAL Configuration
const loginRequest = {
    scopes: ['openid', 'profile', 'User.Read']
  };

Reproduction steps
Checkout below repo
https://github.com/microsoft/BotFramework-WebChat/tree/master/samples/06.recomposing-ui/a.minimizable-web-chat
Expected behavior
Need user email information on user login failure.
Identity Provider

Azure AD

Browsers/Environment

Chrome
Edge
Safari

Regression

[ ] Did this behavior work before? No
Version:

Security

[ ] Is this issue security related? Yes

Source

[ ] Internal (Microsoft)

Please let us know if you need any further information on this

@SreekanthOAuth The user login failure can happen for varied reasons and we throw back the server error we receive to the user as is. We do not have the info for the user email to send it back to you. Also since this is PII (Personally Identifiable Information) we cannot give the info in our client by default.

@sameerag  - Thanks for the information. We will use the server error in our insights.


The SVGs are not all 24x24

Hey, love this repo! I'm creating a Sketch Library out of all of them, but a thing that gets in the way is that the SVGs are not actually all 24x24px. For example, "assignment_late" is 18x20px in this repo, while the SVG 24 that you download from material.io is actually 24x24px.

It is a normal behavior in Sketch.
All icons are 24x24, but when Sketch imports icon, it ignores bounding box. When you download any icon from material.io, it contains an empty rectangle <path d="M0 0h24v24H0z" fill="none"/> which fixes Sketch behavior.
You can use Iconify plug-in for Sketch to import icons, it will add empty rectangle before importing icon: https://github.com/iconify/iconify-sketch


Create MACHINE LEARNING

DRAGON ESTATE HOUSE PRICE PREDICTION

Title: Boston Housing Data

Sources:
(a) Origin:  This dataset was taken from the StatLib library which is
maintained at Carnegie Mellon University.
(b) Creator:  Harrison, D. and Rubinfeld, D.L. 'Hedonic prices and the
demand for clean air', J. Environ. Economics & Management,
vol.5, 81-102, 1978.
(c) Date: July 7, 1993

Past Usage:

Used in Belsley, Kuh & Welsch, 'Regression diagnostics ...', Wiley,
1980.   N.B. Various transformations are used in the table on
pages 244-261.
Quinlan,R. (1993). Combining Instance-Based and Model-Based Learning.
In Proceedings on the Tenth International Conference of Machine
Learning, 236-243, University of Massachusetts, Amherst. Morgan
Kaufmann.

Relevant Information:
Concerns housing values in suburbs of Boston.

Number of Instances: 506

Number of Attributes: 13 continuous attributes (including "class"
attribute "MEDV"), 1 binary-valued attribute.

Attribute Information:

CRIM      per capita crime rate by town
ZN        proportion of residential land zoned for lots over
25,000 sq.ft.
INDUS     proportion of non-retail business acres per town
CHAS      Charles River dummy variable (= 1 if tract bounds
river; 0 otherwise)
NOX       nitric oxides concentration (parts per 10 million)
RM        average number of rooms per dwelling
AGE       proportion of owner-occupied units built prior to 1940
DIS       weighted distances to five Boston employment centres
RAD       index of accessibility to radial highways
TAX      full-value property-tax rate per $10,000
PTRATIO  pupil-teacher ratio by town
B        1000(Bk - 0.63)^2 where Bk is the proportion of blacks
by town
LSTAT    % lower status of the population
MEDV     Median value of owner-occupied homes in $1000's

Missing Attribute Values:  None.

@patrasoumyaranjan1999 ?????

Thanks for opening this pull request! Please check out our contributing guidelines and make sure to follow the pull request template.

Yes


Dynamically create own SVG tree.

Hi,
I am using usvg as an intermediate representation of an image data. In version 0.39, I was able to dynamically create a tree and then render it. Is it still possible to do this with the current API? It seems that now I cannot now create own of tree nodes outside of usvg crate.

It's not possible anymore. See #710.

Thank you.

You're suppose to use tiny-skia directly. Creating usvg::Tree by hand and passing it to resvg would be way slower.

I actually used this mainly for creating PDF; I built a usvg tree and then render it via svg2pdf. Therefore, the correct way for me is to probably directly use pdf-writer. Now I will need two renderers, one via tiny skia and one trough pdf-writer, but I understand your decision.

Writing a renderer from scratch with pdf-writer will be a pain... You will probably have an easier time if you instead construct an SVG string and convert that. This is still more inconvenient than constructing the tree directly, but definitely less inconvenient then maintaining two rendering backends.


Changes to sd.output since samediff handles sessions internally

Change samediff runner to use Change to sd.output(..) instead of inferencesession directly due to performance reasons.

@quickwritereader


Reactive inputs?

First off, thank you @ wobsoriano for the awesome module!
Is there support for passing reactive inputs?
Calling refresh() does not bust the cache regardless of the internal state of the userId ref
const { data, pending, error, refresh } = await useAsyncQuery(
  ['getUser', { name: userId.value }],
  {
    lazy: false,
  }
);

With the native useFetch we use a () => on the url to keep the URL params reactive on calling refresh()
Is there something similar we can do with useAsyncQuery to keep the input parameters reactive?
This reactivity would help greatly with pagination flavored use-cases.
Reproduction link:
https://stackblitz.com/edit/github-mj8gus?file=server%2Ftrpc%2Findex.ts,app.vue
Any assistance would be greatly appreciated.

Hi! Please use v0.4.x of trpc-nuxt and feel free to create your own composables 😄


better organization of Graphics

We will soon have LineCollection so we should probably add a class attribute to each Graphic subclass which is used by Plot when attaching all the graphic names as methods, since we'd want plot.line_collection() rather than plot.linecollection() and it maintains pep8 standards
It would be useful for Subplot.get_graphics() to return a dict instead of a list, where the keys are the object class.
example:

from fastlotlib.graphics import ImageGraphic

graphics_in_subplot = gp[0, 0].get_graphics()

graphics_in_subplot[ImageGraphic] # list of all `ImageGraphic` graphic instances within the subplot

@clewis7 thoughts?

I like this idea! I can work on making Subplot.get_graphics() return a dict instead of a list

I think it'd be useful to use the init_subclass to parse Graphic class names automatically and set it as a class attribute that can be used for this purpose, but also for attaching the various add_graphic-name methods, so we can have this parsing code in just one place.
This would also make it so that the dict keys for this PR are str, I think str is better since then the user doesn't need another set of import statements for graphic objects.

printing it out like a table or just with nice tabspacing would be nice:
images:
  "image-name-a" <mem location etc...>
line_collection:
  "lc-A" <n-items>, ...


panos_nat_rule_group documentation and device_group missing from example

Documentation link
https://registry.terraform.io/providers/PaloAltoNetworks/panos/latest/docs/resources/nat_rule_group

Describe the problem
The documentation does not explain where the device_group statement is supposed to be used nor show it in the example.
Terraform also throws the following error when used in the code:
Error: Unsupported argument
│
│   on natrules.tf line 2, in resource "panos_nat_rule_group" "bottom":
│    2:     device_group = "${panos_device_group.create_eu_device_group.id}"
│
│ An argument named "device_group" is not expected here.

Suggested fix

This is not a documentation issue, there simply just is not an option to specify a device group on a nat rule
This should be classed as a bug

@denwurm Hi, wondering if you ever found a resolution for this? Running into the same issue. Thanks

@denwurm - at this point, my suggestion is

Don't use the Palo Alto TF provider.  I haven't seen any action on this since 2022, feels like a developer left.  Dead product?  In my opinion, there are fundamentally required objects missing.  No DHCP capability?  No DNS Proxy capability?  Even more missing for Panorama.
If you absolutely must use TF - I ended up using the deprecated "panos_nat_rule" resource instead.  It is deprecated, but since I am not seeing any development occurring on this TF provider, I don't think that matters anyway.  Maybe they will get this resource working one day and you can migrate it.

@ganderson-rw @denwurm
According to contacts within Palo Alto, this provider is abandoned.  Apparently their teams are completely rewriting the Golang SDK for it and once complete, they will begin development of a completely new provider.  I wouldn't expect anything new before the middle of next year.
Take this with a grain of salt as this is word of mouth.  The lack of official communication on this to the community is disappointing.


chore: Upgrade actions/cache to v2.1.3

Why:
New version was released to fix some minor issues and resolve a dependency that had a CVE (but wasn't directly affected) https://github.com/actions/cache/releases/tag/v2.1.3
What's being changed:
Hashes used by the CI jobs and test
Check off the following:

[x] All of the tests are passing.
[x] I have reviewed my changes in staging.
[x] For content changes, I have reviewed the localization checklist
[x] For content changes, I have reviewed the Content style guide for GitHub Docs.

@chiedo this might address the occasional timeout issues with uploading the cache

🤞🏿


Fill in Documentation

Many of the components are not yet documented.
If you would like to help out, as you get familiar with Scenic, please pick a module that needs documentation. Submit an issue here to claim that you are working on it, then go for it.
I will be working on as many of these (and the guides) as I can over the next few weeks. There is still quite a bit tho.

Hey @boydm. Let me take this opportunity to thank you for the amazing work and effort you put into bringing this awesomeness, really appreciated!
I just found a dead link in the "General Overview" to the "Scene Overview" but I think it's probably to Structure of a Scene? If this is correct and you want me to fix it no worries.

0.9.0 Will have a lot of improvements in Documentation

I think this is pretty much done in v0.11


Refactor build system

Refactor the build system to make support for other distributions and systems easier. Also the current scripts are too messy.

Started in 52a73685ff236ae884611fa2c7884d43e63f7129. The framework of it is pretty much done as of now, but it may continue to evolve.


Add AKS cluster resources lack of visibility to the list of considerations

Similarly to the AppGW backend health, when you have a read-only lock on an AKS cluster, you are unable to see any cluster resources from the "Kubernetes Resources" section on the AKS cluster left-side blade.
This is because you need to perform an authentication to access the data which uses a POST that is blocked by the lock and resulting on a permissions error content blade.
Please add this limitation to the list under: #considerations-before-applying-locks

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

ID: 4e7af209-7240-dd2a-7130-e7fb3143986a
Version Independent ID: a653b0d1-877d-09f7-17fa-11bf06c37cc9
Content: Lock resources to prevent changes - Azure Resource Manager
Content Source: articles/azure-resource-manager/management/lock-resources.md
Service: azure-resource-manager
Sub-service: management
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

I have verified this behavior and created a PR internally for review.

Since, it is taking longer than expected. I will close this issue for now and will update the thread once the PR gets merged.


Carbon registry usage removal from the XACML

Is your feature request related to a problem? Please describe.
The XACML feature of the Identity Server currently uses the Registry as its storage repository, which is a roadblock to the plan to remove the Registry from the Identity Server.
This is part of the larger effort to remove the Registry from the Identity Server, which will help lower operational and product maintenance costs.
Describe the solution you would prefer
Need to find an alternative solution for managing XACML policies that doesn’t depend on the Registry.
This issue will track the progress of the registry usage removal from the XACML feature.
Additional context
Registry removal parent issue: Remove carbon registry usages in IS

With the recent efforts to incorporate unit tests into the XACML component, we have successfully added unit tests for the newly introduced persistence package. As a result, unit test coverage for each class within this package has now surpassed 80% coverage.

Unit Test Related PRs

https://github.com/wso2/carbon-identity-framework/pull/5883
https://github.com/wso2/carbon-identity-framework/pull/5905
https://github.com/wso2/carbon-identity-framework/pull/5931
https://github.com/wso2/carbon-identity-framework/pull/5943
https://github.com/wso2/carbon-identity-framework/pull/5945
https://github.com/wso2/carbon-identity-framework/pull/5949
https://github.com/wso2/carbon-identity-framework/pull/5950
https://github.com/wso2/carbon-identity-framework/pull/5952
https://github.com/wso2/carbon-identity-framework/pull/5953
https://github.com/wso2/carbon-identity-framework/pull/5955
https://github.com/wso2/carbon-identity-framework/pull/5956
https://github.com/wso2/carbon-identity-framework/pull/5962
https://github.com/wso2/carbon-identity-framework/pull/5964
https://github.com/wso2/carbon-identity-framework/pull/5965


Add templates

Fixes #175

@AnshulMalik @vaibhavsingh97 Please review

@S2606 I am quite late to approve 😅


refactor(headers): Add encode_headers() function

The HTTP headers block is not always a valid UTF-8 string, so it makes no sense to
implement the Display trait for it (additionally Display is intended for humans
and HTTP header blocks clearly are not). Instead the headers should be encoded as
a byte stream.
Removed a few tests, since they do not work without Display.
Remark: Currently formatted headers can't contain invalid chars, another commit
will enable this.
BREAKING CHANGE: fmt::Display is no longer implemented for Headers.

The main point is that to you, implementing fmt::Display for Headers seems wrong, since Headers doesn't always contain UTF-8? This may be true, but I'd like to see farther into the design of how to support non-UTF-8 printing before making a merge like this.

No problem, here is the design in short form:

HeaderFormat gets removed, it is replaced with EncodeHeader, providing the encode_header() method returning a Vec<Vec<u8>>. Allowing multiple lines fixes #80. Using Vec<u8> allows us to encode non-ASCII headers, this is at least useful for Cookie, Set-Cookie, ETag, all other headers using entity tags and maybe some more.
Raw headers are also encoded as Vec<Vec<u8>>
An encode_headers() function is used to encode Headers for HTTP/1.x, for HTTP/2 a hpack should be used
All types representing headers stop implementing Display since they may contain non-ASCII data.

@seanmonstar would you prefer to merge the current code or should I implement the complete design first and land one huge PR?

The idea makes a fair amount of sense. I'll recap:

Headers from new Clients and Servers today should use only ASCII.
Some existing implementations may exist that use non-ASCII headers.
When writing Headers in hyper, we 99% of the time writing explicit Headers set by the user, and they should know better to use ASCII.
When we receive Headers, it's not a requirement that they be in ASCII. It is possible to inspect non-ASCII headers via the raw representation.
The only time we should be needing to write back out non-ASCII headers is in proxying situations: The proxy has received some headers that include non-ASCII, and we must write the Header exactly as we received it, not losing data.
Because of this 1 scenario, we cannot use fmt::Display to do so, since that library type is required to output UTF-8 Strings; the header could be any encoding.

One thing I'd like to solve in this proposed design is encoding to Vec<Vec<u8>>. This means 2 allocations for every header, that will be promptly thrown away. Perhaps we could pass a &mut std::io::Write or something. Most Headers could continue to use write!(wrt, "{}", self), since std::io::Write includes a write_fmt method. The few outliers could use write(&[u8]).

Good summary.
There is a scenario two, where a website provides cookie values or entity tags containing non-ASCII data that should be send back to the website in another request.
We cannot simply pass &mut std::io::Write to an encode_headers function since we need to be able to serialize a header into multiple values at least for the Set-Cookie header and for better compression in HTTP/2. So we would need an iterator. The iterator would yield elements that have an encode() method taking &mut std::io::Write. I do not think that using iterators is any faster since you need also many allocations.

Reem and I were just talking about this last night, and I want to press on
it. Still trying to think of a good way to handle Set-Cookie.
On Sat, May 16, 2015, 4:02 AM Pyfisch<EMAIL_ADDRESS>wrote:

Closed #442 https://github.com/hyperium/hyper/pull/442.
—
Reply to this email directly or view it on GitHub
https://github.com/hyperium/hyper/pull/442#event-306438577.


Limit channel-creation count from the UI

Issue
Closes #534 prevent new channel creation over x channels
I assume this is just meant as a UI thing to cover the majority of cases, and doesn't completely prevent the creation since one could send the API call separately.
Notes

Disabled the channel-creation page in this scenario, with a text explaining why.
Also handled at the API call (doCreateChannel) in case there are other UI components that create channels.

--- Draft ---
Ah, I forgot to exclude yt channels ...

Ready for review

Exclude YTs from channel_list when getting current channel count.
[ ] I don't have YT channels to test for sure, so please test if possible.


Fix to find the correct alarm entries -- the name changed in recent b…

…uilds.

HI @anunayaabb,
Thanks for proposing the pull request. However, I don't see any elements name change between the 2 versions. Is there any AlarmClockTest scenario that fails and requires this fix? It would be great if you can provide the Windows 10 version you are using.

Invalid due to being outdated and not relevant to current state of samples.


Title Template Property

Context
Based on https://github.com/Everduin94/better-commits/discussions/69
Today, although each property is optional, the order in the title is fixed to match conventional commits.
TYPE(SCOPE): TICKET DESCRIPTION
Tasks
Create a property title_template

Default: type(scope): ticket description

Zod Validation

Enforce key words: ["type", "scope", "ticket", "description"]
Enforce separators: ["/", "-", "_", "[]", "()", ":", "{}"]

Regex

Update string builder to use template

Concerns

More difficult to enforce things like "if () is empty remove, if no text before colon then remove colon" etc...

Outstanding Tasks

This will effectively make fields like optional or separator redundant in some cases. Should we deprecate?
We may want to add some way to add custom fields / prompts

Closing. See https://github.com/Everduin94/better-commits/pull/77
Solves most common situations with existing code.


fix: update lesson to reflect changes in UI and in number of the repos (upstream branch)

Closes https://github.com/apify/apify-docs/pull/1108. It's the same PR, but from an upstream branch, not from my fork. As discussed on Slack, this works around unauthorized npm token on CI.

@TC-MO The original PR is already reviewed and approved twice, I'd merge this right away, but the repo rules require me to obtain an approving review nevertheless. Would you please rubber-stamp this?

Interestingly, GitHub picked up a push to this branch and ran CI on the original branch, resulting in all green under the previous PR 🤯

So I merged https://github.com/apify/apify-docs/pull/1108 and I'll close this one. Sorry for all the buzz!


Health inspection no longer being supplied? Change in API?

Version of the custom_component
Happening in both v<IP_ADDRESS> and v0.0.13
Installation method (hacs / manual)
hacs
Installation method of hass (venv, docker, hassio,...)
docker
Configuration
NA
Describe the bug
Health Inspection sensor simply vanished from 2 different HA instances with different custom component versions v<IP_ADDRESS> and v0.0.13 (hence also different versions of the underlying library - v0.50.1 and 0.47.1).
That seems to make me suspect that there might have been a change in the API, considering that the sensor became unavailable in both HA instances at the same time.
Running weconnect-cli seems to still bring the information, not sure about format or placement in terms of "hierarchy", compared to before.
As weconnect-cli is also based in the library and it seems to work, anything else that can be checked before reporting it in the library?

Debug log
NA

@tillsteinbach Are you aware of any issues with Health Inspection data from the API. @mitch-dc In a new installation of the custom component, sensor is not even generated automatically.

I removed it because it stopped working. Do you need it?

I removed it because it stopped working. Do you need it?

Considering this is information that appears in the We Connect app and in theory is provided via API, I would say we should keep it, no?

On what software is that car?
Mine is on 3.0.

If it's different between the software versions we need to check all the values

On what software is that car? Mine is on 3.0.

3.1.0


create domain art.edu for Academy of Art University student emails

student emails for Academy of Art University
https://www.academyart.edu/
phone: +1<PHONE_NUMBER>

@muteshev Thank you for your patience while waiting for a review and processing your request. Pull request merged. Please start applying for JetBrains educational subscription at https://www.jetbrains.com/shop/eform/students in an hour, to allow the changes to propagate through JetBrains systems.

thanks, it works.


Create intermediate symlink for switching between build and launch modules

Summary

Avoids changing /workspace permissions, creating instead a symlink in /tmp which points to build modules during build and launch modules at launch. The /tmp symlink is pointed to by the node_modules symlink in /workspace (i.e. /workspace/node_modules -> /tmp/node_modules -> {build, launch}-modules layer).
The exec.d script is now only run when node_modules is required for both build and launch.
Use Cases

This should resolve https://github.com/paketo-buildpacks/nodejs/issues/602, while still conforming to the Secure Runtime RFC requirements.
Checklist

[ ] I have viewed, signed, and submitted the Contributor License Agreement.
[ ] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[ ] I have added an integration test, if necessary.
[ ] I have reviewed the styleguide for guidance on my code quality.
[ ] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

It's worth capturing here that Angular apps have been observed to fail on stacks with distinct build and run uids as the CLI attempts to create/modify a cache in /workspace. This can be rectified by setting the cache path in the project's configuration (angular.json).

The exec.d script is now only run when node_modules is required for both build and launch.
@thitch97 Can you explain this choice? What happens if only launch is specified?

Can you explain this choice? What happens if only launch is specified?

@ryanmoran My thinking here is that if the setup-symlinks exec.d script is solely responsible for ensuring that /workspace/node_modules eventually points to /layers/.../launch-modules/node_modules instead of /layers/.../build-modules/node_modules, then there should be no need to run it if only build OR launch is specified. If only launch is specified, for example, /workspace/node_modules will already point to /layers/.../launch-modules/node_modules at runtime (the build-modules layer wouldn't even exist).


Update README.md

fix broken links for new users

🚨 IMPORTANT: Please do not create a Pull Request without creating an issue first.
Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of
the pull request.
Description
Proposed changes for resolving new host and URIs for new users looking for documentation.
Fixes #7663
Type of change
Please delete options that are not relevant.

[X] Bug fix (non-breaking change which fixes an issue)
[X] This change requires a documentation update

Screenshots/Sandbox (if appropriate/relevant):

How Has This Been Tested?

New host and URI were updated in the README
Followed the links in the markdown preview to verify they arrive at the appropriate pages as suggested by their names

Test Environment:

web browser

Checklist:

[X] I have followed the
CONTRIBUTING doc and the
style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[X] I have added tests that prove my fix is effective or that my feature works, and I have added a
changeset using yarn changeset that bumps the version
[X] New and existing unit tests and linter rules pass locally with my changes
[X] Any dependent changes have been merged and published in downstream modules

Further comments
Thank you!

Thanks 🙏


No documentation for how to connect an Echo to this

Is it possible to update the README with some documentation on how to connect your echo to it? Even if it's just a link to relevant docs, it'd be super helpful :)

I am pretty sure this isn't meant to be used with a physical device. It is really just a local simulator. The following is from the readme file:

"The server can also serve static web site content, and offers a built-in Alexa App debugger/simulator. This allows you to test your skill using a web browser and view the responses, without actually using the Echo."

Hope this helps.

There is a tutorial series which uses this for the TDD, and the end result is a deployed skill.
part 1
I hope this helps

I have a live skill in the Amazon store served by this. It's been possible since we added support for the amazon verifier.

So do we need to setup a cert and start it as https and use that URL in alexa dev section?

+1 on documentation, PRs welcome

Thanks for all the info on this. It's super helpful :) :)

@TomMettam how'd you get your skill to pass verification?  We've got open issues with setting the verify flag to true causing the skill to timeout. se: #52 #50

@cpup22 : Unfortunately there has been a regression somewhere in this repo - the functionality is broken. However, I'm maintaining a working repo at https://github.com/CasperTech/alexa-app-server which has passed certification.

We're going to sort all this out, with tests so we don't reintroduce regressions. @TomMettam if you have time see comments on #52, and give more recent code a try.

dblock: I'm very sorry but at the moment I don't have time to write tests for this - i'm busy with work at the minute.

I've documented how to run alexa-app-server in production in https://github.com/alexa-js/alexa-app-server/pull/69, please make improvements/suggestions.

:dancer:


Feature/add autorization rules

Hi, 👋
In this branch, we have :
NOTICE:
I DON'T HAVE TEAM OR CODING PARTNERS (Members). below is the screenshot of the Email sent to me by the students success and dashboard.

Installed CanCanCan in my project.
Added a role column to the users' table. Used a migration for this.
A user can delete a post if it is theirs or if they have an admin role (column role has value "admin"). Use CanCanCan for this authorization.
For this, we implemented the post-deleting functionality. Added the "Delete" button to the view and make sure that only authorized users can see it.
A user can delete a comment if it is theirs or if they have an admin role (column role has value "admin"). Used CanCanCan for this authorization.
For this, we implemented the comment-deleting functionality. Add the "Delete" button to the view and make sure that only authorized users can see it.

Hi @maths29, I am trying to run your project but I am experiencing this error when running migrations