BOOST_JSON_STANDALONE results in undefined references to destructors

Fedora 33 / GCC 10.2.1 C++20 / Conan Boost 1.75 2d040665a7cb2820e00fe685a77c8169fcc3b764
When compiling with BOOST_JSON_STANDALONE, linker errors appear with an undefined reference to ~value(). As I understand it, there is no need to link libboost_json.a when standalone mode is enabled. I tried to link it as well anyway and the result is the same.
I have been able to trim it down to the following test case:
#include <boost/json.hpp>

int main() {
    boost::json::value v{};
    return 0;
}

It results in the following linker error:
/usr/bin/ld: CMakeFiles/json-standalone.dir/JsonStandalone.cxx.o: in function `main':
/root/test-cases/JsonStandalone.cxx:4: undefined reference to `boost::json::standalone::value::~value()'
collect2: error: ld returned 1 exit status

I have also tried compiling it directly and it results in the same error:
bash-5.0# g++ -std=c++20 -I/root/.conan/data/boost/1.75.0/_/_/package/2d040665a7cb2820e00fe685a77c8169fcc3b764/include -DBOOST_JSON_STANDALONE JsonStandalone.cxx
/usr/bin/ld: /tmp/ccDoEwjC.o: in function `main':
JsonStandalone.cxx:(.text+0x22): undefined reference to `boost::json::standalone::value::~value()'
collect2: error: ld returned 1 exit status

Why do you think there is no need to link to a library? You still need to link to a version of the library built using the stand-alone mode. Note that standalone is not a Boost feature so you would have to build the library yourself. Alternatively you could use the header-only mode (which can also work with standalone). See:
https://www.boost.org/doc/libs/develop/libs/json/doc/html/json/overview.html#json.overview.requirements.header_only

Why do you think there is no need to link to a library? You still need to link to a version of the library built using the stand-alone mode. Note that standalone is not a Boost feature so you would have to build the library yourself. Alternatively you could use the header-only mode (which can also work with standalone). See:
https://www.boost.org/doc/libs/develop/libs/json/doc/html/json/overview.html#json.overview.requirements.header_only

Ah... my bad. I missed that part of the documentation. It looks like the library I was linking is not built for standalone. Including boost/json/src.hpp resolved the linker problem.

Ah... my bad. I missed that part of the documentation. It looks like the library I was linking is not built for standalone. Including boost/json/src.hpp resolved the linker problem.


Add parameter for changing between testnet and devnet in e2e tests

Please check if the PR fulfills these requirements

[ ] The formatter, linter, and tests all run without an error
[ ] Tests for the changes have been added (for bug fixes/features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Added a --net parameter to e2e tests that allows changing between running tests on "devnet" and "testnet".
Will require further verification as running tests on testnet is super slow.

What is the current behavior? (You can also link to an open issue here)

Test can only be run on devnet
What is the new behavior (if this is a feature change)?
Test can be run on devnet and testnet
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No

We should probably also add a option (perhaps a pytest mark) for some test to be run only on devnet/testnet


Bug in .hh generated files from .msg

@ClarkTucker I'm trying to build the rmw layer for CoreDX following your update to Dashing.
The build breaks on rosidl_generator_py for coredx in the following files:
build/rosidl_generator_py/rosidl_typesupport_coredx_cpp/rosidl_generator_py/msg/Constants_.hh in line 47 static const fixedstring3_t const FOO_ = "foo";
build/test_msgs/rosidl_typesupport_coredx_cpp/test_msgs/msg/Strings_.hh in line 43 static const fixedstring12_t const STRING_CONST_ = "Hello world!";
the problem is the duplication of const. Can you check in the CoreDX ddl generator?
Thanks!

I'm seeing this also with coredx 4.4.0 and 4.7.0. Both on linux x86_64.
I also had to add some headers:

rmw_set_log_severity.cpp needed rmw/error_handling.h and rmw/rmw.h
rmw_publishers_allocation.cpp needed rmw/error_handling.h
rmw_subscription_allocation.cpp needed rmw/error_handling.h


Error "./start.sh: 43: [[: not found" on WSL

Running sh ./start.sh on WSL leads to an error:
RESET_PIPELINES_DIR is not set to true. No action taken.
./start.sh: 43: [[: not found
PIPELINES_REQUIREMENTS_PATH not specified. Skipping installation of requirements.
./start.sh: 116: Syntax error: redirection unexpected

The key here is the [[: not found error, which is caused by sh not understanding [[ in the .sh file.
Running the file with bash ./start.sh works, so there's an easy workaround available, but I'm documenting this here in case someone else encounters the same problem.

Thank you


It is not possible to debug by adb network

Godot version: v3.1.alpha.official
OS/device: OSX/Android Export
Issue description:
It is not possible to debug by adb network, I have already activated the corresponding checks but the phone does not connect to the godot debug server so I can not hear prints, errors or any other activity in the output console
Minimal reproduction project:
print("Hello")

fixed in higher versions

fixed in higher versions


[fix] Placeholder text

Quick fix for the issue raised in #22. Looks likewithExamplePlaceholder overwrites the placeholder when called after the placeholder is initially set. I don't know if I'd qualify this as a true fix, but it definitely gets the job done for scenarios both with and without placeholder text.

@benjaminsage @MojtabaHs @AlexFine it'd be nice if I could get a merge off one of y'all here.

Thanks @AlexFine, I just don't have write access to the repo. So I dunno if the merge button is showing up for you or anything, but that's all we need to wrap this up!

Hi all- how do I get this fix in my version through Xcode / SPM? I'm trying to use this currently in a SwiftUI project and, while the field itself works flawlessly for formatting phone numbers, the placeholder text is conspicuously absent.

I have the fix in my fork if you'd like to use that:
https://github.com/smakus/iPhoneNumberField
On Fri, Apr 30, 2021 at 10:25 PM logankriete @.***>
wrote:

Hi all- how do I get this fix in my version through Xcode / SPM? I'm
trying to use this currently in a SwiftUI project and, while the field
itself works flawlessly for formatting phone numbers, the placeholder text
is conspicuously absent.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/MojtabaHs/iPhoneNumberField/pull/25#issuecomment-830544128,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAS75DGFHXZFSQFJBV4YI3LTLOGDLANCNFSM4ZIGKY3A
.

Thank you!! I’ve been tearing my hair out for an hour trying to figure this out. Much appreciated!

On Apr 30, 2021, at 10:28 PM, smakus @.***> wrote:
I have the fix in my fork if you'd like to use that:
https://github.com/smakus/iPhoneNumberField
On Fri, Apr 30, 2021 at 10:25 PM logankriete @.***>
wrote:

Hi all- how do I get this fix in my version through Xcode / SPM? I'm
trying to use this currently in a SwiftUI project and, while the field
itself works flawlessly for formatting phone numbers, the placeholder text
is conspicuously absent.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/MojtabaHs/iPhoneNumberField/pull/25#issuecomment-830544128,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAS75DGFHXZFSQFJBV4YI3LTLOGDLANCNFSM4ZIGKY3A
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/MojtabaHs/iPhoneNumberField/pull/25#issuecomment-830545605, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABHE22XPBKSOTAYKWCWASHDTLOGPXANCNFSM4ZIGKY3A.

I'm still running into this missing placeholder issue.  How do I pull the correct version?

I would use the version the other person suggested
Sent from my iPhone

On May 23, 2021, at 1:29 PM, JohnOHFS @.***> wrote:

I'm still running into this missing placeholder issue. How do I pull the correct version?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.


Safelinks url issue in Outlook email

We are currently doing some tests and receiving emails in our Outlook but some reason, one of the emails is coming up with an issue.
When the mouse is hovered on top of either a button or a picture in the email, no url is being displayed where as the other email is fine and we can see the URLs.
I've already added both the URLs in the SafeLinks option (Do not rewrite the following URLs in email) but still the same issue.
Not sure where to check further or if there is a bug.
Kindly help me out.
Awaiting for your reply,

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

ID: e6524290-9545-28fc-9cae-5c4a540ad526
Version Independent ID: e6524290-9545-28fc-9cae-5c4a540ad526
Content: Complete Safe Links overview for Microsoft Defender for Office 365 - Office 365
Content Source: microsoft-365/security/office-365-security/safe-links-about.md
Service: microsoft-365-security
Sub-service: mdo
GitHub Login: @chrisda
Microsoft Alias: chrisda

Closing due to lack of response.
Thanks for the feedback.


includeTestsWithTags doesn't respect includeTestsFromTemplates

OpenTest version 1.3.8
Steps to reproduce:

Create a base template base_template.yaml:

sessionLabel: Dummy session
maxIterations: 2
tests:
  - name: dummy_test_pass
    path: unit-tests/dummy

  - name: dummy_test_pass2
    path: unit-tests/dummy

Add some tag to dummy_test_pass2:
tags: [someTag]

Create a new template and inherit the base template child_template.yaml. Note the negation of the tag "!someTag":

sessionLabel: Dummy session
maxIterations: 2
includeTestsWithTags: (!someTag)

includeTestsFromTemplates:
  - name: base_test_template
    path: .

Run the new template => Result is that the includeTestsWithTags: (!someTag) is applied to ALL existing tests in repo instead of the ones defined in the parent template, i.e. ALL tests in repo are executed except the one containing the someTag tag

It sounds like the behavior you are describing is the one that should be expected. The logic for computing the list of tests for the parent template goes something like this:

Start with the tests listed in the tests property (if any).
Compute the list(s) of tests that are matching the expression in the includeTestsWithTags property (if any).
Compute the list(s) of tests for each one of the templates listed in includeTestsFromTemplates (if any).

Compute the union of all tests from points 1, 2 and 3 and that will give you the final list of tests to run.
So based on the above logic it results that whatever tests are matched by the includeTestsWithTags: (!someTag) expression, they will surely appear in the final list of tests for this template, regardless of anything else that might be happening in other parts of the template. The only way the other parts of the template could influence the result is by including some of the tests that don't match the expression !someTag. I hope that makes sense.

Hi @adrianth ,
I am very confused.
What I am expecting is that the includeTestsFromTemplates + tests should be the pool of tests from which we will filter the final list according to includeTestsWithTags.
Did I understand you correctly that it is expected for includeTestsWithTags to add tests from whole repo even though my child_template includes only the tests defined in base_template?

What I am expecting is that the includeTestsFromTemplates + tests should be the pool of tests from which we will filter the final list according to includeTestsWithTags.

That is not accurate. The final list of tests is going to be the union (not intersection - which is what you are describing) of the three lists of tests identified by tests, includeTestsWithTags and includeTestsFromTemplates. Typically, parent templates that use includeTestsFromTemplates don't need to populate anything in their tests and includeTestsWithTags properties and they will rely exclusively on the child templates to bring in the lists of tests. This is actually kind of a best practice which ensures that parent templates only act as "aggregators" of other templates. I can see how this can become confusing.

I still don't understand - what is the point of parent templates aggregation, if when I use includeTestsWithTags in the child it will not respect the parents scope of tests?
It is just simpler to create templates based on includeTestsWithTags only and never use includeTestsWithTags, isn't it?

It is just simpler to create templates based on includeTestsWithTags only and never use includeTestsFromTemplates, isn't it?

I agree. The tag-based approach works best in the vast majority of scenarios. You could probably be able to only ever use includeTestsWithTags in your templates. The includeTestsFromTemplates comes in handy when you need to combine multiple test suites. For example, you could have something like this:
# Child template 1
sessionLabel: Run feature1 tests
includeTestsWithTags: feature1

# Child template 2
sessionLabel: Run feature2 tests
includeTestsWithTags: feature2

# Parent template
sessionLabel: Test all features
includeTestsFromTemplates:
    - name: feature1
      path: .
    - name: feature2
      path: .

The parent template could also be built based on tags by using includeTestsWithTags: feature1 || feature2. However, using includeTestsFromTemplates is probably the better choice because it delegates the test selection to those child templates, so if the child templates were to change, the parent template would automatically reflect those changes. This is useful when - for example - each child template is maintained by a different team.


Exporting Null Values from BigQuery using Nodejs

Hi Team,
While using exporting bq data to json file using nodejs  I am unable to get null values from bq in json file. All fields whose values are null does get exported.
I am using this link for code -https://cloud.google.com/bigquery/docs/exporting-data#exporting_table_data
Is it possible to get this feature with enable and disable option for extracting null values?
There are many systems which are not able to handle missing key:value while importing using json format.
It will really help!!

@mayanksharma1202 that's a limitation on the BigQuery backend size. nothing that we can do to improve that on the client library side.


Add initial elm project

Issues

https://github.com/TransSponsor/trans-sponsor/issues/2

Changes

Add /app directory with basic Elm setup.

NOTE: Doesn't add tests. Won't bother with those until the first feature.

@blad @sethetter @kaylah

:+1:


powershell error

[[

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
OS Version:

Steps to Reproduce:

https://github.com/PowerShell/PowerShell/issues/15426#issuecomment-1118175067
https://github.com/PowerShell/PowerShell/issues/15426#issuecomment-111838749

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines.
Happy Coding!


Don't fetch tags when the plan is cached

For example when running cow release:changelog it will say:
[plan] Loading cached release plan from prior session

At this stage if the release plan is cached perhaps we can skip fetching tags to save time...?

It looks like this might also be happening when you change the version for a package in the plan

Even a --no-fetch-tags option would be useful I think

I've made a PR at #98 to allow us to skip fetching if we want to


None -> nil?

Would it make sense to convert None passed as a Python method param into nil? Is there some unobvious caveat that makes this nontrivial?

Its not a deliberate design decision; I just never encountered the requirement.  It sounds like there should be no reason why it shouldnt be possible.


When PaymentGateway does not return success raise an exception

Related Sentry error:
https://mit-office-of-digital-learning.sentry.io/issues/3915111706/?environment=production&project=5864687&query=is%3Aunresolved+set_rollback()&referrer=issue-stream&statsPeriod=14d
Currently when PaymentGateway does not raise an exception we just log an error and rollback the refund manually: here
Instead we want to throw an error and show the error message.

@annagav was this an error on payment, or an error on a refund?


[go_router] Route not found when registering child route inside ShellRoute's route

Steps to Reproduce

Execute flutter run on the code sample
Click on the button to navigate to child route

Expected results:
Router should push the child route page
Actual results:
Redirected to Page Not Found page

Code sample
import 'package:flutter/material.dart';
import 'package:go_router/go_router.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  final router = GoRouter(
    initialLocation: '/',
    debugLogDiagnostics: true,
    routes: [
      ShellRoute(
        builder: (context, state, child) => Scaffold(body: child),
        routes: [
          GoRoute(
            path: '/',
            builder: (context, state) => const Page1(),
            routes: [
              GoRoute(
                path: 'child',
                builder: (context, state) => const Page1Child(),
              ),
            ],
          )
        ],
      )
    ],
  );

  MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp.router(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      routerConfig: router,
    );
  }
}

class Page1 extends StatelessWidget {
  const Page1({super.key});

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Center(
        child: MaterialButton(
          color: Colors.blue,
          onPressed: () {
            context.go('child');
          },
          child: const Center(
            child: Text("Go to child route"),
          ),
        ),
      ),
    );
  }
}

class Page1Child extends StatelessWidget {
  const Page1Child({super.key});

  @override
  Widget build(BuildContext context) {
    return const Scaffold(
      body: Center(
        child: Text("Page 1 child"),
      ),
    );
  }
}

Logs

[GoRouter] Full paths for routes:
[GoRouter] setting initial location /
[GoRouter] Using MaterialApp configuration
[GoRouter] going to child
[GoRouter] No initial matches: child

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.7.3, on macOS 13.2 22D49 darwin-arm64 (Rosetta),
    locale en-ID)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.1)
[✓] VS Code (version 1.76.0)
Scanning for devices is taking a long time...[✓] Connected device (4 available)
[✓] HTTP Host Availability

• No issues found!

Oh actually, I should've called parent's route + child's route, so in this case context.go('/child')


Support email address missing from tax form message.

The last line here should be "please contact<EMAIL_ADDRESS>but it's missing.

The link is indeed there in the code but not rendering for some reason:
https://github.com/opencollective/opencollective-frontend/blob/master/components/expenses/ExpenseNeedsTaxFormMessage.js
Maybe the reason is obvious for you @Betree ?

@znarf This one is only displayed on the legacy page, the one currently displayed is https://github.com/opencollective/opencollective-frontend/blob/15df3640cbaf03dd397824010603557a21855160/pages/expense.js#L394.
Not sure when this was updated, but it seems react-intl now always passes an array as chunks here. Opened https://github.com/opencollective/opencollective-frontend/pull/5294 to update the existing paths.


Add the use of ServiceLoader for Client Extensibility

As discussed in https://github.com/onetable-io/onetable/issues/293 , I am breaking the larger PR down into more easily reviewed pieces.
This change will introduce the use of ServiceLoader by the TableFormatClientFactory to discover the TargetClient implementations by TableFormat which was recently changed from an Enum to a String in preparation for this change.
ServiceLoader will load all implementations on the classpath (built-in to OneTable or added by the user) and select the intended client implementation by name provided for the Sync via argument or configuration.
This will allow users and/or tooling vendors to extend the capabilities without requiring all TargetClient's to be committed to the project.
In order to move to this approach, we will need to introduce a default noarg ctor for each Client, add an init() to accept the required config params and extract interfaces for all objects that are are being used directly within the config classes that would otherwise require moving them to the api module or add a dependency on core from api.
It will also require addressing the dependency on the config objects themselves. We can extract an interface for the PerTableConfig object and have that in the api module but the hadoop Configuration class likely needs to be added through a dependency on hadoop common from the api module anyway. Perhaps we should just move the PerTableConfig class into the api module?

@the-other-tim-brown - see the open question at the bottom of the description. I think that moving the class and dependency to api is probably better than adding an interface for PerTableConfig like I did in PR #295 but could be convinced otherwise. I also don't think we can avoid the dependency on Hadoop common for the Configuration being added to api but maybe you have another idea?


Pip packaging

Restructures repo for pip packaging.
Requires clients to change from com.yahoo.ml.tf import * to from tensorflowonspark import *.

+1


I can't upload a custom logo.

Hi,
I received this error message when I try upload a custom logo:
Failed to open /etc/usermin/authentic-theme/logo.png for writing : Not a directory
This is a unique problem or general? My OS is very outdated (Debian 6.x)

Most likely it's OS specific. Try to check if destination directory exists, if not create it with right permissions.

Hmm... this is a regular file:
/etc/usermin/authentic-theme

Hmm... this is a regular file:
ecrazor1911@hosting:/home/dani# file /etc/usermin/authentic-theme
/etc/usermin/authentic-theme: ASCII text
It's possible?

That is wrong. Delete this file and replace it with directory. Don't forget to put there config file. After, resave the theme settings and reupload the logo. You should be fine.

Thank you for help! It's working correctly.


Fixed problem with pip package "libvirt-python"

Fixed problem where pip pkg "libvirt-python" won't compile against ol…der libvirt system packages. See openstack bug # 1753539

Build triggered. sha1 is merged.

Build started sha1 is merged.

Build finished.

created this secondary PR to test something on ci


Wallets:Wallets with the same wallet name are being created.

https://github.com/bithyve/bitcoin-keeper/assets/62699947/0e972477-c323-4828-af8a-37dfde25feda

I had 2 wallets in app.After that I created collaborative wallet.After collaborative wallet I again created 2 wallets and those wallets are having same wallet name but both are different.

Verified this issue on keeper app v 1.1.6(256)


Switch to relative import statements

Right now a lot of imports use the absolute name of a module since it was quick and easy and worked.  However going forward relative imports are the right way to reference modules inside modules and are supported by later python 2.7 and 3 releases.

This was switched over to python 3 compatible imports last year.


User config

Implement config in json format.
Create default, if doesn't exist, on app start.
In-app window to modify.
Versioning, in case new config values appear in the future.

In-app window will be introduced with later releases.


CASMINST-4413 make ssh connections faster for clock skew test

Signed-off-by: Jacob Salmela<EMAIL_ADDRESS>Summary and Scope
Adds SSH options to allow re-use of the connection, allowing for faster checks of time.
Issues and Related PRs

Resolves CASMINST-4413 for 1.2

Testing
Tested on:

#redbull
#surtur

Test description:
Ran the script with time and verified it worked.  It usually clocked in around 1.3 seconds, which is fine for allowing 1 second of drift.
Risks and Mitigations
Low
Pull Request Checklist

[ ] Version number(s) incremented, if applicable
[ ] Copyrights updated
[ ] License file intact
[x] Target branch correct
[ ] CHANGELOG.md updated
[ ] Testing is appropriate and complete, if applicable
[ ] HPC Product Announcement prepared, if applicable

Also, this PR does not seem to have a counterpart in master (or 1.0).


Verify the latest Istio runs on minikube

Describe the bug
A clear and concise description of what the bug is.
reviews-v1, reviews-v2 and reviews-v3 are in ImagePullBackOff state with error:
Warning  Failed                 6m                kubelet, minikube  Failed to pull image "istio/examples-bookinfo-reviews-v1:1.8.0": rpc error: code = Unknown desc = failed to register layer: Error processing tar file(exit status 1): operation not supported
Expected behavior
A clear and concise description of what you expected to happen.
Bookinfo app should start
Steps to reproduce the bug
kubectl apply -f <(istioctl kube-inject -f samples/bookinfo/platform/kube/bookinfo.yaml)
Steps to reproduce the behavior.
kubectl apply -f <(istioctl kube-inject -f samples/bookinfo/platform/kube/bookinfo.yaml)
Version
Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.2", GitCommit:"bdaeafa71f6c7c04636251031f93464384d54963", GitTreeState:"clean", BuildDate:"2017-10-24T19:48:57Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:44:10Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Is Istio Auth enabled or not?
yes
kubectl apply -f install/kubernetes/istio-demo.yaml
Environment
minikube version: v0.28.2
Istio Version: 1.0.0
Cluster state
If you're running on Kubernetes, consider following the
instructions
to generate "istio-dump.tar.gz", then attach it here by dragging and dropping
the file onto this issue.

Related to the user's question https://groups.google.com/forum/#!topic/istio-users/d7bnv7tpiHs

cc @rshriram @ZackButcher @costinm


Yael/delete compiled contract class object

This change is

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 78.06%. Comparing base (3243dd2) to head (61b594f).
Report is 33 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #335      +/-   ##
==========================================
+ Coverage   77.01%   78.06%   +1.05%
==========================================
  Files          28       28
  Lines        1379     1409      +30
  Branches     1379     1409      +30
==========================================
+ Hits         1062     1100      +38
+ Misses        262      254       -8
  Partials       55       55

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Backfill configured rooms

Everything is empty when load up. As soon as team connections are made we should try to backfill 25-50 messages so all the chat rooms have content.

Fixed in #7


Circular dependency in v3.0.0 prevents webhook from working

URL to the linked Repository or Organization
https://github.com/
Steps to reproduce the problem

Open a pull request

What is the expected result?
The check shows status of CLA signature
What happens instead?
The check shows:
license/cla Expected — Waiting for status to be reported
permanently
Any other information? (attach screenshot if possible)
The server shows the following error:
(node:2108508) Warning: Accessing non-existent property 'get' of module exports inside circular dependency
    at emitCircularRequireWarning (node:internal/modules/cjs/loader:787:11)
    at Object.get (node:internal/modules/cjs/loader:803:5)
    at RepoService.getPRCommitters (/usr/src/cla-assistant/cla-assistant/src/server/src/services/repo.js:365:47)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async updateStatusAndComment (/usr/src/cla-assistant/cla-assistant/src/server/src/webhooks/pull_request.js:67:28)

Used browser and browser version?
Any other tested browsers/devices(OK/FAIL):

A little more investigation shows that the issue is that src/server/src/services/webhook.js requires repo.js which in turn requires webhook.js.  repo.js also requires org.js which in turn also requires webhook.js.


Extension state get's resetted on reconfigure

We want to use this extension to provide the svelte repl with Vim keybinginds. However we are running into an issue because we need to store the state of the editor on a per document basis (you can swap between tabs and each tab has it's own state and most importantly history). To reset the history we need store the codemirror state of every tab, and upon swapping tab restore the old codemirror state.
By doing so however every extension get's resetted so we need to also add an effect to reconfigure the set of extensions. Doing this reset the internal state of this extension (so for example if you are in insert mode it get's resetted to normal mode) and that's kinda of annoying. Part of the reason this happens is because this extension store all the information in a custom class (also called Codemirror) which is not a facet so when you save the state from Codemirror it doesn't gets serialized. I realize this is a massive overhaul of the current implementation so i totally understand if you decide to not address this.
However in case you are not planning to implement this would you consider instruct me on how could i store the vim state and re-apply this state after the reconfiguration? I'm especially concerned about the mode but all the other state would be cool to.

It should not be very hard to add methods to save and restore the vim state, Do you have an example of another plugin that properly handles the state, or maybe you can point me to the documentation that describes how this should work with facets.

I'm far from an expert but from my understanding the correct way should be to create a StateField (this should be an Extension that you just return in an array with your extension)
https://codemirror.net/docs/ref/#state.StateField
To recover that state you should use the facet method on the Editor state
https://codemirror.net/docs/ref/#state.EditorState.facet
I totally understand that this would be a huge refactor. There some way I can export the current vim extension state and than reapply it?

@nightwing do you have any update on this? The pr to add the vim extension to the svelte REPL is ready but we are waiting to merge it because this behavior it's quite inconvenient. But if there's no way to get and restore the state and you have no man power to update the extension we will merge anyway.

Unfortunately there is no method to set inputState correctly to vim. I think i will be able to implement it and use it from a facet by the end of next week, but most likely some followup work will be needed as well, to get tabs to work the way they do in vim (e.g. some commands are meant to jump between tabs, etc.). So i think it would be better to merge your pr, and add state handling in a followup.

There is no way to use facets in vim code itself, as it is meant to be interoperable with old codemirror and ace. But i think it should be possible to add a way to  update the internal state when facet is reconfigured. One problem though is that i would either have to copy cm.state.vim object with every change, or make it partially compatible with codemirror's immutable api, so that it would work with your usecase but won't work for restoring vim to an earlier state.


Correct response for a DECRQSS query?

According to the VT330/VT340 Text Programming Reference, the response to the DECRQSS query is a DECRPSS sequence with a parameter value indicating whether the request was valid or not.

0 = host's request is valid.
1 = host's request is invalid.

I've checked as many other manuals as I could find, and most seem to agree with this. This includes the VT320 user manual, the VT420 programming reference, the VT510 programming reference, and the VT520/VT525 programming reference.
However, the DEC STD-070 reference describes these values the other way, and so do the VT382 manuals.

0 = unknown selection or setting
1 = request successful

I'm hoping you'll be able to confirm which of these is correct, at least for the VT340.
Here is an example of a valid query (requesting the SGR state):
printf '\eP$qm\e\\'; read -n 100

In theory it should respond with something like this:
^[P0$r0m^[\

And this is an example of an invalid query:
printf '\eP$qx\e\\'; read -n 100

Which should respond with something like this:
^[P1$r^[\

If that's not what you're seeing, then maybe we've got another entry for the errata doc.

The VT320 manual and DEC STD-070 seem to be correct while the VT340 manual is mistaken.  This make some sense since the VT320 came after the VT330 & 340.
$ printf '\eP$qm\e\\'; read -rd '\'; echo
^[P1$r0m^[\

$ printf '\eP$qx\e\\'; read -rd '\'; echo
^[P0$r^[\
$

Thanks. That's a relief, actually, because that's what most modern terminals have been doing. But note that the test you added to the errata doc has the wrong read delimiter (it's using a forward slash rather than backslash).

Thanks for catching that. Wouldn't want someone else to have to create an errata doc for my errata doc.

Just wanted to say thanks!
I was basing my own implementation on the VT510 manual, and was confused by both XTerm's and mlterm's responses...


Broken links in C++ API docs

Apparently most of the links in the main part of the index of the C++ API documentation are broken.
The problem seems to be that the first letter of each file name is in lowercase, so the links look like this:
https://www.tensorflow.org/versions/r0.7/api_docs/cc/classEnv.html
Instead of this:
https://www.tensorflow.org/versions/r0.7/api_docs/cc/ClassEnv.html

@chemelnucfin: Is this bug fixed now?

@girving see pull request #1314


Port to Firefox

A Firefox version would be very neat :)
I think it doesn't even need a new project. Just this project needs to be modified a bit.

Firefox does not support WebHID.
As @iMonZ writes, you could write something like

Firefox does not support WebHID.
As @iMonZ suggests, you could write a desktop program that can be called from the extension. Like: https://github.com/gnaudio/jabra-browser-integration/tree/master/src/ChromeHost Called from: https://github.com/gnaudio/jabra-browser-integration/tree/master/src/ChromeWebExtension

This looks actually pretty interesting

Firefox does not support WebHID.
As @iMonZ suggests, you could write a desktop program that can be called from the extension. Like: https://github.com/gnaudio/jabra-browser-integration/tree/master/src/ChromeHost Called from: https://github.com/gnaudio/jabra-browser-integration/tree/master/src/ChromeWebExtension

Does the Chromehost from Jabra support other browsers? Or is it just a false name?

It should in theory work with all Chromium-based browsers, but Jabra only officially supports Chrome and Microsoft Edge.
You could potentially reuse the binary for a Firefox extension, but you'll probably have to repackage it.

Anyone knows how to do that?


Resolves #1851

Add missing description for MetadataVersion property
https://github.com/MicrosoftDocs/windows-powershell-docs/issues/1851

Docs Build status updates of commit e57e8da:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/windows/bitlocker/Get-BitLockerVolume.md
:white_check_mark:Succeeded

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

@dariomws @get-itips @tseward FYI

Looks good.


wrong(ly formated?) symbol for lock

Description
Since app. 3-4 days ago gBar shows a lock icon which does not look like it should for me (see below) this seems to have been caused by some update, either to gBar or some dependency, since I have made no configuration changes
Steps to Reproduce
I have no frickin clue, just restarted gBar after rebooting, now always looks this way, even after PC- and gBar restart
Expected behavior
show the lock icon in the same style as the other icons

the config I use:
# Example configuration.
# Everything after '#' is ignored
# Format of the variables:
#    [variable]: [value]
# Whitespaces are ignored in the following locations:
# - Before the variable
# - After the ':'
# - After the value

# The following three options control the ordering of the widgets.
# Reordering can cause slight margin inconsistencies,
# so it is recommend to only make minor adjustments to the default layout.
# Adding the same widget multiple times to the layout is *not* supported and will cause issues.

# Widgets to show on the left side
WidgetsLeft: [Workspaces]
# Widgets to center
WidgetsCenter: [Time]
# Widgets to display on the right side
WidgetsRight: [Tray, Packages, Audio, Bluetooth, Network, Disk, VRAM, GPU, RAM, CPU, Battery, Power]

# The CPU sensor to use
CPUThermalZone: /sys/class/thermal/thermal_zone0/hwmon1/temp1_input

# The command to execute on suspend
SuspendCommand: systemctl suspend

# The command to execute on lock
LockCommand: swaylock -f -i /usr/share/backgrounds/cosmiccliffs1440p.png

# The command to execute on exit
ExitCommand: killall Hyprland

# The folder, where the battery sensors reside
BatteryFolder: /sys/class/power_supply/BAT0

# The partition to monitor with disk sensor
DiskPartition: /

# Overrides the icon of the nth (in this case the first) workspace.
# Please note the missing space between "," and the symbol. Adding a space here adds it to the bar too!
#WorkspaceSymbol: 1,

# The default symbol for the workspaces
DefaultWorkspaceSymbol: 

# Scroll through the workspaces of the current monitor instead of all workspaces
WorkspaceScrollOnMonitor: true

# When true: Scroll up -> Next workspace instead of previous workspace. Analogous with scroll down
WorkspaceScrollInvert: false

# Number of workspaces to display. Displayed workspace IDs are 1-n (Default: 1-9)
NumWorkspaces: 10

# Use Hyprland IPC instead of the ext_workspace protocol for workspace polling.
# Hyprland IPC is *slightly* less performant (+0.1% one core), but way less bug prone,
# since the protocol is not as feature complete as Hyprland IPC.
# NOTE: Hyprland no longer supports ext-workspace-unstable-v1 as of commit bb09334.
# Hyprland IPC is thus *required* for workspace support under Hyprland >=v0.30.0!
UseHyprlandIPC: true

# The location of the bar
# Needs to be capitalized!!
# Values are: L (Left), R (Right), T (Top), B (bottom)
Location: T

# Forces the time to be centered.
# This can cause the right widget to clip outside, if there is not enough space on screen (e.g. when opening the text)
# Setting this to false will definitely fix this issue, but it won't look very good, since it will be off-center.
# So try to decrease "TimeSpace" first, before setting this configuration to false.
CenterTime: true

# How much space should be reserved for the time widget. Setting this too high can cause the right widget to clip outside.
# Therefore try to set it as low as possible if you experience clipping.
# Although keep in mind, that a value that is too low can cause the widget to be be off-center,
# which can also cause clipping.
# If you can't find an optimal value, consider setting 'CenterTime' to false
TimeSpace: 300

# Set datetime style
DateTimeStyle: %a %y-%m-%d - %H:%M:%S %Z

# Set datetime locale (defaults to system locale if not set or set to empty string)
#DateTimeLocale: de_DE.utf8

# Adds a audio input(aka. microphone) widget
AudioInput: false

# Sets the audio slider to be on reveal (Just like the sensors) when true. Only affects the bar.
AudioRevealer: false

# Sets the rate of change of the slider on each scroll. In Percent
AudioScrollSpeed: 5

# Display numbers instead of a slider for the two audio widgets. Doesn't affect the audio flyin
AudioNumbers: false

# Command that is run to check if there are out-of-date packages.
# The script should return *ONLY* a number. If it doesn't output a number, updates are no longer checked.
# Default value is applicable for Arch Linux. (See data/update.sh for a human-readable version)
CheckPackagesCommand: p="$(checkupdates)"; e=$?; if [ $e -eq 127 ] ; then exit 127; fi; if [ $e -eq 2 ] ; then echo "0" && exit 0; fi; echo "$p" | wc -l

# How often to check for updates. In seconds
CheckUpdateInterval: 300

# Limits the range of the audio slider. Only works for audio output.
# Slider "empty" is AudioMinVolume, Slider "full" is AudioMaxVolume
# AudioMinVolume: 30 # Audio can't get below 30%
# AudioMaxVolume: 120 # Audio can't get above 120%

# The network adapter to use. You can query /sys/class/net for all possible values
NetworkAdapter: wlan0

# Disables the network widget when set to false
NetworkWidget: true

# Use tooltips instead of sliders for the sensors
SensorTooltips: false

# Enables tray icons
EnableSNI: true

# SNIIconSize sets the icon size for a SNI icon.
# SNIPaddingTop Can be used to push the Icon down. Negative values are allowed
# For both: The first parameter is a filter of the tooltip(The text that pops up, when the icon is hovered) of the icon

# Scale everything down to 25 pixels ('*' as filter means everything)
#SNIIconSize: *, 25
# Explicitly make OBS a bit smaller than default
#SNIIconSize: OBS, 23
# Nudges the Discord icon a bit down
#SNIPaddingTop: Discord, 5

# These set the range for the network widget. The widget changes colors at six intervals:
#    - Below Min...Bytes ("under")
#    - Between ]0%;25%]. 0% = Min...Bytes; 100% = Max...Bytes ("low")
#    - Between ]25%;50%]. 0% = Min...Bytes; 100% = Max...Bytes ("mid-low")
#    - Between ]50%;75%]. 0% = Min...Bytes; 100% = Max...Bytes ("mid-high")
#    - Between ]75%;100%]. 0% = Min...Bytes; 100% = Max...Bytes ("high")
#    - Above Max...Bytes ("over")
MinDownloadBytes: 0
MaxDownloadBytes: 10485760 # 10 * 1024 * 1024 = 10 MiB
MinUploadBytes:   0
MaxUploadBytes:   5242880    # 5 * 1024 * 1024 = 5 MiB

my css
* {
  all: unset;
  font-family: "CaskaydiaCove Nerd Font"; }

.popup {
  color: #50fa7b; }

.bar, tooltip {
  background-color: #282a36;
  border-radius: 16px; }

.right {
  margin-right: 10px;
  border-radius: 16px; }

.time-text {
  font-size: 16px; }

.reboot-button {
  font-size: 28px;
  margin-right: 6px;
  color: #6272a4; }

.sleep-button {
  font-size: 28px;
  color: #6272a4; }

.exit-button {
  font-size: 28px;
  color: #6272a4; }

.power-button {
  font-size: 28px;
  color: #ffb86c; }

.power-box-expand {
  margin-right: 6px; }

.system-confirm {
  color: #50fa7b; }

trough {
  border-radius: 3px;
  border-width: 1px;
  border-style: none;
  background-color: #44475a;
  margin-top: 2px;
  min-width: 4px;
  min-height: 4px; }

slider {
  border-radius: 0%;
  border-width: 1px;
  border-style: none;
  margin: -9px -9px -9px -9px;
  min-width: 16px;
  min-height: 16px;
  background-color: transparent; }

highlight {
  border-radius: 3px;
  border-width: 1px;
  border-style: none;
  min-height: 6px; }

.audio-icon {
  font-size: 24px;
  color: #ff79c6;
  margin-right: 12px; }

.audio-volume trough {
  background-color: #44475a; }

.audio-volume slider {
  background-color: transparent; }

.audio-volume highlight {
  background-color: #ff79c6; }

.mic-icon {
  font-size: 24px;
  color: #bd93f9;
  margin-right: 0px; }

.mic-volume trough {
  background-color: #44475a; }

.mic-volume slider {
  background-color: transparent; }

.mic-volume highlight {
  background-color: #bd93f9; }

.package-outofdate {
  font-size: 24px;
  margin-right: -5px;
  margin-left: -5px;
  color: #ffb86c; }

.bt-num {
  font-size: 16px;
  color: #1793D1;
  margin-left: -6px; }

.bt-label-on {
  font-size: 20px;
  color: #1793D1;
  margin-right: 6px; }

.bt-label-off {
  font-size: 24px;
  color: #1793D1;
  margin-right: 6px; }

.bt-label-connected {
  font-size: 28px;
  color: #1793D1;
  margin-right: 6px; }

.disk-util-progress {
  color: #bd93f9;
  background-color: #44475a;
  font-size: 16px; }

.disk-data-text {
  color: #bd93f9;
  margin-right: 6px;
  font-size: 16px; }

.vram-util-progress {
  color: #ff79c6;
  background-color: #44475a; }

.vram-data-text {
  color: #ff79c6;
  margin-right: 6px;
  font-size: 16px; }

.ram-util-progress {
  color: #f1fa8c;
  background-color: #44475a; }

.ram-data-text {
  color: #f1fa8c;
  margin-right: 6px;
  font-size: 16px; }

.gpu-util-progress {
  color: #8be9fd;
  background-color: #44475a; }

.gpu-data-text {
  color: #8be9fd;
  margin-right: 6px;
  font-size: 16px; }

.cpu-util-progress {
  color: #50fa7b;
  background-color: #44475a;
  font-size: 16px; }

.cpu-data-text {
  color: #50fa7b;
  margin-right: 6px;
  font-size: 16px; }

.battery-util-progress {
  color: #ff79c6;
  background-color: #44475a;
  font-size: 16px; }

.battery-data-text {
  color: #ff79c6;
  margin-right: 6px;
  font-size: 16px; }

.network-data-text {
  color: #50fa7b;
  margin-right: 6px;
  font-size: 16px; }

.network-up-under {
  color: #44475a; }

.network-up-low {
  color: #50fa7b; }

.network-up-mid-low {
  color: #f1fa8c; }

.network-up-mid-high {
  color: #ff79c6; }

.network-up-high {
  color: #bd93f9; }

.network-up-over {
  color: #ffb86c; }

.network-down-under {
  color: #44475a; }

.network-down-low {
  color: #50fa7b; }

.network-down-mid-low {
  color: #f1fa8c; }

.network-down-mid-high {
  color: #ff79c6; }

.network-down-high {
  color: #bd93f9; }

.network-down-over {
  color: #ffb86c; }

.ws-dead {
  color: #44475a;
  font-size: 16px; }

.ws-inactive {
  color: #6272a4;
  font-size: 16px; }

.ws-visible {
  color: #8be9fd;
  font-size: 16px; }

.ws-current {
  color: #f1fa8c;
  font-size: 16px; }

.ws-active {
  color: #50fa7b;
  font-size: 16px; }

@keyframes connectanim {
  from {
    background-image: radial-gradient(circle farthest-side at center, #1793D1 0%, transparent 0%, transparent 100%); }
  to {
    background-image: radial-gradient(circle farthest-side at center, #1793D1 0%, #1793D1 100%, transparent 100%); } }

@keyframes disconnectanim {
  from {
    background-image: radial-gradient(circle farthest-side at center, transparent 0%, #1793D1 0%, #1793D1 100%); }
  to {
    background-image: radial-gradient(circle farthest-side at center, transparent 0%, transparent 100%, #1793D1 100%); } }

@keyframes scanonanim {
  from {
    color: #f1fa8c; }
  to {
    color: #50fa7b; } }

@keyframes scanoffanim {
  from {
    color: #50fa7b; }
  to {
    color: #f1fa8c; } }

.bt-bg {
  background-color: #282a36;
  border-radius: 16px; }

.bt-header-box {
  margin-top: 4px;
  margin-right: 8px;
  margin-left: 8px;
  font-size: 24px;
  color: #1793D1; }

.bt-body-box {
  margin-right: 8px;
  margin-left: 8px; }

.bt-button {
  border-radius: 16px;
  padding-left: 8px;
  padding-right: 8px;
  padding-top: 4px;
  padding-bottom: 4px;
  margin-bottom: 4px;
  margin-top: 4px;
  font-size: 16px; }
  .bt-button.active {
    animation-name: connectanim;
    animation-duration: 50ms;
    animation-timing-function: linear;
    animation-fill-mode: forwards; }
  .bt-button.inactive {
    animation-name: disconnectanim;
    animation-duration: 50ms;
    animation-timing-function: linear;
    animation-fill-mode: forwards; }
  .bt-button.failed {
    color: #ffb86c; }

.bt-close {
  color: #ffb86c;
  background-color: #44475a;
  border-radius: 16px;
  padding: 0px 8px 0px 7px;
  margin: 0px 0px 0px 8px; }

.bt-scan {
  color: #f1fa8c;
  background-color: #44475a;
  border-radius: 16px;
  padding: 2px 11px 0px 7px;
  margin: 0px 0px 0px 10px;
  font-size: 18px; }
  .bt-scan.active {
    animation-name: scanonanim;
    animation-duration: 50ms;
    animation-timing-function: linear;
    animation-fill-mode: forwards; }
  .bt-scan.inactive {
    animation-name: scanoffanim;
    animation-duration: 50ms;
    animation-timing-function: linear;
    animation-fill-mode: forwards; }

Information about your system and gBar

OS:  Arch
Desktop environment [e.g. Hyprland, Sway, ...]
commit sha256 if possible [e.g. 16e7d8aa50ddebeffb2509d7c0428b38cad565f8]

This is a known breaking change since 56c53c4, since I made a copy-paste mistake when initially creating the bar and forgot to give the lock a separate css class (and also forgot to put a .lock-button selector in the css).
To fix this, a simply add e.g.
.lock-button {
    font-size: 28px;

    color: $darkblue;
}

to the scss file.


bug: NEXTAUTH_URL validation failing with vercel env pull

Provide environment information
System:
OS: macOS 13.6
CPU: (8) arm64 Apple M2
Memory: 737.61 MB / 24.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 18.17.1 - ~/.volta/tools/image/node/18.17.1/bin/node
Yarn: 4.0.0-rc.50 - ~/.volta/tools/image/yarn/4.0.0-rc.50/bin/yarn
npm: 9.6.7 - ~/.volta/tools/image/node/18.17.1/bin/npm
pnpm: 8.7.4 - ~/.volta/bin/pnpm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
ct3aMetadata.initVersion: "7.19.0"
Describe the bug
Using Vercel, you can conveniently fetch the latest environment variables with vercel env pull. However, a caveat is that Vercel sets VERCEL_URL="" locally, causing .preprocess() to always use the empty VERCEL_URL instead of the explicitly set NEXTAUTH_URL.
To resolve this, every time you pull the environment variables, you must manually remove VERCEL_URL="" from .env.local. This step is also necessary in the CI environment to pass the env.mjs validation.
I'm considering a logic switch from str => process.env.VERCEL_URL ?? str  to str => str ?? process.env.VERCEL_URL, where VERCEL_URL becomes the fallback value, rather than NEXTAUTH_URL. I'm prepared to implement this change, but I'd appreciate your input on whether this solution makes sense to you, or if you have a better suggestion.
Reproduction repo
I can't set it up, because it depends on a Vercel account. But you don't need any code changes to reproduce.
To reproduce

Run npm create t3-app@latest and install with NextAuth
Connect repo to Vercel
Set NEXTAUTH_URL="http://localhost:3000" in Vercel for development environment.
Run vercel env pull (you may need to run vercel login first)
Run npm run dev

Now you should get the following error
next dev

❌ Invalid environment variables: { NEXTAUTH_URL: [ 'String must contain at least 1 character(s)' ] }
Error: Invalid environment variables

Additional information
No response

Awesome! That's great. And I saw it's already in create-t3 🙌  Thank you @juliusmarminge. I will close the issue then.


Add problems and solutions from Codewars

Since a folder for Codewars_problems has been created, more problems and solutions can be added from Codewars✨
Preferred difficulty level: Easy-Medium/hard (please refrain from adding too beginner/trivial questions)
Refer Contribting.md and read all points carefully before sending a Pull request.
Keep this in mind: When adding solutions, ensure that you provide sufficient comments so as to explain the logic used.🙃
Happy Contributing 😄

I want to contribute in it.

@gitrahulgit Sure you can. Just be sure to read  Contribting.md before sending a Pull request 😃


Dilato: Core: It use characters when the number is 1

Steps:

Launch Brackets
Click Find -> Find in files
Drop down the No files excluded list, select New Exclusion Set
Input characters in the Name this exclusion set field

Result: "1 characters remaining"
Expect: "1 character remaining"

Here is a similar issue

Launch Brackets
File -> Open Folder... then open a folder which only contains 1 file
Find -> Replace in Files
Click "No Files Excluded" then click "New Exclusion Set..."
Result: Allows all 1 files in project
Expect: Allows all 1 file in project


LibCore: SystemWindows.cpp fix includes

Fixes broken includes, making it compile.

Was fixed in 77d2055.


added doodle jump game

fixes #663

fixes #663

Please merge my pr @panwar8279

Please Create new PRs for this because all check are failed.


Enhancement/describe network acls

Related to issue #2997
Includes:

Change the method from get_all_network_acls to describe_network_acls
Add unit test for this new method

I hope that I have implemented correctly.

Coverage increased (+0.005%) to 94.371% when pulling 27df992cf7f78ca5db563158d0d4f10604fbc38e on anardy:enhancement/describe-network-acls into 134cceeb12eb4ff459db29f95e92a6cf4fded68c on spulec:master.


create rare disease slim

30 terms to include all the rare diseases

The suggested grouping terms/slim 'category' for rare diseases are here:
https://docs.google.com/spreadsheets/d/1Xg3to5ThdQjM6YY6gZ-oE3DFRlU6OwZ_EmejRPJ3W4g/edit#gid=0
@matentzn : I cannot check whether these terms cover all the rare diseases (running the subset requires too much memory that my computer cannot handle). Could you please send me something I can review? Thank you!

Will have to be done in a meeting

@matentzn We are still working on a few things, but I think this issue can be closed. Would you agree?


Upgrade JQuery major version

As reported by Snyk, JQuery 2 has a Cross-site Scripting vulnerability, which is fixed in JQuery 3.0.0 and higher.
From JQuery website:
"Despite the 3.0 version number, we anticipate that these releases shouldn’t be too much trouble when it comes to upgrading existing code. Yes, there are a few “breaking changes” that justified the major version bump, but we’re hopeful the breakage doesn’t actually affect that many people."
So hopefully it won't be very difficult to upgrade!

We need help in upgrading the same to major version, which would include extensive testing with the jQuery challenges, and the sections of code that use jQuery.


Question:  How to get new map center on onMapEnd event?

I'm currently catching the onMoveEnd event and would like to then query to see what the new map center is.  Is this possible with the current API?

Yes the first argument that you receive in the callback function is the map object, so you can do :
  _moveEnd = map => {
    map.getCenter();
  };


chore(deps): update dependency synckit to ^0.8.3

I updated dependency sycnkit to from ^0.8.1 to ^0.8.3.
This is because<EMAIL_ADDRESS>breaks using this pugin with Yarn PnP in VSCode.
This issue has already been reported(#164), and has been resolved in synckit(un-ts/synckit#98), but this plugin dependency has not been updated

You can upgrade synckit on your side manually AFAIK?

How can i upgrade synckit manually?

How can i upgrade synckit manually?

yarn upgrade synckit
yarn remove eslint-import-resolver-typescript && yarn add -D eslint-import-resolver-typescript
rm -rf yarn.lock && yarn
Edit yarn.lock file, remove<EMAIL_ADDRESS>section, and run yarn

I am testing in the Yarn Berry Monorepo environment.
As you said, I found a way to manually update directly from Yarn berry, and I executed it.
yarnPath: .yarn/releases/yarn-3.2.1.cjs
packageExtensions:
<EMAIL_ADDRESS>    dependencies:
      synckit: '^0.8.3'

Isn't it impossible to use it in Yarn PnP environment unless you upgrade it manually?

Isn't it impossible to use it in Yarn PnP environment unless you upgrade it manually?

I tried in https://github.com/kriasoft/react-starter-kit, it seems true, so this PR is accepted.
In my imagine, when I remove "synckit@npm:^0.8.1" section in yarn.lock, yarn should reinstall the latest version of synckit, but it seems not true.

@HanSeo0507 Thanks for your contribution!

@JounQin Thank you for reviewing my PR.
How many days will it take for this PR to be reflected in the release?

@JounQin Thank you for reviewing my PR. How many days will it take for this PR to be reflected in the release?

Right now.

@JounQin Thank you for reviewing my PR. How many days will it take for this PR to be reflected in the release?

Right now.

Okay. Thank you!

@HanSeo0507
<EMAIL_ADDRESS>has been released! Thanks for your contribution again!

For future reference, if using Yarn Modern, you can update a transitive dependency like synckit by running yarn up -R synckit. The newly released version matches the semantic version range ^0.8.1, so running yarn up -R synckit will bump the resolved version to the latest matching that range.


Move to dart-lang GitHub org

Changes Unknown when pulling 840afe28974e9611a97cb690f5c7141a192b923c on move_to_dl into ** on master**.

Done!
On Thu, Aug 31, 2017 at 6:07 PM, Devon Carew<EMAIL_ADDRESS>wrote:

@devoncarew approved this pull request.
lgtm! You'll probably need to re-publish http://stagehand.pub/ w/ updated
links.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/stagehand/pull/442#pullrequestreview-60027830,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABCikipbvZkDFISxatj9lX3zMwcxIj2ks5sd1jNgaJpZM4PJlI-
.


Fix for reduction simdization in presence of constant dimensions

There was an issue with "unrequested" blocked inner loops being generated (when the control flow was simplified to fully nested) while lowering krnl to affine dialect.
The fix is relatively simple. I detect when the inner loop of a blocked loop is unused (aka its loop def is not used by any krnl operation). When that is the case, we still use the affine support to block the loop. The code simply forces the inner loop (which is not requested) to become a trivial for(I=0; I<1; I++) loop.
I also added a seed to generate different test case for RunONNXModel.py as it is useful to detect if several versions of a code always fail in the same way because of structural issues, or simply because they use the same seed.
I also added a few lit tests that cover this new issue, both to make sure the correct code pattern is generated when lowering the onnx operations to krnl, as well as when lowering the krnl to affine.

Jenkins Linux amd64 Build #12370 [push] fix for reduction simdiz... started at 08:53

Jenkins Linux s390x Build #12382 [push] fix for reduction simdiz... started at 09:53

Jenkins Linux amd64 Build #12370 [push] fix for reduction simdiz... passed after 1 hr 4 min


[AutoPR] cognitiveservices/data-plane/LUIS/Runtime

Created to accumulate context: cognitiveservices/data-plane/LUIS/Runtime

Codecov Report

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

@@           Coverage Diff           @@
##           master    #3035   +/-   ##
=======================================
  Coverage   57.43%   57.43%
=======================================
  Files        7767     7767
  Lines      158336   158336
=======================================
  Hits        90937    90937
  Misses      67399    67399

Continue to review full report at Codecov.

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

Codecov Report

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

@@           Coverage Diff           @@
##           master    #3035   +/-   ##
=======================================
  Coverage   57.43%   57.43%
=======================================
  Files        7767     7767
  Lines      158336   158336
=======================================
  Hits        90937    90937
  Misses      67399    67399

Continue to review full report at Codecov.

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


New version LLLplus: 1.2.1

Registering: LLLplus
Repository: https://github.com/christianpeel/LLLplus.jl
Version: v1.2.1
Commit: b32061dc0fa6f271e665b88fb13d8a13c1b4fc53
Proposed by: @christianpeel
Reviewed by: @christianpeel
Reference: https://github.com/christianpeel/LLLplus.jl/issues/17

Consider enabling TagBot to make sure the release is persistent in your repo, see https://discourse.julialang.org/t/ann-tagbot-creates-tags-and-releases-for-your-julia-packages-when-theyre-registered/23084

TagBot tag


SW-5066 Allow all file types in document upload

We don't want to restrict which types of files users can send us
for document deliverables. Remove the restricted list of MIME types
on the file chooser.

#2332  👈
main

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

Join @sgrimm and the rest of your teammates on  Graphite


[TC-182] Add additional statuses into traffic ops seeds.sql

This pr adds additional required statuses into the traffic ops status table fixing TC-182.

After looking at this more with Dave, there is a larger underlying problem here affecting more than just statuses.


[model] add DiffMG model

Description

Checklist
Please feel free to remove inapplicable items for your PR.

[x] The PR title starts with [$CATEGORY] (such as [NN], [Model], [Doc], [Feature]])
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage
[x] Code is well-documented
[x] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change
[x] Related issue is referred in this PR
[x] If the PR is for a new model/paper, I've updated the example index here.

Changes

Also, I think it is better to create a dataset module to preprocess the dataset instead of putting this into the trainerflow.

Do you have any documents about your model? Please create a document in the openhgnn/output/ and give a model performance.


Player goes to buffering state after playing SSAI ads instad of the playing the content

Bug
after implementing  SSAI logic the player plays the Ads then after playing the ad the function player.getCurrentPosition() starts to return random value as -1658671026284 then it goes to buffering state instead  of playing the content
Platform
this issue happens on Android onlu

@hueniverse what do you mean by triage needed ? is there anything needed from my side?

sorry i closed it by mistake
@hueniverse
and what does triage needed mean ?
is there anything needed from my side ??

@Lilsax I confirm that a sample stream would be useful !
Additionally did you test on v6 alpha or only on 5.2 ?
Thank you

the issue turned out to be with the audio the playout contain audio source different from the video source which leaded to a buffering issue


Interactive rendered state is not always the current board state

When I do python3 -m safelife play, and repeatedly hit the forward arrow to have the agent walk in a line, I see the agent jump forwards and backwards sometimes. It's very disconcerting. What seems to be happening is that sometimes the state that's rendered to the screen is the previous game state, not the current one.
This only happens with pyglet graphics, but occurs with pyglet 1.3.2 and 1.5.0

Closed in the multiagent branch


Prepare for new release

Codecov Report
Patch coverage: 92.85% and project coverage change: +6.45% :tada:

Comparison is base (9ecf96f) 86.27% compared to head (bdaaafe) 92.72%.
Report is 1 commits behind head on main.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #30      +/-   ##
==========================================
+ Coverage   86.27%   92.72%   +6.45%
==========================================
  Files           1        1
  Lines         102      110       +8
  Branches       20       21       +1
==========================================
+ Hits           88      102      +14
+ Misses         13        7       -6
  Partials        1        1

Files Changed
Coverage Δ

src/utils.js
92.72% <92.85%> (+6.45%)
:arrow_up:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


please update github.com/Azure/azure-sdk-for-go vendoring

The vendored github.com/Azure/azure-sdk-for-go version is obsolete and relies on code of dubious legal status (the godo bits). Please update to a current release which has not got this problem anymore.

Any news on that?
I'm attempting to package docker-distribution for Debian, and hence to build it against the Go libraries shipped by Debian (no vendoring). And right now in Debian unstable, we have azure-sdk v10.
When I try to build against v10 I get these errors.
# github.com/docker/distribution/registry/storage/driver/azure
src/github.com/docker/distribution/registry/storage/driver/azure/azure.go:90:44: not enough arguments in call to containerRef.CreateIfNotExists
	have ()
	want (*storage.CreateContainerOptions)
src/github.com/docker/distribution/registry/storage/driver/azure/azure.go:107:23: d.client.GetBlob undefined (type storage.BlobStorageClient has no field or method GetBlob)
src/github.com/docker/distribution/registry/storage/driver/azure/azure.go:136:24: d.client.GetBlobProperties undefined (type storage.BlobStorageClient has no field or method GetBlobProperties)
src/github.com/docker/distribution/registry/storage/driver/azure/azure.go:141:21: d.client.DeleteBlob undefined (type storage.BlobStorageClient has no field or method DeleteBlob)
src/github.com/docker/distribution/registry/storage/driver/azure/azure.go:147:17: d.client.CreateBlockBlobFromReader undefined (type storage.BlobStorageClient has no field or method CreateBlockBlobFromReader)
src/github.com/docker/distribution/registry/storage/driver/azure/azure.go:153:24: d.client.BlobExists undefined (type storage.BlobStorageClient has no field or method BlobExists)
src/github.com/docker/distribution/registry/storage/driver/azure/azure.go:159:23: d.client.GetBlobProperties undefined (type storage.BlobStorageClient has no field or method GetBlobProperties)
src/github.com/docker/distribution/registry/storage/driver/azure/azure.go:170:23: d.client.GetBlobRange undefined (type storage.BlobStorageClient has no field or method GetBlobRange)
src/github.com/docker/distribution/registry/storage/driver/azure/azure.go:180:29: d.client.BlobExists undefined (type storage.BlobStorageClient has no field or method BlobExists)
src/github.com/docker/distribution/registry/storage/driver/azure/azure.go:187:35: d.client.GetBlobProperties undefined (type storage.BlobStorageClient has no field or method GetBlobProperties)


[SPARK-36690][SS] Clean up deprecated api usage after upgrade commons-pool2 to 2.11.1

What changes were proposed in this pull request?
SPARK-36583 upgrade Apache commons-pool2 from 2.6.2 to 2.11.1 and there are some deprecated API usage related to it that need to be cleaned up.
The list of changes is as follows:

BaseObjectPoolConfig.setMinEvictableIdleTimeMillis -> BaseObjectPoolConfig.setMinEvictableIdleTime
BaseObjectPoolConfig.setSoftMinEvictableIdleTimeMillis -> BaseObjectPoolConfig.setSoftMinEvictableIdleTime
BaseObjectPoolConfig.setTimeBetweenEvictionRunsMillis -> BaseObjectPoolConfig.setTimeBetweenEvictionRuns

Why are the changes needed?
Clean up deprecated API  usage.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass GA or Jenkins Tests.

Test build #143070 has started for PR 33933 at commit 7389ba3.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47572/

I'm going to merge this as this is a simple replacement on deprecated API.

Test build #143070 has finished for PR 33933 at commit 7389ba3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/143070/

Thanks @LuciferYang for contribution! I merged this into master.

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47572/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47572/

Thanks @HeartSaVioR @HyukjinKwon


iOS release mode issue | Did Key not getting generated when archiving

Hi Team.
I am facing 1 issue while integrating the did kit library in flutter.
When I am running on device locally by connecting cable with my mac in debug mode, I am able to get the did key generated. However, when I am archiving it and uploading on the Testflight, did key is not getting generated.
Can you please let me know where could be the issue? Is there any issue already reported.
Thank you
Rohit

Hi @prorohit,
Do you have an error message or stack trace coming from a DIDKit function call?

@prorohit are you still encountering this issue?
Does calling the version function work?
Do you want to discuss this via a different channel?


Command for creating cluster not working

What kind of request is this (question/bug/enhancement/feature request):
bug/question: Is my yaml correct? Or it is a bug?
Steps to reproduce (least amount of steps as possible):
Executing the following command: rancher up --file cluster-template.yml
Result:
Nothing in the Rancher UI.
Nothing in the Rancher logs.
Other details that may be helpful:
Here's the tutorial that I've followed: https://rancher.com/docs/rancher/v2.x/en/cluster-admin/cloning-clusters/
Here's my yaml template file:
Version: v3
clusters:
<CLUSTER_NAME>:
azureKubernetesServiceConfig:
adminUsername:
agentPoolName:
agentVmSize: Standard_D2_v2
clientId:
clientSecret:
count: 3
kubernetesVersion: 1.11.9
location:
osDiskSizeGb: 100
resourceGroup:
sshPublicKeyContents:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):
Installation option (single install/HA):
Just updated Rancher.

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported):
Machine type (cloud/VM/metal) and specifications (CPU/memory):
Kubernetes version (use kubectl version):

(paste the output here)

Docker version (use docker version):

(paste the output here)

I just bumped into this issue today. I'm using rancher 2.5.1 and when running rancher up --file nothing happens. There is no verbose option in cli and the UI is like nothing happened


Cleaned up Spanish translation of Java do-while guide

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

Thank you for  creating this PR.  In addition to needing to fix the issues pointed out by @hestellez, since this PR was created, the underlying document has changed.  Can you please review and resolve the current merge conflicts?  It could be the changes to the underlying document are so significant that your changes are no longer relevant.  If the latter is the case, it might be easier to just close this PR and create a new PR with any changes you still feel are important to make.
If you need any assistance or have questions about resolving the merge conflicts, please reply back or contact someone in the Contributors Room on Gitter.
Thank you.

We are restructuring a lot of the code and learning resources referenced in your pull request, so for now I am going to go ahead and close this pull request. Thanks again for opening this pull request and for contributing to the community.


Recovering terminal

Hi, I write this issue to help any user that had found the same problem.
If the game is close forcefully, the terminal environment is not reset.
You can reset the "repeat" mode of your terminal writting:
xset r

Thanks, I'll try to fix it.


AnalyticsParameterScreenName not setting name with SwiftUI

[REQUIRED] Step 1: Describe your environment

Xcode version: Xcode 12
Firebase SDK version: 6.33.0
Firebase Component: Analytics
Component version: 6.33.0
Installation method: `CocoaPods

[REQUIRED] Step 2: Describe the problem
I am using Swiftui.  I am trying to set the set the screen name and screen class but neither are logged in debug mode or within the console from other users.  I have enabled debug view using -FIRDebugEnabled and I do see some data flowing into debug view such as user_engagement and screen_view, but nothing from AnalyticsParameterScreenName.
Steps to reproduce:

Install FirebaseAnalytics
Run the following code with FirebaseAnalytics
Wait for data in debug view

Relevant Code:
import SwiftUI
import FirebaseAnalytics

struct DoGoodView: View {
    var body: some View {
        VStack {
            Text("Foo")
        }
        .onAppear{
            DispatchQueue.main.asyncAfter(deadline: DispatchTime.now() + DispatchTimeInterval.milliseconds(500)) {
                Analytics.logEvent(AnalyticsEventScreenView, parameters: [AnalyticsParameterScreenName: "Do Good"])
                    }
        }
    }
}

Data seems to be flowing now. Sorry for the bother mates


buildRustPackage: fix cargo flag for release/debug build

Motivation for this change
Previous behavior did not actually allow for "debug" build as it would
try to pass --debug to cargo, which is not a valid flag.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[X] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Assured whether relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Related: #56540
cc @Mic92 @Ericson2314 @illegalprime for review

Ping?


Error ill-formed ticket found in the URL when ticket is encrypted

If the cas server is encrypting the ticket value (cas.ticket.security.cipherEnabled=true) the php client fails with the error:  Error ill-formed ticket found in the URL
You have to set this property to false for the client to work.

Related to #180

I don't believe it is related to #180 because php CAS doesn't need to decrypt the ticket instead the criteria for what is a valid ticket needs to accept that the encrypted ticket is valid and just pass it back.

Can you please supply a debug log?

3424 .START (2017-08-22 12:11:13) phpCAS-1.3.5 ****************** [CAS.php:468]
3424 .=> phpCAS::client('3.0', 'castst.conncoll.edu', 443, 'cas') [index.php:12]
3424 .|    => CAS_Client::__construct('3.0', false, 'castst.conncoll.edu', 443, 'cas', true) [CAS.php:360]
3424 .|    |    Starting a new session cq25i8qv8bbq8uqoiud8hh2g75 [Client.php:932]
3424 .|    |    Session is not authenticated [Client.php:938]
3424 .|    |    => phpCAS::error('ill-formed ticket found in the URL (ticket=eyJhbGciOiJIUzUxMiJ9.WlhsS05tRllRV2xQYVVwRlVsVlphVXhEU21oaVIyTnBUMmxLYTJGWVNXbE1RMHBzWW0xTmFVOXBTa0pOVkVrMFVUQktSRXhWYUZSTmFsVXlTVzR3TGk1NFYxaDNTbWhOY25KMFoxQm9aM1ExVkc4eGFGVjNMakJhZHpRdE0zcFRVV2hFUlhsaGNYVTVibWw1VlUxT05EazFURkpRWDNkRWVHcERXR0l3YUVGcldXSkdPWGxMTmpWRFIyazBiV2M1VUdocldWbHVVa0l1VVUxWmFtZFVUWGRLWm1VM2NVNVhabVk1VjBsclp3PT0.QCt2Ma0yxcfigVaNE5DYlwog1Vz8bIRB_EzoJjs85wWnXKCEwaxlvQKoIMU7C4HdxFbJya-Pj6URByRfpMwbsg\')') [Client.php:1028] 3424 .|    |    |    ill-formed ticket found in the URL (ticket=eyJhbGciOiJIUzUxMiJ9.WlhsS05tRllRV2xQYVVwRlVsVlphVXhEU21oaVIyTnBUMmxLYTJGWVNXbE1RMHBzWW0xTmFVOXBTa0pOVkVrMFVUQktSRXhWYUZSTmFsVXlTVzR3TGk1NFYxaDNTbWhOY25KMFoxQm9aM1ExVkc4eGFGVjNMakJhZHpRdE0zcFRVV2hFUlhsaGNYVTVibWw1VlUxT05EazFURkpRWDNkRWVHcERXR0l3YUVGcldXSkdPWGxMTmpWRFIyazBiV2M1VUdocldWbHVVa0l1VVUxWmFtZFVUWGRLWm1VM2NVNVhabVk1VjBsclp3PT0.QCt2Ma0yxcfigVaNE5DYlwog1Vz8bIRB_EzoJjs85wWnXKCEwaxlvQKoIMU7C4HdxFbJya-Pj6URByRfpMwbsg') in /cwd/cwassets/httpd/alias/tp/cas/cas5-php-test/index.phpon line 12 [CAS.php:566]
3424 .|    |    <= ''

Thanks, looks like we simply need to adjust the regexp security filter for the ticket so that it allows all formats including the new encryption.

Has there been any movement on this? I'm running against master, with all of the fixes for ticket/session length (#248, #257, and #224), but enabling cas.ticket.security.cipherEnabled still throws an error.


Edited "Resolution" section

Edited "Resolution" section: added the basic analysis step and a link to the Driver Verifier documentation page.

@tedhudek - This PR is ready to go to live/master.

@LuigiBruno - This looks fine, thanks for the PR.

Thank you @DOMARS.


CloudWatchWriter fails when writing results of query with >20 items

AWS API seems to limit the maximum number of metrics sent in a single request to 20 items. CloudWatchWriter does not respect this limit and tries to send oversized requests, which fail with message:

com.amazonaws.services.cloudwatch.model.InvalidParameterValueException: The collection MetricData must not have a size greater than 20. (Service: AmazonCloudWatch; Status Code: 400; Error Code: InvalidParameterValue

See AWS docs for limits

20/PutMetricData request. A MetricDatum object can contain a single value or a StatisticSet object representing many values. This limit cannot be changed.

https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/cloudwatch_limits.html
As far as I can tell, the best solution here would be to split the data when we have more than 20 results and send them in separate requests. Not sure if those mentioned StaticSets would be applicable here, but I think not.

Thanks for the report! #666 should fix the issue. Any chance you check it before I merge it?

Based on very preliminary test #666 seems to work for me :thumbsup:


testPathPattern changed when updating from major 12 to major 14

Error: Unknown config option "testPathPattern" with value "modules/*/spec". This is either a typing error or a user mistake and fixing it will remove this message.
Using Jest CLI v14.1.0, jasmine2, babel-jest

This path worked (or appeared to work) with major 12, but major 14 does not seem to like it very much. modules/.*/spec yields the same message.
Excerpt of package.json
  "jest": {
    "collectCoverage": false,
    "testDirectoryName": "spec",
    "testPathPattern": "modules/.*/spec",
    "setupTestFrameworkScriptFile": "scripts/jest/setup.js",
    "preprocessorIgnorePatterns": [
      "/node_modules\/(?!@)/"
    ],
    "testFileExtensions": [
      "spec.js"
    ],
    "moduleFileExtensions": [
      "js",
      "json"
    ],
    "modulePathIgnorePatterns": [
      "/.git/",
      "/.idea/",
      "/.vagrant/",
      "/coverage/",
      "/documentation/",
      "/scripts/"
    ]
  },

We don't support this config option any more. You can still pass it from the CLI or use the testRegex option for this (but then I recommend removing testFileExtensions from the config).

Without the testPathPattern, not all test files are found. (+this option is still listed on the website/docs)

Can you create a repository that shows this issue? Then I can help – I'm pretty sure a proper testRegex pattern is the right solution here.


Add permissions policy header

Expected Behavior
Example should include a section for the permissions policy header. Useful to control browser features as well as opting out of the FLoC tracking currently being tested in certain browsers.
Actual Behavior
Example makes no mention of the header
Section that requires update
https://github.com/cloudflare/cloudflare-docs/blob/production/products/workers/src/content/examples/security-headers.md
Additional information
https://scotthelme.co.uk/what-the-floc/
https://geekflare.com/opt-out-floc-configuration/
https://perishablepress.com/opt-out-google-floc/

Thanks for the resources, mentioned the header in this PR! We might in the future add a headers section to the docs, explaining them in more depth, so we can expand this code example further.


Alpha - Microsite header - feedback and environment variant

Also include Dev, test, prod with or without version number
As a: Full stack developer
I want: Use the "feedback" and "environment" variant of the callout from the UI library
so that: I can spend more time creating features or capabilities that will provide value to my users and stakeholders
Discuss desired behaviour of "feedback" text link with Thomas
Acceptance criteria

[ ] Create web component
[ ] Create React wrapper
[ ] Passing unit tests
[ ] Linting
[ ] Include in "canvas" web component storybook
[ ] Push to Alpha
[ ] Manual design review
[ ] Ensure that ui-component variant naming scheme and Figma component variant names are aligned

Presentable outcomes

[ ] I can show the ui-component in Storybook and provide the link to service teams so that they can view the component for themselves

Sprint Ready Checklist

Acceptance criteria defined
Team has defined steps to satisfy acceptance criteria
Acceptance criteria is verifiable / testable
External / 3rd Party dependencies identified

Related issues:
Resources:
Mockups: Microsite header - Feedback
Feedback pattern
Testing URL: [If applicable a URL to the testing branch]

In case it's helpful: I created a draft of a pattern around gathering feedback within your service that gives some context for how the feedback variant would be used.
https://www.figma.com/file/UbIKwjbxuPUvoFNYvMBGpe/[WIP]-Patterns---DIO-DS?node-id=1239%3A1483

@chrisolsen @Spark450 I updated the microsite header throughout Figma to include the link to Alberta.ca

@chrisolsen Great work on the update, just a few items, let me know if you have any questions, Thanks!

@chrisolsen Just a couple of things, let me know if you have questions about the layout, Thanks!


Add Webauthn example using the secp256r1 API

Note: I haven't really found any good official test vectors when searching for them. So I checked other implementations verifying Webauthn attestations on chain, and I found this Solidity contract and used its test vectors.
They seem to check out, I guess.

Well, this doesn't do the COSE parsing and everything, but that isn't really the main attraction that's needed to verify the crypto API suitability.
The main thing that's important here is the following: You can reconstruct a key and signature into the format needed by the crypto API from the parameters you get via the Webauthn attestation ceremony.
And this proves that you can do that and that the verification will succeed.


update imageconfig on service creation/update

this PR extracts the internal registry hostname from the observed service object and reflects it into the global Image configuration object for the cluster.

@bparees - is the change from this merged PR sufficient for the sample operator to determine if the registry is up before creating/updating imagestreams?
Seems like sample operator could create a watch on the new ImageConfig object now being generated, and look for the internal registry hostname to be set, no?


installing 32 bit trusty / precise

I've been trying to install 32 bit linux chroot on my Acer CB3-111 chromebook.
Version 46.0.2490.82 (64-bit)
Platform 7390.68.0 (Official Build) stable-channel gnawty
Firmware Google_Gnawty.5216.239.34
I have tried several fresh install using the -a i386 / -a i686 on both trusty and precise, for example:
sudo sh ~/Downloads/crouton -t xfce -r trusty -a i386 -e
but each time, when I type uname -m in the linux terminal, it comes back as x86_64, instead of expected i686 or i386.
Any way to install 32 bit on the 64bit Chromos?
Thanks.

You can specify the architecture when installing your chroot using the -a option - see https://github.com/dnschneid/crouton/issues/734#issuecomment-39347222

The command line you used will install i386 packages, however the kernel will not change, because it is the kernel from chromeos and cannot be changed. So uname -m will always keep reporting x86_64.  That said the 64 bit kernel will support the i386 packages.
Any specific reason for using 32bit?

Thanks for the reply divx118.  Hum... i guess I need to forget about getting my crusty old windows CAD program to run on my chromebook.  It will run in wine, but only under 9x mode.  Wine 9X mode seems to break in 64 bit kernel.   Something about 16bit mode no longer being supported in 64bit kernel, which breaks wine.  I can't even start the wine config program once I set the mode to 98....


how add new tasks？

May I ask how to add testing tasks and how to test local tasks

Hi! We have documentation written for how to add a new task here: https://github.com/EleutherAI/lm-evaluation-harness/blob/master/docs/task_guide.md
If you still have questions after reading this, feel free to post again under this issue! This would be helpful to improve our documentation, which we intend to do over the course of the next month.

Our laboratory is planning to develop software based on your code. May I ask when your upload test set function will be implemented?
I would greatly appreciate it if you could answer!


Confirmation email will not be sent to

Hi Rias, unfortunately your plugin does not send the confirmation email. The custom notification email works.
I am using Craft CMS 3 <IP_ADDRESS> and craft-contact-form-extensions 1.0.7.
Craft sends the mails via Mailgun.
Thank you, Andi.

Okay, sorry. It's done. Mailgun was configured incorrectly. :)


ProfileClient: protocol doesn't handle multi-line secret properties correctly

Up until now, all of the secret values we've been fetching via neon-assistant have been single line values.  While implementing code-signing automation for neonCLOUD, we need to download a multi-line public certificate but we're only getting the first line back.
This is happening because our named-pipe protocol is line based and doesn't support multi-line values.
The fix is to convert the secret result value to UTF-8 and then base64 encode on the server and then have the client unpack that before returning the value to the caller.  This will be a breaking change requiring a neon-assistant rebuild and reinstall.

DONE


Line text flipping

Rotate 180 degrees （DCBA）,How to restore "ABCD"

how to add text in the line, please?

@pwj126 view:

https://github.com/jerosoler/Drawflow/issues/18


upgrade pika's network engine pink to 2.0 version

pika use old version pink, and pika don't update pink for a long time.
In this period of time, pink has update its code and its usage.

Working in branch upgrade_pink


Error: Cannot find module 'mocha/lib/cli/run-option-metadata'

Configuring Detox on android giving me this error on running npx detox test --configuration android.emu.release

My .detoxrc is written similar to this

Getting this errors

I'll check if Mocha has changed anything in their folder structure.

What version of Mocha do you use? @sumukhah

I am not using Mocha at all.(In my project)

@sumukhah , there's something wrong with your testRunner property in your Detox config then.

I have generated it through detox init -r jest. So I believe it's correct.

Yes. testRunner is set to : "jest-circus/runner" in e2e/config.json

@sumukhah, actually I've been actually inquiring about your detox.config.js (or .detoxrc.json, ...), and not e2e/config.json.

Oh sorry...
My .detoxrc.json is
  "devices": {
    "emulator": {
      "type": "android.emulator",
      "device": {
        "avdName": "Pixel_API_29"
      }
    }
  },
  "apps": {
    "android.debug": {
      "type": "android.apk",
      "binaryPath": "android/app/build/outputs/apk/debug/app-debug.apk",
      "build": "cd android && ./gradlew assembleDebug assembleAndroidTest -DtestBuildType=debug && cd .."
    },
    "android.release": {
      "type": "android.apk",
      "binaryPath": "android/app/build/outputs/apk/release/app-release.apk",
      "build": "cd android && ./gradlew assembleRelease assembleAndroidTest -DtestBuildType=release && cd .."
    }
  },
  "configurations": {
    "android.emu.debug": {
      "device": "emulator",
      "app": "android.debug"
    },
    "android.emu.release": {
      "device": "emulator",
      "app": "android.release"
    }
  }
}

@sumukhah , so this is exactly where I would expect to see:
 {
+  "testRunner": "jest",
+  "runnerConfig": "e2e/config.json",
   "devices": {
     "emulator": {
...

Due to compatibility reasons, default runner for Detox is mocha, although de facto we recommend jest.

@sumukhah , could you run which mocha in your terminal, please?

No i haven't installed mocha globally

mocha not found

Thanks, now I get why I could not reproduce this issue. 👍
I'll improve the error message soon.

Action items for the pull request:

[ ] print a warning about an undefined testRunner property
[ ] throw an error if the test runner cannot be resolved (have you installed?...)

i have same problem as @sumukhah
after adding testRunner and runnerConfig rules to detoxrc.json
i started to get:
 Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './build/types' is not defined by "exports" in C:\myProjects\localization-class\node_modules\jest-circus\package.json

@shootermv make sure you are using Detox 18.16.0 and above.

Closing (won't fix): We are working on removing mocha support, at least for the time being, in Detox 20.


Patreon key not working, poke me to get this fixed

Where: https://christine.website/patrons
What:  Status Code: 500

Oh, dupe of: #442 nvm


[mysten-metrics/ adjust max channel size log]

Summary:

the mpsc channel is bounded to 1k entries and will log an error when it is maxed out.  this PR changes that log message to debug level.

Test Plan:
it builds

i'll put in another PR that adds a metric counter for this event.  We can graph that over time and get an idea of how common it is.


CSUB-384: Test against mainnet

Description of proposed changes:
Practical tips for PR review & merge:

[ ] All GitHub Actions report PASS
[ ] Newly added code/functions have unit tests

[ ] Coverage tools report all newly added lines as covered
[ ] The positive scenario is exercised
[ ] Negative scenarios are exercised, e.g. assert on all possible errors
[ ] Assert on events triggered if applicable
[ ] Assert on changes made to storage if applicable

[ ] Modified behavior/functions - try to make sure above test items are covered
[ ] Integration tests are added if applicable/needed

Codecov Report

Merging #924 (db983a6) into main (30d0b22) will decrease coverage by 1.62%.
The diff coverage is 75.19%.

@@            Coverage Diff             @@
##             main     #924      +/-   ##
==========================================
- Coverage   79.78%   78.17%   -1.62%
==========================================
  Files          47       68      +21
  Lines        8866    10904    +2038
==========================================
+ Hits         7074     8524    +1450
- Misses       1792     2380     +588

Impacted Files
Coverage Δ

node/src/benchmarking.rs
0.00% <0.00%> (ø)

node/src/chain_spec.rs
0.00% <0.00%> (ø)

node/src/cli.rs
35.71% <0.00%> (-5.60%)
:arrow_down:

node/src/command.rs
0.00% <0.00%> (ø)

node/src/lib.rs
100.00% <ø> (ø)

node/src/main.rs
16.66% <ø> (ø)

node/src/rpc.rs
0.00% <0.00%> (ø)

node/src/service.rs
0.00% <0.00%> (ø)

node/src/service/nonce_monitor.rs
0.00% <0.00%> (ø)

pallets/creditcoin/src/migrations/mod.rs
0.00% <0.00%> (ø)

... and 96 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


first cut at updating CF runloop changes for linux

Here's a first cut at this.   It compiles, but I haven't actually tested it with foundation yet.  Implementation mostly based on the code from experimental/foundation, but I decided to more closely mirror the mach code and stash the eventfd in dq->do_ctxt instead of introducing a static variable just for the main queue.
I'm not that happy with the HANDLE (windows) vs. int (linux) aspect of the patch.  I partially introduced dispatch_handle_t, but I also should introduce a symbolic constant for 0/NULL and be more careful in the linux-specific code to always use dispatch_handle_t instead of int.  Do we want dispatch_handle_t or similar?  On as similar note, we could define dispatch_handle_t to be mach_port_t if TARGET_OS_MAC and if we could change the name of _dispatch_get_main_queue_port_4CF to _dispatch_get_main_queue_handle_4CF we could avoid duplicating code.
Also, I used TARGET_OS_MAC in queue.c instead of HAVE_MACH.  This is different than other places in queue.c where we guard mach specific code.  Is this correct?

I don't think we care much about windows, the port is clearly not working, and I would just get rid of that.
maybe the right thing to do is to have a dispatch_runloop_handle_t rather than dispatch_handle_t which is a bit too generic that abstracts port & fd on linux.
and internally I would have a:
DISPATCH_ALWAYS_INLINE
static inline bool
_dispatch_runloop_handle_is_valid(dispatch_runloop_handle_t handle)
{
#if TARGET_OS_MAC
    return MACH_PORT_VALID(handle);
#elif defined(__linux__)
    return handle >= 0
#else
#error
#endif
}

DISPATCH_ALWAYS_INLINE
static inline dispatch_runloop_handle_t
_dispatch_runloop_queue_get_handle(dispatch_queue_t dq)
{
#if TARGET_OS_MAC
    return ((dispatch_runloop_handle_t)(uintptr_t)dq->dq_ctxt);
#elif defined(__linux__)
    return ((dispatch_runloop_handle_t)(uintptr_t)dq->dq_ctxt) - 1;
#else
#error
#endif
}

DISPATCH_ALWAYS_INLINE
static inline void
_dispatch_runloop_queue_set_handle(dispatch_queue_t dq, dispatch_runloop_handle_t handle)
{
#if TARGET_OS_MAC
    return dq->do_ctxt = (void *)(uintptr_t)handle;
#elif defined(__linux__)
    return dq->do_ctxt = (void *)(uintptr_t)(handle + 1);
#else
#error
#endif
}

That way the actual mangling of the handle is abstracted away and should allow you to write clean code whether it's a mach port, a file descriptor, a HANDLE, or maybe even something else in the future.
I think you need the +1/-1 trick for fd's because do_ctxt is initialized to 0 where you would want it to be -1, and that is easier to do that mangling above than to try to initialize runloop queues differently.
do you agree?

Thanks for the quick review!
The suggestion for dispatch_runloop_handle_t and setters/getters makes sense to me.  I'll update the patch later tonight.

Not a blocker for this, but we will care about Windows in the long run - both because we actually do use dispatch on windows today, and also because Swift will get ported there soon enough (if it hasn't quite made it already).

@parkera I completely agree, what I meant is that @dgrove-oss was trying to maintain code that is not wroking at all. the _get_handle() function is actually a prototype only and has no corresponding function in queue.c, and in my experience, it's best to delete half-assed code so that porters aren't misled into thinking this may work.
I wasn't meaning that I don't care about windows, HTH.

Ok, sounds good.

ok from a cursory glance this looks clean and nice, but I'm too fried to do a proper review now.
I'd also like @das to look at it

Squashed to a single commit.
Confirmed that combined with the changes in https://github.com/apple/swift-corelibs-foundation/pull/434 plus the temporary hack in #100, Foundation links with Dispatch support on Linux and testOperationCount in TestNSOperationQueue passes (however testOperationPriorities hangs).  Did not investigate hang since I don't know if the Foundation side of the support is there for that test case yet.
Would be nice to enable some of the dispatch tests that require CoreFoundation.   Would it make sense to try to reach into swift-corelibs-foundation from the dispatch build to find CoreFoundation to attempt to build them?  Or do you want to defer to testing in the context of swift-corelibs-foundation?

I really want CF to remain a totally private implementation detail of Foundation.

Would it be possible to make these tests use Foundation instead? I guess that would require reimplementing them.

i'll take a look asap

LGTM, @das to rubber stamp too as it affects headers

one bug and various small style/convention comments but lgtm otherwise, back to you

I'd already made changes to private/private.h based on my interpretation of @das comments.  I can undo or do differently, just let me know what you'd like.  Please be sure to look at the availability macro I put on _dispatch_get_main_queue_handle_4CF.  Since this is a new function on MAC_OS, I think it should get these versions, but I'm only guessing.
Once we finalize this, I can update my pull request to foundation to match the final API.

Ok, we can deal with any lockstep changes later probably.

Thanks @dgrove-oss that looks exactly like what I had in mind. The new availability annotation should be __OSX_AVAILABLE(10.12) __IOS_AVAILABLE(10.0) __TVOS_AVAILABLE(10.0) __WATCHOS_AVAILABLE(3.0) I think
Given the above discussion, it would probably also be useful to add a #define DISPATCH_CF_SPI_VERSION 20160712 define above this section, that CF can use to switch to the new call without revlock.

availability macros updated and DISPATCH_CF_SPI_VERSION #define added.

perfect, thanks


Update README to remove 'preview' text.

We should update the README.md file with updated text, removing the preview language, etc.

Done.


Exclude AES from CMake

SwiftPM doesn't need it and this would allow removal of CCryptoBoringSSL dependency on non-Darwin platforms, thus reducing SwiftPM size.
Also remove CryptoKitErrors_boring.swift in _CryptoExtras because the same util already exists in Crypto and code in _CryptoExtras can use that instead.

Need to add exclusions to update_cmakelists or else those files would keep getting re-added to CMakeLists