NIFI-9852 Upgrade Spring Framework from 5.3.16 to 5.3.18

Description of PR
NIFI-9852 Upgrades Spring Framework dependencies from 5.3.16 to 5.3.18, and upgrades Spring Boot from 2.6.4 to 2.6.6 for NiFi Registry.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[X] Has your PR been rebased against the latest commit within the target branch (typically main)?

[X] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[X] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[X] Have you verified that the full build is successful on JDK 8?
[ ] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

Description of PR
NIFI-9852 Upgrades Spring Framework dependencies from 5.3.16 to 5.3.18, and upgrades Spring Boot from 2.6.4 to 2.6.6 for NiFi Registry.
In order to streamline the review of the contribution we ask you to ensure the following steps have been taken:
For all changes:

[x]  Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
[x]  Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[x]  Has your PR been rebased against the latest commit within the target branch (typically main)?
[x]  Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[x]  Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ]  Have you written or updated unit tests to verify your changes?
[x]  Have you verified that the full build is successful on JDK 8?
[ ]  Have you verified that the full build is successful on JDK 11?
[ ]  If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ]  If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ]  If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ]  If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ]  Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

On March 30, Spring announced CVE-2022-22965, an unauthenticated remote code execution vulnerability that has been found in the Spring Framework.

On March 30, Spring announced CVE-2022-22965, an unauthenticated remote code execution vulnerability that has been found in the Spring Framework.

Thanks for the reference @sujeethnayak. As noted in the linked Jira issue NIFI-9852, NiFi does not appear to meet the vulnerability criteria listed. This upgrade mitigates the issue regardless of potential exposure to the vulnerability described.

+1 will merge


Ege frontend

not sure why there is some additions...

@neniman I have fixed most of the conflicts but I think you should double check the remaining one

It is at addproject.vue and marked with // here to ... //here


Create a new pull request by comparing changes across two branches

Description

Motivation & Context

Type of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Refactoring (non-breaking change)
[ ] Breaking change (fix or feature that would change existing functionality)

Checklist

[ ] I have read the contributing guidelines
[ ] My code follows the code style of the project (using npm run lint)
[ ] My change introduces changes to the documentation
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] All new and existing tests passed

Live previews

https://deploy-preview-{your pr number}--twbs-bootstrap.netlify.app/

Related issues

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.06%) to 95.717%

Totals

Change from base Build<PHONE_NUMBER>:
-0.06%

Covered Lines:
2022

Relevant Lines:
2072

💛  - Coveralls


Null pointer exception when starting Teku without some options

Description
As a user, I want Teku to start without NPE even if I don't provide any options. Seeing a NPE and being told that it's a misuse of the software is not acceptable for an enterprise grade product.
Acceptance Criteria

Run Teku binaries and Docker image without options and have no error.
Have a smoke test in CI to make sure Teku works when ran with minimal (no) options.
Find a way to spot these kind of NPE in the future as manual review is not enough (a code checker rule, SonarCube ?) or at least track this need in an issue. Link the issue in this one.

Steps to Reproduce (Bug)
With binaries built from source:

run Gradle installDist task ./gradlew clean installDist
run the binary without options build/install/teku/bin/teku

or with the develop docker image:

docker pull pegasyseng/teku:develop
docker run pegasyseng/teku:develop

Expected behavior: [What you expect to happen]

no error should be thrown
Teku should be up and running with a viable default setup, perhaps matching the most obvious use case.

Actual behavior: [What actually happens]
A null pointer exception is thrown and Teku crashes.
Frequency: [What percentage of the time does it occur?]
100%
Versions (Add all that apply)

Software version: master commit 22e214d1043edcd3990e44ea02814e28e8f0b691
Java version: 12.0.2 but also happens on the Teku develop Docker image which is openjdk:11.0.2-jre-slim-stretch
OS Name & Version: Circle CI linux, Docker image, macOS, so probably on all OSes

Additional Information
Stacktrace:
% build/install/teku/bin/teku
Teku failed to start.
java.lang.NullPointerException
	at tech.pegasys.artemis.services.powchain.PowchainService.<init>(PowchainService.java:54)
	at tech.pegasys.artemis.services.ServiceController.<init>(ServiceController.java:37)
	at tech.pegasys.artemis.BeaconNode.<init>(BeaconNode.java:77)
	at tech.pegasys.artemis.Artemis.start(Artemis.java:38)
	at tech.pegasys.artemis.cli.BeaconNodeCommand.call(BeaconNodeCommand.java:241)
	at tech.pegasys.artemis.cli.BeaconNodeCommand.call(BeaconNodeCommand.java:61)
	at picocli.CommandLine.executeUserObject(CommandLine.java:1783)
	at picocli.CommandLine.access$900(CommandLine.java:145)
	at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2150)
	at picocli.CommandLine$RunLast.handle(CommandLine.java:2144)
	at picocli.CommandLine$RunLast.handle(CommandLine.java:2108)
	at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:1975)
	at picocli.CommandLine.execute(CommandLine.java:1904)
	at tech.pegasys.artemis.cli.BeaconNodeCommand.parse(BeaconNodeCommand.java:194)
	at tech.pegasys.artemis.Artemis.main(Artemis.java:31)

see #1717 - it is the same exception just further along

ok so latest master behaves quite nicely with no args
➜  node_0 git:(master) ./bin/teku
2020-05-29 11:24:00,872 main INFO Configuring logging for destination: console and file
2020-05-29 11:24:00,877 main INFO Logging file location: /Users/sallymacfarlane/Library/teku/logs/teku.log
2020-05-29 11:24:00,877 main INFO Logging includes events: true
2020-05-29 11:24:00,877 main INFO Logging includes color: true
11:24:01.217 INFO  - Using data path: /Users/sallymacfarlane/Library/teku/data
11:24:01.233 INFO  - Initializing storage
11:24:11.248 INFO  - Storage initialization complete
ETH1 is disabled but initial state is unknown. Enable ETH1 or specify an initial state.
To display full help:
teku [COMMAND] --help

I'm handing this one back to @arash009 for the bigger picture issue

Closing this for now as starting with no options gives a meaningful error and no longer an NPE.


Proposal to add a new hook useSubscribeToMore

I've opened a issue with a question about an alternative alternative to query.subscribeToMore (#122). But if it's not possible i thinks this proposal will help.
I'm using this custom hooks that I made. But I think this can be a part of this awesome library. 😜. What do you think @trojanowski?
useSubscribeToMore.js
import { useEffect, useState } from 'react';
import { useSubscription } from 'react-apollo-hooks';

export function useSubscribeToMore(query, { document, updateQuery }) {
  const [data, setData] = useState(query.data);

  const handleSubscriptionData = (options) => {
    setData((prevData) => {
      const nextData = updateQuery(prevData, options);
      if (nextData === undefined) {
        return prevData;
      }
      return nextData;
    });
  };

  const subscription = useSubscription(document, {
    onSubscriptionData: handleSubscriptionData,
  });

  useEffect(() => {
    setData(query.data);
  }, [query.data]);

  return {
    ...query,
    data,
    subscription,
  };
}

Usage eg: messagesExample.js
import React from 'react';
import gql from 'graphql-tag';
import { useQuery } from 'react-apollo-hooks';
import { useSubscribeToMore } from './useSubscribeToMore';

const MESSAGE_FRAGMENT = gql`
  fragment Message on Message {
    id
    body
    createdAt
  }
`;

const MESSAGE_QUERY = gql`
  query {
    messages {
      ...Message
    }
  }
  ${MESSAGE_FRAGMENT}
`;

const MESSAGE_SUBSCRIPTION =  gql`
  subscription {
    messageAdded {
      ...Message
    }
  }
  ${MESSAGE_FRAGMENT}
`;

export function Messages() {
  const messageQuery = useQuery(MESSAGE_QUERY);
  const { data, loading, error } = useSubscribeToMore(messageQuery, {
      document: MESSAGE_SUBSCRIPTION,
      updateQuery: (data, { subscriptionData }) => {
        if (!subscriptionData.data) {
          return void 0;
        }

        return {
          ...prev,
          messages: [ ...prev.messages, subscriptionData.data.messageAdded],
        };
      }
  });

  if (loading) {
    return (
Loading...
);
  }

  if (error) {
    return (
Something is wrong, try again...
);
  }

  return (

      {data.messages.map(({ id, body, createdAt }) => (

{body}

          <time>{createdAt}</time>

      ))}

  );
}

Any suggestion @trojanowski?

@RodolfoSilva there is a problem with this solution - it doesn't save the updated data to the Apollo cache, so you'd see outdated data if the component unmounted and mounted again. useSubscription hook has builtin support for updating the cache with subscription data with the onSubscriptionData option. It works similar to the update option for mutation. messagesExample.js can be rewritten that way with it:
const { data, error, loading } = useSubscription(MESSAGE_SUBSCRIPTION, {
  onSubscriptionData: ({ client, subscriptionData }) => {
    // Client is an instance of Apollo client.
    // It has cache proxy method used in the `update` option in mutations.
    // Please look at: https://www.apollographql.com/docs/react/essentials/mutations#update
    const cachedMessages = client.readQuery({
      query: MESSAGE_QUERY
    });
    cachedMessages.messages.push(subscriptionData.messageAdded);
    client.writeQuery({
      query: MESSAGE_QUERY,
      data: cachedMessages,
    })
  }
});

Nice, I'll add this example in the README.md latter. Thanks @trojanowski  :stuck_out_tongue_winking_eye:

I'm new to Apollo and thus have started with 3.0+
This is a great example, but could you please explain why I would opt out of subscribeToMore for useSubscription, is their benefit to using one over the other?

@IsaacTrevino this library is in maintenance mode. It existed to add hooks support to Apollo, and is no longer necessary when you’re using modern Apollo!

Is there place where I can see full messagesExample.js file, still not able to make it work ? Thanks.


MSID: 97614 Version: 1 DOI: 10.1101/2<IP_ADDRESS>7469

MSID: 97614
Version: 1
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>7469
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=97614
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>7469

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/97614v1
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>7469
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/97614/v1/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c14) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c18) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c36) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c46) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c50) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c53) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c64) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c65) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c72) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c81) has a publication-type='other'. Is that correct?
warn: [title-upper-case] Content of  element is entirely in upper case: Is that correct? 'AUTHOR COMPETING INTERESTS'


CLI tests

This PR adds rudimentary tests for the CLI, testing:

qcengine info and its options terminate successfully
qcengine run and qcengine run-procedure terminate successfully for string and filename input

A future PR will need to address verifying the contents of STDOUT and piping STDIN for run and run-procedure. This will require substantial restructuring of testing.run_process and its coroutine.
TODO

[x] use process running functions from util.py
[x] add coverage

@dgasmith @loriab could I get another review of this please?


How to make time row always visible?

How to make the time row always visible when scrolling, just like the channel column? Thanks!

How to achieve this one? I want time visible always. if we scroll the collectionView it is disappear.

@hansolowireless @m1entus
Is it possible? Thanks

Everything is possible, you should easly implement it, you have already big bunch of code which you should be grateful.

@m1entus
I'm very thankful for what you have done already it's really great. Actually i don't have too much experience in objective c so it will be very helpful for me if you guide me or provide some demo code.
Thanks.


Add 'View'

This is to fix when isVisible is set to false - React was giving an error that View couldn't be found.

Oww good catch ! Thanks @yamill.
I'm gonna merge it

Np! :+1:


Cannot read property 'value' of undefined when calling amplify init

Describe the bug
I wanted to create my very first "Hello World" app in AWS Amplify but when I call amplify init I get following error when I have to choose the type of app I want to use:
❯ npx amplify init
Note: It is recommended to run this command from the root of your app directory
? Enter a name for the project amplifyplayground
? Enter a name for the environment dev
? Choose your default editor: Visual Studio Code
? Choose the type of app that you're building
(node:19168) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'value' of undefined
    at ListPrompt.getCurrentValue (/Users/me/project/node_modules/inquirer/lib/prompts/list.js:121:
53)
    at MapSubscriber._next (/Users/me/project/node_modules/rxjs/internal/operators/map.js:49:35)
    at MapSubscriber.Subscriber.next (/Users/me/project/node_modules/rxjs/internal/Subscriber.js:66
:18)
    at TakeSubscriber._next (/Users/me/project/node_modules/rxjs/internal/operators/take.js:54:30)
    at TakeSubscriber.Subscriber.next (/Users/me/project/node_modules/rxjs/internal/Subscriber.js:66:18)
    at Interface.handler (/Users/me/project/node_modules/rxjs/internal/observable/fromEvent.js:22:28)
    at Interface.emit (events.js:327:22)
    at Interface.EventEmitter.emit (domain.js:485:12)
    at Interface._onLine (readline.js:337:10)
    at Interface._line (readline.js:666:8)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:19168) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:19168) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Amplify CLI Version
4.21.1
To Reproduce
I did nothing except amplify init
Expected behavior
Should initialise my project.
Desktop (please complete the following information):

OS: macOS 10.15.5
Node Version: 14.2.0

I did it a second time now and I guess the main problem is that I don't get any list here:
❯ npx amplify init
Note: It is recommended to run this command from the root of your app directory
? Enter a name for the project amplifyplayground
? Enter a name for the environment dev
? Choose your default editor: Visual Studio Code
? Choose the type of app that you're building (Use arrow keys)

So I can't choose anything. When I now hit Enter I get the error above because I did not select anything, which I can't because nothing is shown.

I found out that here is already an issue about this: https://github.com/aws-amplify/amplify-cli/issues/839
Installing the amplify CLI globally is unfortunately a show stopper for me.


Converts ancestor positioning error to warning

Fixes #64

Interesting. I hadn't thought of the fact that you might render the waypoint in a hidden container. I wonder if changing to a warning gets to the root of the problem though. Can we detect this some other way, and avoid the warning (and error) altogether? There's also a workaround you can apply in your application code: avoid rendering the waypoint until the container is visible. That may or may not be easy, depending on how your element hierarchy looks like.
Any direction you take, we'll need the tests fixed to reflect the new behavior.
Thanks for taking the time to put together a PR @kenaniah!

We are seeing something similar - when our component is mounted, for some reason node.offsetParent is always null - it only becomes non-null later on. So we get the same error.
Changing this to a warning would at least let us proceed, though it's not ideal. Simply not triggering any events until node.offsetParent is there is one option. Another would be to keep the warning (as it probably often helpful) but pass in some sort of flag that suppresses the warning for situations where this behaviour is needed.

Thanks for providing more context @tomdcc. If you can figure out why node.offsetParent is null, drop a line in this thread.
The main issue I have with simply changing to a warning is that it will cause the _distanceToTopOfScrollableAncestor(node) to return something that we then use to calculate whether or not the waypoint is in view. If this number is incorrect, the waypoint won't work the way it's supposed to. I wonder if we should introduce a new position called invisible. We can throw a specific error from _distanceToTopOfScrollableAncestor(node) to signal this state, and catch that error in _currentPosition. Then we won't have to throw any error, nor warn about it. And people can inspect the waypoint component using React devtools to figure out that it ends up in this state.
Since it's probably easier for you to try this out @kenaniah and @tomdcc, would any of you like to take it on? If not I'll get to it when I have a few cycles over, but I can't promise that will be any time soon.

@trotzig I've submitted PR #67 which introduces an invisible position.

Closing this PR since it was fixed by #67. Thanks everyone!


Fixed PDB incorrectly matching Job pod

Signed-off-by: Marcus Noble<EMAIL_ADDRESS>
This PR:

Fixes PodDisruptionBudget incorrectly matching the completed restarter Job pod.

This was incorrectly blocking a node from draining due to incorrectly thinking the maxUnavailable was already reached. To be safe, I've also switched to minAvailable as it's more correct.
Checklist

[x] Update changelog in CHANGELOG.md.
[x] Make sure values.yaml is valid.

nice find, we should release default-apps as well

nice find, we should release default-apps as well

Yup, that's next on my todo list :)


[Appconfig] Move samples out of tests

Following guidelines from: https://github.com/Azure/azure-sdk/blob/master/docs/engineering-system/repo-structure.md

@KrzysztofCwalina for samples is the idea that they should be Tests or small applications? I think applications would be more interesting but I'm not sure what the arch board was hoping from for them.

I think applications would be more interesting but I'm not sure what the arch board was hoping from for them.

One advantage of them being tests is that we are sure they work without having to invent an additional infrastructure.

That is true but they are less useful for folks that want to try and write little apps so get started. As for verifying they don't break we should definitely come up with a strategy for that also, currently these are the first samples so I don't even thing we are building or running them yet in any case.

Agree that we need to decide between having samples as tests or as apps.
For now I am going to merge the PR and work on release AppConfig. Issue https://github.com/Azure/azure-sdk-for-net/issues/6150 created to follow up on the conversation


SharedTable and Path2dControlPoint Type fixes

This PR changes the arg of SharedTable to optional and adds path2dcontrolpoint type to suppress error

Thanks!


Fix ui-test-app initialization for Electron

@DanEastBentley can you please test and make sure everything (both web and electron) work correctly for you now?

@jffmarker this PR has your fix too. Please verify

@jffmarker this PR has your fix too. Please verify

Looks better to me; thanks.


Provide instructions on how to use Registry mirrors in other regions

I don't think we need to repeat the documentation three times. It's only necessary to have the detailed documentation in the README.md with links in .env and the Vagrantfile pointing back to that. This would make it easier to maintain over time.
Also note that it's not just the Region Key that can be used. The following are all valid aliases for a mirror:

container-registry-<region_name>.oracle.com, e.g. container-registry-sydney.oracle.com
container-registry-<region_identifier>.oracle.com, e.g. container-registry-ap-sydney-1.oracle.com
container-registry-<region_key>.oracle.com, e.g. container-registry-syd.oracle.com

Ok. Thanks @Djelibeybi . So I'll close this PR and open an issue. It's valid to have the regions documented somewhere.

You don't need to close this PR. I'm just asking you to adjust it. :)

ok. I'll work on that later today.

For the README.md I would use language similar to this:

For performance reasons, we recommend using the closest Oracle Container Registry mirror
to your region. A list of available regions can be found on the Regions and Availability Domains page of the Oracle Cloud Infrastructure documentation.

To specify an Oracle Container Registry mirror, either edit the Vagrantfile or install the vagrant-env plugin and create a .env.local file that specifies the mirror.

The following syntax can be used to specify a mirror: container-registry-<Region Key>.oracle.com. For example, to use the mirror in Melbourne, specify container-registry-mel.oracle.com .

Thanks @Djelibeybi . PR updated.

Nice. Merged!


Absolute path load chunk

What kind of change does this PR introduce?

Bug, follow up from https://github.com/webpack/webpack/pull/5587
Did you add tests for your changes?
Not yet, let's discuss the PR first

If relevant, link to documentation update:

Summary

This new PR is an attempt to correctly set the source url to get the chunks. If publicPath is set, use it, otherwise set it to "/"
Does this PR introduce a breaking change?
Not that I am aware of.

Other information

"" is a valid public path. It defaults to the current directory. It seems like your use case is different, in this case pass "/" to output.publicPath. The current behavior is correct and do not required changes.

As already stated many times, settings / to output.publicPath doesn't work at all as it will try to get http://app.js which is not even a valid URL.
When output.publicPath  is set to ""  and the url is http://localhost:8080/admin, it doesn't work either as it will try to get "http://localhost:8080/admin/2.js"
The problem exists and is genuine. The current behaviour is not correct and requires change.
What's your solution for this issue ?


🐞 - Cannot create proxy with a non-object as target or handler

Playground Link
https://stackblitz.com/edit/angular-gwybp9?file=src%2Fapp%2Fapp.component.html
Description
error occurs when using primitive as context in tooltip

related #175
Angular version
12>
Taiga UI version
No response
Which browsers have you used?

[ ] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

Which operating systems have you used?

[ ] macOS
[ ] Windows
[ ] Linux
[ ] iOS
[ ] Android

Not sure this is a valid error. Maybe we should just document context better, that it has to be an object? Supporting a primitive makes it impossible to use with templates, which breaks uniformity. However sometimes primitive does make sense, if we intent on using functions or components only 🤔


Question about GUI Availability and Usage Instructions

Hello, dear Mehdi Hadeli.
We are using this project at university pracitve for infosec, testing SonarQube, pentesting and other.
I would like to inquire if there is a graphical user interface (GUI) available in this project. If so, could you please provide some guidance on how to access and use it?
Thank you for your help!
Best regards, Roman Puhlenkov

Hi,
No UI currently, maybe in the future.

Can you explain the main idea of app? How we can use it? And can you suggest what we as infosec can do with this project ?

This is a microservices architecture sample in golang just for practicing different technologies in a project, if someone need to implement a microservices based application they can get some idea from this project. Maybe it is not good for your usage.


Feat: Add stop command

As alias for shutdown

should we rename the command?

I have no opinion on this. @kaufmo suggested adding it as alias

stop is easier to guess than shutdown, and I don't see a reason for two commands that do the same.

Ok I'll remove the shutdown command then


Unable to run reactjs in 64 bit mode

I have followed http://reactjs.net/getting-started/tutorial.html to ge tstarted with RectJS.
The first step works fine running in IISExpress. However running the same example in "real" IIS does not work. I Get the following error:
 Server Error in '/' Application.

 Unable to resolve type: React.Web.IJsxHandler

 Description: An unhandled exception occurred during the execution of the current web request.   Please review the stack trace for more information about the error and where it originated in the code.

 Exception Details: React.TinyIoC.TinyIoCResolutionException: Unable to resolve type: React.Web.IJsxHandler

 Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

 Stack Trace:

[TinyIoCResolutionException: Unable to resolve type: React.Web.IJsxHandler]
       React.TinyIoC.TinyIoCContainer.ResolveInternal(TypeRegistration registration,     NamedParameterOverloads parameters, ResolveOptions options) +1165
   React.TinyIoC.TinyIoCContainer.Resolve() +163
   React.Web.JsxHandlerFactory.ProcessRequest(HttpContext context) +52
   System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +913
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +165

If I set  "Enable 32 bit applications" to true in the application pool, the solution starts to work.
Based on this I guess the problem is related to instansiating  the 64bit react dll (or v8 component)
I have tried installing the x64 runtime components but to no help.

Hmm, I guess this has something to do with the native library (V8) used by ClearScript.
Does that exception have an InnerException? Try attaching a debugger to the 'real' IIS and see. If it's a remote server, you can use the remote debug functionality in Visual Studio.

In the debugger I get: " ReactJS.NET has not been initialised correctly." when running as a 64 bit process.

What's the InnerException? The very innermost InnerException should have more detail.

InnerException :
TinyIoC.TinyIoCResolutionException: {"Unable to resolve type: React.IReactEnvironment"}
Data: ListDictionaryInternal (count 0)
HelpLink: null
HResult: -2146233088
InnerException: null
Message: Unable to resolve type: React.IReactEnvironment
Source: React
StackTrace:    at React.TinyIoC.TinyIoCContainer.ResolveInternal(TypeRegistration registration, NamedParameterOverloads parameters, ResolveOptions options)
at React.TinyIoC.TinyIoCContainer.ResolveResolveType
at React.Web.Mvc.HtmlHelperExtensions.get_Environment()

Any resolution to this? I have the same situation happening. The difference with me is that I am building from source and adding support for a ServiceStack AppHost.
Thanks!

Closing issues older than a year, please re-open if you think this is still relevant.


Feature request: Swipe to return to main menu

App version: 1.2.1
I would like to be able to use a left-to-right ("back") swipe gesture to return from a game to the main menu. As a long-time user of the original ghewgill app, this is probably the feature I miss the most from that app. The current "back" options work, but they are not as natural as swiping.
Looking at the ghewgill app's behavior as a point of reference, it seems like the "back" gesture only works when you initiate it from the edge of the screen. I think that this is pretty natural and makes sense (you wouldn't want a user to be swiping in the middle of the screen to interact with their game and be taken back to the main menu).

Some backstory: The swipe back gesture is intentionally disabled because the swipe area eats long presses - if you try to long press through it, it will instead always treat it as a short press. Super frustrating when you're playing mines and you're trying to mark a bomb!
But, this is fair - depending on what games you play it may not always be an issue for you. I'll look into what it would take to make this an app setting to re-enable the swipe gesture.

This makes a lot of sense, and explains why the old ghewgill app's far-left columns on certain games would occasionally not register long presses. Short of forcing some extra padding on the left-hand side of all games (sort of a "back swipe dead zone"), I see how this could be challenging to address.
I think the current strategy of having both a "back" button in the upper-left and a "back" option in the bottom-left menu makes sense in light of that, and for me it's just a matter of retraining muscle memory. Part of me does wish, however, that there was a way to go back with a single press with something near the bottom-left, instead of the 2 that it takes to use the bottom-left menu currently. Perhaps the "back" option from the bottom-left menu could be moved to a dedicated button at the bottom of the game area, above where the bottom-left menu's button is? Not sure that that would be feasible, but it could be a good compromise.

Optional feature released in 1.3, closing as complete

I've found that if you press-and-drag-up that bottom button, you can open the menu and access the back button. Easily accessing the back button was something I wanted too, and that's the flow I've adopted. Try it out and see if it works for you!

This actually works pretty well, I never would have thought of this myself.
That said -- I've been running 1.3 and the new swipe to go back feature is working 99% perfectly for me. The only game where I've noticed an issue with long presses getting eaten is Loopy (long presses on the far left edges to turn them "off"); everything else seems to work fine with my specific game sizes/settings, so for me, the tradeoff is worth it.


can we install the rezilla v2.0 with by README.md in the master?

Hi @huangliuzhou, I will update this issue as soon there is an initial working version

OK, Thank you so much! Please let me know when the first working version is update, i am holding a company in china for IOT ,I wish we can corporate in the future.

By the way ,I am willing to do the beta testing very much.

Thank you a lot, I will give an update as soon as v2 is working

@huangliuzhou I just released the v2 as promised.
Give it a try and feel free to report any issue you found. Thanks!


Does android have Signal R Android client library with sample

I like to have android version for SignalR

Have you seen either one of these samples in the main repository? (Seems like we should move the samples into their own place - I'll take that action item!)
https://github.com/aspnet/AspNetCore/tree/master/src/SignalR/samples/JwtClientSample
https://github.com/aspnet/AspNetCore/tree/master/src/SignalR/samples/JwtSample

I think this is the link you were looking for https://github.com/aspnet/SignalR-samples/tree/master/AndroidJavaClient 😃
@Ktirumalsetty We've just released the 1.0 Version of our SignalR Java client. You can see a sample (that actually needs to be updated to use the 1.0 Jars) in the link above.
Here is a link to the docs https://docs.microsoft.com/en-us/aspnet/core/signalr/java-client?view=aspnetcore-2.2.
Hope this helps!


How to figure out what in the config yaml file broke the bot?

hey @xuanxu i sent you a slack message but it might be nice to chat here openly. it seems like there are specific things in the YAML file that cause the bot to not respond. However i'm not sure how to identify what i've done wrong to break things.
i wondered if you could help me understand how to troubleshoot? it's probably hard to see if all tests  pass but the bot doesn't respond. One issue was the steps having the same name. i think i've fixed that. but now it's broken again and i'm not sure what i did. i obviously did something however.

Hey!
When the bot responds to simple commands (help, hi...) but there is a specific command where it goes silent, then probably that command is wrongly configured. But when the bot does not respond to anything usually there is something wrong in the YAML file.
The two more common causes of YAML-parsing errors are:

Invalid indentation: if tabs are added where yaml expects a couple of spaces the file becomes invalid/unparseable. We have to make sure we use the same indentation already present in the file, in this case 2 spaces.
Wrong keys: if you use an arbitrary string for a responder, that will not be recognized and the loading of the YAML file will fail. To get the exact error line of the deployed bot, you have to take a look at the logs at Heroku. You can also check you are using only available keys. see documentation here: https://buffy.readthedocs.io/en/latest/available_responders.html

Currently the test suite covers the internal code, it runs the Buffy' specs as a bots generator, it does not validate individual bot config files.

Another tool for debugging is the webhook delivery log, where you can see the server response and redeliver any past request. https://github.com/pyOpenSci/test-pyos-review/settings/hooks

thank you @xuanxu !!! i understand now!

closing this as answered!


🔀 :: (#70) 급식패스 신청시간 설정

Codecov Report

Merging #111 (c5074c5) into develop (dd53a5a) will decrease coverage by 1.97%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             develop     #111      +/-   ##
=============================================
- Coverage      45.70%   43.72%   -1.98%
  Complexity        83       83
=============================================
  Files             45       46       +1
  Lines            442      462      +20
  Branches          18       20       +2
=============================================
  Hits             202      202
- Misses           230      250      +20
  Partials          10       10

Impacted Files
Coverage Δ

...semicolon/gspass/controller/TeacherController.java
0.00% <0.00%> (ø)

.../semicolon/gspass/dto/teacher/PassTimeRequest.java
0.00% <0.00%> (ø)

...ava/com/semicolon/gspass/entity/school/School.java
20.83% <0.00%> (-10.42%)
:arrow_down:

...lon/gspass/service/teacher/TeacherServiceImpl.java
65.21% <0.00%> (-6.22%)
:arrow_down:

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 dd53a5a...c5074c5. Read the comment docs.


Help - to get the picture in PHP

Using the SDK i get following field:
Hash picture: *P¿aÁ†?y2=....
How can i decode it now into PNG or JPEG? is the has picture is in JPEG? following did not worked.
    if(count($cresult) > 0) {
      $arr = explode("\n", $cresult[0]['card']);
      $encodedPhoto =str_replace("Hash picture: ", "", $arr[18]);
      //header('Content-Type: image/jpeg');
      echo "";

    }

Shamun,
The hash of the picture does not contain the actual picture data but is used for verification purposes. If you want a picture, you can look at the example in https://github.com/KeejOow/eidlib/blob/master/eidlibsamples/src/be/belgium/eid/samples/InformationRetrieval.java.
eID.getIDPhoto()

Returns an IDPhoto object with a number of methods to write the file, get the raw data, convert the file, and so on.

@KeejOow : Thank you. My situation is the picture has to be sent to a server (not the case writeToFile() method).
I checked eID.getIDPhoto() methods which has getImage(), getPhoto(), verifyHash(byte[] hash).
Now, Which method gives me RAW PNG or JPEG data? I have to save that data over GET or POST method to PHP server and then display it to a web-browser.

Dear,
eID.getIDPhoto().getPhoto() returns a byte array that you can send to the
server.
Cheers,
Kristof.
On Wed, May 27, 2015 at 9:30 AM, Shamun Toha<EMAIL_ADDRESS>wrote:

@KeejOow https://github.com/KeejOow : Thank you. My situation is the
picture has to be sent to a server (not the case writeToFile() method).
I checked eID.getIDPhoto() methods which has getImage(), getPhoto(),
verifyHash(byte[] hash).
Now, Which method gives me RAW PNG or JPEG data? I have to save that data
over GET or POST method to PHP server and then display it to a web-browser.
—
Reply to this email directly or view it on GitHub
https://github.com/KeejOow/eidlib/issues/5#issuecomment-105798607.

--
Met vriendelijke groeten,
Kristof Overdulve.

OK - Many thanks.

Can you please check why i cant see picture?
I tried following but i cant see the picture yet? i used eID.getIDPhoto().getPhoto()   and got some value like<EMAIL_ADDRESS>then i used that value but not showing any picture.
<?php
$byteArray = "[B@14a3da8";   //eID.getIDPhoto().getPhoto()  Java SDK returned this value
$byteArray = base64_encode($byteArray); // Try with encode or without
$img = "";
echo ($img); // Should show the picture now in web browser but nothing is showing.
exit;
?>

Well .. cause a byte array is a binary structure and what you are posting
is the object reference to the full object. It would be one hell of a
compression algorithm if an image would be encoded as less than 20 bytes.
You can perhaps compute a base64 encoding of the image in Java and then
copy that into the PHP byte array.
Cheers,
Kristof.
On Wed, May 27, 2015 at 10:00 AM, Shamun Toha<EMAIL_ADDRESS>wrote:

Can you please check why i cant see picture?
I tried following but i cant see the picture yet? i used
eID.getIDPhoto().getPhoto() and got some value like<EMAIL_ADDRESS>then i used
that value but not showing any picture.
";
echo ($img); // Should show the picture now in web browser but nothing is showing.
exit;
?>
—
Reply to this email directly or view it on GitHub
https://github.com/KeejOow/eidlib/issues/5#issuecomment-105809259.

--
Met vriendelijke groeten,
Kristof Overdulve.


KMODE_EXCEPTION_NOT_HANDLED (1e) on systems with HVCI

Describe the bug
On a system with Hypervisor Code Integrity (HVCI) enabled a KMODE_EXCEPTION_NOT_HANDLED bugcheck is triggered.
To Reproduce
Turn on Code Integrity checks in Driver Verifier and spawn a new x360 or ds4 pad.
Expected behavior
No crash obviously 😛
Screenshots
If applicable, add screenshots to help explain your problem.
System details (please complete the following information):

OS: Windows 10 (all builds)
Feeder software: doesn't matter
Driver Version: <IP_ADDRESS> until <IP_ADDRESS>

Output of !wdfkd.wdflogdump ViGEmBus:
57: FxIoQueue::Vf_VerifyForwardRequest - Cannot forward a request to a different WDFDEVICE 0x00007CF5A1B7A308

Fixed in v1.16.112


preferred format for static meshes

Should docs/examples prefer a particular format for static meshes?  Or rather demonstrate the ability to read from multiple formats?
The first split is between the internal JSON format and whatever can be read from meshio.  The second split, in the latter, is between Gmsh's MSH, which can contain subdomains and boundaries (as (n − 1)-dimensional cells), other formats in which subdomains and boundary-facets have been encoded using #680, and other formats which are just plain meshes without subdomains or boundaries (e.g. which might have those defined subsequently using .with_boundaries, &c.).  Thus:

skfem.io.json.
skfem.io.meshio

Gmsh's MSH

MSH 4.1 (see also #695)
MSH 2.2

meshio-read formats with subdomains or boundary-facets encoded using #680
meshio-read formats of plain meshes without subdomains or boundaries

Does that cover it?

Should the old internal JSON format be deprecated?  It does have the advantage that it depends only on the Python Standard Library, not using meshio (which does evolve, sometimes by leaps & bounds).  It's portable in that it is JSON but I don't think anything other than scikit-fem will understand the encoding within the JSON.  There's also the slight disadvantage that the serialization of subdomains and boundaries in the JSON differs from that adopted in #680: it lists indices of subsets of cells and facets rather than enumerating the corresponding indicator-function for the subdomains or the indicator function multiplied by binary-encoding of subsets of facets for boundaries.  It's probably not worth revising the JSON to match the new serialization, but what's the role of the JSON henceforth?  I don't have an opinion on this, I probably won't use it much given the new options available in #680 (unless maybe a makeshift is required during a future upheaval of meshio).
I don't think there's anything that needs doing here, unless it is to replace the JSON in docs/examples/meshes should the decision be to deprecate it.

It might be worthwhile indicating to the user what a good fast compact format for serializing meshes with subdomains and boundaries (and possibly other point- or cell-data).
I did have some findings on this in #680 (2021-08-10) and #693.
In the former:

One slight disappointment is that the new docs/examples/ex28.msh is 156K whereas the old JSON was only 52K. A bit of a shame since the latter is not compressed at all and was hardly designed for efficiency. VTK is a bit better at 128K and parity is restored with XDMF at 48+4=52K, with the additional requirement of h5py (not difficult but it is an additional requirement). I suppose all our simple boolean arrays of indicator functions for subdomains and uints for boundaries are getting stored as big floats (float64?). I don't think this matters too much; in particular I don't think it is too much to pay for the ease of being able to immediately open the VTK or XDMF in ParaView and immediately see each subdomain and boundary, along with e.g. point_data={"temperature": temperature[basis["heat"].nodal_dofs.flatten()]}. Conclusion: the indicator functions are verbose but portable, which is a fair compromise and probably the right one to make her

In the latter, some steps were taken to replace the JSON but withdrawn as that made the pull-request as too composite. It was replacing
https://github.com/kinnala/scikit-fem/blob/e4a4b2b87072ece9cd386fb83d67adff54031ff5/docs/examples/ex27.py#L109
with first MSH 4.1 dac551a and then VTU f799d23 for exx 24, 27.  In that case, the MSH 4.1 was slightly smaller (178 K) than the JSON (193 K) and the VTU was much smaller (82.4 KB).
VTU was chosen after inspecting the charts in the meshio Performance comparision, passing over those formats don't support cell-data (Exodus) or have additional dependencies (Exodus, MED, XDMF), and formats that I just wasn't familiar with (MOAB).
I've been using XDMF heavily the last couple of years and it suits me well, but there might be situations where one mightn't want to depend on HDF5.
MSH 2.2 is a poor choice for large files because it's very slow to read.  It's one of several formats that defines the type of each cell so that the cells have to be read one at a time.  This is intrinsically slow in Python.  The fast formats have blocks of cells of the same type, which can be usually be read quickly with NumPy.  Thus when Gmsh updated to MSH 4.1, it became literally a thousand times faster to read in my real-world application.
Note that XDMF (which has quite a broad specification, only incompletely covered by meshio) writes inhomogeneous meshes
(e.g. triangles plus lines to represent boundary-facets) either as homogeneous blocks or as a ‘mixed topology’ but currently only the latter is supported by meshio (possibly pending nschloe/meshio#622) and I suspect that that would radically lower the position of XDMF in the Performance Comparison (which only compares homogeneous meshes, which are stored in XDMF by meshio as a homogeneous block).  Since #680 doesn't use (n − 1)-dimenisonal cells to represent boundary-facets, it doesn't encounter the mixed-topology problem, originally raised in xdmf#15 multiple topology blocks; this is a distinct advantage of #680.

What I think would be important is to have some serialization format which is directly compatible with other tools in the sense that if we export "boundaries" then some other FEM package can use them via their own importers. I don't yet know what is the universal format but I think it will include separate facet elements based on my brief overview.

Ah, yes, of course.  Interoperability is another very important criterion, at least equal to size and speed, perhaps moreso.  It is unfortunate that at the moment these goals conflict.
At the moment, maybe MSH 2.2 is the most widely accepted input format?  (Is that supported by your brief overview?)  By format I mean format that includes subdomains and boundaries, and accepted and understood by finite element systems.  If that's correct, perhaps we should have a method or option to save an skfem.Mesh that records our subdomains and boundaries in the way that they are encoded by Gmsh so that they can be reread by other FEM packages?  This is not exactly the way that meshio does it.  Currently we have
https://github.com/kinnala/scikit-fem/blob/a1496b67ecccd244cdb73d2a9a2fd5bc17bef266/skfem/io/meshio.py#L182-L189
When MSH 2.2 was the main Gmsh output format, which it was for a very long time, Gmsh encoded subdomains and boundaries as what it called ‘physical tags’ of cells, every cell having exactly one physical tag, using (n − 1)-dimensional cells to represent the boundary-facets. When meshio reads these, it encodes them as cell_data.   Gmsh MSH 2.2 (& 4.1) also has a separate concept of ElementData which meshio also encodes as cell_data, so meshio had just one concept corresponding to two different ones in Gmsh MSH.  This two-to-one on meshio-read causes problems on inverting: the cell_data has to be classified as either physical tag or element-data, so the special "gmsh:physical" name was invented and used in cell_data.  Currently we do decode this in
https://github.com/kinnala/scikit-fem/blob/a1496b67ecccd244cdb73d2a9a2fd5bc17bef266/skfem/io/meshio.py#L105-L121
but not re-encode it in skfem.io.meshio.to_meshio.  Should this go in _encode_cell_data?  That is, create a "gmsh:physical" list of arrays?  (Of course this encounters a difficulty when subdomains or boundaries overlap, which we have dealt with differently in #680 but which Gmsh dealt with by deprecating MSH 2.2 in favour of MSH 4.1, and we don't know how to write MSH 4.1 with more than one type of cell because we don't know how to write the new MSH 4.1 ‘entities’.)
Amongst higher-end finite-element packages, perhaps Exodus is more popular?  What was your finding in your brief overview?  It does require netCDF4; not impossible, but an additional requirement.  I'm not sure about the level of support of Exodus in meshio.  It might be possible to lift that with some careful PRs, or perhaps the necessary work can be done prior to meshio in   skfem.io.meshio.
A basic difficulty is that meshio and VTK have no real concept of subdomain or boundary.  meshio does how have cell_sets which do naturally correspond to subdomains and can also be used for boundaries via (n − 1)-dimensional cells, but nschloe/meshio#619 ‘unification of point / cell sets among formats’ seems stalled with nschloe/meshio#691 ‘Unifying point and cell tags’ having been replaced by (the less ambitious?  less prescriptive?) nschloe/meshio#704 ‘more streamlined handling of point and cell data’.
But really my question here wasn't so much about the ultimate ‘universal format’ (as desirable and worthwhile a goal as that is), but rather just the immediate consequences of the splitting up of #693: whether
https://github.com/kinnala/scikit-fem/blob/e4a4b2b87072ece9cd386fb83d67adff54031ff5/docs/examples/ex27.py#L109
is to be retained for now or the JSON to be deprecated and here replaced by something else (MSH 2.2 or MSH 4.1 straight from Gmsh, something exploiting #680, ...).
I don't think it's urgent to deprecate the JSON, but I recall the comment in #556 (2021-03-01)

I plan to deprecate our in-house JSON format and try to use something else (HDF5?) instead.

So for exx 24, 27, I have prepared the pure MSH 4.1 and 2.2 files which could be used, also the #680-style VTU, or it can be left as JSON indefinitely till something decisively better is found.  Should the file-formats used in docs/examples/meshes be overhauled?  Do we want to demonstrate multiple approaches?   Rather than pushing a particular line here, I'm more seeking an opinion, a house style guide for scikit-fem examples.


hi again

https://www.minecraft-downloads.com/minecraft-forge-mod-for-windows-and-mac/ I think forge now exists for 1.13

Bugging devs asking for updates is a sure fire way to have things not get updated. 👌


Add API to create maps at runtime

I'd be happy to review this when it's ready (if you're seeking review). I was just thinking about implementing this sort of functionality.

+1 super interested in this API!


allow popper to run workflows from submodules. issue#728

Resolution for issue https://github.com/systemslab/popper/issues/738

thanks Quincy! can you please rebase master?


Add backend handling for same filename

Closes #205

Project Description and User profileText use different backend endpoints, so not treated in Frontend.


[bug] Fails to query touched files when there is only a single commit

Steps to reproduce:

Initialize a fresh repo:

git init
moon init --yes

Configure a root moon project and set up a simple moon task:

.moon/workspace.yml:
$schema: 'https://moonrepo.dev/schemas/workspace.json'

projects:
  - '.'
vcs:
  manager: git
  defaultBranch: main

moon.yml:
$schema: https://moonrepo.dev/schemas/project.json
language: go
tasks:
  test:
    command: echo "test"

Make the 1st commit

git add .moon moon.yml
git commit -a -m "init"

moon ci fails:

❯ moon ci
▪▪▪▪ Gathering touched files
Error: process::failed

  × Process git failed with a 128 exit code.
  │
  │ fatal: ambiguous argument 'HEAD~1': unknown revision or path not in the
  │ working tree.
  │ Use '--' to separate paths from revisions, like this:
  │ 'git <command> [<revision>...] -- [<file>...]'

Hah this is a good one. I'm kind of leaning towards not fixing this though, as it'll add overhead of detecting the commit count for all CI runs, and it doesn't affect the majority of users.

Yeah it's an edge case for sure, but it does hit people who are trying it out for the first time and gives a bad impression. Maybe just a better error message in this case?

Yeah I'm thinking about this. Maybe git has some config/option that may be useful here.

Ended up adding it to 1.16

This still isn't fixed for me, but I just made a new commit and it was fine so


Public user profile

Hi I came across this project recently and I loved it.
I have some question and one is that can we share our stats in public profile like this:
https://wakatime.com/@ariaieboy

Hi @ariaieboy, glad to hear that! :-) I'll add this as a feature request. Implementing this would probably take a bit, though.


[vcpkg Readme] Added x64 triplet note for Windows Quick Start

Describe the pull request
Adds a note to the README.md about default installation being x86, and an example of how to target x64 instead.

What does your PR fix?
Not a fix, but inspired by #1254 and #12357

Which triplets are supported/not supported? Have you updated the CI baseline?
N/A

Does your PR follow the maintainer guide?
Yes

@MarkIngramUK, thanks for the PR!
This also resolve https://github.com/microsoft/vcpkg/issues/16924#issuecomment-808851643.

@MarkIngramUK, thanks for the PR!
This also resolve #16924 (comment).

Looking through that issue, it seems the reason x86 is still the default, is because Visual Studio also defaults to x86 for new projects. Is this still a requirement (keeping the defaults in-sync)? If not, I'd like to change (in a future PR) the default triplet to x64 on Windows, with the fix proposed in #12357. I won't work on it if the change isn't wanted though :-)

@MarkIngramUK, adding a note to readme is fine, please don't change the default triplet to x64 in this PR, I think we will do that if we decide to change it.


The system supports having sub categories of of work processes that nests skills under it

See example:
WIN_Robotics_Skills_Outline (1).xlsx
And discussion:
Jeanine Soterwood 11:26 AM
Hmm, could we just add a category to the OccupationStandardSkill table with a category…? Or would it really need to be on the Skill table? Like if we added it to the Skill table, then we could be unique across [:category, :description]…?

Or do you feel like we would need another intermediate table?
pcushing 11:28 AM
Honestly, whatever's easiest.
On WorkHands, for the few cases like this, we just stick it in the text like "Safety Procedure - This is a safety procedure skill".
I'd want to be a bit more sophisticated here but dont want to have to tie ourselves in knots, make every other query more difficult, etc. in order to support this

@Pcushing should I modify the import script to handle the new subcategories, or not worry about that for now?

@littleforest yes. Let's do that as it's the main way for us to get this info imported.


runtime: add GODEBUG=traceinit=1 support

Note: Like #38714 this is not a proposal for the proposal process.
This issue is to discuss and track the addition of support for init function tracing through GODEBUG for ad hoc debugging and profiling of init start times.
For the first minimal implementation (future iterations can expand functionality) I think that just showing the package name, start time of the init function, wall clock duration and total heap allocated bytes and number of allocs is sufficient. Later information like module version could be added.
Due to larger complexity and limited utility init tracing of plugins is not supported.
Having a more structured format like json output is omitted and likely needs a more holistic approach and decision in unison with adding support for gctrace in json format too.
Prototype CL: https://go-review.googlesource.com/c/go/+/254659
Example output:
$ GODEBUG=traceinit=1 go test
init internal/bytealg @0.008 ms, 0 ms clock, 0 bytes, 0 allocs
init runtime @0.059 ms, 0.026 ms clock, 0 bytes, 0 allocs
init math @0.19 ms, 0.001 ms clock, 0 bytes, 0 allocs
init errors @0.22 ms, 0.004 ms clock, 0 bytes, 0 allocs
init strconv @0.24 ms, 0.002 ms clock, 32 bytes, 2 allocs
init sync @0.28 ms, 0.003 ms clock, 16 bytes, 1 allocs
init unicode @0.44 ms, 0.11 ms clock, 23328 bytes, 24 allocs
...

/cc @mknyszek @aclements @randall77 @prattmic @josharian

Sorry if this is a silly question; is it not possible to start a pprof profile and end it right before starting main?

In principle possible with the following caveats that come into my mind:

to be able to profile all std lib packages one would need to find the first init function and start the profiling in there or add a GODEBUG flag to immediately start profiling (the user wanting to trace might not have the ability to change the std library)
interrupt driven profiling is sample based and especially for small init functions will require a lot of samples to approximate all init runtimes. we can instead measure with init tracing the same values we are trying to sample with profiling.
profiling flame graphs or summaries usually do not have any ordering (init foo happend before init bar)


Invalid hook call. when using in next.js

Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons: 1. You might have mismatching versions of React and the renderer (such as React DOM) 2. You might be breaking the Rules of Hooks 3. You might have more than one copy of React in the same app See https://fb.me/react-invalid-hook-call for tips about how to debug and fix this problem.

Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons: 1. You might have mismatching versions of React and the renderer (such as React DOM) 2. You might be breaking the Rules of Hooks 3. You might have more than one copy of React in the same app See https://fb.me/react-invalid-hook-call for tips about how to debug and fix this problem.

Can you provide me more details? When is that happening?

I upgraded to 0.5.3 and the problem does not recur


Theano error during training

Dear all,
I'm using DeepMedic as part of my MSc Dissertation to segment the ISLES 2017 data, so first of all I thank you for making DeepMedic available and with such nice instructions to facilitate its use.
To the matter at hand, I'm having a problem with Theano throwing an exception during training, the error is shown in the file attached (theano_error.txt). I'm also attaching the full output of a training session (output_with_error.txt) plus the configuration files I'm using (modelConfig.txt, trainConfig.txt).
output_with_error.txt
theano_error.txt
modelConfig.txt
trainConfig.txt
This error seems to happen rather randomly, but always during the training on segments phase.
I'm using two different computers at the moment:

PC0: 16GB RAM and 1070 Ti (8GB). Ubuntu 17.10.
PC1: 8GB RAM and GK110 TITAN (6GB). Ubuntu 16.04.

While I initially had the same problem in both computers, reducing the segment size to patch size, [17,17,17], and using a batch of 32 on PC0 allowed me to complete a full training run. However, a segment size of [17,17,17] and a batch size of as little as 4 didn't avoid the error in PC1. The error and output I've posted are therefore from PC1.
Given the information above, my guess is that this error is memory related, but I can't be sure because the thrown error doesn't seem to mention any of that, or maybe it does implicitly and I'm not understanding it. Even so, I can't be sure if it's either the RAM of the GPU memory. It specially annoys me is the fact that the error is thrown "randomly", never in a specific epoch or subepoch, so it's more difficult to trace its nature.
It is worth mentioning that both deepMedic and tinyCNN examples run flawlessly in GPU. Also, I'm using deepmedic-0.6.1.
If you need more information, please do not hesitate to ask further.
Thanks a lot.

Hello there, sorry for the error.
These Theano-errors are quite a thing to debug.
From the error, I see nothing that indicates it's a memory problem. Especially on the 16GB RAM you should not get a memory problem (provided that you dont run anything else on it).

You can check if it's memory error by running the process, and do "htop" in unix, and then keep on looking for a few minutes the memory bar, to check if it ever goes up to 16GB/8GB.

The line in the error that attracted my attention is:
IndexError: index 2 is out of bounds for axis 1 with size 2
Apply node that caused the error: AdvancedIncSubtensor{inplace=False,  set_instead_of_inc=False}(HostFromGpu(gpuarray).0, Assert{msg='`x[i]` and `y` do not have the same shape.'}.0, TensorConstant{[[[[0]]]

Something in the code tries to grab index array[2] when array has only 2 elements.
I remember getting such an error during training when I would (by mistake) use a model with 2 output classes while in the Ground Truth labels there would be more than 2 classses (ie, pixels with values >=2).
My assumption is that, in your GT labels there are voxels with value >1, while you specify a network with only 2 classes. And by going at segment_size = [17,17,17], (eg only 32 voxels per batch when batch-size =32), than with a large segment, and so you randomly hit those >1 GT voxels less frequently.
Before we look into anything further, do me a big favor for diagnosis:

Can you change your modelConfig to have 3 classses? Or more, eg 5. Does not matter if more, less is problem. And then run the same training process. If it does not break, it indicates I may be right in the above.
You can also right a script and go over your whole database, and do a check if any voxel in any ground-truth label nii has a value >1. If yes, then this is your problem. You ll need in modelConfig a net with >2 classes.

Let me know if you try any of these, and I ll try to advice after that.
K

Hello again,
Your intuition was right, my GT labels weren't binary, as they were supposed to be. The problem originated during the resampling/registration step of my data preprocessing script. I was using continuous interpolation for all sequences, but GT label sequences need nearest neighbour interpolation instead.
I expect this will fix the problem, I will run the network asap and let you know if it's still not working.
Thank you very much.


word by word audio improvements

in the last release, @sharabash added a great new hidden feature, which is the word by word data for some of the qaris (such that clicking a word would recite just that word).
i'd like to propose one change, which is instead of playing the word when it's clicked, to instead highlight each word as it plays. since these are still parts of recitation, this will be more accurate (from a listening perspective), and will also add a hugely beneficial feature, which is highlighting whatever is playing (including the words).

Fixed by https://github.com/quran/quran.com-frontend/pull/360


Detect and abort when Mac is set to only allow Mac App Store installations

(cannot re-open #477, so creating a new issue)
https://github.com/Installomator/Installomator/pull/477#issuecomment-1442713266

It may be worth re-considering allowing installomator to still run and even install apps when the system is set to only allow Mac App Store apps to run, because it is possible for a user to selectively override that setting to manually allow specific apps to run (this change would mean not considering an spctl assessment rejection and non-zero exit code a failure and instead only manually verify that the app is notarized based on the output).
Obviously I think this is a pretty bit edge case, but allowing installomator to install the apps when they are properly notarized and then leaving whether or not they are able to be launched up to Gatekeeper and the user themself may make sense since there isn't a scenario where it's technically impossible for the app to be run.


chore: default list methods to descending order

Description
Default list methods to descending order.
Documentation
Does this require changes to the WorkOS Docs? E.g. the API Reference or code snippets need updates.
[ ] Yes

If yes, link a related docs PR and add a docs maintainer as a reviewer. Their approval is required.

Codecov Report
Attention: Patch coverage is 66.66667% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 85.89%. Comparing base (b816b6c) to head (460bef5).

Files
Patch %
Lines

workos/directory_sync.py
50.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #234   +/-   ##
=======================================
  Coverage   85.89%   85.89%
=======================================
  Files          31       31
  Lines        1234     1234
=======================================
  Hits         1060     1060
  Misses        174      174

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


:construction: Feat(utils): Add additional ethereumjs utils

Description
Concise description of proposed changes
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1025  👈
#1024
#1023
main

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

Join @roninjin10 and the rest of your teammates on  Graphite


Positive Pixel Count plugin expects user input for "output parameters"

Hi,
Please see the screenshot below. HistomicsTK is asking user input for output parameters in the positive pixel count plugin. I am confused as if these parameters are really 'output' parameters then there's no need to manually input values for them, right?
For now I can just enter 0 for all of them in order to submit the job but it might be something needs to be fixed.
Thanks,

I think we solved this issue in https://github.com/girder/slicer_cli_web/pull/43.  We should probably try to get that merged in.

May I ask when will the fix be merged in?

I resolved all the conflicts with master.  There are still testing errors, but they are unrelated to my changes.  It could be reviewed as is, but @cdeepakroy seemed to indicate that we are moving to taking a different approach with output files.  If that is the case, then these changes probably don't make sense.  I'll leave it to @cdeepakroy if he thinks we should go ahead with it.

https://github.com/girder/slicer_cli_web/pull/43 was merged some time ago.


Unable  to map a new winappdriver to the existing open application

At the end of first test case, closed the winappdriver.exe and then open new winappdriver.
The application is already open but now the driver is unable to map the application.
Kindly help please

ritusenleo Please post code example and error that you got.

You need to attach to root window, find your application by window name or class name and switch window handle to it.

It is solved now, I just close and thenopen the driver in between the tests


Improved readability of TensorFlow description.

Slightly altered the README file of TensorFlow to become more readable, and included a missing indefinite article in the same file.

Hi @soosung80 / @joefernandez Can you please review this PR ? Thank you!


Allow undefined bufferViews in glTF accessors

See https://github.com/KhronosGroup/glTF/issues/2169.
According to the glTF spec, if accessors don't have a bufferView, they should be all zeroes.
This also removes the code to convert non-float joints to float as that is no longer necessary. It was originally for Babylon Native.

[x] Tested changes with Babylon Native master.

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

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


allow request_id to be falsy but not None, fix #56

Addresses https://github.com/bcb/jsonrpcserver/issues/56

Good pickup, thanks.
Will push to pypi later today.

You rock, thanks!

Released in 3.5.3.


Late instantiation of the RadioGroup control in the Android renderer fails to display

My app is using a TabbedPage where each of the child pages are creating their content at the moment the page is selected (UI virtualization). The implementation of this concept is done by my TabbedPageExt plugin. https://www.nuget.org/packages/CwwOnline.TabbedPageExt.Xamarin/.
It works basically as follows:

Each child page is of class TabPage and is created when the TabbedPage is created.
A TabPage receives a ContentPage type and page instantiation parameter.
When the user taps on a TabPage then TabPage instantiates the ContentPage and then uses the ContentPages's Content object and ToolBarItems as its own object and items. That is the idea of delayed page instantiation (sometimes called ui virtualization).

The issue now is that when a child page contains a SegmentedControl the plugin displays correctly on iOS but not on Android; the RadioGroup and buttons or not displayed when the user selects a page containing a SegmentedControl.
I took your code and looked at it and it seems that the reason for the error is in the delayed setting of the RadioGroup control. As it is now, the control is set when a size-changed event occurs on the SegmentedControl object.
I modified your code and set the native control immediately in ElementChanged (where it should be as per xamarin guidelines) and that solves it.
Any reason why it is not done in ElementChanged?

Where is Xamarin Guidelines says it should be done in ElementChanged?

And how to reproduce this because i have it working on a TabbedPage without any issues.

This issue must be related to the other plugin you are using.

Alex,
It doesn't say it explicitly but (as written in https://developer.xamarin.com/guides/xamarin-forms/application-fundamentals/custom-renderer/introduction/) xamarin mentions it as the method in which the native control 'often' is instantiated. In all of their example renderers the control gets instantiated there.
Anyhow, I have modified your Demo project (which I got from Github) to try to find in which circumstance it goes wrong. As I expected the issue where the radiogroup control doesn't appear comes up when the SegmentedControl is not defined immediately when the ContentPage is created but later, e.g. as the result of some user action, or (as in my TabbedPageExt plugin) when the SegmentedControl is created outside of the page). You can easily test this (as I did) with a 'normal' TabbedPage where there is a button that lets the user create/destroy the SegmentedControl.
I did the following in your Demo project:

Created a DynSCPage.xaml:

DynSCPage.xaml.cs:
public partial class DynSCPage : ContentPage
{
SegmentedControl.FormsPlugin.Abstractions.SegmentedControl _segControl;

public DynSCPage()
{
InitializeComponent();
Title = "Inserted SC";
}
void SegControl_ValueChanged(object sender, EventArgs e)
{
this.SegContent.Children.Clear();
switch (_segControl.SelectedSegment)
{
case 0:
SegContent.Children.Add(new Label() { Text = "Items tab selected" });
break;
case 1:
SegContent.Children.Add(new Label() { Text = "Notes tab selected" });
break;
}
}
  private void Button_Clicked(object sender, EventArgs e)

{
if (_segControl == null)
{
_segControl = new SegmentedControl.FormsPlugin.Abstractions.SegmentedControl();
_segControl.Children.Add(new SegmentedControl.FormsPlugin.Abstractions.SegmentedControlOption() { Text = "Items" });
_segControl.Children.Add(new SegmentedControl.FormsPlugin.Abstractions.SegmentedControlOption() { Text = "Notes" });
_segControl.ValueChanged += SegControl_ValueChanged;
segContainer.Children.Add(_segControl);
}
else
{
segContainer.Children.Remove(_segControl);
_segControl = null;
}
}
}

Instantiated 2 TabbedPages in App.xaml.cs:

MainPage = new TabbedPage { Children = { new DemoPage(), new DynSCPage() } };
Doing the above indeed shows the problem where the SegmentedControl doesn't show in SynSCPage when the user clicks the button.
As I mentioned before, when I move the instantiation of the radiogroup to 'OnElementChanged' eveything is OK.
Hope this helps?
Best regards,
Jos

Van: Alex Rainman<EMAIL_ADDRESS>Verzonden: vrijdag 1 september 2017 17:36
Aan: alexrainman/SegmentedControl
CC: Jos Huybrighs; Author
Onderwerp: Re: [alexrainman/SegmentedControl] Late instantiation of the RadioGroup control in the Android renderer fails to display (#45)
Where is Xamarin Guidelines says it should be done in ElementChanged?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/alexrainman/SegmentedControl/issues/45#issuecomment-326612752, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAXMpGD_LfnfNtrGpo0T5EAE03BxIAynks5seCR5gaJpZM4OnX7w.

I have another control, the CarouselView, that uses the same init technique and its about to be included in Xamarin.Forms 3 release :)
Try the last release, i fixed this issue. Thanks

Sorry to say but the issue is still in the latest release. You can easily check this by modifying your DemoPage in such a way that the SegmentedControl is not statically,  upfront defined, but is instantiated when the user presses a button in DemoPage.  The issue also comes up when there is no TabbedPage at all. You can test this by simply assigning the above listed DynSCPage to MainPage.
As I see it, the 'size_changed' event in the renderer doesn't occur in case you want to dynamically insert a SegmentedControl to the StackLayout of a ContentPage. With dynamically I mean: when the ContentPage is open and the user creates the control by pressing a button on the page.
Don't understand what you mean with CarouselView?

Van: Alex Rainman<EMAIL_ADDRESS>Verzonden: zondag 3 september 2017 15:34
Aan: alexrainman/SegmentedControl
CC: Jos Huybrighs; Author
Onderwerp: Re: [alexrainman/SegmentedControl] Late instantiation of the RadioGroup control in the Android renderer fails to display (#45)
I have another control, the CarouselView, that uses the same init technique and its about to be included in Xamarin.Forms 3 release :)
Try the last release, i fixed this issue. Thanks
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/alexrainman/SegmentedControl/issues/45#issuecomment-326805317, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAXMpI1AjKAXWzUIHmnK2b3_DHoSrQelks5seqrvgaJpZM4OnX7w.


Bugfix/filling constraint bcs

This should fix the change in https://github.com/GRTLCollaboration/GRTresna/pull/5/commits/36052c33393101621c937d41ab40ec6f2d0c86ff
In particular:

Oops! Thanks for spotting this!


Get error on docker build

Just forked and try to docker build on it. Got the following errors.  Any idea?
Step 10/21 : RUN go get github.com/turbinelabs/rotor/...
---> Running in 7d210f05d73c
package github.com/lyft/protoc-gen-validate/tests/harness/cases/go: cannot find package "github.com/lyft/protoc-gen-validate/tests/harness/cases/go" in any of:
/usr/local/go/src/github.com/lyft/protoc-gen-validate/tests/harness/cases/go (from $GOROOT)
/go/src/github.com/lyft/protoc-gen-validate/tests/harness/cases/go (from $GOPATH)
package github.com/lyft/protoc-gen-validate/tests/harness/cases/other_package/go: cannot find package "github.com/lyft/protoc-gen-validate/tests/harness/cases/other_package/go" in any of:
/usr/local/go/src/github.com/lyft/protoc-gen-validate/tests/harness/cases/other_package/go (from $GOROOT)
/go/src/github.com/lyft/protoc-gen-validate/tests/harness/cases/other_package/go (from $GOPATH)
package github.com/lyft/protoc-gen-validate/tests/harness/cases/gogo: cannot find package "github.com/lyft/protoc-gen-validate/tests/harness/cases/gogo" in any of:
/usr/local/go/src/github.com/lyft/protoc-gen-validate/tests/harness/cases/gogo (from $GOROOT)
/go/src/github.com/lyft/protoc-gen-validate/tests/harness/cases/gogo (from $GOPATH)
package github.com/lyft/protoc-gen-validate/tests/harness/cases/other_package/gogo: cannot find package "github.com/lyft/protoc-gen-validate/tests/harness/cases/other_package/gogo" in any of:
/usr/local/go/src/github.com/lyft/protoc-gen-validate/tests/harness/cases/other_package/gogo (from $GOROOT)
/go/src/github.com/lyft/protoc-gen-validate/tests/harness/cases/other_package/gogo (from $GOPATH)

That's troubling. Will have a look.

@lilida are you building from the fork? you will probably have to change github.com/turbinelabs/rotor/... to github.com/lilida/rotor/....
Have you added any new code, or are you building from a fresh clone?

@9len Yeah. You are right.

@9len Actually it is still turbinelabes under src. One thing is that the /test are in the .gitignore in lyft repo  https://github.com/lyft/protoc-gen-validate/blob/master/.gitignore

Just so I'm clear on your setup, is this right?

you cloned your fork into $GOPATH/src/turbinelabs/rotor
from that dir, you ran docker build .
:boom:

I followed these steps and am still unable to reproduce. I have a suspicion, but it's hard to prove without repro.

Yes. NVM. I think it is related to my local Mac docker (network or disk). Tried to run go install locally and a separate linux box looks fine. I will just close this. Thanks for helping.

OK! Thanks for the prompt feedback, let us know if you need any other help.


supporting the new "Policy fragments" feature in the extractor

Do you have roadmap for adding support for the new feature of apim  "Policy fragments" to the extractor

Hello @liorklein.
The issue was closed since the PR introducing exporting policy fragments functionality is merged (#775).
Please feel free to report a bug in case you will face some issues with this.
Best regards.

Hi @f-alizada ,
I have encountered a behaviour which I am not sure if it is expected or not.
I have been only able to generate the policy fragments template if I extract all api's.
For example I have an API "api_example". And a policy fragment with the following reference: api_example;rev=1/api_endpoint
Extractor Params that works:
`{
"sourceApimName": "apim-name",
"destinationApimName": "apim-name",
"resourceGroup": "rg-name",
"fileFolder": "./src",
"paramNamedValue": "true",
"paramServiceUrl": "true",
"paramNamedValuesKeyVaultSecrets": "true",
"splitAPIs": "true",
"linkedTemplatesSasToken": "needsOverride",
"policyXMLSasToken": "needsOverride",
"linkedTemplatesBaseUrl": template-url,
"policyXMLBaseUrl": template-url

}
`
When extracting all api's, the following relevant files are generated:

apim-name-policy-fragments.template.json
api_example/api_example;rev=1/apim-name-policy-fragments.template.json
api_example/api_example;rev=2/apim-name-policy-fragments.template.json
api_example/VersionSetMasterFolder/apim-name-policy-fragments.template.json
api-name-master.template.json contains reference to policy fragments

Extractor Params that do not work:
{   "apiName": "api_example",   "sourceApimName": "apim-name",   "destinationApimName": "apim-name",   "resourceGroup": "rg-name",   "fileFolder": "./src",   "paramNamedValue": "true",   "paramServiceUrl": "true",   "paramNamedValuesKeyVaultSecrets": "true",   "linkedTemplatesSasToken": "needsOverride",   "policyXMLSasToken": "needsOverride",   "linkedTemplatesBaseUrl": endpoint-url/templates/,   "policyXMLBaseUrl": endpoint-url/policies/ }
I also tried with "apiName" as "api_example;rev=1" and also adding the field includeAllRevisions to true.
Are policy fragments supposed to be generated in those cases? Thank you for your help!

Hi @leonardosantoss - please open a new issue for this problem so we can gather all the relevant information.


No module named PocketSphinx==0.8 on Ubuntu 14.04.3

While executing sudo pip install -r requirements.txt, pip says that there is no module named PocketSphinx==0.8.  After changing it to PocketSphinx==0.0.9 (PocketSphinx on PyPI) and removing SphinxBase==0.8 (as SphinxBase is installed while installing PocketSphinx), all requirements are successfully installed.
Is this problem occurring only on Ubuntu or on all platforms?
If it's occurring on all platforms, should I update requirements.txt and open a PR?

Hi Aniket,
I am developing Melissa on OS X and hence, didn't face this issue. It's fine to remove SphinxBase as it is installed while installing PocketSphinx. Let's consult @neilnelson as he is working on Ubuntu to know if he has faced this issue as well?
Thanks!

@aniketk21 Apparently I have also started to get this error, this one's on a priority to be fixed.


Graph axes should be swapped

I guess this is more of a nitpick than an outright issue, but the two axes of the graph should be swapped. The independent variable which is temperature belongs on the x axis and the y axis should be speed since it's dependent on temperature.

I'll change this in next release

Graphs swapped and Drag&Drop fixed so currently it should works much better.
When pipeline pass I'll publish AUR, cargo.io is updated


 BEFORE SUBMITTING YOUR ISSUE, PLEASE LOOK AT THE PINNED ISSUES AND USE THE SEARCH FUNCTION TO MAKE SURE IT IS NOT ALREADY REPORTED. ALWAYS COMMENT ON AN EXISTING ISSUE INSTEAD OF MAKING A NEW ONE.
Configuration

UTM Version:
OS Version:
Intel or Apple Silicon?

Crash log
If the app crashed, you need a crash log. To get your crash log, open Console.app, go to Crash Reports, and find the latest entry for either QEMU, QEMUHelper, or qemu-*. Right click and choose Reveal in Finder. Attach the report here.
Debug log
For all issues, including crashes, you should attach a debug log. Open UTM, and open the settings for the VM you wish to launch. Near the top of the QEMU page is Debug Log. Turn it on and save the VM. After you experience the issue, open the VM settings again and select Export Log... and attach it here.
Upload VM
(Optional) If possible, upload the config.plist inside the .utm. If you do not have this, you can upload the entire .utm but note this contains your personal data. Since Github has an attachment size limit, you may want to upload to another service such as Google Drive.  LMOOOOAOOAOOOOO

ohh wanna be gä.ė by deleting commments?!

HAHAHAAAA in the contribs of https://github.com/utmapp/mac.getutm.app compare osy's face with all other faces osy's clearly STÔÒPÏD!


A question about MS-SVconv code.

Thank you very much for releasing the code on torch - points3D. Now I want to further work on your work, I hope to have clean code on MS-SVconv, can you publish it? It is very troublesome to modify the part of MS-SVconv directly in torch-points3D.
Looking forward to your reply.

Hi,
Thanks for your interest in MS-SVConv.  The code of the model is here if you want to play with it. But indeed, you'll need the framework to instantiate the model (this function). You need the dataset in order to automatically instantiate the model with the right input size.you need the config file .(for example this). I hope it can help you.
I think that you don't have to clone the repo to use these functions. You can install tp3d with pip.
Actually, you're right. When I'll have time, I will publish a simple version of the code of the model here.
Don't hesitate if you have other questions.

Thank you for your replying.I look forward to your release of a simpler version.
Best wish.

Hi,
Thanks for your interest in MS-SVConv. The code of the model is here if you want to play with it. But indeed, you'll need the framework to instantiate the model (this function). You need the dataset in order to automatically instantiate the model with the right input size.you need the config file .(for example this). I hope it can help you.
I think that you don't have to clone the repo to use these functions. You can install tp3d with pip.
Actually, you're right. When I'll have time, I will publish a simple version of the code of the model here.
Don't hesitate if you have other questions.

By the way, I want to use MinkowskiEngin instead of Tensor_sparse to build a network for training. Is the result of MinkowskiEngin worse than Tensor_sparse? Or is there just a difference in speed that doesn't affect the recall results.
I looking forward your reply, thank you.

Hi @QWTforGithub ,
You can use ME instead of Torchsparse, it will not affect the result. It is the same convolution.There can be a difference in speed depending on your version of ME or Torchsparse.
Best,


[-wATCH-]— Will Smith Video Original Video Link Will Smith Video Viral On Social Media X Trending Now [1X2U3S]

20 seconds ago
L𝚎aked Video Will Smith Original Video Viral Video L𝚎aked on X Twitter Telegram
hmretdsgsd
[-wATCH-]— Will Smith ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]— Will Smith ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]— Will Smith Video Original Video Link Will Smith Video Viral On Social Media X Trending Now
Will Smith Original Video video took the internet by storm and amazed viewers on various social media platforms. Will Smith, a young and talented digital creator, recently became famous thanks to this interesting video.
L𝚎aked Video Will Smith Original Video Viral Video L𝚎aked on X Twitter
Will Smith Original Video video oficial twitter
L𝚎aked Video Will Smith Original Video Viral Video L𝚎aked on X Twitter..

hjmghjyu


Update scalafmt-core to 2.6.4

Updates org.scalameta:scalafmt-core from 2.6.3 to 2.6.4.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

labels: library-update, semver-patch

Codecov Report

Merging #847 into develop will decrease coverage by 0.06%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop     #847      +/-   ##
===========================================
- Coverage    89.34%   89.27%   -0.07%
===========================================
  Files          117      117
  Lines         9326     9326
  Branches       365      365
===========================================
- Hits          8332     8326       -6
- Misses         994     1000       +6

Impacted Files
Coverage Δ

...in/scala/com/twitter/algebird/scalacheck/Gen.scala
95.34% <0.00%> (-4.66%)
:arrow_down:

...src/main/scala/com/twitter/algebird/Interval.scala
79.13% <0.00%> (-4.35%)
:arrow_down:

.../main/scala/com/twitter/algebird/BloomFilter.scala
93.36% <0.00%> (-1.77%)
:arrow_down:

.../main/scala/com/twitter/algebird/Successible.scala
87.50% <0.00%> (ø)

.../main/scala/com/twitter/algebird/Approximate.scala
90.32% <0.00%> (+1.61%)
:arrow_up:

...om/twitter/algebird/util/summer/AsyncListSum.scala
97.67% <0.00%> (+2.32%)
:arrow_up:

...ain/scala/com/twitter/algebird/AdaptiveCache.scala
78.37% <0.00%> (+5.40%)
:arrow_up:

...main/scala/com/twitter/algebird/monad/Reader.scala
58.82% <0.00%> (+5.88%)
:arrow_up:

Continue to review full report at Codecov.

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


opener is not displayed in Homebridge, only the Bridge

I am trying to get my Nuki Opener in to Homebrdige, but I am getting only the below error message.
Maybe someone could help me with that. Many thanks in advance.
[24/07/2023, 11:11:16] [Nuki] hardware: Raspberry Pi 3B+ 1.3 (1GB)
[24/07/2023, 11:11:16] [Nuki] os: Raspbian GNU/Linux 11 (bullseye) [32 bit]
[24/07/2023, 11:11:19] [Nuki] Bridge_26D0A987: press Nuki bridge button to obtain token
[24/07/2023, 11:11:33] [Nuki] Nuki_Bridge_26D0A987: logLevel: set to 2
[24/07/2023, 11:11:33] [Nuki] Nuki_Bridge_26D0A987: Name: set to "Nuki_Bridge_26D0A987"
[24/07/2023, 11:11:33] [Nuki] Nuki_Bridge_26D0A987: Serial Number: set to "26D0A987"
[24/07/2023, 11:11:33] [Nuki] Nuki_Bridge_26D0A987: Model: set to "Bridge"
[24/07/2023, 11:11:33] [Nuki] Nuki_Bridge_26D0A987: Firmware Revision: set to "2.15.0"
[24/07/2023, 11:11:33] [Nuki] Nuki_Bridge_26D0A987: Nuki Bridge v2.15.0 26D0A987 at <IP_ADDRESS>:8080
[24/07/2023, 11:11:33] [Nuki] Nuki_Bridge_26D0A987: Name: set to "Nuki_Bridge_26D0A987"
[24/07/2023, 11:11:33] [Nuki] Nuki_Bridge_26D0A987: Configured Name: set to "Nuki_Bridge_26D0A987"
[24/07/2023, 11:11:33] [Nuki] Nuki_Bridge_26D0A987: Heartrate: set to 60 seconds
[24/07/2023, 11:11:33] [Nuki] Nuki_Bridge_26D0A987: Restart: set to false
[24/07/2023, 11:11:33] [Nuki] Nuki_Bridge_26D0A987: Log Level: set to 2
[24/07/2023, 11:11:33] [Nuki] Nuki_Bridge_26D0A987: Status Fault: set to 0
[24/07/2023, 11:11:33] [Nuki] Nuki_Bridge_26D0A987: Name: set to "Nuki_Bridge_26D0A987"
[24/07/2023, 11:11:33] [Nuki] Nuki_Bridge_26D0A987: Configured Name: set to "Nuki_Bridge_26D0A987"
[24/07/2023, 11:11:33] [Nuki] listening on http://<IP_ADDRESS>:35289/notify
[24/07/2023, 11:11:33] [Nuki] Nuki_Bridge_26D0A987: subscribe to event notifications
[24/07/2023, 11:11:35] [Nuki] Nuki_Bridge_26D0A987: Last Updated: set to "Mon Jul 24 2023 11:11:39"
[24/07/2023, 11:11:35] [Nuki] Nuki_Bridge_26D0A987: Last Boot: set to "Thu Mar 02 2023 09:54:58"
[24/07/2023, 11:11:35] [Nuki] Nuki_Bridge_26D0A987: warning: heartbeat error: RangeError: : invalid name
at Opener.set name [as name] (/var/lib/homebridge/node_modules/homebridge-nb/node_modules/homebridge-lib/lib/Delegate.js:132:13)
at new Delegate (/var/lib/homebridge/node_modules/homebridge-nb/node_modules/homebridge-lib/lib/Delegate.js:39:15)
at new AccessoryDelegate (/var/lib/homebridge/node_modules/homebridge-nb/node_modules/homebridge-lib/lib/AccessoryDelegate.js:43:5)
at new NbAccessory (/var/lib/homebridge/node_modules/homebridge-nb/lib/NbAccessory.js:14:5)
at new Opener (/var/lib/homebridge/node_modules/homebridge-nb/lib/NbAccessory.js:407:5)
at Bridge.addOpener (/var/lib/homebridge/node_modules/homebridge-nb/lib/NbAccessory.js:230:24)
at Bridge.heartbeat (/var/lib/homebridge/node_modules/homebridge-nb/lib/NbAccessory.js:287:24)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at Bridge.init (/var/lib/homebridge/node_modules/homebridge-nb/lib/NbAccessory.js:172:7)

Did you set a name for the Opener in the Nuki app?

Yes, there is a Name configured for the opener "Haustuer". I tested also another Name but still the same issue.

After Name change and bridge reboot is the system finally online. Many thanks!


Re-submit job to queue again

Dear All,
I have an object which has a refresh method to create queue object and use defer method to submit jobs.  I also implement awaitAll to emit an event.  Everything works fine in my app first run. But when I try to rerun my refresh method, I found that all jobs did submit through defer (proved by logging each callback). But I cannot see awaitAll being called.  How can I reset the queue to make awaitAll works when I re-submit jobs?  Thanks for your advice.

There is no way to reset the queue (under the current API). You must discard your existing queue and create a new one.


Line ending and trailing whitespaces

Just a minor issue - but especially annoying if you want to contribute a patch. So I would suggest to use \n and remove trailing whitespaces. I would create a pull request - but it would be outdated even before I could create it.

Yes, sorry, I missed one space. Reformatted now.


Dive into GeoConcerns : Hands-on exercises with GeoConcerns, a PCDM-based Fedora...

Dive into GeoConcerns : Hands-on exercises with GeoConcerns, a PCDM-based Fedora 4 reference implementation for geospatial resources in a repository.
Suggested by: Darren Hardy
Presenter: Eliot Jordan, Darren Hardy
Format: Workshop - half day
Audience: Managers, developers

2016-07-06
Yes, we’re planning to give this “Dive into GeoConcerns” workshop. It would be a half-day (3 hrs including a break). We require laptops with VirtualBox and Vagrant installed to follow along with the workshop — we will provide instructions beforehand if we can get an email list of participants; otherwise, they can do the installations at the workshop. We’ll work on (b) and get back to you.

2016-07-29
This workshop focuses on hands-on exercises with GeoConcerns, a new PCDM-based Fedora 4 reference implementation for geospatial resources in a repository (see http://geoconcerns.github.io), and we welcome developers and managers alike to participate. These exercises will include modeling content in Fedora 4 using Hydra’s PCDM data model. Furthermore, participants will install and configure the GeoConcerns software on their laptops, and learn how to structure and “wrangle” geospatial data for ingest.
We will discuss how to develop scaleable and sustainable digital repository services for geospatial resources using open, collaborative approaches. Participants will learn about data modeling and metadata requirements for curation of a wide-variety of geospatial content types, including historic scanned maps, vector data, raster data, and georectified maps. The instructors contribute to open source communities, including OpenGeoMetadata, GeoBlacklight, and Hydra, and have practical experience building production-quality geospatial repository services.


README: add citation reference

What do you think about adding some info on how to cite JAXbind to the readme?

👍 I think that makes sense. Patch LGTM.