Set-up instructions need info to get submodules

If you follow the steps as is the examples won't run. Need submodules via npm.

@alaframboise  I ran through the steps here and the sample apps worked for me. The npm install step installs the dependencies including application-base-js
https://github.com/Esri/configurable-app-examples-4x-js#getting-started


fix result when summarize is passed to duckdb

Describe your changes
Now the correct result is displayed when SUMMARIZE is passed to duckdb with sqlalchemy connection
Issue number
Closes #836
Checklist before requesting a review

[x] Performed a self-review of my code
[x] Formatted my code with pkgmt format
[x] Added tests (when necessary).
[x] Added docstring documentation and update the changelog (when needed)

:books: Documentation preview :books:: https://jupysql--841.org.readthedocs.build/en/841/

For context,
With sqlalchemy==1.4.49, result of query is stored in LegacyCursorResult. Not sure why, but result stored here remains even after commit().
In sqlalchemy==2.x.x, LegacyCursorResult is removed, and result is stored in CursorResult. In this case, the CursorResult is emptied after commit() : related issue
So as @edublancas suggested here, returning the CursorResult without commit() (like we do with select, with, and from for duckdb) solves the problem.


How to set connection timeout?

Hello,
Please check documentation for cursor timeout.
Sorry for late reply.
Thanks.


Can you send me eth?

I'm trying to generate huge amount of transactions for a work demo. Is it possible for you to send me 100ETHs for Ropsten test network? My address is 0xF7D48a4B5B2E25C72Cd507e5aF924A30516D753B. Thanks in advance!

done https://ropsten.etherscan.io/tx/0xa2f8b78b8e1eeba43ead35fc3d8d2ab016b0de5c2293cf16818c9b746434aa77


Kategorie in Fahrtenliste abbilden

used categories can't be deleted if for whatever reason categories exist in a fahrt but not in categories it will be  added now


update envoy sha - fix memory leak

Signed-off-by: Shriram Rajagopalan<EMAIL_ADDRESS>

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: rshriram
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [rshriram]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@rshriram: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
4e10d2c2f1c32ec49a393f7d2e13623ca553df93
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
4e10d2c2f1c32ec49a393f7d2e13623ca553df93
link
/test istio-unit-tests

prow/istio-presubmit.sh
4e10d2c2f1c32ec49a393f7d2e13623ca553df93
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
4e10d2c2f1c32ec49a393f7d2e13623ca553df93
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
4e10d2c2f1c32ec49a393f7d2e13623ca553df93
link
/test e2e-mixer-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-mixer-no_auth


Add golangci-lint

Adds golangci-lint. This would be a (picky!) linter for in pull requests.

Will try to rebase. If it compiles it makes sense to add it.


[Feature Request] Include attempted operations in summary coverage message

💡 Idea
At the conclusion of a Restler run, a message is displayed:
Request coverage (successful / total): 17 / 24

It would be nice to indicate how many operations were attempted in this message, e.g.:
Request coverage (successful / attempted / total): 17 / 22 / 24

Where "attempted" means that a request was issued. Operations that were not attempted did not have a request issued because some dependent operation failed.
Design Notes
No response

Hello @MikeKistler,
How about printing the attempted number of requests on a separate line?  (To keep request coverage  as a clear coverage metric of X/Y.)
Request coverage (successful / total): 17 / 24
Attempted requests (executed / total): 21 / 24

Thanks,
Marina


frontend: support multi-way logical join

We need a new plan node, so as to support multi-way delta join rewrite on meta node.

depends on https://github.com/singularity-data/risingwave/issues/1907


max from one team

I want to limit the number of players from a single team in any lineup.  I'm currently grouping players by team and setting a max_from_group on each group.  Is there a more elegant/simpler way to do this?  I see the attribute "max_from_one_team" but don't see how to modify this value.

Sorry...this has been asked and answered.  It looks like if you want to adjust this value on the fly, this is as good as it gets.  Has anyone added a setter for this value?

Looks like I added a setter.
In lineup_optimizer.py, within class LineupOptimizer add:
    def set_max_from_one_team(self, max: int):
        self.settings.max_from_one_team = max

Then you can call this when you're setting up your optimizer:
opt.set_max_from_one_team(maxStack)

I'm not sure how I can get this to work I want to limit the max players for 1 team to 3 from thunders today

If you're saying "I want no more than three OKC players in any given line":
players = optimizer.player_pool.get_players(PlayerFilter(teams=['OKC']))
group = PlayersGroup(players, max_from_group=3)
optimizer.add_players_group(group)

Cam I use multiple group settings for every team
On Tue, Jan 11, 2022, 3:57 PM holmes72 @.***> wrote:

If you're saying "I want no more than three OKC players in any given line":
players = optimizer.player_pool.get_players(PlayerFilter(teams=['OKC']))
group = PlayersGroup(players, max_from_group=3)
optimizer.add_players_group(group)
—
Reply to this email directly, view it on GitHub
https://github.com/DimaKudosh/pydfs-lineup-optimizer/issues/338#issuecomment-1010353260,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANBWO7RAY4CYINJ77C2DAPLUVSKTRANCNFSM5LQYP3UQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>

I'm not a fan of "RTFM" responses, but it seems to apply here.  The answer is "yes", and I encourage you to check out the readthedocs site: https://pydfs-lineup-optimizer.readthedocs.io/en/latest/index.html

Thanks, I'll check it out.
On Tue, Jan 11, 2022, 4:46 PM holmes72 @.***> wrote:

I'm not a fan of "RTFM" responses, but it seems to apply here. The answer
is "yes", and I encourage you to check out the readthedocs site:
https://pydfs-lineup-optimizer.readthedocs.io/en/latest/index.html
—
Reply to this email directly, view it on GitHub
https://github.com/DimaKudosh/pydfs-lineup-optimizer/issues/338#issuecomment-1010388008,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANBWO7QMSB36FDEAWF7ZFLDUVSQM5ANCNFSM5LQYP3UQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>

I I got a question, why do I get this
Traceback (most recent call last):
File "Fanduel2Finish2.py", line 62, in
players = optimizer.player_pool.get_players(PlayerFilter(teams=['MIN']))
NameError: name 'PlayerFilter' is not defined
On Tue, Jan 11, 2022, 5:04 PM joseph offen @.***> wrote:

Thanks, I'll check it out.
On Tue, Jan 11, 2022, 4:46 PM holmes72 @.***> wrote:

I'm not a fan of "RTFM" responses, but it seems to apply here. The answer
is "yes", and I encourage you to check out the readthedocs site:
https://pydfs-lineup-optimizer.readthedocs.io/en/latest/index.html
—
Reply to this email directly, view it on GitHub
https://github.com/DimaKudosh/pydfs-lineup-optimizer/issues/338#issuecomment-1010388008,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANBWO7QMSB36FDEAWF7ZFLDUVSQM5ANCNFSM5LQYP3UQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>

Fixed it
On Tue, Jan 11, 2022, 7:23 PM joseph offen @.***> wrote:

I I got a question, why do I get this
Traceback (most recent call last):
File "Fanduel2Finish2.py", line 62, in
players =
optimizer.player_pool.get_players(PlayerFilter(teams=['MIN']))
NameError: name 'PlayerFilter' is not defined
On Tue, Jan 11, 2022, 5:04 PM joseph offen @.***> wrote:

Thanks, I'll check it out.
On Tue, Jan 11, 2022, 4:46 PM holmes72 @.***> wrote:

I'm not a fan of "RTFM" responses, but it seems to apply here. The
answer is "yes", and I encourage you to check out the readthedocs site:
https://pydfs-lineup-optimizer.readthedocs.io/en/latest/index.html
—
Reply to this email directly, view it on GitHub
https://github.com/DimaKudosh/pydfs-lineup-optimizer/issues/338#issuecomment-1010388008,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANBWO7QMSB36FDEAWF7ZFLDUVSQM5ANCNFSM5LQYP3UQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>


ScheduleOrPostopone in Python, type error

Hi everyone,
I'm trying to use the function ScheduleOrPostpone with Python 3.6 , in my case the invoked function is : ScheduleOrPostpone(var,est,support[i]) where var is an IntervalVar, est is an Int, support is a Dictionary and i is an index.
The error is: TypeError: in method 'Solver_ScheduleOrPostpone', argument 4 of type 'int64 *const'
Then after this error, I saw default arguments types of this function which are IntervalVar* const var, int64 est, int64* const.
Now what I am asking about is, how do i create an int64 *const in python and let my invoked function works without errors? I tried to use the ctypes python library and made a pointer through the byref function  "byref(c_longlong(markers__[i]))" and then pass this to ScheduleOrPostpone but the error still occurs.
Thanks
Valerio

This function is not meant to be used directly as the support is passed by
the decision builder in C++.
If you are interested in scheduling and python, I would suggest you look at
our CP/SAT solver.
There are a few scheduling examples:
examples/python/gate_scheduling_sat.py
examples/python/jobshop_ft06_sat.py
examples/python/rcpsp_sat.py
The API is simpler, and the performance would be much better IMO.
The full modeling API is in ortools/sat/python/cp_model.py
--Laurent
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
2017-11-07 10:32 GMT+01:00 valrem93<EMAIL_ADDRESS>
Hi everyone,
I'm trying to use the function ScheduleOrPostpone with Python 3.6 , in my
case the invoked function is : ScheduleOrPostpone(var,est,support[i])
where var is an IntervalVar, est is an Int, support is a Dictionary and i
is an index.
The error is: TypeError: in method 'Solver_ScheduleOrPostpone', argument 4
of type 'int64 *const'
Then after this error, I saw default arguments types of this function
which are IntervalVar* const var, int64 est, int64* const.
Now what I am asking about is, how do i create an int64 *const in python
and let my invoked function works without errors? I tried to use the ctypes
python library and made a pointer through the byref function
"byref(c_longlong(markers__[i]))" and then pass this to
ScheduleOrPostpone but the error still occurs.
Thanks
Valerio
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/524, or mute the thread
https://github.com/notifications/unsubscribe-auth/AKj17Wrwm3OKQ8Lb7TYbG7XcV5pbrHbgks5s0COzgaJpZM4QUfh8
.


unexpected keyword argument 'skip_instance_cache'

Version: s3fs==0.4.0
Passing skip_instance_cache to s3fs.S3FileSystem as indicated in the docs does not succeed:
>>> import s3fs
>>> s3fs.S3FileSystem(skip_instance_cache=True)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/josephsheedy/venv/py3/lib/python3.8/site-packages/fsspec-0.6.2-py3.8.egg/fsspec/spec.py", line 52, in __call__
    obj = super().__call__(*args, **kwargs)
  File "/Users/josephsheedy/git/s3fs/s3fs/core.py", line 156, in __init__
    self.s3 = self.connect()
  File "/Users/josephsheedy/git/s3fs/s3fs/core.py", line 228, in connect
    self.session = botocore.session.Session(**self.kwargs)
TypeError: __init__() got an unexpected keyword argument 'skip_instance_cache'

Other kwargs ['use_listings_cache', 'listings_expiry_time', 'max_paths'] destined for fsspec are handled in __init__, but not skip_instance_cache.

Thanks for posting.
Note that this is still unreleased.

This issue is still present in s3fs 0.5.1. skip_instance_cache is not passed to the superclass: https://github.com/dask/s3fs/blob/c8ce8a515f7d4e61650bc23742bcdbc25f78cdd1/s3fs/core.py#L198

0.5.2 (available on pypi and shortly on conda-forge) does not appear to have this problem:
In [1]: import s3fs

In [2]: s3 = s3fs.S3FileSystem()

In [3]: s3fs.S3FileSystem(skip_instance_cache=True) is not s3
True

My bad! I had monkeypatched s3fs.core.S3FileSystem.__init__ with some default arguments, but didn't realize there was a metaclass fsspec.spec._Cached that is supposed to consume the skip_instance_cache kwarg. Monkeypatching fsspec.spec._Cached.__call__ solved the issue.
Context: I'm doing this to pass default arguments to S3FileSystem when using Dask. Is there a recommended way of doing this, other than passing them as storage_options to the Dask operation? I'd rather not pass them at every call site, but instead configure them once per process globally.

You could use the configuration for this

Thanks @martindurant, that's exactly what I needed! I was confused for a minute because I've been searching for this in the past, but then I noticed that the fsspec.config module is new. Great that this was added!


Business cases do not re-calculate when strategies are updated

See LES 313 for example.

Since this is only - not working on the production environment - the most easy fix would be to merge all the changes that are related to the business cases to the production environemnt.

Can we identify the issue and cherry-pick the relevant commit onto the production branch? I think we should have another production deploy of Moses soon, but this would be good enough for the short-term.

Can we identify the issue and cherry-pick the relevant commit onto the production branch?

Yes. That's basically what I was trying to say.

@dennisschoenmakers is doing a demo at the moment. Please wait an hour or so before deploying production!

The problem is that the Moses scenario points to ETEngine scenario 434138. ETEngine has no such scenario.
ETEngine production scenarios are currently numbered in the 200,000s, while staging is in the 400,000s. I'm not clear how production Moses could take scenarios from staging ETEngine, and I'm sure I deleted all the scenarios on Moses production during the deploy last week.
The created_at field is "2015-09-27 13:24:33" which is three days before the deploy. Did these scenarios get imported manually somehow?
404 Resource Not Found
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/rest-client-1.6.7/lib/restclient/abstract_response.rb:48:in `return!'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/rest-client-1.6.7/lib/restclient/request.rb:230:in `process_result'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/rest-client-1.6.7/lib/restclient/request.rb:178:in `block in transmit'
/home/ubuntu/.rbenv/versions/2.1.1/lib/ruby/2.1.0/net/http.rb:853:in `start'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/rest-client-1.6.7/lib/restclient/request.rb:172:in `transmit'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/rest-client-1.6.7/lib/restclient/request.rb:64:in `execute'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/rest-client-1.6.7/lib/restclient/request.rb:33:in `execute'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/rest-client-1.6.7/lib/restclient.rb:68:in `get'
/var/www/etmoses/releases/20150930151452/lib/et_engine_connector.rb:67:in `public_send'
/var/www/etmoses/releases/20150930151452/lib/et_engine_connector.rb:67:in `et_api_request'
/var/www/etmoses/releases/20150930151452/lib/et_engine_connector.rb:42:in `merit'
/var/www/etmoses/releases/20150930151452/app/models/market/from_market_model_builder.rb:63:in `merit_curve'
/var/www/etmoses/releases/20150930151452/app/models/market/from_market_model_builder.rb:54:in `convert_tariff'
/var/www/etmoses/releases/20150930151452/app/models/market/from_market_model_builder.rb:33:in `block in relations'
/var/www/etmoses/releases/20150930151452/app/models/market/from_market_model_builder.rb:27:in `map'
/var/www/etmoses/releases/20150930151452/app/models/market/from_market_model_builder.rb:27:in `relations'
/var/www/etmoses/releases/20150930151452/app/models/market/from_market_model_builder.rb:18:in `data'
/var/www/etmoses/releases/20150930151452/app/models/market/from_market_model_builder.rb:11:in `to_market'
/var/www/etmoses/releases/20150930151452/app/models/market.rb:59:in `from_market_model'
/var/www/etmoses/releases/20150930151452/app/services/finance/business_case_calculator.rb:40:in `market'
/var/www/etmoses/releases/20150930151452/app/services/finance/business_case_calculator.rb:32:in `row'
/var/www/etmoses/releases/20150930151452/app/services/finance/business_case_calculator.rb:23:in `block in cells'
/var/www/etmoses/releases/20150930151452/app/services/finance/business_case_calculator.rb:21:in `map'
/var/www/etmoses/releases/20150930151452/app/services/finance/business_case_calculator.rb:21:in `cells'
/var/www/etmoses/releases/20150930151452/app/services/finance/business_case_calculator.rb:10:in `block in rows'
/var/www/etmoses/releases/20150930151452/app/services/finance/business_case_calculator.rb:9:in `map'
/var/www/etmoses/releases/20150930151452/app/services/finance/business_case_calculator.rb:9:in `rows'
/var/www/etmoses/releases/20150930151452/app/services/finance/business_case_creator.rb:16:in `financials'
/var/www/etmoses/releases/20150930151452/app/services/finance/business_case_creator.rb:10:in `calculate'
/var/www/etmoses/releases/20150930151452/app/jobs/business_case_calculator_job.rb:12:in `perform'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/backend/base.rb:94:in `block in invoke_job'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `call'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `block in initialize'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `call'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `execute'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:40:in `run_callbacks'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/backend/base.rb:91:in `invoke_job'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/worker.rb:204:in `block (2 levels) in run'
/home/ubuntu/.rbenv/versions/2.1.1/lib/ruby/2.1.0/timeout.rb:91:in `block in timeout'
/home/ubuntu/.rbenv/versions/2.1.1/lib/ruby/2.1.0/timeout.rb:101:in `call'
/home/ubuntu/.rbenv/versions/2.1.1/lib/ruby/2.1.0/timeout.rb:101:in `timeout'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/worker.rb:204:in `block in run'
/home/ubuntu/.rbenv/versions/2.1.1/lib/ruby/2.1.0/benchmark.rb:294:in `realtime'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/worker.rb:203:in `run'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/worker.rb:280:in `block in reserve_and_run_one_job'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `call'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `block in initialize'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `call'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `execute'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:40:in `run_callbacks'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/worker.rb:280:in `reserve_and_run_one_job'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/worker.rb:187:in `block in work_off'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/worker.rb:186:in `times'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/worker.rb:186:in `work_off'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/worker.rb:150:in `block (4 levels) in start'
/home/ubuntu/.rbenv/versions/2.1.1/lib/ruby/2.1.0/benchmark.rb:294:in `realtime'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/worker.rb:149:in `block (3 levels) in start'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `call'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `block in initialize'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `call'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `execute'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:40:in `run_callbacks'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/worker.rb:148:in `block (2 levels) in start'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/worker.rb:147:in `loop'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/worker.rb:147:in `block in start'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/plugins/clear_locks.rb:7:in `call'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/plugins/clear_locks.rb:7:in `block (2 levels) in <class:ClearLocks>'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:79:in `call'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:79:in `block (2 levels) in add'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `call'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:61:in `block in initialize'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:79:in `call'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:79:in `block in add'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `call'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:66:in `execute'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/lifecycle.rb:40:in `run_callbacks'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/worker.rb:146:in `start'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/command.rb:124:in `run'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/command.rb:112:in `block in run_process'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/daemons-1.2.2/lib/daemons/application.rb:265:in `call'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/daemons-1.2.2/lib/daemons/application.rb:265:in `block in start_proc'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/daemons-1.2.2/lib/daemons/daemonize.rb:84:in `call'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/daemons-1.2.2/lib/daemons/daemonize.rb:84:in `call_as_daemon'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/daemons-1.2.2/lib/daemons/application.rb:269:in `start_proc'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/daemons-1.2.2/lib/daemons/application.rb:295:in `start'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/daemons-1.2.2/lib/daemons/controller.rb:56:in `run'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/daemons-1.2.2/lib/daemons.rb:193:in `block in run_proc'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/daemons-1.2.2/lib/daemons/cmdline.rb:88:in `call'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/daemons-1.2.2/lib/daemons/cmdline.rb:88:in `catch_exceptions'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/daemons-1.2.2/lib/daemons.rb:192:in `run_proc'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/command.rb:110:in `run_process'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/command.rb:91:in `block in daemonize'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/command.rb:89:in `times'
/var/www/etmoses/shared/bundle/ruby/2.1.0/gems/delayed_job-4.0.6/lib/delayed/command.rb:89:in `daemonize'
bin/delayed_job:5:in `<main>'

Did these scenarios get imported manually somehow?

Yes.

Closing.

@grdw please remove the offending LESses again from the production database to prevent future issues.


🧪test lexical analyzer

Closes #39 and #12

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

144 of 182 (79.12%)  changed or added relevant lines in 5 files are covered.
9 unchanged lines in 4 files lost coverage.
Overall coverage increased (+2.9%) to 38.191%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/utils/message.c
10
14
71.43%

unit_test/src/minishell_cases.c
0
34
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/utils/message.c
1
25.0%

src/lexer/lexer.c
2
82.98%

unit_test/src/minishell_cases.c
2
0%

src/lexer/lexer_utils.c
4
75.0%

Totals

Change from base Build<PHONE_NUMBER>:
2.9%

Covered Lines:
553

Relevant Lines:
1448

💛  - Coveralls


Adds Teams scope to the list of default permissions in the docs. Closes #1860

Adds Teams scope to the list of default permissions in the docs. Closes #1860

Merged manually.


can gorm support MySQL type ”point“？

can gorm support MySQL type ”point“ or other geometry type ？

too many legacy for gorm. To get rid of legacy, I purposely wrote another ORM https://github.com/si3nloong/sqlike


angular 6x has an error

Environment

ng-alain version: 1.0.1.beta2
Angular version: 6.0.0

I run yarn install then ng serve.  an error
ERROR in ./src/styles.less (./node_modules/raw-loader!./node_modules/postcss-loader/lib??embedded!./node_modules/@angular-devkit/build-angular/node_modules/less-loader/dist/cjs.js??ref--15-3!./src/styles.less)
Module build failed:

// https://github.com/ant-design/ant-motion/issues/44
.bezierEasingMixin();
^
Inline JavaScript is not enabled. Is it set in your options?
      in node_modules/ng-zorro-antd/src/style/color/bezierEasing.less (line 110, column 0)
ERROR in ./src/app/routes/passport/register/register.component.less
Module build failed:

@cipchk

downgrade less from 3.x to 2.7.x, #10430

好像问题没解决啊，clone下来启动还是会报错

@dai875939260 移除 node_modules 和 package.json，重新 npm i 或 yarn

我移除过了。

I have the same issue when less-loader's version to 4.1.0, and less is 2.7.0.
but if you downgrade less-loader from 4.1.0 to 4.0.6, then it passed.

locate to<EMAIL_ADDRESS> line 136 and 142 （may be different in different version），modify lessPathOptions  object，add property :  lessPathOptions.javascriptEnabled = true
let lessPathOptions = { paths: [], javascriptEnabled: true};     if (......);         lessPathOptions = {             paths: includePaths,             javascriptEnabled: true         };     }
resolution from  https://segmentfault.com/a/1190000015577159

change in package.json,  I found  when use 0.7.0, there is no error.
"@angular-devkit/build-angular": "0.7.0"


Update Spring Boot microservices to use opentracing/java-spring-jaeger

The easiest way to Spring Boot microservices working with Jaeger is to use the corresponding opentracing project.
If you are interested, I could take up this task

It most certainly is.
My idea was to utilize opentracing/java-spring-jaeger to make configuration even simpler


[Automation] - IPMI way to get sensor data

https://github.com/openbmc/openbmc/issues/1089
Most likely we can automate it in March.
I want Prashant to do this under the guidance of Rahul.  Rahul will be the owner.
Prashant will be delivering it.

Please go thru the development issue and understand it this sprint. Start the Base work.

As this is associate development change is parked in Phase 5, We can do it later.

@sivassrr : Dev code is planned to come very late in Phase 5.  So we should keep this story on hold.


2.27 answer I think have some problems

int *const p2 = &i2 ;
const int *const p3 = &i2;
const int *p1 = &i2;
these three "i2"  is  not  definition type . and as far as I am concerned , the "const pointer" or "pointer to const"  only can direction corresponding  type. so i think the  answer have some dispute

It's the question's problem, not the answer :joy:


wrap NLSolvers.jl

https://github.com/JuliaNLSolvers/NLSolvers.jl

Duplicate of https://github.com/SciML/NonlinearSolve.jl/issues/75


Option to specify the Route53 hosted zone

Prerequisites

[x] I am running the latest version. (up upgrade)
[x] I searched to see if the issue already exists.
[x] I inspected the verbose debug output with the -v, --verbose flag.
[ ] Are you an Up Pro subscriber?

Description
Prior to 3.8 one could use up to create hosted zone / use domains without having the dns of the effective tld plus one mapped to the account. In short prior to 3.8 up supported subdomains as the base domain.
But since https://github.com/apex/up/commit/ce1ebf5a46af639252d921dff318448797b3c0e5 up always creates a hosted zone for the effective tld plus one. This adds a requirement on DNS that isn't always fulfillable - pointing the base domains DNS to the account.
Steps to Reproduce
With a config like this:
{
	"name": "vwa-osc-scc",
	"lambda": {
		"memory": 256
	},
	"hooks": {
		"build": "",
		"clean": ""
	},
	"stages": {
		"development": {
			"domain": "dev.sub.domain.example.com"
		},
		"production": {
			"domain": "sub.domain.example.com"
		},
		"staging": {
			"domain": "stage.sub.domain.example.com"
		}
	}
}

you would get a hosted zone for example.com. Prior to 3.8 you would have got a hosted zone for domain.example.com.

Another vote for this please!
https://s.natalian.org/2018-05-08/subdomains.mp4
Was surprised to see a top level zone created in my dev account :sweat_smile:


bump gateway api and implementation versions

Going to merge this with - https://github.com/knative-extensions/net-gateway-api/pull/790


Feature request: Data Class for Cloudwatch Logs passed through Kinesis Stream

Use case
We are currently passing Cloudwatch logs to a Kinesis stream to be subsequently processed by a Lambda. We'd like to use the cloud_watch_logs_event data class but it only works when the source is Cloudwatch directly, not Kinesis. It seems when Cloudwatch targets Lambda, it wraps the payload in the following superstructure:
'awslogs': {'data': {<PAYLOAD>}}
You can see that the existing CloudWatchLogsEvent class' raw_logs_data property expects this structure to unpack the data.
This superstructure doesn't show up when the logs are passed through kinesis
Solution/User Experience
I think a new method/property within the CloudWatchLogsEvent class, perhaps named parse_logs_kinesis() or something, which can be used to unpack this type of payload, could work.
However that may be less than ideal since accidentally using the existing raw_logs_data property would then cause issues, so it's possible that an entirely new class (like CloudWatchLogsKinesisEvent, ex) would be preferable.
A third option would be to rewrite the existing raw_logs_data property, such that it checks for the presence of the Cloudwatch->Lambda superstructure:
return self['awslogs']['data'] if self.get('awslogs') else self[0]
(safe retrieval from nested dicts can get a bit klunky)
Note: Originally posted in discussions forum here.
Alternative solutions
No response
Acknowledgment

[X] This feature request meets Lambda Powertools Tenets
[X] Should this be considered in other Lambda Powertools languages? i.e. Java, TypeScript

Hey @blewinter thanks for following up with a feature request on this - would you have the bandwidth to contribute it? We can offer guidance sync or async on our Discord channel.
If you don't, we can ping you to review a PR once we clear other activities.
:rocket:

Hi! Apologies, I wasn't receiving notifications on this thread. I'd love to contribute!

However that may be less than ideal since accidentally using the existing raw_logs_data property would then cause issues, so it's possible that an entirely new class (like CloudWatchLogsKinesisEvent, ex) would be preferable.

Hi @blewinter! We think this is the best and safest way to implement this. A new class to handle events coming from Kinesis is a great idea.
We look forward to your contribution. If you have any questions or want help testing something, please let me know and I'll be available for that. :robot:

Hi @blewinter! I hope things are going well there.
We are planning to include this change in the next release, which I think will be in 2 or 3 weeks. But it's okay to move this change to another release if you need more time to implement this or we can even implement this and ping it for you to review before the merge. We'd love to hear the best option for you :ear:.
Thank you

Hey, I had to put it aside for a bit but I might be able to have it by the end of next week! I will keep you posted

Hi,
So I had played around with the idea of a separate class for this feature, but I think a simple conversion function might be preferable? Of course can wrap in a class. Lots of ways to implement this. What do you think of this approach?
https://github.com/blewinter/aws-lambda-powertools-python/blob/feat/cloudwatch-kinesis-log/aws_lambda_powertools/utilities/data_classes/cloud_watch_kinesis_log.py

Hi @blewinter! Tomorrow I'll check it out. But at first glance it looks good, I just check more details if nothing is missing.
Thank you

So I had played around with the idea of a separate class for this feature, but I think a simple conversion function might be preferable? Of course can wrap in a class. Lots of ways to implement this. What do you think of this approach?
<EMAIL_ADDRESS>
Hi @blewinter, I really like the idea of reusing existing code and just wrapping the payload, it's very clever. I don't think we need to use KinesisStreamRecordPayload to. Look at this code that I created.
cloud_watch_kinesis_log.py
import base64
import json
import zlib
from aws_lambda_powertools.utilities.data_classes.cloud_watch_logs_event import CloudWatchLogsEvent, CloudWatchLogsDecodedData
from aws_lambda_powertools.utilities.data_classes.common import DictWrapper

class CloudWatchKinesisLogEvents(DictWrapper):

    def __init__(self, data):
        payload = json.dumps(data, indent=2).encode('utf-8')
        payload = base64.b64encode(zlib.compress(payload))
        self.wrapped = {"awslogs": {"data": payload}}

    @property
    def raw_logs_data(self) -> str:
        """The value of the `data` field is a Base64 encoded ZIP archive."""
        return self.wrapped

    def parse_logs_data(self) -> CloudWatchLogsDecodedData:
        return CloudWatchLogsEvent(self.wrapped).parse_logs_data()

lambda_handler.py
from aws_lambda_powertools.utilities.data_classes import event_source, CloudWatchKinesisLogEvents
from aws_lambda_powertools.utilities.data_classes.cloud_watch_logs_event import CloudWatchLogsDecodedData

@event_source(data_class=CloudWatchKinesisLogEvents)
def lambda_handler(event: CloudWatchKinesisLogEvents, context):

    print(event.raw_logs_data)

    decompressed_log: CloudWatchLogsDecodedData = event.parse_logs_data()
    print(decompressed_log.log_events)

    log_events = decompressed_log.log_events
    for xyz in log_events:
        print(xyz.timestamp,xyz.message,xyz.extracted_fields,xyz.raw_event)

output

@heitorlessa or @rubenfonseca can you take a look here and give another opinion if it's worth it?

Yeah I considered the tradeoff of adding the KinesisEvent dependency. In this case I thought the clarity provided by specifying it as the input class was worth it, but totally see the other side of it. This looks great! Thank you!

Yeah I considered the tradeoff of adding the KinesisEvent dependency. In this case I thought the clarity provided by specifying it as the input class was worth it, but totally see the other side of it. This looks great! Thank you!

That's amazing to hear. Do you have the bandwidth to send this PR using this approach? If you have any kind of questions, you can ping me on Discord or even check out this very similar PR #1485.
Thank you!

I don't have bandwidth for a full pr, but would essentially be like this
from aws_lambda_powertools.utilities.data_classes.cloud_watch_logs_event import CloudWatchLogsEvent, CloudWatchLogsDecodedData
from aws_lambda_powertools.utilities.data_classes.kinesis_stream_event import KinesisStreamRecordPayload
from aws_lambda_powertools.utilities.data_classes.common import DictWrapper

class CloudWatchKinesisLogEvents(DictWrapper):

    def __init__(self, kinesis_payload: KinesisStreamRecordPayload):
        payload = kinesis_payload.data_as_bytes()
        self.wrapped = {"awslogs": {"data": payload}}

    @property
    def raw_logs_data(self) -> str:
        """The value of the `data` field is a Base64 encoded ZIP archive."""
        return self.wrapped

    def parse_logs_data(self) -> CloudWatchLogsDecodedData:
        return CloudWatchLogsEvent(self.wrapped).parse_logs_data()

So the usage would be essentially identical, except a KinesisStreamRecordPayload is passed when initalized. I think that explicitness is useful in this case, but it does also add a dependency, so I think it's just a preference thing which approach is better. (Btw I'd think in real-world usage, someone would write a handler for a KinesisStreamEvent, unpack the records, and pass each payload to create this object)

Hi @blewinter! Let me open a PR for this feature and if you have bandwidth you can do a review with me.
Thank you very much for all the interaction so far and we'll be happy to mention you in the credits for this new feature. :1st_place_medal:

@leandrodamascena when you can, could you share what's the latest so I can take over for this iteration cycle?

apologies for the delay @blewinter - Catching up on all messages and the original discussion too. @leandrodamascena is away until mid January so I'm taking over.

alright, I'm caught up. It's missing a sample event in this discussion, so I'll create the infra, create tests, and ping here when a PR is available.

@blewinter (and @leandrodamascena for when you're back) - I've tested both classes and a standalone function, and I settled for the latter to prevent data pollution and coupling where a class instance method returns a completely different entity.
Once I have your confirmation that this solves your use case, I'll create a PR and make sure it's included in the next release.
Here's what I've changed:

New method named data_zlib_compressed_as_json in KinesisStreamRecordPayload. This can also be useful for compressed JSON strings sent to Kinesis (telemetry, AdTech, etc.).
New standalone functions to parse, extract and transform into CloudWatchLogsDecodedData

extract_cloudwatch_logs_from_record(record) -> CloudWatchLogsDecodedData
extract_cloudwatch_logs_from_event(event) -> List[CloudWatchLogsDecodedData]

I've created two samples to best demonstrate this.
Processing batch of logs
This example uses Batch processing utility along with extract_cloudwatch_logs_from_record to parse a given log.
It provides a clear separation to handle each log at a time, partial failure support built-in, allowing you to trace, log correlation data, and potentially make idempotent too depending on how critical the operation is.
from aws_lambda_powertools.utilities.batch import (BatchProcessor, EventType,
                                                   batch_processor)
from aws_lambda_powertools.utilities.data_classes.kinesis_stream_event import (
    KinesisStreamRecord, extract_cloudwatch_logs_from_record)

processor = BatchProcessor(event_type=EventType.KinesisDataStreams)

def record_handler(record: KinesisStreamRecord):
    log = extract_cloudwatch_logs_from_record(record)
    return log.message_type == "DATA_MESSAGE"

@batch_processor(record_handler=record_handler, processor=processor)
def lambda_handler(event, context):
    return processor.response()

Simplest log processing
This example uses Event Source Data Class event_source decorator along with extract_cloudwatch_logs_from_event.
I'm less inclined on this as it puts the onus on you to loop and handle partial failures, since you're dealing with a stream of records - adding for the sake of completion.
If you also don't agree, we can keep extract_cloudwatch_logs_from_record function only to keep the code base tidy.
from typing import List

from aws_lambda_powertools.utilities.data_classes import event_source
from aws_lambda_powertools.utilities.data_classes.cloud_watch_logs_event import \
    CloudWatchLogsDecodedData
from aws_lambda_powertools.utilities.data_classes.kinesis_stream_event import (
    KinesisStreamEvent, extract_cloudwatch_logs_from_event)

@event_source(data_class=KinesisStreamEvent)
def simple_handler(event: KinesisStreamEvent, context):
    logs: List[CloudWatchLogsDecodedData] = extract_cloudwatch_logs_from_event(event)
    for log in logs:
        if log.message_type == "DATA_MESSAGE":
            return "success"
    return "success"

Implementation, tests, and documentation ready: https://github.com/awslabs/aws-lambda-powertools-python/pull/1710
I'll merge this on Wed to ensure it's available in the next release in case I don't hear back from OP

Hey, this looks great, thank you! Looking forward to using it!


GeoJSON Layers are not rendered properly on Map Panning

You can reproduce this problem on your Interactive Cloropleth example.
For example you click on Colorado state and drag it all the way to the right border of the map. You release the mouse and then click and drag all the way to the left and half of the overlay dissapears.
This is only happening when you pan with a click and drag of the mouse.

I wrote a hack on which I remove my GeoJSON layer and add it again after the dragend event.
map.on("dragend", function (e) {
	mygeojsonlayer.clearLayers();
	mygeojsonlayer = L.geoJson(my_geojson_data);
	mygeojsonlayer.addTo(map);
});

I guess this is a small bug easily fixable.

Duplicate of #4743


These privileges are not only for model-driven apps

This topic applies to privileges defined for the Common Data Service, Not only for model-driven apps.
This topic shouldn't be here
/powerapps/maker/model-driven-apps
It should be here
/powerapps/maker/common-data-service
Also this topic in the on-premises content should be removed and redirected to this topic
https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/privileges-required-customization

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

ID: 6c92b4e1-8c8a-6092-11e2-8162c867dc26
Version Independent ID: 04694159-031b-9124-008a-ef9f05219118
Content: Privileges required for model-driven app customizing - Power Apps
Content Source: powerapps-docs/maker/model-driven-apps/privileges-required-customization.md
Service: powerapps
GitHub Login: @Mattp123
Microsoft Alias: matp

@JimDaly  Moved in TOC and revised title and article body to reference Dataverse instead of model-driven app where appropriate.
Closing issue.

@JimDaly  Moved in TOC and revised title and article body to reference Dataverse instead of model-driven app where appropriate.
Closing issue.

I still think the topic should be moved from
/powerapps/maker/model-driven-apps
to
/powerapps/maker/common-data-service
Privileges belong to Dataverse, model driven apps are built on top of Dataverse.
Model-driven apps are a kind of client, but the privileges apply even when model-driven apps are not used.

I still think the topic should be moved from
/powerapps/maker/model-driven-apps
to
/powerapps/maker/common-data-service
Privileges belong to Dataverse, model driven apps are built on top of Dataverse.
Model-driven apps are a kind of client, but the privileges apply even when model-driven apps are not used.

The article content has been revised to explicitly state Dataverse instead of model-driven apps, but will remain in the existing model-driven-apps folder. The customer engagement article will remain as-is since it applies to on-premises versions.
Closing issue.


Contains reserved characters

Hi,
When I run it with the report parameter, I get the following error.
Looking up https://github.com/paypal/Checkout-PHP-SDK/blob/master/LICENSE ...

In CacheItem.php line 167:

  Cache key "https://github.com/paypal/Checkout-PHP-SDK/blob/master/LICENSE" contains reserved characters "{}()/\@:".

I've looked into it and know what the issue is.
This package depends on the composer licenses command that reports entries in the composer.json file. The paypal/checkout-php-sdk in version 1.0.2 just points to a local file. A commit fixing this was made on the same day but did not make it into a package release.
An immediate fix could be to upgrade the package to this specific commit. As it is archived anyway, I don't expect any new versions and this shouldn't be too much of a problem. Can be done using composer require paypal/paypal-checkout-sdk dev-master#19992ce7051ff9e47e643f28abb8cc1b3e5f1812.
I'll fix the bug in this repository where the raw license name was used as a cache key (instead of a hash). This will get rid of the error but the reported license would still be incorrect (as it would not look up Apache-2).


Limit /spawn command

Changes:

Limit to Overworld
Only allow usage if the player has sky access

Thinking about:

Only allow if within X blocks from spawn

Incompatible with #35. These changes are meant to make the command less OP without completely removing it.

don't do X away from spawn


Issues from 3.0.0 to 3.1.2

I cannot import dropzone component as in 3.0.0 anymore:
import DropzoneComponent from 'react-dropzone-component';
with 3.1.2 I have to use import * as DropzoneComponent from 'react-dropzone-component';
That's fine... but now the component event handlers complains that the events (removeFile, processing, error) does not math the return type which are now FileCallBack and ErrorCallback.. which is fine again. I corrected that...
But where I get stuck, is there's still one last type mismatch. Typescript complains that "property 'push' is missing in type" for those  3 events
Could you help on how to fix or could it be something missing in type.d.ts?

Hello, have you resolved this? Facing the same issue here.


CRACO 7 / CRA 5: Uncaught ReferenceError: exports is not defined

Hi, after updating to React 18 / CRACO 7 / CRA 5 / Node 19 we encounter this strange error:
Uncaught ReferenceError: exports is not defined

This error only happens after building when serving the app. We use the latest version of everything.
Do you have any idea what could provoke such an error?

tsconfig:
"compilerOptions": {
"jsx": "react-jsx",
"lib": [
"DOM",
"DOM.Iterable",
"esnext",
"dom"
],
"noFallthroughCasesInSwitch": true,
"module": "esnext",
"allowJs": true,
"allowSyntheticDefaultImports": true,
"esModuleInterop": true,
"forceConsistentCasingInFileNames": true,
"isolatedModules": true,
"moduleResolution": "node",
"noEmit": true,
"resolveJsonModule": true,
"strict": true,
"skipLibCheck": true,
"target": "esnext"
},
babel.config:
module.exports = {
presets: ['module:metro-react-native-babel-preset'],
};

Hi, thanks for the fast reply. Awesome!
We're using a monorepo for react-native-web, android and iOS.
Yes the web part is CRACO / CRA / Webpack.
In your older versions 1.2 ? It worked without error.

I see. So far I couldn't reproduce your error, but I get a different one when trying to use the component with react-native-web: export 'StarIconProps' (reexported as 'StarIconProps') was not found in './StarIcon' (possible exports: default). Looks like it could be related. Unfortunately I don't have time right now, but I will do some research later today or tomorrow.

I just published a beta version which fixes the error that I was having. I hope this fixes your error too, but I'm not sure. Could you please test it by installing 1.6.0-beta.1?

Thanks for your fast changes, your above mentioned error doesn't occur anymore. But as soon as we use your package in any component, our bundled application now throws this error:

It probably has nothing to do with your code, but maybe you have an idea on why this happens.
Thank you in advance !

I don't really have an idea what's causing this, so I just basically recreated the package using the latest version of create-react-native-library. If there's a problem with the configuration of this package I think this might fix it, otherwise I suspect there might be something wrong with your tsconfig. Could you try if you're still seeing this error in 1.6.0-beta.2?

Seems to work! I think your package is working now. The other problems we now have seem to be with webpack and ESM modules :D Thank you for your fast responses.

Alright, great! I merged the changes and created a new release 1.6.0. Thanks for your help!

@bviebahn  We acutally just found out what the problem was with the Uncaught ReferenceError that crashed our whole build.
reac-native-svg: 3.6.0!! As soon as we use 3.6.0 in combination with your package everything crashes. But with 3.5.0 it works fine. FYI

Interesting, and this still happens with the changes I made? Also, you probably mean react-native-svg: 13.6.0, right? Can you tell me if you are able to use that version of react-native-svg on its own without a crash?

Yes of 13.6 of course, sry. Seems like it, i can draw other Icons with it. But I will try tomorrow again with the SVG's of your package inside our app without the star widget. I will update you.

It's really strange behaviour. If I use  like in your package but without using the StarRating, it still crashes.
But other implementations of react-native-svg like in NativeBase (where react-native-svg is a dependency there) work.
I can't really get the hang of it.
13.5.0 works everywhere and 13.6.0 not.

Yes strange. The icons are very basic and only use SVG, Path and Rect elements, so this seems to be an issue with react-native-svg. (Or your specific setup, since I also use 13.6.0). Let me know if you find out anything else.


Font recognition (font.ttf file)

Hello,
I think that you can fix this very fast. I am using the font.ttf file.
It looks like Mozila Firefox does`t recognize this font,
but i think that Pixi render makes a problem here.
Does this looks familiar to you?
Best regards.

pixi.js - v5.1.6
Mozila Firefox

You're description doesn't make sense. What font.ttf file are you talking about.

Do we even have ttf file loader? I mean, it should go to css stuff, either through FontObserver from another lib (not pixi)

Ivan is right, there's no font loading in Pixi. Devs should handle this in the browser themselves. I'm going to close this because it's out of scope. If the user provides more info or an examples, we can reopen.


Typo fix in README

Just a typo fix

LGTM

LGTM TOO!

Hi @tritone11, thank you for the heads up here and for submitting a PR. And @dfischer for the review. We'll push a fix shortly!


dataset links uncreachable

all the links to the datasets listed in the datasets section of the webpage return a 404 error.

Seconding this!

Also having trouble with this.

Thanks for flagging this folks! The entire dataset server is down now and I'm pinging people to investigate. Will keep folks posted here as I hear any updates. Thanks very much for your patience!

Thanks for flagging this folks! The entire dataset server is down now and I'm pinging people to investigate. Will keep folks posted here as I hear any updates. Thanks very much for your patience!

Hi folks, closing this issue as looks like the server is up and running - you should be able to download the dataset now.


Include specific numpy dtype in output of describe()

As required by event-model, the dtype in describe() is a JSONschema data type, such as "number" or "array". For Tiled (and perhaps for other consumers) we need to know that actual machine data type, such as "<f8" or "<i4". The event-model does not currently specify a place to put this, but databroker+tiled have been using a new key dtype_str to place this (optionally) alongside the JSONschema dtype.
It has been observed this, coming fresh to dtype and dtype_str, it's not at all clear what these keys mean. We should evaluate our options, with a view toward both using obvious names and supporting backward-compatibility. Then we update event-model as needed and add the numpy-style data types here.

This design decision affects the schema, so I started an Issue at https://github.com/bluesky/event-model/issues/308. Once we decide on the spelling, we can implement describe() acordingly.

numpy types for arrays
python types for scalars, but limit soft signals to int64 and float64

Add datatype to ShapeProvider as part of this

Decided on dtype_numpy instead of dtype_str over in https://github.com/bluesky/event-model/issues/308

Closed with #438


Merge pull request #1 from naver/master

Bringing fork up to date

 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.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@b9b5411). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #6605   +/-   ##
=========================================
  Coverage          ?   39.27%
=========================================
  Files             ?     3102
  Lines             ?    92712
  Branches          ?    11923
=========================================
  Hits              ?    36417
  Misses            ?    53290
  Partials          ?     3005

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 b9b5411...c0f26e4. Read the comment docs.


Some missing dirty sites...

@StevenBlack @Sinfonietta
https://stape.fun/ (Ex: https://stape.fun/v/MzMdZqVOlrfwpX/16285410026111904a0c2da.mp4)
https://streamtape.com (Ex: https://streamtape.com/v/8qbRG662BQFobxJ/IMG_6481.MP4)
https://selfiedump.com/ (Ex: https://selfiedump.com/140013)

Thank you for this John @Zorono.
@sinfonietta can you please consider listing these?  Thank you!

@StevenBlack @Zorono I have added these thanks

Thank you @Sinfonietta!  Closing.


Update In-tree storage driver status

Follow up on some comments from  PR #42302
/sig storage
/cc @xing-yang
for technical review

/approve
A tech review is desirable. @xing-yang

ping @xing-yang

@kubernetes/sig-storage-pr-reviews : PTAL!
Alternately, @xing-yang whenever you have time, please could you review this?

https://github.com/orgs/kubernetes/teams/sig-storage-pr-reviews : PTAL!
Alternately, @xing-yang whenever you have time, please could you review this?

@divya-mohan0209 I'll take a look. Thanks!

/label tide/merge-method-squash
Preview page:

https://deploy-preview-42415--kubernetes-io-main-staging.netlify.app/docs/concepts/storage/volumes/#gcepersistentdisk
https://deploy-preview-42415--kubernetes-io-main-staging.netlify.app/docs/concepts/storage/persistent-volumes/

/lgtm


Serving impovements

Closes: #910
Description

Misc improvements to Model Serving -- see ticket for the full list.
How Has This Been Tested?

You'll need multiple projects and a few models within' to test some of the effort on the global model serving page.
Merge criteria:

[ ] The commits are squashed in a cohesive manner and have meaningful messages.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

Allow model server replicas to scale to 0

https://github.com/opendatahub-io/odh-dashboard/blob/74ec5b133980636ee360c45a210e2d42ab7d3d7a/frontend/src/pages/modelServing/screens/projects/ServingRuntimeModal/ManageServingRuntimeModal.tsx#L68
Configure becomes disabled even when a valid replica of 0 is set. Set to createData.numReplicas >= 0

(2) allow Request and Limit to be the same value

Same issue as above with validation
https://github.com/opendatahub-io/odh-dashboard/blob/74ec5b133980636ee360c45a210e2d42ab7d3d7a/frontend/src/pages/modelServing/screens/projects/ServingRuntimeModal/ManageServingRuntimeModal.tsx#L73-L76
Also, is it an issue that a user can request a limit of 1 milicore but request a whole core (same with memory units)?
Maybe there should be an additional validation for differing units. Possibly also an error message as this could be a not obvious issue to a user

(2) allow Request and Limit to be the same value

Ah good call on the units -- and wow, I totally missed no2 when I was going through. Thanks!

LGTM

/lgtm

/approve

Trying to wait on #935 as we are going to conflict and I have another PR that also conflicts on 935 -- so I agreed with Chris he can merge first (assuming he is able to clean it up in a timely manner)

Ok perfect!

Looks to be up to date now with the main branch after gpu addition to the model serving

Testing it now


add redirect to route

Are you able to add RedirectToRoute to this please?
RedirectToRoute

Thank you for using the library. Will update once done

@mybigman I've added RedirectToRoute with API similar to mentioned doc.


sub-cycle pulse insertion capability

(from personal email exchange)
Hi, Gents -
WaveDrom is a cool tool for creating cycle-based waveforms, but lacks the ability to place sub-cycle pulses into the waves (without lots of extra characters to stretch out the cycle). I would like to see sub-cycle pulse insertion capability and I would also like to propose the following syntax that could be used (I don't care what the syntax is, but I thought I would at least make a proposal).
For scalar signals, could I suggest:
{name: 'din', wave: '01.0<010.>..10' }
This would insert a ¼ cycle pulse into the 5th cycle. The syntax <010> would also be equivalent to <010.>
The inclusion of the <> angle brackets could denote ¼ sub-cycle granularity.
For buses, a similar syntax would be:
{name: 'data', wave: '22.<.x2.><.22.>222', data: [F0 E3 E7 12 24 A1 B1 B2]}
This would insert X|E7 into the 4th cycle and 12 |24 into the next cycle. Again, the syntax <.x2> = <.x2.> and <.22.> = <.22>
You might also allow <<>> to denote 1/10th cycle pulses, but the <> syntax for ¼ cycle pulses is a great start and might be enough.
The ability to insert short pulses into a cycle-based waveform is a common need, something that would have helped me when using WaveDrom.
Cool tool. I hope you will consider this enhancement.
Regards - Cliff

Hi, Cliff
Thank you for the kind words, great idea, and syntax proposal.
Agree, that it addresses a common need, and it was requested several times in the past.
It will be quite easy to implement 1/2 of a cycle pattern for the default (period:1),
because each cycle of diagram actually constructed out of 2 bricks (skin references).
As well as: 1/4 for (period:2); 1/6 for (period:3); etc.
Is it fine for the first version?
I like your syntax <.10.> and the way to avoid tail padding <.10>
We will definitely consider implementing it soon. Can I mirror this request on the GitHub here: https://github.com/drom/wavedrom/issues ?
That is our usual place for bugs/enchantment requests; public for all collaborators.
Regards,
Aliaksei

Hi, Aliaksei -
The 1/4 for period:2 should work fine.
Permission granted to mirror the request.
Regards - Cliff

@itsayellow what do you think of this idea?

Other option might be using nested arrays of data points. Instead of:
{
  name: 'data', wave: '22.<.x2.><.22.>222',
  data: ['F0', 'E3', 'E7', '12', '24', 'A1', 'B1', 'B2']
}

Use something like:
{
  name: 'data', wave: '22.$$222',
  data: ['F0','E3', '. x E7 .', '12', '24', 'A1', 'B1', 'B2']
}

I like that, because it preserves the "one character equals one time period" methodology.  It would make the code to parse data a little trickier, but I think that should be ok.
One question, I'm wondering if this would fulfill everyone's needs for sub-cycle waveforms.  I could imagine wanting to put a tiny pulse in a sub-cycle waveform, and that wouldn't be in the form of a data label.  Could you put 0 or 1 in the subcycle data list?  If you did, then it would be a little strange because then data field takes on an overlapping meaning with the wave field that it didn't used-to have.

Here's another way that I haven't thought too hard about whether it's great or not, but I thought I'd throw it out there.
{
name: 'data', wave: '22.ab222,
subcycle: { a:'01.0', b:'10.1' }
}
This allows little snippets of sub-cycle waveforms that you could re-use, but it I'm not exactly sure how you would incorporate data strings into this.
Although could you even read sub-cycle data labels?  As it is, if there's only a half-cycle of data, wavedrom doesn't even try to print the label (if it's in the start or end of a waveform, for example.)

I suppose you could bring it all together like
{
  name: 'data', wave: '22.ab222,
  subcycle: { a:'01.0', b:'0220' }
  data: ['F0','E3', ['12', '24'], 'A1', 'B1', 'B2']
}

I agree that you need explicit subcycle format string to be compatible with wave format.
Here is another option:
{
  name: 'data', wave: '22.$$222',
  data: ['F0', 'E3', ['.x2.', 'E7'], ['.22.', '12', '24'], 'A1', 'B1', 'B2']
}

I think I like that a little better.
I was trying to think of a way you could re-use sub-cycles, allowing you to re-use a standard runt-pulse for example.  But using letters in the wave field is a little unsatisfying because we already use 'h','l','H','L','p','P' and it's a little weird to just skip over them and assume the other letters are sub-cycles.  In that way the $ is a nice clear identifier.
We might do like above and also use a "subcycle" field to define all the $ time-periods in order, like the "data" field currently defines all the data cycles:
{
  name: 'data', wave: '22.$$222',
  subcycle: ['.x2.','.22.'],
  data: ['F0', 'E3', ['E7'], ['12', '24'], 'A1', 'B1', 'B2']
}

That way data is only used for data, and subcycle looks like a list of "wavelets" defining each $ in sequence.

@itsayellow the more I look at the original proposal from Cliff Cummings, the more I like it again.
The main concern is that we are stretching wave sequence and (1 char !== 1 cycle) anymore.
The benefit is all format is in one place, and it is the most compact form.

It's true.  It is the conceptually simplest solution.  And everything is in-line, you don't have to pop your eyes back and forth within the same wave object to find what each subcycle is in a separate definition somewhere.  That to me is the biggest advantage.
Already on my own I make little javascript code snippets to do things with my waveforms, like "x4()" which repeats the same string 4 times, etc.  So I have broken the direct 1char<->1cycle wave relationship by adding little functions and it is ok.  Not as easy to read, but ok.  It's easier if you break the 1<->1 in the same place in every waveform, then they all line up.
This would also work for this proposal--if there is a region on the x-axis where EVERY waveform needs more detail, then all the "wave" fields for all waveforms would still line up perfectly, e.g.
{
  name: 'wave1',
  wave: '0...1.<010101010101>..0..1'
}
{
  name: 'wave2',
  wave: '0...1.<000001.00000>..0..1'
}

So you could keep things tidy if you tried.

@itsayellow One limitation of this concept we have to convey clearly to users that number of subcycle details would depend on period.
period: N --> 2*N subcycles

Hi Cliff,
In fact I did. Please try the code below in online version here: http://wavedrom.com/editor.html
There is certain quickness in rendering of sub-cycles, let me know if it is close to your expectations.
--Aliaksei
{ signal: [
  {
      name: 'P1',
      wave: '==2<30>2<0xx1>2333444555',
      data: '0 1 2 a b c 3 4 5 d e f 6 7 8'
  },
  {
      name: 'P2',
      wave: '=2<15.1>2<01>2355',
      data: '0 1 2 a b c 3 4 5 d e f 6 7 8',
      period: 2
  },
  {
      name: 'P3',
      wave: '=2<1001.1>2<01.5>3',
      data: '0 1 2 a b c 3 4 5 d e f 6 7 8',
      period: 3
  },
  {
      name: 'P4',
      wave: '=2<10zuzd1x.1>2',
      data: '0 1 2 a b c 3 4 5 d e f 6 7 8',
      period: 4
  }
]}

On Tue, Jul 5, 2016 at 1:53 PM, Cliff Cummings<EMAIL_ADDRESS>wrote:
Hi, Aliaksei -
Did you ever add this capability to Wavedrom?
Thanks - Cliff


Builder: call to setup matching when 'Affinity Scores' option is selected

Currently when Bid Stage is created the setup_matching is created, some venues want to create paper assignments without bidding.
We need to decide when to call to setup matching so PCs can see the option to run the matching.
Celeste suggested to run it during the Review Stage. We need to make sure the setup_matching doesn't run twice or doesn't override current assignments if they exists.
I would suggest to check if the 'Assignment_Configuration' invitation is created.
Another option is to create a new stage: MatchingStage or AssignmentStage. It would be nice to also compute the scores for the venue.

Fixed.


Can't use other lightcurve class methods after using bin() function

Problem description

I am working with the PDCSAP_FLUX for TESS light curves. When I attempt to first fill the gaps in the light curve and then bin it using Lightkurve functions, I receive a type error like so:
TypeError: No loop matching the specified signature and casting
was found for ufunc bitwise_or
Example

import lightkurve
lcf = lightkurve.search.open(filename)
lc = lcf.PDCSAP_FLUX

lc_filled = lc.fill_gaps()
lc_binned = lc_filled.bin(binsize=15)

Expected behavior

If I understand the docs correctly, both lc.fill_gaps() and lc.bin() should return lightcurve objects and thus the other methods in the class should work on it. However, attempting this returns a type error. I tried .bin(), .normalize(), and .remove_nans() which all gave me the same error.
TypeError: No loop matching the specified signature and casting
was found for ufunc bitwise_or

Oops, this looks like a serious bug!
Slightly simplified snippet to reproduce the problem:
import lightkurve as lk
import numpy as np
lc = lk.TessLightCurve(time=np.arange(50), flux=np.ones(50), quality=np.zeros(50))
lc.bin(binsize=15)

This yields the following exception:
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-1-ecebd391bc07> in <module>
      2 import numpy as np
      3 lc = lk.TessLightCurve(time=np.arange(50), flux=np.ones(50), quality=np.zeros(50))
----> 4 lc.bin(binsize=15)

~/dev/lightkurve/lightkurve/lightcurve.py in bin(self, binsize, bins, method)
   1000                 warnings.simplefilter("ignore", RuntimeWarning)
   1001                 binned_stat = binned_statistic(bin_by_array, values_to_bin,
-> 1002                     statistic=bin_function, bins=bin_edges).statistic
   1003                 setattr(binned_lc, attr, binned_stat)
   1004

~/bin/anaconda/lib/python3.7/site-packages/scipy/stats/_binned_statistic.py in binned_statistic(x, values, statistic, bins, range)
    179
    180     medians, edges, binnumbers = binned_statistic_dd(
--> 181         [x], values, statistic, bins, range)
    182
    183     return BinnedStatisticResult(medians, edges[0], binnumbers)

~/bin/anaconda/lib/python3.7/site-packages/scipy/stats/_binned_statistic.py in binned_statistic_dd(sample, values, statistic, bins, range, expand_binnumbers)
    604         for i in np.unique(binnumbers):
    605             for vv in xrange(Vdim):
--> 606                 result[vv, i] = statistic(values[vv, binnumbers == i])
    607
    608     # Shape into a proper matrix

~/dev/lightkurve/lightkurve/lightcurve.py in <lambda>(x)
    952         method_func = np.__dict__['nan' + method]
    953         quality_func = lambda x: np.bitwise_or.reduce(x) \
--> 954                                  if np.all(np.isfinite(x)) else np.nan
    955         centroid_func = lambda x: method_func(x) \
    956                                   if np.any(np.isfinite(x)) else np.nan

TypeError: No loop matching the specified signature and casting
was found for ufunc bitwise_or

This bug was likely introduced in Lightkurve v1.5.0 via #629.

Findings: the lc.bin() method fails when lc.quality has a non-integer dtype, which is unusual but allowed.
There is a related bug in lc.fill_gaps() which causes the dtype of lc.quality to be turned from integer into floating point.  This explains why the bug in bin() only appears after calling fill_gaps().
This will be easy to fix.

This issue should be fixed now.  A fix and regression test were added in #707
Thanks for reporting this bug @greenstar54! A valuable contribution!! :+1::+1:


Uni.combine().all().unis(Collections.emptyList()).combinedWith(list -> null)

This issue is to express my disappointment about the fact that Uni.combine().all().unis(Collections.emptyList()).combinedWith(list -> null) produces uni which never fires. I believe it should call combinedWith with empty list.
Yes, I found in javadoc "must not be empty"... after spending a few hours trying to find why my transactions are never committed...

Well I'm afraid that if you have an empty list of Uni elements then you have nothing to subscribe to, so the Uni that results from the combination of 0 Uni never emits anything (and combinedWith is never called).

sounds more like implementation details to me

In reactive types nothing happens until you subscribe. So if you trigger a subscription and there is no upstream publisher at all, then you subscribe to nothing, and it doesn't seem odd to get nothing in the remainder of the pipeline.

Well I'm not reactive expert of course.
I see that calling Uni.combine().all().unis(list) I have to check for list emptiness every time, and that makes code to look a lot more complicated than it could be. And of course I have to remember about it and if I forget, it will result in some runtime errors which could be not obviously visible, like timeouts or not committing transactions like in my case.
I checked what other reactive frameworks have:

RxJava has Single and Single.zip(emptyList, arr -> null) throws NoSuchElementException. But it also have Maybe and Maybe.zip(emptyList, arr -> null) returns completed maybe without a value. Single can be easelly converted to Maybe.
ProjectReactor has Mono which acts like Maybe in RxJava and Mono.zip(emptyList, arr-> null) returns completed mono without a value
CompletableFuture which people use the most I think since it's in core java has CompletableFuture.allOf, which returns completed future

So none of them silently eats the list returning Uni which never returns anything.

Would you have a code snippet showing a use-case?

So this code has similar structure to what I had:
@ApplicationScoped
@Slf4j
class Scratch {

    @Inject
    DBRepository dbRepository;

    @Inject
    RestService restService;

    @Scheduled(cron = "0 * * * * ?")
    public void scheduled() {
        //two methods each in a separate transaction
        someTransactionedMethod().subscribe().with(v -> {}, t -> log.debug(t.getMessage(), t));
        anotherTransactionedMethod().subscribe().with(v -> {}, t -> log.debug(t.getMessage(), t));
    }

    @Transactional
    Uni<Void> someTransactionedMethod() {
        List<Object> items1 = dbRepository.queryList1();
        List<Uni<Void>> unis = items1.stream().map(this::restRequestAndSaveDB).collect(Collectors.toList());
                                                // ↓ whoops, it can be empty
        Uni<Void> uni1 = Uni.combine().all().unis(unis).combinedWith(list -> null);

        List<Object> items2 = dbRepository.queryList2();
        Uni<Void> uni2 = restRequestAndSaveDB(items2);
        //if first query returns empty items1 list it will result in uni1 which never finishes
        //so all db saves done for second items2 list will hang in uncommitted state until cancelled by transaction timeout
        return Uni.combine().all().unis(uni1, uni2).combinedWith((v1, v2) -> null);
    }

    @Transactional
    Uni<Void> anotherTransactionedMethod() {
        //some logic here
        return Uni.createFrom().item(null);
    }

    Uni<Void> restRequestAndSaveDB(Object item) {
        Uni<Result> uni = restService.doSomeRestRequestAndReturnUni(item);
        return uni.map(result -> {
            DBObj dbObj = new DBObj();
            dbObj.setSomething(result.getSomething());
            dbRepository.persist(dbObj);
            return null;
        });
    }

    Uni<Void> restRequestAndSaveDB(List<Object> items) {
        Uni<List<Result>> uni = restService.doSomeRestRequestAndReturnUni(items);
        return uni.map(resultList -> {
            List<DBObj> dbObjs = resultList.stream().map(result -> {
                DBObj dbObj = new DBObj();
                dbObj.setSomething(result.getSomething());
                return dbObj;
            }).collect(Collectors.toList());
            dbRepository.persist(dbObjs);
            return null;
        });
    }
}

So I was wondering for quite some time why I persist items in the database and nothing happens...
I finally find the issue and had to rewrite method to
    @Transactional
    Uni<Void> someTransactionedMethod() {
        List<Object> items1 = dbRepository.queryList1();
        List<Uni<Void>> unis = items1.stream().map(this::restRequestAndSaveDB).collect(Collectors.toList());
        Uni<Void> uni1;
        if (unis.isEmpty()) {
            uni1 = Uni.createFrom().voidItem();
        } else {
            uni1 = Uni.combine().all().unis(unis).combinedWith(list -> null);
        }

        List<Object> items2 = dbRepository.queryList2();
        Uni<Void> uni2 = restRequestAndSaveDB(items2);
        //now both uni always finish and returned uni also finishes
        //so transaction manager sees Uni has finised and commits transaction
        return Uni.combine().all().unis(uni1, uni2).combinedWith((v1, v2) -> null);
    }


run_finch: Add docs on Finch pools

Finch starts pool for each {protocol, host, port}, so we might end up with a bunch of pools after a while. We should document this, mention :pool_max_idle_time option, and make it possible to pass that option down to Finch.

@wojtekmach Was just looking for Req + Finch pools docs :) Is there a way to configure the Finch pools that Req uses globally? e.g. how Finch does it:
children = [
  {Finch,
   name: MyConfiguredFinch,
   pools: %{
     :default => [size: 10],
     "https://hex.pm" => [size: 32, count: 8]
   }}
]

Yes, Req.new(finch: MyConfiguredFinch). See Req.Steps.run_finch/1 for more information.

@wojtekmach Just to confirm: That's for an individual Req.Request instance, right? I'm wondering about a way to change the default finch adapter/setting for all Req.Request structs.

You can use Req.default_options/1 for that but it is better to avoid this global configuration and instead pass the options explicitly to Req.new, Req.get etc.


Suggestion: Button 'Edit configuration file'

Hi.
Just a usability suggestion, to make it simpler/faster to trigger the editing of the 'configuration file' through a button in the UI (screenshot below).
After changing paths in my computer I had to update 'favorites.json' to match them, and if a button was there it would have been handy.
Thank you!

Packed this suggestion into the next release !


Upgrade to .net8

This PR requires Elenpay/NBXplorer#9

We are running this in STG via Elenpay/platform#732

We are running this in STG via Elenpay/platform#732 and deployed via this branch

Does this hack fix it then?

We are running this in STG via Elenpay/platform#732 and deployed via this branch

Does this hack fix it then?

Seems so, it does compile and runs. It does not differ much from https://github.com/dgarage/NBXplorer/blob/master/NBXplorer/NBXplorer.csproj
I could update those things that we have introduced like OpenTelemetry but net8 is supported in the current version also.

@RodriFS @gcaracuel #10 closes this?

@RodriFS @gcaracuel #10 closes this?

Yes, @RodriFS 's new PR takes care of this in the proper way


fix for Azure SQL Serverless Connectivty issue

Description & motivation
So it turns out the "serverless" tier of Azure SQL db we're using will auto-pause. To wake it up you have to try and log-in once, have it fail, then try again. Long term, def need to move this testing to a standard tier db, but short term this should work. Per this doc page

If a serverless database is paused, then the first login will resume the database and return an error stating that the database is unavailable with error code 40613. Once the database is resumed, the login must be retried to establish connectivity. Database clients with connection retry logic should not need to be modified.

Checklist

[ ] I have verified that these changes work locally
[ ] I have updated the README.md (if applicable)
[ ] I have added tests & descriptions to my models (and macros if applicable)

not sure if this is a great work around... because the entire job fails even the job works on on the second step...

not sure if this is a great work around... because the entire job fails even the job works on on the second step...

Closing because of this comment:

I actually was able to change the compute tier of the Azure SQL db, so we shouldn't get the login timeout errors anymore.

Closing because of this comment:

I actually was able to change the compute tier of the Azure SQL db, so we shouldn't get the login timeout errors anymore.


Misaligned Phone Indicator

Describe the bug
The icon indicating that a user is online on a phone, destroys the alignment of the profile picture
To Reproduce
Look at your friend list. I tried different resolutions, issue persists.
Screenshots
 in friend list
 in chat
Information:
Discord channel: Stable
OS: Windows
Mod: BetterDiscord
Discord language: English

oh. That's what causes it. Yeah, that's annoying, lol. Ive been trying to fix this for a hot minute but its really damn annoying

I'll provide my own encounter with this issue, with the addition of having radial status loaded

I think this is more of an issue with radialstatus than softx, but I'll have to check...

Saem goes for the Set Custom Status Menu btw. will maybe create another issue for that

I did some messing around with the theme settings, I commented the lines that import radial status and radial glow, and the problem was no longer present, so this is definitely a radialstatus issue, I'll open an issue there.


⚠ Bofrost.de has degraded performance

In b21f78f, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1445 ms

Resolved: Bofrost.de performance has improved in 09e7a45 after 7 minutes.


Einsum error using separable Fourier convolution

Hi,
There seems to be an issue in the tensor contraction when using the separable Fourier convolution option (separable=True).
The problem occurred when I tested the plot_FNO_darcy.py example with Tucker contraction as well as in my own toy project.
Seems like the Einstein summation is not correctly set.
Below, I only pasted the part of the stacktrace which I deemed most relevant. The full error should be reproducible when adding the above option to the model init in the example.
Traceback (most recent call last):   File "C:\Users\Henrik\virtual_environments\neuraloperator\venv\lib\site-packages\tensorly\plugins.py", line 72, in cached_einsum     expression = OPT_EINSUM_PATH_CACHE[key] KeyError: 'abcd,fghi,bf,eg,ch,di->aecd,(32, 32, 9, 9),(20, 10, 6),(32, 20),(16, 10),(9, 6)'
...
 File "C:\Users\Henrik\virtual_environments\venv_pytorch\lib\site-packages\opt_einsum\parser.py", line 354, in parse_einsum_input     raise ValueError("Number of einsum subscripts must be equal to the " "number of operands.") ValueError: Number of einsum subscripts must be equal to the number of operands.

Hi @HenrikAsmuth , thanks for this issue. When I've seen this error in the past, it's been because the shape of the input is not correct. What input shape are you using in your forward pass?

Hi @HenrikAsmuth , i looked into this this morning and found a bug in SpectralConv that is fixed by #389 . Thank you so much for bringing this to our attention!

Thank Dave for the quick fix. Will test it asap once it's merged.

Merged #389


Raccoon user agent

Hi, in a recent investigation I've found out a user agent used by a phishing as a service package, it might be interesting to add it to your user agents list!
User agent is RaccoonO365/9.0 (RaccoonO365; Intel Raccoon O365 2FA/MFA 10_15_7)
Context on raccoon o365: https://www.reddit.com/r/msp/comments/1fqiajn/raccoon0365/

Hi @Cloaec thank you ! it's added to the list https://github.com/mthcht/awesome-lists/commit/fea492607e0ce121feb34dc21e9766de1c971509 !


[Enhancement] Upload Demo to Microsoft Windows Store，Google Play Store and Apple Store etc.

Summary
Could you consider upload the app to the stores？

I personally wonder if that would even be possible. It's a sample app, nothing more, nothing less. We would need to get all the legal bits in place, payments for different store accounts and all of the additional things that come with deploying to stores. Furthermore, I have my doubts that someone like Apple would even approve an app that's merely there for sample purposes.
What would be the use case for it being in the store? It's a developer tool primarily, so a developer can take it and run it on a device locally without too much effort.

You are right , my purpose is just want quickly see the feature ,may be you can uploade the gif to Microsoft docs and Github .md file (but github is very slow in china to load image)

@jingliancui thanks for your suggestion! Although I like the idea of having some kind of showcase app that makes this easier, I don't think it will happen soon. We need a lot of infrastructure (accounts, payment, etc.) like Steven mentioned for this.
What could make this easier for you? We are working on documentation on the official Microsoft Docs, if that is complete and has some screenshots, might that be enough for you?

@jfversluis Thansk, official Microsoft Docs is enough, maybe more gif images will be greate. And mention that image on github is very slow in China and sometime it doesn't load .

I think it would be a great idea.  Look at the Syncfusion app at least in Google Play.  It showcases their controls and has links to github source.  I use it often to get ideas or as a refresher on functionality.

I can see this being a lot of hurdles to jump through.
It could be added to an App Center deployment lifecycle to automate.
Example Apps:
Telerik UI for Xamarin Samples
https://apps.apple.com/gb/app/telerik-ui-for-xamarin-samples/id1083924868
Where to find Syncfusion Xamarin Forms Sample Apps
https://www.syncfusion.com/kb/10811/where-to-find-syncfusion-xamarin-forms-sample-apps
There was an iOS app but it might have been pulled now.

@jfversluis  We can use the AppCenter for this, the Essentials uses this approach.


How should I load JS libraries from within WASM?

(Potentially related to https://github.com/dart-lang/sdk/issues/55733)
Currently, it's unclear what the "well-paved road" is for loading JavaScript libraries within a WASM context. For built-in JS APIs, it's easy: I use dart:js_interop to define the shape of the JS API I want to use and tell Dart what its global name is, and then it gets wired up for me in the generated mjs wrapper. But what if I want to access a name that's not globally available in every context?
Any global name I write via dart:js_interop gets translated in the mjs wrapper to globalThis.<name>. But adding values to this isn't very ergonomic; for example, you can't write:
import * as lib from 'library';
globalThis.lib = lib;
import {instantiate, invoke} from './myapp.mjs';

myapp.mjs won't see globalThis.lib. You'd have to put that assignment in a third library in order for it to work. Is that really the expected pattern here? Or should there be a better way?

Would importing libraries via the dynamic import make this easier? You can define an interface for the resulting JSObject module.

Asynchronous loads are not feasible in this case.

We urgently need an unsafe static definition of methods such as' import xxx from xxx 'and' export xxx '. When I learned about the implementation of dynamic pouring, it seemed that it was very easy for Dart SDK to implement it.
With true top attribute access, we can use Dart to develop any content that complies with CJS or ESM.


Fix graph when only one usage

When i use only VSC, the graph is glitched. Probably the same with other metrics

Fixed in v1.1.4


Recipe Book Window unable to close

Describe the Bug
When I load a saved game that Recipe book were open, there will be a recipe book window that can't be closed.
How To Reproduce
Host new game.
Open Recipe Book.
Save the game (without closing the Recipe Book Window).
Host the saved game again (it will show Recipe Book Window, but you won't be able to close. And when you open, you'll open another one).
Each time, it will open another Window that can't be closed.
Image

Could you attach a save file? I am unable to reproduce this.

Here: c.zip

Detail: This problem just happen to me when I save the window opened while hosting. If I set as single player, this error doesn't happen.

Ah, that's probably why I couldn't reproduce it - I was doing it on singleplayer. I'll let you know.

Thanks for the report, this has been fixed for the next release.


Handle view server crashing during test compile of view functions.

Due to how libmozjs185 library is compiled on Ubuntu 12.04, given
invalid JS code, it will not return with expected error result:
["error","compilation_error",...]
but will crash. Otherwise library seems functional --  it passes
all other mrview tests.
Handle this crash in try_compile() function as a compilation
failure. Error message contains the exit status of the view process
to help debugging.

+1

@rnewson  @kxepal  -- renamed PErr to ExitStatus. Fixed spacing issue.


Incorrect indent guides with treesitter enabled

When tree sitter is enabled there are indent lines on lines 91-97 which should not be there.  Strangely these indent lines are not highlighted like the lines above.
init.vim indent-blankline settings:
let g:indent_blankline_use_treesitter = v:true
let g:indent_blankline_show_current_context = v:true

Treesitter enabled:

Treesitter disabled:

Treesitter indentation for python isn't that great.
You can open an issue there https://github.com/tree-sitter/tree-sitter-python
This plugin just takes the value that treesitter returns. Nothing I can do here to fix this.