Rubber banding on client side

Describe the bug
Client devices are experiencing rubber-banding frequently (multiple times per minute).
To Reproduce
Happens continually throughout world
OS information (IMPORTANT)

OS:  Proxmox>UbuntuVM>Docker
Palworld Version:  3.1 (today's patch)
Docker Image Version:

Hardware information (IMPORTANT)

CPU:  12x core 10th gen i5 3.2ghz
Memory:  32gb DDR4

Additional context
Approx 40% memory consumed;
CPU average around 55%
Bug Report Checklist

[x ] I searched for my issue on the Known issues page
[x ] I searched for my issue in the Closed issues
[x ] I have included all relevant information required above.
[ ] I am willing to fix this bug

Hi @tylerlucas Is this since the Sakurajima update?

Yeah, noticed this too with the new update

Really need to do a bare metal test on the same host and compare. Still
seeing it on my end with memory <50% and CPU at 60%
On Thu, Jul 4, 2024 at 3:34 PM XXMINECRAFTGODXX @.***>
wrote:

Yeah, noticed this too with the new update
—
Reply to this email directly, view it on GitHub
https://github.com/thijsvanloef/palworld-server-docker/issues/569#issuecomment-2209615444,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACAIAT3ZWEH6FTDLGJGYGGDZKXEXRAVCNFSM6AAAAABKCRVOC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGYYTKNBUGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

I do not believe it's related to the docker image, official servers are
unstable and rubber band too.
On Thu, Jul 4, 2024 at 6:41 PM tylerlucas @.***> wrote:

Really need to do a bare metal test on the same host and compare. Still
seeing it on my end with memory <50% and CPU at 60%
On Thu, Jul 4, 2024 at 3:34 PM XXMINECRAFTGODXX @.***>
wrote:

Yeah, noticed this too with the new update
—
Reply to this email directly, view it on GitHub
<
https://github.com/thijsvanloef/palworld-server-docker/issues/569#issuecomment-2209615444>,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/ACAIAT3ZWEH6FTDLGJGYGGDZKXEXRAVCNFSM6AAAAABKCRVOC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGYYTKNBUGQ>

.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/thijsvanloef/palworld-server-docker/issues/569#issuecomment-2209618470,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABB3GKC4QST4JKAS3IOFGVLZKXFSRAVCNFSM6AAAAABKCRVOC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGYYTQNBXGA
.
You are receiving this because you commented.Message ID:
@.***>

Closing this issue, as it is not related to the image.
This is something that needs to be addressed by the Palworld devs.


Float datatype should be Number

See file ngsi.py, line 64.
Float is no ngsi datatype.
Compatibility with Quantumleap is broken.
We should use "Number" instead of "Float".
See:
Fiware data models:

https://fiware-datamodels.readthedocs.io/en/latest/guidelines/index.html
“When possible reuse schema.org data types (Text, Number, DateTime, StructuredValue, etc.).”

Schema.org

https://schema.org/DataType
https://schema.org/Number

Fixed in v2.1.8 : "Number" used instead of "Float" and "Integer".
Sorry for the inconvenience with QuantumLeap.


Add Victor in the Team page

Deploy preview for openbuildservice ready!
Built with commit d341bc254772963f15a044fca07c988cc33da5ca
https://deploy-preview-174--openbuildservice.netlify.com


[PR] Please merge PR and create release

Please merge PR #10 and #12 and release new version. Thank you @rkoval ! :-)

Sorry for the delay here, check out https://github.com/rkoval/alfred-aws-console-services-workflow/releases/tag/v2.3


Prepend namespace name to ClusterRoleBinding for vault Helm Chart

Signed-off-by: Sam Weston<EMAIL_ADDRESS>

Q
A

Bug fix?
no

New feature?
yes

API breaks?
no

Deprecations?
no

Related tickets
fixes #991

License
Apache 2.0

What's in this PR?
Prepends the namespace name to the ClusterRoleBinding name to allow for multiple releases with the same name in the same cluster (but different namespaces).
Why?
Fixes #991

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

/assign @bonifaido


Docker build for campaigns and contact modules

Workflow that builds contact/campaigns on each PR/push to master. Closes  #311.

Please squash all these commits when merging😄


fix(theme): <Tabs> props should allow overriding defaults

Pre-flight checklist

[x] I have read the Contributing Guidelines on pull requests.
[ ] If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
[ ] If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

By switching the priority of inner properties (...tabs) with input properties (...props), we allow the users to control the selectedValue (i.e. switch tabs), as well as to pass a hook selectValue to act on a tab switch.
This is a minor change that should improve UX while not changing anything else.
Test Plan

Existing tests should suffice, since no major change was introduced, only the place of the variables was swapped to give higher priority to the input props
Test links
https://deploy-preview-10091--docusaurus-2.netlify.app/docs/markdown-features/tabs/
Related issues/PRs

Related to this feature request: https://docusaurus.io/feature-requests/p/pass-active-attribute-to-tab-children

Thanks
Ok to do this change, although I'm not sure I'd want to recommend this pattern considering you can mess up with internals.
Note that we won't expose the 3 things you can now override in the TS typedefs, to prevent most users from using those props.
I'm really curious to know how you plan to use those props.  Maybe it would be better to expose a controlled variant of the underlying component instead?

@slorber I needed this to make my tabs change as the user scrolls through the docs:
PREVIEW: https://docs-preview-pr-1919.onrender.com/build/smart-contracts/anatomy/
Relavant lines of code:

use value and hook: https://github.com/near/docs/blob/c511919d2d88c8abc4b098361be6f0dcc8c42354/website/src/components/code-explainer.js#L108
select the line on scroll: https://github.com/near/docs/blob/c511919d2d88c8abc4b098361be6f0dcc8c42354/website/src/components/code-explainer.js#L77-L82
usage: https://github.com/near/docs/blob/c511919d2d88c8abc4b098361be6f0dcc8c42354/docs/2.build/2.smart-contracts/anatomy/anatomy.md?plain=1


How to actually install this?

Sorry if there is an obvious answer, but I tried go get github.com/vkrasnov/dictator and instead of installing a command in $GOPATH/bin, it only built /home/d33tah/GOPATH/pkg/linux_amd64/github.com/vkrasnov/dictator.a. What am I doing wrong?

Try go install github.com/vkrasnov/dictator/cmd

@vkrasnov Thanks, that installed it as "cmd". If I might have a suggestion, renaming the binary name to "dictator" could be helpful :) Anyway, on my side, the issue can be closed.
Thanks!

Maybe add a readme with simple instructions?


[WIP] 1.0.0 Release

This is a tracking issue for the 1.0.0 release. This contains a checklist of all things that should be completed before release.

[x] Dimension creation

This should allow players to choose the type of dimension, seeds, and other information.

[x] Dimension deleting

[ ] Permission-restricting dimensions

This will NOT be an integration with Permissify. We're not bad people, and we don't want to force players to use a plugin that they might not want to use. This will be split into permissions like: dimension.<dimension_name>.allow and dimension.<dimension_name>.deny. This will also be an OPTIONAL feature, enabled through the configuration.

[x] Dimensional Portals

These portals should be permission restricted too, using the same syntax as above, but with the prefix dimensional_portal instead.

[ ] Command to send a specific player to another dimension

[ ] Portal delete

[x] Portal Create

[ ] List current registered worlds

[ ] Allow preload of a specific set of worlds, or all worlds

Configuration option.

[x] Command to send self to a dimension

[ ] Default world

[ ] MySQL backend

[ ] YML Backend

THIS LIST IS SUBJECT TO CHANGE AT ANY POINT IN TIME.

I have decided against the above comment. I'll just make a cool thing that lets platforms implement their own flat-file handler. Maybe someone for some reason wants it


Set Scala versions using properties

Make sure that we set the Scala version at a single place, and that makes it easier to override the properties to set the Scala version of our liking.

@Fokko would you please rebase / merge your work against current master so that we can do a clean merge post approval?

Thanks, @arvindshmicrosoft for the review, I've swapped the properties.

Thanks @Fokko - apologies but it looks like your latest commit did not really change to the desired behavior. Can you double-check?

Hello again @Fokko - could you please double-check your latest commit? It seems to not have the correct property names as we discussed. As previously mentioned we would like to have scala.version as 2.11 and scala.binary.version to include the minor version i.e. 2.11.8

@arvindshmicrosoft I misinterpreted your comment, and I disagree with the suggestion. I would keep it congruent with Spark: https://github.com/apache/spark/blob/master/pom.xml#L164


New syntax

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
✔

Fixed issues
#193, #171

- use Yiisoft\Router\Route;
- use Yiisoft\Router\Group;
+ use Yiisoft\Router\Builder\RouteBuilder as Route;
+ use Yiisoft\Router\Builder\GroupBuilder as Group;

Group::create()->routes(
    Route::get('')->name('index'),
-   Route::get('/posts')->name('posts'),
+   Route::get('/posts')->name('posts'), // No getters, only setters
+   new Route(['GET'], '/'),
);

In this PR keep routes/groups object and additional add new routes/groups objects with named arguments. Seems, this decrease performance...

We can mention it in docs or drop the current syntax.

This not fix https://github.com/yiisoft/router/issues/171.

Yes, doesn't fix directly. Since there is no exception, there is no need for it.

We can mention it in docs or drop the current syntax.

But what goal of syntax change?


Support larger file sizes

I'm getting some 413 errors Request entity too large when syncing some data - would you consider setting client_max_body_size in the nginx configuration to support larger file sizes?

I think an environment variable is the way to go, disabling it completely may not be expected behavior or what people want per default.

@zeitchef Please test this tag. You'll have to add the variable NGINX_CLIENT_MAX_BODY_SIZE (be sure to include the units). Example docker-compose was updated here.


Nested preloading

I'd like to do something like this, but I don't think it's possible:

type City struct {
    Id int
    Name string
}

type Address struct {
    HouseNumber int
    Street string

    City City
    CityId int
}

type Order struct {
    Address Address
    AddressId int

    User User
    UserId int
}

type User struct {
    Id int

    Orders []Order
}

db.Model(user).Preload("Address").Preload("Address.City").Related(&orders) // Address.City is not a relation in Order, so it's ignored

Hi @nkovacs
Yes, this is not supported yet, but on the plan already.

:+1: would be lovely if gorm supports this.

I'm also looking forward to this. Any cues/ideas on how the api will be?

It will like @nkovacs's example.
db.Model(user).Preload("Address").Preload("Address.City").Related(&orders)

That would be really useful.

@jinzhu Can you confirm, this feature is working now?
https://github.com/jinzhu/gorm#nested-preloading
If it works, I think we also can update http://stackoverflow.com/questions/29230261/how-preload-a-full-hierachy-in-go-using-gorm

Hi @rtm7777
Yes, it is works already. sorry forgot to update this issue.

Keep in mind that this implementation uses subsequent SELECT(s). While this is great for simplicity (and perhaps multi-level caching with the correct callback configuration) ... it's also could be optimized by using JOIN statements to reduce latency to/from the server from multiple queries.


1.20.2 issue?

I don't know if this is a 1.20.2 issue, but I get an error during load, and when I try to join a server, I get this and it doesn't connect.
Client disconnected with reason: Internal Exception: java.lang.NoSuchMethodError: 'net.minecraft.class_1934 net.minecraft.class_2678.comp_90()'

1.20.2 requires few code changes, you can't use 1.20.1 version. I will update in few days

Added 1.20.2 version

yep, works.


Upgrade dependencies version

Some notes:

queue-async is deprecated. Should we use d3-queue instead or do you prefer keeping the old package?
tilelive last release is 6.0. Any reason to not use that?
mocha last release is 5.2.0. I guess there might be some issue with not automatically force closing the test if they leave open sockets, right? The old behaviour can be reproduced using --exit (or by fixing the tests).

Security (building Windshaft-cartodb):
Pre-update:
[!] 49 vulnerabilities found [2253 packages audited]
    Severity: 10 Low | 33 Moderate | 5 High | 1 Critical
    Run `npm audit` for more detail

After update:
[!] 49 vulnerabilities found [2259 packages audited]
    Severity: 11 Low | 32 Moderate | 5 High | 1 Critical
    Run `npm audit` for more detail

Performance
Using random point datasets [0, 10, 100, 1000, 10000, 100000], marker symbolizer, 30 warm-up requests, 3000 requests analyzed):
pre_update_large_vs_post_update_large.pdf
I don't see any significant difference (a slight improvement if anything at all).

queue-async is deprecated. Should we use d3-queue instead or do you prefer keeping the old package?

Moving to d3-queue requires changes in the code base, there are some breaking changes that must be resolved and I didn't want to add more entropy to this PR. I want to tackle this in a separated PR.

tilelive last release is 6.0. Any reason to not use that?

yarn outdated didn't tell me anything about<EMAIL_ADDRESS>¯_(ツ)_/¯

mocha last release is 5.2.0. I guess there might be some issue with not automatically force closing the test if they leave open sockets, right? The old behaviour can be reproduced using --exit (or by fixing the tests).

As mentioned above, I want to tackle this in a separated PR.

I think that yarn might have failed to warn you about tilelive because it changed scope from global to @mapbox.

I think that yarn might have failed to warn you about tilelive because it changed the scope from global to @mapbox.

Yep, that's it. As this requires changes in the codebase, I'll tackle this in a separated PR


Want to build custom layer just before Conv2d layer using keras  for that how do I initialize filter weight to zero

Please make sure that this is a Bug or a Feature Request and provide all applicable information asked by the template.
If your issue is an implementation question, please ask your question on StackOverflow or on the Keras Slack channel instead of opening a GitHub issue.
System information

Have I written custom code (as opposed to using example directory):
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
TensorFlow backend (yes / no):
TensorFlow version:
Keras version:
Python version:
CUDA/cuDNN version:
GPU model and memory:

You can obtain the TensorFlow version with:
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
You can obtain the Keras version with:
python -c 'import keras as k; print(k.version)'
Describe the current behavior
Describe the expected behavior
Code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate the problem.
Other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

Hi!
This issue isn't related to a bug/enhancement/feature request or other accepted types of issue.
To ask questions, please see the following resources :
StackOverflow
Keras Slack channel
Keras.io support
Gitter
Thanks!
If you think we made a mistake, please open another issue explaining your request in detail.


fix init_model with subset

to fix #2240

@guolinke Test has been added.

Sorry, i edit the code in the mobile browser, there are many typos...

Hmm, I thought that in the second case type should be string, not None...
import numpy as np
import lightgbm as lgb

data = np.random.random((500, 2))

train_data = lgb.Dataset(data, free_raw_data=False)
type(train_data.construct().get_data())
>>> numpy.ndarray

train_data.save_binary('train_data.bin')
train_data = lgb.Dataset("train_data.bin")
type(train_data.construct().get_data())
>>> NoneType

@StrikerRUS
It seems the free_raw_data=False is needed in  train_data = lgb.Dataset("train_data.bin").

It seems the free_raw_data=False is needed in train_data = lgb.Dataset("train_data.bin").

Sure, you are right! Sorry for my mistake!

Would it work if train data is loaded from a saved binary file?

Binary file cannot used for prediction, so it cannot

I do not understand the reason why training from a subset of a binary file works while continue training does not.
'''
import numpy as np
import lightgbm as lgb
data = np.random.random((500, 2))
y = [1] * 250 + [0] * 250
lgb_train = lgb.Dataset(data, y, free_raw_data=False)
lgb_train.save_binary('lgb_train.bin')
lgb_train = lgb.Dataset("lgb_train.bin")
subset_index_1 = np.random.choice(np.arange(500), 300, replace=False)
subset_data_1 = lgb_train.subset(subset_index_1)
subset_index_2 = np.random.choice(np.arange(500), 200, replace=False)
subset_data_2 = lgb_train.subset(subset_index_2)
params = {
'objective': 'binary',
'verbose': -1
}
init_gbm = lgb.train(params=params,
train_set=subset_data_1,
num_boost_round=10,
keep_training_booster=True)
gbm = lgb.train(params=params,
train_set=subset_data_2,
num_boost_round=10,
init_model=init_gbm)
'''

@guolinke

Binary file cannot used for prediction, so it cannot work.

I just pushed the update for the test with that case.
Also, fixed bug params -> self.params.

@guolinke Seems that a lot of new warnings are generated now from old tests:
tests/python_package_test/test_basic.py::TestBasic::test_subset_group
tests/python_package_test/test_engine.py::TestEngine::test_cv
tests/python_package_test/test_engine.py::TestEngine::test_cv
tests/python_package_test/test_engine.py::TestEngine::test_cv
tests/python_package_test/test_engine.py::TestEngine::test_cv
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_metrics
tests/python_package_test/test_engine.py::TestEngine::test_reference_chain
  /home/travis/.local/lib/python3.6/site-packages/lightgbm/basic.py:1466: UserWarning: The raw data of the subset reference is released, cannot call get_data().
    warnings.warn("The raw data of the subset reference is released, cannot call get_data().")

@StrikerRUS I think we should set free_raw_data=false in these tests.

@guolinke OK. But maybe warning message should be reworked somehow, because I can't see explicit calls of get_data() there?

@StrikerRUS maybe another good solution is avoiding to free the data with subset?
But this is hard, for users may call construct before subset.

@guolinke Yeah, there are a lot use-case...

@StrikerRUS I think these warning are needed, for get_data is a public method and could be called by user.
As for the warning in tests, I use free_raw_data to avoid the unnecessary calls of `get_data'.


multicellular organismal process

Could we make this terms "not for direct annotation"
Only has 2 direct annotations.

@vanaukenk
The 2 direct annotations are from WB based on PMID:15157420
Maybe they can just be deleted? There are other annotations.


bug: ion-datetime max limitation doesn't work when hour or minute is set to 00

Bug Report
Ionic version:

[x] 5.0.1
Current behavior:

ion-datetime with max limitation doesn't work at hour or minute when the hour or minute is set to 00.

Expected behavior:

when the hour or minute of max limitation is 00, the datetime picker should not let users select any other hour or minute but 00.
Steps to reproduce:

https://stackblitz.com/edit/ionic-ssg5bc
Related code:

  <ion-item>
    <ion-label position="floating">Max limitation doesn't work at hour when it's 00 at hour</ion-label>
    <ion-datetime displayFormat="MMM D YYYY H:mm" min="2020-02-27T00:02:27.446-05:00" max="2020-02-28T00:02:27.446-05:00"></ion-datetime>
  </ion-item>
  <ion-item>
    <ion-label position="floating">Max limitation doesn't work at minute when it's 00 at minute</ion-label>
    <ion-datetime displayFormat="MMM D YYYY H:mm" min="2020-02-27T01:00:27.446-05:00" max="2020-02-28T01:00:27.446-05:00"></ion-datetime>
  </ion-item>

Other information:

Ionic info:

Ionic:

   Ionic CLI                     : 6.1.0 (/usr/local/lib/node_modules/@ionic/cli)
   Ionic Framework               : @ionic/angular 5.0.1
   @angular-devkit/build-angular : 0.803.25
   @angular-devkit/schematics    : 8.3.25
   @angular/cli                  : 8.3.25
   @ionic/angular-toolkit        : 2.1.2

Capacitor:

   Capacitor CLI   : 1.5.0
   @capacitor/core : 1.5.0

Utility:

   cordova-res : 0.9.0
   native-run  : 0.3.0

System:

   NodeJS : v13.9.0 (/usr/local/bin/node)
   npm    : 6.14.1
   OS     : Linux 5.3

PS:
English is not my native language. I've tried my best to describe and demonstrate the bug. Please let me know if you need any other information.

Thanks for the issue. This has been resolved via https://github.com/ionic-team/ionic/pull/20665 and will be available in an upcoming release of Ionic Framework.


Fixes for iOS and fully working with Android (including Oreo, Pie, Q)

IOS, We fixed the issue with the RNBoundary.podspec
Android, We fixed the issue with startService when the app is in background and correctly handling it using a startForegroundService with a binded notification.

Any news on the delivery date for the fix?

When do you think this fix will be merged?

cc @eddieowens

@eddieowens is this going to be merged or should I use @woffu's fork?

Any news if this will be merged?

@woffu Your fixes seem to work! Great stuff.
But could you maybe give me an example on how to handle events when the app was killed?
I add some boundaries, I attach EXIT and ENTER listeners. Everything works while the app is in foreground or in background.
When I kill the app and leave the boundary, I can see in the React Native Debugger that the App is triggered. The console logs an onExit event from the boundary index.js file. But the listeners that I attached are not called. I guess the reason is that they were destroyed when the app was killed.
I tried to attach the listeners again on App start in my index.js file (I guess that is the earliest time I can do something) but it did not work.
Since you worked with this feature could you maybe give me an example on how you listened to ENTER/EXIT events when the app was killed?
Help is very much appreciated!

Hi @woffu ,
great work, thanks for the PR!
That PR has been open for months and there is no update,
I need to do the same fix for iOS (work in the background), I have merged it in my own PR https://github.com/eddieowens/react-native-boundary/pull/56
I wonder if we should start maintaining that project in another github?


[SPARK-49477][PYTHON] Improve pandas udf invalid return type error message

What changes were proposed in this pull request?

This PR improves the error message when the specified return type of a pandas udf mismatch the actual return type.
Why are the changes needed?

To improve the error message.
Before this PR:
pyspark.errors.exceptions.base.PySparkValueError: A field of type StructType expects a pandas.DataFrame, but got: <class 'pandas.core.series.Series'>
After this PR:
pyspark.errors.exceptions.base.PySparkValueError: Invalid return type. Please make sure that the UDF returns a pandas.DataFrame when the specified return type is StructType.
Does this PR introduce any user-facing change?

No
How was this patch tested?

New unit test
Was this patch authored or co-authored using generative AI tooling?

No

Merged to master.


Write a C program to convert string to snakecase

Description
Write a C program to convert string to snakecase
Snakecase is a style of writing in which all letters are lowercase and spaces are replaced with underscores.
Input  : "hello world"
Output : "hello_world"

How to contribute

Save the solution in program/ConvertStringToSnakecase.c file
Add ConvertStringToSnakecase.c file in convert-string-to-snakecase folder

!assign

!assign


Removed side effects (fixes #3), Bumped dependencies

See #3.
Will fix the mentioned issues and clones the array properly before modifying. I also updated some dependencies and the TS version.

:tada: This PR is included in version 1.1.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Figure out testing

I don't care about super solid coverage but the workflow of edit-template-generate-run-app is annoying and I want some automated tests.
I want to use https://github.com/hackebrot/pytest-cookies, but installing it fails with an error installing pyyaml, see e.g. https://github.com/python-poetry/poetry/issues/8287, which I can't figure out a workout for, so punting on testing for now

The yaml error randomly went away 🤷🏻


Lineage API depth -1 throws 500 error

Describe the bug
Lineage API depth -1 throws 500 error. Negative depth is not supported . Instead of throwing exception it should gracefully handle the error
To Reproduce
GET call on lineage api - http://localhost:8080/api/v1/lineage/table/LOREM?bw=-1&fw=-1
Unexpected error constructing lineage for table "LOREM"

Expected behavior
Should return Validation Error (404)  status code with formatted json Response
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. MacOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

@sambekar15  can I take this one?

@sambekar15 can I take this one?

Sure . Assigned to you.


[WIP][#744] FkHitRefresh now doesn't do IO inside constructors

Fix for issue #744. Several concerns remain:

There are lots of other places where exceptions are thrown from constructor. I thought about marking them with puzzles but PDD doesn't accept them, saying that they are duplicates to each other (which is true, because the issue is the same everywhere).
Private class HitRefreshHandle was introduced, and there is one mutable field in there. It may have been eliminated by means of StickyScalar from Cactoos, but it is external dependency which is not allowed in Takes.

@yegor256 please, pay attention to this pull request

Job gh:yegor256/takes#745 is in scope.

@rultor merge

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@skapral @yegor256 Oops, I failed. You can see the full log here (spent 5min)
+ status=queued
+ '[' queued == null ']'
+ '[' queued == success ']'
+ '[' queued == failed ']'
+ echo 'waiting for AppVeyor build 2856: queued'
waiting for AppVeyor build 2856: queued
+ sleep 5s
+ true
++ jq -r .build.status
++ curl -K ../curl-appveyor.cfg https://ci.appveyor.com/api/projects/yegor256/takes/build/2856
+ status=running
+ '[' running == null ']'
+ '[' running == success ']'
+ '[' running == failed ']'
+ echo 'waiting for AppVeyor build 2856: running'
waiting for AppVeyor build 2856: running
+ sleep 5s
+ true
++ curl -K ../curl-appveyor.cfg https://ci.appveyor.com/api/projects/yegor256/takes/build/2856
++ jq -r .build.status
+ status=running
+ '[' running == null ']'
+ '[' running == success ']'
+ '[' running == failed ']'
+ echo 'waiting for AppVeyor build 2856: running'
waiting for AppVeyor build 2856: running
+ sleep 5s
+ true
++ curl -K ../curl-appveyor.cfg https://ci.appveyor.com/api/projects/yegor256/takes/build/2856
++ jq -r .build.status
+ status=running
+ '[' running == null ']'
+ '[' running == success ']'
+ '[' running == failed ']'
+ echo 'waiting for AppVeyor build 2856: running'
waiting for AppVeyor build 2856: running
+ sleep 5s
+ true
++ curl -K ../curl-appveyor.cfg https://ci.appveyor.com/api/projects/yegor256/takes/build/2856
++ jq -r .build.status
+ status=running
+ '[' running == null ']'
+ '[' running == success ']'
+ '[' running == failed ']'
+ echo 'waiting for AppVeyor build 2856: running'
waiting for AppVeyor build 2856: running
+ sleep 5s
+ true
++ curl -K ../curl-appveyor.cfg https://ci.appveyor.com/api/projects/yegor256/takes/build/2856
++ jq -r .build.status
+ status=failed
+ '[' failed == null ']'
+ '[' failed == success ']'
+ '[' failed == failed ']'
+ echo 'see https://ci.appveyor.com/project/yegor256/takes/build/2856'
see https://ci.appveyor.com/project/yegor256/takes/build/2856
+ exit 1
container 2003bd2643a90e5c943f12aca361194bccb4a38bd70a93705a83ea5712ae0b21 is dead
Mon Aug 21 13:52:50 CEST 2017

@rultor try to merge

@rultor try to merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor try to merge

@skapral @yegor256 Oops, I failed. You can see the full log here (spent 6min)
+ status=running
+ '[' running == null ']'
+ '[' running == success ']'
+ '[' running == failed ']'
+ echo 'waiting for AppVeyor build 2857: running'
waiting for AppVeyor build 2857: running
+ sleep 5s
+ true
++ curl -K ../curl-appveyor.cfg https://ci.appveyor.com/api/projects/yegor256/takes/build/2857
++ jq -r .build.status
+ status=running
+ '[' running == null ']'
+ '[' running == success ']'
+ '[' running == failed ']'
+ echo 'waiting for AppVeyor build 2857: running'
waiting for AppVeyor build 2857: running
+ sleep 5s
+ true
++ curl -K ../curl-appveyor.cfg https://ci.appveyor.com/api/projects/yegor256/takes/build/2857
++ jq -r .build.status
+ status=running
+ '[' running == null ']'
+ '[' running == success ']'
+ '[' running == failed ']'
+ echo 'waiting for AppVeyor build 2857: running'
waiting for AppVeyor build 2857: running
+ sleep 5s
+ true
++ curl -K ../curl-appveyor.cfg https://ci.appveyor.com/api/projects/yegor256/takes/build/2857
++ jq -r .build.status
+ status=running
+ '[' running == null ']'
+ '[' running == success ']'
+ '[' running == failed ']'
+ echo 'waiting for AppVeyor build 2857: running'
waiting for AppVeyor build 2857: running
+ sleep 5s
+ true
++ curl -K ../curl-appveyor.cfg https://ci.appveyor.com/api/projects/yegor256/takes/build/2857
++ jq -r .build.status
+ status=running
+ '[' running == null ']'
+ '[' running == success ']'
+ '[' running == failed ']'
+ echo 'waiting for AppVeyor build 2857: running'
waiting for AppVeyor build 2857: running
+ sleep 5s
+ true
++ curl -K ../curl-appveyor.cfg https://ci.appveyor.com/api/projects/yegor256/takes/build/2857
++ jq -r .build.status
+ status=failed
+ '[' failed == null ']'
+ '[' failed == success ']'
+ '[' failed == failed ']'
+ echo 'see https://ci.appveyor.com/project/yegor256/takes/build/2857'
see https://ci.appveyor.com/project/yegor256/takes/build/2857
+ exit 1
container a52927b776c6d80a8cf675853089a36c193f937ac9f7984fa48280bc67f87519 is dead
Mon Aug 21 17:37:32 CEST 2017

Codecov Report

Merging #745 into master will decrease coverage by 0.12%.
The diff coverage is 67.39%.

@@             Coverage Diff             @@
##             master    #745      +/-   ##
===========================================
- Coverage     76.72%   76.6%   -0.13%
+ Complexity      912     910       -2
===========================================
  Files           208     208
  Lines          4348    4372      +24
  Branches        330     334       +4
===========================================
+ Hits           3336    3349      +13
- Misses          881     893      +12
+ Partials        131     130       -1

Impacted Files
Coverage Δ
Complexity Δ

.../main/java/org/takes/facets/fork/FkHitRefresh.java
69.11% <67.39%> (-8.16%)
6 <2> (-2)

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 9448788...b1d75be. Read the comment docs.

@skapral looks like something is wrong in your branch

@yegor256 I know, coverage degrades. Moreover, I am against my solution myself, there is one null property and one mutable class. I'm surprised you tried to merge it actually.
I'll think about it later, idea with StickyScalar seems to be perspective.

The job #745 assigned to @t-izbassar/z, here is why. The budget is 30 minutes, see §4. Please, read §8 and §9. If the task is not clear, read this and this.

@0crat status

@0crat status (here)

@t-izbassar This is what I know about this job, as in §32:

The job #745 is in scope for 6mon
The role is DEV
The job is assigned to @t-izbassar/z for 27min
There is a monetary reward attached
@t-izbassar/z will get 50% of their hourly rate for this job
The job doesn't have any impediments
The budget is 30 minutes/points
These users are banned and won't be assigned:

@skapral/z: This user reported the ticket

@yegor256 this job should bi in role REV, not DEV. I don't think I should do anything about it. Also this PR is pretty old. @skapral any plans to finish it?

@0crat waiting

@0crat waiting (here)

@t-izbassar The impediment for #745 was registered successfully by @t-izbassar/z

@skapral any plans to finish it?
@t-izbassar This PR remained in work-in-progress state. I created it to check CI status. From that moment, I had no occasion to complete it.

The solution in this PR lacks two things:

Test coverage.
Eliminating null's

The problem and solution seems still actual for now, but I have no time to complete these two points and I am not sure if puzzles are OK here (since absense of null's is defined as key principle of the framework, probably @yegor256 will never pass it until they are eliminated). If puzzles are ok, then I can resolve the conflicts and complete this PR, but nothing more. Sorry.

@skapral no probs. I was thinking of storing only String, so that we don't need to create File instance in constructor. However, we still need the last instance. Moreover, in README.md itself the example uses constructor with String which is no longer present. I think it's just outdated.
However, this will break public API I don't know what maintainers will think about it. So, the other possible one is to bring Scalar to the codebase and leave puzzle to replace File instances with those scalars. Or, as you mentioned you can finish this solution. But, if you have no time, I think you can just close this pr. The #744 issue is now assigned to me so I would need to finish it anyway somehow.

@skapral if we get rid of NULL, this code may work.

@skapral ping

@skapral if we get rid of NULL, this code may work.

@t-izbassar @yegor256 ok, I resolved the conflicts and eliminated all nulls I personally introduced. One null, introduced before me, still remains (function directoryUpdated) but I consider it out of this issue's scope. Will place puzzle on that.

@yegor256 what should I do in this situation?
#744 assigned to me, however it is done by @skapral and he is not a member of Take afaik.
#745 also assigned to me, because the task has wrong scope. Should be REV and I don't have REV role.
If this PR is merged and issue closed, I will receive +60 points and monetary award. Maybe you want to reassign tasks.

@t-izbassar isn't it a cause for creating an issue to zerocrat? ;)

@t-izbassar isn't it a cause for creating an issue to zerocrat? ;)

@skapral yes, it is) it just could be clarified just in place. Will create one though, just to share experience with others, that might be in same situation.

@yegor256 ping

@0crat refuse

@0crat refuse (here)

@yegor256 The user @t-izbassar/z resigned from #745, please stop working

@rultor merge

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

The job #745 is now out of scope

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 16min)


Feature Request: Helm Charts Pre-loading for Air-Gap Support

The guide for installing the system charts in air-gap environments states that they must be hosted somewhere. Wouldn't it makes sense to be able to mount or copy this charts into a specific location in rancher?
Current:

In air-gap environments you must host your own charts using a git-repo which adds more complexity and prone to errors with instances that require user-auth with ssh-keys.

Expected:

Be able to run Rancher with an extra CLI flag that states to check for charts in a specific folder.
Rancher pre-loads all the charts found in that location.

Environment information

Rancher version: v2.2.1
Installation option (single install/HA): Single Install (air-gap)

Link to https://github.com/rancher/rancher/issues/17126

Tracking progress here

https://github.com/rancher/rancher/pull/21260

Closing as a dupe of #21260

I mean https://github.com/rancher/rancher/issues/20387


Add app version for GC Region Instance Group Manager

Signed-off-by: naiduarvind<EMAIL_ADDRESS>
Without the version attribute present, terraform plan was not working as expected when deploying Vault referencing this module for Consul. Having this attribute for Vault fixed it hence creating this PR to ensure consistency for Consul - being the dependency module.

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement
Learn more about why HashiCorp requires a CLA and what the CLA includes
Have you signed the CLA already but the status is still pending? Recheck it.

@josh-padnick @robmorgan - let's have this reviewed quickly and merged since it is quite simple a one-liner change.

@josh-padnick @robmorgan what is status on reviewing this pull request?

The nomad module has the same issue. PR outstanding and un-merged / unloved.

Any reason/blocker this hasn't been merged yet? Seems like a simple enough change that doesn't appear to brea anything else.

Closing this PR in favor of https://github.com/hashicorp/terraform-google-consul/pull/55. We are going to take advantage of TF 0.12 and no longer use the template_file workaround.


Suggestion: Using z-order to define layer for Mobjects.

Matplotlib has a very nice method to define in which layer objects are shown on the screen with a parameter zorder.

When working with manim, it's sometimes a little tricky to get the layers right, so what about an implementation, where you can write:
d=Dot()
self.add(d, zordner= 1)

Furthermore, there could be defaults like:

Dots at the first layer
Text & Equations at the second layer
Shapes on the third layer
Functions and graphs on the fourth layer.

When I posted this text to the discord server, @eulertour wrote:

I don't think it would require anything more than sorting scene.mobjects by z-index before rendering each frame
and since its already possible to assign arbitrary attributes to mobjects it may end up being a one-line change

Thank you.
So there is no way to do even static ordering in GL huh?
I am just getting into manim. Do most people use ManimCE (community) instead of ManimGL (3b1b)?


Add new secondary button

Description
Updating the secondary button styling.
To do

[x] add secondary button css
[ ] update button examples
[ ] update guidance
[ ] add CHANGELOG entry

I've removed some code that was changing the button padding (in comparison to the NHS design system button).
The differences were:

on mobile - top/bottom padding increases to 12px (from 8px)
on desktop - left/right padding increases to 32px (from 16px)

The default button left/right padding (16px) looks too small because of all the extra visual space on top of the label due to the cap/x-height.
20px looks best, but 24px also looks ok and uses the standard spacing units.
32px looks too big.

The default button left/right padding (16px) looks too small because of all the extra visual space on top of the label due to the cap/x-height.

I've set it to 24px for now, pending feedback

Vertical spacing comparison.
NHS design system = 8px padding (top & bottom)
NHS App design system = 12px padding (top & bottom)

Current guidance

Guidance needs updating to:

say that the secondary button is different to the NHS design system
reference the research

Also is the current usage guidance for secondary buttons correct?

NHS design system usage guidance:
Use a secondary button on pages that have more than 1 action or when users are not noticing standard link text.

Are there instances where you would use the secondary button as the only action?
Here's the gov guidance:

GOV.UK design system usage guidance:
Use secondary buttons for secondary calls to action on a page.

A question from Katy around secondary button usage:

We currently use Secondary button + Link assembly component to give users two distinct options. Our reasoning for using secondary and link rather than primary and link is that each CTA is equally weighted and one is not the natural next step over the other, which the green button may suggest. Is this logic used in other services or is primary button + link the default here?

cc @Graham-Pembrey

Draft addition to the secondary button usage guidance:

Our secondary button design differs from the NHS design system.
Use a secondary button either:

for secondary actions on a page
when an action needs less prominence – for example because it is optional

The second point would fit with cases where we might have reasons to use a secondary button as the only action on a page. It could also work in the scenario Katy described.
Draft addition to the research section of the guidance:

We designed the NHS App secondary button as an alternative to a secondary button with a grey background. This was because our research found some participants overlooked that design or believed it was a disabled button. In moderated usability testing, six out of six participants were able to use the NHS App secondary button for a variety of actions. Two participants had colour vision deficiency (colour blindness).

Suggested changes to the draft guidance above after further discussions with the team this morning. Additions are in code blocks:

We use a variation of the NHS design system secondary button. The "Research" section below has more details about why.
Use a secondary button either:

for secondary actions on a page
when an action needs less prominence – for example because it is optional

In the research section:

We designed the NHS App secondary button as an alternative to a secondary button with a grey background. This was because our research found some participants overlooked that design or believed it was a disabled button. Some participants hesitated before selecting the button. The visual hierarchy of primary and secondary buttons was also found to be unclear for people with monochromatic vision.
In moderated usability testing, six out of six participants were able to use the NHS App secondary button for a variety of actions and without hesitation. Two participants had colour vision deficiency (colour blindness).

Draft guidance - v2


Lots of CSP issues

Had to manually add the following to environments.js's contentSecurityPolicy to stop console errors:
script-src: http://platform.twitter.com https://cdn.syndication.twimg.com
img-src: https://pbs.twimg.com https://abs.twimg.com https://syndication.twitter.com http://platform.twitter.com data:;
style-src: http://platform.twitter.com

Sorry, I forgot to mention in the README that you can copy the CSPs from: https://github.com/aethermx/ember-cli-twitter-feed/blob/master/tests/dummy/config/environment.js#L46
Ideally the CSPs would be merged from an addon to the host app. For now, this is just a wish
https://github.com/rwjblue/ember-cli-content-security-policy/pull/20#issuecomment-118175209


Correct content offset for keyboard when uninverted

Scrolls up the chat when the keyboard shows when uninverted.

I'm glad I found this.  This fix is not in the cocoa pod.  But it is in the sample app. Which drove me nuts, trying to figure out what setting I needed to make it work for me.  I copied this fix to my version.  But can you add this to the cocoa pod, so others don't go through that, too?


Pull out non_tree_adjacency_lists_ into its own class

We want to support batch insertion and deletion into the lists that uses a hash table under the hood.
This will abstract away the complexity for doing the filtering by levels and resizing the hashtables if necessary inside.
The issue itself needs support from #12.

Resolved by #27


Fixed cookie setting, added support for MFA

Purpose

Changed the cookie policy in browser settings to allow 3rd party cookies. This blocked the log in and prompted the user to log in again right after logging in. This page  explains the error we ran into

Added optional otp token property to user info. Now, a step utilizing the XrmApp.OnlineLogin.Login method can be created to work with MFA. I also modified the login step to use this method

Approach
This approach solves MFA being enabled on the test user and also fixes repeated login popup
TODOs

[ ] Automated test coverage for new code
[x] Documentation updated (if required)
[x] Build and tests successful

Hi @metjuperry. Thanks for the pull request.
I'm sure you are already aware but for the first issue you can also set the cookieСontrolsMode in the power-apps-bindings-.yml file. However, I agree that it is sensible to default it to the correct value given that it simply doesn't work otherwise.
I'll try to get this merged and a new version published today.

Hi @metjuperry. Can you please update the configuration section of the README to cover the OTP token functionality?

Hello @ewingjm, thanks for the review. I added the otptoken property to the README

Thanks @metjuperry. This should be published to NuGet shortly.


Cleanups

This pulls in #7 and also:

Add build, install, test targets.
Add generation of testdata regular and cluster clientsets to codegen
target.
ci: add test job
getGoModPath: fix infinite recursion
Use updated logicalcluster package
Rename testdata -> examples, to verify our generated examples compile
Add missing register.go files

Also pulls in #9

@fabianvf @stevekuznetsov updated, PTAL


Fluent interface and relations

This is the quite the same request as 1f59001ff7de3dcd71d2e7497696220039beb413 but this one is for the "relations" method
This allow to use
$myObj->setSomeInt(1)
           ->addSomeEntity($otherObj)

We will make the entity generator much more flexible in the future with a complete rewrite, but until then this wont get into.

@beberlei the EntityGenerator already creates fluent setters for fields. It would be consisten to add if for relations

@beberlei, @stof is rigth, look at the commit I link, which was merged..
Actually, the generated entities are fluent for props ($foo->setBla(1)) but not for relations, which is not consistent.

There you go.


Tests.

Hey, I've set up a minimal example to test the tool with a simple R script, one input, one output (folder):
https://git.nfdi4plants.org/brilator/cwl_generator_test
Unfortunately, I'm running into an error. Which probably comes from naming the output twice: once as an input and once during the ? What is the name you want to assign to the output (e.g. results)?, which allows the option - If your output directory is specified under inputs: /$(inputs.NameOfTheInput).

Details and log in the repo's README.
I couldn't find Louisa and Adrian in the DataHub (registration -> https://register.nfdi4plants.org/registration).
Let me know if I can add you.

@Brilator You can add me now, I will take a look at it!

Okay, I think a good way to approach this is to first think about how the working output file would have to look like.
The first issue I found was that we are supplying the "calculate_means.R" script to the base command but CWL cannot find it because it does not exist in the CWL environment.
There are 2 Possible solutions for this:

Supply"calculate_means.R" as a file input

- id: r_script
  type: File
  inputBinding:
    position: 0

Stage the file to the input directory using an InitialWorkDirRequirement

- class: InitialWorkDirRequirement
  listing:
    - class: File
      location: calculate_means.R

Regarding CWLGenerator, the first option would be the simplest and would not require any changes.
The second issue is that we are supplying out_folder as a Directory. This means we cannot access it in glob without doing any extra-work (staging the directory). Instead, we would have to use outputEval
outputs:
- id: outdir
  type: Directory
  outputBinding:
    outputEval: $(inputs.out_folder)

But this does not feel very idiomatic, since it will place the files in the specified directory and not create a separate output folder. So I would sugest against this.
It would be simpler if we specified the output as a string. If we do however, we need to make sure that the R script creates the directory before writing to it. Alternatively we could create an InitialWorkDirRequirement that creates the folder for us.
Again, I would suggest going with option a) because this would require another edge case for the CWLGenerator which would make the questioning even more confusing (suggestions welcome).
So for me, the "perfect" output file would look like this:
#!/usr/bin/env cwl-runner
cwlVersion: v1.2.0-dev1
class: CommandLineTool
inputs:
- id: r_script
  type: File
  inputBinding:
    position: 0
- id: in_file
  type: File
  inputBinding:
    position: 1
- id: out_folder
  type: string
  inputBinding:
    position: 2

outputs:
- id: outdir
  type: Directory
  outputBinding:
    glob: $(inputs.out_folder)

baseCommand:
- Rscript

The Job file for this would be:
r_script:
  class: File
  location: ./calculate_means.R
in_file:
  class: File
  location: input/expression_table.txt
out_folder: ./output

The "perfect" output should already be achievable with CWLGenerator in the current state (We do have to improve the question phrases though).
PS: I think there is an error in the R script on line 42:
write.table(dfr, file = paste0(out_folder, "expression_withMeans.txt"), row.names=F, sep="\t", quote=F)
should be:
write.table(dfr, file = paste0(out_folder, "/expression_withMeans.txt"), row.names=F, sep="\t", quote=F)
(I added a "/" before expression_withMeans" because directories usually don't end with a "/")
Sorry for the wall of text. Let me know if anything is not clear!

Actually, we do have one bug here!
Pressing Enter on What is the command prefix for your input (e.g. -t). Press Enter if there is none.  Should not yield prefix: "" in the inputBinding  but instead yield nothing.

should be:
write.table(dfr, file = paste0(out_folder, "/expression_withMeans.txt"), row.names=F, sep="\t", quote=F)
(I added a "/" before "expression_withMeans" because directories usually don't end with a "/")

Well, I defined the out_folder as output/. But you're right, your way is safer.

Actually, we do have one bug here!
Pressing Enter on
What is the command prefix for your input (e.g. -t). Press Enter if there is none.
Should not yield prefix: "" in the inputBinding  but instead yield nothing.

Is this the reason it would still fail with your above "protocol"?

Ah, sorry never mind. It did work after pulling your latest version.

Awesome!


Update remove-former-employee.md

Correct navigation to Initiate Sign-out and added a note that only GA can do this.

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/2203

@JohanFreelancer9  Please copy review

@KwekuA Please Merge this PR. Thanks.

@kwekuako Please merge this PR. Thanks


Provide Docker image for agents deployment

Today, we deliver agents as binary and it is not easy to know which distribution to select.
The goal is to deliver agents as Docker image that can be run from any Docker environment.

Closing as dockerfiles are now provided


Add oanda-rest-api

I've had this package for a while, but only recently have all the dependencies been added to stackage (particularly thyme).

Sweet, thanks!


[docs] 404 on MUI X Components

Related page
https://v5.mui.com/x/react-tree-view/
Kind of issue
Other
Issue description
Steps to reproduce
Attempt to navigate to the following components via the https://v5.mui.com NavMenu:

Date & Time Pickers
Charts
Tree View

Expected Result
Navigating to these URLs takes you to the respective pages
Actual Result
You are presented with a 404 page:

Context
No response
Search keywords: 404, docs, MUI X

Hey @YenHub, thanks for reaching out.
MUI X and Material UI components do not share the same major number, so I recommend referring to mui.com for X components. You should be able to use MUI X v7 with Material UI v5. We are aware this might be confusing and we are looking into potentially syncing the versions in the future.

Hey @YenHub, thanks for reaching out.
MUI X and Material UI components do not share the same major number, so I recommend referring to mui.com for X components. You should be able to use MUI X v7 with Material UI v5. We are aware this might be confusing and we are looking into potentially syncing the versions in the future.

Perhaps the navigation links in the UI should point to an absolute URL, instead of the v5 subdomain.
Are the docs part of the main mui codebase? I would be glad to contribute to the fix.


Updating the Raspberry Pi version

The Raspberry Pi ARM version hasn't been merged with the master for a while now.
Is there a specific reason for that, or was something changed that is not supported by the ARM architecture?

It become different some time ago, and now it's a bit hard to maintain both on sync.
I have in mind to move both versions to master in a near future and use same codebase in both images. As the base image don't change frequently (the main changes are on additional scripts) it should be good.

@brighthero It has been updated today.
Now there are two different Dockerfiles on the master branch, and both images are synced.
Also, an updated image has been pushed to the registry: https://hub.docker.com/r/odarriba/timemachine-rpi/


E2E Tests for Dappkit in Valora

Closing this because DappKit is deprecated. #8259 is tracking DappKit deprecation work.


Open ?

We can not modify anything, not really open.

What would you like to modify? You are welcome to submit a pull request.

@gameinskysky That's not how open source works.... open source means that the source is available under a license that allows you to modify anything and publish your modifications, not that you can modify anything in the main version of the code.
Here's a link to the license. It's pretty much a standard MIT license.
https://github.com/commaai/openpilot/blob/master/LICENSE.openpilot
Or, for a summary, may not be completely accurate:
https://tldrlegal.com/license/mit-license
If you click ![Fork button][http://bsite.cc/iLDC/Screen Shot 2016-12-05 at 9.38.16 AM.png] (next the top right corner of the site), you're able to create a copy of this project that you can modify. Then, you can submit a pull request requesting that @mgraczyk (or another collaborator) accepts your changes.


change logo text to path

Converted the text in the logo to a path, to avoid rendering problems when the proper font is not available.
I left the original text in a hidden layer, just for the sake of recording the original font (Gurmukhi MN, which is of the same family used in the julia logo). I hope this hidden layer doesn't interfere with anything. If it does, we just remove it.
This should close #7

I see the new SVG logo as follows

which looks correct, thanks!


Overflows

During testing of the correlations feature, I've noticed a bunch of distributions which casually produce overflows. Users wouldn't notice this except for infinities (np.inf) in their samples or distribution parameters.
I've fixed some of these (mostly those related to input parameters) alongside the distributions feature, but some that are still a problem:

LognormalDistribution:

Outcome: Infinities in distribution parameters.
To replicate: sq.lognorm(1,1e+26)
Location: https://github.com/rethinkpriorities/squigglepy/blob/9491e508a7704c3b09f8101208e8673012a42d4e/squigglepy/distributions.py#L773-L775

LogTDistribution:

Outcome: Infinities in samples.
To replicate: np.any(sq.log_t_sample(1.0, 2.0, 1, 100_000, 90) == np.inf)
Location: https://github.com/rethinkpriorities/squigglepy/blob/9491e508a7704c3b09f8101208e8673012a42d4e/squigglepy/samplers.py#L216-L218

I think it would be hard to fix this, most of these errors come from limitations inherent of the floating point operations; but I would at least try to reraise the warning as an error, to prevent users from creating models which might be silently wrong.

Yeah my guess is that this occurs in underlying numpy right?
Hm yeah this seems pretty annoying. I imagine the user also wouldn't be excited for their programs to randomly crash with an error, though I imagine that is better than having unnoticed infinities. Resampling would also be complicated.

[ ] > Hm yeah this seems pretty annoying. I imagine the user also wouldn't be excited for their programs to randomly crash with an error, though I imagine that is better than having unnoticed infinities. Resampling would also be complicated. I suppose rclip could be helpful here?

In some specific cases we can work around overflow and underflows by limiting calculations to a minimum or a maximum, but it's tough to estimate how they would impact the distributions.
For now I much prefer to raise an error unless there's an obvious fix (like bounding the parameters).


[fpv/prim_packer] Add a FPV TB

Made a Formal Testbench for prim_packer, to make the tb converge, we
constraint the input data size from 2 bits to 16 bits.
Signed-off-by: Cindy Chen<EMAIL_ADDRESS>

I think it is good to have  a FPV test that can run arbitrary input & output widths. Clearly it may need 32bit input and 64 bit output later . I am expecting the prim_packer to be operable in any bit range from 1bit input.

@eunchan thanks for the input. I will make a FPV TB for arbitrary input and output widths.


Ts/3433 speed quality button

Description

Simulation presets.

Resolves #(issue)

IMO the labels should maybe be debug and preset -Debug as it should only be used for this -Preset as a generic wording What "Normal" means can vary :P But this is more of a design thing than anything and a super minor change in future if we want

Yep this is the issue here, we have fast/debug and not fast/debug ... so there is really only one preset but we are modelling it as two.


feat(storage): implement suffix and prefix OLM rules

GCS is adding additional Object Lifecycle Management rules. This PR
introduces support for the rules in REST and gRPC.
Part of the work for #8968

This change is

/FYI @shaffeeullah


ADD BUTTON

This is a(n):

[ ] Update to an existing Animated Button
[ ] Any Error
[x] Proposal to the Repository
[ ] Documentation / README.md changes

Details:
Add Button with a animation to add various type of files.
Assign me this under GSSoC'23
https://github.com/Spyware007/Animating-Buttons/assets/111378171/ddfcf1f8-c0a3-4af9-b24f-7f6db489a613

@Killer2OP Assigned to you!


Menu Driven Code to implement stack

Description
A menu driven program in C to perform the following operations using stack:
Create(); Push(); Pop(); Traverse()
Domain
C/CPP
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign

Closing this issue as the PR got merged !! Open new issues !


[docs] Fix typo on laravel quickstart [skip ci][ci skip]

The Problem/Issue/Bug:
Just a minor file name correction in the laravel doc.

Thanks for this!


Asynchronous usage

I'm aware of the discussion in the open PR #6, this ticket is here to have the discussion without referring to a specific implementation.
One thing you mention is that using coroutines is not a preferred solution, could you elaborate on why not?
Coroutines have low overhead (similar to function calls), and are easy to implement.
I have created a proof of concept PR for LibSerialize that shows how it can be done transparently for the calling code. (https://github.com/rossnichols/LibSerialize/pull/7)
The idea is that the library yields at given byte intervals when it detects it is running inside a coroutine.

It could be solved by WA, by splitting communications into chunks.
You could ask WA to patch LibDeflate with coroutine, shouldn't be very hard.
I do not like coroutine. It should be implemented by streaming interface, APIs similar to zlib
I am not actively maintaining this library. Mostly because I do not play this game any more.
Maybe it's time to setup my IDE for this tiny project and start to work on it again?

I know you don't like coroutines, can you elaborate on why? I'm curious!

Ok. I may allow the user to pass in a hook function.
LibDeflate will call it in the middle of compression or decompression.
LibDeflate does not care what the hook function does.
The hook function can call coroutine.yield(), for example

Can someone explain the issues people are having with coroutines to me?

Can someone explain the issues people are having with coroutines to me?

Coroutines add a lot of complexity and risk breaking invariants in-place throughout a lot of code.
The first - and most critical - issue with respect to coroutines is that they're stackful. A thread can be suspended at any point within any nested stack frame. Within the WoW environment we're on Lua 5.1 which isn't a fully resumable VM and as such you can't actually yield across a few boundaries.

You can't yield across any stack frame above yours that belongs to a C function.
You can't yield from within the iterator y of a for x in y loop.
You can't yield from within the implementation of any metamethod on a table.

The problem is you can't actually reasonably guarantee that none of these invariants aren't actually broken at runtime, either by another loaded addon being present or you making seemingly-innocuous changes elsewhere in your own code. Something as simple as using pcall to capture errors or a secure hook being present on any function in the stack frame above where you're yielding from would break the first invariant for example, as the implementation of those involves a trip through C and back into Lua.
Further, most Lua code is assumed to only ever be called from a single-thread which leads to decisions that are made - either knowingly or accidentally - that prevent re-entrancy.
A simple example would be a function that, to conserve memory, reuses a table stored in an upvalue for processing and polls a user-supplied function to provide some data (such as an iterator). If this iterator recursively executed the function, you'd typically blow up spectacularly then and there with a stack overflow error which makes it extremely obvious and easily fixed. If the iterator yields and another separate thread takes a trip into this function, you've got a subtle bug that's much harder to detect.
This isn't to say that coroutines don't solve problems, but it's generally more reliable to use them in a stackless - or at least near-stackless - manner and to try not go all-in with them, or in the case of libraries, "force" them onto the user.
With respect to LibDeflate (and LibSerialize), an iterative streaming API as mentioned would be the best solution from a least-astonishment perspective. Such an API wouldn't force the use of coroutines with all their complexities and risks on the caller, but also doesn't prevent the caller from processing the stream within a coroutine if they so choose.

Thanks! That's a very interesting read!

I will provide a feature for hook function.
User can use coroutine.yield inside the hook function.
coroutine API will not be used directly in libdeflate


Add Harmony ONE as a custom network - fully EVM compatible

name: adding Harmony ONE as a custom network
about: https://docs.harmony.one/home/network/wallets/browser-extensions-wallets/metamask-wallet
Network Name
Harmony Mainnet
New RPC URL
https://api.harmony.one
Chain ID
(use number only)
Shard 0:<PHONE_NUMBER>
Currency symbol (optional)
ONE
Block Explorer URL (optional)
https://explorer.harmony.one/#/

our logos in svg: https://drive.google.com/drive/u/0/folders/1Y0r5KvRygXNZvLBDTIJTCElEi_ellMsG?ths=true

@ChintanRathod you can push the logo into the iconassets repo. You shouldn't need to use a PR, just commit direct to master; let me know if it doesn't work.

@JamesSmartCell Ok.

Actually, no you can't add it there --- it's a chain, as you pointed out!

It should be a lot easier to add chains now, much less needs to be changed

@JamesSmartCell note that I asked for some clarifications here: https://github.com/AlphaWallet/alpha-wallet-ios/issues/2722

@JamesSmartCell What should we do with this ticket? Is it needed to work on or we can close?

If you can help figure out https://github.com/AlphaWallet/alpha-wallet-ios/issues/2722#issuecomment-841615037, we can proceed :)


User model

To keep the code simple, we could consider to replace devise with a simple user model: http://ruby.railstutorial.org/chapters/modeling-and-viewing-users-one#top
The goal is to have minimal code and dependencies for the core use cases.
We need to discuss this.

I'm not sure. Both methods have their merits. Other resources say that you should never roll your own authentication system.
Some pros for Devise:

We've already built the first portal with it
Devise makes it easier to add OAuth or OpenID support later
Current user management and profile administration is so simple, it's ridiculous :)
Using a framework makes us use less code after all

agreed. let's close this issue and reopen it when necessary.


Keepalive connection to Sentinel

Currently we are setting up a cluster of 120 Redis nodes and 20 nodes of Sentinel.  Everything seems to be working fine except periodically we see the following message:
[ioredis] Unhandled error event: Error: All sentinels are unreachable. Retrying from scratch after 10ms
After some digging, we noticed the connections to Redis are "long-lived", but the connections to Sentinel are on-demand. We see there are times many (or all) of the clients running ioredis simultaneously trying to connect to Sentinel, unfortunately Sentinel is hard coded to have 511 backlog queue. As a result, the system think there is a SYN flood.
Can ioredis use "long live" connection to Sentinel instead of on-demand?

Hi, it seems that the default backlog can be changed at https://github.com/antirez/redis/blob/94658303e9ec5050189728fb8bc514ee682dd5fe/redis.conf#L101.

Redis instances can be, but Sentinels can not. The flood we experienced was with Sentinels.

Not sure but I thought sentinels and typical redis servers share the same code according to the backlog part.
Keeping a long live connection to sentinels is possible but is not trivial to implement. We'll think about that.

Hi, although it's not in the document, but after reading your post, we decided to to create the setting for Sentinel, and it worked. Thanks! We will monitor and see if this address the connection issue we had.
If long live connection to sentinels is not trivial to implement, how about subscribe to Sentinel to receive any changes.

@jfjm could you expand a bit on how you did that? It might be useful for my project as well.

Add the following to your sentinel.conf:
tcp-backlog


[Docs]: React- State

A State doc already exists for this project's doc book, but is currently an empty place holder until its contents are filled in.
This doc should be updated to include all things state related for react. Including things like:

What is component state?
Why is managing state important?
Why you can't and shouldn't directly mutate state?
How to set initial state
How to update a component's state
How to update a component's state on an event action (preferably with code example)
How re-rendering works when state changes

I'll take this one


Fix copy of the URL in RemoteName

Fixes #1040
The copy performed in RemoteName was shallow and this corrupted the original URI that is used during the Dial() call made by the go-libvirt library.
The issue always existed but did not manifest when libvirt.New(conn) was used because the connection was established before the call to RemoteName. The problem manifested when the switch to libvirt.NewWithDialer was made, because the dialing is now made during the call to ConnectToURI, which receives as paramater the result of the call to RemoteName.
Please make sure you read the contributor documentation before opening a Pull Request.

Thanks @X-Cli!


Self Registration is failing and Go Back button prompted during self registration navigates to a form resubmission error page when customizable login portal changes configured

How to reproduce:

Get pack https://wso2.org/jenkins/view/products/job/products/job/product-is/org.wso2.is$wso2is/4201/
Set up cusomizable login portal feature https://docs.google.com/document/d/1_XUbmrokb1Yy7T1eZ8wpiq5i3eKwxEXxrwbBmX5xC4Q/edit
Enable self registration from management console account management
Set up travelocity as the SP and the sample
Access http://localhost:8080/travelocity.com/home.jsp
Click on Create Account
Try to self register by filling mandotory fields
Will navigate to a error page
Click on the Go Back button in the error page
Will get the below error page where form resubmission is failing

Attaching a recording
https://user-images.githubusercontent.com/31848014/182778082-743ef511-fe52-4b9f-a1b5-9f9293851cb6.mp4
Expected behavior:

Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: [e.g., IS 5.10.0, IS 5.9.0]
OS: [e.g., Windows, Linux, Mac]
Database: [e.g., MySQL, H2]
Userstore: [e.g., LDAP, JDBC]

Optional Fields
Related issues:

Suggested labels:

As per Dilshan this issue can be reproduced without the customizable login portal changes too. Hence removing customizable login portal label

After analyzing the issue, I found that this issue persist in both IS 6.0.0 Beta and IS 6.0.0 Alpha3. But IS 6.0.0 Alpha2 haven't this issue. Followings are the identity-apps version used in each release.

IS 6.0.0 Beta - v1.3.26
IS 6.0.0 Alpha3 - v1.3.6
IS 6.0.0 Alpha2 - v1.2.1014

According to my analysis this error occurs form the identity-apps v1.2.1026.

To verify that I configured the IS v6.0.0 alpha2 and pacth the identity-apps v1.2.1025. Then the issue was not there.
After I configured IS v6.0.0 alpha2 and pacth the identity-apps v1.2.1026. Then the issue was found.

I think the root cause for the issue is these changes - https://github.com/wso2/identity-apps/commit/b01d521dc4046001073bb074f6890d2f1b92790a

To fix this issue from UI level, change the callback regex pattern of self registration


Jwt Auth with Angular Auth0 and AspNetCore No 'Access-Control-Allow-Origin' header is present on the requested resource

I'm getting the following error on my WebAPI requests:
XMLHttpRequest cannot load https://localhost:44351/api/values/. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:4200' is therefore not allowed access. The response had HTTP status code 500.

Note that auth & logging in works ok on the angular 2 app (as desribed by the auth0 team).

Note that without AUTH attribute the ValuesController works just fine

I inspected the response from ASP.Net Core and saw that there was indeed no 'Access-Control-Allow-Origin' header. Do I need to add anything else to the pipeline, if so what/how/different order?

HEADER INFO
Request URL:https://localhost:44351/api/values/1/
Request Method:GET
Status Code:500 Internal Server Error
Remote Address:[::1]:44351
Referrer Policy:no-referrer-when-downgrade

Response Headers
Content-Length:0
Date:Mon, 17 Jul 2017 22:19:51 GMT
Server:Kestrel
X-Powered-By:ASP.NET
X-SourceFiles:=?UTF-8?B?RTpcU29sbGljaXRhdGllYmVoZWVyXFNvdXJjZVxCYWNrZW5kXEFwaVxTb2xsaWNpdGF0aWViZWhlZXIuQmFja2VuZC5BcGlcYXBpXHZhbHVlc1wxXA==?=

Request Headers
view source
Accept:application/json, text/plain, */*
Accept-Encoding:gzip, deflate, br
Accept-Language:en-GB,en-US;q=0.8,en;q=0.6
Authorization:Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiIsImtpZCI6Ik56RTFSRE5ETVRCQk9FUTRSRFpEUXpZMU9FWTNRVGxFTVVJNU5qSTROa0U1TkRKQlFUbEZNdyJ9.eyJpc3MiOiJodHRwczovL2xlcmVuYXJkLmV1LmF1dGgwLmNvbS8iLCJzdWIiOiJhdXRoMHw1OTZkMjkzMjYxNzc3YzE4YWY2ZjUyOWUiLCJhdWQiOlsiaHR0cDovL1NvbGxpY2l0YXRpZWJlaGVlckFQSSIsImh0dHBzOi8vbGVyZW5hcmQuZXUuYXV0aDAuY29tL3VzZXJpbmZvIl0sImF6cCI6Ii01M2l5UUNnMzlkYkNHUjdWT0dmRTRKRnFCaVI2bzFHIiwiZXhwIjoxNTAwMzM2OTgyLCJpYXQiOjE1MDAzMjk3ODIsInNjb3BlIjoib3BlbmlkIHByb2ZpbGUifQ.j1BULIZ3TWTRD40sIQ8I1EngQNVreGg-4pOyqoQU3cKKPcHS4OBle_4pJBmXtYG2Eb7woJbABO2-5arKWZmByN11hOaBRTMCj24u-kqdyAPeBXGFBWcCEQ3sCXSpIxpC3S3FfsYELbEZX_8E0-rk9oqyjqlCk4UOd2NXeBuhtHt_rvbQ8SXUlNxnj3WjPri0unWW9yK2tDizc9bsOVl1hGb7e6qav8haD4chIUOuoydaczUAe9sqFUVKZU318snZmM-R_bmEn1n_QB4m4kbAwrKTQlt2tenTiEKKwmpj5aU4rWSGwwnLcw1aj81aRs0mlT0IbuczaH7JHf1y1aAoxw
Connection:keep-alive
Content-Type:application/json
Host:localhost:44351
Origin:http://localhost:4200
Referer:http://localhost:4200/ping
User-Agent:Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

This is my WebAPI setup:
Startup.cs
public class Startup
{
    // This method gets called by the runtime. Use this method to add services to the container.
    public void ConfigureServices(IServiceCollection services)
    {
        services.AddJwtBearerAuthentication(o =>
        {
            o.Audience = "http://***********";
            o.Authority = "https://********.eu.auth0.com/";
        });
        services.AddCors();
        services.AddMvc();

    }

    // This method gets called by the runtime. Use this method to configure the HTTP request pipeline.
    public void Configure(IApplicationBuilder app, IHostingEnvironment env)
    {
        app.UseCors(policy => policy
            .AllowAnyOrigin()
            .AllowAnyHeader()
            .AllowAnyMethod()
            .AllowCredentials()
        );
        app.UseAuthentication();
        app.UseMvc();
    }
}

ValuesController
[Authorize]
[Route("api/[controller]")]
public class ValuesController : Controller
{
    // GET api/values
    [HttpGet]
    public IEnumerable<string> Get()
    {
        return new string[] { "value1", "value2" };
    }

    // GET api/values/5
    [HttpGet("{id}")]
    public string Get(int id)
    {
        return "value";
    }

    // POST api/values
    [HttpPost]
    public void Post([FromBody]string value)
    {
        // For more information on protecting this API from Cross Site Request Forgery (CSRF) attacks, see https://go.microsoft.com/fwlink/?LinkID=717803
    }

    // PUT api/values/5
    [HttpPut("{id}")]
    public void Put(int id, [FromBody]string value)
    {
        // For more information on protecting this API from Cross Site Request Forgery (CSRF) attacks, see https://go.microsoft.com/fwlink/?LinkID=717803
    }

    // DELETE api/values/5
    [HttpDelete("{id}")]
    public void Delete(int id)
    {
        // For more information on protecting this API from Cross Site Request Forgery (CSRF) attacks, see https://go.microsoft.com/fwlink/?LinkID=717803
    }
}

This is the angular 2 app:
ping.component.ts (as provided by auth0 as example)
import { Component, OnInit } from '@angular/core';
import { AuthHttp } from 'angular2-jwt';
import { Http } from '@angular/http';
import { AuthService } from './../auth/auth.service';
import 'rxjs/add/operator/map';

@Component({
  selector: 'app-ping',
  templateUrl: './ping.component.html',
  styleUrls: ['./ping.component.css']
})
export class PingComponent implements OnInit {

  API_URL = 'https://localhost:44351/api';
  message: string;

  constructor(public auth: AuthService, public http: Http, public authHttp: AuthHttp) { }

  ngOnInit() {
  }

  public values(): void {
    this.message = '';
    this.http.get(`${this.API_URL}/values/`)
      .map(res => res.json())
      .subscribe(
      data => this.message = data.message,
      error => this.message = error
      );
  }

  public valuesByNumber(id: number): void {
    this.message = '';
    this.authHttp.get(`${this.API_URL}/values/${id}/`)
      .map(res => res.json())
      .subscribe(
      data => this.message = data.message,
      error => this.message = error
      );
  }
}

@jbagga - can you investigate?

@aredfox Which version of ASP.NET Core are you using?

Unable to repro with the given information. Can you share a functioning app with this issue? The only thing I can think of is that you are not being authorized to access the ValuesController, maybe because your log-in redirection is not set up as expected.

@aredfox I am unable to repro this in 1.1 and 2.0. Can you share a sample app that is running in to this issue? Here is the CORS sample I used (the SampleOrigin) to ping an API that has Jwt auth set up

Status Code:500 Internal Server Error

Do you have logging turned on? This looks like a run of the mill exception is coming from somewhere.

@aredfox Are you able to share what may be the cause of the 500?
Closing this for now as it cannot be reproduced. Please feel free to reopen and provide more details.


Update README.md

Details
I've changed the saample implementation about Delegate.
Related Issue

Motivation and Context
I think the source does not have MagazineLayoutSupplementaryViewVisibilityMode type.
So, if someone copies the sample code and pastes, it can't compile.

How Has This Been Tested

Types of changes

[x] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.

Sorry,
I think the source does not have MagazineLayoutSupplementaryViewVisibilityMode type.
So, if someone copies the sample code and pastes, it can't compile.

Ah, I see the problem @muukii ! Can you update it so that the footer delegate is included too? Looks like this PR removes that.

@muukii if you'd still like to get this merged, can you make the requested changes and push? I can review again then.


drag and drop to invalid location

Testing #196195
I think this should be a no-op 🤔
https://github.com/microsoft/vscode/assets/29464607/75a3721f-5537-4635-a88e-fdeaf44e7b80

here's what happens when I try this with an editor

I can only speak to editors: we have a data transfer to allow for dragging an editor into another application to have its path pasted (works for example in ST). I assume the browser simply does not allow to open a local file on drop, but I would not remove this feature.
For terminals, leaving up to Daniel.


What Should One Do (Manually) To The Output of Retdec To Make It Compilable?

Related to #529, #562, #45, but not exactly a duplicate. Also, this is still relevant even when Retdec’s aim is not so much to produce code that can be decompiled as much as to produce code analysable by a human. It is still relevant to someone just trying to analyse the output of Retdec without re-compiling it.
Given the output files of Retdec, what should one do (manually) to make it compilable?
Eg:
(1) Is the output standard C, or just C-like?
(2) If it’s standard C, why is still not recompilable? Because of unresolvable references etc.
There’s some discussion in #45, but there’s no step-by-step instruction or tutorial (with samples etc.) like what should one change in the output files, and which libraries must one link to again. Wish there’s a tutorial or some sort. This will make it very clear what in the output files of Retdec are missing and different from compilable code, and one needs to know this to understand the code even if one doesn’t wish to recompile it per se.

Any suggestions?

Hi. I will try to provide answers to your questions. @PeterMatula can supply additional information in case I miss something.
As for question number (1), we strive to produce output that conforms to ISO C99. So yes, the output should be C, not just C-like. However, things are not that simple, see below.
As for question number (2), there are generally two reasons why the generated C code is not re-compilable:

Things that can be solved by fixing/improving RetDec.

Adding support for unsupported instructions. When RetDec encounters an instruction that it does not know how to lift to a higher-level representation, it emits an __asm_XYZ function call, where XYZ is the name of the instruction. Example:int128_t d = __asm_addsd(__asm_divsd(a, b), c);

This can be fixed by adding support for these instructions. However, this may not always be possible/desirable, as instructions may be unrepresentable (or hard to represent) in a high-level form. Such instructions may include standard architecture extensions (MMX, SSE, etc.) as well as platform-dependent extensions (e.g. instructions for a specific device, such as PlayStation).
Fixing reconstruction of types. Sometimes, it may happen that RetDec reconstructs incorrect types, which results in compiler errors. Example:struct X {
    int i;
};

void foo(struct X x);

foo(1);

Fixing reconstruction of functions. Sometimes, it may happen that RetDec emits incorrect function bodies, such as with missing goto labels, duplicate goto labels, or use of undeclared variables. Example:void foo() {
    // ...
    generated_label:
        // ...
    // ...
        generated_label:
        // ...
    // ...
}

Things that cannot be solved by fixing/improving RetDec.

Having signatures for detecting all statically linked code that should not be decompiled. Such code includes compiler runtime (before main()) and functions from the standard library (e.g. printf()). When re-compiling the code, these functions are inserted into the binary file automatically by the compiler, and if there are decompiled, the compiler will refuse to compile the code. The biggest issue with this point is that there is a huge number of different compilers and standard libraries and RetDec cannot cover them all (this would make it really huge and slow). Thus, users are encouraged to generate such signatures by themselves.
Unresolved references. The decompiled code may contain references to functions that are not present in the code. In such cases, you have to provide them by yourself when compiling (to provide their declaration) and linking (to provide their definition). RetDec in general has no way of knowing which header files and libraries should be used when compiling and linking the decompiled file.

As for this point:

There’s some discussion in #45, but there’s no step-by-step instruction or tutorial (with samples etc.) like what should one change in the output files, and which libraries must one link to again.

I am afraid there won't be any such tutorial as there is a huge variety of different errors that could go wrong. However, I have been wrong before, so maybe someone actually writes it (it won't be us, though). The best instructions we can give you at the moment are:

Try to compile the generated C source code.
Take a look at the first error, understand what it says, and fix it in the source code (or in the compilation command, e.g. by providing libraries containing unresolved dependencies).
Repeat steps 1 and 2 until the code compiles without any errors.

We are aware that this might not be what you are looking for, but it is the best we can give you at the moment.

Your answer's very helpful so far @s3rvac. Even though as you said "this might not be what [I am] looking for", it's a good start, and at least I can use it as a starting point. thank you very much! I will read the publications to fill in the gaps, and if there's anything else I will post again.

My two cents:

Don't try to re-compile RetDec's output.
Don't try to manually modify and re-compile RetDec's output.

Currently, we are not producing output of sufficient quality to gain anything from compiling it. I doubt this will get better in the future. Decompilation is hard and the way we do things, it is pretty much impossible to decompile a binary of some complexity into something that you could re-compile (even with manual modifications) and expect to work. This project is focused on manual analysis of the output and it is likely we will add more features that goes in this direction in the future (e.g. calling conventions, x86 FPU/SSE intrinsics).


Script fails when image URLs have the same suffix

I tend to share images publicy on my nextcloud. They get their own preview webpage on links like
https://nextcloud/s/xj3DQpSJXgzsA2x
and can be downloaded/inserted into markdown files by appending '/preview'
https://nextcloud/s/xj3DQpSJXgzsA2x/preview
Unfortunately markdown_images_downloader will download all images as preview.ext, overwriting the same file again and again.

Fixed.

That's a nice solution, learned something for my own programming skills. Thanks a lot!


minor changes

This PR includes minor changes in order to make the code base cleaner and easier to read and follow.

This is great, thanks!


PERF-#0000: dask: return node address only if requested

What do these changes do?

I see 4x speedup for the following code (Dask, 8 cores). This problem is only for Dask, for Unidist and Ray the difference is practically unnoticeable. @YarShev @dchigarev
import modin.pandas as pd
import numpy as np
from time import time

n_features = 6000
n_samples = 6000

if __name__ == '__main__':
    df = pd.DataFrame(np.random.rand(n_samples, n_features))

    start = time()
    for _ in range(10):
        df.round(2)
    print(f"10x round calls time: {time()-start}")

[x] first commit message and PR title follow format outlined here

NOTE:  If you edit the PR title to match this format, you need to add another commit (even if it's empty) or amend your last commit for the CI job that checks the PR title to pick up the new PR title.

[ ] passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
[ ] passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
[ ] signed commit with git commit -s
[ ] Resolves #?
[ ] tests added and passing
[ ] module layout described at docs/development/architecture.rst is up-to-date

Looks like returning multiple values from a kernel in Dask is quite inefficient


splunk add-on documentation

Status
Ready
Related Issues
fixes: https://github.com/demisto/etc/issues/29616
Description
splunk add-on documentation

Looks like you have invalid image urls:

@kirbles19 please review

@dantavori Done


feat: Added Tooltip for icon button widget

Description

Added tooltip for an icon button widget

Fixes #13807
Type of change

New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented on my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:red_circle: Total coverage has decreased
// Code coverage diff between base branch:release and head branch: feature/issue-13807

Status
File
% Stmts
% Branch
% Funcs
% Lines

:red_circle:
total
56.71 (0)
38.65 (-0.01)
36.22 (0)
56.96 (0)

:red_circle:
app/client/src/selectors/commentsSelectors.ts
83.61 (-1.64)
61.76 (-2.95)
73.33 (0)
88.24 (-2.35)

:red_circle:
app/client/src/utils/WorkerUtil.ts
88.98 (-0.78)
68.63 (-1.96)
100 (0)
92.38 (-0.95)

:green_circle:
app/client/src/widgets/IconButtonWidget/component/index.tsx
29.41 (6.15)
14.81 (6.48)
0 (0)
44.12 (7.08)

:red_circle:
app/client/src/widgets/IconButtonWidget/widget/index.tsx
52.94 (-1.61)
0 (0)
66.67 (0)
53.13 (-1.71)

/ok-to-test sha=9ffc461

Tested this PR and working as expected


List bug without the meta keyword with [meta] in the title (with auto…

…fix)

Coverage decreased (-0.5%) to 40.249% when pulling da844cf78e8f73ec5f71217590940611d36b958e on sylvestre:master into 8a3e0e0aa1f10d9391e146951378918787b8a8c0 on mozilla:master.


Support #include directives in nodes

I'm using this for a Kinesis advantage 360 keyboard which uses ZMK.  It is possible to use #include directives inside of nodes so that you can write code like this:
/ {
  behaviors {
    #include "macros.dtsi"
  };
  keymap {
    ...
  }
}

@joelspadin Anything that needs additional updates in this PR or can it be merged?

Sorry, I was busy with other things and forgot about this. Is there a reason you chose to only allow #include? Other preprocessor commands like #define, #if, etc. can be used anywhere in a file as well.

Sorry, I was busy with other things and forgot about this. Is there a reason you chose to only allow #include? Other preprocessor commands like #define, #if, etc. can be used anywhere in a file as well.

No specific reason other than I'm not super familiar with the language spec. Added the other preproc nodes.

@joelspadin any chance we can get this PR merged? I think I addressed all of the feedback at this point

I don't think the previous conversation on grammar.js has been resolved? It's fine if a preprocessor command doesn't parse unless there's whitespace after the first token, but including the whitespace in the token itself isn't ideal. For example, if code using this parser were to change the background color of #if tokens, then I expect it would extend to the first whitespace character after the #if as well.

@joelspadin I was able to figure it out finally and re-opened this pull request as I had some of my branches messed up https://github.com/joelspadin/tree-sitter-devicetree/pull/11