Change default jest pattern-to-match to be jest --pattern=pattern-to-match

Do you want to request a feature or report a bug?
Feature
What is the current behavior?
jest pattern-to-match
Finds and runs all tests whose filenames match pattern-to-match
What is the expected behavior?
jest file-to-run.js
Runs tests in the given file, and only that file.
I believe the pattern feature is still useful, but I think that the default behavior is confusing and unexpected. And it can lead to issues when debugging:

It takes a long time (seconds) to start because Jest is looking through all available files and testing them against the pattern.
If the file you're testing doesn't match the testRegex then it wont run at all, which is confusing to the user who is trying to be explicit.

I do think that the pattern feature is important and useful, but I'd prefer that we have a --pattern flag that we can use for that. Then the default can be to run jest on a specific file which would ignore the testRegex because it's explicit.

Jest actually only runs the given test file if the path is given and has a small optimization there. The slowdown you experience during startup is very likely other static analysis that Jest is doing. As discussed previously, installing watchman (brew install watchman) should significantly improve startup time of Jest on large projects with 100000s of files.
I don't think we'll change this pattern API in the cli as it is really useful.


Question about criteriaMode for Form Component: Showing Validation Errors - All at Once or One by One?

I'm wondering if there's a plan to handle the criteriaMode for the form component. Specifically, I want to know if there are plans to handle the option of displaying all validation errors at once or one error at a time
To provide you with a better understanding of my query, I have attached a screenshot below illustrating an example scenario.

const useFormField = () => {
  const fieldContext = React.useContext(FormFieldContext);
  const itemContext = React.useContext(FormItemContext);
  const { getFieldState, formState } = useFormContext();

  const fieldState = getFieldState(fieldContext.name, formState);

  if (!fieldContext) {
    throw new Error('useFormField should be used within <FormField>');
  }

  const { id } = itemContext;

  return {
    id,
    name: fieldContext.name,
    formItemId: `${id}-form-item`,
    formDescriptionId: `${id}-form-item-description`,
    formMessageId: `${id}-form-item-message`,
    errors: formState.errors,
    ...fieldState,
  };
};

// Define the props for the FormMessage component, extending React.HTMLAttributes<HTMLParagraphElement>
interface FormMessageProps extends React.HTMLAttributes<HTMLParagraphElement> {
  showMultipleErrors?: boolean; // Prop to indicate if multiple error messages are expected
}

const FormMessage = React.forwardRef<HTMLParagraphElement, FormMessageProps>(
  ({ className, showMultipleErrors, children, ...props }, ref) => {
    const { error, formMessageId, name, errors } = useFormField();

    const body = showMultipleErrors ? (
      // Render multiple error messages using ErrorMessage component
      <ErrorMessage
        errors={errors}
        name={name}
        render={({ messages }) => {
          return messages
            ? Object.entries(messages).map(
                ([type, error]: [string, ValidateResult]) => (

                    {Array.isArray(error) ? (
                      error.map((errorMsg, index) => (

                          {errorMsg}

                      ))
                    ) : (

                        {error}

                    )}

                )
              )
            : null;
        }}
      />
    ) : error ? (
      String(error?.message)
    ) : (
      children
    );

    if (!body) {
      return null;
    }

    return (

        {body}

    );
  }
);

Would also love to see this part of shadcn/ui also another useful use case to know all the error messages is that we can use it to display something like this where we always see if the requirements of a password ar fulfilled .

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.


Auto rule behavior

Currently, auto rool won't resolve into multiple rules.
E.g.: If you have different auto rules for *.c and *.cpp you need to write:
build obj(*): auto *.c
build obj(*): auto *.cpp

instead of
build obj(*): auto *.c *.cpp

I guess it's impossible to implement if rules dont have expand = true, otherwise it should be ok :)

I investigated this a bit, and now I don't think we need this, mixed source codebases are not that popular (the only case that I know is when your main project in cpp and some 3rd party libs are in c).

A problem with greedy auto is that it's possible to write something like build *.exe *.obj: auto *.cpp *.obj and then this will expand into proper set of build commands. This could be ok, but I think it's too easy to abuse, so let's not do it.
I'll fix msvc core so we will require c sources to be compiled separately as well.


Provide Consistent Status Conditions Defaulting

What would you like to be added:
Consistent status condition defaults for resources.
Why is this needed:
Improve user/dev experience. See https://github.com/kubernetes-sigs/service-apis/pull/308 for additional details.

I believe this has been now fixed with all our additions before v1alpha1 release.
Can you confirm and close this issue @danehans?

I believe this has been now fixed with all our additions before v1alpha1 release.
Can you confirm and close this issue @danehans?

@hbagdi RouteGatewayStatus is missing a default status condition. https://github.com/kubernetes-sigs/service-apis/pull/528 fixes the issue.

@hbagdi RouteGatewayStatus is missing a default status condition. https://github.com/kubernetes-sigs/service-apis/pull/528 fixes the issue.


Фикс ответа 400, Root element 'delivery' not found

Coverage increased (+0.004%) to 83.325% when pulling c09ebcb46b12730c570bd723ad8e3949b036ca68 on Altairko:patch-1 into 60af7c796ce7e0ba76e2626f4fd2dff639ae3e02 on nixsolutions:master.


Support for using Queue mode with minitest/spec

We use minitest/spec from https://github.com/seattlerb/minitest together with minitest, and that breaks Queue mode, because context, before, etc aren't defined:
D, [2019-11-15T14:44:55.150743 #9554] DEBUG -- : [knapsack_pro] API request UUID: 9166cd89-c25f-4c42-b103-abb3b2d38822
D, [2019-11-15T14:44:55.150854 #9554] DEBUG -- : [knapsack_pro] API response:
D, [2019-11-15T14:44:55.150921 #9554] DEBUG -- : [knapsack_pro] {"queue_name"=>"987:3924a8d106184efbc955b3890d762fd1", "build_subset_id"=>nil, "test_files"=>[{"path"=>"test/system/subscriber_notifications/subscriber_notifier_test.rb", "time_execution"=>nil}]}
trying to run ["test/system/subscriber_notifications/subscriber_notifier_test.rb"]
D, [2019-11-15T14:45:01.478340 #9554] DEBUG -- : [knapsack_pro] Test suite time execution queue recording enabled.
rake aborted!
NoMethodError: undefined method `context' for SubscriberNotifierTest:Class
Did you mean?  const_set
/home/caspark/src/status-page-web/test/system/subscriber_notifications/subscriber_notifier_test.rb:8:in `<class:SubscriberNotifierTest>'
/home/caspark/src/status-page-web/test/system/subscriber_notifications/subscriber_notifier_test.rb:5:in `<main>'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:in `require'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:in `block in require_with_bootsnap_lfi'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/loaded_features_index.rb:65:in `register'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:20:in `require_with_bootsnap_lfi'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:29:in `require'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `block in require'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:257:in `load_dependency'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in `require'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/knapsack_pro-1.15.0/lib/knapsack_pro/runners/queue/minitest_runner.rb:89:in `block in minitest_run'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/knapsack_pro-1.15.0/lib/knapsack_pro/runners/queue/minitest_runner.rb:88:in `each'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/knapsack_pro-1.15.0/lib/knapsack_pro/runners/queue/minitest_runner.rb:88:in `minitest_run'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/knapsack_pro-1.15.0/lib/knapsack_pro/runners/queue/minitest_runner.rb:67:in `run_tests'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/knapsack_pro-1.15.0/lib/knapsack_pro/runners/queue/minitest_runner.rb:30:in `run'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/knapsack_pro-1.15.0/lib/tasks/queue/minitest.rake:6:in `block (3 levels) in <main>'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/bundler-2.0.2/lib/bundler/cli/exec.rb:74:in `load'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/bundler-2.0.2/lib/bundler/cli/exec.rb:74:in `kernel_load'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/bundler-2.0.2/lib/bundler/cli/exec.rb:28:in `run'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/bundler-2.0.2/lib/bundler/cli.rb:465:in `exec'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/bundler-2.0.2/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/bundler-2.0.2/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/bundler-2.0.2/lib/bundler/vendor/thor/lib/thor.rb:387:in `dispatch'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/bundler-2.0.2/lib/bundler/cli.rb:27:in `dispatch'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/bundler-2.0.2/lib/bundler/vendor/thor/lib/thor/base.rb:466:in `start'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/bundler-2.0.2/lib/bundler/cli.rb:18:in `start'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/bundler-2.0.2/exe/bundle:30:in `block in <top (required)>'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/bundler-2.0.2/lib/bundler/friendly_errors.rb:124:in `with_friendly_errors'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/gems/bundler-2.0.2/exe/bundle:22:in `<top (required)>'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/bin/bundle:23:in `load'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/bin/bundle:23:in `<main>'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/bin/ruby_executable_hooks:24:in `eval'
/home/caspark/.rvm/gems/ruby-2.6.3@status-page/bin/ruby_executable_hooks:24:in `<main>'
Tasks: TOP => knapsack_pro:queue:minitest
(See full trace by running task with --trace)

We do require 'minitest/spec' as one of the first things in our test_helper.
The regular Knapsack Pro runner works fine, but it looks like the Knapsack Pro Queue runner reimplements minitest's test running.

@caspark What is your version of minitest gem?

Sorry, should've included that already. Here are all the minitest-related gems we're using:
guard-minitest-2.4.6
minispec-metadata-3.3.1
minitest-5.13.0
minitest-reporters-1.4.2
minitest-retry-0.1.9
minitest-spec-rails-5.4.0
minitest-stub_any_instance-1.0.1

Can you double-check you have RAILS_ENV=test set before running queue mode?
export RAILS_ENV=test

Here is how I run tests in queue mode for minitest https://github.com/KnapsackPro/knapsack_pro-ruby/blob/6849d1fd2610d2d7469ae2a7148ab8ef5faab4c7/lib/knapsack_pro/runners/queue/minitest_runner.rb#L56
Maybe I should require 'minitest/spec' as well https://github.com/KnapsackPro/knapsack_pro-ruby/blob/6849d1fd2610d2d7469ae2a7148ab8ef5faab4c7/lib/knapsack_pro/runners/queue/minitest_runner.rb#L6 but not sure if I should do it always even when someone is not using minitest/spec.
I'll try to play more with it tomorrow morning.

Yep, definitely setting RAILS_ENV - invocation is along the lines of env CI_NODE_TOTAL=2 CI_NODE_INDEX=0 RACK_ENV=test KNAPSACK_GENERATE_REPORT=true KNAPSACK_REPORT_PATH=$KNAPSACK_REPORT_PATH KNAPSACK_PRO_BRANCH=SIP-799-knapsack-pro-hacking-local KNAPSACK_PRO_COMMIT_HASH=$(git rev-parse HEAD) KNAPSACK_PRO_TEST_SUITE_TOKEN_MINITEST=<replaced> bundle exec rake knapsack_pro:queue:minitest.

I managed to reproduce this bug on my local repo.
Can you update your test/test_helper.rb and add there
 # Allow context to be used like describe
  class << self
    alias :context :describe
  end

I found this tip https://stackoverflow.com/a/25811713/905697
This is my test_helper.rb:
class ActiveSupport::TestCase
  # Setup all fixtures in test/fixtures/*.yml for all tests in alphabetical order.
  fixtures :all

  # Add more helper methods to be used by all tests here...
  extend MiniTest::Spec::DSL

  # Allow context to be used like describe
  class << self
    alias :context :describe
  end

  register_spec_type(self) do |desc|
    desc < ActiveRecord::Base if desc.is_a?(Class)
  end
end

Also, I found out if you use RSpec and minitest at the same time then RSpec overrides some stuff and minitest test inside of describe blocks are not executed at all.
https://stackoverflow.com/questions/23683009/minitest-not-picking-up-describe-blocks
I had to disable loading RSpec when running minitest with ENV:
https://github.com/KnapsackPro/rails-app-with-knapsack_pro/blob/8f8d55a636f3b59d9558be8f0bc39e6bdb25c817/Gemfile#L65,L69
This is my example minitest test file with spec syntax describe/context
https://github.com/KnapsackPro/rails-app-with-knapsack_pro/blob/8f8d55a636f3b59d9558be8f0bc39e6bdb25c817/test/minitest/meme_spec_test.rb#L12,L17

@caspark Did my tips helped?

@caspark Can you try the solution I posted? Thank you.

Sorry @ArturT , have been busy with other things. I suspect that aliasing context -> describe won't be sufficient, but haven't tried it yet, and unfortunately with some PTO coming up I likely won't have time to try it any time soon. You can close this issue in the meantime, and if this approach doesn't work then I'll comment again when I have time to investigate further.

@caspark I will keep this issue open. You can get back to it when you find some time.
Do you use another test runner like RSpec? I noticed that loading RSpec gem breaks minitest. See my previous tip.

@caspark have you had a chance to revisit this issue?

No, sorry, haven't looked at this since.
(Also, no, not using an alternative test runner like rspec at the moment.)

@caspark If there is anything we can help with, please let me know. If you would revisit this issue that would be helpful. Otherwise, we are going to close this issue.


Fix cortex null block soft-block on functionality

Fixes https://github.com/rancher/opni/issues/790

PR is stale, closing.


AutoMigrate a struct with DEFAULT:0 tag always alert table

Your Question
When I use AutoMigrate a struct with DEFAULT:0 tag, it will always ALTER TABLE when I restart the program.
type TestTable struct {
	ID     uint
        Name string `gorm:"type:varchar(20);NOT NULL;DEFAULT:''"`
	UserID uint `gorm:"type:int;NOT NULL;DEFAULT:0"`
	Status uint `gorm:"type:tinyint;NOT NULL;DEFAULT:0"`
}

It will log this
***/vendor/gorm.io/driver/mysql/migrator.go:83
[140.971ms] [rows:0] ALTER TABLE `test_tables` MODIFY COLUMN `user_id` bigint NOT NULL DEFAULT 0
[174.141ms] [rows:0] ALTER TABLE `test_tables` MODIFY COLUMN `status` tinyint NOT NULL DEFAULT 0

But it is in right state when I see the mysql table. And the 'Name' field DEFAULT:'', it wont ALTER table.
Did I use it wrong?
GORM.version: v1.20.5
GORM.driver.mysql.version: v1.0.3
GORM.datatypes.version: v1.0.0
mysql.version: 8.0.14

The document you expected this should be explained
Not ALTER TABLE when restart program

Expected answer
Is that a BUG?
How do I use it?

We meet the same problem in our production environment, any progress?

Related to go-gorm/mysql#20.
Already fixed by 5973041.

@s-takehana
Thanks for the information.
But now testing with the v1.21.10 version,  if the default value is 1, alert happens every auto migration.
Reproduce infos:
go.mod
gorm.io/gorm v1.21.10

package main

import (
	"fmt"
	"gorm.io/driver/mysql"
	"gorm.io/gorm"
	"log"
	"net/url"
)

type TestTable struct {
	ID     uint
	Status   uint   `gorm:"type:tinyint;NOT NULL;DEFAULT:1"`
}

func main() {
	dsn := fmt.Sprintf(
		"%s:%s@tcp(%s:%d)/%s?charset=utf8mb4&parseTime=True&loc=%s&time_zone=%s",
		"root",
		"123456",
		"<IP_ADDRESS>",
		32000,
		"test",
		url.QueryEscape("Asia/Shanghai"),
		url.QueryEscape("'+8:00'"),
	)
	rds, err := gorm.Open(mysql.Open(dsn), &gorm.Config{})
	if err != nil {
		log.Panic(err)
	}
	rds = rds.Debug()
	err = rds.AutoMigrate(&TestTable{})
	if err != nil {
		log.Panic(err)
	}
}

@zhchbin I've reproduced it.
Sorry, I was only checking DEFAULT:0.

Also happening for postgres on:
gorm.io/driver/postgres v1.1.0
gorm.io/gorm v1.21.11

comment tag too.
I've confirmed the same behavior in MySQL.
type User struct {
	gorm.Model
	Name   string `gorm:"comment:a1"`
	Status uint   `gorm:"comment:1"`
}

Please change the label to type:with reproduction steps from type:question.

comment tag too.
I've confirmed the same behavior in MySQL.
type User struct {
	gorm.Model
	Name   string `gorm:"comment:a1"`
	Status uint   `gorm:"comment:1"`
}

Please change the label to type:with reproduction steps from type:question.

Looks like i can't change the label.


clarify NuGet server api

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

File
Status
Preview URL
Details

docs/api/overview.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 021662c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/TOC.md
:white_check_mark:Succeeded
View

docs/api/overview.md
:white_check_mark:Succeeded
View

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


Siddhi APP creation exception when log sink used with HTTP sink

Description:
Below query causes a SiddhiAppCreation exception.
@App:name('API-Request-Throttler')
@App:description('Enforcesthrottling to API requests ')

-- HTTP endpoint which listens for api request related events
@source(type = 'http', receiver.url = "http://<IP_ADDRESS>:8006/apiRequestStream", basic.auth.enabled = "false",
	@map(type = 'json'))
define stream APIRequestStream (apiName string, version string, tier string, user string, userEmail string);

-- HTTP sink to publich throttle decisions. For testing purpose, there is a mock logger service provided
@sink(type = 'log')
@sink(type = 'http', publisher.url = "http://${LOGGER_SERVICE_HOST}:8080/logger", method = "POST",
	@map(type = 'json'))
define stream ThrottleOutputStream (apiName string, version string, user string, tier string, userEmail string, isThrottled bool);

-- Email sink to send alerts
@sink(type = 'log', @map(type = 'text'))
@sink(type = 'email', username = "${EMAIL_USERNAME}", address = "${SENDER_EMAIL_ADDRESS}", password = "${EMAIL_PASSWORD}",
subject = "Upgrade API Subscription Tier", to = "{{userEmail}}", host = "smtp.gmail.com", port = "465", ssl.enable = "true", auth = "true",
	@map(type = 'text',
		@payload("""
			Hi {{user}}

			You have subscribed to API called {{apiName}}:{{version}} with {{tier}} tier.
			Based on our records, it seems you are hitting the upper limit of the API requests in a frequent manner.

			We kindly request you to consider upgrading to next API subscription tier to avoid this in the future.

			Thanks,
			API Team""")))
define stream UserNotificationStream (user string, apiName string, version string, tier string, userEmail string, throttledCount long);

@info(name = 'Query to find users who needs to be throttled based on tier `silver`')
from APIRequestStream[tier == "silver"]#window.timeBatch(1 min, 0, true)
select apiName, version, user, tier, userEmail, count() as totalRequestCount
	group by apiName, version, user
	having totalRequestCount > 10 or totalRequestCount == 0
insert all events into ThrottledStream;

@info(name = 'Query to find users who needs to be throttled based on tier `gold`')
from APIRequestStream[tier == "gold"]#window.timeBatch(1 min, 0, true)
select apiName, version, user, tier, userEmail, count() as totalRequestCount
	group by apiName, version, user
	having totalRequestCount > 100 or totalRequestCount == 0
insert all events into ThrottledStream;

@info(name = 'Query to add a flag for throttled request')
from ThrottledStream
select apiName, version, user, tier, userEmail, ifThenElse(totalRequestCount == 0, false, true) as isThrottled
insert into ThrottleOutputStream;

@info(name = 'Query to find frequently throttled users - who have throttled more than 10 times in the last hour')
from ThrottleOutputStream[isThrottled]#window.time(1 hour)
select user, apiName, version, tier, userEmail, count() as throttledCount
	group by user, apiName, version, tier
	having throttledCount > 10
output first every 15 min
insert into UserNotificationStream;

Exception printed as below.
[2019-07-31 15:22:43,844] ERROR {io.siddhi.distribution.core.internal.StreamProcessorDeployer} - io.siddhi.core.exception.SiddhiAppCreationException: Error on 'API-Request-Throttler' @ Line: 13. Position: 21, near '@sink(type = 'http', publisher.url = "http://<IP_ADDRESS>:8080/logger", method = "POST",
	@map(type = 'json'))'. Index: 0, Size: 0 io.siddhi.distribution.core.internal.exception.SiddhiAppDeploymentException: io.siddhi.core.exception.SiddhiAppCreationException: Error on 'API-Request-Throttler' @ Line: 13. Position: 21, near '@sink(type = 'http', publisher.url = "http://<IP_ADDRESS>:8080/logger", method = "POST",
	@map(type = 'json'))'. Index: 0, Size: 0
	at io.siddhi.distribution.core.internal.StreamProcessorDeployer.deploySiddhiQLFile(StreamProcessorDeployer.java:104)
	at io.siddhi.distribution.core.internal.StreamProcessorDeployer.deploy(StreamProcessorDeployer.java:295)
	at org.wso2.carbon.deployment.engine.internal.DeploymentEngine.lambda$deployArtifacts$0(DeploymentEngine.java:291)
	at java.util.ArrayList.forEach(ArrayList.java:1257)
	at org.wso2.carbon.deployment.engine.internal.DeploymentEngine.deployArtifacts(DeploymentEngine.java:282)
	at org.wso2.carbon.deployment.engine.internal.RepositoryScanner.sweep(RepositoryScanner.java:112)
	at org.wso2.carbon.deployment.engine.internal.RepositoryScanner.scan(RepositoryScanner.java:68)
	at org.wso2.carbon.deployment.engine.internal.DeploymentEngine.start(DeploymentEngine.java:121)
	at org.wso2.carbon.deployment.engine.internal.DeploymentEngineListenerComponent.onAllRequiredCapabilitiesAvailable(DeploymentEngineListenerComponent.java:216)
	at org.wso2.carbon.kernel.internal.startupresolver.StartupComponentManager.lambda$notifySatisfiableComponents$7(StartupComponentManager.java:266)
	at java.util.ArrayList.forEach(ArrayList.java:1257)
	at org.wso2.carbon.kernel.internal.startupresolver.StartupComponentManager.notifySatisfiableComponents(StartupComponentManager.java:252)
	at org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver$1.run(StartupOrderResolver.java:204)
	at java.util.TimerThread.mainLoop(Timer.java:555)
	at java.util.TimerThread.run(Timer.java:505)
Caused by: io.siddhi.core.exception.SiddhiAppCreationException: Error on 'API-Request-Throttler' @ Line: 13. Position: 21, near '@sink(type = 'http', publisher.url = "http://<IP_ADDRESS>:8080/logger", method = "POST",
	@map(type = 'json'))'. Index: 0, Size: 0
	at io.siddhi.core.util.ExceptionUtil.populateQueryContext(ExceptionUtil.java:43)
	at io.siddhi.core.util.parser.helper.DefinitionParserHelper.addEventSink(DefinitionParserHelper.java:586)
	at io.siddhi.core.util.SiddhiAppRuntimeBuilder.defineStream(SiddhiAppRuntimeBuilder.java:115)
	at io.siddhi.core.util.parser.SiddhiAppParser.defineStreamDefinitions(SiddhiAppParser.java:373)
	at io.siddhi.core.util.parser.SiddhiAppParser.parse(SiddhiAppParser.java:229)
	at io.siddhi.core.SiddhiManager.createSiddhiAppRuntime(SiddhiManager.java:66)
	at io.siddhi.core.SiddhiManager.createSiddhiAppRuntime(SiddhiManager.java:76)
	at io.siddhi.distribution.core.internal.StreamProcessorService.deploySiddhiApp(StreamProcessorService.java:69)
	at io.siddhi.distribution.core.internal.StreamProcessorDeployer.deploySiddhiQLFile(StreamProcessorDeployer.java:92)
	... 14 more
Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
	at java.util.ArrayList.rangeCheck(ArrayList.java:657)
	at java.util.ArrayList.get(ArrayList.java:433)
	at io.siddhi.extension.io.http.sink.HttpSink.init(HttpSink.java:623)
	at io.siddhi.core.stream.output.sink.Sink.init(Sink.java:99)
	at io.siddhi.core.util.parser.helper.DefinitionParserHelper.addEventSink(DefinitionParserHelper.java:547)
	... 21 more

It is due to below issue..
https://github.com/siddhi-io/siddhi-io-http/blob/master/component/src/main/java/io/siddhi/extension/io/http/sink/HttpSink.java#L623

https://github.com/siddhi-io/siddhi/issues/1426 related to this.

Issue is fixed now..
Observed some issues in HTTPSInk implementation. Created a separate ticket to followup that. https://github.com/siddhi-io/siddhi-io-http/issues/142

Fixed in https://github.com/siddhi-io/siddhi-io-http/pull/141 ..


Relocated repo to codedellemc

This patch rewrites all of the "github.com/emccode" to "github.com/codedellemc" in source files, documentation, and other build-related content.

Current coverage is 62.05% (diff: 100%)

Merging #16 into master will not change coverage

@@             master        #16   diff @@
==========================================
  Files             8          8
  Lines           282        282
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            175        175
  Misses          101        101
  Partials          6          6

Powered by Codecov. Last update 3bd901d...3fc7e83


🚀 [Feature] Frontend: Deeplink to table page

🚀 Feature

As a user I want to have a deep-link to every table I have access to, e.g. localhost/table/69 where the number is the id of the table.
If there is no property for the link, then the link must be queried by the table`'s id.
This may also solve some hydration issues.

duplicate of #1007

I cannot see this issue as an duplicate. May be it is a part of #1007

I just had an idea. We often have the situation that the user is given the possibility to share a link so others can join a table. Right now, we would have two different links, one for logged in users and one for guests. That's quite a mental overhead for users and makes user interfaces more complicated.
Instead, could we use one and the same link for both cases? Depending if a user is logged in, he will stay in DreamMall and is shown the table page, or is sent to the /join-table page. (A login option would be nice to have on /join-table, for users which are not logged in but have a DreamMall account.)

Right now, we would have two different links, one for logged in users and one for guests.

For clarity of terms:
The two different user types here are registered users (logged in is one possible state of a registered user) and guests (not-registered users)


[nice to have] implementation of the CBaseAnimating class missing

important funcs like all off the inverse kinematics stuff  and accumulatelayers is missing

i working on my own render & GUI, so when i will finish it, i will move the base to it, include basic animation fix and more classes that actual for 2021, and then finally tag it as version no.2 and publish. im going to close this issue for now


add host param base Draft_6455

add host param base Draft_6455

I renamed and add some description.

Hello @TOTOROYang,
thx a lot for the changes!
Added it to the master branch!
Greetings
marci4

Hello @TOTOROYang,
after reading through the spec and some issues, a non browser websocket client does not have to send a orogin-header.
That is why I am removing this draft again.
Please open a issue at the specific project to let them support non browser clients.
Greetings
marci4

wss://apprtc-ws.webrtc.org:443/ws
you can try to connect this webSocket server.
I find out this webSocket (use go) need origin.
i find it at http://websocket.org/echo.html.

Hello @TOTOROYang,
The following is out of the spec (1.3):
  The |Origin| header field [RFC6454] is used to protect against    unauthorized cross-origin use of a WebSocket server by scripts using    the WebSocket API in a web browser.  The server is informed of the    script origin generating the WebSocket connection request.  If the    server does not wish to accept connections from this origin, it can    choose to reject the connection by sending an appropriate HTTP error    code.  This header field is sent by browser clients; for non-browser    clients, this header field may be sent if it makes sense in the    context of those clients.
The origin field is not required by the spec and for me it is not right in the current context.
Greetings
marci4


Scipy

Create a notebook for module titled "Scientific libraries: scipy"

@SimonHeybrock is "fitting_scipy" covering this story or you intended to write something else?

Yes, it is.


Reformated files, make picklable and encourage to import Attridict

Changes

Reformated files (space indent, PEP8, etc)
from attridict import AttriDict can be used
AttriDict can be pickled

Hello. Thank you for the PR and bringing to my attention that an attridict object cannot be pickled.
The attridict module was meant to be an easy import with just import attridict, and from attridict import AttriDict doesn't look as pretty.
Thanks to your PR, I was able to notice and look into the issue. I found a solution that works still with the simple import. What I did was I added an AttriDict attribute to the class for pickle to reference when loading the object. This is the commit that handles that.
Much appreciated!


Devise::TestHelpers inclusion in Rails 5

I'm running into an inconsistency in how Devise suggests doing controller tests in Rails 5.0.0.beta1.
I set up a minimal app on Devise b97b3e6e3b570324467ac84d807111837943ec20 for you to reproduce, if you'd like:
git clone https://github.com/holman/devise-helpers-test
cd devise-helpers-test && rake

In master's README, we're currently suggesting this to be added to test/test_helper.rb:
class ActionController::TestCase
  include Devise::TestHelpers
end

Running the tests will result in:
NoMethodError: undefined method `sign_in' for #<HomeControllerTest:0x007fa1433cf668>
    test/controllers/home_controller_test.rb:5:in `block in <class:HomeControllerTest>'

Greenfield Rails 5 generated controllers now inherit from ActionDispatch::IntegrationTest:
class HomeControllerTest < ActionDispatch::IntegrationTest
  test "home" do
    sign_in User.create(:email =><EMAIL_ADDRESS>    get root_url
    assert_response :success
  end
end

Modifying the test_helper.rb to include from within the new class causes another problem, though:
NoMethodError: undefined method `env' for nil:NilClass
    /Users/holman/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/bundler/gems/devise-b97b3e6e3b57/lib/devise/test_helpers.rb:27:in `setup_controller_for_warden'

That's currently this line, which doesn't have the @request ivar available.
Likely missing something obvious here! If I am, we should likely update the README to account for bonehead developers like myself.  🎆

Excellent bug report, @holman! :heart:
It seems controller tests in Rails 5 are integration tests, so we may not have a "backdoor" to sign the user in. We will either need to go explicitly through the sign in page OR build a session cookie that we'll store directly in the request. We will explore the options but I hope this is enough information for you to progress!

Thanks, @josevalim! Real helpful.
For those of you who may be following along at home, I'm tossing this in test_helper.rb in the meantime:
class ActionDispatch::IntegrationTest
  def sign_in(user)
    post user_session_path \
      "user[email]"    => user.email,
      "user[password]" => user.password
  end
end

Seems to be the easiest thing to do that allows future drop-in support. Small app too so far, so not a huge deal to add the extra overhead for me.

@holman are you actively working on this? Let me know if there's anything I can do to help. Currently working on several Rails 5 apps and have done the same workaround as you posted in your last comment. Would love to help patch this.

Probbbbbably not. Don't think I know enough of the internals to jump in and figure out which direction to take this. (If there's a consensus on what approach makes the most sense I can probably hop in and build it out though).

Thanks @holman for posting the work around, it helped me a lot.
Although I don't have a solution I thought I'd add a little more information that might help someone else out. I'm pretty new to testing and rails in general so sorry if this isn't much use.
It looks like in Rails 5 you can add gem 'rails-controller-testing' to keep using the old controller tests. I haven't tried this but it might help someone. I'd like to make the integration tests work though because @eileencodes and @tenderlove put so much work into making them faster (https://youtu.be/oT74HLvDo_A).
When I tried the solution @holman posted here, it didn't work without providing a password. I don't really understand why. Here is what did work for me eventually:
My user.rb file:
class User < ApplicationRecord
  devise :database_authenticatable, :registerable,
         :recoverable, :rememberable, :trackable, :validatable,
         :confirmable, :lockable, :timeoutable, :omniauthable
end

My test_helper.rb file:
ENV['RAILS_ENV'] ||= 'test'
require File.expand_path('../../config/environment', __FILE__)
require 'rails/test_help'
require "minitest/reporters"
Minitest::Reporters.use!

class ActiveSupport::TestCase
#  fixtures :all

  def sign_in(user:, password:)
    post user_session_path \
      "user[email]"    => user.email,
      "user[password]" => password
  end
end

My first test file login_test.rb (These tests all pass without generating errors):
require 'test_helper'

class SiteLayoutTest < ActionDispatch::IntegrationTest

  def setup
    @password = "password"
    @confirmed_user = User.create(email<EMAIL_ADDRESS>
                                  password: @password,
                                  confirmed_at: "2016-02-01 11:35:56")
    @unconfirmed_user = User.create(email<EMAIL_ADDRESS>
                                    password: @password,
                                    confirmed_at: "")
  end

  test "successful login of confirmed user" do
    sign_in(user: @confirmed_user, password: @password)
    assert_redirected_to home_url
  end

  test "unsuccessful login of unconfirmed user" do
    sign_in(user: @unconfirmed_user, password: @password)
    get home_path
    assert_response :redirect
  end

  test "unsuccessful login of confirmed user with wrong password" do
    sign_in(user: @confirmed_user, password: "wrong password")
    get home_path
    assert_response :redirect
  end

end

I hope it helps a little.

I'm working on a Rails 5 app as well and ran in to these issues. I slotted in @holman's code to my test_helper.rb:
ENV['RAILS_ENV'] ||= 'test'
require File.expand_path('../../config/environment', __FILE__)
require 'rails/test_help'

class ActiveSupport::TestCase
  fixtures :all

  def sign_in(user)
    post user_session_path \
      'user[email]'    => user.email,
      'user[password]' => user.password
  end
end

And then I've got a controller test:
require 'test_helper'

class KlassesControllerTest < ActionDispatch::IntegrationTest
  setup do
    sign_in users(:one)
    @klass = klasses(:one)
  end

  test 'should get index' do
    get klasses_url
    assert_response :success
  end
end

My user fixture:
one:
  name: 'Lachlan'
  email<EMAIL_ADDRESS>  encrypted_password: <%= Devise::Encryptor.digest(User, 'password') %>

When I run the test, however, I get this:
Error:
KlassesControllerTest#test_should_get_index:
ArgumentError: wrong number of arguments (given 0, expected 1..2)
    test/test_helper.rb:9:in `sign_in'
    test/controllers/klasses_controller_test.rb:5:in `block in <class:KlassesControllerTest>'

How can I fix this issue (even temporarily) so that I can test my app? Thanks :grinning:

I could have sworn I ran into that problem when I was initially looking into this, but for the life of me I can't remember what the specifics were or how to reproduce it. Guessing it might have something to do with your routes, maybe?

Hmm. My routes are pretty straightforward:
devise_for :users, controllers: { registrations: 'registrations' }
as :user do
  get '/login', to: 'devise/sessions#new'
  get '/signin', to: 'devise/sessions#new'
  get '/signup', to: 'devise/registrations#new'
  get '/settings', to: 'devise/registrations#edit'
end

And in case you were wondering, the registrations controller:
class RegistrationsController < Devise::RegistrationsController
  protected

  def update_resource(resource, params)
    resource.update_without_password(params)
  end
end

Really confused as to my next step 😬 — thanks for helping out, though!

@lachlanjc is the sign_in method definitely the one you've defined or is something else overriding it. Try method(:sign_in).source_location.

@twe4ked Source location is confirming the method is from test/test_helper.rb (note that I haven't changed it from what I posted above).

I got the same error as you no matter what I tried so I gave up trying to
use a fixture and created the user in the test setup. (see my previous
comment)

Ok, so I've updated my sign_in method to create a user right there:
def sign_in(user)
  @user = User.create(email<EMAIL_ADDRESS>                      password: 'password')
  post user_registration_path, params: { 'user[email]': user.email, 'user[password]': 'password' }
  # Test authentication state
  puts current_user.email
end

But this isn't actually working:
Error:
KlassesControllerTest#test_should_get_index:
NameError: undefined local variable or method `current_user' for #<KlassesControllerTest:0x007ff9b5e7e878>
    test/test_helper.rb:12:in `sign_in'
    test/controllers/klasses_controller_test.rb:10:in `block in <class:KlassesControllerTest>'

You should have access to a @controller or controller variable in the test. Try @controller.current_user.email? You might get more luck over at http://stackoverflow.com.

@twe4ked The sign_in method is in test/test_helper.rb because I need/will need it in many different controller tests. Is there a better place for it? Also, I'm still getting an error if I set @controller = KlassesController before running sign_in with the change you proposed.

@lachlanjc Try controller.current_user.email. I suggest creating a question on Stack Overflow and linking to it from here. There are a bunch of people getting notifications for each comment here and it's getting a bit off topic.

@twe4ked Yeah, that took a while! When I created a user on the fly instead of using a fixture everything worked, but then the user_ids in my fixtures didn't match up and so authenticated pages wouldn't work. I'm now creating a user on the fly, and then changing the user ID in the database for the subject so that everything works smoothly. Here's my final solution for anyone that needs it:
class ActionDispatch::IntegrationTest
  def sign_in(user)
    post user_session_path \
      "user[email]"    => user.email,
      "user[password]" => user.password
  end

  def sign_in_for(subject)
    @user = User.create(email<EMAIL_ADDRESS>password: 'password')
    sign_in @user
    subject.update_attribute(:user_id, @user.id)
  end
end

And an example for using it (likely inside the setup of the test):
setup do
  @post = posts(:one)
  sign_in_for(@post)
end

This worked for me and I wanted to get some feedback on the solution. I used Warden's test helpers directly as instructed here, https://github.com/hassox/warden/wiki/Testing.

Merged #4071 introducing a new IntegrationHelpers module that uses the Warden testing API and moved the old TestHelpers to ControllerHelpers - I still want to finish a few other things before a 4.2.0 release, but anyone is welcome to try out these modules from master and let us know how it goes 😄

Not trying to re-animate this thread, but is there any documentation on how to get sign_in to work with Minitest following the upgrade to Rails 5? I basically am stopped at:
undefined method `sign_in'

@tirdadc have you checked the updated Test helpers section from the README? If it doesn't work for you, please create a new issue following our CONTRIBUTING.md recommendations.

Hey @tirdadc, this might be a bit late but can help others: According to the README, in RAILS 5 you should do this:
class ActionDispatch::IntegrationTest
    include Devise::Test::IntegrationHelpers
end

Instead of how we use to do it on RAILS 4 ( ActionController::TestCase will be deprecated in RAILS 5)
class ActionController::TestCase
  include Devise::Test::ControllerHelpers
end

Also, very late to the party, but if you use gem 'rails-controller-testing' with rails 5, you should setup test_helper like in rails 4 aka
class ActionController::TestCase
  include Devise::Test::ControllerHelpers
end

otherwise you will start getting these undefined method `sign_in'errors.

In case anyone finds this useful, I have a slightly different approach to logging in users during testing. If you wish to skip over the devise functionality you can use some middleware, similar to how the clearance gem works. This prevents you from having to make a whole other request to sign in and should speed up specs.
spec/support/back_door.rb
# Usage:
#
#   visit new_feedback_path(as: user)
class BackDoor
  def initialize(app, &block)
    @app = app
    @block = block
  end

  def call(env)
    sign_in_through_the_back_door(env)
    @app.call(env)
  end

  private

  def sign_in_through_the_back_door(env)
    params = Rack::Utils.parse_query(env['QUERY_STRING'])
    user_param = params['as']

    return unless user_param.present?
    user = User.find(user_param)
    return unless user
    env['warden'].set_user(user)
  end
end

config/environments/test.rb
require_relative '../../spec/support/back_door'
config.middleware.use BackDoor

In specs:
user = # get_user_here
get '/url', as: user

I got stuck on this for quite a bit. I'm using Rails 5.2.3 with a JWT Devise Strategy and came up against numerous issues with all the options above. My solution was the following:
test/support/authentication.rb
module Authentication
  def authenticate_user(user)
    token = JsonWebToken.encode(id: user.id)
    user.token = 'JWT ' + token
    user.save
  end
end

test/test_helper.rb
ENV['RAILS_ENV'] ||= 'test'
require File.expand_path('../config/environment', __dir__)
require 'rails/test_help'
require 'bcrypt'

class ActiveSupport::TestCase
  fixtures :all
  Dir[Rails.root.join("test/support/**/*.rb")].each { |f| require f }
end

test/fixtures/users.yml
frederick:
  type: 'AuthUser'
  name: 'Frederick'
  email<EMAIL_ADDRESS>  phone: '1234567890'
  encrypted_password: <%= BCrypt::Password.create("password", cost: 4) %>

test/controllers/v1/users_controller_test.rb
require 'test_helper'

class V1::UsersControllerTest < ActionDispatch::IntegrationTest
  include Authentication

  setup do
    @user = users(:frederick)
    authenticate_user(@user)
    @headers = { "Authorization": @user.token }
  end

  test "fetching users should succeed" do
  	get users_url, headers: @headers, xhr: true
    assert_response :success
  end

  test "fetching a user should succeed" do
    get<EMAIL_ADDRESS>headers: @headers, xhr: true
    assert_response :success
  end
end


moving old changes

Hey @whoburg and @bqpd I was cleaning out my gpkit models folder and found these changes that I hadn't committed from last semester.

These look old compared to what's already in the aircraft folder on master. Closing without merging -- reopen if there's anything here that should be incorporated.


Add attribute to distinguish community vs. product in the content

Relates to keycloak/keycloak#22345

Don't do as we don't want to have upstream code differentiating the two.


Add displayable interface and display type enumeration

Codecov Report

Merging #79 (e01035f) into master (31cbd0f) will decrease coverage by 0.39%.
The diff coverage is 26.47%.

@@             Coverage Diff              @@
##             master      #79      +/-   ##
============================================
- Coverage     47.52%   47.12%   -0.40%
- Complexity      413      416       +3
============================================
  Files           107      109       +2
  Lines          1978     2003      +25
  Branches        215      216       +1
============================================
+ Hits            940      944       +4
- Misses         1001     1022      +21
  Partials         37       37

Impacted Files
Coverage Δ

...rc/main/java/seedu/address/logic/LogicManager.java
68.18% <0.00%> (-3.25%)
:arrow_down:

...edu/address/logic/commands/ListStudentCommand.java
0.00% <0.00%> (ø)

...ava/seedu/address/model/assessment/Assessment.java
0.00% <0.00%> (ø)

...in/java/seedu/address/model/tutorial/Tutorial.java
0.00% <0.00%> (ø)

...c/main/java/seedu/address/ui/DisplayListPanel.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/ui/MainWindow.java
0.00% <0.00%> (ø)

...c/main/java/seedu/address/model/person/Person.java
95.45% <50.00%> (-2.17%)
:arrow_down:

.../main/java/seedu/address/model/person/Student.java
4.87% <50.00%> (+2.31%)
:arrow_up:

...va/seedu/address/logic/commands/CommandResult.java
80.00% <60.00%> (ø)

...java/seedu/address/logic/commands/ExitCommand.java
100.00% <100.00%> (ø)

... and 2 more

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 31cbd0f...e01035f. Read the comment docs.


My licence in Gurobi expired, I updated the licence, but it didn't help

I have Gurobi v8.1.1.
I have a license that is valid, I have already checked it.
I am using JuMP (v.0.20.0) in Julia(v 1.2.0) model and with Gurobi solver. At some point, it started to indicate that the license is about to expire and I updated it. It didn't help and just now it just gives me the following message:

Moreover, when I am trying to use the command:

which is weird since when I do

It works.
I have already changed ENV in the following way
ENV["GUROBI_HOME"] = "/Library/gurobi811/mac64" and i can see the file "libgurobi81.dylib" there. However, when I try to use the command build it just responds false.
Could you please tell me if there is any way to fix it?

You can ignore the build command return false.
Did you run grbgetkey? And save follow the instructions to save the license file in the right place, and/or set the appropriate environment variable? If so, you may just need to restart Julia (or Atom).

HI, thank you, I have double-checked the environment variable in Gurobi, and, apparently, it was not pointing to the correct location of the valid license file. Anyway, it works now. Thank you very much.

Great!


feat(ibl): support indent-blankline v3

https://github.com/lukas-reineke/indent-blankline.nvim/wiki/Migrate-to-version-3
WIP

there isn't a 1-to-1 mapping of the old config to the new one, so i tried my best to adapt the v3 config.
the colorschme and the detail settings might need further adjustments.

https://github.com/ayamir/nvimdots/pull/1011/commits/115db0595a68b46ea72df5d7c69122640b317de1 updated several hl groups and added support for big files. It also mapped (almost) all v2 options to the corresponding valid entries in v3. The only exception here is ibl.config.scope.include: We presumably need more context/information (or upstream support) to make indent-blankline.scope work on all languages supported by Treesitter (https://github.com/lukas-reineke/indent-blankline.nvim/issues/632)


Fix the int cast in smpmap.dimension.get_block

the python int cast is different from the behavior in minecraft, for example:
a point (x,y,z)=(-123.7,33,44)
In minecraft this point should be inside the block (-124,33,44).
But in the smpmap.dimension.get_block we use the python int cast, it will cast to (-123,33,44) and get a wrong block data.
So I add a mcint() in utils.py to cast it correctly..

The correct way to do this would be math.floor
But that cast isn't there to solve for passing decimals to the get_block api, its for casting zero'd floats (ex. 5.0, 1.0, 60.0 or something like that) and is marginally faster than math.floor for this purpose. If you're passing a decimal to get_block you're passing garbage arguments and will get garbage out.


Select wrong formatter when file is mhtml-mode

In mhtml-mode, the var major-mode is changed when your point moved into different position:

if point at , major-mode is identidied as css-mode;
if point at , major-mode is identidied as js-mode;
at other place, major-mode is mhtml-mode.

so when I point at  section, apheleia select prettier-css which is wrong, to fix the problem we need to
always get mhtml-mode as major-mode .
;; NOTE if current point is at mhtml submode, then
;; return `mhtml-mode' instead.
(or (and (get-text-property
          (if (and (eobp) (not (bobp)))
              (1- (point))
            (point))
          'mhtml-submode)
         'mhtml-mode)
    major-mode)

@raxod502 I guess need to fix function apheleia--get-formatters, does issue https://github.com/radian-software/apheleia/issues/29 is related to this either ?

One option would be to add to mhtml-mode-hook a function that sets apheleia-formatter to whatever you desire it to be. The buffer-local variable overrides automatic formatter detection.
But, since mhtml-mode is built in, I guess we should make this work by default. I'd like to do it in a way that does not special-case one particular mode in the internal code. Let me add something generic for that, one moment.

How do you feel about the approach in https://github.com/radian-software/apheleia/pull/303? I'm not sure if it's the best, but it seems not unreasonable to me.

LGTM. mhtml-mode is the only mode which can fontify css/js code correctly in html file so far, thanks for your great package !

I use web-mode, personally, but that has its own problems.


2FA Have an error

There was an error when I used bind MFA and I couldn't bind

@v8oo00  您好，第一个输入框用于填写 第一组 2FA 验证码，第二个输入框用于填写第二组 2FA 验证码，填写完第一组验证码之后需要等待 30s 后等 2FA App 验证码跳到下组时再填写。
hi, you should input different two 2FA Code into 2 input box.  Open your 2FA App and Scan QR Code, input the 2FA into the 1st input box, then wait the 2FA  App code change  (about 30s), and input new 2FA Code input the 2nd input box, then click save btn.

All right. Thank you.


Android: "unable to find socket" if there is a problem when connecting!

I have found a quite serious Bug in the Native Android Implementation of the Sockets. Here is some example-code and the steps to reproduce:
let client: Object = net.createConnection({host: HOST, port: PORT}, () => {
    console.log('Connected successfully to ' + HOST + ':' + PORT);
});

client.on('error', (error) => {
    console.log(error);
    // The connection was not successful, close the socket here:
    client.end();
});

client.on('data', (data) => {
    console.log(data);
    // TODO do something with the data
});

client.on('close', () => {
    console.log('Connection closed');
});

This is what happens in my case:

The client tries to connect to HOST:PORT, which is currently unreachable
The connection cannot be established, because the host is not reachable
The onError-callback is called with the expected exception.
Calling client.end() in the onError-callback results in onError being called again
This time with the error unable to find socket
As soon as the host becomes reachable again, the socket connects to the host!
Calling any of the sockets instance-methods has no effect, except for end or destroy which result in onError being called with unable to find socket again.

The Bug is in TcpSocketManager.java on line 136:

If ex is set when onConnectCompleted is called, the first if-branch will be skipped
Therefore, the new socket-instance never makes it into mClients
Instead, the onError-callback is triggered, which we observed in the code.
Any other method call (e.g. close) will try to find the socket with the given cId, which will never be there and always return null.
On the close-method, this will trigger another call to onError, this time with the hardcoded unable to find socket-message we got in JavaScript.
Other methods will just silently fail and not do anything (write for example).
The socket never closed either. It just exists without a way to communicate with it.

Fix: I made a quick test to see how Node.js handles this:
const net = require("net");
const client = net.createConnection(41231, "localhost", () => { // this host:port is NOT reachable!
	console.log("Connected!");
});
client.on("error", (err) => {
	console.log("Error! "+err);
});
client.on("close", () => {
	console.log("Closed...");
});

Node will try to connect, then emit an error-event with the error Error: connect ECONNREFUSED and afterwards emit a close-event.
So, closing the socket automatically if it can't connect might be the most concise way of implementing this.

If you need any further information, I'll be here to help!

There's been no resolution for this has there?

@MattyK14 No, not really. It ended up not mattering in my case, but the problem is still there. Also, I wasn't able do fix this myself (lack of time on the job).
If this is a problem for you and you're short on time I'd suggest writing the code native and calling that from RN. Fixing the bug here will only help when the pull-request is accepted and the package republished.


[FEATURE REQUEST, RR2] Allow merging two config files

In roadrunner 1.x we could have two different config files, one for production and other for develpment.
An example development config file looked like this:
include:
  - .rr.yaml

reload:
  interval: 1s
  patterns: [".php"]

Now the include block is not handled as spf13/viper does not have this feature implemented, (but is requested https://github.com/spf13/viper/pull/893).
As a workaround for this problem I can suggest two solutions:

Allow passing --config multiple times on the command line and merge the configuration from multiple files.
Add a key enabled under reload, so I can call the server with -o reload.enabled=false in production.

FYI, we implemented this feature in RR 1 itself. Not via Viper.

I would like having an enabled option in every plugin just because of the symmetry. This on it's own would suffice to have reload disabled in production.
But I would also like to be able to have very different logging configurations in each environment and this can be cumbersome with the -o options, so having an include mechanism would be the optimal solution.

@hugochinchilla Yeah, I agree to include enabled keys to every plugin. As for the 'includes', let's wait for some time for the viper ticket to get merged (let's say 1-2 weeks) and then return to the discuttion. I plan it to 2021-05-11 release cycle.


Is it reasonable to use diamond(blastx) instead of blast(blastx) in the ARG-OAP？

Hi,
When my data volume is large, I want to accelerate the alignment process. So I want to ask is it reasonable to use diamond(blastx) instead of blast(blastx) in ARG-OAP ？For example, is it reasonable if I change the codes in the .py to make the alignment done by diamond?
Thanks!

yes, you can replace blastx with diamond's blastx in stage_two. the results should not be largely different if you use the same cutoff.

Thanks for your reply!

Hi!
I am interested in this replacememt, but unfortunately I am not familiar with python, I would appreciate it if you could give me a specific modification
Sincerely

Hi!
Am I right to edit the code like below
1)only change the corresponding parameters in this area and do nothing to the else.

2)exchange the stage_two.py of these directions

3)install the diamond to the environment
Sincerely

Yes you only need to replace subprocess.run([...]) with your diamond arguments. Please note the name of arguments may not be exactly identical, e.g. -mt_mode is not used by diamond.

Hi
After some attempts, it didn't work.
First,I changed subprocess.run([...]) to this:
__def extract_seqs(self):
'''
Extract target sequences using more stringent cutoffs & blast.
'''
logger.info(f'Processing <{self.setting.extracted}> ...')
nbps, nlines = simple_count(self.setting.extracted)
blast_mode = 'blastx' if self.dbtype == 'prot' else 'blastn'
    logger.info('Extracting target sequences using BLAST ...')
    logger.info(f'BLAST settings: {nbps} bps, {nlines} reads, {self.thread} threads')

    subprocess.run([
        'diamond',
        blast_mode,
        '--db', self.db,
        '-q', self.setting.extracted,
        '-o', self.setting.blastout,
        '--outfmt', ' '.join(['6'] + self.setting.columns),
        '-e', str(self.e),
        '--max-target-seqs', '5',
        '-p', str(self.thread)])

but I get this error:"Error: Invalid output format: 6 qseqid sseqid pident length qlen slen evalue bitscore"
I can not figure it out SO I just delete the"'--outfmt', ' '.join(['6'] + self.setting.columns)," to find out could it run.
But I get another error :"Opening the database... Error: This executable was not compiled with support for BLAST databases.

try this one:
subprocess.run([
    'diamond',
    blast_mode,
    '--db', self.db + '.dmnd',
    '-q', self.setting.extracted,
    '-o', self.setting.blastout,
    '--outfmt', '6'] + self.setting.columns + [
    '-e', str(self.e),
    '--max-target-seqs', '5',
    '-p', str(self.thread)])


Fixed two modeling assessment bugs

Checklist

[x] I tested all changes and all related features with different users (student, tutor, instructor, admin) on the test server https://artemistest.ase.in.tum.de.
[x] Server: I followed the coding and design guidelines.
[x] Server: I added multiple integration tests (Spring) related to the features (with a high test coverage)
[x] Server: I implemented the changes with a good performance and prevented too many database calls
[x] Server: I documented the Java code using JavaDoc style.
[x] Client: I followed the coding and design guidelines.

Motivation and Context

Description

1: Fixed bug where submission for a modeling assessment did not show up, the assessment was locked by null. (for not exam mode exercises)
2: Fixed bug where instructor could override wrong results.
Steps for Testing
1: Create a modelingexercise, participate and assess. If assessing works the bug is fixed.
2: Create an exam with two correction rounds, assess a submission in both rounds. Then try to override the result of the first round, it should be overridden correctly, and not the second result.

Some additional information about the error:

Some additional information about the error:

@airelawaleria Did you use tutor-test-users or your personal admin users?

@airelawaleria Did you use tutor-test-users or your personal admin users?

@airelawaleria Did you use tutor-test-users or your personal admin users?

Oh, we used test accounts with instructor rights since it wasn't explicitly stated otherwise. Should we re-test with tutor accounts?

@airelawaleria Did you use tutor-test-users or your personal admin users?

Oh, we used test accounts with instructor rights since it wasn't explicitly stated otherwise. Should we re-test with tutor accounts?

@airelawaleria It seems to not be an issue here as the PR got merged, but i would propose to use the test user which matches the task what one is about to do (I will try to do it myself as i dont stick to it as well :P). As an admin you can do anything and so authorization aspects are not tested.

@airelawaleria It seems to not be an issue here as the PR got merged, but i would propose to use the test user which matches the task what one is about to do (I will try to do it myself as i dont stick to it as well :P). As an admin you can do anything and so authorization aspects are not tested.


Red light all the time, can't start, can't initialize

Red light all the time, can't start, can't initialize~what can i do?

What version of the firmware are you running?
Do you have access to a serial cable as described in the readme?


Include labels in BMH scale-up logging messages

Further tweak to improve logging messages for OpenStackBaremetalSet scale-up, based on customer/partner feedback.  Also fixes the placement of the scale-up "success" message which was erroneously displayed even when no scale-up was requested.

/lgtm


virt-launcher: remove redundant cidr from dhcp server address

What this PR does / why we need it:
Remove redundant cidr from dhcp server address
A dummy cidr is added and never used. Removed it to avoid confusion.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/test pull-kubevirt-e2e-k8s-1.18

/test pull-kubevirt-e2e-k8s-1.18

/test pull-kubevirt-e2e-k8s-1.18

I am a bit confused by the commit message here.
The CIDR part is added and removed under the same function. My guess is that someone wanted to validate the address and this was the way to do so (but cannot be sure).

Can you update the commit message (and PR description) to clarify that this is not really about the CIDR, it is about the validation that is not needed? The CIDR was the way to validate.
Now that I think about it, the original reasoning could have been related to the address fitting the subnet.
Lets take an example:
Someone defines an address of <IP_ADDRESS> to the gateway. This is a valid IP address for a subnet of <IP_ADDRESS> but not valid for a subnet of <IP_ADDRESS>.
Was this what they attempted to check here? I have no idea.
Is this even possible in terms of how someone can configure it in the first place? I guess it requires a thorough check.

I am a bit confused by the commit message here.
The CIDR part is added and removed under the same function. My guess is that someone wanted to validate the address and this was the way to do so (but cannot be sure).

Can you update the commit message (and PR description) to clarify that this is not really about the CIDR, it is about the validation that is not needed? The CIDR was the way to validate.

The reason for this PR is not for removing the validation. The reason is what written in the PR message, the cidr is redundant and not being used.

Now that I think about it, the original reasoning could have been related to the address fitting the subnet.
Lets take an example:
Someone defines an address of <IP_ADDRESS> to the gateway. This is a valid IP address for a subnet of <IP_ADDRESS> but not valid for a subnet of <IP_ADDRESS>.
Was this what they attempted to check here? I have no idea.
Is this even possible in terms of how someone can configure it in the first place? I guess it requires a thorough check.

I have no idea what was the intention of this code, maybe it is just a leftover of a previous code that was removed.
But what you're saying emphasize even more the fact this dummy cidr has to be removed.
I the user specifies "vmNetworkCIDR" the parsing with the dummy cidr may fail.

/retest

/retest

/approve

/retest


Qt  and Intel realsense Getting started

librealsense
2.33.1 RELEASE

OS
Windows

Name
Intel RealSense D435

Serial Number
943222071442

Firmware Version
<IP_ADDRESS>

Advanced Mode
YES

Camera Locked
YES

Usb Type Descriptor
3.2

Product Line
D400

Asic Serial Number
943623022438

Firmware Update Id
943623022438

Firstly there is not technical issue, I didn't know where to ask as a beginner.
So If you can help...
I want to create a project using:

Qt 5.15.0 (is a must)
Visual studio 2019 (is a must)
C++
openCV 4.2.0 (if is necessary)

Actually to start I need a simpler project like those from the Examples for Intel RealSense SDK 2.0,
the "im-show"
or/and the "hello-realsense"
A code example will be the best or even better a tutorial.
Till now I didn't found something on google.
In case the above is difficult an advice on how to get start will be fine.
For example, I found: "Qt and openCV on Windows with MSVC"
Is it a good place for me to start?
Thank you in advance.

Hi @ZiSo89   I researched your request very carefully and could not find one central guide that explains everything about linking QT to Librealsense on  Windows.  I have tried to assemble together a starting-point of information though.
The first step is to install the Librealsense SDK, which you may have done by now.
Once the SDK is installed then you can go into QT Creator and follow these steps:

Go to the Open File / Projects menu option.
Browse for the CMakeLists.txt file at this location: librealsense/CMakeLists.txt

I'm going somewhere with my own question, :)
I found online and combined few projects with Qt and openCV and I rewrite in Visual Studio.

Except of few bug and safety functionality, is running. I think in next days I will fix those problems, and then I will upload it on GitHub

I'm glad you were able to make quick progress.  Good luck with your further tests!

Maybe you can have a look and suggest for improvements.  https://github.com/ZiSo89/QtIntelRealSense

My computer is not set up to test programs unfortunately.  Other RealSense QT users will find your program useful though.  Thanks so much for sharing it!


DOC: Document process for deploying updating content.

Should it be done under root, @danielballan?


Placeholder Part II: For commenting about install

The experimental section in support of #13023 now exists.  This is a placeholder so people can easily see the intended content for the Overview.  Pending are the installation instructions.
Signed-off-by: Mary Anthony<EMAIL_ADDRESS>

LGTM (so far)
Are you planning on updating this PR, or add the info in a follow-up?

I'll update this PR with the install. I figure experimental feature developers now have a basis to add their content without relying on the previous PR to close.

ping @icecrime @calavera Updated and rebased with plugin material

This needs rebase :pensive:

done.  I also need to make the install change. Give me a sec.

Author LGTM.  I'm going to merge this when the builds go green. @jfrazelle can you give a quick once over to the install section and make sure I have that correct.

LGTM, but obviously, the experimental domain is not yet up.


no-extraneous-packages should ignore invalid package names

Package names that are invalid in npm most likely use custom resolvers and won't be extraneous.
https://github.com/npm/validate-npm-package-name can be used to validate package names. I'm not sure whether legacy names should be treated as valid for the purpose of this issue.

Hi @novemberborn :)
Do you have an example of a case where this is problematic for you?

Sure. I maintain two Babel plugins which rewrite import statements: import-glob and files. An example of the latter is here:
import files from 'files:../../content/**/*.md'

I suppose this might be solved by writing a resolver for these Babel plugins (though I haven't checked whether this rule follows resolvers). However it seems to me that if we were to validate the package name (up to the first slash), then any invalid package name cannot be a valid dependency and is most likely to be use a custom resolver. In that case it won't be extraneous.

I haven't checked whether this rule follows resolvers

It does, in part.
I think a resolver here would help, though @benmosher is more knowledgeable on the subject ;)
I'm wondering whether removing anything before a : sign would help, but I don't think it does. Since tampering the file path with Webpack/Babel is way too customizable, I don't think we can do anything generic enough (though if you have ideas, would be great!). Especially in the case of your files plugin, it doesn't even link to anything resolvable, if I got it right.
A custom resolver would be the way to go I'd say, though this solution is way more cumbersome than I'd like :/
Any ideas?

Since tampering the file path with Webpack/Babel is way too customizable, I don't think we can do anything generic enough (though if you have ideas, would be great!)

I think my generic approach would be to reject anything that looks invalid. But maybe that's too generic.

Especially in the case of your files plugin, it doesn't even link to anything resolvable, if I got it right.

Correct.

A custom resolver would be the way to go I'd say, though this solution is way more cumbersome than I'd like :/

Apologies for to yet looking into how custom resolvers behave. At their simplest they could return a module path, but perhaps they could return other information for the import rules to use. E.g. 'extraneous: false, extension: '.md', isModule: false`, etc.

Apologies for to yet looking into how custom resolvers behave

I still haven't either, so no worries here :D

I think my generic approach would be to reject anything that looks invalid. But maybe that's too generic.

Well, in the case of this rule (haven't checked for the extensions rule), we actually try to determine the import type (see the src/core/importType file). But in your case, it is considered as an external package, not as the fallback unknown type, which it probably should, and that would fix your problem, at least for this rule. We could use unknown or a new type for anything that contains :.
If you use the order rule, then the type would be different, and if it's considered like a unknown type, then it will force you to put it at the end of your import statements list. We should probably document the unknown type (I didn't at the time as I thought I had covered every case ^^')
I'm :+1: with considered anything containing : as either unknown or a new type (custom?). What do you guys think? It will have an impact on other rules, so we'll have to think this a bit trhough later.

I'm  with considered anything containing : as either unknown or a new type (custom?). What do you guys think?

I think we should try and see where a path starts, and run everything before that through the validate-npm-package-name, rather than just solving for :.

I think maybe a general ignore pattern might be good.
That, or a Babel resolver that knows how to speak to plugins. I'm thinking that might be a good future-proofing strategy to avoid continually re-implementing these and other Babel plugins as custom resolver behaviors.

(Assuming that is technically feasible. It's been a while since I've looked at the Babel plugin API)

That, or a Babel resolver that knows how to speak to plugins. I'm thinking that might be a good future-proofing strategy to avoid continually re-implementing these and other Babel plugins as custom resolver behaviors.

You'd have to transpile the imports of each file, assuming you can determine the Babel config and the correct environment. Sounds tricky.

I think adding a pre-resolver ignore pattern check would solve this.
You could add ^files: as a pattern and it could solve this and #341.
I like the simplicity of requiring the user to explicitly configure patterns for import overloading like this.

I just updated and hit this issue.
We use resolve.alias in webpack:
https://github.com/shakacode/react-webpack-rails-tutorial/blob/master/client/webpack.client.base.config.js#L49
/Users/justin/shakacode/react-on-rails/react-webpack-rails-tutorial/client/app/bundles/comments/components/CommentBox/CommentForm/CommentForm.jsx
   12:1   error  'libs' should be listed in the project's dependencies. Run 'npm i -S libs' to add it  import/no-extraneous-dependencies

Any work around?

@justin808 only //eslint-disable-line import/no-extraneous-dependencies ATM, sorry 😅

I'm finally coming back to this and it appears that the import/ignore setting is not used? The patterns I'm using in my project trigger import/no-extraneous-dependencies and import/extensions.
Adding a resolver doesn't help since it doesn't influence how the source is treated. Extending that and using resolvers in all rules may be the best solution. As I wrote back in May https://github.com/benmosher/eslint-plugin-import/issues/340#issuecomment-219289413:

At their simplest they could return a module path, but perhaps they could return other information for the import rules to use. E.g. extraneous: false, extension: '.md', isModule: false, etc.

https://github.com/benmosher/eslint-plugin-import/issues/340#issuecomment-238781726

I just updated and hit this issue.
Any work around?

@justin808 Yes: https://www.npmjs.com/package/eslint-import-resolver-webpack

I'm confused - npm's validity for package names is irrelevant. Anything that's a valid directory name in node_modules is a resolvable import, according to node's require algorithm.
Just because I can't have npm-installed a package name doesn't mean I didn't mkdir it.

@novemborn import/ignore skips parsing, so you're right, it doesn't impact those rules.
I have also arrived at what you've suggested: resolvers need to return additional metadata to classify import type. #479 is tracking this. I am hoping I will be able to spend some time on it next week.

@novemberborn ^

The proper way to handle this, I think, is the "ignore" setting and/or a custom resolver. Happy to reopen if that's not the case.


chore: remove code climate

I opened this because I could not figure out how to make the code climate badge work. Turns out the issue was within shields.io. This is now resolved through #604.


Inspector - Add Catalogue data reporting if the Catalogue is installed

Check to see if the Catalogue is installed within the same database as the Inspector.
Use the Catalogue modules table to determine what modules are enabled within the catalogue and automatically report on the information collected for these modules.
More detail to be added as I start writing the code.

Missing logins has been added, this will advise when a Login has been created on the primary but not on a secondary for AG databases it will also check for mismatched SIDs.

Dropped tables check, will show information for tables dropped from databases within the last 24hours.
Dropped databases check, will show information for databases dropped in the last 24 hours.


Update data-box-disk-deploy-picked-up.md

minor change in address

@madhurinms : Thanks for your contribution! The author, @alkohli, has been notified to review your proposed change.

@alkohli please merge

Looks good. Please merge. #sign-off


Toast component

Summary of the changes
Cloned PR for toast due to rebasing issue on previous PR.
Related issue
#30
Checklist

[x] I have added relevant unit and visual regression tests.
[x] I have manually accessibility tested any changes, if relevant.
[x] I have ensured any changes match the Figma component library.

On the whole, it looks great. I had a couple of questions however:
With regards to focus, when a toast is displayed we trap focus on the toast element, but you can still use pointer to move focus to something on the base layer. I'm not sure that trapping focus is correct. As the toast doesn't behave modally (you can still interact with the background layer) I would imagine focus would continue to move to other elements on the page. The toast would be injected into the focus order immediately after the triggering element.
The aria dialog spec says this:
"Dialogs can be modal or non-modal. When a modal dialog appears on the screen, it's not possible to interact with any page content outside the dialog. In other words, the main application UI or page content is considered to be temporarily disabled as long as the modal dialog is showing. For non-modal dialogs it is still possible to interact with content outside of the dialog while the dialog is showing. Note that for non-modal dialogs there will have to be a global keyboard shortcut that allows focus to be moved between opened dialogs and the main page."
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/dialog_role
When a non-modal dialog is displayed, we should move focus to the first focusable element within, but should we also allow focus to move out of the non-modal dialog? Could we provide a mechanism (landmark?) for moving between base layer content and dialog content?
Another option would be to automatically dismiss the non-modal dialog (toast) when a user interacts with an element outside of the toast. See this example from deque univesity.
https://dequeuniversity.com/library/aria/tooltip-dialog
Inconveniently, although the WAI-ARIA authoring practices repeatedly reference non-modal dialogs being an option, there doesn't seem to be specific practices around them.
https://w3c.github.io/aria-practices/#dialog_modal
I think we should double check with the a11y team on what they suggest the best approach here is.

Similar to @ad9242's comment for the dialogs PR, I'm not sure the visual tests are adding much value. Might be worth investigating if there's a way to show the toast in the visual tests or remove them?

Have removed them from the loki tests

Looks like the commit messages might need changing as currently the changelog won't describe that there's a new toast component, it'll look more like different issues have been fixed.

Sorted 😌

On the back of the a11y testing session conducted last week, did we manage to get the auto-dismiss toast contents to be announced as a live region? It wasn't doing this when tested, but not sure if this was a browser issue.

For the neutral status version, it would be good to make it so that if a user forgets to specify an icon, no icon is displayed rather than the default. Worried the default ? icon being used as a placeholder could be confusing at it symbolizes a question. If a user doesn't override the icon, can we hide it and have the text move over to fill the width of the toast?

Addressed


Bug: build fail on Ubuntu bionic and focal on linux/arm64 when running utest while LPM is compiled with --cmake-build-type Debug

REF:

NorLab TeamCity build server (require vpn access):  Build #17
Build log: Libpointmatcher_Bleeding_build_matrix_build_and_test_multi-arch_ci_PR_docker_images_17.log.zip

Notes:

Might not be useful to fix, however the doc should warn user that utest might fail when libpointmatcher is compiled with --cmake-build-type Debug

Setup:
This command require multi-architecture docker builder set with linux/amd64 and linux/arm64 platform but note that the tests are failing on linux/arm64 only
bash build_system/lpm_crawl_libpointmatcher_build_matrix.bleeding.bash \
                                     --repository-version-build-matrix-override latest \
                                     --cmake-build-type-build-matrix-override Debug \
                                     --fail-fast -- build ci_PR_arm64v8 ci_PR_amd64

Build log summary from NorLab TeamCity build server

Stacktrace (partial)
See build log in attach

Looking at the test times, we should always be running them in Release build. For example, from the linked log:

#16 22284.6 [       OK ] DataFilterTest.SpectralDecompositionDataPointsFilter (12328508 ms)

that is over 3 hours on a single test.
For the failed tests themselves, here's my two cents: The release and debug build trigger different optimization and in some cases, order of floating-point operations by the compiler, leading to different results between these two builds.
I did some tests in the linked branch, and the tests don't fail anymore when using double precision (can be set on this line).
Note however that the tests related to IO operations start to trigger, which is caused by a different precision when saving point clouds to files.

@boxanm The cmake flag Debug is already not part of the PR to develop build matrix nor the ones for PR to master or release. Debug is only part of the bleeding edge TC build configuration. Also the failing tests are executed on arm64 architecture virtualization until we have a dedicated arm64 machine, so they are 10 time slower then the amd64 ones. All tests in Debug passes on native amd64.
That said, the faster tests are the better. However,  3 hour or 24 hour long for a test is just an inconvenient, what matter in the end is the test case ... providing it's a useful one.
Either we drop the ~3 hours long tests because we judge them irrelevant or we clearly state in the doc that the utest are not to be executed at all when compiled with other than --cmake-build-type Release.  One thing for sure is that we can't drop a test case or a build config in order to save time unless we have a fallback strategy to cover that case an other way.
I think your " two cents" take on cmake flag optimization makes a lot of  sense and  is worth investigating further to help us decide.
PS The reference  from the linked log: #16 22284.6 [ OK ] point to issue #16 from 2013, I guess that you wanted to refer something else?

PS The reference from the linked log: #16 22284.6 [ OK ] point to issue #16 from 2013, I guess that you wanted to refer something else?

Thanks, weird markdown auto-formatting happened there.
I pushed another change to the linked branch, adding a precision argument to the output stream buffers.
The tests are now stable on both debug and release when using double precision, so I suggest I create a PR and we can close this issue afterwards.

@boxanm You're a beast man.
PS Will take time next summer to optimize our CI workflow speed, ie: add arm64 native builder and improve our testing strategy


Issue 96 show notification of assemblies loading

To address issue #96

Why didn't it auto connect? I had it in my message and in the PR... grrrr

I think that the code looks fine (I'm not a WinForms expert).
However, there is not room enough in the label to present most assemblies. I tried to load a couple of assemblies and since these were located at C:\src\NUnit\nunit\bin\Release\net-4.5 I only got the text "Loading Assemblies: C:\src\NUnit\nunit\bin\Release\net-4.5\nunit.frame" and no more.

Also it is a bit strange when one loads assemblies with a lot of tests, like nunit.framework.tests.dll from the nunit project, then the label is presented for a couple of seconds. Afterwards the gui is frozen for 5-8 seconds while refreshing a lot. But perhaps we should solve this in another issue?

So question. I did have wordwrap turned on, but the size is fixed meaning that there was some clipping. EG:

I could show the file names only which would help in most cases

or i could just show the file name of a single file, but for multiple I could just the count

I rebased and went with the 3rd option as it felt the cleanest; however I wont die if I have to change it in favor of what everyone else wants.

@mikkelbu how does it look for you now?

I also like the last one the most, but I'll first have time to look at the actual code/demo it tonight, as current I get a NRE on a clean checkout. The problem is however due to #221 since the code fails in GetAvailableRuntimes.

System.NullReferenceException was unhandled
HResult=-2147467261
Message=Object reference not set to an instance of an object.
Source=nunit.gui.core
StackTrace:
at NUnit.Gui.Model.TestModel.GetAvailableRuntimes() in C:\Temp\GUI\nunit-gui\src\nunit.gui.core\Model\TestModel.cs:line 134
at NUnit.Gui.Model.TestModel.get_AvailableRuntimes() in C:\Temp\GUI\nunit-gui\src\nunit.gui.core\Model\TestModel.cs:line 106
at NUnit.Gui.Presenters.MainPresenter.InitializeMainMenu() in C:\Temp\GUI\nunit-gui\src\nunit-gui\Presenters\MainPresenter.cs:line 144
at NUnit.Gui.Presenters.MainPresenter..ctor(IMainView view, ITestModel model) in C:\Temp\GUI\nunit-gui\src\nunit-gui\Presenters\MainPresenter.cs:line 53
at NUnit.Gui.Program.Main(String[] args) in C:\Temp\GUI\nunit-gui\src\nunit-gui\Program.cs:line 85
InnerException:

Ps. Is it misleading to write "Assemblies" when we could also be loading an nunit, csproj, sln... file?

I like how it looks!
I do see some problems in how it's structured with the rest of the app...

The view now knows when tests are loading. There is nothing else like that in the view. For example, the view doesn't know when tests are running, only the presenter knows that and it tells the view what to display.

The existing IMessageDisplay in each view wouldn't work for this, obviously. I guess IMainView needs another kind of display for long-running messages. Essentially, you implemented that but gave it a name that implies it can only be used for loading assemblies, so maybe it's just a naming issue.

There's a certain logic to putting it in UiKit if we were not trying to get rid of that assembly. 😕 We can remove it as we remove other stuff, however.

Interesting perception. I see what you are saying. I know in WPF it isn't too hard to put a panel on top of everything that is transparent  and so i'd only show what I want to without the user being able to click or keyboard navigate around. I'll give it some thought this week as I have a pressing matter at work that i need to get out of the door. My first thought is to take the code that I added to the view out. Change the presenter to disable being able to run tests, Then either making a different type of view or message interface make it sit on top of the GUI. I believe we could use this as well just like in V2 for when tests are loading.


[5.6] Join once and replace join

Added two methods to builder:
joinOnce - applies join only once for one table, other joins for this table will be ignored.
replaceJoin - applies current join for table and remove all previous joins for this table.

Can you explain more why this is useful and provide some use cases?

One of cases is - you have something like a report builder.
It collect query by different conditions. It can be a lot of handlers to compile query and inside one of them you don't know, joined the table you want already or not. You don't want join it twice. You can use in all places joinOnce method and be no warring about it will be join twice.
Simple example:
$query = (new User)->newQuery()
 ->tap(new FirstHandler)
 ->tap(new SecondHandler)
 ->get();

class FirstHandler
{
    public function __invoke(Builder $query)
    {
           $query->join('profiles', ...);
    }
}

class SecondHandler
{
    public function __invoke(Builder $query)
    {
          // Here i don't know is profiles table was already joined?

          // But if I will use $query->joinOnce('profiles') - all will be ok, no double join.

          $query->joinceOnce('profiles', ...);
    }
}

No plans to add this.


Pods Support?

I'm getting a ton of errors when trying to run my Objective-C projects. In particular, I'm getting a lot of errors with my third-party pods. So, I was wondering if pods are supported? I'm also not sure if I'm setting the pods up correctly. Should I go about installing Cocoapods and doing a pod update? I just copied the pod folder with source along with the application source and ran the vsimporter tool.

@aluong-yammer Are they import errors or build errors? i.e. is vsimporter failing or is something failing to build?
Pods support is something we're working towards.

There weren't any errors when vsimporter runs. I see the errors when building.

When I use vsimporter to generate a solution from a project which uses Pods, the first build errors I encounter are related to issue #58.

We should find a way for vsimporter to provide better feedback.


Added alias system

where a creator can designate a name for their wake command(all commands are assured the name of the file will work).  Along with updated the help plugin to reflect these aliases.

oh and also, get prettier and set it up to run on save (thank me later)
https://www.codereadability.com/automated-code-formatting-with-prettier/

@joey-colon Just so you know this pull request needs you to approve the requested changes. and you can review it further if you want.


Pen Support (Lenovo)

I have been trying to use my pen for my laptop (Lenovo Flex 14) with this app as it has multiline handwriting support. Is it only supported on the Surface, or do I have to turn something on in settings?

Oh, I figured it out, if you tap on the line numbers it takes you to the pen writing.


[eporner] update

Recently eporner slightly changed the URL layout, the ID that used to
be digits only are now digits and letters, so youtube-dl falls back to the
generic extractor that doesn't work.
Fix the matching regex to allow letters in ID.

Add a test.

Commit updated, added a test:
$ nosetests -v test/test_download.py -m porner
test_Eporner (test.test_download.TestDownload) ... ok
test_Eporner_1 (test.test_download.TestDownload) ... ok

Ran 2 tests in 2.139s
OK

Thanks! Do you want to be listed in https://github.com/rg3/youtube-dl/blob/master/AUTHORS? If so under what name?


fixed error in verbose mode for missing dihedrals

PR Summary:
This is relate to a few recent issues posted.
https://github.com/mosdef-hub/foyer/issues/326
https://github.com/mosdef-hub/foyer/issues/323

There was a coding issue in the part of the code that would write out a missing RB dihedral when in verbose mode (undefined parameters referenced).  Also, only ids were being output, not types (inconsistent with, e.g., how angles were outputted).   The coding and formatting issues have been addressed.

Even when fixing that coding/formatting issues, the code only checked the RB torsions. So, when I was testing periodic torsions, it alerted that all dihedrals were missing.    This bit now has two loops, first looping over proper_dihedrals and then rb_torsions in parmed structure.

PR Checklist

[ ] Includes appropriate unit test(s)
[ ] Appropriate docstring(s) are added/updated
[ ] Code is (approximately) PEP8 compliant
[ ] Issue(s) raised/addressed?

Hey @umesh-timalsina @justinGilmer looks like we are having some issues with the tests not running here as well.

Totally didn't see Ray's PR when I put this together.  I merged in his additions to the error messages.  I think we are good to go whenever these checks complete.  I'll merge it at that point.


Yandex Email doesn't work?

When I try via IMAP I get this error "No known authentication method supported"
Is this a limitation of JMAP or the demo? If imap/smtp is enabled/supported on the email server JMAP should work right?

This repo is just for the frontend UI demo. This sounds like a potential issue with the Perl proxy that connects to and IMAP store; you can find that repo at https://github.com/jmapio/jmap-perl and file an issue.
Please not, JMAP itself is a specification for an application synchronisation protocol, independent of IMAP, so I'm not sure what you mean by "limitation of JMAP" in this context.


SlickFilter + SlickGoTo + Responsive don't work together.

If I use SlickFilter followed by SlickGoTo (to reset the slide index to 0 when the filter changes), it works only if I don't use Responsive settings.
====================================================================
http://jsfiddle.net/j3271fs9/
====================================================================
Steps to reproduce the problem

Click to 2nd or 3rd slide.
Click Filter.
Click Unfilter.

The slider won't go back to the start. If you delete the responsive block, it works as expected.
====================================================================
What is the expected behaviour?
Slider resets to 0th index.

Hi Ken, is a fix in planning?


[Candidate 1v1 Double Damination ZH v4] There are water sounds by the dams before there is any water

Issue Description
There are water sounds by the dams before there is any water.
Expected behavior
Water sounds spawn after dam destruction, if technically possible.
Videos
https://github.com/TheSuperHackers/GeneralsRankedMaps/assets/4720891/f63e29b6-7f93-4ece-935f-047aee550f06

there is water, but I agree that it is not as visible - I'd take it as a sound cue that the dam is there and ready to be exploded

Perhaps it is possible to have shallow water at the dam before killing it? Is this possible? This would help give the clue for dam breakage and fit the water sounds.

at the dam... where? I mean it is already behind it... I would not reeeeeaally like to add any more water sources

In front of the dam. Shallow water. Then after dam break, deep water.

wouldn't that just make it impassable?

wouldn't that just make it impassable?

I think so,
I think current is fine, gives a clue that there's water behind the dam.

wouldn't that just make it impassable?

No, shallow water like in "AKAs Magic" map. Unit can drive over it.

let me have a look

As designed.


Integrate symbolic shape inference

Port and integrate symbolic shape inference from ONNX Runtime as an analysis pass / feature

Another issue that is relevant is: enable shape-inference for ORT's custom ops (in the optimizer/rewriter, which currently uses onnx shape inference).
Is the above issue intended for the same purpose, or is it intended to enable the "symbolic" part? Wondering if we should create a separate issue or not (for issue I mention).

I created the issue thinking we may be able to absorb the symbolic shape inference tool from onnxruntime as a pass. We may be able to enable shape inference for ort ops via the same route?


Fix SRV types and glibc compatibility, with some small improvements

This PR:

Most importantly, fixes the types for SRV priority and weight. This is a backwards incompatible change.
Uses usize instead of u64 to fix the build against glibc headers.
Makes it easier/possible to build this project with glibc headers installed to a different location.
Derives some types to make debugging/usage/testing more convenient.

I'm happy to split these up or make other adjustments as you see fit.

Thanks!  I haven't used this crate in years. Glad to have another set of eyeballs keeping it honest.
If you think I should publish (and under a new version) I can do that.

A new release would be nice! Note that this is a backward-incompatible change because the SRV types changed.
Another recent PR (#10) also has backward-incompatible changes, so you may want to wait to release until that is merged (if you decide to merge it as-is).


[WFLY-17733][WFLY-17734] Upgrade to Kafka Clients 3.4.0 and change em…

…bedded Kafka
Migrate tests to work with the new embedded Kafka
https://issues.redhat.com/browse/WFLY-17733
https://issues.redhat.com/browse/WFLY-17734

Thanks @kabir


Unzipped file.zip in the root directory

@hasan-mavlonov There are several files in the request, along with file.zip. It must not be there. Please remove file.zip and make pull request again.  I have to close this request without merging. Thank you for your understanding.

@hasan-mavlonov Please do not make files undeletable in the request. I must reject the request because file.zip must not be present there. Thank you for your understanding.


Bootstrap blocks CSS color property "var(--colorname)"

macOS 10.13.6 / Safari 11.1.2 (13605.3.8) / Sublime Text 3 3.1.1 Build 3176
CSS3 style :root { --skyblue: #0099FF; }
a { color: var(--skyblue); }
Bootstrap must be removed from document for var(color) to work in Safari. Feedback also to Apple.
link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/4.0.0-beta.3/css/bootstrap.min.css" integrity="sha384-Zug+QiDoJOrZ5t4lssLdxGhVrurbmBWopoEl+M6BdEfwnCJZtKxi1KgxUyJq13dy" crossorigin="anonymous"
bootstrap code from Sublime Package Control HTML Page Snippets
https://packagecontrol.io/packages/HTML Page Snippets
Bootstrap blocks CSS color property "var(--colorname)"

Bug reports must include a live demo of the problem. Per our contributing guidelines, please create a reduced test case via JS Bin and report back with your link, Bootstrap version, and specific browser and OS details.

This is a saved reply.


VCF's should not include IUPAC bases in the REF column.

This is a repeat of #295 with modifications & cleanup, was awkward to fix up that PR.

👍

Any chance you could take a look @ekg? I'd prefer not to create a customised copy of the ref genome to avoid getting these in the VCFs.


Brian/twap impl

Pull Request Test Coverage Report for Build 7900

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
1605 unchanged lines in 67 files lost coverage.
Overall coverage decreased (-98.8%) to 1.157%

Files with Coverage Reduction
New Missed Lines
%

contracts/core/lib/SetMath.sol
2
0%

contracts/core/tokens/SetTokenFactory.sol
2
20.0%

contracts/core/modules/lib/ModuleCoreStateV2.sol
3
0%

contracts/core/modules/lib/ModuleCoreState.sol
4
0%

contracts/core/extensions/CoreOperationState.sol
5
0%

contracts/core/extensions/CoreFactory.sol
6
0%

contracts/core/lib/ExchangeWrapperLibrary.sol
6
0%

contracts/core/lib/Rebalance.sol
6
0%

contracts/core/liquidators/impl/AuctionGetters.sol
6
0%

contracts/core/liquidators/twap-impl/TWAPAuctionGetters.sol
6
0%

Totals

Change from base Build 7898:
-98.8%

Covered Lines:
22

Relevant Lines:
1627

💛  - Coveralls


fitness calculators | oring properties

hi @spodila  just testing out fenzo
Seeing the binpackingfitnescalculators.*  it's effectively

sum ( fitness_i( request ).... + fitness_n( request) ) /  total_fitness_fns

# or | fitness |

Wondering if it'd be worth it to make it OR objects... so that one can do

builder.
           .....
           .withFitnessCalculator ( Fitness1 | Fitness2 | Fitness3 )
           .build()

Interested in a patch?
I guess two things:

You can use constraints to do what I want - effectively further filtering of machines to offers
Since there are fairly small set of resources on mesos (cpu, mem, gpu, bandwidth)... it's not really too bad to have 4 or even 10 (in the future) that are hard coded since for most workloads you'll need CPU + mem so the permutations are not that many ... w/ or w/out network, w/ or w/out gpu.. etc.

Hello @senior7515 thank you, hope you find it useful.
Could you elaborate on what you mean by the OR operation here?
Fitness functions are expected to return a double value between 0.0 to 1.0. So, does your expression translate to, for example,
.withFitnessCalculator ( 0.1 | 0.4 | 0.67 )

Sounds like I may have misinterpreted your suggestion?

ah sorry, I mean to say combiner operation.
Say you have binpacking.cpu as well as binpacking.mem
you would then be able to say:
.withFitnessCalculator (binpacking.cpu | binpacking.mem)

The result, internally would be: ;
double result = binpacking.cpu ( request ) + binpacking.mem( request ) / 2.0

which is exactly what happens right now internally.

OK, this sounds good. Looking forward to your PR.